public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: kernel update (relative to 2.6.0-test4)
Date: Wed, 27 Aug 2003 16:54:18 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106200379415994@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106192276030286@msgid-missing>

On Wed, Aug 27, 2003 at 09:01:54AM -0700, Luck, Tony wrote:
> Last few lines of the build output (building for Tiger):
> 
>   KSYM    .tmp_kallsyms2.S
>   AS      .tmp_kallsyms2.o
>   LD      vmlinux
>   OBJCOPY arch/ia64/hp/sim/boot/vmlinux.bin
> BFD: arch/ia64/hp/sim/boot/vmlinux.bin: warning: allocated section `.data.nosave' not in segment
>   GZIP    arch/ia64/hp/sim/boot/vmlinux.gz
>   LN      vmlinux.gz
>   Kernel: vmlinux.gz is ready
> 
> Is that .../hp/sim/boot/... path right?  I don't have CONFIG_IA64_HP_SIM
> set in my .config.

Yes, that's right.  David and I had a little discussion about that a
couple of days ago.  It's a harmless change.

> Any clues on what the warning from OBJCOPY really means?
> 
> -Tony
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

      parent reply	other threads:[~2003-08-27 16:54 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
2003-08-27 16:34 ` Luck, Tony
2003-08-27 16:52 ` Luck, Tony
2003-08-27 16:54 ` Matthew Wilcox [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=marc-linux-ia64-106200379415994@msgid-missing \
    --to=willy@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox