As a workaround just in case someone runs into the same problem, commenting this in "build.ninja" allows to build the image:
############################################# # Custom command for lighttpd-prefix/src/lighttpd-stamp/lighttpd-patch #build lighttpd-prefix/src/lighttpd-stamp/lighttpd-patch: CUSTOM_COMMAND lighttpd-prefix/src/lighttpd-stamp/lighttpd-update || libpcre (...) # COMMAND = cd /home/hugo/seL4/sel4webserver/build/lighttpd-prefix/src/lighttpd && /usr/bin/git apply /home/hugo/seL4/sel4webserve (...) # DESC = Performing patch step for 'lighttpd' # restat = 1 ############################################# El mié, 2 jun 2021 a las 18:27, Hugo V.C. (<[email protected]>) escribió: > Of course manipulating "build.ninja" to bypass this step will allow to > build the image but would be interesting understand why this happens to fix > it. I really don't need the http server (not this one) so I can remove it > from build, but some people may require it. > > El mié, 2 jun 2021 a las 13:49, Hugo V.C. (<[email protected]>) > escribió: > >> Hi Kent, >> >> I get this: >> >> _site/CAmkESNext.html >> _site/PortingSeL4.html >> [12/47] Performing update step for 'lighttpd' >> HEAD está ahora en b1048b2 [doc] NEWS >> [13/47] Performing patch step for 'lighttpd' >> FAILED: lighttpd-prefix/src/lighttpd-stamp/lighttpd-patch >> cd /home/hugo/seL4/sel4webserver/build/lighttpd-prefix/src/lighttpd && >> /usr/bin/git apply >> /home/hugo/seL4/sel4webserver/projects/webserver/lighttpd/lighttpd_cmake.patch >> /home/hugo/seL4/sel4webserver/projects/webserver/lighttpd/lemon_cmake.patch >> && /usr/local/bin/cmake -E touch >> /home/hugo/seL4/sel4webserver/build/lighttpd-prefix/src/lighttpd-stamp/lighttpd-patch >> error: el parche falló: src/CMakeLists.txt:221 >> error: src/CMakeLists.txt: el parche no aplica >> ninja: build stopped: subcommand failed. >> >> >> >> El mié, 2 jun 2021 a las 6:44, Kent Mcleod (<[email protected]>) >> escribió: >> >>> On Wed, Jun 2, 2021 at 3:51 AM <[email protected]> wrote: >>> > >>> > Hi, >>> > >>> > I have noticed I'm never unable to run "ninja" for a second time and >>> I'm required to rm -rf all the contents of "build" directory, and run >>> "../init-build.sh" again before running ninja again. If I try to simpley >>> run "ninja" twice the error I get is: >>> > (...) >>> > /var/lib/gems/2.7.0/gems/jekyll-4.0.0/lib/jekyll/tags/include.rb:179: >>> warning: Using the last argument as keyword parameters is deprecated >>> > /var/lib/gems/2.7.0/gems/jekyll-4.0.0/lib/jekyll/tags/include.rb:179: >>> warning: Using the last argument as keyword parameters is deprecated >>> > (many times...) >>> > /var/lib/gems/2.7.0/gems/jekyll-4.0.0/lib/jekyll/tags/include.rb:179: >>> warning: Using the last argument as keyword parameters is deprecated >>> > >>> /home/hugo/seL4/sel4webserver/build/docsite-prefix/src/docsite/_plugins/include_absolute.rb:71: >>> warning: Using the last argument as keyword parameters is deprecated >>> > done in 10.04 seconds. >>> > Auto-regeneration: disabled. Use --watch to enable. >>> > ninja: build stopped: subcommand failed. >>> > >>> > Any hint on what could be happening? Anyone else having same issue? >>> I'm doing something wrong? >>> >>> I don't experience this when building in the docker container sorry. >>> >>> What happens when you force ninja to run sequentially with `ninja -j1`? >>> >> _______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
