From: Michael Nosthoff <buildroot@heine.tech>
To: buildroot@busybox.net
Subject: [Buildroot] package/boost: Optimization is always -O3
Date: Wed, 05 Aug 2020 14:29:49 +0200 [thread overview]
Message-ID: <58-5f2aa600-1-33499300@111825754> (raw)
In-Reply-To: <20200804233128.459253b8@windsurf.home>
Hi Thomas ,
On Tuesday, August 04, 2020 23:31 CEST, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> >
> > So this wouldn't be mappable cleanly to all optimization levels Buildroot knows.
> > I didn't find a senseable way to set the -O level manually so it is not overwritten by boost,
> > but maybe somebody has an idea...
>
> What about simply doing a $(SED) replacement on that gcc.jam file
> before the build, so that whatever optimization level Buildroot uses is
> the one that Boost will use ?
>
> Yes, it's not the nicest solution, but the Jam stuff is also difficult
> to work with, so it could be a reasonable trade-off.
At first I felt a bit dirty modifying the .jam file but then I found this mail from the
boost developers who suggest [0] basically that (with a copy of the gcc.jam).
But even more luckily someone in a reply figured out how to overwrite those
values using the user-config.jam file [1]. So I have taken this approach.
I'll submit a patch shortly. Let's see what you think.
Regards,
Michael
[0] https://lists.boost.org/boost-build/2007/07/16838.php
[1] https://lists.boost.org/boost-build/2007/07/16955.php
next prev parent reply other threads:[~2020-08-05 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 13:47 [Buildroot] package/boost: Optimization is always -O3 Michael Nosthoff
2020-08-04 21:31 ` Thomas Petazzoni
2020-08-05 12:29 ` Michael Nosthoff [this message]
2020-08-05 12:42 ` Thomas Petazzoni
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=58-5f2aa600-1-33499300@111825754 \
--to=buildroot@heine.tech \
--cc=buildroot@busybox.net \
/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