From: Ryan Hill <rhill@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [PATCH] waf-utils.eclass: respect CFLAGS in linking command
Date: Sun, 6 Apr 2014 17:12:21 -0600 [thread overview]
Message-ID: <20140406171221.1f82202f@caribou.gateway.pace.com> (raw)
In-Reply-To: 5341769E.6040809@gentoo.org
[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]
On Sun, 06 Apr 2014 15:45:34 +0000
hasufell <hasufell@gentoo.org> wrote:
> respect CFLAGS in linking command
> https://bugs.gentoo.org/show_bug.cgi?id=506956
>
> --- eclass/waf-utils.eclass
> +++ eclass/waf-utils.eclass
> @@ -56,18 +56,18 @@
> [[ -z ${NO_WAF_LIBDIR} ]] &&
> libdir="--libdir=${EPREFIX}/usr/$(get_libdir)"
> tc-export AR CC CPP CXX RANLIB
> - echo "CCFLAGS=\"${CFLAGS}\" LINKFLAGS=\"${LDFLAGS}\"
> \"${WAF_BINARY}\" --prefix=${EPREFIX}/usr ${libdir} $@ configure"
> + echo "CCFLAGS=\"${CFLAGS}\" LINKFLAGS=\"${CFLAGS} ${LDFLAGS}\"
> \"${WAF_BINARY}\" --prefix=${EPREFIX}/usr ${libdir} $@ configure"
> # This condition is required because waf takes even whitespace as
> function # calls, awesome isn't it?
> if [[ -z ${NO_WAF_LIBDIR} ]]; then
> - CCFLAGS="${CFLAGS}" LINKFLAGS="${LDFLAGS}" "${WAF_BINARY}" \
> + CCFLAGS="${CFLAGS}" LINKFLAGS="${CFLAGS} ${LDFLAGS}"
> "${WAF_BINARY}" \ "--prefix=${EPREFIX}/usr" \
> "${libdir}" \
> "$@" \
> configure || die "configure failed"
> else
> - CCFLAGS="${CFLAGS}" LINKFLAGS="${LDFLAGS}" "${WAF_BINARY}" \
> + CCFLAGS="${CFLAGS}" LINKFLAGS="${CFLAGS} ${LDFLAGS}"
> "${WAF_BINARY}" \ "--prefix=${EPREFIX}/usr" \
> "$@" \
> configure || die "configure failed"
Good.
--
Ryan Hill psn: dirtyepic_sk
gcc-porting/toolchain/wxwidgets @ gentoo.org
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2014-04-06 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 15:45 [gentoo-dev] [PATCH] waf-utils.eclass: respect CFLAGS in linking command hasufell
2014-04-06 23:12 ` Ryan Hill [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=20140406171221.1f82202f@caribou.gateway.pace.com \
--to=rhill@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