Tom Browder wrote: > On 1/16/08, Tom Browder <tom.browder@xxxxxxxxx> wrote: >> I'm trying to help with a new front end for gcc and have a question >> about the configure system: >> >> I notice that each Makefile generated by configure defines srcdir at >> the top as the directory it is formed in (and then sometimes redefines >> it later). >> >> How, then, should one refer to the absolute root of the source tree >> regardless of the depth of the Makefile? > > I should have been a little more specific: > > The recommended way to build gcc is to use a clean directory outside > the source tree somthing like this: > > mkdir build_dir > cd build_dir > /path/to/gcc_src/configure <options> > > I want to know if there is a preferred or defined way to refer to > "/path/to/gcc_src" in build scripts or configure inputs since > "$(srcdir)" seems to be locally defined per Makefile. > During bootstrap, by default, I observe that $HOME is included in a search for your /path/to/gcc_src When $HOME refers to a path which misleads the bootstrap machinery, it is necessary to export HOME= in order to make the bootstrap succeed. Is there documentation on how this is intended to work?
