> Done. Replacing "cc" with "gcc45" built the library without any error. > (I didn't need to specify the full path to gcc45.) > > So the question is, why is cc being invoked in the first place? As far > as I know, I'm not doing anything to force using it. Something seems to > have gone wrong during py-numpy's configtests...
By default, this port and some of its prerequisites are built with lang/gcc45 and devel/binutils, because they USE_FORTRAN, while other prerequisites are built with the older (and not completely compatible) base system compiler and base system toolchain. This has led to problems in the past, and they have not all been solved. So you should be alert when dealing with this port and any dependent ports, and make sure that they are using gcc45, /usr/local/bin/ld, etc., rather than their older base system counterparts, which may be cached in different files, e.g., /usr/local/lib/python*/config/Makefile, /usr/local/lib/python*/site-packages/numpy/distutils/site.cfg, or /usr/local/lib/python*/site-packages/numpy/distutils/system_info.py. Also, the ports should link with the appropriate LDFLAGS directing them to the newer shared libraries in /usr/local/lib/gcc45, rather than the older libraries in /usr/lib. b. _______________________________________________ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
