Date: Wed, 14 Dec 2016 17:12:30 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 215191] news/nzbget Update to 17.1 Message-ID: <bug-215191-13-28jVZBsCJW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-215191-13@https.bugs.freebsd.org/bugzilla/> References: <bug-215191-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215191 --- Comment #3 from Toxic <toxic@doobie.com> --- Thanks for catching that. I haven't been testing on 9.x for a little while= , as I've upgraded all of my systems. The zlib/pkg-config problem turns out to be just the beginning. It's easily fixed by passing environment variables to the configure script, by adding something like this to Makefile: CONFIGURE_ENV=3D LOCALBASE=3D"${LOCALBASE}" \ zlib_LIBS=3D"-lz " \ zlib_CFLAGS=3D" " But that just reveals a number of other build failures, that at first glance seem to be related to differences between libc++ and stdlibc++. I won't ha= ve the free time to dig into it for at least a few days. If someone else is familiar with C++14, stdlibc++ and 9.3, and has the opportunity to take a l= ook, please do. It might be just a matter of using a GNU compiler/toolchain on 9.3, which w= ill probably be the first thing I try when I next get the opportunity to dig in. With that said, the EOL of FreeBSD 9 is 17 days away on Dec 31. I'm inclin= ed to leave 16.4 as the supported Nzbget version through the end of the year, = and not have this port committed/updated until it's fair to drop 9.x support. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215191-13-28jVZBsCJW>