David Feuer | 1 Mar 03:47 2007
Picon

Spacing vocal music

After looking (fruitlessly) through the manual, checking a bit through
the mailing list archives, and experimenting over and over, I think I
may have figured out the problem I'm having, as well as a hint of its
solution.  It appears that LilyPond sets horizontal spacing for vocal
music without regard for #'shortest-duration-space or
#'spacing-increment.  The result is (to me) ugly and difficult to
read, and utterly unlike any other vocal music I've seen.  If I am
wrong, or if there is a good way to work around this, I would love to
hear about it.

My thoughts on a possible solution (rough, because I don't know any of
the program details):

The natural space following a note in vocal music (the amount of space
it will have if ragged-right is in effect) should never be less than
the space calculated as usual using #'shortest-duration-space and
#'spacing-increment.  The current behavior could be obtained by
setting these to 0 in vocal sections (using a new spacing area), or
(probably better--see below) by using different variables to control
spacing in vocal and non-vocal sections.

If the lyrics font size is set to 0 throughout the piece, the music
should be engraved exactly the way it would be if there were no lyrics
(except for vertical spacing).

If possible, it would be nice for the effective
vocal-shortest-duration-space to be set based on something roughly
like the third quartile of the lengths of the syllables attached to
the common shortest notes, but never tighter than the user-set
vocal-shortest-duration-space.  That way, the text would be fairly
(Continue reading)

serkan.tas | 1 Mar 08:24 2007
Picon

makam.ly

hi all,
 
Does any body know who is in charge with makam.ly ?
 
thanx
 
serkan.
 

www.turkcell.com.tr Bu elektronik posta ve onunla iletilen bütün dosyalar sadece göndericisi tarafindan almasi amaclanan yetkili gercek ya da tüzel kisinin kullanimi icindir. Eger söz konusu yetkili alici degilseniz bu elektronik postanin icerigini aciklamaniz, kopyalamaniz, yönlendirmeniz ve kullanmaniz kesinlikle yasaktir ve bu elektronik postayi derhal silmeniz gerekmektedir.

TURKCELL bu mesajin icerdigi bilgilerin doğruluğu veya eksiksiz oldugu konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin ne sekilde olursa olsun iceriginden, iletilmesinden, alinmasindan ve saklanmasindan sorumlu degildir. Bu mesajdaki görüsler yalnizca gönderen kisiye aittir ve TURKCELLin görüslerini yansitmayabilir

Bu e-posta bilinen bütün bilgisayar virüslerine karsi taranmistir.

This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is strictly prohibited, and the e-mail should immediately be deleted.

TURKCELL makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. The opinions expressed in this message belong to sender alone and may not necessarily reflect the opinions of TURKCELL.

This e-mail has been scanned for all known computer viruses.

_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Mats Bengtsson | 1 Mar 09:18 2007
Picon
Picon

Re: makam.ly

See http://lists.gnu.org/archive/html/lilypond-user/2007-01/msg00748.html

   /Mats

