On Monday 2009-05-04 08:06, John Calcote wrote:
> On 5/3/2009 3:32 PM, Gerald I. Evenden wrote:
>> In a shared library there are about 8 routines out over 100 that refer to
>> libgsl and libpthread. A frequent situation may arise where an application
>> program has no need for using the 8 procedu
Gerald,
On 5/3/2009 3:32 PM, Gerald I. Evenden wrote:
In a shared library there are about 8 routines out over 100 that refer to
libgsl and libpthread. A frequent situation may arise where an application
program has no need for using the 8 procedures infected with other library
needs.
At the cu
Jan Engelhardt writes:
> On Sunday 2009-05-03 23:32, Gerald I. Evenden wrote:
>> In a shared library there are about 8 routines out over 100 that
>> refer to libgsl and libpthread. A frequent situation may arise where
>> an application program has no need for using the 8 procedures
>> infected w
On Sunday 2009-05-03 23:32, Gerald I. Evenden wrote:
>In a shared library there are about 8 routines out over 100 that refer to
>libgsl and libpthread. A frequent situation may arise where an application
>program has no need for using the 8 procedures infected with other library
>needs.
>
>At
In a shared library there are about 8 routines out over 100 that refer to
libgsl and libpthread. A frequent situation may arise where an application
program has no need for using the 8 procedures infected with other library
needs.
At the current time, when I try to link such a program I get a
