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 smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) (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 1465BC19F2D for ; Sat, 6 Aug 2022 19:48:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 3405F405CE; Sat, 6 Aug 2022 19:48:25 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 3405F405CE X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8P-jGJGGO8_j; Sat, 6 Aug 2022 19:48:24 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp2.osuosl.org (Postfix) with ESMTP id 434CF40579; Sat, 6 Aug 2022 19:48:23 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 434CF40579 Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by ash.osuosl.org (Postfix) with ESMTP id 08C151BF352 for ; Sat, 6 Aug 2022 19:48:22 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id E37BC4148B for ; Sat, 6 Aug 2022 19:48:21 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org E37BC4148B 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 rJplBXEOnvoO for ; Sat, 6 Aug 2022 19:48:21 +0000 (UTC) Received: from busybox.osuosl.org (busybox.osuosl.org [140.211.167.122]) by smtp4.osuosl.org (Postfix) with ESMTP id 00449409FA for ; Sat, 6 Aug 2022 19:48:20 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 00449409FA Received: by busybox.osuosl.org (Postfix, from userid 81) id 5F9A883C06; Sat, 6 Aug 2022 19:34:11 +0000 (UTC) From: bugzilla@busybox.net To: buildroot@uclibc.org Date: Sat, 06 Aug 2022 19:48:20 +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: 2022.05.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: trivial X-Bugzilla-Who: bundi78@web.de 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 14951] New: boost compile error when running make silently 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=14951 Bug ID: 14951 Summary: boost compile error when running make silently Product: buildroot Version: 2022.05.1 Hardware: All OS: Linux Status: NEW Severity: trivial Priority: P5 Component: Other Assignee: unassigned@buildroot.uclibc.org Reporter: bundi78@web.de CC: buildroot@uclibc.org Target Milestone: --- Hi, I observed a boost compile error during creation of a linux system. I used make's '--silent' option. According to boost, the '-d' option must be followed by a digit. Therefore, the following lines inside boost.mk: # how verbose should the build be? BOOST_OPTS += $(if $(QUIET),-d,-d+1) HOST_BOOST_OPTS += $(if $(QUIET),-d,-d+1) should be: # how verbose should the build be? BOOST_OPTS += $(if $(QUIET),-d0,-d+1) HOST_BOOST_OPTS += $(if $(QUIET),-d0,-d+1) -- 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