public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] Dealing with global /usr/bin/libtool use vs CC/CXX etc.
Date: Sun, 10 Jan 2021 14:34:13 +0100	[thread overview]
Message-ID: <ff9f8505a46ea8c375f01c52afb7ebfa34f8345f.camel@gentoo.org> (raw)

Hi,

The vast majority of libtool-based programs use configure script to
generate libtool.  However, a few non-autoconf packages also use libtool
by calling system-installed /usr/bin/libtool.  The problem is that this
libtool hardcodes the values of CC/CXX at its' build time, so unless it
is rebuilt frequently, packages end up using the stale values.
The problem is known since 2005 [1] and hasn't been resolved yet.

I can think of two ways of solving it:

1. We could patch system-installed libtool to respect environment
variables such as CC, CXX, etc.  This will probably require carrying
a (possibly non-trivial) patch forever.  On the bright side, libtool is
not exactly a package seeing frequent releases.  I mean, the current
version is from 2015.

2. We could regenerate libtool and force local instance of libtool
in the packages needing it.  The main advantage of this is that it's
a no-brainer.  I could make a quick eclass that does configure a local
instance and prepends it into PATH.

WDYT?


[1] https://bugs.gentoo.org/88596

-- 
Best regards,
Michał Górny




             reply	other threads:[~2021-01-10 13:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 13:34 Michał Górny [this message]
2021-01-10 13:54 ` [gentoo-dev] [RFC] Dealing with global /usr/bin/libtool use vs CC/CXX etc Fabian Groffen
2021-01-10 14:47   ` Michał Górny
2021-01-10 22:49     ` Joshua Kinard
2021-01-11  8:52 ` Jaco Kroon
2021-01-11 18:36   ` Peter Stuge
2021-01-17 22:55     ` Lars Wendler

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=ff9f8505a46ea8c375f01c52afb7ebfa34f8345f.camel@gentoo.org \
    --to=mgorny@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