C
Charles Comstock
with
[167 cc1@tom ~/install/ruby]$ ./configure --prefix=$HOME/usr
--enable-install-doc --enable-pthread
I got -
[163 cc1@tom ~/install/ruby]$ make
gcc -g -O2 -I. -I. -I/home/cc1/usr/include -c bignum.c
bignum.c: In function `rb_uint2big':
bignum.c:153: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
make: *** [bignum.o] Error 1
[164 cc1@tom ~/install/ruby]$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--host=i386-redhat-linux
Thread model: posix
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-20)
This appears to be a bug in gcc but anyone have any ideas with this?
The machine has a fair amount of custom hardware and stuff that may be
part of the problem, but anyone else have a problem like this before?
Charles Comstock
[167 cc1@tom ~/install/ruby]$ ./configure --prefix=$HOME/usr
--enable-install-doc --enable-pthread
I got -
[163 cc1@tom ~/install/ruby]$ make
gcc -g -O2 -I. -I. -I/home/cc1/usr/include -c bignum.c
bignum.c: In function `rb_uint2big':
bignum.c:153: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
make: *** [bignum.o] Error 1
[164 cc1@tom ~/install/ruby]$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--host=i386-redhat-linux
Thread model: posix
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-20)
This appears to be a bug in gcc but anyone have any ideas with this?
The machine has a fair amount of custom hardware and stuff that may be
part of the problem, but anyone else have a problem like this before?
Charles Comstock