[Asterisk-Users] asterisk from cvs head crashes on via samuel 2, kernel 2.6.11-gentoo-r4

[jeff oconnell]

> I think the VIA chip, although a i686 class chip, must be declared as
> a i586 if using GCC.

a fine thought ... but gcc ( ala gentoo ) is already configured for  
i586:

 > gcc -v
Reading specs from /usr/lib/gcc-lib/i586-pc-linux-gnu/3.3.5/specs
Configured with: /var/tmp/portage/gcc-3.3.5-r1/work/gcc-3.3.5/configure  
--enable-version-specific-runtime-libs --prefix=/usr  
--bindir=/usr/i586-pc-linux-gnu/gcc-bin/3.3.5  
--includedir=/usr/lib/gcc-lib/i586-pc-linux-gnu/3.3.5/include  
--datadir=/usr/share/gcc-data/i586-pc-linux-gnu/3.3.5  
--mandir=/usr/share/gcc-data/i586-pc-linux-gnu/3.3.5/man  
--infodir=/usr/share/gcc-data/i586-pc-linux-gnu/3.3.5/info  
--with-gxx-include-dir=/usr/lib/gcc-lib/i586-pc-linux-gnu/3.3.5/ 
include/g++-v3 --host=i586-pc-linux-gnu --disable-altivec --enable-nls  
--without-included-gettext --with-system-zlib --disable-checking  
--disable-werror --disable-libunwind-exceptions --disable-multilib  
--disable-libgcj --enable-languages=c,c++ --enable-shared  
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 3.3.5  (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)

if anyone else has cvs-head working on a via, please let me know.
that way i'll know it's something with my build / instal env.

j-

On Apr 13, 2005, at 3:32 PM, Bob Goddard wrote:

> On Wednesday 13 April 2005 19:39, jeff oconnell wrote:
>> i'm running gentoo on a via motherboard ( MII6000, Samuel 2 ):
>>> uname -a
>>
>>     Linux 2.6.11-gentoo-r4 #5 Fri Apr 1 19:26:50 EST 2005 i686 VIA  
>> Samuel 2
>>     CentaurHauls GNU/Linux
>>
>> and asterisk from cvs-head is core dumping:
>>> /opt/asterisk-head/sbin/asterisk -vvvvgc
>>
>>     Illegal instruction (core dumped)
>>
>> asterisk from cvs-v1-0 works fine.
>>
>> just thought i'd throw this out there in case other gentoo / via /  
>> asterisk
>> users are having similiar problems.
>
> I assume this is the bug in GCC where it does not follow the Intel  
> spec.
>