[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Tinycc-devel] Make'ing tcc-0.9.14

From: Mitchell N Charity
Subject: [Tinycc-devel] Make'ing tcc-0.9.14
Date: Fri, 6 Dec 2002 11:27:10 -0500

(1) libtcc_test fails

  $ ./libtcc_test 
  <string>:1: unrecognized character \x00
  <string>:1: foo not defined

[tcc-0.9.14, RedHat 7.mumble, i686, gcc 2.96]

(2) README patch, clarifying make options.

--- README      Sun Nov 24 10:56:44 2002
+++ README.new  Fri Dec  6 10:46:34 2002
@@ -35,6 +35,11 @@
 Type 'make install' to compile and install tcc in /usr/local/bin and
+Or type 'make all' to only compile it.
+Type 'make libinstall' to compile and install libtcc.
+Or type 'make libtcc_test' to only compile it.
 2) Introduction
 We assume here that you know ANSI C. Look at the example ex1.c to know

I am not saying this is a great way to structure the Makefile, but
let us at least document it, so folks don't have to study the Makefile
to figure out what to do (and what not to do, eg, 'make libtcc').  And
many folks like to build and test software before installing it.

(3) 'make test' fails

  [RedHat 7.mumble]
  $ make test
    gcc -O2 -g -Wall -m386 -malign-functions=0
      -DCONFIG_TCC_PREFIX=\"/usr/local\" -I. -o tcctest.ref tcctest.c
    tcctest.c:26:22: warning: extra tokens at end of #include directive
    tcctest.c:26:26: tcclib: No such file or directory
    make: *** [tcctest.ref] Error 1
  $ gcc --version

I reflexively type 'make test' after 'make'.
Here it was just another "ouch!" in making .14.

The libtcc_test problem seems to stem from libtcc, rather than libtcc_test.c.
So I can start debugging tcc.c etal, or wait for .15 before continuing work
on my perl Inline::C::DisklessTCC module, which, all in memory, automagically
generates glue code, compiles, and dynamically links C code embedded in perl,
or run time generated by it.  Oh well.

Is anyone else actually trying to use libtcc?
How are you approaching it?

Thanks for all the work,
Mitchell Charity

reply via email to

[Prev in Thread] Current Thread [Next in Thread]