|
From: | Alex Ameen |
Subject: | bug#27866: Handle clang's internal libraries when finding compiler's internal libraries |
Date: | Sun, 15 May 2022 13:33:21 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 |
What I did notice was that this change has a wider effect than the problem statement initially suggests. I'm not crazy about the way it has a conditional behavior for two specific libraries since it is an ad-hoc solution directed at two compiler-collections, as opposed to a general purpose solution; but for the time being I see this as a practical change.
As a side effect this change should also resolve issues with certain flag-specs such as `-fsanitize' which is nice; but the impact of unknown side effects is something I expect will rear its head in the near future. With that in mind, I think this is a necessary change, but I want to express up front that "I'm confident this will break a lot of existing builds, and I consider this to be a first draft".
I would greatly appreciate y'all taking this for a spin on any available projects you have to get a sense of how it will behave "in the field". This change really effects "unspecified behavior" that the test-suite isn't designed to audit, but nonetheless has a practical effect on users.
On 5/6/22 04:59, Shea Levy wrote:
Hi all, Is there any status on this? Thanks, Shea Martin Storsjö <martin@martin.st> writes:Hi Alex, I've understood you're a new maintainer of libtool. Can you have a look at this bug (https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27866)? In the last few posts, there's a couple patches attached. They have been used downstream within e.g. MSYS2 since a couple years:
[Prev in Thread] | Current Thread | [Next in Thread] |