From: Dave Kirby <dave.x.kirby@gmail.com>
To: gdb@sourceware.org
Subject: gdb failing to build on RHEL 6
Date: Thu, 20 Nov 2014 11:31:00 -0000 [thread overview]
Message-ID: <CAJxbLdSZJf-1EQAYYeHABa51ppFzeN=eLXPETJAr+fsWJy2D8g@mail.gmail.com> (raw)
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
next reply other threads:[~2014-11-20 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 11:31 Dave Kirby [this message]
2014-11-20 11:45 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJxbLdSZJf-1EQAYYeHABa51ppFzeN=eLXPETJAr+fsWJy2D8g@mail.gmail.com' \
--to=dave.x.kirby@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).