See attached build log.
(Please do not complain about the need for looking at the build log until you can provide an easy way to open bugs with the correct data picked out of a tinderbox log. Thanks.)
Created attachment 247348 [details]
Version 1.0.1 doesn't seem to have this problem anymore (as in, fixed by upstream)