Bob Friesenhahn wrote:
[]
Comments? Should pw32 be tracking Cygwin and MinGW in libtool rather
than being left behind?
Yes, please, if it's not hard, pw32 can follow the same sequence as mingw.
As for general point of removing (parts of) impgen.c, I cannot give
adequate answer as I don't h
I am Cc:ing the libtool list on this response, since there are
interested parties there.
On Wed, 23 Oct 2002, Paul Sokolovsky wrote:
> Bob Friesenhahn wrote:
> > Comments? Should pw32 be tracking Cygwin and MinGW in libtool rather
> > than being left behind?
>
> Yes, please, if it's not ha
On Tue, 22 Oct 2002, Robert Boehne wrote:
> I suppose that leaves one question (in my mind at least),
> and that is, What is pw32?
http://pw32.sourceforge.net/
The latest entry in the changelog is:
2002-08-03 Paul Sokolovsky [EMAIL PROTECTED]
* src/libc/dos/io/{posix2win32.c, win322p
I suppose that leaves one question (in my mind at least),
and that is, What is pw32?
Robert
Bob Friesenhahn wrote:
>
> On 22 Oct 2002, Elizabeth Barham wrote:
>
> >From what I understand, the newer gcc (and/or gnu ld) on win32 uses
> > an "auto import" feature, and the old way of importing
On 22 Oct 2002, Elizabeth Barham wrote:
>From what I understand, the newer gcc (and/or gnu ld) on win32 uses
> an "auto import" feature, and the old way of importing symbols (via
> compiling impgen.c) is no longer needed, although there was some
> platform that still uses the older method (pc3
Robert, Naofumi,
One of the things I am curious about is whether or not impgen.c is
going to be used very often in the future. I had been of the notion
that the latest set of patches more or less did away with the use of
that particular piece of code, although the code for impgen.c itself
has n
