All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: openembedded-devel@openembedded.org
Subject: Re: Problem wt. perl-native building for PXA
Date: Tue, 22 May 2007 01:34:59 +0200	[thread overview]
Message-ID: <46522CA3.1010000@kernelconcepts.de> (raw)
In-Reply-To: <1179789619.5849.59.camel@localhost.localdomain>

Richard Purdie schrieb:
> Hi,
Hi!

> On Tue, 2007-05-22 at 01:05 +0200, Nils Faerber wrote:
>> I am encountering a strange problem while trying to build Angstrom for
>> PXA (for LinuxTag demo purposes). While we have some other machines
>> building it with the same version of OE and Bitbake just fine it fails
>> on my notebook (but I would like to be able to rebuild it directly at
>> LinuxTag, thus the question).
>> My machine has Ubuntu feisty installed. I am using Bitbake 1.8 from SVN
>> and an OE checkout from today.
>>
>> What happens is that the build works quite well until it comes to
>> perl-native-5.8.8-r7. There it fails with the following error:
> 
> I'm not familiar with the error but what does /bin/sh point at?
> 
> If its dash, try bash as dash causes no end of headaches.

Is tihs Ubuntu?
I did never recognise this, but you are perfectly right with your
assumption, sh -> dash.

Gee, hey look, now it works!!!
This dash thing should be tarred and feathered ;)

Many thanks!

> Cheers,
> Richard
Cheers
  nils faerber

-- 
kernel concepts GbR      Tel: +49-271-771091-12
Sieghuetter Hauptweg 48  Fax: +49-271-771091-19
D-57072 Siegen           Mob: +49-176-21024535
--



  reply	other threads:[~2007-05-21 23:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 23:05 Problem wt. perl-native building for PXA Nils Faerber
2007-05-21 23:20 ` Richard Purdie
2007-05-21 23:34   ` Nils Faerber [this message]
2007-05-24  2:35     ` Jamie Lenehan

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=46522CA3.1010000@kernelconcepts.de \
    --to=nils.faerber@kernelconcepts.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    --cc=rpurdie@rpsys.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 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.