Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Fri, 28 Oct 2022 17:42:35 +0200
Message-Id: <CNXO64HT29X6.2MNW0TI2SRW11@sumire>
From: "alice" <alice@ayaya.dev>
To: "Riccardo Mottola" <riccardo.mottola@libero.it>, "alpine-user"
 <alpine-user@lists.alpinelinux.org>
Subject: Re: issue building a dynamic library and using it
References: <52090166-eb5d-3a84-c2ab-eced6695e2a6@libero.it>
 <CNOL3JV8X237.3L7DY85Z6IKQ5@sumire>
 <6a06b408-ebc5-ac77-5baf-17e2799fb723@libero.it>
In-Reply-To: <6a06b408-ebc5-ac77-5baf-17e2799fb723@libero.it>

On Fri Oct 28, 2022 at 2:31 PM CEST, Riccardo Mottola wrote:
> Hi!
>
>
> alice wrote:
> >> So... I am getting a static library even if I want a shared one, I=20
> >> suppose. Do I need some special magic? The gnustep build system is a=
=20
> >> little bit complicated, but supports linux & bsd well.
> > this entirely sounds like the gnustep build system doing something
> > wrong, so you have to figure out what that is. maybe it's just a
> > configure argument (--enable-shared --disable-static , etc)
>
> Shared is default for the gnustep make system.
> I still have an older laptop with Alpine Linux still running 3.15 and
> which I didn't use for a year and which had GNUstep running. Proof it
> worked! First thing, I updated GNUstep and it fails on 3.15 as on 3.16,
> so I'd exclude logically that it is the new release of Alpine, but
> something changed on GNUstep.
>
> As a proof, then I tried bisecting and was able to proove that the issue
> is in the GNUstep make system, a requisite of the later libraries which
> use it.
>
> The breaking commit is this:
>
> https://github.com/gnustep/tools-make/commit/0dee9266100ff65809c0c4ee7d2e=
6fcadb6c6b08
>
> which corresponds to an update of the configure system. I see nothing
> wrong. Do you see something? Are you aware of issues with 2.71 autoconf?
no, if anything 2.71 fixes a bunch of things.
>
> Riccardo