Re: bpf: Throw error when external libcalls are generated.

2023-11-28 Thread Cupertino Miranda
Reverted! Apologies for the mistake. Jose E. Marchesi writes: >> Hi Cuper. >> OK. Thanks for the patch. > > This commit is breaking the BPF build, because libgcc emits libcalls to > __builtin_abort. We need to rethink this. > > Please revert: > > commit faf5b148588bd7fbb60ec669aefa704044037c

Re: bpf: Throw error when external libcalls are generated.

2023-11-28 Thread Jose E. Marchesi
> Hi Cuper. > OK. Thanks for the patch. This commit is breaking the BPF build, because libgcc emits libcalls to __builtin_abort. We need to rethink this. Please revert: commit faf5b148588bd7fbb60ec669aefa704044037cdc Author: Cupertino Miranda Date: Thu Nov 23 22:28:01 2023 + Tha

Re: bpf: Throw error when external libcalls are generated.

2023-11-27 Thread Jose E. Marchesi
Hi Cuper. OK. Thanks for the patch. > Hi everyone, > > The attached patch is a temporary solution for the lack of proper linker > and external library linking of the eBPF platform. > Any calls created by the compiler, that would usually be defined within > libgcc, will endup being undefined in b

bpf: Throw error when external libcalls are generated.

2023-11-27 Thread Cupertino Miranda
User-agent: mu4e 1.4.15; emacs 28.1 Author: Cupertino Miranda Hi everyone, The attached patch is a temporary solution for the lack of proper linker and external library linking of the eBPF platform. Any calls created by the compiler, that would usually be defined within libgcc, will endup being

bpf: Throw error when external libcalls are generated.

2023-11-24 Thread Cupertino Miranda
Hi everyone, The attached patch is a temporary solution for the lack of proper linker and external library linking of the eBPF platform. Any calls created by the compiler, that would usually be defined within libgcc, will endup being undefined in bpftool, when GCC the compiled code is passed. Th