Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3 02/15] directfb: mark as available only for gcc >= 4.5
Date: Thu, 10 Sep 2015 18:39:23 +0200	[thread overview]
Message-ID: <55F1B23B.7060609@mind.be> (raw)
In-Reply-To: <8737ymh3eb.fsf@dell.be.48ers.dk>

On 10-09-15 14:20, Peter Korsgaard wrote:
>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> 
>  > The new DirectFB version does not build with gcc 4.3 from the Blackfin
>  > toolchain. One of the reason is that va_copy has some issues, which
>  > were fixed in gcc 4.4.0
>  > (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36799). There are also
>  > some other issues, which were fixed by a patch proposed by Peter
>  > Seiderer at
>  > http://lists.busybox.net/pipermail/buildroot/2015-February/120281.html.
> 
>  > However, it probably doesn't make a lot of sense to carry patches that
>  > are not upstream for such old compilers. Instead, this commit takes
>  > the action of making DirectFB available only on toolchains using gcc
>  >> = 4.5, which was tested with the Arago toolchain. gcc 4.4 could
>  > potentially work, but wasn't tested (it is no longer supported by the
>  > internal toolchain backend, and we don't have any toolchain based on
>  > gcc 4.4), so we take the safe decision of requiring at least gcc 4.5.
> 
>  > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>  > ---
>  > This commit could be squashed into the DirectFB bump itself for
>  > bisectability, but was kept separate to ease the review.
> 
> Committed with the comments added as suggested by Vincente.
> 
>  > +++ b/package/gstreamer/gst-plugins-bad/Config.in
>  > @@ -263,6 +263,10 @@ config BR2_PACKAGE_GST_PLUGINS_BAD_PLUGIN_DIRECTFB
>  >  	select BR2_PACKAGE_DIRECTFB
>  >  	depends on BR2_TOOLCHAIN_HAS_THREADS
>  >  	depends on BR2_INSTALL_LIBSTDCPP
>  > +	depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_5
>  > +
>  > +comment "directfb needs a toolchain w/ C++, threads, gcc >= 4.5"
>  > +	depends on !BR2_TOOLCHAIN_HAS_THREADS || !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_GCC_AT_LEAST_4_5
> 
> Not directly related to this commit, but even though directfb is a
> library I think it makes more sense to use 'depends on' (and default y)
> for these options for "big libraries", as:
> 
> - People are likely to explicitly enable those libraroes if they want
>   them

 Well, except that there may be _programs_ that need that particular library.

 Except, as it turns out, in most cases we do already depend on directfb rather
than selecting it. The ones that do have a select (gstreamer and qt5) are
unlikely to have a program that needs that specific option.

> 
> - Gstreamer support size is insignificant compared to the library, and
>   people are likely to want E.G. directfb support in gstreamer if they
>   enable directfb and gstreamer, so the default y is nice
> 
> - We don't need to propagate the (often fairly complicated) library
>   dependencies to the users
> 
> This applies for E.G. wayland and Qt as well.

 For Qt it's already the case (cfr. grantlee). For wayland it's just the gst
plugin, where it indeed doesn't make sense to do it this way.


 Regards,
 Arnout

> 
> But that can (should) be handled outside this series.
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-09-10 16:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 22:01 [Buildroot] [PATCHv3 00/15] DirectFB stack bump Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 01/15] directfb: bump to 1.7.7 Thomas Petazzoni
2015-09-04 14:52   ` Vicente Olivert Riera
2015-09-04 16:11     ` Arnout Vandecappelle
2015-09-04 16:41       ` Vicente Olivert Riera
2015-09-01 22:01 ` [Buildroot] [PATCHv3 02/15] directfb: mark as available only for gcc >= 4.5 Thomas Petazzoni
2015-09-04 14:49   ` Vicente Olivert Riera
2015-09-10 12:20   ` Peter Korsgaard
2015-09-10 16:39     ` Arnout Vandecappelle [this message]
2015-09-11  6:57     ` Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 03/15] qt: fix directfb-1.7.7 compiler errors Thomas Petazzoni
2015-09-09 13:37   ` Vicente Olivert Riera
2015-09-09 13:47     ` Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 04/15] directfb: do not use inexistant configure options Thomas Petazzoni
2015-09-04 14:21   ` Vicente Olivert Riera
2015-09-04 14:41     ` Vicente Olivert Riera
2015-09-04 14:54       ` Vicente Olivert Riera
2015-09-01 22:01 ` [Buildroot] [PATCHv3 05/15] directfb: remove broken X.org support Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 06/15] directfb: remove BR2_PACKAGE_DIRECTFB_UNIQUE option Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 07/15] directfb: add options for divine and sawman Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 08/15] directfb: add new TIFF option Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 09/15] divine: remove package Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 10/15] sawman: " Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 11/15] linux-fusion: bump to 9.0.3, use .tar.xz Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 12/15] linux-fusion: use a more traditional style to define LINUX_FUSION_MAKE_OPTS Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 13/15] directfb-examples: remove options for each example Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 14/15] directfb-examples: do not install to staging Thomas Petazzoni
2015-09-01 22:01 ` [Buildroot] [PATCHv3 15/15] directfb-examples: bump to 1.7.0 Thomas Petazzoni
2015-09-10 12:20 ` [Buildroot] [PATCHv3 00/15] DirectFB stack bump Peter Korsgaard

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=55F1B23B.7060609@mind.be \
    --to=arnout@mind.be \
    --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