pc386 BSP has complex dependencies

[Joel Sherrill]

In 4.11, the minimum executable did not include open() and close() because the methods rtems_libio_post_driver() and rtems_libio_exit() were not included in the executable. On the master, these two methods are showing up in minimum and pulling in these methods.

The dependency chain used to be if the console driver was installed, we needed to open and close stdin, stdout, and stderr. Now even without the console configured these are included.

FWIW the minimum size looks pretty good on the master for sis. Fixing this would likely drop it at least another 5%.

[Sebastian Huber]

This looks like a BSP-specific issue. On which BSP do you see this?

[Chris Johns]

SIS by the looks of "FWIW the minimum size looks pretty good on the master for sis. ...".

[Sebastian Huber]

Yes, but I don't see this problem on the sis BSP.

[Sebastian Huber]

It seems to be the pc386 BSP. It pulls in a lot of stuff via printk() (e.g. console_select.c).

[Sebastian Huber]

The pc386 BSP has this problem also in 4.11.

[Joel Sherrill]

I saw this on sis. I was teaching a class and wouldn't use pc386 (or any BSP simulated on qemu) as my first choice since you want a simpler BSP and simpler way to execute it.

But I don't see it in sis minimum.exe now. I am going to close this.

[Joel Sherrill]

The pc386 and motorola_powerpc probe for a lot of features and don't have them as optional. They aren't focused on low size but flexibility. The pc386 can have the console changed by boot arguments and this is the intention. Most BSPs don't have that kind of flexibility.

[Sebastian Huber]

Milestone renamed