unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-devel@gnu.org
Subject: Re: [PATCH] Test -flto on both compiler and linker
Date: Mon, 07 Mar 2022 10:48:08 +0100	[thread overview]
Message-ID: <87pmmy2iw7.fsf@gnu.org> (raw)
In-Reply-To: 20220220093959.3130873-1-slyich@gmail.com

Hi Sergei,

Sergei Trofimovich <slyich@gmail.com> skribis:

> Before the change ./configure incorrectly enabled -flto on toolchains
> that support -flto on compiler side but don't support -flto on linker
> side. This caused incorrect type size detection on nixpkgs' Darwin:
>
>  configure:54594: checking size of size_t
>  configure:54600: clang -std=gnu11 -o conftest -g -O2 -flto   conftest.c  >&5
>  ld: warning: ignoring file /private/tmp/nix-build-guile-3.0.8.drv-0/conftest-00e93d.o,
>    building for macOS-x86_64 but attempting to link with file built
>    for unknown-unsupported file format ( 0xDE 0xC0 0x17 0x0B 0x00 0x00 0x00 0x00 0x14 0x00 0x00 0x00 0x80 0x1A 0x00 0x00 )
>  Undefined symbols for architecture x86_64:
>    "_main", referenced from:
>       implicit entry/start for main executable
>  ld: symbol(s) not found for architecture x86_64
>  clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
>
> Taken from https://github.com/NixOS/nixpkgs/pull/160051#issuecomment-1046105041
>
> The change makes sure -flto support tests basic support of just for
> object file generation but for linker as well.
>
> * configure.ac: use AC_LINK_IFELSE instead of AC_COMPILE_IFELSE.

Applied, thanks!

Ludo’.




      reply	other threads:[~2022-03-07  9:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20  9:39 [PATCH] Test -flto on both compiler and linker Sergei Trofimovich
2022-03-07  9:48 ` Ludovic Courtès [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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmmy2iw7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).