Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: "Шyvind Repvik" <nail@nslu2-linux.org>
Cc: Using the OpenEmbedded metadata to build Linux Distributions
	<openembedded-devel@lists.openembedded.org>
Subject: Re: DVB scan utility
Date: Mon, 4 Sep 2006 23:56:03 +0300	[thread overview]
Message-ID: <13210487720.20060904235603@gmail.com> (raw)
In-Reply-To: <44FC6D96.5030201@nslu2-linux.org>

Hello Øyvind,

Monday, September 4, 2006, 9:16:54 PM, you wrote:

> Mark Howells wrote:
>> Hi,
>>  
>> Can anyone point me toward an OE port (ideally OpenSlug/Slugos binary) of the linuxtv dvb 'scan' utility from HYPERLINK "http://www.linuxtv.org/downloads/linuxtv-dvb-apps-1.1.1.tar.gz"http://www.linuxtv.org/downloads/linuxtv-dvb-apps-1.1.1.tar.gz. I've tried creating a bb file to compile it, but the Makefile is old and seems only capable of compiling natively. I don't have a native compiler on my slug - I guess I could install it, but if anyone has a built binary or suitable BB/Make system it would help.

> The reason it compiles native binaries is simply that the Makefile 
> defines $CC as 'gcc'.

> Applying the included diff should help the Makefile work as it was 
> intended to do

   Likely, even better idea is to define EXTRA_OEMAKE and override
Makefiles vars there:

EXTRA_OEMAKE = "CC='${CC}'"

   Of course, I may be missing something and that might not work for
this package, but looking at the proposed diff, it may be a good idea
to try, if wasn't done.

> Regards,
> Øyvind Repvik
> SlugOS package manager



-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




      reply	other threads:[~2006-09-04 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04 17:37 DVB scan utility Mark Howells
2006-09-04 18:16 ` Øyvind Repvik
2006-09-04 20:56   ` Paul Sokolovsky [this message]

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=13210487720.20060904235603@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=nail@nslu2-linux.org \
    --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