This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Re: GCC 6.1 Hard-coded C++ header paths and relocation problem on Windows
- From: Brett Neumeier <bneumeier at gmail dot com>
- To: Andrew Pinski <pinskia at gmail dot com>
- Cc: lh_mouse <lh_mouse at 126 dot com>, Jonathan Wakely <jwakely dot gcc at gmail dot com>, gcc <gcc at gcc dot gnu dot org>
- Date: Tue, 10 May 2016 08:25:33 -0500
- Subject: Re: Re: GCC 6.1 Hard-coded C++ header paths and relocation problem on Windows
- Authentication-results: sourceware.org; auth=none
- References: <4bee92a3 dot 11b9f7 dot 154710b7ff9 dot Coremail dot lh_mouse at 126 dot com> <27b92139 dot 11ba0f dot 154710f77eb dot Coremail dot lh_mouse at 126 dot com> <CAH6eHdTkL_L6POiuZzDY61=ESM4ZMbepRXxZVoN5-ZnkcFkwmQ at mail dot gmail dot com> <57e3f960 dot 200a dot 154772301e2 dot Coremail dot lh_mouse at 126 dot com> <CAGSetNuPNq0vPvBVVhKZ7iCJiMZ7Dwy=uxSzPKejyhAOz+4M5g at mail dot gmail dot com> <CA+=Sn1nxn+SdBtwgYySCbjKfLw0HXOZQjbZz7dhidcvVhVTYvA at mail dot gmail dot com>
On Mon, May 9, 2016 at 4:10 PM, Andrew Pinski <pinskia@gmail.com> wrote:
> This sounds like a good use of --with-build-sysroot instead of just
> --with-sysroot.
> I use the following for the candian cross:
> --with-sysroot=/ --with-build-sysroot=${SYSROOT}
Hi Andrew! Thanks for your comment.
I thought that --with-build-sysroot is only for cross-compiler builds?
I have to admit I'm not very clear on the way that all the
cross-compiler options are intended to be used, but I am pretty sure
that it's not relevant for my case.
I have a cross-compiler that *seems* perfectly functional, for which I specify:
--build = host
--host = host
--target = target
--with-sysroot = the sysroot dir
--with-build-sysroot = the sysroot dir
Then I'm using that compiler to build a target-native compiler
installed into the sysroot directory, for which I'm specifying:
--build = host
--host = target
--target = target
--with-local-prefix = the sysroot dir
Do you think things will work better for the target-native compiler if
I use a sysroot option for it as well?
Aside from the C++ header path lookup thing that GCC 6.1 introduced, I
haven't had any problems with the target-native compiler. (I'm able to
build at least tcl, expect, dejagnu, and perl with it already.)
--
Brett Neumeier (bneumeier@gmail.com)