Subject: Re: issue building a dynamic library and using it
To: alice <alice@ayaya.dev>, alpine-user <alpine-user@lists.alpinelinux.org>
References: <52090166-eb5d-3a84-c2ab-eced6695e2a6@libero.it>
 <CNOL3JV8X237.3L7DY85Z6IKQ5@sumire>
From: Riccardo Mottola <riccardo.mottola@libero.it>
Message-ID: <6a06b408-ebc5-ac77-5baf-17e2799fb723@libero.it>
Date: Fri, 28 Oct 2022 14:31:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Firefox/68.0 SeaMonkey/2.53.14
MIME-Version: 1.0
In-Reply-To: <CNOL3JV8X237.3L7DY85Z6IKQ5@sumire>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi!


alice wrote:
>> So... I am getting a static library even if I want a shared one, I 
>> suppose. Do I need some special magic? The gnustep build system is a 
>> 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/0dee9266100ff65809c0c4ee7d2e6fcadb6c6b08

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?

Riccardo