Kernel 2.4.18-18 Compile Problems..
Mark Street
jet at sonic.net
Fri Dec 20 22:44:47 PST 2002
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I think I will come to the conclusion that there is something stinky with
RedHat's 2.4.18-18 kernel source package.
On one of my stock Red Hat 7.3 boxes I compiled the 2.4.18-4 kernel and
modules without a problem using their stock config for my platform. Then I
installed the new 2.4.18-18 kernel and proceeded to do the same thing. No
Deal man, it bombed during compilation of the modules.
Go get 2.4.18-19 and give it a go.... ; ) It came out yesterday..... I will
also...
On Friday 20 December 2002 15:30, ME wrote:
> Did this help?
>
> If not, then I'd like to get more information:
> Checking the linux source's root dir called Documentation, there is a file
> "Changes" that has a section on requirements:
>
> o Gnu C 2.95.3 # gcc --version
> o Gnu make 3.77 # make --version
> o binutils 2.9.1.0.25 # ld -v
> o util-linux 2.10o # fdformat --version
> o modutils 2.4.2 # insmod -V
> o e2fsprogs 1.25 # tune2fs
> o reiserfsprogs 3.x.0j # reiserfsck 2>&1|grep
> reiserfsprogs
> o pcmcia-cs 3.1.21 # cardmgr -V
> o PPP 2.4.0 # pppd --version
> o isdn4k-utils 3.1pre1 # isdnctrl 2>&1|grep
> version
>
> Do you have these versions or better?
>
> (granted, isdn utils are not really needed, as are other things you dont
> include support for in your kernel.)
>
> I would also like to see the output of these:
> $ gcc -v
> $ kgcc -v
>
> if none of the above helps, the next time you go to make a kernel and then
> "make modules"
> do the "make modules" on a separate line and instead do this:
> # make modules > /tmp/ME.txt 2>&1 &
> # tail -f /tmp/ME./txt
> (when your kernel modules are finished, you can press control-c to exit
> out of the "tail -f command.)
>
> Then could you send me:
> /tmp/ME.txt and the ".config" located in the root level of the kernel
> source tree. (Send them as attachments.)
>
> When you send them, please, only send them to my e-mail address, as we
> dont need to bomb the list with several thousand lines of messages.
> Also, could you do:
> md5sum on the kernel source package you are using (the rpm file)
> and report the output of the rpm?
>
> I might be able to test compile this to see if it is a system issue or a
> config issue. (saves time.)
>
> Thanks,
> -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
>
> Mark Street said:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > - From the looks of it and the Makefile in drivers/addon/aep. I would
> > comment out
> >
> > CONFIG_CIPE=m
> > and see if the make modules goes...
> >
> > On Thursday 19 December 2002 12:13, Christopher Wagner wrote:
> >> That's a good idea.. <Trying>
> >>
> >> Ok... Had to tweak a litle to get it to compile the bzImage, but no
> >> probs there.
> >>
> >> My make modules returned a similar error:
> >
> > - --
> > Mark Street, D.C.
> > Red Hat Certified Engineer
> > Cert# 807302251406074
> > - --
> > Key fingerprint = 3949 39E4 6317 7C3C 023E 2B1F 6FB3 06E7 D109 56C0 GPG
> > key http://www.streetchiro.com/pubkey.asc
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.0.7 (GNU/Linux)
> >
> > iD8DBQE+Ai5Ab7MG59EJVsARAnN3AKCl1GRfpywhUg+AZqtPwXiZuw5YkQCfV6gl
> > IuHQY/BFH1GZthOtHh3KXb0=Vz3m
> > -----END PGP SIGNATURE-----
- --
Mark Street, D.C.
Red Hat Certified Engineer
Cert# 807302251406074
- --
Key fingerprint = 3949 39E4 6317 7C3C 023E 2B1F 6FB3 06E7 D109 56C0
GPG key http://www.streetchiro.com/pubkey.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+BA3kb7MG59EJVsARAm0RAJ9K5N7vkkASqRLIJgrlVAZXK+wQfQCfSKRA
ry/giDOdaGK9PNTrysxWgVw=
=ps1Q
-----END PGP SIGNATURE-----
More information about the talk
mailing list