From: Randy Dunlap <rdunlap@infradead.org>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org
Subject: Re: m68k allmodconfig build errors
Date: Mon, 23 Jul 2018 18:49:49 -0700 [thread overview]
Message-ID: <8991ac62-0239-ddfd-6378-95c4ec2fe42b@infradead.org> (raw)
In-Reply-To: <alpine.LNX.2.21.1807201454590.8@nippy.intranet>
On 07/19/2018 10:17 PM, Finn Thain wrote:
> On Thu, 19 Jul 2018, Randy Dunlap wrote:
>
>> Hi Geert,
>>
>> I am seeing a few errors when cross-building m68k on x86_64, using the
>> toolchain at https://mirrors.edge.kernel.org/pub/tools/crosstool/
>> (thanks, Arnd). (so this is gcc 8.1.0)
>>
>> block/partitions/ldm.o: In function `ldm_partition':
>> ldm.c:(.text+0x1900): undefined reference to `strcmp'
>> ldm.c:(.text+0x1964): undefined reference to `strcmp'
>> drivers/rtc/rtc-proc.o: In function `is_rtc_hctosys':
>> rtc-proc.c:(.text+0x290): undefined reference to `strcmp'
>> drivers/watchdog/watchdog_pretimeout.o: In function `watchdog_register_governor':
>> (.text+0x142): undefined reference to `strcmp'
>>
>>
>> Adding #include <linux/string.h> does not help.
>>
>> Is this a toolchain problem or drivers or something else?
>>
>
> This gcc build was apparently configured like so:
>
> /home/arnd/git/gcc/configure --target=m68k-linux --enable-targets=all
> --prefix=/home/arnd/cross/x86_64/gcc-8.1.0-nolibc/m68k-linux
> --enable-languages=c --without-headers --disable-bootstrap --disable-nls
> --disable-threads --disable-shared --disable-libmudflap --disable-libssp
> --disable-libgomp --disable-decimal-float --disable-libquadmath
> --disable-libatomic --disable-libcc1 --disable-libmpx
> --enable-checking=release
>
> In my own cross toolchain builds strcmp comes from glibc but this
> toolchain has no libc at all.
>
>> help?
>>
>
> Linux will use the strcmp in lib/string.c unless __HAVE_ARCH_STRCMP is
> defined in the arch headers. Grep suggests that m68k, mips, x86, xtensa,
> arc, sh, arm64, s390 all define that macro. But maybe you could just patch
> out that definition for build testing.
Sure, that works. Thanks.
--
~Randy
next prev parent reply other threads:[~2018-07-24 1:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 22:39 m68k allmodconfig build errors Randy Dunlap
2018-07-20 5:17 ` Finn Thain
2018-07-24 1:49 ` Randy Dunlap [this message]
2018-07-20 7:20 ` Andreas Schwab
2018-07-24 1:52 ` Randy Dunlap
2018-07-24 4:49 ` Finn Thain
2018-07-26 19:29 ` Randy Dunlap
2018-07-27 4:44 ` Finn Thain
2018-07-27 8:40 ` Andreas Schwab
2018-07-27 12:51 ` Finn Thain
2018-07-24 17:35 ` Andreas Schwab
2018-09-26 7:44 ` Geert Uytterhoeven
2018-09-26 16:09 ` Andreas Schwab
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=8991ac62-0239-ddfd-6378-95c4ec2fe42b@infradead.org \
--to=rdunlap@infradead.org \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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;
as well as URLs for NNTP newsgroup(s).