On Tue, Sep 17, 2019 at 02:08:53PM +0100, Leif Lindholm wrote: > > > Please add the requisite support to the GCC5 profile instead. (Which > > > is not actually for gcc 5, but is effectively GCC5+ - we are still > > > successfully using it with gcc 9.) > > > > I can try to use GCC5 profile but the toolchain still has to be > > stick on https://github.com/riscv/riscv-gnu-toolchain @64879b24. We > > got problem on the version higher than this, system hangs at SEC to > > PEI transition if use GCC version higher than @64879b24. > > > > We will figure it out later. > > I suppose this is fine as long as this is specifically on the > edk2-staging branch. We will need to resolve it before we bring the > port to edk2 master. > > I would still like this support to be tweaked to the point where I can > build with either the Fedora or the Debian packaged cross compiler. > > > So how can I mention this restrictions in tool_def? > > I would suggest the following: > - The above information in the top-level Readme.md on the staging branch. > - A single line in the "GCC5 RISCV64 definitions" comment block. > - Adding the above to the commit message.
Oh, and please add information to that Readme.md on which toolchains have successfully built this toolchain. Debian's gcc8 fails. Best Regards, Leif -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#47375): https://edk2.groups.io/g/devel/message/47375 Mute This Topic: https://groups.io/mt/33137137/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
