Hello Wolfgang, On Wed, 01 Jul 2015 23:50:17 +0200, Wolfgang Denk <[email protected]> wrote:
> Actually I think it is inherently wrong to enable > CONFIG_USE_PRIVATE_LIBGCC by default. > > This option is intended as a workaround for broken toolchains, until > these get fixed. By enabling this by default, we miss do not notice > the problems our tool chain has, and therefore these never get fixed, > i. e. brokenness grows. This cannot be good. > > CONFIG_USE_PRIVATE_LIBGCC should only be an emergency-opt-in, but > never ever a default setting. Well then, should we not revisit commits c3dd823 and 7bfd5ee, which enable CONFIG_USE_PRIVATE_LIBGCC for sh and mips respectively? Either we allow it by default for all architectures, or we forbid it by default for all architectures, but I don't like the idea of a heterogeneous per-arch default setting. > Best regards, > > Wolfgang Denk Amicalement, -- Albert. _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
