Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
From: "Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To: "Cygwin-Apps" <cygwin-apps AT cygwin DOT com>
Subject: RE: libtool devel package still  dll crippled.
Date: Sun, 14 Apr 2002 15:27:31 +0200
Message-ID: <000301c1e3b8$2164db30$ea6007d5@BRAMSCHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <FC169E059D1A0442A04C40F86D9BA7600C5E39@itdomain003.itdomain.net.au>
Importance: Normal

> >   _LT_AC_TAGVAR(always_export_symbols, $1)=yes
> >
> > Using "yes" causes libtool to use nm to
> generate a symbol
> > list, which is avoided by setting to "no".
>
> Are the symbol tables identical in both cases?

If have done a short try (nm of the two import libs and
diff) with a little helper project and they are the same

> Would Danny's whole archive patch help the symbols?

May be, I haven't tried yet. Do I remember right, that this
patch isn't in the official binutils releases yet ?

> must be some way to prevent ld outputting the imported
symbols as
> well as the exported symbols...

I'm using a special patched ld (based on the recent official
ld) which rejects exporting of all imported libs with a one
line patch

binutils/ld/pe-dll.c:234
/* Do not specify library suffix explicitly, to allow for
dllized versions.  *
static autofilter_entry_type autofilter_liblist[] =
{
  { "libgcc.", 7 },
  { "libstdc++.", 10 },
  { "libmingw32.", 11 },
+// RH: workaround to allow using static libs in multiple
dlls
+  { ".a", 2 },
  { NULL, 0 }
};

Ralf