From ryandesign at macports.org Sun Jul 1 00:15:31 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 1 Jul 2012 02:15:31 -0500 Subject: Problem installing rpm using macports In-Reply-To: <34096211.post@talk.nabble.com> References: <34096211.post@talk.nabble.com> Message-ID: <82ACA4CA-2840-406D-A861-D1E071FA42AA@macports.org> On Jun 30, 2012, at 13:56, Wim Deblauwe wrote: > > I asked how to install rpm using macports on askdifferent: > http://apple.stackexchange.com/questions/54781/problem-installing-rpm-using-macports > > and I got the answer to try the macports mailing list, so I am doing that > now. Anybody who can help with this? I have filed a bug report for you for this problem: https://trac.macports.org/ticket/35048 Note that the rpm port contains the very old version 4.4.9 of the rpm program. Other ports exist that provide newer versions of rpm which you may want to use instead. None of the newer rpm ports have this particular bug. $ port search "the rpm" rpm @4.4.9 (sysutils, archivers) The RPM package management system. rpm45 @4.5 (sysutils, archivers) The RPM package management system. rpm50 @5.0.3 (sysutils, archivers) The RPM package management system. rpm51 @5.1.9 (sysutils, archivers) The RPM package management system. rpm52 @5.2.1 (sysutils, archivers) The RPM package management system. rpm53 @5.3.11 (sysutils, archivers) The RPM package management system. rpm54 @5.4.9 (sysutils, archivers) The RPM package management system. Found 7 ports. From wim.deblauwe at gmail.com Sun Jul 1 02:13:04 2012 From: wim.deblauwe at gmail.com (Wim Deblauwe) Date: Sun, 1 Jul 2012 11:13:04 +0200 Subject: Problem installing rpm using macports In-Reply-To: References: <34096211.post@talk.nabble.com> Message-ID: I don't want to install an rpm on my mac. I want to build rpm packages on my mac for installation on other CentOS or Redhat machines. 2012/7/1 Brandon Allbery > On Sat, Jun 30, 2012 at 2:56 PM, Wim Deblauwe wrote: > >> I asked how to install rpm using macports on askdifferent: >> >> http://apple.stackexchange.com/questions/54781/problem-installing-rpm-using-macports >> and I got the answer to try the macports mailing list, so I am doing >> that now. Anybody who can help with this? >> > > Just looking at the portfile, it's looking pretty out of date. I suspect > it's not being actively maintained (and don't see offhand why anyone would > use it anyway; it's not like you can usefully install any RPM packages ? > even noarch packages would probably require a metapackage representing OS > X-provided files as dependencies. > > Beyond that , this is apparently something going wrong with fixing up > Python paths. More detail should be available via "port log rpm"; can you > pastebin or attach the output from that? > > -- > brandon s allbery allbery.b at gmail.com > wandering unix systems administrator (available) (412) 475-9364 vm/sms > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From comer.duncan at gmail.com Sun Jul 1 13:47:26 2012 From: comer.duncan at gmail.com (Comer Duncan) Date: Sun, 1 Jul 2012 16:47:26 -0400 Subject: help with trouble with pango, etc Message-ID: Hi, I am in the process of installing a set of macport items prior to installing a big software package on my macbook pro running lion. I need the following ports: szip, gcc46, gsl, hdf5-18 +gcc46 -universal So far I can not get either szip or gcc46 to install and the reason seems connected to pango? Here is the attempt: homelap-3:~ comerduncan$ sudo port install szip Password: ---> Cleaning szip ---> Scanning binaries for linking errors: 100.0% ---> Found 57 broken file(s), matching files to ports ---> Found 9 broken port(s), determining rebuild order ---> Rebuilding in order pango @1.30.0 +x11 atk @2.2.0 gtk2 @2.24.10 +x11 gtk2-aurora @1.5.1 libglade2 @2.6.4 vte @0.28.2 +python27 geany @0.21 poppler @0.18.4 gcc45 @4.5.3 Error: pango: Variant no_x11 conflicts with x11 Error: Unable to open port: Error evaluating variants Error rebuilding pango while executing "error "Error rebuilding $portname"" (procedure "revupgrade_scanandrebuild" line 370) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "action_revupgrade $action $portlist $opts" (procedure "action_target" line 94) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 95) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 4784) And here is the output of trying to install gcc46: homelap-3:~ comerduncan$ sudo port install gcc46 ---> Computing dependencies for gcc46 ---> Cleaning gcc46 ---> Scanning binaries for linking errors: 100.0% ---> Found 57 broken file(s), matching files to ports ---> Found 9 broken port(s), determining rebuild order ---> Rebuilding in order pango @1.30.0 +x11 atk @2.2.0 gtk2 @2.24.10 +x11 gtk2-aurora @1.5.1 libglade2 @2.6.4 vte @0.28.2 +python27 geany @0.21 poppler @0.18.4 gcc45 @4.5.3 Error: pango: Variant no_x11 conflicts with x11 Error: Unable to open port: Error evaluating variants Error rebuilding pango while executing "error "Error rebuilding $portname"" (procedure "revupgrade_scanandrebuild" line 370) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "action_revupgrade $action $portlist $opts" (procedure "action_target" line 94) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 95) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining Can someone please help me get past this barrier? Your help is much appreciated. Comer -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Sun Jul 1 15:18:11 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 1 Jul 2012 17:18:11 -0500 Subject: help with trouble with pango, etc In-Reply-To: References: Message-ID: On Jul 1, 2012, at 15:47, Comer Duncan wrote: > ---> Rebuilding in order > pango @1.30.0 +x11 This shows you have pango installed with the +x11 variant (this is the default). > Error: pango: Variant no_x11 conflicts with x11 This shows MacPorts is trying to rebuild pango with the +x11 and +no_x11 variants. That won't work; they conflict with one another. This could happen if you requested +no_x11 on the command line, but since it's MacPorts automatically rebuilding things, I'm guessing it's rather that you added +no_x11 to your variants.conf file? The decision about whether to use x11 or quartz ideally needs to be made before you've installed any ports, because it's difficult to go back later and discern which of your installed ports care about the distinction. From allbery.b at gmail.com Sun Jul 1 16:36:13 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Sun, 1 Jul 2012 19:36:13 -0400 Subject: help with trouble with pango, etc In-Reply-To: References: Message-ID: On Sun, Jul 1, 2012 at 4:47 PM, Comer Duncan wrote: > homelap-3:~ comerduncan$ sudo port install szip > Password: > ---> Cleaning szip > This mneans szip is already installed. > ---> Scanning binaries for linking errors: 100.0% > ---> Found 57 broken file(s), matching files to ports > ---> Found 9 broken port(s), determining rebuild order > ---> Rebuilding in order > pango @1.30.0 +x11 > Modern MacPorts checks *all* installed ports after an operation for breakage, usually in the form of missing shared libraries. So szip is not really related to this issue, unless your earlier (not shown) attempts to install it reinstalled some dependency with incompatible variants. pango would be an odd one for that, though, so I suspect something else caused its breakage. (Or it was already broken and you recently selfupdate-d to a version of MacPorts with the rev-upgrade checks.) In any case, the reported problem is that you have a version of pango installed with +no_x11, but MacPorts thinks it should be installed with +x11 instead. You can possibly fix this with sudo port -R upgrade --enforce-variants pango -no_x11 +x11 but this may lead to other conflicts down the line with whatever forced you into having the wrong pango variiant installed. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From jam at tigger.ws Sun Jul 1 17:27:37 2012 From: jam at tigger.ws (James Linder) Date: Mon, 2 Jul 2012 08:27:37 +0800 Subject: Problem installing rpm using macports In-Reply-To: References: Message-ID: <1BE686EC-F2D8-4CD9-9CC0-ADEEA79B8E4D@tigger.ws> On 01/07/2012, at 10:00 PM, macports-users-request at lists.macosforge.org wrote: > I don't want to install an rpm on my mac. I want to build rpm packages on > my mac for installation on other CentOS or Redhat machines. > > 2012/7/1 Brandon Allbery > >> On Sat, Jun 30, 2012 at 2:56 PM, Wim Deblauwe wrote: >> >>> I asked how to install rpm using macports on askdifferent: >>> >>> http://apple.stackexchange.com/questions/54781/problem-installing-rpm-using-macports >>> and I got the answer to try the macports mailing list, so I am doing >>> that now. Anybody who can help with this? >>> >> >> Just looking at the portfile, it's looking pretty out of date. I suspect >> it's not being actively maintained (and don't see offhand why anyone would >> use it anyway; it's not like you can usefully install any RPM packages ? >> even noarch packages would probably require a metapackage representing OS >> X-provided files as dependencies. >> >> Beyond that , this is apparently something going wrong with fixing up >> Python paths. More detail should be available via "port log rpm"; can you >> pastebin or attach the output from that? Brandon I don't know what you really want to do, but what you SAID will not work (it may work in a trivial case). If you want to build rpm for xxx distro eg CentOS5 then you need to build on CentOS5. I have examples where rpm built on COS6 won't work on COS5 machines never mind the foibles of OSX. VBOX works nicely on mac and I have guests to build rpm for RedHat 9, COS5 and COS6 in 32 and 64 bit mode. Save yourself the heart ache and believe that you cannot cross build rpm. ('course you can, but you really have to be on the ball to do that). Much much easier to install and use vbox James From sierkb at gmx.de Sun Jul 1 17:37:37 2012 From: sierkb at gmx.de (sierkb at gmx.de) Date: Mon, 2 Jul 2012 02:37:37 +0200 Subject: Problem installing rpm using macports In-Reply-To: <1BE686EC-F2D8-4CD9-9CC0-ADEEA79B8E4D@tigger.ws> References: <1BE686EC-F2D8-4CD9-9CC0-ADEEA79B8E4D@tigger.ws> Message-ID: <3E50FC61-26A5-448E-A507-2A2F7C5885A2@gmx.de> Am 02.07.2012 um 02:27 schrieb James Linder: > > If you want to build rpm for xxx distro eg CentOS5 then you need to build on CentOS5. > [..] > Save yourself the heart ache and believe that you cannot cross build rpm. ('course you can, but you really have to be on the ball to do that). Have a look at: https://build.opensuse.org/ http://www.open-build-service.org/ From allbery.b at gmail.com Sun Jul 1 21:00:26 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Mon, 2 Jul 2012 00:00:26 -0400 Subject: Problem installing rpm using macports In-Reply-To: <1BE686EC-F2D8-4CD9-9CC0-ADEEA79B8E4D@tigger.ws> References: <1BE686EC-F2D8-4CD9-9CC0-ADEEA79B8E4D@tigger.ws> Message-ID: On Sun, Jul 1, 2012 at 8:27 PM, James Linder wrote: > On 01/07/2012, at 10:00 PM, macports-users-request at lists.macosforge.orgwrote: > > I don't want to install an rpm on my mac. I want to build rpm packages on > > my mac for installation on other CentOS or Redhat machines. > > > > Brandon I don't know what you really want to do, but what you SAID will > not work (it may work in a trivial case). > Wim is the OP, not me. Otherwise, you are correct: we don't have cross-build facilities in MacPorts like FreeBSD ports has (and, to be honest, I wouldn't want to rely on even those to build cross-platform RPMs). Correct answer here is VirtualBox or Parallels with the target distribution running as a guest. (I personally like Parallels a little better, find it a bit faster than vbox; I'm also told that many people on Lion get kernel panics from vbox, although as yet I have managed not to trigger that failure mode.) -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From phildobbin at gmail.com Sun Jul 1 23:21:16 2012 From: phildobbin at gmail.com (Phil Dobbin) Date: Mon, 02 Jul 2012 07:21:16 +0100 Subject: xz & liblzma Message-ID: <4FF13DDC.4050905@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, all. I've just ran `sudo port -v selfupdate` & got: `$ port outdated The following installed ports are outdated: liblzma 5.0.3_0 < 5.0.3_1 ruby 1.8.7-p358_0 < 1.8.7-p370_0 xz 5.0.3_0 < 5.0.4_0 ` so I went ahead & upgraded. Then I got: `$ sudo port upgrade outdated - ---> liblzma is replaced by xz - ---> Computing dependencies for xz - ---> Fetching archive for xz - ---> Attempting to fetch xz-5.0.4_0.darwin_10.x86_64.tbz2 from http://packages.macports.org/xz - ---> Attempting to fetch xz-5.0.4_0.darwin_10.x86_64.tbz2.rmd160 from http://packages.macports.org/xz - ---> Installing xz @5.0.4_0 - ---> Cleaning xz - ---> Deactivating liblzma @5.0.3_0 - ---> Unable to deactivate liblzma @5.0.3_0, the following ports depend on it: - ---> ImageMagick @6.7.7-2_0+q16 Warning: Deactivate forced. Proceeding despite dependencies.` so it looks like ImageMagick may have a problem. I don't actually mind losing it on this box (its work is done) so do I just go ahead & do the usual dependency dance & then uninstall? Also, if that's the case, is there a quicker (i.e. one-liner) I can run to take care of uninstalling ImageMagick? Or is it a case of xz replacing liblzma & all's well & I can forget the whole thing? Any help appreciated. Cheers, Phil... - -- But masters, remember that I am an ass. Though it be not written down, yet forget not that I am an ass. Wm. Shakespeare - Much Ado About Nothing -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: ??auto-key-locate cert pka ldap hkp://keys.gnupg.net Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJP8T3ZAAoJEKpMeDHWT5ADe2sH/2MSfjcljzvG5aYyrz+5/Xwr E071To82UIlFrZMskgjcugDTu6jYXgrr59wVlLTGblqULxK/ZeFQ2Cp4R1HtYcBE fgdRyOSaI89M3Jih5Ze04BYdFuumrqnzrAuhfbbh6MP6KdsnsilT08MgYExVo0UN pk4R4E2204im4hV6xlQQbb1mySSbPMVS6CbmPmb1bxlQ7WwTLoid1m4MGdCjMH4H WWQDEnOzAVWbS4lL22H774hU3Qkw1u9MwATyfJnvcwp80PqIG5OPqRPMEMMNTpnf NsodGXGxK4x7+qsVxBP3GjGfujfI7c7pr1RzQN/3Bfsqndy4lZln0U2ttJDfHvU= =d2y/ -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3878 bytes Desc: S/MIME Cryptographic Signature URL: From mparchet at sunrise.ch Mon Jul 2 02:44:48 2012 From: mparchet at sunrise.ch (Michael Parchet) Date: Mon, 02 Jul 2012 11:44:48 +0200 Subject: Unable to install openjdk6 Message-ID: <4FF16D90.1090203@sunrise.ch> Hello, I have tried to install openjdk6 but but I have the error below port openjdk6_bootstrap still broken after rebuilding 3 time(s) while executing "error "Port $portname still broken after rebuilding [expr $broken_port_counts($portname) - 1] time(s)"" (procedure "revupgrade_scanandrebuild" line 256) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "action_revupgrade $action $portlist $opts" (procedure "action_upgrade" line 24) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 95) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 4784) /sudo port -d -y rev-upgrade Password: DEBUG: Copying /Users/rparchet/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/ld64/ld DEBUG: Missing architecture arm in file /usr/lib/libc++abi.dylib DEBUG: Missing architecture arm in file outside prefix referenced from /opt/local/lib/apple-gcc42/gcc/i686-apple-darwin11/4.2.1/libstdc++.dylib DEBUG: Missing architecture arm in file /usr/lib/libSystem.B.dylib DEBUG: Missing architecture arm in file outside prefix referenced from /opt/local/lib/apple-gcc42/gcc/i686-apple-darwin11/4.2.1/libstdc++.dylib DEBUG: Ignoring loadcommand containing @rpath in /opt/local/Library/Frameworks/BGHUDAppKit.framework/Versions/A/Resources/BGHUDAppKitPlugin.ibplugin/Contents/MacOS/BGHUDAppKitPlugin DEBUG: skipping ppc in /opt/local/share/cmake-2.8/Modules/CPack.OSXScriptLauncher.in since this system can't run it anyway DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/bugpoint DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llc DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/lli DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-ar DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-as DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-bcanalyzer DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-cov DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-diff DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-dis DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-dwarfdump DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-extract DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-ld DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-link DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-mc DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-nm DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-objdump DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-prof DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-ranlib DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-rtdyld DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/llvm-size DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/macho-dump DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/llvm-3.0/bin/opt DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/MacOS/Qt Creator DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/MacOS/Qt Creator DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libAnalyzerBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libAnalyzerBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libAnalyzerBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libAnalyzerBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libAnalyzerBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libAnalyzerBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libAnalyzerBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libAnalyzerBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libAnalyzerBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libAnalyzerBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBazaar.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBazaar.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBazaar.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBazaar.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBazaar.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBazaar.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBazaar.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBazaar.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBazaar.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBazaar.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBazaar.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBinEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBinEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBinEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBinEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBinEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBinEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBinEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBinEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBinEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBookmarks.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBookmarks.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBookmarks.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBookmarks.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBookmarks.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBookmarks.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBookmarks.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBookmarks.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBookmarks.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libBookmarks.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCMakeProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCVS.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCVS.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCVS.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCVS.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCVS.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCVS.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCVS.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCVS.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCVS.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCVS.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCVS.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libClassView.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCodePaster.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCodePaster.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCodePaster.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCodePaster.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCodePaster.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCodePaster.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCodePaster.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCodePaster.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCodePaster.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCore.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCore.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCore.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCore.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libCppTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDebugger.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libDesigner.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFakeVim.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFakeVim.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFakeVim.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFakeVim.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFakeVim.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFakeVim.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFakeVim.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFakeVim.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFakeVim.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFind.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFind.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFind.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFind.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libFind.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGLSLEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libGenericProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelloWorld.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelloWorld.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelloWorld.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelloWorld.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelloWorld.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelp.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelp.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelp.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelp.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelp.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelp.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelp.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libHelp.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libImageViewer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libImageViewer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libImageViewer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libImageViewer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libImageViewer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libLocator.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libLocator.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libLocator.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libLocator.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libLocator.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libLocator.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMacros.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMacros.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMacros.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMacros.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMacros.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMacros.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMacros.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMacros.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMacros.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMemcheck.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMercurial.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMercurial.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMercurial.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMercurial.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMercurial.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMercurial.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMercurial.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMercurial.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMercurial.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMercurial.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libMercurial.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libPerforce.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libPerforce.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libPerforce.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libPerforce.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libPerforce.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libPerforce.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libPerforce.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libPerforce.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libPerforce.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libPerforce.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libPerforce.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libProjectExplorer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libProjectExplorer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libProjectExplorer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libProjectExplorer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libProjectExplorer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libProjectExplorer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libProjectExplorer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libProjectExplorer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libProjectExplorer.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSInspector.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlJSTools.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQmlProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libQt4ProjectManager.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libResourceEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libResourceEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libResourceEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libResourceEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libResourceEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libScmGit.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libScmGit.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libScmGit.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libScmGit.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libScmGit.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libScmGit.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libScmGit.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libScmGit.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libScmGit.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libScmGit.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libScmGit.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libSubversion.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libSubversion.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libSubversion.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libSubversion.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libSubversion.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libSubversion.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libSubversion.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libSubversion.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libSubversion.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libSubversion.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libSubversion.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTaskList.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTaskList.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTaskList.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTaskList.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTaskList.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTaskList.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTaskList.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTaskList.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTaskList.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTaskList.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTextEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTextEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTextEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTextEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTextEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTextEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTextEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libTextEditor.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libVCSBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libVCSBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libVCSBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libVCSBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libVCSBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libVCSBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libVCSBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libVCSBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libVCSBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libVCSBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libValgrindToolBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libValgrindToolBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libValgrindToolBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libValgrindToolBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libValgrindToolBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libValgrindToolBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libValgrindToolBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libValgrindToolBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libValgrindToolBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libValgrindToolBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libValgrindToolBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libValgrindToolBase.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libWelcome.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libWelcome.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libWelcome.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libWelcome.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/Nokia/libWelcome.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libCPlusPlus.1.0.0.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libExtensionSystem.1.0.0.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libGLSL.1.0.0.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libGLSL.1.0.0.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libLanguageUtils.1.0.0.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libLanguageUtils.1.0.0.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libQmlEditorWidgets.1.0.0.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libQmlJS.1.0.0.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libQmlJS.1.0.0.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libQmlJS.1.0.0.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libUtils.1.0.0.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libValgrind.1.0.0.dylib DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Qt4/Qt Creator.app/Contents/PlugIns/libValgrind.1.0.0.dylib DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/bin/wineserver DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/bin/wmc DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/bin/wrc DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/acledit.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/aclui.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/activeds.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/actxprxy.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/advapi32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/advpack.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/amstream.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/apphelp.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/appwiz.cpl.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/aspnet_regiis.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/atl.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/attrib.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/authz.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/avicap32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/avifil32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/avifile.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/avrt.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/bcrypt.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/browseui.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/cabarc.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/cabinet.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/cacls.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/capi2032.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/cards.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/cfgmgr32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/clock.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/clusapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/cmd.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/comcat.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/comctl32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/comdlg32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/comm.drv16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/commdlg.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/compobj.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/compstui.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/control.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/credui.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/crtdll.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/crypt32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/cryptdlg.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/cryptdll.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/cryptnet.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/cryptui.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/cscript.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ctapi32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ctl3d.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ctl3d32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ctl3dv2.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3d10.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3d10core.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3d8.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3d9.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dcompiler_33.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dcompiler_34.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dcompiler_35.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dcompiler_36.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dcompiler_37.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dcompiler_38.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dcompiler_39.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dcompiler_40.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dcompiler_41.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dcompiler_42.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dcompiler_43.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dim.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3drm.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx10_33.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx10_34.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx10_35.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx10_36.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx10_37.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx10_38.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx10_39.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx10_40.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx10_41.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx10_42.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx10_43.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_24.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_25.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_26.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_27.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_28.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_29.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_30.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_31.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_33.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_34.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_35.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_36.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_37.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_38.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_39.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_40.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_41.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_42.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dx9_43.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/d3dxof.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dbgeng.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dbghelp.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dciman32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ddeml.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ddraw.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ddrawex.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/devenum.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dhcpcsvc.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dinput.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dinput8.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dispdib.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dispex.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/display.drv16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dmband.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dmcompos.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dmime.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dmloader.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dmscript.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dmstyle.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dmsynth.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dmusic.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dmusic32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dnsapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dplay.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dplayx.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dpnaddr.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dpnet.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dpnhpast.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dpnlobby.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dpwsockx.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/drmclien.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dsound.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dssenh.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dswave.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dwmapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dxdiag.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dxdiagn.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/dxgi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/eject.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/expand.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/explorer.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/explorerframe.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/extrac32.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/faultrep.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/fltlib.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/fusion.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/fwpuclnt.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/gameux.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/gdi.exe16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/gdi32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/gdiplus.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/glu32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/gphoto2.ds.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/gpkcsp.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/hal.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/hh.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/hhctrl.ocx.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/hid.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/hlink.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/hnetcfg.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/hostname.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/httpapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/iccvid.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/icinfo.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/icmp.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ieframe.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/iexplore.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ifsmgr.vxd.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/imaadp32.acm.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/imagehlp.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/imm.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/imm32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/inetcomm.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/inetcpl.cpl.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/inetmib1.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/infosoft.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/initpki.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/inkobj.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/inseng.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ipconfig.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/iphlpapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/itircl.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/itss.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/jscript.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/kernel32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/keyboard.drv16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/krnl386.exe16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ktmw32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/loadperf.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/localspl.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/localui.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/lodctr.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/lz32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/lzexpand.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mapi32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mapistub.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mciavi32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mcicda.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mciqtz32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mciseq.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mciwave.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/midimap.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mlang.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mmcndmgr.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mmdevapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mmdevldr.vxd.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mmsystem.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mofcomp.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/monodebg.vxd.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mountmgr.sys.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mouse.drv16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mpr.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mprapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msacm.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msacm32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msacm32.drv.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msadp32.acm.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mscat32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mscms.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mscoree.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msctf.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msdaps.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msdmo.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msftedit.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msg711.acm.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msgsm32.acm.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mshta.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mshtml.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mshtml.tlb.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msiexec.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msimg32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msimsg.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msimtf.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msisip.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msisys.ocx.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msnet32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mspatcha.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msrle32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mssign32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mssip32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mstask.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcirt.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcp100.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcp60.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcp70.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcp71.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcp80.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcp90.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcr100.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcr70.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcr71.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcr80.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcr90.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcrt.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcrt20.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcrt40.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvcrtd.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvfw32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvidc32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msvideo.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/mswsock.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msxml.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msxml2.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msxml3.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msxml4.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/msxml6.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/nddeapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/net.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/netapi32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/netsh.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/newdev.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ngen.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/normaliz.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/notepad.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/npmshtml.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ntdll.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ntdsapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ntoskrnl.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ntprint.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/objsel.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/odbc32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/odbccp32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ole2.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ole2conv.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ole2disp.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ole2nls.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ole2prox.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ole2thk.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ole32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/oleacc.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/oleaut32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/olecli.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/olecli32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/oledb32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/oledlg.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/olepro32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/olesvr.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/olesvr32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/olethk32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/oleview.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/opencl.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/opengl32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/pdh.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/photometadatahandler.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/pidgen.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ping.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/plugplay.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/powrprof.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/presentationfontcache.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/printui.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/progman.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/propsys.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/psapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/pstorec.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/qcap.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/qedit.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/qmgr.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/qmgrprxy.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/quartz.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/query.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/rasapi16.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/rasapi32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/rasdlg.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/reg.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/regapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/regasm.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/regedit.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/regsvcs.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/regsvr32.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/resutils.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/riched20.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/riched32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/rpcrt4.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/rpcss.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/rsabase.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/rsaenh.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/rstrtmgr.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/rtutils.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/rundll.exe16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/rundll32.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/samlib.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/sane.ds.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/sc.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/scarddlg.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/sccbase.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/schannel.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/scrrun.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/secedit.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/secur32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/security.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/sensapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/serialui.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/servicemodelreg.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/services.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/setupapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/setupx.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/sfc.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/sfc_os.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/shdoclc.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/shdocvw.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/shell.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/shell32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/shfolder.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/shlwapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/slbcsp.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/slc.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/snmpapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/softpub.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/sound.drv16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/spoolss.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/spoolsv.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/start.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/stdole2.tlb.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/stdole32.tlb.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/sti.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/storage.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/stress.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/svchost.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/svrapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/sxs.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/system.drv16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/t2embed.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/tapi32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/taskkill.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/taskmgr.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/termsv.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/toolhelp.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/traffic.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/twain.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/twain_32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/typelib.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/unicows.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/uninstaller.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/unlodctr.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/updspapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/url.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/urlmon.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/usbd.sys.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/user.exe16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/user32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/userenv.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/usp10.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/uxtheme.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/vbscript.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/vcomp.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/vdhcp.vxd.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/vdmdbg.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ver.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/version.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/view.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/vmm.vxd.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/vnbt.vxd.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/vnetbios.vxd.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/vtdapi.vxd.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/vwin32.vxd.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/w32skrnl.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/w32sys.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wbemprox.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wer.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wiaservc.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/win32s16.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/win87em.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winaspi.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/windebug.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/windowscodecs.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wineboot.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winebrowser.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winecfg.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wineconsole.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winecoreaudio.drv.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wined3d.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winedbg.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winedevice.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winefile.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winegstreamer.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winemapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winemenubuilder.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winemine.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winemp3.acm.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winemsibuilder.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winepath.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wineps.drv.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wineps16.drv16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wineqtdecoder.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winequartz.drv.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winevdm.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winex11.drv.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wing.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wing32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winhelp.exe16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winhlp32.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winhttp.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wininet.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winmm.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winnls.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winnls32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winoldap.mod16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winscard.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winsock.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winspool.drv.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winsta.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wintab.dll16.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wintab32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wintrust.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/winver.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wlanapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wldap32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wmi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wmic.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wmiutils.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wnaspi32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wordpad.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wow32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/write.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/ws2_32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wscript.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wshom.ocx.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wsock32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wtsapi32.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wuapi.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/wuaueng.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/xapofx1_1.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/xcopy.exe.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/xinput1_1.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/xinput1_2.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/xinput1_3.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/xinput9_1_0.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/xmllite.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/xolehlp.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/lib/wine/xpsprint.dll.so DEBUG: Ignoring loadcommand containing @executable_path in /opt/local/libexec/wine/wine ---> Scanning binaries for linking errors Could not open /opt/local/var/macports/build/_data_Users_landonf_Documents_Code_MacPorts_macports-trunk_dports_java_openjdk6/work/build/bsd-i586/lib/i386/libjava.dylib: Error opening or reading file (referenced from /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/headless/libmawt.dylib) DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/headless/libmawt.dylib as broken Could not open /opt/local/var/macports/build/_data_Users_landonf_Documents_Code_MacPorts_macports-trunk_dports_java_openjdk6/work/build/bsd-i586/lib/i386/libawt.dylib: Error opening or reading file (referenced from /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/headless/libmawt.dylib) DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/headless/libmawt.dylib as broken Could not open libjvm.dylib: Error opening or reading file (referenced from /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/headless/libmawt.dylib) DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/headless/libmawt.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libattach.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libattach.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libawt.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libawt.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libfontmanager.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libfontmanager.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libfontmanager.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libj2gss.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libj2gss.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libj2pcsc.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libj2pcsc.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libj2pkcs11.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libj2pkcs11.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjaas_unix.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjaas_unix.dylib as broken Could not open /opt/local/var/macports/build/_data_Users_landonf_Documents_Code_MacPorts_macports-trunk_dports_java_openjdk6/work/build/bsd-i586/lib/i386/libverify.dylib: Error opening or reading file (referenced from /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjava.dylib) DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjava.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjava.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjawt.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjawt.dylib as broken Could not open /opt/local/var/macports/build/_data_Users_landonf_Documents_Code_MacPorts_macports-trunk_dports_java_openjdk6/work/build/bsd-i586/lib/i386/xawt/libmawt.dylib: Error opening or reading file (referenced from /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjawt.dylib) DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjawt.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjawt.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjpeg.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjpeg.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjsound.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libjsound.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/liblcms.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/liblcms.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/liblcms.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libmanagement.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libmanagement.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libmlib_image.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libmlib_image.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libnet.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libnet.dylib as broken Could not open /opt/local/var/macports/build/_data_Users_landonf_Documents_Code_MacPorts_macports-trunk_dports_java_openjdk6/work/build/bsd-i586/lib/i386/libnet.dylib: Error opening or reading file (referenced from /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libnio.dylib) DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libnio.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libnio.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/librmi.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/librmi.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libunpack.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libunpack.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libverify.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libzip.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/libzip.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/xawt/libmawt.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/xawt/libmawt.dylib as broken DEBUG: Missing architecture i386 in file /opt/local/lib/libXtst.6.dylib DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/xawt/libmawt.dylib as broken DEBUG: Marking /opt/local/share/java/openjdk6_bootstrap/jre/lib/i386/xawt/libmawt.dylib as broken ---> Found 50 broken file(s), matching files to ports ---> Found 1 broken port(s), determining rebuild order DEBUG: Broken: openjdk6_bootstrap DEBUG: Processing port openjdk6_bootstrap @0:b16-r1_0 ---> Rebuilding in order openjdk6_bootstrap @b16-r1 DEBUG: epoch: in tree: 0 installed: 0 DEBUG: openjdk6_bootstrap b16-r1_0 exists in the ports tree DEBUG: openjdk6_bootstrap b16-r1_0 is the latest installed DEBUG: openjdk6_bootstrap b16-r1_0 is active DEBUG: Merging existing variants '' into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/java/openjdk6_bootstrap DEBUG: OS darwin/11.4.0 (Mac OS X 10.7) arch i386 DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: universal_variant is false, so not adding the default universal variant DEBUG: rev-upgrade override ... upgrading! DEBUG: Not following dependencies Skipping deactivate openjdk6_bootstrap @b16-r1_0 (dry run) Skipping activate openjdk6_bootstrap @b16-r1_0 (dry run) DEBUG: Rebuilding port openjdk6_bootstrap finished with status 0 Warning: If this was no dry run, rev-upgrade would now run the checks again to find unresolved and newly created problems/ Can you help me please ? Best regards mparchet -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexey.muranov at gmail.com Mon Jul 2 04:41:31 2012 From: alexey.muranov at gmail.com (Alexey Muranov) Date: Mon, 2 Jul 2012 13:41:31 +0200 Subject: cannot install ack Message-ID: <1AC1F807-9BA9-491F-B05D-BC93A076AFF8@gmail.com> Hello, i have a strange problem, i cannot install ack with MacPorts: ? sudo port install p5-app-ack ---> Computing dependencies for p5-app-ack ---> Dependencies to be installed: p5.12-app-ack ... ---> Installing p5-app-ack @1.960.0_1 ---> Activating p5-app-ack @1.960.0_1 ---> Cleaning p5-app-ack ---> Updating database of binaries: 100.0%---> Scanning binaries for linking errors: 100.0% ---> No broken files found. ? ack zsh: command not found: ack ? /opt/local/bin/ack zsh: no such file or directory: /opt/local/bin/ack Have anybody had this? What can i do? Thanks, Alexey. From jeremy at lavergne.gotdns.org Mon Jul 2 05:50:10 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Mon, 2 Jul 2012 08:50:10 -0400 Subject: cannot install ack In-Reply-To: <1AC1F807-9BA9-491F-B05D-BC93A076AFF8@gmail.com> References: <1AC1F807-9BA9-491F-B05D-BC93A076AFF8@gmail.com> Message-ID: > ---> Dependencies to be installed: p5.12-app-ack Port p5.12-app-ack contains: /opt/local/bin/ack-5.12 ... Since multiple versions of p5.XX-app-ack can be installed, items in bin/ must be suffixed with the perl version number. Do you see ack-5.12 on your system? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From alexey.muranov at gmail.com Mon Jul 2 06:02:13 2012 From: alexey.muranov at gmail.com (Alexey Muranov) Date: Mon, 2 Jul 2012 15:02:13 +0200 Subject: cannot install ack In-Reply-To: References: <1AC1F807-9BA9-491F-B05D-BC93A076AFF8@gmail.com> Message-ID: <6BD4951D-36D7-40B4-A51D-F4F717F987F7@gmail.com> On 2 Jul 2012, at 14:50, Jeremy Lavergne wrote: >> ---> Dependencies to be installed: p5.12-app-ack > > Port p5.12-app-ack contains: > /opt/local/bin/ack-5.12 > ... > > Since multiple versions of p5.XX-app-ack can be installed, items in bin/ must be suffixed with the perl version number. Do you see ack-5.12 on your system? > Yes, i have /opt/local/bin/ack-5.12 ! Thank you. Can i make MacPorts create "ack" alias for this? From jeremy at lavergne.gotdns.org Mon Jul 2 06:06:57 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Mon, 2 Jul 2012 09:06:57 -0400 Subject: cannot install ack In-Reply-To: <6BD4951D-36D7-40B4-A51D-F4F717F987F7@gmail.com> References: <1AC1F807-9BA9-491F-B05D-BC93A076AFF8@gmail.com> <6BD4951D-36D7-40B4-A51D-F4F717F987F7@gmail.com> Message-ID: <5E97A2BF-3F4C-41A5-8920-609FA3B97518@lavergne.gotdns.org> > Yes, i have /opt/local/bin/ack-5.12 ! > Thank you. > Can i make MacPorts create "ack" alias for this? I'd not recommend having MacPorts do it: if you end up having more than one p5.XX-app-ack installed which one should be the correct one? Instead, I think you should create the alias. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From jonesc at hep.phy.cam.ac.uk Mon Jul 2 06:12:33 2012 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Mon, 02 Jul 2012 14:12:33 +0100 Subject: cannot install ack In-Reply-To: <5E97A2BF-3F4C-41A5-8920-609FA3B97518@lavergne.gotdns.org> References: <1AC1F807-9BA9-491F-B05D-BC93A076AFF8@gmail.com> <6BD4951D-36D7-40B4-A51D-F4F717F987F7@gmail.com> <5E97A2BF-3F4C-41A5-8920-609FA3B97518@lavergne.gotdns.org> Message-ID: <4FF19E41.9060404@hep.phy.cam.ac.uk> On 02/07/12 14:06, Jeremy Lavergne wrote: >> Yes, i have /opt/local/bin/ack-5.12 ! >> Thank you. >> Can i make MacPorts create "ack" alias for this? > > I'd not recommend having MacPorts do it: if you end up having more than one p5.XX-app-ack installed which one should be the correct one? Instead, I think you should create the alias. Why couldn't there be a 'port select' for this (maybe there is, I don't have my mac to hand to check) ? I don't see the difference between this case and others, like python of the various gcc versions, which have this option. Chris > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From jeremy at lavergne.gotdns.org Mon Jul 2 06:14:22 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Mon, 2 Jul 2012 09:14:22 -0400 Subject: cannot install ack In-Reply-To: <4FF19E41.9060404@hep.phy.cam.ac.uk> References: <1AC1F807-9BA9-491F-B05D-BC93A076AFF8@gmail.com> <6BD4951D-36D7-40B4-A51D-F4F717F987F7@gmail.com> <5E97A2BF-3F4C-41A5-8920-609FA3B97518@lavergne.gotdns.org> <4FF19E41.9060404@hep.phy.cam.ac.uk> Message-ID: <43BCB512-CC90-4221-8942-5D4CCEDD065D@lavergne.gotdns.org> > Why couldn't there be a 'port select' for this (maybe there is, I don't have my mac to hand to check) ? I don't see the difference between this case and others, like python of the various gcc versions, which have this option. Simply because no one has created a select for it. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From jonesc at hep.phy.cam.ac.uk Mon Jul 2 06:19:50 2012 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Mon, 02 Jul 2012 14:19:50 +0100 Subject: cannot install ack In-Reply-To: <43BCB512-CC90-4221-8942-5D4CCEDD065D@lavergne.gotdns.org> References: <1AC1F807-9BA9-491F-B05D-BC93A076AFF8@gmail.com> <6BD4951D-36D7-40B4-A51D-F4F717F987F7@gmail.com> <5E97A2BF-3F4C-41A5-8920-609FA3B97518@lavergne.gotdns.org> <4FF19E41.9060404@hep.phy.cam.ac.uk> <43BCB512-CC90-4221-8942-5D4CCEDD065D@lavergne.gotdns.org> Message-ID: <4FF19FF6.1090404@hep.phy.cam.ac.uk> On 02/07/12 14:14, Jeremy Lavergne wrote: >> Why couldn't there be a 'port select' for this (maybe there is, I don't have my mac to hand to check) ? I don't see the difference between this case and others, like python of the various gcc versions, which have this option. > > Simply because no one has created a select for it. OK. Your first reply implied there was a good reason not to have this option at all in this case, not that it simply didn't exist yet... Chris From jeremy at lavergne.gotdns.org Mon Jul 2 06:24:01 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Mon, 2 Jul 2012 09:24:01 -0400 Subject: cannot install ack In-Reply-To: <4FF19FF6.1090404@hep.phy.cam.ac.uk> References: <1AC1F807-9BA9-491F-B05D-BC93A076AFF8@gmail.com> <6BD4951D-36D7-40B4-A51D-F4F717F987F7@gmail.com> <5E97A2BF-3F4C-41A5-8920-609FA3B97518@lavergne.gotdns.org> <4FF19E41.9060404@hep.phy.cam.ac.uk> <43BCB512-CC90-4221-8942-5D4CCEDD065D@lavergne.gotdns.org> <4FF19FF6.1090404@hep.phy.cam.ac.uk> Message-ID: <90211952-6326-4A0C-A86A-F961DF976D45@lavergne.gotdns.org> > OK. Your first reply implied there was a good reason not to have this option at all in this case, not that it simply didn't exist yet... Well, it's not been done yet because every single port that can be installed using different versions of Perl would need a select created. At best we could automate this for everything in bin/, but again how do you pick which version is the one the user wants short of making the user running select on every single package. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From raramayo at gmail.com Mon Jul 2 06:24:57 2012 From: raramayo at gmail.com (Rodolfo Aramayo) Date: Mon, 2 Jul 2012 08:24:57 -0500 Subject: p5.14-Math-Random fails to install Message-ID: I am having trouble installing p5.14-Math-Random The tail of the log follows, the entire log is attached ########################################## /work/.CC_PRINT_OPTIONS' F90FLAGS='-pipe -O2 -m64' LDFLAGS='-L/opt/local/lib -arch x86_64' FCFLAGS='-pipe -O2 -m64' OBJC='/usr/bin/gcc-4.2' INSTALL='/usr/bin/install -c' PERL_AUTOINSTALL='--skipdeps' OBJCFLAGS='-pipe -O2 -arch x86_64' FFLAGS='-pipe -O2 -m64' CC_PRINT_OPTIONS='YES' CC='/usr/bin/gcc-4.2' :debug:configure Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-math-random/p5.14-math-random/work/Math-Random-0.71" && /opt/local/bin/perl5.14 Makefile.PL INSTALLDIRS=vendor' :debug:configure Executing command line: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-math-random/p5.14-math-random/work/Math-Random-0.71" && /opt/local/bin/perl5.14 Makefile.PL INSTALLDIRS=vendor :info:configure Use of qw(...) as parentheses is deprecated at /opt/local/lib/perl5/vendor_perl/5.14.2/ExtUtils/MM_Any.pm line 987. :info:configure Checking if your kit is complete... :info:configure Looks good :info:configure Writing Makefile for Math::Random :debug:configure Executing proc-post-org.macports.configure-configure-0 :debug:configure Privilege de-escalation not attempted as not running as root. :debug:build build phase started at Sun Jul 1 21:54:45 CDT 2012 :notice:build ---> Building p5.14-math-random :debug:build Executing org.macports.build (p5.14-math-random) :debug:build Environment: CPATH='/opt/local/include' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-math-random/p5.14-math-random/work/.CC_PRINT_OPTIONS' LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES' MACOSX_DEPLOYMENT_TARGET='10.6' :debug:build Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-math-random/p5.14-math-random/work/Math-Random-0.71" && /usr/bin/make -j2 -w all' :debug:build Executing command line: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-math-random/p5.14-math-random/work/Math-Random-0.71" && /usr/bin/make -j2 -w all :info:build make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-math-random/p5.14-math-random/work/Math-Random-0.71' :info:build /opt/local/bin/perl5.14 /opt/local/lib/perl5/vendor_perl/5.14.2/ExtUtils/xsubpp -typemap /opt/local/lib/perl5/5.14.2/ExtUtils/typemap Random.xs > Random.xsc && mv Random.xsc Random.c :info:build make: *** No rule to make target `/opt/local/lib/perl5/5.14.2/darwin-thread-multi-2level/CORE/cc_runtime.h', needed by `Random.o'. Stop. :info:build make: *** Waiting for unfinished jobs.... :info:build cp test2.pl blib/lib/Math/test2.pl :info:build cp Random.pm blib/lib/Math/Random.pm :info:build AutoSplitting blib/lib/Math/Random.pm (blib/lib/auto/Math/Random) :info:build cp test1.pl blib/lib/Math/test1.pl :info:build cp example.pl blib/lib/Math/example.pl :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-math-random/p5.14-math-random/work/Math-Random-0.71' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-math-random/p5.14-math-random/work/Math-Random-0.71" && /usr/bin/make -j2 -w all :info:build Exit code: 2 :error:build org.macports.build for port p5.14-math-random returned: command execution failed :debug:build Error code: CHILDSTATUS 20970 2 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: targets not executed for p5.14-math-random: org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Please see the log file for port p5.14-math-random for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-math-random/p5.14-math-random/main.log ########################################## Should this be reported as a bug? Thanks --R -------------- next part -------------- A non-text attachment was scrubbed... Name: p5.14-math-random_main.log Type: application/octet-stream Size: 16421 bytes Desc: not available URL: From larry.velazquez at gmail.com Mon Jul 2 06:30:43 2012 From: larry.velazquez at gmail.com (=?iso-8859-1?Q?Lawrence_Vel=E1zquez?=) Date: Mon, 2 Jul 2012 09:30:43 -0400 Subject: cannot install ack In-Reply-To: <90211952-6326-4A0C-A86A-F961DF976D45@lavergne.gotdns.org> References: <1AC1F807-9BA9-491F-B05D-BC93A076AFF8@gmail.com> <6BD4951D-36D7-40B4-A51D-F4F717F987F7@gmail.com> <5E97A2BF-3F4C-41A5-8920-609FA3B97518@lavergne.gotdns.org> <4FF19E41.9060404@hep.phy.cam.ac.uk> <43BCB512-CC90-4221-8942-5D4CCEDD065D@lavergne.gotdns.org> <4FF19FF6.1090404@hep.phy.cam.ac.uk> <90211952-6326-4A0C-A86A-F961DF976D45@lavergne.gotdns.org> Message-ID: <74640773-9D35-41DD-8210-4CD3E62D25ED@gmail.com> On Jul 2, 2012, at 9:24 a.m., Jeremy Lavergne wrote: >> OK. Your first reply implied there was a good reason not to have this option at all in this case, not that it simply didn't exist yet... > > Well, it's not been done yet because every single port that can be installed using different versions of Perl would need a select created. At best we could automate this for everything in bin/, but again how do you pick which version is the one the user wants short of making the user running select on every single package. Should ack even have subports? Is this something that people would want to install under different Perls? vq From jeremy at lavergne.gotdns.org Mon Jul 2 06:37:04 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Mon, 2 Jul 2012 09:37:04 -0400 Subject: cannot install ack In-Reply-To: <74640773-9D35-41DD-8210-4CD3E62D25ED@gmail.com> References: <1AC1F807-9BA9-491F-B05D-BC93A076AFF8@gmail.com> <6BD4951D-36D7-40B4-A51D-F4F717F987F7@gmail.com> <5E97A2BF-3F4C-41A5-8920-609FA3B97518@lavergne.gotdns.org> <4FF19E41.9060404@hep.phy.cam.ac.uk> <43BCB512-CC90-4221-8942-5D4CCEDD065D@lavergne.gotdns.org> <4FF19FF6.1090404@hep.phy.cam.ac.uk> <90211952-6326-4A0C-A86A-F961DF976D45@lavergne.gotdns.org> <74640773-9D35-41DD-8210-4CD3E62D25ED@gmail.com> Message-ID: > Should ack even have subports? Is this something that people would want to install under different Perls? That's sort of the problem: ack installs modules into the version-specific folders of perl. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From raramayo at gmail.com Mon Jul 2 06:54:30 2012 From: raramayo at gmail.com (Rodolfo Aramayo) Date: Mon, 2 Jul 2012 08:54:30 -0500 Subject: How to best clean old Perl installations directories Message-ID: I upgraded Perl from Perl 5.12 to 5.14, activated perl 5.14 and installed all my perl modules as 5.14 Question: Inside: /opt/local/lib/perl5/ I have the following directories: 5.12.2/ 5.12.3/ 5.12.4/ 5.14.2/ 5.8.9/ site_perl/ vendor_perl/ Why where the Perl 5.12 directories not removed? Is there a safe way or proper way to removed these directories? Thanks --R From raramayo at gmail.com Mon Jul 2 06:54:35 2012 From: raramayo at gmail.com (Rodolfo Aramayo) Date: Mon, 2 Jul 2012 08:54:35 -0500 Subject: p5.14-scalar-list-utils not "seen" during installation of Message-ID: I upgraded Perl from Perl 5.12 to 5.14, activated perl 5.14 and installed all my perl modules as 5.14 The process of migrating my Perl modules from 5.12 to 5.14, was done as follows: 1. deactivate p5.12 module 2. uninstall 5.12 module 3. install same 5.14 module I observed that the following modules failed during installation: Error: Processing of port glib-networking failed Error: Processing of port gnome-doc-utils failed Error: Processing of port gtk-doc failed Error: Processing of port gtksourceview failed Error: Processing of port gtkspell2 failed Error: Processing of port intltool failed Error: Processing of port libgsf failed Error: Processing of port librsvg failed Error: Processing of port libsoup failed Error: Processing of port libwnck failed Error: Processing of port libwpd failed Error: Processing of port libwpg failed Error: Processing of port rarian failed Error: Processing of port rednotebook failed Error: Processing of port rrdtool failed Error: Processing of port webkit-gtk failed Because they could not install: p5.12-scalar-list-utils @1.230.0_3 Even though the: p5.14-scalar-list-utils @1.230.0_3 is installed Should this behavior be reported as bugs? In the past I opened many tickets for similar behavior, many of those remain opened...despite the fact those problems were for the most part fixed... Thanks --R From pixilla at macports.org Mon Jul 2 07:36:48 2012 From: pixilla at macports.org (Bradley Giesbrecht) Date: Mon, 2 Jul 2012 07:36:48 -0700 Subject: Unable to install openjdk6 In-Reply-To: <4FF16D90.1090203@sunrise.ch> References: <4FF16D90.1090203@sunrise.ch> Message-ID: <340A721D-CE6F-48D2-85A1-9487ECF4876F@macports.org> On Jul 2, 2012, at 2:44 AM, Michael Parchet wrote: > Hello, > > I have tried to install openjdk6 but but I have the error below You might want to add yourself to the cc field for this ticket. https://trac.macports.org/ticket/34509 Regards, Bradley Giesbrecht (pixilla) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2763 bytes Desc: not available URL: From arno at alum.wpi.edu Mon Jul 2 07:43:15 2012 From: arno at alum.wpi.edu (Arno Hautala) Date: Mon, 2 Jul 2012 10:43:15 -0400 Subject: How to best clean old Perl installations directories In-Reply-To: References: Message-ID: On Mon, Jul 2, 2012 at 9:54 AM, Rodolfo Aramayo wrote: > > /opt/local/lib/perl5/ > I have the following directories: > > [...] > > Why where the Perl 5.12 directories not removed? > Is there a safe way or proper way to removed these directories? Are those directories empty? Do you still need any of the p5.12 ports? They wouldn't have been automatically removed by just installing the 5.14 versions. You should be able to see what ports are installed with: port installed p5.12-* You could then remove all of those, except for any that are deps of other installed ports with: port -p uninstall p5.12 The '-p' should keep the uninstall going even if there are some that can't be removed. In general, you should only interact with MacPorts installed files through the port command. It's typically best to not manually cleanup the opt directory. -- arno s hautala /-| arno at alum.wpi.edu pgp b2c9d448 From allbery.b at gmail.com Mon Jul 2 07:53:49 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Mon, 2 Jul 2012 10:53:49 -0400 Subject: xz & liblzma In-Reply-To: <4FF13DDC.4050905@gmail.com> References: <4FF13DDC.4050905@gmail.com> Message-ID: On Mon, Jul 2, 2012 at 2:21 AM, Phil Dobbin wrote: > `$ port outdated > The following installed ports are outdated: > liblzma 5.0.3_0 < 5.0.3_1 > ruby 1.8.7-p358_0 < 1.8.7-p370_0 > xz 5.0.3_0 < 5.0.4_0 ` > > so I went ahead & upgraded. Then I got: > > - ---> Deactivating liblzma @5.0.3_0 > - ---> Unable to deactivate liblzma @5.0.3_0, the following ports depend > on it: > - ---> ImageMagick @6.7.7-2_0+q16 > Warning: Deactivate forced. Proceeding despite dependencies.` > > so it looks like ImageMagick may have a problem. > I would expect that someone would have noticed this already if xz didn't replace whatever libraries ImageMagick uses with binary compatible versions. That someone would even have been you if you're up to date on MacPorts itself; rev-upgrade would finish up your upgrade run by scanning everything looking (among other things) for shared object breakage of the sort that might be introduced by this, and by default would have kicked off a rebuild of ImageMagick if that breakage had occurred. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From larry.velazquez at gmail.com Mon Jul 2 08:47:09 2012 From: larry.velazquez at gmail.com (=?iso-8859-1?Q?Lawrence_Vel=E1zquez?=) Date: Mon, 2 Jul 2012 11:47:09 -0400 Subject: p5.14-scalar-list-utils not "seen" during installation of In-Reply-To: References: Message-ID: <8BDF5746-9BA0-4DC5-8CD9-D05A8023DA57@gmail.com> On Jul 2, 2012, at 9:54 a.m., Rodolfo Aramayo wrote: > I observed that the following modules failed during installation: [...snip...] > Because they could not install: > > p5.12-scalar-list-utils @1.230.0_3 > > Even though the: > > p5.14-scalar-list-utils @1.230.0_3 > > is installed > > Should this behavior be reported as bugs? It's not really a bug. Those ports just depend on the Perl 5.12 subport and not the Perl 5.14 subport; in fact, I think most ports that require Perl modules currently depend on the 5.12 versions. Ports are not designed to accept arbitrary subports for dependencies; nor should they, since that behavior would result in unrepeatable builds. You can keep perl5.12 around independently of perl5.14, as well as the 5.12 versions of required dependencies. vq From gideon.simpson at gmail.com Mon Jul 2 08:48:43 2012 From: gideon.simpson at gmail.com (Gideon Simpson) Date: Mon, 2 Jul 2012 10:48:43 -0500 Subject: port problem upon update Message-ID: I did an "update outdated", and the following happened: gideon@~$ sudo port upgrade outdated ---> liblzma is replaced by xz ---> Computing dependencies for xz ---> Fetching archive for xz ---> Attempting to fetch xz-5.0.4_0.darwin_11.x86_64.tbz2 from http://packages.macports.org/xz ---> Attempting to fetch xz-5.0.4_0.darwin_11.x86_64.tbz2.rmd160 from http://packages.macports.org/xz ---> Installing xz @5.0.4_0 ---> Cleaning xz ---> Deactivating liblzma @5.0.3_0 ---> Unable to deactivate liblzma @5.0.3_0, the following ports depend on it: ---> ImageMagick @6.7.7-2_0+q16 Warning: Deactivate forced. Proceeding despite dependencies. ---> Cleaning liblzma ---> Computing dependencies for xz ---> Deactivating xz @5.0.3_0 ---> Cleaning xz ---> Activating xz @5.0.4_0 ---> Cleaning xz ---> Fetching archive for libpixman ---> Attempting to fetch libpixman-0.26.2_0.darwin_11.x86_64.tbz2 from http://packages.macports.org/libpixman ---> Attempting to fetch libpixman-0.26.2_0.darwin_11.x86_64.tbz2.rmd160 from http://packages.macports.org/libpixman ---> Installing libpixman @0.26.2_0 ---> Cleaning libpixman ---> Deactivating libpixman @0.26.0_0 ---> Cleaning libpixman ---> Activating libpixman @0.26.2_0 ---> Cleaning libpixman ---> Computing dependencies for metis ---> Fetching archive for metis ---> Attempting to fetch metis-5.0.2_1.darwin_11.x86_64.tbz2 from http://packages.macports.org/metis ---> Fetching distfiles for metis ---> Attempting to fetch metis-5.0.2.tar.gz from http://glaros.dtc.umn.edu/gkhome/fetch/sw/metis/ ---> Verifying checksum(s) for metis ---> Extracting metis ---> Applying patches to metis ---> Configuring metis ---> Building metis ---> Staging metis into destroot ---> Installing metis @5.0.2_1 ---> Cleaning metis ---> Deactivating metis @4.0.3_1 ---> Cleaning metis ---> Activating metis @5.0.2_1 ---> Cleaning metis ---> Computing dependencies for netcdf ---> Fetching archive for netcdf ---> Attempting to fetch netcdf-4.2.0_4+dap+netcdf4.darwin_11.x86_64.tbz2 from http://packages.macports.org/netcdf ---> Attempting to fetch netcdf-4.2.0_4+dap+netcdf4.darwin_11.x86_64.tbz2.rmd160 from http://packages.macports.org/netcdf ---> Installing netcdf @4.2.0_4+dap+netcdf4 ---> Cleaning netcdf ---> Computing dependencies for netcdf ---> Deactivating netcdf @4.2.0_3+dap+netcdf4 ---> Cleaning netcdf ---> Activating netcdf @4.2.0_4+dap+netcdf4 As of version 4.2 c++ and fortran interfaces are separate ports, netcdf-cxx and netcdf-fortran, respectively. ---> Cleaning netcdf ---> Computing dependencies for openjpeg ---> Fetching archive for openjpeg ---> Attempting to fetch openjpeg-1.5.0_2.darwin_11.x86_64.tbz2 from http://packages.macports.org/openjpeg ---> Attempting to fetch openjpeg-1.5.0_2.darwin_11.x86_64.tbz2.rmd160 from http://packages.macports.org/openjpeg ---> Installing openjpeg @1.5.0_2 ---> Cleaning openjpeg ---> Computing dependencies for openjpeg ---> Deactivating openjpeg @1.5.0_1 ---> Cleaning openjpeg ---> Activating openjpeg @1.5.0_2 ---> Cleaning openjpeg ---> Computing dependencies for ppl ---> Fetching archive for ppl ---> Attempting to fetch ppl-1.0_0.darwin_11.x86_64.tbz2 from http://packages.macports.org/ppl ---> Attempting to fetch ppl-1.0_0.darwin_11.x86_64.tbz2.rmd160 from http://packages.macports.org/ppl ---> Installing ppl @1.0_0 ---> Cleaning ppl ---> Computing dependencies for ppl ---> Deactivating ppl @0.12.1_2 ---> Cleaning ppl ---> Activating ppl @1.0_0 ---> Cleaning ppl ---> Updating database of binaries: 100.0% ---> Scanning binaries for linking errors: 100.0% ---> Found 6 broken file(s), matching files to ports ---> Found 1 broken port(s), determining rebuild order ---> Rebuilding in order gcc46 @4.6.3 ---> Computing dependencies for gcc46 ---> Cleaning gcc46 ---> Scanning binaries for linking errors: 100.0% ---> Found 6 broken file(s), matching files to ports ---> Found 1 broken port(s), determining rebuild order ---> Rebuilding in order gcc46 @4.6.3 ---> Computing dependencies for gcc46 ---> Cleaning gcc46 ---> Unable to uninstall gcc46 @4.6.3_2, the following ports depend on it: ---> fftw-3 @3.3.2_0+gcc46 ---> py27-scipy @0.10.1_1+gcc46 ---> qrupdate @1.1.2_1+atlas+gcc46 ---> openmpi @1.5.5_0+gcc46 Warning: Uninstall forced. Proceeding despite dependencies. ---> Deactivating gcc46 @4.6.3_2 ---> Unable to deactivate gcc46 @4.6.3_2, the following ports depend on it: ---> fftw-3 @3.3.2_0+gcc46 ---> py27-scipy @0.10.1_1+gcc46 ---> qrupdate @1.1.2_1+atlas+gcc46 ---> openmpi @1.5.5_0+gcc46 Warning: Deactivate forced. Proceeding despite dependencies. ---> Cleaning gcc46 ---> Uninstalling gcc46 @4.6.3_2 ---> Cleaning gcc46 ---> Computing dependencies for gcc46 ---> Fetching distfiles for gcc46 ---> Verifying checksum(s) for gcc46 ---> Extracting gcc46 ---> Configuring gcc46 Error: org.macports.configure for port gcc46 returned: configure failure: command execution failed Please see the log file for port gcc46 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/main.log ---> Scanning binaries for linking errors: 100.0% ---> Found 138 broken file(s), matching files to ports ---> Found 5 broken port(s), determining rebuild order ---> Rebuilding in order py27-scipy @0.10.1 +gcc46 atlas @3.9.76 +gcc46 qrupdate @1.1.2 +atlas+gcc46 openmpi @1.5.5 +gcc46 gsl @1.15 +gcc46 ---> Computing dependencies for py27-scipy ---> Dependencies to be installed: gcc46 ---> Configuring gcc46 Error: org.macports.configure for port gcc46 returned: configure failure: command execution failed Error: Failed to install gcc46 Please see the log file for port gcc46 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/main.log Error: The following dependencies were not installed: gcc46 ---> Cleaning atlas ---> Computing dependencies for qrupdate ---> Dependencies to be installed: gcc46 ---> Configuring gcc46 Error: org.macports.configure for port gcc46 returned: configure failure: command execution failed Error: Failed to install gcc46 Please see the log file for port gcc46 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/main.log Error: The following dependencies were not installed: gcc46 ---> Computing dependencies for openmpi ---> Dependencies to be installed: gcc46 ---> Configuring gcc46 Error: org.macports.configure for port gcc46 returned: configure failure: command execution failed Error: Failed to install gcc46 Please see the log file for port gcc46 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/main.log Error: The following dependencies were not installed: gcc46 ---> Cleaning gsl ---> Scanning binaries for linking errors: 100.0% ---> Found 138 broken file(s), matching files to ports ---> Found 5 broken port(s), determining rebuild order ---> Rebuilding in order py27-scipy @0.10.1 +gcc46 atlas @3.9.76 +gcc46 qrupdate @1.1.2 +atlas+gcc46 openmpi @1.5.5 +gcc46 gsl @1.15 +gcc46 ---> Computing dependencies for py27-scipy ---> Dependencies to be installed: gcc46 ---> Configuring gcc46 Error: org.macports.configure for port gcc46 returned: configure failure: command execution failed Error: Failed to install gcc46 Please see the log file for port gcc46 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/main.log Error: The following dependencies were not installed: gcc46 Error: Unable to upgrade port: 1 Error rebuilding py27-scipy while executing "error "Error rebuilding $portname"" (procedure "revupgrade_scanandrebuild" line 370) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "action_revupgrade $action $portlist $opts" (procedure "action_upgrade" line 24) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 95) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 4784) From raramayo at gmail.com Mon Jul 2 08:48:12 2012 From: raramayo at gmail.com (Rodolfo Aramayo) Date: Mon, 2 Jul 2012 10:48:12 -0500 Subject: How to best clean old Perl installations directories In-Reply-To: References: Message-ID: Thanks and Yes I only use the MacPorts command line --R On Mon, Jul 2, 2012 at 9:43 AM, Arno Hautala wrote: > On Mon, Jul 2, 2012 at 9:54 AM, Rodolfo Aramayo wrote: >> >> /opt/local/lib/perl5/ >> I have the following directories: >> >> [...] >> >> Why where the Perl 5.12 directories not removed? >> Is there a safe way or proper way to removed these directories? > > Are those directories empty? > Do you still need any of the p5.12 ports? They wouldn't have been > automatically removed by just installing the 5.14 versions. > > You should be able to see what ports are installed with: > port installed p5.12-* > > You could then remove all of those, except for any that are deps of > other installed ports with: > port -p uninstall p5.12 > > The '-p' should keep the uninstall going even if there are some that > can't be removed. > > In general, you should only interact with MacPorts installed files > through the port command. It's typically best to not manually cleanup > the opt directory. > > -- > arno s hautala /-| arno at alum.wpi.edu > > pgp b2c9d448 From larry.velazquez at gmail.com Mon Jul 2 08:51:35 2012 From: larry.velazquez at gmail.com (=?iso-8859-1?Q?Lawrence_Vel=E1zquez?=) Date: Mon, 2 Jul 2012 11:51:35 -0400 Subject: port problem upon update In-Reply-To: References: Message-ID: <7D8A44C1-D98A-4E2D-9258-B466355E48F2@gmail.com> On Jul 2, 2012, at 11:48 a.m., Gideon Simpson wrote: > Error: org.macports.configure for port gcc46 returned: configure failure: command execution failed > Error: Failed to install gcc46 > Please see the log file for port gcc46 for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/main.log Can you show us this file? vq From gideon.simpson at gmail.com Mon Jul 2 08:52:58 2012 From: gideon.simpson at gmail.com (Gideon Simpson) Date: Mon, 2 Jul 2012 10:52:58 -0500 Subject: port problem upon update In-Reply-To: <7D8A44C1-D98A-4E2D-9258-B466355E48F2@gmail.com> References: <7D8A44C1-D98A-4E2D-9258-B466355E48F2@gmail.com> Message-ID: <20C05D49-38B7-4BFB-AED2-25DA23698FCA@gmail.com> version:1 :debug:main epoch: in tree: 0 installed: 0 :debug:main gmp 5.0.4_1 exists in the ports tree :debug:main gmp 5.0.4_1 is the latest installed :debug:main gmp 5.0.4_1 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/gmp :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main No need to upgrade! gmp 5.0.4_1 >= gmp 5.0.4_1 :debug:main epoch: in tree: 0 installed: 0 :debug:main mpfr 3.1.0-p3_1 exists in the ports tree :debug:main mpfr 3.1.0-p3_1 is the latest installed :debug:main mpfr 3.1.0-p3_1 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/mpfr :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main No need to upgrade! mpfr 3.1.0-p3_1 >= mpfr 3.1.0-p3_1 :debug:main epoch: in tree: 0 installed: 0 :debug:main libiconv 1.14_0 exists in the ports tree :debug:main libiconv 1.14_0 is the latest installed :debug:main libiconv 1.14_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/textproc/libiconv :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main No need to upgrade! libiconv 1.14_0 >= libiconv 1.14_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main libmpc 0.9_0 exists in the ports tree :debug:main libmpc 0.9_0 is the latest installed :debug:main libmpc 0.9_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/libmpc :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main adding the default universal variant :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main No need to upgrade! libmpc 0.9_0 >= libmpc 0.9_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main ppl 1.0_0 exists in the ports tree :debug:main ppl 1.0_0 is the latest installed :debug:main ppl 1.0_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/ppl :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main No need to upgrade! ppl 1.0_0 >= ppl 1.0_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main glpk 4.47_0 exists in the ports tree :debug:main glpk 4.47_0 is the latest installed :debug:main glpk 4.47_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/glpk :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/archcheck-1.0.tcl :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main No need to upgrade! glpk 4.47_0 >= glpk 4.47_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main zlib 1.2.7_0 exists in the ports tree :debug:main zlib 1.2.7_0 is the latest installed :debug:main zlib 1.2.7_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/archivers/zlib :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/xcodeversion-1.0.tcl :debug:main adding the default universal variant :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main No need to upgrade! zlib 1.2.7_0 >= zlib 1.2.7_0 :debug:main epoch: in tree: 1 installed: 1 :debug:main cloog 0.16.3_2 exists in the ports tree :debug:main cloog 0.16.3_2 is the latest installed :debug:main cloog 0.16.3_2 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/cloog :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main No need to upgrade! cloog 0.16.3_2 >= cloog 0.16.3_2 :debug:main epoch: in tree: 1 installed: 1 :debug:main isl 0.07_2 exists in the ports tree :debug:main isl 0.07_2 is the latest installed :debug:main isl 0.07_2 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/isl :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main No need to upgrade! isl 0.07_2 >= isl 0.07_2 :debug:main epoch: in tree: 0 installed: 0 :debug:main gcc_select 0.1_6 exists in the ports tree :debug:main gcc_select 0.1_6 is the latest installed :debug:main gcc_select 0.1_6 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/sysutils/gcc_select :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl :debug:main universal_variant is false, so not adding the default universal variant :debug:main No need to upgrade! gcc_select 0.1_6 >= gcc_select 0.1_6 :debug:main epoch: in tree: 0 installed: 0 :debug:main ld64 128.2_4 exists in the ports tree :debug:main ld64 128.2_4 +llvm30 is the latest installed :debug:main ld64 128.2_4 +llvm30 is active :debug:main Merging existing variants '+llvm30' into variants :debug:main new fully merged portvariants: llvm30 + :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/ld64 :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main Executing variant llvm30 provides llvm30 :debug:main No need to upgrade! ld64 128.2_4 >= ld64 128.2_4 :debug:main epoch: in tree: 1 installed: 1 :debug:main llvm-3.0 3.0_5 exists in the ports tree :debug:main llvm-3.0 3.0_5 is the latest installed :debug:main llvm-3.0 3.0_5 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/lang/llvm-3.0 :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main No need to upgrade! llvm-3.0 3.0_5 >= llvm-3.0 3.0_5 :debug:main epoch: in tree: 0 installed: 0 :debug:main libffi 3.0.11_0 exists in the ports tree :debug:main libffi 3.0.11_0 is the latest installed :debug:main libffi 3.0.11_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/libffi :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main No need to upgrade! libffi 3.0.11_0 >= libffi 3.0.11_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main perl5 5.12.4_0 exists in the ports tree :debug:main perl5 5.12.4_0 +perl5_12 is the latest installed :debug:main perl5 5.12.4_0 +perl5_12 is active :debug:main Merging existing variants '+perl5_12' into variants :debug:main new fully merged portvariants: perl5_12 + :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/lang/perl5 :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main universal_variant is false, so not adding the default universal variant :debug:main Executing variant perl5_12 provides perl5_12 :debug:main No need to upgrade! perl5 5.12.4_0 >= perl5 5.12.4_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main perl5.12 5.12.4_1 exists in the ports tree :debug:main perl5.12 5.12.4_1 is the latest installed :debug:main perl5.12 5.12.4_1 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/lang/perl5.12 :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main adding the default universal variant :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main No need to upgrade! perl5.12 5.12.4_1 >= perl5.12 5.12.4_1 :debug:main epoch: in tree: 0 installed: 0 :debug:main gdbm 1.10_1 exists in the ports tree :debug:main gdbm 1.10_1 is the latest installed :debug:main gdbm 1.10_1 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/databases/gdbm :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main adding the default universal variant :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main No need to upgrade! gdbm 1.10_1 >= gdbm 1.10_1 :debug:main epoch: in tree: 0 installed: 0 :debug:main gettext 0.18.1.1_2 exists in the ports tree :debug:main gettext 0.18.1.1_2 is the latest installed :debug:main gettext 0.18.1.1_2 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/gettext :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/archcheck-1.0.tcl :debug:main universal variant already exists, so not adding the default one :debug:main No need to upgrade! gettext 0.18.1.1_2 >= gettext 0.18.1.1_2 :debug:main epoch: in tree: 0 installed: 0 :debug:main ncurses 5.9_1 exists in the ports tree :debug:main ncurses 5.9_1 is the latest installed :debug:main ncurses 5.9_1 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/ncurses :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main adding the default universal variant :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main No need to upgrade! ncurses 5.9_1 >= ncurses 5.9_1 :debug:main epoch: in tree: 0 installed: 0 :debug:main expat 2.1.0_0 exists in the ports tree :debug:main expat 2.1.0_0 is the latest installed :debug:main expat 2.1.0_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/textproc/expat :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main adding the default universal variant :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main No need to upgrade! expat 2.1.0_0 >= expat 2.1.0_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main llvm_select 0.2_0 exists in the ports tree :debug:main llvm_select 0.2_0 is the latest installed :debug:main llvm_select 0.2_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/sysutils/llvm_select :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl :debug:main universal_variant is false, so not adding the default universal variant :debug:main No need to upgrade! llvm_select 0.2_0 >= llvm_select 0.2_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main cctools 822_2 exists in the ports tree :debug:main cctools 822_2 +llvm30 is the latest installed :debug:main cctools 822_2 +llvm30 is active :debug:main Merging existing variants '+llvm30' into variants :debug:main new fully merged portvariants: llvm30 + :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/cctools :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main Executing variant llvm30 provides llvm30 :debug:main No need to upgrade! cctools 822_2 >= cctools 822_2 :debug:main epoch: in tree: 0 installed: 0 :debug:main cctools-headers 822_2 exists in the ports tree :debug:main cctools-headers 822_2 is the latest installed :debug:main cctools-headers 822_2 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/cctools-headers :debug:main OS darwin/11.4.0 (Mac OS X 10.7) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main universal_variant is false, so not adding the default universal variant :debug:main No need to upgrade! cctools-headers 822_2 >= cctools-headers 822_2 :msg:main ---> Computing dependencies for gcc46:info:main .:debug:main gcc46 has no conflicts :debug:main Searching for dependency: gmp :debug:main Found Dependency: receipt exists for gmp :debug:main Searching for dependency: mpfr :debug:main Found Dependency: receipt exists for mpfr :debug:main Searching for dependency: libiconv :debug:main Found Dependency: receipt exists for libiconv :debug:main Searching for dependency: libmpc :debug:main Found Dependency: receipt exists for libmpc :debug:main Searching for dependency: ppl :debug:main Found Dependency: receipt exists for ppl :debug:main Searching for dependency: cloog :debug:main Found Dependency: receipt exists for cloog :debug:main Searching for dependency: gcc_select :debug:main Found Dependency: receipt exists for gcc_select :debug:main Searching for dependency: ld64 :debug:main Found Dependency: receipt exists for ld64 :debug:main Searching for dependency: cctools :debug:main Found Dependency: receipt exists for cctools :msg:main :debug:main Executing org.macports.main (gcc46) :debug:main changing euid/egid - current euid: 0 - current egid: 0 :debug:main egid changed to: 501 :debug:main euid changed to: 502 :debug:main Skipping completed org.macports.archivefetch (gcc46) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.fetch (gcc46) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.checksum (gcc46) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.extract (gcc46) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.patch (gcc46) :debug:main Privilege de-escalation not attempted as not running as root. :debug:configure configure phase started at Mon Jul 2 10:45:19 CDT 2012 :notice:configure ---> Configuring gcc46 :debug:configure Using compiler 'Mac OS X clang' :debug:configure Executing proc-pre-org.macports.configure-configure-0 :debug:configure Executing org.macports.configure (gcc46) :debug:configure Environment: CPATH='/opt/local/include' CXXFLAGS='-pipe -O2' CPPFLAGS='-I/opt/local/include' CFLAGS='-pipe -O2' AS_FOR_TARGET='/opt/local/bin/as' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.7' CXX='/usr/bin/clang++' CPP='/usr/bin/clang -E' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/work/.CC_PRINT_OPTIONS' F90FLAGS='-pipe -O2 -m64' LD_FOR_TARGET='/opt/local/bin/ld' RANLIB_FOR_TARGET='/opt/local/bin/ranlib' LDFLAGS='-L/opt/local/lib' OBJDUMP_FOR_TARGET='/opt/local/bin/objdump' OTOOL='/opt/local/bin/otool' FCFLAGS='-pipe -O2 -m64' OBJC='/usr/bin/clang' INSTALL='/usr/bin/install -c' AR_FOR_TARGET='/opt/local/bin/ar' NM_FOR_TARGET='/opt/local/bin/nm' FFLAGS='-pipe -O2 -m64' OBJCFLAGS='-pipe -O2' CC_PRINT_OPTIONS='YES' STRIP_FOR_TARGET='/opt/local/bin/strip' CC='/usr/bin/clang -arch x86_64' OTOOL64='/opt/local/bin/otool' :debug:configure Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/work/build" && ../gcc-4.6.3/configure --prefix=/opt/local --build=x86_64-apple-darwin11 --enable-languages=c,c++,objc,obj-c++,lto,fortran --libdir=/opt/local/lib/gcc46 --includedir=/opt/local/include/gcc46 --infodir=/opt/local/share/info --mandir=/opt/local/share/man --datarootdir=/opt/local/share/gcc-4.6 --with-local-prefix=/opt/local --with-libiconv-prefix=/opt/local --with-system-zlib --disable-nls --program-suffix=-mp-4.6 --with-gxx-include-dir=/opt/local/include/gcc46/c++/ --with-gmp=/opt/local --with-mpfr=/opt/local --with-mpc=/opt/local --with-ppl=/opt/local --with-cloog=/opt/local --enable-cloog-backend=isl --enable-stage1-checking --disable-multilib --enable-lto --with-as=/opt/local/bin/as --with-ld=/opt/local/bin/ld --with-ar=/opt/local/bin/ar --with-bugurl=https://trac.macports.org/newticket --with-pkgversion="MacPorts gcc46 4.6.3_2"' :debug:configure Executing command line: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/work/build" && ../gcc-4.6.3/configure --prefix=/opt/local --build=x86_64-apple-darwin11 --enable-languages=c,c++,objc,obj-c++,lto,fortran --libdir=/opt/local/lib/gcc46 --includedir=/opt/local/include/gcc46 --infodir=/opt/local/share/info --mandir=/opt/local/share/man --datarootdir=/opt/local/share/gcc-4.6 --with-local-prefix=/opt/local --with-libiconv-prefix=/opt/local --with-system-zlib --disable-nls --program-suffix=-mp-4.6 --with-gxx-include-dir=/opt/local/include/gcc46/c++/ --with-gmp=/opt/local --with-mpfr=/opt/local --with-mpc=/opt/local --with-ppl=/opt/local --with-cloog=/opt/local --enable-cloog-backend=isl --enable-stage1-checking --disable-multilib --enable-lto --with-as=/opt/local/bin/as --with-ld=/opt/local/bin/ld --with-ar=/opt/local/bin/ar --with-bugurl=https://trac.macports.org/newticket --with-pkgversion="MacPorts gcc46 4.6.3_2" :info:configure checking build system type... x86_64-apple-darwin11 :info:configure checking host system type... x86_64-apple-darwin11 :info:configure checking target system type... x86_64-apple-darwin11 :info:configure checking for a BSD-compatible install... /usr/bin/install -c :info:configure checking whether ln works... yes :info:configure checking whether ln -s works... yes :info:configure checking for a sed that does not truncate output... /opt/local/bin/gsed :info:configure checking for gawk... gawk :info:configure checking for gcc... /usr/bin/clang -arch x86_64 :info:configure checking for C compiler default output file name... a.out :info:configure checking whether the C compiler works... yes :info:configure checking whether we are cross compiling... no :info:configure checking for suffix of executables... :info:configure checking for suffix of object files... o :info:configure checking whether we are using the GNU C compiler... yes :info:configure checking whether /usr/bin/clang -arch x86_64 accepts -g... yes :info:configure checking for /usr/bin/clang -arch x86_64 option to accept ISO C89... none needed :info:configure checking whether we are using the GNU C++ compiler... yes :info:configure checking whether /usr/bin/clang++ accepts -g... yes :info:configure checking for gnatbind... no :info:configure checking for gnatmake... no :info:configure checking whether compiler driver understands Ada... no :info:configure checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1 $$f2 :info:configure checking for objdir... .libs :info:configure checking for the correct version of gmp.h... yes :info:configure checking for the correct version of mpfr.h... yes :info:configure checking for the correct version of mpc.h... yes :info:configure checking for the correct version of the gmp/mpfr/mpc libraries... yes :info:configure checking for PWL_handle_timeout in -lpwl... no :info:configure checking for version 0.11 (revision 0 or later) of PPL... no :info:configure configure: error: Unable to find a usable PPL. See config.log for details. :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/work/build" && ../gcc-4.6.3/configure --prefix=/opt/local --build=x86_64-apple-darwin11 --enable-languages=c,c++,objc,obj-c++,lto,fortran --libdir=/opt/local/lib/gcc46 --includedir=/opt/local/include/gcc46 --infodir=/opt/local/share/info --mandir=/opt/local/share/man --datarootdir=/opt/local/share/gcc-4.6 --with-local-prefix=/opt/local --with-libiconv-prefix=/opt/local --with-system-zlib --disable-nls --program-suffix=-mp-4.6 --with-gxx-include-dir=/opt/local/include/gcc46/c++/ --with-gmp=/opt/local --with-mpfr=/opt/local --with-mpc=/opt/local --with-ppl=/opt/local --with-cloog=/opt/local --enable-cloog-backend=isl --enable-stage1-checking --disable-multilib --enable-lto --with-as=/opt/local/bin/as --with-ld=/opt/local/bin/ld --with-ar=/opt/local/bin/ar --with-bugurl=https://trac.macports.org/newticket --with-pkgversion="MacPorts gcc46 4.6.3_2" :info:configure Exit code: 1 :error:configure org.macports.configure for port gcc46 returned: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed while executing "$procedure $targetname" :info:configure Warning: targets not executed for gcc46: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install :notice:configure Please see the log file for port gcc46 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/main.log -gideon On Jul 2, 2012, at 10:51 AM, Lawrence Vel?zquez wrote: > On Jul 2, 2012, at 11:48 a.m., Gideon Simpson wrote: > >> Error: org.macports.configure for port gcc46 returned: configure failure: command execution failed >> Error: Failed to install gcc46 >> Please see the log file for port gcc46 for details: >> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc46/gcc46/main.log > > Can you show us this file? > > vq > From jdlong at gmail.com Mon Jul 2 11:03:08 2012 From: jdlong at gmail.com (James Long) Date: Mon, 2 Jul 2012 15:03:08 -0300 Subject: how long for changes to propagate in macports? Message-ID: My apologies if this is in a FAQ. I looked but was unable to find the answer. How long does it normally take for changes to ports to propagate from check in to being able to be updated via selfupdate? I'm asking because I am in need of version 0.8.0 of py-pandas which appears to have been added to macports ~5 hours ago: https://trac.macports.org/changeset/94919 However when I do a selfupdate then an `upgrade outdated` macports thinks everything is up to date. I'm assuming this is because the changeset has not propagated into the rsync directory or something like that. Any tips to help me understand the process would be greatly appreciated. Thanks to stromnov and all the other volunteers who keep macports up to date so quickly! -J From larry.velazquez at gmail.com Mon Jul 2 11:36:16 2012 From: larry.velazquez at gmail.com (=?iso-8859-1?Q?Lawrence_Vel=E1zquez?=) Date: Mon, 2 Jul 2012 14:36:16 -0400 Subject: how long for changes to propagate in macports? In-Reply-To: References: Message-ID: On Jul 2, 2012, at 2:03 p.m., James Long wrote: > How long does it normally take for changes to ports to propagate from > check in to being able to be updated via selfupdate? I think it's usually less than an hour. A couple of hours at most. Someone more knowledgeable should correct me on this. > I'm asking because I am in need of version 0.8.0 of py-pandas which > appears to have been added to macports ~5 hours ago: > https://trac.macports.org/changeset/94919 > > However when I do a selfupdate then an `upgrade outdated` macports > thinks everything is up to date. Hm, I just did a selfupdate, and it looks like it's there: % port list py-pandas py-pandas @0.8.0 python/py-pandas vq From mark.brethen at gmail.com Mon Jul 2 11:45:31 2012 From: mark.brethen at gmail.com (Mark Brethen) Date: Mon, 2 Jul 2012 13:45:31 -0500 Subject: how long for changes to propagate in macports? In-Reply-To: References: Message-ID: <248132B8-B9D2-41CB-888F-81AFDB163618@gmail.com> I submitted a revised Portfile for reduce algebra months ago. It still has not been committed. ### -Mark On Jul 2, 2012, at 1:36 PM, Lawrence Vel?zquez wrote: > On Jul 2, 2012, at 2:03 p.m., James Long wrote: > >> How long does it normally take for changes to ports to propagate from >> check in to being able to be updated via selfupdate? > > I think it's usually less than an hour. A couple of hours at most. Someone more knowledgeable should correct me on this. > >> I'm asking because I am in need of version 0.8.0 of py-pandas which >> appears to have been added to macports ~5 hours ago: >> https://trac.macports.org/changeset/94919 >> >> However when I do a selfupdate then an `upgrade outdated` macports >> thinks everything is up to date. > > Hm, I just did a selfupdate, and it looks like it's there: > > % port list py-pandas > py-pandas @0.8.0 python/py-pandas > > > vq > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From allbery.b at gmail.com Mon Jul 2 11:59:07 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Mon, 2 Jul 2012 14:59:07 -0400 Subject: how long for changes to propagate in macports? In-Reply-To: <248132B8-B9D2-41CB-888F-81AFDB163618@gmail.com> References: <248132B8-B9D2-41CB-888F-81AFDB163618@gmail.com> Message-ID: On Mon, Jul 2, 2012 at 2:45 PM, Mark Brethen wrote: > I submitted a revised Portfile for reduce algebra months ago. It still has > not been committed. > That's a different issue; if it has a maintainer you should cc: them on the ticket so they notice that someone has done something, if it's nomaintainer / openmaintainer then your best bet is to comment in IRC or here on the list, since by definition nobody is paying any attention to tickets against the port. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdlong at gmail.com Mon Jul 2 12:14:34 2012 From: jdlong at gmail.com (James Long) Date: Mon, 2 Jul 2012 16:14:34 -0300 Subject: Fwd: how long for changes to propagate in macports? In-Reply-To: References: Message-ID: Meant for that to go to the list, not Lawrence directly. Problem solved. Thank you all for your help! -J ---------- Forwarded message ---------- From: James Long Date: Mon, Jul 2, 2012 at 4:13 PM Subject: Re: how long for changes to propagate in macports? To: Lawrence Vel?zquez After I was armed with the knowledge that I should have it by now, I dug a little deeper. I discovered that I had molested my sources.conf in an earlier attempt to work around my work's draconian blocking of rsync. After geting rsync approval I had then not reverted to the default sources.conf. So, as with most issues, this one was user induced. Thank you all for the fast responses! -J On Mon, Jul 2, 2012 at 3:36 PM, Lawrence Vel?zquez wrote: > On Jul 2, 2012, at 2:03 p.m., James Long wrote: > >> How long does it normally take for changes to ports to propagate from >> check in to being able to be updated via selfupdate? > > I think it's usually less than an hour. A couple of hours at most. Someone more knowledgeable should correct me on this. > >> I'm asking because I am in need of version 0.8.0 of py-pandas which >> appears to have been added to macports ~5 hours ago: >> https://trac.macports.org/changeset/94919 >> >> However when I do a selfupdate then an `upgrade outdated` macports >> thinks everything is up to date. > > Hm, I just did a selfupdate, and it looks like it's there: > > % port list py-pandas > py-pandas @0.8.0 python/py-pandas > > > vq > From raramayo at gmail.com Mon Jul 2 12:38:21 2012 From: raramayo at gmail.com (Rodolfo Aramayo) Date: Mon, 2 Jul 2012 14:38:21 -0500 Subject: gcc46 fails to configure Message-ID: GCC46 is consistently failing to configure in more than one computer Log file is attached Should I file this as a bug? Thanks --R -------------- next part -------------- A non-text attachment was scrubbed... Name: gcc46_main.log Type: application/octet-stream Size: 11269 bytes Desc: not available URL: From eborisch at macports.org Mon Jul 2 13:15:01 2012 From: eborisch at macports.org (Eric A. Borisch) Date: Mon, 2 Jul 2012 15:15:01 -0500 Subject: gcc46 fails to configure In-Reply-To: References: Message-ID: On Mon, Jul 2, 2012 at 2:38 PM, Rodolfo Aramayo wrote: > GCC46 is consistently failing to configure in more than one computer > > Log file is attached > > Should I file this as a bug? It already is: http://trac.macports.org/ticket/35057 It is likely that gcc46 and gcc47 need the same treatment gcc48 received in http://trac.macports.org/changeset/94941. -Eric From raramayo at gmail.com Mon Jul 2 13:17:57 2012 From: raramayo at gmail.com (Rodolfo Aramayo) Date: Mon, 2 Jul 2012 15:17:57 -0500 Subject: gcc46 fails to configure In-Reply-To: References: Message-ID: Thanks --R On Mon, Jul 2, 2012 at 3:15 PM, Eric A. Borisch wrote: > On Mon, Jul 2, 2012 at 2:38 PM, Rodolfo Aramayo wrote: >> GCC46 is consistently failing to configure in more than one computer >> >> Log file is attached >> >> Should I file this as a bug? > > It already is: http://trac.macports.org/ticket/35057 > > It is likely that gcc46 and gcc47 need the same treatment gcc48 > received in http://trac.macports.org/changeset/94941. > > -Eric From phildobbin at gmail.com Mon Jul 2 14:10:29 2012 From: phildobbin at gmail.com (Phil Dobbin) Date: Mon, 02 Jul 2012 22:10:29 +0100 Subject: xz & liblzma In-Reply-To: References: <4FF13DDC.4050905@gmail.com> Message-ID: <4FF20E45.5040103@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/07/2012 15:53, Brandon Allbery wrote: > On Mon, Jul 2, 2012 at 2:21 AM, Phil Dobbin > wrote: > > `$ port outdated The following installed ports are outdated: > liblzma 5.0.3_0 < 5.0.3_1 ruby > 1.8.7-p358_0 < 1.8.7-p370_0 xz 5.0.3_0 > < 5.0.4_0 ` > > so I went ahead & upgraded. Then I got: > > - ---> Deactivating liblzma @5.0.3_0 - ---> Unable to deactivate > liblzma @5.0.3_0, the following ports depend on it: - ---> > ImageMagick @6.7.7-2_0+q16 Warning: Deactivate forced. Proceeding > despite dependencies.` > > so it looks like ImageMagick may have a problem. > > > I would expect that someone would have noticed this already if xz > didn't replace whatever libraries ImageMagick uses with binary > compatible versions. > > That someone would even have been you if you're up to date on > MacPorts itself; rev-upgrade would finish up your upgrade run by > scanning everything looking (among other things) for shared object > breakage of the sort that might be introduced by this, and by > default would have kicked off a rebuild of ImageMagick if that > breakage had occurred. Hi, Brandon. Guess so. All's quiet on the subject so I reckon I'll clean up & go on about my business. Thanks, Phil.. - -- But masters, remember that I am an ass. Though it be not written down, yet forget not that I am an ass. Wm. Shakespeare - Much Ado About Nothing -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: ?auto-key-locate cert pka ldap hkp://keys.gnupg.net Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJP8g5CAAoJEKpMeDHWT5ADQAQH/RoggbBL50uyROSAHvGXHCBT 7Vab5ytgtI6RJNeaxvxRaLr/d3v0WOvtEieWu5vmpL+yD6+SaAv/HkvfRFxYzU+8 5EZDutV+OUszy46wvkdkguZKW7q8YDvJRkPfcyHsp2AkzkcKSoLnzVi3JBJHoAt4 ygn+GO8R/MKfGox7F4XX2CPCnAygnDk4pN6Hf+dBvWvsM+MLTto4iQw1w1XNUsg7 ibfBQbKsJ0ki1mnqr7RJM4TUr0coA6N3TJ1jxMt3ev7jGabUUKp96Sekz+xRZ6P2 iNVADpng7JMUUGs0pw4ekSuwElzHLMjM3So57RKD4lJiwBJCDx6WhcxsBWALDn0= =ZAvE -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3878 bytes Desc: S/MIME Cryptographic Signature URL: From mww at macports.org Mon Jul 2 14:25:25 2012 From: mww at macports.org (=?iso-8859-1?Q?=22Markus_W=2E_Wei=DFmann=22?=) Date: Mon, 2 Jul 2012 23:25:25 +0200 Subject: gcc46 fails to configure In-Reply-To: References: Message-ID: <0E568FEE-25D9-4F50-87A6-F6B451545620@macports.org> Thanks for the report! -Markus On 2 Jul 2012, at 22:17, Rodolfo Aramayo wrote: > Thanks > > --R > > On Mon, Jul 2, 2012 at 3:15 PM, Eric A. Borisch wrote: >> On Mon, Jul 2, 2012 at 2:38 PM, Rodolfo Aramayo wrote: >>> GCC46 is consistently failing to configure in more than one computer >>> >>> Log file is attached >>> >>> Should I file this as a bug? >> >> It already is: http://trac.macports.org/ticket/35057 >> >> It is likely that gcc46 and gcc47 need the same treatment gcc48 >> received in http://trac.macports.org/changeset/94941. >> >> -Eric From artemiog at mac.com Mon Jul 2 15:19:44 2012 From: artemiog at mac.com (Artemio Gonzalez Lopez) Date: Tue, 03 Jul 2012 00:19:44 +0200 Subject: p5.12-locale-gettext fails to compile Message-ID: <936F603E-AC1B-4E65-87DE-B05CFF4B5EC6@mac.com> When trying to build p5.12-locale-gettext with Xcode 4.5 Developer Preview 2, compilation fails with the following error message: DEBUG: Environment: CPATH='/opt/local/include' CFLAGS='-pipe -O2 -arch x86_64' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-pipe -O2 -arch x86_64' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.8' CXX='/usr/bin/llvm-g++-4.2' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-locale-gettext/p5.12-locale-gettext/work/.CC_PRINT_OPTIONS' F90FLAGS='-pipe -O2 -m64' LDFLAGS='-L/opt/local/lib -arch x86_64' FCFLAGS='-pipe -O2 -m64' OBJC='/usr/bin/llvm-gcc-4.2' INSTALL='/usr/bin/install -c' PERL_AUTOINSTALL='--skipdeps' OBJCFLAGS='-pipe -O2 -arch x86_64' FFLAGS='-pipe -O2 -m64' CC_PRINT_OPTIONS='YES' CC='/usr/bin/llvm-gcc-4.2 -O2 -L/opt/local/lib -arch x86_64' Error: org.macports.configure for port p5.12-locale-gettext returned: configure failure: list element in braces followed by """ instead of space DEBUG: Error code: NONE DEBUG: Backtrace: configure failure: list element in braces followed by """ instead of space while executing "$procedure $targetname" Warning: targets not executed for p5.12-locale-gettext: org.macports.install org.macports.configure org.macports.build org.macports.destroot Please see the log file for port p5.12-locale-gettext for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-locale-gettext/p5.12-locale-gettext/main.log DEBUG: can not find channel named "debuglog" while executing "tcl::puts debuglog {DEBUG: Starting logging for p5.12-locale-gettext}" invoked from within "catch "tcl::puts $args"" Error: Unable to upgrade port: 1 I know Xcode 4.5 is rather cutting edge, but if somebody else has experienced this problem and has any ideas as to its cause I would appreciate any pointers, suggestions or workarounds. Artemio Artemio Gonzalez Lopez artemiog at me.com From jeremy at lavergne.gotdns.org Mon Jul 2 15:22:02 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Mon, 02 Jul 2012 18:22:02 -0400 Subject: p5.12-locale-gettext fails to compile In-Reply-To: <936F603E-AC1B-4E65-87DE-B05CFF4B5EC6@mac.com> References: <936F603E-AC1B-4E65-87DE-B05CFF4B5EC6@mac.com> Message-ID: <5d0a867e-d697-4bde-a729-dc6c9328c107@email.android.com> This one is happening with the current xcode as well. Artemio Gonzalez Lopez wrote: >When trying to build p5.12-locale-gettext with Xcode 4.5 Developer >Preview 2, compilation fails with the following error message: > >DEBUG: Environment: CPATH='/opt/local/include' CFLAGS='-pipe -O2 -arch >x86_64' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-pipe -O2 -arch >x86_64' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.8' >CXX='/usr/bin/llvm-g++-4.2' >CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-locale-gettext/p5.12-locale-gettext/work/.CC_PRINT_OPTIONS' >F90FLAGS='-pipe -O2 -m64' LDFLAGS='-L/opt/local/lib -arch x86_64' >FCFLAGS='-pipe -O2 -m64' OBJC='/usr/bin/llvm-gcc-4.2' >INSTALL='/usr/bin/install -c' PERL_AUTOINSTALL='--skipdeps' >OBJCFLAGS='-pipe -O2 -arch x86_64' FFLAGS='-pipe -O2 -m64' >CC_PRINT_OPTIONS='YES' CC='/usr/bin/llvm-gcc-4.2 -O2 -L/opt/local/lib >-arch x86_64' >Error: org.macports.configure for port p5.12-locale-gettext returned: >configure failure: list element in braces followed by """ instead of >space >DEBUG: Error code: NONE >DEBUG: Backtrace: configure failure: list element in braces followed by >""" instead of space > while executing >"$procedure $targetname" >Warning: targets not executed for p5.12-locale-gettext: >org.macports.install org.macports.configure org.macports.build >org.macports.destroot >Please see the log file for port p5.12-locale-gettext for details: >/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_perl_p5-locale-gettext/p5.12-locale-gettext/main.log >DEBUG: can not find channel named "debuglog" > while executing >"tcl::puts debuglog {DEBUG: Starting logging for p5.12-locale-gettext}" > invoked from within >"catch "tcl::puts $args"" >Error: Unable to upgrade port: 1 > >I know Xcode 4.5 is rather cutting edge, but if somebody else has >experienced this problem and has any ideas as to its cause I would >appreciate any pointers, suggestions or workarounds. > >Artemio > > >Artemio Gonzalez Lopez >artemiog at me.com > > > >_______________________________________________ >macports-users mailing list >macports-users at lists.macosforge.org >http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From ryandesign at macports.org Mon Jul 2 17:14:37 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Jul 2012 19:14:37 -0500 Subject: how long for changes to propagate in macports? In-Reply-To: References: Message-ID: <0A2A063D-80C5-4D7C-93E2-02AC2E1AA198@macports.org> On Jul 2, 2012, at 13:03, James Long wrote: > How long does it normally take for changes to ports to propagate from > check in to being able to be updated via selfupdate? The rsync server syncs with the Subversion server every 30 minutes. From ryandesign at macports.org Mon Jul 2 17:16:56 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Jul 2012 19:16:56 -0500 Subject: port problem upon update In-Reply-To: References: Message-ID: <3B3C6967-9461-4103-92ED-9517E75BA154@macports.org> On Jul 2, 2012, at 10:48, Gideon Simpson wrote: > ---> Configuring gcc46 > Error: org.macports.configure for port gcc46 returned: configure failure: command execution failed It has been fixed: https://trac.macports.org/ticket/35057 From ryandesign at macports.org Mon Jul 2 17:21:24 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Jul 2012 19:21:24 -0500 Subject: cannot install ack In-Reply-To: <74640773-9D35-41DD-8210-4CD3E62D25ED@gmail.com> References: <1AC1F807-9BA9-491F-B05D-BC93A076AFF8@gmail.com> <6BD4951D-36D7-40B4-A51D-F4F717F987F7@gmail.com> <5E97A2BF-3F4C-41A5-8920-609FA3B97518@lavergne.gotdns.org> <4FF19E41.9060404@hep.phy.cam.ac.uk> <43BCB512-CC90-4221-8942-5D4CCEDD065D@lavergne.gotdns.org> <4FF19FF6.1090404@hep.phy.cam.ac.uk> <90211952-6326-4A0C-A86A-F961DF976D45@lavergne.gotdns.org> <74640773-9D35-41DD-8210-4CD3E62D25ED@gmail.com> Message-ID: <0AB09F69-DA94-468E-978C-9372FB698DCF@macports.org> On Jul 2, 2012, at 08:30, Lawrence Vel?zquez wrote: > Should ack even have subports? Is this something that people would want to install under different Perls? You should ask the maintainer of the port. If there's no pressing need to have it available to different perl versions (for example, if there are no other perl modules that depend on it -- and I don't see any) then we can certainly change it. From ryandesign at macports.org Mon Jul 2 17:52:16 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Jul 2012 19:52:16 -0500 Subject: p5.14-Math-Random fails to install In-Reply-To: References: Message-ID: On Jul 2, 2012, at 08:24, Rodolfo Aramayo wrote: > I am having trouble installing p5.14-Math-Random > :info:build make: *** No rule to make target > `/opt/local/lib/perl5/5.14.2/darwin-thread-multi-2level/CORE/cc_runtime.h', > needed by `Random.o'. Stop. It builds fine for me... are you sure your other ports are up to date? sudo port selfupdate sudo port upgrade outdated From ryandesign at macports.org Mon Jul 2 17:58:57 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Jul 2012 19:58:57 -0500 Subject: help with trouble with pango, etc In-Reply-To: References: Message-ID: We should keep the discussion on the list. Please use Reply All when you reply. On Jul 2, 2012, at 07:32, Comer Duncan wrote: > Hi Ryan, > > Ok, I found the variants.conf file. I must have changed it a year and a half ago when I first got the macbook pro, but did not recall doing it. My fault. I list below the current contents of the file: > > variants.conf: > > # To specify global variants to use for all port builds, > # customize this file to list variant settings you want. > # > # Be sure to uncomment/define the variants_conf setting > # in the system wide ${prefix}/etc/macports/macports.conf > # file or in your personal ~/.macports/macports.conf to > # point to this file to enable this feature. > # > # Any variants specified here that are not supported by > # a port will just be ignored. Multiple variants can be > # specified per line, or one per line is also allowed. > # > # Example: > # +ipv6 +no_x11 > +no_x11 > -x11 > +quartz > > I guess I must have been induced to modify the default (empty) variants.conf file because of some instruction from someone as I was then new to macports. So, my question is what is the best way forward? I could just rename this file so nothing would be read as a change instruction when getting the port or I can leave in one option? Which one? Maybe the above stuff is inconsistent even? > > Thanks for your help. What you have in the variants.conf file above is consistent with wanting to use Quartz and not X11. As I said before, you should decide whether you want to use Quartz or X11 before installing any ports; based on your above variants.conf, you apparently decided before you installed any ports that you wanted to use Quartz and not X11. That's fine. Changing your mind about that now would mean needing to first uninstall all ports you have installed, then reinstalling them after you make the change. From jam at tigger.ws Mon Jul 2 18:10:47 2012 From: jam at tigger.ws (James Linder) Date: Tue, 3 Jul 2012 09:10:47 +0800 Subject: Problem installing rpm using macports In-Reply-To: References: Message-ID: <10223174-4A0A-400C-A030-F580C924823D@tigger.ws> On 02/07/2012, at 10:00 PM, macports-users-request at lists.macosforge.org wrote: >> If you want to build rpm for xxx distro eg CentOS5 then you need to build on CentOS5. >> [..] >> Save yourself the heart ache and believe that you cannot cross build rpm. ('course you can, but you really have to be on the ball to do that). > > Have a look at: > https://build.opensuse.org/ > http://www.open-build-service.org/ Indeed, and I don't know what they do, but I'd bet my lunch money that they have a farm of VMs and do not try to cross build. James From raramayo at gmail.com Mon Jul 2 18:16:08 2012 From: raramayo at gmail.com (Rodolfo Aramayo) Date: Mon, 2 Jul 2012 20:16:08 -0500 Subject: p5.14-Math-Random fails to install In-Reply-To: References: Message-ID: ohh yesss they are And this happens on a fresh MacPorts install --R On Mon, Jul 2, 2012 at 7:52 PM, Ryan Schmidt wrote: > > On Jul 2, 2012, at 08:24, Rodolfo Aramayo wrote: > >> I am having trouble installing p5.14-Math-Random > >> :info:build make: *** No rule to make target >> `/opt/local/lib/perl5/5.14.2/darwin-thread-multi-2level/CORE/cc_runtime.h', >> needed by `Random.o'. Stop. > > It builds fine for me... are you sure your other ports are up to date? > > sudo port selfupdate > sudo port upgrade outdated > > From gideon.simpson at gmail.com Mon Jul 2 18:43:15 2012 From: gideon.simpson at gmail.com (Gideon Simpson) Date: Mon, 2 Jul 2012 20:43:15 -0500 Subject: ghostscript problem Message-ID: <0D93F01A-9D28-4E7E-B8D9-1164982117E2@gmail.com> gideon@~$ sudo port install ghostscript ---> Computing dependencies for ghostscript ---> Verifying checksum(s) for ghostscript Error: Checksum (md5) mismatch for ghostscript-9.05.tar.gz Error: Checksum (sha1) mismatch for ghostscript-9.05.tar.gz Error: Checksum (rmd160) mismatch for ghostscript-9.05.tar.gz *** The non-matching file appears to be HTML. See this page for possible reasons for the checksum mismatch: *** Error: org.macports.checksum for port ghostscript returned: Unable to verify file checksums Please see the log file for port ghostscript for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ghostscript failed -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Mon Jul 2 18:52:29 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Jul 2012 20:52:29 -0500 Subject: ghostscript problem In-Reply-To: <0D93F01A-9D28-4E7E-B8D9-1164982117E2@gmail.com> References: <0D93F01A-9D28-4E7E-B8D9-1164982117E2@gmail.com> Message-ID: <369F95E6-9F4B-4F3D-B549-4DD26EF3CC22@macports.org> On Jul 2, 2012, at 20:43, Gideon Simpson wrote: > gideon@~$ sudo port install ghostscript > ---> Computing dependencies for ghostscript > ---> Verifying checksum(s) for ghostscript > Error: Checksum (md5) mismatch for ghostscript-9.05.tar.gz > Error: Checksum (sha1) mismatch for ghostscript-9.05.tar.gz > Error: Checksum (rmd160) mismatch for ghostscript-9.05.tar.gz > *** > The non-matching file appears to be HTML. See this page for possible reasons > for the checksum mismatch: > > *** And what does the HTML file contain? From gideon.simpson at gmail.com Mon Jul 2 20:45:37 2012 From: gideon.simpson at gmail.com (Gideon Simpson) Date: Mon, 2 Jul 2012 22:45:37 -0500 Subject: ghostscript problem In-Reply-To: <369F95E6-9F4B-4F3D-B549-4DD26EF3CC22@macports.org> References: <0D93F01A-9D28-4E7E-B8D9-1164982117E2@gmail.com> <369F95E6-9F4B-4F3D-B549-4DD26EF3CC22@macports.org> Message-ID: <0D76DDF4-2886-4B29-A107-A1774DA5AFE6@gmail.com> How do I determine that? -gideon On Jul 2, 2012, at 8:52 PM, Ryan Schmidt wrote: > > On Jul 2, 2012, at 20:43, Gideon Simpson wrote: > >> gideon@~$ sudo port install ghostscript >> ---> Computing dependencies for ghostscript >> ---> Verifying checksum(s) for ghostscript >> Error: Checksum (md5) mismatch for ghostscript-9.05.tar.gz >> Error: Checksum (sha1) mismatch for ghostscript-9.05.tar.gz >> Error: Checksum (rmd160) mismatch for ghostscript-9.05.tar.gz >> *** >> The non-matching file appears to be HTML. See this page for possible reasons >> for the checksum mismatch: >> >> *** > > And what does the HTML file contain? > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at macports.org Mon Jul 2 21:56:32 2012 From: ram at macports.org (Adam Mercer) Date: Mon, 2 Jul 2012 23:56:32 -0500 Subject: p5.12-locale-gettext fails to compile In-Reply-To: <936F603E-AC1B-4E65-87DE-B05CFF4B5EC6@mac.com> References: <936F603E-AC1B-4E65-87DE-B05CFF4B5EC6@mac.com> Message-ID: On Mon, Jul 2, 2012 at 5:19 PM, Artemio Gonzalez Lopez wrote: > I know Xcode 4.5 is rather cutting edge, but if somebody else has experienced this problem and has any ideas as to its cause I would appreciate any pointers, suggestions or workarounds. It's not just Xcode-4.5, I saw the same problem on the Leopard Machine... Cheers Adam From larry.velazquez at gmail.com Mon Jul 2 22:20:46 2012 From: larry.velazquez at gmail.com (=?iso-8859-1?Q?Lawrence_Vel=E1zquez?=) Date: Tue, 3 Jul 2012 01:20:46 -0400 Subject: ghostscript problem In-Reply-To: <0D76DDF4-2886-4B29-A107-A1774DA5AFE6@gmail.com> References: <0D93F01A-9D28-4E7E-B8D9-1164982117E2@gmail.com> <369F95E6-9F4B-4F3D-B549-4DD26EF3CC22@macports.org> <0D76DDF4-2886-4B29-A107-A1774DA5AFE6@gmail.com> Message-ID: On Jul 2, 2012, at 11:45 p.m., Gideon Simpson wrote: > How do I determine that? Use "port distfiles ghostscript" to get the absolute path of the distfile, then open it in a text editor or feed it to cat or less or something. vq From ryandesign at macports.org Tue Jul 3 00:47:51 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jul 2012 02:47:51 -0500 Subject: p5.12-locale-gettext fails to compile In-Reply-To: References: <936F603E-AC1B-4E65-87DE-B05CFF4B5EC6@mac.com> Message-ID: <6F62A630-8366-4DED-9F55-2649FBDFFD8B@macports.org> On Jul 2, 2012, at 23:56, Adam Mercer wrote: > On Mon, Jul 2, 2012 at 5:19 PM, Artemio Gonzalez Lopez wrote: > >> I know Xcode 4.5 is rather cutting edge, but if somebody else has experienced this problem and has any ideas as to its cause I would appreciate any pointers, suggestions or workarounds. > > It's not just Xcode-4.5, I saw the same problem on the Leopard Machine... > > Fixed. From f.calboli at gmail.com Tue Jul 3 07:01:40 2012 From: f.calboli at gmail.com (Federico Calboli) Date: Tue, 3 Jul 2012 15:01:40 +0100 Subject: binaries list Message-ID: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> Hi All, is there a list of which ports are available as a binary (for Lion)? I noticed that, on upgrade, a number of ports are installed from binaries rather than being compiled on my machine. For small ports this is nice but quite unimportant, but for stuff like the GCC ports it would be nice to know if I'm going to get some serious compilation time in front of me. BW F -- Federico Calboli f.calboli at gmail.com From arno at alum.wpi.edu Tue Jul 3 07:07:56 2012 From: arno at alum.wpi.edu (Arno Hautala) Date: Tue, 3 Jul 2012 10:07:56 -0400 Subject: binaries list In-Reply-To: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> Message-ID: On Tue, Jul 3, 2012 at 10:01 AM, Federico Calboli wrote: > > is there a list of which ports are available as a binary (for Lion)? You can browse this page: http://packages.macports.org/ I think there is a script that can be used to query a Portfile's license as well, but just because a port's license allows distribution doesn't mean a binary is available or is the current version that would be installed by 'port'. -- arno s hautala /-| arno at alum.wpi.edu pgp b2c9d448 From gideon.simpson at gmail.com Tue Jul 3 07:28:10 2012 From: gideon.simpson at gmail.com (Gideon Simpson) Date: Tue, 3 Jul 2012 09:28:10 -0500 Subject: ghostscript problem In-Reply-To: References: <0D93F01A-9D28-4E7E-B8D9-1164982117E2@gmail.com> <369F95E6-9F4B-4F3D-B549-4DD26EF3CC22@macports.org> <0D76DDF4-2886-4B29-A107-A1774DA5AFE6@gmail.com> Message-ID: <6260F801-E99E-4DC5-B485-7CB3630E36C9@gmail.com> ---> Distfiles for ghostscript [ghostscript-9.05.tar.gz] /opt/local/var/macports/distfiles/ghostscript/ghostscript-9.05.tar.gz md5: f7c6f0431ca8d44ee132a55d583212c1 sha1: af93787ba966360abbe085b213ec563b5db5a8cc rmd160: 8635300e684513f4b8d1f708869efeae27393514 http://downloads.ghostscript.com/public/ghostscript-9.05.tar.gz http://distfiles.macports.org/ghostscript/ghostscript-9.05.tar.gz http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz http://her.gr.distfiles.macports.org/mirrors/macports/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz http://jog.id.distfiles.macports.org/macports/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz http://lil.fr.distfiles.macports.org/ghostscript/ghostscript-9.05.tar.gz http://sea.us.distfiles.macports.org/macports/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz http://svn.macports.org/repository/macports/distfiles/ghostscript/ghostscript-9.05.tar.gz [ghostscript-fonts-other-6.0.tar.gz] /opt/local/var/macports/distfiles/ghostscript/ghostscript-fonts-other-6.0.tar.gz md5: 1a643ae62ef166562e4d422b1a601272 sha1: da62dfcb9c10d96743c7e30c1eebe7166489798c rmd160: ab60dbf71e7d91283a106c3df381cadfe173082f http://downloads.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://aarnet.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://cdnetworks-us-2.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://cdnetworks-kr-1.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://cdnetworks-kr-2.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://citylan.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://dfn.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://fastbull.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://freefr.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://garr.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://heanet.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://hivelocity.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://ignum.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://internode.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://iweb.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://jaist.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://kent.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://nchc.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://ncu.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://netcologne.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://space.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://sunet.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://surfnet.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://switch.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://ufpr.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://voxel.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://waix.dl.sourceforge.net/gs-fonts/ghostscript-fonts-other-6.0.tar.gz http://distfiles.macports.org/ghostscript/ghostscript-fonts-other-6.0.tar.gz http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/ghostscript/ghostscript-fonts-other-6.0.tar.gz http://her.gr.distfiles.macports.org/mirrors/macports/mpdistfiles/ghostscript/ghostscript-fonts-other-6.0.tar.gz http://jog.id.distfiles.macports.org/macports/mpdistfiles/ghostscript/ghostscript-fonts-other-6.0.tar.gz http://lil.fr.distfiles.macports.org/ghostscript/ghostscript-fonts-other-6.0.tar.gz http://sea.us.distfiles.macports.org/macports/mpdistfiles/ghostscript/ghostscript-fonts-other-6.0.tar.gz http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ghostscript/ghostscript-fonts-other-6.0.tar.gz http://svn.macports.org/repository/macports/distfiles/ghostscript/ghostscript-fonts-other-6.0.tar.gz [mappingresources4pdf_2unicode_20091116.tar.Z] /opt/local/var/macports/distfiles/ghostscript/mappingresources4pdf_2unicode_20091116.tar.Z md5: 59267a7d0b818267c8ce85d1dbc4479a sha1: aaf44cb1e5dd2043c932e641b0e41432aee2ca0d rmd160: bc1b86e6a5f0e022f88070195eb3e01e167114a7 http://downloads.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://aarnet.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://cdnetworks-us-2.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://cdnetworks-kr-1.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://cdnetworks-kr-2.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://citylan.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://dfn.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://fastbull.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://freefr.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://garr.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://heanet.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://hivelocity.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://ignum.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://internode.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://iweb.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://jaist.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://kent.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://nchc.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://ncu.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://netcologne.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://space.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://sunet.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://surfnet.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://switch.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://ufpr.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://voxel.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://waix.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_2unicode_20091116.tar.Z http://distfiles.macports.org/ghostscript/mappingresources4pdf_2unicode_20091116.tar.Z http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/ghostscript/mappingresources4pdf_2unicode_20091116.tar.Z http://her.gr.distfiles.macports.org/mirrors/macports/mpdistfiles/ghostscript/mappingresources4pdf_2unicode_20091116.tar.Z http://jog.id.distfiles.macports.org/macports/mpdistfiles/ghostscript/mappingresources4pdf_2unicode_20091116.tar.Z http://lil.fr.distfiles.macports.org/ghostscript/mappingresources4pdf_2unicode_20091116.tar.Z http://sea.us.distfiles.macports.org/macports/mpdistfiles/ghostscript/mappingresources4pdf_2unicode_20091116.tar.Z http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ghostscript/mappingresources4pdf_2unicode_20091116.tar.Z http://svn.macports.org/repository/macports/distfiles/ghostscript/mappingresources4pdf_2unicode_20091116.tar.Z [mappingresources4pdf_other_20091116.tar.Z] /opt/local/var/macports/distfiles/ghostscript/mappingresources4pdf_other_20091116.tar.Z md5: 202fa0a291fc1f5b50cfa239106c1b92 sha1: fc4eabff932c1623f7ee0a34085e79a44d51d0e5 rmd160: 1e2ea9af6be8b60c9a54963e542fa06ceb2daccd http://downloads.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://aarnet.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://cdnetworks-us-2.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://cdnetworks-kr-1.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://cdnetworks-kr-2.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://citylan.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://dfn.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://fastbull.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://freefr.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://garr.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://heanet.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://hivelocity.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://ignum.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://internode.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://iweb.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://jaist.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://kent.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://nchc.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://ncu.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://netcologne.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://space.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://sunet.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://surfnet.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://switch.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://ufpr.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://voxel.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://waix.dl.sourceforge.net/mapping-for-pdf.adobe/mappingresources4pdf_other_20091116.tar.Z http://distfiles.macports.org/ghostscript/mappingresources4pdf_other_20091116.tar.Z http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/ghostscript/mappingresources4pdf_other_20091116.tar.Z http://her.gr.distfiles.macports.org/mirrors/macports/mpdistfiles/ghostscript/mappingresources4pdf_other_20091116.tar.Z http://jog.id.distfiles.macports.org/macports/mpdistfiles/ghostscript/mappingresources4pdf_other_20091116.tar.Z http://lil.fr.distfiles.macports.org/ghostscript/mappingresources4pdf_other_20091116.tar.Z http://sea.us.distfiles.macports.org/macports/mpdistfiles/ghostscript/mappingresources4pdf_other_20091116.tar.Z http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ghostscript/mappingresources4pdf_other_20091116.tar.Z http://svn.macports.org/repository/macports/distfiles/ghostscript/mappingresources4pdf_other_20091116.tar.Z -gideon On Jul 3, 2012, at 12:20 AM, Lawrence Vel?zquez wrote: > On Jul 2, 2012, at 11:45 p.m., Gideon Simpson wrote: > >> How do I determine that? > > Use "port distfiles ghostscript" to get the absolute path of the distfile, then open it in a text editor or feed it to cat or less or something. > > > vq > From jeremy at lavergne.gotdns.org Tue Jul 3 07:45:19 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Tue, 3 Jul 2012 10:45:19 -0400 Subject: binaries list In-Reply-To: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> Message-ID: > is there a list of which ports are available as a binary (for Lion)? I noticed that, on upgrade, a number of ports are installed from binaries rather than being compiled on my machine. For small ports this is nice but quite unimportant, but for stuff like the GCC ports it would be nice to know if I'm going to get some serious compilation time in front of me. Be worry-free, just have MacPorts run in binary-only mode: sudo port -b install x y z -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From f.calboli at gmail.com Tue Jul 3 07:50:43 2012 From: f.calboli at gmail.com (Federico Calboli) Date: Tue, 3 Jul 2012 15:50:43 +0100 Subject: binaries list In-Reply-To: References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> Message-ID: <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> On 3 Jul 2012, at 15:45, Jeremy Lavergne wrote: >> is there a list of which ports are available as a binary (for Lion)? I noticed that, on upgrade, a number of ports are installed from binaries rather than being compiled on my machine. For small ports this is nice but quite unimportant, but for stuff like the GCC ports it would be nice to know if I'm going to get some serious compilation time in front of me. > > Be worry-free, just have MacPorts run in binary-only mode: > sudo port -b install x y z yes, but that would only work if a binary is available! BW F > -- Federico Calboli f.calboli at gmail.com From jeremy at lavergne.gotdns.org Tue Jul 3 07:52:45 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Tue, 3 Jul 2012 10:52:45 -0400 Subject: binaries list In-Reply-To: <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> Message-ID: <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> > yes, but that would only work if a binary is available! Yes, but it'll do what you're after: letting you know if one is available. You can add -p if you want it go on and do what it can from a list of ports you want to install without bailing at first error. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From arno at alum.wpi.edu Tue Jul 3 08:12:55 2012 From: arno at alum.wpi.edu (Arno Hautala) Date: Tue, 3 Jul 2012 11:12:55 -0400 Subject: binaries list In-Reply-To: <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> Message-ID: On Tue, Jul 3, 2012 at 10:52 AM, Jeremy Lavergne wrote: >> yes, but that would only work if a binary is available! > > Yes, but it'll do what you're after: letting you know if one is available. > > You can add -p if you want it go on and do what it can from a list of ports you want to install without bailing at first error. Good idea, so say you want to install some set of ports, one of which has many deps: > port -p -b install port1 port2 port3 big-port port1 port2 go in fine, port3 isn't available as a binary and one of the deps of big-port isn't available. You can then check what's missing with: > port echo port1 port2 port3 big-port rdepof:big-port and not installed You would see something like: > port3 > big-port > big-port-dep1 You can then install the ports that you have to manually compile when you have the processor time: > port install port3 big-port -- arno s hautala /-| arno at alum.wpi.edu pgp b2c9d448 From jdlong at gmail.com Tue Jul 3 13:29:22 2012 From: jdlong at gmail.com (James Long) Date: Tue, 3 Jul 2012 17:29:22 -0300 Subject: version issues with numpy Message-ID: My newness to both Macports and Python are tripping me up, I am sure. But I can't seem to get my mac to use the version of numpy which I have installed with macports. If I run `port installed` I see the following: ... py27-ipython @0.12.1_0+scientific (active) ... py27-numpy @1.6.2_0 (active) which leads me to believe I have ipython 0.12.1 and numpy 1.6.2 This is confirmed when I fire up ipython and it tells me it's version 0.12.1 and python is 2.7.3. So far, so good. >From ipython if I `import numpy` and ask it for the version, it tells me the following: In [2]: import numpy In [3]: numpy.version.version Out[3]: '1.5.1' Sooooo.. 1.5.1? Any tips on why I'm picking up version 1.5.1 of numpy instead of 1.6.2 which is installed by macports? Thanks in advance for your help. -J From allbery.b at gmail.com Tue Jul 3 13:44:21 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Tue, 3 Jul 2012 16:44:21 -0400 Subject: version issues with numpy In-Reply-To: References: Message-ID: On Tue, Jul 3, 2012 at 4:29 PM, James Long wrote: > My newness to both Macports and Python are tripping me up, I am sure. > But I can't seem to get my mac to use the version of numpy which I > have installed with macports. > > If I run `port installed` I see the following: > > ... > py27-ipython @0.12.1_0+scientific (active) > ... > py27-numpy @1.6.2_0 (active) > > which leads me to believe I have ipython 0.12.1 and numpy 1.6.2 > > This is confirmed when I fire up ipython and it tells me it's version > 0.12.1 and python is 2.7.3. So far, so good. > > From ipython if I `import numpy` and ask it for the version, it tells > me the following: > > > In [2]: import numpy > > In [3]: numpy.version.version > Out[3]: '1.5.1' > haral:34371 Z$ /usr/bin/python Python 2.7.1 (r271:86832, Jun 25 2011, 05:09:01) [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import numpy >>> numpy.version.version '1.5.1' I infer you're running the system python instead of MacPorts' python. "sudo port select --set python27 python" should make MacPorts' python be the default instead of Apple's. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From pengyu.ut at gmail.com Tue Jul 3 14:10:34 2012 From: pengyu.ut at gmail.com (Peng Yu) Date: Tue, 3 Jul 2012 16:10:34 -0500 Subject: Is man gp available? Message-ID: Hi, I have pari installed. But I don't see man gp. Is there a way to double check whether man gp should be available or not? -- Regards, Peng From allbery.b at gmail.com Tue Jul 3 14:16:40 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Tue, 3 Jul 2012 17:16:40 -0400 Subject: Is man gp available? In-Reply-To: References: Message-ID: On Tue, Jul 3, 2012 at 5:10 PM, Peng Yu wrote: > I have pari installed. But I don't see man gp. Is there a way to > double check whether man gp should be available or not? > "port contents pari" for starters. It looks to me like there's no manpage anyway, and you would have to build with the +doc variant to get the documentation; but I don't know that for certain and can't install it myself right now. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimpaulgriffin at gmail.com Tue Jul 3 14:54:30 2012 From: jimpaulgriffin at gmail.com (Jamie Paul Griffin) Date: Tue, 3 Jul 2012 22:54:30 +0100 Subject: version issues with numpy In-Reply-To: References: Message-ID: <20120703215430.GA2860@macmini.kode5.net> On Tue, Jul 03, 2012 at 04:44:21PM -0400, Brandon Allbery wrote: > On Tue, Jul 3, 2012 at 4:29 PM, James Long wrote: > > > My newness to both Macports and Python are tripping me up, I am sure. > > But I can't seem to get my mac to use the version of numpy which I > > have installed with macports. > > > > If I run `port installed` I see the following: > > > > ... > > py27-ipython @0.12.1_0+scientific (active) > > ... > > py27-numpy @1.6.2_0 (active) > > > > which leads me to believe I have ipython 0.12.1 and numpy 1.6.2 > > > > This is confirmed when I fire up ipython and it tells me it's version > > 0.12.1 and python is 2.7.3. So far, so good. > > > > From ipython if I `import numpy` and ask it for the version, it tells > > me the following: > > > > > > In [2]: import numpy > > > > In [3]: numpy.version.version > > Out[3]: '1.5.1' > > > > haral:34371 Z$ /usr/bin/python > Python 2.7.1 (r271:86832, Jun 25 2011, 05:09:01) > [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on > darwin > Type "help", "copyright", "credits" or "license" for more information. > >>> import numpy > >>> numpy.version.version > '1.5.1' > > I infer you're running the system python instead of MacPorts' python. > "sudo port select --set python27 python" should make MacPorts' python be > the default instead of Apple's. I just tried that command and it failed. I then thought it should be: sudo port select --set python2.7 python but that failed also: # port select --set python2.7 python Selecting 'python' for 'python2.7' failed: The specified group 'python2.7' does not exist. How would we/I get around that. I need to use the Macports python because I need py-gdbm which is already installed in Macports so I can build pyzor. Jamie From jonesc at hep.phy.cam.ac.uk Tue Jul 3 15:02:10 2012 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Tue, 3 Jul 2012 23:02:10 +0100 Subject: version issues with numpy In-Reply-To: <20120703215430.GA2860@macmini.kode5.net> References: <20120703215430.GA2860@macmini.kode5.net> Message-ID: <25547F8C-2B53-46B7-B2E2-468C5DDB811B@hep.phy.cam.ac.uk> Hi, Works fine for me Chris-Jones-Macbook-Pro ~ > sudo port select python Password: Available versions for python: none python25 python25-apple python26 python26-apple python27 (active) python27-apple python32 Chris-Jones-Macbook-Pro ~ > sudo port select python python27 Selecting 'python27' for 'python' succeeded. 'python27' is now active. Do you actually have macports python27 installed ? run 'sudo port install python27' cheers Chris On 3 Jul 2012, at 10:54pm, Jamie Paul Griffin wrote: > On Tue, Jul 03, 2012 at 04:44:21PM -0400, Brandon Allbery wrote: >> On Tue, Jul 3, 2012 at 4:29 PM, James Long wrote: >> >>> My newness to both Macports and Python are tripping me up, I am sure. >>> But I can't seem to get my mac to use the version of numpy which I >>> have installed with macports. >>> >>> If I run `port installed` I see the following: >>> >>> ... >>> py27-ipython @0.12.1_0+scientific (active) >>> ... >>> py27-numpy @1.6.2_0 (active) >>> >>> which leads me to believe I have ipython 0.12.1 and numpy 1.6.2 >>> >>> This is confirmed when I fire up ipython and it tells me it's version >>> 0.12.1 and python is 2.7.3. So far, so good. >>> >>> From ipython if I `import numpy` and ask it for the version, it tells >>> me the following: >>> >>> >>> In [2]: import numpy >>> >>> In [3]: numpy.version.version >>> Out[3]: '1.5.1' >>> >> >> haral:34371 Z$ /usr/bin/python >> Python 2.7.1 (r271:86832, Jun 25 2011, 05:09:01) >> [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on >> darwin >> Type "help", "copyright", "credits" or "license" for more information. >>>>> import numpy >>>>> numpy.version.version >> '1.5.1' >> >> I infer you're running the system python instead of MacPorts' python. >> "sudo port select --set python27 python" should make MacPorts' python be >> the default instead of Apple's. > > I just tried that command and it failed. I then thought it should be: > sudo port select --set python2.7 python > > but that failed also: > > # port select --set python2.7 python > Selecting 'python' for 'python2.7' failed: The specified group > 'python2.7' does not exist. > > How would we/I get around that. I need to use the Macports python because I need py-gdbm which is already installed in Macports so I can build pyzor. > > Jamie > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2966 bytes Desc: not available URL: From larry.velazquez at gmail.com Tue Jul 3 15:06:11 2012 From: larry.velazquez at gmail.com (=?iso-8859-1?Q?Lawrence_Vel=E1zquez?=) Date: Tue, 3 Jul 2012 18:06:11 -0400 Subject: version issues with numpy In-Reply-To: <20120703215430.GA2860@macmini.kode5.net> References: <20120703215430.GA2860@macmini.kode5.net> Message-ID: <38263A17-7D8F-4EBE-9BE3-69323E77DDA4@gmail.com> On Jul 3, 2012, at 5:54 p.m., Jamie Paul Griffin wrote: > I just tried that command and it failed. I then thought it should be: > sudo port select --set python2.7 python > > but that failed also: > > # port select --set python2.7 python > Selecting 'python' for 'python2.7' failed: The specified group > 'python2.7' does not exist. > > How would we/I get around that. I need to use the Macports python because I need py-gdbm which is already installed in Macports so I can build pyzor. The order of arguments is mixed up. $ port select --set python python2.7 vq From jimpaulgriffin at gmail.com Tue Jul 3 15:11:25 2012 From: jimpaulgriffin at gmail.com (Jamie Paul Griffin) Date: Tue, 3 Jul 2012 23:11:25 +0100 Subject: version issues with numpy In-Reply-To: <25547F8C-2B53-46B7-B2E2-468C5DDB811B@hep.phy.cam.ac.uk> References: <20120703215430.GA2860@macmini.kode5.net> <25547F8C-2B53-46B7-B2E2-468C5DDB811B@hep.phy.cam.ac.uk> Message-ID: <20120703221125.GA2894@macmini.kode5.net> On Tue, Jul 03, 2012 at 11:02:10PM +0100, Chris Jones wrote: > Hi, > > Works fine for me > > Chris-Jones-Macbook-Pro ~ > sudo port select python > Password: > Available versions for python: > none > python25 > python25-apple > python26 > python26-apple > python27 (active) > python27-apple > python32 > Chris-Jones-Macbook-Pro ~ > sudo port select python python27 > Selecting 'python27' for 'python' succeeded. 'python27' is now active. > > Do you actually have macports python27 installed ? run 'sudo port install python27' > > cheers Chris > > > On 3 Jul 2012, at 10:54pm, Jamie Paul Griffin wrote: > > > On Tue, Jul 03, 2012 at 04:44:21PM -0400, Brandon Allbery wrote: > >> On Tue, Jul 3, 2012 at 4:29 PM, James Long wrote: > >> > >>> My newness to both Macports and Python are tripping me up, I am sure. > >>> But I can't seem to get my mac to use the version of numpy which I > >>> have installed with macports. > >>> > >>> If I run `port installed` I see the following: > >>> > >>> ... > >>> py27-ipython @0.12.1_0+scientific (active) > >>> ... > >>> py27-numpy @1.6.2_0 (active) > >>> > >>> which leads me to believe I have ipython 0.12.1 and numpy 1.6.2 > >>> > >>> This is confirmed when I fire up ipython and it tells me it's version > >>> 0.12.1 and python is 2.7.3. So far, so good. > >>> > >>> From ipython if I `import numpy` and ask it for the version, it tells > >>> me the following: > >>> > >>> > >>> In [2]: import numpy > >>> > >>> In [3]: numpy.version.version > >>> Out[3]: '1.5.1' > >>> > >> > >> haral:34371 Z$ /usr/bin/python > >> Python 2.7.1 (r271:86832, Jun 25 2011, 05:09:01) > >> [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on > >> darwin > >> Type "help", "copyright", "credits" or "license" for more information. > >>>>> import numpy > >>>>> numpy.version.version > >> '1.5.1' > >> > >> I infer you're running the system python instead of MacPorts' python. > >> "sudo port select --set python27 python" should make MacPorts' python be > >> the default instead of Apple's. > > > > I just tried that command and it failed. I then thought it should be: > > sudo port select --set python2.7 python > > > > but that failed also: > > > > # port select --set python2.7 python > > Selecting 'python' for 'python2.7' failed: The specified group > > 'python2.7' does not exist. > > > > How would we/I get around that. I need to use the Macports python because I need py-gdbm which is already installed in Macports so I can build pyzor. I was just about to correct myself and seen your replies. I googled and found: # port select python python27 ... which of course has worked perfectly. cheers, Jamie From gsslist+macports at anthropohedron.net Tue Jul 3 16:04:26 2012 From: gsslist+macports at anthropohedron.net (Gregory Seidman) Date: Tue, 3 Jul 2012 19:04:26 -0400 Subject: binaries list In-Reply-To: References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> Message-ID: <20120703230425.GA19522@anthropohedron.net> On Tue, Jul 03, 2012 at 11:12:55AM -0400, Arno Hautala wrote: > On Tue, Jul 3, 2012 at 10:52 AM, Jeremy Lavergne > wrote: > >> yes, but that would only work if a binary is available! > > > > Yes, but it'll do what you're after: letting you know if one is available. > > > > You can add -p if you want it go on and do what it can from a list of > > ports you want to install without bailing at first error. > > Good idea, so say you want to install some set of ports, one of which > has many deps: > > > port -p -b install port1 port2 port3 big-port > > port1 port2 go in fine, port3 isn't available as a binary and one of > the deps of big-port isn't available. > > You can then check what's missing with: > > > port echo port1 port2 port3 big-port rdepof:big-port and not installed > > You would see something like: > > > port3 > > big-port > > big-port-dep1 > > You can then install the ports that you have to manually compile when > you have the processor time: > > > port install port3 big-port Is there any way to automate this? I'd really like to pass some argument to port to prioritize installing binaries, but still install packages from source when they aren't available as binaries. > arno s hautala /-| arno at alum.wpi.edu --Greg From jeremy at lavergne.gotdns.org Tue Jul 3 16:09:17 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Tue, 03 Jul 2012 19:09:17 -0400 Subject: binaries list In-Reply-To: <20120703230425.GA19522@anthropohedron.net> References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> Message-ID: That's how it just works. Gregory Seidman wrote: >On Tue, Jul 03, 2012 at 11:12:55AM -0400, Arno Hautala wrote: >> On Tue, Jul 3, 2012 at 10:52 AM, Jeremy Lavergne >> wrote: >> >> yes, but that would only work if a binary is available! >> > >> > Yes, but it'll do what you're after: letting you know if one is >available. >> > >> > You can add -p if you want it go on and do what it can from a list >of >> > ports you want to install without bailing at first error. >> >> Good idea, so say you want to install some set of ports, one of which >> has many deps: >> >> > port -p -b install port1 port2 port3 big-port >> >> port1 port2 go in fine, port3 isn't available as a binary and one of >> the deps of big-port isn't available. >> >> You can then check what's missing with: >> >> > port echo port1 port2 port3 big-port rdepof:big-port and not >installed >> >> You would see something like: >> >> > port3 >> > big-port >> > big-port-dep1 >> >> You can then install the ports that you have to manually compile when >> you have the processor time: >> >> > port install port3 big-port > >Is there any way to automate this? I'd really like to pass some >argument to >port to prioritize installing binaries, but still install packages from >source when they aren't available as binaries. > >> arno s hautala /-| arno at alum.wpi.edu >--Greg > >_______________________________________________ >macports-users mailing list >macports-users at lists.macosforge.org >http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From ryandesign at macports.org Tue Jul 3 16:13:05 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jul 2012 18:13:05 -0500 Subject: ghostscript problem In-Reply-To: <6260F801-E99E-4DC5-B485-7CB3630E36C9@gmail.com> References: <0D93F01A-9D28-4E7E-B8D9-1164982117E2@gmail.com> <369F95E6-9F4B-4F3D-B549-4DD26EF3CC22@macports.org> <0D76DDF4-2886-4B29-A107-A1774DA5AFE6@gmail.com> <6260F801-E99E-4DC5-B485-7CB3630E36C9@gmail.com> Message-ID: <1AD7F3ED-3B64-4501-8F48-85B0AC09A033@macports.org> On Jul 3, 2012, at 09:28, Gideon Simpson wrote: > On Jul 3, 2012, at 12:20 AM, Lawrence Vel?zquez wrote: > >> On Jul 2, 2012, at 11:45 p.m., Gideon Simpson wrote: >> >>> On Jul 2, 2012, at 8:52 PM, Ryan Schmidt wrote: >>> >>>> On Jul 2, 2012, at 20:43, Gideon Simpson wrote: >>>> >>>>> gideon@~$ sudo port install ghostscript >>>>> ---> Computing dependencies for ghostscript >>>>> ---> Verifying checksum(s) for ghostscript >>>>> Error: Checksum (md5) mismatch for ghostscript-9.05.tar.gz >>>>> Error: Checksum (sha1) mismatch for ghostscript-9.05.tar.gz >>>>> Error: Checksum (rmd160) mismatch for ghostscript-9.05.tar.gz >>>>> *** >>>>> The non-matching file appears to be HTML. See this page for possible reasons >>>>> for the checksum mismatch: >>>>> >>>>> *** >>>> >>>> And what does the HTML file contain? >>> >>> How do I determine that? >> >> Use "port distfiles ghostscript" to get the absolute path of the distfile, then open it in a text editor or feed it to cat or less or something. > > ---> Distfiles for ghostscript > [ghostscript-9.05.tar.gz] /opt/local/var/macports/distfiles/ghostscript/ghostscript-9.05.tar.gz [snip] That is the path to the file which MacPorts was expecting to be a gzip-compressed tar file, but it is in fact an HTML file on your system. Please display the contents of that HTML file by running the command: cat /opt/local/var/macports/distfiles/ghostscript/ghostscript-9.05.tar.gz From gideon.simpson at gmail.com Tue Jul 3 16:14:01 2012 From: gideon.simpson at gmail.com (Gideon Simpson) Date: Tue, 3 Jul 2012 18:14:01 -0500 Subject: ghostscript problem In-Reply-To: <1AD7F3ED-3B64-4501-8F48-85B0AC09A033@macports.org> References: <0D93F01A-9D28-4E7E-B8D9-1164982117E2@gmail.com> <369F95E6-9F4B-4F3D-B549-4DD26EF3CC22@macports.org> <0D76DDF4-2886-4B29-A107-A1774DA5AFE6@gmail.com> <6260F801-E99E-4DC5-B485-7CB3630E36C9@gmail.com> <1AD7F3ED-3B64-4501-8F48-85B0AC09A033@macports.org> Message-ID: gideon@~$ cat /opt/local/var/macports/distfiles/ghostscript/ghostscript-9.05.tar.gz

-gideon On Jul 3, 2012, at 6:13 PM, Ryan Schmidt wrote: > cat /opt/local/var/macports/distfiles/ghostscript/ghostscript-9.05.tar.gz -------------- next part -------------- An HTML attachment was scrubbed... URL: From macports-users at work.wnsr.net Tue Jul 3 16:22:22 2012 From: macports-users at work.wnsr.net (Marc W.) Date: Tue, 3 Jul 2012 16:22:22 -0700 Subject: Mediawiki and php53/ph54 Message-ID: With the recent migration of php5 to php53/php54, I'm looking at installing MediaWiki, but it has a dependency upon php5-mysql and php5-web: $ port list mediawiki\* mediawiki @1.17.0 www/mediawiki $ port deps mediawiki Full Name: mediawiki @1.17.0_0+mysql Runtime Dependencies: libiconv, jpeg, jasper, tiff, lcms, libpng, freetype, libxml2, jbigkit, expat, fontconfig, ghostscript, ImageMagick, aspell, php5-web, php5-mysql Since I'm using the php53/php54, I don't want to install php5-{web,mysql} and its assorted php5-* dependencies. What are my options here? Does the mediawiki port need to be updated? Does it need different variants or separate ports to support either php53 or php54? Thanks for your advice, -Marc From ryandesign at macports.org Tue Jul 3 16:26:41 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jul 2012 18:26:41 -0500 Subject: ghostscript problem In-Reply-To: References: <0D93F01A-9D28-4E7E-B8D9-1164982117E2@gmail.com> <369F95E6-9F4B-4F3D-B549-4DD26EF3CC22@macports.org> <0D76DDF4-2886-4B29-A107-A1774DA5AFE6@gmail.com> <6260F801-E99E-4DC5-B485-7CB3630E36C9@gmail.com> <1AD7F3ED-3B64-4501-8F48-85B0AC09A033@macports.org> Message-ID: <0676D33A-06A9-4355-B068-17BB77A822D8@macports.org> On Jul 3, 2012, at 18:14, Gideon Simpson wrote: > On Jul 3, 2012, at 6:13 PM, Ryan Schmidt wrote: > >> cat /opt/local/var/macports/distfiles/ghostscript/ghostscript-9.05.tar.gz > > gideon@~$ cat /opt/local/var/macports/distfiles/ghostscript/ghostscript-9.05.tar.gz > > > > > > > > > >

> That's unfortunately less helpful than I had hoped. Usually these HTML files will have been generated by "that domain doesn't exist, maybe you'll like these search results" servers (in which case they usually list what URL you had tried to access), or "you must log in to this network" servers (in which case, you must log in to the network). But in your case it tells us nothing at all. You didn't initially show us which server MacPorts was trying to reach when it got this file, but it must be one of these URLs: On Jul 3, 2012, at 09:28, Gideon Simpson wrote: > http://downloads.ghostscript.com/public/ghostscript-9.05.tar.gz > http://distfiles.macports.org/ghostscript/ghostscript-9.05.tar.gz > http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz > http://her.gr.distfiles.macports.org/mirrors/macports/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz > http://jog.id.distfiles.macports.org/macports/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz > http://lil.fr.distfiles.macports.org/ghostscript/ghostscript-9.05.tar.gz > http://sea.us.distfiles.macports.org/macports/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz > http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz > http://svn.macports.org/repository/macports/distfiles/ghostscript/ghostscript-9.05.tar.gz Perhaps there was a temporary problem with the Ghostscript server or one of the MacPorts servers, because I don't see a problem with any of them right now. In any case, please clean and try again: sudo port clean --all ghostscript sudo port install ghostscript As part of the output, MacPorts will show you where it's downloading the distfiles from. If it fails again, show us that URL. Also, try accessing that URL manually in a browser and see if it works there. From gideon.simpson at gmail.com Tue Jul 3 16:34:11 2012 From: gideon.simpson at gmail.com (Gideon Simpson) Date: Tue, 3 Jul 2012 18:34:11 -0500 Subject: ghostscript problem In-Reply-To: <0676D33A-06A9-4355-B068-17BB77A822D8@macports.org> References: <0D93F01A-9D28-4E7E-B8D9-1164982117E2@gmail.com> <369F95E6-9F4B-4F3D-B549-4DD26EF3CC22@macports.org> <0D76DDF4-2886-4B29-A107-A1774DA5AFE6@gmail.com> <6260F801-E99E-4DC5-B485-7CB3630E36C9@gmail.com> <1AD7F3ED-3B64-4501-8F48-85B0AC09A033@macports.org> <0676D33A-06A9-4355-B068-17BB77A822D8@macports.org> Message-ID: <88FDF35E-AE8F-4A27-B283-828CF121B72C@gmail.com> gideon@~$ sudo port install ghostscript ---> Computing dependencies for ghostscript ---> Fetching archive for ghostscript ---> Attempting to fetch ghostscript-9.05_2.darwin_11.x86_64.tbz2 from http://packages.macports.org/ghostscript ---> Fetching distfiles for ghostscript ---> Attempting to fetch ghostscript-9.05.tar.gz from http://downloads.ghostscript.com/public/ ---> Attempting to fetch ghostscript-fonts-other-6.0.tar.gz from http://downloads.sourceforge.net/gs-fonts ---> Attempting to fetch mappingresources4pdf_2unicode_20091116.tar.Z from http://downloads.sourceforge.net/mapping-for-pdf.adobe ---> Attempting to fetch mappingresources4pdf_other_20091116.tar.Z from http://downloads.sourceforge.net/mapping-for-pdf.adobe ---> Verifying checksum(s) for ghostscript Error: Checksum (md5) mismatch for ghostscript-9.05.tar.gz Error: Checksum (sha1) mismatch for ghostscript-9.05.tar.gz Error: Checksum (rmd160) mismatch for ghostscript-9.05.tar.gz *** The non-matching file appears to be HTML. See this page for possible reasons for the checksum mismatch: *** Error: org.macports.checksum for port ghostscript returned: Unable to verify file checksums Please see the log file for port ghostscript for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ghostscript failed -gideon On Jul 3, 2012, at 6:26 PM, Ryan Schmidt wrote: > sudo port install ghostscript -------------- next part -------------- An HTML attachment was scrubbed... URL: From gsslist+macports at anthropohedron.net Tue Jul 3 16:38:51 2012 From: gsslist+macports at anthropohedron.net (Gregory Seidman) Date: Tue, 3 Jul 2012 19:38:51 -0400 Subject: binaries list In-Reply-To: References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> Message-ID: <20120703233848.GA30542@anthropohedron.net> On Tue, Jul 03, 2012 at 07:09:17PM -0400, Jeremy Lavergne wrote: > That's how it just works. Well, no, it doesn't just work. I want to issue a single port command, e.g. port upgrade outdated, and have it install binaries where available and install anything else from source. I want to *prefer* binaries without *restricting* to binaries. --Greg > Gregory Seidman wrote: > > >On Tue, Jul 03, 2012 at 11:12:55AM -0400, Arno Hautala wrote: > >> On Tue, Jul 3, 2012 at 10:52 AM, Jeremy Lavergne > >> wrote: > >> >> yes, but that would only work if a binary is available! > >> > > >> > Yes, but it'll do what you're after: letting you know if one is > >available. > >> > > >> > You can add -p if you want it go on and do what it can from a list > >of > >> > ports you want to install without bailing at first error. > >> > >> Good idea, so say you want to install some set of ports, one of which > >> has many deps: > >> > >> > port -p -b install port1 port2 port3 big-port > >> > >> port1 port2 go in fine, port3 isn't available as a binary and one of > >> the deps of big-port isn't available. > >> > >> You can then check what's missing with: > >> > >> > port echo port1 port2 port3 big-port rdepof:big-port and not > >installed > >> > >> You would see something like: > >> > >> > port3 > >> > big-port > >> > big-port-dep1 > >> > >> You can then install the ports that you have to manually compile when > >> you have the processor time: > >> > >> > port install port3 big-port > > > >Is there any way to automate this? I'd really like to pass some > >argument to > >port to prioritize installing binaries, but still install packages from > >source when they aren't available as binaries. > > > >> arno s hautala /-| arno at alum.wpi.edu > >--Greg > > > >_______________________________________________ > >macports-users mailing list > >macports-users at lists.macosforge.org > >http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > From larry.velazquez at gmail.com Tue Jul 3 16:44:38 2012 From: larry.velazquez at gmail.com (=?utf-8?Q?Lawrence_Vel=C3=A1zquez?=) Date: Tue, 3 Jul 2012 19:44:38 -0400 Subject: binaries list In-Reply-To: <20120703233848.GA30542@anthropohedron.net> References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> <20120703233848.GA30542@anthropohedron.net> Message-ID: Wait, what? Isn't the default (at least for recent versions) to install binaries if available and compile otherwise? vq Sent from my iPhone On Jul 3, 2012, at 7:38 PM, Gregory Seidman wrote: > On Tue, Jul 03, 2012 at 07:09:17PM -0400, Jeremy Lavergne wrote: >> That's how it just works. > > Well, no, it doesn't just work. I want to issue a single port command, e.g. > port upgrade outdated, and have it install binaries where available and > install anything else from source. I want to *prefer* binaries without > *restricting* to binaries. > > --Greg > >> Gregory Seidman wrote: >> >>> On Tue, Jul 03, 2012 at 11:12:55AM -0400, Arno Hautala wrote: >>>> On Tue, Jul 3, 2012 at 10:52 AM, Jeremy Lavergne >>>> wrote: >>>>>> yes, but that would only work if a binary is available! >>>>> >>>>> Yes, but it'll do what you're after: letting you know if one is >>> available. >>>>> >>>>> You can add -p if you want it go on and do what it can from a list >>> of >>>>> ports you want to install without bailing at first error. >>>> >>>> Good idea, so say you want to install some set of ports, one of which >>>> has many deps: >>>> >>>>> port -p -b install port1 port2 port3 big-port >>>> >>>> port1 port2 go in fine, port3 isn't available as a binary and one of >>>> the deps of big-port isn't available. >>>> >>>> You can then check what's missing with: >>>> >>>>> port echo port1 port2 port3 big-port rdepof:big-port and not >>> installed >>>> >>>> You would see something like: >>>> >>>>> port3 >>>>> big-port >>>>> big-port-dep1 >>>> >>>> You can then install the ports that you have to manually compile when >>>> you have the processor time: >>>> >>>>> port install port3 big-port >>> >>> Is there any way to automate this? I'd really like to pass some >>> argument to >>> port to prioritize installing binaries, but still install packages from >>> source when they aren't available as binaries. >>> >>>> arno s hautala /-| arno at alum.wpi.edu >>> --Greg >>> >>> _______________________________________________ >>> macports-users mailing list >>> macports-users at lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users >> >> > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From allbery.b at gmail.com Tue Jul 3 16:57:27 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Tue, 3 Jul 2012 19:57:27 -0400 Subject: binaries list In-Reply-To: <20120703233848.GA30542@anthropohedron.net> References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> <20120703233848.GA30542@anthropohedron.net> Message-ID: On Tue, Jul 3, 2012 at 7:38 PM, Gregory Seidman < gsslist+macports at anthropohedron.net> wrote: > On Tue, Jul 03, 2012 at 07:09:17PM -0400, Jeremy Lavergne wrote: > > That's how it just works. > > Well, no, it doesn't just work. I want to issue a single port command, e.g. > port upgrade outdated, and have it install binaries where available and > install anything else from source. I want to *prefer* binaries without > *restricting* to binaries. > If that's not how it works by default for you, then you need to check your /opt/local/etc/mac/ports/macports.conf (there should be a stock one in the same directory). Also, don't pass the -b or -s options to the "port" command, which options force binary or source build modes on a particular run. The default behavior is to attempt to download a prebuilt package, and if that fails then do a source build. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From arno at alum.wpi.edu Tue Jul 3 17:39:58 2012 From: arno at alum.wpi.edu (Arno Hautala) Date: Tue, 3 Jul 2012 20:39:58 -0400 Subject: binaries list In-Reply-To: <20120703233848.GA30542@anthropohedron.net> References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> <20120703233848.GA30542@anthropohedron.net> Message-ID: On Tue, Jul 3, 2012 at 7:38 PM, Gregory Seidman wrote: > On Tue, Jul 03, 2012 at 07:09:17PM -0400, Jeremy Lavergne wrote: >> That's how it just works. > > Well, no, it doesn't just work. I want to issue a single port command, e.g. > port upgrade outdated, and have it install binaries where available and > install anything else from source. I want to *prefer* binaries without > *restricting* to binaries. As others have stated, this should be the default behavior. The example commands that I posted would only really be useful if you wanted to delay compiling a large install for some reason. -- arno s hautala /-| arno at alum.wpi.edu pgp b2c9d448 From gsslist+macports at anthropohedron.net Tue Jul 3 17:42:18 2012 From: gsslist+macports at anthropohedron.net (Gregory Seidman) Date: Tue, 3 Jul 2012 20:42:18 -0400 Subject: binaries list In-Reply-To: References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> <20120703233848.GA30542@anthropohedron.net> Message-ID: <20120704004217.GA1627@anthropohedron.net> On Tue, Jul 03, 2012 at 07:57:27PM -0400, Brandon Allbery wrote: > On Tue, Jul 3, 2012 at 7:38 PM, Gregory Seidman < > gsslist+macports at anthropohedron.net> wrote: > > > On Tue, Jul 03, 2012 at 07:09:17PM -0400, Jeremy Lavergne wrote: > > > That's how it just works. > > > > Well, no, it doesn't just work. I want to issue a single port command, e.g. > > port upgrade outdated, and have it install binaries where available and > > install anything else from source. I want to *prefer* binaries without > > *restricting* to binaries. > > > > If that's not how it works by default for you, then you need to check your > /opt/local/etc/macports/macports.conf (there should be a stock one in the > same directory). Also, don't pass the -b or -s options to the "port" > command, which options force binary or source build modes on a particular > run. > > The default behavior is to attempt to download a prebuilt package, and if > that fails then do a source build. If I don't specify -b, I always seem to build from source. What should I be looking for in the macports.conf? Also, is there any way to do something similar to port list outdated that will tell me whether a binary of a newer version is available? > brandon s allbery allbery.b at gmail.com --Greg From pengyu.ut at gmail.com Tue Jul 3 17:44:45 2012 From: pengyu.ut at gmail.com (Peng Yu) Date: Tue, 3 Jul 2012 19:44:45 -0500 Subject: Where is gprc? (pari package) Message-ID: Hi, On ubuntu installation of pari-gp, there is /etc/gprc, which is used by gp. But I don't find gprc in macports' pari, and it seems that gp does not load any system wide gprc file. Shall this be fixed? Thanks! -- Regards, Peng From trg818 at gmail.com Tue Jul 3 18:12:15 2012 From: trg818 at gmail.com (Thomas) Date: Wed, 4 Jul 2012 03:12:15 +0200 Subject: p5.12-locale-gettext fails to compose Message-ID: On 3/7/12 9:47 AM, Ryan Schmidt wrote: On Jul 2, 2012, at 23:56, Adam Mercer wrote: On Mon, Jul 2, 2012 at 5:19 PM, Artemio Gonzalez Lopez wrote: I know Xcode 4.5 is rather cutting edge, but if somebody else has experienced this problem and has any ideas as to its cause I would appreciate any pointers, suggestions or workarounds. It's not just Xcode-4.5, I saw the same problem on the Leopard Machine... Fixed. I would have thought the fix is available by now, but in a lengthy installation started this evening, I get the very same error (also on Leopard machine). Is there a delay in updating the server, and do I have to do something when giving it a new try? Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From allbery.b at gmail.com Tue Jul 3 18:13:16 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Tue, 3 Jul 2012 21:13:16 -0400 Subject: Where is gprc? (pari package) In-Reply-To: References: Message-ID: On Tue, Jul 3, 2012 at 8:44 PM, Peng Yu wrote: > On ubuntu installation of pari-gp, there is /etc/gprc, which is used > by gp. But I don't find gprc in macports' pari, and it seems that gp > does not load any system wide gprc file. Shall this be fixed? Thanks! Even if it doesn't come with one, it will probably (if it follows the usual configure-stye rules) use one created at /opt/local/etc/gprc. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Tue Jul 3 18:17:02 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jul 2012 20:17:02 -0500 Subject: ghostscript problem In-Reply-To: <88FDF35E-AE8F-4A27-B283-828CF121B72C@gmail.com> References: <0D93F01A-9D28-4E7E-B8D9-1164982117E2@gmail.com> <369F95E6-9F4B-4F3D-B549-4DD26EF3CC22@macports.org> <0D76DDF4-2886-4B29-A107-A1774DA5AFE6@gmail.com> <6260F801-E99E-4DC5-B485-7CB3630E36C9@gmail.com> <1AD7F3ED-3B64-4501-8F48-85B0AC09A033@macports.org> <0676D33A-06A9-4355-B068-17BB77A822D8@macports.org> <88FDF35E-AE8F-4A27-B283-828CF121B72C@gmail.com> Message-ID: <1AE7B3D3-A23A-4FFF-A19B-AB5249031B8D@macports.org> On Jul 3, 2012, at 18:34, Gideon Simpson wrote: > gideon@~$ sudo port install ghostscript > ---> Computing dependencies for ghostscript > ---> Fetching archive for ghostscript > ---> Attempting to fetch ghostscript-9.05_2.darwin_11.x86_64.tbz2 from http://packages.macports.org/ghostscript > ---> Fetching distfiles for ghostscript > ---> Attempting to fetch ghostscript-9.05.tar.gz from http://downloads.ghostscript.com/public/ Ok, so it is trying to download the file from the ghostscript server. > ---> Attempting to fetch ghostscript-fonts-other-6.0.tar.gz from http://downloads.sourceforge.net/gs-fonts > ---> Attempting to fetch mappingresources4pdf_2unicode_20091116.tar.Z from http://downloads.sourceforge.net/mapping-for-pdf.adobe > ---> Attempting to fetch mappingresources4pdf_other_20091116.tar.Z from http://downloads.sourceforge.net/mapping-for-pdf.adobe > ---> Verifying checksum(s) for ghostscript > Error: Checksum (md5) mismatch for ghostscript-9.05.tar.gz > Error: Checksum (sha1) mismatch for ghostscript-9.05.tar.gz > Error: Checksum (rmd160) mismatch for ghostscript-9.05.tar.gz > *** > The non-matching file appears to be HTML. See this page for possible reasons > for the checksum mismatch: > > *** And the ghostscript server, or a server impersonating it, is delivering an HTML file to you instead. It still works fine for me, so there's either a local network issue between you and that server, or you're on a restricted network that does not allow you to access that server, or something like that. You could download the file manually from one of our mirrors, such as: http://distfiles.macports.org/ghostscript/ And manually place it in the directory MacPorts looks for it in: /opt/local/var/macports/distfiles/ghostscript/ If you're interested in investigating further why you can't reach the ghostscript server, you could see what its IP address is by running: dig downloads.ghostscript.com On my system this returns: ; <<>> DiG 9.6-ESV-R4-P3 <<>> downloads.ghostscript.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59418 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;downloads.ghostscript.com. IN A ;; ANSWER SECTION: downloads.ghostscript.com. 17591 IN A 188.121.46.128 ;; Query time: 32 msec ;; SERVER: 8.8.4.4#53(8.8.4.4) ;; WHEN: Tue Jul 3 20:08:02 2012 ;; MSG SIZE rcvd: 59 If on your system you get a different IP address than 188.121.46.128, then something on your network is impersonating that server, either deliberately or due to a misconfiguration... From allbery.b at gmail.com Tue Jul 3 18:18:10 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Tue, 3 Jul 2012 21:18:10 -0400 Subject: binaries list In-Reply-To: <20120704004217.GA1627@anthropohedron.net> References: <91927A43-5D03-439F-B617-1AD000961F7D@gmail.com> <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> <20120703233848.GA30542@anthropohedron.net> <20120704004217.GA1627@anthropohedron.net> Message-ID: On Tue, Jul 3, 2012 at 8:42 PM, Gregory Seidman < gsslist+macports at anthropohedron.net> wrote: > If I don't specify -b, I always seem to build from source. What should I be > looking for in the macports.conf? > As from "man macports.conf": buildfromsource Controls whether ports are built from source or downloaded as pre- built archives. Setting to 'always' will never use archives, 'never' will always try to use an archive and fail if one is not available. 'ifneeded' will try to fetch an archive and fall back to building from source if that isn't possible. Default: ifneeded portarchivetype Format of archives in which to store port images. This controls both the type of archive created locally after building from source, and the type to request from remote servers. Changing this will not affect the usability of already installed archives; they can be of any supported type. Supported types are: tgz, tar, tbz, tbz2, tlz, txz, xar, zip, cpgz, cpio Default: tbz2 Changing portarchivetype from tbz2 means that the prebuilt archives won't be found (as they are all in tbz2 format only). Also, is there any way to do something similar to port list outdated that > will tell me whether a binary of a newer version is available? > Not so far as I am aware. It could probably be written, though, since the archives all have (obviously) well defined names. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From pengyu.ut at gmail.com Tue Jul 3 18:20:48 2012 From: pengyu.ut at gmail.com (Peng Yu) Date: Tue, 3 Jul 2012 20:20:48 -0500 Subject: Where is gprc? (pari package) In-Reply-To: References: Message-ID: On Tue, Jul 3, 2012 at 8:13 PM, Brandon Allbery wrote: > On Tue, Jul 3, 2012 at 8:44 PM, Peng Yu wrote: >> >> On ubuntu installation of pari-gp, there is /etc/gprc, which is used >> by gp. But I don't find gprc in macports' pari, and it seems that gp >> does not load any system wide gprc file. Shall this be fixed? Thanks! > > > Even if it doesn't come with one, it will probably (if it follows the usual > configure-stye rules) use one created at /opt/local/etc/gprc. I assume that you meant if there were such a file (/opt/local/etc/gprc), gp would use it. But since there is no such a file, gp will just skip this step? Or gp still trys to access /etc/gprc? ~$ cat /opt/local/etc/gprc cat: /opt/local/etc/gprc: No such file or directory -- Regards, Peng From gideon.simpson at gmail.com Tue Jul 3 18:32:30 2012 From: gideon.simpson at gmail.com (Gideon Simpson) Date: Tue, 3 Jul 2012 20:32:30 -0500 Subject: ghostscript problem In-Reply-To: <0676D33A-06A9-4355-B068-17BB77A822D8@macports.org> References: <0D93F01A-9D28-4E7E-B8D9-1164982117E2@gmail.com> <369F95E6-9F4B-4F3D-B549-4DD26EF3CC22@macports.org> <0D76DDF4-2886-4B29-A107-A1774DA5AFE6@gmail.com> <6260F801-E99E-4DC5-B485-7CB3630E36C9@gmail.com> <1AD7F3ED-3B64-4501-8F48-85B0AC09A033@macports.org> <0676D33A-06A9-4355-B068-17BB77A822D8@macports.org> Message-ID: <2E11D3AD-76E6-447F-82C8-D22D37458C2B@gmail.com> So I VPNed into my employer's network and had no trouble getting ghostscript through them, but there was an issue with my home (Comcast) internet. Very bizarre. -gideon On Jul 3, 2012, at 6:26 PM, Ryan Schmidt wrote: > > On Jul 3, 2012, at 18:14, Gideon Simpson wrote: > >> On Jul 3, 2012, at 6:13 PM, Ryan Schmidt wrote: >> >>> cat /opt/local/var/macports/distfiles/ghostscript/ghostscript-9.05.tar.gz >> >> gideon@~$ cat /opt/local/var/macports/distfiles/ghostscript/ghostscript-9.05.tar.gz >> >> >> >> >> >> >> >> >> >>

>> > > That's unfortunately less helpful than I had hoped. Usually these HTML files will have been generated by "that domain doesn't exist, maybe you'll like these search results" servers (in which case they usually list what URL you had tried to access), or "you must log in to this network" servers (in which case, you must log in to the network). But in your case it tells us nothing at all. > > You didn't initially show us which server MacPorts was trying to reach when it got this file, but it must be one of these URLs: > > On Jul 3, 2012, at 09:28, Gideon Simpson wrote: > >> http://downloads.ghostscript.com/public/ghostscript-9.05.tar.gz >> http://distfiles.macports.org/ghostscript/ghostscript-9.05.tar.gz >> http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz >> http://her.gr.distfiles.macports.org/mirrors/macports/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz >> http://jog.id.distfiles.macports.org/macports/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz >> http://lil.fr.distfiles.macports.org/ghostscript/ghostscript-9.05.tar.gz >> http://sea.us.distfiles.macports.org/macports/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz >> http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/ghostscript/ghostscript-9.05.tar.gz >> http://svn.macports.org/repository/macports/distfiles/ghostscript/ghostscript-9.05.tar.gz > > Perhaps there was a temporary problem with the Ghostscript server or one of the MacPorts servers, because I don't see a problem with any of them right now. In any case, please clean and try again: > > sudo port clean --all ghostscript > sudo port install ghostscript > > As part of the output, MacPorts will show you where it's downloading the distfiles from. If it fails again, show us that URL. Also, try accessing that URL manually in a browser and see if it works there. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gsslist+macports at anthropohedron.net Tue Jul 3 18:39:09 2012 From: gsslist+macports at anthropohedron.net (Gregory Seidman) Date: Tue, 3 Jul 2012 21:39:09 -0400 Subject: binaries list In-Reply-To: References: <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> <20120703233848.GA30542@anthropohedron.net> <20120704004217.GA1627@anthropohedron.net> Message-ID: <20120704013908.GA3300@anthropohedron.net> Changed macports.conf to explicitly set buildfromsource to ifneeded and portarchivetype to tbz2 (also set portarchivemode to yes and set the portarchivepath; none of these settings were present in the macports.conf), did a port selfupdate followed by port upgrade outdated. Verdict: Success! Binaries are installing now, no building from source. Thanks for your help! The only other thing I'd like is "apt-cache policy " functionality, particularly for multiple packages (e.g. the outdated pseudopackage) but that doesn't seem to be easily available. --Greg On Tue, Jul 03, 2012 at 09:18:10PM -0400, Brandon Allbery wrote: > On Tue, Jul 3, 2012 at 8:42 PM, Gregory Seidman < > gsslist+macports at anthropohedron.net> wrote: > > > If I don't specify -b, I always seem to build from source. What should I be > > looking for in the macports.conf? > > > > As from "man macports.conf": > > buildfromsource > Controls whether ports are built from source or downloaded as pre- > built archives. Setting to 'always' will never use archives, > 'never' > will always try to use an archive and fail if one is not available. > 'ifneeded' will try to fetch an archive and fall back to building > from source if that isn't possible. > Default: ifneeded > > portarchivetype > Format of archives in which to store port images. This controls > both > the type of archive created locally after building from source, and > the type to request from remote servers. Changing this will not > affect the usability of already installed archives; they can be of > any supported type. > Supported types are: tgz, tar, tbz, tbz2, tlz, txz, xar, zip, cpgz, > cpio > Default: tbz2 > > Changing portarchivetype from tbz2 means that the prebuilt archives won't > be found (as they are all in tbz2 format only). > > Also, is there any way to do something similar to port list outdated that > > will tell me whether a binary of a newer version is available? > > > > Not so far as I am aware. It could probably be written, though, since the > archives all have (obviously) well defined names. > > -- > brandon s allbery allbery.b at gmail.com > wandering unix systems administrator (available) (412) 475-9364 vm/sms > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From allbery.b at gmail.com Tue Jul 3 18:41:07 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Tue, 3 Jul 2012 21:41:07 -0400 Subject: Where is gprc? (pari package) In-Reply-To: References: Message-ID: On Tue, Jul 3, 2012 at 9:20 PM, Peng Yu wrote: > On Tue, Jul 3, 2012 at 8:13 PM, Brandon Allbery > wrote:I assume that you meant if there were such a file > (/opt/local/etc/gprc), gp would use it. But since there is no such a > file, gp will just skip this step? Or gp still trys to access > /etc/gprc? > > ~$ cat /opt/local/etc/gprc > cat: /opt/local/etc/gprc: No such file or directory The standard package paths, as used by most packages, use /etc if the install prefix is /usr (as it usually is for Linux distribution packages) or /etc for other prefixes. So, since MacPorts uses a prefix of /opt/local, the configuration file should be /opt/local/etc/gprc. It should not attempt to use anything under /etc if it's based on standard paths, although if it's rolling its own instead it might try. Running it under dtruss should give you the answer, if all else fails. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Tue Jul 3 19:02:44 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jul 2012 21:02:44 -0500 Subject: binaries list In-Reply-To: <20120704013908.GA3300@anthropohedron.net> References: <7F99E1E6-69E5-461E-AF7C-9E3CD9E6AE00@gmail.com> <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> <20120703233848.GA30542@anthropohedron.net> <20120704004217.GA1627@anthropohedron.net> <20120704013908.GA3300@anthropohedron.net> Message-ID: <6E202497-A2B9-4B83-935A-FD2C1F6C3352@macports.org> On Jul 3, 2012, at 20:39, Gregory Seidman wrote: > The only other thing I'd like is "apt-cache policy " functionality, Could you explain what that is, for those of us unfamiliar with apt? On Jul 3, 2012, at 19:42, Gregory Seidman wrote: > Also, is there any way to do something similar to port list outdated that > will tell me whether a binary of a newer version is available? No; also, "port list" is not the command you want. See: https://trac.macports.org/wiki/FAQ#portlist From ryandesign at macports.org Tue Jul 3 19:03:58 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jul 2012 21:03:58 -0500 Subject: p5.12-locale-gettext fails to compose In-Reply-To: References: Message-ID: On Jul 3, 2012, at 20:12, Thomas wrote: > On 3/7/12 9:47 AM, Ryan Schmidt wrote: >> On Jul 2, 2012, at 23:56, Adam Mercer wrote: >>> On Mon, Jul 2, 2012 at 5:19 PM, Artemio Gonzalez Lopez wrote: >>>> I know Xcode 4.5 is rather cutting edge, but if somebody else has experienced this problem and has any ideas as to its cause I would appreciate any pointers, suggestions or workarounds. >>> It's not just Xcode-4.5, I saw the same problem on the Leopard Machine... >>> >> Fixed. > I would have thought the fix is available by now, but in a lengthy installation started this evening, I get the very same error (also on Leopard machine). Is there a delay in updating the server, and do I have to do something when giving it a new try? Anything we commit to the Subversion repository is available within 30 minutes on the rsync server. To receive those fixes, run "sudo port selfupdate", then clean the port and try again. From ryandesign at macports.org Tue Jul 3 19:04:40 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jul 2012 21:04:40 -0500 Subject: Mediawiki and php53/ph54 In-Reply-To: References: Message-ID: <4964F30D-00A0-4EF1-AABE-87770CCB95F5@macports.org> On Jul 3, 2012, at 18:22, Marc W. wrote: > With the recent migration of php5 to php53/php54, I'm looking at > installing MediaWiki, but it has a dependency upon php5-mysql and > php5-web: > > $ port list mediawiki\* > mediawiki @1.17.0 www/mediawiki > > $ port deps mediawiki > Full Name: mediawiki @1.17.0_0+mysql > Runtime Dependencies: libiconv, jpeg, jasper, tiff, lcms, libpng, > freetype, libxml2, jbigkit, expat, fontconfig, > ghostscript, ImageMagick, aspell, php5-web, php5-mysql > > > Since I'm using the php53/php54, I don't want to install > php5-{web,mysql} and its assorted php5-* dependencies. What are my > options here? Does the mediawiki port need to be updated? Does it need > different variants or separate ports to support either php53 or php54? The mediawiki port, and all other ports using php5, need to be updated to include variants allowing the user to choose which version(s) of PHP they want to use it with. From gsslist+macports at anthropohedron.net Tue Jul 3 19:20:12 2012 From: gsslist+macports at anthropohedron.net (Gregory Seidman) Date: Tue, 3 Jul 2012 22:20:12 -0400 Subject: binaries list In-Reply-To: <6E202497-A2B9-4B83-935A-FD2C1F6C3352@macports.org> References: <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> <20120703233848.GA30542@anthropohedron.net> <20120704004217.GA1627@anthropohedron.net> <20120704013908.GA3300@anthropohedron.net> <6E202497-A2B9-4B83-935A-FD2C1F6C3352@macports.org> Message-ID: <20120704022009.GA3918@anthropohedron.net> On Tue, Jul 03, 2012 at 09:02:44PM -0500, Ryan Schmidt wrote: > On Jul 3, 2012, at 20:39, Gregory Seidman wrote: > > The only other thing I'd like is "apt-cache policy " > > functionality, > > Could you explain what that is, for those of us unfamiliar with apt? Sorry, yes, I should have explained originally. On my Debian server: % apt-cache policy netatalk netatalk: Installed: 2.2.2-1 Candidate: 2.2.2-1 Version table: *** 2.2.2-1 0 100 /var/lib/dpkg/status 2.1.2-2 0 990 http://ftp.us.debian.org/debian/ stable/main i386 Packages It tells me that netatalk version 2.1.2-2 is available from the repository, but that I have 2.2.2-1 installed (because I jumped through hoops to install a newer version, as it turns out). What I'm looking for is a convenient way to see what versions are available to be installed and what versions, if any, are installed. > On Jul 3, 2012, at 19:42, Gregory Seidman wrote: > > Also, is there any way to do something similar to port list outdated > > that will tell me whether a binary of a newer version is available? > > No; also, "port list" is not the command you want. See: > > https://trac.macports.org/wiki/FAQ#portlist In this case, port list is exactly what I wanted. I wanted to see what was available rather than what is installed. --Greg From ryandesign at macports.org Tue Jul 3 19:38:11 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jul 2012 21:38:11 -0500 Subject: binaries list In-Reply-To: <20120704022009.GA3918@anthropohedron.net> References: <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> <20120703233848.GA30542@anthropohedron.net> <20120704004217.GA1627@anthropohedron.net> <20120704013908.GA3300@anthropohedron.net> <6E202497-A2B9-4B83-935A-FD2C1F6C3352@macports.org> <20120704022009.GA3918@anthropohedron.net> Message-ID: On Jul 3, 2012, at 21:20, Gregory Seidman wrote: > On Tue, Jul 03, 2012 at 09:02:44PM -0500, Ryan Schmidt wrote: >> On Jul 3, 2012, at 20:39, Gregory Seidman wrote: >>> The only other thing I'd like is "apt-cache policy " >>> functionality, >> >> Could you explain what that is, for those of us unfamiliar with apt? > > Sorry, yes, I should have explained originally. On my Debian server: > > % apt-cache policy netatalk > netatalk: > Installed: 2.2.2-1 > Candidate: 2.2.2-1 > Version table: > *** 2.2.2-1 0 > 100 /var/lib/dpkg/status > 2.1.2-2 0 > 990 http://ftp.us.debian.org/debian/ stable/main i386 Packages > > It tells me that netatalk version 2.1.2-2 is available from the repository, > but that I have 2.2.2-1 installed (because I jumped through hoops to > install a newer version, as it turns out). > > What I'm looking for is a convenient way to see what versions are available > to be installed and what versions, if any, are installed. "port installed" tells your which ports are installed. You can restrict that, e.g. "port installed zlib" to see which version(s) of the zlib port are installed. "port outdated" tells you which of those ports are outdated. You can restrict that too, e.g. "port outdated zlib" to see if zlib is outdated. There is always only one version of a port available to be installed?the current version. To install older versions, you have to jump through hoops explained here: https://trac.macports.org/wiki/howto/InstallingOlderPort From allbery.b at gmail.com Tue Jul 3 19:52:32 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Tue, 3 Jul 2012 22:52:32 -0400 Subject: binaries list In-Reply-To: References: <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> <20120703233848.GA30542@anthropohedron.net> <20120704004217.GA1627@anthropohedron.net> <20120704013908.GA3300@anthropohedron.net> <6E202497-A2B9-4B83-935A-FD2C1F6C3352@macports.org> <20120704022009.GA3918@anthropohedron.net> Message-ID: On Tue, Jul 3, 2012 at 10:38 PM, Ryan Schmidt wrote: > > What I'm looking for is a convenient way to see what versions are > available > > to be installed and what versions, if any, are installed. > > "port installed" tells your which ports are installed. You can restrict > that, e.g. "port installed zlib" to see which version(s) of the zlib port > are installed. > > "port outdated" tells you which of those ports are outdated. You can > restrict that too, e.g. "port outdated zlib" to see if zlib is outdated. > > There is always only one version of a port available to be installed?the > current version. To install older versions, you have to jump through hoops > explained here: > And what is missing from all of this is what I understood your original question to be: what *packages* might be available (which depends on variants etc.). "port list" shows what will build from source; only a subset of this is available as binary packages, and even then only for some architectures and default variants (and only with the default MacPorts prefix of /opt/local). -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Tue Jul 3 19:59:56 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jul 2012 21:59:56 -0500 Subject: binaries list In-Reply-To: References: <4DD0D969-F700-4F02-BC23-70022BC9F427@lavergne.gotdns.org> <20120703230425.GA19522@anthropohedron.net> <20120703233848.GA30542@anthropohedron.net> <20120704004217.GA1627@anthropohedron.net> <20120704013908.GA3300@anthropohedron.net> <6E202497-A2B9-4B83-935A-FD2C1F6C3352@macports.org> <20120704022009.GA3918@anthropohedron.net> Message-ID: <8C8E7059-5F5C-405B-A729-FF3BC9CA7B3B@macports.org> On Jul 3, 2012, at 21:52, Brandon Allbery wrote: > And what is missing from all of this is what I understood your original question to be: what *packages* might be available (which depends on variants etc.). Right, there's no MacPorts command that tells you whether a binary would be available. > "port list" shows what will build from source; only a subset of this is available as binary packages, and even then only for some architectures and default variants (and only with the default MacPorts prefix of /opt/local). ...and only for certain OS versions, and only if your applications_dir and frameworks_dir are also the defaults, and possibly there are even more restrictions that I'm forgetting right now. From pengyu.ut at gmail.com Tue Jul 3 20:05:39 2012 From: pengyu.ut at gmail.com (Peng Yu) Date: Tue, 3 Jul 2012 22:05:39 -0500 Subject: Where is gprc? (pari package) In-Reply-To: References: Message-ID: > Running it under dtruss should give you the answer, if all else fails. Never knew dtruss. Good to know. It indeed access /etc/gprc. Shall this problem be corrected in macports? 165 open_nocancel("/etc/gprc\0", 0x0, 0x1B6) = -1 Err#2 -- Regards, Peng From gsslist+macports at anthropohedron.net Tue Jul 3 20:08:47 2012 From: gsslist+macports at anthropohedron.net (Gregory Seidman) Date: Tue, 3 Jul 2012 23:08:47 -0400 Subject: binaries list In-Reply-To: References: <20120703233848.GA30542@anthropohedron.net> <20120704004217.GA1627@anthropohedron.net> <20120704013908.GA3300@anthropohedron.net> <6E202497-A2B9-4B83-935A-FD2C1F6C3352@macports.org> <20120704022009.GA3918@anthropohedron.net> Message-ID: <20120704030843.GA4372@anthropohedron.net> On Tue, Jul 03, 2012 at 10:52:32PM -0400, Brandon Allbery wrote: > On Tue, Jul 3, 2012 at 10:38 PM, Ryan Schmidt wrote: > > > What I'm looking for is a convenient way to see what versions are > > > available to be installed and what versions, if any, are installed. > > > > "port installed" tells your which ports are installed. You can restrict > > that, e.g. "port installed zlib" to see which version(s) of the zlib > > port are installed. > > > > "port outdated" tells you which of those ports are outdated. You can > > restrict that too, e.g. "port outdated zlib" to see if zlib is > > outdated. > > > > There is always only one version of a port available to be > > installed???the current version. To install older versions, you have to > > jump through hoops explained here: > > And what is missing from all of this is what I understood your original > question to be: what *packages* might be available (which depends on > variants etc.). "port list" shows what will build from source; only a > subset of this is available as binary packages, and even then only for some > architectures and default variants (and only with the default MacPorts > prefix of /opt/local). Exactly. I'd like to have a simple way to ask the following questions about a package all at once: 1) What versions are installed, if any, and which is active? 2) What version is available to install from a binary, if any? 3) What version is available to install from source? 4) What versions are sitting in my portarchivepath? (is that meaningful?) Even better would be asking those questions about anything outdated all at once. And, of course, the output should be both human readable and reasonably easy to manipulate if piped to a script (i.e. machine-readable). I take it such a thing does not currently exist. Anyone feeling up to the challenge? > brandon s allbery allbery.b at gmail.com --Greg From jeremy at lavergne.gotdns.org Tue Jul 3 20:22:11 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Tue, 3 Jul 2012 23:22:11 -0400 Subject: binaries list In-Reply-To: <20120704030843.GA4372@anthropohedron.net> References: <20120703233848.GA30542@anthropohedron.net> <20120704004217.GA1627@anthropohedron.net> <20120704013908.GA3300@anthropohedron.net> <6E202497-A2B9-4B83-935A-FD2C1F6C3352@macports.org> <20120704022009.GA3918@anthropohedron.net> <20120704030843.GA4372@anthropohedron.net> Message-ID: <624FFD61-C4BF-464E-A47C-0870F4B65944@lavergne.gotdns.org> > Exactly. I'd like to have a simple way to ask the following questions about > a package all at once: > > 1) What versions are installed, if any, and which is active? > 2) What version is available to install from a binary, if any? > 3) What version is available to install from source? > 4) What versions are sitting in my portarchivepath? (is that meaningful?) > > Even better would be asking those questions about anything outdated all at > once. And, of course, the output should be both human readable and > reasonably easy to manipulate if piped to a script (i.e. machine-readable). > > I take it such a thing does not currently exist. Anyone feeling up to the > challenge? Well, 1 can be done with `port installed x`. The rest (2,3,4) seem like something that can be calculated outside of MacPorts, since it only knows the current versions---nothing more. If you place your own Portfile somewhere and ask MacPorts to use it (`port archivefetch` or `port -b install x`) you'll be able to find out if the version in that Portfile exists as a binary. In the outdated situation, just use `port -p archivefetch outdated`: it'll fetch what it can and your scripts can review the errors. The easy approach? I'd say always stick with binary-only mode unless you have time to do compiles; then let it go with a normal install/upgrade where it uses both binary and source as available. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From ryandesign at macports.org Tue Jul 3 20:34:41 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jul 2012 22:34:41 -0500 Subject: Where is gprc? (pari package) In-Reply-To: References: Message-ID: <659E0DDC-AB18-477A-9168-60AAD7128C96@macports.org> On Jul 3, 2012, at 22:05, Peng Yu wrote: >> Running it under dtruss should give you the answer, if all else fails. > > Never knew dtruss. Good to know. > > It indeed access /etc/gprc. Shall this problem be corrected in macports? > > 165 open_nocancel("/etc/gprc\0", 0x0, 0x1B6) = -1 Err#2 Yes, that should be corrected. From trg818 at gmail.com Wed Jul 4 05:46:58 2012 From: trg818 at gmail.com (Thomas) Date: Wed, 4 Jul 2012 14:46:58 +0200 Subject: p5.12-locale-gettext fails to compose In-Reply-To: References: Message-ID: On Wed, Jul 4, 2012 at 4:03 AM, Ryan Schmidt wrote: > On Jul 3, 2012, at 20:12, Thomas wrote: > > I would have thought the fix is available by now, but in a lengthy > installation started this > > evening, I get the very same error (also on Leopard machine). Is there a > delay in > > updating the server, and do I have to do something when giving it a new > try? > Anything we commit to the Subversion repository is available within 30 > minutes on the rsync server. > Thanks. Strange that I didn't get it on the first attempt, but anyway, it works now. I had failed to clean the port (again). Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From trg818 at gmail.com Wed Jul 4 06:26:02 2012 From: trg818 at gmail.com (Thomas) Date: Wed, 4 Jul 2012 15:26:02 +0200 Subject: gtk2 fails to build Message-ID: Hi, I'm trying to (re)build gtk2 @2.24.8 +x11, which has been found to be broken by port's automatic check, but the compilation fails with the error messages posted below. This happens on a Leopard machine (10.5.8) (and this time I did clean gtk2 before recompiling). What can I do about it? It does seem that I have all required libraries installed, in particular libpng and pixbuf. The whole thing happens while running port upgrade texlive (and I must say, I don't know why macports decided to compile the entire universe when I only wanted my TeX to be upgraded), although I don't understand why gtk2 is rebuilt in the first place here. Thomas :info:build Making all in demos :info:build make[2]: Entering directory `/opt/local/var/macports/build/_opt_loca l_var_macports_sources_rsync.macports.org_release_ports_gnome_gtk2/gtk2/work/gtk +-2.24.10/demos' :info:build /opt/local/bin/gdk-pixbuf-csource --raw --build-list \ :info:build apple_red ./apple-red.png \ :info:build gnome_foot ./gnome-foot.png \ :info:build > test-inline-pixbufs.h \ :info:build || (rm -f test-inline-pixbufs.h && false) :info:build :info:build (process:51647): GdkPixbuf-WARNING **: Bug! gdk-pixbuf loader 'png' didn't set an error on failure. :info:build failed to load "./apple-red.png": Failed to load image './apple-red. png': reason not known, probably a corrupt image file :info:build make[2]: *** [test-inline-pixbufs.h] Error 1 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local _var_macports_sources_rsync.macports.org_release_ports_gnome_gtk2/gtk2/work/gtk+ -2.24.10/demos' :info:build make[1]: *** [all-recursive] Error 1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local _var_macports_sources_rsync.macports.org_release_ports_gnome_gtk2/gtk2/work/gtk+ -2.24.10' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_va r_macports_sources_rsync.macports.org_release_ports_gnome_gtk2/gtk2/work/gtk+-2. 24.10' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_ma cports_sources_rsync.macports.org_release_ports_gnome_gtk2/gtk2/work/gtk+-2.24.1 0" && /usr/bin/make -w all :info:build Exit code: 2 :error:build org.macports.build for port gtk2 returned: command execution failed :debug:build Error code: CHILDSTATUS 80259 2 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: targets not executed for gtk2: org.macports.install org.mac ports.build org.macports.destroot -------------- next part -------------- An HTML attachment was scrubbed... URL: From trg818 at gmail.com Wed Jul 4 06:50:45 2012 From: trg818 at gmail.com (Thomas) Date: Wed, 4 Jul 2012 15:50:45 +0200 Subject: gtk2 fails to build In-Reply-To: References: Message-ID: Here's the screen output of the compilation, which I forgot to post in my earlier post: ---> Scanning binaries for linking errors: 100.0% ---> Found 75 broken file(s), matching files to ports ---> Found 2 broken port(s), determining rebuild order ---> Rebuilding in order gtk2 @2.24.8 +x11 llvm-3.0 @3.0 ---> Computing dependencies for gtk2 ---> Fetching archive for gtk2 ---> Attempting to fetch gtk2-2.24.10_2+x11.darwin_9.i386.tbz2 from http://packages.macports.org/gtk2 ---> Fetching distfiles for gtk2 ---> Verifying checksum(s) for gtk2 ---> Extracting gtk2 ---> Applying patches to gtk2 ---> Configuring gtk2 ---> Building gtk2 Error: org.macports.build for port gtk2 returned: command execution failed Please see the log file for port gtk2 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gtk2/gtk2/main.log Error: Unable to upgrade port: 1 Error rebuilding gtk2 while executing "error "Error rebuilding $portname"" (procedure "revupgrade_scanandrebuild" line 370) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "action_revupgrade $action $portlist $opts" (procedure "action_upgrade" line 24) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 95) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 4784) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Wed Jul 4 08:59:54 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 4 Jul 2012 10:59:54 -0500 Subject: gtk2 fails to build In-Reply-To: References: Message-ID: <9A65A470-0F88-4C07-8E67-FF6FBCE40E22@macports.org> On Jul 4, 2012, at 08:26, Thomas wrote: > I'm trying to (re)build gtk2 @2.24.8 +x11, which has been found to be broken by port's automatic check, but the compilation fails with the error messages posted below. This happens on a Leopard machine (10.5.8) (and this time I did clean gtk2 before recompiling). > What can I do about it? It does seem that I have all required libraries installed, in particular libpng and pixbuf. > The whole thing happens while running port upgrade texlive (and I must say, I don't know why macports decided to compile the entire universe when I only wanted my TeX to be upgraded), although I don't understand why gtk2 is rebuilt in the first place here. After you install or upgrade *any* port, MacPorts 2.1 and up runs rev-upgrade which checks *all* installed ports, and rebuilds any found to have linking problems. The intention is that MacPorts will find and fix any other ports broken by whatever you just upgraded. But if this is the first time you're installing or upgrading a port after upgrading to MacPorts 2.1, rev-upgrade may find all sorts of things that have been broken for awhile that we didn't even know about. > :info:build failed to load "./apple-red.png": Failed to load image './apple-red.png': reason not known, probably a corrupt image file This sounds very familiar: https://trac.macports.org/ticket/29393 Try rebuilding gdk-pixbuf2: sudo port clean gdk-pixbuf2 sudo port -n upgrade --force gdk-pixbuf2 From trg818 at gmail.com Wed Jul 4 10:07:41 2012 From: trg818 at gmail.com (Thomas) Date: Wed, 4 Jul 2012 19:07:41 +0200 Subject: gtk2 fails to build In-Reply-To: <9A65A470-0F88-4C07-8E67-FF6FBCE40E22@macports.org> References: <9A65A470-0F88-4C07-8E67-FF6FBCE40E22@macports.org> Message-ID: On Wed, Jul 4, 2012 at 5:59 PM, Ryan Schmidt wrote: > > :info:build failed to load "./apple-red.png": Failed to load image > './apple-red.png': reason not known, probably a corrupt image file > This sounds very familiar: > https://trac.macports.org/ticket/29393 > Try rebuilding gdk-pixbuf2: > sudo port clean gdk-pixbuf2 > sudo port -n upgrade --force gdk-pixbuf2 > Ok, so I rebuilt gdk-pixbuf2 @2.26.1_1 (which I had built without problems just before) and then rebuilt (or indeed, upgraded to 2.24.10_2) gtk2 (after cleaning it again) but it still doesn't work - the same error, as far as I can tell. I have libpng @1.4.11_0, which seems to be the most recent port available. Would it make sense to force-rebuild that as well, or do you have other suggestions? Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From keybounce at gmail.com Wed Jul 4 17:44:58 2012 From: keybounce at gmail.com (Michael) Date: Wed, 4 Jul 2012 17:44:58 -0700 Subject: Compiling errors Message-ID: I'm trying to compile murmur. I've got an open ticket, but I ran into an oddity. :info:build make[2]: /Applications/Xcode.app/Contents/Developer/usr/bin/g++-4.2: No such file or directory keybounceMBP:bin michael$ ls /Applications/Xcode.app/Contents/Developer/usr/bin/ total 23656 16 BuildStrings* 104 ibtoold* 24 CpMac* 16 ident* 104 DeRez* 96 install_name_tool* 16 GetFileInfo* 32 instruments* 48 ImageUnitAnalyzer* 24 iprofiler* 24 MergePef* 24 javaconfig* 16 MvMac* 48 javatool* 40 PPCExplain* 864 ld* 16 ResMerger* 336 ld_classic* 112 Rez* 112 libtool* 32 RezDet* 152 lldb* 16 RezWack* 8 llvm-cpp-4.2@ 16 SetFile* 8 llvm-g++@ 16 SplitForks* 8 llvm-g++-4.2@ 16 UnRezWack* 8 llvm-gcc@ 16 agvtool* 8 llvm-gcc-4.2@ 0 amlint* 352 make* 32 ar* 16 mapc* 24 as* 112 merge* 24 c89* 56 mksdk* 24 c99* 48 momc* 168 ci* 232 nasm* 80 cmpdylib* 80 ndisasm* 152 co* 96 nm* 104 codesign_allocate* 128 nmedit* 72 codesign_wrapper* 16 opendiff* 0 cpp* 400 otool* 104 ctf_insert* 88 pagestuff* 1368 cvs* 24 projectInfo* 16 cvsbug* 8 ranlib@ 80 desdp* 168 rcs* 120 docsetutil* 8 rcs2log@ 776 dsymutil* 152 rcsclean* 16 dvtexec* 120 rcsdiff* 720 dwarfdump* 112 rcsmerge* 104 dyldinfo* 48 rebase* 8 g++@ 168 redo_prebinding* 48 gatherheaderdoc* 104 resolveLinks* 8 gcc@ 128 rlog* 8 gcov@ 16 sdef* 8 gcov-4.2@ 256 sdp* 0 gdb* 40 segedit* 2592 git* 80 size* 64 git-cvsserver* 152 strip* 8 git-receive-pack@ 2232 svn* 1096 git-shell* 904 svnadmin* 8 git-upload-archive@ 816 svndumpfilter* 1120 git-upload-pack* 856 svnlook* 168 gitk* 1000 svnserve* 352 gnumake* 1240 svnsync* 112 gprof* 840 svnversion* 32 hdxml2manxml* 32 unwinddump* 80 headerdoc2html* 16 xcodebuild* 8 i686-apple-darwin11-llvm-g++-4.2@ 24 xcrun* 8 i686-apple-darwin11-llvm-gcc-4.2@ 104 xed* 32 ibtool* 56 xml2man* 208 ibtool3* keybounceMBP:bin michael$ So a simple question: What's missing from my development directory? What got messed up, and how do I fix it? --- This is coming from Mail.app. I hate the new Gmail web look, and dislike Mail only slightly less. From jeremy at lavergne.gotdns.org Wed Jul 4 17:58:39 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Wed, 4 Jul 2012 20:58:39 -0400 Subject: Compiling errors In-Reply-To: References: Message-ID: > :info:build make[2]: /Applications/Xcode.app/Contents/Developer/usr/bin/g++-4.2: No such file or directory > > So a simple question: What's missing from my development directory? What got messed up, and how do I fix it? You don't have g++-4.2. Murmur/mumble are pretty much a lost cause; their authors only try building on one very specific setup and don't really care about the rest. In this case, you don't have the compiler they use. You might be able to convince it that LLVM suffices, but then you'll run into dependencies that are the wrong arch and other fun things. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From ryandesign at macports.org Thu Jul 5 13:08:50 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 5 Jul 2012 15:08:50 -0500 Subject: Compiling errors In-Reply-To: References: Message-ID: On Jul 4, 2012, at 19:58, Jeremy Lavergne wrote: >> :info:build make[2]: /Applications/Xcode.app/Contents/Developer/usr/bin/g++-4.2: No such file or directory >> >> So a simple question: What's missing from my development directory? What got messed up, and how do I fix it? > > You don't have g++-4.2. To clarify: Apple no longer includes g++-4.2 (or any part of the gcc toolchain) in Xcode 4.3 and up. Apple has switched to clang and llvm. From jeremyhu at macports.org Thu Jul 5 17:58:49 2012 From: jeremyhu at macports.org (Jeremy Huddleston Sequoia) Date: Thu, 05 Jul 2012 17:58:49 -0700 Subject: Compiling errors In-Reply-To: References: Message-ID: On Jul 5, 2012, at 13:08, Ryan Schmidt wrote: > > On Jul 4, 2012, at 19:58, Jeremy Lavergne wrote: > >>> :info:build make[2]: /Applications/Xcode.app/Contents/Developer/usr/bin/g++-4.2: No such file or directory >>> >>> So a simple question: What's missing from my development directory? What got messed up, and how do I fix it? >> >> You don't have g++-4.2. > > To clarify: Apple no longer includes g++-4.2 (or any part of the gcc toolchain) in Xcode 4.3 and up. Apple has switched to clang and llvm. Which port is failing to build (ie, which port is trying to use gcc-4.2)? That port should probably be fixed to build correctly. From jeremy at lavergne.gotdns.org Thu Jul 5 18:18:26 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Thu, 5 Jul 2012 21:18:26 -0400 Subject: Compiling errors In-Reply-To: References: Message-ID: <053E7EFE-14C0-4616-ACF5-5A7EC8FCA975@lavergne.gotdns.org> > Which port is failing to build (ie, which port is trying to use gcc-4.2)? That port should probably be fixed to build correctly. Mumble/murmur. It's a very rigid build--even beyond the compilers. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From ryandesign at macports.org Thu Jul 5 18:39:34 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 5 Jul 2012 20:39:34 -0500 Subject: gtk2 fails to build In-Reply-To: References: <9A65A470-0F88-4C07-8E67-FF6FBCE40E22@macports.org> Message-ID: On Jul 4, 2012, at 12:07, Thomas wrote: > On Wed, Jul 4, 2012 at 5:59 PM, Ryan Schmidt wrote: > > :info:build failed to load "./apple-red.png": Failed to load image './apple-red.png': reason not known, probably a corrupt image file > This sounds very familiar: > https://trac.macports.org/ticket/29393 > Try rebuilding gdk-pixbuf2: > sudo port clean gdk-pixbuf2 > sudo port -n upgrade --force gdk-pixbuf2 > Ok, so I rebuilt gdk-pixbuf2 @2.26.1_1 (which I had built without problems just before) and then rebuilt (or indeed, upgraded to 2.24.10_2) gtk2 (after cleaning it again) but it still doesn't work - the same error, as far as I can tell. > I have libpng @1.4.11_0, which seems to be the most recent port available. Would it make sense to force-rebuild that as well, or do you have other suggestions? I Googled the error message and got this: http://forums.gentoo.org/viewtopic-p-6375954.html It suggests that although you have libpng 1.4.11 installed, perhaps some of the other ports you have installed that need libpng have not been rebuilt and are still linking with the old libpng 1.2.x. Does that seem possible? We upgraded to libpng 1.4.x a long time ago in MacPorts so you really shouldn't have anything left using libpng 1.2.x. We have a script floating around somewhere to help you find things still linked with old libpng. Actually, these days rev-upgrade should find and rebuild them automatically. What happens if you run: sudo port rev-upgrade From davshaonr at gmail.com Thu Jul 5 23:11:30 2012 From: davshaonr at gmail.com (David Shao) Date: Thu, 5 Jul 2012 23:11:30 -0700 Subject: Is octave-devel the "official" octave in preference to octave? Message-ID: On a Macbook 2,1 running Lion 10.7.4, Xcode 4.3.2, octave fails to build with error message: Undefined symbols for architecture x86_64: "_SuiteSparse_time", referenced from: _umfpack_tic in libumfpack.a(umfpack_gn_tictoc.o) _umfpack_toc in libumfpack.a(umfpack_gn_tictoc.o) ld: symbol(s) not found for architecture x86_64 octave-devel using the same packages for dependent libs when possible appears to build and at least run. octave has no maintainer while octave-devel does have one. Is octave-devel the actual recommended octave? From and.damore at macports.org Fri Jul 6 02:12:00 2012 From: and.damore at macports.org (Andrea D'Amore) Date: Fri, 6 Jul 2012 11:12:00 +0200 Subject: Is octave-devel the "official" octave in preference to octave? In-Reply-To: References: Message-ID: On Fri, Jul 6, 2012 at 8:11 AM, David Shao wrote: > On a Macbook 2,1 running Lion 10.7.4, Xcode 4.3.2, octave fails to > build with error message: > Undefined symbols for architecture x86_64: > "_SuiteSparse_time", referenced from: > _umfpack_tic in libumfpack.a(umfpack_gn_tictoc.o) > _umfpack_toc in libumfpack.a(umfpack_gn_tictoc.o) > ld: symbol(s) not found for architecture x86_64 I've fixed this, once I finish building the port (I'm past the SuiteSparse_time issue but octave takes its time to build) I'll commit the change. I've created a new ticket [1] and cc'ed you, once you get notified the ticket is closed you'll have to sync the port tree, clean octave port and rebuild it. As future reference when a port doesn't build check the trac system for an existing ticket and if there's none for your problem file a new one, see [2] for details. > octave-devel using the same packages for dependent libs when possible > appears to build and at least run. octave has no maintainer while > octave-devel does have one. > Is octave-devel the actual recommended octave? There's been a discussion about octave not too much ago, check -dev mailing list's archive. The two ports differ in version, one is 3.2 branch and the other is 3.4, IIRC the discussion was about pulling -devel to 3.4 because that had been left behind. Anyway search for it. -- Andrea [1] http://trac.macports.org/ticket/35100 [2] http://guide.macports.org/#project.tickets From trg818 at gmail.com Fri Jul 6 06:58:33 2012 From: trg818 at gmail.com (Thomas) Date: Fri, 6 Jul 2012 15:58:33 +0200 Subject: gtk2 fails to build In-Reply-To: References: <9A65A470-0F88-4C07-8E67-FF6FBCE40E22@macports.org> Message-ID: On Fri, Jul 6, 2012 at 3:39 AM, Ryan Schmidt wrote: > I Googled the error message and got this: > http://forums.gentoo.org/viewtopic-p-6375954.html > > It suggests that although you have libpng 1.4.11 installed, perhaps some > of the other ports you have installed that need libpng have not been > rebuilt and are still linking with the old libpng 1.2.x. Does that seem > possible? We upgraded to libpng 1.4.x a long time ago in MacPorts so you > really shouldn't have anything left using libpng 1.2.x. > Some time ago, while (unsuccessfully) trying to build another program from sources by hand, I had fiddled with libpng12 and libpng15, and it turns out that those were still there in some form in addition to libpng14. Now I removed them - and broke some more packages in the process. It turns out that openjpeg, which I have installed, needs libpng15, because /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_openjpeg/openjpeg/main.log includes the following error: :info:build CCLD j2k_to_image :info:build ld: library not found for -lpng15 :info:build collect2: ld returned 1 exit status :info:build make[3]: *** [j2k_to_image] Error 1 However, there is no port for libpng15 (which makes me wonder how my old, now broken openjpeg was installed). > We have a script floating around somewhere to help you find things still > linked with old libpng. Actually, these days rev-upgrade should find and > rebuild them automatically. What happens if you run: > sudo port rev-upgrade > The reason for rebuilding gtk2 was apparently that some files or links were broken, I have seen that in my previous attempts when the automatic self-check ran. However, as far as I can see, rev-upgrade does the same stuff as my previous attempts, and fails for the same reason (I did this before fiddling with libpng and openjpeg as described above): ---> Updating database of binaries: 100.0% ---> Scanning binaries for linking errors: 100.0% ---> Found 75 broken file(s), matching files to ports ---> Found 2 broken port(s), determining rebuild order ---> Rebuilding in order gtk2 @2.24.8 +x11 llvm-3.0 @3.0 ---> Computing dependencies for gtk2 ---> Building gtk2 Error: org.macports.build for port gtk2 returned: command execution failed Please see the log file for port gtk2 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gtk2/gtk2/main.log Error: Unable to upgrade port: 1 Error rebuilding gtk2 while executing "error "Error rebuilding $portname"" (procedure "revupgrade_scanandrebuild" line 370) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 95) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 4784) After fiddling with the png and jpeg libs there were more checks: ---> Found 121 broken file(s), matching files to ports ---> Found 5 broken port(s), determining rebuild order ---> Rebuilding in order llvm-3.0 @3.0 ffmpeg @0.7.11 poppler @0.18.4 +qt4+quartz gdk-pixbuf2 @2.26.1 gtk2 @2.24.8 +x11 so the order of llvm and gtk2 in this list was reversed. llvm was compiled and installed correctly, it seems, but then the compilation of ffmpeg failed because of the problems with openjpeg described at the beginning. The more I struggle, the deeper I seem to think into the quagmire. Here's a list of all the ports I currently have on my system: apr @1.4.6_1 (active) apr-util @1.4.1_0 (active) aquaterm @1.0.1_5 (active) atk @2.2.0_1 (active) autoconf @2.69_0 (active) automake @1.12.1_0 (active) bzip2 @1.0.6_0 (active) cairo @1.12.2_0+x11 (active) cctools-headers @822_2 (active) cmake @2.8.7_0 (active) coreutils @8.15_0 (active) cppunit @1.12.1_0 (active) curl @7.26.0_0+ssl (active) curl-ca-bundle @7.26.0_1 (active) cyrus-sasl2 @2.1.25_1+kerberos (active) db46 @4.6.21_6+java (active) dblatex @0.3.2_0+python27 (active) dbus @1.4.20_1+startupitem (active) dejavu-fonts @2.33_0 (active) detex @2.8_1 (active) dirac @1.0.2_1 (active) docbook-xml @5.0_0 (active) docbook-xml-4.1.2 @4.1.2_1 (active) docbook-xml-4.2 @4.2_0 (active) docbook-xml-4.3 @4.3_0 (active) docbook-xml-4.4 @4.4_0 (active) docbook-xml-4.5 @4.5_0 (active) docbook-xml-5.0 @5.0_0 (active) docbook-xsl @1.76.1_0 (active) dvipng @1.14_2 (active) dyld-headers @195.6_1 (active) expat @2.1.0_0 (active) faac @1.28_2 (active) faad2 @2.7_0 (active) ffmpeg @0.7.11_1 (active) fftw-3 @3.3.1_0 (active) file @5.09_0 (active) findutils @4.4.2_1 (active) flac @1.2.1_1 (active) flex @2.5.35_1 (active) fontconfig @2.9.0_1 (active) fontforge @20110222_1 (active) fop @1.0_1 (active) freetype @2.4.10_0 (active) gd2 @2.0.35_12 (active) gdbm @1.10_1 (active) gdk-pixbuf2 @2.26.1_1 (active) getopt @1.1.4_1 (active) gettext @0.18.1.1_2 (active) ghostscript @9.05_2 (active) giflib @4.1.6_1 (active) glib2 @2.32.3_1 (active) gmake @3.82_0 (active) gmp @5.0.4_0 (active) gnome-common @2.28.0_0 (active) gnome-doc-utils @0.20.6_0+python27 (active) gnuplot @4.6.0_0+luaterm+pangocairo (active) gperf @3.0.4_2 (active) groff @1.21_2 (active) gtk-doc @1.18_0+python27 (active) gtk2 @2.24.8_1+x11 (active) guile @1.8.7_3 (active) help2man @1.40.10_0 (active) hicolor-icon-theme @0.12_0 (active) ImageMagick @6.7.8-0_0+perl+q16 (active) intltool @0.50.2_0 (active) iso-codes @3.29_0 (active) jasper @1.900.1_9 (active) jbig2dec @0.11_1 (active) jbigkit @2.0_2 (active) jpeg @8d_0 (active) kerberos5 @1.7.2_0 (active) lame @3.99_1 (active) latexdiff @0.5_1 (active) latexmk @4.31_0 (active) lcms @1.19_2 (active) lcms2 @2.3_0 (active) libao @1.1.0_0 (active) libedit @20120601-3.0_0 (active) libffi @3.0.11_0 (active) libiconv @1.14_0 (active) libid3tag @0.15.1b_2 (active) libidn @1.25_0 (active) liblzma @5.0.3_0 libmad @0.15.1b_2 (active) libmng @1.0.10_2 (active) libmp4v2 @1.5.0.1_0 (active) libogg @1.3.0_1 (active) liboil @0.3.15_0 (active) libpaper @1.1.24_0 (active) libpixman @0.26.2_0 (active) libpng @1.4.11_0 (active) libsamplerate @0.1.7_2 (active) libsdl @1.2.15_0+x11 (active) libsdl_mixer @1.2.8_1 (active) libsndfile @1.0.25_0 (active) libtheora @1.1.1_1 (active) libtool @2.4.2_2 (active) libuninameslist @20091231_0 (active) libunwind-headers @30_2 (active) libvorbis @1.3.2_1 (active) libvpx @1.0.0_0 (active) libxml2 @2.7.8_0 (active) libxslt @1.1.26_0 (active) libzzip @0.13.62_0 (active) lilypond @2.14.2_1+python27 (active) llvm-3.0 @3.0_4 llvm-3.0 @3.0_5 (active) llvm_select @0.2_0 (active) lua @5.1.4_4 (active) m4 @1.4.16_0 (active) mftrace @1.2.16_1 (active) ncurses @5.9_1 (active) ncursesw @5.8_0 (active) neon @0.29.6_1 (active) netpbm @10.47.37_0 (active) nosetests_select @0.1_0 (active) openssl @1.0.1c_0 (active) orc @0.4.16_0 (active) p5-term-readkey @2.30_0 (active) p5-tk @804.028_0 (active) p5.12-getopt-long @2.380.0_2 (active) p5.12-locale-gettext @1.50.0_7 (active) p5.12-pathtools @3.330.0_2 (active) p5.12-scalar-list-utils @1.230.0_2 (active) p5.12-xml-parser @2.400.0_3 (active) pango @1.30.1_0+x11 (active) pdfjam @2.08_0 (active) pdflib @7.0.5_1 (active) perl5 @5.12.4_0+perl5_12 (active) perl5.12 @5.12.4_1 (active) pgf @2.10_0 (active) pkgconfig @0.26_1 (active) poppler @0.18.4_5+qt4+quartz (active) poppler-data @0.4.5_0 (active) portaudio @19.20111121_2 (active) portmidi @217_1 (active) potrace @1.9_1 (active) psutils @p17_1 (active) py26-distribute @0.6.26_0 (active) py26-nose @1.1.2_2 (active) py26-numpy @1.6.1_1 (active) py26-pil @1.1.7_4 (active) py26-pyqt4 @4.9.1_0 (active) py26-pyqwt @5.2.0_2+qwt52 (active) py26-sip @4.13.2_0 (active) py26-tkinter @2.6.8_0 (active) py27-libxml2 @2.7.8_0 (active) python26 @2.6.8_0 (active) python27 @2.7.3_0 (active) python_select @0.3_1 (active) qt4-mac @4.8.2_0+quartz (active) qwt52 @5.2.1_2+qt4 (active) rarian @0.8.1_0 (active) readline @6.2.000_0 (active) recode @3.6_3 (active) sbcl @1.0.29_1+darwin_9_i386+html (active) schroedinger @1.0.11_0 (active) serf1 @1.1.0_0 (active) shared-mime-info @1.0_0 (active) smpeg @0.4.4_8 (active) sox @14.3.2_0 (active) speex @1.2rc1_0 (active) sqlite3 @3.7.13_0 (active) subversion @1.7.5_0 (active) SuiteSparse @3.4.0_3 (active) t1lib @5.1.2_2 (active) t1utils @1.37_0 (active) tcl @8.5.6_0 (active) texi2html @5.0_0 (active) texinfo @4.13_2 (active) texlive @2011_0+doc+medium (active) texlive-basic @23152_1+doc (active) texlive-bin @2011_5+x11 (active) texlive-bin-extra @23089_1+doc (active) texlive-common @2011_0 (active) texlive-context @23171_0+doc (active) texlive-documentation-base @23160_0+doc (active) texlive-documentation-english @22612_0+doc (active) texlive-fonts-recommended @23165_0+doc (active) texlive-fontutils @23142_0+doc (active) texlive-generic-recommended @23088_0+doc (active) texlive-lang-czechslovak @23092_0+doc (active) texlive-lang-dutch @23092_0+doc (active) texlive-lang-english @23092_0+doc (active) texlive-lang-french @23092_0+doc (active) texlive-lang-german @23085_0+doc (active) texlive-lang-italian @23092_0+doc (active) texlive-lang-polish @23092_0+doc (active) texlive-lang-portuguese @23092_0+doc (active) texlive-lang-spanish @23092_0+doc (active) texlive-latex @23089_0+doc (active) texlive-latex-extra @22931_0+doc (active) texlive-latex-recommended @23089_0+doc (active) texlive-luatex @23137_0+doc (active) texlive-math-extra @23089_0+doc (active) texlive-metapost @23089_0+doc (active) texlive-pictures @22961_1+doc (active) texlive-xetex @23080_0+doc (active) tiff @3.9.5_0 (active) tk @8.5.6_1 (active) urw-fonts @1.0.7pre44_0 (active) wavpack @4.60.1_0 (active) webp @0.1.3_0 (active) wxWidgets @2.8.12_0 (active) x264 @20111210_0 (active) Xft2 @2.3.0_0 (active) xmlcatmgr @2.2_1 (active) xmlto @0.0.25_0 (active) xorg-bigreqsproto @1.1.2_0 (active) xorg-compositeproto @0.4.2_0 (active) xorg-damageproto @1.2.1_0 (active) xorg-fixesproto @5.0_0 (active) xorg-inputproto @2.2_0 (active) xorg-kbproto @1.0.6_0 (active) xorg-libice @1.0.8_0 (active) xorg-libpthread-stubs @0.3_0 (active) xorg-libsm @1.2.1_0 (active) xorg-libX11 @1.5.0_0 (active) xorg-libXau @1.0.7_0 (active) xorg-libXaw @1.0.11_0 (active) xorg-libxcb @1.8.1_2+python27 (active) xorg-libXcomposite @0.4.3_0 (active) xorg-libXcursor @1.1.13_0 (active) xorg-libXdamage @1.1.3_0 (active) xorg-libXdmcp @1.1.1_0 (active) xorg-libXext @1.3.1_0 (active) xorg-libXfixes @5.0_0 (active) xorg-libXi @1.6.0_1 (active) xorg-libXinerama @1.1.2_0 (active) xorg-libxkbfile @1.0.8_0 (active) xorg-libxkbui @1.0.2_0 (active) xorg-libXmu @1.1.1_0 (active) xorg-libXp @1.0.1_0 (active) xorg-libXrandr @1.3.2_0 (active) xorg-libXScrnSaver @1.1.3_0 (active) xorg-libXt @1.1.3_0 (active) xorg-printproto @1.0.5_0 (active) xorg-randrproto @1.3.2_0 (active) xorg-renderproto @0.11.1_0 (active) xorg-scrnsaverproto @1.1.0_0 (active) xorg-util-macros @1.17_0 (active) xorg-xcb-proto @1.7.1_0+python27 (active) xorg-xcb-util @0.3.9_0 (active) xorg-xcmiscproto @1.2.2_0 (active) xorg-xextproto @7.2.1_0 (active) xorg-xf86bigfontproto @1.2.0_0 (active) xorg-xineramaproto @1.2.1_0 (active) xorg-xproto @7.0.23_0 (active) xorg-xtrans @1.2.7_0 (active) xpm @3.5.10_0 (active) xrender @0.9.7_0 (active) XviD @1.3.2_2 (active) xz @5.0.4_0 (active) yasm @1.1.0_0 (active) zlib @1.2.7_0 (active) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Fri Jul 6 07:33:31 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 6 Jul 2012 09:33:31 -0500 Subject: gtk2 fails to build In-Reply-To: References: <9A65A470-0F88-4C07-8E67-FF6FBCE40E22@macports.org> Message-ID: <7FDE5D88-EAFD-4E33-A921-BF28AD2592A3@macports.org> On Jul 6, 2012, at 08:58, Thomas wrote: > Some time ago, while (unsuccessfully) trying to build another program from sources by hand, I had fiddled with libpng12 and libpng15, and it turns out that those were still there in some form in addition to libpng14. Ok, so this could indeed be the problem for you. You should get the current libpng 1.4.x port installed and activated and then rebuild anything using a different libpng. > Now I removed them - and broke some more packages in the process. > It turns out that openjpeg, which I have installed, needs libpng15, because /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_openjpeg/openjpeg/main.log includes the following error: > :info:build CCLD j2k_to_image > :info:build ld: library not found for -lpng15 > :info:build collect2: ld returned 1 exit status > :info:build make[3]: *** [j2k_to_image] Error 1 > > However, there is no port for libpng15 (which makes me wonder how my old, now broken openjpeg was installed). My openjpeg is successfully installed against the current libpng 1.4.x port. Try cleaning openjpeg and rebuilding it. > The reason for rebuilding gtk2 was apparently that some files or links were broken, I have seen that in my previous attempts when the automatic self-check ran. However, as far as I can see, rev-upgrade does the same stuff as my previous attempts, and fails for the same reason (I did this before fiddling with libpng and openjpeg as described above): > ---> Updating database of binaries: 100.0% > ---> Scanning binaries for linking errors: 100.0% > ---> Found 75 broken file(s), matching files to ports > ---> Found 2 broken port(s), determining rebuild order > ---> Rebuilding in order > gtk2 @2.24.8 +x11 > llvm-3.0 @3.0 > ---> Computing dependencies for gtk2 > ---> Building gtk2 > Error: org.macports.build for port gtk2 returned: command execution failed > Please see the log file for port gtk2 for details: This was not a clean attempt. (You can tell because it started at the Building phase, skipping the Configuring and earlier phases.) "sudo port clean gtk2" and try again. From trg818 at gmail.com Fri Jul 6 08:04:58 2012 From: trg818 at gmail.com (Thomas) Date: Fri, 6 Jul 2012 17:04:58 +0200 Subject: gtk2 fails to build In-Reply-To: <7FDE5D88-EAFD-4E33-A921-BF28AD2592A3@macports.org> References: <9A65A470-0F88-4C07-8E67-FF6FBCE40E22@macports.org> <7FDE5D88-EAFD-4E33-A921-BF28AD2592A3@macports.org> Message-ID: On Fri, Jul 6, 2012 at 4:33 PM, Ryan Schmidt wrote: > Ok, so this could indeed be the problem for you. You should get the > current libpng 1.4.x port installed and activated and then rebuild anything > using a different libpng. > The libpng14 port was installed and marked as active all the time: libpng @1.4.11_0 (active) > My openjpeg is successfully installed against the current libpng 1.4.x > port. Try cleaning openjpeg and rebuilding it. > [...] > This was not a clean attempt. (You can tell because it started at the > Building phase, skipping the Configuring and earlier phases.) "sudo port > clean gtk2" and try again. > Just to be sure, I cleaned openjpeg, ffmpeg, and gtk2 and started over, but it still fails at the same point - he's still trying to link against libpng15, which is not there, instead of libpng14, which is there and active: ~> sudo port clean openjpeg ffmpeg gtk2---> Cleaning openjpeg ---> Cleaning ffmpeg ---> Cleaning gtk2 ~> sudo port rev-upgrade---> Updating database of binaries: 100.0% ---> Scanning binaries for linking errors: 100.0% ---> Found 92 broken file(s), matching files to ports ---> Found 4 broken port(s), determining rebuild order ---> Rebuilding in order ffmpeg @0.7.11 gdk-pixbuf2 @2.26.1 gtk2 @2.24.8 +x11 poppler @0.18.4 +qt4+quartz ---> Computing dependencies for ffmpeg ---> Dependencies to be installed: openjpeg ---> Fetching archive for openjpeg ---> Attempting to fetch openjpeg-1.5.0_2.darwin_9.i386.tbz2 from http://packages.macports.org/openjpeg ---> Fetching distfiles for openjpeg ---> Verifying checksum(s) for openjpeg ---> Extracting openjpeg ---> Applying patches to openjpeg ---> Configuring openjpeg ---> Building openjpeg Error: org.macports.build for port openjpeg returned: command execution failed Error: Failed to install openjpeg Please see the log file for port openjpeg for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_openjpeg/openjpeg/main.log Error: The following dependencies were not installed: openjpeg Error: Unable to upgrade port: 1 Error rebuilding ffmpeg while executing "error "Error rebuilding $portname"" (procedure "revupgrade_scanandrebuild" line 370) invoked from within "revupgrade_scanandrebuild broken_port_counts $opts" (procedure "macports::revupgrade" line 5) invoked from within "macports::revupgrade $opts" (procedure "action_revupgrade" line 2) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 95) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command set exit_status [process_cmd $remaining..." (file "/opt/local/bin/port" line 4784) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Fri Jul 6 08:33:14 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 6 Jul 2012 10:33:14 -0500 Subject: gtk2 fails to build In-Reply-To: References: <9A65A470-0F88-4C07-8E67-FF6FBCE40E22@macports.org> <7FDE5D88-EAFD-4E33-A921-BF28AD2592A3@macports.org> Message-ID: <09AC9C88-2A73-4430-89BF-ACFA5DCAD591@macports.org> On Jul 6, 2012, at 10:04, Thomas wrote: > ---> Fetching distfiles for openjpeg > ---> Verifying checksum(s) for openjpeg > ---> Extracting openjpeg > ---> Applying patches to openjpeg > ---> Configuring openjpeg > ---> Building openjpeg > Error: org.macports.build for port openjpeg returned: command execution failed > Error: Failed to install openjpeg > Please see the log file for port openjpeg for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_openjpeg/openjpeg/main.log Ok, please file a bug report and attach that main.log. From trg818 at gmail.com Fri Jul 6 09:06:27 2012 From: trg818 at gmail.com (Thomas) Date: Fri, 6 Jul 2012 18:06:27 +0200 Subject: gtk2 fails to build In-Reply-To: <09AC9C88-2A73-4430-89BF-ACFA5DCAD591@macports.org> References: <9A65A470-0F88-4C07-8E67-FF6FBCE40E22@macports.org> <7FDE5D88-EAFD-4E33-A921-BF28AD2592A3@macports.org> <09AC9C88-2A73-4430-89BF-ACFA5DCAD591@macports.org> Message-ID: On Fri, Jul 6, 2012 at 5:33 PM, Ryan Schmidt wrote: > Ok, please file a bug report and attach that main.log. > Done. Ryan, thanks for your help so far. Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdavis.webb at gmail.com Fri Jul 6 22:53:06 2012 From: sdavis.webb at gmail.com (Stephen Webb) Date: Fri, 6 Jul 2012 23:53:06 -0600 Subject: What has MacPorts Installed for py27-iPython? Message-ID: <2A2DC283-8BE6-42DC-BF32-F86C70DC88A0@gmail.com> I used MacPorts to install py27-ipython and found only a directory in /opt/local/var/macports/software/py27-ipython that contains only: py27-ipython-0.12.1_0+scientific.darwin_10.noarch.tbz2 What is this, why is it not added to my path (if it should be), and where is the iPython install I thought I had created? Thanks for your help! -s From allbery.b at gmail.com Fri Jul 6 22:59:54 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Sat, 7 Jul 2012 01:59:54 -0400 Subject: What has MacPorts Installed for py27-iPython? In-Reply-To: <2A2DC283-8BE6-42DC-BF32-F86C70DC88A0@gmail.com> References: <2A2DC283-8BE6-42DC-BF32-F86C70DC88A0@gmail.com> Message-ID: On Sat, Jul 7, 2012 at 1:53 AM, Stephen Webb wrote: > I used MacPorts to install py27-ipython and found only a directory in > /opt/local/var/macports/software/py27-ipython that contains only: > > py27-ipython-0.12.1_0+scientific.darwin_10.noarch.tbz2 > > What is this, why is it not added to my path (if it should be), and where > is the iPython install I thought I had created? > "port contents py27-ipython" will show you what was actually installed; like most python ports, it's probably put stuff in the framework's bin directory, somewhere under /opt/local/Library/Frameworks, and you will need to add that to $PATH yourself. (I do not know why that's how it's done.) The thing you found is the package archive. When you build a package (or download it), you get that; then "port activate" is used to unpack it into the installed ports tree. You can "port deactivate" it and then activate a different version, if you need to (unless you use -u, old versions are retained when you upgrade ports, so you can easily recover if a new version is buggy). -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimpaulgriffin at gmail.com Sat Jul 7 06:57:51 2012 From: jimpaulgriffin at gmail.com (Jamie Paul Griffin) Date: Sat, 7 Jul 2012 14:57:51 +0100 Subject: What has MacPorts Installed for py27-iPython? In-Reply-To: References: <2A2DC283-8BE6-42DC-BF32-F86C70DC88A0@gmail.com> Message-ID: <20120707135751.GA6457@macmini.kode5.net> On Sat, Jul 07, 2012 at 01:59:54AM -0400, Brandon Allbery wrote: > On Sat, Jul 7, 2012 at 1:53 AM, Stephen Webb wrote: > > I used MacPorts to install py27-ipython and found only a directory in /opt/ > local/var/macports/software/py27-ipython that contains only: > > py27-ipython-0.12.1_0+scientific.darwin_10.noarch.tbz2 > > What is this, why is it not added to my path (if it should be), and where > is the iPython install I thought I had created? > > > "port contents py27-ipython" will show you what was actually installed; like > most python ports, it's probably put stuff in the framework's bin directory, > somewhere under /opt/local/Library/Frameworks, and you will need to add that to > $PATH yourself. ?(I do not know why that's how it's done.) > > The thing you found is the package archive. ?When you build a package (or > download it), you get that; then "port activate" is used to unpack it into the > installed ports tree. ?You can "port deactivate" it and then activate a > different version, if you need to (unless you use -u, old versions are retained > when you upgrade ports, so you can easily recover if a new version is buggy). I experienced a similar issue when I installed pyzor (not from Macports but build manually using the Macports installed python2.7) and the binary pyzord was installed in: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/pyzord You can just use a symlink to the binary into a directory in your path; /opt/local/bin for example. What you have there isn't a binary though so i'd imagine there are some more steps you need to make as suggested by Brandon to actually be able to use the port. I hope you get it working. Good luck. Jamie. From arno at alum.wpi.edu Sat Jul 7 07:19:28 2012 From: arno at alum.wpi.edu (Arno Hautala) Date: Sat, 7 Jul 2012 10:19:28 -0400 Subject: What has MacPorts Installed for py27-iPython? In-Reply-To: <20120707135751.GA6457@macmini.kode5.net> References: <2A2DC283-8BE6-42DC-BF32-F86C70DC88A0@gmail.com> <20120707135751.GA6457@macmini.kode5.net> Message-ID: On Sat, Jul 7, 2012 at 9:57 AM, Jamie Paul Griffin wrote: > > I experienced a similar issue when I installed pyzor (not from Macports > but build manually using the Macports installed python2.7) and the > binary pyzord was installed in: > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/pyzord > > You can just use a symlink to the binary into a directory in your path; > /opt/local/bin for example. It's probably not a good idea to put anything in /opt/local/bin If you link it as bin/pyzord, for example, and that port later starts linking into bin on it's own, you'll receive an activation error, and you'll most likely have forgotten that you linked it yourself and not understand the error. (apologies for any assumptions about your technical memory skills) It might be better to link into ~/local/bin or somewhere else that's completely under your control. -- arno s hautala /-| arno at alum.wpi.edu pgp b2c9d448 From jimpaulgriffin at gmail.com Sat Jul 7 11:37:38 2012 From: jimpaulgriffin at gmail.com (Jamie Paul Griffin) Date: Sat, 7 Jul 2012 19:37:38 +0100 Subject: What has MacPorts Installed for py27-iPython? In-Reply-To: References: <2A2DC283-8BE6-42DC-BF32-F86C70DC88A0@gmail.com> <20120707135751.GA6457@macmini.kode5.net> Message-ID: <20120707183738.GB6457@macmini.kode5.net> On Sat, Jul 07, 2012 at 10:19:28AM -0400, Arno Hautala wrote: > On Sat, Jul 7, 2012 at 9:57 AM, Jamie Paul Griffin > wrote: > > > > I experienced a similar issue when I installed pyzor (not from Macports > > but build manually using the Macports installed python2.7) and the > > binary pyzord was installed in: > > > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/pyzord > > > > You can just use a symlink to the binary into a directory in your path; > > /opt/local/bin for example. > > It's probably not a good idea to put anything in /opt/local/bin > If you link it as bin/pyzord, for example, and that port later starts > linking into bin on it's own, you'll receive an activation error, and > you'll most likely have forgotten that you linked it yourself and not > understand the error. (apologies for any assumptions about your > technical memory skills) > > It might be better to link into ~/local/bin or somewhere else that's > completely under your control. It wasn't a port though, I built pyzor from source only I used the port built python2.7 to build it so I can't forsee any issues there but it's a good point to remember none the less. Maybe i'm wrong, though? Jamie From nad at acm.org Sat Jul 7 13:17:06 2012 From: nad at acm.org (Ned Deily) Date: Sat, 07 Jul 2012 13:17:06 -0700 Subject: What has MacPorts Installed for py27-iPython? References: <2A2DC283-8BE6-42DC-BF32-F86C70DC88A0@gmail.com> <20120707135751.GA6457@macmini.kode5.net> <20120707183738.GB6457@macmini.kode5.net> Message-ID: In article <20120707183738.GB6457 at macmini.kode5.net>, Jamie Paul Griffin wrote: > On Sat, Jul 07, 2012 at 10:19:28AM -0400, Arno Hautala wrote: > > On Sat, Jul 7, 2012 at 9:57 AM, Jamie Paul Griffin > > wrote: > > > > > > I experienced a similar issue when I installed pyzor (not from Macports > > > but build manually using the Macports installed python2.7) and the > > > binary pyzord was installed in: > > > > > > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/pyzord > > > > > > You can just use a symlink to the binary into a directory in your path; > > > /opt/local/bin for example. > > > > It's probably not a good idea to put anything in /opt/local/bin > > If you link it as bin/pyzord, for example, and that port later starts > > linking into bin on it's own, you'll receive an activation error, and > > you'll most likely have forgotten that you linked it yourself and not > > understand the error. (apologies for any assumptions about your > > technical memory skills) > > > > It might be better to link into ~/local/bin or somewhere else that's > > completely under your control. > > It wasn't a port though, I built pyzor from source only I used the port > built python2.7 to build it so I can't forsee any issues there but it's a > good point > to remember none the less. Maybe i'm wrong, though? Another solution is to add the framework bin directory to your PATH: export PATH=\ /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin:$PATH or, possibly, to use the default MacPorts python: export PATH=\ /opt/local/Library/Frameworks/Python.framework/Versions/Current/bin:$PATH -- Ned Deily, nad at acm.org From arno at alum.wpi.edu Sat Jul 7 13:20:02 2012 From: arno at alum.wpi.edu (Arno Hautala) Date: Sat, 7 Jul 2012 16:20:02 -0400 Subject: What has MacPorts Installed for py27-iPython? In-Reply-To: <20120707183738.GB6457@macmini.kode5.net> References: <2A2DC283-8BE6-42DC-BF32-F86C70DC88A0@gmail.com> <20120707135751.GA6457@macmini.kode5.net> <20120707183738.GB6457@macmini.kode5.net> Message-ID: On Sat, Jul 7, 2012 at 2:37 PM, Jamie Paul Griffin wrote: > On Sat, Jul 07, 2012 at 10:19:28AM -0400, Arno Hautala wrote: > >> It might be better to link into ~/local/bin or somewhere else that's >> completely under your control. > > It wasn't a port though, I built pyzor from source only I used the port > built python2.7 to build it so I can't forsee any issues there but it's a good point > to remember none the less. Maybe i'm wrong, though? Ah, gotcha. But, yeah, even in that case installing anything into the MacPorts prefix that wasn't put there by MacPorts could cause problems if MacPorts notices it. Unless you're prepared to handle whatever issues crop up. It's just a pain when someone does something not supported and then wants support. -- arno s hautala /-| arno at alum.wpi.edu pgp b2c9d448 From jeremy at lavergne.gotdns.org Sat Jul 7 13:22:59 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Sat, 7 Jul 2012 16:22:59 -0400 Subject: What has MacPorts Installed for py27-iPython? In-Reply-To: References: <2A2DC283-8BE6-42DC-BF32-F86C70DC88A0@gmail.com> <20120707135751.GA6457@macmini.kode5.net> <20120707183738.GB6457@macmini.kode5.net> Message-ID: > Another solution is to add the framework bin directory to your PATH: > > export PATH=\ > /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin:$PATH > > or, possibly, to use the default MacPorts python: > > export PATH=\ > /opt/local/Library/Frameworks/Python.framework/Versions/Current/bin:$PATH The way MacPorts would do it is create symlinks to all the binaries and suffix them with the version of Python they were installed under. For example, if there's a binary called pyzor in /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin, there could be a symlink in /opt/local/bin called pyzor-2.7. I'm kind of curious why you don't just create a Portfile to install your software, letting MacPorts keep track of it for you and making these symlinks automatically. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From tramir at hotmail.com Sat Jul 7 16:14:03 2012 From: tramir at hotmail.com (Mircea Trandafir) Date: Sat, 7 Jul 2012 19:14:03 -0400 Subject: kmymoney4-devel and gpg Message-ID: Hi all, I installed kmymoney4-devel and I'm trying to use my GPG-encrypted file from linux, but when I go to Preferences-Encryption, the "Use GPG Encryption" check box is greyed out. I have both gpg and pinentry installed (I think they were installed automatically as dependencies of kmymoney). I searched on Google for some help but couldn't find anything on setting up GPG with kmymoney on Mac. Does anybody have an idea what I'm doing wrong? Any suggestions are very much appreciated. Thanks, Mircea From jimpaulgriffin at gmail.com Sat Jul 7 21:39:23 2012 From: jimpaulgriffin at gmail.com (Jamie Paul Griffin) Date: Sun, 8 Jul 2012 05:39:23 +0100 Subject: What has MacPorts Installed for py27-iPython? In-Reply-To: References: <2A2DC283-8BE6-42DC-BF32-F86C70DC88A0@gmail.com> <20120707135751.GA6457@macmini.kode5.net> <20120707183738.GB6457@macmini.kode5.net> Message-ID: <20120708043923.GA7348@macmini.kode5.net> On Sat, Jul 07, 2012 at 04:22:59PM -0400, Jeremy Lavergne wrote: > The way MacPorts would do it is create symlinks to all the binaries and suffix them with the version of Python they were installed under. For example, if there's a binary called pyzor in /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin, there could be a symlink in /opt/local/bin called pyzor-2.7. > > I'm kind of curious why you don't just create a Portfile to install your software, letting MacPorts keep track of it for you and making these symlinks automatically. Simply because I've never created a portfile before and I wasn't aware of the benefits of doing so until you just pointed that out. pyzor needs py-gdbm and the easiest way of installing that was by using the Macports system and so it simply led from that really. But, i'll certainly read-up on how to create one and do it, as you suggested. It does make a lot of sense. Jamie From jimpaulgriffin at gmail.com Sat Jul 7 21:43:10 2012 From: jimpaulgriffin at gmail.com (Jamie Paul Griffin) Date: Sun, 8 Jul 2012 05:43:10 +0100 Subject: What has MacPorts Installed for py27-iPython? In-Reply-To: <20120708043923.GA7348@macmini.kode5.net> References: <2A2DC283-8BE6-42DC-BF32-F86C70DC88A0@gmail.com> <20120707135751.GA6457@macmini.kode5.net> <20120707183738.GB6457@macmini.kode5.net> <20120708043923.GA7348@macmini.kode5.net> Message-ID: <20120708044310.GB7348@macmini.kode5.net> Also ... sorry to the OP for creating a digression from the original issue Jamie From bradley.kevin at me.com Sat Jul 7 23:49:49 2012 From: bradley.kevin at me.com (Kevin Bradley) Date: Sun, 08 Jul 2012 01:49:49 -0500 Subject: Trouble building Pallet app Message-ID: Hi all, I'm trying to build the Pallet app but I'm getting an error. I've already reset xcode-select to /Developer since the release of Xcode 4.3. Here's the error log entries of the build. Can anyone decipher what is wrong? Thanks in advance for any help. :info:build === BUILD NATIVE TARGET Pallet OF PROJECT Pallet WITH CONFIGURATION Release === :info:build Check dependencies :info:build :info:build ProcessPCH /var/folders/sk/nbx46y5x79v1r9v_j99j7mch0000gr/C/com.apple.Xcode.504/SharedPrecompiledHeaders/Pallet_Prefix-bqhacddmvrmdqvgttlixmpngutae/Pallet_Prefix.pch.gch Pallet_Prefix.pch normal x86_64 objective-c com.apple.compilers.llvmgcc42 :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet :info:build setenv LANG en_US.US-ASCII :info:build /Developer/usr/bin/llvm-gcc-4.2 -x objective-c-header -arch x86_64 -fmessage-length=0 -pipe -std=c99 -Wno-trigraphs -fpascal-strings -Os -Wreturn-type -Wunused-variable -fasm-blocks -fobjc-gc-only -mmacosx-version-min=10.7 -gdwarf-2 -fvisibility=hidden -iquote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet/build/Pallet.build/Release/Pallet.build/Pallet-generated-files.hmap -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet/build/Pallet.build/Release/Pallet.build/Pallet-own-target-headers.hmap -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet/build/Pallet.build/Release/Pallet.build/Pallet-all-target-headers.hmap -iquote /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet/build/Pallet.build/Release/Pallet.build/Pallet-project-headers.hmap -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet/build/Release/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet/build/Pallet.build/Release/Pallet.build/DerivedSources/x86_64 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet/build/Pallet.build/Release/Pallet.build/DerivedSources -F/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet/build/Release -F/opt/local/Library/Frameworks -FGrowl-1.2.1-Framework -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet/Pallet_Prefix.pch -o /var/folders/sk/nbx46y5x79v1r9v_j99j7mch0000gr/C/com.apple.Xcode.504/SharedPrecompiledHeaders/Pallet_Prefix-bqhacddmvrmdqvgttlixmpngutae/Pallet_Prefix.pch.gch :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet/Pallet_Prefix.pch:6:28: error: Cocoa/Cocoa.h: No such file or directory :info:build :info:build :info:build ** BUILD FAILED ** :info:build :info:build :info:build The following build commands failed: :info:build ProcessPCH /var/folders/sk/nbx46y5x79v1r9v_j99j7mch0000gr/C/com.apple.Xcode.504/SharedPrecompiledHeaders/Pallet_Prefix-bqhacddmvrmdqvgttlixmpngutae/Pallet_Prefix.pch.gch Pallet_Prefix.pch normal x86_64 objective-c com.apple.compilers.llvmgcc42 :info:build (1 failure) :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet" && /usr/bin/xcodebuild -target "Pallet" -configuration Release build OBJROOT=build/ SYMROOT=build/ MACOSX_DEPLOYMENT_TARGET=10.7 ARCHS=x86_64 SDKROOT="" GCC_VERSION=com.apple.compilers.llvmgcc42 FRAMEWORK_SEARCH_PATHS='/opt/local/Library/Frameworks Growl-1.2.1-Framework' :info:build Exit code: 65 :error:build org.macports.build for port Pallet returned: command execution failed :debug:build Error code: NONE :debug:build Backtrace: command execution failed while executing "$procedure $targetname" :info:build Warning: targets not executed for Pallet: org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Please see the log file for port Pallet for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/main.log Kevin Bradley bradley.kevin at me.com -- "We believe that the Universe itself is conscious in a way we can never truly understand. It is engaged in a search for meaning, so it breaks itself apart, investing its own consciousness in every form of life. We are the Universe, trying to explain itself." Delenn, "Babylon 5" in "Passing Through Gethesemane" From ryandesign at macports.org Sun Jul 8 00:15:13 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 8 Jul 2012 02:15:13 -0500 Subject: Trouble building Pallet app In-Reply-To: References: Message-ID: On Jul 8, 2012, at 01:49, Kevin Bradley wrote: > :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/work/Pallet/Pallet_Prefix.pch:6:28: error: Cocoa/Cocoa.h: No such file or directory There are many open tickets for build and runtime problems with Pallet, but this might be a new one. If the problem persists after cleaning and trying again, please file a bug report, and attach this file: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_Pallet/Pallet/main.log However, since Pallet currently has no maintainer, we could really use a volunteer to clean Pallet up a bit and get it working again. From MK-MacPorts at techno.ms Sun Jul 8 00:47:45 2012 From: MK-MacPorts at techno.ms (=?iso-8859-1?Q?Marko_K=E4ning?=) Date: Sun, 8 Jul 2012 09:47:45 +0200 Subject: kmymoney4-devel and gpg In-Reply-To: References: Message-ID: <2AA6B820-24AE-416F-B97D-A8B8BDD66CB9@techno.ms> On Jul 8, 2012, at 1:14 AM, Mircea Trandafir wrote: > help but couldn't find anything on setting up GPG with kmymoney on Mac. Does anybody have an idea what I'm doing wrong? Any suggestions are very much appreciated. Hi Mircea, I am maintaining KMM4 on MacPorts and will try to help out here. I myself have never used GPG with KMyMoney, neither on Linux nor on the Mac. But I'll research it myself a little (also hope for response from the list) and contact KMM's developers on their own list. Please be patient as it might take a while to solve this issue. Greets, Marko From MK-MacPorts at techno.ms Sun Jul 8 01:13:38 2012 From: MK-MacPorts at techno.ms (=?iso-8859-1?Q?Marko_K=E4ning?=) Date: Sun, 8 Jul 2012 10:13:38 +0200 Subject: kmymoney4-devel and gpg In-Reply-To: References: Message-ID: <4FD7DDA3-89DC-4861-A5A9-29A229EE7777@techno.ms> Turns out it does work on my end. Please verify on the console that your GPG is properly set up. What does "gpg --list-keys" show? From MK-MacPorts at techno.ms Sun Jul 8 01:20:39 2012 From: MK-MacPorts at techno.ms (=?iso-8859-1?Q?Marko_K=E4ning?=) Date: Sun, 8 Jul 2012 10:20:39 +0200 Subject: kmymoney4-devel and gpg In-Reply-To: References: Message-ID: And now I realize that the reason that it works for me now is probably that I have MacGPG2 installed (which enables GPG in Mail.app). Its gpg-agent is running and successfully hands out my keys also to KMyMoney. MacGPG2 isn't installed through MacPorts though! So, are you sure that you've got a gpg-agent up and running on your end? From tramir at hotmail.com Sun Jul 8 14:13:50 2012 From: tramir at hotmail.com (Mircea Trandafir) Date: Sun, 8 Jul 2012 17:13:50 -0400 Subject: kmymoney4-devel and gpg In-Reply-To: References: Message-ID: Hi Marko, Thanks so much for getting back to me. Indeed, it seems that no gpg-agent was running, although I tried to get the macports one to start in a terminal. I installed MacGPG2 and now things have progressed: I can enable GPG encryption in KMM and save encrypted files, but I can't open encrypted files. It seems that pinentry is not called and I get an error for "bad passphrase". Can you please check if you can open encrypted files with your setup? You can just create a new (empty) file, save it encrypted and then try to re-open it. Thanks again, Mircea On 12-07-08 4:20 AM, Marko K?ning wrote: > And now I realize that the reason that it works for me now is probably that I have MacGPG2 installed (which enables GPG in Mail.app). Its gpg-agent is running and successfully hands out my keys also to KMyMoney. > > MacGPG2 isn't installed through MacPorts though! > > > > So, are you sure that you've got a gpg-agent up and running on your end? > -- Mircea Trandafir Professeur adjoint / Assistant professor D?partement d'?conomique, Universit? de Sherbrooke 2500, boul. de l'Universit? Sherbrooke (Qu?bec) CANADA J1K 2R1 Tel: +1 (819) 821-8000 #61358 Email: mircea.trandafir at usherbrooke.ca Web: http://pages.usherbrooke.ca/mtrandafir From ktan at realityartisans.com Mon Jul 9 05:02:51 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 09 Jul 2012 08:02:51 -0400 Subject: Error on "sudo port -v upgrade outdated" Message-ID: <4FFAC86B.5020307@realityartisans.com> I first executed the following: sudo port -v selfupdate which chugged along and successfully concluded. Then I followed the instructions in the successful conclusion by issuing a: sudo port -v upgrade outdated and after a couple of hours, got the following error along a snippet of the last few lines before it crashed and burned: libtool: compile: /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I../.. -I./../.. -I./.. -I/opt/local/include -I/opt/local/include -DINET6 -DG_DISABLE_DEPRECATED -DG_DISABLE_SINGLE_INCLUDES -DGSEAL_ENABLE -DGTK_DISABLE_DEPRECATED -DGTK_DISABLE_SINGLE_INCLUDES -D_FORTIFY_SOURCE=2 "-D_U_=__attribute__((unused))" -I/opt/local/include -I/opt/local/include -I/opt/local/include -I/opt/local/include -DPLUGIN_DIR=\"/opt/local/lib/wireshark/plugins/1.8.0\" -no-cpp-precomp -O2 -arch ppc -Wall -W -Wextra -Wdeclaration-after-statement -Wendif-labels -Wpointer-arith -Wno-pointer-sign -Wcast-align -Wformat-security -Wold-style-definition -D_REENTRANT -I/opt/local/include/gtk-2.0 -I/opt/local/lib/gtk-2.0/include -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo -I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include/pango-1.0 -I/opt/local/include/gio-unix-2.0/ -I/opt/local/include -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 -I/opt/local/include/libpng14 -MT packet-rrc.lo -MD -MP -MF .deps/packet-rrc.Tpo -c packet-rrc.c -fno-common -DPIC -o .libs/packet-rrc.o ../../asn1/rrc/rrc.cnf: In function 'dissect_rrc_INTEGER_M2147483648_2147483647': ../../asn1/rrc/rrc.cnf:2288: warning: this decimal constant is unsigned only in ISO C90 ../../asn1/rrc/rrc.cnf: In function 'dissect_rrc_T_v590NonCriticalExtensions_24': ../../asn1/rrc/rrc.cnf:639: internal compiler error: Bus error Please submit a full bug report, with preprocessed source if appropriate. See for instructions. make[5]: *** [packet-rrc.lo] Error 1 make[5]: *** Waiting for unfinished jobs.... packet-parlay.c:82294: warning: 'decode_org_csapi_fw_TpLoadPolicy_st' defined but not used packet-parlay.c:82360: warning: 'decode_org_csapi_fw_TpLoadInitVal_st' defined but not used packet-parlay.c:83511: warning: 'decode_org_csapi_ui_TpUIEventInfo_st' defined but not used make[5]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/wireshark/work/wireshark-1.8.0/epan/dissectors' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/wireshark/work/wireshark-1.8.0/epan/dissectors' make[3]: *** [all] Error 2 make[3]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/wireshark/work/wireshark-1.8.0/epan/dissectors' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/wireshark/work/wireshark-1.8.0/epan' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/wireshark/work/wireshark-1.8.0' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/wireshark/work/wireshark-1.8.0' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/wireshark/work/wireshark-1.8.0" && /usr/bin/make -j2 -w all Exit code: 2 Error: org.macports.build for port wireshark returned: command execution failed Warning: targets not executed for wireshark: org.macports.install org.macports.build org.macports.destroot Please see the log file for port wireshark for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/wireshark/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Any suggestions as to how to proceed short of just filing a bug report? The system is a dual 2GHz PPC tower running 10.5.8 with all patches applied (i.e., Software Update reports that all software is up to date). Thanks in advance. -- Reality Artisans, Inc. # Network Wrangling and Delousing P.O. Box 565, Gracie Station # Apple Certified Consultant New York, NY 10028-0019 # Apple Consultants Network member # Apple Developer Connection member (212) 369-4876 (Voice) # My PGP public key can be found at -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From jeremy at lavergne.gotdns.org Mon Jul 9 05:08:25 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Mon, 9 Jul 2012 08:08:25 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <4FFAC86B.5020307@realityartisans.com> References: <4FFAC86B.5020307@realityartisans.com> Message-ID: <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> > ../../asn1/rrc/rrc.cnf:639: internal compiler error: Bus error > Please submit a full bug report, > with preprocessed source if appropriate. > See for instructions. Check your /Library/Logs/CrashReporter for a crash from around the time the error occurred. Since it's such an old system (gcc-4.0), not sure Apple will do anything for you. Might be worth using a newer compiler from MacPorts (clang-3.1 or at least gcc-4.2). -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From jonesc at hep.phy.cam.ac.uk Mon Jul 9 05:33:42 2012 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Mon, 09 Jul 2012 13:33:42 +0100 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> Message-ID: <4FFACFA6.9040207@hep.phy.cam.ac.uk> On 09/07/12 13:08, Jeremy Lavergne wrote: >> ../../asn1/rrc/rrc.cnf:639: internal compiler error: Bus error >> Please submit a full bug report, >> with preprocessed source if appropriate. >> See for instructions. > > Check your /Library/Logs/CrashReporter for a crash from around the time the error occurred. > > Since it's such an old system (gcc-4.0), not sure Apple will do anything for you. Might be worth using a newer compiler from MacPorts (clang-3.1 or at least gcc-4.2). Might also be worth checking what version of Xcode the OP has installed ? The latest version, AFAIK, that can be used with OSX 10.5 is Xocde 3.1.4, which provides gcc 4.2. The fact the OP is using the older gcc 4.0 suggests they have an older Xcode installed. If so, upgrade your Xocde and try again. cheers Chris > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From ktan at realityartisans.com Mon Jul 9 05:42:11 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 09 Jul 2012 08:42:11 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> Message-ID: <4FFAD1A3.40409@realityartisans.com> On 7/9/12 08:08, Jeremy Lavergne wrote: >> ../../asn1/rrc/rrc.cnf:639: internal compiler error: Bus error >> Please submit a full bug report, >> with preprocessed source if appropriate. >> See for instructions. > Check your /Library/Logs/CrashReporter for a crash from around the time the error occurred. > > Since it's such an old system (gcc-4.0), not sure Apple will do anything for you. Might be worth using a newer compiler from MacPorts (clang-3.1 or at least gcc-4.2). Would that be /Library/Logs/CrashReporter or ~/Library/Logs/CrashReporter? I see many crash files in both but none that might be relevant. Any particularly named one? I'm trying to update everything with the "sudo port -v upgrade outdated". Wouldn't that also upgrade that? Firing up Software Update doesn't do anything for me. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From jeremy at lavergne.gotdns.org Mon Jul 9 05:44:32 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Mon, 9 Jul 2012 08:44:32 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <4FFAD1A3.40409@realityartisans.com> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFAD1A3.40409@realityartisans.com> Message-ID: > Would that be /Library/Logs/CrashReporter or ~/Library/Logs/CrashReporter? I see many crash files in both but none that might be relevant. Any particularly named one? It would probably be in / if you're using `sudo port...` and ~/ if using `port...`. My guess is the crash log would start with gcc in the name. > I'm trying to update everything with the "sudo port -v upgrade outdated". Wouldn't that also upgrade that? Firing up Software Update doesn't do anything for me. Also note that Xcode is not updated via Mac OS X's Software Update utility on OS versions prior to 10.6, and is updated via the Mac App Store on 10.7. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From ktan at realityartisans.com Mon Jul 9 05:46:36 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 09 Jul 2012 08:46:36 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <4FFACFA6.9040207@hep.phy.cam.ac.uk> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> Message-ID: <4FFAD2AC.4070300@realityartisans.com> On 7/9/12 08:33, Chris Jones wrote: > On 09/07/12 13:08, Jeremy Lavergne wrote: >>> ../../asn1/rrc/rrc.cnf:639: internal compiler error: Bus error >>> Please submit a full bug report, >>> with preprocessed source if appropriate. >>> See for instructions. >> >> Check your /Library/Logs/CrashReporter for a crash from around the >> time the error occurred. >> >> Since it's such an old system (gcc-4.0), not sure Apple will do >> anything for you. Might be worth using a newer compiler from MacPorts >> (clang-3.1 or at least gcc-4.2). > > Might also be worth checking what version of Xcode the OP has > installed ? The latest version, AFAIK, that can be used with OSX 10.5 > is Xocde 3.1.4, which provides gcc 4.2. The fact the OP is using the > older gcc 4.0 suggests they have an older Xcode installed. If so, > upgrade your Xocde and try again. > > cheers Chris > I'm the OP. I indeed have Xcode 3.1.4 installed (I checked) but when I went to the Terminal and did a "gcc -v", I have version 4.0.1, which is what came with Xcode 3.1.4. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From ktan at realityartisans.com Mon Jul 9 05:50:03 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 09 Jul 2012 08:50:03 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFAD1A3.40409@realityartisans.com> Message-ID: <4FFAD37B.9080309@realityartisans.com> On 7/9/12 08:44, Jeremy Lavergne wrote: >> Would that be /Library/Logs/CrashReporter or ~/Library/Logs/CrashReporter? I see many crash files in both but none that might be relevant. Any particularly named one? > It would probably be in / if you're using `sudo port...` and ~/ if using `port...`. > > My guess is the crash log would start with gcc in the name. I just took a look in both places mentioned above: Nothing with gcc anywhere in the name. >> I'm trying to update everything with the "sudo port -v upgrade outdated". Wouldn't that also upgrade that? Firing up Software Update doesn't do anything for me. > Also note that Xcode is not updated via Mac OS X's Software Update utility on OS versions prior to 10.6, and is updated via the Mac App Store on 10.7. Okay. I'll start dredging in developer.apple.com to see if there's a Xcode 3.1.5 or later. I definitely have 3.1.4 installed and it came with gcc 4.0.1. IIRC, I don't think Apple provides compilers separate from their IDE. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From jeremy at lavergne.gotdns.org Mon Jul 9 05:50:09 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Mon, 9 Jul 2012 08:50:09 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <4FFAD2AC.4070300@realityartisans.com> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> <4FFAD2AC.4070300@realityartisans.com> Message-ID: > I'm the OP. I indeed have Xcode 3.1.4 installed (I checked) but when I went to the Terminal and did a "gcc -v", I have version 4.0.1, which is what came with Xcode 3.1.4. You might see what all GCCs are installed. gcc[tab][tab] or just see where gcc is located or is symlinked. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From jonesc at hep.phy.cam.ac.uk Mon Jul 9 05:52:30 2012 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Mon, 09 Jul 2012 13:52:30 +0100 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <4FFAD2AC.4070300@realityartisans.com> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> <4FFAD2AC.4070300@realityartisans.com> Message-ID: <4FFAD40E.2040003@hep.phy.cam.ac.uk> Hi, >> Might also be worth checking what version of Xcode the OP has >> installed ? The latest version, AFAIK, that can be used with OSX 10.5 >> is Xocde 3.1.4, which provides gcc 4.2. The fact the OP is using the >> older gcc 4.0 suggests they have an older Xcode installed. If so, >> upgrade your Xocde and try again. >> >> cheers Chris >> > I'm the OP. I indeed have Xcode 3.1.4 installed (I checked) but when I > went to the Terminal and did a "gcc -v", I have version 4.0.1, which is > what came with Xcode 3.1.4. OK. According to http://adcdownload.apple.com/Developer_Tools/xcode_3.1.4_developer_tools/about_xcode_tools_3.1.4.pdf GCC 4.2 & LLVM GCC 4.2 are available as optional compilers. So perhaps not the default (not that what you get running 'gcc -v' at the command line necessarily matches MacPorts own default). I'm surprised MacPorts does not use gcc 4.2 by default it it is there ? That said, its been a long while since I used OSX 10.5 (and never a PPC version). Chris > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From ktan at realityartisans.com Mon Jul 9 05:56:05 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 09 Jul 2012 08:56:05 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> <4FFAD2AC.4070300@realityartisans.com> Message-ID: <4FFAD4E5.2090804@realityartisans.com> On 7/9/12 08:50, Jeremy Lavergne wrote: >> I'm the OP. I indeed have Xcode 3.1.4 installed (I checked) but when I went to the Terminal and did a "gcc -v", I have version 4.0.1, which is what came with Xcode 3.1.4. > You might see what all GCCs are installed. > gcc[tab][tab] or just see where gcc is located or is symlinked. > gcc[tab][tab] gave me 108 possibilities, none of which applied. I did a "which gcc" and it gave me: /usr/bin/gcc and that's what gives me version 4.0.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From jeremy at lavergne.gotdns.org Mon Jul 9 06:00:00 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Mon, 9 Jul 2012 09:00:00 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <4FFAD4E5.2090804@realityartisans.com> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> <4FFAD2AC.4070300@realityartisans.com> <4FFAD4E5.2090804@realityartisans.com> Message-ID: > gcc[tab][tab] gave me 108 possibilities, none of which applied. I did a "which gcc" and it gave me: > > /usr/bin/gcc > > and that's what gives me version 4.0.1. Sounds like you only have gcc in /usr/bin then. Is it a symlink? ls -l /usr/bin/gcc -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From ktan at realityartisans.com Mon Jul 9 06:12:09 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 09 Jul 2012 09:12:09 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> <4FFAD2AC.4070300@realityartisans.com> <4FFAD4E5.2090804@realityartisans.com> Message-ID: <4FFAD8A9.7050202@realityartisans.com> On 7/9/12 09:00, Jeremy Lavergne wrote: >> gcc[tab][tab] gave me 108 possibilities, none of which applied. I did a "which gcc" and it gave me: >> >> /usr/bin/gcc >> >> and that's what gives me version 4.0.1. > Sounds like you only have gcc in /usr/bin then. Is it a symlink? > ls -l /usr/bin/gcc Hmmm, it looks like gcc is a symlink to gcc-4.0. There seems to be a whole lot of things in /usr/bin that have both 4.0.1 and 4.2.1 versions. I'm wondering if I change the symlink to 4.2.1, what else will break: Don't the dynamic libraries, etc., also have to match, not mention the linker, etc.? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From jonesc at hep.phy.cam.ac.uk Mon Jul 9 06:14:58 2012 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Mon, 09 Jul 2012 14:14:58 +0100 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <4FFAD8A9.7050202@realityartisans.com> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> <4FFAD2AC.4070300@realityartisans.com> <4FFAD4E5.2090804@realityartisans.com> <4FFAD8A9.7050202@realityartisans.com> Message-ID: <4FFAD952.5090907@hep.phy.cam.ac.uk> Hi, On 09/07/12 14:12, Kok-Yong Tan wrote: > On 7/9/12 09:00, Jeremy Lavergne wrote: >>> gcc[tab][tab] gave me 108 possibilities, none of which applied. I did >>> a "which gcc" and it gave me: >>> >>> /usr/bin/gcc >>> >>> and that's what gives me version 4.0.1. >> Sounds like you only have gcc in /usr/bin then. Is it a symlink? >> ls -l /usr/bin/gcc > > Hmmm, it looks like gcc is a symlink to gcc-4.0. > > There seems to be a whole lot of things in /usr/bin that have both 4.0.1 > and 4.2.1 versions. I'm wondering if I change the symlink to 4.2.1, what > else will break: Don't the dynamic libraries, etc., also have to match, > not mention the linker, etc.? Don't fiddle with the sym links in /usr/bin by hand !! You will for sure break something. MacPorts doesn't need the compiler to be 'usr/bin/gcc' in order to use it. It will happily used the versioned binaries in there directly, if configured to do so. Chris > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From ktan at realityartisans.com Mon Jul 9 06:17:49 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 09 Jul 2012 09:17:49 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <4FFAD952.5090907@hep.phy.cam.ac.uk> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> <4FFAD2AC.4070300@realityartisans.com> <4FFAD4E5.2090804@realityartisans.com> <4FFAD8A9.7050202@realityartisans.com> <4FFAD952.5090907@hep.phy.cam.ac.uk> Message-ID: <4FFAD9FD.1090203@realityartisans.com> On 7/9/12 09:14, Chris Jones wrote: > Hi, > > On 09/07/12 14:12, Kok-Yong Tan wrote: >> On 7/9/12 09:00, Jeremy Lavergne wrote: >>>> gcc[tab][tab] gave me 108 possibilities, none of which applied. I did >>>> a "which gcc" and it gave me: >>>> >>>> /usr/bin/gcc >>>> >>>> and that's what gives me version 4.0.1. >>> Sounds like you only have gcc in /usr/bin then. Is it a symlink? >>> ls -l /usr/bin/gcc >> >> Hmmm, it looks like gcc is a symlink to gcc-4.0. >> >> There seems to be a whole lot of things in /usr/bin that have both 4.0.1 >> and 4.2.1 versions. I'm wondering if I change the symlink to 4.2.1, what >> else will break: Don't the dynamic libraries, etc., also have to match, >> not mention the linker, etc.? > > Don't fiddle with the sym links in /usr/bin by hand !! You will for > sure break something. > > MacPorts doesn't need the compiler to be 'usr/bin/gcc' in order to use > it. It will happily used the versioned binaries in there directly, if > configured to do so. > > Chris So noted. I haven't done anything yet. However, it seems apparent that I've got to change *SOMETHING* to get MacPorts to compile... -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From jeremy at lavergne.gotdns.org Mon Jul 9 06:19:02 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Mon, 9 Jul 2012 09:19:02 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <4FFAD952.5090907@hep.phy.cam.ac.uk> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> <4FFAD2AC.4070300@realityartisans.com> <4FFAD4E5.2090804@realityartisans.com> <4FFAD8A9.7050202@realityartisans.com> <4FFAD952.5090907@hep.phy.cam.ac.uk> Message-ID: > Don't fiddle with the sym links in /usr/bin by hand !! You will for sure break something. > > MacPorts doesn't need the compiler to be 'usr/bin/gcc' in order to use it. It will happily used the versioned binaries in there directly, if configured to do so. Try building the failed package X again: sudo port clean X sudo port install X configure.compiler=gcc-4.2 MacPorts chooses its default compiler based a combination of architecture and Xcode version ( src/port1.0/portconfigure.tcl's portconfigure::get_compiler_fallback). I believe GCC 4.0 should only get used if Xcode 3.2 with OS X 10.4. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From jonesc at hep.phy.cam.ac.uk Mon Jul 9 06:22:07 2012 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Mon, 09 Jul 2012 14:22:07 +0100 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <4FFAD9FD.1090203@realityartisans.com> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> <4FFAD2AC.4070300@realityartisans.com> <4FFAD4E5.2090804@realityartisans.com> <4FFAD8A9.7050202@realityartisans.com> <4FFAD952.5090907@hep.phy.cam.ac.uk> <4FFAD9FD.1090203@realityartisans.com> Message-ID: <4FFADAFF.5080408@hep.phy.cam.ac.uk> Hi, > So noted. I haven't done anything yet. However, it seems apparent that > I've got to change *SOMETHING* to get MacPorts to compile... Jeremy beat me to it ! AFAIK, MacPorts should already be using gcc 4.2 with your combination of Xcode and OSX. I don't know why its using gcc 4.0 - Does it do this for all ports, or just the one that fails ? - Have you altered your macports.conf file at all ? cheers Chris From ktan at realityartisans.com Mon Jul 9 06:27:25 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 09 Jul 2012 09:27:25 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <4FFADAFF.5080408@hep.phy.cam.ac.uk> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> <4FFAD2AC.4070300@realityartisans.com> <4FFAD4E5.2090804@realityartisans.com> <4FFAD8A9.7050202@realityartisans.com> <4FFAD952.5090907@hep.phy.cam.ac.uk> <4FFAD9FD.1090203@realityartisans.com> <4FFADAFF.5080408@hep.phy.cam.ac.uk> Message-ID: <4FFADC3D.6040704@realityartisans.com> On 7/9/12 09:22, Chris Jones wrote: > Hi, > > >> So noted. I haven't done anything yet. However, it seems apparent that >> I've got to change *SOMETHING* to get MacPorts to compile... > > Jeremy beat me to it ! AFAIK, MacPorts should already be using gcc 4.2 > with your combination of Xcode and OSX. I don't know why its using gcc > 4.0 > > - Does it do this for all ports, or just the one that fails ? > > - Have you altered your macports.conf file at all ? > > cheers Chris Nah, I don't fiddle with the macports.conf file. I just issue commands on the MacPorts level (i.e., "sudo port -v ...") and refrain from touching any config files. I have tried upgrading individual ports--hoping that a "sudo port -v upgrade outdated" will take care of all of them (including recursive upgrades) for me. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From spooky130u at gmail.com Mon Jul 9 06:44:59 2012 From: spooky130u at gmail.com (Jim Graham) Date: Mon, 9 Jul 2012 08:44:59 -0500 Subject: Muttprint install and iconv Message-ID: <20120709134459.GA68053@gmail.com> port install muttprint installs both muttprint and text-iconv. However, when I try to use muttprint to print an e-mail message from Mutt, I get an error screen saying Text::Iconv doesn't exist. I don't know PERL, but I tried editing muttprint anyways to point it directly to /opt/local/bin/iconv, and needless to say, it didn't work.... Suggestions? Did I miss something that I was supposed to do? Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) | "> There it was, right in the title bar: spooky130u at gmail.com | > Microsoft Operations POS." < Running Mac OS X Lion > | ICBM / Hurricane: | "Never before has a TLA been so appropriately 30.44406N 86.59909W | mis-parsed." (alt.sysadmin.recovery) Android Apps Listing at http://www.jstrack.org/barcodes.html From jeremy at lavergne.gotdns.org Mon Jul 9 06:47:51 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Mon, 9 Jul 2012 09:47:51 -0400 Subject: Muttprint install and iconv In-Reply-To: <20120709134459.GA68053@gmail.com> References: <20120709134459.GA68053@gmail.com> Message-ID: <928CAFDA-442F-4601-B313-B5B21E56A93B@lavergne.gotdns.org> > port install muttprint installs both muttprint and text-iconv. However, > when I try to use muttprint to print an e-mail message from Mutt, I get > an error screen saying Text::Iconv doesn't exist. I don't know PERL, but > I tried editing muttprint anyways to point it directly to > /opt/local/bin/iconv, and needless to say, it didn't work.... > > Suggestions? Did I miss something that I was supposed to do? That definitely looks like it's after a perl module (perhaps the port is named p5.12-text-iconv?). It's entirely possible that the perl MacPorts is using doesn't match up with the one that muttprint is using: /usr/bin/perl versus /opt/local/bin/perl5.12 Since modules get installed under each version of perl, it could be "missing". Can you edit muttprint to ensure it's looking at the same version of Perl? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From ktan at realityartisans.com Mon Jul 9 06:48:26 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 09 Jul 2012 09:48:26 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: <4FFADC3D.6040704@realityartisans.com> References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> <4FFAD2AC.4070300@realityartisans.com> <4FFAD4E5.2090804@realityartisans.com> <4FFAD8A9.7050202@realityartisans.com> <4FFAD952.5090907@hep.phy.cam.ac.uk> <4FFAD9FD.1090203@realityartisans.com> <4FFADAFF.5080408@hep.phy.cam.ac.uk> <4FFADC3D.6040704@realityartisans.com> Message-ID: <4FFAE12A.5010509@realityartisans.com> On 7/9/12 09:27, Kok-Yong Tan wrote: > On 7/9/12 09:22, Chris Jones wrote: >> Hi, >> >> >>> So noted. I haven't done anything yet. However, it seems apparent that >>> I've got to change *SOMETHING* to get MacPorts to compile... >> >> Jeremy beat me to it ! AFAIK, MacPorts should already be using gcc >> 4.2 with your combination of Xcode and OSX. I don't know why its >> using gcc 4.0 >> >> - Does it do this for all ports, or just the one that fails ? >> >> - Have you altered your macports.conf file at all ? >> >> cheers Chris > > Nah, I don't fiddle with the macports.conf file. I just issue > commands on the MacPorts level (i.e., "sudo port -v ...") and refrain > from touching any config files. I have tried upgrading individual > ports--hoping that a "sudo port -v upgrade outdated" will take care of > all of them (including recursive upgrades) for me. > Oops. That should be "I have *NOT* tried upgrading individual ports--hoping that..." -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From ktan at realityartisans.com Mon Jul 9 07:01:16 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 09 Jul 2012 10:01:16 -0400 Subject: Error on "sudo port -v upgrade outdated" In-Reply-To: References: <4FFAC86B.5020307@realityartisans.com> <1B0E1F34-1620-43F3-8753-E30FF0AD82DC@lavergne.gotdns.org> <4FFACFA6.9040207@hep.phy.cam.ac.uk> <4FFAD2AC.4070300@realityartisans.com> <4FFAD4E5.2090804@realityartisans.com> <4FFAD8A9.7050202@realityartisans.com> <4FFAD952.5090907@hep.phy.cam.ac.uk> Message-ID: <4FFAE42C.3010501@realityartisans.com> On 7/9/12 09:19, Jeremy Lavergne wrote: >> Don't fiddle with the sym links in /usr/bin by hand !! You will for sure break something. >> >> MacPorts doesn't need the compiler to be 'usr/bin/gcc' in order to use it. It will happily used the versioned binaries in there directly, if configured to do so. > Try building the failed package X again: > sudo port clean X > sudo port install X configure.compiler=gcc-4.2 Okay, I did "sudo port -v clean wireshark" and then "sudo port -v upgrade installed configure.compiler=gcc-4.2" and it seems to be compiling using the gcc-4.2 compiler explicitly now. It's chugging away and will probably take a couple of hours. Since it's now using the gcc-4.2 compiler, what about packages wireshark depends on? Don't they have to also be recompiled using the gcc-4.2 compiler? > MacPorts chooses its default compiler based a combination of architecture and Xcode version ( src/port1.0/portconfigure.tcl's portconfigure::get_compiler_fallback). I believe GCC 4.0 should only get used if Xcode 3.2 with OS X 10.4. Odd that MacPorts still defaults to gcc-4.0 if this is a 10.5 system, albeit it being a PPC system. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From brendan.simon at etrix.com.au Wed Jul 11 01:00:36 2012 From: brendan.simon at etrix.com.au (Brendan Simon (eTRIX)) Date: Wed, 11 Jul 2012 18:00:36 +1000 Subject: Request to update cppcheck to version to the latest (1.55) Message-ID: <4FFD32A4.80504@etrix.com.au> Hello, How do I request that cppcheck be updated to the latest version (1.55) ?? Can this be automated so that it is always at the latest version ?? It seems there are quite a few gaps between previous versions. e.g. 1.48, 1.44, etc. Cheers, Brendan. From ryandesign at macports.org Wed Jul 11 01:54:30 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 11 Jul 2012 03:54:30 -0500 Subject: Request to update cppcheck to version to the latest (1.55) In-Reply-To: <4FFD32A4.80504@etrix.com.au> References: <4FFD32A4.80504@etrix.com.au> Message-ID: <976850F3-5992-48B0-98F3-4252259E7601@macports.org> On Jul 11, 2012, at 03:00, Brendan Simon (eTRIX) wrote: > How do I request that cppcheck be updated to the latest version (1.55) ?? File a port update ticket in the issue tracker. See the MacPorts Guide for instructions. > Can this be automated so that it is always at the latest version ?? No. In MacPorts, a maintainer agrees to maintain a port, which means he declares that he will test new versions and submit updates to those versions. We want users to have the assurance that a port was at least tested by one person on one other machine. Automated updates would not provide that assurance. > It > seems there are quite a few gaps between previous versions. e.g. 1.48, > 1.44, etc. Then the maintainer of this port has not been actively maintaining it. You could email them and ask if they're still interested in maintaining it. If you would like to take on the responsibility of updating this port, you could ask the maintainer if you could co-maintain the port with them or take it over entirely. If you receive no response from the maintainer, you can file a port abandonment ticket requesting to take the port over. From public at francisco-garcia.net Wed Jul 11 09:41:49 2012 From: public at francisco-garcia.net (Francisco Garcia) Date: Wed, 11 Jul 2012 18:41:49 +0200 Subject: Local MacPorts build server no longer works Message-ID: Exploring the macports.conf man page I have noticed that: archive_site_local is no longer listed buildfromsource never is listed as an option, bit it is ignored. The ports are still built from source in any case Have these options changed (or been removed) in the latest releases? I have a build server which used to work in the past, but now it no longer works. I do not think I have touched any configuration of the services involved. The server in question was working according this howto https://trac.macports.org/wiki/howto/ShareArchives2 Now my client machine no longer fetches builds from my server. Instead it just decides to build itself every port In my macports.conf I have this line: archive_site_local http://myserver.local/macports/ I have verified that the address is valid and provides an index of /opt/local/var/macports/software (I am using Apache) Also I verified that my keys (from pubkeys.conf) are the same in both servers I am running out of ideas of what can be wrong and do not know how to track down this problem. How should I debug this? When I try to install a port already compiled by my server with the "-d" parameter, there is no single reference to my archive_site_local server in the output. Should I see my server listed in the output? thanks in advance! Francisco From jeremy at lavergne.gotdns.org Wed Jul 11 09:46:21 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Wed, 11 Jul 2012 12:46:21 -0400 Subject: Local MacPorts build server no longer works In-Reply-To: References: Message-ID: <92540E8B-A53A-4358-8B02-CEFAB3BC3876@lavergne.gotdns.org> Check out archive_sites.conf, added in MacPorts 2.1.0 http://trac.macports.org/browser/trunk/base/ChangeLog On Jul 11, 2012, at 12:41 , Francisco Garcia wrote: > Exploring the macports.conf man page I have noticed that: > > archive_site_local is no longer listed > buildfromsource never is listed as an option, bit it is ignored. The > ports are still built from source in any case > > Have these options changed (or been removed) in the latest releases? > > I have a build server which used to work in the past, but now it no > longer works. > I do not think I have touched any configuration of the services > involved. The server in question > was working according this howto > > https://trac.macports.org/wiki/howto/ShareArchives2 > > Now my client machine no longer fetches builds from my server. Instead > it just decides to build itself every port > > In my macports.conf I have this line: > > archive_site_local http://myserver.local/macports/ > > I have verified that the address is valid and provides an index of > /opt/local/var/macports/software (I am using Apache) > > Also I verified that my keys (from pubkeys.conf) are the same in both servers > > I am running out of ideas of what can be wrong and do not know how to > track down this problem. How should I debug this? > > When I try to install a port already compiled by my server with the > "-d" parameter, there is no single reference to my > archive_site_local server in the output. Should I see my server listed > in the output? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From allbery.b at gmail.com Wed Jul 11 09:48:20 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Wed, 11 Jul 2012 12:48:20 -0400 Subject: Local MacPorts build server no longer works In-Reply-To: References: Message-ID: On Wed, Jul 11, 2012 at 12:41 PM, Francisco Garcia < public at francisco-garcia.net> wrote: > Exploring the macports.conf man page I have noticed that: > > archive_site_local is no longer listed > buildfromsource never is listed as an option, bit it is ignored. The > ports are still built from source in any case > "buildfromsource" works fine for me; i used it literally yesterday (set to never, upgraded packages, later when I had the leisure set back to ifneeded and upgraded the rest). -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From public at francisco-garcia.net Wed Jul 11 09:59:54 2012 From: public at francisco-garcia.net (Francisco Garcia) Date: Wed, 11 Jul 2012 18:59:54 +0200 Subject: Local MacPorts build server no longer works In-Reply-To: <92540E8B-A53A-4358-8B02-CEFAB3BC3876@lavergne.gotdns.org> References: <92540E8B-A53A-4358-8B02-CEFAB3BC3876@lavergne.gotdns.org> Message-ID: wow, that was lightning fast. Shame of me because even the wiki was updated thanks a lot Jeremy On Wed, Jul 11, 2012 at 6:46 PM, Jeremy Lavergne wrote: > Check out archive_sites.conf, added in MacPorts 2.1.0 > http://trac.macports.org/browser/trunk/base/ChangeLog > > On Jul 11, 2012, at 12:41 , Francisco Garcia wrote: > >> Exploring the macports.conf man page I have noticed that: >> >> archive_site_local is no longer listed >> buildfromsource never is listed as an option, bit it is ignored. The >> ports are still built from source in any case >> >> Have these options changed (or been removed) in the latest releases? >> >> I have a build server which used to work in the past, but now it no >> longer works. >> I do not think I have touched any configuration of the services >> involved. The server in question >> was working according this howto >> >> https://trac.macports.org/wiki/howto/ShareArchives2 >> >> Now my client machine no longer fetches builds from my server. Instead >> it just decides to build itself every port >> >> In my macports.conf I have this line: >> >> archive_site_local http://myserver.local/macports/ >> >> I have verified that the address is valid and provides an index of >> /opt/local/var/macports/software (I am using Apache) >> >> Also I verified that my keys (from pubkeys.conf) are the same in both servers >> >> I am running out of ideas of what can be wrong and do not know how to >> track down this problem. How should I debug this? >> >> When I try to install a port already compiled by my server with the >> "-d" parameter, there is no single reference to my >> archive_site_local server in the output. Should I see my server listed >> in the output? > From bookbinder at PreserveYourTreasures.com Wed Jul 11 14:05:33 2012 From: bookbinder at PreserveYourTreasures.com (Susan Llunas) Date: Wed, 11 Jul 2012 14:05:33 -0700 Subject: downloading Ghostscript to OSX Message-ID: We have tried to download Ghostscript to our OSX Lion, we choose the MacPorts, Ghostscript 9.05 listed, we click download, and that box pops up with a box saying we need to download MacPorts. We end up in a do-loop with no download. What gives? Thanks, Les Lunas From allbery.b at gmail.com Wed Jul 11 14:26:05 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Wed, 11 Jul 2012 17:26:05 -0400 Subject: downloading Ghostscript to OSX In-Reply-To: References: Message-ID: On Wed, Jul 11, 2012 at 5:05 PM, Susan Llunas < bookbinder at preserveyourtreasures.com> wrote: > We have tried to download Ghostscript to our OSX Lion, we choose the > MacPorts, Ghostscript 9.05 listed, we click download, and that box > pops up with a box saying we need to download MacPorts. We end up in a > do-loop with no download. > Where are you doing this? Because that's not how MacPorts works. First, you make sure Xcode is installed. While some ports with suitable licenses and default variants on some Mac platforms are available as binary archives, much of the time ports must be built from source. This requires a full Xcode installation (not the minimal one Apple recently came up with) because some ports use xcodebuild. You then install MacPorts ( https://trac.macports.org/wiki/InstallingMacPorts ); this install and configures the MacPorts framework and does an initial download of the ports tree, which is a repository of recipes. You would then open a new Terminal window and type "sudo port install ghostscript" to install the ghostscript port (and its dependencies). There are some GUI wrappers, none of which is fully functional at the moment as I understand it (one is obsolete and nonfunctional on Lion, the others are still in development/incomplete). -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From frankel at circlesfx.com Wed Jul 11 22:05:54 2012 From: frankel at circlesfx.com (Scott Frankel) Date: Wed, 11 Jul 2012 22:05:54 -0700 Subject: py27-pil installation Message-ID: Hi all, I'm having difficulty with the py27-pil installation for my new machine running OSX 10.7.4. 1) macports reports that the installation succeeds: % sudo port install py27-pil Password: ---> Computing dependencies for py27-pil ---> Cleaning py27-pil ---> Scanning binaries for linking errors: 100.0% ---> No broken files found. 2) macports lists the location of the port as being an image file (???): % port location py27-pil Port py27-pil 1.1.7_4 is installed as an image in: /opt/local/var/macports/software/py27-pil/py27-pil-1.1.7_4.darwin_11.x86_64.tbz2 3) the py27-pil components are either not installed, or not installed in their correct location as revealed in Python's cmd-line interpreter: >>> import Image Traceback (most recent call last): File "", line 1, in ImportError: No module named Image This is the second 10.7.x machine I've used macports to install PIL. The first was successful without issue. Is there a step I'm missing? Any remedial steps I can take to complete/troubleshoot the installation? Thanks! Scott From jeremy at lavergne.gotdns.org Wed Jul 11 22:10:28 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Thu, 12 Jul 2012 01:10:28 -0400 Subject: py27-pil installation In-Reply-To: References: Message-ID: <0FC41A78-1F9D-4BD8-A820-D97916438329@lavergne.gotdns.org> > I'm having difficulty with the py27-pil installation for my new machine running OSX 10.7.4. > > 1) macports reports that the installation succeeds: > > % sudo port install py27-pil > Password: > ---> Computing dependencies for py27-pil > ---> Cleaning py27-pil > ---> Scanning binaries for linking errors: 100.0% > ---> No broken files found. > > 2) macports lists the location of the port as being an image file (???): > > % port location py27-pil > Port py27-pil 1.1.7_4 is installed as an image in: > /opt/local/var/macports/software/py27-pil/py27-pil-1.1.7_4.darwin_11.x86_64.tbz2 location Print the install location of a given port. This is a bit of a semantic argument: the point where it is installed from is the archive. The installed contents is provided by `port contents py27-pil`. > 3) the py27-pil components are either not installed, or not installed in their correct location as revealed in Python's cmd-line interpreter: > >>>> import Image > Traceback (most recent call last): > File "", line 1, in > ImportError: No module named Image > > > > This is the second 10.7.x machine I've used macports to install PIL. The first was successful without issue. Is there a step I'm missing? Any remedial steps I can take to complete/troubleshoot the installation? Which python did you run? /opt/local/bin/python2.7 is the one that these supposedly installed for. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 8796 bytes Desc: not available URL: From public at francisco-garcia.net Thu Jul 12 03:49:35 2012 From: public at francisco-garcia.net (Francisco Garcia) Date: Thu, 12 Jul 2012 12:49:35 +0200 Subject: Portfile configuration parameter to replace other ports Message-ID: I have just created my first two port contributions. I submitted one but I am having problems to decide the best approach for the second one. I modified the ctags portfile to build the latest svn/trunk version instead of using the official release. The portfile is here: https://github.com/fgarcia/macports/blob/master/devel/ctags-devel/Portfile Since the official release lacks support for ObjectiveC I came up with two solutions: 1. Create a new port named "ctags-devel". That will show it is not an official release 2. Build a patch file for the ctags Portfile I am not sure which one is the normal way to deal with such situations. I went for point (1) but that port will collide with the ctags port. I know about the parameter to make ctags-devel to conflict with ctags, but I cannot find one where I can say that ctags-devel "provides" plain ctags too. For example, MacVim depends on ctags and I would like an easy way to avoid this dependency conflict. thanks Francisco From ryandesign at macports.org Thu Jul 12 04:33:20 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 12 Jul 2012 06:33:20 -0500 Subject: Portfile configuration parameter to replace other ports In-Reply-To: References: Message-ID: <3721088E-57E5-407F-8BE4-2736CFD6421C@macports.org> On Jul 12, 2012, at 05:49, Francisco Garcia wrote: > I have just created my first two port contributions. I submitted one > but I am having problems to decide the best approach for the second > one. > > I modified the ctags portfile to build the latest svn/trunk version > instead of using the official release. The portfile is here: > > https://github.com/fgarcia/macports/blob/master/devel/ctags-devel/Portfile > > Since the official release lacks support for ObjectiveC I came up with > two solutions: > > 1. Create a new port named "ctags-devel". That will show it is not an > official release > > 2. Build a patch file for the ctags Portfile > > I am not sure which one is the normal way to deal with such > situations. I went for point (1) but that port will collide with the > ctags port. I know about the parameter to make ctags-devel to conflict > with ctags, but I cannot find one where I can say that ctags-devel > "provides" plain ctags too. For example, MacVim depends on ctags and I > would like an easy way to avoid this dependency conflict. You've chosen wisely. A separate ctags-devel port is the correct solution. There is no way to tell MacPorts that ctags-devel "provides" ctags. Instead, every port that declares a dependency on ctags will have to be changed to use a path:-style dependency so that either port could satisfy it. We can simply do a search and replace across all ports to do this. See this ticket for some preliminary documentation about -devel ports: https://trac.macports.org/ticket/14540 From srinath at txcorp.com Thu Jul 12 10:38:19 2012 From: srinath at txcorp.com (Srinath Vadlamani) Date: Thu, 12 Jul 2012 11:38:19 -0600 Subject: any attempt to upgrade openmpi Message-ID: <2A773C19-E879-4AD8-AEC3-57A1561584A1@txcorp.com> Is anyone trying to upgrade to openmpi 1.6? What about also allowing for the use of gcc4.7 as variant for openmpi, hdf5, netcdf and other scientific software? Thanks, <>Srinath =================== Srinath Vadlamani, PhD srinath at txcorp.com (w)303-996-2034 (f)303-448-7756 www.txcorp.com Tech-X Corp. 5621 Arapahoe Ave. Suite A Boulder, CO 80027 ==================== From frankel at circlesfx.com Thu Jul 12 12:54:00 2012 From: frankel at circlesfx.com (Scott Frankel) Date: Thu, 12 Jul 2012 12:54:00 -0700 Subject: py27-pil installation In-Reply-To: <0FC41A78-1F9D-4BD8-A820-D97916438329@lavergne.gotdns.org> References: <0FC41A78-1F9D-4BD8-A820-D97916438329@lavergne.gotdns.org> Message-ID: <3AF6C937-0320-4AD5-88AB-E3D034998109@circlesfx.com> Hi Jeremy, On Jul 11, 2012, at 10:10 PM, Jeremy Lavergne wrote: >> I'm having difficulty with the py27-pil installation for my new machine running OSX 10.7.4. >> >> 1) macports reports that the installation succeeds: >> >> % sudo port install py27-pil >> Password: >> ---> Computing dependencies for py27-pil >> ---> Cleaning py27-pil >> ---> Scanning binaries for linking errors: 100.0% >> ---> No broken files found. > >> >> 2) macports lists the location of the port as being an image file (???): >> >> % port location py27-pil >> Port py27-pil 1.1.7_4 is installed as an image in: >> /opt/local/var/macports/software/py27-pil/py27-pil-1.1.7_4.darwin_11.x86_64.tbz2 > > location > Print the install location of a given port. > > This is a bit of a semantic argument: the point where it is installed from is the archive. The installed contents is provided by `port contents py27-pil`. Aha. >> 3) the py27-pil components are either not installed, or not installed in their correct location as revealed in Python's cmd-line interpreter: >> >>>>> import Image >> Traceback (most recent call last): >> File "", line 1, in >> ImportError: No module named Image >> >> >> >> This is the second 10.7.x machine I've used macports to install PIL. The first was successful without issue. Is there a step I'm missing? Any remedial steps I can take to complete/troubleshoot the installation? > > Which python did you run? > /opt/local/bin/python2.7 is the one that these supposedly installed for. Bingo! I was running Apple's installed Python interpreter. Oops. Thanks for the tip! Scott From ryandesign at macports.org Thu Jul 12 15:09:21 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 12 Jul 2012 17:09:21 -0500 Subject: any attempt to upgrade openmpi In-Reply-To: <2A773C19-E879-4AD8-AEC3-57A1561584A1@txcorp.com> References: <2A773C19-E879-4AD8-AEC3-57A1561584A1@txcorp.com> Message-ID: On Jul 12, 2012, at 12:38, Srinath Vadlamani wrote: > Is anyone trying to upgrade to openmpi 1.6? > What about also allowing for the use of gcc4.7 as variant for openmpi, hdf5, netcdf and other scientific software? I'm not sure, but the port does have a maintainer... you should file a ticket in the issue tracker requesting these changes. From spooky130u at gmail.com Fri Jul 13 05:05:00 2012 From: spooky130u at gmail.com (Jim Graham) Date: Fri, 13 Jul 2012 07:05:00 -0500 Subject: texlive: need variable def for TFMFONTS Message-ID: <20120713120459.GA7146@gmail.com> In the standard (which I assume is full) install for texlive, what do I need to set for TFMFONTS ? I keep trying to run TeX on a file, and after getting TEXINPUTS right, TeX keeps whining that it can't find any of the TFM fonts. Here are the errors TeX spits out: --------------------------- CUT HERE --------------------------- kpathsea: Running mktextfm cmbxti /opt/local/share/texmf-texlive/web2c/mktexnam: Could not map typeface abbreviation mb for cmbxti. /opt/local/share/texmf-texlive/web2c/mktexnam: Need to update /opt/local/share/texmf-texlive-dist/fonts/map/fontname/special.map? mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input cmbxti This is METAFONT, Version 2.718281 (TeX Live 2011/MacPorts 2011_5) kpathsea: Running mktexmf cmbxti ! I can't find file `cmbxti'. <*> ...:=ljfour; mag:=1; nonstopmode; input cmbxti Please type another input file name ! Emergency stop. <*> ...:=ljfour; mag:=1; nonstopmode; input cmbxti Transcript written on mfput.log. grep: cmbxti.log: No such file or directory mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input cmbx i' failed to make cmbxti.tfm. kpathsea: Appending font creation commands to missfont.log. ! Font \titlef=cmbxti at 16.0pt not loadable: Metric (TFM) file not found. l.3 \font\titlef=cmbxti at 16pt ? x No pages of output. --------------------------- CUT HERE --------------------------- Not good..... Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) MiSTie #49997 < Running Mac OS X Lion > spooky130u at gmail.com ICBM/Hurr.: 30.44406N 86.59909W No, I'm not going to explain it. If you can't figure it out, you didn't want to know anyway... --Larry Wall Android Apps Listing at http://www.jstrack.org/barcodes.html From spooky130u at gmail.com Fri Jul 13 05:40:44 2012 From: spooky130u at gmail.com (Jim Graham) Date: Fri, 13 Jul 2012 07:40:44 -0500 Subject: Muttprint install and iconv In-Reply-To: <20120709151529.GA68319@gmail.com> References: <20120709134459.GA68053@gmail.com> <928CAFDA-442F-4601-B313-B5B21E56A93B@lavergne.gotdns.org> <20120709151529.GA68319@gmail.com> Message-ID: <20120713124044.GA7503@gmail.com> Does ANYONE know why muttprint is failing here? On Mon, Jul 09, 2012 at 10:15:29AM -0500, Jim Graham wrote: > On Mon, Jul 09, 2012 at 09:47:51AM -0400, Jeremy Lavergne wrote: > > > > > That definitely looks like it's after a perl module (perhaps the port > > is named p5.12-text-iconv?). > > That sounds right. > > > It's entirely possible that the perl MacPorts is using doesn't match up > > with the one that muttprint is using: /usr/bin/perl versus > > /opt/local/bin/perl5.12 > > (10:10) # which perl > /usr/bin/perl > (10:10) # perl -v > > This is perl 5, version 12, subversion 3 (v5.12.3) .... > > iconv is p5.12-text-iconv > > muttport simply starts with #!/usr/bin/env perl, which unless I'm > seriously mistaken, would be /usr/bin/perl (5.12.3). > > Does this help? > > Thanks, > --jim > > -- > THE SCORE: ME: 2 CANCER: 0 > 73 DE N5IAL (/4) MiSTie #49997 < Running Mac OS X Lion > > spooky130u at gmail.com ICBM/Hurr.: 30.44406N 86.59909W > > Seen in alt.sysadmin.recovery: "Priceless; that's better than telling > him to use the Read Manual command with the Real Fast option." > > Android Apps Listing at http://www.jstrack.org/barcodes.html -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) MiSTie #49997 < Running Mac OS X Lion > spooky130u at gmail.com ICBM/Hurricane: 30.44406N 86.59909W Do not look into waveguide with remaining eye. Android Apps Listing at http://www.jstrack.org/barcodes.html From allbery.b at gmail.com Fri Jul 13 08:06:07 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Fri, 13 Jul 2012 11:06:07 -0400 Subject: Muttprint install and iconv In-Reply-To: <20120713124044.GA7503@gmail.com> References: <20120709134459.GA68053@gmail.com> <928CAFDA-442F-4601-B313-B5B21E56A93B@lavergne.gotdns.org> <20120709151529.GA68319@gmail.com> <20120713124044.GA7503@gmail.com> Message-ID: On Fri, Jul 13, 2012 at 8:40 AM, Jim Graham wrote: > Does ANYONE know why muttprint is failing here? > You were in fact just told why. On Mon, Jul 09, 2012 at 10:15:29AM -0500, Jim Graham wrote: > > On Mon, Jul 09, 2012 at 09:47:51AM -0400, Jeremy Lavergne wrote: > > > That definitely looks like it's after a perl module (perhaps the port > > > is named p5.12-text-iconv?). > > > > That sounds right. > > > > > It's entirely possible that the perl MacPorts is using doesn't match up > > > with the one that muttprint is using: /usr/bin/perl versus > > > /opt/local/bin/perl5.12 > > > > (10:10) # which perl > > /usr/bin/perl > > (10:10) # perl -v > > > > This is perl 5, version 12, subversion 3 (v5.12.3) .... > > > > iconv is p5.12-text-iconv > > > > muttport simply starts with #!/usr/bin/env perl, which unless I'm > > seriously mistaken, would be /usr/bin/perl (5.12.3). > Spelling it out more explicitly: you installed a module into /opt/local/bin/perl5.12. (MacPorts does not install modules into system programs, including the system Perl.) So, you have a port bug: it needs to be changed to invoke the MacPorts perl. The workaround is "sudo port install perl5 +perl5_12", which will install /opt/local/bin/perl pointing to /opt/local/bin/perl5.12. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From allbery.b at gmail.com Fri Jul 13 08:17:22 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Fri, 13 Jul 2012 11:17:22 -0400 Subject: texlive: need variable def for TFMFONTS In-Reply-To: <20120713120459.GA7146@gmail.com> References: <20120713120459.GA7146@gmail.com> Message-ID: On Fri, Jul 13, 2012 at 8:05 AM, Jim Graham wrote: > In the standard (which I assume is full) install for texlive, > You assume wrong, as "port variants texlive" tells you. what do I need to set for TFMFONTS ? I keep trying to run TeX > I think that if you need to set $TFMFONTS then either something is not installed or you have found a bug. > on a file, and after getting TEXINPUTS right, TeX keeps whining > ...and same should go for TEXINPUTS. Do you perhaps have some other TeX installation around as well? -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From mparchet at sunrise.ch Fri Jul 13 09:16:51 2012 From: mparchet at sunrise.ch (Michael Parchet) Date: Fri, 13 Jul 2012 18:16:51 +0200 Subject: mariadb package and QMYSQL driver. Message-ID: <500049F3.3060601@sunrise.ch> Hello, I have installed the mariadb package. Is it compatible with the QMYSQL driver ? Tanks for your answer. Best regards mparchet -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at macports.org Fri Jul 13 09:38:39 2012 From: ram at macports.org (Adam Mercer) Date: Fri, 13 Jul 2012 11:38:39 -0500 Subject: Cleanup of compiler variants in py-numpy and py-scipy In-Reply-To: References: Message-ID: On Mon, Jul 9, 2012 at 6:07 PM, Adam Mercer wrote: > Currently py-numpy and py-scipy have the following compiler variants: > gcc43, gcc44, gcc45, gcc46, and gcc47. Whereas the atlas port only > provides variants using gcc45, gcc46, and gcc47. Therefore I propose > removing the gcc43, and gcc44 variants from py-numpy and py-scipy. > > Any objections? I'll take silence to mean no one has any objections, I'll remove the gcc43 and gcc44 variants over the weekend. Cheers Adam From spooky130u at gmail.com Fri Jul 13 12:30:15 2012 From: spooky130u at gmail.com (Jim Graham) Date: Fri, 13 Jul 2012 14:30:15 -0500 Subject: Muttprint install and iconv In-Reply-To: References: <20120709134459.GA68053@gmail.com> <928CAFDA-442F-4601-B313-B5B21E56A93B@lavergne.gotdns.org> <20120709151529.GA68319@gmail.com> <20120713124044.GA7503@gmail.com> Message-ID: <20120713193015.GA40118@gmail.com> On Fri, Jul 13, 2012 at 11:06:07AM -0400, Brandon Allbery wrote: > On Fri, Jul 13, 2012 at 8:40 AM, Jim Graham wrote: > > > Does ANYONE know why muttprint is failing here? > > > > You were in fact just told why. Not until you explained it below: > Spelling it out more explicitly: you installed a module into > /opt/local/bin/perl5.12. (MacPorts does not install modules into system > programs, including the system Perl.) Ok, now THAT I understand. Nobody mentioned that before now. Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) MiSTie #49997 < Running Mac OS X Lion > spooky130u at gmail.com ICBM/Hurricane: 30.44406N 86.59909W "'Wrong' is one of those concepts that depends on witnesses." --Catbert: Evil Director of Human Resources (Dilbert, 05Nov09) Android Apps Listing at http://www.jstrack.org/barcodes.html From spooky130u at gmail.com Fri Jul 13 12:35:12 2012 From: spooky130u at gmail.com (Jim Graham) Date: Fri, 13 Jul 2012 14:35:12 -0500 Subject: texlive: need variable def for TFMFONTS In-Reply-To: References: <20120713120459.GA7146@gmail.com> Message-ID: <20120713193512.GA40150@gmail.com> On Fri, Jul 13, 2012 at 11:17:22AM -0400, Brandon Allbery wrote: > On Fri, Jul 13, 2012 at 8:05 AM, Jim Graham wrote: > > > In the standard (which I assume is full) install for texlive, > > > > You assume wrong, as "port variants texlive" tells you. As I realized when I installed the full version. Lots and lots of language stuff I have no use for. I also found where the tfm directory was hiding, and it's all happy now. > ...and same should go for TEXINPUTS. Do you perhaps have some other TeX > installation around as well? Nope.... But like I said, TeX is perfectly happy now. :-) Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) | Peter da Silva: No, try "rm -rf /" spooky130u at gmail.com | Dave Aronson: As your life flashes before < Running Mac OS X Lion > | your eyes, in the unit of time known as an ICBM / Hurricane: | ohnosecond.... (alt.sysadmin.recovery) 30.44406N 86. 59909W | Android Apps Listing at http://www.jstrack.org/barcodes.html From pixilla at macports.org Fri Jul 13 13:03:46 2012 From: pixilla at macports.org (Bradley Giesbrecht) Date: Fri, 13 Jul 2012 13:03:46 -0700 Subject: mariadb package and QMYSQL driver. In-Reply-To: <500049F3.3060601@sunrise.ch> References: <500049F3.3060601@sunrise.ch> Message-ID: <115102C9-69A2-4651-9E58-59DFA470CD18@macports.org> On Jul 13, 2012, at 9:16 AM, Michael Parchet wrote: > Hello, > > I have installed the mariadb package. What version of mariadb is installed? $ port installed mariadb > Is it compatible with the QMYSQL driver ? Are you referring to qt4-mac +mysql? The MacPorts mariadb port is likely to be updated to 5.5.24 in the near future and at that point qt4-mac will need to be updated to use mariadb. Regards, Bradley Giesbrecht (pixilla) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2763 bytes Desc: not available URL: From Blaine-Mooers at ouhsc.edu Sat Jul 14 09:00:48 2012 From: Blaine-Mooers at ouhsc.edu (Mooers, Blaine H.M. (HSC)) Date: Sat, 14 Jul 2012 11:00:48 -0500 Subject: libffi on snow leopard Message-ID: <3C8DB3DD-48A5-4B9B-B7B1-81247C536EAD@ouhsc.edu> Snow leopard, 2010 MacBook Pro, Intel, /sw64 I can't upgrade outdated ports due to problem with libffi sudo port selfupdate # goes okay ---> Updating MacPorts base sources using rsync receiving file list ... done base.tar sent 11356 bytes received 111 bytes 2548.22 bytes/sec total size is 3539456 speedup is 308.66 receiving file list ... done base.tar.rmd160 sent 64 bytes received 116 bytes 360.00 bytes/sec total size is 512 speedup is 2.84 MacPorts base version 2.1.1 installed, MacPorts base version 2.1.1 downloaded. ---> Updating the ports tree Synchronizing local ports tree from file:///opt/local/var/macports/sources/svn.macports.org/trunk/dports/ At revision 95508. Creating port index in /opt/local/var/macports/sources/svn.macports.org/trunk/dports Total number of ports parsed: 0 Ports successfully parsed: 0 Ports failed: 0 Up-to-date ports skipped: 15366 ---> MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated sudo port -v upgrade outdated ---> Updating MacPorts base sources using rsync receiving file list ... done base.tar sent 11356 bytes received 111 bytes 2548.22 bytes/sec total size is 3539456 speedup is 308.66 receiving file list ... done base.tar.rmd160 sent 64 bytes received 116 bytes 360.00 bytes/sec total size is 512 speedup is 2.84 MacPorts base version 2.1.1 installed, MacPorts base version 2.1.1 downloaded. ---> Updating the ports tree Synchronizing local ports tree from file:///opt/local/var/macports/sources/svn.macports.org/trunk/dports/ At revision 95508. Creating port index in /opt/local/var/macports/sources/svn.macports.org/trunk/dports Total number of ports parsed: 0 Ports successfully parsed: 0 Ports failed: 0 Up-to-date ports skipped: 15366 ---> MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated bash-3.2$ sudo port upgrade outdated Password: bash-3.2$ sudo port -v upgrade outdated Password: ---> Configuring libffi ---> Configuring libffi for architecture x86_64 Error: org.macports.configure for port libffi returned: error copying "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/work/libffi-3.0.11" to "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/work/libffi-3.0.11-x86_64/libffi-3.0.11": file already exists Warning: targets not executed for libffi: org.macports.install org.macports.configure org.macports.build org.macports.destroot Please see the log file for port libffi for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets sudo port -v install libffi +universal ---> Configuring libffi ---> Configuring libffi for architecture x86_64 Error: org.macports.configure for port libffi returned: error copying "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/work/libffi-3.0.11" to "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/work/libffi-3.0.11-x86_64/libffi-3.0.11": file already exists Warning: targets not executed for libffi: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install Please see the log file for port libffi for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port libffi failed version:1 :debug:main libffi has no conflicts :debug:main Executing org.macports.main (libffi) :debug:main changing euid/egid - current euid: 0 - current egid: 0 :debug:main egid changed to: 503 :debug:main euid changed to: 503 :debug:main Skipping completed org.macports.archivefetch (libffi) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.fetch (libffi) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.checksum (libffi) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.extract (libffi) :debug:main Privilege de-escalation not attempted as not running as root. :debug:main Skipping completed org.macports.patch (libffi) :debug:main Privilege de-escalation not attempted as not running as root. :debug:configure configure phase started at Sat Jul 14 10:32:08 CDT 2012 :notice:configure ---> Configuring libffi :debug:configure Using compiler 'Mac OS X gcc 4.2' :debug:configure Executing org.macports.configure (libffi) :info:configure ---> Configuring libffi for architecture x86_64 :error:configure org.macports.configure for port libffi returned: error copying "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/work/libffi-3.0.11" to "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/work/libffi-3.0.11-x86_64/libffi-3.0.11": file already exists :debug:configure Error code: NONE :debug:configure Backtrace: error copying "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/work/libffi-3.0.11" to "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/work/libffi-3.0.11-x86_64/libffi-3.0.11": file already exists while executing "$procedure $targetname" :info:configure Warning: targets not executed for libffi: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install :notice:configure Please see the log file for port libffi for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/main.log From jeremy at lavergne.gotdns.org Sat Jul 14 09:09:57 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Sat, 14 Jul 2012 12:09:57 -0400 Subject: libffi on snow leopard In-Reply-To: <3C8DB3DD-48A5-4B9B-B7B1-81247C536EAD@ouhsc.edu> References: <3C8DB3DD-48A5-4B9B-B7B1-81247C536EAD@ouhsc.edu> Message-ID: <4F1A7353-6159-45FC-9B14-AEA2D3960DE2@lavergne.gotdns.org> > --> Configuring libffi > ---> Configuring libffi for architecture x86_64 > Error: org.macports.configure for port libffi returned: error copying "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/work/libffi-3.0.11" to "/opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/work/libffi-3.0.11-x86_64/libffi-3.0.11": file already exists > Warning: targets not executed for libffi: org.macports.install org.macports.configure org.macports.build org.macports.destroot > Please see the log file for port libffi for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_libffi/libffi/main.log > Error: Unable to upgrade port: 1 > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets Clean libffi, then try again -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4897 bytes Desc: not available URL: From jeremy at lavergne.gotdns.org Sat Jul 14 10:19:32 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Sat, 14 Jul 2012 13:19:32 -0400 Subject: libffi on snow leopard In-Reply-To: <8BA18C2D-A5EE-4A13-B489-9641DB32A8EF@ouhsc.edu> References: <3C8DB3DD-48A5-4B9B-B7B1-81247C536EAD@ouhsc.edu> <4F1A7353-6159-45FC-9B14-AEA2D3960DE2@lavergne.gotdns.org> <8BA18C2D-A5EE-4A13-B489-9641DB32A8EF@ouhsc.edu> Message-ID: <7F47ADE8-7659-4526-9775-7D2A984235AE@lavergne.gotdns.org> > bash-3.2$ sudo port -v upgrade outdated > ---> Configuring libffi This part bugs me: you keep getting to configure phase, without fetch/extract/patch happening. Can you guarantee that those are happening and you're not using any cached parts in configure? > checking for gawk... no > checking for mawk... no > checking for nawk... nawk Since nawk is found, what happens if you temporarily deactivate it for this build? Like so: sudo port -f deactivate nawk sudo port clean libffi sudo port -v install libffi sudo port activate nawk Note: if you have more than one nawk available (already deactivated), MacPorts may ask you to specify the fully qualified name (name @version[+variants]). -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4897 bytes Desc: not available URL: From mparchet at sunrise.ch Sat Jul 14 14:09:09 2012 From: mparchet at sunrise.ch (Michael Parchet) Date: Sat, 14 Jul 2012 23:09:09 +0200 Subject: mariadb package and QMYSQL driver. In-Reply-To: <115102C9-69A2-4651-9E58-59DFA470CD18@macports.org> References: <500049F3.3060601@sunrise.ch> <115102C9-69A2-4651-9E58-59DFA470CD18@macports.org> Message-ID: <5001DFF5.7020202@sunrise.ch> Le 13.07.12 22:03, Bradley Giesbrecht a ?crit : > On Jul 13, 2012, at 9:16 AM, Michael Parchet wrote: > >> Hello, >> >> I have installed the mariadb package. > What version of mariadb is installed? > $ port installed mariadb > >> Is it compatible with the QMYSQL driver ? > Are you referring to qt4-mac +mysql? > > The MacPorts mariadb port is likely to be updated to 5.5.24 in the near future and at that point qt4-mac will need to be updated to use mariadb. Any more precise idea when this can happen ? Best regards mparchet > > > Regards, > Bradley Giesbrecht (pixilla) > From mparchet at sunrise.ch Sun Jul 15 09:06:41 2012 From: mparchet at sunrise.ch (Michael Parchet) Date: Sun, 15 Jul 2012 18:06:41 +0200 Subject: unable to uninstall a port Message-ID: <5002EA91.7030302@sunrise.ch> Hello, I wold like to uninstall mariadb and replace it with mysql so that the akondi server can walk. but I can't uninstall maradb and its dependencs ? Bellow, here is my command line. sudo port uninstall --follow-dependencies mariadb @5.2.9_4 Is it correct ? Tanks for your answer Best regards mparchet -------------- next part -------------- An HTML attachment was scrubbed... URL: From allbery.b at gmail.com Sun Jul 15 09:12:02 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Sun, 15 Jul 2012 12:12:02 -0400 Subject: unable to uninstall a port In-Reply-To: <5002EA91.7030302@sunrise.ch> References: <5002EA91.7030302@sunrise.ch> Message-ID: On Sun, Jul 15, 2012 at 12:06 PM, Michael Parchet wrote: > I wold like to uninstall mariadb and replace it with mysql so that the akondi > server can walk. but I can't uninstall maradb and its dependencs ? > > Bellow, here is my command line. > > sudo port uninstall ??follow?dependencies mariadb @5.2.9_4 > Looks reasonable. What error(s) are you getting? -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From mparchet at sunrise.ch Sun Jul 15 12:09:57 2012 From: mparchet at sunrise.ch (Michael Parchet) Date: Sun, 15 Jul 2012 21:09:57 +0200 Subject: unable to uninstall a port In-Reply-To: References: <5002EA91.7030302@sunrise.ch> Message-ID: <50031585.9070303@sunrise.ch> Le 15.07.12 18:12, Brandon Allbery a ?crit : > On Sun, Jul 15, 2012 at 12:06 PM, Michael Parchet > wrote: > > I wold like to uninstall mariadb and replace it with mysql so that > the akondi server can walk. but I can't uninstall maradb and its > dependencs ? > > Bellow, here is my command line. > > sudo port uninstall ??follow?dependencies mariadb @5.2.9_4 > > Looks reasonable. What error(s) are you getting? > Hello, here is my output /sudo port uninstall ??follow?dependencies mariadb @5.2.9_4 Unable to uninstall mariadb @5.2.9_4, the following ports depend on it: ---> mariadb-server @5.2.9_0 ---> akonadi @1.7.2_0 Error: org.macports.uninstall for port mariadb returned: Please uninstall the ports that depend on mariadb first. Please see the log file for port mariadb for details: /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_mariadb_5.2.9_4/mariadb/main.log / Can you help me please ? Best regards mparchet > -- > brandon s allbery allbery.b at gmail.com > wandering unix systems administrator (available) (412) 475-9364 > vm/sms > -------------- next part -------------- An HTML attachment was scrubbed... URL: From damon.mcdougall at gmail.com Sun Jul 15 12:15:05 2012 From: damon.mcdougall at gmail.com (Damon McDougall) Date: Sun, 15 Jul 2012 20:15:05 +0100 Subject: unable to uninstall a port In-Reply-To: <50031585.9070303@sunrise.ch> References: <5002EA91.7030302@sunrise.ch> <50031585.9070303@sunrise.ch> Message-ID: <20120715191505.GA377@quagmire.local> On Sun, Jul 15, 2012 at 09:09:57PM +0200, Michael Parchet wrote: > Le 15.07.12 18:12, Brandon Allbery a ?crit : > >On Sun, Jul 15, 2012 at 12:06 PM, Michael Parchet > >> wrote: > > > > I wold like to uninstall mariadb and replace it with mysql so that > > the akondi server can walk. but I can't uninstall maradb and its > > dependencs ? > > > > Bellow, here is my command line. > > > > sudo port uninstall ??follow?dependencies mariadb @5.2.9_4 > > > >Looks reasonable. What error(s) are you getting? > >Hello, > > here is my output > > /sudo port uninstall ??follow?dependencies mariadb @5.2.9_4 > > Unable to uninstall mariadb @5.2.9_4, the following ports depend on it: > ---> mariadb-server @5.2.9_0 > ---> akonadi @1.7.2_0 > Error: org.macports.uninstall for port mariadb returned: Please > uninstall the ports that depend on mariadb first. > Please see the log file for port mariadb for details: > /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_mariadb_5.2.9_4/mariadb/main.log > / > Can you help me please ? > Should it be --follow-dependents instead? > Best regards > > mparchet > >-- > >brandon s allbery allbery.b at gmail.com > >wandering unix systems administrator (available) (412) 475-9364 > > vm/sms > > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users -- Damon McDougall http://damon-is-a-geek.com B2.39 Mathematics Institute University of Warwick Coventry West Midlands CV4 7AL United Kingdom From allbery.b at gmail.com Sun Jul 15 12:19:24 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Sun, 15 Jul 2012 15:19:24 -0400 Subject: unable to uninstall a port In-Reply-To: <50031585.9070303@sunrise.ch> References: <5002EA91.7030302@sunrise.ch> <50031585.9070303@sunrise.ch> Message-ID: On Sun, Jul 15, 2012 at 3:09 PM, Michael Parchet wrote: > * > sudo port uninstall ??follow?dependencies mariadb @5.2.9_4 > > Unable to uninstall mariadb @5.2.9_4, the following ports depend on it: > ---> mariadb-server @5.2.9_0 > ---> akonadi @1.7.2_0 > Error: org.macports.uninstall for port mariadb returned: Please uninstall > the ports that depend on mariadb first.* > Ah, right, you want --follow-dependents not --follow-dependencies. (dependents = children... -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan.scheidt at me.com Sun Jul 15 13:01:33 2012 From: stefan.scheidt at me.com (Stefan Scheidt) Date: Sun, 15 Jul 2012 22:01:33 +0200 Subject: git bash_completion does not work Message-ID: Hi, a couple of days ago I updated my ports (sudo port upgrade outdated), and now bash_completion for git does not work. port installed says: ? bash @4.2.29_0 (active) bash-completion @2.0_1 (active) ? git-core @1.7.11.2_0+bash_completion+credential_osxkeychain+doc+pcre+python27+svn (active) ? bash -version say GNU bash, Version 4.2.29(2)-release (i386-apple-darwin11.3.0) and in .bashrc (sourced by .bash_profile) I have added this: if [ -f /opt/local/etc/profile.d/bash_completion.sh ]; then . /opt/local/etc/profile.d/bash_completion.sh fi with the new "profile.d". Any Ideas why bash_completion does not work for git? Regards Stefan -- Stefan Scheidt -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan.scheidt at me.com Sun Jul 15 13:13:13 2012 From: stefan.scheidt at me.com (Stefan Scheidt) Date: Sun, 15 Jul 2012 22:13:13 +0200 Subject: git bash_completion does not work - solved (?) In-Reply-To: References: Message-ID: <75BFF5FE24C4490AB2114B6B1F015296@me.com> It seems I have solved my problem: Cause: My login shell was still the old /bin/bash. Solution: I added /opt/local/bin/bash to /etc/shells and then did "chsh -s /opt/local/bin/bash" Now bash_completion works! Question: Is this the right way to use MacPorts bash as login shell? Regards Stefan -- Stefan Scheidt Am Sonntag, 15. Juli 2012 um 22:01 schrieb Stefan Scheidt: > Hi, > > a couple of days ago I updated my ports (sudo port upgrade outdated), and now bash_completion for git does not work. > > port installed says: > > ? > bash @4.2.29_0 (active) > bash-completion @2.0_1 (active) > > ? > git-core @1.7.11.2_0+bash_completion+credential_osxkeychain+doc+pcre+python27+svn (active) > ? > > bash -version say > > GNU bash, Version 4.2.29(2)-release (i386-apple-darwin11.3.0) > > and in .bashrc (sourced by .bash_profile) I have added this: > > if [ -f /opt/local/etc/profile.d/bash_completion.sh ]; then > . /opt/local/etc/profile.d/bash_completion.sh > fi > > > with the new "profile.d". > > Any Ideas why bash_completion does not work for git? > > Regards > Stefan > > -- > Stefan Scheidt > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cal at macports.org Sun Jul 15 13:26:13 2012 From: cal at macports.org (Clemens Lang) Date: Sun, 15 Jul 2012 22:26:13 +0200 Subject: git bash_completion does not work - solved (?) In-Reply-To: <75BFF5FE24C4490AB2114B6B1F015296@me.com> References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> Message-ID: <20120715202613.GQ27027@towel.neverpanic.de> Hi, On Sun, Jul 15, 2012 at 10:13:13PM +0200, Stefan Scheidt wrote: > Question: Is this the right way to use MacPorts bash as login shell? Although `port notes bash-completion` suggests changing your terminal emulator's preferences, this is a perfectly fine way to do it, too (and it also is what I've been using for a couple of months now). -- Clemens Lang From thegooddale at gmail.com Sun Jul 15 14:34:50 2012 From: thegooddale at gmail.com (Yansky .) Date: Mon, 16 Jul 2012 07:34:50 +1000 Subject: Trouble accessing trac.macports.org Message-ID: Hi, I seem to be having some issues accessing https://trac.macports.org http://www.downforeveryoneorjustme.com/trac.macports.org says it's up, but I can't get to it. The weird thing is https://macports.org seems to resolve just fine. I did a traceroute of both domain/sub-domain and trac.macports.org seems to time out. I thought it might be my ISP (TPG Australia), but it also seems to time out using google's dns as well. trac.macports.org traceroute ? http://pastebin.com/N7vsV6x0 macports.org traceroute ? http://pastebin.com/Bfw0DeUa Anyone have any ideas? Yansky. From allbery.b at gmail.com Sun Jul 15 14:41:19 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Sun, 15 Jul 2012 17:41:19 -0400 Subject: Trouble accessing trac.macports.org In-Reply-To: References: Message-ID: On Sun, Jul 15, 2012 at 5:34 PM, Yansky . wrote: > Hi, I seem to be having some issues accessing https://trac.macports.org > Working for me, both http and https. > to time out. I thought it might be my ISP (TPG Australia), but it also > seems to time out using google's dns as well. > Er... if the name resolves, changing DNS is not going to make a difference to what happens with traceroute. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From msavory1 at nzbox.com Sun Jul 15 16:35:00 2012 From: msavory1 at nzbox.com (Mike Savory) Date: Sun, 15 Jul 2012 16:35:00 -0700 Subject: Trouble accessing trac.macports.org In-Reply-To: References: Message-ID: Looking at the DNS records, I see that trac has an AAAA record and the parent domain doesn't... > dig trac.macports.org AAAA trac.macports.org. 462 IN CNAME iota4.macosforge.org. but > dig iota4.macosforge.org AAAA Fails for me Could be we have IPv6 connectivity issues? Mike On Jul 15, 2012, at 2:34 PM, Yansky . wrote: > Hi, I seem to be having some issues accessing https://trac.macports.org > > http://www.downforeveryoneorjustme.com/trac.macports.org says it's up, > but I can't get to it. > > The weird thing is https://macports.org seems to resolve just fine. I > did a traceroute of both domain/sub-domain and trac.macports.org seems > to time out. I thought it might be my ISP (TPG Australia), but it also > seems to time out using google's dns as well. > > trac.macports.org traceroute ? http://pastebin.com/N7vsV6x0 > macports.org traceroute ? http://pastebin.com/Bfw0DeUa > > Anyone have any ideas? From ryandesign at macports.org Sun Jul 15 18:10:19 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 15 Jul 2012 20:10:19 -0500 Subject: git bash_completion does not work - solved (?) In-Reply-To: <20120715202613.GQ27027@towel.neverpanic.de> References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> Message-ID: On Jul 15, 2012, at 15:26, Clemens Lang wrote: > On Sun, Jul 15, 2012 at 10:13:13PM +0200, Stefan Scheidt wrote: >> Question: Is this the right way to use MacPorts bash as login shell? > > Although `port notes bash-completion` suggests changing your terminal > emulator's preferences, this is a perfectly fine way to do it, too (and > it also is what I've been using for a couple of months now). I was unable to figure out exactly what I was meant to be changing in Terminal's preferences to make this work. From allbery.b at gmail.com Sun Jul 15 18:25:35 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Sun, 15 Jul 2012 21:25:35 -0400 Subject: git bash_completion does not work - solved (?) In-Reply-To: References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> Message-ID: On Sun, Jul 15, 2012 at 9:10 PM, Ryan Schmidt wrote: > I was unable to figure out exactly what I was meant to be changing in > Terminal's preferences to make this work. > Presumably changing the command to run from your login shell to "/opt/local/bin/bash -l". -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From ktan at realityartisans.com Sun Jul 15 19:39:31 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Sun, 15 Jul 2012 22:39:31 -0400 Subject: Error when trying to start wireshark under X11 Message-ID: <50037EE3.50009@realityartisans.com> Hi, Can anyone tell me what this error means when I try to start wireshark in an xterm window via the X11 system: bash-3.2$ sudo wireshark (wireshark:11767): Gtk-WARNING **: cannot open display: :0.0 bash-3.2$ From allbery.b at gmail.com Sun Jul 15 20:27:47 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Sun, 15 Jul 2012 23:27:47 -0400 Subject: Error when trying to start wireshark under X11 In-Reply-To: <50037EE3.50009@realityartisans.com> References: <50037EE3.50009@realityartisans.com> Message-ID: On Sun, Jul 15, 2012 at 10:39 PM, Kok-Yong Tan wrote: > Can anyone tell me what this error means when I try to start wireshark in > an xterm window via the X11 system: > > bash-3.2$ sudo wireshark > > (wireshark:11767): Gtk-WARNING **: cannot open display: :0.0 > It means something messed with $DISPLAY, which you should not set on OS X; launchd sets it correctly and overriding it can cause problems like this. You're probably setting it in .bash_profile (or .profile, or being really wrong and setting it in .bashrc). Don't. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From ktan at realityartisans.com Sun Jul 15 21:11:27 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 16 Jul 2012 00:11:27 -0400 Subject: Error when trying to start wireshark under X11 In-Reply-To: References: <50037EE3.50009@realityartisans.com> Message-ID: <5003946F.3010406@realityartisans.com> On 7/15/12 23:27, Brandon Allbery wrote: > On Sun, Jul 15, 2012 at 10:39 PM, Kok-Yong Tan > > wrote: > > Can anyone tell me what this error means when I try to start > wireshark in an xterm window via the X11 system: > > bash-3.2$ sudo wireshark > > (wireshark:11767): Gtk-WARNING **: cannot open display: :0.0 > > > It means something messed with $DISPLAY, which you should not set on > OS X; launchd sets it correctly and overriding it can cause problems > like this. You're probably setting it in .bash_profile (or .profile, > or being really wrong and setting it in .bashrc). Don't. > > -- > brandon s allbery allbery.b at gmail.com > wandering unix systems administrator (available) (412) 475-9364 vm/sms > Thanks for the info. I went into .bashrc and found an explicit setting for the DISPLAY environment variable which I ripped out. Then I restarted X11 and did "sudo wireshark" whereupon X11 crashed and took wireshark with it. I then tried doing the same thing under a Terminal window and the same thing happened, except I got an extra line of error (the last line) and Terminal didn't upchuck: Last login: Sun Jul 15 23:47:43 on console zeus:~ kytan$ echo $DISPLAY /tmp/launch-vuNxLR/:0 zeus:~ kytan$ sudo wireshark Password: Xlib: extension "RANDR" missing on display "/tmp/launch-vuNxLR/:0". (wireshark:344): Gdk-WARNING **: shmget failed: error 12 (Cannot allocate memory) wireshark: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-vuNxLR/:0. zeus:~ kytan$ While wireshark was attempting to come up, it displayed a grey but blank window before X11 died and kicked wireshark's legs out from under it... Any ideas that don't involve having to reinstall the X11 server executables? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From ktan at realityartisans.com Sun Jul 15 21:31:59 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 16 Jul 2012 00:31:59 -0400 Subject: Error when trying to start wireshark under X11 In-Reply-To: <5003946F.3010406@realityartisans.com> References: <50037EE3.50009@realityartisans.com> <5003946F.3010406@realityartisans.com> Message-ID: <5003993F.1010209@realityartisans.com> On 7/16/12 00:11, Kok-Yong Tan wrote: > On 7/15/12 23:27, Brandon Allbery wrote: >> On Sun, Jul 15, 2012 at 10:39 PM, Kok-Yong Tan >> > wrote: >> >> Can anyone tell me what this error means when I try to start >> wireshark in an xterm window via the X11 system: >> >> bash-3.2$ sudo wireshark >> >> (wireshark:11767): Gtk-WARNING **: cannot open display: :0.0 >> >> >> It means something messed with $DISPLAY, which you should not set on >> OS X; launchd sets it correctly and overriding it can cause problems >> like this. You're probably setting it in .bash_profile (or .profile, >> or being really wrong and setting it in .bashrc). Don't. >> >> -- >> brandon s allbery allbery.b at gmail.com >> wandering unix systems administrator (available) (412) 475-9364 >> vm/sms >> > > Thanks for the info. I went into .bashrc and found an explicit > setting for the DISPLAY environment variable which I ripped out. Then > I restarted X11 and did "sudo wireshark" whereupon X11 crashed and > took wireshark with it. I then tried doing the same thing under a > Terminal window and the same thing happened, except I got an extra > line of error (the last line) and Terminal didn't upchuck: > > Last login: Sun Jul 15 23:47:43 on console > zeus:~ kytan$ echo $DISPLAY > /tmp/launch-vuNxLR/:0 > zeus:~ kytan$ sudo wireshark > Password: > Xlib: extension "RANDR" missing on display "/tmp/launch-vuNxLR/:0". > > (wireshark:344): Gdk-WARNING **: shmget failed: error 12 (Cannot > allocate memory) > wireshark: Fatal IO error 35 (Resource temporarily unavailable) on X > server /tmp/launch-vuNxLR/:0. > zeus:~ kytan$ > > While wireshark was attempting to come up, it displayed a grey but > blank window before X11 died and kicked wireshark's legs out from > under it... Any ideas that don't involve having to reinstall the X11 > server executables? > It appears that when I changed the default compiler, the "sudo port -v install wireshark configure.compiler=gcc-4.2" command might not have recompiled the ports that wireshark depends on and also compiled a different variant than what I wanted, thus contributing to this problem. So, I've uninstalled the unwanted variants, leaving the one I want and try the following command in the meantime and let it do its "thing" overnight and will report back on what happens if the build succeeds and when I try to run the results: sudo port -v upgrade wireshark configure.compiler=gcc-4.2 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From ktan at realityartisans.com Sun Jul 15 22:20:53 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 16 Jul 2012 01:20:53 -0400 Subject: Error when trying to start wireshark under X11 In-Reply-To: <5003993F.1010209@realityartisans.com> References: <50037EE3.50009@realityartisans.com> <5003946F.3010406@realityartisans.com> <5003993F.1010209@realityartisans.com> Message-ID: <5003A4B5.4000608@realityartisans.com> On 7/16/12 00:31, Kok-Yong Tan wrote: > On 7/16/12 00:11, Kok-Yong Tan wrote: >> On 7/15/12 23:27, Brandon Allbery wrote: >>> On Sun, Jul 15, 2012 at 10:39 PM, Kok-Yong Tan >>> > wrote: >>> >>> Can anyone tell me what this error means when I try to start >>> wireshark in an xterm window via the X11 system: >>> >>> bash-3.2$ sudo wireshark >>> >>> (wireshark:11767): Gtk-WARNING **: cannot open display: :0.0 >>> >>> >>> It means something messed with $DISPLAY, which you should not set on >>> OS X; launchd sets it correctly and overriding it can cause problems >>> like this. You're probably setting it in .bash_profile (or >>> .profile, or being really wrong and setting it in .bashrc). Don't. >>> >>> -- >>> brandon s allbery allbery.b at gmail.com >>> wandering unix systems administrator (available) (412) 475-9364 >>> vm/sms >>> >> >> Thanks for the info. I went into .bashrc and found an explicit >> setting for the DISPLAY environment variable which I ripped out. >> Then I restarted X11 and did "sudo wireshark" whereupon X11 crashed >> and took wireshark with it. I then tried doing the same thing under >> a Terminal window and the same thing happened, except I got an extra >> line of error (the last line) and Terminal didn't upchuck: >> >> Last login: Sun Jul 15 23:47:43 on console >> zeus:~ kytan$ echo $DISPLAY >> /tmp/launch-vuNxLR/:0 >> zeus:~ kytan$ sudo wireshark >> Password: >> Xlib: extension "RANDR" missing on display "/tmp/launch-vuNxLR/:0". >> >> (wireshark:344): Gdk-WARNING **: shmget failed: error 12 (Cannot >> allocate memory) >> wireshark: Fatal IO error 35 (Resource temporarily unavailable) on X >> server /tmp/launch-vuNxLR/:0. >> zeus:~ kytan$ >> >> While wireshark was attempting to come up, it displayed a grey but >> blank window before X11 died and kicked wireshark's legs out from >> under it... Any ideas that don't involve having to reinstall the X11 >> server executables? >> > It appears that when I changed the default compiler, the "sudo port -v > install wireshark configure.compiler=gcc-4.2" command might not have > recompiled the ports that wireshark depends on and also compiled a > different variant than what I wanted, thus contributing to this > problem. So, I've uninstalled the unwanted variants, leaving the one > I want and try the following command in the meantime and let it do its > "thing" overnight and will report back on what happens if the build > succeeds and when I try to run the results: > > sudo port -v upgrade wireshark configure.compiler=gcc-4.2 Hmmm...that seems to be only recompiling wireshark itself. Is there a command in MacPorts that will do a clean for *EVERYTHING* that wireshark depends on without wiping out tarballs? i.e., take the list generated by "port -v rdeps wireshark" and run "port clean " on every individual portname? Then I can recompile the whole tree from scratch. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From ryandesign at macports.org Mon Jul 16 00:42:17 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 16 Jul 2012 02:42:17 -0500 Subject: Error when trying to start wireshark under X11 In-Reply-To: <5003A4B5.4000608@realityartisans.com> References: <50037EE3.50009@realityartisans.com> <5003946F.3010406@realityartisans.com> <5003993F.1010209@realityartisans.com> <5003A4B5.4000608@realityartisans.com> Message-ID: <39513185-6C61-4E87-9FAE-6A5B46954B2B@macports.org> On Jul 16, 2012, at 00:20, Kok-Yong Tan wrote: > On 7/16/12 00:31, Kok-Yong Tan wrote: >> It appears that when I changed the default compiler, the "sudo port -v install wireshark configure.compiler=gcc-4.2" command might not have recompiled the ports that wireshark depends on and also compiled a different variant than what I wanted, thus contributing to this problem. So, I've uninstalled the unwanted variants, leaving the one I want and try the following command in the meantime and let it do its "thing" overnight and will report back on what happens if the build succeeds and when I try to run the results: >> >> sudo port -v upgrade wireshark configure.compiler=gcc-4.2 > > Hmmm...that seems to be only recompiling wireshark itself. Correct, that's all that it's designed to do. > Is there a command in MacPorts that will do a clean for *EVERYTHING* that wireshark depends on without wiping out tarballs? i.e., take the list generated by "port -v rdeps wireshark" and run "port clean " on every individual portname? Then I can recompile the whole tree from scratch. Sure, that would be: sudo port clean rdepof:wireshark Note that would only clean them; it would not uninstall them. Thus MacPorts would not try to rebuild them. If you're wanting to rebuild them all with a different compiler (which as far as I know shouldn't be necessary) then you could: sudo port -f uninstall rdepof:wireshark This will likely break many of the other ports that still remain installed, until you reinstall those dependencies. From allbery.b at gmail.com Mon Jul 16 07:27:44 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Mon, 16 Jul 2012 10:27:44 -0400 Subject: Error when trying to start wireshark under X11 In-Reply-To: <5003A4B5.4000608@realityartisans.com> References: <50037EE3.50009@realityartisans.com> <5003946F.3010406@realityartisans.com> <5003993F.1010209@realityartisans.com> <5003A4B5.4000608@realityartisans.com> Message-ID: On Mon, Jul 16, 2012 at 1:20 AM, Kok-Yong Tan wrote: > Hmmm...that seems to be only recompiling wireshark itself. Is there a > command in MacPorts that will do a clean for *EVERYTHING* that wireshark > depends on without wiping out tarballs? i.e., take the list generated by > "port -v rdeps wireshark" and run "port clean " on every > individual portname? Then I can recompile the whole tree from scratch. > I think adding -f would do it, but I also think you're barking up the wrong tree. You got an shm error. What does "ipcs -Mm" say? (That command is for Lion; it may not work on earlier releases.) FWIW I use wireshark and do not see the X error. Which X11 are you using? Leopard, SL, Lion, XQuartz (version?), MacPorts (version?)? -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From ktan at realityartisans.com Mon Jul 16 11:30:53 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Mon, 16 Jul 2012 14:30:53 -0400 Subject: Error when trying to start wireshark under X11 In-Reply-To: References: <50037EE3.50009@realityartisans.com> <5003946F.3010406@realityartisans.com> <5003993F.1010209@realityartisans.com> <5003A4B5.4000608@realityartisans.com> Message-ID: <50045DDD.8080403@realityartisans.com> On 7/16/12 10:27, Brandon Allbery wrote: > On Mon, Jul 16, 2012 at 1:20 AM, Kok-Yong Tan > > wrote: > > Hmmm...that seems to be only recompiling wireshark itself. Is > there a command in MacPorts that will do a clean for *EVERYTHING* > that wireshark depends on without wiping out tarballs? i.e., take > the list generated by "port -v rdeps wireshark" and run "port > clean " on every individual portname? Then I can > recompile the whole tree from scratch. > > > I think adding -f would do it, but I also think you're barking up the > wrong tree. You got an shm error. What does "ipcs -Mm" say? (That > command is for Lion; it may not work on earlier releases.) > > FWIW I use wireshark and do not see the X error. Which X11 are you > using? Leopard, SL, Lion, XQuartz (version?), MacPorts (version?)? > Uh...no. The -f didn't do it. But it's still possible I'm barking up the wrong tree. This is a Leopard 10.5.8 system on PPC with the following parameters: X11 is "XQuartz 2.1.6 (xorg-server 1.4.2-apple33) Leopard version is 10.5.8 MacPorts is now 2.1.1 (since I basically shitcanned /opt, installed MacPorts 2.1.1 from .dmg, made a copy of macports.config to ~/.macports/macports.config, added the default_compiler key and set it to gcc-4.2 and uncommented and changed the build_arch key to ppc. I decided to modify macports.config rather than add the environment variables during the "sudo port -v install ..." command phase. And here's the result of the ipcs command along with uname: zeus:~ kytan$ ipcs -Mm IPC status from as of Mon Jul 16 14:28:50 EDT 2012 shminfo: shmmax: 4194304 (max shared memory segment size) shmmin: 1 (min shared memory segment size) shmmni: 32 (max number of shared memory identifiers) shmseg: 8 (max shared memory segments per process) shmall: 1024 (max amount of shared memory in pages) T ID KEY MODE OWNER GROUP Shared Memory: m 65536 0x54243263 --rw-rw-rw- root wheel m 65537 0x007cdcd9 --rw------- intermapper intermapper m 3473410 0x53414e44 --rw-rw-rw- kytan staff zeus:~ kytan$ uname -a Darwin zeus.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC Power Macintosh zeus:~ kytan$ On a separate note, wireshark 1.8.0 builds and runs fine on my Intel MBP laptop but that's Snow Leopard 10.6.8, Xcode 3.2.6 and X11 is XQuartz 2.3.6 (xorg-server 1.4.2-apple56) From jeremyhu at macports.org Mon Jul 16 12:59:06 2012 From: jeremyhu at macports.org (Jeremy Huddleston Sequoia) Date: Mon, 16 Jul 2012 12:59:06 -0700 Subject: Error when trying to start wireshark under X11 In-Reply-To: <5003993F.1010209@realityartisans.com> References: <50037EE3.50009@realityartisans.com> <5003946F.3010406@realityartisans.com> <5003993F.1010209@realityartisans.com> Message-ID: <93F45FF0-4714-49FE-A456-9FA0553A6895@macports.org> On Jul 15, 2012, at 21:31, Kok-Yong Tan wrote: >> Thanks for the info. I went into .bashrc and found an explicit setting for the DISPLAY environment variable which I ripped out. Then I restarted X11 and did "sudo wireshark" whereupon X11 crashed and took wireshark with it. What version of XQuartz? OS X? Can you provide the crash log? >> (wireshark:344): Gdk-WARNING **: shmget failed: error 12 (Cannot allocate memory) >> wireshark: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-vuNxLR/:0. >> zeus:~ kytan$ Perhaps a bug in MIT-SHM ... > It appears that when I changed the default compiler, the "sudo port -v install wireshark configure.compiler=gcc-4.2" Why did you do that? What problem are you trying to fix by forcing that compiler to be used? What Xcode version do you have? gcc-4.2 is *ancient* and should only be used as a last resort, or if you're on an old OS (in which case I'd recommend installing a newer compiler with MacPorts and using it instead). From kowalskM at cs.moravian.edu Tue Jul 17 06:20:38 2012 From: kowalskM at cs.moravian.edu (myron) Date: Tue, 17 Jul 2012 09:20:38 -0400 Subject: wireshark fails to start In-Reply-To: <39513185-6C61-4E87-9FAE-6A5B46954B2B@macports.org> References: <50037EE3.50009@realityartisans.com> <5003946F.3010406@realityartisans.com> <5003993F.1010209@realityartisans.com> <5003A4B5.4000608@realityartisans.com> <39513185-6C61-4E87-9FAE-6A5B46954B2B@macports.org> Message-ID: <305E20A0-83DF-42C0-98FD-33CE4F195A2A@cs.moravian.edu> I had been following a thread about wireshark the other day and decided to start up my wireshark which I had just upgraded. I hadn't used it for a few months, and it was working then. Now I'm getting a similar problem as the other poster. I didn't get what his solution was. I start in an X11 window. An empty gray box appears and then everything crashes. Here's what in problem report that comes up. Process: X11.bin [41824] Path: /Applications/Utilities/X11.app/Contents/MacOS/X11.bin Identifier: org.x.X11 Version: 2.1.6 (2.1.6) Build Info: X11server-480700~6 Code Type: X86 (Native) Parent Process: launchd [135] Date/Time: 2012-07-17 08:54:58.306 -0400 OS Version: Mac OS X 10.5.8 (9L31a) Report Version: 6 Anonymous UUID: 1F8BA258-8FEC-48D1-8B3B-F173EC688774 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000 Crashed Thread: 2 Application Specific Information: X.Org X Server 1.4.2-apple33 Build Date: 20090327 Thread 2 Crashed: 0 X11.bin 0x00025f38 RootlessGlyphs + 84 1 X11.bin 0x0011e021 CompositeGlyphs + 163 2 X11.bin 0x00121b60 ProcRenderCompositeGlyphs + 1526 3 X11.bin 0x001236e8 ProcRenderDispatch + 60 4 X11.bin 0x000ec41a XaceCatchExtProc + 173 5 X11.bin 0x0007dad1 Dispatch + 691 6 X11.bin 0x0009b497 dix_main + 1818 7 X11.bin 0x00019526 server_thread + 62 8 libSystem.B.dylib 0x94754055 _pthread_start + 321 9 libSystem.B.dylib 0x94753f12 thread_start + 34 Thread 2 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0x00025ef5 ecx: 0x00000070 edx: 0x006ef320 edi: 0x00000003 esi: 0x00025ee4 ebp: 0xb019f618 esp: 0xb019f570 ss: 0x0000001f efl: 0x00010206 eip: 0x00025f38 cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037 cr2: 0x00000000 7/17/12 8:54:52 AM [0x0-0x1ea1ea].org.x.X11[41824] X11.app Handing off fd to server thread via DarwinListenOnOpenFD(5) 7/17/12 8:54:52 AM [0x0-0x1ea1ea].org.x.X11[41824] DarwinListenOnOpenFD: 5 7/17/12 8:54:52 AM [0x0-0x1ea1ea].org.x.X11[41824] Calling ListenOnOpenFD() for new fd: 5 7/17/12 8:54:52 AM [0x0-0x1ea1ea].org.x.X11[41824] AllocNewConnection: client index = 3, socket fd = 12 7/17/12 8:54:52 AM [0x0-0x1ea1ea].org.x.X11[41824] AllocNewConnection: client index = 4, socket fd = 13 7/17/12 8:54:52 AM [0x0-0x1ea1ea].org.x.X11[41824] X11.app: Launching / usr/X11/bin/xterm: 7/17/12 8:54:52 AM [0x0-0x1ea1ea].org.x.X11[41824] argv[0] = /bin/sh 7/17/12 8:54:52 AM [0x0-0x1ea1ea].org.x.X11[41824] argv[1] = -c 7/17/12 8:54:52 AM [0x0-0x1ea1ea].org.x.X11[41824] argv[2] = /usr/X11/ bin/xterm 7/17/12 8:54:52 AM [0x0-0x1ea1ea].org.x.X11[41824] AllocNewConnection: client index = 3, socket fd = 15 7/17/12 8:54:53 AM org.x.privileged_startx[41851] font_cache: Done 7/17/12 8:54:57 AM [0x0-0x1ea1ea].org.x.X11[41824] AllocNewConnection: client index = 5, socket fd = 18 7/17/12 8:55:00 AM ReportCrash[41983] Formulating crash report for process X11.bin[41824] 7/17/12 8:55:01 AM org.x.startx[41836] Xquartz: start_x11_server: (ipc/ mig) server died 7/17/12 8:55:01 AM com.apple.launchd[135] ([0x0-0x1ea1ea].org.x.X11[41824]) Stray process with PGID equal to this dead job: PID 41835 PPID 1 xterm 7/17/12 8:55:01 AM com.apple.launchd[135] ([0x0-0x1ea1ea].org.x.X11[41824]) Exited abnormally: Bus error 7/17/12 8:55:01 AM org.x.startx[41836] xinit: connection to X server lost. 7/17/12 8:55:01 AM [0x0-0x1ea1ea].org.x.X11 xterm: fatal IO error 32 (Broken pipe) or KillClient on X server "/tmp/launch-5K8QtL/:0" --myron ================================= Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College myron at moravian.edu (610) 861-1441 From allbery.b at gmail.com Tue Jul 17 08:03:02 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Tue, 17 Jul 2012 11:03:02 -0400 Subject: wireshark fails to start In-Reply-To: <305E20A0-83DF-42C0-98FD-33CE4F195A2A@cs.moravian.edu> References: <50037EE3.50009@realityartisans.com> <5003946F.3010406@realityartisans.com> <5003993F.1010209@realityartisans.com> <5003A4B5.4000608@realityartisans.com> <39513185-6C61-4E87-9FAE-6A5B46954B2B@macports.org> <305E20A0-83DF-42C0-98FD-33CE4F195A2A@cs.moravian.edu> Message-ID: On Tue, Jul 17, 2012 at 9:20 AM, myron wrote: > I had been following a thread about wireshark the other day and decided to > start up my wireshark which I had > just upgraded. I hadn't used it for a few months, and it was working then. > Now I'm getting a similar problem as the > other poster. I didn't get what his solution was. > > I start in an X11 window. An empty gray box appears and then everything > crashes. Here's what in problem report that > comes up. > For what it's worth, I am still not seeing this --- but I'm using XQuartz, not stock (Lion) X11.app. I *did* see one oddity, though: it didn't display its splash screen or open its main window until I explicitly switched focus to XQuartz. It seemed to be "hung" before I did that. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From ktan at realityartisans.com Tue Jul 17 09:02:20 2012 From: ktan at realityartisans.com (Kok-Yong Tan) Date: Tue, 17 Jul 2012 12:02:20 -0400 Subject: Error when trying to start wireshark under X11 In-Reply-To: <93F45FF0-4714-49FE-A456-9FA0553A6895@macports.org> References: <50037EE3.50009@realityartisans.com> <5003946F.3010406@realityartisans.com> <5003993F.1010209@realityartisans.com> <93F45FF0-4714-49FE-A456-9FA0553A6895@macports.org> Message-ID: <50058C8C.3060501@realityartisans.com> On 7/16/12 15:59, Jeremy Huddleston Sequoia wrote: > On Jul 15, 2012, at 21:31, Kok-Yong Tan wrote: > >>> Thanks for the info. I went into .bashrc and found an explicit setting for the DISPLAY environment variable which I ripped out. Then I restarted X11 and did "sudo wireshark" whereupon X11 crashed and took wireshark with it. > What version of XQuartz? OS X? Can you provide the crash log? This is a Leopard 10.5.8 system on PPC with the following parameters: X11 is "XQuartz 2.1.6 (xorg-server 1.4.2-apple33) Leopard version is 10.5.8 MacPorts is now 2.1.1 since I wiped out /opt and reinstalled MacPorts from .dmg. >>> (wireshark:344): Gdk-WARNING **: shmget failed: error 12 (Cannot allocate memory) >>> wireshark: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-vuNxLR/:0. >>> zeus:~ kytan$ > Perhaps a bug in MIT-SHM ... Possibly. I have no idea. >> It appears that when I changed the default compiler, the "sudo port -v install wireshark configure.compiler=gcc-4.2" > Why did you do that? What problem are you trying to fix by forcing that compiler to be used? What Xcode version do you have? gcc-4.2 is *ancient* and should only be used as a last resort, or if you're on an old OS (in which case I'd recommend installing a newer compiler with MacPorts and using it instead). > A suggestion from someone on this thread... -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6240 bytes Desc: S/MIME Cryptographic Signature URL: From kowalskM at cs.moravian.edu Tue Jul 17 09:49:18 2012 From: kowalskM at cs.moravian.edu (myron) Date: Tue, 17 Jul 2012 12:49:18 -0400 Subject: wireshark fails to start In-Reply-To: References: <50037EE3.50009@realityartisans.com> <5003946F.3010406@realityartisans.com> <5003993F.1010209@realityartisans.com> <5003A4B5.4000608@realityartisans.com> <39513185-6C61-4E87-9FAE-6A5B46954B2B@macports.org> <305E20A0-83DF-42C0-98FD-33CE4F195A2A@cs.moravian.edu> Message-ID: <95BF94C4-DA86-479E-B6F7-772572A8391A@cs.moravian.edu> On Jul 17, 2012, at 11:03 AM, Brandon Allbery wrote: > On Tue, Jul 17, 2012 at 9:20 AM, myron > wrote: > I had been following a thread about wireshark the other day and > decided to start up my wireshark which I had > just upgraded. I hadn't used it for a few months, and it was working > then. Now I'm getting a similar problem as the > other poster. I didn't get what his solution was. > > I start in an X11 window. An empty gray box appears and then > everything crashes. Here's what in problem report that > comes up. > > For what it's worth, I am still not seeing this --- but I'm using > XQuartz, not stock (Lion) X11.app. I *did* see one oddity, though: > it didn't display its splash screen or open its main window until I > explicitly switched focus to XQuartz. It seemed to be "hung" before > I did that. > > -- > brandon s allbery allbery.b at gmail.com > wandering unix systems administrator (available) (412) 475-9364 > vm/sms > For what it's worth, here's the system call errors that are happening. It would be nice to get wireshark working again. Any ideas what to do? Reinstall macports? X11.bin select 4 1 Interrupted system call X11.bin writev 35 1 Resource temporarily unavailable bash __pthread_canceled 22 1 Invalid argument bash kill 1 1 Operation not permitted bash setpgid 1 1 Operation not permitted bash sigreturn -2 1 bash wait4 4 1 Interrupted system call notifyd lstat 2 1 No such file or directory perl __pthread_canceled 22 1 Invalid argument perl sigreturn -2 1 privileged_star __semwait_signal 60 1 Operation timed out quartz-wm select 4 1 Interrupted system call quartz-wm sigreturn -2 1 sh open 2 1 No such file or directory sh read 5 1 Input/output error wireshark read 35 1 Resource temporarily unavailable wireshark unlink 2 1 No such file or directory xinit kill 3 1 No such process xinit read 35 1 Resource temporarily unavailable xterm chown 1 1 Operation not permitted xterm read 35 1 Resource temporarily unavailable .... wireshark: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-rJaRmL/:0. select(0x4, 0xBFFFF440, 0xBFFFF3C0, 0x0, 0x0) = 1 0 recvfrom(0x3, 0x1478058, 0x1000) = 0 0 write_nocancel(0x2, "wireshark: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-rJaRmL/:0.\n\0", 0x63) = 99 0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rpgoldman at sift.info Tue Jul 17 10:36:07 2012 From: rpgoldman at sift.info (Robert Goldman) Date: Tue, 17 Jul 2012 12:36:07 -0500 Subject: Problem with ECL (embeddable common lisp) 12.2.1 on Lion Message-ID: <5005A287.9020305@sift.info> When I try to run some test code on this system, I get this error: LOAD: Could not load file #P"/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas" (Error: "dlopen(/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas, 10): Library not loaded: /opt/local/lib/libffi.5.dylib This makes sense, because I have libffi.6.dylib, not .5. Should this be reflected in the dependencies of ecl? Because if I do port deps ecl I get ecl @12.2.1_0 has no dependencies. I'm not confident enough in my understanding of ports to determine whether this is a bona fide bug, or if it is simply a misconfiguration on my part. Thanks! From allbery.b at gmail.com Tue Jul 17 10:41:41 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Tue, 17 Jul 2012 13:41:41 -0400 Subject: Problem with ECL (embeddable common lisp) 12.2.1 on Lion In-Reply-To: <5005A287.9020305@sift.info> References: <5005A287.9020305@sift.info> Message-ID: On Tue, Jul 17, 2012 at 1:36 PM, Robert Goldman wrote: > > "dlopen(/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas, > 10): Library not loaded: /opt/local/lib/libffi.5.dylib > (...) > ecl @12.2.1_0 has no dependencies. > That'd be a legitimate port bug, yes. File a ticket against ecl; in the meantime if you rebuild it with "sudo port -n -f upgrade ecl" it should pick up the updated libffi. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonesc at hep.phy.cam.ac.uk Tue Jul 17 10:44:43 2012 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Tue, 17 Jul 2012 18:44:43 +0100 Subject: Error when trying to start wireshark under X11 In-Reply-To: <50058C8C.3060501@realityartisans.com> References: <50037EE3.50009@realityartisans.com> <5003946F.3010406@realityartisans.com> <5003993F.1010209@realityartisans.com> <93F45FF0-4714-49FE-A456-9FA0553A6895@macports.org> <50058C8C.3060501@realityartisans.com> Message-ID: <4317D6E8-8F20-4DDE-8476-743FB8A0F858@hep.phy.cam.ac.uk> >>> It appears that when I changed the default compiler, the "sudo port -v install wireshark configure.compiler=gcc-4.2" >> Why did you do that? What problem are you trying to fix by forcing that compiler to be used? What Xcode version do you have? gcc-4.2 is *ancient* and should only be used as a last resort, or if you're on an old OS (in which case I'd recommend installing a newer compiler with MacPorts and using it instead). >> > > A suggestion from someone on this thread? Actually no, it wasn't. The suggestion was to try using gcc-4.2 for the *one* port that was failing, not to force it for everything... -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2966 bytes Desc: not available URL: From mparchet at sunrise.ch Tue Jul 17 14:18:02 2012 From: mparchet at sunrise.ch (Michael Parchet) Date: Tue, 17 Jul 2012 23:18:02 +0200 Subject: qt4-creaor qt-sdk amd qmake Message-ID: <5005D68A.3050808@sunrise.ch> Hello, To configure qt4-creator, I need a valid qt-sdk and qmake in the PATH. In with package is qt-sdk require by qt-creator ? In with package is the qt4-creator examples ? Can you help me please ? Best regards mparchet From jolivetinsar at gmail.com Tue Jul 17 17:06:46 2012 From: jolivetinsar at gmail.com (Romain Jolivet) Date: Tue, 17 Jul 2012 17:06:46 -0700 Subject: Build Petsc with Shared Libraries Message-ID: <0AD5E35D-E5B2-4AC5-AB3E-9F90D4D56C3A@gmail.com> Hello, I would like to build petsc using macports (because it is easy), and I would need the shared libraries option to be on. I created a variant on the petsc port, adding: variant shared description {build with shared libraries} { configure.args-delete --with-shared-libraries=0 configure.args-delete --with-pic=fPIC configure.args-append --with-shared-libraries=1 } I have to delete --with-pic=fPIC, otherwise it does not run. Then, it configures and builds fine, but when macports checks on the created files, it complains, and restarts the whole process (and does it over and over again): It says: ---> Updating database of binaries: 100.0% ---> Scanning binaries for linking errors: 100.0% ---> Found 3 broken file(s), matching files to ports ---> Found 1 broken port(s), determining rebuild order I don't know how to modify what macport is checking (and probably, I should not). Can someone tell me what I am doing wrong? Thank you very much Romain Romain Jolivet Highland Park, Los Angeles, CA jolivetinsar at gmail.com +1 (626) 560 6356 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thegooddale at gmail.com Tue Jul 17 18:12:18 2012 From: thegooddale at gmail.com (Yansky .) Date: Wed, 18 Jul 2012 11:12:18 +1000 Subject: Trouble accessing trac.macports.org In-Reply-To: References: Message-ID: Anybody on the macports.org admin working on this? I'd really like to be able to access https://trac.macports.org On Mon, Jul 16, 2012 at 9:35 AM, Mike Savory wrote: > Looking at the DNS records, I see that trac has an AAAA record and the parent domain doesn't... >> dig trac.macports.org AAAA > trac.macports.org. 462 IN CNAME iota4.macosforge.org. > > but >> dig iota4.macosforge.org AAAA > > Fails for me > > Could be we have IPv6 connectivity issues? > > Mike > > > On Jul 15, 2012, at 2:34 PM, Yansky . wrote: > >> Hi, I seem to be having some issues accessing https://trac.macports.org >> >> http://www.downforeveryoneorjustme.com/trac.macports.org says it's up, >> but I can't get to it. >> >> The weird thing is https://macports.org seems to resolve just fine. I >> did a traceroute of both domain/sub-domain and trac.macports.org seems >> to time out. I thought it might be my ISP (TPG Australia), but it also >> seems to time out using google's dns as well. >> >> trac.macports.org traceroute ? http://pastebin.com/N7vsV6x0 >> macports.org traceroute ? http://pastebin.com/Bfw0DeUa >> >> Anyone have any ideas? From ryandesign at macports.org Tue Jul 17 21:35:29 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 17 Jul 2012 23:35:29 -0500 Subject: qt4-creaor qt-sdk amd qmake In-Reply-To: <5005D68A.3050808@sunrise.ch> References: <5005D68A.3050808@sunrise.ch> Message-ID: <6A36D45F-59A6-4405-9BBB-82058A4B39F2@macports.org> On Jul 17, 2012, at 16:18, Michael Parchet wrote: > In with package is qt-sdk require by qt-creator ? qt4-mac, I assume. > In with package is the qt4-creator examples ? If anywhere, probably qt4-creator-mac. From ryandesign at macports.org Tue Jul 17 21:36:58 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 17 Jul 2012 23:36:58 -0500 Subject: Build Petsc with Shared Libraries In-Reply-To: <0AD5E35D-E5B2-4AC5-AB3E-9F90D4D56C3A@gmail.com> References: <0AD5E35D-E5B2-4AC5-AB3E-9F90D4D56C3A@gmail.com> Message-ID: On Jul 17, 2012, at 19:06, Romain Jolivet wrote: > I would like to build petsc using macports (because it is easy), and I would need the shared libraries option to be on. > I created a variant on the petsc port, adding: > > variant shared description {build with shared libraries} { > configure.args-delete --with-shared-libraries=0 > configure.args-delete --with-pic=fPIC > configure.args-append --with-shared-libraries=1 > } > > I have to delete --with-pic=fPIC, otherwise it does not run. Then, it configures and builds fine, but when macports checks on the created files, it complains, and restarts the whole process (and does it over and over again): > > It says: > > ---> Updating database of binaries: 100.0% > ---> Scanning binaries for linking errors: 100.0% > ---> Found 3 broken file(s), matching files to ports > ---> Found 1 broken port(s), determining rebuild order And which port does it determine is broken? petsc? > I don't know how to modify what macport is checking (and probably, I should not). Can someone tell me what I am doing wrong? You can turn off the rev-upgrade feature if you want. To turn it off just for one port installation, you could use the "--no-rev-upgrade" flag. (It must go after the words "port install" (or "port upgrade") and before the name of the port.) Or you can turn it off entirely in macports.conf. From ryandesign at macports.org Tue Jul 17 21:37:37 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 17 Jul 2012 23:37:37 -0500 Subject: Trouble accessing trac.macports.org In-Reply-To: References: Message-ID: It works fine for me. The admin's address is admin (at) macosforge.org if you would like to contact him. On Jul 17, 2012, at 20:12, Yansky . wrote: > Anybody on the macports.org admin working on this? I'd really like to > be able to access https://trac.macports.org > > On Mon, Jul 16, 2012 at 9:35 AM, Mike Savory wrote: >> Looking at the DNS records, I see that trac has an AAAA record and the parent domain doesn't... >>> dig trac.macports.org AAAA >> trac.macports.org. 462 IN CNAME iota4.macosforge.org. >> >> but >>> dig iota4.macosforge.org AAAA >> >> Fails for me >> >> Could be we have IPv6 connectivity issues? >> >> Mike >> >> >> On Jul 15, 2012, at 2:34 PM, Yansky . wrote: >> >>> Hi, I seem to be having some issues accessing https://trac.macports.org >>> >>> http://www.downforeveryoneorjustme.com/trac.macports.org says it's up, >>> but I can't get to it. >>> >>> The weird thing is https://macports.org seems to resolve just fine. I >>> did a traceroute of both domain/sub-domain and trac.macports.org seems >>> to time out. I thought it might be my ISP (TPG Australia), but it also >>> seems to time out using google's dns as well. >>> >>> trac.macports.org traceroute ? http://pastebin.com/N7vsV6x0 >>> macports.org traceroute ? http://pastebin.com/Bfw0DeUa >>> >>> Anyone have any ideas? From jolivetinsar at gmail.com Tue Jul 17 23:52:12 2012 From: jolivetinsar at gmail.com (Romain Jolivet) Date: Tue, 17 Jul 2012 23:52:12 -0700 Subject: Build Petsc with Shared Libraries In-Reply-To: References: <0AD5E35D-E5B2-4AC5-AB3E-9F90D4D56C3A@gmail.com> Message-ID: Thanks for your answer. The port that is broken is petsc (I guess, as it rebuilds it, and not the dependencies). I'll try with --no-rev-upgrade flag and get back to you if I cannot make it Romain > > On Jul 17, 2012, at 19:06, Romain Jolivet wrote: > >> I would like to build petsc using macports (because it is easy), and I would need the shared libraries option to be on. >> I created a variant on the petsc port, adding: >> >> variant shared description {build with shared libraries} { >> configure.args-delete --with-shared-libraries=0 >> configure.args-delete --with-pic=fPIC >> configure.args-append --with-shared-libraries=1 >> } >> >> I have to delete --with-pic=fPIC, otherwise it does not run. Then, it configures and builds fine, but when macports checks on the created files, it complains, and restarts the whole process (and does it over and over again): >> >> It says: >> >> ---> Updating database of binaries: 100.0% >> ---> Scanning binaries for linking errors: 100.0% >> ---> Found 3 broken file(s), matching files to ports >> ---> Found 1 broken port(s), determining rebuild order > > And which port does it determine is broken? petsc? > > >> I don't know how to modify what macport is checking (and probably, I should not). Can someone tell me what I am doing wrong? > > You can turn off the rev-upgrade feature if you want. To turn it off just for one port installation, you could use the "--no-rev-upgrade" flag. (It must go after the words "port install" (or "port upgrade") and before the name of the port.) Or you can turn it off entirely in macports.conf. > > From cal at macports.org Wed Jul 18 03:00:02 2012 From: cal at macports.org (Clemens Lang) Date: Wed, 18 Jul 2012 12:00:02 +0200 Subject: Build Petsc with Shared Libraries In-Reply-To: References: <0AD5E35D-E5B2-4AC5-AB3E-9F90D4D56C3A@gmail.com> Message-ID: <20120718100002.GS27027@towel.neverpanic.de> Hi, On Tue, Jul 17, 2012 at 11:52:12PM -0700, Romain Jolivet wrote: > The port that is broken is petsc (I guess, as it rebuilds it, and not > the dependencies). I'll try with --no-rev-upgrade flag and get back > to you if I cannot make it of course you can ignore the problem, but the proper way to do this would be to fix the problem. Can you run port -d -y rev-upgrade and post the output? -- Clemens Lang From kowalskM at cs.moravian.edu Wed Jul 18 06:51:00 2012 From: kowalskM at cs.moravian.edu (myron) Date: Wed, 18 Jul 2012 09:51:00 -0400 Subject: wireshark fails to start In-Reply-To: <6BF2A639-08ED-4545-9144-45A5306BCEDF@apple.com> References: <50037EE3.50009@realityartisans.com> <5003946F.3010406@realityartisans.com> <5003993F.1010209@realityartisans.com> <5003A4B5.4000608@realityartisans.com> <39513185-6C61-4E87-9FAE-6A5B46954B2B@macports.org> <305E20A0-83DF-42C0-98FD-33CE4F195A2A@cs.moravian.edu> <6BF2A639-08ED-4545-9144-45A5306BCEDF@apple.com> Message-ID: <8136D899-9C15-4C46-8894-76D3829F89DE@cs.moravian.edu> I installed the xorg-server and now wireshark works fine. Thanks for your help. --myron ================================= Myron Kowalski MoCoSIN Network/Systems Administrator Moravian College myron at moravian.edu (610) 861-1441 On Jul 17, 2012, at 1:46 PM, Jeremy Huddleston Sequoia wrote: > Ok, now that someone has provided a crash report... > > This smells like https://trac.macports.org/ticket/30927 to me. > Update your version of XQuartz, or use the xorg-server port. > > --Jeremy > > On Jul 17, 2012, at 8:03 AM, Brandon Allbery > wrote: > >> On Tue, Jul 17, 2012 at 9:20 AM, myron >> wrote: >> >>> I had been following a thread about wireshark the other day and >>> decided to >>> start up my wireshark which I had >>> just upgraded. I hadn't used it for a few months, and it was >>> working then. >>> Now I'm getting a similar problem as the >>> other poster. I didn't get what his solution was. >>> >>> I start in an X11 window. An empty gray box appears and then >>> everything >>> crashes. Here's what in problem report that >>> comes up. >>> >> >> For what it's worth, I am still not seeing this --- but I'm using >> XQuartz, >> not stock (Lion) X11.app. I *did* see one oddity, though: it didn't >> display its splash screen or open its main window until I explicitly >> switched focus to XQuartz. It seemed to be "hung" before I did that. >> >> -- >> brandon s allbery allbery.b at gmail.com >> wandering unix systems administrator (available) (412) 475-9364 >> vm/sms >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo/macports-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From rpgoldman at sift.info Wed Jul 18 07:02:30 2012 From: rpgoldman at sift.info (Robert Goldman) Date: Wed, 18 Jul 2012 09:02:30 -0500 Subject: Problem with ECL (embeddable common lisp) 12.2.1 on Lion In-Reply-To: References: <5005A287.9020305@sift.info> Message-ID: <5006C1F6.8@sift.info> On 7/17/12 Jul 17 -12:41 PM, Brandon Allbery wrote: > On Tue, Jul 17, 2012 at 1:36 PM, Robert Goldman > wrote: > > "dlopen(/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas, > 10): Library not loaded: /opt/local/lib/libffi.5.dylib > > (...) > > ecl @12.2.1_0 has no dependencies. > > > That'd be a legitimate port bug, yes. File a ticket against ecl; in the > meantime if you rebuild it with "sudo port -n -f upgrade ecl" it should > pick up the updated libffi. Actually, FWIW, that upgrade command did not fix ecl. My attempt to run it yielded ---> Scanning binaries for linking errors: 100.0% ---> No broken files found. and then ;;; Loading "/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas" LOAD: Could not load file #P"/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas" (Error: "dlopen(/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas, 10): Library not loaded: /opt/local/lib/libffi.5.dylib Referenced from: /Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas Reason: image not found") I have reported the issue on trac: https://trac.macports.org/ticket/35242 From jolivetinsar at gmail.com Wed Jul 18 09:34:24 2012 From: jolivetinsar at gmail.com (Romain Jolivet) Date: Wed, 18 Jul 2012 09:34:24 -0700 Subject: Build Petsc with Shared Libraries In-Reply-To: <20120718100002.GS27027@towel.neverpanic.de> References: <0AD5E35D-E5B2-4AC5-AB3E-9F90D4D56C3A@gmail.com> <20120718100002.GS27027@towel.neverpanic.de> Message-ID: Hi, Following your advice, I built petsc using the shared libraries: port install petsc +shared then I did run: port -d -y rev-upgrade Attached is the output, It seems the petsc library built this way is not properly working (that's what port says) Romain -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: output.txt URL: -------------- next part -------------- Romain Jolivet Highland Park, Los Angeles, CA jolivetinsar at gmail.com +1 (626) 560 6356 On Jul 18, 2012, at 3:00 AM, Clemens Lang wrote: > Hi, > > On Tue, Jul 17, 2012 at 11:52:12PM -0700, Romain Jolivet wrote: >> The port that is broken is petsc (I guess, as it rebuilds it, and not >> the dependencies). I'll try with --no-rev-upgrade flag and get back >> to you if I cannot make it > > of course you can ignore the problem, but the proper way to do this > would be to fix the problem. Can you run > port -d -y rev-upgrade > and post the output? > > -- > Clemens Lang > From cal at macports.org Wed Jul 18 10:42:08 2012 From: cal at macports.org (Clemens Lang) Date: Wed, 18 Jul 2012 19:42:08 +0200 Subject: Build Petsc with Shared Libraries In-Reply-To: References: <0AD5E35D-E5B2-4AC5-AB3E-9F90D4D56C3A@gmail.com> <20120718100002.GS27027@towel.neverpanic.de> Message-ID: <20120718174208.GT27027@towel.neverpanic.de> Hi, On Wed, Jul 18, 2012 at 09:34:24AM -0700, Romain Jolivet wrote: > DEBUG: Marking /opt/local/lib/petsc/lib/libparmetis.dylib as broken > Could not open /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_petsc/petsc/work/petsc-3.3-p0/darwin/lib/libmetis.dylib: Error opening or reading file (referenced from /opt/local/lib/petsc/lib/libparmetis.dylib) > DEBUG: Marking /opt/local/lib/petsc/lib/libpetsc.dylib as broken > Could not open /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_petsc/petsc/work/petsc-3.3-p0/darwin/lib/libparmetis.dylib: Error opening or reading file (referenced from /opt/local/lib/petsc/lib/libpetsc.dylib) > DEBUG: Marking /opt/local/lib/petsc/lib/libpetsc.dylib as broken The libraries have not been linked correctly. I assume the first line in otool -L /opt/local/lib/petsc/lib/libpetsc.dylib contains the worksrcdir, which causes this issue when linking against it. Please file a bug so the maintainer can fix this. -- Clemens Lang From sean.michael.farley at gmail.com Wed Jul 18 11:11:36 2012 From: sean.michael.farley at gmail.com (Sean Farley) Date: Wed, 18 Jul 2012 13:11:36 -0500 Subject: Build Petsc with Shared Libraries In-Reply-To: <20120718174208.GT27027@towel.neverpanic.de> References: <0AD5E35D-E5B2-4AC5-AB3E-9F90D4D56C3A@gmail.com> <20120718100002.GS27027@towel.neverpanic.de> <20120718174208.GT27027@towel.neverpanic.de> Message-ID: > The libraries have not been linked correctly. I assume the first line in > otool -L /opt/local/lib/petsc/lib/libpetsc.dylib contains the > worksrcdir, which causes this issue when linking against it. > > Please file a bug so the maintainer can fix this. The PETSc portfile is very wrong, particularly with the prefix install. I've been meaning to submit a diff but for the time being, here my own PETSc portfile that I use: https://bitbucket.org/seanfarley/scienceports/src/5b57adccee2f/math/petsc/Portfile Notable things that need to be fixed in the MacPorts version: * don't use both --with-c-support and --with-c++-support * unnecessary to use --with-python * don't use --with-pic * don't use --with-mpi=1 * don't pass ${destroot} to --prefix * don't pass mpi compiler wrappers to --with-{cc,cxx}; just use --with-mpi-dir=${prefix} (the correct compilers will be used based on that) * don't ever mess with blas/lapack options * don't pass things to --LIB If the devs at macports want, they could update metis, parmetis, blacs, scalapck, mumps, ml, and SuiteSparse to my ports located at bitbucket; they are the same ones that are used for --download-{metis,parmetis,blacs,scalapack,mumps,ml,umfpack} and, as a bonus, are all updated to the latest versions. From ryandesign at macports.org Wed Jul 18 17:00:36 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 18 Jul 2012 19:00:36 -0500 Subject: Build Petsc with Shared Libraries In-Reply-To: <20120718174208.GT27027@towel.neverpanic.de> References: <0AD5E35D-E5B2-4AC5-AB3E-9F90D4D56C3A@gmail.com> <20120718100002.GS27027@towel.neverpanic.de> <20120718174208.GT27027@towel.neverpanic.de> Message-ID: On Jul 18, 2012, at 12:42, Clemens Lang wrote: > On Wed, Jul 18, 2012 at 09:34:24AM -0700, Romain Jolivet wrote: >> DEBUG: Marking /opt/local/lib/petsc/lib/libparmetis.dylib as broken >> Could not open /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_petsc/petsc/work/petsc-3.3-p0/darwin/lib/libmetis.dylib: Error opening or reading file (referenced from /opt/local/lib/petsc/lib/libparmetis.dylib) >> DEBUG: Marking /opt/local/lib/petsc/lib/libpetsc.dylib as broken >> Could not open /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_petsc/petsc/work/petsc-3.3-p0/darwin/lib/libparmetis.dylib: Error opening or reading file (referenced from /opt/local/lib/petsc/lib/libpetsc.dylib) >> DEBUG: Marking /opt/local/lib/petsc/lib/libpetsc.dylib as broken > > The libraries have not been linked correctly. I assume the first line in > otool -L /opt/local/lib/petsc/lib/libpetsc.dylib contains the > worksrcdir, which causes this issue when linking against it. > > Please file a bug so the maintainer can fix this. Note that this issue only exists because Romain altered the portfile to install shared libraries. There was no problem with the portfile in its unmodified state. Still, it would be nice to have shared libraries, so it's a reasonable request to add properly-linked shared libraries to the port. Here's the ticket Romain filed: https://trac.macports.org/ticket/35245 On Jul 18, 2012, at 13:11, Sean Farley wrote: > The PETSc portfile is very wrong, particularly with the prefix > install. I've been meaning to submit a diff but for the time being, > here my own PETSc portfile that I use: > > https://bitbucket.org/seanfarley/scienceports/src/5b57adccee2f/math/petsc/Portfile > > Notable things that need to be fixed in the MacPorts version: > > * don't use both --with-c-support and --with-c++-support > * unnecessary to use --with-python > * don't use --with-pic > * don't use --with-mpi=1 > * don't pass ${destroot} to --prefix > * don't pass mpi compiler wrappers to --with-{cc,cxx}; just use > --with-mpi-dir=${prefix} (the correct compilers will be used based on > that) > * don't ever mess with blas/lapack options > * don't pass things to --LIB > > If the devs at macports want, they could update metis, parmetis, > blacs, scalapck, mumps, ml, and SuiteSparse to my ports located at > bitbucket; they are the same ones that are used for > --download-{metis,parmetis,blacs,scalapack,mumps,ml,umfpack} and, as a > bonus, are all updated to the latest versions. Sean, it's up to the maintainers of those ports as to whether they would like to incorporate your changes, and for the petsc port, I would encourage you to file a bug report with a diff with these changes and explanations about why the changes need to be made. In the case of our metis and SuiteSparse ports, they have no maintainers. You can still file tickets with diffs and someone will review them and commit them eventually. If the tickets don't get addressed in a timely manner you can ping the macports-dev mailing list to remind us. None of the other ports you mentioned exist in MacPorts at this time. You would be welcome to contribute your ports to us by filing tickets in the issue tracker as usual. Note that for parmetis a port has already been submitted; you could see if that one is the same as yours, or if not, submit an updated version there: https://trac.macports.org/ticket/20844 From ryandesign at macports.org Wed Jul 18 17:10:21 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 18 Jul 2012 19:10:21 -0500 Subject: Problem with ECL (embeddable common lisp) 12.2.1 on Lion In-Reply-To: <5006C1F6.8@sift.info> References: <5005A287.9020305@sift.info> <5006C1F6.8@sift.info> Message-ID: <305654A2-C27C-4C48-A857-62AE2B26BFF0@macports.org> On Jul 18, 2012, at 09:02, Robert Goldman wrote: >> That'd be a legitimate port bug, yes. File a ticket against ecl; in the >> meantime if you rebuild it with "sudo port -n -f upgrade ecl" it should >> pick up the updated libffi. > > Actually, FWIW, that upgrade command did not fix ecl. > > My attempt to run it yielded > > > ---> Scanning binaries for linking errors: 100.0% > ---> No broken files found. So that should have fixed ecl so that it links with the current version of libffi. > and then > > ;;; Loading > "/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas" > LOAD: Could not load file > #P"/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas" > (Error: > "dlopen(/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas, > 10): Library not loaded: /opt/local/lib/libffi.5.dylib > Referenced from: > /Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas > Reason: image not found") I don't know what /Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas is, but that is what is referencing libffi, and that is what needs to be rebuilt now. > I have reported the issue on trac: > > https://trac.macports.org/ticket/35242 Thanks; the ecl port does need to have some dependencies added. From allbery.b at gmail.com Wed Jul 18 17:22:26 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Wed, 18 Jul 2012 20:22:26 -0400 Subject: Problem with ECL (embeddable common lisp) 12.2.1 on Lion In-Reply-To: <305654A2-C27C-4C48-A857-62AE2B26BFF0@macports.org> References: <5005A287.9020305@sift.info> <5006C1F6.8@sift.info> <305654A2-C27C-4C48-A857-62AE2B26BFF0@macports.org> Message-ID: On Wed, Jul 18, 2012 at 8:10 PM, Ryan Schmidt wrote: > > > "dlopen(/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas, > > 10): Library not loaded: /opt/local/lib/libffi.5.dylib > > Referenced from: > > > /Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas > > Reason: image not found") > > I don't know what > /Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas > is, but that is what is referencing libffi, and that is what needs to be > rebuilt now. > It's a Lisp fast-load image, which traditionally was a memory dump of the heap --- this is probably just the shared object version of that. In any case it is more like an executable than a data file, and is now invalid unless ECL provides some way to poke inside it (unlikely). It needs to be removed and regenerated, however ECL does that (I, hm. Have not done a lot of Lisp, ignoring elisp, since the [unrelated!] MIT Maclisp). -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From rpgoldman at sift.info Wed Jul 18 20:58:28 2012 From: rpgoldman at sift.info (Robert P. Goldman) Date: Wed, 18 Jul 2012 22:58:28 -0500 Subject: Problem with ECL (embeddable common lisp) 12.2.1 on Lion In-Reply-To: References: <5005A287.9020305@sift.info> <5006C1F6.8@sift.info> <305654A2-C27C-4C48-A857-62AE2B26BFF0@macports.org> Message-ID: <5BCDAAD2-4BCB-47C6-84AC-B9A6E9599CC7@sift.info> That fasl (fast load) file is not the problem. It is recompiled as part of the testing process, so if it still references the stale libffi, then the ECL compiler is still referencing it, despite the port upgrade. So the port upgrade is not sufficient to fix the problem. I don't know enough about the mechanics to understand why the command Brandon supplied did not trigger a rebuilding of the ECL compiler, but it didn't. Best, R Sent from my iPad On Jul 18, 2012, at 19:22, Brandon Allbery wrote: > On Wed, Jul 18, 2012 at 8:10 PM, Ryan Schmidt wrote: > > "dlopen(/Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas, > > 10): Library not loaded: /opt/local/lib/libffi.5.dylib > > Referenced from: > > /Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas > > Reason: image not found") > > I don't know what /Users/rpg/lisp/asdf/tmp/fasls/ecl-12.2.1-unknown-macosx-x86/test/file3.fas is, but that is what is referencing libffi, and that is what needs to be rebuilt now. > > It's a Lisp fast-load image, which traditionally was a memory dump of the heap --- this is probably just the shared object version of that. In any case it is more like an executable than a data file, and is now invalid unless ECL provides some way to poke inside it (unlikely). It needs to be removed and regenerated, however ECL does that (I, hm. Have not done a lot of Lisp, ignoring elisp, since the [unrelated!] MIT Maclisp). > > -- > brandon s allbery allbery.b at gmail.com > wandering unix systems administrator (available) (412) 475-9364 vm/sms > -------------- next part -------------- An HTML attachment was scrubbed... URL: From allbery.b at gmail.com Thu Jul 19 07:46:39 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Thu, 19 Jul 2012 10:46:39 -0400 Subject: Problem with ECL (embeddable common lisp) 12.2.1 on Lion In-Reply-To: <5BCDAAD2-4BCB-47C6-84AC-B9A6E9599CC7@sift.info> References: <5005A287.9020305@sift.info> <5006C1F6.8@sift.info> <305654A2-C27C-4C48-A857-62AE2B26BFF0@macports.org> <5BCDAAD2-4BCB-47C6-84AC-B9A6E9599CC7@sift.info> Message-ID: On Wed, Jul 18, 2012 at 11:58 PM, Robert P. Goldman wrote: > That fasl (fast load) file is not the problem. It is recompiled as part of > the testing process, so if it still references the stale libffi, then the > ECL compiler is still referencing it, despite the port upgrade. So the port > upgrade is not sufficient to fix the problem. I don't know enough about the > mechanics to understand why the command Brandon supplied did not trigger a > rebuilding of the ECL compiler, but it didn't. > Or it did but that wasn't enough. It occurs to me that, if it's generating FASLs as shared objects, it may have a hardcoded reference somewhere in the source code (a string, not a linker reference that would be updated automatically) and a patch would be needed to update that. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From rpgoldman at sift.info Thu Jul 19 08:14:43 2012 From: rpgoldman at sift.info (Robert Goldman) Date: Thu, 19 Jul 2012 10:14:43 -0500 Subject: Problem with ECL (embeddable common lisp) 12.2.1 on Lion In-Reply-To: References: <5005A287.9020305@sift.info> <5006C1F6.8@sift.info> <305654A2-C27C-4C48-A857-62AE2B26BFF0@macports.org> <5BCDAAD2-4BCB-47C6-84AC-B9A6E9599CC7@sift.info> Message-ID: <50082463.8000301@sift.info> On 7/19/12 Jul 19 -9:46 AM, Brandon Allbery wrote: > On Wed, Jul 18, 2012 at 11:58 PM, Robert P. Goldman > wrote: > > That fasl (fast load) file is not the problem. It is recompiled as > part of the testing process, so if it still references the stale > libffi, then the ECL compiler is still referencing it, despite the > port upgrade. So the port upgrade is not sufficient to fix the > problem. I don't know enough about the mechanics to understand why > the command Brandon supplied did not trigger a rebuilding of the ECL > compiler, but it didn't. > > > Or it did but that wasn't enough. It occurs to me that, if it's > generating FASLs as shared objects, it may have a hardcoded reference > somewhere in the source code (a string, not a linker reference that > would be updated automatically) and a patch would be needed to update that. My mistake. Here's the problem: previous failures mean that the test code did not run to completion. Because it didn't run to completion, the test code *DID NOT WIPE OUT ITS CACHE OF FASLs*. Hence it was loading stale fasls. This is a bug in the test-running code, which I will report to ASDF. At any rate, when I did rm -rf asdf/tmp/, the tests ran. Thanks for your help, R From sean.michael.farley at gmail.com Thu Jul 19 14:23:14 2012 From: sean.michael.farley at gmail.com (Sean Farley) Date: Thu, 19 Jul 2012 16:23:14 -0500 Subject: Build Petsc with Shared Libraries In-Reply-To: References: <0AD5E35D-E5B2-4AC5-AB3E-9F90D4D56C3A@gmail.com> <20120718100002.GS27027@towel.neverpanic.de> <20120718174208.GT27027@towel.neverpanic.de> Message-ID: > Sean, it's up to the maintainers of those ports as to whether they would like to incorporate your changes, and for the petsc port, I would encourage you to file a bug report with a diff with these changes and explanations about why the changes need to be made. That actually was my plan but most of the time when I interact with the MacPorts devs, I never hear back: https://trac.macports.org/ticket/33889 http://lists.macosforge.org/pipermail/macports-dev/2012-May/019203.html https://trac.macports.org/ticket/34831 https://trac.macports.org/ticket/34846 https://trac.macports.org/ticket/34933 As a new person to the MacPorts scene, I've found that it's mostly discouraging to try to submit patches for discussion. > In the case of our metis and SuiteSparse ports, they have no maintainers. You can still file tickets with diffs and someone will review them and commit them eventually. If the tickets don't get addressed in a timely manner you can ping the macports-dev mailing list to remind us. > > None of the other ports you mentioned exist in MacPorts at this time. You would be welcome to contribute your ports to us by filing tickets in the issue tracker as usual. Note that for parmetis a port has already been submitted; you could see if that one is the same as yours, or if not, submit an updated version there: > > https://trac.macports.org/ticket/20844 How is a three-year old ticket that never got reviewed suppose to encourage someone that the MacPorts devs will even bother to respond? I would love to one day submit all my patches for review but I just don't have a clear message from the MacPorts community that the patches would even be reviewed; much less, constructively reviewed. From sean.michael.farley at gmail.com Thu Jul 19 14:41:23 2012 From: sean.michael.farley at gmail.com (Sean Farley) Date: Thu, 19 Jul 2012 16:41:23 -0500 Subject: Build Petsc with Shared Libraries In-Reply-To: <77C92C8C-94FE-47A4-969D-027A62CE6D7A@macports.org> References: <0AD5E35D-E5B2-4AC5-AB3E-9F90D4D56C3A@gmail.com> <20120718100002.GS27027@towel.neverpanic.de> <20120718174208.GT27027@towel.neverpanic.de> <77C92C8C-94FE-47A4-969D-027A62CE6D7A@macports.org> Message-ID: > I see that you use many variants in your Portfile. As a rule of thumb most functionality should be enabled by default. Couldn?t most be enabled by default (possibly as a default_variant)? Sure; I have no preference either way. My only note is that the --download-* options shouldn't be used for PETSc since that could lead to conflicting symbols. > I like your mpi PortGroup [1]. I can see that could be helpful for other packages as well. Thanks :-) Yes, my goal with the MPI PortGroup was to unify the use of +gcc47, +mpi, etc. so that (hopefully) a portfile wouldn't need to specify any custom compiler variant (ala +gcc4X). I haven't decided on a nice way to specify that mpi is optional (similarly, how to specify fortran is optional). > Isn?t MPI support something that should be enabled by default for Petsc? It doesn't really matter one way or the other. If no MPI is specified to PETSc, then it will use its own internal MPI (via MPIUNI). > Is there any consensus within the MacPorts community on what should be the default MPI implementation used in ports that require MPI? Good question. Due to the latest few releases of OpenMPI not being valgrind clean, PETSc recommends mpich2 (well, that and the fact that the mpich guys are on the next floor to the petsc team). Following up with mpi, it should be noted that lam, lammpi, and mpich are all deprecated (and should be removed / replaced_by). From macports-users at work.wnsr.net Thu Jul 19 17:55:17 2012 From: macports-users at work.wnsr.net (Marc W.) Date: Thu, 19 Jul 2012 17:55:17 -0700 Subject: Gource: error upgrading port on Lion 10.7.4 Message-ID: I get an error trying to 'port upgrade gource' today: $ uname -v Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64 $ sudo port selfupdate ---> Updating MacPorts base sources using rsync MacPorts base version 2.1.1 installed, MacPorts base version 2.1.1 downloaded. ---> Updating the ports tree sudo port clean gource ---> MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated $ port outdated The following installed ports are outdated: gource 0.38_1 < 0.38_2 $ sudo port upgrade outdated ---> Computing dependencies for gource ---> Fetching archive for gource ---> Attempting to fetch gource-0.38_2.darwin_11.x86_64.tbz2 from http://packages.macports.org/gource ---> Fetching distfiles for gource ---> Verifying checksum(s) for gource ---> Extracting gource ---> Configuring gource ---> Building gource Error: org.macports.build for port gource returned: command execution failed Please see the log file for port gource for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gource/gource/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets That log file is here: https://dl.dropbox.com/u/1884454/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gource%2Cgource%2Cmain.log """" :info:build /usr/bin/llvm-g++-4.2 -DPACKAGE_NAME=\"Gource\" -DPACKAGE_TARNAME=\"gource\" -DPACKAGE_VERSION=\"0.38\" -DPACKAGE_STRING=\"Gource\ 0.38\" -DPACKAGE_BUGREPORT=\"acaudwell at gmail.com\" -DPACKAGE_URL=\"\" -DPACKAGE=\"gource\" -DVERSION=\"0.38\" -DHAVE_TIMEGM=1 -DHAVE_UNSETENV=1 -DHAVE_PTHREAD=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_OPENGL_GL_H=1 -DHAVE_OPENGL_GLU_H=1 -DHAVE_LIBPCRE=1 -DHAVE_BOOST=/\*\*/ -DHAVE_BOOST_SYSTEM=/\*\*/ -DHAVE_BOOST_FILESYSTEM=/\*\*/ -I. -DSDLAPP_RESOURCE_DIR=\"/opt/local/share/gource\" -I/opt/local/include -D_THREAD_SAFE -D_THREAD_SAFE -I/opt/local/include/SDL -D_GNU_SOURCE=1 -D_THREAD_SAFE -I/opt/local/include/freetype2 -I/opt/local/include -I/opt/local/include -pipe -O2 -arch x86_64 -D_THREAD_SAFE -D_THREAD_SAFE -I/opt/local/include/SDL -D_GNU_SOURCE=1 -D_THREAD_SAFE -I/opt/local/include/freetype2 -I/opt/local/include -MT src/logmill.o -MD -MP -MF $depbase.Tpo -c -o src/logmill.o src/logmill.cpp &&\ :info:build mv -f $depbase.Tpo $depbase.Po :info:build src/logmill.cpp: In member function ?RCommitLog* RLogMill::fetchLog(std::string&)?: :info:build src/logmill.cpp:179: error: expected type-specifier :info:build src/logmill.cpp:179: error: expected unqualified-id before ?::? token :info:build src/logmill.cpp:179: error: expected `)' before ?::? token :info:build src/logmill.cpp:179: error: expected `{' before ?::? token :info:build src/logmill.cpp:179: error: ?::filesystem_error? has not been declared :info:build src/logmill.cpp:179: error: expected `;' before ?)? token :info:build make: *** [src/logmill.o] Error 1 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gource/gource/work/gource-0.38' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gource/gource/work/gource-0.38" && /usr/bin/make -j8 -w all :info:build Exit code: 2 """" Any ideas? Thanks, -Marc From ryandesign at macports.org Fri Jul 20 07:51:58 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 20 Jul 2012 09:51:58 -0500 Subject: Gource: error upgrading port on Lion 10.7.4 In-Reply-To: References: Message-ID: <1BEF8058-B4DA-40A2-A9E6-C2CF21C516D1@macports.org> On Jul 19, 2012, at 19:55, Marc W. wrote: > I get an error trying to 'port upgrade gource' today: Looks like: https://trac.macports.org/ticket/35173 From ryandesign at macports.org Fri Jul 20 07:56:24 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 20 Jul 2012 09:56:24 -0500 Subject: git bash_completion does not work - solved (?) In-Reply-To: References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> Message-ID: On Jul 15, 2012, at 20:25, Brandon Allbery wrote: > On Sun, Jul 15, 2012 at 9:10 PM, Ryan Schmidt wrote: >> I was unable to figure out exactly what I was meant to be changing in Terminal's preferences to make this work. > > Presumably changing the command to run from your login shell to "/opt/local/bin/bash -l". I am still not sure what to change or how to verify it was successful. In Lion's Terminal.app, I have opened Preferences -> Settings -> Shell, checked the "Run command" box, and filled in "/opt/local/bin/bash -l". The "Run inside shell" checkbox is not checked. The bash port is installed. If I open a new terminal window and type "echo $SHELL" it still prints "/bin/bash". Is that a correct way to verify that these steps were not successful? What else should I be doing? From cal at macports.org Fri Jul 20 08:08:33 2012 From: cal at macports.org (Clemens Lang) Date: Fri, 20 Jul 2012 17:08:33 +0200 Subject: git bash_completion does not work - solved (?) In-Reply-To: References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> Message-ID: <20120720150833.GA2769@towel.neverpanic.de> On Fri, Jul 20, 2012 at 09:56:24AM -0500, Ryan Schmidt wrote: > I am still not sure what to change or how to verify it was successful. > In Lion's Terminal.app, I have opened Preferences -> Settings -> > Shell, checked the "Run command" box, and filled in > "/opt/local/bin/bash -l". The "Run inside shell" checkbox is not > checked. The bash port is installed. If I open a new terminal window > and type "echo $SHELL" it still prints "/bin/bash". Is that a correct > way to verify that these steps were not successful? What else should I > be doing? Try echo $BASH_VERSION. It should print something along the line of 4.2.something. If it doesn't you're not using MacPorts bash. -- Clemens Lang From allbery.b at gmail.com Fri Jul 20 08:15:22 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Fri, 20 Jul 2012 11:15:22 -0400 Subject: git bash_completion does not work - solved (?) In-Reply-To: References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> Message-ID: On Fri, Jul 20, 2012 at 10:56 AM, Ryan Schmidt wrote: > not checked. The bash port is installed. If I open a new terminal window > and type "echo $SHELL" it still prints "/bin/bash". Is that a correct way > to verify that these steps were not successful? What else should I be doing? > $SHELL is typically set by login, not by the shell itself. $BASH_VERSION should tell you what version you are running, and $0 may be useful as well. (You may want to set $SHELL in environment.plist.) -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From zen146410 at zen.co.uk Sat Jul 21 02:53:31 2012 From: zen146410 at zen.co.uk (Barrie Stott) Date: Sat, 21 Jul 2012 10:53:31 +0100 Subject: git bash_completion does not work - solved (?) In-Reply-To: <20120720150833.GA2769@towel.neverpanic.de> References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> <20120720150833.GA2769@towel.neverpanic.de> Message-ID: <140A29DD-C230-4660-94AA-D08963F454DC@zen.co.uk> On 20 Jul 2012, at 16:08, Clemens Lang wrote: > On Fri, Jul 20, 2012 at 09:56:24AM -0500, Ryan Schmidt wrote: >> I am still not sure what to change or how to verify it was successful. >> In Lion's Terminal.app, I have opened Preferences -> Settings -> >> Shell, checked the "Run command" box, and filled in >> "/opt/local/bin/bash -l". The "Run inside shell" checkbox is not >> checked. The bash port is installed. If I open a new terminal window >> and type "echo $SHELL" it still prints "/bin/bash". Is that a correct >> way to verify that these steps were not successful? What else should I >> be doing? > Try echo $BASH_VERSION. It should print something along the line of > 4.2.something. If it doesn't you're not using MacPorts bash. I upgraded my system this morning and I now have: bash @4.2.29_0+universal (active) bash-completion @2.0_1 (active) I ran the following: gbs:~ $ echo $BASH_VERSION 3.2.48(1)-release gbs:~ $ /bin/bash --version GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin10.0) gbs:~ $ which bash /opt/local/bin/bash gbs:~ $ bash --version GNU bash, version 4.2.29(2)-release (i386-apple-darwin10.8.0) The results disagree with what Clemens said. Typing 'port SPACE TAB' gives me a listing of the current directory whereas it should give a list of all possible port commands if bash-completion is working. How can I get $BASH_VERSION to give '4.2.29(2)-release'? Barrie. From ryandesign at macports.org Sat Jul 21 03:07:45 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 21 Jul 2012 05:07:45 -0500 Subject: git bash_completion does not work - solved (?) In-Reply-To: <140A29DD-C230-4660-94AA-D08963F454DC@zen.co.uk> References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> <20120720150833.GA2769@towel.neverpanic.de> <140A29DD-C230-4660-94AA-D08963F454DC@zen.co.uk> Message-ID: <13658FE2-1C04-49B9-9C73-041EC6DA2D3D@macports.org> On Jul 21, 2012, at 04:53, Barrie Stott wrote: > > On 20 Jul 2012, at 16:08, Clemens Lang wrote: > >> On Fri, Jul 20, 2012 at 09:56:24AM -0500, Ryan Schmidt wrote: >>> I am still not sure what to change or how to verify it was successful. >>> In Lion's Terminal.app, I have opened Preferences -> Settings -> >>> Shell, checked the "Run command" box, and filled in >>> "/opt/local/bin/bash -l". The "Run inside shell" checkbox is not >>> checked. The bash port is installed. If I open a new terminal window >>> and type "echo $SHELL" it still prints "/bin/bash". Is that a correct >>> way to verify that these steps were not successful? What else should I >>> be doing? > >> Try echo $BASH_VERSION. It should print something along the line of >> 4.2.something. If it doesn't you're not using MacPorts bash. > > I upgraded my system this morning and I now have: > bash @4.2.29_0+universal (active) > bash-completion @2.0_1 (active) > > I ran the following: > > gbs:~ $ echo $BASH_VERSION > 3.2.48(1)-release > gbs:~ $ /bin/bash --version > GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin10.0) > gbs:~ $ which bash > /opt/local/bin/bash > gbs:~ $ bash --version > GNU bash, version 4.2.29(2)-release (i386-apple-darwin10.8.0) > > The results disagree with what Clemens said. But have you actually followed the instructions from earlier in this thread about how to change your shell from /bin/bash to /opt/local/bin/bash? You need to do that first. From zen146410 at zen.co.uk Sat Jul 21 03:51:17 2012 From: zen146410 at zen.co.uk (Barrie Stott) Date: Sat, 21 Jul 2012 11:51:17 +0100 Subject: git bash_completion does not work - solved (?) In-Reply-To: <13658FE2-1C04-49B9-9C73-041EC6DA2D3D@macports.org> References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> <20120720150833.GA2769@towel.neverpanic.de> <140A29DD-C230-4660-94AA-D08963F454DC@zen.co.uk> <13658FE2-1C04-49B9-9C73-041EC6DA2D3D@macports.org> Message-ID: <9BEE0179-7967-4D6B-850F-69B4AB29F8C7@zen.co.uk> On 21 Jul 2012, at 11:07, Ryan Schmidt wrote: > > On Jul 21, 2012, at 04:53, Barrie Stott wrote: > >> >> On 20 Jul 2012, at 16:08, Clemens Lang wrote: >> >>> On Fri, Jul 20, 2012 at 09:56:24AM -0500, Ryan Schmidt wrote: >>>> I am still not sure what to change or how to verify it was successful. >>>> In Lion's Terminal.app, I have opened Preferences -> Settings -> >>>> Shell, checked the "Run command" box, and filled in >>>> "/opt/local/bin/bash -l". The "Run inside shell" checkbox is not >>>> checked. The bash port is installed. If I open a new terminal window >>>> and type "echo $SHELL" it still prints "/bin/bash". Is that a correct >>>> way to verify that these steps were not successful? What else should I >>>> be doing? >> >>> Try echo $BASH_VERSION. It should print something along the line of >>> 4.2.something. If it doesn't you're not using MacPorts bash. >> >> I upgraded my system this morning and I now have: >> bash @4.2.29_0+universal (active) >> bash-completion @2.0_1 (active) >> >> I ran the following: >> >> gbs:~ $ echo $BASH_VERSION >> 3.2.48(1)-release >> gbs:~ $ /bin/bash --version >> GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin10.0) >> gbs:~ $ which bash >> /opt/local/bin/bash >> gbs:~ $ bash --version >> GNU bash, version 4.2.29(2)-release (i386-apple-darwin10.8.0) >> >> The results disagree with what Clemens said. > > But have you actually followed the instructions from earlier in this thread about how to change your shell from /bin/bash to /opt/local/bin/bash? You need to do that first. I have now edited /etc/shells with MacVim to add /opt/local/bin/bash as the first in the list. I then ran 'chsh -s /opt/local/bin/bash'. I had already done what you suggested in Terminal's Preferences -> Settings -> Shell. I removed all terminals, opened a new one and typed 'echo $BASH_VERSION'. The result was the same as before: 3.2.48(1)-release. What have I missed? Barrie. From cal at macports.org Sat Jul 21 04:01:41 2012 From: cal at macports.org (Clemens Lang) Date: Sat, 21 Jul 2012 13:01:41 +0200 Subject: git bash_completion does not work - solved (?) In-Reply-To: <9BEE0179-7967-4D6B-850F-69B4AB29F8C7@zen.co.uk> References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> <20120720150833.GA2769@towel.neverpanic.de> <140A29DD-C230-4660-94AA-D08963F454DC@zen.co.uk> <13658FE2-1C04-49B9-9C73-041EC6DA2D3D@macports.org> <9BEE0179-7967-4D6B-850F-69B4AB29F8C7@zen.co.uk> Message-ID: <20120721110141.GC4424@towel.neverpanic.de> > I have now edited /etc/shells with MacVim to add /opt/local/bin/bash > as the first in the list. I then ran 'chsh -s /opt/local/bin/bash'. I have done this on my system, too, and it works fine for me. > I had already done what you suggested in Terminal's Preferences -> > Settings -> Shell. I removed all terminals, opened a new one and typed > 'echo $BASH_VERSION'. The result was the same as before: > 3.2.48(1)-release. What have I missed? Try resetting your Terminal preferences to the default. It should use /usr/bin/login then, which should start the shell you chose via chsh. -- Clemens Lang From zen146410 at zen.co.uk Sat Jul 21 04:51:04 2012 From: zen146410 at zen.co.uk (Barrie Stott) Date: Sat, 21 Jul 2012 12:51:04 +0100 Subject: git bash_completion does not work - solved (?) In-Reply-To: <20120721110141.GC4424@towel.neverpanic.de> References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> <20120720150833.GA2769@towel.neverpanic.de> <140A29DD-C230-4660-94AA-D08963F454DC@zen.co.uk> <13658FE2-1C04-49B9-9C73-041EC6DA2D3D@macports.org> <9BEE0179-7967-4D6B-850F-69B4AB29F8C7@zen.co.uk> <20120721110141.GC4424@towel.neverpanic.de> Message-ID: <70AED9E6-510E-4B4C-B3BD-70795434D3F6@zen.co.uk> On 21 Jul 2012, at 12:01, Clemens Lang wrote: >> I have now edited /etc/shells with MacVim to add /opt/local/bin/bash >> as the first in the list. I then ran 'chsh -s /opt/local/bin/bash'. > > I have done this on my system, too, and it works fine for me. > > >> I had already done what you suggested in Terminal's Preferences -> >> Settings -> Shell. I removed all terminals, opened a new one and typed >> 'echo $BASH_VERSION'. The result was the same as before: >> 3.2.48(1)-release. What have I missed? > > Try resetting your Terminal preferences to the default. It should use > /usr/bin/login then, which should start the shell you chose via chsh. Nearer in that there's more info and it half works. I ticked 'Run command' in Terminal's Preferences and entered /usr/bin/login. Deleted all terminals (does this need doing?) and opened a new one. Same as before for 'echo $BASH_VERSION'. Typed 'bash' to go down a level and, this time, 'echo $BASH_VERSION' gave the correct answer, 4.2.29(2)-release, and 'port SPACE TAB' gave a listing of all ports. I emptied Terminal's Preferences by unticking 'Run command', did everything else as in previous paragraph and got the same results as previous paragraph. I'm just hoping that this suggests to someone another thing to try. Barrie. From damon.mcdougall at gmail.com Sat Jul 21 05:19:00 2012 From: damon.mcdougall at gmail.com (Damon McDougall) Date: Sat, 21 Jul 2012 13:19:00 +0100 Subject: git bash_completion does not work - solved (?) In-Reply-To: <70AED9E6-510E-4B4C-B3BD-70795434D3F6@zen.co.uk> References: <20120715202613.GQ27027@towel.neverpanic.de> <20120720150833.GA2769@towel.neverpanic.de> <140A29DD-C230-4660-94AA-D08963F454DC@zen.co.uk> <13658FE2-1C04-49B9-9C73-041EC6DA2D3D@macports.org> <9BEE0179-7967-4D6B-850F-69B4AB29F8C7@zen.co.uk> <20120721110141.GC4424@towel.neverpanic.de> <70AED9E6-510E-4B4C-B3BD-70795434D3F6@zen.co.uk> Message-ID: <20120721121900.GA1526@quagmire.local> On Sat, Jul 21, 2012 at 12:51:04PM +0100, Barrie Stott wrote: > > On 21 Jul 2012, at 12:01, Clemens Lang wrote: > > >> I have now edited /etc/shells with MacVim to add /opt/local/bin/bash > >> as the first in the list. I then ran 'chsh -s /opt/local/bin/bash'. > > > > I have done this on my system, too, and it works fine for me. > > > > > >> I had already done what you suggested in Terminal's Preferences -> > >> Settings -> Shell. I removed all terminals, opened a new one and typed > >> 'echo $BASH_VERSION'. The result was the same as before: > >> 3.2.48(1)-release. What have I missed? > > > > Try resetting your Terminal preferences to the default. It should use > > /usr/bin/login then, which should start the shell you chose via chsh. > > Nearer in that there's more info and it half works. > > I ticked 'Run command' in Terminal's Preferences and entered /usr/bin/login. Deleted all terminals (does this need doing?) and opened a new one. Same as before for 'echo $BASH_VERSION'. Typed 'bash' to go down a level and, this time, 'echo $BASH_VERSION' gave the correct answer, 4.2.29(2)-release, and 'port SPACE TAB' gave a listing of all ports. > Unfortunately, I don't think this will persist on a Terminal.app restart. > > I emptied Terminal's Preferences by unticking 'Run command', did everything else as in previous paragraph and got the same results as previous paragraph. > > I'm just hoping that this suggests to someone another thing to try. > > Barrie. -- Damon McDougall http://damon-is-a-geek.com B2.39 Mathematics Institute University of Warwick Coventry West Midlands CV4 7AL United Kingdom From zen146410 at zen.co.uk Sat Jul 21 06:02:50 2012 From: zen146410 at zen.co.uk (Barrie Stott) Date: Sat, 21 Jul 2012 14:02:50 +0100 Subject: git bash_completion does not work - solved (?) In-Reply-To: <20120721121900.GA1526@quagmire.local> References: <20120715202613.GQ27027@towel.neverpanic.de> <20120720150833.GA2769@towel.neverpanic.de> <140A29DD-C230-4660-94AA-D08963F454DC@zen.co.uk> <13658FE2-1C04-49B9-9C73-041EC6DA2D3D@macports.org> <9BEE0179-7967-4D6B-850F-69B4AB29F8C7@zen.co.uk> <20120721110141.GC4424@towel.neverpanic.de> <70AED9E6-510E-4B4C-B3BD-70795434D3F6@zen.co.uk> <20120721121900.GA1526@quagmire.local> Message-ID: <8BEFFA1F-1476-4AC3-9313-44CB04A12B22@zen.co.uk> On 21 Jul 2012, at 13:19, Damon McDougall wrote: > On Sat, Jul 21, 2012 at 12:51:04PM +0100, Barrie Stott wrote: >> >> On 21 Jul 2012, at 12:01, Clemens Lang wrote: >> >>>> I have now edited /etc/shells with MacVim to add /opt/local/bin/bash >>>> as the first in the list. I then ran 'chsh -s /opt/local/bin/bash'. >>> >>> I have done this on my system, too, and it works fine for me. >>> >>> >>>> I had already done what you suggested in Terminal's Preferences -> >>>> Settings -> Shell. I removed all terminals, opened a new one and typed >>>> 'echo $BASH_VERSION'. The result was the same as before: >>>> 3.2.48(1)-release. What have I missed? >>> >>> Try resetting your Terminal preferences to the default. It should use >>> /usr/bin/login then, which should start the shell you chose via chsh. >> >> Nearer in that there's more info and it half works. >> >> I ticked 'Run command' in Terminal's Preferences and entered /usr/bin/login. Deleted all terminals (does this need doing?) and opened a new one. Same as before for 'echo $BASH_VERSION'. Typed 'bash' to go down a level and, this time, 'echo $BASH_VERSION' gave the correct answer, 4.2.29(2)-release, and 'port SPACE TAB' gave a listing of all ports. >> > > Unfortunately, I don't think this will persist on a Terminal.app > restart. No it doesn't. Barrie. From mparchet at sunrise.ch Sat Jul 21 06:21:48 2012 From: mparchet at sunrise.ch (Michael Parchet) Date: Sat, 21 Jul 2012 15:21:48 +0200 Subject: None example in macport/share/qt4 folder Message-ID: <500AACEC.1070204@sunrise.ch> Hello, I have installed the qt4-mac and qt4-creator-mac package but I can't find the doc and example in the macport(/opt/local)/share/qt4 folder. Why Qt4 and qt4-creator has not been installed ? A package isn't completed ? Tanks for your answer. Best regards mparchet From michaelld at macports.org Sat Jul 21 06:30:15 2012 From: michaelld at macports.org (Michael Dickens) Date: Sat, 21 Jul 2012 09:30:15 -0400 Subject: None example in macport/share/qt4 folder In-Reply-To: <99D0DFAD-5176-4AA1-A685-011F4E4B94DE@alum.mit.edu> References: <500AACEC.1070204@sunrise.ch> <99D0DFAD-5176-4AA1-A685-011F4E4B94DE@alum.mit.edu> Message-ID: <237A0AB3-6962-4415-8DEA-3ABC47DE1E0F@mailworks.org> Hi Michael - Well, qt4-mac's doc and examples are in, respectively: ${prefix}/share/doc/qt4 and ${prefix}/share/qt4/examples I don't know about qt4-creator-mac's; why not view the installed files for this port and see what's in ${prefix}/share/... ? - MLD On Jul 21, 2012, at 9:21 AM, Michael Parchet wrote: I have installed the qt4-mac and qt4-creator-mac package but I can't find the doc and example in the macport(/opt/local)/share/qt4 folder. Why Qt4 and qt4-creator has not been installed ? A package isn't completed ? Tanks for your answer. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Sat Jul 21 06:30:29 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 21 Jul 2012 08:30:29 -0500 Subject: None example in macport/share/qt4 folder In-Reply-To: <500AACEC.1070204@sunrise.ch> References: <500AACEC.1070204@sunrise.ch> Message-ID: Please pick just one mailing list to send your question to. Since you're not asking about how to write a Portfile or about modifying MacPorts base code, let's make it the Users list. Please remove the Dev list from any replies. On Jul 21, 2012, at 08:21, Michael Parchet wrote: > I have installed the qt4-mac and qt4-creator-mac package but I can't find the doc and example in the macport(/opt/local)/share/qt4 folder. > > Why > > Qt4 and qt4-creator has not been installed ? > > A package isn't completed ? Exactly what files are you expecting to see? Perhaps the maintainer of whatever package usually provides those files simply hasn't instructed MacPorts to install them. Or perhaps they're installed in a location you didn't expect. From zen146410 at zen.co.uk Sat Jul 21 06:57:36 2012 From: zen146410 at zen.co.uk (Barrie Stott) Date: Sat, 21 Jul 2012 14:57:36 +0100 Subject: git bash_completion does not work - solved (?) In-Reply-To: <13658FE2-1C04-49B9-9C73-041EC6DA2D3D@macports.org> References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> <20120720150833.GA2769@towel.neverpanic.de> <140A29DD-C230-4660-94AA-D08963F454DC@zen.co.uk> <13658FE2-1C04-49B9-9C73-041EC6DA2D3D@macports.org> Message-ID: On 21 Jul 2012, at 11:07, Ryan Schmidt wrote: > > On Jul 21, 2012, at 04:53, Barrie Stott wrote: > >> >> On 20 Jul 2012, at 16:08, Clemens Lang wrote: >> >>> On Fri, Jul 20, 2012 at 09:56:24AM -0500, Ryan Schmidt wrote: >>>> I am still not sure what to change or how to verify it was successful. >>>> In Lion's Terminal.app, I have opened Preferences -> Settings -> >>>> Shell, checked the "Run command" box, and filled in >>>> "/opt/local/bin/bash -l". The "Run inside shell" checkbox is not >>>> checked. The bash port is installed. If I open a new terminal window >>>> and type "echo $SHELL" it still prints "/bin/bash". Is that a correct >>>> way to verify that these steps were not successful? What else should I >>>> be doing? >> >>> Try echo $BASH_VERSION. It should print something along the line of >>> 4.2.something. If it doesn't you're not using MacPorts bash. >> >> I upgraded my system this morning and I now have: >> bash @4.2.29_0+universal (active) >> bash-completion @2.0_1 (active) >> >> I ran the following: >> >> gbs:~ $ echo $BASH_VERSION >> 3.2.48(1)-release >> gbs:~ $ /bin/bash --version >> GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin10.0) >> gbs:~ $ which bash >> /opt/local/bin/bash >> gbs:~ $ bash --version >> GNU bash, version 4.2.29(2)-release (i386-apple-darwin10.8.0) >> >> The results disagree with what Clemens said. > > But have you actually followed the instructions from earlier in this thread about how to change your shell from /bin/bash to /opt/local/bin/bash? You need to do that first. > Thank you for this and your Terminal Preferences change. Everything would have been fine using them and what Stephan said: add /opt/local/bin/bash to /etc/shells and obey "chsh -s /opt/local/bin/bash" Unfortunately, I thought that merely removing Terminal windows, rather than typing cmd-q, was sufficient to start with a clean Terminal state. Once I used cmd-q everything was fine. I'm grateful for all the help given. Barrie From phildobbin at gmail.com Sat Jul 21 07:38:15 2012 From: phildobbin at gmail.com (Phil Dobbin) Date: Sat, 21 Jul 2012 15:38:15 +0100 Subject: git bash_completion does not work - solved (?) In-Reply-To: References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> <20120720150833.GA2769@towel.neverpanic.de> <140A29DD-C230-4660-94AA-D08963F454DC@zen.co.uk> <13658FE2-1C04-49B9-9C73-041EC6DA2D3D@macports.org> Message-ID: <500ABED7.90404@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Barrie Stott wrote: > On 21 Jul 2012, at 11:07, Ryan Schmidt wrote: > >> On Jul 21, 2012, at 04:53, Barrie Stott wrote: >> >>> On 20 Jul 2012, at 16:08, Clemens Lang wrote: [snip] > Thank you for this and your Terminal Preferences change. Everything would have been fine using them and what Stephan said: > > add /opt/local/bin/bash to /etc/shells and > obey "chsh -s /opt/local/bin/bash" > > Unfortunately, I thought that merely removing Terminal windows, rather than typing cmd-q, was sufficient to start with a clean Terminal state. Once I used cmd-q everything was fine. I'm grateful for all the help given. Thanks also from me. I've been silently following this thread trying to work out why alt-backspace doesn't work as expected thinking I was using /opt/local/bin/bash -v4 Now it does. Cheers, Phil... - -- But masters, remember that I am an ass. Though it be not written down, yet forget not that I am an ass. Wm. Shakespeare - Much Ado About Nothing -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: ??auto-key-locate cert pka ldap hkp://keys.gnupg.net Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQCr7XAAoJEKuJdOaOnmMJfIwH/RmtmCwvG423U15ROkfNVn4V n02EWBC3YJVVa3aY0xyRtscIUb490pW8hZrhz31y0rq5MQ+VlXImXF/9zx4LbbZS cBtvRjzLP+6LWqjA6UNCGcWiM7tsTFW9YWAhYnkG9NIBGi++d1D00pJSZiQFzVbn 99naynFjqHCiQebdjYgifDpgdqtZFgCZW7BNr6Ykkt8wY7aUI70FYRKDk76R5EcL Fc3uE9F9qDuU6f5GtVrssoxHdW+r0WtgoCgZ9KvytwthMs1b8G2zbQKv2mYKEWAB VTtGNGxMZkzo7NWCDzs6ewXAyI+fenA0kB3pX9wov/AI5p0fNETCUrIom2th3Co= =8tbD -----END PGP SIGNATURE----- From mparchet at sunrise.ch Sat Jul 21 10:24:58 2012 From: mparchet at sunrise.ch (Michael Parchet) Date: Sat, 21 Jul 2012 19:24:58 +0200 Subject: None example in macport/share/qt4 folder In-Reply-To: References: <500AACEC.1070204@sunrise.ch> Message-ID: <500AE5EA.7070902@sunrise.ch> Le 21.07.12 15:30, Ryan Schmidt a ?crit : > Please pick just one mailing list to send your question to. Since you're not asking about how to write a Portfile or about modifying MacPorts base code, let's make it the Users list. Please remove the Dev list from any replies. > > On Jul 21, 2012, at 08:21, Michael Parchet wrote: > >> I have installed the qt4-mac and qt4-creator-mac package but I can't find the doc and example in the macport(/opt/local)/share/qt4 folder. >> >> Why >> >> Qt4 and qt4-creator has not been installed ? >> >> A package isn't completed ? > Exactly what files are you expecting to see? Perhaps the maintainer of whatever package usually provides those files simply hasn't instructed MacPorts to install them. Or perhaps they're installed in a location you didn't expect. > > Hello, I wold like to see the examples and the demos files There is respectively throw xml files "examples-manifest" and "demo-manifest" with contain the examples and he demos urls. But it seem that the macort qt-creator version not use this files to find the examples and demos. Otherwise, it seems that. qt-make which is inthe macport/bin folder isen't setup by default for the qt4-creator macort version. Can you help me please ? Best regards mparchet -------------- next part -------------- An HTML attachment was scrubbed... URL: From timski.sansom at gmail.com Sat Jul 21 12:41:56 2012 From: timski.sansom at gmail.com (Tim Sansom) Date: Sat, 21 Jul 2012 20:41:56 +0100 Subject: wine fails to load Message-ID: <081AF258-660B-4343-B19E-3EDD0524E032@gmail.com> hi there guys first of all i know this is possibly nothing you guys may be able to help me with, but if you don't ask you dont get as my mother used to say lol, right then i am trying to install a win 32 called cisco packet tracer app using wine i have managed to install xcode and macports and installed wine fantastic this is what i have done so far.. configuered mac ports echo export PATH=/opt/local/bin:/opt/local/sbin:\$PATH$'\n'export MANPATH=/opt/local/man:\$MANPATH | sudo tee -a /etc/profile export PATH=/opt/local/bin:/opt/local/sbin:$PATH export MANPATH=/opt/local/man:$MANPATH checked 64 bit if [ `sysctl -n hw.cpu64bit_capable` -eq 1 ] ; then echo "+universal" | sudo tee -a /opt/local/etc/macports/variants.conf; else echo "not 64bit capable"; fi then ran this to install wine sudo port install wine once i had completed that i decided to create a folder on my desktop and named it CISCO, then copied the 32 bit .exe in to the folder once that was done, through terminal i went to the folder cd Desktop/cisco and i can see my file PacketTracer533_setup_no_tutorials.exe so from there i ran the follwing command to install the application wine PacketTracer533_setup_no_tutorials.exe this took a few moments and the wine window started and the installer launched and i saved it to c:/Program Program Files/Cisco (default location) when i came to run this application i ran this cd ~/.wine/drive_c/Program\ Files/ an then tried to run it with wine Cisco Packet Tracer 5.3.3 then i was confronted with this error Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! wine: cannot find L"C:\\windows\\system32\\Cisco.exe" i did look on thier site on the dbus error and when i ran this launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist i was returned with "Nothing Found" if anybody can help with with this i would appriciate it as i have treid to reinstall this a few times now can can not :-( worst still i can not remove the said application now cheers for any advice :-) From allbery.b at gmail.com Sat Jul 21 12:51:11 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Sat, 21 Jul 2012 15:51:11 -0400 Subject: wine fails to load In-Reply-To: <081AF258-660B-4343-B19E-3EDD0524E032@gmail.com> References: <081AF258-660B-4343-B19E-3EDD0524E032@gmail.com> Message-ID: On Sat, Jul 21, 2012 at 3:41 PM, Tim Sansom wrote: > Dynamic session lookup supported but failed: launchd did not provide a > socket path, verify that org.freedesktop.dbus-session.plist is loaded! > sudo port install dbus; launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist I do wonder what you did that requires dbus but didn't install it; I see no dependency for it in the wine port. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From raramayo at gmail.com Sat Jul 21 13:57:07 2012 From: raramayo at gmail.com (Rodolfo Aramayo) Date: Sat, 21 Jul 2012 15:57:07 -0500 Subject: git bash_completion does not work - solved (?) Message-ID: Hi, I have taken the freedom of summarizing the "proper" way of configuring Bash as per this discussion ################################################################## Proper setting of BASH: $ port install bash Testing current configuration: $ which bash /opt/local/bin/bash $ bash --version GNU bash, version 4.2.29(2)-release (i386-apple-darwin10.8.0) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. $ echo $SHELL /bin/bash $ echo $BASH /bin/bash $Test the settings for your account as present in the dscl database: dscl . -read /Users/yourusername | grep ?UserShell:? UserShell: /bin/bash Configuring BASH: 1. Use your favorite text processor sudo emacs /etc/shells add: /opt/local/bin/bash as first on the list save 2. Run: chsh -u your_username -s /opt/local/bin/bash Testing Proper Configuration: $ which bash /opt/local/bin/bash $ bash --version GNU bash, version 4.2.29(2)-release (i386-apple-darwin10.8.0) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. $ echo $BASH /opt/local/bin/bash $ echo $SHELL /opt/local/bin/bash $Test the settings for your account as present in the dscl database: dscl . -read /Users/yourusername | grep ?UserShell:? /opt/local/bin/bash ################################################################## I found that there is no need to: Go to Terminal>Preferences>Startup>Command (complete path): Add to the top of the list: /opt/local/bin/bash -l These settings can be left default (I am running MacOSX10.6.8) Now my question to all of you is: Does one need to do this for the ?root? account as well? Thanks --R From raimue at macports.org Sat Jul 21 14:21:52 2012 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sat, 21 Jul 2012 23:21:52 +0200 Subject: git bash_completion does not work - solved (?) In-Reply-To: References: <75BFF5FE24C4490AB2114B6B1F015296@me.com> <20120715202613.GQ27027@towel.neverpanic.de> Message-ID: <500B1D70.6020807@macports.org> On 2012-07-16 03:10, Ryan Schmidt wrote: > On Jul 15, 2012, at 15:26, Clemens Lang wrote: > >> On Sun, Jul 15, 2012 at 10:13:13PM +0200, Stefan Scheidt wrote: >>> Question: Is this the right way to use MacPorts bash as login shell? >> >> Although `port notes bash-completion` suggests changing your terminal >> emulator's preferences, this is a perfectly fine way to do it, too (and >> it also is what I've been using for a couple of months now). > > I was unable to figure out exactly what I was meant to be changing in Terminal's preferences to make this work. Some more detailed instructions are in the howto section of the wiki: http://trac.macports.org/wiki/howto/bash-completion#Step3:UsebashfromMacPortsinyourterminal Rainer From raimue at macports.org Sat Jul 21 14:29:23 2012 From: raimue at macports.org (=?UTF-8?B?UmFpbmVyIE3DvGxsZXI=?=) Date: Sat, 21 Jul 2012 23:29:23 +0200 Subject: git bash_completion does not work - solved (?) In-Reply-To: References: Message-ID: <500B1F33.5090906@macports.org> Hello, On 2012-07-21 22:57, Rodolfo Aramayo wrote: > I have taken the freedom of summarizing the "proper" way of > configuring Bash as per this discussion You are right that there are two possibilities of adjusting your environment to use /opt/local/bin/bash in your terminal instead of the bash version shipped with Mac OS X: a) change the login shell b) change the preferences of your terminal emulator Note that changing the login shell is more invasive as it requires changing system files. Also, in case bash from MacPorts ever becomes unusable, it's easier to recover if you still have a working login shell (recovery is possible in either case). Thus, I recommend to switch to bash by editing the preferences of your terminal emulator, which can easily be reverted by choosing "Login shell" again. Detailed instructions on the configuration of Terminal.app/iTerm2.app are in the wiki in the howto section: http://trac.macports.org/wiki/howto/bash-completion#Step3:UsebashfromMacPortsinyourterminal Rainer From allbery.b at gmail.com Sat Jul 21 14:33:55 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Sat, 21 Jul 2012 17:33:55 -0400 Subject: git bash_completion does not work - solved (?) In-Reply-To: <500B1F33.5090906@macports.org> References: <500B1F33.5090906@macports.org> Message-ID: On Sat, Jul 21, 2012 at 5:29 PM, Rainer M?ller wrote: > Note that changing the login shell is more invasive as it requires changing > system files. Also, in case bash from MacPorts ever becomes unusable, it's > easier to recover if you still have a working login shell (recovery is > possible > in either case). Thus, I recommend to switch to bash by editing the > preferences > I suggested that earlier and got yelled at for being too negative.... -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwa at macports.org Sun Jul 22 00:35:17 2012 From: jwa at macports.org (Wahlstedt Jyrki) Date: Sun, 22 Jul 2012 10:35:17 +0300 Subject: wine fails to load In-Reply-To: <081AF258-660B-4343-B19E-3EDD0524E032@gmail.com> References: <081AF258-660B-4343-B19E-3EDD0524E032@gmail.com> Message-ID: <28824B34-520B-4F2D-ADC9-B4799C644597@macports.org> On 21.7.2012, at 22.41, Tim Sansom wrote: > > cd ~/.wine/drive_c/Program\ Files/ > an then tried to run it with > wine Cisco Packet Tracer 5.3.3 > then i was confronted with this error > Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! > wine: cannot find L"C:\\windows\\system32\\Cisco.exe" Could this be the key to the problem instead of the dbus? Cisco Packet Tracer is the program name, so it should be in quotes, like "Cisco Packet Tracer" or Cisco\ Packet\ Tracer in order for Windows to show what to look for!? If it's not that, then you should find the proper program name? > i did look on thier site on the dbus error and when i ran this > launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist > ! ! Jyrki Wahlstedt ! http://www.wahlstedt.fi/jyrki/ ! ! Our life is no dream; but it ought to become one and perhaps will. ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386 From ryandesign at macports.org Sun Jul 22 01:13:49 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 22 Jul 2012 03:13:49 -0500 Subject: None example in macport/share/qt4 folder In-Reply-To: <500AE5EA.7070902@sunrise.ch> References: <500AACEC.1070204@sunrise.ch> <500AE5EA.7070902@sunrise.ch> Message-ID: <13968085-85DD-4949-AEE6-26CDC529F555@macports.org> I'm not sure how well I'm able to help you. I'm not terribly familiar with Qt; I just have it installed because some of the other ports I use require it. On Jul 21, 2012, at 12:24, Michael Parchet wrote: > Le 21.07.12 15:30, Ryan Schmidt a ?crit : >> On Jul 21, 2012, at 08:21, Michael Parchet wrote: >> >>> I have installed the qt4-mac and qt4-creator-mac package but I can't find the doc and example in the macport(/opt/local)/share/qt4 folder. >>> >>> Why >>> >>> Qt4 and qt4-creator has not been installed ? >>> >>> A package isn't completed ? >> Exactly what files are you expecting to see? Perhaps the maintainer of whatever package usually provides those files simply hasn't instructed MacPorts to install them. Or perhaps they're installed in a location you didn't expect. >> >> Hello, > > I wold like to see the examples and the demos files Try opening these HTML pages in a browser; they seem to describe all the available included examples and demos: file:///opt/local/share/doc/qt4/html/all-examples.html file:///opt/local/share/doc/qt4/html/demos.html > There is respectively throw xml files "examples-manifest" and "demo-manifest" with contain the examples and he demos urls. I do see those two xml files, but I'm not familiar with these "manifest" files or what uses them. I do see some URLs in them, like: I don't know what application is meant to process these "qthelp" URLs. > But it seem that the macort qt-creator version not use this files to find the examples and demos. Otherwise, it seems that. qt-make which is in the macport/bin folder isen't setup by default for the qt4-creator macort version. I've never used Qt Creator and I haven't used qmake directly (just indirectly, by installing some other ports). So I'm not clear on how or if they're supposed to know about each other or how they're supposed to behave. I think your best bet may be to consult the normal Qt documentation, since it sounds like your questions may be more about Qt and less about MacPorts. If you can't find documentation on a particular Qt topic, ask in a Qt support venue. If something documented by the Qt people doesn't seem to work that way in the MacPorts version, then that would be a time to report the issue to us so that we can fix our Qt installation to match the Qt documentation. From ryandesign at macports.org Sun Jul 22 01:21:36 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 22 Jul 2012 03:21:36 -0500 Subject: wine fails to load In-Reply-To: <081AF258-660B-4343-B19E-3EDD0524E032@gmail.com> References: <081AF258-660B-4343-B19E-3EDD0524E032@gmail.com> Message-ID: <35D7ED99-2102-4EFB-9189-09F0AE38ED24@macports.org> On Jul 21, 2012, at 14:41, Tim Sansom wrote: > configuered mac ports > echo export PATH=/opt/local/bin:/opt/local/sbin:\$PATH$'\n'export MANPATH=/opt/local/man:\$MANPATH | sudo tee -a /etc/profile > export PATH=/opt/local/bin:/opt/local/sbin:$PATH > export MANPATH=/opt/local/man:$MANPATH > checked 64 bit > if [ `sysctl -n hw.cpu64bit_capable` -eq 1 ] ; then echo "+universal" | sudo tee -a /opt/local/etc/macports/variants.conf; else echo "not 64bit capable"; fi I'm sure this worked fine. However, I think you're following some years-outdated instructions. MacPorts sets up $PATH for you when you install it, so you probably don't need to change it manually. There's no need to add the MacPorts manpath to $MANPATH, unless you had set MANPATH to a nonstandard value before. There's no need to add +universal to variants.conf on 64-bit systems; MacPorts knows to build ports 64-bit when needed. From 200309 at calcentral.com Sun Jul 22 09:41:18 2012 From: 200309 at calcentral.com (Bee) Date: Sun, 22 Jul 2012 09:41:18 -0700 Subject: change log for a port Message-ID: <6AB33CAF-4C1A-4F52-9138-4328B7879569@calcentral.com> Is there a change log for a port? If yes, where? Specifically vim went from revision 0 to revision 1, what changed? vim @7.3.584, Revision 1 (editors) From cal at macports.org Sun Jul 22 09:48:45 2012 From: cal at macports.org (Clemens Lang) Date: Sun, 22 Jul 2012 18:48:45 +0200 Subject: change log for a port In-Reply-To: <6AB33CAF-4C1A-4F52-9138-4328B7879569@calcentral.com> References: <6AB33CAF-4C1A-4F52-9138-4328B7879569@calcentral.com> Message-ID: <20120722164845.GD4424@towel.neverpanic.de> On Sun, Jul 22, 2012 at 09:41:18AM -0700, Bee wrote: > Is there a change log for a port? > If yes, where? There's no changelog, but you can take a look at the version control history of the Portfile. There's a tool that does this for you in contrib/: http://trac.macports.org/browser/contrib/port-whatsnew > Specifically vim went from revision 0 to revision 1, what changed? See http://trac.macports.org/log/trunk/dports/editors/vim, in your case http://trac.macports.org/changeset/95784 -- Clemens Lang From 200309 at calcentral.com Sun Jul 22 10:15:52 2012 From: 200309 at calcentral.com (Bee) Date: Sun, 22 Jul 2012 10:15:52 -0700 Subject: change log for a port In-Reply-To: <20120722164845.GD4424@towel.neverpanic.de> References: <6AB33CAF-4C1A-4F52-9138-4328B7879569@calcentral.com> <20120722164845.GD4424@towel.neverpanic.de> Message-ID: <38848337-46D9-4EAE-9E54-A46B1A6D8F9F@calcentral.com> On Jul 22, 2012, at 9:48 AM, Clemens Lang wrote: > On Sun, Jul 22, 2012 at 09:41:18AM -0700, Bee wrote: >> Is there a change log for a port? >> If yes, where? > > There's no changelog, but you can take a look at the version control > history of the Portfile. > > There's a tool that does this for you in contrib/: > http://trac.macports.org/browser/contrib/port-whatsnew > >> Specifically vim went from revision 0 to revision 1, what changed? > > See > http://trac.macports.org/log/trunk/dports/editors/vim, That is exactly what I was looking for. I know about the vim updates but not the macport 'revisions'. Thank you Bill From surtin at gmail.com Mon Jul 23 09:50:31 2012 From: surtin at gmail.com (Christopher Snelling) Date: Mon, 23 Jul 2012 11:50:31 -0500 Subject: slrnface and macports Message-ID: Basically I'm just wondering if getting slrnface to compile is possible with macports. I see that compface is in the packages list and I even installed it, however, since there is only a Makefile for the slrnface package and no configure file or anything, I just attempted to edit the Makefile. This *kind* of worked in that I was able to get compface from macports recognized, it seems to be crapping out when trying to find the Xt library. Now I'm no expert or anything, but I do know that libXt is comfortably located /usr/X11R6/lib. I guess I'm just looking to see if anyone has slrnface working with any terminals for OS X Lion. If not, no big deal, at least I've finally got slrn working on Lion because of macports--and that in itself is pretty awesome. Anyway, hope I made sense and I hope someone can maybe point me in the right direction. From cal at macports.org Mon Jul 23 09:54:59 2012 From: cal at macports.org (Clemens Lang) Date: Mon, 23 Jul 2012 18:54:59 +0200 Subject: slrnface and macports In-Reply-To: References: Message-ID: <20120723165459.GG4424@towel.neverpanic.de> On Mon, Jul 23, 2012 at 11:50:31AM -0500, Christopher Snelling wrote: > Basically I'm just wondering if getting slrnface to compile is > possible with macports. I see that compface is in the packages list > and I even installed it, however, since there is only a Makefile for > the slrnface package and no configure file or anything, I just > attempted to edit the Makefile. Are you trying to write a Portfile for it or do you only want to compile it against stuff in MacPorts? If you're trying to write a Portfile, there already are several ports that build software without a configure script. You might find some examples by grepping for "use_configure no". If you're only trying to build it, appending CFLAGS="-I/opt/local/include" LDFLAGS="-L/opt/local/lib" is usually enough to build it against MacPorts. > This *kind* of worked in that I was able to get compface from macports > recognized, it seems to be crapping out when trying to find the Xt > library. Now I'm no expert or anything, but I do know that libXt is > comfortably located /usr/X11R6/lib. I guess I'm just looking to see if > anyone has slrnface working with any terminals for OS X Lion. If not, no > big deal, at least I've finally got slrn working on Lion because of > macports--and that in itself is pretty awesome. You can install the xorg-libXt port to get this. -- Clemens Lang From surtin at gmail.com Mon Jul 23 10:04:59 2012 From: surtin at gmail.com (Christopher Snelling) Date: Mon, 23 Jul 2012 12:04:59 -0500 Subject: slrnface and macports In-Reply-To: <20120723165459.GG4424@towel.neverpanic.de> References: <20120723165459.GG4424@towel.neverpanic.de> Message-ID: <7A81133C-7E70-4D95-8AE9-484D6950FD5D@gmail.com> On Jul 23, 2012, at 11:54 AM, Clemens Lang wrote: > On Mon, Jul 23, 2012 at 11:50:31AM -0500, Christopher Snelling wrote: >> Basically I'm just wondering if getting slrnface to compile is >> possible with macports. I see that compface is in the packages list >> and I even installed it, however, since there is only a Makefile for >> the slrnface package and no configure file or anything, I just >> attempted to edit the Makefile. > > Are you trying to write a Portfile for it or do you only want to compile > it against stuff in MacPorts? I was going to attempt to make a portfile for it once I was able to get it working. > > If you're trying to write a Portfile, there already are several ports > that build software without a configure script. You might find some > examples by grepping for "use_configure no". Thanks for the info, I'll look into it. > > If you're only trying to build it, appending > CFLAGS="-I/opt/local/include" LDFLAGS="-L/opt/local/lib" is usually > enough to build it against MacPorts. > >> This *kind* of worked in that I was able to get compface from macports >> recognized, it seems to be crapping out when trying to find the Xt >> library. Now I'm no expert or anything, but I do know that libXt is >> comfortably located /usr/X11R6/lib. I guess I'm just looking to see if >> anyone has slrnface working with any terminals for OS X Lion. If not, no >> big deal, at least I've finally got slrn working on Lion because of >> macports--and that in itself is pretty awesome. > > You can install the xorg-libXt port to get this. Okay great, I'll see if trying with this package will work. Thanks for your help. From vince at macports.org Tue Jul 24 05:00:19 2012 From: vince at macports.org (Vincent Habchi) Date: Tue, 24 Jul 2012 14:00:19 +0200 Subject: New port: eero-devel Message-ID: <60192AB1-9611-48AF-BF66-775C1F79F601@macports.org> Hi there, I have committed in r95835 the Portfile for a language under development, Eero (http://eerolanguage.org). This is a modernized 100 % binary compatible version of Obj-C with Python-like syntax (e.g. bloc indenting instead of {}) replacing the plain old C syntax. Eero provides also many friendly features Obj-C is still lacking like, for instance, namespaces. The Eero language is experimental. It is based on SVN versions of both llvm and clang. The ld64 v.128 that current cctools port provides cannot link eero binaries. This should be fixed with Mountain Lion release in a few days. Have fun! Vincent From jwa at macports.org Tue Jul 24 07:31:53 2012 From: jwa at macports.org (Wahlstedt Jyrki) Date: Tue, 24 Jul 2012 17:31:53 +0300 Subject: New port: eero-devel In-Reply-To: <60192AB1-9611-48AF-BF66-775C1F79F601@macports.org> References: <60192AB1-9611-48AF-BF66-775C1F79F601@macports.org> Message-ID: <8E9983A0-A5F8-4798-8D56-1ED399242C6D@macports.org> On 24.7.2012, at 15.00, Vincent Habchi wrote: > Hi there, > > I have committed in r95835 the Portfile for a language under development, Eero (http://eerolanguage.org). This is a modernized 100 % binary compatible version of Obj-C with Python-like syntax (e.g. bloc indenting instead of {}) replacing the plain old C syntax. Eero provides also many friendly features Obj-C is still lacking like, for instance, namespaces. > > The Eero language is experimental. It is based on SVN versions of both llvm and clang. The ld64 v.128 that current cctools port provides cannot link eero binaries. This should be fixed with Mountain Lion release in a few days. > > Have fun! > Vincent Thanks, especially as I, being a Finn, appreciate a programming language, the name of which is a Finnish given name (this one here inspired by an architect, the works of whom I love as well)! ! ! Jyrki Wahlstedt ! http://www.wahlstedt.fi/jyrki/ ! ! Our life is no dream; but it ought to become one and perhaps will. ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386 From bluestarla_ at hotmail.com Wed Jul 25 01:22:49 2012 From: bluestarla_ at hotmail.com (Sara Buson) Date: Wed, 25 Jul 2012 10:22:49 +0200 Subject: Texlive: kile do not find koma-script files Message-ID: Hi Everyone, I must advise that I am quite a new user of MecPorts and not expert! I recently installed TexLive2011. I then installed the kile editor compiling it by source and everything went fine. Despite this some days ago I run into issues with kile. It wasn't able to find any of the koma-script files. But those files were present as I see them in /usr/local/texlive/2012/texmf-dist/tex/latex/koma-script/ . Since I couldn't find any solution I decided to update from TexLive2011 to TexLive2012. I followed the simple instruction indicated here: http://tug.org/mactex/ . Installation successful but the .profile file was not updated, it still pointed to the old version of TexLive2011. The same for all the binaries in /opt/local/bin/ . I also removed the 2011 version but still they use the old version. I changed manually the .profile putting the path to the 2012 version. Now other editors that I have installed that using TexLive are working with the correct version (e.g. TexShop). Despite this kile still doesn't work properly.. I guess it might have its own configuration files somewhere but I cannot find them. More, isn't there a way to make it update to a new version of TexLive when available? I already lost several days on this problem, any suggestion would be very welcome. Thanks in advance, Starla -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at macports.org Wed Jul 25 07:39:32 2012 From: ram at macports.org (Adam Mercer) Date: Wed, 25 Jul 2012 09:39:32 -0500 Subject: LaTeX documents failing to build, unable to load file loadhyph-lo.tex Message-ID: Hi Recently I've noticed that some of my LaTeX files are failing to build with the following error: ! I can't find file `loadhyph-lo.tex'. I imagine sound kind of update of the TeX cache or similar is needed? Cheers Adam From jeremy at lavergne.gotdns.org Wed Jul 25 07:41:30 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Wed, 25 Jul 2012 10:41:30 -0400 Subject: LaTeX documents failing to build, unable to load file loadhyph-lo.tex In-Reply-To: References: Message-ID: > Recently I've noticed that some of my LaTeX files are failing to build > with the following error: > > ! I can't find file `loadhyph-lo.tex'. > > I imagine sound kind of update of the TeX cache or similar is needed? If that's a hyphen package, you might check out the list of which ports provide it: http://trac.macports.org/wiki/TeXLivePackages From pavillon.nicolas at gmail.com Wed Jul 25 07:56:14 2012 From: pavillon.nicolas at gmail.com (Nicolas Pavillon) Date: Wed, 25 Jul 2012 23:56:14 +0900 Subject: Texlive: kile do not find koma-script files In-Reply-To: References: Message-ID: <399338B3-2F57-4C76-A37B-D4F7D6954299@gmail.com> Hello, Just to be sure, is it the port "kde4-kile" which is the newest one, or the port "kile", which is pretty old and still based on kde3 ? What I write below is mainly concerning kde4-kile, but may also be true for the older one. From the start, kile installed with Macports is not supposed to use an external tex installation in /usr/local, and would use the one installed from Macports. In the case kile points to this external installation (which can be checked in the menu Settings->System Check... ), it would mean that it is not a standard installation. This said, the main paths for kile are set in a file called kilestdtools.rc, which should be located in /opt/local/share/apps/kile/kilestdtools.rc for a standard prefix. The path to the tex install could be changed in there. However, a manual change in this file may be overwritten by an upgrade of the port when it occurs. Cheers, Nicolas On Jul 25, 2012, at 5:22 PM, Sara Buson wrote: > Hi Everyone, > I must advise that I am quite a new user of MecPorts and not expert! > I recently installed TexLive2011. I then installed the kile editor compiling it by source and everything went fine. Despite this some days ago I run into issues with kile. It wasn't able to find any of the koma-script files. But those files were present as I see them in /usr/local/texlive/2012/texmf-dist/tex/latex/koma-script/ . Since I couldn't find any solution I decided to update from TexLive2011 to TexLive2012. I followed the simple instruction indicated here: http://tug.org/mactex/ . Installation successful but the .profile file was not updated, it still pointed to the old version of TexLive2011. The same for all the binaries in /opt/local/bin/ . I also removed the 2011 version but still they use the old version. > I changed manually the .profile putting the path to the 2012 version. > Now other editors that I have installed that using TexLive are working with the correct version (e.g. TexShop). > Despite this kile still doesn't work properly.. I guess it might have its own configuration files somewhere but I cannot find them. More, isn't there a way to make it update to a new version of TexLive when available? > I already lost several days on this problem, any suggestion would be very welcome. > > Thanks in advance, > Starla > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From mojca.miklavec.lists at gmail.com Wed Jul 25 08:38:24 2012 From: mojca.miklavec.lists at gmail.com (Mojca Miklavec) Date: Wed, 25 Jul 2012 17:38:24 +0200 Subject: LaTeX documents failing to build, unable to load file loadhyph-lo.tex In-Reply-To: References: Message-ID: On Wed, Jul 25, 2012 at 4:39 PM, Adam Mercer wrote: > Hi > > Recently I've noticed that some of my LaTeX files are failing to build > with the following error: > > ! I can't find file `loadhyph-lo.tex'. > > I imagine sound kind of update of the TeX cache or similar is needed? The Lao hyphenation patterns have been removed and the file should not be present, however it seems that your language.dat and/or language.def still reference it. I have no idea how macports handle language.dat/def files, but either you have your own copy somewhere or the updated to 2012 is still missing some bits and pieces. What does "kpsewhich language.dat" return you? I checked texlive-lang-other and I don't see any reference to Lao, but it might be hidden somewhere else. Mojca From ram at macports.org Wed Jul 25 09:03:50 2012 From: ram at macports.org (Adam Mercer) Date: Wed, 25 Jul 2012 11:03:50 -0500 Subject: LaTeX documents failing to build, unable to load file loadhyph-lo.tex In-Reply-To: References: Message-ID: On Wed, Jul 25, 2012 at 10:38 AM, Mojca Miklavec wrote: > The Lao hyphenation patterns have been removed and the file should not > be present, however it seems that your language.dat and/or > language.def still reference it. I have no idea how macports handle > language.dat/def files, but either you have your own copy somewhere or > the updated to 2012 is still missing some bits and pieces. This system shouldn't have local tex stuff anywhere. > What does "kpsewhich language.dat" return you? $ kpsewhich language.dat /opt/local/var/db/texmf/tex/generic/config/language.dat $ > I checked texlive-lang-other and I don't see any reference to Lao, but > it might be hidden somewhere else. Cheers Adam From ram at macports.org Wed Jul 25 09:32:42 2012 From: ram at macports.org (Adam Mercer) Date: Wed, 25 Jul 2012 11:32:42 -0500 Subject: LaTeX documents failing to build, unable to load file loadhyph-lo.tex In-Reply-To: References: Message-ID: On Wed, Jul 25, 2012 at 11:23 AM, Mojca Miklavec wrote: >> $ kpsewhich language.dat >> /opt/local/var/db/texmf/tex/generic/config/language.dat >> $ > > When was this file generated? I believe it contains lao? (which it shouldn't) Looks like it was last modified on 16 July, which was around the time I started seeing this problem. This file is provided by the texlive-common port, so I forced a reinstall of that port and that seems to have fixed the problem. Cheers Adam From murrayeisenberg at gmail.com Wed Jul 25 13:19:06 2012 From: murrayeisenberg at gmail.com (Murray Eisenberg) Date: Wed, 25 Jul 2012 16:19:06 -0400 Subject: Will Xcode 4.4 be OK with MacPorts under Lion Message-ID: <501054BA.70404@gmail.com> I'm still running Lion (but preparing for upgrading to Mountain Lion). Update from Xcode from 4.3 to 4.4 is now available at the App Store. Will Xcode 4.4 still work OK under Lion with MacPorts? -- Murray Eisenberg murrayeisenberg at gmail.com 80 Fearing Street phone 413 549-1020 (H) Amherst, MA 01002-1912 From jeremy at lavergne.gotdns.org Wed Jul 25 13:22:15 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Wed, 25 Jul 2012 16:22:15 -0400 Subject: Will Xcode 4.4 be OK with MacPorts under Lion In-Reply-To: <501054BA.70404@gmail.com> References: <501054BA.70404@gmail.com> Message-ID: <8995E964-9630-42A5-BE07-DF68E8F56150@lavergne.gotdns.org> > I'm still running Lion (but preparing for upgrading to Mountain Lion). > > Update from Xcode from 4.3 to 4.4 is now available at the App Store. > > Will Xcode 4.4 still work OK under Lion with MacPorts? There are no significant changes to file structure of Xcode 4.4--it should work without any problems with MacPorts unless Xcode itself has an internal bug. From ryandesign at macports.org Wed Jul 25 13:58:58 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 25 Jul 2012 15:58:58 -0500 Subject: Will Xcode 4.4 be OK with MacPorts under Lion In-Reply-To: <8995E964-9630-42A5-BE07-DF68E8F56150@lavergne.gotdns.org> References: <501054BA.70404@gmail.com> <8995E964-9630-42A5-BE07-DF68E8F56150@lavergne.gotdns.org> Message-ID: <7073443C-B23C-432D-B0C7-3C795F2B0269@macports.org> On Jul 25, 2012, at 15:22, Jeremy Lavergne wrote: >> I'm still running Lion (but preparing for upgrading to Mountain Lion). >> >> Update from Xcode from 4.3 to 4.4 is now available at the App Store. >> >> Will Xcode 4.4 still work OK under Lion with MacPorts? > > There are no significant changes to file structure of Xcode 4.4--it should work without any problems with MacPorts unless Xcode itself has an internal bug. You may need to update to MacPorts 2.1.2 for Xcode 4.4 compatibility (on Lion or Mountain Lion). From iandw.au at gmail.com Wed Jul 25 17:37:33 2012 From: iandw.au at gmail.com (Ian Wadham) Date: Thu, 26 Jul 2012 10:37:33 +1000 Subject: CMake log needed to help find a bug Message-ID: I reported a problem with kdelibs4 @4.8.2_0 failing to detect compiler characteristics correctly, see https://trac.macports.org/ticket/34605?replyto=1#comment and also https://bugs.kde.org/show_bug.cgi?id=300429 A KDE developer has responded to the latter report and he has asked for logs of CMake output from my Macports build of kdelibs4 @4.8.2_0. How do I get this? AFAICS the Macports logs are deleted after a successful build. So must I do: sudo port uninstall kdelibs4 @4.8.2_0 sudo port -k install kdelibs4 @4.8.2_0 ...? And if I do, how do I find the logs? And how do I find the logs I want amongst all the other logs? Thanks in advance, Ian W. From ryandesign at macports.org Wed Jul 25 19:40:25 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 25 Jul 2012 21:40:25 -0500 Subject: CMake log needed to help find a bug In-Reply-To: References: Message-ID: On Jul 25, 2012, at 19:37, Ian Wadham wrote: > I reported a problem with kdelibs4 @4.8.2_0 failing to detect compiler characteristics > correctly, see https://trac.macports.org/ticket/34605?replyto=1#comment and also > https://bugs.kde.org/show_bug.cgi?id=300429 > > A KDE developer has responded to the latter report and he has asked for logs of > CMake output from my Macports build of kdelibs4 @4.8.2_0. How do I get this? > > AFAICS the Macports logs are deleted after a successful build. So must I do: > > sudo port uninstall kdelibs4 @4.8.2_0 > sudo port -k install kdelibs4 @4.8.2_0 > > ...? And if I do, how do I find the logs? And how do I find the logs I want amongst > all the other logs? The command "port logfile kdelibs4" shows you where the kdelibs4 logfile is located. From chris.ruddell at gmail.com Wed Jul 25 21:04:15 2012 From: chris.ruddell at gmail.com (cruddell001) Date: Wed, 25 Jul 2012 21:04:15 -0700 (PDT) Subject: Macports won't update under ML Message-ID: <34213505.post@talk.nabble.com> I updated to Mountain Lion today and ran sudo port selfupdate - something I haven't done in probably a couple of months. However, I got an error message saying it can't install. I tried searching around, but the only proposed solution I could find was to add the line "developer_dir" to the macports.conf file. I tried that, but it didn't change anything. Here is the output using the "-d" setting: pc:~ cruddell001$ sudo port selfupdate Password: ---> Updating MacPorts base sources using rsync MacPorts base version 2.1.1 installed, MacPorts base version 2.1.2 downloaded. ---> Updating the ports tree ---> MacPorts base is outdated, installing new version 2.1.2 Installing new MacPorts release in /opt/local as root:admin; permissions 0755; Tcl-Package in /Library/Tcl Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed pc:~ cruddell001$ sudo port -d selfupdate DEBUG: Copying /Users/cruddell001/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs ---> Updating MacPorts base sources using rsync receiving file list ... done sent 36 bytes received 69 bytes 70.00 bytes/sec total size is 3543040 speedup is 33743.24 receiving file list ... done sent 36 bytes received 76 bytes 74.67 bytes/sec total size is 512 speedup is 4.57 DEBUG: successful verification with key /opt/local/share/macports/macports-pubkey.pem DEBUG: /usr/bin/tar -C /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/tmp -xf /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base.tar MacPorts base version 2.1.1 installed, DEBUG: Rebuilding and reinstalling MacPorts if needed MacPorts base version 2.1.2 downloaded. ---> Updating the ports tree Synchronizing local ports tree from rsync://rsync.macports.org/release/ports/ DEBUG: /usr/bin/rsync -rtzv --delete-after '--exclude=/PortIndex*' rsync://rsync.macports.org/release/ports/ /opt/local/var/macports/sources/rsync.macports.org/release/ports receiving file list ... done sent 53 bytes received 683973 bytes 124368.36 bytes/sec total size is 35682349 speedup is 52.17 DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/ports/PortIndex_darwin_12_i386/PortIndex /opt/local/var/macports/sources/rsync.macports.org/release/ports receiving file list ... done sent 36 bytes received 70 bytes 70.67 bytes/sec total size is 8539698 speedup is 80563.19 ---> MacPorts base is outdated, installing new version 2.1.2 DEBUG: Permissions OK Installing new MacPorts release in /opt/local as root:admin; permissions 0755; Tcl-Package in /Library/Tcl checking build system type... i386-apple-darwin12.0.0 checking host system type... i386-apple-darwin12.0.0 checking target system type... i386-apple-darwin12.0.0 checking MacPorts version... 2.1.2 checking for sw_vers... /usr/bin/sw_vers checking for defaults... /usr/bin/defaults checking for xcode-select... /usr/bin/xcode-select checking Mac OS X version... 10.8 checking Xcode location... /Developer checking Xcode version... 4.2.1 checking for gcc... /usr/bin/cc checking whether the C compiler works... no configure: error: in `/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base': configure: error: C compiler cannot create executables See `config.log' for more details Command failed: cd /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base && CC=/usr/bin/cc ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0755 --enable-readline && make && make install SELFUPDATING=1 Exit code: 77 DEBUG: Error installing new MacPorts base: command execution failed while executing "macports::selfupdate [array get global_options] base_updated" Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed pc:~ cruddell001$ -- View this message in context: http://old.nabble.com/Macports-won%27t-update-under-ML-tp34213505p34213505.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From iandw.au at gmail.com Wed Jul 25 21:20:29 2012 From: iandw.au at gmail.com (Ian Wadham) Date: Thu, 26 Jul 2012 14:20:29 +1000 Subject: CMake log needed to help find a bug In-Reply-To: References: Message-ID: <4765B56B-2983-4D56-9A6E-1BA27E8CC136@gmail.com> On 26/07/2012, at 12:40 PM, Ryan Schmidt wrote: > On Jul 25, 2012, at 19:37, Ian Wadham wrote: >> AFAICS the Macports logs are deleted after a successful build. So must I do: >> >> sudo port uninstall kdelibs4 @4.8.2_0 >> sudo port -k install kdelibs4 @4.8.2_0 >> >> ...? And if I do, how do I find the logs? And how do I find the logs I want amongst >> all the other logs? > > The command "port logfile kdelibs4" shows you where the kdelibs4 logfile is located. Thanks, Ryan. I get the following. That's what made me think I had to uninstall and re-install. Or is there some other problem on my machine? Tara:~>port logfile kdelibs4 Warning: port definitions are more than two weeks old, consider using selfupdate Error: Log file not found for port in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/kde/kdelibs4 Tara:~>port version Version: 2.0.4 Thanks again, Ian W. From ryandesign at macports.org Wed Jul 25 21:56:50 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 25 Jul 2012 23:56:50 -0500 Subject: CMake log needed to help find a bug In-Reply-To: <4765B56B-2983-4D56-9A6E-1BA27E8CC136@gmail.com> References: <4765B56B-2983-4D56-9A6E-1BA27E8CC136@gmail.com> Message-ID: On Jul 25, 2012, at 23:20, Ian Wadham wrote: > On 26/07/2012, at 12:40 PM, Ryan Schmidt wrote: >> On Jul 25, 2012, at 19:37, Ian Wadham wrote: >>> AFAICS the Macports logs are deleted after a successful build. So must I do: >>> >>> sudo port uninstall kdelibs4 @4.8.2_0 >>> sudo port -k install kdelibs4 @4.8.2_0 >>> >>> ...? And if I do, how do I find the logs? And how do I find the logs I want amongst >>> all the other logs? >> >> The command "port logfile kdelibs4" shows you where the kdelibs4 logfile is located. > > Thanks, Ryan. I get the following. That's what made me think I had to uninstall and re-install. > Or is there some other problem on my machine? > > Tara:~>port logfile kdelibs4 > Warning: port definitions are more than two weeks old, consider using selfupdate > Error: Log file not found for port in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/kde/kdelibs4 > Tara:~>port version > Version: 2.0.4 As you already said earlier, MacPorts cleans up logs of successful builds. If you want the logfile, rebuild with -k or set keeplogs to yes in macports.conf and then rebuild normally. You may also need to use the -s flag to actually build on your machine instead of looking for a binary on our server. From ryandesign at macports.org Wed Jul 25 21:57:44 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 25 Jul 2012 23:57:44 -0500 Subject: Macports won't update under ML In-Reply-To: <34213505.post@talk.nabble.com> References: <34213505.post@talk.nabble.com> Message-ID: On Jul 25, 2012, at 23:04, cruddell001 wrote: > checking Mac OS X version... 10.8 > checking Xcode location... /Developer > checking Xcode version... 4.2.1 Update to Xcode 4.4 first. Visit the Mac App Store. From james.busser at ubc.ca Wed Jul 25 23:09:59 2012 From: james.busser at ubc.ca (Busser, Jim) Date: Thu, 26 Jul 2012 06:09:59 +0000 Subject: Macports won't update under ML In-Reply-To: <34213505.post@talk.nabble.com> References: <34213505.post@talk.nabble.com> Message-ID: <96FC7D29-5D23-4B7F-894C-13B287496CE7@ubc.ca> On 2012-07-25, at 9:04 PM, cruddell001 wrote: > I updated to Mountain Lion today and ran sudo port selfupdate ... Here is > the output using the "-d" setting: > > pc:~ cruddell001$ sudo port selfupdate > Password: > ... > checking Xcode location... /Developer > checking Xcode version... 4.2.1 I updated to Mountain Lion without having ever had Xcode (or MacPorts) on my target machine. I installed Xcode via the App Store, and note that it is version 4.4. Also, anyone downloading Xcode from the App Store should also note that the App Store provides no option to select to also download and install the Command Line Tools, which is why -- when I tried a fresh install from MacPorts source -- I ran into no acceptable C compiler found in $PATH Completion of the Xcode install that is required by MacPorts (via App Store download), requires another step. An Admin user needs to launch Xcode and go into File > Preferences and, under the Downloads pane, select to install the Command Line Tools. When you click Install, you are prompted to enter an Apple Developer ID and password, however the free (no charge) account which I had established some time ago was accepted and after a few minutes the status of the Command Line Tools was updated to "Installed". I was then successful, under MacPorts -2.1.2 and after exiting Terminal and re-opening it, to run .configure make sudo make install -- Jim From jmr at macports.org Wed Jul 25 23:56:00 2012 From: jmr at macports.org (Joshua Root) Date: Thu, 26 Jul 2012 16:56:00 +1000 Subject: MacPorts 2.1.2 has been released Message-ID: <5010EA00.9030607@macports.org> The MacPorts Project is pleased to announce the release of version 2.1.2. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new installs, there are also package installers available for 10.5, 10.6, 10.7 and 10.8 (universal builds, the first i386/ppc and the others i386/x86_64) at [2]. The source is also available as tarballs compressed with gzip or bzip2, or from the subversion tag [3]. Detached PGP signatures for the disk image, packages and source tarballs have been made with my key, which is available on the keyservers and my MacPorts wiki page [4], the fingerprint being: 0x63BAD8CF2A10D5EE: 5F83 E16B D885 0601 5084 63C2 63BA D8CF 2A10 D5EE The Mountain Lion pkg was built by Adam Mercer, and is signed with his Developer ID. Josh (on behalf of the MacPorts Port Managers) [1] [2] [3] [4] From bluestarla_ at hotmail.com Thu Jul 26 04:55:16 2012 From: bluestarla_ at hotmail.com (Sara Buson) Date: Thu, 26 Jul 2012 13:55:16 +0200 Subject: Texlive: kile do not find koma-script files In-Reply-To: <399338B3-2F57-4C76-A37B-D4F7D6954299@gmail.com> References: <399338B3-2F57-4C76-A37B-D4F7D6954299@gmail.com> Message-ID: <8D4F5135-611F-4991-A231-3BB88EBF554E@hotmail.com> Thanks for the clarifications Nicolas, I am using kde4-kile @2.1.2_0 In these days I went a bit around in the installed kile files and I already had a look at what you pointed out. Actually I first tried to manually change the kilestdtools.rc putting the correct path but this wasn't of any help. I finally realize that in Preferences->Tools->Build are set all the path that kile will use when compiling (e.g. /opt/local/bin/pdflatex). I set all these path like: /usr/local/texlive/2012/bin/x86_64-darwin/pdflatex But it still do not find classicthesis-preamble.sty. Actually I cannot find it too! > From the start, kile installed with Macports is not supposed to use an external tex installation in /usr/local, and would use the one installed from Macports. Now I uninstall and re-install kile and I checked it: It seems pointing at the correct files. But when trying to use the classic thesis environment it still do not find classicthesis-preamble.sty. I downloaded the classicthesis.zip but that file wasn't there.. Is there a link to directly download the missing file? Thanks, Starla On Jul 25, 2012, at 4:56 PM, Nicolas Pavillon wrote: > Hello, > > Just to be sure, is it the port "kde4-kile" which is the newest one, or the port "kile", which is pretty old and still based on kde3 ? What I write below is mainly concerning kde4-kile, but may also be true for the older one. > > From the start, kile installed with Macports is not supposed to use an external tex installation in /usr/local, and would use the one installed from Macports. In the case kile points to this external installation (which can be checked in the menu Settings->System Check... ), it would mean that it is not a standard installation. > > This said, the main paths for kile are set in a file called kilestdtools.rc, which should be located in /opt/local/share/apps/kile/kilestdtools.rc for a standard prefix. The path to the tex install could be changed in there. However, a manual change in this file may be overwritten by an upgrade of the port when it occurs. > > Cheers, > > Nicolas > > On Jul 25, 2012, at 5:22 PM, Sara Buson wrote: > >> I must advise that I am quite a new user of MecPorts and not expert! >> I recently installed TexLive2011. I then installed the kile editor compiling it by source and everything went fine. Despite this some days ago I run into issues with kile. It wasn't able to find any of the koma-script files. But those files were present as I see them in /usr/local/texlive/2012/texmf-dist/tex/latex/koma-script/ . Since I couldn't find any solution I decided to update from TexLive2011 to TexLive2012. I followed the simple instruction indicated here: http://tug.org/mactex/ . Installation successful but the .profile file was not updated, it still pointed to the old version of TexLive2011. The same for all the binaries in /opt/local/bin/ . I also removed the 2011 version but still they use the old version. >> I changed manually the .profile putting the path to the 2012 version. >> Now other editors that I have installed that using TexLive are working with the correct version (e.g. TexShop). >> Despite this kile still doesn't work properly.. I guess it might have its own configuration files somewhere but I cannot find them. More, isn't there a way to make it update to a new version of TexLive when available? >> I already lost several days on this problem, any suggestion would be very welcome. >> >> Thanks in advance, >> Starla >> >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.png Type: image/png Size: 31898 bytes Desc: not available URL: From magill at me.com Thu Jul 26 05:41:51 2012 From: magill at me.com (William H. Magill) Date: Thu, 26 Jul 2012 08:41:51 -0400 Subject: Upgrading to Mountain Lion -- migration document changes? Message-ID: <38AF664E-48B5-4836-B861-B6A8356815BE@me.com> I am about to upgrade to Mountain Lion and I note that the Migration Document does not mention anything specifically about it. Are there any "differences" or particular "changes/gotchas" unique to Mountain Lion that need to be considered? I've updated Macports itself and all of my installed ports. sudo port selfupdate sudo port upgrade outdated Backup (time machine) is now running. And am now at the "breathe deeply then visit the app store" stage. T.T.F.N. William H. Magill # iMac11,3 Core i7 [2.936GHz - 4 GB 1333] OS X 10.7.4 # MacBook Pro4.1 Core 2 Duo [2.5GHz - 4GB 667] OS X 10.6.8 # Mac mini Core Duo [1.66 Ghz - 2 GB 667] OS X 10.6.8 # PWS433a [Alpha 21164 Rev 7.2 (EV56)- 64 Meg] Tru64 5.1a # XP1000 [Alpha 21264-3 (EV6) - 256 meg] FreeBSD 5.3 # XP1000 [Alpha 21264-A (EV6-7) - 256 meg] FreeBSD 5.3 magill at mcgillsociety.org magill at me.com whmagill at gmail.com From ryandesign at macports.org Thu Jul 26 06:24:09 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 26 Jul 2012 08:24:09 -0500 Subject: Upgrading to Mountain Lion -- migration document changes? In-Reply-To: <38AF664E-48B5-4836-B861-B6A8356815BE@me.com> References: <38AF664E-48B5-4836-B861-B6A8356815BE@me.com> Message-ID: On Jul 26, 2012, at 07:41, William H. Magill wrote: > I am about to upgrade to Mountain Lion and I note that the Migration Document does not mention anything specifically about it. > > Are there any "differences" or particular "changes/gotchas" unique to Mountain Lion that need to be considered? Should be the same as before. Upgrade OS, upgrade Xcode, upgrade Xcode command line tools, accept Xcode license agreement (maybe?), rebuild all ports. From damon.mcdougall at gmail.com Thu Jul 26 06:52:17 2012 From: damon.mcdougall at gmail.com (Damon McDougall) Date: Thu, 26 Jul 2012 14:52:17 +0100 Subject: Will Xcode 4.4 be OK with MacPorts under Lion In-Reply-To: <7073443C-B23C-432D-B0C7-3C795F2B0269@macports.org> References: <501054BA.70404@gmail.com> <8995E964-9630-42A5-BE07-DF68E8F56150@lavergne.gotdns.org> <7073443C-B23C-432D-B0C7-3C795F2B0269@macports.org> Message-ID: <20120726135217.GI8843@host-57-93.warwick.ac.uk> On Wed, Jul 25, 2012 at 03:58:58PM -0500, Ryan Schmidt wrote: > > On Jul 25, 2012, at 15:22, Jeremy Lavergne wrote: > > >> I'm still running Lion (but preparing for upgrading to Mountain Lion). > >> > >> Update from Xcode from 4.3 to 4.4 is now available at the App Store. > >> > >> Will Xcode 4.4 still work OK under Lion with MacPorts? > > > > There are no significant changes to file structure of Xcode 4.4--it should work without any problems with MacPorts unless Xcode itself has an internal bug. > > Might one need to run: sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer so that MacPorts can see where the new version of XCode is (espeically since 10.6 doesn't have the App Store). Maybe I'm wrong, but I thought I'd throw it out there. > > You may need to update to MacPorts 2.1.2 for Xcode 4.4 compatibility (on Lion or Mountain Lion). > -- Damon McDougall http://damon-is-a-geek.com B2.39 Mathematics Institute University of Warwick Coventry West Midlands CV4 7AL United Kingdom From ryandesign at macports.org Thu Jul 26 07:08:27 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 26 Jul 2012 09:08:27 -0500 Subject: Will Xcode 4.4 be OK with MacPorts under Lion In-Reply-To: <20120726135217.GI8843@host-57-93.warwick.ac.uk> References: <501054BA.70404@gmail.com> <8995E964-9630-42A5-BE07-DF68E8F56150@lavergne.gotdns.org> <7073443C-B23C-432D-B0C7-3C795F2B0269@macports.org> <20120726135217.GI8843@host-57-93.warwick.ac.uk> Message-ID: On Jul 26, 2012, at 08:52, Damon McDougall wrote: > On Wed, Jul 25, 2012 at 03:58:58PM -0500, Ryan Schmidt wrote: >> >> On Jul 25, 2012, at 15:22, Jeremy Lavergne wrote: >> >>>> I'm still running Lion (but preparing for upgrading to Mountain Lion). >>>> >>>> Update from Xcode from 4.3 to 4.4 is now available at the App Store. >>>> >>>> Will Xcode 4.4 still work OK under Lion with MacPorts? >>> >>> There are no significant changes to file structure of Xcode 4.4--it should work without any problems with MacPorts unless Xcode itself has an internal bug. >>> > > Might one need to run: > > sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer > > so that MacPorts can see where the new version of XCode is (espeically > since 10.6 doesn't have the App Store). > > Maybe I'm wrong, but I thought I'd throw it out there. If you were upgrading from Snow Leopard and not from Lion, then sure, you would need to do that. That's also spelled out in our documentation. https://trac.macports.org/wiki/ProblemHotlist#xcode-select From ryandesign at macports.org Thu Jul 26 07:09:43 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 26 Jul 2012 09:09:43 -0500 Subject: Will Xcode 4.4 be OK with MacPorts under Lion In-Reply-To: <20120726135217.GI8843@host-57-93.warwick.ac.uk> References: <501054BA.70404@gmail.com> <8995E964-9630-42A5-BE07-DF68E8F56150@lavergne.gotdns.org> <7073443C-B23C-432D-B0C7-3C795F2B0269@macports.org> <20120726135217.GI8843@host-57-93.warwick.ac.uk> Message-ID: <552F833D-B9ED-44D1-A51B-334B4325DADF@macports.org> On Jul 26, 2012, at 08:52, Damon McDougall wrote: > (espeically > since 10.6 doesn't have the App Store). 10.6 does of course have the App Store, since 10.6.8. From koch at abstracture.de Thu Jul 26 07:56:56 2012 From: koch at abstracture.de (uck) Date: Thu, 26 Jul 2012 07:56:56 -0700 (PDT) Subject: Macports won't update under ML Message-ID: <34215715.post@talk.nabble.com> Hi, I saw the same problem with my MacPort update today after the ML installation. The day before I also updated to xcode 4.4. So I don't know exactly which of the 2 updates was responsible for the problem but for me it worked after reinstalling the command line tools in XCode... Good Luck -- View this message in context: http://old.nabble.com/Macports-won%27t-update-under-ML-tp34213505p34215715.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From william at gallaf.net Thu Jul 26 08:13:04 2012 From: william at gallaf.net (William Gallafent) Date: Thu, 26 Jul 2012 16:13:04 +0100 Subject: Oddity using Xcode 4.4 on OS 10.7. Message-ID: Hi All, This is slightly OT, for which apologies, but might have an impact on a MacPorts installation, and I suspect people here might know how to fix it. I'm running up-to-date Mac OS 10.7, and have just installed Xcode 4.4 using the App Store. Next step is to install the Command Line Tools. When I click on "Install" for the Command Line Tools in the Preferences/Downloads pane, a progress bar appears, and after a while changes to "Installed". A quick look in /var/log/install.log indicates that the installation succeeded. Last few lines follow: ? Jul 26 16:04:29 Humber installd[2842]: PackageKit: xpchelper --rebuild-cache --overlay /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At Startup/PKInstallSandbox-tmp/Root Jul 26 16:04:29 Humber installd[2842]: PackageKit: Executing script "preinstall" in /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At Startup/PKInstallSandbox-tmp/Scripts/com.apple.pkg.DeveloperToolsCLI.0qBcl9 Jul 26 16:04:30 Humber installd[2842]: PackageKit: Shoving /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At Startup/PKInstallSandbox-tmp/Root (3 items) to / Jul 26 16:05:23 Humber installd[2842]: PackageKit: Executing script "postinstall" in /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At Startup/PKInstallSandbox-tmp/Scripts/com.apple.pkg.DeveloperToolsCLI.0qBcl9 Jul 26 16:05:23 Humber _securityagent[2875]: Running Install Scripts . . . Jul 26 16:05:23 Humber _securityagent[2877]: Begin script: postflight Jul 26 16:05:34 Humber _securityagent[2883]: End script: postflight Jul 26 16:05:34 Humber _securityagent[2884]: 1 Install Scripts run. Jul 26 16:05:34 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.BluetoothSDKLeo to /private/var/db/receipts Jul 26 16:05:34 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.clang to /private/var/db/receipts Jul 26 16:05:34 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.CoreAudioSDKLeo to /private/var/db/receipts Jul 26 16:05:34 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.DeveloperToolsCLI to /private/var/db/receipts Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.DevSDKLeo to /private/var/db/receipts Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.FireWireSDKLeo to /private/var/db/receipts Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.JavaSDKLeo to /private/var/db/receipts Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.llvm-gcc4.2 to /private/var/db/receipts Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.OpenGLSDKLeo to /private/var/db/receipts Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.QuickTimeSDKLeo to /private/var/db/receipts Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.WebKitSDKLeo to /private/var/db/receipts Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.X11DocumentationLeo to /private/var/db/receipts Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for com.apple.pkg.X11SDKLeo to /private/var/db/receipts Jul 26 16:05:36 Humber installd[2842]: PackageKit: Registered bundle file://localhost/usr/share/git-gui/lib/Git%20Gui.app/ Jul 26 16:05:36 Humber installd[2842]: PackageKit: Registered bundle file://localhost/System/Library/CoreServices/ManagedClient.app/ Jul 26 16:05:36 Humber installd[2842]: PackageKit: ----- End install ----- However, my /usr/bin/clang is still the old version, and does not match the one below /Applications/Xcode.app: Humber:RailEasy williamg$ /usr/bin/clang --version Apple clang version 3.1 (tags/Apple/clang-318.0.61) (based on LLVM 3.1svn) Target: x86_64-apple-darwin11.4.0 Thread model: posix Humber:RailEasy williamg$ /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang --version Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn) Target: x86_64-apple-darwin11.4.0 Thread model: posix Is this expected behaviour? It seems very odd to me. The other thing that's odd is that if I quit and restart Xcode, the Command Line Tools have an "Install" button again, instead of saying "Installed". So clearly Xcode doesn't think the installation has worked either. Any help welcome! -- Bill Gallafent. From jeremy at lavergne.gotdns.org Thu Jul 26 08:15:36 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Thu, 26 Jul 2012 11:15:36 -0400 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: References: Message-ID: <337B8AB0-E1D6-4D73-A31D-3D40058338DC@lavergne.gotdns.org> > However, my /usr/bin/clang is still the old version, and does not > match the one below /Applications/Xcode.app: Is that clang a symlink? > Humber:RailEasy williamg$ /usr/bin/clang --version > Apple clang version 3.1 (tags/Apple/clang-318.0.61) (based on LLVM 3.1svn) > Target: x86_64-apple-darwin11.4.0 > Thread model: posix > Humber:RailEasy williamg$ > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang > --version > Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn) > Target: x86_64-apple-darwin11.4.0 > Thread model: posix > > Is this expected behaviour? It seems very odd to me. The other thing > that's odd is that if I quit and restart Xcode, the Command Line Tools > have an "Install" button again, instead of saying "Installed". So > clearly Xcode doesn't think the installation has worked either. You might consider installing the Command Line Tools from connect.apple.com. From larry.velazquez at gmail.com Thu Jul 26 09:03:23 2012 From: larry.velazquez at gmail.com (=?iso-8859-1?Q?Lawrence_Vel=E1zquez?=) Date: Thu, 26 Jul 2012 12:03:23 -0400 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: <337B8AB0-E1D6-4D73-A31D-3D40058338DC@lavergne.gotdns.org> References: <337B8AB0-E1D6-4D73-A31D-3D40058338DC@lavergne.gotdns.org> Message-ID: <368211A9-BBDC-4F7B-8AE7-E3BDA47FFDB3@gmail.com> On Jul 26, 2012, at 11:15 a.m., Jeremy Lavergne wrote: >> However, my /usr/bin/clang is still the old version, and does not >> match the one below /Applications/Xcode.app: > > Is that clang a symlink? Nope. >> Is this expected behaviour? It seems very odd to me. The other thing >> that's odd is that if I quit and restart Xcode, the Command Line Tools >> have an "Install" button again, instead of saying "Installed". So >> clearly Xcode doesn't think the installation has worked either. I'm seeing the same behavior. When I look at all messages in Console, I see the following messages while Xcode waits for me to authorize: 7/26/12 11:53:20.129 a.m. authorizationhost: SFBuiltinEntitled: Xcode.app is not entitled for system.install.apple-software 7/26/12 11:53:36.094 a.m. authorizationhost: SFBuiltinEntitled: Xcode.app is not entitled for system.install.apple-software 7/26/12 11:53:43.005 a.m. authorizationhost: SFBuiltinEntitled: Xcode.app is not entitled for system.install.apple-software 7/26/12 11:53:58.332 a.m. authorizationhost: SFBuiltinEntitled: Xcode.app is not entitled for system.install.apple-software 7/26/12 11:53:58.367 a.m. authorizationhost: SFBuiltinEntitled: Xcode.app is not entitled for system.install.app-store-software 7/26/12 11:53:58.401 a.m. authorizationhost: SFBuiltinEntitled: Xcode.app is not entitled for system.install.app-store-software When I actually submit my password, I get this: 7/26/12 11:53:58.403 a.m. com.apple.SecurityServer: Failed to authorize right 'system.install.app-store-software' by client '/System/Library/PrivateFrameworks/PackageKit.framework/Versions/A/Resources/installd' [86797] for authorization created by '/Applications/Xcode.app' [86769] vq From larry.velazquez at gmail.com Thu Jul 26 09:12:52 2012 From: larry.velazquez at gmail.com (=?iso-8859-1?Q?Lawrence_Vel=E1zquez?=) Date: Thu, 26 Jul 2012 12:12:52 -0400 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: <337B8AB0-E1D6-4D73-A31D-3D40058338DC@lavergne.gotdns.org> References: <337B8AB0-E1D6-4D73-A31D-3D40058338DC@lavergne.gotdns.org> Message-ID: <65FBA194-2B2B-4EF4-A219-9F5C14CBD86D@gmail.com> On Jul 26, 2012, at 11:15 a.m., Jeremy Lavergne wrote: > You might consider installing the Command Line Tools from connect.apple.com. This works for me, by the way. My /usr/bin/clang is now 4.0, and the Preferences window indicates that the tools are installed, even after restarting Xcode. vq From domiman at gmail.com Thu Jul 26 09:29:31 2012 From: domiman at gmail.com (Dominik Reichardt) Date: Thu, 26 Jul 2012 18:29:31 +0200 Subject: how to proceed past errors? Message-ID: <1B055DA1-3646-4F81-9978-2742E91517D4@gmail.com> how do I proceed past errors? my upgrade on ML fails on w3m (not to mention fluidsynth but that has a solution inthe tracker) and I'd like to move on :) I think I once saw a mention on how to proceed but can't find it anymore... Take care Dominik From jeremyhu at macports.org Thu Jul 26 09:31:23 2012 From: jeremyhu at macports.org (Jeremy Huddleston Sequoia) Date: Thu, 26 Jul 2012 09:31:23 -0700 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: References: Message-ID: Hi William, Can you please file a bug report at http://bugreport.apple.com including: /var/log/system.log /var/log/install.log The output of otool -l /usr/bin/clang | grep uuid The output of pkgutil --lsbom com.apple.pkg.DeveloperToolsCLI Please let me know the radar number, so I can take a look at those logs and keep an eye on the bug. Does installing the package from connect.apple.com fix it? (do this *after* getting the above info) I'd be interested in hearing "me too"s or "works for me"s from others on 10.7 installing through XCode (as opposed to ML users or those going to connect.apple.com) to find out if this is a 1-off issue or something others are seeing. Thanks, Jeremy On Jul 26, 2012, at 08:13, William Gallafent wrote: > Hi All, > > This is slightly OT, for which apologies, but might have an impact on > a MacPorts installation, and I suspect people here might know how to > fix it. > > I'm running up-to-date Mac OS 10.7, and have just installed Xcode 4.4 > using the App Store. Next step is to install the Command Line Tools. > > When I click on "Install" for the Command Line Tools in the > Preferences/Downloads pane, a progress bar appears, and after a while > changes to "Installed". A quick look in /var/log/install.log indicates > that the installation succeeded. Last few lines follow: > > ? > Jul 26 16:04:29 Humber installd[2842]: PackageKit: xpchelper > --rebuild-cache --overlay > /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At > Startup/PKInstallSandbox-tmp/Root > Jul 26 16:04:29 Humber installd[2842]: PackageKit: Executing script > "preinstall" in /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup > At Startup/PKInstallSandbox-tmp/Scripts/com.apple.pkg.DeveloperToolsCLI.0qBcl9 > Jul 26 16:04:30 Humber installd[2842]: PackageKit: Shoving > /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At > Startup/PKInstallSandbox-tmp/Root (3 items) to / > Jul 26 16:05:23 Humber installd[2842]: PackageKit: Executing script > "postinstall" in > /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/Cleanup At > Startup/PKInstallSandbox-tmp/Scripts/com.apple.pkg.DeveloperToolsCLI.0qBcl9 > Jul 26 16:05:23 Humber _securityagent[2875]: Running Install Scripts . . . > Jul 26 16:05:23 Humber _securityagent[2877]: Begin script: postflight > Jul 26 16:05:34 Humber _securityagent[2883]: End script: postflight > Jul 26 16:05:34 Humber _securityagent[2884]: 1 Install Scripts run. > Jul 26 16:05:34 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.BluetoothSDKLeo to /private/var/db/receipts > Jul 26 16:05:34 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.clang to /private/var/db/receipts > Jul 26 16:05:34 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.CoreAudioSDKLeo to /private/var/db/receipts > Jul 26 16:05:34 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.DeveloperToolsCLI to /private/var/db/receipts > Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.DevSDKLeo to /private/var/db/receipts > Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.FireWireSDKLeo to /private/var/db/receipts > Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.JavaSDKLeo to /private/var/db/receipts > Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.llvm-gcc4.2 to /private/var/db/receipts > Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.OpenGLSDKLeo to /private/var/db/receipts > Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.QuickTimeSDKLeo to /private/var/db/receipts > Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.WebKitSDKLeo to /private/var/db/receipts > Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.X11DocumentationLeo to /private/var/db/receipts > Jul 26 16:05:36 Humber installd[2842]: PackageKit: Writing receipt for > com.apple.pkg.X11SDKLeo to /private/var/db/receipts > Jul 26 16:05:36 Humber installd[2842]: PackageKit: Registered bundle > file://localhost/usr/share/git-gui/lib/Git%20Gui.app/ > Jul 26 16:05:36 Humber installd[2842]: PackageKit: Registered bundle > file://localhost/System/Library/CoreServices/ManagedClient.app/ > Jul 26 16:05:36 Humber installd[2842]: PackageKit: ----- End install ----- > > However, my /usr/bin/clang is still the old version, and does not > match the one below /Applications/Xcode.app: > > Humber:RailEasy williamg$ /usr/bin/clang --version > Apple clang version 3.1 (tags/Apple/clang-318.0.61) (based on LLVM 3.1svn) > Target: x86_64-apple-darwin11.4.0 > Thread model: posix > Humber:RailEasy williamg$ > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang > --version > Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn) > Target: x86_64-apple-darwin11.4.0 > Thread model: posix > > Is this expected behaviour? It seems very odd to me. The other thing > that's odd is that if I quit and restart Xcode, the Command Line Tools > have an "Install" button again, instead of saying "Installed". So > clearly Xcode doesn't think the installation has worked either. > > Any help welcome! > > -- > Bill Gallafent. > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users From jeremyhu at macports.org Thu Jul 26 09:35:59 2012 From: jeremyhu at macports.org (Jeremy Huddleston Sequoia) Date: Thu, 26 Jul 2012 09:35:59 -0700 Subject: how to proceed past errors? In-Reply-To: <1B055DA1-3646-4F81-9978-2742E91517D4@gmail.com> References: <1B055DA1-3646-4F81-9978-2742E91517D4@gmail.com> Message-ID: <474078F7-8277-4AA3-8A67-C5150A41D8BB@macports.org> On Jul 26, 2012, at 09:29, Dominik Reichardt wrote: > how do I proceed past errors? my upgrade on ML fails on w3m (not to mention fluidsynth but that has a solution inthe tracker) and I'd like to move on :) > I think I once saw a mention on how to proceed but can't find it anymore... You should be uninstalling everything and then reinstalling it. To "move on" just try the next thing... something like this should work. Note that I just wrote it into this email, so it's not tested and may have a typo, but you get the idea: port list active | awk '{print $1}' > ${HOME}/macports_list sudo port -v -f uninstall installed cat ${HOME}/macports_list | while read f ; do sudo rmdir /opt/local/var/macports/software/$f # Not sure if this is still needed... [ -e /opt/local/var/macports/software/$f ] || sudo port -v install $f done echo "Failed:" cat ${HOME}/macports_list | while read f ; do [ -e /opt/local/var/macports/software/$f ] || echo " $f" done From jeremyhu at macports.org Thu Jul 26 09:37:18 2012 From: jeremyhu at macports.org (Jeremy Huddleston Sequoia) Date: Thu, 26 Jul 2012 09:37:18 -0700 Subject: how to proceed past errors? In-Reply-To: <1B055DA1-3646-4F81-9978-2742E91517D4@gmail.com> References: <1B055DA1-3646-4F81-9978-2742E91517D4@gmail.com> Message-ID: <85D3598D-CDC7-4989-B7CF-1238BC150823@macports.org> Also, Have you filed a ticket about w3m? My guess is that w3m is failing because of boehmgc changes and not because of Lion->ML changes. --Jeremy On Jul 26, 2012, at 09:29, Dominik Reichardt wrote: > how do I proceed past errors? my upgrade on ML fails on w3m (not to mention fluidsynth but that has a solution inthe tracker) and I'd like to move on :) > I think I once saw a mention on how to proceed but can't find it anymore... > > Take care > > Dominik > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users From dluke at geeklair.net Thu Jul 26 09:41:20 2012 From: dluke at geeklair.net (Daniel J. Luke) Date: Thu, 26 Jul 2012 12:41:20 -0400 Subject: how to proceed past errors? In-Reply-To: <1B055DA1-3646-4F81-9978-2742E91517D4@gmail.com> References: <1B055DA1-3646-4F81-9978-2742E91517D4@gmail.com> Message-ID: <4DC36D42-31BC-46F9-BC5F-F77918C71077@geeklair.net> On Jul 26, 2012, at 12:29 PM, Dominik Reichardt wrote: > how do I proceed past errors? my upgrade on ML fails on w3m (not to mention fluidsynth but that has a solution inthe tracker) and I'd like to move on :) > I think I once saw a mention on how to proceed but can't find it anymore... From the man page: -p Despite any errors encountered, proceed to process multiple ports and commands. -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ From jeremyhu at macports.org Thu Jul 26 09:43:07 2012 From: jeremyhu at macports.org (Jeremy Huddleston Sequoia) Date: Thu, 26 Jul 2012 09:43:07 -0700 Subject: how to proceed past errors? In-Reply-To: <4DC36D42-31BC-46F9-BC5F-F77918C71077@geeklair.net> References: <1B055DA1-3646-4F81-9978-2742E91517D4@gmail.com> <4DC36D42-31BC-46F9-BC5F-F77918C71077@geeklair.net> Message-ID: <23E62146-A052-4328-B0F4-2733C0385B00@macports.org> On Jul 26, 2012, at 09:41, "Daniel J. Luke" wrote: > On Jul 26, 2012, at 12:29 PM, Dominik Reichardt wrote: >> how do I proceed past errors? my upgrade on ML fails on w3m (not to mention fluidsynth but that has a solution inthe tracker) and I'd like to move on :) >> I think I once saw a mention on how to proceed but can't find it anymore... > > > From the man page: > > -p Despite any errors encountered, proceed to process multiple > ports and commands. That is *very* problematic. Don't do it unless you really, really, really know what it implies. From ryandesign at macports.org Thu Jul 26 10:04:39 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 26 Jul 2012 12:04:39 -0500 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: References: Message-ID: On Jul 26, 2012, at 11:31, Jeremy Huddleston Sequoia wrote: > Can you please file a bug report at http://bugreport.apple.com including: > > /var/log/system.log > /var/log/install.log > The output of otool -l /usr/bin/clang | grep uuid > The output of pkgutil --lsbom com.apple.pkg.DeveloperToolsCLI > > Please let me know the radar number, so I can take a look at those logs and keep an eye on the bug. > > Does installing the package from connect.apple.com fix it? (do this *after* getting the above info) > > I'd be interested in hearing "me too"s or "works for me"s from others on 10.7 installing through XCode (as opposed to ML users or those going to connect.apple.com) to find out if this is a 1-off issue or something others are seeing. "Me too". New machine, OS X 10.7.4. Installed Xcode 4.3.3 from App Store a week ago, installed command line tools from Preferences > Downloads. Yesterday updated to Xcode 4.4 from App Store, (re)installed command line tools from Preferences > Downloads. Confirmed mismatched clang versions as OP reported. From ram at macports.org Thu Jul 26 11:06:57 2012 From: ram at macports.org (Adam Mercer) Date: Thu, 26 Jul 2012 13:06:57 -0500 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: References: Message-ID: On Thu, Jul 26, 2012 at 11:31 AM, Jeremy Huddleston Sequoia wrote: > I'd be interested in hearing "me too"s or "works for me"s from others on 10.7 installing through XCode (as opposed to ML users or those going to connect.apple.com) to find out if this is a 1-off issue or something others are seeing. Same here, installed Xcode-4.4 on top of Xcode-4.3.3 on 10.7.4. It alerted me that the commands line tools were out of date and needed updating. I updated them from within Xcode. After installation clang still reported that it was version 3.1. No matter how many times I installed the command line tools through Xcode clang was not updated. Only after downloading the command line tools from connect.apple.com and installing manually did clang get updated. Cheers Adam From ram at macports.org Thu Jul 26 14:57:02 2012 From: ram at macports.org (Adam Mercer) Date: Thu, 26 Jul 2012 16:57:02 -0500 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: References: Message-ID: On Thu, Jul 26, 2012 at 11:31 AM, Jeremy Huddleston Sequoia wrote: > I'd be interested in hearing "me too"s or "works for me"s from others on 10.7 installing through XCode (as opposed to ML users or those going to connect.apple.com) to find out if this is a 1-off issue or something others are seeing. Just encountered this on another Lion machine, updating from Xcode-4.3.3. One thing I noticed is that the installation of the command line tools started at 70% complete, as if it didn't download the tools and just used the previous installer. > Can you please file a bug report at http://bugreport.apple.com including: > > /var/log/system.log > /var/log/install.log > The output of otool -l /usr/bin/clang | grep uuid > The output of pkgutil --lsbom com.apple.pkg.DeveloperToolsCLI > > Please let me know the radar number, so I can take a look at those logs and keep an eye on the bug. I need to head home for the day now but I'll file this report first thing in the morning. I'm assuming you want the logs from before I install the command line tools manually? Cheers Adam From ghweber at lbl.gov Thu Jul 26 19:15:15 2012 From: ghweber at lbl.gov (Gunther H. Weber) Date: Thu, 26 Jul 2012 19:15:15 -0700 Subject: Uninstalling a port that won't build during port upgrade outdated Message-ID: <61F16390-C110-482E-8C3F-EE564DD29E00@lbl.gov> Hi, I am currently trying to upgrade my MacPorts install to Mountain Lion. Unfortunately qt4-mac does not seem to build. My plan was to upgrade everything else by uninstalling qt4-mac, i.e., typing "sudo port uninstall qt4-mac". However, even after I do this followed by a "sudo port clean --all qt4-mac", "sudo port upgrade outdated" will still try to upgrade qt4-mac. Is there anything that I am overlooking? If I type "sudo port -v uninstall qt4-mac" it claims that it is already uninstalled. Thanks, Gunther From ryandesign at macports.org Thu Jul 26 20:45:36 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 26 Jul 2012 22:45:36 -0500 Subject: Uninstalling a port that won't build during port upgrade outdated In-Reply-To: <61F16390-C110-482E-8C3F-EE564DD29E00@lbl.gov> References: <61F16390-C110-482E-8C3F-EE564DD29E00@lbl.gov> Message-ID: <4EB3D514-F52E-4EDA-8EC7-6E0B9C8FFCF0@macports.org> On Jul 26, 2012, at 21:15, Gunther H. Weber wrote: > Hi, > > I am currently trying to upgrade my MacPorts install to Mountain Lion. Unfortunately qt4-mac does not seem to build. My plan was to upgrade everything else by uninstalling qt4-mac, i.e., typing "sudo port uninstall qt4-mac". However, even after I do this followed by a "sudo port clean --all qt4-mac", "sudo port upgrade outdated" will still try to upgrade qt4-mac. Is there anything that I am overlooking? If I type "sudo port -v uninstall qt4-mac" it claims that it is already uninstalled. Sounds like you have successfully uninstalled qt4-mac, and that other ports that you want to upgrade require qt4-mac, therefore MacPorts is trying to build it. The build failure of qt4-mac on Mountain Lion is already recorded in our issue tracker. From nicos at macports.org Thu Jul 26 22:38:08 2012 From: nicos at macports.org (Nicolas Pavillon) Date: Fri, 27 Jul 2012 14:38:08 +0900 Subject: Texlive: kile do not find koma-script files In-Reply-To: <8D4F5135-611F-4991-A231-3BB88EBF554E@hotmail.com> References: <399338B3-2F57-4C76-A37B-D4F7D6954299@gmail.com> <8D4F5135-611F-4991-A231-3BB88EBF554E@hotmail.com> Message-ID: Hello, Good to know that you could find a way to solve your issue. Then, concerning your issue about classicthesis, I don't think it is anymore related to Macports, as you now use the TeXLive distribution. The present version of the package classicthesis (see http://www.ctan.org/tex-archive/macros/latex/contrib/classicthesis/) does not contain any file "classic-preamble.sty", which has been suppressed in recent versions of the package (see http://www.tex.ac.uk/tex-archive/macros/latex/contrib/classicthesis/CHANGES) with classicthesis-config.tex. You thus need to download an older version of the package or adapt your use to the new one. However, as already said, this not anymore related to any Macports' port. Cheers, Nicolas > Thanks for the clarifications Nicolas, > I am using kde4-kile @2.1.2_0 > > In these days I went a bit around in the installed kile files and I already had a look at what you pointed out. > Actually I first tried to manually change the kilestdtools.rc putting the correct path but this wasn't of any help. > I finally realize that in Preferences->Tools->Build are set all the path that kile will use when compiling (e.g. /opt/local/bin/pdflatex). > I set all these path like: /usr/local/texlive/2012/bin/x86_64-darwin/pdflatex > But it still do not find classicthesis-preamble.sty. Actually I cannot find it too! > >> From the start, kile installed with Macports is not supposed to use an external tex installation in /usr/local, and would use the one installed from Macports. > > Now I uninstall and re-install kile and I checked it: > > > > It seems pointing at the correct files. But when trying to use the classic thesis environment it still do not find classicthesis-preamble.sty. > I downloaded the classicthesis.zip but that file wasn't there.. Is there a link to directly download the missing file? > > Thanks, > Starla > > On Jul 25, 2012, at 4:56 PM, Nicolas Pavillon wrote: > >> Hello, >> >> Just to be sure, is it the port "kde4-kile" which is the newest one, or the port "kile", which is pretty old and still based on kde3 ? What I write below is mainly concerning kde4-kile, but may also be true for the older one. >> >> From the start, kile installed with Macports is not supposed to use an external tex installation in /usr/local, and would use the one installed from Macports. In the case kile points to this external installation (which can be checked in the menu Settings->System Check... ), it would mean that it is not a standard installation. >> >> This said, the main paths for kile are set in a file called kilestdtools.rc, which should be located in /opt/local/share/apps/kile/kilestdtools.rc for a standard prefix. The path to the tex install could be changed in there. However, a manual change in this file may be overwritten by an upgrade of the port when it occurs. >> >> Cheers, >> >> Nicolas >> >> On Jul 25, 2012, at 5:22 PM, Sara Buson wrote: >> >>> I must advise that I am quite a new user of MecPorts and not expert! >>> I recently installed TexLive2011. I then installed the kile editor compiling it by source and everything went fine. Despite this some days ago I run into issues with kile. It wasn't able to find any of the koma-script files. But those files were present as I see them in /usr/local/texlive/2012/texmf-dist/tex/latex/koma-script/ . Since I couldn't find any solution I decided to update from TexLive2011 to TexLive2012. I followed the simple instruction indicated here: http://tug.org/mactex/ . Installation successful but the .profile file was not updated, it still pointed to the old version of TexLive2011. The same for all the binaries in /opt/local/bin/ . I also removed the 2011 version but still they use the old version. >>> I changed manually the .profile putting the path to the 2012 version. >>> Now other editors that I have installed that using TexLive are working with the correct version (e.g. TexShop). >>> Despite this kile still doesn't work properly.. I guess it might have its own configuration files somewhere but I cannot find them. More, isn't there a way to make it update to a new version of TexLive when available? >>> I already lost several days on this problem, any suggestion would be very welcome. >>> >>> Thanks in advance, >>> Starla >>> >>> _______________________________________________ >>> macports-users mailing list >>> macports-users at lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo/macports-users >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From william at gallaf.net Fri Jul 27 06:24:52 2012 From: william at gallaf.net (William Gallafent) Date: Fri, 27 Jul 2012 14:24:52 +0100 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: References: Message-ID: On 26 July 2012 22:57, Adam Mercer wrote: > On Thu, Jul 26, 2012 at 11:31 AM, Jeremy Huddleston Sequoia >> Can you please file a bug report at http://bugreport.apple.com including: >> >> /var/log/system.log >> /var/log/install.log >> The output of otool -l /usr/bin/clang | grep uuid >> The output of pkgutil --lsbom com.apple.pkg.DeveloperToolsCLI >> >> Please let me know the radar number, so I can take a look at those logs and keep an eye on the bug. I've filed a report, ID 11973121, containing the above information! Let me know if you need any other info to help with the diagnosis! -- Bill Gallafent. From jwa at macports.org Fri Jul 27 08:03:48 2012 From: jwa at macports.org (Wahlstedt Jyrki) Date: Fri, 27 Jul 2012 18:03:48 +0300 Subject: Upgrading to Mountain Lion -- migration document changes? In-Reply-To: References: <38AF664E-48B5-4836-B861-B6A8356815BE@me.com> Message-ID: On 26.7.2012, at 16.24, Ryan Schmidt wrote: > > On Jul 26, 2012, at 07:41, William H. Magill wrote: > >> I am about to upgrade to Mountain Lion and I note that the Migration Document does not mention anything specifically about it. >> >> Are there any "differences" or particular "changes/gotchas" unique to Mountain Lion that need to be considered? > > Should be the same as before. Upgrade OS, upgrade Xcode, upgrade Xcode command line tools, accept Xcode license agreement (maybe?), rebuild all ports. > There may be a problem, though, due to the lack of 10.6SDK in Xcode 4.4. At least wxWidgets seems to require that (old Carbon 32-bit!), so maybe it's time to begin preparing for saying goodbye for some packages in ML. ! ! Jyrki Wahlstedt ! http://www.wahlstedt.fi/jyrki/ ! ! Our life is no dream; but it ought to become one and perhaps will. ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386 From ryandesign at macports.org Fri Jul 27 08:04:57 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 27 Jul 2012 10:04:57 -0500 Subject: Upgrading to Mountain Lion -- migration document changes? In-Reply-To: References: <38AF664E-48B5-4836-B861-B6A8356815BE@me.com> Message-ID: <40888BCE-A4CB-4F32-BB68-862B1EA82F2F@macports.org> On Jul 27, 2012, at 10:03, Wahlstedt Jyrki wrote: > > On 26.7.2012, at 16.24, Ryan Schmidt wrote: > >> >> On Jul 26, 2012, at 07:41, William H. Magill wrote: >> >>> I am about to upgrade to Mountain Lion and I note that the Migration Document does not mention anything specifically about it. >>> >>> Are there any "differences" or particular "changes/gotchas" unique to Mountain Lion that need to be considered? >> >> Should be the same as before. Upgrade OS, upgrade Xcode, upgrade Xcode command line tools, accept Xcode license agreement (maybe?), rebuild all ports. >> > There > may be a problem, though, due to the lack of 10.6SDK in Xcode 4.4. At least wxWidgets seems to require that (old Carbon 32-bit!), so maybe it's time to begin preparing for saying goodbye for some packages in ML. Really? No 10.6 SDK in Xcode 4.4? Not even optionally? I'm surprised. I thought there were previously SDKs for two older versions of the OS in addition to the current version. From allbery.b at gmail.com Fri Jul 27 08:07:46 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Fri, 27 Jul 2012 11:07:46 -0400 Subject: Upgrading to Mountain Lion -- migration document changes? In-Reply-To: <40888BCE-A4CB-4F32-BB68-862B1EA82F2F@macports.org> References: <38AF664E-48B5-4836-B861-B6A8356815BE@me.com> <40888BCE-A4CB-4F32-BB68-862B1EA82F2F@macports.org> Message-ID: On Fri, Jul 27, 2012 at 11:04 AM, Ryan Schmidt wrote: > On Jul 27, 2012, at 10:03, Wahlstedt Jyrki wrote: > > There > > may be a problem, though, due to the lack of 10.6SDK in Xcode 4.4. At > least wxWidgets seems to require that (old Carbon 32-bit!), so maybe it's > time to begin preparing for saying goodbye for some packages in ML. > > Really? No 10.6 SDK in Xcode 4.4? Not even optionally? I'm surprised. I > thought there were previously SDKs for two older versions of the OS in > addition to the current version. Xcode 4 changed that; 4.0-4.3 only provided SDKs for Lion and SL, not for Leopard. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremy at lavergne.gotdns.org Fri Jul 27 08:09:12 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Fri, 27 Jul 2012 11:09:12 -0400 Subject: Upgrading to Mountain Lion -- migration document changes? In-Reply-To: <40888BCE-A4CB-4F32-BB68-862B1EA82F2F@macports.org> References: <38AF664E-48B5-4836-B861-B6A8356815BE@me.com> <40888BCE-A4CB-4F32-BB68-862B1EA82F2F@macports.org> Message-ID: <704677D5-CF71-4DB0-B624-BAB8985CBA2E@lavergne.gotdns.org> > Really? No 10.6 SDK in Xcode 4.4? Not even optionally? I'm surprised. I thought there were previously SDKs for two older versions of the OS in addition to the current version. From my clean installed of xcode 4.4 and command line tools, these are in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs: * MacOSX10.7.sdk * MacOSX10.8.sdk Interestingly, the 10.6 Core Library is available (documentation) inside Xcode as a download--but no SDK in the non-documtation downloads. From face at CentosPrime.COM Fri Jul 27 09:34:20 2012 From: face at CentosPrime.COM (Chris Janton) Date: Fri, 27 Jul 2012 09:34:20 -0700 Subject: Mountain Lion (not server), Apache2, and MacPorts Message-ID: Just a little note. The Apache2 port is set up to use Apple provided infrastructure (in some cases) In the 'httpd-userdir.conf' file there are these 2 lines Include /private/etc/apache2/users/*.conf Include /private/etc/apache2/users/virtual_host_global.conf.virt Please note - the Mountain Lion install removes the contents of the directory /private/etc/apache2/users so if you counted on those configuration files working for you, oops. I'm going to move mine to a better place, out of the way of Apple's steam roller ;-) It might be time to look at the modification to the apache distribution. I do not know what ML Server does, so it may just be a matter of keeping abreast of the changes. 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From jeremyhu at macports.org Fri Jul 27 09:41:58 2012 From: jeremyhu at macports.org (Jeremy Huddleston Sequoia) Date: Fri, 27 Jul 2012 09:41:58 -0700 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: References: Message-ID: I'm curious if this is still happening. If anyone sees this issue when initiating the install from XCode's preferences (*after* this email), please let me know. --Jeremy On Jul 27, 2012, at 6:24 AM, William Gallafent wrote: > On 26 July 2012 22:57, Adam Mercer wrote: >> On Thu, Jul 26, 2012 at 11:31 AM, Jeremy Huddleston Sequoia >>> Can you please file a bug report at http://bugreport.apple.com including: >>> >>> /var/log/system.log >>> /var/log/install.log >>> The output of otool -l /usr/bin/clang | grep uuid >>> The output of pkgutil --lsbom com.apple.pkg.DeveloperToolsCLI >>> >>> Please let me know the radar number, so I can take a look at those logs and keep an eye on the bug. > > I've filed a report, ID 11973121, containing the above information! > > Let me know if you need any other info to help with the diagnosis! > > -- > Bill Gallafent. From sean.michael.farley at gmail.com Fri Jul 27 09:43:41 2012 From: sean.michael.farley at gmail.com (Sean Farley) Date: Fri, 27 Jul 2012 11:43:41 -0500 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: References: Message-ID: > I'm curious if this is still happening. If anyone sees this issue when initiating the install from XCode's preferences (*after* this email), please let me know. I can try later this afternoon, if not before and let you (and the list) know. From mdbecque at gmail.com Fri Jul 27 09:52:31 2012 From: mdbecque at gmail.com (M. Daniel Becque) Date: Fri, 27 Jul 2012 11:52:31 -0500 Subject: More than one version Message-ID: As I was trying to understand a universal build I built a few ports again as universal. No sense on my machine and for example when I do a *port list installed* I get three versions of boehmgc all with the same version number, @7.2c. When I do *port list inactive* I get 2 versions of the same but no way to tell which is which. If I do *su**do port install boehmg**c*, macports understands and deactivates the universal build and activates the ppc build. Now, how do I tell macports to uninstall the inactive versionsand tell them apart in a listing? I might have gotten it wrong when i tried the -u option with install but before i go on and make a further mess I thought that I would ask the group. Thanks in advance, dan -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremy at lavergne.gotdns.org Fri Jul 27 09:54:35 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Fri, 27 Jul 2012 12:54:35 -0400 Subject: More than one version In-Reply-To: References: Message-ID: <67A31965-044C-44D4-9607-6FEDC7EA4313@lavergne.gotdns.org> > As I was trying to understand a universal build I built a few ports again as universal. No sense on my machine and for example when I do a port list installed I get three versions of boehmgc all with the same version number, @7.2c. When I do port list inactive I get 2 versions of the same but no way to tell which is which. If I do sudo port install boehmgc, macports understands and deactivates the universal build andactivates the ppc build. Now, how do I tell macports to uninstall the inactive versions and tell them apart in a listing? I might have gotten it wrong when i tried the -u option with install but before i go on and make a further mess I thought that I would ask the group. port echo gets you information for that specific instance of a port. port list gets you information about the current port. running `port list installed` will show you the same information repeated for each port because it's pulling the current version's info only. From mdbecque at gmail.com Fri Jul 27 10:01:40 2012 From: mdbecque at gmail.com (M. Daniel Becque) Date: Fri, 27 Jul 2012 12:01:40 -0500 Subject: More than one version In-Reply-To: <67A31965-044C-44D4-9607-6FEDC7EA4313@lavergne.gotdns.org> References: <67A31965-044C-44D4-9607-6FEDC7EA4313@lavergne.gotdns.org> Message-ID: Ah ha! Now I see. Thanks On Fri, Jul 27, 2012 at 11:54 AM, Jeremy Lavergne < jeremy at lavergne.gotdns.org> wrote: > > As I was trying to understand a universal build I built a few ports > again as universal. No sense on my machine and for example when I do a port > list installed I get three versions of boehmgc all with the same version > number, @7.2c. When I do port list inactive I get 2 versions of the same > but no way to tell which is which. If I do sudo port install boehmgc, > macports understands and deactivates the universal build andactivates the > ppc build. Now, how do I tell macports to uninstall the inactive versions > and tell them apart in a listing? I might have gotten it wrong when i tried > the -u option with install but before i go on and make a further mess I > thought that I would ask the group. > > port echo gets you information for that specific instance of a port. > port list gets you information about the current port. > > running `port list installed` will show you the same information repeated > for each port because it's pulling the current version's info only. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From deric at macports.org Fri Jul 27 15:06:33 2012 From: deric at macports.org (Daniel Ericsson) Date: Sat, 28 Jul 2012 00:06:33 +0200 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: References: Message-ID: <0841F81B-200F-4202-8371-7B7A46B5BDAF@macports.org> On 27 jul 2012, at 18:41, Jeremy Huddleston Sequoia wrote: > I'm curious if this is still happening. If anyone sees this issue when initiating the install from XCode's preferences (*after* this email), please let me know. Just now installed Xcode 4.4 from MAS and Command Line Tools from Xcode Preferences on a 10.7.4 machine and /usr/bin/clang is still at 3.1. -- Daniel From deric at macports.org Fri Jul 27 15:48:00 2012 From: deric at macports.org (Daniel Ericsson) Date: Sat, 28 Jul 2012 00:48:00 +0200 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: References: Message-ID: <741F8C64-813F-42BB-9E84-CB303C5F78B1@macports.org> On 26 jul 2012, at 23:57, Adam Mercer wrote: > On Thu, Jul 26, 2012 at 11:31 AM, Jeremy Huddleston Sequoia > wrote: > >> I'd be interested in hearing "me too"s or "works for me"s from others on 10.7 installing through XCode (as opposed to ML users or those going to connect.apple.com) to find out if this is a 1-off issue or something others are seeing. > > Just encountered this on another Lion machine, updating from > Xcode-4.3.3. One thing I noticed is that the installation of the > command line tools started at 70% complete, as if it didn't download > the tools and just used the previous installer. Noticing this as well I solved it as described below: 1. ~/Library/Caches/com.apple.dt.Xcode/Downloads deric at cyclone> ls -l total 2313840 -rw-r--r-- 1 deric staff 8069 Mar 8 18:10 58b716ff5428f7961e1403e6d969e605d0f27eaf.dvtdownloadableindex -rw-r--r--@ 1 deric staff 171668418 Feb 29 14:01 Xcode.CLTools.10.7-1.1.dmg -rw-r--r--@ 1 deric staff 180040642 Mar 16 22:12 Xcode.CLTools.10.7-1.2.dmg -rw-r--r--@ 1 deric staff 154619824 Jun 16 19:05 Xcode.CLTools.10.7-1.3.1.dmg -rw-r--r--@ 1 deric staff 180040642 Apr 16 14:18 Xcode.CLTools.10.7-1.3.dmg -rw-r--r--@ 1 deric staff 416569 Mar 18 23:55 Xcode.SDK.iPhoneSimulator.4.3-4.3.1.dmg -rw-r--r--@ 1 deric staff 497845832 Mar 18 23:53 Xcode.SDK.iPhoneSimulator.4.3-4.3.dmg -rw-r--r-- 1 deric staff 11349 Jul 27 23:42 eded78df8bfabaf6560841d10cf8e53766f74f28.dvtdownloadableindex -rw-r--r-- 1 deric staff 8486 Jul 22 16:14 f7133e82a08bdb4ebf724f16beed2bbac2a265cf.dvtdownloadableindex -rw-r--r-- 1 deric staff 7930 Jul 27 16:12 f9556a99100ac5200138e50480d2471b6bdc4adc.dvtdownloadableindex ~/Library/Caches/com.apple.dt.Xcode/Downloads deric at cyclone> rm Xcode.CLTools.10.7-1* 2. Used left-over (from Xcode 4.2 installs) /Library/Developer/Shared/uninstall-devtools to uninstall CLT, this script uninstalls itself as well when it's done. deric at cyclone> sudo /Library/Developer/Shared/uninstall-devtools --mode=unixdev 3. Reinstalled CLT from Xcode Preferences. 4. deric at cyclone> /usr/bin/clang --version Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn) Target: x86_64-apple-darwin11.4.0 Thread model: posix -- Daniel From jack at netgate.net Fri Jul 27 18:42:45 2012 From: jack at netgate.net (Jack Repenning) Date: Fri, 27 Jul 2012 18:42:45 -0700 Subject: How do I know why I have a port? Message-ID: Sometimes, I notice I have some port installed that I have no conscious interest in. I'm sure it's there because it's depended upon by some other port that I do care about (or recursively), but is there some way I can find out what that would be? I see that "port info whatever" tells me what stuff "whatever" depends upon, but I want the inverse of that. <>< Jack Repenning From jeremy at lavergne.gotdns.org Fri Jul 27 18:44:43 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Fri, 27 Jul 2012 21:44:43 -0400 Subject: How do I know why I have a port? In-Reply-To: References: Message-ID: > Sometimes, I notice I have some port installed that I have no conscious interest in. I'm sure it's there because it's depended upon by some other port that I do care about (or recursively), but is there some way I can find out what that would be? > > I see that "port info whatever" tells me what stuff "whatever" depends upon, but I want the inverse of that. port info will include the info of: port depends x the reverse is: port dependents x you can also use this as a pseudo port: port echo depof:x port echo rdepof:x From ryandesign at macports.org Fri Jul 27 19:21:03 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 27 Jul 2012 21:21:03 -0500 Subject: How do I know why I have a port? In-Reply-To: References: Message-ID: <76E42B21-6A15-4731-9A64-C096673BFA72@macports.org> On Jul 27, 2012, at 20:42, Jack Repenning wrote: > Sometimes, I notice I have some port installed that I have no conscious interest in. I'm sure it's there because it's depended upon by some other port that I do care about (or recursively), but is there some way I can find out what that would be? > > I see that "port info whatever" tells me what stuff "whatever" depends upon, but I want the inverse of that. One way of handling this problem is to just try uninstalling the port. If anything depends on it, MacPorts will prevent you from uninstalling it and will tell you why. From ryandesign at macports.org Fri Jul 27 19:22:24 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 27 Jul 2012 21:22:24 -0500 Subject: More than one version In-Reply-To: <67A31965-044C-44D4-9607-6FEDC7EA4313@lavergne.gotdns.org> References: <67A31965-044C-44D4-9607-6FEDC7EA4313@lavergne.gotdns.org> Message-ID: On Jul 27, 2012, at 11:54, Jeremy Lavergne wrote: >> As I was trying to understand a universal build I built a few ports again as universal. No sense on my machine and for example when I do a port list installed I get three versions of boehmgc all with the same version number, @7.2c. When I do port list inactive I get 2 versions of the same but no way to tell which is which. If I do sudo port install boehmgc, macports understands and deactivates the universal build andactivates the ppc build. Now, how do I tell macports to uninstall the inactive versions and tell them apart in a listing? I might have gotten it wrong when i tried the -u option with install but before i go on and make a further mess I thought that I would ask the group. > > port echo gets you information for that specific instance of a port. > port list gets you information about the current port. > > running `port list installed` will show you the same information repeated for each port because it's pulling the current version's info only. As explained in the FAQ: https://trac.macports.org/wiki/FAQ#portlist You want "port installed", "port installed inactive", etc. From ryandesign at macports.org Fri Jul 27 19:24:44 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 27 Jul 2012 21:24:44 -0500 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: References: Message-ID: On Jul 26, 2012, at 12:04, Ryan Schmidt wrote: > "Me too". New machine, OS X 10.7.4. Installed Xcode 4.3.3 from App Store a week ago, installed command line tools from Preferences > Downloads. Yesterday updated to Xcode 4.4 from App Store, (re)installed command line tools from Preferences > Downloads. Confirmed mismatched clang versions as OP reported. FYI, upgrading to OS X 10.8.0 Mountain Lion removed the command line tools and Xcode > Preferences > Downloads again offered me an Install button for them. Clicking it did the right thing and I now have clang 4.0 in /usr/bin. From jamiepaulG at gmail.com Fri Jul 27 23:51:58 2012 From: jamiepaulG at gmail.com (Jamie Paul Griffin) Date: Sat, 28 Jul 2012 07:51:58 +0100 Subject: Oddity using Xcode 4.4 on OS 10.7. In-Reply-To: <0841F81B-200F-4202-8371-7B7A46B5BDAF@macports.org> References: <0841F81B-200F-4202-8371-7B7A46B5BDAF@macports.org> Message-ID: <20120728065158.GA7676@macmini.kode5.net> On Sat, Jul 28, 2012 at 12:06:33AM +0200, Daniel Ericsson wrote: > On 27 jul 2012, at 18:41, Jeremy Huddleston Sequoia wrote: > > > I'm curious if this is still happening. If anyone sees this issue when initiating the install from XCode's preferences (*after* this email), please let me know. > > Just now installed Xcode 4.4 from MAS and Command Line Tools from Xcode Preferences on a 10.7.4 machine and /usr/bin/clang is still at 3.1. > > -- Daniel I had no issues with the upgrade of Xcode and installation of the command-line tools. When I started the newer version for the first time it offered a "Move to Trash" button to discard the older versions, which I did. Then just installed the command-line tools from Preferences -> Downloads: ~ $ /usr/bin/clang --version Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn) Target: x86_64-apple-darwin11.4.0 Thread model: posix jamie From heapifyman at gmail.com Sat Jul 28 04:19:22 2012 From: heapifyman at gmail.com (heapifyman) Date: Sat, 28 Jul 2012 13:19:22 +0200 Subject: [git] turn off localization Message-ID: Hello, is there a way to turn off localization for a specific port? In my case git output on the command line is in German but I would like to have the original English output. How do I do that? Delete the file /opt/local/share/locale/de/LC_MESSAGES/git.mo ? Thanks in advance for any help. -------------- next part -------------- An HTML attachment was scrubbed... URL: From allbery.b at gmail.com Sat Jul 28 07:17:24 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Sat, 28 Jul 2012 10:17:24 -0400 Subject: How do I know why I have a port? In-Reply-To: References: Message-ID: On Fri, Jul 27, 2012 at 9:42 PM, Jack Repenning wrote: > Sometimes, I notice I have some port installed that I have no conscious > interest in. I'm sure it's there because it's depended upon by some other > port that I do care about (or recursively), but is there some way I can > find out what that would be? > One way to check this *without* seeing what installed it: port echo leaves # or: port installed leaves will show all ports which were installed as dependencies, but are no longer needed. (See also "port setrequested".) -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From cal at macports.org Sat Jul 28 07:33:38 2012 From: cal at macports.org (Clemens Lang) Date: Sat, 28 Jul 2012 16:33:38 +0200 Subject: [git] turn off localization In-Reply-To: References: Message-ID: <20120728143338.GA4076@towel.neverpanic.de> On Sat, Jul 28, 2012 at 01:19:22PM +0200, heapifyman wrote: > is there a way to turn off localization for a specific port? In my > case git output on the command line is in German but I would like to > have the original English output. Why don't you just export LC_MESSAGES=en_US.UTF-8 or LANG=en_US.UTF-8 to switch your terminal output to english? You could also write a wrapper for git to do this, if you want to keep your other messages in german. > How do I do that? Delete the file > /opt/local/share/locale/de/LC_MESSAGES/git.mo ? Doing that might lead to warnings and problems when trying to uninstall or upgrade git. -- Clemens Lang From fritzs at gmx.net Sat Jul 28 11:13:56 2012 From: fritzs at gmx.net (FritzS - gmx) Date: Sat, 28 Jul 2012 20:13:56 +0200 Subject: some port outdated could not upgrade Message-ID: <7BE58F70-6A6D-4666-8B3C-B8B1CC4D0936@gmx.net> Hi, I run macports under Mountain Lion an had some errors. pan2 runs now, but if I run port outdated it comes a large list port outdated The following installed ports are outdated: attica 0.4.0_0 < 0.4.0_0 (platform darwin 11 != darwin 12) audiofile 0.3.4_0 < 0.3.4_0 (platform darwin 11 != darwin 12) automoc 0.9.88_3 < 0.9.88_3 (platform darwin 11 != darwin 12) avahi 0.6.31_2 < 0.6.31_2 (platform darwin 11 != darwin 12) babl 0.1.10_0 < 0.1.10_0 (platform darwin 11 != darwin 12) bison 2.5.1_0 < 2.6_0 boehmgc 7.1_2 < 7.2c_0 ...... What should I do? My tickets #35364: some applications want run #35356: macports won't work after upgrade to MountainLion -- FritzS fritzs at gmx.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremy at lavergne.gotdns.org Sat Jul 28 11:17:17 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Sat, 28 Jul 2012 14:17:17 -0400 Subject: some port outdated could not upgrade In-Reply-To: <7BE58F70-6A6D-4666-8B3C-B8B1CC4D0936@gmx.net> References: <7BE58F70-6A6D-4666-8B3C-B8B1CC4D0936@gmx.net> Message-ID: <990A566B-8C7D-4B97-8738-5E37755FCA24@lavergne.gotdns.org> > I run macports under Mountain Lion an had some errors. > pan2 runs now, but if I run port outdated it comes a large list > > port outdated > The following installed ports are outdated: > attica 0.4.0_0 < 0.4.0_0 (platform darwin 11 != darwin 12) > audiofile 0.3.4_0 < 0.3.4_0 (platform darwin 11 != darwin 12) > automoc 0.9.88_3 < 0.9.88_3 (platform darwin 11 != darwin 12) > avahi 0.6.31_2 < 0.6.31_2 (platform darwin 11 != darwin 12) > babl 0.1.10_0 < 0.1.10_0 (platform darwin 11 != darwin 12) > bison 2.5.1_0 < 2.6_0 > boehmgc 7.1_2 < 7.2c_0 > ...... > > What should I do? > > My tickets > #35364: some applications want run > #35356: macports won't work after upgrade to MountainLion http://trac.macports.org/wiki/Migration From murrayeisenberg at gmail.com Sat Jul 28 12:14:40 2012 From: murrayeisenberg at gmail.com (Murray Eisenberg) Date: Sat, 28 Jul 2012 15:14:40 -0400 Subject: Oddity using Xcode 4.4 on OS 10.7 [Digest, Vol 71, Issue 27] In-Reply-To: References: Message-ID: <50143A20.8080304@gmail.com> On 7/28/12 3:00 PM, Jamie Paul Griffin wrote: > > > On Sat, Jul 28, 2012 at 12:06:33AM +0200, Daniel Ericsson wrote: >> >On 27 jul 2012, at 18:41, Jeremy Huddleston Sequoia wrote: >> > >>> > >I'm curious if this is still happening. If anyone sees this issue when initiating the install from XCode's preferences (*after* this email), please let me know. >> > >> >Just now installed Xcode 4.4 from MAS and Command Line Tools from Xcode Preferences on a 10.7.4 machine and /usr/bin/clang is still at 3.1. >> > >> >-- Daniel > I had no issues with the upgrade of Xcode and installation of the > command-line tools. When I started the newer version for the first time > it offered a "Move to Trash" button to discard the older versions, which > I did. Then just installed the command-line tools from Preferences -> > Downloads: > > ~ $ /usr/bin/clang --version > Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM > 3.1svn) > Target: x86_64-apple-darwin11.4.0 > Thread model: posix > > jamie I'm not getting clang version 4.0 under OS X 10.7.4 even after installing Xcode 4.4 and explicitly using the Xcode Preferences > Downloads > Components pane to install the Command Line Tools. In fact, after I did that and it said the tools were installed, not only did /usr/bin/clang --version still show the old version 3.1, but when I reopened Xcode and its preferences, it did not show the Command Line Tools as installed, but rather had an Install button still. Something isn't working correctly. -- Murray Eisenberg murrayeisenberg at gmail.com 80 Fearing Street phone 413 549-1020 (H) Amherst, MA 01002-1912 From murrayeisenberg at gmail.com Sat Jul 28 12:24:25 2012 From: murrayeisenberg at gmail.com (Murray Eisenberg) Date: Sat, 28 Jul 2012 15:24:25 -0400 Subject: Fwd: Re: Oddity using Xcode 4.4 on OS 10.7 [Digest, Vol 71, Issue 27] In-Reply-To: <50143A20.8080304@gmail.com> References: <50143A20.8080304@gmail.com> Message-ID: <50143C69.8040406@gmail.com> I located a solution to the problem of Xcode 4.4 command-line tools not correctly installing under OS X 10.7.4. This was given in: https://discussions.apple.com/message/19035850#19035850 The solution is to do a direct download of the Xcode 4.4 command-line tools for Lion from: https://developer.apple.com/downloads/index.action?=command%20line%20tools# And after mounting the downloaded .dmg and installing the pkg it contains, now Xcode preferences does persistently show the command-line tools as having been installed. Still -- strange! -------- Original Message -------- Subject: Re: Oddity using Xcode 4.4 on OS 10.7 [Digest, Vol 71, Issue 27] Date: Sat, 28 Jul 2012 15:14:40 -0400 From: Murray Eisenberg To: macports-users at lists.macosforge.org On 7/28/12 3:00 PM, Jamie Paul Griffin wrote: > > > On Sat, Jul 28, 2012 at 12:06:33AM +0200, Daniel Ericsson wrote: >> >On 27 jul 2012, at 18:41, Jeremy Huddleston Sequoia wrote: >> > >>> > >I'm curious if this is still happening. If anyone sees this issue when initiating the install from XCode's preferences (*after* this email), please let me know. >> > >> >Just now installed Xcode 4.4 from MAS and Command Line Tools from Xcode Preferences on a 10.7.4 machine and /usr/bin/clang is still at 3.1. >> > >> >-- Daniel > I had no issues with the upgrade of Xcode and installation of the > command-line tools. When I started the newer version for the first time > it offered a "Move to Trash" button to discard the older versions, which > I did. Then just installed the command-line tools from Preferences -> > Downloads: > > ~ $ /usr/bin/clang --version > Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM > 3.1svn) > Target: x86_64-apple-darwin11.4.0 > Thread model: posix > > jamie I'm not getting clang version 4.0 under OS X 10.7.4 even after installing Xcode 4.4 and explicitly using the Xcode Preferences > Downloads > Components pane to install the Command Line Tools. In fact, after I did that and it said the tools were installed, not only did /usr/bin/clang --version still show the old version 3.1, but when I reopened Xcode and its preferences, it did not show the Command Line Tools as installed, but rather had an Install button still. Something isn't working correctly. -- Murray Eisenberg murrayeisenberg at gmail.com 80 Fearing Street phone 413 549-1020 (H) Amherst, MA 01002-1912 From comer.duncan at gmail.com Sat Jul 28 12:52:00 2012 From: comer.duncan at gmail.com (Comer Duncan) Date: Sat, 28 Jul 2012 15:52:00 -0400 Subject: Mountain Lion? Message-ID: I am wondering what are the implications of the OSX Mountain Lion for MacPorts? With the removal of X11 support, is there going to be any problems with building code? Can those who know please clue me in? Thanks for all the great software MacPorts produces!! Comer Duncan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Sat Jul 28 12:53:05 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 28 Jul 2012 14:53:05 -0500 Subject: Mountain Lion? In-Reply-To: References: Message-ID: On Jul 28, 2012, at 14:52, Comer Duncan wrote: > I am wondering what are the implications of the OSX Mountain Lion for MacPorts? With the removal of X11 support, is there going to be any problems with building code? Can those who know please clue me in? MacPorts works fine on Mountain Lion. If you want X11, you can install XQuartz or the xorg-server port. From rlhamil at smart.net Sat Jul 28 18:29:11 2012 From: rlhamil at smart.net (Richard L. Hamilton) Date: Sat, 28 Jul 2012 21:29:11 -0400 Subject: [git] turn off localization In-Reply-To: References: Message-ID: The usual way of communicating the desired locale, certainly for command-line programs, is by setting appropriate environment variables. The lowest priority (overridden by any of the others where they conflict) is LANG, which applies to all categories of locale information not set with one of the other environment variables. Then there are category-specific environment variables: LC_COLLATE collation sequence LC_CTYPE character classification LC_MESSAGES message text LD_MONETARY currency symbol and notation LC_NUMERIC preferred separator and decimal character LC_TIME preferred date and time formats and finally, all of the above can be overridden with LC_ALL Thus, if I start with sh-3.2$ locale LANG="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_CTYPE="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_ALL= but wish to run some single command and its descendants (in place of the locale command below) in another locale: sh-3.2$ env LC_ALL=en_US.UTF-8 locale LANG="de_DE.UTF-8" LC_COLLATE="en_US.UTF-8" LC_CTYPE="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_ALL="en_US.UTF-8" On Jul 28, 2012, at 7:19 AM, heapifyman wrote: > Hello, > > is there a way to turn off localization for a specific port? In my case git output on the command line is in German but I would like to have the original English output. > How do I do that? Delete the file /opt/local/share/locale/de/LC_MESSAGES/git.mo ? > > Thanks in advance for any help. > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users -- eMail: mailto:rlhamil at smart.net Home page: http://www.smart.net/~rlhamil/ Facebook, MySpace, AIM, Yahoo, etc: ask -------------- next part -------------- An HTML attachment was scrubbed... URL: From allbery.b at gmail.com Sat Jul 28 18:32:01 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Sat, 28 Jul 2012 21:32:01 -0400 Subject: [git] turn off localization In-Reply-To: References: Message-ID: On Sat, Jul 28, 2012 at 9:29 PM, Richard L. Hamilton wrote: > The usual way of communicating the desired locale, certainly for > command-line programs, is by setting appropriate environment variables. > The lowest priority (overridden by any of the others where they conflict) > is LANG, which applies to all categories of locale information not set with > one of the other environment variables. Then there are category-specific > environment variables: > LC_COLLATE collation sequence > LC_CTYPE character classification > LC_MESSAGES message text > LD_MONETARY currency symbol and notation > LC_NUMERIC preferred separator and decimal character > LC_TIME preferred date and time formats > You could use aliases to automate this... $ alias git='env LC_ALL=C /opt/local/bin/git' -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From iandw.au at gmail.com Sat Jul 28 21:08:07 2012 From: iandw.au at gmail.com (Ian Wadham) Date: Sun, 29 Jul 2012 14:08:07 +1000 Subject: CMake log needed to help find a bug In-Reply-To: References: Message-ID: <4767BA22-F4C2-4CC0-9340-D5C20C0E4632@gmail.com> On 26/07/2012, at 12:40 PM, Ryan Schmidt wrote: > On Jul 25, 2012, at 19:37, Ian Wadham wrote: > >> I reported a problem with kdelibs4 @4.8.2_0 failing to detect compiler characteristics >> correctly, see https://trac.macports.org/ticket/34605?replyto=1#comment and also >> https://bugs.kde.org/show_bug.cgi?id=300429 >> >> A KDE developer has responded to the latter report and he has asked for logs of >> CMake output from my Macports build of kdelibs4 @4.8.2_0. How do I get this? >> >> AFAICS the Macports logs are deleted after a successful build. So must I do: >> >> sudo port uninstall kdelibs4 @4.8.2_0 >> sudo port -k install kdelibs4 @4.8.2_0 >> >> ...? And if I do, how do I find the logs? And how do I find the logs I want amongst >> all the other logs? > > The command "port logfile kdelibs4" shows you where the kdelibs4 logfile is located. Thanks, Ryan. I also found I needed "port log --phase configure kdelibs4" to extract the CMake output. Cheers, Ian W. From iandw.au at gmail.com Sat Jul 28 21:35:58 2012 From: iandw.au at gmail.com (Ian Wadham) Date: Sun, 29 Jul 2012 14:35:58 +1000 Subject: How to set C++ compiler outside Macports? Message-ID: I think I have got to the bottom of the problem I have been having when I tried to compile and build some of my own source code, but linking to the kdelibs4 @4.8.2_0 library from Macports. See: https://trac.macports.org/ticket/34605?replyto=1#comment The question now is "What is the best thing to do about it?". The Macports logs tell me that kdelibs4 has been compiled with clang. KDE embeds this knowledge in some CMake macros it generates. In a Linux installation, that is fine because you will use the same compiler both for building KDE and for doing your own development. There is not a lot of choice. In my Mac OS X environment, /usr/bin/c++ is a symbolic link to llvm-g++-4.2, but I need it to be to the same compiler as Macports used to build kdelibs4. Then I can compile and link my own code correctly with that library and continue developing and testing my source code for the next release of KDE. For the moment, I have found that "brute force" linking of /usr/bin/c++ to clang works fine, but is there a safer way? Is there, for example, some way (e.g. a script or command) to extract from Macports the compiler it used and make it a symbol in my own builds? Thanks in advance, Ian W. From jeremyhu at macports.org Sat Jul 28 22:43:33 2012 From: jeremyhu at macports.org (Jeremy Huddleston Sequoia) Date: Sat, 28 Jul 2012 22:43:33 -0700 Subject: How to set C++ compiler outside Macports? In-Reply-To: References: Message-ID: <04B03595-6682-44A5-8877-BE7F0BFB8E0C@macports.org> On Jul 28, 2012, at 21:35, Ian Wadham wrote: > I think I have got to the bottom of the problem I have been having > when I tried to compile and build some of my own source code, but > linking to the kdelibs4 @4.8.2_0 library from Macports. See: > https://trac.macports.org/ticket/34605?replyto=1#comment > > The question now is "What is the best thing to do about it?". The > Macports logs tell me that kdelibs4 has been compiled with clang. > > KDE embeds this knowledge in some CMake macros it generates. > > In a Linux installation, that is fine because you will use the same > compiler both for building KDE and for doing your own development. > There is not a lot of choice. > > In my Mac OS X environment, /usr/bin/c++ is a symbolic link to > llvm-g++-4.2, but I need it to be to the same compiler as Macports > used to build kdelibs4. Then I can compile and link my own code > correctly with that library and continue developing and testing my > source code for the next release of KDE. Why are you using /usr/bin/c++? Just use /usr/bin/clang++ (or 'xcrun clang++' if you didn't install the command line tools). > For the moment, I have found that "brute force" linking of /usr/bin/c++ > to clang works fine, but is there a safer way? Is there, for example, > some way (e.g. a script or command) to extract from Macports the > compiler it used and make it a symbol in my own builds? You can look at the build logs to see what compiler is used, but on anything recent will be using clang. > Thanks in advance, Ian W. --Jeremy From iandw.au at gmail.com Sat Jul 28 23:35:58 2012 From: iandw.au at gmail.com (Ian Wadham) Date: Sun, 29 Jul 2012 16:35:58 +1000 Subject: How to set C++ compiler outside Macports? In-Reply-To: <04B03595-6682-44A5-8877-BE7F0BFB8E0C@macports.org> References: <04B03595-6682-44A5-8877-BE7F0BFB8E0C@macports.org> Message-ID: On 29/07/2012, at 3:43 PM, Jeremy Huddleston Sequoia wrote: > On Jul 28, 2012, at 21:35, Ian Wadham wrote: >> In my Mac OS X environment, /usr/bin/c++ is a symbolic link to >> llvm-g++-4.2, but I need it to be to the same compiler as Macports >> used to build kdelibs4. Then I can compile and link my own code >> correctly with that library and continue developing and testing my >> source code for the next release of KDE. > > Why are you using /usr/bin/c++? Just use /usr/bin/clang++ (or 'xcrun clang++' if you didn't install the command line tools). It's not that simple. I never use a compiler directly, just CMake initially, including all the KDE macros and dependencies, then "make" on later runs. CMake picks up /usr/bin/c++, by default, but could no doubt be made to do something else. >> For the moment, I have found that "brute force" linking of /usr/bin/c++ >> to clang works fine, but is there a safer way? Is there, for example, >> some way (e.g. a script or command) to extract from Macports the >> compiler it used and make it a symbol in my own builds? > > You can look at the build logs to see what compiler is used, but on anything recent will be using clang. By default, Macports does not leave logs behind. I was looking perhaps for some Macports cache or config file where compiler assignments are kept for each port or for ports in general, but have been unable to find any. Is use of clang now official Macports policy? Last I heard on this list, a few months back, its use was experimental. Cheers, Ian W. From david at mso.anu.edu.au Sun Jul 29 02:47:02 2012 From: david at mso.anu.edu.au (David Nicholls) Date: Sun, 29 Jul 2012 19:47:02 +1000 Subject: py27-spyder fails to build on Mountain Lion Message-ID: <2B8E9704-6C7F-4D77-B555-51803F581FFE@mso.anu.edu.au> Following exactly the "maintenance" instructions on the Macports website for upgrading to a new OS, and attempting to install py27-spyder (v 2.1.10), I get the following: Error: org.macports.build for port py27-pyobjc returned: command execution failed Error: Failed to install py27-pyobjc Please see the log file for port py27-pyobjc for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py27-pyobjc/py27-pyobjc/main.log Error: The following dependencies were not installed: py27-spyder py27-matplotlib py27-pyobjc-cocoa py27-pyobjc py27-tkinter tk Xft2 fontconfig xrender xorg-libX11 xorg-bigreqsproto xorg-inputproto xorg-kbproto xorg-libXau xorg-xproto xorg-libXdmcp xorg-libxcb xorg-libpthread-stubs xorg-xcb-proto xorg-xcmiscproto xorg-xextproto xorg-xf86bigfontproto xorg-xtrans xorg-renderproto tcl xorg-libXScrnSaver xorg-libXext autoconf help2man p5.12-locale-gettext m4 automake libtool xorg-util-macros xorg-scrnsaverproto py27-pep8 pep8_select py27-pil lcms tiff jpeg py27-pyflakes pyflakes_select py27-pyqt4 py27-sip qt4-mac dbus libmng py27-rope py27-scipy SuiteSparse gcc45 cctools cctools-headers ld64 dyld-headers libunwind-headers llvm-3.1 llvm_select gcc_select gmp libmpc mpfr ppl glpk swig-python bison gsed swig pcre py27-sphinx py27-docutils py27-roman py27-jinja2 py27-markupsafe py27-pygments sphinx_select To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port py-spyder failed I have logged a ticket #35399 (as dcn at dcnicholls.com) including the log file. Before I attempted this exercise, py-spyder worked perfectly well, but Macports reported a series of outdated ports (though not reported under Lion immediately before the OS upgrade). I propose to copy the (safe) old /opt/local folder back so that I can continue to use py-spyder. DN __________ Research School of Astronomy & Astrophysics Mt Stromlo Observatory Australian National University From fritzs at gmx.net Sun Jul 29 04:17:55 2012 From: fritzs at gmx.net (FritzS - gmx) Date: Sun, 29 Jul 2012 13:17:55 +0200 Subject: Computing dependencies for gimp - Error: Dependency 'XviD' not found Message-ID: <418E5B10-44EA-4E8E-8EAB-BDEDDE0B58F8@gmx.net> Hi macports team, I deinstalled all my previous packages and reinstall pan2, putty But with gimp gives a problem: sudo port install gimp ---> Computing dependencies for gimp Error: Dependency 'XviD' not found. To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port gimp failed sudo port install gimp2 ---> Computing dependencies for gimp2 Error: Dependency 'XviD' not found. To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port gimp2 failed sudo port install XviD Error: Port XviD not found But here is XviD listened https://trac.macports.org/browser/trunk/dports/multimedia/XviD PS: You could close my tickets #35364: some applications want run #35356: macports won't work after upgrade to MountainLion -- FritzS fritzs at gmx.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From fritzs at gmx.net Sun Jul 29 04:35:49 2012 From: fritzs at gmx.net (FritzS - gmx) Date: Sun, 29 Jul 2012 13:35:49 +0200 Subject: Computing dependencies for gimp - Error: Dependency 'XviD' not found In-Reply-To: <418E5B10-44EA-4E8E-8EAB-BDEDDE0B58F8@gmx.net> References: <418E5B10-44EA-4E8E-8EAB-BDEDDE0B58F8@gmx.net> Message-ID: <63EE50E2-4216-4AF1-9891-737F484E1C67@gmx.net> Am 29.07.2012 um 13:17 schrieb FritzS - gmx : > Hi macports team, > I deinstalled all my previous packages and reinstall pan2, putty > > But with gimp gives a problem: > > sudo port install gimp > ---> Computing dependencies for gimp > Error: Dependency 'XviD' not found. > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port gimp failed > > sudo port install gimp2 > ---> Computing dependencies for gimp2 > Error: Dependency 'XviD' not found. > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port gimp2 failed > > sudo port install XviD > Error: Port XviD not found > > But here is XviD listened > https://trac.macports.org/browser/trunk/dports/multimedia/XviD > today morning before I begin all my installations I run sudo port -v selfupdate to get the last base I run it now again ... and sudo port install gimp works now 8-) have you done an update in the base installation today? -- FritzS fritzs at gmx.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From fritzs at gmx.net Sun Jul 29 04:56:42 2012 From: fritzs at gmx.net (FritzS - gmx) Date: Sun, 29 Jul 2012 13:56:42 +0200 Subject: Computing dependencies for gimp - Error: The following dependencies were not installed .... In-Reply-To: <63EE50E2-4216-4AF1-9891-737F484E1C67@gmx.net> References: <418E5B10-44EA-4E8E-8EAB-BDEDDE0B58F8@gmx.net> <63EE50E2-4216-4AF1-9891-737F484E1C67@gmx.net> Message-ID: <81010A7E-0B59-4EF1-BDAD-E3A602A8C8C4@gmx.net> Am 29.07.2012 um 13:35 schrieb FritzS - gmx : > today morning before I begin all my installations I run > sudo port -v selfupdate > to get the last base > > I run it now again ... and > sudo port install gimp > works now 8-) it begins but end in an error too: sudo port install gimp Password: ---> Computing dependencies for gimp ---> Dependencies to be installed: gimp-app gimp2 gegl babl w3m ffmpeg XviD dirac cppunit gmake lame libogg libsdl libtheora libvorbis libvpx yasm openjpeg jbigkit lcms2 schroedinger orc speex texi2html x264 lensfun libopenraw boost icu libspiro lua openexr ilmbase gsed gimp-help-en coreutils gmp gawk pngcrush lcms libexif libgnomeui audiofile libbonoboui libgnome esound libgnomecanvas libglade2 libgnome-keyring gnome-keyring libgcrypt libgpg-error libtasn1 xorg-libsm xorg-libice libmng libwmf poppler poppler-data py27-gtk py27-cairo py27-numpy fftw-3 py27-nose nosetests_select py27-distribute py27-py py27-gobject webkit-gtk gst-plugins-base gstreamer bison flex gzip libsoup glib-networking gnutls lzo2 libproxy cmake xorg-libXt xorg-libXmu xpm gimp-jp2 gimp-lqr-plugin liblqr gtk-nodoka-engine gutenprint icns-gimp ufraw cfitsio dcraw exiv2 gtkimageview xsane sane-backends libusb-compat libusb net-snmp ---> Building w3m Error: org.macports.build for port w3m returned: command execution failed Error: Failed to install w3m Please see the log file for port w3m for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_w3m/w3m/main.log Error: The following dependencies were not installed: gimp-app gimp2 gegl babl w3m ffmpeg XviD dirac cppunit gmake lame libogg libsdl libtheora libvorbis libvpx yasm openjpeg jbigkit lcms2 schroedinger orc speex texi2html x264 lensfun libopenraw boost icu libspiro lua openexr ilmbase gsed gimp-help-en coreutils gmp gawk pngcrush lcms libexif libgnomeui audiofile libbonoboui libgnome esound libgnomecanvas libglade2 libgnome-keyring gnome-keyring libgcrypt libgpg-error libtasn1 xorg-libsm xorg-libice libmng libwmf poppler poppler-data py27-gtk py27-cairo py27-numpy fftw-3 py27-nose nosetests_select py27-distribute py27-py py27-gobject webkit-gtk gst-plugins-base gstreamer bison flex gzip libsoup glib-networking gnutls lzo2 libproxy cmake xorg-libXt xorg-libXmu xpm gimp-jp2 gimp-lqr-plugin liblqr gtk-nodoka-engine gutenprint icns-gimp ufraw cfitsio dcraw exiv2 gtkimageview xsane sane-backends libusb-compat libusb net-snmp To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port gimp failed -- FritzS fritzs at gmx.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremy at lavergne.gotdns.org Sun Jul 29 06:04:53 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Sun, 29 Jul 2012 09:04:53 -0400 Subject: Computing dependencies for gimp - Error: The following dependencies were not installed .... In-Reply-To: <81010A7E-0B59-4EF1-BDAD-E3A602A8C8C4@gmx.net> References: <418E5B10-44EA-4E8E-8EAB-BDEDDE0B58F8@gmx.net> <63EE50E2-4216-4AF1-9891-737F484E1C67@gmx.net> <81010A7E-0B59-4EF1-BDAD-E3A602A8C8C4@gmx.net> Message-ID: <0C4D63F7-4105-4C57-97FF-80CF026AD78B@lavergne.gotdns.org> > sudo port install gimp > Password: > ---> Computing dependencies for gimp > ---> Dependencies to be installed: gimp-app gimp2 gegl babl w3m ffmpeg XviD dirac cppunit gmake lame libogg libsdl libtheora libvorbis libvpx yasm openjpeg jbigkit lcms2 schroedinger orc speex texi2html x264 lensfun libopenraw boost icu libspiro lua openexr ilmbase gsed gimp-help-en coreutils gmp gawk pngcrush lcms libexif libgnomeui audiofile libbonoboui libgnome esound libgnomecanvas libglade2 libgnome-keyring gnome-keyring libgcrypt libgpg-error libtasn1 xorg-libsm xorg-libice libmng libwmf poppler poppler-data py27-gtk py27-cairo py27-numpy fftw-3 py27-nose nosetests_select py27-distribute py27-py py27-gobject webkit-gtk gst-plugins-base gstreamer bison flex gzip libsoup glib-networking gnutls lzo2 libproxy cmake xorg-libXt xorg-libXmu xpm gimp-jp2 gimp-lqr-plugin liblqr gtk-nodoka-engine gutenprint icns-gimp ufraw cfitsio dcraw exiv2 gtkimageview xsane sane-backends libusb-compat libusb net-snmp > ---> Building w3m > Error: org.macports.build for port w3m returned: command execution failed > Error: Failed to install w3m > Please see the log file for port w3m for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_w3m/w3m/main.log Well, that wasn't a clean build attempt for w3m. Clean it first and try again. From fritzs at gmx.net Sun Jul 29 06:51:42 2012 From: fritzs at gmx.net (FritzS - gmx) Date: Sun, 29 Jul 2012 15:51:42 +0200 Subject: Computing dependencies for gimp - Error: The following dependencies were not installed .... In-Reply-To: <0C4D63F7-4105-4C57-97FF-80CF026AD78B@lavergne.gotdns.org> References: <418E5B10-44EA-4E8E-8EAB-BDEDDE0B58F8@gmx.net> <63EE50E2-4216-4AF1-9891-737F484E1C67@gmx.net> <81010A7E-0B59-4EF1-BDAD-E3A602A8C8C4@gmx.net> <0C4D63F7-4105-4C57-97FF-80CF026AD78B@lavergne.gotdns.org> Message-ID: <6CD07280-0B22-45DA-BBF0-C086A039B167@gmx.net> Am 29.07.2012 um 15:04 schrieb Jeremy Lavergne : >> sudo port install gimp >> Password: >> ---> Computing dependencies for gimp >> ---> Dependencies to be installed: gimp-app gimp2 gegl babl w3m ffmpeg XviD dirac cppunit gmake lame libogg libsdl libtheora libvorbis libvpx yasm openjpeg jbigkit lcms2 schroedinger orc speex texi2html x264 lensfun libopenraw boost icu libspiro lua openexr ilmbase gsed gimp-help-en coreutils gmp gawk pngcrush lcms libexif libgnomeui audiofile libbonoboui libgnome esound libgnomecanvas libglade2 libgnome-keyring gnome-keyring libgcrypt libgpg-error libtasn1 xorg-libsm xorg-libice libmng libwmf poppler poppler-data py27-gtk py27-cairo py27-numpy fftw-3 py27-nose nosetests_select py27-distribute py27-py py27-gobject webkit-gtk gst-plugins-base gstreamer bison flex gzip libsoup glib-networking gnutls lzo2 libproxy cmake xorg-libXt xorg-libXmu xpm gimp-jp2 gimp-lqr-plugin liblqr gtk-nodoka-engine gutenprint icns-gimp ufraw cfitsio dcraw exiv2 gtkimageview xsane sane-backends libusb-compat libusb net-snmp >> ---> Building w3m >> Error: org.macports.build for port w3m returned: command execution failed >> Error: Failed to install w3m >> Please see the log file for port w3m for details: >> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_w3m/w3m/main.log > > Well, that wasn't a clean build attempt for w3m. Clean it first and try again. I run 'sudo port clean --all' and 'sudo port clean w3m' and 'sudo port -d selfupdate' too the error the same now I run only sudo port install w3m a part from the /w3m/main.log ---- :info:build ^ :info:build 1 error generated. :info:build make: *** [indep.o] Error 1 :info:build make: *** Waiting for unfinished jobs.... :info:build /bin/sh: line 1: 79233 Segmentation fault: 11 ./mktable 100 functable.tab > functable.c :info:build make: *** [functable.c] Error 139 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_w3m/w3m/work/w3m-0.5.3' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_w3m/w3m/work/w3m-0.5.3" && /usr/bin/make -j2 -w all :info:build Exit code: 2 :error:build org.macports.build for port w3m returned: command execution failed :debug:build Error code: CHILDSTATUS 79179 2 :debug:build Backtrace: command execution failed while executing "system -nice 0 $fullcmdstring" ("eval" body line 1) invoked from within "eval system $notty $nice \$fullcmdstring" invoked from within "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: targets not executed for w3m: org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Please see the log file for port w3m for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_w3m/w3m/main.log ---- PS: Could I attach a complete log file in this mailing list? -- FritzS fritzs at gmx.net From jeremy at lavergne.gotdns.org Sun Jul 29 06:56:39 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Sun, 29 Jul 2012 09:56:39 -0400 Subject: Computing dependencies for gimp - Error: The following dependencies were not installed .... In-Reply-To: <6CD07280-0B22-45DA-BBF0-C086A039B167@gmx.net> References: <418E5B10-44EA-4E8E-8EAB-BDEDDE0B58F8@gmx.net> <63EE50E2-4216-4AF1-9891-737F484E1C67@gmx.net> <81010A7E-0B59-4EF1-BDAD-E3A602A8C8C4@gmx.net> <0C4D63F7-4105-4C57-97FF-80CF026AD78B@lavergne.gotdns.org> <6CD07280-0B22-45DA-BBF0-C086A039B167@gmx.net> Message-ID: <339D9FA8-EF37-44BE-92A5-5541C67C1CC8@lavergne.gotdns.org> > PS: Could I attach a complete log file in this mailing list? You're better off attaching it to a ticket. From fritzs at gmx.net Sun Jul 29 07:13:20 2012 From: fritzs at gmx.net (FritzS - gmx) Date: Sun, 29 Jul 2012 16:13:20 +0200 Subject: Computing dependencies for gimp - Error: The following dependencies were not installed .... In-Reply-To: <339D9FA8-EF37-44BE-92A5-5541C67C1CC8@lavergne.gotdns.org> References: <418E5B10-44EA-4E8E-8EAB-BDEDDE0B58F8@gmx.net> <63EE50E2-4216-4AF1-9891-737F484E1C67@gmx.net> <81010A7E-0B59-4EF1-BDAD-E3A602A8C8C4@gmx.net> <0C4D63F7-4105-4C57-97FF-80CF026AD78B@lavergne.gotdns.org> <6CD07280-0B22-45DA-BBF0-C086A039B167@gmx.net> <339D9FA8-EF37-44BE-92A5-5541C67C1CC8@lavergne.gotdns.org> Message-ID: <85564949-5E8A-47B1-8FFD-A77EFD4C96DA@gmx.net> Am 29.07.2012 um 15:56 schrieb Jeremy Lavergne : >> PS: Could I attach a complete log file in this mailing list? > > You're better off attaching it to a ticket. > now in ticket https://trac.macports.org/ticket/35405 -- FritzS fritzs at gmx.net From allbery.b at gmail.com Sun Jul 29 07:38:18 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Sun, 29 Jul 2012 10:38:18 -0400 Subject: py27-spyder fails to build on Mountain Lion In-Reply-To: <2B8E9704-6C7F-4D77-B555-51803F581FFE@mso.anu.edu.au> References: <2B8E9704-6C7F-4D77-B555-51803F581FFE@mso.anu.edu.au> Message-ID: On Sun, Jul 29, 2012 at 5:47 AM, David Nicholls wrote: > Following exactly the "maintenance" instructions on the Macports website > for upgrading to a new OS, and attempting to install py27-spyder (v > 2.1.10), I get the following: > Did you upgrade python and py27-distribute first? The latter has compiler information baked into it which will be incorrect after upgrading to Xcode 4.4 as required by Mountain Lion, and that outdated information will probably break some Python-related builds. Similar concerns apply to the perl5 ports (which themselves have the compiler information baked in), php*-pear, etc. -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Sun Jul 29 09:54:07 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 29 Jul 2012 11:54:07 -0500 Subject: How to set C++ compiler outside Macports? In-Reply-To: References: <04B03595-6682-44A5-8877-BE7F0BFB8E0C@macports.org> Message-ID: <3753B5C8-1E60-4D42-943B-8F19F06A29E9@macports.org> On Jul 29, 2012, at 01:35, Ian Wadham wrote: > On 29/07/2012, at 3:43 PM, Jeremy Huddleston Sequoia wrote: >> On Jul 28, 2012, at 21:35, Ian Wadham wrote: >>> In my Mac OS X environment, /usr/bin/c++ is a symbolic link to >>> llvm-g++-4.2, but I need it to be to the same compiler as Macports >>> used to build kdelibs4. Then I can compile and link my own code >>> correctly with that library and continue developing and testing my >>> source code for the next release of KDE. >> >> Why are you using /usr/bin/c++? Just use /usr/bin/clang++ (or 'xcrun clang++' if you didn't install the command line tools). > > It's not that simple. I never use a compiler directly, just CMake initially, > including all the KDE macros and dependencies, then "make" on later > runs. CMake picks up /usr/bin/c++, by default, but could no doubt be > made to do something else. Probably the usual CC and CXX environment variables could be used to influence that. >>> For the moment, I have found that "brute force" linking of /usr/bin/c++ >>> to clang works fine, but is there a safer way? Is there, for example, >>> some way (e.g. a script or command) to extract from Macports the >>> compiler it used and make it a symbol in my own builds? >> >> You can look at the build logs to see what compiler is used, but on anything recent will be using clang. > > By default, Macports does not leave logs behind. If you like, you can set "keeplogs yes" in macports.conf to change that. > I was looking perhaps for > some Macports cache or config file where compiler assignments are kept > for each port or for ports in general, but have been unable to find any. The source code that decides which compiler to use is here: https://trac.macports.org/browser/trunk/base/src/port1.0/portconfigure.tcl It's not terribly straightforward and not something you can just grep out of it. > Is use of clang now official Macports policy? Last I heard on this list, a > few months back, its use was experimental. The compiler MacPorts uses by default is chosen based on the Xcode version. Xcode 2.x: gcc-4.0 Xcode 3.x: gcc-4.2 Xcode 4.0 and 4.1: llvm-gcc-4.2 Xcode 4.2 and up: clang Individual ports might override that choice if necessary by setting configure.compiler or compiler.blacklist or compiler.whitelist. From mojca.miklavec.lists at gmail.com Sun Jul 29 10:18:54 2012 From: mojca.miklavec.lists at gmail.com (Mojca Miklavec) Date: Sun, 29 Jul 2012 19:18:54 +0200 Subject: How to set C++ compiler outside Macports? In-Reply-To: References: <04B03595-6682-44A5-8877-BE7F0BFB8E0C@macports.org> Message-ID: On Sun, Jul 29, 2012 at 8:35 AM, Ian Wadham wrote: > On 29/07/2012, at 3:43 PM, Jeremy Huddleston Sequoia wrote: >> On Jul 28, 2012, at 21:35, Ian Wadham wrote: >>> In my Mac OS X environment, /usr/bin/c++ is a symbolic link to >>> llvm-g++-4.2, but I need it to be to the same compiler as Macports >>> used to build kdelibs4. Then I can compile and link my own code >>> correctly with that library and continue developing and testing my >>> source code for the next release of KDE. >> >> Why are you using /usr/bin/c++? Just use /usr/bin/clang++ (or 'xcrun clang++' if you didn't install the command line tools). > > It's not that simple. I never use a compiler directly, just CMake initially, > including all the KDE macros and dependencies, then "make" on later > runs. CMake picks up /usr/bin/c++, by default, but could no doubt be > made to do something else. Try to run ccmake path/to/your/sources to see what variables you can change. You can either change them inside ccmake or call cmake -DCMAKE_CXX_COMPILER=/usr/bin/clang++ Mojca From gnurser at gmail.com Sun Jul 29 12:58:54 2012 From: gnurser at gmail.com (George Nurser) Date: Sun, 29 Jul 2012 20:58:54 +0100 Subject: py-netcdf4 port, ticket #32191 Message-ID: Hi, I just wondered how far this was from being available as a MacPort. Best wishes, George Nurser. From david at mso.anu.edu.au Sun Jul 29 16:34:26 2012 From: david at mso.anu.edu.au (David Nicholls) Date: Mon, 30 Jul 2012 09:34:26 +1000 Subject: py27-spyder fails to build on Mountain Lion In-Reply-To: References: <2B8E9704-6C7F-4D77-B555-51803F581FFE@mso.anu.edu.au> Message-ID: <1E1FC741-F88E-4E30-A720-F3957B9936C0@mso.anu.edu.au> On 30/07/2012, at 12:38 AM, Brandon Allbery wrote: > On Sun, Jul 29, 2012 at 5:47 AM, David Nicholls wrote: > Following exactly the "maintenance" instructions on the Macports website for upgrading to a new OS, and attempting to install py27-spyder (v 2.1.10), I get the following: > > Did you upgrade python and py27-distribute first? The latter has compiler information baked into it which will be incorrect after upgrading to Xcode 4.4 as required by Mountain Lion, and that outdated information will probably break some Python-related builds. > > Similar concerns apply to the perl5 ports (which themselves have the compiler information baked in), php*-pear, etc. All I did was completely uninstall and clean everything, then did a sudo install py-spyder It installed (or tried to) all the dependencies it needed, which included the python and py27-distribute. Both of those had been installed before the crash on p27-opbjc I don't want to fight a dependency list in order to get py-spyder to work. The current Apple python on this machine is v 2.7.2 and according to its boot info, it appears to be Apple build 5493, = Enthought EPD 7.1-2 (32 bit) I don't remember ever installing the Enthought distro on this machine. Is that the one that is supposed to come with Mountain Lion? Is there an install sequence you'd suggest to get py-spyder working? The reason I like it is that it has a pretty complete set of scientific python routines built in, and, unlike the Enthought academic version, isn't restricted in extensions. DN __________ Research School of Astronomy & Astrophysics Mt Stromlo Observatory Australian National University From david at mso.anu.edu.au Sun Jul 29 16:36:14 2012 From: david at mso.anu.edu.au (David Nicholls) Date: Mon, 30 Jul 2012 09:36:14 +1000 Subject: py27-spyder fails to build on Mountain Lion In-Reply-To: <1E1FC741-F88E-4E30-A720-F3957B9936C0@mso.anu.edu.au> References: <2B8E9704-6C7F-4D77-B555-51803F581FFE@mso.anu.edu.au> <1E1FC741-F88E-4E30-A720-F3957B9936C0@mso.anu.edu.au> Message-ID: <92A2B91F-6206-4F32-BDFD-DCC673DBA4C2@mso.anu.edu.au> > sudo install py-spyder sudo port install py-spyder, I meant From david at mso.anu.edu.au Sun Jul 29 16:44:02 2012 From: david at mso.anu.edu.au (David Nicholls) Date: Mon, 30 Jul 2012 09:44:02 +1000 Subject: py27-spyder fails to build on Mountain Lion In-Reply-To: <1E1FC741-F88E-4E30-A720-F3957B9936C0@mso.anu.edu.au> References: <2B8E9704-6C7F-4D77-B555-51803F581FFE@mso.anu.edu.au> <1E1FC741-F88E-4E30-A720-F3957B9936C0@mso.anu.edu.au> Message-ID: <7477A1D3-80F9-45DF-A286-41F9C590CE3A@mso.anu.edu.au> Looks like it's a duplicate on the trac.macports system, ticket #35325, but listed under py-objc which I why I didn't find it. Lot's of people are striking the same problem. DN On 30/07/2012, at 9:34 AM, David Nicholls wrote: > On 30/07/2012, at 12:38 AM, Brandon Allbery wrote: > >> On Sun, Jul 29, 2012 at 5:47 AM, David Nicholls wrote: >> Following exactly the "maintenance" instructions on the Macports website for upgrading to a new OS, and attempting to install py27-spyder (v 2.1.10), I get the following: >> >> Did you upgrade python and py27-distribute first? The latter has compiler information baked into it which will be incorrect after upgrading to Xcode 4.4 as required by Mountain Lion, and that outdated information will probably break some Python-related builds. >> >> Similar concerns apply to the perl5 ports (which themselves have the compiler information baked in), php*-pear, etc. > > All I did was completely uninstall and clean everything, then did a > > sudo install py-spyder > > It installed (or tried to) all the dependencies it needed, which included the python and py27-distribute. Both of those had been installed before the crash on p27-opbjc > > I don't want to fight a dependency list in order to get py-spyder to work. The current Apple python on this machine is v 2.7.2 and according to its boot info, it appears to be Apple build 5493, = Enthought EPD 7.1-2 (32 bit) I don't remember ever installing the Enthought distro on this machine. Is that the one that is supposed to come with Mountain Lion? > > Is there an install sequence you'd suggest to get py-spyder working? The reason I like it is that it has a pretty complete set of scientific python routines built in, and, unlike the Enthought academic version, isn't restricted in extensions. > > DN > __________ > Research School of Astronomy & Astrophysics > Mt Stromlo Observatory > Australian National University > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users From robsonpeixoto at gmail.com Mon Jul 30 04:27:58 2012 From: robsonpeixoto at gmail.com (Robson Roberto Souza Peixoto) Date: Mon, 30 Jul 2012 08:27:58 -0300 Subject: libmemcached - fail to build on Mountain Lion Message-ID: I'm having this [1] problem to compile libmemcached on ML. Anybody with the same problem? I had this ports installed [2] To simplify: $ port deps libmemcached Full Name: libmemcached @1.0.9_1 Build Dependencies: perl5, cyrus-sasl2 Library Dependencies: memcached $ port installed perl5 cyrus-sasl2 memcached The following ports are currently installed: cyrus-sasl2 @2.1.25_1+kerberos (active) memcached @1.4.13_0+umem (active) perl5 @5.12.4_0+perl5_12 (active) I opened this bug [3] 1 - https://trac.macports.org/attachment/ticket/35334/main-1.0.9.log 2 - https://gist.github.com/4be8333d13054b709aba 3 - https://trac.macports.org/ticket/35334 -- Robson Roberto Souza Peixoto Robinho Master in Computer Science, University of Campinas Linux Counter #395633 IRC: robsonpeixoto Twitter: http://twitter.com/rrspba github: https://github.com/robsonpeixoto From murrayeisenberg at gmail.com Mon Jul 30 07:14:07 2012 From: murrayeisenberg at gmail.com (Murray Eisenberg) Date: Mon, 30 Jul 2012 10:14:07 -0400 Subject: Which X11 test_extensions setting for xdotool? Message-ID: <501696AF.9030504@gmail.com> Under MacPorts 2.1.2 on Mountain Lion, after updating ports including xdotool, I got the message: To use xdotool (and avoid the error message "Error: XTEST extension unavailabl on '(null)'") you need to enable the XTEST extension. If you're using Apple's X11.app, the command to do so is: defaults write org.x.X11 enable_test_extensions -boolean true If you're using the MacPorts X11.app, use: defaults write org.macports.X11 enable_test_extensions -boolean true This only needs to be done once. But I've directly downloaded and installed XQuartz.app rather than Apple's X11.app. And I don't have any port named x11 from MacPorts; I do have xorg-libX11 from MacPorts. What should I do? -- Murray Eisenberg murrayeisenberg at gmail.com 80 Fearing Street phone 413 549-1020 (H) Amherst, MA 01002-1912 From allbery.b at gmail.com Mon Jul 30 07:18:23 2012 From: allbery.b at gmail.com (Brandon Allbery) Date: Mon, 30 Jul 2012 10:18:23 -0400 Subject: Which X11 test_extensions setting for xdotool? In-Reply-To: <501696AF.9030504@gmail.com> References: <501696AF.9030504@gmail.com> Message-ID: On Mon, Jul 30, 2012 at 10:14 AM, Murray Eisenberg < murrayeisenberg at gmail.com> wrote: > defaults write org.x.X11 enable_test_extensions -boolean true > defaults write org.macports.X11 enable_test_extensions -boolean true > > This only needs to be done once. > > But I've directly downloaded and installed XQuartz.app rather than Apple's > X11.app. And I don't have any port named x11 from MacPorts; I do have > xorg-libX11 from MacPorts. > The defaults domain for XQuartz is org.macosforge.xquartz.X11. defaults write org.macosforge.xquartz.X11 enable_test_extensions -boolean true -- brandon s allbery allbery.b at gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms -------------- next part -------------- An HTML attachment was scrubbed... URL: From gideon.simpson at gmail.com Mon Jul 30 14:52:39 2012 From: gideon.simpson at gmail.com (Gideon Simpson) Date: Mon, 30 Jul 2012 16:52:39 -0500 Subject: texi2html problem Message-ID: <84CA2B41-AD74-4488-BC14-B70A28A28FC6@gmail.com> I'm on Mountain Lion and did a port upgrade outdated. I am getting the following error: gideon@~$ sudo port clean --all texi2html ---> Cleaning texi2html gideon@~$ sudo port install texi2html ---> Computing dependencies for texi2html ---> Fetching archive for texi2html ---> Attempting to fetch texi2html-5.0_0.darwin_12.noarch.tbz2 from http://packages.macports.org/texi2html ---> Fetching distfiles for texi2html ---> Attempting to fetch texi2html-5.0.tar.bz2 from http://mirror.cinquix.com/pub/savannah/texi2html ---> Verifying checksum(s) for texi2html Error: Checksum (md5) mismatch for texi2html-5.0.tar.bz2 Error: Checksum (sha1) mismatch for texi2html-5.0.tar.bz2 Error: Checksum (rmd160) mismatch for texi2html-5.0.tar.bz2 *** The non-matching file appears to be HTML. See this page for possible reasons for the checksum mismatch: *** Error: org.macports.checksum for port texi2html returned: Unable to verify file checksums Please see the log file for port texi2html for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_texi2html/texi2html/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port texi2html failed and this is what's in the log file: gideon@~$ cat /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_texi2html/texi2html/main.log version:1 :debug:main epoch: in tree: 0 installed: 0 :debug:main perl5 5.12.4_0 exists in the ports tree :debug:main perl5 5.12.4_0 +perl5_12 is the latest installed :debug:main perl5 5.12.4_0 +perl5_12 is active :debug:main Merging existing variants '+perl5_12' into variants :debug:main new fully merged portvariants: perl5_12 + :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/lang/perl5 :debug:main OS darwin/12.0.0 (Mac OS X 10.8) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main universal_variant is false, so not adding the default universal variant :debug:main Executing variant perl5_12 provides perl5_12 :debug:main No need to upgrade! perl5 5.12.4_0 >= perl5 5.12.4_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main perl5.12 5.12.4_1 exists in the ports tree :debug:main perl5.12 5.12.4_1 is the latest installed :debug:main perl5.12 5.12.4_1 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/lang/perl5.12 :debug:main OS darwin/12.0.0 (Mac OS X 10.8) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main adding the default universal variant :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main No need to upgrade! perl5.12 5.12.4_1 >= perl5.12 5.12.4_1 :debug:main epoch: in tree: 0 installed: 0 :debug:main gdbm 1.10_2 exists in the ports tree :debug:main gdbm 1.10_2 is the latest installed :debug:main gdbm 1.10_2 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/databases/gdbm :debug:main OS darwin/12.0.0 (Mac OS X 10.8) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main adding the default universal variant :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main No need to upgrade! gdbm 1.10_2 >= gdbm 1.10_2 :debug:main epoch: in tree: 0 installed: 0 :debug:main gettext 0.18.1.1_2 exists in the ports tree :debug:main gettext 0.18.1.1_2 is the latest installed :debug:main gettext 0.18.1.1_2 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/gettext :debug:main OS darwin/12.0.0 (Mac OS X 10.8) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/archcheck-1.0.tcl :debug:main universal variant already exists, so not adding the default one :debug:main No need to upgrade! gettext 0.18.1.1_2 >= gettext 0.18.1.1_2 :debug:main epoch: in tree: 0 installed: 0 :debug:main libiconv 1.14_0 exists in the ports tree :debug:main libiconv 1.14_0 is the latest installed :debug:main libiconv 1.14_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/textproc/libiconv :debug:main OS darwin/12.0.0 (Mac OS X 10.8) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main Using group file /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main No need to upgrade! libiconv 1.14_0 >= libiconv 1.14_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main ncurses 5.9_1 exists in the ports tree :debug:main ncurses 5.9_1 is the latest installed :debug:main ncurses 5.9_1 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/ncurses :debug:main OS darwin/12.0.0 (Mac OS X 10.8) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main adding the default universal variant :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main No need to upgrade! ncurses 5.9_1 >= ncurses 5.9_1 :debug:main epoch: in tree: 0 installed: 0 :debug:main expat 2.1.0_0 exists in the ports tree :debug:main expat 2.1.0_0 is the latest installed :debug:main expat 2.1.0_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/textproc/expat :debug:main OS darwin/12.0.0 (Mac OS X 10.8) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided :debug:main adding the default universal variant :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf :debug:main No need to upgrade! expat 2.1.0_0 >= expat 2.1.0_0 :msg:main ---> Computing dependencies for texi2html:info:main .:debug:main texi2html has no conflicts :debug:main Searching for dependency: perl5 :debug:main Found Dependency: receipt exists for perl5 :msg:main :debug:main Executing org.macports.main (texi2html) :debug:main changing euid/egid - current euid: 0 - current egid: 0 :debug:main egid changed to: 501 :debug:main euid changed to: 502 :debug:archivefetch archivefetch phase started at Mon Jul 30 16:48:30 CDT 2012 :msg:archivefetch ---> Fetching archive for texi2html :debug:archivefetch Executing org.macports.archivefetch (texi2html) :debug:archivefetch euid/egid changed to: 0/0 :debug:archivefetch chowned /opt/local/var/macports/incoming to macports :debug:archivefetch euid/egid changed to: 502/501 :info:archivefetch ---> texi2html-5.0_0.darwin_12.noarch.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified :msg:archivefetch ---> Attempting to fetch texi2html-5.0_0.darwin_12.noarch.tbz2 from http://packages.macports.org/texi2html :debug:archivefetch Fetching archive failed:: The requested URL returned error: 404 :debug:archivefetch Privilege de-escalation not attempted as not running as root. :debug:fetch fetch phase started at Mon Jul 30 16:48:31 CDT 2012 :notice:fetch ---> Fetching distfiles for texi2html :debug:fetch Can't run fetch on this port without elevated privileges. Escalating privileges back to root. :debug:fetch euid changed to: 0. egid changed to: 0. :debug:fetch changing euid/egid - current euid: 0 - current egid: 0 :debug:fetch egid changed to: 501 :debug:fetch euid changed to: 502 :debug:fetch Executing org.macports.fetch (texi2html) :info:fetch ---> texi2html-5.0.tar.bz2 doesn't seem to exist in /opt/local/var/macports/distfiles/texi2html :notice:fetch ---> Attempting to fetch texi2html-5.0.tar.bz2 from http://mirror.cinquix.com/pub/savannah/texi2html :debug:fetch Privilege de-escalation not attempted as not running as root. :debug:checksum checksum phase started at Mon Jul 30 16:48:32 CDT 2012 :notice:checksum ---> Verifying checksum(s) for texi2html :debug:checksum Executing org.macports.checksum (texi2html) :info:checksum ---> Checksumming texi2html-5.0.tar.bz2 :error:checksum Checksum (md5) mismatch for texi2html-5.0.tar.bz2 :info:checksum Portfile checksum: texi2html-5.0.tar.bz2 md5 f15ac876fcdc8be865b16535f480aa54 :info:checksum Distfile checksum: texi2html-5.0.tar.bz2 md5 6b30311698afc0da6f54dfc397ced50d :error:checksum Checksum (sha1) mismatch for texi2html-5.0.tar.bz2 :info:checksum Portfile checksum: texi2html-5.0.tar.bz2 sha1 20072444ce814d0e74fd7e467d1506908f8c889c :info:checksum Distfile checksum: texi2html-5.0.tar.bz2 sha1 8d815a7ac2db48291097a267d8182100178c2323 :error:checksum Checksum (rmd160) mismatch for texi2html-5.0.tar.bz2 :info:checksum Portfile checksum: texi2html-5.0.tar.bz2 rmd160 193d2ab489e61546100a57943c410deffb8d4c4b :info:checksum Distfile checksum: texi2html-5.0.tar.bz2 rmd160 e9f5ff2b81c0b52549b5ddd418ae0da40e1ab76f :info:checksum The correct checksum line may be: :info:checksum checksums md5 6b30311698afc0da6f54dfc397ced50d \ sha1 8d815a7ac2db48291097a267d8182100178c2323 \ rmd160 e9f5ff2b81c0b52549b5ddd418ae0da40e1ab76f :notice:checksum *** :notice:checksum The non-matching file appears to be HTML. See this page for possible reasons :notice:checksum for the checksum mismatch: :notice:checksum :notice:checksum *** :error:checksum org.macports.checksum for port texi2html returned: Unable to verify file checksums :debug:checksum Error code: NONE :debug:checksum Backtrace: Unable to verify file checksums while executing "$procedure $targetname" :info:checksum Warning: targets not executed for texi2html: org.macports.activate org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install :notice:checksum Please see the log file for port texi2html for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_texi2html/texi2html/main.log If i check the HTML file, I get: gideon@~$ cat /opt/local/var/macports/distfiles/texi2html/texi2html-5.0.tar.bz2 cinquix.com

 
 
Welcome to
cinquix.com

 
 
  


-gideon From ryandesign at macports.org Mon Jul 30 15:44:44 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 30 Jul 2012 17:44:44 -0500 Subject: texi2html problem In-Reply-To: <84CA2B41-AD74-4488-BC14-B70A28A28FC6@gmail.com> References: <84CA2B41-AD74-4488-BC14-B70A28A28FC6@gmail.com> Message-ID: <4932D42C-7BAE-48E8-BFB0-2639FC9F9BB2@macports.org> On Jul 30, 2012, at 16:52, Gideon Simpson wrote: > ---> Attempting to fetch texi2html-5.0.tar.bz2 from http://mirror.cinquix.com/pub/savannah/texi2html > ---> Verifying checksum(s) for texi2html > Error: Checksum (md5) mismatch for texi2html-5.0.tar.bz2 > Error: Checksum (sha1) mismatch for texi2html-5.0.tar.bz2 > Error: Checksum (rmd160) mismatch for texi2html-5.0.tar.bz2 > *** > The non-matching file appears to be HTML. See this page for possible reasons > for the checksum mismatch: > > *** Already fixed: https://trac.macports.org/ticket/35435 From arno at alum.wpi.edu Mon Jul 30 19:16:33 2012 From: arno at alum.wpi.edu (Arno Hautala) Date: Mon, 30 Jul 2012 22:16:33 -0400 Subject: noidle In-Reply-To: <4AA6EC7D-7CD5-48E7-8B65-9DA8BC9B65A4@verkehrsplanung.com> References: <4AA6EC7D-7CD5-48E7-8B65-9DA8BC9B65A4@verkehrsplanung.com> Message-ID: On Thu, Mar 22, 2012 at 4:00 AM, Drechsel Wolf wrote: > > frequently I noticed that my iMac G5 will go to sleep during a time > extensive build (gcc45 at the moment). >> pmset noidle & This won't be of help to the G5, but Mountain Lion introduced a new command called 'caffeinate' [1]. i.e.: > caffeinate -s port install gcc45 [1]: http://www.manpagez.com/man/8/caffeinate/ -- arno s hautala /-| arno at alum.wpi.edu pgp b2c9d448 From jasperfrumau at gmail.com Tue Jul 31 01:13:11 2012 From: jasperfrumau at gmail.com (Jasper Frumau) Date: Tue, 31 Jul 2012 15:13:11 +0700 Subject: Upgrade of MacPorts fails Message-ID: Just upgraded xCode to the latest version and upgraded to Mountain Lion. Wanted to upgrade MacPorts now as well. Got stuck: sudo port -d selfupdate Password: DEBUG: Copying /Users/jasper/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences DEBUG: MacPorts sources location: /opt/local/var/macports/sources/ rsync.macports.org/release/base ---> Updating MacPorts base sources using rsync receiving file list ... done ./ deleting config.log sent 42 bytes received 8238 bytes 1840.00 bytes/sec total size is 3261808 speedup is 393.94 MacPorts base version 2.1.1 installed, DEBUG: Rebuilding and reinstalling MacPorts if needed MacPorts base version 2.1.2 downloaded. ---> Updating the ports tree Synchronizing local ports tree from rsync:// rsync.macports.org/release/ports/ DEBUG: /usr/bin/rsync -rtzv --delete-after '--exclude=/PortIndex*' rsync:// rsync.macports.org/release/ports/ /opt/local/var/macports/sources/ rsync.macports.org/release/ports receiving file list ... done ./ sent 59 bytes received 684965 bytes 13564.83 bytes/sec total size is 35704166 speedup is 52.12 DEBUG: /usr/bin/rsync -rtzv --delete-after rsync:// rsync.macports.org/release/ports/PortIndex_darwin_12_i386/PortIndex/opt/local/var/macports/sources/ rsync.macports.org/release/ports receiving file list ... done sent 36 bytes received 70 bytes 42.40 bytes/sec total size is 8547616 speedup is 80637.89 ---> MacPorts base is outdated, installing new version 2.1.2 DEBUG: Permissions OK Installing new MacPorts release in /opt/local as root:admin; permissions 0755; Tcl-Package in /Library/Tcl checking build system type... i386-apple-darwin12.0.0 checking host system type... i386-apple-darwin12.0.0 checking target system type... i386-apple-darwin12.0.0 checking MacPorts version... 2.1.2 checking for sw_vers... /usr/bin/sw_vers checking for defaults... /usr/bin/defaults checking for xcode-select... /usr/bin/xcode-select checking Mac OS X version... 10.8 checking Xcode location... /Applications/Xcode.app/Contents/Developer checking Xcode version... 4.4 checking for gcc... /usr/bin/cc checking whether the C compiler works... no configure: error: in `/opt/local/var/macports/sources/ rsync.macports.org/release/base': configure: error: C compiler cannot create executables See `config.log' for more details Command failed: cd /opt/local/var/macports/sources/ rsync.macports.org/release/base && CC=/usr/bin/cc ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0755 --enable-readline && make && make install SELFUPDATING=1 Exit code: 77 DEBUG: Error installing new MacPorts base: command execution failed while executing "macports::selfupdate [array get global_options] base_updated" Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed Any ideas how I can get MacPorts to do it all without these errors? -------------- next part -------------- An HTML attachment was scrubbed... URL: From domiman at gmail.com Tue Jul 31 01:58:04 2012 From: domiman at gmail.com (Dominik Reichardt) Date: Tue, 31 Jul 2012 10:58:04 +0200 Subject: Upgrade of MacPorts fails In-Reply-To: References: Message-ID: <25EDF647-9C5F-45BC-AB67-8F32D10F9DCE@gmail.com> Nit directly solving this but... First of all you upgraded to Mountain Lion and thus you will need to go through the migration process. In my case I just nuked MacPorts, downloaded the ML installer of MacPorts and begun anew. Second, since you updated Xcode as well you need to accept the xcode license again or sime ports will fail. Am 31.07.2012 um 10:13 schrieb Jasper Frumau : > Just upgraded xCode to the latest version and upgraded to Mountain Lion. Wanted to upgrade MacPorts now as well. Got stuck: > > sudo port -d selfupdate > Password: > DEBUG: Copying /Users/jasper/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences > DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/base > ---> Updating MacPorts base sources using rsync > receiving file list ... done > ./ > deleting config.log > > sent 42 bytes received 8238 bytes 1840.00 bytes/sec > total size is 3261808 speedup is 393.94 > MacPorts base version 2.1.1 installed, > DEBUG: Rebuilding and reinstalling MacPorts if needed > MacPorts base version 2.1.2 downloaded. > ---> Updating the ports tree > Synchronizing local ports tree from rsync://rsync.macports.org/release/ports/ > DEBUG: /usr/bin/rsync -rtzv --delete-after '--exclude=/PortIndex*' rsync://rsync.macports.org/release/ports/ /opt/local/var/macports/sources/rsync.macports.org/release/ports > receiving file list ... done > ./ > > sent 59 bytes received 684965 bytes 13564.83 bytes/sec > total size is 35704166 speedup is 52.12 > DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/ports/PortIndex_darwin_12_i386/PortIndex /opt/local/var/macports/sources/rsync.macports.org/release/ports > receiving file list ... done > > sent 36 bytes received 70 bytes 42.40 bytes/sec > total size is 8547616 speedup is 80637.89 > ---> MacPorts base is outdated, installing new version 2.1.2 > DEBUG: Permissions OK > Installing new MacPorts release in /opt/local as root:admin; permissions 0755; Tcl-Package in /Library/Tcl > > checking build system type... i386-apple-darwin12.0.0 > checking host system type... i386-apple-darwin12.0.0 > checking target system type... i386-apple-darwin12.0.0 > checking MacPorts version... 2.1.2 > checking for sw_vers... /usr/bin/sw_vers > checking for defaults... /usr/bin/defaults > checking for xcode-select... /usr/bin/xcode-select > checking Mac OS X version... 10.8 > checking Xcode location... /Applications/Xcode.app/Contents/Developer > checking Xcode version... 4.4 > checking for gcc... /usr/bin/cc > checking whether the C compiler works... no > configure: error: in `/opt/local/var/macports/sources/rsync.macports.org/release/base': > configure: error: C compiler cannot create executables > See `config.log' for more details > Command failed: cd /opt/local/var/macports/sources/rsync.macports.org/release/base && CC=/usr/bin/cc ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0755 --enable-readline && make && make install SELFUPDATING=1 > Exit code: 77 > DEBUG: Error installing new MacPorts base: command execution failed > while executing > "macports::selfupdate [array get global_options] base_updated" > Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed > > Any ideas how I can get MacPorts to do it all without these errors? > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From cal at macports.org Tue Jul 31 02:41:11 2012 From: cal at macports.org (Clemens Lang) Date: Tue, 31 Jul 2012 11:41:11 +0200 Subject: Upgrade of MacPorts fails In-Reply-To: References: Message-ID: <20120731094111.GE13308@towel.neverpanic.de> Hi, On Tue, Jul 31, 2012 at 03:13:11PM +0700, Jasper Frumau wrote: > configure: error: C compiler cannot create executables you didn't install the Command Line Tools from Xcode's preferences' downloads tab. See: http://trac.macports.org/wiki/Migration -- Clemens Lang From jasperfrumau at gmail.com Tue Jul 31 03:25:32 2012 From: jasperfrumau at gmail.com (Jasper Frumau) Date: Tue, 31 Jul 2012 17:25:32 +0700 Subject: Upgrade of MacPorts fails In-Reply-To: <20120731094111.GE13308@towel.neverpanic.de> References: <20120731094111.GE13308@towel.neverpanic.de> Message-ID: Yeah, just realized this starting up XCode and reading about it here and there. Slipper my mind. Will install it again and retry. Thanks! Sent from my iPhone On 31 Jul 2012, at 16:41, Clemens Lang wrote: > Hi, > > On Tue, Jul 31, 2012 at 03:13:11PM +0700, Jasper Frumau wrote: >> configure: error: C compiler cannot create executables > > you didn't install the Command Line Tools from Xcode's preferences' > downloads tab. > See: http://trac.macports.org/wiki/Migration > > -- > Clemens Lang > From jasperfrumau at gmail.com Tue Jul 31 03:27:58 2012 From: jasperfrumau at gmail.com (Jasper Frumau) Date: Tue, 31 Jul 2012 17:27:58 +0700 Subject: Upgrade of MacPorts fails In-Reply-To: <25EDF647-9C5F-45BC-AB67-8F32D10F9DCE@gmail.com> References: <25EDF647-9C5F-45BC-AB67-8F32D10F9DCE@gmail.com> Message-ID: Sent from my iPhone On 31 Jul 2012, at 15:58, Dominik Reichardt wrote: > Nit directly solving this but... > > First of all you upgraded to Mountain Lion and thus you will need to go through the migration process. Yeah. Realized I missed a step. Have to (re)install the Xcode command line tools. That should do the trick. > In my case I just nuked MacPorts, downloaded the ML installer of MacPorts and begun anew. Am also considering this. Just to get things cleaner up a bit. Thanks! > > Second, since you updated Xcode as well you need to accept the xcode license again or sime ports will fail. > > Am 31.07.2012 um 10:13 schrieb Jasper Frumau : > >> Just upgraded xCode to the latest version and upgraded to Mountain Lion. Wanted to upgrade MacPorts now as well. Got stuck: >> >> sudo port -d selfupdate >> Password: >> DEBUG: Copying /Users/jasper/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences >> DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/base >> ---> Updating MacPorts base sources using rsync >> receiving file list ... done >> ./ >> deleting config.log >> >> sent 42 bytes received 8238 bytes 1840.00 bytes/sec >> total size is 3261808 speedup is 393.94 >> MacPorts base version 2.1.1 installed, >> DEBUG: Rebuilding and reinstalling MacPorts if needed >> MacPorts base version 2.1.2 downloaded. >> ---> Updating the ports tree >> Synchronizing local ports tree from rsync://rsync.macports.org/release/ports/ >> DEBUG: /usr/bin/rsync -rtzv --delete-after '--exclude=/PortIndex*' rsync://rsync.macports.org/release/ports/ /opt/local/var/macports/sources/rsync.macports.org/release/ports >> receiving file list ... done >> ./ >> >> sent 59 bytes received 684965 bytes 13564.83 bytes/sec >> total size is 35704166 speedup is 52.12 >> DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/ports/PortIndex_darwin_12_i386/PortIndex /opt/local/var/macports/sources/rsync.macports.org/release/ports >> receiving file list ... done >> >> sent 36 bytes received 70 bytes 42.40 bytes/sec >> total size is 8547616 speedup is 80637.89 >> ---> MacPorts base is outdated, installing new version 2.1.2 >> DEBUG: Permissions OK >> Installing new MacPorts release in /opt/local as root:admin; permissions 0755; Tcl-Package in /Library/Tcl >> >> checking build system type... i386-apple-darwin12.0.0 >> checking host system type... i386-apple-darwin12.0.0 >> checking target system type... i386-apple-darwin12.0.0 >> checking MacPorts version... 2.1.2 >> checking for sw_vers... /usr/bin/sw_vers >> checking for defaults... /usr/bin/defaults >> checking for xcode-select... /usr/bin/xcode-select >> checking Mac OS X version... 10.8 >> checking Xcode location... /Applications/Xcode.app/Contents/Developer >> checking Xcode version... 4.4 >> checking for gcc... /usr/bin/cc >> checking whether the C compiler works... no >> configure: error: in `/opt/local/var/macports/sources/rsync.macports.org/release/base': >> configure: error: C compiler cannot create executables >> See `config.log' for more details >> Command failed: cd /opt/local/var/macports/sources/rsync.macports.org/release/base && CC=/usr/bin/cc ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0755 --enable-readline && make && make install SELFUPDATING=1 >> Exit code: 77 >> DEBUG: Error installing new MacPorts base: command execution failed >> while executing >> "macports::selfupdate [array get global_options] base_updated" >> Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed >> >> Any ideas how I can get MacPorts to do it all without these errors? >> >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo/macports-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From fritzs at gmx.net Tue Jul 31 04:47:30 2012 From: fritzs at gmx.net (FritzS - gmx) Date: Tue, 31 Jul 2012 13:47:30 +0200 Subject: Upgrade of MacPorts fails In-Reply-To: References: Message-ID: <385B8E0D-D3B1-4302-99FE-CDB64CE07357@gmx.net> Am 31.07.2012 um 10:13 schrieb Jasper Frumau : > Just upgraded xCode to the latest version and upgraded to Mountain Lion. Wanted to upgrade MacPorts now as well. Got stuck: I had the same problem an fix it ... I download the latest MacPorts version 2.1.2 ?pkg? installer for Mountain Lion and install them, it helps .... http://www.macports.org/install.php -- FritzS fritzs at gmx.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From phildobbin at gmail.com Tue Jul 31 04:53:03 2012 From: phildobbin at gmail.com (Phil Dobbin) Date: Tue, 31 Jul 2012 12:53:03 +0100 Subject: Terminal vim Message-ID: <5017C71F.7040101@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, all. Am I correct in thinking in order to install terminal vim with python enabled, it has to use python25? Reason I ask is I'd like to use python27 as quite a few plugins I need to use require it. Cheers, Phil... - -- But masters, remember that I am an ass. Though it be not written down, yet forget not that I am an ass. Wm. Shakespeare - Much Ado About Nothing -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: ??auto-key-locate cert pka ldap hkp://keys.gnupg.net Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQF8ceAAoJEKuJdOaOnmMJdGUH/jhAwZcVJZKZAQrzY7snWOjw 96rycPhu+dRUhezgnlqdLi5ql5HUqHkd+z6M7q2DhSZ1ioVQt2WPsODbZ0mew6ei hGwQxDRYvvuKOQwqfDtlpXzB3Ld8TwAO0hxduBM77fAk8NQIg8gZELXgZJRX15LC 1rMe73lCFoyZgNrfb6nhL41HVGmULNUSAaWn/g0lNs5bY63Eqggdh7C2YWcmkp1Z D30j+vkjHe+4Lo/2Fz8kweJg1/4hVTURr6mUMWipG3C6/KIiF2lskKUJB3fs+6pL zPGi+5o6+L2OXOazt747sWwFOVM8qdGXFGSX7+e8hsCpT39GpMecXw1ZHOSneqQ= =iaai -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3865 bytes Desc: S/MIME Cryptographic Signature URL: From fritzs at gmx.net Tue Jul 31 04:59:03 2012 From: fritzs at gmx.net (FritzS - gmx) Date: Tue, 31 Jul 2012 13:59:03 +0200 Subject: Upgrade of MacPorts fails In-Reply-To: <25EDF647-9C5F-45BC-AB67-8F32D10F9DCE@gmail.com> References: <25EDF647-9C5F-45BC-AB67-8F32D10F9DCE@gmail.com> Message-ID: Am 31.07.2012 um 10:58 schrieb Dominik Reichardt : > Second, since you updated Xcode as well you need to accept the xcode license again or sime ports will fail. And don't forget to install the Xcode Command Line Tools You will find them: Xcode / Preferences / Downloads / Components Xcode accept license sudo xcodebuild -license -- FritzS fritzs at gmx.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasperfrumau at gmail.com Tue Jul 31 05:04:07 2012 From: jasperfrumau at gmail.com (Jasper Frumau) Date: Tue, 31 Jul 2012 19:04:07 +0700 Subject: Upgrade of MacPorts fails In-Reply-To: References: <25EDF647-9C5F-45BC-AB67-8F32D10F9DCE@gmail.com> Message-ID: On Tue, Jul 31, 2012 at 6:59 PM, FritzS - gmx wrote: > > Am 31.07.2012 um 10:58 schrieb Dominik Reichardt : > > Second, since you updated Xcode as well you need to accept the xcode > license again or sime ports will fail. > > > And don't forget to install the Xcode Command Line Tools > That is what was the issue. Thanks for the information! > > You will find them: Xcode / Preferences / Downloads / Components > > Xcode accept license > sudo xcodebuild -license > > > -- > FritzS > fritzs at gmx.net > > > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cal at macports.org Tue Jul 31 05:46:19 2012 From: cal at macports.org (Clemens Lang) Date: Tue, 31 Jul 2012 14:46:19 +0200 Subject: Terminal vim In-Reply-To: <5017C71F.7040101@gmail.com> References: <5017C71F.7040101@gmail.com> Message-ID: <20120731124619.GA21792@towel.neverpanic.de> Hi, On Tue, Jul 31, 2012 at 12:53:03PM +0100, Phil Dobbin wrote: > Am I correct in thinking in order to install terminal vim with python > enabled, it has to use python25? No. > Reason I ask is I'd like to use python27 as quite a few plugins I need > to use require it. You can use the +python27 variant. See `port variants vim`. -- Clemens Lang From phildobbin at gmail.com Tue Jul 31 05:54:03 2012 From: phildobbin at gmail.com (Phil Dobbin) Date: Tue, 31 Jul 2012 13:54:03 +0100 Subject: Terminal vim In-Reply-To: <20120731124619.GA21792@towel.neverpanic.de> References: <5017C71F.7040101@gmail.com> <20120731124619.GA21792@towel.neverpanic.de> Message-ID: <5017D56B.6010404@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Clemens Lang wrote: > On Tue, Jul 31, 2012 at 12:53:03PM +0100, Phil Dobbin wrote: >> Am I correct in thinking in order to install terminal vim with >> python enabled, it has to use python25? > > No. > >> Reason I ask is I'd like to use python27 as quite a few plugins I >> need to use require it. > > You can use the +python27 variant. See `port variants vim`. Hi, Clemens. Port variants says: `python: Compatibility variant, requires +python25` which is the reason I asked about it. Cheers, Phil... - -- But masters, remember that I am an ass. Though it be not written down, yet forget not that I am an ass. Wm. Shakespeare - Much Ado About Nothing -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: ??auto-key-locate cert pka ldap hkp://keys.gnupg.net Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQF9VrAAoJEKuJdOaOnmMJLbEIALCX6srWGzBCaV8kXN8p3TBz fUKsJBfemmfYvJHuRFQRTUvBzZnwCWo1a4yrL49RKYh/tK+oL6KCu7WGALFtBR9N wCX7c8r5UcIA0bJgfOW7LRqBOlJEUqjq7NsrSt6b1bvb0fn9WUR0z6Tv/YNOp4kt vVc6JSORTDhO32E+gxNh9Wx6h+7b1svCBDJqCBj5nu3WRBU8qiFHjEtunFvPm7aZ tBKIP8jTYdcEU59F/w1ji2x29JleWSTFVjeTySG8GcNTU9qq6BXi+zVZzvXqRDc5 eRPBnEtsVqgWTwhrAX3/3D+SB9EPMde0YES3dU04S3+ArlE2drwdGZOM9raBsKE= =vdst -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3865 bytes Desc: S/MIME Cryptographic Signature URL: From jeremy at lavergne.gotdns.org Tue Jul 31 06:01:14 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Tue, 31 Jul 2012 09:01:14 -0400 Subject: Terminal vim In-Reply-To: <5017D56B.6010404@gmail.com> References: <5017C71F.7040101@gmail.com> <20120731124619.GA21792@towel.neverpanic.de> <5017D56B.6010404@gmail.com> Message-ID: <17D68242-F503-4400-B478-94103EAAF486@lavergne.gotdns.org> > Port variants says: > > `python: Compatibility variant, requires +python25` > > which is the reason I asked about it. That's a "backwards compatibility" variant. Nothing to see there. From ctreleaven at cogeco.ca Tue Jul 31 06:10:31 2012 From: ctreleaven at cogeco.ca (Craig Treleaven) Date: Tue, 31 Jul 2012 09:10:31 -0400 Subject: Terminal vim In-Reply-To: <5017D56B.6010404@gmail.com> References: <5017C71F.7040101@gmail.com> <20120731124619.GA21792@towel.neverpanic.de> <5017D56B.6010404@gmail.com> Message-ID: At 1:54 PM +0100 7/31/12, Phil Dobbin wrote: >Clemens Lang wrote: > > On Tue, Jul 31, 2012 at 12:53:03PM +0100, Phil Dobbin wrote: >>> Am I correct in thinking in order to install terminal vim with >>> python enabled, it has to use python25? >> >> No. >> >>> Reason I ask is I'd like to use python27 as quite a few plugins I >>> need to use require it. >> > > You can use the +python27 variant. See `port variants vim`. >Port variants says: > >`python: Compatibility variant, requires +python25` > >which is the reason I asked about it. vim has quite a list of variants, including various versions of python: > > port variants vim >vim has the variants: > athena: Build GUI version using Athena widgets > * conflicts with gtk1 gtk2 motif > * requires x11 > big: Build big feature set > * conflicts with small tiny > cscope: Enable source code browsing with cscope > gtk1: Build GUI version using GTK 1.x widgets > * conflicts with athena gtk2 motif > * requires x11 > gtk2: Build GUI version using GTK 2.x widgets > * conflicts with athena gtk1 motif > * requires x11 > huge: Build huge feature set > * conflicts with big small tiny > motif: Build GUI version with Motif widgets > * conflicts with athena gtk1 gtk2 > * requires x11 > perl: Enable Perl scripting > python: Compatibility variant, requires +python25 > * requires python25 > python25: Enable Python scripting > * conflicts with python26 python27 > python26: Enable Python scripting > * conflicts with python25 python27 > python27: Enable Python scripting > * conflicts with python25 python26 > python31: Enable Python scripting > * conflicts with python32 > python32: Enable Python scripting > * conflicts with python31 > ruby: Enable Ruby scripting > small: Build small feature set > * conflicts with tiny > tcl: Enable Tcl scripting > tiny: Build tiny feature set > universal: Build for multiple architectures > x11: Build CLI version with X support > xim: Build with support for X Input Method So it still appears you want "+python27". Craig From arno at alum.wpi.edu Tue Jul 31 07:55:45 2012 From: arno at alum.wpi.edu (Arno Hautala) Date: Tue, 31 Jul 2012 10:55:45 -0400 Subject: -p considered problematic (was Re: how to proceed past errors?) Message-ID: On Thu, Jul 26, 2012 at 12:43 PM, Jeremy Huddleston Sequoia wrote: > > On Jul 26, 2012, at 09:41, "Daniel J. Luke" wrote: > >> From the man page: >> >> -p Despite any errors encountered, proceed to process multiple >> ports and commands. > > That is *very* problematic. Don't do it unless you really, really, really know what it implies. Why is this considered problematic? My understanding is that this won't allow a port to be installed if it's dependencies fail, but will continue to build as many requested ports as is possible. ie: port-a depends on port-b, port-c, and port-d > port install port-a would install port -b, port-c fails, and port stops > port -p install port-a would install port-b, port-c fails, install port-d, doesn't install port-a because deps aren't satisfied. I've been using this flag in an automated process for quite some time. What problems should I be aware of with using this switch? -- arno s hautala /-| arno at alum.wpi.edu pgp b2c9d448 From jeremy at lavergne.gotdns.org Tue Jul 31 08:05:46 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Tue, 31 Jul 2012 11:05:46 -0400 Subject: -p considered problematic (was Re: how to proceed past errors?) In-Reply-To: References: Message-ID: > Why is this considered problematic? My understanding is that this > won't allow a port to be installed if it's dependencies fail, but will > continue to build as many requested ports as is possible. > > ie: port-a depends on port-b, port-c, and port-d > >> port install port-a > > would install port -b, port-c fails, and port stops > >> port -p install port-a > > would install port-b, port-c fails, install port-d, doesn't install > port-a because deps aren't satisfied. > > I've been using this flag in an automated process for quite some time. > What problems should I be aware of with using this switch? The only issue that comes to mind is missing/incorrect dependencies. A package may install (from binary or source) but there may be issues because it built or rebuilt differently based on availability of an opportunist dependency. We've seen some maintainers write library dependencies as build dependencies, which of course would be missing when installing in the default, binary mode. There's also the case where a dependency was already installed on the developer's machine and the software would link opportunistically with it: this results in no error for anyone but may result in missing functionality. I don't think that's a problem with -p, however it will be more likely to manifest itself that way; it's more of a bug with the port that's allowing that opportunist linking or otherwise incorrectly declared dependencies. From arno at alum.wpi.edu Tue Jul 31 08:38:45 2012 From: arno at alum.wpi.edu (Arno Hautala) Date: Tue, 31 Jul 2012 11:38:45 -0400 Subject: -p considered problematic (was Re: how to proceed past errors?) In-Reply-To: References: Message-ID: On Tue, Jul 31, 2012 at 11:05 AM, Jeremy Lavergne wrote: > > I don't think that's a problem with -p, however it will be more likely to manifest itself that way; it's more of a bug with the port that's allowing that opportunist linking or otherwise incorrectly declared dependencies. Gotcha, thanks. -- arno s hautala /-| arno at alum.wpi.edu pgp b2c9d448 From fritzs at gmx.net Tue Jul 31 08:44:40 2012 From: fritzs at gmx.net (FritzS - gmx) Date: Tue, 31 Jul 2012 17:44:40 +0200 Subject: [Mountain Lion] gimp installation fails Message-ID: Hi, my gimp (or gimp2) installation on Mountain Lion fails on: ---> Building gimp-help-en Error: org.macports.build for port gimp-help-en returned: command execution failed Please see the log file for port gimp-help-en for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp-help-en/gimp-help-en/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port gimp-help-en failed install gimp or install gimp2 hangs on the same point About this hint https://trac.macports.org/ticket/35285 what should I do on my system? Please look for this tracks too https://trac.macports.org/ticket/35283 #35378: w3m: sed: RE error: illegal byte sequence #35405: w3m: sed: RE error: illegal byte sequence #35364: some applications want run #35356: macports won't work after upgrade to MountainLion -- FritzS fritzs at gmx.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremyhu at macports.org Tue Jul 31 09:17:12 2012 From: jeremyhu at macports.org (Jeremy Huddleston Sequoia) Date: Tue, 31 Jul 2012 09:17:12 -0700 Subject: -p considered problematic (was Re: how to proceed past errors?) In-Reply-To: References: Message-ID: <42A8AEF8-30FF-4D56-84BD-9558156D2A6C@macports.org> On Jul 31, 2012, at 7:55 AM, Arno Hautala wrote: > On Thu, Jul 26, 2012 at 12:43 PM, Jeremy Huddleston Sequoia > wrote: >> >> On Jul 26, 2012, at 09:41, "Daniel J. Luke" wrote: >> >>> From the man page: >>> >>> -p Despite any errors encountered, proceed to process multiple >>> ports and commands. >> >> That is *very* problematic. Don't do it unless you really, really, really know what it implies. > > Why is this considered problematic? My understanding is that this > won't allow a port to be installed if it's dependencies fail, but will > continue to build as many requested ports as is possible. > > ie: port-a depends on port-b, port-c, and port-d > >> port install port-a > > would install port -b, port-c fails, and port stops > >> port -p install port-a > > would install port-b, port-c fails, install port-d, doesn't install > port-a because deps aren't satisfied. > > I've been using this flag in an automated process for quite some time. > What problems should I be aware of with using this switch? IIRC, the OP was talking about upgrade, not install. So in your case, you would have: port -p upgrade upgrade port-a This is problematic because port-a will be upgraded even through port-d failed. If port-a was rev-bumped specifically because of port-d to force a rebuild after the port-d install, this will thwart that. Luckily, rev-upgrade now exists to work around such issues these days, but I still do not recommended '-p upgrade' --Jeremy From jeremy at lavergne.gotdns.org Tue Jul 31 09:24:46 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Tue, 31 Jul 2012 12:24:46 -0400 Subject: -p considered problematic (was Re: how to proceed past errors?) In-Reply-To: <42A8AEF8-30FF-4D56-84BD-9558156D2A6C@macports.org> References: <42A8AEF8-30FF-4D56-84BD-9558156D2A6C@macports.org> Message-ID: <79AA7A3B-3AF1-4FE0-AD50-E58F0077186E@lavergne.gotdns.org> > IIRC, the OP was talking about upgrade, not install. So in your case, you would have: > > port -p upgrade upgrade port-a > > This is problematic because port-a will be upgraded even through port-d failed. If port-a was rev-bumped specifically because of port-d to force a rebuild after the port-d install, this will thwart that. Luckily, rev-upgrade now exists to work around such issues these days, but I still do not recommended '-p upgrade' Ah good point, I forgot they were doing an upgrade rather than install. From arno at alum.wpi.edu Tue Jul 31 09:28:04 2012 From: arno at alum.wpi.edu (Arno Hautala) Date: Tue, 31 Jul 2012 12:28:04 -0400 Subject: -p considered problematic (was Re: how to proceed past errors?) In-Reply-To: <42A8AEF8-30FF-4D56-84BD-9558156D2A6C@macports.org> References: <42A8AEF8-30FF-4D56-84BD-9558156D2A6C@macports.org> Message-ID: On Tue, Jul 31, 2012 at 12:17 PM, Jeremy Huddleston Sequoia wrote: > > IIRC, the OP was talking about upgrade, not install. So in your case, you would have: > > port -p upgrade upgrade port-a > > This is problematic because port-a will be upgraded even through port-d failed. If port-a was rev-bumped specifically because of port-d to force a rebuild after the port-d install, this will thwart that. Luckily, rev-upgrade now exists to work around such issues these days, but I still do not recommended '-p upgrade' Ah, good point. So if '-p upgrade' causes such a problem, upgraded port-a, outdated and incompatible port-d, does rev-upgrade leave the now broken port-a in place if port-d and port-a can't be properly built? Or does it leave the broken port? I've watched rev-upgrade before, but I can't remember if it uninstalls the broken ports before rebuilding or if it only uninstalls them when the rebuild succeeds. Thanks, --Arno -- arno s hautala /-| arno at alum.wpi.edu pgp b2c9d448 From cal at macports.org Tue Jul 31 09:40:54 2012 From: cal at macports.org (Clemens Lang) Date: Tue, 31 Jul 2012 18:40:54 +0200 Subject: -p considered problematic (was Re: how to proceed past errors?) In-Reply-To: References: <42A8AEF8-30FF-4D56-84BD-9558156D2A6C@macports.org> Message-ID: <20120731164054.GB21792@towel.neverpanic.de> Hi, On Tue, Jul 31, 2012 at 12:28:04PM -0400, Arno Hautala wrote: > I've watched rev-upgrade before, but I can't remember if it uninstalls > the broken ports before rebuilding or if it only uninstalls them when > the rebuild succeeds. it mimics port -n upgrade --force broken-port, so no, it doesn't keep the broken port and only replaces it if the build succeeds. I've thought about this previously and it's an improvement worth adding, IMHO. -- Clemens Lang From jeremyhu at macports.org Tue Jul 31 09:51:18 2012 From: jeremyhu at macports.org (Jeremy Huddleston Sequoia) Date: Tue, 31 Jul 2012 09:51:18 -0700 Subject: -p considered problematic (was Re: how to proceed past errors?) In-Reply-To: References: <42A8AEF8-30FF-4D56-84BD-9558156D2A6C@macports.org> Message-ID: <9E144411-F2F1-428D-B61B-0DAB64F1B1D6@macports.org> rev-upgrade will notice if a port is linking against something that doesn't exist, uninstall it, and re-install it. In my example, port-d installed a new version of the library with a new name causing port-a to not link against it any more, so port-a was rev-bumped. Someone using -p when port-d failed to upgrade would upgrade port-a against the old name. When port-d gets fixed to install properly, it will install the new dylib name, and port-a will be broken. rev-upgrade will notice that, uninstall port-a, and re-install port-a. --Jeremy On Jul 31, 2012, at 9:28 AM, Arno Hautala wrote: > On Tue, Jul 31, 2012 at 12:17 PM, Jeremy Huddleston Sequoia > wrote: >> >> IIRC, the OP was talking about upgrade, not install. So in your case, you would have: >> >> port -p upgrade upgrade port-a >> >> This is problematic because port-a will be upgraded even through port-d failed. If port-a was rev-bumped specifically because of port-d to force a rebuild after the port-d install, this will thwart that. Luckily, rev-upgrade now exists to work around such issues these days, but I still do not recommended '-p upgrade' > > Ah, good point. So if '-p upgrade' causes such a problem, upgraded > port-a, outdated and incompatible port-d, does rev-upgrade leave the > now broken port-a in place if port-d and port-a can't be properly > built? Or does it leave the broken port? > > I've watched rev-upgrade before, but I can't remember if it uninstalls > the broken ports before rebuilding or if it only uninstalls them when > the rebuild succeeds. > > Thanks, > --Arno > > > -- > arno s hautala /-| arno at alum.wpi.edu > > pgp b2c9d448 From ryandesign at macports.org Tue Jul 31 13:58:39 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 31 Jul 2012 15:58:39 -0500 Subject: [Mountain Lion] gimp installation fails In-Reply-To: References: Message-ID: On Jul 31, 2012, at 10:44, FritzS - gmx wrote: > ---> Building gimp-help-en > Error: org.macports.build for port gimp-help-en returned: command execution failed > Please see the log file for port gimp-help-en for details: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp-help-en/gimp-help-en/main.log > To report a bug, follow the instructions in the guide: > http://guide.macports.org/#project.tickets > Error: Processing of port gimp-help-en failed > > install gimp or > install gimp2 > hangs on the same point > > About this hint > https://trac.macports.org/ticket/35285 > what should I do on my system? I've fixed this and resolved this ticket. > Please look for this tracks too > https://trac.macports.org/ticket/35283 I've fixed this as well and resolved this ticket. > #35378: w3m: sed: RE error: illegal byte sequence > #35405: w3m: sed: RE error: illegal byte sequence These are duplicates of #35080 which was fixed. > #35364: some applications want run > #35356: macports won't work after upgrade to MountainLion These were closed as invalid days ago already. From ctreleaven at cogeco.ca Tue Jul 31 14:54:41 2012 From: ctreleaven at cogeco.ca (Craig Treleaven) Date: Tue, 31 Jul 2012 17:54:41 -0400 Subject: Monitoring Internet Usage Message-ID: Hi: I want to be able to monitor internet usage from my son's Mac*. (Top 5 applications by MB transferred; maybe top 20 internet addresses, etc.) I think there was a commit in the last couple of weeks to a port that did just that--but, of course, I can't find it now. Craig *We keep blowing through our GB cap and the overage charge was $50 on the last bill!! Since there is 4 of us in the house, I've never been clear on how much data he uses. Hover, he has been away at camp the last 4 weeks and our GB usage is down by 2/3! From phildobbin at gmail.com Tue Jul 31 16:10:18 2012 From: phildobbin at gmail.com (Phil Dobbin) Date: Wed, 01 Aug 2012 00:10:18 +0100 Subject: Monitoring Internet Usage In-Reply-To: References: Message-ID: <501865DA.5000103@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Craig Treleaven wrote: > I want to be able to monitor internet usage from my son's Mac*. (Top 5 > applications by MB transferred; maybe top 20 internet addresses, etc.) > I think there was a commit in the last couple of weeks to a port that > did just that--but, of course, I can't find it now. > > Craig > > *We keep blowing through our GB cap and the overage charge was $50 on > the last bill!! Since there is 4 of us in the house, I've never been > clear on how much data he uses. Hover, he has been away at camp the > last 4 weeks and our GB usage is down by 2/3! If you have a router, it's probably easier to cap his bandwidth. Cheers, Phil... - -- But masters, remember that I am an ass. Though it be not written down, yet forget not that I am an ass. Wm. Shakespeare - Much Ado About Nothing -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: ??auto-key-locate cert pka ldap hkp://keys.gnupg.net Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQGGXaAAoJEKuJdOaOnmMJ5ckH/A85s1Zju4uBy1Xr1qNvLleG OujVzllSTLA7KiSN8HtNb2bU09sjuyqc/ySyQk4iIWdmSa2uh2NFoSd02sxsmMvf GNk+njkf96op/DcTrr3h+NXyKoMLJc3eNeX4YX0JOiOyCcbs+sdr1uYBDF3P5WyH MvYX4oW3iPS5d4YaPWoJI4ioImTI6/FIbkT5gxmle+7DhG8RWezfWmma/KJzMtTC iqyCmoesWmigzbrCpTNdEze06MD6las0usC9OOPF13o1FuGOKiGJ/tpDeiTU4R4I iL5B2gKI28fofRa2biXH1q1CUOraBLylGWh+va7KCFSBU5jYiOKgfGgL/f7b4lA= =Gm/s -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3865 bytes Desc: S/MIME Cryptographic Signature URL: From jeremy at lavergne.gotdns.org Tue Jul 31 16:13:13 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Tue, 31 Jul 2012 19:13:13 -0400 Subject: Monitoring Internet Usage In-Reply-To: References: Message-ID: > I want to be able to monitor internet usage from my son's Mac*. (Top 5 applications by MB transferred; maybe top 20 internet addresses, etc.) I think there was a commit in the last couple of weeks to a port that did just that--but, of course, I can't find it now. Apart from finding that app, you could log the size of all HTTP requests using squid. Or suggest your son get his own connection. :-) From ctreleaven at cogeco.ca Tue Jul 31 17:12:29 2012 From: ctreleaven at cogeco.ca (Craig Treleaven) Date: Tue, 31 Jul 2012 20:12:29 -0400 Subject: Monitoring Internet Usage In-Reply-To: <501865DA.5000103@gmail.com> References: <501865DA.5000103@gmail.com> Message-ID: At 12:10 AM +0100 8/1/12, Phil Dobbin wrote: >Craig Treleaven wrote: > >> I want to be able to monitor internet usage from my son's Mac*. (Top 5 >> applications by MB transferred; maybe top 20 internet addresses, etc.) >> I think there was a commit in the last couple of weeks to a port that > > did just that--but, of course, I can't find it now. > > > > Craig > > >> *We keep blowing through our GB cap and the overage charge was $50 on >> the last bill!! Since there is 4 of us in the house, I've never been >> clear on how much data he uses. Hover, he has been away at camp the >> last 4 weeks and our GB usage is down by 2/3! > >If you have a router, it's probably easier to cap his bandwidth. > I'd like to understand what is using all this bandwidth. He was running torrents for a while but I believe he stopped months ago. He talks to friends on Skype. He plays a couple of online games which occasionally have enormous updates. Some YouTube. Lots of Facebook and other lower-bandwidth stuff. It seems that he is going through 40-70 GB per month by himself and I really don't understand what he's doing that is consuming all that data. BTW, with my D-Link router, I think I can limit his network use to certain times of the day (and block specific web sites) but I don't think I can "cap" his bandwidth. Craig From sam.kuper at uclmail.net Tue Jul 31 17:18:01 2012 From: sam.kuper at uclmail.net (Sam Kuper) Date: Wed, 1 Aug 2012 01:18:01 +0100 Subject: Monitoring Internet Usage In-Reply-To: References: <501865DA.5000103@gmail.com> Message-ID: On 1 August 2012 01:12, Craig Treleaven wrote: > ... BTW, with my D-Link router, I think I can limit his network use to > certain times of the day (and block specific web sites) but I don't think I > can "cap" his bandwidth. > OpenWRT, DD-RT, Tomato or suchlike might be installable on your router, and may be able to give you this power. Sam -------------- next part -------------- An HTML attachment was scrubbed... URL: From ctreleaven at cogeco.ca Tue Jul 31 17:34:47 2012 From: ctreleaven at cogeco.ca (Craig Treleaven) Date: Tue, 31 Jul 2012 20:34:47 -0400 Subject: Monitoring Internet Usage In-Reply-To: References: <501865DA.5000103@gmail.com> Message-ID: At 1:18 AM +0100 8/1/12, Sam Kuper wrote: >On 1 August 2012 01:12, Craig Treleaven ><ctreleaven at cogeco.ca> wrote: > >... BTW, with my D-Link router, I think I can limit his network use >to certain times of the day (and block specific web sites) but I >don't think I can "cap" his bandwidth. > > >OpenWRT, DD-RT, Tomato or suchlike might be installable on your >router, and may be able to give you this power. Unfortunately, none of those appear to work with my specific router. I'm reluctant to experiment since my wife uses VPN to connect to work on a regular basis. Craig -------------- next part -------------- An HTML attachment was scrubbed... URL: From iandw.au at gmail.com Tue Jul 31 20:03:32 2012 From: iandw.au at gmail.com (Ian Wadham) Date: Wed, 1 Aug 2012 13:03:32 +1000 Subject: How to set C++ compiler outside Macports? In-Reply-To: <3753B5C8-1E60-4D42-943B-8F19F06A29E9@macports.org> References: <04B03595-6682-44A5-8877-BE7F0BFB8E0C@macports.org> <3753B5C8-1E60-4D42-943B-8F19F06A29E9@macports.org> Message-ID: On 30/07/2012, at 2:54 AM, Ryan Schmidt wrote: > Probably the usual CC and CXX environment variables could be used to influence that. Thanks, Ryan. I have set those up in my CMake script now. >> Is use of clang now official Macports policy? Last I heard on this list, a >> few months back, its use was experimental. > > The compiler MacPorts uses by default is chosen based on the Xcode version. > > Xcode 2.x: gcc-4.0 > Xcode 3.x: gcc-4.2 > Xcode 4.0 and 4.1: llvm-gcc-4.2 > Xcode 4.2 and up: clang Thanks again, Ryan. I have passed that information on to the KDE developers. It turns out that the KDE project is intending to move to clang in the future but is not ready for it yet. Its build macros do not generate the right settings of clang. It is OK to build KDE modules with clang, but if you build one that way you must build the lot with clang. I was not building my own code with clang, hence my problems. When clang is used to build KDE modules, many more symbols than necessary are exported. That is harmless, but will lead to larger object files than necessary. Please would you close https://trac.macports.org/ticket/34605 now (I do not seem to have the right access). I have included there a summary and a link to the details of what the KDE build-system developer had to say. I hope the KDE port guys will have a look. All the best, Ian W. From fritzs at gmx.net Tue Jul 31 21:51:08 2012 From: fritzs at gmx.net (FritzS - gmx) Date: Wed, 1 Aug 2012 06:51:08 +0200 Subject: Processing of port gimp-help-en failed, was: [Mountain Lion] gimp installation fails In-Reply-To: References: Message-ID: Am 31.07.2012 um 22:58 schrieb Ryan Schmidt : > On Jul 31, 2012, at 10:44, FritzS - gmx wrote: > >> ---> Building gimp-help-en >> Error: org.macports.build for port gimp-help-en returned: command execution failed >> Please see the log file for port gimp-help-en for details: >> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp-help-en/gimp-help-en/main.log >> To report a bug, follow the instructions in the guide: >> http://guide.macports.org/#project.tickets >> Error: Processing of port gimp-help-en failed >> >> install gimp or >> install gimp2 >> hangs on the same point >> >> About this hint >> https://trac.macports.org/ticket/35285 >> what should I do on my system? > > I've fixed this and resolved this ticket. > > >> Please look for this tracks too >> https://trac.macports.org/ticket/35283 > > I've fixed this as well and resolved this ticket. > > >> #35378: w3m: sed: RE error: illegal byte sequence >> #35405: w3m: sed: RE error: illegal byte sequence > > These are duplicates of #35080 which was fixed. > > >> #35364: some applications want run >> #35356: macports won't work after upgrade to MountainLion > > These were closed as invalid days ago already. Hi Ryan, I read all and done all what you tell I should do But the gimp installation hangs an gimp-help-en too Please, please help me to get a gimp installation. I am not a port or Linux guru. Today I run bash-3.2$ sudo port -v selfupdate bash-3.2$ sudo port -v upgrade outdated bash-3.2$ sudo port clean --all installed bash-3.2$ sudo port -f uninstall gimp-help-en bash-3.2$ sudo port -s install gimp-help-en configure.args=--without-gimp But it fails again, what should I do now? I make a new clean ticket. https://trac.macports.org/ticket/35461 the logfile https://trac.macports.org/attachment/ticket/35461/main-help-en-ver4.log I use ML 10.8, Xcode 4.4, MacPorts 2.1.2 -- FritzS fritzs at gmx.net From jeremy at lavergne.gotdns.org Tue Jul 31 22:05:51 2012 From: jeremy at lavergne.gotdns.org (Jeremy Lavergne) Date: Wed, 1 Aug 2012 01:05:51 -0400 Subject: Processing of port gimp-help-en failed, was: [Mountain Lion] gimp installation fails In-Reply-To: References: Message-ID: <811F8D33-3C69-4EF3-8A57-AB0B423A577A@lavergne.gotdns.org> > But it fails again, what should I do now? > > I make a new clean ticket. > https://trac.macports.org/ticket/35461 > the logfile > https://trac.macports.org/attachment/ticket/35461/main-help-en-ver4.log > > I use ML 10.8, Xcode 4.4, MacPorts 2.1.2 This was not a clean install: :debug:main Skipping completed org.macports.configure (gimp-help-en) :debug:main Privilege de-escalation not attempted as not running as root. :debug:build build phase started at Wed Aug 1 06:24:43 CEST 2012 :notice:build ---> Building gimp-help-en Configure phase should not be skipped. `sudo port clean gimp-help-en` then try again, then attach the log to that ticket. Also, indicate if libxml2 is installed: `port installed libxml2` And seriously, don't use priority flags in emails for distribution lists. Tech-oriented people are likely to immediately trash such emails--if the list doesn't automatically. From spooky130u at gmail.com Tue Jul 31 22:13:21 2012 From: spooky130u at gmail.com (Jim Graham) Date: Wed, 1 Aug 2012 00:13:21 -0500 Subject: Processing of port gimp-help-en failed, was: [Mountain Lion] gimp installation fails In-Reply-To: References: Message-ID: <20120801051321.GA51706@gmail.com> On Wed, Aug 01, 2012 at 06:51:08AM +0200, FritzS - gmx wrote: > Am 31.07.2012 um 22:58 schrieb Ryan Schmidt : > > On Jul 31, 2012, at 10:44, FritzS - gmx wrote: > >> ---> Building gimp-help-en > >> Error: org.macports.build for port gimp-help-en returned: command execution failed > >> Please see the log file for port gimp-help-en for details: > >> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp-help-en/gimp-help-en/main.log > >> To report a bug, follow the instructions in the guide: > >> http://guide.macports.org/#project.tickets > >> Error: Processing of port gimp-help-en failed Hmmmm, this looks oddly familiar. In fact, it's EXACTLY what I'm seeing. > > I've fixed this and resolved this ticket. Oh, ok. Well, I just did a port selfupdate, and I'm still getting the same error. Also, what variant do I use to get gimpshop? > >> #35356: macports won't work after upgrade to MountainLion For what it's worth, I have not upgraded, and until I have the money to buy a BIG (at least 2--4 TB, as it will not be exclusively for backups, it'll be partitioned for other stuff, too) external drive to do a full backup, there's no chance that I will. > > These were closed as invalid days ago already. > Please, please help me to get a gimp installation. And for me, please extend that to include gimpshop. Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) | "> There it was, right in the title bar: spooky130u at gmail.com | > Microsoft Operations POS." < Running Mac OS X Lion > | ICBM / Hurricane: | "Never before has a TLA been so appropriately 30.44406N 86.59909W | mis-parsed." (alt.sysadmin.recovery) Android Apps Listing at http://www.jstrack.org/barcodes.html From fritzs at gmx.net Tue Jul 31 22:37:19 2012 From: fritzs at gmx.net (FritzS - gmx) Date: Wed, 1 Aug 2012 07:37:19 +0200 Subject: Processing of port gimp-help-en failed, was: [Mountain Lion] gimp installation fails In-Reply-To: <811F8D33-3C69-4EF3-8A57-AB0B423A577A@lavergne.gotdns.org> References: <811F8D33-3C69-4EF3-8A57-AB0B423A577A@lavergne.gotdns.org> Message-ID: <5AB752DF-9C80-43EA-AEA5-E780CB4029CD@gmx.net> Am 01.08.2012 um 07:05 schrieb Jeremy Lavergne : >> But it fails again, what should I do now? >> >> I make a new clean ticket. >> https://trac.macports.org/ticket/35461 >> the logfile >> https://trac.macports.org/attachment/ticket/35461/main-help-en-ver4.log >> >> I use ML 10.8, Xcode 4.4, MacPorts 2.1.2 > > This was not a clean install: > :debug:main Skipping completed org.macports.configure (gimp-help-en) > :debug:main Privilege de-escalation not attempted as not running as root. > :debug:build build phase started at Wed Aug 1 06:24:43 CEST 2012 > :notice:build ---> Building gimp-help-en > > Configure phase should not be skipped. > > `sudo port clean gimp-help-en` then try again, then attach the log to that ticket. > > Also, indicate if libxml2 is installed: `port installed libxml2` This I don now bash-3.2$ sudo port -f uninstall gimp-help-en Password: bash-3.2$ sudo port clean gimp-help-en ---> Cleaning gimp-help-en bash-3.2$ sudo port -s install gimp-help-en configure.args=--without-gimp ---> Computing dependencies for gimp-help-en ---> Fetching distfiles for gimp-help-en ---> Verifying checksum(s) for gimp-help-en ---> Extracting gimp-help-en ---> Configuring gimp-help-en ---> Building gimp-help-en Error: org.macports.build for port gimp-help-en returned: command execution failed Please see the log file for port gimp-help-en for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp-help-en/gimp-help-en/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port gimp-help-en failed bash-3.2$ port installed libxml2 The following ports are currently installed: libxml2 @2.7.8_0 (active) https://trac.macports.org/ticket/35461#comment:3 > And seriously, don't use priority flags in emails for distribution lists. Tech-oriented people are likely to immediately trash such emails--if the list doesn't automatically. > ops ... mea culpa .... sorry .... but I am confuse abut this errors .... under Lion ports works well, but after upgrade to ML one error after the other .... -- FritzS fritzs at gmx.net From ryandesign at macports.org Tue Jul 31 23:03:45 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 1 Aug 2012 01:03:45 -0500 Subject: Processing of port gimp-help-en failed, was: [Mountain Lion] gimp installation fails In-Reply-To: <5AB752DF-9C80-43EA-AEA5-E780CB4029CD@gmx.net> References: <811F8D33-3C69-4EF3-8A57-AB0B423A577A@lavergne.gotdns.org> <5AB752DF-9C80-43EA-AEA5-E780CB4029CD@gmx.net> Message-ID: On Aug 1, 2012, at 00:37, FritzS - gmx wrote: > https://trac.macports.org/ticket/35461#comment:3 You just need to clean and "sudo port selfupdate" to receive the fix we already committed for this earlier. > under Lion ports works well, but after upgrade to ML one error after the other ?. And we will try to help you in fixing each of the errors as they're reported to us. That's the best we can do. Note that these errors with gimp-help-en aren't actually Mountain Lion-specific; you'd see them on other OS versions too, if you didn't happen to already have the needed dependencies installed. From ryandesign at macports.org Tue Jul 31 23:10:01 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 1 Aug 2012 01:10:01 -0500 Subject: Processing of port gimp-help-en failed In-Reply-To: <20120801051321.GA51706@gmail.com> References: <20120801051321.GA51706@gmail.com> Message-ID: On Aug 1, 2012, at 00:13, Jim Graham wrote: > On Wed, Aug 01, 2012 at 06:51:08AM +0200, FritzS - gmx wrote: >> Am 31.07.2012 um 22:58 schrieb Ryan Schmidt : >>> On Jul 31, 2012, at 10:44, FritzS - gmx wrote: > >>>> ---> Building gimp-help-en >>>> Error: org.macports.build for port gimp-help-en returned: command execution failed >>>> Please see the log file for port gimp-help-en for details: >>>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp-help-en/gimp-help-en/main.log >>>> To report a bug, follow the instructions in the guide: >>>> http://guide.macports.org/#project.tickets >>>> Error: Processing of port gimp-help-en failed > > Hmmmm, this looks oddly familiar. In fact, it's EXACTLY what I'm seeing. The above doesn't actually say very much. It just says gimp-help-en failed to build, but it doesn't say why; to learn why, we'd have to read the main.log. So we don't know, just based on the above, that you were seeing the same error as FritzS. >>> I've fixed this and resolved this ticket. > > Oh, ok. Well, I just did a port selfupdate, and I'm still getting the > same error. If you're sure you've cleaned gimp-help-en, and run selfupdate, and you're still getting a build failure, then please file a bug report in the issue tracker. However, I've resolved the three separate issues with gimp-help-en today, after which the buildbot is now able to build it on Snow Leopard and Lion, and I can build it on Mountain Lion, so I now have some confidence in it at this point. > Also, what variant do I use to get gimpshop? I'm sorry, I don't know what gimpshop is or how it can be installed using MacPorts. From spooky130u at gmail.com Tue Jul 31 23:25:18 2012 From: spooky130u at gmail.com (Jim Graham) Date: Wed, 1 Aug 2012 01:25:18 -0500 Subject: Processing of port gimp-help-en failed In-Reply-To: References: <20120801051321.GA51706@gmail.com> Message-ID: <20120801062518.GA53906@gmail.com> On Wed, Aug 01, 2012 at 01:10:01AM -0500, Ryan Schmidt wrote: > On Aug 1, 2012, at 00:13, Jim Graham wrote: > > On Wed, Aug 01, 2012 at 06:51:08AM +0200, FritzS - gmx wrote: > >> Am 31.07.2012 um 22:58 schrieb Ryan Schmidt : > >>> On Jul 31, 2012, at 10:44, FritzS - gmx wrote: > > Hmmmm, this looks oddly familiar. In fact, it's EXACTLY what I'm seeing. > > The above doesn't actually say very much. It just says gimp-help-en > failed to build, but it doesn't say why; to learn why, we'd have to > read the main.log. So we don't know, just based on the above, that you > were seeing the same error as FritzS. Where is main.log? I looked in the directory I was in while trying to build gimp, in the ports/graphics directory, and in the gimp directory. No main.log. > > Also, what variant do I use to get gimpshop? > > I'm sorry, I don't know what gimpshop is or how it can be installed > using MacPorts. Seriously? It's a UI/theme/whatever that supposedly makes gimp look and work like Photoshop. I got used to the UI in Photoshop when I worked in Special Ops Intel, and would like to see if gimpshop actually lives up to its name. Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) MiSTie #49997 < Running Mac OS X Lion > spooky130u at gmail.com ICBM/Hurricane: 30.44406N 86.59909W Do not look into waveguide with remaining eye! Android Apps Listing at http://www.jstrack.org/barcodes.html From ryandesign at macports.org Tue Jul 31 23:31:37 2012 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 1 Aug 2012 01:31:37 -0500 Subject: Processing of port gimp-help-en failed In-Reply-To: <20120801062518.GA53906@gmail.com> References: <20120801051321.GA51706@gmail.com> <20120801062518.GA53906@gmail.com> Message-ID: On Aug 1, 2012, at 01:25, Jim Graham wrote: > On Wed, Aug 01, 2012 at 01:10:01AM -0500, Ryan Schmidt wrote: >> On Aug 1, 2012, at 00:13, Jim Graham wrote: >>> On Wed, Aug 01, 2012 at 06:51:08AM +0200, FritzS - gmx wrote: >>>> Am 31.07.2012 um 22:58 schrieb Ryan Schmidt : >>>>> On Jul 31, 2012, at 10:44, FritzS - gmx wrote: > >>> Hmmmm, this looks oddly familiar. In fact, it's EXACTLY what I'm seeing. >> >> The above doesn't actually say very much. It just says gimp-help-en >> failed to build, but it doesn't say why; to learn why, we'd have to >> read the main.log. So we don't know, just based on the above, that you >> were seeing the same error as FritzS. > > Where is main.log? I looked in the directory I was in while trying to > build gimp, in the ports/graphics directory, and in the gimp directory. > No main.log. MacPorts prints its location anytime an error occurs. Quoting from before: >>>>> Please see the log file for port gimp-help-en for details: >>>>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp-help-en/gimp-help-en/main.log That was from FritzS's system; it's possible you've configured your system to have it at a different location, so just use the location MacPorts prints on your system. You can also use the command "port logfile gimp-help-en" to see the location printed again. Note that if a port builds successfully, its log is deleted; if you want to keep logs even for successful builds, set "keeplogs yes" in macports.conf. >>> Also, what variant do I use to get gimpshop? >> >> I'm sorry, I don't know what gimpshop is or how it can be installed >> using MacPorts. > > Seriously? It's a UI/theme/whatever that supposedly makes gimp look and > work like Photoshop. I got used to the UI in Photoshop when I worked in > Special Ops Intel, and would like to see if gimpshop actually lives up to > its name. Yes, sorry, I don't use gimp and am not familiar with it. That sounds nice though and if we don't already have a way to install that in MacPorts then we should certainly get one. From spooky130u at gmail.com Tue Jul 31 23:58:14 2012 From: spooky130u at gmail.com (Jim Graham) Date: Wed, 1 Aug 2012 01:58:14 -0500 Subject: Processing of port gimp-help-en failed In-Reply-To: References: <20120801051321.GA51706@gmail.com> <20120801062518.GA53906@gmail.com> Message-ID: <20120801065814.GA54840@gmail.com> On Wed, Aug 01, 2012 at 01:31:37AM -0500, Ryan Schmidt wrote: > MacPorts prints its location anytime an error occurs. Quoting from before: Ahh, ok, I found it. Here's what it says: --------------------------- CUT HERE --------------------------- :debug:configure configure phase started at Wed Aug 1 01:18:11 CDT 2012 :notice:configure ---> Configuring gimp-help-en :debug:configure Using compiler 'Mac OS X clang' :debug:configure Executing org.macports.configure (gimp-help-en) :debug:configure Environment: CPATH='/opt/local/include' CFLAGS='-pipe -O2' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-pipe -O2' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10.7' CXX='/usr/bin/clang++' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp-help-en/gimp-help-en/work/.CC_PRINT_OPTIONS' F90FLAGS='-pipe -O2' LDFLAGS='-L/opt/local/lib' FCFLAGS='-pipe -O2' OBJC='/usr/bin/clang' INSTALL='/usr/bin/install -c' ALL_LINGUAS='en' OBJCFLAGS='-pipe -O2' FFLAGS='-pipe -O2' CC_PRINT_OPTIONS='YES' CC='/usr/bin/clang' :debug:configure Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp-help-en/gimp-help-en/work/gimp-help-2.8.0" && ./configure --prefix=/opt/local' :debug:configure Executing command line: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp-help-en/gimp-help-en/work/gimp-help-2.8.0" && ./configure --prefix=/opt/local :info:configure checking build system type... x86_64-apple-darwin11.4.0 :info:configure checking for a BSD-compatible install... /usr/bin/install -c :info:configure checking whether build environment is sane... yes :info:configure checking for a thread-safe mkdir -p... /opt/local/bin/gmkdir -p :info:configure checking for gawk... gawk :info:configure checking whether make sets $(MAKE)... yes :info:configure checking whether to enable maintainer-specific portions of Makefiles... no :info:configure checking whether ln -s works... yes :info:configure checking whether make sets $(MAKE)... (cached) yes :info:configure checking for a sed that does not truncate output... /opt/local/bin/gsed :info:configure checking whether make is GNU make... yes :info:configure checking for xsltproc... /opt/local/bin/xsltproc :info:configure checking for xmllint... /opt/local/bin/xmllint :info:configure checking for dblatex... no :info:configure configure: WARNING: cannot find dblatex(1), PDF generation disabled :info:configure checking for docbook2odf... no :info:configure configure: cannot find docbook2odf(1), ODF generation disabled :info:configure checking for msgfmt... /opt/local/bin/msgfmt :info:configure checking for msginit... /opt/local/bin/msginit :info:configure checking for msgmerge... /opt/local/bin/msgmerge :info:configure checking for msguniq... /opt/local/bin/msguniq :info:configure checking for msgcat... /opt/local/bin/msgcat :info:configure checking for dot... /opt/local/bin/dot :info:configure checking for pngnq... no :info:configure configure: WARNING: cannot find pngnq, :info:configure images will not be optimized during distribution creation :info:configure checking for pngcrush... /opt/local/bin/pngcrush :info:configure checking for pkg-config... /opt/local/bin/pkg-config :info:configure checking pkg-config is at least version 0.9.0... yes :info:configure checking for GIMP... no :info:configure configure: error: :info:configure ** Couldn't find a GIMP-2.0 installation. If you want to skip this check and :info:configure ** install the help files to the configured prefix, use the --without-gimp :info:configure ** configure option. Note that GIMP will then only find the help files if it :info:configure ** is installed in the same prefix. See the file 'INSTALL' for more help. :info:configure Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp-help-en/gimp-help-en/work/gimp-help-2.8.0" && ./configure --prefix=/opt/local :info:configure Exit code: 1 :error:configure org.macports.configure for port gimp-help-en returned: configure failure: command execution failed :debug:configure Error code: NONE :debug:configure Backtrace: configure failure: command execution failed while executing "$procedure $targetname" :info:configure Warning: targets not executed for gimp-help-en: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install :error:configure Failed to install gimp-help-en :debug:configure couldn't open "/System/Library/Frameworks/Tcl.framework/Versions/8.5/Resources/tclIndex": no such file or directory while executing "open [file join $dir tclIndex]" :notice:configure Please see the log file for port gimp-help-en for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_gimp-help-en/gimp-help-en/main.log --------------------------- CUT HERE --------------------------- And with that, considering that I normally wake up (whether I want to or not) at about 0400, and it's now just minutes away from 0200, I think it might be time for me to get some sleep. :-) Thanks, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) MiSTie #49997 < Running Mac OS X Lion > spooky130u at gmail.com ICBM/Hurricane: 30.44406N 86.59909W Do not look into waveguide with remaining eye. Android Apps Listing at http://www.jstrack.org/barcodes.html