Bug#913909: [Ceph-maintainers] Bug#913909: Bug#913909: ceph: FTBFS on i386 and mipsel (regression)

2018-11-19 Thread Gaudenz Steinlin

Hi

Salvatore Bonaccorso  writes:

Hi Gaudenz, and hi James, 

On Mon, Nov 19, 2018 at 03:48:14PM +0100, Gaudenz Steinlin 
wrote: 
James Page  writes: 
> https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/ceph/tree/debian/patches?h=ubuntu/xenial 
> I think I hit the same issue in Ubuntu a while back for which 
> I picked 3 rocksdb patches - see above URL - 000*.patch. 
 Thanks James. It looks like these patches actually fix the 
build issue.  I already had these patches applied to the build 
in unstable, but I did not make the connection to the infinite 
loop.   Salvatore, do you agree to an upload of 10.2.11-2 with 
these patches to stretch-security? Or how should we proceed? 


Yes we should release a regression update for ceph via 
stretch-security. 


Can you ping us when you have it ready?


I'm currently building a new fixed version (10.2.11-2). Should I 
just upload to stretch-security or do you want to have a look at 
it first?


I attached the debdiff to the previous stretch-security upload.

Gaudenz



ceph_10.2.11-1to2.debdiff
Description: Binary data

>
> Regards,
> Salvatore
>
-- 
PGP: 836E 4F81 EFBB ADA7 0852 79BF A97A 7702 BAF9 1EF5


Bug#913909: [Ceph-maintainers] Bug#913909: Bug#913909: ceph: FTBFS on i386 and mipsel (regression)

2018-11-19 Thread Salvatore Bonaccorso
Hi Gaudenz, and hi James,

On Mon, Nov 19, 2018 at 03:48:14PM +0100, Gaudenz Steinlin wrote:
> James Page  writes:
> > https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/ceph/tree/debian/patches?h=ubuntu/xenial
> > 
> > I think I hit the same issue in Ubuntu a while back for which I picked 3
> > rocksdb patches - see above URL - 000*.patch.
> 
> Thanks James. It looks like these patches actually fix the build issue.  I
> already had these patches applied to the build in unstable, but I did not
> make the connection to the infinite loop.
> 
> Salvatore, do you agree to an upload of 10.2.11-2 with these patches to
> stretch-security? Or how should we proceed?

Yes we should release a regression update for ceph via
stretch-security.

Can you ping us when you have it ready?

Regards,
Salvatore



Bug#913909: [Ceph-maintainers] Bug#913909: Bug#913909: ceph: FTBFS on i386 and mipsel (regression)

2018-11-19 Thread Gaudenz Steinlin
James Page  writes: 
https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/ceph/tree/debian/patches?h=ubuntu/xenial 

I think I hit the same issue in Ubuntu a while back for which I 
picked 3 rocksdb patches - see above URL - 000*.patch.


Thanks James. It looks like these patches actually fix the build 
issue.  I already had these patches applied to the build in 
unstable, but I did not make the connection to the infinite loop.


Salvatore, do you agree to an upload of 10.2.11-2 with these 
patches to stretch-security? Or how should we proceed?


Gaudenz
--
PGP: 836E 4F81 EFBB ADA7 0852 79BF A97A 7702 BAF9 1EF5


signature.asc
Description: PGP signature


Bug#913909: [Ceph-maintainers] Bug#913909: Bug#913909: ceph: FTBFS on i386 and mipsel (regression)

2018-11-19 Thread James Page
Hi Gaudenz

On Mon, 19 Nov 2018 at 07:51 Gaudenz Steinlin  wrote:
[...]

> I did the same and the build hanged as well. Retrying the hanging
> call with all the -O2 arguments removed succeeds. So this seems to
> be a bug in GCC with optimizations. I'm unsure on how to proceeed
> from here. It's quite clear this is not a bug in Ceph. Is there a
> chance that GCC will get fixed in stable? Would it make sense to
> open a bug on g++-6? To workaround this in Ceph I would need to
> find a way to disable optimizations just for this file on i386.
> Because I suspect that generally disabling -O2 would have some
> performance implications.
>
> The failing call is:
> /usr/lib/gcc/i686-linux-gnu/6/cc1plus -quiet -I . -I ./include
> -imultiarch i386-linux-gnu -D_GNU_SOURCE -D ROCKSDB_PLATFORM_POSIX
> -D ROCKSDB_LIB_IO_POSIX -D _LARGEFILE64_SOURCE -D OS_LINUX -D
> ROCKSDB_FALLOCATE_PRESENT -D SNAPPY -D ZLIB -D BZIP2 -D
> ROCKSDB_MALLOC_USABLE_SIZE -D ROCKSDB_PTHREAD_ADAPTIVE_MUTEX -D
> ROCKSDB_BACKTRACE -D ROCKSDB_RANGESYNC_PRESENT -D NDEBUG -isystem
> ./third-party/gtest-1.7.0/fused-src monitoring/statistics.cc
> -quiet -dumpbase statistics.cc -momit-leaf-frame-pointer
> -mtune=generic -march=i686 -auxbase-strip monitoring/statistics.o
> -g -g1 -g -g -g1 -g -g1 -O2 -O2 -O2 -O2 -Wformat=1
> -Werror=format-security -Wextra -Wall -Wsign-compare -Wshadow
> -Wno-unused-parameter -Wformat=1 -Werror=format-security
> -Wformat=1 -Werror=format-security -Woverloaded-virtual
> -Wnon-virtual-dtor -Wno-missing-field-initializers -std=c++11
> -fdebug-prefix-map=/home/gaudenz/ceph=. -fstack-protector-strong
> -fPIC -fdebug-prefix-map=/home/gaudenz/ceph=.
> -fstack-protector-strong -fdebug-prefix-map=/home/gaudenz/ceph=.
> -fstack-protector-strong -fno-builtin-memcmp
> -fno-omit-frame-pointer -o /tmp/ccWWcwWO.s
>
> Running in src/rocksdb.


https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/ceph/tree/debian/patches?h=ubuntu/xenial

I think I hit the same issue in Ubuntu a while back for which I picked 3
rocksdb patches - see above URL - 000*.patch.

HTH (and I really need to work towards re-sync between Ubuntu and Debian).

James