On 2010-01-14, Keaton Mowery wrote:
> Here's the ./configure output:
> 
> http://pastebin.com/m3daee40b

Hmm.  I don't see anything wrong/unusual about this output.

Also, your patch below doesn't affect later behavior, so your font
issue is still unresolved.

Can you compile LilyPond on different machines to compare logs of
"configure", "make", etc. ?  I don't know how else I would debug this
problem, since I've never seen these specific symptoms before.

> I did modify the configure script to use the python-config program on
> OSX, the patch is below. I'm fairly sure that this won't change later
> behavior.
> 
> ----------------------------------------------------
> diff --git a/configure b/configure
> index 914184d..a54bb09 100755
> --- a/configure
> +++ b/configure
> @@ -790,6 +790,7 @@ with_localedir
>  with_lang
>  with_python_include
>  with_python_lib
> +with_python_config
>  '
>        ac_precious_vars='build_alias
>  host_alias
> @@ -8635,6 +8636,11 @@ $as_echo "$as_me: WARNING: Usage:
> --with-python-lib=name" >&2;}
> 
>  fi
> 
> +if test "${with_python_config+set}" = set; then
> +       withval=$with_python_config;
> +       PYTHON_CFLAGS="`python-config --includes`"
> +       LDFLAGS="$LDFLAGS `python-config --ldflags`"
> +fi
> 
>      for ac_prog in python-config
>  do
> 

Can you explain why you need this?  This is a little over my head.

If you want to get this integrated with LilyPond, you'll need to patch
the higher-level autoconf files, since "configure" is autogenerated.

It looks like stepmake/aclocal.m4 is where the various python-config
checks are made.


Thanks,
Patrick


_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to