I am using the original RTG 0.9 and the steps that I had to take were replacing 
the my_* mysql references with mysql_* references and also compensate for how 
GCC 10 handles duplicate declarations by default.

If anyone runs into trouble hit me up. ❤

-Drew


From: NANOG <nanog-bounces+drew.weaver=thenap....@nanog.org> On Behalf Of 
ja...@unlimitednet.us
Sent: Friday, July 12, 2024 9:29 PM
To: nanog@nanog.org
Subject: Re: Compiling RTG on EL9


Total blast from the past, Nick!

We're using rtg2 on our network and John, I appreciate you sending this link 
over with the update.  Just discussing internally that we need to get this 
server updated and not sure how that'll all go over.

Best wishes, Drew!

Best Regards,

Jason
On 7/12/24 8:35 PM, John Von Essen wrote:
Have you tried the rtg2 fork on github? 
https://github.com/synergycp/RTG2<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_synergycp_RTG2&d=DwMDaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=OPufM5oSy-PFpzfoijO_w76wskMALE1o4LtA3tMGmuw&m=FklUvxIwsQBlFOqvvYTFHQFb-o7etmiXGNQWrRbrCQJ74pfO1tTerpO3YlcB0UlD&s=AeplxoFr4xcAwhbF4veELekuOeMP8Po7Kv2eOS8-kjI&e=>

Its still pretty old, like 2009, but there was an update made just 2 years ago 
with MariaDB support. I stopped using rtg/rtg2 around 2015, but I was always a 
huge fan of it.

-John


On Jul 12, 2024, at 6:19 PM, Nick Hilliard 
<n...@foobar.org><mailto:n...@foobar.org> wrote:

Drew Weaver wrote on 12/07/2024 14:37:

I am just curious with the demise of EL7 if anyone else is working on trying to 
compile RTG for EL9.
If you don’t know what RTG is it’s just an old SNMP poller/graph plotter that 
some networks have found useful in the past.

Drew,

Whoa, that's some blast from the past. At the time of the latest release in 
2003, rtg was still duking it out with mrtg and cricket, which was used by the 
cool kids.  Still some good memories there.

Out of curiosity I had a look. It barfs at my_thread_init(). Probably this is 
related to mysql 8.0.2 which removed my_init() entirely as it's now called 
implicitly from regular mysql api calls, i.e. it can be deleted from the code. 
Here's the reference in the release notes:


https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-2.html#mysqld-8-0-2-compiling<https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.mysql.com_doc_relnotes_mysql_8.0_en_news-2D8-2D0-2D2.html-23mysqld-2D8-2D0-2D2-2Dcompiling&d=DwMDaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=OPufM5oSy-PFpzfoijO_w76wskMALE1o4LtA3tMGmuw&m=FklUvxIwsQBlFOqvvYTFHQFb-o7etmiXGNQWrRbrCQJ74pfO1tTerpO3YlcB0UlD&s=57bVJE_34K19gE7ivZWEweZKfrDyGj_B0tp5_uklECU&e=>

After 20 years, most of the code compiles even without warnings, which is 
pretty good. I'm sure it would be pretty straightforward for a C dev to get it 
to compile again. Whether you'd want this or not is a different issue :)

Nick

Reply via email to