From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: drow@false.org, gdb@sourceware.org, chrisj@rtems.org,
joel.sherrill@OARcorp.com
Subject: Re: [ANNOUNCEMENT] GDB 6.7 released!
Date: Sun, 14 Oct 2007 09:46:00 -0000 [thread overview]
Message-ID: <1192355172.3500.73.camel@mccallum.corsepiu.local> (raw)
In-Reply-To: <uzlyol2d7.fsf@gnu.org>
On Fri, 2007-10-12 at 18:33 +0200, Eli Zaretskii wrote:
> > From: Ralf Corsepius <ralf.corsepius@rtems.org>
> > Cc: drow@false.org, gdb@sourceware.org, chrisj@rtems.org, joel.sherrill@OARcorp.com
> > Date: Fri, 12 Oct 2007 11:15:26 +0200
> >
> > > Note that, strictly speaking, this problem is more or less harmless in
> > > the official release (as opposed to CVS snapshot) because all the Info
> > > files are already built and distributed as part of the tarball.
> > Such is theory ;)
> >
> > I encountered this issue when building gdb-4.7 rpms from original
> > gdb-6.7 tarballs with no patches applied.
>
> Sorry, I don't understand: are you saying that you don't see the
> *.info* files in the gdb-6.7 tarball (some or all of them)?
Sorry, I was wrong. I didn't look carefully enough.
What happens, is "make" returning with an error, which causes building
to abort:
...
Doing info in libiberty
make[2]: Entering directory
`/users/rtems/src/rpms/BUILD/rtems-4.9-i386-rtems4.9-gdb-6.7/build/libiberty'
/users/rtems/src/rpms/BUILD/rtems-4.9-i386-rtems4.9-gdb-6.7/gdb-6.7/missing makeinfo --split-size=5000000 --split-size=5000000 -I../../gdb-6.7/libiberty ../../gdb-6.7/libiberty/libiberty.texi
WARNING: `makeinfo' is missing on your system. You should only need it
if
you modified a `.texi' or `.texinfo' file, or any other file
indirectly affecting the aspect of the manual. The spurious
call might also be the consequence of using a buggy
`make' (AIX,
DU, IRIX). You might want to install the `Texinfo' package or
the `GNU make' package. Grab either from any GNU archive site.
make[2]: *** [libiberty.info] Error 1
make[2]: Leaving directory
`/users/rtems/src/rpms/BUILD/rtems-4.9-i386-rtems4.9-gdb-6.7/build/libiberty'
make[1]: *** [info-libiberty] Error 1
make[1]: Leaving directory
`/users/rtems/src/rpms/BUILD/rtems-4.9-i386-rtems4.9-gdb-6.7/build'
make: *** [do-info] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.42398 (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.42398 (%build)
Ralf
next prev parent reply other threads:[~2007-10-14 9:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 19:19 Joel Brobecker
2007-10-11 11:49 ` Ralf Corsepius
2007-10-11 12:14 ` Daniel Jacobowitz
2007-10-11 13:54 ` Ralf Corsepius
2007-10-11 14:04 ` Daniel Jacobowitz
2007-10-11 15:52 ` Joel Brobecker
2007-10-12 14:04 ` Daniel Jacobowitz
2007-10-12 8:01 ` Eli Zaretskii
2007-10-12 9:15 ` Ralf Corsepius
2007-10-12 16:34 ` Eli Zaretskii
2007-10-12 16:42 ` Joel Brobecker
2007-10-14 9:46 ` Ralf Corsepius [this message]
2007-10-14 15:39 ` Daniel Jacobowitz
2007-10-14 20:38 ` Eli Zaretskii
2007-10-14 20:57 ` Daniel Jacobowitz
2007-10-14 20:27 ` Eli Zaretskii
2007-10-13 4:15 Michael Snyder
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=1192355172.3500.73.camel@mccallum.corsepiu.local \
--to=ralf.corsepius@rtems.org \
--cc=chrisj@rtems.org \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=joel.sherrill@OARcorp.com \
/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).