From: Chris Johns <chris@contemporary.net.au>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Building gcc 12 cross-compiler with --enable-lto on FreeBSD fails
Date: Wed, 15 Jun 2022 20:40:14 +1000 [thread overview]
Message-ID: <841b9a27-e591-675b-68ad-6f0774587464@contemporary.net.au> (raw)
In-Reply-To: <CAFiYyc22b67+3GeJFQmjqdHBp5jsuDx4TeFK4FDmF+L2M1euZw@mail.gmail.com>
On 15/6/22 7:56 pm, Richard Biener wrote:
> On Wed, Jun 15, 2022 at 11:27 AM Chris Johns <chris@contemporary.net.au> wrote:
>>
>> Hi,
>>
>> I am trying to build a cross-compiler on FreeBSD with --enable-lto because a
>> chip vendor is using it when building controller software that is part of a system.
>>
>> The build I am using symlinks gmp, mpfr etc as source so they are built as part
>> of the gcc build.
>>
>> The mpfr package is reporting ...
>>
>> build/mpfr/config.log:configure:17408: error: Link Time Optimisation is not
>> supported (see config.log for details).
>>
>> Should the enable option be passed to these packages?
>
> You shouldn't need --enable-lto, it's effect (adding lto to the set of compiled
> languages) is already the default. You can use --enable-languages=default,lto
> to achieve the same effect without getting the mpfr side-effect.
Oh that is great and I had no idea this is how it is controlled. I have rebuilt
my compiler and it is now building. Nice.
>> I have assumed the enable option for LTO is for the cross compiler and not the
>> host gcc?
>
> it's for the built GCC, enabling LTO support (but not for enabling
> building GCC itself
> with LTO).
It now makes sense. I will also update the RTEMS tools builds.
Thanks
Chris
prev parent reply other threads:[~2022-06-15 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 9:25 Chris Johns
2022-06-15 9:56 ` Richard Biener
2022-06-15 10:40 ` Chris Johns [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=841b9a27-e591-675b-68ad-6f0774587464@contemporary.net.au \
--to=chris@contemporary.net.au \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).