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/67102] Parallel build fails in libffi/configure
Date: Tue, 25 Jan 2022 17:47:25 +0000	[thread overview]
Message-ID: <bug-67102-4-ISQ3qWx1rM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67102-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Thomas Schwinge <tschwinge@gcc.gnu.org>:

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

commit r12-6861-gaeac414923aa1e87986c7fc6f9b921d89a9b86cf
Author: Thomas Schwinge <thomas@codesourcery.com>
Date:   Tue Jan 25 18:44:02 2022 +0100

    Revert "Fix PR 67102: Add libstdc++ dependancy to libffi" [PR67102]

    This reverts commit db1a65d9364fe72c2fff65fb2dec051728b6f3fa.

    On 2021-09-17T01:01:39-0700, Andrew Pinski via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
    > On Fri, Sep 17, 2021 at 12:46 AM Thomas Schwinge
<thomas@codesourcery.com> wrote:
    >> On 2021-09-15T13:56:37-0700, apinski--- via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
    >> > The error message is obvious -funconfigured-libstdc++-v3 is used
    >> > on the g++ command line.  So we just add the dependancy.
    >>
    >> > --- a/Makefile.def
    >> > +++ b/Makefile.def
    >> > @@ -592,6 +592,7 @@ dependencies = { module=configure-target-fastjar;
on=configure-target-zlib; };
    >> >  dependencies = { module=all-target-fastjar; on=all-target-zlib; };
    >> >  dependencies = { module=configure-target-libgo;
on=configure-target-libffi; };
    >> >  dependencies = { module=configure-target-libgo;
on=all-target-libstdc++-v3; };
    >> > +dependencies = { module=configure-target-libffi;
on=all-target-libstdc++-v3; };
    >> >  dependencies = { module=all-target-libgo; on=all-target-libbacktrace;
};
    >> >  dependencies = { module=all-target-libgo; on=all-target-libffi; };
    >> >  dependencies = { module=all-target-libgo; on=all-target-libatomic; };
    >>
    >> I'm confused, because given that this 'Makefile.def' change only has the
    >> following effect:
    >>
    >> > --- a/Makefile.in
    >> > +++ b/Makefile.in
    >> > @@ -61261,6 +61261,7 @@ all-bison: maybe-all-intl
    >> >  all-flex: maybe-all-intl
    >> >  all-m4: maybe-all-intl
    >> >  configure-target-libgo: maybe-all-target-libstdc++-v3
    >> > +configure-target-libffi: maybe-all-target-libstdc++-v3
    >> >  configure-target-liboffloadmic: maybe-configure-target-libgomp
    >> >  all-target-liboffloadmic: maybe-all-target-libgomp
    >> >  configure-target-newlib: maybe-all-binutils
    >>
    >> ... isn't that actually a no-op, because we already had such a
dependency
    >> listed?  Now twice:
    >>
    >>     $ grep -n -F 'configure-target-libffi:
maybe-all-target-libstdc++-v3' -- Makefile.in
    >>     61264:configure-target-libffi: maybe-all-target-libstdc++-v3
    >>     61372:configure-target-libffi: maybe-all-target-libstdc++-v3
    >>
    >> Compared to the existing one, the one you've added is additionally
    >> restricted by '@unless gcc-bootstrap'.
    >>
    >> I noticed this as I remembered that on our og[...] development branches
    >> we have a patch in the opposite direction: get rid of this dependency
via
    >> removing 'lang_env_dependencies = { module=libffi; cxx=true; };' from
    >> 'Makefile.def'.  See
    >>
<http://mid.mail-archive.com/alpine.DEB.2.21.9999.1812201344250.99920@build7-trusty-cs.sje.mentorg.com>
    >> "Disable libstdc++ dependency for libffi".  (Maciej CCed in case you
have
    >> any further thoughts on that.)
    >
    > Oh, I see what happened now, the old bug was actually fixed by r6-5415
    > which added cxx=true.
    > So yes my patch is actually not needed and can be reverted.
    > I tried to look to see if there was a dependency was there but for
    > some reason I did not see it.

      parent reply	other threads:[~2022-01-25 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 15:30 [Bug libffi/67102] New: " dilyan.palauzov at aegee dot org
2021-09-15  9:47 ` [Bug bootstrap/67102] " pinskia at gcc dot gnu.org
2021-09-15 10:03 ` pinskia at gcc dot gnu.org
2021-09-15 20:57 ` pinskia at gcc dot gnu.org
2021-09-16 17:54 ` cvs-commit at gcc dot gnu.org
2021-09-16 17:55 ` pinskia at gcc dot gnu.org
2022-01-25 17:47 ` cvs-commit at gcc dot gnu.org [this message]

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-67102-4-ISQ3qWx1rM@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).