If only it was that simple.
It is all part of the year 2038 problem (see https://en.wikipedia.org/wiki/Year_2038_problem
Unlike the millennium bug where software developers were busy in 1999 racing to find a fix they are trying to tackle this bug early.
This is causing all sorts of problems as there is, as yet, no agreed solution.
They all know what needs to happen but are taking slightly different approaches.
The error causing, "Failed to compile OSS" is due to how "memmove" is defined. At the moment the time problem is only a warning but may become
an error in the future. It is due to different approaches taken by GlibC and the Linux kernel developers and the way OSS is compiled outside
the kernel but linked using Kmod.
Ironically if nothing had been done it would never have been a problem for x86_64 architecture PCs as I doubt that the human race will be around
in a billion years time let alone 64 bit computers.
The return value of the ktime_get_real_seconds function shouldn't matter to a sound driver as despite its name it is only being used to obtain
the date to check that the software license is still valid.
This is not a problem for GPL'ed software but is required, as 4Front use the same codebase (with nonfree additions) to build their
proprietary sound drivers.