Re: /usr/lib/libomp.so that was added in 13-CURRENT causes port failures and might conflict with libomp.so provided by devel/openmp
On Sat, 18 May 2019 at 22:23, Yuri wrote: > > Why was /usr/lib/libomp.so added to the base? It was added to the base because it's a runtime library required to support a feature provided by the base system compiler. Do you have an example of a failing port? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
/usr/lib/libomp.so that was added in 13-CURRENT causes port failures and might conflict with libomp.so provided by devel/openmp
There are several port failures triggered by LIB_DEPENDS=libomp.so:devel/openmp. It finds /usr/lib/libomp.so and doesn't use devel/openmp, but then the build fails because it also needs some other libraries. Why was /usr/lib/libomp.so added to the base? Its addition potentially creates an error-prone situation with library compatibility issues between base and port libraries. Yuri ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
