From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Add --hash-style=gnu to LDFLAGS
Date: Sat, 14 Aug 2010 00:14:28 -0400 [thread overview]
Message-ID: <AANLkTikmfGRDCizJeHEO2Tm-kQKg8JJqS2j-Gom7Vr_c@mail.gmail.com> (raw)
In-Reply-To: <20100813214335.4f0b83b9@gentoo.org>
On Fri, Aug 13, 2010 at 11:43 PM, Ryan Hill wrote:
> On Fri, 13 Aug 2010 18:11:42 +0300 Markos Chandras wrote:
>> Could someone guide me to add --hash-style=gnu to default/linux/amd64/dev
>> profile? I don't want to break anything
>
> The thing is, you can't right now. :D LDFLAGS don't stack, meaning you'd
> have to do something like
>
> --- targets/developer/make.defaults 26 Jul 2010 19:15:05 -0000 1.9
> +++ targets/developer/make.defaults 14 Aug 2010 03:31:18 -0000
> @@ -12,3 +12,6 @@
>
> # Log eqawarn messages
> PORTAGE_ELOG_CLASSES="${PORTAGE_ELOG_CLASSES} qa"
> +
> +# Help find packages not respecting LDFLAGS
> +LDFLAGS="-Wl,--hash-style=gnu ${LDFLAGS}"
>
>
> Which breaks boost-build (bug #293652). That's why I suggested just putting
> a message in targets/developer/profile.bashrc (which is otherwise completely
> useless).
that's crap. fix the package or at least work around it:
LDFLAGS=`echo ${LDFLAGS}`
we shouldnt be forced to add random hacks throughout the tree because
of one or two random broken packages
-mike
next prev parent reply other threads:[~2010-08-14 4:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 16:32 [gentoo-dev] Add --hash-style=gnu to LDFLAGS Markos Chandras
2010-08-07 16:35 ` Tomáš Chvátal
2010-08-07 16:37 ` Alexis Ballier
2010-08-07 16:48 ` Markos Chandras
2010-08-07 18:59 ` Alexis Ballier
2010-08-07 22:08 ` Mike Frysinger
2010-08-07 17:18 ` [gentoo-dev] " Diego Elio “Flameeyes” Pettenò
2010-08-10 21:53 ` Markos Chandras
2010-08-10 22:31 ` Mike Frysinger
2010-08-11 9:11 ` Markos Chandras
2010-08-11 10:42 ` Thilo Bangert
2010-08-12 8:35 ` Christian Faulhammer
2010-08-13 15:11 ` Markos Chandras
2010-08-14 3:43 ` Ryan Hill
2010-08-14 3:50 ` Ryan Hill
2010-08-14 9:23 ` Markos Chandras
2010-08-14 4:14 ` Mike Frysinger [this message]
2010-08-14 6:41 ` Ryan Hill
2010-08-14 6:40 ` Mike Frysinger
2010-08-14 12:08 ` Markos Chandras
2010-08-14 17:58 ` Mike Frysinger
2010-08-14 18:05 ` Markos Chandras
2010-08-14 18:31 ` Samuli Suominen
2010-08-14 18:34 ` Mike Frysinger
2010-08-14 19:46 ` Markos Chandras
2010-08-15 7:31 ` Christian Faulhammer
2010-08-07 21:32 ` Mike Frysinger
2010-08-08 0:11 ` Markos Chandras
2010-08-08 0:15 ` Alec Warner
2010-08-08 0:21 ` Markos Chandras
2010-08-08 7:57 ` Petteri Räty
2010-08-08 8:37 ` Ryan Hill
2010-08-08 0:22 ` Diego Elio Pettenò
2010-08-08 0:19 ` Diego Elio Pettenò
2010-08-08 11:12 ` Markos Chandras
2010-08-08 2:16 ` Mike Frysinger
2010-08-08 11:14 ` Markos Chandras
2010-08-09 23:03 ` Markos Chandras
2010-08-09 23:05 ` Mike Frysinger
2010-08-10 8:45 ` Brian Harring
2010-08-10 18:40 ` Francesco R
2010-08-10 20:09 ` Mike Frysinger
2010-08-10 20:16 ` Mike Frysinger
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=AANLkTikmfGRDCizJeHEO2Tm-kQKg8JJqS2j-Gom7Vr_c@mail.gmail.com \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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