Control: tags -1 - moreinfo Control: severity -1 serious On Thu, May 21, 2015 at 07:24:18PM +0200, Helmut Grohne wrote: > | Looking for ncursesw-config > | checking for ncursesw-config... no > | checking for ncursesw6-config... no > | checking for ncursesw5-config... no
There is a notable difference to successful builds here. Those say: | checking for ncursesw5-config... ncursesw5-config Now where does that come from? ncurses-bin. Well, it came from there, but it no longer does. > I've seen this in a native amd64 reproducible build on > jenkins.debian.net: > > https://jenkins.debian.net/job/reproducible_builder_alpha/46528/console > (the above excerpt is from this log) This build uses the new ncurses-bin. > I've also seen this in a cross build for x32 and a cross build for i386. > > https://jenkins.debian.net/job/rebootstrap_i386_gcc49_nobiarch/139/console > > In the x32 build (no log available), I created the directory being > stat()ed. At that point, the build continued and finished successfully. > Both cross builds set DEB_BUILD_OPTIONS="nocheck parallel=1". These did as well. > Notably, the reproducible jenkins job was able to build this version of > ncurses earlier, so it seems that something else is the cause. The > buildds had no problems building it either. These builds used the old ncurses-bin that contained ncurses5-config. Now this doesn't tell me how to fix it, but it tells me that ncurses is seriously broken. Maybe Build-Depends: libncursesw5-dev? But that sounds very bad from a bootstrap perspective. Helmut -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
