revious
Tomcat 5.5 Debian security announcement was on 2008-06-09.
So.. everything points to Tomcat 5.5 being unpached in Debian for 3 years now,
despite several more or less severe security vulnerabilities (several are
classified as "important" on the Apache Tomcat site). Can this real
> OK, but it does fail. What does config.log tell you at this point about the
> failure reason? Note that the configure test is still broken; it's linking
> with
> many unnecessary libraries, and it should only link with libdl to check for
> the
> presence of dlopen. A problem with one of the
dl:
checking for dlopen... no
checking for dlopen in -ldl... yes
So something else must be the cause
Regards,
Johan
-Original Message-
From: Roger Leigh [mailto:rle...@codelibre.net]
Sent: den 16 februari 2011 14:51
To: Johan Karlsson
Cc: debian-user@lists.debian.org
Subject: Re: Debi
ternal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char dlopen();
int main() {
dlopen()
; return 0; }
---
Regards,
Johan
-Original Message-----
From: Roger Leigh [mai
C'mon, anyone? :)
Maybe this is the wrong list for these kinds of problems?
Regards,
Johan
-Original Message-
From: Johan Karlsson [mailto:johan.karls...@deltamanagement.se]
Sent: den 10 februari 2011 17:20
To: debian-user@lists.debian.org
Subject: Debian Squeeze 64-bit, d
Hi!
I'm trying to compile pmacct from source under Debian Squeeze 64-bit, but it
can't seem to find dlopen(). The very same thing works without problems on
Debian Squeeze 32-bit.
If I run "nm /usr/lib/libdl.a", I get this output (looks fine to me):
dlopen.o:
U __dlopen
000
6 matches
Mail list logo
