From: Ian Lance Taylor <ian@airs.com>
To: deo@logos-m.ru
Cc: binutils@sourceware.cygnus.com
Subject: Re: elf "note" section for win32-style thread context
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <19990510170556.20520.qmail@daffy.airs.com> (raw)
In-Reply-To: <7858.990510@logos-m.ru>
Date: Mon, 10 May 1999 20:36:31 +0400
From: Egor Duda <deo@logos-m.ru>
ILT> The prstatus_t stuff is all ELF specific, so you would have to copy it
ILT> anyhow for the PE-based cygwin code. The current implementation is
ILT> actually not quite right in that it relies on host header files, and
ILT> even if the right header files are available can not be built
ILT> correctly for a cross toolchain.
i'm not sure why? you mean that my changes will make cygwin depend on
bfd?
cygwin already depends upon BFD.
prstatus_t is used in bfd/elf.c, so it is ELF specific. That ELF code
is not used for the cygwin target.
Moreover, the code in bfd/elf.c depends upon having a host header file
which defines the prstatus_t struct. Therefore, it does not work when
the binutils are configured as a cross toolchain.
Ian
prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Egor Duda
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Re[2]: " Egor Duda
1999-07-01 0:00 ` Ian Lance Taylor [this message]
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=19990510170556.20520.qmail@daffy.airs.com \
--to=ian@airs.com \
--cc=binutils@sourceware.cygnus.com \
--cc=deo@logos-m.ru \
/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).