From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: openssl-native-1.0.0d-r14.0 compile fails
Date: Tue, 21 Jun 2011 13:49:20 +0100 [thread overview]
Message-ID: <1308660560.21613.16.camel@phil-desktop> (raw)
In-Reply-To: <201106211432.22700.embedded@gmx.net>
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 reply
> to his mail now.)
>
> Here is what I get:
>
> Log data follows:
> | + do_compile
> | + oe_runmake
> | + oenote make -e MAKEFLAGS=
> | + echo NOTE: 'make -e MAKEFLAGS='
> | NOTE: make -e MAKEFLAGS=
> | + make -e MAKEFLAGS=
> | make: *** No targets specified and no makefile found. Stop.
> | + die 'oe_runmake failed'
> | + oefatal 'oe_runmake failed'
> | + echo FATAL: 'oe_runmake failed'
> | FATAL: oe_runmake failed
> | + exit 1
> NOTE: package openssl-native-1.0.0d-r14.0: task do_compile: Failed
>
> I didn't find any Makefile that "touch"ing would make it compile.
>
> Has anybody an idea what I am doing wrong?
> Wrong toolchain? Wrong distro version selection?
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 code, or at least not the complete source code. What do you have
in the WORKDIR at that point?
p.
next prev parent reply other threads:[~2011-06-21 12:52 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 [this message]
2011-06-21 13:19 ` A. Schallenberg
2011-06-21 16:54 ` Henning Heinold
2011-06-22 7:51 ` A. Schallenberg
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=1308660560.21613.16.camel@phil-desktop \
--to=philb@gnu.org \
--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.