[sr #110525] Typos caught by codespell

Update of sr #110525 (project libtool): Assigned to:None => growpotkin ___ Reply to this item at: ___

[sr #110550] File expected to be at /usr/bin/file, isn't on ChromeOS

Update of sr #110550 (project libtool): Status: Ready For Test => Done Open/Closed:Open => Closed ___ Reply to this item at:

[patch #9996] Patch libtool for macOS 11.0 (aka darwin20)

Update of patch #9996 (project libtool): Status:None => Done Assigned to:None => growpotkin Open/Closed:Open => Closed

[patch #10113] remove hard coded paths to /usr/bin/file

Update of patch #10113 (project libtool): Status:None => Done Assigned to:None => growpotkin Open/Closed:Open => Closed

Re: New libtool maintainer

On Sun, 2021-11-21 at 13:14 -0600, Alex Ameen wrote: > I just took a look at those. Good catches on the typos, I probably would > not have noticed them just reading the script myself. Same thing with > the M4 `[]' quoting issue ( classic pitfall ). I'll get these merged ASAP. > > For the

Re: New libtool maintainer

That would be a huge help. Thanks for the tip, I'm filling out the account request stuff now. :) On 11/21/21 2:04 PM, Russ Allbery wrote: Alex Ameen writes: For the non-Linux patches I can merge them, but I don't have personally have OSX, powerpc, or Solaris boxes, and while I do have a

Re: [patch #9687] bugfix: make -export-dynamic imply --whole-archive

On Sun, 21 Nov 2021, Alex Ameen wrote: Overall I think we're on the same page. I understand that `libtool' is ultimately intended to provide cross-platform consistency as a portability wrapper around each platform's various compilers, linkers, and loaders. It is certainly not my intention to

Re: New libtool maintainer

Alex Ameen writes: > For the non-Linux patches I can merge them, but I don't have personally > have OSX, powerpc, or Solaris boxes, and while I do have a Windows > partition I don't currently have it set up to run these kinds of > tests. Nonetheless I can merge these - if you have access to any

Re: New libtool maintainer

I just took a look at those. Good catches on the typos, I probably would not have noticed them just reading the script myself. Same thing with the M4 `[]' quoting issue ( classic pitfall ). I'll get these merged ASAP. For the non-Linux patches I can merge them, but I don't have personally

Re: [patch #9687] bugfix: make -export-dynamic imply --whole-archive

Howdy Bob, I totally agree with you. `libtool' definitely should not be creating solutions that only work with a particular linker in mind, and at a high level I think it should ultimately work to provide a sense of consistency across a variety of linkers. In this case my concern is about

Re: [patch #9687] bugfix: make -export-dynamic imply --whole-archive

On Sat, 20 Nov 2021, Alex Ameen wrote: Thanks for the follow up, this gave me a much clearer idea of the underlying issue that you're trying to solve. I really do appreciate you taking the time to help improve `libtool'. You're absolutely right that `libtool' completely bungles the use of