All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/aespipe: fix host compile
Date: Sat, 17 Dec 2016 08:56:46 +0100	[thread overview]
Message-ID: <87r3579ef5.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20161217071659.3975-2-bernd.kuhls@t-online.de> (Bernd Kuhls's message of "Sat, 17 Dec 2016 08:16:59 +0100")

>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:

 > Building host-aespipe fails on
 > $ cat /etc/debian_version
 > stretch/sid

 > at linking stage:

 > /usr/bin/gcc -L/home/buildroot/br6/output/host/lib
 > -L/home/buildroot/br6/output/host/usr/lib
 > -Wl,-rpath,/home/buildroot/br6/output/host/usr/lib -o aespipe
 > aespipe.o aes-amd64.o md5-amd64.o md5-2x-amd64.o aes-intel64.o
 > sha512.o rmd160.o
 > /usr/bin/ld: aes-amd64.o: relocation R_X86_64_32S against `.rodata'
 > can not be used when making a shared object; recompile with -fPIC

 > Fix is also used in Debian:
 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837393

Ahh, so we will start to see various fallout of them enabling -fPIE by
default?

If it happends to a lot of packages, then I think we should do it
globally in HOST_CFLAGS / HOST_LDFLAGS, but I have committed this for
now after adding a comment explaining why, thanks.


 > Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
 > ---
 >  package/aespipe/aespipe.mk | 4 ++++
 >  1 file changed, 4 insertions(+)

 > diff --git a/package/aespipe/aespipe.mk b/package/aespipe/aespipe.mk
 > index 6a38556..3a95469 100644
 > --- a/package/aespipe/aespipe.mk
 > +++ b/package/aespipe/aespipe.mk
 > @@ -9,5 +9,9 @@ AESPIPE_SOURCE = aespipe-v$(AESPIPE_VERSION).tar.bz2
 >  AESPIPE_SITE = http://loop-aes.sourceforge.net/aespipe
 >  AESPIPE_LICENSE = GPL
 
 > +HOST_AESPIPE_CONF_ENV = \
 > +	CFLAGS="$(HOST_CFLAGS) -no-pie" \
 > +	LDFLAGS="$(HOST_LDFLAGS) -no-pie"
 > +
 >  $(eval $(autotools-package))
 >  $(eval $(host-autotools-package))
 > -- 
 > 2.10.2

 > _______________________________________________
 > buildroot mailing list
 > buildroot at busybox.net
 > http://lists.busybox.net/mailman/listinfo/buildroot

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2016-12-17  7:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-17  7:16 [Buildroot] [PATCH 1/2] package/aespipe: bump version to 2.4d Bernd Kuhls
2016-12-17  7:16 ` [Buildroot] [PATCH 2/2] package/aespipe: fix host compile Bernd Kuhls
2016-12-17  7:56   ` Peter Korsgaard [this message]
2016-12-17 14:59   ` Thomas Petazzoni
2016-12-17 16:55     ` Peter Korsgaard
2017-05-28 15:32       ` Bernd Kuhls
2016-12-17  7:42 ` [Buildroot] [PATCH 1/2] package/aespipe: bump version to 2.4d Peter Korsgaard
2017-07-03  8:41 [Buildroot] [PATCH 1/2] package/Makefile.in: add host-cc-option macro Arnout Vandecappelle
2017-07-03  8:41 ` [Buildroot] [PATCH 2/2] package/aespipe: fix host compile Arnout Vandecappelle
2017-07-25 22:14   ` 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=87r3579ef5.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.