On Wed, Apr 17, 2024 at 2:35 PM Heng Qi <hengqi@xxxxxxxxxxxxxxxxx> wrote: > > > > 在 2024/4/17 上午10:53, Jason Xing 写道: > > Hello Jakub, > > > > On Wed, Apr 17, 2024 at 10:30 AM Jakub Kicinski <kuba@xxxxxxxxxx> wrote: > >> On Wed, 17 Apr 2024 10:22:52 +0800 Heng Qi wrote: > >>> Have you encountered compilation problems in v8? > >> Yes, please try building allmodconfig: > >> > >> make allmodconfig > >> make .. > >> > >> there's many drivers using this API, you gotta build the full kernel.. > >> > > About compiling the kernel, I would like to ask one question: what > > parameters of 'make' do you recommend just like the netdev/build_32bit > > [1] does? > > Hi Jason, > > I founded and checked the use of nipa[1] made from Kuba today. I used > run.sh in the ./nipa/docker > directory locally to run full compilation. > If there are additional errors or warnings after applying our own > patches than before, we will be given > information in the results directory. > > [1] https://github.com/linux-netdev/nipa/tree/main Great! Thanks for the information:) I'll try it locally. Thanks, Jason > > Thanks. > > > > > If I run the normal 'make' command without parameters, there is no > > warning even if the file is not compiled. If running with '-Oline -j > > 16 W=1 C=1', it will print lots of warnings which makes it very hard > > to see the useful information related to the commits I just wrote. > > > > I want to build and then print all the warnings which are only related > > to my patches locally, but I cannot find a good way :( > > > > [1]: https://netdev.bots.linux.dev/static/nipa/845020/13631720/build_32bit/stderr > > > > Thanks, > > Jason >
