On Sat, 26 Jul 2003 14:42:48 +0900, Junichi Uekawa
[EMAIL PROTECTED] wrote:
Lintian, however, can't know that this particular library usually is
preloaded, not linked to. Hence the override.
If its use is going to be something like that, please don't put it in
/usr/lib. That's what the lintian
On Sat, 26 Jul 2003 14:42:48 +0900, Junichi Uekawa
[EMAIL PROTECTED] wrote:
Lintian, however, can't know that this particular library usually is
preloaded, not linked to. Hence the override.
If its use is going to be something like that, please don't put it in
/usr/lib. That's what the lintian
Lintian, however, can't know that this particular library usually is
preloaded, not linked to. Hence the override.
If its use is going to be something like that, please don't put it in
/usr/lib. That's what the lintian warning is about.
regards,
junichi
--
To UNSUBSCRIBE, email
Hi, Junichi Uekawa wrote:
Lintian, however, can't know that this particular library usually is
preloaded, not linked to. Hence the override.
If its use is going to be something like that, please don't put it in
/usr/lib. That's what the lintian warning is about.
Usually. Sometimes you
Lintian, however, can't know that this particular library usually is
preloaded, not linked to. Hence the override.
If its use is going to be something like that, please don't put it in
/usr/lib. That's what the lintian warning is about.
regards,
junichi
Lintian, however, can't know that this particular library usually is
preloaded, not linked to. Hence the override.
If its use is going to be something like that, please don't put it in
/usr/lib. That's what the lintian warning is about.
regards,
junichi
Hi, Junichi Uekawa wrote:
Lintian, however, can't know that this particular library usually is
preloaded, not linked to. Hence the override.
If its use is going to be something like that, please don't put it in
/usr/lib. That's what the lintian warning is about.
Usually. Sometimes you
Hi, Sean 'Shaleh' Perry wrote:
correct, so it does not belong in /usr/lib, it belongs in
/usr/lib/snoopy or some such location.
IMHO it doesn't make much sense to create a subdirectory for a single
file. Besides, when developing sometimes you _do_ want to link to this
shared library. (I've
On Fri, Jul 25, 2003 at 07:07:01PM +0200, Matthias Urlichs wrote:
My personal preference is to add a Lintian override, and leave it at
that.
But the error says that it isn't a shared library at all, which is
equally applicable to LD_PRELOADed libraries. The right approach is to
find out *why*
Hi, Colin Watson wrote:
On Fri, Jul 25, 2003 at 07:07:01PM +0200, Matthias Urlichs wrote:
My personal preference is to add a Lintian override, and leave it at
that.
But the error says that it isn't a shared library at all, which is
equally applicable to LD_PRELOADed libraries. The right
Hi, Sean 'Shaleh' Perry wrote:
correct, so it does not belong in /usr/lib, it belongs in
/usr/lib/snoopy or some such location.
IMHO it doesn't make much sense to create a subdirectory for a single
file. Besides, when developing sometimes you _do_ want to link to this
shared library. (I've
On Fri, Jul 25, 2003 at 07:07:01PM +0200, Matthias Urlichs wrote:
My personal preference is to add a Lintian override, and leave it at
that.
But the error says that it isn't a shared library at all, which is
equally applicable to LD_PRELOADed libraries. The right approach is to
find out *why*
Hi, Colin Watson wrote:
On Fri, Jul 25, 2003 at 07:07:01PM +0200, Matthias Urlichs wrote:
My personal preference is to add a Lintian override, and leave it at
that.
But the error says that it isn't a shared library at all, which is
equally applicable to LD_PRELOADed libraries. The right
Hi,
for one of my packages, later lintian versions emit a Warning saying:
W: snoopy: sharedobject-in-library-directory-not-actually-a-shlib
lib/snoopy.so
Unfortunately, I am not too clueful about binary libraries, sonames
and that stuff and do not even understand the lintian --info output.
The
On Thu, Jul 24, 2003 at 08:26:14PM +0200, Marc Haber wrote:
for one of my packages, later lintian versions emit a Warning saying:
W: snoopy: sharedobject-in-library-directory-not-actually-a-shlib
lib/snoopy.so
That suggests that it's not a shared library *at all*, even discounting
versions
On Thursday 24 July 2003 12:10, Colin Watson wrote:
On Thu, Jul 24, 2003 at 08:26:14PM +0200, Marc Haber wrote:
for one of my packages, later lintian versions emit a Warning saying:
W: snoopy: sharedobject-in-library-directory-not-actually-a-shlib
lib/snoopy.so
That suggests that it's not
On Thu, Jul 24, 2003 at 08:26:14PM +0200, Marc Haber wrote:
for one of my packages, later lintian versions emit a Warning saying:
W: snoopy: sharedobject-in-library-directory-not-actually-a-shlib
lib/snoopy.so
That suggests that it's not a shared library *at all*, even discounting
versions
On Thursday 24 July 2003 12:10, Colin Watson wrote:
On Thu, Jul 24, 2003 at 08:26:14PM +0200, Marc Haber wrote:
for one of my packages, later lintian versions emit a Warning saying:
W: snoopy: sharedobject-in-library-directory-not-actually-a-shlib
lib/snoopy.so
That suggests that it's not
18 matches
Mail list logo
