;
> One more thing I just realised: that spurious warning renders the original
> warning message inoperative:
>
> configure: WARNING: using cross tools not prefixed with host triplet
>
> The reason is, that warning message is issued only once. If it is always
> genera
warning message inoperative:
configure: WARNING: using cross tools not prefixed with host triplet
The reason is, that warning message is issued only once. If it is always
generated for the manifest tool, it will not come up again for any other tool
where that warning would have really helped. I
> [...]
> Why is searching for on
> platform when isn't available there?
>
> Because it's the autoconf way! It's not a bug.
> [...]
First of all, thanks for your answer.
At the moment, "autoconf's way" means generating a pointless warning or
alternatively forcing the user to come
On 2014-09-17 16:48, R. Diez wrote:
> Hi there:
>
> I am cross-compiling on a Linux PC host for an embedded ARM target, and I am
> getting this warning:
>
> checking for arm-none-eabi-mt... no
> checking for mt... mt
> configure: WARNING: using cross tools not pr
Hi there:
I am cross-compiling on a Linux PC host for an embedded ARM target, and I am
getting this warning:
checking for arm-none-eabi-mt... no
checking for mt... mt
configure: WARNING: using cross tools not prefixed with host triplet
I have built the cross-compiler toolchain mayself
