From: Michael Elizabeth Chastain <mec@shout.net>
To: zack@codesourcery.com
Cc: binutils@sources.redhat.com, gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Status of gcc/intl and src/intl?
Date: Sat, 13 Sep 2003 02:22:00 -0000 [thread overview]
Message-ID: <200309130222.h8D2MCI5030218@duracef.shout.net> (raw)
Hi Zack,
I saw your message about an intl/ update:
http://sources.redhat.com/ml/binutils/2003-07/msg00032.html
Here's my story. Gdb has a build problem, PR gdb/857, which is about
intl/Makefile.in and the lack of a few files in the 'distclean' rule. I
started working on this and I noticed that gcc/intl is a lot newer than
src/intl.
My plan is to add a few lines of kludgery to the top level src-release
file and not touch src/intl/Makefile.in at all, on the grounds that
src/intl is about to get a big upgrade soon anyways. The specific
kludgery is a couple of lines like 'rm -f intl/config.cache' and 'rm -f
intl/stamp-h'. I think this will be benign if an upgrade happens.
I just wanna make sure that my plan is okay in light of whatever's
going on with src/intl these days. Can you comment on the status
of that?
Thanks,
Michael C
next reply other threads:[~2003-09-13 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 2:22 Michael Elizabeth Chastain [this message]
2003-09-14 0:33 ` Zack Weinberg
2003-09-14 17:17 Michael Elizabeth Chastain
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=200309130222.h8D2MCI5030218@duracef.shout.net \
--to=mec@shout.net \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=zack@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).