From: Erich T. <eri...@th...> - 2021-11-22 18:39:26
|
Hi KP Am 22.11.2021 um 17:03 schrieb KP.Kirchdoerfer: > Hi Erich > > Am Sonntag, 21. November 2021, 20:05:18 CET schrieb Erich Titl: >> Hi Folks >> >> OK I may be a bit old fashioned as I believe a build system is supposed >> to run without hickups and definitely without crashing. > > Agreed. > >> Ours is not. >> >> the following packages fail to build for i486 >> >> protobuf-c,kismet,rtty,pmacctd,ca-certificates > > for protobuf-c (and therefor kismet you need a protobuf-c compiler on the > host. So basically to compile with itself. > > like > protobuf-c-compiler 1.3.3-1build2 amd64 > Protocol Buffers C compiler (protobuf-c) > > on an ubuntu system. So much for portable code. > > For rtty you may need libevdev2 on the host. > dito. > The remaining packages listed above should compile AFAIK without prerequisites > - at least it does for me. Will have a look > > What says the logs? For protobuf-c there is something missing when the build tries to execute protoc. protoc is built but is missing something. > >> Also in the current master mimalloc fails, I fixed that in my >> environment but I feel like this should be done in a generic way, e.g. >> the standard should not crash. > > A more generic solution shall be "kernel based" - it fails with the i486/wrap > kernel, but shall build with i686 (and geode?). > It build with arm and x86_64 toolchains. Yes, basically this should be built in either the configure code which then can decide to abort cleanly or like in my case I checked for the buildtool environment and skipped the build. Of course buildpacket will barf but that is the least of my concerns. cheers ET |