Re: Compiling with gcc -march ix86
Thanks. It worked, but it didn't solve the linking problem. A forum was reporting that compiling with -march set to something newer than i386 would solve the problem. I tried instead to undefine HAVE_GCC_ATOMICS in the autotools scripts and then it linked. I'm reporting for logging purpose, if of any interest. It seems that gcc atomicity is not properly implemented in BSD variants. The autoconf generates this: int foo1; int foo2 = __sync_fetch_and_add(&foo1, 1); It compiles with success, so autoconf flags gcc atomicity as supported. But while linking, I'm getting errors that tells that the function __sync_fetch_and_add is undefined. I don't even find where it is declared, neither in Asterisk sources nor DFBSD includes. SR Le 2011-01-04 11:37, Oliver Fromme a écrit : > Stephane Russell wrote: > > Don't work, unfortunatly. > > > > $ setenv UNAME_M i686 > > $ uname -m > > i386 > > $ echo $UNAME_M > > i686 > > The flags are lower-case. > > sh> UNAME_m=i868 uname -m > i868 > > Best regards >Oliver >
Re: Compiling with gcc -march ix86
Stephane Russell wrote: > Don't work, unfortunatly. > > $ setenv UNAME_M i686 > $ uname -m > i386 > $ echo $UNAME_M > i686 The flags are lower-case. sh> UNAME_m=i868 uname -m i868 Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
Re: Compiling with gcc -march ix86
The main reason is that the hardware drivers has been ported to NetBSD for Asterisk 1.4. 1.6 BSD drivers are still work in progress for what I understand. Maybe I should take a look at the DAHDI port for FreeBSD. It's a replacement for zaptel drivers and seems to be used for Asterisk 1.8 in FreeBSD, as well as for 1.6 and 1.4. I'll see. Bye SR Le 2010-12-26 03:01, Francois Tigeot a écrit : > On Fri, Dec 24, 2010 at 05:34:38PM -0500, Stephane Russell wrote: >> >> I'm actually trying to compile asterisk on DFBSD. It needs to compile >> with the compiler option -march=ix86, with x>3 (gcc spec). But DFBSD >> "uname -m" is returning systematically "i386". Is their a workaround for >> that, that would allow me to compile without hacking the autotools scripts? > > Why don't you try asterisk18 from pkgsrc -head ? > > It builds fine out-of the box on DragonFly/i386. >
Re: Compiling with gcc -march ix86
Don't work, unfortunatly. $ setenv UNAME_M i686 $ uname -m i386 $ echo $UNAME_M i686 $ bootstrap.sh [...] $ configure checking build system type... i386-unknown-dragonfly2.8 checking host system type... i386-unknown-dragonfly2.8 [...] configure: Package configured for: configure: OS type : dragonfly2.8 configure: Host CPU : i386 I'll search for some workaround. Thanks for the help. SR Le 2010-12-25 22:16, Justin C. Sherrill a écrit : > On Fri, December 24, 2010 5:34 pm, Stephane Russell wrote: >> Hi, >> >> I'm actually trying to compile asterisk on DFBSD. It needs to compile >> with the compiler option -march=ix86, with x>3 (gcc spec). But DFBSD >> "uname -m" is returning systematically "i386". Is their a workaround for >> that, that would allow me to compile without hacking the autotools >> scripts? > > You could set the environment variable UNAME_M to whatever you think would > work; I don't know if that would get picked up during the build process, > but it's worth a try. I'm interested in seeing asterisk work. >
Re: Compiling with gcc -march ix86
On Fri, Dec 24, 2010 at 05:34:38PM -0500, Stephane Russell wrote: > > I'm actually trying to compile asterisk on DFBSD. It needs to compile > with the compiler option -march=ix86, with x>3 (gcc spec). But DFBSD > "uname -m" is returning systematically "i386". Is their a workaround for > that, that would allow me to compile without hacking the autotools scripts? Why don't you try asterisk18 from pkgsrc -head ? It builds fine out-of the box on DragonFly/i386. -- Francois Tigeot
Re: Compiling with gcc -march ix86
On Fri, December 24, 2010 5:34 pm, Stephane Russell wrote: > Hi, > > I'm actually trying to compile asterisk on DFBSD. It needs to compile > with the compiler option -march=ix86, with x>3 (gcc spec). But DFBSD > "uname -m" is returning systematically "i386". Is their a workaround for > that, that would allow me to compile without hacking the autotools > scripts? You could set the environment variable UNAME_M to whatever you think would work; I don't know if that would get picked up during the build process, but it's worth a try. I'm interested in seeing asterisk work.
Compiling with gcc -march ix86
Hi, I'm actually trying to compile asterisk on DFBSD. It needs to compile with the compiler option -march=ix86, with x>3 (gcc spec). But DFBSD "uname -m" is returning systematically "i386". Is their a workaround for that, that would allow me to compile without hacking the autotools scripts? Thanks.
