[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Build errors for Lilypond 2.19.19 on FreeBSD
From: |
David Kastrup |
Subject: |
Re: Build errors for Lilypond 2.19.19 on FreeBSD |
Date: |
Thu, 30 Apr 2015 15:27:13 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
Ben Woods <address@hidden> writes:
> On 30 April 2015 at 16:06, David Kastrup <address@hidden> wrote:
>> Ben Woods <address@hidden> writes:
>>
>>> Hi everyone,
>>>
>>> I am trying to build lilypond 2.19.19 on FreeBSD, and getting the
>>> following build errors:
>>> In file included from ./include/smobs.hh:326:
>>> ./include/smobs.tcc:151:18: error: no matching function for call to
>>> 'scm_c_define_gsubr'
>>> SCM subr = scm_c_define_gsubr (Super::type_p_name_, 1, 0, 0,
>>> ^~~~~~~~~~~~~~~~~~
>>> ...
>>> ./include/smobs.tcc:157:7: error: no matching function for call to
>>> 'scm_c_export'
>>> scm_c_export (Super::type_p_name_, NULL);
>>> ^~~~~~~~~~~~
>>>
>>> Any ideas on how this can be fixed?
>>
>> Link or compile time? Which compile command? And is that all? I
>> thought the error messages of Clang were supposed to be more useful than
>> those of GCC.
>>
>> --
>> David Kastrup
>
> Hi David,
>
> Thanks for your help.
>
> The errors are occurring during compile time. The full build log can
> be found here:
> http://woodsb02.no-ip.org/poudriere/data/101amd64-default/2015-04-29_19h52m02s/logs/errors/lilypond-devel-2.19.19.log
That's a lot of noise in there. There are in lily/include/smobs.hh
several definitions of the kind
static const int type_p_name = 0;
The question is whether you fare better with
static const char * const type_p_name = 0;
here.
--
David Kastrup