Re: script to generate macports dependency graph
Yes, the scripts can be placed anywhere. Typically, you would put them somewhere in your $PATH so that you do not have to remember where they are but this is not actually required. Mathias On 21 Jan 2015, at 22:11, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: On Wed, January 21, 2015 20:58, Murray Eisenberg wrote: Where should one place those two scripts on one's computer? It looks like they can both run from anywhere, making use of your $PATH to find MacPorts. ___ 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
Re: OT probably, help please
On Thu, 22 Jan 2015, William H. Magill wrote: After a tremendous amount of effort on the part of numerous kernel programmers at DEC, they discovered that the bottom level BSD I/O modules had not been looked at (literally) since PDP days. Disk I/O was being done in 128 byte blocks. You sure abut this? My memory of the PDP days (ye olde 11/40) was that I/O was the same as the disk sector i.e. 512 bytes; this was V5/V6/V7 Unix. One thing which I noticed immediately when I turned on iCloud disk in Yosemite -- the lag involved with launching any program which stored anything in the cloud. Not unexpected, but significant none the less. I've never bothered with iCloud; I don't store much stuff anyway (see my signature), and it all gets backed up to my Time Capsule. Similarly, I had a problem where my internal hard drive would literally not spin-up. Took the iMac in to the Apple Store and they ran their diagnostics and pronounced nothing wrong -- the tests passed with flying colors! I finally convinced them that the drive was not spinning up and they got a tech to come out front who had a stethoscope and instantly verified that the drive was not spinning. Didn't they see the dreaded question mark on booting up? I've seen too many cases related to both BSD (and later Mach, i.e. NeXT and OSX) where much of the hardware level stuff is completely ignored by any of the upper-level reporting software. -- one of the main reasons why Drive manufacturers developed S.M.A.R.T. -- the OS does not do the job. Hmmm... I just tried SMART on my drive, but being an external USB drive (long story) it's not supported, so... In my experience, by the time the OS flags a Disk error, you have been suffering constant performance degrading failures which are simply below the reporting threshold, for quite some time. I have been seeing slow performance lately; I bought the MacBook early in 2010, but it's a late 2009 model. I wonder? -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: OT probably, help please
On Thu, Jan 22, 2015 at 4:29 AM, René J.V. rjvber...@gmail.com wrote: A bit too many reports of comparable symptoms in 10.9 somehow related to disk I/O errors for my comfort zone. OS X wouldn't be doing something low level that somehow stresses the disk hardware I hope? Just for one example (in the area of complex systems): HFS+'s hot file support is the sort of thing that can exacerbate failing disks... and the effect would get worse with certain kinds of changes to what files are hot, which might well cause it to become more evident in a newer OS version. And I don't think the right answer here is simplify because that just covers up the fact that it's failing, ensuring that when it becomes obvious again it'll be too late to save your data. (Yes, yes, have backups --- guess what? Backups will *also* make this more obvious. So do you also disable backups because they trigger disk errors?) -- 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: OT probably, help please
On Thu, Jan 22, 2015 at 4:29 AM, René J.V. rjvber...@gmail.com wrote: I wouldn't immediately think about disk i/o errors either from the symptoms you described (not for short freezes in anyway). Not with an hdd anyway. I would --- but that may be because I've seen it in action (most closely related to this thread: freezes like that led me to discover that the HD in my old iBook was kaput). -- 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: OT probably, help please
On Thursday January 22 2015 09:40:28 Brandon Allbery wrote: Just for one example (in the area of complex systems): HFS+'s hot file support is the sort of thing that can exacerbate failing disks... and the effect would get worse with certain kinds of changes to what files are hot, which might well cause it to become more evident in a newer OS version. I don't know if the hot file feature is what I was thinking with low level operations, but yes, it is something that could exacerbate failing disk by concentration frequent read/writes on a specific part of the disk. again it'll be too late to save your data. (Yes, yes, have backups --- guess what? Backups will *also* make this more obvious. So do you also I guess you mean full backups which are a way of testing the entire set of sectors in use? disable backups because they trigger disk errors?) What did you think I was suggesting? I wasn't. I was asking. And yes, I do keep in mind that Apple has reasons to drive sales and incite people to buy new hardware and is probably not above tactics that decrease a product's theoretical lifetime. R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: OT probably, help please
On Thu, Jan 22, 2015 at 11:02 AM, René J.V. rjvber...@gmail.com wrote: And yes, I do keep in mind that Apple has reasons to drive sales and incite people to buy new hardware and is probably not above tactics that decrease a product's theoretical lifetime. I think there are a lot of things one can do that can have the side effect of pushing the boundaries of hardware (this includes things like compression). Not to mention things like SSD where you are explicitly trading lifetime for performance. Searching for reasons to believe it's just to drive obsolescence isn't particularly fruitful, unless you consider paranoia an end in itself. -- 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
Eclipse IDE
Is the Eclipse IDE available from MacPorts? I had the notion that it is but all I see is the following which does not look like the IDE: eclipse-ecj32 3.2.2-200702121330 Eclipse java bytecode compiler Licenses: EPL-1 Maintained by: gmail.com:mvfranz openmaintainer Categories: java Platforms: darwin Dependencies: kaffe unzip apache-ant Jerry ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Not really MacPorts problem, I don't think.
On Jan 22, 2015, at 11:47 AM, William H. Magill wrote: I don't know what MacPorts can do about this one. I have the MacPorts version of Apache2 installed. - Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1k DAV/2 PHP/5.6.4 configured If I power-cycle my machine, when it comes back up, Apache2 has failed to start. If I then try to load Apache2 -- it is reported as already running. $ sudo port load apache2 $ Password: $ /opt/local/etc/LaunchDaemons/org.macports.apache2/org.macports.apache2.plist: Operation already in progress So I unload, then load and Apache starts with no problems. What is happening is apparently a timing problem. I.e. it fails on boot, but works fine after OSX is up and running. The error is simple -- [Thu Jan 22 02:17:12 2015] [info] mod_ssl/2.2.29 compiled against Server: Apache/2.2.29, Library: OpenSSL/1.0.1j [Thu Jan 22 02:17:19 2015] [notice] Digest: generating secret for digest authentication ... [Thu Jan 22 02:17:19 2015] [notice] Digest: done [Thu Jan 22 02:17:19 2015] [alert] (EAI 8)nodename nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of shianbrae.mcgillsociety.org Configuration Failed Shianbrae.mcgillsociety.org is the FQDN of the server. ServerName is configured: ServerName localhost:80 From trying to deal with the local host issue from before. So launchd is launching apache too early. I believe there are some keys one can use in a launchd plist that would affect when launchd tries to launch a service. If you can find a launchd plist key/value that fixes this issue, MacPorts could be enhanced to offer portfile authors a way to use that key, or to use that key/value by default even. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Not really MacPorts problem, I don't think.
At 8:42 PM -0600 1/22/15, Ryan Schmidt wrote: On Jan 22, 2015, at 11:47 AM, William H. Magill wrote: I don't know what MacPorts can do about this one. I have the MacPorts version of Apache2 installed. - Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1k DAV/2 PHP/5.6.4 configured If I power-cycle my machine, when it comes back up, Apache2 has failed to start. If I then try to load Apache2 -- it is reported as already running. $ sudo port load apache2 $ Password: $ /opt/local/etc/LaunchDaemons/org.macports.apache2/org.macports.apache2.plist: Operation already in progress So I unload, then load and Apache starts with no problems. What is happening is apparently a timing problem. I.e. it fails on boot, but works fine after OSX is up and running. The error is simple -- [Thu Jan 22 02:17:12 2015] [info] mod_ssl/2.2.29 compiled against Server: Apache/2.2.29, Library: OpenSSL/1.0.1j [Thu Jan 22 02:17:19 2015] [notice] Digest: generating secret for digest authentication ... [Thu Jan 22 02:17:19 2015] [notice] Digest: done [Thu Jan 22 02:17:19 2015] [alert] (EAI 8)nodename nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of shianbrae.mcgillsociety.org Configuration Failed Shianbrae.mcgillsociety.org is the FQDN of the server. ServerName is configured: ServerName localhost:80 From trying to deal with the local host issue from before. So launchd is launching apache too early. I believe there are some keys one can use in a launchd plist that would affect when launchd tries to launch a service. If you can find a launchd plist key/value that fixes this issue, MacPorts could be enhanced to offer portfile authors a way to use that key, or to use that key/value by default even. I'm not expert, but would the NetworkState key help? See: http://launchd.info/ Goto Configuration, scroll down to ...Depending on Network Availability: Craig ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
pulseaudio 5.0 fails to build
Hello, After the recent request to let phonon-backend-gstreamer depend on the good gstreamer plugins, which by default depend on pulseaudio, I decided to rebuild that port myself without X11 support. Turns out that I cannot even build its default configuration; the build fails with libtool: compile: /usr/bin/clang -DHAVE_CONFIG_H -I. -I.. -I../src -I../src/modules -I../src/modules -DPA_ALSA_PATHS_DIR=\\ -DPA_ALSA_PROFILE_SETS_DIR=\\ -I/opt/local/include -DFASTPATH -D_FORTIFY_SOURCE=2 -D_THREAD_SAFE -pthread -DPA_SRCDIR=\/opt/local/var/macports/build/_opt_local_site-ports_audio_pulseaudio/pulseaudio/work/pulseaudio-5.0/src\ -DPA_BUILDDIR=\/opt/local/var/macports/build/_opt_local_site-ports_audio_pulseaudio/pulseaudio/work/pulseaudio-5.0/src\ -I/opt/local/include/json-c -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -D_REENTRANT -I/opt/local/include/gtk-3.0 -I/opt/local/include/at-spi2-atk/2.0 -I/opt /local/include/at-spi-2.0 -I/opt/local/include/dbus-1.0 -I/opt/local/lib/dbus-1.0/include -I/opt/local/include/gtk-3.0 -I/opt/local/include/gio-unix-2.0/ -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include/cairo -I/opt/local/include/pango-1.0 -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo -I/opt/local/include/pixman-1 -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include/freetype2 -I/opt/local/include -I/opt/local/include/libpng16 -I/opt/local/include/harfbuzz -I/Volumes/Debian/MacPorts/include -I/opt/local/include/freetype2 -I/opt/local/include -I/opt/local/include/harfbuzz -I/opt/local/include -I/opt/local/include/libpng16 -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include/libpng16 -I/opt/lo cal/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/Developer/Headers/FlatCarbon/ -I/opt/local/include/dbus-1.0 -I/opt/local/lib/dbus-1.0/include -Os -arch x86_64 -Wall -W -Wextra -pipe -Wno-long-long -Wno-overlength-strings -Wundef -Wformat=2 -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option -isysroot / -mmacosx-version-min=10.9 -MT pulsecore/libpulsecommon_5.0_la-core-util.lo -MD -MP -MF pulsecore/.deps/libpulsecommon_5.0_la-core-util.Tpo -c pulsecore/core-util.c -fno-common -DPIC -o pulsecore/.libs/libpulsecommon_5.0_la-core-util.o In file included from pulsecore/core-rtclock.c:41: In file included from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:23: In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20: In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:31: /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Finder.h:240:3: error: unknown type name 'Point' Point location; /* File's location in the folder */ ^ /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Finder.h:246:3: error: unknown type name 'Rect' RectwindowBounds; /* The position and dimension of the folder's window */ ^ Any idea what to look for? Is this related to the Xcode update - the binary build is from June 1st 2014, which would be Xcode 5.1 I guess? R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: pulseaudio 5.0 fails to build
On 1/22/15 3:47 PM, René J.V. Bertin wrote: Hello, After the recent request to let phonon-backend-gstreamer depend on the good gstreamer plugins, which by default depend on pulseaudio, I decided to rebuild that port myself without X11 support. Turns out that I cannot even build its default configuration; the build fails with libtool: compile: /usr/bin/clang -DHAVE_CONFIG_H -I. -I.. -I../src -I../src/modules -I../src/modules -DPA_ALSA_PATHS_DIR=\\ -DPA_ALSA_PROFILE_SETS_DIR=\\ -I/opt/local/include -DFASTPATH -D_FORTIFY_SOURCE=2 -D_THREAD_SAFE -pthread -DPA_SRCDIR=\/opt/local/var/macports/build/_opt_local_site-ports_audio_pulseaudio/pulseaudio/work/pulseaudio-5.0/src\ -DPA_BUILDDIR=\/opt/local/var/macports/build/_opt_local_site-ports_audio_pulseaudio/pulseaudio/work/pulseaudio-5.0/src\ -I/opt/local/include/json-c -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -D_REENTRANT -I/opt/local/include/gtk-3.0 -I/opt/local/include/at-spi2-atk/2.0 -I/opt /local/include/at-spi-2.0 -I/opt/local/include/dbus-1.0 -I/opt/local/lib/dbus-1.0/include -I/opt/local/include/gtk-3.0 -I/opt/local/include/gio-unix-2.0/ -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include/cairo -I/opt/local/include/pango-1.0 -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo -I/opt/local/include/pixman-1 -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include/freetype2 -I/opt/local/include -I/opt/local/include/libpng16 -I/opt/local/include/harfbuzz -I/Volumes/Debian/MacPorts/include -I/opt/local/include/freetype2 -I/opt/local/include -I/opt/local/include/harfbuzz -I/opt/local/include -I/opt/local/include/libpng16 -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include/libpng16 -I/opt/lo cal/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/Developer/Headers/FlatCarbon/ -I/opt/local/include/dbus-1.0 -I/opt/local/lib/dbus-1.0/include -Os -arch x86_64 -Wall -W -Wextra -pipe -Wno-long-long -Wno-overlength-strings -Wundef -Wformat=2 -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option -isysroot / -mmacosx-version-min=10.9 -MT pulsecore/libpulsecommon_5.0_la-core-util.lo -MD -MP -MF pulsecore/.deps/libpulsecommon_5.0_la-core-util.Tpo -c pulsecore/core-util.c -fno-common -DPIC -o pulsecore/.libs/libpulsecommon_5.0_la-core-util.o In file included from pulsecore/core-rtclock.c:41: In file included from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:23: In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20: In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:31: /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Finder.h:240:3: error: unknown type name 'Point' Point location; /* File's location in the folder */ ^ /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Finder.h:246:3: error: unknown type name 'Rect' RectwindowBounds; /* The position and dimension of the folder's window */ ^ Any idea what to look for? Is this related to the Xcode update - the binary build is from June 1st 2014, which would be Xcode 5.1 I guess? R. Builds OK for me on Mavericks (10.9.5) both with and without x11 variant. Xcode 6.1.1 Build version 6A2008a What OS version are you using? Dave ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: pulseaudio 5.0 fails to build
On 1/22/15 3:47 PM, René J.V. Bertin wrote: Hello, After the recent request to let phonon-backend-gstreamer depend on the good gstreamer plugins, which by default depend on pulseaudio, I decided to rebuild that port myself without X11 support. Turns out that I cannot even build its default configuration; the build fails with libtool: compile: /usr/bin/clang -DHAVE_CONFIG_H -I. -I.. -I../src -I../src/modules -I../src/modules -DPA_ALSA_PATHS_DIR=\\ -DPA_ALSA_PROFILE_SETS_DIR=\\ -I/opt/local/include -DFASTPATH -D_FORTIFY_SOURCE=2 -D_THREAD_SAFE -pthread -DPA_SRCDIR=\/opt/local/var/macports/build/_opt_local_site-ports_audio_pulseaudio/pulseaudio/work/pulseaudio-5.0/src\ -DPA_BUILDDIR=\/opt/local/var/macports/build/_opt_local_site-ports_audio_pulseaudio/pulseaudio/work/pulseaudio-5.0/src\ -I/opt/local/include/json-c -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -D_REENTRANT -I/opt/local/include/gtk-3.0 -I/opt/local/include/at-spi2-atk/2.0 -I/opt /local/include/at-spi-2.0 -I/opt/local/include/dbus-1.0 -I/opt/local/lib/dbus-1.0/include -I/opt/local/include/gtk-3.0 -I/opt/local/include/gio-unix-2.0/ -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include/cairo -I/opt/local/include/pango-1.0 -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo -I/opt/local/include/pixman-1 -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include/freetype2 -I/opt/local/include -I/opt/local/include/libpng16 -I/opt/local/include/harfbuzz -I/Volumes/Debian/MacPorts/include -I/opt/local/include/freetype2 -I/opt/local/include -I/opt/local/include/harfbuzz -I/opt/local/include -I/opt/local/include/libpng16 -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/Volumes/Debian/MacPorts/include -I/opt/local/include -I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include/libpng16 -I/opt/lo cal/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/Developer/Headers/FlatCarbon/ -I/opt/local/include/dbus-1.0 -I/opt/local/lib/dbus-1.0/include -Os -arch x86_64 -Wall -W -Wextra -pipe -Wno-long-long -Wno-overlength-strings -Wundef -Wformat=2 -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -fno-common -fdiagnostics-show-option -isysroot / -mmacosx-version-min=10.9 -MT pulsecore/libpulsecommon_5.0_la-core-util.lo -MD -MP -MF pulsecore/.deps/libpulsecommon_5.0_la-core-util.Tpo -c pulsecore/core-util.c -fno-common -DPIC -o pulsecore/.libs/libpulsecommon_5.0_la-core-util.o In file included from pulsecore/core-rtclock.c:41: In file included from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:23: In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20: In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:31: /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Finder.h:240:3: error: unknown type name 'Point' Point location; /* File's location in the folder */ ^ /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Finder.h:246:3: error: unknown type name 'Rect' RectwindowBounds; /* The position and dimension of the folder's window */ ^ Any idea what to look for? Is this related to the Xcode update - the binary build is from June 1st 2014, which would be Xcode 5.1 I guess? R. I'll take a look but please file a ticket on trac with all the relevant information including a clean build log in its entirety, Thanks. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: OT probably, help please
On 23 Jan 2015, at 12:42 am, William H. Magill mag...@mac.com wrote: I cannot explain why a (normally) rational, sane thinking idiot did not make that his first port of call (beautifully synced) Jan 21 00:04:34 haycorn kernel[0]: disk0s2: I/O error. Thanks everybody, and sorry for being an idiot I wouldn't immediately think about disk i/o errors either from the symptoms you described (not for short freezes in anyway). Not with an hdd anyway. What's in your logs around those I/O error messages, and what do the smartmontools (in MacPorts) tell about the disk's health? smartctl -a /dev/disk0 and do run smartctl -t long /dev/disk0 (disabling disk spin down for the duration of the test as that would interrupt it)? A bit too many reports of comparable symptoms in 10.9 somehow related to disk I/O errors for my comfort zone. OS X wouldn't be doing something low level that somehow stresses the disk hardware I hope? I confess to bias suspecting yosemite before anything else! smartctl -a gives zillions of errors eg SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000e 078 077 006Old_age Always - 183829319 3 Spin_Up_Time0x0003 100 100 000Pre-fail Always - 0 4 Start_Stop_Count0x0032 099 099 020Old_age Always - 1749 5 Reallocated_Sector_Ct 0x0033 100 100 036Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 081 060 030Pre-fail Always - 147598082 9 Power_On_Hours 0x0032 078 078 000Old_age Always - 19827 10 Spin_Retry_Count0x0013 100 100 097Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 099 099 020Old_age Always - 1505 184 End-to-End_Error0x0032 100 100 099Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000Old_age Always - 34330 188 Command_Timeout 0x0032 100 100 000Old_age Always - 0 189 High_Fly_Writes 0x003a 099 099 000Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 058 040 045Old_age Always In_the_past 42 (3 248 42 24 0) 194 Temperature_Celsius 0x0022 042 060 000Old_age Always - 42 (0 16 0 0 0) 195 Hardware_ECC_Recovered 0x001a 038 025 000Old_age Always - 183829319 197 Current_Pending_Sector 0x0012 100 100 000Old_age Always - 2 198 Offline_Uncorrectable 0x0010 100 100 000Old_age Offline - 2 199 UDMA_CRC_Error_Count0x003e 200 200 000Old_age Always - 0 James ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: OT probably, help please
On Friday January 23 2015 08:56:31 James Linder wrote: smartctl -a gives zillions of errors eg 7 Seek_Error_Rate 0x000f 081 060 030Pre-fail Always - 147598082 195 Hardware_ECC_Recovered 0x001a 038 025 000Old_age Always - 183829319 A zillion is a bit over the top: I see only these 2 indicators that catch attention, but without knowing the disk model it's hard to interpret the data. port:gsmartcontrol can help with that, btw. Bad sectors aren't necessarily detected and recorded on the fly, though. I always forget if the get stored (and remapped) during the 1st extensive self-test after a full disk write or if it's the other way round (last time I had to cope with one was about 10y ago) but in your case a full rewrite may not be required as long as the disk doesn't spin down after the last error and the self test. Good luck, R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: pulseaudio 5.0 fails to build
On Thursday January 22 2015 16:19:39 David Evans wrote: Hi, Thanks for looking. Builds OK for me on Mavericks (10.9.5) both with and without x11 variant. Xcode 6.1.1 Build version 6A2008a What OS version are you using? Same. But I bet you don't get this (copied from my initial message): cal/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/Developer/Headers/FlatCarbon/ - or at least you have nothing at that particular location. Seems the build process picks up things in /Developer when they exist: checking looking for Apple CoreService Framework... checking /Developer/Headers/FlatCarbon/CoreServices.h usability... no checking /Developer/Headers/FlatCarbon/CoreServices.h presence... no Could be worth it trying to deactivate that logic for 10.7 or 10.8 and beyond? R. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: pulseaudio 5.0 fails to build
On Jan 22, 2015, at 7:51 PM, René J.V. Bertin rjvber...@gmail.com wrote: Same. But I bet you don't get this (copied from my initial message): cal/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/Developer/Headers/FlatCarbon/ - or at least you have nothing at that particular location. Seems the build process picks up things in /Developer when they exist: checking looking for Apple CoreService Framework... checking /Developer/Headers/FlatCarbon/CoreServices.h usability... no checking /Developer/Headers/FlatCarbon/CoreServices.h presence... no Could be worth it trying to deactivate that logic for 10.7 or 10.8 and beyond? Does doing so fix your build? vq ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: OT probably, help please (fwd)
Oops; this was meant foe the list... -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) -- Forwarded message -- Date: Fri, 23 Jan 2015 15:11:06 +1100 (EST) From: Dave Horsfall d...@horsfall.org To: René J.V. Bertin rjvber...@gmail.com Subject: Re: OT probably, help please Someone mentioned launchd.info (and I daftly deleted the message). Does it look as wonky for others as it does for me? I'm using Firefox 35.0 (haven't tried others, as the last time I did it buggered up a few things) and I get, in the top half, a static window with some sort of an index and a silhouette of something looking like a watering can, with a full-screen scrolling window under it. -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there)___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
hypermail port problem
*S*ystem: MacMini -- late 2014 - Yosemite 10.10.1; Xcode installed. I've installed macports 2.3.3 with no problems; I've installed port hypermail with no 'apparent' problem. I've followed the MacPorts Guide every step of the way. My first question is this: The install of the hypermail port gives: jeromes-Mac-mini:bin jeromeschatten$ sudo port install hypermail Warning: The Xcode Command Line Tools don't appear to be installed; most ports will likely fail to build. Warning: Install them by running `xcode-select --install'. --- Fetching archive for hypermail --- Attempting to fetch hypermail-2.3.0_1.darwin_14.x86_64.tbz2 from http://packages.macports.org/hypermail --- Attempting to fetch hypermail-2.3.0_1.darwin_14.x86_64.tbz2.rmd160 from http://packages.macports.org/hypermail --- Installing hypermail @2.3.0_1 --- Activating hypermail @2.3.0_1 --- Cleaning hypermail --- Updating database of binaries --- Scanning binaries for linking errors --- No broken files found. But Xcode IS installed and the tools work as I've used them elsewhere. Is this a or is this not a problem? If it's not a problem, then at this point, I should be able to launch the hypermail binary with a './hypermail' and it should run. But it doesn't. The cursor simply moves to the next line and it sits there. No error messages, nothing. I looked at the hypermail and xcode process with top and it reports: PID COMMAND %CPU TIME #TH #WQ #PORT MEMPURG CMPR PGRP [...] 1435 hypermail 0.0 00:00.001015 604K 0B 0B 1435 1404 Xcode0.0 00:02.2681249 66M 72K 0B 1404 So, it doesn't look like hypermail is doing much and Xcode is indeed there. I'd appreciate any suggestions you might have. Thanks, jerome ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: OT probably, help please
On Thu, Jan 22, 2015 at 2:26 PM, René J.V. rjvber...@gmail.com wrote: Oh wait, but you're running FreeBSD on it ... O:-) I read MacBook with a FreeBSD *server*. I used to run that kind of setup myself (and am trying to scrounge hardware to do so again...). -- 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: OT probably, help please
On Jan 22, 2015, at 4:29 AM, René J.V. Bertin rjvber...@gmail.com wrote: On Thursday January 22 2015 08:56:25 James Linder wrote: I cannot explain why a (normally) rational, sane thinking idiot did not make that his first port of call (beautifully synced) Jan 21 00:04:34 haycorn kernel[0]: disk0s2: I/O error. Thanks everybody, and sorry for being an idiot I wouldn't immediately think about disk i/o errors either from the symptoms you described (not for short freezes in anyway). Not with an hdd anyway. What's in your logs around those I/O error messages, and what do the smartmontools (in MacPorts) tell about the disk's health? smartctl -a /dev/disk0 and do run smartctl -t long /dev/disk0 (disabling disk spin down for the duration of the test as that would interrupt it)? A bit too many reports of comparable symptoms in 10.9 somehow related to disk I/O errors for my comfort zone. OS X wouldn't be doing something low level that somehow stresses the disk hardware I hope? Long ago in the days of Ultrix, there were some massive parts of the low-level disk-i/o that never saw the light of day. (Ultrix from DEC being a direct BSD clone.) None of the hardware level routines were addressed by any of the accounting routines. Made performance look good, but debugging impossible. Performance was unexplaninedly lower than the new hardware predicted. After a tremendous amount of effort on the part of numerous kernel programmers at DEC, they discovered that the bottom level BSD I/O modules had not been looked at (literally) since PDP days. Disk I/O was being done in 128 byte blocks. The new hardware had 4096 byte tracks. Calculate how many I/Os were required to write a single track! Increasing the basic block size dramatically cut down on the number of I/Os and their consequent overhead - performance improvement was dramatic. One thing which I noticed immediately when I turned on iCloud disk in Yosemite -- the lag involved with launching any program which stored anything in the cloud. Not unexpected, but significant none the less. Similarly, I had a problem where my internal hard drive would literally not spin-up. Took the iMac in to the Apple Store and they ran their diagnostics and pronounced nothing wrong -- the tests passed with flying colors! I finally convinced them that the drive was not spinning up and they got a tech to come out front who had a stethoscope and instantly verified that the drive was not spinning. I've seen too many cases related to both BSD (and later Mach, i.e. NeXT and OSX) where much of the hardware level stuff is completely ignored by any of the upper-level reporting software. -- one of the main reasons why Drive manufacturers developed S.M.A.R.T. -- the OS does not do the job. In my experience, by the time the OS flags a Disk error, you have been suffering constant performance degrading failures which are simply below the reporting threshold, for quite some time. 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
Not really MacPorts problem, I don't think.
I don't know what MacPorts can do about this one. I have the MacPorts version of Apache2 installed. - Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1k DAV/2 PHP/5.6.4 configured If I power-cycle my machine, when it comes back up, Apache2 has failed to start. If I then try to load Apache2 -- it is reported as already running. $ sudo port load apache2 $ Password: $ /opt/local/etc/LaunchDaemons/org.macports.apache2/org.macports.apache2.plist: Operation already in progress So I unload, then load and Apache starts with no problems. What is happening is apparently a timing problem. I.e. it fails on boot, but works fine after OSX is up and running. The error is simple -- [Thu Jan 22 02:17:12 2015] [info] mod_ssl/2.2.29 compiled against Server: Apache/2.2.29, Library: OpenSSL/1.0.1j [Thu Jan 22 02:17:19 2015] [notice] Digest: generating secret for digest authentication ... [Thu Jan 22 02:17:19 2015] [notice] Digest: done [Thu Jan 22 02:17:19 2015] [alert] (EAI 8)nodename nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of shianbrae.mcgillsociety.org Configuration Failed Shianbrae.mcgillsociety.org is the FQDN of the server. ServerName is configured: ServerName localhost:80 From trying to deal with the local host issue from before. T.T.F.N. William H. Magill # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.10.1 # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.10.1 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: hypermail port problem
On Jan 23, 2015, at 1:31 AM, jerome schatten rom...@shaw.ca wrote: *S*ystem: MacMini -- late 2014 - Yosemite 10.10.1; Xcode installed. I've installed macports 2.3.3 with no problems; I've installed port hypermail with no 'apparent' problem. I've followed the MacPorts Guide every step of the way. For others' benefit, OP already opened a ticket about this: https://trac.macports.org/ticket/46655 vq ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: pulseaudio 5.0 fails to build
On Jan 22, 2015, at 5:47 PM, René J.V. Bertin wrote: In file included from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:23: In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20: In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:31: /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Finder.h:240:3: error: unknown type name 'Point' Point location; /* File's location in the folder */ ^ /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Finder.h:246:3: error: unknown type name 'Rect' RectwindowBounds; /* The position and dimension of the folder's window */ ^ Point and Rect are Carbon types. Carbon is obsolete and should no longer be used. On Jan 22, 2015, at 7:38 PM, René J.V. Bertin wrote: On Thursday January 22 2015 19:58:50 Lawrence Velázquez wrote: checking looking for Apple CoreService Framework... checking /Developer/Headers/FlatCarbon/CoreServices.h usability... no checking /Developer/Headers/FlatCarbon/CoreServices.h presence... no Could be worth it trying to deactivate that logic for 10.7 or 10.8 and beyond? Does doing so fix your build? For now I have only tried the complementary action (moving /Developer/Headers aside) as evidenced by the quote above, and yes, the build works like that. /Developer should only exist on OS X 10.6 and earlier. If you have this directory on OS X 10.9, delete it. All it can do is cause problems. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: hypermail port problem
Looks to me that the command line tools were installed -- are not the compilers part of command line tools? Maybe they're not in the expected place in Yosemite? Last login: Thu Jan 22 23:41:26 on ttys001 jeromes-Mac-mini:~ jeromeschatten$ gcc --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/usr/include/c++/4.2.1 Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn) Target: x86_64-apple-darwin14.0.0 Thread model: posix jeromes-Mac-mini:~ jeromeschatten$ j. On 2015-01-22 11:23 PM, Ryan Schmidt wrote: On Jan 23, 2015, at 12:31 AM, jerome schatten wrote: *S*ystem: MacMini -- late 2014 - Yosemite 10.10.1; Xcode installed. I've installed macports 2.3.3 with no problems; I've installed port hypermail with no 'apparent' problem. I've followed the MacPorts Guide every step of the way. My first question is this: The install of the hypermail port gives: jeromes-Mac-mini:bin jeromeschatten$ sudo port install hypermail Warning: The Xcode Command Line Tools don't appear to be installed; most ports will likely fail to build. Warning: Install them by running `xcode-select --install'. --- Fetching archive for hypermail --- Attempting to fetch hypermail-2.3.0_1.darwin_14.x86_64.tbz2 from http://packages.macports.org/hypermail --- Attempting to fetch hypermail-2.3.0_1.darwin_14.x86_64.tbz2.rmd160 from http://packages.macports.org/hypermail --- Installing hypermail @2.3.0_1 --- Activating hypermail @2.3.0_1 --- Cleaning hypermail --- Updating database of binaries --- Scanning binaries for linking errors --- No broken files found. But Xcode IS installed and the tools work as I've used them elsewhere. Is this a or is this not a problem? Yes, MacPorts requires the Xcode command line tools, and Xcode. These are two separate installations, as of OS X 10.7 Lion. If it's not a problem, then at this point, I should be able to launch the hypermail binary with a './hypermail' and it should run. But it doesn't. The cursor simply moves to the next line and it sits there. No error messages, nothing. I looked at the hypermail and xcode process with top and it reports: PID COMMAND %CPU TIME #TH #WQ #PORT MEMPURG CMPR PGRP [...] 1435 hypermail 0.0 00:00.001015 604K 0B 0B 1435 1404 Xcode0.0 00:02.2681249 66M72K 0B 1404 So, it doesn't look like hypermail is doing much and Xcode is indeed there. Xcode does not need to be running to use MacPorts, it just needs to be installed, as do the separate Xcode command line tools. You didn't get an error while installing hypermail, so I would not suspect absence of the Xcode command line tools to have been a problem in this particular case. But you should install them to prevent future problems with other ports. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: hypermail port problem
On Jan 23, 2015, at 12:31 AM, jerome schatten wrote: *S*ystem: MacMini -- late 2014 - Yosemite 10.10.1; Xcode installed. I've installed macports 2.3.3 with no problems; I've installed port hypermail with no 'apparent' problem. I've followed the MacPorts Guide every step of the way. My first question is this: The install of the hypermail port gives: jeromes-Mac-mini:bin jeromeschatten$ sudo port install hypermail Warning: The Xcode Command Line Tools don't appear to be installed; most ports will likely fail to build. Warning: Install them by running `xcode-select --install'. --- Fetching archive for hypermail --- Attempting to fetch hypermail-2.3.0_1.darwin_14.x86_64.tbz2 from http://packages.macports.org/hypermail --- Attempting to fetch hypermail-2.3.0_1.darwin_14.x86_64.tbz2.rmd160 from http://packages.macports.org/hypermail --- Installing hypermail @2.3.0_1 --- Activating hypermail @2.3.0_1 --- Cleaning hypermail --- Updating database of binaries --- Scanning binaries for linking errors --- No broken files found. But Xcode IS installed and the tools work as I've used them elsewhere. Is this a or is this not a problem? Yes, MacPorts requires the Xcode command line tools, and Xcode. These are two separate installations, as of OS X 10.7 Lion. If it's not a problem, then at this point, I should be able to launch the hypermail binary with a './hypermail' and it should run. But it doesn't. The cursor simply moves to the next line and it sits there. No error messages, nothing. I looked at the hypermail and xcode process with top and it reports: PID COMMAND %CPU TIME #TH #WQ #PORT MEMPURG CMPR PGRP [...] 1435 hypermail 0.0 00:00.001015 604K 0B 0B 1435 1404 Xcode0.0 00:02.2681249 66M72K 0B 1404 So, it doesn't look like hypermail is doing much and Xcode is indeed there. Xcode does not need to be running to use MacPorts, it just needs to be installed, as do the separate Xcode command line tools. You didn't get an error while installing hypermail, so I would not suspect absence of the Xcode command line tools to have been a problem in this particular case. But you should install them to prevent future problems with other ports. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
