On Mon, Dec 19, 2005 at 01:18:21PM +0000, Richard Earnshaw wrote: > I think the problem is PWDCMD (defaults to pwd) in the top-level > makefile. If your shell builds in pwd, then things will work. If it > doesn't then you'll get /bin/pwd which gives the canonical path. Bash > has a built-in pwd, and since on Linux /bin/sh is bash in disguise, it > still uses the builtin. A traditional Berkeley sh doesn't do this. > > 'info pwd' on Linux says: > > `pwd' prints the fully resolved name of the current directory. > That is, all components of the printed name will be actual > directory names--none will be symbolic links. > > I suspect that if you run a bootstrap of gcc on Linux with > PWDCMD=/bin/pwd it will fail too.
Yes, I saw a suggestion about this on IRC, but I tried it - it doesn't fail. The path that matters is not one ever returned by PWDCMD but the one seen in $PWD by GCC; the only cd that's happened at that point is done in the shell, by the toplevel Makefile, into 'gcc'. -- Daniel Jacobowitz CodeSourcery, LLC
