4da52517c1
This patch removes the component_entry_point library, which used to proved a hook for the libc to intercept the call of the 'Component::construct' function. The mechansim has several shortcomings (see the discussion in the associated issue) and was complex. So we eventually discarded the approach in favor of the explicit handling of the startup. A regular Genode component provides a 'Component::construct' function, which is determined by the dynamic linker via a symbol lookup. For the time being, the dynamic linker falls back to looking up a 'main' function if no 'Component::construct' function could be found. The libc provides an implementation of 'Component::construct', which sets up the libc's task handling and finally call the function 'Libc::Component::construct' from the context of the appllication task. This function is expected to be provided by the libc-using application. Consequently, Genode components that use the libc have to implement the 'Libc::Component::construct' function. The new 'posix' library provides an implementation of 'Libc::Component::construct' that calls a main function. Hence, POSIX programs that merely use the POSIX API merely have to add 'posix' to the 'LIBS' declaration in their 'target.mk' file. Their execution starts at 'main'. Issue #2199
20 lines
561 B
Plaintext
20 lines
561 B
Plaintext
/*
|
|
* Symbols that shall always be added to the section '.dynsym'
|
|
*/
|
|
{
|
|
/*
|
|
* The ctors and dtors symbols are not used by a dynamic program as such
|
|
* programs have no '_main' function. Hence the linker doesn't add them to
|
|
* the dynsym section by itself. However, we need to lookup the ctors and
|
|
* dtors arrays of the dynamic program in LDSO, which is why we must
|
|
* explicitely add them to the dynsym section.
|
|
*/
|
|
_ctors_start;
|
|
_ctors_end;
|
|
_dtors_start;
|
|
_dtors_end;
|
|
_ZN9Component9constructERN6Genode3EnvE;
|
|
_ZN9Component10stack_sizeEv;
|
|
main;
|
|
};
|