Control: affects -1 = src:3depict src:aegisub src:amule src:asc src:codeblocks src:filezilla src:flamerobin src:freedink-dfarc src:lamarc src:maitreya src:mediainfo src:openyahtzee src:poedit src:spek src:usbprog src:wxsqlite3 src:wxsvg src:xchm
Hi Olly, On Sun, Nov 03, 2019 at 06:06:55PM +1300, Olly Betts wrote: > Reassigning - the GTK2 flavour packages are gone from testing and only > present in unstable due to a handful of untransitioned rdeps. Thank you! Often times, I've seen such bugs closed in a transition. > On Thu, Sep 14, 2017 at 11:03:08PM +0200, Helmut Grohne wrote: > > I believe that mediainfo's use of --host is reasonable and wx-config > > should handle the native --host just fine. > > I noticed the upstream bug this is forwarded too was closed as invalid > way back in 2011. It seems unlikely upstream will fix this without > prodding, so we probably should reopen the upstream bug and provide > an explanation for why this should work. I do agree with this. It seemed beyond my reasonable reach though, so I left it at documenting that it actually affects cross building in Debian today. I don't think, I can drive this upstream, but I'll help where I can. > But reviewing your report I'm confused. Is this really a cross-build or > not? > > You say "native --host", which seems to imply it's not really a > cross-build but a native build with --host=`./config.guess` or > something similar, and that is indeed what the upstream bug report > this bug is forwarded to is complaining doesn't work. I now see how you find that confusing. In the example, I installed the wx-config on a ppc64el box, so there ppc64el was native. Once you pass --host, it stops working. The example works exactly the same way on amd64. Once you pass --host=x86_64-linux-gnu, it stops working. > But looking at mediainfo's ./Project/GNU/GUI/wxwin.m4 it seems we must > be triggering this conditional appending: > > if test "$cross_compiling" = "yes"; then > wx_config_args="$wx_config_args --host=$host_alias" > fi The usual native invocations lack --host, which is why the problem could fly under the radar for this long. > So it seems that mediainfo's configure script thinks we are > cross-compiling. Yes, the bug at hand only affects cross building, because you don't usually pass --host otherwise (given that it doesn't work at all). > I checked the crossqa logs for mediainfo, but they show a failure due > to libzen, not wx: > > configure: error: libzen configuration is not found > > http://crossqa.debian.net/build/mediainfo_18.12-2.1_ppc64el_20191016050307.log You're seeing a different problem #875830 here. I updated the affects such that you have more direct instances to choose from. Thank you Helmut
