public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/108142] New: Many empty directories created in the build directory Date: Fri, 16 Dec 2022 09:57:24 +0000 [thread overview] Message-ID: <bug-108142-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108142 Bug ID: 108142 Summary: Many empty directories created in the build directory Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2 Assignee: gaius at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- Seems a lot of new empty directories are created in the build directory during toplevel configure: stage{1,2,3,4}/m2 m2/ (lots of subdirectories) They are created regardless of whether m2 is in --enable-languages= or not, both when using absolute pathnames and relative (/whatever/configure --enable-languages=m2 or ../configure --enable-languages=m2 or ../configure --enable-languages=c etc.) and from what I can see, they remain empty (don't contain any non-directories) for the whole duration of build or bootstrap. Can we get rid of those, or create them only before they'd be actually used? And, preferably without those stage{1,2,3,4} toplevel directories at least (say move the stages into m2/ or even gcc/m2 subdirectory of the build directory).
next reply other threads:[~2022-12-16 9:57 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-16 9:57 jakub at gcc dot gnu.org [this message] 2022-12-21 15:05 ` [Bug modula2/108142] " ebotcazou at gcc dot gnu.org 2022-12-22 4:27 ` gaius at gcc dot gnu.org 2022-12-22 4:28 ` gaius at gcc dot gnu.org 2022-12-22 9:41 ` jakub at gcc dot gnu.org 2022-12-22 11:59 ` gaius at gcc dot gnu.org 2022-12-22 12:37 ` gaius at gcc dot gnu.org 2023-01-10 1:51 ` gaius at gcc dot gnu.org 2023-01-10 18:01 ` gaius 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-108142-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).