unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 48088@debbugs.gnu.org, libtool@gnu.org
Subject: bug#48088: libtool hardcodes native (cross-)compiler, incorrect when using libtool as cross-compiler
Date: Thu, 29 Apr 2021 19:18:56 +0200	[thread overview]
Message-ID: <0bcb6ff1fc169172a0ad85851948874fd97cafae.camel@telenet.be> (raw)
In-Reply-To: <87o8dxl33x.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 860 bytes --]

Severity: minor

Hi Ludo,

Ludovic Courtès schreef op do 29-04-2021 om 13:52 [+0200]:
> [...]
> The ‘libtool’ script provided by the ‘libtool’ package is usually
> unused.  The modus operandi for Libtool is that packages generate their
> own ‘libtool’ script at configure time, tailored for the given
> configuration options, based on a template installed by ‘libtoolize’
> (itself invoked by ‘autoreconf’).
> 
> Perhaps the ‘libtomsmath’ package is doing something unusual?

Yes, it does not have a configure script, and invokes "libtool" directly from
the makefile.  It seems like ‘we’ will have to patch libtomsmath appropriately.
I might eventually look into the issue, but probably not in the near future.

Let's stop CC'ing libtool@gnu.org; this issue isn't really a bug in libtool.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      reply	other threads:[~2021-04-29 17:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 22:03 bug#48088: libtool hardcodes native (cross-)compiler, incorrect when using libtool as cross-compiler Maxime Devos
2021-04-29 11:52 ` Ludovic Courtès
2021-04-29 17:18   ` Maxime Devos [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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=0bcb6ff1fc169172a0ad85851948874fd97cafae.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=48088@debbugs.gnu.org \
    --cc=libtool@gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).