Bug#167604: debian-policy: provides the exception of static libraries.
On Sat, Nov 23, 2002 at 12:11:30AM +0900, Akira TAGOH wrote:
> >>>>> On Thu, 21 Nov 2002 11:30:18 +0100,
> >>>>> "BA" == Bill Allombert <allomber@math.u-bordeaux.fr> wrote:
>
> So if -static issue is described in README.Debian or
> similar, and provides a solution for using static libraries,
> then even if people submits a bug like Bug#121278(Yes, it's
> also the same situation), can I close such bug? or should it
> be left as current status of Bug#121278?
> And when I get a bug as "libfoo doesn't work with -static",
> who should own it?
I believe you must just explain the situation to the submitter and close
the bug. You have no obligation to add something to README.Debian.
Please be kind with the bug submitter, but you have no obligation to document
the correct use of gcc/ld in your packages.
There are two distinct problems when building code that use dlopen
on ELF platform.
1) You must not link fully static,
2) you must link with -export-dynamic if you want to dlopen() symbol that are
statically linked.
So I believe (ld expert please correct me) the right way to build something
almost static is to do
gcc -export-dynamic -o $@ t.c -Wl,-static -ldl -L. -lfoo -Wl,-Bdynamic
This work with your testsuite.
Anyway this is irrelevant to debian-policy, we should move it to debian-devel.
Cheers,
Bill.
--
Bill. <ballombe@debian.org>
There is no record of the ballombe@debian.org package, and no bugs have been
filed against it.
Reply to: