From: "Zack Weinberg" <zack@codesourcery.com>
To: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org
Subject: RFC: Moving gcc/intl to toplevel; syncing both copies to 0.12.1
Date: Wed, 02 Jul 2003 17:07:00 -0000 [thread overview]
Message-ID: <877k70yi2t.fsf@codesourcery.com> (raw)
In the GCC CVS, the local copy of libintl lives in gcc/intl, and is a
slightly hacked version of gettext 0.10.40, which dates to 2000. In
the binutils/GDB CVS, the local copy of libintl lives in the top-level
intl directory, and dates to 1998; I do not see a version number
anywhere.
For entirely unrelated reasons I need to put the gcc libintl at the
top level. I think it would be a good idea to update both copies to
the latest upstream release, that is 0.12.1, at the same time. I will
need to rewrite the Makefile for that directory nearly from scratch,
and make drastic modifications to the configury, in order to support
building libintl in a directory that is _not_ a subdirectory of the
directory with the code that uses it. However, I expect that it will
not be necessary to modify the C source code at all.
I'd like to do this today, and commit to both gcc and src CVS
as soon as I've tested it; it is blocking another major change
over in gcc land, which needs to happen this week. Will this be
okay? Does anyone know a reason why upgrading to 0.12.1 is a bad idea?
zw
next reply other threads:[~2003-07-02 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 17:07 Zack Weinberg [this message]
2003-07-02 17:49 ` Andrew Cagney
2003-07-02 17:56 ` Zack Weinberg
2003-07-02 17:59 ` Phil Edwards
2003-07-03 16:01 ` 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=877k70yi2t.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
/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).