Re: using --enable-auto-image-base
--- 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: [...] James R. Phillips: fftw3 lapack OK, I'll stipulate to that fact for fftw3. I'll get to fixing that real soon now. However, lapack is supposed to be linked with --enable-auto-image-base. If it isn't, there is something wrong with the makefile. I have put a half-hour of googling into trying to find out how to verify or discover the assigned base address of the dll (/usr/lib/lapack/cyglapack.dll). No luck. So, I give up. How do you discover this information? jrp
Re: using --enable-auto-image-base
On Fri, Dec 23, 2005 at 07:59:12AM -0800, James R. Phillips wrote: I have put a half-hour of googling into trying to find out how to verify or discover the assigned base address of the dll (/usr/lib/lapack/cyglapack.dll). No luck. So, I give up. How do you discover this information? Use objdump: $ objdump -p /usr/lib/lapack/cyglapack.dll | fgrep ImageBase ImageBase 1000 Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
Re: using --enable-auto-image-base
On Thu, Dec 22, 2005 at 07:55:06AM +0100, Gerrit P. Haase wrote: 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 the subject Attention all maintainers? I didn't want to do so not knowing for sure that the consensus was as above. It is default now in libtool to include this flag, so all packages using libtool will be transfered automatically (if the latest libtool is used) and I think that it is not that imortant to convert all older packages. Most frequently reported problems are with perl, python and other packages with lot of modules, also openssl was often a problem. 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 obviously it wasn't used). Perhaps he built it with an older release of perl?
Re: using --enable-auto-image-base
On Wed, Dec 21, 2005 at 11:06:59PM -0800, Brian Dessent wrote: 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 needing rebasing. Right, but Gerrit has perl set to build all module dlls with auto image base, yet the new perl-Tk distribution doesn't have it set.
Re: using --enable-auto-image-base
Brian Dessent wrote: 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 needing rebasing. The modules need rebasing or at least an auto-image-base anyway and I already saw the thread and added zlib to my 'important' listing: [EMAIL PROTECTED] Gerrit -- =^..^=
Re: using --enable-auto-image-base
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. I will do in case of DB if there are problems reported. Hmm, I'll take a look if there are newer releases of Exif, Jasper, Freeglut or Libcroco available. Openjade contains DLLs? Doesn't it use OpenSP as backend? Hmm, probably there will be an update once OpenSP is ready. Anyway, openjade is just an application, does anyone link to its library? -- =^..^=
Re: using --enable-auto-image-base
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 and OpenSP releases on the way, no need to rebuild the older version IMO. I will do in case of DB if there are problems reported. Hmm, I'll take a look if there are newer releases of Exif, Jasper, Freeglut or Libcroco available. Openjade contains DLLs? Doesn't it use OpenSP as backend? Hmm, probably there will be an update once OpenSP is ready. Anyway, openjade is just an application, does anyone link to its library? Further down you'll see openjade: usr/bin/cygogrove-0.dll usr/bin/cygospgrove-0.dll usr/bin/cygostyle-0.dll But if nothing uses the dlls, there's no problem :)
Re: using --enable-auto-image-base
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 maintainers? I didn't want to do so not knowing for sure that the consensus was as above.
Re: using --enable-auto-image-base
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 the subject Attention all maintainers? I didn't want to do so not knowing for sure that the consensus was as above. It is default now in libtool to include this flag, so all packages using libtool will be transfered automatically (if the latest libtool is used) and I think that it is not that imortant to convert all older packages. Most frequently reported problems are with perl, python and other packages with lot of modules, also openssl was often a problem. 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 obviously it wasn't used). Gerrit -- =^..^=
Re: using --enable-auto-image-base
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 obviously it wasn't used). And zlib! Gerrit -- =^..^=
Re: using --enable-auto-image-base
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 needing rebasing. Brian
