7:56 a.m.
Hi,
I'm starting to hit more and more challenges in the OpenVPN 3 Linux
project with the RHEL-7 GCC version (which is 4.8.5), especially when it
comes to C++ building. I've tried to keep the project compatible with
RHEL-7 as the oldest supported distro, but it is getting harder and
harder. In addition to newer C++ standards making the development of
the project easier.
I do see that RHEL/CentOS 7 has the needed compiler versions in the
devtoolset. I also stumbled across this blog post:
<https://smoogespace.blogspot.com/2018/03/using-red-hat-developer-toolset-...
But ...
a) Is that blog post still relevant? I couldn't find anything in the
Fedora packaging guidelines giving any further advice.
b) By adding the devtoolset as a build dependency, is that enough?
Will the final .rpm need anything else installed to function? Like a
newer libstdc++?
c) Which other traps may I be facing using a devtoolset for EPEL-7 builds?
--
kin
d regards,
David Sommerseth
8:11 a.m.
I’d like to point to
https://src.fedoraproject.org/rpms/sleef/blob/epel7/f/sleef.spec as a
working example of a package that is built with a devtoolset in EPEL7.
While I maintain the sleef package, the EPEL7 backport was contributed
by Dave Love.
– Ben Beasley
On 11/25/21 08:56, David Sommerseth wrote:
>
> Hi,
>
> I'm starting to hit more and more challenges in the OpenVPN 3 Linux
> project with the RHEL-7 GCC version (which is 4.8.5), especially when it
> comes to C++ building. I've tried to keep the project compatible with
> RHEL-7 as the oldest supported distro, but it is getting harder and
> harder. In addition to newer C++ standards making the development of
> the project easier.
>
> I do see that RHEL/CentOS 7 has the needed compiler versions in the
> devtoolset. I also stumbled across this blog post:
>
<https://smoogespace.blogspot.com/2018/03/using-red-hat-developer-toolset-...
>
>
> But ...
>
> a) Is that blog post still relevant? I couldn't find anything in the
> Fedora packaging guidelines giving any further advice.
>
> b) By adding the devtoolset as a build dependency, is that enough?
> Will the final .rpm need anything else installed to function? Like a
> newer libstdc++?
>
> c) Which other traps may I be facing using a devtoolset for EPEL-7 builds?
>
>
>
> --
> kin
> d regards,
>
> David Sommerseth
>
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>
3:26 p.m.
On Thu, 25 Nov 2021 at 13:59, David Sommerseth wrote:
b) By adding the devtoolset as a build dependency, is that enough?
Will the final .rpm need anything else installed to function? Like a
newer libstdc++?
No, that's the point of devtoolset, as opposed to just building your
own new GCC. It doesn't have any dependencies on any shared libs
except the baseOS ones.
3:03 p.m.
On 25/11/2021 15:11, Ben Beasley wrote:
I’d like to point to
https://src.fedoraproject.org/rpms/sleef/blob/epel7/f/sleef.spec as a
working example of a package that is built with a devtoolset in EPEL7.
While I maintain the sleef package, the EPEL7 backport was contributed
by Dave Love.
– Ben Beasley
Thanks a lot! I adopted a few tricks from there, and seems to build
great. Will run more testing on the binaries, but hopefully nothing
unexpected will be found.
--
kind regards,
David Sommerseth
878
days inactive
884
days old
3 comments
3 participants
participants (3)
-
Ben Beasley -
David Sommerseth -
Jonathan Wakely