|
| From: | Dmitry Roshchin |
| Subject: | Re: [RFC] build with OpenMP by default? |
| Date: | Wed, 23 Apr 2014 11:27:05 +0400 |
| User-agent: | KMail/4.12.4 (Linux/3.11.10-7-desktop; KDE/4.12.4; x86_64; ; ) |
On Tuesday 22 April 2014 09:31:11 Mike Miller wrote: > Is it time to build Octave with OpenMP by default? It looks to me like > it's been an "experimental" disabled-by-default option since the 3.4.0 > release. It has been enabled in Debian and Ubuntu builds since 3.4.3 > was released in late 2011 and I'm not aware of any negative > consequences. > Not all octave-forge packages build with enabled OpenMP. At least: geometry >[ 573s] /home/abuild/rpmbuild/BUILD/octave- forge/install/geometry-1.7.0/i586-suse-linux-gnu-api-v49+/_oc_polybool.oct: failed to load: /home/abuild/rpmbuild/BUILD/octave- forge/install/geometry-1.7.0/i586-suse-linux-gnu-api-v49+/_oc_polybool.oct: undefined symbol: GOMP_parallel_start nurbs > [ 1340s] /home/abuild/rpmbuild/BUILD/octave- forge/install/nurbs-1.3.7/x86_64-suse-linux-gnu-api-v49+/bspeval.oct: failed to load: /home/abuild/rpmbuild/BUILD/octave-forge/install/nurbs-1.3.7/x86_64- suse-linux-gnu-api-v49+/bspeval.oct: undefined symbol: GOMP_parallel_start
| [Prev in Thread] | Current Thread | [Next in Thread] |