On 10.03.2015 20:18, Mattias Gaertner wrote:
On Tue, 10 Mar 2015 19:34:59 +0100
Sven Barth <[email protected]> wrote:
[...]
Yes, it fails randomly, because the parameters can not be parsed
correctly (some of the passed arguments are randomly missing). I've now
finally committed my fix in r30160 which also allows the usage of FPC
binaries on OSv (which had originally been the reason I investigated
this... but it seems my procrastination took the better of me ^^)
I get:
/home/mattias/3.1.1/fpc/compiler/ppc1 -Ur -Xs -O2 -n -Fux86_64 -Fusystems
-Fu/home/mattias/3.1.1/fpc/rtl/units/x86_64-linux -Fix86_64 -FE.
-FUx86_64/units/x86_64-linux -Cg -dRELEASE -dFPC_USE_LIBC -dx86_64 -dGDB
-dBROWSERLOG -Fux86 -Sew pp.pas
pp.pas(247,1) Warning: "crtbeginS.o" not found, this will probably cause a
linking failure
pp.pas(247,1) Warning: "crtendS.o" not found, this will probably cause a
linking failure
/usr/bin/ld: warning: ./link.res contains output sections; did you forget -T?
pp.pas(247,1) Fatal: There were 2 errors compiling module, stopping
For me those two are in /usr/lib/gcc/i686-pc-linux-gnu/4.9.2 (for you it
might be different, especially if you compile for x86_64) so you need to
add that path using -Fl...
Regards,
Sven
_______________________________________________
fpc-devel maillist - [email protected]
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
