Re: arm support for gprbuild

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCgAGBQJTsCdmAAoJEOE4WtzWSuY/vF4QAKojIWZGr2rOQj2eopGSUtBT
UXXbP6MVml50lQ1b5+HnaN/8q+VRMEJFiH2OnPD0oKIOfehClzOaifoLUy0z2pX2
ZQwfTc+ak8W0YXdLauy50nGTSyIHVffZBvjFT5YceEhGGRTJGL1N+cIvyPbe6BSO
B3/CkV5hE+MCC9JOHxQ/JEKjqXN0Sfh92pEOc079joHB7Pi+d6YZGJwqpYAjm7/0
sZhVd77+sKZLx7vdzfkxXCgzLq9gDOt7qiKZlZaC4zkp3vdoxUcRZskkChNm849g
5rsRNqVQQyIrCV2fBst9AKUnbyL4Yty0txKA7Hce19vr3JeAl0WH3eUzRHQ+3aw+
kId3///wE+Bw5T8RlIAx8pgSL7j2rKq6GULwNlxHTiMgTkMFZKZvLvzhYPLNvDQu
Quaotj8udHD1/CeU5gGjT0HpVl5Ca+fpVcYG81vMKkWVwWcU4iK2Ylj9e2C78rm6
TrWhZ/V62AhuNak67FyIAmLAVX+Q6eCAEBG6852W8qT0BeYUbkRbuf8gmgaEMTwp
UzTpCT5gB0HNC8KT03DAE3faubmJSV+wTUlZ2qcTSPQ0fa6zkOLxte5EBOmpozXW
3/1Qe9MrBJesiiJAbLR6iz0zPW5X9ap8PQY9tDPLO4TN94TA095lwxyb9MnTqOHF
6BBuNfr2Dm8mKez1mZEC
=KJg5
-----END PGP SIGNATURE-----
Pavel Zhukov wrote:
> Quoting Björn Persson <bjorn@rombobjörn.se>:
> > · Do you know if there's an important difference between "gnu" and
> > "gnueabi", or if it's just two names for the same thing?
>
> As per answer from arm-guys is only two names for consistency. I
> have no idea that consistency they mean.
>
> > · I get the impression that GPRbuild has a default target compiled
> > in, which it uses if --target isn't passed, and the value it uses
> > for the default comes from the RPM macro "configure". Is that right?
> You're right.
>
> > · Do GPRbuild and GPRconfig use the target string only for
> > comparing to the output of "gcc -dumpmachine", or is it also used
> > for something else? Does GPRbuild for example pass parameters to
> > GCC based on the target string that affect how GCC compiles code?
> as far as I understood it uses -dumpmachine to determinate the
> target and use compiller/linker options accordingly.

OK, but if "gnu" and "gnueabi" are synonymous, then the correct compiler
and linker options should be the same for both. If we could get GPRbuild
configured to look for a "gnueabi" compiler, would it then know to use
the same options that it would use for "gnu"?

If so, then how about patching the makefile to run "gcc -dumpmachine"
and compile that value into GPRbuild instead of what was passed to the
configuration script? This wouldn't be acceptable upstream, but it
should produce the desired result for Fedora. Koji doesn't cross-compile
the packages, so the GCC that is present when GPRbuild is built will
always be the same as the native GCC on installed systems.

It would also be interesting to know what happens if no --build or
--host is passed to configure. It may cause correct defaults to be used,
but I can also imagine that it might break building i386 packages on
x86-64 build servers.

If GPRbuild doesn't know what compiler and linker options to use for
"gnueabi", then perhaps GPRconfig could be patched to accept "gnueabi"
as a synonym for "gnu"?

Björn