summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-sql
diff options
context:
space:
mode:
authoraszlig <aszlig@nix.build>2017-11-08 06:33:21 +0100
committeraszlig <aszlig@nix.build>2017-11-08 06:48:15 +0100
commit7603da33decd2f3777306729d2a95c091b7801ab (patch)
tree2479bbf383258b78e5ce5b29e1e16b7b42360c52 /pkgs/development/python-modules/python-sql
parent3429d8cbbfd5cb15ab57ee1bbd173411fbee7328 (diff)
uqm: Fix build against glibc 2.26
I've bisected the introduction of the build failure to be the glibc 2.26 upgrade with commit 9bb67d5c1e546968fa3d195f0bcad82414243566. At first I was somewhat stumped why an glibc update could cause undeclared identifiers, but after looking at the changes of glibc and the source code of The Ur-Quan Masters the problem quickly turned out to be this very change: https://sourceware.org/git/?p=glibc.git;a=commit;h=7b037c095e31c2396d0a9b0e6356bc566ee4812f So string.h now in turn includes strings.h, which in theory wouldn't be a problem. However, both strings.h and the strings.h in the uqm source code use constant _STRINGS_H, which causes the glibc strings.h to be included but the one from uqm basically includes an empty file. Signed-off-by: aszlig <aszlig@nix.build>
Diffstat (limited to 'pkgs/development/python-modules/python-sql')
0 files changed, 0 insertions, 0 deletions