Op 06-10-15 om 08:47 schreef Jonas Maebe:
As Sergei mentioned, this is definitely not the right approach. The
difficulty with finding these files automatically is that they're
often in non-standard locations. Normally, fpcmkcfg
(utils/fpcmkcfg/fpcmkcfg.pp, executed to create /etc/fpc.cfg) will ask
GCC for the path to these object files by extracting the path from the
output of "gcc --print-libgcc-file-name". It will then prepend -Fl to
that path and add the result to fpc.cfg
There has been a patch to fix the extraction of the libgcc-path in trunk
very recently. There was a problem with non-English versions of gcc.
(using set language)
Joost.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
