From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: Installing kernel 2.6.6 on hp zx6000 (fwd)
Date: Wed, 26 May 2004 14:28:18 +0000 [thread overview]
Message-ID: <20040526142818.GC29458@lucon.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0405251608490.28567@tokyo.cc.gatech.edu>
On Wed, May 26, 2004 at 08:46:19AM -0400, Younggyun Koh wrote:
> > > 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/
> >
> > Can you add "V=1" parameter so we can see the commands?
>
> /opt/gcc-3.3.3/usr/local/bin/ld -static -T
> arch/ia64/kernel/vmlinux.lds.s arch/ia64/kernel/head.o arch/ia64/kernel/init_task.o init/built-in.o
> --start-group usr/built-in.o arch/ia64/kernel/built-in.o arch/ia64/mm/built-in.o
> arch/ia64/ia32/built-in.o arch/ia64/dig/built-in.o kernel/built-in.o mm/built-in.o
> fs/built-in.o ipc/built-in.o security/built-in.o crypto/built-in.o lib/lib.a
> arch/ia64/lib/lib.a lib/built-in.o arch/ia64/lib/built-in.o drivers/built-in.o
> sound/built-in.o arch/ia64/pci/built-in.o arch/ia64/hp/common/built-in.o
> arch/ia64/hp/zx1/built-in.o arch/ia64/hp/sim/built-in.o arch/ia64/sn/built-in.o net/built-in.o
> --end-group -o .tmp_vmlinux1
> /opt/gcc-3.3.3/usr/local/bin/ld: final link failed: File truncated
> make: *** [.tmp_vmlinux1] Error 1
>
Which linker are you using? I suggest get the current one from
http://www.kernel.org/pub/linux/devel/binutils/
It may fix your problem or tell you more about why it fails.
H.J.
next prev parent reply other threads:[~2004-05-26 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 20:09 Installing kernel 2.6.6 on hp zx6000 (fwd) Younggyun Koh
2004-05-25 20:19 ` Matthew Wilcox
2004-05-26 2:15 ` Younggyun Koh
2004-05-26 3:23 ` Grant Grundler
2004-05-26 12:46 ` Younggyun Koh
2004-05-26 14:28 ` H. J. Lu [this message]
2004-05-26 15:08 ` Grant Grundler
2004-05-27 0:44 ` Younggyun Koh
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=20040526142818.GC29458@lucon.org \
--to=hjl@lucon.org \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.