Conversation
|
Some of you did test this, right? |
|
This fails building on Linux. I thought it was no problem, but some packages we have explicitly link against this libintl even on Linux. I don't really know why. Any ideas? Example: aegisub; others seen in http://hydra.nixos.org/eval/1156552?compare=1156478&full=1#tabs-now-fail. |
|
Indeed, libiconv 1.14 does not build on Linux. This is an issue. I don’t think I can (look at how to) fix it now. So I won’t mind if this PR is closed without merging. On the other hand, thanks a lot for your testing vcunat. I’ve just pushed an other commit that should fix the failures you’ve observed and that are due to libiconv. I think that the second commit is independent from the first one and is useful on its own. There is still one derivation that explicitly requires libiconv: vagrant. I don’t know how to fix it. |
|
CC vagrant maint. @lovek323: any idea whether external libiconv is really needed for vagrant on linux (instead of the glibc builtin)? |
|
@vcunat: Nope. Haven't tested it either way. |
This fixes build after #4419. It seems to start fine without the flags, CC maint. @AndersonTorres.
|
OK, I think I've fixed almost all now. |
No description provided.