From: Andreas Haumer <andreas@xss.co.at>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.21rc2-ac2
Date: Fri, 16 May 2003 19:23:36 +0200 [thread overview]
Message-ID: <3EC51E98.1070600@xss.co.at> (raw)
In-Reply-To: <200305121756.h4CHu4t20051@devserv.devel.redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
There are still a few glitches remaining (sorry, no patches yet)...
*) "make xconfig" fails
(Again, but on a different place than in plain 2.4.21-rc2...
kernel hackers just don't seem to like "make xconfig"...)
root@install:/usr/src/linux {511} $ make xconfig
rm -f include/asm
( cd include ; ln -sf asm-i386 asm)
make -C scripts kconfig.tk
make[1]: Entering directory `/usr/src/linux-2.4.21-rc2-ac2/scripts'
cat header.tk >> ./kconfig.tk
./tkparse < ../arch/i386/config.in >> kconfig.tk
drivers/ide/Config.in: 69: can't handle dep_bool/dep_mbool/dep_tristate condition
make[1]: *** [kconfig.tk] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.21-rc2-ac2/scripts'
make: *** [xconfig] Error 2
*) Unresolved symbols in xfs.o
root@install:~ {501} $ depmod -ae
depmod: *** Unresolved symbols in /lib/modules/2.4.21-rc2-ac2/kernel/fs/xfs/xfs.o
depmod: find_trylock_page
depmod: path_lookup
- - andreas
- --
Andreas Haumer | mailto:andreas@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE+xR6QxJmyeGcXPhERAtGEAJ4w83NzN/UV8kBJDGdrUnIbPADxoQCgkh5/
9pQCmndk6pIMA6W7H0qSsXc=
=e8mM
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2003-05-16 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 17:56 Linux 2.4.21rc2-ac2 Alan Cox
2003-05-16 17:23 ` Andreas Haumer [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=3EC51E98.1070600@xss.co.at \
--to=andreas@xss.co.at \
--cc=alan@redhat.com \
--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