From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libhdhomerun: new package
Date: Sun, 13 Dec 2015 14:43:10 +0100 [thread overview]
Message-ID: <e890kcx3eu.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20151213120353.GG2318@tarshish
Hi Baruch,
Am Sun, 13 Dec 2015 14:03:53 +0200 schrieb Baruch Siach:
> Hi Bernd,
>
> On Sun, Dec 13, 2015 at 12:47:11PM +0100, Bernd Kuhls wrote:
>> Am Sun, 13 Dec 2015 13:33:42 +0200 schrieb Baruch Siach:
>> >
>> > Are you sure this is not for staging?
>>
>> yes, because it is not a script but a binary compiled for the target:
>>
>> $ file /home/bernd/buildroot/br2_kodi16/output/target/usr/bin/
>> hdhomerun_config
>> /home/bernd/buildroot/br2_kodi16/output/target/usr/bin/
hdhomerun_config:
>> ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically
>> linked, interpreter /lib/ld64-uClibc.so.0, not stripped
>
> This most likely matches your host. Is that your target as well?
coincidentally yes, here is the arm version:
$ file /home/bernd/buildroot/br2_kodi16/output/target/usr/bin/
hdhomerun_config
/home/bernd/buildroot/br2_kodi16/output/target/usr/bin/hdhomerun_config:
ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically
linked, interpreter /lib/ld-uClibc.so.0, not stripped
>> I am not sure whether the file is really needed on the target or not
>> but it is definitely not suited for staging.
>
> Agreed. But is this file really intended for target use? Most library
> *_config files are only useful during build. What is the purpose of
> hdhomerun_config?
Honestly I do not know, so I sent v2 of my patch:
http://patchwork.ozlabs.org/patch/556182/
If someone misses hdhomerun_config a follow-up patch is needed ;)
Regards, Bernd
next prev parent reply other threads:[~2015-12-13 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 10:58 [Buildroot] [PATCH 1/1] package/libhdhomerun: new package Bernd Kuhls
2015-12-13 11:33 ` Baruch Siach
2015-12-13 11:47 ` Bernd Kuhls
2015-12-13 12:03 ` Baruch Siach
2015-12-13 13:43 ` Bernd Kuhls [this message]
2015-12-13 18:59 ` Baruch Siach
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=e890kcx3eu.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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