I don't think there is a way to find out which path was compiled into the
system pkg-config binary. We should just make our pkg-config a script that
punts to the system pkg-config if the library is not in Sage.
On Thursday, May 1, 2014 8:18:18 PM UTC+1, François wrote:
>
> That’s a serious issue that Volker and I have overlooked when pushing
> for pkg-config. For those who don’t the tipping point for inclusion
> was building recent matplotlib in OS X. matplotlib absolutely relies
> on using pkgconfig and all the previous work around failed with 1.3.1.
> At which point we decided the easiest solution was inclusion of
> pkgconfig.
> Now to fix this, and I believe you are right that this is a blocker, I
> think we should change the way we override PKG_CONFIG_PATH
> in sage-env. pkgconfig usually has a hardcoded internal value for
> system install so you are able to find system packages without the
> variable
> having to be defined. We are breaking that.
> So we should either find the system folders in sage-env or patch our
> pkgconfig source to search them automagically.
>
> As a work around that doesn’t involve moving things around defining
> PKG_CONFIG_PATH=/usr/lib{64}/pkgconfig
> before running make should help.
>
> Francois
> On 2/05/2014, at 5:38, William Stein <wst...@gmail.com <javascript:>>
> wrote:
>
> > Hi,
> >
> > I just spent a while trying to figure out how to get R png graphics to
> > work again in Sage-6.2rc0 on Ubuntu 14.04. Note that graphics worked
> > fine with Sage-6.2beta1 on Ubuntu 12.04. Karl Dieter's many random
> > posts around the web asking about this problem were helpful, though in
> > this case the problem is new in sage-6.2rc0 due to trac #15742, and
> > will kill R usage for a lot of people if we release sage-6.2.rc0 as
> > is...
> >
> > I tracked the problem down to pkg-config being in Sage-6.2rc0, whereas
> > it is not in Sage-6.2beta1.
> >
> > This is because of http://trac.sagemath.org/ticket/15742, which is
> > very important to getting Sage to build at all on some wonky systems.
> > But on a mainstream modern Linux OS this ticket leads to problems.
> > Wouldn't it be better to only build/install pkgconfig on systems that
> > don't have a good one already?
> >
> > My solution to deal with this R problem is:
> >
> > cd $SAGE_ROOT/local/bin && mv pkg-config pkg-config.orig && ln -s
> > /usr/bin/pkg-config .
> > sage -f r
> >
> > Of course, I have to wonder what other components of Sage got built
> > incorrectly due to Sage's pkg-config returning misleading results
> > (e.g., saying that a system-wide library isn't available even though
> > it is)...
> >
> > William
> >
> >
> > --
> > William Stein
> > Professor of Mathematics
> > University of Washington
> > http://wstein.org
> >
> > --
> > 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 sage-devel+...@googlegroups.com <javascript:>.
> > To post to this group, send email to
> > sage-...@googlegroups.com<javascript:>.
>
> > Visit this group at http://groups.google.com/group/sage-devel.
> > For more options, visit https://groups.google.com/d/optout.
>
>
> This email may be confidential and subject to legal privilege, it may
> not reflect the views of the University of Canterbury, and it is not
> guaranteed to be virus free. If you are not an intended recipient,
> please notify the sender immediately and erase all copies of the message
> and any attachments.
>
> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
> information.
>
--
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
