[frogs] Re: Lilypond and Guile forward compatibility

[Ian Hulin <ian@xxxxxxxxxxxx>]

Hi Patrick,

On 21/04/10 00:57, Patrick McCarty wrote:
> On Tue, Apr 20, 2010 at 3:51 PM, Ian Hulin<ian@xxxxxxxxxxxx>  wrote:
>    
> > On 19/04/10 01:11, Patrick McCarty wrote:
> >      
> > >    In other words, if I compile LilyPond with these commands,
> > >    everything checks out, and compilation fails for me at the same
> > >    place it did before:
> > >
> > >      $ libguiledir="/path/to/guile-1.9.10/libguile/.libs"
> > >      $ export LDFLAGS="-L$libguiledir -Wl,-rpath $libguiledir"
> > >      $ ./autogen.sh --disable-optimising
> > >      $ make all
> > >
> > >
> > > Can you test this to see if you get the same results?
> > >
> > >        
> > Rebuilt Guile, then
> >
> > $ meta/uninstalled-env bash
> > $ libguiledir="$PWD/libguile/.libs"
> > $ export LDFLAGS="-L$libguiledir -Wl, -rpath $libguiledir"
> > $ echo $libguiledir
> > /home/ian/Desktop/Development/Guile-and-Scheme/guile-1.9.10/libguile/.libs
> > $ echo $LDFLAGS
> > -L/home/ian/Desktop/Development/Guile-and-Scheme/guile-1.9.10/libguile/.libs
> > -Wl, -rpath
> > /home/ian/Desktop/Development/Guile-and-Scheme/guile-1.9.10/libguile/.libs
> > $ cd lilypond
> > $ ./autogen.sh --prefix=$HOME/usr --disable-optimising
> > processing .
> > Running autoconf ...
> > Running ./configure --prefix=/home/ian/usr --disable-optimising ...
> > checking build system type... i686-pc-linux-gnu
> > checking host system type... i686-pc-linux-gnu
> > checking Package... LILYPOND
> > checking builddir...
> > /home/ian/Desktop/Development/Guile-and-Scheme/guile-1.9.10/lilypond
> > checking for stepmake... ./stepmake  (${datarootdir}/stepmake not found)
> > checking for gmake... no
> > checking for make... make
> > checking for find... find
> > checking for tar... tar
> > checking for bash... /bin/bash
> > checking for python... python
> > checking python version... 2.6.4
> > checking for python... /usr/bin/python
> > checking for gcc... gcc
> > checking for C compiler default output file name...
> > configure: error: in
> > `/home/ian/Desktop/Development/Guile-and-Scheme/guile-1.9.10/lilypond':
> > configure: error: C compiler cannot create executables
> > See `config.log' for more details.
> > $
> > So now it doesn't get as far as it does on your system.
> >      
> Hmm...
>
> IIRC, I saw this error message too before I discovered the correct
> setting for LDFLAGS.
>
> I'm pretty sure a space is not allowed after the comma in the LDFLAGS, so
>
> correct: $ export LDFLAGS="-L$libguiledir -Wl,-rpath $libguiledir"
> not:     $ export LDFLAGS="-L$libguiledir -Wl, -rpath $libguiledir"
>
> Does it still fail if you omit the space that crept into LDFLAGS?
>
> Thanks,
> Patrick
>
>    
I've now rebuilt Lilypond OK after eliminating the space LDFLAGS, but it 
still fails in the same place in the build.  It links the image but 
Segfaults when trying to run it to build the docs,
It's still dying in ly_init_ly_module when the array pointer reaches  
976 and it's trying to execute Accidental_placement_init_ifaces().
It's not getting as far as the call to
scm_primitive_load_path (scm_from_locale_string ("lily.scm"));
which is presumable what executes lily.scm.

Cheers,

Ian



---
----
Join the Frogs!