This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/11408] installation fails for many target libraries using CONFIG_SHELL
- From: "pme at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Jul 2003 23:06:46 -0000
- Subject: [Bug bootstrap/11408] installation fails for many target libraries using CONFIG_SHELL
- References: <20030702154556.11408.pme@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11408
------- Additional Comments From pme at gcc dot gnu dot org 2003-07-21 23:06 -------
Not NFS mounts, but automounters tend to get confused. Thus this fragment,
snipped from libstdc++'s configury:
# These need to be absolute paths, yet at the same time need to
# canonicalize only relative paths, because then amd will not unmount
# drives. Thus the use of PWDCMD: set it to 'pawd' or 'amq -w' if using amd.
glibcxx_builddir=`${PWDCMD-pwd}`
case $srcdir in
[\\/$]* | ?:[\\/]*) glibcxx_srcdir=${srcdir} ;;
*) glibcxx_srcdir=`cd "$srcdir" && ${PWDCMD-pwd} || echo "$srcdir"` ;;
esac
So I guess srcdir needs to stay unchanged. However, INSTALL does need to be
fixed, somehow; that's the actual bug. (The srcdir thing just caught my
attention.)