View Full Version : Building 1.1 beta2 on Fedore Core 4 64 Bit
0x00coffee
06-11-2005, 05:05
I had initial problem building 64 bit version. But after changing /usr/lib and /usr/lib/mysql to /usr/lib64 and /usr/lib64/mysql and adding CFLAGS="-g -O2 -m64" Did the trick. I was able to build 64 bit version on FC4. It would be nice if the configure script would support this out of the box when you pass -m64 as part of CFLAGS or some auto detection.
Also to build 32 bit version I have to ls -n /usr/lib/libnetsnmp.so /usr/lib/libnetsnmp.so.5. This fixed the linking.
Still working on making static linking
I had initial problem building 64 bit version. But after changing /usr/lib and /usr/lib/mysql to /usr/lib64 and /usr/lib64/mysql and adding CFLAGS="-g -O2 -m64" Did the trick. I was able to build 64 bit version on FC4. It would be nice if the configure script would support this out of the box when you pass -m64 as part of CFLAGS or some auto detection.
Also to build 32 bit version I have to ls -n /usr/lib/libnetsnmp.so /usr/lib/libnetsnmp.so.5. This fixed the linking.
Still working on making static linking
I've noticed that compiles are flaky on different platforms. Probably because it's untested. Someone really needs to go in and redo the configure scripts. Building agents on FreeBSD was a hassle as well. The make process is broken, halfway through you have to move files around manually then let it continue the build. Personally I enjoy the challenge, but someone not used compiling software would probably be lost.
-Alex
0x00coffee
07-11-2005, 17:33
Alex,
What is the time frame for next update/release?
Robert
0x00coffee
07-11-2005, 17:38
Also, not sure Alex if you noticed this but http://www.zabbix.com/manual/v1.1/index.php is invalid
Robert
The make process is broken, halfway through you have to move files around manually then let it continue the build.
ZABBIX agent build is automatically tested on a dozen of platforms and it works without any problems (Fedora 3/64bit is included). If a distribution is using non-standard locations for libraries like /usr/lib64 (as obviously FC4 does), what can ZABBIX configuration scripts do about this?
ZABBIX agent build is automatically tested on a dozen of platforms and it works without any problems (Fedora 3/64bit is included). If a distribution is using non-standard locations for libraries like /usr/lib64 (as obviously FC4 does), what can ZABBIX configuration scripts do about this?
Every distrubution puts files in a different location, so what makes FC4 different from any other distro? Just FYI, I'm no the one who originally posted the question about FC4_64bit. I've never tried it under FC4 64bit. My comments were regarding the regular FC4 distro where the build breaks as well.
Perhaps a second effort should be started to rewrite the configuration rules. I know you're probably tied up with more important work in developing the actual code, and I personally can deal with manual compiles, but other people are not as fortunate. Once I have some more time I will put some effort into helping out in this area.
Thanks,
-Alex
Someone on this post solved the 64 bit problem by below solution.
I had initial problem building 64 bit version. But after changing /usr/lib and /usr/lib/mysql to /usr/lib64 and /usr/lib64/mysql and adding CFLAGS="-g -O2 -m64" Did the trick. I was able to build 64 bit version on FC4. It would be nice if the configure script would support this out of the box when you pass -m64 as part of CFLAGS or some auto detection.
can someone elaborate how to do this? I mean step by step ?
thanks,
vaneet
We have significantly improved configuration scripts to detect various locations of header and library files. This is for 1.3.x only. It is too risky release it for 1.1.x.