On Mon, Jul 4, 2016 at 4:48 PM, YANG Boyuan <[email protected]> wrote: > Hi, > > Upstream seems to be using both a testing m4 script grabbed from > Google[0] **and** a hardcoded list to determine whether > -fstack-protector should be enabled. It's strange that the test was > passed on hppa[1] and alpha[2]. Maybe the testing case is broken? > > I may dig into it afterwards, but I can't find any alpha/hppa machine :-( > > +1 for using `--disable-ssp' globally and depend on dpkg-buildflags, > if it works. Yet the problem may need be solved upstream later.
Dear Boyuan, First, I have to admit that I don't have much knowledge on autotools. I tried to follow your comment, and here's the result, which is in "disable-ssp" branch: - https://anonscm.debian.org/git/collab-maint/shadowsocks-libev.git/commit/?h=disable-ssp&id=90ce60 I already tried to build by git-pbuilder, and it built fine. Please kindly help to confirm this is just the way you're preparing to fix. Thank you! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
