Dear Dirk,
In message 4A5A3439.9000208@googlemail.com you wrote:
And as I mantioned before: I do not oppose the change itself. I agree that it is useful and actually a very good idea to support users who really need this. The only things I oppose are (1) making this the default (or even mandatory) for all tool chains and (2) making it architecture-dependent.
So to do in in positive logic, what do you propose how to enable it? In the other mail you mentioned "The selection could be done by passing some argument or environment variables to "make""?
Right.
Maybe you could give some (Makefile?) (pseudo?) code that Jean-Christophe gets an idea how to do this correctly? Sorry if this was given already in the Makefile discussion and I missed it.
No example was given yet.
If someone puts enough effort into it, a clean implementation would probably provide a "spec string" with a "%G" definition to the CFLAGS and thus to the cross compiler's command-line options to override the GCC-provided definition of 'libgcc' with a new (U-Boot provided) one (see gcc.info, Node: Spec Files, Section 3.15 Specifying subprocesses and the switches to pass to them).
A simpler implementation could use the '-B_prefix_' command-line option to select a different run-time support library.
The feature itself could for example be triggered by using something like
$ make USE_PRIVATE_LIBGCC=yes
or $ USE_PRIVATE_LIBGCC=yes $ export USE_PRIVATE_LIBGCC $ make
or similar.
Best regards,
Wolfgang Denk