_FORTIFY_SOURCE being added syntactically wrong for ppa builds breaking them
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-apsw (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
python2.7 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I'm the author of apsw - https:/
This has worked fine for a few years. However builds for Quantal are failing. You can see a failed build log at https:/
The cause is because _FORTIFY_SOURCE is being mishandled. Its definition and usage is not coming from my code. I can't tell if the problem is the server side environment having a bug or something involved in making packages for submission is adding it. Perhaps the Python stuff on 12.04 (where I do the ppa submissions) is putting in gunk that breaks 12.10?
Attached is a .build file from the client machine. It contains the following line which is not my doing
dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): -D_FORTIFY_SOURCE=2
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: python-dev 2.7.3-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-31-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Wed Oct 10 15:39:41 2012
SourcePackage: python-defaults
UpgradeStatus: No upgrade log present (probably fresh install)
summary: |
- _FORTIFY_SOURCE being added for ppa builds + _FORTIFY_SOURCE being added syntactically wrong for ppa builds breaking + them |
it looks like the Ubuntu package for raring did build. I do see that you use another packaging debian directory. Maybe you could update the packaging, and see if it does build? And please drop using dh_pycentral ...