Re: LilyPond 2.13.10 (OSX) Font Issues

[Keaton Mowery]

Okay, I think I've tracked it down... Whew, autotools is a mess.
Anyways, here's the short story:

python-config reports information about the local python install.
Lilypond's configure scripts already use python-config, but in a
slightly different manner than my original hack (which is now
obsolete).

On OSX, "python-config --cflags" returns
"-I/System/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6
-I/System/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6
-fno-strict-aliasing -fno-common -dynamic -DNDEBUG -g -fwrapv -Os
-Wall -Wstrict-prototypes -DENABLE_DTRACE -arch i386 -arch ppc -arch
x86_64"

stepmake/aclocal.m4 attempts to remove some of the useless flags from
this, but my testing indicated that the sed command wasn't doing
anything. Also, the "-arch i386 -arch ppc -arch x86_64" flags were not
removed and caused errors elsewhere in the configure. I've attached a
small patch for aclocal.m4 that should properly strip unneeded and
dangerous cflags returned by python-config.

Unfortunately my font issues remain. Here's the configure output from
my new patched version of configure:
http://pastebin.com/m6c2433da
And the make output:
https://dl.dropbox.com/u/41619/homebrew_build.txt

Here's ./configure from a lilypond install via MacPorts (whose fonts
work properly):
http://pastebin.com/m2b4ce81
And the make output:
https://dl.dropbox.com/u/41619/macports_build.txt

Also, if you could point me in the direction of the second-phase font
selecting code (where my lilypond decides to print
[/usr/X11/lib/X11/fonts/TTF/Vera.ttf], etc), I can start poking around
in there to see what's going on. Thanks for your help!

Keaton


On Tue, Jan 19, 2010 at 6:44 PM, Patrick McCarty <address@hidden> wrote:
> 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
>

aclocal.patch
Description: Binary data