On 03.04.2014 21:26, Ram Pai wrote: >> > BOOTCFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \ >> > -fno-strict-aliasing -Os -msoft-float -pipe \ >> > -fomit-frame-pointer -fno-builtin -fPIC -nostdinc \ >> > -isystem $(shell $(CROSS32CC) -print-file-name=include) \ >> > -mbig-endian > > But that is different though. How so? It's exactly the same thing: compilation of standalone BE using LE compiler. Andrey found a very good argument. And if distro can't compile Linux, it's surely broken. Also powerpc64le is relatively new platform as far as distrros are concerned. I think if big distros show good example, other minor will follow, resulting in more comfortable environment rather than locking ourselves into uncomfortable environments. > Yes it is possible to cross compile for > any target on any arch. But the key is that the environment needs to be > setup to do so. > > We are talking about generating crosscompiled grub boot loader by an > uninitiated/not-so-expert adminstrator. It probably amounts to adding -mbig-endian to TARGET_* and using right --target. Both of which can be automated in configure.ac rather than maintaining yet another port.
> If the distribution makes it > easy for that administrator to be able to cross-compile, than life is > easy. But that is not generally the case though. The administrator has > to scramble around to find the right cross-compilation setup installed > on her system to achieve the end result.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
