Hello openssh-unix-dev, Some time ago I successfully compiled version 3.1 of OpenSSH. Today I tried new OpenSSH version and I am not able to compile it. Configuration script runned well. When running make, following error occured: make[1]: Entering directory `/tools/openssh-3.4p1/openbsd-compat' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/tools/openssh-3.4p1/openbsd-compat' gcc -o ssh ssh.o sshconnect.o sshconnect1.o sshconnect2.o sshtty.o readconf.o clientloop.o -L. -Lopenbsd-compat/ -L/usr/local/ssl/lib -lssh -lopenbsd-compat -lbsd -lz -lcrypto ./libssh.a(monitor_fdpass.o): In function `mm_send_fd': /tools/openssh-3.4p1/monitor_fdpass.c:54: undefined reference to `CMSG_FIRSTHDR' /tools/openssh-3.4p1/monitor_fdpass.c:58: undefined reference to `CMSG_DATA' ./libssh.a(monitor_fdpass.o): In function `mm_receive_fd': /tools/openssh-3.4p1/monitor_fdpass.c:114: undefined reference to `CMSG_FIRSTHDR' /tools/openssh-3.4p1/monitor_fdpass.c:118: undefined reference to `CMSG_DATA' collect2: ld returned 1 exit status make: *** [ssh] Error 1 Really don't know where the problem could be. Some info about comp: i386 Slackware linux Kernel 2.0.34 OpenSSL 0.9.6 egcs-2.90.29 980515 (egcs-1.0.3 release) libc 4.7.6 - don't know what other info can help you. -- Best regards, seth mailto:seth at kokos.cz
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've just sucessfully build RedHat 7.2 RPMs. (Does anyone wnat to upload them somewhere?) Looking up CMSG_FIRSTHDR I find it in /usr/include/bits/socket.h and /usr/include/linux/socket.h The former belongs to my glibc-devel package and the latter belongs to my kernel-headers package. Seeing "Kernel 2.0.34" in your systems configuration make me suspicious of your kernel headers but it could be the version of glibc you've got installed. You could try upgrading but both of these packages are *really* fundamental things that you should upgrade with care. Craig. seth at kokos.cz wrote:> Hello openssh-unix-dev, > > Some time ago I successfully compiled version 3.1 of OpenSSH. > Today I tried new OpenSSH version and I am not able to compile it. > Configuration script runned well. When running make, following error > occured: > > make[1]: Entering directory `/tools/openssh-3.4p1/openbsd-compat' > make[1]: Nothing to be done for `all'. > make[1]: Leaving directory `/tools/openssh-3.4p1/openbsd-compat' > gcc -o ssh ssh.o sshconnect.o sshconnect1.o sshconnect2.o sshtty.o readconf.o clientloop.o -L. -Lopenbsd-compat/ -L/usr/local/ssl/lib -lssh -lopenbsd-compat -lbsd -lz -lcrypto > ./libssh.a(monitor_fdpass.o): In function `mm_send_fd': > /tools/openssh-3.4p1/monitor_fdpass.c:54: undefined reference to `CMSG_FIRSTHDR' > /tools/openssh-3.4p1/monitor_fdpass.c:58: undefined reference to `CMSG_DATA' > ./libssh.a(monitor_fdpass.o): In function `mm_receive_fd': > /tools/openssh-3.4p1/monitor_fdpass.c:114: undefined reference to `CMSG_FIRSTHDR' > /tools/openssh-3.4p1/monitor_fdpass.c:118: undefined reference to `CMSG_DATA' > collect2: ld returned 1 exit status > make: *** [ssh] Error 1 > > Really don't know where the problem could be. > > Some info about comp: > i386 Slackware linux > Kernel 2.0.34 > OpenSSL 0.9.6 > egcs-2.90.29 980515 (egcs-1.0.3 release) > libc 4.7.6 > > - don't know what other info can help you. > > > >-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE9Gv+XBIRM2chQkvERAo0rAJ49FH/Mjp/ivKTKlxF/wkyi/L06/wCfYuhH gOCod8oU7k3jnnFRw6RrAQ8=q1Qf -----END PGP SIGNATURE-----
On Thu, Jun 27, 2002 at 01:51:13PM +0200, seth at kokos.cz wrote: | Hello openssh-unix-dev, | | Some time ago I successfully compiled version 3.1 of OpenSSH. | Today I tried new OpenSSH version and I am not able to compile it. | Configuration script runned well. When running make, following error | occured: | | make[1]: Entering directory `/tools/openssh-3.4p1/openbsd-compat' | make[1]: Nothing to be done for `all'. | make[1]: Leaving directory `/tools/openssh-3.4p1/openbsd-compat' | gcc -o ssh ssh.o sshconnect.o sshconnect1.o sshconnect2.o sshtty.o readconf.o clientloop.o -L. -Lopenbsd-compat/ -L/usr/local/ssl/lib -lssh -lopenbsd-compat -lbsd -lz -lcrypto | ./libssh.a(monitor_fdpass.o): In function `mm_send_fd': | /tools/openssh-3.4p1/monitor_fdpass.c:54: undefined reference to `CMSG_FIRSTHDR' | /tools/openssh-3.4p1/monitor_fdpass.c:58: undefined reference to `CMSG_DATA' | ./libssh.a(monitor_fdpass.o): In function `mm_receive_fd': | /tools/openssh-3.4p1/monitor_fdpass.c:114: undefined reference to `CMSG_FIRSTHDR' | /tools/openssh-3.4p1/monitor_fdpass.c:118: undefined reference to `CMSG_DATA' | collect2: ld returned 1 exit status | make: *** [ssh] Error 1 | | Really don't know where the problem could be. | | Some info about comp: | i386 Slackware linux Which specific Slackware? Too embarrassed to say? | Kernel 2.0.34 | OpenSSL 0.9.6 Which OpenSSL? 0.9.6a? 0.9.6b? 0.9.6c? 0.9.6d? | egcs-2.90.29 980515 (egcs-1.0.3 release) | libc 4.7.6 | | - don't know what other info can help you. How about telling me how long you're going to leave this machine running such an old system? Slackware 8.1 is out now. Be sure to get the "patches" directory, which includes OpenSSH 3.4p1. -- ----------------------------------------------------------------- | Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ | | phil-nospam at ipal.net | Texas, USA | http://phil.ipal.org/ | -----------------------------------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hiya, One of the other "issues" I came across with building RPMs was that I couldn't just do % rpm -tb SOURCES/openssh-3.4p1.tar.gz because the .spec file that was found was *not* the openssh-3.4p1/contrib/redhat/openssh.spec one. :-( I haven't checked but I guess rpm "grabs" the first one it finds in a tarball (which would have been openssh-3.4p1/contrib/caldera/openssh.spec). Now you may say "if a user can do rpm -tb ... they can figure this out" but this made me scratch my head for a while & I maintain RPMs for two SF.net projects. On the general note of who to trust binaries from, you're right. All the signature on the binaries I've produced proves is that *I'm* the guy who built it. It speaks naught to how trustable I am! :-) Now a process where people submit themselves to some kind of scrutiny (presumably to DJM as it's his key we're all trusting for the tarballs), & get their public keys a degree of "trust" might be a good start. Just my $0.02. :-) Craig. Christian Vogel wrote: > Hi, > > >>I've just sucessfully build RedHat 7.2 RPMs. > > > The question is if it is wise to grab such security > sensitive things like the ssh-server from just somewhere...? > > On the other hand it should be made very easy for people > to upgrade, and maybe some people don't want to rpm -ba/--rebuild > or don't even hava a compiler on their web/dns/... server? > > Is there some official policy encouraging<sp?> people > to contrinute binaries... or to refrain from it? > > Chris > (who just built RH7.1 i386.rpms... :-) ) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE9GxfFBIRM2chQkvERAo3CAKD7cXPOZ7oAS0tOWaIyvaz89XnskgCfYXfe 8l+yHWSEeAe2rIMig8VgpzQ=FxK5 -----END PGP SIGNATURE-----