#43593: geant4: adding a variant for multithreading ------------------------------+---------------------- Reporter: patrick.sizun@… | Owner: mojca@… Type: enhancement | Status: new Priority: Low | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: haspatch Port: geant4 | ------------------------------+---------------------- Comment (by mojca@…): Speaking about compatible variant names ... here's what a `grep` for `thread` returns in other port variants: {{{ boost: variant no_single description {Disable building single- threaded libraries} gauche: variant no_threads { configure.args-delete --enable- threads=pthreads } raxml: variant pthreads conflicts hybrid description {Pthreads implementation} cherokee: variant no_pthread description {Disable threading support} sbcl: variant threads description {Enable multi-threaded runtime using the Mach pthreads interface.} tcl: variant threads description {add multithreading support} yap: variant threads abinit: variant threads description {Build with support for multi- thread support (openMP)} openmpi: variant threads description {enable threads for MPI applications} wannier90: variant threads description {Build with threaded ATLAS} hdf5: variant threadsafe description {Enable threadsafety (experimental, fails unit-tests)} octopus: # variants: berkeleygw, openmp, threads (for fftw, atlas?), scalapack, arpack }}} Did you mean `+threads` or `+threaded` when talking about Tcl? Indeed the keyword `+threads` seems to be the winner, but it also looks like some ports might need some clean up to get rid of those `no_*` variants. -- Ticket URL: <https://trac.macports.org/ticket/43593#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X