On 8/16/06, Graham Dumpleton <grahamd@dscpl.com.au> wrote: 
>
> Huh!
>
> Do you have more than one version of Python installed?

Nope.  I just have Python from /usr/bin/python.  Nothing special.

> I do all my work on Mac OS X and have no problem. I only have the standard
> OSE supplied version of Python installed though.

Not sure what you mean by OSE - do you mean OS?  Anyway, I just rely
on what comes with the OS.

I'm sure it worked at some point, but that's probably years ago.

I have:

Python 2.3.5 (#1, Mar 20 2005, 20:38:20)
[GCC 3.3 20030304 (Apple Computer, Inc. build 1809)] on darwin

> FWIW, am using Mac OS X 10.4.7 at present.

So am I.

mod_python.so doesn't link as the LINKFORSHARED values don't expand
properly.  It's not even the right value to be bringing in from
Python's Makefile!

> Because of other stuff, have been ignoring the table object issues, but ma
ybe
> I should start paying more attention. :-)

I'm more than happy to fix up autoconf to stop doing the insanity with
sed and determine those values within Python directly.  I'll try to do
so this weekend: time permitting.  (Greg and I and the other SVN devs
solved this problem already within Subversion.)

However, since I can't build, this means that I can't debug this pool
problem.  =(  -- justin

[ Post a follow-up to this message ]

Justin Erenkrantz wrote ..
> On 8/16/06, Graham Dumpleton <grahamd@dscpl.com.au> wrote: 
> OS X. 
>
> Nope.  I just have Python from /usr/bin/python.  Nothing special.

Strange.
 
>
> Not sure what you mean by OSE - do you mean OS?  Anyway, I just rely
> on what comes with the OS.

I meant OS. My slip up was because I actually do make available a product
called OSE and so have a predilection for typing that. Same sort of thing
when I have to use cvs at one of my jobs, I always keep typing 'svn'. :-)

> mod_python.so doesn't link as the LINKFORSHARED values don't expand
> properly.  It's not even the right value to be bringing in from
> Python's Makefile!
> 
> maybe 
>
> I'm more than happy to fix up autoconf to stop doing the insanity with
> sed and determine those values within Python directly.  I'll try to do
> so this weekend: time permitting.  (Greg and I and the other SVN devs
> solved this problem already within Subversion.)

Would what you have in mind address the following in any way:

https://issues.apache.org/jira/browse/MODPYTHON-20

Or is that a separate unrelated problem?

Graham

[ Post a follow-up to this message ]

On 8/16/06, Graham Dumpleton <grahamd@dscpl.com.au> wrote: 
>
> Strange.

What does your LINKFORSHARED variable have?  See
/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/confi
g/Makefile.

Again I have:

LINKFORSHARED=-u __dummy -u _PyMac_Error -framework System
$(PYTHONFRAMEWORKDIR)/Versions/$(VERSION)/$(PYTHONFRAMEWORK)
-framework CoreServices -framework Foundation

> Would what you have in mind address the following in any way:
>
>   https://issues.apache.org/jira/browse/MODPYTHON-20
>
> Or is that a separate unrelated problem?

The issue is whether mod_python should compile with Python's flags or
httpd's flags.  Typically, when there's a conflict like that, goofy
things that happen.  But, yah, we could switch to getting compile
flags from apxs instead of trying to determine them ourselves or using
what Python has.  When I take a pass at fixing my build issues, I'll
commit what works for me and we can see how that fares...  -- justin

[ Post a follow-up to this message ]

On 17/08/2006, at 10:55 AM, Justin Erenkrantz wrote:

> On 8/16/06, Graham Dumpleton <grahamd@dscpl.com.au> wrote: 
>
> What does your LINKFORSHARED variable have?  See
> /System/Library/Frameworks/Python.framework/Versions/2.3/lib/
> python2.3/config/Makefile.
>
> Again I have:
>
> LINKFORSHARED=-u __dummy -u _PyMac_Error -framework System
> $(PYTHONFRAMEWORKDIR)/Versions/$(VERSION)/$(PYTHONFRAMEWORK)
> -framework CoreServices -framework Foundation

Same:

LINKFORSHARED=  -u __dummy -u _PyMac_Error -framework System $
(PYTHONFRAMEWORKDIR)/Versions/$(VERSION)/$(PYTHONFRAMEWORK) -
framework CoreServices -framework Foundation

LDSHARED in same file is:

LDSHARED=       $(CC) $(LDFLAGS) -bundle -undefined dynamic_lookup

With src/Makefile in mod_python source having:

LDFLAGS= -Wl,-framework,Python  -u __dummy -u _PyMac_Error -framework
System $(PYTHONFRAMEWORKDIR)/Versions/$(VERSION)/$(PYTHONFRAMEWORK) -
framework CoreServices -framework Foundation   -Wl,-F. -Wl,-F.

FWIW, my XCode version is:

xcode_2.3_8m1780_oz693620813.dmg

Also, dist/setup.py in mod_python source contains:

if sys.platform == "darwin":
if not '-undefined' in sysconfig.get_config_var("LDSHARED").split
():
sysconfig._config_vars["LDSHARED"] = \
string.replace(sysconfig.get_config_var("LDSHARED"), \
" -bundle "," -bundle -flat_namespace -undefined
suppress ")
sysconfig._config_vars["BLDSHARED"] = \
string.replace(sysconfig.get_config_var("BLDSHARED"), \
" -bundle "," -bundle -flat_namespace -undefined
suppress ")

But I think this was a workaround for older version of Mac OS X.

What is the actual error you are getting when building?


Graham

[ Post a follow-up to this message ]

On 8/17/06, Graham Dumpleton <grahamd@dscpl.com.au> wrote:
>Also, dist/setup.py in mod_python source contains:
>...
> But I think this was a workaround for older version of Mac OS X.
>
> What is the actual error you are getting when building?

Um, how are you building?

Per README, I'm running:

$ ./configure --with-apxs=/path/to/apxs --prefix=/path/to/install
$ make

and it just goes haywire.

dist/setup.py would never get called at all.  Why do I get a sense
you're not using autoconf or make?  -- justin

[ Post a follow-up to this message ]