From: Jeffrey A Law <law@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: msokolov@ivan.Harhan.ORG (Michael Sokolov),
binutils@sources.redhat.com, gcc-patches@gcc.gnu.org,
gdb-patches@sources.redhat.com
Subject: Re: PATCH to top level: don't use dirname in configure
Date: Sun, 23 Jul 2000 09:11:00 -0000 [thread overview]
Message-ID: <12548.964368714@upchuck> (raw)
In-Reply-To: <200007220919.FAA12005@indy.delorie.com>
In message < 200007220919.FAA12005@indy.delorie.com >you write:
> > Date: Fri, 21 Jul 00 17:29:14 CDT
> > From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
> >
> > ! topsrcdir=`cd \`echo ${progname} | sed 's:/configure$::'\`; pwd`
>
> This assumes that (a) $(progname) always expands to "configure", and
> (b) that the last delimiter is '/'. I don't know whether the first
> assumption is true on each supported system, but the second might be
> wrong on DOS/Windows where a backslash might be used instead.
I believe we can use something like this to deal with the first problem:
## this sed command emulates the dirname command
dstdir=`echo $dst | sed -e 's,[^/]*$,,;s,/$,,;s,^$,.,'`
The second problem exists in many places in the various configure & install
scripts and probably should be attacked and fixed en-masse.
Michael -- can you verify the sed command I provided above does the right
thing for you?
Also I'd like to have a comment which references dirname (like the one above)
to make these things easier to find (either when updating them to handle
DOS filesystems in the future, or when we need to find a suitable sed command
to emulate dirname elsewhere).
Thanks,
jeff
next parent reply other threads:[~2000-07-23 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200007220919.FAA12005@indy.delorie.com>
2000-07-23 9:11 ` Jeffrey A Law [this message]
2000-07-22 8:44 Michael Sokolov
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=12548.964368714@upchuck \
--to=law@cygnus.com \
--cc=binutils@sources.redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=msokolov@ivan.Harhan.ORG \
/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