From: "A. Schallenberg" <embedded@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: openssl-native-1.0.0d-r14.0 compile fails
Date: Tue, 21 Jun 2011 14:32:22 +0200 [thread overview]
Message-ID: <201106211432.22700.embedded@gmx.net> (raw)
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 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?
Some additional information about the system:
Build Configuration:
BB_VERSION = "1.12.0"
METADATA_BRANCH = "master"
METADATA_REVISION = "1b9260e"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "beagleboard"
DISTRO = "angstrom"
DISTRO_VERSION = "v2011.06"
TARGET_FPU = "hard"
> arm-none-eabi-gcc -v
Using built-in specs.
COLLECT_GCC=arm-none-eabi-gcc
COLLECT_LTO_WRAPPER=/opt/arm-2011.03/bin/../libexec/gcc/arm-none-
eabi/4.5.2/lto-wrapper
Target: arm-none-eabi
...
Thread model: single
gcc version 4.5.2 (Sourcery G++ Lite 2011.03-42)
My ./build/conf/local.conf is:
-------------------------------------------------------
# Where to store sources
DL_DIR = "/home/aschallenberg/3wm-devel/manual-distro-build/setup-
scripts/sources/downloads"
INHERIT += "rm_work"
# Which files do we want to parse:
BBFILES ?= "/home/aschallenberg/3wm-devel/manual-distro-build/setup-
scripts/sources/openembedded/recipes/*/*.bb"
BBMASK = ""
# Qemu 0.12.x is giving too much problems recently (2010.05), so disable it
for users
ENABLE_BINARY_LOCALE_GENERATION = "0"
# What kind of images do we want?
IMAGE_FSTYPES += "tar.bz2"
# Make use of SMP:
# PARALLEL_MAKE specifies how many concurrent compiler threads are spawned
per bitbake process
# BB_NUMBER_THREADS specifies how many concurrent bitbake tasks will be run
PARALLEL_MAKE = "-j3"
BB_NUMBER_THREADS = "2"
#DISTRO = "angstrom-2011.3"
DISTRO = "angstrom-2010.x"
#DISTRO = "angstrom-2008.1"
MACHINE ?= "beagleboard"
# Set TMPDIR instead of defaulting it to /tmp
TMPDIR = "/home/aschallenberg/3wm-devel/manual-distro-build/setup-
scripts/build/tmp-angstrom_2011_3"
# Don't generate the mirror tarball for SCM repos, the snapshot is enough
BB_GENERATE_MIRROR_TARBALLS = "0"
# Go through the Firewall
#HTTP_PROXY = "http://:/"
IMAGE_PKGTYPE = "ipk"
----------------------------------------------------------
Best,
Andreas
next reply other threads:[~2011-06-21 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 12:32 A. Schallenberg [this message]
2011-06-21 12:45 ` openssl-native-1.0.0d-r14.0 compile fails 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
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=201106211432.22700.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.