On Saturday, May 11, 2019 at 9:21:19 AM UTC-5, Dima Pasechnik wrote: > > On Sat, 11 May 2019 15:12 Josh Haberman, <jhab...@gmail.com <javascript:>> > wrote: > >> I just got the same error. I can attempt the workaround also, but is >> there a more permanent fix that would avoid the need for the workaround? >> Why is gfortran looking for this specific directory? >> > > every sane Unix system, except MacOS 10.14, has system header files in > /usr/include >
Right but you don't usually need to specifically look for this directory or pass -I to find files there. A regular invocation of the compiler will look in the system header directories. I am curious why the build system is specifically inspecting this directory. > It could be that the newer versions of gcc have a fix. Anyhow, > you could also install Homebrew and have gfortran, gmp, yasm, and a number > of other Sage packages installed there, then they won't even need to be > built... > I tried installing gcc (which includes gfortran) from Homebrew, and then I set "export SAGE_INSTALL_GCC=no" but it tried (and failed) building gfortran anyway. Maybe I need to unset "SAGE_KEEP_BUILT_SPKGS=yes" so it starts over from scratch? Or maybe I need to make the brew "gcc" available as "gcc" instead of "gcc-9", which is what it got installed as. Also I tried the workaround of installing /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg but then the build of gfortran fails with: "strip: invalid option -- c" I think this is because it found the Homebrew-installed GNU /usr/local/bin/strip instead of the macOS /usr/bin/strip. On Saturday, March 2, 2019 at 7:09:45 AM UTC-6, Jeremy Martin wrote: >>> >>> I just had to reinstall Sage (now running Mojave). I got the same error >>> as I had reported earlier, even though the command line tools were >>> installed. I followed Michael's suggestions and the build proceeded fine. >>> Thank you! >>> -Jeremy >>> >>> On Wednesday, October 10, 2018 at 9:47:45 PM UTC-5, Michael Frey wrote: >>>> >>>> I get the same error with MAcOS Mojave and Xcode 10.0. The release >>>> notes for Xcode 10 state that /usr/include is being relocated to >>>> /Library/Developer//CommandLineTools/SDKs/MacOSX.sdk/usr/include/. >>>> See the Xcode 10 release notes: >>>> https://developer.apple.com/documentation/xcode_release_notes/xcode_10_release_notes. >>>> >>>> There is a temporary workaround by installing >>>> /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg. >>>> >>>> >>>> -- >> You received this message because you are subscribed to the Google Groups >> "sage-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-...@googlegroups.com <javascript:>. >> To post to this group, send email to sage-...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/sage-devel. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/sage-devel/8a4caf26-93cb-432d-beab-91469828e627%40googlegroups.com >> >> <https://groups.google.com/d/msgid/sage-devel/8a4caf26-93cb-432d-beab-91469828e627%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/f52807f3-8303-459e-a839-642a101243dc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
