with flags: CCLD lemon /usr/lib/libgcrypt.so: undefined reference to `GOMP_parallel_end' /usr/lib/libgcrypt.so: undefined reference to `omp_get_num_threads' /usr/lib/libgcrypt.so: undefined reference to `GOMP_parallel_start' /usr/lib/libgcrypt.so: undefined reference to `omp_get_thread_num' without: CCLD lemon Success! Reproducible: Always
And no, I am not using -fopenmp anywhere.
I'm afraid you'll have to stop using the flag then because that flag implies -fopenmp..
@flameeyes: Before I go closing this, which one of the flags in question is implying -fopenmp? I know that parallelize-tree-loops requires -pthread, but I haven't been able to dig anything up regarding those flags and openmp. Thanks!
-ftree-parallelize-loop is the one that implies OpenMP.
Given that, I think this is safe to close. If you want to try to use those flags, try making sure gcc has USE="openmp". Beyond that, this really isn't a bug for this packages.
This is mostly a bug in libtool, as it doesn't passes (all) the cflags used for build when linking, but some cflags also change the behaviour of the gcc link editor frontend :/