On 4/14/11, O. Hartmann wrote:
> On 04/14/11 08:32, b. f. wrote:
>> On 4/14/11, O. Hartmann wrote:
>>> On 04/13/11 20:59, b. f. wrote:
> We had hope for clang, but clang lacks in many aspects we desperately
> need - like OpenMP support.
That may change, if:
http://wiki.llvm.org/Polyhedral_opti
On 04/14/11 08:32, b. f. wrote:
On 4/14/11, O. Hartmann wrote:
On 04/13/11 20:59, b. f. wrote:
I looked into ports/Mk/bsd.gcc.mk and found that only gcc45 is set in
case of using USE_FORTRAN, not gcc46. It would be nice also having gcc46
set, since we try to optimise for AVX in the new Intel
On 4/14/11, O. Hartmann wrote:
> On 04/13/11 20:59, b. f. wrote:
> I looked into ports/Mk/bsd.gcc.mk and found that only gcc45 is set in
> case of using USE_FORTRAN, not gcc46. It would be nice also having gcc46
> set, since we try to optimise for AVX in the new Intel Sandy-Bridge CPUs
> and gcc4
On 04/13/11 20:59, b. f. wrote:
Using a self brewn port of a scientific software package which is
intended to use gcc 4.5 or higher, I use "USE_GCC= 4.5+" in the top
level Makefile. But I get an error when starting the application:
/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.6: version GLIBCXX_3
> Using a self brewn port of a scientific software package which is
> intended to use gcc 4.5 or higher, I use "USE_GCC= 4.5+" in the top
> level Makefile. But I get an error when starting the application:
>
> /libexec/ld-elf.so.1: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.11
> required by /usr/
Using a self brewn port of a scientific software package which is
intended to use gcc 4.5 or higher, I use "USE_GCC= 4.5+" in the top
level Makefile. But I get an error when starting the application:
/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.11
required by /usr/local/i
