----- Am 25. Jul 2019 um 21:19 schrieb joel j...@rtems.org: > On Thu, Jul 25, 2019 at 2:13 PM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> ----- Am 25. Jul 2019 um 20:59 schrieb joel j...@rtems.org: >> >> > Having a separate library for rtems default configuration breaks autoconf >> > probes for packages which are built using BSP specific arguments. These >> > have built the same way for well over a decade. >> > >> > I know this can be resolved by passing in an extra library on the >> configure >> > line. But this broke a public behavior in an undesirable and subtle way. >> >> I think we have to make a trade-off between difficult to figure out >> configuration issues which normally need the help of a linker map file (I >> don't think the average user knows what this is) and an extra option for >> already complicated Autoconf invocations. >> > > Is there any documentation on this flag and how it might be needed? > > I am not suggesting changing this -- just stating that it had a visible > side-effect that I don't recall getting the discussion that publicly > visible behavior changes should get.
Maybe a section in the user manual which explains 1. which Autoconf stuff you need to build a multilib based configuration, and 2. which Autoconf stuff you need to build a BSP based configuration. _______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
