> Marco van de Voort wrote: > >>Is there a way to strictly define the paths where FPC looks for objects > >>and libraries? > >> > >>AFAIK -Fl can only add a new value, not override the old one. I'm trying > >>to compile with solaris target on a linux machine, so I need to tell FPC > >>to use solaris libc.a, crti.o, and crtn.o instead of those from linux. > >>But the produced link.res file always has > >>SEARCH_DIR(/usr/) > >>SEARCH_DIR(/usr/lib/) > >>at the begining. Only when I remove them by hand and provide a proper path > >>for crti.o and crtn.o does the linker produce a good solaris executable. > >>Can it be done in a less nasty way? > > > > > > 1.9+: add parameter -Xd to not add the std paths. > > 1.0.x: No. > > You can tweak compiler/targets/t_sunos.pas: > > Constructor TLinkersunos.Init; > begin > Inherited Init; > LibrarySearchPath.AddPath('/lib;/usr/lib;/usr/X11R6/lib',true); > end; > > around line 200. I guess removing the Library... line should solve your > problem.
Yes, that is what -Xd does. _______________________________________________ fpc-pascal maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-pascal