Re: ct-ng: question regards cross-native toolchain

[Daniel Dittmann <ddittmann at gmx dot net>]

Hi Yann,
hi All,

Yann E. MORIN wrote:
> If you are willing to add and test such support :
> 
> - build standard cross-compiler for your target
> - look at scripts/crosstool-ng.sh.in
> - at around line 333, add a case entry, smthg like:
>     cross-native)
>         CT_HOST="${CT_TARGET}"
>         build_mangle="build_"
>         # Mangling CT_HOST should not be needed
>         # If it is, use: host_mangle="host_"
>         host_mangle=""
>         # It might be in fact that CT_TARGET is to be
>         # mangled instead of, or along with CT_HOST.
>         # If it is, use: target_mangle="target_"
>         target_mangle=""
>         # No need to install tools for 'host',
>         # they are the same as for 'target'
>         install_build_tools_for="BUILD TARGET"
>         ;;
> - at around line 437, duplicate the canadian case
> 
> Try. :-]   Keep us informed. :-)
> Of course, install the cross-native in another place than the standard
> cross-compiler.
Thanks for your hint. I made some short tests and now I have some
questions again.

In my case I use the cross compiler to compile my applications (which
are cross compilable) and the cross-native for third-party applications
which are not cross-compilable.
So I need a cross-native compiler which uses the libs from target (at
the target).

In my first tests I found out that the c-library will be compiled once
in the cross compiler and a second one when compiling the cross-native.
Is that intended?
I think the cross-native should use the libs which are available at the
target.
Should the cross-native compiler also use the same configuration like
the cross compiler (kernel-headers, etc.)?


Regards,
Daniel

--
For unsubscribe information see http://sourceware.org/lists.html#faq