From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16197 invoked by alias); 7 Nov 2009 18:56:33 -0000 Received: (qmail 12441 invoked by alias); 7 Nov 2009 18:56:19 -0000 Date: Sat, 07 Nov 2009 18:56:00 -0000 Message-ID: <20091107185619.12439.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/41977] gfortran -fopenp and ACML_MP seem incompatible In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "nmm1 at cam dot ac dot uk" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-11/txt/msg00649.txt.bz2 ------- Comment #8 from nmm1 at cam dot ac dot uk 2009-11-07 18:56 ------- Subject: Re: gfortran -fopenp and ACML_MP seem incompatible On Nov 7 2009, rguenth at gcc dot gnu dot org wrote: > > ------- Comment #7 from rguenth at gcc dot gnu dot org 2009-11-07 18:40 > ------- I suspect acml_mp is built using a different GCC version and they > link libgomp statically. Can you check what the acml_mp library links > against? Just use ldd for this. Then check that this is consistent with > what your test program uses. Nothing noticeable. The only lines that are in the executable and not acml_mp are: libacml_mp.so => /usr/local/lib64/libacml_mp.so libgcc_s.so.1 => /lib64/libgcc_s.so.1 and the only line that is in acml_mp but not acml is: libgomp.so.1 => /usr/lib64/libgomp.so.1 No other differences (checked by diff), except for the hex. grobble in brackets. Checking the binary for the lapack version shows that the only difference from the failing one is the ACML libraries are replaced by LAPACK and BLAS. It could still be a gcc version problem, of course, but not in that respect. Regards, Nick. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41977