CJ Keist wrote:
>Running the bash command came back to the prompt with no errors.
>
>
>On 8/7/10 10:26 AM, Mark Sapiro wrote:
>> bash -c 'for p in ; do echo Huh? $p ; done'
That's the expected result.
Per your immediately previous post, it seems the issue was some
incompatibility with a specifi
Running the bash command came back to the prompt with no errors.
On 8/7/10 10:26 AM, Mark Sapiro wrote:
bash -c 'for p in ; do echo Huh? $p ; done'
--
C. J. Keist Email: cj.ke...@colostate.edu
UNIX/Network ManagerPhone: 970-491-0630
Engineering Network Serv
Another update.
It looks to be a make problem. The make I used was in
/usr/ccs/bin. Using GNU make, in /usr/sfw/bin ran just fine.
On 8/7/10 10:26 AM, Mark Sapiro wrote:
- Original Message ---
Subject: Re: [Mailman-Users] mailman install problems (syntax error
atline1
- Original Message ---
Subject: Re: [Mailman-Users] mailman install problems (syntax error
atline1:`; ' unexpected)
From: CJ Keist
Date: Sat, 07 Aug 2010 09:25:19 -0600
To: Mark Sapiro
Cc: "Stephen J. Turnbull" ,
mailman-users@pytho
Mark Sapiro writes:
> I agree that the underlying issue is with the shell, but in at least
> these bash versions:
>
> GNU bash, version 3.2.49(22)-release (i686-pc-cygwin)
>
> GNU bash, version 3.2.48(1)-release (i386-apple-darwin10.0)
>
> GNU bash, version 3.1.17(1)-release (i686-redha
On Sat, 7 Aug 2010, Mark Sapiro wrote:
I agree that the underlying issue is with the shell, but in at least
these bash versions:
GNU bash, version 3.2.49(22)-release (i686-pc-cygwin)
GNU bash, version 3.2.48(1)-release (i386-apple-darwin10.0)
GNU bash, version 3.1.17(1)-release (i686-redhat-l
If this helps. I'm on Solaris 10 10/09 s10s_u8wos_08a SPARC. This make
installed failed with
tcsh - version 6.12.00
bash - version 3.00.16(1)
As for bourne shell, don't know how to get the version info.
On 8/7/10 9:13 AM, Mark Sapiro wrote:
Stephen J. Turnbull wrote:
Mark Sapiro writes
Stephen J. Turnbull wrote:
>Mark Sapiro writes:
> > CJ Keist wrote:
>
> > >I simply commented out the for p loop:
> > >
> > > #for p in $(PACKAGES); \
>
> > That is a perfectly acceptable workaround, but the question is why
> > doesn't your make properly handle
> >
> >for p in ; do
Mark Sapiro writes:
> CJ Keist wrote:
> >I simply commented out the for p loop:
> >
> > #for p in $(PACKAGES); \
> That is a perfectly acceptable workaround, but the question is why
> doesn't your make properly handle
>
>for p in ; do ... ; done
Because make doesn't (shoul
CJ Keist wrote:
>>
>I did try running in both sh and bash but still got same error.
>But I did get mailman to install. The problem was with the Makefile in
>the misc folder.
>
>EMAILPKG=
>JACODECSPKG=
>KOCODECSPKG=
>
>PACKAGES= $(EMAILPKG) $(JACODECSPKG) $(KOCODECSPKG)
>
>There were no packag
Thanks for the reply. See below for the solution I found.
On 8/5/10 10:10 PM, Gary R. Schmidt wrote:
On Thu, August 5, 2010 07:14, CJ Keist wrote:
Hi,
Trying to install mailman mailman-2.1.13rc on Solaris 10x86.
Getting an error when I try to do make install. I found similar post on
On Thu, August 5, 2010 07:14, CJ Keist wrote:
> Hi,
> Trying to install mailman mailman-2.1.13rc on Solaris 10x86.
> Getting an error when I try to do make install. I found similar post on
> this error on making sure using correct version of python. I have two
> version of python installed,
Hi,
Trying to install mailman mailman-2.1.13rc on Solaris 10x86.
Getting an error when I try to do make install. I found similar post on
this error on making sure using correct version of python. I have two
version of python installed, there is the native python that comes with
Solaris
Hi Mark,
Yes, that was a problem with my Python compiler.
I used another python compiler and I was successful.
Thanks!
Elvis
On 12/5/05, Mark Sapiro <[EMAIL PROTECTED]> wrote:
>
> Elvis Fernandes wrote:
> >
> >I tried manually running:
> >
> >isd80{mailman}8: /opt/local/bin/python -c 'from comp
Elvis Fernandes wrote:
>
>I tried manually running:
>
>isd80{mailman}8: /opt/local/bin/python -c 'from compileall import *;
>compile_dir("/mailman/mailman/Mailman")'
> File "", line 1
>from
> ^
>SyntaxError: invalid syntax
>isd80{mailman}9:
>
>Still no go.
It seems something is wrong wi
Hi Mark,
I tried manually running:
isd80{mailman}8: /opt/local/bin/python -c 'from compileall import *;
compile_dir("/mailman/mailman/Mailman")'
File "", line 1
from
^
SyntaxError: invalid syntax
isd80{mailman}9:
Still no go.
Elvis
On 12/5/05, Mark Sapiro <[EMAIL PROTECTED]> wrote
Elvis Fernandes wrote:
>
>I tried the following:
>
>isd80{mailman}2:
>isd80{mailman}2: /opt/local/bin/python
>Python 2.2.2 (#1, Jun 5 2003, 12:34:45)
>[GCC 3.2.1] on sunos5
>Type "help", "copyright", "credits" or "license" for more information.
from compileall import *
^D
>isd8
Hi Mark,
Thanks for responding.
I tried the following:
isd80{mailman}2:
isd80{mailman}2: /opt/local/bin/python
Python 2.2.2 (#1, Jun 5 2003, 12:34:45)
[GCC 3.2.1] on sunos5
Type "help", "copyright", "credits" or "license" for more information.
>>> from compileall import *
>>>
>>>
>>> ^D
isd80{m
Elvis Fernandes wrote:
>/opt/local/bin/python -c 'from compileall import *;
>compile_dir("/mailman/mailman/Mailman")'
> File "", line 1
>from
> ^
>SyntaxError: invalid syntax
>*** Error code 1
>make: Fatal error: Command failed for target `doinstall'
Presumably your MUA split
>/opt/loc
Hello,
I have been strugging all day to install mailman-2.1.6 on solaris8.
The configure goes thru successfully.
The make goes thru successfully.
When I do make install, it does a bunch of things and then I get the
following message:
Creating language directory /mailman/mailman/messages/tr/LC_M
Hi ,
I'm trying to install mailman in an SGI running IRIX6.5 with sendmail
and python 2.0.
Configuring and installing seems to go without problems.
I check permissions in /home/mailman and no errors are reported.
Start cron and then create a list and keep getting error reports from
cron sent to m
21 matches
Mail list logo
