Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14951] New: boost compile error when running make silently
Date: Sat, 06 Aug 2022 19:48:20 +0000	[thread overview]
Message-ID: <bug-14951-163@https.bugs.busybox.net/> (raw)

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

             reply	other threads:[~2022-08-06 19:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 19:48 bugzilla [this message]
2022-08-07 12:37 ` [Buildroot] [Bug 14951] boost compile error when running make silently bugzilla

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=bug-14951-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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