public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47174] New: libquadmath: Build now depends on makeinfo
Date: Wed, 05 Jan 2011 08:51:00 -0000	[thread overview]
Message-ID: <bug-47174-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: libquadmath: Build now depends on makeinfo
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org


http://gcc.gnu.org/ml/fortran/2011-01/msg00012.html

libquadmath now fails to build if makeinfo isn't installed on the system:
[...]
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[3]: *** [libquadmath.info] Error 1


There is apparently a dependency on libquadmath.info via INFO_DEPS:

INFO_DEPS = libquadmath.info


> In what way is that different from, say, libgomp?
> IIUC makeinfo is required for the development tree.

libgomp doesn't fail to build in this configuration.  In fact, all components
used to build in this configuration (except maybe libjava) up to the patch.


             reply	other threads:[~2011-01-05  8:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05  8:51 burnus at gcc dot gnu.org [this message]
2011-01-06 19:30 ` [Bug fortran/47174] " rwild at gcc dot gnu.org
2011-01-06 22:26 ` rwild at gcc dot gnu.org
2011-01-06 22:38 ` rwild at gcc dot gnu.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=bug-47174-4@http.gcc.gnu.org/bugzilla/ \
    --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).