Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-05-21
Date: Mon, 22 May 2017 23:54:14 +0200	[thread overview]
Message-ID: <20170522215414.GD6202@waldemar-brodkorb.de> (raw)
In-Reply-To: <20170522175415.pcy3uykh7ycoh42b@tarshish>

Hi Baruch,
Baruch Siach wrote,

> Hi Waldemar,
> 
> On Mon, May 22, 2017 at 06:22:55PM +0300, Baruch Siach wrote:
> > On Mon, May 22, 2017 at 04:14:28PM +0200, Waldemar Brodkorb wrote:
> > > take a look here:
> > > https://github.com/richfelker/musl-cross-make/blob/master/patches/gcc-6.3.0/0010-static-pie-support.diff
> > 
> > Thanks for the pointer.
> > 
> > I don't see this, or equivalent, patch in any gcc version that Buildroot 
> > supports. Is this the right fix to the cifs-utils build failure?
> > 
> > diff --git a/package/cifs-utils/cifs-utils.mk b/package/cifs-utils/cifs-utils.mk
> > index 152a3eeccf8a..ceedcf5de86f 100644
> > --- a/package/cifs-utils/cifs-utils.mk
> > +++ b/package/cifs-utils/cifs-utils.mk
> > @@ -12,6 +12,8 @@ CIFS_UTILS_LICENSE_FILES = COPYING
> >  
> >  ifeq ($(BR2_TOOLCHAIN_SUPPORTS_PIE),)
> >  CIFS_UTILS_CONF_OPTS += --disable-pie
> > +else ifeq ($(BR2_STATIC_LIBS),y)
> > +CIFS_UTILS_CONF_OPTS += --disable-pie
> >  endif
> >  
> >  ifeq ($(BR2_PACKAGE_KEYUTILS),y)
> 
> A more generic solution might be this, which is similar to what we do with 
> uClibc-ng toolchains:
> 
> diff --git a/toolchain/Config.in b/toolchain/Config.in
> index 652c9d8c1df4..6aaf68bf6547 100644
> --- a/toolchain/Config.in
> +++ b/toolchain/Config.in
> @@ -28,7 +28,7 @@ config BR2_TOOLCHAIN_USES_MUSL
>  	select BR2_TOOLCHAIN_HAS_THREADS
>  	select BR2_TOOLCHAIN_HAS_THREADS_DEBUG
>  	select BR2_TOOLCHAIN_HAS_THREADS_NPTL
> -	select BR2_TOOLCHAIN_SUPPORTS_PIE
> +	select BR2_TOOLCHAIN_SUPPORTS_PIE if !BR2_STATIC_LIBS
>  
>  choice
>  	prompt "Toolchain type"


You can add my Acked-By.

Best regards
 Waldemar

      reply	other threads:[~2017-05-22 21:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2017-05-21 Thomas Petazzoni
2017-05-22 12:07 ` Baruch Siach
2017-05-22 14:14   ` Waldemar Brodkorb
2017-05-22 15:22     ` Baruch Siach
2017-05-22 17:54       ` Baruch Siach
2017-05-22 21:54         ` Waldemar Brodkorb [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=20170522215414.GD6202@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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