gdb failing to build on RHEL 6

gdb failing to build on RHEL 6

[Dave Kirby]

I am trying to build the latest version of gdb on RHEL 6, but it is
failing with the following error:

> ...
> make[1]: Leaving directory `/home/tideway/tools/binutils-gdb/gdb'
> /bin/sh ./common/create-version.sh . \
>               version.c
> mv: missing destination file operand after `version.c-tmp'
> Try `mv --help' for more information.
> gcc -g -O2   -I. -I. -I./common -I./config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I./../include/opcode -I./../opcodes/.. -I./../readline/.. -I../bfd -I./../bfd -I./../include -I../libdecnumber -I./../libdecnumber  -I./gnulib/import -Ibuild-gnulib/import   -DTUI=1  -I/usr/tideway/include/python2.7 -I/usr/tideway/include/python2.7 -Wall -Wdeclaration-after-statement -Wpointer-arith -Wpointer-sign -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wmissing-prototypes -Wdeclaration-after-statement -Wempty-body -Wmissing-parameter-type -Wold-style-declaration -Wold-style-definition -Wformat-nonliteral -Werror -c -o version.o -MT version.o -MMD -MP -MF .deps/version.Tpo version.c
> gcc: version.c: No such file or directory
> gcc: no input files
> make: *** [version.o] Error 1

I have tried it with both the official 7.8.1 release from the ftp site
and the current head from the git repository - commit
8908fca5772fcff9f7766158ba2aa59f5a2b1f68.

I googled the error but all I found was a post on this forum from last
June with someone reporting the same problem
(http://sourceware.org/ml/gdb/2014-06/msg00007.html).  The only
response said there had been a broken commit, but no work-around was
given.  I find it hard to believe that it is the same issue and that
gdb has been released in a state where it would not build.

So what am I missing?  Or doing wrong?  Or is the release itself
broken?  How do I fix it and get a working build?

Dave

Re: gdb failing to build on RHEL 6

[Joel Brobecker]

> I have tried it with both the official 7.8.1 release from the ftp site
> and the current head from the git repository - commit
> 8908fca5772fcff9f7766158ba2aa59f5a2b1f68.
> 
> I googled the error but all I found was a post on this forum from last
> June with someone reporting the same problem
> (http://sourceware.org/ml/gdb/2014-06/msg00007.html).  The only
> response said there had been a broken commit, but no work-around was
> given.  I find it hard to believe that it is the same issue and that
> gdb has been released in a state where it would not build.
> 
> So what am I missing?  Or doing wrong?  Or is the release itself
> broken?  How do I fix it and get a working build?

version.c is create by a Makefile rule that calls
gdb/common/create-version.sh.

I would check your build logs to see if that script got called,
and if it did, then whether it printed any error or not.

-- 
Joel