[Bug binutils/23731] New: Building from git issues Ubuntu

[jg at jguk dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=23731

            Bug ID: 23731
           Summary: Building from git issues Ubuntu
           Product: binutils
           Version: 2.32 (HEAD)
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: jg at jguk dot org
  Target Milestone: ---

1)
Is there a way for ./configure to check for "makeinfo" "bison" "flex" commands
first? I just get it bailing out at the end half way through a build. I imagine
everyone else on Ubuntu sees the same as me... Impacts new developers getting
started


gcc -c -I. -I. -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow
-Wstack-usage=262144 -Werror -I./../zlib -g -O2 -Wno-error ./syslex_wrap.c
./syslex_wrap.c:25:10: fatal error: syslex.c: No such file or directory
 #include "syslex.c"
          ^~~~~~~~~~
compilation terminated.


As bison, flex, makeinfo commands a really needed, and they mess with the files
generated which must be cleaned... could these be checked up front?


2) After "bison" and "flex" I saw this error:

I got this error:

configure: loading cache ./config.cache
configure: error: `YACC' has changed since the previous run:
configure:   former value:  `/home/jonny/code/binutils-gdb/missing bison -y'
configure:   current value: `bison -y'
configure: error: in `/home/jonny/code/binutils-gdb/binutils':
configure: error: changes in the environment can compromise the build
configure: error: run `make distclean' and/or `rm ./config.cache' and start
over
Makefile:3527: recipe for target 'configure-binutils' failed
make[1]: *** [configure-binutils] Error 1
make[1]: Leaving directory '/home/jonny/code/binutils-gdb'
Makefile:849: recipe for target 'all' failed
make: *** [all] Error 2


Even the following commands did not clear it:


make distclean
./configure --program-prefix=dev


I'm 20 mins in.. and still no working build.


3) 
I saw some warnings wizz past from -Wmaybe-uninitialized


  CXX    macrotab.o
In file included from infrun.c:26:0:
inferior.h: In function ‘void handle_vfork_child_exec_or_exit(int)’:
inferior.h:567:26: warning: ‘*((void*)(&
maybe_restore_inferior)+40).scoped_restore_current_inferior::m_saved_inf’ may
be used uninitialized in this function [-Wmaybe-uninitialized]
   { set_current_inferior (m_saved_inf); }
     ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~
infrun.c:931:6: note: ‘*((void*)(&
maybe_restore_inferior)+40).scoped_restore_current_inferior::m_saved_inf’ was
declared here
      maybe_restore_inferior;
      ^~~~~~~~~~~~~~~~~~~~~~
In file included from inferior.h:49:0,
                 from infrun.c:26:
progspace.h:285:31: warning: ‘*((void*)(&
maybe_restore_inferior)+32).scoped_restore_current_program_space::m_saved_pspace’
may be used uninitialized in this function [-Wmaybe-uninitialized]
   { set_current_program_space (m_saved_pspace); }
     ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
infrun.c:931:6: note: ‘*((void*)(&
maybe_restore_inferior)+32).scoped_restore_current_program_space::m_saved_pspace’
was declared here
      maybe_restore_inferior;
      ^~~~~~~~~~~~~~~~~~~~~~
  CXX    main.o



Also i noticed the build stopped once after "make -j16", but then "make" on its
own, did a lot more compiling for several minutes... could be a build race
condition.

-- 
You are receiving this mail because:
You are on the CC list for the bug.