From: Goffredo Baroncelli <kreijack@inwind.it>
To: linux-kernel@vger.kernel.org
Cc: bfennema@falcon.csc.calpoly.edu
Subject: [TRIVIAL][PATCH] UDF filesystem: array '__mon_yday' declared as not static
Date: Tue, 31 May 2005 23:52:35 +0200 [thread overview]
Message-ID: <200505312352.35842.kreijack@inwind.it> (raw)
[Please CC' me in the reply because I'am not in the mailing list ]
Hi,
I sent already this mail to the linux_udf@hpesjro.fc.hp.com and to
bfennema@falcon.csc.calpoly.edu, the address reported in MAINTAINER file, but
no response was returned.
in fs/udf/udftime.c the global array '__mon_yday' are defined as not static,
so it conflicts with the glibc one when the kernel are compiled as user mode
linux.
[ghigo@therra 2.6.10]$ make linux ARCH=um
[....]
CC fs/udf/udftime.o
LD fs/udf/udf.o
LD fs/udf/built-in.o
[....]
/usr/lib/libc.a(mktime.o)(.rodata+0x0): multiple definition of
`__mon_yday'
fs/built-in.o(.rodata+0x3540):fs/buffer.c:375: first defined here
collect2: ld returned 1 exit status
KSYM .tmp_kallsyms1.S
nm '.tmp_vmlinux1': No such file
make: *** [.tmp_kallsyms1.S] Error 139
Even tough I don't understand why the error message complains about
fs/buffer.c, I found that the problem is in fs/udf/udftime.c.
The patch below declare the array static. I checked the linux tree and I
didn't find any reference to an array '__mon_yday' from an extern module.
diff -Naur new/fs/udf/udftime.c orig/fs/udf/udftime.c
--- new/fs/udf/udftime.c Sun Feb 20 12:18:06 2005
+++ orig/fs/udf/udftime.c Sun Feb 20 12:18:32 2005
@@ -46,7 +46,7 @@
#endif
/* How many days come before each month (0-12). */
-const unsigned short int __mon_yday[2][13] =
+static const unsigned short int __mon_yday[2][13] =
{
/* Normal years. */
{ 0, 31, 59, 90, 120, 151, 181, 212, 243, 273, 304, 334, 365 },
--
gpg key@ keyserver.linux.it:
Goffredo Baroncelli (ghigo) <kreijack AT inwind DOT it>
Key fingerprint = CE3C 7E01 6782 30A3 5B87 87C0 BB86 505C 6B2A CFF9
reply other threads:[~2005-05-30 21:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200505312352.35842.kreijack@inwind.it \
--to=kreijack@inwind.it \
--cc=bfennema@falcon.csc.calpoly.edu \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®