From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: automake/aclocal or env problem?
Date: Wed, 16 Sep 2009 12:17:23 +0200 [thread overview]
Message-ID: <4AB0BB33.7050304@dresearch.de> (raw)
We're using automake (1.10.2) on our target machine for rapid prototyping.
Calling "autoreconf --install" results in this error:
/usr/bin/env: perl -w: No such file or directory
autoreconf: aclocal failed with exit status: 127
An strace shows this:
[pid 1258] execve("/usr/local/bin/perl -w", ["perl -w", "/usr/bin/aclocal", "--output=aclocal.m4t"], [/* 15 vars */]) = -1 ENOENT (No such file or directory)
[pid 1258] execve("/usr/bin/perl -w", ["perl -w", "/usr/bin/aclocal", "--output=aclocal.m4t"], [/* 15 vars */]) = -1 ENOENT (No such file or directory)
[pid 1258] execve("/bin/perl -w", ["perl -w", "/usr/bin/aclocal", "--output=aclocal.m4t"], [/* 15 vars */]) = -1 ENOENT (No such file or directory)
[pid 1258] execve("/usr/local/sbin/perl -w", ["perl -w", "/usr/bin/aclocal", "--output=aclocal.m4t"], [/* 15 vars */]) = -1 ENOENT (No such file or directory)
[pid 1258] execve("/usr/sbin/perl -w", ["perl -w", "/usr/bin/aclocal", "--output=aclocal.m4t"], [/* 15 vars */]) = -1 ENOENT (No such file or directory)
[pid 1258] execve("/sbin/perl -w", ["perl -w", "/usr/bin/aclocal", "--output=aclocal.m4t"], [/* 15 vars */]) = -1 ENOENT (No such file or directory)
[pid 1258] execve("/opt/bin/perl -w", ["perl -w", "/usr/bin/aclocal", "--output=aclocal.m4t"], [/* 15 vars */]) = -1 ENOENT (No such file or directory)
[pid 1258] execve("/opt/avr/bin/perl -w", ["perl -w", "/usr/bin/aclocal", "--output=aclocal.m4t"], [/* 15 vars */]) = -1 ENOENT (No such file or directory)
[pid 1258] write(2, "/usr/bin/env: ", 14/usr/bin/env: ) = 14
[pid 1258] write(2, "perl -w", 7perl -w) = 7
[pid 1258] write(2, ": No such file or directory", 27: No such file or directory) = 27
[pid 1258] write(2, "\n", 1
My interpretation is that execve looks e.g. for an executable named "/usr/bin/perl -w" and not for "/usr/bin/perl" with option "-w". A look into /usr/bin/aclocal shows this shebang line:
#!/usr/bin/env perl -w
# -*- perl -*-
# Generated from aclocal.in; do not edit by hand.
I'm not sure if this is wrong or /usr/bin/env is buggy.
Steffen
PS: A few lines later /usr/bin/aclocal contains pathes into the staging area. This should be fixed too.
next reply other threads:[~2009-09-16 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 10:17 Steffen Sledz [this message]
2009-09-16 16:23 ` automake/aclocal or env problem? Stanislav Brabec
2009-09-17 21:59 ` Stanislav Brabec
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=4AB0BB33.7050304@dresearch.de \
--to=sledz@dresearch.de \
--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.