This is strange, as I did not have to do any of this. Would you mind telling me which version of xcode you have, and also if you have macports installed?
I have latest xcode, and a healthy number of ports installed. I don't think they should matter, but you never know. Miki. On 15 February 2012 18:53, David Mertens <dcmertens.p...@gmail.com> wrote: > I found that if I edit config.mak and change ARCH=i686, the compile moves > forward just fine. However, the next step, > > ar rcs libtcc.a > > fails with the message "ar: no archive members specified" > > I have not investigated further, but thought I'd pass that along. I hope > to spend some more time on this tonight. > > David > On Feb 15, 2012 5:28 PM, "Jorge Alberto Garcia" < > jorge.garcia.gonza...@gmail.com> wrote: > >> Hi , this also happens on Leopard I remember to change >> >> -mpreferred-stack-boundary=2 >> to >> -mpreferred-stack-boundary=4 >> >> dont remember what i did about the rest... >> >> J.A. Garcia >> >> >> On Wed, Feb 15, 2012 at 6:14 AM, David Mertens >> <dcmertens.p...@gmail.com>wrote: >> >>> Milutin - >>> >>> I had some trouble compiling your code on Lion. Here is what I did, >>> starting from scratch: >>> >>> # Clone and get into the source directory: >>> git clone git://repo.or.cz/tinycc.git >>> cd tinycc >>> # Check out the latest mob and create a named local branch: >>> git checkout origin/mob >>> git checkout -b mob >>> # Try to compile: >>> ./configure >>> make >>> >>> For make I get this output: >>> gcc -o tcc.o -c tcc.c -DTCC_TARGET_I386 -DWITHOUT_LIBTCC -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 >>> tcc.c:1: error: CPU you selected does not support x86-64 instruction set >>> tcc.c:1: error: CPU you selected does not support x86-64 instruction set >>> tcc.c:1: error: -mpreferred-stack-boundary=2 is not between 4 and 12 >>> make: *** [tcc.o] Error 1 >>> >>> The errors make some sense to me, but I have no idea why the flags are >>> set the way they are set. I just left it up to ./configure to figure out. >>> >>> Any suggestions? Would any particular diagnostic output be helpful? >>> >>> David >>> >>> >>> -- >>> "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 >>> >>> >>> _______________________________________________ >>> Tinycc-devel mailing list >>> Tinycc-devel@nongnu.org >>> https://lists.nongnu.org/mailman/listinfo/tinycc-devel >>> >>> >> >> _______________________________________________ >> Tinycc-devel mailing list >> Tinycc-devel@nongnu.org >> https://lists.nongnu.org/mailman/listinfo/tinycc-devel >> >> > _______________________________________________ > Tinycc-devel mailing list > Tinycc-devel@nongnu.org > https://lists.nongnu.org/mailman/listinfo/tinycc-devel > > -- Miki.
_______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
