[RTEMS Project] #4892: MacOS tools build failures on Ventura and M series processors
trac at rtems.org
Wed Mar 29 05:57:47 UTC 2023
#4892: MacOS tools build failures on Ventura and M series processors
Reporter: Chris Johns | Owner: Chris Johns
Type: defect | Status: assigned
Priority: normal | Milestone: 6.1
Component: tool/rsb | Version: 6
Severity: normal | Resolution:
Keywords: | Blocked By:
Comment (by Chris Johns):
Replying to [comment:8 kgardas]:
> Hold on! You added patches.
Indeed I did, please read the ticket. I clearly said this at the start of
> I described two ways how is it possible to build tool and yet you claim
patches are needed when half of the patches try to deal with crashing of
gcc on your Ventura.
The patches are not attempting to address the crashing. I have no idea
what causes those. The patches address other issues. They are:
1. Using Python virtual env and cleaning up python support for MacOS. This
lets a user install python from python.org.
2. DTC did not build because of warnings treated as errors. No idea how
you missed this is you are at the same level of updates as me.
3. Libgcc uses `sh` and not `$(SHELL)` in it's `Makefile.in`. I have not
looked into why I got it but something is different in the set up or
environment to trigger it.
4. Add homebrew as a I wanted to try building `xgcc` with `gcc` rather
than Xcode. It did not help so I am currently considering dropping that
> Also you claim homebrew is optional yet you like to use it's gcc/g++ to
I have not yet added Homebrew support. It is sitting in a patch. I would
prefer not to have it part of the build. I have explained this on the
devel list in the past.
> A bit contradicting.
I did not and have not and I cannot understand why you need to talk to me
like this. Can you please not?
> Anyway, please make sure you are on the *LATEST* Ventura and not on the
I am on the latest.
> If you update, you will see your gcc crashes may be gone for good. I
reported that on devel@ few times already.
They have not gone for me. I am on an M2 Pro and I think you are on an M1.
> Yes, makeinfo is still required by RSB otherwise I would not install it.
The RSB checks but is it needed in any packages these days? It was added
long ago when all projects built the docs by default using it. We do not
build doc. If needed support should be added like `gsed`.
> Yes, if RSB build its own xz and python and whatever, it would be good.
The RSB is written in python so building python would be difficult without
it already being installed. Ah yes `xz` is another. I built that by hand
and had forgotten.
Ticket URL: <http://devel.rtems.org/ticket/4892#comment:9>
RTEMS Project <http://www.rtems.org/>
More information about the bugs