From: Ian Lance Taylor <ian@airs.com>
To: dave@hiauly1.hia.nrc.ca
Cc: nickc@cygnus.com, binutils@sourceware.cygnus.com
Subject: Re: Duplicate symbols in recent cvs source
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <19990604181936.8577.qmail@daffy.airs.com> (raw)
In-Reply-To: <199906041814.OAA26216@hiauly1.hia.nrc.ca>
Date: Fri, 4 Jun 1999 14:14:11 -0400 (EDT)
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
I checked out the latest source and now there is another problem:
These problems are due to the symbol handling changes I checked in on
Wednesday. These particular ones should be fixed by Mark Klein's
patches which I just checked in.
Ian
next prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Nick Clifton
1999-07-01 0:00 ` John David Anglin
1999-07-01 0:00 ` Ian Lance Taylor [this message]
1999-07-01 0:00 ` John David Anglin
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
1999-07-01 0:00 John David Anglin
1999-07-01 0:00 Nick Clifton
[not found] <no.id>
1999-07-01 0:00 ` John David Anglin
1999-07-01 0:00 ` John David Anglin
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=19990604181936.8577.qmail@daffy.airs.com \
--to=ian@airs.com \
--cc=binutils@sourceware.cygnus.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=nickc@cygnus.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).