From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] spidev_test: new package
Date: Sat, 18 Oct 2014 23:08:26 +0300 [thread overview]
Message-ID: <20141018200826.GA2220@tarshish> (raw)
In-Reply-To: <20141017215539.GM3971@free.fr>
Hi Yann,
On Fri, Oct 17, 2014 at 11:55:39PM +0200, Yann E. MORIN wrote:
> On 2014-10-14 22:54 +0300, Baruch Siach spake thusly:
> > On Tue, Oct 14, 2014 at 12:45:53PM -0300, Gustavo Zacarias wrote:
> > > Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> >
> > [snip]
> >
> > > diff --git a/package/spidev_test/Config.in b/package/spidev_test/Config.in
> > > new file mode 100644
> > > index 0000000..c0ed9ef
> > > --- /dev/null
> > > +++ b/package/spidev_test/Config.in
> > > @@ -0,0 +1,15 @@
> > > +config BR2_PACKAGE_SPIDEV_TEST
> > > + bool "spidev_test"
> > > + depends on BR2_LINUX_KERNEL
> >
> > That is a heavy dependency. As you noted in another message, it also make the
> > autobuilder skip this package. I suggest to download just spidev_test.c from
> > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Documentation/spi/spidev_test.c?id=$(SPIDEV_TEST_VERSION),
> > and make it depend on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_15 (as of v3.17). This
>
> What about directly getting the appropriate one, something like:
>
> ifeq ($(BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_15),y)
> SPIDEV_TEST_VERSION = v3.15
> else
> SPIDEV_TEST_VERSION = v3.14
> endif
>
> SPIDEV_TEST_SOURCE =
> SPIDEV_TEST_EXTRA_DOWNLOADS = http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Documentation/spi/spidev_test.c?id=$(SPIDEV_TEST_VERSION)
>
> Since, without the proper kernel headers, it is not possible to build
> the quad-pump blabla, we can directly get the spidev_test that will
> indeed compile with our toolchain, no?
As Gustavo mentioned in another message in this thread, the newer spidev_test
is also run-time dependent on kernel v3.15 or newer. An automatic spidev_test
version choice would produce a broken binary for users of newer toolchains
with pre v3.15 kernels. We should use BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_15 to
disable build of v3.15 spidev_test, as this would break the build. But I don't
think we want to force v3.15 spidev_test just because the toolchain kernel
headers are post v3.15.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
prev parent reply other threads:[~2014-10-18 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 15:45 [Buildroot] [PATCH] spidev_test: new package Gustavo Zacarias
2014-10-14 17:29 ` Thomas De Schampheleire
2014-10-14 17:34 ` Gustavo Zacarias
2014-10-14 17:57 ` Ryan Barnett
2014-10-14 19:54 ` Baruch Siach
2014-10-14 19:56 ` Gustavo Zacarias
2014-10-14 20:09 ` Baruch Siach
2014-10-14 20:14 ` Thomas De Schampheleire
2014-10-14 20:18 ` Gustavo Zacarias
2014-10-14 20:19 ` Baruch Siach
2014-10-17 21:55 ` Yann E. MORIN
2014-10-18 20:08 ` Baruch Siach [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=20141018200826.GA2220@tarshish \
--to=baruch@tkos.co.il \
--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