Upstream reimplemented KCONFIG_STRICT, just calling it KCONFIG_WERROR. Therefore, adapt our build system and documentation. Upstream is less strict at this time, but there's a proposed patch that got imported. TEST=`util/abuild/abuild -C` output (config.h and config.build) remains the same. Also, the failure type fixed in https://review.coreboot.org/c/coreboot/+/11272 can be detected, which I tested by manually breaking our Kconfig in a similar way. Change-Id: I322fb08a2f7308b93cff71a5dd4136f1a998773b Signed-off-by: Patrick Georgi <patrick@coreboot.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/79259 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Martin L Roth <gaumless@gmail.com> Reviewed-by: Felix Singer <service+coreboot-gerrit@felixsinger.de>
		
			
				
	
	
		
			19 lines
		
	
	
		
			435 B
		
	
	
	
		
			Diff
		
	
	
	
	
	
			
		
		
	
	
			19 lines
		
	
	
		
			435 B
		
	
	
	
		
			Diff
		
	
	
	
	
	
| Make KCONFIG_WERROR more verbose.
 | |
| 
 | |
| Index: kconfig/confdata.c
 | |
| ===================================================================
 | |
| --- kconfig.orig/confdata.c
 | |
| +++ kconfig/confdata.c
 | |
| @@ -533,8 +533,10 @@ load:
 | |
|  	free(line);
 | |
|  	fclose(in);
 | |
|  
 | |
| -	if (conf_warnings && werror)
 | |
| +	if (conf_warnings && werror) {
 | |
| +		fprintf(stderr, "\nERROR: %d warnings encountered, and warnings are errors.\n\n", conf_warnings);
 | |
|  		exit(1);
 | |
| +	}
 | |
|  
 | |
|  	return 0;
 | |
|  }
 |