On Sun, Nov 03 2019, Marc Espie <es...@nerim.net> wrote: > On Mon, Nov 04, 2019 at 02:32:03AM +0900, Daniel Dickman wrote: >> > clang doesn't error out, gcc does. >> > Why does numpy use gcc? >> >> Because that’s what upstream recommends in their docs. >> >> “Note that NumPy is developed mainly using GNU compilers. Compilers >> from other vendors such as Intel, Absoft, Sun, NAG, Compaq, Vast, >> Portland, Lahey, HP, IBM, Microsoft are only supported in the form of >> community feedback, and may not work out of the box. GCC 4.x (and >> later) compilers are recommended.” >> >> See: https://numpy.org/devdocs/user/building.html > > That's probably not a good enough reason, especially considering how many > security improvements are in base clang as opposed to base gcc...
hmmpf. I initially thought that maybe the failure was due to /usr/bin/gcc being used instead of /usr/bin/cc. I was wrong. numpy uses gfortran from ports/lang/gcc, so it makes perfect sense for some gcc-ish option parser to bail out when passed a bogus -Oprout option. And indeed math/py-numpy fails the same way with the previous python2 package on an amd64 system without /usr/bin/gcc. I'm not willing to spend more time on this but I'm not keen on seeing others waste time on this either. Sorry for bringing this up without actually checking in the first place. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
