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 #18 from hjl dot tools at gmail dot com  2008-06-09 23:58 -------
(In reply to comment #17)
> Subject: Re:  [4.3/4.4 Regression]: HOSTCC doesn't work
>  with unstalled gcc
> 
> hjl dot tools at gmail dot com wrote:
> > ------- Comment #16 from hjl dot tools at gmail dot com  2008-06-09 14:16 -------
> > (In reply to comment #9)
> >> I suspect that if you remove the setting in site.exp you will break the 
> >> following scenario:
> >>
> >> 1. User puts libraries/headers in $pefix/{lib,include}
> > 
> > I am not convinced it is the right thing to do. What
> > are those libraries/headers? Are they from gcc? If yes,
> > you don't need to do it. If not, can you use --sysroot
> > to handle non-gcc libraries/headers?
> 
> In general, no, these are not from GCC.  They're probably from your C 
> library -- which might not be GLIBC or Newlib, of course.  And, they 
> probably include your installed assembler and linker -- which not be 
> from GNU binutils, of course.
>

They sound to me the ideal usage for --sysroot. They aren't from
gcc and they don't change from one gcc version to another one.
You can use one --sysroot for gcc 4.1, 4.2, 4.3, 4.4, ...
--syroot supports libraries and headers.  Does it support
assembler and linker?


-- 


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]