From: Sam Ravnborg <sam@ravnborg•org>
To: David Miller <davem@davemloft•net>
Cc: sfr@canb•auug.org.au, linux-next@vger•kernel.org
Subject: Re: linux-next: sparc32 build failure
Date: Wed, 11 Jun 2008 12:23:34 +0200 [thread overview]
Message-ID: <20080611102334.GA32748@uranus.ravnborg.org> (raw)
In-Reply-To: <20080611.023630.176176702.davem@davemloft.net>
On Wed, Jun 11, 2008 at 02:36:30AM -0700, David Miller wrote:
> From: Stephen Rothwell <sfr@canb•auug.org.au>
> Date: Wed, 11 Jun 2008 19:32:09 +1000
>
> > Hi Dave, Sam,
> >
> > Today's linux-next build (sparc32 defconfig) failed like this:
> >
> > Building modules, stage 2.
> > /opt/crosstool/gcc-3.4.5-glibc-2.3.6/sparc64-unknown-linux-gnu/bin/sparc64-unknown-linux-gnu-ld: .tmp_kallsyms2.o: No such file: No such file or directory
> > make[2]: *** [arch/sparc/boot/image] Error 1
> >
> > I am guessing some kbuild change that sparc32 doesn't like.
>
> Yes, it seems arch/sparc/Makefile needs some updates to match those
> recent Kbuild changes which eliminate the second kallsyms pass.
Killing the following lines should do the trick:
ifdef CONFIG_KALLSYMS
kallsyms.o := .tmp_kallsyms2.o
endif
They were added in 2003. See:
http://git.kernel.org/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git;a=commit;h=aa13a1c61f9a5edca32b06dba4da4ebe9fb5f766
I am not sure why and the changelog is of no help.
To me it looks like a trick to force the second pass when ever KALLSYMS is enabled.
And I do not think this is needed anymore.
Sam
prev parent reply other threads:[~2008-06-11 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 9:32 linux-next: sparc32 build failure Stephen Rothwell
2008-06-11 9:36 ` David Miller
2008-06-11 10:23 ` Sam Ravnborg [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=20080611102334.GA32748@uranus.ravnborg.org \
--to=sam@ravnborg$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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