On Fri, Mar 15, 2002 at 07:43:43PM -0300, Alexandre Oliva wrote:
> Another possibility that occurred to me, that would further alleviate
> the problem of duplicate shared libraries, would be to get GCC to no
> longer issue the `-lgcc_s -lc -lgcc_s' sequence, but instead, to use
> just `-lgcc_s -lc
But then, wouldn't calling the project ``GNU Win'' or, even better,
``GNU Wins'', be a good thing? :-)
"GNU Win" might be a fine name for something else, but "gnuwin32"
where "win32" refers to the Microsoft system would not be good,
because it would be calling the Microsoft system a win.
Original note was talking about making technical feature which
applies to all targets using GNU compiler/linker/other utilities to
produce applications for set of systems (aka platform) officially
called 'Win32', and not about putting anything containing substring
'gnu-
An issue has recently been raised (by me) in the libtool mailing list
regarding the desirability of using the label "gnu-win32" in scripts
like libtool (and, I presume, configure).
In hacker terminology, calling something a "win" is a form of praise.
People who wish to praise Microsof
ct compiler and so I find myself answering fan mail...
I really hope this is going to change some lucky day.
Regards
-richy.
--
Richard Kreckel
<[EMAIL PROTECTED]>
<http://wwwthep.physik.uni-mainz.de/~kreckel/>
On Mon, May 15, 2000 at 01:00:29PM +0200, Jakub Jelinek wrote:
> What about using symbol version map?
> Say:
>
> MYPLUGIN {
> global:
> init_plugin; what__C9exception; ...
Incidentally, version maps do support
extern "C++" {
some_class::function
other_class::*
101 - 106 of 106 matches
Mail list logo
