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: <20010930203921.67129.qmail@web14508.mail.yahoo.com>
Date: Mon, 1 Oct 2001 06:39:21 +1000 (EST)
From: =?iso-8859-1?q?Danny=20Smith?= <danny_r_smith_2001 AT yahoo DOT co DOT nz>
Subject: Re: binutils: auto-import, C++, STLport/SGI iostream
To: Charles Wilson <cwilson AT ece DOT gatech DOT edu>, cygwin AT cygwin DOT com
In-Reply-To: <3BB74762.4000506@ece.gatech.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

 --- Charles Wilson <cwilson AT ece DOT gatech DOT edu> wrote: > 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
> 
> 
> 
And here was my analysis which I reported to binutils list:

http://sources.redhat.com/ml/binutils/2001-08/msg00083.html

I may have been wrong.  I'll look at I again to see if I get a
link-time error when I get acess to my home box. (Sorry my lap top only
has 3.0.x and CVS GCC on it and C++ dll's on that have different
problems). 

Danny

> 
> --
> 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/
>  

http://travel.yahoo.com.au - Yahoo! Travel
- Got Itchy feet? Get inspired!

--
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/