Date: Sat, 26 May 2018 08:58:55 -0600 From: Adam Weinberger <adamw@adamw.org> To: matthew@freebsd.org Cc: freebsd-ports@freebsd.org Subject: Re: How to debug this... Message-ID: <CAP7rwcgyMLKbDj8yADs0LUcWDzAy4_0zXSF9wHzqdJApPfA_AA@mail.gmail.com> In-Reply-To: <4e795677-e0a1-55c8-77de-017b416aa367@FreeBSD.org> References: <4e795677-e0a1-55c8-77de-017b416aa367@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 26, 2018 at 5:20 AM Matthew Seaman <matthew@freebsd.org> wrote: > Hi, Folks, > Here's something that's had me head-scratching for a while. I've what > should be a pretty routine update to sysutils/rsyslog8 in the works, > except that my test builds in poudriere all bomb out with: > =======================<phase: check-sanity > ============================ > make: don't know how to make check-sanity. Stop > make: stopped in /usr/ports/sysutils/rsyslog8 > =>> Cleaning up wrkdir > ===> Cleaning for rsyslog-8.35.0 > build of sysutils/rsyslog8 | rsyslog-8.35.0 ended at Fri May 25 08:51:36 > BST 2018 > build time: 00:00:01 > !!! build failure encountered !!! > It looks like a fairly obvious problem -- or it should be. Except that > I can't reproduce this in a way that I can debug it effectively. Just > building the updated port ... works fine. Using poudriere -i to go into > the poudriere build environment and building the port there ... works > fine. Anything else I've tried -- no improvement, enlightenment still > proving elusive. > It's definitely specific to this version of rsyslog -- 8.34.0 builds > just fine, and I've not seen anything similar for any of the multitude > of other ports I've built. > Any ideas? > Cheers, > Matthew Hi Matthew, Does it work properly against the version in head? If so, what's your patch look like? # Adam -- Adam Weinberger adamw@adamw.org https://www.adamw.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAP7rwcgyMLKbDj8yADs0LUcWDzAy4_0zXSF9wHzqdJApPfA_AA>