Building yourself is the way to go; I've run through a bunch of issues on windows typically traced back to different versions of the MS c++ runtime; if hadoop is built against a different version than is on your box it just kind of fails silently.
On Tue, Jul 7, 2015 at 1:17 PM, Parise, Jonathan <[email protected]> wrote: > It seems like compiling would be the way to go in this case. > > > > He has access to a 64-bit Linux VM on another machine, so he may just use > that. > > > > I was just wondering if a winutils.exe that was 32-bit was stashed > anywhere. I found a 64-bit version on git hub, but nothing 32 bit. > > > > Thanks, > > > > Jon > > > > *From:* Mike Atlas [mailto:[email protected]] > *Sent:* Tuesday, July 07, 2015 12:34 PM > *To:* [email protected] > *Subject:* Re: 32-bit Version of Winutils.exe > > > > Also, painful, but perhaps compiling hadoop from scratch on the 32bit Win7 > machine might still be feasible yourself: > > > > > http://www.srccodes.com/p/article/38/build-install-configure-run-apache-hadoop-2.2.0-microsoft-windows-os > > > > > > > > On Tue, Jul 7, 2015 at 12:30 PM, Mike Atlas <[email protected]> wrote: > > Perhaps convoluted, but if the CPU itself is x64 and your colleague is > running Windows 7-32bit, you *could* run VirtualBox and host a guest x64 > OS: > http://askubuntu.com/questions/180761/can-i-use-virtualbox-with-a-64-bit-image-in-a-32-bit-host > > > > I'm guessing your colleague really does have a 32-bit CPU though, huh. > > > > > > On Tue, Jul 7, 2015 at 12:12 PM, Josh Elser <[email protected]> wrote: > > ... MAC actually runs on Windows? Color me surprised. > > > > Parise, Jonathan wrote: > > Hi, > > Does anyone know where I can find a 32-bit version of Winutils.exe? I > have written some unit tests using the Mini Accumulo Cluster(MAC) and > they need this file. I have found several places that have a 64-bit > version of this file, but I can’t find a 32-bit one. > > A colleague of mine is stuck on Window 7 32-bit. He won’t be able to run > the tests locally without the file. > > Thanks, > > Jon Parise > > > > >
