public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rearnsha@buzzard.freeserve.co.uk
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/10484: fastjar requires modern makeinfo
Date: Thu, 24 Apr 2003 19:36:00 -0000 [thread overview]
Message-ID: <200304241927.h3OJRdg18602@osprey.buzzard.freeserve.co.uk> (raw)
>Number: 10484
>Category: bootstrap
>Synopsis: fastjar requires modern makeinfo
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Apr 24 19:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Richard Earnshaw
>Release: 3.4 20030423 (experimental)
>Organization:
ARM
>Environment:
System: NetBSD osprey.buzzard.freeserve.co.uk 1.6P NetBSD 1.6P (OSPREY) #87: Sat Mar 15 00:03:40 GMT 2003 rearnsha@osprey.buzzard.freeserve.co.uk:/usr/src/sys/arch/cats/compile/OSPREY cats
host: arm-unknown-netbsdelf
build: arm-unknown-netbsdelf
target: arm-unknown-netbsdelf
configured with: /work/rearnsha/gnusrc/egcs/configure --prefix=/work/rearnsha/gnu/install --disable-checking arm-netbsdelf
>Description:
The Makefile in the fastjar directory now uses the --split-size
option, but this is not available in non-modern version of makeinfo.
Either the option should not be used, or configure should check for
a version of makeinfo that has this capability.
>How-To-Repeat:
Bootstrap gcc on a machine with an old version of makeinfo (eg 4.0)
>Fix:
Copy the code from gcc/configure.in into fastjar/configure.in that
checks the version of makeinfo.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2003-04-24 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 19:36 rearnsha [this message]
2003-04-24 19:46 Joseph S. Myers
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=200304241927.h3OJRdg18602@osprey.buzzard.freeserve.co.uk \
--to=rearnsha@buzzard.freeserve.co.uk \
--cc=gcc-gnats@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).