@Scott: the problem is not the addition of the flags. I have no problem with them being added, being different for PPAs or anything like that.
The problem is that the flags are added in an *invalid way*. See a more detailed recent/build log at https://launchpadlibrarian.net/128659634 /buildlog_ubuntu-quantal-amd64.python- apsw_3.7.15.2-r1-1ppa1~quantal1_FAILEDTOBUILD.txt.gz ie the flags are supposed to be added like this: [ ('_FORTIFY_SOURCE', '2'), ('FOO', 'BAR') ] which translates into #define _FORTIFY_SOURCE 2 #define FOO BAR Instead this is being supplied: [ '_FORTIFY_SOURCE', '2' ] which translates into #define _FORTIFY_SOURCE #define 2 The PPA system is messing up the *syntax* of how it adds the flags, and then that causes the builds to fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065302 Title: _FORTIFY_SOURCE being added for ppa builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apsw/+bug/1065302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
