I wonder if this is a result of some recent changes by Erik in detecting system packages. I certainly didn’t design things to have this behaviour when I introduced the gfortran package to complement clang.
François > On 18/11/2018, at 23:30, Volker Braun <[email protected]> wrote: > > I just upgraded the buildbot to the new OSX version and I can't build Sage > any more. I've read the thread about the Mojave dumpster fire and installed > command line tools and > /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg, > so /usr/include is populated. Latest XCode. Compilation fails in GCC as per > https://trac.sagemath.org/ticket/26426, but shouldn't we use Xcode clang by > default nowadays? Relevant configure output: > > > configure: === checking whether to install the gcc SPKG === > checking for C++ compiler vendor... clang > checking whether g++ supports C++11 features by default... no > checking whether g++ supports C++11 features with -std=gnu++11... yes > checking for gcc option to accept ISO C99... none needed > checking if gcc accepts -dumpversion option... yes > checking gcc version... 4.2.1 > checking if g++ accepts -dumpversion option... yes > checking g++ version... 4.2.1 > configure: === checking whether to install the git SPKG === > checking for git... /usr/bin/git > checking for a sed that does not truncate output... /usr/bin/sed > configure: === checking whether to install the patch SPKG === > checking for GNU patch >= 2.7.0... no > configure: === checking whether to install the curl SPKG === > checking for curl 7.22... /usr/bin/curl > checking curl/curl.h usability... yes > checking curl/curl.h presence... yes > checking for curl/curl.h... yes > configure: === checking whether to install the yasm SPKG === > checking for yasm supporting the adox instruction... no > checking for Fortran flag needed to accept free-form source... unknown > configure: Your Fortran compiler does not accept free-format source code > configure: which means the compiler is either seriously broken, or > configure: is too old to build Sage. > configure: === checking whether to install the gfortran SPKG === > configure: Installing GCC because a Fortran compiler is missing > > > We all know that OSX doesn't come with a fortran compiler, but that output > comes from SAGE_MUST_INSTALL_GCC([a Fortran compiler is missing]) so it > forces installing of all of gcc? Shouldn't that just force gfortran > installation? > > > Not related, but I made https://trac.sagemath.org/ticket/26713 to deal with > the /usr/include situation > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sage-devel. > 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
