public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "d dot yu dot bolkhovityanov at inp dot nsk dot su" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/6728] compilation of gcc 3.1 fails - msgfmt
Date: Wed, 13 Oct 2004 06:53:00 -0000 [thread overview]
Message-ID: <20041013065341.27958.qmail@sourceware.org> (raw)
In-Reply-To: <20020519204601.6728.joseph@itgssi.com>
------- Additional Comments From d dot yu dot bolkhovityanov at inp dot nsk dot su 2004-10-13 06:53 -------
I've encountered the very same problem when trying to compile gcc-3.4 on
RedHat-7.3. The key to the problem is more obvious in Joseph's report than it
was in my case: /usr/openwin/bin/msgfmt -- OPENWIN!!! My system has
xview-clients RPM installed, which, among other things, contains "msgfmt"
binary, which is INCOMPATIBLE with regular "msgfmt" from gettext package.
The solution for a builder is to either exclude "/usr/openwin/bin" from the
$PATH, or to add it to the *end* of $PATH.
As for GCC compilation system -- it can be worth testing in "configure" which
kind of "msgfmt" is available, or to find where the "good" one is located.
Should the bug be reopened?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6728
next parent reply other threads:[~2004-10-13 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020519204601.6728.joseph@itgssi.com>
2004-10-13 6:53 ` d dot yu dot bolkhovityanov at inp dot nsk dot su [this message]
2004-10-13 11:24 ` [Bug bootstrap/6728] Add a configure test for msgfmt (it could be openwin's, not gettext's) giovannibajo at libero dot it
2004-11-06 17:20 ` pinskia 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=20041013065341.27958.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).