https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
Jens-S. Vöckler changed:
What|Removed |Added
CC||jens4303 at me dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
--- Comment #73 from Jens-S. Vöckler ---
I agree with Damien Merenne: I recently tried to build gcc 8 on High Sierra on
an APFS in various ways, and it failed every time. I used my old work-around of
creating an HFS+ partition-in-a-file to build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
--- Comment #82 from Jens-S. Vöckler ---
I had some prior issues with w.r.t 32bits. Tinkering, this script does build a
gcc 9.1 on macOS 10.14.5 on APFS. I didn't create it for beauty, and it's
specific to my setup. The resulting compiler is unab
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
--- Comment #55 from Jens-S. Vöckler ---
Would it be worthwhile to limit it to "darwin" *and* "apfs" on objdir? I am
thinking of something along the lines of
diskutil info $(stat -f '%Sd' /path/to/objdir) | \
perl -lane 'print $F[$#F] if /^
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
--- Comment #57 from Jens-S. Vöckler ---
(In reply to Francois-Xavier Coudert from comment #56)
> I would advise to keep it simple.
Agreed: Simple is better.
