François Bissey wrote:
On Thu, 01 May 2014 23:06:53 leif wrote:
François Bissey wrote:
On Thu, 01 May 2014 22:58:47 leif wrote:
Felix Salfelder wrote:
pkg-config --variable pc_path pkg-config

That doesn't always work.  (See my other post on how to get it.)

Using configure is certainly a good option. +1, I like it.

Sage's top-level 'configure' or pkg-config's?


sage's configure.

Well, we could just patch our pkgconf; it apparently hasn't a configure option to set the default search path, but hardcodes

    -DPKG_DEFAULT_PATH=\"${pkgconfigdir}\"

in Makefile.in.

So we could look up a system's pkg-config path in its spkg-install, and append it to our pkgconf's.

(Unfortunately sage-env currently doesn't save the original setting of PATH though, AFAICS, so we'd have to do that as well.)


We could put it into sage-env as well, but regarding how often that's
called...


I was actually thinking of feeding it to sage-env :)

? sage-env.in?

The problem is that it's under revision control of course, but we could there source some $SAGE_ROOT/local/var/lib/sage/system_pkg-config_path if it exists...


I gave up with 'sed' (due to shell escape weirdness), but we'd have to
use $AWK (or @AWK@) otherwise to stay portable.


And "sed -i" is a GNU extension, that is one of the pains I have dealing
with AIX.

On Solaris as well...


-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 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.

Reply via email to