Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: gdb@sources.redhat.com
Cc: Eli Zaretskii <eliz@is.elta.co.il>,
	amodra@bigpond.net.au, aoliva@redhat.com, drow@mvista.com
Subject: [5.1] Re: po/POTFILES.in doesn't exist
Date: Sun, 14 Oct 2001 11:49:00 -0000	[thread overview]
Message-ID: <3BC9DE01.2030609@cygnus.com> (raw)
In-Reply-To: <2593-Tue02Oct2001190537+0300-eliz@is.elta.co.il>

>> Date: Tue, 02 Oct 2001 12:05:03 -0400
>> From: Andrew Cagney <ac131313@cygnus.com>
>> 
>> Assuming it makes it into the trunk, does anyone have an opinion on 
>> committing it to the 5.1 branch?  On the up-side is that it eliminates 
>> the configure warning, on the down side, the warning didn't appear to do 
>> any harm any way.
> 
> 
> I generally think that something is very wrong when the configure
> script prints error messages.

Yes.  Er.  If anyone knows the correct tools / process to use to 
re-generate bfd's configure can they let me know.  I tried 
--enable-maintainer-mode using the 000227 auto* tools in the binutils 
ftp site and got the error:

gmake[1]: Entering directory `/home/scratch/51/gdb/native/bfd'
cd /home/scratch/51/gdb/src/bfd && aclocal
cd /home/scratch/51/gdb/src/bfd && automake --cygnus Makefile
cd /home/scratch/51/gdb/src/bfd && autoconf
configure.in:8: AC_TRY_COMPILE was called before AC_ISC_POSIX
configure.in:8: AC_TRY_RUN was called before AC_ISC_POSIX
autoconf: Undefined macros:
***BUG in Autoconf--please report*** AC_FD_MSG
***BUG in Autoconf--please report*** AC_FD_CC
***BUG in Autoconf--please report*** AC_FD_MSG
***BUG in Autoconf--please report*** AC_FD_MSG
***BUG in Autoconf--please report*** AC_FD_MSG
***BUG in Autoconf--please report*** AC_FD_MSG

Andrew

2001-10-03  Alan Modra  <amodra@bigpond.net.au>

     * gettext.m4: Test po/POTFILES.in exists before trying to read.


Index: gettext.m4
===================================================================
RCS file: /cvs/src/src/gettext.m4,v
retrieving revision 1.1
diff -u -p -r1.1 gettext.m4
--- gettext.m4	2000/08/31 09:25:11	1.1
+++ gettext.m4	2001/10/03 01:15:56
@@ -256,8 +256,8 @@ __argz_count __argz_stringify __argz_nex

     dnl Generate list of files to be processed by xgettext which will
     dnl be included in po/Makefile.  But only do this if the po directory
-   dnl exists in srcdir.
-   if test -d $srcdir/po; then
+   dnl exists in srcdir and contains POTFILES.in.
+   if test -f $srcdir/po/POTFILES.in; then
        test -d po || mkdir po
        if test "x$srcdir" != "x."; then
  	 if test "x`echo $srcdir | sed 's@/.*@@'`" = "x"; then






  reply	other threads:[~2001-10-14 11:49 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             ` Andrew Cagney [this message]
2001-10-20 18:32               ` [5.1] " 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=3BC9DE01.2030609@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=amodra@bigpond.net.au \
    --cc=aoliva@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