This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: cross-builds failing
- To: manfred at s-direktnet dot de, Manfred dot Hollstein at ks dot sel dot alcatel dot de
- Subject: Re: cross-builds failing
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 07 Oct 1998 02:38:03 -0600
- cc: richard dot earnshaw at arm dot com, egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <13851.9309.876684.984215@slsvhmt>you write:
> I guess, this is an unfortunate side-effect of the $(unlibsubdir)
> patch that had been applied last week. gcc and cpp are now using a
> relative path starting from $(libsubdir); since your xgcc isnt't already
> installed, $(libsubdir) of course doesn't exist, hence
> $(libsubdir)/../../../${target}/include doesn't either.
>
> Jeff, you mentionened somewhere, that the $(unlibsubdir) was mostly
> meant to aid the Windoof users; how do you think, if we'll be going to
> implement it via a new "--enable-relative-dirs" flag and retain the old
> behaviour as a default?
Something's got to be messed up somewhere -- Cygnus has been using this stuff
for about 4 years now. We've got a bug, we should go fix it, not disable
the feature via configury. :-)
I just backed out one patch that depends on code not yet in the compiler
(the final bits to allow movement of binaries). I don't think it would
effect Richard's problem though.
jeff