serkan.tas <at> turkcell.com.tr wrote:
> hi all,
>  
> Does any body know who is in charge with makam.ly ?
>  
> thanx
>  
> serkan.
>  
>
> www.turkcell.com.tr <http://www.turkcell.com.tr>
>
> ------------------------------------------------------------------------
> Bu elektronik posta ve onunla iletilen bütün dosyalar sadece 
> göndericisi tarafindan almasi amaclanan yetkili gercek ya da tüzel 
> kisinin kullanimi icindir. Eger söz konusu yetkili alici degilseniz bu 
> elektronik postanin icerigini aciklamaniz, kopyalamaniz, 
> yönlendirmeniz ve kullanmaniz kesinlikle yasaktir ve bu elektronik 
> postayi derhal silmeniz gerekmektedir.
>
> TURKCELL bu mesajin icerdigi bilgilerin doğruluğu veya eksiksiz oldugu 
> konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin 
> ne sekilde olursa olsun iceriginden, iletilmesinden, alinmasindan ve 
> saklanmasindan sorumlu degildir. Bu mesajdaki görüsler yalnizca 
> gönderen kisiye aittir ve TURKCELLin görüslerini yansitmayabilir
>
> Bu e-posta bilinen bütün bilgisayar virüslerine karsi taranmistir.
>
> ------------------------------------------------------------------------
> This e-mail and any files transmitted with it are confidential and 
> intended solely for the use of the individual or entity to whom they 
> are addressed. If you are not the intended recipient you are hereby 
> notified that any dissemination, forwarding, copying or use of any of 
> the information is strictly prohibited, and the e-mail should 
> immediately be deleted.
>
> TURKCELL makes no warranty as to the accuracy or completeness of any 
> information contained in this message and hereby excludes any 
> liability of any kind for the information contained therein or for the 
> information transmission, reception, storage or use of such in any way 
> whatsoever. The opinions expressed in this message belong to sender 
> alone and may not necessarily reflect the opinions of TURKCELL.
>
> This e-mail has been scanned for all known computer viruses.
>
> ------------------------------------------------------------------------
> ------------------------------------------------------------------------
>
> _______________________________________________
> lilypond-devel mailing list
> lilypond-devel <at> gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
>   

--

-- 
=============================================
	Mats Bengtsson
	Signal Processing
	Signals, Sensors and Systems
	Royal Institute of Technology
	SE-100 44  STOCKHOLM
	Sweden
	Phone: (+46) 8 790 8463				
        Fax:   (+46) 8 790 7260
	Email: mats.bengtsson <at> ee.kth.se
	WWW: http://www.s3.kth.se/~mabe
=============================================
greg A Wissing | 1 Mar 15:58 2007
Picon

lilypond

LS,

A few times I have stumbled upon this Lilypond project of yours. What an
 incredible amount of work has been done, and the print results of the 
scores look splendid indeed.
But, I am amazed, if not stupefied in amazement, that with such a capital
of knowledge nobody in your ranks has thought of making a decent 
working user interface of this magnificent software.
I think it can be done, and should be done next as a logical step in the 
development process.
For me, and I'm sure a lot of other music people, using the asci keyboard 
along with a prof. level of programming parlance is out of reach, sort of 
acabadabra.
Yes, we composers are very interested in a score notator that can write 
ANYthing, and do it well. But most of us are want a tool that is both 
comprehensive and intuitive. It seems to me that you are almost there, if
 I understand it well, even MIDI files can be edited!. With a little effort you 
can beat Finale and others.
What is there against the use of the mouse, and who cares if Lilypond 
ends up to be a fine composing app. with top rank score possibilities?
Along with that, I read comment in your files about Finale, but have you 
ever looked into Logic, Cubase and Sibelius? The competition is not doing 
so bad at all in the score field, yes, there are severe shortcomings, but 
things are not half as bad as in your comparisons.
If, in developing such an interface, I can be of assistance I would be glad 
to get involved in one way or another.
I am both a composer and a graphic designer. I do have an insight in what 
an interface should do. 

Sincerely,
Gregory Wissing
Mats Bengtsson | 1 Mar 16:14 2007
Picon
Picon

Re: lilypond

If you search the mailing list archives, you will find a number of related
discussions. See also the related questions at 
http://lilypond.org/web/about/faq
Note that several people on the mailing list have testified that they 
can enter the
music much faster using the LilyPond text format than using a graphical 
interface
or a MIDI keyboard.

   /Mats

greg A Wissing wrote:
> LS,
>
> A few times I have stumbled upon this Lilypond project of yours. What an
>  incredible amount of work has been done, and the print results of the 
> scores look splendid indeed.
> But, I am amazed, if not stupefied in amazement, that with such a capital
> of knowledge nobody in your ranks has thought of making a decent 
> working user interface of this magnificent software.
> I think it can be done, and should be done next as a logical step in the 
> development process.
> For me, and I'm sure a lot of other music people, using the asci keyboard 
> along with a prof. level of programming parlance is out of reach, sort of 
> acabadabra.
> Yes, we composers are very interested in a score notator that can write 
> ANYthing, and do it well. But most of us are want a tool that is both 
> comprehensive and intuitive. It seems to me that you are almost there, if
>  I understand it well, even MIDI files can be edited!. With a little effort you 
> can beat Finale and others.
> What is there against the use of the mouse, and who cares if Lilypond 
> ends up to be a fine composing app. with top rank score possibilities?
> Along with that, I read comment in your files about Finale, but have you 
> ever looked into Logic, Cubase and Sibelius? The competition is not doing 
> so bad at all in the score field, yes, there are severe shortcomings, but 
> things are not half as bad as in your comparisons.
> If, in developing such an interface, I can be of assistance I would be glad 
> to get involved in one way or another.
> I am both a composer and a graphic designer. I do have an insight in what 
> an interface should do. 
>
> Sincerely,
> Gregory Wissing
>
>
>
>
>  
>
>
>
> _______________________________________________
> lilypond-devel mailing list
> lilypond-devel <at> gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
>   

--

-- 
=============================================
	Mats Bengtsson
	Signal Processing
	Signals, Sensors and Systems
	Royal Institute of Technology
	SE-100 44  STOCKHOLM
	Sweden
	Phone: (+46) 8 790 8463				
        Fax:   (+46) 8 790 7260
	Email: mats.bengtsson <at> ee.kth.se
	WWW: http://www.s3.kth.se/~mabe
=============================================
Till Rettig | 1 Mar 16:41 2007
Picon
Picon

Re: lilypond

Well, I think the most promising project at the moment is canorus at 
http://canorus.berlios.de/ which is not a directly what you are looking 
for, but I think it shows much better the structure that a frontend to 
the lilypond generator should have: not so much one big block of 
software but modules that can be combined. The same goes for the 
lilypond-tool which is already a great enhancement. And I would think 
that in future all these products could easily be linked to one common 
page from where they can be downloaded, so if I would like to edit my 
scores with a graphic front end I would download that one, but if I 
would like the more direct way, I can get it also. And they could be 
combined in future.
In my point of view it is not so much about the input language (which is 
not so difficult at all) but more about the ability of intuitively 
tweaking properties. The direkt input language is really easy, but when 
you start wanting something special you will really have to start 
learning strange commands...
I agree that the linking of an optical representation back to the 
original output is probably not trivial at all, and so canorus' way is 
not to show the final picture of the output but an scematic version 
whith all the elements existing but not arranged yet in the final way. 
So where would you start here to tweak the output in order to get better 
results?
But maybe it should also be clear that some graphical special effects 
doesn't necessarily have to be *inside* the program but can be added 
easily afterwards using vector graphic programs. Thus they would have to 
be applied every time you change your file and compile it again, so it 
resembles somewhat the old way of note engraving. But in the end also 
this could be automated by adding a second language layout layer upon 
the lilypond file which defines the graphic corrections that have been 
done afterwards and include this file into the compilation process.

Just some thoughts about the topic...
Greetings
Till

Mats Bengtsson wrote:
> If you search the mailing list archives, you will find a number of 
> related
> discussions. See also the related questions at 
> http://lilypond.org/web/about/faq
> Note that several people on the mailing list have testified that they 
> can enter the
> music much faster using the LilyPond text format than using a 
> graphical interface
> or a MIDI keyboard.
>
>   /Mats
>
> greg A Wissing wrote:
>> LS,
>>
>> A few times I have stumbled upon this Lilypond project of yours. What an
>>  incredible amount of work has been done, and the print results of 
>> the scores look splendid indeed.
>> But, I am amazed, if not stupefied in amazement, that with such a 
>> capital
>> of knowledge nobody in your ranks has thought of making a decent 
>> working user interface of this magnificent software.
>> I think it can be done, and should be done next as a logical step in 
>> the development process.
>> For me, and I'm sure a lot of other music people, using the asci 
>> keyboard along with a prof. level of programming parlance is out of 
>> reach, sort of acabadabra.
>> Yes, we composers are very interested in a score notator that can 
>> write ANYthing, and do it well. But most of us are want a tool that 
>> is both comprehensive and intuitive. It seems to me that you are 
>> almost there, if
>>  I understand it well, even MIDI files can be edited!. With a little 
>> effort you can beat Finale and others.
>> What is there against the use of the mouse, and who cares if Lilypond 
>> ends up to be a fine composing app. with top rank score possibilities?
>> Along with that, I read comment in your files about Finale, but have 
>> you ever looked into Logic, Cubase and Sibelius? The competition is 
>> not doing so bad at all in the score field, yes, there are severe 
>> shortcomings, but things are not half as bad as in your comparisons.
>> If, in developing such an interface, I can be of assistance I would 
>> be glad to get involved in one way or another.
>> I am both a composer and a graphic designer. I do have an insight in 
>> what an interface should do.
>> Sincerely,
>> Gregory Wissing
>>
>>
>>
>>
>>  
>>
>>
>>
>> _______________________________________________
>> lilypond-devel mailing list
>> lilypond-devel <at> gnu.org
>> http://lists.gnu.org/mailman/listinfo/lilypond-devel
>>   
>
Johannes Schindelin | 1 Mar 18:16 2007
Picon
Picon

Re: lilypond

Hi,

On Thu, 1 Mar 2007, greg A Wissing wrote:

> A few times I have stumbled upon this Lilypond project of yours. What an
>  incredible amount of work has been done, and the print results of the 
> scores look splendid indeed.

Thank you very much!

> But, I am amazed, if not stupefied in amazement, that with such a 
> capital of knowledge nobody in your ranks has thought of making a decent 
> working user interface of this magnificent software.

There is indeed a lot of knowledge in LilyPond. However, those who know 
how to write nice GUIs, and those who know how to craft elegant algorithms 
for elegant sheet music, usually form two mutual exclusive groups of 
people.

However, given people who actually put a lot of effort into it, I have no 
problem to believe that a nice GUI could be either put on top of LilyPond, 
or even be integrated.

Ciao,
Dscho
Werner LEMBERG | 1 Mar 19:25 2007
Picon

Re: lilypond


> However, given people who actually put a lot of effort into it, I
> have no problem to believe that a nice GUI could be either put on
> top of LilyPond, or even be integrated.

I doubt that the latter will happen soon: Today's processors are
simply far too slow.  Compare this with TeX about 20 years ago.

    Werner
Johannes Schindelin | 1 Mar 19:39 2007
Picon
Picon

Re: lilypond

Hi,

On Thu, 1 Mar 2007, Werner LEMBERG wrote:

> > However, given people who actually put a lot of effort into it, I
> > have no problem to believe that a nice GUI could be either put on
> > top of LilyPond, or even be integrated.
> 
> I doubt that the latter will happen soon: Today's processors are
> simply far too slow.  Compare this with TeX about 20 years ago.

Ssh. I tried to trick him into contributing to LilyPond!

Ciao,
Dscho
Joe Neeman | 2 Mar 00:05 2007
Picon

gub fails on odcctools

make -f lilypond.make bootstrap fails on odcctools. I've stuck the full output 
at the bottom of this email just in case it has something I've missed, but 
the basic problem is that (struct ranlib).ran_un doesn't have an element 
ran_name.

I've traced this to the definition of struct ranlib in 
target/darwin-ppc/src/odcctools-20060413/include/mach-o/ranlib.h:
struct  ranlib {
    union {
        uint32_t        ran_strx;       /* string table index of */
#ifndef __LP64__
        char            *ran_name;      /* symbol defined by */
#endif
    } ran_un;
    uint32_t            ran_off;        /* library member at this offset */
};

I added an
#else
#error "foo"
after the definition of ran_name and it turns out that __LP64__ is defined. I 
would have thought that it shouldn't be, given that I am cross-compiling for 
a 32-bit system. What do I do now?

invoking cd /programming/lilypond/target/darwin-ppc/build/odcctools-20060413 
&& /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/configure
--prefix=/programming/lilypond/target/darwin-ppc/install/odcctools-20060413-root/usr
--program-prefix=powerpc-apple-darwin7-
--prefix=/programming/lilypond/target/darwin-ppc/system/usr/cross/
--with-slibdir=/usr/lib/ --target=powerpc-apple-darwin7
--with-sysroot=/programming/lilypond/target/darwin-ppc/system/ --disable-multilib
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... powerpc-apple-darwin7
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for ranlib... ranlib
checking for ar... ar
checking for configured assembler targets... ppc ppc64 i386
checking if -mdynamic-no-pic is supported... no
checking if -fno-builtin-round is supported... yes
checking if -fno-builtin-trunc is supported... yes
checking if -no-cpp-precomp is supported... no
checking if -Wall is supported... yes
checking if -Wno-long-double is supported... no
checking if -Wno-import is supported... yes
checking if -x objective-c is supported... no
checking if __private_extern__ is supported... no
checking if -multiply_defined suppress is supported... no
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for max unsigned long long... 18446744073709551615ULL
checking for strmode... no
checking for qsort_r... no
checking for qsort... yes
checking for getattrlist... no
checking for NSIsSymbolNameDefined... no
checking whether getc_unlocked is declared... yes
checking whether byte ordering is bigendian... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating include/Makefile
config.status: creating libstuff/Makefile
config.status: creating libmacho/Makefile
config.status: creating ar/Makefile
config.status: creating as/Makefile
config.status: creating as/ppc/Makefile
config.status: creating as/ppc64/Makefile
config.status: creating as/i386/Makefile
config.status: creating ld/Makefile
config.status: creating ld64/Makefile
config.status: creating man/Makefile
config.status: creating misc/Makefile
config.status: creating otool/Makefile
config.status: creating include/config.h
substituting 
in /programming/lilypond/target/darwin-ppc/build/odcctools-20060413/Makefile
'ld64' -> ''
invoking 
mv /programming/lilypond/target/darwin-ppc/build/odcctools-20060413/Makefile /programming/lilypond/target/darwin-ppc/build/odcctools-20060413/Makefile~
 *** Stage: compile (odcctools)
invoking cd /programming/lilypond/target/darwin-ppc/build/odcctools-20060413 
&& make  -j2
make[1]: Entering directory 
`/programming/lilypond/target/darwin-ppc/build/odcctools-20060413'
cd libstuff && make
cd include && make
make[2]: Entering directory 
`/programming/lilypond/target/darwin-ppc/build/odcctools-20060413/libstuff'
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
allocate.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/allocate.c
make[2]: Entering directory 
`/programming/lilypond/target/darwin-ppc/build/odcctools-20060413/include'
make[2]: Nothing to be done for `default'.
make[2]: Leaving directory 
`/programming/lilypond/target/darwin-ppc/build/odcctools-20060413/include'
cd libmacho && make
make[2]: Entering directory 
`/programming/lilypond/target/darwin-ppc/build/odcctools-20060413/libmacho'
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc -c -o 
arch.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libmacho/arch.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
errors.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/errors.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
arch.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/arch.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc -c -o 
emulated.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/emulated.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
execute.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/execute.c
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/emulated.c: 
In function 'vm_allocate':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/emulated.c:67: 
warning: cast from pointer to integer of different size
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/emulated.c: 
In function 'map_fd':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/emulated.c:105: 
warning: cast from pointer to integer of different size
ar cru libmacho.a arch.o emulated.o
ranlib libmacho.a
make[2]: Leaving directory 
`/programming/lilypond/target/darwin-ppc/build/odcctools-20060413/libmacho'
cd man && make
make[2]: Entering directory 
`/programming/lilypond/target/darwin-ppc/build/odcctools-20060413/man'
make[2]: Nothing to be done for `default'.
make[2]: Leaving directory 
`/programming/lilypond/target/darwin-ppc/build/odcctools-20060413/man'
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
bytesex.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/bytesex.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
round.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/round.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
hppa.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/hppa.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
swap_headers.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/swap_headers.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
reloc.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/reloc.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
version_number.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/version_number.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
get_toc_byte_sex.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/get_toc_byte_sex.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
best_arch.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/best_arch.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
fatals.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/fatals.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
arch_usage.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/arch_usage.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
ofile.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/ofile.c
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/ofile.c: 
In function 'ofile_map':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/ofile.c:743: 
warning: dereferencing type-punned pointer will break strict-aliasing rules
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/ofile.c: 
In function 'ofile_unmap':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/ofile.c:1238: 
warning: cast from pointer to integer of different size
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/ofile.c: 
In function 'ofile_first_member':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/ofile.c:1652: 
warning: implicit declaration of function 'temporary_archive_member_warning'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/ofile.c:3761:8: 
warning: extra tokens at end of #endif directive
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
ofile_error.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/ofile_error.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
print.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/print.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
set_arch_flag_name.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/set_arch_flag_name.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
seg_addr_table.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/seg_addr_table.c
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/seg_addr_table.c: 
In function
'parse_seg_addr_table':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/seg_addr_table.c:103: 
warning: dereferencing type-punned pointer will break strict-aliasing rules
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/seg_addr_table.c: 
In function
'process_seg_addr_table':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/seg_addr_table.c:257: 
warning: dereferencing type-punned pointer will break strict-aliasing rules
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
dylib_table.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/dylib_table.c
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/dylib_table.c: 
In function 'parse_dylib_table':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/dylib_table.c:75: 
warning: dereferencing type-punned pointer will break strict-aliasing rules
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
breakout.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/breakout.c
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
writeout.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c: 
In function 'writeout':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:131: 
warning: dereferencing type-punned pointer will break strict-aliasing rules
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:264: 
warning: cast from pointer to integer of different size
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c: 
In function 'writeout_to_mem':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:382: 
warning: dereferencing type-punned pointer will break strict-aliasing rules
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c: 
In function 'make_table_of_contents':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1021: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1036: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1129: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c: 
In function 'ranlib_name_qsort':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1232: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c: 
In function 'check_sort_ranlibs':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1280: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1297: 
error: 'union <anonymous>' has no member named 'ran_name'
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1304: 
error: 'union <anonymous>' has no member named 'ran_name'
gcc -Wall -Wno-import  -DHAVE_CONFIG_H -D__LITTLE_ENDIAN__=1
-D_MACH_I386_THREAD_STATUS_FPSTATE_LEGACY_FIELD_NAMES_
-D_ARCHITECTURE_I386_FPU_FPSTATE_LEGACY_FIELD_NAMES_  -I..//include
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include -include
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/extern.h
-I/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/include/foreign -g -O2
-fno-builtin-round -fno-builtin-trunc   -c -o 
checkout.o /programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/checkout.c
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c: 
In function 'ranlib_name_qsort':
/programming/lilypond/target/darwin-ppc/src/odcctools-20060413/libstuff/writeout.c:1233: 
warning: control reaches end of non-void function
make[2]: *** [writeout.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory 
`/programming/lilypond/target/darwin-ppc/build/odcctools-20060413/libstuff'
make[1]: *** [libstuff] Error 2
make[1]: Leaving directory 
`/programming/lilypond/target/darwin-ppc/build/odcctools-20060413'
Command barfed: 
cd /programming/lilypond/target/darwin-ppc/build/odcctools-20060413 && 
make  -j2
Traceback (most recent call last):
  File "gub-builder.py", line 339, in ?
    main ()
  File "gub-builder.py", line 332, in main
    run_builder (options, settings, pm, deps, spec_object_dict)
  File "gub-builder.py", line 256, in run_builder
    run_one_builder (options, spec)
  File "gub-builder.py", line 195, in run_one_builder
    (available[stage]) ()
  File "lib/gub.py", line 413, in compile
    self.system ('cd %(builddir)s && %(compile_command)s')
  File "lib/context.py", line 145, in system
    verbose=self.verbose)
  File "lib/oslog.py", line 67, in system
    self.system_one (i, call_env, ignore_errors)
  File "lib/oslog.py", line 37, in system_one
    raise SystemFailed (m)
misc.SystemFailed: Command barfed: 
cd /programming/lilypond/target/darwin-ppc/build/odcctools-20060413 && 
make  -j2

make: *** [cross-compilers] Error 1

Gmane