> > I do think we should provide something in ports as an interim solution. > > There are other 3rd party applications looking to drop FreeBSD support > > because we are missing APIs that almost all other OS's have. I'm fine > > if the interim lives in ports and that we don't import substandard > > routines into the base. I would even be fine with calling it > > /usr/local/lib/libm_inaccurate.so. However, I do think we need an option. > > > > I think it should be called libm.so. Otherwise we have to do a serious > editing job on the Makefiles/configure scripts. I think that this is as it should be: only those applications that really need to link against such a library should do so, and this should be enforced and checked by the port maintainer. If you call it by the same name you still need to make other changes to ensure that the right library is used, and these other changes can be confusing and lead to problems, as with the openssl and gcc support libraries. Some portable applications already provide convenient variables in their build infrastructure, since the quality, coverage, and location of the math libraries varies on different systems. b.Received on Fri Jun 01 2012 - 05:17:46 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:27 UTC