From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: [patch/rfc] Only use ../intl/ when present
Date: Tue, 18 Jan 2005 00:04:00 -0000 [thread overview]
Message-ID: <41EC520B.7060003@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 290 bytes --]
Hello,
This patch should stop getgext.m4 trying to use ../intl when it isn't
present.
I can't actually test it - all the systems I looked to test it on had a
bundled gettext :-/
comments?
Andrew
(I'll need to regenerate the binutils@ and gdb@ configure files, hence
the cross post.)
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 952 bytes --]
2005-01-17 Andrew Cagney <cagney@gnu.org>
* gettext.m4: Only fall back to ../intl/ when it's present.
Index: gettext.m4
===================================================================
RCS file: /cvs/src/src/gettext.m4,v
retrieving revision 1.3
diff -p -u -r1.3 gettext.m4
--- gettext.m4 14 Jan 2004 13:41:36 -0000 1.3
+++ gettext.m4 17 Jan 2005 23:56:17 -0000
@@ -81,9 +81,9 @@ AC_DEFUN([CY_WITH_NLS],
dnl In the standard gettext, we would now check for catgets.
dnl However, we never want to use catgets for our releases.
- if test "$CATOBJEXT" = "NONE"; then
- dnl Neither gettext nor catgets in included in the C library.
- dnl Fall back on GNU gettext library.
+ if test "$CATOBJEXT" = "NONE" && test -d $srcdir/../intl; then
+ # Neither gettext nor catgets in included in the C library.
+ # Fall back on GNU gettext library (assuming it is present).
nls_cv_use_gnu_gettext=yes
fi
fi
next reply other threads:[~2005-01-18 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 0:04 Andrew Cagney [this message]
2005-01-18 0:24 ` Andreas Schwab
2005-01-24 19:35 ` Andrew Cagney
2005-01-24 19:32 ` Andrew Cagney
2005-01-27 14:59 ` [commit] Avoid CATOBJEXT=NONE; Was: " Andrew Cagney
2005-01-27 20:40 ` Mark Kettenis
2005-01-31 21:22 ` [commit] Fix ENABLE_NLS; Was .... " Andrew Cagney
2005-01-31 21:46 ` Daniel Jacobowitz
2005-01-31 22:37 ` Andrew Cagney
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=41EC520B.7060003@gnu.org \
--to=cagney@gnu.org \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@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