HI Heinrich,
On Thu, 11 Feb 2021 at 10:34, Simon Glass wrote:
>
> On Wed, 10 Feb 2021 at 10:59, Heinrich Schuchardt wrote:
> >
> > UEFI test files like helloworld.efi require an architecture specific
> > PE-COFF header.
> >
> > Currently this does not work for cross compiling. If $CROSS_COMPILE
HI Heinrich,
On Thu, 11 Feb 2021 at 10:34, Simon Glass wrote:
>
> On Wed, 10 Feb 2021 at 10:59, Heinrich Schuchardt wrote:
> >
> > UEFI test files like helloworld.efi require an architecture specific
> > PE-COFF header.
> >
> > Currently this does not work for cross compiling. If $CROSS_COMPILE
On Wed, 10 Feb 2021 at 10:59, Heinrich Schuchardt wrote:
>
> UEFI test files like helloworld.efi require an architecture specific
> PE-COFF header.
>
> Currently this does not work for cross compiling. If $CROSS_COMPILE is set,
> use the first part of the architecture triplet from the variable to
On 2/10/21 1:20 PM, Sean Anderson wrote:
On 2/10/21 12:54 PM, Heinrich Schuchardt wrote:
> UEFI test files like helloworld.efi require an architecture specific
> PE-COFF header.
>
> Currently this does not work for cross compiling. If $CROSS_COMPILE
is set,
> use the first part of the
On 2/10/21 12:54 PM, Heinrich Schuchardt wrote:
> UEFI test files like helloworld.efi require an architecture specific
> PE-COFF header.
>
> Currently this does not work for cross compiling. If $CROSS_COMPILE
is set,
> use the first part of the architecture triplet from the variable to
> choo
UEFI test files like helloworld.efi require an architecture specific
PE-COFF header.
Currently this does not work for cross compiling. If $CROSS_COMPILE is set,
use the first part of the architecture triplet from the variable to
choose the PE-COFF header.
Now we can cross-compile the sandbox, e.g
6 matches
Mail list logo
