From: Randy Broman <rbroman@bayarea.net>
To: linux-kernel@vger.kernel.org, rbroman@bayarea.net
Subject: RH7.3 Updates - Compile Issues
Date: Wed, 01 Jan 2003 17:09:24 -0800 [thread overview]
Message-ID: <3E139144.9020806@bayarea.net> (raw)
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
next reply other threads:[~2003-01-02 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 1:09 Randy Broman [this message]
2003-01-02 1:54 ` RH7.3 Updates - Compile Issues Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E139144.9020806@bayarea.net \
--to=rbroman@bayarea.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox