It would be useful for posts to be specific, and/or to include a link
to a detailed explanation. Such information might attract the interest
of others, and tend to encourage the discovery of multiple approaches
towards dealing with the underlying problems.
On 4/29/19 1210 UTC, Jonathan Wakely wrote:
On 29/04/19 07:52 -0400, Neal Gompa wrote:
On Mon, Apr 29, 2019 at 7:50 AM Dan Čermák
<dan.cermak@xxxxxxxxxxxxxxxxxxx> wrote:
Hi list,
I'm co-maintaining a C++ library that has been continuously updated in
Which library in which package?
CentOS 7 but a recent change made it incompatible with the default GCC
version available in el7. I.e. the next release (scheduled for the end
of 2019) will FTBFS in CentOS/RHEL 7.
What is the nature of the incompatibilities, and what are specific examples?
Would it be fine to require a gcc version from a SCL to build this
library? I'm afraid that due to the nature of C++'s non-standardized ABI
it would require all dependent packages to be rebuild with gcc from the
SCL too.
Software Collections GCC is configured to follow C++ ABI from system
GCC. This puts some limitations on the libstdc++ shipped by SCL GCC,
For example, or a link to an explanation?
but allows us to avoid that problem entirely.
If you're talking about the devtoolset version of GCC, that's not
strictly true. There are limitations on what is supported, so the
For example; or a link to an explanation?
problem isn't avoided entirely.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
