shared libraries should not be distributed

Bug #987617 reported by sds
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ffcall (Ubuntu)
New
Undecided
Unassigned

Bug Description

As explained in http://cvs.savannah.gnu.org/viewvc/*checkout*/ffcall/README?root=libffcall
There is absolutely no reason to build libffcall shared libraries.
Moreover, they are actually harmful.
In fact, the crash reported in https://bugs.launchpad.net/ubuntu/+source/ffcall/+bug/751112
is caused by the shared libraries: when clisp is build with libffcall shared libraries (i.e., "-lavcall -lcallback")
the test suite segfaults, but when clisp is built with libffcall static libraries (i.e., "/usr/bin/libavcall.a /usr/lib/libavcall.a")
everything works just fine (as explained in
https://bugs.launchpad.net/ubuntu/+source/ffcall/+bug/274951).

Let me repeat:

1. the package libffcall1 which only distributes libavcall.so and libcallback.so should be REMOVED.
There is no reason to distribute the shared libraries.

2. CLISP should be linked with libavcall.a and libcallback.a - statically.
otherwise it crashes in FFI callbacks.

3. libffcall1-dev should be kept, it works just fine; but it should NOT depend on libffcall1.

Revision history for this message
sds (sds-gnu) wrote :

if you insist on using --enable-shared, you can just upgrade to the upstream cvs which now ignores --enable-shared

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.