leif wrote:
Montgomery-Smith, Stephen wrote:
I was building sage-6.2 using FreeBSD. I found out that the subpackage
libm4ri was picking up the system libpng rather than the sage libpng.
? We prepend Sage's pkg-config dir to PKG_CONFIG_PATH in sage-env...
Or actually no longer... This is now done in our local/bin/pkg-config
wrapper script.
Probably some flaw in our dependencies?
*Might* be the cause, since our deps w.r.t. pkgconf/pkgconfig (the
latter just some Python interface) are total crap AFAICS:
The only package that depends on pkgconf is matplotlib, which means
since we removed setting PKG_CONFIG_PATH from sage-env, any package
built before pkgconf won't see Sage's pkgconfig dir and hence may pick
up packages installed system-wide instead of Sage's versions.
(I should add that I had been against [re]moving PKG_CONFIG_PATH from
sage-env, but I also have to admit that I didn't check our deps when
reviewing the wrapper script changes; I actually thought pkgconf was
meanwhile a prerequisite for almost all packages, just like e.g. patch is.)
So feel free to open a ticket, but I think we don't have to fix libm4ri
but our dependencies.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.