The build log talks about
autogen.sh --noconfigure
can you confirm that with " ./autogen.sh && make -j4" it also fails?
Fwiw, I had the same compile error as David yesterday. (It had been
quite a while since I last pulled & compiled, so I was not very much
surprised when make didn't suc
David Kastrup writes:
> Han-Wen Nienhuys writes:
>
>> On Tue, Feb 18, 2020 at 11:08 PM David Kastrup wrote:
>>
>>> Han-Wen Nienhuys writes:
>>>
>>> > This surprises me greatly. I just checked
>>> > out b16c3d14f3d1f10aa919e70107e6103c67a9aa01 which is what I pushed this
>>> > morning, and I c
Han-Wen Nienhuys writes:
> On Tue, Feb 18, 2020 at 11:08 PM David Kastrup wrote:
>
>> Han-Wen Nienhuys writes:
>>
>> > This surprises me greatly. I just checked
>> > out b16c3d14f3d1f10aa919e70107e6103c67a9aa01 which is what I pushed this
>> > morning, and I can execute
>> >
>> > ./autogen.sh
On Tue, Feb 18, 2020 at 11:08 PM David Kastrup wrote:
> Han-Wen Nienhuys writes:
>
> > This surprises me greatly. I just checked
> > out b16c3d14f3d1f10aa919e70107e6103c67a9aa01 which is what I pushed this
> > morning, and I can execute
> >
> > ./autogen.sh ; make -j4
> >
> > just fine. In fac
Han-Wen Nienhuys writes:
> This surprises me greatly. I just checked
> out b16c3d14f3d1f10aa919e70107e6103c67a9aa01 which is what I pushed this
> morning, and I can execute
>
> ./autogen.sh ; make -j4
>
> just fine. In fact, I actually did test this before pushing this morning.
>
> Could it be
I double checked, and it compiles at
b16c3d14f3d1f10aa919e70107e6103c67a9aa01 without error in a clean directory
as well.
Could you provide instructions how I can reproduce this build breakage?
thanks,
On Tue, Feb 18, 2020 at 10:56 PM Han-Wen Nienhuys wrote:
> This surprises me greatly. I just
This surprises me greatly. I just checked
out b16c3d14f3d1f10aa919e70107e6103c67a9aa01 which is what I pushed this
morning, and I can execute
./autogen.sh ; make -j4
just fine. In fact, I actually did test this before pushing this morning.
Could it be that you forgot to run autogen.sh ?
On T
James writes:
> Hello,
>
> On 18.02.2020 11:59, David Kastrup wrote:
>> David Kastrup writes:
>>
>>> Hi, staging does not compile anymore.
>>> Making lily/out/keyword.o < cc
>>> Making lily/out/simple-spacer-scheme.o < cc
>>> Making lily/out/episema-engraver.o < cc
>>> Making lily/out/lyric-ext
Hello,
On 18.02.2020 11:59, David Kastrup wrote:
David Kastrup writes:
Hi, staging does not compile anymore.
Making lily/out/keyword.o < cc
Making lily/out/simple-spacer-scheme.o < cc
Making lily/out/episema-engraver.o < cc
Making lily/out/lyric-extender.o < cc
Making lily/out/includable-lex
On 2020/02/18 10:20:31, michael.kaeppler wrote:
> This patch has already been counted down, however, I would
> like to have at least one LGTM to the last version of this patch
before pushing
> this.
> Knowing that this is only an intermediate state and further
clarification would
> help.
I skimme
David Kastrup writes:
> Hi, staging does not compile anymore.
>
> Making lily/out/keyword.o < cc
> Making lily/out/simple-spacer-scheme.o < cc
> Making lily/out/episema-engraver.o < cc
> Making lily/out/lyric-extender.o < cc
> Making lily/out/includable-lexer.o < cc
> Making lily/out/timing-trans
Hi, staging does not compile anymore.
Making lily/out/keyword.o < cc
Making lily/out/simple-spacer-scheme.o < cc
Making lily/out/episema-engraver.o < cc
Making lily/out/lyric-extender.o < cc
Making lily/out/includable-lexer.o < cc
Making lily/out/timing-translator.o < cc
Making lily/out/pango-fo
10:35:17 (UTC) Begin LilyPond compile, previous commit at
b16c3d14f3d1f10aa919e70107e6103c67a9aa01
10:35:20 Merged staging, now at:b16c3d14f3d1f10aa919e70107e6103c67a9aa01
10:35:21Success:./autogen.sh --noconfigure
10:35:34Success:/tmp/
This patch has already been counted down, however, I would
like to have at least one LGTM to the last version of this patch before
pushing this.
Knowing that this is only an intermediate state and further
clarification would help.
https://codereview.appspot.com/579280043/
> à vo -- cê uma can -- ção legal
>
> I don't know how to change it, so that
> http://lsr.di.unimi.it/LSR/Snippet?id=600
> shows the same as in Han-Wen's patch here.
This seems to be a bug on LSR webpage: What you see is double-encoded
UTF-8 (see
https://stackoverflow.com/questions/1143659
On 2020/02/18 07:39:45, lemzwerg wrote:
> > Werner, may I ask you to have a look?
>
> What exactly shall I check?
If you look at
https://lsr.di.unimi.it/form.php?type=snippet;id=600;rld=m_snippet
you'll see:
portuguese = \lyricmode {
à vo -- cê uma can -- ção legal
}
I don't know how to
16 matches
Mail list logo
