I think I may have found a section of the WIKI that needs a little
modification (perhaps). Reading section 6 under Installation of the tutorial
page on compiling the GDAL/OGR plugin, it reads:
"6. GDAL/OGR-GRASS plugin - file: gdal-grass-1.3.1.1.tar.gz (or later) [1]
NOTE: the plugin needs to see the GRASS libraries . The best way is to add a
file 'grass6.conf' into the directory /etc/ld.so.conf.d (edit as root) which
contains the path to the GRASS libraries; then run 'ldconfig'."
What if I have a path in /etc/ld.so.conf that points to my Grass libs? Will
my compile stand a better chance of having the Grass libs detected one way
or another? For example, here's my /etc/ld.so.conf:
/usr/X11R6/lib
/usr/local/lib
/usr/share/qt3/lib
/usr/local/grass-6.1.cvs/lib
/opt/grass-6.1.cvs/lib
I'm currently trying to get Grass-cvs compiled on /opt. Maybe a line should
be added to the section of the WIKI noted above that only a line within
/etc/ld.so.conf need point to Grass libs if indeed that is the case?
~ Eric.
Patton, Eric wrote:
I think I may have found a section of the WIKI that needs a little
modification (perhaps). Reading section 6 under Installation of the tutorial
page on compiling the GDAL/OGR plugin, it reads:
"6. GDAL/OGR-GRASS plugin - file: gdal-grass-1.3.1.1.tar.gz (or later) [1]
NOTE: the plugin needs to see the GRASS libraries . The best way is to add a
file 'grass6.conf' into the directory /etc/ld.so.conf.d (edit as root) which
contains the path to the GRASS libraries; then run 'ldconfig'."
What if I have a path in /etc/ld.so.conf that points to my Grass libs? Will
my compile stand a better chance of having the Grass libs detected one way
or another? For example, here's my /etc/ld.so.conf:
/usr/X11R6/lib
/usr/local/lib
/usr/share/qt3/lib
/usr/local/grass-6.1.cvs/lib
/opt/grass-6.1.cvs/lib
I'm currently trying to get Grass-cvs compiled on /opt. Maybe a line should
be added to the section of the WIKI noted above that only a line within
/etc/ld.so.conf need point to Grass libs if indeed that is the case?
Eric,
the only way is to try out and then add the answer to the wiki. The
first line in /etc/ld.so.conf
which refers to GRASS will be picked, if it contains all libs, the
system is happy, otherwise
will seek the second indication. Here is the danger to mess up things,
so I suggest to
indicate only a single path to GRASS libs in the /etc/ld.so.conf file.
Markus
Patton, Eric wrote:
I think I may have found a section of the WIKI that needs a little
modification (perhaps). Reading section 6 under Installation of the tutorial
page on compiling the GDAL/OGR plugin, it reads:
"6. GDAL/OGR-GRASS plugin - file: gdal-grass-1.3.1.1.tar.gz (or later) [1]
NOTE: the plugin needs to see the GRASS libraries . The best way is to add a
file 'grass6.conf' into the directory /etc/ld.so.conf.d (edit as root) which
contains the path to the GRASS libraries; then run 'ldconfig'."
What if I have a path in /etc/ld.so.conf that points to my Grass libs? Will
my compile stand a better chance of having the Grass libs detected one way
or another?
Possibly. But this isn't related to your libstdc++ problems.
ld.so.conf is used by ldconfig to generate the ld.so.cache file, which
is used by the loader (aka "run-time linker") to locate shared
libraries when a program is run. It doesn't affect where the linker
looks for the specified libraries at compile time.
Also, I'm not sure whether the /etc/ld.so.conf.d is used directly by
ldconfig, or whether it's used by an init script to create ld.so.conf
at boot time (my Gentoo system doesn't have a ld.so.conf.d directory).
If it's the latter, you will need to perform some additional step (I
have no idea what) between adding the grass6.conf file and running
ldconfig.
For example, here's my /etc/ld.so.conf:
/usr/X11R6/lib
/usr/local/lib
/usr/share/qt3/lib
/usr/local/grass-6.1.cvs/lib
/opt/grass-6.1.cvs/lib
I'm currently trying to get Grass-cvs compiled on /opt. Maybe a line should
be added to the section of the WIKI noted above that only a line within
/etc/ld.so.conf need point to Grass libs if indeed that is the case?
Regardless of whether you use the ld.so.conf file or the ld.so.conf.d
directory, neither will have any effect until you run ldconfig. The
loader itself only uses the ld.so.cache file.
--
Glynn Clements <glynn@gclements.plus.com>