public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: Mailing List: CygWin-Apps <cygwin-apps@cygwin.com>
Subject: Re: GCC4 status.
Date: Thu, 26 Feb 2009 03:29:00 -0000	[thread overview]
Message-ID: <49A60C93.5060102@cwilson.fastmail.fm> (raw)
In-Reply-To: <20090225142128.GK18319@calimero.vinschen.de>

Corinna Vinschen wrote:
>   /usr/lib/gcc/i686-pc-cygwin/4.3.2/../../../../i686-pc-cygwin/bin/ld:
>   warning: auto-importing has been activated without --enable-auto-import
>   specified on the command line.
>   This should work unless it involves constant data structures referencing
>   symbols from auto-imported DLLs.
> 
>   *Sob*  Yes, officer, I confess everything!  But *please* don't tell
>   me this every time I dare to link an application.
> 
> Is there any chance to get rid of this really useless stuff upstream?

This is a binutils, not gcc, issue (unless you just want gcc's specs
file to automatically pass the option to ld.  But then, how does Bruno
turn it off, as he does, for gettext and libintl?  ld would see both
--enable (from specs) and --disable (from Bruno's cmdline -- but do we
guarantee which order specs-derived and cmdline-derived options are
delivered to ld?).  I think it's better to change cygwin-ld's default
behavior than to try to work around the warning in gcc's specs file.


Now, ld for pe[i]-386 already (as of 2008/11/24) defaults to
--enable-runtime-pseudo-reloc-v1.
http://sourceware.org/cgi-bin/cvsweb.cgi/src/ld/emultempl/pe.em.diff?r1=1.137&r2=1.138&cvsroot=src&f=h

This doesn't make much sense unless we also default to
--enable-auto-import, which is a one-line change to the same file at
line 148:

-link_info.pei386_auto_import = -1;
+link_info.pei386_auto_import = 1; /* default to enabled */

There might be pushback from other pe platforms, but changing the
default behavior for cygwin is in cgf's court.

--
Chuck

  parent reply	other threads:[~2009-02-26  3:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24  2:44 Dave Korn
2009-02-24  3:04 ` Dave Korn
2009-02-24  3:59 ` Yaakov (Cygwin/X)
2009-02-24  4:05   ` Dave Korn
2009-02-24  5:05     ` Charles Wilson
2009-02-24  5:18       ` Christopher Faylor
2009-02-24  5:27         ` Charles Wilson
2009-02-24  5:51           ` Christopher Faylor
2009-02-24  6:40             ` Yaakov (Cygwin/X)
2009-02-24  9:15           ` Corinna Vinschen
2009-02-24 16:35             ` Christopher Faylor
2009-02-24 16:53               ` Corinna Vinschen
2009-02-24 18:13                 ` Dave Korn
2009-02-25 14:21                   ` Corinna Vinschen
2009-02-25 17:21                     ` Dave Korn
2009-02-25 17:37                       ` Corinna Vinschen
2009-02-26  4:36                         ` Dave Korn
2009-02-26  5:05                           ` Danny Smith
2009-02-26  3:37                       ` Charles Wilson
2009-02-26  5:16                         ` Danny Smith
2009-02-26  5:36                           ` Charles Wilson
2009-02-26  5:58                             ` Dave Korn
2009-02-26  3:29                     ` Charles Wilson [this message]
2009-02-26  3:47                       ` Yaakov (Cygwin/X)
2009-02-26  3:54                         ` Charles Wilson
2009-02-26  4:23                           ` Dave Korn
2009-02-24 12:37       ` Dave Korn
2009-02-24 14:29         ` Charles Wilson
2009-02-24 14:41           ` Dave Korn
2009-02-24 16:12           ` Christopher Faylor

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=49A60C93.5060102@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --cc=cygwin-apps@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).