Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ./build.sh -k feature request (was Re: GENERIC Kernel Build errors with -fsanitize=undefined option enabled)



On 25.06.2018 20:23, Reinoud Zandijk wrote:
> On Sun, Jun 24, 2018 at 10:01:42PM +0200, Reinoud Zandijk wrote:
>> On Wed, May 30, 2018 at 07:11:19PM +0800, Harry Pantazis wrote:
>>> Continuing..
>>>
>>> This first errors are located in
>>> src/sys/external/bsd/drm2/dist/drm/i915/intel_ddi.c and are specific to
>>> the switch statement concerning that the case flags are not reducing
>>> directly to integer constants.
>>
>> I'd like to request a -k flag to ./build.sh that as with a normal make(1)
>> continues to build as much as possible. This will result in reporting all
>> errors in one go without needing the 1st to be resolved before the 2nd is
>> showing up!
> 
> Attached patch will do, objections against me comitting it? It allows all that
> is buildable to be build and the failing files to be compiled later when
> patched with the -u option.
> 
> With regards,
> Reinoud
> 

I'm usually going the other direction. If I hit a problem and an issue
is not visible from a multi-job build (multiple processes print onto the
same screen concurrently), I go for -j1. If this is still no enough I
change the verbosity level and check commands that caused a problem.

The -k option wouldn't not help me.

On the other hand, can you just specify -V MAKEFLAGS="-k" in your local
build?

Attachment: signature.asc
Description: OpenPGP digital signature



Home | Main Index | Thread Index | Old Index