Re: [sr #110849] make check darwin.at test fails on Linux

y're running because it's certainly possible that they should be skipped or that the test suite isn't detecting the build/host system properly. On Tue, Mar 7, 2023, 8:45 AM Alex Ameen wrote: > Thanks for the report > > On Mon, Mar 6, 2023, 5:16 PM open software >

Re: [sr #110849] make check darwin.at test fails on Linux

Thanks for the report On Mon, Mar 6, 2023, 5:16 PM open software wrote: > URL: > > > Summary: make check darwin.at test fails on Linux >Group: GNU Libtool >Submitter: opensoftware >S

Re: LD_LIBRARY_PATH set by wrapper on Ubuntu, not on Rocky (Redhat)

I've run into situations like this on RHEL 6 and 7 with libtool 2.4.6. My approach was manually write a recipe to link a shlib looking in `.libs/' and avoid the wrapper to be used at "build time". The wrapper is made redundant by `RUNPATH' in my opinion when used with `$ORIGIN'; but your mileage m

Re: lt_dlforeach replacement?

M4sugar provides an `m4_foreach` I believe. Im writing from my phone and can't reference the code, so forgive me if the real name is something like `m4s_foreach` but it's provided by `autoconf` under `lib/foreach.m4`. On Thu, Jul 21, 2022, 8:02 PM Zopolis0 wrote: > I'm trying to revive a project

[sr #110542] Patch to libtool for solaris 11.4 link-editor which rejects -pthread option

Update of sr #110542 (project libtool): Status:None => Done Assigned to:None => growpotkin Open/Closed:Open => Closed _

Re: Use of -fsanitize=address still leads to unresolved symbols on gcc

Thanks for reporting this. I haven't recreated the issue yet; but for the purposes of this message I'll assume that this is an issue that isn't caused by quirks in your environment. Let me check my understanding, but I think I understand the issue. Conventionally `-fsanitize=address' "just wor

Libtool Roadmap

teams to improve integration with the rest of the family, and make `libtool' more extensible, but those are conversations for another day.        ━    

Re: Submission process for libtool?

Hey thanks for the kind words y'all. Honestly credit mostly goes to the folks who checked in unreleased changes and submitted patches over the last few years; but I'm glad to have given it the last push. I absolutely encourage package maintainers out there to reach out with any patches that they

Re: .gitmodules security

Thanks for bringing this up. This point is actually relevant for a change I was considering this week. As you pointed out, `libtool' "really" doesn't need to be synced with the most up to date `gnulib', since really these are all "developer dependencies". The only parts of this which are a bit

Re: new release?

Thanks for all of the advice y'all. I'm going to get this release together as soon as possible and resolve issues from there. I agree that paralysis set in a bit as a result of me trying to test a bit overboard on my own ( lots of VMs ). I appreciate the reality check :) On Mon, Feb 7, 2022, 4:5

Re: .gitmodules security

Hey, I can't claim to be an expert about this category of vulnerability; but I appreciate you raising this concern. So is your recommendation to use https://git.savannah.gnu.org/git/gnulib.git instead of git://git.sv.gnu.org/gnulib.git? On 2/6/22 2:26 PM, Vincent Lefevre wrote: On 2022-02-0

Re: new release?

This is a good question. I plan on making a new release this month. When I first adopted the project I ambitiously thought I'd manage to create a new release after about a month; but the truth is when I started doing a deep dive into the internals there was a lot of history and complexity for

[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:

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

Re: New libtool maintainer

On 11/20/21 2:56 AM, Ozkan Sezer wrote: On 10/27/21, Alex Ameen wrote: Howdy! This is Alex Ameen reporting in from Austin, Texas. I'm a long time GNU and `autotools' user who specializes in ELF linking and loading. I'm writing you today to introduce myself and announce that I was r

New libtool maintainer

Howdy! This is Alex Ameen reporting in from Austin, Texas. I'm a long time GNU and `autotools' user who specializes in ELF linking and loading. I'm writing you today to introduce myself and announce that I was recently approved as the new maintainer of `libtool'! I

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

Update of sr #110550 (project libtool): Status:None => Ready For Test Assigned to:None => growpotkin ___ Reply to this item at:

Re: Libtool Digest, Vol 207, Issue 1

I actually just submitted a PR for this issue that you can probably use. savannah.gnu.org/patch/?10113 Hopefully this helps. On Sun, Oct 17, 2021, 11:03 AM wrote: > Send Libtool mailing list submissions to > libtool@gnu.org > > To subscribe or unsubscribe via the World Wide Web, visit

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

Follow-up Comment #1, sr #110550 (project libtool): I actually just submitted a PR for this issue that you can probably use. savannah.gnu.org/patch/?10113 Hopefully this helps. ___ Reply to this item at: