On 2019/03/21 17:33, Jeremie Courreges-Anglas wrote: > On Wed, Mar 20 2019, Charlene Wendling <juliana...@posteo.jp> wrote: > > Hi, > > > > On Wed, 20 Mar 2019 15:48:58 +0100 > > Jeremie Courreges-Anglas <j...@wxcvbn.org> wrote: > > > >> > >> Hi, > >> > >> filezilla fails to build at least on powerpc and sparc64: > >> > >> http://build-failures.rhaalovely.net/powerpc/2019-02-04/net/filezilla.log > >> http://build-failures.rhaalovely.net/sparc64/2019-03-04/net/filezilla.log > >> > >> --8<-- > >> checking whether pugixml has been compiled with long long support... > >> no configure: error: pugixml system library has been compiled without > >> long long support > >> -->8-- > >> > >> We have a local patch that prevents cmake from turning on long long > >> (C++11) support. I guess the diff was needed to avoid a failure with > >> cmake-3.1.x and/or base-gcc, back in 2015. > >> > >> If I remove our local patch, cmake-3.10.2 and ports-gcc happily build > >> a library with long long support activated. base-clang builds aren't > >> affected (long long support by default). > > > > Thanks a lot! > > > > I've tested on macppc, your diff solves the 'long long' issue at > > filezilla's configure time (But the build fails later sadly, and i'm > > building webkitgtk4 atm). > > Yeah I suspected that but figured that the diff would still be an > improvement. > > > By the way, HOMEPAGE should be moved to https. > > And HOMEPAGE says pugixml-1.9 has been released, so here's a diff for > both. Not tested yet, if someone wants to pick it up:
Dep's seem ok, the changelog is sane ... OK with me. I wonder why portroach didn't find the update.
