This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: install vs. install-sh
- From: Nathanael Nerode <neroden at twcny dot rr dot com>
- To: gcc at gcc dot gnu dot org, dj at redhat dot com
- Date: Mon, 14 Jul 2003 21:30:33 -0400
- Subject: Re: install vs. install-sh
>Got this today...
>
>/usr/bin/install: cannot create regular file
>`/greed/dj/uber/inst/lib/gcc-lib/sh-elf/3.4/cc1': No such file or
>directory
>
>The install-sh in the source tree seems to do "mkdir -p" as needed.
>Do we expect this of install? Or should we expect to call
>mkinstalldirs ourselves as needed?
What a good question.
The docs for 'ginstall' indicate that it requires the -D option in order
to do that:
install -D file directory/file
That's not portable, of course...
Alternatively the directory (plus all its parents) can be constructed
separately:
install -d directory
and then the file can be installed with
install file directory/file
This combination appears to be portable, but...
I'm guessing we should call mkinstalldirs ourselves as needed.
--
Nathanael Nerode <neroden at gcc.gnu.org>
http://home.twcny.rr.com/nerode/neroden/fdl.html