public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "euloanty at live dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/29658] New: error: '_POSIX2_LINE_MAX' was not declared in this scope for x86_64-freebsd14.0 host Date: Fri, 07 Oct 2022 07:37:20 +0000 [thread overview] Message-ID: <bug-29658-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29658 Bug ID: 29658 Summary: error: '_POSIX2_LINE_MAX' was not declared in this scope for x86_64-freebsd14.0 host Product: gdb Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- Created attachment 14383 --> https://sourceware.org/bugzilla/attachment.cgi?id=14383&action=edit config ../../../../../binutils-gdb/gdb/bsd-kvm.c: In function 'void bsd_kvm_target_open(const char*, int)': ../../../../../binutils-gdb/gdb/bsd-kvm.c:111:15: error: '_POSIX2_LINE_MAX' was not declared in this scope 111 | char errbuf[_POSIX2_LINE_MAX]; | ^~~~~~~~~~~~~~~~ ../../../../../binutils-gdb/gdb/bsd-kvm.c:127:61: error: 'errbuf' was not declared in this scope 127 | write_files ? O_RDWR : O_RDONLY, errbuf); | ^~~~~~ make[2]: *** [Makefile:1896: bsd-kvm.o] Error 1 make[2]: *** Waiting for unfinished jobs.... CC rddbg.o -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-10-07 7:37 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-07 7:37 euloanty at live dot com [this message] 2022-10-07 7:37 ` [Bug build/29658] " euloanty at live dot com 2022-10-07 7:40 ` euloanty at live dot com 2022-10-07 7:40 ` euloanty at live 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-29658-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).