Hello,
thank you, Henning, for pointing me to the correct directory.
Its contents are:
openssl-1.0.0d> ls
ACKNOWLEDGMENTS
apps
bugs
certs
CHANGES
CHANGES.SSLeay
config
Configure
crypto
demos
doc
engines
e_os2.h
e_os.h
FAQ
include
INSTALL
install.com
INSTALL.DJGPP
INSTALL.MacOS
INSTALL.NW
INSTALL.
On Tue, Jun 21, 2011 at 03:19:22PM +0200, A. Schallenberg wrote:
> Hi,
>
> Am Dienstag, 21. Juni 2011, um 14:49:20 schrieb Phil Blundell:
> > ...
> > It isn't likely that your choice of toolchain is causing this problem,
> > since the package in question is a -native one. From the error you
> > p
Hi,
Am Dienstag, 21. Juni 2011, um 14:49:20 schrieb Phil Blundell:
> ...
> It isn't likely that your choice of toolchain is causing this problem,
> since the package in question is a -native one. From the error you
> pasted it looks as though the recipe has simply failed to unpack any
> source co
On Tue, 2011-06-21 at 14:32 +0200, A. Schallenberg wrote:
> I tried to compile Angstrom (which is based on openembedded).
> Unfortunately it fails with a message that is very similar to the
> one Robert Schuster reported on 07 Mar 2011.
> (Since I wasn't subscribed to this list back then I cannot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21-06-11 14:32, A. Schallenberg wrote:
> Hello,
>
> I tried to compile Angstrom (which is based on openembedded).
> gcc version 4.5.2 (Sourcery G++ Lite 2011.03-42)
That's not angstrom, that's a harry potter toolchain, don't file bug
reports wh
Hello,
I tried to compile Angstrom (which is based on openembedded).
Unfortunately it fails with a message that is very similar to the
one Robert Schuster reported on 07 Mar 2011.
(Since I wasn't subscribed to this list back then I cannot reply
to his mail now.)
Here is what I get:
Log data fol
