public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/30546] [4.2/4.3 regression] build fail in libgomp when building from SVN because makeinfo is missing
Date: Sat, 27 Jan 2007 03:53:00 -0000	[thread overview]
Message-ID: <20070127035254.5667.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30546-10259@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from pinskia at gcc dot gnu dot org  2007-01-27 03:52 -------
This is a minor issue at best because it only happens when building from SVN or
a snapshot and not a release.  Also we don't want to include the .info in svn
because they will then not get updated correctly when people update the
documents.

So I still say we should just require makeinfo when building from SVN/snapshot.
 There is no reason not really.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |minor
  GCC build triplet|i386-pc-mingw32             |
   GCC host triplet|i386-pc-mingw32             |
 GCC target triplet|i386-pc-mingw32             |
           Keywords|                            |build
            Summary|[4.2/4.3 regression] build  |[4.2/4.3 regression] build
                   |fail in libgomp because     |fail in libgomp when
                   |makeinfo is missing         |building from SVN because
                   |                            |makeinfo is missing


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30546


  parent reply	other threads:[~2007-01-27  3:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-22 17:36 [Bug libgomp/30546] New: [4.3 regression] build fail in libgomp " fxcoudert at gcc dot gnu dot org
2007-01-22 18:20 ` [Bug libgomp/30546] " pinskia at gcc dot gnu dot org
2007-01-26 12:34 ` jakub at gcc dot gnu dot org
2007-01-26 13:07 ` fxcoudert at gcc dot gnu dot org
2007-01-27  0:08 ` dfranke at gcc dot gnu dot org
2007-01-27  0:34 ` dfranke at gcc dot gnu dot org
2007-01-27  0:37   ` Andrew Pinski
2007-01-27  0:37 ` pinskia at physics dot uc dot edu
2007-01-27  1:11 ` [Bug libgomp/30546] [4.2/4.3 " dfranke at gcc dot gnu dot org
2007-01-27  3:53 ` pinskia at gcc dot gnu dot org [this message]
2007-01-27  9:00 ` [Bug libgomp/30546] [4.2/4.3 regression] build fail in libgomp when building from SVN " fxcoudert at gcc dot gnu dot org
2007-01-27 10:06 ` dannysmith at users dot sourceforge dot net
2007-01-27 13:46 ` dfranke at gcc dot gnu dot org
2007-01-30  9:15 ` patchapp at dberlin dot org
2007-01-31 21:29 ` dfranke at gcc dot gnu dot org
2007-01-31 21:30 ` dfranke at gcc dot gnu dot org
2007-02-06 18:48 ` dfranke at gcc dot gnu dot org
2007-02-06 18:50 ` dfranke at gcc dot gnu dot org
2007-02-06 18:54 ` dfranke at gcc dot gnu dot org

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=20070127035254.5667.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).