Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Scanned-By: AMaViS at pumpkin.vmfacility.fr From: "Ivan Warren" To: Subject: RE: getopt: ugly linker messages Date: Fri, 19 Sep 2003 20:51:51 +0200 Message-ID: <006601c37edf$16bba970$1411d0d4@vmfacility.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <20030919151803.GE17232@redhat.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h8JIq78W011076 > > I'm willing to do this but I have the same reservations that I think > you're expressing above, Chuck. Also, the auto-import of > data variables > is slower than a normal dllimport so I don't feel real > comfortable about > making this the default. > > I don't feel really strongly about this however, so if the > consensus is > that this should be turned on, I'll make a cygwin-specific change to > binutils. > > cgf And.. Hmmm.. I *think* auto import of data variables may be somewhat broken (and declared import of data variables too) if 1) The import library is stripped with --strip-unneeded and/or 2) The import is from another DLL (.exe -> .dll[func] -> .dll[data]) (See msg dated 9/17/03 which seems to have been drowned.. There is a test case in it) --Ivan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/