public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: jeffdb@goodnet.com
Cc: gas2@cygnus.com
Subject: Re: cygwin32 relocatable linking error?
Date: Sat, 06 Jun 1998 10:40:00 -0000	[thread overview]
Message-ID: <199806061740.NAA20444@subrogation.cygnus.com> (raw)
In-Reply-To: <3578bd4d.24745784@smtp.goodnet.com>

   From: jeffdbREMOVETHIS@goodnet.com (Mikey)
   Date: Sat, 06 Jun 1998 05:08:42 GMT

   shouldn't pe.sc have
   ${RELOCATING+ENTRY(_mainCRTStartup)}
   ?

   instead of just 
   ENTRY(_mainCRTStartup)

   otherwise ld -r puts an undefined _mainCRTStartup in every
   intermediate object file, which can mess up a final link
   if you are using _WinMainCRTStartup(), _DllMainCRTStartup or some other
   entry point.

Are you sure?  That does not happen when I try it.

The ENTRY keyword does not change the symbol table at all, nor does it
change which objects are included in the link.  It only affects the
setting of the entry point field in the internal a.out header.

Ian

      reply	other threads:[~1998-06-06 10:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-05 22:10 Mikey
1998-06-06 10:40 ` 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=199806061740.NAA20444@subrogation.cygnus.com \
    --to=ian@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=jeffdb@goodnet.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).