libimlib2 version 1.2.0 breaks libimage-imlib2-perl
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
imlib2 (Debian) |
Fix Released
|
Unknown
|
|||
imlib2 (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
Automatically imported from Debian bug report #293815 http://
In Debian Bug tracker #293815, Don Armstrong (dondelelcaro) wrote : | #2 |
On Mon, 07 Feb 2005, Adeodato Simó wrote:
> * Don Armstrong [Sat, 05 Feb 2005 15:31:21 -0800]:
> > Package: libimage-
> > Severity: important
> > Version: 1.03-1
>
> > libimlib2 version 1.2.0 breaks Image::Imlib2::load
>
> Do you think it would be sensible to prevent libimlib2 1.2.0 from
> entering testing until the issue is solved? I'm not claiming that
> libimlib2 is at fault, but I think saving testing users from a
> non-working combination would be a good thing.
>
> What about?:
>
> severity 293815 serious
> tag 293815 sid
> reassign 293815 libimlib2,
Yeah, the only problem is that 1.03-1 should really make it into
testing if possible, since it has the fix for alpha support that
showed up in libimlib2 1.1.2-something
Dunno. Laurence: This is really your call to make... I'll try to
figure out what is happening here, but nothing has jumped out at me
yet.
Don Armstrong
--
She was alot like starbucks.
IE, generic and expensive.
-- hugh macleod http://
In Debian Bug tracker #293815, Dato Simó (dato) wrote : | #3 |
* Don Armstrong [Mon, 07 Feb 2005 10:27:48 -0800]:
> Yeah, the only problem is that 1.03-1 should really make it into
> testing if possible, since it has the fix for alpha support that
> showed up in libimlib2 1.1.2-something
As noted on IRC, libimage-
this should not bet a problem.
--
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
Beauty, brains, availability, personality: pick any two.
In Debian Bug tracker #293815, Don Armstrong (don-debian) wrote : some loaders aren't able to load | #4 |
It looks like (from where I'm sitting right now) that this bug is
being caused by the png, jpg, and tiff loaders (amongst others) not
being able to load with perl running.
See the following:
don@archimedes:
don@archimedes:
don@archimedes:
Image::Imlib2 load error: Unknown at -e line 1.
I haven't quite figured out yet why this is occuring, though.
Don Armstrong
--
Il semble que la perfection soit atteinte non quand il n'y a plus rien
a ajouter, mais quand il n'y a plus rien a retrancher.
(Perfection is apparently not achieved when nothing more can be added,
but when nothing else can be removed.)
-- Antoine de Saint-Exupe'ry, Terres des Hommes
In Debian Bug tracker #293815, Don Armstrong (dondelelcaro) wrote : | #5 |
reassign 293815 libimlib2
severity 293815 serious
thanks
The loaders for libimlib2 need to link with libImlib2.so by default.
This was apparently changed in 1.2.0 (see after the IRC conversation)
<dondelelcaro> vorlon: well, maybe that's not what it is... I'm trying
to understand why the loaders for Imlib2 would work
fine with just Imlib2, but fail when I try to load them
into perl
<dondelelcaro> it's #293815
<dondelelcaro> there doesn't seem to be any obvious issues that I can
see
<dondelelcaro> (but then, I'm not an expert at dynamic libraries by
any stretch of the imagination
<vorlon> dondelelcaro: you're trying to load them directly into perl,
or you're trying to load Imlib2 which is then loading the
loaders?
* trave11er senses a trick question
<dondelelcaro> vorlon: load Imlib2 which is then loading the loaders
<vorlon> if the latter, there's a possible issue if the loaders are
trying to look up symbols in imlib2 but have not been linked
against it, since symbols in a library linked by an
a library that has itself been dlopen()ed are not.
<dondelelcaro> well, even more complicated. load Image::Imlib2 which
then loads Imlib2 which loads the loaders
<vorlon> right, same problem.
<vorlon> Are you getting undefined symbol errors, or no error at all?
<dondelelcaro> vorlon: no error at all...
<vorlon> what does ldd -d -r <loader.so> show?
<dondelelcaro> vorlon: ah, excellent
<dondelelcaro> undefined symbol: __imlib_GetTag (/usr/lib/
<vorlon> yep.
<vorlon> so to be used in situations where imlib2 is being dlopen()ed,
those loaders themselves need to be linked against imlib.
<dondelelcaro> vorlon: ok...
<dondelelcaro> cool... makes sense... and the fact that the perl
<dondelelcaro> rrr... links against libImlib2
<vorlon> right. When I say "imlib2 is being dlopen()ed", I mean
"imlib2 is only linked to by something that's being dlopen()ed"
<vorlon> either way, it doesn't end up in the master symbol list.
<dondelelcaro> oh, ok... so when the next thing gets dlopen()ed it
that was dlopen()ed?
<vorlon> right.
<vorlon> unless you use a particular flag to dlopen() -- one that you should never, ever use. :)
<dondelelcaro> vorlon: right. Ok, good.
* dondelelcaro reassigns the bug to imlib2 with this conversation
This probably needs to be taken care of upstream, because I've already
heard reports of it breaking on Fedora, Mandrake, and Ubuntu.
[Probably breaks elsewhere as well.]
The following is basically the change that broke Imlib2 for perl:
--- Makefile.in 2005-01-05 17:22:26.000000000 -0800
+++ ../../imlib2-
@@ -286,49 +268,54 @@
$(GIF_L) \
$(ZLIB_L) \
$(BZ2_L) \
-pnm.la argb.la bmp.la xpm.la tga.la lbm.la
+pnm.la \
+argb.la \
+bmp.la \
+xpm.la \
+tga.la \
+lbm.la
...
In Debian Bug tracker #293815, Don Armstrong (dondelelcaro) wrote : patch for this bug | #6 |
tag 293815 patch
thanks
Attached is a patch to get src/modules/
libraries as appropriate. (This probably should actually be applied to
Makefile.am, and then rerun... but whatever.)
Don Armstrong
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead
bodies. Do you think I want to have an academic debate on this
subject?"
-- Robert Fisk
Debian Bug Importer (debzilla) wrote : | #7 |
Automatically imported from Debian bug report #293815 http://
Debian Bug Importer (debzilla) wrote : | #8 |
Message-ID: <email address hidden>
Date: Sat, 5 Feb 2005 15:31:21 -0800
From: Don Armstrong <email address hidden>
To: <email address hidden>
Subject: libimlib2 version 1.2.0 breaks libimage-
Package: libimage-
Severity: important
Version: 1.03-1
libimlib2 version 1.2.0 breaks Image::Imlib2::load
See the following:
perl -MImage::Imlib2 -le 'my $image =Image:
Downgrading to 1.1.2 fixes the problem.
However, the following C code works with 1.2.0:
#include <X11/Xlib.h>
#include <Imlib2.h>
#include <stdio.h>
typedef Imlib_Image Image__Imlib2;
int main(void){
Imlib_Image image;
Imlib_Load_Error err;
image = imlib_load_
if(image){
fprintf(stdout, "Worked %d\n",err);
}
else{
fprintf(stdout, "Failed %d\n",err);
}
exit(0);
}
Working on figuring out what is actually the problem right now.
Don Armstrong
--
Filing a bug is probably not going to get it fixed any faster.
-- Anthony Towns
Debian Bug Importer (debzilla) wrote : | #9 |
Message-ID: <email address hidden>
Date: Mon, 7 Feb 2005 19:17:59 +0100
From: Adeodato =?iso-8859-
To: Don Armstrong <email address hidden>, <email address hidden>
Cc: "Laurence J. Lane" <email address hidden>
Subject: Re: libimlib2 version 1.2.0 breaks libimage-
* Don Armstrong [Sat, 05 Feb 2005 15:31:21 -0800]:
> Package: libimage-
> Severity: important
> Version: 1.03-1
> libimlib2 version 1.2.0 breaks Image::Imlib2::load
Do you think it would be sensible to prevent libimlib2 1.2.0 from
entering testing until the issue is solved? I'm not claiming that
libimlib2 is at fault, but I think saving testing users from a
non-working combination would be a good thing.
What about?:
severity 293815 serious
tag 293815 sid
reassign 293815 libimlib2,
Thanks.
--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
The pure and simple truth is rarely pure and never simple.
-- Oscar Wilde
Debian Bug Importer (debzilla) wrote : | #10 |
Message-ID: <email address hidden>
Date: Mon, 7 Feb 2005 10:27:48 -0800
From: Don Armstrong <email address hidden>
To: Adeodato =?iso-8859-
Cc: <email address hidden>, "Laurence J\. Lane" <email address hidden>
Subject: Re: libimlib2 version 1.2.0 breaks libimage-
On Mon, 07 Feb 2005, Adeodato Sim=F3 wrote:
> * Don Armstrong [Sat, 05 Feb 2005 15:31:21 -0800]:
> > Package: libimage-
> > Severity: important
> > Version: 1.03-1
>=20
> > libimlib2 version 1.2.0 breaks Image::Imlib2::load
>=20
> Do you think it would be sensible to prevent libimlib2 1.2.0 from
> entering testing until the issue is solved? I'm not claiming that
> libimlib2 is at fault, but I think saving testing users from a
> non-working combination would be a good thing.
>=20
> What about?:
>=20
> severity 293815 serious
> tag 293815 sid
> reassign 293815 libimlib2,
Yeah, the only problem is that 1.03-1 should really make it into
testing if possible, since it has the fix for alpha support that
showed up in libimlib2 1.1.2-something
Dunno. Laurence: This is really your call to make... I'll try to
figure out what is happening here, but nothing has jumped out at me
yet.
Don Armstrong
--=20
She was alot like starbucks.
IE, generic and expensive.
-- hugh macleod http://
Debian Bug Importer (debzilla) wrote : | #11 |
Message-ID: <email address hidden>
Date: Mon, 7 Feb 2005 19:34:42 +0100
From: Adeodato =?iso-8859-
To: Don Armstrong <email address hidden>
Cc: <email address hidden>, "Laurence J. Lane" <email address hidden>
Subject: Re: libimlib2 version 1.2.0 breaks libimage-
* Don Armstrong [Mon, 07 Feb 2005 10:27:48 -0800]:
> Yeah, the only problem is that 1.03-1 should really make it into
> testing if possible, since it has the fix for alpha support that
> showed up in libimlib2 1.1.2-something
As noted on IRC, libimage-
this should not bet a problem.
--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
Beauty, brains, availability, personality: pick any two.
Debian Bug Importer (debzilla) wrote : | #12 |
Message-ID: <email address hidden>
Date: Mon, 7 Feb 2005 21:35:35 -0800
From: Don Armstrong <email address hidden>
To: <email address hidden>
Subject: some loaders aren't able to load
It looks like (from where I'm sitting right now) that this bug is
being caused by the png, jpg, and tiff loaders (amongst others) not
being able to load with perl running.
See the following:
don@archimedes:
don@archimedes:
don@archimedes:
Image::Imlib2 load error: Unknown at -e line 1.
I haven't quite figured out yet why this is occuring, though.
Don Armstrong
--
Il semble que la perfection soit atteinte non quand il n'y a plus rien
a ajouter, mais quand il n'y a plus rien a retrancher.
(Perfection is apparently not achieved when nothing more can be added,
but when nothing else can be removed.)
-- Antoine de Saint-Exupe'ry, Terres des Hommes
Debian Bug Importer (debzilla) wrote : | #13 |
Message-ID: <email address hidden>
Date: Mon, 7 Feb 2005 22:04:45 -0800
From: Don Armstrong <email address hidden>
To: <email address hidden>
--S1BNGpv0yoYahz37
Content-Type: text/plain; charset=us-ascii
Content-
Content-
reassign 293815 libimlib2
severity 293815 serious
thanks
The loaders for libimlib2 need to link with libImlib2.so by default.
This was apparently changed in 1.2.0 (see after the IRC conversation)
<dondelelcaro> vorlon: well, maybe that's not what it is... I'm trying
to understand why the loaders for Imlib2 would work
fine with just Imlib2, but fail when I try to load them
into perl
<dondelelcaro> it's #293815
<dondelelcaro> there doesn't seem to be any obvious issues that I can
see
<dondelelcaro> (but then, I'm not an expert at dynamic libraries by
any stretch of the imagination
<vorlon> dondelelcaro: you're trying to load them directly into perl,
or you're trying to load Imlib2 which is then loading the
loaders?
* trave11er senses a trick question
<dondelelcaro> vorlon: load Imlib2 which is then loading the loaders
<vorlon> if the latter, there's a possible issue if the loaders are
trying to look up symbols in imlib2 but have not been linked
against it, since symbols in a library linked by an
a library that has itself been dlopen()ed are not.
<dondelelcaro> well, even more complicated. load Image::Imlib2 which
then loads Imlib2 which loads the loaders
<vorlon> right, same problem.
<vorlon> Are you getting undefined symbol errors, or no error at all?
<dondelelcaro> vorlon: no error at all...
<vorlon> what does ldd -d -r <loader.so> show?
<dondelelcaro> vorlon: ah, excellent
<dondelelcaro> undefined symbol: __imlib_GetTag (/usr/lib/
ders/png.so)
<vorlon> yep.
<vorlon> so to be used in situations where imlib2 is being dlopen()ed,
those loaders themselves need to be linked against imlib.
<dondelelcaro> vorlon: ok...
<dondelelcaro> cool... makes sense... and the fact that the perl
<dondelelcaro> rrr... links against libImlib2
<vorlon> right. When I say "imlib2 is being dlopen()ed", I mean
"imlib2 is only linked to by something that's being dlopen()ed"
<vorlon> either way, it doesn't end up in the master symbol list.
<dondelelcaro> oh, ok... so when the next thing gets dlopen()ed it
that was dlopen()ed?
<vorlon> right.
<vorlon> unless you use a particular flag to dlopen() -- one that you shoul=
d never, ever use. :)
<dondelelcaro> vorlon: right. Ok, good.
* dondelelcaro reassigns the bug to imlib2 with this conversation
This probably needs to be taken care of upstream, because I've already
heard reports of it breaking on Fedora, Mandrake, and Ubuntu.
[Probably breaks elsewhere as well.]
The following is basically the change that broke Imlib2 for perl:
--- M...
Debian Bug Importer (debzilla) wrote : | #14 |
Message-ID: <email address hidden>
Date: Mon, 7 Feb 2005 22:41:38 -0800
From: Don Armstrong <email address hidden>
To: <email address hidden>
Subject: patch for this bug
--gDGSpKKIBgtShtf+
Content-Type: text/plain; charset=us-ascii
Content-
tag 293815 patch
thanks
Attached is a patch to get src/modules/
libraries as appropriate. (This probably should actually be applied to
Makefile.am, and then rerun... but whatever.)
Don Armstrong
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead
bodies. Do you think I want to have an academic debate on this
subject?"
-- Robert Fisk
http://
--gDGSpKKIBgtShtf+
Content-Type: text/plain; charset=us-ascii
Content-
diff -ru imlib2-
--- imlib2-
+++ imlib2-
@@ -276,41 +276,41 @@
lbm.la
jpeg_la_SOURCES = loader_jpeg.c
-jpeg_la_LDFLAGS = -module -avoid-version
-jpeg_la_LIBADD = @JPEGLIBS@
+jpeg_la_LDFLAGS = -module -avoid-version -L$(top_
+jpeg_la_LIBADD = @JPEGLIBS@ -lImlib2
png_la_SOURCES = loader_png.c
-png_la_LDFLAGS = -module -avoid-version
-png_la_LIBADD = @PNGLIBS@
+png_la_LDFLAGS = -module -avoid-version -L$(top_
+png_la_LIBADD = @PNGLIBS@ -lImlib2
tiff_la_SOURCES = loader_tiff.c
-tiff_la_LDFLAGS = -module -avoid-version
-tiff_la_LIBADD = @TIFFLIBS@
+tiff_la_LDFLAGS = -module -avoid-version -L$(top_
+tiff_la_LIBADD = @TIFFLIBS@ -lImlib2
gif_la_SOURCES = loader_gif.c
-gif_la_LDFLAGS = -module -avoid-version
-gif_la_LIBADD = @GIFLIBS@
+gif_la_LDFLAGS = -module -avoid-version -L$(top_
+gif_la_LIBADD = @GIFLIBS@ -lImlib2
zlib_la_SOURCES = loader_zlib.c
-zlib_la_LDFLAGS = -module -avoid-version
-zlib_la_LIBADD = @ZLIBLIBS@
+zlib_la_LDFLAGS = -module -avoid-version -L$(top_
+zlib_la_LIBADD = @ZLIBLIBS@ -lImlib2
bz2_la_SOURCES = loader_bz2.c
-bz2_la_LDFLAGS = -module -avoid-version
-bz2_la_LIBADD = @BZ2LIBS@
+bz2_la_LDFLAGS = -module -avoid-version -L$(top_
+bz2_la_LIBADD = @BZ2LIBS@ -lImlib2
pnm_la_SOURCES = loader_pnm.c
-pnm_la_LDFLAGS = -module -avoid-version
-pnm_la_LIBADD =
+pnm_la_LDFLAGS = -module -avoid-version -L$(top_
+pnm_la_LIBADD = -lImlib2
argb_la_SOURCES = loader_argb.c
-argb_la_LDFLAGS = -module -avoid-version
-argb_la_LIBADD =
+argb_la_LDFLAGS = -module -avoid-version -L$(top_
+argb_la_LIBADD = -lImlib2
bmp_la_SOURCES = loader_bmp.c
-bmp_la_LDFLAGS = -module -avoid-version
-bmp_la_LIBADD =
+bmp_la_LDFLAGS = -module -avoid-version -L$(top_
+bmp_la_LIBADD = -lImlib2
xpm_la_SOURCES = loader_xpm.c
-xpm_la_LDFLAGS = -module -avoid-version
-xpm_la_LIBADD =
+xpm_la_LDFLAGS = -module -avoid-version -L$(top_
In Debian Bug tracker #293815, Steve Langasek (vorlon) wrote : | #15 |
I am uploading a 0-day NMU for this bug, based on Don Armstrong's patch.
Please find the final diffset attached.
--
Steve Langasek
postmodern programmer
In Debian Bug tracker #293815, Steve Langasek (vorlon) wrote : | #16 |
Hmm, the last patch was not final after all -- a last review before upload
showed that the filters had thee same problem as the loaders. Attached is an
updated patch that fixes both sets of plugins.
Thanks,
--
Steve Langasek
postmodern programmer
Debian Bug Importer (debzilla) wrote : | #17 |
Message-ID: <email address hidden>
Date: Sat, 12 Feb 2005 15:48:58 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: Re: libimlib2 version 1.2.0 breaks libimage-
--jho1yZJdad60DJr+
Content-Type: multipart/mixed; boundary=
Content-
--OgqxwSJOaUobr8KG
Content-Type: text/plain; charset=us-ascii
Content-
Content-
I am uploading a 0-day NMU for this bug, based on Don Armstrong's patch.
Please find the final diffset attached.
--=20
Steve Langasek
postmodern programmer
--OgqxwSJOaUobr8KG
Content-Type: text/plain; charset=us-ascii
Content-
Content-
diff -u imlib2-
es/loaders/
--- imlib2-
+++ imlib2-
@@ -276,41 +276,41 @@
lbm.la
=20
jpeg_la_SOURCES =3D loader_jpeg.c
-jpeg_la_LDFLAGS =3D -module -avoid-version
-jpeg_la_LIBADD =3D @JPEGLIBS@
+jpeg_la_LDFLAGS =3D -module -avoid-version -L$(top_
+jpeg_la_LIBADD =3D @JPEGLIBS@ -lImlib2
png_la_SOURCES =3D loader_png.c
-png_la_LDFLAGS =3D -module -avoid-version
-png_la_LIBADD =3D @PNGLIBS@
+png_la_LDFLAGS =3D -module -avoid-version -L$(top_
+png_la_LIBADD =3D @PNGLIBS@ -lImlib2
tiff_la_SOURCES =3D loader_tiff.c
-tiff_la_LDFLAGS =3D -module -avoid-version
-tiff_la_LIBADD =3D @TIFFLIBS@
+tiff_la_LDFLAGS =3D -module -avoid-version -L$(top_
+tiff_la_LIBADD =3D @TIFFLIBS@ -lImlib2
gif_la_SOURCES =3D loader_gif.c
-gif_la_LDFLAGS =3D -module -avoid-version
-gif_la_LIBADD =3D @GIFLIBS@
+gif_la_LDFLAGS =3D -module -avoid-version -L$(top_
+gif_la_LIBADD =3D @GIFLIBS@ -lImlib2
zlib_la_SOURCES =3D loader_zlib.c
-zlib_la_LDFLAGS =3D -module -avoid-version
-zlib_la_LIBADD =3D @ZLIBLIBS@=20
+zlib_la_LDFLAGS =3D -module -avoid-version -L$(top_
+zlib_la_LIBADD =3D @ZLIBLIBS@ -lImlib2
bz2_la_SOURCES =3D loader_bz2.c
-bz2_la_LDFLAGS =3D -module -avoid-version
-bz2_la_LIBADD =3D @BZ2LIBS@=20
+bz2_la_LDFLAGS =3D -module -avoid-version -L$(top_
+bz2_la_LIBADD =3D @BZ2LIBS@ -lImlib2
pnm_la_SOURCES =3D loader_pnm.c
-pnm_la_LDFLAGS =3D -module -avoid-version
-pnm_la_LIBADD =3D=20
+pnm_la_LDFLAGS =3D -module -avoid-version -L$(top_
+pnm_la_LIBADD =3D -lImlib2
argb_la_SOURCES =3D loader_argb.c
-argb_la_LDFLAGS =3D -module -avoid-version
-argb_la_LIBADD =3D=20
+argb_la_LDFLAGS =3D -module -avoid-version -L$(top_
+argb_la_LIBADD =3D -lImlib2
bmp_la_SOURCES =3D loader_bmp.c
-bmp_la_LDFLAGS =3D -module -avoid-version
-bmp_la_LIBADD =3D=20
+bmp_la_LDFLAGS =3D -module -avoid-version -L$(top_
+bmp_la_LIBADD =3D -lImlib2
xpm_la_SOURCES =3D loader_xpm.c
-xpm_la_LDFLAGS =3D -module -avoid-version
-xpm_la_LIBADD =3D=20
+xpm_la_LDFLAGS =3D -module -avoid-version -L$(top_
+xpm_la_LIBADD =3D -lImlib2
tga_la_SOURCES =3D loader_tga.c
-tga_la_LDFLAGS =3D -module -avoid-v...
Debian Bug Importer (debzilla) wrote : | #18 |
Message-ID: <email address hidden>
Date: Sat, 12 Feb 2005 16:22:55 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: Re: libimlib2 version 1.2.0 breaks libimage-
--7DO5AaGCk89r4vaK
Content-Type: multipart/mixed; boundary=
Content-
--bAmEntskrkuBymla
Content-Type: text/plain; charset=us-ascii
Content-
Content-
Hmm, the last patch was not final after all -- a last review before upload
showed that the filters had thee same problem as the loaders. Attached is =
an
updated patch that fixes both sets of plugins.
Thanks,
--=20
Steve Langasek
postmodern programmer
--bAmEntskrkuBymla
Content-Type: text/plain; charset=us-ascii
Content-
Content-
diff -u imlib2-
es/loaders/
--- imlib2-
+++ imlib2-
@@ -276,41 +276,41 @@
lbm.la
=20
jpeg_la_SOURCES =3D loader_jpeg.c
-jpeg_la_LDFLAGS =3D -module -avoid-version
-jpeg_la_LIBADD =3D @JPEGLIBS@
+jpeg_la_LDFLAGS =3D -module -avoid-version -L$(top_
+jpeg_la_LIBADD =3D @JPEGLIBS@ -lImlib2
png_la_SOURCES =3D loader_png.c
-png_la_LDFLAGS =3D -module -avoid-version
-png_la_LIBADD =3D @PNGLIBS@
+png_la_LDFLAGS =3D -module -avoid-version -L$(top_
+png_la_LIBADD =3D @PNGLIBS@ -lImlib2
tiff_la_SOURCES =3D loader_tiff.c
-tiff_la_LDFLAGS =3D -module -avoid-version
-tiff_la_LIBADD =3D @TIFFLIBS@
+tiff_la_LDFLAGS =3D -module -avoid-version -L$(top_
+tiff_la_LIBADD =3D @TIFFLIBS@ -lImlib2
gif_la_SOURCES =3D loader_gif.c
-gif_la_LDFLAGS =3D -module -avoid-version
-gif_la_LIBADD =3D @GIFLIBS@
+gif_la_LDFLAGS =3D -module -avoid-version -L$(top_
+gif_la_LIBADD =3D @GIFLIBS@ -lImlib2
zlib_la_SOURCES =3D loader_zlib.c
-zlib_la_LDFLAGS =3D -module -avoid-version
-zlib_la_LIBADD =3D @ZLIBLIBS@=20
+zlib_la_LDFLAGS =3D -module -avoid-version -L$(top_
+zlib_la_LIBADD =3D @ZLIBLIBS@ -lImlib2
bz2_la_SOURCES =3D loader_bz2.c
-bz2_la_LDFLAGS =3D -module -avoid-version
-bz2_la_LIBADD =3D @BZ2LIBS@=20
+bz2_la_LDFLAGS =3D -module -avoid-version -L$(top_
+bz2_la_LIBADD =3D @BZ2LIBS@ -lImlib2
pnm_la_SOURCES =3D loader_pnm.c
-pnm_la_LDFLAGS =3D -module -avoid-version
-pnm_la_LIBADD =3D=20
+pnm_la_LDFLAGS =3D -module -avoid-version -L$(top_
+pnm_la_LIBADD =3D -lImlib2
argb_la_SOURCES =3D loader_argb.c
-argb_la_LDFLAGS =3D -module -avoid-version
-argb_la_LIBADD =3D=20
+argb_la_LDFLAGS =3D -module -avoid-version -L$(top_
+argb_la_LIBADD =3D -lImlib2
bmp_la_SOURCES =3D loader_bmp.c
-bmp_la_LDFLAGS =3D -module -avoid-version
-bmp_la_LIBADD =3D=20
+bmp_la_LDFLAGS =3D -module -avoid-version -L$(top_
+bmp_la_LIBADD =3D -lImlib2
xpm_la_SOURCES =3D loader_xpm.c
-xpm_la_LDFLAGS =3D -module -avoid-version
-xpm_la_LIBADD =3D=20
+xpm_la_LDFLAGS =3D -module -avoid-version -L$(top_
...
In Debian Bug tracker #293815, Steve Langasek (vorlon) wrote : Fixed in NMU of imlib2 1.2.0-1.1 | #19 |
tag 293815 + fixed
quit
This message was generated automatically in response to a
non-maintainer upload. The .changes file follows.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 12 Feb 2005 15:19:12 -0800
Source: imlib2
Binary: libimlib2 libimlib2-dev
Architecture: source i386
Version: 1.2.0-1.1
Distribution: unstable
Urgency: high
Maintainer: Laurence J. Lane <email address hidden>
Changed-By: Steve Langasek <email address hidden>
Description:
libimlib2 - powerful image loading and rendering library
libimlib2-dev - Imlib2 development files
Closes: 293815
Changes:
imlib2 (1.2.0-1.1) unstable; urgency=high
.
* Non-maintainer upload.
* High-urgency upload for sarge-targetted RC bugfix
* Fix regression in the linkage of the loader modules which resulted
in undefined symbols, making libimlib2 unusable when being
dlopen()ed by an application; thanks to Don Armstrong for the patch.
Closes: #293815.
Files:
592ffea93ef393
e11c313081dddd
c3795d0fe71a21
a96bd6026c2e39
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCDwCIKN6
7FOrQxZqmoJJoDr
=dcBs
-----END PGP SIGNATURE-----
Debian Bug Importer (debzilla) wrote : | #20 |
Message-Id: <email address hidden>
Date: Sun, 13 Feb 2005 04:02:08 -0500
From: Steve Langasek <email address hidden>
To: <email address hidden>
Cc: Steve Langasek <email address hidden>, <email address hidden> (Laurence J. Lane)
Subject: Fixed in NMU of imlib2 1.2.0-1.1
tag 293815 + fixed
quit
This message was generated automatically in response to a
non-maintainer upload. The .changes file follows.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 12 Feb 2005 15:19:12 -0800
Source: imlib2
Binary: libimlib2 libimlib2-dev
Architecture: source i386
Version: 1.2.0-1.1
Distribution: unstable
Urgency: high
Maintainer: Laurence J. Lane <email address hidden>
Changed-By: Steve Langasek <email address hidden>
Description:
libimlib2 - powerful image loading and rendering library
libimlib2-dev - Imlib2 development files
Closes: 293815
Changes:
imlib2 (1.2.0-1.1) unstable; urgency=high
.
* Non-maintainer upload.
* High-urgency upload for sarge-targetted RC bugfix
* Fix regression in the linkage of the loader modules which resulted
in undefined symbols, making libimlib2 unusable when being
dlopen()ed by an application; thanks to Don Armstrong for the patch.
Closes: #293815.
Files:
592ffea93ef393
e11c313081dddd
c3795d0fe71a21
a96bd6026c2e39
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCDwCIKN6
7FOrQxZqmoJJoDr
=dcBs
-----END PGP SIGNATURE-----
In Debian Bug tracker #293815, Laurence J. Lane (ljlane) wrote : | #21 |
Closed.
Debian Bug Importer (debzilla) wrote : | #22 |
Message-ID: <email address hidden>
Date: Thu, 17 Feb 2005 20:42:32 -0600
From: "Laurence J. Lane" <email address hidden>
To: <email address hidden>
Subject: libimlib2 version 1.2.0 breaks libimage-
Closed.
In Debian Bug tracker #293815, Laurence J. Lane (ljlane) wrote : cleanup | #23 |
reopen 293815
tag 293815 sarge
thanks, control
Debian Bug Importer (debzilla) wrote : | #24 |
Message-ID: <email address hidden>
Date: Sat, 26 Feb 2005 10:05:34 -0600
From: "Laurence J. Lane" <email address hidden>
To: <email address hidden>
Subject: cleanup
reopen 293815
tag 293815 sarge
thanks, control
Matt Zimmerman (mdz) wrote : | #25 |
Seems to be a regression introduced in the newer version in Debian
In Debian Bug tracker #293815, Laurence J. Lane (ljlane) wrote : | #26 |
NMU fixed some time ago
Changed in imlib2: | |
status: | Unknown → Fix Released |
* Don Armstrong [Sat, 05 Feb 2005 15:31:21 -0800]: imlib2- perl
> Package: libimage-
> Severity: important
> Version: 1.03-1
> libimlib2 version 1.2.0 breaks Image::Imlib2::load
Do you think it would be sensible to prevent libimlib2 1.2.0 from
entering testing until the issue is solved? I'm not claiming that
libimlib2 is at fault, but I think saving testing users from a
non-working combination would be a good thing.
What about?:
severity 293815 serious libimage- imlib2- perl
tag 293815 sid
reassign 293815 libimlib2,
Thanks.
--
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
The pure and simple truth is rarely pure and never simple.
-- Oscar Wilde