#838: Compile error for lib/driver ----------------------+----------------------------------------------------- Reporter: sprice | Owner: [email protected] Type: defect | Status: new Priority: normal | Milestone: 6.4.0 Component: default | Version: svn-releasebranch64 Resolution: | Keywords: Platform: MacOSX | Cpu: OSX/Intel ----------------------+----------------------------------------------------- Comment (by glynn):
Replying to [comment:7 kyngchaos]: > You need to be very detailed with GRASS configure. use both --with-libs and --with-includes. That way compilation will find the right headers and linking will find the right libs. It goes beyond that. There is no (portable) way to tell the compiler/linker to look for a specific header/library in a specific directory. You specify header/library search paths with -I/-L switches, then all headers/libraries are located using the same search path. If you have multiple versions of a library installed, there may not be '''any''' combination of options which will make it work. Two modules which both use a particular library may use different combinations of other libraries, resulting in different combinations of -L switches, resulting in different versions of the first library being used. If you happen get into this situation, the only reliable way out of it (other than uninstalling stuff) is to create a dedicated header/library directory populated with symlinks to the desired versions, and specify that directory as the '''only''' additional header/library directory to be used. For the most part, it's much easier to just ensure that you don't have more than one version of anything. Of course, that's easier said than done if your OS vendor only ships versions which have been considered "stable" for at least three years but you need to use some FOSS package whose maintainers view anything over a month old as a historical relic. -- Ticket URL: <http://trac.osgeo.org/grass/ticket/838#comment:8> GRASS GIS <http://grass.osgeo.org>
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
