[SCM] ardour3/master: Pass env variables to waf

[Felipe Sateler]

On Tue, Sep 24, 2013 at 5:01 PM, Jaromír Mikeš <mira.mikes at gmail.com> wrote:

> 2013/9/24 Felipe Sateler <fsateler at debian.org>
>>
>> On Tue, Sep 24, 2013 at 11:33 AM,  <fsateler at users.alioth.debian.org>
>> wrote:
>> > The following commit has been merged in the master branch:
>> > commit ae11cc02389f29f0e7c3545f35606a113ce68d60
>> > Author: Felipe Sateler <fsateler at debian.org>
>> > Date:   Tue Sep 24 11:33:11 2013 -0300
>> >
>> >     Pass env variables to waf
>>
>>
>> For some reason this works for LDFLAGS but not CFLAGS or CXXFLAGS. Any
>> ideas on why waf decides to ignore them? They are supposed to work...
>
>
> Hi,
>
> I've encountered this problem when tried fix hardening too :(
> Maybe we can try update waf-light from 1.6.11 (Feb 2012) to current 1.7.13,
> but reading waf upstream changelog I can't find nothing related to this
> issue.
>
> waf build system using standard names for "*FLAGS" ... so there shouldn't be
> problem
> http://code.google.com/p/waf/wiki/EnvironmentVariables

Yes, I read this page so I assumed it would work, but it doesn't...
Can you try updating the waf-light script and seeing if *FLAGS are
respected? Fortunately configure prints the *FLAGS so no need to build
the whole package to test if that works.

We should also disable the optimizations and enable them manually (it
is now ftbs everywhere). We need to set the --dist-target argument to
configure appropriately (x86_64 in amd64, i386 in i386 and none in the
rest, I think). Not sure if that is enough.

-- 

Saludos,
Felipe Sateler