readline 32bit for Linux/64bit
Next problem. The Icarus Verilog simulation engine wants the readline package for the vvp program. If I'm gonna succeed at making a vvp32 for AMD64, I'm going to need readline-32bits and readline-32bits-devel packages. I'd be willing to have a go at this myself. Is there a standard way to do this? I'm thinking the way to do this is take the same readline source that the 64bit package uses, make a new .spec file that compiles it with -m32, and install only the bits that are not already installed by the 64bit readline. -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
On Thu, Oct 02, 2003 at 04:56:53PM -0700, Stephen Williams wrote:
Next problem. The Icarus Verilog simulation engine wants the readline package for the vvp program. If I'm gonna succeed at making a vvp32 for AMD64, I'm going to need readline-32bits and readline-32bits-devel packages. I'd be willing to have a go at this myself. Is there a standard way to do this?
On SLES8 libreadline.so.4.3 is offered by baselibs-32bit Maybe it will work with that version. -Andi
Hi, On Thu, 2 Oct 2003, Stephen Williams wrote:
Next problem. The Icarus Verilog simulation engine wants the readline package for the vvp program. If I'm gonna succeed at making a vvp32 for AMD64, I'm going to need readline-32bits and readline-32bits-devel packages. I'd be willing to have a go at this myself. Is there a standard way to do this?
Hmm, readline is a package already provided by SuSE. If you would go and make your own, it's likely that it will conflict with that one. The 32bit runtime version is already included in baselibs-32bit. You would only need the 32bit -devel rpm, and if you already have the (64 bit) readline-devel rpm installed (so that you already have all necessary headers), all you need is the .so link in /lib to make the linker find the library also in 32 bit mode. You would miss the static library, but that might be acceptable. I.e. all you probably have to do is install baselibs-32bit, and % cd /lib % ln -sf libreadline.so.4.3 libreadline.so % ln -sf libhistory.so.4.3 libhistory.so Ciao, Michael.
Michael Matz matz-at-suse.de |suse-amd64| wrote:
Hmm, readline is a package already provided by SuSE. If you would go and make your own, it's likely that it will conflict with that one. The 32bit runtime version is already included in baselibs-32bit. You would only need the 32bit -devel rpm, and if you already have the (64 bit) readline-devel rpm installed (so that you already have all necessary headers), all you need is the .so link in /lib to make the linker find the library also in 32 bit mode. You would miss the static library, but that might be acceptable.
I.e. all you probably have to do is install baselibs-32bit, and % cd /lib % ln -sf libreadline.so.4.3 libreadline.so % ln -sf libhistory.so.4.3 libhistory.so
Ah, so this smells like a bug in the packaging for baselibs-32bit. If the rpm were to add those links itself, all may be well. -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
Hi, On Mon, 6 Oct 2003, Stephen Williams wrote:
I.e. all you probably have to do is install baselibs-32bit, and % cd /lib % ln -sf libreadline.so.4.3 libreadline.so % ln -sf libhistory.so.4.3 libhistory.so
Ah, so this smells like a bug in the packaging for baselibs-32bit.
Not really. That package is intended as _runtime_ system, and for that the .so links are not required. It's not for actually building programs against it. For that a separate package (maybe named baselibs-32bit-devel) would be required, but that doesn't exist. I know, that this doesn't help you ;-| Ciao, Michael.
Michael Matz matz-at-suse.de |suse-amd64| wrote:
Hi,
On Mon, 6 Oct 2003, Stephen Williams wrote:
I.e. all you probably have to do is install baselibs-32bit, and % cd /lib % ln -sf libreadline.so.4.3 libreadline.so % ln -sf libhistory.so.4.3 libhistory.so
Ah, so this smells like a bug in the packaging for baselibs-32bit.
Not really. That package is intended as _runtime_ system, and for that the .so links are not required. It's not for actually building programs against it. For that a separate package (maybe named baselibs-32bit-devel) would be required, but that doesn't exist. I know, that this doesn't help you ;-|
I guess this means I can't really do what I'm trying to do here, which is to make a one-button build of bith 64bit and 32bit versions of the Icarus Verilog runtime for AMD64. The latter is intended for interfacing with third party i386 extensions. -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
Hi, On Mon, 6 Oct 2003, Stephen Williams wrote:
I guess this means I can't really do what I'm trying to do here, which is to make a one-button build of bith 64bit and 32bit versions of the Icarus Verilog runtime for AMD64. The latter is intended for interfacing with third party i386 extensions.
Well, theoretically you can even create those .so links on your own in a temporary directory during the build process. Something like: % cd <builddir> % mkdir libs32; cd libs32 % ln -sf /lib/libreadline.so.4.3 libreadline.so % cd <builddir>/some-program/ % gcc a.o b.o -o program -L<builddir>/libs32 -lreadline A bit ugly, but would probably work; as said those .so links are only required during build time itself (you have to be careful to not encode that tempdir <builddir>/libs32 as RPATH into the executable, if you use RPATHs at all). Ciao, Michael.
Not really. That package is intended as _runtime_ system, and for that the .so links are not required. It's not for actually building programs against it. For that a separate package (maybe named baselibs-32bit-devel) would be required, but that doesn't exist. I know, that this doesn't help you ;-|
They exist, but only in 9.0, not in SLES8. % rpm -qlp readline-devel-32bit.rpm /usr/lib/libhistory.a /usr/lib/libhistory.so /usr/lib/libreadline.a /usr/lib/libreadline.so % rpm -qip readline-devel-32bit.rpm Name : readline-devel-32bit Relocations: (not relocateable) Version : 9.0 Vendor: SuSE Linux AG, Nuernberg, Germany Release : 0 Build Date: Wed Sep 24 16:31:03 2003 Install date: (not installed) Build Host: Weber.suse.de Group : Development/Libraries/C and C++ Source RPM: baselibs-32bit-9.0-0.src.rpm Size : 608490 License: GPL Packager : http://www.suse.de/feedback Summary : The readline library link kit Sorry. For SLES8 you can only build them yourself for now as a workaround or copy them from a 32bit system. -Andi
* Andi Kleen
Not really. That package is intended as _runtime_ system, and for that the .so links are not required. It's not for actually building programs against it. For that a separate package (maybe named baselibs-32bit-devel) would be required, but that doesn't exist. I know, that this doesn't help you ;-|
They exist, but only in 9.0, not in SLES8.
% rpm -qlp readline-devel-32bit.rpm /usr/lib/libhistory.a /usr/lib/libhistory.so /usr/lib/libreadline.a /usr/lib/libreadline.so % rpm -qip readline-devel-32bit.rpm Name : readline-devel-32bit Relocations: (not relocateable) Version : 9.0 Vendor: SuSE Linux AG, Nuernberg, Germany Release : 0 Build Date: Wed Sep 24 16:31:03 2003 Install date: (not installed) Build Host: Weber.suse.de Group : Development/Libraries/C and C++ Source RPM: baselibs-32bit-9.0-0.src.rpm Size : 608490 License: GPL Packager : http://www.suse.de/feedback Summary : The readline library link kit
Sorry.
For SLES8 you can only build them yourself for now as a workaround or copy them from a 32bit system.
No, there is a devel_libs-32bit-packages on SLES8, that contains almost all .so-links and the static libs: stravinsky:~ # rpm -qlp /mounts/dist/sles8-x86_64/suse/i586/devel_libs-32bit.rpm |grep readline /usr/lib/libreadline.a /usr/lib/libreadline.so stravinsky:i~ # rpm -qlp /mounts/dist/sles8-x86_64/suse/i586/devel_libs-32bit.rpm |grep history /usr/lib/libhistory.a /usr/lib/libhistory.so stravinsky:~ # Sorry for not noticing this earlier.
-Andi
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
-Stefan -- Stefan Fent SUSE LINUX AG, Deutschherrnstr. 15-19, D-90429 N\374rnberg
Hi, On Tue, 7 Oct 2003, Stefan Fent wrote:
No, there is a devel_libs-32bit-packages on SLES8, that contains almost all .so-links and the static libs:
stravinsky:~ # rpm -qlp /mounts/dist/sles8-x86_64/suse/i586/devel_libs-32bit.rpm |grep readline /usr/lib/libreadline.a /usr/lib/libreadline.so
Oh. Wonderful. It seems we thought about everything ;-) That should solve Stephens problem. Ciao, Michael.
participants (4)
-
Andi Kleen -
Michael Matz -
Stefan Fent -
Stephen Williams