Carey Evans wrote:
> I've tried out the Python support, and I've found some problems with
> the configure.in code. Some of this might be because my /bin/sh is
> ash, not bash.
>
> When running configure, I get the following output:
>
> checking for python... /usr/bin/python
> checking for python prefix... Traceback (innermost last):
> File "<stdin>", line 3, in ?
> NameError: EOF
> /usr
> checking for python version... Traceback (innermost last):
> File "<stdin>", line 3, in ?
> NameError: EOF
> 1.5
>
> Part of the problem is that the <<EOF isn't being recognised by the
> shell. There's also that standard error should be getting redirected
> to config.log.
>
> Instead of the quite complicated code to work out the Python version,
> I'd suggest:
>
> PYTHON_VERSION="`$PYTHON -c 'import sys; print sys.version[[:3]]' 2>&5`"
>
> with similar code for PYTHON_PREFIX.
>
> Looking at the configure.in, I also wonder why the glib.m4 code that
> comes with glib isn't being used to set CFLAGS and LIBS, making it a
> lot simpler. This patch makes both these changes.
There was a historic problem with the GLIB macro, and I just got in the
habit of doing it manually a long time back <g> I even forgot what the
problem was.
I'm not sure why the <<EOF thing didn't work under ash, but I like yours
better anyway. I can't imagine using ash as a default shell (*shudder*
I can barely stand using it on rescue disks), but if you must <g> My
experience has been that ksh is the default shell on most systems (AIX,
sco?, and something else which I can't remember), bsh on others, bash on
Solaris and Linux. I've never used *BSD, but I assumed it was bash
there as well.
Patch applied to CVS.
+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to [EMAIL PROTECTED]
| To subscribe to this list send email to [EMAIL PROTECTED]
| To unsubscribe from this list send email to [EMAIL PROTECTED]
| Questions should be directed to the list owner/operator: [EMAIL PROTECTED]
+---
