Merge ~ahasenack/ubuntu/+source/uwsgi:disco-ftbfs-1820095 into ~ahasenack/ubuntu/+source/uwsgi:master
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Andreas Hasenack | ||||
Approved revision: | 88e9db5bd4cd1ae7021566c16048225f4da14690 | ||||
Merged at revision: | 88e9db5bd4cd1ae7021566c16048225f4da14690 | ||||
Proposed branch: | ~ahasenack/ubuntu/+source/uwsgi:disco-ftbfs-1820095 | ||||
Merge into: | ~ahasenack/ubuntu/+source/uwsgi:master | ||||
Diff against target: |
79 lines (+15/-6) 3 files modified
debian/changelog (+9/-0) debian/control (+3/-3) debian/control.in (+3/-3) |
||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Christian Ehrhardt (community) | Approve | ||
Canonical Server MOTU reviewers | Pending | ||
Review via email: mp+364802@code.launchpad.net |
Description of the change
PPA with test builds: https:/
uwsgi is not imported into git-ubuntu, so this MP is against my own "master" branch which is the state of the package in disco.
gccgo recently[1] switched to pull in gccgo-9 instead of -8, and that breaks the uwsgi gccgo plugin build. The plugin looks for the "go1" in binary in gcc's (and cpp's) "/8/" directory, because that's where default gcc and cpp point at:
$ cpp -v 2>&1|grep /include
ignoring nonexistent directory "/usr/local/
ignoring nonexistent directory "/usr/lib/
/usr/lib/
/usr/local/include
/usr/lib/
/usr/include/
/usr/include
$ dpkg -s cpp|grep Depends
Depends: cpp-8 (>= 8.3.0-1~)
Switching the whole build to use gcc-9 instead of -8 is a much bigger change that I'm not entertaining at this point. Telling uwsgi to use gccgo-8, which is what it used before, is a much safer option and the right thing to do now in feature freeze.
I'm also dropping the libqdbm-dev build dependency for reasons explained in https:/
1. https:/
Ack to "Switching the whole build to use gcc-9 instead of -8 is a much bigger change that I'm not entertaining at this point. Telling uwsgi to use gccgo-8, which is what it used before, is a much safer option and the right thing to do now in feature freeze."
let me check the details ...