General question about MacPorts
I'm new to Mac OS and to MacPorts and I could use some guidance. 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). My questions are these: 1) Would this be considered a non-priority problem? Is it common for MacPorts to be unable to build vitally important tools like mod_python and subversion? Trust me, I'm not being snarky - I'd just like to know. 2) If that's in fact the case, what are the alternatives, if someone (like me) has been using MacPorts for other things? It appears (to this newbie) that you can't tell MacPorts, "hey, you don't need to build this - I built it myself," so it doesn't consider that it has a missing dependency. 3) Is MacPorts really just a convenience, and not something that one should depend on? Mr. Mod_Python (Graham Dumpleton) recommends not using it, for example. Again, I don't know whether that's true or not - I'm just interested in an objective answer. This is NOT a flame. I respect and admire the MacPorts project, and I'm aware that the folks who are working on it are doing so for the good of the community, for no personal gain. The thing is, I'm a database guy - I just need some very basic functionality. If someone could give their opinion on the questions above, I'd very much appreciate it! ///ark
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. 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].
My questions are these:
1) Would this be considered a non-priority problem?
no.
Is it common for MacPorts to be unable to build vitally important tools like mod_python and subversion?
'vitally important' is in the eye of the user ;-) Ports with a maintainer should all build (at least most of the time), but there are many ports without a current maintainer that may or may not have been tested recently.
2) If that's in fact the case, what are the alternatives, if someone (like me) has been using MacPorts for other things? It appears (to this newbie) that you can't tell MacPorts, "hey, you don't need to build this - I built it myself," so it doesn't consider that it has a missing dependency.
By design, you can't do this. The rational for why is on website. Modifying portfiles isn't hard, however, so it's often easier to fix the macports port (and submit a patch so others can benefit) than building and managing things by hand by yourself.
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 ;-)
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. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
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
Wilden Mark wrote:
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?
I think this happens for a lot of tickets. Really good would be someone volunteering as a ticket wrangler to assign all new tickets to the according maintainer. Could be done by anyone and it is definitely a way of contributing to MacPorts in order to "give somthing back". I don't know if assigning tickets can be done by the reporter only/committers/anyone. Rainer
On Thu, Mar 6, 2008 at 12:43 PM, Rainer Müller <raimue@macports.org> wrote:
Wilden Mark wrote:
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?
I don't know if assigning tickets can be done by the reporter only/committers/anyone.
When a ticket is opened, there is a CC field. By putting the maintainer of the port's email address (obtained with the port info command) into that box, then the maintainer will be informed of the ticket.
On Mar 6, 2008, at 13:11, Wilden Mark wrote:
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?
Regular users cannot assign tickets. I don't know why we don't allow this. Regular users can set the Cc field when tickets are created, but not after. I don't know why we restrict this either.
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.
Did you clean first? sudo port clean --work apr sudo port install apr
On Mar 6, 2008, at 10:52 PM, Ryan Schmidt wrote:
Did you clean first?
sudo port clean --work apr sudo port install apr
That worked! apr builds fine and so do the dependencies. However, mod_python itself does not build. http://trac.macosforge.org/projects/macports/ticket/14582 ///ark
participants (6)
-
Daniel J. Luke
-
Mark Wilden
-
Matrix Mole
-
Rainer Müller
-
Ryan Schmidt
-
Wilden Mark