On Feb 5, 2023, at 09:28, Dan Eble wrote:
>
> 2. Attack this TODO in flower/include/real.hh.
>
>using std::abs; // TODO: replace abs (x) with std::abs (x) and remove this
https://gitlab.com/lilypond/lilypond/-/merge_requests/1834
—
Dan
> On 5 Feb 2023, at 13:54, Werner LEMBERG wrote:
>
> I see the following error:
>
> rational.cc:68:33: error: call to 'abs' is ambiguous
> num_ = static_cast (::abs (n));
>^
> /usr/include/stdlib.h:129:6: note: candidate function
> int abs(int)
Friends,
I don't have a Yosemite or El Capitan environment in which to validate changes.
There are two things I would try.
1. Does changing the few occurrences of `#include ` to `#include
` fix it? I don't know that it will, but it seems like less work than
2.
2. Attack this TODO in
>> > These are *ancient*, the last version 10.11.6 was released in
>> > 2018. Even if we find one, I think we must not introduce any
>> > workaround for such outdated systems.
>>
>> *Must not*? This is a bit harsh IMHO.
>
> Any workaround we introduce will have to be removed at some point.
I
Jonas Hahnfeld via Discussions on LilyPond development
writes:
> On Sun, 2023-02-05 at 12:54 +, Werner LEMBERG wrote:
>> Looking into MacPorts 'lilypond-devel' log files for Yosimite
>> (
>> https://build.macports.org/builders/ports-10.10_x86_64-builder/builds/
>>
On Sun, 5 Feb 2023 at 13:09, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
>
> Any workaround we introduce will have to be removed at some point.
> When? 5 years after the last system goes EOL sounds like a reasonable
> time, don't you think? So yes, in my opinion "must not".
On Sun, 2023-02-05 at 13:05 +, Werner LEMBERG wrote:
> > These are *ancient*, the last version 10.11.6 was released in 2018.
> > Even if we find one, I think we must not introduce any workaround
> > for such outdated systems.
>
> *Must not*? This is a bit harsh IMHO.
Any workaround we
> These are *ancient*, the last version 10.11.6 was released in 2018.
> Even if we find one, I think we must not introduce any workaround
> for such outdated systems.
*Must not*? This is a bit harsh IMHO. The problem could also be in
the used clang versions, which are probably used on
On Sun, 2023-02-05 at 12:54 +, Werner LEMBERG wrote:
> Looking into MacPorts 'lilypond-devel' log files for Yosimite
> (
> https://build.macports.org/builders/ports-10.10_x86_64-builder/builds/
> 211914/steps/install-port/logs/stdio)
> and El Capitan
> (
>
