On Do, 06 Jun 2019, Mike Williams wrote:
> 16.04 is a Ubuntu LTS and supported for another 18 months or so. It > would be nice to think they would want to updated for such an obvious > bug on release widely used, but who knows. Just for the fun of it, I have been trying to see what commit caused it. I think, this commit fixed it: http://git.savannah.gnu.org/cgit/gettext.git/commit/?id=68ab0dafa99f1941b3ebb47b7cf969381e7310f4 Going further I could successfully apply that patch against Ubuntus 16.04 LTS version and rebuild the complete package. That seems to have fixed the problem on my local xenial (16.04LTS) box. So perhaps you can convince them to rebuild with that patch applied on top. > This is for a work machine so modifying toolchains via a PPA is not > possible. I can work around the problem now that I know what it is. Understood. I have been wondering if it would be doable to detect this problem somewhere and then skip this step. Not sure how to do this and if it would be worth the trouble. Best, Christian -- Sobald der Glaube an die Allmacht physischer Gewalt das Leben einer Nation beherrscht, emanzipiert sich diese Kraft, wird zum Selbstzweck und wird mächtiger als jene Männer, die sie als Werkzeug benützen wollen. -- Albert Einstein -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20190606154825.GN23877%40256bit.org. For more options, visit https://groups.google.com/d/optout.
