public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "René Berber" <r.berber@computer.org>
To: cygwin@cygwin.com
Subject: Re: g++ linker problem with libcygwin.a
Date: Sun, 23 Oct 2011 17:53:00 -0000	[thread overview]
Message-ID: <j81k9k$r4s$1@dough.gmane.org> (raw)
In-Reply-To: <j80p0p$pd6$1@dough.gmane.org>

On 10/23/2011 5:07 AM, Philipp Kraus wrote:

> On 2011-10-23 01:28:37 +0200, René Berber said:
> 
>> I'm not sure why this static library is pulled.
> 
> yes *g* that my problem also. My cygwin g++ / ld
> links it automatically

Where it comes from? The compiler specs:

$ g++ -dumpspecs
...
*lib:
  %{pg:-lgmon}   %{!mno-cygwin:-lcygwin}  ...

Its always linked and needed, and it doesn't cause the "undefined
reference to _WinMain" problem in other compilations.

There must be something else that uses something that pulls _WinMain.

Perhaps looking at the link map will clarify what is going on:

	g++ -Wl,-M ... > link-map.txt
-- 
René Berber



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2011-10-23 17:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-22 19:19 Philipp Kraus
2011-10-22 20:17 ` René Berber
2011-10-22 20:37   ` Philipp Kraus
2011-10-22 21:44     ` René Berber
2011-10-22 22:49       ` Philipp Kraus
2011-10-22 23:29         ` René Berber
2011-10-22 23:37           ` René Berber
2011-10-23 10:38             ` Philipp Kraus
2011-10-23 10:07           ` Philipp Kraus
2011-10-23 17:53             ` René Berber [this message]
2011-10-23 17:58               ` René Berber
2014-03-17  1:57                 ` zosrothko
2014-03-17  2:28                   ` Marco Atzeri
2011-10-23 18:22 ` Csaba Raduly

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='j81k9k$r4s$1@dough.gmane.org' \
    --to=r.berber@computer.org \
    --cc=cygwin@cygwin.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).