Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: /usr/bin/fop ???
Date: Wed, 6 Oct 2010 16:50:51 +0200	[thread overview]
Message-ID: <20101006145051.GK3264@jama> (raw)
In-Reply-To: <4CAC8B19.9050502@gmail.com>

On Wed, Oct 06, 2010 at 03:43:37PM +0100, Arigead wrote:
> trying to "bitbake tangogps" and getting errors about /usr/bin/fop
> 
> I'm searching for a solution but not getting too far with that. I'm not
> sure why and embedded verison of tangogps would require Apache FOP but
> I'm on the wrong end of a learning curve.
> 
> Cheers for any pointers which would get me over this hurdle.

what about providing whole log.do_compile and log.do_configure to be
sure which recipe has this problem (I see libx11 in log, but you're
talking about tangogps).

Regards,
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com



  reply	other threads:[~2010-10-06 14:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 14:43 /usr/bin/fop ??? Arigead
2010-10-06 14:50 ` Martin Jansa [this message]
2010-10-06 15:00   ` Martin Jansa
2010-10-09  7:38     ` Arigead
2010-10-12 14:14       ` Arigead

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=20101006145051.GK3264@jama \
    --to=martin.jansa@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