Sorry about being unresponsive lately. Trying to correct that (a bit) with
this response.
I haven't upgraded any machine to Fedora 32 yet (I'll do it soon), so I
can't test this myself. But I can make a suggestion without trying it:

On Tue, May 5, 2020 at 6:09 PM Waldek Kozaczuk <jwkozac...@gmail.com> wrote:

> Trying to build OSv on Fedora 32 with GCC 10 yields (unsurprisingly)
> errors:
>
> "  AS arch/x64/boot.S
>   CXX bsd/init.cc
>   CXX bsd/net.cc
>   CXX bsd/x64/machine/in_cksum.cc
>   CC bsd/sys/crypto/rijndael/rijndael-alg-fst.c
>   CC bsd/sys/crypto/rijndael/rijndael-api.c
> In file included from include/osv/mutex.h:84,
>                  from arch/x64/exceptions.hh:15,
>                  from arch/x64/arch-cpu.hh:12,
>                  from include/osv/sched.hh:13,
>                  from include/osv/percpu.hh:11,
>                  from ./bsd/porting/uma_stub.h:161,
>                  from ./bsd/sys/sys/mbuf.h:40,
>                  from bsd/x64/machine/in_cksum.cc:45:
> /usr/include/c++/10/mutex: In member function ‘bool
> std::timed_mutex::_M_clocklock(clockid_t, const __gthread_time_t&)’:
> /usr/include/c++/10/mutex:270:17: error: ‘pthread_mutex_clocklock’ was not
> declared in this scope; did you mean ‘pthread_mutex_timedlock’?
>   270 |       { return !pthread_mutex_clocklock(&_M_mutex, clockid,
> &__ts); }
>

It appears that the new <mutex> C++ header file (included by
include/osv/mutex.h, I don't remember why) needs pthread_mutex_clocklock()
to be defined in our pthread header files.

Let's just implement this function. Seeing that our
pthread_mutex_timedlock() is already a stub (nobody ever complained...),
pthread_mutex_clocklock() can also be a stub.
I think this will be easy, and hopefully work.

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/osv-dev/CANEVyjtRSPfAa2xtFg%3DfkxNweJ-KrKotDV03SVZ%2B1J0wMrMkDw%40mail.gmail.com.

Reply via email to