From: Christoph Fritz <chf.fritz@googlemail.com>
To: barebox@lists.infradead.org
Subject: [BUG] Fail to build: "cp: target `defaultenv/barebox_default_env.genenv.tmp' is not a directory"
Date: Mon, 28 Apr 2014 12:03:47 +0200 [thread overview]
Message-ID: <1398679427.7861.41.camel@mars> (raw)
Hi,
while building current Barebox, with out-of-tree make parameter O=,
there is an error which leads to lack of environment in final image. The
build process itself falsely doesn't get interrupted.
make -j$(nproc) ARCH=arm CROSS_COMPILE=arm-cortexa8-linux-gnueabihf- O=../o_beagle omap3530_beagle_defconfig
make -j$(nproc) ARCH=arm CROSS_COMPILE=arm-cortexa8-linux-gnueabihf- O=../o_beagle
CC drivers/of/mem_generic.o
ENV defaultenv/barebox_default_env
CC drivers/of/partition.o
cp: target `defaultenv/barebox_default_env.genenv.tmp' is not a directory
ENV defaultenv/defaultenv-2-base.bbenv
CC commands/automount.o
cp: target `defaultenv/defaultenv-2-base.bbenv.genenv.tmp' is not a directory
CC commands/global.o
in contrast to:
make -j$(nproc) ARCH=arm CROSS_COMPILE=arm-cortexa8-linux-gnueabihf- omap3530_beagle_defconfig
make -j$(nproc) ARCH=arm CROSS_COMPILE=arm-cortexa8-linux-gnueabihf-
AS arch/arm/lib/memcpy.o
LD arch/arm/mach-omap/built-in.o
ENV defaultenv/defaultenv-2-base.bbenv
PBLLD arch/arm/mach-omap/built-in-pbl.o
CC drivers/usb/core/usb.o
ENVH defaultenv/barebox_default_env.h
I haven't done bisecting, but barebox-2013.07 is fine.
Any ideas?
Thanks
-- Christoph
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-04-28 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 10:03 Christoph Fritz [this message]
2014-04-28 11:00 ` [BUG] Fail to build: "cp: target `defaultenv/barebox_default_env.genenv.tmp' is not a directory" Sascha Hauer
2014-04-28 12:29 ` [PATCH] genenv: fix tempdir creation when target is a relative path Christoph Fritz
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=1398679427.7861.41.camel@mars \
--to=chf.fritz@googlemail.com \
--cc=barebox@lists.infradead.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.