On Thu, 2016-06-30 16:09:23 -0400, David Malcolm <dmalc...@redhat.com> wrote: > On Thu, 2016-06-30 at 08:38 -0400, Nathan Sidwell wrote: > > > I haven't given it any additional manual testing so far. It's > > > pre-installation though. Maybe I'd just set WIND_BASE to some > > > arbitrary value, just to make xgcc pass it's initial start-up > > > test so that it can continue with self-testing? Or shall we set > > > some value in gcc/Makefile.in for running the self-test? > > > > As I recall, WIND_BASE is expected to point at a vxworks install > > to pick up header files. It is an error not to have it set > > (silently skipping it leads to user confusion). > > > > If that's irrelevant for this testing environment, then setting it > > to something (probably just "", but safer might be > > "/These.are.not.the.dirs.you.are.looking.for") should be fine. > > Sorry about the breakage.
You just uncovered it :)
> The error message appears to affect a few other targets within
> gcc/Makefile.in.
[...]
>
> So there are at least 2 ways of fixing this:
>
> (a) add "-nostdinc" when running the selftests i.e. to the invocations
> of GCC_FOR_TARGET in the "s-selftest" and "selftest-gdb" clauses of
> gcc/Makefile.in.
> I've verified that this fixes the issue for --target=i686-wrs-vxworks.
>
> (b) set WIND_BASE to a dummy value in contrib/config-list.mk (if not
> already set) so that the vxworks targets are able to at least build all
> of "gcc" without needing a vxworks install.
I'd probably just do (b) and go for it. Easy, non-invasive fix.
MfG, JBG
--
Jan-Benedict Glaw jbg...@lug-owl.de +49-172-7608481
Signature of: Don't believe in miracles: Rely on them!
the second :
signature.asc
Description: Digital signature
