The Linux Kernel Mailing List
 help / color / mirror / Atom feed
* RH7.3 Updates - Compile Issues
@ 2003-01-02  1:09 Randy Broman
  2003-01-02  1:54 ` Alan Cox
  0 siblings, 1 reply; 2+ messages in thread
From: Randy Broman @ 2003-01-02  1:09 UTC (permalink / raw)
  To: linux-kernel, rbroman

I had a working RH7.3 system with a stock 2.4.18-3 kernel. "Working"
included previous ability to compile a variety of software successfully,
although I had never compiled a new kernel.

With the intention of compiling a custom kernel I installed the following
software from Red Hat 7.3 Updates as follows: 

cpp-2.96-113.i386.rpm
gcc-2.96-113.i386.rpm
gcc-c++-2.96-113.i386.rpm
gcc-chill-2.96-113.i386.rpm
gcc-g77-2.96-113.i386.rpm
libstdc++-2.96-113.i386.rpm
libstdc++-devel-2.96-113.i386.rpm
binutils-2.11.93.0.2-11.i386.rpm
glibc-2.2.5-42.i386.rpm
glibc-common-2.2.5-42.i386.rpm
glibc-kernheaders-2.4-7.16.i386.rpm
kernel-source-2.4.18-19.7.x.i386.rpm

Unable to compile kernel, with the error messages below. Carefully went thru
.config file, reran after make clean/mrproper, etc. Make dep looks OK, but ...

#make bzImage
etc, etc, then ....

gcc -D__KERNEL__ -I/usr/src/linux-2.4.18-19.7.x/include -Wall -Wstrict-prototypes 
-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe 
-mpreferred-stack-boundary=2 -march=i686 -malign-functions=4    -nostdinc -I 
/usr/lib/gcc-lib/i386-redhat-linux/2.96/include -DKBUILD_BASENAME=serial  
-DEXPORT_SYMTAB -c serial.c
serial.c: In function `rs_read_proc':
serial.c:3361: Internal error: Segmentation fault.
Please submit a full bug report.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
make[3]: *** [serial.o] Error 2
make[3]: Leaving directory `/usr/src/linux-2.4.18-19.7.x/drivers/char'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.18-19.7.x/drivers/char'
make[1]: *** [_subdir_char] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.18-19.7.x/drivers'
make: *** [_dir_drivers] Error 2


I then did some further testing and found I was unable to compile some
software that previously compiled successfully. Ideas appreciated ..

Pls cc me personally on responses ... thx, Randy



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: RH7.3 Updates - Compile Issues
  2003-01-02  1:09 RH7.3 Updates - Compile Issues Randy Broman
@ 2003-01-02  1:54 ` Alan Cox
  0 siblings, 0 replies; 2+ messages in thread
From: Alan Cox @ 2003-01-02  1:54 UTC (permalink / raw)
  To: Randy Broman; +Cc: Linux Kernel Mailing List

On Thu, 2003-01-02 at 01:09, Randy Broman wrote:
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.18-19.7.x/include -Wall -Wstrict-prototypes 
> -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe 
> -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4    -nostdinc -I 
> /usr/lib/gcc-lib/i386-redhat-linux/2.96/include -DKBUILD_BASENAME=serial  
> -DEXPORT_SYMTAB -c serial.c
> serial.c: In function `rs_read_proc':
> serial.c:3361: Internal error: Segmentation fault.
> Please submit a full bug report.
> See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.

> I then did some further testing and found I was unable to compile some
> software that previously compiled successfully. Ideas appreciated ..

gcc tends to show up hardware problems, however if you could use the old
compiler reliably thats not neccessarily fitting the pattern well. 

rpm --verify will let you check packages installed correctly

In general though
If the error is at the same spot each time - suspect software
If the error is in different spots when you rerun the same make -
suspect hardware

Also check you have swap space so are not running out of RAM


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-01-02  1:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-01-02  1:09 RH7.3 Updates - Compile Issues Randy Broman
2003-01-02  1:54 ` Alan Cox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox