>0.33~cvs20110710-2 still ftbfs
>
>[...]
>make: *** [build-stamp] Segmentation fault
The versions shipped with oneiric were unusable on all architectures.
On ARM it just happened to segfault during package build. It may or
may not have been the same issue; please test with the upload I did
to Debian experimental right now.
The fix was to always pass -fno-stack-protector from diet to gcc iff
dietlibc was built without SSP support.
If ARM on *buntu is still broken after this, we can re-investigate,
but I needed to fix this first, as it happened on _all_ platforms.
Hector Oron dixit:
[ tc523086 ]
>Not sure if it can be an armhf buildd issue.
If armhf has an experimental buildd, we’ll see; otherwise I would
appreciate a manual schedule here, too. (Now, to see about hppa…)
I wonder why armel and armhf behave so different, anyway. At one
point I even had the Linaro patch as suspect… let’s see here, too,
how far we get with -5 and fix onwards from there.
FWIW, both mksh 40.2-2 and 40.2-3 (the one with all hardening
options, PIE and bindnow and whatnot, enabled) build fine in
a precise/i386 chroot with this version; all regression tests
of mksh pass.
bye,
//mirabilos
--
<dileks> ch: good, you corrected yourself. ppl tend to tweet such news
immediately, sth. like "grml devs seem to be buyable" <ch> dileks: we
_are_. if you throw enough money in our direction, things will happen
<mika> everyone is buyable, it's just a matter of price <mrud> and now
comes [mira] and uses this as a signature ;0 -- they asked for it…
Matthias Klose dixit:
>0.33~cvs20110710-2 still ftbfs
>
>[...]
>make: *** [build-stamp] Segmentation fault
The versions shipped with oneiric were unusable on all architectures.
On ARM it just happened to segfault during package build. It may or
may not have been the same issue; please test with the upload I did
to Debian experimental right now.
The fix was to always pass -fno-stack- protector from diet to gcc iff
dietlibc was built without SSP support.
If ARM on *buntu is still broken after this, we can re-investigate,
but I needed to fix this first, as it happened on _all_ platforms.
Hector Oron dixit:
[ tc523086 ]
>Not sure if it can be an armhf buildd issue.
If armhf has an experimental buildd, we’ll see; otherwise I would
appreciate a manual schedule here, too. (Now, to see about hppa…)
I wonder why armel and armhf behave so different, anyway. At one
point I even had the Linaro patch as suspect… let’s see here, too,
how far we get with -5 and fix onwards from there.
FWIW, both mksh 40.2-2 and 40.2-3 (the one with all hardening
options, PIE and bindnow and whatnot, enabled) build fine in
a precise/i386 chroot with this version; all regression tests
of mksh pass.
bye,
//mirabilos
--
<dileks> ch: good, you corrected yourself. ppl tend to tweet such news
immediately, sth. like "grml devs seem to be buyable" <ch> dileks: we
_are_. if you throw enough money in our direction, things will happen
<mika> everyone is buyable, it's just a matter of price <mrud> and now
comes [mira] and uses this as a signature ;0 -- they asked for it…