From ryandesign at macports.org Sun Jun 1 00:43:46 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 1 Jun 2008 02:43:46 -0500 Subject: libdvdnav install issue In-Reply-To: <33531acd0805311421k1d0bb800of26ff2e04114a832@mail.gmail.com> References: <33531acd0805302146k76c781b7m148277e4e53d2137@mail.gmail.com> <34FA44EF-C900-4CC8-97DA-4E2F190553D5@macports.org> <33531acd0805311421k1d0bb800of26ff2e04114a832@mail.gmail.com> Message-ID: <0C773BCA-F329-40EA-89E8-077B93C05218@macports.org> On May 31, 2008, at 16:21, David Clark wrote: > On Sat, May 31, 2008 at 2:47 AM, Ryan Schmidt wrote: > >> On May 30, 2008, at 23:46, David Clark wrote: >> >>> I want to install libdvdnav so I can use it with my self-compiled >>> SVN version of mplayer, but alas, I'm having no luck; this is the >>> result: >>> >>> ---> Fetching libdvdnav >>> ---> Attempting to fetch libdvdnav-0.1.10.tar.gz from http:// >>> downloads.sourceforge.net/dvd >>> ---> Verifying checksum(s) for libdvdnav >>> ---> Extracting libdvdnav >>> ---> Applying patches to libdvdnav >>> ---> Configuring libdvdnav >>> ---> Building libdvdnav with target all >>> [no progress] >>> >>> So I tried it again with the -d flag so I could actually watch >>> the verbose versions of those commands. >>> >>> It turns out that every time it starts to built it, it loops back >>> through the configure again and never goes anywhere: >>> >>> WARNING: `aclocal-1.6' is missing on your system. You should >>> only need it if >>> you modified `acinclude.m4' or `configure.ac'. You might >>> want >>> to install the `Automake' and `Perl' packages. Grab them >>> from >>> any GNU archive site. >>> >>> checking for doxygen... no >>> configure: creating ./config.status >>> cd . && /bin/sh ./config.status Makefile >>> config.status: creating Makefile >>> config.status: WARNING: 'Makefile.in' seems to ignore the -- >>> datarootdir setting >>> cd . && \ >>> /bin/sh /opt/local/var/macports/build/ >>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_dev >>> el_libdvdnav/work/libdvdnav-0.1.10/missing --run automake-1.6 -- >>> gnu Makefile >>> /opt/local/var/macports/build/ >>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_dev >>> el_libdvdnav/work/libdvdnav-0.1.10/missing: line 46: >>> automake-1.6: command not found >>> WARNING: `automake-1.6' is missing on your system. You should >>> only need it if >>> you modified `Makefile.am', `acinclude.m4' or >>> `configure.ac'. >>> You might want to install the `Automake' and `Perl' >>> packages. >>> Grab them from any GNU archive site. >>> cd . && /bin/sh /opt/local/var/macports/build/ >>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_dev >>> el_libdvdnav/work/libdvdnav-0.1.10/missing --run autoconf >>> /bin/sh ./config.status --recheck >>> running CONFIG_SHELL=/bin/sh /bin/sh ./configure --prefix=/opt/ >>> local CC=/usr/bin/gcc-4.0 CFLAGS=-O2 CPPFLAGS=-I/opt/local/ >>> include CPP=/usr/bin/cpp-4.0 CXXFLAGS=-O2 CXX=/usr/bin/g++-4.0 >>> FFLAGS=-O2 LDFLAGS=-L/opt/local/lib --no-create --no-recursion >>> >>> I have both perl5.8 and automake installed. I tried uninstalling >>> automake (via MacPorts), but that made no difference. >>> >>> Any clue how I can get this port installed? >> >> I tried on a MacBook Pro with MacPorts 1.6.0 and Xcode 2.5 on Mac >> OS X 10.4.11 and got this: >> >> bswap.h:92:2: error: #error "You need to add endian swap macros >> for you're system" >> >> So it doesn't work at all on Intel Macs. You must be using a >> PowerPC Mac then. What version of Mac OS X, Xcode and MacPorts do >> you have, and on what Mac? >> >> I also tried on a Power Mac G4 (MacPorts 1.6.0, Xcode 2.5, Mac OS >> X 10.4.11) and it worked fine. I do have "aclocal-1.6" in /usr/ >> bin, which means it was provided by Apple. Do you not have this >> file? On my Mac, I believe it was provided by the BSD.pkg part of >> the Mac OS X installation. You could try reinstalling that pkg. > >> > Yeah, that would be helpful, wouldn't it? Sorry about that, my > mind wasn't all there, apparently (current excuse: not enough > sleep and it was late). > > This was on 10.5.3, with MacPorts 1.600 and Xcode 3.0 [gcc powerpc- > apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465)]. I'm > using a dual-2.5 GHz G5. > > I have an Intel MacBook Pro, also, but hadn't bothered to try to > install it on there; while I have the SVN of MPlayer compiled on my > MBP, I never use it. > > Hope this helps; if I can do anything to help you debug, let me know. Ok, I looked on a Leopard machine and I see it only has aclocal-1.10 in /usr/bin, not the older aclocal-1.6. libdvdnav is old. This latest version is from 2004. I suppose it will need to be updated to work with the newer aclocal. But if the developers haven't already released a new version of their own accord in four years, they may no longer be actively developing it. You may need to contact the developers of libdvdnav to see what the situation is, and report this problem (and the lack of Intel Mac support) to them. Usually the maintainer of the port would do that, but libdvdnav has no maintainer, so nobody is looking after it. Don't forget to Reply All so your reply goes to the list too, not just to me. From ryandesign at macports.org Sun Jun 1 00:48:59 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 1 Jun 2008 02:48:59 -0500 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <484215E5.2020406@macports.org> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> Message-ID: On May 31, 2008, at 22:22, Rainer M?ller wrote: >> So this would really be the only way (with a machine and parsing >> software) >> to automatically confirm the probable version information of the ldap >> (openldap port) variant for the library dependency when ldap is a >> variant >> tacked on to postfix? > > Hmmmmmm.... *taking a deep thought* > Aaaah, port info! > > Use like this: > $ port info --depends_build --depends_lib --depends_run postfix +ldap I'm glad to know this! I had no idea. I'll have to incorporate this into my portviz port dependency visualizer to show correct dependencies of installed ports taking into account the selected variants (which it has thus far been unable to do). From listaccount at starionline.com Sun Jun 1 09:27:51 2008 From: listaccount at starionline.com (Jeff Justice) Date: Sun, 1 Jun 2008 11:27:51 -0500 Subject: Can't get 1.6.0 to work Message-ID: Fresh Leopard install. Fresh Xcode 3.0 install. Downloaded MacPorts version 1.6.0 Leopard image. Installed MacPorts. Can't get a man port page. Ran the postflight "fix". Still doesn't work. Suggestions? Jeff J. From iqgrande at gmail.com Sun Jun 1 11:54:19 2008 From: iqgrande at gmail.com (Anthony Agelastos) Date: Sun, 1 Jun 2008 14:54:19 -0400 Subject: Can't get 1.6.0 to work In-Reply-To: References: Message-ID: <6CC2A15D-7D94-418A-9B93-DDA9C061EAE8@gmail.com> Did you modify your .profile file for $MANPATH? From http://www.macports.org/install.php ... You will need to manually adapt your shell's environment to work with MacPorts and your chosen installation prefix (the value passed to configure's --prefix flag, defaulting to /opt/local): Add ${prefix}/bin and ${prefix}/sbin to the start of your PATH environment variable so that MacPorts-installed programs take precedence over system-provided programs of the same name. If a standard MANPATH environment variable already exists (that is, one that doesn't contain any empty components), add the ${prefix}/ share/man path to it so that MacPorts-installed man pages are found by your shell. For Tiger and earlier only, add an appropriate X11 DISPLAY environment variable to run X11-dependent programs, as Leopard takes care of this requirement on its own. On Jun 1, 2008, at 12:27 PM, Jeff Justice wrote: > Fresh Leopard install. Fresh Xcode 3.0 install. Downloaded MacPorts > version 1.6.0 Leopard image. Installed MacPorts. Can't get a man > port page. > > Ran the postflight "fix". Still doesn't work. Suggestions? > > Jeff J. > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080601/d65ce865/attachment.htm From zavpublic at mac.com Sun Jun 1 12:39:26 2008 From: zavpublic at mac.com (Alex Zavatone) Date: Sun, 01 Jun 2008 14:39:26 -0500 Subject: Two new HOWTOs available In-Reply-To: <48420B02.3080006@macports.org> References: <48420B02.3080006@macports.org> Message-ID: <80FD0089-7F56-4249-9FAE-099D0EC6F9C4@mac.com> This didn't make it back out to the list last night. Nice to see the Howto. I got a boatload of errors starting with the build of SQLlite3. I hope this sheds some light on making the Install bullet/newbie-proof Fetching sqlite3 ---> Attempting to fetch sqlite-3.5.7.tar.gz from http://www.sqlite.org/ ---> Verifying checksum(s) for sqlite3 ---> Extracting sqlite3 ---> Configuring sqlite3 ---> 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.7" && gnumake all " returned error 2 Command output: sed -e s/--VERS--/3.5.7/ ./src/sqlite.h.in | \ sed -e s/--VERSION-NUMBER--/3005007/ >sqlite3.h /usr/bin/gcc-4.0 -O2 -o mkkeywordhash ./tool/mkkeywordhash.c ./mkkeywordhash >keywordhash.h /usr/bin/gcc-4.0 -O2 -o lemon ./tool/lemon.c cp ./tool/lempar.c . cp ./src/parse.y . ./lemon parse.y mv parse.h parse.h.temp f ./addopcodes.awk parse.h.temp >parse.h /bin/sh: f: command not found gnumake: [parse.c] Error 127 (ignored) cat parse.h ./src/vdbe.c | -f ./mkopcodeh.awk >opcodes.h /bin/sh: -f: command not found cat: stdout: Broken pipe gnumake: *** [opcodes.h] Error 127 On May 31, 2008, at 9:35 PM, Rainer M?ller wrote: > Hi, > > Let me use this mail to announce two new tutorials in our HOWTO > section > in the wiki to you: > > * How to get a Apache, PHP, MySQL (MAMP) setup > > > * How to setup Subversion client or server > > > These were written by jaguarcy. > I really appreciate the work you have invested for them! > > Kudos, > Rainer > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080601/05f62cbe/attachment.htm From blb at macports.org Sun Jun 1 13:22:22 2008 From: blb at macports.org (Bryan Blackburn) Date: Sun, 1 Jun 2008 14:22:22 -0600 Subject: Two new HOWTOs available In-Reply-To: <80FD0089-7F56-4249-9FAE-099D0EC6F9C4@mac.com> References: <48420B02.3080006@macports.org> <80FD0089-7F56-4249-9FAE-099D0EC6F9C4@mac.com> Message-ID: <826959F9-5C09-4F2D-BA1A-14C3540FDE39@macports.org> On Jun 1, 2008, at 1:39 PM, Alex Zavatone wrote: > This didn't make it back out to the list last night. > > Nice to see the Howto. > > I got a boatload of errors starting with the build of SQLlite3. > > I hope this sheds some light on making the Install bullet/newbie-proof > > Fetching sqlite3 > ---> Attempting to fetch sqlite-3.5.7.tar.gz from http://www.sqlite.org/ ... > f ./addopcodes.awk parse.h.temp >parse.h > /bin/sh: f: command not found Smells like the tcl environment problem with 10.5: Just run the command again and it should be fine. Bryan > > gnumake: [parse.c] Error 127 (ignored) > cat parse.h ./src/vdbe.c | -f ./mkopcodeh.awk >opcodes.h > /bin/sh: -f: command not found > cat: stdout: Broken pipe > gnumake: *** [opcodes.h] Error 127 > ... From zavpublic at mac.com Sun Jun 1 14:10:02 2008 From: zavpublic at mac.com (Zav public) Date: Sun, 01 Jun 2008 16:10:02 -0500 Subject: Two new HOWTOs available In-Reply-To: <826959F9-5C09-4F2D-BA1A-14C3540FDE39@macports.org> References: <48420B02.3080006@macports.org> <80FD0089-7F56-4249-9FAE-099D0EC6F9C4@mac.com> <826959F9-5C09-4F2D-BA1A-14C3540FDE39@macports.org> Message-ID: <67C40E47-7DAC-45B3-8028-C75A016D4025@mac.com> On Jun 1, 2008, at 3:22 PM, Bryan Blackburn wrote: > Smells like the tcl environment problem with 10.5: > > > > > Just run the command again and it should be fine. > > Bryan > Nope. I wish it was that easy. ---> 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.7" && gnumake all " returned error 2 Command output: sort -n -b -k 3 opcodes.h | -f ./mkopcodec.awk >opcodes.c /bin/sh: -f: command not found gnumake: *** [opcodes.c] Error 127 Error: The following dependencies failed to build: apr-util sqlite3 openssl pcre Error: Status 1 encountered during processing. Alex-Zavatones-Fearsome-Power-Mac-G5-2:~ zav$ From blb at macports.org Sun Jun 1 14:29:10 2008 From: blb at macports.org (Bryan Blackburn) Date: Sun, 1 Jun 2008 15:29:10 -0600 Subject: Two new HOWTOs available In-Reply-To: <67C40E47-7DAC-45B3-8028-C75A016D4025@mac.com> References: <48420B02.3080006@macports.org> <80FD0089-7F56-4249-9FAE-099D0EC6F9C4@mac.com> <826959F9-5C09-4F2D-BA1A-14C3540FDE39@macports.org> <67C40E47-7DAC-45B3-8028-C75A016D4025@mac.com> Message-ID: <84EB4F76-ACF6-475F-AD83-928481B32951@macports.org> On Jun 1, 2008, at 3:10 PM, Zav public wrote: > On Jun 1, 2008, at 3:22 PM, Bryan Blackburn wrote: > >> Smells like the tcl environment problem with 10.5: >> >> >> >> >> Just run the command again and it should be fine. >> >> Bryan >> > > Nope. I wish it was that easy. > > ---> 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.7" && > gnumake all " returned error 2 > Command output: sort -n -b -k 3 opcodes.h | -f ./mkopcodec.awk >> opcodes.c > /bin/sh: -f: command not found > gnumake: *** [opcodes.c] Error 127 > Ah, bad assumption on my part. Instead it looks like tickets 14523 and/or 14938: Seems like the workaround may be to just install the nawk port first. Bryan > Error: The following dependencies failed to build: apr-util sqlite3 > openssl pcre > Error: Status 1 encountered during processing. > Alex-Zavatones-Fearsome-Power-Mac-G5-2:~ zav$ > From ryandesign at macports.org Sun Jun 1 17:28:04 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 1 Jun 2008 19:28:04 -0500 Subject: unable to upgrade wine In-Reply-To: <0E526F3D-9085-409C-9A0D-4449B500DCB7@macports.org> References: <74CC6DBA-4700-4A28-900C-2144473ABA64@gmail.com> <0E526F3D-9085-409C-9A0D-4449B500DCB7@macports.org> Message-ID: <49FD26AE-0A62-4135-B045-725742AF8745@macports.org> On May 31, 2008, at 15:34, Bryan Blackburn wrote: > On May 31, 2008, at 7:40 AM, Michael Thon wrote: > >> Hi all - I get the following error when I try to upgrade the port >> wine >> ( :) ) >> I'm using a macbook with Mac OS 10.5.3. openssl and gcc were both >> upgraded recently I think. Any idea what the problem is? >> >> Cheers >> Mike >> >> >> [mike at mikes-macbook ~]$ sudo port upgrade wine >> ---> Fetching wine > ... >> /opt/local/include/openssl/x509.h:207: error: syntax error before >> numeric constant >> In file included from /opt/local/include/openssl/ssl.h:183, >> from internet.h:48, >> from http.c:60: > > You've run into ticket 15461, which is an incompatibility between > OpenSSL 0.9.8h and wine: > > > > I think at this point the only way to deal with it is to use OpenSSL > 0.9.8g until wine is updated to deal with it. It's fixed now, so if you hadn't already followed Bryan's advice, you can wait 30 minutes, then "sudo port selfupdate" and try upgrading wine again. From ryandesign at macports.org Sun Jun 1 22:43:05 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Jun 2008 00:43:05 -0500 Subject: Two new HOWTOs available In-Reply-To: <84EB4F76-ACF6-475F-AD83-928481B32951@macports.org> References: <48420B02.3080006@macports.org> <80FD0089-7F56-4249-9FAE-099D0EC6F9C4@mac.com> <826959F9-5C09-4F2D-BA1A-14C3540FDE39@macports.org> <67C40E47-7DAC-45B3-8028-C75A016D4025@mac.com> <84EB4F76-ACF6-475F-AD83-928481B32951@macports.org> Message-ID: <63F5A6A1-5BB9-4822-905B-BE0259791C88@macports.org> On Jun 1, 2008, at 16:29, Bryan Blackburn wrote: > On Jun 1, 2008, at 3:10 PM, Zav public wrote: > >> On Jun 1, 2008, at 3:22 PM, Bryan Blackburn wrote: >> >>> Smells like the tcl environment problem with 10.5: >>> >>> >> LeopardProblems#environmentvariablesbecomeblankbetweenconfigureandbu >>> ildphases >>>> >>> >>> Just run the command again and it should be fine. >> >> Nope. I wish it was that easy. >> >> ---> 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.7" && >> gnumake all " returned error 2 >> Command output: sort -n -b -k 3 opcodes.h | -f ./mkopcodec.awk >>> opcodes.c >> /bin/sh: -f: command not found >> gnumake: *** [opcodes.c] Error 127 >> > > Ah, bad assumption on my part. Instead it looks like tickets 14523 > and/or 14938: > > > > > Seems like the workaround may be to just install the nawk port first. It still sounds like the Leopard environment variable issue, as Bryan said. Clean the sqlite3 port before trying to install it again. sudo port clean --work sqlite3 sudo port install sqlite3 You should not need to install nawk or do anything else. From ryandesign at macports.org Sun Jun 1 22:58:27 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Jun 2008 00:58:27 -0500 Subject: Two new HOWTOs available In-Reply-To: <732910EA-F04F-470F-B448-2BEFE4F94A88@mac.com> References: <48420B02.3080006@macports.org> <80FD0089-7F56-4249-9FAE-099D0EC6F9C4@mac.com> <826959F9-5C09-4F2D-BA1A-14C3540FDE39@macports.org> <67C40E47-7DAC-45B3-8028-C75A016D4025@mac.com> <84EB4F76-ACF6-475F-AD83-928481B32951@macports.org> <63F5A6A1-5BB9-4822-905B-BE0259791C88@macports.org> <732910EA-F04F-470F-B448-2BEFE4F94A88@mac.com> Message-ID: <1F485674-E571-489A-957B-195DEDDC8B9E@macports.org> On Jun 2, 2008, at 00:46, Alex Zavatone wrote: > On Jun 2, 2008, at 12:43 AM, Ryan Schmidt wrote: > >> It still sounds like the Leopard environment variable issue, as Bryan >> said. > > I'm not on Leopard. That system is a 10.5.x install on a Quad G5. 10.5.x is Leopard. From mike.thon at gmail.com Sun Jun 1 23:02:38 2008 From: mike.thon at gmail.com (Michael Thon) Date: Mon, 2 Jun 2008 08:02:38 +0200 Subject: unable to upgrade wine In-Reply-To: <49FD26AE-0A62-4135-B045-725742AF8745@macports.org> References: <74CC6DBA-4700-4A28-900C-2144473ABA64@gmail.com> <0E526F3D-9085-409C-9A0D-4449B500DCB7@macports.org> <49FD26AE-0A62-4135-B045-725742AF8745@macports.org> Message-ID: <97818F21-AC27-40BC-868D-2AEA05B15C4C@gmail.com> Thanks to the handy instructions on the wiki, I was able to download the Portfile for the previous version of openssl and then get it and wine installed. Now I just upgraded openssl and recompiled wine. All appears to be running smoothly. Cheers Mike From nb at saltybanana.com Sun Jun 1 23:03:08 2008 From: nb at saltybanana.com (Nathan Brazil) Date: Sun, 1 Jun 2008 23:03:08 -0700 Subject: FreeTDS Message-ID: Hi. I see that FreeTDS has no maintainer. The latest portfile lists it at version 0.64, while the latest version at http://freetds.org is 0.82. I have updated and attached the portfile. I installed the port with the +mssql variant, and it works on these systems against SQL Server 2005: - PowerPC G4 running latest version of Tiger - Intel-based Mac running 10.5.2 I don't have commit access. Can someone help me commit the updated portfile? Thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name: Portfile Type: application/octet-stream Size: 1888 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080601/60048a14/attachment.obj -------------- next part -------------- From ryandesign at macports.org Mon Jun 2 02:28:01 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Jun 2008 04:28:01 -0500 Subject: FreeTDS In-Reply-To: References: Message-ID: On Jun 2, 2008, at 01:03, Nathan Brazil wrote: > Hi. I see that FreeTDS has no maintainer. The latest portfile > lists it at version 0.64, while the latest version at http:// > freetds.org is 0.82. > > I have updated and attached the portfile. I installed the port > with the +mssql variant, and it works on these systems against SQL > Server 2005: > > - PowerPC G4 running latest version of Tiger > - Intel-based Mac running 10.5.2 > > I don't have commit access. Can someone help me commit the updated > portfile? I'll work on this tomorrow. There are a few things I want to change and check on before I commit. In the future you can file tickets in our issue tracker. Would you like to be the maintainer of the freetds port? From david.trem at gmail.com Mon Jun 2 06:48:27 2008 From: david.trem at gmail.com (David Trem) Date: Mon, 02 Jun 2008 15:48:27 +0200 Subject: enable to fetch g95 Message-ID: <4843FA2B.7030405@gmail.com> Using fresh install of macport on leopard: ---> Fetching g95 ---> Attempting to fetch g95_source.tgz from http://ftp.g95.org/v0.91/ Error: Target org.macports.fetch returned: fetch failed Is this temporary server problem or something else? David From raimue at macports.org Mon Jun 2 07:39:58 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Mon, 02 Jun 2008 16:39:58 +0200 Subject: enable to fetch g95 In-Reply-To: <4843FA2B.7030405@gmail.com> References: <4843FA2B.7030405@gmail.com> Message-ID: <4844063E.1060002@macports.org> David Trem wrote: > Using fresh install of macport on leopard: > > ---> Fetching g95 > ---> Attempting to fetch g95_source.tgz from http://ftp.g95.org/v0.91/ > Error: Target org.macports.fetch returned: fetch failed > > Is this temporary server problem or something else? g95.org is a server we do not control. So you would have to speak to their admins to find out what the issue is. But you can use our new MacPorts distfiles mirror for now: $ sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/g95/:g95 \ port fetch g95 Or get the file from somewhere else and simply put it into /opt/local/var/macports/distfiles/g95. Rainer From lrivers at gmail.com Mon Jun 2 07:47:21 2008 From: lrivers at gmail.com (Lorin Rivers) Date: Mon, 2 Jun 2008 09:47:21 -0500 Subject: Reading apache, mysql, etc. logs in Console.app automatically Message-ID: <949829840806020747p49571d44y879757f6e7513bdb@mail.gmail.com> Is there a way to have Console load the logs from /opt/local/apache2/logs automatically? Likewise, mysql, etc? I know I can load them via the open dialog and so on, but it would be nice to not have to do that step -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080602/d69a53e7/attachment.htm From ml-vic at de-martino.it Mon Jun 2 08:48:05 2008 From: ml-vic at de-martino.it (Vittorio) Date: Mon, 2 Jun 2008 17:48:05 +0200 Subject: Unable to start postgresql server 8.3.1.1 Message-ID: having always used postgreSQL satisfactorily under FreeBSD I installed postgresql83 & postgresql83-server on my leopard Macbook via sudo port install postgresql83 postgresql83-server. The process concluded successfully . I ran as requested: sudo launchctl load -w /Library/LaunchDaemons/ org.macports.postgresql83-server.plist sudo mkdir -p /opt/local/var/db/postgresql83/defaultdb sudo chown postgres:postgres /opt/local/var/db/postgresql83/defaultdb sudo su postgres -c '/opt/local/lib/postgresql83/bin/initdb -D /opt/ local/var/db/postgresql83/defaultdb' BUT sudo launchctl load -w /Library/LaunchDaemons/ org.macports.postgresql83-server.plist gives the following victor$ ps ax|grep postgres 383 ?? Ss 0:00.00 /opt/local/bin/daemondo -- label=postgresql83-server --start-cmd /opt/local/etc/LaunchDaemons/ org.macports.postgresql83-server/postgresql83-server.wrapper start ; -- stop-cmd /opt/local/etc/LaunchDaemons/org.macports.postgresql83-server/ postgresql83-server.wrapper stop ; --restart-cmd /opt/local/etc/ LaunchDaemons/org.macports.postgresql83-server/postgresql83- server.wrapper restart ; --pid=none and I don't see any process with the usual "postgres" name when I run top. Could you help me straightening postgresql up? Ciao Vittorio From face at CentosPrime.COM Mon Jun 2 08:53:56 2008 From: face at CentosPrime.COM (Chris Janton) Date: Mon, 02 Jun 2008 08:53:56 -0700 Subject: Reading apache, mysql, etc. logs in Console.app automatically In-Reply-To: <949829840806020747p49571d44y879757f6e7513bdb@mail.gmail.com> References: <949829840806020747p49571d44y879757f6e7513bdb@mail.gmail.com> Message-ID: <1EC28318-91A0-499F-932B-47E9090BA0F4@centosprime.com> On 2008-06-02 , at 07:47 , Lorin Rivers wrote: > Is there a way to have Console load the logs from /opt/local/apache2/ > logs > automatically? Likewise, mysql, etc? I know I can load them via the > open > dialog and so on, but it would be nice to not have to do that step Well, don't know about automatic opening, but you can do this cd ~/Library/Logs ln -s /opt/local/apache2/logs ./Apache2Logs at which point the Apache2 logs show up in the "LOG FILES" hierarchy. 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From krischik at users.sourceforge.net Mon Jun 2 11:11:17 2008 From: krischik at users.sourceforge.net (Martin Krischik) Date: Mon, 2 Jun 2008 20:11:17 +0200 Subject: New Howto Message-ID: Hello, just wanted to let you know that I finished a new Howto http://trac.macports.org/wiki/howto/SetupDovecot It's the first of a 3 part series and I hope finish the other parts soon. Martin From blb at macports.org Mon Jun 2 14:36:17 2008 From: blb at macports.org (Bryan Blackburn) Date: Mon, 2 Jun 2008 15:36:17 -0600 Subject: Unable to start postgresql server 8.3.1.1 In-Reply-To: References: Message-ID: <131F78D9-A52D-4A4A-AA12-B1D5C0B46ABD@macports.org> On Jun 2, 2008, at 9:48 AM, Vittorio wrote: > having always used postgreSQL satisfactorily under FreeBSD I installed > postgresql83 & postgresql83-server on my leopard Macbook via > > sudo port install postgresql83 postgresql83-server. > > The process concluded successfully . I ran as requested: > > sudo launchctl load -w /Library/LaunchDaemons/ > org.macports.postgresql83-server.plist > sudo mkdir -p /opt/local/var/db/postgresql83/defaultdb > sudo chown postgres:postgres /opt/local/var/db/postgresql83/defaultdb > sudo su postgres -c '/opt/local/lib/postgresql83/bin/initdb -D /opt/ > local/var/db/postgresql83/defaultdb' > Hmm, the launchctl command on that list should be at the end, not the beginning. If you ran everything in that order, try an unload then load again with launchctl and see if it comes up then. Bryan > ... > Ciao > Vittorio > From tabithamc at gmail.com Mon Jun 2 19:35:25 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Mon, 2 Jun 2008 16:35:25 -1000 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <484215E5.2020406@macports.org> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> Message-ID: <7fccb3000806021935n6318bd5bpcb4101e4109c5722@mail.gmail.com> On Sat, May 31, 2008 at 5:22 PM, Rainer M?ller wrote: > Tabitha McNerney wrote: > >> On 5/30/08, Rainer M?ller wrote: >> $ port deps Xft2 @2.1.12_0 >> >>> @version is ignored for port deps. >>> >>> port deps takes infos from PortIndex only, so it may not always be >>> accurate. >>> >> >> Meaning, if a port has changed (or a new port has been added) but the >> PortIndex has not been updated? >> > > Exactly. Or the port has been installed before, but a new PortIndex (and > Portfile) was synced later which adds a new dependency. > > > [...] > >> So this would really be the only way (with a machine and parsing software) >> to automatically confirm the probable version information of the ldap >> (openldap port) variant for the library dependency when ldap is a variant >> tacked on to postfix? >> > > Hmmmmmm.... *taking a deep thought* > Aaaah, port info! > > Use like this: > $ port info --depends_build --depends_lib --depends_run postfix +ldap > > You can also add --line to compress the output to one line only. You can > hide the label in front of the line and error output by using port -q info. > > As variants are also parsed from the @version notation, you can simply call > this as: > $ port -q info --line --depends_build --depends_lib --depends_run \ postfix > @2.4.6_0+ldap+pcre+sasl+tls > > But if you only need the set of variants you have currently installed: > $ port -q info --line --depends_build --depends_lib --depends_run \ postfix > and installed > > And if you need this for multiple installed ports, this is also possible. > You can use port echo to check to what such a port list expands: > $ port echo \( postfix openldap \) and installed > > "or" is the default logical operator in such lists, so you do not need to > write it explicitely. > > There is still a little bug though, port -q info --depends_build postfix > outputs the usual info as postfix does not have dependencies. I am going to > have a look into this. > > > These are awesome features of port, don't you think? I hope you didn't > invest too much work into writing your own parser for Portfiles... Rainier, very awesome indeed! Like Ryan, I also was not aware of some of these great features. You really saved the day because I took part of the weekend off and then now (a few days later, thanks for your prompt reply to my email a few days ago) I didn't yet write a Portifle parser so now I'm really glad I don't have to write one -- I can easily use the port command-line output especially with all those goodies (such as the --depends_build, etc.) options! > But I have to admit I would have never gotten the idea to use port info if > I would not have made other changes to port/port.tcl today. :-) I didn't have a chance yet to look at the changes in Trac but I'll take a look. I'm glad this triggered some additional thoughts and thank you for your modifications! Its great that we can run MacPorts on a variety of machines that can run Mac OS X or OS X Server (whether its a MacBook or an Xserve). The Xserves are pretty heavy-duty systems and and its great to know that we can build a robust infrastructure of open source programs all glued together with MacPorts! All my best, Tabitha > Maybe we should really make port deps aware of variants. > > Rainer > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080602/4fba31e1/attachment.htm From s.renals at ed.ac.uk Mon Jun 2 22:59:17 2008 From: s.renals at ed.ac.uk (Steve Renals) Date: Tue, 3 Jun 2008 06:59:17 +0100 Subject: Building packages which require Xcode2.5 on leopard Message-ID: <28BDF174-E6A4-4EDC-9D65-1AE10170BAE3@ed.ac.uk> Hello, I'm having problems installing packages which require Xcode MacOSX10.4u.sdk on Leopard. A good example of a package with which I am having problems is aquaterm. I'm running 10.5.3 on a macbook pro, and have Xcode 3.0 installed, and MacPorts 1.6. I install Xcode 2.5 alongside 3.0; it defaults to install as / Xcode2.5 ; packages requiring Xcode2.5 seem to expect /Developer/SDKs/ MacOSX10.4u.sdk, so I symlink to /Xcode2.5/SDKs/MacOSX10.4u.sdk. This gets me one step further, but the build process picks up / Developer/usr/bin/gcc-4.0 (Xcode 3) (rather than /Xcode2.5/usr/bin/ gcc-4.0 ?) and compiling with this 'wrong' gcc fails (excerpt below). How can I build Xcode2.5 packages on leopard with both Xcode2.5 and Xcode3.0 installed? More specifically how do I make the build pick up the Xcode2.5 compiler? thanks - Steve --------------------- /Developer/usr/bin/gcc-4.0 -x objective-c-header -arch ppc -pipe - Wno-trigraphs -fpascal-strings -fasm-blocks -Os -fmessage-length=0 - mtune=G4 -mmacosx-version-min=10.1 -gdwarf-2 -I/opt/local/var/macports/ build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_aqua_aquaterm/work/aquaterm/build/ AquaTerm.build/Deployment/AQTFwk.build/AquaTerm.hmap -Wmost -Wno-four- char-constants -Wno-unknown-pragmas -F/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_aqua_aquaterm/work/aquaterm/build/ Deployment -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_aqua_aquaterm/work/aquaterm/build/ Deployment/include -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_aqua_aquaterm/work/aquaterm/build/ AquaTerm.build/Deployment/AQTFwk.build/DerivedSources -isysroot / Developer/SDKs/MacOSX10.4u.sdk -c /Developer/SDKs/MacOSX10.4u.sdk/ System/Library/Frameworks/AppKit.framework/Headers/AppKit.h -o / Library/Caches/com.apple.Xcode.0/SharedPrecompiledHeaders/AppKit- fnqlhyfibnglwocvctysklolcwvr/AppKit.h.gch In file included from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:12, from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ Frameworks/Foundation.framework/Headers/Foundation.h:6, from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ Frameworks/AppKit.framework/Headers/AppKit.h:10: /Developer/SDKs/MacOSX10.4u.sdk/usr/include/stdarg.h:4:25: error: stdarg.h: No such file or directory In file included from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:16, from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ Frameworks/Foundation.framework/Headers/Foundation.h:6, from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ Frameworks/AppKit.framework/Headers/AppKit.h:10: /Developer/SDKs/MacOSX10.4u.sdk/usr/include/float.h:8:24: error: float.h: No such file or directory -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. From lanceboyle at qwest.net Tue Jun 3 00:30:23 2008 From: lanceboyle at qwest.net (Jerry) Date: Tue, 3 Jun 2008 00:30:23 -0700 Subject: Octave 3.0.1 plotting is very slow In-Reply-To: References: <78841956-3976-4E58-89E6-3242A532759E@qwest.net> Message-ID: <2C1DB5FA-3713-4CF3-8844-B6F50B7AFB8D@qwest.net> On May 31, 2008, at 6:55 AM, Alakazam wrote: > Hi ! > > On 30 mai 08, at 06:41, Jerry wrote: > >> I noticed that plotting with the new Octave version 3.0.1 on Macports >> is very slow compared to older versions of Octave, e.g. 2.1.71. In >> the old Octave, small plots appear instantaneously, probably before >> the Return key hits its stop. In Octave 3.0.1, there is a lag of >> about a second--enough to be slightly annoying. On larger plots, the >> problem gets much worse. Plotting a 100,000 point vector on old >> Octave takes 3 seconds but on Octave 3.0.1 it takes 21 seconds. >> >> I suppose this is something that I should take up with the Octave >> people but I thought I'd tweak this list and the maintainer just in >> case it is something obviously wrong with this particular version. > > Let me start with my (quick) tests : > >> octave:1> t = time(); x = [1:100000]; y = cos(x); plot(x, y); time() >> - t >> ans = 0.29453 > > But as you have noted, the graphic only appears after several seconds > (~10s on my Nov '07 Mac Book). > > So octave still manages the points very fast, but the graphics backend > (X11 GnuPlot) seems to lag a bit. > > If my example is not valid, and doesn't illustrate your problem > correctly, could you give some reduction cases please ? > > I also have a couple of questions which might help understand the > cause of the problem. > > - What machine are you running octave on ? PPC Powerbook 1.5 GHz 2 GB > - What version of Mac OS X are you running ? 10.5.11 > - How did you compile octave 2.1 ? I downloaded it from http://hpc.sourceforge.net/ which is linked from http://www.gnu.org/software/octave/download.html as one of three binary download sites. (The others are Macports and Fink.) > - What graphics backend does octave 2.1 use for plotting ? It uses gnuplot working with Aquaterm--versions of which are installed separately from the Macports versions. Here are some more test results from running this program: The setup is this, run only once per session: x = [1:100000]; y = cos(x); The timed part is this: t = time(); plot(x, y); time() - t which reports an answer (call it t1) some time before the plot appears (and at which time the prompt returns)--the latter time I time on my watch call t2. In all cases the plot was run at least once before timing it. Here are some results for t1 and t2 for various versions which are: 2.1.71 downloaded last year from http://hpc.sourceforge.net 3.0.1 downloaded today from http://hpc.sourceforge.net 3.0.1 installed by Macports a few days ago Octave version Output device t1 t2 ================================================== Macports 3.0.1 Aquaterm 0.64575 22 Macports 3.0.1 X11 0.41969 22 HPC 2.1.71 Aquaterm 2.7057 4 HPC 2.1.71 X11 N/A; uses Aquaterm HPC 3.0.1 Aquaterm 0.62115 22 HPC 3.0.1 X11 N/A; defaults to Terminal.app FWIW, Activity Monitor reports high CPU usage from gnuplot while waiting for the plots to appear. Jerry > > My guess would be that your octave 2.1 doesn't use GnuPlot in the same > way as the macports version of octave 3.0. > > This might be fixable by changing configure/build options, though. If > we reduce the problem to the graphics backend, as I suspect is the > case, then we can look if the graphics backend has changed for all > octave3.0s from octave2.1s, or if this is indeed configurable, and it > is possible to get the old plotting infrastructure back. > >> BTW, the first time or two that I tried to make a plot (simple, like >> plot(x, y)) with the newly installed version of Octave from Macports, >> it failed completely and emitted about 10 lines of Octave-related >> errors. One or two restarts resulted in plots being made, but slowly, >> as noted above. > > > Are you able to reproduce the errors, or at least do you still have > the corresponding octave output ? Did anything (files, paths, relaunch > shell) change between restarts ? Are you talking about Mac OS X > restarts, or simply exiting octave and launching it again > immediately ? > > Regards, > -- > Alakazam > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > From alakazam at melix.net Tue Jun 3 02:10:52 2008 From: alakazam at melix.net (Alakazam) Date: Tue, 3 Jun 2008 11:10:52 +0200 Subject: Octave 3.0.1 plotting is very slow In-Reply-To: <2C1DB5FA-3713-4CF3-8844-B6F50B7AFB8D@qwest.net> References: <78841956-3976-4E58-89E6-3242A532759E@qwest.net> <2C1DB5FA-3713-4CF3-8844-B6F50B7AFB8D@qwest.net> Message-ID: >> - What machine are you running octave on ? > PPC Powerbook 1.5 GHz 2 GB Which explains why plotting takes ~20s for you, and ~10s for me. >> - What version of Mac OS X are you running ? > 10.5.11 Is that 10.4.11 or 10.5.3 ? Anyway, this obviously does not change anything, since we obtain similar results on the performance tests. > Here are some more test results from running this program: > The setup is this, run only once per session: > x = [1:100000]; > y = cos(x); > > The timed part is this: > t = time(); plot(x, y); time() - t > > which reports an answer (call it t1) some time before the plot > appears (and at which time the prompt returns)--the latter time I > time on my watch call t2. In all cases the plot was run at least once > before timing it. This is the same test I was running, so no problem here. > Here are some results for t1 and t2 for various versions which are: > 2.1.71 downloaded last year from http://hpc.sourceforge.net > 3.0.1 downloaded today from http://hpc.sourceforge.net > 3.0.1 installed by Macports a few days ago > > Octave version Output device t1 t2 > ================================================== > Macports 3.0.1 Aquaterm 0.64575 22 > Macports 3.0.1 X11 0.41969 22 > HPC 2.1.71 Aquaterm 2.7057 4 > HPC 2.1.71 X11 N/A; uses Aquaterm > HPC 3.0.1 Aquaterm 0.62115 22 > HPC 3.0.1 X11 N/A; defaults to Terminal.app > > FWIW, Activity Monitor reports high CPU usage from gnuplot while > waiting for the plots to appear. So it would seem the problem may not be with the octave compilation options, but indeed with the octave<->gnuplot interaction. Do any macports users still have old octave2.9s (or, less likely, octave2.1s) installed (via macports) ? Would you be willing to run the quick aforementioned tests to check precisely when the problem may have appeared ? Reading > http://www.gnu.org/software/octave/NEWS-3.html I see that octave 3 (and 2.9) have introduced may changes to the graphics backend, in particular to the way data is output to gnuplot : > Octave now sends data over the same pipe that is used to send > commands to gnuplot. While this avoids the problem of cluttering / > tmp with data files, it is no longer possible to use the mouse to > zoom in on plots. This is a limitation of gnuplot, which is unable > to zoom when the data it plots is not stored in a file. Some work > has been done to fix this problem in newer versions of gnuplot (> > 4.2.2). See for example, this thread on the gnuplot development list. I think it would be best to take this issue to the octave team, and see if they can reproduce the problem (on other platforms even ?) or know where it might come from. You may also want to check the different gnuplot versions used by these octave versions ; maybe changes on that end might also influence the plotting performance. Regards, -- Alakazam From ryandesign at macports.org Tue Jun 3 04:00:34 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jun 2008 06:00:34 -0500 Subject: Building packages which require Xcode2.5 on leopard In-Reply-To: <28BDF174-E6A4-4EDC-9D65-1AE10170BAE3@ed.ac.uk> References: <28BDF174-E6A4-4EDC-9D65-1AE10170BAE3@ed.ac.uk> Message-ID: On Jun 3, 2008, at 00:59, Steve Renals wrote: > I'm having problems installing packages which require Xcode > MacOSX10.4u.sdk on Leopard. A good example of a package with which I > am having problems is aquaterm. > > I'm running 10.5.3 on a macbook pro, and have Xcode 3.0 installed, and > MacPorts 1.6. > > I install Xcode 2.5 alongside 3.0; it defaults to install as / > Xcode2.5 ; packages requiring Xcode2.5 seem to expect /Developer/ > SDKs/ > MacOSX10.4u.sdk, so I symlink to /Xcode2.5/SDKs/MacOSX10.4u.sdk. > This gets me one step further, but the build process picks up / > Developer/usr/bin/gcc-4.0 (Xcode 3) (rather than /Xcode2.5/usr/bin/ > gcc-4.0 ?) and compiling with this 'wrong' gcc fails (excerpt below). > > How can I build Xcode2.5 packages on leopard with both Xcode2.5 and > Xcode3.0 installed? More specifically how do I make the build pick up > the Xcode2.5 compiler? Why do you believe that just because something requires MacOSX10.4u.sdk that it also requires Xcode 2.5? I've not heard that before. I was able to install aquaterm just fine on Mac OS X 10.5.3 with Xcode 3.0 on a MacBook Pro just now, and I don't have Xcode 2.5 installed. But I do have MacOSX10.4u.sdk in /Developer/SDKs. It's not a symlink; it's a normal directory placed there by the Xcode 3.0 installer package. If you don't have that normal directory, you should reinstall Xcode 3.0. Then try installing aquaterm again. I do use MacPorts trunk, not 1.6.0, so maybe that's relevant too. > /Developer/usr/bin/gcc-4.0 -x objective-c-header -arch ppc -pipe - > Wno-trigraphs -fpascal-strings -fasm-blocks -Os -fmessage-length=0 - > mtune=G4 -mmacosx-version-min=10.1 -gdwarf-2 -I/opt/local/var/ > macports/ > build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_aqua_aquaterm/work/aquaterm/build/ > AquaTerm.build/Deployment/AQTFwk.build/AquaTerm.hmap -Wmost -Wno-four- > char-constants -Wno-unknown-pragmas -F/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_aqua_aquaterm/work/aquaterm/build/ > Deployment -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_aqua_aquaterm/work/aquaterm/build/ > Deployment/include -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_aqua_aquaterm/work/aquaterm/build/ > AquaTerm.build/Deployment/AQTFwk.build/DerivedSources -isysroot / > Developer/SDKs/MacOSX10.4u.sdk -c /Developer/SDKs/MacOSX10.4u.sdk/ > System/Library/Frameworks/AppKit.framework/Headers/AppKit.h -o / > Library/Caches/com.apple.Xcode.0/SharedPrecompiledHeaders/AppKit- > fnqlhyfibnglwocvctysklolcwvr/AppKit.h.gch > > In file included from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ > Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:12, > from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ > Frameworks/Foundation.framework/Headers/Foundation.h:6, > from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ > Frameworks/AppKit.framework/Headers/AppKit.h:10: > /Developer/SDKs/MacOSX10.4u.sdk/usr/include/stdarg.h:4:25: error: > stdarg.h: No such file or directory > In file included from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ > Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:16, > from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ > Frameworks/Foundation.framework/Headers/Foundation.h:6, > from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ > Frameworks/AppKit.framework/Headers/AppKit.h:10: > /Developer/SDKs/MacOSX10.4u.sdk/usr/include/float.h:8:24: error: > float.h: No such file or directory From ml-vic at de-martino.it Tue Jun 3 04:05:21 2008 From: ml-vic at de-martino.it (Vittorio) Date: Tue, 3 Jun 2008 13:05:21 +0200 Subject: Unable to start postgresql server 8.3.1.1 In-Reply-To: <131F78D9-A52D-4A4A-AA12-B1D5C0B46ABD@macports.org> References: <131F78D9-A52D-4A4A-AA12-B1D5C0B46ABD@macports.org> Message-ID: <7FE58A82-EAAF-4839-B8BC-CAFDD73DC1FC@de-martino.it> Here it is but the result is unchanged: MacBookVictor:~ victor$ sudo mkdir -p /opt/local/var/db/postgresql83/ defaultdb Password: MacBookVictor:~ victor$ sudo chown postgres:postgres /opt/local/var/db/ postgresql83/defaultdb MacBookVictor:~ victor$ sudo su postgres -c '/opt/local/lib/ postgresql83/bin/initdb -D /opt/local/var/db/postgresql83/defaultdb' MacBookVictor:~ victor$ sudo launchctl load -w /Library/LaunchDaemons/ org.macports.postgresql83-server.plist org.macports.postgresql83-server: Already loaded MacBookVictor:~ victor$ ps a|grep postgr 320 s000 S+ 0:00.00 grep postgr Ciao Vittorio From tabithamc at gmail.com Tue Jun 3 04:30:56 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue, 3 Jun 2008 01:30:56 -1000 Subject: Suggested port command enhancement? Message-ID: <7fccb3000806030430ke5424d5xcbe4ebef164cc70@mail.gmail.com> Hello all -- As seen in some recent threads, I think I have mentioned that I'm building a system that audits and keeps track of MacPorts on some Xserves that I work on. The port command, as Rainer, et al is quite flexible and can be used to source a lot of information. But I believe I have identified a nice future feature of the port command. What I would like to do is conduct an audit of all ports that have been fetched (thus in a separate fetch phase) but not yet installed. I can in fact write a parsing program that looks at: $prefix/var/macports/build which contains underscore-substituted names of directories that have not yet been built, such as: _opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_scrollkeeper > In a text processing language, its relatively easy to write a parser that plucks the name from the above filesystem directory structure, such as: scrollkeeper > by chunking the name into pieces based on the underscore "_" as a separator to split up the name from. However, I discovered there are some ports whose names also include underscores, like this: _opt_local_var_macports_sources_rsync.macports.org_release_ports_audio_libsdl_mixer > Alas, the final underscore in the above example that separates "lisdl" and "mixer" --> "libsdl_mixer" in fact does not map to a final directory on the file system named "mixer" but rather the above maps to: /opt/local/var/macports/sources/ > rsync.macports.org/release/ports/audio/libsdl_mixer > There are ways to work with this situation of course (in my text processing script I can try to map the build directory name to a fully path name) but considering that some ports have underscores in their names (and who knows, maybe many underscores in the future?), it would be really neat if the port command in the future could offer a feature to just return a list of port names who have only been fetched but not installed yet. Maybe, in fact, it might be nice for port to be able to audit each phase of ports all the way from fetch to installed in the steps along the way? Hopefully this is an inspirational idea for advancing MacPorts? Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080603/86f0cb04/attachment.htm From ryandesign at macports.org Tue Jun 3 04:37:00 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jun 2008 06:37:00 -0500 Subject: Unable to start postgresql server 8.3.1.1 In-Reply-To: <7FE58A82-EAAF-4839-B8BC-CAFDD73DC1FC@de-martino.it> References: <131F78D9-A52D-4A4A-AA12-B1D5C0B46ABD@macports.org> <7FE58A82-EAAF-4839-B8BC-CAFDD73DC1FC@de-martino.it> Message-ID: <4AEDCBBD-6BC7-4D9F-A6FA-4BEC19B7C622@macports.org> On Jun 3, 2008, at 06:05, Vittorio wrote: > Here it is but the result is unchanged: > > > MacBookVictor:~ victor$ sudo mkdir -p /opt/local/var/db/postgresql83/ > defaultdb > Password: > MacBookVictor:~ victor$ sudo chown postgres:postgres /opt/local/var/ > db/ > postgresql83/defaultdb > MacBookVictor:~ victor$ sudo su postgres -c '/opt/local/lib/ > postgresql83/bin/initdb -D /opt/local/var/db/postgresql83/defaultdb' > MacBookVictor:~ victor$ sudo launchctl load -w /Library/LaunchDaemons/ > org.macports.postgresql83-server.plist > org.macports.postgresql83-server: Already loaded Then you should first unload it, then load it again. From s.renals at ed.ac.uk Tue Jun 3 05:02:22 2008 From: s.renals at ed.ac.uk (Steve Renals) Date: Tue, 3 Jun 2008 13:02:22 +0100 Subject: Building packages which require Xcode2.5 on leopard In-Reply-To: References: <28BDF174-E6A4-4EDC-9D65-1AE10170BAE3@ed.ac.uk> Message-ID: <139AE096-3EFA-441D-BDE7-EC597F85E7F9@ed.ac.uk> thanks. installs OK now - it never occurred to me that I somehow had an "incomplete" installation of Xcode 3.0... reinstalling xcode did the trick steve On 3 Jun 2008, at 12:00, Ryan Schmidt wrote: > > On Jun 3, 2008, at 00:59, Steve Renals wrote: > >> I'm having problems installing packages which require Xcode >> MacOSX10.4u.sdk on Leopard. A good example of a package with which I >> am having problems is aquaterm. >> >> I'm running 10.5.3 on a macbook pro, and have Xcode 3.0 installed, >> and >> MacPorts 1.6. >> >> I install Xcode 2.5 alongside 3.0; it defaults to install as / >> Xcode2.5 ; packages requiring Xcode2.5 seem to expect /Developer/ >> SDKs/ >> MacOSX10.4u.sdk, so I symlink to /Xcode2.5/SDKs/MacOSX10.4u.sdk. >> This gets me one step further, but the build process picks up / >> Developer/usr/bin/gcc-4.0 (Xcode 3) (rather than /Xcode2.5/usr/bin/ >> gcc-4.0 ?) and compiling with this 'wrong' gcc fails (excerpt below). >> >> How can I build Xcode2.5 packages on leopard with both Xcode2.5 and >> Xcode3.0 installed? More specifically how do I make the build pick >> up >> the Xcode2.5 compiler? > > Why do you believe that just because something requires > MacOSX10.4u.sdk that it also requires Xcode 2.5? I've not heard that > before. I was able to install aquaterm just fine on Mac OS X 10.5.3 > with Xcode 3.0 on a MacBook Pro just now, and I don't have Xcode 2.5 > installed. But I do have MacOSX10.4u.sdk in /Developer/SDKs. It's > not a symlink; it's a normal directory placed there by the Xcode 3.0 > installer package. If you don't have that normal directory, you > should reinstall Xcode 3.0. Then try installing aquaterm again. > > I do use MacPorts trunk, not 1.6.0, so maybe that's relevant too. > > >> /Developer/usr/bin/gcc-4.0 -x objective-c-header -arch ppc -pipe - >> Wno-trigraphs -fpascal-strings -fasm-blocks -Os -fmessage-length=0 - >> mtune=G4 -mmacosx-version-min=10.1 -gdwarf-2 -I/opt/local/var/ >> macports/ >> build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_aquaterm/work/aquaterm/build/ >> AquaTerm.build/Deployment/AQTFwk.build/AquaTerm.hmap -Wmost -Wno- >> four- >> char-constants -Wno-unknown-pragmas -F/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_aquaterm/work/aquaterm/build/ >> Deployment -I/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_aquaterm/work/aquaterm/build/ >> Deployment/include -I/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_aqua_aquaterm/work/aquaterm/build/ >> AquaTerm.build/Deployment/AQTFwk.build/DerivedSources -isysroot / >> Developer/SDKs/MacOSX10.4u.sdk -c /Developer/SDKs/MacOSX10.4u.sdk/ >> System/Library/Frameworks/AppKit.framework/Headers/AppKit.h -o / >> Library/Caches/com.apple.Xcode.0/SharedPrecompiledHeaders/AppKit- >> fnqlhyfibnglwocvctysklolcwvr/AppKit.h.gch >> >> In file included from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ >> Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:12, >> from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ >> Frameworks/Foundation.framework/Headers/Foundation.h:6, >> from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ >> Frameworks/AppKit.framework/Headers/AppKit.h:10: >> /Developer/SDKs/MacOSX10.4u.sdk/usr/include/stdarg.h:4:25: error: >> stdarg.h: No such file or directory >> In file included from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ >> Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:16, >> from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ >> Frameworks/Foundation.framework/Headers/Foundation.h:6, >> from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/ >> Frameworks/AppKit.framework/Headers/AppKit.h:10: >> /Developer/SDKs/MacOSX10.4u.sdk/usr/include/float.h:8:24: error: >> float.h: No such file or directory > > -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. From j.van_den_hoff at fzd.de Tue Jun 3 06:10:08 2008 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Tue, 3 Jun 2008 15:10:08 +0200 Subject: compilation of `hydra' failed Message-ID: <20080603131008.GB15569@marco.fz-rossendorf.de> hi, wanted to check strengths of my password(s) against brute force attacks with `hydra' (hope this is the tool to do it?) but sudo port install hydra yielded #============================CUT================================================ ---> Fetching libssh ---> Attempting to fetch libssh-0.2.tgz from http://www.0xbadc0de.be/libssh ---> Verifying checksum(s) for libssh ---> Extracting libssh ---> Configuring libssh ---> Building libssh with target all ---> Staging libssh into destroot ---> Packaging tgz archive for libssh 0.2_0 ---> Installing libssh 0.2_0 ---> Activating libssh 0.2_0 ---> Cleaning libssh ---> Fetching hydra ---> Attempting to fetch hydra-5.4-src.tar.gz from http://freeworld.thc.org/releases ---> Verifying checksum(s) for hydra ---> Extracting hydra ---> Configuring hydra ---> Building hydra 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_security_hydra/work/hydra-5.4-src" && make all XLIBPATHS="-L/opt/local/lib" CC=/usr/bin/gcc-4.0 " returned error 2 Command output: /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-pop3.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-smb.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-icq.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-cisco-enable.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ldap.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-mysql.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-http-proxy.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-smbnt.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-mssql.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-snmp.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-cvs.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-smtpauth.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-sapr3.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ssh2.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include hydra-ssh2.c:10:2: warning: #warning "If compilation of hydra-ssh2 fails, you are not using v0.11. Download from http://www.0xbadc0de.be/" hydra-ssh2.c: In function 'start_ssh2': hydra-ssh2.c:34: warning: implicit declaration of function 'options_new' hydra-ssh2.c:34: warning: assignment makes pointer from integer without a cast hydra-ssh2.c:44: warning: implicit declaration of function 'options_set_wanted_method' hydra-ssh2.c:44: error: 'KEX_COMP_C_S' undeclared (first use in this function) hydra-ssh2.c:44: error: (Each undeclared identifier is reported only once hydra-ssh2.c:44: error: for each function it appears in.) hydra-ssh2.c:45: error: 'KEX_COMP_S_C' undeclared (first use in this function) hydra-ssh2.c:46: warning: implicit declaration of function 'options_set_port' hydra-ssh2.c:47: warning: implicit declaration of function 'options_set_host' hydra-ssh2.c:48: warning: implicit declaration of function 'options_set_username' hydra-ssh2.c:50: warning: passing argument 1 of 'ssh_connect' from incompatible pointer type hydra-ssh2.c:50: warning: assignment makes pointer from integer without a cast hydra-ssh2.c:82: warning: implicit declaration of function 'ssh_error_code' make: *** [hydra-ssh2.o] Error 1 #============================CUT================================================ the problem seems that libssh-0.2.tgz is fetched from www.0xbadc0de.be but `hydra' expects v0.11??? this is with 10.4.11 and PPC (and current `macports'). any hope of a fix (no maintainer, apparently...)? regards joerg From j.van_den_hoff at fzd.de Tue Jun 3 07:26:23 2008 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Tue, 3 Jun 2008 16:26:23 +0200 Subject: Octave 3.0.1 plotting is very slow In-Reply-To: References: <78841956-3976-4E58-89E6-3242A532759E@qwest.net> <2C1DB5FA-3713-4CF3-8844-B6F50B7AFB8D@qwest.net> Message-ID: <20080603142622.GC15569@marco.fz-rossendorf.de> On Tue, Jun 03, 2008 at 11:10:52AM +0200, Alakazam wrote: > >> - What machine are you running octave on ? > > PPC Powerbook 1.5 GHz 2 GB > > Which explains why plotting takes ~20s for you, and ~10s for me. > > >> - What version of Mac OS X are you running ? > > 10.5.11 > > Is that 10.4.11 or 10.5.3 ? Anyway, this obviously does not change > anything, since we obtain similar results on the performance tests. > > > Here are some more test results from running this program: > > The setup is this, run only once per session: > > x = [1:100000]; > > y = cos(x); > > > > The timed part is this: > > t = time(); plot(x, y); time() - t > > > > which reports an answer (call it t1) some time before the plot > > appears (and at which time the prompt returns)--the latter time I > > time on my watch call t2. In all cases the plot was run at least once > > before timing it. > > This is the same test I was running, so no problem here. > > > Here are some results for t1 and t2 for various versions which are: > > 2.1.71 downloaded last year from http://hpc.sourceforge.net > > 3.0.1 downloaded today from http://hpc.sourceforge.net > > 3.0.1 installed by Macports a few days ago > > > > Octave version Output device t1 t2 > > ================================================== > > Macports 3.0.1 Aquaterm 0.64575 22 > > Macports 3.0.1 X11 0.41969 22 > > HPC 2.1.71 Aquaterm 2.7057 4 > > HPC 2.1.71 X11 N/A; uses Aquaterm > > HPC 3.0.1 Aquaterm 0.62115 22 > > HPC 3.0.1 X11 N/A; defaults to Terminal.app > > > > FWIW, Activity Monitor reports high CPU usage from gnuplot while > > waiting for the plots to appear. > > So it would seem the problem may not be with the octave compilation > options, but indeed with the octave<->gnuplot interaction. > > Do any macports users still have old octave2.9s (or, less likely, > octave2.1s) installed (via macports) ? Would you be willing to run the > quick aforementioned tests to check precisely when the problem may > have appeared ? hi, if it helps: with GNU Octave, version 2.1.71 (powerpc-apple-darwin). and G N U P L O T Version 4.0 patchlevel 0 I get t = 1.7 sec (with a 2 GHz G5 under X11) regards, joerg > > Reading > > > http://www.gnu.org/software/octave/NEWS-3.html > > I see that octave 3 (and 2.9) have introduced may changes to the > graphics backend, in particular to the way data is output to gnuplot : > > > Octave now sends data over the same pipe that is used to send > > commands to gnuplot. While this avoids the problem of cluttering / > > tmp with data files, it is no longer possible to use the mouse to > > zoom in on plots. This is a limitation of gnuplot, which is unable > > to zoom when the data it plots is not stored in a file. Some work > > has been done to fix this problem in newer versions of gnuplot (> > > 4.2.2). See for example, this thread on the gnuplot development list. > > > I think it would be best to take this issue to the octave team, and > see if they can reproduce the problem (on other platforms even ?) or > know where it might come from. > > You may also want to check the different gnuplot versions used by > these octave versions ; maybe changes on that end might also influence > the plotting performance. > > Regards, > -- > Alakazam > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org From ml-vic at de-martino.it Tue Jun 3 07:43:38 2008 From: ml-vic at de-martino.it (Vittorio) Date: Tue, 3 Jun 2008 16:43:38 +0200 Subject: Unable to start postgresql server 8.3.1.1 In-Reply-To: <7FE58A82-EAAF-4839-B8BC-CAFDD73DC1FC@de-martino.it> References: <131F78D9-A52D-4A4A-AA12-B1D5C0B46ABD@macports.org> <7FE58A82-EAAF-4839-B8BC-CAFDD73DC1FC@de-martino.it> Message-ID: <9885BBB8-7E0A-42CF-A086-E3D9014E6BD7@de-martino.it> I Just did as suggested but cannot change the result: MacBookVictor:PostgreSQL victor$ sudo launchctl load -w /Library/ LaunchDaemons/org.macports.postgresql83-server.plist org.macports.postgresql83-server: Already loaded MacBookVictor:PostgreSQL victor$ sudo launchctl unload /Library/ LaunchDaemons/org.macports.postgresql83-server.plist MacBookVictor:PostgreSQL victor$ sudo launchctl load -w /Library/ LaunchDaemons/org.macports.postgresql83-server.plist MacBookVictor:PostgreSQL victor$ ps ax |grep postgres 1379 ?? Ss 0:00.01 /opt/local/bin/daemondo -- label=postgresql83-server --start-cmd /opt/local/etc/LaunchDaemons/ org.macports.postgresql83-server/postgresql83-server.wrapper start ; -- stop-cmd /opt/local/etc/LaunchDaemons/org.macports.postgresql83-server/ postgresql83-server.wrapper stop ; --restart-cmd /opt/local/etc/ LaunchDaemons/org.macports.postgresql83-server/postgresql83- server.wrapper restart ; --pid=none 1384 s000 R+ 0:00.00 grep postgres What elese should I try? Ciao Vittorio From jmr at macports.org Tue Jun 3 09:29:20 2008 From: jmr at macports.org (Joshua Root) Date: Wed, 04 Jun 2008 02:29:20 +1000 Subject: plans for 64bit support In-Reply-To: <476A12CD.9040909@root.id.au> References: <20071219085002.93FEF16F377@lists.macosforge.org> <476A12CD.9040909@root.id.au> Message-ID: <48457160.6010309@macports.org> Joshua Root wrote: > Emil Lundberg wrote: >>>> Is there documentation backing up the >>>> claim >>>> that 64-bit ppc code is slower on 64-bit ppc machines than 32-bit >>>> ppc code? >>> I've seen benchmark numbers that show this. I'll see if I can dig >>> them up. > > OK, I found some of the comparisons I was thinking of: a Linux-based one > with several benchmarks[1], and two Darwin-based ones using Geekbench, > on Tiger[2] and Leopard[3]. > > [1] > [2] > [3] > > > I'll have access to a G5 in a few days' time, so if no one beats me to > it, I'll run some other comparisons. Well, no one beat me to it. ;-) I've added a use_64_bit variant to the nbench-byte and ubench ports, and run them with and without the variant on a Power Mac G5 and a Mac Pro. Results are attached. - Josh -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: nbench-i386.txt Url: http://lists.macosforge.org/pipermail/macports-users/attachments/20080604/7c3567ff/attachment.txt -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: nbench-ppc.txt Url: http://lists.macosforge.org/pipermail/macports-users/attachments/20080604/7c3567ff/attachment-0001.txt -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: nbench-ppc64.txt Url: http://lists.macosforge.org/pipermail/macports-users/attachments/20080604/7c3567ff/attachment-0002.txt -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: nbench-x86_64.txt Url: http://lists.macosforge.org/pipermail/macports-users/attachments/20080604/7c3567ff/attachment-0003.txt -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ubench-i386.txt Url: http://lists.macosforge.org/pipermail/macports-users/attachments/20080604/7c3567ff/attachment-0004.txt -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ubench-ppc.txt Url: http://lists.macosforge.org/pipermail/macports-users/attachments/20080604/7c3567ff/attachment-0005.txt -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ubench-ppc64.txt Url: http://lists.macosforge.org/pipermail/macports-users/attachments/20080604/7c3567ff/attachment-0006.txt -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ubench-x86_64.txt Url: http://lists.macosforge.org/pipermail/macports-users/attachments/20080604/7c3567ff/attachment-0007.txt From pth at ispnet.ca Tue Jun 3 14:07:48 2008 From: pth at ispnet.ca (Peter Hindrichs) Date: Tue, 3 Jun 2008 17:07:48 -0400 Subject: mtr issues Message-ID: Good Day, I have been using "mtr" to check the network signal from my wireless ISP, and it has been working fine until the other day when I updated my system to 10.5.3 I did an uninstall of mtr and reinstalled it, with no change here is what I get when I try "mtr ispnet.ca" Freedom:~ peterhin$ mtr ispnet.ca nodename nor servname provided, or not known: Undefined error: 0 Freedom:~ peterhin$ Now if I do a "ping" or a "traceroute" of the same or any other address it works fine. My question then is this a compatibility issue with 10.5.3 or some other issue. From matrixm at gmail.com Tue Jun 3 14:53:15 2008 From: matrixm at gmail.com (Matrix Mole) Date: Tue, 3 Jun 2008 14:53:15 -0700 Subject: compilation of `hydra' failed In-Reply-To: <20080603192439.GH380@claude.fz-rossendorf.de> References: <20080603131008.GB15569@marco.fz-rossendorf.de> <20080603192439.GH380@claude.fz-rossendorf.de> Message-ID: (sorry forgot to Reply-to-all on the original message to include the mailing list) On Tue, Jun 3, 2008 at 12:24 PM, Joerg van den Hoff wrote: >> Also, be sure to run a port sync to get the most recent version of the >> port files, I believe the old maintainer removed the dependency on >> libssh for hydra until the issue could be resolved. > > I did. `variant ssh' is indeed commented out in the portfile. nevertheless > I get the same error complaining about libssh version mismatch. You may have to uninstall libssh first, if libssh is installed, it will try to pull the libraries into a hydra build. Once you have libssh removed, then hydra should build without ssh support. > I'll wait and observe the status of the ticket. Unfortunately, I don't think much work is going to get done on that ticket since the maintainer of the port has stepped down. I contemplated picking it up myself, but I don't have any time (nor programming experience) to do so. Matrix Mole From ryandesign at macports.org Tue Jun 3 15:19:52 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jun 2008 17:19:52 -0500 Subject: compilation of `hydra' failed In-Reply-To: <20080603131008.GB15569@marco.fz-rossendorf.de> References: <20080603131008.GB15569@marco.fz-rossendorf.de> Message-ID: That's this ticket: http://trac.macports.org/ticket/12765 Since hydra doesn't work with libssh 0.2, the dependency on libssh was removed from the hydra port in r36653. Please "sudo port upgrade" and try installing hydra again. On Jun 3, 2008, at 08:10, Joerg van den Hoff wrote: > wanted to check strengths of my password(s) against brute force > attacks > with `hydra' (hope this is the tool to do it?) but > > sudo port install hydra > > yielded > > #============================CUT====================================== > ========== > ---> Fetching libssh > ---> Attempting to fetch libssh-0.2.tgz from http://www. > 0xbadc0de.be/libssh > ---> Verifying checksum(s) for libssh > ---> Extracting libssh > ---> Configuring libssh > ---> Building libssh with target all > ---> Staging libssh into destroot > ---> Packaging tgz archive for libssh 0.2_0 > ---> Installing libssh 0.2_0 > ---> Activating libssh 0.2_0 > ---> Cleaning libssh > ---> Fetching hydra > ---> Attempting to fetch hydra-5.4-src.tar.gz from http:// > freeworld.thc.org/releases > ---> Verifying checksum(s) for hydra > ---> Extracting hydra > ---> Configuring hydra > ---> Building hydra 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_secur > ity_hydra/work/hydra-5.4-src" && > make all XLIBPATHS="-L/opt/local/lib" CC=/usr/bin/gcc-4.0 " > returned error 2 > Command output: /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-pop3.c - > DLIBOPENSSL -DLIBSSH -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-smb.c -DLIBOPENSSL -DLIBSSH > -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-icq.c -DLIBOPENSSL -DLIBSSH > -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-cisco-enable.c -DLIBOPENSSL > -DLIBSSH -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ldap.c -DLIBOPENSSL - > DLIBSSH -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-mysql.c -DLIBOPENSSL - > DLIBSSH -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-http-proxy.c -DLIBOPENSSL - > DLIBSSH -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-smbnt.c -DLIBOPENSSL - > DLIBSSH -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-mssql.c -DLIBOPENSSL - > DLIBSSH -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-snmp.c -DLIBOPENSSL - > DLIBSSH -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-cvs.c -DLIBOPENSSL -DLIBSSH > -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-smtpauth.c -DLIBOPENSSL - > DLIBSSH -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-sapr3.c -DLIBOPENSSL - > DLIBSSH -I/opt/local/include -I/opt/local/include > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ssh2.c -DLIBOPENSSL - > DLIBSSH -I/opt/local/include -I/opt/local/include > hydra-ssh2.c:10:2: warning: #warning "If compilation of hydra-ssh2 > fails, you are not using v0.11. Download from http://www. > 0xbadc0de.be/" > hydra-ssh2.c: In function 'start_ssh2': > hydra-ssh2.c:34: warning: implicit declaration of function > 'options_new' > hydra-ssh2.c:34: warning: assignment makes pointer from integer > without a cast > hydra-ssh2.c:44: warning: implicit declaration of function > 'options_set_wanted_method' > hydra-ssh2.c:44: error: 'KEX_COMP_C_S' undeclared (first use in > this function) > hydra-ssh2.c:44: error: (Each undeclared identifier is reported > only once > hydra-ssh2.c:44: error: for each function it appears in.) hydra- > ssh2.c:45: error: 'KEX_COMP_S_C' undeclared (first use in this > function) > hydra-ssh2.c:46: warning: implicit declaration of function > 'options_set_port' > hydra-ssh2.c:47: warning: implicit declaration of function > 'options_set_host' > hydra-ssh2.c:48: warning: implicit declaration of function > 'options_set_username' > hydra-ssh2.c:50: warning: passing argument 1 of 'ssh_connect' from > incompatible pointer type > hydra-ssh2.c:50: warning: assignment makes pointer from integer > without a cast > hydra-ssh2.c:82: warning: implicit declaration of function > 'ssh_error_code' > make: *** [hydra-ssh2.o] Error 1 > #============================CUT====================================== > ========== > > the problem seems that libssh-0.2.tgz is fetched from www. > 0xbadc0de.be but `hydra' expects > v0.11??? > > this is with 10.4.11 and PPC (and current `macports'). > > any hope of a fix (no maintainer, apparently...)? From ryandesign at macports.org Tue Jun 3 15:50:00 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Jun 2008 17:50:00 -0500 Subject: Suggested port command enhancement? In-Reply-To: <7fccb3000806030430ke5424d5xcbe4ebef164cc70@mail.gmail.com> References: <7fccb3000806030430ke5424d5xcbe4ebef164cc70@mail.gmail.com> Message-ID: <3B2FEE32-D9C8-46A7-B55A-1484709F1271@macports.org> On Jun 3, 2008, at 06:30, Tabitha McNerney wrote: > As seen in some recent threads, I think I have mentioned that I'm > building a system that audits and keeps track of MacPorts on some > Xserves that I work on. The port command, as Rainer, et al is quite > flexible and can be used to source a lot of information. > > But I believe I have identified a nice future feature of the port > command. What I would like to do is conduct an audit of all ports > that have been fetched (thus in a separate fetch phase) but not yet > installed. I can in fact write a parsing program that looks at: > > $prefix/var/macports/build > > which contains underscore-substituted names of directories that > have not yet been built, such as: > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_textp > roc_scrollkeeper > > In a text processing language, its relatively easy to write a > parser that plucks the name from the above filesystem directory > structure, such as: > > scrollkeeper > > by chunking the name into pieces based on the underscore "_" as a > separator to split up the name from. However, I discovered there > are some ports whose names also include underscores, like this: > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_audio > _libsdl_mixer > > Alas, the final underscore in the above example that separates > "lisdl" and "mixer" --> "libsdl_mixer" in fact does not map to a > final directory on the file system named "mixer" but rather the > above maps to: > > /opt/local/var/macports/sources/rsync.macports.org/release/ports/ > audio/libsdl_mixer > > There are ways to work with this situation of course (in my text > processing script I can try to map the build directory name to a > fully path name) but considering that some ports have underscores > in their names (and who knows, maybe many underscores in the > future?), it would be really neat if the port command in the future > could offer a feature to just return a list of port names who have > only been fetched but not installed yet. Maybe, in fact, it might > be nice for port to be able to audit each phase of ports all the > way from fetch to installed in the steps along the way? > > Hopefully this is an inspirational idea for advancing MacPorts? Why do you want to identify ports that have been fetched but not built? I myself would like to identify ports that have been fetched but not installed. Maybe that's the same thing you meant. I often install ports to verify bugs others have reported, and while I generally remember to uninstall them afterward, I sometimes forget to clean the distfiles, so I'm left with distfiles I don't need which I'd like to remove. This also applies to distfiles for older versions of ports I do still use. With the new "port distfiles" target, I think it could be implemented like this: 1. Get the list of all distfiles (find /opt/local/var/macports/ distfiles -type f) 2. Get the list of installed ports (port installed) 3. For each installed port foo, get the list of distfiles (port distfiles foo) and remove them from the list of distfiles 4. All the distfiles that are left in the list at the end aren't used for any installed port and can be removed to save space The one missing piece of the puzzle is the dist_subdir. Often this is the port name, but a port can override this. I don't know of a way to get the port command to tell me a port's dist_subdir. Now that I think about it, the second missing piece is that "port distfiles" shows the distfiles for the current version of the port. It won't show you distfiles for an older version of that port you have installed. But that might be ok if you generally keep your ports up to date and don't want to install older versions. From blb at macports.org Tue Jun 3 17:01:27 2008 From: blb at macports.org (Bryan Blackburn) Date: Tue, 3 Jun 2008 18:01:27 -0600 Subject: mtr issues In-Reply-To: References: Message-ID: <3C8FA530-3D67-4499-A28B-0BB07831A533@macports.org> On Jun 3, 2008, at 3:07 PM, Peter Hindrichs wrote: > Good Day, > > I have been using "mtr" to check the network signal from my wireless > ISP, and it has been working fine until the other day when I updated > my system to 10.5.3 > > I did an uninstall of mtr and reinstalled it, with no change here is > what I get when I try "mtr ispnet.ca" > > Freedom:~ peterhin$ mtr ispnet.ca > nodename nor servname provided, or not known: Undefined error: 0 > Freedom:~ peterhin$ > > > Now if I do a "ping" or a "traceroute" of the same or any other > address it works fine. > > My question then is this a compatibility issue with 10.5.3 or some > other issue. > Which version of mtr, 0.72 or 0.73? If 0.72, try upgrading it, as it was just updated [1] and one note mentions a patch to getaddrinfo() which could definitely be related to the problem you're seeing. Bryan [1] - From tabithamc at gmail.com Tue Jun 3 17:35:49 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue, 3 Jun 2008 14:35:49 -1000 Subject: Suggested port command enhancement? In-Reply-To: <3B2FEE32-D9C8-46A7-B55A-1484709F1271@macports.org> References: <7fccb3000806030430ke5424d5xcbe4ebef164cc70@mail.gmail.com> <3B2FEE32-D9C8-46A7-B55A-1484709F1271@macports.org> Message-ID: <7fccb3000806031735h2c2680eex6832486dd1b08bed@mail.gmail.com> On 6/3/08, Ryan Schmidt wrote: [SNIP] Why do you want to identify ports that have been fetched but not built? > > I myself would like to identify ports that have been fetched but not > installed. Maybe that's the same thing you meant. Yes, that's what I meant. Fetched but not installed. Thanks, T.M. [SNIP] -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080603/d127ca36/attachment.htm From raimue at macports.org Tue Jun 3 18:05:38 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Wed, 04 Jun 2008 03:05:38 +0200 Subject: Suggested port command enhancement? In-Reply-To: <3B2FEE32-D9C8-46A7-B55A-1484709F1271@macports.org> References: <7fccb3000806030430ke5424d5xcbe4ebef164cc70@mail.gmail.com> <3B2FEE32-D9C8-46A7-B55A-1484709F1271@macports.org> Message-ID: <4845EA62.9010002@macports.org> Ryan Schmidt wrote: > With the new "port distfiles" target, I think it could be implemented > like this: > > 1. Get the list of all distfiles (find /opt/local/var/macports/ > distfiles -type f) > 2. Get the list of installed ports (port installed) > 3. For each installed port foo, get the list of distfiles (port > distfiles foo) and remove them from the list of distfiles > 4. All the distfiles that are left in the list at the end aren't used > for any installed port and can be removed to save space Already possible: $ sudo port mirror installed $ sudo portmirror This should delete any unneeded distfiles. But I agree that this is not really obvious, especially as it requires the use of port mirror instead of port fetch. But usually you don't need any distfile again, so cleaning them all is mostly save: $ sudo port clean --dist installed Or even: $ sudo port clean --dist all Rainer From sonikbuddha at hotmail.com Tue Jun 3 22:11:41 2008 From: sonikbuddha at hotmail.com (Sonikbuddha -) Date: Tue, 3 Jun 2008 22:11:41 -0700 Subject: encfs 1.4.2 fails to configure In-Reply-To: <637D1F2F-C3B0-489B-A590-296B9306CB9D@macports.org> References: <637D1F2F-C3B0-489B-A590-296B9306CB9D@macports.org> Message-ID: I haven't touched this in a while in hopes that developers would be able to resolve this issue before it became an issue but I'm beginning to hurt missing my encoded files. The ticket lists the problem as being directly related to the version of boost and rolling back a version would resolve the issue. How exactly is that achieved? I see neither a means of selecting package versions from the command line or locations for manual downloads, if necessary. Thanks ~c From: sonikbuddha at hotmail.com To: ryandesign at macports.org CC: macports-users at lists.macosforge.org Subject: RE: encfs 1.4.2 fails to configure Date: Mon, 19 May 2008 16:08:45 -0700 Ticket filed for this issue, for those interested in commenting or following: #15348 > CC: macports-users at lists.macosforge.org > From: ryandesign at macports.org > Subject: Re: encfs 1.4.2 fails to configure > Date: Sat, 17 May 2008 03:27:21 -0500 > To: sonikbuddha at hotmail.com > > > On May 16, 2008, at 8:25 PM, Sonikbuddha - wrote: > > > I've been attempting to install the newest version of encfs, > > version 1.4.2, which was released last month, but it has been > > failing every time it attempts to configure with the below error. > > Has anyone else encountered this problem? I have not found a bug > > tracker ticket for it as of yet. > > > > Since I recently reinstalled macports, I have only the most recent > > required packages installed and nothing else. I am running Leopard > > 10.5.2, macports 1.6, xcode 3.0. > > > > Final error in configure output. I am also attaching my config.log: > > > > checking for boostlib>= 1.33... yes > > configure: WARNING: BOOST_CPPFLAGS -I/opt/local/include > > checking whether the Boost::Serialization library is available... yes > > configure: error: Could not link against ! > > I get the same error on 10.4.11 Intel with Xcode 2.4.1. Please file a > bug in the issue tracker: > > http://guide.macports.org/#project > Give to a good cause with every e-mail. Join the i?m Initiative from Microsoft. _________________________________________________________________ Instantly invite friends from Facebook and other social networks to join you on Windows Live? Messenger. https://www.invite2messenger.net/im/?source=TXT_EML_WLH_InviteFriends -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080603/06193404/attachment.htm From ryandesign at macports.org Tue Jun 3 22:30:39 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 4 Jun 2008 00:30:39 -0500 Subject: encfs 1.4.2 fails to configure In-Reply-To: References: <637D1F2F-C3B0-489B-A590-296B9306CB9D@macports.org> Message-ID: <1ED918BA-4071-4CAD-B6A7-4E0DDC100771@macports.org> On Jun 4, 2008, at 00:11, Sonikbuddha - wrote: > I haven't touched this in a while in hopes that developers would be > able to resolve this issue before it became an issue but I'm > beginning to hurt missing my encoded files. The ticket lists the > problem as being directly related to the version of boost and > rolling back a version would resolve the issue. How exactly is > that achieved? I see neither a means of selecting package versions > from the command line or locations for manual downloads, if necessary. See this how-to: http://trac.macports.org/wiki/howto/InstallingOlderPort From lanceboyle at qwest.net Wed Jun 4 00:42:34 2008 From: lanceboyle at qwest.net (Jerry) Date: Wed, 4 Jun 2008 00:42:34 -0700 Subject: Octave 3.0.1 plotting is very slow In-Reply-To: References: <78841956-3976-4E58-89E6-3242A532759E@qwest.net> <2C1DB5FA-3713-4CF3-8844-B6F50B7AFB8D@qwest.net> Message-ID: On Jun 3, 2008, at 2:10 AM, Alakazam wrote: >>> - What version of Mac OS X are you running ? >> 10.5.11 > > Is that 10.4.11 or 10.5.3 ? Anyway, this obviously does not change > anything, since we obtain similar results on the performance tests. Oops. 10.4.11. > > > I think it would be best to take this issue to the octave team, and > see if they can reproduce the problem (on other platforms even ?) > or know where it might come from. You're right, and that was my first hunch. Thanks for your help. Jerry > > You may also want to check the different gnuplot versions used by > these octave versions ; maybe changes on that end might also > influence the plotting performance. > From j.van_den_hoff at fzd.de Wed Jun 4 02:24:22 2008 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Wed, 4 Jun 2008 11:24:22 +0200 Subject: compilation of `hydra' failed In-Reply-To: References: <20080603131008.GB15569@marco.fz-rossendorf.de> <20080603192439.GH380@claude.fz-rossendorf.de> Message-ID: <20080604092421.GA7623@marco.fz-rossendorf.de> On Tue, Jun 03, 2008 at 02:53:15PM -0700, Matrix Mole wrote: > (sorry forgot to Reply-to-all on the original message to include the > mailing list) > > On Tue, Jun 3, 2008 at 12:24 PM, Joerg van den Hoff > wrote: > >> Also, be sure to run a port sync to get the most recent version of the > >> port files, I believe the old maintainer removed the dependency on > >> libssh for hydra until the issue could be resolved. > > > > I did. `variant ssh' is indeed commented out in the portfile. nevertheless > > I get the same error complaining about libssh version mismatch. thanks again (to ryan, too). got it installed now. > > You may have to uninstall libssh first, if libssh is installed, it > will try to pull the libraries into a hydra build. Once you have > libssh removed, then hydra should build without ssh support. > > > I'll wait and observe the status of the ticket. > > Unfortunately, I don't think much work is going to get done on that > ticket since the maintainer of the port has stepped down. I that would be bad. really no hope?? > contemplated picking it up myself, but I don't have any time (nor > programming experience) to do so. regards, joerg > > Matrix Mole From ryandesign at macports.org Wed Jun 4 03:14:53 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 4 Jun 2008 05:14:53 -0500 Subject: compilation of `hydra' failed In-Reply-To: <20080604092421.GA7623@marco.fz-rossendorf.de> References: <20080603131008.GB15569@marco.fz-rossendorf.de> <20080603192439.GH380@claude.fz-rossendorf.de> <20080604092421.GA7623@marco.fz-rossendorf.de> Message-ID: <6A3CFA10-985F-436A-8494-82A363A5D081@macports.org> On Jun 4, 2008, at 04:24, Joerg van den Hoff wrote: > On Tue, Jun 03, 2008 at 02:53:15PM -0700, Matrix Mole wrote: >> (sorry forgot to Reply-to-all on the original message to include the >> mailing list) >> >> On Tue, Jun 3, 2008 at 12:24 PM, Joerg van den Hoff >> wrote: >>>> Also, be sure to run a port sync to get the most recent version >>>> of the >>>> port files, I believe the old maintainer removed the dependency on >>>> libssh for hydra until the issue could be resolved. >>> >>> I did. `variant ssh' is indeed commented out in the portfile. >>> nevertheless >>> I get the same error complaining about libssh version mismatch. > > thanks again (to ryan, too). got it installed now. > >> >> You may have to uninstall libssh first, if libssh is installed, it >> will try to pull the libraries into a hydra build. Once you have >> libssh removed, then hydra should build without ssh support. >> >>> I'll wait and observe the status of the ticket. >> >> Unfortunately, I don't think much work is going to get done on that >> ticket since the maintainer of the port has stepped down. I > > that would be bad. really no hope?? Ticket is resolved. :) From j.van_den_hoff at fzd.de Wed Jun 4 03:23:44 2008 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Wed, 4 Jun 2008 12:23:44 +0200 Subject: compilation of `hydra' failed In-Reply-To: <6A3CFA10-985F-436A-8494-82A363A5D081@macports.org> References: <20080603131008.GB15569@marco.fz-rossendorf.de> <20080603192439.GH380@claude.fz-rossendorf.de> <20080604092421.GA7623@marco.fz-rossendorf.de> <6A3CFA10-985F-436A-8494-82A363A5D081@macports.org> Message-ID: <20080604102343.GA2353@marco.fz-rossendorf.de> On Wed, Jun 04, 2008 at 05:14:53AM -0500, Ryan Schmidt wrote: > > On Jun 4, 2008, at 04:24, Joerg van den Hoff wrote: > > >On Tue, Jun 03, 2008 at 02:53:15PM -0700, Matrix Mole wrote: > >>(sorry forgot to Reply-to-all on the original message to include the > >>mailing list) > >> > >>On Tue, Jun 3, 2008 at 12:24 PM, Joerg van den Hoff > >> wrote: > >>>>Also, be sure to run a port sync to get the most recent version > >>>>of the > >>>>port files, I believe the old maintainer removed the dependency on > >>>>libssh for hydra until the issue could be resolved. > >>> > >>>I did. `variant ssh' is indeed commented out in the portfile. > >>>nevertheless > >>>I get the same error complaining about libssh version mismatch. > > > >thanks again (to ryan, too). got it installed now. > > > >> > >>You may have to uninstall libssh first, if libssh is installed, it > >>will try to pull the libraries into a hydra build. Once you have > >>libssh removed, then hydra should build without ssh support. > >> > >>>I'll wait and observe the status of the ticket. > >> > >>Unfortunately, I don't think much work is going to get done on that > >>ticket since the maintainer of the port has stepped down. I > > > >that would be bad. really no hope?? > > Ticket is resolved. :) > hey, great! thanks a lot. > From j.van_den_hoff at fzd.de Wed Jun 4 08:06:14 2008 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Wed, 4 Jun 2008 17:06:14 +0200 Subject: compilation of `hydra' failed In-Reply-To: <6A3CFA10-985F-436A-8494-82A363A5D081@macports.org> References: <20080603131008.GB15569@marco.fz-rossendorf.de> <20080603192439.GH380@claude.fz-rossendorf.de> <20080604092421.GA7623@marco.fz-rossendorf.de> <6A3CFA10-985F-436A-8494-82A363A5D081@macports.org> Message-ID: <20080604150614.GB18268@marco.fz-rossendorf.de> On Wed, Jun 04, 2008 at 05:14:53AM -0500, Ryan Schmidt wrote: > > On Jun 4, 2008, at 04:24, Joerg van den Hoff wrote: > > >On Tue, Jun 03, 2008 at 02:53:15PM -0700, Matrix Mole wrote: > >>(sorry forgot to Reply-to-all on the original message to include the > >>mailing list) > >> > >>On Tue, Jun 3, 2008 at 12:24 PM, Joerg van den Hoff > >> wrote: > >>>>Also, be sure to run a port sync to get the most recent version > >>>>of the > >>>>port files, I believe the old maintainer removed the dependency on > >>>>libssh for hydra until the issue could be resolved. > >>> > >>>I did. `variant ssh' is indeed commented out in the portfile. > >>>nevertheless > >>>I get the same error complaining about libssh version mismatch. > > > >thanks again (to ryan, too). got it installed now. > > > >> > >>You may have to uninstall libssh first, if libssh is installed, it > >>will try to pull the libraries into a hydra build. Once you have > >>libssh removed, then hydra should build without ssh support. > >> > >>>I'll wait and observe the status of the ticket. > >> > >>Unfortunately, I don't think much work is going to get done on that > >>ticket since the maintainer of the port has stepped down. I > > > >that would be bad. really no hope?? > > Ticket is resolved. :) > > ryan, I'm back to field one: due to your above news, I just did: port clean --all libssh port uninstall hydra #this was the old (working) version without ssh support port clean --all hydra port selfupdate port sync port install hydra which crashed again: ============================CUT====================================== ---> Building hydra with target all /usr/bin/gcc-4.0 -I. -Wall -O2 -o pw-inspector pw-inspector.c /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-vnc.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-pcnfs.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-rexec.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-nntp.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-socks5.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-telnet.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-cisco.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-http.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ftp.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-imap.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-pop3.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-smb.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-icq.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-cisco-enable.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ldap.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-mysql.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-http-proxy.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-smbnt.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-mssql.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-snmp.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-cvs.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-smtpauth.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-sapr3.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ssh2.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include hydra-ssh2.c:10:2: warning: #warning "If compilation of hydra-ssh2 fails, you are not using v0.11. Download from http://www.0xbadc0de.be/" hydra-ssh2.c:12:27: error: libssh/libssh.h: No such file or directory hydra-ssh2.c: In function 'start_ssh2': hydra-ssh2.c:24: error: 'SSH_SESSION' undeclared (first use in this function) hydra-ssh2.c:24: error: (Each undeclared identifier is reported only once hydra-ssh2.c:24: error: for each function it appears in.) hydra-ssh2.c:24: error: 'ssh_session' undeclared (first use in this function) hydra-ssh2.c:25: error: 'SSH_OPTIONS' undeclared (first use in this function) hydra-ssh2.c:25: error: 'ssh_opt' undeclared (first use in this function) hydra-ssh2.c:34: warning: implicit declaration of function 'options_new' hydra-ssh2.c:44: warning: implicit declaration of function 'options_set_wanted_method' hydra-ssh2.c:44: error: 'KEX_COMP_C_S' undeclared (first use in this function) hydra-ssh2.c:45: error: 'KEX_COMP_S_C' undeclared (first use in this function) hydra-ssh2.c:46: warning: implicit declaration of function 'options_set_port' hydra-ssh2.c:47: warning: implicit declaration of function 'options_set_host' hydra-ssh2.c:48: warning: implicit declaration of function 'options_set_username' hydra-ssh2.c:50: warning: implicit declaration of function 'ssh_connect' hydra-ssh2.c:51: warning: implicit declaration of function 'ssh_get_error' hydra-ssh2.c:51: warning: assignment makes pointer from integer without a cast hydra-ssh2.c:53: warning: passing argument 2 of 'strncmp' makes pointer from integer without a cast hydra-ssh2.c:66: warning: implicit declaration of function 'ssh_userauth_kbdint' hydra-ssh2.c:67: error: 'SSH_AUTH_INFO' undeclared (first use in this function) hydra-ssh2.c:68: warning: implicit declaration of function 'ssh_userauth_kbdint_setanswer' hydra-ssh2.c:73: error: 'SSH_AUTH_SUCCESS' undeclared (first use in this function) hydra-ssh2.c:73: warning: implicit declaration of function 'ssh_userauth_password' hydra-ssh2.c:74: warning: implicit declaration of function 'ssh_disconnect' hydra-ssh2.c:82: warning: implicit declaration of function 'ssh_error_code' make: *** [hydra-ssh2.o] Error 1 Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_security_hydra/work/hydra-5.4-src" && make all XIPATHS="-I/opt/local/include/libssh01 -I/opt/local/include" XLIBPATHS="-L/opt/local/lib/libssh01 -L/opt/local/lib" " returned error 2 Command output: /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-sapr3.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ssh2.c -DLIBOPENSSL -DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include hydra-ssh2.c:10:2: warning: #warning "If compilation of hydra-ssh2 fails, you are not using v0.11. Download from http://www.0xbadc0de.be/" hydra-ssh2.c:12:27: error: libssh/libssh.h: No such file or directory hydra-ssh2.c: In function 'start_ssh2': hydra-ssh2.c:24: error: 'SSH_SESSION' undeclared (first use in this function) hydra-ssh2.c:24: error: (Each undeclared identifier is reported only once hydra-ssh2.c:24: error: for each function it appears in.) hydra-ssh2.c:24: error: 'ssh_session' undeclared (first use in this function) hydra-ssh2.c:25: error: 'SSH_OPTIONS' undeclared (first use in this function) hydra-ssh2.c:25: error: 'ssh_opt' undeclared (first use in this function) hydra-ssh2.c:34: warning: implicit declaration of function 'options_new' hydra-ssh2.c:44: warning: implicit declaration of function 'options_set_wanted_method' hydra-ssh2.c:44: error: 'KEX_COMP_C_S' undeclared (first use in this function) hydra-ssh2.c:45: error: 'KEX_COMP_S_C' undeclared (first use in this function) hydra-ssh2.c:46: warning: implicit declaration of function 'options_set_port' hydra-ssh2.c:47: warning: implicit declaration of function 'options_set_host' hydra-ssh2.c:48: warning: implicit declaration of function 'options_set_username' hydra-ssh2.c:50: warning: implicit declaration of function 'ssh_connect' hydra-ssh2.c:51: warning: implicit declaration of function 'ssh_get_error' hydra-ssh2.c:51: warning: assignment makes pointer from integer without a cast hydra-ssh2.c:53: warning: passing argument 2 of 'strncmp' makes pointer from integer without a cast hydra-ssh2.c:66: warning: implicit declaration of function 'ssh_userauth_kbdint' hydra-ssh2.c:67: error: 'SSH_AUTH_INFO' undeclared (first use in this function) hydra-ssh2.c:68: warning: implicit declaration of function 'ssh_userauth_kbdint_setanswer' hydra-ssh2.c:73: error: 'SSH_AUTH_SUCCESS' undeclared (first use in this function) hydra-ssh2.c:73: warning: implicit declaration of function 'ssh_userauth_password' hydra-ssh2.c:74: warning: implicit declaration of function 'ssh_disconnect' hydra-ssh2.c:82: warning: implicit declaration of function 'ssh_error_code' make: *** [hydra-ssh2.o] Error 1 Warning: the following items did not execute (for hydra): org.macports.activate org.macports.build org.macports.destroot org.macports.archive org.macports.install Error: Status 1 encountered during processing. ============================CUT====================================== what I'm doing wrong now? joerg From ryandesign at macports.org Wed Jun 4 13:08:38 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 4 Jun 2008 15:08:38 -0500 Subject: compilation of `hydra' failed In-Reply-To: <20080604150614.GB18268@marco.fz-rossendorf.de> References: <20080603131008.GB15569@marco.fz-rossendorf.de> <20080603192439.GH380@claude.fz-rossendorf.de> <20080604092421.GA7623@marco.fz-rossendorf.de> <6A3CFA10-985F-436A-8494-82A363A5D081@macports.org> <20080604150614.GB18268@marco.fz-rossendorf.de> Message-ID: <8D7BAF80-8166-4673-BC3F-2D09EE005B05@macports.org> On Jun 4, 2008, at 10:06, Joerg van den Hoff wrote: > I'm back to field one: due to your above news, I just did: > > port clean --all libssh > port uninstall hydra #this was the old (working) version > without ssh support > port clean --all hydra > port selfupdate > port sync > port install hydra > > which crashed again: > ============================CUT====================================== > ---> Building hydra with target all [snip] > /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ssh2.c -DLIBOPENSSL - > DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include > hydra-ssh2.c:10:2: warning: #warning "If compilation of hydra-ssh2 > fails, you are not using v0.11. Download from http://www. > 0xbadc0de.be/" > hydra-ssh2.c:12:27: error: libssh/libssh.h: No such file or directory [snip] > Did the port libssh01 get installed? It would provide libssh/libssh.h in /opt/local/include/libssh01. From mp at dpj.sent.com Wed Jun 4 17:03:55 2008 From: mp at dpj.sent.com (Daniel Horwood) Date: Thu, 5 Jun 2008 08:03:55 +0800 Subject: Suggested port command enhancement? In-Reply-To: <4845EA62.9010002@macports.org> References: <7fccb3000806030430ke5424d5xcbe4ebef164cc70@mail.gmail.com> <3B2FEE32-D9C8-46A7-B55A-1484709F1271@macports.org> <4845EA62.9010002@macports.org> Message-ID: <51747F4D-E49B-4EA3-9132-0FD696518C19@dpj.sent.com> On 04/06/2008, at 9:05 AM, Rainer M?ller wrote: > Already possible: > $ sudo port mirror installed > $ sudo portmirror On 10.5.3 with macports 1.6, $ sudo pormirror outputs: can't read "0": no such variable while executing "exec /usr/bin/tclsh "$0" "$@"" (file "/opt/local/bin/portmirror" line 3) Am I missing something? Also, are 'port mirror' or 'portmirror' documented anywhere? Dan From ryandesign at macports.org Wed Jun 4 22:22:10 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 5 Jun 2008 00:22:10 -0500 Subject: Port path problem [was Re: Several errors building gnutls] In-Reply-To: <20080605051005.GA95793@camus.local> References: <1214C752-793E-4517-841B-234DFA46C73F@macports.org> <20080605051005.GA95793@camus.local> Message-ID: <65997C5F-9A83-486A-87F4-A23F493652E3@macports.org> On Jun 5, 2008, at 00:10, Brian Flaherty wrote: > On Thu, May 29, 2008 at 10:18:30PM -0500, Ryan Schmidt wrote: > >> On May 17, 2008, at 14:27, Brian P. Flaherty wrote: >> >>> On Wed, 14 May 2008, Chris Pickel wrote: >>> >>>> If you're concerned about your MacPorts installation, the best >>>> thing to >>>> do >>>> would be to remove the configure args you added, then `sudo port -f >>>> configure >>>> libgcrypt`, and find config.log in `sudo port dir libgcrypt`/ >>>> work. That >>>> might >>>> have some info. >>> >>> Thank you for the suggestion. I just had a similar problem with >>> mc being >>> unable to find pkg-config. I ran sudo port -f configure as >>> suggested >>> above and it shows this as the path: >>> >>> PATH: ${prefix}/bin >>> PATH: ${prefix}/sbin >>> PATH: /bin >>> PATH: /sbin >>> PATH: /usr/bin >>> PATH: /usr/sbin >>> PATH: /usr/X11R6/bin >>> PATH: /usr/texbin >> >> I didn't quite understand... what command causes these paths to be >> printed >> out like this? > > I'm sorry for the ambiguity. The list of PATHs above is from > config.log, as Chris Pickel suggested I look at. > > The problem is in my MacPorts installation on my laptop. I had a > similar problem occur today when I tried to install wyrd via port on > my laptop. Note, that it installed fine on my Mac Pro. > > Wyrd depends on ocaml, which was installed via port. > > camus:wyrd-1.4.4 bxf4$ which ocamlc > /opt/local/bin/ocamlc > > But, when I try to install wyrd via port, configure cannot find > ocamlc. > > camus:wyrd-1.4.4 bxf4$ sudo port install wyrd---> Configuring wyrd > 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_textp > roc_wyrd/work/wyrd-1.4.4" && ./configure --prefix=/opt/local -- > mandir=/opt/local/share/man " returned error 1 > Command output: checking for ocamlc... no > configure: error: Cannot find ocamlc. > > > When I go to the wyrd work directory (below): > > camus:wyrd-1.4.4 bxf4$ port dir wyrd > /opt/local/var/macports/sources/rsync.macports.org/release/ports/ > textproc/wyrd > > and run configure by hand, it works fine. > > I save the config.logs from both the port configure and my running > configure by hand. Here's the difference in paths: > > part of config.log following sudo port configure wyrd > > PATH: ${prefix}/bin > PATH: ${prefix}/sbin > PATH: /bin > PATH: /sbin > PATH: /usr/bin > PATH: /usr/sbin > PATH: /usr/X11R6/bin > PATH: /usr/texbin > > part of config.log following my running sudo ./configure (with the > proper arguments) in the wyrd macports work directory: > > PATH: /Users/bxf4/bin > PATH: /opt/local/bin > PATH: /opt/local/sbin > PATH: /usr/X11/bin > PATH: /bin > PATH: /sbin > PATH: /usr/bin > PATH: /usr/sbin > PATH: /usr/local/bin > PATH: /usr/texbin > > When I run configure myself, it appears to inherit my user path. But > when I try to configure/install it with port, configure isn't getting > the /opt/local segment. > > I have no idea why this might be. Any thoughts or suggestions will be > appreciated. I'd rather not remove it all and restart my macports > tree. I've got a fair number of packages installed. Thank you for > your time. Now I understood! Thanks. Have you set binpath to something (possibly including "${prefix}/bin" and "${prefix}/sbin") in /opt/local/etc/macports/macports.conf on the laptop where it doesn't work? If that's not it, what are the differences between the laptop where it doesn't work an the Mac Pro where it does work? Mac OS X version? Xcode version? MacPorts version? From j.van_den_hoff at fzd.de Thu Jun 5 01:41:54 2008 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Thu, 5 Jun 2008 10:41:54 +0200 Subject: compilation of `hydra' failed In-Reply-To: <8D7BAF80-8166-4673-BC3F-2D09EE005B05@macports.org> References: <20080603131008.GB15569@marco.fz-rossendorf.de> <20080603192439.GH380@claude.fz-rossendorf.de> <20080604092421.GA7623@marco.fz-rossendorf.de> <6A3CFA10-985F-436A-8494-82A363A5D081@macports.org> <20080604150614.GB18268@marco.fz-rossendorf.de> <8D7BAF80-8166-4673-BC3F-2D09EE005B05@macports.org> Message-ID: <20080605084154.GA29136@marco.fz-rossendorf.de> On Wed, Jun 04, 2008 at 03:08:38PM -0500, Ryan Schmidt wrote: > On Jun 4, 2008, at 10:06, Joerg van den Hoff wrote: > > >I'm back to field one: due to your above news, I just did: > > > >port clean --all libssh > >port uninstall hydra #this was the old (working) version > >without ssh support > >port clean --all hydra > >port selfupdate > >port sync > >port install hydra > > > >which crashed again: > >============================CUT====================================== > >---> Building hydra with target all > [snip] > >/usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ssh2.c -DLIBOPENSSL - > >DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include > >hydra-ssh2.c:10:2: warning: #warning "If compilation of hydra-ssh2 > >fails, you are not using v0.11. Download from http://www. > >0xbadc0de.be/" > >hydra-ssh2.c:12:27: error: libssh/libssh.h: No such file or directory > [snip] > > > > Did the port libssh01 get installed? It would provide libssh/libssh.h > in /opt/local/include/libssh01. > I checked this: no libssh01 in this location. but then I repeated exactly the sequence of commands (history excerpt...): 2 10:32 sudo port -v clean --all libssh 3 10:32 sudo port uninstall hydra 4 10:32 sudo port clean --all hydra 5 10:32 sudo port -v sync 6 10:34 sudo port -v install hydra and now hydra installed just so!? so, sorry for the noise (though I swear the usual oath that I used exactly the same commands yesterday...) and many thanks again for fixing the ssh issue. joerg > From ryandesign at macports.org Thu Jun 5 04:52:57 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 5 Jun 2008 06:52:57 -0500 Subject: compilation of `hydra' failed In-Reply-To: <20080605084154.GA29136@marco.fz-rossendorf.de> References: <20080603131008.GB15569@marco.fz-rossendorf.de> <20080603192439.GH380@claude.fz-rossendorf.de> <20080604092421.GA7623@marco.fz-rossendorf.de> <6A3CFA10-985F-436A-8494-82A363A5D081@macports.org> <20080604150614.GB18268@marco.fz-rossendorf.de> <8D7BAF80-8166-4673-BC3F-2D09EE005B05@macports.org> <20080605084154.GA29136@marco.fz-rossendorf.de> Message-ID: <2702AA28-842D-4345-85CF-3A3B8989E006@macports.org> On Jun 5, 2008, at 03:41, Joerg van den Hoff wrote: > On Wed, Jun 04, 2008 at 03:08:38PM -0500, Ryan Schmidt wrote: > >> On Jun 4, 2008, at 10:06, Joerg van den Hoff wrote: >> >>> I'm back to field one: due to your above news, I just did: >>> >>> port clean --all libssh >>> port uninstall hydra #this was the old (working) version >>> without ssh support >>> port clean --all hydra >>> port selfupdate >>> port sync >>> port install hydra >>> >>> which crashed again: >>> ============================CUT===================================== >>> = >>> ---> Building hydra with target all >> [snip] >>> /usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ssh2.c -DLIBOPENSSL - >>> DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include >>> hydra-ssh2.c:10:2: warning: #warning "If compilation of hydra-ssh2 >>> fails, you are not using v0.11. Download from http://www. >>> 0xbadc0de.be/" >>> hydra-ssh2.c:12:27: error: libssh/libssh.h: No such file or >>> directory >> [snip] >>> >> >> Did the port libssh01 get installed? It would provide libssh/libssh.h >> in /opt/local/include/libssh01. > > I checked this: no libssh01 in this location. but then I repeated > exactly the sequence of commands (history excerpt...): > > 2 10:32 sudo port -v clean --all libssh > 3 10:32 sudo port uninstall hydra > 4 10:32 sudo port clean --all hydra > 5 10:32 sudo port -v sync > 6 10:34 sudo port -v install hydra > > and now hydra installed just so!? > > so, sorry for the noise (though I swear the usual oath that I used > exactly the same commands yesterday...) and many thanks again for > fixing the > ssh issue. I take it libssh01 is installed now? I think the first time you tried to install must have been before libssh01 got added to the PortIndex (which is only regenerated every 12 hours), so when hydra asked for it as a dependency, MacPorts didn't know where to find it, skipped it, and proceeded to try to install hydra anyway, which failed. Now that libssh01 is in the index it can be installed properly. From j.van_den_hoff at fzd.de Thu Jun 5 07:35:19 2008 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Thu, 5 Jun 2008 16:35:19 +0200 Subject: compilation of `hydra' failed In-Reply-To: <2702AA28-842D-4345-85CF-3A3B8989E006@macports.org> References: <20080603131008.GB15569@marco.fz-rossendorf.de> <20080603192439.GH380@claude.fz-rossendorf.de> <20080604092421.GA7623@marco.fz-rossendorf.de> <6A3CFA10-985F-436A-8494-82A363A5D081@macports.org> <20080604150614.GB18268@marco.fz-rossendorf.de> <8D7BAF80-8166-4673-BC3F-2D09EE005B05@macports.org> <20080605084154.GA29136@marco.fz-rossendorf.de> <2702AA28-842D-4345-85CF-3A3B8989E006@macports.org> Message-ID: <20080605143519.GE29136@marco.fz-rossendorf.de> On Thu, Jun 05, 2008 at 06:52:57AM -0500, Ryan Schmidt wrote: > On Jun 5, 2008, at 03:41, Joerg van den Hoff wrote: > > >On Wed, Jun 04, 2008 at 03:08:38PM -0500, Ryan Schmidt wrote: > > > >>On Jun 4, 2008, at 10:06, Joerg van den Hoff wrote: > >> > >>>I'm back to field one: due to your above news, I just did: > >>> > >>>port clean --all libssh > >>>port uninstall hydra #this was the old (working) version > >>>without ssh support > >>>port clean --all hydra > >>>port selfupdate > >>>port sync > >>>port install hydra > >>> > >>>which crashed again: > >>>============================CUT===================================== > >>>= > >>>---> Building hydra with target all > >>[snip] > >>>/usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ssh2.c -DLIBOPENSSL - > >>>DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include > >>>hydra-ssh2.c:10:2: warning: #warning "If compilation of hydra-ssh2 > >>>fails, you are not using v0.11. Download from http://www. > >>>0xbadc0de.be/" > >>>hydra-ssh2.c:12:27: error: libssh/libssh.h: No such file or > >>>directory > >>[snip] > >>> > >> > >>Did the port libssh01 get installed? It would provide libssh/libssh.h > >>in /opt/local/include/libssh01. > > > >I checked this: no libssh01 in this location. but then I repeated > >exactly the sequence of commands (history excerpt...): > > > >2 10:32 sudo port -v clean --all libssh > >3 10:32 sudo port uninstall hydra > >4 10:32 sudo port clean --all hydra > >5 10:32 sudo port -v sync > >6 10:34 sudo port -v install hydra > > > >and now hydra installed just so!? > > > >so, sorry for the noise (though I swear the usual oath that I used > >exactly the same commands yesterday...) and many thanks again for > >fixing the > >ssh issue. > > I take it libssh01 is installed now? right. > > I think the first time you tried to install must have been before > libssh01 got added to the PortIndex (which is only regenerated every > 12 hours), so when hydra asked for it as a dependency, MacPorts > didn't know where to find it, skipped it, and proceeded to try to > install hydra anyway, which failed. Now that libssh01 is in the index > it can be installed properly. > thanks a lot for explaining this issue. it's comforting to learn that the machine is actually still acting "deterministic". I really hate these "no you see it, now you don't" errors :-) joerg From tabithamc at gmail.com Thu Jun 5 07:47:27 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Thu, 5 Jun 2008 04:47:27 -1000 Subject: Suggested port command enhancement? In-Reply-To: <51747F4D-E49B-4EA3-9132-0FD696518C19@dpj.sent.com> References: <7fccb3000806030430ke5424d5xcbe4ebef164cc70@mail.gmail.com> <3B2FEE32-D9C8-46A7-B55A-1484709F1271@macports.org> <4845EA62.9010002@macports.org> <51747F4D-E49B-4EA3-9132-0FD696518C19@dpj.sent.com> Message-ID: <7fccb3000806050747y6921f5bdmf44a45ad5a0a93c5@mail.gmail.com> On 6/4/08, Daniel Horwood wrote: > > > On 04/06/2008, at 9:05 AM, Rainer M?ller wrote: > > > Already possible: > > $ sudo port mirror installed > > $ sudo portmirror > > > > On 10.5.3 with macports 1.6, > $ sudo pormirror > > outputs: > can't read "0": no such variable > while executing > "exec /usr/bin/tclsh "$0" "$@"" > (file "/opt/local/bin/portmirror" line 3) I get the same output on my system. T.M. Am I missing something? Also, are 'port mirror' or 'portmirror' > documented anywhere? > > Dan > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080605/d33a456e/attachment.htm From xkenneth at gmail.com Thu Jun 5 07:57:29 2008 From: xkenneth at gmail.com (Kenneth Miller) Date: Thu, 5 Jun 2008 09:57:29 -0500 Subject: Bus Errors? Python2.4? Python2.5? Message-ID: All, I seem to be getting quite a few "Bus Errors" when using macports compiled python2.4 and python2.5 on 10.5. Does anyone have any idea what's caused this, or if it's a problem for anyone else? Regards, Kenneth Miller From lrivers at gmail.com Thu Jun 5 08:42:27 2008 From: lrivers at gmail.com (Lorin Rivers) Date: Thu, 5 Jun 2008 10:42:27 -0500 Subject: New Howto In-Reply-To: References: Message-ID: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> Awesome! I did not even know about these How To's. You know, it's actually kind of hard to find them, if you don't know about where they are in the first place. I think they deserve more prominence. There should be a link from the documentation area of the main MacPorts site to the HowTo's. On Mon, Jun 2, 2008 at 1:11 PM, Martin Krischik < krischik at users.sourceforge.net> wrote: > Hello, > > just wanted to let you know that I finished a new Howto > > http://trac.macports.org/wiki/howto/SetupDovecot > > It's the first of a 3 part series and I hope finish the other parts > soon. > > Martin > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080605/258d37a4/attachment.htm From clubjuggler at gmail.com Thu Jun 5 08:55:03 2008 From: clubjuggler at gmail.com (Tanner Lovelace) Date: Thu, 5 Jun 2008 11:55:03 -0400 Subject: qt4 missing when installing LyX In-Reply-To: <341D3D1E-0164-4D88-A62E-5CA599B65BFC@qwest.net> References: <341D3D1E-0164-4D88-A62E-5CA599B65BFC@qwest.net> Message-ID: On Sun, May 25, 2008 at 6:24 PM, Jerry wrote: > Hi, > > I'm still having trouble getting LyX installed. The problem seems to > be a missing qt4 library. Just wondering if anyone else is having > this problem. > > Jerry This should work correctly now with the latest version of the qt4-mac port. There were, as I remember, 2 problems here: 1. The qt4-mac pkgconfig files were in ${prefix}/Library/Frameworks/pkgconfig instead of ${prefix}/lib/pkgconfig where pkgconfig was looking for them. 2. The qt4-mac pkgconfig files provided flags to include the qt headers as "flat files" instead of the framework packages. Both of these issues have been resolved with commit r37370. I have successfully tested and the LyX port does correctly compile, install, and run. Cheers, Tanner Lovelace -- Tanner Lovelace http://wtl.wayfarer.org/ (fieldless) In fess two roundels in pale, a billet fesswise and an increscent, all sable. From j.van_den_hoff at fzd.de Thu Jun 5 09:06:31 2008 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Thu, 5 Jun 2008 18:06:31 +0200 Subject: compilation of `hydra' failed In-Reply-To: <20080605143519.GE29136@marco.fz-rossendorf.de> References: <20080603192439.GH380@claude.fz-rossendorf.de> <20080604092421.GA7623@marco.fz-rossendorf.de> <6A3CFA10-985F-436A-8494-82A363A5D081@macports.org> <20080604150614.GB18268@marco.fz-rossendorf.de> <8D7BAF80-8166-4673-BC3F-2D09EE005B05@macports.org> <20080605084154.GA29136@marco.fz-rossendorf.de> <2702AA28-842D-4345-85CF-3A3B8989E006@macports.org> <20080605143519.GE29136@marco.fz-rossendorf.de> Message-ID: <20080605160631.GH29136@marco.fz-rossendorf.de> On Thu, Jun 05, 2008 at 04:35:19PM +0200, Joerg van den Hoff wrote: > On Thu, Jun 05, 2008 at 06:52:57AM -0500, Ryan Schmidt wrote: > > On Jun 5, 2008, at 03:41, Joerg van den Hoff wrote: > > > > >On Wed, Jun 04, 2008 at 03:08:38PM -0500, Ryan Schmidt wrote: > > > > > >>On Jun 4, 2008, at 10:06, Joerg van den Hoff wrote: > > >> > > >>>I'm back to field one: due to your above news, I just did: > > >>> > > >>>port clean --all libssh > > >>>port uninstall hydra #this was the old (working) version > > >>>without ssh support > > >>>port clean --all hydra > > >>>port selfupdate > > >>>port sync > > >>>port install hydra > > >>> > > >>>which crashed again: > > >>>============================CUT===================================== > > >>>= > > >>>---> Building hydra with target all > > >>[snip] > > >>>/usr/bin/gcc-4.0 -I. -Wall -O2 -c hydra-ssh2.c -DLIBOPENSSL - > > >>>DLIBSSH -I/opt/local/include/libssh01 -I/opt/local/include > > >>>hydra-ssh2.c:10:2: warning: #warning "If compilation of hydra-ssh2 > > >>>fails, you are not using v0.11. Download from http://www. > > >>>0xbadc0de.be/" > > >>>hydra-ssh2.c:12:27: error: libssh/libssh.h: No such file or > > >>>directory > > >>[snip] > > >>> > > >> > > >>Did the port libssh01 get installed? It would provide libssh/libssh.h > > >>in /opt/local/include/libssh01. > > > > > >I checked this: no libssh01 in this location. but then I repeated > > >exactly the sequence of commands (history excerpt...): > > > > > >2 10:32 sudo port -v clean --all libssh > > >3 10:32 sudo port uninstall hydra > > >4 10:32 sudo port clean --all hydra > > >5 10:32 sudo port -v sync > > >6 10:34 sudo port -v install hydra > > > > > >and now hydra installed just so!? > > > > > >so, sorry for the noise (though I swear the usual oath that I used > > >exactly the same commands yesterday...) and many thanks again for > > >fixing the > > >ssh issue. > > > > I take it libssh01 is installed now? > > right. > > > > > I think the first time you tried to install must have been before > > libssh01 got added to the PortIndex (which is only regenerated every > > 12 hours), so when hydra asked for it as a dependency, MacPorts > > didn't know where to find it, skipped it, and proceeded to try to > > install hydra anyway, which failed. Now that libssh01 is in the index > > it can be installed properly. > > me again. `hydra' is now installed and running, sort of: when using the `ssh2' protocol hydra apparently runs as it should but terminates (apparently _not_ prematurely, but I'm not sure) with something like: hydra(2814) malloc: *** set a breakpoint in szone_error to debug hydra(2814) malloc: *** error for object 0x401920: incorrect checksum for freed object - object was probably modified after being freed, break at szone_error to debug hydra(2814) malloc: *** set a breakpoint in szone_error to debug hydra(2814) malloc: *** error for object 0x400d70: incorrect checksum for freed object - object was probably modified after being freed, break at szone_error to debug hydra(2814) malloc: *** set a breakpoint in szone_error to debug hydra(2814) malloc: *** error for object 0x400d70: incorrect checksum for freed object - object was probably modified after being freed, break at szone_error to debug hydra(2814) malloc: *** set a breakpoint in szone_error to debug hydra(2814) malloc: *** error for object 0x400d70: incorrect checksum for freed object - object was probably modified after being freed, break at szone_error to debug hydra(2814) malloc: *** set a breakpoint in szone_error to debug hydra(2814) malloc: *** error for object 0x400d70: incorrect checksum for freed object - object was probably modified after being freed, break at szone_error to debug hydra(2814) malloc: *** set a breakpoint in szone_error to debug Hydra (http://www.thc.org) finished at 2008-06-05 18:02:29 has somebody an idea what to make of this? is this specific for the mac port or is this seen otherwise, too? and: does it harm? joerg From raimue at macports.org Thu Jun 5 09:29:00 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Thu, 05 Jun 2008 18:29:00 +0200 Subject: Suggested port command enhancement? In-Reply-To: <51747F4D-E49B-4EA3-9132-0FD696518C19@dpj.sent.com> References: <7fccb3000806030430ke5424d5xcbe4ebef164cc70@mail.gmail.com> <3B2FEE32-D9C8-46A7-B55A-1484709F1271@macports.org> <4845EA62.9010002@macports.org> <51747F4D-E49B-4EA3-9132-0FD696518C19@dpj.sent.com> Message-ID: <4848144C.1080601@macports.org> Daniel Horwood wrote: > On 04/06/2008, at 9:05 AM, Rainer M?ller wrote: > On 10.5.3 with macports 1.6, > $ sudo pormirror > > outputs: > can't read "0": no such variable > while executing > "exec /usr/bin/tclsh "$0" "$@"" > (file "/opt/local/bin/portmirror" line 3) Hm, this looks like the line meant for /bin/sh got executed by Tcl. Yes, a backslash is missing there. I can confirm the issue for 1.6.0. But it was already fixed in trunk and works there. Quick fix for 1.6.0: Replace the first three lines of portmirror with the first three lines from port. Or simply add the missing backslash at the end of the modeline (line 2) in portmirror. > Am I missing something? Also, are 'port mirror' or 'portmirror' > documented anywhere? Don't think so. I found out what they do by reading the source. port mirror downloads the distfiles and stores them in the distfiles map. portmirror iterates over the distfiles and deletes anything that is not in the distfiles map. Rainer From jkh at apple.com Thu Jun 5 12:22:15 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Thu, 5 Jun 2008 12:22:15 -0700 Subject: New Howto In-Reply-To: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> Message-ID: On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: > Awesome! I did not even know about these How To's. > > You know, it's actually kind of hard to find them, if you don't know > about where they are in the first place. I think they deserve more > prominence. There should be a link from the documentation area of > the main MacPorts site to the HowTo's. I'm still of the opinion that we should install mediawiki on the site and turn these "howtos" into full-blown, collaboratively maintained reference pages worthy of wikipedia (but, unlike wikipedia, also free to be relevant only in the context of projects hosted at macosforge). What do other folks think? - Jordan From krischik at users.sourceforge.net Thu Jun 5 12:28:58 2008 From: krischik at users.sourceforge.net (Martin Krischik) Date: Thu, 5 Jun 2008 21:28:58 +0200 Subject: New Howto: Fetchmail Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have finished the 2nd part of the advanced e-mail series: https://trac.macports.org/wiki/howto/SetupFetchmail Enjoy Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iD8DBQFISD56ijwKaHyem9cRAlQPAJ4hkyZgPlMOxDa7wio2y5XuFx1sNgCfXVg5 0i95Kr3IRs1C0vPLRNCk3Co= =oqdo -----END PGP SIGNATURE----- From zavpublic at mac.com Thu Jun 5 12:29:42 2008 From: zavpublic at mac.com (Zav public) Date: Thu, 05 Jun 2008 14:29:42 -0500 Subject: New Howto In-Reply-To: References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> Message-ID: <66CD45D3-066D-4BDB-9FDE-660AE7BEB021@mac.com> Simple pages where you can read what to do and then do them are VERY GOOD. I like simple and straightforwards. Also, how to recover from errors are very good. I plan on having virgin OS X installs set up to make sure these HowTos work from a new install. - Zav On Jun 5, 2008, at 2:22 PM, Jordan K. Hubbard wrote: > > On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: > >> Awesome! I did not even know about these How To's. >> >> You know, it's actually kind of hard to find them, if you don't know >> about where they are in the first place. I think they deserve more >> prominence. There should be a link from the documentation area of >> the main MacPorts site to the HowTo's. > > I'm still of the opinion that we should install mediawiki on the site > and turn these "howtos" into full-blown, collaboratively maintained > reference pages worthy of wikipedia (but, unlike wikipedia, also free > to be relevant only in the context of projects hosted at macosforge). > What do other folks think? > > - Jordan > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From paulbeard at gmail.com Thu Jun 5 12:43:16 2008 From: paulbeard at gmail.com (paul beard) Date: Thu, 5 Jun 2008 12:43:16 -0700 Subject: Suggested port command enhancement? Message-ID: On Thu, Jun 5, 2008 at 12:00 PM, < macports-users-request at lists.macosforge.org> wrote: > Message: 12 > Date: Thu, 05 Jun 2008 18:29:00 +0200 > From: Rainer M?ller > Subject: Re: Suggested port command enhancement? > To: Daniel Horwood > Cc: MacPorts Users > Message-ID: <4848144C.1080601 at macports.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Daniel Horwood wrote: > > On 04/06/2008, at 9:05 AM, Rainer M?ller wrote: > > On 10.5.3 with macports 1.6, > > $ sudo pormirror > > > > outputs: > > can't read "0": no such variable > > while executing > > "exec /usr/bin/tclsh "$0" "$@"" > > (file "/opt/local/bin/portmirror" line 3) > > Hm, this looks like the line meant for /bin/sh got executed by Tcl. Yes, > a backslash is missing there. I can confirm the issue for 1.6.0. But > it was already fixed in trunk and works there. > > Quick fix for 1.6.0: Replace the first three lines of portmirror with > the first three lines from port. Or simply add the missing backslash at > the end of the modeline (line 2) in portmirror. > > > Am I missing something? Also, are 'port mirror' or 'portmirror' > > documented anywhere? > > Don't think so. I found out what they do by reading the source. > > port mirror downloads the distfiles and stores them in the distfiles > map. portmirror iterates over the distfiles and deletes anything that is > not in the distfiles map. > I don't see the difference? [/Users/paul]# head -4 /opt/local/bin/port /opt/local/bin/portmirror ==> /opt/local/bin/port <== #!/bin/sh # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:filetype=tcl:et:sw=4:ts=4:sts=4 \ exec /usr/bin/tclsh "$0" "$@" # port.tcl ==> /opt/local/bin/portmirror <== #!/bin/sh # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:filetype=tcl:et:sw=4:ts=4:sts=4 \ exec /usr/bin/tclsh "$0" "$@" # portmirror.tcl -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080605/17b37c37/attachment.htm From krischik at users.sourceforge.net Thu Jun 5 12:43:49 2008 From: krischik at users.sourceforge.net (Martin Krischik) Date: Thu, 5 Jun 2008 21:43:49 +0200 Subject: New Howto In-Reply-To: References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 05.06.2008 um 21:22 schrieb Jordan K. Hubbard: > > On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: > >> Awesome! I did not even know about these How To's. >> >> You know, it's actually kind of hard to find them, if you don't >> know about where they are in the first place. I think they deserve >> more prominence. There should be a link from the documentation area >> of the main MacPorts site to the HowTo's. > > I'm still of the opinion that we should install mediawiki on the > site and turn these "howtos" into full-blown, collaboratively > maintained reference pages worthy of wikipedia (but, unlike > wikipedia, also free to be relevant only in the context of projects > hosted at macosforge). What do other folks think? > Well I am quite happy with the wiki as it is - anybody can register and edit. No Problem here. Note that fully open Wikis need SPAM protection which can be tricky so the need to register is quite ok for a small Wiki. What we need is an easier to find link off the main page! Regards Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iD8DBQFISEH1ijwKaHyem9cRAvXyAJ0dPqAI/t5i4xSpk7l1MKPPr9J31ACfeJo1 iyiz4lXU59wLU6F+5L1Vp4o= =lG95 -----END PGP SIGNATURE----- From jkh at apple.com Thu Jun 5 13:33:24 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Thu, 5 Jun 2008 13:33:24 -0700 Subject: New Howto In-Reply-To: <66CD45D3-066D-4BDB-9FDE-660AE7BEB021@mac.com> References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> <66CD45D3-066D-4BDB-9FDE-660AE7BEB021@mac.com> Message-ID: <817E93F5-92E7-443F-9342-B00D5C1A1D2C@apple.com> Hmm. I don't disagree with any of your points made as general statements, but are you also saying that you think mediawiki would be an impediment to achieving those goals in some way? - Jordan On Jun 5, 2008, at 12:29 PM, Zav public wrote: > Simple pages where you can read what to do and then do them are VERY > GOOD. > > I like simple and straightforwards. > > Also, how to recover from errors are very good. I plan on having > virgin OS X installs set up to make sure these HowTos work from a > new install. > > - Zav > > On Jun 5, 2008, at 2:22 PM, Jordan K. Hubbard wrote: > >> >> On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: >> >>> Awesome! I did not even know about these How To's. >>> >>> You know, it's actually kind of hard to find them, if you don't know >>> about where they are in the first place. I think they deserve more >>> prominence. There should be a link from the documentation area of >>> the main MacPorts site to the HowTo's. >> >> I'm still of the opinion that we should install mediawiki on the site >> and turn these "howtos" into full-blown, collaboratively maintained >> reference pages worthy of wikipedia (but, unlike wikipedia, also free >> to be relevant only in the context of projects hosted at macosforge). >> What do other folks think? >> >> - Jordan >> >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > From dluke at geeklair.net Thu Jun 5 13:35:28 2008 From: dluke at geeklair.net (Daniel J. Luke) Date: Thu, 5 Jun 2008 16:35:28 -0400 Subject: Suggested port command enhancement? In-Reply-To: References: Message-ID: <8DB2C101-B912-44C4-98BA-03D2F7F53C69@geeklair.net> On Jun 5, 2008, at 3:43 PM, paul beard wrote: > I don't see the difference? There's extra whitespace after the \ in portmirror but not in port. > [/Users/paul]# head -4 /opt/local/bin/port /opt/local/bin/portmirror > ==> /opt/local/bin/port <== > #!/bin/sh > # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; > c-basic-offset: 4 -*- vim:fenc=utf-8:filetype=tcl:et:sw=4:ts=4:sts=4 \ > exec /usr/bin/tclsh "$0" "$@" > # port.tcl > > ==> /opt/local/bin/portmirror <== > #!/bin/sh > # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; > c-basic-offset: 4 -*- vim:fenc=utf-8:filetype=tcl:et:sw=4:ts=4:sts=4 \ > exec /usr/bin/tclsh "$0" "$@" > # portmirror.tcl -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080605/bb27b49d/attachment.sig From paulbeard at gmail.com Thu Jun 5 13:52:48 2008 From: paulbeard at gmail.com (paul beard) Date: Thu, 5 Jun 2008 13:52:48 -0700 Subject: Suggested port command enhancement? In-Reply-To: <8DB2C101-B912-44C4-98BA-03D2F7F53C69@geeklair.net> References: <8DB2C101-B912-44C4-98BA-03D2F7F53C69@geeklair.net> Message-ID: On Thu, Jun 5, 2008 at 1:35 PM, Daniel J. Luke wrote: > On Jun 5, 2008, at 3:43 PM, paul beard wrote: > >> I don't see the difference? >> > > There's extra whitespace after the \ in portmirror but not in port. > OK. So that's solved. But perhaps these is an additional postflight step needed? [/Users/paul]# portmirror The database doesn't exist at while executing "open_database" (file "/opt/local/bin/portmirror" line 91) (root at tichy.paulbeard.org)-(01:51 PM / Thu Jun 05) [/Users/paul]# touch /opt/local/var/macports/distfiles_mirror.db (root at tichy.paulbeard.org)-(01:51 PM / Thu Jun 05) [/Users/paul]# portmirror deleting /opt/local/var/macports/distfiles/aalib/aalib-1.4rc5.tar.gz deleting /opt/local/var/macports/distfiles/apache2/httpd-2.2.8.tar.bz2 deleting /opt/local/var/macports/distfiles/apr/apr-1.2.12.tar.bz2 -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080605/b73111c9/attachment.htm From dluke at geeklair.net Thu Jun 5 14:04:55 2008 From: dluke at geeklair.net (Daniel J. Luke) Date: Thu, 5 Jun 2008 17:04:55 -0400 Subject: Suggested port command enhancement? In-Reply-To: References: <8DB2C101-B912-44C4-98BA-03D2F7F53C69@geeklair.net> Message-ID: <237A5434-7BBE-4183-86AC-14316555FA64@geeklair.net> On Jun 5, 2008, at 4:52 PM, paul beard wrote: > OK. So that's solved. But perhaps these is an additional postflight > step needed? you need to run: port mirror installed first (which will download any missing distfiles for installed ports and set up the distfiles_mirror.db file) > [/Users/paul]# portmirror > The database doesn't exist at distfiles_mirror.db> > while executing > "open_database" > (file "/opt/local/bin/portmirror" line 91) > (root at tichy.paulbeard.org)-(01:51 PM / Thu Jun 05) > [/Users/paul]# touch /opt/local/var/macports/distfiles_mirror.db > (root at tichy.paulbeard.org)-(01:51 PM / Thu Jun 05) > [/Users/paul]# portmirror > deleting /opt/local/var/macports/distfiles/aalib/aalib-1.4rc5.tar.gz > deleting /opt/local/var/macports/distfiles/apache2/httpd-2.2.8.tar.bz2 > deleting /opt/local/var/macports/distfiles/apr/apr-1.2.12.tar.bz2 -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080605/0e32a71d/attachment.sig From raimue at macports.org Thu Jun 5 16:34:55 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Fri, 06 Jun 2008 01:34:55 +0200 Subject: Suggested port command enhancement? In-Reply-To: References: Message-ID: <4848781F.6030700@macports.org> paul beard wrote: > I don't see the difference? > > [/Users/paul]# head -4 /opt/local/bin/port /opt/local/bin/portmirror > ==> /opt/local/bin/port <== > #!/bin/sh > # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; > c-basic-offset: 4 -*- vim:fenc=utf-8:filetype=tcl:et:sw=4:ts=4:sts=4 \ > exec /usr/bin/tclsh "$0" "$@" > # port.tcl > > ==> /opt/local/bin/portmirror <== > #!/bin/sh > # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; > c-basic-offset: 4 -*- vim:fenc=utf-8:filetype=tcl:et:sw=4:ts=4:sts=4 \ > exec /usr/bin/tclsh "$0" "$@" > # portmirror.tcl Sorry, I was unclear, it is not a "missing" backslash. There is a trailing whitespace after the backslash in portmirror. The backslash has to be the last character on the line, otherwise Tcl doesn't see the next line as continuation of the comment. Tcl interprets the backslash as an escape for the space, not for the newline character, so "missing" was really misleading here. It's hard to see the difference when looking at the output of head or cat. Fixed in r37393 for the release_1_6 branch. Hope this is clear now? Rainer From paulbeard at gmail.com Thu Jun 5 16:53:28 2008 From: paulbeard at gmail.com (paul beard) Date: Thu, 5 Jun 2008 16:53:28 -0700 Subject: Suggested port command enhancement? In-Reply-To: <4848781F.6030700@macports.org> References: <4848781F.6030700@macports.org> Message-ID: On Thu, Jun 5, 2008 at 4:34 PM, Rainer M?ller wrote: > > Sorry, I was unclear, it is not a "missing" backslash. There is a trailing > whitespace after the backslash in portmirror. The backslash has to be the > last character on the line, otherwise Tcl doesn't see the next line as > continuation of the comment. > > Tcl interprets the backslash as an escape for the space, not for the > newline character, so "missing" was really misleading here. It's hard to see > the difference when looking at the output of head or cat. > > Fixed in r37393 for the release_1_6 branch. > > Hope this is clear now? > Yup, perfectly. Now if only these changes could be pushed out to a waiting world -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080605/96ce2af1/attachment.htm From raimue at macports.org Thu Jun 5 16:58:08 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Fri, 06 Jun 2008 01:58:08 +0200 Subject: New Howto In-Reply-To: References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> Message-ID: <48487D90.7010209@macports.org> Jordan K. Hubbard wrote: > I'm still of the opinion that we should install mediawiki on the site > and turn these "howtos" into full-blown, collaboratively maintained > reference pages worthy of wikipedia (but, unlike wikipedia, also free > to be relevant only in the context of projects hosted at macosforge). > What do other folks think? We already have spread our website over enough different places. There is macports.org, trac.macports.org and guide.macports.org (and the upcoming MPWA at db.macports.org). It is already hard enough to find the relevant information one is looking for. If we now add yet another new site, this will become even worse. I don't see what a MediaWiki would offer that a Trac Wiki does not. Okay, Trac Wiki has some caveats (like it does not do automatic merging when editing simultaneously). But I don't see a major benefit from switching to MediaWiki. We already opened up the wiki access to anyone who registers, so I think that's collaborative enough. Rainer From jkh at apple.com Thu Jun 5 17:32:40 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Thu, 5 Jun 2008 17:32:40 -0700 Subject: New Howto In-Reply-To: <48487D90.7010209@macports.org> References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> <48487D90.7010209@macports.org> Message-ID: <5D43B242-E0FF-4432-967B-A135AD807FFE@apple.com> On Jun 5, 2008, at 4:58 PM, Rainer M?ller wrote: > We already have spread our website over enough different places. > There is macports.org, trac.macports.org and guide.macports.org (and > the upcoming MPWA at db.macports.org). It is already hard enough to > find the relevant information one is looking for. If we now add yet > another new site, this will become even worse. Rainer, I'm beginning to wonder if you just like to argue. I know, the thought of a german who likes to argue - it's almost impossible to conceive of, isn't it? :-) I was thinking of a somewhat broader problem space than just MacPorts here, given that the notion of writing "howtos" ultimately and logically extends well beyond just the software you choose to add explicitly yourself. There are also other projects on macosforge who would like to see their own howtos on various topics, some of which are essentially meta-topics ("you must know foo before you can understand bar, even though foo is not logically in the domain of what we are doing"). Rather than have multiple people re-write howtos like "The Unix PATH and how it affects you", it would therefore be better to have a group of documentation-centric people who maintain howtos (or mediawiki pages) like that, whether or not they're also members of the macports project (or the ruby project or the webkit project) being essentially irrelevant as long as they can write good docs. There's no rule that says all developers have to be in one and only one project, or that all projects have to force all URLs into a single domain in order for people to find stuff. From my perspective, knowing I can go to http://howto.macosforge.org or http://doc.macosforge.org, or whatever the heck we might decide to call it, and find all the docs that the various projects are publishing seems to make it a lot EASIER to find the information I am looking for rather than the opposite. More to the point, if we feel it's appropriate to have a general documentation project on MacOSForge, we're going to create one regardless of what macports decides to do since we have plenty of meta- topics to cover, including but not limited to general rules of the road for open source collaboration, how to use MacOSForge itself, etc etc. In comparison with that, splintering the docs into different domains and documentation formats seems a lot more confusing to me as well as having the potential to turn away contributors who would like to write end-user tutorials on using popular software but don't actually use macports. What's been done in macports so far represents an excellent start, don't get me wrong, but it's also raising the question as to whether or not it's happening in precisely the right project context and/or using the right tools. In any case, there's little point in arguing about this since the bigger picture goal here is going to evolve independently of any argument you or I might have anyway, so I think both you and I can save our fingerpads this time around. - Jordan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080605/6f015cbe/attachment.htm From ryandesign at macports.org Thu Jun 5 21:26:53 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 5 Jun 2008 23:26:53 -0500 Subject: New Howto In-Reply-To: <5D43B242-E0FF-4432-967B-A135AD807FFE@apple.com> References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> <48487D90.7010209@macports.org> <5D43B242-E0FF-4432-967B-A135AD807FFE@apple.com> Message-ID: <5FAA2470-228A-4193-B005-68A0D9791D32@macports.org> On Jun 5, 2008, at 19:32, Jordan K. Hubbard wrote: > On Jun 5, 2008, at 4:58 PM, Rainer M?ller wrote: > >> We already have spread our website over enough different places. >> There is macports.org, trac.macports.org and guide.macports.org >> (and the upcoming MPWA at db.macports.org). It is already hard >> enough to find the relevant information one is looking for. If we >> now add yet another new site, this will become even worse. > > Rainer, I'm beginning to wonder if you just like to argue. I know, > the thought of a german who likes to argue - it's almost impossible > to conceive of, isn't it? :-) I was going to disagree with you too, Jordan. Then again, I'm German too... Hmm... :-) > I was thinking of a somewhat broader problem space than just > MacPorts here, given that the notion of writing "howtos" ultimately > and logically extends well beyond just the software you choose to > add explicitly yourself. There are also other projects on > macosforge who would like to see their own howtos on various > topics, some of which are essentially meta-topics ("you must know > foo before you can understand bar, even though foo is not logically > in the domain of what we are doing"). Rather than have multiple > people re-write howtos like "The Unix PATH and how it affects you", > it would therefore be better to have a group of documentation- > centric people who maintain howtos (or mediawiki pages) like that, > whether or not they're also members of the macports project (or the > ruby project or the webkit project) being essentially irrelevant as > long as they can write good docs. There's no rule that says all > developers have to be in one and only one project, or that all > projects have to force all URLs into a single domain in order for > people to find stuff. From my perspective, knowing I can go to > http://howto.macosforge.org or http://doc.macosforge.org, or > whatever the heck we might decide to call it, and find all the docs > that the various projects are publishing seems to make it a lot > EASIER to find the information I am looking for rather than the > opposite. > > More to the point, if we feel it's appropriate to have a general > documentation project on MacOSForge, we're going to create one > regardless of what macports decides to do since we have plenty of > meta-topics to cover, including but not limited to general rules of > the road for open source collaboration, how to use MacOSForge > itself, etc etc. In comparison with that, splintering the docs > into different domains and documentation formats seems a lot more > confusing to me as well as having the potential to turn away > contributors who would like to write end-user tutorials on using > popular software but don't actually use macports. What's been > done in macports so far represents an excellent start, don't get me > wrong, but it's also raising the question as to whether or not it's > happening in precisely the right project context and/or using the > right tools. Ah, I didn't understand at all from your original post that you were thinking of a larger scope than MacPorts, so thanks for clarifying that. Still, I like that we have documentation on how to set up the PATH for MacPorts, not just a general document on the PATH that lacks MacPorts specifics. And I like that we're getting how-tos which tell you how to do things with MacPorts that people frequently ask how to do. I think MediaWiki is a fine wiki engine. It's the wiki system I use for myself personally. At the time I set that up, I liked its wiki syntax best. But I think a more important consideration is that we already have a wiki system in Trac. We should not now add another wiki system with a conflicting syntax. If we wanted to switch from Trac wiki to MediaWiki we could discuss that, but converting all existing content could be difficult (though maybe someone's already written an importer; I haven't looked). I'm in fact in favor of separating MacPorts further from Mac OS Forge, not joining it further by creating a consolidated documentation space. For example, I'd like to get the links to the other Mac OS Forge hosted projects off of the MacPorts Trac web pages; IMHO they have no place there. As a MacPorts user, I really don't need to know that Mac OS Forge also hosts Bonjour, BridgeSupport, CalendarServer, etc.; If I want to know that I can go to www.macosforge.org. > In any case, there's little point in arguing about this since the > bigger picture goal here is going to evolve independently of any > argument you or I might have anyway, so I think both you and I can > save our fingerpads this time around. Oh. Right. :-) From ryandesign at macports.org Thu Jun 5 21:54:01 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 5 Jun 2008 23:54:01 -0500 Subject: compilation of `hydra' failed In-Reply-To: <20080605160631.GH29136@marco.fz-rossendorf.de> References: <20080603192439.GH380@claude.fz-rossendorf.de> <20080604092421.GA7623@marco.fz-rossendorf.de> <6A3CFA10-985F-436A-8494-82A363A5D081@macports.org> <20080604150614.GB18268@marco.fz-rossendorf.de> <8D7BAF80-8166-4673-BC3F-2D09EE005B05@macports.org> <20080605084154.GA29136@marco.fz-rossendorf.de> <2702AA28-842D-4345-85CF-3A3B8989E006@macports.org> <20080605143519.GE29136@marco.fz-rossendorf.de> <20080605160631.GH29136@marco.fz-rossendorf.de> Message-ID: <18ACD69C-DE4F-42FB-BB27-021C8C727F49@macports.org> On Jun 5, 2008, at 11:06, Joerg van den Hoff wrote: > `hydra' is now installed and running, sort of: when using the `ssh2' > protocol hydra apparently runs as it should but terminates (apparently > _not_ prematurely, but I'm not sure) with something like: > > hydra(2814) malloc: *** set a breakpoint in szone_error to debug > hydra(2814) malloc: *** error for object 0x401920: incorrect > checksum for freed object - object was probably modified after > being freed, break at szone_error to debug > hydra(2814) malloc: *** set a breakpoint in szone_error to debug > hydra(2814) malloc: *** error for object 0x400d70: incorrect > checksum for freed object - object was probably modified after > being freed, break at szone_error to debug > hydra(2814) malloc: *** set a breakpoint in szone_error to debug > hydra(2814) malloc: *** error for object 0x400d70: incorrect > checksum for freed object - object was probably modified after > being freed, break at szone_error to debug > hydra(2814) malloc: *** set a breakpoint in szone_error to debug > hydra(2814) malloc: *** error for object 0x400d70: incorrect > checksum for freed object - object was probably modified after > being freed, break at szone_error to debug > hydra(2814) malloc: *** set a breakpoint in szone_error to debug > hydra(2814) malloc: *** error for object 0x400d70: incorrect > checksum for freed object - object was probably modified after > being freed, break at szone_error to debug > hydra(2814) malloc: *** set a breakpoint in szone_error to debug > Hydra (http://www.thc.org) finished at 2008-06-05 18:02:29 > > has somebody an idea what to make of this? is this specific for the > mac > port or is this seen otherwise, too? and: does it harm? I'm afraid I'm now out of my element. You may have to ask the Hydra developers for assistance. From tabithamc at gmail.com Fri Jun 6 00:43:02 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Thu, 5 Jun 2008 21:43:02 -1000 Subject: New Howto In-Reply-To: References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> Message-ID: <7fccb3000806060043h20c0290auf4fa17c520987e4a@mail.gmail.com> On 6/5/08, Jordan K. Hubbard wrote: > > > On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: > > > Awesome! I did not even know about these How To's. > > > > You know, it's actually kind of hard to find them, if you don't know > > about where they are in the first place. I think they deserve more > > prominence. There should be a link from the documentation area of > > the main MacPorts site to the HowTo's. > > > I'm still of the opinion that we should install mediawiki on the site > and turn these "howtos" into full-blown, collaboratively maintained > reference pages worthy of wikipedia (but, unlike wikipedia, also free > to be relevant only in the context of projects hosted at macosforge). > What do other folks think? A fantastic idea! And MediaWiki is itself a MacPort. Very cool! Tabitha - Jordan > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080605/0670c513/attachment.htm From tabithamc at gmail.com Fri Jun 6 00:50:32 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Thu, 5 Jun 2008 21:50:32 -1000 Subject: New Howto In-Reply-To: <7fccb3000806060043h20c0290auf4fa17c520987e4a@mail.gmail.com> References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> <7fccb3000806060043h20c0290auf4fa17c520987e4a@mail.gmail.com> Message-ID: <7fccb3000806060050q2ad7fb18n93289540ad608556@mail.gmail.com> On 6/5/08, Tabitha McNerney wrote: > > > > On 6/5/08, Jordan K. Hubbard wrote: >> >> >> On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: >> >> > Awesome! I did not even know about these How To's. >> > >> > You know, it's actually kind of hard to find them, if you don't know >> > about where they are in the first place. I think they deserve more >> > prominence. There should be a link from the documentation area of >> > the main MacPorts site to the HowTo's. >> >> >> I'm still of the opinion that we should install mediawiki on the site >> and turn these "howtos" into full-blown, collaboratively maintained >> reference pages worthy of wikipedia (but, unlike wikipedia, also free >> to be relevant only in the context of projects hosted at macosforge). >> What do other folks think? > > > A fantastic idea! And MediaWiki is itself a MacPort. Very cool! > An update after I read the rest of the thread ... if I recall, MacPorts.org is graciously hosted on servers provided by Apple true? Xserve? MacPro tower? If so, then what about the software -- is it Mac OS X Server or Mac OS X? If OS X Server, is it Leopard? If so, could we then avail of Apple's built-in-to-Leopard-Server Wiki? Just another thought. Thanks, T.M. Tabitha > > > - Jordan >> >> >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080605/4ef31309/attachment.htm From tabithamc at gmail.com Fri Jun 6 02:15:39 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Thu, 5 Jun 2008 23:15:39 -1000 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <484215E5.2020406@macports.org> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> Message-ID: <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> Rainer, et al ... On 5/31/08, Rainer M?ller wrote: [snip] Hmmmmmm.... *taking a deep thought* > Aaaah, port info! > > Use like this: > $ port info --depends_build --depends_lib --depends_run postfix +ldap > > You can also add --line to compress the output to one line only. You can > hide the label in front of the line and error output by using port -q info. > > As variants are also parsed from the @version notation, you can simply call > this as: > $ port -q info --line --depends_build --depends_lib --depends_run \ > postfix @2.4.6_0+ldap+pcre+sasl+tls > > But if you only need the set of variants you have currently installed: > $ port -q info --line --depends_build --depends_lib --depends_run \ > postfix and installed I have recently written a script that runs the commands as you suggested, for a list of all MacPorts I have on my system. My parsing script pretty much expects this type of format resulting from the port command (example for library dependencies): $ port info --depends_lib portname @version_revision > --> depends_lib: [sequence of zero or more: port:dependencyportname] > Here's a real example: $ port info --depends_lib libvorbis > --> depends_lib: port:libogg > In the above example of course we only have one instance of "port:" which is "port:libogg" but of course there could be zero or more than one instance. I wrote my script to expect the format of either zero instances or at least one of: "depends_lib: port:portname" as well has handling the type cases of "depends_build:" and "depends_run:" But, then my script ran into this specific problem: $ port info --depends_lib speex @1.0.5 > --> depends_lib: lib:libogg:libogg > Hmmm ... the repeat of the library dependency libogg looks to be incorrect. Also, the first instance of the libogg dependency is preceded by "lib:" but shouldn't that be "port:" instead? Of course the port command is only reading what it sees, which is correct for it do this logically since the port command probably doesn't check for human authoring errors of Portfiles. I state so because I had a look at the speex Portfile and I found this, excerpted: depends_lib lib:libogg:libogg > Since my script is going to go through about 450 ports looking for their dependencies (library, build, run), I will find the Portfiles that have errors such as speex above and I imagine the best thing to do is file a ticket / bug reporting true? I will of course also change and correct the errors. Does that seem to be the right thing to do or maybe, if I am missing something, I should instead write my script to adapt for a variety of output conditions such as the above? Thanks, T.M. [snip] -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080605/b4ff104c/attachment.htm From jmr at macports.org Fri Jun 6 04:06:27 2008 From: jmr at macports.org (Joshua Root) Date: Fri, 06 Jun 2008 21:06:27 +1000 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> Message-ID: <48491A33.8020400@macports.org> Tabitha McNerney wrote: > But, then my script ran into this specific problem: > > $ port info --depends_lib speex @1.0.5 > > --> > > depends_lib: lib:libogg:libogg > > Hmmm ... the repeat of the library dependency libogg looks to be incorrect. > Also, the first instance of the libogg dependency is preceded by "lib:" but > shouldn't that be "port:" instead? This is not an error, but a different type of dependency. A "port:foo" dependency means "install the port named 'foo'", whereas "lib:foo:bar" means "check if the library 'foo' is present, and if not, install the port named 'bar'". You can also use 'bin' or 'path' instead of 'lib' to make the port installation conditional on the absence of executables and arbitrary files, respectively. This is only mentioned in passing in the guide: . It's documented a little better in the portfile(7) manual. Most of the time dependencies should be of the port: variety, but sometimes it is better/easier to use software that Apple ships with OS X, a common example being X11. You'll see lib:libX11.6:XFree86 in a lot of portfiles. - Josh From rswwalker at hotmail.com Fri Jun 6 06:11:32 2008 From: rswwalker at hotmail.com (Ross Walker) Date: Fri, 06 Jun 2008 09:11:32 -0400 Subject: New Howto In-Reply-To: <5D43B242-E0FF-4432-967B-A135AD807FFE@apple.com> Message-ID: On 6/5/08 8:32 PM, "Jordan K. Hubbard" wrote: > > On Jun 5, 2008, at 4:58 PM, Rainer M?ller wrote: > >> We already have spread our website over enough different places. There is >> macports.org , trac.macports.org >> and guide.macports.org >> (and the upcoming MPWA at db.macports.org >> ). It is already hard enough to find the relevant >> information one is looking for. If we now add yet another new site, this will >> become even worse. > > Rainer, I'm beginning to wonder if you just like to argue. I know, the > thought of a german who likes to argue - it's almost impossible to conceive > of, isn't it? :-) > > I was thinking of a somewhat broader problem space than just MacPorts here, > given that the notion of writing "howtos" ultimately and logically extends > well beyond just the software you choose to add explicitly yourself. There > are also other projects on macosforge who would like to see their own howtos > on various topics, some of which are essentially meta-topics ("you must know > foo before you can understand bar, even though foo is not logically in the > domain of what we are doing"). Rather than have multiple people re-write > howtos like "The Unix PATH and how it affects you", it would therefore be > better to have a group of documentation-centric people who maintain howtos (or > mediawiki pages) like that, whether or not they're also members of the > macports project (or the ruby project or the webkit project) being essentially > irrelevant as long as they can write good docs. There's no rule that says all > developers have to be in one and only one project, or that all projects have > to force all URLs into a single domain in order for people to find stuff. > From my perspective, knowing I can go to http://howto.macosforge.org or > http://doc.macosforge.org, or whatever the heck we might decide to call it, > and find all the docs that the various projects are publishing seems to make > it a lot EASIER to find the information I am looking for rather than the > opposite. > > More to the point, if we feel it's appropriate to have a general documentation > project on MacOSForge, we're going to create one regardless of what macports > decides to do since we have plenty of meta-topics to cover, including but not > limited to general rules of the road for open source collaboration, how to use > MacOSForge itself, etc etc. In comparison with that, splintering the docs > into different domains and documentation formats seems a lot more confusing to > me as well as having the potential to turn away contributors who would like to > write end-user tutorials on using popular software but don't actually use > macports. What's been done in macports so far represents an excellent start, > don't get me wrong, but it's also raising the question as to whether or not > it's happening in precisely the right project context and/or using the right > tools. > > In any case, there's little point in arguing about this since the bigger > picture goal here is going to evolve independently of any argument you or I > might have anyway, so I think both you and I can save our fingerpads this time > around. Jordan, I was pleasantly surprised to see you on the list as I remember you way back from my FreeBSD list days. Anyways I think what needs to happen first is to decide what should be MacOSForge and what should be MacPorts and split the documentation appropriately. Maybe restrict the documentation on MacPorts to just the documentation on how to use MacPorts, how to develop ports for MacPorts and how to troubleshoot repair a broken MacPorts tree and put the appropriate OSS project how-tos under MacOSForge. You can always create out-of-wiki links between the two. It's probably not the most thought out approach but my wife is talking my ear off while I write this... -Ross From tabithamc at gmail.com Fri Jun 6 09:23:15 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Fri, 6 Jun 2008 06:23:15 -1000 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <48491A33.8020400@macports.org> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> <48491A33.8020400@macports.org> Message-ID: <7fccb3000806060923o6795b146s6f3c0138335cff1a@mail.gmail.com> On 6/6/08, Joshua Root wrote: > > Tabitha McNerney wrote: > >> But, then my script ran into this specific problem: >> >> $ port info --depends_lib speex @1.0.5 >> >> --> >> >> depends_lib: lib:libogg:libogg >> >> Hmmm ... the repeat of the library dependency libogg looks to be >> incorrect. >> Also, the first instance of the libogg dependency is preceded by "lib:" >> but >> shouldn't that be "port:" instead? >> > > This is not an error, but a different type of dependency. A "port:foo" > dependency means "install the port named 'foo'", whereas "lib:foo:bar" means > "check if the library 'foo' is present, and if not, install the port named > 'bar'". You can also use 'bin' or 'path' instead of 'lib' to make the port > installation conditional on the absence of executables and arbitrary files, > respectively. > > This is only mentioned in passing in the guide: < > http://guide.macports.org/#reference.dependencies.types>. It's documented > a little better in the portfile(7) manual. > > Most of the time dependencies should be of the port: variety, but sometimes > it is better/easier to use software that Apple ships with OS X, a common > example being X11. You'll see lib:libX11.6:XFree86 in a lot of portfiles. Thanks Josh, for pointing that sliver of documentation out (I should have found it after Rainer shed light on $ port info ... ). - Josh > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080606/2ee59b0f/attachment.htm From ryandesign at macports.org Fri Jun 6 14:20:02 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 6 Jun 2008 16:20:02 -0500 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <48491A33.8020400@macports.org> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> <48491A33.8020400@macports.org> Message-ID: On Jun 6, 2008, at 06:06, Joshua Root wrote: > Tabitha McNerney wrote: > >> But, then my script ran into this specific problem: >> >> $ port info --depends_lib speex @1.0.5 >> >> --> >> >> depends_lib: lib:libogg:libogg >> >> Hmmm ... the repeat of the library dependency libogg looks to be >> incorrect. >> Also, the first instance of the libogg dependency is preceded by >> "lib:" but >> shouldn't that be "port:" instead? > > This is not an error, but a different type of dependency. A "port:foo" > dependency means "install the port named 'foo'", whereas "lib:foo:bar" > means "check if the library 'foo' is present, and if not, install the > port named 'bar'". You can also use 'bin' or 'path' instead of > 'lib' to > make the port installation conditional on the absence of > executables and > arbitrary files, respectively. > > This is only mentioned in passing in the guide: > . It's > documented a little better in the portfile(7) manual. > > Most of the time dependencies should be of the port: variety, but > sometimes it is better/easier to use software that Apple ships with OS > X, a common example being X11. You'll see lib:libX11.6:XFree86 in a > lot > of portfiles. In the case of the speex port, the dependency should be changed to "port:libogg". This port probably dates from a time before MacPorts had "port:"-style dependencies. I changed the dependency for speex in r37416. From paulbeard at gmail.com Fri Jun 6 19:20:37 2008 From: paulbeard at gmail.com (paul beard) Date: Fri, 6 Jun 2008 19:20:37 -0700 Subject: macports-users Digest, Vol 22, Issue 6 In-Reply-To: References: Message-ID: On Fri, Jun 6, 2008 at 12:00 PM, < macports-users-request at lists.macosforge.org> wrote: > > Message: 14 > Date: Thu, 5 Jun 2008 23:26:53 -0500 > From: Ryan Schmidt > Subject: Re: New Howto > To: Jordan K.Hubbard > Cc: MacPorts Users > Message-ID: <5FAA2470-228A-4193-B005-68A0D9791D32 at macports.org> > Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed > > We should not now add another > wiki system with a conflicting syntax. If we wanted to switch from > Trac wiki to MediaWiki we could discuss that, but converting all > existing content could be difficult (though maybe someone's already > written an importer; I haven't looked). Do we have to discuss it? I think discussion is one of the reasons there is no 1.6.x release (or an even more full-featured one). What format are most of the articles in and what flavor is getting the most attention right now? And who decided a format as simple as wiki needed to be forked or otherwise complicated? -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080606/9a9e0faf/attachment.htm From akiabo at googlemail.com Fri Jun 6 22:58:39 2008 From: akiabo at googlemail.com (A. Osthoff) Date: Sat, 07 Jun 2008 07:58:39 +0200 Subject: Problems with Gnucash, Aqbanking since OSX Leopard upgrade Message-ID: <484A238F.2080102@googlemail.com> Hello, I have been using Gnucash with Aqbanking under Tiger for about a year without a problem. Recently, I bought a new iMac und hence had to do a fresh install. Under OSX 10.5.2 I installed Gnucash 2.2.5, aqbanking 2.3.3_0 with the help of Macports 1.6. I am able to configure the Online Banking access via HBCI, yet every time I try to access the account, I get an error message (...) Empfangenes Konto: ?????? / ????? Auftr?ge werden kodiert Auftr?ge werden gesendet Fehler beim Senden (Netzwerk-Fehler) --> Error while Sending (Network Error) Verbindung von Bank trennen Getrennt AqHBCI abgeschlossen. The error is the same across different banks, so I exclude wrong configuration as the cause ... Thanks, Andreas From ryandesign at macports.org Sat Jun 7 00:27:57 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 7 Jun 2008 02:27:57 -0500 Subject: New Howto In-Reply-To: References: Message-ID: On Jun 6, 2008, at 21:20, paul beard wrote: > On Fri, Jun 6, 2008 at 12:00 PM, wrote: > >> We should not now add another >> wiki system with a conflicting syntax. If we wanted to switch from >> Trac wiki to MediaWiki we could discuss that, but converting all >> existing content could be difficult (though maybe someone's already >> written an importer; I haven't looked). > > Do we have to discuss it? I think discussion is one of the reasons > there is no 1.6.x release (or an even more full-featured one). What > format are most of the articles in and what flavor is getting the > most attention right now? And who decided a format as simple as > wiki needed to be forked or otherwise complicated? The MacPorts project is not a dictatorship, it's an open-source collaborative project, and mine is not the only opinion, hence discussion. My opinion is we should not have two wiki systems with different syntax rules. We have enough trouble getting people to follow just the syntax rules for Trac today. (Bugs are constantly filed with wrong syntax.) We should either keep Trac as the only wiki system, or move to MediaWiki as the only wiki system, and convert all existing content to MediaWiki format, and close the Trac wiki. The former option is less work so I vote for that, since I haven't seen any outcry against the Trac wiki. From mp at dpj.sent.com Sat Jun 7 01:32:07 2008 From: mp at dpj.sent.com (Daniel Horwood) Date: Sat, 7 Jun 2008 16:32:07 +0800 Subject: Problems with Gnucash, Aqbanking since OSX Leopard upgrade In-Reply-To: <484A238F.2080102@googlemail.com> References: <484A238F.2080102@googlemail.com> Message-ID: <3EFE58F9-EE83-413E-B315-D86C0AD37571@dpj.sent.com> On 07/06/2008, at 1:58 PM, A. Osthoff wrote: > Hello, > > I have been using Gnucash with Aqbanking under Tiger for about a year > without a problem. Recently, I bought a new iMac und hence had to do a > fresh install. > Under OSX 10.5.2 I installed Gnucash 2.2.5, aqbanking 2.3.3_0 with the > help of Macports 1.6. > I am able to configure the Online Banking access via HBCI, yet every > time I try to access the account, I get an error message > > (...) > Empfangenes Konto: ?????? / ????? > Auftr?ge werden kodiert > Auftr?ge werden gesendet > Fehler beim Senden (Netzwerk-Fehler) --> Error while Sending > (Network Error) > > Verbindung von Bank trennen > Getrennt > AqHBCI abgeschlossen. > > The error is the same across different banks, so I exclude wrong > configuration as the cause ... > > Thanks, > Andreas > Hi Andreas, I think this is an issue with aqbanking or gwenhywfar. Googling 'aqbanking "network error"' returns a few promising links in German (which I don't speak). Also, the gnucash wiki - http://wiki.gnucash.org/wiki/AqBanking - states that this is a known problem on windows and provides a link to a possible patch, which you could try. Unfortunately I can't test it because none of my banks support any kind of connection :-( Dan From randall.h.wood at alexandriasoftware.com Sat Jun 7 01:52:11 2008 From: randall.h.wood at alexandriasoftware.com (Randall Wood) Date: Sat, 7 Jun 2008 04:52:11 -0400 Subject: Fwd: Google Search for Macports In-Reply-To: References: Message-ID: This is a link to a google search I created for possible use in MacPorts sites. Use it your own risk. ---------- Forwarded message ---------- From: Randall Wood Date: Sun, May 18, 2008 at 7:14 AM Subject: Google Search for Macports To: PortMgr ALCON: I created a Google Custom Search for Macports at http://www.google.com/coop/cse?cx=011837386708472035020:5lqtx6zp3qw Its open to others to volunteer to maintain it, so multiple users can maintain it. There is one problem with embedding this search in our site: Since we are not a legal non-profit organization, we would need to allow Google to place ads in the search results. In any event, I hope this is useful in helping get a unified search for MacPorts. -- Randall Wood randall.h.wood at alexandriasoftware.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." -- Randall Wood randall.h.wood at alexandriasoftware.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." From face at CentosPrime.COM Sat Jun 7 06:01:07 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sat, 07 Jun 2008 06:01:07 -0700 Subject: Errors upgrading ImageMagick Message-ID: running from trunk. rebuilt and updated this morning. sudo port upgrade outdated ... tiff upgraded OK... Portfile changed since last build; discarding previous state. ---> Fetching ImageMagick ---> Attempting to fetch ImageMagick-6.4.1-5.tar.bz2 from http://downloads.sourceforge.net/imagemagick ---> Verifying checksum(s) for ImageMagick Error: Checksum (md5) mismatch for ImageMagick-6.4.1-5.tar.bz2 Error: Checksum (sha1) mismatch for ImageMagick-6.4.1-5.tar.bz2 Error: Checksum (rmd160) mismatch for ImageMagick-6.4.1-5.tar.bz2 Error: Target org.macports.checksum returned: Unable to verify file checksums Error: Unable to upgrade port: 1 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From dbreiser at gmail.com Sat Jun 7 10:16:32 2008 From: dbreiser at gmail.com (David Reiser) Date: Sat, 7 Jun 2008 13:16:32 -0400 Subject: Problems with Gnucash, Aqbanking since OSX Leopard upgrade In-Reply-To: <484A238F.2080102@googlemail.com> References: <484A238F.2080102@googlemail.com> Message-ID: <54566123-38C8-405E-98FA-DAEE345FB44A@gmail.com> On Jun 7, 2008, at 1:58 AM, A. Osthoff wrote: > Hello, > > I have been using Gnucash with Aqbanking under Tiger for about a year > without a problem. Recently, I bought a new iMac und hence had to do a > fresh install. > Under OSX 10.5.2 I installed Gnucash 2.2.5, aqbanking 2.3.3_0 with the > help of Macports 1.6. > I am able to configure the Online Banking access via HBCI, yet every > time I try to access the account, I get an error message > > (...) > Empfangenes Konto: ?????? / ????? > Auftr?ge werden kodiert > Auftr?ge werden gesendet > Fehler beim Senden (Netzwerk-Fehler) --> Error while Sending > (Network Error) > > Verbindung von Bank trennen > Getrennt > AqHBCI abgeschlossen. > > The error is the same across different banks, so I exclude wrong > configuration as the cause ... > > Thanks, > Andreas If the Macports available ports list is accurate, you may want to try requesting or creating an updated port for gwenhywfar. The port list says it is at 2.5.3. The last released version for gwenhywfar before the version 3 series (started with 2.9.x) is 2.6.2. Since I pushed gwenhywfar in fink from 2.4.? to 2.6.2 just after Leopard came out, I suspect there were some changes in there required when OS X 10.5 came out. Gwenhywfar handles all the network activity for aqbanking. Gnucash is not yet able to use aqbanking/gwenhywfar 3.x. I don't think the other suggestion of using the proposed patch for the windows version will work. Using a sleep command in gwenhywfar to enable some connections was initiated for the mac version in gwen 2.2.0. The real fix for this problem was committed upstream just after 2.6.2 was released, so it isn't available in any 2.x series tarball. However, 2.6.2 with the sleep fix works well for me for OFXDirectConnect sessions. I don't have any other type of bank connections I can test. Dave -- David Reiser dbreiser at gmail.com From ryandesign at macports.org Sat Jun 7 22:12:02 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 8 Jun 2008 00:12:02 -0500 Subject: Errors upgrading ImageMagick In-Reply-To: References: Message-ID: <4562859B-C625-4F45-A9D8-D8AB8345D218@macports.org> On Jun 7, 2008, at 08:01, Chris Janton wrote: > running from trunk. rebuilt and updated this morning. > > sudo port upgrade outdated > ... tiff upgraded OK... > > Portfile changed since last build; discarding previous state. > ---> Fetching ImageMagick > ---> Attempting to fetch ImageMagick-6.4.1-5.tar.bz2 from http:// > downloads.sourceforge.net/imagemagick > ---> Verifying checksum(s) for ImageMagick > Error: Checksum (md5) mismatch for ImageMagick-6.4.1-5.tar.bz2 > Error: Checksum (sha1) mismatch for ImageMagick-6.4.1-5.tar.bz2 > Error: Checksum (rmd160) mismatch for ImageMagick-6.4.1-5.tar.bz2 > Error: Target org.macports.checksum returned: Unable to verify file > checksums > Error: Unable to upgrade port: 1 http://trac.macports.org/ticket/15341 From jschnide at umn.edu Sun Jun 8 03:46:00 2008 From: jschnide at umn.edu (Joe Schnide) Date: Sun, 8 Jun 2008 05:46:00 -0500 Subject: Deluge install issue Message-ID: Hello, I had no problem installing deluge on a MacBookPro but am having a problem on an Intel iMac. schnide-iMac:~ root# port -d install deluge DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/net/deluge DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/net/deluge DEBUG: Requested variant darwin is not provided by port deluge. DEBUG: Requested variant i386 is not provided by port deluge. DEBUG: Requested variant macosx is not provided by port deluge. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/python25 DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/python25 DEBUG: Requested variant darwin is not provided by port python25. DEBUG: Requested variant i386 is not provided by port python25. DEBUG: Requested variant macosx is not provided by port python25. DEBUG: Executing variant darwin_9 provides darwin_9 DEBUG: Searching for dependency: python25 DEBUG: Found Dependency: receipt exists for python25 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/dbus-python25 DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/dbus-python25 DEBUG: Requested variant darwin is not provided by port dbus-python25. DEBUG: Requested variant i386 is not provided by port dbus-python25. DEBUG: Requested variant macosx is not provided by port dbus-python25. DEBUG: Executing variant darwin_9 provides darwin_9 DEBUG: Searching for dependency: dbus-python25 DEBUG: Found Dependency: receipt exists for dbus-python25 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: Found Dependency: receipt exists for gettext DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/librsvg DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/librsvg DEBUG: Requested variant darwin is not provided by port librsvg. DEBUG: Requested variant i386 is not provided by port librsvg. DEBUG: Requested variant macosx is not provided by port librsvg. DEBUG: Searching for dependency: librsvg DEBUG: Found Dependency: receipt exists for librsvg DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/python/py25-gtk DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/python/py25-gtk DEBUG: Requested variant darwin is not provided by port py25-gtk. DEBUG: Requested variant i386 is not provided by port py25-gtk. DEBUG: Requested variant macosx is not provided by port py25-gtk. DEBUG: Executing variant darwin_9 provides darwin_9 DEBUG: Searching for dependency: py25-gtk DEBUG: Found Dependency: receipt exists for py25-gtk DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/python/py25-hashlib DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/python/py25-hashlib DEBUG: Requested variant darwin is not provided by port py25-hashlib. DEBUG: Requested variant i386 is not provided by port py25-hashlib. DEBUG: Requested variant macosx is not provided by port py25-hashlib. DEBUG: Searching for dependency: py25-hashlib DEBUG: Found Dependency: receipt exists for py25-hashlib DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/python/py25-xdg DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/python/py25-xdg DEBUG: Requested variant darwin is not provided by port py25-xdg. DEBUG: Requested variant i386 is not provided by port py25-xdg. DEBUG: Requested variant macosx is not provided by port py25-xdg. DEBUG: Searching for dependency: py25-xdg DEBUG: Found Dependency: receipt exists for py25-xdg DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/python/py25-zlib DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/python/py25-zlib DEBUG: Requested variant darwin is not provided by port py25-zlib. DEBUG: Requested variant i386 is not provided by port py25-zlib. DEBUG: Requested variant macosx is not provided by port py25-zlib. DEBUG: Searching for dependency: py25-zlib DEBUG: Found Dependency: receipt exists for py25-zlib DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/boost DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/boost DEBUG: Requested variant i386 is not provided by port boost. DEBUG: Requested variant macosx is not provided by port boost. DEBUG: Executing variant darwin_9 provides darwin_9 DEBUG: Executing variant darwin provides darwin DEBUG: Searching for dependency: boost DEBUG: Found Dependency: receipt exists for boost DEBUG: Skipping completed org.macports.main (deluge) DEBUG: Skipping completed org.macports.fetch (deluge) DEBUG: Skipping completed org.macports.checksum (deluge) DEBUG: Skipping completed org.macports.extract (deluge) DEBUG: Skipping completed org.macports.patch (deluge) DEBUG: Skipping completed org.macports.configure (deluge) ---> Building deluge with target build DEBUG: Executing org.macports.build (deluge) DEBUG: Environment: CFLAGS='-I/opt/local/include -I/opt/local/include/boost' PYTHON_CFLAGS='-I/opt/local/include -I/opt/local/include/boost' PYTHON_LDFLAGS='-L/opt/local/lib' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_deluge/work/deluge-torrent-0.5.8.9" && /opt/local/bin/python2.5 setup.py build' Attempting to detect your system information 32bit x86 system detected Darwin / OS X system detected running build running build_py running build_ext building 'deluge_core' extension /usr/bin/gcc-4.0 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/opt/local/include -I/opt/local/include/boost -I./libtorrent -I./libtorrent/include -I./libtorrent/include/libtorrent -I/usr/include/python2.5 -I/opt/local/include/python2.5 -c libtorrent/src/alert.cpp -o build/temp.macosx-10.3-i386-2.5/libtorrent/src/alert.o -Wno-missing-braces -DHAVE_INCLUDE_LIBTORRENT_ASIO____ASIO_HPP=1 -DHAVE_INCLUDE_LIBTORRENT_ASIO_SSL_STREAM_HPP=1 -DHAVE_INCLUDE_LIBTORRENT_ASIO_IP_TCP_HPP=1 -DHAVE_PTHREAD=1 -DTORRENT_USE_OPENSSL=1 -DHAVE_SSL=1 -DNDEBUG=1 -O2 cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++ ./libtorrent/include/libtorrent/time.hpp:157: error: 'time_traits' is not a template ./libtorrent/include/libtorrent/time.hpp:158: error: explicit specialization of non-template 'asio::time_traits' error: command '/usr/bin/gcc-4.0' failed with exit status 1 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_deluge/work/deluge-torrent-0.5.8.9" && /opt/local/bin/python2.5 setup.py build " returned error 1 Command output: Attempting to detect your system information 32bit x86 system detected Darwin / OS X system detected running build running build_py running build_ext building 'deluge_core' extension /usr/bin/gcc-4.0 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/opt/local/include -I/opt/local/include/boost -I./libtorrent -I./libtorrent/include -I./libtorrent/include/libtorrent -I/usr/include/python2.5 -I/opt/local/include/python2.5 -c libtorrent/src/alert.cpp -o build/temp.macosx-10.3-i386-2.5/libtorrent/src/alert.o -Wno-missing-braces -DHAVE_INCLUDE_LIBTORRENT_ASIO____ASIO_HPP=1 -DHAVE_INCLUDE_LIBTORRENT_ASIO_SSL_STREAM_HPP=1 -DHAVE_INCLUDE_LIBTORRENT_ASIO_IP_TCP_HPP=1 -DHAVE_PTHREAD=1 -DTORRENT_USE_OPENSSL=1 -DHAVE_SSL=1 -DNDEBUG=1 -O2 cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++ ./libtorrent/include/libtorrent/time.hpp:157: error: 'time_traits' is not a template ./libtorrent/include/libtorrent/time.hpp:158: error: explicit specialization of non-template 'asio::time_traits' error: command '/usr/bin/gcc-4.0' failed with exit status 1 Warning: the following items did not execute (for deluge): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. schnide-iMac:~ root# Any ideas on what the problem is here? Please let me know if I can provide further information. Thanks Joe -- ------- jschnide at umn.edu From tabithamc at gmail.com Sun Jun 8 03:50:01 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun, 8 Jun 2008 00:50:01 -1000 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <48491A33.8020400@macports.org> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> <48491A33.8020400@macports.org> Message-ID: <7fccb3000806080350k2cc794e6s3fb74210ab779b1a@mail.gmail.com> On 6/6/08, Joshua Root wrote: > > Tabitha McNerney wrote: > >> But, then my script ran into this specific problem: >> >> $ port info --depends_lib speex @1.0.5 >> >> --> >> >> depends_lib: lib:libogg:libogg >> >> Hmmm ... the repeat of the library dependency libogg looks to be >> incorrect. >> Also, the first instance of the libogg dependency is preceded by "lib:" >> but >> shouldn't that be "port:" instead? >> > > This is not an error, but a different type of dependency. A "port:foo" > dependency means "install the port named 'foo'", whereas "lib:foo:bar" means > "check if the library 'foo' is present, and if not, install the port named > 'bar'". You can also use 'bin' or 'path' instead of 'lib' to make the port > installation conditional on the absence of executables and arbitrary files, > respectively. Hi, I have a followup question. I noticed that with the subversion port, when I get information from it (along with enabling its variant, the perl variant), for the lib_depends output, I get: $ port info --depends_lib postgresql81 @8.1.11 +perl > --> depends_lib: port:readline, port:openssl, port:zlib, bin:perl:perl5.8 > So if I follow Josh's logic, what this means is that there is a library dependency of a non-port type that has an executable condition which is saying, in a paraphrase: "the port installation of subversion plus its perl variant has library MacPort dependencies of readline, openssl and zlib' and it has a non-MacPort dependency baed on the perl binary executable. If this perl executable is available on the operating system (e.g., Mac OS X) then use it, but if this perl executable can not be found, then the MacPort perl5.8 should be installed and once its installed its binary executable shall be used" ?? Is it not unusual to see binary executable types of non-port dependencies in the library (depends_lib) definition of a port? It doesn't matter if binary requirements are in fact mixed and matched (regardless of dependency type, library, build, run)? Thanks, T.M. This is only mentioned in passing in the guide: < > http://guide.macports.org/#reference.dependencies.types>. It's documented > a little better in the portfile(7) manual. > > Most of the time dependencies should be of the port: variety, but sometimes > it is better/easier to use software that Apple ships with OS X, a common > example being X11. You'll see lib:libX11.6:XFree86 in a lot of portfiles. > > - Josh > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080608/0cbef641/attachment.htm From jschnide at umn.edu Sun Jun 8 03:53:35 2008 From: jschnide at umn.edu (Joe Schnide) Date: Sun, 8 Jun 2008 05:53:35 -0500 Subject: Request process for ports Message-ID: Hello, I'm not sure of what the process is for requesting ports. If there is an officail process, please provide a pointer to the document detailing the process. The ports I'd like to request are: bwctl command line client application and a scheduling and policy daemon that wraps Iperf http://e2epi.internet2.edu/bwctl/ mturoute check the mtu values between you and a host http://www.elifulkerson.com/projects/mturoute.php npad Pathdiag http://www.psc.edu/networking/projects/pathdiag/ OWAMP command line client application and a policy daemon used to determine one way latencies between hosts http://e2epi.internet2.edu/owamp/ thrulay is used to measure the capacity of a network by sending a bulk TCP stream over it Like other tools (such as iperf, netperf, nettest, nuttcp, ttcp, etc.), thrulay can report TCP throughput periodically so that TCP performance plots can be produced. Unlike other tools, thrulay not only reports goodput, but round-trip delay time as well. The output of thrulay is easy to parse by machine (in fact, it's ready to be used as a data file for gnuplot). http://sourceforge.net/projects/thrulay/ http://e2epi.internet2.edu/thrulay/ dhcptool http://freshmeat.net/projects/dhcptool/ openlldp http://openlldp.sourceforge.net/ Please let me know if I can provide further information. Thanks Joe -- ------- jschnide at umn.edu From ryandesign at macports.org Sun Jun 8 04:01:36 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 8 Jun 2008 06:01:36 -0500 Subject: Request process for ports In-Reply-To: References: Message-ID: <8D8A66F4-77FF-4D6A-89D0-1F6AF0629B97@macports.org> On Jun 8, 2008, at 05:53, Joe Schnide wrote: > I'm not sure of what the process is for requesting ports. If there is > an officail process, please provide a pointer to the document > detailing > the process. The best thing to do is file a ticket in our issue tracker for each port. Set the Type to "enhancement" and the Milestone to "Port Requests". Here are instructions for filing tickets: http://guide.macports.org/#project The best way to get ports added is to write them yourself. Instructions for writing portfiles are in the guide too: http://guide.macports.org/ You can also learn how to write portfiles by reading the existing portfiles. > The ports I'd like to request are: > > bwctl > command line client application and a scheduling and policy daemon > that > wraps Iperf > http://e2epi.internet2.edu/bwctl/ > > mturoute > check the mtu values between you and a host > http://www.elifulkerson.com/projects/mturoute.php > > npad Pathdiag > http://www.psc.edu/networking/projects/pathdiag/ > > OWAMP > command line client application and a policy daemon used to > determine one > way latencies between hosts > http://e2epi.internet2.edu/owamp/ > > thrulay is used to measure the capacity of a network by sending a > bulk TCP stream over it > Like other tools (such as iperf, netperf, nettest, nuttcp, ttcp, > etc.), > thrulay can report TCP throughput periodically so that TCP > performance > plots can be produced. Unlike other tools, thrulay not only reports > goodput, but round-trip delay time as well. The output of thrulay > is easy to parse by machine (in fact, it's ready to be used as a data > file for gnuplot). > http://sourceforge.net/projects/thrulay/ > http://e2epi.internet2.edu/thrulay/ > > dhcptool > http://freshmeat.net/projects/dhcptool/ > > openlldp > http://openlldp.sourceforge.net/ > > Please let me know if I can provide further information. From ryandesign at macports.org Sun Jun 8 04:04:22 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 8 Jun 2008 06:04:22 -0500 Subject: Deluge install issue In-Reply-To: References: Message-ID: <66174D40-2CA1-4C12-BBEA-4854D4CF9827@macports.org> On Jun 8, 2008, at 05:46, Joe Schnide wrote: > I had no problem installing deluge on a MacBookPro but am having a > problem on > an Intel iMac. What is the difference between the MacBook Pro and the iMac? They're both Intel... Are the both running the same version of Mac OS X, Xcode, and MacPorts? What versions? Is your ports tree up to date? (Use "sudo port selfupdate" to update.) Are the same versions of all dependencies installed? From ryandesign at macports.org Sun Jun 8 04:30:16 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 8 Jun 2008 06:30:16 -0500 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <7fccb3000806080350k2cc794e6s3fb74210ab779b1a@mail.gmail.com> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> <48491A33.8020400@macports.org> <7fccb3000806080350k2cc794e6s3fb74210ab779b1a@mail.gmail.com> Message-ID: On Jun 8, 2008, at 05:50, Tabitha McNerney wrote: > Hi, I have a followup question. I noticed that with the subversion > port, when I get information from it (along with enabling its > variant, the perl variant), for the lib_depends output, I get: > > $ port info --depends_lib postgresql81 @8.1.11 +perl > > --> > > depends_lib: port:readline, port:openssl, port:zlib, bin:perl:perl5.8 > > So if I follow Josh's logic, what this means is that there is a > library dependency of a non-port type that has an executable > condition which is saying, in a paraphrase: > > "the port installation of subversion plus its perl variant has > library MacPort dependencies of readline, openssl and zlib' and it > has a non-MacPort dependency baed on the perl binary executable. If > this perl executable is available on the operating system (e.g., > Mac OS X) then use it, but if this perl executable can not be > found, then the MacPort perl5.8 should be installed and once its > installed its binary executable shall be used" ?? That's about right, except that I would say "If the perl executable is available on the OS, then consider the dependency satisfied, otherwise install the perl5.8 port." > Is it not unusual to see binary executable types of non-port > dependencies in the library (depends_lib) definition of a port? It > doesn't matter if binary requirements are in fact mixed and matched > (regardless of dependency type, library, build, run)? Is your question why is a *binary* (executable) appearing in a *library* dependency clause? That's not necessarily wrong. For example, in the php5 port's mysql5 variant, I declare the dependency like this: depends_lib-append path:${prefix}/bin/mysql_config5:mysql5 The MySQL 5 software doesn't link with the mysql_config5 program as a library, sure, but it does use the mysql_config5 program at build time to figure out where the includes and libraries are, and then it links with those libraries. The point in any of the non-port dependency declarations is to identify a single representative file, the presence or absence of which indicates whether the indicated port needs to be installed to satisfy the dependency or not. In the case of php5 +mysql5, I declared it this way so that if the user already has mysql5-devel installed, that will satisfy the dependency. In the case of postgresql81, the dependency may have been written the way it was so that if the user already has perl5.10 installed, that would satisfy the dependency. Actually I think many ports declare their perl dependency like this so as to avoid forcing the user to install perl5.8, which is a rather large port, when Mac OS X's included perl could probably handle the task. For basic perl tasks, perl hasn't changed in a long time. I don't know what postgresql81 actually does with perl. If something installed by the postgresql81 port actually links with one of the libraries installed by the perl port in ${prefix}/lib/perl5/5.8.8/ darwin-2level/auto then a library dependency (depends_lib) is fine. But if OTOH something installed by the postgresql81 port merely makes use of the perl executable at runtime, then a runtime dependency (depends_run) would be more appropriate. Or, if the perl executable is just used during the build process to produce something, and then perl is not needed anymore to run the thing, then a build-time dependency (depends_build) would be correct (see curl-ca-bundle for an example). To discover what it should be, we'd have to consult the PostgreSQL source code or ask the maintainers of the postgresql81 port or the authors of the PostgreSQL software. From jmr at macports.org Sun Jun 8 04:54:58 2008 From: jmr at macports.org (Joshua Root) Date: Sun, 08 Jun 2008 21:54:58 +1000 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <7fccb3000806080350k2cc794e6s3fb74210ab779b1a@mail.gmail.com> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> <48491A33.8020400@macports.org> <7fccb3000806080350k2cc794e6s3fb74210ab779b1a@mail.gmail.com> Message-ID: <484BC892.4080602@macports.org> Tabitha McNerney wrote: > On 6/6/08, *Joshua Root* > wrote: > Tabitha McNerney wrote: > > But, then my script ran into this specific problem: > > $ port info --depends_lib speex @1.0.5 > > --> > > depends_lib: lib:libogg:libogg > > Hmmm ... the repeat of the library dependency libogg looks to be > incorrect. > Also, the first instance of the libogg dependency is preceded by > "lib:" but > shouldn't that be "port:" instead? > > > This is not an error, but a different type of dependency. A > "port:foo" dependency means "install the port named 'foo'", whereas > "lib:foo:bar" means "check if the library 'foo' is present, and if > not, install the port named 'bar'". You can also use 'bin' or 'path' > instead of 'lib' to make the port installation conditional on the > absence of executables and arbitrary files, respectively. > > > Hi, I have a followup question. I noticed that with the subversion port, > when I get information from it (along with enabling its variant, the > perl variant), for the lib_depends output, I get: > > $ port info --depends_lib postgresql81 @8.1.11 +perl > > > --> > > depends_lib: port:readline, port:openssl, port:zlib, bin:perl:perl5.8 > > > So if I follow Josh's logic, what this means is that there is a library > dependency of a non-port type that has an executable condition which is > saying, in a paraphrase: > > "the port installation of subversion plus its perl variant has library > MacPort dependencies of readline, openssl and zlib' and it has a > non-MacPort dependency baed on the perl binary executable. If this perl > executable is available on the operating system (e.g., Mac OS X) then > use it, but if this perl executable can not be found, then the MacPort > perl5.8 should be installed and once its installed its binary executable > shall be used" ?? That's right (though the last part, "once its installed its binary executable shall be used," is an implicit consequence rather than a guarantee made by the dependency). > Is it not unusual to see binary executable types of non-port > dependencies in the library (depends_lib) definition of a port? It > doesn't matter if binary requirements are in fact mixed and matched > (regardless of dependency type, library, build, run)? Depends_lib doesn't apply to only libraries. Its actual meaning is "these dependencies are required both at build time and at runtime." Depends_build means "required at build time but not runtime", and depends_run means "required at runtime but not build time." So all dependency specifications (bin,lib,path,port) are valid in each list (depends_lib,depends_build,depends_run). (Do we have preferred disambiguating terminology for these concepts? Would make discussing them a lot clearer...) As I mentioned in the earlier discussion of gperf, MacPorts didn't always have port: dependencies, so there are probably quite a few of the other kinds left around which should really be changed to port:. Often they don't cause any problems; sometimes, as with gperf, they do. Apart from XFree86, a deliberate one that you'll see a lot is bin:tex:texlive. This is because there are multiple TeX distribution ports, which are quite large, and many ports will work with any of them equally well. - Josh From msavory1 at nzbox.com Sun Jun 8 13:20:45 2008 From: msavory1 at nzbox.com (Mike Savory) Date: Sun, 8 Jun 2008 13:20:45 -0700 Subject: Request process for ports In-Reply-To: References: Message-ID: <36CDCE28-1A1B-4232-879E-F47471D82EDF@nzbox.com> Hi Joe from the web pages you linked to bwctl, compiles cleanly on OS X and require Iperf2 (which is already a port, should provide a good example) owamp and thrulay seem like they would build on OS X mturoute is a windows program, Check out the existing port hping3 or maybe scamper will meet your needs > scamper can do ICMP-based Path MTU discovery. scamper starts with > the outgoing interface's MTU and discovers the location of Path MTU > bottlenecks. Recent revision of scamper do a PMTUD search when an > ICMP fragmentation required message is not returned to establish the > PMTU to the next point in the network, followed by a TTL limited > search to infer the where failure appears to occur. http://www.wand.net.nz/scamper/ pathdiag seems to be specific to some variant of a Linux kernet and is unlikely to work on OS X > This will require a test host with a web100 kernel and other supporting software, and will be > covered under a future document on advanced pathdiag techniques. dhcptool has not been updated since 2002 and seem specific for embedded Linux applications. openlldp claims OS X support in the latest build A "port" in the MacPorts terminology is just a recipe for building an application and its dependancies. Writing a "port" for MacPorts is reasonably simple if the application is well behaved and can be compiled with prefix= support out of the box. Taking an application from another platform and "porting" it to OS X is usually outside the scope of the MacPorts project and is better taken up with the project concerned and asking them to support OS X. I am actually interested in openlldp but on trying it it fails the ./ configure; make. Regards Mike On Jun 8, 2008, at 3:53 AM, Joe Schnide wrote: > Hello, > > I'm not sure of what the process is for requesting ports. If there is > an officail process, please provide a pointer to the document > detailing > the process. The ports I'd like to request are: > > bwctl > command line client application and a scheduling and policy daemon > that > wraps Iperf > http://e2epi.internet2.edu/bwctl/ > > mturoute > check the mtu values between you and a host > http://www.elifulkerson.com/projects/mturoute.php > > npad Pathdiag > http://www.psc.edu/networking/projects/pathdiag/ > > OWAMP > command line client application and a policy daemon used to > determine one > way latencies between hosts > http://e2epi.internet2.edu/owamp/ > > thrulay is used to measure the capacity of a network by sending a > bulk TCP stream over it > Like other tools (such as iperf, netperf, nettest, nuttcp, ttcp, > etc.), > thrulay can report TCP throughput periodically so that TCP > performance > plots can be produced. Unlike other tools, thrulay not only reports > goodput, but round-trip delay time as well. The output of thrulay > is easy to parse by machine (in fact, it's ready to be used as a data > file for gnuplot). > http://sourceforge.net/projects/thrulay/ > http://e2epi.internet2.edu/thrulay/ > > dhcptool > http://freshmeat.net/projects/dhcptool/ > > openlldp > http://openlldp.sourceforge.net/ > > Please let me know if I can provide further information. > > Thanks > Joe > -- > ------- > jschnide at umn.edu > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > From tabithamc at gmail.com Sun Jun 8 14:09:27 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun, 8 Jun 2008 11:09:27 -1000 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <484BC892.4080602@macports.org> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> <48491A33.8020400@macports.org> <7fccb3000806080350k2cc794e6s3fb74210ab779b1a@mail.gmail.com> <484BC892.4080602@macports.org> Message-ID: <7fccb3000806081409lc244a1cg65a6755dbad46600@mail.gmail.com> Ryan and Josh and everyone else, Thank you so very very much for helping to clarify how all this works and disambiguating the terminology and helping to understand how it all lays together logically! We could write a book: "The Anatomy of MacPorts" and make it a Best Seller on Amazon! All jokes aside, would it be helpful to take the great explanations you have all written and integrating them into chapter 5.4.1 of the MacPorts Guide ? Is this something that would benefit the MacPorts Community (even though I might have been one of the first people to ask such questions explicitly)? Thanks, T.M. On 6/8/08, Joshua Root wrote: > > Tabitha McNerney wrote: > >> On 6/6/08, *Joshua Root* > >> wrote: >> Tabitha McNerney wrote: >> >> But, then my script ran into this specific problem: >> >> $ port info --depends_lib speex @1.0.5 >> >> --> >> >> depends_lib: lib:libogg:libogg >> >> Hmmm ... the repeat of the library dependency libogg looks to be >> incorrect. >> Also, the first instance of the libogg dependency is preceded by >> "lib:" but >> shouldn't that be "port:" instead? >> >> >> This is not an error, but a different type of dependency. A >> "port:foo" dependency means "install the port named 'foo'", whereas >> "lib:foo:bar" means "check if the library 'foo' is present, and if >> not, install the port named 'bar'". You can also use 'bin' or 'path' >> instead of 'lib' to make the port installation conditional on the >> absence of executables and arbitrary files, respectively. >> >> >> Hi, I have a followup question. I noticed that with the subversion port, >> when I get information from it (along with enabling its variant, the perl >> variant), for the lib_depends output, I get: >> >> $ port info --depends_lib postgresql81 @8.1.11 +perl >> >> >> --> >> >> depends_lib: port:readline, port:openssl, port:zlib, bin:perl:perl5.8 >> >> >> So if I follow Josh's logic, what this means is that there is a library >> dependency of a non-port type that has an executable condition which is >> saying, in a paraphrase: >> >> "the port installation of subversion plus its perl variant has library >> MacPort dependencies of readline, openssl and zlib' and it has a non-MacPort >> dependency baed on the perl binary executable. If this perl executable is >> available on the operating system (e.g., Mac OS X) then use it, but if this >> perl executable can not be found, then the MacPort perl5.8 should be >> installed and once its installed its binary executable shall be used" ?? >> > > That's right (though the last part, "once its installed its binary > executable shall be used," is an implicit consequence rather than a > guarantee made by the dependency). > > Is it not unusual to see binary executable types of non-port dependencies >> in the library (depends_lib) definition of a port? It doesn't matter if >> binary requirements are in fact mixed and matched (regardless of dependency >> type, library, build, run)? >> > > Depends_lib doesn't apply to only libraries. Its actual meaning is "these > dependencies are required both at build time and at runtime." Depends_build > means "required at build time but not runtime", and depends_run means > "required at runtime but not build time." So all dependency specifications > (bin,lib,path,port) are valid in each list > (depends_lib,depends_build,depends_run). (Do we have preferred > disambiguating terminology for these concepts? Would make discussing them a > lot clearer...) > > As I mentioned in the earlier discussion of gperf, MacPorts didn't always > have port: dependencies, so there are probably quite a few of the other > kinds left around which should really be changed to port:. Often they don't > cause any problems; sometimes, as with gperf, they do. > > Apart from XFree86, a deliberate one that you'll see a lot is > bin:tex:texlive. This is because there are multiple TeX distribution ports, > which are quite large, and many ports will work with any of them equally > well. > > - Josh > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080608/45aac577/attachment.htm From markd at macports.org Sun Jun 8 16:01:12 2008 From: markd at macports.org (markd at macports.org) Date: Sun, 08 Jun 2008 16:01:12 -0700 Subject: Ports and their dependencies Message-ID: >> This is not an error, but a different type of dependency. A "port:foo" >> dependency means "install the port named 'foo'", whereas "lib:foo:bar" >means >> "check if the library 'foo' is present, and if not, install the port >named >> 'bar'". You can also use 'bin' or 'path' instead of 'lib' to make the >port >> installation conditional on the absence of executables and arbitrary >files, >> respectively. >> >> This is only mentioned in passing in the guide: < >> [ http://guide.macports.org/#reference.dependencies.types >]http://guide.macports.org/#reference.dependencies.types>. It's documented >> a little better in the portfile(7) manual. >> >> Most of the time dependencies should be of the port: variety, but >sometimes >> it is better/easier to use software that Apple ships with OS X, a common >> example being X11. You'll see lib:libX11.6:XFree86 in a lot of >portfiles. > > How is it described better in the man page? Below is the text in the guide. And don't forget that the guide is going to be the source for the new man pages (1.7? 1.8?), so if the man pages are better in some respect, the guide needs to be corrected in those respects. http://guide.macports.org/#reference.dependencies.types ----------- Port dependencies should be provided by MacPorts ports whenever possible, however dependencies may be provided by vendor-supplied software when satisfying a dependency by a port is not practical or desirable for a special reason. Dependencies of this type are called non-port dependencies. Non-port dependencies should only be used if the application or library can be installed by multiple ports (for example stable and -devel version) or if it can't be installed with MacPorts. Port dependencies, the preferred type, are specified as shown in these examples: depends_lib port:rrdtool port:apache2 depends_build port:libtool depends_run port:apache2 port:php5 Non-port dependencies are specified as shown in these examples: depends_lib lib:libX11.6:xorg depends_build bin:glibtool:libtool depends_run path:${prefix}/lib/libltdl.a:libtool ---------- Mark From jmr at macports.org Mon Jun 9 07:25:51 2008 From: jmr at macports.org (Joshua Root) Date: Tue, 10 Jun 2008 00:25:51 +1000 Subject: Ports and their dependencies In-Reply-To: References: Message-ID: <484D3D6F.7090608@macports.org> markd at macports.org wrote: > How is it described better in the man page? The man page says what lib,bin,path mean: > type:: > > may be used. Where type is "bin" if is a program, "lib" > if it is a library, or "path" if it is a path to an installed file. The guide also doesn't explicitly state that the thing at the end of the depspec is a port name (maybe that's obvious though). Another point is that neither the guide nor the man page explicitly states what is done with the port mentioned at the end of non-port depspecs, i.e. it is installed if and only if the specified library, binary or file is not present. Might also want to mention that in lib: dependencies, you list the library name without its extension (e.g. .dylib on Darwin). - Josh From tabithamc at gmail.com Mon Jun 9 09:17:51 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Mon, 9 Jun 2008 06:17:51 -1000 Subject: Ports and their dependencies In-Reply-To: <484D3D6F.7090608@macports.org> References: <484D3D6F.7090608@macports.org> Message-ID: <7fccb3000806090917k24cb0216tf62412a663355d0@mail.gmail.com> On 6/9/08, Joshua Root wrote: > > markd at macports.org wrote: > > How is it described better in the man page? > > > The man page says what lib,bin,path mean: > > > type:: > > > > may be used. Where type is "bin" if is a program, "lib" > > if it is a library, or "path" if it is a path to an installed file. Reading this and also the previous posts, the condition of "path" being a path to an "installed file" (and given Ryan's example in a different thread whereby the php5 port with the mysql5 variant added triggers the depends_lib of a path whose path value leads to a possibly installed configuration file (but this configuration file only exists if the mysql5_dev port has been installed) kind of strikes me as a means to confusion because such a dependency isn't really a "non-port" then right? In other words, an "installed file" which has a path that only exists if the port responsible for installing that file has itself been built and installed, then really that's not a "non-port" unlike a lib: or bin: which could be, say, an Apple Mac OS X provided resource (library or binary). True? Granted, from a pure syntactical standpoint, the "path: ..." is not the same as a "port: ..." and thus I can see why its categorized as a "non-port". Thanks, T.M. The guide also doesn't explicitly state that the thing at the end of the > depspec is a port name (maybe that's obvious though). Another point is > that neither the guide nor the man page explicitly states what is done > with the port mentioned at the end of non-port depspecs, i.e. it is > installed if and only if the specified library, binary or file is not > present. > > Might also want to mention that in lib: dependencies, you list the > library name without its extension (e.g. .dylib on Darwin). > > - Josh > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080609/ec5cab3f/attachment.htm From tabithamc at gmail.com Mon Jun 9 09:23:37 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Mon, 9 Jun 2008 06:23:37 -1000 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> <48491A33.8020400@macports.org> Message-ID: <7fccb3000806090923x3a178ea7rddb8bc9c486c0bbf@mail.gmail.com> On 6/6/08, Ryan Schmidt wrote: > > > On Jun 6, 2008, at 06:06, Joshua Root wrote: > > Tabitha McNerney wrote: >> >> But, then my script ran into this specific problem: >>> >>> $ port info --depends_lib speex @1.0.5 >>> >>> --> >>> >>> depends_lib: lib:libogg:libogg >> >> Ryan, Josh, et al: This may sound like a dumb question, but what would be a suggested way to discover if Apple / Mac OS X is provided the same or similar library for a non-port library dependency of type lib: (e.g. depends_lib: lib:libogg)? In the case of a bin: type I can easily do something like: $ which perl Easy as pie. Is there a command similar to "which" that can be passed the name of a library from a MacPorts file such as "libogg" written above? A program such as libtool? Which would come back with info definitively yes or no about the library name collision? I suppose I could also dig for it in /usr/lib but it would be nice to have something like "which" for libraries as part of my MacPorts quality control script. Thanks, T.M. > Hmmm ... the repeat of the library dependency libogg looks to be incorrect. >>> Also, the first instance of the libogg dependency is preceded by "lib:" >>> but >>> shouldn't that be "port:" instead? >>> >> >> This is not an error, but a different type of dependency. A "port:foo" >> dependency means "install the port named 'foo'", whereas "lib:foo:bar" >> means "check if the library 'foo' is present, and if not, install the >> port named 'bar'". You can also use 'bin' or 'path' instead of 'lib' to >> make the port installation conditional on the absence of executables and >> arbitrary files, respectively. >> >> This is only mentioned in passing in the guide: >> . It's >> documented a little better in the portfile(7) manual. >> >> Most of the time dependencies should be of the port: variety, but >> sometimes it is better/easier to use software that Apple ships with OS >> X, a common example being X11. You'll see lib:libX11.6:XFree86 in a lot >> of portfiles. >> > > In the case of the speex port, the dependency should be changed to > "port:libogg". This port probably dates from a time before MacPorts had > "port:"-style dependencies. I changed the dependency for speex in r37416. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080609/f9d9aaa1/attachment.htm From kuepper.jochen at googlemail.com Mon Jun 9 09:30:42 2008 From: kuepper.jochen at googlemail.com (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Mon, 9 Jun 2008 18:30:42 +0200 Subject: Problem with Molden installation In-Reply-To: <1213015266.484d24e2b63f1@webmail.u-bourgogne.fr> References: <1213015266.484d24e2b63f1@webmail.u-bourgogne.fr> Message-ID: <535A40D6-8BAE-4455-A4B0-34C0124C39F5@googlemail.com> On 09.06.2008, at 14:41, Vincent Boudon wrote: > sudo port install molden > ---> Verifying checksum(s) for molden > Error: Checksum (md5) mismatch for molden4.6.tar.gz > Error: Checksum (sha1) mismatch for molden4.6.tar.gz > Error: Checksum (rmd160) mismatch for molden4.6.tar.gz > Error: Target org.macports.checksum returned: Unable to verify file > checksums > Error: Status 1 encountered during processing. This is due to a stealth maintainer upgrade. It is now fixed in MacPorts. > What shall I do ? Generally, report a bug via trac.macports.org. Now (or better, in a few hours) you have to run sudo port sync sudo port install molden 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 jmr at macports.org Mon Jun 9 10:02:55 2008 From: jmr at macports.org (Joshua Root) Date: Tue, 10 Jun 2008 03:02:55 +1000 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <7fccb3000806090923x3a178ea7rddb8bc9c486c0bbf@mail.gmail.com> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> <48491A33.8020400@macports.org> <7fccb3000806090923x3a178ea7rddb8bc9c486c0bbf@mail.gmail.com> Message-ID: <484D623F.7090600@macports.org> Tabitha McNerney wrote: > > On 6/6/08, *Ryan Schmidt* > wrote: > > > On Jun 6, 2008, at 06:06, Joshua Root wrote: > > Tabitha McNerney wrote: > > But, then my script ran into this specific problem: > > $ port info --depends_lib speex @1.0.5 > > --> > > depends_lib: lib:libogg:libogg > > > Ryan, Josh, et al: > > This may sound like a dumb question, but what would be a suggested way > to discover if Apple / Mac OS X is provided the same or similar library > for a non-port library dependency of type lib: (e.g. depends_lib: > lib:libogg)? In the case of a bin: type I can easily do something like: > > $ which perl > > Easy as pie. Is there a command similar to "which" that can be passed > the name of a library from a MacPorts file such as "libogg" written > above? A program such as libtool? Which would come back with info > definitively yes or no about the library name collision? I suppose I > could also dig for it in /usr/lib but it would be nice to have something > like "which" for libraries as part of my MacPorts quality control script. `locate ${libname}.dylib` would work I guess, though you'd probably want to filter the output to contain only the paths where MacPorts will search. Usually that list is as follows: /Library/Frameworks /Network/Library/Frameworks /System/Library/Frameworks /lib /usr/lib /usr/X11R6/lib /usr/X11/lib ${prefix}/lib However, this can be modified by the DYLD_FRAMEWORK_PATH, DYLD_FALLBACK_FRAMEWORK_PATH, DYLD_LIBRARY_PATH, and DYLD_FALLBACK_LIBRARY_PATH environment variables. - Josh From jbarr at nmt.edu Mon Jun 9 16:20:28 2008 From: jbarr at nmt.edu (Jayson Barr) Date: Mon, 9 Jun 2008 17:20:28 -0600 Subject: Question about install options Message-ID: I am considering using macports to make packages for distribution at work. I have a question about functionality: Is it possible to configure macports in such a way as to make it so that my current installation layout (by this I mean file locations) will be preserved? Basically I am having trouble finding documentation on this feature talked about in MacPorts Guide: "Allows you to create pre-compiled binary installers of ported applications to quickly install software on remote computers without compiling from source code." Could someone point me to the right page? thanks From ryandesign at macports.org Mon Jun 9 16:26:43 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 9 Jun 2008 18:26:43 -0500 Subject: Ports and their dependencies In-Reply-To: <7fccb3000806090917k24cb0216tf62412a663355d0@mail.gmail.com> References: <484D3D6F.7090608@macports.org> <7fccb3000806090917k24cb0216tf62412a663355d0@mail.gmail.com> Message-ID: <92364B23-CCBD-4039-BBB3-344CF32DF635@macports.org> On Jun 9, 2008, at 11:17, Tabitha McNerney wrote: >> The man page says what lib,bin,path mean: >> >> > type:: >> > >> > may be used. Where type is "bin" if is a >> program, "lib" >> > if it is a library, or "path" if it is a path to an >> installed file. > > Reading this and also the previous posts, the condition of "path" > being a path to an "installed file" (and given Ryan's example in a > different thread whereby the php5 port with the mysql5 variant > added triggers the depends_lib of a path whose path value leads to > a possibly installed configuration file (but this configuration > file only exists if the mysql5_dev port has been installed) I didn't say that: the situation is that either the mysql5 port or the mysql5-devel port can provide the mysql_config5 file (and indeed all the MySQL libraries) but only one of these two ports can be installed at a time. This is (or should be) the case for all -devel ports. The intention is that most users will use mysql5 but some will want to try the new features only available in mysql5-devel. To support this notion, all ports that depend on MySQL 5 functionality must declare their dependency on MySQL 5 not via a port:-style dependency (because that would unequivocally require the mysql5 port, not the mysql5-devel port), but instead via a path:-style dependency to a specific path within ${prefix}. The lib:-style dependency should not be used, because a MySQL library provided by the operating system (for example on Mac OS X Server) would also satisfy that dependency, but we don't want it to. Maybe path:${prefix}/something:portname should be the preferred dependency style (instead of port:portname)? Unless we have a better plan for -devel ports (or the "slots" feature) in the future. > kind of strikes me as a means to confusion because such a > dependency isn't really a "non-port" then right? I too find the "non-port" terminology confusing and not entirely accurate. > In other words, an "installed file" which has a path that only > exists if the port responsible for installing that file has itself > been built and installed, then really that's not a "non-port" > unlike a lib: or bin: which could be, say, an Apple Mac OS X > provided resource (library or binary). True? Granted, from a pure > syntactical standpoint, the "path: ..." is not the same as a > "port: ..." and thus I can see why its categorized as a "non-port". From ryandesign at macports.org Mon Jun 9 16:34:00 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 9 Jun 2008 18:34:00 -0500 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <7fccb3000806090923x3a178ea7rddb8bc9c486c0bbf@mail.gmail.com> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> <48491A33.8020400@macports.org> <7fccb3000806090923x3a178ea7rddb8bc9c486c0bbf@mail.gmail.com> Message-ID: <862F4FE9-99DA-40A3-8CEB-2E64F68CEEE8@macports.org> On Jun 9, 2008, at 11:23, Tabitha McNerney wrote: > This may sound like a dumb question, but what would be a suggested > way to discover if Apple / Mac OS X is provided the same or similar > library for a non-port library dependency of type lib: (e.g. > depends_lib: lib:libogg)? In the case of a bin: type I can easily > do something like: > > $ which perl > > Easy as pie. Is there a command similar to "which" that can be > passed the name of a library from a MacPorts file such as "libogg" > written above? A program such as libtool? Which would come back > with info definitively yes or no about the library name collision? > I suppose I could also dig for it in /usr/lib but it would be nice > to have something like "which" for libraries as part of my MacPorts > quality control script. Why do you want to know? :-) As a general rule, if you're writing a port that has dependencies on other libraries, declare the dependency on other MacPorts ports. There's no need to investigate which libraries might already be provided with the version of Mac OS X you happen to have on your computer because it might be different in other versions on Mac OS X which is why we try to use only other MacPorts ports so we know what we're getting. From ryandesign at macports.org Mon Jun 9 16:35:39 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 9 Jun 2008 18:35:39 -0500 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <484BC892.4080602@macports.org> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> <48491A33.8020400@macports.org> <7fccb3000806080350k2cc794e6s3fb74210ab779b1a@mail.gmail.com> <484BC892.4080602@macports.org> Message-ID: <20C79627-B4A6-4C49-AD53-ACE803B8F687@macports.org> On Jun 8, 2008, at 06:54, Joshua Root wrote: > Depends_lib doesn't apply to only libraries. Its actual meaning is > "these dependencies are required both at build time and at runtime." Goodness. I never thought of it that way. I suppose I can't find anything wrong with that definition... > Depends_build means "required at build time but not runtime", and > depends_run means "required at runtime but not build time." So all > dependency specifications (bin,lib,path,port) are valid in each list > (depends_lib,depends_build,depends_run). (Do we have preferred > disambiguating terminology for these concepts? Would make discussing > them a lot clearer...) From ryandesign at macports.org Mon Jun 9 17:46:30 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 9 Jun 2008 19:46:30 -0500 Subject: Question about install options In-Reply-To: References: Message-ID: On Jun 9, 2008, at 18:20, Jayson Barr wrote: > I am considering using macports to make packages for distribution > at work. > I have a question about functionality: > Is it possible to configure macports in such a way as to make it so > that my current > installation layout (by this I mean file locations) will be preserved? I'm not sure what you mean? > Basically I am having trouble finding documentation on this feature > talked about in MacPorts Guide: > "Allows you to create pre-compiled binary installers of ported > applications to quickly install software on remote computers without > compiling from source code." > > Could someone point me to the right page? If you "port pkg foo" (create a package of foo) or "port mpkg foo" (create a package of foo and all its dependencies), it will create a Mac OS X installer package of foo (and, with mpkg, its dependencies). On the computer on which you install this package, the files will get installed in the same place where they were on the computer where you made the package. For example, if you have MacPorts in /opt/local (the default) and create a package, then on the other computer where you install the package, the files will also go into /opt/local. Note that the files installed by the package are not registered with a MacPorts installation on that computer. So that other computer where you install the package should not now nor at any time while your package is installed have MacPorts installed. From tabithamc at gmail.com Mon Jun 9 17:53:51 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Mon, 9 Jun 2008 14:53:51 -1000 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <862F4FE9-99DA-40A3-8CEB-2E64F68CEEE8@macports.org> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> <48491A33.8020400@macports.org> <7fccb3000806090923x3a178ea7rddb8bc9c486c0bbf@mail.gmail.com> <862F4FE9-99DA-40A3-8CEB-2E64F68CEEE8@macports.org> Message-ID: <7fccb3000806091753k5fdd66dcq6a4fcd746f3adfc0@mail.gmail.com> On 6/9/08, Ryan Schmidt wrote: > > > On Jun 9, 2008, at 11:23, Tabitha McNerney wrote: > > This may sound like a dumb question, but what would be a suggested way to >> discover if Apple / Mac OS X is provided the same or similar library for a >> non-port library dependency of type lib: (e.g. depends_lib: lib:libogg)? In >> the case of a bin: type I can easily do something like: >> >> $ which perl >> >> Easy as pie. Is there a command similar to "which" that can be passed the >> name of a library from a MacPorts file such as "libogg" written above? A >> program such as libtool? Which would come back with info definitively yes or >> no about the library name collision? I suppose I could also dig for it in >> /usr/lib but it would be nice to have something like "which" for libraries >> as part of my MacPorts quality control script. >> > > Why do you want to know? :-) > > As a general rule, if you're writing a port that has dependencies on other > libraries, declare the dependency on other MacPorts ports. There's no need > to investigate which libraries might already be provided with the version of > Mac OS X you happen to have on your computer because it might be different > in other versions on Mac OS X which is why we try to use only other MacPorts > ports so we know what we're getting. Ryan, I think I am confused, sorry. The reason I want to know is that I want to be sure that any of the hundreds of ports I install, say on an Xserve, are in fact only dependent on libraries of other MacPorts which libraries would need to be installed. In fact, I don't want any libraries to depend on OS X's names of those same libraries but there might be an exception or two. For example, I do use Apple's X11 application and so let's take the ImageMagik MacPort as an example. ImageMagic has a depend_lib that outputs on the command line (port info --depends_lib ...) with a non-port dependency of type "lib:" like this: lib:libX11.6:XFree86 > How do I (or better yet a script I'm writing) parse that information? Meaning, for example, are libraries associated with libX11.6 supplied by another Mac Port, or does MacPorts look on the root file system (e.g., Mac OS X 10.5 Leopard) to try and find the libraries supplied by Apple (?) with the same namespace associated with "libX11.6"? Another example, lets' take the sodipodi port. It has a library non-port dependency that looks like this: lib:libgnomeprintui-2-2:libgnomeprintui > Can either the libraries associated with libgnomeprintui-2-2 or libgnomeprintui be provided potentially by Mac OS X? Or like the non-port dependency of type path:, only these lib: non-port dependencies can be found within the MacPorts prefix on the filesystem? I just want to be sure that I can know with certainty if any of these libraries might be somehow be provided by OS X and if so when to be alerted when this might be the case ahead of time before I install a port. I hope these questions are clearer, thanks! T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080609/d21f3053/attachment.htm From markd at macports.org Mon Jun 9 18:57:14 2008 From: markd at macports.org (markd at macports.org) Date: Mon, 09 Jun 2008 18:57:14 -0700 Subject: Ports and their dependencies Message-ID: >All jokes aside, would it be helpful to take the great >explanations you have all written and integrating them into chapter 5.4.1 >of >the MacPorts Guide >? Is this >something that would benefit the MacPorts Community (even though I >might have been one of the first people to ask such questions explicitly)? I renamed "non-port dependencies" to "file dependencies". See what you think of the revisions in r37493. It can be refined further if necessary. Thanks to Joshua and Ryan for the explanations. http://trac.macports.org/changeset/37493 Mark From jmr at macports.org Mon Jun 9 20:47:33 2008 From: jmr at macports.org (Joshua Root) Date: Tue, 10 Jun 2008 13:47:33 +1000 Subject: Ports and their dependencies In-Reply-To: References: Message-ID: <484DF955.7010508@macports.org> markd at macports.org wrote: >> All jokes aside, would it be helpful to take the great >> explanations you have all written and integrating them into chapter 5.4.1 >> of >> the MacPorts Guide >> ? Is this >> something that would benefit the MacPorts Community (even though I >> might have been one of the first people to ask such questions explicitly)? > > I renamed "non-port dependencies" to "file dependencies". See what you > think of the revisions in r37493. It can be refined further if necessary. > Thanks to Joshua and Ryan for the explanations. > > http://trac.macports.org/changeset/37493 Looks good, thanks. I found a couple of bugs though: Line 14/15: "though you may remove one with a build dependency" should be "though you may remove one that is a build dependency". Line 100/101: "Note that the <port> specified is only installed if the file the specified library, binary, or file is not found." Need to remove "the file". And one that was incorrect all along: "upgrading a port will upgrade its library and build dependencies also, but not its run dependencies." Runtime dependencies are in fact upgraded. - Josh From ryandesign at macports.org Mon Jun 9 21:30:13 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 9 Jun 2008 23:30:13 -0500 Subject: Ports and their dependencies (run deps and also versioning questions) In-Reply-To: <7fccb3000806091753k5fdd66dcq6a4fcd746f3adfc0@mail.gmail.com> References: <7fccb3000805301041q268896dbq14d58299b85132b4@mail.gmail.com> <48404223.3040605@macports.org> <7fccb3000805310924o56bbc61ei9faec108d70ceed4@mail.gmail.com> <484215E5.2020406@macports.org> <7fccb3000806060215y65e7cf86t42f155d3fb03b9f7@mail.gmail.com> <48491A33.8020400@macports.org> <7fccb3000806090923x3a178ea7rddb8bc9c486c0bbf@mail.gmail.com> <862F4FE9-99DA-40A3-8CEB-2E64F68CEEE8@macports.org> <7fccb3000806091753k5fdd66dcq6a4fcd746f3adfc0@mail.gmail.com> Message-ID: On Jun 9, 2008, at 19:53, Tabitha McNerney wrote: > On 6/9/08, Ryan Schmidt wrote: > >> On Jun 9, 2008, at 11:23, Tabitha McNerney wrote: >> >>> This may sound like a dumb question, but what would be a >>> suggested way to discover if Apple / Mac OS X is provided the >>> same or similar library for a non-port library dependency of type >>> lib: (e.g. depends_lib: lib:libogg)? In the case of a bin: type I >>> can easily do something like: >>> >>> $ which perl >>> >>> Easy as pie. Is there a command similar to "which" that can be >>> passed the name of a library from a MacPorts file such as >>> "libogg" written above? A program such as libtool? Which would >>> come back with info definitively yes or no about the library name >>> collision? I suppose I could also dig for it in /usr/lib but it >>> would be nice to have something like "which" for libraries as >>> part of my MacPorts quality control script. >> >> Why do you want to know? :-) >> >> As a general rule, if you're writing a port that has dependencies >> on other libraries, declare the dependency on other MacPorts >> ports. There's no need to investigate which libraries might >> already be provided with the version of Mac OS X you happen to >> have on your computer because it might be different in other >> versions on Mac OS X which is why we try to use only other >> MacPorts ports so we know what we're getting. > > Ryan, I think I am confused, sorry. The reason I want to know is > that I want to be sure that any of the hundreds of ports I install, > say on an Xserve, are in fact only dependent on libraries of other > MacPorts which libraries would need to be installed. In fact, I > don't want any libraries to depend on OS X's names of those same > libraries but there might be an exception or two. For example, I do > use Apple's X11 application and so let's take the ImageMagik > MacPort as an example. ImageMagic has a depend_lib that outputs on > the command line (port info --depends_lib ...) with a non-port > dependency of type "lib:" like this: > > lib:libX11.6:XFree86 > > How do I (or better yet a script I'm writing) parse that > information? Meaning, for example, are libraries associated with > libX11.6 supplied by another Mac Port, or does MacPorts look on the > root file system (e.g., Mac OS X 10.5 Leopard) to try and find the > libraries supplied by Apple (?) with the same namespace associated > with "libX11.6"? X11 is an exception to the usual rule, because the X11 system Apple provides is good and has a Mac OS X look and feel, and XFree86 is large, takes a long time to build, and in the end you get something that looks like Linux, not Mac OS X. Also X11 software seems to be special in that it needs to install into /usr/X11R6 (or /usr/X11 on 10.5 and greater) so you can only install XFree86 if you have not already installed Apple's X11. But Apple's X11 is installed by default on 10.5 and later, and is pretty common on 10.4 too. It's available as a download for 10.3, and isn't available on earlier Mac OS X. For these reasons, for ports that depend on an X Window system, the dependency should be written "lib:libX11.6:XFree86" so that they will use the Apple X11 installation if it's installed. If you really do not want to use Apple's X11 to satisfy the X dependency, then uninstall Apple's X11 (remove /usr/X11 (or /usr/X11R6 on 10.4 or earlier) and /Applications/Utilities/X11.app), and then MacPorts will build and use the XFree86 port. Another option is to use the xorg port. xorg is a competing X Window system which should also work. It will also provide libX11.6 so it will also satisfy that dependency. > Another example, lets' take the sodipodi port. It has a library non- > port dependency that looks like this: > > lib:libgnomeprintui-2-2:libgnomeprintui > > Can either the libraries associated with libgnomeprintui-2-2 or > libgnomeprintui be provided potentially by Mac OS X? I know of no version of Mac OS X that includes any Gnome components. The sodipodi port has no maintainer, so it has not seen any love in a long time. The dependency on lib:libgnomeprintui-2-2:libgnomeprintui has been in the port since it was originally authored in r4876 on 2004-01-19, likely well before MacPorts had port:-style dependencies. I changed it to a port:-style dependency in r37496. > Or like the non-port dependency of type path:, only these lib: non- > port dependencies can be found within the MacPorts prefix on the > filesystem? All non-port dependencies could be satisfied by things outside of MacPorts, even path:-style depending on how the path is written. For example, mpg123 declares a peculiar dependency on "path:/System/ Library/Frameworks/CoreAudio.framework:XXX". I guess it means it requires the CoreAudio framework, and if that's not present, then your Mac OS X is too old? If that case ever occurs, of course, an error will be printed that port "XXX" could not be found, so this isn't a good way to solve this problem. > I just want to be sure that I can know with certainty if any of > these libraries might be somehow be provided by OS X and if so when > to be alerted when this might be the case ahead of time before I > install a port. There's no way to know before you install a port what will ultimately happen when you install it. What it links with could even vary based on Mac OS X version or even your processor architecture. But after a port is installed, you can use "otool -L" on all Mach-O files installed by the port to see what it's actually linking with. For example, here's what cairo links with: $ port contents cairo | sed 1d | xargs file \ | grep Mach-O | sed 's%[: ].*$%%' | uniq \ | xargs otool -L /opt/local/lib/libcairo.2.17.5.dylib: /opt/local/lib/libcairo.2.dylib (compatibility version 20.0.0, current version 20.5.0) /opt/local/lib/libfontconfig.1.dylib (compatibility version 5.0.0, current version 5.0.0) /opt/local/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /opt/local/lib/libexpat.1.dylib (compatibility version 7.0.0, current version 7.2.0) /opt/local/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0) /opt/local/lib/libpng12.0.dylib (compatibility version 30.0.0, current version 30.0.0) /opt/local/lib/libXrender.1.dylib (compatibility version 5.0.0, current version 5.0.0) /usr/X11R6/lib/libX11.6.dylib (compatibility version 6.2.0, current version 6.2.0) /usr/X11R6/lib/libSM.6.dylib (compatibility version 6.0.0, current version 6.0.0) /usr/X11R6/lib/libICE.6.dylib (compatibility version 6.3.0, current version 6.3.0) /opt/local/lib/libpixman-1.0.dylib (compatibility version 11.0.0, current version 11.0.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/ CoreServices (compatibility version 1.0.0, current version 18.0.0) /System/Library/Frameworks/ApplicationServices.framework/ Versions/A/ApplicationServices (compatibility version 1.0.0, current version 22.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.9) $ As it shows, the cairo library links with fontconfig, libiconv, zlib, expat, freetype, libpng, xrender and libpixman from MacPorts; libX11, libSM and libICE from Apple's X11; and CoreServices, ApplicationServices and libSystem provided by the core Mac OS X. Replace "cairo" with the name of another installed port in the command line above to see what that port links with. From tabithamc at gmail.com Mon Jun 9 23:51:28 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Mon, 9 Jun 2008 20:51:28 -1000 Subject: Ports and their dependencies In-Reply-To: References: Message-ID: <7fccb3000806092351y1202a710mcd0ade9d08837cce@mail.gmail.com> On 6/9/08, markd at macports.org wrote: > > >All jokes aside, would it be helpful to take the great > >explanations you have all written and integrating them into chapter 5.4.1 > >of > >the MacPorts Guide > >? Is this > >something that would benefit the MacPorts Community (even though I > >might have been one of the first people to ask such questions explicitly)? > > I renamed "non-port dependencies" to "file dependencies". See what you > think of the revisions in r37493. It can be refined further if necessary. > Thanks to Joshua and Ryan for the explanations. > > http://trac.macports.org/changeset/37493 Mark, that is great, thank you so much. The term "file dependencies" makes a ton more sense than "non-port". And thanks Josh for proof reading the changes Mark made. This makes the MacPorts community ever more stronger! Tabitha Mark > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080609/146569cb/attachment.htm From lrivers at gmail.com Tue Jun 10 09:27:30 2008 From: lrivers at gmail.com (Lorin Rivers) Date: Tue, 10 Jun 2008 11:27:30 -0500 Subject: New Howto In-Reply-To: References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> Message-ID: <949829840806100927x3a90e548rf8d24ffd3109c221@mail.gmail.com> Leaving aside the issue of what the best platform for sharing the info might be. If nobody knows it's there, the kick-assingest wiki server the world has or will ever see is not going to address my suggestion in the slightest. My point was that it's quite a challenge finding the current how-to's even if you already know they exist. If you are not in that smallish (I'm guessing--but I've been using *Ports for a fairly long time, and it was a recent message on this list that made me aware) category, then the chances this very useful series of articles will reach the audience that needs it is quite small. Just to refresh, there needs to be a link from the main MacPorts documentation site to the how-to's. As a first step, it's awesome. On Thu, Jun 5, 2008 at 2:22 PM, Jordan K. Hubbard wrote: > > On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: > > Awesome! I did not even know about these How To's. >> >> You know, it's actually kind of hard to find them, if you don't know about >> where they are in the first place. I think they deserve more prominence. >> There should be a link from the documentation area of the main MacPorts site >> to the HowTo's. >> > > I'm still of the opinion that we should install mediawiki on the site and > turn these "howtos" into full-blown, collaboratively maintained reference > pages worthy of wikipedia (but, unlike wikipedia, also free to be relevant > only in the context of projects hosted at macosforge). What do other folks > think? > > - Jordan > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080610/c31dccdc/attachment.htm From markd at macports.org Tue Jun 10 09:43:34 2008 From: markd at macports.org (markd at macports.org) Date: Tue, 10 Jun 2008 09:43:34 -0700 Subject: Is "MacPort" a valid term? Message-ID: >For a long time, I thought that when people were saying port, in this >discussion, I thought the were referring to a port or a tcp/ip address. >like localhost:80 Clarity is one of the reasons that in the past I frequently used the term "MacPorts port" (to distinguish it from FreeBSD and other port systems), but this is too cumbersome and inelegant when used a lot so I mostly curtailed that. Using the term "MacPort" would make the term clear, but is that really a valid term in current usage? It seems we're only comfortable with the plural form, and I think that is why we always fall back to the more generic "port" to express a single MacPorts port. Mark From kuepper.jochen at googlemail.com Tue Jun 10 11:38:54 2008 From: kuepper.jochen at googlemail.com (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Tue, 10 Jun 2008 20:38:54 +0200 Subject: Problem with Molden installation In-Reply-To: References: <1213015266.484d24e2b63f1@webmail.u-bourgogne.fr> <535A40D6-8BAE-4455-A4B0-34C0124C39F5@googlemail.com> Message-ID: <06000D69-CD95-471C-842E-EC7E2072F441@googlemail.com> On 10.06.2008, at 16:26, Vincent BOUDON wrote: > Thanks a lot, it worked fine. > > I am really sorry to bother you again with this, but I have another > problem with molden on Mac OS X and I must admit that the way to > report this via trac.macports.org seems quite obscure to me ... please report it via trac, so we have the records and more people can look at it... > Each time I try to add a line in the Z-matrix editor, I get: > > Segmentation fault i can reproduce this. However, I am sorry, I do not have time to look at this right now. Please report it in trac and to the molden maintainer upstreams 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: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080610/97c7cd47/attachment.sig From raimue at macports.org Tue Jun 10 11:53:34 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Tue, 10 Jun 2008 20:53:34 +0200 Subject: Problem with Molden installation In-Reply-To: <06000D69-CD95-471C-842E-EC7E2072F441@googlemail.com> References: <1213015266.484d24e2b63f1@webmail.u-bourgogne.fr> <535A40D6-8BAE-4455-A4B0-34C0124C39F5@googlemail.com> <06000D69-CD95-471C-842E-EC7E2072F441@googlemail.com> Message-ID: <484ECDAE.6060601@macports.org> Jochen K?pper wrote: > On 10.06.2008, at 16:26, Vincent BOUDON wrote: >> I am really sorry to bother you again with this, but I have another >> problem with molden on Mac OS X and I must admit that the way to >> report this via trac.macports.org seems quite obscure to me ... Our guide should shed some light on this, see Rainer From paulbeard at gmail.com Tue Jun 10 12:59:31 2008 From: paulbeard at gmail.com (paul beard) Date: Tue, 10 Jun 2008 12:59:31 -0700 Subject: New Howto Message-ID: On Tue, Jun 10, 2008 at 12:00 PM, < macports-users-request at lists.macosforge.org> wrote: Message: 11 Date: Tue, 10 Jun 2008 11:27:30 -0500 From: "Lorin Rivers" Subject: Re: New Howto To: "Jordan K. Hubbard" Cc: MacPorts Users Message-ID: <949829840806100927x3a90e548rf8d24ffd3109c221 at mail.gmail.com> Content-Type: text/plain; charset="utf-8" > Leaving aside the issue of what the best platform for sharing the info might > be. If nobody knows it's there, the kick-assingest wiki server the world has > or will ever see is not going to address my suggestion in the slightest. > My point was that it's quite a challenge finding the current how-to's even > if you already know they exist. If you are not in that smallish (I'm > guessing--but I've been using *Ports for a fairly long time, and it was a > recent message on this list that made me aware) category, then the chances > this very useful series of articles will reach the audience that needs it is > quite small. > Just to refresh, there needs to be a link from the main MacPorts > documentation site to the how-to's. As a first step, it's awesome. > Taking up the earlier comment on a need for discussion, what are the pros and cons of the different wiki platforms? I would say, if I had a vote (who does?), that whatever people are willing to use wins. It may not be elegant or state of the art, but the best is the enemy of the good, and good is usually good enough. -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080610/62203832/attachment.htm From jkh at apple.com Tue Jun 10 13:04:15 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Tue, 10 Jun 2008 13:04:15 -0700 Subject: New Howto In-Reply-To: <949829840806100927x3a90e548rf8d24ffd3109c221@mail.gmail.com> References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> <949829840806100927x3a90e548rf8d24ffd3109c221@mail.gmail.com> Message-ID: <02061700-00F5-4457-9EDE-3056C34DF40D@apple.com> On Jun 10, 2008, at 9:27 AM, Lorin Rivers wrote: > Leaving aside the issue of what the best platform for sharing the > info might be. If nobody knows it's there, the kick-assingest wiki > server the world has or will ever see is not going to address my > suggestion in the slightest. Well, to be fair, I thought I was trying to address that by suggesting that there should be a "top level doc project" - individual projects could point up to it just as easily as it could point down to them, but it would be a clear "docs portal" for everyone. I know not everyone agrees with this assertion, but I think all the projects on macosforge have more knowledge collectively in common than they think. I then look laterally to the success of projects like wikipedia, which has a knowledge base and contributing community far more vast by comparison, and cannot help but think "hmmm.." > Just to refresh, there needs to be a link from the main MacPorts > documentation site to the how-to's. As a first step, it's awesome. No disagreement at all. Links are cheap, people! Use them! - Jordan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080610/86885729/attachment.htm From m_nez_j at mac.com Tue Jun 10 13:59:02 2008 From: m_nez_j at mac.com (Mack Johnson) Date: Tue, 10 Jun 2008 13:59:02 -0700 Subject: ThisApp? Message-ID: This port is no longer? ---> Attempting to fetch JHymn_0_9_2_source.zip from http://www.hymn-project.org/download/ ---> Attempting to fetch JHymn_0_9_2_source.zip from http://svn.macports.org/repository/macports/distfiles/JHymn ---> Attempting to fetch JHymn_0_9_2_source.zip from http://svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch JHymn_0_9_2_source.zip from http://svn.macports.org/repository/macports/downloads/JHymn Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. Mack From ryandesign at macports.org Tue Jun 10 14:30:05 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 10 Jun 2008 16:30:05 -0500 Subject: JHymn distfiles (was: Re: ThisApp?) In-Reply-To: References: Message-ID: <9882DD42-504B-4982-8AC1-C6AD55B75244@macports.org> On Jun 10, 2008, at 15:59, Mack Johnson wrote: > This port is no longer? > ---> Attempting to fetch JHymn_0_9_2_source.zip from http:// > www.hymn-project.org/download/ > ---> Attempting to fetch JHymn_0_9_2_source.zip from http:// > svn.macports.org/repository/macports/distfiles/JHymn > ---> Attempting to fetch JHymn_0_9_2_source.zip from http:// > svn.macports.org/repository/macports/distfiles/general/ > ---> Attempting to fetch JHymn_0_9_2_source.zip from http:// > svn.macports.org/repository/macports/downloads/JHymn > Error: Target org.macports.fetch returned: fetch failed > Error: Status 1 encountered during processing. The developer apparently received a cease and desist order in February 2008 and had to remove the files. http://www.hymn-project.org/forums/viewtopic.php?t=1314 We don't seem to have the files on our mirror either. http://distfiles.macports.org/JHymn/ The forum topic above seems to list some alternatives. Maybe we should remove the JHymn port. From ryandesign at macports.org Tue Jun 10 15:07:53 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 10 Jun 2008 17:07:53 -0500 Subject: Deluge install issue In-Reply-To: References: <66174D40-2CA1-4C12-BBEA-4854D4CF9827@macports.org> Message-ID: <745A83F8-0978-4460-9ED0-08055DEFDBDC@macports.org> On Jun 8, 2008, at 18:09, Joe Schnide wrote: > At 6:04 AM -0500 6/8/08, Ryan Schmidt wrote: > >> On Jun 8, 2008, at 05:46, Joe Schnide wrote: >> >>> I had no problem installing deluge on a MacBookPro but am having >>> a problem on >>> an Intel iMac. >> >> What is the difference between the MacBook Pro and the iMac? >> They're both Intel... Are the both running the same version of Mac >> OS X > > yes > >> , Xcode, > > yes > >> and MacPorts? > > yes > >> What versions? > > 10.5.3 > Xcode > schnide-iMac:~ schnide$ gcc -v > Using built-in specs. > Target: i686-apple-darwin9 > Configured with: /var/tmp/gcc/gcc-5465~16/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=i686-apple-darwin9 --with-arch=apple --with- > tune=generic --host=i686-apple-darwin9 --target=i686-apple-darwin9 > Thread model: posix > gcc version 4.0.1 (Apple Inc. build 5465) > > MacPorts 1.600 > >> Is your ports tree up to date? > > yes > >> (Use "sudo port selfupdate" to update.) Are the same versions of >> all dependencies installed? > > Certainly appear to be so. > > The Intel iMac was built as a clone of the MacBookPro so > they should be pretty close to identical. Hard to know where to start looking then. Certainly there's at least one difference between the two computers: deluge works on one and not the other. :-) I can try installing on 10.5.3 and see what happens. Don't forget to Reply All so your reply goes to the mailing list too, not just to me. From bxf4 at u.washington.edu Tue Jun 10 15:36:43 2008 From: bxf4 at u.washington.edu (Brian Flaherty) Date: Tue, 10 Jun 2008 15:36:43 -0700 Subject: Deluge install issue In-Reply-To: <745A83F8-0978-4460-9ED0-08055DEFDBDC@macports.org> References: <66174D40-2CA1-4C12-BBEA-4854D4CF9827@macports.org> <745A83F8-0978-4460-9ED0-08055DEFDBDC@macports.org> Message-ID: <20080610223643.GC2974@camus.local> > On Jun 8, 2008, at 18:09, Joe Schnide wrote: > > > > > The Intel iMac was built as a clone of the MacBookPro so > > they should be pretty close to identical. I was recently having difficulties building some ports on my MacBook Pro, but no problems building the same programs on my Mac Pro. (There were problems with the paths when building ports on the laptop.) Both machines have the same versions of Leopard, Xcode, MacPorts, etc. A difference is that when I upgraded from Tiger to Leopard on my Mac Pro, I erased and did a fresh install. On my MacBook Pro, I upgraded from Tiger to Leopard, installing over the previous OS and not deleting a lot of stuff. This past weekend, I removed the entire MacPorts tree and all the other files listed in the MacPorts Guide (and on Trac), and reinstalled MacPorts on my laptop, and I still couldn't build everything I wanted. So, I formatted the laptop hard drive, reinstalled Leopard and I haven't had any problems installing any port. I spent a fair amount of time looking to see what was going on, but could not find the cause. Maybe this issue parallels your two machines? Brian From macports at orindasoftware.com Tue Jun 10 18:05:26 2008 From: macports at orindasoftware.com (David Evans) Date: Tue, 10 Jun 2008 18:05:26 -0700 Subject: JHymn distfiles In-Reply-To: <9882DD42-504B-4982-8AC1-C6AD55B75244@macports.org> References: <9882DD42-504B-4982-8AC1-C6AD55B75244@macports.org> Message-ID: <484F24D6.6040005@orindasoftware.com> Ryan Schmidt wrote: > The developer apparently received a cease and desist order in > February 2008 and had to remove the files. > > http://www.hymn-project.org/forums/viewtopic.php?t=1314 > > We don't seem to have the files on our mirror either. > > http://distfiles.macports.org/JHymn/ > > The forum topic above seems to list some alternatives. > > Maybe we should remove the JHymn port. > > If so port hymn should probably go as well (and is equally broken) From ryandesign at macports.org Tue Jun 10 20:21:23 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 10 Jun 2008 22:21:23 -0500 Subject: Is "MacPort" a valid term? In-Reply-To: References: Message-ID: <2AF28880-1F4A-44BB-8FFA-BCE920B15FD8@macports.org> On Jun 10, 2008, at 11:43, markd at macports.org wrote: >> For a long time, I thought that when people were saying port, in this >> discussion, I thought the were referring to a port or a tcp/ip >> address. >> like localhost:80 > > Clarity is one of the reasons that in the past I frequently used > the term > "MacPorts port" (to distinguish it from FreeBSD and other port > systems), > but this is too cumbersome and inelegant when used a lot so I mostly > curtailed that. Using the term "MacPort" would make the term > clear, but > is that really a valid term in current usage? It seems we're only > comfortable with the plural form, and I think that is why we always > fall > back to the more generic "port" to express a single MacPorts port. Just like Apple doesn't want you to say "I wrote an AppleScript" (they want you to say "I wrote an AppleScript script"), I don't like hearing "I installed a MacPort" (I think "I installed a MacPorts port" is clearer). That's not to say I don't see your point too. "MacPorts port" (and "AppleScript script") is long and sounds silly. Would be neat if we could come up with a new cute term for our ports. Ruby has gems, for instance. What entities could MacPorts have? From tabithamc at gmail.com Tue Jun 10 21:28:44 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue, 10 Jun 2008 18:28:44 -1000 Subject: Output of port info --depends_xyz inconsistent (usually commas but not always) Message-ID: <7fccb3000806102128v485f6648yc1d4059b3bdcbaea@mail.gmail.com> Hello all -- I have been working on a script (written in Ruby) that takes the output of the port command-line program (as suggested by Rainer recently), and parses the output looking for either port dependencies or file dependencies (note: up until yesterday, file dependences were referred to ambiguously as "non-ports"). I notice that in almost all cases (among a collection of 450 MacPorts I use which of course is just a fragment of what's available), that the port dependencies are separated with commas, like this: $ port info --depends_lib gnome-vfs > depends_lib: port:gconf, port:dbus, port:openssl, port:libidl, > port:dbus-glib, port:libxml2, port:libiconv, port:gettext > But in what appears to be a minority of cases, the comma has been forgone like this: $ port info --depends_run gnome-vfs depends_run: port:desktop-file-utils port:gnome-mime-data port:shared-mime-info It was not difficult to adjust my Ruby parser to handle spaces instead of commas, but I'm wondering if it matters in terms of the strictness / policy as to how Portfiles should be authored and maintained? Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080610/71c912ec/attachment.htm From markd at macports.org Tue Jun 10 22:08:52 2008 From: markd at macports.org (markd at macports.org) Date: Tue, 10 Jun 2008 22:08:52 -0700 Subject: Is "MacPort" a valid term? Message-ID: >>> For a long time, I thought that when people were saying port, in this >>> discussion, I thought the were referring to a port or a tcp/ip >>> address. >>> like localhost:80 >> >> Clarity is one of the reasons that in the past I frequently used >> the term >> "MacPorts port" (to distinguish it from FreeBSD and other port >> systems), >> but this is too cumbersome and inelegant when used a lot so I mostly >> curtailed that. Using the term "MacPort" would make the term >> clear, but >> is that really a valid term in current usage? It seems we're only >> comfortable with the plural form, and I think that is why we always >> fall >> back to the more generic "port" to express a single MacPorts port. > >Just like Apple doesn't want you to say "I wrote an >AppleScript" (they want you to say "I wrote an AppleScript script"), >I don't like hearing "I installed a MacPort" (I think "I installed a >MacPorts port" is clearer). > >That's not to say I don't see your point too. "MacPorts port" (and >"AppleScript script") is long and sounds silly. Would be neat if we >could come up with a new cute term for our ports. Ruby has gems, for >instance. What entities could MacPorts have? Hmn. How about "mport" as shorthand for "MacPorts port". "MacPorts mport" would never be used, since it is redundant. Mark From krischik at users.sourceforge.net Tue Jun 10 23:15:49 2008 From: krischik at users.sourceforge.net (Martin Krischik) Date: Wed, 11 Jun 2008 08:15:49 +0200 Subject: New Wiki (Was: New Howto) In-Reply-To: References: Message-ID: <20080611081549.epht0h8ocow4wko0@server265-han.de-nserver.de> Hi, > I would say, if I had a vote (who does?), that whatever people are willing > to use wins. It may not be elegant or state of the art, but the best is the > enemy of the good, and good is usually good enough. I like to point out one more aspect: *If* we are going for a new Wiki we might as well replace the homepage as well. For a week or so there was consensus (as in: no one disagreed) that a link from the homepage to the HowTo would be helpful - yet it has not been done. Let me check .... No still not done. And we would not be the first project to go "all wiki": http://gnuada.sourceforge.net/ http://uiq3.sourceforge.net/wiki/index.php/Main_Page http://vimplugin.org/ Martin From ryandesign at macports.org Tue Jun 10 23:27:02 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 11 Jun 2008 01:27:02 -0500 Subject: Output of port info --depends_xyz inconsistent (usually commas but not always) In-Reply-To: <7fccb3000806102128v485f6648yc1d4059b3bdcbaea@mail.gmail.com> References: <7fccb3000806102128v485f6648yc1d4059b3bdcbaea@mail.gmail.com> Message-ID: <3DCF9AFD-9F0B-49F8-A8C4-64EE25EF4921@macports.org> On Jun 10, 2008, at 23:28, Tabitha McNerney wrote: > I have been working on a script (written in Ruby) that takes the > output of the port command-line program (as suggested by Rainer > recently), and parses the output looking for either port > dependencies or file dependencies (note: up until yesterday, file > dependences were referred to ambiguously as "non-ports"). I notice > that in almost all cases (among a collection of 450 MacPorts I use > which of course is just a fragment of what's available), that the > port dependencies are separated with commas, like this: > > $ port info --depends_lib gnome-vfs > depends_lib: port:gconf, port:dbus, port:openssl, port:libidl, > port:dbus-glib, port:libxml2, port:libiconv, port:gettext > > But in what appears to be a minority of cases, the comma has been > forgone like this: > > $ port info --depends_run gnome-vfs > depends_run: port:desktop-file-utils port:gnome-mime-data > port:shared-mime-info > > It was not difficult to adjust my Ruby parser to handle spaces > instead of commas, but I'm wondering if it matters in terms of the > strictness / policy as to how Portfiles should be authored and > maintained? The commas do not appear in the portfiles. It must be something added by the "port info" command. I seem to get commas always: $ port info --depends_lib gnome-vfs depends_lib: port:gconf, port:dbus, port:openssl, port:libidl, port:dbus-glib, port:libxml2, port:libiconv, port:gettext $ port info --depends_run gnome-vfs depends_run: port:desktop-file-utils, port:gnome-mime-data, port:shared-mime-info $ Are you sure you're using the latest MacPorts? From krischik at users.sourceforge.net Tue Jun 10 23:23:07 2008 From: krischik at users.sourceforge.net (Martin Krischik) Date: Wed, 11 Jun 2008 08:23:07 +0200 Subject: New Howto In-Reply-To: <02061700-00F5-4457-9EDE-3056C34DF40D@apple.com> References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> <949829840806100927x3a90e548rf8d24ffd3109c221@mail.gmail.com> <02061700-00F5-4457-9EDE-3056C34DF40D@apple.com> Message-ID: <20080611082307.3enhi0yjqsco4cwc@server265-han.de-nserver.de> Zitat von "Jordan K. Hubbard" : > Well, to be fair, I thought I was trying to address that by suggesting > that there should be a "top level doc project" - individual projects > could point up to it just as easily as it could point down to them, > but it would be a clear "docs portal" for everyone. Note that MediaWiki supports up to 256 name spaces. For example on wikibooks the cookbook runs in it's own name space: http://en.wikibooks.org/wiki/Cookbook I think it would be a good idea to have one wiki for - including the homepage. It just need a clear structure form the onset. Martin From ryandesign at macports.org Tue Jun 10 23:32:17 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 11 Jun 2008 01:32:17 -0500 Subject: New Wiki (Was: New Howto) In-Reply-To: <20080611081549.epht0h8ocow4wko0@server265-han.de-nserver.de> References: <20080611081549.epht0h8ocow4wko0@server265-han.de-nserver.de> Message-ID: On Jun 11, 2008, at 01:15, Martin Krischik wrote: >> I would say, if I had a vote (who does?), that whatever people are >> willing >> to use wins. It may not be elegant or state of the art, but the >> best is the >> enemy of the good, and good is usually good enough. > > I like to point out one more aspect: *If* we are going for a new Wiki > we might as well replace the homepage as well. For a week or so there > was consensus (as in: no one disagreed) that a link from the homepage > to the HowTo would be helpful - yet it has not been done. > > Let me check .... No still not done. > > And we would not be the first project to go "all wiki": > > http://gnuada.sourceforge.net/ > http://uiq3.sourceforge.net/wiki/index.php/Main_Page > http://vimplugin.org/ The proposed new wiki was to be a global Mac OS Forge documentation wiki, not a MacPorts-specific wiki. I'm still not a fan of the idea. Do we really want to spend the time and energy converting content from the MacPorts Trac wiki to a Mac OS Forge MediaWiki when we have more important things we could be doing? From krischik at users.sourceforge.net Wed Jun 11 01:18:20 2008 From: krischik at users.sourceforge.net (Martin Krischik) Date: Wed, 11 Jun 2008 10:18:20 +0200 Subject: New Wiki (Was: New Howto) In-Reply-To: References: <20080611081549.epht0h8ocow4wko0@server265-han.de-nserver.de> Message-ID: <20080611101820.0zw4j1x6o4w4kg8g@server265-han.de-nserver.de> Zitat von Ryan Schmidt : > On Jun 11, 2008, at 01:15, Martin Krischik wrote: > >>> I would say, if I had a vote (who does?), that whatever people are willing >>> to use wins. It may not be elegant or state of the art, but the best is the >>> enemy of the good, and good is usually good enough. >> >> I like to point out one more aspect: *If* we are going for a new Wiki >> we might as well replace the homepage as well. For a week or so there >> was consensus (as in: no one disagreed) that a link from the homepage >> to the HowTo would be helpful - yet it has not been done. >> >> Let me check .... No still not done. >> >> And we would not be the first project to go "all wiki": >> >> http://gnuada.sourceforge.net/ >> http://uiq3.sourceforge.net/wiki/index.php/Main_Page >> http://vimplugin.org/ > > The proposed new wiki was to be a global Mac OS Forge documentation > wiki, not a MacPorts-specific wiki. I'm still not a fan of the idea. Do > we really want to spend the time and energy converting content from the > MacPorts Trac wiki to a Mac OS Forge MediaWiki when we have more > important things we could be doing? I don't know either - but if we do I propose we replace the home pages (and macports guide) as well. Note that a quick check shows that Bonjour, BridgeSupport, CalendarServer, MacRuby etc. use the track wiki as home page. *If* we go thue the trouble of installing media wiki - or any other large scale wiki - then we might as well use it for the homepage and the guide as well. But note the *if* - maybe the track wiki is enough after all - in which case I suggest we move at least the guide to track wiki as well to have more in one place. From my quick check I also noted that MacPorts clearly is the largest Project on MacOS Forge ao we might as well take the lead. Martin From randall.h.wood at alexandriasoftware.com Wed Jun 11 02:20:29 2008 From: randall.h.wood at alexandriasoftware.com (Randall Wood) Date: Wed, 11 Jun 2008 05:20:29 -0400 Subject: New Wiki (Was: New Howto) In-Reply-To: <20080611101820.0zw4j1x6o4w4kg8g@server265-han.de-nserver.de> References: <20080611081549.epht0h8ocow4wko0@server265-han.de-nserver.de> <20080611101820.0zw4j1x6o4w4kg8g@server265-han.de-nserver.de> Message-ID: On Wed, Jun 11, 2008 at 4:18 AM, Martin Krischik wrote: > Zitat von Ryan Schmidt : > >> On Jun 11, 2008, at 01:15, Martin Krischik wrote: >> >>>> I would say, if I had a vote (who does?), that whatever people are willing >>>> to use wins. It may not be elegant or state of the art, but the best is the >>>> enemy of the good, and good is usually good enough. >>> >>> I like to point out one more aspect: *If* we are going for a new Wiki >>> we might as well replace the homepage as well. For a week or so there >>> was consensus (as in: no one disagreed) that a link from the homepage >>> to the HowTo would be helpful - yet it has not been done. >>> >>> Let me check .... No still not done. >>> >>> And we would not be the first project to go "all wiki": >>> >>> http://gnuada.sourceforge.net/ >>> http://uiq3.sourceforge.net/wiki/index.php/Main_Page >>> http://vimplugin.org/ I don't know of any large project to go all wiki. Even wikimedia/wikipedia has locked down much of its wiki in the same way that www.macports.org is locked down against random edits of anyone. >> >> The proposed new wiki was to be a global Mac OS Forge documentation >> wiki, not a MacPorts-specific wiki. I'm still not a fan of the idea. Do >> we really want to spend the time and energy converting content from the >> MacPorts Trac wiki to a Mac OS Forge MediaWiki when we have more >> important things we could be doing? Does anyone remember when MacPorts and Fink used the same mediawiki instance for their wiki? Namespaces, interlinking, and searches were fun as one project would get the nice page name or search results would kick you from one project to the other...it was not nice, to say the least. > I don't know either - but if we do I propose we replace the home pages > (and macports guide) as well. We should not replace these. We can improve them and change the workflow that controls them, but I do not like the idea of replacing (relatively) static and controlled information sources with a completely open one. > Note that a quick check shows that Bonjour, BridgeSupport, CalendarServer, > MacRuby etc. use the track wiki as home page. > > *If* we go thue the trouble of installing media wiki - or any other > large scale wiki - then we might as well use it for the homepage and > the guide as well. > > But note the *if* - maybe the track wiki is enough after all - in > which case I suggest we move at least the guide to track wiki as well > to have more in one place. The trac wiki has a couple of major advantages over other wikis, particularly for our project: integrated ticketing and svn browsing. If we cut off part of trac, we need to loose it all, and that means also standing up bugzilla, and using viewcvs (which is just ugly after trac) and none of these are integrated, and ...wait... we've returned to the old opendarwin.org infrastructure, and all of its maintenance headaches (it was essentially abandoned because of the amount of maintenance work involved). > From my quick check I also noted that MacPorts clearly is the largest > Project on MacOS Forge ao we might as well take the lead. > > Martin > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -- Randall Wood randall.h.wood at alexandriasoftware.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." From ryandesign at macports.org Wed Jun 11 03:39:47 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 11 Jun 2008 05:39:47 -0500 Subject: FreeTDS In-Reply-To: References: Message-ID: On Jun 2, 2008, at 04:28, Ryan Schmidt wrote: > On Jun 2, 2008, at 01:03, Nathan Brazil wrote: > >> Hi. I see that FreeTDS has no maintainer. The latest portfile >> lists it at version 0.64, while the latest version at http:// >> freetds.org is 0.82. >> >> I have updated and attached the portfile. I installed the port >> with the +mssql variant, and it works on these systems against SQL >> Server 2005: >> >> - PowerPC G4 running latest version of Tiger >> - Intel-based Mac running 10.5.2 >> >> I don't have commit access. Can someone help me commit the updated >> portfile? > > I'll work on this tomorrow. There are a few things I want to change > and check on before I commit. In the future you can file tickets in > our issue tracker. Would you like to be the maintainer of the freetds > port? Sorry, "tomorrow" didn't quite happen, but someone else filed a ticket on this so work will continue there: http://trac.macports.org/ticket/15574 From tabithamc at gmail.com Wed Jun 11 03:53:45 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Wed, 11 Jun 2008 00:53:45 -1000 Subject: Output of port info --depends_xyz inconsistent (usually commas but not always) In-Reply-To: <3DCF9AFD-9F0B-49F8-A8C4-64EE25EF4921@macports.org> References: <7fccb3000806102128v485f6648yc1d4059b3bdcbaea@mail.gmail.com> <3DCF9AFD-9F0B-49F8-A8C4-64EE25EF4921@macports.org> Message-ID: <7fccb3000806110353g22e68c25xda3ca520a101e960@mail.gmail.com> On Tue, Jun 10, 2008 at 8:27 PM, Ryan Schmidt wrote: > > On Jun 10, 2008, at 23:28, Tabitha McNerney wrote: > > I have been working on a script (written in Ruby) that takes the output of >> the port command-line program (as suggested by Rainer recently), and parses >> the output looking for either port dependencies or file dependencies (note: >> up until yesterday, file dependences were referred to ambiguously as >> "non-ports"). I notice that in almost all cases (among a collection of 450 >> MacPorts I use which of course is just a fragment of what's available), that >> the port dependencies are separated with commas, like this: >> >> $ port info --depends_lib gnome-vfs >> depends_lib: port:gconf, port:dbus, port:openssl, port:libidl, >> port:dbus-glib, port:libxml2, port:libiconv, port:gettext >> >> But in what appears to be a minority of cases, the comma has been forgone >> like this: >> >> $ port info --depends_run gnome-vfs >> depends_run: port:desktop-file-utils port:gnome-mime-data >> port:shared-mime-info >> >> It was not difficult to adjust my Ruby parser to handle spaces instead of >> commas, but I'm wondering if it matters in terms of the strictness / policy >> as to how Portfiles should be authored and maintained? >> > > The commas do not appear in the portfiles. It must be something added by > the "port info" command. > > I seem to get commas always: > > $ port info --depends_lib gnome-vfs > depends_lib: port:gconf, port:dbus, port:openssl, port:libidl, > port:dbus-glib, port:libxml2, port:libiconv, port:gettext > $ port info --depends_run gnome-vfs > depends_run: port:desktop-file-utils, port:gnome-mime-data, > port:shared-mime-info > $ > > Are you sure you're using the latest MacPorts? 1.6.0 right? T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080611/fdf977f7/attachment.htm From ryandesign at macports.org Wed Jun 11 04:00:43 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 11 Jun 2008 06:00:43 -0500 Subject: Output of port info --depends_xyz inconsistent (usually commas but not always) In-Reply-To: <7fccb3000806110353g22e68c25xda3ca520a101e960@mail.gmail.com> References: <7fccb3000806102128v485f6648yc1d4059b3bdcbaea@mail.gmail.com> <3DCF9AFD-9F0B-49F8-A8C4-64EE25EF4921@macports.org> <7fccb3000806110353g22e68c25xda3ca520a101e960@mail.gmail.com> Message-ID: <0E6050D2-5283-463F-929D-79115D3DB735@macports.org> On Jun 11, 2008, at 05:53, Tabitha McNerney wrote: >> I seem to get commas always: >> >> >> $ port info --depends_lib gnome-vfs >> depends_lib: port:gconf, port:dbus, port:openssl, port:libidl, >> port:dbus-glib, port:libxml2, port:libiconv, port:gettext >> $ port info --depends_run gnome-vfs >> depends_run: port:desktop-file-utils, port:gnome-mime-data, >> port:shared-mime-info >> $ >> >> Are you sure you're using the latest MacPorts? > > 1.6.0 right? Oh, I thought for some reason this "port info --depends_foo" stuff had been added more recently than 1.6.0 and that you were running the latest version from trunk, as I am. So if the problem exists in 1.6.0, then it has already been fixed and that fix will be in the next release. From raimue at macports.org Wed Jun 11 10:02:47 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Wed, 11 Jun 2008 19:02:47 +0200 Subject: Output of port info --depends_xyz inconsistent (usually commas but not always) In-Reply-To: <0E6050D2-5283-463F-929D-79115D3DB735@macports.org> References: <7fccb3000806102128v485f6648yc1d4059b3bdcbaea@mail.gmail.com> <3DCF9AFD-9F0B-49F8-A8C4-64EE25EF4921@macports.org> <7fccb3000806110353g22e68c25xda3ca520a101e960@mail.gmail.com> <0E6050D2-5283-463F-929D-79115D3DB735@macports.org> Message-ID: <48500537.3030706@macports.org> Ryan Schmidt wrote: >>> Are you sure you're using the latest MacPorts? >> 1.6.0 right? > > Oh, I thought for some reason this "port info --depends_foo" stuff > had been added more recently than 1.6.0 and that you were running the > latest version from trunk, as I am. So if the problem exists in > 1.6.0, then it has already been fixed and that fix will be in the > next release. depends_run was broken. This was fixed in r32725 by eridius and merged back to release_1_6 in r33045 by jmpp. Rainer From raimue at macports.org Wed Jun 11 10:33:29 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Wed, 11 Jun 2008 19:33:29 +0200 Subject: Is "MacPort" a valid term? In-Reply-To: References: Message-ID: <48500C69.10805@macports.org> markd at macports.org wrote: >> That's not to say I don't see your point too. "MacPorts port" (and >> "AppleScript script") is long and sounds silly. Would be neat if we >> could come up with a new cute term for our ports. Ruby has gems, for >> instance. What entities could MacPorts have? > > Hmn. How about "mport" as shorthand for "MacPorts port". "MacPorts > mport" would never be used, since it is redundant. I dislike 'MacPort', but I like the term 'mport'. 'mport' is already used in the source and API as a reference for MacPorts (mportinit, mportopen, etc). But this should not stop us from using the term as an alternative to 'MacPorts port'. Rainer From rrebhuhnglanz at gmail.com Wed Jun 11 10:56:50 2008 From: rrebhuhnglanz at gmail.com (Rebecca Rebhuhn-Glanz) Date: Wed, 11 Jun 2008 13:56:50 -0400 Subject: gnome-sharp2 problems Message-ID: <788b0da90806111056t166159d3ydb280bea6eaef35f@mail.gmail.com> Hi, I'm trying to install gnome-sharp2 and am getting the following error message when I use 'sudo port install gnome-sharp2': *configure: error: Package requirements (render >= 0.9) were not met. Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively you may set the RENDER_CFLAGS and RENDER_LIBS environment variables to avoid the need to call pkg-config. See the pkg-config man page for more details.* I'm fairly new to command line and I have no idea how to do this. I did install render using MacPorts, but still got the same error. Thanks, Rebecca R.G. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080611/0dd9bee8/attachment.htm From jkh at apple.com Wed Jun 11 11:02:11 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Wed, 11 Jun 2008 11:02:11 -0700 Subject: New Howto In-Reply-To: <20080611082307.3enhi0yjqsco4cwc@server265-han.de-nserver.de> References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> <949829840806100927x3a90e548rf8d24ffd3109c221@mail.gmail.com> <02061700-00F5-4457-9EDE-3056C34DF40D@apple.com> <20080611082307.3enhi0yjqsco4cwc@server265-han.de-nserver.de> Message-ID: <2E075881-4E63-4B55-AF3F-303EEC73E396@apple.com> On Jun 10, 2008, at 11:23 PM, Martin Krischik wrote: > Note that MediaWiki supports up to 256 name spaces. For example on > wikibooks the cookbook runs in it's own name space: > > http://en.wikibooks.org/wiki/Cookbook > > I think it would be a good idea to have one wiki for - including the > homepage. It just need a clear structure form the onset. That's a bit more ambitious than what I had in mind, at least at the very start, but I think that's a fine goal. Why don't we do this: Why don't we get MediaWiki up on the MacOSForge cluster and start experimenting with it? If we don't like it, we certainly don't have to use it, but we should have options. I've used trac to edit various things on MacOSForge and cannot consider myself a fan of it given how it makes a number of things which should be simple and obvious, well, rather less so. I've also added entries to wikipedia, or edited existing ones, and found that to be a very straight-forward and relatively intuitive process by comparison. - Jordan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080611/b91fe14b/attachment.htm From jkh at apple.com Wed Jun 11 11:06:08 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Wed, 11 Jun 2008 11:06:08 -0700 Subject: New Wiki (Was: New Howto) In-Reply-To: References: <20080611081549.epht0h8ocow4wko0@server265-han.de-nserver.de> Message-ID: <76EB63AB-AD49-4743-9C93-A03F8E0DFF1F@apple.com> On Jun 10, 2008, at 11:32 PM, Ryan Schmidt wrote: > The proposed new wiki was to be a global Mac OS Forge documentation > wiki, not a MacPorts-specific wiki. I'm still not a fan of the idea. > Do we really want to spend the time and energy converting content > from the MacPorts Trac wiki to a Mac OS Forge MediaWiki when we have > more important things we could be doing? I think that's something of a straw man argument, Ryan. First off, if the conversion chore is genuinely distasteful then you can always elect not to do it but simply point others who ARE willing at your raw material and say "if you want to pretty that up and convert it, be our guest!" If the end result ends up looking a lot nicer, or is easier to find, you then simply change which one is now "live" and deprecate the other, either quickly or over time. Second, there just aren't that many howtos right now, at least not in comparison to what could be, and if there's a time to bear any conversion cost then that time is now, not later after there are dozens of the things. I think a simple evaluation, as I just proposed to Martin, is a reasonable next step at this point. How are you sure you're using the best tool for the job if you haven't even tried other alternatives? - Jordan From jkh at apple.com Wed Jun 11 11:08:04 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Wed, 11 Jun 2008 11:08:04 -0700 Subject: New Wiki (Was: New Howto) In-Reply-To: <20080611101820.0zw4j1x6o4w4kg8g@server265-han.de-nserver.de> References: <20080611081549.epht0h8ocow4wko0@server265-han.de-nserver.de> <20080611101820.0zw4j1x6o4w4kg8g@server265-han.de-nserver.de> Message-ID: <970A1A42-9474-480C-B6F2-6D20D9EDCC72@apple.com> On Jun 11, 2008, at 1:18 AM, Martin Krischik wrote: > From my quick check I also noted that MacPorts clearly is the largest > Project on MacOS Forge ao we might as well take the lead. Actually, I believe that honor goes to WebKit. :-) It would be nice to have some pageview stats to back that up, of course. I'll see about some sort of macosforge-wide project status page. - Jordan From jkh at apple.com Wed Jun 11 11:22:29 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Wed, 11 Jun 2008 11:22:29 -0700 Subject: Is "MacPort" a valid term? In-Reply-To: <48500C69.10805@macports.org> References: <48500C69.10805@macports.org> Message-ID: On Jun 11, 2008, at 10:33 AM, Rainer M?ller wrote: > I dislike 'MacPort', but I like the term 'mport'. I dunno, that just doesn't seem to roll off the tongue and also suffers from excessive contraction at the wrong place. If, for example, you were trying to come up with a more convenient way of distinguishing "pickup truck" from "semi tractor trailer truck" then it's just not human nature (at least not anywhere I know of) to call one a ptruck and the other an struck. Here in the US, for example, we call one a pickup and the other a semi, and people have no trouble with those contractions. I don't know what you folks in Germany call pickups since I hardly ever saw any there, but the latter are called LKVs (short for "Leistungskraftwagen", one of German's shorter words :)) which is also a fine abbreviation (the germans pronounce it as "ell-kah-veh which, if you say it quickly, is a rather pronounceable nice word of its own) and also kind of supports my point. Mmm-port is how you'd pronounce mport in english, and I don't think that's very phonetically pleasing. I'd almost prefer to call it a McPort and wait to see if the McDonalds people complain (I kind of doubt they will, that ship already sailed when the term "McMansion" became popular in the US for describing overly large new houses built by the newly wealthy). - Jordan From randall.h.wood at alexandriasoftware.com Wed Jun 11 11:56:08 2008 From: randall.h.wood at alexandriasoftware.com (Randall Wood) Date: Wed, 11 Jun 2008 14:56:08 -0400 Subject: Fwd: New Howto In-Reply-To: References: <949829840806050842n6a2ea1d1gc0e77f707bc8058d@mail.gmail.com> <949829840806100927x3a90e548rf8d24ffd3109c221@mail.gmail.com> <02061700-00F5-4457-9EDE-3056C34DF40D@apple.com> <20080611082307.3enhi0yjqsco4cwc@server265-han.de-nserver.de> <2E075881-4E63-4B55-AF3F-303EEC73E396@apple.com> Message-ID: Failed to send to list... ---------- Forwarded message ---------- From: Randall Wood Date: Wed, Jun 11, 2008 at 2:55 PM Subject: Re: New Howto To: "Jordan K. Hubbard" On Wed, Jun 11, 2008 at 2:02 PM, Jordan K. Hubbard wrote: > > On Jun 10, 2008, at 11:23 PM, Martin Krischik wrote: > > Note that MediaWiki supports up to 256 name spaces. For example on > wikibooks the cookbook runs in it's own name space: > > http://en.wikibooks.org/wiki/Cookbook > > I think it would be a good idea to have one wiki for - including the > homepage. It just need a clear structure form the onset. > > That's a bit more ambitious than what I had in mind, at least at the very > start, but I think that's a fine goal. > Why don't we do this: Why don't we get MediaWiki up on the MacOSForge > cluster and start experimenting with it? If we don't like it, we certainly > don't have to use it, but we should have options. I've used trac to edit > various things on MacOSForge and cannot consider myself a fan of it given > how it makes a number of things which should be simple and obvious, well, > rather less so. I've also added entries to wikipedia, or edited existing > ones, and found that to be a very straight-forward and relatively intuitive > process by comparison. I'll ask this instead: Why not simply get our trac site looking like we want it, instead of having it in the hideous MacOSForge theme? Webkit is using the MacOSForge trac without all the MacOSForge stuff on it and with its own theme. We could do the same thing. I'm not aware that we have tried. I'll also give you a reason not to stand up MediaWiki on MacOSForge: It will lead to multiple wiki syntaxes in MacPorts unless we abandon trac for SVN browsing and ticketing. And I really don't want to see that. viewcvs sucks as an SVN browsers, and MediaWiki/Bugzilla/SVN have no real integration between each other. We'll loose the integration that trac brings and it is valuable. > > - Jordan > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > -- Randall Wood randall.h.wood at alexandriasoftware.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." -- Randall Wood randall.h.wood at alexandriasoftware.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." From paulbeard at gmail.com Wed Jun 11 12:49:31 2008 From: paulbeard at gmail.com (paul beard) Date: Wed, 11 Jun 2008 12:49:31 -0700 Subject: New wiki Message-ID: Hmm, is it about time for the Bike Shed link to be cited? As a non-committer who has used MacPorts since it was DarwinPorts and used Fink before that, here's my two shiny bits of something or other. I wasn't aware there was large body of documentation to be migrated, so the argument that a new syntax has to be mastered isn't all that strong. As to whether or not this is the most important issue, that is up to each person who uses this project. No one is suggesting that port hacking stop so that documentation can be re-written. What I suspect will happen, if an accessible format is chosen, is that more contributors will appear to do that work. I considered doing some docs for DarwinPorts and FreeBSD but the work was to be done in docbook, if memory serves, and that just didn't work for me. I didn't want to learn a text formatting system just to document how to use a port management system. If you want to examine prioritization, there's an example: how much of a volunteer's scarce attention do you want applied to productive work vs learning a toolset? Perhaps in the review of page views/status, we could find out how many people use the docs in place and how many use TRAC as a resource. I wasn't aware of it as documentation repository so much as a ticket manager, and I have not seen a lot of wiki syntax/formatting beyond using the {{{ }}} markup to denote code or fixed-width output. I agree that the best way to see if this is a good idea is to try it. As often as useage tips appear on this list, it would make a lot of sense to put them all in one place. Maybe some docs on how to build from the MacPorts trunk, so we can access all the bug fixes to 1.6, would be a good place to start? -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080611/830e05c3/attachment.htm From kykim_lists at mac.com Wed Jun 11 12:52:44 2008 From: kykim_lists at mac.com (kykim_lists at mac.com) Date: Wed, 11 Jun 2008 12:52:44 -0700 Subject: local port tries to download patch files Message-ID: <5B83FA78-011A-1000-8219-A62A37E315B6-Webmail-10016@mac.com> Hi all, I'm trying to make a new Portfile (for the ruby GeoIP module). And I've set up a local ports repository. Inside my local port repository, I've set up a directory with the "Portfile" and a "files" directory that contains patch files. It looks good when I run a "portindex" command. However, everytime I try to run a "port install " it tries to download the patch files from the macports repository. How can I get it so it doesn't try to download the patch files? Thanks, -kevin From blb at macports.org Wed Jun 11 14:34:25 2008 From: blb at macports.org (Bryan Blackburn) Date: Wed, 11 Jun 2008 15:34:25 -0600 Subject: New wiki In-Reply-To: References: Message-ID: On Jun 11, 2008, at 1:49 PM, paul beard wrote: > ... > Maybe some docs on how to build from the MacPorts trunk, so we can > access all the bug fixes to 1.6, would be a good place to start? > You mean something like The howto page at has seen some recent improvements, so have a quick look at least. I think this definitely reinforces the point that it should probably have a prominent link at www.macports.org. Bryan > > -- > Paul Beard / www.paulbeard.org/ > From jmr at macports.org Wed Jun 11 15:30:00 2008 From: jmr at macports.org (Joshua Root) Date: Thu, 12 Jun 2008 08:30:00 +1000 Subject: Is "MacPort" a valid term? In-Reply-To: References: <48500C69.10805@macports.org> Message-ID: <485051E8.6010501@macports.org> Jordan K. Hubbard wrote: > Mmm-port is how you'd pronounce mport in english, and I don't think > that's very phonetically pleasing. I've always mentally pronounced it as "emport", with the accent on the first syllable, which isn't too bad. - Josh From ryandesign at macports.org Wed Jun 11 15:45:20 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 11 Jun 2008 17:45:20 -0500 Subject: Is "MacPort" a valid term? In-Reply-To: <48502D3A.6060903@rppass.com> References: <2AF28880-1F4A-44BB-8FFA-BCE920B15FD8@macports.org> <48502D3A.6060903@rppass.com> Message-ID: <51CB4A25-8826-4309-A05A-5B1358FC059D@macports.org> On Jun 11, 2008, at 14:53, Ralph Pass wrote: > Ryan Schmidt wrote: > >> On Jun 10, 2008, at 11:43, markd at macports.org wrote: >> >>>> For a long time, I thought that when people were saying port, in >>>> this discussion, I thought the were referring to a port or a tcp/ >>>> ip address. like localhost:80 >>> >>> Clarity is one of the reasons that in the past I frequently used >>> the term "MacPorts port" (to distinguish it from FreeBSD and >>> other port systems), but this is too cumbersome and inelegant >>> when used a lot so I mostly curtailed that. Using the term >>> "MacPort" would make the term clear, but is that really a valid >>> term in current usage? It seems we're only comfortable with the >>> plural form, and I think that is why we always fall back to the >>> more generic "port" to express a single MacPorts port. >> >> Just like Apple doesn't want you to say "I wrote an >> AppleScript" (they want you to say "I wrote an AppleScript >> script"), I don't like hearing "I installed a MacPort" (I think "I >> installed a MacPorts port" is clearer). That's not to say I don't >> see your point too. "MacPorts port" (and "AppleScript script") is >> long and sounds silly. Would be neat if we could come up with a >> new cute term for our ports. Ruby has gems, for instance. What >> entities could MacPorts have? > > What entities could MacPorts have? macboats? > macships? > maccanoes? > macdocks? > macpallets? > macboxes? > maccrates? > > > :-))) I just knew this was coming. :) Pardon my forwarding this to the list, it's too funny. Of course, "Pallet" is one of the MacPorts GUIs: http://trac.macports.org/browser/users/rhwood/Pallet From ryandesign at macports.org Wed Jun 11 15:46:41 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 11 Jun 2008 17:46:41 -0500 Subject: local port tries to download patch files In-Reply-To: <5B83FA78-011A-1000-8219-A62A37E315B6-Webmail-10016@mac.com> References: <5B83FA78-011A-1000-8219-A62A37E315B6-Webmail-10016@mac.com> Message-ID: <490BD1BE-75AD-421C-A6E7-7541092FC522@macports.org> On Jun 11, 2008, at 14:52, kykim_lists at mac.com wrote: > I'm trying to make a new Portfile (for the ruby GeoIP module). > And I've set up a local ports repository. > > Inside my local port repository, I've set up a directory > with the "Portfile" and a "files" directory that contains > patch files. It looks good when I run a "portindex" command. > > However, everytime I try to run a "port install " > it tries to download the patch files from the macports > repository. > > How can I get it so it doesn't try to download the patch files? It should use the patchfiles in the files directory, if they truly have the same names (including extensions) that you've typed into the patchfiles line in the Portfile. From ryandesign at macports.org Wed Jun 11 15:49:13 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 11 Jun 2008 17:49:13 -0500 Subject: Is "MacPort" a valid term? In-Reply-To: <485051E8.6010501@macports.org> References: <48500C69.10805@macports.org> <485051E8.6010501@macports.org> Message-ID: <1DE4C842-0F1B-458C-839B-57488976DCDE@macports.org> On Jun 11, 2008, at 17:30, Joshua Root wrote: > Jordan K. Hubbard wrote: > >> Mmm-port is how you'd pronounce mport in english, and I don't think >> that's very phonetically pleasing. > > I've always mentally pronounced it as "emport", with the accent on the > first syllable, which isn't too bad. That can be our new verb. "I need to emport that new software." A noble spirit embiggens the smallest man... From jkh at apple.com Wed Jun 11 22:40:32 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Wed, 11 Jun 2008 22:40:32 -0700 Subject: Is "MacPort" a valid term? In-Reply-To: <1DE4C842-0F1B-458C-839B-57488976DCDE@macports.org> References: <48500C69.10805@macports.org> <485051E8.6010501@macports.org> <1DE4C842-0F1B-458C-839B-57488976DCDE@macports.org> Message-ID: On Jun 11, 2008, at 3:49 PM, Ryan Schmidt wrote: > That can be our new verb. "I need to emport that new software." > > A noble spirit embiggens the smallest man... OK, consider my mind changed in just 2 lines. :-) - Jordan From markd at macports.org Wed Jun 11 23:51:18 2008 From: markd at macports.org (markd at macports.org) Date: Wed, 11 Jun 2008 23:51:18 -0700 Subject: Is "MacPort" a valid term? Message-ID: >> I dislike 'MacPort', but I like the term 'mport'. > >I dunno, that just doesn't seem to roll off the tongue and also >suffers from excessive contraction at the wrong place. If, for >example, you were trying to come up with a more convenient way of >distinguishing "pickup truck" from "semi tractor trailer truck" then >it's just not human nature (at least not anywhere I know of) to call >one a ptruck and the other an struck. Here in the US, for example, we >call one a pickup and the other a semi, and people have no trouble >with those contractions. So are you saying that you think "MacPort" is a valid term? I was thinking it wasn't an accepted and/or used term. If folks think it is, I can stop flipping between using "MacPorts port" (mostly in intro parts) and "port" in the docs. It's not a really big deal though, except just to settle if the term "MacPort" is considered invalid usage or not. Mark From randall.h.wood at alexandriasoftware.com Thu Jun 12 01:40:12 2008 From: randall.h.wood at alexandriasoftware.com (Randall Wood) Date: Thu, 12 Jun 2008 04:40:12 -0400 Subject: ThisApp? In-Reply-To: References: Message-ID: The distributors of this application have received a "Cease and Desist" order preventing distribution and so its no longer available. I'll patch the Portfile... Should this port simply be removed from tree? On Tue, Jun 10, 2008 at 4:59 PM, Mack Johnson wrote: > This port is no longer? > ---> Attempting to fetch JHymn_0_9_2_source.zip from http://www.hymn-project.org/download/ > ---> Attempting to fetch JHymn_0_9_2_source.zip from http://svn.macports.org/repository/macports/distfiles/JHymn > ---> Attempting to fetch JHymn_0_9_2_source.zip from http://svn.macports.org/repository/macports/distfiles/general/ > ---> Attempting to fetch JHymn_0_9_2_source.zip from http://svn.macports.org/repository/macports/downloads/JHymn > Error: Target org.macports.fetch returned: fetch failed > Error: Status 1 encountered during processing. > > > > Mack > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -- Randall Wood randall.h.wood at alexandriasoftware.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." From randall.h.wood at alexandriasoftware.com Thu Jun 12 02:13:34 2008 From: randall.h.wood at alexandriasoftware.com (Randall Wood) Date: Thu, 12 Jun 2008 05:13:34 -0400 Subject: JHymn distfiles (was: Re: ThisApp?) In-Reply-To: <9882DD42-504B-4982-8AC1-C6AD55B75244@macports.org> References: <9882DD42-504B-4982-8AC1-C6AD55B75244@macports.org> Message-ID: In r37540, I added a pre-fetch error message about this. However, I think this port should be removed. Comments? On Tue, Jun 10, 2008 at 5:30 PM, Ryan Schmidt wrote: > > On Jun 10, 2008, at 15:59, Mack Johnson wrote: > >> This port is no longer? >> ---> Attempting to fetch JHymn_0_9_2_source.zip from http:// >> www.hymn-project.org/download/ >> ---> Attempting to fetch JHymn_0_9_2_source.zip from http:// >> svn.macports.org/repository/macports/distfiles/JHymn >> ---> Attempting to fetch JHymn_0_9_2_source.zip from http:// >> svn.macports.org/repository/macports/distfiles/general/ >> ---> Attempting to fetch JHymn_0_9_2_source.zip from http:// >> svn.macports.org/repository/macports/downloads/JHymn >> Error: Target org.macports.fetch returned: fetch failed >> Error: Status 1 encountered during processing. > > The developer apparently received a cease and desist order in > February 2008 and had to remove the files. > > http://www.hymn-project.org/forums/viewtopic.php?t=1314 > > We don't seem to have the files on our mirror either. > > http://distfiles.macports.org/JHymn/ > > The forum topic above seems to list some alternatives. > > Maybe we should remove the JHymn port. > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -- Randall Wood randall.h.wood at alexandriasoftware.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." From frstan at bellsouth.net Thu Jun 12 06:35:50 2008 From: frstan at bellsouth.net (William Davis) Date: Thu, 12 Jun 2008 09:35:50 -0400 Subject: Is "MacPort" a valid term? In-Reply-To: References: <48500C69.10805@macports.org> Message-ID: On Jun 11, 2008, at 2:22 PM, Jordan K. Hubbard wrote: > > Mmm-port is how you'd pronounce mport in english, and I don't think > that's very phonetically pleasing. I'd almost prefer to call it a > McPort and wait to see if the McDonalds people complain (I kind of > doubt they will, that ship already sailed when the term "McMansion" > became popular in the US for describing overly large new houses built > by the newly wealthy). > > - Jordan McPort! -- gotta luv that! ;) William Davis frstanATbellsouthDOTnet Mac OS X.5.3 Darwin 9.3.0 Xquartz 2.2.1 - (xorg-server 1.3.0-apple20) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From yvon.thoraval at gmail.com Thu Jun 12 07:43:00 2008 From: yvon.thoraval at gmail.com (Yvon Thoraval) Date: Thu, 12 Jun 2008 16:43:00 +0200 Subject: Activating git-core 1.5.3.1_0 failed: Message-ID: Hey all, i wanted to upgrade git-core by: $ sudo port upgrade git-core and get : ---> Activating git-core 1.5.3.1_0+doc Error: Activating git-core 1.5.3.1_0 failed: Image error: Another version of this port (git-core @1.5.0.5_0) is already active. the I deactivated it : $ sudo port deactivate git-core ---> Deactivating git-core and re-upgraded it : $ sudo port upgrade git-core ---> Activating git-core 1.5.3.1_0+doc Error: Activating git-core 1.5.3.1_0 failed: Image error: /opt/local/lib/perl5/5.8.8/darwin-2level/perllocal.pod already exists and does not belong to a registered port. Unable to activate port git-core. i never touch at the Perl under /opt, then i wonder what's going wrong and how to get "/perllocal.pod" regsitered and/or git-core upgraded ? best, -- yvon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080612/488954b3/attachment.htm From jkh at apple.com Thu Jun 12 10:43:22 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Thu, 12 Jun 2008 10:43:22 -0700 Subject: Is "MacPort" a valid term? In-Reply-To: References: Message-ID: <87BCE6D9-288A-4179-8812-2383DDF8B828@apple.com> On Jun 11, 2008, at 11:51 PM, markd at macports.org wrote: > So are you saying that you think "MacPort" is a valid term? I was > thinking it wasn't an accepted and/or used term. If folks think it > is, I > can stop flipping between using "MacPorts port" (mostly in intro > parts) > and "port" in the docs. It's not a really big deal though, except > just to > settle if the term "MacPort" is considered invalid usage or not. I'm not saying it's invalid, how about that? :-) Ultimately, I think it's like a nickname. You generally don't get to pick your own nickname and, whether you like it or not, once you have one it sticks to you like glue for the rest of your life. We're still just in that awkward phase where nobody has found a nickname that really applies to the extent where everyone goes "Yes! That's it!" and then continues to use that name regardless of what the Powers That Be attempt to call it. - Jordan From ryandesign at macports.org Thu Jun 12 12:01:08 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 12 Jun 2008 14:01:08 -0500 Subject: Activating git-core 1.5.3.1_0 failed: In-Reply-To: References: Message-ID: On Jun 12, 2008, at 09:43, Yvon Thoraval wrote: > i wanted to upgrade git-core by: > > $ sudo port upgrade git-core > > and get : > ---> Activating git-core 1.5.3.1_0+doc > Error: Activating git-core 1.5.3.1_0 failed: Image error: Another > version of this port (git-core @1.5.0.5_0) is already active. > > the I deactivated it : > > $ sudo port deactivate git-core > ---> Deactivating git-core > > and re-upgraded it : > > $ sudo port upgrade git-core > ---> Activating git-core 1.5.3.1_0+doc > Error: Activating git-core 1.5.3.1_0 failed: Image error: /opt/ > local/lib/perl5/5.8.8/darwin-2level/perllocal.pod already exists > and does not belong to a registered port. Unable to activate port > git-core. > > i never touch at the Perl under /opt, then i wonder what's going > wrong and how to get "/perllocal.pod" regsitered and/or git-core > upgraded ? Hi! No port should claim ownership of perllocal.pod. Any port that does needs to be fixed. git-core stopped claiming ownership of perllocal.pod in r34462 (2008-02-25) so you should update your ports ("sudo port selfupdate"), clean git-core ("sudo port clean --work git-core") and try upgrading it again ("sudo port upgrade git-core"). From alan at batie.org Thu Jun 12 13:52:56 2008 From: alan at batie.org (Alan Batie) Date: Thu, 12 Jun 2008 13:52:56 -0700 Subject: upgrades fail after leopard update Message-ID: <48518CA8.2080103@batie.org> I just got around to upgrading my work machine to leopard. The first problem I ran into was that apparently I had a really old xcode installed, so none of the old ported binaries would run (something about an old threading model no longer supported apparently). I upgraded that and did the self update, which appeared to work, but "port upgrade" still fails. I finally did a "port install dovecot" trying to get my mail going again, which worked, until I tried to start it, at which time "daemondo" failed to run. Apparently even though I did "self update" it didn't. I downloaded installed macports 1.6.0, which fixed *that* finally, but the "port upgrade installed" still fails: [163] # port upgrade installed ---> Configuring xorg-util-macros 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_x11_xorg-util-macros/work/util-macros-1.1.5" && ./configure --prefix=/opt/local " returned error 1 Command output: sh: line 0: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-util-macros/work/util-macros-1.1.5: No such file or directory Error: The following dependencies failed to build: xorg-util-macros ---> Configuring xorg-util-macros 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_x11_xorg-util-macros/work/util-macros-1.1.5" && ./configure --prefix=/opt/local " returned error 1 Command output: sh: line 0: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-util-macros/work/util-macros-1.1.5: No such file or directory and on for each of them. I'm not sure "port upgrade" will fix everything anyhow: if there's not a newer version of something, it's not going to rebuild it. What I really need is "port reinstall installed" to force rebuilding everything with new binaries... -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3263 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080612/079419ae/attachment.bin From ryandesign at macports.org Thu Jun 12 14:47:40 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 12 Jun 2008 16:47:40 -0500 Subject: upgrades fail after leopard update In-Reply-To: <48518CA8.2080103@batie.org> References: <48518CA8.2080103@batie.org> Message-ID: On Jun 12, 2008, at 15:52, Alan Batie wrote: > I just got around to upgrading my work machine to leopard. The > first problem I ran into was that apparently I had a really old > xcode installed, so none of the old ported binaries would run > (something about an old threading model no longer supported > apparently). I upgraded that and did the self update, which > appeared to work, but "port upgrade" still fails. I finally did a > "port install dovecot" trying to get my mail going again, which > worked, until I tried to start it, at which time "daemondo" failed > to run. Apparently even though I did "self update" it didn't. I > downloaded installed macports 1.6.0, which fixed *that* finally, > but the "port upgrade installed" still fails: > > [163] # port upgrade installed > ---> Configuring xorg-util-macros > 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_x11_x > org-util-macros/work/util-macros-1.1.5" && ./configure --prefix=/ > opt/local " returned error 1 > Command output: sh: line 0: cd: /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_x > org-util-macros/work/util-macros-1.1.5: No such file or directory > > Error: The following dependencies failed to build: xorg-util-macros > ---> Configuring xorg-util-macros > 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_x11_x > org-util-macros/work/util-macros-1.1.5" && ./configure --prefix=/ > opt/local " returned error 1 > Command output: sh: line 0: cd: /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_x > org-util-macros/work/util-macros-1.1.5: No such file or directory > > and on for each of them. > > I'm not sure "port upgrade" will fix everything anyhow: if there's > not a newer version of something, it's not going to rebuild it. > What I really need is "port reinstall installed" to force > rebuilding everything with new binaries... Using Leopard to run ports built on Tiger isn't really supported. You could rebuild each port foo using "sudo port -ncuf upgrade foo" but the trick is you would need to reinstall each port in the correct order. For example, you would need to reinstall zlib before libpng, because libpng depends on zlib. "port deps foo" can tell you about a port foo's dependencies. You'd have to keep track of your rebuilding progress manually because there wouldn't necessarily be any indication in your list of installed ports which ones you had rebuilt and which you hadn't. There's also the problem that if you had any ports installed with e.g. the "darwin_8" variant (which is auto-selected on Tiger), when you rebuild, you would retain the darwin_8 variant, even though it's not appropriate for use on Leopard (where the darwin_9 variant is instead appropriate). For ports that define both, you'd even end up with ports installed that have both the darwin_8 and darwin_9 variants selected, which is surely bad. To work around this for a port foo you would have to "sudo port uninstall foo" and then "sudo port install foo +bar" (where "+bar" is whatever variants you had selected before (minus darwin_8 if applicable)). For these reasons you may be better off uninstalling MacPorts and then reinstalling the ports you need. Uninstall instructions are in the FAQ: http://trac.macports.org/wiki/FAQ#HowdoIremoveoruninstallMacPorts Before you uninstall, you can use "port installed" to get the list of ports and variants that you currently have installed, and use that when reinstalling. Alternate uninstall instructions might be "sudo port -f uninstall installed" which would leave behind any files that you had installed, such as configuration files or databases which you may want to save. From ryandesign at macports.org Thu Jun 12 14:56:50 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 12 Jun 2008 16:56:50 -0500 Subject: Is "MacPort" a valid term? In-Reply-To: <485058E4.3040206@gmail.com> References: <2AF28880-1F4A-44BB-8FFA-BCE920B15FD8@macports.org> <48502D3A.6060903@rppass.com> <51CB4A25-8826-4309-A05A-5B1358FC059D@macports.org> <485058E4.3040206@gmail.com> Message-ID: <0587ABCB-FF72-4526-9E7E-815F57A4A39C@macports.org> On Jun 11, 2008, at 17:59, Watson Ladd wrote: > Ryan Schmidt wrote: > >> On Jun 11, 2008, at 14:53, Ralph Pass wrote: >> >>> Ryan Schmidt wrote: >>> >>>> What entities could MacPorts have? >>> >>> macboats? >>> macships? >>> maccanoes? >>> macdocks? >>> macpallets? >>> macboxes? >>> maccrates? >>> >>> >>> :-))) >> >> I just knew this was coming. :) > > How about seeds? After all, they grow into ports for Apple machines. >> Cute! Though "seed" also has another connotation in the software industry (a pre-release version of something given to select individuals for testing) that we may not want. Old Mac OS installers had some interesting names for the files they stored their bits in. I remember "Installer Tome", "System Morsels", "System Orts"... Maybe we could reuse one of these terms. * "Did you install the libiconv morsel?" * "Please upgrade the zlib ort." "Ort" has the added advantage (or possibly confusion) that it's just one letter off from "port"... sudo ort install.... MacOrts.... From raimue at macports.org Thu Jun 12 15:05:45 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Fri, 13 Jun 2008 00:05:45 +0200 Subject: Is "MacPort" a valid term? In-Reply-To: <0587ABCB-FF72-4526-9E7E-815F57A4A39C@macports.org> References: <2AF28880-1F4A-44BB-8FFA-BCE920B15FD8@macports.org> <48502D3A.6060903@rppass.com> <51CB4A25-8826-4309-A05A-5B1358FC059D@macports.org> <485058E4.3040206@gmail.com> <0587ABCB-FF72-4526-9E7E-815F57A4A39C@macports.org> Message-ID: <48519DB9.9070700@macports.org> Ryan Schmidt wrote: > "Ort" has the added advantage (or possibly confusion) that it's just > one letter off from "port"... > > sudo ort install.... > > MacOrts.... This rather looks like a typo to me :-) Rainer From alan at batie.org Thu Jun 12 15:53:13 2008 From: alan at batie.org (Alan Batie) Date: Thu, 12 Jun 2008 15:53:13 -0700 Subject: upgrades fail after leopard update In-Reply-To: References: <48518CA8.2080103@batie.org> Message-ID: <4851A8D9.6000800@batie.org> Ryan Schmidt wrote: > For these reasons you may be better off uninstalling MacPorts and then > reinstalling the ports you need. !!! Consider this a feature request that "port upgrade" actually do an upgrade... I realize that's a different sort of upgrade, but this is going to be a royal pain in the backside... -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3263 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080612/5b8084fb/attachment.bin From ryandesign at macports.org Thu Jun 12 16:26:14 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 12 Jun 2008 18:26:14 -0500 Subject: upgrades fail after leopard update In-Reply-To: <4851A8D9.6000800@batie.org> References: <48518CA8.2080103@batie.org> <4851A8D9.6000800@batie.org> Message-ID: On Jun 12, 2008, at 17:53, Alan Batie wrote: > Ryan Schmidt wrote: > >> For these reasons you may be better off uninstalling MacPorts and >> then reinstalling the ports you need. > > !!! > > Consider this a feature request that "port upgrade" actually do an > upgrade... I realize that's a different sort of upgrade, but this > is going to be a royal pain in the backside... One way to improve this would be to remove autoselected variants during upgrade if they aren't applicable anymore. For example, if you have a port installed with +darwin_8 but you're now on Leopard, upgrading the port should deselect the darwin_8 variant. Can you think of other concrete ways we could improve the situation? I suppose it would be really nice if we had a script you could run which would fix everything for you. Rebuild all ports in the right order. Of course if you have a lot of ports installed and/or a slow machine it could take days to run. Also there might be a few cases where it wouldn't work. (I think we still have a few ports which work on Tiger but not on Leopard...) I guess such a script hasn't materialized yet (and the other mentioned issues haven't been resolved) because upgrading across major OS releases is not something one does often. Generally one does it once per major OS release, which is no more frequently than once a year. Also, testing such a script could be difficult. The fixes I've seen committed to the MacPorts repository recently deal with issues one would encounter in normal day-to-day use of MacPorts, so that's more important. From raimue at macports.org Thu Jun 12 16:42:06 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Fri, 13 Jun 2008 01:42:06 +0200 Subject: upgrades fail after leopard update In-Reply-To: <4851A8D9.6000800@batie.org> References: <48518CA8.2080103@batie.org> <4851A8D9.6000800@batie.org> Message-ID: <4851B44E.9050205@macports.org> Alan Batie wrote: > Consider this a feature request that "port upgrade" actually do an > upgrade... I realize that's a different sort of upgrade, but this is > going to be a royal pain in the backside... MacPorts simply cannot know that the underlying platform changed. But this does not happen very often, so it is not a great issue. But how should we improve this? We treat the auto-selected special platform variants like any other variant. So at upgrade we don't know if this is special or a requested variant. Correct me if I am wrong on this. Rainer From alan at batie.org Thu Jun 12 17:27:33 2008 From: alan at batie.org (Alan Batie) Date: Thu, 12 Jun 2008 17:27:33 -0700 Subject: upgrades fail after leopard update In-Reply-To: References: <48518CA8.2080103@batie.org> <4851A8D9.6000800@batie.org> Message-ID: <4851BEF5.4030304@batie.org> Ryan Schmidt wrote: > One way to improve this would be to remove autoselected variants during > upgrade if they aren't applicable anymore. For example, if you have a > port installed with +darwin_8 but you're now on Leopard, upgrading the > port should deselect the darwin_8 variant. > > Can you think of other concrete ways we could improve the situation? I would look at the upgrade process as iterating thus: get list of what's installed generate dependency graph scan the graph to break cycles and turn it into a tree? (not sure if you even have cycles, but I'd be surprised if they weren't possible, so you probably already have to deal with that anyhow) find out what version of os is installed traverse the tree depth first, for each port: what version is current what version is installed if there's an os specific variant, does the one installed match the current platform? if there's a change from what's installed, replace what's installed with the new version Obviously, retain any existing configs and data (e.g. I'd be *very* upset if upgrading dovecot removed my mail archive...). If there's a major change in the application that requires config file changes, that should be flagged before the upgrade starts and allow the choice of skipping that one port or aborting the entire process. Automatically shooting the application developers who made such a requirement is optional ;-) Having the port prompt you for required change info and updating the config accordingly so that it will at least run as it did before, while warning you that there are major changes that you should look into would be gravy. Library versions that are incompatible should always be able to co-exist. It was really frustrating in the early-to-mid days of tcl to find two apps (actually, it seemed like *every* app) requiring different versions of tcl that installed themselves in the same place. But I digress... > one does it once per major OS release, which is no more frequently than > once a year. Hopefully! > Also, testing such a script could be difficult. That's why I really want to run osx in a vm, but haven't gotten around to trying any of the hacks yet. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3263 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080612/d415a523/attachment.bin From cs at zip.com.au Thu Jun 12 18:24:06 2008 From: cs at zip.com.au (Cameron Simpson) Date: Fri, 13 Jun 2008 11:24:06 +1000 Subject: upgrades fail after leopard update In-Reply-To: <4851BEF5.4030304@batie.org> Message-ID: <20080613012406.GA12845@cskk.homeip.net> On 12Jun2008 17:27, Alan Batie wrote: > Ryan Schmidt wrote: > >> One way to improve this would be to remove autoselected variants during >> upgrade if they aren't applicable anymore. For example, if you have a >> port installed with +darwin_8 but you're now on Leopard, upgrading the >> port should deselect the darwin_8 variant. >> >> Can you think of other concrete ways we could improve the situation? I think you might have a "system signature" of some kind. Eg a string consisting of os-revision/cpu(ppc/intel)/xcode-version. Let macports track that (per installed port I guess so a partial upgrade doesn't get fubarred) as part of its "upgrade needed" criteria. > I would look at the upgrade process as iterating thus: > > get list of what's installed > generate dependency graph > scan the graph to break cycles and turn it into a tree? > (not sure if you even have cycles, but I'd be surprised > if they weren't possible, so you probably already have > to deal with that anyhow) Breaking cycles doesn't turn it into a tree, but fortunately that's ok; an acyclic digraph is fine - you can traverse it like a tree and just need to avoid rebuilding a package you rebuilt on another path. Which macports seems to do just fine anyway. > find out what version of os is installed Plus tools, maybe. See signature stuff above. > traverse the tree depth first, for each port: > what version is current > what version is installed > if there's an os specific variant, does the one installed match the > current platform? > if there's a change from what's installed, replace what's installed > with the new version As remarked, it would be good to distinguish chosen variants from auto-variants in the port install state information. Gentoo's emerge has a --pretend mode that is very useful. Does port install have that? Cheers, -- Cameron Simpson DoD#743 http://www.cskk.ezoshosting.com/cs/ From alan at batie.org Thu Jun 12 18:53:11 2008 From: alan at batie.org (Alan Batie) Date: Thu, 12 Jun 2008 18:53:11 -0700 Subject: upgrades fail after leopard update In-Reply-To: <20080613012406.GA12845@cskk.homeip.net> References: <20080613012406.GA12845@cskk.homeip.net> Message-ID: <4851D307.6080605@batie.org> Cameron Simpson wrote: > Breaking cycles doesn't turn it into a tree, but fortunately that's ok; > an acyclic digraph is fine - you can traverse it like a tree and just > need to avoid rebuilding a package you rebuilt on another path. Which > macports seems to do just fine anyway. If it looks like a tree... ;-) You would probably redundantly check a port, but the following times around, it would match as current, so nothing would be done. > As remarked, it would be good to distinguish chosen variants from > auto-variants in the port install state information. I'm not familiar with the variant options (I usually just say "port install something" and if it doesn't work, curse ;-) and manually install it), but yes, I can see where someone may choose to force a non-standard version and that would need to be tracked. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3263 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080612/e59c259f/attachment.bin From jmr at macports.org Thu Jun 12 19:26:28 2008 From: jmr at macports.org (Joshua Root) Date: Fri, 13 Jun 2008 12:26:28 +1000 Subject: upgrades fail after leopard update In-Reply-To: <20080613012406.GA12845@cskk.homeip.net> References: <20080613012406.GA12845@cskk.homeip.net> Message-ID: <4851DAD4.3070003@macports.org> Cameron Simpson wrote: > Gentoo's emerge has a --pretend mode that is very useful. Does port > install have that? There's a somewhat bitrotted patch here: - Josh From ryandesign at macports.org Thu Jun 12 23:07:52 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 13 Jun 2008 01:07:52 -0500 Subject: upgrades fail after leopard update In-Reply-To: <4851D307.6080605@batie.org> References: <20080613012406.GA12845@cskk.homeip.net> <4851D307.6080605@batie.org> Message-ID: On Jun 12, 2008, at 20:53, Alan Batie wrote: > Cameron Simpson wrote: > >> Breaking cycles doesn't turn it into a tree, but fortunately >> that's ok; >> an acyclic digraph is fine - you can traverse it like a tree and just >> need to avoid rebuilding a package you rebuilt on another path. Which >> macports seems to do just fine anyway. > > If it looks like a tree... ;-) > You would probably redundantly check a port, but the following > times around, it would match as current, so nothing would be done. We don't have circular dependencies in MacPorts. If we did, attempting to install any port involved in that cycle would cause port to go into an infinite loop. Believe me, we've (inadvertently, of course) had this situation before. >> As remarked, it would be good to distinguish chosen variants from >> auto-variants in the port install state information. > > I'm not familiar with the variant options (I usually just say "port > install something" and if it doesn't work, curse ;-) and manually > install it), but yes, I can see where someone may choose to force a > non-standard version and that would need to be tracked. If a port does not work as expected, your first step should not be to abandon the port and install the software manually; instead, please report a bug in our issue tracker so the bug can be fixed so the port works as expected. From alan at batie.org Thu Jun 12 23:24:38 2008 From: alan at batie.org (Alan Batie) Date: Thu, 12 Jun 2008 23:24:38 -0700 Subject: upgrades fail after leopard update In-Reply-To: References: <20080613012406.GA12845@cskk.homeip.net> <4851D307.6080605@batie.org> Message-ID: <485212A6.8000503@batie.org> Ryan Schmidt wrote: > If a port does not work as expected, your first step should not be to > abandon the port and install the software manually; instead, please > report a bug in our issue tracker so the bug can be fixed so the port > works as expected. I try, hence this discussion ;-) but don't always have time to properly characterize it or to make sure that everything is uptodate (which is usually the problem)... fortunately, most stuff does "just work". -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3263 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080612/5330a773/attachment.bin From ryandesign at macports.org Thu Jun 12 23:29:47 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 13 Jun 2008 01:29:47 -0500 Subject: upgrades fail after leopard update In-Reply-To: <20080613012406.GA12845@cskk.homeip.net> References: <20080613012406.GA12845@cskk.homeip.net> Message-ID: <7E6C4E5F-9D3B-4078-A376-45FB40BFB077@macports.org> On Jun 12, 2008, at 20:24, Cameron Simpson wrote: > On 12Jun2008 17:27, Alan Batie wrote: > >> Ryan Schmidt wrote: >> >>> One way to improve this would be to remove autoselected variants >>> during >>> upgrade if they aren't applicable anymore. For example, if you >>> have a >>> port installed with +darwin_8 but you're now on Leopard, >>> upgrading the >>> port should deselect the darwin_8 variant. >>> >>> Can you think of other concrete ways we could improve the situation? > > I think you might have a "system signature" of some kind. Eg a string > consisting of os-revision/cpu(ppc/intel)/xcode-version. Let macports > track that (per installed port I guess so a partial upgrade doesn't > get > fubarred) as part of its "upgrade needed" criteria. Good! I like it. Just storing all this info with each port when it's installed should be the first step. Providing a way to then display this info (maybe an enhanced version of "port installed") and making use of that info in "port outdated" can be later enhancements. I had suggested in the "Universal issues" [1] thread that we should store the build CPU architecture, the target architecture(s), and the major OS version, but we may as well store the complete OS version, and storing the Xcode version is a great idea too. We've certainly had some issues with earlier Xcode versions (2.0 <= x < 2.4.1) that it would be nice to be able to identify. Though often the issue is that the port won't compile at all. [1] http://lists.macosforge.org/pipermail/macports-dev/2008-June/ 005366.html >> I would look at the upgrade process as iterating thus: >> >> get list of what's installed >> generate dependency graph >> scan the graph to break cycles and turn it into a tree? >> (not sure if you even have cycles, but I'd be surprised >> if they weren't possible, so you probably already have >> to deal with that anyhow) > > Breaking cycles doesn't turn it into a tree, but fortunately that's > ok; > an acyclic digraph is fine - you can traverse it like a tree and just > need to avoid rebuilding a package you rebuilt on another path. Which > macports seems to do just fine anyway. > >> find out what version of os is installed > > Plus tools, maybe. See signature stuff above. > >> traverse the tree depth first, for each port: >> what version is current >> what version is installed >> if there's an os specific variant, does the one installed match the >> current platform? >> if there's a change from what's installed, replace what's installed >> with the new version MacPorts has no way to know "if there's a change from what's installed" since it's quite possible that the software will build differently on, say, Leopard than it would on Tiger, even if the port version, chosen variants and processor architecture don't change. The Xcode version will change since on Tiger you'd have at best Xcode 2.5 and on Leopard you'd have at least Xcode 3.0, but merely upgrading the Xcode version is no reason (usually) to force a port to be rebuilt (though if we store the Xcode version, we could then make exceptions for known-bad Xcode versions). From alan at batie.org Fri Jun 13 00:35:35 2008 From: alan at batie.org (Alan Batie) Date: Fri, 13 Jun 2008 00:35:35 -0700 Subject: upgrades fail after leopard update In-Reply-To: <7E6C4E5F-9D3B-4078-A376-45FB40BFB077@macports.org> References: <20080613012406.GA12845@cskk.homeip.net> <7E6C4E5F-9D3B-4078-A376-45FB40BFB077@macports.org> Message-ID: <48522347.1040107@batie.org> Ryan Schmidt wrote: >>> if there's a change from what's installed, replace what's installed >>> with the new version > > MacPorts has no way to know "if there's a change from what's > installed" Given that you can say "port installed" to list what's installed, there must be some sort of registration that could be compared with what would be recorded if the port were built "now". > merely upgrading > the Xcode version is no reason (usually) to force a port to be > rebuilt (though if we store the Xcode version, we could then make > exceptions for known-bad Xcode versions). The ease of being able to just say "port upgrade installed" and going home for the night (or to bed or work on a home machine) would make it worth the time of doing unnecessary rebuilds. Keep good logs of course, in case of problems. If you really want to get fancy, support checkpointing and reversion in case of errors, but let's not go there now ;-) The quick fix for right now would be to just add "reinstall" where it just rebuilds what it's already got. As it is now, my ports registry is basically messed up (though not enough to really break it) because to get my mail archive going again, I just did "port install dovecot" and it installed the latest version over the top of the old one, and now as far as the ports system is concerned I have a couple different versions installed. I suppose it's a "bug" that it did that, but it was a feature in this instance. Hmm. I seem to have managed 3 somehow: [1] $ port installed | grep dove dovecot @1.0.0_0+darwin_8 dovecot @1.0.13_0+darwin_8+darwin_9 (active) dovecot @1.0.13_0+darwin_9 Anyhow, the point is that all the fancy stuff is all well and nice, but just a basic rebuild would be a 90% solution. Actually, the problem seems even smaller --- it looks like "port upgrade one-port" is working, it's the "installed" arg that for some reason isn't creating an expected file that's blocking the way... Though I was able to upgrade gettext, but popt is still complaining, so I suppose when I get a chance, I'll have to debug it and file a real bug report: checking for GNU xgettext... configure: error: *** GNU gettext is required. The latest version *** is always available from ftp://ftp.gnu.org/gnu/gettext/. Error: Unable to upgrade port: 1 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3263 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080613/361fdc3d/attachment.bin From j.van_den_hoff at fzd.de Fri Jun 13 04:11:38 2008 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Fri, 13 Jun 2008 13:11:38 +0200 Subject: python2.5 install failed Message-ID: <20080613111137.GC7354@marco.fz-rossendorf.de> hi, under 10.4.11 I did a `port upgrade mercurial'. which depends on python2.5 and `port' tries to install this (only python2.4 installed up to now). now I see the following: ==============================================CUT======================================== ---> Fetching python25 ---> Attempting to fetch Python-2.5.2.tar.bz2 from http://www.python.org//ftp/python/2.5.2/ ---> Verifying checksum(s) for python25 ---> Extracting python25 ---> Applying patches to python25 ---> Configuring python25 ---> Building python25 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_python25/work/Python-2.5.2" && make all " returned error 2 ==============================================CUT======================================== after this point compile nevertheless seemingly runs fine till the final `ranlib' run: ==============================================CUT======================================== ranlib libpython2.5.a /usr/bin/libtool -o libpython2.5.dylib -dynamic \ -all_load libpython2.5.a -single_module \ -install_name /opt/local/lib/libpython2.5.dylib \ -compatibility_version 2.5 \ -current_version 2.5 -lSystem -lSystemStubs -L/opt/local/lib ld64 failed: in libpython2.5.a(getbuildinfo.o), not a valid ppc64 mach-o file /usr/bin/libtool: internal link edit command failed make: *** [libpython2.5.dylib] Error 1 ==============================================CUT======================================== then some other stuff (gperf, gettext are fetched/upgraded and finally I see: ==============================================CUT======================================== Error: The following dependencies failed to build: python25 ---> Fetching bzip2 ---> Attempting to fetch bzip2-1.0.5.tar.gz from http://www.bzip.org/1.0.5/ ---> Verifying checksum(s) for bzip2 ---> Extracting bzip2 ---> Applying patches to bzip2 ---> Configuring bzip2 ---> Building bzip2 with target all ---> Staging bzip2 into destroot ---> Packaging tgz archive for bzip2 1.0.5_1 ---> Deactivating bzip2 1.0.4_1 ---> Installing bzip2 1.0.5_1 ---> Activating bzip2 1.0.5_1 ---> Cleaning bzip2 ---> Building python25 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_python25/work/Python-2.5.2" && make all " returned error 2 Command output: /usr/bin/libtool -o libpython2.5.dylib -dynamic \ -all_load libpython2.5.a -single_module \ -install_name /opt/local/lib/libpython2.5.dylib \ -compatibility_version 2.5 \ -current_version 2.5 -lSystem -lSystemStubs -L/opt/local/lib ld64 failed: in libpython2.5.a(getbuildinfo.o), not a valid ppc64 mach-o file /usr/bin/libtool: internal link edit command failed make: *** [libpython2.5.dylib] Error 1 Error: The following dependencies failed to build: py25-bz2 python25 py25-hashlib py25-zlib Error: Unable to upgrade port: 1 ==============================================CUT======================================== `port' is current and up-to-date. where's my fault? and if the python2.5 problem is not easily solved: can I enforce upgrade of `mercurial' (assuming it will run just fine with python2.4)? joerg From ryandesign at macports.org Fri Jun 13 13:47:56 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 13 Jun 2008 15:47:56 -0500 Subject: Activating git-core 1.5.3.1_0 failed: In-Reply-To: References: Message-ID: <43BF7A0D-5A15-4BCD-937C-BC9BC8A0CA1A@macports.org> On Jun 13, 2008, at 13:48, Yvon Thoraval wrote: >> No port should claim ownership of perllocal.pod. Any port that >> does needs to be fixed. >> >> git-core stopped claiming ownership of perllocal.pod in r34462 >> (2008-02-25) so you should update your ports ("sudo port >> selfupdate"), clean git-core ("sudo port clean --work git-core") >> and try upgrading it again ("sudo port upgrade git-core"). > > Unfortunately, i got about the same : > > ~%> sudo port selfupdate > Password: > > 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! > ~%> sudo port clean --work git-core > Password: > Portfile changed since last build; discarding previous state. > ---> Cleaning git-core > ~%> sudo port upgrade git-core > ---> Activating git-core 1.5.3.1_0+doc > Error: Activating git-core 1.5.3.1_0 failed: Image error: /opt/ > local/lib/perl5/5.8.8/darwin-2level/perllocal.pod already exists > and does not belong to a registered port. Unable to activate port > git-core. > ~%> Try uninstalling git-core @1.5.3.1_0+doc first. sudo port -f uninstall git-core @1.5.3.1_0+doc Better yet, uninstall all versions of git-core you have installed. Then "sudo port install git-core" and it should rebuild. From blb at macports.org Fri Jun 13 13:52:25 2008 From: blb at macports.org (Bryan Blackburn) Date: Fri, 13 Jun 2008 14:52:25 -0600 Subject: python2.5 install failed In-Reply-To: <20080613111137.GC7354@marco.fz-rossendorf.de> References: <20080613111137.GC7354@marco.fz-rossendorf.de> Message-ID: <83A73F49-7CA7-4DF6-9F95-EAE2D2E313E6@macports.org> On Jun 13, 2008, at 5:11 AM, Joerg van den Hoff wrote: > hi, > > under 10.4.11 I did a `port upgrade mercurial'. > ... > /usr/bin/libtool -o libpython2.5.dylib -dynamic \ > -all_load libpython2.5.a -single_module \ > -install_name /opt/local/lib/libpython2.5.dylib \ > -compatibility_version 2.5 \ > -current_version 2.5 -lSystem -lSystemStubs -L/opt/local/lib > ld64 failed: in libpython2.5.a(getbuildinfo.o), not a valid ppc64 > mach-o file > /usr/bin/libtool: internal link edit command failed > make: *** [libpython2.5.dylib] Error 1 Check your Xcode version, and see: Bryan ... > > joerg > From jmr at macports.org Fri Jun 13 14:00:28 2008 From: jmr at macports.org (Joshua Root) Date: Sat, 14 Jun 2008 07:00:28 +1000 Subject: tracking down extraction In-Reply-To: <4852DAFD.3000905@batie.org> References: <4852DAFD.3000905@batie.org> Message-ID: <4852DFEC.8030902@macports.org> Alan Batie wrote: > The error I'm seeing (I did a "port -f uninstall glib2" before to try to > start fresh): > > # port install glib2 > ---> Applying patches to glib2 > Error: Target org.macports.patch returned: couldn't change working > directory to > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_glib2/work/glib-2.16.3": > no such file or directory > Error: Status 1 encountered during processing. Looks like MacPorts expects the work directory to be present, but it has been deleted. Running `sudo port clean glib2` should make expectation and reality match up. - Josh From ryandesign at macports.org Fri Jun 13 14:08:34 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 13 Jun 2008 16:08:34 -0500 Subject: upgrades fail after leopard update In-Reply-To: <48522347.1040107@batie.org> References: <20080613012406.GA12845@cskk.homeip.net> <7E6C4E5F-9D3B-4078-A376-45FB40BFB077@macports.org> <48522347.1040107@batie.org> Message-ID: <725D8C94-BA92-48B4-A3DD-419FA4F1A7AE@macports.org> On Jun 13, 2008, at 02:35, Alan Batie wrote: > Ryan Schmidt wrote: > >>>> if there's a change from what's installed, replace what's >>>> installed >>>> with the new version >> >> MacPorts has no way to know "if there's a change from what's >> installed" > > Given that you can say "port installed" to list what's installed, > there must be some sort of registration that could be compared with > what would be recorded if the port were built "now". And I'm saying that the "unique" identifier for what would be built "now" (currently made up of the combination of the port name, version and variants) might not be any different from the unique identifier for what was built "then", even if the resulting software might be different. MacPorts just has no way to know. That's why it's an excellent suggestion to add the OS version, Xcode version and processor architecture to the unique identifier to try to make it truly unique. >> merely upgrading >> the Xcode version is no reason (usually) to force a port to be >> rebuilt (though if we store the Xcode version, we could then make >> exceptions for known-bad Xcode versions). > > The ease of being able to just say "port upgrade installed" and > going home for the night (or to bed or work on a home machine) > would make it worth the time of doing unnecessary rebuilds. You never want "port upgrade installed"; you want "port upgrade outdated", if anything. "port upgrade" does not upgrade ports that are not outdated, so saying "port upgrade installed" just wastes time evaluating ports that won't get upgraded. Just having a newer version of Xcode should not trigger a port to show up in "port outdated", though once we start storing information about Xcode version and such with each installed port, there could be an optional more-pedantic "outdated" which could list this. > Keep good logs of course, in case of problems. MacPorts keeps no logs of any kind at this time. There is a logging proposal written, but the feature is not yet coded: http://trac.macports.org/wiki/LoggingProposal > If you really want to get fancy, support checkpointing and > reversion in case of errors, but let's not go there now ;-) Not sure what you mean. If you mean the ability to go back to a previous version of a port, you already have that ability. When you "port upgrade foo", the old version of foo remains installed (but deactivated). If you want to go back to the old version, you can deactivate the new version and (re)activate the old one. > The quick fix for right now would be to just add "reinstall" where > it just rebuilds what it's already got. You already have that, for individual ports. To rebuild port foo even if port doesn't think it needs to be rebuilt: sudo port -ncuf upgrade foo In MacPorts 1.6.0, I don't know a good way to tell it to rebuild more than one port at a time. Omitting the -n flag will cause port to rebuild some ports many many times. I think this has been fixed in trunk but I haven't had occasion to try it. > As it is now, my ports registry is basically messed up (though not > enough to really break it) because to get my mail archive going > again, I just did "port install dovecot" and it installed the > latest version over the top of the old one, and now as far as the > ports system is concerned I have a couple different versions > installed. I suppose it's a "bug" that it did that, but it was a > feature in this instance. Not a bug. Works as intended. > Hmm. I seem to have managed 3 somehow: > > [1] $ port installed | grep dove > dovecot @1.0.0_0+darwin_8 > dovecot @1.0.13_0+darwin_8+darwin_9 (active) > dovecot @1.0.13_0+darwin_9 As I see it, dovecot @1.0.0_0+darwin_8 was installed on Tiger. When 1.0.13_0 was released, you did "sudo port upgrade dovecot" which installed and activated dovecot @1.0.13_0+darwin_8 and deactivated (but left installed) dovecot @1.0.0_0+darwin_8. Then you upgraded to Leopard. Then you forced the reinstall of dovecot, which now caused the +darwin_9 variant to get added, so you ended up with dovecot @1.0.13_0+darwin_8+darwin_9 (the error I was telling you about in the last mail). Then you asked for dovecot to be installed, and because the set of variants MacPorts decided to use (only +darwin_9) differed from what was already installed, it built it again, and installed (but couldn't activate because of the other version already active) dovecot @1.0.13_0+darwin_9. You should now deactivate (and, if you like, uninstall) dovecot @1.0.13_0+darwin_8+darwin_9 and activate dovecot @1.0.13_0+darwin_9 to get a version that is expected to work on Leopard. I can give you no expectations about dovecot @1.0.13_0 +darwin_8+darwin_9. > Anyhow, the point is that all the fancy stuff is all well and nice, > but just a basic rebuild would be a 90% solution. If you mean something that would rebuild all ports in order, then we don't have it, and I don't think it would be "basic"; I think it would be a non-trivial script to write. For me at least. > Actually, the problem seems even smaller --- it looks like "port > upgrade one-port" is working, it's the "installed" arg that for > some reason isn't creating an expected file that's blocking the way... > > Though I was able to upgrade gettext, but popt is still > complaining, so I suppose when I get a chance, I'll have to debug > it and file a real bug report: > > checking for GNU xgettext... configure: error: > *** GNU gettext is required. The latest version > *** is always available from ftp://ftp.gnu.org/gnu/gettext/. > > Error: Unable to upgrade port: 1 I haven't had a chance to test this and my battery is about to die so I'm going to send this mail now. :) From alan at batie.org Fri Jun 13 14:27:43 2008 From: alan at batie.org (Alan Batie) Date: Fri, 13 Jun 2008 14:27:43 -0700 Subject: upgrades fail after leopard update In-Reply-To: <725D8C94-BA92-48B4-A3DD-419FA4F1A7AE@macports.org> References: <20080613012406.GA12845@cskk.homeip.net> <7E6C4E5F-9D3B-4078-A376-45FB40BFB077@macports.org> <48522347.1040107@batie.org> <725D8C94-BA92-48B4-A3DD-419FA4F1A7AE@macports.org> Message-ID: <4852E64F.9080207@batie.org> Ryan Schmidt wrote: > MacPorts just has no way to know. That's why it's an > excellent suggestion to add the OS version, Xcode version and processor > architecture to the unique identifier to try to make it truly unique. We're in violent agreement ;-) I was thinking of this future, sorry about that... > You never want "port upgrade installed"; you want "port upgrade > outdated", if anything. "port upgrade" does not upgrade ports that are > not outdated, so saying "port upgrade installed" just wastes time > evaluating ports that won't get upgraded. makes sense > Just having a newer version of Xcode should not trigger a port to show > up in "port outdated", though once we start storing information about > Xcode version and such with each installed port, there could be an > optional more-pedantic "outdated" which could list this. perhaps a "port rebuild outdated", where "outdated" in this case refers to the environment rather than the port version? I'm assuming "port upgrade outdated" would eliminate the issue in the cases where the port *does* have a newer version. > If you > want to go back to the old version, you can deactivate the new version > and (re)activate the old one. Ahhh, cool. > You already have that, for individual ports. To rebuild port foo even if > port doesn't think it needs to be rebuilt: > > sudo port -ncuf upgrade foo Also cool. Though this is going to fetch the latest version, which may not be what you want. Perhaps if you specified the existing version as the "upgrade"? > installed and activated dovecot @1.0.13_0+darwin_8 and deactivated (but > left installed) dovecot @1.0.0_0+darwin_8. > Then you asked for dovecot to be installed, and because the > set of variants MacPorts decided to use (only +darwin_9) differed from > what was already installed, it built it again, and installed (but > couldn't activate because of the other version already active) I'm confused why it could activate the new version the first time and not the second? > If you mean something that would rebuild all ports in order, then we > don't have it, and I don't think it would be "basic"; I think it would > be a non-trivial script to write. For me at least. The ncuf thing is what I meant I suppose, though doing it recursively would be nice. Isn't the basic code there already for the "outdated" operation? There may not really be anything that needs doing, saving fixing the bugs I'm running into... > I haven't had a chance to test this and my battery is about to die so > I'm going to send this mail now. :) ;-) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3263 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080613/0ea3b5f2/attachment.bin From ryandesign at macports.org Fri Jun 13 16:21:11 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 13 Jun 2008 18:21:11 -0500 Subject: upgrades fail after leopard update In-Reply-To: <4852E64F.9080207@batie.org> References: <20080613012406.GA12845@cskk.homeip.net> <7E6C4E5F-9D3B-4078-A376-45FB40BFB077@macports.org> <48522347.1040107@batie.org> <725D8C94-BA92-48B4-A3DD-419FA4F1A7AE@macports.org> <4852E64F.9080207@batie.org> Message-ID: On Jun 13, 2008, at 16:27, Alan Batie wrote: > Ryan Schmidt wrote: > >> MacPorts just has no way to know. That's why it's an excellent >> suggestion to add the OS version, Xcode version and processor >> architecture to the unique identifier to try to make it truly unique. > > We're in violent agreement ;-) I was thinking of this future, > sorry about that... > >> You never want "port upgrade installed"; you want "port upgrade >> outdated", if anything. "port upgrade" does not upgrade ports that >> are not outdated, so saying "port upgrade installed" just wastes >> time evaluating ports that won't get upgraded. > > makes sense > >> Just having a newer version of Xcode should not trigger a port to >> show up in "port outdated", though once we start storing >> information about Xcode version and such with each installed port, >> there could be an optional more-pedantic "outdated" which could >> list this. > > perhaps a "port rebuild outdated", where "outdated" in this case > refers to the environment rather than the port version? "outdated" is a "pseudo-port", which MacPorts expands into a list of ports. MacPorts cannot expand "outdated" to mean one set of ports in one circumstance and a different set of ports in a different circumstance. The list of "outdated" ports is always the same, regardless what port command you issue. > I'm assuming "port upgrade outdated" would eliminate the issue in > the cases where the port *does* have a newer version. Not in the case where the port you're wanting to upgrade already has e.g. the +darwin_8 variant selected. In that case, MacPorts will currently add the +darwin_9 variant (if the port has one) but not remove the +darwin_8 variant. MacPorts should be enhanced to remove the +darwin_8 variant in this case. >> If you want to go back to the old version, you can deactivate the >> new version and (re)activate the old one. > > Ahhh, cool. > >> You already have that, for individual ports. To rebuild port foo >> even if port doesn't think it needs to be rebuilt: >> sudo port -ncuf upgrade foo > > Also cool. Though this is going to fetch the latest version, which > may not be what you want. Correct. > Perhaps if you specified the existing version as the "upgrade"? Not possible. MacPorts has no built-in way to install an older version once a portfile has been updated. Instructions for getting an older version are in the How To's: http://trac.macports.org/wiki/howto/InstallingOlderPort >> installed and activated dovecot @1.0.13_0+darwin_8 and deactivated >> (but left installed) dovecot @1.0.0_0+darwin_8. > >> Then you asked for dovecot to be installed, and because the set of >> variants MacPorts decided to use (only +darwin_9) differed from >> what was already installed, it built it again, and installed (but >> couldn't activate because of the other version already active) > > I'm confused why it could activate the new version the first time > and not the second? In one instance, I think you said "port upgrade", which means "install the new version, then deactivate the currently-active version, then activate the new version." In the other case, I think you said "port install", which means "install the new version and activate it". Only one port can be active at a time, so "port install" had an error when attempting to activate. From bxf4 at u.washington.edu Fri Jun 13 16:29:14 2008 From: bxf4 at u.washington.edu (Brian Flaherty) Date: Fri, 13 Jun 2008 16:29:14 -0700 Subject: Emacs.app & carbon emacs Message-ID: <20080613232914.GA85726@stendahl.psych.washington.edu> Hello, I have Emacs.app installed, and I'd like to install emacs +carbon too. When I did that, everything was fine until activation: ---> Activating emacs 22.2_0+carbon Error: Target org.macports.activate returned: Image error: /Applications/MacPorts/Emacs.app/Contents/Info.plist is being used by the active emacs-app port. Please deactivate this port first, or use the -f flag to force the activation. Error: Status 1 encountered during processing. What does it mean to force it? Will they peacefully coexist? Thank you for your time. Brian From ryandesign at macports.org Fri Jun 13 16:44:46 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 13 Jun 2008 18:44:46 -0500 Subject: Emacs.app & carbon emacs In-Reply-To: <20080613232914.GA85726@stendahl.psych.washington.edu> References: <20080613232914.GA85726@stendahl.psych.washington.edu> Message-ID: <6A4616D4-B985-48E3-B349-ADA55CB5BD96@macports.org> On Jun 13, 2008, at 18:29, Brian Flaherty wrote: > Hello, > > I have Emacs.app installed, and I'd like to install emacs +carbon > too. When I did that, everything was fine until activation: > > ---> Activating emacs 22.2_0+carbon > Error: Target org.macports.activate returned: Image error: > /Applications/MacPorts/Emacs.app/Contents/Info.plist is being used by > the active emacs-app port. Please deactivate this port first, or use > the -f flag to force the activation. > Error: Status 1 encountered during processing. > > What does it mean to force it? Will they peacefully coexist? No, they won't coexist. Their files want to live in the same places, so you can only have one at a time. You can "sudo port -f activate emacs" but it will overwrite the files that belong to emacs-app and this is probably not what you want. You should deactivate emacs-app and then activate (force should no longer be necessary) emacs. From alan at batie.org Fri Jun 13 17:01:16 2008 From: alan at batie.org (Alan Batie) Date: Fri, 13 Jun 2008 17:01:16 -0700 Subject: upgrades fail after leopard update In-Reply-To: References: <20080613012406.GA12845@cskk.homeip.net> <7E6C4E5F-9D3B-4078-A376-45FB40BFB077@macports.org> <48522347.1040107@batie.org> <725D8C94-BA92-48B4-A3DD-419FA4F1A7AE@macports.org> <4852E64F.9080207@batie.org> Message-ID: <48530A4C.8020902@batie.org> BTW, for the record here, the problem with the upgrade turned out to be macports found the old bzip2 and was trying to use it to extract the tarball. It was the old tiger binary, and failing, but the ports code wasn't detecting the failure. When it went to process the extracted files, they weren't there. removing and reinstalling bzip2 fixed it. Ryan Schmidt wrote: >> perhaps a "port rebuild outdated", where "outdated" in this case >> refers to the environment rather than the port version? > > "outdated" is a "pseudo-port", which MacPorts expands into a list of > ports. MacPorts cannot expand "outdated" to mean one set of ports in one > circumstance and a different set of ports in a different circumstance. I see; well, "port rebuild installed" would be most likely what you'd want "just to be sure" in a case like this anyhow. > MacPorts should be enhanced to remove the > +darwin_8 variant in this case. Yes, as I understand things, I agree. > In one instance, I think you said "port upgrade", which means "install > the new version, then deactivate the currently-active version, then > activate the new version." In the other case, I think you said "port > install", which means "install the new version and activate it". Only > one port can be active at a time, so "port install" had an error when > attempting to activate. That sounds very likely. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3263 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080613/87702351/attachment.bin From hirshj at att.net Sat Jun 14 10:02:11 2008 From: hirshj at att.net (JasonHirsh) Date: Sat, 14 Jun 2008 10:02:11 -0700 (PDT) Subject: Apache Apache 2.2.8 install fails -Error: Target org.macports.fetch returned: fetch failed Message-ID: <17841700.post@talk.nabble.com> When attempt to install Apache 2.2.8 under 10.4.11 I get the following: ---> Fetching apache2 ---> Attempting to fetch httpd-2.2.8.tar.bz2 from http://www.apache.org/dist/httpd ---> Attempting to fetch httpd-2.2.8.tar.bz2 from http://apache.planetmirror.com.au/dist/httpd ---> Attempting to fetch httpd-2.2.8.tar.bz2 from ftp://ftp.planetmirror.com/pub/apache/dist/httpd ---> Attempting to fetch httpd-2.2.8.tar.bz2 from ftp://ftp.is.co.za/Apache/dist/httpd ---> Attempting to fetch httpd-2.2.8.tar.bz2 from ftp://ftp.infoscience.co.jp/pub/net/apache/dist/httpd ---> Attempting to fetch httpd-2.2.8.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/apache2 ---> Attempting to fetch httpd-2.2.8.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch httpd-2.2.8.tar.bz2 from http://svn.macports.org/repository/macports/downloads/apache2 Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. I have verified that my macports is up to date... any ideas?? -- View this message in context: http://www.nabble.com/Apache-Apache-2.2.8-install-fails--Error%3A-Target-org.macports.fetch-returned%3A-fetch-failed-tp17841700p17841700.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From marius173 at mchsi.com Sat Jun 14 12:39:24 2008 From: marius173 at mchsi.com (Marius Schamschula) Date: Sat, 14 Jun 2008 14:39:24 -0500 Subject: Apache Apache 2.2.8 install fails -Error: Target org.macports.fetch returned: fetch failed In-Reply-To: <17841700.post@talk.nabble.com> References: <17841700.post@talk.nabble.com> Message-ID: <8E1DA097-DA26-47EC-B5D4-74F376A840FD@mchsi.com> Apache released httpd 2.2.9 this morning... On Jun 14, 2008, at 12:02 PM, JasonHirsh wrote: > > > > When attempt to install Apache 2.2.8 under 10.4.11 I get the > following: > ---> Fetching apache2 > ---> Attempting to fetch httpd-2.2.8.tar.bz2 from > http://www.apache.org/dist/httpd > ---> Attempting to fetch httpd-2.2.8.tar.bz2 from > http://apache.planetmirror.com.au/dist/httpd > ---> Attempting to fetch httpd-2.2.8.tar.bz2 from > ftp://ftp.planetmirror.com/pub/apache/dist/httpd > ---> Attempting to fetch httpd-2.2.8.tar.bz2 from > ftp://ftp.is.co.za/Apache/dist/httpd > ---> Attempting to fetch httpd-2.2.8.tar.bz2 from > ftp://ftp.infoscience.co.jp/pub/net/apache/dist/httpd > ---> Attempting to fetch httpd-2.2.8.tar.bz2 from > http://svn.macports.org/repository/macports/distfiles/apache2 > ---> Attempting to fetch httpd-2.2.8.tar.bz2 from > http://svn.macports.org/repository/macports/distfiles/general/ > ---> Attempting to fetch httpd-2.2.8.tar.bz2 from > http://svn.macports.org/repository/macports/downloads/apache2 > Error: Target org.macports.fetch returned: fetch failed > Error: Status 1 encountered during processing. > > I have verified that my macports is up to date... any ideas?? > -- > View this message in context: http://www.nabble.com/Apache- > Apache-2.2.8-install-fails--Error%3A-Target-org.macports.fetch- > returned%3A-fetch-failed-tp17841700p17841700.html > Sent from the MacPorts - Users mailing list archive at Nabble.com. > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users Marius -- Marius Schamschula Webmaster The Huntsville Macintosh Users Group www.hmug.org webmaster at hmug dot org marius at schamschula dot com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080614/b250c3d6/attachment.htm From hirshj at att.net Sat Jun 14 12:50:11 2008 From: hirshj at att.net (JasonHirsh) Date: Sat, 14 Jun 2008 12:50:11 -0700 (PDT) Subject: Apache Apache 2.2.8 install fails -Error: Target org.macports.fetch returned: fetch failed In-Reply-To: <8E1DA097-DA26-47EC-B5D4-74F376A840FD@mchsi.com> References: <17841700.post@talk.nabble.com> <8E1DA097-DA26-47EC-B5D4-74F376A840FD@mchsi.com> Message-ID: <17843176.post@talk.nabble.com> So I presume I wait and that macports will be updated to correct the fetch commands? Marius Schamschula-2 wrote: > > Apache released httpd 2.2.9 this morning... > > On Jun 14, 2008, at 12:02 PM, JasonHirsh wrote: > >> >> >> >> When attempt to install Apache 2.2.8 under 10.4.11 I get the >> following: >> ---> Fetching apache2 >> ---> Attempting to fetch httpd-2.2.8.tar.bz2 from >> http://www.apache.org/dist/httpd >> ---> Attempting to fetch httpd-2.2.8.tar.bz2 from >> http://apache.planetmirror.com.au/dist/httpd >> ---> Attempting to fetch httpd-2.2.8.tar.bz2 from >> ftp://ftp.planetmirror.com/pub/apache/dist/httpd >> ---> Attempting to fetch httpd-2.2.8.tar.bz2 from >> ftp://ftp.is.co.za/Apache/dist/httpd >> ---> Attempting to fetch httpd-2.2.8.tar.bz2 from >> ftp://ftp.infoscience.co.jp/pub/net/apache/dist/httpd >> ---> Attempting to fetch httpd-2.2.8.tar.bz2 from >> http://svn.macports.org/repository/macports/distfiles/apache2 >> ---> Attempting to fetch httpd-2.2.8.tar.bz2 from >> http://svn.macports.org/repository/macports/distfiles/general/ >> ---> Attempting to fetch httpd-2.2.8.tar.bz2 from >> http://svn.macports.org/repository/macports/downloads/apache2 >> Error: Target org.macports.fetch returned: fetch failed >> Error: Status 1 encountered during processing. >> >> I have verified that my macports is up to date... any ideas?? >> -- >> View this message in context: http://www.nabble.com/Apache- >> Apache-2.2.8-install-fails--Error%3A-Target-org.macports.fetch- >> returned%3A-fetch-failed-tp17841700p17841700.html >> Sent from the MacPorts - Users mailing list archive at Nabble.com. >> >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > Marius > -- > Marius Schamschula > Webmaster > > The Huntsville Macintosh Users Group > www.hmug.org > > webmaster at hmug dot org > marius at schamschula dot com > > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > -- View this message in context: http://www.nabble.com/Apache-Apache-2.2.8-install-fails--Error%3A-Target-org.macports.fetch-returned%3A-fetch-failed-tp17841700p17843176.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From raimue at macports.org Sat Jun 14 15:36:27 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sun, 15 Jun 2008 00:36:27 +0200 Subject: Apache Apache 2.2.8 install fails -Error: Target org.macports.fetch returned: fetch failed In-Reply-To: <17841700.post@talk.nabble.com> References: <17841700.post@talk.nabble.com> Message-ID: <485447EB.4090600@macports.org> JasonHirsh wrote: > I have verified that my macports is up to date... any ideas?? The file moved on the server. Use this command: $ sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/apache2 port -v fetch apache2 Rainer From hirshj at att.net Sat Jun 14 16:41:28 2008 From: hirshj at att.net (Jason Hirsh) Date: Sat, 14 Jun 2008 19:41:28 -0400 Subject: {solved}Re: Apache Apache 2.2.8 install fails -Error: Target org.macports.fetch returned: fetch failed In-Reply-To: <485447EB.4090600@macports.org> References: <17841700.post@talk.nabble.com> <485447EB.4090600@macports.org> Message-ID: <3A82C428-85DA-48E1-A110-0D32F8F7AF52@att.net> On Jun 14, 2008, at 6:36 PM, Rainer M?ller wrote: > JasonHirsh wrote: >> I have verified that my macports is up to date... any ideas?? > > The file moved on the server. Use this command: > > $ sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/apache2 > port -v fetch apache2 > > Rainer that did it From philrand at gmail.com Sun Jun 15 17:21:18 2008 From: philrand at gmail.com (Phil Rand) Date: Sun, 15 Jun 2008 17:21:18 -0700 Subject: Mercurial install after MacPython.app, Leopard, Google App Engine Message-ID: <5784c1b10806151721x72b85c74mbdf6ae5aa9a9452c@mail.gmail.com> Hi all, I recently upgraded to Leopard, and today I had trouble upgrading Mercurial. I've got it working now, but don't have a compete explanation. Here's what I found and did (all done interactively, without taking notes, so the details are rapidly slipping away). I decided to rename /opt/local to /opt/local.00, create a new /opt/local, and reinstall MacPorts. That went nicely, but "sudo port install mercurial" ran into trouble with the python extensions, py25-zlib, py25-hashlib, and py25-bz2. I found "Library/Frameworks/Python.framework/Versions/2.5/bin" at the beginning of my PATH environment variable. I tracked that down to my ~/.profile file, removed that, and made sure /opt/local/bin was first in my PATH. I found MacPython2.5.app in my Applications folder, and renamed it. I found symbolic links from /usr/local/bin for python, python2.5, and related commands, pointing to files in /Library/Frameworks/Python.framework/Versions/2.5/bin. I had installed an early version of the Google App Engine prior to Leopard, and wonder if it might have done some of this. I uninstalled all the deps for mercurial, and installed python25. It did not install /opt/local/bin/python, only /opt/local/bin/python2.5. After that the python extensions py25-zlib, py25-hashlib, py25-bz2 woudn't install until I created a symbolic link: cd /opt/local/bin; ln -s python2.5 python Is it expected for the python25 port NOT to create /opt/local/bin/python, but only /opt/local/bin/python2.5? Is there a better workaround than my symbolic link? And I guess another lesson here is that installing a package in multiple locations can lead to confusion. No surprise there. What is the MacPorts strategy to deal with a situation where OSX comes with some version of a package like python for which people will want to install add-ons? I'm assuming it is "Install our own copy in the usual locations in /opt/local, and depend on PATH and other environment variables to keep the MacPorts version from fighting with the OSX version, right? It's not very clean, but I'm sure we don't want MacPorts modifying OSX-supplied components. Thanks for reading this far. I hope my example might save somebody else some frustration. -- Phil Rand philrand at pobox.com , From raimue at macports.org Sun Jun 15 18:04:07 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Mon, 16 Jun 2008 03:04:07 +0200 Subject: Mercurial install after MacPython.app, Leopard, Google App Engine In-Reply-To: <5784c1b10806151721x72b85c74mbdf6ae5aa9a9452c@mail.gmail.com> References: <5784c1b10806151721x72b85c74mbdf6ae5aa9a9452c@mail.gmail.com> Message-ID: <4855BC07.3000004@macports.org> Phil Rand wrote: > [Dealing with a previous installation of python outside MacPorts] I don't know why py25-* failed for you, MacPorts sanitizes PATH for building, so it should really not use some version from outside. mercurial calls /opt/local/bin/python instead of /opt/local/bin/python2.5. This is ticket #14536 [1]. But this might be fixed by the new python25 port building as framework I created. > I uninstalled all the deps for mercurial, and installed python25. It > did not install /opt/local/bin/python, only /opt/local/bin/python2.5. > After that the python extensions py25-zlib, py25-hashlib, py25-bz2 > woudn't install until I created a symbolic link: cd /opt/local/bin; > ln -s python2.5 python > > Is it expected for the python25 port NOT to create > /opt/local/bin/python, but only /opt/local/bin/python2.5? Is there a > better workaround than my symbolic link? As we provide multiple versions, there is python_select (can be installed by the port of the same name) to create this symlink. $ sudo python_select python25 > And I guess another lesson here is that installing a package in > multiple locations can lead to confusion. No surprise there. > > What is the MacPorts strategy to deal with a situation where OSX comes > with some version of a package like python for which people will want > to install add-ons? I'm assuming it is "Install our own copy in the > usual locations in /opt/local, and depend on PATH and other > environment variables to keep the MacPorts version from fighting with > the OSX version, right? It's not very clean, but I'm sure we don't > want MacPorts modifying OSX-supplied components. We do not provide python modules for Apple's python, you need to install python from MacPorts as well. Reasons are given in the FAQ [2]. > Thanks for reading this far. I hope my example might save somebody > else some frustration. I can understand if you are frustrated here, the install is not as flawless as it could be. Rainer [1] http://trac.macports.org/ticket/14536 [2] http://trac.macports.org/wiki/FAQ#WillMacPortslinktosystemlibrariesratherthanitsown From philrand at gmail.com Sun Jun 15 21:54:18 2008 From: philrand at gmail.com (Phil Rand) Date: Sun, 15 Jun 2008 21:54:18 -0700 Subject: Mercurial install after MacPython.app, Leopard, Google App Engine In-Reply-To: <4855BC07.3000004@macports.org> References: <5784c1b10806151721x72b85c74mbdf6ae5aa9a9452c@mail.gmail.com> <4855BC07.3000004@macports.org> Message-ID: <5784c1b10806152154v492b952xa5916616f0057554@mail.gmail.com> On Sun, Jun 15, 2008 at 6:04 PM, Rainer M?ller wrote: [snip] > I can understand if you are frustrated here, the install is not as flawless > as it could be. > > Rainer Thanks, Rainer. I think MacPorts does amazingly well, given the complex problem it faces. -- Phil Rand philrand at pobox.com From j.van_den_hoff at fzd.de Mon Jun 16 03:18:29 2008 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Mon, 16 Jun 2008 12:18:29 +0200 Subject: python2.5 install failed In-Reply-To: <83A73F49-7CA7-4DF6-9F95-EAE2D2E313E6@macports.org> References: <20080613111137.GC7354@marco.fz-rossendorf.de> <83A73F49-7CA7-4DF6-9F95-EAE2D2E313E6@macports.org> Message-ID: <20080616101829.GC15763@marco.fz-rossendorf.de> On Fri, Jun 13, 2008 at 02:52:25PM -0600, Bryan Blackburn wrote: > On Jun 13, 2008, at 5:11 AM, Joerg van den Hoff wrote: > > > hi, > > > > under 10.4.11 I did a `port upgrade mercurial'. > > > ... > > /usr/bin/libtool -o libpython2.5.dylib -dynamic \ > > -all_load libpython2.5.a -single_module \ > > -install_name /opt/local/lib/libpython2.5.dylib \ > > -compatibility_version 2.5 \ > > -current_version 2.5 -lSystem -lSystemStubs -L/opt/local/lib > > ld64 failed: in libpython2.5.a(getbuildinfo.o), not a valid ppc64 > > mach-o file > > /usr/bin/libtool: internal link edit command failed > > make: *** [libpython2.5.dylib] Error 1 > > Check your Xcode version, and see: > > > > Bryan > indeed. had'nt checked Xcode for quite some time. thank's a lot! question: could'nt/should'nt `port' check the Xcode version itself and issue a complain if it's too old? joerg From LenoreHorner at sbcglobal.net Mon Jun 16 11:26:01 2008 From: LenoreHorner at sbcglobal.net (Lenore Horner) Date: Mon, 16 Jun 2008 13:26:01 -0500 Subject: numpy error Message-ID: <6E67A826-0C3D-4FC1-A305-8CF5D659A22E@sbcglobal.net> I'm installing Gnumeric as the first port on a brand new MacPorts installation on an Intel iMac. The ProblemsHotlist and LeopardProblems pages have gotten me through several hiccups, but now I've got something I don't remember seeing on this mailing list. Numpy failed so I was going to clean and install which has fixed problems 2 or 3 times. However I get the following error that doesn't make sense to me. sudo port clean --all py25-numpy Password: ---> Cleaning py25-numpy Warning: Distfiles directory '/opt/local/var/macports/distfiles/ python' may contain distfiles needed for other ports, use the -f flag to force removal Why is it going to python rather than phython/py25-numpy? Thanks, Lenore Here's the barf that caused me to try cleaning. (I think it's the usual problem with Leopard.) ---> Verifying checksum(s) for py25-numpy ---> Checksumming numpy-1.1.0.tar.gz ---> Extracting py25-numpy ---> Extracting numpy-1.1.0.tar.gz ---> Applying patches to py25-numpy ---> Applying /opt/local/var/macports/sources/rsync.macports.org/ release/ports/python/py25-numpy/files/patch-g95_link.diff patching file numpy/distutils/fcompiler/g95.py ---> Configuring py25-numpy ---> Building py25-numpy with target build Running from numpy source directory. non-existing path in 'numpy/distutils': 'site.cfg' F2PY Version 2_5237 blas_opt_info: FOUND: extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] define_macros = [('NO_ATLAS_INFO', 3)] extra_compile_args = ['-msse3', '-I/System/Library/Frameworks/ vecLib.framework/Headers'] lapack_opt_info: FOUND: extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] define_macros = [('NO_ATLAS_INFO', 3)] extra_compile_args = ['-msse3'] running build running scons customize UnixCCompiler Could not locate executable -DNDEBUG error: Could not find compiler executable info for scons 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-numpy/work/numpy-1.1.0" && / opt/local/bin/python2.5 setup.py build " returned error 1 Command output: Running from numpy source directory. non-existing path in 'numpy/distutils': 'site.cfg' F2PY Version 2_5237 blas_opt_info: FOUND: extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] define_macros = [('NO_ATLAS_INFO', 3)] extra_compile_args = ['-msse3', '-I/System/Library/Frameworks/ vecLib.framework/Headers'] lapack_opt_info: FOUND: extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] define_macros = [('NO_ATLAS_INFO', 3)] extra_compile_args = ['-msse3'] running build running scons customize UnixCCompiler Could not locate executable -DNDEBUG error: Could not find compiler executable info for scons Warning: the following items did not execute (for py25-numpy): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: The following dependencies failed to build: py25-gtk py25-cairo py25-numpy Error: Status 1 encountered during processing. From LenoreHorner at sbcglobal.net Mon Jun 16 14:24:24 2008 From: LenoreHorner at sbcglobal.net (Lenore Horner) Date: Mon, 16 Jun 2008 16:24:24 -0500 Subject: numpy error In-Reply-To: <6E67A826-0C3D-4FC1-A305-8CF5D659A22E@sbcglobal.net> References: <6E67A826-0C3D-4FC1-A305-8CF5D659A22E@sbcglobal.net> Message-ID: > > Numpy failed so I was going to clean and install which has fixed > problems 2 or 3 times. However I get the following error that > doesn't make sense to me. > > sudo port clean --all py25-numpy > Password: > ---> Cleaning py25-numpy > Warning: Distfiles directory '/opt/local/var/macports/distfiles/ > python' may contain distfiles needed for other ports, use the -f > flag to force removal > > Why is it going to python rather than phython/py25-numpy? The problem seems to have been that there wasn't a py25-numpy in distfiles/python. I simply redid the install (even though clean had failed) and everything appears to be fine. Gnumeric is now installed. Lenore From ryandesign at macports.org Tue Jun 17 02:01:34 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 17 Jun 2008 04:01:34 -0500 Subject: numpy error In-Reply-To: <6E67A826-0C3D-4FC1-A305-8CF5D659A22E@sbcglobal.net> References: <6E67A826-0C3D-4FC1-A305-8CF5D659A22E@sbcglobal.net> Message-ID: <9FE26651-A052-4056-8AB1-F6E0639126D5@macports.org> On Jun 16, 2008, at 1:26 PM, Lenore Horner wrote: > I'm installing Gnumeric as the first port on a brand new MacPorts > installation on an Intel iMac. The ProblemsHotlist and > LeopardProblems pages have gotten me through several hiccups, but now > I've got something I don't remember seeing on this mailing list. > > Numpy failed so I was going to clean and install which has fixed > problems 2 or 3 times. However I get the following error that doesn't > make sense to me. > > sudo port clean --all py25-numpy > Password: > ---> Cleaning py25-numpy > Warning: Distfiles directory '/opt/local/var/macports/distfiles/ > python' may contain distfiles needed for other ports, use the -f flag > to force removal > > Why is it going to python rather than phython/py25-numpy? > > Thanks, > Lenore > > Here's the barf that caused me to try cleaning. (I think it's the > usual problem with Leopard.) It does look like the usual Leopard environment variables issue, yes. You don't need to clean --all (which also cleans the downloaded distfiles, which are not corrupted and don't need to be cleaned). You just need to clean --work (which cleans only the work area). > ---> Verifying checksum(s) for py25-numpy > ---> Checksumming numpy-1.1.0.tar.gz > ---> Extracting py25-numpy > ---> Extracting numpy-1.1.0.tar.gz > ---> Applying patches to py25-numpy > ---> Applying /opt/local/var/macports/sources/rsync.macports.org/ > release/ports/python/py25-numpy/files/patch-g95_link.diff > patching file numpy/distutils/fcompiler/g95.py > ---> Configuring py25-numpy > ---> Building py25-numpy with target build > Running from numpy source directory. > non-existing path in 'numpy/distutils': 'site.cfg' > F2PY Version 2_5237 > blas_opt_info: > FOUND: > extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] > define_macros = [('NO_ATLAS_INFO', 3)] > extra_compile_args = ['-msse3', '-I/System/Library/Frameworks/ > vecLib.framework/Headers'] > > lapack_opt_info: > FOUND: > extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] > define_macros = [('NO_ATLAS_INFO', 3)] > extra_compile_args = ['-msse3'] > > running build > running scons > customize UnixCCompiler > Could not locate executable -DNDEBUG > error: Could not find compiler executable info for scons > 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-numpy/work/numpy-1.1.0" && / > opt/local/bin/python2.5 setup.py build " returned error 1 > Command output: Running from numpy source directory. > non-existing path in 'numpy/distutils': 'site.cfg' > F2PY Version 2_5237 > blas_opt_info: > FOUND: > extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] > define_macros = [('NO_ATLAS_INFO', 3)] > extra_compile_args = ['-msse3', '-I/System/Library/Frameworks/ > vecLib.framework/Headers'] > > lapack_opt_info: > FOUND: > extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] > define_macros = [('NO_ATLAS_INFO', 3)] > extra_compile_args = ['-msse3'] > > running build > running scons > customize UnixCCompiler > Could not locate executable -DNDEBUG > error: Could not find compiler executable info for scons > > Warning: the following items did not execute (for py25-numpy): > org.macports.activate org.macports.build org.macports.destroot > org.macports.install > Error: The following dependencies failed to build: py25-gtk py25-cairo > py25-numpy > Error: Status 1 encountered during processing. From ryandesign at macports.org Tue Jun 17 02:04:45 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 17 Jun 2008 04:04:45 -0500 Subject: python2.5 install failed In-Reply-To: <20080616101829.GC15763@marco.fz-rossendorf.de> References: <20080613111137.GC7354@marco.fz-rossendorf.de> <83A73F49-7CA7-4DF6-9F95-EAE2D2E313E6@macports.org> <20080616101829.GC15763@marco.fz-rossendorf.de> Message-ID: On Jun 16, 2008, at 5:18 AM, Joerg van den Hoff wrote: > question: could'nt/should'nt `port' check the Xcode version itself and > issue a complain if it's too old? Yes, that would be wonderful. I filed a request for that some time ago but it hasn't really been implemented yet: http;//trac.macports.org/ticket/12794 From raimue at macports.org Tue Jun 17 03:11:16 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Tue, 17 Jun 2008 12:11:16 +0200 Subject: python2.5 install failed In-Reply-To: References: <20080613111137.GC7354@marco.fz-rossendorf.de> <83A73F49-7CA7-4DF6-9F95-EAE2D2E313E6@macports.org> <20080616101829.GC15763@marco.fz-rossendorf.de> Message-ID: <48578DC4.2020406@macports.org> Ryan Schmidt wrote: > On Jun 16, 2008, at 5:18 AM, Joerg van den Hoff wrote: > > >> question: could'nt/should'nt `port' check the Xcode version itself and >> issue a complain if it's too old? > > Yes, that would be wonderful. I filed a request for that some time > ago but it hasn't really been implemented yet: > > http;//trac.macports.org/ticket/12794 The source install checks the Xcode version on configure and warns if one is using an old version. I don't think the dmg installer does something like this. Checking the version on every run of port is not a good idea, especially not when we allow to choose other compilers through configure.compiler (or a new setting in macports.conf as I proposed recently). Bundling the check with the currently setting of configure.compiler could work. Maybe it would be enough to add this check to 'port selfupdate' (or a new 'port selfcheck'?). But we also have users with old MacPorts versions from time to time... Rainer From j.van_den_hoff at fzd.de Tue Jun 17 03:29:11 2008 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Tue, 17 Jun 2008 12:29:11 +0200 Subject: python2.5 install failed In-Reply-To: <48578DC4.2020406@macports.org> References: <20080613111137.GC7354@marco.fz-rossendorf.de> <83A73F49-7CA7-4DF6-9F95-EAE2D2E313E6@macports.org> <20080616101829.GC15763@marco.fz-rossendorf.de> <48578DC4.2020406@macports.org> Message-ID: <20080617102911.GB15744@marco.fz-rossendorf.de> On Tue, Jun 17, 2008 at 12:11:16PM +0200, Rainer M?ller wrote: > Ryan Schmidt wrote: > >On Jun 16, 2008, at 5:18 AM, Joerg van den Hoff wrote: > > > > > >>question: could'nt/should'nt `port' check the Xcode version itself and > >>issue a complain if it's too old? > > > >Yes, that would be wonderful. I filed a request for that some time > >ago but it hasn't really been implemented yet: > > > >http;//trac.macports.org/ticket/12794 > > The source install checks the Xcode version on configure and warns if > one is using an old version. I don't think the dmg installer does > something like this. > > Checking the version on every run of port is not a good idea, especially > not when we allow to choose other compilers through configure.compiler > (or a new setting in macports.conf as I proposed recently). Bundling the > check with the currently setting of configure.compiler could work. > > Maybe it would be enough to add this check to 'port selfupdate' (or a > new 'port selfcheck'?). But we also have users with old MacPorts > versions from time to time... that's true (happened to me, too...). but the adivice "first run port selfupdate and look whether problem goes away" is seen so often that most people will try this sooner or later anyway. so, I'd say a check at `port selfupdate' time would probably "solve" 95-99% of all cases where the Xcode version problem arises. joerg > > Rainer From martin at siarp.de Wed Jun 18 01:34:51 2008 From: martin at siarp.de (Martin Stadler) Date: Wed, 18 Jun 2008 10:34:51 +0200 Subject: python24 +puredarwin Message-ID: <19D19D53-FE3A-4782-A99B-BC235DEADFEA@siarp.de> Hi! I'm using python24 with the puredarwin variant because it seems to fit better with virtual python, easy install and Plone. Then I upgraded my Python and now it looks like the puredarwin variant was not used. Now I uninstalled and cleaned everything and tried to install but I get an error: MartinsMacBook:~ martin$ sudo port install python24 +puredarwin ---> Fetching python24 ---> Attempting to fetch Python-2.4.5.tgz from http://www.python.org/ftp/python/2.4.5/ ---> Verifying checksum(s) for python24 ---> Extracting python24 ---> Applying patches to python24 ---> Configuring python24 ---> Building python24 with target all libpython2.4.dylib ---> Staging python24 into destroot Error: Target org.macports.destroot returned: no such file or directory Error: Status 1 encountered during processing. Installing Python without puredarwin works perfectly. Any idea? Martin From martin at siarp.de Wed Jun 18 06:37:47 2008 From: martin at siarp.de (Martin Stadler) Date: Wed, 18 Jun 2008 15:37:47 +0200 Subject: python24 +puredarwin In-Reply-To: <53C97F16-4DA6-41D0-874B-201A5F91B7BE@gmail.com> References: <19D19D53-FE3A-4782-A99B-BC235DEADFEA@siarp.de> <53C97F16-4DA6-41D0-874B-201A5F91B7BE@gmail.com> Message-ID: <744A546B-514C-42D6-9425-E472F2D0E542@siarp.de> I'm not shure about the details but Python is installed as a OS X framework in /opt/local/Library/Frameworks/Python.framework Python packages are not installed in the standard site-packages directory and virtual python[1] is not working with setuptools this way. Martin [1] http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python Am 18.06.2008 um 15:11 schrieb Kenneth Miller: > Martin, > > I've never used the +puredarwin option, what does it give you? I > just generally use "sudo port install python24" > > Regards, > Ken > > On Jun 18, 2008, at 3:34 AM, Martin Stadler wrote: > >> Hi! >> >> I'm using python24 with the puredarwin variant because it seems to >> fit >> better with virtual python, easy install and Plone. Then I upgraded >> my >> Python and now it looks like the puredarwin variant was not used. Now >> I uninstalled and cleaned everything and tried to install but I get >> an >> error: >> >> MartinsMacBook:~ martin$ sudo port install python24 +puredarwin >> ---> Fetching python24 >> ---> Attempting to fetch Python-2.4.5.tgz from http://www.python.org/ftp/python/2.4.5/ >> ---> Verifying checksum(s) for python24 >> ---> Extracting python24 >> ---> Applying patches to python24 >> ---> Configuring python24 >> ---> Building python24 with target all libpython2.4.dylib >> ---> Staging python24 into destroot >> Error: Target org.macports.destroot returned: no such file or >> directory >> Error: Status 1 encountered during processing. >> >> Installing Python without puredarwin works perfectly. Any idea? >> >> Martin >> >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > From raimue at macports.org Wed Jun 18 06:49:28 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Wed, 18 Jun 2008 15:49:28 +0200 Subject: python24 +puredarwin In-Reply-To: <744A546B-514C-42D6-9425-E472F2D0E542@siarp.de> References: <19D19D53-FE3A-4782-A99B-BC235DEADFEA@siarp.de> <53C97F16-4DA6-41D0-874B-201A5F91B7BE@gmail.com> <744A546B-514C-42D6-9425-E472F2D0E542@siarp.de> Message-ID: <48591268.3050200@macports.org> Martin Stadler wrote: > I'm not shure about the details but Python is installed as a OS X > framework in > /opt/local/Library/Frameworks/Python.framework > > Python packages are not installed in the standard site-packages > directory and virtual python[1] is not working with setuptools this way. This will hopefully be resolved with the new python ports building as framework. If you are curious to try them out right now, you can find the Portfiles for them in svn [1]. Any comments if these work for you are appreciated. Rainer [1] http://svn.macports.org/repository/macports/branches/python-frameworks/dports/lang/ From martin at siarp.de Wed Jun 18 07:33:59 2008 From: martin at siarp.de (Martin Stadler) Date: Wed, 18 Jun 2008 16:33:59 +0200 Subject: python24 +puredarwin In-Reply-To: <48591268.3050200@macports.org> References: <19D19D53-FE3A-4782-A99B-BC235DEADFEA@siarp.de> <53C97F16-4DA6-41D0-874B-201A5F91B7BE@gmail.com> <744A546B-514C-42D6-9425-E472F2D0E542@siarp.de> <48591268.3050200@macports.org> Message-ID: Am 18.06.2008 um 15:49 schrieb Rainer M?ller: > Martin Stadler wrote: >> I'm not shure about the details but Python is installed as a OS X >> framework in >> /opt/local/Library/Frameworks/Python.framework >> Python packages are not installed in the standard site-packages >> directory and virtual python[1] is not working with setuptools this >> way. > > This will hopefully be resolved with the new python ports building > as framework. If you are curious to try them out right now, you can > find the Portfiles for them in svn [1]. > > Any comments if these work for you are appreciated. > > Rainer > > [1] http://svn.macports.org/repository/macports/branches/python-frameworks/dports/lang/ > I added file:///Users/martin/ports to sources.conf. I copied the files from svn to ~/ports/lang/python24/. ### $ cd ports $ portindex ### -> successfully parsed: 1 ### $ sudo port install python24 $ python2.4 virtual-python.py --prefix=~/py_i18n Creating /Users/martin/py_i18n/lib/python2.4 Creating /Users/martin/py_i18n/lib/python2.4/site-packages Creating /Users/martin/py_i18n/include/python2.4 Creating /Users/martin/py_i18n/bin Copying /opt/local/Library/Frameworks/Python.framework/Versions/2.4/ Resources/Python.app/Contents/MacOS/Python to /Users/martin/py_i18n/bin You're now ready to download ez_setup.py, and run /Users/martin/py_i18n/bin/python ez_setup.py $ /Users/martin/py_i18n/bin/python ez_setup.py Downloading http://pypi.python.org/packages/2.4/s/setuptools/setuptools-0.6c8-py2.4.egg error: can't create or remove files in install directory The following error occurred while trying to add or remove files in the installation directory: [Errno 13] Permission denied: '/opt/local/Library/Frameworks/ Python.framework/Versions/2.4/lib/python2.4/site-packages/test-easy- install-68344.write-test' The installation directory you specified (via --install-dir, --prefix, or the distutils default setting) was: /opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/ python2.4/site-packages/ Perhaps your account does not have write access to this directory? If the installation directory is a system-owned directory, you may need to sign in as the administrator or "root" account. If you do not have administrative access to this machine, you may wish to choose a different installation directory, preferably one that is listed in your PYTHONPATH environment variable. For information on other options, you may wish to consult the documentation at: http://peak.telecommunity.com/EasyInstall.html Please make the appropriate changes for your system and try again. ### I think the installation directory should be ~/py_i18n/lib/python2.4/site-packages/ I believe it used to work this way. Martin OS X 10.5.3 MacPorts 1.6.0 Intel From xkenneth at gmail.com Wed Jun 18 07:35:32 2008 From: xkenneth at gmail.com (Kenneth Miller) Date: Wed, 18 Jun 2008 09:35:32 -0500 Subject: python24 +puredarwin In-Reply-To: <744A546B-514C-42D6-9425-E472F2D0E542@siarp.de> References: <19D19D53-FE3A-4782-A99B-BC235DEADFEA@siarp.de> <53C97F16-4DA6-41D0-874B-201A5F91B7BE@gmail.com> <744A546B-514C-42D6-9425-E472F2D0E542@siarp.de> Message-ID: Martin, What do you mean by the standard site-packages directory. The system python and the macports python are going to completely different locations. Virtual python? You mean Virtualenv? Regards, Ken On Jun 18, 2008, at 8:37 AM, Martin Stadler wrote: > I'm not shure about the details but Python is installed as a OS X > framework in > /opt/local/Library/Frameworks/Python.framework > > Python packages are not installed in the standard site-packages > directory and virtual python[1] is not working with setuptools this > way. > > Martin > > [1] http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python > > > Am 18.06.2008 um 15:11 schrieb Kenneth Miller: > >> Martin, >> >> I've never used the +puredarwin option, what does it give you? I >> just generally use "sudo port install python24" >> >> Regards, >> Ken >> >> On Jun 18, 2008, at 3:34 AM, Martin Stadler wrote: >> >>> Hi! >>> >>> I'm using python24 with the puredarwin variant because it seems to >>> fit >>> better with virtual python, easy install and Plone. Then I >>> upgraded my >>> Python and now it looks like the puredarwin variant was not used. >>> Now >>> I uninstalled and cleaned everything and tried to install but I >>> get an >>> error: >>> >>> MartinsMacBook:~ martin$ sudo port install python24 +puredarwin >>> ---> Fetching python24 >>> ---> Attempting to fetch Python-2.4.5.tgz from http://www.python.org/ftp/python/2.4.5/ >>> ---> Verifying checksum(s) for python24 >>> ---> Extracting python24 >>> ---> Applying patches to python24 >>> ---> Configuring python24 >>> ---> Building python24 with target all libpython2.4.dylib >>> ---> Staging python24 into destroot >>> Error: Target org.macports.destroot returned: no such file or >>> directory >>> Error: Status 1 encountered during processing. >>> >>> Installing Python without puredarwin works perfectly. Any idea? >>> >>> Martin >>> >>> _______________________________________________ >>> macports-users mailing list >>> macports-users at lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users >> >> > From frstan at bellsouth.net Wed Jun 18 09:58:58 2008 From: frstan at bellsouth.net (William Davis) Date: Wed, 18 Jun 2008 12:58:58 -0400 Subject: typo in rubygems? Message-ID: <509284C9-0F88-4AA5-AA82-489C4A634C97@bellsouth.net> When upgrading rb-rubygems, I noticed the following: install -c -m 0644 ubygems.rb /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_ruby_rb-rubygems/work/destroot/opt/local/ lib/ubygems.rb note: that is "ubygems.rb" appearing twice. Is this correct? William Davis frstanATbellsouthDOTnet Mac OS X.5.3 Darwin 9.3.0 Xquartz 2.2.2 - (xorg-server 1.3.0-apple21) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From kuepper.jochen at googlemail.com Wed Jun 18 06:54:06 2008 From: kuepper.jochen at googlemail.com (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Wed, 18 Jun 2008 15:54:06 +0200 Subject: Portfile syntax: copying complete directory Message-ID: Hi, so in Ticket #15049 I proposed a patch to install man-files and info- pages of gcc-4.3 in a custom location in order to get them installed without conflicts between different gcc version. However, the line file copy ${destroot}${prefix}/share/man/man7/* ${destroot}${prefix}/ share/gcc43/man/man7 now causes the destroot to fail, as reported in Ticket #15666. What would be the correct Portfile code instead of the following? # move manuals to gcc43-specific directory xinstall -m 755 -d ${destroot}${prefix}/share/gcc43/man/man7 xinstall -m 755 -d ${destroot}${prefix}/share/gcc43/info file copy ${destroot}${prefix}/share/man/man7/* ${destroot}${prefix}/ share/gcc43/man/man7 file copy ${destroot}${prefix}/share/info/* ${destroot}${prefix}/share/ gcc43/info 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: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080618/18ab98c5/attachment.sig From blb at macports.org Wed Jun 18 13:35:02 2008 From: blb at macports.org (Bryan Blackburn) Date: Wed, 18 Jun 2008 14:35:02 -0600 Subject: Portfile syntax: copying complete directory In-Reply-To: References: Message-ID: On Jun 18, 2008, at 7:54 AM, Jochen K?pper wrote: > Hi, > > so in Ticket #15049 I proposed a patch to install man-files and info- > pages of gcc-4.3 in a custom location in order to get them installed > without conflicts between different gcc version. > > However, the line > file copy ${destroot}${prefix}/share/man/man7/* ${destroot}${prefix}/ > share/gcc43/man/man7 > now causes the destroot to fail, as reported in Ticket #15666. > What would be the correct Portfile code instead of the following? > > # move manuals to gcc43-specific directory > xinstall -m 755 -d ${destroot}${prefix}/share/gcc43/man/man7 > xinstall -m 755 -d ${destroot}${prefix}/share/gcc43/info > file copy ${destroot}${prefix}/share/man/man7/* ${destroot}${prefix}/ > share/gcc43/man/man7 > file copy ${destroot}${prefix}/share/info/* ${destroot}${prefix}/ > share/gcc43/info > You need to glob it, and since some things (like xinstall at least, don't remember about file copy) don't like the return from glob, eval the whole thing. For example, from the lzo2 Portfile [1]: eval xinstall -m 0644 [glob ${worksrcpath}/doc/*] ${destroot}$ {docdir} So for gcc43: eval xinstall -m 0644 [glob ${destroot}${prefix}/share/man/man7/*] ${destroot}${prefix}/share/gcc43/man/man7 eval xinstall -m 0644 [glob ${destroot}${prefix}/share/info/*] $ {destroot}${prefix}/share/gcc43/info should do it (warning, only tested with Mail.app). Bryan [1] - > > 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 martin at siarp.de Wed Jun 18 13:43:41 2008 From: martin at siarp.de (Martin Stadler) Date: Wed, 18 Jun 2008 22:43:41 +0200 Subject: python24 +puredarwin In-Reply-To: References: <19D19D53-FE3A-4782-A99B-BC235DEADFEA@siarp.de> <53C97F16-4DA6-41D0-874B-201A5F91B7BE@gmail.com> <744A546B-514C-42D6-9425-E472F2D0E542@siarp.de> Message-ID: <5D977C97-492F-48F5-A497-3361DCE2687A@siarp.de> Am 18.06.2008 um 16:06 schrieb Mike: > What advantage is there to using python from ports vs the native osx > python installation in /usr/bin/ ? > > -mike Well, using Macports I follow the philosophy not to play around (install additional packages i.e.) with the system frameworks but having everything separate. Anyway, there's no Python 2.4 in Mac OS X 10.5 - simple as that. Martin From evilensky at gmail.com Wed Jun 18 20:46:15 2008 From: evilensky at gmail.com (Eugene Vilensky) Date: Wed, 18 Jun 2008 22:46:15 -0500 Subject: configure: error: ./configure failed for glib-1.2.10 Message-ID: Hello everyone, I have searched Trac, Google, and the list archives; I can't build any ports from a clean install because it seems like my base dependencies refuse to build. I am using an svn trunk from just a few hours ago, in desperation, but the same failure happens to almost any port I try with 1.6.0: checking size of char... configure: error: cannot compute sizeof (char) See `config.log' for more details. configure: error: ./configure failed for glib-1.2.10 This machine is a Time Machine full-restore...I've reinstalled the developer tools just in case. Any ideas? Thanks everyone, Eugene Vilensky -------------- next part -------------- A non-text attachment was scrubbed... Name: config.log Type: application/octet-stream Size: 56004 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080618/1e866b72/attachment.obj From ryandesign at macports.org Wed Jun 18 21:01:47 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 18 Jun 2008 23:01:47 -0500 Subject: configure: error: ./configure failed for glib-1.2.10 In-Reply-To: References: Message-ID: On Jun 18, 2008, at 10:46 PM, Eugene Vilensky wrote: > I have searched Trac, Google, and the list archives; I can't build any > ports from a clean install because it seems like my base dependencies > refuse to build. > > I am using an svn trunk from just a few hours ago, in desperation, but > the same failure happens to almost any port I try with 1.6.0: > > > checking size of char... configure: error: cannot compute sizeof > (char) > See `config.log' for more details. > configure: error: ./configure failed for glib-1.2.10 > > This machine is a Time Machine full-restore...I've reinstalled the > developer tools just in case. What version of Mac OS X and Xcode do you have? Do you have DYLD_LIBRARY_PATH or DYLD_FALLBACK_LIBRARY_PATH or LD_LIBRARY_PATH set, and if so to what? (Type "env" to check.) From ryandesign at macports.org Wed Jun 18 21:06:00 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 18 Jun 2008 23:06:00 -0500 Subject: configure: error: ./configure failed for glib-1.2.10 In-Reply-To: References: Message-ID: On Jun 18, 2008, at 11:01 PM, Ryan Schmidt wrote: > On Jun 18, 2008, at 10:46 PM, Eugene Vilensky wrote: > >> I have searched Trac, Google, and the list archives; I can't build >> any >> ports from a clean install because it seems like my base dependencies >> refuse to build. >> >> I am using an svn trunk from just a few hours ago, in desperation, >> but >> the same failure happens to almost any port I try with 1.6.0: >> >> >> checking size of char... configure: error: cannot compute sizeof >> (char) >> See `config.log' for more details. >> configure: error: ./configure failed for glib-1.2.10 >> >> This machine is a Time Machine full-restore...I've reinstalled the >> developer tools just in case. > > What version of Mac OS X and Xcode do you have? Nevermind that... I see the answer in your attachment: configure:2124: checking Mac OS X version configure:2127: result: 10.5.3 configure:2152: checking Xcode version configure:2155: result: 3.0 But you attached the config.log from installing MacPorts itself, whereas the config.log that will tell us what why you had a problem building glib is the one generated by trying to install glib. This file should be in the glib port's worksrcdir. You can get there by typing: cd `port dir glib`/work/glib-1.2.10 Why do you need glib 1.2.10, by the way? The current version of glib is in the glib2 port. glib 1.2.10 is old and may not be expected to work on Leopard. From evilensky at gmail.com Wed Jun 18 21:45:46 2008 From: evilensky at gmail.com (Eugene Vilensky) Date: Wed, 18 Jun 2008 23:45:46 -0500 Subject: configure: error: ./configure failed for glib-1.2.10 In-Reply-To: References: Message-ID: > Why do you need glib 1.2.10, by the way? The current version of glib is in > the glib2 port. glib 1.2.10 is old and may not be expected to work on > Leopard. I was actually trying to install xeyes as a test, which told me I was missing pkgconfig. Here is a bunch of the output. I'm pretty lost; the last time I had a need for macports, everything 'just worked'. Thanks for taking a look! supermac:base evilensky$ sudo port install xeyes ---> Fetching xeyes ---> Attempting to fetch xeyes-1.0.1.tar.bz2 from http://distfiles.macports.org/xeyes ---> Verifying checksum(s) for xeyes ---> Extracting xeyes ---> Configuring xeyes 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_x11_xeyes/work/xeyes-1.0.1" && ./configure --prefix=/opt/local --mandir=/opt/local/share/man " returned error 1 Command output: checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... /usr/bin/gcc-4.0 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 /usr/bin/gcc-4.0 accepts -g... yes checking for /usr/bin/gcc-4.0 option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of /usr/bin/gcc-4.0... gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking for pkg-config... no checking for XEYES... configure: error: The pkg-config script could not be found or is too old. Make sure it is in your PATH or set the PKG_CONFIG environment variable to the full path to pkg-config. Alternatively, you may set the environment variables XEYES_CFLAGS and XEYES_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. To get pkg-config, see . See `config.log' for more details. Error: Status 1 encountered during processing. Then: supermac:base evilensky$ sudo port install pkgconfig ---> Fetching pkgconfig ---> Attempting to fetch pkg-config-0.23.tar.gz from http://www.vg.kernel.org/pub/mirrors/gentoo/source/distfiles/ ---> Verifying checksum(s) for pkgconfig ---> Extracting pkgconfig ---> Configuring pkgconfig 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_devel_pkgconfig/work/pkg-config-0.23" && ./configure --prefix=/opt/local --enable-indirect-deps " returned error 1 Command output: mkdir: out: File exists rmdir: out: Directory not empty rmdir: conftest: Directory not empty yes checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/i686-apple-darwin9/4.0.1/ld) supports shared libraries... yes checking dynamic linker characteristics... darwin9.3.0 dyld checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking whether to enable maintainer-specific portions of Makefiles... no checking host system type... (cached) i386-apple-darwin9.3.0 checking whether to enable memory checking... no checking whether to enable memory profiling... no checking for gcc... (cached) /usr/bin/gcc-4.0 checking whether we are using the GNU C compiler... (cached) yes checking whether /usr/bin/gcc-4.0 accepts -g... (cached) yes checking for /usr/bin/gcc-4.0 option to accept ISO C89... (cached) none needed checking dependency style of /usr/bin/gcc-4.0... (cached) gcc3 checking for /usr/bin/gcc-4.0 option to accept ANSI C... none needed checking for a BSD-compatible install... /usr/bin/install -c checking for extra flags to get ANSI library prototypes... configure: WARNING: No ANSI prototypes found in library. (-std1 didn't work.) checking for extra flags for POSIX compliance... none needed checking for ANSI C header files... (cached) yes checking for vprintf... no checking for atexit... no checking for on_exit... no checking for char... yes checking size of char... configure: error: cannot compute sizeof (char) See `config.log' for more details. configure: error: ./configure failed for glib-1.2.10 Error: Status 1 encountered during processing. supermac:~ evilensky$ sudo port install glib1 ---> Fetching expat ---> Attempting to fetch expat-2.0.1.tar.gz from http://internap.dl.sourceforge.net/expat ---> Verifying checksum(s) for expat ---> Extracting expat ---> Configuring expat ---> Building expat 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_textproc_expat/work/expat-2.0.1" && gnumake all " returned error 2 Command output: /bin/sh ./libtool --silent --mode=compile /usr/bin/gcc-4.0 -I./lib -I. -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -I/opt/local/include -DHAVE_EXPAT_CONFIG_H -o lib/xmlparse.lo -c lib/xmlparse.c lib/xmlparse.c:81:2: error: #error memmove does not exist on this platform, nor is a substitute available gnumake: *** [lib/xmlparse.lo] Error 1 Error: The following dependencies failed to build: gettext expat libiconv gperf ncurses ncursesw pkgconfig Error: Status 1 encountered during processing. supermac:~ evilensky$ sudo port install glib2 ---> Building expat 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_textproc_expat/work/expat-2.0.1" && gnumake all " returned error 2 Command output: /bin/sh ./libtool --silent --mode=compile /usr/bin/gcc-4.0 -I./lib -I. -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -I/opt/local/include -DHAVE_EXPAT_CONFIG_H -o lib/xmlparse.lo -c lib/xmlparse.c lib/xmlparse.c:81:2: error: #error memmove does not exist on this platform, nor is a substitute available gnumake: *** [lib/xmlparse.lo] Error 1 Error: The following dependencies failed to build: gettext expat libiconv gperf ncurses ncursesw pkgconfig Error: Status 1 encountered during processing. From ryandesign at macports.org Wed Jun 18 22:49:52 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 19 Jun 2008 00:49:52 -0500 Subject: configure: error: ./configure failed for glib-1.2.10 In-Reply-To: References: Message-ID: On Jun 18, 2008, at 11:45 PM, Eugene Vilensky wrote: >> Why do you need glib 1.2.10, by the way? The current version of >> glib is in >> the glib2 port. glib 1.2.10 is old and may not be expected to work on >> Leopard. > > I was actually trying to install xeyes as a test, which told me I was > missing pkgconfig. > > Here is a bunch of the output. I'm pretty lost; the last time I had a > need for macports, everything 'just worked'. > > Thanks for taking a look! > > supermac:base evilensky$ sudo port install xeyes > ---> Fetching xeyes > ---> Attempting to fetch xeyes-1.0.1.tar.bz2 from > http://distfiles.macports.org/xeyes > ---> Verifying checksum(s) for xeyes > ---> Extracting xeyes > ---> Configuring xeyes [snip] > checking for pkg-config... no > checking for XEYES... configure: error: The pkg-config script could > not be found or is too old. Make sure it > is in your PATH or set the PKG_CONFIG environment variable to the full > path to pkg-config. > > Alternatively, you may set the environment variables XEYES_CFLAGS > and XEYES_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > > To get pkg-config, see pkgconfig>. > See `config.log' for more details. > > Error: Status 1 encountered during processing. Ok. xeyes does not declare a dependency on pkgconfig and clearly needs to. I filed a bug: http://trac.macports.org/ticket/15674 You can Cc yourself there if you want to be informed when it's resolved. > Then: > > > supermac:base evilensky$ sudo port install pkgconfig > ---> Fetching pkgconfig > ---> Attempting to fetch pkg-config-0.23.tar.gz from > http://www.vg.kernel.org/pub/mirrors/gentoo/source/distfiles/ > ---> Verifying checksum(s) for pkgconfig > ---> Extracting pkgconfig > ---> Configuring pkgconfig > 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_devel > _pkgconfig/work/pkg-config-0.23" > && ./configure --prefix=/opt/local --enable-indirect-deps " returned > error 1 > Command output: mkdir: out: File exists > rmdir: out: Directory not empty > rmdir: conftest: Directory not empty > yes > checking whether the /usr/bin/g++-4.0 linker > (/usr/libexec/gcc/i686-apple-darwin9/4.0.1/ld) supports shared > libraries... yes > checking dynamic linker characteristics... darwin9.3.0 dyld > checking how to hardcode library paths into programs... immediate > appending configuration tag "F77" to libtool > checking whether to enable maintainer-specific portions of > Makefiles... no > checking host system type... (cached) i386-apple-darwin9.3.0 > checking whether to enable memory checking... no > checking whether to enable memory profiling... no > checking for gcc... (cached) /usr/bin/gcc-4.0 > checking whether we are using the GNU C compiler... (cached) yes > checking whether /usr/bin/gcc-4.0 accepts -g... (cached) yes > checking for /usr/bin/gcc-4.0 option to accept ISO C89... (cached) > none needed > checking dependency style of /usr/bin/gcc-4.0... (cached) gcc3 > checking for /usr/bin/gcc-4.0 option to accept ANSI C... none needed > checking for a BSD-compatible install... /usr/bin/install -c > checking for extra flags to get ANSI library prototypes... > configure: WARNING: No ANSI prototypes found in library. (-std1 > didn't work.) > checking for extra flags for POSIX compliance... none needed > checking for ANSI C header files... (cached) yes > checking for vprintf... no > checking for atexit... no > checking for on_exit... no > checking for char... yes > checking size of char... configure: error: cannot compute sizeof > (char) > See `config.log' for more details. > configure: error: ./configure failed for glib-1.2.10 > > Error: Status 1 encountered during processing. Oh I see. We're not talking about the glib (1) port, but the glib that's included inside the pkgconfig source. pkgconfig is like oxygen so it has to work on all our supported platforms. I know it should work on Leopard. I'm not sure why it's blowing up like this for you. I'll have to reboot to Leopard and reinstall pkgconfig and compare my verbose output with yours above. We may want to see more output than what's shown above. You should attach the config.log from the failed pkgconfig install attempt, and also you should try to install pkgconfig with the debug flag to get more output and send us all the output. sudo port clean --work pkgconfig sudo port -d install pkgconfig 2>&1 | tee ~/Desktop/pkgconfig.out Then send us pkgconfig.out on your Desktop. > supermac:~ evilensky$ sudo port install glib1 > ---> Fetching expat > ---> Attempting to fetch expat-2.0.1.tar.gz from > http://internap.dl.sourceforge.net/expat > ---> Verifying checksum(s) for expat > ---> Extracting expat > ---> Configuring expat > ---> Building expat 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_textp > roc_expat/work/expat-2.0.1" > && gnumake all " returned error 2 > Command output: /bin/sh ./libtool --silent --mode=compile > /usr/bin/gcc-4.0 -I./lib -I. -O2 -Wall -Wmissing-prototypes > -Wstrict-prototypes -I/opt/local/include -DHAVE_EXPAT_CONFIG_H -o > lib/xmlparse.lo -c lib/xmlparse.c > lib/xmlparse.c:81:2: error: #error memmove does not exist on this > platform, nor is a substitute available > gnumake: *** [lib/xmlparse.lo] Error 1 > > Error: The following dependencies failed to build: gettext expat > libiconv gperf ncurses ncursesw pkgconfig > Error: Status 1 encountered during processing. expat is also a rather central and important dependency which also must work on Leopard, and does for me, so I don't know why this isn't working for you. I see one report like this here: https://sourceforge.net/tracker/? func=detail&atid=110127&aid=1647805&group_id=10127 But I don't really see a solution listed there. Can you try uninstalling Xcode (using the script provided by Apple) and then installing Xcode again? Not sure what else to try, short of an OS reinstall... From Damien at Clauzel.nom.fr Thu Jun 19 02:47:43 2008 From: Damien at Clauzel.nom.fr (Damien Clauzel) Date: Thu, 19 Jun 2008 11:47:43 +0200 Subject: [darkstat] Improvement for MacOS Message-ID: <1213868863.31930.7.camel@liristpq.Univ-Lyon1.fr> Hi all, ?I have been briefly working with the creator of darkstat, Emil Mikulic, for improving the use of this software of MacOS. The idea is to have darkstat working nicely as a clean service. For doing this, Emil have made some changes in the code for adding a new option (--no-daemon, see attached patch) for preventing darkstat to fork when started, and I have created a launchd plist config file for setting up darkstat as a MacOS service (without the need of third part tools like daemonic). The method I am using is to drop a service file into /Library/LaunchDaemons/ (see attached document), and let launchd do its job. This approach means that darkstat run as a system wide service. The trick is just to use a different label for each distribution (fink and macports) in order to avoid conflict in case darkstat is installed from both of them (not a smart move, but anyway...) What I would like to do is to validate those modifications with both of the fink and macports mainteneurs of darkstat, and to make a new release (so I can have it directly on my machines without the need of patching manually; yes, I am lazy :) What do you think of all of this? Damien Clauzel -------------- next part -------------- A non-text attachment was scrubbed... Name: darkstat.patch-no-daemon.patch Type: text/x-patch Size: 5242 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080619/fc578b01/attachment.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: DISTRIB.darkstat.plist Type: application/xml Size: 644 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080619/fc578b01/attachment.xml -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?= Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080619/fc578b01/attachment.sig From graef at ebi.ac.uk Thu Jun 19 09:38:00 2008 From: graef at ebi.ac.uk (=?ISO-8859-1?Q?Stefan_Gr=E4f?=) Date: Thu, 19 Jun 2008 17:38:00 +0100 Subject: Problem installing metacity Message-ID: <485A8B68.8000809@ebi.ac.uk> Hi there, It seems like there are some packages in the dependency list that are missing. Any help is very much appreciated. Cheers, Stefan ---> Configuring metacity 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_gnome_metacity/work/metacity-2.22.0" && ./configure --prefix=/opt/local --mandir=/opt/local/share/man --disable-scrollkeeper --x-libraries=/usr/X11R6/lib --x-includes=/usr/X11R6/include " returned error 1 Command output: checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... /opt/local/bin/msgfmt checking for xgettext... /opt/local/bin/xgettext checking for pkg-config... /opt/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for ALL... yes checking for METACITY_MESSAGE... yes checking for METACITY_WINDOW_DEMO... yes pangoxft found checking Startup notification library >= 0.7... yes Building with libstartup-notification checking Xcomposite >= 0.2... no Building compositing manager by default now. Building with CompositeExt checking Xcursor... yes Building with Xcursor checking for METACITY... configure: error: Package requirements (gtk+-2.0 >= 2.10.0 pango >= 1.2.0 gconf-2.0 >= 1.2.0 libstartup-notification-1.0 >= 0.7 xcomposite >= 0.2 xfixes xrender xdamage xcursor) were not met: No package 'xcomposite' found No package 'xfixes' found No package 'xdamage' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables METACITY_CFLAGS and METACITY_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. Error: Status 1 encountered during processing. From william at gallaf.net Thu Jun 19 10:20:12 2008 From: william at gallaf.net (William Gallafent) Date: Thu, 19 Jun 2008 18:20:12 +0100 Subject: GraphicsMagick Message-ID: <6D883A91-BD30-48B0-8926-F1293DEDDD97@gallaf.net> I would like to request that the GraphicsMagick port be updated to version 1.2.3. I have manually installed this version from the upstream tarball without any problem, so I'm guessing that it should be straightforward to update the macport. How should I proceed with this request? (I notice that the macports trac requires a login to open a new ticket ... how do I get a login to do so?) Thanks, -- Bill Gallafent. From raimue at macports.org Thu Jun 19 10:29:37 2008 From: raimue at macports.org (=?UTF-8?B?UmFpbmVyIE3DvGxsZXI=?=) Date: Thu, 19 Jun 2008 19:29:37 +0200 Subject: [darkstat] Improvement for MacOS In-Reply-To: <1213868863.31930.7.camel@liristpq.Univ-Lyon1.fr> References: <1213868863.31930.7.camel@liristpq.Univ-Lyon1.fr> Message-ID: <485A9781.4050904@macports.org> Damien Clauzel wrote: > ?I have been briefly working with the creator of darkstat, Emil Mikulic, > for improving the use of this software of MacOS. The idea is to have > darkstat working nicely as a clean service. I am CC'ing the maintainer of darkstat in MacPorts. > For doing this, Emil have made some changes in the code for adding a new > option (--no-daemon, see attached patch) for preventing darkstat to fork > when started, and I have created a launchd plist config file for setting > up darkstat as a MacOS service (without the need of third part tools > like daemonic). > > The method I am using is to drop a service file > into /Library/LaunchDaemons/ (see attached document), and let launchd do > its job. This approach means that darkstat run as a system wide service. Have a look at startupitem.* commands for Portfiles, they can already create most of this stuff automatically for you. > The trick is just to use a different label for each distribution (fink > and macports) in order to avoid conflict in case darkstat is installed > from both of them (not a smart move, but anyway...) Yes, we usually use 'org.macports.' (e.g. 'org.macports.apache2') and others. > What I would like to do is to validate those modifications with both of > the fink and macports mainteneurs of darkstat, and to make a new release > (so I can have it directly on my machines without the need of patching > manually; yes, I am lazy :) > > What do you think of all of this? As usual: Patch welcomed ;-) Rainer From ryandesign at macports.org Thu Jun 19 10:58:42 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 19 Jun 2008 12:58:42 -0500 Subject: [darkstat] Improvement for MacOS In-Reply-To: <1213868863.31930.7.camel@liristpq.Univ-Lyon1.fr> References: <1213868863.31930.7.camel@liristpq.Univ-Lyon1.fr> Message-ID: <214E1487-B7BB-4EEC-81B5-5BB3B4EE86F2@macports.org> On Jun 19, 2008, at 4:47 AM, Damien Clauzel wrote: > I have been briefly working with the creator of darkstat, Emil > Mikulic, > for improving the use of this software of MacOS. The idea is to have > darkstat working nicely as a clean service. > > For doing this, Emil have made some changes in the code for adding > a new > option (--no-daemon, see attached patch) for preventing darkstat to > fork > when started, and I have created a launchd plist config file for > setting > up darkstat as a MacOS service (without the need of third part tools > like daemonic). > > The method I am using is to drop a service file > into /Library/LaunchDaemons/ (see attached document), and let > launchd do > its job. This approach means that darkstat run as a system wide > service. > > The trick is just to use a different label for each distribution (fink > and macports) in order to avoid conflict in case darkstat is installed > from both of them (not a smart move, but anyway...) > > What I would like to do is to validate those modifications with > both of > the fink and macports mainteneurs of darkstat, and to make a new > release > (so I can have it directly on my machines without the need of patching > manually; yes, I am lazy :) For MacPorts you would generally use the startupitem directives to have MacPorts create a launchd plist for you. See the Guide: http://guide.macports.org/#reference.startupitems From Damien at Clauzel.nom.fr Thu Jun 19 11:23:55 2008 From: Damien at Clauzel.nom.fr (Damien Clauzel) Date: Thu, 19 Jun 2008 20:23:55 +0200 Subject: [darkstat] Improvement for MacOS In-Reply-To: <214E1487-B7BB-4EEC-81B5-5BB3B4EE86F2@macports.org> References: <1213868863.31930.7.camel@liristpq.Univ-Lyon1.fr> <214E1487-B7BB-4EEC-81B5-5BB3B4EE86F2@macports.org> Message-ID: <8305F379-6DCE-4528-BE74-2B916BC83095@Clauzel.nom.fr> Le 19 juin 08 ? 19:58, Ryan Schmidt a ?crit : > For MacPorts you would generally use the startupitem directives to > have MacPorts create a launchd plist for you. See the Guide: > > http://guide.macports.org/#reference.startupitems Yes, I saw that, but I couldn't find information about how to setup various parameters in the plist. For example, I am using things like : ___ UserName root KeepAlive RunAtLoad Nice 1 ___ It is far more easier for me to just write the plist and to drop it in /Library/LaunchDaemons/ than to try to understand what exactly daemondo is, and how it interacts with launchd. I don't really see what is the purpose of daemondo for running services, because launchd does already have everything that is needed for managing them. Am I missing something there ? Damien -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080619/54c42a90/attachment.sig From floss-survey at inf.fu-berlin.de Thu Jun 19 03:34:18 2008 From: floss-survey at inf.fu-berlin.de (FLOSS Survey - Free University Berlin, Institute of CS) Date: Thu, 19 Jun 2008 12:34:18 +0200 Subject: Survey request: Survey on contributor's activities in OS/FS projects (Free University of Berlin) Message-ID: <485A362A.1010603@inf.fu-berlin.de> Dear community member, in cooperation with the software engineering research group at Free University of Berlin (Freie Universit?t Berlin), we are currently conducting an empirical survey on time consumption of participants in Open Source/Free Software projects. In this survey we want to find out how much time is consumed in the different activities and aspects of Open Source/Free Software projects, such as software development, documenting, maintaining or user support. We would greatly appreciate you participating in our survey! This survey will take you no more than 15 minutes of your precious time. It is now open and will be closed in 10 days. Note on data security: This survey is anonymous, so no personal information will be asked. As a gift in return we will share our insights with you (an URL is shown at completion of the survey). The Link to the survey: http://page.mi.fu-berlin.de/pepper/survey/ Thank You!!! Contact: floss-survey at inf.fu-berlin.de From olabuschagne at growthpathanalytics.com Thu Jun 19 12:36:43 2008 From: olabuschagne at growthpathanalytics.com (Ockert Labuschagne) Date: Thu, 19 Jun 2008 14:36:43 -0500 Subject: No subject Message-ID: <008901c8d243$d1ceec60$756cc520$@com> I have mono 1.9.1 and MacPorts for Leopard installed on a PPC mac running OSX Leopard. When I run sudo port install mono I eventually get: ---> Building mono with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macport s.org_release_ports_devel_mono/work/mono-1.9.1" && make all " returned error 2 Command output: darwin_stop_world.c:259: error: 'ppc_thread_state_t' has no member named '__r6' darwin_stop_world.c:260: error: 'ppc_thread_state_t' has no member named '__r7' darwin_stop_world.c:261: error: 'ppc_thread_state_t' has no member named '__r8' darwin_stop_world.c:262: error: 'ppc_thread_state_t' has no member named '__r9' darwin_stop_world.c:263: error: 'ppc_thread_state_t' has no member named '__r10' darwin_stop_world.c:264: error: 'ppc_thread_state_t' has no member named '__r11' darwin_stop_world.c:265: error: 'ppc_thread_state_t' has no member named '__r12' darwin_stop_world.c:266: error: 'ppc_thread_state_t' has no member named '__r13' darwin_stop_world.c:267: error: 'ppc_thread_state_t' has no member named '__r14' darwin_stop_world.c:268: error: 'ppc_thread_state_t' has no member named '__r15' darwin_stop_world.c:269: error: 'ppc_thread_state_t' has no member named '__r16' darwin_stop_world.c:270: error: 'ppc_thread_state_t' has no member named '__r17' darwin_stop_world.c:271: error: 'ppc_thread_state_t' has no member named '__r18' darwin_stop_world.c:272: error: 'ppc_thread_state_t' has no member named '__r19' darwin_stop_world.c:273: error: 'ppc_thread_state_t' has no member named '__r20' darwin_stop_world.c:274: error: 'ppc_thread_state_t' has no member named '__r21' darwin_stop_world.c:275: error: 'ppc_thread_state_t' has no member named '__r22' darwin_stop_world.c:276: error: 'ppc_thread_state_t' has no member named '__r23' darwin_stop_world.c:277: error: 'ppc_thread_state_t' has no member named '__r24' darwin_stop_world.c:278: error: 'ppc_thread_state_t' has no member named '__r25' darwin_stop_world.c:279: error: 'ppc_thread_state_t' has no member named '__r26' darwin_stop_world.c:280: error: 'ppc_thread_state_t' has no member named '__r27' darwin_stop_world.c:281: error: 'ppc_thread_state_t' has no member named '__r28' darwin_stop_world.c:282: error: 'ppc_thread_state_t' has no member named '__r29' darwin_stop_world.c:283: error: 'ppc_thread_state_t' has no member named '__r30' darwin_stop_world.c:284: error: 'ppc_thread_state_t' has no member named '__r31' make[3]: *** [darwin_stop_world.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: Status 1 encountered during processing. According to the Mono developers this is a MacPorts issue that was fixed before. I ran the same on an Intel Mac with Tiger (OSX 10.4) installed and it did not throw an error. How do I get around this? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080619/0ef9a905/attachment.htm From jmr at macports.org Thu Jun 19 14:09:25 2008 From: jmr at macports.org (Joshua Root) Date: Fri, 20 Jun 2008 07:09:25 +1000 Subject: Problem installing metacity In-Reply-To: <485A8B68.8000809@ebi.ac.uk> References: <485A8B68.8000809@ebi.ac.uk> Message-ID: <485ACB05.7030109@macports.org> Stefan Gr?f wrote: > Hi there, > > It seems like there are some packages in the dependency list that are > missing. Any help is very much appreciated. > > Cheers, > Stefan > > ---> Configuring metacity > > No package 'xcomposite' found > No package 'xfixes' found > No package 'xdamage' found These are X extensions which are present in Apple's X11 on Leopard but not on earlier OS X versions. It might be possible to create ports for them, but that has not been done at present. Metacity should theoretically be able to work without them, but nobody has yet been able to figure out a way to make it build in their absence. See: - Josh From graef at ebi.ac.uk Thu Jun 19 14:59:15 2008 From: graef at ebi.ac.uk (=?UTF-8?B?U3RlZmFuIEdyw6Rm?=) Date: Thu, 19 Jun 2008 22:59:15 +0100 Subject: Problem installing metacity In-Reply-To: <485ACB05.7030109@macports.org> References: <485A8B68.8000809@ebi.ac.uk> <485ACB05.7030109@macports.org> Message-ID: <485AD6B3.6000402@ebi.ac.uk> Thanks Josh, So, what is your suggestion then if you don't want to upgrade to leopard yet? Is there any alternative to make gnome work properly? Stefan Joshua Root wrote: > Stefan Gr?f wrote: >> Hi there, >> >> It seems like there are some packages in the dependency list that are >> missing. Any help is very much appreciated. >> >> Cheers, >> Stefan >> >> ---> Configuring metacity > >> >> No package 'xcomposite' found >> No package 'xfixes' found >> No package 'xdamage' found > > These are X extensions which are present in Apple's X11 on Leopard but > not on earlier OS X versions. It might be possible to create ports for > them, but that has not been done at present. Metacity should > theoretically be able to work without them, but nobody has yet been able > to figure out a way to make it build in their absence. > > See: > > - Josh From pyle129 at policeone.com Thu Jun 19 15:16:03 2008 From: pyle129 at policeone.com (Brent Austin) Date: Thu, 19 Jun 2008 15:16:03 -0700 Subject: After install - Unable to so "sudo port" anything Message-ID: <20080619151603.977DAF83@resin11.mta.everyone.net> An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080619/09fc42d5/attachment.htm From frstan at bellsouth.net Thu Jun 19 16:53:04 2008 From: frstan at bellsouth.net (William Davis) Date: Thu, 19 Jun 2008 19:53:04 -0400 Subject: After install - Unable to so "sudo port" anything In-Reply-To: <20080619151603.977DAF83@resin11.mta.everyone.net> References: <20080619151603.977DAF83@resin11.mta.everyone.net> Message-ID: You need to add this to your ~/.profile file: # Setting the path for MacPorts. export PATH=/opt/local/bin:/opt/local/sbin:$PATH Due to a bug the installer doesnt do this for ver 1.6. Dont know why it hasnt been fixed. good luck On Jun 19, 2008, at 6:16 PM, Brent Austin wrote: > I've installed the latest MacPorts for Leopard (on Mac Pro Leopard > 10.5.3). When I go to Terminal to "sudo port selfupdate" all I get > is an invalid commad for "port". > Any ideas, advice? > thanks > -Brent > > > Sign up for FREE email from PoliceOne.com at http://www.policeone.com > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users William Davis frstanATbellsouthDOTnet Mac OS X.5.3 Darwin 9.3.0 Xquartz 2.2.3 - (xorg-server 1.3.0-apple21) 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/20080619/0ac5d8fc/attachment.htm From pyle129 at policeone.com Thu Jun 19 17:10:47 2008 From: pyle129 at policeone.com (Brent Austin) Date: Thu, 19 Jun 2008 17:10:47 -0700 Subject: After install - Unable to so "sudo port" anything Message-ID: <20080619171047.977C49AF@resin11.mta.everyone.net> An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080619/8a251123/attachment.htm From frstan at bellsouth.net Thu Jun 19 17:19:08 2008 From: frstan at bellsouth.net (William Davis) Date: Thu, 19 Jun 2008 20:19:08 -0400 Subject: After install - Unable to so "sudo port" anything In-Reply-To: <20080619171047.977C49AF@resin11.mta.everyone.net> References: <20080619171047.977C49AF@resin11.mta.everyone.net> Message-ID: <648C103A-289F-4E85-9879-B6E6F4BE40FC@bellsouth.net> sure, it's in your home directory -- that's what the "~" is short for. something like /Users/Austin/.profile or whatever your username is. On Jun 19, 2008, at 8:10 PM, Brent Austin wrote: > OK no problem.....could you be a bit more specific on where > the .profile file is? > thanks > -Brent > > --- frstan at bellsouth.net wrote: > > From: William Davis > To: pyle129 at policeone.com > Cc: > Subject: Re: After install - Unable to so "sudo port" anything > Date: Thu, 19 Jun 2008 19:53:04 -0400 > > You need to add this to your ~/.profile file: > > # Setting the path for MacPorts. > export PATH=/opt/local/bin:/opt/local/sbin:$PATH > > Due to a bug the installer doesnt do this for ver 1.6. Dont know why > it hasnt been fixed. > good luck > > On Jun 19, 2008, at 6:16 PM, Brent Austin wrote: > > I've installed the latest MacPorts for Leopard (on Mac Pro Leopard > 10.5.3). When I go to Terminal to "sudo port selfupdate" all I get > is an invalid commad for "port". > Any ideas, advice? > thanks > -Brent > > > Sign up for FREE email from PoliceOne.com at http://www.policeone.com > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > > > William Davis > frstanATbellsouthDOTnet > Mac OS X.5.3 Darwin 9.3.0 > Xquartz 2.2.3 - (xorg-server 1.3.0-apple21) > Mac Mini Intel Duo @ 1.86 GHz > > Mundus vult decepi, ego non > > > > Sign up for FREE email from PoliceOne.com at http://www.policeone.com William Davis frstanATbellsouthDOTnet Mac OS X.5.3 Darwin 9.3.0 Xquartz 2.2.3 - (xorg-server 1.3.0-apple21) 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/20080619/7c1af59c/attachment.htm From ryandesign at macports.org Thu Jun 19 20:55:30 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 19 Jun 2008 22:55:30 -0500 Subject: GraphicsMagick In-Reply-To: <6D883A91-BD30-48B0-8926-F1293DEDDD97@gallaf.net> References: <6D883A91-BD30-48B0-8926-F1293DEDDD97@gallaf.net> Message-ID: <2123AC93-BABD-45D0-A5B8-9006E5CC3B73@macports.org> On Jun 19, 2008, at 12:20 PM, William Gallafent wrote: > I would like to request that the GraphicsMagick port be updated to > version 1.2.3. I have manually installed this version from the > upstream tarball without any problem, so I'm guessing that it should > be straightforward to update the macport. How should I proceed with > this request? (I notice that the macports trac requires a login to > open a new ticket ... how do I get a login to do so?) I'll see about updating the port. In the future, we'd like you to file tickets in Trac. To get a login, click Register at the upper right of any Trac screen. From ryandesign at macports.org Thu Jun 19 23:41:27 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 20 Jun 2008 01:41:27 -0500 Subject: GraphicsMagick In-Reply-To: <2123AC93-BABD-45D0-A5B8-9006E5CC3B73@macports.org> References: <6D883A91-BD30-48B0-8926-F1293DEDDD97@gallaf.net> <2123AC93-BABD-45D0-A5B8-9006E5CC3B73@macports.org> Message-ID: <485538D4-2BF7-4A7E-BFBE-FC3404EDD9A4@macports.org> On Jun 19, 2008, at 10:55 PM, Ryan Schmidt wrote: > On Jun 19, 2008, at 12:20 PM, William Gallafent wrote: > >> I would like to request that the GraphicsMagick port be updated to >> version 1.2.3. I have manually installed this version from the >> upstream tarball without any problem, so I'm guessing that it should >> be straightforward to update the macport. How should I proceed with >> this request? (I notice that the macports trac requires a login to >> open a new ticket ... how do I get a login to do so?) > > I'll see about updating the port. In the future, we'd like you to > file tickets in Trac. To get a login, click Register at the upper > right of any Trac screen. Ok, GraphicsMagick 1.2.3 is now in the repository. Wait 12 hours, then "sudo port selfupdate" to get the new port definition, then "sudo port install GraphicsMagick" (or if you already had an earlier version installed, "sudo port upgrade GraphicsMagick"). From Damien at Clauzel.nom.fr Fri Jun 20 04:59:42 2008 From: Damien at Clauzel.nom.fr (Damien Clauzel) Date: Fri, 20 Jun 2008 13:59:42 +0200 Subject: [dia] cannot compile : configure: error: perl not found; required for intltool Message-ID: Hi, On Leopard, with everything up to date : ___ $ port install dia ---> Configuring dia 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_gnome_dia/work/dia-0.96.1" && ./configure --prefix=/opt/local --mandir=/opt/local/share/man --infodir=/opt/local/ share/info --enable-static " returned error 1 Command output: checking dynamic linker characteristics... darwin9.3.0 dyld checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking whether build environment is sane... yes checking for a BSD-compatible install... /usr/bin/install checking whether ln -s works... yes checking whether make sets $(MAKE)... (cached) yes checking for library containing strerror... none required checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for ANSI C header files... (cached) yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for unistd.h... (cached) yes checking utime.h usability... yes checking utime.h presence... yes checking for utime.h... yes checking for an ANSI C-conforming const... yes checking for select... yes checking for strcspn... yes checking for strdup... yes checking for strtol... yes checking for snprintf... yes checking for intltool >= 0.21... 0.35.0 found checking for perl... (cached) no configure: error: perl not found; required for intltool Error: Status 1 encountered during processing. $ /opt/local/bin/perl --version This is perl, v5.8.8 built for darwin-2level Copyright 1987-2006, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using "man perl" or "perldoc perl". If you have access to the Internet, point your browser at http://www.perl.org/, the Perl Home Page. ___ So perl is present, but configure fails. Any idea on how to solve this ? Best, Damien Clauzel -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080620/f3dfd684/attachment.sig From bxf4 at u.washington.edu Fri Jun 20 08:46:34 2008 From: bxf4 at u.washington.edu (Brian Flaherty) Date: Fri, 20 Jun 2008 08:46:34 -0700 Subject: [dia] cannot compile : configure: error: perl not found; required for intltool In-Reply-To: References: Message-ID: <20080620154633.GA700@camus.local> On Fri, Jun 20, 2008 at 01:59:42PM +0200, Damien Clauzel wrote: > Hi, > > On Leopard, with everything up to date : ... > ___ > $ port install dia > ---> Configuring dia ... > ___ > > So perl is present, but configure fails. Any idea on how to solve this ? This looks a lot like problems I was having on my laptop. If you go to the dia directory (cd `port dir dia`, I think) and look at the config.log. What are the paths? In my case, PREFIX was not being handled correctly and appeared in the config.log. My guess is that it should have been /opt/local/. One thing I did just to get things installed, was to do it by hand. This is my recollection of how: - change to the work directory for dia - look at the Portfile for dia to see if there are any configure arguments (I just looked at it and there are a fair number of arguments and I don't know where they all go. Also, there's a patch file to apply, and I'm not sure I know how to do that by hand.) - run sudo ./configure --configure-args-from-portfile - run sudo make - run sudo make install This worked for me several times. However, I got sick of doing it after a while. I could not find the source of the problem. (There are past messages to MacPorts Users list from me on these problems.) For several reasons, I ended up formatting the disk and reinstalling Leopard. (I had upgraded from Tiger to Leopard, not re-formatted and installed Leopard on a clean drive before.) I haven't had the problem since. xfig is a very good drawing program, if you don't mind the X-windows interface. Brian From Damien at Clauzel.nom.fr Fri Jun 20 09:23:33 2008 From: Damien at Clauzel.nom.fr (Damien Clauzel) Date: Fri, 20 Jun 2008 18:23:33 +0200 Subject: [dia] cannot compile : configure: error: perl not found; required for intltool In-Reply-To: <20080620154633.GA700@camus.local> References: <20080620154633.GA700@camus.local> Message-ID: <7AB84C31-52EA-4472-9D2A-40FF1E23DEE8@Clauzel.nom.fr> Le 20 juin 08 ? 17:46, Brian Flaherty a ?crit : >> perl is present, but configure fails. Any idea on how to solve >> this ? > > This looks a lot like problems I was having on my laptop. If you go > to the dia directory (cd `port dir dia`, I think) and look at the > config.log. What are the paths? In my case, PREFIX was not being > handled correctly and appeared in the config.log. My guess is that it > should have been /opt/local/. I am attaching the log file for full reference (/opt/local/var/ macports/sources/rsync.macports.org/release/ports/gnome/dia/work/ dia-0.96.1/config.log) > One thing I did just to get things installed, was to do it by hand. > This is my recollection of how: > > - change to the work directory for dia > - look at the Portfile for dia to see if there are any configure > arguments (I just looked at it and there are a fair number of > arguments and I don't know where they all go. Also, there's a patch > file to apply, and I'm not sure I know how to do that by hand.) > - run sudo ./configure --configure-args-from-portfile Didn't work for me. But I can successfully do this : ___ /opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/ dia/work/dia-0.96.1 $ ./configure --prefix=/opt/local [SNIP] Configuration: Source code location: . Compiler: gcc Gnome support: no Python support: no Libart support (PNG export): yes Cairo support (experimental): no Gnome Print support (experimental): no Now type make to build dia... ___ Then the compilation fails near the end : ___ Making all in po /opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/ dia/work/dia-0.96.1/po file=`echo am | sed 's,.*/,,'`.gmo \ && rm -f $file && -o $file am.po /bin/sh: -o: command not found make[2]: *** [am.gmo] Error 127 make[1]: *** [all-recursiv ___ Obviously, a variable is missing. Damien -------------- next part -------------- A non-text attachment was scrubbed... Name: config.log Type: application/octet-stream Size: 45790 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080620/acee3729/attachment.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080620/acee3729/attachment.sig From jmr at macports.org Fri Jun 20 10:24:39 2008 From: jmr at macports.org (Joshua Root) Date: Sat, 21 Jun 2008 03:24:39 +1000 Subject: Problem installing metacity In-Reply-To: <485AD6B3.6000402@ebi.ac.uk> References: <485A8B68.8000809@ebi.ac.uk> <485ACB05.7030109@macports.org> <485AD6B3.6000402@ebi.ac.uk> Message-ID: <485BE7D7.3080004@macports.org> Stefan Gr?f wrote: > Thanks Josh, > > So, what is your suggestion then if you don't want to upgrade to leopard > yet? Is there any alternative to make gnome work properly? I don't know. Making Tiger-XFree86-compatible xcomposite, xfixes and xdamage ports might be the quickest way forward, followed by asking upstream to make the build work without them. - Josh From bxf4 at u.washington.edu Fri Jun 20 10:34:15 2008 From: bxf4 at u.washington.edu (Brian Flaherty) Date: Fri, 20 Jun 2008 10:34:15 -0700 Subject: [dia] cannot compile : configure: error: perl not found; required for intltool In-Reply-To: <7AB84C31-52EA-4472-9D2A-40FF1E23DEE8@Clauzel.nom.fr> References: <20080620154633.GA700@camus.local> <7AB84C31-52EA-4472-9D2A-40FF1E23DEE8@Clauzel.nom.fr> Message-ID: <20080620173415.GB31948@stendahl.psych.washington.edu> On Fri, Jun 20, 2008 at 06:23:33PM +0200, Damien Clauzel wrote: > Le 20 juin 08 ? 17:46, Brian Flaherty a ?crit : > >>> perl is present, but configure fails. Any idea on how to solve this >>> ? >> >> This looks a lot like problems I was having on my laptop. If you go >> to the dia directory (cd `port dir dia`, I think) and look at the >> config.log. What are the paths? In my case, PREFIX was not being >> handled correctly and appeared in the config.log. My guess is that it >> should have been /opt/local/. > I am attaching the log file for full reference (/opt/local/var/ > macports/sources/rsync.macports.org/release/ports/gnome/dia/work/ > dia-0.96.1/config.log) I think your paths look right, so it is a different problem than what I had. >> One thing I did just to get things installed, was to do it by hand. >> This is my recollection of how: >> >> - change to the work directory for dia >> - look at the Portfile for dia to see if there are any configure >> arguments (I just looked at it and there are a fair number of >> arguments and I don't know where they all go. Also, there's a patch >> file to apply, and I'm not sure I know how to do that by hand.) >> - run sudo ./configure --configure-args-from-portfile > Didn't work for me. There were several compiler flags in the Portfile. Did you get all those into the build environment? > But I can successfully do this : > ___ > /opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/ > dia/work/dia-0.96.1 $ ./configure --prefix=/opt/local When you did this, did configure find perl? If so, then I think that means there's something different between your shell environment and the MacPort's build environment. One person suggested I check if any variables in macports.conf that could interfere (/opt/local/etc/macports/macports.conf on my system). If that's the case, is there some way to fully compare the two shell environments? > [SNIP] > > Configuration: > Source code location: . > Compiler: gcc > > Gnome support: no > Python support: no > Libart support (PNG export): yes > Cairo support (experimental): no > Gnome Print support (experimental): no > > Now type make to build dia... > > ___ > > Then the compilation fails near the end : > ___ > Making all in po > /opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/ > dia/work/dia-0.96.1/po > file=`echo am | sed 's,.*/,,'`.gmo \ > && rm -f $file && -o $file am.po > /bin/sh: -o: command not found > make[2]: *** [am.gmo] Error 127 > make[1]: *** [all-recursiv > ___ > > Obviously, a variable is missing. I don't know where to go from here. Sorry I couldn't be of more help. Brian From Damien at Clauzel.nom.fr Fri Jun 20 10:56:10 2008 From: Damien at Clauzel.nom.fr (Damien Clauzel) Date: Fri, 20 Jun 2008 19:56:10 +0200 Subject: [dia] cannot compile : configure: error: perl not found; required for intltool In-Reply-To: <20080620173415.GB31948@stendahl.psych.washington.edu> References: <20080620154633.GA700@camus.local> <7AB84C31-52EA-4472-9D2A-40FF1E23DEE8@Clauzel.nom.fr> <20080620173415.GB31948@stendahl.psych.washington.edu> Message-ID: Le 20 juin 08 ? 19:34, Brian Flaherty a ?crit : >>> One thing I did just to get things installed, was to do it by hand. >>> This is my recollection of how: >>> >>> - change to the work directory for dia >>> - look at the Portfile for dia to see if there are any configure >>> arguments (I just looked at it and there are a fair number of >>> arguments and I don't know where they all go. Also, there's a patch >>> file to apply, and I'm not sure I know how to do that by hand.) >>> - run sudo ./configure --configure-args-from-portfile >> Didn't work for me. > > There were several compiler flags in the Portfile. Did you get all > those into the build environment? Yes. >> But I can successfully do this : >> ___ >> /opt/local/var/macports/sources/rsync.macports.org/release/ports/ >> gnome/ >> dia/work/dia-0.96.1 $ ./configure --prefix=/opt/local > > When you did this, did configure find perl? Yes. > If so, then I think that means there's something different between > your shell environment and > the MacPort's build environment. One person suggested I check if any > variables in macports.conf that could interfere > (/opt/local/etc/macports/macports.conf on my system). If that's the > case, is there some way to fully compare the two shell environments? Sure : ___ $ env MANPATH=/sw/share/man:/usr/share/man:/usr/local/share/man:/usr/X11/ man:/sw/lib/perl5/5.8.8/man:/usr/X11R6/man:/usr/local/man:/opt/local/ share/man:/Users/ltp/share/man:/usr/local/man:/opt/local/share/man:/ var/root/share/man SSH_AGENT_PID=478 TERM_PROGRAM=Apple_Terminal XDG_DATA_HOME=/var/root/.local/share GPG_AGENT_INFO=/tmp/gpg-KiBvXm/S.gpg-agent:554:1 SHELL=/bin/sh TERM=xterm-color Apple_PubSub_Socket_Render=/tmp/launch-yRb4nh/Render PERL5LIB=/sw/lib/perl5:/sw/lib/perl5/darwin TERM_PROGRAM_VERSION=240 OLDPWD=/opt/local/var/macports/sources/rsync.macports.org/release/ ports/gnome/dia QTDIR=/sw/lib/qt3 ac_cv_path_INTLTOOL_PERL=/usr/bin/perl LC_ALL=fr_FR.UTF-8 XAPPLRESDIR=/sw/etc/app-defaults/ CDPATH=.:~:/sw/share/doc: USER=dclauzel SGML_CATALOG_FILES=/sw/etc/sgml/catalog COMMAND_MODE=unix2003 GDK_USE_XFT=1 SSH_AUTH_SOCK=/tmp/ssh-6GdWrCQuFr/agent.465 __CF_USER_TEXT_ENCODING=0x0:0:1 KDEDIR=/sw GNOME_DISABLE_CRASH_DIALOG=1 PAGER=less XDG_CONFIG_DIRS=/sw/etc/xdg PATH=/Users/root/bin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/ Developer/Tools/:/Users/ltp/bin:/opt/local/bin:/opt/local/sbin:/usr/ local/bin:/Developer/Tools/:/opt/local/bin:/opt/local/sbin:/sw/bin:/sw/ sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/ X11R6/bin:.:. XML_CATALOG_FILES=/sw/etc/xml/catalog PWD=/opt/local/var/macports/sources/rsync.macports.org/release/ports/ gnome/dia/work/dia-0.96.1 EDITOR=vim LANG=fr PS1=\! [\[\e[31;40;2m\]\u\[\e[0m\]@\[\e[34;40;2m\]\H\[\e[0m\]]\w $ HOME=/var/root SHLVL=2 XDG_CONFIG_HOME=/var/root/.config XDG_CACHE_HOME=/var/root/.cache LOGNAME=ltp LESS=I M q DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus- IfsvLN5CeC,guid=a14bb16f1eef24975080ac00485a955e XDG_DATA_DIRS=/sw/share LESSOPEN=|/sw/bin/lesspipe.sh %s BROWSER=lynx:w3m INFOPATH=/sw/share/info:/sw/info:/usr/share/info CVSEDITOR=/usr/bin/vim DISPLAY=:0 SECURITYSESSIONID=821630 G_BROKEN_FILENAMES=true _=/sw/bin/env ___ I have no idea how to debug this quickly. Perl is installed from MacOS, from fink as a dependance and from macport as well. Each install is separated, but maybe macport is troubled when it look for it. Other software that depend on perl (apache and so) don't have this problem. Damien Clauzel -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080620/ee5c9cf5/attachment.sig From ryandesign at macports.org Fri Jun 20 17:05:04 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 20 Jun 2008 19:05:04 -0500 Subject: [dia] cannot compile : configure: error: perl not found; required for intltool In-Reply-To: References: <20080620154633.GA700@camus.local> <7AB84C31-52EA-4472-9D2A-40FF1E23DEE8@Clauzel.nom.fr> <20080620173415.GB31948@stendahl.psych.washington.edu> Message-ID: On Jun 20, 2008, at 12:56 PM, Damien Clauzel wrote: > PATH=/Users/root/bin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/ > Developer/Tools/:/Users/ltp/bin:/opt/local/bin:/opt/local/sbin:/usr/ > local/bin:/Developer/Tools/:/opt/local/bin:/opt/local/sbin:/sw/bin:/ > sw/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/ > usr/X11R6/bin:.:. According to your PATH, you have MacPorts (/opt/local), and Fink (/ sw), and things manually installed in /usr/local. We do not recommend or generally support using MacPorts alongside another package manager (Fink) installed, or with things installed in /usr/local. Please remove them (easiest way: rename /sw to /sw-off and /usr/local to / usr/local-off), clean the affected port (sudo port clean --work foo) and try again. We recommend you install any software you need using MacPorts. If software you need is not in MacPorts, please file tickets requesting portfiles be created, or better yet provide portfiles if possible. Portfile creation instructions are in the guide at http://guide.macports.org/ From paulbeard at gmail.com Sat Jun 21 13:19:13 2008 From: paulbeard at gmail.com (paul beard) Date: Sat, 21 Jun 2008 13:19:13 -0700 Subject: dealing with ports that can't upgrade Message-ID: So I have this problem where I can't upgrade metacity until I get Leopard. Is there a way to have MacPorts simply ignore you don't want upgraded or that can't be upgraded? Something as simple as a .ignore file in the port directory or an entry in a list in ports.conf . . . In the case of metacity and other ports similarly situated, why not an OS version test, if it's confirmed that Tiger is not suitable build platform? -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080621/3fb8d074/attachment.htm From ryandesign at macports.org Sat Jun 21 14:08:01 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 21 Jun 2008 16:08:01 -0500 Subject: dealing with ports that can't upgrade In-Reply-To: References: Message-ID: On Jun 21, 2008, at 3:19 PM, paul beard wrote: > So I have this problem where I can't upgrade metacity until I get > Leopard. Is there a way to have MacPorts simply ignore you don't > want upgraded or that can't be upgraded? Something as simple as > a .ignore file in the port directory or an entry in a list in > ports.conf . . . There is no such feature at this time. > In the case of metacity and other ports similarly situated, why not > an OS version test, if it's confirmed that Tiger is not suitable > build platform? If the current version of metacity will not be fixed to work on pre- Leopard, then the port should error out on pre-Leopard OS versions, and the last Tiger-compatible version of metacity should be resurrected from the repository and reinstated as a separate port. But if the current metacity can be fixed to work on pre-Leopard, then that should be done instead. From paulbeard at gmail.com Sat Jun 21 14:12:57 2008 From: paulbeard at gmail.com (paul beard) Date: Sat, 21 Jun 2008 14:12:57 -0700 Subject: dealing with ports that can't upgrade In-Reply-To: References: Message-ID: On Sat, Jun 21, 2008 at 2:08 PM, Ryan Schmidt wrote: > > On Jun 21, 2008, at 3:19 PM, paul beard wrote: > > So I have this problem where I can't upgrade metacity until I get Leopard. >> Is there a way to have MacPorts simply ignore you don't want upgraded or >> that can't be upgraded? Something as simple as a .ignore file in the port >> directory or an entry in a list in ports.conf . . . >> > > There is no such feature at this time. I suspected not: I'll make an RFE. > > > In the case of metacity and other ports similarly situated, why not an OS >> version test, if it's confirmed that Tiger is not suitable build platform? >> > > If the current version of metacity will not be fixed to work on > pre-Leopard, then the port should error out on pre-Leopard OS versions, and > the last Tiger-compatible version of metacity should be resurrected from the > repository and reinstated as a separate port. > I am actually working my way through that: looks like 2.21.2 works, where 2.22 fails. > > But if the current metacity can be fixed to work on pre-Leopard, then that > should be done instead. > > That sounds like a lot of work: something to do with X.org stuff that is leopard-specific. Seems to me that erroring out based on OS version is the cleanest way to go forward. -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080621/61256002/attachment.htm From ryandesign at macports.org Sat Jun 21 14:28:29 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 21 Jun 2008 16:28:29 -0500 Subject: dealing with ports that can't upgrade In-Reply-To: References: Message-ID: <57399BF2-F716-454A-9C33-81FFB22F7E1A@macports.org> On Jun 21, 2008, at 4:12 PM, paul beard wrote: > On Sat, Jun 21, 2008 at 2:08 PM, Ryan Schmidt wrote: > >> On Jun 21, 2008, at 3:19 PM, paul beard wrote: >> >>> So I have this problem where I can't upgrade metacity until I get >>> Leopard. Is there a way to have MacPorts simply ignore you don't >>> want upgraded or that can't be upgraded? Something as simple as >>> a .ignore file in the port directory or an entry in a list in >>> ports.conf . . . >> >> There is no such feature at this time. > > > I suspected not: I'll make an RFE. Do we really want people ignoring available upgrades? I don't think that's a good feature to add. >>> In the case of metacity and other ports similarly situated, why >>> not an OS version test, if it's confirmed that Tiger is not >>> suitable build platform? >> >> If the current version of metacity will not be fixed to work on >> pre-Leopard, then the port should error out on pre-Leopard OS >> versions, and the last Tiger-compatible version of metacity should >> be resurrected from the repository and reinstated as a separate port. > > > I am actually working my way through that: looks like 2.21.2 works, > where 2.22 fails. > >> But if the current metacity can be fixed to work on pre-Leopard, >> then that should be done instead. > > > That sounds like a lot of work: something to do with X.org stuff > that is leopard-specific. Seems to me that erroring out based on OS > version is the cleanest way to go forward. OK. Then something like this can be added to the metacity port: platform darwin 7 { pre-fetch { return -code error "${name} requires Mac OS X 10.5 or newer." } } platform darwin 8 { pre-fetch { return -code error "${name} requires Mac OS X 10.5 or newer." } } However, this will not prevent the port from showing up in the list of outdated ports, and it will not enable Tiger users to install the older version. For that, the older version of metacity would need to be broken out into a new port. From paulbeard at gmail.com Sat Jun 21 14:36:28 2008 From: paulbeard at gmail.com (paul beard) Date: Sat, 21 Jun 2008 14:36:28 -0700 Subject: dealing with ports that can't upgrade In-Reply-To: <57399BF2-F716-454A-9C33-81FFB22F7E1A@macports.org> References: <57399BF2-F716-454A-9C33-81FFB22F7E1A@macports.org> Message-ID: On Sat, Jun 21, 2008 at 2:28 PM, Ryan Schmidt wrote: > On Jun 21, 2008, at 4:12 PM, paul beard wrote: > > On Sat, Jun 21, 2008 at 2:08 PM, Ryan Schmidt wrote: >> >> On Jun 21, 2008, at 3:19 PM, paul beard wrote: >>> >>> So I have this problem where I can't upgrade metacity until I get >>>> Leopard. Is there a way to have MacPorts simply ignore you don't want >>>> upgraded or that can't be upgraded? Something as simple as a .ignore file in >>>> the port directory or an entry in a list in ports.conf . . . >>>> >>> >>> There is no such feature at this time. >>> >> >> >> I suspected not: I'll make an RFE. >> > > Do we really want people ignoring available upgrades? I don't think that's > a good feature to add. > If the upgrade doesn't install, why waste the cycles on it? And if a port's current version is the only one that works for a given use case, do we want to force an unwanted upgrade or force a user to downgrade it themselves? Assume that someone who is using MacPorts knows what they're doing: setting the ignore flag is not something that can be done by accident and it would be trivial to display a message listing the ignored ports, so the user could be reminded that they had thrown that switch. Let's not get in the habit of thinking for others. > > > In the case of metacity and other ports similarly situated, why not an OS >>>> version test, if it's confirmed that Tiger is not suitable build platform? >>>> >>> >>> If the current version of metacity will not be fixed to work on >>> pre-Leopard, then the port should error out on pre-Leopard OS versions, and >>> the last Tiger-compatible version of metacity should be resurrected from the >>> repository and reinstated as a separate port. >>> >> >> >> I am actually working my way through that: looks like 2.21.2 works, where >> 2.22 fails. >> >> But if the current metacity can be fixed to work on pre-Leopard, then >>> that should be done instead. >>> >> >> >> That sounds like a lot of work: something to do with X.org stuff that is >> leopard-specific. Seems to me that erroring out based on OS version is the >> cleanest way to go forward. >> > > OK. Then something like this can be added to the metacity port: > > > platform darwin 7 { > pre-fetch { > return -code error "${name} requires Mac OS X 10.5 or > newer." > } > } > platform darwin 8 { > pre-fetch { > return -code error "${name} requires Mac OS X 10.5 or > newer." > } > } > > > However, this will not prevent the port from showing up in the list of > outdated ports, and it will not enable Tiger users to install the older > version. For that, the older version of metacity would need to be broken out > into a new port. > > I leave this decision to the port's maintainers: ideally it would no longer show up in the list of outdated ports, because it really isn't outdated for that release of the OS. -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080621/2fdf86db/attachment.htm From raimue at macports.org Sat Jun 21 14:57:14 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sat, 21 Jun 2008 23:57:14 +0200 Subject: dealing with ports that can't upgrade In-Reply-To: References: <57399BF2-F716-454A-9C33-81FFB22F7E1A@macports.org> Message-ID: <485D793A.6050807@macports.org> paul beard wrote: > Do we really want people ignoring available upgrades? I don't think > that's a good feature to add. > > If the upgrade doesn't install, why waste the cycles on it? And if a > port's current version is the only one that works for a given use case, > do we want to force an unwanted upgrade or force a user to downgrade it > themselves? Assume that someone who is using MacPorts knows what they're > doing: setting the ignore flag is not something that can be done by > accident and it would be trivial to display a message listing the > ignored ports, so the user could be reminded that they had thrown that > switch. If the upgrade does not install it needs to be fixed. I don't think a ignore list would be really useful. I think you could just create a local repository with the old version of the port, overriding the version from the official tree. >[...] > I leave this decision to the port's maintainers: ideally it would no > longer show up in the list of outdated ports, because it really isn't > outdated for that release of the OS. Ideally you are requesting multiple versions of the same port here, so we could specify if they are working on a platform or not. That would mean the latest version for Tiger would be a different version than for Leopard. But currently there is only one version of a port for all platforms and we have to deal with it somehow. Splitting the port up in two separate ports would be a solution. A message to the users on Tiger would tell them about the new port they should use instead. Rainer From raimue at macports.org Sat Jun 21 15:30:41 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sun, 22 Jun 2008 00:30:41 +0200 Subject: dealing with ports that can't upgrade In-Reply-To: <485D793A.6050807@macports.org> References: <57399BF2-F716-454A-9C33-81FFB22F7E1A@macports.org> <485D793A.6050807@macports.org> Message-ID: <485D8111.4050807@macports.org> Rainer M?ller wrote: > I think you could just create a local repository with the old version of > the port, overriding the version from the official tree. Another possibility: $ sudo port upgrade outdated and not metacity This prevents the upgrade of metacity while applying all other upgrades. You would have to specify it every time doing upgrades, but already a lot better than having to specify a list of outdated ports manually. Rainer From garylaw at garylaw.net Sat Jun 21 16:46:10 2008 From: garylaw at garylaw.net (Gary Law) Date: Sun, 22 Jun 2008 00:46:10 +0100 Subject: ushare startup issues Message-ID: Hi I've compiled and installed ushare, but have issues trying to start it:- glaw at macmini:~ $ /opt/local/bin/ushare -i en1 -d dlna -t -c ~ Warning: can't parse file "/opt/local/etc/ushare.conf". Interface en1 is down. Recheck uShare's configuration and try again ! uShare (version 1.1a), a lightweight UPnP A/V and DLNA Media Server. Benjamin Zores (C) 2005-2007, for GeeXboX Team. See http://ushare.geexbox.org/ for updates. Initializing UPnP subsystem ... Cannot initialize UPnP subsystem Stopping UPnP Service ... glaw at macmini:~ $ en1 is not down: glaw at macmini:~ $ ifconfig en1 en1: flags=8863 mtu 1500 inet6 fe80::214:51ff:feee:e2d1%en1 prefixlen 64 scopeid 0x5 inet 192.168.1.68 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:14:51:ee:e2:d1 media: autoselect status: active supported media: autoselect putting in a config file with en1 as the interface doesn't help. Curiously, pointing this at en0 -- which is down -- generates a different error Can't find interface en0. any ideas why this won't start? -- Gary Law Email: garylaw at garylaw.net Chat googletalk/messenger: gary.law at gmail.com iChat/jabber/AIM: gary.law at mac.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080622/38144d8f/attachment.htm From philip at trauring.com Sat Jun 21 23:31:04 2008 From: philip at trauring.com (Philip Trauring) Date: Sun, 22 Jun 2008 09:31:04 +0300 Subject: problem installing ruby/readline Message-ID: <064AFB75-F097-477A-9EE6-60CB14560384@trauring.com> I just installed macports and the first thing I wanted to install was the new version of ruby. I ran the install for ruby which installed several dependencies, when it got to readline I got the following message: ---> Activating readline 5.2.012_1 Error: Target org.macports.activate returned: Image error: /opt/local/ lib/libreadline.5.2.dylib already exists and does not belong to a registered port. Unable to activate port readline. Error: The following dependencies failed to build: readline Error: Status 1 encountered during processing. Where it then ended the install. I tried running the install again and this time it seemed to install ruby without dependencies (since they were already installed), but it ended as: port activate ruby at 1.8.7-p22_2+thread_hooks Port command started with PID 28242 ---> Activating ruby 1.8.7-p22_2+thread_hooks Error: port activate failed: Image error: ruby @1.8.7- p22_2+thread_hooks is already active. Curious if was properly installed I ran upgrade as follows: port upgrade ruby +thread_hooks Port command started with PID 28258 ---> Activating readline 5.2.012_1 Error: Activating readline 5.2.012_1 failed: Image error: /opt/local/ lib/libreadline.5.2.dylib already exists and does not belong to a registered port. Unable to activate port readline. Which revealed the original readline problem. I then tried to uninstall readline, but was stopped because ruby depends on it. I figured I could force-uninstall is and then reinstall it. So I force uninstalled it and then got this when trying to re-install: port install readline Port command started with PID 28316 ---> Installing readline 5.2.012_1 ---> Activating readline 5.2.012_1 Error: Target org.macports.activate returned: Image error: /opt/local/ lib/libreadline.5.2.dylib already exists and does not belong to a registered port. Unable to activate port readline. Error: Status 1 encountered during processing. Any ideas here? I saw a similar problem in the archives from last year, but I didn't see a solution. Thanks, Philip p.s. I'm new to using ports, but I guess the ruby that is installed does not replace the ruby already on my system? I tried running ruby -- version but saw the same version as before... From tabithamc at gmail.com Sun Jun 22 04:19:47 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun, 22 Jun 2008 01:19:47 -1000 Subject: Question regarding workaround for gnutar 1.20 on 10.5 (and related question about gcc) Message-ID: <7fccb3000806220419r3c6ebf57hf6d8b71e596bd180@mail.gmail.com> Hello all -- I would like to install the gnutar port version 1.2.0 on an Xserve running Leopard Server (10.5.x) and noticed that when attempting to install, the install failed. There is indeed a trouble ticket for gnutar version 1.19 (ticket # 13462 regarding Leopard problems). Consulting the latest revision of the gnutar 1.20 Portfile (updated "1 month ago"), I saw this interesting note: http://trac.macports.org/browser/trunk/dports/archivers/gnutar/Portfile version 1.20 with workaround for broken gcc-4.0 on 10.5: *beta gcc 4.2 needs > to be installed* > and then the reference to gcc 4.2 at the tail of the Portfile: 48 platform darwin 9 { > 49 # gcc 4.0 fails to compile gnutar on 10.5 (probably will get > fixed with XCode 3.1) > 50 configure.compiler gcc-4.2 > 51 } > Leaving it to one's imagination, its not too difficult to fathom that some people who are Apple Developer Connection members might have early access to XCode 3.1 pre-release which may or may not included gcc 4.2. So, I looked at the MacPorts database and found two port options regarding gcc 4.2: 1.) The port named: *apple-gcc42*, version 5531 whose Portifle is at: http://trac.macports.org/browser/trunk/dports/lang/apple-gcc42/Portfile and I did noticed that the apple-gcc42's Portfile lists a Master site of: http://www.opensource.apple.com/darwinsource/tarballs/other/ Indeed, a the URL above, I found the resource defined in the apple-gcc42 Portfile named: *gcc_42-5531.tar.gz* So I downloaded it and looked at the file named "README.Apple" which has this header, excerpted: APPLE LOCAL file documentation > > This file describes Apple's version of GCC 4.x modified for Darwin / > Mac OS X. Although Apple's stated policy is to contribute all of its > GCC work to the FSF GCC mainstream, at any given moment there will be > changes that are permanently unacceptable for FSF GCC, in need of > rework before acceptance, or that we simply aren't ready to send in. > This version of GCC contains all those changes. > > In keeping with provision 2a of the GPL, each Apple change is marked > with a comment saying "APPLE LOCAL", followed by optional words "begin", > "end", or "file", followed by a short phrase describing the change > generally ("AltiVec" for instance, if the change is related to AltiVec > support). > > BUILDING, THE APPLE WAY > And it goes on from there. 2.) The port named: *gcc42*, version 4.2.4 whose Portifle is at: http://trac.macports.org/browser/trunk/dports/lang/gcc42/Portfile Now taking the two options above: (1) apple-gcc42 or (2) gcc42, does it really matter which of these ports satisfies the gnutar's compiler configuration option for gcc 4.2 on darwin version 9.x (Mac OS X 10.5.x)? Is the apple-gcc42 source separate from what might be released by XCode 3.1? I guess that's really Apple's business as to what they release with XCode 3.1 so it may be a moot point, so long as the resource is made separately available by Apple to the open source communities at large under GPL via opensource.apple.com What is the *best* *practice* suggested by the MacPorts community with respect to compilers? In other words, is it not more or less a chicken-and-egg situation -- before MacPorts (base) can be created, gcc must exist and if I am understanding correctly, the gcc version(s) that ship with XCode (3.0 being the current release and best suggestion). Granted, I could see that if someone was really paranoid they could download the gcc 4.2 source (prior to MacPorts base installation) and make it separate from what comes with Xcode true? It wasn't until today, when I investigated this situation, that I first became aware that there is a port named apple-gcc42. I wonder if this port is indeed the suggested port to use for building gnutar 1.20 on a Leopard 10.5.x system? Thank you, Tabitha -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080622/93fa8af6/attachment.htm From florian.ebeling at gmail.com Sun Jun 22 07:05:38 2008 From: florian.ebeling at gmail.com (Caspar Florian Ebeling) Date: Sun, 22 Jun 2008 16:05:38 +0200 Subject: problem installing ruby/readline In-Reply-To: <064AFB75-F097-477A-9EE6-60CB14560384@trauring.com> References: <064AFB75-F097-477A-9EE6-60CB14560384@trauring.com> Message-ID: <5cbbe4ae0806220705o2128d5fdmf1d2bd2ac30da87f@mail.gmail.com> > I just installed macports and the first thing I wanted to install was > the new version of ruby. I ran the install for ruby which installed > several dependencies, when it got to readline I got the following > message: > > ---> Activating readline 5.2.012_1 > Error: Target org.macports.activate returned: Image error: /opt/local/ > lib/libreadline.5.2.dylib already exists and does not belong to a > registered port. Unable to activate port readline. > Error: The following dependencies failed to build: readline > Error: Status 1 encountered during processing. This is usually the case when a port is defective and does not remove all its artefacts. Did you do previous installs which you tried to remove entirely afterwards, or something like that? Or interrupt an install procedure? I always remove these forcefully with sudo rm, because the file system /opt/local "belongs" to macports, so if it does not know something there this is a bug/inconsistency. Or you manually installed something under this PREFIX, which should be avoided, of course. You can manually check which port owns a file by: port provides PATH_TO_FILE > Where it then ended the install. I tried running the install again and > this time it seemed to install ruby without dependencies (since they > were already installed), but it ended as: > > port activate ruby at 1.8.7-p22_2+thread_hooks > Port command started with PID 28242 > ---> Activating ruby 1.8.7-p22_2+thread_hooks > Error: port activate failed: Image error: ruby @1.8.7- > p22_2+thread_hooks is already active. > > Curious if was properly installed I ran upgrade as follows: > > port upgrade ruby +thread_hooks > Port command started with PID 28258 > ---> Activating readline 5.2.012_1 > Error: Activating readline 5.2.012_1 failed: Image error: /opt/local/ > lib/libreadline.5.2.dylib already exists and does not belong to a > registered port. Unable to activate port readline. > > Which revealed the original readline problem. I then tried to > uninstall readline, but was stopped because ruby depends on it. I > figured I could force-uninstall is and then reinstall it. So I force > uninstalled it and then got this when trying to re-install: > > port install readline > Port command started with PID 28316 > ---> Installing readline 5.2.012_1 > ---> Activating readline 5.2.012_1 > Error: Target org.macports.activate returned: Image error: /opt/local/ > lib/libreadline.5.2.dylib already exists and does not belong to a > registered port. Unable to activate port readline. > Error: Status 1 encountered during processing. > > Any ideas here? I saw a similar problem in the archives from last > year, but I didn't see a solution. > > Thanks, > > Philip > > p.s. I'm new to using ports, but I guess the ruby that is installed > does not replace the ruby already on my system? I tried running ruby -- > version but saw the same version as before... yes, the mp one lives at /opt/local (unless you changed PREFIX for mp), and you can use whichever ruby you like by setting your PATH variable appropriately. Btw, usually it's a good idea to include infrmation about OS and hardware when you report a problem to a mailing list. Florian -- Florian Ebeling florian.ebeling at gmail.com From tabithamc at gmail.com Sun Jun 22 08:55:55 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun, 22 Jun 2008 05:55:55 -1000 Subject: Question regarding workaround for gnutar 1.20 on 10.5 (and related question about gcc) In-Reply-To: <7fccb3000806220419r3c6ebf57hf6d8b71e596bd180@mail.gmail.com> References: <7fccb3000806220419r3c6ebf57hf6d8b71e596bd180@mail.gmail.com> Message-ID: <7fccb3000806220855r4ad33682n3051ddb8e756c5ac@mail.gmail.com> Hello all (again) -- This is rather interesting. I separately installed the two gcc 4.2 ports mentioned in my email that started this thread (apple-gcc42 and gcc42). After each install, I attempted then to build and install (after first cleaning) gnutar 1.20. In both cases gnutar 1.20 failed to install. So I guess this means that the beta of gcc 4.2 is that which is likely associated with pre-release of XCode 3.1? Any suggestions? Has anyone successfully built gnutar 1.20 on Leopard 10.5.x? Thanks, T.M. On Sun, Jun 22, 2008 at 1:19 AM, Tabitha McNerney wrote: > Hello all -- > > I would like to install the gnutar port version 1.2.0 on an Xserve running > Leopard Server (10.5.x) and noticed that when attempting to install, the > install failed. There is indeed a trouble ticket for gnutar version 1.19 > (ticket # 13462 regarding Leopard problems). > > Consulting the latest revision of the gnutar 1.20 Portfile (updated "1 > month ago"), I saw this interesting note: > > http://trac.macports.org/browser/trunk/dports/archivers/gnutar/Portfile > > version 1.20 with workaround for broken gcc-4.0 on 10.5: *beta gcc 4.2 >> needs to be installed* >> > > and then the reference to gcc 4.2 at the tail of the Portfile: > > 48 platform darwin 9 { >> 49 # gcc 4.0 fails to compile gnutar on 10.5 (probably will >> get fixed with XCode 3.1) >> 50 configure.compiler gcc-4.2 >> 51 } >> > > Leaving it to one's imagination, its not too difficult to fathom that some > people who are Apple Developer Connection members might have early access to > XCode 3.1 pre-release which may or may not included gcc 4.2. So, I looked at > the MacPorts database and found two port options regarding gcc 4.2: > > 1.) The port named: *apple-gcc42*, version 5531 whose Portifle is at: > > http://trac.macports.org/browser/trunk/dports/lang/apple-gcc42/Portfile > > and I did noticed that the apple-gcc42's Portfile lists a Master site of: > > http://www.opensource.apple.com/darwinsource/tarballs/other/ > > Indeed, a the URL above, I found the resource defined in the apple-gcc42 > Portfile named: > > *gcc_42-5531.tar.gz* > > So I downloaded it and looked at the file named "README.Apple" which has > this header, excerpted: > > APPLE LOCAL file documentation >> >> This file describes Apple's version of GCC 4.x modified for Darwin / >> Mac OS X. Although Apple's stated policy is to contribute all of its >> GCC work to the FSF GCC mainstream, at any given moment there will be >> changes that are permanently unacceptable for FSF GCC, in need of >> rework before acceptance, or that we simply aren't ready to send in. >> This version of GCC contains all those changes. >> >> In keeping with provision 2a of the GPL, each Apple change is marked >> with a comment saying "APPLE LOCAL", followed by optional words "begin", >> "end", or "file", followed by a short phrase describing the change >> generally ("AltiVec" for instance, if the change is related to AltiVec >> support). >> >> BUILDING, THE APPLE WAY >> > > And it goes on from there. > > 2.) The port named: *gcc42*, version 4.2.4 whose Portifle is at: > > http://trac.macports.org/browser/trunk/dports/lang/gcc42/Portfile > > Now taking the two options above: (1) apple-gcc42 or (2) gcc42, does it > really matter which of these ports satisfies the gnutar's compiler > configuration option for gcc 4.2 on darwin version 9.x (Mac OS X 10.5.x)? Is > the apple-gcc42 source separate from what might be released by XCode 3.1? I > guess that's really Apple's business as to what they release with XCode 3.1 > so it may be a moot point, so long as the resource is made separately > available by Apple to the open source communities at large under GPL via > opensource.apple.com > > What is the *best* *practice* suggested by the MacPorts community with > respect to compilers? In other words, is it not more or less a > chicken-and-egg situation -- before MacPorts (base) can be created, gcc must > exist and if I am understanding correctly, the gcc version(s) that ship with > XCode (3.0 being the current release and best suggestion). Granted, I could > see that if someone was really paranoid they could download the gcc 4.2 > source (prior to MacPorts base installation) and make it separate from what > comes with Xcode true? It wasn't until today, when I investigated this > situation, that I first became aware that there is a port named apple-gcc42. > I wonder if this port is indeed the suggested port to use for building > gnutar 1.20 on a Leopard 10.5.x system? > > Thank you, > > Tabitha > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080622/0bb33e55/attachment.htm From raimue at macports.org Sun Jun 22 15:13:05 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Mon, 23 Jun 2008 00:13:05 +0200 Subject: Question regarding workaround for gnutar 1.20 on 10.5 (and related question about gcc) In-Reply-To: <7fccb3000806220855r4ad33682n3051ddb8e756c5ac@mail.gmail.com> References: <7fccb3000806220419r3c6ebf57hf6d8b71e596bd180@mail.gmail.com> <7fccb3000806220855r4ad33682n3051ddb8e756c5ac@mail.gmail.com> Message-ID: <485ECE71.4060906@macports.org> Tabitha McNerney wrote: > This is rather interesting. I separately installed the two gcc 4.2 ports > mentioned in my email that started this thread (apple-gcc42 and gcc42). > After each install, I attempted then to build and install (after first > cleaning) gnutar 1.20. In both cases gnutar 1.20 failed to install. > > So I guess this means that the beta of gcc 4.2 is that which is likely > associated with pre-release of XCode 3.1? Any suggestions? Has anyone > successfully built gnutar 1.20 on Leopard 10.5.x? Yes, it really wants /usr/bin/gcc-4.2 from the Xcode beta, which is bad in my opinion as it prevents to install this port on normal systems. I already wrote a mail about this to Markus and macports-dev [1]. It works fine for me with gcc42 or gcc43 from MacPorts. You can overwrite the compiler manually as a workaround: $ sudo port install gnutar configure.compiler=macports-gcc-4.2 The only thing that won't work are universal builds, as noted by Markus in the thread from above. Rainer [1] http://lists.macosforge.org/pipermail/macports-dev/2008-June/005403.html From tabithamc at gmail.com Sun Jun 22 18:44:34 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sun, 22 Jun 2008 15:44:34 -1000 Subject: Question regarding workaround for gnutar 1.20 on 10.5 (and related question about gcc) In-Reply-To: <485ECE71.4060906@macports.org> References: <7fccb3000806220419r3c6ebf57hf6d8b71e596bd180@mail.gmail.com> <7fccb3000806220855r4ad33682n3051ddb8e756c5ac@mail.gmail.com> <485ECE71.4060906@macports.org> Message-ID: <7fccb3000806221844k176c18e0h7b1edcaf001f9380@mail.gmail.com> Rainer, Thank you for your detailed response. I will revert to gcc42 per your suggestion and I should have just changed the compiler information in the gnutar Portfile (I wasn't previously sure how to do that so thank you for your example)! Thanks, T.M. On Sun, Jun 22, 2008 at 12:13 PM, Rainer M?ller wrote: > Tabitha McNerney wrote: > > This is rather interesting. I separately installed the two gcc 4.2 ports > > mentioned in my email that started this thread (apple-gcc42 and gcc42). > > After each install, I attempted then to build and install (after first > > cleaning) gnutar 1.20. In both cases gnutar 1.20 failed to install. > > > > So I guess this means that the beta of gcc 4.2 is that which is likely > > associated with pre-release of XCode 3.1? Any suggestions? Has anyone > > successfully built gnutar 1.20 on Leopard 10.5.x? > > Yes, it really wants /usr/bin/gcc-4.2 from the Xcode beta, which is bad > in my opinion as it prevents to install this port on normal systems. I > already wrote a mail about this to Markus and macports-dev [1]. > > It works fine for me with gcc42 or gcc43 from MacPorts. You can > overwrite the compiler manually as a workaround: > > $ sudo port install gnutar configure.compiler=macports-gcc-4.2 > > The only thing that won't work are universal builds, as noted by Markus > in the thread from above. > > Rainer > > [1] > http://lists.macosforge.org/pipermail/macports-dev/2008-June/005403.html > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080622/5cc1ba85/attachment.htm From ryandesign at macports.org Mon Jun 23 00:16:06 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 23 Jun 2008 02:16:06 -0500 Subject: Activating git-core 1.5.3.1_0 failed: In-Reply-To: References: <43BF7A0D-5A15-4BCD-937C-BC9BC8A0CA1A@macports.org> Message-ID: <2BE8FBE9-FFEA-4BAD-8C3E-9EAF654FEB4C@macports.org> On Jun 22, 2008, at 14:09, Yvon Thoraval wrote: > 2008/6/13 Ryan Schmidt: > >> Try uninstalling git-core @1.5.3.1_0+doc first. >> >> sudo port -f uninstall git-core @1.5.3.1_0+doc >> >> Better yet, uninstall all versions of git-core you have installed. >> Then "sudo port install git-core" and it should rebuild. > > i did that, however, i get sha1 mismatch : > > $ sudo port install git-core > Password: > ---> Fetching git-core > ---> Attempting to fetch git-1.5.5.3.tar.bz2 from http:// > www.kernel.org/pub/software/scm/git/ > ---> Attempting to fetch git-manpages-1.5.5.3.tar.bz2 from http:// > www.kernel.org/pub/software/scm/git/ > ---> Attempting to fetch git-htmldocs-1.5.5.3.tar.bz2 from http:// > www.kernel.org/pub/software/scm/git/ > ---> Verifying checksum(s) for git-core > Error: Checksum (sha1) mismatch for git-1.5.5.3.tar.bz2 > Error: Checksum (sha1) mismatch for git-manpages-1.5.5.3.tar.bz2 > Error: Target org.macports.checksum returned: Unable to verify file > checksums > Error: Status 1 encountered during processing. > > > then i did : > $ sudo port clean git-core > > and redo : > $ sudo port install git-core > ---> Fetching git-core > ---> Verifying checksum(s) for git-core > Error: Checksum (sha1) mismatch for git-1.5.5.3.tar.bz2 > Error: Checksum (sha1) mismatch for git-manpages-1.5.5.3.tar.bz2 > Error: Target org.macports.checksum returned: Unable to verify file > checksums > Error: Status 1 encountered during processing. > > > i think port didn't re-fetch new tared files, does i need to remove > those file manually (something like rm -f /path/to... ?) > > or is there a way to tell port re-fetch new ones ? MacPorts knows to download new files when necessary. git-core checksums just fine for me. It looks like you got a corrupted download. Use "sudo port clean --all git-core" to clean out the bad downloads. Then try installing again and they will be fetched again. This is mentioned in the FAQ on reasons why a checksum error might occur: http://trac.macports.org/wiki/ FAQ#IgetError:checksummd5sha1rmd160mismatchforport.WhatcanIdoaboutit Please use Reply All so your message gets to the mailing list too, not just to me. From graef at ebi.ac.uk Mon Jun 23 03:49:11 2008 From: graef at ebi.ac.uk (=?ISO-8859-1?Q?Stefan_Gr=E4f?=) Date: Mon, 23 Jun 2008 11:49:11 +0100 Subject: apache2 install: fetching apr fails Message-ID: <485F7FA7.4060000@ebi.ac.uk> Hi Guys, I'm not able to install apache2 cause the requested apr-1.3.0.tar.bz2 are no longer available from the servers. The current version seems to be 1.3.2. Any workaround or fix would be very much appreciated. Cheers, Stefan $ port install apache2 ---> Fetching apr ---> Attempting to fetch apr-1.3.0.tar.bz2 from http://www.apache.org/dist/apr ---> Attempting to fetch apr-1.3.0.tar.bz2 from http://apache.planetmirror.com.au/dist/apr ---> Attempting to fetch apr-1.3.0.tar.bz2 from ftp://ftp.planetmirror.com/pub/apache/dist/apr ---> Attempting to fetch apr-1.3.0.tar.bz2 from ftp://ftp.is.co.za/Apache/dist/apr ---> Attempting to fetch apr-1.3.0.tar.bz2 from ftp://ftp.infoscience.co.jp/pub/net/apache/dist/apr ---> Attempting to fetch apr-1.3.0.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/apr ---> Attempting to fetch apr-1.3.0.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch apr-1.3.0.tar.bz2 from http://svn.macports.org/repository/macports/downloads/apr Error: Target org.macports.fetch returned: fetch failed Error: The following dependencies failed to build: apr apr-util sqlite3 gmake pcre Error: Status 1 encountered during processing. From ryandesign at macports.org Mon Jun 23 05:04:48 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 23 Jun 2008 07:04:48 -0500 Subject: apache2 install: fetching apr fails In-Reply-To: <485F7FA7.4060000@ebi.ac.uk> References: <485F7FA7.4060000@ebi.ac.uk> Message-ID: On Jun 23, 2008, at 05:49, Stefan Gr?f wrote: > I'm not able to install apache2 cause the requested apr-1.3.0.tar.bz2 > are no longer available from the servers. The current version seems to > be 1.3.2. The port has already been updated to 1.3.2. Please "sudo port selfupdate" and try again. From mail at thorstenzoerner.de Mon Jun 23 06:24:55 2008 From: mail at thorstenzoerner.de (=?ISO-8859-1?Q?Thorsten_Z=F6rner?=) Date: Mon, 23 Jun 2008 15:24:55 +0200 Subject: Trying to get a new Scribus to work Message-ID: <0ACEDE0F-AA76-4496-BF82-41647106D2CD@thorstenzoerner.de> Hi there, this is Thorsten, stand-in maintainer of the scribus-macport. Scribus has come out with a new version 1.3.3.12 which I've tried to compile locally. It compiles all right, but then one of the next steps fails. Have a look at this and please tell me, what is going wrong here: Macintosh-3:Temp thorsten$ sudo port install scribus ---> Fetching scribus ---> Attempting to fetch scribus-1.3.3.12.tar.bz2 from http://downloads.sourceforge.net/scribus ---> Verifying checksum(s) for scribus ---> Extracting scribus ---> Configuring scribus ---> Building scribus with target all ---> Staging scribus into destroot Error: Target org.macports.destroot returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/scribus-1.3.3.12" && make install DESTDIR=/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot " returned error 2 Command output: /usr/bin/install -m 644 ./scribuspdfoptions.dtd /opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/dtd/scribuspdfoptions.dtd Making install in loremipsum make[3]: Nothing to be done for `install-exec-am'. /bin/sh ../../admin/mkinstalldirs /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/ mkdir -p -- /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/ /usr/bin/install -m 644 ./loremipsum.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/loremipsum.xml /usr/bin/install -m 644 ./arabic.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/arabic.xml /usr/bin/install -m 644 ./czech.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/czech.xml /usr/bin/install -m 644 ./dutch.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/dutch.xml /usr/bin/install -m 644 ./fr.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/fr.xml /usr/bin/install -m 644 ./finnish.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/finnish.xml /usr/bin/install -m 644 ./german.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/german.xml /usr/bin/install -m 644 ./english.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/english.xml /usr/bin/install -m 644 ./eo.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/eo.xml /usr/bin/install -m 644 ./greek.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/greek.xml /usr/bin/install -m 644 ./hebrew.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/hebrew.xml /usr/bin/install -m 644 ./hu.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/hu.xml /usr/bin/install -m 644 ./italian.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/italian.xml /usr/bin/install -m 644 ./russian.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/russian.xml /usr/bin/install -m 644 ./slovenian.xml /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/ share/scribus/loremipsum/slovenian.xml Making install in text make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. Making install in . test -z "/opt/local/bin" || ../admin/install-sh -c -d "/opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_print_scribus/work/destroot/opt/local/bin" /bin/sh: ../admin/install-sh: Permission denied make[3]: *** [install-binPROGRAMS] Error 126 make[2]: *** [install-am] Error 2 make[1]: *** [install-recursive] Error 1 make: *** [install-recursive] Error 1 Error: Status 1 encountered during processing. Okay, so what goes wrong here? 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/20080623/29e71bd3/attachment.p7s From graef at ebi.ac.uk Mon Jun 23 07:14:48 2008 From: graef at ebi.ac.uk (=?ISO-8859-1?Q?Stefan_Gr=E4f?=) Date: Mon, 23 Jun 2008 15:14:48 +0100 Subject: apache2 install: fetching apr fails In-Reply-To: References: <485F7FA7.4060000@ebi.ac.uk> Message-ID: <485FAFD8.1050904@ebi.ac.uk> Wonderful, that's working now. Thanks, Stefan Ryan Schmidt wrote: > On Jun 23, 2008, at 05:49, Stefan Gr?f wrote: > >> I'm not able to install apache2 cause the requested apr-1.3.0.tar.bz2 >> are no longer available from the servers. The current version seems to >> be 1.3.2. > > > The port has already been updated to 1.3.2. Please "sudo port > selfupdate" and try again. From yvon.thoraval at gmail.com Mon Jun 23 10:49:14 2008 From: yvon.thoraval at gmail.com (Yvon Thoraval) Date: Mon, 23 Jun 2008 19:49:14 +0200 Subject: Activating git-core 1.5.3.1_0 failed: In-Reply-To: <2BE8FBE9-FFEA-4BAD-8C3E-9EAF654FEB4C@macports.org> References: <43BF7A0D-5A15-4BCD-937C-BC9BC8A0CA1A@macports.org> <2BE8FBE9-FFEA-4BAD-8C3E-9EAF654FEB4C@macports.org> Message-ID: 2008/6/23 Ryan Schmidt : > > MacPorts knows to download new files when necessary. > > git-core checksums just fine for me. It looks like you got a corrupted > download. yes i suspected a bad net connection at that time. > Use "sudo port clean --all git-core" to clean out the bad downloads. Then > try installing again and they will be fetched again. This is mentioned in > the FAQ on reasons why a checksum error might occur: > > http://trac.macports.org/wiki/ > FAQ#IgetError:checksummd5sha1rmd160mismatchforport.WhatcanIdoaboutit > > Please use Reply All so your message gets to the mailing list too, not just > to me. > i should remeber that point too. sorry for the noise... -- yvon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080623/4ad2b8e3/attachment.htm From lrivers at gmail.com Mon Jun 23 11:31:52 2008 From: lrivers at gmail.com (Lorin Rivers) Date: Mon, 23 Jun 2008 13:31:52 -0500 Subject: reverting to a previous version of a port? Message-ID: <949829840806231131r503e1634xa275e093040fee7a@mail.gmail.com> I foolishly upgraded to subversion 1.5 without checking to see if my other tools play nicely. Well, they don't. I need to revert to the previous version of Subversion, but I don't see how to. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080623/0fd3d1d5/attachment.htm From dluke at geeklair.net Mon Jun 23 11:45:48 2008 From: dluke at geeklair.net (Daniel J. Luke) Date: Mon, 23 Jun 2008 14:45:48 -0400 Subject: reverting to a previous version of a port? In-Reply-To: <949829840806231131r503e1634xa275e093040fee7a@mail.gmail.com> References: <949829840806231131r503e1634xa275e093040fee7a@mail.gmail.com> Message-ID: <8AC62683-4397-4A77-89E8-7DA59C379BA4@geeklair.net> On Jun 23, 2008, at 2:31 PM, Lorin Rivers wrote: > I foolishly upgraded to subversion 1.5 without checking to see if my > other tools play nicely. Well, they don't. If there's something I can do with the subversion port to help here, please let me know (and/or point me to any documentation of the issues you're seeing with potential workarounds). > I need to revert to the previous version of Subversion, but I don't > see how to. If you didn't uninstall the old version, you can just deactivate 1.5.0 and activate the older version. Otherwise: http://trac.macports.org/wiki/howto/InstallingOlderPort -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080623/dcafa54e/attachment.sig From danstowell at gmail.com Mon Jun 23 11:52:39 2008 From: danstowell at gmail.com (Dan Stowell) Date: Mon, 23 Jun 2008 19:52:39 +0100 Subject: qt4-mac provides version 3? Message-ID: <286e6b7c0806231152s51ae449dk16452e2178363b25@mail.gmail.com> Hi - I installed the "qt4-mac" port. Looks fine so far: % port installed | grep qt qt4-mac @4.4.0_3+dbus+docs (active) % which qmake /opt/local/bin/qmake % port provides `which qmake` /opt/local/bin/qmake is provided by: qt4-mac So how come I get this: % qmake --version Qmake version: 1.07a (Qt 3.3.7) ? I tried to compile something which requires qt 4, and got errors, hence I discovered this. I'm on PPC, Mac 10.4.11. Thanks in advance for any suggestions - Dan From blb at macports.org Mon Jun 23 14:33:14 2008 From: blb at macports.org (Bryan Blackburn) Date: Mon, 23 Jun 2008 15:33:14 -0600 Subject: Trying to get a new Scribus to work In-Reply-To: <0ACEDE0F-AA76-4496-BF82-41647106D2CD@thorstenzoerner.de> References: <0ACEDE0F-AA76-4496-BF82-41647106D2CD@thorstenzoerner.de> Message-ID: <279BFA7B-AC9B-42EA-9DFC-0465CEC931DF@macports.org> On Jun 23, 2008, at 7:24 AM, Thorsten Z?rner wrote: > Hi there, > > this is Thorsten, stand-in maintainer of the scribus-macport. > Scribus has come out with a new version 1.3.3.12 which I've tried to > compile locally. > It compiles all right, but then one of the next steps fails. > Have a look at this and please tell me, what is going wrong here: > > Macintosh-3:Temp thorsten$ sudo port install scribus > ---> Fetching scribus ... > /bin/sh: ../admin/install-sh: Permission denied Looks like install-sh isn't executable, so I'd suggest adding post-extract { file attributes ${worksrcpath}/admin/install-sh -permissions 0755 } (note, only tested in Mail.app). Bryan > > make[3]: *** [install-binPROGRAMS] Error 126 > make[2]: *** [install-am] Error 2 > make[1]: *** [install-recursive] Error 1 > make: *** [install-recursive] Error 1 > > Error: Status 1 encountered during processing. > > Okay, so what goes wrong here? > > Cheers, > Thorsten._______________________________________________ From sfiera at macports.org Mon Jun 23 19:54:08 2008 From: sfiera at macports.org (Chris Pickel) Date: Mon, 23 Jun 2008 22:54:08 -0400 Subject: ushare startup issues In-Reply-To: References: Message-ID: <19B86DDB-8386-456F-8B4F-A31792B9E269@macports.org> I'm the maintainer of ushare, but it's been a long time since I've looked at the port (since it didn't quite work with my 360), and I also don't currently have access to the computer I installed in on. What I can tell you right now is that I have in the past successfully run ushare, listening on ethernet, and that I might be able to post a working ushare.conf tomorrow. If you're willing to try other things, there's also a port for mediatomb, another UPnP server, in the tree (I don't know if it supports the device you want). On 21 Jun, 2008, at 19:46, Gary Law wrote: > I've compiled and installed ushare, but have issues trying to start > it:- > > glaw at macmini:~ $ /opt/local/bin/ushare -i en1 -d dlna -t -c ~ > Warning: can't parse file "/opt/local/etc/ushare.conf". > Interface en1 is down. > Recheck uShare's configuration and try again ! > uShare (version 1.1a), a lightweight UPnP A/V and DLNA Media Server. > Benjamin Zores (C) 2005-2007, for GeeXboX Team. > See http://ushare.geexbox.org/ for updates. > Initializing UPnP subsystem ... > Cannot initialize UPnP subsystem > Stopping UPnP Service ... > glaw at macmini:~ $ > > en1 is not down: > > glaw at macmini:~ $ ifconfig en1 > en1: flags=8863 mtu 1500 > inet6 fe80::214:51ff:feee:e2d1%en1 prefixlen 64 scopeid 0x5 > inet 192.168.1.68 netmask 0xffffff00 broadcast 192.168.1.255 > ether 00:14:51:ee:e2:d1 > media: autoselect status: active > supported media: autoselect > > > putting in a config file with en1 as the interface doesn't help. > Curiously, pointing this at en0 -- which is down -- generates a > different error > Can't find interface en0. > > any ideas why this won't start? -------------- 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/20080623/90d85bf8/attachment.sig From william at gallaf.net Tue Jun 24 03:19:17 2008 From: william at gallaf.net (William Gallafent) Date: Tue, 24 Jun 2008 11:19:17 +0100 Subject: GraphicsMagick In-Reply-To: <485538D4-2BF7-4A7E-BFBE-FC3404EDD9A4@macports.org> References: <6D883A91-BD30-48B0-8926-F1293DEDDD97@gallaf.net> <2123AC93-BABD-45D0-A5B8-9006E5CC3B73@macports.org> <485538D4-2BF7-4A7E-BFBE-FC3404EDD9A4@macports.org> Message-ID: On 20 Jun 2008, at 07:41, Ryan Schmidt wrote: > Ok, GraphicsMagick 1.2.3 is now in the repository. Wait 12 hours, > then "sudo port selfupdate" to get the new port definition, then > "sudo port install GraphicsMagick" (or if you already had an earlier > version installed, "sudo port upgrade GraphicsMagick"). Great, many thanks. Builds and installs fine here. From ryandesign at macports.org Tue Jun 24 17:33:18 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 24 Jun 2008 19:33:18 -0500 Subject: qt4-mac provides version 3? In-Reply-To: <286e6b7c0806231152s51ae449dk16452e2178363b25@mail.gmail.com> References: <286e6b7c0806231152s51ae449dk16452e2178363b25@mail.gmail.com> Message-ID: <7757C9EA-9C4E-4609-9748-C617359ED81B@macports.org> On Jun 23, 2008, at 13:52, Dan Stowell wrote: > I installed the "qt4-mac" port. Looks fine so far: > > % port installed | grep qt > qt4-mac @4.4.0_3+dbus+docs (active) > > % which qmake > /opt/local/bin/qmake > > % port provides `which qmake` > /opt/local/bin/qmake is provided by: qt4-mac > > > So how come I get this: > > % qmake --version > Qmake version: 1.07a (Qt 3.3.7) > > ? I tried to compile something which requires qt 4, and got errors, > hence I discovered this. I'm on PPC, Mac 10.4.11. Goodness, qt4-mac is huge. It takes 1.6GB of space after installation, plus an additional 5GB of space during installation. Anyway I don't have a problem with this on Mac OS X 10.4.11 Intel. $ port installed qt4-mac The following ports are currently installed: qt4-mac @4.4.0_3+dbus+docs (active) $ which qmake /mp/bin/qmake $ qmake --version QMake version 2.01a Using Qt version 4.4.0 in /mp/Library/Frameworks $ Maybe you have another qt manually installed? Maybe you have a shell alias set up for "qmake" pointing somewhere else? ("which" doesn't take shell aliases into account....) From queshaw at pacbell.net Tue Jun 24 18:15:31 2008 From: queshaw at pacbell.net (Kendall Shaw) Date: Tue, 24 Jun 2008 18:15:31 -0700 Subject: Is "MacPort" a valid term? In-Reply-To: <87BCE6D9-288A-4179-8812-2383DDF8B828@apple.com> References: <87BCE6D9-288A-4179-8812-2383DDF8B828@apple.com> Message-ID: <1214356531.7005.48.camel@pokey.kendallshaw.com> On Thu, 2008-06-12 at 10:43 -0700, Jordan K. Hubbard wrote: > On Jun 11, 2008, at 11:51 PM, markd at macports.org wrote: > > > So are you saying that you think "MacPort" is a valid term? I was > > thinking it wasn't an accepted and/or used term. If folks think it > > is, I > > can stop flipping between using "MacPorts port" (mostly in intro > > parts) > > and "port" in the docs. It's not a really big deal though, except > > just to > > settle if the term "MacPort" is considered invalid usage or not. > > I'm not saying it's invalid, how about that? :-) > > Ultimately, I think it's like a nickname. You generally don't get to > pick your own nickname and, whether you like it or not, once you have > one it sticks to you like glue for the rest of your life. > > We're still just in that awkward phase where nobody has found a > nickname that really applies to the extent where everyone goes "Yes! > That's it!" and then continues to use that name regardless of what the > Powers That Be attempt to call it. How about: Mmmm... port? From zavpublic at mac.com Tue Jun 24 19:21:17 2008 From: zavpublic at mac.com (Zav Public) Date: Tue, 24 Jun 2008 21:21:17 -0500 Subject: Is "MacPort" a valid term? In-Reply-To: <1214356531.7005.48.camel@pokey.kendallshaw.com> References: <87BCE6D9-288A-4179-8812-2383DDF8B828@apple.com> <1214356531.7005.48.camel@pokey.kendallshaw.com> Message-ID: <52880460-862D-4ADC-9319-7385CD92F269@mac.com> What are these ports? What do they constitute? Is there a term that can define them? If so, then I propose Mac-whatever-ports where whatever is the term that most appropriately describes what they would be and could be understandable by the layperson. Something palatable, steering away from the GNU practice of "the abbreviation is part of the name" which leads to strangeness in project names. Really, it does. If these are open source ports and they were last time I checked, then we may have: Open source Mac Ports The Open Source MacPorts Project. Open Source Ports for the Mac. Mac Open Source Ports. Open Mac Ports. MacPorts OpenSource. And so on. Cheers - Zav On Jun 24, 2008, at 8:15 PM, Kendall Shaw wrote: > > On Thu, 2008-06-12 at 10:43 -0700, Jordan K. Hubbard wrote: >> On Jun 11, 2008, at 11:51 PM, markd at macports.org wrote: >> >>> So are you saying that you think "MacPort" is a valid term? I was >>> thinking it wasn't an accepted and/or used term. If folks think it >>> is, I >>> can stop flipping between using "MacPorts port" (mostly in intro >>> parts) >>> and "port" in the docs. It's not a really big deal though, except >>> just to >>> settle if the term "MacPort" is considered invalid usage or not. >> >> I'm not saying it's invalid, how about that? :-) >> >> Ultimately, I think it's like a nickname. You generally don't get to >> pick your own nickname and, whether you like it or not, once you have >> one it sticks to you like glue for the rest of your life. >> >> We're still just in that awkward phase where nobody has found a >> nickname that really applies to the extent where everyone goes "Yes! >> That's it!" and then continues to use that name regardless of what >> the >> Powers That Be attempt to call it. > > How about: Mmmm... port? > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From tom at tacocat.net Tue Jun 24 19:38:27 2008 From: tom at tacocat.net (Tom Allison) Date: Tue, 24 Jun 2008 22:38:27 -0400 Subject: apache, postgresql, perl Message-ID: <4861AFA3.5070904@tacocat.net> I ran into a problem with trying to set up a cgi page on my macbook. The code uses CGI and DBD::Pg. From the command line, it works great. From Apache it works badly... Can't load '/Library/Perl/5.8.6/darwin-thread-multi-2level/auto/DBD/Pg/Pg.bundle' for module DBD::Pg: dlopen(/Library/Perl/5.8.6/darwin-thread-multi-2level/auto/DBD/Pg/Pg.bundle, 1): Library not loaded: /usr/local/pgsql/lib/libpq.5.dylib I have no /usr/local/pgsql/... But I have a /opt/local/lib/postgresql83/libpq.5.dylib which was put there by the mac port installation. How do I get these mac port installations playing nice together? From ryandesign at macports.org Tue Jun 24 22:07:56 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 25 Jun 2008 00:07:56 -0500 Subject: qt4-mac provides version 3? In-Reply-To: <7757C9EA-9C4E-4609-9748-C617359ED81B@macports.org> References: <286e6b7c0806231152s51ae449dk16452e2178363b25@mail.gmail.com> <7757C9EA-9C4E-4609-9748-C617359ED81B@macports.org> Message-ID: <6C707229-1820-4AC3-B37E-A3DAB76592D1@macports.org> On Jun 24, 2008, at 19:33, Ryan Schmidt wrote: > On Jun 23, 2008, at 13:52, Dan Stowell wrote: > >> I installed the "qt4-mac" port. Looks fine so far: >> >> % port installed | grep qt >> qt4-mac @4.4.0_3+dbus+docs (active) >> >> % which qmake >> /opt/local/bin/qmake >> >> % port provides `which qmake` >> /opt/local/bin/qmake is provided by: qt4-mac >> >> >> So how come I get this: >> >> % qmake --version >> Qmake version: 1.07a (Qt 3.3.7) >> >> ? I tried to compile something which requires qt 4, and got errors, >> hence I discovered this. I'm on PPC, Mac 10.4.11. > > Goodness, qt4-mac is huge. It takes 1.6GB of space after > installation, plus an additional 5GB of space during installation. > > Anyway I don't have a problem with this on Mac OS X 10.4.11 Intel. > > > $ port installed qt4-mac > The following ports are currently installed: > qt4-mac @4.4.0_3+dbus+docs (active) > $ which qmake > /mp/bin/qmake > $ qmake --version > QMake version 2.01a > Using Qt version 4.4.0 in /mp/Library/Frameworks > $ > > > Maybe you have another qt manually installed? Maybe you have a shell > alias set up for "qmake" pointing somewhere else? ("which" doesn't > take shell aliases into account....) To offer another suggestion: You should try calling qmake by its absolute path, e.g.: /opt/local/bin/qmake --version Does that now show Qmake 2.01a / Qt 4.4.0? If so, then my shell alias hunch may be correct. You can type: alias to see all your defined aliases. From ryandesign at macports.org Tue Jun 24 22:21:22 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 25 Jun 2008 00:21:22 -0500 Subject: Is "MacPort" a valid term? In-Reply-To: <52880460-862D-4ADC-9319-7385CD92F269@mac.com> References: <87BCE6D9-288A-4179-8812-2383DDF8B828@apple.com> <1214356531.7005.48.camel@pokey.kendallshaw.com> <52880460-862D-4ADC-9319-7385CD92F269@mac.com> Message-ID: On Jun 24, 2008, at 21:21, Zav Public wrote: > What are these ports? What do they constitute? Is there a term that > can define them? They are software packages. I can't think of a more specific term that would still apply to all ports. MacPorts is a package manager, or a package management system: http://en.wikipedia.org/wiki/Package_management_system So we could say we install packages. Instead, for now, we say we install ports, because the term "port" is used by the FreeBSD ports project which inspired MacPorts. This causes confusion with other uses of the word "port" (a software network connection; a physical connector on an electronic device; the process of rewriting software from one platform so it runs on another). However, the term "package" would also cause confusion on Mac OS X, because Apple uses the term "package" for software installed through its Installer program, and MacPorts does not make use of this. > If so, then I propose Mac-whatever-ports where whatever is the term > that most appropriately describes what they would be and could be > understandable by the layperson. > > Something palatable, steering away from the GNU practice of "the > abbreviation is part of the name" which leads to strangeness in > project names. Really, it does. Agreed, recursive acronyms are of the "cute but stupid" variety which certainly confuse the average computer user of today. > If these are open source ports and they were last time I checked, > then we may have: > > Open source Mac Ports > > The Open Source MacPorts Project. > > Open Source Ports for the Mac. > > Mac Open Source Ports. > > Open Mac Ports. > > MacPorts OpenSource. > > And so on. Most of the ports we have are open source, true, but some are not. For example, the oracle-instantclient port installs freely available libraries for connecting with Oracle databases, but Oracle Corporation does not make the source of their software public. The isightcapture port installs a tool with which you can snap a picture from your iSight camera, but its source is not available either. These ports install from binaries provided by the developer. We prefer to build from source, but when it's not available, binaries can be used. From ryandesign at macports.org Tue Jun 24 22:24:35 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 25 Jun 2008 00:24:35 -0500 Subject: apache, postgresql, perl In-Reply-To: <4861AFA3.5070904@tacocat.net> References: <4861AFA3.5070904@tacocat.net> Message-ID: <0470D764-B1B7-4FB3-B582-ABF6691D3D1D@macports.org> On Jun 24, 2008, at 21:38, Tom Allison wrote: > I ran into a problem with trying to set up a cgi page on my macbook. > > The code uses CGI and DBD::Pg. > From the command line, it works great. > > From Apache it works badly... > > Can't load > '/Library/Perl/5.8.6/darwin-thread-multi-2level/auto/DBD/Pg/Pg.bundle' > for module DBD::Pg: > dlopen(/Library/Perl/5.8.6/darwin-thread-multi-2level/auto/DBD/Pg/ > Pg.bundle, > 1): Library not loaded: /usr/local/pgsql/lib/libpq.5.dylib > > > I have no /usr/local/pgsql/... > But I have a > /opt/local/lib/postgresql83/libpq.5.dylib > > which was put there by the mac port installation. > > How do I get these mac port installations playing nice together? As you said, MacPorts doesn't put things in /usr/local. It doesn't put things in /Library/Perl either. The fact that from Apache it's trying to load something in /Library/Perl suggests that from Apache you're trying to use Apple's Perl instead of the Perl from MacPorts. You didn't say which Apache. Is this apache2 from MacPorts? How do you test this from the command line? What command do you run? If there is a perl source file involved, can you provide it? How do you test this from Apache? From tom at tacocat.net Tue Jun 24 23:39:57 2008 From: tom at tacocat.net (Tom Allison) Date: Wed, 25 Jun 2008 02:39:57 -0400 Subject: postgresql configuration Message-ID: <4861E83D.9010709@tacocat.net> where are the configuration files for postgresql83? From ryandesign at macports.org Tue Jun 24 23:41:21 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 25 Jun 2008 01:41:21 -0500 Subject: apache, postgresql, perl In-Reply-To: <4861E66A.1060804@tacocat.net> References: <4861AFA3.5070904@tacocat.net> <0470D764-B1B7-4FB3-B582-ABF6691D3D1D@macports.org> <4861E66A.1060804@tacocat.net> Message-ID: <5192A56B-5891-4FCE-B7C1-BA91568DB8D6@macports.org> On Jun 25, 2008, at 01:32, Tom Allison wrote: > Ryan Schmidt wrote: > >> On Jun 24, 2008, at 21:38, Tom Allison wrote: >> >>> I ran into a problem with trying to set up a cgi page on my macbook. >>> >>> The code uses CGI and DBD::Pg. >>> From the command line, it works great. >>> >>> From Apache it works badly... >>> >>> Can't load >>> '/Library/Perl/5.8.6/darwin-thread-multi-2level/auto/DBD/Pg/ >>> Pg.bundle' >>> for module DBD::Pg: >>> dlopen(/Library/Perl/5.8.6/darwin-thread-multi-2level/auto/DBD/Pg/ >>> Pg.bundle, >>> 1): Library not loaded: /usr/local/pgsql/lib/libpq.5.dylib >>> >>> >>> I have no /usr/local/pgsql/... >>> But I have a >>> /opt/local/lib/postgresql83/libpq.5.dylib >>> >>> which was put there by the mac port installation. >>> >>> How do I get these mac port installations playing nice together? >> >> As you said, MacPorts doesn't put things in /usr/local. It doesn't >> put things in /Library/Perl either. The fact that from Apache it's >> trying to load something in /Library/Perl suggests that from >> Apache you're trying to use Apple's Perl instead of the Perl from >> MacPorts. >> You didn't say which Apache. Is this apache2 from MacPorts? >> How do you test this from the command line? What command do you >> run? If there is a perl source file involved, can you provide it? >> How do you test this from Apache? > > It's the macport Apache (apache2). All the mentinoed packages are > from mac port. > > pg-dbd-pg is installed. > apache2 is installed and running. > > which perl tells me I'm runnign /opt/local/bin/perl from the > command line, My assumption is that if I'm running this perl > installation, and apache2 was installed by mac port -- isn't it > running the same perl? > > How can I tell? > > And if they are running the same version then it should see the path. I don't know. The last time I used Perl CGIs was about ten years ago so I'm a bit rusty. That's why I'm asking you. What all did you do to get to where you are now? In other words, what do I need to do to see the same error on my computer, so that I can begin debugging the problem? Please Reply All so that your reply goes to the mailing list too, not just to me. From tom at tacocat.net Tue Jun 24 23:54:24 2008 From: tom at tacocat.net (Tom Allison) Date: Wed, 25 Jun 2008 02:54:24 -0400 Subject: apache, postgresql, perl In-Reply-To: <5192A56B-5891-4FCE-B7C1-BA91568DB8D6@macports.org> References: <4861AFA3.5070904@tacocat.net> <0470D764-B1B7-4FB3-B582-ABF6691D3D1D@macports.org> <4861E66A.1060804@tacocat.net> <5192A56B-5891-4FCE-B7C1-BA91568DB8D6@macports.org> Message-ID: <4861EBA0.9050606@tacocat.net> Ryan Schmidt wrote: > On Jun 25, 2008, at 01:32, Tom Allison wrote: > >> Ryan Schmidt wrote: >> >>> On Jun 24, 2008, at 21:38, Tom Allison wrote: >>> >>>> I ran into a problem with trying to set up a cgi page on my macbook. >>>> >>>> The code uses CGI and DBD::Pg. >>>> From the command line, it works great. >>>> >>>> From Apache it works badly... >>>> >>>> Can't load >>>> '/Library/Perl/5.8.6/darwin-thread-multi-2level/auto/DBD/Pg/Pg.bundle' >>>> for module DBD::Pg: >>>> dlopen(/Library/Perl/5.8.6/darwin-thread-multi-2level/auto/DBD/Pg/Pg.bundle, >>>> >>>> 1): Library not loaded: /usr/local/pgsql/lib/libpq.5.dylib >>>> >>>> >>>> I have no /usr/local/pgsql/... >>>> But I have a >>>> /opt/local/lib/postgresql83/libpq.5.dylib >>>> >>>> which was put there by the mac port installation. >>>> >>>> How do I get these mac port installations playing nice together? >>> >>> As you said, MacPorts doesn't put things in /usr/local. It doesn't >>> put things in /Library/Perl either. The fact that from Apache it's >>> trying to load something in /Library/Perl suggests that from Apache >>> you're trying to use Apple's Perl instead of the Perl from MacPorts. >>> You didn't say which Apache. Is this apache2 from MacPorts? >>> How do you test this from the command line? What command do you run? >>> If there is a perl source file involved, can you provide it? How do >>> you test this from Apache? >> >> It's the macport Apache (apache2). All the mentinoed packages are >> from mac port. >> >> pg-dbd-pg is installed. >> apache2 is installed and running. >> >> which perl tells me I'm runnign /opt/local/bin/perl from the command >> line, My assumption is that if I'm running this perl installation, >> and apache2 was installed by mac port -- isn't it running the same perl? >> >> How can I tell? >> >> And if they are running the same version then it should see the path. > > I don't know. The last time I used Perl CGIs was about ten years ago so > I'm a bit rusty. That's why I'm asking you. What all did you do to get > to where you are now? In other words, what do I need to do to see the > same error on my computer, so that I can begin debugging the problem? > > Please Reply All so that your reply goes to the mailing list too, not > just to me. > > I'm not sure exactly what may be required to create the problem originally as I was not having this problem originally. Last year I wrote several CGI and FCGI based projects on my notebook. Since then the only thing I've run is: upgrade installed. earlier this morning I ran this again and upgraded all my mac port stuff with the exception of ruby. Of course, as the result of this, right now I can't even get users to run any cgi (eg: /~tom/works.cgi) AllowOverride FileInfo AuthConfig Limit Indexes Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec ExecCGI Order allow,deny Allow from all Order deny,allow Deny from all From jmedley at aesrg.tamu.edu Wed Jun 25 06:34:14 2008 From: jmedley at aesrg.tamu.edu (James Medley) Date: Wed, 25 Jun 2008 08:34:14 -0500 Subject: installing ntop Message-ID: I am trying to install ntop on an iMac 20" Intel (2.16 GHz Intel Core 2 Duo, 2 GB 667 MHz DDR2 SDRAM) running OS X 10.5.3. I am following directions from . I give the command "sudo port install ntop +server" in Terminal and after installing several packages, I eventually get this error with rrdtool. Unfortunately, I'm not command line savvy enough to figure out where to go and what to do. Could somebody please put this in simpler terms. Thanks Much, Jim ---> Configuring rrdtool 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_rrdtool/work/rrdtool-1.3.0" && ./ configure --prefix=/opt/local --prefix=/opt/local --enable-perl-site- install --with-tcllib=/opt/local/lib --disable-python --disable-ruby -- disable-tcl --mandir=/opt/local/share/man " returned error 1 Command output: You may want to set the PKG_CONFIG_PATH variable to point to its location. ---------------------------------------------------------------------------- configure: WARNING: ---------------------------------------------------------------------------- * I could not find a working copy of pangocairo. Check config.log for hints on why this is the case. Maybe you need to set LDFLAGS and CPPFLAGS appropriately so that compiler and the linker can find libpango-1.0 and its header files. If you have not installed pangocairo, you can get it either from its original home on http://ftp.gnome.org/pub/GNOME/sources/pango/1.17 You can find also find an archive copy on http://oss.oetiker.ch/rrdtool/pub/libs The last tested version of pangocairo is 1.17. LIBS=-lcairo -lcairo -lcairo -lcairo -lSM -lICE -lfontconfig - lexpat -lfreetype -lz -lpng12 -lXrender -lX11 -lpixman-1 LDFLAGS=-L/opt/local/lib -L/opt/local/lib -L/usr/X11/lib -R/usr/ X11/lib -Wl,-framework,CoreServices -Wl,-framework,ApplicationServices CPPFLAGS=-I/opt/local/include -I/opt/local/include/freetype2 -I/ opt/local/include/libpng -D_THREAD_SAFE -DXTHREADS -I/opt/local/ include/cairo -I/opt/local/include/libpng12 -I/opt/local/include/ freetype2 -I/opt/local/include -I/usr/X11/include -I/opt/local/include/ pixman-1 ---------------------------------------------------------------------------- checking for xmlParseFile in -lxml2... yes checking libxml/parser.h usability... yes checking libxml/parser.h presence... yes checking for libxml/parser.h... yes configure: error: Please fix the library issues listed above and try again. Error: The following dependencies failed to build: rrdtool Error: Status 1 encountered during processing. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080625/01655b89/attachment.htm From dluke at geeklair.net Wed Jun 25 07:38:58 2008 From: dluke at geeklair.net (Daniel J. Luke) Date: Wed, 25 Jun 2008 10:38:58 -0400 Subject: apache, postgresql, perl In-Reply-To: <4861EBA0.9050606@tacocat.net> References: <4861AFA3.5070904@tacocat.net> <0470D764-B1B7-4FB3-B582-ABF6691D3D1D@macports.org> <4861E66A.1060804@tacocat.net> <5192A56B-5891-4FCE-B7C1-BA91568DB8D6@macports.org> <4861EBA0.9050606@tacocat.net> Message-ID: <992FDF24-283B-41C8-A0FA-A416BA4E6A58@geeklair.net> On Jun 25, 2008, at 2:54 AM, Tom Allison wrote: > Of course, as the result of this, right now I can't even get users to > run any cgi (eg: /~tom/works.cgi) > > > AllowOverride FileInfo AuthConfig Limit Indexes > Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec > ExecCGI > > Order allow,deny > Allow from all > > > Order deny,allow > Deny from all > > Whats your #! line look like in your test cgi script (should be something like #!/opt/local/bin/perl) -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080625/e4950f64/attachment.sig From dluke at geeklair.net Wed Jun 25 07:40:54 2008 From: dluke at geeklair.net (Daniel J. Luke) Date: Wed, 25 Jun 2008 10:40:54 -0400 Subject: postgresql configuration In-Reply-To: <4861E83D.9010709@tacocat.net> References: <4861E83D.9010709@tacocat.net> Message-ID: On Jun 25, 2008, at 2:39 AM, Tom Allison wrote: > where are the configuration files for postgresql83? wherever you decided to put them (they get installed in the directory you pass to initdb). If you followed the instructions in the postgresql83-server port, they're probably in: /opt/local/var/db/postgresql83/defaultdb -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080625/7060fa15/attachment.sig From jmedley at aesrg.tamu.edu Wed Jun 25 07:54:29 2008 From: jmedley at aesrg.tamu.edu (James Medley) Date: Wed, 25 Jun 2008 09:54:29 -0500 Subject: installing ntop In-Reply-To: References: Message-ID: As an update, I decided to try "sudo port install pango", which it did. I then went back to "sudo port install ntop +server" which it did and without the rrdtool error. Now I enter the command "sudo ntop @/ opt/local/ntop/ntop.conf -d" and I get the message: Processing file /opt/local/etc/ntop/ntop.conf for parameters... Wed Jun 25 09:48:12 2008 NOTE: Interface merge enabled by default ntop: unrecognized option `--set-pcap-nonblock' Wed Jun 25 09:48:12 2008 Initializing gdbm databases ntop: unrecognized option `--set-pcap-nonblock' FATAL ERROR: unknown ntop option, '?' Welcome to ntop v.3.3 [Configured on Jun 25 2008 8:43:23, built on Jun 25 2008 08:44:06] Copyright 1998-2007 by Luca Deri . Get the freshest ntop from http://www.ntop.org/ When I do a "ps -ax |grep ntop" I get: 18509 ttys000 0:00.00 grep ntop So, I'm still having a problem. Any solutions? Thanks, Jim On Jun 25, 2008, at 8:34 AM, James Medley wrote: > I am trying to install ntop on an iMac 20" Intel (2.16 GHz Intel > Core 2 Duo, 2 GB 667 MHz DDR2 SDRAM) running OS X 10.5.3. I am > following directions from >. I give the command "sudo port install ntop +server" in Terminal > and after installing several packages, I eventually get this error > with rrdtool. Unfortunately, I'm not command line savvy enough to > figure out where to go and what to do. Could somebody please put > this in simpler terms. Thanks Much, Jim > > ---> Configuring rrdtool > 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_rrdtool/work/rrdtool-1.3.0" && ./ > configure --prefix=/opt/local --prefix=/opt/local --enable-perl-site- > install --with-tcllib=/opt/local/lib --disable-python --disable-ruby > --disable-tcl --mandir=/opt/local/share/man " returned error 1 > Command output: You may want to set the PKG_CONFIG_PATH variable > to point to its > location. > ---------------------------------------------------------------------------- > > configure: WARNING: > ---------------------------------------------------------------------------- > * I could not find a working copy of pangocairo. Check config.log > for hints on why > this is the case. Maybe you need to set LDFLAGS and CPPFLAGS > appropriately > so that compiler and the linker can find libpango-1.0 and its > header files. If > you have not installed pangocairo, you can get it either from its > original home on > > http://ftp.gnome.org/pub/GNOME/sources/pango/1.17 > > You can find also find an archive copy on > > http://oss.oetiker.ch/rrdtool/pub/libs > > The last tested version of pangocairo is 1.17. > > LIBS=-lcairo -lcairo -lcairo -lcairo -lSM -lICE -lfontconfig > -lexpat -lfreetype -lz -lpng12 -lXrender -lX11 -lpixman-1 > LDFLAGS=-L/opt/local/lib -L/opt/local/lib -L/usr/X11/lib -R/usr/ > X11/lib -Wl,-framework,CoreServices -Wl,-framework,ApplicationServices > CPPFLAGS=-I/opt/local/include -I/opt/local/include/freetype2 -I/ > opt/local/include/libpng -D_THREAD_SAFE -DXTHREADS -I/opt/local/ > include/cairo -I/opt/local/include/libpng12 -I/opt/local/include/ > freetype2 -I/opt/local/include -I/usr/X11/include -I/opt/local/ > include/pixman-1 > > ---------------------------------------------------------------------------- > > checking for xmlParseFile in -lxml2... yes > checking libxml/parser.h usability... yes > checking libxml/parser.h presence... yes > checking for libxml/parser.h... yes > configure: error: Please fix the library issues listed above and try > again. > > Error: The following dependencies failed to build: rrdtool > Error: Status 1 encountered during processing. > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080625/b27504de/attachment.htm From tom at tacocat.net Wed Jun 25 09:59:08 2008 From: tom at tacocat.net (Tom Allison) Date: Wed, 25 Jun 2008 12:59:08 -0400 Subject: apache, postgresql, perl In-Reply-To: <992FDF24-283B-41C8-A0FA-A416BA4E6A58@geeklair.net> References: <4861AFA3.5070904@tacocat.net> <0470D764-B1B7-4FB3-B582-ABF6691D3D1D@macports.org> <4861E66A.1060804@tacocat.net> <5192A56B-5891-4FCE-B7C1-BA91568DB8D6@macports.org> <4861EBA0.9050606@tacocat.net> <992FDF24-283B-41C8-A0FA-A416BA4E6A58@geeklair.net> Message-ID: <05AA0BD0-2D49-4BDC-92D9-C90F4030F8F0@tacocat.net> Excellent point! I'll have to try this out when I get to my machine. Sent from my iPhone. On Jun 25, 2008, at 10:38 AM, "Daniel J. Luke" wrote: > On Jun 25, 2008, at 2:54 AM, Tom Allison wrote: >> Of course, as the result of this, right now I can't even get users to >> run any cgi (eg: /~tom/works.cgi) >> >> >> AllowOverride FileInfo AuthConfig Limit Indexes >> Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec >> ExecCGI >> >> Order allow,deny >> Allow from all >> >> >> Order deny,allow >> Deny from all >> >> > > > Whats your #! line look like in your test cgi script (should be > something like #!/opt/local/bin/perl) > > -- > Daniel J. Luke > +========================================================+ > | *---------------- dluke at geeklair.net ----------------* | > | *-------------- http://www.geeklair.net -------------* | > +========================================================+ > | Opinions expressed are mine and do not necessarily | > | reflect the opinions of my employer. | > +========================================================+ > > > From ryandesign at macports.org Wed Jun 25 11:16:56 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 25 Jun 2008 13:16:56 -0500 Subject: installing ntop In-Reply-To: References: Message-ID: <1EFADBD5-C6EB-4169-9B94-DAFB50C5ED2F@macports.org> On Jun 25, 2008, at 9:54 AM, James Medley wrote: > As an update, I decided to try "sudo port install pango", which it > did. I then went back to "sudo port install ntop +server" which it > did and without the rrdtool error. Thanks for letting us know. I filed a ticket requesting that pango (and some other ports) be added to rrdtool's dependency list. http://trac.macports.org/ticket/15748 > Now I enter the command "sudo ntop @/opt/local/ntop/ntop.conf -d" > and I get the message: > > Processing file /opt/local/etc/ntop/ntop.conf for parameters... > Wed Jun 25 09:48:12 2008 NOTE: Interface merge enabled by default > ntop: unrecognized option `--set-pcap-nonblock' > Wed Jun 25 09:48:12 2008 Initializing gdbm databases > ntop: unrecognized option `--set-pcap-nonblock' > FATAL ERROR: unknown ntop option, '?' > Welcome to ntop v.3.3 > [Configured on Jun 25 2008 8:43:23, built on Jun 25 2008 08:44:06] > Copyright 1998-2007 by Luca Deri . > Get the freshest ntop from http://www.ntop.org/ > > When I do a "ps -ax |grep ntop" I get: > > 18509 ttys000 0:00.00 grep ntop > > So, I'm still having a problem. Any solutions? Here I'm not sure. I haven't used ntop so I don't know its options. Do the contents of /opt/local/ntop/ntop.conf look ok to you? From davis at guydavis.ca Wed Jun 25 12:08:19 2008 From: davis at guydavis.ca (Guy Davis) Date: Wed, 25 Jun 2008 13:08:19 -0600 Subject: tomcatctl fails to stop Tomcat In-Reply-To: <2b7747b70806251159t3abb75ddv8dc008d780b182e4@mail.gmail.com> References: <2b7747b70806251159t3abb75ddv8dc008d780b182e4@mail.gmail.com> Message-ID: <2b7747b70806251208n529a88fcpac555508588e148e@mail.gmail.com> Hi, I'm moving from a Fedora Core system for my JSP-based web site to Mac OSX 10.5. I just installed Apache, mod_jk, and Tomcat 5 using MacPorts. However, even though Tomcat's server.xml file has the following: a quick netstat shows that Tomcat is not actually listening to 8005 when it starts. So when I run: sudo tomcatctl stop I get this on the console: Stopping Tomcat...(pid 3468)............... giving up. and this in catalina.2008-06-25.log: Jun 24, 2008 9:37:20 PM org.apache.catalina.startup.Catalina stopServer SEVERE: Catalina.stop: java.net.ConnectException: Connection refused ... Any ideas? How are people currently stopping tomcat? Right now all I can do is 'kill PID' and then it is restarted (by daemondo?) Thanks, Guy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080625/6a519431/attachment.htm From ryandesign at macports.org Wed Jun 25 12:56:27 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 25 Jun 2008 14:56:27 -0500 Subject: tomcatctl fails to stop Tomcat In-Reply-To: <2b7747b70806251208n529a88fcpac555508588e148e@mail.gmail.com> References: <2b7747b70806251159t3abb75ddv8dc008d780b182e4@mail.gmail.com> <2b7747b70806251208n529a88fcpac555508588e148e@mail.gmail.com> Message-ID: <836B3A9B-55EC-468C-B672-45D56206FCE0@macports.org> On Jun 25, 2008, at 14:08, Guy Davis wrote: > Hi, I'm moving from a Fedora Core system for my JSP-based web site > to Mac OSX > 10.5. I just installed Apache, mod_jk, and Tomcat 5 using MacPorts. > However, even though Tomcat's server.xml file has the following: > > > > a quick netstat shows that Tomcat is not actually listening to 8005 > when it > starts. So when I run: > > sudo tomcatctl stop > > I get this on the console: > > Stopping Tomcat...(pid 3468)............... giving up. > > and this in catalina.2008-06-25.log: > > Jun 24, 2008 9:37:20 PM org.apache.catalina.startup > .Catalina stopServer > SEVERE: Catalina.stop: > java.net.ConnectException: Connection refused > ... > > Any ideas? How are people currently stopping tomcat? Right now > all I can do is 'kill PID' and then it is restarted (by daemondo?) Have you tried: sudo launchctl -w unload /Library/LaunchDaemons/ org.macports.tomcat5.plist That would be the usual way to stop any launchd-managed process. To start it again: sudo launchctl -w load /Library/LaunchDaemons/org.macports.tomcat5.plist From davis at guydavis.ca Wed Jun 25 13:24:00 2008 From: davis at guydavis.ca (Guy Davis) Date: Wed, 25 Jun 2008 14:24:00 -0600 Subject: tomcatctl fails to stop Tomcat In-Reply-To: <836B3A9B-55EC-468C-B672-45D56206FCE0@macports.org> References: <2b7747b70806251159t3abb75ddv8dc008d780b182e4@mail.gmail.com> <2b7747b70806251208n529a88fcpac555508588e148e@mail.gmail.com> <836B3A9B-55EC-468C-B672-45D56206FCE0@macports.org> Message-ID: <2b7747b70806251324y639744b3i3ee28062753a77c@mail.gmail.com> Hi Ryan, Thanks. Those worked with the -w switch after the load/unload. I've aliased them as tomcatstart and tomcatstop in my .profile and I won't use tomcatctl. Guy On Wed, Jun 25, 2008 at 1:56 PM, Ryan Schmidt wrote: > On Jun 25, 2008, at 14:08, Guy Davis wrote: > > Hi, I'm moving from a Fedora Core system for my JSP-based web site to Mac >> OSX >> 10.5. I just installed Apache, mod_jk, and Tomcat 5 using MacPorts. >> However, even though Tomcat's server.xml file has the following: >> >> >> >> a quick netstat shows that Tomcat is not actually listening to 8005 when >> it >> starts. So when I run: >> >> sudo tomcatctl stop >> >> I get this on the console: >> >> Stopping Tomcat...(pid 3468)............... giving up. >> >> and this in catalina.2008-06-25.log: >> >> Jun 24, 2008 9:37:20 PM org.apache.catalina.startup >> .Catalina stopServer >> SEVERE: Catalina.stop: >> java.net.ConnectException: Connection refused >> ... >> >> Any ideas? How are people currently stopping tomcat? Right now all I can >> do is 'kill PID' and then it is restarted (by daemondo?) >> > > Have you tried: > > sudo launchctl -w unload /Library/LaunchDaemons/org.macports.tomcat5.plist > > That would be the usual way to stop any launchd-managed process. To start > it again: > > sudo launchctl -w load /Library/LaunchDaemons/org.macports.tomcat5.plist > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080625/190a455e/attachment.htm From macsforever2000 at macports.org Wed Jun 25 13:41:42 2008 From: macsforever2000 at macports.org (Frank Schima) Date: Wed, 25 Jun 2008 14:41:42 -0600 Subject: Using wxPython In-Reply-To: <1994CEC2-81BA-4CDC-A4BA-5F49AEAFD17B@macports.org> References: <99867DB8-BA2A-412B-9A46-3E475E6E52B3@macports.org> <740B2048-73DA-48E9-B7AA-C51F7746234B@macports.org> <1994CEC2-81BA-4CDC-A4BA-5F49AEAFD17B@macports.org> Message-ID: <5BC4631F-B3FD-41D8-9E6A-90ABD3E04CDB@macports.org> On May 24, 2008, at 2:24 AM, Ryan Schmidt wrote: > On May 20, 2008, at 17:47, Frank Schima wrote: > >> On May 20, 2008, at 4:28 PM, Frank Schima wrote: >> >>> I'm trying to run a simple wxPython program, but I get a strange >>> error: >>> >>> This program needs access to the screen. >>> Please run with 'pythonw', not 'python', and only when you are >>> logged >>> in on the main display of your Mac. >> >> [deleted] >> >>> There is no "pythonw" in the MacPorts version of Python 2.5. Does >>> anyone know how I can use wxPython with MacPorts? >>> >>> I'm running Mac OS X 10.5.2 on a Mac Pro. Xcode 3.0. MacPorts 1.6. >> >> I see this ticket is related to all this: >> > > Also: > > http://trac.macports.org/ticket/12817 > > >> Is there a status on when this might be fixed? :) I just wanted to give a huge THANK YOU to everyone involved for fixing bug 11267 and making Python 2.5 a framework build. Now wxPython finally works for me! I think we can close 12817 too. Cheers! Frank From m_nez_j at mac.com Wed Jun 25 15:00:09 2008 From: m_nez_j at mac.com (Mack) Date: Wed, 25 Jun 2008 15:00:09 -0700 Subject: noProfile Message-ID: <2E72BA53-0381-4BC0-B498-1B764D4CAE33@mac.com> Hi, my install didn't create a .profile for me. Do I create one? how do I do this? mack From raimue at macports.org Wed Jun 25 16:41:13 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Thu, 26 Jun 2008 01:41:13 +0200 Subject: Using wxPython In-Reply-To: <5BC4631F-B3FD-41D8-9E6A-90ABD3E04CDB@macports.org> References: <99867DB8-BA2A-412B-9A46-3E475E6E52B3@macports.org> <740B2048-73DA-48E9-B7AA-C51F7746234B@macports.org> <1994CEC2-81BA-4CDC-A4BA-5F49AEAFD17B@macports.org> <5BC4631F-B3FD-41D8-9E6A-90ABD3E04CDB@macports.org> Message-ID: <4862D799.8040305@macports.org> Frank Schima wrote: > I just wanted to give a huge THANK YOU to everyone involved for fixing > bug 11267 and making Python 2.5 a framework build. Now wxPython > finally works for me! I think we can close 12817 too. I agree, I closed #12817. Rainer From 0x62_0x6c_0x62 at pobox.com Wed Jun 25 16:49:17 2008 From: 0x62_0x6c_0x62 at pobox.com (Bryan Blackburn) Date: Wed, 25 Jun 2008 17:49:17 -0600 Subject: noProfile In-Reply-To: <2E72BA53-0381-4BC0-B498-1B764D4CAE33@mac.com> References: <2E72BA53-0381-4BC0-B498-1B764D4CAE33@mac.com> Message-ID: On Jun 25, 2008, at 4:00 PM, Mack wrote: > Hi, my install didn't create a .profile for me. Do I create one? how > do I do this? > See Bryan > mack From tom at tacocat.net Wed Jun 25 18:19:20 2008 From: tom at tacocat.net (Tom Allison) Date: Wed, 25 Jun 2008 21:19:20 -0400 Subject: apache, postgresql, perl In-Reply-To: <992FDF24-283B-41C8-A0FA-A416BA4E6A58@geeklair.net> References: <4861AFA3.5070904@tacocat.net> <0470D764-B1B7-4FB3-B582-ABF6691D3D1D@macports.org> <4861E66A.1060804@tacocat.net> <5192A56B-5891-4FCE-B7C1-BA91568DB8D6@macports.org> <4861EBA0.9050606@tacocat.net> <992FDF24-283B-41C8-A0FA-A416BA4E6A58@geeklair.net> Message-ID: <4862EE98.8080806@tacocat.net> Daniel J. Luke wrote: > On Jun 25, 2008, at 2:54 AM, Tom Allison wrote: >> Of course, as the result of this, right now I can't even get users to >> run any cgi (eg: /~tom/works.cgi) >> >> >> AllowOverride FileInfo AuthConfig Limit Indexes >> Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec >> ExecCGI >> >> Order allow,deny >> Allow from all >> >> >> Order deny,allow >> Deny from all >> >> > > > Whats your #! line look like in your test cgi script (should be > something like #!/opt/local/bin/perl) Well, that idea is a bust. Best I can get the source code displayed as text/ascii. Shouldn't the AddHandler and ExecCGI cover this? From dluke at geeklair.net Wed Jun 25 18:24:49 2008 From: dluke at geeklair.net (Daniel J. Luke) Date: Wed, 25 Jun 2008 21:24:49 -0400 Subject: apache, postgresql, perl In-Reply-To: <4862EE98.8080806@tacocat.net> References: <4861AFA3.5070904@tacocat.net> <0470D764-B1B7-4FB3-B582-ABF6691D3D1D@macports.org> <4861E66A.1060804@tacocat.net> <5192A56B-5891-4FCE-B7C1-BA91568DB8D6@macports.org> <4861EBA0.9050606@tacocat.net> <992FDF24-283B-41C8-A0FA-A416BA4E6A58@geeklair.net> <4862EE98.8080806@tacocat.net> Message-ID: <334C869C-FFFF-4CBB-BFB0-AAD9D8277673@geeklair.net> On Jun 25, 2008, at 9:19 PM, Tom Allison wrote: >> Whats your #! line look like in your test cgi script (should be >> something like #!/opt/local/bin/perl) > > Well, that idea is a bust. > > Best I can get the source code displayed as text/ascii. So, the first line of the script should be your #! line (but you should be able to log into the server and look at the script with more/cat/head/vi/whatever) > Shouldn't the AddHandler and ExecCGI cover this? probably not (since they just tell Apache to exec() the file. If you think about it, your CGI could be written in C, perl, python, ruby, tcl, or many other languages). -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080625/03329b7f/attachment.sig From m_nez_j at mac.com Wed Jun 25 18:29:24 2008 From: m_nez_j at mac.com (Mack) Date: Wed, 25 Jun 2008 18:29:24 -0700 Subject: hellanzb Message-ID: Anyone know what I could do to get this installed? 6-2.4/zope/interface/tests running build_ext building '_zope_interface_coptimizations' extension creating build/temp.macosx-10.3-i386-2.4 creating build/temp.macosx-10.3-i386-2.4/src creating build/temp.macosx-10.3-i386-2.4/src/zope creating build/temp.macosx-10.3-i386-2.4/src/zope/interface -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -fno-common -fno- common -dynamic -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/opt/local/ include/python2.4 -c src/zope/interface/ _zope_interface_coptimizations.c -o build/temp.macosx-10.3-i386-2.4/ src/zope/interface/_zope_interface_coptimizations.o unable to execute -fno-strict-aliasing: No such file or directory error: command '-fno-strict-aliasing' failed with exit status 1 Error: The following dependencies failed to build: py-twisted py- zopeinterface shorten unrar Error: Status 1 encountered during processing. From 0x62_0x6c_0x62 at pobox.com Wed Jun 25 18:54:09 2008 From: 0x62_0x6c_0x62 at pobox.com (Bryan Blackburn) Date: Wed, 25 Jun 2008 19:54:09 -0600 Subject: hellanzb In-Reply-To: References: Message-ID: On Jun 25, 2008, at 7:29 PM, Mack wrote: > Anyone know what I could do to get this installed? > > 6-2.4/zope/interface/tests > running build_ext > building '_zope_interface_coptimizations' extension > creating build/temp.macosx-10.3-i386-2.4 > creating build/temp.macosx-10.3-i386-2.4/src > creating build/temp.macosx-10.3-i386-2.4/src/zope > creating build/temp.macosx-10.3-i386-2.4/src/zope/interface > -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -fno-common - > fno- > common -dynamic -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/opt/ > local/ > include/python2.4 -c src/zope/interface/ > _zope_interface_coptimizations.c -o build/temp.macosx-10.3-i386-2.4/ > src/zope/interface/_zope_interface_coptimizations.o > unable to execute -fno-strict-aliasing: No such file or directory > error: command '-fno-strict-aliasing' failed with exit status 1 > Looks like the infamous Tcl environment bug: Do a 'sudo port clean --work py-zopeinterface' then try your original install again. Bryan > Error: The following dependencies failed to build: py-twisted py- > zopeinterface shorten unrar > Error: Status 1 encountered during processing. > From tegbains at tegbains.com Thu Jun 26 00:12:35 2008 From: tegbains at tegbains.com (Teg Bains) Date: Thu, 26 Jun 2008 00:12:35 -0700 Subject: MySQL5 source headers Message-ID: I have looked through the guides, but I cannot figure out where to find the header files. Specifically for mysql5. I have a program (cpgav) that needs the header files :( Thanks, Teg Bains From 0x62_0x6c_0x62 at pobox.com Thu Jun 26 00:45:11 2008 From: 0x62_0x6c_0x62 at pobox.com (Bryan Blackburn) Date: Thu, 26 Jun 2008 01:45:11 -0600 Subject: MySQL5 source headers In-Reply-To: References: Message-ID: <47C67DD9-97BB-4803-8F03-CC44A627431D@pobox.com> On Jun 26, 2008, at 1:12 AM, Teg Bains wrote: > I have looked through the guides, but I cannot figure out where to > find the header files. Specifically for mysql5. I have a program > (cpgav) that needs the header files :( > > Thanks, > (Dang, first time I didn't send to the list, so resent...) Headers installed with ports are usually in /opt/local/include, but mysql5 uses a subdirectory: /opt/local/include/mysql5. Also note libraries for mysql5 are in /opt/local/lib/mysql5/mysql. Bryan > Teg Bains From face at CentosPrime.COM Thu Jun 26 07:51:12 2008 From: face at CentosPrime.COM (Chris Janton) Date: Thu, 26 Jun 2008 07:51:12 -0700 Subject: MySQL5 source headers In-Reply-To: References: Message-ID: On 2008-06-26 , at 00:12 , Teg Bains wrote: > I have looked through the guides, but I cannot figure out where to > find the header files. Specifically for mysql5. I have a program > (cpgav) that needs the header files :( Use "mysql_config" to determine where the include libraries are... face at mac:~:125 $ mysql_config5 --include -I/opt/local/include/mysql5/mysql 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From lars.sonchocky-helldorf at hamburg.de Thu Jun 26 16:37:14 2008 From: lars.sonchocky-helldorf at hamburg.de (Lars Sonchocky-Helldorf) Date: Fri, 27 Jun 2008 01:37:14 +0200 Subject: Is "MacPort" a valid term? In-Reply-To: References: <87BCE6D9-288A-4179-8812-2383DDF8B828@apple.com> <1214356531.7005.48.camel@pokey.kendallshaw.com> <52880460-862D-4ADC-9319-7385CD92F269@mac.com> Message-ID: Am 25.06.2008 um 07:21 schrieb Ryan Schmidt: > > On Jun 24, 2008, at 21:21, Zav Public wrote: > >> What are these ports? What do they constitute? Is there a term that >> can define them? > > They are software packages. I can't think of a more specific term > that would still apply to all ports. > > MacPorts is a package manager, or a package management system: > > http://en.wikipedia.org/wiki/Package_management_system > > So we could say we install packages. Instead, for now, we say we > install ports, because the term "port" is used by the FreeBSD ports > project which inspired MacPorts. This causes confusion with other > uses of the word "port" (a software network connection; a physical > connector on an electronic device; the process of rewriting software > from one platform so it runs on another). However, the term "package" > would also cause confusion on Mac OS X, because Apple uses the term > "package" for software installed through its Installer program, and > MacPorts does not make use of this. > how about "packs" then? Or "MacPacks" if you want so ? >> regards, Lars From tabithamc at gmail.com Sat Jun 28 01:33:05 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Fri, 27 Jun 2008 22:33:05 -1000 Subject: Recommendations for converting WAV to MP3? Message-ID: <7fccb3000806280133j5817a7caof913a28a40564d28@mail.gmail.com> Hi all -- I noticed among MacPorts there is a collection of audio-related tools -- many of them in fact. Can someone recommend a command-line tool to convert (one or batch) WAV files to MP3 format? Something simple would be great. I just have no idea where to start (audio is not my forte). Thanks, -T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080627/bdfe6768/attachment.html From ryandesign at macports.org Sat Jun 28 02:12:34 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 28 Jun 2008 04:12:34 -0500 Subject: Recommendations for converting WAV to MP3? In-Reply-To: <7fccb3000806280133j5817a7caof913a28a40564d28@mail.gmail.com> References: <7fccb3000806280133j5817a7caof913a28a40564d28@mail.gmail.com> Message-ID: <71F2D420-5023-4586-B716-24D4984D2405@macports.org> On Jun 28, 2008, at 03:33, Tabitha McNerney wrote: > I noticed among MacPorts there is a collection of audio-related > tools -- many of them in fact. Can someone recommend a command-line > tool to convert (one or batch) WAV files to MP3 format? Something > simple would be great. I just have no idea where to start (audio is > not my forte). Honestly, I'd recommend Apple's iTunes. Drag all your WAV files into iTunes. Then go to iTunes - Preferences - Advanced - Importing and set your encoding settings the way you want them (MP3 or AAC (a.k.a. M4A), bitrate, mono/stereo, etc.). Then select all your imported WAV files in the library and choose "Convert Selection to MP3" (or "to AAC") from the Advanced menu. Then you can delete the WAV files from iTunes. From tabithamc at gmail.com Sat Jun 28 02:27:51 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Fri, 27 Jun 2008 23:27:51 -1000 Subject: Recommendations for converting WAV to MP3? In-Reply-To: <71F2D420-5023-4586-B716-24D4984D2405@macports.org> References: <7fccb3000806280133j5817a7caof913a28a40564d28@mail.gmail.com> <71F2D420-5023-4586-B716-24D4984D2405@macports.org> Message-ID: <7fccb3000806280227i1b45465i4d27199b249d42b6@mail.gmail.com> Hi Ryan, Indeed a good idea. Though, is there a way to batch? I suppose one could write an Apple Script to drive iTunes. It would be nice to have a purely command-line option besides iTunes, if that's possible. Thanks, T.M. On Fri, Jun 27, 2008 at 11:12 PM, Ryan Schmidt wrote: > On Jun 28, 2008, at 03:33, Tabitha McNerney wrote: > > I noticed among MacPorts there is a collection of audio-related tools -- >> many of them in fact. Can someone recommend a command-line tool to convert >> (one or batch) WAV files to MP3 format? Something simple would be great. I >> just have no idea where to start (audio is not my forte). >> > > Honestly, I'd recommend Apple's iTunes. Drag all your WAV files into > iTunes. Then go to iTunes - Preferences - Advanced - Importing and set your > encoding settings the way you want them (MP3 or AAC (a.k.a. M4A), bitrate, > mono/stereo, etc.). Then select all your imported WAV files in the library > and choose "Convert Selection to MP3" (or "to AAC") from the Advanced menu. > Then you can delete the WAV files from iTunes. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080627/d890897a/attachment.html From ryandesign at macports.org Sat Jun 28 02:33:25 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 28 Jun 2008 04:33:25 -0500 Subject: Recommendations for converting WAV to MP3? In-Reply-To: <7fccb3000806280227i1b45465i4d27199b249d42b6@mail.gmail.com> References: <7fccb3000806280133j5817a7caof913a28a40564d28@mail.gmail.com> <71F2D420-5023-4586-B716-24D4984D2405@macports.org> <7fccb3000806280227i1b45465i4d27199b249d42b6@mail.gmail.com> Message-ID: On Jun 28, 2008, at 04:27, Tabitha McNerney wrote: > On Fri, Jun 27, 2008 at 11:12 PM, Ryan Schmidt wrote: > >> On Jun 28, 2008, at 03:33, Tabitha McNerney wrote: >> >>> I noticed among MacPorts there is a collection of audio-related >>> tools -- many of them in fact. Can someone recommend a command- >>> line tool to convert (one or batch) WAV files to MP3 format? >>> Something simple would be great. I just have no idea where to >>> start (audio is not my forte). >> >> Honestly, I'd recommend Apple's iTunes. Drag all your WAV files >> into iTunes. Then go to iTunes - Preferences - Advanced - >> Importing and set your encoding settings the way you want them >> (MP3 or AAC (a.k.a. M4A), bitrate, mono/stereo, etc.). Then select >> all your imported WAV files in the library and choose "Convert >> Selection to MP3" (or "to AAC") from the Advanced menu. Then you >> can delete the WAV files from iTunes. > > Indeed a good idea. Though, is there a way to batch? I suppose one > could write an Apple Script to drive iTunes. It would be nice to > have a purely command-line option besides iTunes, if that's possible. For just a single batch, as I say, you just drag all your WAVs into iTunes, set up your settings once, then select all your WAVs and tell iTunes to convert them. It will do them all at once. But if you repeatedly want to convert batches of files, then you're right, a script is needed, and though AppleScript could work, a command-line utility might serve better. A popular mp3 encoder is "lame", for which a MacPorts port exists. I haven't used it myself, but maybe it will work for you. Looking through the output of "port search mp3" I also see "bladeenc" which might work too. From face at CentosPrime.COM Sat Jun 28 06:16:59 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sat, 28 Jun 2008 06:16:59 -0700 Subject: Recommendations for converting WAV to MP3? In-Reply-To: References: <7fccb3000806280133j5817a7caof913a28a40564d28@mail.gmail.com> <71F2D420-5023-4586-B716-24D4984D2405@macports.org> <7fccb3000806280227i1b45465i4d27199b249d42b6@mail.gmail.com> Message-ID: <4F33B1D3-2A94-4BE8-AFF5-8C81E1E1A33B@centosprime.com> On 2008-06-28 , at 02:33 , Ryan Schmidt wrote: > But if you repeatedly want to convert batches of files, then you're > right, a script is needed, and though AppleScript could work, a > command-line utility might serve better. A popular mp3 encoder is > "lame", for which a MacPorts port exists. I haven't used it myself, > but maybe it will work for you. Looking through the output of "port > search mp3" I also see "bladeenc" which might work too. Try this - sudo port install ffmpeg +lame +extvorbis +faac +faad +xvid +x264 Now you can translate like this ffmpeg -i ./imaprofessional.wav -y -acodec libmp3lame -ab 128k ./b.mp3 2&>/dev/null which says take the input file "imaprofessional.wav" overwrite output files (-y) use audio codec libmp3lame (-acodec) with an audio bitrate of 128K (-ab) with file ./b.mp3 as output - please put all of the chatter on stderr onto /dev/null 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From tabithamc at gmail.com Sat Jun 28 15:12:20 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Sat, 28 Jun 2008 12:12:20 -1000 Subject: Recommendations for converting WAV to MP3? In-Reply-To: <4F33B1D3-2A94-4BE8-AFF5-8C81E1E1A33B@centosprime.com> References: <7fccb3000806280133j5817a7caof913a28a40564d28@mail.gmail.com> <71F2D420-5023-4586-B716-24D4984D2405@macports.org> <7fccb3000806280227i1b45465i4d27199b249d42b6@mail.gmail.com> <4F33B1D3-2A94-4BE8-AFF5-8C81E1E1A33B@centosprime.com> Message-ID: <7fccb3000806281512h3e7ec1ebi7716306bac169aec@mail.gmail.com> On Sat, Jun 28, 2008 at 3:16 AM, Chris Janton wrote: > On 2008-06-28 , at 02:33 , Ryan Schmidt wrote: > > But if you repeatedly want to convert batches of files, then you're >> right, a script is needed, and though AppleScript could work, a >> command-line utility might serve better. A popular mp3 encoder is >> "lame", for which a MacPorts port exists. I haven't used it myself, >> but maybe it will work for you. Looking through the output of "port >> search mp3" I also see "bladeenc" which might work too. >> > > > Try this - > > sudo port install ffmpeg +lame +extvorbis +faac +faad +xvid +x264 > > Now you can translate like this > > ffmpeg -i ./imaprofessional.wav -y -acodec libmp3lame -ab 128k ./b.mp3 > 2&>/dev/null > > which says take the input file "imaprofessional.wav" overwrite output files > (-y) use audio codec libmp3lame (-acodec) with an audio bitrate of 128K > (-ab) with file ./b.mp3 as output - please put all of the chatter on stderr > onto /dev/null Chris, Thanks. I really like this approach. Nothing wrong with using iTunes also, but all power to open source and the command-line! Thanks, T.M. > > > > 8) > ---------------------------------- > Chris Janton - face at CentosPrime dot COM > Netminder for Opus1.COM > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080628/b7ec6ebe/attachment.html From alejandro.aragon at gmail.com Sun Jun 29 10:23:53 2008 From: alejandro.aragon at gmail.com (Alejandro Aragon) Date: Sun, 29 Jun 2008 12:23:53 -0500 Subject: gcc43 and openmp??? Message-ID: Hello everyone, Is there a chance that the macports provided gcc43 is not compiled with openmp support? I've been trying to run a very simple C++ program with openmp to see if I can take advantage of both cores. The program is as follows: #include #include using namespace std; int main() { cout<<"num processors -> "< "< g++-mp-4.3 -fopenmp openmp.cxx and run it, I see: $> ./a.out num processors -> 1 num threads -> 1 From bxf4 at u.washington.edu Sun Jun 29 12:44:07 2008 From: bxf4 at u.washington.edu (Brian Flaherty) Date: Sun, 29 Jun 2008 12:44:07 -0700 Subject: clam says boot.efi Broken.Executable Message-ID: <20080629194407.GA3157@lowry.local> Hello, I just happened to scan my /System/Library/CoreServices with clamdscan, and it came back and said that boot.efi was a broken executable. I'm running up to date Leopard & MacPorts. On this machine, clamdscan --version says: ClamAV 0.93.1/7583/Sat Jun 28 08:00:59 2008 I believe it too is up to date. To check, I logged into my office machine and scanned boot.efi there with clamdscan. It did not come up as Broken.Executable. port list shows the same version of clamav installed (@0.93.1), but on my office desktop clamdscan --version comes back as 0.93 not 0.93.1. clamscan --version comes back as 0.93.1 though, and the clamav binaries are the same size on both machines. In fact, boot.efi is the same size on both machines too. Anyone else see this? Any thoughts will be appreciated. Thank you for your time. Brian From bxf4 at u.washington.edu Sun Jun 29 12:50:14 2008 From: bxf4 at u.washington.edu (Brian Flaherty) Date: Sun, 29 Jun 2008 12:50:14 -0700 Subject: clam says boot.efi Broken.Executable In-Reply-To: <20080629194407.GA3157@lowry.local> References: <20080629194407.GA3157@lowry.local> Message-ID: <20080629195014.GA3256@lowry.local> On Sun, Jun 29, 2008 at 12:44:07PM -0700, Brian Flaherty wrote: > Hello, > > I just happened to scan my /System/Library/CoreServices with > clamdscan, and it came back and said that boot.efi was a broken > executable. I'm running up to date Leopard & MacPorts. On this > machine, clamdscan --version says: > > ClamAV 0.93.1/7583/Sat Jun 28 08:00:59 2008 > > I believe it too is up to date. > > To check, I logged into my office machine and scanned boot.efi there > with clamdscan. It did not come up as Broken.Executable. I also just checked to see if clamscan --detect-broken said boot.efi was a Broken.Executable and it did on both machines (laptop and desktop). Thank you again. From raimue at macports.org Sun Jun 29 14:19:43 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sun, 29 Jun 2008 23:19:43 +0200 Subject: clam says boot.efi Broken.Executable In-Reply-To: <20080629195014.GA3256@lowry.local> References: <20080629194407.GA3157@lowry.local> <20080629195014.GA3256@lowry.local> Message-ID: <4867FC6F.5000306@macports.org> Brian Flaherty wrote: > I also just checked to see if clamscan --detect-broken said boot.efi > was a Broken.Executable and it did on both machines (laptop and > desktop). I get the same: /System/Library/CoreServices/boot.efi: Broken.Executable FOUND But I think this question would be better targeted to the mailing list of the clamav project at . Rainer From bxf4 at u.washington.edu Sun Jun 29 14:43:24 2008 From: bxf4 at u.washington.edu (Brian Flaherty) Date: Sun, 29 Jun 2008 14:43:24 -0700 Subject: clam says boot.efi Broken.Executable In-Reply-To: <4867FC6F.5000306@macports.org> References: <20080629194407.GA3157@lowry.local> <20080629195014.GA3256@lowry.local> <4867FC6F.5000306@macports.org> Message-ID: <20080629214324.GA3677@lowry.local> On Sun, Jun 29, 2008 at 11:19:43PM +0200, Rainer M?ller wrote: > Brian Flaherty wrote: >> I also just checked to see if clamscan --detect-broken said boot.efi >> was a Broken.Executable and it did on both machines (laptop and >> desktop). > > I get the same: > /System/Library/CoreServices/boot.efi: Broken.Executable FOUND Thanks for the reply. Sorry you found the same thing. After looking into it more, I suspect it is a false alarm. I scanned boot.efi on a Debian linux machine with clamav and it came up as a broken executable there too. However, it also provided this message, which the MacPorts version did not: LibClamAV Warning: Incorrect magic number in optional header It sounds as though that message is referring to something called a PE (portable executable) file described here: http://win32assembly.online.fr/pe-tut1.html This is also what the --detect-broken option for clamscan is supposed to detect. It doesn't seem odd (to me) that a boot file would be structured differently than a standard executable. But it is still a little troubling the clamdscan doesn't give me the same answer on both my Macs. > But I think this question would be better targeted to the mailing list > of the clamav project at . I'll post something there too. Thanks again. From landonf at macports.org Sun Jun 29 18:50:47 2008 From: landonf at macports.org (Landon Fuller) Date: Sun, 29 Jun 2008 18:50:47 -0700 Subject: clam says boot.efi Broken.Executable In-Reply-To: <20080629214324.GA3677@lowry.local> References: <20080629194407.GA3157@lowry.local> <20080629195014.GA3256@lowry.local> <4867FC6F.5000306@macports.org> <20080629214324.GA3677@lowry.local> Message-ID: On Jun 29, 2008, at 2:43 PM, Brian Flaherty wrote: > This is also what the --detect-broken option for clamscan is supposed > to detect. It doesn't seem odd (to me) that a boot file would be > structured differently than a standard executable. "EFI uses a subset of the PE32+ image format with a modified header signature. The modification to signature value in the PE32+ image is done to distinguish EFI images from normal PE32 executables. The ?+? addition to PE32 provides the 64 bit relocation fix-up extensions to standard PE32 format. " Intel EFI Spec v1.02, Section 4.2, EFI Image Header: http://download.intel.com/technology/efi/docs/pdfs/EFISpec_v102.pdf Cheers, -landonf -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080629/3069c956/attachment.bin From ocroquette at free.fr Mon Jun 30 14:43:01 2008 From: ocroquette at free.fr (Olivier Croquette) Date: Mon, 30 Jun 2008 23:43:01 +0200 Subject: qt4-mac provides version 3? In-Reply-To: <286e6b7c0806231152s51ae449dk16452e2178363b25@mail.gmail.com> References: <286e6b7c0806231152s51ae449dk16452e2178363b25@mail.gmail.com> Message-ID: <48695365.1010309@free.fr> Dan Stowell wrote, On 23/06/08 20:52: > % which qmake > /opt/local/bin/qmake What shell are you using? Under bash, "which" won't take aliases and such into consideration. From tom at tacocat.net Mon Jun 30 16:49:46 2008 From: tom at tacocat.net (Tom Allison) Date: Mon, 30 Jun 2008 19:49:46 -0400 Subject: apache, postgresql, perl In-Reply-To: <992FDF24-283B-41C8-A0FA-A416BA4E6A58@geeklair.net> References: <4861AFA3.5070904@tacocat.net> <0470D764-B1B7-4FB3-B582-ABF6691D3D1D@macports.org> <4861E66A.1060804@tacocat.net> <5192A56B-5891-4FCE-B7C1-BA91568DB8D6@macports.org> <4861EBA0.9050606@tacocat.net> <992FDF24-283B-41C8-A0FA-A416BA4E6A58@geeklair.net> Message-ID: <4869711A.8010900@tacocat.net> Daniel J. Luke wrote: > On Jun 25, 2008, at 2:54 AM, Tom Allison wrote: >> Of course, as the result of this, right now I can't even get users to >> run any cgi (eg: /~tom/works.cgi) Something else is seriously wrong with this installation.... I stopped apache (apachectl stop) and the only change is that I get a message that I do not have permission to access /~tom/ -- not that the server is down. OK, I went on a hunt and uninstalled, then deleted, then kill -9 anything that looked like apache. Got that fixed. Now that I have a new installation, there's no http.conf file -- copy the sample one over and go from there? From tom at tacocat.net Mon Jun 30 17:13:41 2008 From: tom at tacocat.net (Tom Allison) Date: Mon, 30 Jun 2008 20:13:41 -0400 Subject: apache foul up Message-ID: <486976B5.5030306@tacocat.net> I'm getting more confused every 10 minutes with this apache installation. I installed apache2: sudo port installed | grep apache apache2 @2.2.9_1 (active) The manual says version 1.3 Error pages say 1.3.41. Prior to this, in uninstalled all the apache modules and deleted the /opt/local/apache2 directory and then installed apache2. Versions don't match up. I'm lost. These kinds of things aren't expected. So, first. How does mac ports install version 1.3 when someone has specified 2.2.9? Hacked website? Assuming that it's just a matter of someone not updating any of the documentation between the mac port for 1.3.41 and 2.2.9 then I've worked myself into another problem with this installation. ServerRoot "/opt/local/apache2" ErrorLog "logs/error_log" As for the httpd.conf I just copied the original/http.conf over to conf/httpd.conf and restarted apache. No logs. Even when I create an error (like page not found or others) I have no files, nothing for access_log or error_log. OK, I found that even after apachectl stop there are still processes running. So, after a killall I managed to get something working (found error_log and access_log). But the versions are still incorrect. From tom at tacocat.net Mon Jun 30 18:07:04 2008 From: tom at tacocat.net (Tom Allison) Date: Mon, 30 Jun 2008 21:07:04 -0400 Subject: Not a Fan of Cyrus-Sasl Message-ID: <48698338.30702@tacocat.net> I noticed that the last upgrade of subversion picked up cyrus-sasl on my macbook. I'm interested to know how I can lock ports to a specific version of subversion (or other software) so that I can avoid something like this? From landonf at macports.org Mon Jun 30 19:31:37 2008 From: landonf at macports.org (Landon Fuller) Date: Mon, 30 Jun 2008 19:31:37 -0700 Subject: Not a Fan of Cyrus-Sasl In-Reply-To: <48698338.30702@tacocat.net> References: <48698338.30702@tacocat.net> Message-ID: On Jun 30, 2008, at 6:07 PM, Tom Allison wrote: > I noticed that the last upgrade of subversion picked up cyrus-sasl > on my > macbook. > > I'm interested to know how I can lock ports to a specific version of > subversion (or other software) so that I can avoid something like > this? I'm curious -- why is this an issue in your environment? -landonf -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080630/5ce34bbf/attachment.bin From kykim_lists at mac.com Mon Jun 30 22:13:38 2008 From: kykim_lists at mac.com (kykim_lists at mac.com) Date: Tue, 01 Jul 2008 01:13:38 -0400 Subject: status of submitted portfile? Message-ID: <2E73B026-801F-4E1E-91A1-ADFA94A17A2E@mac.com> Hi, I submitted a portfile a few weeks back (ticket #15596) and haven't heard anything one way or another. Anyone know who I might contact about this? Thanks, -kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080701/b032078d/attachment.html From ryandesign at macports.org Mon Jun 30 23:59:17 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 1 Jul 2008 01:59:17 -0500 Subject: qt4-mac provides version 3? In-Reply-To: <286e6b7c0806302342x10a4656ey42be7ca0bdd1cee8@mail.gmail.com> References: <286e6b7c0806231152s51ae449dk16452e2178363b25@mail.gmail.com> <7757C9EA-9C4E-4609-9748-C617359ED81B@macports.org> <6C707229-1820-4AC3-B37E-A3DAB76592D1@macports.org> <286e6b7c0806302342x10a4656ey42be7ca0bdd1cee8@mail.gmail.com> Message-ID: <65CFBE6A-CA2C-492B-93E7-23BFB65EB73B@macports.org> On Jul 1, 2008, at 01:42, Dan Stowell wrote: > 2008/6/25 Ryan Schmidt: > >> On Jun 24, 2008, at 19:33, Ryan Schmidt wrote: >> >>> On Jun 23, 2008, at 13:52, Dan Stowell wrote: >>> >>>> I installed the "qt4-mac" port. Looks fine so far: >>>> >>>> % port installed | grep qt >>>> qt4-mac @4.4.0_3+dbus+docs (active) >>>> >>>> % which qmake >>>> /opt/local/bin/qmake >>>> >>>> % port provides `which qmake` >>>> /opt/local/bin/qmake is provided by: qt4-mac >>>> >>>> >>>> So how come I get this: >>>> >>>> % qmake --version >>>> Qmake version: 1.07a (Qt 3.3.7) >>>> >>>> ? I tried to compile something which requires qt 4, and got errors, >>>> hence I discovered this. I'm on PPC, Mac 10.4.11. [snip] >>> I don't have a problem with this on Mac OS X 10.4.11 Intel. >>> >>> >>> $ port installed qt4-mac >>> The following ports are currently installed: >>> qt4-mac @4.4.0_3+dbus+docs (active) >>> $ which qmake >>> /mp/bin/qmake >>> $ qmake --version >>> QMake version 2.01a >>> Using Qt version 4.4.0 in /mp/Library/Frameworks >>> $ >>> >>> >>> Maybe you have another qt manually installed? Maybe you have a shell >>> alias set up for "qmake" pointing somewhere else? ("which" doesn't >>> take shell aliases into account....) >> >> To offer another suggestion: You should try calling qmake by its >> absolute >> path, e.g.: >> >> /opt/local/bin/qmake --version >> >> Does that now show Qmake 2.01a / Qt 4.4.0? If so, then my shell >> alias hunch >> may be correct. You can type: >> >> alias >> >> to see all your defined aliases. > [snip] > If I call qmake using the absolute path then it states the > expected version, and also compiles my project correctly. > > I've just found this in my environment: QTDIR=/sw/lib/qt3 - this is > probably the culprit! Not sure exactly where this is getting set, but > it's clearly something to do with a fink install. Removing the > fink-installed qt3 will probably save me some disk space as well as > fixing the confusing behaviour. Glad you found the problem. As you see, Fink and MacPorts can interfere with another like this, which is why we don't recommend or support using both together. It can be done, but is tricky. We recommend you use and have installed only a single package manager. Of course we're biased towards MacPorts. If you're using Fink because it provides something that MacPorts does not, please let us know so we can consider adding it to MacPorts so you will no longer find Fink necessary.