Am 30.06.2011 23:03, schrieb Mark Morgan Lloyd:
Felipe Monteiro de Carvalho wrote:
On Thu, Jun 30, 2011 at 7:05 PM, Mark Morgan Lloyd
<markmll.fpc-de...@telemetry.co.uk> wrote:
I think his is a loader issue- the binary needs to know what .so to
pull in
that later allows it to work out paths etc.
ops, it seams that you are right =O
I only spotted it when I started wondering whether 'which' was going to
be any use in a cross-development environment such as I think one has to
start with in this case.
I presume the answer to the original question is "use the one on the
system you're working on". In other words, if building a cross compiler
to run on i386 assume /lib/ld-linux.so.2; the {$ifdef mips} will only
come into play when building to run natively.
You are wrong. The define "mips" is set when you are compiling a FPC
that supports "mips" no matter what platform you run on. The CPU defines
that are defined when crosscompiling are prefixed with "CPU". So the
define for checking whether you are running on MIPS is "CPUMIPS".
My personal assumption regarding the linker: it might be ok to use the
normal Linux ones.
Regards,
Sven
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
