On Wed, Nov 24, 2021 at 4:56 PM Thomas Goirand <zigo@xxxxxxxxxx> wrote: > > Hi Kefu, > > Thanks a lot for your help, that's invaluable! > > I've applied the mips 16-byte atomic support patch and I will rebuild > and re-upload to Experimental, let's see how it goes now! :) hi Zigo, i found following error in https://buildd.debian.org/status/fetch.php?pkg=ceph&arch=mipsel&ver=16.2.6%2Bds-5&stamp=1639003196&raw=0 ===== 8< ======= Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_9f34f/fast && gmake[2]: Entering directory '/<<PKGBUILDDIR>>/obj-mipsel-linux-gnu/CMakeFiles/CMakeTmp' /usr/bin/gmake -f CMakeFiles/cmTC_9f34f.dir/build.make CMakeFiles/cmTC_9f34f.dir/build gmake[3]: Entering directory '/<<PKGBUILDDIR>>/obj-mipsel-linux-gnu/CMakeFiles/CMakeTmp' Building CXX object CMakeFiles/cmTC_9f34f.dir/src.cxx.o /usr/bin/c++ -DHAVE_CXX11_ATOMIC -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -g1 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fPIE -o CMakeFiles/cmTC_9f34f.dir/src.cxx.o -c /<<PKGBUILDDIR>>/obj-mipsel-linux-gnu/CMakeFiles/CMakeTmp/src.cxx /<<PKGBUILDDIR>>/obj-mipsel-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:15:44: error: template argument 1 is invalid 15 | bool atomic16(std::atomic<unsigned __int128> *ptr) | ^ /<<PKGBUILDDIR>>/obj-mipsel-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:15:44: error: template argument 1 is invalid /<<PKGBUILDDIR>>/obj-mipsel-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:15:44: error: template argument 1 is invalid /<<PKGBUILDDIR>>/obj-mipsel-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:15:44: error: template argument 1 is invalid /<<PKGBUILDDIR>>/obj-mipsel-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:15:47: error: ‘ptr’ was not declared in this scope 15 | bool atomic16(std::atomic<unsigned __int128> *ptr) | ^~~ ===== >8 ======= so it seems that https://github.com/ceph/ceph/pull/44071 does not work. could you please help test https://github.com/ceph/ceph/pull/44264 ? > > On 11/23/21 5:58 PM, kefu chai wrote: > >> As for the mipsel arch, the error is: > >> virtual memory exhausted: Cannot allocate memory > >> > >> so I'd need to save some memory at build time, somehow. Tips would be > >> appreciated. > > > > hmm, the memory consumption is always an issue. but the "Status" cell > > in the "mipsel" row is not a hyperlink in > > https://buildd.debian.org/status/package.php?p=ceph&suite=experimental, > > so i cannot check or at least try to figure out who was using the > > memory at that very moment.. > > That's because I clicked on the "giveback" link to attempt another > build. Though if you click on the "last log" link on the right you > should be able to see it. > > >> For armel, the issue is: > >> /tmp/cc3CvITT.s:2594: Error: selected processor does not support `yield' > >> in ARM mode > >> > >> Does anyone know how to fix that? > > > > it's should be a bug tracked by > > https://github.com/facebook/folly/issues/1159 . could you try to > > upgrade rocksdb submodule which includes the fix to address this > > issue? probably you will have to backport > > https://github.com/ceph/ceph/pull/42815 to build with a newer rocksdb. > > > >> Thanks in advance for anyone who will help, > > > > no problem. and thank you! > > I don't use git, but the Ceph released tarballs. So I backported the > patch you linked to. > > Thanks a lot for your help, let's hope we can also fix the out-of-memory > problem. > > Otherwise, do you know if it's possible to only build librbd for those > arch that I'm having problem with? That's indeed the only thing that > would make sense going forward, so that qemu still has librbd to link > with, but we wouldn't support those arch for Ceph. Your thoughts? > > Cheers, > > Thomas Goirand (zigo) > _______________________________________________ > Dev mailing list -- dev@xxxxxxx > To unsubscribe send an email to dev-leave@xxxxxxx -- Regards Kefu Chai _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
