On Thu, Mar 31, 2016 at 9:28 AM, Rene Engelhard <[email protected]> wrote: > On Thu, Mar 31, 2016 at 08:27:20AM +0200, László Böszörményi (GCS) wrote: > unset DISPLAY. debian/rules already does that[1] and that fixed it for me > so I wonder why you got it. ran make check manually or so? Yes, 'make check' was issued by hand in a previously built tree. After I unset DISPLAY before the tests, all passed successfully. A full build takes about half a day on my machine if I stop everything and use console only.
>> it? I think it would be better to wait until it's accepted and re-run >> my tests with ICU 57.1 version. What do you think? > > The main usage of boost is the headers (and ttbomk date-time and system > - and filesystem in 5.2 - shouldn't be affected by ICU changes, should it?) > Of course you never know. Boost C++ libraries also build depends on ICU. > But I guess the RT will not want to have a boost and a icu transition at the > same time anyway, so... Well, it wouldn't be a parallel transition in the traditional sense due to the following: - Boost 1.60 targets _Sid_, - until boost-defaults (separate source package) is not updated, packages will not even know 1.60, - ICU 57.1 would target _experimental_. Thanks for the help, Laszlo/GCS
