devel@edk2.groups.io, "Kinney, Michael D"
主題: Re: [edk2-devel] Can RELEASE target disable -Werror CC_FLAG？
I successfully resolved the build issue by adding the flag
-Wno-maybe-uninitialized in the BaseTools/Conf/tools_def.template file. I have
also submitted a patch email to the
星期四)
收件人: devel@edk2.groups.io, wang...@iscas.ac.cn
抄送: "Kinney, Michael D"
主題: Re: [edk2-devel] Can RELEASE target disable -Werror CC_FLAG？
Can you add -Wno-maybe-uninitialized to compiler flags to work around the error?
On Aug 16, 2023, at 11:31 PM, 汪流 wrote:
This is the failed bui
age-
> From: Pedro Falcato
> Sent: Thursday, August 17, 2023 1:18 PM
> To: devel@edk2.groups.io; Kinney, Michael D
> Cc: Andrew (EFI) Fish ; wang...@iscas.ac.cn
> Subject: Re: [edk2-devel] Can RELEASE target disable -Werror CC_FLAG？
>
> On Thu, Aug 17, 2023 at 9:00 PM Michael D Ki
On Thu, Aug 17, 2023 at 9:00 PM Michael D Kinney
wrote:
>
> I am surprised this same GCC error is not being seen for other CPU archs.
>
>
>
> The simple fix is to this specific issue is to initialize CommandLine to NULL
> at the beginning of the function.
The correct fix here is to -Wno-error=ma
Subject: Re: [edk2-devel] Can RELEASE target disable -Werror CC_FLAG？
Can you add -Wno-maybe-uninitialized to compiler flags to work around the error?
On Aug 16, 2023, at 11:31 PM, 汪流
mailto:wang...@iscas.ac.cn>> wrote:
This is the failed build log:
https://build.tarsier-infra.com/p
s we have been able to apply in the past.
Mike
From: Andrew (EFI) Fish
Sent: Wednesday, August 16, 2023 10:41 AM
To: edk2-devel-groups-io ; Kinney, Michael D
Cc: wang...@iscas.ac.cn
Subject: Re: [edk2-devel] Ca
2023-08-17 01:50:37 (星期四)
收件人: "Andrew (EFI) Fish" , edk2-devel-groups-io
抄送: "wang...@iscas.ac.cn" , "Kinney, Michael D"
主題: RE: [edk2-devel] Can RELEASE target disable -Werror CC_FLAG？
Hi Andrew,
There are compiler flags we set to suppress some of these type
: Re: [edk2-devel] Can RELEASE target disable -Werror CC_FLAG？
Mike,
I seem to remember it was a maybe-uninitialized compiler error. The DEBUG build
did not hit it due to the NULL check in the ASSERT. The NULL check only exists
if ASSERT() is enabled. So if ASSERT is disabled this code in the
half Of ??
> Sent: Wednesday, August 16, 2023 12:46 AM
> To: Andrew (EFI) Fish mailto:af...@apple.com>>
> Cc: edk2-devel-groups-io mailto:devel@edk2.groups.io>>
> Subject: Re: [edk2-devel] Can RELEASE target disable -Werror CC_FLAG？
>
> Yes, the RELEASE build compiler
ompiler doesn't work with it.
-原始郵件-
發件人:"Andrew (EFI) Fish" mailto:af...@apple.com>>
發送時間:2023-08-10 21:50:55 (星期四)
收件人: edk2-devel-groups-io mailto:devel@edk2.groups.io>>,
wang...@iscas.ac.cn<mailto:wang...@iscas.ac.cn>
抄送:
主題: Re: [edk2-devel] Can
't work with it.
-原始郵件-
發件人:"Andrew (EFI) Fish"
發送時間:2023-08-10 21:50:55 (星期四)
收件人: edk2-devel-groups-io , wang...@iscas.ac.cn
抄送:
主題: Re: [edk2-devel] Can RELEASE target disable -Werror CC_FLAG？
I think that you are advocating that since we have code that error checks on
D
I think that you are advocating that since we have code that error checks on
DEBUG and not RELEASE builds we should relax the RELEASE build compiler flags?
/home/abuild/rpmbuild/BUILD/edk2-edk2-stable202305/MdeModulePkg/Core/Dxe/Hand/Handle.c:1183:24:
error: ‘Prot’ may be used uninitialized [-We
I want to build a rpm package for edk2-stable202305 on riscv64, however I get
some uninitialized variable error, I have found that the reason is -Werror flag.
My build target was release. I think the flag should used in the debug ,not in
release.
My build command: build -t GCC5 -n $NCPUS -b RELE
13 matches
Mail list logo
