similar to: Compiling NUT static binaries

Has anyone tried or had success statically linking Asterisk? I'd like to do this to deploy to smaller boxes that don't have the toolchain and libraries to build the thing. I've tried using statifier (at sf.net) which claims to take a dynamic executable and transform it into a static executable. It seemed to work on my box, but when I tried it on the target box it did this:

Hi I use RH 9 + asterisk v1.0 stable + 2 PCI fritz cards + chan_capi 3.5 and it works fine, Since my users want fax fonctionnality and customers know 1 of the msm as fax number I wanted to try the chan_capi-0.3.5 patch if I patch chan_capi and run make, I get an error message , as you can read below, orginal chan_capi compile works, when patched I get an error, no CID ? Any idea ? anybody

Is fPIC broken on x86_64 in LLVM 2.6? I looked through the release notes but did not see anything mentioned. When I try: ------------------- > 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 ------------------- on an x86 machine it works fine. When I try it on x86_64, the

> 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

Hi, The -Xlinker command line option is currently broken. E.g. llvm-ld -native -lXXX -Xlinker=YYY will call the native linker with the otpions: -XXX -YYY -lXXX The attached patch removes the obviously wrong line. daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm-ld-xlinker.patch Type: text/x-diff Size: 385 bytes Desc: not available URL:

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

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

I had unexpected hangups from my asterix box using the i4l driver. (SIP <-> SIP calls worked execellent, but SIP<->ISDN didn't.) Then I changed the i4l driver in modem.conf with the chan_capi from jungham. (http://www.junghanns.net/asterisk) I followed his instructions in the INSTALL file, and first encountered some errors compiling it. It help by deinstalling several

> Due to the lack of bugpoint examples in the documentation, I have no > idea how to use bugpoint > in this complex case, where vm.o firstly needs to be linked with lots > of other compiled modules > and libraries, then the resulting program needs to be executed with > some parameters! It should be possible. I did something like that for debugging a clang bootstrap. What I did

Hi, This email reports bugs in acinclude.m4, src/library/tcltk/src/Makefile, and share/perl/Rd2contents.pl. It is based on R-patched.tgz from 07/27/2001 (R 1.3.0) and comes from trying to compile R on AIX 4.3. 1) acinclude.m4: A string on line 3096 starts with a single quote: ' but is terminated with a double quote: ". (This leads to the weird error message that configure can't

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:

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

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\"

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

Thanks All In fact, to answer Pete, I was trying to do as much as possible like valgrind including as much as possible, which includes all tools. M very elated to know about ASan, given the fact that LLVM is Compile time whereas valgrind is Dynamic, need to rethink, Can you guys check this. build clang 3.2 but I got this linker error. Let me also examine closely clang++ -W -Wall

Hey guys! I'm still having problems trying to get Asterisk compiled but when compiling res_crypto.c, I get this error: NSSL_NO_KRB5 -fPIC -c -o res_parking.o res_parking.c gcc -shared -Xlinker -x -o res_parking.so res_parking.o gcc -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g -Iinclude -I../include -D_REENTRANT -D_GNU_SOURCE -O6 -march=i686

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

hello can u tell me what is the problem in my asterisk or linux why i am getting this error while make. PTEL_OPTIMIZATIONS -DASTERISK_VERSION=\"CVS-HEAD-05/26/05-20:43:39\" -DASTERISK _VERSION_NUM=999999 -DINSTALL_PREFIX=\"\" -DASTETCDIR=\"/etc/asterisk\" -DASTLIB DIR=\"/usr/lib/asterisk\" -DASTVARLIBDIR=\"/var/lib/asterisk\"

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

Hi, I am trying to compile Asterisk under Yellow Dog 3.0 distributionn. I am getting an error gcc -shared -Xlinker -x -o codec_gsm.so codec_gsm.o -lgsm /usr/bin/ld: cannot find -lgsm May be I need packages that my distribution does not include? What do I need to download to get it compiled? Thanks Serge _________________________________________________________________ The new MSN 8: smart spam