lilypond-devel
[Top][All Lists]
Advanced

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

Re: Building GUB3


From: Jan Nieuwenhuizen
Subject: Re: Building GUB3
Date: Wed, 18 Feb 2009 09:00:50 +0000

On di, 2009-02-17 at 10:40 -0800, Patrick McCarty wrote:

Hi Patrick,

> # Compile-time system search path for libraries.
> sys_lib_search_path_spec=" =./i686-pc-linux-gnu/4.3.3/ ./ 
> /usr/lib/gcc/i686-pc-linux-gnu/4.3.3/ /usr/lib/gcc/i686-pc-linux-gnu/4.3.3/ 
> /usr/lib/gcc/i686-pc-linux-gnu/4.3.3/../../../../i686-pc-linux-gnu/lib/i686-pc-linux-gnu/4.3.3/
>  /usr/lib/gcc/i686-pc-linux-gnu/4.3.3/../../../../i686-pc-linux-gnu/lib/ 
> /usr/lib/gcc/i686-pc-linux-gnu/4.3.3/../../../i686-pc-linux-gnu/4.3.3/ 
> /usr/lib/gcc/i686-pc-linux-gnu/4.3.3/../../../ /lib/i686-pc-linux-gnu/4.3.3/ 
> /lib/ /usr/lib/i686-pc-linux-gnu/4.3.3/ /usr/lib/"

Ah, well that's totally bogus.  It should be filled by this command
in libtools' configure

    mingw* | cegcc*)
      # MinGW DLLs use traditional 'lib' prefix
      soname_spec='${libname}`echo ${release} | $SED -e 
's/[.]/-/g'`${versuffix}${shared_ext}'
      sys_lib_search_path_spec=`$CC -print-search-dirs | $GREP "^libraries:" | 
$SED -e "s/^libraries://" -e "s,=/,/,g"`

Where CC should be i686-mingw32-gcc

Aussuming that

    target/mingw/root/usr/cross/bin/i686-mingw32-gcc -print-search-dirs | grep 
^libraries

prints something sane (ie, starting with target/mingw/root/usr/lib and
no i686-pc-linux-gnu elements in it), could you try running libtool's
configure with -x and see how this sys_lib_search_path_spec gets set?

In gub/specs/libtool.py, in class Libtool add a configure_command
function:

    def configure_command (self):
        return (' bin/bash +x '
                + target.AutoBuild.configure_command (self))

Jan.

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org





reply via email to

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