From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb@sources.redhat.com
Subject: Re: po/POTFILES.in doesn't exist
Date: Tue, 07 Aug 2001 16:04:00 -0000 [thread overview]
Message-ID: <3B707412.9080906@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010729143812.3073B-100000@is>
> When I run the configure script, bfd/configure complains about
> po/POTFILES.in being absent. That's true: the file isn't there, since we
> now have SRC-POTFILES.in and BLD-POTFILES.in.
>
> Does that mean bfd/configure needs to be updated somehow? Do others see
> this error message?
FYI, I'm not seeing the message but that could be for many reasons.
Anyone else?
Andrew
next prev parent reply other threads:[~2001-08-07 16:04 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 [this message]
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
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=3B707412.9080906@cygnus.com \
--to=ac131313@cygnus.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