Nick Coghlan <[email protected]> writes: > One thing you might want to try is to send yourself a PR that reverts > everything back to the way it was for your 0.1.0 release, and see if > *that* builds. If it doesn't, you can plausibly guess that something > changed unexpectedly in the Travis build environment. If it does > build, then you can start selectively removing things from the > reversion PR until the build breaks again.
Thank you Nick, this morning I ran a dozen of different attempts, and even if I was able to isolate the commit that makes the difference, I'm still lost in determining exactly *what* it does "wrong". Just for the history, and maybe to relax a bit, here is a brain dump of my discovering: * the commit that triggers the problem[1] is apparently innocuous, the prominent change is that instead of #including a "version.h" with some #defines it keeps the module's version in a toplevel "version.txt" and the actual version is passed to the compiler with a -D option * the immediate parent commit[2] does not exhibit the issue, * I tried to wander around the problematic commit trying out several different approaches and trialing various assumptions, without luck: my last attempt[3] (for today...) seems to prove that it's not the -D option the cause What a strange and boring problem :-\ Thanks for any further suggestion, ciao, lele. [1] https://github.com/python-rapidjson/python-rapidjson/commit/957be619ae24e5758bfd93711713d0296724acb9 [2] https://github.com/python-rapidjson/python-rapidjson/commit/3f350c7e3362d23713c06fa2884d92e10e0cc018 [3] https://github.com/python-rapidjson/python-rapidjson/commit/f750e43c23e3e990a4e596029c0029fab2793d55 -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. [email protected] | -- Fortunato Depero, 1929. _______________________________________________ Wheel-builders mailing list [email protected] https://mail.python.org/mailman/listinfo/wheel-builders
