Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 26880 - apps built with graphviz fail to link shared libraries
Summary: apps built with graphviz fail to link shared libraries
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Marius Mauch (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-18 12:44 UTC by Wiffle Fan
Modified: 2003-09-30 20:39 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wiffle Fan 2003-08-18 12:44:13 UTC
I have successfully emerged, built, and installed the graphviz ebuild.  I can
successfully build a C/C++ application that relies on one of the graphviz
libraries.  However, when attempting to execute the application that relies on
graphviz, an "error while loading shared libraries: libagraph.so.0: cannot open
shared object file: No such file or directory" error appears, and the program
fails to execute.

Reproducible: Always
Steps to Reproduce:
1.emerge graphviz
2.build a C/C++ application that includes "agraph.h"
3.attempt to execute the new application

Actual Results:  
the application fails to execute, and an error message appears that says ""error
while loading shared libraries: libagraph.so.0: cannot open shared object file:
No such file or directory"

Expected Results:  
the application should have executed successfully

this can be fixed easily by adding a "/usr/lib/graphviz" line to
/etc/ld.so.conf; for some reason, env-update fails to add that line
Comment 1 Marius Mauch (RETIRED) gentoo-dev 2003-09-30 20:39:04 UTC
Don't know anything about graphviz but as I see it you want to compile a
custom app, so you should pass the library path to gcc (the -L option) to
find the libagraph.so. I mark this as invalid because it doesn't break a
package in portage and you probably don't want that we add every possible
library path to ld.so.conf ;)