Kernel 2.4.18-18 Compile Problems..
Christopher Wagner
chrisw at pacaids.com
Tue Dec 17 16:57:06 PST 2002
Wonderful!! I've been trying to find anything useful in Bugzilla for almost
an hour. It doesn't seem to like my search terms.
I changed both references to gcc (for HOSTCC and the make variables) and it
successfully passed that section. It had been consistently seg faulting at
that one spot.
NOW, I'm faced with yet another stepping block. :( In the sound drivers
section I'm getting:
---
make[1]: Entering directory `/usr/src/linux-2.4.18-18.7.x'
kallsyms pass 1
ld -m elf_i386 -T /usr/src/linux-2.4.18-18.7.x/arch/i386/vmlinux.lds -e
stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o i
nit/main.o init/version.o init/do_mounts.o --start-group
arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o
ipc/ipc.o drivers/parport/driver.o drivers/char/char.o
drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/m
edia.o drivers/char/agp/agp.o drivers/char/drm/drm.o
drivers/net/appletalk/appletalk.o drivers/ide/idedriver.o
drivers/cdrom/driver.
o drivers/sound/sounddrivers.o drivers/pci/driver.o drivers/pnp/pnp.o
drivers/video/video.o drivers/md/mddev.o net/network.o crypto/
crypto.o abi/abi.o /usr/src/linux-2.4.18-18.7.x/arch/i386/lib/lib.a
/usr/src/linux-2.4.18-18.7.x/lib/lib.a /usr/src/linux-2.4.18-18.
7.x/arch/i386/lib/lib.a --end-group -o .tmp_vmlinux1
drivers/sound/sounddrivers.o: In function `es1371_probe':
drivers/sound/sounddrivers.o(.text+0x6550): undefined reference to
`gameport_register_port'
drivers/sound/sounddrivers.o: In function `es1371_remove':
drivers/sound/sounddrivers.o(.text+0x66ba): undefined reference to
`gameport_unregister_port'
make[1]: *** [kallsyms] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.18-18.7.x'
make: *** [vmlinux] Error 2
---
This is happening every time now.. Any thoughts?
- Christopher Wagner
chrisw at pacaids.com
Packaging Aids Corporation - Information Systems
P.O. Box 9144
San Rafael, CA 94912-9144
http://www.pacaids.com/
(415) 454-4868 x116
-----Original Message-----
From: ME [mailto:dugan at passwall.com]
Sent: Tuesday, December 17, 2002 3:09 PM
To: talk at nblug.org
Subject: Re: Kernel 2.4.18-18 Compile Problems..
(Comments below)
Christopher Wagner said:
> Hey folks. Was hoping someone might be able to figure this one out..
>
> I downloaded the latest and "greatest" kernel source rpm from Redhat..
> I ran the make menuconfig, make dep, and make bzImage..
>
> It starts compiling like normal and then crashes with this error:
> ---
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.18-18.7.x/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-commo n
> -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
> -malign-functions=4 -nostdinc -I /usr/lib/gcc-lib/i386-redh
> at-linux/2.96/include -DKBUILD_BASENAME=floppy -c -o floppy.o floppy.c
> floppy.c: In function `floppy_revalidate':
> floppy.c:3898: Internal error: Segmentation fault.
This is bad. It is likely a problem with the compiler, or something that
came up when the compiler was running.
Suggestions to help[ you to diagnose this:
do a "make clean" on the kernel and then do a "make dep && make bzImage"
See if the same error comes up in the same section.
If you again see a "seg fault" but in a different area, then it is more
likely that you have "hardware issues".
If you continue to see this error in the same place, there is likely an
issue with your compiler.
Also, if using RedHat (I think it was with version 7.x) they shipped it
with a version of gcc that would not "work well" with compiling kernels.
I dont recall a "Seg fault" as being a symptom of the issue, but hey, who
knows? If you wish to try the "RedHat" work around, they include "kgcc"
instead of "gcc" so that kernels can be compiled.
To use this, after you "make clean", I *think* you need to edit and modify
the "Makefile" located in the root of the kernel source tree, and within
that file locte the entry :
HOSTCC = gcc
and change it to:
HOSTCC = kgcc
Only try this if you are running RedHat and notice that the first test,
shows the problem (seg fault) occurs at the *same* spot each time you try
to build your kernel.
(Background: A seg fault can occur under many circumstances, but the end
result is almosty always as a result of a program trying to use memory
that it was not allocated to use. The causes that lead up to this event
are many. Not all seg faults are as a result of bad hardware, or hardware
probelsm, but when you notice them while *compiling* something that is as
tested as a stable kernel, hardware issues are high on the list.)
(more)
> Please submit a full bug report.
> See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
> make[3]: *** [floppy.o] Error 2
> make[3]: Leaving directory `/usr/src/linux-2.4.18-18.7.x/drivers/block'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.4.18-18.7.x/drivers/block'
> make[1]: *** [_subdir_block] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.18-18.7.x/drivers'
> make: *** [_dir_drivers] Error 2
> ---
> Anyone else seen this error? Should I go digging in floppy.c under the
> floppy_revalidate function to see what it's trying to call? Or is this
> a symptom of a larger problem?
I would not expect this to be an issue in floppy.c. (See above) I see this
as part of a lerger problem.
> Should I reinstall GCC?
You can do this if you want, and also do a check:
# which kgcc
If you have kgcc, consider using it in your Makefile and
then
make dep && make bzImage
again as stated above.
Results and feedback welcome. :-)
-ME
--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS/CM$/IT$/LS$/S/O$ !d--( ) !s !a (-----) C $( ) U $( $) P $>
L $( ) E W $( ) N o K w $> > O-@ M $ V-$>- !PS !PE Y PGP
t at -( ) 5 @ X@ R- tv- b DI D G--@ e > > h( )> r*>? z?
------END GEEK CODE BLOCK------
decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html
Campus IT(/OS Security): Operating Systems Support Specialist Assistant
SPAM: ---- Start SpamAssassin results
SPAM: -4.4 hits, 5 required;
SPAM: * -4.4 -- 'In-Reply-To' line found
SPAM:
SPAM: ---- End of SpamAssassin results
More information about the talk
mailing list