From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linux/m68k <linux-m68k@vger.kernel.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: m68k: main.c:(.init.text+0x730): undefined reference to `strlen'
Date: Wed, 14 May 2008 10:02:11 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0805140958400.5778@anakin> (raw)
M68k builds with current mainline fail with
init/built-in.o: In function `kernel_init':
main.c:(.init.text+0x730): undefined reference to `strlen'
Reverting commit e662e1cfd434aa234b72fbc781f1d70211cb785b
Author: Cyrill Gorcunov <gorcunov@gmail.com>
Date: Mon May 12 14:02:22 2008 -0700
init: don't lose initcall return values
There is an ability to lose an initcall return value if it happened with irq
disabled or imbalanced preemption (and if we debug initcall).
fixes the problem. My first guess is gcc is turning sizeof() into strlen()
again.
Sample build log available at
http://kisskb.ellerman.id.au/kisskb/buildresult/27596/
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2008-05-14 8:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 8:02 Geert Uytterhoeven [this message]
2008-05-14 8:37 ` Andreas Schwab
2008-05-14 9:57 ` Cyrill Gorcunov
2008-05-14 10:48 ` Cyrill Gorcunov
2008-05-14 14:10 ` Adrian Bunk
2008-05-14 14:28 ` Andreas Schwab
2008-05-14 14:40 ` Cyrill Gorcunov
2008-05-14 14:55 ` Andreas Schwab
2008-05-14 14:58 ` Cyrill Gorcunov
2008-05-14 15:14 ` Cyrill Gorcunov
2008-05-14 15:27 ` Andreas Schwab
2008-05-14 15:31 ` Cyrill Gorcunov
2008-05-14 20:14 ` Geert Uytterhoeven
2008-05-14 14:51 ` Cyrill Gorcunov
2008-05-14 15:30 ` Adrian Bunk
2008-05-14 15:48 ` Cyrill Gorcunov
2008-05-14 15:56 ` Adrian Bunk
2008-05-14 16:03 ` Cyrill Gorcunov
2008-05-14 14:55 ` Roman Zippel
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=Pine.LNX.4.64.0805140958400.5778@anakin \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@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®