public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Akber Basha J" <akberbasha.j@zohocorp.com>
To: "devel" <devel@edk2.groups.io>, "isaacworam" <isaac.w.oram@intel.com>
Cc: "Desimone,   Nathaniel L" <nathaniel.l.desimone@intel.com>
Subject: Re: [edk2-devel] EDK2 WilsonCityRVP BIOS Build Error
Date: Sun, 01 May 2022 16:17:40 +0530	[thread overview]
Message-ID: <1807f3bb2ab.d30e538f54270.3470748552837162045@zohocorp.com> (raw)
In-Reply-To: <MW3PR11MB47477DF3F9FE8BC504E91C51D0FC9@MW3PR11MB4747.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 4629 bytes --]

Hello Issac,



Thank you for your time and help.

Yes, the patch is working fine for both JunctionCity and WilsonCityRvp.

I will boot it on WIlsonCityRvp. If got any issues, will let you.



Regards,

Akber







---- On Sat, 30 Apr 2022 02:45:14 +0530 Oram, Isaac W <isaac.w.oram@intel.com> wrote ----




Akber,

 

I just sent a patch with some GCC build fixes.  https://edk2.groups.io/g/devel/message/89450
 

There are more fixes needed.  In the meantime, this workaround procedure worked for me:

 

export WORKSPACE=~/src

export EDK_TOOLS_PATH=~/src/edk2/BaseTools

 

cd ~/src/edk2

 

make -C BaseTools

. edksetup.sh BaseTools

 

cd ../edk2-platforms/Platform/Intel/

python build_bios.py -p WilsonCityRvp -t GCC5 -d

 

The problem as I currently understand it is that the pre_build_ex board specific extension is being run before the edk2 build environment is set up by the build_bios.py script.  The workaround effectively creates the environment needed
 to perform the pre-build steps.

I will confer with Nate on the correct fix for this.  It seems like we might need another extension point after ed2 build environment and before main build, but maybe there is a more elegant solution.

 

Also note that there has been an initial report of a binary compatibility issue between the FSP binary and the gcc built bootloader.  At this time it is not expected to boot properly.  The issue reported was only with enabling a second
 SATA drive.  But if there is a binary compatibility issue in the API, any number of things might be incorrect functionally with GCC built edk2 WhitleyOpenBoardPkg bootloader.

 

Regards,
 Isaac
 

From: mailto:devel@edk2.groups.io <mailto:devel@edk2.groups.io>  On Behalf Of Akber Basha J via groups.io
 Sent: Sunday, April 24, 2022 5:11 AM
 To: Desimone, Nathaniel L <mailto:nathaniel.l.desimone@intel.com>
 Cc: devel <mailto:devel@edk2.groups.io>
 Subject: Re: [edk2-devel] EDK2 WilsonCityRVP BIOS Build Error


 

Hello Nate,


Yes. The error is same, relating to CPUTARGET.


I have followed the steps exactly you shared.


 


Regards,


Akber


 


 


 



 


---- On Fri, 22 Apr 2022 23:05:08 +0530 Desimone, Nathaniel L<mailto:nathaniel.l.desimone@intel.com> wrote ----


 


Hi Akber,

 

Is the error in the build log the same as before? The build script should resolve the issue of CPUTARGET
 being undefined.

 

Thanks,

Nate

 

From: Akber
 Basha J <mailto:akberbasha.j@zohocorp.com> 
 Sent: Tuesday, April 19, 2022 11:36 PM
 To: Desimone, Nathaniel L <mailto:nathaniel.l.desimone@intel.com>
 Cc: mailto:devel@edk2.groups.io
 Subject: Re: [edk2-devel] EDK2 WilsonCityRVP BIOS Build Error


 

Hello Nate,


 


Thank you for your response.


 


Build is still getting failed after trying the steps you have mentioned.


 


Regards,


Akber


 


 


 


---- On Mon, 11 Apr 2022 23:14:14 +0530 Desimone, Nathaniel L <mailto:nathaniel.l.desimone@intel.com> wrote ----


 


Hi Akber,

 

It looks like you are trying to build without using the MinPlatform build
 script. Please try building using the following:

 

cd edk2

source edksetup.sh

cd ../edk2-platforms/Platform/Intel

python ./build_bios.py -p WilsonCityRvp

 

Thanks,

Nate

 

From: mailto:devel@edk2.groups.io <mailto:devel@edk2.groups.io>
 on behalf of Akber Basha J via groups.io <akberbasha.j=mailto:zohocorp.com@groups.io>
 Date: Monday, April 11, 2022 at 4:38 AM
 To: devel <mailto:devel@edk2.groups.io>
 Cc: Sadafale, Mangesh <mailto:mangesh.s@zohocorp.com>
 Subject: [edk2-devel] EDK2 WilsonCityRVP BIOS Build Error

Team,


 


We are getting build errors while trying to build BIOS for Intel WilsonCityRVP
 under WhitleyOpenBoardPkg platform.


 


Toolchains used:


GCC: 5 and 7 (getting same error for both GCC5 and GCC7)


IASL: 20211217


OS: Ubuntu-20.04-LTS


Source: Latest EDK2 "master" source is being used for compilation.


 


All pre-build tests has been run successfully.


 


With the above-mentioned toolchains, we could successfully able to build
 BIOS images for TigerlakeURVP platform. But for WhitleyOpenBoardPkg, errors are thrown.


 


Error screenshot has been attached with this mail for reference.


 





 


Any help would be appreciated.


 


Regards,


Akber



 





 



 





 







[-- Attachment #2.1: Type: text/html, Size: 46796 bytes --]

[-- Attachment #2.2: 1.png --]
[-- Type: image/png, Size: 682933 bytes --]

  reply	other threads:[~2022-05-01 10:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 11:38 EDK2 WilsonCityRVP BIOS Build Error Akber Basha J
2022-04-11 17:44 ` [edk2-devel] " Nate DeSimone
2022-04-20  6:36   ` Akber Basha J
2022-04-22 17:35     ` Nate DeSimone
2022-04-24 12:11       ` Akber Basha J
2022-04-29 21:15         ` Oram, Isaac W
2022-05-01 10:47           ` Akber Basha J [this message]
2022-05-17  8:37             ` Akber Basha J
     [not found]             ` <16EFD79BCF54458D.13068@groups.io>
2022-05-17 10:33               ` Akber Basha J
2022-05-19  6:26             ` Akber Basha J
2022-05-19 17:57               ` Oram, Isaac W
2022-04-20  6:29 ` Akber Basha J

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1807f3bb2ab.d30e538f54270.3470748552837162045@zohocorp.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox