From: "Kevin Gordon" <kgordon@paradise.net.nz>
To: <gentoo-dev@cvs.gentoo.org>
Subject: Re: [gentoo-dev] GLIB error
Date: Fri Aug 31 15:24:01 2001 [thread overview]
Message-ID: <000401c13263$6c3135c0$0501010a@kgpro> (raw)
In-Reply-To: 998936649.12892.10.camel@zoidberg
Thank you Mikael for your help.
I think my problems started with installing a new kernel 2.4.6 which would
not boot.
However I tried to install again this morning:
>emerge rsync
>rm -rf /tmp/portage/*
>cd /usr/portage/sys-apps/portage
>emerge portage-1.6.4.ebuild
>vi /etc/make.conf (changed to i686)
>cd /usr/portage/sys-kernel/linux-sources
>emerge linux-sources-2.4.6.ebuild
>cp /usr/portage/sys-kernel/linux-sources/files/2.4.5-r1/config.bootcomp
/usr/src/linux/.config
>cd /usr/src/linux
>make menuconfig (removed "Video for linux" added i686, SMP, Amateur
Radio)
>make dep
>make clean
>make bzImage
>make modules
>make modules_install (error - Unresolved symbols in
/lib/modules/2.4.1-pre8/kernel/drivers/net/pcmcia/.......This did not happen
the first time I tried to compile the kernel)
The first time I continued:
>depmod -a
>mount /dev/sda11/boot
>cp /usr/src/linux/arch/i386/boot/bzImage /boot/boot/bzImage246
>vi /etc/lilo.conf (added bzImage246)
>/sbin/lilo (The new kernel appeared to start but hung)
I am guessing that the GLIB problem is a result of my first try to install
the additional kernel. Comments please?
Regards,
Kevin Gordon
----- Original Message -----
From: "Mikael Hallendal" <hallski@gentoo.org>
To: <gentoo-dev@cvs.gentoo.org>
Sent: Tuesday, August 28, 2001 6:24 AM
Subject: Re: [gentoo-dev] GLIB error
> Den 27 Aug 2001 09:15:57 -0600 skrev Daniel Robbins:
> > On Mon, Aug 27, 2001 at 11:49:13AM +0000, Mikael Hallendal wrote:
> >
> > > /usr/include/linux should be a link to /usr/src/linux/include/linux.
> >
> > Under rc5, this is correct, but under rc6 this is not true anymore.
> > /usr/include/linux and /usr/include/asm contains headers that glibc
> > were compiled with, and stay constant.
>
> Ok, so if this is a rc6-system it seems broken, how should it be fixed?
>
> Regards,
> Mikael Hallendal
>
> --
>
> Mikael Hallendal
> Gentoo Linux Developer, Desktop Team Leader
> CodeFactory AB, Stockholm, Sweden
>
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
>
prev parent reply other threads:[~2001-08-31 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 0:37 [gentoo-dev] GLIB error Kevin Gordon
2001-08-27 3:49 ` Mikael Hallendal
2001-08-27 9:16 ` Daniel Robbins
2001-08-27 10:24 ` Mikael Hallendal
2001-08-28 23:40 ` Daniel Robbins
2001-08-31 15:24 ` Kevin Gordon [this message]
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='000401c13263$6c3135c0$0501010a@kgpro' \
--to=kgordon@paradise.net.nz \
--cc=gentoo-dev@cvs.gentoo.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