From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
parisc-linux@lists.parisc-linux.org, Helge Deller <deller@gmx.de>
Subject: Re: nfs: __setup_str_nfs_root_setup causes a section type conflict
Date: Mon, 03 Aug 2009 17:07:23 -0400 [thread overview]
Message-ID: <1249333643.18161.36.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <200908032257.51739.elendil@planet.nl>
On Mon, 2009-08-03 at 22:57 +0200, Frans Pop wrote:
> $ make init/do_mounts.o
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> SYMLINK include/asm -> include/asm-parisc
> CALL scripts/checksyscalls.sh
> CC init/do_mounts.o
>
> while:
>
> $ make fs/nfs/nfsroot.o
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> SYMLINK include/asm -> include/asm-parisc
> CALL scripts/checksyscalls.sh
> CC fs/nfs/nfsroot.o
> fs/nfs/nfsroot.c:403: error: __setup_str_nfs_root_setup causes a section type
> conflict
To me that looks like some kind of compiler bug. There appears to be
nothing incorrect about the c code generated by the preprocessor.
Just out of interest, could you do
'make fs/nfs/nfsroot.s'
and send us the resulting file?
Cheers
Trond
next prev parent reply other threads:[~2009-08-03 21:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 12:46 Frans Pop
2009-08-01 22:10 ` Frans Pop
2009-08-03 18:23 ` Trond Myklebust
2009-08-03 19:21 ` Frans Pop
2009-08-03 19:47 ` Trond Myklebust
2009-08-03 20:57 ` Frans Pop
2009-08-03 21:07 ` Trond Myklebust [this message]
2009-08-03 21:34 ` Frans Pop
2009-08-03 21:52 ` Sam Ravnborg
2009-08-03 22:11 ` Trond Myklebust
2009-08-05 19:47 ` Helge Deller
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=1249333643.18161.36.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=deller@gmx.de \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=parisc-linux@lists.parisc-linux.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
all inboxes | Powered by JetHome®