mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Cc: Baruch Siach <baruch@tkos.co.il>
Subject: Re: [musl] Switch to 64-bit time_t breaks strace build
Date: Thu, 26 Mar 2020 10:49:41 -0400	[thread overview]
Message-ID: <20200326144941.GB11469@brightrain.aerifal.cx> (raw)
In-Reply-To: <87lfnndzwv.fsf@tarshish>

On Thu, Mar 26, 2020 at 03:11:12PM +0200, Baruch Siach wrote:
> Hi musl list,
> 
> Commit 381433396 (switch all existing 32-bit archs to 64-bit time_t)
> changed the IPC_STAT value on 32-bit arches from 2 to 0x102. This break
> strace build time assertion of IPC_STAT value:
> 
> In file included from ./static_assert.h:11,
>                  from xlat/msgctl_flags.h:4,
>                  from ipc_msgctl.c:32:
> xlat/msgctl_flags.h:22:1: error: static assertion failed: "IPC_STAT != 2"
>  static_assert((IPC_STAT) == (2), "IPC_STAT != 2");
> 
> I that a strace bug?

Yes, it's one of the things mentioned in the time64 release notes:

https://musl.libc.org/time64.html

The upstream bug is:

https://github.com/strace/strace/issues/116

and it's fixed in:

https://github.com/strace/strace/commit/ce2c968a614ae2a3cf2354620b3b8200f003e87c

There are also some other non-build-breaking bugs with decoding of
structs, such as:

https://github.com/strace/strace/issues/122

I suspect most if not all are fixed now but I haven't checked lately.

Rich

      reply	other threads:[~2020-03-26 14:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 13:11 Baruch Siach
2020-03-26 14:49 ` Rich Felker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200326144941.GB11469@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=baruch@tkos.co.il \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).