#16274: include system pkgconfig path
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-6.2
Component: build | Resolution:
Keywords: | Merged in:
Authors: Volker Braun | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/include_system_pkgconfig_path|
afcbfaf2ebadbc81eec58cdc9060c1ae2be6c94d
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by leif):
Replying to [comment:11 fbissey]:
> Replying to [comment:10 leif]:
> > One issue still is that we have to call the system-wide `pkg-config`
(if present) in `spkg-install`; I'd suggest to modify `sage-env` to save
the original `PATH` in `SAGE_ORIG_PATH`, say.
> >
> > (Otherwise we'd presumably at least accumulate folders upon
reinstallation of Sage's `pkgconf`.)
> >
> > Or we could first try to delete Sage's symlink from `pkg-config` to
`pkgconf`.
> >
> Have you read Volker's patch?
Yes, a while ago though... m)
> One of the first thing he does is removing any pkg-config already
installed in sage.
Well, "the" `pkg-config` if present.
> Since we are interested in hardcoded path in the application doing
> {{{
> PKG_CONFIG_PATH="" pkg-config .....
> }}}
> would work.
Yep. Or go with `(unset PKG_CONFIG_PATH; ...)`.
--
Ticket URL: <http://trac.sagemath.org/ticket/16274#comment:12>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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-trac.
For more options, visit https://groups.google.com/d/optout.
