From: Christian Kujau <evil@g-house.de>
To: Younggyun Koh <young@cc.gatech.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Installing 2.6.6 on hp zx6000
Date: Wed, 26 May 2004 00:59:02 +0200 [thread overview]
Message-ID: <40B3CFB6.1080405@g-house.de> (raw)
In-Reply-To: <Pine.GSO.4.58.0405251451300.28567@tokyo.cc.gatech.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Younggyun Koh schrieb:
| 1. has anyone succeeded with the same condition?
no, as i don't own such a machine.
| 2. nfs-utils currently installed is version 0.3.3. the minimum requirement
| for 2.6.6 is 1.0.5, but i was told from the system management guy that
| installing 1.0.5 might cause serious problems... is it true?
just ask the "system management guy" exactly *what* seems to be the
problem with nfs-utils 1.0.5. i have 1.0.6 running with no problems.
| 3. i got the link error when i build the kernel
|
| bash-2.05$ make CROSS_COMPILE=/opt/gcc-3.3.3/usr/local/bin/
| warning: your linker cannot handle cross-segment segment-relative
| relocations.
| please upgrade to a newer version (it is safe to use this linker,
| but
| the kernel will be bigger than strictly necessary).
well, that's a pretty good error message, don't you think? a quick grep
with this error on your local kernel-sources will show that the message
is from: arch/ia64/scripts/toolchain-flags.
upgrading binutils (and other tools too) to the recommended versions as
shown in Documentation/Changes would be a first step. maybe system
management guy can help with that ;-)
Christian.
- --
BOFH excuse #23:
improperly oriented keyboard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAs8+2+A7rjkF8z0wRArPFAJ4lDlVs6ny7AhZbATYI88N14x0leQCg2Dio
WO9pWDOtK0qNVhPpj05cnyo=
=RcVy
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2004-05-25 23:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 19:00 Installing 2.6.6 on hp zx6000 Younggyun Koh
2004-05-25 22:59 ` Christian Kujau [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=40B3CFB6.1080405@g-house.de \
--to=evil@g-house.de \
--cc=linux-kernel@vger.kernel.org \
--cc=young@cc.gatech.edu \
/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