`<div dir="ltr">On Mon, Dec 12, 2016 at 4:15 PM, Dan McDonald <span dir="ltr"><<a href="mailto:danmcd@omniti.com" target="_blank">danmcd@omniti.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">How many folks in the audience are running 32-bit binaries that HAVE to be 32-bit for whatever reason? The Y2038 problem crossed my mind today, and the easy permanent cure is to cut off support for 32-bit userland.<br></blockquote><div><br></div><div>I'm pretty sure that the day job doesn't have anything that is irredeemably 32-bit.<br></div><div>We build what we use from source anyway, and virtually everything is 64-bit already.<br><br></div><div>(Speaking from a wider context, there's a huge amount of stuff that needs fixing,<br></div><div>and it's a pile of work.)<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Don't worry, this isn't a question that'll affect bloody or r151022... heck it probably won't affect r151030 (SUBSEQUENT LTS), but I am curious.<br></blockquote><div><br></div></div>But r151102 then...<br clear="all"></div><div class="gmail_extra"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">-Peter Tribble<br><a href="http://www.petertribble.co.uk/" target="_blank">http://www.petertribble.co.uk/</a> - <a href="http://ptribble.blogspot.com/" target="_blank">http://ptribble.blogspot.com/</a></div>
</div></div>
`