From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc-patches@gcc.gnu.org, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com
Subject: (toplevel) remove squirelly path setting
Date: Sat, 28 Dec 2002 00:28:00 -0000 [thread overview]
Message-ID: <20021228072754.GA7935@doctormoo> (raw)
Tested by configuring on i686-pc-linux-gnu. This code is, as suspected,
unneeded.
* configure.in: Remove unnecessary PATH setting.
Index: configure.in
===================================================================
RCS file: /cvs/gcc/gcc/configure.in,v
retrieving revision 1.200
diff -u -r1.200 configure.in
--- configure.in 28 Dec 2002 06:57:48 -0000 1.200
+++ configure.in 28 Dec 2002 07:25:48 -0000
@@ -80,14 +80,6 @@
# if PWD already has a value, it is probably wrong.
if test -n "$PWD" ; then PWD=`${PWDCMD-pwd}`; fi
-case "${progname}" in
-/* | [[A-Za-z]]:[[\\/]]* ) ;;
-*/*) ;;
-*)
- PATH=$PATH:${PWD=`${PWDCMD-pwd}`} ; export PATH
- ;;
-esac
-
# Export original configure arguments for use by sub-configures.
TOPLEVEL_CONFIGURE_ARGUMENTS="$progname $@"
export TOPLEVEL_CONFIGURE_ARGUMENTS
next reply other threads:[~2002-12-28 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 0:28 Nathanael Nerode [this message]
2002-12-28 1:06 ` Alexandre Oliva
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=20021228072754.GA7935@doctormoo \
--to=neroden@twcny.rr.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@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