Anybody with a Alpha around to test this?
http://buildd.debian.org/fetch.cgi?&pkg=pike7.6&ver=7.6.112-1&ar...
I saw a discusion about this maybe being libjpeg's fault, if it's so can we workaround it or help fix libjpeg.
This stops pike76 from entering testing, thus being a part of lenny.
//Henrik Andreasson
Now being a DD, I have some access to various machines, including an alpha. Accordingly, I've tried to debug. I'm not terribly good at getting libjpeg's debug symbols loaded though.
I was thinking of asking debian-alpha@lists.d.o as well as the libjpeg maintainer for help as well.
On Sat, 3 May 2008, Magnus Holmgren, Millnet AB (nu med fast anst?llning) @ Pike (-) developers forum wrote:
I'll help with some of that, just tell me what to start with.
Now being a DD, I have some access to various machines, including an alpha. Accordingly, I've tried to debug. I'm not terribly good at getting libjpeg's debug symbols loaded though.
I was thinking of asking debian-alpha@lists.d.o as well as the libjpeg maintainer for help as well.
I'm having libjpeg/Image.JPEG problems on Ubuntu/AMD64 as well. I would say they are related. Still don't know if it's a libjpeg or an Image.JPEG problem though...
The crashes happen in different ways. It looks a bit like some kind of heap corruption in Image.JPEG.
Reproducing it on AMD64 would be nice so it can be Valgrinded. If it is heap corruption maybe we'll get lucky and trigger a write in a red-zone.
Yes, that's my symptoms too. I think I got a "double free" error from glibc last time.
If noone objects I'm going to "cheat" and remove build-indep from the prerequisites of build in debian/rules. This means that autodoc generation will take place at the binary-indep stage, which is not recommended but not completely forbidden either ("The build target should perform all the configuration and compilation of the package." -- Debian Policy 4.9).
could you explain why that is cheating, how that solves a problem, and how it affects users of the package?
greetings, martin. (i am not objecting, just being curious)
I thought I did. The 'build' target should do everything that doesn't require root (which the install and binary targets do, because files should be owned by root).
The problem is rather complicated. It lies in the fact that the autobuilders always invoke the build target of debian/rules, which does all building of arch-specific as well as arch-independent stuff. Optional build-arch and build-indep targets are defined in policy, but the fact that they are optional and that there is no robust way to check for their existance means that can't be used in the general case. Technically nothing has to be done by the build target though, since it's the binary-arch and binary-indep targets that complete the package building.
pike-devel@lists.lysator.liu.se
-
Henrik Andreasson -
Magnus Holmgren, Millnet AB (nu med fast anst�llning) ＠ Pike (-) developers forum -
Martin Bähr -
Mirar ＠ Pike developers forum
-
Peter Bortas ＠ Pike developers forum