Re: [Slackbuilds-users] the .info file

2010-02-26 Thread Rob McGee
On Thu, Feb 25, 2010 at 06:25:24PM -0600, JK Wood wrote:
> The day SBo starts tracking dependencies is the day I fork the 
> project...
> 
> Wait, I already forked the project...

Wood man speak with forked tongue! Powwow, smoke peace pipe!

> Okay, so the day SBo starts tracking dependencies is the day I
> stop submitting SlackBuilds.

A day without JKWood SlackBuilds is like a day without sunshine!

Seriously, I think you nothing to worry about. Not that you WERE
worried, of course.
-- 
Rob -- /dev/rob0
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/



Re: [Slackbuilds-users] Problem with python3

2010-02-26 Thread Audrius Kažukauskas
On Fri, 2010-02-26 at 12:58:24 +1100, Kevin Pulo wrote:
> Hi,
> 
> This builds and installs fine, but I get the following when I try to
> run the python3.1 interpreter:
> 
> $ python3.1
> Could not find platform independent libraries 
> Could not find platform dependent libraries 
> Consider setting $PYTHONHOME to [:]
> Fatal Python error: Py_Initialize: can't initialize sys standard streams
> ImportError: No module named encodings.utf_8
> Aborted
> $ 
> 
> Even when I try setting $PYTHONHOME to /usr, or /usr:/usr/bin, I still
> get the same error, minus the first 3 lines.

Looks like Python can't find its standard libraries.  And $PYTHONHOME
var should point to them if set, not to Python executable.  According to
the man page, standard libraries are searched in
${prefix}/lib/python and ${exec_prefix}/lib/python by
default (and both ${prefix} and ${exec_prefix} would be '/usr' in this
case if I'm not mistaken).  I wonder if the problem you're experiencing
is related to x86_64, where Python libraries are placed in
/usr/lib64/python.

> This is on Slackware64 13.0, with alienBob's -current multilib
> compilers.
> 
> Any ideas?

Unfortunately, I don't have any 64bit system to test this, so I'm really
not sure how to remedy this properly.  One way would be to use
$PYTHONHOME, but there should be something better.

BTW, does Python 2.x from Slackware work well?  (I guess it does.)  I'll
look into its SlackBuild later today to see what it does for x86_64.

> I'm also wondering if copying the subdirectories of Tools/, most of
> which are standalone scripts, into the site-packages/ directory, is
> correct, since site-packages is supposed to be for python modules that
> are imported into the interpreter.  Probably these files belong in
> /usr/doc/python3-3.1.1, instead of just being symlinked there.

I was basing my SlackBuild on the official one, so I believe I've copied
this bit from there.

-- 
Audrius Kažukauskas


pgpBY4fOtDlcf.pgp
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/