tinycc-devel
[Top][All Lists]
Advanced

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

Re: [Tinycc-devel] cleanups


From: David Mertens
Subject: Re: [Tinycc-devel] cleanups
Date: Sat, 15 Oct 2016 22:41:10 -0400

Ah, now I get errors running the preprocessor tests. Here's a representative result:

PPTest 14 ...
--- 14.expect    2016-10-15 13:07:53.790016538 -0400
+++ 14.output    2016-10-15 22:36:25.971293975 -0400
@@ -1,3 +1,8 @@
+
 return Z(Z(1,2),2);
+
 return Q(1,2);
+
 return ((A + A) * (A + A)) + ((B * B) + (B * B));
+
+tcc: error: file '/usr/local/lib/tcc/x86-64/libtcc1.a' not found

Obviously something (a lib path?) is not getting set up correctly for these, though it is getting set up correctly for the other tests. In case it's not obvious, I have not installed tcc to a system-wide path. I suspect there's something amiss in the pp makefile, but I am not a makefile guru.

David

On Sat, Oct 15, 2016 at 10:23 PM, David Mertens <address@hidden> wrote:
D'oh! Thanks!

On Sat, Oct 15, 2016 at 6:09 PM, Michael Matz <address@hidden> wrote:
Hello,

On Sat, 15 Oct 2016, David Mertens wrote:

This commit:

0a624782dfc8fee6f0600066b135d3b20e4274f4

causes "make test" to fail on my 64-bit Linux (ubuntu 16.04). Any idea of
what's going on? Below is the output of "make" followed by "make test".

$ make test
../tcc -B.. -I/include -I -I.. ../examples/ex1.c -o hello || (../tcc -vv;

See the -I/include here.  It's missing the setting of SRCTOP.  Which means you haven't rerun configure after this commit.  Just do ./configure and be done.


Ciao,
Michael.


_______________________________________________
Tinycc-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/tinycc-devel



--
 "Debugging is twice as hard as writing the code in the first place.
  Therefore, if you write the code as cleverly as possible, you are,
  by definition, not smart enough to debug it." -- Brian Kernighan



--
 "Debugging is twice as hard as writing the code in the first place.
  Therefore, if you write the code as cleverly as possible, you are,
  by definition, not smart enough to debug it." -- Brian Kernighan

reply via email to

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