Hello *,
I tried to install Mailman 2.1b3 and I followed the installation instruction exactly but make install fails with the following message:
--- snip --- Compiling /usr/local/mailman/Mailman/versions.py ... Traceback (most recent call last): File "bin/update", line 44, in ? import paths ImportError: No module named paths make: *** [update] Error 1 --- snap ---
My system: SuSE 7.2 Python 2.2.1 gcc 2.95.3
The problem was already described here: http://mail.python.org/pipermail/mailman-users/2002-July/020991.html but no solution has been posted as far as I could see...
Any idea how solve this or how to further debug the problem?
thanks a lot in advance, Goeran Zaengerlein
Hi *,
ok, I found out what the problem is: The configure script creates the file "/src/mailman-2.1b3/misc/paths.py", but "make install" does not copy it to "$prefix/bin".
When make runs the update target it calls the $prefix/bin/update script which tries to import the paths module. If you do the installation on a system where already a mailman installation exists you won't get the error as the paths.py already exists... So problem is only visible for a from-the-scratch installation.
Any idea where in the Makefile the paths.py should be copied and why this does actually not happen? I think there might be a problem with the makefile in /misc, but I am not so fluent in makefiles ;)
My workaround for now is: make install cp ./misc/paths.py /usr/local/mailman/bin make install
regards, Goeran Zaengerlein
"GZ" == Goeran Zaengerlein goeran@zaengerlein.de writes:
GZ> ok, I found out what the problem is: The configure script
GZ> creates the file "/src/mailman-2.1b3/misc/paths.py", but "make
GZ> install" does not copy it to "$prefix/bin".
I do occasionally get reports about this, but I've never been able to reproduce it, even on fresh installs. I wonder if this is a GNU make-ism problem? I've primarily tested on various flavi of Linux, but OTOH, it doesn't /seem/ like I'm doing anything particularly GNU make-y.
Thanks Dan for analyzing the way it /ought/ to work (and does for me and most people). I'd love to understand why it's broken for some folks.
-Barry
participants (2)
-
barry@python.org
-
Goeran Zaengerlein