From: Philipp Stephani <p.stephani2@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52431-done@debbugs.gnu.org
Subject: bug#52431: 29.0.50; Semantic bovine GCC tests failing on macOS
Date: Tue, 28 Dec 2021 21:08:29 +0100 [thread overview]
Message-ID: <CAArVCkQzQPv2PZYs7XzZ2CB-ysDB1OK90e_Oqc_oEzFBrDa5hg@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkSM3_8e7yRjEp2OLti0zFZ0Y-r2QugUD=vV2oy5Xpy9Og@mail.gmail.com>
Am Di., 28. Dez. 2021 um 21:02 Uhr schrieb Philipp Stephani
<p.stephani2@gmail.com>:
>
> Am Di., 28. Dez. 2021 um 21:00 Uhr schrieb Philipp Stephani
> <p.stephani2@gmail.com>:
> >
> > Am So., 12. Dez. 2021 um 06:58 Uhr schrieb Lars Ingebrigtsen <larsi@gnus.org>:
> > >
> > > Philipp <p.stephani2@gmail.com> writes:
> > >
> > > > I guess this test assumes a specific output from the compiler, which is
> > > > only present on GNU/Linux?
> > >
> > > The test tries to determine when running gcc gives us llvm, but it looks
> > > like the method only works on older Macos versions? So I've now updated
> > > it to check for the current Macos setup, too.
> > >
> >
> > The test still fails for me.
>
> If it helps, this is the output of gcc -v:
>
> Configured with: --prefix=/Library/Developer/CommandLineTools/usr
> --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
> Apple clang version 13.0.0 (clang-1300.0.29.30)
> Target: arm64-apple-darwin21.2.0
> Thread model: posix
> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
Hopefully fixed for real now with commit
6e52becfbe2a33c025b8c4838b3c8f06ba5a6fb8.
prev parent reply other threads:[~2021-12-28 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 13:40 bug#52431: 29.0.50; Semantic bovine GCC tests failing on macOS Philipp
2021-12-12 5:58 ` Lars Ingebrigtsen
2021-12-28 20:00 ` Philipp Stephani
2021-12-28 20:02 ` Philipp Stephani
2021-12-28 20:08 ` Philipp Stephani [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=CAArVCkQzQPv2PZYs7XzZ2CB-ysDB1OK90e_Oqc_oEzFBrDa5hg@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=52431-done@debbugs.gnu.org \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.