On Tue, May 07, 2019 at 10:47:40AM +0200, FX wrote:
> >> Those are certainly exported from my GCC 9 libgomp.so.1.0.0 (at least on
> >> Linux but I don't see how it could not be elsewhere).
>
> I can confirm they are present.
>
> The issue I am having is indeed due to GCC 9 trying to link against
Update on this issue:
>> Those are certainly exported from my GCC 9 libgomp.so.1.0.0 (at least on
>> Linux but I don't see how it could not be elsewhere).
I can confirm they are present.
The issue I am having is indeed due to GCC 9 trying to link against the wrong
library: it turns out that LLV
> On 6 May 2019, at 09:02, Jakub Jelinek wrote:
>
> On Mon, May 06, 2019 at 02:41:41PM +0200, FX wrote:
>> Hi gcc and gfortran developers,
>>
>> While testing GCC 9.1.0 before shipping it as part of Homebrew for macOS,
>> we’re seeing the following OpenMP-based failure when recompiling severa
On Mon, May 06, 2019 at 02:41:41PM +0200, FX wrote:
> Hi gcc and gfortran developers,
>
> While testing GCC 9.1.0 before shipping it as part of Homebrew for macOS,
> we’re seeing the following OpenMP-based failure when recompiling several
> software packages with GCC 9. It includes both C++ and
Hi gcc and gfortran developers,
While testing GCC 9.1.0 before shipping it as part of Homebrew for macOS, we’re
seeing the following OpenMP-based failure when recompiling several software
packages with GCC 9. It includes both C++ and Fortran codes, which were working
fine with the exact same se
