From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] microperl compile fails for arm
Date: Sun, 16 Oct 2011 19:01:08 +0200 [thread overview]
Message-ID: <20111016170108.GC7761@tarshish> (raw)
In-Reply-To: <CAFo83mEZiX6BRzN+LY2XAstAqet=rOtQiWd1uv=aU2aCMnsvEg@mail.gmail.com>
Hi Jed,
On Sun, Oct 16, 2011 at 12:24:10PM -0400, Jed Evnull wrote:
> My compile is blowing up when it hits perl. I'm using qemu_arm as a base
> config. I dont see a log file but below is a fragment of where things start
> to go south. I'm running ubuntu 10.10. ??
[snip]
> test is in /usr/local/bin/test.
...
> Checking how to test for symbolic links...
> Your builtin 'test -h' may be broken.
> Trying external '/usr/local/bin/test -h'.
> External '/usr/local/bin/test -h' is broken, too.
So, what is this /usr/local/bin/test? Is it test(1) compatible?
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2011-10-16 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 16:24 [Buildroot] microperl compile fails for arm Jed Evnull
2011-10-16 17:01 ` Baruch Siach [this message]
2011-10-16 18:08 ` Jed Evnull
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=20111016170108.GC7761@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox