denemo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] The lilypond build system adopted to build Denemo for


From: Jan Nieuwenhuizen
Subject: Re: [Denemo-devel] The lilypond build system adopted to build Denemo for various OS
Date: Mon, 13 Jul 2009 14:01:11 +0200

On ma, 2009-07-13 at 11:34 +0100, Richard Shann wrote:
> On Sun, 2009-07-12 at 19:47 +0200, Jan Nieuwenhuizen wrote:
> > On zo, 2009-07-12 at 17:00 +0100, Richard Shann wrote:
> > > On Sun, 2009-07-12 at 13:19 +0200, Jan Nieuwenhuizen wrote:
> > > > On zo, 2009-07-12 at 10:08 +0100, Richard Shann wrote:
> > libtool: link: rm -fr  .libs/libasprintf.a .libs/libasprintf.la 
> > .libs/libasprintf.lai .libs/libasprintf.so .libs/libasprintf.so.0 
> > .libs/libasprintf.so.0.0.0
> > libtool: link: g++ -shared -nostdlib 
> > /usr/lib/gcc/x86_64-linux-gnu/4.3.3/../../../../lib/crti.o 
> > /usr/lib/gcc/x86_64-linux-gnu/4.3.3/crtbeginS.o  .libs/lib-asprintf.o 
> > .libs/autosprintf.o   -L/home/janneke/vc/gub/target/tools/root/usr/lib 
> > -L/home/janneke/vc/gub/target/tools/root/usr/lib/../lib 
> > -L/usr/lib/gcc/x86_64-linux-gnu/4.3.3 
> > -L/usr/lib/gcc/x86_64-linux-gnu/4.3.3/../../../../lib -L/lib/../lib 
> > -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.3.3/../../.. -lstdc++ 
> > -lm -lc -lgcc_s /usr/lib/gcc/x86_64-linux-gnu/4.3.3/crtendS.o 
> > /usr/lib/gcc/x86_64-linux-gnu/4.3.3/../../../../lib/crtn.o    -Wl,-soname 
> > -Wl,libasprintf.so.0 -o .libs/libasprintf.so.0.0.0

> when I try to force a make the line you have that makes the .so.0.0.0
> just does not exist:

At least that makes some sense: it isn't being built.
  
> Here is the diff -u of the script libtool, having looked through it I
> can't claim to be much the wiser...

You can't? 

Well, this is pretty devastating.  You are not using GCC, or at least
configure/libtool does not recognise it as GCC, and it cannot find
G++

>  # A language specific compiler.
> -CC="g++"
> +CC=""
 
>  # Is the compiler the GNU compiler?
> -with_gcc=yes
> +with_gcc=

Ouch, no GCC?  So also

>  # Compiler flag to turn off builtin functions.
> -no_builtin_flag=" -fno-builtin"
> +no_builtin_flag=""

...no nice gcc flags...

>  # How to pass a linker flag through the compiler.
> -wl="-Wl,"
> +wl=""

...no way to talk to the linker through CC...
 
>  # Additional compiler flags for building library objects.
> -pic_flag=" -fPIC -DPIC"
> +pic_flag=""

...no idea of how to build shared code... (think: libasprintf.so.0.0.0)

>  # Compiler flag to prevent dynamic linking.
> -link_static_flag="-static"
> +link_static_flag=""

...so we need no -static flags, assume always building everything
staticly...
 
>  # Does compiler simultaneously support -c and -o options?
> -compiler_c_o="yes"
> +compiler_c_o=""

...no compile/output flags...

>  # Whether we are building with GNU ld or not.
> -with_gnu_ld="yes"
> +with_gnu_ld=""

...no GNU linker...

>  # Flag to hardcode $libdir into a binary during linking.
>  # This must work even if $libdir does not exist
> -hardcode_libdir_flag_spec="\${wl}-rpath \${wl}\$libdir"
> +hardcode_libdir_flag_spec=""

...no way to use rpath: relocated executables will be broken lateron...
 
> -postdeps="-lstdc++ -lm -lgcc_s -lc -lgcc_s"
> +postdeps=""

no need to link to gcc specific libraries, btw, you *do* have

   /usr/lib/libstdc++.so

which is needed to link libasprintf dynamically?

> Nils reported getting to the denemo installer executable, but hit gtk
> installation lacked the svg loader.

Interesting...possibly another librsvg dependency problem...

> It's ok if you think it is not profitable to do this keyhole debugging
> of my gub attempt - OTOH I am happy to keep on pushing through, as
> uncovering facts such as "you need g++ installed for gub" is presumably
> useful (?)

I'm not sure.  On the one hand, you seem to have a pretty weird machine,
so if gub runs there, it should run anywhere :-)

Otoh, we're not even past tools::.  I'm wondering what kind of setup
you have, being a denemo developer without a working gcc/g++ 
installation?  What am I missing?

The gub documentation still requires a working unix development
environment with gcc and g++, I assumed you knew that?

    http://lilypond.org/gub

I'll try to clarify it a bit and add some checks, maybe.

Greetings,
Jan.

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
AvatarĀ®: http://AvatarAcademy.nl    | http://lilypond.org





reply via email to

[Prev in Thread] Current Thread [Next in Thread]