When passing -fopenmp to a linker, the compiler links against internally with the openmp lib. Current libtool doesn't pass -(f)openmp to the linker resulting in borken linkage against libgomp.so or similar. Libtool should handle it similar to *threads flag.
Similar bug like #314095 happen.
ive gotten us out of the business of changing libtool. reports about libtool ignoring linker flags should go to firstname.lastname@example.org:
How is normally the contact to upstream? I didn't got any reply.
i saw your report to the list. that is the correct place. now to wait.
*** Bug 370117 has been marked as a duplicate of this bug. ***
The bug was fixed upstream and the patches got accepted. Just waiting for the official release now.
if the patches are not invasive, and you can post the commit ids, we can add a rev bump with them in it
I'd suggest adding them to elibtoolize as well though.
Its SHA 1b76054f4763a28ae1b01fbeee86ba0c524d1923 in upstream git with me as author.
*** Bug 375447 has been marked as a duplicate of this bug. ***
Can we get this bug fixed?
should be all set now in the tree; thanks for the report!
Commit message: Unify live/release ebuilds again. Add patch from upstream for openmp when linking