From: Lukas-David Gorris <lukas@htc-linux.org>
To: openembedded-devel@lists.openembedded.org
Subject: autoconf213: do_configure fails
Date: Sat, 12 Mar 2011 13:36:28 +0100 [thread overview]
Message-ID: <1299933388.3518.2.camel@computer> (raw)
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Build Configuration:
BB_VERSION = "1.12.0"
METADATA_BRANCH = "master"
METADATA_REVISION = "9dd12ec"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "htcleo"
DISTRO = "shr"
DISTRO_VERSION = "-20110312"
TARGET_FPU = "hard"
Log data follows:
| + do_configure
| + true
| + export ac_cv_path_PERL=/usr/bin/perl
| + ac_cv_path_PERL=/usr/bin/perl
| + export ac_cv_path_M4=/usr/bin/m4
| + ac_cv_path_M4=/usr/bin/m4
| + export ac_cv_prog_gnu_m4=yes
| + ac_cv_prog_gnu_m4=yes
| + sed -i '-es,^SUBDIRS = .*,SUBDIRS = bin .
lib,' /home/luke/linux/openembedded/tmp/work/armv7a-oe-linux-gnueabi/autoconf213-2.13-r13.0/autoconf-2.13/Makefile.am
| sed: can't
read /home/luke/linux/openembedded/tmp/work/armv7a-oe-linux-gnueabi/autoconf213-2.13-r13.0/autoconf-2.13/Makefile.am: No such file or directory
The same situation with autoconf213-native:
"Makefile.am: No such file or directory"
[-- Attachment #2: log.do_configure.3514 --]
[-- Type: text/plain, Size: 538 bytes --]
+ do_configure
+ true
+ export ac_cv_path_PERL=/usr/bin/perl
+ ac_cv_path_PERL=/usr/bin/perl
+ export ac_cv_path_M4=/usr/bin/m4
+ ac_cv_path_M4=/usr/bin/m4
+ export ac_cv_prog_gnu_m4=yes
+ ac_cv_prog_gnu_m4=yes
+ sed -i '-es,^SUBDIRS = .*,SUBDIRS = bin . lib,' /home/luke/linux/openembedded/tmp/work/armv7a-oe-linux-gnueabi/autoconf213-2.13-r13.0/autoconf-2.13/Makefile.am
sed: can't read /home/luke/linux/openembedded/tmp/work/armv7a-oe-linux-gnueabi/autoconf213-2.13-r13.0/autoconf-2.13/Makefile.am: No such file or directory
next reply other threads:[~2011-03-12 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 12:36 Lukas-David Gorris [this message]
2011-03-12 13:22 ` autoconf213: do_configure fails Lukas-David Gorris
2011-03-12 21:45 ` Lukas-David Gorris
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=1299933388.3518.2.camel@computer \
--to=lukas@htc-linux.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.