Hi fpc RTL experts.
My project uses Synapse but features link problems and crashes when I
resolve same.
Tracking this down:
Synapse uses the unit dynlibs
dynlibs uses the unit dl
dl does not have a uses clause, so the problem seems to be here.
When in a dedicated test project I just do
From: Michael Schnell mschn...@lumino.de
Hi fpc RTL experts.
My project uses Synapse but features link problems and crashes when
I resolve same.
Tracking this down:
Synapse uses the unit dynlibs
dynlibs uses the unit dl
dl does not have a uses clause, so the problem seems to be here.
When
Michael Schnell wrote:
Hi fpc RTL experts.
Non-expert here.
My project uses Synapse but features link problems and crashes when I
resolve same.
Tracking this down:
Synapse uses the unit dynlibs
dynlibs uses the unit dl
dl does not have a uses clause, so the problem seems to be here.
In
Hi,
[topic is about a compilation problem specific to qnap ARM/linux based
NASes using the heavily modded stock OS]
On Wed, 2013-01-23 at 09:33 +0100, Michael Schnell wrote:
My project uses Synapse but features link problems and crashes when I
resolve same.
Tracking this down:
Synapse
Hi,
On Wed, 2013-01-23 at 10:20 +0100, Thomas Schatzl wrote:
Hi,
[topic is about a compilation problem specific to qnap ARM/linux based
NASes using the heavily modded stock OS]
On Wed, 2013-01-23 at 09:33 +0100, Michael Schnell wrote:
This can be resolved by
{$I crti.o}
and
On Wed, Jan 23, 2013 at 10:20:50AM +0100, Thomas Schatzl wrote:
Compile with:
ppcarm -Fl/opt/arm-none-linux-gnueabi/lib test.pas
I had to do something similar when ubuntu moved to multiarch for arm,
but the path was later added in the compiler.
Henry
On 01/23/2013 10:00 AM, Yury Sidorov wrote:
It seems you have libdl statically linked to your executable.
Is this what
{$linklib c}
does ?
I just copied it from dl.pp in the svn.
That's why you have such linker errors. Probably the linker is unable
to find libdl.so but finds only libdl.a
I
In our previous episode, Mark Morgan Lloyd said:
Non-expert here.
My project uses Synapse but features link problems and crashes when I
resolve same.
Tracking this down:
Synapse uses the unit dynlibs
dynlibs uses the unit dl
dl does not have a uses clause, so the problem
Am 23.01.2013 10:50, schrieb Michael Schnell:
That's why you have such linker errors. Probably the linker is unable
to find libdl.so but finds only libdl.a
I can't believe that the linker should automatically search for
potentially usable dynamic libraries: in fact it does not know on
which
On 01/23/2013 10:20 AM, Thomas Schatzl wrote:
[topic is about a compilation problem specific to qnap ARM/linux based
NASes using the heavily modded stock OS]
Yep, but I don't see how this is related to the problem.
I understand the program crashes before it tries to do system depending
Michael Schnell wrote:
I don't see why the problem should be related to the target (other than
in fact the crti provided is buggy which I esteem rather unlikely).
Except for the possible case where the OS and standard libraries have
been built to not support dynamic linkage.
--
Mark Morgan
On 01/23/2013 11:12 AM, Sven Barth wrote:
That's normal on ELF based systems: all libraries need to be known at
link time (at least as long as you don't load them dynamically at
runtime).
I see. But automatically using a library statically when the dynamic
version is not found does not seem
On 01/23/2013 10:34 AM, Thomas Schatzl wrote:
That may be different in your ipkg installation - your firmware is
likely different/newer. Still, there should be no need to directly link
to crti.o.
That is what I hope, as in fact the project never access any CRT related
stuff. The binding of CRT
On 01/23/2013 11:36 AM, Mark Morgan Lloyd wrote:
Except for the possible case where the OS and standard libraries have
been built to not support dynamic linkage.
I seem to remember that there are lots of .so used in this system (I'll
recheck)
Moreover I suppose it then should crash not
Hi,
On Wed, 2013-01-23 at 11:23 +0100, Michael Schnell wrote:
On 01/23/2013 10:20 AM, Thomas Schatzl wrote:
[topic is about a compilation problem specific to qnap ARM/linux
based NASes using the heavily modded stock OS]
Yep, but I don't see how this is related to the problem.
People are
Hi,
I messed up with replying to Michael privately only first, then only
noticing that I hit the wrong reply button.
@Michael: Please try to avoid CC'ing additional people from the list in
addition to the list for list-specific discussions. The additional
cc'ing achieves nothing but people
Am 23.01.2013 12:55, schrieb Michael Schnell:
On 01/23/2013 10:34 AM, Thomas Schatzl wrote:
That may be different in your ipkg installation - your firmware is
likely different/newer. Still, there should be no need to directly link
to crti.o.
That is what I hope, as in fact the project never
17 matches
Mail list logo
