Cross-Compiling OpenSSH/OpenSSL

Cross-Compiling OpenSSH/OpenSSL

[rh-user]

Help! How do I compile OpenSSH/OpenSSL on one machine (running RH7.2) for use 
on another machine (running stripped RH6.2)? I'm trying to build a server, 
and don't want to load it up with things not needed like sources and 
development tools. Also, my user machine compiles a whole lot faster. But 
when I transfer the resulting binaries, they're expecting different library 
versions. Suggestions?

RE: Cross-Compiling OpenSSH/OpenSSL

[Kirkwood, David A]

Assuming the libraries are dynamic, and the revisions are close,
you can usually get by by making a link to the name required.

	suppose you used libxxx.so.1.2.3 for your compile
			     libxxx.so.1.2.2 is one the target system

	execute ln -s libxxx.so.1.2.2 libxxx.so.1.2.3
	
using a symbolic link keeps things so you can tell what the configuration
really is later.

dave

-----Original Message-----
From: rh-user@golden-home.net [mailto:rh-user@golden-home.net]
Sent: Friday, June 28, 2002 7:20 AM
To: linux-admin@vger.kernel.org
Subject: Cross-Compiling OpenSSH/OpenSSL


Help! How do I compile OpenSSH/OpenSSL on one machine (running RH7.2) for
use 
on another machine (running stripped RH6.2)? I'm trying to build a server, 
and don't want to load it up with things not needed like sources and 
development tools. Also, my user machine compiles a whole lot faster. But 
when I transfer the resulting binaries, they're expecting different library 
versions. Suggestions?
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Cross-Compiling OpenSSH/OpenSSL

[Glynn Clements]

rh-user@golden-home.net wrote:

> Help! How do I compile OpenSSH/OpenSSL on one machine (running RH7.2) for use 
> on another machine (running stripped RH6.2)? I'm trying to build a server, 
> and don't want to load it up with things not needed like sources and 
> development tools. Also, my user machine compiles a whole lot faster. But 
> when I transfer the resulting binaries, they're expecting different library 
> versions. Suggestions?

Copy the necessary libraries and their associated headers to their own
directories on the build system, then force them to be preferred over
the system versions, e.g. with

	CFLAGS='-I/path/to/headers'
	LDFLAGS='-L/path/to/libs -Wl,-rpath-link,/path/to/libs'
	export CFLAGS LDFLAGS
	./configure ....

If OpenSSH/OpenSSL don't use autoconf, you may need to modify the
Makefiles manually.

-- 
Glynn Clements <glynn.clements@virgin.net>

Re: Cross-Compiling OpenSSH/OpenSSL

[rh-user]

On Friday 28 June 2002 05:08 pm, Glynn Clements wrote:
> rh-user@golden-home.net wrote:
> > Help! How do I compile OpenSSH/OpenSSL on one machine (running RH7.2) for
> > use on another machine (running stripped RH6.2)? I'm trying to build a
> > server, and don't want to load it up with things not needed like sources
> > and development tools. Also, my user machine compiles a whole lot faster.
> > But when I transfer the resulting binaries, they're expecting different
> > library versions. Suggestions?
>
> Copy the necessary libraries and their associated headers to their own
> directories on the build system, then force them to be preferred over

	How do I go about getting the associated headers for the libraries? I didn't 
install any source or headers when I installed the server ...

Re: Cross-Compiling OpenSSH/OpenSSL

[Glynn Clements]

rh-user@golden-home.net wrote:

> > > Help! How do I compile OpenSSH/OpenSSL on one machine (running RH7.2) for
> > > use on another machine (running stripped RH6.2)? I'm trying to build a
> > > server, and don't want to load it up with things not needed like sources
> > > and development tools. Also, my user machine compiles a whole lot faster.
> > > But when I transfer the resulting binaries, they're expecting different
> > > library versions. Suggestions?
> >
> > Copy the necessary libraries and their associated headers to their own
> > directories on the build system, then force them to be preferred over
> 
> How do I go about getting the associated headers for the libraries? I didn't 
> install any source or headers when I installed the server ...

Either:

1. Install the appropriate -devel RPMs on the server, copy the files,
then uninstall the RPMs.

2. Convert the RPMs to cpio archives with rpm2cpio then extract the
files with cpio.

3. Install the -devel RPMs on the build host (you may need to
re-install the original versions afterwards).

In either case, note that the -devel RPMs include the unversioned
symlinks (or, in the case of glibc, the linker script) as well as the
headers. These are necessary for linking against the correct version
of the library.

-- 
Glynn Clements <glynn.clements@virgin.net>