From: Dan Kegel <dank@kegel.com>
To: Dave Korn <dk@artimi.com>
Cc: binutils@sources.redhat.com
Subject: Re: cvs HEAD fails building bfd: msgfmt not found
Date: Tue, 04 May 2004 15:29:00 -0000 [thread overview]
Message-ID: <4097B662.9050805@kegel.com> (raw)
In-Reply-To: <NUTMEGM3SOlbpH71yEX00000160@NUTMEG.CAM.ARTIMI.COM>
Dave Korn wrote:
> Uptodate as of a few minutes ago, I got this error. Haven't seen it before,
> but there's lots of hits at
> http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=msgfmt+not+found
> which suggest that it's something to do with autoconf problem in
> configuring nls support. I'm about to try reconfiguring with --disable-nls
> and see if that solves the problem, but this level of autoconf internals is
> way over my head.
> ...
> msgfmt: not found
Um, did you try installing gnu gettext, which provides msgfmt?
- Dan
--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change
next prev parent reply other threads:[~2004-05-04 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 9:13 Dave Korn
2004-05-04 10:00 ` Dave Korn
2004-05-04 15:29 ` Dan Kegel [this message]
2004-05-04 16:30 ` Dave Korn
2004-05-04 21:50 ` Hans-Peter Nilsson
2004-05-05 9:36 ` Dave Korn
2004-05-05 2:54 ` Dan Kegel
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=4097B662.9050805@kegel.com \
--to=dank@kegel.com \
--cc=binutils@sources.redhat.com \
--cc=dk@artimi.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).