From: "Zack Weinberg" <zack@codesourcery.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: binutils@sources.redhat.com, gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: Status of gcc/intl and src/intl?
Date: Sun, 14 Sep 2003 00:33:00 -0000 [thread overview]
Message-ID: <878yosw6ny.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <200309130222.h8D2MCI5030218@duracef.shout.net> (Michael Elizabeth Chastain's message of "Fri, 12 Sep 2003 22:22:12 -0400")
Michael Elizabeth Chastain <mec@shout.net> writes:
> 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.
Yeah. Updating src/intl to match gcc/intl is on my list but I am not
going to get to it soon.
> 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'm not familiar with src-release so I have no idea whether this will
be a problem. What will happen eventually is, gcc/intl will be copied
over to src/intl, and everyone's configure scripts will be modified to
match. Testing this change is a bit daunting, which is one of the
reasons I haven't gotten to it. Help would be appreciated. (Note I
am moving, so I may not respond to mail in a timely fashion for the
next week or so.)
zw
next prev parent reply other threads:[~2003-09-14 0:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 2:22 Michael Elizabeth Chastain
2003-09-14 0:33 ` Zack Weinberg [this message]
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=878yosw6ny.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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