pkx1...@posteo.net writes:
> Hello,
>
> (replying to my own email)
>
> On 25/02/2020 10:59, pkx1...@posteo.net wrote:
>> Hello,
>>
>> I reported this last week (and to be fair I did get replies) but
>> didn't get the chance to follow up.
>>
>> I have a few hours spare this week and I just tried to run
>> patchy-staging from the lilypond-extra dir based (and I have just
>> recloned by lilypond-got repo) and it fails on the very first 'make'
>> here:
>>
>> --snip--
>>
>> ...
>>
>> Making lily/out/metronome-engraver.o < cc
>> Making lily/out/warn-scheme.o < cc
>> Making lily/out/includable-lexer.o < cc
>> Making lily/out/lexer.o < cc
>> Making lily/out/parser.o < cc
>> ./out/parser.cc: In function 'int yyparse(Lily_parser*,
>> scm_unused_struct**)':
>> ./out/parser.cc:2917:12: warning: conversion to 'yytype_int16 {aka
>> short int}' from 'int' may alter its value [-Wconversion]
>> *yyssp = yystate;
>> ^~~~~~~
>> out/lexer.cc: In member function 'virtual int
>> yyFlexLexer::LexerInput(char*, int)':
>> out/lexer.cc:6468:21: warning: conversion to 'int' from
>> 'std::streamsize {aka long int}' may alter its value [-Wconversion]
>> return yyin.gcount();
>> ~~~~~~~~~~~^~
>> Making lily/out/lilypond
>> /usr/bin/ld: final link failed: No space left on device
>> collect2: error: ld returned 1 exit status
>> /tmp/lilypond-autobuild/stepmake/stepmake/executable-rules.make:12:
>> recipe for target 'out/lilypond' failed
>> make[1]: *** [out/lilypond] Error 1
>> /tmp/lilypond-autobuild/stepmake/stepmake/generic-targets.make:6:
>> recipe for target 'all' failed
>> make: *** [all] Error 2
>>
>> --snip--
>>
>>
>> Yet I can obviously 'make' manually (so to speak) as I have already
>> tested a patch this morning running the make commands manually.
>>
>> Can someone else who runs patchy make sure this isn't something more
>> generic and what could be my problem?
>>
>> Regards
>>
>> James
>>
>>
> I know it says
>
> /usr/bin/ld: final link failed: No space left on device
> collect2: error: ld returned 1 exit status
>
> but I have plenty. I moved the build dir to a place I know I have
> plenty of space (just to be sure) and still get the same problem.
>
> Could this be some permission issue?
>
> I don't know how to get more logging here.
First, the build dir of patchy is somewhere else. Second, my
.lilypond-patchy-config contains
[runner_limits]
RLIMIT_CPU = 1000,2000
[self_limits]
RLIMIT_FSIZE = 256000000
and particularly the last number (whatever it is set to on your system)
looks like it could cause trouble for you.
--
David Kastrup
