Re: lilypond-2.4 compile problem in Slackware 10

[Mats Bengtsson]

LilyPond developers, shouldn't the lines

checking kpathsea/kpathsea.h usability... no
checking kpathsea/kpathsea.h presence... no
checking for kpathsea/kpathsea.h... no

from configure result in a warning, at least?

Anand, check where/if the file kpathsea.h is installed on your
system. Maybe you have to set CPPFLAGS as indicated in INSTALL.txt.
Note that it should point to the directory containing
kpathsea/kpathsea.h and not to the kpathsea/ directory.

   /Mats

Ananda Murthy R S wrote:
> This is the output I got from ./configure
>
> checking build system type... i486-slackware-linux-gnu
> checking Package... LILYPOND
> checking builddir... /root/lilypond-2.4.0
> checking for stepmake... ./stepmake  (${prefix}/share/stepmake not  found)
> checking host system type... i486-slackware-linux-gnu
> checking for gmake... gmake
> checking for find... find
> checking for tar... tar
> checking for bash... /bin/sh
> checking for python... python
> checking python version... 2.3.4
> 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 whether compiler understands -pipe... yes
> checking for IEEE-conformance compiler flags... none
> checking for python... /usr/bin/python
> checking /usr/bin/python version... 2.3.4
> checking for /usr/bin/python... (cached) /usr/bin/python
> checking gcc version... 3.3.4
> 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.4
> 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.35
> 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... yes
> checking language... English
> checking g++ version... 3.3.4
> configure: WARNING: autoconf <= 2.59 with g++ >= 3.3 gettext test  broken.
> configure: WARNING: Trying gcc, cross fingers.
> 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 how to run the C preprocessor... gcc -E
> checking kpathsea/kpathsea.h usability... no
> checking kpathsea/kpathsea.h presence... no
> checking for kpathsea/kpathsea.h... no
> 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.34
> checking for makeinfo... (cached) makeinfo
> checking makeinfo version... 4.7
> configure: creating ./config.status
> config.status: creating config.make
> config.status: creating config.hh
>
> Type:
>    make all       to build LilyPond
>    make install   to install LilyPond
>    make help      to see all possible targets
>
> Anand
>
> On 11/09/2004 09:29:54 PM, Mats Bengtsson wrote:
>
> > You should have got a warning from configure about a missing
> > kpathsea library.
> > I don't know how Slackware is packaged, but to quote INSTALL.txt,
> > "you may need to install tetex-devel, tetex-dev or libkpathsea-dev  too"
> >
> > If the libries and include files for libkpathsea are actually  installed
> > but not where the compiler looks for them, read the section of
> > INSTALL.txt on "Linking to kpathsea".
> >
> >    /Mats
> >
> > Ananda Murthy R S wrote:
> >
> > > Hello,
> > >
> > > I am trying to compile lilypond-2.4 on Slackware 10 system. But I  
> > > got  the following error message:
> > >
> > > kpath.cc: In function `String kpathsea_find_afm(const char*)':
> > > kpath.cc:48: error: `kpse_afm_format' undeclared (first use this   
> > > function)
> > > kpath.cc:48: error: (Each undeclared identifier is reported only  
> > > once  for each
> > >   function it appears in.)
> > > kpath.cc:48: error: `kpse_find_file' undeclared (first use this   
> > > function)
> > > kpath.cc: In function `String kpathsea_find_tfm(const char*)':
> > > kpath.cc:81: error: `kpse_tfm_format' undeclared (first use this   
> > > function)
> > > kpath.cc:81: error: `kpse_find_file' undeclared (first use this   
> > > function)
> > > kpath.cc: At global scope:
> > > kpath.cc:95: error: syntax error before `(' token
> > > kpath.cc:97: error: `kpse_last_format' was not declared in this  scope
> > > kpath.cc:97: error: parse error before `;' token
> > > kpath.cc:97: error: syntax error before `++' token
> > > kpath.cc:102: error: `kpse_format_info' was not declared in this  scope
> > > kpath.cc:102: error: `i' was not declared in this scope
> > > kpath.cc:103: error: `kpse_format_info' was not declared in this  scope
> > > kpath.cc:103: error: `i' was not declared in this scope
> > > kpath.cc:104: error: parse error before `for'
> > > kpath.cc:104: error: parse error before `;' token
> > > kpath.cc:104: error: syntax error before `++' token
> > > kpath.cc:105: error: syntax error before `&&' token
> > > kpath.cc:105: error: syntax error before `++' token
> > > kpath.cc: In function `String kpathsea_gulp_file_to_string(String)':
> > > kpath.cc:124: error: `kpathsea_find_format' undeclared (first use  this
> > >   function)
> > > kpath.cc:125: error: `kpse_find_file' undeclared (first use this   
> > > function)
> > > kpath.cc: In function `scm_unused_struct*
> > >   ly_kpathsea_expand_path(scm_unused_struct*)':
> > > kpath.cc:163: error: `kpathsea_find_format' undeclared (first use  this
> > >   function)
> > > kpath.cc:164: error: `kpse_find_file' undeclared (first use this   
> > > function)
> > > kpath.cc: In function `scm_unused_struct*
> > >   ly_kpathsea_expand_variable(scm_unused_struct*)':
> > > kpath.cc:181: error: `kpse_var_expand' undeclared (first use this   
> > > function)
> > > kpath.cc: In function `void initialize_kpathsea(char*)':
> > > kpath.cc:191: warning: unused parameter `char*av0'
> > > make[1]: *** [out/kpath.o] Error 1
> > > make[1]: Leaving directory `/root/lilypond-2.4.0/lily'
> > > make: *** [all] Error 2
> > >
> > > What is the mistake? Can anybody help?
> > >
> > > Thanks for your help.
> > >
> > > Anand
> > >
> > >
> > > _______________________________________________
> > > lilypond-user mailing list
> > > address@hidden
> > > http://lists.gnu.org/mailman/listinfo/lilypond-user
> >
> >
> > --
> > =============================================
> >     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: address@hidden
> >     WWW: http://www.s3.kth.se/~mabe
> > =============================================
>
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-user

--
=============================================
        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: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================