[tahoe-dev] Building tahoe-lafs on 64bit Windows 7 - Part 1, The building bits.

[knuttila @dslextreme.com]

On Tue, Jan 15, 2013 at 11:42 PM, David-Sarah Hopwood <
david-sarah at jacaranda.org> wrote:

> On 15/01/13 05:46, knuttila @dslextreme.com wrote:
> > Step 4 blunts its nose into the wall. The root cause is needing a 64bit
> twisted -- but the
> > symptom is "Unable to find vcvarsall.bat". "google is your friend" on
> this sort of thing.
> > Some rummaging, and you find there's a couple of ways to make the
> message go
> > away.
> >
> > Current solution -- basically, go to Twisted Matrix _(_
> http://twistedmatrix.com/trac/) and
> > look for
> > the current win7 64bit version. I used:
> "Twisted-12.3.0.win-amd64-py.2.7.msi".
>
> Unfortunately the precompiled "egg" for that dependency is missing for
> 64-bit Python 2.7
> on Windows:
>
>
> https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html
>
> which is why it tried to compile from source.
>
>
Agreed. And I see someone has added this now, so going to the twisted site
should
no longer be necessary. Thx! (we'll test that btw and report back :)


> > Aside: it turns out that you can install the 32bit Twisted version as
> well, and it will make
> > the message go away.
>
> That won't work.
>
>
Yeh, I was "suspicious".  Mostly I figured if we documented some of this on
the thread, others
could skip trying it. I'm not exactly a windows-guy, so some of this is
translating linux experience.


> > Step 5 won't work -- at least as far as I can see. The python file named
> "tahoe" appears to
> > need a "c:\Python27\python.exe" in front of it. (I'm a linux guy -- on
> any unix, we can use
> > the shell trick of marking a file executable, and giving the name of the
> interpreter in the
> > first line. What is the equivalent trick for DOS/Win7?) In any event, if
> you want to actually
> > run tahoe, you do something like:
> >
> > c:\Python27\python.exe C:\tahoe-lafs\bin\tahoe create-client
> C:\tahoelafsbase
> >
> > Rather than:
> >
> > C:\tahoe-lafs\bin\tahoe create-client C:\tahoelafsbase
> >
> > as described.
>
> That's odd, it should just work.
>
>
Agreed. And in fact, it does work. (I've confessed to goofing on the path
already. With appropriate
repairs, all works fine)


> - Do you have Python 3.x installed?
>

This is a great point. I missed on detailing the Python 2.7 install. (which
worked fine of
course, but without that information, it's hard to parse some of the rest
of the mail)

(there is no Python 3.x install on this box)


> - What is the first line of C:\tahoe-lafs\bin\tahoe.pyscript ?
> - What version of Python, if any, is first on the PATH? (i.e. what does
>   "python -V" report)
>
>
I shall report on this from the office in the morning. (no machine access)


> > Yes, we did some path tricks, and wrote some cheesy bat files to paper
> > over some of this, but it's awkward. (the silly part is I'm sure it's
> > do-able under win7/dos, but I've not run across the formula in casual
> > googling)
> >
> > The last bit comes from trying to fire it up. I'm missing a bit of notes
> here, but somewhere
> > we got a message moaning about a missing win32 api. I googled that, and
> came across
> > a blog who was following similar footsteps for a different application.
> Anyway, we installed
> > the pywin32 pieces from sourceforge and all that went away.
>
> It shouldn't be necessary to install pywin32. If you uninstall pywin32
> (from Add/Remove
> Programs), what error message does it give exactly?
>
>
Yeh. I googled it to get the repair, but didn't write it down. It was a
fairly generic
sort of "missing win32 api" sounding message. We're about to do a clean
install, and
will definitely faithfully record messages. (sometimes, the energy in
pushing to get
something working leads to blank sheets of paper at the wrong times....)

But first some overall status, and some next steps. We've attached the win7
box to the
grid, and loaded/unloaded files into the grid. Files shares are being
allocated to it, and the
universe seems to be running as it should. So with all the mucking around,
it all seems to
be working.

Our next step will be to clear the box and validate the steps we used to
get it onto our
test grid. I will try to give the complete steps used, and will definitely
be more faithful about
"cut/paste" messages/etc.

btw, I totally appreciate the commentary. We've started using tahoe-lafs
only weeks ago, and
have made solid progress even in learning mode.

--krk.

---
Kim Knuttila
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130116/1e7a9d75/attachment.html>