tinycc-devel
[Top][All Lists]
Advanced

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

Re: [Tinycc-devel] Help with tests... (osx build but please read anyway)


From: David Mertens
Subject: Re: [Tinycc-devel] Help with tests... (osx build but please read anyway)
Date: Thu, 9 Feb 2012 14:10:14 -0600

Milutin -

This is great news! I've been thinking about playing with tcc but my aim is cross-platform and I wanted to have something that works on Macs. I couldn't even compile the current tcc on my 10.7, but I'll see if I can compile your work and start playing with this soon!

:-D

David

2012/2/9 Milutin Jovanović <address@hidden>

Hi all,

Before I get to the crux of my mail, I'd like to send a greeting to all. I've been using tcc on and off on windows for a while, and it is a sleek little tool. Thanks for your efforts!

I am attempting to do a OSX build. OSX problems for tcc are nothing new, but I decided to give it a go any way. I made an attempt to make tcc build and run, by incorporating some fixes I found and by making some modifications myself. So far, so good, it builds and a very basic test works. You can see my mob commit

http://repo.or.cz/w/tinycc.git/commit/8ca8b08890c220a9e238c711aef96b49727e80f0

to check my changes.

However, I am now stuck with some tests. The test output is below. The issue seems related to the old "tcc does not do mach-o binaries", but I am only guessing. If anyone has any better understanding of what the tests are trying to do, I'd appreciate a comment.

$ make test
make -C tests test
gcc -o libtcc_test libtcc_test.c ../libtcc.a -I.. -Wall -g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare -D_FORTIFY_SOURCE=0 -lm -ldl
------------ libtest ------------
./libtcc_test lib_path=..
Hello World!
fib(32) = 2178309
add(32, 64) = 96
cp ../include/tcclib.h .
gcc -o tcctest.gcc tcctest.c -I. -w -Wall -g -O2 -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare -D_FORTIFY_SOURCE=0 -std=gnu99
Undefined symbols for architecture x86_64:
  "_weak_f1", referenced from:
      _weak_test in ccSy7y2b.o
  "_weak_v1", referenced from:
      _weak_test in ccSy7y2b.o
  "_weak_fpa", referenced from:
      _weak_test in ccSy7y2b.o
  "_weak_fpb", referenced from:
      _weak_test in ccSy7y2b.o
  "_weak_fpc", referenced from:
      _weak_test in ccSy7y2b.o
  "weak_asm_f1x", referenced from:
      _weak_test in ccSy7y2b.o
  "weak_asm_f2x", referenced from:
      _weak_test in ccSy7y2b.o
  "weak_asm_f3x", referenced from:
      _weak_test in ccSy7y2b.o
  "weak_asm_v1x", referenced from:
      _weak_test in ccSy7y2b.o
  "weak_asm_v2x", referenced from:
      _weak_test in ccSy7y2b.o
  "weak_asm_v3x", referenced from:
      _weak_test in ccSy7y2b.o
ld: symbol(s) not found for architecture x86_64
collect2: ld returned 1 exit status
make[1]: *** [test.ref] Error 1
make: *** [test] Error 2


--
Miki.


_______________________________________________
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


reply via email to

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