I'm facing same problem, can't build chromium anymore (stopped recently)
ninja: build stopped: subcommand failed. ==> ERRO: Uma falha ocorreu em build()
Em sáb., 25 de nov. de 2023 12:57, Jude DaShiell <jdashiel@xxxxxxxxx> escreveu:
https://www.panix.com/~jdashiel/edbrowse-git-log.zip
has the four logs this build fail produced.
--
Jude <jdashiel at panix dot com>
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo.
Please use in that order."
Ed Howdershelt 1940.
On Sat, 25 Nov 2023, Lone_Wolf wrote:
>
> On 25-11-2023 01:21, Jude DaShiell wrote:
> > With --cleanbuild and -f options added after having erased
> > ~/share/yay/edbrowse-git and ~/.share/yay/quickjs I got:
> >
> > ==> Starting package()...
> > mkdir -p -m 755 /home/jude/builds/edbrowse-git/pkg/edbrowse-git/usr/bin
> > install -m755 edbrowse
> > /home/jude/builds/edbrowse-git/pkg/edbrowse-git/usr/bin
> > install: cannot stat 'edbrowse': No such file or directory
> > make: *** [makefile:82: install] Error 1
> > ==> ERROR: A failure occurred in package().
> > Aborting...
>
>
> I doublechecked by building in a cleanchroot and everything works fine.
> Something in your build environment seems amiss.
>
> If you want to investigate that further, you need to append the --log
> parameter to the makepkg command and upload the build logs somewhere.
>
> a command like
>
> curl -F 'f:1=<-' ix.io </path/to/log-file /
>
> works well for that. after it has finished there will be an url shown on the
> command line, that's what we need to see the logs.
>
>
> There's no telling how much time troubleshooting will take, incase you need
> edbrowse soon building using a clean chroot is probably best solution.
>
>
> Are you familiar with devtools & extra-x86_64-build ?
>
>
> LW
>
>
>
> /
> /
>
