[Mailman-Users] mailman install problem

[Piniella, David A]

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:vancleef at bronze.lostwells.net]
Sent: Tue 1/23/2007 3:52 PM
To: Piniella, David A
Cc: mailman-users at 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 (vancleef at lostwells.net, hvanclee at nyx.net)
1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming)
1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all"