public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "allan at archlinux dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nis/14303] rpcgen looks for "cpp" in /lib, but not in /usr/bin
Date: Fri, 06 Jul 2012 15:40:00 -0000 [thread overview]
Message-ID: <bug-14303-131-3Bdl69RpRJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14303-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14303
--- Comment #1 from Allan McRae <allan at archlinux dot org> 2012-07-06 15:40:20 UTC ---
There are other patches floating around to do this.
The one attached to https://bugzilla.redhat.com/show_bug.cgi?id=456089 makes an
array of paths to search. That would be easier to extend.
Others use execvp to call cpp and so use the system path, although I doubt that
will detect /lib/cpp and /usr/ccs/lib/cpp will not be a PATH so that would not
be backwards compatible.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-07-06 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 14:54 [Bug nptl/14303] New: " arjan at linux dot intel.com
2012-06-27 14:55 ` [Bug nis/14303] " arjan at linux dot intel.com
2012-06-27 14:59 ` aj at suse dot de
2012-07-06 15:14 ` allan at archlinux dot org
2012-07-06 15:40 ` allan at archlinux dot org [this message]
2012-07-06 15:48 ` arjan at linux dot intel.com
2012-07-06 17:21 ` bugdal at aerifal dot cx
2012-07-06 17:26 ` aj at suse dot de
2012-07-06 17:33 ` arjan at linux dot intel.com
2012-07-14 8:25 ` allan at archlinux dot org
2012-07-14 8:30 ` allan at archlinux dot org
2012-07-25 18:02 ` aj at suse dot de
2012-08-08 7:20 ` aj at suse dot de
2014-06-18 4:31 ` fweimer at redhat dot com
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=bug-14303-131-3Bdl69RpRJ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).