From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 84F4AC001DE for ; Fri, 11 Aug 2023 00:54:32 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id CBB9841D8F; Fri, 11 Aug 2023 00:54:31 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org CBB9841D8F X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KGFH5depz2e; Fri, 11 Aug 2023 00:54:30 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp4.osuosl.org (Postfix) with ESMTP id AAB4741D9D; Fri, 11 Aug 2023 00:54:29 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org AAB4741D9D Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by ash.osuosl.org (Postfix) with ESMTP id E001F1BF98E for ; Fri, 11 Aug 2023 00:54:27 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id B9BA160A74 for ; Fri, 11 Aug 2023 00:54:27 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org B9BA160A74 X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mFUfXGOELyrj for ; Fri, 11 Aug 2023 00:54:27 +0000 (UTC) Received: from busybox.osuosl.org (busybox.osuosl.org [140.211.167.122]) by smtp3.osuosl.org (Postfix) with ESMTP id E4F4F60A63 for ; Fri, 11 Aug 2023 00:54:26 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org E4F4F60A63 Received: by busybox.osuosl.org (Postfix, from userid 81) id D06FD84944; Fri, 11 Aug 2023 00:54:26 +0000 (UTC) From: bugzilla@busybox.net To: buildroot@uclibc.org Date: Fri, 11 Aug 2023 00:54:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: buildroot X-Bugzilla-Component: Other X-Bugzilla-Version: 2023.02 X-Bugzilla-Keywords: X-Bugzilla-Severity: trivial X-Bugzilla-Who: jimgeorge@gmail.com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P5 X-Bugzilla-Assigned-To: unassigned@buildroot.uclibc.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: X-Bugzilla-URL: https://bugs.busybox.net/ Auto-Submitted: auto-generated MIME-Version: 1.0 Subject: [Buildroot] [Bug 15718] New: Cross-compiler called through toolchain-wrapper generates bogus error messages X-BeenThere: buildroot@buildroot.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion and development of buildroot List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: buildroot-bounces@buildroot.org Sender: "buildroot" https://bugs.busybox.net/show_bug.cgi?id=15718 Bug ID: 15718 Summary: Cross-compiler called through toolchain-wrapper generates bogus error messages Product: buildroot Version: 2023.02 Hardware: All OS: Linux Status: NEW Severity: trivial Priority: P5 Component: Other Assignee: unassigned@buildroot.uclibc.org Reporter: jimgeorge@gmail.com CC: buildroot@uclibc.org Target Milestone: --- Cause: Invoking the cross-compiler from the package generated by 'make sdk' with no arguments Expected behavior: Should print arm-linux-cc: fatal error: No input files Observed behavior: Output is: /path/to/buildroot/output/host/lib/gcc/arm-buildroot-linux-gnueabihf/11.3.0/../../../../arm-buildroot-linux-gnueabihf/bin/ld: /path/to/buildroot/output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/Scrt1.o: in function `_start': (.text+0x40): undefined reference to `main' collect2: error: ld returned 1 exit status With BR2_DEBUG_WRAPPER set to 2, I get the following extra information: Toolchain wrapper was called with: 'buildroot-ts/buildroot/output/host/bin/arm-linux-cc' Toolchain wrapper executing: '/path/to/buildroot/output/host/bin/arm-linux-cc.br_real' '--sysroot' '/path/to/buildroot/output/host/arm-buildroot-linux-gnueabihf/sysroot' '-fstack-protector-strong' '-fPIE' '-pie' '-Wl,-z,now' '-Wl,-z,relro' When invoking arm-linux-cc with an example program to compile, behavior is normal. It seems like the 'Wl' options are what trigger the errors from the underlying gcc. Adding this as a 'trivial' bug so that it could either be documented or calling toolchain-wrapper with no arguments is special-cased so other buildroot newbies aren't tripped up by this. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot