similar to: [LLVMdev] fPIC in llvm 2.6

> Is fPIC broken on x86_64 in LLVM 2.6? No, it works w/o any problems > ------------------- >  > llvm-gcc -Iinclude -emit-llvm -fPIC -O3 -c -o file.opt.bc  file.c >  > llvm-ld -native -Xlinker=-shared -Xlinker=-Wl,-soname,libtest.so -o > file.so file.opt.bc > ------------------- PIC-ness is a backend option. So, passing -fPIC to llvm-gcc does not make any sense, it is not

The reason I was linking via llvm-ld is because I didn't know how to pass bitcode files to llvm-gcc. How can I do that? Anton Korobeynikov wrote: >> Is fPIC broken on x86_64 in LLVM 2.6? > No, it works w/o any problems > >> ------------------- >> > llvm-gcc -Iinclude -emit-llvm -fPIC -O3 -c -o file.opt.bc file.c >> > llvm-ld -native -Xlinker=-shared

You do it by using the -flto flag. But you will need a linker that's able to handle the bitcode files. The Apple linker can and so can the "gold" linker. -bw On Oct 3, 2010, at 7:47 PM, Ryan M. Lefever wrote: > The reason I was linking via llvm-ld is because I didn't know how to > pass bitcode files to llvm-gcc. How can I do that? > > Anton Korobeynikov wrote:

It appears that llvm-ld can handle bitcode files but llvm-gcc complains that when I pass bitcode files to it. I assume that means that llvm-gcc does not use llvm-ld by default. Is there a way to force it to use llvm-ld? Bill Wendling wrote: > You do it by using the -flto flag. But you will need a linker that's able to handle the bitcode files. The Apple linker can and so can the

On my 32 bit linux box, things seam to work find, but on my 64 bit linux box I am getting problems. I have the following c file (lib.c): -------------------------------- #include <stdio.h> void libmethod(){ printf("libmethod()\n"); } ------------------------------- I tried to get a shared library using the following commands: llvm-gcc -emit-llvm -Wall -fPIC -c -o lib.opt.bc

Does llvm-gcc support the -fPIC option? I am using LLVM on both 32 bit linux and 64 bit linux, if that matters. Regards, Ryan -- Ryan M. Lefever [http://www.crhc.uiuc.edu/~lefever/index.html]

Yup! -bw On Nov 3, 2008, at 7:39 PM, Ryan M. Lefever wrote: > Does llvm-gcc support the -fPIC option? I am using LLVM on both 32 > bit > linux and 64 bit linux, if that matters. > > Regards, > Ryan > > -- > Ryan M. Lefever [http://www.crhc.uiuc.edu/~lefever/index.html] > _______________________________________________ > LLVM Developers mailing list >

I am instaling asterisk on Fedora core 3. I have instaled zaptel-1.2.3, libpri-1.2.2, but when I am instaling (make install) asterisk I have the following error: .................... _GNU_SOURCE -O6 -march=i686 -DZAPTEL_OPTIMIZATIONS -fomit-frame-pointer -fPIC -c -o app_zapscan.o app_zapscan.c gcc -shared -Xlinker -x -o app_zapscan.so app_zapscan.o gcc -pipe -Wall

Hi - after hearing others rave about * I thought I'd have a go - extract from a 'make' on a stock debian system as follows... (I tried to post the whole make up to this point but it was too big for the list) make[1]: Leaving directory `/usr/src/asterisk/channels' make[1]: Entering directory `/usr/src/asterisk/pbx' gcc -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes

After looking through the README for the llvm gcc frontend, it says: ----------------------------------------------------------------------- X86-64/AMD-64/EM64-T for any OS other than Darwin/Mac OS X: When targeting non-darwin X86-64/AMD-64/EM64-T, configure with --disable-shared. The LLVM X86-64 backend doesn't support PIC codegen on non-darwin systems yet. If you get a build error, try

hello i have a small problem in installation of asterisk can any one tell me what is the solution gcc -shared -Xlinker -x -o app_zapscan.so app_zapscan.o gcc -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g -Iinclude -I../include -D_REENTRANT -D_GNU_SOURCE -O6 -march=i686 -DZAPTEL_OPTIMIZATIONS -DASTERISK_VERSION=\"CVS-HEAD-05/26/05-20:43:39\"

Hi everyone: I'm trying to compile Asterisk on FreeBSD 6.0-RELEASE and I'm getting the following error: cc -O2 -fno-strict-aliasing -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Iinclude -I../include -D_REENTRANT -D_GNU_SOURCE -DMAKE_VALGRIND_HAPPY -I/usr/local/include -L/usr/local/lib -I/usr/local/include/spandsp -DZAPTEL_OPTIMIZATIONS

I am trying to build asterisk-0.9.0 on 533MHz 160MB Redhat Linux 9.0 machine. I have followed the instructions to build asterisk. Building zaptel and libpri seemed to go well (lots of messages but nothing that indicated an error) However, when I do the make clean ; make install for asterisk-0.9.0 after running for sometime I get the following: gcc -shared -Xlinker -x -o app_senddtmf.so

<<[Samba] [ANNOUNCE] Samba 3.2.1 Available for Download.eml>> ********* *BEGIN ENCRYPTED or SIGNED PART* ********* Michael Adam wrote: > That is right: the link creation in source/bin is fixed, > but the installation of the links is still broken. > > It _is_ fixed in the v3-3-test branch which will be used for > 3.3.0 (scheduled for December). The changes to the Make

Hi, It's taken me ages to get past teh compile dependencies and having to build most of the dependencies from source. I then ran make and within a few short compilations the samba3 make fails with the following errors: ~/samba-3.5.5/source3> make Using CFLAGS = -I../lib/zlib -I/app/utils//include -O -I. -I/app/builduser/samba-3.5.5/source3

Hello maybe someone can help me? I did the CVS checkout and then compiled asterisk Then I tried to compile the addons and got the following (don't understand what's wrong at all and can't find anything about this error on google/wiki) app_addon_sql_mysql.c:164:64: macro "AST_LIST_REMOVE" requires 4 arguments, but only 3 given app_addon_sql_mysql.c: In function

I'm trying to compile the last * CVS version and I got this error: gcc -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g -Iinclude -I../include -D_REENTRANT -D_GNU_SOURCE -O6 -march=i686 -DZAPTEL_OPTIMIZATIONS -DASTERISK_VERSION=\"CVS-09/10/03-18:47:18\" -DINSTALL_PREFIX=\"\" -DASTETCDIR=\"/etc/asterisk\"

Apparently this didn't/doesn't build on FreeBSD by default...or is it "doesn't build at all". If it is buildable, what should I do to build it, as without it...see wiki: http://wiki.samba.org/index.php/Samba4/Winbind Cheers, TMS III

Do anybody could compile app_conference on x86_64??? I tryied with two versions of app_conference and got the same problem on compiling: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared recompile with -fPIC app_conference.o: could not read symbols: Bad value" ENVIRONMENT:

I am nuilding that now. CC=clang CXX=clang++ cmake -DCMAKE_INSTALL_PREFIX=$HOME/opt/llvm11-git \ -DCMAKE_BUILD_TYPE=Release \ -DBUILD_SHARED_LIBS=ON \ -DLLVM_ENABLE_EH=ON \ -DLLVM_ENABLE_RTTI=ON \ -DLLVM_HOST_TRIPLE=x86_64-pc-linux-gnu \ -DLLVM_TARGETS_TO_BUILD="AMDGPU;MSP430;WebAssembly;X86" \