From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/pkgconfig
Date: Tue, 1 Apr 2008 08:29:04 -0700 (PDT) [thread overview]
Message-ID: <20080401152904.38D863C555@busybox.net> (raw)
Author: jacmet
Date: 2008-04-01 08:29:03 -0700 (Tue, 01 Apr 2008)
New Revision: 21612
Log:
pkgconfig: Return appropriate error code from pkgconfig script
Patch by Will Newton.
Currently the wrapper script for pkgconfig clobbers the return status
of pkgconfig. This is a problem for example when someone tries to run
"pkgconfig --exists". This patch should allow the correct return code
to be passed through. Note it uses the "pipefail" option that was
introduced with bash 3.
Modified:
trunk/buildroot/package/pkgconfig/pkgconfig-filter.sh
Changeset:
Modified: trunk/buildroot/package/pkgconfig/pkgconfig-filter.sh
===================================================================
--- trunk/buildroot/package/pkgconfig/pkgconfig-filter.sh 2008-04-01 14:50:40 UTC (rev 21611)
+++ trunk/buildroot/package/pkgconfig/pkgconfig-filter.sh 2008-04-01 15:29:03 UTC (rev 21612)
@@ -2,6 +2,8 @@
# filter the output from pkg-config (renamed as pkg-config.real)
# and ensures PKG_CONFIG_SYSROOT is prepended to all paths
+set -o pipefail
+
CMD=$0
if [ ! "$PKG_CONFIG_SYSROOT" ]; then
@@ -22,6 +24,5 @@
#echo "OKAY" >&2;
exit 0;
else
- echo "pkg-config failed!" >&2
exit $?
fi
next reply other threads:[~2008-04-01 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 15:29 jacmet at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-04 2:12 [Buildroot] svn commit: trunk/buildroot/package/pkgconfig correa at uclibc.org
2007-06-21 22:05 aldot at uclibc.org
2007-01-14 4:20 andersen at uclibc.org
2006-08-29 16:41 aldot at uclibc.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080401152904.38D863C555@busybox.net \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox