Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Arigead <captain.deadly@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Asterisk and termcap
Date: Thu, 09 Sep 2010 15:10:58 +0100	[thread overview]
Message-ID: <4C88EAF2.7010208@gmail.com> (raw)
In-Reply-To: <4C88E9BC.9040603@eukrea.com>

Eric Bénard wrote:
> Le 09/09/2010 15:57, Arigead a écrit :
>> Frans Meulenbroeks wrote:
>>> 2010/9/9 Denis 'GNUtoo' Carikli<GNUtoo@no-log.org>:
>>>> On Mon, 2010-09-06 at 16:15 +0100, Arigead wrote:
>>>>> was trying to build Asterisk for the OpenMoko Free runner and it
>>>>> failed
>>>>> on a dependency on termcap so I tried to bitbake termcap first and
>>>>> that
>>>>> failed. The termcap compile stage is working but it's when it tries to
>>>>> install that the recipe seems to fail but I'm new to this.
>>>>>
>>>>> I'm off to read the openembedded documentation again but in the mean
>>>>> time if anybody can give me a hit that would be great.
>>>> We can't help you if you don't post some logs or console output.
>>>> Copy-pasting the part where it fails, if it's small, could be enough
>>>> for
>>>> a start.
>>>> Denis.
>>>>
>>>>
>>> Denis, the message from Arigead is 3 days old and has already been
>>> dealt with.
>>> There is a patch for asterisk from Eric that makes it build fine for me.
>>>
>>> Frans.
>>>
>>
>> Yes sorry if my original post was too vague, but it was a known issue at
>> the time anyhow. As Frans says the patch was added and is in the feeds
>> and Asterisk is now building for my target device. Thanks for you help
>> and pointing out where the problem was.
>>
> OK so it means the patch solves your problem. Does asterisk runs fine on
> the target ?
> 
> Eric
> 

Sorry I'll have to get back to you on that one. I left my OpenMoko (The
Target) at home this morning so can't install the ipk :-(

Actually thinking about it I'd not be too sure if Asterisk was ever
running fine on a mobile phone. Simply wanted to play with it and see
what it could do. There is an OpenMoko wiki page on messing with it so
thought I'd have a look.

Anyhow I'll get back to you when I test it later today or tomorrow if
that's any help.




  reply	other threads:[~2010-09-09 14:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06 15:15 Asterisk and termcap Arigead
2010-09-09  1:33 ` Denis 'GNUtoo' Carikli
2010-09-09  6:20   ` Frans Meulenbroeks
2010-09-09 13:57     ` Arigead
2010-09-09 14:05       ` Eric Bénard
2010-09-09 14:10         ` Arigead [this message]
2010-09-09 14:15           ` Eric Bénard
2010-09-13 15:21             ` Arigead
2010-09-13 16:22               ` Frans Meulenbroeks
2010-09-13 17:17                 ` Henning Heinold
2010-09-13 17:41                 ` Gary Thomas
2010-09-11 22:25     ` Denis 'GNUtoo' Carikli

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=4C88EAF2.7010208@gmail.com \
    --to=captain.deadly@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox