Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp2471703imm; Thu, 19 Jul 2018 22:18:18 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcsUxoLRyE0Se9dncJLnEvI8WU7oWBT4xm7WcFdONgNWxTmf2fIYqxf8u5J6VlxvjajEBkC X-Received: by 2002:a62:df4e:: with SMTP id u75-v6mr665428pfg.195.1532063898195; Thu, 19 Jul 2018 22:18:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532063898; cv=none; d=google.com; s=arc-20160816; b=bzir14JXun95hStIcZ010P1MLxz5iWSMg4XOXNBxQVA41zyIZSV9MjiJNhs8qtCbvd oD16zdajqnnOleUhKp8pz0QZGi2BREZPSQC2ZyydusKBr8EqBi8eYFhEk/UTXBic258A J9y9gBQfRUyCDfHZ/fT9bcQqqK6cG6LkcnTfRyRQupoMRaGECvoHqbKQNoY4hzCI0K/7 CY6kmMoavtCJhT3z5RGzj4JHa6gUksaRMAqLTA8GSnGecC7K0ACcXFwjCPnxGN+koXzc utu23HhTjXqdYDn5fT54PeW6jjCNr9AWn1llgXmtgkFHiwaNC11zxms+Qlm89BqIpkFr jrHA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:message-id :in-reply-to:subject:cc:to:from:date:arc-authentication-results; bh=wdj1ZuCw07AXhgM2Ll08bt/+/2r7t1PJqDz/c8G38Vo=; b=jeBlSTKPOce32r8M1YqMPFiTFVbyy0oRD/BDyxH7u2mj0Jyb7lwSsxvNHP32GoMAE1 PrTx23ETIGN6+tgYV8TkTXbtXMGcTzqcMYvih5UrWuCtd676ZM//FwZ8rPllWySb0rHY Tw5WsiWYiWKn3P1vbs7KMcHz3aTZq3DBWX5QTp4p/iDi0OyF46y7Q3vVzV9CeglgUMwL pD2qHUdh4ZSu0LXIvlFnR2jVBDbp3etE8BROmnuPxf3od4E7mhIEBcsrmFf4kqMfdigt 7dpmbFM5e8/Cw9TA+8fEGAFATYHOrgyDzqGxJEUssj0xQKoXCtfQGvc0wSvxIH2ZwFVB kMwQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 3-v6si1015257pld.36.2018.07.19.22.18.02; Thu, 19 Jul 2018 22:18:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727198AbeGTGDx (ORCPT + 99 others); Fri, 20 Jul 2018 02:03:53 -0400 Received: from kvm5.telegraphics.com.au ([98.124.60.144]:40994 "EHLO kvm5.telegraphics.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726918AbeGTGDx (ORCPT ); Fri, 20 Jul 2018 02:03:53 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by kvm5.telegraphics.com.au (Postfix) with ESMTP id 6B46228E40; Fri, 20 Jul 2018 01:17:25 -0400 (EDT) Date: Fri, 20 Jul 2018 15:17:28 +1000 (AEST) From: Finn Thain To: Randy Dunlap cc: LKML , Geert Uytterhoeven , linux-m68k@lists.linux-m68k.org Subject: Re: m68k allmodconfig build errors In-Reply-To: <28ebe45d-3dbd-2a82-f537-b0725f7a2bcf@infradead.org> Message-ID: References: <28ebe45d-3dbd-2a82-f537-b0725f7a2bcf@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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. -- > thanks, >