public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/106977] [13 regression] d21 dies with SIGBUS on 32-bit Darwin
Date: Mon, 07 Nov 2022 14:49:33 +0000	[thread overview]
Message-ID: <bug-106977-4-suBjCZ2nI1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106977-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #1 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
> Is there a (sort of simple) bootstrap process one can follow for 32-bit OSX?
>
> I have the means to test locally, but I can't get much further than building
> gdc-11 -m32 - using said compiler to bootstrap mainline fails for non-D related
> reasons when building stage1.

I'm just using gdc 11.2.1 as of
1250dcee74985eaeacae3b85e5ec78937225d322, configure with

/vol/gcc/src/hg/gcc-11-branch/local/configure --prefix=/vol/gcc-11
--enable-objc-gc --with-gmp-include=/vol/gcc/include
--with-gmp-lib=/vol/gcc/lib/amd64 --with-mpfr-include=/vol/gcc/include
--with-mpfr-lib=/vol/gcc/lib/amd64 --with-mpc-include=/vol/gcc/include
--with-mpc-lib=/vol/gcc/lib/amd64 --with-target-bdw-gc-include=/vol/gcc/include
--with-target-bdw-gc-lib=/vol/gcc/lib/amd64,i386=/vol/gcc/lib
--enable-libphobos --enable-languages=c,ada,c++,d,fortran,lto,objc,obj-c++

Most of this can be ignored for the issue at hand.  I think only
--enable-languages=d (if at all) and --enable-libphobos are required.

The 11.3 release should do just fine, I believe.

Apart from that, nothing springs to mind immediately.

My builds are on Mac OS X 10.7/Darwin 11 still.  What macOS version are
you trying this on?  FWIW, I gave up on 32-bit builds with macOS
10.14/Darwin 18 when Apple made it close to impossible to build 32-bit
software.

  parent reply	other threads:[~2022-11-07 14:49 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 14:06 [Bug d/106977] New: " ro at gcc dot gnu.org
2022-09-21  7:48 ` [Bug d/106977] " rguenth at gcc dot gnu.org
2022-11-07 14:37 ` ibuclaw at gdcproject dot org
2022-11-07 14:49 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2022-11-07 15:34 ` ibuclaw at gdcproject dot org
2022-11-07 15:43 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-02-22 23:58 ` iains at gcc dot gnu.org
2023-02-23  1:20 ` ibuclaw at gcc dot gnu.org
2023-02-23  7:38 ` iains at gcc dot gnu.org
2023-02-23 10:21 ` iains at gcc dot gnu.org
2023-02-23 10:43 ` ibuclaw at gcc dot gnu.org
2023-02-23 10:50 ` ibuclaw at gcc dot gnu.org
2023-02-23 10:51 ` iains at gcc dot gnu.org
2023-02-23 22:49 ` ibuclaw at gcc dot gnu.org
2023-02-23 23:11 ` ibuclaw at gcc dot gnu.org
2023-02-23 23:29 ` iains at gcc dot gnu.org
2023-02-23 23:33 ` pinskia at gcc dot gnu.org
2023-02-23 23:34 ` iains at gcc dot gnu.org
2023-02-23 23:36 ` iains at gcc dot gnu.org
2023-02-23 23:55 ` pinskia at gcc dot gnu.org
2023-02-24  0:00 ` pinskia at gcc dot gnu.org
2023-02-24  1:13 ` ibuclaw at gcc dot gnu.org
2023-02-24  2:03 ` ibuclaw at gcc dot gnu.org
2023-02-24  2:12 ` ibuclaw at gcc dot gnu.org
2023-02-24  7:52 ` iains at gcc dot gnu.org
2023-02-24  8:20 ` ibuclaw at gcc dot gnu.org
2023-02-24  8:46 ` iains at gcc dot gnu.org
2023-02-24 11:39 ` ibuclaw at gcc dot gnu.org
2023-02-24 17:48 ` iains at gcc dot gnu.org
2023-02-24 18:14 ` iains at gcc dot gnu.org
2023-02-24 18:39 ` ibuclaw at gcc dot gnu.org
2023-02-24 20:07 ` iains at gcc dot gnu.org
2023-04-26  6:56 ` [Bug d/106977] [13/14 " rguenth at gcc dot gnu.org
2023-06-28 18:19 ` cvs-commit at gcc dot gnu.org
2023-06-28 18:52 ` cvs-commit at gcc dot gnu.org
2023-06-28 18:57 ` ibuclaw at gcc dot gnu.org
2023-06-29  7:52 ` iains 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-106977-4-suBjCZ2nI1@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).