public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/110085] New: make clean inside the gcc directory when configured with m2 language and for sh-elf messes up
Date: Fri, 02 Jun 2023 06:54:48 +0000	[thread overview]
Message-ID: <bug-110085-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110085

            Bug ID: 110085
           Summary: make clean inside the gcc directory when configured
                    with m2 language and for sh-elf messes up
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

make clean does:
# Delete files used by the "multilib" facility (including libgcc subdirs).
        -rm -f multilib.h tmpmultilib*
        -if [ "x$(MULTILIB_DIRNAMES)" != x ] ; then \
          rm -rf $(MULTILIB_DIRNAMES); \
        else if [ "x$(MULTILIB_OPTIONS)" != x ] ; then \
          rm -rf `echo $(MULTILIB_OPTIONS) | sed -e 's/\// /g'`; \
        fi ; fi


and one of the MULTILIB_DIRNAMES for sh-elf is m2 but m2 is also the name of
the language.

I think that part of the gcc/Makefile.in can be removed now (since libgcc is
not built inside the gcc directory for years now) but I am not 100% sure.

             reply	other threads:[~2023-06-02  6:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02  6:54 pinskia at gcc dot gnu.org [this message]
2023-06-05  4:15 ` [Bug bootstrap/110085] " pinskia at gcc dot gnu.org
2023-06-05  4:42 ` pinskia at gcc dot gnu.org
2023-06-05  5:42 ` cvs-commit at gcc dot gnu.org
2023-06-05  5:44 ` pinskia at gcc dot gnu.org
2023-06-06 21:33 ` cvs-commit at gcc dot gnu.org
2023-06-06 21:34 ` pinskia 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-110085-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: 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).