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: Re: Status of gcc/intl and src/intl?
Date: Sun, 14 Sep 2003 17:17:00 -0000 [thread overview]
Message-ID: <200309141717.h8EHHmCx026034@duracef.shout.net> (raw)
zw> Yeah. Updating src/intl to match gcc/intl is on my list but I am not
zw> going to get to it soon. ...
zw> What will happen eventually is, gcc/intl will be copied
zw> over to src/intl, and everyone's configure scripts will be modified to
zw> match.
Okay. That sounds normal. And it sounds like there is nothing hidden
that is going to leap up and bite me.
mec> My plan is to add a few lines of kludgery to the top level src-release
mec> file ...
zw> I'm not familiar with src-release so I have no idea whether this will
zw> be a problem.
I guess I can't ask you to know about src-release, so I will have to
be responsible for this bit. I'll make sure that my bits in src-release
look compatible with the gcc/intl/Makefile.in as well as the current
src/intl/Makefile.in.
zw> Testing this change is a bit daunting, which is one of the
zw> reasons I haven't gotten to it. Help would be appreciated.
I can do some garden variety cross builds, like gdb_mbuild.sh,
whenever the time is good for you. I'm not much on exotic builds though.
Thanks,
Michael C
next reply other threads:[~2003-09-14 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-14 17:17 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-13 2:22 Michael Elizabeth Chastain
2003-09-14 0:33 ` Zack Weinberg
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=200309141717.h8EHHmCx026034@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).