Re: Updating database of binaries step very slow under Yosemite?
In at least some cases, the Yosemite installer wraps HFS+ volumes up into a Core Storage Logical Volume Group, and they become Core Storage Logical Volumes. http://arstechnica.com/apple/2014/10/os-x-10-10/2/#diskutil-list that's the part I was wondering about ... and in what unexpected ways it could mess up one's partition table ... R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Updating database of binaries step very slow under Yosemite?
Hey, - On 23 Oct, 2014, at 08:55, René J.V. Bertin rjvber...@gmail.com wrote: In at least some cases, the Yosemite installer wraps HFS+ volumes up into a Core Storage Logical Volume Group, and they become Core Storage Logical Volumes. http://arstechnica.com/apple/2014/10/os-x-10-10/2/#diskutil-list that's the part I was wondering about ... and in what unexpected ways it could mess up one's partition table ... CoreStorage is unlikely what caused the performance issues, because I've been running a fully encrypted FileVault2-CoreStorage setup ever since it was available and have seen good performance meanwhile. I still think the issue is somewhere in SQLite and how we use it. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
error install
Hello, I can’t install blackbox, I send you the main.log. Thank you in advance main.log Description: Binary data ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: error install
On Oct 23, 2014, at 2:40 AM, Nicolas Kozic wrote: I can’t install blackbox, I send you the main.log. Please sudo port clean blackbox and then try again. If the problem persists, please file a ticket in our issue tracker. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Installing Metis V4
I have a need to install Metis V4 for a project that I am working on right now. I notice that the Metis in Macports is V5 and unfortunately the code I have won't compile under V5. Is there an easy way to install V4 using the Macports infrastructure? - - - - - - - - - - - - - - - - - L.Bryce Whitson Jr. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Installing Metis V4
It seems parmetis is still version 4.0.3. If you need regular metis, you can find the newest version 4.0.3: http://trac.macports.org/browser/trunk/dports/math/metis/Portfile?rev=84527 You'll want to setup a local ports tree so that this file is deemed canonical over MacPorts': https://guide.macports.org/#development.local-repositories http://trac.macports.org/wiki/howto/SyncingWithSVN On Oct 23, 2014, at 10:01 AM, L.Bryce Whitson Jr. wrote: I have a need to install Metis V4 for a project that I am working on right now. I notice that the Metis in Macports is V5 and unfortunately the code I have won't compile under V5. Is there an easy way to install V4 using the Macports infrastructure? - - - - - - - - - - - - - - - - - L.Bryce Whitson Jr. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Strange problems with launchd and macports toolchains/libraries
Hello,
I am working on setting up a build-bot on OS X 10.8.5, but I'm having some
issues when I use my scripts with launchd.
Our software downloads configures, and builds a few other packages using
cmake. One of these external projects is GTS, which, uses configure (as
opposed to cmake) to configure and build using make and gcc.
So to use the mp libraries and compilers we configure it specifying the
compiler that used by cmake, i.e. something like:
CC=${CMAKE_C_COMPILER} CPP=${CMAKE_CXX_COMPILER}
${${proj}_OUTPUT_DIR}/configure --prefix=${GTS_INSTALL_DIR}
These values are set to a mp compiler.
This works perfectly on linux (automatic and cron) and on mac when I
initiate the build manually, but when I added it to a launchd (or cronjob).
I believe that the issue lies with the toolchain, when I run the script,
the tool chain used is the one in /opt/local/, however when I run the
script, it uses XCode's toolchain for some reason... It also not finding
any of the mp libraries (i.e. glib).
Any Idea why this might be? I've tried setting the path in the script, but
this does not help. And Im out of ideas as to the cause.
I know this isn't specifically a macports issue, but since I am trying to
use the macports toolchain, I thought someone else might have run into
it
Thank you!!
-Jameson
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Strange problems with launchd and macports toolchains/libraries
On Thu, Oct 23, 2014 at 11:17 AM, Jameson Merkow jmer...@gmail.com wrote: This works perfectly on linux (automatic and cron) and on mac when I initiate the build manually, but when I added it to a launchd (or cronjob). I believe that the issue lies with the toolchain, when I run the script, the tool chain used is the one in /opt/local/, however when I run the script, it uses XCode's toolchain for some reason... It also not finding any of the mp libraries (i.e. glib). Any Idea why this might be? I've tried setting the path in the script, but this does not help. And Im out of ideas as to the cause. The first thing to look at in such cases is to compare the output of `env` from a shell and in the cron job. $PATH is far from the only thing that can affect builds. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Installing Metis V4
Jeremy Lavergne writes: It seems parmetis is still version 4.0.3. Unfortunately, parmetis is not the same as metis. George decided to keep two separate projects. I have done the leg work to make parmetis depend on metis. On Oct 23, 2014, at 10:01 AM, L.Bryce Whitson Jr. wrote: I have a need to install Metis V4 for a project that I am working on right now. I notice that the Metis in Macports is V5 and unfortunately the code I have won't compile under V5. Is there an easy way to install V4 using the Macports infrastructure? The upgrade isn't that bad, actually. Which project is this? If it's a C project, you can look at the SuiteSparse port to see how I patched it to work with metis 5.x. If it's fortran, take a look at mumps. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Updating database of binaries step very slow under Yosemite?
On Oct 23, 2014, at 3:18 AM, Clemens Lang c...@macports.org wrote: Hey, - On 23 Oct, 2014, at 08:55, René J.V. Bertin rjvber...@gmail.com wrote: In at least some cases, the Yosemite installer wraps HFS+ volumes up into a Core Storage Logical Volume Group, and they become Core Storage Logical Volumes. http://arstechnica.com/apple/2014/10/os-x-10-10/2/#diskutil-list that's the part I was wondering about ... and in what unexpected ways it could mess up one's partition table ... CoreStorage is unlikely what caused the performance issues, because I've been running a fully encrypted FileVault2-CoreStorage setup ever since it was available and have seen good performance meanwhile. I still think the issue is somewhere in SQLite and how we use it. I agree; I just mentioned boot volume conversion as something new in Yosemite. For what it's worth, I have not noticed degraded I/O performance anywhere else. For instance, builds take about the same amount of time. vq Sent from my iPhone ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
LLVM 3.3 failed
I am trying to update ports after upgrading to 10.10 and XCODE 6.1. LLVM 3.3 is failing. According to the log: import sys; print sys.version.split has invalid syntax at sys. configure: error: found python (opt/loca/bin/python); required = 2.5 Does anyone have any ideas? thanks ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Installation log files?
In going through the Yosemite upgrade, I have come up with the following question. I don't find any answer in the guide (guide.macports.org) -- the closest I have found is a reference under 3.1.11 port install to the main.log Since this was a successful installation, it contains 3 lines. What I'm looking for is the notes (or explanations) which were in the install stream. Are they recorded anywhere? Or do you have to remember to copy them down on the fly? Put another way, this seems to be a feature lacking in the basic MacPorts documentation structure. Or well hidden as the case may be. :) === Now I realize this issue may only be relevant for certain ports. In my case, I'm playing with Apache2 -- and while apachectl does something, it is not clear that it does the right thing -- especially since I think I remember that the MacPorts version of Apache2 does something different. What I'm looking for is that block of text from the installation log which tells me how to start and stop Apache2. T.T.F.N. William H. Magill # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.10 # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.10 OSX Server (now dead) mag...@icloud.com mag...@mac.com whmag...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Installation log files?
On Thu, Oct 23, 2014 at 7:06 PM, William H. Magill mag...@mac.com wrote: What I'm looking for is the notes (or explanations) which were in the install stream. Are they recorded anywhere? Or do you have to remember to copy them down on the fly? port notes installed -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Installation log files?
On Oct 23, 2014, at 7:09 PM, Brandon Allbery allber...@gmail.com wrote: On Thu, Oct 23, 2014 at 7:06 PM, William H. Magill mag...@mac.com wrote: What I'm looking for is the notes (or explanations) which were in the install stream. Are they recorded anywhere? Or do you have to remember to copy them down on the fly? port notes installed Aha useful. Except that Apache2 yields: apache2 has no notes. T.T.F.N. William H. Magill mag...@icloud.com mag...@mac.com whmag...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: LLVM 3.3 failed
On Oct 23, 2014, at 17:50, Robert Broome wrote: I am trying to update ports after upgrading to 10.10 and XCODE 6.1. LLVM 3.3 is failing. According to the log: import sys; print sys.version.split has invalid syntax at sys. configure: error: found python (opt/loca/bin/python); required = 2.5 Does anyone have any ideas? And what version of python is /opt/local/bin/python? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
controlling Macports version of Apache2
On Oct 23, 2014, at 8:34 PM, William H. Magill mag...@mac.com wrote: On Oct 23, 2014, at 7:09 PM, Brandon Allbery allber...@gmail.com wrote: On Thu, Oct 23, 2014 at 7:06 PM, William H. Magill mag...@mac.com wrote: What I'm looking for is the notes (or explanations) which were in the install stream. Are they recorded anywhere? Or do you have to remember to copy them down on the fly? port notes installed Aha useful. Except that Apache2 yields: apache2 has no notes. I am fairly certain that I recalled instructions in the re-installation process (post Yosemite) of Apache2 on how to start and stop Apache2. Clearly Apachectl does not work. (/usr/sbin/apachectl) It expects to run /usr/sbin/httpd as its binary The plist file it uses is similarly not involved. /System/Library/LaunchDaemons/org.apache.httpd.plist What I am unable to find is those instructions. echo $PATH /opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Server.app/Contents/ServerRoot/usr/bin:/Applications/Server.app/Contents/ServerRoot/usr/sbin:/Users/magill/bin:/usr/bin/X11:/usr/local/bin:/usr/local/sbin:/usr/local1/bin:/usr/X11R6/bin:/usr/bin/X11:/etc:/usr/etc:/usr/local/etc:/usr/local1/etc I can eventually puzzle out the answer, but I can't find it documented anywhere. T.T.F.N. William H. Magill # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.10 # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.10 OSX Server (now dead) mag...@icloud.com mag...@mac.com whmag...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2
On Thu, Oct 23, 2014 at 9:23 PM, William H. Magill mag...@mac.com wrote: On Oct 23, 2014, at 8:34 PM, William H. Magill mag...@mac.com wrote: On Oct 23, 2014, at 7:09 PM, Brandon Allbery allber...@gmail.com wrote: port notes installed Aha useful. Except that Apache2 yields: apache2 has no notes. I am fairly certain that I recalled instructions in the re-installation process (post Yosemite) of Apache2 on how to start and stop Apache2. Sadly, there are still ports which use ui_msg in their postinstall sections, which can only be found after the fact by manually inspecting their Portfiles. (I ran into another one, xinit, earlier today.) Clearly Apachectl does not work. (/usr/sbin/apachectl) It expects to run /usr/sbin/httpd as its binary I would have expected the apache2 ports to install /opt/local/sbin/apachectl, possibly with a version appended. But looking at the apache2 Portfile, it appears to actually be /opt/local/apache2/bin/apachectl. (This path should have been visible in the plist you found.) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
controlling Macports version of Apache2 -- part 2
On Oct 23, 2014, at 9:23 PM, William H. Magill mag...@mac.com wrote: On Oct 23, 2014, at 8:34 PM, William H. Magill mag...@mac.com wrote: On Oct 23, 2014, at 7:09 PM, Brandon Allbery allber...@gmail.com wrote: On Thu, Oct 23, 2014 at 7:06 PM, William H. Magill mag...@mac.com wrote: What I'm looking for is the notes (or explanations) which were in the install stream. Are they recorded anywhere? Or do you have to remember to copy them down on the fly? port notes installed Aha useful. Except that Apache2 yields: apache2 has no notes. I am fairly certain that I recalled instructions in the re-installation process (post Yosemite) of Apache2 on how to start and stop Apache2. Clearly Apachectl does not work. (/usr/sbin/apachectl) It expects to run /usr/sbin/httpd as its binary The plist file it uses is similarly not involved. /System/Library/LaunchDaemons/org.apache.httpd.plist What I am unable to find is those instructions. echo $PATH /opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Server.app/Contents/ServerRoot/usr/bin:/Applications/Server.app/Contents/ServerRoot/usr/sbin:/Users/magill/bin:/usr/bin/X11:/usr/local/bin:/usr/local/sbin:/usr/local1/bin:/usr/X11R6/bin:/usr/bin/X11:/etc:/usr/etc:/usr/local/etc:/usr/local1/etc I can eventually puzzle out the answer, but I can't find it documented anywhere. I note that /opt/local/apache2/bin/apachectl contains the following reference: # a command that outputs a formatted text version of the HTML at the # url given on the command line. Designed for lynx, however other # programs may work. LYNX=lynx -dump Obviously an artifact from long, long ago in the Unix world. What is the equivalent today? MacPorts does not contain a Lynx port which the search command can find. T.T.F.N. William H. Magill # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.10 # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.10 OSX Server (now dead) mag...@icloud.com mag...@mac.com whmag...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2 -- part 2
On Thu, Oct 23, 2014 at 9:37 PM, William H. Magill mag...@mac.com wrote: What is the equivalent today? MacPorts does not contain a Lynx port which the search command can find. links or elinks, probably. Ports exist for both. There's also w3m and netrik. (port search browser also tells me there is indeed a lynx port. What exactly did you use with port search?) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2 -- part 2
On Oct 23, 2014, at 9:42 PM, Brandon Allbery allber...@gmail.com wrote: On Thu, Oct 23, 2014 at 9:37 PM, William H. Magill mag...@mac.com wrote: What is the equivalent today? MacPorts does not contain a Lynx port which the search command can find. links or elinks, probably. Ports exist for both. There's also w3m and netrik. (port search browser also tells me there is indeed a lynx port. What exactly did you use with port search?) Using the search function on the web page: https://www.macports.org/ports.php?by=categorysubstr=Lynx And https://www.macports.org/ports.php?by=categorysubstr=lynx T.T.F.N. William H. Magill mag...@icloud.com mag...@mac.com whmag...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2 -- part 2
On Oct 23, 2014, at 8:42 PM, Brandon Allbery allber...@gmail.com wrote: On Thu, Oct 23, 2014 at 9:37 PM, William H. Magill mag...@mac.com wrote: What is the equivalent today? MacPorts does not contain a Lynx port which the search command can find. links or elinks, probably. Ports exist for both. There's also w3m and netrik. (port search browser also tells me there is indeed a lynx port. What exactly did you use with port search?) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net pluto:~ marius$ port list lynx lynx @2.8.8rel.2 www/lynx Which is more up to date than elinks (in terms of release date). I know nothing about links… Marius -- Marius Schamschula ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2
On Oct 23, 2014, at 9:33 PM, Brandon Allbery allber...@gmail.com wrote: On Thu, Oct 23, 2014 at 9:23 PM, William H. Magill mag...@mac.com wrote: On Oct 23, 2014, at 8:34 PM, William H. Magill mag...@mac.com wrote: On Oct 23, 2014, at 7:09 PM, Brandon Allbery allber...@gmail.com wrote: port notes installed Aha useful. Except that Apache2 yields: apache2 has no notes. I am fairly certain that I recalled instructions in the re-installation process (post Yosemite) of Apache2 on how to start and stop Apache2. Sadly, there are still ports which use ui_msg in their postinstall sections, which can only be found after the fact by manually inspecting their Portfiles. (I ran into another one, xinit, earlier today.) Clearly Apachectl does not work. (/usr/sbin/apachectl) It expects to run /usr/sbin/httpd as its binary I would have expected the apache2 ports to install /opt/local/sbin/apachectl, possibly with a version appended. But looking at the apache2 Portfile, it appears to actually be /opt/local/apache2/bin/apachectl. (This path should have been visible in the plist you found.) Finding /opt/local/apache2/bin/apachectl was obvious. But not from any pllist file. Looking at that file and comparing it with Apple's they are significantly different. I.e. /opt/local/apache2/bin/apachectl contains no reference to a plist file, OR the use of launchctl. It looks like a non-Apple oriented, plain Unix start file. T.T.F.N. William H. Magill # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.10 # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.10 OSX Server (now dead) mag...@icloud.com mag...@mac.com whmag...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2
On Thu, Oct 23, 2014 at 9:52 PM, William H. Magill mag...@mac.com wrote: Finding /opt/local/apache2/bin/apachectl was obvious. But not from any pllist file. Looking at that file and comparing it with Apple's they are significantly different. I.e. /opt/local/apache2/bin/apachectl contains no reference to a plist file, OR the use of launchctl. It looks like a non-Apple oriented, plain Unix start file. Other way around: the MacPorts launchd plist uses apachectl to actually start the web server, as indicated by the apache2 Portfile. apachectl itself does not reference launchd, it is referenced *by* launchd via the plist. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2
On Oct 23, 2014, at 9:55 PM, Brandon Allbery allber...@gmail.com wrote: On Thu, Oct 23, 2014 at 9:52 PM, William H. Magill mag...@mac.com wrote: Finding /opt/local/apache2/bin/apachectl was obvious. But not from any pllist file. Looking at that file and comparing it with Apple's they are significantly different. I.e. /opt/local/apache2/bin/apachectl contains no reference to a plist file, OR the use of launchctl. It looks like a non-Apple oriented, plain Unix start file. Other way around: the MacPorts launchd plist uses apachectl to actually start the web server, as indicated by the apache2 Portfile. apachectl itself does not reference launchd, it is referenced *by* launchd via the plist. That is the set of instructions I was looking for... I know I've seen them someplace, but cannot find them anywhere! I don't see them in the Portfile for apache2. Maybe they have just gotten lost in an upgrade. They should be something like: sudo /opt/local/etc/LaunchDaemons/org.macports.apache2/apache2.wrapper stop sudo /opt/local/etc/LaunchDaemons/org.macports.apache2/apache2.wrapper start sudo /opt/local/etc/LaunchDaemons/org.macports.apache2/apache2.wrapper restart It's not the most obvious thing in the world. T.T.F.N. William H. Magill # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.10 # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.10 OSX Server (now dead) mag...@icloud.com mag...@mac.com whmag...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2
At 9:52 PM -0400 10/23/14, William H. Magill wrote: On Oct 23, 2014, at 9:33 PM, Brandon Allbery allber...@gmail.com wrote: On Thu, Oct 23, 2014 at 9:23 PM, William H. Magill mag...@mac.com wrote: On Oct 23, 2014, at 8:34 PM, William H. Magill mag...@mac.com wrote: On Oct 23, 2014, at 7:09 PM, Brandon Allbery allber...@gmail.com wrote: Clearly Apachectl does not work. (/usr/sbin/apachectl) It expects to run /usr/sbin/httpd as its binary I would have expected the apache2 ports to install /opt/local/sbin/apachectl, possibly with a version appended. But looking at the apache2 Portfile, it appears to actually be /opt/local/apache2/bin/apachectl. (This path should have been visible in the plist you found.) Finding /opt/local/apache2/bin/apachectl was obvious. But not from any pllist file. The launchd plist's for system-wide services like Apache2 are in '/Library/LaunchDaemons': $ ls -l /Library/LaunchDaemons/org.macports.apache2.plist lrwxr-xr-x 1 root admin 76 4 Jun 14:32 /Library/LaunchDaemons/org.macports.apache2.plist - /opt/local/etc/LaunchDaemons/org.macports.apache2/org.macports.apache2.plist You can 'cat' the plist file to see what it is doing. In this case, it calls a wrapper script. Craig ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2
On Oct 23, 2014, at 10:32 PM, Craig Treleaven ctrelea...@macports.org wrote: At 9:52 PM -0400 10/23/14, William H. Magill wrote: On Oct 23, 2014, at 9:33 PM, Brandon Allbery allber...@gmail.com wrote: On Thu, Oct 23, 2014 at 9:23 PM, William H. Magill mag...@mac.com wrote: On Oct 23, 2014, at 8:34 PM, William H. Magill mag...@mac.com wrote: On Oct 23, 2014, at 7:09 PM, Brandon Allbery allber...@gmail.com wrote: Clearly Apachectl does not work. (/usr/sbin/apachectl) It expects to run /usr/sbin/httpd as its binary I would have expected the apache2 ports to install /opt/local/sbin/apachectl, possibly with a version appended. But looking at the apache2 Portfile, it appears to actually be /opt/local/apache2/bin/apachectl. (This path should have been visible in the plist you found.) Finding /opt/local/apache2/bin/apachectl was obvious. But not from any pllist file. The launchd plist's for system-wide services like Apache2 are in '/Library/LaunchDaemons': $ ls -l /Library/LaunchDaemons/org.macports.apache2.plist lrwxr-xr-x 1 root admin 76 4 Jun 14:32 /Library/LaunchDaemons/org.macports.apache2.plist - /opt/local/etc/LaunchDaemons/org.macports.apache2/org.macports.apache2.plist You can 'cat' the plist file to see what it is doing. In this case, it calls a wrapper script. As i said -- that part of the documentation is missing!!! At one time there were instructions in the port on how to start and stop the Apache server -- they are now missing. The technique to be used is anything but obvious for anyone familiar with Apache. T.T.F.N. William H. Magill mag...@icloud.com mag...@mac.com whmag...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2
On Thu, Oct 23, 2014 at 10:49 PM, William H. Magill mag...@mac.com wrote: At one time there were instructions in the port on how to start and stop the Apache server -- they are now missing. Actually, the way you are *supposed* to do it --- and I suspect this will infuriate you --- is sudo port load apache2 # tell launchd to start it sudo port unload apache2# tell launchd to stop it If you prefer micromanagement, don't use OS X, *or* any Linux using systemd, *or* Solaris's SMF, etc. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2
On Thu, Oct 23, 2014 at 10:49 PM, William H. Magill mag...@mac.com wrote: At one time there were instructions in the port on how to start and stop the Apache server -- they are now missing. The technique to be used is anything but obvious for anyone familiar with Apache. By the way, could you explain why using apachectl --- which is the way you are supposed to manage it directly --- is somehow wrong (not to mention different from systems like Linux or *BSD or Solaris where you control it directly with apachectl)? I think earlier versions *did* require a wrapper script --- but that likely was a workaround for a bug, and is fixed now. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2
On Oct 23, 2014, at 10:58 PM, Craig Treleaven ctrelea...@macports.org wrote: At 10:43 PM -0400 10/23/14, William H. Magill wrote: On Oct 23, 2014, at 9:55 PM, Brandon Allbery allber...@gmail.com wrote: On Thu, Oct 23, 2014 at 9:52 PM, William H. Magill mag...@mac.com wrote: Finding /opt/local/apache2/bin/apachectl was obvious. But not from any pllist file. Looking at that file and comparing it with Apple's they are significantly different. I.e. /opt/local/apache2/bin/apachectl contains no reference to a plist file, OR the use of launchctl. It looks like a non-Apple oriented, plain Unix start file. Other way around: the MacPorts launchd plist uses apachectl to actually start the web server, as indicated by the apache2 Portfile. apachectl itself does not reference launchd, it is referenced *by* launchd via the plist. That is the set of instructions I was looking for... I know I've seen them someplace, but cannot find them anywhere! I don't see them in the Portfile for apache2. Maybe they have just gotten lost in an upgrade. They should be something like: sudo /opt/local/etc/LaunchDaemons/org.macports.apache2/apache2.wrapper stop sudo /opt/local/etc/LaunchDaemons/org.macports.apache2/apache2.wrapper start sudo /opt/local/etc/LaunchDaemons/org.macports.apache2/apache2.wrapper restart It's not the most obvious thing in the world. Perhaps you want the A portion of MAMP: https://trac.macports.org/wiki/howto/MAMP Thanks for providing the URL!!! -- otherwise one can't find it from the MacPorts home page. The link to Documentation is a dead-end page. No links to any other documents. Or even a reference to the existence of the WikI I'll have to read through it to see if it is current now with Yosemite. I last used it back under snow leopard, but then switched to using OSX Server since it was bundled with my MacMiini. But now Apple has unbundled it. At any rate, I expect I'll wind up getting all of MAMP installed and running again -- I had forgotten all of the pieces to the puzzle! Thanks again for the link! I haven't had this much fun migrating from one environment to another since I retired! At least it gives me something to do when I get tired of killing Orcs! T.T.F.N. William H. Magill # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.10 # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.10 OSX Server (now dead) mag...@icloud.com mag...@mac.com whmag...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2
On Oct 23, 2014, at 11:02 PM, Brandon Allbery allber...@gmail.com wrote: On Thu, Oct 23, 2014 at 10:49 PM, William H. Magill mag...@mac.com wrote: At one time there were instructions in the port on how to start and stop the Apache server -- they are now missing. The technique to be used is anything but obvious for anyone familiar with Apache. By the way, could you explain why using apachectl --- which is the way you are supposed to manage it directly --- is somehow wrong (not to mention different from systems like Linux or *BSD or Solaris where you control it directly with apachectl)? I think earlier versions *did* require a wrapper script --- but that likely was a workaround for a bug, and is fixed now. Obviously using /opt/local/apache2/bin/apachectl would be the expected way of doing things. But even that probably needs to be documented because the PATH does not include /opt/local/apache2/bin/ - you have to know that it is there. Because Apple has a copy in /usr/sbin/apachectl which you will get by default. At least I now have the pointer to MMAP again! T.T.F.N. William H. Magill # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.10 # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.10 OSX Server (now dead) mag...@icloud.com mag...@mac.com whmag...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: controlling Macports version of Apache2
On Oct 23, 2014, at 9:54 PM, Brandon Allbery wrote: On Thu, Oct 23, 2014 at 10:49 PM, William H. Magill wrote: At one time there were instructions in the port on how to start and stop the Apache server -- they are now missing. Actually, the way you are *supposed* to do it --- and I suspect this will infuriate you --- is sudo port load apache2 # tell launchd to start it sudo port unload apache2# tell launchd to stop it Right. And to complete the trifecta, to restart the server, kill the master httpd process and launchd will relaunch it for you. MacPorts would have printed instructions about how to load this port when you installed the port. This function is provided by MacPorts base automatically for all ports that use the startupitem keywords. However there is presently no way to re-print the messages at a later time, without reinstalling the port. You have to pay attention to these messages when installing ports. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: pypy checksum mismatch error for OS X 10.10
On Oct 23, 2014, at 6:58 PM, Carlo Tambuatco wrote: Have been unable thus far to reinstall pypy due to a checksum mismatch error: Error: Checksum (md5) mismatch for pypy-2.4.0-src.tar.bz2 Error: Checksum (sha1) mismatch for pypy-2.4.0-src.tar.bz2 Error: Checksum (rmd160) mismatch for pypy-2.4.0-src.tar.bz2 Error: org.macports.checksum for port pypy returned: Unable to verify file checksums I'll attach the log file if there are any interesting errors there. This was already fixed 2 days ago: https://trac.macports.org/ticket/45552 Please sudo port selfupdate and try again. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Strange problems with launchd and macports toolchains/libraries
On Oct 23, 2014, at 10:17 AM, Jameson Merkow wrote:
Our software downloads configures, and builds a few other packages using
cmake. One of these external projects is GTS, which, uses configure (as
opposed to cmake) to configure and build using make and gcc.
So to use the mp libraries and compilers we configure it specifying the
compiler that used by cmake, i.e. something like:
CC=${CMAKE_C_COMPILER} CPP=${CMAKE_CXX_COMPILER}
${${proj}_OUTPUT_DIR}/configure --prefix=${GTS_INSTALL_DIR}
$CPP is the C pre-processor, not the C++ compiler. The C++ compiler variable is
$CXX.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
controlling Macports version of Apache2 -- part 2
On Oct 23, 2014, at 9:42 PM, Brandon Allbery allbery.b at gmail.com wrote: On Thu, Oct 23, 2014 at 9:37 PM, William H. Magill magill at mac.com wrote: What is the equivalent today? MacPorts does not contain a Lynx port which the search command can find. links or elinks, probably. Ports exist for both. There's also w3m and netrik. (port search browser also tells me there is indeed a lynx port. What exactly did you use with port search?) Using the search function on the web page: https://www.macports.org/ports.php?by=categorysubstr=Lynx And https://www.macports.org/ports.php?by=categorysubstr=lynx T.T.F.N. William H. Magill You were searching by category (and there is no lynx category). Searching by name works: https://www.macports.org/ports.php?by=namesubstr=lynx - Josh ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
