On Fri, 26 Aug 2005, Nick wrote:
Here's another idea: Fail the flex test fairly silently (e.g. just "no"), but
fall back to a script that generates a nice, verbose error message explaining
the situation. That way, when the user tries to call "make" after modifying
the .l file, the fake flex
Nick wrote:
Jim,
I don't think it's too verbose, but maybe you could delay it to the end
of the configure script so you don't have to either interrupt with
control-C or scroll back to see what went "wrong."
Good point. I'll move it to the end. Since most systems still ship with
the older fl
Jim,
I don't think it's too verbose, but maybe you could delay it to the end of
the configure script so you don't have to either interrupt with control-C or
scroll back to see what went "wrong."
Here's another idea: Fail the flex test fairly silently (e.g. just "no"),
but fall back to a scri
Gregory (Grisha) Trubetskoy wrote:
OK, here is the flex scoop - as the the docs point out, anything before
2.5.31 is not reentrant and I think even uses a slightly different
interface so older flex won't even process the psp_parser.l file correctly.
Looking at Fedora Core 4, it still has fle
2005/8/19, Jim Gallacher <[EMAIL PROTECTED]>:
Gregory (Grisha) Trubetskoy wrote:>> OK, looks like the test failure that I was seeing was more caused by my> environment, so all tests pass.>> So we've got:>> 1. flex>
> 2. MacOS compile>> 3. http://issues.apache.org/jira/browse/MODPYTHON-72> Is this a
Oops, it's MacOSX 10.4.2, not MacOSX 1.4.2 -- sorry.
[zim:~] ron% gcc --version
powerpc-apple-darwin8-gcc-4.0.0 (GCC) 4.0.0 20041026 (Apple Computer, Inc.
build 4061)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
war
On 19/08/2005, at 8:01 PM, Graham Dumpleton wrote:Thus, setup.py will thus need to check first whether the -undefined optionalready exists. Thus, setup.py should use:if sys.platform == "darwin": if not '-bundle' in sysconfig.get_config_var("LDSHARED").split(): sysconfig._config_va
On 19/08/2005, at 7:57 AM, Graham Dumpleton wrote:On 19/08/2005, at 2:59 AM, Jim Gallacher wrote: Ron Reisor wrote: Hello,I ran into a problem with the loader on MacOSX.MaxOSX 1.4.2python 2.4.1apache 2.0.54The loader seems to not like the "-undefined suppress" arguments in the final load.I modified
On 19/08/2005, at 2:59 AM, Jim Gallacher wrote:
Ron Reisor wrote:
Hello,
I ran into a problem with the loader on MacOSX.
MaxOSX 1.4.2
python 2.4.1
apache 2.0.54
The loader seems to not like the "-undefined suppress" arguments in
the final load.
I modified dist/setup.py by removing the two "-u
Gregory (Grisha) Trubetskoy wrote:
OK, here is the flex scoop - as the the docs point out, anything before
2.5.31 is not reentrant and I think even uses a slightly different
interface so older flex won't even process the psp_parser.l file correctly.
Looking at Fedora Core 4, it still has fle
+1 on Win32 with Python 2.4. Here is how I tested it :
1) Switched to the 3.2.0-BETA tag
2) Update
3) cd dist & build_installer.bat
4) Got this installer, that you can also download :
http://nicolas.lehuen.com/download/mod_python/mod_python-3.2.0-BETA.win32-py2.4.exe
5) Ran the installer, everyt
Hello,
I ran into a problem with the loader on MacOSX.
MaxOSX 1.4.2
python 2.4.1
apache 2.0.54
The loader seems to not like the "-undefined suppress" arguments in the
final load.
I modified dist/setup.py by removing the two "-undefined suppress" and ran
configure and make again and the new
A few comments:
1. If you have an older version of flex than that expected, it gives
message:
checking flex version... configure: WARNING: Flex version 2.5.31 or
greater is required. The one you have seems to be 2.5.4. Use
--with-flex to specify another.
There is nothing in the README des
OK, I think I have a -1 :-(
checking for flex... no
configure: error: flex binary not found in path
flex shouldn't be required for build since the flex-generated psp_parser.c
is already included?
Aside from this I had a few tests fail - I'll have to take a look at the
details tomorrow. This
Here are the rules:
In order for a file to be officially announced, it has to be tested by
developers on the dev list. Anyone subscribed to this list can (and
should feel obligated to :-) ) test it, and provide feedback *to _this_
list*! (Not the [EMAIL PROTECTED] list, and preferably not me
15 matches
Mail list logo
