search for: crvs

...ks. the build tools are different from the naive build tools as follows: CC="p llvm-gcc-4.2 `llvm-config --cflags` -march=i386 --emit-llvm -O0 -c -I$PLAT/include -I$ROOT/include -I$ROOT/utils/ include" LD="p llvm-ld `llvm-config --ldflags --libs all `" AR="p llvm-ar crvs" any simplifications or rules of thumb that might help would be greatly appreciated.... the build proceeds, finishes, and leaves me guessing: #957$457 Thu 09073022:29:22 jim at bframe4:~/work/inferno : CC=llvm-gcc-4.2 PATH=/usr/local/inferno/MacOSX/386/bin/:/opt/local/bin:$PATH ./makemk.sh...

...mes northrup<northrup.james at gmail.com> wrote: > CC="p llvm-gcc-4.2 `llvm-config --cflags` -march=i386  --emit-llvm -O0 >  -c -I$PLAT/include -I$ROOT/include -I$ROOT/utils/    include" > LD="p llvm-ld `llvm-config --ldflags --libs all  `" > AR="p llvm-ar crvs" Using llvm-ar+llvm-ld is likely to give you bad results. On Mac, AFAIK, the native ar and ld should do the right thing with bitcode files, assuming you have relatively recent versions; I don't know the details, though, since I don't have a Mac. -Eli

...-c mxml-attr.c gcc -O -Wall -c mxml-entity.c gcc -O -Wall -c mxml-file.c gcc -O -Wall -c mxml-index.c gcc -O -Wall -c mxml-node.c gcc -O -Wall -c mxml-search.c gcc -O -Wall -c mxml-set.c gcc -O -Wall -c mxml-private.c gcc -O -Wall -c mxml-string.c /bin/rm -f libmxml.a /usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o a - mxml-attr.o a - mxml-entity.o a - mxml-file.o a - mxml-index.o a - mxml-node.o a - mxml-search.o a - mxml-set.o a - mxml-private.o a - mxml-string.o ranlib libmxml.a ma...

1.6.1 svn 190575: CC="cc" CXX="g++" LD="" AR="" RANLIB="" CFLAGS="" make -C menuselect CONFIGURE_SILENT="--silent" menuselect make[1]: Entering directory `/home/asterisk/rpmbuild/BUILD/asterisk-1.6.1/menuselect' gcc -m64 -march=native -mtune=native -floop-interchange -floop-strip-mine -floop-block -c -o