public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xfedch at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/29225] New: Mistyped define statement in socket/sys/socket.h in line 184
Date: Sat, 04 Jun 2022 16:33:16 +0000 [thread overview]
Message-ID: <bug-29225-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29225
Bug ID: 29225
Summary: Mistyped define statement in socket/sys/socket.h in
line 184
Product: glibc
Version: 2.35
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: network
Assignee: unassigned at sourceware dot org
Reporter: xfedch at gmail dot com
Target Milestone: ---
Created attachment 14129
--> https://sourceware.org/bugzilla/attachment.cgi?id=14129&action=edit
Patch for socket/sys/socket.h
In commit #77ede5f010f in line #184 wrote:
# defien sendmsg __sendmsg64
Statement "defien" mistyped word define. This affects application compilations
and preprocessing without defines __USE_GNU and __REDIRECT with error messages:
Syntax error at line 184, column 4, file /usr/include/sys/socket.h:
Error at line 184, column 4 in file /usr/include/sys/socket.h
# defien sendmsg __sendmsg64
Please find my path suggestion in attach.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-06-04 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 16:33 xfedch at gmail dot com [this message]
2022-06-05 23:24 ` [Bug network/29225] " sam at gentoo dot org
2022-06-05 23:25 ` sam at gentoo dot org
2022-06-06 15:55 ` adhemerval.zanella at linaro dot org
2022-06-08 12:59 ` cvs-commit at gcc dot gnu.org
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-29225-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).