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: Fri, 12 Oct 2007 09:15:00 -0000 [thread overview]
Message-ID: <1192180526.3500.42.camel@mccallum.corsepiu.local> (raw)
In-Reply-To: <ufy0gn4o6.fsf@gnu.org>
On Fri, 2007-10-12 at 10:00 +0200, Eli Zaretskii wrote:
> > From: Ralf Corsepius <ralf.corsepius@rtems.org>
> > Cc: gdb@sourceware.org, Chris Johns <chrisj@rtems.org>, Joel Sherrill <joel.sherrill@OARcorp.com>
> > Date: Thu, 11 Oct 2007 15:53:56 +0200
> >
> > # makeinfo --version
> > makeinfo (GNU texinfo) 4.11
> >
> > Copyright (C) 2007 Free Software Foundation, Inc.
> > License GPLv3+: GNU GPL version 3 or later
> > <http://gnu.org/licenses/gpl.html>
> > This is free software: you are free to change and redistribute it.
> > There is NO WARRANTY, to the extent permitted by law.
> >
> > > Either too old or so new
> > Probably the latter.
>
> 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.
This triggers this configure script bug in libiberty, and caused info
file generation to break, causing some info files to be missing in the
final build.
Ralf
next prev parent reply other threads:[~2007-10-12 9:15 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 [this message]
2007-10-12 16:34 ` Eli Zaretskii
2007-10-12 16:42 ` Joel Brobecker
2007-10-14 9:46 ` Ralf Corsepius
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=1192180526.3500.42.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).