On 02/18/2019 08:08 PM, Daniel Kiper wrote:
On Mon, Feb 18, 2019 at 07:57:35PM +0100, Daniel Kiper wrote:
On Thu, Feb 14, 2019 at 02:12:28PM +0100, Alexander Graf wrote:
[...]
+ - mkdir /tmp/cross
+ # results in binaries like
/tmp/cross/gcc-8.1.0-nolibc/ia64-linux/bin/ia64-linux-gcc
+ - for i in $CROSS_TARGETS; do
+ ( cd /tmp/cross; wget -O -
https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/8.1.0/x86_64-gcc-8.1.0-nolibc-$i.tar.xz
| xzcat | tar x );
Should not we add e.g. -t 3 to wget command line?
s/mirrors.edge.kernel.org/mirrors.kernel.org/?
s/xzcat | tar x/tar xJ/
And should not we verify signatures of
x86_64-gcc-8.1.0-nolibc-$i.tar.xz?
And why we need "(...)", brackets here?
https://mirrors.edge.kernel.org/pub/tools/crosstool/ says:
These compilers are only functional for kernel builds, they cannot be
used to build userspace code. For complete toolchains, go to
https://toolchains.bootlin.com/
We build userspace code. So, maybe this is not the best fit for us.
We do not build user space code for the cross target, only for the host.
Pretty much the same as the kernel.
Alex
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
