Hi,

As far as I can see, the problem is not OS X related, but rather it is
related to using gcc-4.2, or another version of the gcc compiler. If you
use latest llvm version, it should work. If I use gcc-4.2 I get the same
problem as you. It might help if you can send your printout of commands:

$ gcc --version
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build
5658) (LLVM build 2336.1.00)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

In any case I will see if I can figure out what is going on.

Miki.



On 10 June 2012 00:51, Pedro A ARANDA <[email protected]> wrote:

>  Hi,
>
> I'm trying to compile tinycc on an older Intel Mac. It is detected as x86
> by configure. During the build,
> when tcc is used to create libtcc.a, it crashes with a segmentation fault:
>
> gcc -o tcc tcc.o libtcc.a -lm -ldl -Wall -g -O2 -fno-strict-aliasing
> -Wno-pointer-sign -Wno-sign-compare -D_FORTIFY_SOURCE=0
> -mpreferred-stack-boundary=2 -march=i386 -falign-functions=0 -m32
> gcc -o tiny_libmaker win32/tools/tiny_libmaker.c -Wall -g -O2
> -fno-strict-aliasing -Wno-pointer-sign -Wno-sign-compare
> -D_FORTIFY_SOURCE=0 -mpreferred-stack-boundary=2 -march=i386
> -falign-functions=0 -m32
> mkdir -p i386
> ../tcc -B.. -m32 -D_ANSI_SOURCE -c libtcc1.c -o i386/libtcc1.o
> -DTCC_TARGET_I386
> make[1]: *** [i386/libtcc1.o] Segmentation fault
> make: *** [libtcc1.a] Error 2
>
> The uname -a command yields
>
> Darwin Pedro-A-Arandas-mac.local 10.5.0 Darwin Kernel Version 10.5.0: Fri
> Nov  5 23:20:39 PDT 2010; root:xnu-1504.9.17~1/RELEASE_I386 i386
>
> Cheers,/PA
>
>
>
> _______________________________________________
> Tinycc-devel mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel
>
>
_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to