"Gerrit P. Haase" wrote:
> perlTk and Ruby. I don't understand why perlTk doesn't has random base
> addresses, it should use ld2 as linker when building (but obviously it
> wasn't used).
The reported problem with perl/tk had nothing to do with the perl/tk
DLLs, it was a problem with cygz.dll nee
Gerrit P. Haase wrote:
Openssl uses a unique base address for libcrypto but not for libssl,
maybe both should use it? IMO important candidates are Apache/Apache2,
perlTk and Ruby. I don't understand why perlTk doesn't has random base
addresses, it should use ld2 as linker when building (but
Yitzchak Scott-Thoennes wrote:
On Mon, Dec 19, 2005 at 03:44:48AM -0800, Yitzchak Scott-Thoennes wrote:
It had sounded like there was consensus that -Wl,--enable-auto-image-base
should be used to build all dlls. Right now, we're a long way away from
that goal:
Should I have marked this in
On Mon, Dec 19, 2005 at 03:44:48AM -0800, Yitzchak Scott-Thoennes wrote:
> It had sounded like there was consensus that -Wl,--enable-auto-image-base
> should be used to build all dlls. Right now, we're a long way away from
> that goal:
Should I have marked this in the subject "Attention all maint
On Thu, Dec 22, 2005 at 04:20:51AM +0100, Gerrit P. Haase wrote:
> Yitzchak Scott-Thoennes wrote:
>
> >Gerrit P. Haase:
> > expat
> > freeglut
> > jasper
> > libcroco06
> > libdb4.2
> > libdb4.3
> > libexif10
> > openjade
> > OpenSP
>
> There are new DB, Expat
Yitzchak Scott-Thoennes wrote:
Gerrit P. Haase:
expat
freeglut
jasper
libcroco06
libdb4.2
libdb4.3
libexif10
openjade
OpenSP
There are new DB, Expat and OpenSP releases on the way, no need to
rebuild the older version IMO.
setup.ini says:
setup-timestamp: 1135015205
...
@ libjpeg62
sdesc: "A library for manipulating JPEG image format files (runtime)"
ldesc: "The jpeg package contains a library of functions for manipulating
JPEG images, as well as simple client programs for accessing the
libjpeg functions. Libjpeg c
