From tabithamc at gmail.com Tue Jan 1 02:04:51 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 02:03:04 2008 Subject: Ok to switch from Crypt to Shadow Password? Message-ID: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> Hello all -- I am happily running Leopard Server and installing MacPorts 1.6.0. Some of the ports install users in the local directory domain (with Leopard Apple has officially done away with NetInfo by the way). There is an option using Workgroup Manager -- a GUI tool only bundled by Apple with Mac OS X Server, to change the password type of local directory domain users (for example, the user "ldap" installed by MacPorts as part of the openldap port) from crypt to Shadow Password. Has anyone ever tried this and if so are there any reasons not to switch from crypt to Shadow Password? Thank, -T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/f0e7959d/attachment.html From tabithamc at gmail.com Tue Jan 1 05:35:01 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 05:33:20 2008 Subject: Some confusion about XFree86 Message-ID: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> Hello all -- Its been a while since I've made a bunch of MacPorts, but I have an Xserve running Leopard Server 10.5.1 and wanted to give it a try with MacPorts 1.6.0. I had problems building XFree86 (I tried to install with the -d debug option and have saved the output in case it might be useful to submit to the Trac bug reporting system). Before submitting anything, I started poking around a bit, looking at some of the more recent posts about Leopard and XFree86 on the MacPorts mailing list and also noticing that Apple's X11 app is now based on X.org. I noticed that there are also some new (well, new since I last tried MacPorts 1.5.0 on a Tiger Server system in August of 2007), ports that seem to be related to X, such as xorg-util-macros and xorg-xproto (but even these newish ports still depend on XFree86). I'm wondering if anyone can provide a little clearer lay of the land / big picture to help me fill in the missing pieces (with apologies if there is a lot more details interwoven into these mail threads). Are there any recommended paths to take with regard to X11 app or building XFree86 port? Has anyone else had failure building XFree86 on Leopard Server 10.5.1 or Leopard 10.5.1? Thank you for any suggestions. Best regards, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/c435d474/attachment.html From someguyonearth at gmail.com Tue Jan 1 05:40:09 2008 From: someguyonearth at gmail.com (Some Guy) Date: Tue Jan 1 05:38:23 2008 Subject: problem using port to install gnucash on mac 10.5 Message-ID: <9153cb050801010540y6a8f53cdw501b27bcb636174f@mail.gmail.com> could anyone please help, i have been trying to install gnucash on my mac but i get this; "---> Building aqbanking with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_aqbanking/work/aqbanking- 2.3.3" && make all " returned error 2 Command output: make[6]: Nothing to be done for `all'. Making all in dialogs make[6]: Nothing to be done for `all'. Making all in views make[6]: Nothing to be done for `all'. make[6]: Nothing to be done for `all-am'. Making all in qbanking Making all in lib make all-recursive Making all in widgets make all-am make[8]: Nothing to be done for `all-am'. Making all in dialogs make all-am make[8]: Nothing to be done for `all-am'. Making all in views make all-am make[8]: Nothing to be done for `all-am'. /bin/sh ../../../../libtool --tag=CXX --mode=link /usr/bin/g++-4.0 -O2 -g -Wall -L/opt/local/lib -g -o testlib testlib.o libqbanking.la/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_aqbanking/work/aqbanking- 2.3.3/src/libs/aqbanking/libaqbanking.la -lintl /usr/bin/g++-4.0 -O2 -g -Wall -g -o .libs/testlib testlib.o-Wl,-bind_at_load -L/opt/local/lib ./.libs/libqbanking.dylib -L/usr/lib -L/sw/lib -L/opt/local/lib/qt3/lib /opt/local/lib/qt3/lib/libqt- mt.dylib-L/usr/X11R6/lib -lresolv -lz -lGL /usr/X11/lib/libXmu.6.2.0.dylib /opt/local/lib/libXrender.dylib /usr/X11/lib/libXrandr.2.0.0.dylib /usr/X11/lib/libXcursor.1.0.2.dylib /usr/X11/lib/libXinerama.1.0.0.dylib /opt/local/lib/libXft.dylib /opt/local/lib/libfreetype.dylib /opt/local/lib/libfontconfig.dylib /usr/X11/lib/libXext.6.4.0.dylib /usr/X11/lib/libX11.6.2.0.dylib -lm /usr/X11/lib/libSM.6.0.0.dylib /usr/X11/lib/libICE.6.3.0.dylib -ldl /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_aqbanking/work/aqbanking- 2.3.3/src/libs/aqbanking/.libs/libaqbanking.dylib /opt/local/lib/libgwenhywfar.dylib -lssl -lcrypto /opt/local/lib/libintl.dylib /opt/local/lib/libiconv.dylib -lc ld: cycle in dylib re-exports with /usr/X11R6/lib/libGL.dylib collect2: ld returned 1 exit status make[7]: *** [testlib] Error 1 make[6]: *** [all-recursive] Error 1 make[5]: *** [all] Error 2 make[4]: *** [all-recursive] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: The following dependencies failed to build: aqbanking evince avahi esound gconf intltool orbit2 libidl gnome-doc-utils iso-codes py25-hashlib openssl py25-libxml2 gnome-icon-theme icon-naming-utils p5-getopt-long p5-pathtools p5-xml-simple p5-test-simple p5-test-harness p5-xml-namespacesupport p5-xml-sax gnome-keyring libgcrypt libgpg-error gnome-vfs gnome-mime-data howl neon libart_lgpl libgnome libbonobo popt libgnomecanvas gail libgnomeui libbonoboui m4 nautilus eel gnome-desktop fribidi startup-notification gnome-menus libexif librsvg libcroco libgsf shared-mime-info poppler poppler-data gnucash-docs yelp firefox-x11 zip libgtkhtml goffice03 libgnomeprintui libgnomeprint bison libgnomecups pcre guile16 readline ncurses ncursesw gawk libgtkhtml3 p5-finance-quote p5-crypt-ssleay p5-libwww-perl p5-compress-zlib p5-compress-raw-zlib p5-io-compress-base p5-scalar-list-utils p5-io-compress-zlib p5-html-parser p5-html-tagset p5-uri p5-datemanip p5-html-tableextract slib slib-guile16 Error: Status 1 encountered during processing." -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/7fc1336a/attachment-0001.html From james.sumners at gmail.com Tue Jan 1 10:03:48 2008 From: james.sumners at gmail.com (James Sumners) Date: Tue Jan 1 10:01:59 2008 Subject: problem using port to install gnucash on mac 10.5 In-Reply-To: <9153cb050801010540y6a8f53cdw501b27bcb636174f@mail.gmail.com> References: <9153cb050801010540y6a8f53cdw501b27bcb636174f@mail.gmail.com> Message-ID: I have the best luck installing gnucash when enabling the following variants: without_quotes, without_hbci, without_ofx, and without_docs. On Jan 1, 2008 8:40 AM, Some Guy wrote: > could anyone please help, i have been trying to install gnucash on my mac > but i get this; -- James Sumners http://james.roomfullofmirrors.com/ "All governments suffer a recurring problem: Power attracts pathological personalities. It is not that power corrupts but that it is magnetic to the corruptible. Such people have a tendency to become drunk on violence, a condition to which they are quickly addicted." Missionaria Protectiva, Text QIV (decto) CH:D 59 From rsync at reifferscheid.org Tue Jan 1 11:58:01 2008 From: rsync at reifferscheid.org (Thomas Reifferscheid) Date: Tue Jan 1 11:56:13 2008 Subject: Pidgin with OTR? In-Reply-To: <4779E0A3.3090106@gmail.com> References: <4776C0FE.1010604@gmail.com> <4776F44C.8030804@reifferscheid.org> <47779628.3090005@reifferscheid.org> <4779E0A3.3090106@gmail.com> Message-ID: <477A9B49.7070701@reifferscheid.org> pigdin-encryption is http://pidgin-encrypt.sourceforge.net/ it has nothing to do with pidgin-otr. pidgin-otr is not available yet in macports. You find details here: http://trac.macosforge.org/projects/macports/ticket/13759 Kind regards Thomas Matrix Mole wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Thomas Reifferscheid wrote: > >> Success. The new portfile got already posted to the >> macports devel mailinglist, so it should be available shortly. >> >> The port is called pidgin-otr. >> > > I've re-sync'd my ports tree and I saw a port called pidgin-encryption > but not one labeled pidgin-otr. I'm guessing that the pidgin-encryption > is the correct port. Otherwise it might be that it hasn't been put into > the port tree for non-devel users yet. I do notice that > pidgin-encryption does not have libotr port as a dependent. I haven't > had a chance to test out the encryption with the encrypted pidgin as of > yet to confirm that it works in concert with the OTR encryption. > > Matrix Mole > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHeeCjNtosHRPp48MRAmQkAKCiPNXuo7MHon2DmDdsZrp6IKIBdwCgjykM > YkDPdhafKV7YvX2iE05rgXk= > =eQkw > -----END PGP SIGNATURE----- > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > From jkh at apple.com Tue Jan 1 12:16:34 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Tue Jan 1 12:16:15 2008 Subject: Emacs and Leopard problems continue In-Reply-To: <887865AB-59C2-436B-99CC-15C7CCE06CF4@cvrti.utah.edu> References: <887865AB-59C2-436B-99CC-15C7CCE06CF4@cvrti.utah.edu> Message-ID: <88E9028D-D470-43E5-BD51-0EE50D328E3F@apple.com> OK, I'll bite. What specifically is wrong with the system emacs that requires folks to struggle so hard to build another copy? It even supports carbon if you add an app wrapper (like the one I just attached - a mere 55k, and most of that is the icon), so I'm not sure what would lead one to struggle so hard to build emacs again. Yes, the macports version should certainly work just on general principle, but that's not the question I'm asking. - Jordan -------------- next part -------------- A non-text attachment was scrubbed... Name: Emacs.app.zip Type: application/zip Size: 24960 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/4f32ccb6/Emacs.app-0001.zip -------------- next part -------------- p On Dec 31, 2007, at 2:58 PM, Rob MacLeod wrote: > Hi folks, > > I am still struggling with Leopard woes with emacs. > > I was able to get emacs, emacs-devel, and emacs-app all made by > manually applying the patch provided in ticket #13294. emacs made > in the wrong directory while emacs-devel did better and ended up > properly placed. > > However, neither emacs nor emacs-devel launch a new X window when I > start them. I vaguely recall that this was a problem in the past > but I was able with Tiger to get at least one of them (no longer > sure which) to work in the proper X window mode. > > Does anyone know if there are some other settings I need to get a > full functioning X11 based emacs to work? > > In the meantime, I will experiment with emacs-app to see if I can > get it to work the way I am used to... > > Good thing this is the break and I have time to deal with all the > frustrations of Leopard.... > > Happy New Year, > > Rob > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users From jkh at apple.com Tue Jan 1 12:18:27 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Tue Jan 1 12:18:06 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> Message-ID: <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> Let's ask a different question: What are you trying to achieve? - Jordan On Jan 1, 2008, at 2:04 AM, Tabitha McNerney wrote: > Hello all -- > > I am happily running Leopard Server and installing MacPorts 1.6.0. > Some of the ports install users in the local directory domain (with > Leopard Apple has officially done away with NetInfo by the way). > There is an option using Workgroup Manager -- a GUI tool only > bundled by Apple with Mac OS X Server, to change the password type > of local directory domain users (for example, the user "ldap" > installed by MacPorts as part of the openldap port) from crypt to > Shadow Password. Has anyone ever tried this and if so are there any > reasons not to switch from crypt to Shadow Password? > > Thank, > > -T.M. > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users From ryandesign at macports.org Tue Jan 1 13:16:11 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 13:14:47 2008 Subject: Some confusion about XFree86 In-Reply-To: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> References: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> Message-ID: On Jan 1, 2008, at 07:35, Tabitha McNerney wrote: > Its been a while since I've made a bunch of MacPorts, but I have an > Xserve running Leopard Server 10.5.1 and wanted to give it a try > with MacPorts 1.6.0. > > I had problems building XFree86 (I tried to install with the -d > debug option and have saved the output in case it might be useful > to submit to the Trac bug reporting system). Before submitting > anything, I started poking around a bit, looking at some of the > more recent posts about Leopard and XFree86 on the MacPorts mailing > list and also noticing that Apple's X11 app is now based on X.org. > > I noticed that there are also some new (well, new since I last > tried MacPorts 1.5.0 on a Tiger Server system in August of 2007), > ports that seem to be related to X, such as xorg-util-macros and > xorg-xproto (but even these newish ports still depend on XFree86). > > I'm wondering if anyone can provide a little clearer lay of the > land / big picture to help me fill in the missing pieces (with > apologies if there is a lot more details interwoven into these mail > threads). Are there any recommended paths to take with regard to > X11 app or building XFree86 port? Has anyone else had failure > building XFree86 on Leopard Server 10.5.1 or Leopard 10.5.1? I guess the first question is: why do you want to build XFree86? Ports that depend on XFree86 only do so in the event that you have not installed Apple X11. MacPorts installation documents state that you must install Apple X11. Therefore, nobody should need to install the XFree86 port, and in fact, you cannot do so if Apple X11 is already installed, which it is now by default on Leopard. From ryandesign at macports.org Tue Jan 1 13:17:28 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 13:16:03 2008 Subject: problem using port to install gnucash on mac 10.5 In-Reply-To: <9153cb050801010540y6a8f53cdw501b27bcb636174f@mail.gmail.com> References: <9153cb050801010540y6a8f53cdw501b27bcb636174f@mail.gmail.com> Message-ID: <38E322B1-12C0-4F25-B921-6010027D3CCE@macports.org> On Jan 1, 2008, at 07:40, Some Guy wrote: > could anyone please help, i have been trying to install gnucash on > my mac but i get this; > > > "---> Building aqbanking with target all [snip] > ld: cycle in dylib re-exports with /usr/X11R6/lib/libGL.dylib You are experiencing this bug: http://trac.macosforge.org/projects/macports/ticket/13173 From ryandesign at macports.org Tue Jan 1 13:18:28 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 13:17:00 2008 Subject: Rebuild after Xcode update? In-Reply-To: References: Message-ID: <6D1FBB42-3EBB-4152-BE2B-1635B5686522@macports.org> On Dec 31, 2007, at 23:19, Skip Montanaro wrote: > I'm currently using Xcode 2.2.1 and am having trouble building the > Python > 2.5 port. A little searching suggested I should update my Xcode, > so I'm > downloading the Xcode 2.5 image as I write this. > > Once I've updated my Xcode installation, what should I do on the > MacPorts > side of things? Is there some way to say "rebuild all" or do I > just plow > ahead with the Python 2.5 install and ignore the fact that > everything else > was built up to that point with Xcode 2.2.1? There isn't a way to say "rebuild all" that I know of. I'm not sure if it's necessary. I would begin with the assumption that it is not necessary. Just upgrade to Xcode 2.5 and then install whatever ports you wanted to install. From harrylparker at gmail.com Tue Jan 1 13:49:57 2008 From: harrylparker at gmail.com (Harry Parker) Date: Tue Jan 1 13:48:07 2008 Subject: unable to upgrade port py25-scipy Message-ID: <2a77b9140801011349tf3fe815ne7899ce218c12748@mail.gmail.com> I have been having trouble for several weeks upgrading port py25-scipy. Today I did a port selfupdate and successfully upgraded g95 and tried to upgrade py25-scipy from from version 0.6.0_0. The attempted upgrade ends with: ------- building 'scipy.interpolate.dfitpack' extension error: extension 'scipy.interpolate.dfitpack' has Fortran sources but no Fortran compiler found Warning: the following items did not execute (for py25-scipy): org.macports.destroot org.macports.build Error: Unable to upgrade port: 1 ------- I tried this with the default variant and with the +g95 variant set explicitly. This is on a PowerPC G4 recently upgraded to Mac OS X 10.4.11. Any ideas? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/dfbed239/attachment.html From tabithamc at gmail.com Tue Jan 1 15:09:10 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 15:07:21 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> Message-ID: <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> On 1/1/08, Jordan K. Hubbard wrote: > > Let's ask a different question: What are you trying to achieve? > > - Jordan Hi Jordan, You raise a good question, about what I am trying to achieve. My concern is that, after reading Apple's Mac OS X Server Leopard documentation, it strikes me that crypt passwords are less secure compared to other options such as Shadow Passwords, as I quote the Leopard Server OpenDirectory documentation (PDF): User accounts not used on computers that require a crypt password should > have an > Open Directory password or a shadow password. A crypt password is required > only for > logging in to a computer with Mac OS X v10.1 or earlier and on computers > with some > types of UNIX. > > A crypt password is stored as an encrypted value, or hash, in the user > account record in > the directory domain. Because the crypt password can be recovered from the > directory > domain, it is subject to offline attack and is less secure than other > password types. > Maybe I am misinterpreting, but it strikes me that Apple is recommending that, if possible, a crypt password should be last on the list of password type choices. Thanks, T.M. On Jan 1, 2008, at 2:04 AM, Tabitha McNerney wrote: > > > Hello all -- > > > > I am happily running Leopard Server and installing MacPorts 1.6.0. > > Some of the ports install users in the local directory domain (with > > Leopard Apple has officially done away with NetInfo by the way). > > There is an option using Workgroup Manager -- a GUI tool only > > bundled by Apple with Mac OS X Server, to change the password type > > of local directory domain users (for example, the user "ldap" > > installed by MacPorts as part of the openldap port) from crypt to > > Shadow Password. Has anyone ever tried this and if so are there any > > reasons not to switch from crypt to Shadow Password? > > > > Thank, > > > > -T.M. > > _______________________________________________ > > macports-users mailing list > > macports-users@lists.macosforge.org > > http://lists.macosforge.org/mailman/listinfo/macports-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/6c286d27/attachment.html From skip at pobox.com Tue Jan 1 15:11:35 2008 From: skip at pobox.com (skip@pobox.com) Date: Tue Jan 1 15:09:53 2008 Subject: gcc42 target bootstrap runs forever? Message-ID: <18298.51367.714305.630046@montanaro.dyndns.org> I executed sudo port upgrade active this morning. It made it through several different port upgrades, but when it got to gcc42 it just seemed to run forever. I don't know how long I let it run before killing it, but it had to be at least two-three hours. I'm going to try installing gcc43 instead. Should the gcc42 upgrade have worked? I've got MacPorts 1.6.0 and Xcode 2.5 installed on a Powerbook G4 running OSX 10.4.11. Thx, -- Skip Montanaro - skip@pobox.com - http://www.webfast.com/~skip/ From ryandesign at macports.org Tue Jan 1 15:36:19 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 15:34:53 2008 Subject: gcc42 target bootstrap runs forever? In-Reply-To: <18298.51367.714305.630046@montanaro.dyndns.org> References: <18298.51367.714305.630046@montanaro.dyndns.org> Message-ID: <6977BAF9-F1F3-4AA4-99EC-718276B521DF@macports.org> On Jan 1, 2008, at 17:11, skip@pobox.com wrote: > I executed sudo port upgrade active this morning. It made it through > several different port upgrades, but when it got to gcc42 it just > seemed to > run forever. I don't know how long I let it run before killing it, > but it > had to be at least two-three hours. > > I'm going to try installing gcc43 instead. Should the gcc42 > upgrade have > worked? I've got MacPorts 1.6.0 and Xcode 2.5 installed on a > Powerbook G4 > running OSX 10.4.11. gcc42 took about 6 hours to build and install on my 1.5-GHz PowerBook G4 back when I had it. If your PowerBook is slower, it'll take even longer. You can install with the -v flag to see what's going on, to show that it's still working, and not frozen. sudo port -v upgrade gcc42 From ryandesign at macports.org Tue Jan 1 15:39:11 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 15:37:44 2008 Subject: gcc42 target bootstrap runs forever? In-Reply-To: <6977BAF9-F1F3-4AA4-99EC-718276B521DF@macports.org> References: <18298.51367.714305.630046@montanaro.dyndns.org> <6977BAF9-F1F3-4AA4-99EC-718276B521DF@macports.org> Message-ID: On Jan 1, 2008, at 17:11, skip@pobox.com wrote: > I executed sudo port upgrade active this morning. [snip] FYI: "sudo port upgrade active" probably isn't best. You probably want "sudo port upgrade outdated" From skip at pobox.com Tue Jan 1 16:00:26 2008 From: skip at pobox.com (skip@pobox.com) Date: Tue Jan 1 15:58:44 2008 Subject: gcc42 target bootstrap runs forever? In-Reply-To: <6977BAF9-F1F3-4AA4-99EC-718276B521DF@macports.org> References: <18298.51367.714305.630046@montanaro.dyndns.org> <6977BAF9-F1F3-4AA4-99EC-718276B521DF@macports.org> Message-ID: <18298.54298.79567.420660@montanaro.dyndns.org> Ryan> gcc42 took about 6 hours to build and install on my 1.5-GHz Ryan> PowerBook G4 back when I had it. If your PowerBook is slower, Ryan> it'll take even longer. Ah, okay. That's good to know. Yes, my PB is only 800MHz. I'll give it a try with -v so I can see what's happening. Skip From skip at pobox.com Tue Jan 1 16:01:34 2008 From: skip at pobox.com (skip@pobox.com) Date: Tue Jan 1 15:59:47 2008 Subject: gcc42 target bootstrap runs forever? In-Reply-To: References: <18298.51367.714305.630046@montanaro.dyndns.org> <6977BAF9-F1F3-4AA4-99EC-718276B521DF@macports.org> Message-ID: <18298.54366.729333.297004@montanaro.dyndns.org> Ryan> FYI: "sudo port upgrade active" probably isn't best. You probably Ryan> want "sudo port upgrade outdated" I trust that upgrade active will only update those activated items which are out-of-date, yes? Skip From tabithamc at gmail.com Tue Jan 1 16:03:11 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 16:01:21 2008 Subject: Some confusion about XFree86 In-Reply-To: References: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> Message-ID: <7fccb3000801011603y2e0a64a0g66a283356a5637ad@mail.gmail.com> On 1/1/08, Ryan Schmidt wrote: > > On Jan 1, 2008, at 07:35, Tabitha McNerney wrote: > > > Its been a while since I've made a bunch of MacPorts, but I have an > > Xserve running Leopard Server 10.5.1 and wanted to give it a try > > with MacPorts 1.6.0. > > > > I had problems building XFree86 (I tried to install with the -d > > debug option and have saved the output in case it might be useful > > to submit to the Trac bug reporting system). Before submitting > > anything, I started poking around a bit, looking at some of the > > more recent posts about Leopard and XFree86 on the MacPorts mailing > > list and also noticing that Apple's X11 app is now based on X.org. > > > > I noticed that there are also some new (well, new since I last > > tried MacPorts 1.5.0 on a Tiger Server system in August of 2007), > > ports that seem to be related to X, such as xorg-util-macros and > > xorg-xproto (but even these newish ports still depend on XFree86). > > > > I'm wondering if anyone can provide a little clearer lay of the > > land / big picture to help me fill in the missing pieces (with > > apologies if there is a lot more details interwoven into these mail > > threads). Are there any recommended paths to take with regard to > > X11 app or building XFree86 port? Has anyone else had failure > > building XFree86 on Leopard Server 10.5.1 or Leopard 10.5.1? > > I guess the first question is: why do you want to build XFree86? > Ports that depend on XFree86 only do so in the event that you have > not installed Apple X11. MacPorts installation documents state that > you must install Apple X11. Therefore, nobody should need to install > the XFree86 port, and in fact, you cannot do so if Apple X11 is > already installed, which it is now by default on Leopard. Ryan, this is, in hindsight, a good question. I had, by habit in the past, been building the Mac(Darwin) Port, XFree86, mostly because IIRC the Apple X11 app was historically not open source totally and I was concerned about moving to a possible proprietary application. But, based on what I've read yesterday, I guess X11 from Apple has been re-based on X.org now so I can see how that would, in essence, deprecate the need to build XFree86. With that being said, so if XFree86 is pretty much no longer needed in lieu of the changes to Apple's X11 app on Leopard, then what about some of the X Windows ports such as wireshark? Checking out the dependencies for wireshark, I can trace its dependencies to the XFree86 port: $ ports deps wireshark > wireshark has library dependencies on: > glib2 > gtk2 > openssl > libpcap > zlib > ... $ port deps gtk2 > gtk2 has library dependencies on: > cairo > fontconfig > freetype > glib2 > jpeg > tiff > libiconv > libpng > atk > pango > gettext > render > zlib > xrender > xorg > ... $ port deps pango > glib2 > XFree86 > Xft2 > cairo > fontconfig > Thanks for the clearing some of my confusion. Best regards, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/06058e15/attachment.html From ryandesign at macports.org Tue Jan 1 16:14:27 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 16:13:00 2008 Subject: Some confusion about XFree86 In-Reply-To: <7fccb3000801011603y2e0a64a0g66a283356a5637ad@mail.gmail.com> References: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> <7fccb3000801011603y2e0a64a0g66a283356a5637ad@mail.gmail.com> Message-ID: <10E62387-1073-44E8-A181-2C3BDB0024B6@macports.org> On Jan 1, 2008, at 18:03, Tabitha McNerney wrote: > On 1/1/08, Ryan Schmidt wrote: > >> On Jan 1, 2008, at 07:35, Tabitha McNerney wrote: >> >> > Its been a while since I've made a bunch of MacPorts, but I have an >> > Xserve running Leopard Server 10.5.1 and wanted to give it a try >> > with MacPorts 1.6.0. >> > >> > I had problems building XFree86 (I tried to install with the -d >> > debug option and have saved the output in case it might be useful >> > to submit to the Trac bug reporting system). Before submitting >> > anything, I started poking around a bit, looking at some of the >> > more recent posts about Leopard and XFree86 on the MacPorts mailing >> > list and also noticing that Apple's X11 app is now based on X.org. >> > >> > I noticed that there are also some new (well, new since I last >> > tried MacPorts 1.5.0 on a Tiger Server system in August of 2007), >> > ports that seem to be related to X, such as xorg-util-macros and >> > xorg-xproto (but even these newish ports still depend on XFree86). >> > >> > I'm wondering if anyone can provide a little clearer lay of the >> > land / big picture to help me fill in the missing pieces (with >> > apologies if there is a lot more details interwoven into these mail >> > threads). Are there any recommended paths to take with regard to >> > X11 app or building XFree86 port? Has anyone else had failure >> > building XFree86 on Leopard Server 10.5.1 or Leopard 10.5.1? >> >> I guess the first question is: why do you want to build XFree86? >> Ports that depend on XFree86 only do so in the event that you have >> not installed Apple X11. MacPorts installation documents state that >> you must install Apple X11. Therefore, nobody should need to install >> the XFree86 port, and in fact, you cannot do so if Apple X11 is >> already installed, which it is now by default on Leopard. > > Ryan, this is, in hindsight, a good question. I had, by habit in > the past, been building the Mac(Darwin) Port, XFree86, mostly > because IIRC the Apple X11 app was historically not open source > totally and I was concerned about moving to a possible proprietary > application. But, based on what I've read yesterday, I guess X11 > from Apple has been re-based on X.org now so I can see how that > would, in essence, deprecate the need to build XFree86. > > With that being said, so if XFree86 is pretty much no longer needed > in lieu of the changes to Apple's X11 app on Leopard, then what > about some of the X Windows ports such as wireshark? Checking out > the dependencies for wireshark, I can trace its dependencies to the > XFree86 port: > > $ ports deps wireshark > wireshark has library dependencies on: > glib2 > gtk2 > openssl > libpcap > zlib > > ... > > $ port deps gtk2 > gtk2 has library dependencies on: > cairo > fontconfig > freetype > glib2 > jpeg > tiff > libiconv > libpng > atk > pango > gettext > render > zlib > xrender > xorg > > ... > > $ port deps pango > glib2 > XFree86 > Xft2 > cairo > fontconfig > > > Thanks for the clearing some of my confusion. As I explained, "Ports that depend on XFree86 only do so in the event that you have not installed Apple X11." To take your example of pango, look at how the dependency is defined in the pango portfile: depends_lib \ ... lib:libX11.6:XFree86 \ That means: it depends on the library libX11.6, and if that library does not exist, then install it via the XFree86 port. libX11.6 will already exist on your system if Apple X11 is installed, therefore the XFree86 port will not be installed. From tabithamc at gmail.com Tue Jan 1 16:23:14 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 16:21:24 2008 Subject: Some confusion about XFree86 In-Reply-To: <10E62387-1073-44E8-A181-2C3BDB0024B6@macports.org> References: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> <7fccb3000801011603y2e0a64a0g66a283356a5637ad@mail.gmail.com> <10E62387-1073-44E8-A181-2C3BDB0024B6@macports.org> Message-ID: <7fccb3000801011623q3b8c714cmb7235043a7121c91@mail.gmail.com> On 1/1/08, Ryan Schmidt wrote: > > On Jan 1, 2008, at 18:03, Tabitha McNerney wrote: [SNIP] As I explained, "Ports that depend on XFree86 only do so in the event > that you have not installed Apple X11." To take your example of > pango, look at how the dependency is defined in the pango portfile: > > depends_lib \ > ... > lib:libX11.6:XFree86 \ > > That means: it depends on the library libX11.6, and if that library > does not exist, then install it via the XFree86 port. libX11.6 will > already exist on your system if Apple X11 is installed, therefore the > XFree86 port will not be installed. > Hmm ... ok, I must have done something without realizing it or basing off of my Tiger documentation because I have the X11 app and I could swear that I installed the X11 headers from the Leopard Server DVD. Thanks again for reinforcing this. -T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/721b05ac/attachment-0001.html From jkh at apple.com Tue Jan 1 17:39:02 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Tue Jan 1 17:38:41 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> Message-ID: <15FA2886-6246-4108-A45D-C2D552AC287B@apple.com> I see your confusion. The documentation only mentions Crypt passwords as and old-style way of leaving passwords around if you need interoperability with 10.0 or 10.1 machines. By default, you're already using a shadow password and have been for quite a few releases now. - Jordan On Jan 1, 2008, at 3:09 PM, Tabitha McNerney wrote: > > On 1/1/08, Jordan K. Hubbard wrote: > Let's ask a different question: What are you trying to achieve? > > - Jordan > > Hi Jordan, > > You raise a good question, about what I am trying to achieve. My > concern is that, after reading Apple's Mac OS X Server Leopard > documentation, it strikes me that crypt passwords are less secure > compared to other options such as Shadow Passwords, as I quote the > Leopard Server OpenDirectory documentation (PDF): > > User accounts not used on computers that require a crypt password > should have an > Open Directory password or a shadow password. A crypt password is > required only for > logging in to a computer with Mac OS X v10.1 or earlier and on > computers with some > types of UNIX. > > A crypt password is stored as an encrypted value, or hash, in the > user account record in > the directory domain. Because the crypt password can be recovered > from the directory > domain, it is subject to offline attack and is less secure than > other password types. > > Maybe I am misinterpreting, but it strikes me that Apple is > recommending that, if possible, a crypt password should be last on > the list of password type choices. > > Thanks, > > T.M. > > On Jan 1, 2008, at 2:04 AM, Tabitha McNerney wrote: > > > Hello all -- > > > > I am happily running Leopard Server and installing MacPorts 1.6.0. > > Some of the ports install users in the local directory domain (with > > Leopard Apple has officially done away with NetInfo by the way). > > There is an option using Workgroup Manager -- a GUI tool only > > bundled by Apple with Mac OS X Server, to change the password type > > of local directory domain users (for example, the user "ldap" > > installed by MacPorts as part of the openldap port) from crypt to > > Shadow Password. Has anyone ever tried this and if so are there any > > reasons not to switch from crypt to Shadow Password? > > > > Thank, > > > > -T.M. > > _______________________________________________ > > macports-users mailing list > > macports-users@lists.macosforge.org > > http://lists.macosforge.org/mailman/listinfo/macports-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/24e9fa48/attachment.html From harrylparker at gmail.com Tue Jan 1 19:02:50 2008 From: harrylparker at gmail.com (Harry Parker) Date: Tue Jan 1 19:01:01 2008 Subject: unable to upgrade port py25-scipy In-Reply-To: <2a77b9140801011349tf3fe815ne7899ce218c12748@mail.gmail.com> References: <2a77b9140801011349tf3fe815ne7899ce218c12748@mail.gmail.com> Message-ID: <2a77b9140801011902r3e72f5canc5def3df77dc7cb4@mail.gmail.com> I submitted this to TRAC as ticket # 13776. -- Harry On Jan 1, 2008 4:49 PM, Harry Parker wrote: > I have been having trouble for several weeks upgrading port py25-scipy. > > Today I did a port selfupdate and successfully upgraded g95 and tried to > upgrade py25-scipy from from version 0.6.0_0. > The attempted upgrade ends with: > > ------- > building 'scipy.interpolate.dfitpack' extension > error: extension 'scipy.interpolate.dfitpack' has Fortran sources but no > Fortran compiler found > > Warning: the following items did not execute (for py25-scipy): > org.macports.destroot org.macports.build > Error: Unable to upgrade port: 1 > ------- > > I tried this with the default variant and with the +g95 variant set > explicitly. > This is on a PowerPC G4 recently upgraded to Mac OS X 10.4.11. > > Any ideas? > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/3c0b27a8/attachment.html From boeyms at macports.org Tue Jan 1 19:36:13 2008 From: boeyms at macports.org (Boey Maun Suang) Date: Tue Jan 1 19:34:21 2008 Subject: Rebuild after Xcode update? In-Reply-To: <6D1FBB42-3EBB-4152-BE2B-1635B5686522@macports.org> References: <6D1FBB42-3EBB-4152-BE2B-1635B5686522@macports.org> Message-ID: <21757.203.20.35.28.1199244973.squirrel@webmail.tuffmail.net> On Wed, January 2, 2008 8:18 am, Ryan Schmidt wrote: > > On Dec 31, 2007, at 23:19, Skip Montanaro wrote: > >> I'm currently using Xcode 2.2.1 and am having trouble building the >> Python >> 2.5 port. A little searching suggested I should update my Xcode, >> so I'm >> downloading the Xcode 2.5 image as I write this. >> >> Once I've updated my Xcode installation, what should I do on the >> MacPorts >> side of things? Is there some way to say "rebuild all" or do I >> just plow >> ahead with the Python 2.5 install and ignore the fact that >> everything else >> was built up to that point with Xcode 2.2.1? > > There isn't a way to say "rebuild all" that I know of. I'm not sure > if it's necessary. I would begin with the assumption that it is not > necessary. Just upgrade to Xcode 2.5 and then install whatever ports > you wanted to install. I think that, should you find it necessary, a forced upgrade of all your installed ports (sudo port -ufn upgrade installed) has the effect of rebuilding everything that you have installed. (The -n is needed to avoid unnecessary multiple rebuilds of ports that are dependencies of others -- this is a bug in MacPorts; -u is needed to uninstall the installed ports so that the the automatic reinstallation works properly). As for the compatibility of code built with Xcode 2.5 with that built with Xcode 2.2.1, I think that they should be largely compatible, as my reading of the release notes from 2.2.1 to 2.5 is that there have only been bugfixes and feature enhancements to Xcode's GCC in that time, rather than any deliberate compatibility-breaking changes. If that's the case, any incompatibilities ought to be due to incorrect code produced by Xcode. Kind regards, Maun Suang -- Boey Maun Suang Email: boeyms@macports.org From jkh at apple.com Tue Jan 1 19:38:45 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Tue Jan 1 19:36:53 2008 Subject: Some confusion about XFree86 In-Reply-To: <10E62387-1073-44E8-A181-2C3BDB0024B6@macports.org> References: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> <7fccb3000801011603y2e0a64a0g66a283356a5637ad@mail.gmail.com> <10E62387-1073-44E8-A181-2C3BDB0024B6@macports.org> Message-ID: <9AE497DC-41B5-495F-99C1-A86B11E9170F@apple.com> On Jan 1, 2008, at 4:14 PM, Ryan Schmidt wrote: > As I explained, "Ports that depend on XFree86 only do so in the > event that you have not installed Apple X11." To take your example > of pango, look at how the dependency is defined in the pango portfile: I think Tabitha's question suggests another, however. Given that the center of gravity has clearly shifted over to X.org (and the fact that Jeremy Huddleston and Ben Byer have substantially evolved that code base over what shipped in Leopard, said collection of packages / git branch checkouts needing a bit of manual labor to currently install), why is XFree86 the fall back at all? Even if the intention is not to install it, it seems like there should still be a more sensible default now. - Jordan From matrixm at gmail.com Tue Jan 1 19:40:10 2008 From: matrixm at gmail.com (Matrix Mole) Date: Tue Jan 1 19:38:23 2008 Subject: Pidgin with OTR? In-Reply-To: <477A9B49.7070701@reifferscheid.org> References: <4776C0FE.1010604@gmail.com> <4776F44C.8030804@reifferscheid.org> <47779628.3090005@reifferscheid.org> <4779E0A3.3090106@gmail.com> <477A9B49.7070701@reifferscheid.org> Message-ID: <477B079A.40001@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thomas Reifferscheid wrote: > pigdin-encryption is http://pidgin-encrypt.sourceforge.net/ it has nothing > to do with pidgin-otr. Thank you for pointing that out, I didn't realize that they were two distinct different encryption builds. > pidgin-otr is not available yet in macports. You find details here: > http://trac.macosforge.org/projects/macports/ticket/13759 Using the tarball file from that site, where would I place it so that I could then install it into my port tree? I'd be more than willing to install the build and report back any bugs I run across while using it. Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHeweaNtosHRPp48MRAigAAJ9uXSSqMZ4NI43RbNupG2/pLZ4IKQCeIt/H REecfnukwpcX0o5nNapwC8Q= =wdqE -----END PGP SIGNATURE----- From tabithamc at gmail.com Tue Jan 1 20:01:26 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 19:59:37 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: <15FA2886-6246-4108-A45D-C2D552AC287B@apple.com> References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> <15FA2886-6246-4108-A45D-C2D552AC287B@apple.com> Message-ID: <7fccb3000801012001r2baa29a9g547dd19e3052ee69@mail.gmail.com> On 1/1/08, Jordan K. Hubbard wrote: > > I see your confusion. The documentation only mentions Crypt passwords as > and old-style way of leaving passwords around if you need interoperability > with 10.0 or 10.1 machines. By default, you're already using a shadow > password and have been for quite a few releases now. > Jordan, appreciate the further clarity. Quick question then (just to make sure I'm ultra clear) -- even if a MacPort installs a new entry in the local directory domain with a "Crypt Password" type, what you're saying is that in reality, under Leopard Server (and the past few versions of Mac OS X Server) this password is a Shadow Password disguised to the system as a Crypt Password? I ask because using Workgroup Manager on Leopard Server, I can select the user that was installed by the MacPort (for example, take the openldap MacPort which installs a local directory domain entry with the username "ldap", UID "500" and a User Password Type of "Crypt Password" and I can select the pop-up menu with the "Crypt Password" selection and change the type to either "Shadow Password" or "OpenDirectory" because I am also running an OpenDirectory Master on the same machine). I appreciate the insight as this is actually quite interesting! Thanks, T.M. - Jordan > > On Jan 1, 2008, at 3:09 PM, Tabitha McNerney wrote: > > > On 1/1/08, Jordan K. Hubbard wrote: > > > > Let's ask a different question: What are you trying to achieve? > > > > - Jordan > > > Hi Jordan, > > You raise a good question, about what I am trying to achieve. My concern > is that, after reading Apple's Mac OS X Server Leopard documentation, it > strikes me that crypt passwords are less secure compared to other options > such as Shadow Passwords, as I quote the Leopard Server OpenDirectory > documentation (PDF): > > User accounts not used on computers that require a crypt password should > > have an > > Open Directory password or a shadow password. A crypt password is > > required only for > > logging in to a computer with Mac OS X v10.1 or earlier and on computers > > with some > > types of UNIX. > > > > A crypt password is stored as an encrypted value, or hash, in the user > > account record in > > the directory domain. Because the crypt password can be recovered from > > the directory > > domain, it is subject to offline attack and is less secure than other > > password types. > > > > Maybe I am misinterpreting, but it strikes me that Apple is recommending > that, if possible, a crypt password should be last on the list of password > type choices. > > Thanks, > > T.M. > > On Jan 1, 2008, at 2:04 AM, Tabitha McNerney wrote: > > > > > Hello all -- > > > > > > I am happily running Leopard Server and installing MacPorts 1.6.0. > > > Some of the ports install users in the local directory domain (with > > > Leopard Apple has officially done away with NetInfo by the way). > > > There is an option using Workgroup Manager -- a GUI tool only > > > bundled by Apple with Mac OS X Server, to change the password type > > > of local directory domain users (for example, the user "ldap" > > > installed by MacPorts as part of the openldap port) from crypt to > > > Shadow Password. Has anyone ever tried this and if so are there any > > > reasons not to switch from crypt to Shadow Password? > > > > > > Thank, > > > > > > -T.M. > > > _______________________________________________ > > > macports-users mailing list > > > macports-users@lists.macosforge.org > > > http://lists.macosforge.org/mailman/listinfo/macports-users > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/92df5cd4/attachment-0001.html From jkh at apple.com Tue Jan 1 20:32:31 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Tue Jan 1 20:32:09 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: <7fccb3000801012001r2baa29a9g547dd19e3052ee69@mail.gmail.com> References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> <15FA2886-6246-4108-A45D-C2D552AC287B@apple.com> <7fccb3000801012001r2baa29a9g547dd19e3052ee69@mail.gmail.com> Message-ID: On Jan 1, 2008, at 8:01 PM, Tabitha McNerney wrote: > Jordan, appreciate the further clarity. Quick question then (just to > make sure I'm ultra clear) -- even if a MacPort installs a new entry > in the local directory domain with a "Crypt Password" type, what > you're saying is that in reality, under Leopard Server (and the past > few versions of Mac OS X Server) this password is a Shadow Password > disguised to the system as a Crypt Password? I ask because using > Workgroup Manager on Leopard Server, I can select the user that was > installed by the MacPort (for example, take the openldap MacPort > which installs a local directory domain entry with the username > "ldap", UID "500" and a User Password Type of "Crypt Password" and I > can select the pop-up menu with the "Crypt Password" selection and > change the type to either "Shadow Password" or "OpenDirectory" > because I am also running an OpenDirectory Master on the same > machine). I'm not sure how MacPorts installs user records on Leopard (I've never looked). Presumably, it just drops a plist file into /var/db/dslocal/ nodes/Default/users since that's all you need to do in Leopard. The contents of that plist file, however, can specify a number of different password types - "it all depends" is about the best answer I can give you there. You should look at the authentication_authority array in the user plists you're wondering about and verify that they're doing whatever it is you want them to do (this is an array value, so there are multiple options here). I'd be surprised if MacPorts was using some obsolete password types, but you never know I guess. - Jordan From ryandesign at macports.org Tue Jan 1 20:39:54 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 20:45:08 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> <15FA2886-6246-4108-A45D-C2D552AC287B@apple.com> <7fccb3000801012001r2baa29a9g547dd19e3052ee69@mail.gmail.com> Message-ID: <14A27BBE-CB12-403B-9878-D01AA8FFA227@macports.org> On Jan 1, 2008, at 22:32, Jordan K. Hubbard wrote: > On Jan 1, 2008, at 8:01 PM, Tabitha McNerney wrote: > >> Jordan, appreciate the further clarity. Quick question then (just >> to make sure I'm ultra clear) -- even if a MacPort installs a new >> entry in the local directory domain with a "Crypt Password" type, >> what you're saying is that in reality, under Leopard Server (and >> the past few versions of Mac OS X Server) this password is a >> Shadow Password disguised to the system as a Crypt Password? I ask >> because using Workgroup Manager on Leopard Server, I can select >> the user that was installed by the MacPort (for example, take the >> openldap MacPort which installs a local directory domain entry >> with the username "ldap", UID "500" and a User Password Type of >> "Crypt Password" and I can select the pop-up menu with the "Crypt >> Password" selection and change the type to either "Shadow >> Password" or "OpenDirectory" because I am also running an >> OpenDirectory Master on the same machine). > > I'm not sure how MacPorts installs user records on Leopard (I've > never looked). Presumably, it just drops a plist file into /var/db/ > dslocal/nodes/Default/users since that's all you need to do in > Leopard. The contents of that plist file, however, can specify a > number of different password types - "it all depends" is about the > best answer I can give you there. You should look at the > authentication_authority array in the user plists you're wondering > about and verify that they're doing whatever it is you want them to > do (this is an array value, so there are multiple options here). > I'd be surprised if MacPorts was using some obsolete password > types, but you never know I guess. It looks like MacPorts uses dscl to create users and groups, on all versions of Mac OS X. See src/port1.0/portutil.tcl. proc adduser {name args} { global os.platform set passwd {*} set uid [nextuid] set gid [existsgroup nogroup] set realname ${name} set home /dev/null set shell /dev/null foreach arg $args { if {[regexp {([a-z]*)=(.*)} $arg match key val]} { regsub -all " " ${val} "\\ " val set $key $val } } if {[existsuser ${name}] != 0 || [existsuser ${uid}] != 0} { return } if {${os.platform} eq "darwin"} { exec dscl . -create /Users/${name} Password ${passwd} exec dscl . -create /Users/${name} UniqueID ${uid} exec dscl . -create /Users/${name} PrimaryGroupID ${gid} exec dscl . -create /Users/${name} RealName ${realname} exec dscl . -create /Users/${name} NFSHomeDirectory ${home} exec dscl . -create /Users/${name} UserShell ${shell} } else { # XXX adduser is only available for darwin, add more support here ui_warn "WARNING: adduser is not implemented on $ {os.platform}." ui_warn "The requested user was not created." } } From tabithamc at gmail.com Tue Jan 1 20:47:41 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 20:45:49 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: <14A27BBE-CB12-403B-9878-D01AA8FFA227@macports.org> References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> <15FA2886-6246-4108-A45D-C2D552AC287B@apple.com> <7fccb3000801012001r2baa29a9g547dd19e3052ee69@mail.gmail.com> <14A27BBE-CB12-403B-9878-D01AA8FFA227@macports.org> Message-ID: <7fccb3000801012047x360ce69as3da24aa7f8dd7b9@mail.gmail.com> On 1/1/08, Ryan Schmidt wrote: > > > On Jan 1, 2008, at 22:32, Jordan K. Hubbard wrote: > > > On Jan 1, 2008, at 8:01 PM, Tabitha McNerney wrote: > > > >> Jordan, appreciate the further clarity. Quick question then (just > >> to make sure I'm ultra clear) -- even if a MacPort installs a new > >> entry in the local directory domain with a "Crypt Password" type, > >> what you're saying is that in reality, under Leopard Server (and > >> the past few versions of Mac OS X Server) this password is a > >> Shadow Password disguised to the system as a Crypt Password? I ask > >> because using Workgroup Manager on Leopard Server, I can select > >> the user that was installed by the MacPort (for example, take the > >> openldap MacPort which installs a local directory domain entry > >> with the username "ldap", UID "500" and a User Password Type of > >> "Crypt Password" and I can select the pop-up menu with the "Crypt > >> Password" selection and change the type to either "Shadow > >> Password" or "OpenDirectory" because I am also running an > >> OpenDirectory Master on the same machine). > > > > I'm not sure how MacPorts installs user records on Leopard (I've > > never looked). Presumably, it just drops a plist file into /var/db/ > > dslocal/nodes/Default/users since that's all you need to do in > > Leopard. The contents of that plist file, however, can specify a > > number of different password types - "it all depends" is about the > > best answer I can give you there. You should look at the > > authentication_authority array in the user plists you're wondering > > about and verify that they're doing whatever it is you want them to > > do (this is an array value, so there are multiple options here). > > I'd be surprised if MacPorts was using some obsolete password > > types, but you never know I guess. > > It looks like MacPorts uses dscl to create users and groups, on all > versions of Mac OS X. See src/port1.0/portutil.tcl. > > proc adduser {name args} { > global os.platform > set passwd {*} > set uid [nextuid] > set gid [existsgroup nogroup] > set realname ${name} > set home /dev/null > set shell /dev/null > > foreach arg $args { > if {[regexp {([a-z]*)=(.*)} $arg match key val]} { > regsub -all " " ${val} "\\ " val > set $key $val > } > } > > if {[existsuser ${name}] != 0 || [existsuser ${uid}] != 0} { > return > } > > if {${os.platform} eq "darwin"} { > exec dscl . -create /Users/${name} Password ${passwd} I just checked the man page for dscl on Leopard Server (sorry I don't have a copy of Leopard (non-Server) but its probably the same). It strikes me that dscl is just fine (it would be a major hassle to change MacPorts ports) and it should be left up to the system administrator who takes responsibility for installing and maintaining MacPorts on a Mac OS X / Mac OS X Server system to decide what to do with passwords after the installation by MacPorts: passwd > Usage: passwd user_path [new_pasword | old_password new_pasword] > > Changes a password for a user. The user must be specified by full > path, not just a username. If you are authenticated to the node (either by > specifying the -u > and -P flags or by using the auth command when in interactive node) > then you can simply specify a new password. If you are not authenticated > then the user's old > password must be specified. If passwords are not specified while in > interactive mode, you will be prompted for them. > Thanks for touching on this subject, T.M. exec dscl . -create /Users/${name} UniqueID ${uid} > exec dscl . -create /Users/${name} PrimaryGroupID ${gid} > exec dscl . -create /Users/${name} RealName ${realname} > exec dscl . -create /Users/${name} NFSHomeDirectory ${home} > exec dscl . -create /Users/${name} UserShell ${shell} > } else { > # XXX adduser is only available for darwin, add more support > here > ui_warn "WARNING: adduser is not implemented on $ > {os.platform}." > ui_warn "The requested user was not created." > } > } > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/84f31370/attachment.html From rsync at reifferscheid.org Wed Jan 2 00:10:24 2008 From: rsync at reifferscheid.org (Thomas Reifferscheid) Date: Wed Jan 2 00:08:30 2008 Subject: Pidgin with OTR? In-Reply-To: <477B079A.40001@gmail.com> References: <4776C0FE.1010604@gmail.com> <4776F44C.8030804@reifferscheid.org> <47779628.3090005@reifferscheid.org> <4779E0A3.3090106@gmail.com> <477A9B49.7070701@reifferscheid.org> <477B079A.40001@gmail.com> Message-ID: <477B46F0.6010602@reifferscheid.org> You can have the portfile in a local repository. You find all the details here: http://guide.macports.org/#development.local-repositories However, it would be more easier, if someone would commit the port to the global macports repository. Kind regards Thomas Reifferscheid Matrix Mole wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Thomas Reifferscheid wrote: > >> pigdin-encryption is http://pidgin-encrypt.sourceforge.net/ it has nothing >> to do with pidgin-otr. >> > > Thank you for pointing that out, I didn't realize that they were two > distinct different encryption builds. > > >> pidgin-otr is not available yet in macports. You find details here: >> http://trac.macosforge.org/projects/macports/ticket/13759 >> > > Using the tarball file from that site, where would I place it so that I > could then install it into my port tree? I'd be more than willing to > install the build and report back any bugs I run across while using it. > > Matrix Mole > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHeweaNtosHRPp48MRAigAAJ9uXSSqMZ4NI43RbNupG2/pLZ4IKQCeIt/H > REecfnukwpcX0o5nNapwC8Q= > =wdqE > -----END PGP SIGNATURE----- > From ludwig at fh-worms.de Wed Jan 2 00:18:28 2008 From: ludwig at fh-worms.de (Christoph Ludwig) Date: Wed Jan 2 00:16:43 2008 Subject: gpgme variant for mutt-devel? Message-ID: <20080102081828.GB3170@castellio.ztt.fh-worms.de> Hi, I have a request: I'd be grateful if support for mutt's gpgme crypto backend was added to the port mutt-devel, at least as a variant. Unfortunately, I am swamped so I do not have the time to come up with a portfile patch myself. I'd like to take advantage of the bug fixes that went into mutt over the last year, but right now I am stuck at 1.5.11. Since I need S/MIME support and I am not satisfied with the S/MIME support provided by the "classic" crypto backend that calls openssl's command line tools, I cannot switch to the mutt-devel port. Thanks Christoph -- FH Worms - University of Applied Sciences Fachbereich Informatik / Telekommunikation Erenburgerstr. 19, 67549 Worms, Germany From afb at macports.org Wed Jan 2 01:26:00 2008 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Wed Jan 2 01:24:24 2008 Subject: Rebuild after Xcode update? In-Reply-To: <21757.203.20.35.28.1199244973.squirrel@webmail.tuffmail.net> References: <6D1FBB42-3EBB-4152-BE2B-1635B5686522@macports.org> <21757.203.20.35.28.1199244973.squirrel@webmail.tuffmail.net> Message-ID: <624c7a7b8979f04ef4633b9c442a20fe@macports.org> Boey Maun Suang wrote: > As for the compatibility of code built with Xcode 2.5 with that built > with > Xcode 2.2.1, I think that they should be largely compatible, as my > reading > of the release notes from 2.2.1 to 2.5 is that there have only been > bugfixes and feature enhancements to Xcode's GCC in that time, rather > than > any deliberate compatibility-breaking changes. If that's the case, any > incompatibilities ought to be due to incorrect code produced by Xcode. Xcode 2.4.1 is largely compatible, and fixes the Intel 64-bit issues that makes using Xcode 2.2.1 not work for compiling some ports that want it... Xcode 2.5, on the other hand, introduces some breaking changes so that it can run in a prefix on Leopard - such as not including /usr/share/libtool: http://trac.macports.org/projects/macports/ticket/13334 http://trac.macports.org/projects/macports/ticket/13736 --anders From ramercer at gmail.com Wed Jan 2 03:37:30 2008 From: ramercer at gmail.com (Adam Mercer) Date: Wed Jan 2 03:35:38 2008 Subject: unable to upgrade port py25-scipy In-Reply-To: <2a77b9140801011349tf3fe815ne7899ce218c12748@mail.gmail.com> References: <2a77b9140801011349tf3fe815ne7899ce218c12748@mail.gmail.com> Message-ID: <799406d60801020337v3fc42d1ev2c1aa3527ab7fbe7@mail.gmail.com> On Jan 1, 2008 9:49 PM, Harry Parker wrote: > ------- > building 'scipy.interpolate.dfitpack' extension > error: extension 'scipy.interpolate.dfitpack' has Fortran sources but no > Fortran compiler found > > Warning: the following items did not execute (for py25-scipy): > org.macports.destroot org.macports.build > Error: Unable to upgrade port: 1 > ------- Already requested this in #13776 but the full debug output of the build would be very helpful here. Cheers Adam From mjs at beebo.org Wed Jan 2 06:16:53 2008 From: mjs at beebo.org (Michael Stillwell) Date: Wed Jan 2 06:15:01 2008 Subject: what configuration files are read? In-Reply-To: References: <37CF4227-52D1-4159-9BD8-31451BAA84C7@beebo.org> Message-ID: <140eba4e0801020616r3dbd7b28k2e7ffe56cbfa8bf9@mail.gmail.com> On Jan 1, 2008 12:00 AM, Ryan Schmidt wrote: > > On Dec 31, 2007, at 06:48, Michael Stillwell wrote: > > > How does "port" figure out which configuration files to read? Mine > > is now trying to get configuration information from a non-existent > > file: [ ... ] > > Issue #1: The reason why your two installations are conflicting with > one another is that they both installed their Tcl components to / > Library/Tcl/macports1.0, and the $HOME/scratch/ports instalation's / > Library/Tcl/macports1.0 has overwritten the one from $HOME/Ports. > > [ ... ] > > You could bypass all the arguments and just do it yourself. You > should reinstall both of your installations (or at least the /Ports > one, since its /Library/Tcl/macports1.0 is gone), making sure that at > least one, or perhaps both, of them put their Tcl directory > elsewhere, for example: > > PATH=/usr/bin:/usr/sbin:/bin:/sbin ./configure \ > --prefix=$HOME/Ports \ > --with-tclpackage=$HOME/Ports/share/macports/Tcl Thanks; this worked perfectly. Is it possible to improve the --prefix documentation? "./configure --help" doesn't make it clear that 99% (but not 100%) of the installed files will go into the specified directory, and it's somewhat unexpected that the crucial missing directory of files is configured via --with-tclinclude. --M. -- http://beebo.org +44 78 2118 9049 From hashashin at gmail.com Wed Jan 2 07:16:13 2008 From: hashashin at gmail.com (=?ISO-8859-1?Q?Alberto_Sim=F5es?=) Date: Wed Jan 2 07:14:20 2008 Subject: Activating stalls Message-ID: <2b670b7e0801020716u72327632q2424aa559169491a@mail.gmail.com> Hi I have a Leopard and until some time ago, port worked fine. At the moment, I have a problem with activation. I mean, any package compiles correctly, installs on destroot, and everything, but the 'activating' line appears, and no more information is given. It just freezes. I tried to get with 'top' information about the stalled process, but I did not find anything suspicious. Any hint on what might be happening? Thanks Alberto PS: Also, why 'man' does not find the 'port' manpage? I think this worked correctly on my old Tiger.... :-S -- Alberto Sim?es From macleod at cvrti.utah.edu Wed Jan 2 07:46:48 2008 From: macleod at cvrti.utah.edu (Rob MacLeod) Date: Wed Jan 2 07:45:03 2008 Subject: Emacs and Leopard problems continue In-Reply-To: <88E9028D-D470-43E5-BD51-0EE50D328E3F@apple.com> References: <887865AB-59C2-436B-99CC-15C7CCE06CF4@cvrti.utah.edu> <88E9028D-D470-43E5-BD51-0EE50D328E3F@apple.com> Message-ID: <6154BF4D-DE56-41D0-A12A-B72683275543@cvrti.utah.edu> Hi, This is pretty easy--I want emacs to work in X11. Cheers, Rob On Jan 1, 2008, at 1:16 PM, Jordan K. Hubbard wrote: > OK, I'll bite. What specifically is wrong with the system emacs > that requires folks to struggle so hard to build another copy? It > even supports carbon if you add an app wrapper (like the one I just > attached - a mere 55k, and most of that is the icon), so I'm not > sure what would lead one to struggle so hard to build emacs again. > Yes, the macports version should certainly work just on general > principle, but that's not the question I'm asking. > > - Jordan > > > > > p > On Dec 31, 2007, at 2:58 PM, Rob MacLeod wrote: > >> Hi folks, >> >> I am still struggling with Leopard woes with emacs. >> >> I was able to get emacs, emacs-devel, and emacs-app all made by >> manually applying the patch provided in ticket #13294. emacs made >> in the wrong directory while emacs-devel did better and ended up >> properly placed. >> >> However, neither emacs nor emacs-devel launch a new X window when I >> start them. I vaguely recall that this was a problem in the past >> but I was able with Tiger to get at least one of them (no longer >> sure which) to work in the proper X window mode. >> >> Does anyone know if there are some other settings I need to get a >> full functioning X11 based emacs to work? >> >> In the meantime, I will experiment with emacs-app to see if I can >> get it to work the way I am used to... >> >> Good thing this is the break and I have time to deal with all the >> frustrations of Leopard.... >> >> Happy New Year, >> >> Rob >> >> _______________________________________________ >> macports-users mailing list >> macports-users@lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo/macports-users > From liontooth at cogweb.net Wed Jan 2 08:31:00 2008 From: liontooth at cogweb.net (David Liontooth) Date: Wed Jan 2 08:29:40 2008 Subject: Display separate cpu states in top Message-ID: <477BBC44.5010007@cogweb.net> Dual-core CPUs are now commonplace on Macs. Can top display the load on each core? In Linux, the top from procps has for a while now included this option: <1> :Toggle_Single/Separate_Cpu_States -- On/Off This command affects how the 't' command's Cpu States portion is shown. Although this toggle exists primarily to serve massively-parallel SMP machines, it is not restricted to solely SMP environments. When you see 'Cpu(s):' in the summary area, the '1' toggle is On and all cpu information is gathered in a single line. Otherwise, each cpu is displayed separately as: 'Cpu0, Cpu1, ...' Any way to get this functionality in OSX? Cheers, Dave From caliel at caliel.no-ip.org Wed Jan 2 08:56:18 2008 From: caliel at caliel.no-ip.org (caliel) Date: Wed Jan 2 08:54:27 2008 Subject: Kismet on OSX 10.5.1 Leopard In-Reply-To: References: Message-ID: <610e924ffeded3be62c97f03405596fc@localhost> Paul, Sorry for the delayed response, but I wanted to make sure that the thread is complete for others who are researching. From the KisMAC faq (http://kismac.macpirate.ch/wiki/doku.php?id=faq) ----- If you've updated to OS 10.4.10, you MUST use r239. OS 10.5 (Leopard) breaks AirPort Extreme passive mode support again, but shouldn't break support for other devices (USB and PCMCIA). ----- This is what the Kismet team told me they are also facing. I assume both parties are working on the issue, but it seems to be a communication problem between Apple developers and Kis[Mm]?? developers. Naturally, the proper solution is to use 1.4.10, then I could use either of them. Pioneers, as they say, take the arrows :) --caliel On Sat, 8 Dec 2007 19:33:00 -0800, "paul beard" wrote: > On 11/28/07, caliel wrote: >> >> I have returned home from my holiday travels with eager anticipation to >> try >> kismet with my ralink USB Wi-Fi card. Just as I plugged it in, I > realized >> ...... ...... darwin and viha are the only valid capture sources for > OSX! >> > > Any reason not to use KisMac? > > > > -- > Paul Beard / www.paulbeard.org/ > From ryandesign at macports.org Wed Jan 2 09:15:28 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 09:14:01 2008 Subject: what configuration files are read? In-Reply-To: <140eba4e0801020616r3dbd7b28k2e7ffe56cbfa8bf9@mail.gmail.com> References: <37CF4227-52D1-4159-9BD8-31451BAA84C7@beebo.org> <140eba4e0801020616r3dbd7b28k2e7ffe56cbfa8bf9@mail.gmail.com> Message-ID: <0FABD196-47B8-4B61-B5DA-11E37BFB90CA@macports.org> On Jan 2, 2008, at 08:16, Michael Stillwell wrote: > On Jan 1, 2008 12:00 AM, Ryan Schmidt wrote: > >> On Dec 31, 2007, at 06:48, Michael Stillwell wrote: >> >>> How does "port" figure out which configuration files to read? Mine >>> is now trying to get configuration information from a non-existent >>> file: [ ... ] >> >> Issue #1: The reason why your two installations are conflicting with >> one another is that they both installed their Tcl components to / >> Library/Tcl/macports1.0, and the $HOME/scratch/ports instalation's / >> Library/Tcl/macports1.0 has overwritten the one from $HOME/Ports. >> >> [ ... ] >> >> You could bypass all the arguments and just do it yourself. You >> should reinstall both of your installations (or at least the /Ports >> one, since its /Library/Tcl/macports1.0 is gone), making sure that at >> least one, or perhaps both, of them put their Tcl directory >> elsewhere, for example: >> >> PATH=/usr/bin:/usr/sbin:/bin:/sbin ./configure \ >> --prefix=$HOME/Ports \ >> --with-tclpackage=$HOME/Ports/share/macports/Tcl > > Thanks; this worked perfectly. > > Is it possible to improve the --prefix documentation? "./configure > --help" doesn't make it clear that 99% (but not 100%) of the installed > files will go into the specified directory, and it's somewhat > unexpected that the crucial missing directory of files is configured > via --with-tclinclude. I agree. It's so unclear that I read the ./configure --help, couldn't figure it out, and went searching for Daniel's email (because I remembered seeing it before). But that doesn't help people who don't know to go looking for it. From bengt.nilsson11 at spray.se Wed Jan 2 10:20:13 2008 From: bengt.nilsson11 at spray.se (Bengt Nilsson) Date: Wed Jan 2 10:18:21 2008 Subject: tsclient missing Message-ID: <4B1C0DE4-D01A-438F-A6BD-E850F4509F33@spray.se> Hi! tsclient seems to be missing from the repositories: sh-3.2# port install tsclient ---> Fetching tsclient ---> Attempting to fetch tsclient-0.148.tar.gz from http://www.gnomepro.com/tsclient/ ---> Attempting to fetch tsclient-0.148.tar.gz from http://svn.macports.org/repository/macports/distfiles/tsclient ---> Attempting to fetch tsclient-0.148.tar.gz from http://svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch tsclient-0.148.tar.gz from http://svn.macports.org/repository/macports/downloads/tsclient Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. sh-3.2# Is it coming back, is it just not there yet? BN From matrixm at gmail.com Wed Jan 2 10:24:27 2008 From: matrixm at gmail.com (Matrix Mole) Date: Wed Jan 2 10:22:35 2008 Subject: Activating stalls In-Reply-To: <2b670b7e0801020716u72327632q2424aa559169491a@mail.gmail.com> References: <2b670b7e0801020716u72327632q2424aa559169491a@mail.gmail.com> Message-ID: <477BD6DB.1010808@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alberto Sim?es wrote: > Hi > > I have a Leopard and until some time ago, port worked fine. At the > moment, I have a problem with activation. I mean, any package compiles > correctly, installs on destroot, and everything, but the 'activating' > line appears, and no more information is given. It just freezes. > Any hint on what might be happening? I would suggest using the -d flag for port (ie, sudo port -d install foo) this will give debug information that will be helpful in seeing exactly where the error is occurring. > PS: Also, why 'man' does not find the 'port' manpage? I think this > worked correctly on my old Tiger.... :-S Check your $MANPATH variable at the command prompt 'echo $MANPATH' and see what it lists. I know some time back I had to add /opt/local/man to $MANPATH in my .bashrc file (add a line that says 'export MANPATH=/opt/local/man:$MANPATH' without the quotes) so that it would be able to find the man page for port along with all the files that are installed via macports. Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHe9bbNtosHRPp48MRAvwzAKCKNz4eV/L/VJXYw8g0BS0hhjawGACffSqE t7oNgpIdND9wTMzgsMu+2lw= =vgjn -----END PGP SIGNATURE----- From ryandesign at macports.org Wed Jan 2 10:44:12 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 10:42:44 2008 Subject: tsclient missing In-Reply-To: <4B1C0DE4-D01A-438F-A6BD-E850F4509F33@spray.se> References: <4B1C0DE4-D01A-438F-A6BD-E850F4509F33@spray.se> Message-ID: <5D715D6E-DEEE-40B7-B659-2466632022CF@macports.org> On Jan 2, 2008, at 12:20, Bengt Nilsson wrote: > tsclient seems to be missing from the repositories: > > sh-3.2# port install tsclient > ---> Fetching tsclient > ---> Attempting to fetch tsclient-0.148.tar.gz from http:// > www.gnomepro.com/tsclient/ > ---> Attempting to fetch tsclient-0.148.tar.gz from http:// > svn.macports.org/repository/macports/distfiles/tsclient > ---> Attempting to fetch tsclient-0.148.tar.gz from http:// > svn.macports.org/repository/macports/distfiles/general/ > ---> Attempting to fetch tsclient-0.148.tar.gz from http:// > svn.macports.org/repository/macports/downloads/tsclient > Error: Target org.macports.fetch returned: fetch failed > Error: Status 1 encountered during processing. > sh-3.2# > > > Is it coming back, is it just not there yet? www.gnomepro.com appears to be inaccessible at the moment, hence the distfile cannot be downloaded from that website. According to the wiki page http://en.wikipedia.org/wiki/Tsclient it has been offline for several weeks already. I added a few backup download locations to the portfile in r32452. Wait 30 minutes, then "sudo port selfupdate", then try installing tsclient again and it should work. From ryandesign at macports.org Wed Jan 2 10:48:08 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 10:46:40 2008 Subject: Display separate cpu states in top In-Reply-To: <477BBC44.5010007@cogweb.net> References: <477BBC44.5010007@cogweb.net> Message-ID: On Jan 2, 2008, at 10:31, David Liontooth wrote: > Dual-core CPUs are now commonplace on Macs. Can top display the > load on each core? > > In Linux, the top from procps has for a while now included this > option: > > <1> :Toggle_Single/Separate_Cpu_States -- On/Off > This command affects how the 't' command's Cpu States > portion is shown. Although this toggle exists primarily to serve > massively-parallel > SMP machines, it is not restricted to solely SMP > environments. > > When you see 'Cpu(s):' in the summary area, the '1' > toggle is On and all cpu information is gathered in a single line. > Otherwise, each cpu > is displayed separately as: 'Cpu0, Cpu1, ...' > > Any way to get this functionality in OSX? A quick glance at the top manpage doesn't show me any way to do this. And a quick look through "port search top" doesn't show me any alternate versions of top available. From ryandesign at macports.org Wed Jan 2 10:50:20 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 10:48:54 2008 Subject: gpgme variant for mutt-devel? In-Reply-To: <20080102081828.GB3170@castellio.ztt.fh-worms.de> References: <20080102081828.GB3170@castellio.ztt.fh-worms.de> Message-ID: On Jan 2, 2008, at 02:18, Christoph Ludwig wrote: > I have a request: I'd be grateful if support for mutt's gpgme > crypto backend > was added to the port mutt-devel, at least as a variant. > Unfortunately, I am > swamped so I do not have the time to come up with a portfile patch > myself. [snip] Then you should file an enhancement request ticket in Trac. From ludwig at fh-worms.de Wed Jan 2 11:08:12 2008 From: ludwig at fh-worms.de (Christoph Ludwig) Date: Wed Jan 2 11:06:37 2008 Subject: gpgme variant for mutt-devel? In-Reply-To: References: <20080102081828.GB3170@castellio.ztt.fh-worms.de> Message-ID: <20080102190812.GA3356@castellio.local> On Wed, Jan 02, 2008 at 12:50:20PM -0600, Ryan Schmidt wrote: > On Jan 2, 2008, at 02:18, Christoph Ludwig wrote: > >I have a request: I'd be grateful if support for mutt's gpgme > >crypto backend > >was added to the port mutt-devel, at least as a variant. > >Unfortunately, I am > >swamped so I do not have the time to come up with a portfile patch > >myself. > > > [snip] > > Then you should file an enhancement request ticket in Trac. done, it is #13788. Thanks Christoph -- FH Worms - University of Applied Sciences Fachbereich Informatik / Telekommunikation Erenburgerstr. 19, 67549 Worms, Germany From hashashin at gmail.com Wed Jan 2 11:26:54 2008 From: hashashin at gmail.com (=?ISO-8859-1?Q?Alberto_Sim=F5es?=) Date: Wed Jan 2 11:25:01 2008 Subject: Activating stalls In-Reply-To: <477BD6DB.1010808@gmail.com> References: <2b670b7e0801020716u72327632q2424aa559169491a@mail.gmail.com> <477BD6DB.1010808@gmail.com> Message-ID: <2b670b7e0801021126r4615b4d1vd764caf531ce2ddf@mail.gmail.com> Hi, Matrix. On Jan 2, 2008 6:24 PM, Matrix Mole wrote: > > I have a Leopard and until some time ago, port worked fine. At the > > moment, I have a problem with activation. I mean, any package compiles > > correctly, installs on destroot, and everything, but the 'activating' > > line appears, and no more information is given. It just freezes. > I would suggest using the -d flag for port (ie, sudo port -d install > foo) this will give debug information that will be helpful in seeing > exactly where the error is occurring. It did not help much :( [ambs@rachmaninoff ~]$ sudo port -d install ispell Password: DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/ispell DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/ispell DEBUG: Requested variant darwin is not provided by port ispell. DEBUG: Requested variant i386 is not provided by port ispell. DEBUG: Requested variant macosx is not provided by port ispell. DEBUG: Skipping completed org.macports.main (ispell) DEBUG: Skipping completed org.macports.fetch (ispell) DEBUG: Skipping completed org.macports.checksum (ispell) DEBUG: Skipping completed org.macports.extract (ispell) DEBUG: Skipping completed org.macports.patch (ispell) DEBUG: Skipping completed org.macports.configure (ispell) DEBUG: Skipping completed org.macports.build (ispell) DEBUG: Skipping completed org.macports.destroot (ispell) DEBUG: Skipping org.macports.install (ispell) since this port is already installed DEBUG: Executing org.macports.activate (ispell) ---> Activating ispell 3.3.02_0 Thanks -- Alberto Sim?es From frstan at bellsouth.net Wed Jan 2 12:06:55 2008 From: frstan at bellsouth.net (William Davis) Date: Wed Jan 2 12:05:02 2008 Subject: Display separate cpu states in top In-Reply-To: References: <477BBC44.5010007@cogweb.net> Message-ID: <1E9BB937-0520-45D0-BB23-0F2CBE96EAE8@bellsouth.net> see On Jan 2, 2008, at 1:48 PM, Ryan Schmidt wrote: > > On Jan 2, 2008, at 10:31, David Liontooth wrote: > >> Dual-core CPUs are now commonplace on Macs. Can top display the >> load on each core? >> >> In Linux, the top from procps has for a while now included this >> option: >> >> <1> :Toggle_Single/Separate_Cpu_States -- On/Off >> This command affects how the 't' command's Cpu States >> portion is shown. Although this toggle exists primarily to serve >> massively-parallel >> SMP machines, it is not restricted to solely SMP >> environments. >> >> When you see 'Cpu(s):' in the summary area, the '1' >> toggle is On and all cpu information is gathered in a single line. >> Otherwise, each cpu >> is displayed separately as: 'Cpu0, Cpu1, ...' >> >> Any way to get this functionality in OSX? > > A quick glance at the top manpage doesn't show me any way to do > this. And a quick look through "port search top" doesn't show me any > alternate versions of top available. > > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users William Davis frstanATbellsouthDOTnet Mac OS X.5.1 Darwin 9.1.0 X11.app 2.1.1 - (xorg-server 1.3.0-apple5) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non -------------- next part -------------- Skipped content of type multipart/related From tabithamc at gmail.com Wed Jan 2 12:22:54 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Wed Jan 2 12:21:00 2008 Subject: Incredible speed ups on Leopard!? Message-ID: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> Has anyone else noticed incredible MacPorts speed up improvements when installing various ports? Here's an example: The same hardware (Xserve Intel 2 x 2 GhZ Dual Core Intel). Once this machine was running Tiger Server with MacPorts 1.5.0 and I installed the gcc41 port which (if my notes are accurate) took about 88minutes to install from beginning to end (some of the time could have been eaten up in the "fetching" of the resource source files). Anyway, the same port on Leopard Server on the same machine with MacPort 1.6.0 took me roughly 20 minutes to install today. From 88 to 20 minutes is almost unheard of. I checked the port files too, to make sure the version of the gcc41 port I was installing was the same: Tiger Server: gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > darwin_i386, powerpc, odcctools) > Leopard Server: gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > darwin_i386, powerpc, odcctools) > I presume this is because Leopard and Leopard Server are now leveraging the Apple Developer tools with a complete 64-bit wide architecture (both the hardware and the software)? Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080102/55a771dc/attachment.html From tabithamc at gmail.com Wed Jan 2 13:17:06 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Wed Jan 2 13:15:12 2008 Subject: Incredible speed ups on Leopard!? In-Reply-To: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> References: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> Message-ID: <7fccb3000801021317y364a39adre1d11a6b4b6962c4@mail.gmail.com> I may have spoken too soon without investigating under the hood because building the gcc42 port took the same amount of time on Leopard Server as Tiger Server on the same Xserve (70 minute). -T.M. On 1/2/08, Tabitha McNerney wrote: > > Has anyone else noticed incredible MacPorts speed up improvements when > installing various ports? > > Here's an example: The same hardware (Xserve Intel 2 x 2 GhZ Dual Core > Intel). Once this machine was running Tiger Server with MacPorts 1.5.0 and > I installed the gcc41 port which (if my notes are accurate) took about 88minutes to install from beginning to end (some of the time could have been > eaten up in the "fetching" of the resource source files). Anyway, the same > port on Leopard Server on the same machine with MacPort 1.6.0 took me > roughly 20 minutes to install today. From 88 to 20 minutes is almost > unheard of. I checked the port files too, to make sure the version of the > gcc41 port I was installing was the same: > > Tiger Server: > > gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > > darwin_i386, powerpc, odcctools) > > > > Leopard Server: > > gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > > darwin_i386, powerpc, odcctools) > > > > I presume this is because Leopard and Leopard Server are now leveraging > the Apple Developer tools with a complete 64-bit wide architecture (both the > hardware and the software)? > > Thanks, > > T.M . > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080102/e6ca96b0/attachment.html From tabithamc at gmail.com Wed Jan 2 15:01:09 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Wed Jan 2 14:59:17 2008 Subject: gnustep family of ports and Leopard Message-ID: <7fccb3000801021501l2ea51371y839c4c454bfb388b@mail.gmail.com> Hello all -- I noticed ticket #13466 which states that there are problems building the gnustep port on Leopard 10.5.1 I discovered today that building the actual "gnustep" port worked fine (Leopard Server 10.5.1) but then attempting to build gnustep-gui and its dependencies had problems. I can either update ticket #13466 or issue a new ticket. What would be the best course to take? Has anyone else had problems building various gnustep related family of ports on Leopard? Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080102/fdde055b/attachment.html From spindle23 at gmail.com Wed Jan 2 15:03:39 2008 From: spindle23 at gmail.com (spindle) Date: Wed Jan 2 15:01:47 2008 Subject: darwin ports and xfree86 Message-ID: <477C184B.5070805@gmail.com> Hello everybody, i want to install ddd package with darwin ports (with sudo port install ddd) but this wants to compile xfree86 packet,and it gets errors. i want it to use Apple X11 instead of xfree86,how can i do that? Thanks... From tabithamc at gmail.com Wed Jan 2 15:33:34 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Wed Jan 2 15:31:39 2008 Subject: darwin ports and xfree86 In-Reply-To: <477C184B.5070805@gmail.com> References: <477C184B.5070805@gmail.com> Message-ID: <7fccb3000801021533w41c9b9edhc7ac168215247b2@mail.gmail.com> On 1/2/08, spindle wrote: > > Hello everybody, > > i want to install ddd package with darwin ports > > (with sudo port install ddd) > > but this wants to compile xfree86 packet,and it gets errors. > > i want it to use Apple X11 instead of xfree86,how can i do that? spindle, what version of Mac OS X are you use? I'm using Leopard and some of the well seasoned respected MacPorts maintainers and I had a threaded discussion about this yesterday (check the archives for yesterday, 1 January 2008) -T.M. Thanks... > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080102/58ca22ce/attachment.html From walt at wump.org Wed Jan 2 16:12:22 2008 From: walt at wump.org (Walt Pawley) Date: Wed Jan 2 16:18:00 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> Message-ID: At 8:12 AM -0700 12/29/07, Chris Janton wrote: >I would be glad to help figure things out for Panther. I don't expect >to be upgrading that OS for some time (long) so having a working, >viable MacPorts is important to me. Sadly, supporting older versions of Mac OS X is not something the MacPorts effort has been "up" for. The excuse is always the same - no one else is using that old stuff. Which bothers me just a bit as I see far more Mac users not using the latest stuff than I do those who bleed along with the progressing edge and not just because I look in a mirror once a day at least. I could be wrong, but I suspect that the gestalt of the MacPorts effort would have to change to capture old source distributions of the ports referenced files before it'd make a lot of sense to "retain compatibility". -- Walter M. Pawley Wump Research & Company 676 River Bend Road, Roseburg, OR 97470 541-672-8975 From ryandesign at macports.org Wed Jan 2 16:34:58 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 16:33:29 2008 Subject: Pidgin with OTR? In-Reply-To: <477B46F0.6010602@reifferscheid.org> References: <4776C0FE.1010604@gmail.com> <4776F44C.8030804@reifferscheid.org> <47779628.3090005@reifferscheid.org> <4779E0A3.3090106@gmail.com> <477A9B49.7070701@reifferscheid.org> <477B079A.40001@gmail.com> <477B46F0.6010602@reifferscheid.org> Message-ID: Anders committed it. On Jan 2, 2008, at 02:10, Thomas Reifferscheid wrote: > You can have the portfile in a local repository. You find all the > details here: > > http://guide.macports.org/#development.local-repositories > > However, it would be more easier, if someone would commit the port to > the global macports repository. > > Kind regards > Thomas Reifferscheid > > > Matrix Mole wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Thomas Reifferscheid wrote: >> >>> pigdin-encryption is http://pidgin-encrypt.sourceforge.net/ it >>> has nothing >>> to do with pidgin-otr. >>> >> >> Thank you for pointing that out, I didn't realize that they were two >> distinct different encryption builds. >> >> >>> pidgin-otr is not available yet in macports. You find details here: >>> http://trac.macosforge.org/projects/macports/ticket/13759 >>> >> >> Using the tarball file from that site, where would I place it so >> that I >> could then install it into my port tree? I'd be more than willing to >> install the build and report back any bugs I run across while >> using it. From ryandesign at macports.org Wed Jan 2 16:53:20 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 16:51:51 2008 Subject: darwin ports and xfree86 In-Reply-To: <477C184B.5070805@gmail.com> References: <477C184B.5070805@gmail.com> Message-ID: On Jan 2, 2008, at 17:03, spindle wrote: > Hello everybody, > > i want to install ddd package with darwin ports > > (with sudo port install ddd) > > but this wants to compile xfree86 packet,and it gets errors. > > i want it to use Apple X11 instead of xfree86,how can i do that? You need both X11User.pkg and X11SDK.pkg. Depending on your version of Mac OS X, these are found in different places. For Leopard: X11User is already installed. Install Xcode 3 to get X11SDK. For Tiger: X11User is an optional install on your Mac OS X DVD. After you do that, install X11SDK from the Xcode 2.5 disk image downloaded from Apple Developer Connection. For Panther: X11User is available from Apple Support Downloads. After that's installed, install the X11SDK from the Xcode 1.5 disk image downloaded from Apple Developer Connection. Once X11User and X11SDK are installed, ports that claim to depend on XFree86 will make use of Apple X11 instead of using XFree86. From liontooth at cogweb.net Wed Jan 2 19:09:07 2008 From: liontooth at cogweb.net (David Liontooth) Date: Wed Jan 2 19:07:18 2008 Subject: Display separate cpu states in top In-Reply-To: <1E9BB937-0520-45D0-BB23-0F2CBE96EAE8@bellsouth.net> References: <477BBC44.5010007@cogweb.net> <1E9BB937-0520-45D0-BB23-0F2CBE96EAE8@bellsouth.net> Message-ID: <477C51D3.6020405@cogweb.net> William Davis wrote: > see Thanks, that works; I was hoping for a CLI version. Dave > On Jan 2, 2008, at 1:48 PM, Ryan Schmidt wrote: > >> >> On Jan 2, 2008, at 10:31, David Liontooth wrote: >> >>> Dual-core CPUs are now commonplace on Macs. Can top display the load >>> on each core? >>> >>> In Linux, the top from procps has for a while now included this option: >>> >>> <1> :Toggle_Single/Separate_Cpu_States -- On/Off >>> This command affects how the 't' command's Cpu States >>> portion is shown. Although this toggle exists primarily to serve >>> massively-parallel >>> SMP machines, it is not restricted to solely SMP >>> environments. >>> >>> When you see 'Cpu(s):' in the summary area, the '1' >>> toggle is On and all cpu information is gathered in a single line. >>> Otherwise, each cpu >>> is displayed separately as: 'Cpu0, Cpu1, ...' >>> >>> Any way to get this functionality in OSX? >> >> A quick glance at the top manpage doesn't show me any way to do this. >> And a quick look through "port search top" doesn't show me any >> alternate versions of top available. >> >> >> _______________________________________________ >> macports-users mailing list >> macports-users@lists.macosforge.org >> >> http://lists.macosforge.org/mailman/listinfo/macports-users > > > > William Davis > frstanATbellsouthDOTnet > Mac OS X.5.1 Darwin 9.1.0 > X11.app 2.1.1 - (xorg-server 1.3.0-apple5) > Mac Mini Intel Duo @ 1.86 GHz > > Mundus vult decepi, ego non > From jkh at apple.com Wed Jan 2 19:08:57 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Wed Jan 2 19:08:32 2008 Subject: Incredible speed ups on Leopard!? In-Reply-To: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> References: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> Message-ID: [ Resent from correct account, so MacPorts won't bounce it back again ] On Jan 2, 2008, at 12:22 PM, Tabitha McNerney wrote: > Has anyone else noticed incredible MacPorts speed up improvements > when installing various ports? > > Here's an example: The same hardware (Xserve Intel 2 x 2 GhZ Dual > Core Intel). Once this machine was running Tiger Server with > MacPorts 1.5.0 and I installed the gcc41 port which (if my notes are > accurate) took about 88 minutes to install from beginning to end > (some of the time could have been eaten up in the "fetching" of the > resource source files). Anyway, the same port on Leopard Server on > the same machine with MacPort 1.6.0 took me roughly 20 minutes to > install today. From 88 to 20 minutes is almost unheard of. I checked > the port files too, to make sure the version of the gcc41 port I was > installing was the same: > > Tiger Server: > > gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > darwin_i386, powerpc, odcctools) > > Leopard Server: > > gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > darwin_i386, powerpc, odcctools) > > I presume this is because Leopard and Leopard Server are now > leveraging the Apple Developer tools with a complete 64-bit wide > architecture (both the hardware and the software)? No, I think it's because Leopard's Tcl no longer searches an insane search path (including network volumes) as part of its startup. When we made this change in Leopard (largely because of pathological performance problems I noticed with MacPorts and fs_usage(1)), a full minute was shaved off the most basic port operations, including build/ install (it's more observable with something like "port search"). - Jordan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080102/dfee8b98/attachment.html From scacinto at gmail.com Wed Jan 2 21:56:26 2008 From: scacinto at gmail.com (Scott Petersen) Date: Wed Jan 2 21:54:30 2008 Subject: arts fails to build Message-ID: <9c7c33430801022156t168342cdk9129613279ddbf3a@mail.gmail.com> hi, i've attempted to install the arts port. It fails with the following error: Error: Target org.macports.patch returned: shell command "cd '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_audio_arts/work/arts- 1.1.2' && sed -e 's#@PREFIX@#/opt/local#g' '/opt/local/var/macports/sources/rsync.macports.org/release/ports/audio/arts/files/stable/patch- arts-artsc-artsc-config.in.diff' | patch -p0" returned error 1 Command output: patching file artsc/artsc-config.in Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file artsc/artsc-config.in.rej Error: Status 1 encountered during processing. Is there something I am doing wrong? I had previously gotten an autoconf version error (it said KDE needs 2.54, etc. and that I was using 2.61.) I uninstalled autoconf 2.61 and tried an earlier version, but no go. Upon reinstalling the newest version the above error appeared. Many thanks for any and all advice. -Scott -- Scott Petersen, composer Eastman Computer Music Center Eastman School of Music www.scottpetersen.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/66449362/attachment.html From ryandesign at macports.org Wed Jan 2 22:21:06 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 22:19:38 2008 Subject: arts fails to build In-Reply-To: <9c7c33430801022156t168342cdk9129613279ddbf3a@mail.gmail.com> References: <9c7c33430801022156t168342cdk9129613279ddbf3a@mail.gmail.com> Message-ID: On Jan 2, 2008, at 23:56, Scott Petersen wrote: > hi, i've attempted to install the arts port. It fails with the > following error: > > Error: Target org.macports.patch returned: shell command "cd '/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_audio > _arts/work/arts- 1.1.2' && sed -e 's#@PREFIX@#/opt/local#g' '/opt/ > local/var/macports/sources/rsync.macports.org/release/ports/audio/ > arts/files/stable/patch-arts-artsc-artsc-config.in.diff' | patch - > p0" returned error 1 > Command output: patching file artsc/artsc-config.in > Reversed (or previously applied) patch detected! Assume -R? [n] > Apply anyway? [n] > Skipping patch. > 1 out of 1 hunk ignored -- saving rejects to file artsc/artsc- > config.in.rej > > Error: Status 1 encountered during processing. > > > Is there something I am doing wrong? I had previously gotten an > autoconf version error (it said KDE needs 2.54, etc. and that I > was using 2.61.) I uninstalled autoconf 2.61 and tried an earlier > version, but no go. Upon reinstalling the newest version the above > error appeared. > > Many thanks for any and all advice. Hi Scott. You're not doing anything wrong. I just took a look at the aRts portfile, and it's pretty screwy. I get a different error but it also doesn't work for me. I filed a ticket. http://trac.macosforge.org/projects/macports/ticket/13800 From tabithamc at gmail.com Thu Jan 3 03:01:05 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Thu Jan 3 02:59:12 2008 Subject: Incredible speed ups on Leopard!? In-Reply-To: References: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> Message-ID: <7fccb3000801030301xddcb884wbc2153b60da86f8a@mail.gmail.com> On 1/2/08, Jordan K. Hubbard wrote: > > [ Resent from correct account, so MacPorts won't bounce it back again ] > On Jan 2, 2008, at 12:22 PM, Tabitha McNerney wrote: > > Has anyone else noticed incredible MacPorts speed up improvements when > installing various ports? > > Here's an example: The same hardware (Xserve Intel 2 x 2 GhZ Dual Core > Intel). Once this machine was running Tiger Server with MacPorts 1.5.0 and > I installed the gcc41 port which (if my notes are accurate) took about 88minutes to install from beginning to end (some of the time could have been > eaten up in the "fetching" of the resource source files). Anyway, the same > port on Leopard Server on the same machine with MacPort 1.6.0 took me > roughly 20 minutes to install today. From 88 to 20 minutes is almost > unheard of. I checked the port files too, to make sure the version of the > gcc41 port I was installing was the same: > > Tiger Server: > > gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > > darwin_i386, powerpc, odcctools) > > > > Leopard Server: > > gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > > darwin_i386, powerpc, odcctools) > > > > I presume this is because Leopard and Leopard Server are now leveraging > the Apple Developer tools with a complete 64-bit wide architecture (both the > hardware and the software)? > > > No, I think it's because Leopard's Tcl no longer searches an insane search > path (including network volumes) as part of its startup. When we made this > change in Leopard (largely because of pathological performance problems I > noticed with MacPorts and fs_usage(1)), a full minute was shaved off the > most basic port operations, including build/install (it's more observable > with something like "port search"). > Jordan, Thank you for providing a reality check (and thanks to Apple for modifying Leopard's Tcl to speed things up). I wonder then, will having a 64-bit operating system with 64-bit tools (e.g., Xcode) assist anywhere in the process of compiling a MacPort (or running a MacPort)? I think I did read in a much earlier post several weeks ago whereby someone asked a similar question about gaining 64-bit binaries and I think I recall that the answer is that its possible (but forgot the details of how -- perhaps just "automagic" with the gcc compiler provided by Apple with Xcode dev tools? For what its worth, I'm having quite an enjoyable time using Leopard Server and am thankful to the MacPorts community for making the transition to Leopard / Leopard Server quite smooth with MacPorts 1.6.0. Thanks, T.M. - Jordan > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/d01741a1/attachment-0001.html From mww at macports.org Thu Jan 3 04:11:53 2008 From: mww at macports.org (Markus Weissmann) Date: Thu Jan 3 04:10:08 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> Message-ID: <41C29E3E-E827-4654-9FBB-C3D78664C3DD@macports.org> On 3 Jan 2008, at 01:12, Walt Pawley wrote: > At 8:12 AM -0700 12/29/07, Chris Janton wrote: >> I would be glad to help figure things out for Panther. I don't expect >> to be upgrading that OS for some time (long) so having a working, >> viable MacPorts is important to me. > > Sadly, supporting older versions of Mac OS X is not something > the MacPorts effort has been "up" for. The excuse is always the > same - no one else is using that old stuff. Which bothers me > just a bit as I see far more Mac users not using the latest > stuff than I do those who bleed along with the progressing edge > and not just because I look in a mirror once a day at least. > > I could be wrong, but I suspect that the gestalt of the > MacPorts effort would have to change to capture old source > distributions of the ports referenced files before it'd make a > lot of sense to "retain compatibility". It is not like we actively oppose supporting 10.3, but our manpower is very limited and some maintainers might even have access to either 10.4 or 10.5 only. So if you want to work on a "long term support" version of ports, you're welcome to join us -- we'll see if perhaps an alternative ports tree could be a solution to this problem. Regards, -Markus -- Dipl. Inf. (FH) Markus W. Weissmann http://www.macports.org/ http://www.mweissmann.de/ From hashashin at gmail.com Thu Jan 3 06:31:03 2008 From: hashashin at gmail.com (=?ISO-8859-1?Q?Alberto_Sim=F5es?=) Date: Thu Jan 3 06:29:07 2008 Subject: Activating stalls In-Reply-To: <2b670b7e0801021126r4615b4d1vd764caf531ce2ddf@mail.gmail.com> References: <2b670b7e0801020716u72327632q2424aa559169491a@mail.gmail.com> <477BD6DB.1010808@gmail.com> <2b670b7e0801021126r4615b4d1vd764caf531ce2ddf@mail.gmail.com> Message-ID: <2b670b7e0801030631h4919b7fey2f34273e82d0e362@mail.gmail.com> A reboot seems to have helped with this. On Jan 2, 2008 7:26 PM, Alberto Sim?es wrote: > Hi, Matrix. > > On Jan 2, 2008 6:24 PM, Matrix Mole wrote: > > > I have a Leopard and until some time ago, port worked fine. At the > > > moment, I have a problem with activation. I mean, any package compiles > > > correctly, installs on destroot, and everything, but the 'activating' > > > line appears, and no more information is given. It just freezes. > > > I would suggest using the -d flag for port (ie, sudo port -d install > > foo) this will give debug information that will be helpful in seeing > > exactly where the error is occurring. > > It did not help much :( > > [ambs@rachmaninoff ~]$ sudo port -d install ispell > Password: > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/ispell > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/ispell > DEBUG: Requested variant darwin is not provided by port ispell. > DEBUG: Requested variant i386 is not provided by port ispell. > DEBUG: Requested variant macosx is not provided by port ispell. > DEBUG: Skipping completed org.macports.main (ispell) > DEBUG: Skipping completed org.macports.fetch (ispell) > DEBUG: Skipping completed org.macports.checksum (ispell) > DEBUG: Skipping completed org.macports.extract (ispell) > DEBUG: Skipping completed org.macports.patch (ispell) > DEBUG: Skipping completed org.macports.configure (ispell) > DEBUG: Skipping completed org.macports.build (ispell) > DEBUG: Skipping completed org.macports.destroot (ispell) > DEBUG: Skipping org.macports.install (ispell) since this port is > already installed > DEBUG: Executing org.macports.activate (ispell) > ---> Activating ispell 3.3.02_0 > > Thanks > -- > Alberto Sim?es > -- Alberto Sim?es From someguyonearth at gmail.com Thu Jan 3 07:35:58 2008 From: someguyonearth at gmail.com (Some Guy) Date: Thu Jan 3 07:34:02 2008 Subject: problem using port to install gnucash on mac 10.5 In-Reply-To: <38E322B1-12C0-4F25-B921-6010027D3CCE@macports.org> References: <9153cb050801010540y6a8f53cdw501b27bcb636174f@mail.gmail.com> <38E322B1-12C0-4F25-B921-6010027D3CCE@macports.org> Message-ID: <9153cb050801030735o54ecd589u3ad4e46ee2cde1ab@mail.gmail.com> thanks. Unfortunately i now get a problem with avahi ---> Configuring avahi > Error: Target org.macports.configure returned: configure failure: shell > command " cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_avahi/work/avahi- > 0.6.17" && ./configure --prefix=/opt/local --disable-autoipd --disable-qt3 > --disable-qt4 --disable-mono --disable-monodoc --with-distro=darwin " > returned error 1 > Command output: checking for sys/prctl.h... no > checking for chroot... yes > checking for dlopen in -ldl... yes > checking for dlfcn.h... (cached) yes > checking for pkg-config... yes > checking for pkg-config... /opt/local/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for GLIB20... yes > checking for GTK20... yes > checking for GLADE20... yes > checking for DBUS... yes > Your D-Bus version is 1,0,2. > checking for dbus_connection_close... yes > checking for dbus_bus_get_private... yes > checking for XML_ParserCreate in -lexpat... yes > checking expat.h usability... yes > checking expat.h presence... yes > checking for expat.h... yes > checking for gdbm_open in -lgdbm... yes > checking gdbm.h usability... yes > checking gdbm.h presence... yes > checking for gdbm.h... yes > checking for LIBDAEMON... yes > checking whether /opt/local/bin/python2.5 version >= 2.4... yes > checking for /opt/local/bin/python2.5 version... 2.5 > checking for /opt/local/bin/python2.5 platform... darwin > checking for /opt/local/bin/python2.5 script directory... > ${prefix}/lib/python2.5/site-packages > checking for /opt/local/bin/python2.5 extension module directory... > ${exec_prefix}/lib/python2.5/site-packages > checking for python module gtk... no > configure: error: Could not find Python module gtk > > Error: The following dependencies failed to build: evince avahi esound > gconf intltool orbit2 libidl gnome-doc-utils iso-codes py25-hashlib openssl > py25-libxml2 gnome-icon-theme icon-naming-utils p5-getopt-long p5-pathtools > p5-xml-simple p5-test-simple p5-test-harness p5-xml-namespacesupport > p5-xml-sax gnome-keyring libgcrypt libgpg-error gnome-vfs gnome-mime-data > howl neon libart_lgpl libgnome libbonobo popt libgnomecanvas gail libgnomeui > libbonoboui m4 nautilus eel gnome-desktop fribidi startup-notification > gnome-menus libexif librsvg libcroco libgsf shared-mime-info poppler > poppler-data gnucash-docs yelp firefox-x11 zip libgtkhtml goffice03 > libgnomeprintui libgnomeprint bison libgnomecups pcre guile16 readline > ncurses ncursesw gawk libgtkhtml3 p5-finance-quote p5-crypt-ssleay > p5-libwww-perl p5-compress-zlib p5-compress-raw-zlib p5-io-compress-base > p5-scalar-list-utils p5-io-compress-zlib p5-html-parser p5-html-tagset > p5-uri p5-datemanip p5-html-tableextract slib slib-guile16 > Error: Status 1 encountered during processing. > On Jan 1, 2008 9:17 PM, Ryan Schmidt wrote: > On Jan 1, 2008, at 07:40, Some Guy wrote: > > > could anyone please help, i have been trying to install gnucash on > > my mac but i get this; > > > > > > "---> Building aqbanking with target all > [snip] > > ld: cycle in dylib re-exports with /usr/X11R6/lib/libGL.dylib > > You are experiencing this bug: > > http://trac.macosforge.org/projects/macports/ticket/13173 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/3c050444/attachment.html From tom at vilot.com Thu Jan 3 08:31:10 2008 From: tom at vilot.com (Tom Vilot) Date: Thu Jan 3 08:29:19 2008 Subject: Install fails Message-ID: <3442B39B-8364-4C0C-AD93-7009A068FCE1@vilot.com> I tried the disk image and received an error: The following install step failed: run preflight script. I tried from source, and got: ===> making all in src/registry2.0 cc -dynamiclib -L/usr/local/lib registry.o util.o entry.o entryobj.o - o registry.dylib -L/System/Library/Frameworks/Tcl.framework/Versions/ 8.4 -ltclstub8.4 -L/usr/local/lib ../cregistry/cregistry.a -lsqlite3 ld: in ../cregistry/cregistry.a, archive has no table of contents collect2: ld returned 1 exit status make[2]: *** [registry.dylib] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1 From jkh at apple.com Thu Jan 3 11:10:05 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Thu Jan 3 11:09:37 2008 Subject: Incredible speed ups on Leopard!? In-Reply-To: <7fccb3000801030301xddcb884wbc2153b60da86f8a@mail.gmail.com> References: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> <7fccb3000801030301xddcb884wbc2153b60da86f8a@mail.gmail.com> Message-ID: <12A83712-83A5-4B5F-98E9-30AE99F9F47F@apple.com> On Jan 3, 2008, at 3:01 AM, Tabitha McNerney wrote: > Thank you for providing a reality check (and thanks to Apple for > modifying Leopard's Tcl to speed things up). I wonder then, will > having a 64-bit operating system with 64-bit tools ( e.g., Xcode) > assist anywhere in the process of compiling a MacPort (or running a > MacPort)? I think I did read in a much earlier post several weeks > ago whereby someone asked a similar question about gaining 64-bit > binaries and I think I recall that the answer is that its possible > (but forgot the details of how -- perhaps just "automagic" with the > gcc compiler provided by Apple with Xcode dev tools? I think that for the most part, the 64 bit environment is not going to impact MacPorts as a whole. You gain some performance due to having the extra registers, but you also lose performance due to increased memory pressure and, at least right now, there's just no reason to compile something 64 bit unless it's the sort of application with a really large working set (scientific simulation, photo processing tools working on RAW images, etc). - Jordan From guido.soranzio at gmail.com Thu Jan 3 11:36:43 2008 From: guido.soranzio at gmail.com (Guido Soranzio) Date: Thu Jan 3 11:34:50 2008 Subject: problem using port to install gnucash on mac 10.5 Message-ID: Some Guy wrote: > thanks. Unfortunately i now get a problem with avahi: >> checking for python module gtk... no >> configure: error: Could not find Python module gtk A temporary workaround has been committed today: you should reinstall py25-gobject, py25-cairo and py25-gtk. Regards, Guido From tabithamc at gmail.com Thu Jan 3 12:17:21 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Thu Jan 3 12:15:24 2008 Subject: Standardizing a MacPorts system Message-ID: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> Hello all -- I would like to build, from source, on an Xserve running Leopard Server, a "standard" MacPorts system that could be deployed, in an organization, on numerous other Apple servers running the same version of the OS (e.g. Leopard Server). In doing so I would use Apple's command-line tools (such as hdiutil and asr) create a restorable disk image (.dmg) file of a disc volume that hangs off an external disk on my original Xserve which houses the MacPorts prefix (e.g., /opt/local). I would then restore from this disc image to the additional machines slated to be the recipients of the original standard. I don't see any immediate problems in doing so, however I have noticed when installing some ports (when I have occasionally enabled verbose mode "-v" during the install), depending on the port, some ports seem to take into consideration the Hostname of the Xserve I'm running it on. On my Xserve running Leopard Server, the Hostname is very importantly tied to the DNS name because I am running Apple's DNS server that is buncled with Leopard Server since I need it for other services on the machine which are not directly related to MacPorts such as running an OpenDirectory Master. The problem is, with hundreds of MacPorts tied together and with complex dependency chains, how can anyone determine when a specific MacPort reads the hostname and uses the hostname of the machine during the configuration process (unless a sys admin such as myself builds each and every port with verbose mode and analysis the output grepping for the hostname)? It might be problematic if the hostname of any given MacPort somehow becomes "hard wired" into the port itself during the configuration / install processing. Then again, I might be making a mountain out of a mole hill. Has anyone else built a Standardized MacPorts system that is cloned to multiple Macs? Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/65702ac8/attachment.html From macports.users at gmail.com Thu Jan 3 12:18:47 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Thu Jan 3 12:17:06 2008 Subject: sudo port upgrade outdated > PortUpgradeOutdated.log Message-ID: <9345764E-E5AA-4069-A4E9-0568B9E84C89@gmail.com> How do I get the port to write the output to a log file? `$ sudo port upgrade outdated > PortUpgradeOutdated.log' didn't fly well. From macports.users at gmail.com Thu Jan 3 14:32:10 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Thu Jan 3 14:30:16 2008 Subject: $ sudo port -f install MacPorts Message-ID: <76AEA96B-0DD7-41DC-919E-A498DF38B3C4@gmail.com> $ sudo port -f install MacPorts Portfile changed since last build; discarding previous state. ---> Fetching MacPorts ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// svn.macports.org/repository/macports/distfiles/MacPorts-1.6.0 ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// svn.macports.org/repository/macports/distfiles/general/MacPorts-1.6.0 ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// svn.macports.org/repository/macports/downloads/MacPorts-1.6.0 ---> Verifying checksum(s) for MacPorts ---> Extracting MacPorts ---> Configuring MacPorts Fixing your MacOSX10.4u installation by copying libtclstub8.4.a to / Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/ Tcl.framework/Versions/8.4/libtclstub8.4.a Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutil s_MacPorts/work/MacPorts-1.6.0" && ./configure --prefix=/opt/local -- enable-readline " returned error 1 Command output: configure: error: cannot run /bin/sh ./config.sub Error: Status 1 encountered during processing. $ From macports.users at gmail.com Thu Jan 3 14:40:21 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Thu Jan 3 14:38:25 2008 Subject: $ sudo port -f install MacPorts Message-ID: <87FFC008-A323-415C-ADF4-88A4E3A69370@gmail.com> $ sudo port -fvd install MacPorts DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/sysutils/MacPorts DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/sysutils/MacPorts DEBUG: Requested variant powerpc is not provided by port MacPorts. DEBUG: Requested variant darwin is not provided by port MacPorts. DEBUG: Requested variant macosx is not provided by port MacPorts. DEBUG: Executing variant darwin_8 provides darwin_8 DEBUG: Executing variant darwin_8_powerpc provides darwin_8_powerpc DEBUG: Skipping completed org.macports.main (MacPorts) DEBUG: Skipping completed org.macports.fetch (MacPorts) DEBUG: Skipping completed org.macports.checksum (MacPorts) DEBUG: Skipping completed org.macports.extract (MacPorts) DEBUG: Skipping completed org.macports.patch (MacPorts) ---> Configuring MacPorts DEBUG: Executing proc-pre-org.macports.configure-configure-0 DEBUG: Executing org.macports.configure (MacPorts) DEBUG: Using compiler 'Mac OS X gcc 4.0' DEBUG: Environment: CFLAGS='-O2 -isysroot /Developer/SDKs/ MacOSX10.4u.sdk -arch ppc -arch i386' CXXFLAGS='-O2' CPP='/usr/bin/ cpp-4.0' CXX='/usr/bin/g++-4.0' F90FLAGS='-O2' SHLIB_LDFLAGS='-Wl,- syslibroot,/Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386' OBJC='/usr/bin/gcc-4.0' FCFLAGS='-O2' INSTALL='/usr/bin/install' OBJCFLAGS='-O2' FFLAGS='-O2' CC='/usr/bin/gcc-4.0' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutil s_MacPorts/work/MacPorts-1.6.0" && ./configure --prefix=/opt/local -- enable-readline' configure: error: cannot run /bin/sh ./config.sub Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutil s_MacPorts/work/MacPorts-1.6.0" && ./configure --prefix=/opt/local -- enable-readline " returned error 1 Command output: configure: error: cannot run /bin/sh ./config.sub Warning: the following items did not execute (for MacPorts): org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. $ From paulbeard at gmail.com Thu Jan 3 16:42:10 2008 From: paulbeard at gmail.com (paul beard) Date: Thu Jan 3 16:40:10 2008 Subject: Standardizing a MacPorts system In-Reply-To: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> References: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> Message-ID: On Jan 3, 2008 12:17 PM, Tabitha McNerney wrote: > Hello all -- > > I would like to build, from source, on an Xserve running Leopard Server, a > "standard" MacPorts system that could be deployed, in an organization, on > numerous other Apple servers running the same version of the OS ( e.g. > Leopard Server). In doing so I would use Apple's command-line tools (such as > hdiutil and asr) create a restorable disk image (.dmg) file of a disc volume > that hangs off an external disk on my original Xserve which houses the > MacPorts prefix ( e.g., /opt/local). I would then restore from this disc > image to the additional machines slated to be the recipients of the original > standard. > I wonder if some combination of nfs (to mount your master repository), rsync (to update your local store) and some voodoo with a regex to update any files that are tied to hostnames (all your master builds might be tagged with "master" or "changeme"). > > I don't see any immediate problems in doing so, however I have noticed > when installing some ports (when I have occasionally enabled verbose mode > "-v" during the install), depending on the port, some ports seem to take > into consideration the Hostname of the Xserve I'm running it on. On my > Xserve running Leopard Server, the Hostname is very importantly tied to the > DNS name because I am running Apple's DNS server that is buncled with > Leopard Server since I need it for other services on the machine which are > not directly related to MacPorts such as running an OpenDirectory Master. > The problem is, with hundreds of MacPorts tied together and with complex > dependency chains, how can anyone determine when a specific MacPort reads > the hostname and uses the hostname of the machine during the configuration > process (unless a sys admin such as myself builds each and every port with > verbose mode and analysis the output grepping for the hostname)? It might be > problematic if the hostname of any given MacPort somehow becomes "hard > wired" into the port itself during the configuration / install processing. > Then again, I might be making a mountain out of a mole hill. > > Has anyone else built a Standardized MacPorts system that is cloned to > multiple Macs? > > Thanks, > > T.M. > > > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > > -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/d866def1/attachment.html From tabithamc at gmail.com Thu Jan 3 17:15:49 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Thu Jan 3 17:13:50 2008 Subject: Standardizing a MacPorts system In-Reply-To: References: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> Message-ID: <7fccb3000801031715r8993d73ocf8f0887a4d518db@mail.gmail.com> On 1/3/08, paul beard wrote: > > > > On Jan 3, 2008 12:17 PM, Tabitha McNerney wrote: > > > Hello all -- > > > > I would like to build, from source, on an Xserve running Leopard Server, > > a "standard" MacPorts system that could be deployed, in an organization, on > > numerous other Apple servers running the same version of the OS ( e.g. > > Leopard Server). In doing so I would use Apple's command-line tools (such as > > hdiutil and asr) create a restorable disk image (.dmg) file of a disc volume > > that hangs off an external disk on my original Xserve which houses the > > MacPorts prefix ( e.g., /opt/local). I would then restore from this disc > > image to the additional machines slated to be the recipients of the original > > standard. > > > > I wonder if some combination of nfs (to mount your master repository), > rsync (to update your local store) and some voodoo with a regex to update > any files that are tied to hostnames (all your master builds might be tagged > with "master" or "changeme"). > Paul, Appreciate the directional suggestion! Probably I could live without NFS and rsync, as I'd probably be ok with with cloning a master courtesy of the diskutil, hdiutil and asr tools on OS X. The regex is probably the way to go! Thanks, T.M. [SNIP] -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/0010f133/attachment-0001.html From ryandesign at macports.org Thu Jan 3 18:17:26 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 3 18:15:55 2008 Subject: sudo port upgrade outdated > PortUpgradeOutdated.log In-Reply-To: <9345764E-E5AA-4069-A4E9-0568B9E84C89@gmail.com> References: <9345764E-E5AA-4069-A4E9-0568B9E84C89@gmail.com> Message-ID: On Jan 3, 2008, at 14:18, Charlse Darwin wrote: > How do I get the port to write the output to a log file? `$ sudo > port upgrade outdated > PortUpgradeOutdated.log' didn't fly well. In what way didn't it fly? From macports.users at gmail.com Thu Jan 3 18:21:47 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Thu Jan 3 18:19:51 2008 Subject: sudo port upgrade outdated > PortUpgradeOutdated.log In-Reply-To: References: <9345764E-E5AA-4069-A4E9-0568B9E84C89@gmail.com> Message-ID: <98E0BEEE-F7F1-4000-823C-2E4B33BCE038@gmail.com> A non-text attachment was scrubbed... Name: PortUpgradeInstalled.log Type: application/octet-stream Size: 12284 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/c977e583/PortUpgradeInstalled.obj -------------- next part -------------- It didn't log the whole thing? On Jan 3, 2008, at 9:17 PM, Ryan Schmidt wrote: > > On Jan 3, 2008, at 14:18, Charlse Darwin wrote: > >> How do I get the port to write the output to a log file? `$ sudo >> port upgrade outdated > PortUpgradeOutdated.log' didn't fly well. > > In what way didn't it fly? > > From ryandesign at macports.org Thu Jan 3 18:22:45 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 3 18:21:15 2008 Subject: Standardizing a MacPorts system In-Reply-To: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> References: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> Message-ID: On Jan 3, 2008, at 14:17, Tabitha McNerney wrote: > I would like to build, from source, on an Xserve running Leopard > Server, a "standard" MacPorts system that could be deployed, in an > organization, on numerous other Apple servers running the same > version of the OS ( e.g. Leopard Server). In doing so I would use > Apple's command-line tools (such as hdiutil and asr) create a > restorable disk image (.dmg) file of a disc volume that hangs off > an external disk on my original Xserve which houses the MacPorts > prefix ( e.g., /opt/local). I would then restore from this disc > image to the additional machines slated to be the recipients of the > original standard. > > I don't see any immediate problems in doing so, however I have > noticed when installing some ports (when I have occasionally > enabled verbose mode "-v" during the install), depending on the > port, some ports seem to take into consideration the Hostname of > the Xserve I'm running it on. On my Xserve running Leopard Server, > the Hostname is very importantly tied to the DNS name because I am > running Apple's DNS server that is buncled with Leopard Server > since I need it for other services on the machine which are not > directly related to MacPorts such as running an OpenDirectory > Master. The problem is, with hundreds of MacPorts tied together and > with complex dependency chains, how can anyone determine when a > specific MacPort reads the hostname and uses the hostname of the > machine during the configuration process (unless a sys admin such > as myself builds each and every port with verbose mode and analysis > the output grepping for the hostname)? It might be problematic if > the hostname of any given MacPort somehow becomes "hard wired" into > the port itself during the configuration / install processing. Then > again, I might be making a mountain out of a mole hill. > > Has anyone else built a Standardized MacPorts system that is cloned > to multiple Macs? I wasn't aware that any ports tied themselves to the build system's hostname. That would be problematic as well if we started to distribute binaries of ports. Then again, I'm only familiar with a small minority of our ports collection. With which ports have you observed this problem? From ryandesign at macports.org Thu Jan 3 18:27:43 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 3 18:26:12 2008 Subject: sudo port upgrade outdated > PortUpgradeOutdated.log In-Reply-To: <98E0BEEE-F7F1-4000-823C-2E4B33BCE038@gmail.com> References: <9345764E-E5AA-4069-A4E9-0568B9E84C89@gmail.com> <98E0BEEE-F7F1-4000-823C-2E4B33BCE038@gmail.com> Message-ID: <452C8D2C-3242-4CAB-9CC4-5BF087855AD1@macports.org> On Jan 3, 2008, at 20:21, Charlse Darwin wrote: > On Jan 3, 2008, at 9:17 PM, Ryan Schmidt wrote: > >> On Jan 3, 2008, at 14:18, Charlse Darwin wrote: >> >>> How do I get the port to write the output to a log file? `$ sudo >>> port upgrade outdated > PortUpgradeOutdated.log' didn't fly well. >> >> In what way didn't it fly? > > > > It didn't log the whole thing? I can't quite tell, looking at that, what's missing. Perhaps you're wanting to capture text from stderr as well as stdout? If so, try: $ sudo port upgrade outdated &> PortUpgradeOutdated.log From ryandesign at macports.org Thu Jan 3 18:28:57 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 3 18:27:27 2008 Subject: Install fails In-Reply-To: <3442B39B-8364-4C0C-AD93-7009A068FCE1@vilot.com> References: <3442B39B-8364-4C0C-AD93-7009A068FCE1@vilot.com> Message-ID: <0EC7E7AF-036A-436F-9A52-A0FDA361E10E@macports.org> On Jan 3, 2008, at 10:31, Tom Vilot wrote: > I tried the disk image and received an error: > > The following install step failed: run preflight script. > > I tried from source, and got: > > ===> making all in src/registry2.0 > cc -dynamiclib -L/usr/local/lib registry.o util.o entry.o > entryobj.o -o registry.dylib -L/System/Library/Frameworks/ > Tcl.framework/Versions/8.4 -ltclstub8.4 -L/usr/local/lib ../ > cregistry/cregistry.a -lsqlite3 > ld: in ../cregistry/cregistry.a, archive has no table of contents > collect2: ld returned 1 exit status > make[2]: *** [registry.dylib] Error 1 > make[1]: *** [all] Error 1 > make: *** [all] Error 1 What OS version do you have? What version of Xcode do you have? What version of MacPorts are you trying to install? What model of Mac do you have? From macports.users at gmail.com Thu Jan 3 18:35:32 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Thu Jan 3 18:33:37 2008 Subject: sudo port upgrade outdated > PortUpgradeOutdated.log In-Reply-To: <452C8D2C-3242-4CAB-9CC4-5BF087855AD1@macports.org> References: <9345764E-E5AA-4069-A4E9-0568B9E84C89@gmail.com> <98E0BEEE-F7F1-4000-823C-2E4B33BCE038@gmail.com> <452C8D2C-3242-4CAB-9CC4-5BF087855AD1@macports.org> Message-ID: It works! Thanks. I have a daemon to upgrade my ports, set for after midnight. Now I can have a log of what's happened the morning after. On Jan 3, 2008, at 9:27 PM, Ryan Schmidt wrote: > On Jan 3, 2008, at 20:21, Charlse Darwin wrote: > >> On Jan 3, 2008, at 9:17 PM, Ryan Schmidt wrote: >> >>> On Jan 3, 2008, at 14:18, Charlse Darwin wrote: >>> >>>> How do I get the port to write the output to a log file? `$ sudo >>>> port upgrade outdated > PortUpgradeOutdated.log' didn't fly well. >>> >>> In what way didn't it fly? >> >> >> >> It didn't log the whole thing? > > > I can't quite tell, looking at that, what's missing. Perhaps you're > wanting to capture text from stderr as well as stdout? If so, try: > > $ sudo port upgrade outdated &> PortUpgradeOutdated.log > From ryandesign at macports.org Thu Jan 3 18:41:26 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 3 18:39:54 2008 Subject: Install fails In-Reply-To: References: <3442B39B-8364-4C0C-AD93-7009A068FCE1@vilot.com> <0EC7E7AF-036A-436F-9A52-A0FDA361E10E@macports.org> Message-ID: On Jan 3, 2008, at 20:37, Tom Vilot wrote: > Ryan Schmidt wrote: > >> What OS version do you have? What version of Xcode do you have? >> What version of MacPorts are you trying to install? What model of >> Mac do you have? > > Thanks, Ryan, for your reply. > > Sorry, that was very absent minded of me: > > Leopard, 10.5.1. > Xcode is the latest, I believe. just downloaded it. 3.0 > MacPorts version 1.6.0 > MacBook Pro. Ok. I know we had some problems building under Panther, but that's not it then. I'm sending this back to the list so someone with Leopard can look at it. From ryandesign at macports.org Thu Jan 3 19:12:56 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 3 19:11:26 2008 Subject: $ sudo port -f install MacPorts In-Reply-To: <76AEA96B-0DD7-41DC-919E-A498DF38B3C4@gmail.com> References: <76AEA96B-0DD7-41DC-919E-A498DF38B3C4@gmail.com> Message-ID: <0A5C870E-2B27-4AE6-B88D-23DF09A84AC3@macports.org> Out of curiosity, why do you want to install the MacPorts port? On Jan 3, 2008, at 16:32, Charlse Darwin wrote: > $ sudo port -f install MacPorts > Portfile changed since last build; discarding previous state. > ---> Fetching MacPorts > ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// > svn.macports.org/repository/macports/distfiles/MacPorts-1.6.0 > ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// > svn.macports.org/repository/macports/distfiles/general/MacPorts-1.6.0 > ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// > svn.macports.org/repository/macports/downloads/MacPorts-1.6.0 > ---> Verifying checksum(s) for MacPorts > ---> Extracting MacPorts > ---> Configuring MacPorts > Fixing your MacOSX10.4u installation by copying libtclstub8.4.a to / > Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/ > Tcl.framework/Versions/8.4/libtclstub8.4.a > Error: Target org.macports.configure returned: configure failure: > shell command " cd "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_sysut > ils_MacPorts/work/MacPorts-1.6.0" && ./configure --prefix=/opt/ > local --enable-readline " returned error 1 > Command output: configure: error: cannot run /bin/sh ./config.sub > > Error: Status 1 encountered during processing. > $ From paulbeard at gmail.com Thu Jan 3 20:13:50 2008 From: paulbeard at gmail.com (paul beard) Date: Thu Jan 3 20:11:49 2008 Subject: Standardizing a MacPorts system In-Reply-To: References: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> Message-ID: On Jan 3, 2008 6:22 PM, Ryan Schmidt wrote: > > > I wasn't aware that any ports tied themselves to the build system's > hostname. That would be problematic as well if we started to > distribute binaries of ports. Then again, I'm only familiar with a > small minority of our ports collection. > > With which ports have you observed this problem? > > Aren't you the maintainer of the mysql port? [/opt/local/var/db/mysql5]# ls .turd_mysql5 ibdata1 test ib_logfile0 localhost.err white.paulbeard.org.err ib_logfile1 mysql There may well be others but this one came to mind immediately. -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/1a134b17/attachment.html From ryandesign at macports.org Thu Jan 3 20:18:01 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 3 20:16:29 2008 Subject: $ sudo port -f install MacPorts In-Reply-To: <3977330F-ED37-481E-94FA-4486F85A7626@gmail.com> References: <76AEA96B-0DD7-41DC-919E-A498DF38B3C4@gmail.com> <0A5C870E-2B27-4AE6-B88D-23DF09A84AC3@macports.org> <3977330F-ED37-481E-94FA-4486F85A7626@gmail.com> Message-ID: <9559D3F5-439C-4EF4-BF97-5E55C8AC902B@macports.org> On Jan 3, 2008, at 22:11, Charlse Darwin wrote: > On Jan 3, 2008, at 10:12 PM, Ryan Schmidt wrote: > >> On Jan 3, 2008, at 16:32, Charlse Darwin wrote: >> >>> $ sudo port -f install MacPorts >>> Portfile changed since last build; discarding previous state. >>> ---> Fetching MacPorts >>> ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// >>> svn.macports.org/repository/macports/distfiles/MacPorts-1.6.0 >>> ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// >>> svn.macports.org/repository/macports/distfiles/general/ >>> MacPorts-1.6.0 >>> ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// >>> svn.macports.org/repository/macports/downloads/MacPorts-1.6.0 >>> ---> Verifying checksum(s) for MacPorts >>> ---> Extracting MacPorts >>> ---> Configuring MacPorts >>> Fixing your MacOSX10.4u installation by copying libtclstub8.4.a >>> to /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/ >>> Tcl.framework/Versions/8.4/libtclstub8.4.a >>> Error: Target org.macports.configure returned: configure failure: >>> shell command " cd "/opt/local/var/macports/build/ >>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_sys >>> utils_MacPorts/work/MacPorts-1.6.0" && ./configure --prefix=/opt/ >>> local --enable-readline " returned error 1 >>> Command output: configure: error: cannot run /bin/sh ./config.sub >>> >>> Error: Status 1 encountered during processing. >>> $ >> >> Out of curiosity, why do you want to install the MacPorts port? > > `Command output: configure: error: cannot run /bin/sh ./config.sub' > shows up in every port that I'm trying to install, I just though > reinstalling MacPorts might help. Oh, I didn't realize that. Well that certainly shouldn't be. Reinstalling MacPorts might help. But I don't think installing the port called MacPorts is the way to do that. At least, that's not documented anywhere. From ryandesign at macports.org Thu Jan 3 20:21:56 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 3 20:20:25 2008 Subject: Standardizing a MacPorts system In-Reply-To: References: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> Message-ID: <1B701D57-44E5-49B5-81A2-E5252F10E07E@macports.org> On Jan 3, 2008, at 22:13, paul beard wrote: > On Jan 3, 2008 6:22 PM, Ryan Schmidt wrote: > >> I wasn't aware that any ports tied themselves to the build system's >> hostname. That would be problematic as well if we started to >> distribute binaries of ports. Then again, I'm only familiar with a >> small minority of our ports collection. >> >> With which ports have you observed this problem? > > Aren't you the maintainer of the mysql port? Yes I am. > [/opt/local/var/db/mysql5]# ls > .turd_mysql5 ibdata1 test > ib_logfile0 localhost.err > white.paulbeard.org.err > ib_logfile1 mysql > > There may well be others but this one came to mind immediately. MySQL writes logfiles whose names contain the hostname, yes. The hostname is not, however, to the best of my knowledge, encoded into any files installed by the MySQL ports. There should be no problem installing MySQL on one system and running it on another. The two systems will merely use separate logfiles by default -- which is in fact probably a good thing, isn't it? If it isn't, there's probably a way to have MySQL write to a logfile of a name of your choosing. Consult the MySQL documentation. From macports.users at gmail.com Thu Jan 3 20:27:18 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Thu Jan 3 20:25:20 2008 Subject: $ sudo port -f install MacPorts In-Reply-To: <0A5C870E-2B27-4AE6-B88D-23DF09A84AC3@macports.org> References: <76AEA96B-0DD7-41DC-919E-A498DF38B3C4@gmail.com> <0A5C870E-2B27-4AE6-B88D-23DF09A84AC3@macports.org> Message-ID: <6BF594DE-4B6A-475C-90D4-F47D7395C3F1@gmail.com> `Command output: configure: error: cannot run /bin/sh ./config.sub' shows up in every port that I'm trying to install, I just though reinstalling MacPorts might help. On Jan 3, 2008, at 10:12 PM, Ryan Schmidt wrote: > Out of curiosity, why do you want to install the MacPorts port? > > > On Jan 3, 2008, at 16:32, Charlse Darwin wrote: > >> $ sudo port -f install MacPorts >> Portfile changed since last build; discarding previous state. >> ---> Fetching MacPorts >> ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// >> svn.macports.org/repository/macports/distfiles/MacPorts-1.6.0 >> ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// >> svn.macports.org/repository/macports/distfiles/general/MacPorts-1.6.0 >> ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// >> svn.macports.org/repository/macports/downloads/MacPorts-1.6.0 >> ---> Verifying checksum(s) for MacPorts >> ---> Extracting MacPorts >> ---> Configuring MacPorts >> Fixing your MacOSX10.4u installation by copying libtclstub8.4.a >> to /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/ >> Tcl.framework/Versions/8.4/libtclstub8.4.a >> Error: Target org.macports.configure returned: configure failure: >> shell command " cd "/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_sysu >> tils_MacPorts/work/MacPorts-1.6.0" && ./configure --prefix=/opt/ >> local --enable-readline " returned error 1 >> Command output: configure: error: cannot run /bin/sh ./config.sub >> >> Error: Status 1 encountered during processing. >> $ > From paulbeard at gmail.com Thu Jan 3 20:35:06 2008 From: paulbeard at gmail.com (paul beard) Date: Thu Jan 3 20:33:06 2008 Subject: Standardizing a MacPorts system In-Reply-To: <1B701D57-44E5-49B5-81A2-E5252F10E07E@macports.org> References: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> <1B701D57-44E5-49B5-81A2-E5252F10E07E@macports.org> Message-ID: On Jan 3, 2008 8:21 PM, Ryan Schmidt wrote: > On Jan 3, 2008, at 22:13, paul beard wrote: > > > On Jan 3, 2008 6:22 PM, Ryan Schmidt wrote: > > > >> I wasn't aware that any ports tied themselves to the build system's > >> hostname. That would be problematic as well if we started to > >> distribute binaries of ports. Then again, I'm only familiar with a > >> small minority of our ports collection. > >> > >> With which ports have you observed this problem? > > > > Aren't you the maintainer of the mysql port? > > Yes I am. > > > [/opt/local/var/db/mysql5]# ls > > .turd_mysql5 ibdata1 test > > ib_logfile0 localhost.err > > white.paulbeard.org.err > > ib_logfile1 mysql > > > > There may well be others but this one came to mind immediately. > > MySQL writes logfiles whose names contain the hostname, yes. The > hostname is not, however, to the best of my knowledge, encoded into > any files installed by the MySQL ports. There should be no problem > installing MySQL on one system and running it on another. The two > systems will merely use separate logfiles by default -- which is in > fact probably a good thing, isn't it? If it isn't, there's probably a > way to have MySQL write to a logfile of a name of your choosing. > Consult the MySQL documentation. > > I'm not that interested in a solution to a problem I don't have. But the inferred question was, do any ports make use of the hostname. it looks like mysql derives it when it creates the file (I tested it). I'm not sure this one admittedly thin example answers the OP's question. -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/4b587e9a/attachment-0001.html From wsiegrist at apple.com Thu Jan 3 20:36:35 2008 From: wsiegrist at apple.com (William Siegrist) Date: Thu Jan 3 20:35:35 2008 Subject: Standardizing a MacPorts system In-Reply-To: <1B701D57-44E5-49B5-81A2-E5252F10E07E@macports.org> References: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> <1B701D57-44E5-49B5-81A2-E5252F10E07E@macports.org> Message-ID: The use of the hostname for MySQL's error log is coded into mysql itself: http://dev.mysql.com/doc/refman/5.0/en/error-log.html Even if you had .err left over on the other "cloned" hosts, it shouldnt be a problem, since a .err will be made and used. And that same link shows the line to put in etc/my.cnf to make it standard anyway. FWIW, Mac OS Forge uses 1 installation of MacPorts for many XServes, and we dont have problems. I'd really be interested to know which ports are hostname-dependent. -Bill On Jan 3, 2008, at 8:21 PM, Ryan Schmidt wrote: > On Jan 3, 2008, at 22:13, paul beard wrote: > >> On Jan 3, 2008 6:22 PM, Ryan Schmidt wrote: >> >>> I wasn't aware that any ports tied themselves to the build system's >>> hostname. That would be problematic as well if we started to >>> distribute binaries of ports. Then again, I'm only familiar with a >>> small minority of our ports collection. >>> >>> With which ports have you observed this problem? >> >> Aren't you the maintainer of the mysql port? > > Yes I am. > >> [/opt/local/var/db/mysql5]# ls >> .turd_mysql5 ibdata1 test >> ib_logfile0 localhost.err >> white.paulbeard.org.err >> ib_logfile1 mysql >> >> There may well be others but this one came to mind immediately. > > MySQL writes logfiles whose names contain the hostname, yes. The > hostname is not, however, to the best of my knowledge, encoded into > any files installed by the MySQL ports. There should be no problem > installing MySQL on one system and running it on another. The two > systems will merely use separate logfiles by default -- which is in > fact probably a good thing, isn't it? If it isn't, there's probably > a way to have MySQL write to a logfile of a name of your choosing. > Consult the MySQL documentation. > > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users ---- William Siegrist Software Support Engineer Mac OS Forge http://macosforge.org/ wsiegrist@apple.com 408 862 7337 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2421 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/6d3d7c8e/smime.bin From ryandesign at macports.org Thu Jan 3 20:41:25 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 3 20:55:42 2008 Subject: $ sudo port -f install MacPorts In-Reply-To: <7606F127-A982-457C-BA6B-20BD5EB8D46D@gmail.com> References: <76AEA96B-0DD7-41DC-919E-A498DF38B3C4@gmail.com> <0A5C870E-2B27-4AE6-B88D-23DF09A84AC3@macports.org> <3977330F-ED37-481E-94FA-4486F85A7626@gmail.com> <9559D3F5-439C-4EF4-BF97-5E55C8AC902B@macports.org> <7606F127-A982-457C-BA6B-20BD5EB8D46D@gmail.com> Message-ID: <92E070E3-B773-45FA-9465-054BF5CB0825@macports.org> On Jan 3, 2008, at 22:26, Charlse Darwin wrote: > On Jan 3, 2008, at 11:18 PM, Ryan Schmidt wrote: > >> On Jan 3, 2008, at 22:11, Charlse Darwin wrote: >> >>> On Jan 3, 2008, at 10:12 PM, Ryan Schmidt wrote: >>> >>>> On Jan 3, 2008, at 16:32, Charlse Darwin wrote: >>>> >>>>> $ sudo port -f install MacPorts >>>>> Portfile changed since last build; discarding previous state. >>>>> ---> Fetching MacPorts >>>>> ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// >>>>> svn.macports.org/repository/macports/distfiles/MacPorts-1.6.0 >>>>> ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// >>>>> svn.macports.org/repository/macports/distfiles/general/ >>>>> MacPorts-1.6.0 >>>>> ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// >>>>> svn.macports.org/repository/macports/downloads/MacPorts-1.6.0 >>>>> ---> Verifying checksum(s) for MacPorts >>>>> ---> Extracting MacPorts >>>>> ---> Configuring MacPorts >>>>> Fixing your MacOSX10.4u installation by copying libtclstub8.4.a >>>>> to /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/ >>>>> Tcl.framework/Versions/8.4/libtclstub8.4.a >>>>> Error: Target org.macports.configure returned: configure >>>>> failure: shell command " cd "/opt/local/var/macports/build/ >>>>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_s >>>>> ysutils_MacPorts/work/MacPorts-1.6.0" && ./configure --prefix=/ >>>>> opt/local --enable-readline " returned error 1 >>>>> Command output: configure: error: cannot run /bin/sh ./config.sub >>>>> >>>>> Error: Status 1 encountered during processing. >>>>> $ >>>> >>>> Out of curiosity, why do you want to install the MacPorts port? >>> >>> `Command output: configure: error: cannot run /bin/sh ./ >>> config.sub' shows up in every port that I'm trying to install, I >>> just though reinstalling MacPorts might help. >> >> Oh, I didn't realize that. Well that certainly shouldn't be. >> >> Reinstalling MacPorts might help. But I don't think installing the >> port called MacPorts is the way to do that. At least, that's not >> documented anywhere. > > It all happened after I started playing with xnu (darwin_9, uname - > r on my machine returns 8.11.0) > I have tried installing MacPorts from this package > http://svn.macports.org/repository/macports/downloads/ > MacPorts-1.6.0/MacPorts-1.6.0-10.4-Tiger.dmg > > but it failed. I'm thinking maybe I should reinstalling the Xcode too? XNU is the Mac OS X kernel, yes? What do you mean, playing with it? You are running Tiger? If so, what did you mean when you said "darwin_9"? In what way did installing MacPorts 1.6.0 from the Tiger disk image fail? If you're on Tiger, reinstalling Xcode 2.5 couldn't hurt. From lisfolks.lists at gmail.com Thu Jan 3 21:10:28 2008 From: lisfolks.lists at gmail.com (LeAnne Lis) Date: Thu Jan 3 21:08:29 2008 Subject: Error building p5-sdl_perl Message-ID: <14610995.post@talk.nabble.com> A search for the p5-sdl_perl port brings up a ticket from Dec 30, #13757: frozenbubble2 doesn't build on leopard. However, it's been closed as a duplicate. If it truly is a duplicate, then of what? And, how do I fix this? Here's the error I get: ---> Fetching p5-sdl_perl ---> Verifying checksum(s) for p5-sdl_perl ---> Extracting p5-sdl_perl ---> Applying patches to p5-sdl_perl ---> Configuring p5-sdl_perl ---> Building p5-sdl_perl with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_perl_p5-sdl_perl/work/SDL_Perl-2.1.3" && /opt/local/bin/perl Build build " returned error 2 Command output: Copying lib/SDL/Video.pm -> blib/lib/SDL/Video.pm Copying lib/SDL/Event.pm -> blib/lib/SDL/Event.pm Copying lib/SDL/Tutorial.pm -> blib/lib/SDL/Tutorial.pm Copying lib/SDL/Sound.pm -> blib/lib/SDL/Sound.pm Copying lib/SDL/Mixer.pm -> blib/lib/SDL/Mixer.pm Copying lib/SDL/OpenGL.pm -> blib/lib/SDL/OpenGL.pm Copying lib/SDL.pm -> blib/lib/SDL.pm Copying lib/SDL/Timer.pm -> blib/lib/SDL/Timer.pm Copying lib/SDL/Font.pm -> blib/lib/SDL/Font.pm Copying lib/SDL/Music.pm -> blib/lib/SDL/Music.pm Copying lib/SDL/OpenGL/Constants.pm -> blib/lib/SDL/OpenGL/Constants.pm Copying lib/SDL/Color.pm -> blib/lib/SDL/Color.pm Copying lib/SDL/Config.pm -> blib/lib/SDL/Config.pm Copying lib/SDL/Tool/Font.pm -> blib/lib/SDL/Tool/Font.pm Copying lib/SDL_perl.pm -> blib/lib/SDL_perl.pm Copying lib/SDL/Cdrom.pm -> blib/lib/SDL/Cdrom.pm Copying lib/SDL/Tutorial/Images.pm -> blib/lib/SDL/Tutorial/Images.pm Copying lib/SDL/App.pm -> blib/lib/SDL/App.pm Copying lib/SDL/TTFont.pm -> blib/lib/SDL/TTFont.pm Copying lib/SDL/Constants.pm -> blib/lib/SDL/Constants.pm Copying src/SDL.xs -> src/SDL_perl.xs src/SDL_perl.xs -> src/SDL_perl.c cc -I/opt/local/lib/perl5/5.8.8/darwin-2level/CORE -DXS_VERSION="2.1.3" -DVERSION="2.1.3" -I/Library/Frameworks/SDL_mixer.framework/Headers -I/Library/Frameworks/SDL_gfx.framework/Headers -I/Library/Frameworks/SDL.framework/Headers -I/Library/Frameworks/SDL_image.framework/Headers -I/Library/Frameworks/SDL_net.framework/Headers -I/Library/Frameworks/SDL_ttf.framework/Headers -I/opt/local/include/SDL -D_GNU_SOURCE=1 -D_THREAD_SAFE -DHAVE_SDL -DHAVE_SDL_TTF -DHAVE_SDL_NET -DHAVE_SDL_IMAGE -DHAVE_SDL_GFX -DHAVE_SDL_MIXER -Ddarwin -DMACOSX -fPIC -c -I/opt/local/include -fno-common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/opt/local/include -O3 -o src/SDL_perl.o src/SDL_perl.c src/SDL_perl.xs: In function 'XS_SDL_NetResolveIP': src/SDL_perl.xs:2471: warning: assignment discards qualifiers from pointer target type ExtUtils::Mkbootstrap::Mkbootstrap('blib/arch/auto/src/SDL_perl/SDL_perl.bs') env MACOSX_DEPLOYMENT_TARGET=10.3 cc -L/opt/local/lib -bundle -undefined dynamic_lookup -o blib/arch/auto/src/SDL_perl/SDL_perl.bundle src/SDL_perl.o -L../../lib -L/opt/local/lib -lSDLmain -lSDL -Wl,-framework,Cocoa -lSDL -lSDL_ttf -lSDL_net -lSDL_image -lSDL_gfx -lSDL_mixer ld: library not found for -lSDL_ttf collect2: ld returned 1 exit status error building blib/arch/auto/src/SDL_perl/SDL_perl.bundle from src/SDL_perl.o at /opt/local/lib/perl5/vendor_perl/5.8.8/ExtUtils/CBuilder/Base.pm line 213. Error: The following dependencies failed to build: p5-sdl_perl Error: Status 1 encountered during processing. -- View this message in context: http://www.nabble.com/Error-building-p5-sdl_perl-tp14610995p14610995.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From boeyms at macports.org Thu Jan 3 22:32:15 2008 From: boeyms at macports.org (Boey Maun Suang) Date: Thu Jan 3 22:30:15 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> Message-ID: <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> Hi Chris and js (and anybody else who wants to help squash this apparent Panther bug), Thanks for your kind offers to help with reproducing the bug that I was getting on Panther. In order to reproduce it, you'll need to apply a couple of patches to the MacPorts 1.6.0 source, then build and install from that source. If you want to remove it at any stage, just erasing the /opt/local directory should be fine, as the bug that I'd like reproduced prevents the installation of ports. The steps to take appear below (apologies if they are more detailed that you need); steps 1, 4, 5 and 7 are the same as the normal steps for installing MacPorts from source [1]. 1. Download the MacPorts 1.6.0 source tarball [2]. 2. Download changesets 32105 [3] and 32212 [4]; they should save with the respective filenames of changeset_r32105.diff and changeset_r32212.diff. If your browser shows the text of those changesets instead of saving them as files (Safari 3 does so for me), use your "Save As..." or equivalent function from the File menu to save them with the above filenames. 3. Place all three files into the same directory (wherever you'll be happy to extract the source tarball). 4. Extract the MacPorts 1.6.0 source tarball at the command line by changing to the directory containing the tarball, then running tar -xjf MacPorts-1.6.0.tar.bz2 5. Change into the MacPorts-1.6.0 directory ("cd MacPorts-1.6.0") containing the extracted MacPorts source. 6. Patch the extracted source by running patch -p3 < ../changeset_r32105.diff ; patch -p3 < ../changeset_r32212.diff If patch reports that either of these steps failed (it will say "FAILED" in capital letters), stop and let me know as the following steps won't work. 7. Run "./configure", "make" and "sudo make install" as normal [1]. 8. If you haven't set your shell variables, do so at this point. If you use bash, follow the guide [5]. If you use tcsh (which I believe is the default on Panther), then running setenv PATH /opt/local/bin:/opt/local/sbin:$(PATH) at the command line should be sufficient. 9. Run "sudo port selfupdate" as normal [6]. 10. At the command line, you should now find that, when run on any portname (e.g. xmlcatmgr) the "port info " and "port install " commands fail with Error: Unable to open port: invalid command name "ui_channels" However, you should find that "port search " works fine. (In general, it appears to me that the port commands that fail with the above message are the ones for which the "port" command attempts to open a Portfile.) Thank you once again for offering to help; I hope that your help will enable us to get MacPorts 1.6.0 working on Panther very soon! Please feel free to ask me any other questions you may have in this regard. Kind regards, Maun Suang [1] http://guide.macports.org/#installing.source [2] http://svn.macports.org/repository/macports/downloads/MacPorts-1.6.0/MacPorts-1.6.0.tar.bz2 [3] http://trac.macports.org/projects/macports/changeset/32105?format=diff&new=32105 [4] http://trac.macports.org/projects/macports/changeset/32212?format=diff&new=32212 [5] http://guide.macports.org/#installing.shell [6] http://guide.macports.org/#installing.selfupdate -- Boey Maun Suang Email: boeyms@macports.org From guido.soranzio at gmail.com Thu Jan 3 23:29:48 2008 From: guido.soranzio at gmail.com (Guido Soranzio) Date: Thu Jan 3 23:27:52 2008 Subject: problem using port to install gnucash on mac 10.5 In-Reply-To: <9153cb050801031441x599afb40leb0207a0eb8c63bc@mail.gmail.com> References: <9153cb050801031441x599afb40leb0207a0eb8c63bc@mail.gmail.com> Message-ID: <739B163F-8E4E-4B27-8CDE-0AC771BAFF3C@gmail.com> On Jan 3, 2008, at 11:41 PM, Some Guy wrote: > i have re-installed those items but still get the problem with avahi > > checking for /opt/local/bin/python2.5 extension module directory... $ > {exec_prefix}/lib/python2.5/site-packages > checking for python module gtk... yes > checking for python module dbus... no > configure: error: Could not find Python module dbus I have suggested a similar workaround for dbus-python25 but it has not yet been committed to the MacPorts's Trac repository: . Keep in mind, however, that gnome is currently unmaintained and that dbus, gconf and the entire help system are not working correctly. Regards, Guido From ryandesign at macports.org Thu Jan 3 22:16:18 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 3 23:58:48 2008 Subject: Error building p5-sdl_perl In-Reply-To: <14610995.post@talk.nabble.com> References: <14610995.post@talk.nabble.com> Message-ID: On Jan 3, 2008, at 23:10, LeAnne Lis wrote: > A search for the p5-sdl_perl port brings up a ticket from Dec 30, > #13757: > frozenbubble2 doesn't build on leopard. However, it's been closed > as a > duplicate. If it truly is a duplicate, then of what? The note in the ticket says it is a duplicate of #13724. > And, how do I fix this? I do not know. Hopefully the maintainer of the port can figure it out. The ticket is assigned to him so he should be aware of it. The port is openmaintainer, so anyone else is welcome to step in and provide a solution if one is known. From tabithamc at gmail.com Fri Jan 4 01:01:53 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Fri Jan 4 00:59:55 2008 Subject: Standardizing a MacPorts system In-Reply-To: References: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> <1B701D57-44E5-49B5-81A2-E5252F10E07E@macports.org> Message-ID: <7fccb3000801040101hdaf3cf2x473068ff002c89ba@mail.gmail.com> On 1/3/08, William Siegrist wrote: > > The use of the hostname for MySQL's error log is coded into mysql > itself: > > http://dev.mysql.com/doc/refman/5.0/en/error-log.html > > Even if you had .err left over on the other "cloned" > hosts, it shouldnt be a problem, since a .err will be made > and used. And that same link shows the line to put in etc/my.cnf to > make it standard anyway. > > FWIW, Mac OS Forge uses 1 installation of MacPorts for many XServes, > and we dont have problems. I'd really be interested to know which > ports are hostname-dependent. With apologies, I didn't at the time (when I was installing some of my ports with the verbos option) make a note -- it was more of an afterthought, but in the verbose output of one my 180+ ports I made the past few days, I did see the hostname show up in the verbose output which made me wonder if this could be a problem such as if some ports were made which would depend on in some way the hostname. It may be that there is no problem at all. I'm glad to learn that Mac OS Forge has successfully cloned and implemented MacPorts systems for use with multiple machines. Thanks, T.M. -Bill > > > > On Jan 3, 2008, at 8:21 PM, Ryan Schmidt wrote: > > > On Jan 3, 2008, at 22:13, paul beard wrote: > > > >> On Jan 3, 2008 6:22 PM, Ryan Schmidt wrote: > >> > >>> I wasn't aware that any ports tied themselves to the build system's > >>> hostname. That would be problematic as well if we started to > >>> distribute binaries of ports. Then again, I'm only familiar with a > >>> small minority of our ports collection. > >>> > >>> With which ports have you observed this problem? > >> > >> Aren't you the maintainer of the mysql port? > > > > Yes I am. > > > >> [/opt/local/var/db/mysql5]# ls > >> .turd_mysql5 ibdata1 test > >> ib_logfile0 localhost.err > >> white.paulbeard.org.err > >> ib_logfile1 mysql > >> > >> There may well be others but this one came to mind immediately. > > > > MySQL writes logfiles whose names contain the hostname, yes. The > > hostname is not, however, to the best of my knowledge, encoded into > > any files installed by the MySQL ports. There should be no problem > > installing MySQL on one system and running it on another. The two > > systems will merely use separate logfiles by default -- which is in > > fact probably a good thing, isn't it? If it isn't, there's probably > > a way to have MySQL write to a logfile of a name of your choosing. > > Consult the MySQL documentation. > > > > > > _______________________________________________ > > macports-users mailing list > > macports-users@lists.macosforge.org > > http://lists.macosforge.org/mailman/listinfo/macports-users > > > > > ---- > William Siegrist > Software Support Engineer > Mac OS Forge > http://macosforge.org/ > wsiegrist@apple.com > 408 862 7337 > > > > > > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/1a7bbf91/attachment.html From tabithamc at gmail.com Fri Jan 4 04:06:48 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Fri Jan 4 04:04:48 2008 Subject: Kaffe (Java) and Leopard? Message-ID: <7fccb3000801040406t772b498dnba9190674c6b3fd5@mail.gmail.com> Has anyone had any success installing some Java-related MacPorts, specifically the kaffe port, on Leopard or Leopard Server? I just tried kaffe on Leopard Server and got failure. I can post a bug report (as I didn't see any for kaffe and Leopard yet) but wanted to first inquire on the mailing list to see if there might be a simple workaround (I can then modify the Portfile with the workaround if need be and get the modified Portfile into the subversion repo). Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080104/33c6fb67/attachment.html From jochen at fhi-berlin.mpg.de Fri Jan 4 04:15:43 2008 From: jochen at fhi-berlin.mpg.de (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Fri Jan 4 04:13:57 2008 Subject: configure.args-delete Message-ID: <39C53211-190A-4D1C-93F1-F249C79D636B@fhi-berlin.mpg.de> Hi, in the qt4-mac port I need to specify something like configure.args-delete "-nomake examples" Hw does one delete arguments containing whitespace from the args? I have tried multiple different ideas ("-nomake examples", '-nomake examples', -nomake\ examples, {-nomake examples}) but none seems to work. I cannot simply say configure.args-delete -nomake examples because -nomake occurs multiple times in the configure.args. Is it possible to use regex? Which syntax? Any other hints? Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080104/2bdbcf75/PGP.bin From macports.users at gmail.com Fri Jan 4 07:41:54 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Fri Jan 4 07:40:08 2008 Subject: ocaml fails on Tiger (was: Re: sudo port install mldonkey) In-Reply-To: References: <590A936D-453F-4369-9E09-69E7D05001B2@gmail.com> Message-ID: <53DF8FAC-D824-438D-8AF1-6B62D94BC177@gmail.com> # I installed ocaml from precompiled binary # $ sudo port clean --dist --archive --work mldonkey ---> Cleaning mldonkey $ sudo port clean --dist --archive --work ocaml Password: ---> Cleaning ocaml $ sudo port clean --dist --archive --work mldonkey ---> Cleaning mldonkey Mac:~ pm$ sudo port -f install mldonkey ---> Fetching ocaml ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// caml.inria.fr/pub/distrib/ocaml-3.10/ ---> Verifying checksum(s) for ocaml ---> Extracting ocaml ---> Applying patches to ocaml ---> Configuring ocaml Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_oc aml/work/ocaml-3.10.0" && ./configure -prefix /opt/local -no-tk " returned error 2 Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) not balanced ../gnu/config.sub: line 128: [: !=: unary operator expected Invalid configuration `powerpc-apple-darwin8.11.0': machine `' not recognized Please specify the correct host type with the -host option Error: The following dependencies failed to build: lablgtk ocaml Error: Status 1 encountered during processing. $ # How do I get it to skip ocaml? On Dec 26, 2007, at 8:14 AM, Ryan Schmidt wrote: > This bug has already been reported: > > http://trac.macosforge.org/projects/macports/ticket/13583 > > I've added your email address to the bug's Cc list so you'll be > informed of its progress. > > > On Dec 26, 2007, at 05:58, Charlse Darwin wrote: > >> $ sudo port install mldonkey >> ---> Building ocaml with target world.opt >> Error: Target org.macports.build returned: shell command " cd "/ >> opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang >> _ocaml/work/ocaml-3.10.0" && unset LD_PREBIND >> LD_PREBIND_ALLOW_OVERLAP && make world.opt " returned error 2 >> Command output: cd byterun; make all >> make[1]: Nothing to be done for `all'. >> if test -f stdlib/libcamlrun.a; then :; else \ >> ln -s ../byterun/libcamlrun.a stdlib/libcamlrun.a; fi >> cd yacc; make all >> make[1]: Nothing to be done for `all'. >> cd lex; make all >> make[1]: Nothing to be done for `all'. >> cd tools; make all >> make[1]: Nothing to be done for `all'. >> cd stdlib; make all >> make[1]: Nothing to be done for `all'. >> cd asmrun; make all >> gcc -I../byterun -DCAML_NAME_SPACE -DNATIVE_CODE -DTARGET_power - >> DSYS_rhapsody -O -Wall -DDARWIN_VERSION_6 -D_FILE_OFFSET_BITS=64 >> -D_REENTRANT -c -o signals_asm.o signals_asm.c >> signals_asm.c: In function 'handle_signal': >> signals_asm.c:87: error: 'struct mcontext' has no member named '__ss' >> signals_asm.c:87: error: 'struct mcontext' has no member named '__ss' >> signals_asm.c:88: error: 'struct mcontext' has no member named '__ss' >> signals_asm.c: In function 'trap_handler': >> signals_asm.c:160: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c:161: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c:163: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c:164: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c: In function 'segv_handler': >> signals_asm.c:193: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c:193: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c:198: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c:199: error: 'struct mcontext' has no member named >> '__ss' >> make[1]: *** [signals_asm.o] Error 1 >> make: *** [runtimeopt] Error 2 >> >> Error: The following dependencies failed to build: lablgtk ocaml >> Error: Status 1 encountered during processing. From macports.users at gmail.com Fri Jan 4 07:45:08 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Fri Jan 4 07:43:20 2008 Subject: ocaml fails on Tiger (was: Re: sudo port install mldonkey) In-Reply-To: References: <590A936D-453F-4369-9E09-69E7D05001B2@gmail.com> Message-ID: # README from pre-compiled reads: # This package installs Objective Caml version 3.10.0. # You need Mac OS X 10.4.x (Tiger), with X11 and the # XCode tools (v2.4) installed. # Files will be installed in the following directories: # /usr/local/bin - command-line executables # /usr/local/lib/ocaml - library and support files # /usr/local/man - manual pages # I installed ocaml from precompiled binary # $ sudo port clean --dist --archive --work mldonkey ---> Cleaning mldonkey $ sudo port clean --dist --archive --work ocaml Password: ---> Cleaning ocaml $ sudo port clean --dist --archive --work mldonkey ---> Cleaning mldonkey Mac:~ pm$ sudo port -f install mldonkey ---> Fetching ocaml ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// caml.inria.fr/pub/distrib/ocaml-3.10/ ---> Verifying checksum(s) for ocaml ---> Extracting ocaml ---> Applying patches to ocaml ---> Configuring ocaml Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_oc aml/work/ocaml-3.10.0" && ./configure -prefix /opt/local -no-tk " returned error 2 Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) not balanced ../gnu/config.sub: line 128: [: !=: unary operator expected Invalid configuration `powerpc-apple-darwin8.11.0': machine `' not recognized Please specify the correct host type with the -host option Error: The following dependencies failed to build: lablgtk ocaml Error: Status 1 encountered during processing. $ # How do I get it to skip ocaml? On Dec 26, 2007, at 8:14 AM, Ryan Schmidt wrote: > This bug has already been reported: > > http://trac.macosforge.org/projects/macports/ticket/13583 > > I've added your email address to the bug's Cc list so you'll be > informed of its progress. > > > On Dec 26, 2007, at 05:58, Charlse Darwin wrote: > >> $ sudo port install mldonkey >> ---> Building ocaml with target world.opt >> Error: Target org.macports.build returned: shell command " cd "/ >> opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang >> _ocaml/work/ocaml-3.10.0" && unset LD_PREBIND >> LD_PREBIND_ALLOW_OVERLAP && make world.opt " returned error 2 >> Command output: cd byterun; make all >> make[1]: Nothing to be done for `all'. >> if test -f stdlib/libcamlrun.a; then :; else \ >> ln -s ../byterun/libcamlrun.a stdlib/libcamlrun.a; fi >> cd yacc; make all >> make[1]: Nothing to be done for `all'. >> cd lex; make all >> make[1]: Nothing to be done for `all'. >> cd tools; make all >> make[1]: Nothing to be done for `all'. >> cd stdlib; make all >> make[1]: Nothing to be done for `all'. >> cd asmrun; make all >> gcc -I../byterun -DCAML_NAME_SPACE -DNATIVE_CODE -DTARGET_power - >> DSYS_rhapsody -O -Wall -DDARWIN_VERSION_6 -D_FILE_OFFSET_BITS=64 >> -D_REENTRANT -c -o signals_asm.o signals_asm.c >> signals_asm.c: In function 'handle_signal': >> signals_asm.c:87: error: 'struct mcontext' has no member named '__ss' >> signals_asm.c:87: error: 'struct mcontext' has no member named '__ss' >> signals_asm.c:88: error: 'struct mcontext' has no member named '__ss' >> signals_asm.c: In function 'trap_handler': >> signals_asm.c:160: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c:161: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c:163: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c:164: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c: In function 'segv_handler': >> signals_asm.c:193: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c:193: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c:198: error: 'struct mcontext' has no member named >> '__ss' >> signals_asm.c:199: error: 'struct mcontext' has no member named >> '__ss' >> make[1]: *** [signals_asm.o] Error 1 >> make: *** [runtimeopt] Error 2 >> >> Error: The following dependencies failed to build: lablgtk ocaml >> Error: Status 1 encountered during processing. From lisfolks.lists at gmail.com Fri Jan 4 08:58:00 2008 From: lisfolks.lists at gmail.com (LeAnne Lis) Date: Fri Jan 4 08:55:58 2008 Subject: Error building p5-sdl_perl In-Reply-To: References: <14610995.post@talk.nabble.com> Message-ID: <14620410.post@talk.nabble.com> Ryan Schmidt-24 wrote: > > > On Jan 3, 2008, at 23:10, LeAnne Lis wrote: > >> A search for the p5-sdl_perl port brings up a ticket from Dec 30, >> #13757: >> frozenbubble2 doesn't build on leopard. However, it's been closed >> as a >> duplicate. If it truly is a duplicate, then of what? > > The note in the ticket says it is a duplicate of #13724. > Ah, yes - I missed that; however, #13724 is for the libsdl_image-framework. I was having that error earlier. A hard-coded requirement for +universal was suggested in that ticket as part of the problem, so I uninstalled/reinstalled all of its dependencies with +universal. That got me past the libsdl_image-framework error. I am trying to install frozenbubble2, and I got additional errors after that with similar messages. Each time I encountered an error, I tried uninstalling the error'd item, then reinstalling the port and its dependencies with +universal, and then it worked, so I have installed everything up to this p5-sdl_perl with the +universal variant. But this one says something about a missing library just before it crashes: ld: library not found for -lSDL_ttf Does that mean it's looking for libsdl_ttf? -- View this message in context: http://www.nabble.com/Error-building-p5-sdl_perl-tp14610995p14620410.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From afb at macports.org Fri Jan 4 09:30:05 2008 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Fri Jan 4 09:28:06 2008 Subject: Error building p5-sdl_perl In-Reply-To: <14620410.post@talk.nabble.com> References: <14610995.post@talk.nabble.com> <14620410.post@talk.nabble.com> Message-ID: <7424a83b821013b11c6d5ff0e70444b9@macports.org> LeAnne Lis wrote: > I am trying to install frozenbubble2, and I got additional errors > after that > with similar messages. Each time I encountered an error, I tried > uninstalling the error'd item, then reinstalling the port and its > dependencies with +universal, and then it worked, so I have installed > everything up to this p5-sdl_perl with the +universal variant. But > this one > says something about a missing library just before it crashes: ld: > library > not found for -lSDL_ttf > > Does that mean it's looking for libsdl_ttf? Yeah, p5-sdl_perl is a little confused in that it depends on the "framework" variants but actually links with the "library" variants. I ended up having to install both / all of them, before it ran... (also including to move all my existing /Library/Frameworks aside) --anders From ryandesign at macports.org Fri Jan 4 10:05:14 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri Jan 4 10:03:42 2008 Subject: ocaml fails on Tiger (was: Re: sudo port install mldonkey) In-Reply-To: <53DF8FAC-D824-438D-8AF1-6B62D94BC177@gmail.com> References: <590A936D-453F-4369-9E09-69E7D05001B2@gmail.com> <53DF8FAC-D824-438D-8AF1-6B62D94BC177@gmail.com> Message-ID: <903349F2-4D42-4AC6-AA07-DDE14D0C8D5E@macports.org> On Jan 4, 2008, at 09:41, Charlse Darwin wrote: > On Dec 26, 2007, at 8:14 AM, Ryan Schmidt wrote: > >> This bug has already been reported: >> >> http://trac.macosforge.org/projects/macports/ticket/13583 > > # I installed ocaml from precompiled binary > > # > > $ sudo port clean --dist --archive --work mldonkey > ---> Cleaning mldonkey > $ sudo port clean --dist --archive --work ocaml > Password: > ---> Cleaning ocaml > $ sudo port clean --dist --archive --work mldonkey > ---> Cleaning mldonkey > Mac:~ pm$ sudo port -f install mldonkey > ---> Fetching ocaml > ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// > caml.inria.fr/pub/distrib/ocaml-3.10/ > ---> Verifying checksum(s) for ocaml > ---> Extracting ocaml > ---> Applying patches to ocaml > ---> Configuring ocaml > Error: Target org.macports.configure returned: configure failure: > shell command " cd "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ > ocaml/work/ocaml-3.10.0" && ./configure -prefix /opt/local -no-tk " > returned error 2 > Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) not > balanced > ../gnu/config.sub: line 128: [: !=: unary operator expected > Invalid configuration `powerpc-apple-darwin8.11.0': machine `' not > recognized > Please specify the correct host type with the -host option > > Error: The following dependencies failed to build: lablgtk ocaml > Error: Status 1 encountered during processing. > $ > > # How do I get it to skip ocaml? There isn't a built-in way to do that. MacPorts is designed not to make use of any software you install outside of MacPorts. You could possibly modify the portfile to look for ocaml in a different directory. But what we would really like is for someone to figure out why the ocaml port fails to build, and fix it. From macports.users at gmail.com Fri Jan 4 10:16:23 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Fri Jan 4 10:14:48 2008 Subject: ocaml fails on Tiger (was: Re: sudo port install mldonkey) In-Reply-To: <903349F2-4D42-4AC6-AA07-DDE14D0C8D5E@macports.org> References: <590A936D-453F-4369-9E09-69E7D05001B2@gmail.com> <53DF8FAC-D824-438D-8AF1-6B62D94BC177@gmail.com> <903349F2-4D42-4AC6-AA07-DDE14D0C8D5E@macports.org> Message-ID: <3587928E-9410-4390-A732-7F248A231D0E@gmail.com> I get the message here that say `Software was successfully installed' for ocml. Why can't they put the same thing on MacPorts server? Also README file of the ocaml.package says this: Files will be installed in the following directories: /usr/local/bin - command-line executables /usr/local/lib/ocaml - library and support files /usr/local/man - manual pages Is there any way to move the stuff manually? On Jan 4, 2008, at 1:05 PM, Ryan Schmidt wrote: > > On Jan 4, 2008, at 09:41, Charlse Darwin wrote: > >> On Dec 26, 2007, at 8:14 AM, Ryan Schmidt wrote: >> >>> This bug has already been reported: >>> >>> http://trac.macosforge.org/projects/macports/ticket/13583 >> >> # I installed ocaml from precompiled binary >> >> # >> >> $ sudo port clean --dist --archive --work mldonkey >> ---> Cleaning mldonkey >> $ sudo port clean --dist --archive --work ocaml >> Password: >> ---> Cleaning ocaml >> $ sudo port clean --dist --archive --work mldonkey >> ---> Cleaning mldonkey >> Mac:~ pm$ sudo port -f install mldonkey >> ---> Fetching ocaml >> ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// >> caml.inria.fr/pub/distrib/ocaml-3.10/ >> ---> Verifying checksum(s) for ocaml >> ---> Extracting ocaml >> ---> Applying patches to ocaml >> ---> Configuring ocaml >> Error: Target org.macports.configure returned: configure failure: >> shell command " cd "/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang >> _ocaml/work/ocaml-3.10.0" && ./configure -prefix /opt/local -no-tk >> " returned error 2 >> Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) >> not balanced >> ../gnu/config.sub: line 128: [: !=: unary operator expected >> Invalid configuration `powerpc-apple-darwin8.11.0': machine `' not >> recognized >> Please specify the correct host type with the -host option >> >> Error: The following dependencies failed to build: lablgtk ocaml >> Error: Status 1 encountered during processing. >> $ >> >> # How do I get it to skip ocaml? > > There isn't a built-in way to do that. MacPorts is designed not to > make use of any software you install outside of MacPorts. You could > possibly modify the portfile to look for ocaml in a different > directory. But what we would really like is for someone to figure > out why the ocaml port fails to build, and fix it. > > > From paulbeard at gmail.com Fri Jan 4 10:29:28 2008 From: paulbeard at gmail.com (paul beard) Date: Fri Jan 4 10:27:32 2008 Subject: ocaml fails on Tiger (was: Re: sudo port install mldonkey) In-Reply-To: <3587928E-9410-4390-A732-7F248A231D0E@gmail.com> References: <590A936D-453F-4369-9E09-69E7D05001B2@gmail.com> <53DF8FAC-D824-438D-8AF1-6B62D94BC177@gmail.com> <903349F2-4D42-4AC6-AA07-DDE14D0C8D5E@macports.org> <3587928E-9410-4390-A732-7F248A231D0E@gmail.com> Message-ID: <076C8841-2A8F-4EF7-85AB-EBD0C8CD6DFA@gmail.com> On Jan 4, 2008, at 10:16 AM, Charlse Darwin wrote: > I get the message here that say `Software was successfully > installed' for ocml. Why can't they put the same thing on MacPorts > server? > > Also README file of the ocaml.package says this: > > Files will be installed in the following directories: > /usr/local/bin - command-line executables > /usr/local/lib/ocaml - library and support files > /usr/local/man - manual pages > > Is there any way to move the stuff manually? > Does ocaml come with an ocaml-config binary that might explain how those porters got it to work? Or, perhaps easiest, ask them what their special sauce it? From ryandesign at macports.org Fri Jan 4 10:49:11 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri Jan 4 10:47:37 2008 Subject: $ sudo port -f install MacPorts In-Reply-To: References: <76AEA96B-0DD7-41DC-919E-A498DF38B3C4@gmail.com> <0A5C870E-2B27-4AE6-B88D-23DF09A84AC3@macports.org> <3977330F-ED37-481E-94FA-4486F85A7626@gmail.com> <9559D3F5-439C-4EF4-BF97-5E55C8AC902B@macports.org> <7606F127-A982-457C-BA6B-20BD5EB8D46D@gmail.com> <92E070E3-B773-45FA-9465-054BF5CB0825@macports.org> Message-ID: On Jan 4, 2008, at 08:10, Charlse Darwin wrote: > On Jan 3, 2008, at 11:41 PM, Ryan Schmidt wrote: > >> On Jan 3, 2008, at 22:26, Charlse Darwin wrote: >> >>> On Jan 3, 2008, at 11:18 PM, Ryan Schmidt wrote: >>> >>>> On Jan 3, 2008, at 22:11, Charlse Darwin wrote: >>>> >>>>> `Command output: configure: error: cannot run /bin/sh ./ >>>>> config.sub' shows up in every port that I'm trying to install, >>>>> I just though reinstalling MacPorts might help. >>>> >>>> Oh, I didn't realize that. Well that certainly shouldn't be. >>>> >>>> Reinstalling MacPorts might help. But I don't think installing >>>> the port called MacPorts is the way to do that. At least, that's >>>> not documented anywhere. >>> >>> It all happened after I started playing with xnu (darwin_9, uname >>> -r on my machine returns 8.11.0) >>> I have tried installing MacPorts from this package >>> http://svn.macports.org/repository/macports/downloads/ >>> MacPorts-1.6.0/MacPorts-1.6.0-10.4-Tiger.dmg >>> >>> but it failed. I'm thinking maybe I should reinstalling the Xcode >>> too? >> >> XNU is the Mac OS X kernel, yes? What do you mean, playing with >> it? You are running Tiger? If so, what did you mean when you said >> "darwin_9"? In what way did installing MacPorts 1.6.0 from the >> Tiger disk image fail? If you're on Tiger, reinstalling Xcode 2.5 >> couldn't hurt. > > Yes I meant XNU the kernel of Mac OS X and I am running Tiger > (darwin_8.11.0). Days ago I tried to build and install the new > version of kernel from source code darwinsource/Current/> which failed. Somewhere along I must have > messed up something because after that I kept getting this error > message: > "Command output: configure: error: cannot run /bin/sh ./config.sub" > for almost every port I'm trying to install It does sound messed up. You could try reinstalling Xcode, or you may have to reinstall Mac OS X. Unless there's a config.log file you could look at that suggests a different course of action. But you definitely need to solve this general inability to build things before we tackle any port-specific problems. From macports.users at gmail.com Fri Jan 4 11:55:31 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Fri Jan 4 11:53:34 2008 Subject: sudo port install mldonkey References: <062.eb8a5ba5335bf52b777fe741a23dff2c@macosforge.org> Message-ID: <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> $ sudo port -f clean --dist --archive --work ocmal Error: Port ocmal not found $ sudo port -d sync DEBUG: Synchronizing ports tree(s) Synchronizing local ports tree from rsync://rsync.macports.org/ release/ports/ DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/ release/ports/ /opt/local/var/macports/sources/rsync.macports.org/ release/ports receiving file list ... done archivers/bzip2/ devel/apr/ devel/apr-util/ devel/atk/ graphics/ImageMagick/ graphics/cairo/ net/bmon/ net/bwm-ng/ net/curl/ shells/bash/ textproc/aspell/ www/apache2/ x11/Xft2/ sent 74 bytes received 292538 bytes 16720.69 bytes/sec total size is 16277463 speedup is 55.63 $ sudo port -f install ocmal Error: Port ocmal not found $ sudo port -f install ocaml ---> Fetching ocaml ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// caml.inria.fr/pub/distrib/ocaml-3.10/ ---> Verifying checksum(s) for ocaml ---> Extracting ocaml ---> Configuring ocaml Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_oc aml/work/ocaml-3.10.0" && ./configure -prefix /opt/local -no-tk " returned error 2 Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) not balanced ../gnu/config.sub: line 128: [: !=: unary operator expected Invalid configuration `powerpc-apple-darwin8.11.0': machine `' not recognized Please specify the correct host type with the -host option Error: Status 1 encountered during processing. $ # where do I get the fixed version from? Begin forwarded message: > From: "MacPorts" > Date: January 4, 2008 2:17:32 PM EST (CA) > To: ryandesign@macports.org, pguyot@kallisys.net > Cc: macports-tickets@lists.macosforge.org, bfulgham@macports.org, > ajmas@sympatico.ca, macports.users@gmail.com > Subject: Re: [MacPorts] #13583: ocaml 3.10.0 build failure on > Tiger: 'struct mcontext' has no member named '__ss' > Reply-To: noreply@macosforge.org > > #13583: ocaml 3.10.0 build failure on Tiger: 'struct mcontext' has > no member named > '__ss' > -------------------------------------- > +------------------------------------- > Reporter: ryandesign@macports.org | Owner: > pguyot@kallisys.net > Type: defect | Status: closed > Priority: Normal | Milestone: Port Bugs > Component: ports | Version: 1.7.0 > Resolution: fixed | Keywords: > -------------------------------------- > +------------------------------------- > Changes (by ryandesign@macports.org): > > * status: new => closed > * resolution: => fixed > > Comment: > > Since the maintainer is not responding, I'll deal with this. > > r31240 broke ocaml. When the patch was originally attached to ticket > #13308, the patchfiles were wrapped in a "`platform darwin 9`" > section, > but as committed, the patchfiles apply on all platforms. I am > changing > this in r32486 so that the patchfiles only apply on darwin 9, so > that it > builds again on earlier systems. > > -- > Ticket URL: 13583#comment:3> > MacPorts > Ports system for Mac OS From dluke at geeklair.net Fri Jan 4 12:23:47 2008 From: dluke at geeklair.net (Daniel J. Luke) Date: Fri Jan 4 12:21:46 2008 Subject: sudo port install mldonkey In-Reply-To: <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> References: <062.eb8a5ba5335bf52b777fe741a23dff2c@macosforge.org> <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> Message-ID: <71547161-7F9E-4C5A-8662-DA34C3FC3E3F@geeklair.net> On Jan 4, 2008, at 2:55 PM, Charlse Darwin wrote: > Error: Target org.macports.configure returned: configure failure: > shell command " cd "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_lang_ocaml/work/ocaml-3.10.0" && ./ > configure -prefix /opt/local -no-tk " returned error 2 > Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) not > balanced > ../gnu/config.sub: line 128: [: !=: unary operator expected > Invalid configuration `powerpc-apple-darwin8.11.0': machine `' not > recognized > Please specify the correct host type with the -host option That's not the same error as mentioned in the ticket you quoted below. > # where do I get the fixed version from? From your other posts, it sounds like you have created a unique state on your machine that no one here is likely to be able to help you fix. If you cannot figure out how to undo the changes you have made that make your system differ from a 'normal' install, you may be best off reinstalling Mac OS X and starting again. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080104/dc0e2f5c/PGP.bin From face at CentosPrime.COM Fri Jan 4 12:29:00 2008 From: face at CentosPrime.COM (Chris Janton) Date: Fri Jan 4 12:27:09 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> Message-ID: <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> On 2008-01-03 , at 23:32 , Boey Maun Suang wrote: > The steps to take appear below (apologies if they are more detailed > that > you need); steps 1, 4, 5 and 7 are the same as the normal steps for > installing MacPorts from source [1]. I started with a "clean" source install of MacPorts 1.5 The initial "port selfupdate" is updating to 1.6 (if I am to believe the messages on my screen). Fails in the expected way - the sqllite errors > 7. Run "./configure", "make" and "sudo make install" as normal [1]. > > 8. If you haven't set your shell variables, do so at this point. > If you > use bash, follow the guide [5]. If you use tcsh (which I believe > is the > default on Panther), then running > > setenv PATH /opt/local/bin:/opt/local/sbin:$(PATH) > > at the command line should be sufficient. > > 9. Run "sudo port selfupdate" as normal [6]. selfupdate done! > > 10. At the command line, you should now find that, when run on any > portname (e.g. xmlcatmgr) the "port info " and "port install > " commands fail with > > Error: Unable to open port: invalid command name "ui_channels" > > However, you should find that "port search " works > fine. > (In general, it appears to me that the port commands that fail with > the above message are the ones for which the "port" command attempts > to open a Portfile.) Yes. That is exactly what I see now. Next steps? 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From macports.users at gmail.com Fri Jan 4 12:30:08 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Fri Jan 4 12:28:10 2008 Subject: sudo port install mldonkey In-Reply-To: <8190E5C7-3C1B-47D9-9F86-66F872779379@macports.org> References: <062.eb8a5ba5335bf52b777fe741a23dff2c@macosforge.org> <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> <8190E5C7-3C1B-47D9-9F86-66F872779379@macports.org> Message-ID: $ ls -l /usr/bin/sed -r-xr-xr-x 1 root wheel 38424 Dec 31 09:16 /usr/bin/sed* $ file /usr/bin/sed /usr/bin/sed: Mach-O executable ppc $ which sed /usr/bin/sed Should chmod 68388 /usr/bin/sed ? On Jan 4, 2008, at 3:23 PM, Ryan Schmidt wrote: > On Jan 4, 2008, at 13:55, Charlse Darwin wrote: > >> $ sudo port -f clean --dist --archive --work ocmal >> Error: Port ocmal not found > > It's called ocaml... > >> $ sudo port -d sync >> DEBUG: Synchronizing ports tree(s) >> Synchronizing local ports tree from rsync://rsync.macports.org/ >> release/ports/ >> DEBUG: /usr/bin/rsync -rtzv --delete-after rsync:// >> rsync.macports.org/release/ports/ /opt/local/var/macports/sources/ >> rsync.macports.org/release/ports >> receiving file list ... done >> archivers/bzip2/ >> devel/apr/ >> devel/apr-util/ >> devel/atk/ >> graphics/ImageMagick/ >> graphics/cairo/ >> net/bmon/ >> net/bwm-ng/ >> net/curl/ >> shells/bash/ >> textproc/aspell/ >> www/apache2/ >> x11/Xft2/ >> >> sent 74 bytes received 292538 bytes 16720.69 bytes/sec >> total size is 16277463 speedup is 55.63 >> $ sudo port -f install ocmal >> Error: Port ocmal not found > > Still called ocaml... > >> $ sudo port -f install ocaml >> ---> Fetching ocaml >> ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// >> caml.inria.fr/pub/distrib/ocaml-3.10/ >> ---> Verifying checksum(s) for ocaml >> ---> Extracting ocaml >> ---> Configuring ocaml >> Error: Target org.macports.configure returned: configure failure: >> shell command " cd "/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang >> _ocaml/work/ocaml-3.10.0" && ./configure -prefix /opt/local -no-tk >> " returned error 2 >> Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) >> not balanced >> ../gnu/config.sub: line 128: [: !=: unary operator expected >> Invalid configuration `powerpc-apple-darwin8.11.0': machine `' not >> recognized >> Please specify the correct host type with the -host option >> >> Error: Status 1 encountered during processing. >> $ >> >> # where do I get the fixed version from? > > As you see from the output of "port sync" above, you did not > receive an updated portfile for ocaml. You need to wait 30 minutes > after a commit is made to the repository before it shows up on the > rsync server. > > However, the errors you are experiencing are different from the > errors reported in the ticket. The errors you are experiencing may > be related to your experiments in installing a new xnu kernel. You > may need to reinstall Xcode or Mac OS X to resolve those issues. > > But first, let's start with your sed. There's nothing that I can > see that's wrong with "s/-[^-]*$//"; looks perfectly balanced to > me. What can you tell me about your sed? Here's info about mine, > from my MacBook Pro running 10.4.11: > > $ ls -l /usr/bin/sed > -r-xr-xr-x 1 root wheel 68388 Dec 7 2006 /usr/bin/sed > $ file /usr/bin/sed > /usr/bin/sed: Mach-O universal binary with 2 architectures > /usr/bin/sed (for architecture i386): Mach-O executable i386 > /usr/bin/sed (for architecture ppc): Mach-O executable ppc > $ > > Your info will be different because you're on PowerPC but I'm > curious to see if it has about the same modification date > (indicating it's from Apple), or if it's newer (indicating it was > replaced with something else at some point). > From ryandesign at macports.org Fri Jan 4 12:40:45 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri Jan 4 12:39:12 2008 Subject: sudo port install mldonkey In-Reply-To: References: <062.eb8a5ba5335bf52b777fe741a23dff2c@macosforge.org> <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> <8190E5C7-3C1B-47D9-9F86-66F872779379@macports.org> Message-ID: On Jan 4, 2008, at 14:30, Charlse Darwin wrote: > On Jan 4, 2008, at 3:23 PM, Ryan Schmidt wrote: > >> On Jan 4, 2008, at 13:55, Charlse Darwin wrote: [snip] >>> $ sudo port -f install ocaml >>> ---> Fetching ocaml >>> ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// >>> caml.inria.fr/pub/distrib/ocaml-3.10/ >>> ---> Verifying checksum(s) for ocaml >>> ---> Extracting ocaml >>> ---> Configuring ocaml >>> Error: Target org.macports.configure returned: configure failure: >>> shell command " cd "/opt/local/var/macports/build/ >>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lan >>> g_ocaml/work/ocaml-3.10.0" && ./configure -prefix /opt/local -no- >>> tk " returned error 2 >>> Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) >>> not balanced >>> ../gnu/config.sub: line 128: [: !=: unary operator expected >>> Invalid configuration `powerpc-apple-darwin8.11.0': machine `' >>> not recognized >>> Please specify the correct host type with the -host option [snip] >> But first, let's start with your sed. There's nothing that I can >> see that's wrong with "s/-[^-]*$//"; looks perfectly balanced to >> me. What can you tell me about your sed? Here's info about mine, >> from my MacBook Pro running 10.4.11: >> >> $ ls -l /usr/bin/sed >> -r-xr-xr-x 1 root wheel 68388 Dec 7 2006 /usr/bin/sed >> $ file /usr/bin/sed >> /usr/bin/sed: Mach-O universal binary with 2 architectures >> /usr/bin/sed (for architecture i386): Mach-O executable i386 >> /usr/bin/sed (for architecture ppc): Mach-O executable ppc >> $ >> >> Your info will be different because you're on PowerPC but I'm >> curious to see if it has about the same modification date >> (indicating it's from Apple), or if it's newer (indicating it was >> replaced with something else at some point). > > $ ls -l /usr/bin/sed > -r-xr-xr-x 1 root wheel 38424 Dec 31 09:16 /usr/bin/sed* > $ file /usr/bin/sed > /usr/bin/sed: Mach-O executable ppc > $ which sed > /usr/bin/sed > > Should chmod 68388 /usr/bin/sed ? That doesn't make sense. 68388 is the size in bytes of my sed program. Yours is 38424 bytes. That sounds about right, given that on PowerPC Macs, it should contain only ppc code (and not ppc and i386 code as on Intel Macs). However, the fact that it was modified December 31, 2007 is not right, and it indicates that you have probably replaced the sed that came with Mac OS X with something else which is apparently not functioning the way Apple's version did. You could replace this broken sed with the one that came with Mac OS X by copying it from the Mac OS X Tiger DVD. However, I recommend you first check /usr/bin and see if anything else was replaced by you on December 31. If so, who knows where else on your system essential components have been replaced, so reinstalling Mac OS X would be safer. From ryandesign at macports.org Fri Jan 4 12:23:27 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri Jan 4 12:49:54 2008 Subject: sudo port install mldonkey In-Reply-To: <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> References: <062.eb8a5ba5335bf52b777fe741a23dff2c@macosforge.org> <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> Message-ID: <8190E5C7-3C1B-47D9-9F86-66F872779379@macports.org> On Jan 4, 2008, at 13:55, Charlse Darwin wrote: > $ sudo port -f clean --dist --archive --work ocmal > Error: Port ocmal not found It's called ocaml... > $ sudo port -d sync > DEBUG: Synchronizing ports tree(s) > Synchronizing local ports tree from rsync://rsync.macports.org/ > release/ports/ > DEBUG: /usr/bin/rsync -rtzv --delete-after rsync:// > rsync.macports.org/release/ports/ /opt/local/var/macports/sources/ > rsync.macports.org/release/ports > receiving file list ... done > archivers/bzip2/ > devel/apr/ > devel/apr-util/ > devel/atk/ > graphics/ImageMagick/ > graphics/cairo/ > net/bmon/ > net/bwm-ng/ > net/curl/ > shells/bash/ > textproc/aspell/ > www/apache2/ > x11/Xft2/ > > sent 74 bytes received 292538 bytes 16720.69 bytes/sec > total size is 16277463 speedup is 55.63 > $ sudo port -f install ocmal > Error: Port ocmal not found Still called ocaml... > $ sudo port -f install ocaml > ---> Fetching ocaml > ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// > caml.inria.fr/pub/distrib/ocaml-3.10/ > ---> Verifying checksum(s) for ocaml > ---> Extracting ocaml > ---> Configuring ocaml > Error: Target org.macports.configure returned: configure failure: > shell command " cd "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ > ocaml/work/ocaml-3.10.0" && ./configure -prefix /opt/local -no-tk " > returned error 2 > Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) not > balanced > ../gnu/config.sub: line 128: [: !=: unary operator expected > Invalid configuration `powerpc-apple-darwin8.11.0': machine `' not > recognized > Please specify the correct host type with the -host option > > Error: Status 1 encountered during processing. > $ > > # where do I get the fixed version from? As you see from the output of "port sync" above, you did not receive an updated portfile for ocaml. You need to wait 30 minutes after a commit is made to the repository before it shows up on the rsync server. However, the errors you are experiencing are different from the errors reported in the ticket. The errors you are experiencing may be related to your experiments in installing a new xnu kernel. You may need to reinstall Xcode or Mac OS X to resolve those issues. But first, let's start with your sed. There's nothing that I can see that's wrong with "s/-[^-]*$//"; looks perfectly balanced to me. What can you tell me about your sed? Here's info about mine, from my MacBook Pro running 10.4.11: $ ls -l /usr/bin/sed -r-xr-xr-x 1 root wheel 68388 Dec 7 2006 /usr/bin/sed $ file /usr/bin/sed /usr/bin/sed: Mach-O universal binary with 2 architectures /usr/bin/sed (for architecture i386): Mach-O executable i386 /usr/bin/sed (for architecture ppc): Mach-O executable ppc $ Your info will be different because you're on PowerPC but I'm curious to see if it has about the same modification date (indicating it's from Apple), or if it's newer (indicating it was replaced with something else at some point). From macports.users at gmail.com Fri Jan 4 13:05:35 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Fri Jan 4 13:03:37 2008 Subject: sudo port install mldonkey In-Reply-To: References: <062.eb8a5ba5335bf52b777fe741a23dff2c@macosforge.org> <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> <8190E5C7-3C1B-47D9-9F86-66F872779379@macports.org> Message-ID: <5C403FE6-BE33-473C-BB65-2B7CCF6FE7D2@gmail.com> God you master this thing! So I reinstalled text_cmds (sed is there) from its source: and right now `$ sudo port -f install ocaml' is flying before my eyes On Jan 4, 2008, at 3:40 PM, Ryan Schmidt wrote: > On Jan 4, 2008, at 14:30, Charlse Darwin wrote: > >> On Jan 4, 2008, at 3:23 PM, Ryan Schmidt wrote: >> >>> On Jan 4, 2008, at 13:55, Charlse Darwin wrote: > > [snip] > >>>> $ sudo port -f install ocaml >>>> ---> Fetching ocaml >>>> ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// >>>> caml.inria.fr/pub/distrib/ocaml-3.10/ >>>> ---> Verifying checksum(s) for ocaml >>>> ---> Extracting ocaml >>>> ---> Configuring ocaml >>>> Error: Target org.macports.configure returned: configure >>>> failure: shell command " cd "/opt/local/var/macports/build/ >>>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_la >>>> ng_ocaml/work/ocaml-3.10.0" && ./configure -prefix /opt/local - >>>> no-tk " returned error 2 >>>> Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) >>>> not balanced >>>> ../gnu/config.sub: line 128: [: !=: unary operator expected >>>> Invalid configuration `powerpc-apple-darwin8.11.0': machine `' >>>> not recognized >>>> Please specify the correct host type with the -host option > > [snip] > >>> But first, let's start with your sed. There's nothing that I can >>> see that's wrong with "s/-[^-]*$//"; looks perfectly balanced to >>> me. What can you tell me about your sed? Here's info about mine, >>> from my MacBook Pro running 10.4.11: >>> >>> $ ls -l /usr/bin/sed >>> -r-xr-xr-x 1 root wheel 68388 Dec 7 2006 /usr/bin/sed >>> $ file /usr/bin/sed >>> /usr/bin/sed: Mach-O universal binary with 2 architectures >>> /usr/bin/sed (for architecture i386): Mach-O executable i386 >>> /usr/bin/sed (for architecture ppc): Mach-O executable ppc >>> $ >>> >>> Your info will be different because you're on PowerPC but I'm >>> curious to see if it has about the same modification date >>> (indicating it's from Apple), or if it's newer (indicating it was >>> replaced with something else at some point). >> >> $ ls -l /usr/bin/sed >> -r-xr-xr-x 1 root wheel 38424 Dec 31 09:16 /usr/bin/sed* >> $ file /usr/bin/sed >> /usr/bin/sed: Mach-O executable ppc >> $ which sed >> /usr/bin/sed >> >> Should chmod 68388 /usr/bin/sed ? > > That doesn't make sense. 68388 is the size in bytes of my sed > program. Yours is 38424 bytes. That sounds about right, given that > on PowerPC Macs, it should contain only ppc code (and not ppc and > i386 code as on Intel Macs). However, the fact that it was modified > December 31, 2007 is not right, and it indicates that you have > probably replaced the sed that came with Mac OS X with something > else which is apparently not functioning the way Apple's version > did. You could replace this broken sed with the one that came with > Mac OS X by copying it from the Mac OS X Tiger DVD. However, I > recommend you first check /usr/bin and see if anything else was > replaced by you on December 31. If so, who knows where else on your > system essential components have been replaced, so reinstalling Mac > OS X would be safer. > From ryandesign at macports.org Fri Jan 4 14:12:13 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri Jan 4 14:10:40 2008 Subject: sudo port install mldonkey In-Reply-To: <8FE63DDA-6898-4A5B-966A-DABA5755BEAC@gmail.com> References: <062.eb8a5ba5335bf52b777fe741a23dff2c@macosforge.org> <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> <8190E5C7-3C1B-47D9-9F86-66F872779379@macports.org> <8FE63DDA-6898-4A5B-966A-DABA5755BEAC@gmail.com> Message-ID: <84EB1E79-76EC-4145-94CE-0E67E988FEE5@macports.org> Please keep the discussion on the mailing list using Reply All when you reply. On Jan 4, 2008, at 15:55, Charlse Darwin wrote: > $ sudo port install mldonkey > Password: > ---> Configuring mldonkey > Error: Target org.macports.configure returned: configure failure: > shell command " cd "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_m > ldonkey/work/mldonkey-2.8.5" && ./configure --prefix=/opt/local " > returned error 1 > Command output: > -------------------------------- > Checking system tools. > -------------------------------- > checking for ranlib... ranlib > checking for gmake... gmake > checking for make... (cached) gmake > checking if gmake is GNU make ... yes > checking for bzip2... bzip2 > checking for gzip... (cached) bzip2 > checking for perl... /opt/local/bin/perl > checking for rpmbuild... no > checking for rpm... no > checking for wget... wget > ---------------------------------------- > Checking system tools finished. > ---------------------------------------- > > -------------------------------- > Checking Ocaml compiler. > -------------------------------- > checking for ocamlc.opt... /opt/local/bin/ocamlc.opt > checking for ocamlc... /opt/local/bin/ocamlc.opt > checking for camlp4... /opt/local/bin/camlp4 > Need build > ******** Objective-Caml 3.09.3 is required ********* > ******* Check http://caml.inria.fr/ ******** > Do you want this script to try to download and install ocaml > LOCALLY in mldonkey directory ? > ./configure: line 4612: read: read error: 0: Bad file descriptor > > Error: Status 1 encountered during processing. > $ port -q info --version ocaml > 3.10.0 > $ I agree. I get the same thing. Maybe mldonkey 2.8.5 just does not work with ocaml 3.10.0 (since it says it needs "3.09.3" (and not "3.09.3 or later")). You should file a ticket in our issue tracker and assign it to the maintainer of the mldonkey port. Maybe updating the port to the current version of mldonkey, 2.9.2, would help. You could edit the portfile yourself and test whether updating to 2.9.2 works; if it does, you can attach your diff to the ticket. From macports.users at gmail.com Fri Jan 4 15:47:23 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Fri Jan 4 15:45:22 2008 Subject: sudo port install mldonkey In-Reply-To: References: <062.eb8a5ba5335bf52b777fe741a23dff2c@macosforge.org> <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> <8190E5C7-3C1B-47D9-9F86-66F872779379@macports.org> Message-ID: <580A7E4C-9359-4318-A408-1057BF7E9700@gmail.com> $ sudo port install mldonkey Password: ---> Configuring mldonkey Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_mld onkey/work/mldonkey-2.8.5" && ./configure --prefix=/opt/local " returned error 1 Command output: -------------------------------- Checking system tools. -------------------------------- checking for ranlib... ranlib checking for gmake... gmake checking for make... (cached) gmake checking if gmake is GNU make ... yes checking for bzip2... bzip2 checking for gzip... (cached) bzip2 checking for perl... /opt/local/bin/perl checking for rpmbuild... no checking for rpm... no checking for wget... wget ---------------------------------------- Checking system tools finished. ---------------------------------------- -------------------------------- Checking Ocaml compiler. -------------------------------- checking for ocamlc.opt... /opt/local/bin/ocamlc.opt checking for ocamlc... /opt/local/bin/ocamlc.opt checking for camlp4... /opt/local/bin/camlp4 Need build ******** Objective-Caml 3.09.3 is required ********* ******* Check http://caml.inria.fr/ ******** Do you want this script to try to download and install ocaml LOCALLY in mldonkey directory ? ./configure: line 4612: read: read error: 0: Bad file descriptor Error: Status 1 encountered during processing. $ port -q info --version ocaml 3.10.0 $ On Jan 4, 2008, at 3:40 PM, Ryan Schmidt wrote: > On Jan 4, 2008, at 14:30, Charlse Darwin wrote: > >> On Jan 4, 2008, at 3:23 PM, Ryan Schmidt wrote: >> >>> On Jan 4, 2008, at 13:55, Charlse Darwin wrote: > > [snip] > >>>> $ sudo port -f install ocaml >>>> ---> Fetching ocaml >>>> ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// >>>> caml.inria.fr/pub/distrib/ocaml-3.10/ >>>> ---> Verifying checksum(s) for ocaml >>>> ---> Extracting ocaml >>>> ---> Configuring ocaml >>>> Error: Target org.macports.configure returned: configure >>>> failure: shell command " cd "/opt/local/var/macports/build/ >>>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_la >>>> ng_ocaml/work/ocaml-3.10.0" && ./configure -prefix /opt/local - >>>> no-tk " returned error 2 >>>> Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) >>>> not balanced >>>> ../gnu/config.sub: line 128: [: !=: unary operator expected >>>> Invalid configuration `powerpc-apple-darwin8.11.0': machine `' >>>> not recognized >>>> Please specify the correct host type with the -host option > > [snip] > >>> But first, let's start with your sed. There's nothing that I can >>> see that's wrong with "s/-[^-]*$//"; looks perfectly balanced to >>> me. What can you tell me about your sed? Here's info about mine, >>> from my MacBook Pro running 10.4.11: >>> >>> $ ls -l /usr/bin/sed >>> -r-xr-xr-x 1 root wheel 68388 Dec 7 2006 /usr/bin/sed >>> $ file /usr/bin/sed >>> /usr/bin/sed: Mach-O universal binary with 2 architectures >>> /usr/bin/sed (for architecture i386): Mach-O executable i386 >>> /usr/bin/sed (for architecture ppc): Mach-O executable ppc >>> $ >>> >>> Your info will be different because you're on PowerPC but I'm >>> curious to see if it has about the same modification date >>> (indicating it's from Apple), or if it's newer (indicating it was >>> replaced with something else at some point). >> >> $ ls -l /usr/bin/sed >> -r-xr-xr-x 1 root wheel 38424 Dec 31 09:16 /usr/bin/sed* >> $ file /usr/bin/sed >> /usr/bin/sed: Mach-O executable ppc >> $ which sed >> /usr/bin/sed >> >> Should chmod 68388 /usr/bin/sed ? > > That doesn't make sense. 68388 is the size in bytes of my sed > program. Yours is 38424 bytes. That sounds about right, given that > on PowerPC Macs, it should contain only ppc code (and not ppc and > i386 code as on Intel Macs). However, the fact that it was modified > December 31, 2007 is not right, and it indicates that you have > probably replaced the sed that came with Mac OS X with something > else which is apparently not functioning the way Apple's version > did. You could replace this broken sed with the one that came with > Mac OS X by copying it from the Mac OS X Tiger DVD. However, I > recommend you first check /usr/bin and see if anything else was > replaced by you on December 31. If so, who knows where else on your > system essential components have been replaced, so reinstalling Mac > OS X would be safer. > From macports.users at gmail.com Fri Jan 4 16:08:50 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Fri Jan 4 16:06:50 2008 Subject: Fwd: sudo port install mldonkey References: <84EB1E79-76EC-4145-94CE-0E67E988FEE5@macports.org> Message-ID: $ sudo port -fvd install mldonkey DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/net/mldonkey DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/net/mldonkey DEBUG: Requested variant powerpc is not provided by port mldonkey. DEBUG: Requested variant darwin is not provided by port mldonkey. DEBUG: Requested variant macosx is not provided by port mldonkey. DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/lang/ocaml DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/lang/ocaml DEBUG: Requested variant powerpc is not provided by port ocaml. DEBUG: Requested variant darwin is not provided by port ocaml. DEBUG: Requested variant macosx is not provided by port ocaml. DEBUG: Searching for dependency: ocaml DEBUG: Found Dependency: receipt exists for ocaml DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/x11/lablgtk DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/x11/lablgtk DEBUG: Requested variant powerpc is not provided by port lablgtk. DEBUG: Requested variant darwin is not provided by port lablgtk. DEBUG: Requested variant macosx is not provided by port lablgtk. DEBUG: Searching for dependency: lablgtk DEBUG: Found Dependency: receipt exists for lablgtk DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/textproc/expat DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/textproc/expat DEBUG: Requested variant powerpc is not provided by port expat. DEBUG: Requested variant darwin is not provided by port expat. DEBUG: Requested variant macosx is not provided by port expat. DEBUG: Searching for dependency: expat DEBUG: Found Dependency: receipt exists for expat DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/graphics/fontconfig DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/graphics/fontconfig DEBUG: Requested variant powerpc is not provided by port fontconfig. DEBUG: Requested variant darwin is not provided by port fontconfig. DEBUG: Executing variant macosx provides macosx DEBUG: Searching for dependency: fontconfig DEBUG: Found Dependency: receipt exists for fontconfig DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/print/freetype DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/print/freetype DEBUG: Requested variant powerpc is not provided by port freetype. DEBUG: Requested variant darwin is not provided by port freetype. DEBUG: Requested variant macosx is not provided by port freetype. DEBUG: Searching for dependency: freetype DEBUG: Found Dependency: receipt exists for freetype DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/graphics/gd2 DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/graphics/gd2 DEBUG: Requested variant powerpc is not provided by port gd2. DEBUG: Requested variant macosx is not provided by port gd2. DEBUG: Executing variant darwin provides darwin DEBUG: Searching for dependency: gd2 DEBUG: Found Dependency: receipt exists for gd2 DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/graphics/jpeg DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/graphics/jpeg DEBUG: Requested variant powerpc is not provided by port jpeg. DEBUG: Requested variant darwin is not provided by port jpeg. DEBUG: Requested variant macosx is not provided by port jpeg. DEBUG: Searching for dependency: jpeg DEBUG: Found Dependency: receipt exists for jpeg DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/textproc/libiconv DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/textproc/libiconv DEBUG: Requested variant powerpc is not provided by port libiconv. DEBUG: Requested variant darwin is not provided by port libiconv. DEBUG: Requested variant macosx is not provided by port libiconv. DEBUG: Executing variant darwin_8 provides darwin_8 DEBUG: Searching for dependency: libiconv DEBUG: Found Dependency: receipt exists for libiconv DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/graphics/libpng DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/graphics/libpng DEBUG: Requested variant powerpc is not provided by port libpng. DEBUG: Requested variant darwin is not provided by port libpng. DEBUG: Requested variant macosx is not provided by port libpng. DEBUG: Executing variant darwin_8 provides darwin_8 DEBUG: Searching for dependency: libpng DEBUG: Found Dependency: receipt exists for libpng DEBUG: Executing org.macports.main (mldonkey) ---> Fetching mldonkey DEBUG: Executing org.macports.fetch (mldonkey) ---> mldonkey-2.8.5.tar.bz2 doesn't seem to exist in /opt/local/var/ macports/distfiles/mldonkey ---> Attempting to fetch mldonkey-2.8.5.tar.bz2 from http:// downloads.sourceforge.net/mldonkey % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:01:39 --:--:-- 0 DEBUG: Fetching failed:: server returned nothing (no headers, no data) ---> Attempting to fetch mldonkey-2.8.5.tar.bz2 from http:// easynews.dl.sourceforge.net/mldonkey % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2600k 100 2600k 0 0 277k 0 0:00:09 0:00:09 --:--:-- 262k ---> Verifying checksum(s) for mldonkey DEBUG: Executing org.macports.checksum (mldonkey) ---> Checksumming mldonkey-2.8.5.tar.bz2 DEBUG: Correct (md5) checksum for mldonkey-2.8.5.tar.bz2 DEBUG: Correct (sha1) checksum for mldonkey-2.8.5.tar.bz2 DEBUG: Correct (rmd160) checksum for mldonkey-2.8.5.tar.bz2 DEBUG: setting option extract.cmd to /opt/local/bin/bzip2 ---> Extracting mldonkey DEBUG: Executing org.macports.extract (mldonkey) ---> Extracting mldonkey-2.8.5.tar.bz2 DEBUG: setting option extract.args to /opt/local/var/macports/ distfiles/mldonkey/mldonkey-2.8.5.tar.bz2 DEBUG: Environment: DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_mld onkey/work" && /opt/local/bin/bzip2 -dc /opt/local/var/macports/ distfiles/mldonkey/mldonkey-2.8.5.tar.bz2 | /usr/bin/gnutar --no-same- owner -xf -' DEBUG: Executing org.macports.patch (mldonkey) ---> Configuring mldonkey DEBUG: Executing org.macports.configure (mldonkey) DEBUG: Using compiler 'Mac OS X gcc 4.0' DEBUG: Environment: CFLAGS='-O2' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-O2' CPP='/usr/bin/cpp-4.0' CXX='/usr/bin/g++-4.0' F90FLAGS='-O2' LDFLAGS='-L/opt/local/lib' FCFLAGS='-O2' OBJC='/usr/ bin/gcc-4.0' INSTALL='/usr/bin/install' OBJCFLAGS='-O2' FFLAGS='-O2' CC='gcc' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_mld onkey/work/mldonkey-2.8.5" && ./configure --prefix=/opt/local' Arguments to configure: '--prefix=/opt/local' 'CC=gcc' 'CFLAGS=-O2' 'LDFLAGS=-L/opt/local/lib' 'CPPFLAGS=-I/opt/local/include' 'CPP=/usr/ bin/cpp-4.0' 'CXX=/usr/bin/g++-4.0' 'CXXFLAGS=-O2' checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... /usr/bin/cpp-4.0 checking build system type... powerpc-apple-darwin8.11.0 checking host system type... powerpc-apple-darwin8.11.0 checking for sed... sed -------------------------------- Checking system tools. -------------------------------- checking for ranlib... ranlib checking for gmake... gmake checking for make... (cached) gmake checking if gmake is GNU make ... yes checking for bzip2... bzip2 checking for gzip... (cached) bzip2 checking for perl... /opt/local/bin/perl checking for rpmbuild... no checking for rpm... no checking for wget... wget ---------------------------------------- Checking system tools finished. ---------------------------------------- -------------------------------- Checking Ocaml compiler. -------------------------------- checking for ocamlc.opt... /opt/local/bin/ocamlc.opt checking for ocamlc... /opt/local/bin/ocamlc.opt checking for camlp4... /opt/local/bin/camlp4 Need build ******** Objective-Caml 3.09.3 is required ********* ******* Check http://caml.inria.fr/ ******** Do you want this script to try to download and install ocaml LOCALLY in mldonkey directory ? ./configure: line 4612: read: read error: 0: Bad file descriptor Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_mld onkey/work/mldonkey-2.8.5" && ./configure --prefix=/opt/local " returned error 1 Command output: -------------------------------- Checking system tools. -------------------------------- checking for ranlib... ranlib checking for gmake... gmake checking for make... (cached) gmake checking if gmake is GNU make ... yes checking for bzip2... bzip2 checking for gzip... (cached) bzip2 checking for perl... /opt/local/bin/perl checking for rpmbuild... no checking for rpm... no checking for wget... wget ---------------------------------------- Checking system tools finished. ---------------------------------------- -------------------------------- Checking Ocaml compiler. -------------------------------- checking for ocamlc.opt... /opt/local/bin/ocamlc.opt checking for ocamlc... /opt/local/bin/ocamlc.opt checking for camlp4... /opt/local/bin/camlp4 Need build ******** Objective-Caml 3.09.3 is required ********* ******* Check http://caml.inria.fr/ ******** Do you want this script to try to download and install ocaml LOCALLY in mldonkey directory ? ./configure: line 4612: read: read error: 0: Bad file descriptor Warning: the following items did not execute (for mldonkey): org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. $ Begin forwarded message: > From: Ryan Schmidt > Date: January 4, 2008 5:12:13 PM EST (CA) > To: Charlse Darwin > Cc: Users MacPorts > Subject: Re: sudo port install mldonkey > > Please keep the discussion on the mailing list using Reply All when > you reply. > > On Jan 4, 2008, at 15:55, Charlse Darwin wrote: > >> $ sudo port install mldonkey >> Password: >> ---> Configuring mldonkey >> Error: Target org.macports.configure returned: configure failure: >> shell command " cd "/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_ >> mldonkey/work/mldonkey-2.8.5" && ./configure --prefix=/opt/local " >> returned error 1 >> Command output: >> -------------------------------- >> Checking system tools. >> -------------------------------- >> checking for ranlib... ranlib >> checking for gmake... gmake >> checking for make... (cached) gmake >> checking if gmake is GNU make ... yes >> checking for bzip2... bzip2 >> checking for gzip... (cached) bzip2 >> checking for perl... /opt/local/bin/perl >> checking for rpmbuild... no >> checking for rpm... no >> checking for wget... wget >> ---------------------------------------- >> Checking system tools finished. >> ---------------------------------------- >> >> -------------------------------- >> Checking Ocaml compiler. >> -------------------------------- >> checking for ocamlc.opt... /opt/local/bin/ocamlc.opt >> checking for ocamlc... /opt/local/bin/ocamlc.opt >> checking for camlp4... /opt/local/bin/camlp4 >> Need build >> ******** Objective-Caml 3.09.3 is required ********* >> ******* Check http://caml.inria.fr/ ******** >> Do you want this script to try to download and install ocaml >> LOCALLY in mldonkey directory ? >> ./configure: line 4612: read: read error: 0: Bad file descriptor >> >> Error: Status 1 encountered during processing. >> $ port -q info --version ocaml >> 3.10.0 >> $ > > I agree. I get the same thing. Maybe mldonkey 2.8.5 just does not > work with ocaml 3.10.0 (since it says it needs "3.09.3" (and not > "3.09.3 or later")). You should file a ticket in our issue tracker > and assign it to the maintainer of the mldonkey port. Maybe > updating the port to the current version of mldonkey, 2.9.2, would > help. You could edit the portfile yourself and test whether > updating to 2.9.2 works; if it does, you can attach your diff to > the ticket. > > From macports.users at gmail.com Fri Jan 4 16:13:42 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Fri Jan 4 16:11:43 2008 Subject: sudo port install mldonkey In-Reply-To: <84EB1E79-76EC-4145-94CE-0E67E988FEE5@macports.org> References: <062.eb8a5ba5335bf52b777fe741a23dff2c@macosforge.org> <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> <8190E5C7-3C1B-47D9-9F86-66F872779379@macports.org> <8FE63DDA-6898-4A5B-966A-DABA5755BEAC@gmail.com> <84EB1E79-76EC-4145-94CE-0E67E988FEE5@macports.org> Message-ID: <0C6809F7-8D48-4B67-ABA0-C824ACF6C0D3@gmail.com> I just filled a ticket, I think I also noticed this: ---> Attempting to fetch mldonkey-2.8.5.tar.bz2 from http:// downloads.sourceforge.net/mldonkey % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:01:39 --:--:-- 0 DEBUG: Fetching failed:: server returned nothing (no headers, no data) If you go to you will see that they only have mldonkey-2.9.2.shared.foo.tar.bz2 posted there. Does that tell you anything at all? On Jan 4, 2008, at 5:12 PM, Ryan Schmidt wrote: > Please keep the discussion on the mailing list using Reply All when > you reply. > > On Jan 4, 2008, at 15:55, Charlse Darwin wrote: > >> $ sudo port install mldonkey >> Password: >> ---> Configuring mldonkey >> Error: Target org.macports.configure returned: configure failure: >> shell command " cd "/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_ >> mldonkey/work/mldonkey-2.8.5" && ./configure --prefix=/opt/local " >> returned error 1 >> Command output: >> -------------------------------- >> Checking system tools. >> -------------------------------- >> checking for ranlib... ranlib >> checking for gmake... gmake >> checking for make... (cached) gmake >> checking if gmake is GNU make ... yes >> checking for bzip2... bzip2 >> checking for gzip... (cached) bzip2 >> checking for perl... /opt/local/bin/perl >> checking for rpmbuild... no >> checking for rpm... no >> checking for wget... wget >> ---------------------------------------- >> Checking system tools finished. >> ---------------------------------------- >> >> -------------------------------- >> Checking Ocaml compiler. >> -------------------------------- >> checking for ocamlc.opt... /opt/local/bin/ocamlc.opt >> checking for ocamlc... /opt/local/bin/ocamlc.opt >> checking for camlp4... /opt/local/bin/camlp4 >> Need build >> ******** Objective-Caml 3.09.3 is required ********* >> ******* Check http://caml.inria.fr/ ******** >> Do you want this script to try to download and install ocaml >> LOCALLY in mldonkey directory ? >> ./configure: line 4612: read: read error: 0: Bad file descriptor >> >> Error: Status 1 encountered during processing. >> $ port -q info --version ocaml >> 3.10.0 >> $ > > I agree. I get the same thing. Maybe mldonkey 2.8.5 just does not > work with ocaml 3.10.0 (since it says it needs "3.09.3" (and not > "3.09.3 or later")). You should file a ticket in our issue tracker > and assign it to the maintainer of the mldonkey port. Maybe > updating the port to the current version of mldonkey, 2.9.2, would > help. You could edit the portfile yourself and test whether > updating to 2.9.2 works; if it does, you can attach your diff to > the ticket. > > From wsiegrist at apple.com Fri Jan 4 16:18:13 2008 From: wsiegrist at apple.com (William Siegrist) Date: Fri Jan 4 16:17:39 2008 Subject: sudo port install mldonkey In-Reply-To: <0C6809F7-8D48-4B67-ABA0-C824ACF6C0D3@gmail.com> References: <062.eb8a5ba5335bf52b777fe741a23dff2c@macosforge.org> <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> <8190E5C7-3C1B-47D9-9F86-66F872779379@macports.org> <8FE63DDA-6898-4A5B-966A-DABA5755BEAC@gmail.com> <84EB1E79-76EC-4145-94CE-0E67E988FEE5@macports.org> <0C6809F7-8D48-4B67-ABA0-C824ACF6C0D3@gmail.com> Message-ID: Wrong trac system. That should go here: http://trac.macosforge.org/projects/macports/newticket -Bill On Jan 4, 2008, at 4:13 PM, Charlse Darwin wrote: > I just filled a ticket, I think > > > > I also noticed this: > ---> Attempting to fetch mldonkey-2.8.5.tar.bz2 from http://downloads.sourceforge.net/mldonkey > % Total % Received % Xferd Average Speed Time Time > Time Current > Dload Upload Total Spent > Left Speed > 0 0 0 0 0 0 0 0 --:--:-- 0:01:39 > --:--:-- 0 > DEBUG: Fetching failed:: server returned nothing (no headers, no data) > > If you go to you will > see that they only have mldonkey-2.9.2.shared.foo.tar.bz2 posted > there. Does that tell you anything at all? > > > On Jan 4, 2008, at 5:12 PM, Ryan Schmidt wrote: > >> Please keep the discussion on the mailing list using Reply All when >> you reply. >> >> On Jan 4, 2008, at 15:55, Charlse Darwin wrote: >> >>> $ sudo port install mldonkey >>> Password: >>> ---> Configuring mldonkey >>> Error: Target org.macports.configure returned: configure failure: >>> shell command " cd "/opt/local/var/macports/build/ >>> _opt_local_var_macports_sources_rsync >>> .macports.org_release_ports_net_mldonkey/work/mldonkey-2.8.5" && ./ >>> configure --prefix=/opt/local " returned error 1 >>> Command output: >>> -------------------------------- >>> Checking system tools. >>> -------------------------------- >>> checking for ranlib... ranlib >>> checking for gmake... gmake >>> checking for make... (cached) gmake >>> checking if gmake is GNU make ... yes >>> checking for bzip2... bzip2 >>> checking for gzip... (cached) bzip2 >>> checking for perl... /opt/local/bin/perl >>> checking for rpmbuild... no >>> checking for rpm... no >>> checking for wget... wget >>> ---------------------------------------- >>> Checking system tools finished. >>> ---------------------------------------- >>> >>> -------------------------------- >>> Checking Ocaml compiler. >>> -------------------------------- >>> checking for ocamlc.opt... /opt/local/bin/ocamlc.opt >>> checking for ocamlc... /opt/local/bin/ocamlc.opt >>> checking for camlp4... /opt/local/bin/camlp4 >>> Need build >>> ******** Objective-Caml 3.09.3 is required ********* >>> ******* Check http://caml.inria.fr/ ******** >>> Do you want this script to try to download and install ocaml >>> LOCALLY in mldonkey directory ? >>> ./configure: line 4612: read: read error: 0: Bad file descriptor >>> >>> Error: Status 1 encountered during processing. >>> $ port -q info --version ocaml >>> 3.10.0 >>> $ >> >> I agree. I get the same thing. Maybe mldonkey 2.8.5 just does not >> work with ocaml 3.10.0 (since it says it needs "3.09.3" (and not >> "3.09.3 or later")). You should file a ticket in our issue tracker >> and assign it to the maintainer of the mldonkey port. Maybe >> updating the port to the current version of mldonkey, 2.9.2, would >> help. You could edit the portfile yourself and test whether >> updating to 2.9.2 works; if it does, you can attach your diff to >> the ticket. >> >> > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users ---- William Siegrist Software Support Engineer Mac OS Forge http://macosforge.org/ wsiegrist@apple.com 408 862 7337 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2421 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080104/69b308f6/smime.bin From macports.users at gmail.com Fri Jan 4 16:23:40 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Fri Jan 4 16:21:43 2008 Subject: sudo port install mldonkey In-Reply-To: References: <062.eb8a5ba5335bf52b777fe741a23dff2c@macosforge.org> <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> <8190E5C7-3C1B-47D9-9F86-66F872779379@macports.org> <8FE63DDA-6898-4A5B-966A-DABA5755BEAC@gmail.com> <84EB1E79-76EC-4145-94CE-0E67E988FEE5@macports.org> <0C6809F7-8D48-4B67-ABA0-C824ACF6C0D3@gmail.com> Message-ID: feed://trac.macosforge.org/projects/macports/ticket/13829?format=rss On Jan 4, 2008, at 7:18 PM, William Siegrist wrote: > Wrong trac system. That should go here: > > http://trac.macosforge.org/projects/macports/newticket > > > -Bill > > On Jan 4, 2008, at 4:13 PM, Charlse Darwin wrote: > >> I just filled a ticket, I think >> >> >> >> I also noticed this: >> ---> Attempting to fetch mldonkey-2.8.5.tar.bz2 from http:// >> downloads.sourceforge.net/mldonkey >> % Total % Received % Xferd Average Speed Time Time >> Time Current >> Dload Upload Total Spent >> Left Speed >> 0 0 0 0 0 0 0 0 --:--:-- 0:01:39 >> --:--:-- 0 >> DEBUG: Fetching failed:: server returned nothing (no headers, no >> data) >> >> If you go to you will >> see that they only have mldonkey-2.9.2.shared.foo.tar.bz2 posted >> there. Does that tell you anything at all? >> >> >> On Jan 4, 2008, at 5:12 PM, Ryan Schmidt wrote: >> >>> Please keep the discussion on the mailing list using Reply All >>> when you reply. >>> >>> On Jan 4, 2008, at 15:55, Charlse Darwin wrote: >>> >>>> $ sudo port install mldonkey >>>> Password: >>>> ---> Configuring mldonkey >>>> Error: Target org.macports.configure returned: configure >>>> failure: shell command " cd "/opt/local/var/macports/build/ >>>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_ne >>>> t_mldonkey/work/mldonkey-2.8.5" && ./configure --prefix=/opt/ >>>> local " returned error 1 >>>> Command output: >>>> -------------------------------- >>>> Checking system tools. >>>> -------------------------------- >>>> checking for ranlib... ranlib >>>> checking for gmake... gmake >>>> checking for make... (cached) gmake >>>> checking if gmake is GNU make ... yes >>>> checking for bzip2... bzip2 >>>> checking for gzip... (cached) bzip2 >>>> checking for perl... /opt/local/bin/perl >>>> checking for rpmbuild... no >>>> checking for rpm... no >>>> checking for wget... wget >>>> ---------------------------------------- >>>> Checking system tools finished. >>>> ---------------------------------------- >>>> >>>> -------------------------------- >>>> Checking Ocaml compiler. >>>> -------------------------------- >>>> checking for ocamlc.opt... /opt/local/bin/ocamlc.opt >>>> checking for ocamlc... /opt/local/bin/ocamlc.opt >>>> checking for camlp4... /opt/local/bin/camlp4 >>>> Need build >>>> ******** Objective-Caml 3.09.3 is required ********* >>>> ******* Check http://caml.inria.fr/ ******** >>>> Do you want this script to try to download and install ocaml >>>> LOCALLY in mldonkey directory ? >>>> ./configure: line 4612: read: read error: 0: Bad file descriptor >>>> >>>> Error: Status 1 encountered during processing. >>>> $ port -q info --version ocaml >>>> 3.10.0 >>>> $ >>> >>> I agree. I get the same thing. Maybe mldonkey 2.8.5 just does not >>> work with ocaml 3.10.0 (since it says it needs "3.09.3" (and not >>> "3.09.3 or later")). You should file a ticket in our issue >>> tracker and assign it to the maintainer of the mldonkey port. >>> Maybe updating the port to the current version of mldonkey, >>> 2.9.2, would help. You could edit the portfile yourself and test >>> whether updating to 2.9.2 works; if it does, you can attach your >>> diff to the ticket. >>> >>> >> >> _______________________________________________ >> macports-users mailing list >> macports-users@lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo/macports-users > > > > > ---- > William Siegrist > Software Support Engineer > Mac OS Forge > http://macosforge.org/ > wsiegrist@apple.com > 408 862 7337 > > > > > From tabithamc at gmail.com Fri Jan 4 17:29:42 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Fri Jan 4 17:27:39 2008 Subject: Underscores in some directory user, group names (Postfix MacPort example) Message-ID: <7fccb3000801041729t2b45fc10qbd783220da57a6f@mail.gmail.com> Hello all -- I just installed the current version of the Postfix port (version 2.4.6) on a Leopard Server system. After the install, I noticed a username and group name of "_postfix" and "_postdrop" respectively, as in: drwx--x--- 2 _postfix _postdrop 102 Jan 4 23:06 public/ drwx-wx--- 2 _postfix _postdrop 102 Jan 4 23:06 maildrop/ This differs from previous Postfix port installations (UID 27 was "postfix" not "_postfix"). This isn't really a MacPorts specific issue but I'm wondering if anyone knows why Apple changed their naming schema on Leopard, for short names such as: from "postfix" to "_postfix" ? I wonder if this has something to do with becoming fully UNIX compliant? POSIX? Mr. Jordan Hubbard, can you offer some wisdom and perspective on this subject? Thank you, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080104/f86cc052/attachment.html From jkh at apple.com Fri Jan 4 17:46:57 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Fri Jan 4 17:45:53 2008 Subject: Underscores in some directory user, group names (Postfix MacPort example) In-Reply-To: <7fccb3000801041729t2b45fc10qbd783220da57a6f@mail.gmail.com> References: <7fccb3000801041729t2b45fc10qbd783220da57a6f@mail.gmail.com> Message-ID: This is because the original designers of Unix neglected to take into account the notion of user namespaces - the namespace is flat. That means that system or role specific names can conflict with names that users would like to use for themselves (c.f. "admin" or "operator") unless you adopt a convention for keeping them separate. That convention is the prefix underscore. - Jordan On Jan 4, 2008, at 5:29 PM, Tabitha McNerney wrote: > Hello all -- > > I just installed the current version of the Postfix port (version > 2.4.6) on a Leopard Server system. > > After the install, I noticed a username and group name of "_postfix" > and "_postdrop" respectively, as in: > drwx--x--- 2 _postfix _postdrop 102 Jan 4 23:06 public/ > drwx-wx--- 2 _postfix _postdrop 102 Jan 4 23:06 maildrop/ > This differs from previous Postfix port installations (UID 27 was > "postfix" not "_postfix"). This isn't really a MacPorts specific > issue but I'm wondering if anyone knows why Apple changed their > naming schema on Leopard, for short names such as: > > from "postfix" to "_postfix" > > ? > > I wonder if this has something to do with becoming fully UNIX > compliant? POSIX? > > Mr. Jordan Hubbard, can you offer some wisdom and perspective on > this subject? > > Thank you, > > T.M. > From boeyms at macports.org Fri Jan 4 18:12:49 2008 From: boeyms at macports.org (Boey Maun Suang) Date: Fri Jan 4 18:10:44 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> Message-ID: <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> Hi Chris, [snip] >> 10. At the command line, you should now find that, when run on any >> portname (e.g. xmlcatmgr) the "port info " and "port install >> " commands fail with >> >> Error: Unable to open port: invalid command name "ui_channels" >> >> However, you should find that "port search " works >> fine. >> (In general, it appears to me that the port commands that fail with >> the above message are the ones for which the "port" command attempts >> to open a Portfile.) > > Yes. That is exactly what I see now. > > Next steps? Thank you so much for testing this. Next steps, unfortunately, are in the hands of the developers to try to work out why we're getting this error, and then how to fix it. If you think that you might be able to help with figuring out what is going wrong in the core MacPorts code, that would be great. Otherwise, I'm afraid you'll have to sit tight until we can give you a fix to test. Of course, if you have any suggestions or questions, or notice anything further, we'd be most happy to hear from you. I'm sorry that I can't be more helpful; my understanding of the core MacPorts code just isn't good enough yet to be able to propose any immediate fixes. I hope that we can get this done for you as soon as we can. Once again, thank you for your help so far. Kind regards, Maun Suang -- Boey Maun Suang Email: boeyms@macports.org From ryandesign at macports.org Fri Jan 4 18:33:08 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri Jan 4 22:31:35 2008 Subject: sudo port install mldonkey In-Reply-To: <0C6809F7-8D48-4B67-ABA0-C824ACF6C0D3@gmail.com> References: <062.eb8a5ba5335bf52b777fe741a23dff2c@macosforge.org> <5D51C848-B4B6-4862-894A-5C84027E40F8@gmail.com> <8190E5C7-3C1B-47D9-9F86-66F872779379@macports.org> <8FE63DDA-6898-4A5B-966A-DABA5755BEAC@gmail.com> <84EB1E79-76EC-4145-94CE-0E67E988FEE5@macports.org> <0C6809F7-8D48-4B67-ABA0-C824ACF6C0D3@gmail.com> Message-ID: You filed it in Edgewall's Trac issue tracker. You need to file it in MacPorts's Trac issue tracker. On Jan 4, 2008, at 18:13, Charlse Darwin wrote: > I just filled a ticket, I think > > > > I also noticed this: > ---> Attempting to fetch mldonkey-2.8.5.tar.bz2 from http:// > downloads.sourceforge.net/mldonkey > % Total % Received % Xferd Average Speed Time Time > Time Current > Dload Upload Total Spent > Left Speed > 0 0 0 0 0 0 0 0 --:--:-- 0:01:39 > --:--:-- 0 > DEBUG: Fetching failed:: server returned nothing (no headers, no data) > > If you go to you will > see that they only have mldonkey-2.9.2.shared.foo.tar.bz2 posted > there. Does that tell you anything at all? > > > On Jan 4, 2008, at 5:12 PM, Ryan Schmidt wrote: > >> Please keep the discussion on the mailing list using Reply All >> when you reply. >> >> On Jan 4, 2008, at 15:55, Charlse Darwin wrote: >> >>> $ sudo port install mldonkey >>> Password: >>> ---> Configuring mldonkey >>> Error: Target org.macports.configure returned: configure failure: >>> shell command " cd "/opt/local/var/macports/build/ >>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_net >>> _mldonkey/work/mldonkey-2.8.5" && ./configure --prefix=/opt/local >>> " returned error 1 >>> Command output: >>> -------------------------------- >>> Checking system tools. >>> -------------------------------- >>> checking for ranlib... ranlib >>> checking for gmake... gmake >>> checking for make... (cached) gmake >>> checking if gmake is GNU make ... yes >>> checking for bzip2... bzip2 >>> checking for gzip... (cached) bzip2 >>> checking for perl... /opt/local/bin/perl >>> checking for rpmbuild... no >>> checking for rpm... no >>> checking for wget... wget >>> ---------------------------------------- >>> Checking system tools finished. >>> ---------------------------------------- >>> >>> -------------------------------- >>> Checking Ocaml compiler. >>> -------------------------------- >>> checking for ocamlc.opt... /opt/local/bin/ocamlc.opt >>> checking for ocamlc... /opt/local/bin/ocamlc.opt >>> checking for camlp4... /opt/local/bin/camlp4 >>> Need build >>> ******** Objective-Caml 3.09.3 is required ********* >>> ******* Check http://caml.inria.fr/ ******** >>> Do you want this script to try to download and install ocaml >>> LOCALLY in mldonkey directory ? >>> ./configure: line 4612: read: read error: 0: Bad file descriptor >>> >>> Error: Status 1 encountered during processing. >>> $ port -q info --version ocaml >>> 3.10.0 >>> $ >> >> I agree. I get the same thing. Maybe mldonkey 2.8.5 just does not >> work with ocaml 3.10.0 (since it says it needs "3.09.3" (and not >> "3.09.3 or later")). You should file a ticket in our issue tracker >> and assign it to the maintainer of the mldonkey port. Maybe >> updating the port to the current version of mldonkey, 2.9.2, would >> help. You could edit the portfile yourself and test whether >> updating to 2.9.2 works; if it does, you can attach your diff to >> the ticket. From ryandesign at macports.org Fri Jan 4 21:32:12 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri Jan 4 22:31:37 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> Message-ID: <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> On Jan 4, 2008, at 20:12, Boey Maun Suang wrote: >>> 10. At the command line, you should now find that, when run on any >>> portname (e.g. xmlcatmgr) the "port info " and "port >>> install >>> " commands fail with >>> >>> Error: Unable to open port: invalid command name "ui_channels" >>> >>> However, you should find that "port search " works >>> fine. >>> (In general, it appears to me that the port commands that fail with >>> the above message are the ones for which the "port" command attempts >>> to open a Portfile.) >> >> Yes. That is exactly what I see now. >> >> Next steps? > > Thank you so much for testing this. Next steps, unfortunately, are > in the > hands of the developers to try to work out why we're getting this > error, > and then how to fix it. If you think that you might be able to > help with > figuring out what is going wrong in the core MacPorts code, that > would be > great. Otherwise, I'm afraid you'll have to sit tight until we can > give > you a fix to test. Of course, if you have any suggestions or > questions, > or notice anything further, we'd be most happy to hear from you. > > I'm sorry that I can't be more helpful; my understanding of the core > MacPorts code just isn't good enough yet to be able to propose any > immediate fixes. I hope that we can get this done for you as soon > as we > can. Maybe this changeset is related to the problem? http://trac.macports.org/projects/macports/changeset/29498 From eridius at macports.org Sat Jan 5 00:19:18 2008 From: eridius at macports.org (Kevin Ballard) Date: Sat Jan 5 00:17:14 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> Message-ID: If this problem is related to that commit and 10.3, then the only thing I can think of is that Mac OS X 10.3 included a broken version of tclsh, but that doesn't seem too plausible. I can't think of any reason for this error to only affect commands that open Portfiles. -Kevin Ballard On Jan 5, 2008, at 12:32 AM, Ryan Schmidt wrote: > On Jan 4, 2008, at 20:12, Boey Maun Suang wrote: > >>>> 10. At the command line, you should now find that, when run on any >>>> portname (e.g. xmlcatmgr) the "port info " and "port >>>> install >>>> " commands fail with >>>> >>>> Error: Unable to open port: invalid command name "ui_channels" >>>> >>>> However, you should find that "port search " works >>>> fine. >>>> (In general, it appears to me that the port commands that fail with >>>> the above message are the ones for which the "port" command >>>> attempts >>>> to open a Portfile.) >>> >>> Yes. That is exactly what I see now. >>> >>> Next steps? >> >> Thank you so much for testing this. Next steps, unfortunately, are >> in the >> hands of the developers to try to work out why we're getting this >> error, >> and then how to fix it. If you think that you might be able to >> help with >> figuring out what is going wrong in the core MacPorts code, that >> would be >> great. Otherwise, I'm afraid you'll have to sit tight until we can >> give >> you a fix to test. Of course, if you have any suggestions or >> questions, >> or notice anything further, we'd be most happy to hear from you. >> >> I'm sorry that I can't be more helpful; my understanding of the core >> MacPorts code just isn't good enough yet to be able to propose any >> immediate fixes. I hope that we can get this done for you as soon >> as we >> can. > > Maybe this changeset is related to the problem? > > http://trac.macports.org/projects/macports/changeset/29498 > -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com From tabithamc at gmail.com Sat Jan 5 02:05:23 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sat Jan 5 02:03:18 2008 Subject: Underscores in some directory user, group names (Postfix MacPort example) In-Reply-To: References: <7fccb3000801041729t2b45fc10qbd783220da57a6f@mail.gmail.com> Message-ID: <7fccb3000801050205h27b0bf34p52b404f3adac5871@mail.gmail.com> On 1/4/08, Jordan K. Hubbard wrote: > > This is because the original designers of Unix neglected to take into > account the notion of user namespaces - the namespace is flat. That > means that system or role specific names can conflict with names that > users would like to use for themselves (c.f. "admin" or "operator") > unless you adopt a convention for keeping them separate. That > convention is the prefix underscore. > > - Jordan Jordan, Thank you very much. Makes perfect sense. Its hard to find fault with the original designers of Unix (they probably never would have guessed, decades later, that individuals in the comfort of their own homes would run Unix on a machine that sits in their lap)! Best, T.M. On Jan 4, 2008, at 5:29 PM, Tabitha McNerney wrote: > > > Hello all -- > > > > I just installed the current version of the Postfix port (version > > 2.4.6) on a Leopard Server system. > > > > After the install, I noticed a username and group name of "_postfix" > > and "_postdrop" respectively, as in: > > drwx--x--- 2 _postfix _postdrop 102 Jan 4 23:06 public/ > > drwx-wx--- 2 _postfix _postdrop 102 Jan 4 23:06 maildrop/ > > This differs from previous Postfix port installations (UID 27 was > > "postfix" not "_postfix"). This isn't really a MacPorts specific > > issue but I'm wondering if anyone knows why Apple changed their > > naming schema on Leopard, for short names such as: > > > > from "postfix" to "_postfix" > > > > ? > > > > I wonder if this has something to do with becoming fully UNIX > > compliant? POSIX? > > > > Mr. Jordan Hubbard, can you offer some wisdom and perspective on > > this subject? > > > > Thank you, > > > > T.M. > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080105/3beb0d12/attachment.html From face at CentosPrime.COM Sat Jan 5 02:43:36 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sat Jan 5 02:41:42 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> Message-ID: <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> On 2008-01-05 , at 01:19 , Kevin Ballard wrote: > If this problem is related to that commit and 10.3, then the only > thing I can think of is that Mac OS X 10.3 included a broken > version of tclsh, but that doesn't seem too plausible. > > I can't think of any reason for this error to only affect commands > that open Portfiles. Anything I can do to help track down what is going wrong? The "version" of tclsh on 10.3 appears just like 10.4 and 10.5 - a symbolic link to tclsh8.4 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From daniel at danieloberhoff.de Sat Jan 5 03:18:26 2008 From: daniel at danieloberhoff.de (Daniel Oberhoff) Date: Sat Jan 5 03:16:41 2008 Subject: mozilla-dev fails to build In-Reply-To: <3B479A6D-60D0-492F-9902-819105BC7496@danieloberhoff.de> References: <20071219085002.93FEF16F377@lists.macosforge.org> <4C81E39B-20D8-49D4-AEE1-54DCC39B23E9@danieloberhoff.de> <8094A635-A854-4A99-9BAC-9FA43152F06A@macports.org> <3B479A6D-60D0-492F-9902-819105BC7496@danieloberhoff.de> Message-ID: Ok, I rebuilt now, and still get the same set of errors. Am 30.12.2007 um 01:58 schrieb Daniel Oberhoff: > Hi, > > Ok, yes, I had lots of those darwin_8 thingies. While deinstalling > openssl macports just broke (it seems the whole ports system > depended on openssl) so now I had to shoot it and reinstall, and > lost interest along the way :o (other things where more interesting > ^^). Anyhow, I wanted the mozilla-dev to build the mugshot tracker, > for which there is no osx version yet, and it uses gecko-sdk, which > again bases on the mozilla-sdk. > Once I get back on track with this I will update here if it works. > > Best > > Daniel > > Am 28.12.2007 um 16:44 schrieb Ryan Schmidt: > >> On Dec 28, 2007, at 02:08, Daniel Oberhoff wrote: >> >>> I can't get mozilla-dev built. It gives lots and lots of errors. I >>> started fixing some, but after an while I kinda though I'd first >>> ask if anyone has succeeded with it before, so that maybe it's >>> just a local misconfiguration. Among the things I fixed so far are: >>> >>> 1) some of the headers of the package confuse signal.h (they >>> #define some things that mess up signal.h) so I had to move >>> signal.h to the top of the include list in those cases. >>> >>> 2) the interface to freetype is broken. the mozilla-dev uses >>> funtion pointers with non-const arguments, while ft2 seems to >>> expect them to be with const arguments (moveto, lineto, >>> cubicto...), so I added const qualifiers in the correesponding >>> function declarations. >>> >>> another thing I didn't fix yet is NSOID being undefined in lots of >>> places. I just couldn't find where it is defined. This only shows >>> btw. when there is an array of NSOID defined. The compiler merilly >>> compiles pointer statements (NSOID *). >>> >>> My system is osx leopard on a core2duo mbp. I took over the >>> macports tree from my tiger installation, but that had no >>> problems...so far :). I recently did selfupdate (to 1.6) and >>> upgrade outdated successfully. >> >> mozilla and mozilla-devel ports are not being maintained, and >> appear to be old. Why do you want to install mozilla 1.8b1? >> >> Migrating a MacPorts tree from Tiger to Leopard (or across any >> major OS release version, or from one architecture processor to >> another) can be problematic. In the case of moving from Tiger to >> Leopard, you probably still have a lot of ports installed that have >> the "darwin_8" variant. Examine "port installed" to see. You should >> forcibly uninstall each of those (sudo port -f uninstall foo) >> (making note of which other variants you selected), then reinstall >> them (sudo port install foo +whatever), so they lose the now- >> inappropriate darwin_8 variant and gain (if necessary) the darwin_9 >> variant. >> > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users From jochen at fhi-berlin.mpg.de Sat Jan 5 04:40:48 2008 From: jochen at fhi-berlin.mpg.de (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Sat Jan 5 04:38:58 2008 Subject: Qt4.3.3 crashs with -system-sqlite In-Reply-To: References: <193EC6E6-2B6D-406A-97B6-F40FABC6CFD5@fhi-berlin.mpg.de> Message-ID: Dear MacPort users, this is an Email to qt-interest due to problems of sqlite support in Qt4 using macPorts' sqlite3 port. See the end for macPorts-specific questions, please. On 05.01.2008, at 10:46, Dimitri wrote: >> I am the MacPorts (www.macports.org) maintainer of Qt4 for Mac OS X. > > I understand this MacPort is a binary package for MacOS made from a > vanilla Qt/Mac source package. Is that correct? Yes. However, we do (yet) not distribute binary packages but "recipes" to build them on the destination machine. When executed the qt4-mac Portfile (recipe) downloads the source from TrollTech and builds it.. > By the way, you shouldn't have to force: > -largefile > -stl > > You definitely shouldn't need: > -no-nis > -no-cups > These are Qt/X11 only. Okay, but thet should not hurd, I guess. >> We are having some problems with sqlite support when using the >> system-sqlite (sqlite 3.5.4), i.e., calls to sqlite3_set_auxdata >> fail (confirmed, for example, for sqliteman and the books demo of >> Qt4). >> [...] >> Starting the books demo gives the following backtrace: >> [...] >> Exception Type: EXC_BAD_ACCESS (SIGBUS) >> Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000003d >> Crashed Thread: 0 >> Thread 0 Crashed: >> 0 libsqlite3.0.dylib 0x95f0a56e >> sqlite3_set_auxdata + 6062 >> 1 libsqlite3.0.dylib 0x95f380b2 >> sqlite3RegisterBuiltinFunctions + 178 >> 2 libsqlite3.0.dylib 0x010d2f41 openDatabase + 961 >> 3 libsqlite3.0.dylib 0x010d3033 sqlite3_open16 + 131 >> 4 libqsqlite.dylib 0x010a6124 [...] > > This could as well be an issue with SQLite. It would be interesting > to see how the system SQLite library itself has been built. It's build using this Portfile http://trac.macports.org/projects/macports/browser/trunk/dports/databases/sqlite3/Portfile > What are the arguments passed to sqlite3_open16? It would be worth > writing a non-Qt program and passing the same arguments to > sqlite3_open16. Does it also crash? For the books example this should be the call from within Qt's bool QSQLiteDriver::open(const QString & db, const QString &, const QString &, const QString &, int, const QString &conOpts) which is this: if (sqlite3_open16(db.constData(), &d->access) == SQLITE_OK) { We get there from books.app QSqlError initDb() which contains QSqlDatabase db = QSqlDatabase::addDatabase("QSQLITE"); ... MacPorts question: Are people successfully using MacPorts' sqlite3 port? Are you using the functions in question? sqlite3_open16 sqlite3_set_auxdata Are there any known issues with these functions on Mac OS X or in MacPorts? Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll From macports.users at gmail.com Sat Jan 5 05:46:00 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Sat Jan 5 05:44:11 2008 Subject: Fwd: [MacPorts] #13829: sudo port -fvd install mldonkey References: <063.388a75ac9344036e2f45702b2dd56baa@macosforge.org> Message-ID: `Assign to maintainer'? You mean pguyot@kallisys.net? Begin forwarded message: > From: "MacPorts" > Date: January 5, 2008 12:02:40 AM EST (CA) > To: macports.users@gmail.com, pguyot@kallisys.net > Cc: macports-tickets@lists.macosforge.org > Subject: Re: [MacPorts] #13829: sudo port -fvd install mldonkey > Reply-To: noreply@macosforge.org > > #13829: sudo port -fvd install mldonkey > --------------------------------------- > +------------------------------------ > Reporter: macports.users@gmail.com | Owner: > pguyot@kallisys.net > Type: defect | Status: new > Priority: Normal | Milestone: Port Bugs > Component: ports | Version: 1.6.0 > Resolution: | Keywords: > --------------------------------------- > +------------------------------------ > Changes (by ryandesign@macports.org): > > * owner: macports-tickets@lists.macosforge.org => > pguyot@kallisys.net > * milestone: => Port Bugs > > Comment: > > Assign to maintainer > > -- > Ticket URL: 13829#comment:1> > MacPorts > Ports system for Mac OS From mikev at geo.umass.edu Sat Jan 5 09:30:45 2008 From: mikev at geo.umass.edu (Michael J. Vollinger) Date: Sat Jan 5 09:28:42 2008 Subject: abiword issues Message-ID: <46A9249B-2C4E-40B1-A9DA-FEF6FD85B395@geo.umass.edu> Hello all, Can anyone help me with some Abiword issues I am having? I tried to install abiword-x11 and long list of error messages. Can be viewed at http://www.nabble.com/abiword-x11-issues-to14518635.html#a14518635 After that I tried installing the other abiword package, version 2.4.5_0 and it says it installed. The problem I am having now is I can not start the program. When I open a xterm window and type abiword I get the error message: bash: abiword: command not found. Am I doing anything wrong? Help help would be looked upon kindly with any version of abiword. Mike -------------------------- Michael J. Vollinger Research Assistant Ronald B. Gilmore XRF Lab Dept. of Geosciences 611 North Pleasant Street University of Massachusetts Amherst, MA 01003 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080105/cf11846f/attachment.html From rowue at digitalis.org Sat Jan 5 09:35:33 2008 From: rowue at digitalis.org (=?ISO-8859-1?Q?Rolf_W=FCrdemann?=) Date: Sat Jan 5 09:33:22 2008 Subject: Can someone commit? (gtkglext, gwyddion, qucs) Message-ID: First: #13624 (http://trac.macosforge.org/projects/macports/ticket/13624) (Update of the Portfile for gtkglext, so it runs on Leopard also) after that: #13737 (http://trac.macosforge.org/projects/macports/ticket/13737) (Update of gwyddion, so gwyddion works on leoparf also (depend on #13624) If this both updates are commited, tickets: #13560 (http://trac.macosforge.org/projects/macports/ticket/13560) and #13517 (http://trac.macosforge.org/projects/macports/ticket/13517) can also be closed (dealing with same issues, so no commits of them please;) if you have some spare time after this, it would be fine to commit #13826 (http://trac.macosforge.org/projects/macports/ticket/13826) which is an update of qucs to 0.0.13 ;) If there is anything whch denies to Portfiles from getting committed, please let me know ;) Reg's Rolf -- Security is an illusion - Datasecurity twice Rolf W?rdemann - private: rowue@digitalis.org - office: rowue@crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue@digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Signierter Teil der Nachricht Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080105/cb5d18af/PGP.bin From mta at umich.edu Sat Jan 5 10:03:34 2008 From: mta at umich.edu (Mike Alexander) Date: Sat Jan 5 10:01:35 2008 Subject: Guile 1.8 port and Gnucash Message-ID: I discovered that there is a problem with the Guile 1.8 port. It includes a patch left over from the 1.6 version which is no longer relevant (and which causes problems) in version 1.8. It also fails to add some symlinks that are needed to make it work with Gnucash. I've attached a patch that fixes this (and adds a +debug variant). With these changes the current SVN version of Gnucash works with Guile 1.8. I haven't tried it with the Macports version of Gnucash, but it might work too. After applying the Portfile patch, the file patch-slib.scm is no longer needed and could be deleted. I'm not currently getting messages from the list since I'm on the road and trying to cut down on EMail, so reply directly if you need to contact me about this. -- Mike Alexander mta@umich.edu Ann Arbor, MI PGP key ID: BEA343A6 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-patch Size: 1026 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080105/ca0ec35d/attachment-0001.bin From ram at macports.org Sat Jan 5 11:09:47 2008 From: ram at macports.org (Adam Mercer) Date: Sat Jan 5 11:07:40 2008 Subject: g95-0.90_2 Intel Leopard build error Message-ID: <799406d60801051109w4a99e22an6072f6704e73729c@mail.gmail.com> Hi I'm having a problem building g95-0.90_2 on Intel Leopard, I get the following error: Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/g95-0.90" && make all " returned error 2 Command output: /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/gcc.h:45:1: warning: this is the location of the previous definition gawk -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opt-functions.awk \ -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opt-gather.awk \ /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/common.opt lang.opt > options.tmp gawk -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opt-functions.awk \ -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/optc-gen.awk options.tmp > options.c gawk -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opt-functions.awk \ -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opth-gen.awk options.tmp > options.h /usr/bin/gcc-4.0 -c -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -I. -I- -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/config -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/libcpp/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc -I/opt/local/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/intl -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/intl /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opts.c cc1: note: obsolete option -I- used, please use -iquote instead /usr/bin/gcc-4.0 -c -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -I. -I- -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/config -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/libcpp/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc -I/opt/local/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/intl -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/intl options.c cc1: note: obsolete option -I- used, please use -iquote instead /usr/bin/gcc-4.0 -c -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -DTARGET_NAME=\"i386-apple-darwin9.1.0\" -DSTANDARD_EXEC_PREFIX=\"/opt/local/lib/gcc-lib/i386-apple-darwin9.1.0/4.0.3\" -DTARGET_SYSTEM_ROOT=\"\" -DDEFAULT_TARGET_VERSION=\"\" -DDEFAULT_TARGET_MACHINE=\"\" -DTOOLDIR_BASE_PREFIX=\"\" -DSTANDARD_STARTFILE_PREFIX=\"\" -DSTANDARD_STARTFILE_PREFIX_2=\"/usr/lib/\" -DSTANDARD_EXEC_PREFIX=\"/opt/local/lib/gcc-lib/i386-apple-darwin9.1.0/4.0.3\" -DSTANDARD_BINDIR_PREFIX=\"/opt/local/bin\" -DSTANDARD_LIBEXEC_PREFIX=\"/opt/local/lib/gcc-lib/i386-apple-darwin9.1.0/4.0.3\" -DG95_SPEC=\"\" -I. -I- -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/config -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/libcpp/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc -I/opt/local/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/intl -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/intl /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/gcc.c cc1: note: obsolete option -I- used, please use -iquote instead echo "const char version_string[] = \"`cat gcc_version` (g95 0.90!) \" __DATE__;" > version.c echo 'const char bug_report_url[] = "http://www.g95.org or mail andyv@firstinter.net";' >> version.c /usr/bin/gcc-4.0 -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -c version.c /usr/bin/gcc-4.0 -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -L/opt/local/lib -o g95 g95-g95spec.o /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc/prefix.o gcc.o version.o /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc/intl.o /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/libiberty/libiberty.a /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/intl/libintl.a -liconv Undefined symbols: "_iconv", referenced from: __nl_find_msg in libintl.a(dcigettext.o) "_iconv_open", referenced from: __nl_init_domain_conv in libintl.a(loadmsgcat.o) __nl_init_domain_conv in libintl.a(loadmsgcat.o) "_iconv_close", referenced from: __nl_free_domain_conv in libintl.a(loadmsgcat.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[1]: *** [g95] Error 1 make: *** [all] Error 2 Warning: the following items did not execute (for g95): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. Any ideas? Cheers Adam From mbthorn at gmail.com Sat Jan 5 11:34:17 2008 From: mbthorn at gmail.com (Mike) Date: Sat Jan 5 11:32:15 2008 Subject: Can someone commit? (gtkglext, gwyddion, qucs) In-Reply-To: References: Message-ID: I second this! thanks, mike On Jan 5, 2008, at 12:35 PM, Rolf W?rdemann wrote: > First: > > #13624 (http://trac.macosforge.org/projects/macports/ticket/13624) > > (Update of the Portfile for gtkglext, so it runs on Leopard also) > > after that: > > #13737 (http://trac.macosforge.org/projects/macports/ticket/13737) > > (Update of gwyddion, so gwyddion works on leoparf also (depend on > #13624) > > If this both updates are commited, tickets: > > #13560 (http://trac.macosforge.org/projects/macports/ticket/13560) > and > #13517 (http://trac.macosforge.org/projects/macports/ticket/13517) > > can also be closed (dealing with same issues, so no commits of them > please;) > > if you have some spare time after this, it would be fine to commit > > #13826 (http://trac.macosforge.org/projects/macports/ticket/13826) > > which is an update of qucs to 0.0.13 ;) > > If there is anything whch denies to Portfiles from getting committed, > please let me know ;) > > Reg's > > Rolf > -- > Security is an illusion - Datasecurity twice > Rolf W?rdemann - private: rowue@digitalis.org - office: rowue@crew-gmbh.de > GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 > 67F0 D02F > jabber: rowue@digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF > 53C3E932 > > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users From ryandesign at macports.org Sat Jan 5 11:59:56 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 11:58:23 2008 Subject: mozilla-dev fails to build In-Reply-To: References: <20071219085002.93FEF16F377@lists.macosforge.org> <4C81E39B-20D8-49D4-AEE1-54DCC39B23E9@danieloberhoff.de> <8094A635-A854-4A99-9BAC-9FA43152F06A@macports.org> <3B479A6D-60D0-492F-9902-819105BC7496@danieloberhoff.de> Message-ID: <5631063A-600C-4634-A68E-B6559EA24AF3@macports.org> On Jan 5, 2008, at 05:16, Daniel Oberhoff wrote: > Ok, I rebuilt now, Ok, good, that should ensure that you avoid some unexpected errors. > and still get the same set of errors. The errors you're seeing with the mozilla ports are, however, probably expected. Like I said, they're old and not maintained, so I'm not surprised they're broken. Apparently nobody else here has been interested enough in these ports to get them working again. If you're interested in these ports, you could see if you can figure out why they fail, and fix them. > Am 30.12.2007 um 01:58 schrieb Daniel Oberhoff: > >> Hi, >> >> Ok, yes, I had lots of those darwin_8 thingies. While deinstalling >> openssl macports just broke (it seems the whole ports system >> depended on openssl) so now I had to shoot it and reinstall, and >> lost interest along the way :o (other things where more >> interesting ^^). Anyhow, I wanted the mozilla-dev to build the >> mugshot tracker, for which there is no osx version yet, and it >> uses gecko-sdk, which again bases on the mozilla-sdk. >> Once I get back on track with this I will update here if it works. >> >> Best >> >> Daniel >> >> Am 28.12.2007 um 16:44 schrieb Ryan Schmidt: >> >>> On Dec 28, 2007, at 02:08, Daniel Oberhoff wrote: >>> >>>> I can't get mozilla-dev built. It gives lots and lots of errors. >>>> I started fixing some, but after an while I kinda though I'd >>>> first ask if anyone has succeeded with it before, so that maybe >>>> it's just a local misconfiguration. Among the things I fixed so >>>> far are: >>>> >>>> 1) some of the headers of the package confuse signal.h (they >>>> #define some things that mess up signal.h) so I had to move >>>> signal.h to the top of the include list in those cases. >>>> >>>> 2) the interface to freetype is broken. the mozilla-dev uses >>>> funtion pointers with non-const arguments, while ft2 seems to >>>> expect them to be with const arguments (moveto, lineto, >>>> cubicto...), so I added const qualifiers in the correesponding >>>> function declarations. >>>> >>>> another thing I didn't fix yet is NSOID being undefined in lots >>>> of places. I just couldn't find where it is defined. This only >>>> shows btw. when there is an array of NSOID defined. The compiler >>>> merilly compiles pointer statements (NSOID *). >>>> >>>> My system is osx leopard on a core2duo mbp. I took over the >>>> macports tree from my tiger installation, but that had no >>>> problems...so far :). I recently did selfupdate (to 1.6) and >>>> upgrade outdated successfully. >>> >>> mozilla and mozilla-devel ports are not being maintained, and >>> appear to be old. Why do you want to install mozilla 1.8b1? >>> >>> Migrating a MacPorts tree from Tiger to Leopard (or across any >>> major OS release version, or from one architecture processor to >>> another) can be problematic. In the case of moving from Tiger to >>> Leopard, you probably still have a lot of ports installed that >>> have the "darwin_8" variant. Examine "port installed" to see. You >>> should forcibly uninstall each of those (sudo port -f uninstall >>> foo) (making note of which other variants you selected), then >>> reinstall them (sudo port install foo +whatever), so they lose >>> the now-inappropriate darwin_8 variant and gain (if necessary) >>> the darwin_9 variant. From ryandesign at macports.org Sat Jan 5 11:54:42 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 11:59:47 2008 Subject: [MacPorts] #13829: sudo port -fvd install mldonkey In-Reply-To: References: <063.388a75ac9344036e2f45702b2dd56baa@macosforge.org> Message-ID: <4D9A0912-56DF-4FC9-9352-EC2712296D13@macports.org> I mean, port bugs should be assigned to the maintainer of the port. See the ticketing guidelines: http://guide.macports.org/#project.tickets Since the ticket was assigned to the generic macports-tickets address when I found it, I assigned it to Paul, and added a note explaining why I did that. I should have written "Assigned" instead of "Assign". On Jan 5, 2008, at 07:46, Charlse Darwin wrote: > `Assign to maintainer'? You mean pguyot@kallisys.net? > > Begin forwarded message: > >> From: "MacPorts" >> Date: January 5, 2008 12:02:40 AM EST (CA) >> To: macports.users@gmail.com, pguyot@kallisys.net >> Cc: macports-tickets@lists.macosforge.org >> Subject: Re: [MacPorts] #13829: sudo port -fvd install mldonkey >> Reply-To: noreply@macosforge.org >> >> #13829: sudo port -fvd install mldonkey >> --------------------------------------- >> +------------------------------------ >> Reporter: macports.users@gmail.com | Owner: >> pguyot@kallisys.net >> Type: defect | Status: new >> Priority: Normal | Milestone: Port Bugs >> Component: ports | Version: 1.6.0 >> Resolution: | Keywords: >> --------------------------------------- >> +------------------------------------ >> Changes (by ryandesign@macports.org): >> >> * owner: macports-tickets@lists.macosforge.org => >> pguyot@kallisys.net >> * milestone: => Port Bugs >> >> Comment: >> >> Assign to maintainer >> >> -- >> Ticket URL: > 13829#comment:1> >> MacPorts >> Ports system for Mac OS > From ryandesign at macports.org Sat Jan 5 12:19:02 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 12:17:28 2008 Subject: abiword issues In-Reply-To: <46A9249B-2C4E-40B1-A9DA-FEF6FD85B395@geo.umass.edu> References: <46A9249B-2C4E-40B1-A9DA-FEF6FD85B395@geo.umass.edu> Message-ID: On Jan 5, 2008, at 11:30, Michael J. Vollinger wrote: > Can anyone help me with some Abiword issues I am having? I tried > to install abiword-x11 and long list of error messages. Can be > viewed at http://www.nabble.com/abiword-x11-issues- > to14518635.html#a14518635 There is an issue filed about problems installing abiword-x11 on Leopard (I assumed you're on Leopard since your output mentioned "i686-apple-darwin9-g++-4.0.1" and Leopard is Darwin 9): http://trac.macosforge.org/projects/macports/ticket/13214 Not sure if that's the same issue you're experiencing. Unfortunately the abiword-x11 port is unmaintained so the problem won't get fixed until someone steps up to figure out what the problem is. > After that I tried installing the other abiword package, version > 2.4.5_0 and it says it installed. The problem I am having now is I > can not start the program. When I open a xterm window and type > abiword I get the error message: bash: abiword: command not found. > Am I doing anything wrong? Help help would be looked upon kindly > with any version of abiword. Try typing the full path to the executable, presumably /opt/local/bin/ abiword. Your xterm may not be using the same PATH as your Mac OS X Terminal. From ryandesign at macports.org Sat Jan 5 12:30:50 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 12:29:17 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> Message-ID: <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> On Jan 5, 2008, at 04:43, Chris Janton wrote: > On 2008-01-05 , at 01:19 , Kevin Ballard wrote: > >> If this problem is related to that commit and 10.3, then the only >> thing I can think of is that Mac OS X 10.3 included a broken >> version of tclsh, but that doesn't seem too plausible. >> >> I can't think of any reason for this error to only affect commands >> that open Portfiles. > > Anything I can do to help track down what is going wrong? The > "version" of tclsh on 10.3 appears just like 10.4 and 10.5 - a > symbolic link to tclsh8.4 I looked through the sources for "ui_channels" and found reference in the ChangeLog to the changeset I mentioned a couple messages ago. I could try reverting that changeset and compiling, see if it works then. From mikev at geo.umass.edu Sat Jan 5 12:48:15 2008 From: mikev at geo.umass.edu (Michael J. Vollinger) Date: Sat Jan 5 12:46:08 2008 Subject: abiword issues In-Reply-To: References: <46A9249B-2C4E-40B1-A9DA-FEF6FD85B395@geo.umass.edu> Message-ID: <477FED0F.6080301@geo.umass.edu> > There is an issue filed about problems installing abiword-x11 on Leopard > (I assumed you're on Leopard since your output mentioned > "i686-apple-darwin9-g++-4.0.1" and Leopard is Darwin 9): > > http://trac.macosforge.org/projects/macports/ticket/13214 > > Not sure if that's the same issue you're experiencing. That is the same trouble I am having with abiword-x11. >> After that I tried installing the other abiword package, version 2.4.5_0 and it says it installed. The problem I am having now is I can not start the program. When I open a xterm window and type abiword I get the error message: bash: abiword: command not found. Am I doing anything wrong? Help help would be looked upon kindly with any version of abiword. > > Try typing the full path to the executable, presumably /opt/local/bin/abiword. Your xterm may not be using the same PATH as your Mac OS X Terminal. I typed /opt/local/bin/abiword and got the return of bash: /opt/local/bin/abiword: No such file or directory. This happened both in xterm and in the Terminal. Mike -- Michael J. Vollinger Research Assistant Ronald B. Gilmore XRF Lab Dept. of Geosciences 611 North Pleasant Street University of Massachusetts Amherst, MA 01003 From ryandesign at macports.org Sat Jan 5 12:53:03 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 12:51:28 2008 Subject: abiword issues In-Reply-To: <477FED0F.6080301@geo.umass.edu> References: <46A9249B-2C4E-40B1-A9DA-FEF6FD85B395@geo.umass.edu> <477FED0F.6080301@geo.umass.edu> Message-ID: <8255A7A5-FA4D-4FF6-9FA8-F659C85F6F81@macports.org> On Jan 5, 2008, at 14:48, Michael J. Vollinger wrote: >>> After that I tried installing the other abiword package, version >>> 2.4.5_0 and it says it installed. The problem I am having now is >>> I can not start the program. When I open a xterm window and type >>> abiword I get the error message: bash: abiword: command not >>> found. Am I doing anything wrong? Help help would be looked >>> upon kindly with any version of abiword. >> >> Try typing the full path to the executable, presumably /opt/local/ >> bin/abiword. Your xterm may not be using the same PATH as your Mac >> OS X Terminal. > > I typed /opt/local/bin/abiword and got the return of bash: /opt/ > local/bin/abiword: No such file or directory. This happened both > in xterm and in the Terminal. Then I guess that's not what it installs. Type "port contents abiword- x11" to discover what it does install and where. From randall.h.wood at alexandriasoftware.com Sat Jan 5 13:11:27 2008 From: randall.h.wood at alexandriasoftware.com (Randall Wood) Date: Sat Jan 5 13:09:23 2008 Subject: abiword issues In-Reply-To: <8255A7A5-FA4D-4FF6-9FA8-F659C85F6F81@macports.org> References: <46A9249B-2C4E-40B1-A9DA-FEF6FD85B395@geo.umass.edu> <477FED0F.6080301@geo.umass.edu> <8255A7A5-FA4D-4FF6-9FA8-F659C85F6F81@macports.org> Message-ID: <549F1EEA-2B32-4B77-A9AA-E66216B59DB2@alexandriasoftware.com> Port abiword installs an Aqua app in /Applications/MacPorts. Look for it in the Finder. On 5 Jan 2008, at 15:53, Ryan Schmidt wrote: > > On Jan 5, 2008, at 14:48, Michael J. Vollinger wrote: > >>>> After that I tried installing the other abiword package, version >>>> 2.4.5_0 and it says it installed. The problem I am having now is >>>> I can not start the program. When I open a xterm window and type >>>> abiword I get the error message: bash: abiword: command not >>>> found. Am I doing anything wrong? Help help would be looked >>>> upon kindly with any version of abiword. >>> >>> Try typing the full path to the executable, presumably /opt/local/ >>> bin/abiword. Your xterm may not be using the same PATH as your Mac >>> OS X Terminal. >> >> I typed /opt/local/bin/abiword and got the return of bash: /opt/ >> local/bin/abiword: No such file or directory. This happened both >> in xterm and in the Terminal. > > Then I guess that's not what it installs. Type "port contents > abiword-x11" to discover what it does install and where. > > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users Randall Wood randall.h.wood@alexandriasoftware.com http://shyramblings.blogspot.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." From mikev at geo.umass.edu Sat Jan 5 13:27:08 2008 From: mikev at geo.umass.edu (Michael J. Vollinger) Date: Sat Jan 5 13:25:17 2008 Subject: abiword issues In-Reply-To: <8255A7A5-FA4D-4FF6-9FA8-F659C85F6F81@macports.org> References: <46A9249B-2C4E-40B1-A9DA-FEF6FD85B395@geo.umass.edu> <477FED0F.6080301@geo.umass.edu> <8255A7A5-FA4D-4FF6-9FA8-F659C85F6F81@macports.org> Message-ID: <28350AF0-8EC3-439D-A331-55D7D6D80715@geo.umass.edu> Here is the output and part of the list: tephra:~ mikev$ port contents abiword Port abiword contains: /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ enchant.framework/enchant /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ enchant.framework/Headers /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ enchant.framework/Resources /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ enchant.framework/Versions/A/enchant /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ enchant.framework/Versions/A/Headers/enchant.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ enchant.framework/Versions/A/Resources/AppleSpell.config /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ enchant.framework/Versions/A/Resources/AppleSpell.so /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ enchant.framework/Versions/A/Resources/English.lproj/InfoPlist.strings /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ enchant.framework/Versions/A/Resources/Info.plist /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ enchant.framework/Versions/A/Resources/ISpell.so /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ enchant.framework/Versions/Current /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/fribidi /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Headers /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/fribidi /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi_char_sets.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi_char_sets_cap_rtl.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi_char_sets_cp1255.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi_char_sets_cp1256.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi_char_sets_isiri_3342.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi_char_sets_iso8859_6.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi_char_sets_iso8859_8.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi_char_sets_utf8.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi_config.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi_mem.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi_types.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/A/Headers/fribidi_unicode.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ fribidi.framework/Versions/Current /Applications/MacPorts/AbiWord.app/Contents/Frameworks/libbz2.1.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ libglib-2.0.0.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ libglib-2.0.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ libgmodule-2.0.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ libgobject-2.0.0.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ libgobject-2.0.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ libgsf-1.1.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ libgthread-2.0.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/libiconv. 2.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/libintl. 1.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/liblink- grammar.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ libwpd-0.8.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/libwpd- stream-0.8.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ libxml2.2.dylib /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ png.framework/Headers /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ png.framework/png /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ png.framework/Resources /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ png.framework/Versions/1.2/Headers/png.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ png.framework/Versions/1.2/Headers/pngconf.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ png.framework/Versions/1.2/png /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ png.framework/Versions/1.2/Resources/English.lproj/InfoPlist.strings /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ png.framework/Versions/Current /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ popt.framework/Headers /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ popt.framework/popt /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ popt.framework/Versions/1.6/Headers/popt.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ popt.framework/Versions/1.6/popt /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ popt.framework/Versions/Current /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ Headers /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ Versions/1.0/Headers/libole2/ms-ole-summary.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ Versions/1.0/Headers/libole2/ms-ole.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ Versions/1.0/Headers/wv.h /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ Versions/1.0/wv /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ Versions/Current /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ wv /Applications/MacPorts/AbiWord.app/Contents/Info.plist /Applications/MacPorts/AbiWord.app/Contents/MacOS/AbiWord /Applications/MacPorts/AbiWord.app/Contents/PkgInfo /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/AbiBZ2.so-abi /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/AbiGoogle.so-abi /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/AbiLaTeX.so-abi /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/ AbiLinkGrammar.so-abi /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/ AbiOpenDocument.so-abi /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/ AbiOpenWriter.so-abi /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/AbiSDW.so-abi /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/AbiURLDict.so- abi /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/ AbiWikipedia.so-abi /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/ AbiWordPerfect.so-abi /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/AbiXHTML.so-abi /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/am-ET.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/ar.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/ast-ES.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/be-BY.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/bg-BG.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/br-FR.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/ca-ES.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/cs-CZ.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/CVS/Entries /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/CVS/Repository /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/CVS/Root /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/CVS/Tag /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/cy-GB.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/da-DK.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/de-CH.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/de-DE.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/el-GR.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/en-AU.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/en-CA.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/en-GB.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/en-IE.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/es-ES.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/es-MX.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/et.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/eu-ES.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/fi-FI.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/fr-FR.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/ga-IE.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/gl-ES.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/he-IL.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/hr-HR.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/hu-HU.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/id-ID.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/it-IT.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/ja-JP.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/jbo.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/ku.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/lt-LT.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/lv-LV.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/mg-MG.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/mh-MH.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/mk-MK.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/ms-MY.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/nb-NO.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/ne-NP.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/nl-NL.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/nn-NO.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/pl-PL.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/pt-BR.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/pt-PT.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/qu-BO.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/ro-RO.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/ru-RU.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/sc-IT.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/sk-SK.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/sl-SI.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/sq-AL.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/sr.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/sv-SE.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/ta-IN.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/tr-TR.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/uk-UA.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/vi-VN.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/yi.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/zh-CN.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/zh-HK.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ strings/zh-TW.strings /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-am-ET /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-ar /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-ar-EG /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-ar-SA /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-bg-BG /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-ca-ES /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-CP1254 /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-cs-CZ /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-da-DK /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-de /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-de-AT /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-de-CH /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-de-DE /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-div-MV /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-el-GR /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-en /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-en-AU /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-en-CA /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-en-GB /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-en-IE /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-en-NZ /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-en-US /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-en-ZA /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-es /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-es-ES /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-es-MX /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-eu /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-eu-ES /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-fa-IR /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-fi-FI /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-fr /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-fr-BE /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-fr-CA /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-fr-CH /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-fr-FR /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-gl-ES /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-he /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-he-IL /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-hu-HU /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-it-IT /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-ja-JP /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-KOI8-R /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-KOI8-U /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-KOI8-UB /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-lt-LT /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-nb-NO /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-nl-NL /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-nn-NO /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-pl-PL /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-ps /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-pt-BR /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-pt-PT /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-ru /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-ru-RU /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-sk-SK /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-sk-SK.CP1250 /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-sl /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-sv /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-sv-SE /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-syr /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-tr /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-tr-TR /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-tr-TR.CP1254 /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-uk-UA /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-ur-PK /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-yi /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-zh-CN /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ system.profile-zh-TW /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord.icns /Applications/MacPorts/AbiWord.app/Contents/Resources/ABWBackup.icns /Applications/MacPorts/AbiWord.app/Contents/Resources/ ABWDocument.icns /Applications/MacPorts/AbiWord.app/Contents/Resources/ABWPlugin.icns /Applications/MacPorts/AbiWord.app/Contents/Resources/ABWSaved.icns /Applications/MacPorts/AbiWord.app/Contents/Resources/ ap_CocoaDialog_Background.nib/classes.nib On Jan 5, 2008, at 3:53 PM, Ryan Schmidt wrote: > port contents abiword-x11 ------------------------------------- Michael J. Vollinger Research Assistant Ronald B. Gilmore XRF Lab Dept. of Geosciences 611 North Pleasant Street University of Massachusetts Amherst, MA 01003 From ryandesign at macports.org Sat Jan 5 13:30:45 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 13:29:12 2008 Subject: abiword issues In-Reply-To: <28350AF0-8EC3-439D-A331-55D7D6D80715@geo.umass.edu> References: <46A9249B-2C4E-40B1-A9DA-FEF6FD85B395@geo.umass.edu> <477FED0F.6080301@geo.umass.edu> <8255A7A5-FA4D-4FF6-9FA8-F659C85F6F81@macports.org> <28350AF0-8EC3-439D-A331-55D7D6D80715@geo.umass.edu> Message-ID: <996CD9DD-EEB6-41C8-ADC9-FDDA97B66B9F@macports.org> On Jan 5, 2008, at 15:27, Michael J. Vollinger wrote: > On Jan 5, 2008, at 3:53 PM, Ryan Schmidt wrote: > >> port contents abiword-x11 > > Here is the output and part of the list: > > tephra:~ mikev$ port contents abiword > Port abiword contains: > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > enchant.framework/enchant [snip] > /Applications/MacPorts/AbiWord.app/Contents/Resources/ > ap_CocoaDialog_Background.nib/classes.nib Ok. So then, as Randall said, the port installs AbiWord.app into / Applications/MacPorts. To use it, go to /Applications/MacPorts in the Finder and double-click AbiWord.app. From mikev at geo.umass.edu Sat Jan 5 13:34:57 2008 From: mikev at geo.umass.edu (Michael J. Vollinger) Date: Sat Jan 5 13:33:05 2008 Subject: abiword issues In-Reply-To: <28350AF0-8EC3-439D-A331-55D7D6D80715@geo.umass.edu> References: <46A9249B-2C4E-40B1-A9DA-FEF6FD85B395@geo.umass.edu> <477FED0F.6080301@geo.umass.edu> <8255A7A5-FA4D-4FF6-9FA8-F659C85F6F81@macports.org> <28350AF0-8EC3-439D-A331-55D7D6D80715@geo.umass.edu> Message-ID: <3D2BB0BD-1FC9-4238-8744-9D9E9474BF0B@geo.umass.edu> I checked in /Applications/MacPorts and it Abiword.app is there, but it is Cocoa version (not using x11) for some reason. I installed that version a while ago when I could not get the MacPorts (x11) version to install. But I did NOT install it in the MacPorts directory, I installed it in /Applications. I would prefer to use the x11 version if that is possible. Mike On Jan 5, 2008, at 4:27 PM, Michael J. Vollinger wrote: > Here is the output and part of the list: > > tephra:~ mikev$ port contents abiword > Port abiword contains: > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > enchant.framework/enchant > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > enchant.framework/Headers > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > enchant.framework/Resources > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > enchant.framework/Versions/A/enchant > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > enchant.framework/Versions/A/Headers/enchant.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > enchant.framework/Versions/A/Resources/AppleSpell.config > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > enchant.framework/Versions/A/Resources/AppleSpell.so > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > enchant.framework/Versions/A/Resources/English.lproj/InfoPlist.strings > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > enchant.framework/Versions/A/Resources/Info.plist > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > enchant.framework/Versions/A/Resources/ISpell.so > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > enchant.framework/Versions/Current > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/fribidi > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Headers > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/fribidi > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi_char_sets.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi_char_sets_cap_rtl.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi_char_sets_cp1255.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi_char_sets_cp1256.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi_char_sets_isiri_3342.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi_char_sets_iso8859_6.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi_char_sets_iso8859_8.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi_char_sets_utf8.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi_config.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi_mem.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi_types.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/A/Headers/fribidi_unicode.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > fribidi.framework/Versions/Current > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/libbz2.1.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > libglib-2.0.0.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > libglib-2.0.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > libgmodule-2.0.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > libgobject-2.0.0.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > libgobject-2.0.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > libgsf-1.1.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > libgthread-2.0.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/libiconv. > 2.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/libintl. > 1.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/liblink- > grammar.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > libwpd-0.8.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/libwpd- > stream-0.8.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > libxml2.2.dylib > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > png.framework/Headers > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > png.framework/png > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > png.framework/Resources > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > png.framework/Versions/1.2/Headers/png.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > png.framework/Versions/1.2/Headers/pngconf.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > png.framework/Versions/1.2/png > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > png.framework/Versions/1.2/Resources/English.lproj/InfoPlist.strings > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > png.framework/Versions/Current > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > popt.framework/Headers > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > popt.framework/popt > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > popt.framework/Versions/1.6/Headers/popt.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > popt.framework/Versions/1.6/popt > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/ > popt.framework/Versions/Current > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ > Headers > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ > Versions/1.0/Headers/libole2/ms-ole-summary.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ > Versions/1.0/Headers/libole2/ms-ole.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ > Versions/1.0/Headers/wv.h > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ > Versions/1.0/wv > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ > Versions/Current > /Applications/MacPorts/AbiWord.app/Contents/Frameworks/wv.framework/ > wv > /Applications/MacPorts/AbiWord.app/Contents/Info.plist > /Applications/MacPorts/AbiWord.app/Contents/MacOS/AbiWord > /Applications/MacPorts/AbiWord.app/Contents/PkgInfo > /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/AbiBZ2.so-abi > /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/AbiGoogle.so-abi > /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/AbiLaTeX.so-abi > /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/ > AbiLinkGrammar.so-abi > /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/ > AbiOpenDocument.so-abi > /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/ > AbiOpenWriter.so-abi > /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/AbiSDW.so-abi > /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/AbiURLDict.so- > abi > /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/ > AbiWikipedia.so-abi > /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/ > AbiWordPerfect.so-abi > /Applications/MacPorts/AbiWord.app/Contents/Plug-ins/AbiXHTML.so-abi > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/am-ET.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/ar.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/ast-ES.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/be-BY.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/bg-BG.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/br-FR.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/ca-ES.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/cs-CZ.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/CVS/Entries > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/CVS/Repository > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/CVS/Root > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/CVS/Tag > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/cy-GB.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/da-DK.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/de-CH.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/de-DE.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/el-GR.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/en-AU.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/en-CA.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/en-GB.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/en-IE.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/es-ES.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/es-MX.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/et.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/eu-ES.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/fi-FI.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/fr-FR.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/ga-IE.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/gl-ES.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/he-IL.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/hr-HR.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/hu-HU.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/id-ID.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/it-IT.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/ja-JP.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/jbo.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/ku.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/lt-LT.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/lv-LV.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/mg-MG.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/mh-MH.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/mk-MK.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/ms-MY.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/nb-NO.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/ne-NP.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/nl-NL.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/nn-NO.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/pl-PL.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/pt-BR.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/pt-PT.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/qu-BO.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/ro-RO.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/ru-RU.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/sc-IT.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/sk-SK.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/sl-SI.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/sq-AL.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/sr.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/sv-SE.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/ta-IN.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/tr-TR.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/uk-UA.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/vi-VN.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/yi.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/zh-CN.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/zh-HK.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > strings/zh-TW.strings > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-am-ET > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-ar > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-ar-EG > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-ar-SA > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-bg-BG > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-ca-ES > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-CP1254 > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-cs-CZ > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-da-DK > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-de > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-de-AT > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-de-CH > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-de-DE > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-div-MV > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-el-GR > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-en > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-en-AU > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-en-CA > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-en-GB > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-en-IE > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-en-NZ > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-en-US > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-en-ZA > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-es > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-es-ES > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-es-MX > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-eu > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-eu-ES > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-fa-IR > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-fi-FI > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-fr > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-fr-BE > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-fr-CA > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-fr-CH > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-fr-FR > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-gl-ES > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-he > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-he-IL > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-hu-HU > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-it-IT > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-ja-JP > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-KOI8-R > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-KOI8-U > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-KOI8-UB > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-lt-LT > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-nb-NO > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-nl-NL > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-nn-NO > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-pl-PL > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-ps > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-pt-BR > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-pt-PT > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-ru > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-ru-RU > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-sk-SK > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-sk-SK.CP1250 > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-sl > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-sv > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-sv-SE > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-syr > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-tr > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-tr-TR > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-tr-TR.CP1254 > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-uk-UA > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-ur-PK > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-yi > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-zh-CN > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord/ > system.profile-zh-TW > /Applications/MacPorts/AbiWord.app/Contents/Resources/AbiWord.icns > /Applications/MacPorts/AbiWord.app/Contents/Resources/ABWBackup.icns > /Applications/MacPorts/AbiWord.app/Contents/Resources/ > ABWDocument.icns > /Applications/MacPorts/AbiWord.app/Contents/Resources/ABWPlugin.icns > /Applications/MacPorts/AbiWord.app/Contents/Resources/ABWSaved.icns > /Applications/MacPorts/AbiWord.app/Contents/Resources/ > ap_CocoaDialog_Background.nib/classes.nib > > On Jan 5, 2008, at 3:53 PM, Ryan Schmidt wrote: > >> port contents abiword-x11 > > ------------------------------------- > Michael J. Vollinger > Research Assistant > Ronald B. Gilmore XRF Lab > Dept. of Geosciences > 611 North Pleasant Street > University of Massachusetts > Amherst, MA 01003 > > > > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users ------------------------------------- Michael J. Vollinger Research Assistant Ronald B. Gilmore XRF Lab Dept. of Geosciences 611 North Pleasant Street University of Massachusetts Amherst, MA 01003 From ryandesign at macports.org Sat Jan 5 13:47:27 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 13:45:51 2008 Subject: abiword issues In-Reply-To: <3D2BB0BD-1FC9-4238-8744-9D9E9474BF0B@geo.umass.edu> References: <46A9249B-2C4E-40B1-A9DA-FEF6FD85B395@geo.umass.edu> <477FED0F.6080301@geo.umass.edu> <8255A7A5-FA4D-4FF6-9FA8-F659C85F6F81@macports.org> <28350AF0-8EC3-439D-A331-55D7D6D80715@geo.umass.edu> <3D2BB0BD-1FC9-4238-8744-9D9E9474BF0B@geo.umass.edu> Message-ID: On Jan 5, 2008, at 15:34, Michael J. Vollinger wrote: > I checked in /Applications/MacPorts and it Abiword.app is there, > but it is Cocoa version (not using x11) for some reason. I > installed that version a while ago when I could not get the > MacPorts (x11) version to install. But I did NOT install it in the > MacPorts directory, I installed it in /Applications. I would > prefer to use the x11 version if that is possible. It seems that "abiword" is the Aqua version of Abiword and "abiword- x11" is the X11 version of Abiword. Here's your initial message: On Jan 5, 2008, at 11:30, Michael J. Vollinger wrote: > Can anyone help me with some Abiword issues I am having? I tried > to install abiword-x11 and long list of error messages. Can be > viewed at http://www.nabble.com/abiword-x11-issues- > to14518635.html#a14518635 > After that I tried installing the other abiword package, version > 2.4.5_0 and it says it installed. The problem I am having now is I > can not start the program. When I open a xterm window and type > abiword I get the error message: bash: abiword: command not found. > Am I doing anything wrong? Help help would be looked upon kindly > with any version of abiword. You explained that you cannot install abiword-x11 because of various errors, and I showed you a ticket in our issue tracker that had already been filed about that. You then asked for help using the abiword port instead. We have now shown you how to use the abiword port. If you would like to use the abiword-x11 port instead, you will have to discover why those error messages occur and help us to fix the portfile. You may have to open a discussion with the developers of the Abiword software. From David.Epstein at warwick.ac.uk Sat Jan 5 14:00:31 2008 From: David.Epstein at warwick.ac.uk (David Epstein) Date: Sat Jan 5 13:58:23 2008 Subject: Problem installing apache2 Message-ID: <14639067.post@talk.nabble.com> sudo port -d selfupdate ---- this passed, but with some warning messages that I might try cleaning up some directory or directories manually; I paid no attention to this As apache2 was giving me trouble, I then did sudo port clean --all apache2 --- this worked sudo port install apache2 --- error messages below Can anyone tell me what is going wrong, and, more to the point, how to fix it? Thanks a lot David ---> Fetching apache2 ---> Attempting to fetch httpd-2.2.6.tar.bz2 from http://www.apache.org/dist/httpd ---> Verifying checksum(s) for apache2 ---> Extracting apache2 ---> Applying patches to apache2 ---> Configuring apache2 ---> Building apache2 with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6" && make all " returned error 2 Command output: Making all in srclib Making all in os Making all in unix /opt/local/share/apr-1/build/libtool --silent --mode=compile /usr/bin/gcc-4.0 -I/opt/local/include -O2 -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp -I/opt/local/include -I. -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/os/unix -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/server/mpm/prefork -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/http -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/filters -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/proxy -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/generators -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/mappers -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/database -I/opt/local/include/apr-1 -I/opt/local/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/server -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/proxy/../generators -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/ssl -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.6/modules/dav/main -prefer-non-pic -static -c unixd.c && touch unixd.lo libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' make[3]: *** [unixd.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 Error: Status 1 encountered during processing. -- View this message in context: http://www.nabble.com/Problem-installing-apache2-tp14639067p14639067.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From ryandesign at macports.org Sat Jan 5 14:11:58 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 14:10:24 2008 Subject: Problem installing apache2 In-Reply-To: <14639067.post@talk.nabble.com> References: <14639067.post@talk.nabble.com> Message-ID: <3F3D1714-965C-41ED-AED6-723140266056@macports.org> On Jan 5, 2008, at 16:00, David Epstein wrote: > sudo port -d selfupdate ---- this passed, but with some warning > messages that > I might try cleaning up some directory or directories manually; I > paid no > attention to this > As apache2 was giving me trouble, I then did > sudo port clean --all apache2 --- this worked > sudo port install apache2 --- error messages below > Can anyone tell me what is going wrong, and, more to the point, how > to fix > it? [snip] > libtool: compile: unable to infer tagged configuration > libtool: compile: specify a tag with `--tag' > make[3]: *** [unixd.lo] Error 1 > make[2]: *** [all-recursive] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all-recursive] Error 1 We have a ticket for this: http://trac.macosforge.org/projects/macports/ticket/13653 I don't know what causes it or how to fix it. From eridius at macports.org Sat Jan 5 14:49:55 2008 From: eridius at macports.org (Kevin Ballard) Date: Sat Jan 5 14:47:48 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> Message-ID: Reverting changes just because of the name is probably a bad idea - that change was made for a reason, and there's nothing I can think of that would make that change have any problems on 10.3. -Kevin Ballard On Jan 5, 2008, at 3:30 PM, Ryan Schmidt wrote: > > On Jan 5, 2008, at 04:43, Chris Janton wrote: > >> On 2008-01-05 , at 01:19 , Kevin Ballard wrote: >> >>> If this problem is related to that commit and 10.3, then the only >>> thing I can think of is that Mac OS X 10.3 included a broken >>> version of tclsh, but that doesn't seem too plausible. >>> >>> I can't think of any reason for this error to only affect commands >>> that open Portfiles. >> >> Anything I can do to help track down what is going wrong? The >> "version" of tclsh on 10.3 appears just like 10.4 and 10.5 - a >> symbolic link to tclsh8.4 > > I looked through the sources for "ui_channels" and found reference > in the ChangeLog to the changeset I mentioned a couple messages ago. > I could try reverting that changeset and compiling, see if it works > then. -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com From ryandesign at macports.org Sat Jan 5 15:03:32 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 15:01:57 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> Message-ID: On Jan 5, 2008, at 16:49, Kevin Ballard wrote: > On Jan 5, 2008, at 3:30 PM, Ryan Schmidt wrote: > >> On Jan 5, 2008, at 04:43, Chris Janton wrote: >> >>> On 2008-01-05 , at 01:19 , Kevin Ballard wrote: >>> >>>> On Jan 4, 2008, at 23:32, Ryan Schmidt wrote: >>>> >>>>> Maybe this changeset is related to the problem? >>>>> >>>>> http://trac.macports.org/projects/macports/changeset/29498 >>>> >>>> If this problem is related to that commit and 10.3, then the >>>> only thing I can think of is that Mac OS X 10.3 included a >>>> broken version of tclsh, but that doesn't seem too plausible. >>>> >>>> I can't think of any reason for this error to only affect >>>> commands that open Portfiles. >>> >>> Anything I can do to help track down what is going wrong? The >>> "version" of tclsh on 10.3 appears just like 10.4 and 10.5 - a >>> symbolic link to tclsh8.4 >> >> I looked through the sources for "ui_channels" and found reference >> in the ChangeLog to the changeset I mentioned a couple messages >> ago. I could try reverting that changeset and compiling, see if it >> works then. I meant "You could try..." > Reverting changes just because of the name is probably a bad idea - > that change was made for a reason, and there's nothing I can think > of that would make that change have any problems on 10.3. I understand the change was made for a reason. But the error message reported on Panther is "Error: Unable to open port: invalid command name 'ui_channels'" and that changeset does remove three functions called "ui_channels" from port.tcl, portindex.tcl and portmirror.tcl. I don't have Panther or I'd test it myself. Chris does have Panther and was asking for suggestions for what he could try. So I made a suggestion. From macports.users at gmail.com Sat Jan 5 15:09:13 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Sat Jan 5 15:07:11 2008 Subject: sudo port install zsh Message-ID: $ sudo port install zsh Password: ---> Fetching zsh ---> Attempting to fetch zsh-4.2.6.tar.bz2 from http://www.zsh.org/pub/ ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp://ftp.zsh.org/zsh/ ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp:// ftp.sterling.com/zsh/ ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp://ftp.fu- berlin.de/pub/unix/shells/zsh/ ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp://ftp.iij.ad.jp/ pub/misc/zsh/ ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp://ftp.icm.edu.pl/ vol/wojsyl/zsh/ ---> Attempting to fetch zsh-4.2.6.tar.bz2 from http:// svn.macports.org/repository/macports/distfiles/zsh ---> Attempting to fetch zsh-4.2.6.tar.bz2 from http:// svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch zsh-4.2.6.tar.bz2 from http:// svn.macports.org/repository/macports/downloads/zsh Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. $ From eridius at macports.org Sat Jan 5 15:12:52 2008 From: eridius at macports.org (Kevin Ballard) Date: Sat Jan 5 15:10:49 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> Message-ID: We removed ui_channels and added a ui_channels_default, then changed where we call ui_channels to check and see if the command exists (so clients can override it), and if it doesn't exist to call ui_channels_default instead. So basically, the only reason it might fail on 10.3 is if [info commands ui_channels] returns something other than the blank string when ui_channels doesn't exist. Chris, can you fire up the tclsh shell and tell me what that command returns? -Kevin Ballard On Jan 5, 2008, at 6:03 PM, Ryan Schmidt wrote: > On Jan 5, 2008, at 16:49, Kevin Ballard wrote: > >> On Jan 5, 2008, at 3:30 PM, Ryan Schmidt wrote: >> >>> On Jan 5, 2008, at 04:43, Chris Janton wrote: >>> >>>> On 2008-01-05 , at 01:19 , Kevin Ballard wrote: >>>> >>>>> On Jan 4, 2008, at 23:32, Ryan Schmidt wrote: >>>>> >>>>>> Maybe this changeset is related to the problem? >>>>>> >>>>>> http://trac.macports.org/projects/macports/changeset/29498 >>>>> >>>>> If this problem is related to that commit and 10.3, then the >>>>> only thing I can think of is that Mac OS X 10.3 included a >>>>> broken version of tclsh, but that doesn't seem too plausible. >>>>> >>>>> I can't think of any reason for this error to only affect >>>>> commands that open Portfiles. >>>> >>>> Anything I can do to help track down what is going wrong? The >>>> "version" of tclsh on 10.3 appears just like 10.4 and 10.5 - a >>>> symbolic link to tclsh8.4 >>> >>> I looked through the sources for "ui_channels" and found reference >>> in the ChangeLog to the changeset I mentioned a couple messages >>> ago. I could try reverting that changeset and compiling, see if it >>> works then. > > I meant "You could try..." > >> Reverting changes just because of the name is probably a bad idea - >> that change was made for a reason, and there's nothing I can think >> of that would make that change have any problems on 10.3. > > I understand the change was made for a reason. But the error message > reported on Panther is "Error: Unable to open port: invalid command > name 'ui_channels'" and that changeset does remove three functions > called "ui_channels" from port.tcl, portindex.tcl and > portmirror.tcl. I don't have Panther or I'd test it myself. Chris > does have Panther and was asking for suggestions for what he could > try. So I made a suggestion. > -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com From ryandesign at macports.org Sat Jan 5 15:47:16 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 15:45:40 2008 Subject: sudo port install zsh In-Reply-To: References: Message-ID: On Jan 5, 2008, at 17:09, Charlse Darwin wrote: > $ sudo port install zsh > Password: > ---> Fetching zsh > ---> Attempting to fetch zsh-4.2.6.tar.bz2 from http://www.zsh.org/ > pub/ > ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp://ftp.zsh.org/ > zsh/ > ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp:// > ftp.sterling.com/zsh/ > ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp://ftp.fu- > berlin.de/pub/unix/shells/zsh/ > ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp:// > ftp.iij.ad.jp/pub/misc/zsh/ > ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp:// > ftp.icm.edu.pl/vol/wojsyl/zsh/ > ---> Attempting to fetch zsh-4.2.6.tar.bz2 from http:// > svn.macports.org/repository/macports/distfiles/zsh > ---> Attempting to fetch zsh-4.2.6.tar.bz2 from http:// > svn.macports.org/repository/macports/distfiles/general/ > ---> Attempting to fetch zsh-4.2.6.tar.bz2 from http:// > svn.macports.org/repository/macports/downloads/zsh > Error: Target org.macports.fetch returned: fetch failed > Error: Status 1 encountered during processing. > $ $ dig www.zsh.org ; <<>> DiG 9.3.4 <<>> www.zsh.org ;; global options: printcmd ;; connection timed out; no servers could be reached $ It appears that none of zsh.org's nameservers are reachable, thus www.zsh.org and ftp.zsh.org are unavailable. I have reported this to zefram at fysh.org, listed as the registrant of the zsh.org domain name. Attempting to contact ftp.sterling.com, I get a network timeout. Perhaps that mirror should be removed from the list. I can connect to ftp.fu-berlin.de but it only has versions 4.2.7 and 4.3.4. Maybe the zsh port should be updated. ftp.iij.ad.jp does have 4.2.6 and 4.3.2, but the first time I tried to connect it rejected me because it had reached its maximum of 10 connected users. Maybe that happened to you too. Maybe if you try again it'll work. The directory /vol/wojsyl/zsh/ does not seem to exist on ftp.icm.edu.pl so that mirror should be removed from the list too. I'm Cc'ing the maintainer of zsh on this email so he can take care of these issues. In the future, please file a ticket in our issue tracker when you discover something that doesn't work, and assign it to the maintainer of the port in question. From macports.users at gmail.com Sat Jan 5 15:51:06 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Sat Jan 5 15:49:03 2008 Subject: sudo port install zsh In-Reply-To: References: Message-ID: <1F7869BF-4400-457A-A87A-03B19CD6AD72@gmail.com> will do. On Jan 5, 2008, at 6:47 PM, Ryan Schmidt wrote: > > On Jan 5, 2008, at 17:09, Charlse Darwin wrote: > >> $ sudo port install zsh >> Password: >> ---> Fetching zsh >> ---> Attempting to fetch zsh-4.2.6.tar.bz2 from http:// >> www.zsh.org/pub/ >> ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp://ftp.zsh.org/ >> zsh/ >> ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp:// >> ftp.sterling.com/zsh/ >> ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp://ftp.fu- >> berlin.de/pub/unix/shells/zsh/ >> ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp:// >> ftp.iij.ad.jp/pub/misc/zsh/ >> ---> Attempting to fetch zsh-4.2.6.tar.bz2 from ftp:// >> ftp.icm.edu.pl/vol/wojsyl/zsh/ >> ---> Attempting to fetch zsh-4.2.6.tar.bz2 from http:// >> svn.macports.org/repository/macports/distfiles/zsh >> ---> Attempting to fetch zsh-4.2.6.tar.bz2 from http:// >> svn.macports.org/repository/macports/distfiles/general/ >> ---> Attempting to fetch zsh-4.2.6.tar.bz2 from http:// >> svn.macports.org/repository/macports/downloads/zsh >> Error: Target org.macports.fetch returned: fetch failed >> Error: Status 1 encountered during processing. >> $ > > $ dig www.zsh.org > > ; <<>> DiG 9.3.4 <<>> www.zsh.org > ;; global options: printcmd > ;; connection timed out; no servers could be reached > $ > > It appears that none of zsh.org's nameservers are reachable, thus > www.zsh.org and ftp.zsh.org are unavailable. I have reported this > to zefram at fysh.org, listed as the registrant of the zsh.org > domain name. > > Attempting to contact ftp.sterling.com, I get a network timeout. > Perhaps that mirror should be removed from the list. > > I can connect to ftp.fu-berlin.de but it only has versions 4.2.7 > and 4.3.4. Maybe the zsh port should be updated. > > ftp.iij.ad.jp does have 4.2.6 and 4.3.2, but the first time I tried > to connect it rejected me because it had reached its maximum of 10 > connected users. Maybe that happened to you too. Maybe if you try > again it'll work. > > The directory /vol/wojsyl/zsh/ does not seem to exist on > ftp.icm.edu.pl so that mirror should be removed from the list too. > > I'm Cc'ing the maintainer of zsh on this email so he can take care > of these issues. In the future, please file a ticket in our issue > tracker when you discover something that doesn't work, and assign > it to the maintainer of the port in question. > > From ryandesign at macports.org Sat Jan 5 16:03:45 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 16:02:10 2008 Subject: sudo port install zsh In-Reply-To: References: Message-ID: On Jan 5, 2008, at 17:47, Ryan Schmidt wrote: > $ dig www.zsh.org > > ; <<>> DiG 9.3.4 <<>> www.zsh.org > ;; global options: printcmd > ;; connection timed out; no servers could be reached > $ > > It appears that none of zsh.org's nameservers are reachable, thus > www.zsh.org and ftp.zsh.org are unavailable. I have reported this > to zefram at fysh.org, listed as the registrant of the zsh.org > domain name. zefram has responded to me to let me know he is contacting the responsible parties about the nameserver problems. From face at CentosPrime.COM Sat Jan 5 16:28:49 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sat Jan 5 16:26:57 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> Message-ID: <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> On 2008-01-05 , at 16:12 , Kevin Ballard wrote: > Chris, can you fire up the tclsh shell and tell me what that > command returns? Interestingly - the system I am "working with" - OS X Client 10.3.9 - doesn't show any problem in tclsh, but it fails. My target system - the OS X Server - shows an error. admin@x:admin:128 $ sw_vers ProductName: Mac OS X Server ProductVersion: 10.3.9 BuildVersion: 7W98 admin@x:admin:129 $ tclsh % [info commands ui_channels] ambiguous command name "": after append apply array auto_execok auto_import auto_load auto_load_index auto_qualify binary break case catch cd chan clock close concat continue dict encoding eof error eval exec exit expr fblocked fconfigure fcopy file fileevent flush for foreach format gets glob global history if incr info interp join lappend lassign lindex linsert list llength load lrange lrepeat lreplace lreverse lsearch lset lsort namespace open package pid proc puts pwd read regexp regsub rename return scan seek set socket source split string subst switch tclLog tell time trace unknown unload unset update uplevel upvar variable vwait while % admin@x:admin:130 $ house54 2 # sw_vers ProductName: Mac OS X ProductVersion: 10.3.9 BuildVersion: 7W98 house54 3 # tclsh % [info commands ui_channels] empty command name "" face@mac:face:122 $ sw_vers ProductName: Mac OS X ProductVersion: 10.4.11 BuildVersion: 8S2167 face@mac:face:123 $ tclsh % [info commands ui_channels] empty command name "" % house58 2 # sw_vers ProductName: Mac OS X ProductVersion: 10.5.1 BuildVersion: 9B18 house58 3 # tclsh % [info commands ui_channels] empty command name "" 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From ryandesign at macports.org Sat Jan 5 16:33:32 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 16:31:56 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> Message-ID: <347F960E-8678-40DB-B43B-88B6D687853C@macports.org> On Jan 5, 2008, at 18:28, Chris Janton wrote: > On 2008-01-05 , at 16:12 , Kevin Ballard wrote: > >> Chris, can you fire up the tclsh shell and tell me what that >> command returns? > > Interestingly - the system I am "working with" - OS X Client 10.3.9 > - doesn't show any problem in tclsh, but it fails. My target system > - the OS X Server - shows an error. > > admin@x:admin:128 $ sw_vers > ProductName: Mac OS X Server > ProductVersion: 10.3.9 > BuildVersion: 7W98 > admin@x:admin:129 $ tclsh > % [info commands ui_channels] > ambiguous command name "": after append apply array auto_execok > auto_import auto_load auto_load_index auto_qualify binary break > case catch cd chan clock close concat continue dict encoding eof > error eval exec exit expr fblocked fconfigure fcopy file fileevent > flush for foreach format gets glob global history if incr info > interp join lappend lassign lindex linsert list llength load lrange > lrepeat lreplace lreverse lsearch lset lsort namespace open package > pid proc puts pwd read regexp regsub rename return scan seek set > socket source split string subst switch tclLog tell time trace > unknown unload unset update uplevel upvar variable vwait while > % admin@x:admin:130 $ > > house54 2 # sw_vers > ProductName: Mac OS X > ProductVersion: 10.3.9 > BuildVersion: 7W98 > house54 3 # tclsh > % [info commands ui_channels] > empty command name "" > > face@mac:face:122 $ sw_vers > ProductName: Mac OS X > ProductVersion: 10.4.11 > BuildVersion: 8S2167 > face@mac:face:123 $ tclsh > % [info commands ui_channels] > empty command name "" > > % house58 2 # sw_vers > ProductName: Mac OS X > ProductVersion: 10.5.1 > BuildVersion: 9B18 > house58 3 # tclsh > % [info commands ui_channels] > empty command name "" Does your target system have the MacPorts tcl port installed? I see the same "ambiguous command name" error with the MacPorts tclsh 8.4.16 port installed, but see "empty command name" using the system's tclsh. $ sw_vers ProductName: Mac OS X ProductVersion: 10.4.11 BuildVersion: 8S2167 $ /usr/bin/tclsh % [info commands ui_channels] empty command name "" % exit $ /opt/local/bin/tclsh % [info commands ui_channels] ambiguous command name "": after append array auto_execok auto_import auto_load auto_load_index auto_qualify binary break case catch cd clock close concat continue encoding eof error eval exec exit expr fblocked fconfigure fcopy file fileevent flush for foreach format gets glob global history if incr info interp join lappend lindex linsert list llength load lrange lreplace lsearch lset lsort namespace open package pid proc puts pwd read regexp regsub rename return scan seek set socket source split string subst switch tclLog tell time trace unknown unset update uplevel upvar variable vwait while % exit $ From eridius at macports.org Sat Jan 5 16:36:52 2008 From: eridius at macports.org (Kevin Ballard) Date: Sat Jan 5 16:34:44 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> Message-ID: I think I must have misinformed you. Do not put the square brackets around the command when typing it at the tclsh prompt. % info commands ui_channels Try just doing that. -Kevin Ballard On Jan 5, 2008, at 7:28 PM, Chris Janton wrote: > On 2008-01-05 , at 16:12 , Kevin Ballard wrote: > >> Chris, can you fire up the tclsh shell and tell me what that >> command returns? > > > Interestingly - the system I am "working with" - OS X Client 10.3.9 > - doesn't show any problem in tclsh, but it fails. My target system > - the OS X Server - shows an error. > > admin@x:admin:128 $ sw_vers > ProductName: Mac OS X Server > ProductVersion: 10.3.9 > BuildVersion: 7W98 > admin@x:admin:129 $ tclsh > % [info commands ui_channels] > ambiguous command name "": after append apply array auto_execok > auto_import auto_load auto_load_index auto_qualify binary break case > catch cd chan clock close concat continue dict encoding eof error > eval exec exit expr fblocked fconfigure fcopy file fileevent flush > for foreach format gets glob global history if incr info interp join > lappend lassign lindex linsert list llength load lrange lrepeat > lreplace lreverse lsearch lset lsort namespace open package pid proc > puts pwd read regexp regsub rename return scan seek set socket > source split string subst switch tclLog tell time trace unknown > unload unset update uplevel upvar variable vwait while > % admin@x:admin:130 $ > > house54 2 # sw_vers > ProductName: Mac OS X > ProductVersion: 10.3.9 > BuildVersion: 7W98 > house54 3 # tclsh > % [info commands ui_channels] > empty command name "" > > face@mac:face:122 $ sw_vers > ProductName: Mac OS X > ProductVersion: 10.4.11 > BuildVersion: 8S2167 > face@mac:face:123 $ tclsh > % [info commands ui_channels] > empty command name "" > > % house58 2 # sw_vers > ProductName: Mac OS X > ProductVersion: 10.5.1 > BuildVersion: 9B18 > house58 3 # tclsh > % [info commands ui_channels] > empty command name "" > > > 8) > ---------------------------------- > Chris Janton - face at CentosPrime dot COM > Netminder for Opus1.COM > > -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com From face at CentosPrime.COM Sat Jan 5 16:47:53 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sat Jan 5 16:45:57 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> Message-ID: On 2008-01-05 , at 17:36 , Kevin Ballard wrote: > I think I must have misinformed you. Do not put the square brackets > around the command when typing it at the tclsh prompt. > > % info commands ui_channels > > Try just doing that. face@mac:face:120 $ sw_vers ProductName: Mac OS X ProductVersion: 10.4.11 BuildVersion: 8S2167 face@mac:face:121 $ which tclsh /usr/bin/tclsh face@mac:face:122 $ tclsh % info commands ui_channels % face@mac:face:123 $ admin@x:admin:121 $ sw_vers ProductName: Mac OS X Server ProductVersion: 10.3.9 BuildVersion: 7W98 admin@x:admin:122 $ which tclsh /opt/local/bin/tclsh admin@x:admin:123 $ tclsh % info commands ui_channels % admin@x:admin:124 $ /usr/bin/tclsh % info commands ui_channels house54 1 # sw_vers ProductName: Mac OS X ProductVersion: 10.3.9 BuildVersion: 7W98 house54 2 # which tclsh /usr/bin/tclsh house54 3 # tclsh % info commands ui_channels house58 1 # sw_vers ProductName: Mac OS X ProductVersion: 10.5.1 BuildVersion: 9B18 house58 2 # which tclsh /usr/bin/tclsh house58 3 # tclsh % info commands ui_channels % house58 4 # 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From eridius at macports.org Sat Jan 5 16:55:37 2008 From: eridius at macports.org (Kevin Ballard) Date: Sat Jan 5 16:53:28 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> Message-ID: <7B992CB1-9BF0-41AF-929D-087217E6F115@macports.org> Ok, the other possibility is that it's doing a substring search on some versions of tclsh. Try this: kevin@Erebor:~> tclsh % proc foo_bar {} { return 3 } % foo_bar 3 % info commands foo_bar foo_bar % info commands foo % Tell me if you get different results. -Kevin Ballard On Jan 5, 2008, at 7:47 PM, Chris Janton wrote: > On 2008-01-05 , at 17:36 , Kevin Ballard wrote: > >> I think I must have misinformed you. Do not put the square brackets >> around the command when typing it at the tclsh prompt. >> >> % info commands ui_channels >> >> Try just doing that. > > > face@mac:face:120 $ sw_vers > ProductName: Mac OS X > ProductVersion: 10.4.11 > BuildVersion: 8S2167 > face@mac:face:121 $ which tclsh > /usr/bin/tclsh > face@mac:face:122 $ tclsh > % info commands ui_channels > % face@mac:face:123 $ > > admin@x:admin:121 $ sw_vers > ProductName: Mac OS X Server > ProductVersion: 10.3.9 > BuildVersion: 7W98 > admin@x:admin:122 $ which tclsh > /opt/local/bin/tclsh > admin@x:admin:123 $ tclsh > % info commands ui_channels > % admin@x:admin:124 $ /usr/bin/tclsh > % info commands ui_channels > > house54 1 # sw_vers > ProductName: Mac OS X > ProductVersion: 10.3.9 > BuildVersion: 7W98 > house54 2 # which tclsh > /usr/bin/tclsh > house54 3 # tclsh > % info commands ui_channels > > house58 1 # sw_vers > ProductName: Mac OS X > ProductVersion: 10.5.1 > BuildVersion: 9B18 > house58 2 # which tclsh > /usr/bin/tclsh > house58 3 # tclsh > % info commands ui_channels > % house58 4 # > > 8) > ---------------------------------- > Chris Janton - face at CentosPrime dot COM > Netminder for Opus1.COM > > -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com From skip at pobox.com Sat Jan 5 16:58:25 2008 From: skip at pobox.com (skip@pobox.com) Date: Sat Jan 5 16:56:20 2008 Subject: Can I tell MacPorts a package is installed? Message-ID: <18304.10161.541429.142143@montanaro.dyndns.org> I'm still plugging away at getting glade3 installed. My latest problem port is py25-wxpython. I get a compile error (syntax error of some sort - unexpected ; or something). I decided to try simply building and installing it from source. Worked fine. Now, is there some way to tell the port command to ignore the dependency of glade3 on py25-wxpython so I can continue with my fumbling attempts at installing it? Thx, -- Skip Montanaro - skip@pobox.com - http://www.webfast.com/~skip/ From face at CentosPrime.COM Sat Jan 5 17:04:52 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sat Jan 5 17:02:57 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <7B992CB1-9BF0-41AF-929D-087217E6F115@macports.org> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> Message-ID: On 2008-01-05 , at 17:55 , Kevin Ballard wrote: > kevin@Erebor:~> tclsh > % proc foo_bar {} { return 3 } > % foo_bar > 3 > % info commands foo_bar > foo_bar > % info commands foo > % > > Tell me if you get different results. % house54 4 # which tclsh /usr/bin/tclsh house54 5 # tclsh % proc foo_bar {} { return 3 } % foo_bar 3 % info commands foo_bar foo_bar % info commands foo % house54 6 # admin@x:admin:125 $ which tclsh /opt/local/bin/tclsh admin@x:admin:126 $ tclsh % proc foo_bar {} { return 3 } % foo_bar 3 % info commands foo_bar foo_bar % info commands foo % % admin@x:admin:127 $ /usr/bin/tclsh % proc foo_bar {} { return 3 } % foo_bar 3 % info commands foo_bar foo_bar % info commands foo % admin@x:admin:128 $ 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From ryandesign at macports.org Sat Jan 5 17:06:52 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 17:05:17 2008 Subject: Can I tell MacPorts a package is installed? In-Reply-To: <18304.10161.541429.142143@montanaro.dyndns.org> References: <18304.10161.541429.142143@montanaro.dyndns.org> Message-ID: <8B0C1C44-3291-4EA6-ADC0-81E805347855@macports.org> On Jan 5, 2008, at 18:58, skip@pobox.com wrote: > I'm still plugging away at getting glade3 installed. My latest > problem port > is py25-wxpython. I get a compile error (syntax error of some sort - > unexpected ; or something). I decided to try simply building and > installing > it from source. Worked fine. Now, is there some way to tell the port > command to ignore the dependency of glade3 on py25-wxpython so I can > continue with my fumbling attempts at installing it? Not really. MacPorts isn't designed to be used in that way. MacPorts is designed to install "all" its software and dependencies itself. (There are exceptions, but py25-wxpython is not one of them.) If you can install it from source, but not install the port, then it should be relatively easy to fix the port. You should search the issue tracker and if there is not a bug you should file one. Then you could work with the maintainers of the port to see if you can help them resolve the problem. From ryandesign at macports.org Sat Jan 5 17:18:11 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 17:16:35 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> Message-ID: <5726DC1D-AE1A-439C-AD10-EB95B91C349C@macports.org> On Dec 29, 2007, at 09:12, Chris Janton wrote: > On 2007-12-29 , at 05:16 , Boey Maun Suang wrote: > >> Unfortunately, we don't seem to have too many people with Panther >> boxes >> who are able to help us test on that platform. If you, or indeed >> anybody >> else, would like to help me and see if they can reproduce the runtime >> error I describe, we'll be happy to post how to do so. > > I would be glad to help figure things out for Panther. I don't > expect to be upgrading that OS for some time (long) so having a > working, viable MacPorts is important to me. Probably what we should do first is determine the specific commit / revision / changeset that broke the build on Panther. I don't think we've established that yet. My wild guess was revision 29498. To test whether that's the culprit, check out trunk at r29497 and build it on Panther. If it builds, then check out trunk at r29498 and build it. If it fails, then r29498 broke the build, and we can further analyze the changes made in that revision. If r29497 already doesn't build, then go further back through the revisions. Try a binary search pattern of revisions between r29497 and r27897 (which is when the 1.5.2 tag was created) to try to find the one revision that breaks the build. Or, if r29498 still builds, then continue forward through the revisions. Binary search between r29498 and r32094 (which is when the 1.6.0 tag was created). From ryandesign at macports.org Sat Jan 5 17:20:06 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 17:18:29 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <5726DC1D-AE1A-439C-AD10-EB95B91C349C@macports.org> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <5726DC1D-AE1A-439C-AD10-EB95B91C349C@macports.org> Message-ID: <0ED54121-0829-4C59-BD0B-491C16D37FAB@macports.org> On Jan 5, 2008, at 19:18, Ryan Schmidt wrote: > On Dec 29, 2007, at 09:12, Chris Janton wrote: > >> On 2007-12-29 , at 05:16 , Boey Maun Suang wrote: >> >>> Unfortunately, we don't seem to have too many people with Panther >>> boxes >>> who are able to help us test on that platform. If you, or indeed >>> anybody >>> else, would like to help me and see if they can reproduce the >>> runtime >>> error I describe, we'll be happy to post how to do so. >> >> I would be glad to help figure things out for Panther. I don't >> expect to be upgrading that OS for some time (long) so having a >> working, viable MacPorts is important to me. > > Probably what we should do first is determine the specific commit / > revision / changeset that broke the build on Panther. I don't think > we've established that yet. My wild guess was revision 29498. To > test whether that's the culprit, check out trunk at r29497 and > build it on Panther. If it builds, then check out trunk at r29498 > and build it. If it fails, then r29498 broke the build, and we can > further analyze the changes made in that revision. > > If r29497 already doesn't build, then go further back through the > revisions. Try a binary search pattern of revisions between r29497 > and r27897 (which is when the 1.5.2 tag was created) to try to find > the one revision that breaks the build. Or, if r29498 still builds, > then continue forward through the revisions. Binary search between > r29498 and r32094 (which is when the 1.6.0 tag was created). Oh, um... I guess it wasn't that the build fails, it was that the port command doesn't work for some subcommands and complains about ui_channels. So after you build a given revision of trunk, test those failing port commands to see if they fail. From eridius at macports.org Sat Jan 5 17:21:35 2008 From: eridius at macports.org (Kevin Ballard) Date: Sat Jan 5 17:19:27 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> Message-ID: <05208774-7711-4A62-A235-9FC551DA8660@macports.org> Ok, I've just replaced the if-else statement that used this info command with a try-catch block instead, to see if that makes any difference (r32514). Please update to HEAD, reinstall port, and see if the problem remains. If the problem persists, please pass the -d switch and see if you can't get a backtrace out of it. -Kevin Ballard On Jan 5, 2008, at 8:04 PM, Chris Janton wrote: > On 2008-01-05 , at 17:55 , Kevin Ballard wrote: > >> kevin@Erebor:~> tclsh >> % proc foo_bar {} { return 3 } >> % foo_bar >> 3 >> % info commands foo_bar >> foo_bar >> % info commands foo >> % >> >> Tell me if you get different results. > > > % house54 4 # which tclsh > /usr/bin/tclsh > house54 5 # tclsh > % proc foo_bar {} { return 3 } > % foo_bar > 3 > % info commands foo_bar > foo_bar > % info commands foo > % house54 6 # > > admin@x:admin:125 $ which tclsh > /opt/local/bin/tclsh > admin@x:admin:126 $ tclsh > % proc foo_bar {} { return 3 } > % foo_bar > 3 > % info commands foo_bar > foo_bar > % info commands foo > % > > % admin@x:admin:127 $ /usr/bin/tclsh > % proc foo_bar {} { return 3 } > % foo_bar > 3 > % info commands foo_bar > foo_bar > % info commands foo > % admin@x:admin:128 $ > > 8) > ---------------------------------- > Chris Janton - face at CentosPrime dot COM > Netminder for Opus1.COM > > -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080105/a120f0ef/attachment-0001.html From kuraaku.deibiddo at gmail.com Sat Jan 5 17:28:46 2008 From: kuraaku.deibiddo at gmail.com (KURAAKU Deibiddo) Date: Sat Jan 5 17:26:36 2008 Subject: fusefs/ntfs-3g on Leopard Message-ID: <33531acd0801051728u2575dbd3n3337daaa5bae4809@mail.gmail.com> I've been trying to install both of these ports on 10.5 Leopard, but have met with no success so far. For some insane reason, it looks for /Applications/Developer/usr/bin/xcodebuild (which with Xcode tools installed, is actually in /usr/bin). If i symlink /usr into /Applications/Developer, I get this: [root@dissonance ~]# port install fusefs (With a blank line afterwards.) Even if i leave it for hours, it goes nowhere. If I delete my symlink: [root@dissonance ~]# rm -f /Applications/Developer/usr This is the result: [root@dissonance ~]# port install fusefs ---> Building fusefs Error: Target org.macports.build returned: shell command "cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_fusefs/work/fusefs/10.5" && xcodebuild -target "fusefs" -buildstyle Release build OBJROOT=build/ SYMROOT=build/ OBJROOT=build/ SYMROOT=build/" returned error 1 Command output: Error: Can't run /Applications/Developer/usr/bin/xcodebuild (no such file). Does anyone have a way to actually get fusefs and ntfs-3g to build successfully on 10.5 Leopard? Thanks in advance. david -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080105/5223cffb/attachment.html From ryandesign at macports.org Sat Jan 5 17:48:58 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 17:47:23 2008 Subject: fusefs/ntfs-3g on Leopard In-Reply-To: <33531acd0801051728u2575dbd3n3337daaa5bae4809@mail.gmail.com> References: <33531acd0801051728u2575dbd3n3337daaa5bae4809@mail.gmail.com> Message-ID: <4AAFE3EC-3DD6-47FD-B63D-49A828013305@macports.org> On Jan 5, 2008, at 19:28, KURAAKU Deibiddo wrote: > I've been trying to install both of these ports on 10.5 Leopard, > but have met with no success so far. > > For some insane reason, it looks for /Applications/Developer/usr/ > bin/xcodebuild (which with Xcode tools installed, is actually in / > usr/bin). If i symlink /usr into /Applications/Developer, I get this: > > [root@dissonance ~]# port install fusefs > > (With a blank line afterwards.) > > Even if i leave it for hours, it goes nowhere. If I delete my > symlink: > > [root@dissonance ~]# rm -f /Applications/Developer/usr > > This is the result: > > [root@dissonance ~]# port install fusefs > ---> Building fusefs > Error: Target org.macports.build returned: shell command "cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_ > fusefs/work/fusefs/10.5" && xcodebuild -target "fusefs" - > buildstyle Release build OBJROOT=build/ SYMROOT=build/ > OBJROOT=build/ SYMROOT=build/" returned error 1 > Command output: Error: Can't run /Applications/Developer/usr/bin/ > xcodebuild (no such file). > > Does anyone have a way to actually get fusefs and ntfs-3g to build > successfully on 10.5 Leopard? Do you have Xcode 2.5, Xcode 3, or both installed on your Leopard system? They can coexist on Leopard. And Xcode 2.5 can be installed in any prefix on Leopard. /Applications/Developer is weird. AFAIK Xcode has always been in / Developer. Did you tell it to install in /Applications/Developer instead? In order to support coexistence, Xcode 2.5 installs its files, like xcodebuild, under the Xcode directory, whatever directory you told that to be, rather than in system directories. On my Tiger system, for example, with Xcode 2.5, I have /Developer/usr/bin/xcodebuild. On Tiger, Xcode 2.5 also installs xcodebuild and other items into /usr/ bin. On Leopard, only Xcode 3 installs into system directories. None of this perhaps explains the problems building fusefs on Leopard. You should file a ticket in our issue tracker if one does not already exist. From face at CentosPrime.COM Sat Jan 5 17:52:15 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sat Jan 5 17:50:20 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <05208774-7711-4A62-A235-9FC551DA8660@macports.org> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> Message-ID: <92BE4E70-D01D-4C1A-8D71-6F393A75DE2F@CentosPrime.COM> On 2008-01-05 , at 18:21 , Kevin Ballard wrote: > Ok, I've just replaced the if-else statement that used this info > command with a try-catch block instead, to see if that makes any > difference (r32514). Please update to HEAD, reinstall port, and see > if the problem remains. > > If the problem persists, please pass the -d switch and see if you > can't get a backtrace out of it. > > -Kevin Ballard uhhh - now I am lost. update to HEAD? I'm not sure what you want me to do. I'm a "port sync" and/or "port selfupdate" kind of guy. I'm willing to learn ;-) 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From ryandesign at macports.org Sat Jan 5 18:03:31 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 18:01:55 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <92BE4E70-D01D-4C1A-8D71-6F393A75DE2F@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <92BE4E70-D01D-4C1A-8D71-6F393A75DE2F@CentosPrime.COM> Message-ID: <39A5FBCF-426E-422E-B09F-1FB175A89D55@macports.org> On Jan 5, 2008, at 19:52, Chris Janton wrote: > On 2008-01-05 , at 18:21 , Kevin Ballard wrote: > >> Ok, I've just replaced the if-else statement that used this info >> command with a try-catch block instead, to see if that makes any >> difference (r32514). Please update to HEAD, reinstall port, and >> see if the problem remains. >> >> If the problem persists, please pass the -d switch and see if you >> can't get a backtrace out of it. > > uhhh - now I am lost. > > update to HEAD? I'm not sure what you want me to do. I'm a "port > sync" and/or "port selfupdate" kind of guy. > I'm willing to learn ;-) Then you're going to need to become a "check out the source from Subversion and build it by hand" kind of guy to help us resolve this. You need the subversion port installed, if you don't have it already. Then you need to check out the current code from the HEAD of trunk, configure it, build it, and install it. $ svn checkout http://svn.macosforge.org/repository/macports/trunk/base $ cd base $ ./configure --enable-readline $ make $ sudo make install This will overwrite your existing MacPorts base in /opt/local. (It will not affect your installed ports.) If you want to install it to a different directory for testing instead, which might be a good idea, you can do this configure step instead: $ ./configure --enable-readline --prefix=/tmp/macports --with- tclpackage=/tmp/macports/share/macports/Tcl --with-install-user=YOU -- with-install-group=YOU where "YOU" is your Mac OS X username. This will install into /tmp/ macports. You can then run port with /tmp/macports/bin/port. From ryandesign at macports.org Sat Jan 5 18:40:15 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 18:38:39 2008 Subject: sudo port install zsh In-Reply-To: References: Message-ID: <5B028BED-F3A2-4357-8533-5BE0D49606B5@macports.org> On Jan 5, 2008, at 18:03, Ryan Schmidt wrote: > On Jan 5, 2008, at 17:47, Ryan Schmidt wrote: > >> $ dig www.zsh.org >> >> ; <<>> DiG 9.3.4 <<>> www.zsh.org >> ;; global options: printcmd >> ;; connection timed out; no servers could be reached >> $ >> >> It appears that none of zsh.org's nameservers are reachable, thus >> www.zsh.org and ftp.zsh.org are unavailable. I have reported this >> to zefram at fysh.org, listed as the registrant of the zsh.org >> domain name. > > zefram has responded to me to let me know he is contacting the > responsible parties about the nameserver problems. zsh.org is back online. They have two redundant sites, but apparently an uninterruptible power supply at one site failed, and there was a nameserver misconfiguration that prevented the backup site from being available. These issues are either now resolved or being worked on. From paulbeard at gmail.com Sat Jan 5 21:43:03 2008 From: paulbeard at gmail.com (paul beard) Date: Sat Jan 5 21:40:53 2008 Subject: dbus-glib hangs Message-ID: The maintainer is the ever-popular "nomaintainer" so I have no idea who should get this. And I couldn't access TRAC to look for or file a ticket. -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: dbus-glib.zip Type: application/zip Size: 5574 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080105/5d557093/dbus-glib-0001.zip From ajmas at sympatico.ca Sat Jan 5 21:44:07 2008 From: ajmas at sympatico.ca (Andre-John Mas) Date: Sat Jan 5 21:41:57 2008 Subject: Apache2 & IPv6 Message-ID: <550EE147-DA7D-4CB7-857C-9C564B894086@sympatico.ca> Hi, I noticed that there is no variant of Apache2 allowing for IPv6 support. Is there any chance one could be added? Andre From ryandesign at macports.org Sat Jan 5 22:13:16 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 22:11:41 2008 Subject: Apache2 & IPv6 In-Reply-To: <550EE147-DA7D-4CB7-857C-9C564B894086@sympatico.ca> References: <550EE147-DA7D-4CB7-857C-9C564B894086@sympatico.ca> Message-ID: <0372F219-86BE-4D2F-8DE3-0FA396BFB008@macports.org> On Jan 5, 2008, at 23:44, Andre-John Mas wrote: > I noticed that there is no variant of Apache2 allowing for IPv6 > support. Is there any > chance one could be added? If this is not already possible with the standard apache2, then you should file an enhancement request ticket in our issue tracker and assign it to the maintainer of the apache2 port. From ryandesign at macports.org Sat Jan 5 22:18:45 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 5 22:17:08 2008 Subject: dbus-glib hangs In-Reply-To: References: Message-ID: <6197D687-517C-48D6-98B0-2F70CAC0A7AE@macports.org> On Jan 5, 2008, at 23:43, paul beard wrote: > The maintainer is the ever-popular "nomaintainer" so I have no idea > who should get this. And I couldn't access TRAC to look for or file a > ticket. It's this bug: http://trac.macosforge.org/projects/macports/ticket/13448 and this bug: http://trac.macosforge.org/projects/macports/ticket/13566 and it's apparently a bad interaction between dbus-glib and glib- genmarshal from glib 2.14.4. glib-genmarshal from glib 2.14.2 apparently works fine. I maintain glib2 but I don't know what to do about this problem. I filed a bug with the developers of glib2 but it doesn't sound like it's their bug. I guess I should file a bug with the developers of dbus-glib next. Since I don't use dbus-glib, though, nor know anything about it, it might be better if someone who actually uses and knows something about the software were to file the bug and interact with the dbus-glib developers to resolve it. From tabithamc at gmail.com Sat Jan 5 22:27:34 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sat Jan 5 22:25:25 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work Message-ID: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> Hello all -- I've taken note of Ticket 11755 regarding a patch to the Apache2 MacPort due to the known problems with mod_ssl on Leopard. I have installed both the openssl and openssl97 MacPorts. I deactivated openssl and ensured that openssl97 was active. I patched the apache2 (version 2.2.6 of Apache) Portfile. And then I installed apache2 with the openssl97 variant: $ sudo port install apache2 +openssl97 > Then, when I try running apache I get: $ opt/local/apache2/bin/apachectl start > httpd: Syntax error on line 96 of /opt/local/apache2/conf/httpd.conf: > Cannot load /opt/local/apache2/modules/mod_ssl.so into server: > dlopen(/opt/local/apache2/modules/mod_ssl.so, 10): Symbol not found: > _ssl_cmd_SSLCACertificateFile\n Referenced from: > /opt/local/apache2/modules/mod_ssl.so\n Expected in: flat namespace\n > Line 96 of my http.conf file looks like this: LoadModule ssl_module modules/mod_ssl.so > Checking the file itself, I get: -rwxr-xr-x 2 admin staff 156512 Jan 6 06:09 mod_ssl.so > What would I be doing wrong? Maybe its best to compile mod_ssl.so manually, against openssl97, instead of with the patched Portfile? I would rather fix this for Apache2 rather than uproot the openssl Portfile (which uses 0.9.8g) and which many other MacPorts depend on. Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080105/03589648/attachment.html From guido.soranzio at gmail.com Sat Jan 5 23:16:33 2008 From: guido.soranzio at gmail.com (Guido Soranzio) Date: Sat Jan 5 23:14:28 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> Message-ID: On Jan 6, 2008, at 7:27 AM, Tabitha McNerney wrote: > I would rather fix this for Apache2 rather than uproot the openssl > Portfile (which uses 0.9.8g) and which many other MacPorts depend on. Yes, it is possible: a simple workaround consists in stripping out from Apache2's configure the option "-export-symbols-regex ssl_module". From blb at macports.org Sun Jan 6 00:21:16 2008 From: blb at macports.org (Bryan Blackburn) Date: Sun Jan 6 00:19:11 2008 Subject: Apache2 & IPv6 In-Reply-To: <0372F219-86BE-4D2F-8DE3-0FA396BFB008@macports.org> References: <550EE147-DA7D-4CB7-857C-9C564B894086@sympatico.ca> <0372F219-86BE-4D2F-8DE3-0FA396BFB008@macports.org> Message-ID: On Jan 5, 2008, at 11:13 PM, Ryan Schmidt wrote: > On Jan 5, 2008, at 23:44, Andre-John Mas wrote: > >> I noticed that there is no variant of Apache2 allowing for IPv6 >> support. Is there any >> chance one could be added? > > If this is not already possible with the standard apache2, then you > should file an enhancement request ticket in our issue tracker and > assign it to the maintainer of the apache2 port. > It should be the default, as it's working fine with my install: $ telnet ::1 80 Trying ::1... Connected to localhost. ... so at least IPv6 localhost is working. Bryan From tabithamc at gmail.com Sun Jan 6 01:23:45 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun Jan 6 01:21:36 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> Message-ID: <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> On 1/5/08, Guido Soranzio wrote: > > > On Jan 6, 2008, at 7:27 AM, Tabitha McNerney wrote: > > > I would rather fix this for Apache2 rather than uproot the openssl > > Portfile (which uses 0.9.8g) and which many other MacPorts depend on. > > > Yes, it is possible: a simple workaround consists in stripping out from > Apache2's configure the option "-export-symbols-regex ssl_module". It sounds as if stripping that would would mean that I would not be able to use OpenSSL 0.9.7. Hmmm ... that's a bummer. Thank you, T.M. _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080105/a6cba742/attachment.html From guido.soranzio at gmail.com Sun Jan 6 01:52:19 2008 From: guido.soranzio at gmail.com (Guido Soranzio) Date: Sun Jan 6 01:50:13 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> Message-ID: <0D7BAC06-6EA0-414F-8AE9-7C884FF55876@gmail.com> On Jan 6, 2008, at 10:23 AM, Tabitha McNerney wrote: > It sounds as if stripping that would would mean that I would not be > able to use OpenSSL 0.9.7. Hmmm ... that's a bummer. "-export-symbols-regex" is an option for libtool that limits the symbols exported by a module. I don't have yet tested this workaround on apache2, but under Leopard omitting this option from other troublesome makefiles makes accessible again the symbols reported as not to find. Here is a positive report on the "Symbol not found: _ssl_cmd_SSLCACertificateFile" error which happens otherwise with the current apache2 port: From tabithamc at gmail.com Sun Jan 6 02:12:16 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun Jan 6 02:10:06 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: <0D7BAC06-6EA0-414F-8AE9-7C884FF55876@gmail.com> References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> <0D7BAC06-6EA0-414F-8AE9-7C884FF55876@gmail.com> Message-ID: <7fccb3000801060212n15143c74w7eb5fd890dbf9fd1@mail.gmail.com> On 1/5/08, Guido Soranzio wrote: > > > On Jan 6, 2008, at 10:23 AM, Tabitha McNerney wrote: > > > It sounds as if stripping that would would mean that I would not be > > able to use OpenSSL 0.9.7. Hmmm ... that's a bummer. > > "-export-symbols-regex" is an option for libtool that limits the > symbols exported by a module. > > I don't have yet tested this workaround on apache2, but under Leopard > omitting this option from other troublesome makefiles makes accessible > again the symbols reported as not to find. > > Here is a positive report on the "Symbol not found: > _ssl_cmd_SSLCACertificateFile" > error which happens otherwise with the current apache2 port: > > < > http://www.nabble.com/Re%3A-Apache2%3A-Default-configuration-does-not-work--p14563107.html > > Hi Guido, Thanks for extra pointer. This seems worth trying out. I would rather stay with OpenSSL 0.9.8g only (instead of having two versions of OpenSSL). I will give this a try and see what I can come up with and will post my findings to this email thread on the list. Best, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080106/8672604e/attachment.html From ludwig at fh-worms.de Sun Jan 6 02:31:24 2008 From: ludwig at fh-worms.de (Christoph Ludwig) Date: Sun Jan 6 02:29:41 2008 Subject: OCamlDuce port install fails due to warnings turned into errors Message-ID: <20080106103123.GB18671@castellio.local> Hi, I cannot install the OCamlDuce port because the build encounters warnings which are treated as errors due to a compiler option. I filed an issue in Track , but perhaps someone on the list already has a fix. Regards Christoph -- FH Worms - University of Applied Sciences Fachbereich Informatik / Telekommunikation Erenburgerstr. 19, 67549 Worms, Germany From pmq at macports.org Sun Jan 6 04:01:56 2008 From: pmq at macports.org (Pierre Queinnec) Date: Sun Jan 6 03:59:54 2008 Subject: Error building p5-sdl_perl In-Reply-To: <14610995.post@talk.nabble.com> References: <14610995.post@talk.nabble.com> Message-ID: <4780C334.60907@macports.org> Ticket #13757 is a duplicate, as afb pointed out. This illustrates the fact that most bugs in Trac reported by users are filed against the port they originally intended to install. Sometimes the build fails while installing prerequisites though. Ticket #13757 isn't an exception: libsdl_image-framework fails to build, but the user said frozenbubble2 was the culprit. As for your bug, it is clearly different. Could you file a ticket and assign it to me? Thanks, -- Pierre LeAnne Lis wrote: > A search for the p5-sdl_perl port brings up a ticket from Dec 30, #13757: > frozenbubble2 doesn't build on leopard. However, it's been closed as a > duplicate. If it truly is a duplicate, then of what? And, how do I fix > this? > > Here's the error I get: > > ---> Fetching p5-sdl_perl > ---> Verifying checksum(s) for p5-sdl_perl > ---> Extracting p5-sdl_perl > ---> Applying patches to p5-sdl_perl > ---> Configuring p5-sdl_perl > ---> Building p5-sdl_perl with target all > Error: Target org.macports.build returned: shell command " cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_perl_p5-sdl_perl/work/SDL_Perl-2.1.3" > && /opt/local/bin/perl Build build " returned error 2 > Command output: Copying lib/SDL/Video.pm -> blib/lib/SDL/Video.pm > Copying lib/SDL/Event.pm -> blib/lib/SDL/Event.pm > Copying lib/SDL/Tutorial.pm -> blib/lib/SDL/Tutorial.pm > Copying lib/SDL/Sound.pm -> blib/lib/SDL/Sound.pm > Copying lib/SDL/Mixer.pm -> blib/lib/SDL/Mixer.pm > Copying lib/SDL/OpenGL.pm -> blib/lib/SDL/OpenGL.pm > Copying lib/SDL.pm -> blib/lib/SDL.pm > Copying lib/SDL/Timer.pm -> blib/lib/SDL/Timer.pm > Copying lib/SDL/Font.pm -> blib/lib/SDL/Font.pm > Copying lib/SDL/Music.pm -> blib/lib/SDL/Music.pm > Copying lib/SDL/OpenGL/Constants.pm -> blib/lib/SDL/OpenGL/Constants.pm > Copying lib/SDL/Color.pm -> blib/lib/SDL/Color.pm > Copying lib/SDL/Config.pm -> blib/lib/SDL/Config.pm > Copying lib/SDL/Tool/Font.pm -> blib/lib/SDL/Tool/Font.pm > Copying lib/SDL_perl.pm -> blib/lib/SDL_perl.pm > Copying lib/SDL/Cdrom.pm -> blib/lib/SDL/Cdrom.pm > Copying lib/SDL/Tutorial/Images.pm -> blib/lib/SDL/Tutorial/Images.pm > Copying lib/SDL/App.pm -> blib/lib/SDL/App.pm > Copying lib/SDL/TTFont.pm -> blib/lib/SDL/TTFont.pm > Copying lib/SDL/Constants.pm -> blib/lib/SDL/Constants.pm > Copying src/SDL.xs -> src/SDL_perl.xs > src/SDL_perl.xs -> src/SDL_perl.c > cc -I/opt/local/lib/perl5/5.8.8/darwin-2level/CORE -DXS_VERSION="2.1.3" > -DVERSION="2.1.3" -I/Library/Frameworks/SDL_mixer.framework/Headers > -I/Library/Frameworks/SDL_gfx.framework/Headers > -I/Library/Frameworks/SDL.framework/Headers > -I/Library/Frameworks/SDL_image.framework/Headers > -I/Library/Frameworks/SDL_net.framework/Headers > -I/Library/Frameworks/SDL_ttf.framework/Headers -I/opt/local/include/SDL > -D_GNU_SOURCE=1 -D_THREAD_SAFE -DHAVE_SDL -DHAVE_SDL_TTF -DHAVE_SDL_NET > -DHAVE_SDL_IMAGE -DHAVE_SDL_GFX -DHAVE_SDL_MIXER -Ddarwin -DMACOSX -fPIC -c > -I/opt/local/include -fno-common -DPERL_DARWIN -no-cpp-precomp > -fno-strict-aliasing -pipe -Wdeclaration-after-statement > -I/opt/local/include -O3 -o src/SDL_perl.o src/SDL_perl.c > src/SDL_perl.xs: In function 'XS_SDL_NetResolveIP': > src/SDL_perl.xs:2471: warning: assignment discards qualifiers from pointer > target type > ExtUtils::Mkbootstrap::Mkbootstrap('blib/arch/auto/src/SDL_perl/SDL_perl.bs') > env MACOSX_DEPLOYMENT_TARGET=10.3 cc -L/opt/local/lib -bundle -undefined > dynamic_lookup -o blib/arch/auto/src/SDL_perl/SDL_perl.bundle src/SDL_perl.o > -L../../lib -L/opt/local/lib -lSDLmain -lSDL -Wl,-framework,Cocoa -lSDL > -lSDL_ttf -lSDL_net -lSDL_image -lSDL_gfx -lSDL_mixer > ld: library not found for -lSDL_ttf > collect2: ld returned 1 exit status > error building blib/arch/auto/src/SDL_perl/SDL_perl.bundle from > src/SDL_perl.o at > /opt/local/lib/perl5/vendor_perl/5.8.8/ExtUtils/CBuilder/Base.pm line 213. > > Error: The following dependencies failed to build: p5-sdl_perl > Error: Status 1 encountered during processing. > From pmq at macports.org Sun Jan 6 05:15:02 2008 From: pmq at macports.org (Pierre Queinnec) Date: Sun Jan 6 05:12:55 2008 Subject: Error building p5-sdl_perl In-Reply-To: <4780C334.60907@macports.org> References: <14610995.post@talk.nabble.com> <4780C334.60907@macports.org> Message-ID: <4780D456.4010005@macports.org> Pierre Queinnec wrote: > As for your bug, it is clearly different. Could you file a ticket and > assign it to me? Errr, actually I really thought I maintained that port, but I'm not. So please discard the "assign it to me" part ;) -- Pierre From face at CentosPrime.COM Sun Jan 6 07:37:42 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sun Jan 6 07:35:46 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <39A5FBCF-426E-422E-B09F-1FB175A89D55@macports.org> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> Message-ID: <2278A3E8-C19C-41C9-A06B-F7A0C166A2EC@CentosPrime.COM> On 2008-01-05 , at 19:03 , Ryan Schmidt wrote: > Then you're going to need to become a "check out the source from > Subversion and build it by hand" kind of guy to help us resolve this. > > You need the subversion port installed, if you don't have it already. > > Then you need to check out the current code from the HEAD of trunk, > configure it, build it, and install it. > > $ svn checkout http://svn.macosforge.org/repository/macports/trunk/ > base > $ cd base > $ ./configure --enable-readline > $ make > $ sudo make install > > This will overwrite your existing MacPorts base in /opt/local. (It > will not affect your installed ports.) > > If you want to install it to a different directory for testing > instead, which might be a good idea, you can do this configure step > instead: I could have "cheated" and grabbed an svn client - but... I re-did MacPorts 1.5 so I could "port" house54 29 # port --version MacPorts 1.700 Entering interactive mode... ("help" for help, "quit" to quit) [s/base] > quit Goodbye house54 30 # port cat tree # $Id: Portfile 32371 2007-12-28 09:23:15Z boeyms@macports.org $ PortSystem 1.0 name tree version 1.5.1.1 categories sysutils maintainers nomaintainer description display tree-view of directories with optional color/HTML output long_description Tree is a simple utility that displays a \ tree-view of directories and files. It has \ options to use ANSI color escape-sequences or \ ASCII graphic characters, and can also output in \ HTML format. Tree was written by Steve Baker \ for Linux. master_sites ftp://mama.indstate.edu/linux/tree/ extract.suffix .tgz checksums md5 f8fc70a9260b50bf8b4613e9d5f5e589 platforms darwin patchfiles patch-tree.c.diff use_configure no build.args CFLAGS="-no-cpp-precomp" destroot.args BINDIR=${destroot}${prefix}/bin \ MANDIR=${destroot}${prefix}/share/ man/man1 post-destroot { xinstall -d -m 0755 ${destroot}${prefix}/share/doc/${name} xinstall -m 0644 -W ${worksrcpath} README CHANGES LICENSE \ ${destroot}${prefix}/share/doc/${name} } house54 31 # port install tree Error: Unable to execute port: can't create directory "/opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutil s_tree": permission denied house54 32 # sudo port install tree invalid command name "ui_prefix" Error: Status 1 encountered during processing. 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From guido.soranzio at gmail.com Sun Jan 6 10:04:37 2008 From: guido.soranzio at gmail.com (Guido Soranzio) Date: Sun Jan 6 10:02:28 2008 Subject: problem using port to install gnucash on mac 10.5 In-Reply-To: <9153cb050801060928s67e913bo7d3790120360f09f@mail.gmail.com> References: <9153cb050801031441x599afb40leb0207a0eb8c63bc@mail.gmail.com> <739B163F-8E4E-4B27-8CDE-0AC771BAFF3C@gmail.com> <9153cb050801060928s67e913bo7d3790120360f09f@mail.gmail.com> Message-ID: <75D53150-93CD-4E76-AAE7-94D61E44B8EF@gmail.com> On Jan 6, 2008, at 6:28 PM, Some Guy wrote: > I have re-installed dbus-python25 and tried again to install gnucash > but it fails again at this point :( > > -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/opt/local/include -I/ > opt/local/include/python2.5 -c _hashopenssl.c -o build/temp.macosx- > 10.3-i386-2.5/_hashopenssl.o > unable to execute -DNDEBUG: No such file or directory > error: command '-DNDEBUG' failed with exit status 1 This a hairy bug which is affecting recently the sequential build of Python packages: simply note that the compiler name is missing. You have to clean the Python port which stopped the build process ("sudo port clean py25-hashlib" in your case) and relaunch the original port command. -- Guido From tabithamc at gmail.com Sun Jan 6 11:24:24 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun Jan 6 11:22:13 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: <7fccb3000801060212n15143c74w7eb5fd890dbf9fd1@mail.gmail.com> References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> <0D7BAC06-6EA0-414F-8AE9-7C884FF55876@gmail.com> <7fccb3000801060212n15143c74w7eb5fd890dbf9fd1@mail.gmail.com> Message-ID: <7fccb3000801061124r11a9c97cm7999e2236d67c2fc@mail.gmail.com> Guido, I just had an idea. Why not use Apple's libssl.so that comes with Leopard Server, which can be found in: /usr/libexec/httpd/libssl.so Based on the output of otool, Apple has built libssl.so against OpenSSL 0.9.7 rather than the troublesome 0.9.8: $ otool -L libssl.so libssl.so: /usr/lib/libssl.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7) /usr/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0) Is there any reason why libssl could not be used in place of mod_ssl for those running MacPorts on Leopard Server? I don't spend enough of my time in the depths of Apache but I think I will try this out and see what happens. Note: if this solution works, it would not solve the problem for people who are running Leopard but not Leopard Server. Thanks, T.M. On 1/6/08, Tabitha McNerney wrote: > > > > On 1/5/08, Guido Soranzio wrote: > > > > > > On Jan 6, 2008, at 10:23 AM, Tabitha McNerney wrote: > > > > > It sounds as if stripping that would would mean that I would not be > > > able to use OpenSSL 0.9.7. Hmmm ... that's a bummer. > > > > "-export-symbols-regex" is an option for libtool that limits the > > symbols exported by a module. > > > > I don't have yet tested this workaround on apache2, but under Leopard > > omitting this option from other troublesome makefiles makes accessible > > again the symbols reported as not to find. > > > > Here is a positive report on the "Symbol not found: > > _ssl_cmd_SSLCACertificateFile" > > error which happens otherwise with the current apache2 port: > > > > > > > > > Hi Guido, > > Thanks for extra pointer. This seems worth trying out. I would rather stay > with OpenSSL 0.9.8g only (instead of having two versions of OpenSSL). I > will give this a try and see what I can come up with and will post my > findings to this email thread on the list. > > Best, > > T.M. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080106/0a0df9d9/attachment.html From someguyonearth at gmail.com Sun Jan 6 11:36:56 2008 From: someguyonearth at gmail.com (Some Guy) Date: Sun Jan 6 11:34:44 2008 Subject: problem using port to install gnucash on mac 10.5 In-Reply-To: <75D53150-93CD-4E76-AAE7-94D61E44B8EF@gmail.com> References: <9153cb050801031441x599afb40leb0207a0eb8c63bc@mail.gmail.com> <739B163F-8E4E-4B27-8CDE-0AC771BAFF3C@gmail.com> <9153cb050801060928s67e913bo7d3790120360f09f@mail.gmail.com> <75D53150-93CD-4E76-AAE7-94D61E44B8EF@gmail.com> Message-ID: <9153cb050801061136u24b01353w57652d56ba01d863@mail.gmail.com> thanks now the problem is with firefox-x11 ---> Building firefox-x11 with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_firefox-x11/work/mozilla" && make all " returned error 2 Command output: mv -f /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_firefox-x11/work/mozilla/dist/include/nspr/_darwin.cfg /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_firefox-x11/work/mozilla/dist/include/nspr/prcpucfg.h cd private; /usr/bin/make export ../../../config/./nsinstall -L /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_firefox-x11/work/mozilla/nsprpub/pr/include/private -m 444 ./pprio.h ./pprthred.h ./prpriv.h /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_firefox-x11/work/mozilla/dist/include/nspr/private cd obsolete; /usr/bin/make export ../../../config/./nsinstall -L /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_firefox-x11/work/mozilla/nsprpub/pr/include/obsolete -m 444 ./pralarm.h ./probslet.h ./protypes.h ./prsem.h /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_firefox-x11/work/mozilla/dist/include/nspr/obsolete ../../config/./nsinstall -L /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_firefox-x11/work/mozilla/nsprpub/pr/include -m 444 ./nspr.h ./pratom.h ./prbit.h ./prclist.h ./prcmon.h ./prcountr.h ./prcvar.h ./prdtoa.h ./prenv.h ./prerr.h ./prerror.h ./prinet.h ./prinit.h ./prinrval.h ./prio.h ./pripcsem.h ./prlink.h ./prlock.h ./prlog.h ./prlong.h ./prmem.h ./prmon.h ./prmwait.h ./prnetdb.h ./prolock.h ./prpdce.h ./prprf.h ./prproces.h ./prrng.h ./prrwlock.h ./prshm.h ./prshma.h ./prsystem.h ./prthread.h ./prtime.h ./prtpool.h ./prtrace.h ./prtypes.h ./prvrsion.h ./prwin16.h /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_firefox-x11/work/mozilla/dist/include/nspr cd src; /usr/bin/make export cd io; /usr/bin/make export make[5]: Nothing to be done for `export'. cd linking; /usr/bin/make export /usr/bin/gcc-4.0 -o prlink.o -c -I/opt/local/include -O2 -pipe -Wmost -fno-common -no-cpp-precomp -pthread -O2 -fPIC -UDEBUG -DMOZILLA_CLIENT=1 -DNDEBUG=1 -DHAVE_VISIBILITY_HIDDEN_ATTRIBUTE=1 -DXP_UNIX=1 -DDARWIN=1 -DHAVE_BSD_FLOCK=1 -Di386=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 -DHAVE_STRERROR=1 -DFORCE_PR_LOG -D_PR_PTHREADS -UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_firefox-x11/work/mozilla/dist/include/nspr -I../../../pr/include -I../../../pr/include/private -I/Developer/Headers/FlatCarbon prlink.c In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:21, from /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:20, from /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20, from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:21, from /Developer/Headers/FlatCarbon/CodeFragments.h:1, from prlink.c:48: /usr/include/signal.h:84: error: syntax error before numeric constant prlink.c: In function 'pr_LoadViaCFM': prlink.c:701: warning: 'ResolveAliasFile' is deprecated (declared at /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Aliases.h:1035) prlink.c: In function 'pr_FindSymbolInLib': prlink.c:1400: warning: 'c2pstrcpy' is deprecated (declared at /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/TextUtils.h:578) prlink.c: In function 'PR_GetLibraryFilePathname': prlink.c:1629: warning: assignment discards qualifiers from pointer target type make[5]: *** [prlink.o] Error 1 make[4]: *** [export] Error 2 make[3]: *** [export] Error 2 make[2]: *** [export] Error 2 make[1]: *** [nspr] Error 2 make: *** [all] Error 2 Error: The following dependencies failed to build: gnucash-docs yelp firefox-x11 libgtkhtml goffice03 libgnomeprintui libgnomeprint bison libgnomecups pcre guile16 readline ncurses ncursesw gawk libgtkhtml3 p5-finance-quote p5-crypt-ssleay p5-libwww-perl p5-compress-zlib p5-compress-raw-zlib p5-io-compress-base p5-scalar-list-utils p5-io-compress-zlib p5-html-parser p5-html-tagset p5-uri p5-datemanip p5-html-tableextract slib slib-guile16 Error: Status 1 encountered during processing. On Jan 6, 2008 6:04 PM, Guido Soranzio wrote: > On Jan 6, 2008, at 6:28 PM, Some Guy wrote: > > > I have re-installed dbus-python25 and tried again to install gnucash > > but it fails again at this point :( > > > > -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/opt/local/include -I/ > > opt/local/include/python2.5 -c _hashopenssl.c -o build/temp.macosx- > > 10.3-i386-2.5/_hashopenssl.o > > unable to execute -DNDEBUG: No such file or directory > > error: command '-DNDEBUG' failed with exit status 1 > > > This a hairy bug which is affecting recently the sequential > build of Python packages: simply note that the compiler > name is missing. > > You have to clean the Python port which stopped the build > process ("sudo port clean py25-hashlib" in your case) and > relaunch the original port command. > > > -- > Guido > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080106/3fe6141d/attachment.html From ansgar at esztermann.de Sun Jan 6 11:43:38 2008 From: ansgar at esztermann.de (Ansgar Esztermann) Date: Sun Jan 6 11:41:39 2008 Subject: Fwd: problem using port to install gnucash on mac 10.5 References: <020F2477-AFAC-4DF1-BD92-98E7E25AA18A@esztermann.de> Message-ID: <216A8AE3-8EA8-47A4-89EF-28B4AEC0EAAB@esztermann.de> [Sorry, forgot to reply to the list] > On Jan 6, 2008, at 20:36 , Some Guy wrote: > >> now the problem is with firefox-x11 > > firefox-x11 is only needed to read the documentation, so you can try > to install without it: > > sudo port install gnucash +without_docs > > Using that option, I managed to install all prerequisites. The > gnucash port itself still would not install, though. This is due to > a guile problem. > > > A. From someguyonearth at gmail.com Sun Jan 6 12:34:19 2008 From: someguyonearth at gmail.com (Some Guy) Date: Sun Jan 6 12:32:08 2008 Subject: problem using port to install gnucash on mac 10.5 In-Reply-To: <216A8AE3-8EA8-47A4-89EF-28B4AEC0EAAB@esztermann.de> References: <020F2477-AFAC-4DF1-BD92-98E7E25AA18A@esztermann.de> <216A8AE3-8EA8-47A4-89EF-28B4AEC0EAAB@esztermann.de> Message-ID: <9153cb050801061234r59de548cn51f60251ec67a024@mail.gmail.com> mmm, it says it needs guile 1.6 or later Used port to install guile and it spins out --> Building guile with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/work/guile- 1.8.3" && make all " returned error 2 Command output: /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I/opt/local/include -D_THREAD_SAFE -O2 -Wall -Wmissing-prototypes -Werror -MT libguile_la-fports.lo -MD -MP -MF .deps/libguile_la-fports.Tpo -c fports.c -fno-common -DPIC -o .libs/libguile_la-fports.o cc1: warnings being treated as errors fports.c: In function 'scm_open_file': fports.c:364: warning: implicit declaration of function 'open64' fports.c: At top level: fports.c:614: error: syntax error before 'fport_seek_or_seek64' fports.c:614: error: syntax error before 'off64_t' fports.c:615: warning: return type defaults to 'int' fports.c:615: warning: no previous prototype for 'fport_seek_or_seek64' fports.c: In function 'fport_seek_or_seek64': fports.c:616: error: 'port' undeclared (first use in this function) fports.c:616: error: (Each undeclared identifier is reported only once fports.c:616: error: for each function it appears in.) fports.c:618: error: 'off64_t' undeclared (first use in this function) fports.c:618: error: syntax error before 'rv' fports.c:623: error: 'offset' undeclared (first use in this function) fports.c:623: error: 'whence' undeclared (first use in this function) fports.c:626: error: 'result' undeclared (first use in this function) fports.c:626: error: 'rv' undeclared (first use in this function) fports.c:626: warning: implicit declaration of function 'lseek64' fports.c: In function 'fport_seek': fports.c:677: error: 'off64_t' undeclared (first use in this function) fports.c:677: error: syntax error before 'rv' fports.c:678: error: 'rv' undeclared (first use in this function) fports.c: In function 'scm_i_fport_truncate': fports.c:711: warning: implicit declaration of function 'ftruncate64' make[3]: *** [libguile_la-fports.lo] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: Status 1 encountered during processing. On Jan 6, 2008 7:43 PM, Ansgar Esztermann wrote: > > [Sorry, forgot to reply to the list] > > > On Jan 6, 2008, at 20:36 , Some Guy wrote: > > > >> now the problem is with firefox-x11 > > > > firefox-x11 is only needed to read the documentation, so you can try > > to install without it: > > > > sudo port install gnucash +without_docs > > > > Using that option, I managed to install all prerequisites. The > > gnucash port itself still would not install, though. This is due to > > a guile problem. > > > > > > A. > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080106/0f591a46/attachment-0001.html From ansgar at esztermann.de Sun Jan 6 12:42:00 2008 From: ansgar at esztermann.de (Ansgar Esztermann) Date: Sun Jan 6 12:39:49 2008 Subject: problem using port to install gnucash on mac 10.5 In-Reply-To: <9153cb050801061234r59de548cn51f60251ec67a024@mail.gmail.com> References: <020F2477-AFAC-4DF1-BD92-98E7E25AA18A@esztermann.de> <216A8AE3-8EA8-47A4-89EF-28B4AEC0EAAB@esztermann.de> <9153cb050801061234r59de548cn51f60251ec67a024@mail.gmail.com> Message-ID: On Jan 6, 2008, at 21:34 , Some Guy wrote: > mmm, it says it needs guile 1.6 or later > > Used port to install guile and it spins out ... > Error: Status 1 encountered during processing. So it does. By the way, the dependency is on guile16, not guile. That port does install fine, but at configure time, gnucash fails to find the necessary files, so it still does not work. A. From guido.soranzio at gmail.com Sun Jan 6 13:14:38 2008 From: guido.soranzio at gmail.com (Guido Soranzio) Date: Sun Jan 6 13:12:30 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: <7fccb3000801061124r11a9c97cm7999e2236d67c2fc@mail.gmail.com> References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> <0D7BAC06-6EA0-414F-8AE9-7C884FF55876@gmail.com> <7fccb3000801060212n15143c74w7eb5fd890dbf9fd1@mail.gmail.com> <7fccb3000801061124r11a9c97cm7999e2236d67c2fc@mail.gmail.com> Message-ID: <47C148C2-D589-4436-8963-F737C6B4FB40@gmail.com> On Jan 6, 2008, at 8:24 PM, Tabitha McNerney wrote: > I just had an idea. Why not use Apple's libssl.so that comes with > Leopard Server Because the goal of the MacPorts project is the contrary of that: we should mess with the sources provided by third parties, not with the binaries distributed by Apple! I have tried to apply the rough workaround I suggested you; these are the simple steps I followed: * extract the sources of Apache with "sudo port extract apache2" * search where in the sources the option "-export-simbol-regex" is defined with: grep -r "-export-symbols-regex" /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_www_apache2 ==> [...] [...] /httpd-2.2.6/configure: test "x$silent" != "xyes" && echo " setting MOD_SSL_LDADD to \"-export-symbols-regex ssl_module\"" [...]/ httpd-2.2.6/configure: MOD_SSL_LDADD="-export-symbols-regex ssl_module" [...] /httpd-2.2.6/configure: apr_addto_bugger="-export-symbols- regex ssl_module" [...] * as suspected, the option is used to build the ssl_module... * let's edit the apache2 Portfile with "sudo port edit apache2" and add our patch to the configure script in the Leopard section: platform darwin 9 { depends_build-append port:gawk post-extract { reinplace "s|-export-symbols-regex ssl_module||g" $ {worksrcpath}/configure } } * after cleaning the apache2 port and compiling it, let's test it: sudo apachectl start * no message errors about missing symbols: we got it! -- Guido From skip at pobox.com Sun Jan 6 13:23:02 2008 From: skip at pobox.com (skip@pobox.com) Date: Sun Jan 6 13:20:54 2008 Subject: libtoolize vs. glibtoolize? Message-ID: <18305.18102.782112.397805@montanaro.dyndns.org> I'm slowly deleting stuff that I had installed previous to installing MacPorts. Today I launched into the libtool/auto* stuff. I have the latest libtool-devel installed. I find I have glibtoolize but no longer have libtoolize. What's the difference? When I try to bootstrap the configuration of a little project from work with these commands: glibtoolize --automake aclocal autoheader automake --foreign --add-missing autoconf aclocal fails with this output: /opt/local/share/aclocal/smpeg.m4:13: warning: underquoted definition of AM_PATH_SMPEG /opt/local/share/aclocal/smpeg.m4:13: run info '(automake)Extending aclocal' /opt/local/share/aclocal/smpeg.m4:13: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal /opt/local/bin/gm4:configure.ac:23: recursion limit of 1024 exceeded, use -L to change it autom4te: /opt/local/bin/gm4 failed with exit status: 1 aclocal: autom4te failed with exit status: 1 This is a configuration which used to work (and still works on the Solaris machines at work, modulo the "libtoolize" vs. "glibtoolize" bit). Is the smpeg.m4 warning related to the recursion limit error? Thx, -- Skip Montanaro - skip@pobox.com - http://www.webfast.com/~skip/ From ryandesign at macports.org Sun Jan 6 13:44:48 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Jan 6 13:43:10 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <2278A3E8-C19C-41C9-A06B-F7A0C166A2EC@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <2278A3E8-C19C-41C9-A06B-F7A0C166A2EC@CentosPrime.COM> Message-ID: <03D498F4-869A-4399-A7FB-2E4D58FDD139@macports.org> On Jan 6, 2008, at 09:37, Chris Janton wrote: > On 2008-01-05 , at 19:03 , Ryan Schmidt wrote: > >> Then you're going to need to become a "check out the source from >> Subversion and build it by hand" kind of guy to help us resolve this. > > I could have "cheated" and grabbed an svn client - but... > I re-did MacPorts 1.5 so I could "port" [snip] > house54 31 # port install tree > Error: Unable to execute port: can't create directory "/opt/local/ > var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_sysut > ils_tree": permission denied > house54 32 # sudo port install tree > invalid command name "ui_prefix" > Error: Status 1 encountered during processing. Ok, so you've discovered that Kevin's latest attempt did not fix the issue. Perhaps you could try what I suggested to discover which change caused the issue in the first place? http://lists.macosforge.org/pipermail/macports-users/2008-January/ 008061.html From tabithamc at gmail.com Sun Jan 6 13:47:19 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun Jan 6 13:45:06 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: <47C148C2-D589-4436-8963-F737C6B4FB40@gmail.com> References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> <0D7BAC06-6EA0-414F-8AE9-7C884FF55876@gmail.com> <7fccb3000801060212n15143c74w7eb5fd890dbf9fd1@mail.gmail.com> <7fccb3000801061124r11a9c97cm7999e2236d67c2fc@mail.gmail.com> <47C148C2-D589-4436-8963-F737C6B4FB40@gmail.com> Message-ID: <7fccb3000801061347q5af9f374x331a78fb71cbdf23@mail.gmail.com> On 1/6/08, Guido Soranzio wrote: > > On Jan 6, 2008, at 8:24 PM, Tabitha McNerney wrote: > > > I just had an idea. Why not use Apple's libssl.so that comes with > > Leopard Server > > > Because the goal of the MacPorts project is the contrary of that: > we should mess with the sources provided by third parties, not with > the binaries distributed by Apple! Guido, I am with you and agree with you. MacPorts should have the goal of being as independent as possible. And that reminds me then that I should take a closer look to see why the kaffe port will not build on Leopard, too (rather than using Apple Leopard Server's Tomcat, since I want to build Tomcat from MacPorts and it depends on Kaffe). I have tried to apply the rough workaround I suggested you; these > are the simple steps I followed: > > > * extract the sources of Apache with "sudo port extract apache2" Guido, this is fascinating! I was not aware of the command-line tool named "extract". I don't see it in my PATH on either my Tiger Server or Leopard Server system. I also don't see "extract" as a MacPort as in: $ port info extract > Error: Port extract not found > Could you point me (and the MacPorts mailing list) to where we can find the extract command-line tool? Thank you! * search where in the sources the option "-export-simbol-regex" > is defined with: > > grep -r "-export-symbols-regex" /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_www_apache2 > > ==> > > [...] > [...] /httpd-2.2.6/configure: test "x$silent" != "xyes" && echo " > setting MOD_SSL_LDADD to \"-export-symbols-regex ssl_module\"" > [...]/ httpd-2.2.6/configure: MOD_SSL_LDADD="-export-symbols-regex > ssl_module" > [...] /httpd-2.2.6/configure: apr_addto_bugger="-export-symbols- > regex ssl_module" > [...] > > > * as suspected, the option is used to build the ssl_module... > > > * let's edit the apache2 Portfile with "sudo port edit apache2" and > add our patch to the configure script in the Leopard section: > > platform darwin 9 { > depends_build-append port:gawk > post-extract { > reinplace "s|-export-symbols-regex ssl_module||g" $ > {worksrcpath}/configure > } > } > > > * after cleaning the apache2 port and compiling it, let's test it: > > sudo apachectl start > > > * no message errors about missing symbols: we got it! Guido, you are a hero of the day!!! I will also test your solution on Leopard Server and confirm that it works for me. If it works for you and also for me, then I think you (or I can do this for you if you are busy) should submit the patch to MacPorts Trac system. Thanks for helping to find the solution, T.M. -- > Guido > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080106/879cc121/attachment.html From tabithamc at gmail.com Sun Jan 6 14:09:24 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun Jan 6 14:07:11 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: <7fccb3000801061347q5af9f374x331a78fb71cbdf23@mail.gmail.com> References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> <0D7BAC06-6EA0-414F-8AE9-7C884FF55876@gmail.com> <7fccb3000801060212n15143c74w7eb5fd890dbf9fd1@mail.gmail.com> <7fccb3000801061124r11a9c97cm7999e2236d67c2fc@mail.gmail.com> <47C148C2-D589-4436-8963-F737C6B4FB40@gmail.com> <7fccb3000801061347q5af9f374x331a78fb71cbdf23@mail.gmail.com> Message-ID: <7fccb3000801061409l1bea56e4n6bab8983f1e97534@mail.gmail.com> On 1/6/08, Tabitha McNerney wrote: > > > > On 1/6/08, Guido Soranzio wrote: > > > > On Jan 6, 2008, at 8:24 PM, Tabitha McNerney wrote: > > > > > I just had an idea. Why not use Apple's libssl.so that comes with > > > Leopard Server > > > > > > Because the goal of the MacPorts project is the contrary of that: > > we should mess with the sources provided by third parties, not with > > the binaries distributed by Apple! > > > Guido, I am with you and agree with you. MacPorts should have the goal of > being as independent as possible. And that reminds me then that I should > take a closer look to see why the kaffe port will not build on Leopard, too > (rather than using Apple Leopard Server's Tomcat, since I want to build > Tomcat from MacPorts and it depends on Kaffe). > > > I have tried to apply the rough workaround I suggested you; these > > are the simple steps I followed: > > > > > > * extract the sources of Apache with "sudo port extract apache2" > > > Guido, this is fascinating! I was not aware of the command-line tool named > "extract". I don't see it in my PATH on either my Tiger Server or Leopard > Server system. I also don't see "extract" as a MacPort as in: > > $ port info extract > > Error: Port extract not found > > > > Could you point me (and the MacPorts mailing list) to where we can find > the extract command-line tool? Thank you! > Guido, sorry, my eyes missed it the first time reading through ... "extract" is a verb for the port command. Will try your solution today and confirm that it works for me too. Thank you, T.M. [SNIP] -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080106/9d250976/attachment-0001.html From jkh at apple.com Sun Jan 6 14:35:54 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Sun Jan 6 14:34:44 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: <7fccb3000801061347q5af9f374x331a78fb71cbdf23@mail.gmail.com> References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> <0D7BAC06-6EA0-414F-8AE9-7C884FF55876@gmail.com> <7fccb3000801060212n15143c74w7eb5fd890dbf9fd1@mail.gmail.com> <7fccb3000801061124r11a9c97cm7999e2236d67c2fc@mail.gmail.com> <47C148C2-D589-4436-8963-F737C6B4FB40@gmail.com> <7fccb3000801061347q5af9f374x331a78fb71cbdf23@mail.gmail.com> Message-ID: On Jan 6, 2008, at 1:47 PM, Tabitha McNerney wrote: > Guido, this is fascinating! I was not aware of the command-line tool > named "extract". I don't see it in my PATH on either my Tiger Server > or Leopard Server system. I also don't see "extract" as a MacPort as > in: "port help" is the command you want to use, not "port info" - that is for an entirely different namespace. - Jordan From jkh at apple.com Sun Jan 6 14:35:54 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Sun Jan 6 14:36:33 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: <7fccb3000801061347q5af9f374x331a78fb71cbdf23@mail.gmail.com> References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> <0D7BAC06-6EA0-414F-8AE9-7C884FF55876@gmail.com> <7fccb3000801060212n15143c74w7eb5fd890dbf9fd1@mail.gmail.com> <7fccb3000801061124r11a9c97cm7999e2236d67c2fc@mail.gmail.com> <47C148C2-D589-4436-8963-F737C6B4FB40@gmail.com> <7fccb3000801061347q5af9f374x331a78fb71cbdf23@mail.gmail.com> Message-ID: On Jan 6, 2008, at 1:47 PM, Tabitha McNerney wrote: > Guido, this is fascinating! I was not aware of the command-line tool > named "extract". I don't see it in my PATH on either my Tiger Server > or Leopard Server system. I also don't see "extract" as a MacPort as > in: "port help" is the command you want to use, not "port info" - that is for an entirely different namespace. - Jordan From eridius at macports.org Sun Jan 6 14:39:11 2008 From: eridius at macports.org (Kevin Ballard) Date: Sun Jan 6 14:36:59 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <2278A3E8-C19C-41C9-A06B-F7A0C166A2EC@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <2278A3E8-C19C-41C9-A06B-F7A0C166A2EC@CentosPrime.COM> Message-ID: That's rather interesting. The missing command name has changed. Looking a second time, ui_prefix is actually done the same way as ui_channels, with an if-else statement. It's actually just a about 10 lines after the ui_channels block. I'm going to make the same change there and see if that helps. Here's the diff: Index: src/macports1.0/macports.tcl =================================================================== --- src/macports1.0/macports.tcl (revision 32524) +++ src/macports1.0/macports.tcl (revision 32525) @@ -111,9 +111,9 @@ if {$nbchans == 0} { proc ::ui_$priority {str} {} } else { - if {[llength [info commands ui_prefix]] > 0} { + try { set prefix [ui_prefix $priority] - } else { + } catch * { set prefix [ui_prefix_default $priority] } On Jan 6, 2008, at 10:37 AM, Chris Janton wrote: > invalid command name "ui_prefix" -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com From pgijnxn02 at sneakemail.com Sun Jan 6 14:56:46 2008 From: pgijnxn02 at sneakemail.com (Joel Thibault (MacPorts)) Date: Sun Jan 6 14:54:34 2008 Subject: wireshark 0.99.7 problem (solved) Message-ID: <7a665ffc0801061456l4eee1be2gf9293b20b796bde4@mail.gmail.com> I had a problem upgrading wireshark from 0.99.6 to 0.99.7 but it's working now. I eventually solved it by uninstalling the existing wireshark, and installing the new version fresh. (I removed kerberos as well, which I installed as an attempted fix) I thought I'd share in case anyone else sees this or something similar. Hope it's useful to someone. ...begin problem... I have been trying to upgrade wireshark to the latest version with no luck. It appears that it needs Kerberos 5, but installing it didn't help. Here's the end of my output from sudo port -d upgrade -cuv wireshark: ---> Building wireshark with target all DEBUG: Executing org.macports.build (wireshark) DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.4' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/work/wireshark- 0.99.7" && nice -n 10 make all' /opt/local/bin/perl ./make-version.pl . Version configuration file version.conf not found. Using defaults. This is not a SVN build. svnversion.h is up-to-date. make all-recursive Making all in tools Making all in lemon make[3]: Nothing to be done for `all'. make[3]: Nothing to be done for `all-am'. Making all in wiretap make all-am make[3]: Nothing to be done for `all-am'. Making all in doc make[2]: Nothing to be done for `all'. Making all in epan Making all in crypt make[3]: Nothing to be done for `all'. Making all in ftypes make[3]: Nothing to be done for `all'. Making all in dfilter make[3]: Nothing to be done for `all'. Making all in dissectors make all-am make[4]: Nothing to be done for `all-am'. make[3]: Nothing to be done for `all-am'. Making all in plugins Making all in agentx /bin/sh ../../libtool --tag=CC --mode=link ccache /usr/bin/gcc-4.0 -no-cpp-precomp -D_U_="__attribute__((unused))" -O2 -Wall -W -Wdeclaration-after-statement -Wendif-labels -Wpointer-arith -Wno-pointer-sign -DXTHREADS -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/pango-1.0 -I/opt/local/include/glib-2.0-I/opt/local/lib/glib- 2.0/include -I/opt/local/include -I/opt/local/include/freetype2 -I/opt/local/include/libpng12 -I/usr/X11R6/include -I/opt/local/include -I/opt/local/include -module -avoid-version -Wl,-search_paths_first -L/opt/local/lib -Wl,-search_paths_first -L/opt/local/lib -L/opt/local/lib -o agentx.la -rpath /opt/local/lib/wireshark/plugins/0.99.7 plugin.lo packet-agentx.lo -L../../epan -lwireshark -L/opt/local/lib -lgmodule-2.0 - lglib-2.0 -lintl -liconv grep: /opt/local/lib/libkrb5.la: No such file or directory sed: /opt/local/lib/libkrb5.la: No such file or directory libtool: link: `/opt/local/lib/libkrb5.la' is not a valid libtool archive make[3]: *** [agentx.la] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/work/wireshark- 0.99.7" && nice -n 10 make all " returned error 2 Command output: Making all in tools Making all in lemon make[3]: Nothing to be done for `all'. make[3]: Nothing to be done for `all-am'. Making all in wiretap make all-am make[3]: Nothing to be done for `all-am'. Making all in doc make[2]: Nothing to be done for `all'. Making all in epan Making all in crypt make[3]: Nothing to be done for `all'. Making all in ftypes make[3]: Nothing to be done for `all'. Making all in dfilter make[3]: Nothing to be done for `all'. Making all in dissectors make all-am make[4]: Nothing to be done for `all-am'. make[3]: Nothing to be done for `all-am'. Making all in plugins Making all in agentx /bin/sh ../../libtool --tag=CC --mode=link ccache /usr/bin/gcc-4.0 -no-cpp-precomp -D_U_="__attribute__((unused))" -O2 -Wall -W -Wdeclaration-after-statement -Wendif-labels -Wpointer-arith -Wno-pointer-sign -DXTHREADS -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/pango-1.0 -I/opt/local/include/glib-2.0-I/opt/local/lib/glib- 2.0/include -I/opt/local/include -I/opt/local/include/freetype2 -I/opt/local/include/libpng12 -I/usr/X11R6/include -I/opt/local/include -I/opt/local/include -module -avoid-version -Wl,-search_paths_first -L/opt/local/lib -Wl,-search_paths_first -L/opt/local/lib -L/opt/local/lib -o agentx.la -rpath /opt/local/lib/wireshark/plugins/0.99.7 plugin.lo packet-agentx.lo -L../../epan -lwireshark -L/opt/local/lib -lgmodule-2.0 - lglib-2.0 -lintl -liconv grep: /opt/local/lib/libkrb5.la: No such file or directory sed: /opt/local/lib/libkrb5.la: No such file or directory libtool: link: `/opt/local/lib/libkrb5.la' is not a valid libtool archive make[3]: *** [agentx.la] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Warning: the following items did not execute (for wireshark): org.macports.archive org.macports.build org.macports.destroot DEBUG: Registry error: xorg not registered as installed. invoked from within "registry_installed ${portname}" invoked from within "$workername eval registry_installed \${portname}" Error: Unable to upgrade port: 1 I'm running OS X 10.4 on a Mac Mini G4 with MacPorts 1.600. ...end problem... -- Joel Thibault [AIM: Jole Tebo] Software Engineer in Boston -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080106/9e679e10/attachment.html From tabithamc at gmail.com Sun Jan 6 15:13:34 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun Jan 6 15:11:23 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> <0D7BAC06-6EA0-414F-8AE9-7C884FF55876@gmail.com> <7fccb3000801060212n15143c74w7eb5fd890dbf9fd1@mail.gmail.com> <7fccb3000801061124r11a9c97cm7999e2236d67c2fc@mail.gmail.com> <47C148C2-D589-4436-8963-F737C6B4FB40@gmail.com> <7fccb3000801061347q5af9f374x331a78fb71cbdf23@mail.gmail.com> Message-ID: <7fccb3000801061513n67698d8ev7f91300075c8400e@mail.gmail.com> On 1/6/08, Jordan K. Hubbard wrote: > > > On Jan 6, 2008, at 1:47 PM, Tabitha McNerney wrote: > > > Guido, this is fascinating! I was not aware of the command-line tool > > named "extract". I don't see it in my PATH on either my Tiger Server > > or Leopard Server system. I also don't see "extract" as a MacPort as > > in: > > "port help" is the command you want to use, not "port info" - that is > for an entirely different namespace. > > - Jordan Jordan, In a week you have graciously twice reinforced the importance of namespaces (besides this thread, also the thread about Unix usernames using underscores in Leopard such as _postfix). Thank you for making the world a better place and helping educate people in the MacPorts community these important concepts (it makes the community stronger, and is such a welcome relief to the legacy approach to the world that some have taken such as Microsoft). Its great to be working with Xserves, iMacs, Macbooks, OS X and MacPorts! Best, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080106/0fb0f74c/attachment-0001.html From ryandesign at macports.org Sun Jan 6 14:56:17 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Jan 6 15:21:19 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <2278A3E8-C19C-41C9-A06B-F7A0C166A2EC@CentosPrime.COM> Message-ID: <499F1268-6A49-460D-89DB-8C416F3B1EC2@macports.org> On Jan 6, 2008, at 16:39, Kevin Ballard wrote: > On Jan 6, 2008, at 10:37 AM, Chris Janton wrote: > >> invalid command name "ui_prefix" > > That's rather interesting. The missing command name has changed. Whoops! You're right. I totally didn't pay attention there. > Looking a second time, ui_prefix is actually done the same way as > ui_channels, with an if-else statement. It's actually just a about > 10 lines after the ui_channels block. I'm going to make the same > change there and see if that helps. Here's the diff: > > Index: src/macports1.0/macports.tcl > =================================================================== > --- src/macports1.0/macports.tcl (revision 32524) > +++ src/macports1.0/macports.tcl (revision 32525) > @@ -111,9 +111,9 @@ > if {$nbchans == 0} { > proc ::ui_$priority {str} {} > } else { > - if {[llength [info commands ui_prefix]] > 0} { > + try { > set prefix [ui_prefix $priority] > - } else { > + } catch * { > set prefix [ui_prefix_default $priority] > } From george at galis.org Sun Jan 6 15:30:00 2008 From: george at galis.org (George Georgalis) Date: Sun Jan 6 15:27:48 2008 Subject: problem building gnupod Message-ID: <20080106233000.GC3137@run.duo> I'm not sure what the problem is here, expat is installed (subversion, at least, is using it) but p5-xml-parser won't go in because it cannot find it. I've tried exporting EXPATLIBPATH and EXPATINCPATH but still no cookie. (I have synced and cleaned installed too.) What could be wrong? // George geo@fuji:/Users/geo port installed expat The following ports are currently installed: expat @2.0.0_1 expat @2.0.1_0 (active) geo@fuji:/Users/geo sudo port outdated The following installed ports are outdated: gmp 4.2.2_0 < 4.2.2_1 libpcap 0.9.5_1 < 0.9.8_0 R 2.5.1_0 < 2.6.1_0 tcl 8.4.16_0 < 8.5.0_0 urw-fonts 1.0.7pre43_0 < 1.0.7pre44_0 vim 7.1.175_0 < 7.1.203_0 xrender 0.9.0_1 < 0.9.0_2 geo@fuji:/Users/geo sudo port install gnupod Password: ---> Configuring p5-xml-parser Error: Target org.macports.configure returned: configure failure: shell command " cd "/usr/local/MacPorts/var/macports/build/_usr_local_MacPorts_var_macports_sources_rsync.macports.org_release_ports_perl_p5-xml-parser/work/XML-Parser-2.36" && /usr/local/MacPorts/bin/perl Makefile.PL INSTALLDIRS=vendor " returned error 2 Command output: Note (probably harmless): No library found for -lexpat Expat must be installed prior to building XML::Parser and I can't find it in the standard library directories. You can download expat from: http://sourceforge.net/projects/expat/ If expat is installed, but in a non-standard directory, then use the following options to Makefile.PL: EXPATLIBPATH=... To set the directory in which to find libexpat EXPATINCPATH=... To set the directory in which to find expat.h For example: perl Makefile.PL EXPATLIBPATH=/home/me/lib EXPATINCPATH=/home/me/include Note that if you build against a shareable library in a non-standard location you may (on some platforms) also have to set your LD_LIBRARY_PATH environment variable at run time for perl to find the library. Error: The following dependencies failed to build: p5-xml-parser Error: Status 1 encountered during processing. -- George Georgalis, information system scientist < From lisfolks.lists at gmail.com Sun Jan 6 15:47:08 2008 From: lisfolks.lists at gmail.com (LeAnne Lis) Date: Sun Jan 6 15:44:56 2008 Subject: Error building p5-sdl_perl In-Reply-To: <4780C334.60907@macports.org> References: <14610995.post@talk.nabble.com> <4780C334.60907@macports.org> Message-ID: <14655745.post@talk.nabble.com> Pierre Queinnec-3 wrote: > > As for your bug, it is clearly different. Could you file a ticket and > assign it to me? > I'm not able to enter tickets - it asks for a login and password. Unless I missed it, I don't see how one signs up to be able to put in tickets. How would I do that? -- View this message in context: http://www.nabble.com/Error-building-p5-sdl_perl-tp14610995p14655745.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From ryandesign at macports.org Sun Jan 6 15:56:20 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Jan 6 15:54:41 2008 Subject: Error building p5-sdl_perl In-Reply-To: <14655745.post@talk.nabble.com> References: <14610995.post@talk.nabble.com> <4780C334.60907@macports.org> <14655745.post@talk.nabble.com> Message-ID: On Jan 6, 2008, at 17:47, LeAnne Lis wrote: > Pierre Queinnec wrote: > >> As for your bug, it is clearly different. Could you file a ticket and >> assign it to me? > > I'm not able to enter tickets - it asks for a login and password. > Unless I > missed it, I don't see how one signs up to be able to put in > tickets. How > would I do that? You do need to log in to file bugs, yes. I believe you would click the Register link at the top right of any of our Trac pages to create one. From face at CentosPrime.COM Sun Jan 6 16:08:36 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sun Jan 6 16:06:38 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <03D498F4-869A-4399-A7FB-2E4D58FDD139@macports.org> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <"D6D36799-CD42-497F-B20B-0 4F908060822"@macports.org> Message-ID: <10C181CA-996C-406B-BC08-FC6B28E458AA@CentosPrime.COM> On 2008-01-06 , at 14:44 , Ryan Schmidt wrote: > Ok, so you've discovered that Kevin's latest attempt did not fix > the issue. > > Perhaps you could try what I suggested to discover which change > caused the issue in the first place? > > http://lists.macosforge.org/pipermail/macports-users/2008-January/ > 008061.html > Probably what we should do first is determine the specific commit / > revision / changeset that broke the build on Panther. I don't think > we've established that yet. My wild guess was revision 29498. To test > whether that's the culprit, check out trunk at r29497 and build it on > Panther. If it builds, then check out trunk at r29498 and build it. > If it fails, then r29498 broke the build, and we can further analyze > the changes made in that revision. > OK. I can do that. Just a tiny bit more help (I'm good at following directions, but not so good at understanding the ins and outs of svn) How do I "check out trunk at r29497" I assume that the configure, make, sudo make install apply for all of the tests. Once I figure out how to check out the right copy of the source I can apply the same method again (and again, and again...) Thanks. 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From paulbeard at gmail.com Sun Jan 6 16:11:22 2008 From: paulbeard at gmail.com (paul beard) Date: Sun Jan 6 16:09:09 2008 Subject: dbus-glib hangs In-Reply-To: <6197D687-517C-48D6-98B0-2F70CAC0A7AE@macports.org> References: <6197D687-517C-48D6-98B0-2F70CAC0A7AE@macports.org> Message-ID: Well, anyone who uses any of these: gnome-terminal depends on dbus-glib dasher depends on dbus-glib gcalctool depends on dbus-glib gnome-games depends on dbus-glib gnome-media depends on dbus-glib gnopernicus depends on dbus-glib libgtkhtml3 depends on dbus-glib libgail-gnome depends on dbus-glib control-center depends on dbus-glib libgtkhtml3 depends on dbus-glib gnome-keyring-manager depends on dbus-glib libgtkhtml3 depends on dbus-glib libgnome depends on dbus-glib libgsf depends on dbus-glib gnome-games depends on dbus-glib file-roller depends on dbus-glib gconf-editor depends on dbus-glib libgtkhtml3 depends on dbus-glib gucharmap depends on dbus-glib file-roller depends on dbus-glib file-roller depends on dbus-glib gnome-vfs depends on dbus-glib libgnome depends on dbus-glib libgsf depends on dbus-glib gnome-vfs depends on dbus-glib libgnome depends on dbus-glib file-roller depends on dbus-glib gnome-keyring-manager depends on dbus-glib libgtkhtml3 depends on dbus-glib dbus-python25 depends on dbus-glib gcalctool depends on dbus-glib libgnome depends on dbus-glib gedit depends on dbus-glib gnome-session depends on dbus-glib libbonoboui depends on dbus-glib gnome-applets depends on dbus-glib gnome-desktop depends on dbus-glib gnome-panel depends on dbus-glib libgnome depends on dbus-glib gnome-utils depends on dbus-glib nautilus depends on dbus-glib seahorse depends on dbus-glib eel depends on dbus-glib evince depends on dbus-glib avahi depends on dbus-glib gnome-system-monitor depends on dbus-glib uses dbus-glib. It looks like gimp2 is what's blocked for me. I'll see if I can find where to file a bug. On 1/5/08, Ryan Schmidt wrote: > > On Jan 5, 2008, at 23:43, paul beard wrote: > > > The maintainer is the ever-popular "nomaintainer" so I have no idea > > who should get this. And I couldn't access TRAC to look for or file a > > ticket. > > It's this bug: > > http://trac.macosforge.org/projects/macports/ticket/13448 > > and this bug: > > http://trac.macosforge.org/projects/macports/ticket/13566 > > and it's apparently a bad interaction between dbus-glib and glib- > genmarshal from glib 2.14.4. glib-genmarshal from glib 2.14.2 > apparently works fine. I maintain glib2 but I don't know what to do > about this problem. I filed a bug with the developers of glib2 but it > doesn't sound like it's their bug. I guess I should file a bug with > the developers of dbus-glib next. Since I don't use dbus-glib, > though, nor know anything about it, it might be better if someone who > actually uses and knows something about the software were to file the > bug and interact with the dbus-glib developers to resolve it. > > -- Paul Beard / www.paulbeard.org/ From ajmas at sympatico.ca Sun Jan 6 16:22:43 2008 From: ajmas at sympatico.ca (Andre-John Mas) Date: Sun Jan 6 16:20:30 2008 Subject: Apache2 & IPv6 In-Reply-To: References: <550EE147-DA7D-4CB7-857C-9C564B894086@sympatico.ca> <0372F219-86BE-4D2F-8DE3-0FA396BFB008@macports.org> Message-ID: On 6-Jan-08, at 03:21 , Bryan Blackburn wrote: > > On Jan 5, 2008, at 11:13 PM, Ryan Schmidt wrote: > >> On Jan 5, 2008, at 23:44, Andre-John Mas wrote: >> >>> I noticed that there is no variant of Apache2 allowing for IPv6 >>> support. Is there any >>> chance one could be added? >> >> If this is not already possible with the standard apache2, then you >> should file an enhancement request ticket in our issue tracker and >> assign it to the maintainer of the apache2 port. >> > > It should be the default, as it's working fine with my install: > > $ telnet ::1 80 > Trying ::1... > Connected to localhost. Yup its working when I do that, so IPv6 is present, though I can't seem to connect from my other Mac. I'll have to investigate. Andre From ryandesign at macports.org Sun Jan 6 16:25:13 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Jan 6 16:23:35 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <10C181CA-996C-406B-BC08-FC6B28E458AA@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <"D6D36799-CD42-497F-B20B- 0 4F908060822"@macports.org> <10C181CA-996C-406B-BC08-FC6B28E458AA@CentosPrime.COM> Message-ID: On Jan 6, 2008, at 18:08, Chris Janton wrote: > On 2008-01-06 , at 14:44 , Ryan Schmidt wrote: > >> Ok, so you've discovered that Kevin's latest attempt did not fix >> the issue. >> >> Perhaps you could try what I suggested to discover which change >> caused the issue in the first place? >> >> http://lists.macosforge.org/pipermail/macports-users/2008-January/ >> 008061.html > > >> Probably what we should do first is determine the specific commit / >> revision / changeset that broke the build on Panther. I don't think >> we've established that yet. My wild guess was revision 29498. To test >> whether that's the culprit, check out trunk at r29497 and build it on >> Panther. If it builds, then check out trunk at r29498 and build it. >> If it fails, then r29498 broke the build, and we can further analyze >> the changes made in that revision. > > OK. I can do that. Just a tiny bit more help (I'm good at following > directions, but not so good at understanding the ins and outs of svn) > > How do I > > "check out trunk at r29497" > > I assume that the configure, make, sudo make install apply for all > of the tests. > Once I figure out how to check out the right copy of the source I > can apply the same method again (and again, and again...) Well, nevermind, since I wasn't paying attention, and the error message you're getting now is different from the error message you were getting before, so it looks like Kevin did find the cause, and he has committed hopefully a fix for the next error you're seeing, and you should just update your working copy of base and build and install it (cd base; make clean; svn update; ./configure --enable- readline etc etc; make; make install; try using port again). FYI, if you wanted to get a different (previous) revision, you would e.g. "svn update -r 29497" instead of "svn update". From dnb at ccs.neu.edu Sun Jan 6 18:02:09 2008 From: dnb at ccs.neu.edu (David Blank-Edelman) Date: Sun Jan 6 18:00:09 2008 Subject: Bus Errors with Perl/Tk In-Reply-To: <20080106231126.C92EF17D4E4@lists.macosforge.org> References: <20080106231126.C92EF17D4E4@lists.macosforge.org> Message-ID: <12E11F0D-739B-4C38-B4E9-0EEA79D4C647@ccs.neu.edu> Hi- I haven't seen any mention of this in the archives, so I'm wondering if anyone else has seen this problem. I'm trying to run another package from MacPorts called "cssh" which is essentially a Perl/Tk script. I've done every permutation of install/uninstall/clean I can think of for perl5.8, tcl/tk8.5 and p5-tk but I still get a situation where every Perl/Tk script (even as simple as just "use Tk;") bites the dust with this backtrace: rogram received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000000 0x003f550f in boot_Tk__Event () (gdb) bt #0 0x003f550f in boot_Tk__Event () #1 0x00077f3f in Perl_pp_entersub () #2 0x0006f295 in Perl_runops_standard () #3 0x0000466a in Perl_call_sv () #4 0x0000495d in Perl_call_list () #5 0x0003f36c in Perl_newATTRSUB () #6 0x0003fc9f in Perl_utilize () #7 0x0002d8c8 in Perl_yyparse () #8 0x000a3f35 in S_doeval () #9 0x000abc30 in Perl_pp_require () #10 0x0006f295 in Perl_runops_standard () #11 0x0000466a in Perl_call_sv () #12 0x0000495d in Perl_call_list () #13 0x0003f36c in Perl_newATTRSUB () #14 0x0003fc9f in Perl_utilize () #15 0x0002d8c8 in Perl_yyparse () #16 0x0000847e in S_parse_body () #17 0x00009c66 in perl_parse () #18 0x0000197f in main () I have a sneaking suspicion that this may either be: 1) due to a mismatch between p5-tk which describes itself as being version 804.027 and Tk which is 8.5.0. 2) related to the Tk 8.5 upgrade problem (http://trac.macports.org/projects/macports/ticket/13678 ) which also bit me 3) be a conflict with something that ships with Leopard p5-tk doesn't appear to have a maintainer so I have to throw myself on the mercy of the mailing list. Does anybody have any suggestions on how to fix or at least start tracking down the problem? Thanks for any help you can offer. -- dNb From eridius at macports.org Sun Jan 6 18:09:47 2008 From: eridius at macports.org (Kevin Ballard) Date: Sun Jan 6 18:07:35 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <10C181CA-996C-406B-BC08-FC6B28E458AA@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <"D6D36799-CD42-497F-B20B- 0 4F908060822"@macports.org> <10C181CA-996C-406B-BC08-FC6B28E458AA@CentosPrime.COM> Message-ID: <8A820A63-E716-4673-9B9A-FFA2D943832E@macports.org> Once you have svn installed, simply navigate to the directory you want to check out the source into (into a subfolder, that is) and run the following command: svn checkout http://svn.macports.org/repository/macports/trunk/base macports This will check out the macports source into a folder called macports. You can then execute the following: cd macports ./configure make sudo make install This will overwrite your previous macports installation (but leave your installed ports untouched). If you do this, you should continue to update your ports tree with `sudo port sync` but never run `sudo port selfupdate` or you risk overwriting your macports installation with a released version instead of one from source. To update to the latest in the future, simply run: cd path/to/macports svn update make sudo make install Please note that this is deliberately not giving you an svn checkout of the dports tree, in the interests of saving time. If you want a checkout of the dports tree itself, remove the trailing /base from the URL above, and instead navigate to macports/base before building. Of course, if you do this you also have to edit your /opt/local/etc/ macports/source.conf file to point to your dports checkout instead of the rsync server. -Kevin Ballard On Jan 6, 2008, at 7:08 PM, Chris Janton wrote: > On 2008-01-06 , at 14:44 , Ryan Schmidt wrote: > >> Ok, so you've discovered that Kevin's latest attempt did not fix >> the issue. >> >> Perhaps you could try what I suggested to discover which change >> caused the issue in the first place? >> >> http://lists.macosforge.org/pipermail/macports-users/2008-January/008061.html > > >> Probably what we should do first is determine the specific commit / >> revision / changeset that broke the build on Panther. I don't think >> we've established that yet. My wild guess was revision 29498. To test >> whether that's the culprit, check out trunk at r29497 and build it on >> Panther. If it builds, then check out trunk at r29498 and build it. >> If it fails, then r29498 broke the build, and we can further analyze >> the changes made in that revision. >> > > OK. I can do that. Just a tiny bit more help (I'm good at following > directions, but not so good at understanding the ins and outs of svn) > > How do I > > "check out trunk at r29497" > > I assume that the configure, make, sudo make install apply for all > of the tests. > Once I figure out how to check out the right copy of the source I > can apply the same method again (and again, and again...) > > Thanks. > > 8) > ---------------------------------- > Chris Janton - face at CentosPrime dot COM > Netminder for Opus1.COM > > -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com From face at CentosPrime.COM Sun Jan 6 19:39:38 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sun Jan 6 19:37:44 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <"D6D36799-CD42-497F-B20B-0 4F908060822"@macports.org> Message-ID: On 2008-01-06 , at 17:25 , Ryan Schmidt wrote: > Well, nevermind, since I wasn't paying attention, and the error > message you're getting now is different from the error message you > were getting before, so it looks like Kevin did find the cause, and > he has committed hopefully a fix for the next error you're seeing, > and you should just update your working copy of base and build and > install it (cd base; make clean; svn update; ./configure --enable- > readline etc etc; make; make install; try using port again). looks like the latest change has done something. I updated the source, etc. house54 15 # port version Version: 1.700 house54 16 # sudo port install coreutils ---> Fetching coreutils ---> Attempting to fetch coreutils-6.9.tar.bz2 from http:// ftp.gnu.org/gnu/coreutils and it is running now (configuring). 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From tabithamc at gmail.com Sun Jan 6 20:17:36 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun Jan 6 20:15:24 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: <47C148C2-D589-4436-8963-F737C6B4FB40@gmail.com> References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> <0D7BAC06-6EA0-414F-8AE9-7C884FF55876@gmail.com> <7fccb3000801060212n15143c74w7eb5fd890dbf9fd1@mail.gmail.com> <7fccb3000801061124r11a9c97cm7999e2236d67c2fc@mail.gmail.com> <47C148C2-D589-4436-8963-F737C6B4FB40@gmail.com> Message-ID: <7fccb3000801062017k70d3ae25vca878f2f5dd0611a@mail.gmail.com> Guido, I can confirm that your solution that you eloquently described aforementioned works perfectly -- the namespace error when running Apache2 with mod_ssl.so loaded on Leopard Server (10.5.1 Server) with MacPorts 1.6.0apache version 2.2.6 is alleviated completely. I think ticket # 13182 should be updated per your solution. However, please note that I have not yet tried to do anything over SSL with certificates, etc. Also, I am not sure if this will alleviate the perhaps related problem with Subversion when communicating with Subversion over SSL with Apache (or there is also the option to communicate with Subversion over SSL independent of Apache's mod_dav_svn.so module): http://subversion.tigris.org/faq.html#ssl-negotiation-error When performing Subversion operations involving a lot of data over SSL, I > get the error SSL negotiation failed: SSL error: decryption failed or bad > record mac. > This can occur due to a problem with OpenSSL 0.9.8. Downgrading to an > older version (or possibly upgrading to a newer version) is known to fix > this issue. > So maybe for now its best to treat the SSL / Subversion problem separate from Apache-with-SSL-and-Subversion. I have some additional tickets to contribute information to later today so I will add your fix to ticket 13182 unless you prefer to do this. Thanks, T.M. On 1/6/08, Guido Soranzio wrote: > > On Jan 6, 2008, at 8:24 PM, Tabitha McNerney wrote: > > > I just had an idea. Why not use Apple's libssl.so that comes with > > Leopard Server > > > Because the goal of the MacPorts project is the contrary of that: > we should mess with the sources provided by third parties, not with > the binaries distributed by Apple! > > I have tried to apply the rough workaround I suggested you; these > are the simple steps I followed: > > > * extract the sources of Apache with "sudo port extract apache2" > > > * search where in the sources the option "-export-simbol-regex" > is defined with: > > grep -r "-export-symbols-regex" /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_www_apache2 > > ==> > > [...] > [...] /httpd-2.2.6/configure: test "x$silent" != "xyes" && echo " > setting MOD_SSL_LDADD to \"-export-symbols-regex ssl_module\"" > [...]/ httpd-2.2.6/configure: MOD_SSL_LDADD="-export-symbols-regex > ssl_module" > [...] /httpd-2.2.6/configure: apr_addto_bugger="-export-symbols- > regex ssl_module" > [...] > > > * as suspected, the option is used to build the ssl_module... > > > * let's edit the apache2 Portfile with "sudo port edit apache2" and > add our patch to the configure script in the Leopard section: > > platform darwin 9 { > depends_build-append port:gawk > post-extract { > reinplace "s|-export-symbols-regex ssl_module||g" $ > {worksrcpath}/configure > } > } > > > * after cleaning the apache2 port and compiling it, let's test it: > > sudo apachectl start > > > * no message errors about missing symbols: we got it! > > > -- > Guido > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080106/6115b4c2/attachment.html From lisfolks.lists at gmail.com Sun Jan 6 20:33:17 2008 From: lisfolks.lists at gmail.com (LeAnne Lis) Date: Sun Jan 6 20:31:03 2008 Subject: Error building p5-sdl_perl In-Reply-To: References: <14610995.post@talk.nabble.com> <4780C334.60907@macports.org> <14655745.post@talk.nabble.com> Message-ID: <14658708.post@talk.nabble.com> Ryan Schmidt-24 wrote: > > > On Jan 6, 2008, at 17:47, LeAnne Lis wrote: > >> I'm not able to enter tickets - it asks for a login and password. >> Unless I >> missed it, I don't see how one signs up to be able to put in >> tickets. How >> would I do that? > > You do need to log in to file bugs, yes. I believe you would click > the Register link at the top right of any of our Trac pages to create > one. > That worked, Ryan. I have now registered and entered ticket #13854. -- View this message in context: http://www.nabble.com/Error-building-p5-sdl_perl-tp14610995p14658708.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From boeyms at macports.org Sun Jan 6 21:56:48 2008 From: boeyms at macports.org (Boey Maun Suang) Date: Sun Jan 6 21:54:34 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <"D6D36799-CD42-497F-B20B-0 4F908060822"@macports.org> Message-ID: <52377.128.250.31.223.1199685408.squirrel@webmail.tuffmail.net> Hi Chris, Ryan and Kevin, On Mon, January 7, 2008 2:39 pm, Chris Janton wrote: > > looks like the latest change has done something. > I updated the source, etc. > > house54 15 # port version > Version: 1.700 > house54 16 # sudo port install coreutils > ---> Fetching coreutils > ---> Attempting to fetch coreutils-6.9.tar.bz2 from http:// > ftp.gnu.org/gnu/coreutils > > and it is running now (configuring). Thanks so much for helping me out with fixing this! I won't be able to get to my Panther machine for another day or so, but once I do, I'll double-check that this fix works for me, and then prep the Panther DMG and source releases. Just out of curiosity, Kevin, any idea as to exactly why we were getting this problem? I wonder if there was a bug fixed between the tcl on 10.3.9 (which appears to be 8.4.4 [1], Chris can confirm this by running `info patchlevel` in tclsh) and the tcl on 10.4.11, which is 8.4.7. )I've looked briefly at the Tcl Changelog for that period, but it's awfully long.) Kind regards, Maun Suang [1] http://www.opensource.apple.com/darwinsource/10.3.9/tcl-14/tcl/ChangeLog -- Boey Maun Suang Email: boeyms@macports.org From eridius at macports.org Mon Jan 7 00:05:36 2008 From: eridius at macports.org (Kevin Ballard) Date: Mon Jan 7 00:03:23 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <52377.128.250.31.223.1199685408.squirrel@webmail.tuffmail.net> References: <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <"D6D36799-CD42-497F-B20B-0 4F908060822"@macports.org> <52377.128.250.31.223.119968540 8.squirrel@webmail.tuffmail.net> Message-ID: <78F97257-0779-4FDB-A876-BE46EB1AD3E9@macports.org> Glad to hear that it seems to be working now. I really don't know what was wrong, but obviously there was some bug with the info command on 10.3. The recent changes mean we no longer rely on the 'info commands' behaviour, so we should be good. -Kevin Ballard On Jan 7, 2008, at 12:56 AM, Boey Maun Suang wrote: > Thanks so much for helping me out with fixing this! I won't be able > to > get to my Panther machine for another day or so, but once I do, I'll > double-check that this fix works for me, and then prep the Panther > DMG and > source releases. > > Just out of curiosity, Kevin, any idea as to exactly why we were > getting > this problem? I wonder if there was a bug fixed between the tcl on > 10.3.9 > (which appears to be 8.4.4 [1], Chris can confirm this by running > `info > patchlevel` in tclsh) and the tcl on 10.4.11, which is 8.4.7. )I've > looked briefly at the Tcl Changelog for that period, but it's awfully > long.) -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com From jochen at fhi-berlin.mpg.de Mon Jan 7 00:27:54 2008 From: jochen at fhi-berlin.mpg.de (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Mon Jan 7 00:25:56 2008 Subject: Qt port? In-Reply-To: <68927630-F518-4FB4-8181-7AE6FFBA7131@alum.mit.edu> References: <68927630-F518-4FB4-8181-7AE6FFBA7131@alum.mit.edu> Message-ID: Hi Adam, > I just saw that there is a new Qt port available. It contains several small improvements, but for sqlite I retracted, for now, to your workaround to use Qt's shipped sqlite. > Does that mean that you got this problem figured out? No, not yet. I also, again, don't have much time to look into it. In case you, or sqliteman developers, want to look at it: the books demo of Qt needs to be debugged and it's sqlite calls should be verified manually against MacPorts sqlite3. I have to see when I can get back to this... Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080107/2dbda26a/PGP.bin From j.van_den_hoff at fzd.de Mon Jan 7 02:32:15 2008 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Mon Jan 7 02:30:07 2008 Subject: ocaml fails on Tiger (was: Re: sudo port install mldonkey) In-Reply-To: <903349F2-4D42-4AC6-AA07-DDE14D0C8D5E@macports.org> References: <590A936D-453F-4369-9E09-69E7D05001B2@gmail.com> <53DF8FAC-D824-438D-8AF1-6B62D94BC177@gmail.com> <903349F2-4D42-4AC6-AA07-DDE14D0C8D5E@macports.org> Message-ID: <20080107103215.GB9144@marco.fz-rossendorf.de> On Fri, Jan 04, 2008 at 12:05:14PM -0600, Ryan Schmidt wrote: > > On Jan 4, 2008, at 09:41, Charlse Darwin wrote: > > >On Dec 26, 2007, at 8:14 AM, Ryan Schmidt wrote: > > > >>This bug has already been reported: > >> > >>http://trac.macosforge.org/projects/macports/ticket/13583 > > > ># I installed ocaml from precompiled binary > > > ># > > > >$ sudo port clean --dist --archive --work mldonkey > >---> Cleaning mldonkey > >$ sudo port clean --dist --archive --work ocaml > >Password: > >---> Cleaning ocaml > >$ sudo port clean --dist --archive --work mldonkey > >---> Cleaning mldonkey > >Mac:~ pm$ sudo port -f install mldonkey > >---> Fetching ocaml > >---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// > >caml.inria.fr/pub/distrib/ocaml-3.10/ > >---> Verifying checksum(s) for ocaml > >---> Extracting ocaml > >---> Applying patches to ocaml > >---> Configuring ocaml > >Error: Target org.macports.configure returned: configure failure: > >shell command " cd "/opt/local/var/macports/build/ > >_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ > >ocaml/work/ocaml-3.10.0" && ./configure -prefix /opt/local -no-tk " > >returned error 2 > >Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) not > >balanced > >../gnu/config.sub: line 128: [: !=: unary operator expected > >Invalid configuration `powerpc-apple-darwin8.11.0': machine `' not > >recognized > >Please specify the correct host type with the -host option > > > >Error: The following dependencies failed to build: lablgtk ocaml > >Error: Status 1 encountered during processing. > >$ > > > ># How do I get it to skip ocaml? > > There isn't a built-in way to do that. MacPorts is designed not to > make use of any software you install outside of MacPorts. You could > possibly modify the portfile to look for ocaml in a different > directory. But what we would really like is for someone to figure out > why the ocaml port fails to build, and fix it. is there hope (i.e. is the package still actively maintained)? would it be helpful to "cross post" this issue on one of the ocaml lists asking for opinions/help? if so, where to send potential answers? to "pguyot@kallisys.net" as `port info ocaml' tells me? regards, joerg From tabithamc at gmail.com Mon Jan 7 03:07:09 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Mon Jan 7 03:04:54 2008 Subject: mod_ssl, Apache2 and Leopard with patch -- doesn't work In-Reply-To: <7fccb3000801062017k70d3ae25vca878f2f5dd0611a@mail.gmail.com> References: <7fccb3000801052227i9f378eaqe6bc46200e63f93b@mail.gmail.com> <7fccb3000801060123i4f163c83s83366a0db85b1c87@mail.gmail.com> <0D7BAC06-6EA0-414F-8AE9-7C884FF55876@gmail.com> <7fccb3000801060212n15143c74w7eb5fd890dbf9fd1@mail.gmail.com> <7fccb3000801061124r11a9c97cm7999e2236d67c2fc@mail.gmail.com> <47C148C2-D589-4436-8963-F737C6B4FB40@gmail.com> <7fccb3000801062017k70d3ae25vca878f2f5dd0611a@mail.gmail.com> Message-ID: <7fccb3000801070307i56d9fccfgc58332017ba4349a@mail.gmail.com> Hello Guido and all others interested ... I have amended Ticket numbers: 13182 and 11755 per this thread. Thanks, T.M. On 1/6/08, Tabitha McNerney wrote: > > Guido, > > I can confirm that your solution that you eloquently described > aforementioned works perfectly -- the namespace error when running Apache2 > with mod_ssl.so loaded on Leopard Server (10.5.1 Server) with MacPorts > 1.6.0 apache version 2.2.6 is alleviated completely. I think ticket # > 13182 should be updated per your solution. > > However, please note that I have not yet tried to do anything over SSL > with certificates, etc. Also, I am not sure if this will alleviate the > perhaps related problem with Subversion when communicating with Subversion > over SSL with Apache (or there is also the option to communicate with > Subversion over SSL independent of Apache's mod_dav_svn.so module): > > http://subversion.tigris.org/faq.html#ssl-negotiation-error > > When performing Subversion operations involving a lot of data over SSL, I > > get the error SSL negotiation failed: SSL error: decryption failed or bad > > record mac. > > This can occur due to a problem with OpenSSL 0.9.8. Downgrading to an > > older version (or possibly upgrading to a newer version) is known to fix > > this issue. > > > > So maybe for now its best to treat the SSL / Subversion problem separate > from Apache-with-SSL-and-Subversion. > > I have some additional tickets to contribute information to later today so > I will add your fix to ticket 13182 unless you prefer to do this. > > Thanks, > > T.M. > > On 1/6/08, Guido Soranzio wrote: > > > > On Jan 6, 2008, at 8:24 PM, Tabitha McNerney wrote: > > > > > I just had an idea. Why not use Apple's libssl.so that comes with > > > Leopard Server > > > > > > Because the goal of the MacPorts project is the contrary of that: > > we should mess with the sources provided by third parties, not with > > the binaries distributed by Apple! > > > > I have tried to apply the rough workaround I suggested you; these > > are the simple steps I followed: > > > > > > * extract the sources of Apache with "sudo port extract apache2" > > > > > > * search where in the sources the option "-export-simbol-regex" > > is defined with: > > > > grep -r "-export-symbols-regex" /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync > > .macports.org_release_ports_www_apache2 > > > > ==> > > > > [...] > > [...] /httpd-2.2.6/configure: test "x$silent" != "xyes" && echo " > > setting MOD_SSL_LDADD to \"-export-symbols-regex ssl_module\"" > > [...]/ httpd-2.2.6/configure: MOD_SSL_LDADD="-export-symbols-regex > > ssl_module" > > [...] /httpd-2.2.6/configure: apr_addto_bugger="-export-symbols- > > regex ssl_module" > > [...] > > > > > > * as suspected, the option is used to build the ssl_module... > > > > > > * let's edit the apache2 Portfile with "sudo port edit apache2" and > > add our patch to the configure script in the Leopard section: > > > > platform darwin 9 { > > depends_build-append port:gawk > > post-extract { > > reinplace "s|-export-symbols-regex ssl_module||g" $ > > {worksrcpath}/configure > > } > > } > > > > > > * after cleaning the apache2 port and compiling it, let's test it: > > > > sudo apachectl start > > > > > > * no message errors about missing symbols: we got it! > > > > > > -- > > Guido > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080107/01b60113/attachment.html From tabithamc at gmail.com Mon Jan 7 03:15:22 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Mon Jan 7 03:19:35 2008 Subject: enscript fails to build on Leopard Server Message-ID: <7fccb3000801070315l3840241fvd25a68b0fb3ea8d3@mail.gmail.com> For anyone who might be interested, I just filed a new bug report, Ticket #13855 regarding building the enscript port (quite popular if I recall correctly when used with Trac), as it doesn't want to build on my system (MacPorts 1.6.0 and Leopard Server 10.5.1). Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080107/33ebb281/attachment-0001.html From tabithamc at gmail.com Mon Jan 7 03:58:19 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Mon Jan 7 03:56:06 2008 Subject: mod_python fails to build on Leopard Message-ID: <7fccb3000801070358lc11bc56v39280508cf7cb7d@mail.gmail.com> For anyone that may be interested, I filed a bug report, Ticket #13856, regarding attempts to build the mod_python port for use with Apache 2 on a fresh system of MacPorts 1.6.0 on Leopard Server 10.5.1 Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080107/5db8af66/attachment.html From tabithamc at gmail.com Mon Jan 7 04:27:32 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Mon Jan 7 04:25:17 2008 Subject: kaffe won't build / install on Leopard Server 10.5.1 (can someone help me delete an accidental duplicate Ticket?) Message-ID: <7fccb3000801070427r404b477fu49f5d2b808da16f2@mail.gmail.com> For anyone who might be interested, I added a bug report as Ticket #13858with regard to the Kaffe port not building / installing on Leopard Server. I made a mistake at first by trying to upload as an attachment to this original ticket (which was ticket #13857) a large verbose output file from my Terminal but it exceeded the maximum file size alloted by the MacPorts Trac system. Can anyone with the appropriate editorial authority in the Trac system (maybe Ryan or Jordan?) delete Ticket #13857 since that ticket is an accidental duplicate whereby the file was not accepted? Thanks very much, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080107/40e186a0/attachment.html From raimue at macports.org Mon Jan 7 04:32:25 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Mon Jan 7 04:30:23 2008 Subject: kaffe won't build / install on Leopard Server 10.5.1 (can someone help me delete an accidental duplicate Ticket?) In-Reply-To: <7fccb3000801070427r404b477fu49f5d2b808da16f2@mail.gmail.com> References: <7fccb3000801070427r404b477fu49f5d2b808da16f2@mail.gmail.com> Message-ID: <47821BD9.6010408@macports.org> Tabitha McNerney wrote: > Can anyone with the appropriate editorial authority in the Trac system ( > maybe Ryan or Jordan?) delete Ticket #13857 since that ticket is an > accidental duplicate whereby the file was not accepted? Marked it as duplicate and closed the ticket. Rainer From tabithamc at gmail.com Mon Jan 7 04:39:56 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Mon Jan 7 04:37:41 2008 Subject: kaffe won't build / install on Leopard Server 10.5.1 (can someone help me delete an accidental duplicate Ticket?) In-Reply-To: <47821BD9.6010408@macports.org> References: <7fccb3000801070427r404b477fu49f5d2b808da16f2@mail.gmail.com> <47821BD9.6010408@macports.org> Message-ID: <7fccb3000801070439y40e0cc95q64787b764840ec51@mail.gmail.com> On 1/7/08, Rainer M?ller wrote: > > Tabitha McNerney wrote: > > Can anyone with the appropriate editorial authority in the Trac system ( > > maybe Ryan or Jordan?) delete Ticket #13857 since that ticket is an > > accidental duplicate whereby the file was not accepted? > > Marked it as duplicate and closed the ticket. > > Rainer Thanks Rainer, that was quick! T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080107/50539beb/attachment.html From muffetta66 at email.it Mon Jan 7 04:48:12 2008 From: muffetta66 at email.it (muffetta66) Date: Mon Jan 7 04:46:32 2008 Subject: Problems using macports Message-ID: <47821F8C.9020600@email.it> Hallo, i've a problem after installing macports 1.600 When i tring to install my first package (Midnight Commander), this was the output: ibook-g4-di-*************-********:~ *************$ sudo port install mc Password: ---> Extracting libiconv Error: Target org.macports.extract returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libiconv/work" && gzip -dc /opt/local/var/macports/distfiles/libiconv/libiconv-1.12.tar.gz | -xf - " returned error 127 Command output: sh: line 1: -xf: command not found gzip: stdout: Broken pipe Error: The following dependencies failed to build: glib2 gettext libiconv pkgconfig Error: Status 1 encountered during processing. The macports installation is correct and at the last version (1.600). Someone knows how can i solve this problem? editing wich file?, because it should be a missing in the main installation script that broke the pipe (this occurr also with all other ports). The system is: iBook G4 Power PC 933Mhz 640 SDRAM Mac OS X 10.4.11 Thanks in advantage. -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Prestiti Finatel? Fino a 50.000 Euro, rate su misura, zero spese, anche protestati e cattivi pagatori, in pochissimo tempo. Scoprili on line * Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=7373&d=7-1 From face at CentosPrime.COM Mon Jan 7 06:25:16 2008 From: face at CentosPrime.COM (Chris Janton) Date: Mon Jan 7 06:23:17 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <52377.128.250.31.223.1199685408.squirrel@webmail.tuffmail.net> References: <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <"D6D36799-CD42-497F-B20B-0 4F908060822"@macports.org> <52377.128.250.31.223.1199685408.squirrel@webmail.tuffmail.net> Message-ID: <89DA7D9B-A1E6-45C9-99C3-A7DCFAE7C069@CentosPrime.COM> On 2008-01-06 , at 22:56 , Boey Maun Suang wrote: > Just out of curiosity, Kevin, any idea as to exactly why we were > getting > this problem? I wonder if there was a bug fixed between the tcl on > 10.3.9 > (which appears to be 8.4.4 [1], Chris can confirm this by running > `info > patchlevel` in tclsh) and the tcl on 10.4.11, which is 8.4.7. )I've > looked briefly at the Tcl Changelog for that period, but it's awfully > long.) On my test 10.3.9 system - tclsh is 8.4.4 On my primary 10.4.11 system - tclsh is 8.4.7 On my test 10.5.1 system - tclsh is 8.4.7 On my primary server (10.3.9) - tclsh is 8.5.0 - the macports installed version - needed for "expect" 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From face at CentosPrime.COM Mon Jan 7 06:41:57 2008 From: face at CentosPrime.COM (Chris Janton) Date: Mon Jan 7 06:40:01 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <78F97257-0779-4FDB-A876-BE46EB1AD3E9@macports.org> References: <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <"D6D36799-CD42-497F-B20B-0 4F908060822"@macports.org> Message-ID: <87CF28A9-B74D-4210-8C76-D98BB5DD51A7@CentosPrime.COM> On 2008-01-07 , at 01:05 , Kevin Ballard wrote: > Glad to hear that it seems to be working now. I really don't know > what was wrong, but obviously there was some bug with the info > command on 10.3. The recent changes mean we no longer rely on the > 'info commands' behaviour, so we should be good. So at what point should port selfupdate work on 10.3.9 systems again? It's not clear to me, but I assume that this command svn checkout http://svn.macosforge.org/repository/macports/trunk/base gets the "real thing" - the current port sourcecode, and that the update that was obtained by this command svn update (svn "knows" where the source repository is, etc. etc.) 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From george at galis.org Mon Jan 7 06:49:37 2008 From: george at galis.org (George Georgalis) Date: Mon Jan 7 06:47:22 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <20080106233000.GC3137@run.duo> References: <20080106233000.GC3137@run.duo> Message-ID: <20080107144937.GD3137@run.duo> I have also tried exporting DYLD_LIBRARY_PATH, expat is not found. On Sun, Jan 06, 2008 at 06:30:00PM -0500, George Georgalis wrote: >I'm not sure what the problem is here, expat is installed >(subversion, at least, is using it) but p5-xml-parser won't go >in because it cannot find it. I've tried exporting EXPATLIBPATH >and EXPATINCPATH but still no cookie. (I have synced and cleaned >installed too.) What could be wrong? > >// George > > geo@fuji:/Users/geo port installed expat >The following ports are currently installed: > expat @2.0.0_1 > expat @2.0.1_0 (active) > geo@fuji:/Users/geo sudo port outdated >The following installed ports are outdated: >gmp 4.2.2_0 < 4.2.2_1 >libpcap 0.9.5_1 < 0.9.8_0 >R 2.5.1_0 < 2.6.1_0 >tcl 8.4.16_0 < 8.5.0_0 >urw-fonts 1.0.7pre43_0 < 1.0.7pre44_0 >vim 7.1.175_0 < 7.1.203_0 >xrender 0.9.0_1 < 0.9.0_2 > geo@fuji:/Users/geo sudo port install gnupod >Password: >---> Configuring p5-xml-parser >Error: Target org.macports.configure returned: configure failure: shell command " cd "/usr/local/MacPorts/var/macports/build/_usr_local_MacPorts_var_macports_sources_rsync.macports.org_release_ports_perl_p5-xml-parser/work/XML-Parser-2.36" && /usr/local/MacPorts/bin/perl Makefile.PL INSTALLDIRS=vendor " returned error 2 >Command output: Note (probably harmless): No library found for -lexpat > >Expat must be installed prior to building XML::Parser and I can't find >it in the standard library directories. You can download expat from: > >http://sourceforge.net/projects/expat/ > >If expat is installed, but in a non-standard directory, then use the >following options to Makefile.PL: > > EXPATLIBPATH=... To set the directory in which to find libexpat > > EXPATINCPATH=... To set the directory in which to find expat.h > >For example: > > perl Makefile.PL EXPATLIBPATH=/home/me/lib EXPATINCPATH=/home/me/include > >Note that if you build against a shareable library in a non-standard location >you may (on some platforms) also have to set your LD_LIBRARY_PATH environment >variable at run time for perl to find the library. > > >Error: The following dependencies failed to build: p5-xml-parser >Error: Status 1 encountered during processing. > -- George Georgalis, information system scientist < From frstan at bellsouth.net Mon Jan 7 07:14:01 2008 From: frstan at bellsouth.net (William Davis) Date: Mon Jan 7 07:11:50 2008 Subject: Fwd: Beginner question -- how to resolve dependent dylib's when linking References: <47779959.9090806@wanadoo.fr> Message-ID: possible useful info from uni-porting list; Begin forwarded message: > From: Martin Costabel > Date: December 30, 2007 8:12:57 AM EST > To: kelsey@slac.stanford.edu > Cc: unix-porting@lists.apple.com > Subject: Re: Beginner question -- how to resolve dependent dylib's > when linking > > Peter O'Gorman wrote: >> Mike Kelsey wrote: >>> Is there an option I can give to |libtool| or/and |ld|, such that >>> dependent >>> libraries mentioned inside .dylib's will be resolved via the -L >>> options? >> See -dylib_file in the ld(1) manpage. > > If you are on Leopard, you probably don't have to do anything in > this case. It is standard behavior there (in most situations > perceived as an annoying bug, though) that indirect libraries are > *not* looked up according to their install_name, but in the > directories defined by -L. > > Perversely, you are forced to use -dylib_file, or explicit -L -l > references, if you want them to be looked up at the path mentioned > in the referencing dylib. This wreaks all kinds of havoc if you have > several dylibs of the same name on your system, but in your > situation this may be the behavior you are wishing for. > > -- > Martin > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Unix-porting mailing list (Unix-porting@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/unix-porting/frstan%40bellsouth.net > > This email sent to frstan@bellsouth.net William Davis frstanATbellsouthDOTnet Mac OS X.5.1 Darwin 9.1.0 X11.app 2.1.1 - (xorg-server 1.3.0-apple5) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080107/59c87b45/attachment.html From leo.studer at mus.ch Mon Jan 7 07:48:57 2008 From: leo.studer at mus.ch (Leo Studer) Date: Mon Jan 7 07:46:44 2008 Subject: qt3-mac Message-ID: <658BE300-DFCB-450A-8BD1-7D1E16129D6E@mus.ch> Hello I want to install LyX on my MacBook Pro Leopard 10.5.1 and did as follows sudo port install LyX then by building the dependencies port wants to configure qt3-mac and fails. Error: The following dependencies failed to build: qt3-mac Error: Status 1 encountered during processing. It seems that qt3-mac is not supported on Leopard. Does anyone have a work around? Thanks Leo From stefmit at gmail.com Mon Jan 7 08:20:43 2008 From: stefmit at gmail.com (Stefmit) Date: Mon Jan 7 08:18:32 2008 Subject: libpcap failure - Leopard 10.5.1 Message-ID: <200801071020.43938.stefmit@gmail.com> ---> Building libpcap with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_libpcap/work/libpcap-0.9.8" && make all " returned error 2 Command output: rm -f libpcap.dylib /usr/bin/gcc-4.0 -dynamiclib -o libpcap.`cat VERSION`.dylib \ -install_name /opt/local/lib/libpcap.0.dylib \ -compatibility_version 1.0.0 -current_version `cat VERSION` \ pcap-bpf.o fad-getad.o pcap.o inet.o gencode.o optimize.o nametoaddr.o etherent.o savefile.o bpf_filter.o bpf_image.o bpf_dump.o scanner.o grammar.o version.o Undefined symbols: "_lex_init", referenced from: _pcap_compile in gencode.o "_lex_cleanup", referenced from: _pcap_compile in gencode.o _pcap_compile in gencode.o "_pcap_lex", referenced from: _pcap_parse in grammar.o ld: symbol(s) not found collect2: ld returned 1 exit status make: *** [libpcap.dylib] Error 1 Error: Unable to upgrade port: 1 From face at CentosPrime.COM Mon Jan 7 08:30:04 2008 From: face at CentosPrime.COM (Chris Janton) Date: Mon Jan 7 08:28:09 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <87CF28A9-B74D-4210-8C76-D98BB5DD51A7@CentosPrime.COM> References: <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <"D6D36799-CD42-497F-B20B-0 4F908060822"@macports.org> <87CF28A9-B74D-4210-8C76-D98BB5DD51A7@CentosPrime.COM> Message-ID: Well - we're getting closer, but something is still not right. I am trying to install all of the ports that are on my production server. Some work, some don't house54 25 # sudo port -vd install analog DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/www/analog DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/www/analog DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/archivers/zlib DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/archivers/zlib DEBUG: Searching for dependency: zlib DEBUG: Found Dependency: receipt exists for zlib ---> Fetching analog ---> Verifying checksum(s) for analog ---> Extracting analog ---> Applying patches to analog ---> Configuring analog ---> Building analog with target analog ---> Staging analog into destroot Error: Target org.macports.destroot returned: invalid command name "cd" Error: Status 1 encountered during processing. Any ideas? From sfiera at macports.org Mon Jan 7 09:19:40 2008 From: sfiera at macports.org (Chris Pickel) Date: Mon Jan 7 09:17:36 2008 Subject: Problems using macports In-Reply-To: <47821F8C.9020600@email.it> References: <47821F8C.9020600@email.it> Message-ID: [Resending to post to list; sorry to muffetta for the extra copy] On 07 Jan, 2008, at 7:48, muffetta66 wrote: > ibook-g4-di-*************-********:~ *************$ sudo port > install mc > Password: > ---> Extracting libiconv > Error: Target org.macports.extract returned: shell command " cd "/ > opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_textproc_libiconv/work" && gzip -dc /opt/ > local/var/macports/distfiles/libiconv/libiconv-1.12.tar.gz | -xf - " > returned error 127 > Command output: sh: line 1: -xf: command not found Looks like you have `tar` missing. What's the value of tar_command on your system? You can get it as follows: % cat /opt/local/share/macports/Tcl/port1.0/port_autoconf.tcl | grep tar variable tar_command "/usr/bin/gnutar --no-same-owner" I'm assuming that the value will be missing on your system. As you can see, on my system it refers to /usr/bin/gnutar: % /usr/bin/gnutar --version tar (GNU tar) 1.15.1 It's possible that you could fix your problem simply by editing port_autoconf.tcl, but that would break upon selfupdating, and it would be better to know why it didn't originally find the tar command. Chris From wsiegrist at apple.com Mon Jan 7 10:07:45 2008 From: wsiegrist at apple.com (William Siegrist) Date: Mon Jan 7 10:06:58 2008 Subject: Problems using macports In-Reply-To: References: <47821F8C.9020600@email.it> Message-ID: This looks similar to the problem with mod_python on Leopard (the lack of a command name): http://trac.macports.org/projects/macports/ticket/13856 -Bill On Jan 7, 2008, at 9:19 AM, Chris Pickel wrote: > [Resending to post to list; sorry to muffetta for the extra copy] > > On 07 Jan, 2008, at 7:48, muffetta66 wrote: >> ibook-g4-di-*************-********:~ *************$ sudo port >> install mc >> Password: >> ---> Extracting libiconv >> Error: Target org.macports.extract returned: shell command " cd "/ >> opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_textproc_libiconv/work" && gzip -dc / >> opt/local/var/macports/distfiles/libiconv/libiconv-1.12.tar.gz | - >> xf - " returned error 127 >> Command output: sh: line 1: -xf: command not found > > Looks like you have `tar` missing. What's the value of tar_command > on your system? You can get it as follows: > > % cat /opt/local/share/macports/Tcl/port1.0/port_autoconf.tcl | grep > tar > variable tar_command "/usr/bin/gnutar --no-same-owner" > > I'm assuming that the value will be missing on your system. As you > can see, on my system it refers to /usr/bin/gnutar: > > % /usr/bin/gnutar --version > tar (GNU tar) 1.15.1 > > It's possible that you could fix your problem simply by editing > port_autoconf.tcl, but that would break upon selfupdating, and it > would be better to know why it didn't originally find the tar command. > > > Chris > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users ---- William Siegrist Software Support Engineer Mac OS Forge http://macosforge.org/ wsiegrist@apple.com 408 862 7337 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2421 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080107/ba21e129/smime-0001.bin From eridius at macports.org Mon Jan 7 10:16:15 2008 From: eridius at macports.org (Kevin Ballard) Date: Mon Jan 7 10:14:05 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <87CF28A9-B74D-4210-8C76-D98BB5DD51A7@CentosPrime.COM> References: <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <"D6D36799-CD42-497F-B20B-0 4F908060822"@macports.org> <87CF28A9-B74D-4210-8C76-D98BB5 DD51A7@CentosPrime.COM> Message-ID: port selfupdate is not appropriate anymore simply because it will overwrite your self-built copy of macports with the latest released version (well, it actually won't do this until the latest released version is a higher version number than what you currently have installed). I mean, if that's what you want, go ahead and do it, but if you'd rather stay pegged to the tip of trunk, you need to do svn update/make/make install yourself. And yes, that svn checkout command got the latest source that the developers are working from, and svn update, when called in the directory produced by the checkout, does just "know" where the repo is and updates from it. -Kevin Ballard On Jan 7, 2008, at 9:41 AM, Chris Janton wrote: > So at what point should > > port selfupdate > > work on 10.3.9 systems again? > > It's not clear to me, but I assume that this command > > svn checkout http://svn.macosforge.org/repository/macports/trunk/base > > gets the "real thing" - the current port sourcecode, and that the > update that was obtained by this command > > svn update > > (svn "knows" where the source repository is, etc. etc.) -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080107/33329c8b/attachment.html From eridius at macports.org Mon Jan 7 10:21:47 2008 From: eridius at macports.org (Kevin Ballard) Date: Mon Jan 7 10:19:31 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> <57740.128.250.6.246.1199428335.squirrel@webmail.tuffmail.net> <249FDC08-6BE0-4769-ADFB-2EC0211CD98E@CentosPrime.COM> <54453.128.250.6.247.1199499169.squirrel@webmail.tuffmail.net> <0930482B-2800-4A8D-84D8-10F09DEA0BEA@macports.org> <9612CF9F-A6FF-407B-9E19-DFCEC2269D3F@CentosPrime.COM> <5EAFCA47-B2CE-4474-A239-2D3E9ADBFB00@macports.org> <318A7E68-0B3C-4B60-B0AC-885B110AF6FE@CentosPrime.COM> <"D6D36799-CD42-497F-B20B-0 4F908060822"@macports.org> <87CF28A9-B74D-4210-8C76-D98BB5 DD51A7@CentosPrime.COM> Message-ID: <797CFD4B-B6AE-4639-B3A1-DE31D2EFFBCE@macports.org> Yes, the analog port needs updating. The cd command was removed, but some ports still use it. I've just gone ahead and fixed the analog port (the updated Portfile is available in svn now and will be available through `port sync `within 12 hours). Any other ports that complain about invalid command name "cd" you should file a ticket on. -Kevin Ballard On Jan 7, 2008, at 11:30 AM, Chris Janton wrote: > Well - we're getting closer, but something is still not right. > > I am trying to install all of the ports that are on my production > server. Some work, some don't > > house54 25 # sudo port -vd install analog > DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/www/analog > DEBUG: Changing to port directory: /opt/local/var/macports/sources/ > rsync.macports.org/release/ports/www/analog > DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/archivers/zlib > DEBUG: Changing to port directory: /opt/local/var/macports/sources/ > rsync.macports.org/release/ports/archivers/zlib > DEBUG: Searching for dependency: zlib > DEBUG: Found Dependency: receipt exists for zlib > ---> Fetching analog > ---> Verifying checksum(s) for analog > ---> Extracting analog > ---> Applying patches to analog > ---> Configuring analog > ---> Building analog with target analog > ---> Staging analog into destroot > Error: Target org.macports.destroot returned: invalid command name > "cd" > Error: Status 1 encountered during processing. > > Any ideas? > -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com From lists at sequestered.net Mon Jan 7 10:49:49 2008 From: lists at sequestered.net (Jay Chandler) Date: Mon Jan 7 10:47:33 2008 Subject: ntop fails to build Message-ID: <4782744D.8070500@sequestered.net> jay@Singularity~$ sudo port install ntop ---> Building ntop with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_ntop/work/ntop-3.3" && gnumake all " returned error 2 Command output: gnumake all-recursive Making all in . /bin/sh ./libtool --tag=CC --mode=compile /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -g -Os -DBUILD=112 -DMACOSX_DEPLOYMENT_TARGET=10.5 -F/System/Library/PrivateFrameworks/ -F/System/Library/Frameworks/ -pipe -Udarwin9 -Ddarwin9=darwin9 -I. -I/usr/local/include -I/opt/local/include -DDARWIN -I/usr/local/include -g -no-cpp-precomp -O2 -I/opt/local/include -I/usr/local/include -g -Wshadow -Wpointer-arith -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-common -DPIC -MT address.lo -MD -MP -MF .deps/address.Tpo -c -o address.lo address.c /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -g -Os -DBUILD=112 -DMACOSX_DEPLOYMENT_TARGET=10.5 -F/System/Library/PrivateFrameworks/ -F/System/Library/Frameworks/ -pipe -Udarwin9 -Ddarwin9=darwin9 -I. -I/usr/local/include -I/opt/local/include -DDARWIN -I/usr/local/include -g -no-cpp-precomp -O2 -I/opt/local/include -I/usr/local/include -g -Wshadow -Wpointer-arith -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-common -DPIC -MT address.lo -MD -MP -MF .deps/address.Tpo -c address.c -fno-common -DPIC -o .libs/address.o In file included from ntop.h:484, from address.c:21: globals-structtypes.h:103: error: two or more data types in declaration specifiers globals-structtypes.h:103: warning: useless type name in empty declaration gnumake[2]: *** [address.lo] Error 1 gnumake[1]: *** [all-recursive] Error 1 gnumake: *** [all] Error 2 Error: Status 1 encountered during processing. -- Jay Chandler / KB1JWQ Living Legend / Systems Exorcist Today's Excuse: SIMM crosstalk From ajmas at sympatico.ca Mon Jan 7 11:22:00 2008 From: ajmas at sympatico.ca (Andre-John Mas) Date: Mon Jan 7 11:19:48 2008 Subject: MacPorts and IPv6 Message-ID: <6buhm2$54c50j@toip7.srvr.bell.ca> Hi, Since MacOS X officially supports IPv6, it would be nice if programs that provide an IPv6 build option could either have IPv6 specified in the default port, or at the very least as a variant. Hopefully everyone is ok with this enhancement request. I don't plan on testing the ports for this, but I can say that the Apache2 port already supports IPv6, but the Lynx port doesn't (ticket 13864). Andre From ryandesign at macports.org Mon Jan 7 12:23:05 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 12:21:25 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <20080107144937.GD3137@run.duo> References: <20080106233000.GC3137@run.duo> <20080107144937.GD3137@run.duo> Message-ID: <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> On Jan 7, 2008, at 08:49, George Georgalis wrote: > I have also tried exporting DYLD_LIBRARY_PATH, expat is not found. That should not be necessary. I have p5-xml-parser and expat installed. Never seen this problem. The obvious difference I see is that your MacPorts prefix is /usr/ local/MacPorts instead of the usual /opt/local. Can you check if anything ended up getting installed in the /opt/local by mistake? Also, can you tell us your version of MacPorts, Mac OS X, Xcode, and your processor architecture? > On Sun, Jan 06, 2008 at 06:30:00PM -0500, George Georgalis wrote: > >> I'm not sure what the problem is here, expat is installed >> (subversion, at least, is using it) but p5-xml-parser won't go >> in because it cannot find it. I've tried exporting EXPATLIBPATH >> and EXPATINCPATH but still no cookie. (I have synced and cleaned >> installed too.) What could be wrong? >> >> // George >> >> geo@fuji:/Users/geo port installed expat >> The following ports are currently installed: >> expat @2.0.0_1 >> expat @2.0.1_0 (active) >> geo@fuji:/Users/geo sudo port outdated >> The following installed ports are outdated: >> gmp 4.2.2_0 < 4.2.2_1 >> libpcap 0.9.5_1 < 0.9.8_0 >> R 2.5.1_0 < 2.6.1_0 >> tcl 8.4.16_0 < 8.5.0_0 >> urw-fonts 1.0.7pre43_0 < 1.0.7pre44_0 >> vim 7.1.175_0 < 7.1.203_0 >> xrender 0.9.0_1 < 0.9.0_2 >> geo@fuji:/Users/geo sudo port install gnupod >> Password: >> ---> Configuring p5-xml-parser >> Error: Target org.macports.configure returned: configure failure: >> shell command " cd "/usr/local/MacPorts/var/macports/build/ >> _usr_local_MacPorts_var_macports_sources_rsync.macports.org_release_p >> orts_perl_p5-xml-parser/work/XML-Parser-2.36" && /usr/local/ >> MacPorts/bin/perl Makefile.PL INSTALLDIRS=vendor " returned error 2 >> Command output: Note (probably harmless): No library found for - >> lexpat >> >> Expat must be installed prior to building XML::Parser and I can't >> find >> it in the standard library directories. You can download expat from: >> >> http://sourceforge.net/projects/expat/ >> >> If expat is installed, but in a non-standard directory, then use the >> following options to Makefile.PL: >> >> EXPATLIBPATH=... To set the directory in which to find libexpat >> >> EXPATINCPATH=... To set the directory in which to find expat.h >> >> For example: >> >> perl Makefile.PL EXPATLIBPATH=/home/me/lib EXPATINCPATH=/home/ >> me/include >> >> Note that if you build against a shareable library in a non- >> standard location >> you may (on some platforms) also have to set your LD_LIBRARY_PATH >> environment >> variable at run time for perl to find the library. >> >> >> Error: The following dependencies failed to build: p5-xml-parser >> Error: Status 1 encountered during processing. From ryandesign at macports.org Mon Jan 7 12:37:32 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 12:42:31 2008 Subject: ntop fails to build In-Reply-To: <4782744D.8070500@sequestered.net> References: <4782744D.8070500@sequestered.net> Message-ID: <21E10BA5-5AE3-4A8B-8AC8-48C1E82D06AA@macports.org> On Jan 7, 2008, at 12:49, Jay Chandler wrote: > jay@Singularity~$ sudo port install ntop > ---> Building ntop with target all > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_n > top/work/ntop-3.3" && gnumake all " returned error 2 > Command output: gnumake all-recursive > Making all in . > /bin/sh ./libtool --tag=CC --mode=compile /usr/bin/gcc-4.0 - > DHAVE_CONFIG_H -I. -I. -g -Os -DBUILD=112 - > DMACOSX_DEPLOYMENT_TARGET=10.5 -F/System/Library/PrivateFrameworks/ > -F/System/Library/Frameworks/ -pipe -Udarwin9 -Ddarwin9=darwin9 -I. > -I/usr/local/include -I/opt/local/include -DDARWIN -I/usr/local/ > include -g -no-cpp-precomp -O2 -I/opt/local/include -I/usr/local/ > include -g -Wshadow -Wpointer-arith -Wmissing-prototypes -Wmissing- > declarations -Wnested-externs -fno-common -DPIC -MT address.lo -MD > -MP -MF .deps/address.Tpo -c -o address.lo address.c > /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -g -Os -DBUILD=112 - > DMACOSX_DEPLOYMENT_TARGET=10.5 -F/System/Library/PrivateFrameworks/ > -F/System/Library/Frameworks/ -pipe -Udarwin9 -Ddarwin9=darwin9 -I. > -I/usr/local/include -I/opt/local/include -DDARWIN -I/usr/local/ > include -g -no-cpp-precomp -O2 -I/opt/local/include -I/usr/local/ > include -g -Wshadow -Wpointer-arith -Wmissing-prototypes -Wmissing- > declarations -Wnested-externs -fno-common -DPIC -MT address.lo -MD - > MP -MF .deps/address.Tpo -c address.c -fno-common -DPIC -o .libs/ > address.o > In file included from ntop.h:484, > from address.c:21: > globals-structtypes.h:103: error: two or more data types in > declaration specifiers > globals-structtypes.h:103: warning: useless type name in empty > declaration > gnumake[2]: *** [address.lo] Error 1 > gnumake[1]: *** [all-recursive] Error 1 > gnumake: *** [all] Error 2 > > Error: Status 1 encountered during processing. I see this problem was reported 3 weeks ago but the maintainer hasn't commented on it yet. http://trac.macosforge.org/projects/macports/ticket/13610 I'll add you to the Cc list of that ticket so you're informed of its progress. I see you're running Mac OS X 10.5. Looks like the reporter of that ticket was too. And do you have Xcode 3? What version of MacPorts do you have, and what architecture is your processor? I note occurrences of /usr/local in your output above, and also in the filed ticket. What do you have in /usr/local? It can conflict with MacPorts ports, so we recommend not having anything in /usr/ local. Try renaming /usr/local to /usr/local-off and cleaning (sudo port clean --work ntop) and building (sudo port install ntop) ntop again. If it works, you'll know something in /usr/local conflicted, and you should install whatever you need using MacPorts instead of manually installing in /usr/local. From ryandesign at macports.org Mon Jan 7 12:55:43 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 12:54:01 2008 Subject: qt3-mac In-Reply-To: <658BE300-DFCB-450A-8BD1-7D1E16129D6E@mus.ch> References: <658BE300-DFCB-450A-8BD1-7D1E16129D6E@mus.ch> Message-ID: <6F7DBCC7-E16C-4750-BD95-D675EEC0E3AF@macports.org> On Jan 7, 2008, at 09:48, Leo Studer wrote: > I want to install LyX on my MacBook Pro Leopard 10.5.1 and did as > follows > > sudo port install LyX > > then by building the dependencies port wants to configure qt3-mac > and fails. > > Error: The following dependencies failed to build: qt3-mac > Error: Status 1 encountered during processing. > > It seems that qt3-mac is not supported on Leopard. > > Does anyone have a work around? You need to give us more of the error message. Why did qt3-mac fail to build? We already have one ticket about qt3-mac failing to build on Leopard: http://trac.macosforge.org/projects/macports/ticket/13208 Is that what you're seeing? If so, then we know about it, and hopefully the maintainer of qt3-mac will resolve it soon. If you're seeing a different issue, then you should file a ticket on it. From ryandesign at macports.org Mon Jan 7 12:57:19 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 12:55:37 2008 Subject: mod_python fails to build on Leopard In-Reply-To: <7fccb3000801070358lc11bc56v39280508cf7cb7d@mail.gmail.com> References: <7fccb3000801070358lc11bc56v39280508cf7cb7d@mail.gmail.com> Message-ID: On Jan 7, 2008, at 05:58, Tabitha McNerney wrote: > For anyone that may be interested, I filed a bug report, Ticket > #13856, regarding attempts to build the mod_python port for use > with Apache 2 on a fresh system of MacPorts 1.6.0 on Leopard Server > 10.5.1 I've assigned the ticket to the maintainer of mod_python. Don't forget to do this when filing tickets, otherwise the maintainer might never see the ticket... From ryandesign at macports.org Mon Jan 7 13:03:32 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 13:01:51 2008 Subject: Beginner question -- how to resolve dependent dylib's when linking In-Reply-To: References: <47779959.9090806@wanadoo.fr> Message-ID: <07F39105-3C02-42E9-9919-FC7FB5DD08AC@macports.org> On Jan 7, 2008, at 09:14, William Davis wrote: > possible useful info from uni-porting list; > > Begin forwarded message: > >> From: Martin Costabel >> Date: December 30, 2007 8:12:57 AM EST >> To: kelsey@slac.stanford.edu >> Cc: unix-porting@lists.apple.com >> Subject: Re: Beginner question -- how to resolve dependent dylib's >> when linking >> >> Peter O'Gorman wrote: >>> Mike Kelsey wrote: >>>> Is there an option I can give to |libtool| or/and |ld|, such >>>> that dependent >>>> libraries mentioned inside .dylib's will be resolved via the -L >>>> options? >>> See -dylib_file in the ld(1) manpage. >> >> If you are on Leopard, you probably don't have to do anything in >> this case. It is standard behavior there (in most situations >> perceived as an annoying bug, though) that indirect libraries are >> *not* looked up according to their install_name, but in the >> directories defined by -L. >> >> Perversely, you are forced to use -dylib_file, or explicit -L -l >> references, if you want them to be looked up at the path mentioned >> in the referencing dylib. This wreaks all kinds of havoc if you >> have several dylibs of the same name on your system, but in your >> situation this may be the behavior you are wishing for. Presumably you are sending this as information for solving the "cycle in dylib re-exports" problem we see with some software under Leopard? But isn't the solution provided by Apple in their technote already sufficient to resolve this? http://developer.apple.com/qa/qa2007/qa1567.html Or am I misunderstanding your message? From ryandesign at macports.org Mon Jan 7 13:14:21 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 13:19:21 2008 Subject: ocaml fails on Tiger (was: Re: sudo port install mldonkey) In-Reply-To: <20080107103215.GB9144@marco.fz-rossendorf.de> References: <590A936D-453F-4369-9E09-69E7D05001B2@gmail.com> <53DF8FAC-D824-438D-8AF1-6B62D94BC177@gmail.com> <903349F2-4D42-4AC6-AA07-DDE14D0C8D5E@macports.org> <20080107103215.GB9144@marco.fz-rossendorf.de> Message-ID: <9647D02E-22CC-44F3-AAE0-813DF4D640BC@macports.org> On Jan 7, 2008, at 04:32, Joerg van den Hoff wrote: > On Fri, Jan 04, 2008 at 12:05:14PM -0600, Ryan Schmidt wrote: > >> On Jan 4, 2008, at 09:41, Charlse Darwin wrote: >> >>> On Dec 26, 2007, at 8:14 AM, Ryan Schmidt wrote: >>> >>>> This bug has already been reported: >>>> >>>> http://trac.macosforge.org/projects/macports/ticket/13583 >>> >>> # I installed ocaml from precompiled binary >>> >>> # >>> >>> $ sudo port clean --dist --archive --work mldonkey >>> ---> Cleaning mldonkey >>> $ sudo port clean --dist --archive --work ocaml >>> Password: >>> ---> Cleaning ocaml >>> $ sudo port clean --dist --archive --work mldonkey >>> ---> Cleaning mldonkey >>> Mac:~ pm$ sudo port -f install mldonkey >>> ---> Fetching ocaml >>> ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// >>> caml.inria.fr/pub/distrib/ocaml-3.10/ >>> ---> Verifying checksum(s) for ocaml >>> ---> Extracting ocaml >>> ---> Applying patches to ocaml >>> ---> Configuring ocaml >>> Error: Target org.macports.configure returned: configure failure: >>> shell command " cd "/opt/local/var/macports/build/ >>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lan >>> g_ >>> ocaml/work/ocaml-3.10.0" && ./configure -prefix /opt/local -no-tk " >>> returned error 2 >>> Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) not >>> balanced >>> ../gnu/config.sub: line 128: [: !=: unary operator expected >>> Invalid configuration `powerpc-apple-darwin8.11.0': machine `' not >>> recognized >>> Please specify the correct host type with the -host option >>> >>> Error: The following dependencies failed to build: lablgtk ocaml >>> Error: Status 1 encountered during processing. >>> $ >>> >>> # How do I get it to skip ocaml? >> >> There isn't a built-in way to do that. MacPorts is designed not to >> make use of any software you install outside of MacPorts. You could >> possibly modify the portfile to look for ocaml in a different >> directory. But what we would really like is for someone to figure out >> why the ocaml port fails to build, and fix it. > > is there hope (i.e. is the package still actively > maintained)? > > would it be helpful to "cross post" this issue on one of the > ocaml lists asking for opinions/help? if so, where to send > potential answers? to "pguyot@kallisys.net" as > > `port info ocaml' > > tells me? If you want to know if a package is being actively maintained, you should email the package maintainer. If "nomaintainer" is the package maintainer, then it is not being maintained. The problems Charlse Darwin was experiencing were the result of his unique setup which included a broken sed program. The general problems building ocaml on Tiger which were reported in ticket 13583 were resolved by me 3 days ago because the maintainer had not responded to the issue. After you "sudo port selfupdate" do you still see any problems? From ara.t.howard at gmail.com Mon Jan 7 13:38:47 2008 From: ara.t.howard at gmail.com (ara howard) Date: Mon Jan 7 13:37:10 2008 Subject: tiger -->> leopard link error: -lcrt Message-ID: <77198364-34F8-49FA-96E3-1AE2A6E312F6@domain.actdsltmp> just migrated tiger -->> leopard: clean install. i'm copying stuff over by hand and had hoped i could do an rsync of my /opt tree on tiger to leopard. this seems to have work as at least many things are working. however, just tried to port install iterm and got: ld: library not found for -lcrt1.10.5.o so - is the iterm port hosed for leopard? or was i simply too hopeful that i could copy the tree over like that and have things work? kind regards. -a -- http://codeforpeople.com From olaf at foellinger.de Mon Jan 7 13:51:51 2008 From: olaf at foellinger.de (Olaf Foellinger) Date: Mon Jan 7 13:49:38 2008 Subject: please submit the following update and patch was: [Fwd:[MacPorts] #13845: UPDATE: darkstat 3.0.707] Message-ID: <20080107215151.GA1857@foellinger.de> Hi, I've tested the patch and the update, it works, please submit it. Gruss Olaf -------------- next part -------------- An embedded message was scrubbed... From: "MacPorts" Subject: [MacPorts] #13845: UPDATE: darkstat 3.0.707 Date: Sun, 06 Jan 2008 04:45:52 -0000 Size: 3149 Url: http://lists.macosforge.org/pipermail/macports-users/attachments/20080107/58fa6041/attachment.mht From ryandesign at macports.org Mon Jan 7 12:53:07 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 13:51:26 2008 Subject: libpcap failure - Leopard 10.5.1 In-Reply-To: <200801071020.43938.stefmit@gmail.com> References: <200801071020.43938.stefmit@gmail.com> Message-ID: <19F694C6-8DB8-4B46-9E81-5451022C5177@macports.org> I see we have a ticket on this already: http://trac.macosforge.org/projects/macports/ticket/13802 I'll add you to the Cc list so you'll be informed of its progress. Any help you can provide in resolving the problem would of course also be appreciated. On Jan 7, 2008, at 10:20, Stefmit wrote: > ---> Building libpcap with target all > Error: Target org.macports.build returned: shell command " > cd "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_l > ibpcap/work/libpcap-0.9.8" > && make all " returned error 2 > Command output: rm -f libpcap.dylib > /usr/bin/gcc-4.0 -dynamiclib -o libpcap.`cat VERSION`.dylib \ > -install_name /opt/local/lib/libpcap.0.dylib \ > -compatibility_version 1.0.0 -current_version `cat > VERSION` \ > pcap-bpf.o fad-getad.o pcap.o inet.o gencode.o > optimize.o > nametoaddr.o etherent.o savefile.o bpf_filter.o bpf_image.o bpf_dump.o > scanner.o grammar.o version.o > Undefined symbols: > "_lex_init", referenced from: > _pcap_compile in gencode.o > "_lex_cleanup", referenced from: > _pcap_compile in gencode.o > _pcap_compile in gencode.o > "_pcap_lex", referenced from: > _pcap_parse in grammar.o > ld: symbol(s) not found > collect2: ld returned 1 exit status > make: *** [libpcap.dylib] Error 1 > > Error: Unable to upgrade port: 1 From ryandesign at macports.org Mon Jan 7 13:54:38 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 13:52:57 2008 Subject: tiger -->> leopard link error: -lcrt In-Reply-To: <77198364-34F8-49FA-96E3-1AE2A6E312F6@domain.actdsltmp> References: <77198364-34F8-49FA-96E3-1AE2A6E312F6@domain.actdsltmp> Message-ID: On Jan 7, 2008, at 15:38, ara howard wrote: > > just migrated tiger -->> leopard: clean install. i'm copying stuff > over by hand and had hoped i could do an rsync of my /opt tree on > tiger to leopard. this seems to have work as at least many things > are working. however, just tried to port install iterm and got: > > ld: library not found for -lcrt1.10.5.o > > so - is the iterm port hosed for leopard? or was i simply too > hopeful that i could copy the tree over like that and have things > work? Copying MacPorts from Tiger to Leopard (or upgrading from Tiger to Leopard and keeping your MacPorts installation) is problematic because many ports will have built with the auto-selected "darwin_8" variant, which is now not appropriate on Leopard. Any such ports that you have should be forcibly uninstalled (sudo port -f uninstall foo) and reinstalled (sudo port install foo) so that they pick up the darwin_9 variant, if necessary. That may not be related to your iterm issue, however. I'm not sure. From frstan at bellsouth.net Mon Jan 7 14:01:28 2008 From: frstan at bellsouth.net (William Davis) Date: Mon Jan 7 13:59:14 2008 Subject: Beginner question -- how to resolve dependent dylib's when linking In-Reply-To: <07F39105-3C02-42E9-9919-FC7FB5DD08AC@macports.org> References: <47779959.9090806@wanadoo.fr> <07F39105-3C02-42E9-9919-FC7FB5DD08AC@macports.org> Message-ID: <32EF2FBC-2612-498E-B8F4-D9ECD523183D@bellsouth.net> On Jan 7, 2008, at 4:03 PM, Ryan Schmidt wrote: > On Jan 7, 2008, at 09:14, William Davis wrote: > >> possible useful info from uni-porting list; >> >> Begin forwarded message: >> >>> From: Martin Costabel >>> Date: December 30, 2007 8:12:57 AM EST >>> To: kelsey@slac.stanford.edu >>> Cc: unix-porting@lists.apple.com >>> Subject: Re: Beginner question -- how to resolve dependent dylib's >>> when linking >>> >>> Peter O'Gorman wrote: >>>> Mike Kelsey wrote: >>>>> Is there an option I can give to |libtool| or/and |ld|, such >>>>> that dependent >>>>> libraries mentioned inside .dylib's will be resolved via the -L >>>>> options? >>>> See -dylib_file in the ld(1) manpage. >>> >>> If you are on Leopard, you probably don't have to do anything in >>> this case. It is standard behavior there (in most situations >>> perceived as an annoying bug, though) that indirect libraries are >>> *not* looked up according to their install_name, but in the >>> directories defined by -L. >>> >>> Perversely, you are forced to use -dylib_file, or explicit -L -l >>> references, if you want them to be looked up at the path mentioned >>> in the referencing dylib. This wreaks all kinds of havoc if you >>> have several dylibs of the same name on your system, but in your >>> situation this may be the behavior you are wishing for. > > Presumably you are sending this as information for solving the > "cycle in dylib re-exports" problem we see with some software under > Leopard? > > But isn't the solution provided by Apple in their technote already > sufficient to resolve this? > > http://developer.apple.com/qa/qa2007/qa1567.html > > Or am I misunderstanding your message? > Besides the recycling problem I thought perhaps some other ports which fail config or build on Leopard might be suffering from trying to find indirect libs from their "install_name". William Davis frstanATbellsouthDOTnet Mac OS X.5.1 Darwin 9.1.0 X11.app 2.1.1 - (xorg-server 1.3.0-apple5) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From jberry at macports.org Mon Jan 7 14:26:33 2008 From: jberry at macports.org (James Berry) Date: Mon Jan 7 14:24:27 2008 Subject: MacPorts servers will be down for a bit in about 5 hours Message-ID: <19531F38-9F5A-43B7-A3EF-9D4F2112ADC5@macports.org> Our friends at MacOSForge tell us that the servers running macports will be down in about 5 hours for some scheduled maintenance: > We need to take the servers down briefly to apply some updates and > configuration changes. All services will have 5-10m of downtime > starting around 8PM on Monday. The Trac & Subversion services will > have additional downtime to upgrade the RAM to improve performance. > I expect Trac/SVN to be down for 30m total. I'll make announcements > in #macosforge as each services goes down and up. Everything should > be back to normal around 9pm. If the unexpected occurs, as it sometimes does, please bear with us. If you need a status update you might stop in on the #macports or #macosforge channels on freenode, where more information might or might not be available ;) James From boeyms at macports.org Mon Jan 7 16:07:33 2008 From: boeyms at macports.org (Boey Maun Suang) Date: Mon Jan 7 16:05:15 2008 Subject: please submit the following update and patch was: [Fwd:[MacPorts] #13845: UPDATE: darkstat 3.0.707] In-Reply-To: <20080107215151.GA1857@foellinger.de> References: <20080107215151.GA1857@foellinger.de> Message-ID: <52869.128.250.31.223.1199750853.squirrel@webmail.tuffmail.net> Hi Olaf, On Tue, January 8, 2008 8:51 am, Olaf Foellinger wrote: > Hi, > > I've tested the patch and the update, it works, please submit it. Done in r32564 [1]. Thanks! Kind regards, Maun Suang [1] http://trac.macosforge.org/projects/macports/changeset/32564 -- Boey Maun Suang Email: boeyms@macports.org From skip at pobox.com Mon Jan 7 16:51:24 2008 From: skip at pobox.com (skip@pobox.com) Date: Mon Jan 7 16:49:09 2008 Subject: libtool vs. libtool-devel Message-ID: <18306.51468.130428.679779@montanaro.dyndns.org> I was seduced by the libtool-devel port (v. 1.9f), which caused me to deactivate the libtool port (v 1.5.24) in favor of it. As it turns out, the automake folks told me 1.9f is pretty old. The other kicker which got me to try libtool-devel was that the libtool port doesn't actually install tools named "libtool" and "libtoolize". I was looking for libtoolize, so assumed without investigating that if 1.9 > 1.5 and 1.5 doesn't have libtoolize, maybe 1.9 would have it. Given the naive view that a larger version number implies something a bit more current and "-devel" implies something a bit more development-oriented, shouldn't the libtool-devel port either be renamed or deleted altogether? -- Skip Montanaro - skip@pobox.com - http://www.webfast.com/~skip/ From george at galis.org Mon Jan 7 18:10:26 2008 From: george at galis.org (George Georgalis) Date: Mon Jan 7 18:08:11 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> References: <20080106233000.GC3137@run.duo> <20080107144937.GD3137@run.duo> <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> Message-ID: <20080108021026.GB29114@run.duo> On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote: > > On Jan 7, 2008, at 08:49, George Georgalis wrote: > >> I have also tried exporting DYLD_LIBRARY_PATH, expat is not found. > > That should not be necessary. > > I have p5-xml-parser and expat installed. Never seen this problem. > > The obvious difference I see is that your MacPorts prefix is > /usr/local/MacPorts instead of the usual /opt/local. Can you check if > anything ended up getting installed in the /opt/local by mistake? ls: /opt/local: No such file or directory > Also, can you tell us your version of MacPorts, Mac OS X, Xcode, and your > processor architecture? not sure how to determine xcode version maybe this is good enough? + port version Version: 1.600 + system_profiler + grep 'System Version' System Version: Mac OS X 10.4.11 (8S165) + which gcc /usr/bin/gcc + gcc -v Using built-in specs. Target: powerpc-apple-darwin8 Configured with: /private/var/tmp/gcc/gcc-5363.obj~28/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib --build=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 --target=powerpc-apple-darwin8 Thread model: posix gcc version 4.0.1 (Apple Computer, Inc. build 5363) + ls /Developer/SDKs MacOSX10.3.9.sdk MacOSX10.4u.sdk + uname -p powerpc // George >> On Sun, Jan 06, 2008 at 06:30:00PM -0500, George Georgalis wrote: >> >>> I'm not sure what the problem is here, expat is installed >>> (subversion, at least, is using it) but p5-xml-parser won't go >>> in because it cannot find it. I've tried exporting EXPATLIBPATH >>> and EXPATINCPATH but still no cookie. (I have synced and cleaned >>> installed too.) What could be wrong? >>> >>> // George >>> >>> geo@fuji:/Users/geo port installed expat >>> The following ports are currently installed: >>> expat @2.0.0_1 >>> expat @2.0.1_0 (active) >>> geo@fuji:/Users/geo sudo port outdated >>> The following installed ports are outdated: >>> gmp 4.2.2_0 < 4.2.2_1 >>> libpcap 0.9.5_1 < 0.9.8_0 >>> R 2.5.1_0 < 2.6.1_0 >>> tcl 8.4.16_0 < 8.5.0_0 >>> urw-fonts 1.0.7pre43_0 < 1.0.7pre44_0 >>> vim 7.1.175_0 < 7.1.203_0 >>> xrender 0.9.0_1 < 0.9.0_2 >>> geo@fuji:/Users/geo sudo port install gnupod >>> Password: >>> ---> Configuring p5-xml-parser >>> Error: Target org.macports.configure returned: configure failure: shell >>> command " cd >>> "/usr/local/MacPorts/var/macports/build/_usr_local_MacPorts_var_macports_sources_rsync.macports.org_release_ports_perl_p5-xml-parser/work/XML-Parser-2.36" >>> && /usr/local/MacPorts/bin/perl Makefile.PL INSTALLDIRS=vendor " returned >>> error 2 >>> Command output: Note (probably harmless): No library found for -lexpat >>> >>> Expat must be installed prior to building XML::Parser and I can't find >>> it in the standard library directories. You can download expat from: >>> >>> http://sourceforge.net/projects/expat/ >>> >>> If expat is installed, but in a non-standard directory, then use the >>> following options to Makefile.PL: >>> >>> EXPATLIBPATH=... To set the directory in which to find libexpat >>> >>> EXPATINCPATH=... To set the directory in which to find expat.h >>> >>> For example: >>> >>> perl Makefile.PL EXPATLIBPATH=/home/me/lib >>> EXPATINCPATH=/home/me/include >>> >>> Note that if you build against a shareable library in a non-standard >>> location >>> you may (on some platforms) also have to set your LD_LIBRARY_PATH >>> environment >>> variable at run time for perl to find the library. >>> >>> >>> Error: The following dependencies failed to build: p5-xml-parser >>> Error: Status 1 encountered during processing. > -- George Georgalis, information system scientist < From stefmit at gmail.com Mon Jan 7 18:32:31 2008 From: stefmit at gmail.com (Stefmit) Date: Mon Jan 7 18:30:18 2008 Subject: please submit the following update and patch was: [Fwd:[MacPorts] #13845: UPDATE: darkstat 3.0.707] In-Reply-To: <52869.128.250.31.223.1199750853.squirrel@webmail.tuffmail.net> References: <20080107215151.GA1857@foellinger.de> <52869.128.250.31.223.1199750853.squirrel@webmail.tuffmail.net> Message-ID: <200801072032.31642.stefmit@gmail.com> Per http://trac.macosforge.org/projects/macports/changeset/32564 it seems that I have the right Portfile: $less /opt/local/var/macports/sources/rsync.macports.org/release/ports/net/darkstat/Portfile PortSystem 1.0 name darkstat version 3.0.707 categories net platforms darwin maintainers olaf@foellinger.de description network traffic analyzer long_description \ darkstat is a network traffic analyzer. It's basically a packet \ sniffer which runs as a background process on a cable/DSL router and \ gathers all sorts of useless but interesting statistics. homepage http://dmr.ath.cx/net/darkstat/ master_sites ${homepage} use_bzip2 yes checksums md5 91c70f96498dd679b21330214361e4dc \ sha1 a5df521ffbd801b32cb52aaa846fea3448f5750f configure.cflags-append -include stdint.h while: $ sudo port upgrade outdated ---> Building libpcap with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_libpcap/work/libpcap-0.9.8" && make all " returned error 2 Command output: rm -f libpcap.dylib /usr/bin/gcc-4.0 -dynamiclib -o libpcap.`cat VERSION`.dylib \ -install_name /opt/local/lib/libpcap.0.dylib \ -compatibility_version 1.0.0 -current_version `cat VERSION` \ pcap-bpf.o fad-getad.o pcap.o inet.o gencode.o optimize.o nametoaddr.o etherent.o savefile.o bpf_filter.o bpf_image.o bpf_dump.o scanner.o grammar.o version.o Undefined symbols: "_lex_init", referenced from: _pcap_compile in gencode.o "_lex_cleanup", referenced from: _pcap_compile in gencode.o _pcap_compile in gencode.o "_pcap_lex", referenced from: _pcap_parse in grammar.o ld: symbol(s) not found collect2: ld returned 1 exit status make: *** [libpcap.dylib] Error 1 Error: Unable to upgrade port: 1 What am I missing? Stefan On Monday 07 January 2008 18:07:33 Boey Maun Suang wrote: > http://trac.macosforge.org/projects/macports/changeset/32564 From raimue at macports.org Mon Jan 7 18:33:38 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Mon Jan 7 18:31:34 2008 Subject: MacPorts and IPv6 In-Reply-To: <6buhm2$54c50j@toip7.srvr.bell.ca> References: <6buhm2$54c50j@toip7.srvr.bell.ca> Message-ID: <4782E102.9000704@macports.org> Andre-John Mas wrote: > Hi, Hi, > Since MacOS X officially supports IPv6, it would be nice if programs that provide an IPv6 build option could either have IPv6 specified in the default port, or at the very least as a variant. Hopefully everyone is ok with this enhancement request. > > I don't plan on testing the ports for this, but I can say that the Apache2 port already supports IPv6, but the Lynx port doesn't (ticket 13864). Now I fixed that ticket before even reading this mail... Okay, there are many ports which have an +ipv6 variant. But I don't see any reason why IPv6 should not be enabled by default, many other software without extra switches might already support it anyway. At least for now you could add +ipv6 to your variants.conf to install every port with that option if it is provided. But for long term support for IPv6 should be provided by default in my opinion. Rainer From raimue at macports.org Mon Jan 7 18:36:33 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Mon Jan 7 18:34:27 2008 Subject: please submit the following update and patch was: [Fwd:[MacPorts] #13845: UPDATE: darkstat 3.0.707] In-Reply-To: <200801072032.31642.stefmit@gmail.com> References: <20080107215151.GA1857@foellinger.de> <52869.128.250.31.223.1199750853.squirrel@webmail.tuffmail.net> <200801072032.31642.stefmit@gmail.com> Message-ID: <4782E1B1.2080102@macports.org> Stefmit wrote: > $ sudo port upgrade outdated > ---> Building libpcap with target all > Error: Target org.macports.build returned: shell command " > cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_libpcap/work/libpcap-0.9.8" > && make all " returned error 2 [...] > What am I missing? That's libpcap failing and not darkstat. You hit an issue already filed as ticket here: http://trac.macosforge.org/projects/macports/ticket/13802 Rainer From stefmit at gmail.com Mon Jan 7 18:42:55 2008 From: stefmit at gmail.com (Stefmit) Date: Mon Jan 7 18:40:43 2008 Subject: please submit the following update and patch was: [Fwd:[MacPorts] #13845: UPDATE: darkstat 3.0.707] In-Reply-To: <4782E1B1.2080102@macports.org> References: <20080107215151.GA1857@foellinger.de> <200801072032.31642.stefmit@gmail.com> <4782E1B1.2080102@macports.org> Message-ID: <200801072042.55650.stefmit@gmail.com> I am sorry - followed the wrong thread, thus patch - of course it is libpcap, I just reported it earlier ... long Monday, sorry for the screw-up :( Stefan On Monday 07 January 2008 20:36:33 Rainer M?ller wrote: > Stefmit wrote: > > $ sudo port upgrade outdated > > ---> Building libpcap with target all > > Error: Target org.macports.build returned: shell command " > > cd > > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macp > >orts.org_release_ports_net_libpcap/work/libpcap-0.9.8" && make all " > > returned error 2 > > [...] > > > What am I missing? > > That's libpcap failing and not darkstat. > You hit an issue already filed as ticket here: > http://trac.macosforge.org/projects/macports/ticket/13802 > > Rainer From tabithamc at gmail.com Mon Jan 7 19:22:50 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Mon Jan 7 19:20:35 2008 Subject: mod_python fails to build on Leopard In-Reply-To: References: <7fccb3000801070358lc11bc56v39280508cf7cb7d@mail.gmail.com> Message-ID: <7fccb3000801071922j72ba0634p163a04b85277ced5@mail.gmail.com> On 1/7/08, Ryan Schmidt wrote: > > > On Jan 7, 2008, at 05:58, Tabitha McNerney wrote: > > > For anyone that may be interested, I filed a bug report, Ticket > > #13856, regarding attempts to build the mod_python port for use > > with Apache 2 on a fresh system of MacPorts 1.6.0 on Leopard Server > > 10.5.1 > > I've assigned the ticket to the maintainer of mod_python. Don't > forget to do this when filing tickets, otherwise the maintainer might > never see the ticket... > > Hello Ryan, Thank you for the reminder about the best way to file a ticket. What happens when a MacPort doesn't have a maintainer? For example, I filed a Ticket for the Kaffe port but the kaffe port doesn't have a maintainer according to: $ port info kaffe > kaffe 1.1.7, lang/kaffe (Variants: universal, darwin_9) > http://www.kaffe.org > > This is Kaffe, a complete virtual machine and class library set which > allows the execution of Java code. It comes with a virtual machine and a set > of class libraries including beans, and an AWT graphics system. > > Library Dependencies: esound, gmp, gtk2, libart_lgpl, freetype > Platforms: darwin > Maintainers: nomaintainer@macports.org > Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080107/e77cc0fe/attachment.html From ryandesign at macports.org Mon Jan 7 19:31:50 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 19:30:07 2008 Subject: mod_python fails to build on Leopard In-Reply-To: <7fccb3000801071922j72ba0634p163a04b85277ced5@mail.gmail.com> References: <7fccb3000801070358lc11bc56v39280508cf7cb7d@mail.gmail.com> <7fccb3000801071922j72ba0634p163a04b85277ced5@mail.gmail.com> Message-ID: <96A685ED-2E04-4581-AB44-A1B1726845BC@macports.org> On Jan 7, 2008, at 21:22, Tabitha McNerney wrote: > Thank you for the reminder about the best way to file a ticket. > What happens when a MacPort doesn't have a maintainer? For example, > I filed a Ticket for the Kaffe port but the kaffe port doesn't have > a maintainer according to: > > $ port info kaffe [snip] Well, for ports with no maintainer, unfortunately nothing happens, until someone volunteers to take care of it. Ports listed as having no maintainer are open for adoption by anyone who cares about that software. From ryandesign at macports.org Mon Jan 7 19:32:58 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 19:31:17 2008 Subject: please submit the following update and patch was: [Fwd:[MacPorts] #13845: UPDATE: darkstat 3.0.707] In-Reply-To: <20080107215151.GA1857@foellinger.de> References: <20080107215151.GA1857@foellinger.de> Message-ID: <0D824FCA-E1B6-4894-9644-5D4F6BB5209C@macports.org> Regarding ticket #13845: On Jan 7, 2008, at 15:51, Olaf Foellinger wrote: > I've tested the patch and the update, it works, please submit it. boeyms committed the patch and closed the ticket. From ryandesign at macports.org Mon Jan 7 19:44:40 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 19:49:38 2008 Subject: libtool vs. libtool-devel In-Reply-To: <18306.51468.130428.679779@montanaro.dyndns.org> References: <18306.51468.130428.679779@montanaro.dyndns.org> Message-ID: On Jan 7, 2008, at 18:51, skip@pobox.com wrote: > I was seduced by the libtool-devel port (v. 1.9f), which caused me to > deactivate the libtool port (v 1.5.24) in favor of it. As it turns > out, the > automake folks told me 1.9f is pretty old. libtool-devel is unmaintained so it wouldn't surprise me if it's out of date. As all unmaintained ports, it's open for adoption. > The other kicker which got me to try libtool-devel was that the > libtool port > doesn't actually install tools named "libtool" and "libtoolize". I > was > looking for libtoolize, so assumed without investigating that if > 1.9 > 1.5 > and 1.5 doesn't have libtoolize, maybe 1.9 would have it. According to "port contents libtool", it installs glibtool and glibtoolize, not libtool and libtoolize, because that would conflict with Apple's libtool, which is not the same as GNU libtool and should therefore not be replaced with GNU libtool. libtool-devel also uses the "g" prefix. > Given the naive view that a larger version number implies something > a bit > more current and "-devel" implies something a bit more development- > oriented, > shouldn't the libtool-devel port either be renamed or deleted > altogether? The "-devel" suffix indicates a development (non-production-quality, pre-release) version of a port, according to the definition of the developer of the software. To what would you suggest the port name be changed? I think the name "libtool-devel" is accurate, since the port does install a development version of libtool. It can be deleted, but presumably the better course of action would be to update it to the latest development version of libtool. Although, according to http://www.gnu.org/software/libtool/, 1.9f is the latest development version, though it is over 3 years old. I guess the 2.1a version is newer, but they seem to be releasing daily new versions of 2.1a, which isn't helpful. From ryandesign at macports.org Mon Jan 7 19:46:26 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 19:51:23 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <20080108021026.GB29114@run.duo> References: <20080106233000.GC3137@run.duo> <20080107144937.GD3137@run.duo> <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> <20080108021026.GB29114@run.duo> Message-ID: <4043C306-98FB-4F49-B6F7-6AECA57606C0@macports.org> On Jan 7, 2008, at 20:10, George Georgalis wrote: > On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote: > >> On Jan 7, 2008, at 08:49, George Georgalis wrote: >> >>> I have also tried exporting DYLD_LIBRARY_PATH, expat is not found. >> >> That should not be necessary. >> >> I have p5-xml-parser and expat installed. Never seen this problem. >> >> The obvious difference I see is that your MacPorts prefix is >> /usr/local/MacPorts instead of the usual /opt/local. Can you check if >> anything ended up getting installed in the /opt/local by mistake? > > ls: /opt/local: No such file or directory > >> Also, can you tell us your version of MacPorts, Mac OS X, Xcode, >> and your >> processor architecture? > > not sure how to determine xcode version maybe this is good enough? Get Info on /Developer/Applications/Xcode.app in the Finder to find the installed version of Xcode. From ryandesign at macports.org Mon Jan 7 19:30:48 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 19:55:46 2008 Subject: MacPorts and IPv6 In-Reply-To: <4782E102.9000704@macports.org> References: <6buhm2$54c50j@toip7.srvr.bell.ca> <4782E102.9000704@macports.org> Message-ID: <6C346C6A-9353-4A09-A842-5EF46A249A25@macports.org> On Jan 7, 2008, at 20:33, Rainer M?ller wrote: >> Since MacOS X officially supports IPv6, it would be nice if >> programs that provide an IPv6 build option could either have IPv6 >> specified in the default port, or at the very least as a variant. >> Hopefully everyone is ok with this enhancement request. >> I don't plan on testing the ports for this, but I can say that the >> Apache2 port already supports IPv6, but the Lynx port doesn't >> (ticket 13864). > > Now I fixed that ticket before even reading this mail... > > Okay, there are many ports which have an +ipv6 variant. But I don't > see any reason why IPv6 should not be enabled by default, many > other software without extra switches might already support it anyway. > > At least for now you could add +ipv6 to your variants.conf to > install every port with that option if it is provided. But for long > term support for IPv6 should be provided by default in my opinion. Tickets should be filed for each port which does not provide IPv6 support but could. Also, tickets could be filed for each port which provides an +ipv6 variant, to make that support default instead of having it in a variant, because I agree it should be enabled by default. Certain ports may merit an exception (I'm not sure). From skip at pobox.com Mon Jan 7 19:58:43 2008 From: skip at pobox.com (skip@pobox.com) Date: Mon Jan 7 19:56:28 2008 Subject: libtool vs. libtool-devel In-Reply-To: References: <18306.51468.130428.679779@montanaro.dyndns.org> Message-ID: <18306.62707.984869.979446@montanaro.dyndns.org> >> Given the naive view that a larger version number implies something a >> bit more current and "-devel" implies something a bit more >> development- oriented, shouldn't the libtool-devel port either be >> renamed or deleted altogether? Ryan> The "-devel" suffix indicates a development Ryan> (non-production-quality, pre-release) version of a port, according Ryan> to the definition of the developer of the software. Sorry, I'm used to common convention in the Linux arena where the XXX-devel package contains the .h files and such necessary to compile code that uses XXX, while XXX is a binary containing the libXXX library (.so files, etc). Ryan> To what would you suggest the port name be changed? I think the Ryan> name "libtool-devel" is accurate, since the port does install a Ryan> development version of libtool. Ryan> It can be deleted, but presumably the better course of action Ryan> would be to update it to the latest development version of Ryan> libtool. Although, according to Ryan> http://www.gnu.org/software/libtool/, 1.9f is the latest Ryan> development version, though it is over 3 years old. I guess the Ryan> 2.1a version is newer, but they seem to be releasing daily new Ryan> versions of 2.1a, which isn't helpful. Given that it's unmaintained, I can't see that deleting it should be all that big a deal. It's apparently way behind the current development bleeding edge (which as you suggest might leave one pretty bloody to use it). I guess that given the meaning of "-devel" (is that a consistent meaning throughout MacPorts?), it's best left as-is. Once burned, twice shy, so I will stay away from -devel packages in the future unless there is no alternative. Thanks, Skip From ryandesign at macports.org Mon Jan 7 20:21:36 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 20:19:55 2008 Subject: libtool vs. libtool-devel In-Reply-To: <18306.62707.984869.979446@montanaro.dyndns.org> References: <18306.51468.130428.679779@montanaro.dyndns.org> <18306.62707.984869.979446@montanaro.dyndns.org> Message-ID: <8A60A5ED-4A8B-4129-9B30-B49BEAF95CC3@macports.org> On Jan 7, 2008, at 21:58, skip@pobox.com wrote: >>> Given the naive view that a larger version number implies >>> something a >>> bit more current and "-devel" implies something a bit more >>> development- oriented, shouldn't the libtool-devel port either be >>> renamed or deleted altogether? >> > >> The "-devel" suffix indicates a development > >> (non-production-quality, pre-release) version of a port, according > >> to the definition of the developer of the software. > > > Sorry, I'm used to common convention in the Linux arena where the > XXX-devel > package contains the .h files and such necessary to compile code > that uses > XXX, while XXX is a binary containing the libXXX library (.so > files, etc). Right, that's a difference between MacPorts and some other package managers. In MacPorts, the .h files and other necessary files for compiling code are already included in every port. The -devel ports are merely newer development versions of the software (or, sometimes, older versions of the software, in the event that no new development versions have been released following a stable release). >> It can be deleted, but presumably the better course of action > >> would be to update it to the latest development version of > >> libtool. Although, according to > >> http://www.gnu.org/software/libtool/, 1.9f is the latest > >> development version, though it is over 3 years old. I guess the > >> 2.1a version is newer, but they seem to be releasing daily new > >> versions of 2.1a, which isn't helpful. > > > Given that it's unmaintained, I can't see that deleting it should > be all > that big a deal. It's apparently way behind the current development > bleeding edge (which as you suggest might leave one pretty bloody > to use > it). I guess that given the meaning of "-devel" (is that a consistent > meaning throughout MacPorts?), it's best left as-is. Ok, let's leave it for now. Perhaps the libtool developers should be encouraged to release a new development version. Surely something useful has been changed in the past 3 years to merit a new release. > Once burned, twice shy, so I will stay away from -devel packages in > the > future unless there is no alternative. Right, there's usually no need to install -devel ports. I don't have any installed. From george at galis.org Mon Jan 7 20:30:25 2008 From: george at galis.org (George Georgalis) Date: Mon Jan 7 21:28:54 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <4043C306-98FB-4F49-B6F7-6AECA57606C0@macports.org> References: <20080106233000.GC3137@run.duo> <20080107144937.GD3137@run.duo> <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> <20080108021026.GB29114@run.duo> <4043C306-98FB-4F49-B6F7-6AECA57606C0@macports.org> Message-ID: <20080108043025.GD29114@run.duo> On Mon, Jan 07, 2008 at 09:46:26PM -0600, Ryan Schmidt wrote: > On Jan 7, 2008, at 20:10, George Georgalis wrote: > >> On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote: >> >>> On Jan 7, 2008, at 08:49, George Georgalis wrote: >>> >>>> I have also tried exporting DYLD_LIBRARY_PATH, expat is not found. >>> >>> That should not be necessary. >>> >>> I have p5-xml-parser and expat installed. Never seen this problem. >>> >>> The obvious difference I see is that your MacPorts prefix is >>> /usr/local/MacPorts instead of the usual /opt/local. Can you check if >>> anything ended up getting installed in the /opt/local by mistake? >> >> ls: /opt/local: No such file or directory >> >>> Also, can you tell us your version of MacPorts, Mac OS X, Xcode, and your >>> processor architecture? >> >> not sure how to determine xcode version maybe this is good enough? > > Get Info on /Developer/Applications/Xcode.app in the Finder to find the > installed version of Xcode. okay, Xcode version 2.3 from Aug 11 2006. I guess that's not part of 'Software Update' ...I have no reservations about updating it if that may be the issue. // George -- George Georgalis, information system scientist < From ryandesign at macports.org Mon Jan 7 21:44:59 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 7 22:12:18 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <20080108043025.GD29114@run.duo> References: <20080106233000.GC3137@run.duo> <20080107144937.GD3137@run.duo> <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> <20080108021026.GB29114@run.duo> <4043C306-98FB-4F49-B6F7-6AECA57606C0@macports.org> <20080108043025.GD29114@run.duo> Message-ID: <451EBF42-377F-4ACB-80F8-9D9368945BB9@macports.org> On Jan 7, 2008, at 22:30, George Georgalis wrote: > On Mon, Jan 07, 2008 at 09:46:26PM -0600, Ryan Schmidt wrote: > >> On Jan 7, 2008, at 20:10, George Georgalis wrote: >> >>> On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote: >>> >>>> On Jan 7, 2008, at 08:49, George Georgalis wrote: >>>> >>>>> I have also tried exporting DYLD_LIBRARY_PATH, expat is not found. >>>> >>>> That should not be necessary. >>>> >>>> I have p5-xml-parser and expat installed. Never seen this problem. >>>> >>>> The obvious difference I see is that your MacPorts prefix is >>>> /usr/local/MacPorts instead of the usual /opt/local. Can you >>>> check if >>>> anything ended up getting installed in the /opt/local by mistake? >>> >>> ls: /opt/local: No such file or directory >>> >>>> Also, can you tell us your version of MacPorts, Mac OS X, Xcode, >>>> and your >>>> processor architecture? >>> >>> not sure how to determine xcode version maybe this is good enough? >> >> Get Info on /Developer/Applications/Xcode.app in the Finder to >> find the >> installed version of Xcode. > > okay, Xcode version 2.3 from Aug 11 2006. > > I guess that's not part of 'Software Update' > > ...I have no reservations about updating it if that may be the issue. Xcode 2.4.1 ought to work fine, as should the latest which is 2.5, but 2.3 may be too old. It's a big download but I recommend it. http://developer.apple.com/tools/download/ From ryandesign at macports.org Tue Jan 8 01:28:14 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 8 01:28:53 2008 Subject: ocaml fails on Tiger (was: Re: sudo port install mldonkey) In-Reply-To: <20080108090803.GA5166@marco.fz-rossendorf.de> References: <590A936D-453F-4369-9E09-69E7D05001B2@gmail.com> <53DF8FAC-D824-438D-8AF1-6B62D94BC177@gmail.com> <903349F2-4D42-4AC6-AA07-DDE14D0C8D5E@macports.org> <20080107103215.GB9144@marco.fz-rossendorf.de> <9647D02E-22CC-44F3-AAE0-813DF4D640BC@macports.org> <20080108090803.GA5166@marco.fz-rossendorf.de> Message-ID: <08EAC7E0-A0CD-45AC-89A3-A980BF820C61@macports.org> On Jan 8, 2008, at 03:08, Joerg van den Hoff wrote: > On Mon, Jan 07, 2008 at 03:14:21PM -0600, Ryan Schmidt wrote: > >> On Jan 7, 2008, at 04:32, Joerg van den Hoff wrote: >> >>> On Fri, Jan 04, 2008 at 12:05:14PM -0600, Ryan Schmidt wrote: >>> >>>> On Jan 4, 2008, at 09:41, Charlse Darwin wrote: >>>> >>>>> Mac:~ pm$ sudo port -f install mldonkey >>>>> ---> Fetching ocaml [snip] >>>>> # How do I get it to skip ocaml? >>>> >>>> There isn't a built-in way to do that. MacPorts is designed not to >>>> make use of any software you install outside of MacPorts. You could >>>> possibly modify the portfile to look for ocaml in a different >>>> directory. But what we would really like is for someone to >>>> figure out >>>> why the ocaml port fails to build, and fix it. >>> >>> is there hope (i.e. is the package still actively >>> maintained)? >>> >>> would it be helpful to "cross post" this issue on one of the >>> ocaml lists asking for opinions/help? if so, where to send >>> potential answers? to "pguyot@kallisys.net" as >>> >>> `port info ocaml' >>> >>> tells me? >> >> If you want to know if a package is being actively maintained, you >> should email the package maintainer. If "nomaintainer" is the package >> maintainer, then it is not being maintained. >> >> The problems Charlse Darwin was experiencing were the result of his >> unique setup which included a broken sed program. >> >> The general problems building ocaml on Tiger which were reported in >> ticket 13583 were resolved by me 3 days ago because the maintainer >> had not responded to the issue. >> >> After you "sudo port selfupdate" do you still see any problems? > > thanks. > > I upgraded to 3.10.0 already some time ago (when it appeared > on macports) without problems (sorry for not being specific > in this respect). _should_ I have experienced problems at > that time?? Nope, if you were on Tiger, it should have worked fine, initially. See, when ocaml was first updated to 3.10.0 (r25800, 2007-06-02), it worked on Tiger, but not on Leopard. Then later (r30771, 2007-11-06), a fix was committed for Leopard, but it only worked on MacPorts trunk, not the latest released version of MacPorts, 1.5.2. Then the Leopard fix was changed (r31240, 2007-11-18), but this broke the build on Tiger. Then I fixed it (r32486, 2008-01-04) so the Leopard- specific fix was applied only on Leopard, fixing the build on Tiger. But by this point MacPorts 1.6.0 had been released, so Kevin restored the original Leopard fix (r32488, 2008-01-04). You can see the history of the port's changes in the Trac repository browser: http://trac.macports.org/projects/macports/log/trunk/dports/lang/ocaml > my question was a general one: ocaml is a very good piece of > software so I'd like to see it supported by macports in the > future. The port has a maintainer. If a maintainer is unresponsive to an issue for 72 hours, another committer can take care of a problem, if a solution is known. If you or anyone would like to take over maintenance of a port, or would like to co-maintain a port with the current maintainer, you should contact the maintainer. If you get no response from the maintainer after repeated attempts, we can consider the maintainer gone and change it to nomaintainer, or to yourself or anyone else who wants to take it over. From ryandesign at macports.org Tue Jan 8 03:24:10 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 8 03:24:49 2008 Subject: qt3-mac In-Reply-To: <40531123-7057-4D10-A7A1-A706E793E57B@mus.ch> References: <658BE300-DFCB-450A-8BD1-7D1E16129D6E@mus.ch> <6F7DBCC7-E16C-4750-BD95-D675EEC0E3AF@macports.org> <40531123-7057-4D10-A7A1-A706E793E57B@mus.ch> Message-ID: <7B04E827-246A-4BC5-9EEE-39A0C40BECAC@macports.org> Don't forget to Reply All (not just Reply) so that your reply goes to the list too, not just to me. On Jan 8, 2008, at 05:07, Leo Studer wrote: > On 07.01.2008, at 21:55, Ryan Schmidt wrote: > >> You need to give us more of the error message. Why did qt3-mac >> fail to build? > > here is what happens on my macbook pro X 10.5.1 with xcode 3.0 > > ---> Configuring qt3-mac > Error: Target org.macports.configure returned: configure failure: > shell command " cd "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_ > qt3-mac/work/qt-mac-free-3.3.8" && echo yes | ./configure --prefix=/ > opt/local -v -prefix '/opt/local' -docdir '/opt/local/share/doc/qt3- > mac/html' -datadir '/opt/local/share/qt3' -headerdir '/opt/local/ > include/qt3' -plugindir '/opt/local/lib/qt3-plugins' -release - > shared -fast -thread -stl -qt-gif -qt-imgfmt-png -qt-imgfmt-jpeg - > qt-imgfmt-mng -no-sql-ibase -no-sql-mysql -no-sql-odbc -no-sql-psql > -no-sql-sqlite -no-nis -no-cups -no-ipv6 -largefile -system-zlib - > system-libpng -system-libjpeg -system-libmng '-I/opt/local/include' > '-L/opt/local/lib' " returned error 2 > Command output: PostgreSQL auto-detection... > Could not find libpq.* anywhere in /lib /usr/lib /opt/local/lib > PostgreSQL disabled. > Testing Mac version... > mac_version.cpp:5: error: missing terminating " character > mac_version.cpp:6: error: missing terminating " character > mac_version.cpp: In function 'int main()': > mac_version.cpp:7: error: expected primary-expression before 'return' > Mac version cannot be detected! > > This is the Qt/Mac Open Source Edition. > > You are licensed to use this software under the terms of > the GNU General Public License (GPL). > > Type 'G' to view the GNU General Public License. > Type 'yes' to accept this license offer. > Type 'no' to decline this license offer. > > Do you accept the terms of the license? > Creating qmake. Please wait... > c++ -c -o project.o -pipe -DQT_MACOSX_VERSION= -I. -Igenerators - > Igenerators/unix -Igenerators/win32 -Igenerators/mac -I/opt/local/ > var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_ > qt3-mac/work/qt-mac-free-3.3.8/include/qmake -I/opt/local/var/ > macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_ > qt3-mac/work/qt-mac-free-3.3.8/include -I/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_ > qt3-mac/work/qt-mac-free-3.3.8/include -DQT_NO_TEXTCODEC - > DQT_NO_UNICODETABLES -DQT_NO_COMPONENT -DQT_NO_STL -DQT_NO_COMPRESS > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_ > qt3-mac/work/qt-mac-free-3.3.8/mkspecs/macx-g++ -DHAVE_QCONFIG_CPP > project.cpp > In file included from /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_ > qt3-mac/work/qt-mac-free-3.3.8/include/qtl.h:42, > from /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_ > qt3-mac/work/qt-mac-free-3.3.8/include/qvaluelist.h:42, > from /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_ > qt3-mac/work/qt-mac-free-3.3.8/include/qstringlist.h:42, > from project.h:39, > from project.cpp:36: > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_ > qt3-mac/work/qt-mac-free-3.3.8/include/qglobal.h:187:6: error: > #error "This version of Mac OS X is unsupported" > make: *** [project.o] Error 1 > qmake failed to build. Aborting. > > Error: The following dependencies failed to build: qt3-mac > Error: Status 1 encountered during processing. > >> We already have one ticket about qt3-mac failing to build on Leopard: >> >> http://trac.macosforge.org/projects/macports/ticket/13208 > > This seems not the same issue? Well, I think it might be the same issue. Not sure, since the person who filed that ticket did not include the error output they're getting. But the issue (qt3-mac doesn't support Leopard) is the same, so maybe that existing ticket is sufficient. I can add you to the ticket's Cc list if you would like to be informed of any changes made to it. >> Is that what you're seeing? If so, then we know about it, and >> hopefully the maintainer of qt3-mac will resolve it soon. If >> you're seeing a different issue, then you should file a ticket on it. > > How do I do that? Instructions for filing tickets, should you want to do so for other issues, are in the guide. See this section: http://guide.macports.org/#project From leo.studer at mus.ch Tue Jan 8 06:01:36 2008 From: leo.studer at mus.ch (Leo Studer) Date: Tue Jan 8 06:01:40 2008 Subject: qt3-mac In-Reply-To: <7B04E827-246A-4BC5-9EEE-39A0C40BECAC@macports.org> References: <658BE300-DFCB-450A-8BD1-7D1E16129D6E@mus.ch> <6F7DBCC7-E16C-4750-BD95-D675EEC0E3AF@macports.org> <40531123-7057-4D10-A7A1-A706E793E57B@mus.ch> <7B04E827-246A-4BC5-9EEE-39A0C40BECAC@macports.org> Message-ID: > > On 08.01.2008, at 12:24, Ryan Schmidt wrote: > > Don't forget to Reply All (not just Reply) so that your reply goes > to the list too, not just to me. Thanks for this suggestion. > > > On Jan 8, 2008, at 05:07, Leo Studer wrote: > >> On 07.01.2008, at 21:55, Ryan Schmidt wrote: >> >>> You need to give us more of the error message. Why did qt3-mac >>> fail to build? >> >> here is what happens on my macbook pro X 10.5.1 with xcode 3.0 >> >> ---> Configuring qt3-mac >> Error: Target org.macports.configure returned: configure failure: >> shell command " cd "/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_qt3-mac/work/qt-mac-free-3.3.8" && >> echo yes | ./configure --prefix=/opt/local -v -prefix '/opt/local' - >> docdir '/opt/local/share/doc/qt3-mac/html' -datadir '/opt/local/ >> share/qt3' -headerdir '/opt/local/include/qt3' -plugindir '/opt/ >> local/lib/qt3-plugins' -release -shared -fast -thread -stl -qt-gif - >> qt-imgfmt-png -qt-imgfmt-jpeg -qt-imgfmt-mng -no-sql-ibase -no-sql- >> mysql -no-sql-odbc -no-sql-psql -no-sql-sqlite -no-nis -no-cups -no- >> ipv6 -largefile -system-zlib -system-libpng -system-libjpeg -system- >> libmng '-I/opt/local/include' '-L/opt/local/lib' " returned error 2 >> Command output: PostgreSQL auto-detection... >> Could not find libpq.* anywhere in /lib /usr/lib /opt/local/lib >> PostgreSQL disabled. >> Testing Mac version... >> mac_version.cpp:5: error: missing terminating " character >> mac_version.cpp:6: error: missing terminating " character >> mac_version.cpp: In function 'int main()': >> mac_version.cpp:7: error: expected primary-expression before 'return' >> Mac version cannot be detected! >> >> This is the Qt/Mac Open Source Edition. >> >> You are licensed to use this software under the terms of >> the GNU General Public License (GPL). >> >> Type 'G' to view the GNU General Public License. >> Type 'yes' to accept this license offer. >> Type 'no' to decline this license offer. >> >> Do you accept the terms of the license? >> Creating qmake. Please wait... >> c++ -c -o project.o -pipe -DQT_MACOSX_VERSION= -I. -Igenerators - >> Igenerators/unix -Igenerators/win32 -Igenerators/mac -I/opt/local/ >> var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_qt3-mac/work/qt-mac-free-3.3.8/ >> include/qmake -I/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_qt3-mac/work/qt-mac-free-3.3.8/ >> include -I/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_qt3-mac/work/qt-mac-free-3.3.8/ >> include -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_NO_COMPONENT - >> DQT_NO_STL -DQT_NO_COMPRESS -I/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_qt3-mac/work/qt-mac-free-3.3.8/ >> mkspecs/macx-g++ -DHAVE_QCONFIG_CPP project.cpp >> In file included from /opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_qt3-mac/work/qt-mac-free-3.3.8/ >> include/qtl.h:42, >> from /opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_qt3-mac/work/qt-mac-free-3.3.8/ >> include/qvaluelist.h:42, >> from /opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_qt3-mac/work/qt-mac-free-3.3.8/ >> include/qstringlist.h:42, >> from project.h:39, >> from project.cpp:36: >> /opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_qt3-mac/work/qt-mac-free-3.3.8/ >> include/qglobal.h:187:6: error: #error "This version of Mac OS X is >> unsupported" >> make: *** [project.o] Error 1 >> qmake failed to build. Aborting. >> >> Error: The following dependencies failed to build: qt3-mac >> Error: Status 1 encountered during processing. >> >>> We already have one ticket about qt3-mac failing to build on >>> Leopard: >>> >>> http://trac.macosforge.org/projects/macports/ticket/13208 >> >> This seems not the same issue? > > Well, I think it might be the same issue. Not sure, since the person > who filed that ticket did not include the error output they're > getting. But the issue (qt3-mac doesn't support Leopard) is the > same, so maybe that existing ticket is sufficient. I can add you to > the ticket's Cc list if you would like to be informed of any changes > made to it. yes, please > > > >>> Is that what you're seeing? If so, then we know about it, and >>> hopefully the maintainer of qt3-mac will resolve it soon. If >>> you're seeing a different issue, then you should file a ticket on >>> it. >> >> How do I do that? > > Instructions for filing tickets, should you want to do so for other > issues, are in the guide. See this section: > > http://guide.macports.org/#project > Thanks From face at CentosPrime.COM Tue Jan 8 07:49:14 2008 From: face at CentosPrime.COM (Chris Janton) Date: Tue Jan 8 07:49:20 2008 Subject: TRAC down? Message-ID: <2C82067D-0096-4E40-897D-E28DE5F4D92E@centosprime.com> Anyone else having trouble connecting to the Trac system? http://www.macosforge.org/wp-login.php Login to trac failed! Message was " $PROJECT_SEARCH_PATH="/trac/env";". I have another port with a "cd" command that needs to be "fixed". 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From stefan.schwarzer at grid.unep.ch Tue Jan 8 07:51:57 2008 From: stefan.schwarzer at grid.unep.ch (Stefan Schwarzer) Date: Tue Jan 8 07:52:00 2008 Subject: "The following install step failed: run postflight script for MacPorts-1.6.0." Message-ID: Hi there, I wanted to install MacPorts on my Mac - MacPro with Leopard, latest version. But, while using the disk image, the installation finished with this message: "The following install step failed: run postflight script for MacPorts-1.6.0." Can anyone let me know what I should do? Thanks for any hints! Stef ____________________________________________________________________ Stefan Schwarzer Lean Back and Relax - Enjoy some Nature Photography http://photoblog.la-famille-schwarzer.de Appetite for Global Data? UNEP GEO Data Portal: http://geodata.grid.unep.ch ____________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080108/4d7faa3f/attachment.html From wsiegrist at apple.com Tue Jan 8 07:57:20 2008 From: wsiegrist at apple.com (William Siegrist) Date: Tue Jan 8 07:58:55 2008 Subject: TRAC down? In-Reply-To: <2C82067D-0096-4E40-897D-E28DE5F4D92E@centosprime.com> References: <2C82067D-0096-4E40-897D-E28DE5F4D92E@centosprime.com> Message-ID: <9A15F3AB-5C14-4DE5-9041-F25CA002DFEE@apple.com> Sorry about that, we had some trouble with the maintenance and did not catch the login problem till this morning. It should be fixed now. Let me know (admin@macosforge.org) if you still have trouble. -Bill On Jan 8, 2008, at 7:49 AM, Chris Janton wrote: > Anyone else having trouble connecting to the Trac system? > > > http://www.macosforge.org/wp-login.php > > Login to trac failed! Message was " $PROJECT_SEARCH_PATH="/trac/ > env";". > > I have another port with a "cd" command that needs to be "fixed". > > 8) > ---------------------------------- > Chris Janton - face at CentosPrime dot COM > Netminder for Opus1.COM > > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users ---- William Siegrist Software Support Engineer Mac OS Forge http://macosforge.org/ wsiegrist@apple.com 408 862 7337 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2421 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080108/33d703c6/smime.bin From george at galis.org Tue Jan 8 09:05:58 2008 From: george at galis.org (George Georgalis) Date: Tue Jan 8 09:06:02 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <451EBF42-377F-4ACB-80F8-9D9368945BB9@macports.org> References: <20080106233000.GC3137@run.duo> <20080107144937.GD3137@run.duo> <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> <20080108021026.GB29114@run.duo> <4043C306-98FB-4F49-B6F7-6AECA57606C0@macports.org> <20080108043025.GD29114@run.duo> <451EBF42-377F-4ACB-80F8-9D9368945BB9@macports.org> Message-ID: <20080108170558.GH29114@run.duo> On Mon, Jan 07, 2008 at 11:44:59PM -0600, Ryan Schmidt wrote: > On Jan 7, 2008, at 22:30, George Georgalis wrote: > >> On Mon, Jan 07, 2008 at 09:46:26PM -0600, Ryan Schmidt wrote: >>> >>> Get Info on /Developer/Applications/Xcode.app in the Finder to find the >>> installed version of Xcode. >> >> okay, Xcode version 2.3 from Aug 11 2006. >> >> I guess that's not part of 'Software Update' >> >> ...I have no reservations about updating it if that may be the issue. > > Xcode 2.4.1 ought to work fine, as should the latest which is 2.5, but 2.3 > may be too old. It's a big download but I recommend it. > > http://developer.apple.com/tools/download/ Okay, downloading, will try tonight. To reduce consumed disk space after it's all in place, should I think about purging /Developer before I start the install? is that even necessary? Is there something else that is better to do? // George -- George Georgalis, information system scientist < From dbreiser at gmail.com Tue Jan 8 10:27:33 2008 From: dbreiser at gmail.com (David Reiser) Date: Tue Jan 8 10:27:35 2008 Subject: gnucash - aqbanking build fails In-Reply-To: <547667.83789.qm@web26903.mail.ukl.yahoo.com> References: <547667.83789.qm@web26903.mail.ukl.yahoo.com> Message-ID: <69812df90801081027k2faf8445n7357289b94e07496@mail.gmail.com> On Dec 19, 2007 5:50 AM, Peter Schneider wrote: > [snip] > > Hay anyone tried a manual build (./configure && make > && make install -> /usr/local) of gnucash + some newer > version of aqbanking and gwenhywfar? I guess from that > point on it shouldn't be too difficult to adapt the > portfile for building gwenhywfar and aqbanking 3.0.1 .. > I'm getting to this a little late, but since the thread doesn't show an update, I'll chime in. Gnucash doesn't work yet with aqbanking 3.x. Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080108/f0892118/attachment-0001.html From sfiera at macports.org Tue Jan 8 10:44:09 2008 From: sfiera at macports.org (Chris Pickel) Date: Tue Jan 8 10:44:26 2008 Subject: Problems using macports In-Reply-To: <4783358B.40702@email.it> References: <47821F8C.9020600@email.it> <4782A775.7070208@email.it> <8DDB5AC6-2DC0-4FF7-9EA1-924202DB0077@macports.org> <4783358B.40702@email.it> Message-ID: [resending to list] On 08 Jan, 2008, at 3:34, muffetta66 wrote: > Chris Pickel ha scritto: >> On 07 Jan, 2008, at 17:28, muffetta66 wrote: >>> Chris Pickel ha scritto: >>>> On 07 Jan, 2008, at 7:48, muffetta66 wrote: >>>>> ibook-g4-di-*************-********:~ *************$ sudo port >>>>> install mc >>>>> Password: >>>>> ---> Extracting libiconv >>>>> Error: Target org.macports.extract returned: shell command " cd >>>>> "/opt/local/var/macports/build/ >>>>> _opt_local_var_macports_sources_rsync >>>>> .macports.org_release_ports_textproc_libiconv/work" && gzip -dc / >>>>> opt/local/var/macports/distfiles/libiconv/libiconv-1.12.tar.gz | >>>>> -xf - " returned error 127 >>>>> Command output: sh: line 1: -xf: command not found >>>> >>>> Looks like you have `tar` missing. What's the value of >>>> tar_command on your system? You can get it as follows: >>>> >>>> % cat /opt/local/share/macports/Tcl/port1.0/port_autoconf.tcl | >>>> grep tar >>>> variable tar_command "/usr/bin/gnutar --no-same-owner" >>>> >>>> I'm assuming that the value will be missing on your system. As >>>> you can see, on my system it refers to /usr/bin/gnutar: >>>> >>>> % /usr/bin/gnutar --version >>>> tar (GNU tar) 1.15.1 >>>> >>>> It's possible that you could fix your problem simply by editing >>>> port_autoconf.tcl, but that would break upon selfupdating, and it >>>> would be better to know why it didn't originally find the tar >>>> command. >>>> >>> Yes!! was exactly that (the gnutar/tat missing value!) >>> Many thanks >> >> But did `/usr/bin/gnutar --version` give the expected output? >> There's something being detected wrong on your system, and it will >> probably break again when you selfupdate if we don't know what the >> cause is. >> >> >> Chris >> > This is the output: > $ gnutar --version > tar (GNU tar) 1.14 +CVE-2006-0300 +CVE-2006-6097 > > $ tar --version > tar (GNU tar) 1.14 +CVE-2006-0300 +CVE-2006-6097 > > And this is mine port_autoconf.tcl: > package provide port 1.0 > > namespace eval portutil::autoconf { > variable cvs_path "/usr/bin/cvs" > variable svn_path "" > variable rsync_path "/usr/bin/rsync" > variable mtree_path "/usr/sbin/mtree" > variable xar_path "" > variable sed_command "/usr/bin/sed" > variable sed_ext_flag "-E" > variable tar_command "/usr/bin/tar" > variable have_launchd "yes" > variable launchctl_path "/bin/launchctl" > variable install_user "root" > variable install_group "admin" > variable prefix "/opt/local" > > > Should i use gnutar instead of tar? should i update to 1.15? > > Many thanks for youtr patient, it's my first experience with ports, > scripts, commands line, compilers, programming...etc in this > environvemt, just curiosity because Mac OS X by hearsay should be > similar to UNIX/Linux, and i used a little only linux suse, red-hat, > ubunto and mandriva. but nothing about the command line or similar > in both. Your version of tar seems to be the one that's provided with Tiger. If you have Tiger, then you should keep that version. I'm not sure what caused your problem, but I'd suggest trying `sudo port -f selfupdate` and making sure MacPorts to continues to work thereafter. If it does, then the problem shouldn't appear again. Chris From merrick.jd at gmail.com Tue Jan 8 12:09:16 2008 From: merrick.jd at gmail.com (J.D. Merrick) Date: Tue Jan 8 12:09:19 2008 Subject: Does MacPorts require XCode 3.0's UNIX developer support? Message-ID: <905E7B6E-7990-467B-B1B6-BB9376BAD6C1@gmail.com> When installing Xcode 3.0 on Leopard, by default Unix developer support is disabled. That is, by default the command line tools (gcc, ld, etc.) are installed in /Developer without adding to the boot volume symlinks to the tools in /usr/bin or to the header files in /usr/include. Does MacPorts, including both the application itself as well as its individual ports, require those tools to be in /usr? Or, is it just necessary for the tools to be visible in one's PATH? The issue would arise if, for example, makefiles used hardcoded paths like /usr/bin/gcc or #include directives used paths like /usr/include/ stdio.h. Do port maintainers attempt to remove such fully qualified filenames when working on a port? I'd prefer not to have the development tools in /usr just because I just like keeping the root file system as clean as possible. But if MacPorts needs it, I'll break the rule. Thanks in advance, J.D. From ryandesign at macports.org Tue Jan 8 13:03:24 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 8 13:04:01 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <20080108170558.GH29114@run.duo> References: <20080106233000.GC3137@run.duo> <20080107144937.GD3137@run.duo> <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> <20080108021026.GB29114@run.duo> <4043C306-98FB-4F49-B6F7-6AECA57606C0@macports.org> <20080108043025.GD29114@run.duo> <451EBF42-377F-4ACB-80F8-9D9368945BB9@macports.org> <20080108170558.GH29114@run.duo> Message-ID: On Jan 8, 2008, at 11:05, George Georgalis wrote: > On Mon, Jan 07, 2008 at 11:44:59PM -0600, Ryan Schmidt wrote: > >> On Jan 7, 2008, at 22:30, George Georgalis wrote: >> >>> On Mon, Jan 07, 2008 at 09:46:26PM -0600, Ryan Schmidt wrote: >>> >>>> Get Info on /Developer/Applications/Xcode.app in the Finder to >>>> find the >>>> installed version of Xcode. >>> >>> okay, Xcode version 2.3 from Aug 11 2006. >>> >>> I guess that's not part of 'Software Update' >>> >>> ...I have no reservations about updating it if that may be the >>> issue. >> >> Xcode 2.4.1 ought to work fine, as should the latest which is 2.5, >> but 2.3 >> may be too old. It's a big download but I recommend it. >> >> http://developer.apple.com/tools/download/ > > Okay, downloading, will try tonight. To reduce consumed disk space > after it's all in place, should I think about purging /Developer > before I start the install? is that even necessary? Is there > something else that is better to do? I assume that installing Xcode 2.5 will be smart about removing obsolete parts of Xcode 2.3 first. If you're concerned that it won't be, you could first run the Xcode 2.3 uninstall script. (Xcode installs things in more places than just /Developer.) The uninstall script is probably on the Xcode 2.3 CD or disk image. From afb at macports.org Tue Jan 8 13:23:56 2008 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Tue Jan 8 13:23:59 2008 Subject: Does MacPorts require XCode 3.0's UNIX developer support? In-Reply-To: <905E7B6E-7990-467B-B1B6-BB9376BAD6C1@gmail.com> References: <905E7B6E-7990-467B-B1B6-BB9376BAD6C1@gmail.com> Message-ID: J.D. Merrick wrote: > When installing Xcode 3.0 on Leopard, by default Unix developer > support is disabled. That is, by default the command line tools (gcc, > ld, etc.) are installed in /Developer without adding to the boot > volume symlinks to the tools in /usr/bin or to the header files in > /usr/include. When I installed Xcode 3.0, it did install to /usr. (I think Xcode 2.5 installed into "/Xcode2.5") > Does MacPorts, including both the application itself as well as its > individual ports, require those tools to be in /usr? Or, is it just > necessary for the tools to be visible in one's PATH? Yes, several paths such as /usr/bin/gcc-4.0 are currently hardcoded within base (and in ports too) --anders From ryandesign at macports.org Tue Jan 8 13:35:04 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 8 13:35:41 2008 Subject: "The following install step failed: run postflight script for MacPorts-1.6.0." In-Reply-To: References: Message-ID: <8D63E40A-5563-488C-9E4A-302098EC13A9@macports.org> On Jan 8, 2008, at 09:51, Stefan Schwarzer wrote: > I wanted to install MacPorts on my Mac - MacPro with Leopard, > latest version. But, while using the disk image, the installation > finished with this message: "The following install step failed: run > postflight script for MacPorts-1.6.0." > > Can anyone let me know what I should do? I'm not sure... Were you using the correct disk image? the one whose name is MacPorts-1.6.0-10.5-Leopard.dmg? If so, can you just try installing it again, see if it works now? From mail at thorstenzoerner.de Tue Jan 8 14:29:50 2008 From: mail at thorstenzoerner.de (=?ISO-8859-1?Q?Thorsten_Z=F6rner?=) Date: Tue Jan 8 14:29:52 2008 Subject: New Scribus version out Message-ID: <54A4130C-7984-470E-8FB5-5BFB418E92D2@thorstenzoerner.de> Hi there, over at the Scribus list, I heard that there is a new stable version of Scribus out, namely 1.3.3.10. How and when will I be able to get it on my MacPorts? What is the procedure like? Cheers, Thorsten. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2429 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080108/1408ea8f/smime.bin From ryandesign at macports.org Tue Jan 8 14:42:23 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 8 14:43:01 2008 Subject: New Scribus version out In-Reply-To: <54A4130C-7984-470E-8FB5-5BFB418E92D2@thorstenzoerner.de> References: <54A4130C-7984-470E-8FB5-5BFB418E92D2@thorstenzoerner.de> Message-ID: On Jan 8, 2008, at 16:29, Thorsten Z?rner wrote: > over at the Scribus list, I heard that there is a new stable > version of Scribus out, namely 1.3.3.10. > > How and when will I be able to get it on my MacPorts? > What is the procedure like? You should file an update request ticket in our issue tracker, if one does not already exist. Even better would be if you would update the portfile yourself, test it, make sure it works, then attach your patch to the ticket. Usually the port maintainer would notice that a new version is available and test and update the port. However, the scribus port has no maintainer. If you are interested in being its maintainer, let us know. From mail at thorstenzoerner.de Tue Jan 8 14:52:23 2008 From: mail at thorstenzoerner.de (=?ISO-8859-1?Q?Thorsten_Z=F6rner?=) Date: Tue Jan 8 14:52:24 2008 Subject: New Scribus version out In-Reply-To: References: <54A4130C-7984-470E-8FB5-5BFB418E92D2@thorstenzoerner.de> Message-ID: On 08.01.08, at 23:42, Ryan Schmidt wrote: > On Jan 8, 2008, at 16:29, Thorsten Z?rner wrote: > >> over at the Scribus list, I heard that there is a new stable >> version of Scribus out, namely 1.3.3.10. >> >> How and when will I be able to get it on my MacPorts? >> What is the procedure like? > > You should file an update request ticket in our issue tracker, if > one does not already exist. Even better would be if you would update > the portfile yourself, test it, make sure it works, then attach your > patch to the ticket. > > Usually the port maintainer would notice that a new version is > available and test and update the port. However, the scribus port > has no maintainer. If you are interested in being its maintainer, > let us know. > Hi Ryan, sounds cool, but I am just a poor user so far... I will try and update my portfile and so on. If I succeed, I'll apply for becoming a maintainer... quick career, don't you think. :-) Cheers, Thorsten. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2429 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080108/3fa9fe8a/smime-0001.bin From mail at thorstenzoerner.de Tue Jan 8 15:20:21 2008 From: mail at thorstenzoerner.de (=?ISO-8859-1?Q?Thorsten_Z=F6rner?=) Date: Tue Jan 8 15:20:23 2008 Subject: New Scribus version out In-Reply-To: References: <54A4130C-7984-470E-8FB5-5BFB418E92D2@thorstenzoerner.de> Message-ID: On 08.01.08, at 23:42, Ryan Schmidt wrote: > On Jan 8, 2008, at 16:29, Thorsten Z?rner wrote: > >> over at the Scribus list, I heard that there is a new stable >> version of Scribus out, namely 1.3.3.10. >> >> How and when will I be able to get it on my MacPorts? >> What is the procedure like? > > You should file an update request ticket in our issue tracker, if > one does not already exist. Even better would be if you would update > the portfile yourself, test it, make sure it works, then attach your > patch to the ticket. > > Usually the port maintainer would notice that a new version is > available and test and update the port. However, the scribus port > has no maintainer. If you are interested in being its maintainer, > let us know. > Ryan, okay, found the Portfile to change, found the place to change the version number... How do I find the correct checksums: md, sha1, rmd160 of the new version? Cheers, Thorsten. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2429 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080109/bb5de513/smime.bin From mail at thorstenzoerner.de Tue Jan 8 15:24:25 2008 From: mail at thorstenzoerner.de (=?ISO-8859-1?Q?Thorsten_Z=F6rner?=) Date: Tue Jan 8 15:24:29 2008 Subject: New Scribus version out In-Reply-To: References: <54A4130C-7984-470E-8FB5-5BFB418E92D2@thorstenzoerner.de> Message-ID: <7F448EBE-1863-4443-95C0-379EA8951255@thorstenzoerner.de> On 09.01.08, at 00:20, Thorsten Z?rner wrote: > > On 08.01.08, at 23:42, Ryan Schmidt wrote: > >> On Jan 8, 2008, at 16:29, Thorsten Z?rner wrote: >> >>> over at the Scribus list, I heard that there is a new stable >>> version of Scribus out, namely 1.3.3.10. >>> >>> How and when will I be able to get it on my MacPorts? >>> What is the procedure like? >> >> You should file an update request ticket in our issue tracker, if >> one does not already exist. Even better would be if you would >> update the portfile yourself, test it, make sure it works, then >> attach your patch to the ticket. >> >> Usually the port maintainer would notice that a new version is >> available and test and update the port. However, the scribus port >> has no maintainer. If you are interested in being its maintainer, >> let us know. >> > > Ryan, > > okay, found the Portfile to change, found the place to change the > version number... > How do I find the correct checksums: md, sha1, rmd160 of the new > version? > > Cheers, > Thorsten. Okay, no worries, I've found it. Something along this line: %% md5 rrdtool-1.2.23.tar.gz %% openssl sha1 rrdtool-1.2.23.tar.gz %% openssl rmd160 rrdtool-1.2.23.tar.gz Thorsten. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2429 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080109/fb7f0fef/smime.bin From ryandesign at macports.org Tue Jan 8 15:27:46 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 8 15:28:22 2008 Subject: New Scribus version out In-Reply-To: <7F448EBE-1863-4443-95C0-379EA8951255@thorstenzoerner.de> References: <54A4130C-7984-470E-8FB5-5BFB418E92D2@thorstenzoerner.de> <7F448EBE-1863-4443-95C0-379EA8951255@thorstenzoerner.de> Message-ID: On Jan 8, 2008, at 17:24, Thorsten Z?rner wrote: > On 09.01.08, at 00:20, Thorsten Z?rner wrote: > >> On 08.01.08, at 23:42, Ryan Schmidt wrote: >> >>> On Jan 8, 2008, at 16:29, Thorsten Z?rner wrote: >>> >>>> over at the Scribus list, I heard that there is a new stable >>>> version of Scribus out, namely 1.3.3.10. >>>> >>>> How and when will I be able to get it on my MacPorts? >>>> What is the procedure like? >>> >>> You should file an update request ticket in our issue tracker, if >>> one does not already exist. Even better would be if you would >>> update the portfile yourself, test it, make sure it works, then >>> attach your patch to the ticket. >>> >>> Usually the port maintainer would notice that a new version is >>> available and test and update the port. However, the scribus port >>> has no maintainer. If you are interested in being its maintainer, >>> let us know. >> >> okay, found the Portfile to change, found the place to change the >> version number... >> How do I find the correct checksums: md, sha1, rmd160 of the new >> version? > > Okay, no worries, I've found it. Something along this line: > %% md5 rrdtool-1.2.23.tar.gz > %% openssl sha1 rrdtool-1.2.23.tar.gz > %% openssl rmd160 rrdtool-1.2.23.tar.gz Yes, except presumably you mean to use a scribus distfile, not an rrdtool distfile. This should all be addressed in the guide, by the way. For example, checksums are section 4.2.12: http://guide.macports.org/#development.creating-portfile If you have any suggestions about things which are missing or unclear in the guide, please bring them up. The guide is still new and a work in progress. From mail at thorstenzoerner.de Tue Jan 8 16:36:04 2008 From: mail at thorstenzoerner.de (=?ISO-8859-1?Q?Thorsten_Z=F6rner?=) Date: Tue Jan 8 16:36:07 2008 Subject: New Scribus version out In-Reply-To: References: <54A4130C-7984-470E-8FB5-5BFB418E92D2@thorstenzoerner.de> <7F448EBE-1863-4443-95C0-379EA8951255@thorstenzoerner.de> Message-ID: On 09.01.08, at 00:27, Ryan Schmidt wrote: > On Jan 8, 2008, at 17:24, Thorsten Z?rner wrote: > >> On 09.01.08, at 00:20, Thorsten Z?rner wrote: >> >>> On 08.01.08, at 23:42, Ryan Schmidt wrote: >>> >>>> On Jan 8, 2008, at 16:29, Thorsten Z?rner wrote: >>>> >>>>> over at the Scribus list, I heard that there is a new stable >>>>> version of Scribus out, namely 1.3.3.10. >>>>> >>>>> How and when will I be able to get it on my MacPorts? >>>>> What is the procedure like? >>>> >>>> You should file an update request ticket in our issue tracker, if >>>> one does not already exist. Even better would be if you would >>>> update the portfile yourself, test it, make sure it works, then >>>> attach your patch to the ticket. >>>> >>>> Usually the port maintainer would notice that a new version is >>>> available and test and update the port. However, the scribus port >>>> has no maintainer. If you are interested in being its maintainer, >>>> let us know. >>> >>> okay, found the Portfile to change, found the place to change the >>> version number... >>> How do I find the correct checksums: md, sha1, rmd160 of the new >>> version? >> >> Okay, no worries, I've found it. Something along this line: >> %% md5 rrdtool-1.2.23.tar.gz >> %% openssl sha1 rrdtool-1.2.23.tar.gz >> %% openssl rmd160 rrdtool-1.2.23.tar.gz > > Yes, except presumably you mean to use a scribus distfile, not an > rrdtool distfile. > > This should all be addressed in the guide, by the way. For example, > checksums are section 4.2.12: > > http://guide.macports.org/#development.creating-portfile > > If you have any suggestions about things which are missing or > unclear in the guide, please bring them up. The guide is still new > and a work in progress. Ryan, mission accomplished. Scribus 1.3.3.10 downloads, compiles and runs all right. Filed a TRAC ticket right here http://trac.macosforge.org/projects/macports/ticket/13880 The guide helped me a big deal. I only took a long time to search WHERE my portfiles live - that could be explained a little better. Ah, and there is even a description of how to file a TRAC ticket... So I conclude, there seems to be almost everything in the guide already, but I find it still tricky to find. Maybe a "situational" ordering would be preferable over an "organizational" ordering... If I can help anyone with it, I volunteer to be the maintainer for Scribus. Good night, Thorsten. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2429 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080109/0c21f215/smime.bin From james.sumners at gmail.com Tue Jan 8 16:50:20 2008 From: james.sumners at gmail.com (James Sumners) Date: Tue Jan 8 16:50:20 2008 Subject: [macports] Ticket #12962 Message-ID: Would someone with some authority take a look at this ticket. I don't think the maintainer is much caring about it. I've added a portfile patch to the ticket. http://trac.macosforge.org/projects/macports/ticket/12962 -- James Sumners http://james.roomfullofmirrors.com/ "All governments suffer a recurring problem: Power attracts pathological personalities. It is not that power corrupts but that it is magnetic to the corruptible. Such people have a tendency to become drunk on violence, a condition to which they are quickly addicted." Missionaria Protectiva, Text QIV (decto) CH:D 59 From ryandesign at macports.org Tue Jan 8 17:07:15 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 8 17:07:53 2008 Subject: New Scribus version out In-Reply-To: References: <54A4130C-7984-470E-8FB5-5BFB418E92D2@thorstenzoerner.de> <7F448EBE-1863-4443-95C0-379EA8951255@thorstenzoerner.de> Message-ID: On Jan 8, 2008, at 18:36, Thorsten Z?rner wrote: > Scribus 1.3.3.10 downloads, compiles and runs all right. > Filed a TRAC ticket right here http://trac.macosforge.org/projects/ > macports/ticket/13880 I committed your patch. Thanks! > The guide helped me a big deal. > I only took a long time to search WHERE my portfiles live - that > could be explained a little better. > > Ah, and there is even a description of how to file a TRAC ticket... > So I conclude, there seems to be almost everything in the guide > already, > but I find it still tricky to find. Maybe a "situational" ordering > would be preferable > over an "organizational" ordering... We have a couple people who have been working on the guide; maybe one of them can respond to this. > If I can help anyone with it, I volunteer to be the maintainer for > Scribus. Should I make you the maintainer of scribus? Let me know and I will. If you like we can make it an open-maintainer port, so that you're listed as the maintainer, but anyone else can feel free to make changes too. From dlb at davidlballenger.com Tue Jan 8 17:53:25 2008 From: dlb at davidlballenger.com (David L Ballenger) Date: Tue Jan 8 17:53:28 2008 Subject: Safari can't verify identity of the website "www.macosforge.com" Message-ID: When logging into MacPorts and being redirected to www.macosforge.com I get the error in the subject line. It says the certificate was signed by an unknown certifying authority. According to the certificate details it was issued by opensource.apple.com. I'm running Safari on a MacBook Pro running Mac OS X 10.5.1. I would hope that this system would have the latest set of authority certificates. Is this a problem on my system? Is opensource.apple.com not the correct certifying authority or should I just tell Safari to accept certificates issued by opensource.apple.com? Thanks -David From rowue at digitalis.org Tue Jan 8 17:55:01 2008 From: rowue at digitalis.org (=?ISO-8859-1?Q?Rolf_W=FCrdemann?=) Date: Tue Jan 8 17:54:51 2008 Subject: Ticket #13826 Message-ID: <4A72948E-3FB6-4CA7-A66C-FEE75C7C3AB0@digitalis.org> Hi ... as mentioned a few days ago I've updated the Portfile for qucs to 0.0.13 a few days ago. (And checked for compilation) 2day I've changed the Portfile to be relative to the svn Version and put also an diff to svn on the ticket ... I would be glad if someone can commit the changes, 'cause I can't do that ... reg's Rolf -- Security is an illusion - Datasecurity twice Rolf W?rdemann - private: rowue@digitalis.org - office: rowue@crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue@digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Signierter Teil der Nachricht Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080109/aee37daf/PGP.bin From raimue at macports.org Tue Jan 8 18:01:48 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Tue Jan 8 18:02:05 2008 Subject: [macports] Ticket #12962 In-Reply-To: References: Message-ID: <47842B0C.6040403@macports.org> James Sumners wrote: > Would someone with some authority take a look at this ticket. I don't > think the maintainer is much caring about it. I've added a portfile > patch to the ticket. Paul Guyot (pguyot@) did not respond to any ticket requests for a while. See also http://trac.macosforge.org/projects/macports/ticket/13295 I don't know what we can/should do about that. I'm cc'ing him - just in case... Rainer From rowue at digitalis.org Tue Jan 8 18:02:34 2008 From: rowue at digitalis.org (=?ISO-8859-1?Q?Rolf_W=FCrdemann?=) Date: Tue Jan 8 18:02:29 2008 Subject: Ticket #13624 Message-ID: <3A0659DC-E009-4292-97D0-8D381965D482@digitalis.org> Hi ... also some changes done two weeks ago to get gtkglext running on leopard ... (also tested with gwyddion) Added diff to svn today ... Can someone commit? (Will also close #13517) Reg's Rolf -- Security is an illusion - Datasecurity twice Rolf W?rdemann - private: rowue@digitalis.org - office: rowue@crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue@digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Signierter Teil der Nachricht Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080109/06123740/PGP.bin From wsiegrist at apple.com Tue Jan 8 20:50:07 2008 From: wsiegrist at apple.com (William Siegrist) Date: Tue Jan 8 20:50:38 2008 Subject: Safari can't verify identity of the website "www.macosforge.com" In-Reply-To: References: Message-ID: <634B62B1-9672-43D2-9340-ED13CC1AA3CC@apple.com> Its not you, its our certificates. We're working on acquiring new ones currently. -Bill On Jan 8, 2008, at 5:53 PM, David L Ballenger wrote: > When logging into MacPorts and being redirected to > www.macosforge.com I get the error in the subject line. It says the > certificate was signed by an unknown certifying authority. > According to the certificate details it was issued by > opensource.apple.com. > > I'm running Safari on a MacBook Pro running Mac OS X 10.5.1. I would > hope that this system would have the latest set of authority > certificates. > > Is this a problem on my system? Is opensource.apple.com not the > correct certifying authority or should I just tell Safari to accept > certificates issued by opensource.apple.com? > > Thanks -David > > > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users ---- William Siegrist Software Support Engineer Mac OS Forge http://macosforge.org/ wsiegrist@apple.com 408 862 7337 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2421 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080108/b3efb82e/smime.bin From stefan.schwarzer at grid.unep.ch Tue Jan 8 21:43:23 2008 From: stefan.schwarzer at grid.unep.ch (Stefan Schwarzer) Date: Tue Jan 8 21:43:23 2008 Subject: "The following install step failed: run postflight script for MacPorts-1.6.0." In-Reply-To: <8D63E40A-5563-488C-9E4A-302098EC13A9@macports.org> References: <8D63E40A-5563-488C-9E4A-302098EC13A9@macports.org> Message-ID: >> I wanted to install MacPorts on my Mac - MacPro with Leopard, >> latest version. But, while using the disk image, the installation >> finished with this message: "The following install step failed: run >> postflight script for MacPorts-1.6.0." >> >> Can anyone let me know what I should do? > > I'm not sure... > > Were you using the correct disk image? the one whose name is > MacPorts-1.6.0-10.5-Leopard.dmg? > > If so, can you just try installing it again, see if it works now? Yep, was the right disk image. Downloaded it again and installed it. But same message.... From george at galis.org Tue Jan 8 22:12:39 2008 From: george at galis.org (George Georgalis) Date: Tue Jan 8 22:12:39 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: References: <20080106233000.GC3137@run.duo> <20080107144937.GD3137@run.duo> <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> <20080108021026.GB29114@run.duo> <4043C306-98FB-4F49-B6F7-6AECA57606C0@macports.org> <20080108043025.GD29114@run.duo> <451EBF42-377F-4ACB-80F8-9D9368945BB9@macports.org> <20080108170558.GH29114@run.duo> Message-ID: <20080109061239.GA14541@run.duo> Well I get the same missing expat problem, with Xcode 2.5 I'm tempted to make a symlink to /usr/local/MacPorts from /opt/local but I'd really like to get this figured out vs just make it work. below are notes on my Xcode update. What else can I try? // George On Tue, Jan 08, 2008 at 03:03:24PM -0600, Ryan Schmidt wrote: > On Jan 8, 2008, at 11:05, George Georgalis wrote: >> On Mon, Jan 07, 2008 at 11:44:59PM -0600, Ryan Schmidt wrote: >>> >>> http://developer.apple.com/tools/download/ >> >> Okay, downloading, will try tonight. To reduce consumed disk space >> after it's all in place, should I think about purging /Developer >> before I start the install? is that even necessary? Is there >> something else that is better to do? > > I assume that installing Xcode 2.5 will be smart about removing obsolete > parts of Xcode 2.3 first. If you're concerned that it won't be, you could > first run the Xcode 2.3 uninstall script. (Xcode installs things in more > places than just /Developer.) The uninstall script is probably on the Xcode > 2.3 CD or disk image. here's some summary notes I don't have the dmg from my current Xcode install. Version 2.5 says this in the About pdf... Uninstalling Xcode 2.5 developer tools Since multiple versions of the Xcode developer tools can coexist on your system on Mac OS X 10.5, the uninstall-devtools.pl script has been changed to only remove content installed into the Xcode directory. On Mac OS X 10.4.x, the uninstall-devtools script continues to remove all Xcode 2.5 developer tools content from the boot volume. On Mac OS X 10.4.x, type the following in Terminal to remove the Xcode 2.5 developer tools: $ sudo /Developer/Library/uninstall-devtools On Mac OS X 10.5, type the following in Terminal to remove the Xcode 2.5 developer tools: $ sudo /Library/uninstall-devtools NOTE: The uninstaller that ships with previous versions of Xcode developer tools will not clean everything off of your system properly. You should either use the one on the Xcode 2.5 DVD, or you should use the one installed when you installed the Xcode 2.5 developer tools. NOTE: Running the uninstall script will uninstall any previous installations of Mac OS X Developer Tools or Xcode developer tools releases on Tiger systems. On Leopard systems, the uninstaller will only remove the Xcode developer tools installed on the boot volume outside of the Xcode directory. To remove the remaining Xcode content, drag the Xcode directory to the trash. I used that to discover: geo@fuji:/Users/geo find /Developer/ -iname \*uninstall\* /Developer//ADC Reference Library/documentation/QuickTime/APIREF/qtuninstallnexttaskneededsoonercallback.htm /Developer//Tools/uninstall-devtools.pl and ran it after the df command... geo@fuji:/Users/geo df -h Filesystem Size Used Avail Capacity Mounted on /dev/disk0s3 74G 73G 938M 99% / it freed up a lot of space, /dev/disk0s3 74G 71G 3.6G 95% / and the 2.5 install used a bit more: /dev/disk0s3 74G 74G 626M 99% / -- George Georgalis, information system scientist < From jmpp at macports.org Tue Jan 8 22:16:08 2008 From: jmpp at macports.org (Juan Manuel Palacios) Date: Tue Jan 8 22:14:14 2008 Subject: "The following install step failed: run postflight script for MacPorts-1.6.0." In-Reply-To: References: <8D63E40A-5563-488C-9E4A-302098EC13A9@macports.org> Message-ID: <3D4AEF5E-9EBB-4571-B78D-FC28A18E7846@macports.org> On Jan 9, 2008, at 1:13 AM, Stefan Schwarzer wrote: >>> I wanted to install MacPorts on my Mac - MacPro with Leopard, >>> latest version. But, while using the disk image, the installation >>> finished with this message: "The following install step failed: >>> run postflight script for MacPorts-1.6.0." >>> >>> Can anyone let me know what I should do? >> >> I'm not sure... >> >> Were you using the correct disk image? the one whose name is >> MacPorts-1.6.0-10.5-Leopard.dmg? >> >> If so, can you just try installing it again, see if it works now? > > Yep, was the right disk image. Downloaded it again and installed it. > But same message.... I wrote the postflight script so I should chime in. Can you please try grepping through /var/log/install* files to see if there are any relevant messages there about the failure? On a similar note, are you experiencing any problems with your MacPorts usage? Was your terminal environment set up correctly by the installer? Regards,.... -jmpp From stefan.schwarzer at grid.unep.ch Tue Jan 8 22:30:21 2008 From: stefan.schwarzer at grid.unep.ch (Stefan Schwarzer) Date: Tue Jan 8 22:30:20 2008 Subject: "The following install step failed: run postflight script for MacPorts-1.6.0." In-Reply-To: <3D4AEF5E-9EBB-4571-B78D-FC28A18E7846@macports.org> References: <8D63E40A-5563-488C-9E4A-302098EC13A9@macports.org> <3D4AEF5E-9EBB-4571-B78D-FC28A18E7846@macports.org> Message-ID: >>>> I wanted to install MacPorts on my Mac - MacPro with Leopard, >>>> latest version. But, while using the disk image, the installation >>>> finished with this message: "The following install step failed: >>>> run postflight script for MacPorts-1.6.0." >>>> >>>> Can anyone let me know what I should do? >>> >>> I'm not sure... >>> >>> Were you using the correct disk image? the one whose name is >>> MacPorts-1.6.0-10.5-Leopard.dmg? >>> >>> If so, can you just try installing it again, see if it works now? >> >> Yep, was the right disk image. Downloaded it again and installed >> it. But same message.... > > > I wrote the postflight script so I should chime in. Can you please > try grepping through /var/log/install* files to see if there are any > relevant messages there about the failure? > > On a similar note, are you experiencing any problems with your > MacPorts usage? Was your terminal environment set up correctly by > the installer? Here are the info. Can it be that it can't connect to MacPorts (for an update or so) which causes the problem? I am behind a firewill - will have to ask the admin to open port 873 - if that's correct Jan 9 07:25:23 gridmac7 Installer[18967]: Localized installer script postflight found in the MacPorts-1.6.0 package. Using compatibility mode. Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Unknown shell! Please set your MacPorts compatible environment manually. Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:23: --- last message repeated 1 time --- Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Checking the shell environment for user "schwarzer"... Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:23: --- last message repeated 1 time --- Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: /Users/ schwarzer/Downloads/8.1.08/MacPorts-1.6.0.pkg/Contents/Resources/ English.lproj/postflight: line 71: /Users/schwarzer/.: Is a directory Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: /Users/ schwarzer/Downloads/8.1.08/MacPorts-1.6.0.pkg/Contents/Resources/ English.lproj/postflight: line 96: /Users/schwarzer/.: Is a directory Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Your shell already has the right MANPATH environment variable for use with MacPorts! Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Your shell already has the right DISPLAY environment variable for use with MacPorts! Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:24: --- last message repeated 1 time --- Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Synchronizing the MacPorts installation with the project's rsync server... Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:24: --- last message repeated 1 time --- Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Synchronizing local ports tree from rsync://rsync.macports.org/release/ ports/ Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: rsync: failed to connect to rsync.macports.org: Connection refused (61) Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-30/ rsync/clientserver.c(94) Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Error: /opt/ local/bin/port: port selfupdate failed: Couldn't sync the ports tree: Synchronization the local ports tree failed doing rsync Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: An attempt to synchronize your recent MacPorts installation with the project's rsync server failed! Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Please run 'port -d selfupdate' manually to find out the cause of the error. Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Jan 9 07:25:24 gridmac7 Installer[18967]: Install failed: The following install step failed: run postflight script for MacPorts-1.6.0. Contact the software manufacturer for assistance. From rsync at reifferscheid.org Wed Jan 9 08:43:49 2008 From: rsync at reifferscheid.org (Thomas Reifferscheid) Date: Wed Jan 9 08:47:15 2008 Subject: [MacPorts] #13847: pidgin 2.3.1 does not start (old gtk-x11 version) In-Reply-To: <4784F361.5070509@hotmail.com> References: <4784F361.5070509@hotmail.com> Message-ID: <4784F9C5.8040609@reifferscheid.org> Dear Victor, please keep mailing to the macports-users mailinglist. I need more information here. Please do: sudo port -d selfupdate sudo port -d uninstall pidgin sudo port -d install pidgin and show us the relevant lines from the pidgin configure process. Kind regards Thomas Victor Escobar wrote: > Original error: >> dyld: Library not loaded: /opt/local/lib/libgtk-x11-2.0.0.dylib >> Referenced from: /opt/local/bin/pidgin Reason: Incompatible library >> version: pidgin requires version 1201.0.0 or later, but >> libgtk-x11-2.0.0.dylib provides version 1001.0.0 Trace/BPT trap > Thomas, > Thank you for your comment. Do you have any pointers on where I should continue my investigation, since you've shown that it's not a problem with the Pidgin port /per se/? It's very interesting to note that on my box *libgtk-x11-2.0.0.dylib* is symlinked to *libgtk-x11-2.0.0.1200.2.dylib*, even though it's somehow being reported to Pidgin as 1001.0.0 -- any idea how this could be? Again, any help or advice you can offer is most appreciated. :-) > > $ ls -l /opt/local/lib/libgtk*.dylib > -rwxr-xr-x 2 root admin 4618156 Dec 28 06:15 */opt/local/lib/libgtk-x11-2.0.0.1200.2.dylib* > lrwxr-xr-x 1 root admin 29 Dec 28 06:15 */opt/local/lib/libgtk-x11-2.0.0.dylib -> libgtk-x11-2.0.0.1200.2.dylib* > lrwxr-xr-x 1 root admin 29 Dec 28 06:15 */opt/local/lib/libgtk-x11-2.0.dylib -> libgtk-x11-2.0.0.1200.2.dylib* > > From someguyonearth at gmail.com Wed Jan 9 08:48:55 2008 From: someguyonearth at gmail.com (Some Guy) Date: Wed Jan 9 08:48:52 2008 Subject: problem using port to install gnucash on mac 10.5 In-Reply-To: References: <020F2477-AFAC-4DF1-BD92-98E7E25AA18A@esztermann.de> <216A8AE3-8EA8-47A4-89EF-28B4AEC0EAAB@esztermann.de> <9153cb050801061234r59de548cn51f60251ec67a024@mail.gmail.com> Message-ID: <9153cb050801090848u4bb34ba6gf32b9f3ed0dab903@mail.gmail.com> It looks like the port file for gnucash needs a look at. I'm a novice at all this so would not have a clue where to start :( I have been told that you can do some kind of linking to make it work but the resulting program is not that stable which, for record keeping is not the best solution. On Jan 6, 2008 8:42 PM, Ansgar Esztermann wrote: > > On Jan 6, 2008, at 21:34 , Some Guy wrote: > > > mmm, it says it needs guile 1.6 or later > > > > Used port to install guile and it spins out > ... > > Error: Status 1 encountered during processing. > > > So it does. By the way, the dependency is on guile16, not guile. That > port does install fine, but at configure time, gnucash fails to find > the necessary files, so it still does not work. > > A. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080109/267f727c/attachment.html From wsiegrist at apple.com Wed Jan 9 09:05:02 2008 From: wsiegrist at apple.com (William Siegrist) Date: Wed Jan 9 09:06:09 2008 Subject: "The following install step failed: run postflight script for MacPorts-1.6.0." In-Reply-To: References: <8D63E40A-5563-488C-9E4A-302098EC13A9@macports.org> <3D4AEF5E-9EBB-4571-B78D-FC28A18E7846@macports.org> Message-ID: The rsync server looks okay, so is it possible that you are behind a firewall or proxy that is blocking 873/tcp? Can you connect using just telnet? bash# telnet rsync.macports.org 873 Trying 17.254.17.246... Connected to alpha.macosforge.org. Escape character is '^]'. @RSYNCD: 28 -Bill On Jan 8, 2008, at 10:30 PM, Stefan Schwarzer wrote: >>>>> I wanted to install MacPorts on my Mac - MacPro with Leopard, >>>>> latest version. But, while using the disk image, the >>>>> installation finished with this message: "The following install >>>>> step failed: run postflight script for MacPorts-1.6.0." >>>>> >>>>> Can anyone let me know what I should do? >>>> >>>> I'm not sure... >>>> >>>> Were you using the correct disk image? the one whose name is >>>> MacPorts-1.6.0-10.5-Leopard.dmg? >>>> >>>> If so, can you just try installing it again, see if it works now? >>> >>> Yep, was the right disk image. Downloaded it again and installed >>> it. But same message.... >> >> >> I wrote the postflight script so I should chime in. Can you please >> try grepping through /var/log/install* files to see if there are >> any relevant messages there about the failure? >> >> On a similar note, are you experiencing any problems with your >> MacPorts usage? Was your terminal environment set up correctly by >> the installer? > > Here are the info. Can it be that it can't connect to MacPorts (for > an update or so) which causes the problem? I am behind a firewill - > will have to ask the admin to open port 873 - if that's correct > > Jan 9 07:25:23 gridmac7 Installer[18967]: Localized installer > script postflight found in the MacPorts-1.6.0 package. Using > compatibility mode. > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Unknown > shell! Please set your MacPorts compatible environment manually. > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:23: --- last message repeated 1 time --- > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Checking > the shell environment for user "schwarzer"... > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:23: --- last message repeated 1 time --- > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: /Users/ > schwarzer/Downloads/8.1.08/MacPorts-1.6.0.pkg/Contents/Resources/ > English.lproj/postflight: line 71: /Users/schwarzer/.: Is a directory > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: /Users/ > schwarzer/Downloads/8.1.08/MacPorts-1.6.0.pkg/Contents/Resources/ > English.lproj/postflight: line 96: /Users/schwarzer/.: Is a directory > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Your > shell already has the right MANPATH environment variable for use > with MacPorts! > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Your > shell already has the right DISPLAY environment variable for use > with MacPorts! > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24: --- last message repeated 1 time --- > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Synchronizing the MacPorts installation with the project's rsync > server... > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24: --- last message repeated 1 time --- > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Synchronizing local ports tree from rsync://rsync.macports.org/ > release/ports/ > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: rsync: > failed to connect to rsync.macports.org: Connection refused (61) > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: rsync > error: error in socket IO (code 10) at /SourceCache/rsync/rsync-30/ > rsync/clientserver.c(94) > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Error: / > opt/local/bin/port: port selfupdate failed: Couldn't sync the ports > tree: Synchronization the local ports tree failed doing rsync > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: An > attempt to synchronize your recent MacPorts installation with the > project's rsync server failed! > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Please > run 'port -d selfupdate' manually to find out the cause of the error. > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 Installer[18967]: Install failed: The > following install step failed: run postflight script for > MacPorts-1.6.0. Contact the software manufacturer for assistance. > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users ---- William Siegrist Software Support Engineer Mac OS Forge http://macosforge.org/ wsiegrist@apple.com 408 862 7337 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2421 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080109/1d60cb03/smime-0001.bin From ryandesign at macports.org Wed Jan 9 12:50:18 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 9 12:57:34 2008 Subject: "The following install step failed: run postflight script for MacPorts-1.6.0." In-Reply-To: References: <8D63E40A-5563-488C-9E4A-302098EC13A9@macports.org> <3D4AEF5E-9EBB-4571-B78D-FC28A18E7846@macports.org> Message-ID: On Jan 8, 2008, at 10:30 PM, Stefan Schwarzer wrote: >>> I wanted to install MacPorts on my Mac - MacPro with Leopard, >>> latest version. But, while using the disk image, the installation >>> finished with this message: "The following install step failed: >>> run postflight script for MacPorts-1.6.0." [snip] >> I wrote the postflight script so I should chime in. Can you please >> try grepping through /var/log/install* files to see if there are >> any relevant messages there about the failure? [snip] > Here are the info. Can it be that it can't connect to MacPorts (for > an update or so) which causes the problem? I am behind a firewill - > will have to ask the admin to open port 873 - if that's correct [snip] > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Synchronizing local ports tree from rsync://rsync.macports.org/ > release/ports/ > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: rsync: > failed to connect to rsync.macports.org: Connection refused (61) > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: rsync > error: error in socket IO (code 10) at /SourceCache/rsync/rsync-30/ > rsync/clientserver.c(94) > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Error: / > opt/local/bin/port: port selfupdate failed: Couldn't sync the ports > tree: Synchronization the local ports tree failed doing rsync > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: An > attempt to synchronize your recent MacPorts installation with the > project's rsync server failed! > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Please > run 'port -d selfupdate' manually to find out the cause of the error. > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 Installer[18967]: Install failed: The > following install step failed: run postflight script for > MacPorts-1.6.0. Contact the software manufacturer for assistance. So the postflight script failed because it couldn't connect to the rsync server. Doesn't matter why it happened (whether our rsync server was down (which it wasn't) or whether the user's firewall prevented the connection); we should ensure that any inability to connect to the rsync server does not cause the postflight script to fail like that. Best thing would be if we could pop up a friendly message to the user that they need to update their installation themselves, but it might also be ok to just silently fail. In any event, the installation in the Installer should complete. From ryandesign at macports.org Wed Jan 9 12:57:19 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 9 12:57:54 2008 Subject: New Scribus version out In-Reply-To: <08C240ED-6D2C-4648-8DFA-52D318226A78@thorstenzoerner.de> References: <54A4130C-7984-470E-8FB5-5BFB418E92D2@thorstenzoerner.de> <7F448EBE-1863-4443-95C0-379EA8951255@thorstenzoerner.de> <08C240ED-6D2C-4648-8DFA-52D318226A78@thorstenzoerner.de> Message-ID: On Jan 9, 2008, at 08:05, Thorsten Z?rner wrote: > On 09.01.08, at 02:07, Ryan Schmidt wrote: > >> On Jan 8, 2008, at 18:36, Thorsten Z?rner wrote: >> >>> If I can help anyone with it, I volunteer to be the maintainer >>> for Scribus. >> >> Should I make you the maintainer of scribus? Let me know and I >> will. If you like we can make it an open-maintainer port, so that >> you're listed as the maintainer, but anyone else can feel free to >> make changes too. > > Okay, let's do it as you suggest: make me maintainer and keep it open. I did it: http://trac.macosforge.org/projects/macports/changeset/32620 > Anythings else than my e-mail that you need to know from me? Not a thing. :) If you want an update to be made to the port, just file a ticket in the issue tracker and attach your patch. You can add me to the Cc line in the ticket so that I'll see it right away and can commit it. From matrixm at gmail.com Wed Jan 9 13:49:55 2008 From: matrixm at gmail.com (Matrix Mole) Date: Wed Jan 9 13:49:56 2008 Subject: Mplayer and apple remote Message-ID: <47854183.5090203@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was looking at the variants for mplayer, and noticed one there for noappleremote and it's description says that this would disable apple remote support for the build. I was wondering if this referred to the apple remote control software, or the infrared apple remote control that is used with the newer systems. Anyone know which is it? Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHhUGDNtosHRPp48MRAg7TAJ9+6qTI/NSXyr6zEyiV1BO6EG98CgCeOrtb Iybpvjs2Pww7ByByUxcLN44= =h9jP -----END PGP SIGNATURE----- From matrixm at gmail.com Wed Jan 9 13:58:49 2008 From: matrixm at gmail.com (Matrix Mole) Date: Wed Jan 9 13:58:51 2008 Subject: 10.5 and $PATH variable Message-ID: <47854399.3020602@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just obtained a new mac mini today with Leopard installed on it. Since this is my first experience with 10.5, I'm still learning some things. One of the first things I did though was to install macports. After the installation, I noticed that the .profile file wasn't modified to include /opt/local/bin and /opt/local/sbin like my 10.4 version was. At least, I think I installed the 10.4 version from the dmg image. Anyway, after doing a little looking around on the file system and reading the startup files, I discovered two things. First, there is no default .bash_profile, .bashrc, or .profile in the users startup directory. No problem there, just left up as an experience for the user to perform if they need to customize their environment beyond the default. Secndly, I learned that Leopard has /etc/paths and /etc/manpaths files that are used during login to set the default paths and manpaths. By adding /opt/local/bin and /opt/local/sbin to /etc/paths and putting /opt/local/man into the man path, I can guarantee that these are added to the path for any user on the system. This is actually a pretty cool idea, and it prompted the reason for my email. Could it be possible to modify the port install scripts to add it's paths to those two files on 10.5? Those files don't exist nor are used on 10.4 as I already checked, so the 10.4 install scripts wouldn't need modified. Just wondering, and not even sure if this has already come up and been discussed to death. Since I just got Leopard, I hadn't been reading anything related to that version up till now. Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHhUOZNtosHRPp48MRAhl4AKCbUShG/I9dtArnIK8pLG1Knqfg8ACgomlM oVKJRUGvJ6SvYbc2VgMWZzQ= =24K3 -----END PGP SIGNATURE----- From ryandesign at macports.org Wed Jan 9 13:59:03 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 9 13:59:37 2008 Subject: Mplayer and apple remote In-Reply-To: <47854183.5090203@gmail.com> References: <47854183.5090203@gmail.com> Message-ID: <5F54F6B9-6AD1-411C-B7D3-89AA75F00B1A@macports.org> On Jan 9, 2008, at 15:49, Matrix Mole wrote: > I was looking at the variants for mplayer, and noticed one there for > noappleremote and it's description says that this would disable apple > remote support for the build. I was wondering if this referred to the > apple remote control software, or the infrared apple remote control > that > is used with the newer systems. Anyone know which is it? I presume it's the infrared Apple Remote device that comes with newer Macs. You could ask the maintainer of the MPlayer port or the developers of the MPlayer software if you want to know for sure. From pburleson at gmail.com Wed Jan 9 14:02:33 2008 From: pburleson at gmail.com (Patrick Burleson) Date: Wed Jan 9 14:02:29 2008 Subject: 10.5 and $PATH variable In-Reply-To: <47854399.3020602@gmail.com> References: <47854399.3020602@gmail.com> Message-ID: On Jan 9, 2008 3:58 PM, Matrix Mole wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I just obtained a new mac mini today with Leopard installed on it. Since > this is my first experience with 10.5, I'm still learning some things. > One of the first things I did though was to install macports. After the > installation, I noticed that the .profile file wasn't modified to > include /opt/local/bin and /opt/local/sbin like my 10.4 version was. Just to let you know, a few of us have noticed this. It's been reported here: http://trac.macosforge.org/projects/macports/ticket/13742 I haven't had time to try the requested operation, but for anyone who can, I think the feedback will help determine why MacPorts 1.6 is behaving this way on 10.5 installs. Patrick From ryandesign at macports.org Wed Jan 9 14:13:58 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 9 14:21:12 2008 Subject: 10.5 and $PATH variable In-Reply-To: <47854399.3020602@gmail.com> References: <47854399.3020602@gmail.com> Message-ID: <54602504-E290-4F85-81A4-EBECA8B62F90@macports.org> On Jan 9, 2008, at 15:58, Matrix Mole wrote: > I just obtained a new mac mini today with Leopard installed on it. > Since > this is my first experience with 10.5, I'm still learning some things. > One of the first things I did though was to install macports. After > the > installation, I noticed that the .profile file wasn't modified to > include /opt/local/bin and /opt/local/sbin like my 10.4 version > was. At > least, I think I installed the 10.4 version from the dmg image. > > Anyway, after doing a little looking around on the file system and > reading the startup files, I discovered two things. First, there is no > default .bash_profile, .bashrc, or .profile in the users startup > directory. No problem there, just left up as an experience for the > user > to perform if they need to customize their environment beyond the > default. Secndly, I learned that Leopard has /etc/paths and > /etc/manpaths files that are used during login to set the default > paths > and manpaths. By adding /opt/local/bin and /opt/local/sbin to /etc/ > paths > and putting /opt/local/man into the man path, I can guarantee that > these > are added to the path for any user on the system. > > This is actually a pretty cool idea, and it prompted the reason for my > email. Could it be possible to modify the port install scripts to add > it's paths to those two files on 10.5? Those files don't exist nor are > used on 10.4 as I already checked, so the 10.4 install scripts > wouldn't > need modified. > > Just wondering, and not even sure if this has already come up and been > discussed to death. Since I just got Leopard, I hadn't been reading > anything related to that version up till now. This has already come up and been discussed to death. :) See: http://lists.macosforge.org/pipermail/macports-dev/2007-November/ 003606.html Discussion continues in December: http://lists.macosforge.org/pipermail/macports-dev/2007-December/ 003706.html It was my understanding that the MacPorts path setup was redone for the 1.6.0 release. See the first change listed under the 1.6.0 release in the ChangeLog: http://trac.macosforge.org/projects/macports/browser/tags/ release_1_6_0/base/ChangeLog "Revamped the postflight script that is run by Installer.app with our pkg installer to gracefully handle the addition of PATH, MANPATH and DISPLAY environment variables separately, if needed. Read http:// guide.macports.org/#installing.binary.postflight.details for more information (jmpp in many commits directly on the release_1_6 branch)." But I don't know if it properly handles the absence of ~/.bash_profile, ~/.bashrc and ~/.profile. From jmpp at macports.org Wed Jan 9 14:49:59 2008 From: jmpp at macports.org (Juan Manuel Palacios) Date: Wed Jan 9 14:48:08 2008 Subject: 10.5 and $PATH variable In-Reply-To: <47854399.3020602@gmail.com> References: <47854399.3020602@gmail.com> Message-ID: <1585B1B0-53F3-4A50-A2A0-1525C451C9CF@macports.org> On Jan 9, 2008, at 5:28 PM, Matrix Mole wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I just obtained a new mac mini today with Leopard installed on it. > Since > this is my first experience with 10.5, I'm still learning some things. > One of the first things I did though was to install macports. After > the > installation, I noticed that the .profile file wasn't modified to > include /opt/local/bin and /opt/local/sbin like my 10.4 version was. > At > least, I think I installed the 10.4 version from the dmg image. > > Anyway, after doing a little looking around on the file system and > reading the startup files, I discovered two things. First, there is no > default .bash_profile, .bashrc, or .profile in the users startup > directory. No problem there, just left up as an experience for the > user > to perform if they need to customize their environment beyond the > default. Secndly, I learned that Leopard has /etc/paths and > /etc/manpaths files that are used during login to set the default > paths > and manpaths. By adding /opt/local/bin and /opt/local/sbin to /etc/ > paths > and putting /opt/local/man into the man path, I can guarantee that > these > are added to the path for any user on the system. > > This is actually a pretty cool idea, and it prompted the reason for my > email. Could it be possible to modify the port install scripts to add > it's paths to those two files on 10.5? Those files don't exist nor are > used on 10.4 as I already checked, so the 10.4 install scripts > wouldn't > need modified. > > Just wondering, and not even sure if this has already come up and been > discussed to death. Since I just got Leopard, I hadn't been reading > anything related to that version up till now. For the record, MacPorts developers are still somewhat figuring out the best possible way to tweak a user's environment to include MacPorts compatible settings. 1.6.0 sources and the pkg installers are pulled from the "release_1_6" subversion branch, and in it the adopted approach is the pkg's "postflight" script, which I authored, that gets run by Insaller.app when the pkgs are used. Unfortunately, this script has been exhibiting some bugs that I haven't been able to reproduce locally in order to fix them, even though I tested and debugged it thoroughly before putting it into production. I'm actively looking into these issues, rest assured. "trunk" sources (that is, unreleased code) approach the problem of a MacPorts compatible environment by making use of the Leopard specific / etc/paths.d and /etc/manpaths.d directories, as originally posted in this thread. But that, added to being a Leopard only solution (and thus leaving the still larger Tiger users pool out in the cold), also creates other problems for us, since it *appends* MacPorts settings to the environment (e.g., /opt/local/bin being at the end of $PATH) while it has been established that it is best if they are *prepended* (/opt/ local/bin being at the *start* of $PATH). So as you can see, there's still no silver bullet for this problem, so please bear with us. As for the workings of the "postflight" script in the 1.6.0 pkg installers, please read "details of the postflight script" at http://guide.macports.org/#installing.macports to become acquainted with the several reasons why the script might not tweak the environment, as there are several. In short, the script refusing to tweak a non-vanilla environment (or, obviously, refusing to touch already customized ~/.profile or ~/.tcshrc files) is not necessarily a bug. As for the bugs that do exist, there are seemingly two macro cases: 1) the environment tweaks work as expected but then the script fails to selfupdate the MacPorts installation due to rsync blocking on the user's side: this is a completely harmless failure and thankfully a very easy one to fix both by us and users experiencing it. The latter should simply ignore the error and figure out how to unblock rsync to then run "selfupdate" manually (or switch to other MacPorts updating means, but that's an entirely different discussion). Some reports in ticket #13742 have mixed this case in. Please ignore them. 2) the user's environment is a vanilla one, but for some still undetected reason the script fails to tweak it to make it MacPorts compatible. This is obviously an important bug and what I'm focusing my energies on fixing, what ticket #13742 should be about. Any help in getting this fixed will be greatly appreciated. I'll analyze the feedback already received and will try to post new questions/instructions in order to find the bugs and squash them. Thank you all for your help! Regards,... -jmpp PS: There's also the "The following install step failed: run postflight script for MacPorts-1.6.0." thread on this very list, discussing the same problems. I'll try to keep discussion concentrated there and will from now on reply only to that one. From matrixm at gmail.com Wed Jan 9 14:52:33 2008 From: matrixm at gmail.com (Matrix Mole) Date: Wed Jan 9 14:52:32 2008 Subject: 10.5 and $PATH variable In-Reply-To: <54602504-E290-4F85-81A4-EBECA8B62F90@macports.org> References: <47854399.3020602@gmail.com> <54602504-E290-4F85-81A4-EBECA8B62F90@macports.org> Message-ID: <47855031.4000002@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ryan Schmidt wrote: | This has already come up and been discussed to death. :) See: | | It was my understanding that the MacPorts path setup was redone for the | 1.6.0 release. See the first change listed under the 1.6.0 release in | the ChangeLog: | | http://trac.macosforge.org/projects/macports/browser/tags/release_1_6_0/base/ChangeLog Per Patrick, there is already a ticket open regarding this that is still ongoing at http://trac.macosforge.org/projects/macports/ticket/13742 I'll report there what I've discovered, and see if my information can be of any help. Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHhVAwNtosHRPp48MRApg2AJ46QjAwmHJzzUI/59MhZFQikuDOSQCggiMI /msjWjN6bW3s0g0eXDirWAQ= =2WhO -----END PGP SIGNATURE----- From ryandesign at macports.org Wed Jan 9 15:07:12 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 9 15:07:48 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <20080109061239.GA14541@run.duo> References: <20080106233000.GC3137@run.duo> <20080107144937.GD3137@run.duo> <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> <20080108021026.GB29114@run.duo> <4043C306-98FB-4F49-B6F7-6AECA57606C0@macports.org> <20080108043025.GD29114@run.duo> <451EBF42-377F-4ACB-80F8-9D9368945BB9@macports.org> <20080108170558.GH29114@run.duo> <20080109061239.GA14541@run.duo> Message-ID: <39221154-7E02-4B07-B502-70C541431AB2@macports.org> On Jan 9, 2008, at 00:12, George Georgalis wrote: > Well I get the same missing expat problem, with Xcode 2.5 I'm > tempted to make a symlink to /usr/local/MacPorts from /opt/local > but I'd really like to get this figured out vs just make it work. I don't know why it happens yet, but I have been able to reproduce your problem so I filed a ticket. http://trac.macosforge.org/projects/macports/ticket/13885 From matrixm at gmail.com Wed Jan 9 15:07:49 2008 From: matrixm at gmail.com (Matrix Mole) Date: Wed Jan 9 15:07:52 2008 Subject: Mplayer and apple remote In-Reply-To: <5F54F6B9-6AD1-411C-B7D3-89AA75F00B1A@macports.org> References: <47854183.5090203@gmail.com> <5F54F6B9-6AD1-411C-B7D3-89AA75F00B1A@macports.org> Message-ID: <478553C5.3080804@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ryan Schmidt wrote: | On Jan 9, 2008, at 15:49, Matrix Mole wrote: | | I presume it's the infrared Apple Remote device that comes with newer | Macs. You could ask the maintainer of the MPlayer port or the developers | of the MPlayer software if you want to know for sure. | I see in the Portfile for MPlayer that the maintainer is listed as: maintainers ecronin \ ~ openmaintainer Unfortunately, on the Developers page at macports, the link to ecronin appears to generate a 404 error. Does anyone know how to get ahold of him, or have his email handy to forward my question on to? If I can't get a hold of the maintainer, then I'll have no recourse but to subscribe to the mplayer mail lists to ask my question there (although it seems kind of silly to go through the entire subscription process only to ask a single question and then leave). Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHhVPFNtosHRPp48MRAm9CAJ9LX4LW8KWM/q0q01mgcQoe6xT3HwCgnQlp ogKW2gzuSkuRdfom+3Rg3Wg= =+KHY -----END PGP SIGNATURE----- From ryandesign at macports.org Wed Jan 9 15:10:08 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 9 15:10:43 2008 Subject: Mplayer and apple remote In-Reply-To: <478553C5.3080804@gmail.com> References: <47854183.5090203@gmail.com> <5F54F6B9-6AD1-411C-B7D3-89AA75F00B1A@macports.org> <478553C5.3080804@gmail.com> Message-ID: <82073F0E-6E53-469A-BC85-4CAE74EF504F@macports.org> On Jan 9, 2008, at 17:07, Matrix Mole wrote: > Ryan Schmidt wrote: > >> I presume it's the infrared Apple Remote device that comes with newer >> Macs. You could ask the maintainer of the MPlayer port or the >> developers >> of the MPlayer software if you want to know for sure. > > > I see in the Portfile for MPlayer that the maintainer is listed as: > > maintainers ecronin \ > ~ openmaintainer > > Unfortunately, on the Developers page at macports, the link to ecronin > appears to generate a 404 error. Does anyone know how to get ahold of > him, or have his email handy to forward my question on to? No need to look in the Portfile itself. Just type "port info MPlayer". That will print out the maintainer's complete email address, which in this case ends with macports.org > If I can't get a hold of the maintainer, then I'll have no recourse > but > to subscribe to the mplayer mail lists to ask my question there > (although it seems kind of silly to go through the entire subscription > process only to ask a single question and then leave). Sadly, that's how many mailing lists work. :) And it's how they have to work, to reduce spam. From matrixm at gmail.com Wed Jan 9 15:19:28 2008 From: matrixm at gmail.com (Matrix Mole) Date: Wed Jan 9 15:19:27 2008 Subject: port info (was Re: Mplayer and apple remote) In-Reply-To: <82073F0E-6E53-469A-BC85-4CAE74EF504F@macports.org> References: <47854183.5090203@gmail.com> <5F54F6B9-6AD1-411C-B7D3-89AA75F00B1A@macports.org> <478553C5.3080804@gmail.com> <82073F0E-6E53-469A-BC85-4CAE74EF504F@macports.org> Message-ID: <47855680.7080801@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ryan Schmidt wrote: | No need to look in the Portfile itself. Just type "port info MPlayer". | That will print out the maintainer's complete email address, which in | this case ends with macports.org Wow, for some reason I hadn't ever used that command of port before. The info shows both the description, along with all the dependencies. Here I had been using port search {portname} followed up with port deps {portname} and port variants {portname} to get all the info that can be found in port info {portname}. I must say, I'm quite pleased with that feature, and glad that you mentioned Ryan, since I'll be using it much more in the future. Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHhVaANtosHRPp48MRAgRZAKCi3GIxFmNqsr3uB49EQYCzhkcKogCfS0qs gujCzPNx56z8UZoBDwP5NsY= =3Ajp -----END PGP SIGNATURE----- From ryandesign at macports.org Wed Jan 9 15:37:17 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 9 15:37:54 2008 Subject: port info (was Re: Mplayer and apple remote) In-Reply-To: <47855680.7080801@gmail.com> References: <47854183.5090203@gmail.com> <5F54F6B9-6AD1-411C-B7D3-89AA75F00B1A@macports.org> <478553C5.3080804@gmail.com> <82073F0E-6E53-469A-BC85-4CAE74EF504F@macports.org> <47855680.7080801@gmail.com> Message-ID: On Jan 9, 2008, at 17:19, Matrix Mole wrote: > Ryan Schmidt wrote: > >> No need to look in the Portfile itself. Just type "port info >> MPlayer". >> That will print out the maintainer's complete email address, which in >> this case ends with macports.org > > > Wow, for some reason I hadn't ever used that command of port > before. The > info shows both the description, along with all the dependencies. > Here I > had been using port search {portname} followed up with port deps > {portname} and port variants {portname} to get all the info that > can be > found in port info {portname}. I must say, I'm quite pleased with that > feature, and glad that you mentioned Ryan, since I'll be using it much > more in the future. You should read "man port" and http://guide.macports.org/ ; maybe there will be more things you'd like to know! :-) From opendarwin.org at darkart.com Wed Jan 9 15:49:15 2008 From: opendarwin.org at darkart.com (Eric Hall) Date: Wed Jan 9 15:49:10 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> References: <20080106233000.GC3137@run.duo> <20080107144937.GD3137@run.duo> <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> Message-ID: <20080109234915.GO5860@darkart.com> On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote: > > On Jan 7, 2008, at 08:49, George Georgalis wrote: > > >I have also tried exporting DYLD_LIBRARY_PATH, expat is not found. > > That should not be necessary. > > I have p5-xml-parser and expat installed. Never seen this problem. > > The obvious difference I see is that your MacPorts prefix is /usr/ > local/MacPorts instead of the usual /opt/local. Can you check if > anything ended up getting installed in the /opt/local by mistake? > Also note that /usr/local is not a good prefix to use for MacPorts. Some ports have specific instructions to ignore /usr/local as they (would otherwise) automatically search /usr/local and pick up items that users had manually (or otherwise outside of MacPorts) installed, which can result in confusion and later breakage. -eric From ryandesign at macports.org Wed Jan 9 16:04:09 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 9 16:11:23 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <20080109234915.GO5860@darkart.com> References: <20080106233000.GC3137@run.duo> <20080107144937.GD3137@run.duo> <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> <20080109234915.GO5860@darkart.com> Message-ID: On Jan 9, 2008, at 17:49, Eric Hall wrote: > On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote: > >> On Jan 7, 2008, at 08:49, George Georgalis wrote: >> >>> I have also tried exporting DYLD_LIBRARY_PATH, expat is not found. >> >> That should not be necessary. >> >> I have p5-xml-parser and expat installed. Never seen this problem. >> >> The obvious difference I see is that your MacPorts prefix is /usr/ >> local/MacPorts instead of the usual /opt/local. Can you check if >> anything ended up getting installed in the /opt/local by mistake? > > Also note that /usr/local is not a good prefix to use > for MacPorts. Some ports have specific instructions to > ignore /usr/local as they (would otherwise) automatically > search /usr/local and pick up items that users had > manually (or otherwise outside of MacPorts) installed, > which can result in confusion and later breakage. True, /usr/local is a bad prefix to use for MacPorts. However, George is not using /usr/local as his MacPorts prefix. He's using /usr/local/ MacPorts. And there should be no problem with that. From jmpp at macports.org Wed Jan 9 22:12:28 2008 From: jmpp at macports.org (Juan Manuel Palacios) Date: Wed Jan 9 22:10:31 2008 Subject: "The following install step failed: run postflight script for MacPorts-1.6.0." In-Reply-To: References: <8D63E40A-5563-488C-9E4A-302098EC13A9@macports.org> <3D4AEF5E-9EBB-4571-B78D-FC28A18E7846@macports.org> Message-ID: On Jan 9, 2008, at 2:00 AM, Stefan Schwarzer wrote: > > Here are the info. Can it be that it can't connect to MacPorts (for > an update or so) which causes the problem? I am behind a firewill - > will have to ask the admin to open port 873 - if that's correct > > Jan 9 07:25:23 gridmac7 Installer[18967]: Localized installer > script postflight found in the MacPorts-1.6.0 package. Using > compatibility mode. > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Unknown > shell! Please set your MacPorts compatible environment manually. The script is built to only tweak the environment for the bash and tcsh shells, which I attempt to detect in the script. If I don't detect either I instruct the user to setup his/her environment manually, since the script is built for a default scenario and shells other than bash and tcsh (legacy support) are not standard. What shell are you running? Can you please tell me the output of "basename $SHELL"? > > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:23: --- last message repeated 1 time --- > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Checking > the shell environment for user "schwarzer"... Even though the shell was not recognized, the script still went ahead and tried to tweak the environment. My mistake, I should have instructed it to exit successfully and not do anything else if the shell can't be determined. This is already fixed and will be in the next MacPorts pkg installer, whenever that comes around (I'll think about re-releasing the 1.6.0 installers with an improved script, but at the moment I have no final word on that). > > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:23: --- last message repeated 1 time --- > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: /Users/ > schwarzer/Downloads/8.1.08/MacPorts-1.6.0.pkg/Contents/Resources/ > English.lproj/postflight: line 71: /Users/schwarzer/.: Is a directory > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: /Users/ > schwarzer/Downloads/8.1.08/MacPorts-1.6.0.pkg/Contents/Resources/ > English.lproj/postflight: line 96: /Users/schwarzer/.: Is a directory These errors creep up because the script doesn't have a file to add the settings to, since it couldn't determine the shell and didn't exit. Already fixed per my comments above. > > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Your > shell already has the right MANPATH environment variable for use > with MacPorts! Expected: no shell could be determined and therefore, most likely, no MANPATH variable was found; in such case the script refrains from adding anything to MANPATH (see "destails of the postflight script" at http://guide.macports.org/#installing.macports for more details) > > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:23 gridmac7 runner[18974]: postflight[18990]: Your > shell already has the right DISPLAY environment variable for use > with MacPorts! Expected if you're on Leopard, are you? In any other case, adding a DISPLAY variable would have been attempted and an error such as Users/schwarzer/Downloads/8.1.08/MacPorts-1.6.0.pkg/Contents/Resources/ English.lproj/postflight: line 71: /Users/schwarzer/.: Is a directory should have occurred. > > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24: --- last message repeated 1 time --- > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Synchronizing the MacPorts installation with the project's rsync > server... > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24: --- last message repeated 1 time --- > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Synchronizing local ports tree from rsync://rsync.macports.org/ > release/ports/ > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: rsync: > failed to connect to rsync.macports.org: Connection refused (61) > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: rsync > error: error in socket IO (code 10) at /SourceCache/rsync/rsync-30/ > rsync/clientserver.c(94) > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Error: / > opt/local/bin/port: port selfupdate failed: Couldn't sync the ports > tree: Synchronization the local ports tree failed doing rsync > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: An > attempt to synchronize your recent MacPorts installation with the > project's rsync server failed! > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Please > run 'port -d selfupdate' manually to find out the cause of the error. > Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: > Jan 9 07:25:24 gridmac7 Installer[18967]: Install failed: The > following install step failed: run postflight script for > MacPorts-1.6.0. Contact the software manufacturer for assistance. "selfupdate" failed for some reason, probably rsync blocking, and the script bailed out with an error code. I've corrected this behavior too. Thanks for your feedback, much appreciated! Regards,... -jmpp From jmpp at macports.org Wed Jan 9 22:13:18 2008 From: jmpp at macports.org (Juan Manuel Palacios) Date: Wed Jan 9 22:11:17 2008 Subject: "The following install step failed: run postflight script for MacPorts-1.6.0." In-Reply-To: References: <8D63E40A-5563-488C-9E4A-302098EC13A9@macports.org> <3D4AEF5E-9EBB-4571-B78D-FC28A18E7846@macports.org> Message-ID: <95CB3A4D-CFCF-40CE-96B5-C2A29D0FDACD@macports.org> On Jan 9, 2008, at 4:20 PM, Ryan Schmidt wrote: > >> Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: >> Synchronizing local ports tree from rsync://rsync.macports.org/ >> release/ports/ >> Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: >> Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: rsync: >> failed to connect to rsync.macports.org: Connection refused (61) >> Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: >> Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: rsync >> error: error in socket IO (code 10) at /SourceCache/rsync/rsync-30/ >> rsync/clientserver.c(94) >> Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Error: / >> opt/local/bin/port: port selfupdate failed: Couldn't sync the ports >> tree: Synchronization the local ports tree failed doing rsync >> Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: >> Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: An >> attempt to synchronize your recent MacPorts installation with the >> project's rsync server failed! >> Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: >> Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: Please >> run 'port -d selfupdate' manually to find out the cause of the error. >> Jan 9 07:25:24 gridmac7 runner[18974]: postflight[18990]: >> Jan 9 07:25:24 gridmac7 Installer[18967]: Install failed: The >> following install step failed: run postflight script for >> MacPorts-1.6.0. Contact the software manufacturer for assistance. > > So the postflight script failed because it couldn't connect to the > rsync server. Doesn't matter why it happened (whether our rsync > server was down (which it wasn't) or whether the user's firewall > prevented the connection); we should ensure that any inability to > connect to the rsync server does not cause the postflight script to > fail like that. Best thing would be if we could pop up a friendly > message to the user that they need to update their installation > themselves, but it might also be ok to just silently fail. In any > event, the installation in the Installer should complete. Done! -jmpp From ryandesign at macports.org Wed Jan 9 22:32:27 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 9 22:33:02 2008 Subject: "The following install step failed: run postflight script for MacPorts-1.6.0." In-Reply-To: References: <8D63E40A-5563-488C-9E4A-302098EC13A9@macports.org> <3D4AEF5E-9EBB-4571-B78D-FC28A18E7846@macports.org> Message-ID: <9BED490F-F9F2-4C0B-AB70-E133A7E02175@macports.org> On Jan 10, 2008, at 00:12, Juan Manuel Palacios wrote: > This is already fixed and will be in the next MacPorts pkg > installer, whenever that comes around (I'll think about re- > releasing the 1.6.0 installers with an improved script, but at the > moment I have no final word on that). You're not contemplating a stealth upgrade, are you? That thing we hate other software developers for doing? :-) If there is a problem in the disk images and we need to rebuild them, then the version number of such new images should be no less than 1.6.1. From jmpp at macports.org Wed Jan 9 22:52:10 2008 From: jmpp at macports.org (Juan Manuel Palacios) Date: Wed Jan 9 22:50:15 2008 Subject: "The following install step failed: run postflight script for MacPorts-1.6.0." In-Reply-To: <9BED490F-F9F2-4C0B-AB70-E133A7E02175@macports.org> References: <8D63E40A-5563-488C-9E4A-302098EC13A9@macports.org> <3D4AEF5E-9EBB-4571-B78D-FC28A18E7846@macports.org> <9BED490F-F9F2-4C0B-AB70-E133A7E02175@macports.org> Message-ID: <3AFBC320-0342-45B3-B54B-F719DCA4F629@macports.org> On Jan 10, 2008, at 2:02 AM, Ryan Schmidt wrote: > > On Jan 10, 2008, at 00:12, Juan Manuel Palacios wrote: > >> This is already fixed and will be in the next MacPorts pkg >> installer, whenever that comes around (I'll think about re- >> releasing the 1.6.0 installers with an improved script, but at the >> moment I have no final word on that). > > You're not contemplating a stealth upgrade, are you? That thing we > hate other software developers for doing? :-) If there is a problem > in the disk images and we need to rebuild them, then the version > number of such new images should be no less than 1.6.1. Thankfully, most of the problems that have crept up only affect Panther, which is a small audience. All of them have been fixed already so I'm preparing a 1.6.1 release, off which I'm planning to rebuild the dmg's. So, in short: no, it wouldn't be a stealth update, not-while-I'm-around-days ;-) In any case, I have to think a bit more about it and consider other possible failures (mostly of the postflight script) in order to fix them before the bite us in round 2... but one thing I definitely need to do is think about this entire business once I get my sanity back after some much needed sleep! Regards,... -jmpp From boeyms at macports.org Wed Jan 9 23:09:46 2008 From: boeyms at macports.org (Boey Maun Suang) Date: Wed Jan 9 23:09:41 2008 Subject: MacPorts 1.6.0 dmg now available for Panther (Mac OS X 10.3) Message-ID: <16386.202.81.69.153.1199948986.squirrel@webmail.tuffmail.net> Hi everyone, Firstly, apologies for cross-posting, but I wanted to make sure everyone gets this. This message is to notify all of our wonderful Panther-using MacPorts users that we've finally ironed out the bugs that were preventing MacPorts 1.6.0 from operating correctly on Panther, and have now uploaded a Panther dmg incorporating our fixes, which you can now download (you can fetch it directly [1], or go via the installation page of the MacPorts website [2]). A big thank you to Juan Manuel Palacios and Kevin Ballard for providing the fixes, to Chris Janton for confirming that one particular problem wasn't just with my build machine, and to all of the Panther users who reported the problems! For those Panther users who like installing MacPorts from source instead of from our dmgs, the 1.6.0 tarball doesn't yet incorporate the Panther fixes, but we'll be releasing a 1.6.1 update soon, so you should have to wait too long. If you're really keen, however, you can still do a 1.6.0 source install by applying a few patches from our repository. Those not interested can safely skip this bit, but if you are interested, here's what to do: === Start of patch instructions === 1. Download and extract the MacPorts tarball as normal (see the "Source Install" section of the MacPorts Guide [3]). 2. Download the changesets 32105 [4], 32212 [5], 32514 [6] and 32525 [7] from the MacPorts repository, copying or saving them to the "MacPorts 1.x.x" directory that the MacPorts tarball extracted itself into. If your browser displays the patches instead of saving them, use your browser's "File > Save As..." menu item -- they should save with filenames like "changeset_32105.diff". 3. At the command line, change into the directory as per the MacPorts Guide [3], but before running the "./configure" command as described there, run the following commands (one for each of the changeset files you saved above): % patch -p3 < changeset_32105.diff % patch -p3 < changeset_32212.diff % patch -p3 < changeset_32514.diff % patch -p3 < changeset_32525.diff 4. Follow the rest of the source install procedure as normal. === End of patch instructions === Don't worry, we won't be making you source installers get used to doing things like this! Once again, apologies to all our Panther users out there, and thanks for using MacPorts. Wishing you all a happy 2008, Boey Maun Suang [1] http://svn.macports.org/repository/macports/downloads/MacPorts-1.6.0/MacPorts-1.6.0-10.3-Panther.dmg [2] http://www.macports.org/install.php [3] http://guide.macports.org/#installing.source [4] http://trac.macosforge.org/projects/macports/changeset/32105?format=diff&new=32105 [5] http://trac.macosforge.org/projects/macports/changeset/32212?format=diff&new=32212 [6] http://trac.macosforge.org/projects/macports/changeset/32514?format=diff&new=32514 [7] http://trac.macosforge.org/projects/macports/changeset/32525?format=diff&new=32525 -- Boey Maun Suang (Boey is my surname) Email: boeyms@macports.org From raimue at macports.org Thu Jan 10 07:42:07 2008 From: raimue at macports.org (=?UTF-8?B?UmFpbmVyIE3DvGxsZXI=?=) Date: Thu Jan 10 07:42:13 2008 Subject: [MacPorts] #12873: Python25 upgrade 2 does not work with Mac OSX 10.3.9, fix attached In-Reply-To: <055.c2df8ebba46f5ca6d5a4b8eb0b46fd46@macosforge.org> References: <046.d2f3212b69cafc093261969ad6eb594a@macosforge.org> <055.c2df8ebba46f5ca6d5a4b8eb0b46fd46@macosforge.org> Message-ID: <47863CCF.6060808@macports.org> MacPorts wrote: > #12873: Python25 upgrade 2 does not work with Mac OSX 10.3.9, fix attached > -------------------------------+-------------------------------------------- > Reporter: jwelp1@gmail.com | Owner: mww@macports.org > Type: defect | Status: closed > Priority: Normal | Milestone: Port Bugs > Component: ports | Version: 1.5.0 > Resolution: fixed | Keywords: Python25 > -------------------------------+-------------------------------------------- > Comment (by william.allen.simpson@gmail.com): > > Because the ticket was closed before verification, and I'm not on the CC > list, it disappeared from the tickets I'm watching. Just checked, and it > does install here.... > > It doesn't install a link from python to python2.5, but that's another > issue. Thanks! The symlink can be created by using the port python_select. As we provide multiple python versions, there is no other solution possible. $ sudo port install python_select $ sudo python_select python25 Rainer From face at CentosPrime.COM Thu Jan 10 08:02:07 2008 From: face at CentosPrime.COM (Chris Janton) Date: Thu Jan 10 08:02:09 2008 Subject: perl5.8.8_1 does not properly activate on 10.3.9 Message-ID: <52EE3B23-4645-47D2-B761-1417B4E60AF2@CentosPrime.COM> house54 4 # sudo port upgrade perl5.8 ---> Fetching perl5.8 ---> Verifying checksum(s) for perl5.8 ---> Extracting perl5.8 ---> Applying patches to perl5.8 ---> Configuring perl5.8 ---> Building perl5.8 with target all ---> Staging perl5.8 into destroot ---> Deactivating perl5.8 5.8.8_0 Error: Deactivating perl5.8 5.8.8_0 failed: error deleting "/opt/ local/lib/perl5/5.8.8/vars.pm": invalid argument 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From braden at endoframe.com Thu Jan 10 16:30:31 2008 From: braden at endoframe.com (Braden McDaniel) Date: Thu Jan 10 16:30:23 2008 Subject: Confused dependencies? Message-ID: <4786B8A7.60701@endoframe.com> I'm presented with the following: > turketron:~ bmcdaniel$ port installed | grep tiff > tiff @3.8.2_0+darwin_8 > tiff @3.8.2_1+darwin_8+macosx (active) > turketron:~ bmcdaniel$ sudo port uninstall tiff@3.8.2_0+darwin_8 > ---> Unable to uninstall tiff 3.8.2_0+darwin_8, the following ports depend on it: > ---> gtk2 > ---> gtk2 > ---> gtk2 > Error: port uninstall failed: Please uninstall the ports that depend on tiff first. > turketron:~ bmcdaniel$ port installed | grep gtk2 > gtk2 @2.12.2_0+x11 (active) There were two other versions of gtk2 installed; but port let me uninstall them. I'm assuming things have fallen into some confused state. How might I fix it? -- Braden McDaniel e-mail: Jabber: From eridius at macports.org Thu Jan 10 17:01:22 2008 From: eridius at macports.org (Kevin Ballard) Date: Thu Jan 10 17:01:15 2008 Subject: Confused dependencies? In-Reply-To: <4786B8A7.60701@endoframe.com> References: <4786B8A7.60701@endoframe.com> Message-ID: If you uninstall and reinstall tiff, that might fix it. You can uninstall tiff by passing the -f flag to force it. On Jan 10, 2008, at 7:30 PM, Braden McDaniel wrote: > I'm presented with the following: > >> turketron:~ bmcdaniel$ port installed | grep tiff >> tiff @3.8.2_0+darwin_8 >> tiff @3.8.2_1+darwin_8+macosx (active) >> turketron:~ bmcdaniel$ sudo port uninstall tiff@3.8.2_0+darwin_8 >> ---> Unable to uninstall tiff 3.8.2_0+darwin_8, the following >> ports depend on it: >> ---> gtk2 >> ---> gtk2 >> ---> gtk2 >> Error: port uninstall failed: Please uninstall the ports that >> depend on tiff first. >> turketron:~ bmcdaniel$ port installed | grep gtk2 >> gtk2 @2.12.2_0+x11 (active) > > There were two other versions of gtk2 installed; but port let me > uninstall them. > > I'm assuming things have fallen into some confused state. How might > I fix it? > > -- > Braden McDaniel e-mail: > Jabber: > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080110/d335abba/attachment.html From ecronin at macports.org Thu Jan 10 17:15:03 2008 From: ecronin at macports.org (Eric Cronin) Date: Thu Jan 10 17:22:06 2008 Subject: Mplayer and apple remote In-Reply-To: <478553C5.3080804@gmail.com> References: <47854183.5090203@gmail.com> <5F54F6B9-6AD1-411C-B7D3-89AA75F00B1A@macports.org> <478553C5.3080804@gmail.com> Message-ID: <82D7ED89-5297-4ACA-A294-BE78CA65A65D@macports.org> On Jan 9, 2008, at 6:07 PM, Matrix Mole wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ryan Schmidt wrote: > | On Jan 9, 2008, at 15:49, Matrix Mole wrote: > | > | I presume it's the infrared Apple Remote device that comes with > newer > | Macs. You could ask the maintainer of the MPlayer port or the > developers > | of the MPlayer software if you want to know for sure. > | > > I see in the Portfile for MPlayer that the maintainer is listed as: > > maintainers ecronin \ > ~ openmaintainer > > Unfortunately, on the Developers page at macports, the link to ecronin > appears to generate a 404 error. Does anyone know how to get ahold of > him, or have his email handy to forward my question on to? I was successfully located off-list and replied there, but just for the curious and the mailing list archives, noappleremote does refer to the IR remote, I changed to variant description for it to be clearer. Thanks, Eric From ryandesign at macports.org Thu Jan 10 19:54:17 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 10 19:54:47 2008 Subject: Confused dependencies? In-Reply-To: <4786B8A7.60701@endoframe.com> References: <4786B8A7.60701@endoframe.com> Message-ID: <0B1567B1-4A71-49A8-90A0-8028BF83C5B6@macports.org> On Jan 10, 2008, at 18:30, Braden McDaniel wrote: > I'm presented with the following: > >> turketron:~ bmcdaniel$ port installed | grep tiff >> tiff @3.8.2_0+darwin_8 >> tiff @3.8.2_1+darwin_8+macosx (active) >> turketron:~ bmcdaniel$ sudo port uninstall tiff@3.8.2_0+darwin_8 >> ---> Unable to uninstall tiff 3.8.2_0+darwin_8, the following >> ports depend on it: >> ---> gtk2 >> ---> gtk2 >> ---> gtk2 >> Error: port uninstall failed: Please uninstall the ports that >> depend on tiff first. >> turketron:~ bmcdaniel$ port installed | grep gtk2 >> gtk2 @2.12.2_0+x11 (active) > > There were two other versions of gtk2 installed; but port let me > uninstall them. > > I'm assuming things have fallen into some confused state. How might > I fix it? Are you just referring to the fact that "gtk2" is printed three times as a dependency, though it's only installed once? If so, then that's a well-known (but still unfixed) bug: http://trac.macosforge.org/projects/macports/ticket/8763 From braden at endoframe.com Thu Jan 10 20:24:51 2008 From: braden at endoframe.com (Braden McDaniel) Date: Thu Jan 10 20:24:42 2008 Subject: Confused dependencies? In-Reply-To: <0B1567B1-4A71-49A8-90A0-8028BF83C5B6@macports.org> References: <4786B8A7.60701@endoframe.com> <0B1567B1-4A71-49A8-90A0-8028BF83C5B6@macports.org> Message-ID: <1200025491.5278.225.camel@hinge.endoframe.net> On Thu, 2008-01-10 at 21:54 -0600, Ryan Schmidt wrote: > On Jan 10, 2008, at 18:30, Braden McDaniel wrote: > > > I'm presented with the following: > > > >> turketron:~ bmcdaniel$ port installed | grep tiff > >> tiff @3.8.2_0+darwin_8 > >> tiff @3.8.2_1+darwin_8+macosx (active) > >> turketron:~ bmcdaniel$ sudo port uninstall tiff@3.8.2_0+darwin_8 > >> ---> Unable to uninstall tiff 3.8.2_0+darwin_8, the following > >> ports depend on it: > >> ---> gtk2 > >> ---> gtk2 > >> ---> gtk2 > >> Error: port uninstall failed: Please uninstall the ports that > >> depend on tiff first. > >> turketron:~ bmcdaniel$ port installed | grep gtk2 > >> gtk2 @2.12.2_0+x11 (active) > > > > There were two other versions of gtk2 installed; but port let me > > uninstall them. > > > > I'm assuming things have fallen into some confused state. How might > > I fix it? > > Are you just referring to the fact that "gtk2" is printed three times > as a dependency, though it's only installed once? If so, then that's > a well-known (but still unfixed) bug: > > http://trac.macosforge.org/projects/macports/ticket/8763 Not "just" that; if this were only cosmetic, I wouldn't care much. I'm referring to the fact that port won't let me uninstall the inactive tiff because there are apparently bogus dependencies around. The lone installed (and active) gtk2 should be using the active tiff installation. This is just a particular instance of a problem that now pervades my MacPorts installation. -- Braden McDaniel e-mail: Jabber: From ryandesign at macports.org Thu Jan 10 20:38:11 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 10 20:45:23 2008 Subject: Confused dependencies? In-Reply-To: <1200025491.5278.225.camel@hinge.endoframe.net> References: <4786B8A7.60701@endoframe.com> <0B1567B1-4A71-49A8-90A0-8028BF83C5B6@macports.org> <1200025491.5278.225.camel@hinge.endoframe.net> Message-ID: <9799E0E5-ED92-416D-93EB-51BC96F47E39@macports.org> On Jan 10, 2008, at 22:24, Braden McDaniel wrote: > On Thu, 2008-01-10 at 21:54 -0600, Ryan Schmidt wrote: > >> On Jan 10, 2008, at 18:30, Braden McDaniel wrote: >> >>> I'm presented with the following: >>> >>>> turketron:~ bmcdaniel$ port installed | grep tiff >>>> tiff @3.8.2_0+darwin_8 >>>> tiff @3.8.2_1+darwin_8+macosx (active) >>>> turketron:~ bmcdaniel$ sudo port uninstall tiff@3.8.2_0+darwin_8 >>>> ---> Unable to uninstall tiff 3.8.2_0+darwin_8, the following >>>> ports depend on it: >>>> ---> gtk2 >>>> ---> gtk2 >>>> ---> gtk2 >>>> Error: port uninstall failed: Please uninstall the ports that >>>> depend on tiff first. >>>> turketron:~ bmcdaniel$ port installed | grep gtk2 >>>> gtk2 @2.12.2_0+x11 (active) >>> >>> There were two other versions of gtk2 installed; but port let me >>> uninstall them. >>> >>> I'm assuming things have fallen into some confused state. How might >>> I fix it? >> >> Are you just referring to the fact that "gtk2" is printed three times >> as a dependency, though it's only installed once? If so, then that's >> a well-known (but still unfixed) bug: >> >> http://trac.macosforge.org/projects/macports/ticket/8763 > > Not "just" that; if this were only cosmetic, I wouldn't care much. > > I'm referring to the fact that port won't let me uninstall the > inactive > tiff because there are apparently bogus dependencies around. The lone > installed (and active) gtk2 should be using the active tiff > installation. > > This is just a particular instance of a problem that now pervades my > MacPorts installation. That issue, too, pervades all our MacPorts installations. It's expected behavior, until someone reworks that aspect of how MacPorts works. gtk2 depends on tiff. Any tiff port you attempt to uninstall will generate this message, even if it's inactive and you have another one installed that's active. This is the ticket for this bug: http://trac.macosforge.org/projects/macports/ticket/12344 In this case, it is most probably safe to forcibly uninstall the older inactive tiff. sudo port -f uninstall tiff @3.8.2_0+darwin_8 From boeyms at macports.org Thu Jan 10 21:49:51 2008 From: boeyms at macports.org (Boey Maun Suang) Date: Thu Jan 10 21:49:50 2008 Subject: MacPorts 1.6.0 dmg now available for Panther (Mac OS X 10.3) In-Reply-To: References: <16386.202.81.69.153.1199948986.squirrel@webmail.tuffmail.net> Message-ID: <4541C30A-8A58-4B62-B403-198293C6F435@macports.org> Hi Larry, On 11/01/2008, at 2:58 AM, Larry Snyder wrote: > Thanks for doing this, and for sending out the email. Unfortunately, > I get the following at the 'summary' stage of installing: > > "Installation had errors. Install Failed. The following install > step failed: run postflight script for MacPorts. Contact the > software manufacturer for assistance" There have been some problems reported with the postflight script, including in this thread [1]. Juan's the person who knows about the script, so you'd be best off asking him for help, but you should at least try the troubleshooting steps in that thread to see if your problem is the same or slightly different. I hope that that helps. Kind regards, Maun Suang [1] http://lists.macosforge.org/pipermail/macports-users/2008-January/ thread.html#8169 -- Boey Maun Suang (Boey is my surname) Email: boeyms at macports dot org From face at CentosPrime.COM Fri Jan 11 06:39:52 2008 From: face at CentosPrime.COM (Chris Janton) Date: Fri Jan 11 06:39:54 2008 Subject: Upgrade of imap-uw @2004g_0+darwin_7 fails Message-ID: <34C13CE0-E004-4BA3-9E9C-6CFDF8AF35FB@centosprime.com> Today's port sync offered that imap-uw was in need of an upgrade. This was the result on my 10.3.9 server. admin@x:admin:126 $ sudo port upgrade imap-uw Warning: No mirror sites on file for class opendarwin ---> Fetching imap-uw ---> Attempting to fetch imap-2007.tar.Z from ftp:// ftp.cac.washington.edu/imap/ ---> Verifying checksum(s) for imap-uw ---> Extracting imap-uw ---> Applying patches to imap-uw Error: Target org.macports.patch returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_mail_im ap-uw/work/imap-2007" && patch -p0 < '/opt/local/var/macports/sources/ rsync.macports.org/release/ports/mail/imap-uw/files/patch-src-osdep- unix-Makefile'" returned error 1 Command output: patching file src/osdep/unix/Makefile Hunk #1 FAILED at 525. 1 out of 1 hunk FAILED -- saving rejects to file src/osdep/unix/ Makefile.rej Error: Unable to upgrade port: 1 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From face at CentosPrime.COM Fri Jan 11 07:06:07 2008 From: face at CentosPrime.COM (Chris Janton) Date: Fri Jan 11 07:06:43 2008 Subject: Upgrade of imap-uw @2004g_0+darwin_7 fails In-Reply-To: <34C13CE0-E004-4BA3-9E9C-6CFDF8AF35FB@centosprime.com> References: <34C13CE0-E004-4BA3-9E9C-6CFDF8AF35FB@centosprime.com> Message-ID: <063FF45F-8F8C-472E-AE0D-F2908B30695B@CentosPrime.COM> On 2008-01-11 , at 07:39 , Chris Janton wrote: > Today's port sync offered that imap-uw was in need of an upgrade. > > This was the result on my 10.3.9 server. Note: imap-uw installs cleanly on my 10.4.11 system (Intel) mac 2 # sudo port install imap-uw Warning: No mirror sites on file for class opendarwin ---> Fetching imap-uw ---> Attempting to fetch imap-2007.tar.Z from ftp:// ftp.cac.washington.edu/imap/ ---> Verifying checksum(s) for imap-uw ---> Extracting imap-uw ---> Configuring imap-uw ---> Building imap-uw with target oxp ---> Staging imap-uw into destroot ---> Installing imap-uw 2007_0 ---> Activating imap-uw 2007_0 ---> Cleaning imap-uw 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From face at CentosPrime.COM Fri Jan 11 07:06:21 2008 From: face at CentosPrime.COM (Chris Janton) Date: Fri Jan 11 07:06:43 2008 Subject: perl5.8.8_1 does not properly activate on 10.3.9 In-Reply-To: <52EE3B23-4645-47D2-B761-1417B4E60AF2@CentosPrime.COM> References: <52EE3B23-4645-47D2-B761-1417B4E60AF2@CentosPrime.COM> Message-ID: <7F1FA7EC-8202-45DC-8BF1-06D318CB8908@CentosPrime.COM> On 2008-01-10 , at 09:02 , Chris Janton wrote: > house54 4 # sudo port upgrade perl5.8 > ---> Deactivating perl5.8 5.8.8_0 > Error: Deactivating perl5.8 5.8.8_0 failed: error deleting "/opt/ > local/lib/perl5/5.8.8/vars.pm": invalid argument > I did a port sync followed by a port upgrade outdated today and the upgrade for perl5.8 worked. house54 4 # sudo port upgrade outdated ---> Deactivating perl5.8 5.8.8_0 ---> Installing perl5.8 5.8.8_1 ---> Activating perl5.8 5.8.8_1 ---> Cleaning perl5.8 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From william at gallaf.net Fri Jan 11 08:44:41 2008 From: william at gallaf.net (William Gallafent) Date: Fri Jan 11 08:44:32 2008 Subject: LibSDL build failure on Mac OS 10.5. Message-ID: <6C46BBB1-9A58-4C36-82B0-7C6C53B5E262@gallaf.net> It looks as if the macports patch does not apply to the version of libsdl sources which are downloaded: humber:Video williamg$ sudo port install mpeg4ip ---> Fetching automake ---> Attempting to fetch automake-1.10.tar.bz2 from http://ftp.gnu.org/gnu/automake ---> Verifying checksum(s) for automake ---> Extracting automake ---> Configuring automake ---> Building automake with target all ---> Staging automake into destroot ---> Installing automake 1.10_0 ---> Activating automake 1.10_0 ---> Cleaning automake ---> Fetching libsdl ---> Attempting to fetch SDL-1.2.13.tar.gz from http://www.libsdl.org/release/ ---> Verifying checksum(s) for libsdl ---> Extracting libsdl ---> Applying patches to libsdl Error: Target org.macports.patch returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_devel_libsdl/work/SDL-1.2.13" && patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/release/ports/ devel/libsdl/files/patch-AudioFilePlayer.h'" returned error 1 Command output: patching file src/cdrom/macosx/AudioFilePlayer.h Hunk #1 FAILED at 33. 1 out of 1 hunk FAILED -- saving rejects to file src/cdrom/macosx/ AudioFilePlayer.h.rej Error: The following dependencies failed to build: libsdl Error: Status 1 encountered during processing. From william at gallaf.net Fri Jan 11 08:52:25 2008 From: william at gallaf.net (William Gallafent) Date: Fri Jan 11 08:52:17 2008 Subject: LibSDL build failure on Mac OS 10.5. In-Reply-To: <6C46BBB1-9A58-4C36-82B0-7C6C53B5E262@gallaf.net> References: <6C46BBB1-9A58-4C36-82B0-7C6C53B5E262@gallaf.net> Message-ID: <6A0EB6C2-42FE-474B-8C8E-64CF4B1238F7@gallaf.net> On 11 Jan 2008, at 16:44, William Gallafent wrote: > ---> Applying patches to libsdl > Error: Target org.macports.patch returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_devel_libsdl/work/SDL-1.2.13" && patch - > p0 < '/opt/local/var/macports/sources/rsync.macports.org/release/ > ports/devel/libsdl/files/patch-AudioFilePlayer.h'" returned error 1 > Command output: patching file src/cdrom/macosx/AudioFilePlayer.h > Hunk #1 FAILED at 33. > 1 out of 1 hunk FAILED -- saving rejects to file src/cdrom/macosx/ > AudioFilePlayer.h.rej Removing the following section from the port file completely appears to fix the problem: platform darwin 9 { patchfiles-append patch-AudioFilePlayer.h patch-SDL_coreaudio.c } - It looks as if the upstream sources now work OK on Mac OS 10.5, so there's no need for macports to apply these patches any more. From ryandesign at macports.org Fri Jan 11 12:44:16 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri Jan 11 12:44:45 2008 Subject: Upgrade of imap-uw @2004g_0+darwin_7 fails In-Reply-To: <063FF45F-8F8C-472E-AE0D-F2908B30695B@CentosPrime.COM> References: <34C13CE0-E004-4BA3-9E9C-6CFDF8AF35FB@centosprime.com> <063FF45F-8F8C-472E-AE0D-F2908B30695B@CentosPrime.COM> Message-ID: On Jan 11, 2008, at 09:06, Chris Janton wrote: > On 2008-01-11 , at 07:39 , Chris Janton wrote: > >> Today's port sync offered that imap-uw was in need of an upgrade. >> >> This was the result on my 10.3.9 server. > > Note: imap-uw installs cleanly on my 10.4.11 system (Intel) > > mac 2 # sudo port install imap-uw > Warning: No mirror sites on file for class opendarwin > ---> Fetching imap-uw > ---> Attempting to fetch imap-2007.tar.Z from ftp:// > ftp.cac.washington.edu/imap/ > ---> Verifying checksum(s) for imap-uw > ---> Extracting imap-uw > ---> Configuring imap-uw > ---> Building imap-uw with target oxp > ---> Staging imap-uw into destroot > ---> Installing imap-uw 2007_0 > ---> Activating imap-uw 2007_0 > ---> Cleaning imap-uw The port contains patches specific to Mac OS X 10.3.x. Those probably didn't get updated during the update to version 2007. You should file a ticket about this bug. If you can figure out whether the 10.3- specific patches are still needed, and if so how they need to be modified, that will make it easier to resolve this problem. From ryandesign at macports.org Fri Jan 11 12:45:18 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri Jan 11 12:45:44 2008 Subject: LibSDL build failure on Mac OS 10.5. In-Reply-To: <6A0EB6C2-42FE-474B-8C8E-64CF4B1238F7@gallaf.net> References: <6C46BBB1-9A58-4C36-82B0-7C6C53B5E262@gallaf.net> <6A0EB6C2-42FE-474B-8C8E-64CF4B1238F7@gallaf.net> Message-ID: <211ADD29-ABF5-4D63-82AE-44773EEEDF47@macports.org> On Jan 11, 2008, at 10:52, William Gallafent wrote: > On 11 Jan 2008, at 16:44, William Gallafent wrote: > >> ---> Applying patches to libsdl >> Error: Target org.macports.patch returned: shell command " cd "/ >> opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_deve >> l_libsdl/work/SDL-1.2.13" && patch -p0 < '/opt/local/var/macports/ >> sources/rsync.macports.org/release/ports/devel/libsdl/files/patch- >> AudioFilePlayer.h'" returned error 1 >> Command output: patching file src/cdrom/macosx/AudioFilePlayer.h >> Hunk #1 FAILED at 33. >> 1 out of 1 hunk FAILED -- saving rejects to file src/cdrom/macosx/ >> AudioFilePlayer.h.rej > > Removing the following section from the port file completely > appears to fix the problem: > > platform darwin 9 { > patchfiles-append patch-AudioFilePlayer.h patch-SDL_coreaudio.c > } > > - It looks as if the upstream sources now work OK on Mac OS 10.5, > so there's no need for macports to apply these patches any more. Please file a ticket in our issue tracker then, and assign it to the maintainer of the libsdl port. From afb at macports.org Fri Jan 11 12:49:22 2008 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Fri Jan 11 12:49:21 2008 Subject: LibSDL build failure on Mac OS 10.5. In-Reply-To: <211ADD29-ABF5-4D63-82AE-44773EEEDF47@macports.org> References: <6C46BBB1-9A58-4C36-82B0-7C6C53B5E262@gallaf.net> <6A0EB6C2-42FE-474B-8C8E-64CF4B1238F7@gallaf.net> <211ADD29-ABF5-4D63-82AE-44773EEEDF47@macports.org> Message-ID: <82d805e3334a4085daf1c01037723446@macports.org> Ryan Schmidt wrote: > On Jan 11, 2008, at 10:52, William Gallafent wrote: > >> On 11 Jan 2008, at 16:44, William Gallafent wrote: >> >>> ---> Applying patches to libsdl >>> Error: Target org.macports.patch returned: shell command " cd >>> "/opt/local/var/macports/build/ >>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_deve >>> l_libsdl/work/SDL-1.2.13" && patch -p0 < >>> '/opt/local/var/macports/sources/rsync.macports.org/release/ports/ >>> devel/libsdl/files/patch-AudioFilePlayer.h'" returned error 1 >>> Command output: patching file src/cdrom/macosx/AudioFilePlayer.h >>> Hunk #1 FAILED at 33. >>> 1 out of 1 hunk FAILED -- saving rejects to file >>> src/cdrom/macosx/AudioFilePlayer.h.rej >> >> Removing the following section from the port file completely appears >> to fix the problem: >> >> platform darwin 9 { >> patchfiles-append patch-AudioFilePlayer.h patch-SDL_coreaudio.c >> } >> >> - It looks as if the upstream sources now work OK on Mac OS 10.5, so >> there's no need for macports to apply these patches any more. > > Please file a ticket in our issue tracker then, and assign it to the > maintainer of the libsdl port. This issue was already fixed as http://trac.macports.org/projects/macports/ticket/13882 --anders From greg.hauptmann.ruby at gmail.com Fri Jan 11 17:21:28 2008 From: greg.hauptmann.ruby at gmail.com (Greg Hauptmann) Date: Fri Jan 11 17:21:16 2008 Subject: wireshark install failed? (Attempting to fetch docbkx412.zip from http://svn.macports.org/repository/macports/downloads/docbook-xml-4.1.2) Message-ID: Hi, I'm on leopard and have performed a successful "sudo port selfupdate", however I'm getting an error when performing "sudo port install wireshark". The console out is below. Any ideas/suggestions? ---> Attempting to fetch docbkx412.zip from http://svn.macports.org/repository/macports/downloads/docbook-xml-4.1.2 Error: Target org.macports.fetch returned: fetch failed Error: The following dependencies failed to build: gtk2 gtk-doc docbook-xml-4.1.2 docbook-xsl libxml2 scrollkeeper docbook-xml docbook-xml-4.2 docbook-xml-4.3 docbook-xml-4.4 docbook-xml-4.5 libxslt p5-xml-parser pango Xft2 xorg-xproto xorg-util-macros tiff libpcap Error: Status 1 encountered during processing. Full console ouput below: Macintosh:~ greg$ sudo port selfupdate MacPorts base version 1.5 installed Downloaded MacPorts base version 1.600 Configuring, Building and Installing new MacPorts base selfupdate done! Macintosh:~ greg$ Macintosh:~ greg$ Macintosh:~ greg$ sudo port install wireshark Password: ---> Fetching pkgconfig ---> Attempting to fetch pkg-config-0.22.tar.gz from http://pkg-config.freedesktop.org/releases/ ---> Verifying checksum(s) for pkgconfig ---> Extracting pkgconfig ---> Configuring pkgconfig ---> Building pkgconfig with target all ---> Staging pkgconfig into destroot ---> Installing pkgconfig 0.22_0 ---> Activating pkgconfig 0.22_0 ---> Cleaning pkgconfig ---> Fetching glib2 ---> Attempting to fetch glib-2.14.4.tar.bz2 from ftp://ftp.gtk.org/pub/glib/2.14/ ---> Verifying checksum(s) for glib2 ---> Extracting glib2 ---> Applying patches to glib2 ---> Configuring glib2 ---> Building glib2 with target all ---> Staging glib2 into destroot ---> Installing glib2 2.14.4_1+darwin_9 ---> Activating glib2 2.14.4_1+darwin_9 ---> Cleaning glib2 ---> Fetching atk ---> Attempting to fetch atk-1.20.0.tar.bz2 from http://mandril.creatis.insa-lyon.fr/linux/gnome.org/sources/atk/1.20/ ---> Verifying checksum(s) for atk ---> Extracting atk ---> Configuring atk ---> Building atk with target all ---> Staging atk into destroot ---> Installing atk 1.20.0_1 ---> Activating atk 1.20.0_1 ---> Cleaning atk ---> Fetching fontconfig ---> Attempting to fetch fontconfig-2.5.0.tar.gz from http://fontconfig.org/release/ ---> Verifying checksum(s) for fontconfig ---> Extracting fontconfig ---> Configuring fontconfig ---> Building fontconfig with target all ---> Staging fontconfig into destroot ---> Installing fontconfig 2.5.0_0+macosx ---> Activating fontconfig 2.5.0_0+macosx ---> Cleaning fontconfig ---> Fetching render ---> Attempting to fetch renderext-0.9.tar.bz2 from http://xlibs.freedesktop.org/release/ ---> Verifying checksum(s) for render ---> Extracting render ---> Configuring render ---> Building render with target all ---> Staging render into destroot ---> Installing render 0.9_1 ---> Activating render 0.9_1 ---> Cleaning render ---> Fetching xrender ---> Attempting to fetch libXrender-0.9.0.tar.bz2 from http://xlibs.freedesktop.org/release/ ---> Verifying checksum(s) for xrender ---> Extracting xrender ---> Configuring xrender ---> Building xrender with target all ---> Staging xrender into destroot ---> Installing xrender 0.9.0_2 ---> Activating xrender 0.9.0_2 ---> Cleaning xrender ---> Fetching cairo ---> Attempting to fetch cairo-1.4.12.tar.gz from http://cairographics.org/releases/ ---> Verifying checksum(s) for cairo ---> Extracting cairo ---> Configuring cairo ---> Building cairo with target all ---> Staging cairo into destroot ---> Installing cairo 1.4.12_0 ---> Activating cairo 1.4.12_0 ---> Cleaning cairo ---> Fetching xmlcatmgr ---> Attempting to fetch xmlcatmgr-2.2.tar.gz from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ ---> Verifying checksum(s) for xmlcatmgr ---> Extracting xmlcatmgr ---> Configuring xmlcatmgr ---> Building xmlcatmgr with target all ---> Staging xmlcatmgr into destroot ---> Installing xmlcatmgr 2.2_1 ---> Activating xmlcatmgr 2.2_1 ---> Cleaning xmlcatmgr ---> Fetching docbook-xml-4.1.2 ---> Attempting to fetch docbkx412.zip from http://www.oasis-open.org/docbook/xml/4.1.2/ ---> Attempting to fetch docbkx412.zip from http://svn.macports.org/repository/macports/distfiles/docbook-xml-4.1.2 ---> Attempting to fetch docbkx412.zip from http://svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch docbkx412.zip from http://svn.macports.org/repository/macports/downloads/docbook-xml-4.1.2 Error: Target org.macports.fetch returned: fetch failed Error: The following dependencies failed to build: gtk2 gtk-doc docbook-xml-4.1.2 docbook-xsl libxml2 scrollkeeper docbook-xml docbook-xml-4.2 docbook-xml-4.3 docbook-xml-4.4 docbook-xml-4.5 libxslt p5-xml-parser pango Xft2 xorg-xproto xorg-util-macros tiff libpcap Error: Status 1 encountered during processing. Macintosh:~ greg$ Tks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080112/7d07a47e/attachment-0001.html From ryandesign at macports.org Fri Jan 11 17:40:12 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri Jan 11 17:40:41 2008 Subject: wireshark install failed? (Attempting to fetch docbkx412.zip from http://svn.macports.org/repository/macports/downloads/docbook-xml-4.1.2) In-Reply-To: References: Message-ID: <82D6D3C7-13B5-4FAD-B600-378337C65701@macports.org> On Jan 11, 2008, at 19:21, Greg Hauptmann wrote: > I'm on leopard and have performed a successful "sudo port > selfupdate", however I'm getting an error when performing "sudo > port install wireshark". The console out is below. [snip] > ---> Fetching docbook-xml-4.1.2 > ---> Attempting to fetch docbkx412.zip from http://www.oasis- > open.org/docbook/xml/4.1.2/ > ---> Attempting to fetch docbkx412.zip from http:// > svn.macports.org/repository/macports/distfiles/docbook-xml-4.1.2 > ---> Attempting to fetch docbkx412.zip from http:// > svn.macports.org/repository/macports/distfiles/general/ > ---> Attempting to fetch docbkx412.zip from http:// > svn.macports.org/repository/macports/downloads/docbook-xml-4.1.2 > Error: Target org.macports.fetch returned: fetch failed > Error: The following dependencies failed to build: gtk2 gtk-doc > docbook-xml-4.1.2 docbook-xsl libxml2 scrollkeeper docbook-xml > docbook-xml-4.2 docbook-xml-4.3 docbook-xml-4.4 docbook-xml-4.5 > libxslt p5-xml-parser pango Xft2 xorg-xproto xorg-util-macros tiff > libpcap > Error: Status 1 encountered during processing. > Macintosh:~ greg$ So the problem was docbook-xml-4.1.2 couldn't fetch its distfile. It looks to me like it's still there on their server, so maybe their server just had a temporary problem. Please try again. From greg.hauptmann.ruby at gmail.com Sat Jan 12 00:16:48 2008 From: greg.hauptmann.ruby at gmail.com (Greg Hauptmann) Date: Sat Jan 12 00:16:37 2008 Subject: Fwd: wireshark install failed? (Attempting to fetch docbkx412.zip from http://svn.macports.org/repository/macports/downloads/docbook-xml-4.1.2) In-Reply-To: References: <82D6D3C7-13B5-4FAD-B600-378337C65701@macports.org> Message-ID: I actually get the following error when running wireshark, i.e. after a few seconds of a capture: Macintosh:~ greg$ wireshark --sync The program 'wireshark' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 50746 error_code 8 request_code 152 minor_code 4) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Macintosh:~ greg$ Any ideas/suggestions? The installation console out (which succeeded I believe) is below: Macintosh:~ greg$ sudo port install wireshark Password: ---> Fetching docbook-xml-4.1.2 ---> Attempting to fetch docbkx412.zip from http://www.oasis-open.org/docbook/xml/4.1.2/ ---> Verifying checksum(s) for docbook-xml-4.1.2 ---> Extracting docbook-xml-4.1.2 ---> Configuring docbook-xml-4.1.2 ---> Building docbook-xml-4.1.2 with target all ---> Staging docbook-xml-4.1.2 into destroot ---> Installing docbook-xml-4.1.2 4.1.2_1 ---> Activating docbook-xml-4.1.2 4.1.2_1 ###################################################################### # As MacPorts does not currently have a post-deactivate hook, # you will need to ensure that you manually remove the catalog # entry for this port when you uninstall it. To do so, run # "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.1.2/catalog.xml". ###################################################################### ---> Cleaning docbook-xml-4.1.2 ---> Fetching docbook-xsl ---> Attempting to fetch docbook-xsl-1.72.0.tar.bz2 from http://downloads.sourceforge.net/docbook ---> Verifying checksum(s) for docbook-xsl ---> Extracting docbook-xsl ---> Configuring docbook-xsl ---> Building docbook-xsl with target all ---> Staging docbook-xsl into destroot ---> Installing docbook-xsl 1.72.0_0 ---> Activating docbook-xsl 1.72.0_0 ###################################################################### # As MacPorts does not currently have a post-deactivate hook, # you will need to ensure that you manually remove the catalog # entry for this port when you uninstall it. To do so, run # "xmlcatmgr remove nextCatalog /opt/local/share/xsl/docbook-xsl/catalog.xml". ###################################################################### ---> Cleaning docbook-xsl ---> Fetching libxml2 ---> Attempting to fetch libxml2-2.6.30.tar.gz from http://xmlsoft.org/sources/ ---> Verifying checksum(s) for libxml2 ---> Extracting libxml2 ---> Configuring libxml2 ---> Building libxml2 with target all ---> Staging libxml2 into destroot ---> Installing libxml2 2.6.30_0 ---> Activating libxml2 2.6.30_0 ---> Cleaning libxml2 ---> Fetching docbook-xml-4.2 ---> Attempting to fetch docbook-xml-4.2.zip from http://www.oasis-open.org/docbook/xml/4.2/ ---> Verifying checksum(s) for docbook-xml-4.2 ---> Extracting docbook-xml-4.2 ---> Configuring docbook-xml-4.2 ---> Building docbook-xml-4.2 with target all ---> Staging docbook-xml-4.2 into destroot ---> Installing docbook-xml-4.2 4.2_0 ---> Activating docbook-xml-4.2 4.2_0 ###################################################################### # As MacPorts does not currently have a post-deactivate hook, # you will need to ensure that you manually remove the catalog # entry for this port when you uninstall it. To do so, run # "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.2/catalog.xml". ###################################################################### ---> Cleaning docbook-xml-4.2 ---> Fetching docbook-xml-4.3 ---> Attempting to fetch docbook-xml-4.3.zip from http://www.oasis-open.org/docbook/xml/4.3/ ---> Verifying checksum(s) for docbook-xml-4.3 ---> Extracting docbook-xml-4.3 ---> Configuring docbook-xml-4.3 ---> Building docbook-xml-4.3 with target all ---> Staging docbook-xml-4.3 into destroot ---> Installing docbook-xml-4.3 4.3_0 ---> Activating docbook-xml-4.3 4.3_0 ###################################################################### # As MacPorts does not currently have a post-deactivate hook, # you will need to ensure that you manually remove the catalog # entry for this port when you uninstall it. To do so, run # "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.3/catalog.xml". ###################################################################### ---> Cleaning docbook-xml-4.3 ---> Fetching docbook-xml-4.4 ---> Attempting to fetch docbook-xml-4.4.zip from http://www.oasis-open.org/docbook/xml/4.4/ ---> Verifying checksum(s) for docbook-xml-4.4 ---> Extracting docbook-xml-4.4 ---> Configuring docbook-xml-4.4 ---> Building docbook-xml-4.4 with target all ---> Staging docbook-xml-4.4 into destroot ---> Installing docbook-xml-4.4 4.4_0 ---> Activating docbook-xml-4.4 4.4_0 ###################################################################### # As MacPorts does not currently have a post-deactivate hook, # you will need to ensure that you manually remove the catalog # entry for this port when you uninstall it. To do so, run # "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.4/catalog.xml". ###################################################################### ---> Cleaning docbook-xml-4.4 ---> Fetching docbook-xml-4.5 ---> Attempting to fetch docbook-xml-4.5.zip from http://www.oasis-open.org/docbook/xml/4.5/ ---> Verifying checksum(s) for docbook-xml-4.5 ---> Extracting docbook-xml-4.5 ---> Configuring docbook-xml-4.5 ---> Building docbook-xml-4.5 with target all ---> Staging docbook-xml-4.5 into destroot ---> Installing docbook-xml-4.5 4.5_0 ---> Activating docbook-xml-4.5 4.5_0 ###################################################################### # As MacPorts does not currently have a post-deactivate hook, # you will need to ensure that you manually remove the catalog # entry for this port when you uninstall it. To do so, run # "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.5/catalog.xml". ###################################################################### ---> Cleaning docbook-xml-4.5 ---> Fetching docbook-xml ---> Verifying checksum(s) for docbook-xml ---> Extracting docbook-xml ---> Configuring docbook-xml ---> Building docbook-xml with target all ---> Staging docbook-xml into destroot ---> Installing docbook-xml 4.5_1 ---> Activating docbook-xml 4.5_1 ---> Cleaning docbook-xml ---> Fetching libxslt ---> Attempting to fetch libxslt-1.1.22.tar.gz from ftp://xmlsoft.org/libxslt/ ---> Verifying checksum(s) for libxslt ---> Extracting libxslt ---> Configuring libxslt ---> Building libxslt with target all ---> Staging libxslt into destroot ---> Installing libxslt 1.1.22_0 ---> Activating libxslt 1.1.22_0 ---> Cleaning libxslt ---> Fetching p5-xml-parser ---> Attempting to fetch XML-Parser-2.36.tar.gz from http://ftp.ucr.ac.cr/Unix/CPAN/modules/by-module/XML ---> Verifying checksum(s) for p5-xml-parser ---> Extracting p5-xml-parser ---> Configuring p5-xml-parser ---> Building p5-xml-parser with target all ---> Staging p5-xml-parser into destroot ---> Installing p5-xml-parser 2.36_0 ---> Activating p5-xml-parser 2.36_0 ---> Cleaning p5-xml-parser ---> Fetching scrollkeeper ---> Attempting to fetch scrollkeeper-0.3.14.tar.gz from http://downloads.sourceforge.net/scrollkeeper ---> Verifying checksum(s) for scrollkeeper ---> Extracting scrollkeeper ---> Applying patches to scrollkeeper ---> Configuring scrollkeeper ---> Building scrollkeeper with target all ---> Staging scrollkeeper into destroot ---> Installing scrollkeeper 0.3.14_6 ---> Activating scrollkeeper 0.3.14_6 ---> Cleaning scrollkeeper ---> Fetching gtk-doc ---> Attempting to fetch gtk-doc-1.9.tar.bz2 from http://mandril.creatis.insa-lyon.fr/linux/gnome.org/sources/gtk-doc/1.9/ ---> Verifying checksum(s) for gtk-doc ---> Extracting gtk-doc ---> Configuring gtk-doc ---> Building gtk-doc with target all ---> Staging gtk-doc into destroot ---> Installing gtk-doc 1.9_0 ---> Activating gtk-doc 1.9_0 ---> Cleaning gtk-doc ---> Fetching xorg-util-macros ---> Attempting to fetch util-macros-1.1.5.tar.bz2 from http://www.x.org/pub/individual/util/ ---> Verifying checksum(s) for xorg-util-macros ---> Extracting xorg-util-macros ---> Configuring xorg-util-macros ---> Building xorg-util-macros with target all ---> Staging xorg-util-macros into destroot ---> Installing xorg-util-macros 1.1.5_0 ---> Activating xorg-util-macros 1.1.5_0 ---> Cleaning xorg-util-macros ---> Fetching xorg-xproto ---> Attempting to fetch xproto-7.0.11.tar.bz2 from http://www.x.org/pub/individual/proto/ ---> Verifying checksum(s) for xorg-xproto ---> Extracting xorg-xproto ---> Applying patches to xorg-xproto ---> Configuring xorg-xproto ---> Building xorg-xproto with target all ---> Staging xorg-xproto into destroot ---> Installing xorg-xproto 7.0.11_1 ---> Activating xorg-xproto 7.0.11_1 ---> Cleaning xorg-xproto ---> Fetching Xft2 ---> Attempting to fetch libXft-2.1.12.tar.bz2 from http://xorg.freedesktop.org/releases/individual/lib/ ---> Verifying checksum(s) for Xft2 ---> Extracting Xft2 ---> Configuring Xft2 ---> Building Xft2 with target all ---> Staging Xft2 into destroot ---> Installing Xft2 2.1.12_0 ---> Activating Xft2 2.1.12_0 ---> Cleaning Xft2 ---> Fetching pango ---> Attempting to fetch pango-1.18.3.tar.bz2 from http://mandril.creatis.insa-lyon.fr/linux/gnome.org/sources/pango/1.18 ---> Verifying checksum(s) for pango ---> Extracting pango ---> Applying patches to pango ---> Configuring pango ---> Building pango with target all ---> Staging pango into destroot ---> Installing pango 1.18.3_0 ---> Activating pango 1.18.3_0 ---> Cleaning pango ---> Fetching tiff ---> Attempting to fetch tiff-3.8.2.tar.gz from ftp://ftp.remotesensing.org/pub/libtiff/ ---> Verifying checksum(s) for tiff ---> Extracting tiff ---> Configuring tiff ---> Building tiff with target all ---> Staging tiff into destroot ---> Installing tiff 3.8.2_1+macosx ---> Activating tiff 3.8.2_1+macosx ---> Cleaning tiff ---> Fetching gtk2 ---> Attempting to fetch gtk+-2.12.2.tar.bz2 from http://mandril.creatis.insa-lyon.fr/linux/gnome.org/sources/gtk+/2.12/ ---> Verifying checksum(s) for gtk2 ---> Extracting gtk2 ---> Configuring gtk2 ---> Building gtk2 with target all ---> Staging gtk2 into destroot ---> Installing gtk2 2.12.2_0+x11 ---> Activating gtk2 2.12.2_0+x11 ---> Cleaning gtk2 ---> Fetching libpcap ---> Attempting to fetch libpcap-0.9.8.tar.gz from http://www.tcpdump.org/release/ ---> Verifying checksum(s) for libpcap ---> Extracting libpcap ---> Applying patches to libpcap ---> Configuring libpcap ---> Building libpcap with target all ---> Staging libpcap into destroot ---> Installing libpcap 0.9.8_0 ---> Activating libpcap 0.9.8_0 ---> Cleaning libpcap ---> Fetching wireshark ---> Attempting to fetch wireshark-0.99.7.tar.bz2 from http://www.wireshark.org/download/src/ ---> Verifying checksum(s) for wireshark ---> Extracting wireshark ---> Configuring wireshark ---> Building wireshark with target all ---> Staging wireshark into destroot ---> Installing wireshark 0.99.7_0+darwin_9 ---> Activating wireshark 0.99.7_0+darwin_9 ---> Cleaning wireshark Thanks On Jan 12, 2008 11:40 AM, Ryan wrote: > > On Jan 11, 2008, at 19:21, Greg Hauptmann wrote: > > > I'm on leopard and have performed a successful "sudo port > > selfupdate", however I'm getting an error when performing "sudo > > port install wireshark". The console out is below. > > [snip] > > > ---> Fetching docbook-xml-4.1.2 > > ---> Attempting to fetch docbkx412.zip from http://www.oasis- > > open.org/docbook/xml/4.1.2/ > > ---> Attempting to fetch docbkx412.zip from http:// > > svn.macports.org/repository/macports/distfiles/docbook-xml-4.1.2 > > ---> Attempting to fetch docbkx412.zip from http:// > > svn.macports.org/repository/macports/distfiles/general/ > > ---> Attempting to fetch docbkx412.zip from http:// > > svn.macports.org/repository/macports/downloads/docbook-xml-4.1.2 > > Error: Target org.macports.fetch returned: fetch failed > > Error: The following dependencies failed to build: gtk2 gtk-doc > > docbook-xml-4.1.2 docbook-xsl libxml2 scrollkeeper docbook-xml > > docbook-xml-4.2 docbook-xml-4.3 docbook-xml-4.4 docbook-xml-4.5 > > libxslt p5-xml-parser pango Xft2 xorg-xproto xorg-util-macros tiff > > libpcap > > Error: Status 1 encountered during processing. > > Macintosh:~ greg$ > > So the problem was docbook-xml-4.1.2 couldn't fetch its distfile. It > looks to me like it's still there on their server, so maybe their > server just had a temporary problem. Please try again. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080112/4c0f3019/attachment-0001.html From ryandesign at macports.org Sat Jan 12 00:23:28 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 12 00:23:57 2008 Subject: wireshark install failed? (Attempting to fetch docbkx412.zip from http://svn.macports.org/repository/macports/downloads/docbook-xml-4.1.2) In-Reply-To: References: <82D6D3C7-13B5-4FAD-B600-378337C65701@macports.org> Message-ID: <321D158C-2B53-4341-8A28-87461C3B66F1@macports.org> On Jan 12, 2008, at 02:16, Greg Hauptmann wrote: > I actually get the following error when running wireshark, i.e. > after a few seconds of a capture: > > Macintosh:~ greg$ wireshark --sync > The program 'wireshark' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadMatch (invalid parameter attributes)'. > (Details: serial 50746 error_code 8 request_code 152 minor_code 4) > (Note to programmers: normally, X errors are reported > asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() > function.) > Macintosh:~ greg$ [snip] I searched the issue tracker for tickets with "wireshark" in the summary and found that this has already been reported: http://trac.macosforge.org/projects/macports/ticket/13740 I've added you to the Cc list so you'll be informed of any progress. From msavory1 at nzbox.com Sat Jan 12 01:04:45 2008 From: msavory1 at nzbox.com (Mike Savory) Date: Sat Jan 12 01:04:35 2008 Subject: wireshark install failed? (Attempting to fetch docbkx412.zip from http://svn.macports.org/repository/macports/downloads/docbook-xml-4.1.2) In-Reply-To: <321D158C-2B53-4341-8A28-87461C3B66F1@macports.org> References: <82D6D3C7-13B5-4FAD-B600-378337C65701@macports.org> <321D158C-2B53-4341-8A28-87461C3B66F1@macports.org> Message-ID: Hi Greg I had this problem Upgrading to the latest XQuartz fixed it for me.... http://trac.macosforge.org/projects/xquartz/ see this blog for more info http://www.anders.com/cms/241/Wireshark/MacPorts Cheers Mike On Jan 12, 2008, at 12:23 AM, Ryan Schmidt wrote: > On Jan 12, 2008, at 02:16, Greg Hauptmann wrote: > >> I actually get the following error when running wireshark, i.e. >> after a few seconds of a capture: >> >> Macintosh:~ greg$ wireshark --sync >> The program 'wireshark' received an X Window System error. >> This probably reflects a bug in the program. >> The error was 'BadMatch (invalid parameter attributes)'. >> (Details: serial 50746 error_code 8 request_code 152 minor_code 4) >> (Note to programmers: normally, X errors are reported >> asynchronously; >> that is, you will receive the error a while after causing it. >> To debug your program, run it with the --sync command line >> option to change this behavior. You can then get a meaningful >> backtrace from your debugger if you break on the gdk_x_error() >> function.) >> Macintosh:~ greg$ > > > [snip] > > I searched the issue tracker for tickets with "wireshark" in the > summary and found that this has already been reported: > > http://trac.macosforge.org/projects/macports/ticket/13740 > > I've added you to the Cc list so you'll be informed of any progress. > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > From pguyot at kallisys.net Sat Jan 12 10:28:52 2008 From: pguyot at kallisys.net (Paul Guyot) Date: Sat Jan 12 10:28:20 2008 Subject: Upgrade of imap-uw @2004g_0+darwin_7 fails In-Reply-To: <063FF45F-8F8C-472E-AE0D-F2908B30695B@CentosPrime.COM> References: <34C13CE0-E004-4BA3-9E9C-6CFDF8AF35FB@centosprime.com> <063FF45F-8F8C-472E-AE0D-F2908B30695B@CentosPrime.COM> Message-ID: <1337AEF4-021E-4239-9F4B-0A9F19A1FF31@kallisys.net> Le 11 janv. 08 ? 16:06, Chris Janton a ?crit : > On 2008-01-11 , at 07:39 , Chris Janton wrote: > >> Today's port sync offered that imap-uw was in need of an upgrade. >> >> This was the result on my 10.3.9 server. > > > Note: imap-uw installs cleanly on my 10.4.11 system (Intel) Indeed. I think that now that 10.5 was released, MacPorts only supports 10.4 and 10.5. Besides, imap-uw is officially without any maintainer. Yet, I've just committed a tentative fix. I don't have 10.3, so I cannot tell if it will work. Regards, Paul From ryandesign at macports.org Sat Jan 12 11:32:14 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 12 11:32:44 2008 Subject: Upgrade of imap-uw @2004g_0+darwin_7 fails In-Reply-To: <1337AEF4-021E-4239-9F4B-0A9F19A1FF31@kallisys.net> References: <34C13CE0-E004-4BA3-9E9C-6CFDF8AF35FB@centosprime.com> <063FF45F-8F8C-472E-AE0D-F2908B30695B@CentosPrime.COM> <1337AEF4-021E-4239-9F4B-0A9F19A1FF31@kallisys.net> Message-ID: <3B6ACA4E-28E0-49FD-B2D9-824504133FDD@macports.org> On Jan 12, 2008, at 12:28, Paul Guyot wrote: > Le 11 janv. 08 ? 16:06, Chris Janton a ?crit : > >> On 2008-01-11 , at 07:39 , Chris Janton wrote: >> >>> Today's port sync offered that imap-uw was in need of an upgrade. >>> >>> This was the result on my 10.3.9 server. >> >> Note: imap-uw installs cleanly on my 10.4.11 system (Intel) > > Indeed. I think that now that 10.5 was released, MacPorts only > supports 10.4 and 10.5. Besides, imap-uw is officially without any > maintainer. We've just had a big long thread on the list about getting MacPorts 1.6.0 to compile on Mac OS X 10.3, and the 10.3 disk image for MacPorts 1.6.0 is now available. As far as I'm concerned, MacPorts needs to still support Mac OS X 10.3. > Yet, I've just committed a tentative fix. I don't have 10.3, so I > cannot tell if it will work. Thanks. From jochen at fhi-berlin.mpg.de Sat Jan 12 12:12:31 2008 From: jochen at fhi-berlin.mpg.de (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Sat Jan 12 12:12:28 2008 Subject: [MacPorts] #13894: checksum mismatch for molden In-Reply-To: <049.96d6ef60d2ef5eff074a57be992be0e4@macosforge.org> References: <049.96d6ef60d2ef5eff074a57be992be0e4@macosforge.org> Message-ID: <65E50EF4-8DDC-4403-8EB9-D80E9F4A8B11@fhi-berlin.mpg.de> solved in r32732 However, I cannot close the ticket because Safari constantly crashes after login... On 11.01.2008, at 20:35, MacPorts wrote: > #13894: checksum mismatch for molden > --------------------------------- > +------------------------------------------ > Reporter: jaeger@ccqc.uga.edu | Owner: macports-tickets@lists.macosforge.org > Type: defect | Status: new > Priority: Normal | Milestone: Port Bugs > Component: ports | Version: 1.6.0 > Keywords: molden | > --------------------------------- > +------------------------------------------ > I am trying to install molden 4.6 and have encountered the checksum > error[[BR]] > > Here are the results: > > > ======================================================[[BR]] > > Error: Checksum (md5) mismatch for molden4.6.tar.gz[[BR]] > > Portfile checksum: molden4.6.tar.gz md5 > f2d929fe96ab85a3f994557140f5dcbe[[BR]] > > Distfile checksum: molden4.6.tar.gz md5 > 51c69eb6c4e21ab5e906019f8bfb4655[[BR]] > > Error: Checksum (sha1) mismatch for molden4.6.tar.gz[[BR]] > > Portfile checksum: molden4.6.tar.gz sha1 > 04cc6e32c1c8a79e54c02cfacdcddee4a64d08dc[[BR]] > > Distfile checksum: molden4.6.tar.gz sha1 > 68266e7be08833c41e9724dcc49a00f04c4d26f6[[BR]] > > Error: Checksum (rmd160) mismatch for molden4.6.tar.gz[[BR]] > > Portfile checksum: molden4.6.tar.gz rmd160 > f11735e616afb7e6de7bd94bc8782068a9fb47bf[[BR]] > > Distfile checksum: molden4.6.tar.gz rmd160 > 9b1f9c268251d43fa36018b18a4dfabe27663d60[[BR]] > > Error: Target org.macports.checksum returned: Unable to verify file > checksums[[BR]] > > =============================================================[[BR]] > > > > > I have updated Macports with selfupdate and sync to no avail.[[BR]] > > > your help is much appreciated > > -- > Ticket URL: 13894> > MacPorts > Ports system for Mac OS Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080112/0d69722b/PGP.bin From matrixm at gmail.com Sat Jan 12 15:58:21 2008 From: matrixm at gmail.com (Matrix Mole) Date: Sat Jan 12 15:58:08 2008 Subject: compiler cannot create executables error Message-ID: <4789541D.4080507@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was attempting to install pwsafe and during the config process it errors out with "checking for C compiler default output... configure: error: C compiler cannot create executable" is this a problem with the config script of the program, or with my compiler? Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHiVQcNtosHRPp48MRAil0AJsHayIoZKzfzgz3WdVGam/2MhisigCfYxUB Mk2sp1hTwsHdkokpSFz7Ig0= =lZQ0 -----END PGP SIGNATURE----- From jberry at macports.org Sat Jan 12 16:18:39 2008 From: jberry at macports.org (James Berry) Date: Sat Jan 12 16:18:31 2008 Subject: Upgrade of imap-uw @2004g_0+darwin_7 fails In-Reply-To: <3B6ACA4E-28E0-49FD-B2D9-824504133FDD@macports.org> References: <34C13CE0-E004-4BA3-9E9C-6CFDF8AF35FB@centosprime.com> <063FF45F-8F8C-472E-AE0D-F2908B30695B@CentosPrime.COM> <1337AEF4-021E-4239-9F4B-0A9F19A1FF31@kallisys.net> <3B6ACA4E-28E0-49FD-B2D9-824504133FDD@macports.org> Message-ID: On Jan 12, 2008, at 11:32 AM, Ryan Schmidt wrote: > We've just had a big long thread on the list about getting MacPorts > 1.6.0 to compile on Mac OS X 10.3, and the 10.3 disk image for > MacPorts 1.6.0 is now available. As far as I'm concerned, MacPorts > needs to still support Mac OS X 10.3. Officially, MacPorts supports 10.4 and 10.5 (the current OS release, and the previous release). That means that maintainers may not choose to go to extreme lengths to fix issues on earlier releases. That said, we also don't want to stand in the way of having things continue to work on 10.3; it's up to maintainers to decide how much effort to go to in order to do so. Some may want to apply patches for 10.3, and some may not. The current attitude is to put some effort into keeping things running on 10.3, which I think is positive. But I don't want to edge into a situation where we have, in all cases, to continue to support older releases; that would negate the very valid reasons that this policy was implemented in the first place. James From rsync at reifferscheid.org Sat Jan 12 16:49:44 2008 From: rsync at reifferscheid.org (Thomas Reifferscheid) Date: Sat Jan 12 16:49:36 2008 Subject: Fail to install Pidgin 2.3.1 on Leopard 10.5.1 with Macports 1.6.0 In-Reply-To: <383882.85512.qm@web30213.mail.mud.yahoo.com> References: <383882.85512.qm@web30213.mail.mud.yahoo.com> Message-ID: <47896028.7030403@reifferscheid.org> Hi, please run the following commands: sudo port sync sudo port -d install pidgin and show us what comes out. Kind regards Thomas Reifferscheid fas fdas wrote: > I run the command > > sudo port install pidgin > > it run few mins then show error. > > Error: The following dependencies failed to build: gnutls libgcrypt > libgpg-error gettext ncurses ncursesw gawk opencdk readline gtk2 atk > glib2 gtk-doc scrollkeeper pango > > then run sudo port -d install pidgin > > skyneede-macbook:~ skynee$ sudo port -d install pidgin > Password: > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/net/pidgin > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/net/pidgin > DEBUG: Requested variant darwin is not provided by port pidgin. > DEBUG: Requested variant i386 is not provided by port pidgin. > DEBUG: Requested variant macosx is not provided by port pidgin. > DEBUG: Executing variant msn provides msn > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/gtk2 > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/gtk2 > DEBUG: Requested variant darwin is not provided by port gtk2. > DEBUG: Requested variant i386 is not provided by port gtk2. > DEBUG: Requested variant macosx is not provided by port gtk2. > DEBUG: Executing variant x11 provides x11 > DEBUG: Searching for dependency: gtk2 > DEBUG: Didn't find receipt, going to depspec regex for: gtk2 > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/audio/libao > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/audio/libao > DEBUG: Requested variant i386 is not provided by port libao. > DEBUG: Requested variant macosx is not provided by port libao. > DEBUG: Executing variant darwin provides darwin > DEBUG: Searching for dependency: libao > DEBUG: Found Dependency: receipt exists for libao > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/audio/audiofile > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/audio/audiofile > DEBUG: Requested variant darwin is not provided by port audiofile. > DEBUG: Requested variant i386 is not provided by port audiofile. > DEBUG: Requested variant macosx is not provided by port audiofile. > DEBUG: Searching for dependency: audiofile > DEBUG: Found Dependency: receipt exists for audiofile > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/perl/p5-xml-parser > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/perl/p5-xml-parser > DEBUG: Requested variant darwin is not provided by port p5-xml-parser. > DEBUG: Requested variant i386 is not provided by port p5-xml-parser. > DEBUG: Requested variant macosx is not provided by port p5-xml-parser. > DEBUG: Searching for dependency: p5-xml-parser > DEBUG: Found Dependency: receipt exists for p5-xml-parser > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libxml2 > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libxml2 > DEBUG: Requested variant darwin is not provided by port libxml2. > DEBUG: Requested variant i386 is not provided by port libxml2. > DEBUG: Requested variant macosx is not provided by port libxml2. > DEBUG: Searching for dependency: libxml2 > DEBUG: Found Dependency: receipt exists for libxml2 > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gnutls > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gnutls > DEBUG: Requested variant darwin is not provided by port gnutls. > DEBUG: Requested variant i386 is not provided by port gnutls. > DEBUG: Requested variant macosx is not provided by port gnutls. > DEBUG: Searching for dependency: gnutls > DEBUG: Didn't find receipt, going to depspec regex for: gnutls > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/cairo > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/cairo > DEBUG: Requested variant darwin is not provided by port cairo. > DEBUG: Requested variant i386 is not provided by port cairo. > DEBUG: Requested variant macosx is not provided by port cairo. > DEBUG: Searching for dependency: cairo > DEBUG: Found Dependency: receipt exists for cairo > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/fontconfig > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/fontconfig > DEBUG: Requested variant darwin is not provided by port fontconfig. > DEBUG: Requested variant i386 is not provided by port fontconfig. > DEBUG: Executing variant macosx provides macosx > DEBUG: Searching for dependency: fontconfig > DEBUG: Found Dependency: receipt exists for fontconfig > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/print/freetype > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/print/freetype > DEBUG: Requested variant darwin is not provided by port freetype. > DEBUG: Requested variant i386 is not provided by port freetype. > DEBUG: Requested variant macosx is not provided by port freetype. > DEBUG: Searching for dependency: freetype > DEBUG: Found Dependency: receipt exists for freetype > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/glib2 > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/glib2 > DEBUG: Requested variant darwin is not provided by port glib2. > DEBUG: Requested variant i386 is not provided by port glib2. > DEBUG: Requested variant macosx is not provided by port glib2. > DEBUG: Executing variant darwin_9 provides darwin_9 > DEBUG: Searching for dependency: glib2 > DEBUG: Didn't find receipt, going to depspec regex for: glib2 > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/jpeg > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/jpeg > DEBUG: Requested variant darwin is not provided by port jpeg. > DEBUG: Requested variant i386 is not provided by port jpeg. > DEBUG: Requested variant macosx is not provided by port jpeg. > DEBUG: Searching for dependency: jpeg > DEBUG: Found Dependency: receipt exists for jpeg > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/tiff > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/tiff > DEBUG: Requested variant darwin is not provided by port tiff. > DEBUG: Requested variant i386 is not provided by port tiff. > DEBUG: Executing variant macosx provides macosx > DEBUG: Searching for dependency: tiff > DEBUG: Found Dependency: receipt exists for tiff > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv > DEBUG: Requested variant darwin is not provided by port libiconv. > DEBUG: Requested variant i386 is not provided by port libiconv. > DEBUG: Requested variant macosx is not provided by port libiconv. > DEBUG: Searching for dependency: libiconv > DEBUG: Found Dependency: receipt exists for libiconv > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/libpng > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/libpng > DEBUG: Requested variant darwin is not provided by port libpng. > DEBUG: Requested variant i386 is not provided by port libpng. > DEBUG: Requested variant macosx is not provided by port libpng. > DEBUG: Searching for dependency: libpng > DEBUG: Found Dependency: receipt exists for libpng > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/atk > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/atk > DEBUG: Requested variant darwin is not provided by port atk. > DEBUG: Requested variant i386 is not provided by port atk. > DEBUG: Requested variant macosx is not provided by port atk. > DEBUG: Searching for dependency: atk > DEBUG: Didn't find receipt, going to depspec regex for: atk > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/pango > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/pango > DEBUG: Requested variant darwin is not provided by port pango. > DEBUG: Requested variant i386 is not provided by port pango. > DEBUG: Requested variant macosx is not provided by port pango. > DEBUG: Searching for dependency: pango > DEBUG: Didn't find receipt, going to depspec regex for: pango > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext > DEBUG: Requested variant darwin is not provided by port gettext. > DEBUG: Requested variant i386 is not provided by port gettext. > DEBUG: Requested variant macosx is not provided by port gettext. > DEBUG: Searching for dependency: gettext > DEBUG: Didn't find receipt, going to depspec regex for: gettext > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/render > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/render > DEBUG: Requested variant darwin is not provided by port render. > DEBUG: Requested variant i386 is not provided by port render. > DEBUG: Requested variant macosx is not provided by port render. > DEBUG: Searching for dependency: render > DEBUG: Found Dependency: receipt exists for render > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/archivers/zlib > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/archivers/zlib > DEBUG: Requested variant darwin is not provided by port zlib. > DEBUG: Requested variant i386 is not provided by port zlib. > DEBUG: Requested variant macosx is not provided by port zlib. > DEBUG: Searching for dependency: zlib > DEBUG: Found Dependency: receipt exists for zlib > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xrender > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xrender > DEBUG: Requested variant darwin is not provided by port xrender. > DEBUG: Requested variant i386 is not provided by port xrender. > DEBUG: Requested variant macosx is not provided by port xrender. > DEBUG: Searching for dependency: xrender > DEBUG: Found Dependency: receipt exists for xrender > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xorg > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/xorg > DEBUG: Requested variant i386 is not provided by port xorg. > DEBUG: Requested variant macosx is not provided by port xorg. > DEBUG: Executing variant darwin provides darwin > DEBUG: Searching for dependency: xorg > DEBUG: Didn't find receipt, going to depspec regex for: xorg > DEBUG: Found Dependency: path: /usr/X11R6/lib filename: libX11.6.dylib > regex: ^libX11\.6\.dylib$ > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/gtk-doc > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/gtk-doc > DEBUG: Requested variant darwin is not provided by port gtk-doc. > DEBUG: Requested variant i386 is not provided by port gtk-doc. > DEBUG: Requested variant macosx is not provided by port gtk-doc. > DEBUG: Searching for dependency: gtk-doc > DEBUG: Didn't find receipt, going to depspec regex for: gtk-doc > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pkgconfig > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pkgconfig > DEBUG: Requested variant darwin is not provided by port pkgconfig. > DEBUG: Requested variant i386 is not provided by port pkgconfig. > DEBUG: Requested variant macosx is not provided by port pkgconfig. > DEBUG: Searching for dependency: pkgconfig > DEBUG: Found Dependency: receipt exists for pkgconfig > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext > DEBUG: Searching for dependency: gettext > DEBUG: Didn't find receipt, going to depspec regex for: gettext > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv > DEBUG: Searching for dependency: libiconv > DEBUG: Found Dependency: receipt exists for libiconv > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pkgconfig > DEBUG: Searching for dependency: pkgconfig > DEBUG: Found Dependency: receipt exists for pkgconfig > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/glib2 > DEBUG: Searching for dependency: glib2 > DEBUG: Didn't find receipt, going to depspec regex for: glib2 > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext > DEBUG: Searching for dependency: gettext > DEBUG: Didn't find receipt, going to depspec regex for: gettext > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv > DEBUG: Searching for dependency: libiconv > DEBUG: Found Dependency: receipt exists for libiconv > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pkgconfig > DEBUG: Searching for dependency: pkgconfig > DEBUG: Found Dependency: receipt exists for pkgconfig > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/glib2 > DEBUG: Searching for dependency: glib2 > DEBUG: Didn't find receipt, going to depspec regex for: glib2 > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/XFree86 > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/XFree86 > DEBUG: Requested variant i386 is not provided by port XFree86. > DEBUG: Executing variant darwin provides darwin > DEBUG: Executing variant macosx provides macosx > DEBUG: Searching for dependency: XFree86 > DEBUG: Didn't find receipt, going to depspec regex for: XFree86 > DEBUG: Found Dependency: path: /usr/X11R6/lib filename: libX11.6.dylib > regex: ^libX11\.6\.dylib$ > DEBUG: Found Dependency: path: /usr/X11R6/lib filename: libX11.6.dylib > regex: ^libX11\.6\.dylib$ > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/Xft2 > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/Xft2 > DEBUG: Requested variant darwin is not provided by port Xft2. > DEBUG: Requested variant i386 is not provided by port Xft2. > DEBUG: Requested variant macosx is not provided by port Xft2. > DEBUG: Searching for dependency: Xft2 > DEBUG: Found Dependency: receipt exists for Xft2 > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/cairo > DEBUG: Searching for dependency: cairo > DEBUG: Found Dependency: receipt exists for cairo > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/fontconfig > DEBUG: Searching for dependency: fontconfig > DEBUG: Found Dependency: receipt exists for fontconfig > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv > DEBUG: Searching for dependency: libiconv > DEBUG: Found Dependency: receipt exists for libiconv > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncurses > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncurses > DEBUG: Requested variant darwin is not provided by port ncurses. > DEBUG: Requested variant i386 is not provided by port ncurses. > DEBUG: Requested variant macosx is not provided by port ncurses. > DEBUG: Searching for dependency: ncurses > DEBUG: Didn't find receipt, going to depspec regex for: ncurses > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/expat > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/expat > DEBUG: Requested variant darwin is not provided by port expat. > DEBUG: Requested variant i386 is not provided by port expat. > DEBUG: Requested variant macosx is not provided by port expat. > DEBUG: Searching for dependency: expat > DEBUG: Found Dependency: receipt exists for expat > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncursesw > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncursesw > DEBUG: Requested variant darwin is not provided by port ncursesw. > DEBUG: Requested variant i386 is not provided by port ncursesw. > DEBUG: Requested variant macosx is not provided by port ncursesw. > DEBUG: Executing variant darwin_9 provides darwin_9 > DEBUG: Searching for dependency: ncursesw > DEBUG: Didn't find receipt, going to depspec regex for: ncursesw > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/gawk > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/gawk > DEBUG: Requested variant darwin is not provided by port gawk. > DEBUG: Requested variant i386 is not provided by port gawk. > DEBUG: Requested variant macosx is not provided by port gawk. > DEBUG: Searching for dependency: gawk > DEBUG: Didn't find receipt, going to depspec regex for: gawk > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv > DEBUG: Searching for dependency: libiconv > DEBUG: Found Dependency: receipt exists for libiconv > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext > DEBUG: Searching for dependency: gettext > DEBUG: Didn't find receipt, going to depspec regex for: gettext > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/docbook-xml-4.1.2 > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/docbook-xml-4.1.2 > DEBUG: Requested variant darwin is not provided by port docbook-xml-4.1.2. > DEBUG: Requested variant i386 is not provided by port docbook-xml-4.1.2. > DEBUG: Requested variant macosx is not provided by port docbook-xml-4.1.2. > DEBUG: Searching for dependency: docbook-xml-4.1.2 > DEBUG: Found Dependency: receipt exists for docbook-xml-4.1.2 > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/docbook-xsl > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/docbook-xsl > DEBUG: Requested variant darwin is not provided by port docbook-xsl. > DEBUG: Requested variant i386 is not provided by port docbook-xsl. > DEBUG: Requested variant macosx is not provided by port docbook-xsl. > DEBUG: Searching for dependency: docbook-xsl > DEBUG: Found Dependency: receipt exists for docbook-xsl > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libxml2 > DEBUG: Searching for dependency: libxml2 > DEBUG: Found Dependency: receipt exists for libxml2 > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/scrollkeeper > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/scrollkeeper > DEBUG: Requested variant darwin is not provided by port scrollkeeper. > DEBUG: Requested variant i386 is not provided by port scrollkeeper. > DEBUG: Requested variant macosx is not provided by port scrollkeeper. > DEBUG: Searching for dependency: scrollkeeper > DEBUG: Didn't find receipt, going to depspec regex for: scrollkeeper > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pkgconfig > DEBUG: Searching for dependency: pkgconfig > DEBUG: Found Dependency: receipt exists for pkgconfig > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5.8 > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5.8 > DEBUG: Requested variant i386 is not provided by port perl5.8. > DEBUG: Requested variant macosx is not provided by port perl5.8. > DEBUG: Executing variant darwin provides darwin > DEBUG: Searching for dependency: perl5.8 > DEBUG: Found Dependency: receipt exists for perl5.8 > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libxslt > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libxslt > DEBUG: Requested variant darwin is not provided by port libxslt. > DEBUG: Requested variant i386 is not provided by port libxslt. > DEBUG: Requested variant macosx is not provided by port libxslt. > DEBUG: Searching for dependency: libxslt > DEBUG: Found Dependency: receipt exists for libxslt > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libxml2 > DEBUG: Searching for dependency: libxml2 > DEBUG: Found Dependency: receipt exists for libxml2 > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext > DEBUG: Searching for dependency: gettext > DEBUG: Didn't find receipt, going to depspec regex for: gettext > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv > DEBUG: Searching for dependency: libiconv > DEBUG: Found Dependency: receipt exists for libiconv > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pkgconfig > DEBUG: Searching for dependency: pkgconfig > DEBUG: Found Dependency: receipt exists for pkgconfig > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5.8 > DEBUG: Searching for dependency: perl5.8 > DEBUG: Found Dependency: receipt exists for perl5.8 > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/perl/p5-xml-parser > DEBUG: Searching for dependency: p5-xml-parser > DEBUG: Found Dependency: receipt exists for p5-xml-parser > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/docbook-xsl > DEBUG: Searching for dependency: docbook-xsl > DEBUG: Found Dependency: receipt exists for docbook-xsl > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/docbook-xml > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/docbook-xml > DEBUG: Requested variant darwin is not provided by port docbook-xml. > DEBUG: Requested variant i386 is not provided by port docbook-xml. > DEBUG: Requested variant macosx is not provided by port docbook-xml. > DEBUG: Searching for dependency: docbook-xml > DEBUG: Found Dependency: receipt exists for docbook-xml > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/libgcrypt > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/libgcrypt > DEBUG: Requested variant darwin is not provided by port libgcrypt. > DEBUG: Requested variant i386 is not provided by port libgcrypt. > DEBUG: Requested variant macosx is not provided by port libgcrypt. > DEBUG: Searching for dependency: libgcrypt > DEBUG: Didn't find receipt, going to depspec regex for: libgcrypt > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/libtasn1 > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/libtasn1 > DEBUG: Requested variant darwin is not provided by port libtasn1. > DEBUG: Requested variant i386 is not provided by port libtasn1. > DEBUG: Requested variant macosx is not provided by port libtasn1. > DEBUG: Searching for dependency: libtasn1 > DEBUG: Found Dependency: receipt exists for libtasn1 > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/opencdk > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/opencdk > DEBUG: Requested variant darwin is not provided by port opencdk. > DEBUG: Requested variant i386 is not provided by port opencdk. > DEBUG: Requested variant macosx is not provided by port opencdk. > DEBUG: Searching for dependency: opencdk > DEBUG: Didn't find receipt, going to depspec regex for: opencdk > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/lzo > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/lzo > DEBUG: Requested variant darwin is not provided by port lzo. > DEBUG: Requested variant i386 is not provided by port lzo. > DEBUG: Requested variant macosx is not provided by port lzo. > DEBUG: Searching for dependency: lzo > DEBUG: Found Dependency: receipt exists for lzo > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/archivers/zlib > DEBUG: Searching for dependency: zlib > DEBUG: Found Dependency: receipt exists for zlib > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/readline > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/readline > DEBUG: Requested variant i386 is not provided by port readline. > DEBUG: Requested variant macosx is not provided by port readline. > DEBUG: Executing variant darwin provides darwin > DEBUG: Executing variant darwin_9 provides darwin_9 > DEBUG: Searching for dependency: readline > DEBUG: Didn't find receipt, going to depspec regex for: readline > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/libgpg-error > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/libgpg-error > DEBUG: Requested variant darwin is not provided by port libgpg-error. > DEBUG: Requested variant i386 is not provided by port libgpg-error. > DEBUG: Requested variant macosx is not provided by port libgpg-error. > DEBUG: Searching for dependency: libgpg-error > DEBUG: Didn't find receipt, going to depspec regex for: libgpg-error > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv > DEBUG: Searching for dependency: libiconv > DEBUG: Found Dependency: receipt exists for libiconv > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext > DEBUG: Searching for dependency: gettext > DEBUG: Didn't find receipt, going to depspec regex for: gettext > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv > DEBUG: Searching for dependency: libiconv > DEBUG: Found Dependency: receipt exists for libiconv > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncurses > DEBUG: Searching for dependency: ncurses > DEBUG: Didn't find receipt, going to depspec regex for: ncurses > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/expat > DEBUG: Searching for dependency: expat > DEBUG: Found Dependency: receipt exists for expat > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncursesw > DEBUG: Searching for dependency: ncursesw > DEBUG: Didn't find receipt, going to depspec regex for: ncursesw > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/gawk > DEBUG: Searching for dependency: gawk > DEBUG: Didn't find receipt, going to depspec regex for: gawk > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv > DEBUG: Searching for dependency: libiconv > DEBUG: Found Dependency: receipt exists for libiconv > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext > DEBUG: Searching for dependency: gettext > DEBUG: Didn't find receipt, going to depspec regex for: gettext > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/libgcrypt > DEBUG: Searching for dependency: libgcrypt > DEBUG: Didn't find receipt, going to depspec regex for: libgcrypt > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/archivers/zlib > DEBUG: Searching for dependency: zlib > DEBUG: Found Dependency: receipt exists for zlib > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncurses > DEBUG: Searching for dependency: ncurses > DEBUG: Didn't find receipt, going to depspec regex for: ncurses > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncursesw > DEBUG: Searching for dependency: ncursesw > DEBUG: Didn't find receipt, going to depspec regex for: ncursesw > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/gawk > DEBUG: Searching for dependency: gawk > DEBUG: Didn't find receipt, going to depspec regex for: gawk > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv > DEBUG: Searching for dependency: libiconv > DEBUG: Found Dependency: receipt exists for libiconv > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext > DEBUG: Searching for dependency: gettext > DEBUG: Didn't find receipt, going to depspec regex for: gettext > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv > DEBUG: Searching for dependency: libiconv > DEBUG: Found Dependency: receipt exists for libiconv > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncurses > DEBUG: Searching for dependency: ncurses > DEBUG: Didn't find receipt, going to depspec regex for: ncurses > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/expat > DEBUG: Searching for dependency: expat > DEBUG: Found Dependency: receipt exists for expat > Error: The following dependencies failed to build: gnutls libgcrypt > libgpg-error gettext ncurses ncursesw gawk opencdk readline gtk2 atk > glib2 gtk-doc scrollkeeper pango > Error: Status 1 encountered during processing. > > > What is the problem? My system is Leopard 10.5.1 with Macports 1.6.0 > > Thank you > > Andy > > > > ------------------------------------------------------------------------ > ??Yahoo! Mail?2008??????????????? *iPod Touch*! *? > ???* From george at galis.org Sat Jan 12 16:55:37 2008 From: george at galis.org (George Georgalis) Date: Sat Jan 12 16:55:20 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <39221154-7E02-4B07-B502-70C541431AB2@macports.org> References: <20080107144937.GD3137@run.duo> <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> <20080108021026.GB29114@run.duo> <4043C306-98FB-4F49-B6F7-6AECA57606C0@macports.org> <20080108043025.GD29114@run.duo> <451EBF42-377F-4ACB-80F8-9D9368945BB9@macports.org> <20080108170558.GH29114@run.duo> <20080109061239.GA14541@run.duo> <39221154-7E02-4B07-B502-70C541431AB2@macports.org> Message-ID: <20080113005537.GE13860@run.duo> On Wed, Jan 09, 2008 at 05:07:12PM -0600, Ryan Schmidt wrote: > > On Jan 9, 2008, at 00:12, George Georgalis wrote: > >> Well I get the same missing expat problem, with Xcode 2.5 I'm >> tempted to make a symlink to /usr/local/MacPorts from /opt/local >> but I'd really like to get this figured out vs just make it work. > > I don't know why it happens yet, but I have been able to reproduce your > problem so I filed a ticket. > > http://trac.macosforge.org/projects/macports/ticket/13885 > resolution confirmed, your patch in macports works as expected, thanks! // George -- George Georgalis, information system scientist < From ryandesign at macports.org Sat Jan 12 17:46:21 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 12 17:46:48 2008 Subject: finding expat Re: problem building gnupod In-Reply-To: <20080113005537.GE13860@run.duo> References: <20080107144937.GD3137@run.duo> <0B6F001E-B5BD-4F60-88EF-B45CCFE5552F@macports.org> <20080108021026.GB29114@run.duo> <4043C306-98FB-4F49-B6F7-6AECA57606C0@macports.org> <20080108043025.GD29114@run.duo> <451EBF42-377F-4ACB-80F8-9D9368945BB9@macports.org> <20080108170558.GH29114@run.duo> <20080109061239.GA14541@run.duo> <39221154-7E02-4B07-B502-70C541431AB2@macports.org> <20080113005537.GE13860@run.duo> Message-ID: <906FD1A1-DA3A-46A2-A6D5-BB78AD7AEEDE@macports.org> On Jan 12, 2008, at 18:55, George Georgalis wrote: > On Wed, Jan 09, 2008 at 05:07:12PM -0600, Ryan Schmidt wrote: > >> On Jan 9, 2008, at 00:12, George Georgalis wrote: >> >>> Well I get the same missing expat problem, with Xcode 2.5 I'm >>> tempted to make a symlink to /usr/local/MacPorts from /opt/local >>> but I'd really like to get this figured out vs just make it work. >> >> I don't know why it happens yet, but I have been able to reproduce >> your >> problem so I filed a ticket. >> >> http://trac.macosforge.org/projects/macports/ticket/13885 > > resolution confirmed, your patch in macports works as expected, > thanks! Great! Thanks for reporting the problem and working through it with us until it was resolved. From ryandesign at macports.org Sat Jan 12 17:57:24 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 12 17:57:50 2008 Subject: compiler cannot create executables error In-Reply-To: <4789541D.4080507@gmail.com> References: <4789541D.4080507@gmail.com> Message-ID: <755C0A1F-B176-4054-A469-840B5757C2B1@macports.org> On Jan 12, 2008, at 17:58, Matrix Mole wrote: > I was attempting to install pwsafe and during the config process it > errors out with "checking for C compiler default output... configure: > error: C compiler cannot create executable" is this a problem with the > config script of the program, or with my compiler? Looks like a problem with the port. I filed a bug, and I'll see if I can do anything about it: http://trac.macosforge.org/projects/macports/ticket/13902 From matrixm at gmail.com Sat Jan 12 18:29:00 2008 From: matrixm at gmail.com (Matrix Mole) Date: Sat Jan 12 18:28:45 2008 Subject: compiler cannot create executables error In-Reply-To: <755C0A1F-B176-4054-A469-840B5757C2B1@macports.org> References: <4789541D.4080507@gmail.com> <755C0A1F-B176-4054-A469-840B5757C2B1@macports.org> Message-ID: <4789776C.8030602@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ryan Schmidt wrote: | On Jan 12, 2008, at 17:58, Matrix Mole wrote: | |> I was attempting to install pwsafe and during the config process it |> errors out with "checking for C compiler default output... configure: |> error: C compiler cannot create executable" is this a problem with the |> config script of the program, or with my compiler? | | Looks like a problem with the port. I filed a bug, and I'll see if I can | do anything about it: | | http://trac.macosforge.org/projects/macports/ticket/13902 Thank you for creating the ticket, I wasn't sure if I'd actually found a bug yet or not. It looks like the ticket was already updated and resolved. I'll wait about 45 minutes then re-synch my port tree and try the install again. Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHiXdsNtosHRPp48MRAlsqAJ4jIe+IYtCGYCZtM50UtpTn1mikVgCglsq+ MVHRnkcN217HiW9GpuTJb0Q= =B4Bc -----END PGP SIGNATURE----- From brian at brian-hunter.com Sat Jan 12 20:55:10 2008 From: brian at brian-hunter.com (brian hunter) Date: Sat Jan 12 20:54:51 2008 Subject: perl-5.8.8.tar.bz2 checksum mismatch Message-ID: Help! Anyone know how to get around this? This is after I manually downloaded the archive and stuck it in /opt/local/var/macports/ distfiles/perl5.8/ because I was getting the 'fetch failed' error. Sorry, I'm a bit of a newb. brian brian@brian-hunter.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080112/654bf1c5/attachment.html From ryandesign at macports.org Sat Jan 12 21:15:28 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 12 21:15:55 2008 Subject: perl-5.8.8.tar.bz2 checksum mismatch In-Reply-To: References: Message-ID: On Jan 12, 2008, at 22:55, brian hunter wrote: > Help! Anyone know how to get around this? This is after I manually > downloaded the archive and stuck it in /opt/local/var/macports/ > distfiles/perl5.8/ because I was getting the 'fetch failed' error. > Sorry, I'm a bit of a newb. Then probably the archive you fetched is not the one the maintainer of the port was expecting to find. Your archive probably differs in subtle (or possible non-subtle) ways from the correct archive. Where did you get it from? I too get a fetch error for perl5.8. It seems many files are missing from the CPAN server. I'll file a ticket and see what I can do about it: http://trac.macosforge.org/projects/macports/ticket/13903 From dersh at alum.mit.edu Sat Jan 12 22:27:24 2008 From: dersh at alum.mit.edu (Adam Dershowitz) Date: Sat Jan 12 22:27:09 2008 Subject: py25-gobject py-gtk fail on 10.5 Message-ID: <5D5E0CE9-18BB-42F7-8F61-D9940EF43472@alum.mit.edu> I recently upgraded to Leopard. I use gimp from Macports and it depends on py25-gobject and py25-gtk. Recently both of these were updated on macports from 2.14.0_0 to 2.14.0_1 and 2.12.0_0 to 2.12.0_1 respectively. When I tried to do this upgrades they failed. I then tried to do an uninstall -f of these because in the past I have run into problem with old ports confusing upgrades with a few other ports (I realized after the fact that I should have just done deactivate...oh well). Now I get errors if I try to install either the older or newer versions. I get similar errors for both of the builds. No one is listed as the maintainer for these, so I am not sure who might be able to help, but any suggestions would be appreciated. Has anyone managed to get these to build under 10.5.1? Thanks, Here is what I see for gobject: sudo port clean --all py25-gobject @2.14.0_1 ---> Cleaning py25-gobject macintosh$ sudo port install py25-gobject ---> Fetching py25-gobject ---> Attempting to fetch pygobject-2.14.0.tar.bz2 from http://mandril.creatis.insa-lyon.fr/linux/gnome.org/sources/pygobject/2.14/ ---> Verifying checksum(s) for py25-gobject ---> Extracting py25-gobject ---> Configuring py25-gobject ---> Building py25-gobject with target all Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_python_py25-gobject/work/pygobject-2.14.0" && make all " returned error 2 Command output: /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/ local/include/python2.5 -I/opt/local/include/python2.5 -D_REENTRANT -I/ opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/ local/include -DPY_SSIZE_T_CLEAN -I/opt/local/include -D_REENTRANT -I/ opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/ local/include -O2 -Wall -fno-strict-aliasing -std=c9x -MT _gobject_la- pygiochannel.lo -MD -MP -MF .deps/_gobject_la-pygiochannel.Tpo -c pygiochannel.c -fno-common -DPIC -o .libs/_gobject_la-pygiochannel.o if /bin/sh ../libtool --mode=compile /usr/bin/gcc-4.0 -DHAVE_CONFIG_H - I. -I. -I.. -I/opt/local/include/python2.5 -I/opt/local/include/ python2.5 -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/lib/ glib-2.0/include -I/opt/local/include -DPY_SSIZE_T_CLEAN -I/opt/ local/include -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/ lib/glib-2.0/include -I/opt/local/include -O2 -Wall -fno-strict- aliasing -std=c9x -MT _gobject_la-pygsource.lo -MD -MP -MF ".deps/ _gobject_la-pygsource.Tpo" -c -o _gobject_la-pygsource.lo `test -f 'pygsource.c' || echo './'`pygsource.c; \ then mv -f ".deps/_gobject_la-pygsource.Tpo" ".deps/_gobject_la- pygsource.Plo"; else rm -f ".deps/_gobject_la-pygsource.Tpo"; exit 1; fi /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/local/include/ python2.5 -I/opt/local/include/python2.5 -D_REENTRANT -I/opt/local/ include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/ include -DPY_SSIZE_T_CLEAN -I/opt/local/include -D_REENTRANT -I/opt/ local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/ include -O2 -Wall -fno-strict-aliasing -std=c9x -MT _gobject_la- pygsource.lo -MD -MP -MF .deps/_gobject_la-pygsource.Tpo -c pygsource.c -fno-common -DPIC -o .libs/_gobject_la-pygsource.o if /bin/sh ../libtool --mode=compile /usr/bin/gcc-4.0 -DHAVE_CONFIG_H - I. -I. -I.. -I/opt/local/include/python2.5 -I/opt/local/include/ python2.5 -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/lib/ glib-2.0/include -I/opt/local/include -DPY_SSIZE_T_CLEAN -I/opt/ local/include -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/ lib/glib-2.0/include -I/opt/local/include -O2 -Wall -fno-strict- aliasing -std=c9x -MT _gobject_la-pygtype.lo -MD -MP -MF ".deps/ _gobject_la-pygtype.Tpo" -c -o _gobject_la-pygtype.lo `test -f 'pygtype.c' || echo './'`pygtype.c; \ then mv -f ".deps/_gobject_la-pygtype.Tpo" ".deps/_gobject_la- pygtype.Plo"; else rm -f ".deps/_gobject_la-pygtype.Tpo"; exit 1; fi /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/local/include/ python2.5 -I/opt/local/include/python2.5 -D_REENTRANT -I/opt/local/ include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/ include -DPY_SSIZE_T_CLEAN -I/opt/local/include -D_REENTRANT -I/opt/ local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/ include -O2 -Wall -fno-strict-aliasing -std=c9x -MT _gobject_la- pygtype.lo -MD -MP -MF .deps/_gobject_la-pygtype.Tpo -c pygtype.c - fno-common -DPIC -o .libs/_gobject_la-pygtype.o if /bin/sh ../libtool --mode=compile /usr/bin/gcc-4.0 -DHAVE_CONFIG_H - I. -I. -I.. -I/opt/local/include/python2.5 -I/opt/local/include/ python2.5 -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/lib/ glib-2.0/include -I/opt/local/include -DPY_SSIZE_T_CLEAN -I/opt/ local/include -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/ lib/glib-2.0/include -I/opt/local/include -O2 -Wall -fno-strict- aliasing -std=c9x -MT _gobject_la-pygoptioncontext.lo -MD -MP -MF ".deps/_gobject_la-pygoptioncontext.Tpo" -c -o _gobject_la- pygoptioncontext.lo `test -f 'pygoptioncontext.c' || echo './'`pygoptioncontext.c; \ then mv -f ".deps/_gobject_la-pygoptioncontext.Tpo" ".deps/ _gobject_la-pygoptioncontext.Plo"; else rm -f ".deps/_gobject_la- pygoptioncontext.Tpo"; exit 1; fi /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/local/include/ python2.5 -I/opt/local/include/python2.5 -D_REENTRANT -I/opt/local/ include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/ include -DPY_SSIZE_T_CLEAN -I/opt/local/include -D_REENTRANT -I/opt/ local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/ include -O2 -Wall -fno-strict-aliasing -std=c9x -MT _gobject_la- pygoptioncontext.lo -MD -MP -MF .deps/_gobject_la-pygoptioncontext.Tpo -c pygoptioncontext.c -fno-common -DPIC -o .libs/_gobject_la- pygoptioncontext.o if /bin/sh ../libtool --mode=compile /usr/bin/gcc-4.0 -DHAVE_CONFIG_H - I. -I. -I.. -I/opt/local/include/python2.5 -I/opt/local/include/ python2.5 -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/lib/ glib-2.0/include -I/opt/local/include -DPY_SSIZE_T_CLEAN -I/opt/ local/include -D_REENTRANT -I/opt/local/include/glib-2.0 -I/opt/local/ lib/glib-2.0/include -I/opt/local/include -O2 -Wall -fno-strict- aliasing -std=c9x -MT _gobject_la-pygoptiongroup.lo -MD -MP -MF ".deps/ _gobject_la-pygoptiongroup.Tpo" -c -o _gobject_la-pygoptiongroup.lo `test -f 'pygoptiongroup.c' || echo './'`pygoptiongroup.c; \ then mv -f ".deps/_gobject_la-pygoptiongroup.Tpo" ".deps/_gobject_la- pygoptiongroup.Plo"; else rm -f ".deps/_gobject_la- pygoptiongroup.Tpo"; exit 1; fi /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/local/include/ python2.5 -I/opt/local/include/python2.5 -D_REENTRANT -I/opt/local/ include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/ include -DPY_SSIZE_T_CLEAN -I/opt/local/include -D_REENTRANT -I/opt/ local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/ include -O2 -Wall -fno-strict-aliasing -std=c9x -MT _gobject_la- pygoptiongroup.lo -MD -MP -MF .deps/_gobject_la-pygoptiongroup.Tpo -c pygoptiongroup.c -fno-common -DPIC -o .libs/_gobject_la- pygoptiongroup.o if /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/local/include/ python2.5 -I/opt/local/include/python2.5 -D_REENTRANT -I/opt/local/ include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/ include -DPY_SSIZE_T_CLEAN -I/opt/local/include -D_REENTRANT -I/ opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/ local/include -O2 -Wall -fno-strict-aliasing -std=c9x -MT generate_constants-generate-constants.o -MD -MP -MF ".deps/ generate_constants-generate-constants.Tpo" -c -o generate_constants- generate-constants.o `test -f 'generate-constants.c' || echo './'`generate-constants.c; \ then mv -f ".deps/generate_constants-generate-constants.Tpo" ".deps/ generate_constants-generate-constants.Po"; else rm -f ".deps/ generate_constants-generate-constants.Tpo"; exit 1; fi /bin/sh ../libtool --mode=link /usr/bin/gcc-4.0 -O2 -Wall -fno-strict- aliasing -std=c9x -L/opt/local/lib -o generate-constants generate_constants-generate-constants.o /usr/bin/gcc-4.0 -O2 -Wall -fno-strict-aliasing -std=c9x -o generate- constants generate_constants-generate-constants.o -L/opt/local/lib rm -f constants.py cp ./constants.py.in constants.py chmod 644 constants.py ../gobject/generate-constants >> constants.py chmod 444 constants.py /bin/sh ../libtool --mode=link /usr/bin/gcc-4.0 -O2 -Wall -fno-strict- aliasing -std=c9x -L/opt/local/lib -o _gobject.la -rpath /opt/local/ lib/python2.5/site-packages/gtk-2.0/gobject -module -avoid-version _gobject_la-gobjectmodule.lo _gobject_la-pygboxed.lo _gobject_la- pygenum.lo _gobject_la-pygflags.lo _gobject_la-pygobject.lo _gobject_la-pygmaincontext.lo _gobject_la-pygmainloop.lo _gobject_la- pygparamspec.lo _gobject_la-pygpointer.lo _gobject_la-pygiochannel.lo _gobject_la-pygsource.lo _gobject_la-pygtype.lo _gobject_la- pygoptioncontext.lo _gobject_la-pygoptiongroup.lo -L/opt/local/lib - lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lintl -liconv /usr/bin/gcc-4.0 ${wl}-flat_namespace ${wl}-undefined ${wl}suppress - o .libs/_gobject.so -bundle .libs/_gobject_la-gobjectmodule.o .libs/ _gobject_la-pygboxed.o .libs/_gobject_la-pygenum.o .libs/_gobject_la- pygflags.o .libs/_gobject_la-pygobject.o .libs/_gobject_la- pygmaincontext.o .libs/_gobject_la-pygmainloop.o .libs/_gobject_la- pygparamspec.o .libs/_gobject_la-pygpointer.o .libs/_gobject_la- pygiochannel.o .libs/_gobject_la-pygsource.o .libs/_gobject_la- pygtype.o .libs/_gobject_la-pygoptioncontext.o .libs/_gobject_la- pygoptiongroup.o -L/opt/local/lib /opt/local/lib/ libgobject-2.0.dylib /opt/local/lib/libgthread-2.0.dylib /opt/local/ lib/libglib-2.0.dylib /opt/local/lib/libintl.dylib /opt/local/lib/ libiconv.dylib ld: duplicate symbol _g_bit_nth_lsf in .libs/_gobject_la-pygboxed.o and .libs/_gobject_la-gobjectmodule.o collect2: ld returned 1 exit status make[2]: *** [_gobject.la] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: Status 1 encountered during processing. --Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080112/83f01f7f/attachment-0001.html From ryandesign at macports.org Sat Jan 12 22:32:59 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Jan 12 22:33:24 2008 Subject: py25-gobject py-gtk fail on 10.5 In-Reply-To: <5D5E0CE9-18BB-42F7-8F61-D9940EF43472@alum.mit.edu> References: <5D5E0CE9-18BB-42F7-8F61-D9940EF43472@alum.mit.edu> Message-ID: <7CB4CD5B-456A-4EAD-BA26-D07A6BA9DDA1@macports.org> On Jan 13, 2008, at 00:27, Adam Dershowitz wrote: > I recently upgraded to Leopard. I use gimp from Macports and it > depends on py25-gobject and py25-gtk. Recently both of these were > updated on macports from 2.14.0_0 to 2.14.0_1 and 2.12.0_0 to > 2.12.0_1 respectively. When I tried to do this upgrades they > failed. I then tried to do an uninstall -f of these because in the > past I have run into problem with old ports confusing upgrades with > a few other ports (I realized after the fact that I should have > just done deactivate...oh well). Now I get errors if I try to > install either the older or newer versions. > > I get similar errors for both of the builds. No one is listed as > the maintainer for these, so I am not sure who might be able to > help, but any suggestions would be appreciated. > > Has anyone managed to get these to build under 10.5.1? > > Thanks, > > Here is what I see for gobject: > > sudo port clean --all py25-gobject @2.14.0_1 > ---> Cleaning py25-gobject > macintosh$ sudo port install py25-gobject [snip] > ld: duplicate symbol _g_bit_nth_lsf in .libs/_gobject_la-pygboxed.o > and .libs/_gobject_la-gobjectmodule.o [snip] The "duplicate symbol: _g_bit_nth_lsf" bug on Leopard is filed in this ticket: http://trac.macosforge.org/projects/macports/ticket/13006 Is your glib2 up to date? If not, try updating that first. From informatique at thibaut-cousin.net Sun Jan 13 03:23:58 2008 From: informatique at thibaut-cousin.net (Thibaut Cousin) Date: Sun Jan 13 03:24:14 2008 Subject: XeTeX fails to compile on Leopard Message-ID: <14E4C04F-96D4-43D2-8E5A-D103717E9B35@thibaut-cousin.net> Hello, I'm running Macports 1.6.0 on Leopard 10.5.1 PPC and Xcode 3.0. I installed TeXLive successfully, but XeTeX fails to compile. I found a bugreport mentionning the problem, but nothing to help solve it. The bugreport is ticket #11388: http://trac.macports.org/projects/macports/ticket/11388 And my filesystem is NOT case-sensitive. Thanks for any help, -- Thibaut Cousin http://www.thibaut-cousin.net From douglas at practicalguile.com Sun Jan 13 05:49:24 2008 From: douglas at practicalguile.com (Douglas Tan) Date: Sun Jan 13 05:49:06 2008 Subject: Using Leopard's ruby with Macports' ruby libraries Message-ID: <478A16E4.6050909@practicalguile.com> As the subject states, I'm looking to find a way to use Leopard's ruby with Macport's ruby libraries like rb-rubygems, rb-mysql, et al. The main reason for doing this is so that I can use DTrace probes for ruby applications. Would a DTraced ruby be in the horizon for Macports? -- Practical Guile Clever::Tagline::Pending -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080113/9ca94412/attachment.html From dersh at alum.mit.edu Sun Jan 13 07:44:01 2008 From: dersh at alum.mit.edu (Adam Dershowitz) Date: Sun Jan 13 07:43:49 2008 Subject: py25-gobject py-gtk fail on 10.5 In-Reply-To: <7CB4CD5B-456A-4EAD-BA26-D07A6BA9DDA1@macports.org> References: <5D5E0CE9-18BB-42F7-8F61-D9940EF43472@alum.mit.edu> <7CB4CD5B-456A-4EAD-BA26-D07A6BA9DDA1@macports.org> Message-ID: <7AE688E7-D97B-4893-9D11-2B73C9529B0F@alum.mit.edu> On Jan 12, 2008, at 10:32 PM, Ryan Schmidt wrote: > > On Jan 13, 2008, at 00:27, Adam Dershowitz wrote: > >> I recently upgraded to Leopard. I use gimp from Macports and it >> depends on py25-gobject and py25-gtk. Recently both of these were >> updated on macports from 2.14.0_0 to 2.14.0_1 and 2.12.0_0 to >> 2.12.0_1 respectively. When I tried to do this upgrades they >> failed. I then tried to do an uninstall -f of these because in the >> past I have run into problem with old ports confusing upgrades with >> a few other ports (I realized after the fact that I should have >> just done deactivate...oh well). Now I get errors if I try to >> install either the older or newer versions. >> >> I get similar errors for both of the builds. No one is listed as >> the maintainer for these, so I am not sure who might be able to >> help, but any suggestions would be appreciated. >> >> Has anyone managed to get these to build under 10.5.1? >> >> Thanks, >> >> Here is what I see for gobject: >> >> sudo port clean --all py25-gobject @2.14.0_1 >> ---> Cleaning py25-gobject >> macintosh$ sudo port install py25-gobject > > [snip] > >> ld: duplicate symbol _g_bit_nth_lsf in .libs/_gobject_la-pygboxed.o >> and .libs/_gobject_la-gobjectmodule.o > > [snip] > > The "duplicate symbol: _g_bit_nth_lsf" bug on Leopard is filed in > this ticket: > > http://trac.macosforge.org/projects/macports/ticket/13006 > > Is your glib2 up to date? If not, try updating that first. Thanks. Updating glib2 to the version that came out in the last day or so solved the problem. From jean-philippe.humbert at gmx.de Sun Jan 13 11:39:28 2008 From: jean-philippe.humbert at gmx.de (Jean-Philippe Humbert) Date: Sun Jan 13 11:39:09 2008 Subject: Macport 1.6.0, Leopard and port swi-prolog and tetex do not build Message-ID: Hi, I don?t see this in Trac, so I post it here. I have tried after a fresh Installation from MAcport 1.6 on Leopard to rebuild every ports I use. 1/ I can?t build tetex: ---> Building teTeX with target all Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_teTeX/work/tetex-src-3.0" && make all " returned error 2 Command output: help-window.c:91: error: 'XmNtopAttachment' undeclared (first use in this function) help-window.c:91: error: 'XmATTACH_FORM' undeclared (first use in this function) help-window.c:91: warning: left-hand operand of comma expression has no effect help-window.c:94: error: 'XmNleftAttachment' undeclared (first use in this function) help-window.c:94: warning: left-hand operand of comma expression has no effect help-window.c:95: error: 'XmNrightAttachment' undeclared (first use in this function) help-window.c:95: warning: left-hand operand of comma expression has no effect help-window.c:96: error: 'XmNbottomAttachment' undeclared (first use in this function) help-window.c:96: warning: left-hand operand of comma expression has no effect help-window.c:97: error: 'XmNscrollingPolicy' undeclared (first use in this function) help-window.c:97: error: 'XmAUTOMATIC' undeclared (first use in this function) help-window.c:97: warning: left-hand operand of comma expression has no effect help-window.c:98: error: 'XmNscrollBarDisplayPolicy' undeclared (first use in this function) help-window.c:98: error: 'XmAS_NEEDED' undeclared (first use in this function) help-window.c:98: warning: left-hand operand of comma expression has no effect help-window.c:100: warning: implicit declaration of function 'XmCreateScrolledText' help-window.c:100: warning: assignment makes pointer from integer without a cast help-window.c: In function 'init_item': help-window.c:205: error: 'xmFormWidgetClass' undeclared (first use in this function) help-window.c:206: error: 'XmNtopAttachment' undeclared (first use in this function) help-window.c:206: error: 'XmATTACH_FORM' undeclared (first use in this function) help-window.c:207: error: 'XmNleftAttachment' undeclared (first use in this function) help-window.c:208: error: 'XmNrightAttachment' undeclared (first use in this function) help-window.c:209: error: 'XmNbottomAttachment' undeclared (first use in this function) help-window.c: In function 'initialize_items': help-window.c:296: error: 'XmVERSION_STRING' undeclared (first use in this function) make[3]: *** [help-window.o] Error 1 make[2]: *** [libguibuild] Error 2 make[1]: *** [all] Error 1 make: *** [all] Error 1 2/ I can?t build swi-prolog: Jph@Christel/~ % sudo port install -v swi-prolog >> prolog.log Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_swi-prolog/work/pl-5.6.48" && make all " returned error 2 Command output: config.status: creating Makefile config.status: creating config.h touch .pkg-config cd packages && make for p in clib cpp odbc table xpce sgml sgml/RDF semweb http chr clpqr nlp ssl pldoc plunit jpl zlib; do \ if [ -r $p/Makefile ]; then make -C $p || exit 1; fi; \ done ../plld.sh -O2 -fno-strict-aliasing -Wall -fpic -I. -Imaildrop/rfc2045 -Imaildrop/rfc822 -DHAVE_CONFIG_H -c -o random.o random.c ../plld.sh -shared -o random.dylib random.o ../plld.sh -O2 -fno-strict-aliasing -Wall -fpic -I. -Imaildrop/rfc2045 -Imaildrop/rfc822 -DHAVE_CONFIG_H -c -o error.o error.c error.c: In function 'pl_error': error.c:78: warning: unused variable 'argn' ../plld.sh -O2 -fno-strict-aliasing -Wall -fpic -I. -Imaildrop/rfc2045 -Imaildrop/rfc822 -DHAVE_CONFIG_H -c -o process.o process.c ../plld.sh -shared -o unix.dylib error.o process.o ../plld.sh -O2 -fno-strict-aliasing -Wall -fpic -I. -Imaildrop/rfc2045 -Imaildrop/rfc822 -DHAVE_CONFIG_H -c -o socket.o socket.c ../plld.sh -O2 -fno-strict-aliasing -Wall -fpic -I. -Imaildrop/rfc2045 -Imaildrop/rfc822 -DHAVE_CONFIG_H -c -o nonblockio.o nonblockio.c ../plld.sh -shared -o socket.dylib error.o socket.o nonblockio.o ../plld.sh -O2 -fno-strict-aliasing -Wall -fpic -I. -Imaildrop/rfc2045 -Imaildrop/rfc822 -DHAVE_CONFIG_H -c -o form.o form.c ../plld.sh -O2 -fno-strict-aliasing -Wall -fpic -I. -Imaildrop/rfc2045 -Imaildrop/rfc822 -DHAVE_CONFIG_H -c -o cgi.o cgi.c ../plld.sh -shared -o cgi.dylib error.o form.o cgi.o ../plld.sh -O2 -fno-strict-aliasing -Wall -fpic -I. -Imaildrop/rfc2045 -Imaildrop/rfc822 -DHAVE_CONFIG_H -c -o memfile.o memfile.c ../plld.sh -shared -o memfile.dylib error.o memfile.o ../plld.sh -O2 -fno-strict-aliasing -Wall -fpic -I. -Imaildrop/rfc2045 -Imaildrop/rfc822 -DHAVE_CONFIG_H -c -o files.o files.c ../plld.sh -shared -o files.dylib error.o files.o ../plld.sh -O2 -fno-strict-aliasing -Wall -fpic -I. -Imaildrop/rfc2045 -Imaildrop/rfc822 -DHAVE_CONFIG_H -c -o mime.o mime.c (cd maildrop/rfc2045 && make) make[3]: *** No targets specified and no makefile found. Stop. make[2]: *** [maildrop/rfc2045/librfc2045.a] Error 2 make[1]: *** [objects] Error 1 make: *** [packages] Error 2 Error: Status 1 encountered during processing. Well I have no idea what happens here. Can someone help or should I report this in Trac? Thanks // Jean-Philippe Humbert From jochen at fhi-berlin.mpg.de Sun Jan 13 12:46:21 2008 From: jochen at fhi-berlin.mpg.de (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Sun Jan 13 12:46:13 2008 Subject: [OS X Emacs] spell checking - once more In-Reply-To: References: Message-ID: <91621673-1DCF-4123-8688-A75F08962D06@fhi-berlin.mpg.de> On 13.01.2008, at 17:34, Alex Hamann wrote: > In my previous setup I had a macports installation of aspell. Now > after reinstalling Tiger I want to minimize the use of macports. What's the reason behind that??? Especially since MacPorts' aspell has no dependencies... Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll From james.sumners at gmail.com Sun Jan 13 13:05:57 2008 From: james.sumners at gmail.com (James Sumners) Date: Sun Jan 13 13:05:34 2008 Subject: [macports] The teTeX package should be phased out Message-ID: I've created a ticket [1] requesting TeXmacs' dependency be updated from teTeX to texLive. But in light of recent emails to the list about teTeX failing to build on Leopard (which I hope to be running soon), I think the teTeX port itself should be reconsidered. It is no longer being maintained upstream, and new releases have been discontinued since May 2006. The author of teTeX even suggests that users move on to using texLive. So I think it would be wise to evaluate the inclusion of, and dependencies on, teTeX. [1] -- http://trac.macosforge.org/projects/macports/ticket/13911 -- James Sumners http://james.roomfullofmirrors.com/ "All governments suffer a recurring problem: Power attracts pathological personalities. It is not that power corrupts but that it is magnetic to the corruptible. Such people have a tendency to become drunk on violence, a condition to which they are quickly addicted." Missionaria Protectiva, Text QIV (decto) CH:D 59 From benoit.caccinolo at gmail.com Sun Jan 13 13:09:34 2008 From: benoit.caccinolo at gmail.com (Benoit Caccinolo) Date: Sun Jan 13 13:09:10 2008 Subject: View of non maintained packages Message-ID: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> Hello, Is it possible to have a view of all the non maintained ports ? -- Benoit From rowue at digitalis.org Sun Jan 13 13:17:45 2008 From: rowue at digitalis.org (=?ISO-8859-1?Q?Rolf_W=FCrdemann?=) Date: Sun Jan 13 13:17:30 2008 Subject: View of non maintained packages In-Reply-To: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> References: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> Message-ID: <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> Am 13.01.2008 um 22:09 schrieb Benoit Caccinolo: > Hello, > > Is it possible to have a view of all the non maintained ports ? try: port echo maintainer:nomaintainer reg's Rolf > > -- > Benoit > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users -- Security is an illusion - Datasecurity twice Rolf W?rdemann - private: rowue@digitalis.org - office: rowue@crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue@digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Signierter Teil der Nachricht Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080113/90f09770/PGP.bin From benoit.caccinolo at gmail.com Sun Jan 13 13:25:05 2008 From: benoit.caccinolo at gmail.com (Benoit Caccinolo) Date: Sun Jan 13 13:24:45 2008 Subject: View of non maintained packages In-Reply-To: <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> References: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> Message-ID: <1d5b78a10801131325x5b2cac07s49709aa7a1164d21@mail.gmail.com> On Jan 13, 2008 10:17 PM, Rolf W?rdemann wrote: > > Am 13.01.2008 um 22:09 schrieb Benoit Caccinolo: > > > Hello, > > > > Is it possible to have a view of all the non maintained ports ? > > try: > > port echo maintainer:nomaintainer Thank you ! > port echo maintainer:nomaintainer | wc -l 2292 Gosh, there is a lot of packages not maintained ! It could be interesting to launch a call for maintainers on the blog ? Benoit From rowue at digitalis.org Sun Jan 13 13:31:54 2008 From: rowue at digitalis.org (=?ISO-8859-1?Q?Rolf_W=FCrdemann?=) Date: Sun Jan 13 13:31:40 2008 Subject: View of non maintained packages In-Reply-To: <1d5b78a10801131325x5b2cac07s49709aa7a1164d21@mail.gmail.com> References: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> <1d5b78a10801131325x5b2cac07s49709aa7a1164d21@mail.gmail.com> Message-ID: Am 13.01.2008 um 22:25 schrieb Benoit Caccinolo: > On Jan 13, 2008 10:17 PM, Rolf W?rdemann wrote: >> >> Am 13.01.2008 um 22:09 schrieb Benoit Caccinolo: >> >>> Hello, >>> >>> Is it possible to have a view of all the non maintained ports ? >> >> try: >> >> port echo maintainer:nomaintainer > Thank you ! > >> port echo maintainer:nomaintainer | wc -l > 2292 > > Gosh, there is a lot of packages not maintained ! > > It could be interesting to launch a call for maintainers on the blog ? Hmmm - I'm a maintainer of three ports - and waiting since one to three weeks for commitments ... If this happens to new maintainers - think they will not be maintainers for very long > > Benoit Reg's Rolf -- Security is an illusion - Datasecurity twice Rolf W?rdemann - private: rowue@digitalis.org - office: rowue@crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue@digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Signierter Teil der Nachricht Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080113/8ebb8333/PGP.bin From mark at wardle.org Sun Jan 13 13:49:24 2008 From: mark at wardle.org (Mark Wardle) Date: Sun Jan 13 13:49:01 2008 Subject: [macports] The teTeX package should be phased out In-Reply-To: References: Message-ID: I would second that! As only a lurker on this list, but an active user of LaTeX and macports, I uninstalled teTeX last year in favour of texlive. While it is not perfect (ideally it would be a core system with additional packages installed as required directly from CTAN with some form of auto-update) it is what is available "right now". It is a pain installing anything using macports that has TeX as a dependency and subsequently having teTeX installed automatically. It is easy to then fix, but still an annoyance! Best wishes, Mark NB: Must say a thank-you for making macports available - it is really rather good, and I rely on it all the time On 13/01/2008, James Sumners wrote: > I've created a ticket [1] requesting TeXmacs' dependency be updated > from teTeX to texLive. But in light of recent emails to the list about > teTeX failing to build on Leopard (which I hope to be running soon), I > think the teTeX port itself should be reconsidered. It is no longer > being maintained upstream, and new releases have been discontinued > since May 2006. The author of teTeX even suggests that users move on > to using texLive. So I think it would be wise to evaluate the > inclusion of, and dependencies on, teTeX. > > [1] -- http://trac.macosforge.org/projects/macports/ticket/13911 > > -- > James Sumners > http://james.roomfullofmirrors.com/ > > "All governments suffer a recurring problem: Power attracts > pathological personalities. It is not that power corrupts but that it > is magnetic to the corruptible. Such people have a tendency to become > drunk on violence, a condition to which they are quickly addicted." > > Missionaria Protectiva, Text QIV (decto) > CH:D 59 > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > -- Dr. Mark Wardle Specialist registrar, Neurology Cardiff, UK From lisfolks.lists at gmail.com Sun Jan 13 13:56:50 2008 From: lisfolks.lists at gmail.com (LeAnne Lis) Date: Sun Jan 13 13:56:28 2008 Subject: libffi: pyobjc-4.1 fetch failing Message-ID: <14791653.post@talk.nabble.com> I'm trying to install libffi, which apparently needs a 'pyobjc-1.4.tar.gz' file to install. It's failing on the fetch as follows. Should I put a ticket in? sudo port install libffi ---> Fetching libffi ---> Attempting to fetch pyobjc-1.4.tar.gz from http://pyobjc.sourceforge.net/software/ ---> Attempting to fetch pyobjc-1.4.tar.gz from http://downloads.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://easynews.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://ufpr.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://kent.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://jaist.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://svn.macports.org/repository/macports/distfiles/libffi ---> Attempting to fetch pyobjc-1.4.tar.gz from http://svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch pyobjc-1.4.tar.gz from http://svn.macports.org/repository/macports/downloads/libffi Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. -- View this message in context: http://www.nabble.com/libffi%3A--pyobjc-4.1-fetch-failing-tp14791653p14791653.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From lisfolks.lists at gmail.com Sun Jan 13 13:57:49 2008 From: lisfolks.lists at gmail.com (LeAnne Lis) Date: Sun Jan 13 13:57:27 2008 Subject: libffi: pyobjc-1.4 fetch failing Message-ID: <14791653.post@talk.nabble.com> I'm trying to install libffi, which apparently needs a 'pyobjc-1.4.tar.gz' file to install. It's failing on the fetch as follows. Should I put a ticket in? sudo port install libffi ---> Fetching libffi ---> Attempting to fetch pyobjc-1.4.tar.gz from http://pyobjc.sourceforge.net/software/ ---> Attempting to fetch pyobjc-1.4.tar.gz from http://downloads.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://easynews.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://ufpr.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://kent.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://jaist.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://svn.macports.org/repository/macports/distfiles/libffi ---> Attempting to fetch pyobjc-1.4.tar.gz from http://svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch pyobjc-1.4.tar.gz from http://svn.macports.org/repository/macports/downloads/libffi Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. -- View this message in context: http://www.nabble.com/libffi%3A--pyobjc-1.4-fetch-failing-tp14791653p14791653.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From paulbeard at gmail.com Sun Jan 13 14:01:08 2008 From: paulbeard at gmail.com (paul beard) Date: Sun Jan 13 14:00:46 2008 Subject: Using Leopard's ruby with Macports' ruby libraries In-Reply-To: <478A16E4.6050909@practicalguile.com> References: <478A16E4.6050909@practicalguile.com> Message-ID: On Jan 13, 2008 5:49 AM, Douglas Tan wrote: > As the subject states, I'm looking to find a way to use Leopard's ruby > with Macport's ruby libraries like rb-rubygems, rb-mysql, et al. The main > reason for doing this is so that I can use DTrace probes for ruby > applications. > > Would a DTraced ruby be in the horizon for Macports? > I don't have Leopard and won't see it for quite some time. What does it take to make an app DTrace-able? Is this something that can be done in the port? -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080113/388d726e/attachment-0001.html From jberry at macports.org Sun Jan 13 14:28:15 2008 From: jberry at macports.org (James Berry) Date: Sun Jan 13 14:27:55 2008 Subject: View of non maintained packages In-Reply-To: References: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> <1d5b78a10801131325x5b2cac07s49709aa7a1164d21@mail.gmail.com> Message-ID: <25890C56-1FFA-461F-85F1-6304024B98B6@macports.org> Hi Rolf, On Jan 13, 2008, at 1:31 PM, Rolf W?rdemann wrote: >> Gosh, there is a lot of packages not maintained ! >> >> It could be interesting to launch a call for maintainers on the >> blog ? > > Hmmm - I'm a maintainer of three ports - and waiting since one to > three > weeks for commitments ... > > If this happens to new maintainers - think they will not be > maintainers > for very long I would encourage you, and anybody else who is a maintainer and who would like to be able to do their own commits, to simply apply for committer status. We are not particularly selective about giving out commit bits, as long as the individual has shown that they can maintain ports in a trustworthy fashion. http://trac.macports.org/projects/macports/wiki/NewCommittersGuide James From rowue at digitalis.org Sun Jan 13 15:08:22 2008 From: rowue at digitalis.org (=?ISO-8859-1?Q?Rolf_W=FCrdemann?=) Date: Sun Jan 13 15:08:08 2008 Subject: View of non maintained packages In-Reply-To: <25890C56-1FFA-461F-85F1-6304024B98B6@macports.org> References: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> <1d5b78a10801131325x5b2cac07s49709aa7a1164d21@mail.gmail.com> <25890C56-1FFA-461F-85F1-6304024B98B6@macports.org> Message-ID: Am 13.01.2008 um 23:28 schrieb James Berry: > Hi Rolf, Hi James, > > On Jan 13, 2008, at 1:31 PM, Rolf W?rdemann wrote: >>> Gosh, there is a lot of packages not maintained ! >>> >>> It could be interesting to launch a call for maintainers on the >>> blog ? >> >> Hmmm - I'm a maintainer of three ports - and waiting since one to >> three >> weeks for commitments ... >> >> If this happens to new maintainers - think they will not be >> maintainers >> for very long > > I would encourage you, and anybody else who is a maintainer and who > would like to be able to do their own commits, to simply apply for > committer status. We are not particularly selective about giving > out commit bits, as long as the individual has shown that they can > maintain ports in a trustworthy fashion. O.K. - I've thought about it today - and wrote the mail a few minutes ago ;) But it seems that we need more committers before asking on the website - if we get mainatiners for a quarter of the ports there will be much work (if my case with the one to three weeks was not a single case) ;) > > http://trac.macports.org/projects/macports/wiki/NewCommittersGuide > > James reg's Rolf -- Security is an illusion - Datasecurity twice Rolf W?rdemann - private: rowue@digitalis.org - office: rowue@crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue@digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Signierter Teil der Nachricht Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080114/fb51bc29/PGP.bin From ryandesign at macports.org Sun Jan 13 15:18:31 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Jan 13 15:18:55 2008 Subject: libffi: pyobjc-1.4.tar.gz fetch failing In-Reply-To: <14791653.post@talk.nabble.com> References: <14791653.post@talk.nabble.com> Message-ID: <5B0728CE-9D64-4FA9-BC3D-2F4F83861C71@macports.org> On Jan 13, 2008, at 15:56, LeAnne Lis wrote: > I'm trying to install libffi, which apparently needs a > 'pyobjc-1.4.tar.gz' > file to install. It's failing on the fetch as follows. Should I > put a > ticket in? > > sudo port install libffi > ---> Fetching libffi > ---> Attempting to fetch pyobjc-1.4.tar.gz from > http://pyobjc.sourceforge.net/software/ > ---> Attempting to fetch pyobjc-1.4.tar.gz from > http://downloads.sourceforge.net/pyobjc > ---> Attempting to fetch pyobjc-1.4.tar.gz from > http://easynews.dl.sourceforge.net/pyobjc > ---> Attempting to fetch pyobjc-1.4.tar.gz from > http://ufpr.dl.sourceforge.net/pyobjc > ---> Attempting to fetch pyobjc-1.4.tar.gz from > http://kent.dl.sourceforge.net/pyobjc > ---> Attempting to fetch pyobjc-1.4.tar.gz from > http://jaist.dl.sourceforge.net/pyobjc > ---> Attempting to fetch pyobjc-1.4.tar.gz from > http://svn.macports.org/repository/macports/distfiles/libffi > ---> Attempting to fetch pyobjc-1.4.tar.gz from > http://svn.macports.org/repository/macports/distfiles/general/ > ---> Attempting to fetch pyobjc-1.4.tar.gz from > http://svn.macports.org/repository/macports/downloads/libffi > Error: Target org.macports.fetch returned: fetch failed > Error: Status 1 encountered during processing. Based on the transcript in ticket #13287, pyobjc-1.4.tar.gz used to exist at http://pyobjc.sourceforge.net/software/ but nothing except a verbose error message exists there now. So yes, you should file a ticket and assign the ticket to the maintainer of libffi. Perhaps he can fix the py-pyobjc file while he's at it, if indeed the files need fixing (if the download location has changed). Or maybe the pyobjc web site administrators just need to be prodded into fixing their site. From raimue at macports.org Sun Jan 13 15:21:41 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sun Jan 13 15:21:26 2008 Subject: View of non maintained packages In-Reply-To: References: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> <1d5b78a10801131325x5b2cac07s49709aa7a1164d21@mail.gmail.com> <25890C56-1FFA-461F-85F1-6304024B98B6@macports.org> Message-ID: <478A9D05.4040707@macports.org> Rolf W?rdemann wrote: > But it seems that we need more committers before asking on > the website - if we get mainatiners for a quarter of the ports > there will be much work (if my case with the one to three weeks > was not a single case) ;) Maybe we should have someone who is responsible for committing updates for particular port categories. I think the problem at the moment is that a port update is committed if someone looked into Trac to see any pending updates... So this is rather random when a port update is committed. Rainer From ryandesign at macports.org Sun Jan 13 15:25:04 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Jan 13 15:25:30 2008 Subject: Macport 1.6.0, Leopard and port swi-prolog and tetex do not build In-Reply-To: References: Message-ID: On Jan 13, 2008, at 13:39, Jean-Philippe Humbert wrote: > I don?t see this in Trac, so I post it here. > I have tried after a fresh Installation from MAcport 1.6 on Leopard > to rebuild every ports I use. [snip] > Well I have no idea what happens here. > Can someone help or should I report this in Trac? Bugs should always be reported in our issue tracker, of course. > 1/ I can?t build tetex: > ---> Building teTeX with target all > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_print > _teTeX/work/tetex-src-3.0" && make all " returned error 2 > Command output: help-window.c:91: error: 'XmNtopAttachment' > undeclared (first use in this function) [snip] Note that there are already many tickets filed about teTeX; perhaps one of them relates? http://trac.macosforge.org/projects/macports/query? status=new&status=assigned&status=reopened&summary=% 7Etetex&order=priority Note also that teTeX is essentially dead: http://trac.macosforge.org/projects/macports/ticket/12913 Do you really want teTeX? You may want to try texlive instead. > 2/ I can?t build swi-prolog: > Jph@Christel/~ % sudo port install -v swi-prolog >> prolog.log > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ > swi-prolog/work/pl-5.6.48" && make all " returned error 2 [snip] > make[3]: *** No targets specified and no makefile found. Stop. > make[2]: *** [maildrop/rfc2045/librfc2045.a] Error 2 > make[1]: *** [objects] Error 1 > make: *** [packages] Error 2 > > Error: Status 1 encountered during processing. That looks like this ticket: http://trac.macosforge.org/projects/macports/ticket/13670 I've added your email address to the bug's Cc list so you'll be informed of any progress in resolving it. From ryandesign at macports.org Sun Jan 13 15:27:18 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Jan 13 15:27:41 2008 Subject: XeTeX fails to compile on Leopard In-Reply-To: <14E4C04F-96D4-43D2-8E5A-D103717E9B35@thibaut-cousin.net> References: <14E4C04F-96D4-43D2-8E5A-D103717E9B35@thibaut-cousin.net> Message-ID: On Jan 13, 2008, at 05:23, Thibaut Cousin wrote: > I'm running Macports 1.6.0 on Leopard 10.5.1 PPC and Xcode 3.0. > I installed TeXLive successfully, but XeTeX fails to compile. I > found a bugreport mentionning the problem, but nothing to help > solve it. The bugreport is ticket #11388: > > http://trac.macports.org/projects/macports/ticket/11388 > > And my filesystem is NOT case-sensitive. > Thanks for any help, I added your email address to the bug's Cc list so you'll be informed of any progress in resolving it. From rowue at digitalis.org Sun Jan 13 15:37:04 2008 From: rowue at digitalis.org (=?ISO-8859-1?Q?Rolf_W=FCrdemann?=) Date: Sun Jan 13 15:37:00 2008 Subject: View of non maintained packages In-Reply-To: <478A9D05.4040707@macports.org> References: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> <1d5b78a10801131325x5b2cac07s49709aa7a1164d21@mail.gmail.com> <25890C56-1FFA-461F-85F1-6304024B98B6@macports.org> <478A9D05.4040707@macports.org> Message-ID: Am 14.01.2008 um 00:21 schrieb Rainer M?ller: > Rolf W?rdemann wrote: >> But it seems that we need more committers before asking on >> the website - if we get mainatiners for a quarter of the ports >> there will be much work (if my case with the one to three weeks >> was not a single case) ;) > > Maybe we should have someone who is responsible for committing updates > for particular port categories. I think the problem at the moment is > that a port update is committed if someone looked into Trac to see any > pending updates... So this is rather random when a port update is > committed. Maybe an commit-group would be an idea ;) (something like the support- group at our office ;) > > Rainer Rolf -- Security is an illusion - Datasecurity twice Rolf W?rdemann - private: rowue@digitalis.org - office: rowue@crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue@digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Signierter Teil der Nachricht Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080114/e3ef9481/PGP.bin From garrett.reid at gmail.com Sun Jan 13 16:00:34 2008 From: garrett.reid at gmail.com (Garrett Reid) Date: Sun Jan 13 16:00:15 2008 Subject: sqlite3 update problem Message-ID: <153C061D-FA28-4292-90DA-3372ABBE5B9F@gmail.com> I've been trying to update my installed ports, but it keeps bombing out on sqlite3 and I can't figure out why. Included below is the full transcript (it's not too long). Any ideas? Thanks in advance, Garrett [myhost:~] garrett$ sudo port selfupdate MacPorts base version 1.600 installed Downloaded MacPorts base version 1.600 The MacPorts installation is not outdated and so was not updated selfupdate done! [myhost:~] garrett$ sudo port upgrade outdated ---> Building sqlite3 with target all Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_databases_sqlite3/work/sqlite-3.5.4" && gnumake all " returned error 2 Command output: ./libtool --mode=compile --tag=CC /usr/bin/gcc-4.0 -O2 -I. -I./src -DNDEBUG -DSQLITE_THREADSAFE=1 - DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c ./ src/alter.c /usr/bin/gcc-4.0 -O2 -I. -I./src -DNDEBUG -DSQLITE_THREADSAFE=1 - DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c ./ src/alter.c -fno-common -DPIC -o .libs/alter.o ./src/alter.c: In function 'renameTableFunc': ./src/alter.c:77: error: 'TK_SPACE' undeclared (first use in this function) ./src/alter.c:77: error: (Each undeclared identifier is reported only once ./src/alter.c:77: error: for each function it appears in.) ./src/alter.c:79: error: 'TK_LP' undeclared (first use in this function) ./src/alter.c:79: error: 'TK_USING' undeclared (first use in this function) ./src/alter.c: In function 'renameTriggerFunc': ./src/alter.c:135: error: 'TK_SPACE' undeclared (first use in this function) ./src/alter.c:148: error: 'TK_DOT' undeclared (first use in this function) ./src/alter.c:148: error: 'TK_ON' undeclared (first use in this function) ./src/alter.c:151: error: 'TK_WHEN' undeclared (first use in this function) ./src/alter.c:151: error: 'TK_FOR' undeclared (first use in this function) ./src/alter.c:151: error: 'TK_BEGIN' undeclared (first use in this function) ./src/alter.c: In function 'reloadTableSchema': ./src/alter.c:246: error: 'OP_DropTrigger' undeclared (first use in this function) ./src/alter.c:251: error: 'OP_DropTable' undeclared (first use in this function) ./src/alter.c:256: error: 'OP_ParseSchema' undeclared (first use in this function) ./src/alter.c: In function 'sqlite3AlterRenameTable': ./src/alter.c:365: error: 'OP_String8' undeclared (first use in this function) ./src/alter.c:366: error: 'OP_VRename' undeclared (first use in this function) ./src/alter.c: In function 'sqlite3AlterFinishAddColumn': ./src/alter.c:478: error: 'TK_NULL' undeclared (first use in this function) gnumake: *** [alter.lo] Error 1 Error: Unable to upgrade port: 1 From jay+macports at covariant.org Sun Jan 13 16:08:05 2008 From: jay+macports at covariant.org (Jay Sachs) Date: Sun Jan 13 16:07:49 2008 Subject: sqlite3 update problem In-Reply-To: <153C061D-FA28-4292-90DA-3372ABBE5B9F@gmail.com> References: <153C061D-FA28-4292-90DA-3372ABBE5B9F@gmail.com> Message-ID: On Jan 13, 2008, at 7:00 PM, Garrett Reid wrote: > I've been trying to update my installed ports, but it keeps bombing > out on sqlite3 and I can't figure out why. Included below is the > full transcript (it's not too long). Any ideas? Try force removing sqlite3 and then installing it. sqllite seems very sensitive to prior versions in /opt/local. > j. > Thanks in advance, > Garrett > > > [myhost:~] garrett$ sudo port selfupdate > > MacPorts base version 1.600 installed > > Downloaded MacPorts base version 1.600 > > The MacPorts installation is not outdated and so was not updated > selfupdate done! > [myhost:~] garrett$ sudo port upgrade outdated > ---> Building sqlite3 with target all > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_databases_sqlite3/work/sqlite-3.5.4" && > gnumake all " returned error 2 > Command output: ./libtool --mode=compile --tag=CC /usr/bin/gcc-4.0 - > O2 -I. -I./src -DNDEBUG -DSQLITE_THREADSAFE=1 - > DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c ./ > src/alter.c > /usr/bin/gcc-4.0 -O2 -I. -I./src -DNDEBUG -DSQLITE_THREADSAFE=1 - > DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c ./ > src/alter.c -fno-common -DPIC -o .libs/alter.o > ./src/alter.c: In function 'renameTableFunc': > ./src/alter.c:77: error: 'TK_SPACE' undeclared (first use in this > function) > ./src/alter.c:77: error: (Each undeclared identifier is reported > only once > ./src/alter.c:77: error: for each function it appears in.) > ./src/alter.c:79: error: 'TK_LP' undeclared (first use in this > function) > ./src/alter.c:79: error: 'TK_USING' undeclared (first use in this > function) > ./src/alter.c: In function 'renameTriggerFunc': > ./src/alter.c:135: error: 'TK_SPACE' undeclared (first use in this > function) > ./src/alter.c:148: error: 'TK_DOT' undeclared (first use in this > function) > ./src/alter.c:148: error: 'TK_ON' undeclared (first use in this > function) > ./src/alter.c:151: error: 'TK_WHEN' undeclared (first use in this > function) > ./src/alter.c:151: error: 'TK_FOR' undeclared (first use in this > function) > ./src/alter.c:151: error: 'TK_BEGIN' undeclared (first use in this > function) > ./src/alter.c: In function 'reloadTableSchema': > ./src/alter.c:246: error: 'OP_DropTrigger' undeclared (first use in > this function) > ./src/alter.c:251: error: 'OP_DropTable' undeclared (first use in > this function) > ./src/alter.c:256: error: 'OP_ParseSchema' undeclared (first use in > this function) > ./src/alter.c: In function 'sqlite3AlterRenameTable': > ./src/alter.c:365: error: 'OP_String8' undeclared (first use in this > function) > ./src/alter.c:366: error: 'OP_VRename' undeclared (first use in this > function) > ./src/alter.c: In function 'sqlite3AlterFinishAddColumn': > ./src/alter.c:478: error: 'TK_NULL' undeclared (first use in this > function) > gnumake: *** [alter.lo] Error 1 > > Error: Unable to upgrade port: 1 > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users From garrett.reid at gmail.com Sun Jan 13 16:11:41 2008 From: garrett.reid at gmail.com (Garrett Reid) Date: Sun Jan 13 16:11:22 2008 Subject: sqlite3 update problem In-Reply-To: References: <153C061D-FA28-4292-90DA-3372ABBE5B9F@gmail.com> Message-ID: <28AA4DBD-92CB-4050-9324-4C2769AC7DD0@gmail.com> Other ports seem to depend on it, do I need to delete them too? > [myhost:~] garrett$ sudo port uninstall sqlite3 > ---> The following versions of sqlite3 are currently installed: > ---> sqlite3 @3.3.15_0+darwin_8 > ---> sqlite3 @3.3.16_0+darwin_8 > ---> sqlite3 @3.3.17_0+darwin_8 > ---> sqlite3 @3.4.1_0+darwin_8 > ---> sqlite3 @3.5.1_0+darwin_8 > ---> sqlite3 @3.5.2_0+darwin_8 > ---> sqlite3 @3.5.3_1+darwin_8 (active) > Error: port uninstall failed: Registry error: Please specify the > full version as recorded in the port registry. > [myhost:~] garrett$ sudo port uninstall sqlite3 @3.5.3_1+darwin_8 > ---> Unable to uninstall sqlite3 3.3.15_0+darwin_8, the following > ports depend on it: > ---> apr-util > ---> apr-util > ---> apr-util > Error: port uninstall failed: Please uninstall the ports that depend > on sqlite3 first. Or am I going about this wrong? Sorry for being so helpless, I'll get macports figured eventually :P - Garrett On Jan 13, 2008, at 4:08 PM, Jay Sachs wrote: > On Jan 13, 2008, at 7:00 PM, Garrett Reid wrote: > >> I've been trying to update my installed ports, but it keeps bombing >> out on sqlite3 and I can't figure out why. Included below is the >> full transcript (it's not too long). Any ideas? > > Try force removing sqlite3 and then installing it. sqllite seems > very sensitive to prior versions in /opt/local. >> > > j. > >> Thanks in advance, >> Garrett >> >> >> [myhost:~] garrett$ sudo port selfupdate >> >> MacPorts base version 1.600 installed >> >> Downloaded MacPorts base version 1.600 >> >> The MacPorts installation is not outdated and so was not updated >> selfupdate done! >> [myhost:~] garrett$ sudo port upgrade outdated >> ---> Building sqlite3 with target all >> Error: Target org.macports.build returned: shell command " cd "/opt/ >> local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_databases_sqlite3/work/sqlite-3.5.4" && >> gnumake all " returned error 2 >> Command output: ./libtool --mode=compile --tag=CC /usr/bin/gcc-4.0 - >> O2 -I. -I./src -DNDEBUG -DSQLITE_THREADSAFE=1 - >> DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c ./ >> src/alter.c >> /usr/bin/gcc-4.0 -O2 -I. -I./src -DNDEBUG -DSQLITE_THREADSAFE=1 - >> DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c ./ >> src/alter.c -fno-common -DPIC -o .libs/alter.o >> ./src/alter.c: In function 'renameTableFunc': >> ./src/alter.c:77: error: 'TK_SPACE' undeclared (first use in this >> function) >> ./src/alter.c:77: error: (Each undeclared identifier is reported >> only once >> ./src/alter.c:77: error: for each function it appears in.) >> ./src/alter.c:79: error: 'TK_LP' undeclared (first use in this >> function) >> ./src/alter.c:79: error: 'TK_USING' undeclared (first use in this >> function) >> ./src/alter.c: In function 'renameTriggerFunc': >> ./src/alter.c:135: error: 'TK_SPACE' undeclared (first use in this >> function) >> ./src/alter.c:148: error: 'TK_DOT' undeclared (first use in this >> function) >> ./src/alter.c:148: error: 'TK_ON' undeclared (first use in this >> function) >> ./src/alter.c:151: error: 'TK_WHEN' undeclared (first use in this >> function) >> ./src/alter.c:151: error: 'TK_FOR' undeclared (first use in this >> function) >> ./src/alter.c:151: error: 'TK_BEGIN' undeclared (first use in this >> function) >> ./src/alter.c: In function 'reloadTableSchema': >> ./src/alter.c:246: error: 'OP_DropTrigger' undeclared (first use in >> this function) >> ./src/alter.c:251: error: 'OP_DropTable' undeclared (first use in >> this function) >> ./src/alter.c:256: error: 'OP_ParseSchema' undeclared (first use in >> this function) >> ./src/alter.c: In function 'sqlite3AlterRenameTable': >> ./src/alter.c:365: error: 'OP_String8' undeclared (first use in >> this function) >> ./src/alter.c:366: error: 'OP_VRename' undeclared (first use in >> this function) >> ./src/alter.c: In function 'sqlite3AlterFinishAddColumn': >> ./src/alter.c:478: error: 'TK_NULL' undeclared (first use in this >> function) >> gnumake: *** [alter.lo] Error 1 >> >> Error: Unable to upgrade port: 1 >> _______________________________________________ >> macports-users mailing list >> macports-users@lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo/macports-users > From lisfolks.lists at gmail.com Sun Jan 13 17:33:54 2008 From: lisfolks.lists at gmail.com (LeAnne Lis) Date: Sun Jan 13 17:33:32 2008 Subject: libffi: pyobjc-1.4.tar.gz fetch failing In-Reply-To: <5B0728CE-9D64-4FA9-BC3D-2F4F83861C71@macports.org> References: <14791653.post@talk.nabble.com> <5B0728CE-9D64-4FA9-BC3D-2F4F83861C71@macports.org> Message-ID: <14793899.post@talk.nabble.com> Ryan Schmidt-24 wrote: > > On Jan 13, 2008, at 15:56, LeAnne Lis wrote: > >> I'm trying to install libffi, which apparently needs a >> 'pyobjc-1.4.tar.gz' >> file to install. It's failing on the fetch ... Should I >> put a >> ticket in? >> > > Based on the transcript in ticket #13287, pyobjc-1.4.tar.gz used to > exist at http://pyobjc.sourceforge.net/software/ but nothing except a > verbose error message exists there now. So yes, you should file a > ticket and assign the ticket to the maintainer of libffi. Perhaps he > can fix the py-pyobjc file while he's at it, if indeed the files need > fixing (if the download location has changed). Or maybe the pyobjc > web site administrators just need to be prodded into fixing their site. > Ticket #13912 has been entered for this issue. -- View this message in context: http://www.nabble.com/libffi%3A--pyobjc-1.4-fetch-failing-tp14791653p14793899.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From jay+macports at covariant.org Sun Jan 13 18:33:15 2008 From: jay+macports at covariant.org (Jay Sachs) Date: Sun Jan 13 18:33:09 2008 Subject: sqlite3 update problem In-Reply-To: <28AA4DBD-92CB-4050-9324-4C2769AC7DD0@gmail.com> References: <153C061D-FA28-4292-90DA-3372ABBE5B9F@gmail.com> <28AA4DBD-92CB-4050-9324-4C2769AC7DD0@gmail.com> Message-ID: On Jan 13, 2008, at 7:11 PM, Garrett Reid wrote: > Other ports seem to depend on it, do I need to delete them too? If you can afford the time, yes. Just to be clear, I haven't tested this, it's just something that worked in the past when I ran into problems upgrading sqlite3. I did just install it successfully, so I know it builds. >> [myhost:~] garrett$ sudo port uninstall sqlite3 >> ---> The following versions of sqlite3 are currently installed: >> ---> sqlite3 @3.3.15_0+darwin_8 >> ---> sqlite3 @3.3.16_0+darwin_8 >> ---> sqlite3 @3.3.17_0+darwin_8 >> ---> sqlite3 @3.4.1_0+darwin_8 >> ---> sqlite3 @3.5.1_0+darwin_8 >> ---> sqlite3 @3.5.2_0+darwin_8 >> ---> sqlite3 @3.5.3_1+darwin_8 (active) >> Error: port uninstall failed: Registry error: Please specify the >> full version as recorded in the port registry. >> [myhost:~] garrett$ sudo port uninstall sqlite3 @3.5.3_1+darwin_8 >> ---> Unable to uninstall sqlite3 3.3.15_0+darwin_8, the following >> ports depend on it: >> ---> apr-util >> ---> apr-util >> ---> apr-util >> Error: port uninstall failed: Please uninstall the ports that >> depend on sqlite3 first. > > > Or am I going about this wrong? > Sorry for being so helpless, I'll get macports figured eventually :P Just need to "force" the uninstall, with the "-f" flag. j. From douglas at practicalguile.com Sun Jan 13 18:38:35 2008 From: douglas at practicalguile.com (Douglas Tan) Date: Sun Jan 13 18:38:17 2008 Subject: Using Leopard's ruby with Macports' ruby libraries Message-ID: <478ACB2B.5030608@practicalguile.com> -------- Original Message -------- Subject: macports-users Digest, Vol 17, Issue 59 Date: Sun, 13 Jan 2008 14:00:50 -0800 (PST) From: macports-users-request@lists.macosforge.org Reply-To: macports-users@lists.macosforge.org To: macports-users@lists.macosforge.org Send macports-users mailing list submissions to macports-users@lists.macosforge.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.macosforge.org/mailman/listinfo/macports-users or, via email, send a message with subject or body 'help' to macports-users-request@lists.macosforge.org You can reach the person managing the list at macports-users-owner@lists.macosforge.org When replying, please edit your Subject line so it is more specific than "Re: Contents of macports-users digest..." Today's Topics: 1. Re: View of non maintained packages (Rolf W?rdemann) 2. Re: View of non maintained packages (Benoit Caccinolo) 3. Re: View of non maintained packages (Rolf W?rdemann) 4. Re: [macports] The teTeX package should be phased out (Mark Wardle) 5. libffi: pyobjc-4.1 fetch failing (LeAnne Lis) 6. libffi: pyobjc-1.4 fetch failing (LeAnne Lis) 7. Re: Using Leopard's ruby with Macports' ruby libraries (paul beard) ---------------------------------------------------------------------- Message: 1 Date: Sun, 13 Jan 2008 22:17:45 +0100 From: Rolf W?rdemann Subject: Re: View of non maintained packages To: Benoit Caccinolo Cc: macports-users@lists.macosforge.org Message-ID: <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> Content-Type: text/plain; charset="iso-8859-1" Am 13.01.2008 um 22:09 schrieb Benoit Caccinolo: > Hello, > > Is it possible to have a view of all the non maintained ports ? try: port echo maintainer:nomaintainer reg's Rolf > > -- > Benoit > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users -- Security is an illusion - Datasecurity twice Rolf W?rdemann - private: rowue@digitalis.org - office: rowue@crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue@digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Signierter Teil der Nachricht Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080113/90f09770/PGP-0001.bin ------------------------------ Message: 2 Date: Sun, 13 Jan 2008 22:25:05 +0100 From: "Benoit Caccinolo" Subject: Re: View of non maintained packages To: " Rolf W?rdemann " Cc: macports-users@lists.macosforge.org Message-ID: <1d5b78a10801131325x5b2cac07s49709aa7a1164d21@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 On Jan 13, 2008 10:17 PM, Rolf W?rdemann wrote: > > Am 13.01.2008 um 22:09 schrieb Benoit Caccinolo: > > > Hello, > > > > Is it possible to have a view of all the non maintained ports ? > > try: > > port echo maintainer:nomaintainer Thank you ! > port echo maintainer:nomaintainer | wc -l 2292 Gosh, there is a lot of packages not maintained ! It could be interesting to launch a call for maintainers on the blog ? Benoit ------------------------------ Message: 3 Date: Sun, 13 Jan 2008 22:31:54 +0100 From: Rolf W?rdemann Subject: Re: View of non maintained packages To: Benoit Caccinolo Cc: macports-users@lists.macosforge.org Message-ID: Content-Type: text/plain; charset="iso-8859-1" Am 13.01.2008 um 22:25 schrieb Benoit Caccinolo: > On Jan 13, 2008 10:17 PM, Rolf W?rdemann wrote: >> >> Am 13.01.2008 um 22:09 schrieb Benoit Caccinolo: >> >>> Hello, >>> >>> Is it possible to have a view of all the non maintained ports ? >> >> try: >> >> port echo maintainer:nomaintainer > Thank you ! > >> port echo maintainer:nomaintainer | wc -l > 2292 > > Gosh, there is a lot of packages not maintained ! > > It could be interesting to launch a call for maintainers on the blog ? Hmmm - I'm a maintainer of three ports - and waiting since one to three weeks for commitments ... If this happens to new maintainers - think they will not be maintainers for very long > > Benoit Reg's Rolf -- Security is an illusion - Datasecurity twice Rolf W?rdemann - private: rowue@digitalis.org - office: rowue@crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue@digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Signierter Teil der Nachricht Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080113/8ebb8333/PGP-0001.bin ------------------------------ Message: 4 Date: Sun, 13 Jan 2008 21:49:24 +0000 From: "Mark Wardle" Subject: Re: [macports] The teTeX package should be phased out To: macports-users@lists.macosforge.org Message-ID: Content-Type: text/plain; charset=ISO-8859-1 I would second that! As only a lurker on this list, but an active user of LaTeX and macports, I uninstalled teTeX last year in favour of texlive. While it is not perfect (ideally it would be a core system with additional packages installed as required directly from CTAN with some form of auto-update) it is what is available "right now". It is a pain installing anything using macports that has TeX as a dependency and subsequently having teTeX installed automatically. It is easy to then fix, but still an annoyance! Best wishes, Mark NB: Must say a thank-you for making macports available - it is really rather good, and I rely on it all the time On 13/01/2008, James Sumners wrote: > I've created a ticket [1] requesting TeXmacs' dependency be updated > from teTeX to texLive. But in light of recent emails to the list about > teTeX failing to build on Leopard (which I hope to be running soon), I > think the teTeX port itself should be reconsidered. It is no longer > being maintained upstream, and new releases have been discontinued > since May 2006. The author of teTeX even suggests that users move on > to using texLive. So I think it would be wise to evaluate the > inclusion of, and dependencies on, teTeX. > > [1] -- http://trac.macosforge.org/projects/macports/ticket/13911 > > -- > James Sumners > http://james.roomfullofmirrors.com/ > > "All governments suffer a recurring problem: Power attracts > pathological personalities. It is not that power corrupts but that it > is magnetic to the corruptible. Such people have a tendency to become > drunk on violence, a condition to which they are quickly addicted." > > Missionaria Protectiva, Text QIV (decto) > CH:D 59 > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > -- Dr. Mark Wardle Specialist registrar, Neurology Cardiff, UK ------------------------------ Message: 5 Date: Sun, 13 Jan 2008 13:56:50 -0800 (PST) From: LeAnne Lis Subject: libffi: pyobjc-4.1 fetch failing To: macports-users@lists.macosforge.org Message-ID: <14791653.post@talk.nabble.com> Content-Type: text/plain; charset=us-ascii I'm trying to install libffi, which apparently needs a 'pyobjc-1.4.tar.gz' file to install. It's failing on the fetch as follows. Should I put a ticket in? sudo port install libffi ---> Fetching libffi ---> Attempting to fetch pyobjc-1.4.tar.gz from http://pyobjc.sourceforge.net/software/ ---> Attempting to fetch pyobjc-1.4.tar.gz from http://downloads.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://easynews.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://ufpr.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://kent.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://jaist.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://svn.macports.org/repository/macports/distfiles/libffi ---> Attempting to fetch pyobjc-1.4.tar.gz from http://svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch pyobjc-1.4.tar.gz from http://svn.macports.org/repository/macports/downloads/libffi Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. -- View this message in context: http://www.nabble.com/libffi%3A--pyobjc-4.1-fetch-failing-tp14791653p14791653.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ------------------------------ Message: 6 Date: Sun, 13 Jan 2008 13:57:49 -0800 (PST) From: LeAnne Lis Subject: libffi: pyobjc-1.4 fetch failing To: macports-users@lists.macosforge.org Message-ID: <14791653.post@talk.nabble.com> Content-Type: text/plain; charset=us-ascii I'm trying to install libffi, which apparently needs a 'pyobjc-1.4.tar.gz' file to install. It's failing on the fetch as follows. Should I put a ticket in? sudo port install libffi ---> Fetching libffi ---> Attempting to fetch pyobjc-1.4.tar.gz from http://pyobjc.sourceforge.net/software/ ---> Attempting to fetch pyobjc-1.4.tar.gz from http://downloads.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://easynews.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://ufpr.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://kent.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://jaist.dl.sourceforge.net/pyobjc ---> Attempting to fetch pyobjc-1.4.tar.gz from http://svn.macports.org/repository/macports/distfiles/libffi ---> Attempting to fetch pyobjc-1.4.tar.gz from http://svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch pyobjc-1.4.tar.gz from http://svn.macports.org/repository/macports/downloads/libffi Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. -- View this message in context: http://www.nabble.com/libffi%3A--pyobjc-1.4-fetch-failing-tp14791653p14791653.html Sent from the MacPorts - Users mailing list archive at Nabble.com. ------------------------------ Message: 7 Date: Sun, 13 Jan 2008 14:01:08 -0800 From: "paul beard" Subject: Re: Using Leopard's ruby with Macports' ruby libraries To: "Douglas Tan" Cc: macports-users@lists.macosforge.org Message-ID: Content-Type: text/plain; charset="iso-8859-1" On Jan 13, 2008 5:49 AM, Douglas Tan wrote: > As the subject states, I'm looking to find a way to use Leopard's ruby > with Macport's ruby libraries like rb-rubygems, rb-mysql, et al. The main > reason for doing this is so that I can use DTrace probes for ruby > applications. > > Would a DTraced ruby be in the horizon for Macports? > I don't have Leopard and won't see it for quite some time. What does it take to make an app DTrace-able? Is this something that can be done in the port? -- Paul Beard / www.paulbeard.org/ There's a diff for the Joyent port of Ruby with Dtrace probes enabled here: http://svn.joyent.com/opensource/dtrace/ruby/patches/ruby-dtrace-1.8.6.diff I'll hazard a guess that this can be compiled into Macports' Ruby during installation? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080113/388d726e/attachment.html ------------------------------ _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users End of macports-users Digest, Vol 17, Issue 59 ********************************************** -- Practical Guile Clever::Tagline::Pending -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080114/8cb0b16f/attachment-0001.html From tabithamc at gmail.com Sun Jan 13 21:17:18 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun Jan 13 21:16:56 2008 Subject: Underscores in some directory user, group names (Postfix MacPort example) In-Reply-To: <7fccb3000801050205h27b0bf34p52b404f3adac5871@mail.gmail.com> References: <7fccb3000801041729t2b45fc10qbd783220da57a6f@mail.gmail.com> <7fccb3000801050205h27b0bf34p52b404f3adac5871@mail.gmail.com> Message-ID: <7fccb3000801132117j34ab51acoba84f5c026d073c4@mail.gmail.com> Hello Jordan, et al: Today I was reading my documentation for running a separate OpenLDAP daemon on an Xserve running Leopard Server. I installed the openldap MacPort (which is based on OpenLDAP version 2.3.35) and I was somewhat surprised that the installation created a user with short name "ldap" and a UID of 500 (with a group short name of "ldap" and a gid of 502). The reason this surprised me is that Apple ships with Leopard Server a compilation instance of OpenLDAP 2.3.27 which is of course the basis for OpenDirectory, and which slapd daemon is run by root apparently at boot time (I presume there is a launchd plist for this but I haven't looked yet). Now, therefore, considering the logic of using underscores as prefixes to avoid namespace collisions since the founders of Unix didn't consider this to be a problem in the 1970s / 1980s, and considering the examples of uids and gids whose corresponding short names that reside in the local domain directory that Apple ships with Leopard Server are, in examples: _postfix _postdrop _guest _xgridagent _spotlight _mysql _svn _www _jabber _sshd and the list goes on ... Why oh why do I not see (when I search the local directory domain of my Leopard Server 10.5.1 instance using WorkgGroup Manager to search on names with underscores in them): _ldap ??? Am I out of my mind that the ommission of "_ldap" is illogical and without basis and is inconsistent with the namespace issue that has been raised herein this discussoin thread thus far? Would it not be possible, for example, for a person to accidentally choose a short user name of "ldap" just as they might also accidentally do so with a name such as "postfix"? Why does life have to be so complicated -- meaning, why do humans create their own unnecessary complexity? We have too many rules we have to remember. Where oh where is my missing friend in Leopard's local directory domain named, "_ldap"? Thus as a result, the openldap MacPort created a separate user account named "ldap". Ugh! Thanks, T.M. On 1/5/08, Tabitha McNerney wrote: > > > > On 1/4/08, Jordan K. Hubbard wrote: > > > > This is because the original designers of Unix neglected to take into > > account the notion of user namespaces - the namespace is flat. That > > means that system or role specific names can conflict with names that > > users would like to use for themselves ( c.f. "admin" or "operator") > > unless you adopt a convention for keeping them separate. That > > convention is the prefix underscore. > > > > - Jordan > > > Jordan, > > Thank you very much. Makes perfect sense. Its hard to find fault with the > original designers of Unix (they probably never would have guessed, decades > later, that individuals in the comfort of their own homes would run Unix on > a machine that sits in their lap)! > > Best, > > T.M. > > On Jan 4, 2008, at 5:29 PM, Tabitha McNerney wrote: > > > > > Hello all -- > > > > > > I just installed the current version of the Postfix port (version > > > 2.4.6) on a Leopard Server system. > > > > > > After the install, I noticed a username and group name of "_postfix" > > > and "_postdrop" respectively, as in: > > > drwx--x--- 2 _postfix _postdrop 102 Jan 4 23:06 public/ > > > drwx-wx--- 2 _postfix _postdrop 102 Jan 4 23:06 maildrop/ > > > This differs from previous Postfix port installations (UID 27 was > > > "postfix" not "_postfix"). This isn't really a MacPorts specific > > > issue but I'm wondering if anyone knows why Apple changed their > > > naming schema on Leopard, for short names such as: > > > > > > from "postfix" to "_postfix" > > > > > > ? > > > > > > I wonder if this has something to do with becoming fully UNIX > > > compliant? POSIX? > > > > > > Mr. Jordan Hubbard, can you offer some wisdom and perspective on > > > this subject? > > > > > > Thank you, > > > > > > T.M. > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080113/4938dd38/attachment.html From jmpp at macports.org Sun Jan 13 21:59:07 2008 From: jmpp at macports.org (Juan Manuel Palacios) Date: Sun Jan 13 21:57:16 2008 Subject: Call for help testing 1.6.1 revamped postflight script Message-ID: As some of you may have seen, I've been improving the postflight script in the release_1_6 branch with the feedback I've received so far, plus some other relevant fixes/improvements. The final product is what will be in the 1.6.1 pkg installer, which I plan to upload to our website to replace the buggy 1.6.0 installers. I've tested it locally on both virgin and customized accounts, extensively, and have found it to work reliably so far. I'd now like to openly call for some wider testing in case I'm missing bugs that my environment is not surfacing. If you're up for it, please grab the script off this URL [1] and take it for a hard ride on whatever environment you can think of. I've tried to bullet-proof it for straight forward functionality in a default environment and to be as polite and non-disruptive as possible in a non-default one. Standard disclaimer applies about this code potentially having bugs that may disrupt your working environment, so do not use on a production machine/account if you can't afford any errors. For those of you wondering what I'm considering as a default environment, have a read at: http://guide.macports.org/#installing.binary.postflight.details That, plus the fact that I only do it for bash and tcsh shells, and the latter only as legacy support for Jaguar and previous accounts. I'm somewhat considering removing such support because tweaking tcsh configuration file has proven a tad difficult: 1) It's not easy to invoke a non-interactive, login tcsh shell session. In a nutshell, so far it has proven impossible for me. This limits my ability to properly test the environment to figure out what I need to add and what I don't, which takes me onto 2) below 2) It's not entirely clear to me whether I should write to ~/.tchsrc, ~/.cshrc or ~/.login (I've heard solid claims for all of them), barring my inability to properly test the environment; 3) barring 2), the form of the settings to be written varies ("set foo = bar" Vs. "setenv foo bar"); 4) I'm by no means a tcsh user, so all I can do is *guess* the best approach in unpleasant tcsh debugging sessions ;-) Various instances of 4), plus very kind help from both Eric Hall and Wilfredo Sanchez at times, have lead me to a combination of ~/.tcshrc with "setenv foo bar" statements, which I think works fairly well. But still, I'd love some experienced tcsh using eyes if available to shed some more light on this aspect of the script (thinking a bit more about it, resolving 1) above would probably solve this entire problem). So, without any further ado, I'd appreciate as much help I can get in testing this script and, in case of failure, getting detailed reports if possible. Success reports are also of course welcomed! Regards,... -jmpp [1] http://trac.macports.org/projects/macports/browser/branches/release_1_6/base/portmgr/dmg/postflight?format=ra From jmpp at macports.org Sun Jan 13 22:01:51 2008 From: jmpp at macports.org (Juan Manuel Palacios) Date: Sun Jan 13 22:00:05 2008 Subject: Call for help testing 1.6.1 revamped postflight script In-Reply-To: References: Message-ID: <46086EEA-2B86-4821-8A13-BEED1E881BC5@macports.org> On Jan 14, 2008, at 1:29 AM, Juan Manuel Palacios wrote: > > [1] http://trac.macports.org/projects/macports/browser/branches/release_1_6/base/portmgr/dmg/postflight?format=ra > That's: http://trac.macports.org/projects/macports/browser/branches/release_1_6/base/portmgr/dmg/postflight?format=raw (missed a w originally) Thanks! -jmpp From ryandesign at macports.org Sun Jan 13 22:15:49 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Jan 13 22:42:51 2008 Subject: sqlite3 update problem In-Reply-To: References: <153C061D-FA28-4292-90DA-3372ABBE5B9F@gmail.com> <28AA4DBD-92CB-4050-9324-4C2769AC7DD0@gmail.com> Message-ID: <288AFD07-CD93-43CD-A9C9-3785D0344865@macports.org> On Jan 13, 2008, at 20:33, Jay Sachs wrote: > On Jan 13, 2008, at 7:11 PM, Garrett Reid wrote: > >> Other ports seem to depend on it, do I need to delete them too? > > If you can afford the time, yes. Just to be clear, I haven't tested > this, it's just something that worked in the past when I ran into > problems upgrading sqlite3. I did just install it successfully, so > I know it builds. > >>> [myhost:~] garrett$ sudo port uninstall sqlite3 >>> ---> The following versions of sqlite3 are currently installed: >>> ---> sqlite3 @3.3.15_0+darwin_8 >>> ---> sqlite3 @3.3.16_0+darwin_8 >>> ---> sqlite3 @3.3.17_0+darwin_8 >>> ---> sqlite3 @3.4.1_0+darwin_8 >>> ---> sqlite3 @3.5.1_0+darwin_8 >>> ---> sqlite3 @3.5.2_0+darwin_8 >>> ---> sqlite3 @3.5.3_1+darwin_8 (active) >>> Error: port uninstall failed: Registry error: Please specify the >>> full version as recorded in the port registry. >>> [myhost:~] garrett$ sudo port uninstall sqlite3 @3.5.3_1+darwin_8 >>> ---> Unable to uninstall sqlite3 3.3.15_0+darwin_8, the >>> following ports depend on it: >>> ---> apr-util >>> ---> apr-util >>> ---> apr-util >>> Error: port uninstall failed: Please uninstall the ports that >>> depend on sqlite3 first. >> >> Or am I going about this wrong? >> Sorry for being so helpless, I'll get macports figured eventually :P > > Just need to "force" the uninstall, with the "-f" flag. To be more clear: Garret: No, you do not need to uninstall the ports that depend on sqlite3. You can, but you most likely don't have to. Just forcibly uninstall all versions of sqlite3. Then install sqlite3. Run these commands: sudo port -f uninstall sqlite3 @3.3.15_0+darwin_8 sudo port -f uninstall sqlite3 @3.3.16_0+darwin_8 sudo port -f uninstall sqlite3 @3.3.17_0+darwin_8 sudo port -f uninstall sqlite3 @3.4.1_0+darwin_8 sudo port -f uninstall sqlite3 @3.5.1_0+darwin_8 sudo port -f uninstall sqlite3 @3.5.2_0+darwin_8 sudo port -f uninstall sqlite3 @3.5.3_1+darwin_8 sudo port clean --work sqlite3 sudo port install sqlite3 From ryandesign at macports.org Sun Jan 13 23:57:18 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Jan 13 23:57:42 2008 Subject: View of non maintained packages In-Reply-To: References: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> <1d5b78a10801131325x5b2cac07s49709aa7a1164d21@mail.gmail.com> <25890C56-1FFA-461F-85F1-6304024B98B6@macports.org> <478A9D05.4040707@macports.org> Message-ID: <770B4428-11C5-4578-9D76-57A2E57D1ADE@macports.org> On Jan 13, 2008, at 17:37, Rolf W?rdemann wrote: > Am 14.01.2008 um 00:21 schrieb Rainer M?ller: > >> Rolf W?rdemann wrote: >> >>> But it seems that we need more committers before asking on >>> the website - if we get mainatiners for a quarter of the ports >>> there will be much work (if my case with the one to three weeks >>> was not a single case) ;) >> >> Maybe we should have someone who is responsible for committing >> updates >> for particular port categories. I think the problem at the moment is >> that a port update is committed if someone looked into Trac to see >> any >> pending updates... So this is rather random when a port update is >> committed. > > Maybe an commit-group would be an idea ;) (something like the > support-group > at our office ;) Do you mean a group of people who do nothing but commit things that others submit? If we have people who are interested in performing that function, then sure. But we don't want everything that's submitted into Trac just blindly committed into Subversion. We need the committer to be aware of the changes that are being made, to police the changes in a way. Don't commit patches that do multiple things; break it into separate patches or ask the contributor to do so. Don't commit patches that make whitespace changes to the entire portfile in addition to functional changes. Don't commit patches that obviously revert a previous revision without the contributor explaining why. Don't commit patches that use inadvisable practices without first discussing these with the contributor. And so forth. In order to know these things, it helps if such a committer is also an accomplished port maintainer/author. I think what we need are committers who are interested in each category of software. I occasionally look through the unassigned tickets and either try to handle them (new ports, or patches for unmaintained ports) or assign them to their ports' maintainers. But some tickets I don't deal with, like most tickets for Python modules or most Gnome tickets, because I don't use or sufficiently understand Python and Gnome. We need committers who are interested in and proficient in Python and Gnome (and maybe some other categories) who will deal with those tickets. From ballagas at gmail.com Mon Jan 14 00:05:02 2008 From: ballagas at gmail.com (Tico Ballagas) Date: Mon Jan 14 00:04:43 2008 Subject: All HTTP Fetches fail, only FTP working Message-ID: <3D7A83C3-2002-4F56-A6AF-1230395B936D@gmail.com> Hello- I'm having a strange problem where all of the fetch attempts using HTTP fail, but all FTP work fine (see output below). Any ideas what might be going wrong? I've tried uninstalling and reinstalling MacPorts, but the problem persists. Currently, as a workaround, I have to manually download packages and place them in the /opt/local/ directory myself. Thanks -Tico ---> Fetching curl ---> Attempting to fetch curl-7.17.1.tar.bz2 from http:// curl.haxx.se/download/ ---> Attempting to fetch curl-7.17.1.tar.bz2 from ftp://ftp.sunet.se/ pub/www/utilities/curl/ ---> Verifying checksum(s) for curl ---> Extracting curl ---> Configuring curl ---> Building curl with target all ---> Staging curl into destroot ---> Installing curl 7.17.1_0+darwin_8 ---> Activating curl 7.17.1_0+darwin_8 ---> Cleaning curl ---> Fetching openssh ---> Attempting to fetch openssh-4.7p1.tar.gz from http:// mirror.roothell.org/pub/OpenBSD/OpenSSH/portable ---> Attempting to fetch openssh-4.7p1.tar.gz from http://ftp- stud.fht-esslingen.de/pub/OpenBSD/OpenSSH/portable ---> Attempting to fetch openssh-4.7p1.tar.gz from http:// mirror.paranoidbsd.org/pub/OpenBSD/OpenSSH/portable ---> Attempting to fetch openssh-4.7p1.tar.gz from ftp:// ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable ---> Verifying checksum(s) for openssh ---> Extracting openssh ---> Configuring openssh ---> Building openssh with target all ---> Staging openssh into destroot ---> Creating launchd control script ########################################################### # A startup item has been generated that will aid in # starting openssh with launchd. It is disabled # by default. Execute the following command to start it, # and to cause it to launch at startup: # # sudo launchctl load -w /Library/LaunchDaemons/ org.macports.OpenSSH.plist ########################################################### ---> Installing openssh 4.7p1_1+darwin_8 ---> Activating openssh 4.7p1_1+darwin_8 ---> Cleaning openssh ---> Fetching perl5.8 ---> Attempting to fetch perl-5.8.8.tar.bz2 from http://www.cpan.org/ src/5.0/ ---> Attempting to fetch perl-5.8.8.tar.bz2 from http:// svn.macports.org/repository/macports/distfiles/perl5.8 ---> Attempting to fetch perl-5.8.8.tar.bz2 from http:// svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch perl-5.8.8.tar.bz2 from http:// svn.macports.org/repository/macports/downloads/perl5.8 Error: Target org.macports.fetch returned: fetch failed Error: The following dependencies failed to build: p5-error perl5.8 rsync popt Error: Status 1 encountered during processing. From jochen at fhi-berlin.mpg.de Mon Jan 14 00:20:40 2008 From: jochen at fhi-berlin.mpg.de (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Mon Jan 14 00:20:31 2008 Subject: [OS X Emacs] spell checking - once more In-Reply-To: References: <91621673-1DCF-4123-8688-A75F08962D06@fhi-berlin.mpg.de> Message-ID: <31DC4C0A-47C1-4A7D-8E5A-7773CD075A65@fhi-berlin.mpg.de> On 14.01.2008, at 08:58, Alex Hamann wrote: > The reason is simply that I ran into a posting on another mailing- > list that made me notice that MacPorts creates a ~/.profile upon > install, to add /opt/local/bin and /opt/local/sbin *before* the OS X > defaults /usr/bin and /usr/sbin in $PATH. While I do not see the problem here... You can simply change that by opening the configuration file in an editor and change the PATH to whatever you want... You can even leae MacPorts $prefix completely out and always call the programs specifying the complete path, if you consider that useful. > I want to investigate deeper wether I find this behaviour of > modifying OS X instead of adding to it concerning This is definitely a wrong picture you have here. a) This behaviour is common on Un*x system and not considered modifying the OS. b) This setting is only for shells. c) You can still always call the original OS tool y specifying the PATH. d) It is very easy to change the PAH to whatever you want. MacPorts is simply providing a default setting. The one which is most appropriate for the average system/user... > alex (who is still hoping for a hint regarding his original > problem :-) Use MacPorts' aspell! ;-) Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll From garrett.reid at gmail.com Mon Jan 14 00:35:14 2008 From: garrett.reid at gmail.com (Garrett Reid) Date: Mon Jan 14 00:34:50 2008 Subject: sqlite3 update problem In-Reply-To: <288AFD07-CD93-43CD-A9C9-3785D0344865@macports.org> References: <153C061D-FA28-4292-90DA-3372ABBE5B9F@gmail.com> <28AA4DBD-92CB-4050-9324-4C2769AC7DD0@gmail.com> <288AFD07-CD93-43CD-A9C9-3785D0344865@macports.org> Message-ID: <26C540E2-3171-4E03-B92C-7D9A75137E0E@gmail.com> I got things figured out from Jay's reply, thank you for the additional clarification though! (all that was needed was uninstalling the active one, installing new one, and cleaning.) Thanks! Garrett On Jan 13, 2008, at 10:15 PM, Ryan Schmidt wrote: > > On Jan 13, 2008, at 20:33, Jay Sachs wrote: > >> On Jan 13, 2008, at 7:11 PM, Garrett Reid wrote: >> >>> Other ports seem to depend on it, do I need to delete them too? >> >> If you can afford the time, yes. Just to be clear, I haven't tested >> this, it's just something that worked in the past when I ran into >> problems upgrading sqlite3. I did just install it successfully, so >> I know it builds. >> >>>> [myhost:~] garrett$ sudo port uninstall sqlite3 >>>> .... >>>> Error: port uninstall failed: Please uninstall the ports that >>>> depend on sqlite3 first. >>> >>> Or am I going about this wrong? >>> Sorry for being so helpless, I'll get macports figured eventually :P >> >> Just need to "force" the uninstall, with the "-f" flag. > > To be more clear: Garret: No, you do not need to uninstall the ports > that depend on sqlite3. You can, but you most likely don't have to. > Just forcibly uninstall all versions of sqlite3. Then install > sqlite3. Run these commands: > > > sudo port -f uninstall sqlite3 @3.3.15_0+darwin_8 > sudo port -f uninstall sqlite3 @3.3.16_0+darwin_8 > sudo port -f uninstall sqlite3 @3.3.17_0+darwin_8 > sudo port -f uninstall sqlite3 @3.4.1_0+darwin_8 > sudo port -f uninstall sqlite3 @3.5.1_0+darwin_8 > sudo port -f uninstall sqlite3 @3.5.2_0+darwin_8 > sudo port -f uninstall sqlite3 @3.5.3_1+darwin_8 > sudo port clean --work sqlite3 > sudo port install sqlite3 From ryandesign at macports.org Mon Jan 14 00:40:32 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 14 00:40:55 2008 Subject: All HTTP Fetches fail, only FTP working In-Reply-To: <3D7A83C3-2002-4F56-A6AF-1230395B936D@gmail.com> References: <3D7A83C3-2002-4F56-A6AF-1230395B936D@gmail.com> Message-ID: <66A6DA67-4427-4575-82A4-BD3714E96CF8@macports.org> On Jan 14, 2008, at 02:05, Tico Ballagas wrote: > I'm having a strange problem where all of the fetch attempts using > HTTP fail, but all FTP work fine (see output below). Any ideas > what might be going wrong? > > I've tried uninstalling and reinstalling MacPorts, but the problem > persists. Currently, as a workaround, I have to manually download > packages and place them in the /opt/local/ directory myself. Tell us more about your network. Work network or home? Restrictive firewall? Proxy? From jochen at fhi-berlin.mpg.de Mon Jan 14 00:44:52 2008 From: jochen at fhi-berlin.mpg.de (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Mon Jan 14 00:44:31 2008 Subject: View of non maintained packages In-Reply-To: <770B4428-11C5-4578-9D76-57A2E57D1ADE@macports.org> References: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> <1d5b78a10801131325x5b2cac07s49709aa7a1164d21@mail.gmail.com> <25890C56-1FFA-461F-85F1-6304024B98B6@macports.org> <478A9D05.4040707@macports.org> <770B4428-11C5-4578-9D76-57A2E57D1ADE@macports.org> Message-ID: On 14.01.2008, at 08:57, Ryan Schmidt wrote: > > On Jan 13, 2008, at 17:37, Rolf W?rdemann wrote: > >> Am 14.01.2008 um 00:21 schrieb Rainer M?ller: >> >>> Rolf W?rdemann wrote: >>> >>>> But it seems that we need more committers before asking on >>>> the website - if we get mainatiners for a quarter of the ports >>>> there will be much work (if my case with the one to three weeks >>>> was not a single case) ;) >>> >>> Maybe we should have someone who is responsible for committing >>> updates >>> for particular port categories. I think the problem at the moment is >>> that a port update is committed if someone looked into Trac to see >>> any >>> pending updates... So this is rather random when a port update is >>> committed. >> > Do you mean a group of people who do nothing but commit things that > others submit? If we have people who are interested in performing > that function, then sure. > > But we don't want everything that's submitted into Trac just blindly > committed into Subversion. We need the committer to be aware of the > changes that are being made, to police the changes in a way. Don't > commit patches that do multiple things; break it into separate > patches or ask the contributor to do so. Don't commit patches that > make whitespace changes to the entire portfile in addition to > functional changes. Don't commit patches that obviously revert a > previous revision without the contributor explaining why. Don't > commit patches that use inadvisable practices without first > discussing these with the contributor. And so forth. In order to > know these things, it helps if such a committer is also an > accomplished port maintainer/author. > > I think what we need are committers who are interested in each > category of software. I occasionally look through the unassigned > tickets and either try to handle them (new ports, or patches for > unmaintained ports) or assign them to their ports' maintainers. But > some tickets I don't deal with, like most tickets for Python modules > or most Gnome tickets, because I don't use or sufficiently > understand Python and Gnome. We need committers who are interested > in and proficient in Python and Gnome (and maybe some other > categories) who will deal with those tickets. I think this is the way to go. What do we need? First, we need people to volunteer for group-committers on all groups! Of course individuals can decide themselves whether they cannot perform this task at all or perform it on one or multiple port groups. As Ryan said: he can do it on some (practically does it on several) but not on others... Second, we need to "announce" these port-group committers, i.e., on the MacPorts Wiki. Preferably the committers of a single group are placed on a -commit-pending@ mailing list... Third, some means to assign a committed patch to one or, if appropriate, multiple port groups. Optimally, this would be automatic based on the Portfile. Then the -commit-pending@ is automatically emailed. Obviously, a poor mans version would to request the ticket creator to add the correct -commit-pending@ to the cc: field (good enough for a test of the whole system). Fourth, the people behind -commit-pending@ need the time to look at these tickets on a (nearly) daily basis... From my perspective this is te hardest point! Fifth: we need more volunteers! a) more maintainers b) more people with commit-rights c) group-committers ... Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080114/34c22617/PGP.bin From jkh at apple.com Mon Jan 14 00:55:41 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Mon Jan 14 00:56:19 2008 Subject: Underscores in some directory user, group names (Postfix MacPort example) In-Reply-To: <7fccb3000801132117j34ab51acoba84f5c026d073c4@mail.gmail.com> References: <7fccb3000801041729t2b45fc10qbd783220da57a6f@mail.gmail.com> <7fccb3000801050205h27b0bf34p52b404f3adac5871@mail.gmail.com> <7fccb3000801132117j34ab51acoba84f5c026d073c4@mail.gmail.com> Message-ID: <998BD549-7CAB-477A-AAC0-9D13BD164054@apple.com> I'm sorry, Tabitha, but I've read this message twice and I still have no idea just what question it is you're actually asking here. :-) - Jordan On Jan 13, 2008, at 9:17 PM, Tabitha McNerney wrote: > Hello Jordan, et al: > > Today I was reading my documentation for running a separate OpenLDAP > daemon on an Xserve running Leopard Server. I installed the openldap > MacPort (which is based on OpenLDAP version 2.3.35) and I was > somewhat surprised that the installation created a user with short > name "ldap" and a UID of 500 (with a group short name of "ldap" and > a gid of 502). The reason this surprised me is that Apple ships with > Leopard Server a compilation instance of OpenLDAP 2.3.27 which is of > course the basis for OpenDirectory, and which slapd daemon is run by > root apparently at boot time (I presume there is a launchd plist for > this but I haven't looked yet). > > Now, therefore, considering the logic of using underscores as > prefixes to avoid namespace collisions since the founders of Unix > didn't consider this to be a problem in the 1970s / 1980s, and > considering the examples of uids and gids whose corresponding short > names that reside in the local domain directory that Apple ships > with Leopard Server are, in examples: > > _postfix > _postdrop > _guest > _xgridagent > _spotlight > _mysql > _svn > _www > _jabber > _sshd > > and the list goes on ... > > Why oh why do I not see (when I search the local directory domain of > my Leopard Server 10.5.1 instance using WorkgGroup Manager to search > on names with underscores in them): > > _ldap ??? > > Am I out of my mind that the ommission of "_ldap" is illogical and > without basis and is inconsistent with the namespace issue that has > been raised herein this discussoin thread thus far? Would it not be > possible, for example, for a person to accidentally choose a short > user name of "ldap" just as they might also accidentally do so with > a name such as "postfix"? Why does life have to be so complicated -- > meaning, why do humans create their own unnecessary complexity? We > have too many rules we have to remember. Where oh where is my > missing friend in Leopard's local directory domain named, "_ldap"? > Thus as a result, the openldap MacPort created a separate user > account named "ldap". Ugh! > > Thanks, > > T.M. > > On 1/5/08, Tabitha McNerney wrote: > > > On 1/4/08, Jordan K. Hubbard < jkh@apple.com> wrote: > This is because the original designers of Unix neglected to take into > account the notion of user namespaces - the namespace is flat. That > means that system or role specific names can conflict with names that > users would like to use for themselves ( c.f. "admin" or "operator") > unless you adopt a convention for keeping them separate. That > convention is the prefix underscore. > > - Jordan > > Jordan, > > Thank you very much. Makes perfect sense. Its hard to find fault > with the original designers of Unix (they probably never would have > guessed, decades later, that individuals in the comfort of their own > homes would run Unix on a machine that sits in their lap)! > > Best, > > T.M. > > On Jan 4, 2008, at 5:29 PM, Tabitha McNerney wrote: > > > Hello all -- > > > > I just installed the current version of the Postfix port (version > > 2.4.6) on a Leopard Server system. > > > > After the install, I noticed a username and group name of "_postfix" > > and "_postdrop" respectively, as in: > > drwx--x--- 2 _postfix _postdrop 102 Jan 4 23:06 public/ > > drwx-wx--- 2 _postfix _postdrop 102 Jan 4 23:06 maildrop/ > > This differs from previous Postfix port installations (UID 27 was > > "postfix" not "_postfix"). This isn't really a MacPorts specific > > issue but I'm wondering if anyone knows why Apple changed their > > naming schema on Leopard, for short names such as: > > > > from "postfix" to "_postfix" > > > > ? > > > > I wonder if this has something to do with becoming fully UNIX > > compliant? POSIX? > > > > Mr. Jordan Hubbard, can you offer some wisdom and perspective on > > this subject? > > > > Thank you, > > > > T.M. > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080114/8e5e5466/attachment-0001.html From rowue at digitalis.org Mon Jan 14 01:23:00 2008 From: rowue at digitalis.org (=?ISO-8859-1?Q?Rolf_W=FCrdemann?=) Date: Mon Jan 14 01:22:45 2008 Subject: View of non maintained packages In-Reply-To: <770B4428-11C5-4578-9D76-57A2E57D1ADE@macports.org> References: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> <1d5b78a10801131325x5b2cac07s49709aa7a1164d21@mail.gmail.com> <25890C56-1FFA-461F-85F1-6304024B98B6@macports.org> <478A9D05.4040707@macports.org> <770B4428-11C5-4578-9D76-57A2E57D1ADE@macports.org> Message-ID: <9C3C3F24-D7FF-4BAA-BA42-7A98235AD78D@digitalis.org> Am 14.01.2008 um 08:57 schrieb Ryan Schmidt: > > On Jan 13, 2008, at 17:37, Rolf W?rdemann wrote: > >> Am 14.01.2008 um 00:21 schrieb Rainer M?ller: >> >>> Rolf W?rdemann wrote: >>> >>>> [Need of more committers] >>> [Port Categories] >> >> Maybe an commit-group would be an idea ;) (something like the >> support-group >> at our office ;) > > Do you mean a group of people who do nothing but commit things that > others submit? If we have people who are interested in performing > that function, then sure. Not but nothing (o.k. that's different to support parts at office) - but beeing responsible ;) but I think your approach below is the better one ;) > > But we don't want everything that's submitted into Trac just > blindly committed into Subversion. We need the committer to be > aware of the changes that are being made, to police the changes in > a way. Don't commit patches that do multiple things; break it into > separate patches or ask the contributor to do so. Don't commit > patches that make whitespace changes to the entire portfile in > addition to functional changes. Don't commit patches that obviously > revert a previous revision without the contributor explaining why. > Don't commit patches that use inadvisable practices without first > discussing these with the contributor. And so forth. In order to > know these things, it helps if such a committer is also an > accomplished port maintainer/author. Definitive. (And perhaps we should state this better in the documentation - otherwise one guy can set up an update for bugfix or new version, read the documentation, tidy up, submit and get the message "hey! you better break this in a few steps ;) (I've just made an update to gwyddion and tidy the portfile in one step ;) > > I think what we need are committers who are interested in each > category of software. I occasionally look through the unassigned > tickets and either try to handle them (new ports, or patches for > unmaintained ports) or assign them to their ports' maintainers. But > some tickets I don't deal with, like most tickets for Python > modules or most Gnome tickets, because I don't use or sufficiently > understand Python and Gnome. We need committers who are interested > in and proficient in Python and Gnome (and maybe some other > categories) who will deal with those tickets. > *g* - o.k. - thats the better approach (having people which where insterested in each category of software and feel responsible ;) But a problem will be a bug fix that's in the ticket (and the fixing one (maintainer or other person) have no possibillity to change the status - than we have to look throught all tickets complete or the fixing one must open a new ticket (which is perhaps stated in the documentation ;) reg's Rolf -- Security is an illusion - Datasecurity twice Rolf W?rdemann - private: rowue@digitalis.org - office: rowue@crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue@digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932 -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: Signierter Teil der Nachricht Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080114/7075334b/PGP.bin From ryandesign at macports.org Mon Jan 14 02:10:55 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 14 02:11:18 2008 Subject: View of non maintained packages In-Reply-To: <9C3C3F24-D7FF-4BAA-BA42-7A98235AD78D@digitalis.org> References: <1d5b78a10801131309x6b4eb045w7fdd3c4d1317bd18@mail.gmail.com> <0046C8F1-7BC1-4AE9-983D-C232AEC62696@digitalis.org> <1d5b78a10801131325x5b2cac07s49709aa7a1164d21@mail.gmail.com> <25890C56-1FFA-461F-85F1-6304024B98B6@macports.org> <478A9D05.4040707@macports.org> <770B4428-11C5-4578-9D76-57A2E57D1ADE@macports.org> <9C3C3F24-D7FF-4BAA-BA42-7A98235AD78D@digitalis.org> Message-ID: On Jan 14, 2008, at 03:23, Rolf W?rdemann wrote: >> I think what we need are committers who are interested in each >> category of software. I occasionally look through the unassigned >> tickets and either try to handle them (new ports, or patches for >> unmaintained ports) or assign them to their ports' maintainers. >> But some tickets I don't deal with, like most tickets for Python >> modules or most Gnome tickets, because I don't use or sufficiently >> understand Python and Gnome. We need committers who are interested >> in and proficient in Python and Gnome (and maybe some other >> categories) who will deal with those tickets. > > *g* - o.k. - thats the better approach (having people which where > insterested in each category of software > and feel responsible ;) > > But a problem will be a bug fix that's in the ticket (and the > fixing one (maintainer or other person) > have no possibillity to change the status - than we have to look > throught all tickets complete or > the fixing one must open a new ticket (which is perhaps stated in > the documentation ;) I didn't quite understand your last paragraph? From tabithamc at gmail.com Mon Jan 14 03:57:10 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Mon Jan 14 03:56:47 2008 Subject: Underscores in some directory user, group names (Postfix MacPort example) In-Reply-To: <998BD549-7CAB-477A-AAC0-9D13BD164054@apple.com> References: <7fccb3000801041729t2b45fc10qbd783220da57a6f@mail.gmail.com> <7fccb3000801050205h27b0bf34p52b404f3adac5871@mail.gmail.com> <7fccb3000801132117j34ab51acoba84f5c026d073c4@mail.gmail.com> <998BD549-7CAB-477A-AAC0-9D13BD164054@apple.com> Message-ID: <7fccb3000801140357h43b8707en6655a2c66f4ca419@mail.gmail.com> On 1/13/08, Jordan K. Hubbard wrote: > > I'm sorry, Tabitha, but I've read this message twice and I still have no > idea just what question it is you're actually asking here. :-) > - Jordan > Jordan, I'll try to rephrase my question to hopefully clarify: Why doesn't Apple include, in Mac OS X Server 10.5, a local directory entry of a user user named "_ldap"? A follow up question: What criteria did Apple use for selecting names, in the local directory domain of Mac OS X Server 10.5, which were eligible to receive an underscore prefix? What triggered my question was the MacPorts openldap installation on Leopard Server creates a local directory user named "ldap" but I half expected in Leopard to find a prexisting user named "_ldap" in the local directory (courtesy of Apple), considering some of the other underscored prefixed Unix user names that prexist courtesy of Apple as _postfix Thank you, T.M. On Jan 13, 2008, at 9:17 PM, Tabitha McNerney wrote: > > Hello Jordan, et al: > > Today I was reading my documentation for running a separate OpenLDAP > daemon on an Xserve running Leopard Server. I installed the openldap MacPort > (which is based on OpenLDAP version 2.3.35) and I was somewhat surprised > that the installation created a user with short name "ldap" and a UID of 500 > (with a group short name of "ldap" and a gid of 502). The reason this > surprised me is that Apple ships with Leopard Server a compilation instance > of OpenLDAP 2.3.27 which is of course the basis for OpenDirectory, and > which slapd daemon is run by root apparently at boot time (I presume there > is a launchd plist for this but I haven't looked yet). > > Now, therefore, considering the logic of using underscores as prefixes to > avoid namespace collisions since the founders of Unix didn't consider this > to be a problem in the 1970s / 1980s, and considering the examples of uids > and gids whose corresponding short names that reside in the local domain > directory that Apple ships with Leopard Server are, in examples: > > _postfix > _postdrop > _guest > _xgridagent > _spotlight > _mysql > _svn > _www > _jabber > _sshd > > and the list goes on ... > > Why oh why do I not see (when I search the local directory domain of my > Leopard Server 10.5.1 instance using WorkgGroup Manager to search on names > with underscores in them): > > _ldap ??? > > Am I out of my mind that the ommission of "_ldap" is illogical and without > basis and is inconsistent with the namespace issue that has been raised > herein this discussoin thread thus far? Would it not be possible, for > example, for a person to accidentally choose a short user name of "ldap" > just as they might also accidentally do so with a name such as "postfix"? > Why does life have to be so complicated -- meaning, why do humans create > their own unnecessary complexity? We have too many rules we have to > remember. Where oh where is my missing friend in Leopard's local directory > domain named, "_ldap"? Thus as a result, the openldap MacPort created a > separate user account named "ldap". Ugh! > > Thanks, > > T.M. > > On 1/5/08, Tabitha McNerney wrote: > > > > > > > > On 1/4/08, Jordan K. Hubbard < jkh@apple.com> wrote: > > > > > > This is because the original designers of Unix neglected to take into > > > account the notion of user namespaces - the namespace is flat. That > > > means that system or role specific names can conflict with names that > > > users would like to use for themselves ( c.f. "admin" or "operator") > > > unless you adopt a convention for keeping them separate. That > > > convention is the prefix underscore. > > > > > > - Jordan > > > > > > Jordan, > > > > Thank you very much. Makes perfect sense. Its hard to find fault with > > the original designers of Unix (they probably never would have guessed, > > decades later, that individuals in the comfort of their own homes would run > > Unix on a machine that sits in their lap)! > > > > Best, > > > > T.M. > > > > On Jan 4, 2008, at 5:29 PM, Tabitha McNerney wrote: > > > > > > > Hello all -- > > > > > > > > I just installed the current version of the Postfix port (version > > > > 2.4.6) on a Leopard Server system. > > > > > > > > After the install, I noticed a username and group name of "_postfix" > > > > > > > and "_postdrop" respectively, as in: > > > > drwx--x--- 2 _postfix _postdrop 102 Jan 4 23:06 public/ > > > > drwx-wx--- 2 _postfix _postdrop 102 Jan 4 23:06 maildrop/ > > > > This differs from previous Postfix port installations (UID 27 was > > > > "postfix" not "_postfix"). This isn't really a MacPorts specific > > > > issue but I'm wondering if anyone knows why Apple changed their > > > > naming schema on Leopard, for short names such as: > > > > > > > > from "postfix" to "_postfix" > > > > > > > > ? > > > > > > > > I wonder if this has something to do with becoming fully UNIX > > > > compliant? POSIX? > > > > > > > > Mr. Jordan Hubbard, can you offer some wisdom and perspective on > > > > this subject? > > > > > > > > Thank you, > > > > > > > > T.M. > > > > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080114/30f02af7/attachment.html From elabsjng at mac.com Mon Jan 14 04:06:27 2008 From: elabsjng at mac.com (elabsjng@mac.com) Date: Mon Jan 14 04:06:05 2008 Subject: OS X and shared Libraries Message-ID: Hi, When macports compiles and links an application are the shared library paths hard coded into the binary? I s this the typical behaviour on OS X? Best Regards, Simon. From frstan at bellsouth.net Mon Jan 14 04:15:30 2008 From: frstan at bellsouth.net (William Davis) Date: Mon Jan 14 04:15:11 2008 Subject: Using Leopard's ruby with Macports' ruby libraries In-Reply-To: <478ACB2B.5030608@practicalguile.com> References: <478ACB2B.5030608@practicalguile.com> Message-ID: <77FA88F3-D531-46C4-B33F-352478236371@bellsouth.net> On Jan 13, 2008, at 9:38 PM, Douglas Tan wrote: > When replying, please edit your Subject line so it is more specific > than "Re: Contents of macports-users digest..." > Douglas, would you pleeeeeease do some editing before you send a reply to a digest message. It really isnt needed or helpful to resend the entire digest every time you reply. William Davis frstanATbellsouthDOTnet Mac OS X.5.1 Darwin 9.1.0 X11.app 2.1.2 - (xorg-server 1.3.0-apple7) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From stefan.schwarzer at grid.unep.ch Mon Jan 14 05:35:20 2008 From: stefan.schwarzer at grid.unep.ch (Stefan Schwarzer) Date: Mon Jan 14 05:35:02 2008 Subject: Error messages with Freetype and XFree86 Message-ID: <0CA49DE2-8EDB-40FF-B124-4B0D93681EF3@grid.unep.ch> Hi, I got the following error when trying to install FREETYPE, and in a later effort XFree86. Can anyone tell me what it means and if there is a solution to this? Thanks a lot, Stef gridmac7:Documents schwarzer$ sudo /opt/local/bin/port install freetype Password: ---> Fetching freetype ---> Attempting to fetch freetype-2.3.5.tar.bz2 from http://download.savannah.gnu.org/releases/freetype/ ---> Verifying checksum(s) for freetype ---> Extracting freetype ---> Applying patches to freetype ---> Configuring freetype ---> Building freetype with target all ---> Staging freetype into destroot ---> Installing freetype 2.3.5_1 ---> Activating freetype 2.3.5_1 ---> Cleaning freetype gridmac7:Documents schwarzer$ sudo /opt/local/bin/port install gd2 ---> Fetching XFree86 ---> Attempting to fetch XFree86-4.7.0-src-1.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ ---> Attempting to fetch XFree86-4.7.0-src-2.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ ---> Attempting to fetch XFree86-4.7.0-src-3.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ ---> Attempting to fetch XFree86-4.7.0-src-4.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ ---> Attempting to fetch XFree86-4.7.0-src-5.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ ---> Verifying checksum(s) for XFree86 ---> Extracting XFree86 ---> Applying patches to XFree86 ---> Configuring XFree86 ---> Building XFree86 with target World Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_XFree86/work/xc" && make World " returned error 2 Command output: including in lib/dps... checking ../../config/pswrap/pswrap over in ../../config/pswrap first... /usr/bin/cc -Os -fno-strict-aliasing -Wall -Wpointer-arith -no-cpp- precomp -I. -I../../exports/include "-I/opt/local/var/macports/ build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_XFree86/work/include" -D__i386__ - D__DARWIN__ -DNO_ALLOCA - DCSRG_BASED -DXENVIRONMENT -c -o main.o main.c yacc -d pswparser.y conflicts: 1 shift/reduce mv -f y.tab.c pswparser.c + mv -f y.tab.h pswparser.h /usr/bin/cc -Os -fno-strict-aliasing -Wall -Wpointer-arith -no-cpp- precomp -I. -I../../exports/include "-I/opt/local/var/macports/ build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_XFree86/work/include" -D__i386__ - D__DARWIN__ -DNO_ALLOCA - DCSRG_BASED -DXENVIRONMENT -c -o pswparser.o pswparser.c flex -l lexer.l lexer.l:108: bad character: % lexer.l:108: unknown error processing section 1 lexer.l:108: unknown error processing section 1 lexer.l:108: bad character: 3 lexer.l:108: bad character: 5 lexer.l:108: bad character: 0 lexer.l:108: bad character: 0 lexer.l:109: bad character: % lexer.l:109: unknown error processing section 1 lexer.l:109: bad character: 2 lexer.l:109: bad character: 5 lexer.l:109: bad character: 0 lexer.l:109: bad character: 0 make[4]: *** [lexer.c] Error 1 okay, continuing in lib/dps ../../config/pswrap/pswrap -a -o dpsclrops.c -h dpsclrops.h dpsclrops.psw make[3]: ../../config/pswrap/pswrap: Command not found make[3]: *** [dpsclrops.c] Error 127 make[2]: *** [includes] Error 1 make[1]: *** [includes] Error 1 make: *** [World] Error 2 Error: The following dependencies failed to build: XFree86 fontconfig Error: Status 1 encountered during processing. gridmac7:Documents schwarzer$ sudo /opt/local/bin/port install XFree86 ---> Building XFree86 with target World Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_XFree86/work/xc" && make World " returned error 2 Command output: including in lib/dps... checking ../../config/pswrap/pswrap over in ../../config/pswrap first... /usr/bin/cc -Os -fno-strict-aliasing -Wall -Wpointer-arith -no-cpp- precomp -I. -I../../exports/include "-I/opt/local/var/macports/ build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_XFree86/work/include" -D__i386__ - D__DARWIN__ -DNO_ALLOCA - DCSRG_BASED -DXENVIRONMENT -c -o main.o main.c yacc -d pswparser.y conflicts: 1 shift/reduce mv -f y.tab.c pswparser.c + mv -f y.tab.h pswparser.h /usr/bin/cc -Os -fno-strict-aliasing -Wall -Wpointer-arith -no-cpp- precomp -I. -I../../exports/include "-I/opt/local/var/macports/ build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_XFree86/work/include" -D__i386__ - D__DARWIN__ -DNO_ALLOCA - DCSRG_BASED -DXENVIRONMENT -c -o pswparser.o pswparser.c flex -l lexer.l lexer.l:108: bad character: % lexer.l:108: unknown error processing section 1 lexer.l:108: unknown error processing section 1 lexer.l:108: bad character: 3 lexer.l:108: bad character: 5 lexer.l:108: bad character: 0 lexer.l:108: bad character: 0 lexer.l:109: bad character: % lexer.l:109: unknown error processing section 1 lexer.l:109: bad character: 2 lexer.l:109: bad character: 5 lexer.l:109: bad character: 0 lexer.l:109: bad character: 0 make[4]: *** [lexer.c] Error 1 okay, continuing in lib/dps ../../config/pswrap/pswrap -a -o dpsclrops.c -h dpsclrops.h dpsclrops.psw make[3]: ../../config/pswrap/pswrap: Command not found make[3]: *** [dpsclrops.c] Error 127 make[2]: *** [includes] Error 1 make[1]: *** [includes] Error 1 make: *** [World] Error 2 Error: Status 1 encountered during processing. gridmac7:Documents schwarzer$ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080114/4b307fb5/attachment.html From matrixm at gmail.com Mon Jan 14 05:37:36 2008 From: matrixm at gmail.com (Matrix Mole) Date: Mon Jan 14 05:37:18 2008 Subject: OS X and shared Libraries In-Reply-To: References: Message-ID: <478B65A0.9030104@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 elabsjng@mac.com wrote: | Hi, | | When macports compiles and links an application are the shared library | paths hard coded into the binary? I s this the typical behaviour on OS X? ~From my understanding, this is typical behavior on just about any platform that has software compiled with shared library support. When a binary file is compiled, during the configuration step there is usually an option that determines the shard library path. If you wanted to change the location of shared libraries you'd have to re-run the configure script with the new library directory and then recompile the software. Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHi2WgNtosHRPp48MRAmSpAKCBixIn2Ingwtdl6pUXq1PCk/wNWgCfTjqp u5V7n4lxQgBKerY5sXSdxTc= =y/xT -----END PGP SIGNATURE----- From elabsjng at mac.com Mon Jan 14 05:52:36 2008 From: elabsjng at mac.com (elabsjng@mac.com) Date: Mon Jan 14 05:52:15 2008 Subject: OS X and shared Libraries In-Reply-To: <478B65A0.9030104@gmail.com> References: <478B65A0.9030104@gmail.com> Message-ID: Hi, Thanks for the reply. Maybe I misunderstand but I though, on Linux, the run-time linker had a set of search paths to look for shared libraries? Best Regards, Simon. On 14 Jan 2008, at 13:37, Matrix Mole wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > elabsjng@mac.com wrote: > | Hi, > | > | When macports compiles and links an application are the shared > library > | paths hard coded into the binary? I s this the typical behaviour > on OS X? > > ~From my understanding, this is typical behavior on just about any > platform that has software compiled with shared library support. > When a > binary file is compiled, during the configuration step there is > usually > an option that determines the shard library path. If you wanted to > change the location of shared libraries you'd have to re-run the > configure script with the new library directory and then recompile the > software. > > Matrix Mole > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHi2WgNtosHRPp48MRAmSpAKCBixIn2Ingwtdl6pUXq1PCk/wNWgCfTjqp > u5V7n4lxQgBKerY5sXSdxTc= > =y/xT > -----END PGP SIGNATURE----- > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users From matrixm at gmail.com Mon Jan 14 06:11:51 2008 From: matrixm at gmail.com (Matrix Mole) Date: Mon Jan 14 06:11:29 2008 Subject: OS X and shared Libraries In-Reply-To: References: <478B65A0.9030104@gmail.com> Message-ID: <478B6DA7.5080605@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 elabsjng@mac.com wrote: | Thanks for the reply. Maybe I misunderstand but I though, on Linux, the | run-time linker had a set of search paths to look for shared libraries? I might be wrong then. I always thought that there was some kind of lib directory option in the ./configure script that could be set, if not it'd default (usually to /usr/local or whatever had been coded by the programmer). For systems such as macports, they'd have set the library path to /opt/local/lib I believe. Unfortunately, my programming experience and knowledge is extremely limited, and I might be mistaking shared libraries with runtime dependent libraries. I'm hoping if I'm incorrect then someone can show me where, but this is how I've understood it for a while now. Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHi22nNtosHRPp48MRAnkxAJ9A+MdS92gvFd4vuhJMiLTmnbZH4wCgiGmR lg7cYIstdtMUJSccULcPeMc= =cl52 -----END PGP SIGNATURE----- From stefmit at gmail.com Mon Jan 14 06:23:56 2008 From: stefmit at gmail.com (Stefmit) Date: Mon Jan 14 06:23:36 2008 Subject: lbpcap - yet again - Q Message-ID: <200801140823.56804.stefmit@gmail.com> I keep getting errors on this (libpcap) port, using macports. Would anybody be kind enough to tell me if this package is being maintained? I apologize if I am breaking any rules of Qs, but this is my first version (10.5.x) macosx ever trying to use macports (have used only fink up to and including 10.4.x): $ sudo port upgrade outdated ---> Building libpcap with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_libpcap/work/libpcap-0.9.8" && make all " returned error 2 Command output: rm -f libpcap.dylib /usr/bin/gcc-4.0 -dynamiclib -o libpcap.`cat VERSION`.dylib \ -install_name /opt/local/lib/libpcap.0.dylib \ -compatibility_version 1.0.0 -current_version `cat VERSION` \ pcap-bpf.o fad-getad.o pcap.o inet.o gencode.o optimize.o nametoaddr.o etherent.o savefile.o bpf_filter.o bpf_image.o bpf_dump.o scanner.o grammar.o version.o Undefined symbols: "_lex_init", referenced from: _pcap_compile in gencode.o "_lex_cleanup", referenced from: _pcap_compile in gencode.o _pcap_compile in gencode.o "_pcap_lex", referenced from: _pcap_parse in grammar.o ld: symbol(s) not found collect2: ld returned 1 exit status make: *** [libpcap.dylib] Error 1 Error: Unable to upgrade port: 1 TIA, Stefan From stefmit at gmail.com Mon Jan 14 07:26:09 2008 From: stefmit at gmail.com (Stefmit) Date: Mon Jan 14 07:25:50 2008 Subject: follow-up to early Q about package maintainers Message-ID: <200801140926.10143.stefmit@gmail.com> I apologize for coming back to this, but I have - I hope this time - a more constructive question: where do I find a quick tutorial on how to use and possibly help the macports process of package maintenance and updating? I am not a programmer, so I won;t be able to produce source from scratch, but I can find my way around code (having helped source code maintenance, at least as tester, for some network stuff for macosx - mostly informal) enough to lend a hand, at least with testing and ticket updates ... TIA, Stefan P.S. I am dying for the libpcap fix - my expertise is in network (and associated security) and without this one properly done majority of my tools are practically useless From mreid at pobox.com Mon Jan 14 08:50:23 2008 From: mreid at pobox.com (Melissa Reid) Date: Mon Jan 14 08:49:03 2008 Subject: All HTTP Fetches fail, only FTP working In-Reply-To: <3D7A83C3-2002-4F56-A6AF-1230395B936D@gmail.com> Message-ID: ballagas@gmail.com (Tico Ballagas) sent forth on 1/14/08: >Hello- > >I'm having a strange problem where all of the fetch attempts using >HTTP fail, but all FTP work fine (see output below). Any ideas what >might be going wrong? When that happened to me, it turned out that something had set the environment variable 'http_proxy' to something bogus, and curl was honoring that. I never did figure out what was doing that; I wound up having to manually unset it in my .bashrc. Melissa Reid From ryandesign at macports.org Mon Jan 14 12:22:57 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 14 12:23:18 2008 Subject: Error messages with Freetype and XFree86 In-Reply-To: <0CA49DE2-8EDB-40FF-B124-4B0D93681EF3@grid.unep.ch> References: <0CA49DE2-8EDB-40FF-B124-4B0D93681EF3@grid.unep.ch> Message-ID: On Jan 14, 2008, at 07:35, Stefan Schwarzer wrote: > I got the following error when trying to install FREETYPE, and in a > later effort XFree86. Can anyone tell me what it means and if there > is a solution to this? > > Thanks a lot, > > Stef > > > gridmac7:Documents schwarzer$ sudo /opt/local/bin/port install > freetype > Password: > ---> Fetching freetype > ---> Attempting to fetch freetype-2.3.5.tar.bz2 from http:// > download.savannah.gnu.org/releases/freetype/ > ---> Verifying checksum(s) for freetype > ---> Extracting freetype > ---> Applying patches to freetype > ---> Configuring freetype > ---> Building freetype with target all > ---> Staging freetype into destroot > ---> Installing freetype 2.3.5_1 > ---> Activating freetype 2.3.5_1 > ---> Cleaning freetype It looks like the freetype install succeeded without error? > gridmac7:Documents schwarzer$ sudo /opt/local/bin/port install gd2 > ---> Fetching XFree86 > ---> Attempting to fetch XFree86-4.7.0-src-1.tgz from http://ftp- > stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/ > source/ > ---> Attempting to fetch XFree86-4.7.0-src-2.tgz from http://ftp- > stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/ > source/ > ---> Attempting to fetch XFree86-4.7.0-src-3.tgz from http://ftp- > stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/ > source/ > ---> Attempting to fetch XFree86-4.7.0-src-4.tgz from http://ftp- > stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/ > source/ > ---> Attempting to fetch XFree86-4.7.0-src-5.tgz from http://ftp- > stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/ > source/ > ---> Verifying checksum(s) for XFree86 > ---> Extracting XFree86 > ---> Applying patches to XFree86 > ---> Configuring XFree86 > ---> Building XFree86 with target World > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_X > Free86/work/xc" && make World " returned error 2 > Command output: including in lib/dps... > checking ../../config/pswrap/pswrap over in ../../config/pswrap > first... > /usr/bin/cc -Os -fno-strict-aliasing -Wall -Wpointer-arith -no-cpp- > precomp -I. -I../../exports/include "-I/opt/local/var/ > macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_X > Free86/work/include" -D__i386__ - > D__DARWIN__ -DNO_ALLOCA - > DCSRG_BASED -DXENVIRONMENT -c -o main.o main.c > yacc -d pswparser.y > conflicts: 1 shift/reduce > mv -f y.tab.c pswparser.c > + mv -f y.tab.h pswparser.h > /usr/bin/cc -Os -fno-strict-aliasing -Wall -Wpointer-arith -no-cpp- > precomp -I. -I../../exports/include "-I/opt/local/var/ > macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_X > Free86/work/include" -D__i386__ - > D__DARWIN__ -DNO_ALLOCA - > DCSRG_BASED -DXENVIRONMENT -c -o pswparser.o pswparser.c > flex -l lexer.l > lexer.l:108: bad character: % > lexer.l:108: unknown error processing section 1 > lexer.l:108: unknown error processing section 1 > lexer.l:108: bad character: 3 > lexer.l:108: bad character: 5 > lexer.l:108: bad character: 0 > lexer.l:108: bad character: 0 > lexer.l:109: bad character: % > lexer.l:109: unknown error processing section 1 > lexer.l:109: bad character: 2 > lexer.l:109: bad character: 5 > lexer.l:109: bad character: 0 > lexer.l:109: bad character: 0 > make[4]: *** [lexer.c] Error 1 > okay, continuing in lib/dps > ../../config/pswrap/pswrap -a -o dpsclrops.c -h dpsclrops.h > dpsclrops.psw > make[3]: ../../config/pswrap/pswrap: Command not found > make[3]: *** [dpsclrops.c] Error 127 > make[2]: *** [includes] Error 1 > make[1]: *** [includes] Error 1 > make: *** [World] Error 2 > > Error: The following dependencies failed to build: XFree86 fontconfig > Error: Status 1 encountered during processing. I'm not sure why this happens. What version of Mac OS X, Xcode and MacPorts do you have, and what kind of Mac is this happening on? Based on the existence of "-D__i386__" in your output I assume you're on an Intel Mac? From ryandesign at macports.org Mon Jan 14 12:24:04 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 14 12:24:26 2008 Subject: OS X and shared Libraries In-Reply-To: <478B6DA7.5080605@gmail.com> References: <478B65A0.9030104@gmail.com> <478B6DA7.5080605@gmail.com> Message-ID: On Jan 14, 2008, at 08:11, Matrix Mole wrote: > elabsjng@mac.com wrote: > > | Thanks for the reply. Maybe I misunderstand but I though, on > Linux, the > | run-time linker had a set of search paths to look for shared > libraries? > > I might be wrong then. I always thought that there was some kind of > lib > directory option in the ./configure script that could be set, if not > it'd default (usually to /usr/local or whatever had been coded by the > programmer). For systems such as macports, they'd have set the library > path to /opt/local/lib I believe. Unfortunately, my programming > experience and knowledge is extremely limited, and I might be > mistaking > shared libraries with runtime dependent libraries. I'm hoping if I'm > incorrect then someone can show me where, but this is how I've > understood it for a while now. I guess Simon is talking about ld.conf that exists on Linux, and for which there is no Mac OS X equivalent. From ryandesign at macports.org Mon Jan 14 12:18:41 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 14 12:25:41 2008 Subject: follow-up to early Q about package maintainers In-Reply-To: <200801140926.10143.stefmit@gmail.com> References: <200801140926.10143.stefmit@gmail.com> Message-ID: On Jan 14, 2008, at 09:26, Stefmit wrote: > I apologize for coming back to this, but I have - I hope this time > - a more > constructive question: where do I find a quick tutorial on how to > use and > possibly help the macports process of package maintenance and > updating? I am > not a programmer, so I won;t be able to produce source from > scratch, but I > can find my way around code (having helped source code maintenance, > at least > as tester, for some network stuff for macosx - mostly informal) > enough to > lend a hand, at least with testing and ticket updates ... Have you looked in the guide? http://guide.macports.org/ If it does not address this, we may need to add a section. (The guide is still new and a work in progress.) From mattness at mac.com Mon Jan 14 12:54:07 2008 From: mattness at mac.com (Matt) Date: Mon Jan 14 12:53:44 2008 Subject: newbie help wanted with installing/using netpbm through macports Message-ID: <9362247C-056D-4546-9F24-FD6A00AAF802@mac.com> I did a little c++ coding in college but that was 10 years ago, so I apologize if I am missing something obvious. I am trying to compile an intel mac compatible version of an open source printer driver so I can use my old but beloved Alps printer on my new intel imac. The source for the driver is here: http://openprinting.org/show_driver.cgi?driver=ppmtomd&fromprinter=Alps-MD-1000 I downloaded the source for the driver and tried to perform a make on it in the terminal. The string of errors showed me that it was missing the pgm.h and ppm.h header files. Searching for these files online I found that they belong to the netpbm library. It seemed like the easiest way to install netpbm and any dependant libraries was through macports. I succesfully downloaded, installed, and updated macports, then told it to install netpbm. I got no errors and everything looked good. Unfortunately, the source for the ppmtomd driver still can't find those header files (though I can through spotlight). When I check to see what ports I have installed I get the following output: iMatt:~ mwoods$ port installed The following ports are currently installed: jasper @1.701.0_0 (active) jpeg @6b_2 (active) libpng @1.2.24_0 (active) netpbm @10.26.48_0 (active) tiff @3.8.2_1+macosx (active) zlib @1.2.3_1 (active) iMatt:~ mwoods$ if they were installed properly though, I would think I could use the "which" command on them. Unfortunately, the only port that responds to "which" is jasper which I assume is a dependent library that was installed with netpbm. iMatt:~ mwoods$ which netpbm iMatt:~ mwoods$ which jasper /opt/local/bin/jasper I suspect either netpbm is not installed properly, or I have to do something to the makefile of the printer driver to get it to find those libraries, but I haven't been able to figure it out. Does anyone have any advice? Thanks! -Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080114/a3fc1edf/attachment.html From stefmit at gmail.com Mon Jan 14 13:00:42 2008 From: stefmit at gmail.com (Stefmit) Date: Mon Jan 14 13:00:20 2008 Subject: lbpcap - yet again - Q In-Reply-To: <2AC82179-E2EA-402A-B43E-1A69111F66AE@macports.org> References: <200801140823.56804.stefmit@gmail.com> <2AC82179-E2EA-402A-B43E-1A69111F66AE@macports.org> Message-ID: <200801141500.42903.stefmit@gmail.com> I have already replied to a few people who have been involved in the process, via direct email, that the workaround did not fix the problem. I am not sure if any one of them is the maintainer, or not. I will take another look at the ticket, to see if it's been updated. Thanks, Stefan On Monday 14 January 2008 14:44:56 you wrote: > On Jan 14, 2008, at 08:23, Stefmit wrote: > > I keep getting errors on this (libpcap) port, using macports. Would > > anybody be > > kind enough to tell me if this package is being maintained? I > > apologize if I > > am breaking any rules of Qs, but this is my first version (10.5.x) > > macosx > > ever trying to use macports (have used only fink up to and > > including 10.4.x): > > Only the maintainer of the libpcap port can tell you if he is > actively maintaining the port. If you get no response from the > maintainer within 72 hours, someone else can try to fix the problem. > > > $ sudo port upgrade outdated > > ---> Building libpcap with target all > > Error: Target org.macports.build returned: shell command " > > cd "/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_l > > ibpcap/work/libpcap-0.9.8" > > && make all " returned error 2 > > Command output: rm -f libpcap.dylib > > /usr/bin/gcc-4.0 -dynamiclib -o libpcap.`cat VERSION`.dylib \ > > -install_name /opt/local/lib/libpcap.0.dylib \ > > -compatibility_version 1.0.0 -current_version `cat > > VERSION` \ > > pcap-bpf.o fad-getad.o pcap.o inet.o gencode.o > > optimize.o > > nametoaddr.o etherent.o savefile.o bpf_filter.o bpf_image.o bpf_dump.o > > scanner.o grammar.o version.o > > Undefined symbols: > > "_lex_init", referenced from: > > _pcap_compile in gencode.o > > "_lex_cleanup", referenced from: > > _pcap_compile in gencode.o > > _pcap_compile in gencode.o > > "_pcap_lex", referenced from: > > _pcap_parse in grammar.o > > ld: symbol(s) not found > > collect2: ld returned 1 exit status > > make: *** [libpcap.dylib] Error 1 > > As I've already told you, this bug has already been reported: > > http://trac.macports.org/projects/macports/ticket/13802 > > As you see in the ticket notes, the maintainer has been quite active > in trying to resolve this problem, a possible workaround has been > found, and he is waiting on you to confirm whether the solution works > for you. You should have been receiving email for every change made > to the ticket, since I added you to its Cc list a week ago. Please > try the workaround listed there and add a note to the ticket to let > the maintainer know whether or not it worked for you. From ryandesign at macports.org Mon Jan 14 12:44:56 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 14 13:11:57 2008 Subject: lbpcap - yet again - Q In-Reply-To: <200801140823.56804.stefmit@gmail.com> References: <200801140823.56804.stefmit@gmail.com> Message-ID: <2AC82179-E2EA-402A-B43E-1A69111F66AE@macports.org> On Jan 14, 2008, at 08:23, Stefmit wrote: > I keep getting errors on this (libpcap) port, using macports. Would > anybody be > kind enough to tell me if this package is being maintained? I > apologize if I > am breaking any rules of Qs, but this is my first version (10.5.x) > macosx > ever trying to use macports (have used only fink up to and > including 10.4.x): Only the maintainer of the libpcap port can tell you if he is actively maintaining the port. If you get no response from the maintainer within 72 hours, someone else can try to fix the problem. > $ sudo port upgrade outdated > ---> Building libpcap with target all > Error: Target org.macports.build returned: shell command " > cd "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_l > ibpcap/work/libpcap-0.9.8" > && make all " returned error 2 > Command output: rm -f libpcap.dylib > /usr/bin/gcc-4.0 -dynamiclib -o libpcap.`cat VERSION`.dylib \ > -install_name /opt/local/lib/libpcap.0.dylib \ > -compatibility_version 1.0.0 -current_version `cat > VERSION` \ > pcap-bpf.o fad-getad.o pcap.o inet.o gencode.o > optimize.o > nametoaddr.o etherent.o savefile.o bpf_filter.o bpf_image.o bpf_dump.o > scanner.o grammar.o version.o > Undefined symbols: > "_lex_init", referenced from: > _pcap_compile in gencode.o > "_lex_cleanup", referenced from: > _pcap_compile in gencode.o > _pcap_compile in gencode.o > "_pcap_lex", referenced from: > _pcap_parse in grammar.o > ld: symbol(s) not found > collect2: ld returned 1 exit status > make: *** [libpcap.dylib] Error 1 As I've already told you, this bug has already been reported: http://trac.macports.org/projects/macports/ticket/13802 As you see in the ticket notes, the maintainer has been quite active in trying to resolve this problem, a possible workaround has been found, and he is waiting on you to confirm whether the solution works for you. You should have been receiving email for every change made to the ticket, since I added you to its Cc list a week ago. Please try the workaround listed there and add a note to the ticket to let the maintainer know whether or not it worked for you. From jochen at fhi-berlin.mpg.de Mon Jan 14 14:17:52 2008 From: jochen at fhi-berlin.mpg.de (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Mon Jan 14 14:17:40 2008 Subject: newbie help wanted with installing/using netpbm through macports In-Reply-To: <9362247C-056D-4546-9F24-FD6A00AAF802@mac.com> References: <9362247C-056D-4546-9F24-FD6A00AAF802@mac.com> Message-ID: Hi Matt, On 14.01.2008, at 21:54, Matt wrote: > I am trying to compile an intel mac compatible version of an open > source printer driver so I can use my old but beloved Alps printer > on my new intel imac. The source for the driver is here: > > http://openprinting.org/show_driver.cgi?driver=ppmtomd&fromprinter=Alps-MD-1000 Not sure what you are trying to achieve, but isn't it god enough to just downlaod the PPD from the page you give here and then go to preferences, add printer, and give it that PPD? > I succesfully downloaded, installed, and updated macports, then told > it to install netpbm. I got no errors and everything looked good. > Unfortunately, the source for the ppmtomd driver still can't find > those header files (though I can through spotlight). Again, what are you doing? Where exactly did you get the source code from? If you *really* need the compiler to find the header files, you can specify them using -I, i.e., gcc -I=/opt/local/bin or set C_INCLUDE_PATH appropriately. Hope this helps. Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll From ryandesign at macports.org Mon Jan 14 14:26:04 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 14 14:26:26 2008 Subject: newbie help wanted with installing/using netpbm through macports In-Reply-To: <9362247C-056D-4546-9F24-FD6A00AAF802@mac.com> References: <9362247C-056D-4546-9F24-FD6A00AAF802@mac.com> Message-ID: <39383524-B883-4B43-9744-AFDF77B2D44B@macports.org> On Jan 14, 2008, at 14:54, Matt wrote: > I am trying to compile an intel mac compatible version of an open > source > printer driver so I can use my old but beloved Alps printer on my > new intel > imac. The source for the driver is here: > > http://openprinting.org/show_driver.cgi? > driver=ppmtomd&fromprinter=Alps-MD-1000 > > I downloaded the source for the driver and tried to perform a make > on it in > the terminal. The string of errors showed me that it was missing > the pgm.h > and ppm.h header files. Searching for these files online I found > that they > belong to the netpbm library. It seemed like the easiest way to > install > netpbm and any dependant libraries was through macports. > > I succesfully downloaded, installed, and updated macports, then > told it to > install netpbm. I got no errors and everything looked good. > Unfortunately, > the source for the ppmtomd driver still can't find those header files > (though I can through spotlight). You probably haven't told the ppmtomd build system that you've installed netpbm in /opt/local and it probably won't think to look there on its own. > When I check to see what ports I have installed I get the following > output: > > iMatt:~ mwoods$ port installed > The following ports are currently installed: > jasper @1.701.0_0 (active) > jpeg @6b_2 (active) > libpng @1.2.24_0 (active) > netpbm @10.26.48_0 (active) > tiff @3.8.2_1+macosx (active) > zlib @1.2.3_1 (active) > iMatt:~ mwoods$ > > if they were installed properly though, I would think I could use the > "which" command on them. If they all provided a binary by the same name as the port, then yes. But not all ports provide binaries of the same name. Not all ports even provide binaries. (Some just provide libraries.) > Unfortunately, the only port that responds to > "which" is jasper which I assume is a dependent library that was > installed > with netpbm. > > iMatt:~ mwoods$ which netpbm > iMatt:~ mwoods$ which jasper > /opt/local/bin/jasper Yes. As you can see with "port deps netpbm", netpbm declares a library dependency on jasper. > I suspect either netpbm is not installed properly, or I have to do > something > to the makefile of the printer driver to get it to find those > libraries, but > I haven't been able to figure it out. netpbm is likely installed just fine. "port contents netpbm" will show you everything it installed. It looks like it installs many binaries but none called "netpbm". It does install a libnetpbm, but "which" does not search for libraries, only binaries. Bottom line: when you configure and compile ppmtomd, you just need to tell it where netpbm is. This could help: export CFLAGS="-I/opt/local/include" export LDFLAGS="-L/opt/local/lib" And then follow the instructions for how to compile ppmtomd. From mattness at mac.com Mon Jan 14 15:35:20 2008 From: mattness at mac.com (Matt) Date: Mon Jan 14 15:34:55 2008 Subject: newbie help wanted with installing/using netpbm through macports In-Reply-To: <39383524-B883-4B43-9744-AFDF77B2D44B@macports.org> References: <9362247C-056D-4546-9F24-FD6A00AAF802@mac.com> <39383524-B883-4B43-9744-AFDF77B2D44B@macports.org> Message-ID: Hi Ryan, Thanks for the help. I did find the following in the makefile for ppmtomd: # if your ppm libraries are not in a standard place, uncomment # and change this. You may also need thing like -R, but if you're # on that sort of system you probably know it! # LDLIBS = -L/usr/local/lib I uncommented and changed the line to: LDLIBS = -L/opt/local/lib I also added your: export CFLAGS="-I/opt/local/include" export LDFLAGS="-L/opt/local/lib" to my ~/.profile Unfortunately, it still can't find those two header files on compiling. Do I need to add something more to the makefile that points to -I/opt/ local/include? Thanks! -Matt On Jan 14, 2008, at 5:26 PM, Ryan Schmidt wrote: > On Jan 14, 2008, at 14:54, Matt wrote: > >> I am trying to compile an intel mac compatible version of an open >> source >> printer driver so I can use my old but beloved Alps printer on my >> new intel >> imac. The source for the driver is here: >> >> http://openprinting.org/show_driver.cgi?driver=ppmtomd&fromprinter=Alps-MD-1000 >> >> I downloaded the source for the driver and tried to perform a make >> on it in >> the terminal. The string of errors showed me that it was missing >> the pgm.h >> and ppm.h header files. Searching for these files online I found >> that they >> belong to the netpbm library. It seemed like the easiest way to >> install >> netpbm and any dependant libraries was through macports. >> >> I succesfully downloaded, installed, and updated macports, then >> told it to >> install netpbm. I got no errors and everything looked good. >> Unfortunately, >> the source for the ppmtomd driver still can't find those header files >> (though I can through spotlight). > > You probably haven't told the ppmtomd build system that you've > installed netpbm in /opt/local and it probably won't think to look > there on its own. > > >> When I check to see what ports I have installed I get the following >> output: >> >> iMatt:~ mwoods$ port installed >> The following ports are currently installed: >> jasper @1.701.0_0 (active) >> jpeg @6b_2 (active) >> libpng @1.2.24_0 (active) >> netpbm @10.26.48_0 (active) >> tiff @3.8.2_1+macosx (active) >> zlib @1.2.3_1 (active) >> iMatt:~ mwoods$ >> >> if they were installed properly though, I would think I could use the >> "which" command on them. > > If they all provided a binary by the same name as the port, then > yes. But not all ports provide binaries of the same name. Not all > ports even provide binaries. (Some just provide libraries.) > >> Unfortunately, the only port that responds to >> "which" is jasper which I assume is a dependent library that was >> installed >> with netpbm. >> >> iMatt:~ mwoods$ which netpbm >> iMatt:~ mwoods$ which jasper >> /opt/local/bin/jasper > > Yes. As you can see with "port deps netpbm", netpbm declares a > library dependency on jasper. > >> I suspect either netpbm is not installed properly, or I have to do >> something >> to the makefile of the printer driver to get it to find those >> libraries, but >> I haven't been able to figure it out. > > netpbm is likely installed just fine. "port contents netpbm" will > show you everything it installed. It looks like it installs many > binaries but none called "netpbm". It does install a libnetpbm, but > "which" does not search for libraries, only binaries. > > > Bottom line: when you configure and compile ppmtomd, you just need > to tell it where netpbm is. This could help: > > export CFLAGS="-I/opt/local/include" > export LDFLAGS="-L/opt/local/lib" > > And then follow the instructions for how to compile ppmtomd. > > From mattness at mac.com Mon Jan 14 15:56:02 2008 From: mattness at mac.com (Matthew Woods) Date: Mon Jan 14 15:55:37 2008 Subject: newbie help wanted with installing/using netpbm through macports In-Reply-To: References: <9362247C-056D-4546-9F24-FD6A00AAF802@mac.com> Message-ID: <14820790.post@talk.nabble.com> I actually tried downloading the ppd first but it didn't work. I assume because it was compiled under linux and is slightly different. There is also an OSX faq on the site that specifically mentions this driver saying: ALPS Microdry Which driver do I use? Use the free software printer driver ppmtomd You will have to compile it under OS X to use it. unfortunately it doesn't give better instructions on how to go about it. Where would I put gcc -I=/opt/local/bin or find C_INCLUDE_PATH? Thanks, -Matt Jochen K?pper wrote: > > Hi Matt, > > On 14.01.2008, at 21:54, Matt wrote: > >> I am trying to compile an intel mac compatible version of an open >> source printer driver so I can use my old but beloved Alps printer >> on my new intel imac. The source for the driver is here: >> >> http://openprinting.org/show_driver.cgi?driver=ppmtomd&fromprinter=Alps-MD-1000 > > Not sure what you are trying to achieve, but isn't it god enough to > just downlaod the PPD from the page you give here and then go to > preferences, add printer, and give it that PPD? > >> I succesfully downloaded, installed, and updated macports, then told >> it to install netpbm. I got no errors and everything looked good. >> Unfortunately, the source for the ppmtomd driver still can't find >> those header files (though I can through spotlight). > > Again, what are you doing? Where exactly did you get the source code > from? > > If you *really* need the compiler to find the header files, you can > specify them using -I, i.e., > gcc -I=/opt/local/bin > or set C_INCLUDE_PATH appropriately. > > > Hope this helps. > > Greetings, > Jochen > -- > Einigkeit und Recht und Freiheit > http://www.Jochen-Kuepper.de > Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D > Sex, drugs and rock-n-roll > > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > > -- View this message in context: http://www.nabble.com/newbie-help-wanted-with-installing-using-netpbm-through-macports-tp14814260p14820790.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From ryandesign at macports.org Mon Jan 14 16:12:04 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 14 16:12:27 2008 Subject: newbie help wanted with installing/using netpbm through macports In-Reply-To: References: <9362247C-056D-4546-9F24-FD6A00AAF802@mac.com> <39383524-B883-4B43-9744-AFDF77B2D44B@macports.org> Message-ID: <612392A4-8437-4533-BF0E-D7E277296995@macports.org> I see now that ppmtomd is more difficult to compile than most software. As such, as soon as someone figures out how to do it, a portfile should be created so nobody else has to figure it out again. I'm working on a portfile. I'll see how far I can get. On Jan 14, 2008, at 17:35, Matt wrote: > Hi Ryan, > > Thanks for the help. > > I did find the following in the makefile for ppmtomd: > > # if your ppm libraries are not in a standard place, uncomment > # and change this. You may also need thing like -R, but if you're > # on that sort of system you probably know it! > # LDLIBS = -L/usr/local/lib > > I uncommented and changed the line to: > > LDLIBS = -L/opt/local/lib > > I also added your: > > export CFLAGS="-I/opt/local/include" > export LDFLAGS="-L/opt/local/lib" > > to my ~/.profile > > Unfortunately, it still can't find those two header files on > compiling. > > Do I need to add something more to the makefile that points to -I/ > opt/local/include? > > Thanks! > > -Matt > > > > On Jan 14, 2008, at 5:26 PM, Ryan Schmidt wrote: > >> On Jan 14, 2008, at 14:54, Matt wrote: >> >>> I am trying to compile an intel mac compatible version of an open >>> source >>> printer driver so I can use my old but beloved Alps printer on my >>> new intel >>> imac. The source for the driver is here: >>> >>> http://openprinting.org/show_driver.cgi? >>> driver=ppmtomd&fromprinter=Alps-MD-1000 >>> >>> I downloaded the source for the driver and tried to perform a >>> make on it in >>> the terminal. The string of errors showed me that it was missing >>> the pgm.h >>> and ppm.h header files. Searching for these files online I found >>> that they >>> belong to the netpbm library. It seemed like the easiest way to >>> install >>> netpbm and any dependant libraries was through macports. >>> >>> I succesfully downloaded, installed, and updated macports, then >>> told it to >>> install netpbm. I got no errors and everything looked good. >>> Unfortunately, >>> the source for the ppmtomd driver still can't find those header >>> files >>> (though I can through spotlight). >> >> You probably haven't told the ppmtomd build system that you've >> installed netpbm in /opt/local and it probably won't think to look >> there on its own. >> >> >>> When I check to see what ports I have installed I get the >>> following output: >>> >>> iMatt:~ mwoods$ port installed >>> The following ports are currently installed: >>> jasper @1.701.0_0 (active) >>> jpeg @6b_2 (active) >>> libpng @1.2.24_0 (active) >>> netpbm @10.26.48_0 (active) >>> tiff @3.8.2_1+macosx (active) >>> zlib @1.2.3_1 (active) >>> iMatt:~ mwoods$ >>> >>> if they were installed properly though, I would think I could use >>> the >>> "which" command on them. >> >> If they all provided a binary by the same name as the port, then >> yes. But not all ports provide binaries of the same name. Not all >> ports even provide binaries. (Some just provide libraries.) >> >>> Unfortunately, the only port that responds to >>> "which" is jasper which I assume is a dependent library that was >>> installed >>> with netpbm. >>> >>> iMatt:~ mwoods$ which netpbm >>> iMatt:~ mwoods$ which jasper >>> /opt/local/bin/jasper >> >> Yes. As you can see with "port deps netpbm", netpbm declares a >> library dependency on jasper. >> >>> I suspect either netpbm is not installed properly, or I have to >>> do something >>> to the makefile of the printer driver to get it to find those >>> libraries, but >>> I haven't been able to figure it out. >> >> netpbm is likely installed just fine. "port contents netpbm" will >> show you everything it installed. It looks like it installs many >> binaries but none called "netpbm". It does install a libnetpbm, >> but "which" does not search for libraries, only binaries. >> >> >> Bottom line: when you configure and compile ppmtomd, you just need >> to tell it where netpbm is. This could help: >> >> export CFLAGS="-I/opt/local/include" >> export LDFLAGS="-L/opt/local/lib" >> >> And then follow the instructions for how to compile ppmtomd. >> >> > From ryandesign at macports.org Mon Jan 14 16:29:14 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 14 16:29:36 2008 Subject: newbie help wanted with installing/using netpbm through macports In-Reply-To: <612392A4-8437-4533-BF0E-D7E277296995@macports.org> References: <9362247C-056D-4546-9F24-FD6A00AAF802@mac.com> <39383524-B883-4B43-9744-AFDF77B2D44B@macports.org> <612392A4-8437-4533-BF0E-D7E277296995@macports.org> Message-ID: <7AAFC8D4-1EB2-48F2-AC70-6CA0FB434E19@macports.org> I just added the ppmtomd portfile. Wait 12 hours, then "sudo port selfupdate", then "sudo port install ppmtomd". If you're interested to see what I had to do to get it to work, you can "port cat ppmtomd" and "cat `port dir ppmtomd`/files/patch- Makefile.diff". On Jan 14, 2008, at 18:12, Ryan Schmidt wrote: > I see now that ppmtomd is more difficult to compile than most > software. As such, as soon as someone figures out how to do it, a > portfile should be created so nobody else has to figure it out again. > > I'm working on a portfile. I'll see how far I can get. > > > On Jan 14, 2008, at 17:35, Matt wrote: > >> Hi Ryan, >> >> Thanks for the help. >> >> I did find the following in the makefile for ppmtomd: >> >> # if your ppm libraries are not in a standard place, uncomment >> # and change this. You may also need thing like -R, but if you're >> # on that sort of system you probably know it! >> # LDLIBS = -L/usr/local/lib >> >> I uncommented and changed the line to: >> >> LDLIBS = -L/opt/local/lib >> >> I also added your: >> >> export CFLAGS="-I/opt/local/include" >> export LDFLAGS="-L/opt/local/lib" >> >> to my ~/.profile >> >> Unfortunately, it still can't find those two header files on >> compiling. >> >> Do I need to add something more to the makefile that points to -I/ >> opt/local/include? >> >> Thanks! >> >> -Matt >> >> >> >> On Jan 14, 2008, at 5:26 PM, Ryan Schmidt wrote: >> >>> On Jan 14, 2008, at 14:54, Matt wrote: >>> >>>> I am trying to compile an intel mac compatible version of an >>>> open source >>>> printer driver so I can use my old but beloved Alps printer on >>>> my new intel >>>> imac. The source for the driver is here: >>>> >>>> http://openprinting.org/show_driver.cgi? >>>> driver=ppmtomd&fromprinter=Alps-MD-1000 >>>> >>>> I downloaded the source for the driver and tried to perform a >>>> make on it in >>>> the terminal. The string of errors showed me that it was >>>> missing the pgm.h >>>> and ppm.h header files. Searching for these files online I >>>> found that they >>>> belong to the netpbm library. It seemed like the easiest way to >>>> install >>>> netpbm and any dependant libraries was through macports. >>>> >>>> I succesfully downloaded, installed, and updated macports, then >>>> told it to >>>> install netpbm. I got no errors and everything looked good. >>>> Unfortunately, >>>> the source for the ppmtomd driver still can't find those header >>>> files >>>> (though I can through spotlight). >>> >>> You probably haven't told the ppmtomd build system that you've >>> installed netpbm in /opt/local and it probably won't think to >>> look there on its own. >>> >>> >>>> When I check to see what ports I have installed I get the >>>> following output: >>>> >>>> iMatt:~ mwoods$ port installed >>>> The following ports are currently installed: >>>> jasper @1.701.0_0 (active) >>>> jpeg @6b_2 (active) >>>> libpng @1.2.24_0 (active) >>>> netpbm @10.26.48_0 (active) >>>> tiff @3.8.2_1+macosx (active) >>>> zlib @1.2.3_1 (active) >>>> iMatt:~ mwoods$ >>>> >>>> if they were installed properly though, I would think I could >>>> use the >>>> "which" command on them. >>> >>> If they all provided a binary by the same name as the port, then >>> yes. But not all ports provide binaries of the same name. Not all >>> ports even provide binaries. (Some just provide libraries.) >>> >>>> Unfortunately, the only port that responds to >>>> "which" is jasper which I assume is a dependent library that was >>>> installed >>>> with netpbm. >>>> >>>> iMatt:~ mwoods$ which netpbm >>>> iMatt:~ mwoods$ which jasper >>>> /opt/local/bin/jasper >>> >>> Yes. As you can see with "port deps netpbm", netpbm declares a >>> library dependency on jasper. >>> >>>> I suspect either netpbm is not installed properly, or I have to >>>> do something >>>> to the makefile of the printer driver to get it to find those >>>> libraries, but >>>> I haven't been able to figure it out. >>> >>> netpbm is likely installed just fine. "port contents netpbm" will >>> show you everything it installed. It looks like it installs many >>> binaries but none called "netpbm". It does install a libnetpbm, >>> but "which" does not search for libraries, only binaries. >>> >>> >>> Bottom line: when you configure and compile ppmtomd, you just >>> need to tell it where netpbm is. This could help: >>> >>> export CFLAGS="-I/opt/local/include" >>> export LDFLAGS="-L/opt/local/lib" >>> >>> And then follow the instructions for how to compile ppmtomd. From opendarwin.org at darkart.com Mon Jan 14 16:59:44 2008 From: opendarwin.org at darkart.com (Eric Hall) Date: Mon Jan 14 16:59:19 2008 Subject: lbpcap - yet again - Q In-Reply-To: <200801141500.42903.stefmit@gmail.com> References: <200801140823.56804.stefmit@gmail.com> <2AC82179-E2EA-402A-B43E-1A69111F66AE@macports.org> <200801141500.42903.stefmit@gmail.com> Message-ID: <20080115005944.GV5860@darkart.com> On Mon, Jan 14, 2008 at 03:00:42PM -0600, Stefmit wrote: > > I have already replied to a few people who have been involved in the process, > via direct email, that the workaround did not fix the problem. I am not sure > if any one of them is the maintainer, or not. I will take another look at the > ticket, to see if it's been updated. Sorry, I haven't had a chance to get back to it and test on PPC. I'm not sure why it doesn't build for you. It appears that deactivating MP-installed flex resolved the problem on x86, but did not for you on PPC. I don't know if that's due to something special on PPC or something else you have installed. Do you have other (esp. development related) ports installed? -eric From mattness at mac.com Mon Jan 14 17:04:55 2008 From: mattness at mac.com (Matt) Date: Mon Jan 14 17:04:32 2008 Subject: newbie help wanted with installing/using netpbm through macports In-Reply-To: <7AAFC8D4-1EB2-48F2-AC70-6CA0FB434E19@macports.org> References: <9362247C-056D-4546-9F24-FD6A00AAF802@mac.com> <39383524-B883-4B43-9744-AFDF77B2D44B@macports.org> <612392A4-8437-4533-BF0E-D7E277296995@macports.org> <7AAFC8D4-1EB2-48F2-AC70-6CA0FB434E19@macports.org> Message-ID: Hi Ryan, Thanks for doing that! I'll download it when it updates, then let you know how it works. I am curious to see what you did to get it to work. I'll be sure to check that out. Thanks, -Matt On Jan 14, 2008, at 7:29 PM, Ryan Schmidt wrote: > I just added the ppmtomd portfile. Wait 12 hours, then "sudo port > selfupdate", then "sudo port install ppmtomd". > > If you're interested to see what I had to do to get it to work, you > can "port cat ppmtomd" and "cat `port dir ppmtomd`/files/patch- > Makefile.diff". > > > On Jan 14, 2008, at 18:12, Ryan Schmidt wrote: > >> I see now that ppmtomd is more difficult to compile than most >> software. As such, as soon as someone figures out how to do it, a >> portfile should be created so nobody else has to figure it out again. >> >> I'm working on a portfile. I'll see how far I can get. >> >> >> On Jan 14, 2008, at 17:35, Matt wrote: >> >>> Hi Ryan, >>> >>> Thanks for the help. >>> >>> I did find the following in the makefile for ppmtomd: >>> >>> # if your ppm libraries are not in a standard place, uncomment >>> # and change this. You may also need thing like -R, but if you're >>> # on that sort of system you probably know it! >>> # LDLIBS = -L/usr/local/lib >>> >>> I uncommented and changed the line to: >>> >>> LDLIBS = -L/opt/local/lib >>> >>> I also added your: >>> >>> export CFLAGS="-I/opt/local/include" >>> export LDFLAGS="-L/opt/local/lib" >>> >>> to my ~/.profile >>> >>> Unfortunately, it still can't find those two header files on >>> compiling. >>> >>> Do I need to add something more to the makefile that points to -I/ >>> opt/local/include? >>> >>> Thanks! >>> >>> -Matt >>> >>> >>> >>> On Jan 14, 2008, at 5:26 PM, Ryan Schmidt wrote: >>> >>>> On Jan 14, 2008, at 14:54, Matt wrote: >>>> >>>>> I am trying to compile an intel mac compatible version of an >>>>> open source >>>>> printer driver so I can use my old but beloved Alps printer on >>>>> my new intel >>>>> imac. The source for the driver is here: >>>>> >>>>> http://openprinting.org/show_driver.cgi?driver=ppmtomd&fromprinter=Alps-MD-1000 >>>>> >>>>> I downloaded the source for the driver and tried to perform a >>>>> make on it in >>>>> the terminal. The string of errors showed me that it was >>>>> missing the pgm.h >>>>> and ppm.h header files. Searching for these files online I >>>>> found that they >>>>> belong to the netpbm library. It seemed like the easiest way to >>>>> install >>>>> netpbm and any dependant libraries was through macports. >>>>> >>>>> I succesfully downloaded, installed, and updated macports, then >>>>> told it to >>>>> install netpbm. I got no errors and everything looked good. >>>>> Unfortunately, >>>>> the source for the ppmtomd driver still can't find those header >>>>> files >>>>> (though I can through spotlight). >>>> >>>> You probably haven't told the ppmtomd build system that you've >>>> installed netpbm in /opt/local and it probably won't think to >>>> look there on its own. >>>> >>>> >>>>> When I check to see what ports I have installed I get the >>>>> following output: >>>>> >>>>> iMatt:~ mwoods$ port installed >>>>> The following ports are currently installed: >>>>> jasper @1.701.0_0 (active) >>>>> jpeg @6b_2 (active) >>>>> libpng @1.2.24_0 (active) >>>>> netpbm @10.26.48_0 (active) >>>>> tiff @3.8.2_1+macosx (active) >>>>> zlib @1.2.3_1 (active) >>>>> iMatt:~ mwoods$ >>>>> >>>>> if they were installed properly though, I would think I could >>>>> use the >>>>> "which" command on them. >>>> >>>> If they all provided a binary by the same name as the port, then >>>> yes. But not all ports provide binaries of the same name. Not all >>>> ports even provide binaries. (Some just provide libraries.) >>>> >>>>> Unfortunately, the only port that responds to >>>>> "which" is jasper which I assume is a dependent library that was >>>>> installed >>>>> with netpbm. >>>>> >>>>> iMatt:~ mwoods$ which netpbm >>>>> iMatt:~ mwoods$ which jasper >>>>> /opt/local/bin/jasper >>>> >>>> Yes. As you can see with "port deps netpbm", netpbm declares a >>>> library dependency on jasper. >>>> >>>>> I suspect either netpbm is not installed properly, or I have to >>>>> do something >>>>> to the makefile of the printer driver to get it to find those >>>>> libraries, but >>>>> I haven't been able to figure it out. >>>> >>>> netpbm is likely installed just fine. "port contents netpbm" will >>>> show you everything it installed. It looks like it installs many >>>> binaries but none called "netpbm". It does install a libnetpbm, >>>> but "which" does not search for libraries, only binaries. >>>> >>>> >>>> Bottom line: when you configure and compile ppmtomd, you just >>>> need to tell it where netpbm is. This could help: >>>> >>>> export CFLAGS="-I/opt/local/include" >>>> export LDFLAGS="-L/opt/local/lib" >>>> >>>> And then follow the instructions for how to compile ppmtomd. From mvfranz at gmail.com Mon Jan 14 17:38:45 2008 From: mvfranz at gmail.com (Michael Franz) Date: Mon Jan 14 17:38:17 2008 Subject: freetype-devel Message-ID: Hi, I have a program that needs to link against freetype-devel. I have installed freetype using macports - does this install the devel library? If not how do I install the devel portion? Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080114/8ed8c186/attachment.html From ryandesign at macports.org Mon Jan 14 18:09:07 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 14 18:09:29 2008 Subject: freetype-devel In-Reply-To: References: Message-ID: On Jan 14, 2008, at 19:38, Michael Franz wrote: > I have a program that needs to link against freetype-devel. I have > installed freetype using macports - does this install the devel > library? If not how do I install the devel portion? In MacPorts there is no separation between the binaries and libraries (what some other package managers might install as "freetype") and the headers needed to build other software (what some other package managers might install as "freetype-devel"). Instead, in MacPorts, everything you need is already in "freetype". In MacPorts, there are a few ports named *-devel. But they serve a different and unrelated purpose -- to give you access to development versions of a particular port. Usually you do not need development versions, and can stick with the stable versions offered in the regular versions of the ports. From mvfranz at gmail.com Mon Jan 14 18:34:42 2008 From: mvfranz at gmail.com (Michael Franz) Date: Mon Jan 14 18:34:14 2008 Subject: freetype-devel In-Reply-To: References: Message-ID: Ryan, On Jan 14, 2008 9:09 PM, Ryan Schmidt wrote: > On Jan 14, 2008, at 19:38, Michael Franz wrote: > > > I have a program that needs to link against freetype-devel. I have > > installed freetype using macports - does this install the devel > > library? If not how do I install the devel portion? > > In MacPorts there is no separation between the binaries and libraries > (what some other package managers might install as "freetype") and > the headers needed to build other software (what some other package > managers might install as "freetype-devel"). Instead, in MacPorts, > everything you need is already in "freetype". > This might be asking too much, but how would I solve this problem? checking for FT_Init_FreeType in -lfreetype... no configure: error: "Freetype not found - try installing freetype-devel" Thanks Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080114/29ea2b23/attachment-0001.html From ryandesign at macports.org Mon Jan 14 18:38:37 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon Jan 14 18:38:59 2008 Subject: freetype-devel In-Reply-To: References: Message-ID: <2EF8AFF8-DBD3-4A16-BE90-9FFE551F8ECC@macports.org> On Jan 14, 2008, at 20:34, Michael Franz wrote: > On Jan 14, 2008 9:09 PM, Ryan Schmidt wrote: > >> On Jan 14, 2008, at 19:38, Michael Franz wrote: >> >> > I have a program that needs to link against freetype-devel. I have >> > installed freetype using macports - does this install the devel >> > library? If not how do I install the devel portion? >> >> In MacPorts there is no separation between the binaries and libraries >> (what some other package managers might install as "freetype") and >> the headers needed to build other software (what some other package >> managers might install as "freetype-devel"). Instead, in MacPorts, >> everything you need is already in "freetype". > > > This might be asking too much, but how would I solve this problem? > checking for FT_Init_FreeType in -lfreetype... no > configure: error: "Freetype not found - try installing freetype-devel" Without knowing what software it is that you're trying to build, I can only make basic suggestions about how to compile something against the MacPorts libraries. See this message from earlier today: http://lists.macosforge.org/pipermail/macports-users/2008-January/ 008313.html Especially see the "Bottom line" at the end. From mvfranz at gmail.com Mon Jan 14 18:49:32 2008 From: mvfranz at gmail.com (Michael Franz) Date: Mon Jan 14 18:49:04 2008 Subject: freetype-devel In-Reply-To: <2EF8AFF8-DBD3-4A16-BE90-9FFE551F8ECC@macports.org> References: <2EF8AFF8-DBD3-4A16-BE90-9FFE551F8ECC@macports.org> Message-ID: > > Without knowing what software it is that you're trying to build, I > can only make basic suggestions about how to compile something > against the MacPorts libraries. See this message from earlier today: > > http://lists.macosforge.org/pipermail/macports-users/2008-January/ > 008313.html > > Especially see the "Bottom line" at the end. > > I have been trying this, but it does not solve my problem. export CFLAGS="-I/opt/local/include" export LDFLAGS="-L/opt/local/lib" I am trying to compile icedtea, which as far as I know is not in the Macports. At least, freetype-devel is installed, I only have to find a way to get configure to find it. Thanks for you help! Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080114/80d46506/attachment.html From erchache2000.macports at gmail.com Mon Jan 14 10:32:45 2008 From: erchache2000.macports at gmail.com (erchache2000) Date: Mon Jan 14 19:32:27 2008 Subject: Problems with python idle2.4 Message-ID: <478BAACD.5000501@gmail.com> Hi, i was trying to install python idle2.4 on my macbook pro. I'm using leopard and lastest stable version of macports. I install python idle2.4 and show this error: sh-3.2# idle2.4 Traceback (most recent call last): File "/opt/local/bin/idle2.4", line 5, in ? main() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/idlelib/PyShell.py", line 1350, in main root = Tk(className="Idle") File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/lib-tk/Tkinter.py", line 1571, in __init__ self._loadtk() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/lib-tk/Tkinter.py", line 1589, in _loadtk raise RuntimeError, \ RuntimeError: tk.h version (8.5) doesn't match libtk.a version (8.4) But worst problem is that i make a port -d syn and after port -d update outdated, when try to search idle dissapear! :-S I dont know where is, so, before to send a ticket i want to hear some opinions about this. Any sugestion? Other question, if a package dissapear but is previous installed on my system. How i can know that is deleted from repository? Thanks in advance. From srogers1 at austin.rr.com Mon Jan 14 20:32:22 2008 From: srogers1 at austin.rr.com (Steven Rogers) Date: Mon Jan 14 20:31:54 2008 Subject: sqlite3 update problem In-Reply-To: <288AFD07-CD93-43CD-A9C9-3785D0344865@macports.org> References: <153C061D-FA28-4292-90DA-3372ABBE5B9F@gmail.com> <28AA4DBD-92CB-4050-9324-4C2769AC7DD0@gmail.com> <288AFD07-CD93-43CD-A9C9-3785D0344865@macports.org> Message-ID: <9BF5C48B-C866-4353-AC09-C61AA5A03A32@austin.rr.com> On Jan 14, 2008, at 12:15 AM, Ryan Schmidt wrote: > To be more clear: Garret: No, you do not need to uninstall the ports > that depend on sqlite3. You can, but you most likely don't have to. > Just forcibly uninstall all versions of sqlite3. Then install > sqlite3. . . . I was having similar trouble, and that worked for me. Thanks, SR From mail at thorstenzoerner.de Tue Jan 15 03:11:30 2008 From: mail at thorstenzoerner.de (=?ISO-8859-1?Q?Thorsten_Z=F6rner?=) Date: Tue Jan 15 03:11:06 2008 Subject: Run time messages with Scribus Message-ID: Hi there, for the last three versions of Scribus I've been experiencing warnings or errors (cannot tell) at run time, that look like this: p5085AEFD:~ thorsten$ scribus QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QDateTime::fromString: Parameter out of range QComboBox::changeItem: (Lang) Index 0 out of range QComboBox::changeItem: (Lang) Index 0 out of range QComboBox::changeItem: (Lang) Index 0 out of range QComboBox::changeItem: (Lang) Index 0 out of range QComboBox::changeItem: (Lang) Index 0 out of range QComboBox::changeItem: (Lang) Index 0 out of range and so on. The first block of QDateTime's I get when the program starts up. Then I opened an existing file - no extra output here. Then I clicked into two text boxes and a picture box - resulting in two lines of QComboBox each... When I asked it earlier on this list, I was pointed to newer versions of X11 over at http://trac.macosforge.org/projects/xquartz Now I have the latest version 2.1.2 installed, but the messages remain. My whole setup is this: MacBook Pro, Intel Core Duo 2GHz, running MacOS 10.5.1, MacPorts 1.60, X11 2.1.2, Scribus 1.3.3.11. Thanks in advance for any pointers! Cheers, Thorsten. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2429 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080115/02fa1bab/smime.bin From ryandesign at macports.org Tue Jan 15 03:22:02 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 15 03:22:25 2008 Subject: Compiling IcedTea (was: Re: freetype-devel) In-Reply-To: References: <2EF8AFF8-DBD3-4A16-BE90-9FFE551F8ECC@macports.org> Message-ID: <90067A4A-4CA6-4376-8248-F5ABE6A981A7@macports.org> On Jan 14, 2008, at 20:49, Michael Franz wrote: >> Without knowing what software it is that you're trying to build, I >> can only make basic suggestions about how to compile something >> against the MacPorts libraries. See this message from earlier today: >> >> http://lists.macosforge.org/pipermail/macports-users/2008-January/ >> 008313.html >> >> Especially see the "Bottom line" at the end. > > I have been trying this, but it does not solve my problem. > export CFLAGS="-I/opt/local/include" export LDFLAGS="-L/opt/local/ > lib"I am trying to compile icedtea, which as far as I know is not > in the Macports. At least, freetype-devel is installed, I only have > to find a way to get configure to find it.Thanks for you help!Michael You mean this thing? http://icedtea.classpath.org/ Yow, they have lots of requirements. From their INSTALL file: > The build requirements are as follows: > > GNU libgcj 4.1.2 > Eclipse Java Compiler 3.2.1 > CUPS > libX11 (libXp, libXtst, libXi, libXt) > lesstif > Freetype2 > patch > sed > unzip > md5sum > wget > alsa > xalan > xerces > firefox-devel > glib2-devel > gtk2-devel > ant >= 1.6.5 > libXinerama-devel > giflib-devel > libpng-devel > libjpeg-devel > zlib-devel > mercurial 0.9.5 + forest extension We have ports for many of those things. Not sure if we have ports for all of them. Some are already part of Mac OS X and doesn't need separate ports (CUPS, patch, sed, unzip, md5sum). I don't see a port for alsa (Advanced Linux Sound Architecture?) or the Eclipse Java Compiler. I don't know if alsa works on Mac OS X. We have gcc42 and gcc41 ports, which provide libgcj, but gcc42 is the earliest version that will work on Intel Macs, which we should be supporting today. So hopefully libgcj 4.2.2 would satisfy the requirements. Hopefully once you figure out how to compile IcedTea, you can create a portfile for it. Here is my start at one, though it's not much. I see that IcedTea automatically downloads files and builds them. Hopefully there's a way to tell it where to download them to (it should be pointed at a subdirectory of the distfiles directory). -------------- next part -------------- A non-text attachment was scrubbed... Name: Portfile Type: application/octet-stream Size: 1036 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080115/6983200a/Portfile-0001.obj From ryandesign at macports.org Tue Jan 15 03:24:57 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 15 03:25:17 2008 Subject: Run time messages with Scribus In-Reply-To: References: Message-ID: On Jan 15, 2008, at 05:11, Thorsten Z?rner wrote: > for the last three versions of Scribus I've been experiencing > warnings or errors (cannot tell) at run time, > that look like this: > > p5085AEFD:~ thorsten$ scribus > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QDateTime::fromString: Parameter out of range > QComboBox::changeItem: (Lang) Index 0 out of range > QComboBox::changeItem: (Lang) Index 0 out of range > QComboBox::changeItem: (Lang) Index 0 out of range > QComboBox::changeItem: (Lang) Index 0 out of range > QComboBox::changeItem: (Lang) Index 0 out of range > QComboBox::changeItem: (Lang) Index 0 out of range > > and so on. > > The first block of QDateTime's I get when the program starts up. > Then I opened an existing file - no extra output here. > Then I clicked into two text boxes and a picture box - resulting in > two lines of QComboBox each... > > When I asked it earlier on this list, I was pointed to newer > versions of X11 over at http://trac.macosforge.org/projects/xquartz > Now I have the latest version 2.1.2 installed, but the messages > remain. > > My whole setup is this: > MacBook Pro, Intel Core Duo 2GHz, running MacOS 10.5.1, MacPorts > 1.60, X11 2.1.2, Scribus 1.3.3.11. You're the maintainer; you have to figure it out! You may need to ask the developers of Scribus for help. From mail at thorstenzoerner.de Tue Jan 15 03:34:21 2008 From: mail at thorstenzoerner.de (=?ISO-8859-1?Q?Thorsten_Z=F6rner?=) Date: Tue Jan 15 03:33:58 2008 Subject: Run time messages with Scribus - QT related? In-Reply-To: References: Message-ID: <939F5CEF-3529-457D-8D79-1BCC8AD33990@thorstenzoerner.de> On 15.01.08, at 12:24, Ryan Schmidt wrote: > On Jan 15, 2008, at 05:11, Thorsten Z?rner wrote: > >> for the last three versions of Scribus I've been experiencing >> warnings or errors (cannot tell) at run time, >> that look like this: >> >> p5085AEFD:~ thorsten$ scribus >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QDateTime::fromString: Parameter out of range >> QComboBox::changeItem: (Lang) Index 0 out of range >> QComboBox::changeItem: (Lang) Index 0 out of range >> QComboBox::changeItem: (Lang) Index 0 out of range >> QComboBox::changeItem: (Lang) Index 0 out of range >> QComboBox::changeItem: (Lang) Index 0 out of range >> QComboBox::changeItem: (Lang) Index 0 out of range >> >> and so on. >> >> The first block of QDateTime's I get when the program starts up. >> Then I opened an existing file - no extra output here. >> Then I clicked into two text boxes and a picture box - resulting in >> two lines of QComboBox each... >> >> When I asked it earlier on this list, I was pointed to newer >> versions of X11 over at http://trac.macosforge.org/projects/xquartz >> Now I have the latest version 2.1.2 installed, but the messages >> remain. >> >> My whole setup is this: >> MacBook Pro, Intel Core Duo 2GHz, running MacOS 10.5.1, MacPorts >> 1.60, X11 2.1.2, Scribus 1.3.3.11. > > > You're the maintainer; you have to figure it out! You may need to > ask the developers of Scribus for help. > Come on Ryan, don't give me this. This is not fair! I volunteered to do little things and maybe raise questions like this, but of course I am missing the larger picture, that you certainly have. The first thing to find out is certainly: who to ask? Looks like a QT related issue, right? Any ideas from the QT experts? Greetings, Thorsten. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2429 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080115/24dac631/smime.bin From stefan.schwarzer at grid.unep.ch Tue Jan 15 04:30:56 2008 From: stefan.schwarzer at grid.unep.ch (Stefan Schwarzer) Date: Tue Jan 15 04:30:31 2008 Subject: Error messages with Freetype and XFree86 In-Reply-To: References: <0CA49DE2-8EDB-40FF-B124-4B0D93681EF3@grid.unep.ch> Message-ID: >> gridmac7:Documents schwarzer$ sudo /opt/local/bin/port install gd2 >> ---> Fetching XFree86 >> ---> Attempting to fetch XFree86-4.7.0-src-1.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ >> ---> Attempting to fetch XFree86-4.7.0-src-2.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ >> ---> Attempting to fetch XFree86-4.7.0-src-3.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ >> ---> Attempting to fetch XFree86-4.7.0-src-4.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ >> ---> Attempting to fetch XFree86-4.7.0-src-5.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ >> ---> Verifying checksum(s) for XFree86 >> ---> Extracting XFree86 >> ---> Applying patches to XFree86 >> ---> Configuring XFree86 >> ---> Building XFree86 with target World >> Error: Target org.macports.build returned: shell command " cd "/opt/ >> local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_x11_XFree86/work/xc" && make World " >> returned error 2 >> Command output: including in lib/dps... >> checking ../../config/pswrap/pswrap over in ../../config/pswrap >> first... >> /usr/bin/cc -Os -fno-strict-aliasing -Wall -Wpointer-arith -no-cpp- >> precomp -I. -I../../exports/include "-I/opt/local/var/ >> macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_x11_XFree86/work/include" -D__i386__ - >> D__DARWIN__ -DNO_ALLOCA - >> DCSRG_BASED -DXENVIRONMENT -c -o main.o main.c >> yacc -d pswparser.y >> conflicts: 1 shift/reduce >> mv -f y.tab.c pswparser.c >> + mv -f y.tab.h pswparser.h >> /usr/bin/cc -Os -fno-strict-aliasing -Wall -Wpointer-arith -no-cpp- >> precomp -I. -I../../exports/include "-I/opt/local/var/ >> macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_x11_XFree86/work/include" -D__i386__ - >> D__DARWIN__ -DNO_ALLOCA - >> DCSRG_BASED -DXENVIRONMENT -c -o pswparser.o pswparser.c >> flex -l lexer.l >> lexer.l:108: bad character: % >> lexer.l:108: unknown error processing section 1 >> lexer.l:108: unknown error processing section 1 >> lexer.l:108: bad character: 3 >> lexer.l:108: bad character: 5 >> lexer.l:108: bad character: 0 >> lexer.l:108: bad character: 0 >> lexer.l:109: bad character: % >> lexer.l:109: unknown error processing section 1 >> lexer.l:109: bad character: 2 >> lexer.l:109: bad character: 5 >> lexer.l:109: bad character: 0 >> lexer.l:109: bad character: 0 >> make[4]: *** [lexer.c] Error 1 >> okay, continuing in lib/dps >> ../../config/pswrap/pswrap -a -o dpsclrops.c -h dpsclrops.h >> dpsclrops.psw >> make[3]: ../../config/pswrap/pswrap: Command not found >> make[3]: *** [dpsclrops.c] Error 127 >> make[2]: *** [includes] Error 1 >> make[1]: *** [includes] Error 1 >> make: *** [World] Error 2 >> >> Error: The following dependencies failed to build: XFree86 fontconfig >> Error: Status 1 encountered during processing. > > I'm not sure why this happens. What version of Mac OS X, Xcode and > MacPorts do you have, and what kind of Mac is this happening on? > Based on the existence of "-D__i386__" in your output I assume > you're on an Intel Mac? MacPro, Leopard, latest version of MacPorts (downloaded yesterday) and I'd say latest Xcode as well... From mail at thorstenzoerner.de Tue Jan 15 04:51:16 2008 From: mail at thorstenzoerner.de (=?ISO-8859-1?Q?Thorsten_Z=F6rner?=) Date: Tue Jan 15 04:50:50 2008 Subject: Fwd: Error messages with Freetype and XFree86 References: Message-ID: <46EE53F4-06D7-4253-911D-680A5044BD02@thorstenzoerner.de> On 15.01.08, at 13:30, Stefan Schwarzer wrote: >>> gridmac7:Documents schwarzer$ sudo /opt/local/bin/port install gd2 >>> ---> Fetching XFree86 >>> ---> Attempting to fetch XFree86-4.7.0-src-1.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ >>> ---> Attempting to fetch XFree86-4.7.0-src-2.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ >>> ---> Attempting to fetch XFree86-4.7.0-src-3.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ >>> ---> Attempting to fetch XFree86-4.7.0-src-4.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ >>> ---> Attempting to fetch XFree86-4.7.0-src-5.tgz from http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp.xfree86.org/XFree86/4.7.0/source/ >>> ---> Verifying checksum(s) for XFree86 >>> ---> Extracting XFree86 >>> ---> Applying patches to XFree86 >>> ---> Configuring XFree86 >>> ---> Building XFree86 with target World >>> Error: Target org.macports.build returned: shell command " cd "/ >>> opt/local/var/macports/build/ >>> _opt_local_var_macports_sources_rsync >>> .macports.org_release_ports_x11_XFree86/work/xc" && make World " >>> returned error 2 >>> Command output: including in lib/dps... >>> checking ../../config/pswrap/pswrap over in ../../config/pswrap >>> first... >>> /usr/bin/cc -Os -fno-strict-aliasing -Wall -Wpointer-arith -no-cpp- >>> precomp -I. -I../../exports/include "-I/opt/local/var/ >>> macports/build/ >>> _opt_local_var_macports_sources_rsync >>> .macports.org_release_ports_x11_XFree86/work/include" -D__i386__ - >>> D__DARWIN__ -DNO_ALLOCA - >>> DCSRG_BASED -DXENVIRONMENT -c -o main.o main.c >>> yacc -d pswparser.y >>> conflicts: 1 shift/reduce >>> mv -f y.tab.c pswparser.c >>> + mv -f y.tab.h pswparser.h >>> /usr/bin/cc -Os -fno-strict-aliasing -Wall -Wpointer-arith -no-cpp- >>> precomp -I. -I../../exports/include "-I/opt/local/var/ >>> macports/build/ >>> _opt_local_var_macports_sources_rsync >>> .macports.org_release_ports_x11_XFree86/work/include" -D__i386__ - >>> D__DARWIN__ -DNO_ALLOCA - >>> DCSRG_BASED -DXENVIRONMENT -c -o pswparser.o pswparser.c >>> flex -l lexer.l >>> lexer.l:108: bad character: % >>> lexer.l:108: unknown error processing section 1 >>> lexer.l:108: unknown error processing section 1 >>> lexer.l:108: bad character: 3 >>> lexer.l:108: bad character: 5 >>> lexer.l:108: bad character: 0 >>> lexer.l:108: bad character: 0 >>> lexer.l:109: bad character: % >>> lexer.l:109: unknown error processing section 1 >>> lexer.l:109: bad character: 2 >>> lexer.l:109: bad character: 5 >>> lexer.l:109: bad character: 0 >>> lexer.l:109: bad character: 0 >>> make[4]: *** [lexer.c] Error 1 >>> okay, continuing in lib/dps >>> ../../config/pswrap/pswrap -a -o dpsclrops.c -h dpsclrops.h >>> dpsclrops.psw >>> make[3]: ../../config/pswrap/pswrap: Command not found >>> make[3]: *** [dpsclrops.c] Error 127 >>> make[2]: *** [includes] Error 1 >>> make[1]: *** [includes] Error 1 >>> make: *** [World] Error 2 >>> >>> Error: The following dependencies failed to build: XFree86 >>> fontconfig >>> Error: Status 1 encountered during processing. >> >> I'm not sure why this happens. What version of Mac OS X, Xcode and >> MacPorts do you have, and what kind of Mac is this happening on? >> Based on the existence of "-D__i386__" in your output I assume >> you're on an Intel Mac? > > MacPro, Leopard, latest version of MacPorts (downloaded yesterday) > and I'd say latest Xcode as well... Hi Stefan, do you really want XFree86? I guess, you don't. XFree86 is often only chosen because a more recent version of X11 is not available. Try to get the latest X11 from http://trac.macosforge.org/projects/xquartz You install this on top the existing Leopard-X11 and the X11-SDK from the Leopard Install DVD. Clean everything up in MacPorts and try to compile again. If the "right" X11 is availble, MacPorts won't bother with XFree86. At least this is the case, when I install Scribus: Scribus nominally also depends on XFree86, but if a fresher X11 is around, it goes with this instead. Good luck, Thorsten. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2429 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080115/0ca2cb5f/smime.bin From chad.a.chamberlin at nasa.gov Tue Jan 15 09:05:10 2008 From: chad.a.chamberlin at nasa.gov (Chad Chamberlin) Date: Tue Jan 15 09:05:11 2008 Subject: MacPorts and a2ps Message-ID: Hello all, I need help with installing a2ps. I think I am getting a fairly simple error. I am brand new to MacPorts and recently installed it just so that I could install a2ps. I did contact the maintainer of a2ps, mike@pentangle.net, but he is on vacation for three weeks. I believe I installed MacPorts correctly and believe I have successfully installed the aspell port but am getting the following error when trying to install a2ps: Error: Target org.macports.patch returned: error copying "/usr/share/libtool/config.guess": no such file or directory Error: Status 1 encountered during processing. I am not sure if this is the right user list for this. I did read as many things as I could find at MacPorts.org and did not find anything pertaining to this problem. Any help or direction would be greatly appreciated. Thanks Chad ---------------------------------------------- "sw_vers" ProductName: Mac OS X ProductVersion: 10.4.11 BuildVersion: 8S2167 "uname -a" Darwin KOW000000954922.local 8.11.1 Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386 i386 "sudo port -v -d install a2ps >> a2ps_help" ---> Fetching a2ps ---> Verifying checksum(s) for a2ps ---> Checksumming a2ps-4.13b.tar.gz ---> Extracting a2ps ---> Extracting a2ps-4.13b.tar.gz ---> Applying patches to a2ps ---> Applying /opt/local/var/macports/sources/rsync.macports.org/release/ports/print/a2ps/ files/patch-ps-base.ps patching file ps/base.ps Warning: the following items did not execute (for a2ps): org.macports.activate org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/prin t/a2ps DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/print/a2ps DEBUG: Requested variant i386 is not provided by port a2ps. DEBUG: Requested variant macosx is not provided by port a2ps. DEBUG: Executing variant darwin provides darwin DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/prin t/psutils DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/print/psuti ls DEBUG: Requested variant darwin is not provided by port psutils. DEBUG: Requested variant i386 is not provided by port psutils. DEBUG: Requested variant macosx is not provided by port psutils. DEBUG: Searching for dependency: psutils DEBUG: Found Dependency: receipt exists for psutils DEBUG: Executing org.macports.main (a2ps) DEBUG: Executing org.macports.fetch (a2ps) DEBUG: Executing org.macports.checksum (a2ps) DEBUG: Correct (md5) checksum for a2ps-4.13b.tar.gz DEBUG: Executing org.macports.extract (a2ps) DEBUG: setting option extract.args to /opt/local/var/macports/distfiles/a2ps/a2ps-4.13b.tar.gz DEBUG: Environment: DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macport s.org_release_ports_print_a2ps/work" && gzip -dc /opt/local/var/macports/distfiles/a2ps/a2ps-4.13b.tar.gz | /usr/bin/gnutar --no-same-owner -xf -' DEBUG: Executing org.macports.patch (a2ps) DEBUG: Environment: DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macport s.org_release_ports_print_a2ps/work/a2ps-4.13" && patch -p0' DEBUG: Executing proc-post-org.macports.patch-patch-0 Error: Target org.macports.patch returned: error copying "/usr/share/libtool/config.guess": no such file or directory Error: Status 1 encountered during processing. From mvfranz at gmail.com Tue Jan 15 09:41:48 2008 From: mvfranz at gmail.com (Michael Franz) Date: Tue Jan 15 09:41:18 2008 Subject: Compiling IcedTea (was: Re: freetype-devel) In-Reply-To: <90067A4A-4CA6-4376-8248-F5ABE6A981A7@macports.org> References: <2EF8AFF8-DBD3-4A16-BE90-9FFE551F8ECC@macports.org> <90067A4A-4CA6-4376-8248-F5ABE6A981A7@macports.org> Message-ID: On Jan 15, 2008 6:22 AM, Ryan Schmidt wrote: > > On Jan 14, 2008, at 20:49, Michael Franz wrote: > > >> Without knowing what software it is that you're trying to build, I > >> can only make basic suggestions about how to compile something > >> against the MacPorts libraries. See this message from earlier today: > >> > >> http://lists.macosforge.org/pipermail/macports-users/2008-January/ > >> 008313.html > >> > >> Especially see the "Bottom line" at the end. > > > > I have been trying this, but it does not solve my problem. > > export CFLAGS="-I/opt/local/include" export LDFLAGS="-L/opt/local/ > > lib"I am trying to compile icedtea, which as far as I know is not > > in the Macports. At least, freetype-devel is installed, I only have > > to find a way to get configure to find it.Thanks for you help!Michael > > You mean this thing? > > http://icedtea.classpath.org/ > Yes, that is the one. I think the eclipse compiler is easy, as it is pure java. Some of the other things are not 100% necessary. I think there are some work-arounds for them. I won't know until I get to each problem. Since I have Linux, I am hoping it will be easy to determine what is missing and how the build should work. > > Yow, they have lots of requirements. From their INSTALL file: > > > The build requirements are as follows: > > > > GNU libgcj 4.1.2 > > Eclipse Java Compiler 3.2.1 > > CUPS > > libX11 (libXp, libXtst, libXi, libXt) > > lesstif > > Freetype2 > > patch > > sed > > unzip > > md5sum > > wget > > alsa > > xalan > > xerces > > firefox-devel > > glib2-devel > > gtk2-devel > > ant >= 1.6.5 > > libXinerama-devel > > giflib-devel > > libpng-devel > > libjpeg-devel > > zlib-devel > > mercurial 0.9.5 + forest extension > > We have ports for many of those things. Not sure if we have ports for > all of them. Some are already part of Mac OS X and doesn't need > separate ports (CUPS, patch, sed, unzip, md5sum). > > I don't see a port for alsa (Advanced Linux Sound Architecture?) or > the Eclipse Java Compiler. I don't know if alsa works on Mac OS X. We > have gcc42 and gcc41 ports, which provide libgcj, but gcc42 is the > earliest version that will work on Intel Macs, which we should be > supporting today. So hopefully libgcj 4.2.2 would satisfy the > requirements. I struggled with getting 4.2.2 to compile - I was using an older version of XCode - needed 2.4 to get it to compile. > Hopefully once you figure out how to compile IcedTea, you can create > a portfile for it. Here is my start at one, though it's not much. > > I see that IcedTea automatically downloads files and builds them. > Hopefully there's a way to tell it where to download them to (it > should be pointed at a subdirectory of the distfiles directory). > > Thanks for the Portfile start - I was thinking that maybe using macports will help with the configuration script. Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080115/ab228d09/attachment.html From mvfranz at gmail.com Tue Jan 15 09:45:06 2008 From: mvfranz at gmail.com (Michael Franz) Date: Tue Jan 15 09:44:35 2008 Subject: Compiling IcedTea (was: Re: freetype-devel) In-Reply-To: <90067A4A-4CA6-4376-8248-F5ABE6A981A7@macports.org> References: <2EF8AFF8-DBD3-4A16-BE90-9FFE551F8ECC@macports.org> <90067A4A-4CA6-4376-8248-F5ABE6A981A7@macports.org> Message-ID: > > > The build requirements are as follows: > > > > GNU libgcj 4.1.2 > > Eclipse Java Compiler 3.2.1 > > CUPS > > libX11 (libXp, libXtst, libXi, libXt) > > lesstif > > Freetype2 > > patch > > sed > > unzip > > md5sum > > wget > > alsa > > xalan > > xerces > > firefox-devel > > glib2-devel > > gtk2-devel > > ant >= 1.6.5 > > libXinerama-devel > > giflib-devel > > libpng-devel > > libjpeg-devel > > zlib-devel > > mercurial 0.9.5 + forest extension > I looked at the Porfile, that is areally good start. The xerces and xalan are the java versions, those already exist in the ports. As I said before, the eclipse compiler should be easy, so it looks like only the alsa is the missing dependency. thanks again Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080115/82583e98/attachment.html From ngetker at mac.com Tue Jan 15 10:03:53 2008 From: ngetker at mac.com (Neil Getker) Date: Tue Jan 15 10:03:26 2008 Subject: ClusterSSH / Leopard Fix Message-ID: <74C3F371-41C5-4D31-A2BA-B9407027D9F5@mac.com> I posted a thread on here awhile ago, detailing problems with ClusterSSH and Leopard. I found a solution a few days later, but never posted it. Someone emailed me a couple of days ago so here is the solution for all, enjoy. From either an upgrade or a clean install of Leopard: (If old caches exist from a upgrade, remove from /var/cache) Install All SDK/XCODE 3.0 Tools. After that, from a Terminal: sudo /usr/bin/perl -MCPAN -e shell install CPAN::Bundle (wait too fucking long) force install Tk force install X11::Protocol After that, download clusterssh from http://sourceforge.net/project/showfiles.php?group_id=89139 untar, cd into dir sudo perl -f Makefile This will install it to /usr/local/bin/ WOAH NELLY! Don't run it yet, won't work. You need a few things leopard doesn't install by default that tiger did: An xinitrc, copy the system default from: cp /usr/X11/lib/X11/xinit/xinitrc ~/.xinitrc A bashrc to set ur enviornment variables. Here is mine: source /etc/profile DISPLAY=127.0.0.1:0.0;export DISPLAY Now, you can run X11 and you should see a normal prompt in xterm, not the weird bash 3.21# And just running cssh or whatever works fine. -Neil From jochen at fhi-berlin.mpg.de Tue Jan 15 10:30:19 2008 From: jochen at fhi-berlin.mpg.de (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Tue Jan 15 10:30:01 2008 Subject: ClusterSSH / Leopard Fix In-Reply-To: <74C3F371-41C5-4D31-A2BA-B9407027D9F5@mac.com> References: <74C3F371-41C5-4D31-A2BA-B9407027D9F5@mac.com> Message-ID: On 15.01.2008, at 19:03, Neil Getker wrote: > DISPLAY=127.0.0.1:0.0;export DISPLAY Doesn't Leopard start X11 on demand via launchd via an corresponding socket in the DISPLAY variable? You are just defeating that... Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080115/75a6622b/PGP.bin From daniel at danieloberhoff.de Tue Jan 15 11:54:58 2008 From: daniel at danieloberhoff.de (Daniel Oberhoff) Date: Tue Jan 15 11:54:33 2008 Subject: tetex won't build on my mbp c2d running Leopard Message-ID: <1FE12163-64E7-4786-8C88-9AC351163ECE@danieloberhoff.de> I get this kind of odd error when trying to build teTex. Basically there is stray "1" in the list of objects to link. It works out if I go to the build directory and manually enter the correct link command. error message: Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_teTeX/work/tetex-src-3.0" && make all " returned error 2 [...] /usr/bin/gcc-4.0 -o xdvi-xaw.bin browser.o dvi-draw.o dvi-init.o dvisel.o encodings.o events.o filehist.o font-open.o gf.o hypertex.o image-magick.o mime.o my-snprintf.o my-vsnprintf.o pagehist.o pk.o print-internal.o psdps.o psgs.o psheader.o psnews.o read-mapfile.o search-internal.o special.o string-utils.o tfmload.o util.o vf.o xdvi.o xserver-info.o x_util.o 1 -L/opt/local/lib ./gui/ libgui.a ../../libs/t1lib/libt1.a ../../libs/t1lib/../type1/libtype1.a -L/usr/lib/ruby -L/usr/X11/lib -lXaw -lXmu -lXt -lSM -lICE -lXp -lXext -liconv -lXpm -lX11 -lXau -lXdmcp ../kpathsea/.libs/libkpathsea.a -lm i686-apple-darwin9-gcc-4.0.1: 1: No such file or directory make[2]: *** [xdvi-xaw.bin] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1 Best Daniel From andrew.capon at zen.co.uk Tue Jan 15 13:36:16 2008 From: andrew.capon at zen.co.uk (Andrew Capon) Date: Tue Jan 15 13:35:53 2008 Subject: libxml2 checksum problem Message-ID: <381D8BFD-EE13-4C94-B07D-5E516BAD51EB@zen.co.uk> Hi Guys, I don't know if this is the correct place to ask but I thought I would start here. Basically I am trying to get ethereal or wireshark running on my MacPro. I am having a problem with libxml2 and checksums as shown here: MacPro:~ andrewcapon$ sudo port clean --all libxml2 ---> Cleaning libxml2 MacPro:~ andrewcapon$ sudo port -d install libxml2 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libxml2 DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/textproc/libxml2 DEBUG: Requested variant darwin is not provided by port libxml2. DEBUG: Requested variant i386 is not provided by port libxml2. DEBUG: Requested variant macosx is not provided by port libxml2. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/textproc/libiconv DEBUG: Requested variant darwin is not provided by port libiconv. DEBUG: Requested variant i386 is not provided by port libiconv. DEBUG: Requested variant macosx is not provided by port libiconv. DEBUG: Searching for dependency: libiconv DEBUG: Found Dependency: receipt exists for libiconv DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/archivers/zlib DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/archivers/zlib DEBUG: Requested variant darwin is not provided by port zlib. DEBUG: Requested variant i386 is not provided by port zlib. DEBUG: Requested variant macosx is not provided by port zlib. DEBUG: Searching for dependency: zlib DEBUG: Found Dependency: receipt exists for zlib DEBUG: Executing org.macports.main (libxml2) ---> Fetching libxml2 DEBUG: Executing org.macports.fetch (libxml2) ---> libxml2-2.6.30.tar.gz doesn't seem to exist in /opt/local/var/ macports/distfiles/libxml2 ---> Attempting to fetch libxml2-2.6.30.tar.gz from http://xmlsoft.org/sources/ % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 4615k 100 4615k 0 0 432k 0 0:00:10 0:00:10 --:--:-- 480k ---> Verifying checksum(s) for libxml2 DEBUG: Executing org.macports.checksum (libxml2) ---> Checksumming libxml2-2.6.30.tar.gz Error: Checksum (md5) mismatch for libxml2-2.6.30.tar.gz Portfile checksum: libxml2-2.6.30.tar.gz md5 460e6d853e824da700d698532e57316b Distfile checksum: libxml2-2.6.30.tar.gz md5 5a5bfd9a611d113e0b28e650a979ca4e Error: Checksum (sha1) mismatch for libxml2-2.6.30.tar.gz Portfile checksum: libxml2-2.6.30.tar.gz sha1 519701df3a10770980e993336fe19ef7d95b5bba Distfile checksum: libxml2-2.6.30.tar.gz sha1 f59910a08c292a93d1c3a677e10ab64792c4915c Error: Checksum (rmd160) mismatch for libxml2-2.6.30.tar.gz Portfile checksum: libxml2-2.6.30.tar.gz rmd160 8adcca2a60b4e90de898d9710a3a45069b73bbfe Distfile checksum: libxml2-2.6.30.tar.gz rmd160 4a7d23ee18c4df5269784cf64e68901c4a5428b1 Error: Target org.macports.checksum returned: Unable to verify file checksums Warning: the following items did not execute (for libxml2): org.macports.activate org.macports.extract org.macports.checksum org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. MacPro:~ andrewcapon$ How do I go about trying to resolve this issue? Thanks for any help Andy From sfiera at macports.org Tue Jan 15 14:20:25 2008 From: sfiera at macports.org (Chris Pickel) Date: Tue Jan 15 14:19:56 2008 Subject: libxml2 checksum problem In-Reply-To: <381D8BFD-EE13-4C94-B07D-5E516BAD51EB@zen.co.uk> References: <381D8BFD-EE13-4C94-B07D-5E516BAD51EB@zen.co.uk> Message-ID: On 15 Jan, 2008, at 16:36, Andrew Capon wrote: > I don't know if this is the correct place to ask but I thought I > would start here. > > Basically I am trying to get ethereal or wireshark running on my > MacPro. > > I am having a problem with libxml2 and checksums as shown here: This is ticket 13931 [1]. It should be fixed in trunk within a day or two, but a workaround is given on the ticket page if you don't feel like waiting. [1] http://trac.macports.org/projects/macports/ticket/13931 Regards, Chris From andrew.capon at zen.co.uk Tue Jan 15 14:42:40 2008 From: andrew.capon at zen.co.uk (Andrew Capon) Date: Tue Jan 15 14:42:14 2008 Subject: libxml2 checksum problem In-Reply-To: References: <381D8BFD-EE13-4C94-B07D-5E516BAD51EB@zen.co.uk> Message-ID: Hi Chris, Thanks for the info. The workaround has it installing for me Cheers Andy On 15 Jan 2008, at 22:20, Chris Pickel wrote: > On 15 Jan, 2008, at 16:36, Andrew Capon wrote: >> I don't know if this is the correct place to ask but I thought I >> would start here. >> >> Basically I am trying to get ethereal or wireshark running on my >> MacPro. >> >> I am having a problem with libxml2 and checksums as shown here: > > This is ticket 13931 [1]. It should be fixed in trunk within a day > or two, but a workaround is given on the ticket page if you don't > feel like waiting. > > [1] http://trac.macports.org/projects/macports/ticket/13931 > > > Regards, > > Chris From dnb at ccs.neu.edu Tue Jan 15 14:44:40 2008 From: dnb at ccs.neu.edu (David Blank-Edelman) Date: Tue Jan 15 14:44:19 2008 Subject: ClusterSSH / Leopard Fix In-Reply-To: <20080115213556.C9F2718F5FA@lists.macosforge.org> References: <20080115213556.C9F2718F5FA@lists.macosforge.org> Message-ID: <13EF2A55-FEA9-46A0-8946-9DF016FE8ED0@ccs.neu.edu> > I posted a thread on here awhile ago, detailing problems with > ClusterSSH and Leopard. Hi Neil and others- I'm sorry I didn't see your message earlier because I've been chasing the same bug for a while. Neither of us mentioned ClusterSSH in our subject messages so we missed each other. My message was this: http://lists.macosforge.org/pipermail/macports-users/2008-January/008107.html The problem with the cssh port as it exists is that the p5-tk port (currently without a maintainer) doesn't work. A simple script like this: use Tk; causes a bus error. I don't have the expertise to figure out why that is happening (and I've tried a bunch of things including back-revving to the 8.4.16 port of Tk) and haven't heard back from anyone who does. I tried asking the current Tk port maintainer (the very busy Markus) if he had any ideas but did not hear back. As a last resort, I just wrote the current Perl/ Tk maintainer last night but I haven't heard back from him either. Your recipe gets around this problem by building Perl/Tk using the version of Tk that ships with Leopard. I'm trying to avoid that if I can because it means you are dropping your own user installed stuff into the Apple provided Perl tree vs. installing it into the MacPorts Perl installation. I did something like this for Tiger but was hoping to avoid sullying the Apple stuff this time around. I'd really prefer to get a working p5-tk port if possible. As an aside, you asked about strace in your message. With the addition of Dtrace in Leopard (yay, Apple!), you can now get the same functionality. The easiest way to get this out of the box is to use the dtruss Dtrace script that ships with Leopard (just say "dtruss command", perhaps running under sudo). -- dNb From ryandesign at macports.org Tue Jan 15 15:04:26 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 15 15:04:46 2008 Subject: MacPorts and a2ps In-Reply-To: References: Message-ID: On Jan 15, 2008, at 11:05, Chad Chamberlin wrote: > I need help with installing a2ps. I think I am getting a fairly > simple > error. I am brand new to MacPorts and recently installed it just > so that I > could install a2ps. I did contact the maintainer of a2ps, > mike@pentangle.net, but he is on vacation for three weeks. I believe I > installed MacPorts correctly and believe I have successfully > installed the > aspell port but am getting the following error when trying to > install a2ps: > > Error: Target org.macports.patch returned: error copying > "/usr/share/libtool/config.guess": no such file or directory > Error: Status 1 encountered during processing. > > > I am not sure if this is the right user list for this. I did read > as many > things as I could find at MacPorts.org and did not find anything > pertaining > to this problem. > > Any help or direction would be greatly appreciated. [snip] > Error: Target org.macports.patch returned: error copying > "/usr/share/libtool/config.guess": no such file or directory > Error: Status 1 encountered during processing. This is "the Xcode 2.5 problem" again. Xcode 2.5 no longer provides / usr/share/libtool/. There are a handful of ports that made use