libhistory.so 32bit on SuSE9.2
On a 64bit machine, I compile Icarus Verilog vvp for 64bit *and* 32bit, the latter for compatibility with 32bit vpi code. But I cannot seem to find a 32bit libhistory.so? I think I remember having to hunt for it on SLES8 too. Why wasn't it just isntalled? The 64bit libhistory.so is present and functional. -- Steve Williams "The woods are lovely, dark and deep. steve at .......... But I have promises to keep, http://www........... and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
* Stephen Williams (1mc9i5i02@sneakemail.com) [20050118 17:27]:
On a 64bit machine, I compile Icarus Verilog vvp for 64bit *and* 32bit, the latter for compatibility with 32bit vpi code. But I cannot seem to find a 32bit libhistory.so? I think I remember having to hunt for it on SLES8 too. Why wasn't it just installed?
The libhistory.so is a symlink pointing to the actual library to use. As this link needs to be in /usr/lib for linker to find it, there can only be one present at a time. The only workaround I can think of is readjusting the symlink for the 32bit compile and changing it back afterwards, i.e. ln -sf /lib/libhistory.so.5 /usr/lib/libhistory.so <32bit compile> ln -sf /lib64/libhistory.so.5 /usr/lib/libhistory.so Philipp -- Philipp Thomas <pth@suse.de> Research & Development SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuremberg, Germany
Philipp Thomas pth-at-suse.de |suse-amd64| wrote:
* Stephen Williams (1mc9i5i02@sneakemail.com) [20050118 17:27]:
On a 64bit machine, I compile Icarus Verilog vvp for 64bit *and* 32bit, the latter for compatibility with 32bit vpi code. But I cannot seem to find a 32bit libhistory.so? I think I remember having to hunt for it on SLES8 too. Why wasn't it just installed?
The libhistory.so is a symlink pointing to the actual library to use. As this link needs to be in /usr/lib for linker to find it, there can only be one present at a time.
The only workaround I can think of is readjusting the symlink for the 32bit compile and changing it back afterwards, i.e.
ln -sf /lib/libhistory.so.5 /usr/lib/libhistory.so <32bit compile> ln -sf /lib64/libhistory.so.5 /usr/lib/libhistory.so
That makes no sense, as that is what the /usr/lib64 directory is for. And there is already a /usr/lib64/libhistory.so file there. I'm looking for the 32bit libhistory.so file to install in /usr/lib. It turns out that there is a /lib/libhistory.so.5, so maybe that's what I need and I wonder why the normal link is not picking it up? Perhaps I wasn't clear. I make seperate vvp binaries, a normal vvp and a vvp32. The latter obviously needs to link to 32bit versions of libraries. -- Steve Williams "The woods are lovely, dark and deep. steve at .......... But I have promises to keep, http://www........... and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
Hi Stephen, * Stephen Williams (1mc9i5i02@sneakemail.com) [20050118 19:08]:
That makes no sense
As I wrote in my answer to Robert, it indeed makes no sense.
It turns out that there is a /lib/libhistory.so.5, so maybe that's what I need and I wonder why the normal link is not picking it up?
No, what you need is the symlink /usr/lib/libhistory.so->/lib/libhistory.so.5 and like Robert wrote, readline-devel-32bit.rpm provides that. Philipp -- Philipp Thomas <pth@suse.de> Research & Development SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuremberg, Germany
On Tue, Jan 18, 2005 at 06:08:23PM +0100, Philipp Thomas wrote:
* Stephen Williams (1mc9i5i02@sneakemail.com) [20050118 17:27]:
On a 64bit machine, I compile Icarus Verilog vvp for 64bit *and* 32bit, the latter for compatibility with 32bit vpi code. But I cannot seem to find a 32bit libhistory.so? I think I remember having to hunt for it on SLES8 too. Why wasn't it just installed?
Just install readline-devel-32bit.
The libhistory.so is a symlink pointing to the actual library to use. As this link needs to be in /usr/lib for linker to find it, there can only be one present at a time.
Huh? The 64 bit libraries for AMD64 should be in /usr/lib64/, shouldn't they? Only the 32 bit libraries reside in /usr/lib/.
The only workaround I can think of is readjusting the symlink for the 32bit compile and changing it back afterwards, i.e.
ln -sf /lib/libhistory.so.5 /usr/lib/libhistory.so <32bit compile> ln -sf /lib64/libhistory.so.5 /usr/lib/libhistory.so
Are you sure you want to do that? Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
* Robert Schiele (rschiele@uni-mannheim.de) [20050118 19:14]:
On Tue, Jan 18, 2005 at 06:08:23PM +0100, Philipp Thomas wrote:
Huh? The 64 bit libraries for AMD64 should be in /usr/lib64/, shouldn't they? Only the 32 bit libraries reside in /usr/lib/.
Just forget the stuff I wrote, will you? My mind seems to have been somewhere else when I wrote that. Yes, libraries including the .so symlink are put in /usr/lib64 for 64bit and /usr/lib for 32bit. The only problem are the myriad configure fragments that know nothing of /lib64 and /usr/lib64 and thus pull in 32 bit libraries. But that's a different can of worms. Philipp -- Philipp Thomas <pth@suse.de> Research & Development SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuremberg, Germany
participants (3)
-
Philipp Thomas -
Robert Schiele -
Stephen Williams