Bug#546823: __thread usage in libcap-ng0 broken on armel if optimizing

2009-10-27 Thread Pierre Chifflier
Hi Simon, On Sun, Oct 25, 2009 at 03:53:39PM +, Simon McVittie wrote: > The uploaded packages do solve this bug at least for now (verified on my armel > box by restarting smartd), since Debian doesn't yet cross-build anything and > so > host = build in practice; however, my change was wrong

Bug#546823: __thread usage in libcap-ng0 broken on armel if optimizing

2009-10-25 Thread Simon McVittie
On Sun, 25 Oct 2009 at 03:50:57 +0100, Guillem Jover wrote: > On Thu, 2009-10-22 at 23:46:22 +0100, Simon McVittie wrote: > > +# armel compiler doesn't seem to do too well at __thread if optimizing > > +ifeq ($(DEB_BUILD_GNU_TYPE),arm-linux-gnueabi) > > +CFLAGS += -O0 > > +endif > > This is not co

Bug#546823: __thread usage in libcap-ng0 broken on armel if optimizing

2009-10-24 Thread Guillem Jover
Hi! On Thu, 2009-10-22 at 23:46:22 +0100, Simon McVittie wrote: > diff -u libcap-ng-0.6.2/debian/rules libcap-ng-0.6.2/debian/rules > --- libcap-ng-0.6.2/debian/rules > +++ libcap-ng-0.6.2/debian/rules > @@ -23,7 +23,10 @@ > PYDEF=$(shell pyversions -d) > PYVERS=$(shell pyversions -r) > > - >

Bug#546823: __thread usage in libcap-ng0 broken on armel if optimizing

2009-10-22 Thread Simon McVittie
It appears that the segfaults in libcap-ng0 described in my earlier bug report, caused by (or at least related to) use of R_ARM_GOTOFF32 relocations with TLS symbols, can be avoided by compiling libcap-ng without optimization. I attach an interdiff; for your convenience, it also includes fixes for

Bug#546823: __thread usage in libcap-ng0 broken on armel

2009-09-29 Thread Martin Guy
On 9/28/09, Pierre Chifflier wrote: > On Sat, Sep 26, 2009 at 04:28:36PM +0100, Simon McVittie wrote: > > ARM porters: can you shed any light on this? > As I have no armel platform here (and no knowledge specific to the > architecture), some help would be appreciated. There is a big fast arme

Bug#546823: __thread usage in libcap-ng0 broken on armel

2009-09-28 Thread Pierre Chifflier
On Sat, Sep 26, 2009 at 04:28:36PM +0100, Simon McVittie wrote: > ARM porters: can you shed any light on this? Hi, As I have no armel platform here (and no knowledge specific to the architecture), some help would be appreciated. Regards, Pierre > > If I compile libcap-ng0 on armel, then run "m

Bug#546823: __thread usage in libcap-ng0 broken on armel

2009-09-26 Thread Simon McVittie
ARM porters: can you shed any light on this? If I compile libcap-ng0 on armel, then run "make check", the segfault described in the bug appears: > make[3]: Entering directory `/home/smcv/bugsquash/libcap-ng-0.6.1/src/test' > Doing basic bit tests... > /bin/bash: line 5: 25105 Segmentation fault