From: Matthias Maier <tamiko@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] mingw-w64 crossdev prefix?
Date: Wed, 17 May 2017 23:25:40 -0500 [thread overview]
Message-ID: <87shk223ln.fsf@kestrel.kyomu.43-1.org> (raw)
In-Reply-To: <CAOazyz0EhHMoXdzO5Td-12zgb5Uze0sHQ6T5Y-XnonLZuQvUxA@mail.gmail.com> (Alon Bar-Lev's message of "Thu, 18 May 2017 06:53:01 +0300")
On Wed, May 17, 2017, at 22:53 CDT, Alon Bar-Lev <alonbl@gentoo.org> wrote:
> On 18 May 2017 at 06:46, Matthias Maier <tamiko@gentoo.org> wrote:
>> [2] I had to manually disable libsanitizer for gcc-6.3.0. Just set
>> EXTRA_ECONF="--disable-libsanitizer" via env/package.env for the
>> cross-x86_64-w64-mingw32/gcc package.
>
> Hi,
> You should use the USE flags and not apply such workarounds, for example:
> USE="-sanitizer" crossdev ...
Yes, correct. It should read USE="-sanitize" though.
Best,
Matthias
prev parent reply other threads:[~2017-05-18 4:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 22:25 [gentoo-dev] mingw-w64 crossdev prefix? Marty Plummer
2017-05-18 3:46 ` Alon Bar-Lev
2017-05-18 4:08 ` Marty Plummer
2017-05-18 4:42 ` Ian Stakenvicius
2017-05-18 4:52 ` Marty Plummer
2017-05-19 4:46 ` Marty Plummer
2017-05-18 3:46 ` Matthias Maier
2017-05-18 3:53 ` Alon Bar-Lev
2017-05-18 4:25 ` Matthias Maier [this message]
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=87shk223ln.fsf@kestrel.kyomu.43-1.org \
--to=tamiko@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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