Hi Thomas,

On 07.03.25 09:17 Thomas Adam wrote:
> On Fri, 7 Mar 2025 at 04:49, Johannes Kastl <mail@johannes-kastl.de> wrote:
>> After figuring out that I have to use bmake aka bsd-make, not GNU
>> make, I am now stuck. Running "bmake regress" always tells me the
>> target is up to date.
> 
> That's because you don't need to use bmake in -portable.  If anything,
> I suspect that wouldn't work.

My bad, I was chasing the wrong error. The Makefile is (apparently)
not fully usable until the configure has been run. So I got lots of
syntax errors, which lead me to believe that bsdmake might be the
solution... :-)

> Could you tell us what commands you're running, using GNU Make?  For
> example, the following will work:
> 
> ./autogen.sh && ./configure && make && sudo make install

That part was missing. I needed to install all development
dependencies and run the configure like in the package build. After
that running "make tests" runs the tests. Hooray!

I need to check the test output more thorougly, but what I noticed the
most errors are like this:

> --- /tmp/got-test-commit_logmsg_ref-wRvjHlc3Cx/stdout.expected  2025-03-09 17:51:18.666666620 +0100
> +++ /tmp/got-test-commit_logmsg_ref-wRvjHlc3Cx/stdout   2025-03-09 17:51:18.683333287 +0100
> @@ -1,7 +1,7 @@
>  -----------------------------------------------
>  cherrypick e9fc3edb034bb18912e4c3372a7fef0d42f1e167 (newbranch)
>  from: Flan Hacker <flan_hacker@openbsd.org>
> -date: Sun Mar  9 17:51:18 2025 UTC
> +date: Sun Mar  9 16:51:18 2025 UTC
>   
>   changes to cherrypick but omit from the commit
>   
> test failed; leaving test data in /tmp/got-test-commit_logmsg_ref-wRvjHlc3Cx

Any idea how to fix those? Is there documentation on the tests so I
can RTFM myself?


Kind Regards,
Johannes