** Changed in: pygpiv (Debian)
Status: New => Fix Released
--
FTBFS with gcc 4.4
https://bugs.launchpad.net/bugs/434142
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
http
** Changed in: pygpiv (Debian)
Status: Unknown => New
--
FTBFS with gcc 4.4
https://bugs.launchpad.net/bugs/434142
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://l
** Branch linked: lp:ubuntu/pygpiv
--
FTBFS with gcc 4.4
https://bugs.launchpad.net/bugs/434142
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://lists.ubuntu.com/mailman/li
** Bug watch added: Debian Bug tracker #563228
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563228
** Also affects: pygpiv (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563228
Importance: Unknown
Status: Unknown
--
FTBFS with gcc 4.4
https://bugs.launchpad.net
This bug was fixed in the package pygpiv - 2.0.0-1ubuntu1
---
pygpiv (2.0.0-1ubuntu1) lucid; urgency=low
* pygpiv.i: add #define PNG_SKIP_SETJMP_CHECK to fix a multiple setjmp.h
inclusion problem due to swig including Python.h before we add gpiv.h
(LP: #434142)
-- SevenM
Thanks for the patch. I have uploaded it. Please forward the changes to
Debian if it does not do any harm to the Debian package. They may have
the same problem once they use Python 2.6.
--
FTBFS with gcc 4.4
https://bugs.launchpad.net/bugs/434142
You received this bug notification because you are
this isnt a problem for debian unstable, libpng-dev contains the same
test but builds against python 2.5 so perhaps its a result of using 2.6
in ubuntu.
--
FTBFS with gcc 4.4
https://bugs.launchpad.net/bugs/434142
You received this bug notification because you are a member of Ubuntu
Bugs, which i
There doesn't seem to be a better way solve this in this specific case. the
problem is
1. swig automatically generates a #include call before any of
pygpiv's code, this brings in setjmp.h
2. pygpiv then includes gpiv.h which in turn includes png.h, this brings in
pngconf.h
3. pngvonf.h fails i
** Attachment added: "pygpiv_2.0.0-1ubuntu1.debdiff"
http://launchpadlibrarian.net/36624322/pygpiv_2.0.0-1ubuntu1.debdiff
--
FTBFS with gcc 4.4
https://bugs.launchpad.net/bugs/434142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "proper lucid diff"
http://launchpadlibrarian.net/36624308/pygpiv_2.0.0-1ubuntu1.debdiff
** Attachment removed: "pygpiv_1.0.0-1ubuntu1.debdiff"
http://launchpadlibrarian.net/36619062/pygpiv_1.0.0-1ubuntu1.debdiff
** Attachment removed: "proper lucid diff"
http://lau
from pngconf.h, on PNG_SKIP_SETJMP_CHECK
"You can bypass this test if you know that your application uses exactly
the same setjmp.h that was included when libpng was built."
--
FTBFS with gcc 4.4
https://bugs.launchpad.net/bugs/434142
You received this bug notification because you are a member o
** Attachment added: "pygpiv_1.0.0-1ubuntu1.debdiff"
http://launchpadlibrarian.net/36619062/pygpiv_1.0.0-1ubuntu1.debdiff
** Attachment removed: "pygpiv_1.0.0-1ubuntu1.debdiff"
http://launchpadlibrarian.net/36619040/pygpiv_1.0.0-1ubuntu1.debdiff
--
FTBFS with gcc 4.4
https://bugs.launchpa
** Attachment added: "pygpiv_1.0.0-1ubuntu1.debdiff"
http://launchpadlibrarian.net/36619040/pygpiv_1.0.0-1ubuntu1.debdiff
** Attachment removed: "pygpiv_1.0.0-1ubuntu1.debdiff"
http://launchpadlibrarian.net/36619017/pygpiv_1.0.0-1ubuntu1.debdiff
--
FTBFS with gcc 4.4
https://bugs.launchpa
** Attachment added: "pygpiv_1.0.0-1ubuntu1.debdiff"
http://launchpadlibrarian.net/36619017/pygpiv_1.0.0-1ubuntu1.debdiff
** Attachment removed: "pygpiv_1.0.0-1ubuntu1.debdiff"
http://launchpadlibrarian.net/36619008/pygpiv_1.0.0-1ubuntu1.debdiff
--
FTBFS with gcc 4.4
https://bugs.launchpa
well, if #define PNG_SKIP_SETJMP_CHECK is added then pngconf.h will
ignore the check and assume multiple setjmp.h inclusion isn't a problem,
i think this is ok in this case (probably true in a lot of cases) so if
that seems reasonable we could just do that?
** Attachment added: "pygpiv_1.0.0-1ubun
not sure about the best way to fix this, its swig that inserts the
python include into pygpiv_wrap.c
--
FTBFS with gcc 4.4
https://bugs.launchpad.net/bugs/434142
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
this seems to be a problem with including png.h after setjmp.h in the
code 'swigged' from pygpiv.i. Python.h is included first, and it
includes setjmp.h, whereas including gpiv.h then draws in png.h, causing
the error.
#include //includes setjmp.h
#include //includes png.h
Reversing the ord
** Changed in: pygpiv (Ubuntu)
Status: New => Confirmed
--
FTBFS with gcc 4.4
https://bugs.launchpad.net/bugs/434142
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:/
** Tags added: ftbfs
--
FTBFS with gcc 4.4
https://bugs.launchpad.net/bugs/434142
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://lists.ubuntu.com/mailman/listinfo/ubuntu-
19 matches
Mail list logo
