This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug testsuite/36443] [4.3/4.4 Regression]: HOSTCC doesn't work with installed gcc



------- Comment #22 from hjl dot tools at gmail dot com  2008-06-10 05:49 -------
(In reply to comment #21)
> Subject: Re:  [4.3/4.4 Regression]: HOSTCC doesn't work
>  with installed gcc
> 
> hjl dot tools at gmail dot com wrote:
> 
> >>> --syroot supports libraries and headers.  Does it support
> >>> assembler and linker?
> >> Not as far as I know; --sysroot is about the target, not the host.
> > 
> > So setting GCC_EXEC_PREFIX is to support "make check" using
> > non-system assembler and linker with gcc for a target which
> > probably isn't a GNU target/OS. Am I correct?
> 
> Or which *is* a GNU target/OS, but isn't using an in-tree build of all 
> the components -- like, for example, if you already have good versions 
> of the cross tools around.
> 

I have done that all the time. I just combine a known good gcc source tree
with a known good binutils source tree. The main problem is many times
the common directories, like include, libiberty and top level files, aren't
compatible between gcc and binutils. My solutions are

1. Use PATH for build/testing if I can't use combined tree.  Or
2. Patch the common directories/files so that they are compatible between
gcc and binutils.

I thought it was my problem. I believe such changes belong to vendor
branches, not gcc trunk.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36443


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]