On Mon, Aug 02, 2010 at 04:42:33PM +0200, Mike Hommey wrote:
> On Mon, Aug 02, 2010 at 12:12:53PM +0200, Mike Hommey
> wrote:
> > Upstream is partially responsible for the problem. I'd say there are
> > actually
> > 2 different problems. The first one is that despite using weak symbols, the
> >
On Mon, Aug 02, 2010 at 12:12:53PM +0200, Mike Hommey wrote:
> Upstream is partially responsible for the problem. I'd say there are actually
> 2 different problems. The first one is that despite using weak symbols, the
> initialization steps don't check if the symbols are resolved before using
> t
How do you check if a weak symbol was resolved?
2010/8/2 Mike Hommey :
> On Fri, Jul 30, 2010 at 11:53:17AM +0200, Christoph Junghans
> wrote:
>> Package: libxml2
>> Version: 2.6.32.dfsg-5+lenny1
>>
>> I know static compiling is bad, but from time to time you need it.
>>
>> Here is the simplest
On Fri, Jul 30, 2010 at 11:53:17AM +0200, Christoph Junghans
wrote:
> Package: libxml2
> Version: 2.6.32.dfsg-5+lenny1
>
> I know static compiling is bad, but from time to time you need it.
>
> Here is the simplest case I can imagine:
> $ cat main.c
> #include
>
> int main(int argc, char **ar
Package: libxml2
Version: 2.6.32.dfsg-5+lenny1
I know static compiling is bad, but from time to time you need it.
Here is the simplest case I can imagine:
$ cat main.c
#include
int main(int argc, char **argv) {
xmlInitParser();
}
$ gcc -static main.c `xml2-config --libs --cflags` -p
5 matches
Mail list logo
