public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "euloanty at live dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29130] New: error: #error "Assumed value of MB_LEN_MAX wrong"
Date: Sun, 08 May 2022 20:49:39 +0000 [thread overview]
Message-ID: <bug-29130-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29130
Bug ID: 29130
Summary: error: #error "Assumed value of MB_LEN_MAX wrong"
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: euloanty at live dot com
CC: carlos at redhat dot com
Target Milestone: ---
Created attachment 14094
--> https://sourceware.org/bugzilla/attachment.cgi?id=14094&action=edit
error file
i find that the gcc C freestanding headers have issues with glibc with
aarch64-Lin/home/cqwrteur/toolchains/gnu/native/aarch64-linux-gnu/aarch64-linux-gnu/include/bits/wchar2.h:398:3:
error: #error "Assumed value of MB_LEN_MAX wrong"
398 | # error "Assumed value of MB_LEN_MAX wrong"
| ^~~~~ux-gnu host etc.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-05-08 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 20:49 euloanty at live dot com [this message]
2022-05-08 20:49 ` [Bug build/29130] " euloanty at live dot com
2022-05-08 20:50 ` euloanty at live dot com
2022-05-08 20:51 ` euloanty at live dot com
2022-05-08 20:52 ` euloanty at live dot com
2022-05-09 11:29 ` [Bug libc/29130] " fweimer at redhat dot com
2022-05-09 13:32 ` euloanty at live dot com
2022-05-11 12:51 ` fweimer at redhat dot com
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-29130-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).