On 2015/10/29 15:05, ni...@openbsd.org wrote: > GitHub is currently expecting to use the standard dynamic tarballs not > the uploaded tarballs.
https://github.com/blog/1547-release-your-software doesn't suggest that dynamic tarballs are expected. And indeed dynamic tarballs are responsible for all the half-finished releases you see without generated configure scripts (risking user problems if they try and build it with a bad autoconf version, etc). > sh & vax don't have cunit, so can either skip including nghttp2 in curl > as nghttp2 can't be tested, curl itself doesn't look like it does much > testing of nghttp2 and the --http2 option. I prefer to keep things simple and use the same dependency chain on all arch. > Best I could come up with so far..... > > TEST_DEPENDS = devel/cunit > pre-test: > rm ${WRKDIR}/build-amd64/.configure_done > make configure ${WRKBUILD}... but doing it this way feels like too much magic. Updated tarball attached, naddy spotted missing -I/-L in CONFIGURE_ENV dating from when I tried to build the examples/hpack tools.
nghttp2.tgz
Description: application/tar-gz