Page MenuHomeFreeBSD

sysutils/cmocka: Update cmocka from version 1.1.3 to 1.1.5

Authored by dteske on Dec 2 2019, 4:29 AM.



Update cmocka to latest version.

Test Plan

Install port. Check installed files. Uninstall.
Make package. Install package. Uninstall package.

Diff Detail

rP FreeBSD ports repository
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

This revision is now accepted and ready to land.Dec 2 2019, 6:08 AM
swills added inline comments.
14 ↗(On Diff #65113)

Why :noninja here, it doesn't seem required?

14 ↗(On Diff #65113)

On 12.0-RELEASE attempting to compile without :noninja results in the following error:

[0/1] /usr/local/bin/cmake -S/home/dteske/src/freebsd/ports/sysutils/cmocka/work/cmocka-1.1.5 -B/home/dteske/src/freebsd/ports/sysutils/cmocka/work/.build
-- Configuring done
-- Generating done
-- Build files have been written to: /home/dteske/src/freebsd/ports/sysutils/cmocka/work/.build
ninja: error: manifest '' still dirty after 100 tries

===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

make[1]: stopped in /home/dteske/src/freebsd/ports/sysutils/cmocka
*** Error code 1

make: stopped in /home/dteske/src/freebsd/ports/sysutils/cmocka
14 ↗(On Diff #65113)

Strange, I'm not able to reproduce. Can you confirm what version of ninja you're using? I'm using ninja-1.9.0,2.

14 ↗(On Diff #65113)


14 ↗(On Diff #65113)

My build was in a jail, so I thought maybe that may be the source of the difference, so I tried reproducing this on ref12-amd64 and wasn't able to reproduce there either. But ref12-amd64 is running 12-STABLE, so maybe it's only an issue for 12.0-RELEASE? Any ideas?

14 ↗(On Diff #65113)

In case it helps:

dteske@scribe12 devel > uname -a
FreeBSD scribe12 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC  amd64
14 ↗(On Diff #65113)

I wonder if it's related to this issue:

There seems to be an implication there that it's related to some sort of local issue, perhaps NFS or some sort of system time issue?

14 ↗(On Diff #65113)

It might be the date/time. Let me see if that fixes it.

dteske@scribe12 ~ > date
Tue Oct 29 05:36:17 UTC 2019

Remove noninja args to USES=cmake

Problem was date/time. We should discuss how we can improve error-
condition checking to alert the user of this condition since the
current error is not very forthcoming.

This revision now requires review to proceed.Dec 2 2019, 5:54 PM
dteske added inline comments.
14 ↗(On Diff #65113)

It was the date/time.

We should potentially discuss adding some error checking to the cmake include under Mk/Uses to perhaps alert the user when the date/time is too far behind, since ninja doesn't like that.

This revision is now accepted and ready to land.Dec 2 2019, 6:09 PM