Skip to contentSkip to conversation

openssl-native-1.0.0d-r14.0 compile fails

DISCUSSION A. Schallenberg 4 participants 6 messages Jun 21, 2011 – Jun 22, 2011

lore
Share & tools
lore
#0 lore 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"
Quoted 1 line

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

#1 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 5 lines · A. Schallenberg

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 when you're using a broken compiler to start with. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFOAJJoMkyGM64RGpERAhJxAJ0ZGDAHwG1Hz2/7PNhG4YDmEVev8ACePLQA +HsBNXLto955hWLJI7Nx+9Q=
=bFVs
-----END PGP SIGNATURE-----

#2 lore raw
In reply to A. Schallenberg
Quoted 21 lines · A. Schallenberg

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
Quoted 6 lines

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.

#3 lore raw

Hi,

Am Dienstag, 21. Juni 2011, um 14:49:20 schrieb Phil Blundell:

Quoted 7 lines

...
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?
...

Is this the directory in question?

Quoted 1 line

setup-scripts$ find sources/openembedded/recipes/openssl/

sources/openembedded/recipes/openssl/ sources/openembedded/recipes/openssl/ocf-linux_20100325.bb sources/openembedded/recipes/openssl/openssl.inc sources/openembedded/recipes/openssl/openssl-native_1.0.0d.bb sources/openembedded/recipes/openssl/openssl_0.9.8m.bb sources/openembedded/recipes/openssl/ocf-linux.inc sources/openembedded/recipes/openssl/openssl_1.0.0d.bb sources/openembedded/recipes/openssl/openssl-native_0.9.8m.bb sources/openembedded/recipes/openssl/openssl-1.0.0d sources/openembedded/recipes/openssl/openssl-1.0.0d/engines-install-in-libdir- ssl.patch sources/openembedded/recipes/openssl/openssl-1.0.0d/shared-libs.patch sources/openembedded/recipes/openssl/openssl-1.0.0d/oe-ldflags.patch sources/openembedded/recipes/openssl/openssl-1.0.0d/libdeps-first.patch sources/openembedded/recipes/openssl/openssl-1.0.0d/debian.patch sources/openembedded/recipes/openssl/openssl-1.0.0d/configure-targets.patch sources/openembedded/recipes/openssl/openssl-0.9.8m sources/openembedded/recipes/openssl/openssl-0.9.8m/shared-libs.patch sources/openembedded/recipes/openssl/openssl-0.9.8m/oe-ldflags.patch sources/openembedded/recipes/openssl/openssl-0.9.8m/Configure-nios2.patch sources/openembedded/recipes/openssl/openssl-0.9.8m/debian.patch sources/openembedded/recipes/openssl/openssl-0.9.8m/configure-targets.patch

Best,
Andreas

#4 lore raw
Quoted 37 lines · A. Schallenberg

Hi,

Am Dienstag, 21. Juni 2011, um 14:49:20 schrieb Phil Blundell:

Quoted 7 lines

...
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?
...

Is this the directory in question?

Quoted 1 line

setup-scripts$ find sources/openembedded/recipes/openssl/

sources/openembedded/recipes/openssl/ sources/openembedded/recipes/openssl/ocf-linux_20100325.bb sources/openembedded/recipes/openssl/openssl.inc sources/openembedded/recipes/openssl/openssl-native_1.0.0d.bb sources/openembedded/recipes/openssl/openssl_0.9.8m.bb sources/openembedded/recipes/openssl/ocf-linux.inc sources/openembedded/recipes/openssl/openssl_1.0.0d.bb sources/openembedded/recipes/openssl/openssl-native_0.9.8m.bb sources/openembedded/recipes/openssl/openssl-1.0.0d sources/openembedded/recipes/openssl/openssl-1.0.0d/engines-install-in-libdir- ssl.patch sources/openembedded/recipes/openssl/openssl-1.0.0d/shared-libs.patch sources/openembedded/recipes/openssl/openssl-1.0.0d/oe-ldflags.patch sources/openembedded/recipes/openssl/openssl-1.0.0d/libdeps-first.patch sources/openembedded/recipes/openssl/openssl-1.0.0d/debian.patch sources/openembedded/recipes/openssl/openssl-1.0.0d/configure-targets.patch sources/openembedded/recipes/openssl/openssl-0.9.8m sources/openembedded/recipes/openssl/openssl-0.9.8m/shared-libs.patch sources/openembedded/recipes/openssl/openssl-0.9.8m/oe-ldflags.patch sources/openembedded/recipes/openssl/openssl-0.9.8m/Configure-nios2.patch sources/openembedded/recipes/openssl/openssl-0.9.8m/debian.patch sources/openembedded/recipes/openssl/openssl-0.9.8m/configure-targets.patch

Quoted 2 lines

Best,
Andreas

No,

if you would have read the oe-manual, you would have found
that the workdir is TMPDIR(set in local.conf)/work/arch-tripple/recipename-version

Bye Henning

#5 lore raw
In reply to A. Schallenberg

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

Signature · 16 lines
Firmware developer
--------------------------------------------
FON:+49-(0)8233-78994-18
FAX:+49-(0)8233-78994-28
mailto:[email protected]
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