From: "John R. Shannon" <john@johnrshannon.com>
To: gcc@gcc.gnu.org
Subject: Re: ACATS
Date: Thu, 29 Apr 2004 13:55:00 -0000 [thread overview]
Message-ID: <200404290619.45106.john@johnrshannon.com> (raw)
In-Reply-To: <NUTMEG6ufxNvHqvUoYv000000b6@NUTMEG.CAM.ARTIMI.COM>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm sorry, but I don't understand your reply.
On Thursday 29 April 2004 6:13 am, Dave Korn wrote:
> > -----Original Message-----
> > From: gcc-owner On Behalf Of John R. Shannon
> > Sent: 29 April 2004 13:09
> > To: gcc@gcc.gnu.org
> > Subject: ACATS
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Could someone please point me in the right direction in
> > chasing down undefined
> > references to `.LC124' and `.LC93' in gnatlink? Off-hand, I
> > don't see where
> > the references come from.
>
> --save-temps
>
> cheers,
> DaveK
- --
John R. Shannon
john@johnrshannon.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)
iEYEARECAAYFAkCQ8t8ACgkQOKbCxya4HYs1PwCfXHVUuvNXnWC4cqE4h2smyhFL
diQAnR/YySB97MPX8OfA4iUZFNoEmBsB
=xHem
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-04-29 12:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 13:12 ACATS John R. Shannon
2004-04-29 13:44 ` ACATS Dave Korn
2004-04-29 13:55 ` John R. Shannon [this message]
2004-04-29 14:10 ` ACATS Dave Korn
2004-04-29 17:11 ` ACATS John R. Shannon
2004-04-29 18:32 ` ACATS Dave Korn
2004-04-29 18:46 ` ACATS John R. Shannon
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 21:14 ACATS Richard Kenner
2004-04-30 1:48 ` ACATS Zack Weinberg
2004-05-03 20:39 ` ACATS Mark Mitchell
2004-04-29 20:55 ACATS Richard Kenner
2004-04-29 19:46 ACATS Richard Kenner
2004-04-29 20:46 ` ACATS John R. Shannon
2001-12-06 15:12 ACATS Richard Kenner
2001-12-06 15:08 ACATS Richard Kenner
2001-12-06 14:32 ACATS guerby
2001-12-06 15:00 ` ACATS Joseph S. Myers
2001-12-06 15:06 ` ACATS Florian Weimer
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=200404290619.45106.john@johnrshannon.com \
--to=john@johnrshannon.com \
--cc=gcc@gcc.gnu.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).