On 9/19/06, iwankoenig <[EMAIL PROTECTED]> wrote:

Hi!
I have compiled the openssl for a powerpc-processor with:
./Configure linux-ppc --prefix=/home/compile/openssl no-asm
make clean
make CC=powerpc-604-linux-gnu-gcc
make install

It works with no errors!
Now i have four directorys:
/home/compile/openssl/bin
/home/compile/openssl/include
/home/compile/openssl/lib
/home/compile/openssl/ssl

And now i have to put the compiled OpenSSL on embedded linux (with
powerpc-processor). How can i do this? Do i need a .iso-file of openssl?
Please help me!

Hi Ivan;

Where did you get your toolchain from?  Was it from another embedded project?

What you want to look at is how the *other* things on your embedded
device are packaged, if at all.  For example, the "ipkg" format is
quite common, and there's a scaffolding or framework to build them.

You might want to look into the buildroot (buildroot.org or
busybox.org) or the buildroot-ng (only from openwrt.org?) as
toolchain/packaging frameworks -- you can contribute ytour openssl
work there, and even if it turns out to be too big for others to use,
they might extend your work -- but you get the packaging system for
eaier install, if possible.

If your current embedded hardware is not an ipkg or similar packaging,
and you're building a rootdisk, then you might be able to install them
before building the rootdisk.

If you're not building your rootdisk, simply tar them up and untar in-situ

Much of the following steps are really dependent on how your PPC
device gets its packages and rootdisk, and it's really not an openssl
issue (unless you have build/config patches to give back) so let's
take this off the list, reply to me directly, I might be able to give
some advice.  Perhaps others here can also give some advice, but I
think it's best if it comes away from the openssl list.

Allan
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to