Re: [Mailman-Users] Taking a stab at Mailman on Mac OS X

2009-11-26 Thread Larry Stone
On 11/26/09 12:12 AM, Larry Stone at lston...@stonejongleux.com wrote: > Also, search the archives as I have posted detailed instructions on > installing Mailman on Mac OS X. There is a version for Tiger (10.4) I posted > on 7/17/05. Now that I had time to do the search myself, the URL is

Re: [Mailman-Users] Taking a stab at Mailman on Mac OS X

2009-11-26 Thread Steve Burling
--On November 26, 2009 12:12:50 AM -0600 Larry Stone wrote: Also, search the archives as I have posted detailed instructions on installing Mailman on Mac OS X. There is a version for Tiger (10.4) I posted on 7/17/05. To which I reply: Also see:

Re: [Mailman-Users] Taking a stab at Mailman on Mac OS X

2009-11-25 Thread Larry Stone
On 11/25/09 9:32 PM, Bill Catambay at and...@excaliburworld.com wrote: > Is there anyone on this list who has successfully got Mailman running > on Mac OS? As Mark posted, you need to install the developer tools. Also, search the archives as I have posted detailed instructions on installing Ma

Re: [Mailman-Users] Taking a stab at Mailman on Mac OS X

2009-11-25 Thread Terri Oda
Mark Sapiro wrote: Bill Catambay wrote: I didn't get very far. I thought Mailman only required Python? Is there anyone on this list who has successfully got Mailman running on Mac OS? There is a small amount of compiled C code. You have to install the developer tools. This package is usually

Re: [Mailman-Users] Taking a stab at Mailman on Mac OS X

2009-11-25 Thread Mark Sapiro
Bill Catambay wrote: > >I didn't get very far. I thought Mailman only required Python? > >Is there anyone on this list who has successfully got Mailman running >on Mac OS? There is a small amount of compiled C code. You have to install the developer tools. This package is usually under optiona

[Mailman-Users] Taking a stab at Mailman on Mac OS X

2009-11-25 Thread Bill Catambay
Mailman v. 2.1.12 -> Mac OS 10.4.11 Tried to configure, and got the following results in config.log under Core Tests: configure:1714: checking for --with-python configure:1726: result: no configure:1733: checking for python configure:1751: found /Library/Frameworks/Python.framework/Versions/2