> Oh, now I know why the test case looked funny to me.
> The bug was updated because you didn't like the original,
> accurate impact and test case.
But I don't see that anyone has taken the initiative to correct that
test case, and the bug is still marked verification-failed.
I'm therefore removing this package from trusty-proposed, after 4 months
with no further activity.
** Changed in: giflib (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to giflib in Ubuntu.
https://bugs.launchpad.net/bugs/1337898
Title:
Invalid symlinks for libungif.so and libungif.a
Status in giflib package in Ubuntu:
Fix Released
Status in giflib source package in Trusty:
Won't Fix
Status in giflib package in Debian:
Fix Released
Bug description:
Impact
======
Linking programs that need libungif ("-lungif") will fail.
Test Case
=========
apt-get install build-essential libgif-dev
cat >>test.c EOF
int main(int argc, char **argv) {
return 0;
}
EOF
gcc -lungif test.c
GCC will fail with "/usr/bin/ld: cannot find -lungif" on affected
systems.
Regression Potential
====================
None, just removing some dangling symlinks that couldn't work any way.
Original Bug Report
===================
In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in
libgif-dev 4.1.6-11:
Symbol links for libungif.a, libungif.la, and libungif.so are created
in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6
respectively. However, these files are not in /usr/lib but in
/usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid.
I suggest fixing this by placing the symbol links in the same
directory as the target files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
