#16274: include system pkgconfig path
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: defect | Status: positive_review
Priority: blocker | Milestone: sage-6.2
Component: build | Resolution:
Keywords: R cairo pango X11 | Merged in:
graphics pkg-config | Reviewers: Leif Leonhardy
Authors: Volker Braun | Work issues:
Report Upstream: N/A | Commit:
Branch: | e9b4a60563f815c99dd37014c639f94b126d1018
u/vbraun/include_system_pkgconfig_path| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by leif):
Replying to [comment:38 leif]:
> I still don't get what goes wrong or who's to blame otherwise.
Apparently some GNUish non-POSIX interpretation of how `command -v` is
supposed to work.
Under "normal"(?) circumstances, bash (even when invoked as `/bin/sh`)
returns the path of '''any existing''' (not necessarily executable or even
readable) file "foo" found along `PATH` as the result of `command -v foo`.
In contrast, `bash --posix -c "command -v foo"` acts as expected.
[[BR]]
That still doesn't explain why {{{esyscmd(`bash -c "command -v pkg-
config"')}}} worked for me (without using a temporary file), whereas
{{{esyscmd(`command -v pkg-config')}}} did not.
Digging through `strace`s, the former calls both `stat()` and `access()`,
while the latter only calls `stat()` and seems to be happy with that.
--
Ticket URL: <http://trac.sagemath.org/ticket/16274#comment:52>
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.
