public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/114895] New: Build failure with !HAVE_WORKING_STAT Date: Tue, 30 Apr 2024 06:54:31 +0000 [thread overview] Message-ID: <bug-114895-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114895 Bug ID: 114895 Summary: Build failure with !HAVE_WORKING_STAT Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org Target Milestone: --- [31724s] libtool: compile: /home/abuild/rpmbuild/BUILD/gcc-14.0.1+git9885/obj-x86_64-suse-linux/./gcc/xgcc -B/home/abuild/rpmbuild/BUILD/gcc-14.0.1+git9885/obj-x86_64-suse-linux/./gcc/ -B/usr/x86_64-suse-linux/bin/ -B/usr/x86_64-suse-linux/lib/ -isystem /usr/x86_64-suse-linux/include -isystem /usr/x86_64-suse-linux/sys-include -DHAVE_CONFIG_H -I. -I../../../../libgfortran -iquote../../../../libgfortran/io -I../../../../libgfortran/../gcc -I../../../../libgfortran/../gcc/config -I../../.././gcc -I../../../../libgfortran/../libgcc -I../../libgcc -I../../../../libgfortran/../libbacktrace -I../../libbacktrace -I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wextra -Wwrite-strings -Werror=implicit-function-declaration -Werror=vla -fcf-protection -mshstk -fcx-fortran-rules -ffunction-sections -fdata-sections -g -O2 -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -m32 -MT unix.lo -MD -MP -MF .deps/unix.Tpo -c ../../../../libgfortran/io/unix.c -fPIC -DPIC -o .libs/unix.o [31724s] ../../../../libgfortran/io/unix.c: In function ‘find_file’: [31724s] ../../../../libgfortran/io/unix.c:1704:26: error: ‘id’ undeclared (first use in this function) [31724s] 1704 | # define FIND_FILE0_ARGS id, path [31724s] | ^~ [31724s] ../../../../libgfortran/io/unix.c:1778:30: note: in expansion of macro ‘FIND_FILE0_ARGS’ [31724s] 1778 | u = find_file0 (unit_root, FIND_FILE0_ARGS); [31724s] | ^~~~~~~~~~~~~~~ [31724s] ../../../../libgfortran/io/unix.c:1704:26: note: each undeclared identifier is reported only once for each function it appears in [31724s] 1704 | # define FIND_FILE0_ARGS id, path [31724s] | ^~ [31724s] ../../../../libgfortran/io/unix.c:1778:30: note: in expansion of macro ‘FIND_FILE0_ARGS’ [31724s] 1778 | u = find_file0 (unit_root, FIND_FILE0_ARGS); [31724s] | ^~~~~~~~~~~~~~~ [31724s] make[6]: *** [Makefile:6863: unix.lo] Error 1 which is because find_file does #if defined(__MINGW32__) && !HAVE_WORKING_STAT id = id_from_path (path); #endif RDLOCK (&unit_rwlock); retry: u = find_file0 (unit_root, FIND_FILE0_ARGS); so as long as __MINGW32__ is not defined this won't work. The fix might be to remove the __MINGW32__ part of the conditional. (and no, I didn't yet know how we arrived at !HAVE_WORKING_STAT - this is on x86_64 linux, but with a -j1 build - see https://bugzilla.suse.com/show_bug.cgi?id=1223169)
next reply other threads:[~2024-04-30 6:54 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-30 6:54 rguenth at gcc dot gnu.org [this message] 2024-04-30 6:58 ` [Bug libfortran/114895] " rguenth at gcc dot gnu.org 2024-04-30 7:01 ` rguenth at gcc dot gnu.org 2024-04-30 7:07 ` rguenth at gcc dot gnu.org 2024-04-30 7:48 ` jakub at gcc dot gnu.org 2024-04-30 7:53 ` jakub at gcc dot gnu.org 2024-04-30 7:55 ` jakub at gcc dot gnu.org 2024-05-02 7:03 ` rguenth at gcc dot gnu.org 2024-05-02 7:16 ` sjames at gcc dot gnu.org 2024-05-02 7:26 ` rguenth at gcc dot gnu.org 2024-05-02 7:29 ` sjames at gcc dot gnu.org 2024-05-02 7:44 ` rguenth 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-114895-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).