The esteemed Piniella, David A has said:
>
>
>
> 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
> import grp
> ImportError: ld.so.1: python:
Piniella, David A wrote:
>
>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
>import grp
>ImportError: ld.so.1: python: fatal: libgcc_s.so.1: open fail
Piniella, David A wrote:
>
>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 befo
p 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 - So
ark 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
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 somet
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
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,
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 Pin
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 --p
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/sb
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
m
Piniella, David A wrote:
>I have actually already renamed the /usr/ucb/cc (to cc_old) and modified my
>path (specifically for the install):
>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 j
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
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
snprintf
configure:2040: gcc -o conftest -g -O2 conftest.c 1>&5
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
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
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
Hello,
I am having trouble getting Mailman setup on my Redhat 8.0 machine. I'm
using Python version 2.2.1. I got most of it set up except the archived
messages part. I can admin lists, create lists, and add users to lists but
cannot view archives and Apache keeps giving me a "Symbolic link not
allo
* Á¤ Çϳç ([EMAIL PROTECTED]) wrote:
>
> I've installed mailman and tried to set up test list with admin's help, but
> got the following error and have not solved till now. :(
>
> The original message was received at Wed, 11 Dec 2002 15:59:11 +0900 (KST)
> from blahblah
>
>- The follow
I've installed mailman and tried to set up test list with admin's help, but
got the following error and have not solved till now. :(
The original message was received at Wed, 11 Dec 2002 15:59:11 +0900 (KST)
from blahblah
- The following addresses had permanent fatal errors -
"|/hom
21 matches
Mail list logo