bug#27866: Handle clang's internal libraries when finding compiler's internal libraries

Manoj Gupta <[email protected]> Wed, 21 May 2025 08:47:22 -0700
Newsgroups gmane.comp.gnu.libtool.bugs
Message-ID <CAAMbb04qno8CLMgGyxJv0eaq39P9H35sV0TzNOU0cYcSkURK2w@mail.gmail.com>
--00000000000088cf470635a7484b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks Ileana for applying the patch.

On Wed, May 21, 2025 at 8:00=E2=80=AFAM Ileana Dumitrescu <
[email protected]> wrote:

> Hi Martin,
>
> On 21/05/2025 11:17, Martin Storsj=C3=B6 wrote:
> > Hi Ileana,
> >
> > On Mon, 19 May 2025, Ileana Dumitrescu wrote:
> >
> >> I decided to apply the proposed patches to development [1][2] for now.
> >> If there are any issues, I might revert these commits, but there will
> >> still be the option to use '--enable-cxx-stdlib' during configuration.
> >
> > Thanks for taking care of this! What's the expected process for
> > migrating patches further from development into master; will you revisi=
t
> > them in e.g. 6-12 months and consider including them in master if they
> > haven't caused issues in the development branch since?
>
> Thank you for the fixes! Commits are cherry-picked from development to
> master periodically. There is not a set time frame, but it should not
> be longer than a couple of months for general code changes. I want to
> have time for testing libtool's behaviour and for users to give
> feedback.
>
> --
> Ileana Dumitrescu
>
> GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354
>
>

--00000000000088cf470635a7484b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks=C2=A0Ileana for applying the patch.</div><br><div c=
lass=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_=
attr">On Wed, May 21, 2025 at 8:00=E2=80=AFAM Ileana Dumitrescu &lt;<a href=
=3D"mailto:[email protected]">[email protected]</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Mar=
tin,<br>
<br>
On 21/05/2025 11:17, Martin Storsj=C3=B6 wrote:<br>
&gt; Hi Ileana,<br>
&gt; <br>
&gt; On Mon, 19 May 2025, Ileana Dumitrescu wrote:<br>
&gt; <br>
&gt;&gt; I decided to apply the proposed patches to development [1][2] for =
now.<br>
&gt;&gt; If there are any issues, I might revert these commits, but there w=
ill<br>
&gt;&gt; still be the option to use &#39;--enable-cxx-stdlib&#39; during co=
nfiguration.<br>
&gt; <br>
&gt; Thanks for taking care of this! What&#39;s the expected process for <b=
r>
&gt; migrating patches further from development into master; will you revis=
it <br>
&gt; them in e.g. 6-12 months and consider including them in master if they=
 <br>
&gt; haven&#39;t caused issues in the development branch since?<br>
<br>
Thank you for the fixes! Commits are cherry-picked from development to<br>
master periodically. There is not a set time frame, but it should not<br>
be longer than a couple of months for general code changes. I want to<br>
have time for testing libtool&#39;s behaviour and for users to give<br>
feedback.<br>
<br>
-- <br>
Ileana Dumitrescu<br>
<br>
GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354<br>
<br>
</blockquote></div>

--00000000000088cf470635a7484b--