Re: how to debug go build errors

[Martin Sebor <msebor at gmail dot com>]

Never mind.  I see the problem.  I overlooked a few failures
in the preprocessor test suite.  Turns out the patch accidentally
deletes the -d option from the .opt file.  I didn't notice it in
the diff because the "-d" at the beginning of the line looks just
like the option is still there!

@@ -1186,7 +1186,6 @@ ansi
 C ObjC C++ ObjC++
 A synonym for -std=c89 (for C) or -std=c++98 (for C++).

-d
 C ObjC C++ ObjC++ Joined
 ; Documented in common.opt.  FIXME - what about -dI, -dD, -dN and -dD?

Sorry for the noise!

On 02/08/2018 04:24 PM, Martin Sebor wrote:
> Hi Ian,
>
> While testing what should be an innocuous patch to add LTO
> to a bunch of middle-end warning options
>
>   https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00381.html
>
> I get Go errors during ordinary bootstrap about undefined names
> for errno constants:
>
> /opt/notnfs/msebor/src/gcc/84212/libgo/go/syscall/env_unix.go:96:10:
> error: reference to undefined name ‘EINVAL’
>
> Bootstrapping all other front ends (including Ada and Brig),
> succeeds and there are no regressions in the test suite.
>
> I have no experience with Go.  Does anything about the patch
> jump out at you that could be causing this?  If not, can you
> suggest how to debug it?
>
> Thanks
> Martin