From yvoinov at gmail.com Sat Jan 4 15:56:44 2025 From: yvoinov at gmail.com (Yuri) Date: Sat, 4 Jan 2025 19:56:44 +0500 Subject: Time for some updates Message-ID: <42f13809-0e4e-4124-a307-d0be039cc2e0@gmail.com> Gentlemen, don't you think it's time for some updates? For example, Perl. It's too old, 14 years is a bit too much to run most of the CPAN modules. Or GCC. I'd like to see at least 6.5 in 2024. Or openvpn. The current version is outdated. Redis is generally archaic, given that 5.0.14 is built from sources on Solaris 10 without any problems. I understand that the problem of maintainers has not gone away and in general - if you want something, build it yourself. But let's at least refresh Perl and GCC a little, okay? They are hopelessly ancient. If I can build a compiler from sources myself, whichever I like, then I couldn't build Perl. Not with any attempt. Maybe there are newer versions posted somewhere and I just don't see them? For example, in unstable or testing? WBR, Yuri -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwalton at opencsw.org Sat Jan 4 17:33:43 2025 From: bwalton at opencsw.org (Ben Walton) Date: Sat, 4 Jan 2025 16:33:43 +0000 Subject: Time for some updates In-Reply-To: <42f13809-0e4e-4124-a307-d0be039cc2e0@gmail.com> References: <42f13809-0e4e-4124-a307-d0be039cc2e0@gmail.com> Message-ID: On Sat 4 Jan 2025, 14:58 Yuri via users, wrote: > Gentlemen, don't you think it's time for some updates? > > For example, Perl. It's too old, 14 years is a bit too much to run most > of the CPAN modules. Or GCC. I'd like to see at least 6.5 in 2024. Or > openvpn. The current version is outdated. > > Redis is generally archaic, given that 5.0.14 is built from sources on > Solaris 10 without any problems. > > I understand that the problem of maintainers has not gone away and in > general - if you want something, build it yourself. > > But let's at least refresh Perl and GCC a little, okay? They are > hopelessly ancient. If I can build a compiler from sources myself, > whichever I like, then I couldn't build Perl. Not with any attempt. > I think you already understand the problem here. The people that were investing their time in this aren't doing that much anymore because they've moved on. It's been a long time since I logged into any Solaris machine at this point and it's unlikely I will in the future. If I do, it's very unlikely to be building software on it. I think many other folks are in a similar position because they are scratching different itches in different technical contexts. Not everyone has moved on, but those still here seemingly don't have a need to update these packages. If you need these, I suggest you roll up your sleeves. Dago can still get you access to the build farm where you'd have a pretty straight forward path to building the updated packages you want. I know this doesn't actually help you, but at least it confirms your suspicion. Thanks -Ben > Maybe there are newer versions posted somewhere and I just don't see them? For > example, in unstable or testing? > > WBR, Yuri > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joncox at alum.mit.edu Sat Jan 4 19:29:47 2025 From: joncox at alum.mit.edu (Jonathan Cox) Date: Sat, 4 Jan 2025 18:29:47 +0000 Subject: Time for some updates In-Reply-To: References: <42f13809-0e4e-4124-a307-d0be039cc2e0@gmail.com> Message-ID: By the way, I invested quite a bit of time recently building new packages for Solaris 10 SPARC, including Python, SDL, Numpy, Geany and many others. I took detailed notes and had a fair amount of success, although I wasn't able to figure out how to build newer versions of GCC. This became a limiting factor because many open source projects, especially anything GNU, have moved to C++17 and even newer versions (for no apparent reason, as far as I can tell). I did inquire about releasing my builds in the OpenCSW repository, but I never got a response. I am interested in how to compile GCC 9 for Solaris 10, as well as generating these updated packages on OpenCSW. It's really a hobby, I'm not doing this because I'm constrained to 25 year old hardware... ________________________________ From: users on behalf of Ben Walton via users Sent: Saturday, January 4, 2025 9:33:43 AM To: Questions and discussions Cc: Ben Walton Subject: Re: Time for some updates On Sat 4 Jan 2025, 14:58 Yuri via users, > wrote: Gentlemen, don't you think it's time for some updates? For example, Perl. It's too old, 14 years is a bit too much to run most of the CPAN modules. Or GCC. I'd like to see at least 6.5 in 2024. Or openvpn. The current version is outdated. Redis is generally archaic, given that 5.0.14 is built from sources on Solaris 10 without any problems. I understand that the problem of maintainers has not gone away and in general - if you want something, build it yourself. But let's at least refresh Perl and GCC a little, okay? They are hopelessly ancient. If I can build a compiler from sources myself, whichever I like, then I couldn't build Perl. Not with any attempt. I think you already understand the problem here. The people that were investing their time in this aren't doing that much anymore because they've moved on. It's been a long time since I logged into any Solaris machine at this point and it's unlikely I will in the future. If I do, it's very unlikely to be building software on it. I think many other folks are in a similar position because they are scratching different itches in different technical contexts. Not everyone has moved on, but those still here seemingly don't have a need to update these packages. If you need these, I suggest you roll up your sleeves. Dago can still get you access to the build farm where you'd have a pretty straight forward path to building the updated packages you want. I know this doesn't actually help you, but at least it confirms your suspicion. Thanks -Ben Maybe there are newer versions posted somewhere and I just don't see them? For example, in unstable or testing? WBR, Yuri -------------- next part -------------- An HTML attachment was scrubbed... URL: From yvoinov at gmail.com Sat Jan 4 23:26:57 2025 From: yvoinov at gmail.com (Yuri) Date: Sun, 5 Jan 2025 03:26:57 +0500 Subject: Time for some updates In-Reply-To: References: <42f13809-0e4e-4124-a307-d0be039cc2e0@gmail.com> Message-ID: <9b5efa17-901f-4e8a-8689-72e6b4ee45b2@gmail.com> I built GCC 6.5 from source on Solaris 10 (latest release update 1/13) just a couple of months ago. It builds without any problems with the latest libraries from OpenCSW and on the first try. Version 6.5 already supports C++17 (partially) with an explicit specification of the standard (-std=c++17). I studied the issue and found out that it is possible to build GCC up to version 9.5 on Solaris 10 and the only reason why I did not do this was compatibility with already built packages on my setups. At the moment, native compatibility with C++14 is enough for me. Unfortunately, I was unable to compile Perl version 5.40 as easily and effortlessly due to a stupid error with the UTF8 locale. I have not yet found and written a comprehensive guide to this build. Unlike GCC.You could say that this is also a hobby for me (albeit a forced one). True, my hardware is somewhat younger, it is only fourteen years old ) By the way, I haven't looked into the issue in depth, but I heard that GCC has returned support for SPARC processors to compilers of versions later than 9. However, I'm not entirely sure about full compatibility with Solaris 10 libC, as Solaris 10 support was declared to be discontinued _after_ version 9. However, version 9.5 should be supported and I hope, if I have some free time, to run a test build on my build environment - just for show. AFAIK, GCC 9 is fully compatible with C11/C++17. 04.01.2025 23:29, Jonathan Cox via users ?????: > By the way, I invested quite a bit of time recently building new > packages for Solaris 10 SPARC, including Python, SDL, Numpy, Geany and > many others. I took detailed notes and had a fair amount of success, > although I wasn't able to figure out how to build newer versions of > GCC. This became a limiting factor because many open source projects, > especially anything GNU, have moved to C++17 and even newer versions > (for no apparent reason, as far as I can tell). > > I did inquire about releasing my builds in the OpenCSW repository, but > I never got a response. > > I am interested in how to compile GCC 9 for Solaris 10, as well as > generating these updated packages on OpenCSW. > > It's really a hobby, I'm not doing this because I'm constrained to 25 > year old hardware... > ------------------------------------------------------------------------ > *From:* users on > behalf of Ben Walton via users > *Sent:* Saturday, January 4, 2025 9:33:43 AM > *To:* Questions and discussions > *Cc:* Ben Walton > *Subject:* Re: Time for some updates > > > On Sat 4 Jan 2025, 14:58 Yuri via users, wrote: > > Gentlemen, don't you think it's time for some updates? > > For example, Perl. It's too old, 14 years is a bit too much to run > most of the CPAN modules. Or GCC. I'd like to see at least 6.5 in > 2024. Or openvpn. The current version is outdated. > > Redis is generally archaic, given that 5.0.14 is built from > sources on Solaris 10 without any problems. > > I understand that the problem of maintainers has not gone away and > in general - if you want something, build it yourself. > > But let's at least refresh Perl and GCC a little, okay? They are > hopelessly ancient. If I can build a compiler from sources myself, > whichever I like, then I couldn't build Perl. Not with any attempt. > > I think you already understand the problem here. The people that were > investing their time in this aren't doing that much anymore because > they've moved on. It's been a long time since I logged into any > Solaris machine at this point and it's unlikely I will in the future. > If I do, it's very unlikely to be building software on it. I think > many other folks are in a similar position because they are scratching > different itches in different technical contexts. Not everyone has > moved on, but those still here seemingly don't have a need to update > these packages. > > If you need these, I suggest you roll up your sleeves. Dago can still > get you access to the build farm where you'd have a pretty straight > forward path to building the updated packages you want. > > I know this doesn't actually help you, but at least it confirms your > suspicion. > > Thanks > -Ben > > Maybe there are newer versions posted somewhere and I just don't > see them? For example, in unstable or testing? > > WBR, Yuri > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joncox at alum.mit.edu Sun Jan 5 02:04:09 2025 From: joncox at alum.mit.edu (Jonathan Cox) Date: Sun, 5 Jan 2025 01:04:09 +0000 Subject: Time for some updates In-Reply-To: <9b5efa17-901f-4e8a-8689-72e6b4ee45b2@gmail.com> References: <42f13809-0e4e-4124-a307-d0be039cc2e0@gmail.com> <9b5efa17-901f-4e8a-8689-72e6b4ee45b2@gmail.com> Message-ID: Interesting to know what GCC has returned support for SPARC. The LEON series of SPARC processors are still used in embedded systems today, especially for space applications. ________________________________ From: users on behalf of Yuri via users Sent: Saturday, January 4, 2025 3:26:57 PM To: users at lists.opencsw.org Cc: Yuri Subject: Re: Time for some updates I built GCC 6.5 from source on Solaris 10 (latest release update 1/13) just a couple of months ago. It builds without any problems with the latest libraries from OpenCSW and on the first try. Version 6.5 already supports C++17 (partially) with an explicit specification of the standard (-std=c++17). I studied the issue and found out that it is possible to build GCC up to version 9.5 on Solaris 10 and the only reason why I did not do this was compatibility with already built packages on my setups. At the moment, native compatibility with C++14 is enough for me. Unfortunately, I was unable to compile Perl version 5.40 as easily and effortlessly due to a stupid error with the UTF8 locale. I have not yet found and written a comprehensive guide to this build. Unlike GCC. You could say that this is also a hobby for me (albeit a forced one). True, my hardware is somewhat younger, it is only fourteen years old ) By the way, I haven't looked into the issue in depth, but I heard that GCC has returned support for SPARC processors to compilers of versions later than 9. However, I'm not entirely sure about full compatibility with Solaris 10 libC, as Solaris 10 support was declared to be discontinued _after_ version 9. However, version 9.5 should be supported and I hope, if I have some free time, to run a test build on my build environment - just for show. AFAIK, GCC 9 is fully compatible with C11/C++17. 04.01.2025 23:29, Jonathan Cox via users ?????: By the way, I invested quite a bit of time recently building new packages for Solaris 10 SPARC, including Python, SDL, Numpy, Geany and many others. I took detailed notes and had a fair amount of success, although I wasn't able to figure out how to build newer versions of GCC. This became a limiting factor because many open source projects, especially anything GNU, have moved to C++17 and even newer versions (for no apparent reason, as far as I can tell). I did inquire about releasing my builds in the OpenCSW repository, but I never got a response. I am interested in how to compile GCC 9 for Solaris 10, as well as generating these updated packages on OpenCSW. It's really a hobby, I'm not doing this because I'm constrained to 25 year old hardware... ________________________________ From: users on behalf of Ben Walton via users Sent: Saturday, January 4, 2025 9:33:43 AM To: Questions and discussions Cc: Ben Walton Subject: Re: Time for some updates On Sat 4 Jan 2025, 14:58 Yuri via users, > wrote: Gentlemen, don't you think it's time for some updates? For example, Perl. It's too old, 14 years is a bit too much to run most of the CPAN modules. Or GCC. I'd like to see at least 6.5 in 2024. Or openvpn. The current version is outdated. Redis is generally archaic, given that 5.0.14 is built from sources on Solaris 10 without any problems. I understand that the problem of maintainers has not gone away and in general - if you want something, build it yourself. But let's at least refresh Perl and GCC a little, okay? They are hopelessly ancient. If I can build a compiler from sources myself, whichever I like, then I couldn't build Perl. Not with any attempt. I think you already understand the problem here. The people that were investing their time in this aren't doing that much anymore because they've moved on. It's been a long time since I logged into any Solaris machine at this point and it's unlikely I will in the future. If I do, it's very unlikely to be building software on it. I think many other folks are in a similar position because they are scratching different itches in different technical contexts. Not everyone has moved on, but those still here seemingly don't have a need to update these packages. If you need these, I suggest you roll up your sleeves. Dago can still get you access to the build farm where you'd have a pretty straight forward path to building the updated packages you want. I know this doesn't actually help you, but at least it confirms your suspicion. Thanks -Ben Maybe there are newer versions posted somewhere and I just don't see them? For example, in unstable or testing? WBR, Yuri -------------- next part -------------- An HTML attachment was scrubbed... URL: From yvoinov at gmail.com Sun Jan 5 08:44:13 2025 From: yvoinov at gmail.com (Yuri) Date: Sun, 5 Jan 2025 12:44:13 +0500 Subject: Time for some updates In-Reply-To: References: <42f13809-0e4e-4124-a307-d0be039cc2e0@gmail.com> <9b5efa17-901f-4e8a-8689-72e6b4ee45b2@gmail.com> Message-ID: <0cfc4b37-9c7c-42c1-9fb7-91ba8809a408@gmail.com> And what's more, Openindiana has released a beta version for SPAR? CPUs. ) 05.01.2025 06:04, Jonathan Cox ?????: > Interesting to know what GCC has returned support for SPARC. The LEON > series of SPARC processors are still used in embedded systems today, > especially for space applications. > ------------------------------------------------------------------------ > *From:* users on > behalf of Yuri via users > *Sent:* Saturday, January 4, 2025 3:26:57 PM > *To:* users at lists.opencsw.org > *Cc:* Yuri > *Subject:* Re: Time for some updates > > I built GCC 6.5 from source on Solaris 10 (latest release update 1/13) > just a couple of months ago. It builds without any problems with the > latest libraries from OpenCSW and on the first try. Version 6.5 > already supports C++17 (partially) with an explicit specification of > the standard (-std=c++17). I studied the issue and found out that it > is possible to build GCC up to version 9.5 on Solaris 10 and the only > reason why I did not do this was compatibility with already built > packages on my setups. At the moment, native compatibility with C++14 > is enough for me. > > Unfortunately, I was unable to compile Perl version 5.40 as easily and > effortlessly due to a stupid error with the UTF8 locale. I have not > yet found and written a comprehensive guide to this build. Unlike > GCC.You could say that this is also a hobby for me (albeit a forced > one). True, my hardware is somewhat younger, it is only fourteen years > old ) > > By the way, I haven't looked into the issue in depth, but I heard that > GCC has returned support for SPARC processors to compilers of versions > later than 9. However, I'm not entirely sure about full compatibility > with Solaris 10 libC, as Solaris 10 support was declared to be > discontinued _after_ version 9. However, version 9.5 should be > supported and I hope, if I have some free time, to run a test build on > my build environment - just for show. > > AFAIK, GCC 9 is fully compatible with C11/C++17. > > 04.01.2025 23:29, Jonathan Cox via users ?????: >> By the way, I invested quite a bit of time recently building new >> packages for Solaris 10 SPARC, including Python, SDL, Numpy, Geany >> and many others. I took detailed notes and had a fair amount of >> success, although I wasn't able to figure out how to build newer >> versions of GCC. This became a limiting factor because many open >> source projects, especially anything GNU, have moved to C++17 and >> even newer versions (for no apparent reason, as far as I can tell). >> >> I did inquire about releasing my builds in the OpenCSW repository, >> but I never got a response. >> >> I am interested in how to compile GCC 9 for Solaris 10, as well as >> generating these updated packages on OpenCSW. >> >> It's really a hobby, I'm not doing this because I'm constrained to 25 >> year old hardware... >> ------------------------------------------------------------------------ >> *From:* users >> on >> behalf of Ben Walton via users >> >> *Sent:* Saturday, January 4, 2025 9:33:43 AM >> *To:* Questions and discussions >> >> *Cc:* Ben Walton >> *Subject:* Re: Time for some updates >> >> >> On Sat 4 Jan 2025, 14:58 Yuri via users, > > wrote: >> >> Gentlemen, don't you think it's time for some updates? >> >> For example, Perl. It's too old, 14 years is a bit too much to >> run most of the CPAN modules. Or GCC. I'd like to see at least >> 6.5 in 2024. Or openvpn. The current version is outdated. >> >> Redis is generally archaic, given that 5.0.14 is built from >> sources on Solaris 10 without any problems. >> >> I understand that the problem of maintainers has not gone away >> and in general - if you want something, build it yourself. >> >> But let's at least refresh Perl and GCC a little, okay? They are >> hopelessly ancient. If I can build a compiler from sources >> myself, whichever I like, then I couldn't build Perl. Not with >> any attempt. >> >> I think you already understand the problem here. The people that were >> investing their time in this aren't doing that much anymore because >> they've moved on. It's been a long time since I logged into any >> Solaris machine at this point and it's unlikely I will in the future. >> If I do, it's very unlikely to be building software on it. I think >> many other folks are in a similar position because they are >> scratching different itches in different technical contexts. Not >> everyone has moved on, but those still here seemingly don't have a >> need to update these packages. >> >> If you need these, I suggest you roll up your sleeves. Dago can still >> get you access to the build farm where you'd have a pretty straight >> forward path to building the updated packages you want. >> >> I know this doesn't actually help you, but at least it confirms your >> suspicion. >> >> Thanks >> -Ben >> >> Maybe there are newer versions posted somewhere and I just don't >> see them? For example, in unstable or testing? >> >> WBR, Yuri >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From ihsan at opencsw.org Sun Jan 5 11:04:39 2025 From: ihsan at opencsw.org (Ihsan Dogan) Date: Sun, 5 Jan 2025 11:04:39 +0100 Subject: Time for some updates In-Reply-To: References: <42f13809-0e4e-4124-a307-d0be039cc2e0@gmail.com> Message-ID: <73E9E842-59E9-4BBC-A781-AF6BDAA6BB13@opencsw.org> Hello > Am 04.01.2025 um 17:33 schrieb Ben Walton via users : > > I think you already understand the problem here. The people that were investing their time in this aren't doing that much anymore because they've moved on. It's been a long time since I logged into any Solaris machine at this point and it's unlikely I will in the future. If I do, it's very unlikely to be building software on it. I think many other folks are in a similar position because they are scratching different itches in different technical contexts. Not everyone has moved on, but those still here seemingly don't have a need to update these packages. That is the case for many here. Professionally, I haven't had anything to do with Solaris for 8 years and like others, I only update my packages for fun and when I have the time. Please understand that this is all very time consuming and we all do not work anymore with Solaris professionally. > If you need these, I suggest you roll up your sleeves. Dago can still get you access to the build farm where you'd have a pretty straight forward path to building the updated packages you want. Fully agree with Ben. We always appreciate support to keep the project alive. Regards Ihsan -------------- next part -------------- An HTML attachment was scrubbed... URL: