mirror of
https://github.com/genodelabs/genode.git
synced 2024-12-24 07:46:42 +00:00
cd92b32622
This is important to issue sync requests for written-to files. As the closing must be performed by an atexit handler, it happens at a time _after_ libc plugins are destructed. Consequently an FD allocated by such a plugin results in a close error, which in turn, does not destruct the FD. We ultimatedly end up in an infinte loop of re-attempting the close. For this reason, the patch changes 'close' to be robust against this special case. This is generally not a problem because libc plugins are phased out. However, at present, the libc_noux plugin is still important. With the changed 'close' in place, there occurred an error message "Error: close: close not implemented" at the exit of each noux program. This patch removes the error printing from the libc plugin mechansim to avoid this noise. The error messages are not important anyway because the deprecation of the libc plugin interface. Issue #3578 |
||
|---|---|---|
| .. | ||
| doc | ||
| include | ||
| lib | ||
| ports | ||
| recipes | ||
| run | ||
| src | ||
| README | ||
This directory contains ports of popular 3rd-party software to Genode. Usage ----- The tool './tool/ports/prepare_port' in the toplevel directory automates the task of downloading and preparing the library source codes. You can select individual packages that have to be prepared by specifying their base names (without the version number) as command-line argument. For example, the following command prepares both the C library and the Freetype library: ! ./tool/ports/prepare_port libc freetype To compile and link against 3rd-party libraries of the 'libports' repository, you have to include the repository into the build process by appending it to the 'REPOSITORIES' declaration of your '<build-dir>/etc/build.conf' file. Under the hood -------------- For each library, there is a file contained in the 'libports/ports/' subdirectory. The file is named after the library and contains the library-specific rules for downloading the source code and installing header files. How does 'libports' relate to the other repositories? ----------------------------------------------------- Most libraries hosted in the 'libports' repository expect a complete C library, which is provided with the 'libc' package. Please do not forget to prepare the libc package when using any of the other libports packages. The libc, in turn, depends on the 'os' repository for its back end. Because the 'os' repository is the home of the dynamic linker, libraries contained in 'libports' are safe to assume the presence of the dynamic linker and, thus, should be built as shared libraries.