From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org
Subject: -emit-relocs (fwd)
Date: Mon, 03 Dec 2001 22:19:00 -0000 [thread overview]
Message-ID: <23900000.1007446483@warlock.codesourcery.com> (raw)
---------- Forwarded Message ----------
Date: Monday, December 03, 2001 06:06:17 PM -0800
From: Matt <matt@use.net>
To: "mark@codesourcery.com" <mark@codesourcery.com>
Subject: -emit-relocs
ORBS still hasn't removed my host, so I can't post this to the gcc list.
Can you forward this for me? Thanks.
---------- Forwarded message ----------
Date: Mon, 3 Dec 2001 17:54:24 -0800 (PST)
From: Matt <matt@use.net>
To: gcc@gcc.gnu.org
Subject: -emit-relocs
Hi,
I'm attempting to use Purify on cygwin generated binaries and need to
generated a .reloc section for it to work properly. It seems like
--emit-relocs would be the answer, but doesn't appear to be working
properly in gcc 2.95.3 that is included with Cygwin.
Can someone please give me step-by-step instructions for compiling a foo.c
test file with .reloc sections?
Any help is appreciated,
Thanks.
--
http://www.clock.org/~matt
---------- End Forwarded Message ----------
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
reply other threads:[~2001-12-04 6:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=23900000.1007446483@warlock.codesourcery.com \
--to=mark@codesourcery.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).