** Changed in: nspluginwrapper (Ubuntu)
Status: Fix Committed => Fix Released
--
fails to build with gcc-4.4 on amd64 in karmic
https://bugs.launchpad.net/bugs/387224
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: nspluginwrapper (Ubuntu)
Status: Fix Released => Fix Committed
--
fails to build with gcc-4.4 on amd64 in karmic
https://bugs.launchpad.net/bugs/387224
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
fixed a while ago:
nspluginwrapper (1.2.2-0ubuntu6) karmic; urgency=low
* debian/patches/use_syslsb.patch; dont build LSB libs on our own;
this should unbreak flash+nspluginwrapper after latest ia32-libs
update
+ use USE_SYSTEM_LSB accordingly in debian/rules
-- Alexander Sack < a
fixed in rev 54 and 55.
** Changed in: nspluginwrapper (Ubuntu)
Status: In Progress => Fix Committed
--
fails to build with gcc-4.4 on amd64 in karmic
https://bugs.launchpad.net/bugs/387224
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Branch linked: lp:nspluginwrapper
--
fails to build with gcc-4.4 on amd64 in karmic
https://bugs.launchpad.net/bugs/387224
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
nees that nspluginwrapper builds its own libgcc from lsb-build directory
which then is incompatible with ours. Most likely they use different
build flags (for stack protection).
Solution would be to build against system libs and don't build the lsb-
build libs.
** Changed in: nspluginwrapper (Ubu
