Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/6] libselinux: bump to version 2.5
Date: Fri, 24 Jun 2016 09:38:05 +0200	[thread overview]
Message-ID: <20160624093805.6793ed48@free-electrons.com> (raw)
In-Reply-To: <1466736201-17310-5-git-send-email-Aduskett@gmail.com>

Hello,

On Thu, 23 Jun 2016 22:43:20 -0400, Adam Duskett wrote:

> diff --git a/package/libselinux/Config.in b/package/libselinux/Config.in
> index bc8298d..af4d759 100644
> --- a/package/libselinux/Config.in
> +++ b/package/libselinux/Config.in
> @@ -6,6 +6,8 @@ config BR2_PACKAGE_LIBSELINUX
>  	depends on !BR2_STATIC_LIBS
>  	# Toolchain issue: "fixup not contained within frag"
>  	depends on !BR2_arc
> +   # Newer versions of libselinux won't compile against glibc 2.22.

Indentation must be done with one tab here.

> +	depends on !BR2_GLIBC_VERSION_2_22

What is the issue you're facing with glibc 2.22 ?

Adding a depends on !BR2_GLIBC_VERSION_2_22 is not possible, because
this symbol only makes sense when you're using the internal toolchain
mechanism (i.e when Buildroot builds the toolchain for you). When
you're using an external toolchain, this symbol has no meaning, so you
might very well have BR2_GLIBC_VERSION_2_22 disabled, but still have a
glibc 2.22 based external toolchain.

So I'd rather understand what is the build failure, and see if it can
be fixed.

>  	help
>  	  libselinux is the runtime SELinux library that provides
>  	  interfaces (e.g. library functions for the SELinux kernel
> @@ -17,6 +19,9 @@ config BR2_PACKAGE_LIBSELINUX
>  
>  	  http://selinuxproject.org/page/Main_Page
>  
> -comment "libselinux needs a toolchain w/ threads, dynamic library"
> +comment "libselinux needs a toolchain w/ threads, dynamic library, glibc version != 2.22"
>  	depends on !BR2_arc
> -	depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS
> +	depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS || BR2_GLIBC_VERSION_2_22
> +
> +
> +

Unnecessary line additions.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-06-24  7:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24  2:43 [Buildroot] [PATCH 1/1] Add libselinux and libsepol dependency for SELinux support Adam Duskett
2016-06-24  2:43 ` [Buildroot] [PATCH 2/6] Audit: bump to version 2.5.2 Adam Duskett
2016-06-24  2:43 ` [Buildroot] [PATCH 3/6] checkpolicy: bump to version 2.5 Adam Duskett
2016-06-24  2:43 ` [Buildroot] [PATCH 4/6] libsepol: " Adam Duskett
2016-06-24  7:36   ` Thomas Petazzoni
2016-06-24  2:43 ` [Buildroot] [PATCH 5/6] libselinux: " Adam Duskett
2016-06-24  7:38   ` Thomas Petazzoni [this message]
2016-06-24  2:43 ` [Buildroot] [PATCH 6/6] libsemanage: " Adam Duskett
2016-06-24  8:02   ` Thomas Petazzoni
2016-06-24  7:46 ` [Buildroot] [PATCH 1/1] Add libselinux and libsepol dependency for SELinux support Thomas Petazzoni

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=20160624093805.6793ed48@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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