public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/110085] make clean inside the gcc directory when configured with m2 language and for sh-elf messes up
Date: Mon, 05 Jun 2023 05:42:22 +0000	[thread overview]
Message-ID: <bug-110085-4-ubcw77O5Bs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110085-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:afd87299cefd021daf0158d5b6276c37013996b9

commit r14-1541-gafd87299cefd021daf0158d5b6276c37013996b9
Author: Andrew Pinski <apinski@marvell.com>
Date:   Mon Jun 5 04:32:00 2023 +0000

    Fix PR 110085: `make clean` in GCC directory on sh target causes a failure

    On sh target, there is a MULTILIB_DIRNAMES (or is it MULTILIB_OPTIONS)
named m2,
    this conflicts with the langauge m2. So when you do a `make clean`, it will
remove
    the m2 directory and then a build will fail. Now since
r0-78222-gfa9585134f6f58,
    the multilib directories are no longer created in the gcc directory as
libgcc
    was moved to the toplevel. So we can remove the part of clean that removes
those
    directories.

    Tested on x86_64-linux-gnu and a cross to sh-elf that `make clean` followed
by
    `make` works again.

    OK?

    gcc/ChangeLog:

            PR bootstrap/110085
            * Makefile.in (clean): Remove the removing of
            MULTILIB_DIR/MULTILIB_OPTIONS directories.

  parent reply	other threads:[~2023-06-05  5:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02  6:54 [Bug bootstrap/110085] New: " pinskia at gcc dot gnu.org
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 [this message]
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-ubcw77O5Bs@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).