[Mailman-Users] mailman install problem
Hi, I'm trying to install mailman 2.1.9 on a Solaris 10 x86 machine and I'm running into problems with make install. I have no cc installed, I am using GCC 3.4.5 which I've installed from blastwave.org; python is 2.3.5. I've searched the archives of the list and hit up google to no avail, any suggestion(s) or hints would be most appreciated, I'm ready to scrap this install. I don't know if it's something funky in Sol10's make or maybe mailman's expecting gcc to be cc (see unable to execute cc: No such file or directory \ error: command 'cc' failed with exit status 1 -- I did NOT specify the --with-gcc=no option during the configure). bash-3.00# make install Creating architecture independent directories... chmod o-r /usr/local/mailman/archives/private Creating architecture dependent directories... make[1]: Entering directory `/usr/local/mailman/bin' for f in mmsitepass newlist rmlist add_members list_members remove_members clone_member update arch sync_members check_db withlist check_perms find_member version config_list list_lists dumpdb cleanarch list_admins genaliases change_pw mailmanctl qrunner inject unshunt fix_url.py convert.py transcheck b4b5-archfix list_owners msgfmt.py show_qfiles discard rb-archfix reset_pw.py; \ do \ .././install-sh -c -m 755 ../build/bin/$f /usr/local/mailman/bin; \ done make[1]: Leaving directory `/usr/local/mailman/bin' make[1]: Entering directory `/usr/local/mailman/cron' for f in crontab.in; \ do \ .././install-sh -c -m 644 $f /usr/local/mailman/cron; \ done for f in checkdbs mailpasswds senddigests gate_news nightly_gzip bumpdigests disabled; \ do \ .././install-sh -c -m 755 ../build/cron/$f /usr/local/mailman/cron; \ done make[1]: Leaving directory `/usr/local/mailman/cron' make[1]: Entering directory `/usr/local/mailman/misc' for i in ./*.jpg ./*.png; \ do \ .././install-sh -c -m 644 $i /usr/local/mailman/icons; \ done for d in bin cron scripts tests; \ do \ dir=/usr/local/mailman/$d; \ .././install-sh -c -m 644 paths.py $dir; \ done .././install-sh -c -m 755 mailman /usr/local/mailman/scripts .././install-sh -c -m 644 sitelist.cfg /usr/local/mailman/data for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \ do \ gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /opt/csw/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /opt/csw/lib/python2.3/distutils/dist.py:213: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) unable to execute cc: No such file or directory error: command 'cc' failed with exit status 1 make[1]: *** [install-packages] Error 1 make[1]: Leaving directory `/usr/local/mailman/misc' *** Error code 2 The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall' bash-3.00# Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman install problem
I don't see any obvious errors, but I don't know...
bash-3.00# more config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:558: checking for --with-python
configure:576: checking for python
configure:612: checking Python interpreter
configure:628: checking Python version
configure:662: checking that Python has a working distutils
configure:728: checking for a BSD compatible install
configure:781: checking whether make sets ${MAKE}
configure:810: checking for true
configure:846: checking for --without-gcc
configure:875: checking for gcc
configure:988: checking whether the C compiler (gcc ) works
configure:1004: gcc -o conftestconftest.c 15
configure:1030: checking whether the C compiler (gcc ) is a cross-compiler
configure:1035: checking whether we are using GNU C
configure:1044: gcc -E conftest.c
configure:1063: checking whether gcc accepts -g
configure:1115: checking whether #! works in shell scripts
configure:1148: checking for --with-var-prefix
configure:1163: checking for --with-permcheck
configure:1195: checking for --with-username
configure:1213: checking for user name mailman
configure:1259: checking for --with-groupname
configure:1278: checking for group name mailman
configure:1323: checking permissions on /usr/local/mailman
configure:1379: checking for mail wrapper group; i.e. --with-mail-gid
configure:1438: checking for CGI wrapper group; i.e. --with-cgi-gid
configure:1500: checking for CGI extensions
configure:1520: checking for --with-mailhost
configure:1538: checking for --with-urlhost
configure:1567: checking for default mail host name
configure:1574: checking for default URL host component
configure:1586: checking for strerror
configure:1614: gcc -o conftest -g -O2 conftest.c 15
configure:1586: checking for setregid
configure:1614: gcc -o conftest -g -O2 conftest.c 15
configure:1586: checking for syslog
configure:1614: gcc -o conftest -g -O2 conftest.c 15
configure:1677: checking how to run the C preprocessor
configure:1698: gcc -E conftest.c /dev/null 2conftest.out
configure:1757: checking for ANSI C header files
configure:1770: gcc -E conftest.c /dev/null 2conftest.out
configure:1837: gcc -o conftest -g -O2 conftest.c 15
configure:1864: checking for syslog.h
configure:1874: gcc -E conftest.c /dev/null 2conftest.out
configure:1903: checking for uid_t in sys/types.h
configure:1937: checking type of array argument to getgroups
configure:1970: gcc -o conftest -g -O2 conftest.c 15
configure:2012: checking for vsnprintf
configure:2040: gcc -o conftest -g -O2 conftest.c 15
configure:2024: warning: conflicting types for built-in function 'vsnprintf'
bash-3.00#
-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED]
Sent: Tue 1/23/2007 3:17 PM
To: Piniella, David A; mailman-users@python.org
Subject: Re: [Mailman-Users] mailman install problem
Piniella, David A wrote:
I'm trying to install mailman 2.1.9 on a Solaris 10 x86 machine and I'm
running into problems with make install.
I have no cc installed, I am using GCC 3.4.5 which I've installed from
blastwave.org; python is 2.3.5.
I've searched the archives of the list and hit up google to no avail,
any suggestion(s) or hints would be most appreciated, I'm ready to scrap
this install. I don't know if it's something funky in Sol10's make or
maybe mailman's expecting gcc to be cc (see unable to execute cc: No
such file or directory \ error: command 'cc' failed with exit status 1
-- I did NOT specify the --with-gcc=no option during the configure).
configure should find an appropriate C compiler and taylor the Makefile
appropriately. Were there any errors from configure. What does
config.log say about the C compiler?
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman install problem
I have actually already renamed the /usr/ucb/cc (to cc_old) and modified my path (specifically for the install): bash-3.00# which gcc /opt/csw/gcc3/bin/gcc bash-3.00# which cc no cc in /usr/local/sbin /opt/csw/sbin /opt/sfw/sbin /opt/sbin /usr/sbin /sbin /usr/local/bin /usr/bin /opt/bin /bin /usr/openwin/bin /opt/csw/bin /opt/sfw/bin /usr/apache/bin /opt/csw/gcc3/bin /usr/ccs/bin bash-3.00# I'm still getting the same unable to execute cc error. I really don't understand it; would there be any cached info? -d. -Original Message- From: Hank van Cleef [mailto:[EMAIL PROTECTED] Sent: Tue 1/23/2007 3:52 PM To: Piniella, David A Cc: mailman-users@python.org Subject: Re: [Mailman-Users] mailman install problem The esteemed Piniella, David A has said: Hi, I'm trying to install mailman 2.1.9 on a Solaris 10 x86 machine and I'm running into problems with make install. I have no cc installed, I am using GCC 3.4.5 which I've installed from blastwave.org; python is 2.3.5. I've searched the archives of the list and hit up google to no avail, any suggestion(s) or hints would be most appreciated, I'm ready to scrap this install. I don't know if it's something funky in Sol10's make or maybe mailman's expecting gcc to be cc (see unable to execute cc: No such file or directory \ error: command 'cc' failed with exit status 1 -- I did NOT specify the --with-gcc=no option during the configure). (snippity snippity) /opt/csw/lib/python2.3/distutils/dist.py:213: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) unable to execute cc: No such file or directory error: command 'cc' failed with exit status 1 make[1]: *** [install-packages] Error 1 make[1]: Leaving directory `/usr/local/mailman/misc' *** Error code 2 You're probably seeing what's a well-known problem with Solaris using GNU-type configure and Makefile generation. Easy to fix. The cc that some makefile is finding is probably /usr/ucb/cc in the Solaris install. That is a stub that does nothing. Rename it to cc.bsd. On a Solaris site, you have to set up PATH as a post-install operation. Most Solaris admins have a post-install script for doing this. Do a check, using the which command. which gcc should point to the path where the gcc you want to use is located, and do a version check. Then do a which cc. Unless you have Studio 11 installed, you should get a not found return. The Studio 11 compiler resources are in /opt/SUNWspro/bin if they are installed. You may have to locate the offending Makefile or rerun configure to recover, but try make install first, after assuring that nothing can find /usr/ucb/cc. Hank Hank -- Hank van Cleef ([EMAIL PROTECTED], [EMAIL PROTECTED]) 1986 420SEL A stranger in paradise (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup Seen one, seen them all -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman install problem
Thanks for you help, guys. Actually, I checked the Makefile in /usr/local/mailman (my $prefix), and /usr/local/mailman/src/Makefile and they both have CC= gcc. I have deleted the Makefiles, config.cache config.status, rerun ./configure (my specific options are --prefix, --with-cgi-gid, --with-mailhost and --with-urlhost) and re-run make and make install. I keep getting the error on make install. For laughs, since I saw the Makefile had the full path in the PYTHON= line, I put the full path to gcc in the CC= line, re-ran configure and it still fails. -d. -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 23, 2007 4:17 PM To: Piniella, David A; Hank van Cleef Cc: mailman-users@python.org Subject: Re: [Mailman-Users] mailman install problem Piniella, David A wrote: I have actually already renamed the /usr/ucb/cc (to cc_old) and modified my path (specifically for the install): snip I'm still getting the same unable to execute cc error. I really don't understand it; would there be any cached info? Did you rerun configure (not just config.status) after making those changes? If all else fails, look at src/Makefile in the directory in which you are running make and find the CC= line (which probably says 'CC= cc') and change it to 'CC= gcc'. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman install problem
Hmmm, that didn't work. Same error about no cc... -Original Message- From: Hank van Cleef [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 23, 2007 4:52 PM To: Piniella, David A Cc: mailman-users@python.org Subject: Re: [Mailman-Users] mailman install problem The esteemed Piniella, David A has said: I have actually already renamed the /usr/ucb/cc (to cc_old) and modified my path (specifically for the install): bash-3.00# which gcc /opt/csw/gcc3/bin/gcc bash-3.00# which cc no cc in /usr/local/sbin /opt/csw/sbin /opt/sfw/sbin /opt/sbin /usr/sbin /sbin /usr/local/bin /usr/bin /opt/bin /bin /usr/openwin/bin /opt/csw/bin /opt/sfw/bin /usr/apache/bin /opt/csw/gcc3/bin /usr/ccs/bin bash-3.00# I'm still getting the same unable to execute cc error. I really don't understand it; would there be any cached info? Hokay! Here's the deal. I have just walked this question through with a junk Mailman 2.1.9 tree. This tree was originally build using Studio 11 cc. I took the pointer to that out of my PATH, ran a make clean, and ran configure. It crashed at what appears to be the same point yours did. Then I ran a make distclean, and reran configure. That ran to completion properly. Followed that up with a make, although that doesn't compile the stuff in the misc directory. However, checking that makefile it has CC=gcc. I'll suggest that you start over with a make distclean and a new configure. Hank -- Hank van Cleef ([EMAIL PROTECTED], [EMAIL PROTECTED]) 1986 420SEL A stranger in paradise (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup Seen one, seen them all -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman install problem - Solaris
No dice, I tried that with gcc and yacc. Is there any way to just avoid the Japanese and Korean codecs packages' compilation, or to skip them entirely? I don't really need to host any lists in Japanese or Korean (or do these packages do something else?) -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 23, 2007 5:09 PM To: Piniella, David A; Hank van Cleef Cc: mailman-users@python.org; Kent Taylor Subject: RE: [Mailman-Users] mailman install problem - Solaris Piniella, David A wrote: Thanks for you help, guys. Actually, I checked the Makefile in /usr/local/mailman (my $prefix), and /usr/local/mailman/src/Makefile and they both have CC=3D gcc. I have deleted the Makefiles, config.cache config.status, rerun ./configure (my specific options are --prefix, --with-cgi-gid, --with-mailhost and --with-urlhost) and re-run make and make install. I keep getting the error on make install. For laughs, since I saw the Makefile had the full path in the PYTHON=3D line, I put the full path to gcc in the CC=3D line, re-ran configure and it still fails. Yeah, I realized the problem after I sent my last reply. The problem is in the 'make install'. The install target runs the install target of misc/Makefile which in turn runs install-packages which installs the email, JapaneseCodecs, and KoreanCodecs packages. This install starts by unzipping and expanding the .tar.gz files containing the packages and then running the setup.py file from the package. Part of the KoreanCodecs package requires compilation of C modules. I think this is where you and other Solaris users run into difficulty. I'm not really an expert on this, but perhaps if you put a symlink to your gcc named cc somewhere on your path before running make install, this will do it. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman install problem - Solaris
I did a make distclean, a new configure, patched, verified that my $prefix/pythonlib/ dir had no korean dir (a japanese dir though) and then make and make install and this is where it breaks: (a lot of listing and compiling, well after where it was breaking before and then ) Compiling /usr/local/mailman/Mailman/htmlformat.py ... Compiling /usr/local/mailman/Mailman/i18n.py ... Compiling /usr/local/mailman/Mailman/mm_cfg.py ... Compiling /usr/local/mailman/Mailman/versions.py ... Traceback (most recent call last): File bin/update, line 46, in ? import paths File /usr/local/mailman/bin/paths.py, line 60, in ? import korean ImportError: No module named korean make: *** [update] Error 1 bash-3.00# Could this be because I am using Python 2.3.5 or my python doesn't have the korean module? Dave -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Tue 1/23/2007 7:27 PM To: Piniella, David A; Hank van Cleef Cc: Kent Taylor; mailman-users@python.org Subject: Re: [Mailman-Users] mailman install problem - Solaris Mark Sapiro wrote: Piniella, David A wrote: No dice, I tried that with gcc and yacc. Is there any way to just avoid the Japanese and Korean codecs packages' compilation, or to skip them entirely? I don't really need to host any lists in Japanese or Korean (or do these packages do something else?) This too is really tricky. See yesterday's take on this in the thread at http://mail.python.org/pipermail/mailman-users/2007-January/055498.html. I *think* the attached patch to misc/Makefile will solve the problem. Here's the procedure: After running 'configure' apply the attached patch to misc/Makefile. Then if you have a pythonlib/korean directory in your installation ($prefix) directory left over from previous attempts, remove it. Then 'make install' should give you a working installation. This installed version of the Korean codecs will not have the compiled C language modules, but if you aren't actually using Korean, the Python modules will be good enough - the only difference is performance. Let us know how it works out. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman install problem - Solaris
OK, for giggles, I updated python to 2.5 from 2.3.5, and now configure does this: checking for group name mailman... Traceback (most recent call last): File conftest.py, line 1, in module import grp ImportError: ld.so.1: python: fatal: libgcc_s.so.1: open failed: No such file or directory cat: cannot open conftest.out configure: error: * No mailman group found! * Your system must have a mailman group defined * (usually in your /etc/group file). Please see the INSTALL * file for details. bash-3.00# cat /etc/group | grep mailman mailman::100:mailman bash-3.00# ...what? Dave. -Original Message- From: [EMAIL PROTECTED] on behalf of Piniella, David A Sent: Tue 1/23/2007 9:56 PM To: Mark Sapiro; Hank van Cleef Cc: Kent Taylor; mailman-users@python.org Subject: Re: [Mailman-Users] mailman install problem - Solaris I did a make distclean, a new configure, patched, verified that my $prefix/pythonlib/ dir had no korean dir (a japanese dir though) and then make and make install and this is where it breaks: (a lot of listing and compiling, well after where it was breaking before and then ) Compiling /usr/local/mailman/Mailman/htmlformat.py ... Compiling /usr/local/mailman/Mailman/i18n.py ... Compiling /usr/local/mailman/Mailman/mm_cfg.py ... Compiling /usr/local/mailman/Mailman/versions.py ... Traceback (most recent call last): File bin/update, line 46, in ? import paths File /usr/local/mailman/bin/paths.py, line 60, in ? import korean ImportError: No module named korean make: *** [update] Error 1 bash-3.00# Could this be because I am using Python 2.3.5 or my python doesn't have the korean module? Dave -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Tue 1/23/2007 7:27 PM To: Piniella, David A; Hank van Cleef Cc: Kent Taylor; mailman-users@python.org Subject: Re: [Mailman-Users] mailman install problem - Solaris Mark Sapiro wrote: Piniella, David A wrote: No dice, I tried that with gcc and yacc. Is there any way to just avoid the Japanese and Korean codecs packages' compilation, or to skip them entirely? I don't really need to host any lists in Japanese or Korean (or do these packages do something else?) This too is really tricky. See yesterday's take on this in the thread at http://mail.python.org/pipermail/mailman-users/2007-January/055498.html. I *think* the attached patch to misc/Makefile will solve the problem. Here's the procedure: After running 'configure' apply the attached patch to misc/Makefile. Then if you have a pythonlib/korean directory in your installation ($prefix) directory left over from previous attempts, remove it. Then 'make install' should give you a working installation. This installed version of the Korean codecs will not have the compiled C language modules, but if you aren't actually using Korean, the Python modules will be good enough - the only difference is performance. Let us know how it works out. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dpiniella%40med.miami.edu Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
