This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: [patch] ld: PE: comprehensive auto-filtering for DLL-exportable symbols
- To: binutils <binutils at sources dot redhat dot com>
- Subject: Re: [patch] ld: PE: comprehensive auto-filtering for DLL-exportable symbols
- From: Danny Smith <danny_r_smith_2001 at yahoo dot co dot nz>
- Date: Thu, 3 May 2001 07:53:30 +1000 (EST)
Re: [patch] ld: PE: comprehensive auto-filtering for DLL-exportable symbols
To: paul-ml at is dot lg dot ua
Subject: Re: [patch] ld: PE: comprehensive auto-filtering for DLL-exportable
symbols
From: DJ Delorie <dj at delorie dot com>
Date: Wed, 2 May 2001 08:51:22 -0400
CC: binutils at sources dot redhat dot com
References: <19664.010429@is.lg.ua>
--------------------------------------------------------------------------------
DJ Delorie wrote:
>> 3. Contextual filtering by containing library name (no need to export
>> anything coming from predefined libraries like libgcc or
>> libstdc++).
>I haven't looked at the patch yet, but question: what happens if you
>build a dll of libgcc.a itself?
As I understand, the default exclusion of symbols is only turned on if
(--export-all-symbols is given on command line)
||(there is no .def file && there are no declspecs in code).
The way I to build something like libgcc.dll.a would be to use a def file.
Then the default exclusion is a non-issue.
Danny
_____________________________________________________________________________
http://store.yahoo.com.au - Yahoo! Store
- It's time you had your business online!