[Bug binutils/23731] Building from git issues Ubuntu

[nickc at redhat dot com]

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

Nick Clifton <nickc at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nickc at redhat dot com

--- Comment #1 from Nick Clifton <nickc at redhat dot com> ---
Hi Jon,

> 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

Sorry for this.  I think that the assumption has always been that if you want
to work on the development of the binutils (or a compiler, or gdb, or any other
low level tool) then you will already have all of these other packages
installed.

The top level configure.ac file (which is used to generate the configure file)
does already have checks for these tools, but if they are absent it uses the
"missing" script to replace them.  This behaviour has been inherited from the
gcc project, which actually has the master version of the configure.ac file.


> 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?

One trick that some people use, (including myself) is to "touch" the generated
files after they have been extracted from the source tarball/downloaded from
the git repository, but before the build starts.  In that way they do not need
to be regenerated.


> 2) After "bison" and "flex" I saw this error:
> 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'

Using the trick above should resolve this problem.  Providing that you start
with an empty build directory.


> 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); }

These files are part of GDB, not the binutils.  So you need to report this
particular problem there ... 

Cheers
  Nick

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