Re: Openssh shared library problem
On Fri, Jan 30, 2009 at 03:10:11PM +0100, Martin Koeppe wrote:
> interix everything is in /lib or /usr/lib, the default paths that
> ld.so uses. But 64-bit probably has different paths for the 32-bit
> stuff. I didn't test on 64-bit at all.
So the paths in ld.so are just hard coded?
> Did you happen to test with Rodney's sshd from interopsystems.com
> if that one has the same problem? Or if not, you may find out, how
> Rodney did it?
> Or you try to put symlinks in /lib/ pointing to the real libc.so.3.5.
> As there are no .so files on 64-bit, the names shouldn't clash.
> This should be necessary only for the system .so files, as the
> debian-interix stuff will get installed into /lib or /usr/lib
> automatically (even if that is probably "wrong" on 64-bit).
Good call on the different library path for 32 bit. I think the
symlink answer might be the best. Perhaps the links could be placed
in a meta package for 64 bit users?
> > So, I was attempting to comment back the line is session.c and
> > rebuild, but I wasn't even able to do a build from the deb source
> > before running into a number of issues, including this header
> > related one from configure during the dpkg-buildpackage of openssh.
> >checking dirent.h presence... yes
> >configure: WARNING: dirent.h: present but cannot be compiled
> >configure: WARNING: dirent.h: check for missing prerequisite headers?
> >configure: WARNING: dirent.h: see the Autoconf documentation
> I did all my builds on a 32-bit system, more precisely on SFU 3.5, for
> best compatibility. Maybe you can setup a chroot environment with all
> the SFU 3.5 stuff in it and build within that. I successfully do
> that on Vista 32-bit.
This would require a 32-bit XP Pro system for 3.5 to install on to
gather the chroot files? Or can I just extract the install files
manually from that the 3.5 32bit SUA package?
Paul Holcomb *pholcomb \@ cpoint net*
GPG key fingerprint 2B62 05AE EE74 845A 705F D716 28C4 FE1C 088F CFAC