From: "A. Schallenberg" <embedded@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: openssl-native-1.0.0d-r14.0 compile fails
Date: Wed, 22 Jun 2011 09:51:18 +0200 [thread overview]
Message-ID: <201106220951.18472.embedded@gmx.net> (raw)
In-Reply-To: <201106211519.23045.embedded@gmx.net>
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.OS2
INSTALL.VMS
INSTALL.W32
INSTALL.W64
INSTALL.WCE
libcrypto.a
LICENSE
MacOS
Makefile
Makefile.org
Makefile.shared
makevms.com
ms
Netware
NEWS
openssl.doxy
openssl.ld
openssl.spec
os2
patches
perl
PROBLEMS
README
README.ASN1
README.ENGINE
shlib
ssl
test
times
tools
util
VMS
I tried "touch"ing this Makefile (like Robert suggested
on his mail on this list in March) but it didn't help.
So it seems that the files are downloaded and extracted.
The message
"make: *** No targets specified and no makefile found. Stop."
is a bit strange, since here is a Makefile.
Best,
Andreas
--
Firmware developer
--------------------------------------------
FON:+49-(0)8233-78994-18
FAX:+49-(0)8233-78994-28
mailto:Andreas.Schallenberg@3alitydigital.de
http://www.3alitydigital.de
--------------------------------------------
3ality Digital Systems GmbH
Gut Mergenthau
D-86438 Kissing / Bavaria / Germany
--------------------------------------------
Geschäftsführer/CEO: Steve Schklair
Sitz der Gesellschaft: Kissing
Registergericht Augsburg, HRB 16421
prev parent reply other threads:[~2011-06-22 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 12:32 openssl-native-1.0.0d-r14.0 compile fails A. Schallenberg
2011-06-21 12:45 ` Koen Kooi
2011-06-21 12:49 ` Phil Blundell
2011-06-21 13:19 ` A. Schallenberg
2011-06-21 16:54 ` Henning Heinold
2011-06-22 7:51 ` A. Schallenberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201106220951.18472.embedded@gmx.net \
--to=embedded@gmx.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.