public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daan.j.demeyer at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29354] New: netinet/in.h redefines in_addr if linux/in.h is included first
Date: Mon, 11 Jul 2022 12:55:48 +0000	[thread overview]
Message-ID: <bug-29354-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29354

            Bug ID: 29354
           Summary: netinet/in.h redefines in_addr if linux/in.h is
                    included first
           Product: glibc
           Version: 2.36
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: daan.j.demeyer at gmail dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

netinet/in.h already has logic to not redefine in6_addr if linux/in6.h has
already been included. It'd be great if we could do the same for in_addr.

To reproduce, try to compile a source file that includes linux/in.h followed by
netinet/in.h

-- 
You are receiving this mail because:
You are on the CC list for the bug.

                 reply	other threads:[~2022-07-11 12: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=bug-29354-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).