On 2/20/2019 12:39 PM, J.R. wrote: >> unixpackages.com uses gcc-3.4.6 and has clamav built, along with 20 >> dependency packages. >> Pointing it out because 'severely ancient' compilers aren't necessarily the >> issue here. > I know on the x86_64 platform, I think it started with the 0.100 there > were some new flags that weren't implemented until like 4.4.x (or > maybe 4.8.x?) (at least when trying to compile on x86_64). > > I'm not sure what would happen if you remove the "unknown" flags from > the code and try to compile. That might be what unixpackages did? > > When you get those "error: unrecognized command line option" about the > only thing you can do is either modify the code to not use that option > (with unknown consequences), or check the gcc documentation online to > see when exactly that option got implemented in gcc and upgrade to > that (or higher).
I have a crazy old system running clamav and some legacy software. With 4.2.4, it won't work with base. Anyway, I'm using the opportunity to A) modernize and B) figure out how to compile GCC to support -Wno-logical-op-parentheses nor -Wno-dangling-else. See this FreeBSD bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233800 That patches the Makefile after it's built so it's pretty specific but it might give you some thoughts. There is also a small bug even with 100.2 for old systems where AI_ADDCONFIG isn't always available. clamd handles it but not freshclam. Simple fix there to add ifdef. 101 fixed that. Hope this helps! Regards, KAM _______________________________________________ clamav-users mailing list [email protected] http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
