Date: Wed, 2 Nov 2005 13:53:39 +0100 From: Michael Nottebrock <lofi@freebsd.org> To: Volker Stolz <vs@freebsd.org> Cc: cvs-ports@freebsd.org, Tilman Linneweh <arved@freebsd.org>, ports-committers@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: cvs commit: ports/graphics/py-graphviz Makefile Message-ID: <200511021353.47830.lofi@freebsd.org> In-Reply-To: <20051102103147.GF9487@i2.informatik.rwth-aachen.de> References: <200511011418.jA1EIqVv060958@repoman.freebsd.org> <20051102094550.GA60209@arved.priv.at> <20051102103147.GF9487@i2.informatik.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1923751.mKCDf3ZY4j
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Wednesday, 2. November 2005 11:31, Volker Stolz wrote:
> Am 02. Nov 2005 um 10:45 CET schrieb Tilman Linneweh:
> > * Volker Stolz [2005-11-02 09:30]:
> > > > > arved 2005-11-01 14:18:52 UTC
> > > > >
> > > > > FreeBSD ports repository
> > > > >
> > > > > Modified files:
> > > > > graphics/py-graphviz Makefile
> > > > > Log:
> > > > > Fix dependency on graphviz, the graphviz libraries are installed
> > > > > in a non-default libdir, add BUILD_ and RUN_ dependendencies
> > > > > instead.
> > > >
> > > > Shouldn't graphviz be setting LDCONFIG_DIRS instead?
> >
> > Yes, that's the problem.
> > According to perky, the graphviz port does not install a startup script,
> > that sets LDCONFIG_DIRS, because the libraries have very common names.
>
> This means that the python-binding will be broken anyway:
> >>> from graphviz import *;
>
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> File "/usr/local/lib/python2.3/site-packages/graphviz/__init__.py", line
> 23, in ? from graphviz import *
> File "/usr/local/lib/python2.3/site-packages/graphviz/graphviz.py", line
> 5, in ? import _graphviz
> ImportError: Shared object "libagraph.so.0" not found, required by
> "_graphviz.so"
>
> Having spent the last week in -rpath-hell anyway, how about this solution:
> - ${CC} -shared ${LOCALBASE}/lib/graphviz/libagraph.so
> ${LOCALBASE}/lib/graphviz/libcdt.so gv_wrap.o -o _graphviz.so + ${L=
D}
> -shared -L${LOCALBASE}/lib/graphviz -rpath ${LOCALBASE}/lib/graphviz
> -lagraph -lcdt gv_wrap.o -o _graphviz.so
>
> This makes the use-case above work again and doesn't require and ldconfig.
> I'll check if there are any other consumers of graphviz' shlibs.
Probably not: The graphviz libraries aren't supposed to be used by other=20
applications anyway, that's why they're not in the standard library path.
The graphviz licence is incompatible with the GPL as well, prohibiting GPL'=
d=20
applications from linking to the libraries (Fun fact: There is a GPL'd=20
pygraphviz binding around (https://networkx.lanl.gov/pygraphviz/), which is=
=20
'based' on the (non-GPL'd) code that his port uses to boot. Don't even thin=
k=20
of porting that. =3D) )
=2D-=20
,_, | Michael Nottebrock | lofi@freebsd.org
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
--nextPart1923751.mKCDf3ZY4j
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)
iD8DBQBDaLbbXhc68WspdLARAtiuAJ404ZpJJQZMUq9NKe8vi340WnbVJwCeLeD1
E1eiS04yvfrmWRfcgCvuYpE=
=Jzrx
-----END PGP SIGNATURE-----
--nextPart1923751.mKCDf3ZY4j--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511021353.47830.lofi>