From: Andrew Morton <akpm@osdl.org>
To: Judith Lebzelter <judith@osdl.org>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
Greg KH <greg@kroah.com>,
linux-xfs@oss.sgi.com
Subject: Re: 2.6.18-rc6-mm1 'uio_read' redefined, breaks allyesconfig on i386
Date: Mon, 11 Sep 2006 15:53:11 -0700 [thread overview]
Message-ID: <20060911155311.270a8fbb.akpm@osdl.org> (raw)
In-Reply-To: <20060911224520.GJ9335@shell0.pdx.osdl.net>
On Mon, 11 Sep 2006 15:45:20 -0700
Judith Lebzelter <judith@osdl.org> wrote:
> Hello,
>
> I noticed in the 'allyesconfig' build for i386 is not working for 2.6.18-rc6-mm1.
> The function 'uio_read' in gregkh-driver-uio.patch has the same name as a
> function in fs/xfs/support/move.c. Here is the error message:
>
> LD drivers/w1/built-in.o
> LD drivers/built-in.o
> GEN .version
> CHK include/linux/compile.h
> UPD include/linux/compile.h
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> drivers/built-in.o(.text+0x6eb597): In function `uio_read':
> drivers/uio/uio_dev.c:59: multiple definition of `uio_read'
> fs/built-in.o(.text+0x2f4ee8):fs/xfs/support/move.c:26: first defined here
> i686-unknown-linux-gnu-ld: Warning: size of symbol `uio_read' changed from 123 in fs/built-in.o to 397 in drivers/built-in.o
> make: [.tmp_vmlinux1] Error 1 (ignored)
> KSYM .tmp_kallsyms1.S
> i686-unknown-linux-gnu-nm: '.tmp_vmlinux1': No such file
> No valid symbol.
> make: [.tmp_kallsyms1.S] Error 1 (ignored)
>
Thanks. I'd suggest that XFS is being poorly behaved here. "uio_read" isn't
an appropriately named symbol for a filesystem to be exposing.
next parent reply other threads:[~2006-09-12 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060911224520.GJ9335@shell0.pdx.osdl.net>
2006-09-11 22:53 ` Andrew Morton [this message]
2006-09-11 23:28 ` 2.6.18-rc6-mm1 'uio_read' redefined, breaks allyesconfig on i386 Judith Lebzelter
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=20060911155311.270a8fbb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=judith@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=tglx@linutronix.de \
/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