PR4114, 4113, 4082, 4078, (part of) 4096 plus other reports in gcc-bugs

[Phil Edwards]

On Sun, Aug 26, 2001 at 09:40:46AM -0300, Alexandre Oliva wrote:
> <target>/[multilibdirs]libstdc++-v3/foo -> ../../[...]libstdc++-v3/foo
> 
> You're probably wondering why.  Think, for example, of libiberty: it's
> built for the host in <toplevel_builddir>/libiberty and for the target
> in <toplevel_builddir>/<target_alias>/[multilib]libiberty.  When
> srcdir=builddir, you'd get libiberty configured in the top-level
> directory for the host build.

That all makes sense.  In my other message I was wondering why we do
this all the time, and not (as the comments claim) only "if cross".
For a native compile, shouldn't configuring for the host be the same as
configuring for the target?  I /know/ I'm missing somthing here.


> As for clobbering the source tree in order to test this stuff, you may
> use symlink-tree to create a mirror of the source tree and then build
> in it, so it won't affect the actual source tree.

I could have sworn that the Makefiles do this already.  Isn't that why
symlink-tree is in the source in the first place?  (Beats me why it never
gets called.)


Phil

-- 
Would I had phrases that are not known, utterances that are strange, in
new language that has not been used, free from repetition, not an utterance
which has grown stale, which men of old have spoken.
                                     - anonymous Egyptian scribe, c.1700 BC