On Oct 20, 12:53 am, "Graham Dumpleton" <[EMAIL PROTECTED]>
wrote:
> ...
> s,@abs_top_builddir@,/home/peter/src/python/mod-wsgi/mod_wsgi,svn/mod_wsgi,;t
> t
> ' Makefile.in
> + eval 'sed -f ./confstatm13299/subs-1.sed'
> ++ sed -f ./confstatm13299/subs-1.sed
> sed: -e expression #1, char 321: unknown option to `s'
>
> It looks like you are using a directory for holding source code which
> has a comma in it. Ie.,
>
> /home/peter/src/python/mod-wsgi/mod_wsgi,svn/mod_wsgi
>
> The presence of the command is stuffing up the patterns.
You are right, of course. I should have seen it.
Although, comma is a perfectly valid character (i.e. no need to escape
it) in a path on Unix.
One migh say autoconf should use a more esoteric character as pattern
delimiter
when dealing with a path.
Anyway, from a mod_wsgi point of view it was a false alarm. Removing
the comma from the
path, everything works fine.
Thank you for your help,
Peter
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en
-~----------~----~----~----~------~----~------~--~---
