Prev: emlxs.conf and persistent binding
Next: what happened to "text file busy" ?
From: Jay G. Scott on 16 Nov 2006 15:01


i'm trying to compile and install openssh-4.4p1 on solaris 9.
the compile step goes fine, and it leaves me with good programs
or so it appears.

the compiler is:
oz# cc -V
cc: Sun WorkShop 6 update 2 C 5.3 Patch 111679-08 2002/05/09
usage: cc [ options] files. Use 'cc -flags' for details
oz# uname -a
SunOS oz 5.9 Generic_117171-15 sun4u sparc SUNW,Sun-Blade-100

the install program from:
fileutils-4.1
coreutils-5.2.1
and
install-sh -c
all, somehow put the file in place with this result:

oz# ldd /opt/depot/openssh-4.4p1/sbin/sshd
ldd: /opt/depot/openssh-4.4p1/sbin/sshd: file has insecure interpreter ELF

BEFORE it is installed:
oz# ldd sshd
libresolv.so.2 => /usr/lib/libresolv.so.2
libcrypto.so.0.9.8 => /opt/lib/libcrypto.so.0.9.8
librt.so.1 => /usr/lib/librt.so.1
libz.so.0 => /opt/lib/libz.so.0
libsocket.so.1 => /usr/lib/libsocket.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libc.so.1 => /usr/lib/libc.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libaio.so.1 => /usr/lib/libaio.so.1
libmd5.so.1 => /usr/lib/libmd5.so.1
libmp.so.2 => /usr/lib/libmp.so.2
/usr/platform/SUNW,Sun-Blade-100/lib/libc_psr.so.1
/usr/platform/SUNW,Sun-Blade-100/lib/libmd5_psr.so.1

so it's the install step which is doing it to me. /usr/sbin/install does NOT do that
to me, but it has other problems.

anybody know what's going on? sunsolve got me nowhere, and i didn't find the
answer with google.

j.
--
Jay Scott 512-835-3553 gl(a)arlut.utexas.edu
Head of Sun Support, Sr. Operating Systems Specialist
Applied Research Labs, Computer Science Div. S224
University of Texas at Austin
From: Oscar del Rio on 16 Nov 2006 15:45
Jay G. Scott wrote:
> the install program from:
> fileutils-4.1
> coreutils-5.2.1
> and
> install-sh -c
> all, somehow put the file in place with this result:
>
> oz# ldd /opt/depot/openssh-4.4p1/sbin/sshd
> ldd: /opt/depot/openssh-4.4p1/sbin/sshd: file has insecure interpreter ELF

ISTR some versions of GNU "strip" corrupting executables.
Is "install" stripping the executables before installing them?
From: Jay G. Scott on 16 Nov 2006 17:11
In article <ejiilq$1d0$1(a)news.mie>,
Oscar del Rio <delrio(a)mie.utoronto.ca> wrote:
>Jay G. Scott wrote:
>> the install program from:
>> fileutils-4.1
>> coreutils-5.2.1
>> and
>> install-sh -c
>> all, somehow put the file in place with this result:
>>
>> oz# ldd /opt/depot/openssh-4.4p1/sbin/sshd
>> ldd: /opt/depot/openssh-4.4p1/sbin/sshd: file has insecure interpreter ELF
>
>ISTR some versions of GNU "strip" corrupting executables.
>Is "install" stripping the executables before installing them?


this is my hypothesis, too. i finally thought of a way to
work around my problem. i set an INSTALL variable to point
to a script i wrote. it simply parroted its args to a file.
then i edited the file to use /usr/sbin/install (and some
other fixups).

however, install-sh -c, in theory, should change the command
to a "mv". however, that apparently didn't work, as:
1. the output files still lived in the build dir,
2. the install files (which come from the output files) were
corrupt.
i don't know what really happened.

i'm wondering if this is something peculiar to this compiler.
this is the first time i've encountered this, ever, and i've
been doing openssh and pals for three years at least. i've
never had to monkey with INSTALL before..... though, i guess
it's slowly dawning on me that perhaps now, i do.

j.
--
Jay Scott 512-835-3553 gl(a)arlut.utexas.edu
Head of Sun Support, Sr. Operating Systems Specialist
Applied Research Labs, Computer Science Div. S224
University of Texas at Austin
From: Gary Mills on 16 Nov 2006 18:40
In <ejinlp$24$1(a)ns3.arlut.utexas.edu> gl(a)csdsun1.arlut.utexas.edu (Jay G. Scott) writes:

>In article <ejiilq$1d0$1(a)news.mie>,
>Oscar del Rio <delrio(a)mie.utoronto.ca> wrote:
>>Jay G. Scott wrote:
>>> the install program from:
>>> fileutils-4.1
>>> coreutils-5.2.1
>>> and
>>> install-sh -c
>>> all, somehow put the file in place with this result:
>>>
>>> oz# ldd /opt/depot/openssh-4.4p1/sbin/sshd
>>> ldd: /opt/depot/openssh-4.4p1/sbin/sshd: file has insecure interpreter ELF
>>
>>ISTR some versions of GNU "strip" corrupting executables.
>>Is "install" stripping the executables before installing them?

>this is my hypothesis, too. i finally thought of a way to
>work around my problem. i set an INSTALL variable to point
>to a script i wrote. it simply parroted its args to a file.
>then i edited the file to use /usr/sbin/install (and some
>other fixups).

Setting INSTALL=/usr/ucb/install is a lot simpler. I've been
doing that for years.

--
-Gary Mills- -Unix Support- -U of M Academic Computing and Networking-
 | 
Pages: 1
Prev: emlxs.conf and persistent binding
Next: what happened to "text file busy" ?