The sage pkg-config script uses the system pkg-config if it exists (so you can use libraries that are installed system-wide), and our own pkgconf binary if not. The decision is made at Sage build time, so you need to reinstall (sage -f pkg-config) if you delete the /usr/bin/pkg-config. Though then its also quite possible that you linked to system-wide libraries via said pkg-config, so its probably better to just "make distclean && make" in that case.
On Saturday, October 17, 2015 at 1:14:24 PM UTC+2, Jeroen Demeyer wrote: > > On 2015-10-17 05:21, Francois Bissey wrote: > > It looks, to me, like /usr/local/sage/sage-1/local/bin/pkg-config was > > actually a script redirecting to /usr/bin/pkg-config. > > The problem boils down to: "pkgconf" != "pkg-config" > > Sage installs "pkgconf" but not "pkg-config" > > It adds a script redirecting $SAGE_LOCAL/bin/pkg-config to > /usr/bin/pkg-config > -- You received this message because you are subscribed to the Google Groups "sage-release" 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-release. For more options, visit https://groups.google.com/d/optout.
