bug-lilypond
[Top][All Lists]
Advanced

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

Re: build dependencies


From: Erik Sandberg
Subject: Re: build dependencies
Date: Mon, 23 Feb 2004 01:22:23 +0100
User-agent: KMail/1.5.4

On Monday 23 February 2004 00.32, Han-Wen Nienhuys wrote:
> address@hidden writes:
> > Hi,
> >
> > While compiling from sources, I found these minor issues:
> >
> > 1.
> > ./autogen says
> > See INSTALL.txt for more information on how to build LilyPond
> > ...but INSTALL.txt doesn't exist.
> > 2.
> > ./autogen does not report when guile 1.6 header files are missing.
>
> huh? Are you sure?
>
> autogen runs configure, so it will complain as much as configure.

Yes, but configure doesn't complain. It seems that it doesn't search for its 
header files. After removing debian's guile-1.6-dev package, configure runs 
fine (see below), but make gives me the following error:

rm -f ./out/midi.dep; DEPENDENCIES_OUTPUT="./out/midi.dep ./out/midi.lo" gcc 
-c   -DHAVE_CONFIG_H  -DSTRING_UTILS_INLINED -Iinclude -I./out 
-I../flower/include -I../flower/./out -O2 -finline-functions -g   
-I/usr/include/python2.3    -fpic -fPIC -o out/midi.lo midi.c
In file included from midi.c:21:
out/config.h:79:22: warning: libguile.h: No such file or directory
g++ -shared -o out/midi.so out/midi.lo      -lguile -lguile-ltdl -lqthreads 
-lpthread -lcrypt -lm
/usr/bin/ld: cannot find -lguile
collect2: ld returned 1 exit status
make[1]: *** [out/midi.so] Error 1
make[1]: Leaving directory `/home/erik/lily/lilypond/python'
make: *** [all] Error 2

configure output:

~/lily/lilypond$ ./configure
checking build system type... i686-pc-linux-gnu
checking Package... LILYPOND
checking builddir... /home/erik/lily/lilypond
checking for stepmake... ./stepmake  (${prefix}/share/stepmake not found)
checking host system type... i686-pc-linux-gnu
checking for gmake... no
checking for make... make
checking for find... find
checking for tar... tar
checking for bash... /bin/sh
checking for python... python
checking python version... 2.3.3
checking for python... /usr/bin/python
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 IEEE-conformance compiler flags... none
checking for python... /usr/bin/python
checking /usr/bin/python version... 2.3.3
checking for /usr/bin/python... (cached) /usr/bin/python
checking gcc version... 3.3.3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking g++ version... 3.3.3
checking whether explicit instantiation is needed... no
checking for ar... ar
checking for ranlib... ranlib
checking for bison... bison -y
checking for bison... bison
checking bison version... 1.875
checking for flex... flex
checking how to run the C++ preprocessor... g++ -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 FlexLexer.h usability... yes
checking FlexLexer.h presence... yes
checking for FlexLexer.h... yes
checking for yyFlexLexer.yy_current_buffer... no
checking language... English
checking g++ version... 3.3.3
configure: WARNING: autoconf <= 2.57 with g++ >= 3.3 gettext test broken.
configure: WARNING: Trying gcc, cross thumbs.
checking for gettext in -lintl... no
checking for gettext... yes
checking for msgfmt... msgfmt
checking for mf... mf
checking for inimf... inimf
checking for working metafont mode... ljfour
checking for kpsewhich... kpsewhich
checking for tfm 
path... /usr/share/texmf/fonts/tfm/public/cm 
/usr/share/texmf/fonts/tfm/ams/symbols
checking for guile-config... guile-config
checking guile-config version... 1.6.4
checking guile compile flags...
checking guile link flags... -lguile -lguile-ltdl -lqthreads -lpthread -lcrypt 
-lm
checking kpathsea/kpathsea.h usability... yes
checking kpathsea/kpathsea.h presence... yes
checking for kpathsea/kpathsea.h... yes
checking for kpse_find_file in -lkpathsea... yes
checking for kpse_find_file... yes
checking whether to use kpathsea... yes
checking for makeinfo... makeinfo
checking whether makeinfo can split html by @node... yes
checking Python.h usability... yes
checking Python.h presence... yes
checking for Python.h... yes
checking assert.h usability... yes
checking assert.h presence... yes
checking for assert.h... yes
checking for sys/stat.h... (cached) yes
checking sstream usability... yes
checking sstream presence... yes
checking for sstream... yes
checking whether stat file-mode macros are broken... no
checking for working memcmp... yes
checking for vprintf... yes
checking for _doprnt... no
checking for gettext... (cached) yes
checking for isinf... yes
checking for memmem... yes
checking for snprintf... yes
checking for vsnprintf... yes
checking for gettext... (cached) yes
checking for guile... guile
checking for guile... /usr/bin/guile
checking for perl... perl
checking for perl... /usr/bin/perl
checking for mftrace... mftrace
checking mftrace version... 1.0.19
checking for makeinfo... (cached) makeinfo
checking makeinfo version... 4.6
configure: creating ./config.status
config.status: creating config.make
config.status: creating config.h

WARNING: Please consider installing optional programs:  mftrace >= 1.0.27 
(installed: 1.0.19)

See INSTALL.txt for more information on how to build LilyPond

Type:
    make all       to build LilyPond
    make install   to install LilyPond
    make help      to see all possible targets

Do not worry if ./Documentation should not build.





reply via email to

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