On 2011-Sep-08, 06:42, Alexey Dokuchaev wrote: > On Thu, Sep 08, 2011 at 08:22:13AM +0200, Pietro Cerutti wrote: > > In this particular port, whether SSE is available or not decides wheter > > a set of SSE-enabled plugins are built, in addition to the standard > > plugins. The most harm will be having a handful of additional files > > installed, that the target machine won't be able to use. On the other > > hand, reverting the change means not being able to predict which files > > will be installed, thus having leftovers, thus having a BROKEN port. > > If SSE detection is performed during run-time, isn't it simpler to just > enable SSE plugins unconditionally?
I don't see any simpler way, but I'm open to practical suggestions.
It is even possible to force the use of non-SSE plugins at run time, but
I have no way to control whether ${CONFIGURE_SCRIPT} will detect SSE or
not (other than hacking ito it). What I really need is to be able to
*predict* whether SSE-enabled plugins will be built or not, and the use
of the sysctl is the only way I have found to do so.
--
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org
PGP Public Key:
http://gahr.ch/pgp
pgpKtAgKqATY1.pgp
Description: PGP signature
