From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: kernel update (relative to 2.6.0-test4)
Date: Wed, 27 Aug 2003 16:22:32 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106200160512868@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106192276030286@msgid-missing>
>>>>> On Wed, 27 Aug 2003 09:01:54 -0700, "Luck, Tony" <tony.luck@intel.com> said:
>> The latest ia64 patch is now available at
>> ftp://www.kernel.org/pub/linux/kernel/ports/ia64/v2.5/ in
>> file:
>>
>> linux-2.6.0-test4-ia64-030826.diff.gz
>>
Tony> Last few lines of the build output (building for Tiger):
Tony> KSYM .tmp_kallsyms2.S
Tony> AS .tmp_kallsyms2.o
Tony> LD vmlinux
Tony> OBJCOPY arch/ia64/hp/sim/boot/vmlinux.bin
Tony> BFD: arch/ia64/hp/sim/boot/vmlinux.bin: warning: allocated section `.data.nosave' not in segment
Tony> GZIP arch/ia64/hp/sim/boot/vmlinux.gz
Tony> LN vmlinux.gz
Tony> Kernel: vmlinux.gz is ready
Tony> Is that .../hp/sim/boot/... path right?
Not really, but it doesn't hurt, AFAIK (I'll try to remember to clean
it up, though).
Tony> Any clues on what the warning from OBJCOPY really means?
Nope. I don't get that (building for zx1):
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
Building modules, stage 2.
OBJCOPY arch/ia64/hp/sim/boot/vmlinux.bin
GZIP arch/ia64/hp/sim/boot/vmlinux.gz
MODPOST
LN vmlinux.gz
Kernel: vmlinux.gz is ready
--david
next prev parent reply other threads:[~2003-08-27 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 18:29 kernel update (relative to 2.6.0-test4) David Mosberger
2003-08-26 21:16 ` Alex Williamson
2003-08-27 16:01 ` Luck, Tony
2003-08-27 16:22 ` David Mosberger [this message]
2003-08-27 16:34 ` Luck, Tony
2003-08-27 16:52 ` Luck, Tony
2003-08-27 16:54 ` Matthew Wilcox
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=marc-linux-ia64-106200160512868@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox