public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Linux: Forward declaration of struct iovec for process_madvise
Date: Wed, 29 Jun 2022 11:55:20 +0000 (GMT)	[thread overview]
Message-ID: <20220629115520.8AB633854153@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ecd0fbebc0ce2818ac87ca1ed2ce46a733e8c839

commit ecd0fbebc0ce2818ac87ca1ed2ce46a733e8c839
Author: Florian Weimer <fweimer@redhat.com>
Date:   Wed Jun 29 13:50:50 2022 +0200

    Linux: Forward declaration of struct iovec for process_madvise
    
    This maintains compatibility between <sys/mman.h> and <linux/uio.h>.
    Before that, the addition of process_madvise made those two header
    files incompatible.  This has been observed resulting in a build
    failure in LLDB's Process/Linux/NativeRegisterContextLinux_s390x.cpp
    source file.
    
    Fixes commit d19ee3473d68ca0e794f3a8b7677a0983ae1342e
    ("linux: Add process_madvise").
    
    Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

Diff:
---
 sysdeps/unix/sysv/linux/bits/mman_ext.h | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/sysdeps/unix/sysv/linux/bits/mman_ext.h b/sysdeps/unix/sysv/linux/bits/mman_ext.h
index 97234a7adf..5612852e64 100644
--- a/sysdeps/unix/sysv/linux/bits/mman_ext.h
+++ b/sysdeps/unix/sysv/linux/bits/mman_ext.h
@@ -21,11 +21,8 @@
 #endif
 
 #ifdef __USE_GNU
-#include <bits/types/struct_iovec.h>
-
-/*
- */
-extern __ssize_t process_madvise (int __pid_fd, const struct iovec* __iov,
+struct iovec;
+extern __ssize_t process_madvise (int __pid_fd, const struct iovec *__iov,
 				  size_t __count, int __advice,
 				  unsigned __flags)
   __THROW;


                 reply	other threads:[~2022-06-29 11:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220629115520.8AB633854153@sourceware.org \
    --to=fw@sourceware.org \
    --cc=glibc-cvs@sourceware.org \
    /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).