public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lars Wendler <polynomial-c@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Dealing with global /usr/bin/libtool use vs CC/CXX etc.
Date: Sun, 17 Jan 2021 23:55:02 +0100	[thread overview]
Message-ID: <20210117235502.19554e24@abudhabi.paradoxon.rec> (raw)
In-Reply-To: <20210111183631.24700.qmail@stuge.se>

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

On Mon, 11 Jan 2021 18:36:31 +0000 Peter Stuge wrote:

>Jaco Kroon wrote:
>> > I can think of two ways of solving it:
>> >
>> > 1. We could patch system-installed libtool to respect environment
>> >
>> > 2. We could regenerate libtool and force local instance of libtool
>> > in the packages needing it.  
>> 
>> 3.  Have it always use some fixed compiler somewhere (ie, compile it
>>  
>
>4. Make gcc-config regenerate libtool, otherwise as 2.
>
>
>//Peter
>

5.) Try to replace GNU libtool with sys-devel/slibtool

slibtool is aimed to be a drop-in replacement although at the current
state it still has a couple of hiccups. I've created a tracker bug at
[1] to track all issues arising from using slibtool instead of GNU
libtool.

Cheers
Lars

[1] https://bugs.gentoo.org/765709
-- 
Lars Wendler
Gentoo package maintainer
GPG: 21CC CF02 4586 0A07 ED93  9F68 498F E765 960E 9B39

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-01-17 22:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10 13:34 [gentoo-dev] [RFC] Dealing with global /usr/bin/libtool use vs CC/CXX etc Michał Górny
2021-01-10 13:54 ` 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 [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=20210117235502.19554e24@abudhabi.paradoxon.rec \
    --to=polynomial-c@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