Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- compile error
January 14, 2011, 3:15 pm
rate this thread
I'm trying to compile the latest version of openssh, but keep
running into problems. This build if for a custom distro, so I'm
still in the process of learning - patience is required. :) Below I
have my compile options (that are run from a script) with the output
generated. Any help would greatly be appreciated.
./configure --build --with-ssl-dir=/usr/bin \
--with-tcp-wrappers --with-superuser-path=/users/root --with-pid-dir=/
--with-curses --disable-debugger \
--prefix="$STAGINGDIR" --exec-prefix="$STAGINGDIR" \
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type:
checking for -gcc... no
checking for gcc... gcc
configure: WARNING: In the future, Autoconf will not detect cross-
whose name does not start with the host triplet. If you think this
configuration is useful to you, please write to email@example.com.
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking build system type... configure: error: /bin/bash ./config.sub
configure: WARNING: Cache variable ac_cv_build contains a newline.
./compile.sh: line 48: --infodir=/opt/staging/package/var/help/info:
No such file or directory
I also wanted to add in the zlib option, but it failed with similar
results. Also, the final line in the output from above I don't quite
understand. I've triple checked that the directory mentioned *does*
exist, yet I still get the error!
- Nico Kadel-Garcia
January 19, 2011, 12:46 pm
Re: compile error
Slow down. "custom distro" of what? BSD, OpenBSD, RPM based Linux,
gentoo, CygWin? Give us a hint here.
Second. Stop restating STAGINGDIR everywhere. Once you've set --
prefix, the rest should be pretty consistently set.
Third. Why is "ssl-dir" set to "/usr/bin"? If you have a working SSL
installation, why isn't it "/usr"? That looks like where it exploded
Fourth. That "invalid-host-type" is a hint that your "custom distro"
is not recognized by autoconf, and *THAT* is going to be a problem
with anything else you compile that uses a "./configure" file. Have
you re-run "autoconf" to get a new ./configure file that might
accomodate your local setup?
Re: compile error
I'm building a custom distro of GNU/Linux (actually Busybox/Linux :)
for a specific purpose as well as gaining more knowledge of the OS at
the building level. At the present, it's a very basic system, but
coming along very nicely.
Noted. So should it look more like:
--prefix=3D"$STAGINGDIR" --exec-prefix=3D"$STAGINGDIR" \
So a /usr directory is a necessity of openSSH? Even with setting the
directory values via 'configure'?
I have noticed that error message when compiling several packages, but
other than just that message, nothing seems to be hindered. Also,
these packages are not being compiled on the custom distro, but a
working installation of Kubuntu. So if this is causing that problem,
autoconf can't reliably recognize a Debian based distro (unless I'm
doing something wrong - which could be the case).
Re: compile error
Also, looking at the /etc/ssh/sshd_config file, it seems to have
retained the --prefix value for the 'subsystem' option. I thought --
prefix was used by system package maintainers to compile the software
to a temp directory, package, and then delete. Can someone help me
understand this better? I am trying to compile and package openssh,
but when it's installed everything needs to be referenced without the
--prefix directory. Is there a way to do this easily (e.g. a variable
value or passed parameter during the compile stage)?
- » How to prompt for some information from PAM module
- — Previous thread in » Secure Shell Forum
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum