#warning "Consider adding the right clone() syscall definitions here!"

Mathieu Malaterre <[email protected]>
Newsgroups gmane.linux.debian.ports.mips
Message-ID <CA+7wUswA69PLn6f2RzxVeMx5tFda_u7bWVSQwD=9=zVPD6nDhg@mail.gmail.com>
Hi there,

Did anyone review the warning(s) generated during systemd building on mipsel* ?

I am starring at the clone warning (mmap seems to trigger something
equivalent apparently):

https://buildd.debian.org/status/fetch.php?pkg=systemd&arch=mips64el&ver=232-22&stamp=1490743348&raw=0

See:
http://sources.debian.net/src/systemd/232-22/src/shared/seccomp-util.c/#L726


$ man 2 clone
[...]
       On x86-32, and several other common architectures (including
score, ARM, ARM 64, PA-RISC, arc, Power PC, xtensa, and MIPS), the
order of the last two arguments is reversed:

           long clone(unsigned long flags, void *child_stack,
                     int *ptid, unsigned long newtls,
                     int *ctid);
[...]

Is this worth reporting a bug for this ?

thx
-M
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.