libedit

[Ted Creedon]

configure works fine on a Suse 10.3 64 bit system but - strangely not an the
latest 11.1 64 bit

as a note pkg-config would solve both the include and lib flags problem -
but from what I can tell a new (and simpler) configure.ac wold be
required...

/usr/lib64/lib is a valid path - it just doesn't exist...

more later today

On Sun, Apr 5, 2009 at 11:01 AM, J.A. Neitzel <gsocsftp at v6shell.org> wrote:

> Ted Creedon <tcreedon at easystreet.net> wrote:
>
> > adding set -x to .configure reveals that --with-libedit=/usr/lib64 makes
> it
> > look for //usr/lib64/lib which is why it can't find el_init...
> >
> > As a general note it looks like configure needs to be rewritten to use
> > pkg-config...
> >
> > Its difficult to get a working ssh because configure doesn't clearly
> report
> > errors..
>
> Oh, I see...  This seems a strange problem since //usr/lib64/lib
> is a valid UNIX pathname.  Except for checking config.log when I
> need to, I have not done anything with the GNU Autotools since at
> least 2004.  So, this problem is rather out of my territory.
>
> I do not run the portable version on OpenBSD, but I do run it on
> NetBSD 4.0.1_PATCH amd64 and Mac OS X 10.5.x Intel.  In both cases,
> building with libedit support behaves as expected by doing a
> `./configure --with-libedit=/usr/lib'.
>
> For me, ./configure looks for /usr/lib, not //usr/lib .  This is
> reflected both in configure output and in config.log .
>
> So, could the problem you experience be a Suse Linux problem and
> not a configure problem?  Did you look at your config.log ?  Also,
> I am guessing that you are trying to build with a clean OpenSSH
> source tree (i.e., newly extracted or `make distclean').
>
> > On Sat, Apr 4, 2009 at 8:42 PM, J.A. Neitzel <gsocsftp at v6shell.org>
> wrote:
> >
> > > Ted Creedon <tcreedon at easystreet.net> wrote:
> > >
> > > > Moving s sccessful compole of 5.2.p1 from a Suse 10.3 x86-64 box to a
> > > Suse
> > > > 11.1 x86-box created a build problem
> > >
> > > I wonder what the result is if you build OpenSSH in 32-bit mode?
> > > The reason I wonder is because "x86-box" == "32-bit" in my world.
> > > Does your system run in 32-bit or 64-bit mode?
> > >
> > > > ./configure --with-libedit=/usr/lib64
> > > > checking for el_init in -ledit... no
> > > > configure: error: libedit not found
> > >
> > > So, what happens if you do a `./configure --with-libedit=/usr/lib'
> > > or a `./configure --with-libedit=/usr/lib32'?  I am rather guessing
> > > on the path since I do not know anything about Suse Linux.  Also,
> > > is LD_LIBRARY_PATH unset?  If not, what is it set to?
> > >
> > > > however libedit (amd el_init) certainly exist:
> > > >
> > > > ookpik:/data/openssh-5.2p1.test # l /usr/lib64/libedit*
> > > > lrwxrwxrwx 1 root root     17 Apr  4 17:11 /usr/lib64/libedit.so ->
> > > > libedit.so.0.0.27*
> > > > lrwxrwxrwx 1 root root     17 Apr  4 17:10 /usr/lib64/libedit.so.0 ->
> > > > libedit.so.0.0.27*
> > > > -rwxr-xr-x 1 root root 180568 Dec  3 02:50
> /usr/lib64/libedit.so.0.0.27*
> > > >
> > > > any clues?
> > >
> > > I dare not guess any more, as I may be stepping out of bounds.
> > > Hopefully, some of the preceding hints may prove useful.
> > >
> > > Jeff
>
> --
> J.A. Neitzel
> V6 Thompson Shell Port - http://v6shell.org/
>