>> freetype-config --libs >> >> and it should return the right command options, but obviously it doesn't. > > It looks like the problem is that it is providing the correct flags to pass > to ld, but we are passing them to gcc.
Why do you say that ? Any evidence ? What I personally immediately noticed in that linker command line is that it has both -Wl,-R/usr/X11R6/lib -L/usr/X11R6/lib *and* -Wl,-R/usr/X11R7/lib -L/usr/X11R7/lib. Wouldn't these refer to different releases of X11 ? Is it wise to link against the two at the same time ? Wouldn't you get conflicting (or just the wrong) libraries linked in ? > The correct thing for us to do would be to invoke ld directly, rather than > via the compiler driver, Why would that be "correct" ? GCC provides a (relatively) platform-independent way to link, and then it interfaces with the local platform linker and drives it for us, so why would we want to replicate that layer ? > but this would complicate GNUstep Make a lot (especially on Windows / Solaris > / anywhere > else that doesn't use GNU ld). Yes, so why would invoking ld directly be "correct" ? It would make porting to different platforms harder. I mean, we could change to use "ld" directly to link, but I can't see any reason why that would help. Thanks _______________________________________________ Discuss-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnustep
