On Wednesday, September 14, 2016 at 8:37:47 AM UTC, François wrote: > > > > On 14/09/2016, at 20:31, Vincent Delecroix <20100.d...@gmail.com > <javascript:>> wrote: > > > > On 14/09/16 10:26, Jeroen Demeyer wrote: > >> On 2016-09-14 10:18, Vincent Delecroix wrote: > >>> On 14/09/16 10:14, Jeroen Demeyer wrote: > >>>> On 2016-09-14 10:07, Vincent Delecroix wrote: > >>>>> Apparently, there needs to be a libc with headers on the host to > have > >>>>> anything related to compilation working properly. Is that right? > >>>> > >>>> Obviously yes. You cannot compile C code without a working toolchain > >>>> (this includes a compiler, assembler, linker, header files, > libraries). > >>> > >>> Then why gcc is shipped within the dmg? > >> > >> We ship GCC with the binaries for the same reason that we install GCC > >> within Sage: to be able to compile C/C++/Fortran code provided that the > >> rest of the toolchain is available from the system. In other words, it > >> is meant for people who do have XCode installed. > > > > If XCode is installed, there is gcc on the system. This is the part I do > not understand. > > > No. You have clang - which may have an alias pretending to be gcc. > > did anyone try to build Sage with recent Xcode clang? Perhaps it would work (one advantage is that it's faster). One still would have to do something to provide fortran, though.
Dima > François -- 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. For more options, visit https://groups.google.com/d/optout.
