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. --joel On Mon, Jul 22, 2019 at 1:11 AM <gro...@chichak.ca> wrote: > Thank you. Thank you. Thank you. > > Yes, of course, once I added the configuration section and changed main > into an appropriately formatted Init, it compiles nicely. > > Thanks again, > > Andrei > > > On 2019-July-22, at 00:05, Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > > > > On 22/07/2019 07:58, Mr. Andrei Chichak wrote: > >> The linker is bitching about a whole bunch of missing symbols. I expect > that there is a problem finding a library. > >> Any pointers? > > > > You need an application configuration. If you just have a main() > function, then you can use the default configuration (I would always write > a custom application configuration). To use the default configuration, add > -lrtemsdefaultconfig to the linker command line. > > > > -- > > Sebastian Huber, embedded brains GmbH > > > > Address : Dornierstr. 4, D-82178 Puchheim, Germany > > Phone : +49 89 189 47 41-16 > > Fax : +49 89 189 47 41-09 > > E-Mail : sebastian.hu...@embedded-brains.de > > PGP : Public key available on request. > > > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. > > _______________________________________________ > users mailing list > users@rtems.org > http://lists.rtems.org/mailman/listinfo/users
_______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
