From: Mumit Khan <khan@xraylith.wisc.edu>
To: Donn Terry <donn@interix.com>
Cc: gas2@cygnus.com, bfd@cygnus.com
Subject: Re: PE patches available
Date: Mon, 12 Apr 1999 13:30:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.93.990412151550.700G-100000@modi.xraylith.wisc.edu> (raw)
In-Reply-To: <370CFDA7.36716C75@interix.com>
Hi Donn,
Ran into a few nits when building for Cygwin --
1. you mention that you've *put back* the .bss handling, but it's missing
from the post-patched ld/scripttempl/pe.sc. I just put it in my hand.
2. bfd/Makefile.in needs peigen.lo as target. Trivial obviously.
3. the $ENTRY in pe.sc expands to __mainCRTStartup, but Cygwin provides
_mainCRTStartup. Trivial to fix/make consistent of course.
The final executable doesn't work yet, but that I did expect. I'll do
some digging to see why it's not loading correctly (under Cygwin or
Mingw which uses MS runtime).
btw, I always thought that the Makefiles were setup to do the `make
headers' automatically in bfd. Guess not.
Regards,
Mumit
next prev parent reply other threads:[~1999-04-12 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-08 12:08 Donn Terry
1999-04-12 13:30 ` Mumit Khan [this message]
1999-04-13 8:26 ` Donn Terry
1999-04-13 18:20 ` Ian Lance Taylor
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=Pine.SUN.3.93.990412151550.700G-100000@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=bfd@cygnus.com \
--cc=donn@interix.com \
--cc=gas2@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).