Control: reassign -1 apt-build 0.12.47 On Fri, Mar 01, 2019 at 09:23:20PM +0100, Mattia Rizzolo wrote: > On Fri, Mar 01, 2019 at 07:21:27PM +0100, jEsuSdA wrote: > > I tried to build Inkscape via apt-build and it was impossible. The debian/rules > > binary subprocess fails. > > I have no idea what `apt --build` is doing, but: While "apt --build" exists in terms of "apt source -b" this isn't used here… as there really exists a "apt-build" package I am happy to pass it on (yeah for uncontrolled namespace), but I feel obligated to mention that this package is orphaned for years. So as a tip for the reporter: Try if you can "handroll" what is done here as in "apt build-dep" & "apt source -b". If that fails as well its not a problem with apt-build and you can hand this report back to inkscape (given that a package should usually build from source). Although it might still be an issue with your system they will know best how to make sense of failing builds of their packages. > > CMake Error at /usr/share/cmake-3.13/Modules/CMakeTestCCompiler.cmake:52 > > (message): > > The C compiler > > > > "/usr/lib/apt-build/cc" > > > > is not able to compile a simple test program. > > > > It fails with the following output: > … > > cc: error trying to exec 'cc1': execvp: No existe el fichero o el > > directorio > > This feels like something is off with either apt or your own system; > reassigning to apt to check what they think, but most likely it's > something at fault in your setup. I don't speak español (guessed by report using es_ES) but that sounds like "No such file or directory exists". Something like PATH issues, missing dependencies or something like that perhaps. Having a quick look at the open bugreports against apt-build suggests that this could also be an instance of #358730 if apt-build really continues even if build-dependencies aren't satisfied (I can envision that to be a source of all sorts of fun). Best regards David Kalnischkies
Attachment:
signature.asc
Description: PGP signature