From: Alexandre Oliva <aoliva@redhat.com>
To: Alan Modra <amodra@bigpond.net.au>
Cc: Andrew Cagney <ac131313@cygnus.com>,
Daniel Jacobowitz <drow@mvista.com>,
Eli Zaretskii <eliz@is.elta.co.il>,
gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: po/POTFILES.in doesn't exist
Date: Tue, 02 Oct 2001 16:03:00 -0000 [thread overview]
Message-ID: <oritdxve64.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20011002232138.L1019@bubble.sa.bigpond.net.au>
On Oct 2, 2001, Alan Modra <amodra@bigpond.net.au> wrote:
>> > checking for xgettext... (cached) /usr/bin/xgettext
>> > ./configure: ./po/POTFILES.in: No such file or directory
> This tweak should fix it.
> * gettext.m4: Test po/POTFILES.in exists before trying to read.
> Anybody have any objections to installing this?
Erhm... IIRC, this file is imported from the GNU gettext
distribution, so I'd rather not needlessly diverge. Anyway, what's
the point of having a `po' directory if it doesn't contain
POTFILES.in?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2001-10-02 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-29 4:38 Eli Zaretskii
2001-08-07 16:04 ` Andrew Cagney
2001-08-07 16:11 ` Daniel Jacobowitz
2001-09-26 21:35 ` Andrew Cagney
2001-10-02 6:51 ` Alan Modra
2001-10-02 9:05 ` Andrew Cagney
2001-10-02 10:05 ` Eli Zaretskii
2001-10-14 11:49 ` [5.1] " Andrew Cagney
2001-10-20 18:32 ` Andrew Cagney
2001-11-12 14:06 ` Alexandre Oliva
2001-11-19 6:53 ` Andrew Cagney
2001-11-27 23:26 ` Andrew Cagney
2001-10-02 16:03 ` Alexandre Oliva [this message]
2001-10-02 18:44 ` Alan Modra
2001-10-02 20:25 ` Alexandre Oliva
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=oritdxve64.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=ac131313@cygnus.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.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