public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Ola x Nilsson via Libc-help <libc-help@sourceware.org>
Cc: Ola x Nilsson <ola.x.nilsson@axis.com>
Subject: Re: ppoll with -D_TIME_BITS=64 and -D_FORTIFY_SOURCE
Date: Wed, 09 Nov 2022 12:34:01 +0100	[thread overview]
Message-ID: <87cz9wfjkm.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <jwqpmdwqtti.fsf@axis.com> (Ola x. Nilsson via Libc-help's message of "Wed, 9 Nov 2022 09:31:21 +0100")

* Ola x. Nilsson via Libc-help:

> I've run into some problems when building programs using ppoll on a
> 32bit system with
> -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE -O

There's already discussion on a bug and on libc-alpha:

  ppoll() does not switch to __ppoll64 when -D_TIME_BITS=64 and
  -D_FORTIFY_SOURCE=2 is given on 32bit
  <https://sourceware.org/bugzilla/show_bug.cgi?id=29746>

  [PATCH v4] Linux: Add ppoll fortify symbol for 64 bit time_t (BZ# 29746)
  <https://sourceware.org/pipermail/libc-alpha/2022-November/143344.html>
  (plus earlier threads for previous versions)

Thanks,
Florian


      reply	other threads:[~2022-11-09 11:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09  8:31 Ola x Nilsson
2022-11-09 11:34 ` Florian Weimer [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=87cz9wfjkm.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-help@sourceware.org \
    --cc=ola.x.nilsson@axis.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. 
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 read-only IMAP folder(s) and NNTP newsgroup(s).