Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3BB74762.4000506@ece.gatech.edu>
Date: Sun, 30 Sep 2001 12:25:06 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: binutils: auto-import, C++, STLport/SGI iostream
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

This message is primarily for Danny Smith:

In the binutils.README, there's a bug report from Danny that says:

>    "I am still having some (sorry, one very specific) problem
>    with C++ and auto-import.  It is with cerr, cin, cout in
>    the STLport of the SGI iostream lib.  These are initialised
>    before main.  When building dll with auto-export and using
>    auto-import to link (no dllimport attributes), I get
>    successful link, but runtime failure of app at initialisation
>    (before main). When building dll with --export-all, but
>    marking DATA with dllimport when compiling client, I get
>    successful link and run."


This was reported LONG ago, before the run-time problems with 
auto-importing multi-word variables was discovered, isolated, and 
addressed.  The currently distributed cygwin-binutils identifies these 
problem variables, and generates a link-time, rather than run-time error.

Danny: can you try again whatever procedure it was that caused the 
errors you described, but this time with a current binutils?  What happens?

My hypothesis: Danny's problems with SGLport/SGI iostream were *not 
"initialization before main" errors, but rather were "runtime error with 
auto-imported multi-word variable" errors.  If Danny STILL gets 
error-free linktime behavior but gets the runtime errors, then I'm 
wrong.  However, if I'm right, then Danny will see a "can't auto-import 
"cerr" ...." error message at link-time, and I can "close" his bug report.

Danny?

--Chuck





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/