On 2019/05/20 11:24, Peter Ezetta wrote: > Ping :) > > On Thu, May 16, 2019 at 6:25 AM Peter Ezetta <protoca...@gmail.com> wrote: > > > Hi Stuart, > > > > Sorry about that, I have attached a diff instead of pasting it this time. > > > > There are quite a few changes over the last few releases. Change notes are > > available here: https://libcheck.github.io/check/NEWS > > > > - Peter > > > > > > > > On Thu, May 16, 2019 at 1:24 AM Stuart Henderson <s...@spacehopper.org> > > wrote: > > > >> On 2019/05/15 09:55, Peter Ezetta wrote: > >> > Hello Ports, > >> > > >> > The following diff updates devel/check from v0.10.0 to 0.12.0, as well > >> as > >> > updating the master site from SourceForge to GitHub. This change was > >> > required for a personal project which utilizes the ck_assert_ldouble_* > >> > macros, which were introduced in 0.11.0. > >> > > >> > I was unsure whether modifying the existing patches or creating new > >> patches > >> > was the correct way to go. This diff modifies the existing patches, but > >> I > >> > could re-do this with fresh patches if that is more appropriate. > >> > > >> > This has update been tested successfully against my own code on amd64. > >> Any > >> > testing or feedback would be greatly appreciated. > >> > >> Your diff reads OK, but it's word-wrapped and doesn't apply with patch, > >> so I haven't done a test build or checked to see if there are any changes > >> to the library that would require a SHARED_LIBS bump. > >> > >>
Committed (with a shared library bump as there are new functions exported, so a program depending against this version may not work with an older version).