Chuck,
On Sun, Mar 15, 2009 at 03:05:37PM -0400, Charles Wilson wrote:
> Reini Urban wrote:
> > I hope that the frequent Vista unable to remap perl Cwd.dll errors
> > will be gone then, but I have not Vista to test.
>
> Using peflags to mark Cwd.dll with dynbase solves the problem for me.
> Now t
Reini Urban wrote:
> I hope that the frequent Vista unable to remap perl Cwd.dll errors will
> be gone then, but I have not Vista to test.
Using peflags to mark Cwd.dll with dynbase solves the problem for me.
Now that binutils' ld has a the capability to do this, and they have
decided on a comman
Dave Korn schrieb:
Marco Atzeri wrote:
I found a case where
CC="gcc-4 -shared-libgcc"
is absolutely needed
I suppose it is an exception handling issues, and it
Yes, anything that throws exceptions will need this.
I have come to the conclusion that it was probably a mistake on my pa
> I have come to the conclusion that it was probably a mistake on my part not
> to make shared libgcc default in this release. I will probably do a fairly
> rapid re-release to change this. (Might move to 4.3.3 while I'm doing it, and
> should I make -4 the default?)
I've used gcc-4 to compile
Marco Atzeri wrote:
> I found a case where
>
>CC="gcc-4 -shared-libgcc"
>
> is absolutely needed
> I suppose it is an exception handling issues, and it
Yes, anything that throws exceptions will need this.
I have come to the conclusion that it was probably a mistake on my part not
t
Hi All,
this is just an info for other mantainers and users
on gcc-4.3.2-2.
As reported by David announcment
http://cygwin.com/ml/cygwin/2009-03/msg00378.html
the current standard is "linked statically against libgcc".
I found a case where
CC="gcc-4 -shared-libgcc"
is absolutely needed and
6 matches
Mail list logo
