Comment 4 for bug 1896293
Revision history for this message
| Michael Van Canneyt (7-michael-z) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Any news on this ?
This effectively prevents the Free Pascal compiler from creating & loading pascal dynamic libraries.
The supposition that "libc is always in scope" is incorrect:
The Free Pascal compiler does not link to libc at all by default and produces binaries that make direct kernel calls. The users can of course opt to use libc by explicitly linking to it, but this is by no means a requirement, and it never has been.
Till this change, it was also possible to have a pascal program link in a pascal library (in which case neither has the calloc/malloc/free etc. symbols. With this change, the bug as reported here has effectively blocked us from creating dynamic libraries.
In absence of a solution in the dynamic linker, what are the possible solutions for the Free Pascal compiler to fix the possibility to create dynamic libraries that do not link to libc ?