Working on installing Python 3.2, a little help needed please
 

So I have patched the 3.2 sources similar to the 3.1.3 sources. I used the slackbuild from 3.1.3 as well. I get to the install of the script and I get this:

Any thoughts on how to fix this? I can't build Blender anymore without this update. :(

Thanks in advance,
Eric

Hi,

just replace string
cp -a README LICENSE Demo Doc Misc $PKG/usr/doc/python3-$VERSION

with
cp -a README LICENSE Doc Misc $PKG/usr/doc/python3-$VERSION

Or you can use the package I've built for myself (i486)
http://asafonov.org/images/slackware...1_asafonov.tgz



Good luck!

@me@asafonov.org: I've had a look at your package but it seems to be built for Slackware, (standard 32 bit), whereas I assume the OP was enquiring about Slackware64 as his post mentions this :
If this is the case - I too am interested in a build of python3.2 for Slackware64 - preferably a SlackBuild rather than a package - as I have messed around with a build of python3.2 on my Slackware64 system but gave up early on as I haven't had the time to customize the patches needed to make the build work correctly on Slackware64. Not that it's a huge amount of work but making such patches to source code can be quite time consuming. If not then I apologize but, in that case,the OP has something badly wrong with his SlackBuild or ARCH settings!

@bgeddy It seems you're right about x64.

Please try this slackbuild and feel free to report about any issues

http://asafonov.org/python3.2.tar.gz

Thanks me@asafonov.org, that was the ticket. I really need to spend a little more time reading slackbuild scripts. This is in fact for an x64 system.

bgeddy, I still have a ways to go before I can start publishing slackbuilds. I'll give you a run-down so you can try to reproduce my steps if you like. I downloaded the 3.2 source and the slackbuild for 3.1.3. I uncompressed the source and opened the diff files from the slackbuild and manually applied the patches to the new source. From there I recompressed the source folder and removed the patch lines from the slackbuild and removed the Demo tag as shown above. From there the script ran perfectly.

Hi, I'm the maintainer of python3 SlackBuild at SlackBuilds.org. I've updated my SlackBuild for Python 3.2, but currently submissions to SBo are closed, so you can grab it from my Mercurial repository.

One thing to notice is that I've consolidated two patches for Slackware64 into one, since previous approach didn't make much sense to me (it was done in the same way as in official SlackBuild). I'm planning to do the same for Python 2.x and propose this to Pat after Slackware 13.37 release.

So far I haven't noticed any problems with my SlackBuild, though I'm not using Python 3.x that much. At least installing libraries via distutils (both pure Python and with C extensions) works fine, same with distribute (setuptools fork). There's one bug I've stumbled upon, but it's a problem in Python code.

Damn it - I wish I had read your post a little earlier as I have just spent a good few hours creating new .diff's for the patches to python3.2. I too consolidated the two patches python3.pure64.diff and python3.x86_64.diff as they appear to duplicate each other (well one duplicates the other anyway). It has been good practice creating and consolidating patches if nothing else - something I tend to avoid and, to be honest, leave to others to work out! Thanks for the update - builds fine and all seems good. So thanks due to me@asafonov.org, em21701 and audriusk - good work fellas.

Great, thanks for updating audriusk. I can compile Blender now.