public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/31050] Compile error in gnulib/import/closedir.c
Date: Fri, 10 Nov 2023 23:18:31 +0000 [thread overview]
Message-ID: <bug-31050-4717-gm2RfwOkhl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31050-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31050
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
I gave it a try (on Arch Linux, not Fedora) and I don't see it.
Your error happens in a !HAVE_CLOSEDIR path. Whereas in my build,
HAVE_CLOSEDIR is defined:
/* Define to 1 if you have the `closedir' function. */
#define HAVE_CLOSEDIR 1
Can you check in build/gnulib/config.log, what happened when gnulib probed for
closedir? In my case, I see:
configure:23178: checking for closedir
configure:23178: i686-w64-mingw32-gcc -o conftest.exe -g -O2
-Wl,--stack,12582912 conftest.c >&5
configure:23178: $? = 0
configure:23178: result: yes
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-10 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 23:04 [Bug build/31050] New: " madebr at gmail dot com
2023-11-10 23:18 ` simark at simark dot ca [this message]
2023-11-10 23:28 ` [Bug build/31050] " madebr at gmail 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-31050-4717-gm2RfwOkhl@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: 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).