At the suggestion of my friend Chris, who posted a comment to my most recent MacPorts complaint, I contacted the maintainer of the post, Mark D. After a few e-mails between each other discussing the issue, Mark instructed me to add the following two lines to the end of /opt/local/var/macports/sources/
rsync.macports.org/release/ports/net/ntop/Portfile :
build.env-append MACOSX_DEPLOYMENT_TARGET="10.3"
destroot.env-append MACOSX_DEPLOYMENT_TARGET="10.3"
I added those lines and ntop finally compiled correctly… but it still didn’t work. Something about a GDBM error, which I didn’t record. So I removed MacPorts, reinstalled it, re-ran the ntop install, and it failed this time compiling Perl 5.8. Just to be super duper sure, I re-ran the install one more time and it finally installed a working ntop and all dependencies, as if Perl had never been a problem. What a load of crap that I have to go to such trouble.
I do want to thank ntop port maintainer Mark D. for his help. In his e-mail, Mark stated that he had not tested a compile of ntop on a PowerPC system because he has an Intel Mac, and that the necessary changes will be added to MacPorts and available in a few hours.
The error, for those who don’t know, and the Google page crawler, was
ld: flag: -undefined dynamic_lookup can't be used with MACOSX_DEPLOYMENT_TARGET environment variable set to: 10.1
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: internal link edit command failed
gnumake[2]: *** [libntop.la] Error 1
gnumake[1]: *** [all-recursive] Error 1
gnumake: *** [all] Error 2
The whole point of attempting to compile ntop to begin with is because I’d like to create a sort of network appliance that I can plug into customer networks, consisting of a Mac mini and ntop, that would monitor and record their traffic for a certain amount of time and assist with troubleshooting and other issues. I’ll likely keep plugging away with MacPorts and compile an mpkg with ntop and its dependencies as universal binaries. However, I can’t recommend using MacPorts to install software on any kind of production server - it’s just too flaky. What I would recommend is to have a second machine to create mkpg files containing dependencies, and compiling those as universal binaries for storage and installation elsewhere, as I stated that I will do.




My .Mac Web Gallery
Recent Comments