On 27/11/2019 21:27, Ryan Joseph via fpc-pascal wrote:
>> On Nov 27, 2019, at 2:22 PM, Jonas Maebe wrote:
>>
>> There is no tool that can show this, because a static library is just a
>> collection of random object files. It does not contain any metadata
>> about where these symbols are supposed t
> On Nov 27, 2019, at 2:22 PM, Jonas Maebe wrote:
>
> There is no tool that can show this, because a static library is just a
> collection of random object files. It does not contain any metadata
> about where these symbols are supposed to come from (and they could o,
> fact come from anywhere,
On 27/11/2019 17:59, Ryan Joseph via fpc-pascal wrote:
> how can I do this for static libraries on Linux?
There is no tool that can show this, because a static library is just a
collection of random object files. It does not contain any metadata
about where these symbols are supposed to come from
Hi,
On Wed, 27 Nov 2019, Ryan Joseph via fpc-pascal wrote:
> > On Nov 27, 2019, at 11:25 AM, Karoly Balogh (Charlie/SGR)
> > wrote:
> >
> > Yes. By Default, FPC doesn't link against libc on Linux by default, only
> > when some more advanced things, say, threading is used. To the contrary on
> >
> On Nov 27, 2019, at 11:25 AM, Karoly Balogh (Charlie/SGR)
> wrote:
>
> Yes. By Default, FPC doesn't link against libc on Linux by default, only
> when some more advanced things, say, threading is used. To the contrary on
> Darwin (macOS), we always link against libc. There comes your differe
On Wed, 27 Nov 2019, Ryan Joseph via fpc-pascal wrote:
I'm trying to link to a static library (built from Python sources) in Pascal
and having troubles on Linux. On Mac where I have experience I successfully
link and every works as expected but on Linux I get slews of linker errors in
what
Hi,
On Wed, 27 Nov 2019, Ryan Joseph via fpc-pascal wrote:
> I'm trying to link to a static library (built from Python sources) in
> Pascal and having troubles on Linux. On Mac where I have experience I
> successfully link and every works as expected but on Linux I get slews
> of linker errors in
