On Mar 5, 2008, at 10:53 AM, Daniel J. Luke wrote:
On Mar 5, 2008, at 12:27 PM, Wilden Mark wrote:
A couple of days ago, I posted about the inability to build mod_python. There appears to be a problem building apr-1.2.12, which mod_python and others (like Subversion) depend on. A ticket was added for this (#14470).
Sorry, I didn't notice this ticket (as it wasn't assigned or CC'd to me), and I'm the maintainer of the apr port.
Ah, cool. How does a ticket get assigned? Was there something I could have done?
It looks like your issue is a duplicate of #14203 (it's a conflict with ossp-uuid) and you should be able to get things working by temporarily deactivating ossp-uuid, rebuilding apr, and then activating ossp-uuid after you get it installed. [There's more detailed information in the ticket].
I had in fact installed postgresql83 by mistake, and that seems to relate. However, after uninstalling ossp-uuid and building apr, I received the error: misc/unix/rand.c:39:18: error: uuid.h: No such file or directory. The places on my system where that file exists are /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/ Kernel.framework/Versions/A/Headers/uuid/uuid.h /Developer/SDKs/MacOSX10.4u.sdk/usr/include/uuid/uuid.h /Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/ Kernel.framework/Versions/A/Headers/uuid/uuid.h /Developer/SDKs/MacOSX10.5.sdk/usr/include/uuid/uuid.h /System/Library/Frameworks/Kernel.framework/Versions/A/Headers/uuid/ uuid.h /usr/include/uuid/uuid.h and the output from sudo port install apr is Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_devel_apr/work/apr-1.2.12" && make all " returned error 2 Command output: /bin/sh /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_devel_apr/work/apr-1.2.12/libtool --silent --mode=compile /usr/bin/gcc-4.0 -O2 -DHAVE_CONFIG_H -DDARWIN - DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp -I/opt/local/include - I./include -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_devel_apr/work/apr-1.2.12/include/arch/ unix -I./include/arch/unix -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_devel_apr/work/apr-1.2.12/include -o misc/ unix/rand.lo -c misc/unix/rand.c && touch misc/unix/rand.lo misc/unix/rand.c:39:18: error: uuid.h: No such file or directory make[1]: *** [misc/unix/rand.lo] Error 1 make: *** [all-recursive] Error 1 Error: Status 1 encountered during processing.
3) Is MacPorts really just a convenience, and not something that one should depend on?
That's something you have to determine for yourself. Macports is a volunteer project. I'm sure if you wanted to pay someone to make sure everything that's important to you kept working, you could ;-)
I don't think I -can- determine this for myself. I don't even know how I would do such a thing without much, much more experience with MacPorts. That's why I was asking the community at large.
Mr. Mod_Python (Graham Dumpleton) recommends not using it, for example.
That's interesting, and I would be curious as to why that would be the case.
It's annoying, I agree. Thanks very much for your comments, not only on how to solve my problem, but also on MacPorts in general! ///ark