Vorbis - Mar 2002 - Problem compiling libvorbis-1.0rc3 (fatal signal 11 with envelope.c)

Hi everyone. First, excuse me if this problem was discussed before but 
seems that I can't search the list archive.

The problem is that when I try to compile libvorbis-1.0rc3, it fails 
throwing:

gcc: Internal compiler error: program cc1 got fatal signal 11
make[2]: *** [envelope.lo] Error 1

It happens when trying to compile envelope.c as you can see. Anyway, I'm 
not very experienced with gcc or libvorbis to know what's the problem so 
any help will be great.

I'm using Linux compiled from source code (linuxfromscratch.org), my 
kernel version is 2.4.18, gcc 2.95.3

I don't know if you need any other information right now.

I'd compiled libogg-1.0rc3 without any problem.

Thanks for all and excuse my english but it's not my native language.

Greettings.
Ernesto.

<p><p>--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

> The problem is that when I try to compile libvorbis-1.0rc3, it fails
> throwing:
>
> gcc: Internal compiler error: program cc1 got fatal signal 11
> make[2]: *** [envelope.lo] Error 1
>
I found this from a quick search on google at the following link
http://www.ibiblio.org/oswg/oswg-nightly/oswg/en_GB.ISO_8859-1/books/linux-c
-programming/GCC-HOWTO/x250.html#INDEX.29
>From the page:
"4.2.2. Internal compiler error: cc1 got fatal signal 11
Signal 11 is SIGSEGV, or `segmentation violation'. Usually it means that the
program got its pointers    confused and tried to write to memory it didn't
own. So, it could be a gcc bug.

"gcc is however, a well tested and reliable piece of software, for the most
part. It also uses a large number of complex data structures, and an awful
lot of pointers. In short, it's the pickiest RAM tester commonly available.
If you can't duplicate the bug --- if it doesn't stop in the same place
when
you restart the compilation --- it's almost certainly a problem with your
hardware (CPU, memory, motherboard or cache). Don't claim it as a bug
because your computer passes the power-on checks or runs Windows ok or
whatever; these `tests' are commonly and rightly held to be worthless. And
don't claim it's a bug because a kernel compile always stops during
`make
zImage' --- of course it will! `make zImage' is probably compiling over
200
files; we're looking for a slightly smaller place than that.

"If you can duplicate the bug, and (better) can produce a short program
that
exhibits it, you can submit it as a bug report to the FSF, or to the
linux-gcc mailing list. See the gcc documentation for details of exactly
what information they need."

<p>There are more links out there too, if you search on the error message.
The
recommendations always seemed to be either upgrade gcc or check your
hardware.  (Not very helpful, but at least a place to start)

Later,
Alan

<p><p>--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

Ernesto Domato wrote:
> 
> Hi everyone. First, excuse me if this problem was discussed before but
> seems that I can't search the list archive.
> 
> The problem is that when I try to compile libvorbis-1.0rc3, it fails
> throwing:
> 
> gcc: Internal compiler error: program cc1 got fatal signal 11
> make[2]: *** [envelope.lo] Error 1
You use gcc2.95 with the flag -march=i686.  This will crash gcc.
Your linux distribution adds that flag silently behind your back.
Try adding -march=i586 in the toplevel configure.in.

Good luck,

<p>Segher

<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.