From macports.users at gmail.com Fri Feb 1 09:42:06 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Sat Feb 2 15:14:47 2008 Subject: This version of Links does not contain SSL/TLS support Message-ID: Hi, I get this error when I try to load some pages. `This version of Links does not contain SSL/TLS support' However it reads `SSL support since version 0.94.' here: $ links -version Links 2.1pre28 Regards, From blb at macports.org Fri Feb 1 17:36:35 2008 From: blb at macports.org (Bryan Blackburn) Date: Sat Feb 2 15:14:48 2008 Subject: This version of Links does not contain SSL/TLS support In-Reply-To: References: Message-ID: <328C41C4-5201-4963-AF8B-BA13131AEA3C@macports.org> On Feb 1, 2008, at 10:42 AM, Charlse Darwin wrote: > Hi, > > I get this error when I try to load some pages. > `This version of Links does not contain SSL/TLS support' > How did you install links? You need to use the ssl variant: $ sudo port install links +ssl and that should build in support for SSL/TLS. Bryan > However it reads `SSL support since version 0.94.' here: > > > $ links -version > Links 2.1pre28 > > Regards, From ebgssth at gmail.com Fri Feb 1 21:45:06 2008 From: ebgssth at gmail.com (js) Date: Sat Feb 2 15:14:48 2008 Subject: [Proposal ] Name of Python's port Message-ID: Hi, port search python shows me that every python2.5 port has prefix "py25" but that of 2.4 is only "py". If MacPorts would consider python2.4 is recommended python (due to some known problem) and called python2.4 port just "python", that would make sense, but ,unfortunately, it's not so. So IMHO using py24 prefix for 2.4 port would be more intuitive. What do you think of this? I' like to hear some comments on this and as a long-term goal, it would be nice to have a portnaming guildeline for python (or ALl ports across MacPorts project) Thanks in advance! From ryandesign at macports.org Sat Feb 2 04:48:26 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 15:14:49 2008 Subject: Anyone have dcraw 8.81 installed? Message-ID: <01EF8893-4C61-4D9B-A60B-6E3A6D4F44CD@macports.org> Does anybody have the dcraw 8.81 port installed? If so, please email me; I would like to get the distfile from you. The distfile currently available from the dcraw web site does not match the one with which the portfile was made; see: http://trac.macosforge.org/projects/macports/ticket/13941 I would like to compare the current distfile with the old one, to make sure the differences are ok, as per reason 2 here: http://trac.macports.org/projects/macports/wiki/ FAQ#IgetError:checksummd5sha1rmd160mismatchforport.WhatcanIdoaboutit But I can't find the old distfile available for download anywhere, hence I need to ask you. From nox at macports.org Sat Feb 2 08:35:48 2008 From: nox at macports.org (N_Ox) Date: Sat Feb 2 15:14:49 2008 Subject: My Nano Is in French! In-Reply-To: <4BEC5961-1325-42AE-9E3F-255CBDA3C475@gmail.com> References: <4BEC5961-1325-42AE-9E3F-255CBDA3C475@gmail.com> Message-ID: <93310620-D3CA-4187-B976-59EEE23DB87B@macports.org> Le 2 f?vr. 08 ? 14:30, Charlse Darwin a ?crit : > Hi, > Nano is installed in French; how do I change it back to English? > > Regards, Your environment must say you're french. Check your environment to see if LANG or LC_ALL is set to something like fr_FR and reset it accordingly. Regards, -- Anthony Ramine, the "Ports tree cleaning Maestro". From face at CentosPrime.COM Sat Feb 2 08:41:27 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sat Feb 2 15:14:50 2008 Subject: Error in sqlite3 build - invalid command name "configure.awk" Message-ID: <7AEA72C8-F165-4728-AADF-451B738D05AC@CentosPrime.COM> PPC Mac OS X 10.3.9 server admin@x:admin:124 $ sudo port sync admin@x:admin:125 $ sudo port outdated The following installed ports are outdated: sqlite3 3.5.4_0 < 3.5.5_0 admin@x:admin:126 $ sudo port upgrade sqlite3 Error: Unable to open port: invalid command name "configure.awk" Unfortunately I can't see how it works on my 10.4 or 10.5 system - I think it will, but... mac-2 3 # sudo port upgrade sqlite3 ---> Fetching sqlite3 ---> Attempting to fetch sqlite-3.5.5.tar.gz from http:// www.sqlite.org/ ---> Attempting to fetch sqlite-3.5.5.tar.gz from http:// svn.macports.org/repository/macports/distfiles/sqlite3 ---> Attempting to fetch sqlite-3.5.5.tar.gz from http:// svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch sqlite-3.5.5.tar.gz from http:// svn.macports.org/repository/macports/downloads/sqlite3 Error: Target org.macports.fetch returned: fetch failed Error: Unable to upgrade port: 1 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From face at CentosPrime.COM Sat Feb 2 09:06:12 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sat Feb 2 15:14:50 2008 Subject: Error upgrading Apache2 Message-ID: <3BE99452-B436-43BF-8D8C-FF117E1C763D@CentosPrime.COM> This occurs on both 10.4 and 10.5 with macports version 1.6 or later. Same error on both systems. ---> Building apache2 with target all Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8" && make all " returned error 2 Command output: Making all in srclib Making all in os Making all in unix /opt/local/share/apr-1/build/libtool --silent --mode=compile /usr/bin/ gcc-4.0 -I/opt/local/include -O2 -DDARWIN - DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp -I/opt/local/include - I. -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/os/unix -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/server/mpm/prefork -I/opt/local/var/macports/ build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/modules/http -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/modules/filters -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/modules/proxy -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/include -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/modules/generators -I/opt/local/var/macports/ build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/modules/mappers -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/modules/database -I/opt/local/include/apr-1 -I/ opt/local/include -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/server -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/modules/proxy/../generators -I/opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/modules/ssl -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apa che2/work/httpd-2.2.8/modules/dav/main -prefer-non-pic -static -c unixd.c && touch unixd.lo libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' make[3]: *** [unixd.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 Error: Unable to upgrade port: 1 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From skip at pobox.com Sat Feb 2 10:53:53 2008 From: skip at pobox.com (skip@pobox.com) Date: Sat Feb 2 15:14:50 2008 Subject: Can the port command take advantage of multiple cores? Message-ID: <18340.48193.193025.467642@montanaro.dyndns.org> As the subject says, can I take advantage my my shiny new dual-core MacBook Pro? Something like "port install -j2"? Thx, -- Skip Montanaro - skip@pobox.com - http://www.webfast.com/~skip/ The major difference between Democrats and Republicans is that Republicans don't know that Randy Newman's lyrics are full of sarcasm. From jmpp at macports.org Sat Feb 2 12:25:06 2008 From: jmpp at macports.org (Juan Manuel Palacios) Date: Sat Feb 2 15:14:51 2008 Subject: bug for installing Macports? In-Reply-To: <20080129212546.GA10565@velsheda.lateralis.org> References: <25bab8360801272156x14642fe3waf97f333989ab425@mail.gmail.com> <25bab8360801280101oe1d29e3j1f8c991b4812058f@mail.gmail.com> <25bab8360801280105u17acef18h4eaa99aa382669ca@mail.gmail.com> <25bab8360801291230h2486ad44qe8a0d306296b6505@mail.gmail.com> <20080129212546.GA10565@velsheda.lateralis.org> Message-ID: > ' >> Even for the selfupdate I get error messages: >> >> $ sudo port selfupdate >> Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the >> ports tree: Synchronization the local ports tree failed doing rsync >> >> and fails. >> Providing us with more information through port(1)'s -d flag would be very helpful to diagnose the problem that's keeping you from syncing your ports tree. -jmpp From dersh at alum.mit.edu Sat Feb 2 14:19:42 2008 From: dersh at alum.mit.edu (Adam Dershowitz) Date: Sat Feb 2 15:14:51 2008 Subject: Endless Avahi system.log errors Message-ID: <4365E5A4-3101-4A3F-8ED8-D36B12EF9867@alum.mit.edu> I have Avahi port installed due to a dependency. I recently noticed that my system.log contains this repeated every 10 seconds: Feb 2 14:16:35 Macintosh org.freedesktop.avahi-dnsconfd[808]: connect(): No such file or directory Feb 2 14:16:35 Macintosh org.freedesktop.avahi-dnsconfd[808]: Failed to connect to the daemon. This probably means that you Feb 2 14:16:35 Macintosh org.freedesktop.avahi-dnsconfd[808]: didn't start avahi-daemon before avahi-dnsconfd. Feb 2 14:16:35 Macintosh com.apple.launchd[1] (org.freedesktop.avahi- dnsconfd[808]): Exited with exit code: 1 Feb 2 14:16:35 Macintosh com.apple.launchd[1] (org.freedesktop.avahi- dnsconfd): Throttling respawn: Will start in 10 seconds Feb 2 14:16:36 Macintosh org.freedesktop.avahi-daemon[809]: Found user 'avahi' (UID 502) and group 'avahi' (GID 502). Feb 2 14:16:36 Macintosh org.freedesktop.avahi-daemon[809]: Successfully dropped root privileges. Feb 2 14:16:36 Macintosh org.freedesktop.avahi-daemon[809]: avahi- daemon 0.6.22 starting up. Feb 2 14:16:36 Macintosh org.freedesktop.avahi-daemon[809]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Feb 2 14:16:36 Macintosh org.freedesktop.avahi-daemon[809]: dbus_bus_get_private(): Failed to connect to socket /opt/local/var/run/ dbus/system_bus_socket: No such file or directory Feb 2 14:16:36 Macintosh org.freedesktop.avahi-daemon[809]: WARNING: Failed to contact D-Bus daemon. Feb 2 14:16:36 Macintosh com.apple.launchd[1] (org.freedesktop.avahi- daemon[809]): Exited with exit code: 255 Feb 2 14:16:36 Macintosh com.apple.launchd[1] (org.freedesktop.avahi- daemon): Throttling respawn: Will start in 10 seconds I found this: http://lists.macosforge.org/pipermail/macports-users/2007-October/006496.html that seems to relate, but I am not sure why the stream of errors. Any suggestions about why and what to do about it? I am not even sure if this is really a macports issue or an avahi issue, but I figured that this is the right place to start. It looks like something is perhaps not installed or configured correctly? Thanks, --Adam From wsiegrist at apple.com Sat Feb 2 15:16:46 2008 From: wsiegrist at apple.com (William Siegrist) Date: Sat Feb 2 15:18:10 2008 Subject: macports-users has been fixed Message-ID: <8679795E-98A7-4B6A-9C52-4E2966C20D0A@apple.com> Sorry for the oversight, there was a mis-set permission on the server for macports-users. All the mail got deferred and has now been delivered. -Bill ---- William Siegrist Software Support Engineer Mac OS Forge http://macosforge.org/ wsiegrist@apple.com 408 862 7337 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2421 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080202/1cc2b02a/smime.bin From ryandesign at macports.org Sat Feb 2 15:18:33 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 15:18:30 2008 Subject: PostGIS - Installation in different Schema In-Reply-To: <2772C9B7-3033-49D5-9A98-C32D9BB4B9F1@grid.unep.ch> References: <2772C9B7-3033-49D5-9A98-C32D9BB4B9F1@grid.unep.ch> Message-ID: <3BDA3C8A-6D4F-4823-8D1D-EBFAB1173BC6@macports.org> On Jan 31, 2008, at 11:02, Stefan Schwarzer wrote: > I would like to know if somebody could tell me how I can - by using > the PostGIS MacPort - install the postgis functions not in the > schema "public", but in another schema (to separate it from the > tables which are being inserted into the public schema). I don't know the postgis software, so I don't even know what any of that means. You may want to ask the maintainer of the postgis port, the developers of postgis, or on a postgis mailing list or forum. From ryandesign at macports.org Sat Feb 2 15:24:35 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 15:24:33 2008 Subject: python/py-mysql In-Reply-To: References: Message-ID: <0C37202A-1124-4DFB-B507-E1620BE1DF53@macports.org> I can't really help you since I don't use python or leopard. I just wanted to say a few things: On Jan 31, 2008, at 09:29, Suresh Pillai wrote: > I was imprecise on python25 not installing. In fact, it was py25- > hashlib that failed to compile, a dependency for py25-mysql. I don't see any tickets open about py25-hashlib so you should show us the error you get when trying to build it, or file it in a ticket > I've also found with some googling that the py-mysql error can be > fixed on LEOPARD by commenting out from _mysql.c > > #ifndef uint > #define uint unsigned int > #endif > > Apologies if everyone already knew this. :) The py25-mysql portfile does indeed include a patchfile which does just that. It was added 2 months ago specifically to fix build issues on leopard: http://trac.macosforge.org/projects/macports/changeset/31502 This implies that it should work on leopard. > I've got things working with system python and downloads of mysql/ > mysql-python so I guess I'll stick it out while Leopard problems > with Macports python are being dealt with. > > Thanks, > Suresh > > On Thu, 31 Jan 2008, Suresh Pillai wrote: > >> I am running >> >> Macports 1.6 >> OS X 10.5 >> xcode 3.0 >> xquartz 2.1.3 >> >> python24 installs fine but gives me bus errors for the simplest of >> things like printing a list. Someone else mentioned this too back >> in Nov but I didnt see any responses to the thread. Also py-mysql >> won't compile (log not show since python itself is unstable). >> >> So I tried python25/py25-mysql and python25 won't even compile. >> >> I am new to OSX and Macports, but if I can't get python working ... >> >> Okay, so I thought I'd stick with the system python and downloaded >> the source for python-mysql from sourceforge. I got errors >> installing that too, although the errors were related to the >> macports install of mysql5: >> >> ... >> running build_ext >> building '_mysql' extension >> creating build/temp.macosx-10.5-i386-2.5 >> gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno- >> fused-madd -fno-common -dynamic -DNDEBUG -g -Os -Wall -Wstrict- >> prototypes -DMACOSX -I/usr/include/ffi -DENABLE_DTRACE -arch i386 - >> arch ppc -pipe -Dversion_info=(1,2,2,'final',0) - >> D__version__=1.2.2 -I/opt/local/include/mysql5/mysql -I/System/ >> Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 >> -c _mysql.c -o build/temp.macosx-10.5-i386-2.5/_mysql.o >> In file included from /opt/local/include/mysql5/mysql/mysql.h:47, >> from _mysql.c:40: >> /usr/include/sys/types.h:92: error: duplicate 'unsigned' >> /usr/include/sys/types.h:92: error: two or more data types in >> declaration specifiers >> In file included from /opt/local/include/mysql5/mysql/mysql.h:47, >> from _mysql.c:40: >> /usr/include/sys/types.h:92: error: duplicate 'unsigned' >> /usr/include/sys/types.h:92: error: two or more data types in >> declaration specifiers >> lipo: can't open input file: /var/folders/ZV/ZVl4o2PwHqaUrZYDYfN2CE >> +++TI/-Tmp-//ccXNdGDK.out (No such file or directory) >> error: command 'gcc' failed with exit status 1 >> >> >> Anyone got py-mysql/mysql-python working using the base Apple >> python? Otherwise I am reverting to linux. From ryandesign at macports.org Sat Feb 2 15:28:11 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 15:28:07 2008 Subject: libtool woes In-Reply-To: References: Message-ID: <4E2EFAA0-4AC4-4767-8EE9-B97286A8EE62@macports.org> "unable to infer tagged configuration" when trying to build apache2 is already filed: http://trac.macosforge.org/projects/macports/ticket/13653 Someone also filed it for mjpegtools: http://trac.macosforge.org/projects/macports/ticket/13648 Both tickets include lots of discussion. The apache2 ticket includes patches which someone said worked. Neither maintainer has responded to the tickets. Looks like it's time for someone else to commit the fixes. Probably not me, since I'm not experiencing the issue. On Jan 31, 2008, at 18:34, paul beard wrote: > Looks like I have some problem with libtool. libIDL and Apache2 > both fail to upgrade. > > ---> Building apache2 with target all > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8" && make all " returned error 2 > Command output: Making all in srclib > Making all in os > Making all in unix > /opt/local/share/apr-1/build/libtool --silent --mode=compile /usr/ > bin/gcc-4.0 -I/opt/local/include -O2 -DDARWIN - > DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp -I/opt/local/ > include -I. -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/os/unix -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/server/mpm/prefork -I/opt/local/var/ > macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/http -I/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/filters -I/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/proxy -I/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/include -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/generators -I/opt/local/var/ > macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/mappers -I/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/database -I/opt/local/include/apr-1 > -I/opt/local/include -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/server -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/proxy/../generators -I/opt/local/ > var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/ssl -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/dav/main -prefer-non-pic -static - > c unixd.c && touch unixd.lo > libtool: compile: unable to infer tagged configuration > libtool: compile: specify a tag with `--tag' > make[3]: *** [unixd.lo] Error 1 > make[2]: *** [all-recursive] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all-recursive] Error 1 From ryandesign at macports.org Sat Feb 2 15:28:57 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 15:28:50 2008 Subject: Error upgrading Apache2 In-Reply-To: <3BE99452-B436-43BF-8D8C-FF117E1C763D@CentosPrime.COM> References: <3BE99452-B436-43BF-8D8C-FF117E1C763D@CentosPrime.COM> Message-ID: <54AD9D13-2F55-43AD-919F-0FD177A99DE4@macports.org> See my response just now to Paul Beard about the same problem: http://lists.macosforge.org/pipermail/macports-users/2008-February/ 008651.html On Feb 2, 2008, at 11:06, Chris Janton wrote: > This occurs on both 10.4 and 10.5 with macports version 1.6 or later. > Same error on both systems. > > ---> Building apache2 with target all > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8" && make all " returned error 2 > Command output: Making all in srclib > Making all in os > Making all in unix > /opt/local/share/apr-1/build/libtool --silent --mode=compile /usr/ > bin/gcc-4.0 -I/opt/local/include -O2 -DDARWIN - > DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp -I/opt/local/ > include -I. -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/os/unix -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/server/mpm/prefork -I/opt/local/var/ > macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/http -I/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/filters -I/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/proxy -I/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/include -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/generators -I/opt/local/var/ > macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/mappers -I/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/database -I/opt/local/include/apr-1 > -I/opt/local/include -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/server -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/proxy/../generators -I/opt/local/ > var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/ssl -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_a > pache2/work/httpd-2.2.8/modules/dav/main -prefer-non-pic -static - > c unixd.c && touch unixd.lo > libtool: compile: unable to infer tagged configuration > libtool: compile: specify a tag with `--tag' > make[3]: *** [unixd.lo] Error 1 > make[2]: *** [all-recursive] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all-recursive] Error 1 From ryandesign at macports.org Sat Feb 2 15:31:29 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 15:31:27 2008 Subject: Installing PHP5: "Error, SSL/TLS libraries were missing or unusable" In-Reply-To: <2EAD27D1-5D4F-4962-BCD3-E7825471F2C3@grid.unep.ch> References: <2EAD27D1-5D4F-4962-BCD3-E7825471F2C3@grid.unep.ch> Message-ID: <87D8BCD9-13CF-4BCC-9A57-B1FA5D428677@macports.org> On Jan 30, 2008, at 02:28, Stefan Schwarzer wrote: > I did a successful install like this: > > sudo port install php5 +apache2 +mysql5 +server The php5 port does not have a +server variant. If you were trying to get a mysql5 server out of this, then you need to do two separate commands: sudo port install mysql5 +server sudo port install php5 +apache2 +mysql5 > Now, I discovered that php5 wasn't configured with postgres, that's > why I wanted to repeat the process, this time using the postgres > variant. > > So, I did an uninstall and clean of php5, mysql5 and apache2, and > entered this: > > sudo port install php5 +postgresql +pear +universal +macosx > +apache2 +mysql5 +server You don't need to specify +macosx; MacPorts automatically selects this variant if you are running on Mac OS X. Most people don't need +universal. Do you really need to run this software on both a PowerPC and an Intel Mac? If not, don't use +universal. If you do use +universal, then you must make sure that you have already compiled all dependencies with +universal too. > But then I received the following error message: > > > checking for openssl/ssl.h... yes > OK > checking openssl/engine.h usability... yes > checking openssl/engine.h presence... yes > checking for openssl/engine.h... yes > checking for SSLeay_version in -lcrypto... no > checking for SSL_CTX_new in -lssl... no > checking for ENGINE_init... no > checking for ENGINE_load_builtin_engines... no > checking for SSL_set_cert_store... no > configure: error: ... Error, SSL/TLS libraries were missing or > unusable > > Error: The following dependencies failed to build: apache2 > Error: Status 1 encountered during processing. > > > What does that mean? What can I do? From ryandesign at macports.org Sat Feb 2 15:35:10 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 15:35:08 2008 Subject: myodbc 5.1.1? In-Reply-To: <6106438e0801301443v565c6381ud4957dea1fe88673@mail.gmail.com> References: <6106438e0801301443v565c6381ud4957dea1fe88673@mail.gmail.com> Message-ID: <8463FD8C-F325-41BC-B20C-6CEC5DEECEA7@macports.org> On Jan 30, 2008, at 16:43, Justin Fagnani wrote: > Is there any chance that a portfile for the MySQL odbc 5.1.1 > drivers are coming soon? I don't see any ticket filed on that, so I'd guess not. You could file a ticket requesting such an update. Be sure to Cc the maintainer of the port. You could also send an email to the port and ask them what's up. > I tried getting it to compile and work with the macports mysql5, > but found it quicker to just pay for some commercial drivers for > the moment. The only problem with the MySQL provided binaries is > that they're looking for the sock file in the wrong place. If I > knew anything about authoring a portfile I'd try... You can learn about writing portfiles by reading the guide: http://guide.macports.org/ And by looking at existing portfiles. From ryandesign at macports.org Sat Feb 2 15:37:24 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 15:37:22 2008 Subject: libgnomeprint patch fetch fails In-Reply-To: References: Message-ID: This was fixed: http://trac.macosforge.org/projects/macports/changeset/33577 On Jan 30, 2008, at 08:06, William Davis wrote: > ---> Fetching libgnomeprint > DEBUG: Executing org.macports.fetch (libgnomeprint) > ---> patch-configure.diff doesn't seem to exist in /opt/local/var/ > macports/distfiles/libgnomeprint > ---> Attempting to fetch patch-configure.diff from http:// > svn.macports.org/repository/macports/distfiles/libgnomeprint > % Total % Received % Xferd Average Speed Time Time > Time Current > Dload Upload Total Spent > Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- > --:--:-- 0 > DEBUG: Fetching failed:: HTTP response code said error [snip] From ryandesign at macports.org Sat Feb 2 15:38:00 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 15:37:53 2008 Subject: myodbc 5.1.1? In-Reply-To: <8463FD8C-F325-41BC-B20C-6CEC5DEECEA7@macports.org> References: <6106438e0801301443v565c6381ud4957dea1fe88673@mail.gmail.com> <8463FD8C-F325-41BC-B20C-6CEC5DEECEA7@macports.org> Message-ID: <13916CDE-3C06-4819-A6F8-062B1B7E470F@macports.org> On Feb 2, 2008, at 17:35, Ryan Schmidt wrote: > On Jan 30, 2008, at 16:43, Justin Fagnani wrote: > >> Is there any chance that a portfile for the MySQL odbc 5.1.1 >> drivers are coming soon? > > I don't see any ticket filed on that, so I'd guess not. You could > file a ticket requesting such an update. Be sure to Cc the > maintainer of the port. You could also send an email to the port > and ask them what's up. Whoops, I meant: send an email to the port *maintainer* to ask them what's up. From ryandesign at macports.org Sat Feb 2 15:41:02 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 15:40:56 2008 Subject: [Proposal ] Name of Python's port In-Reply-To: References: Message-ID: <090129C0-391A-4987-8D03-6CC79BC46026@macports.org> On Feb 1, 2008, at 23:45, js wrote: > port search python shows me that every python2.5 port has prefix > "py25" but that of 2.4 is only "py". > If MacPorts would consider python2.4 is recommended python (due to > some known problem) > and called python2.4 port just "python", that would make sense, but > ,unfortunately, it's not so. > So IMHO using py24 prefix for 2.4 port would be more intuitive. > > What do you think of this? > I' like to hear some comments on this and > as a long-term goal, it would be nice to have a portnaming guildeline > for python (or ALl ports across MacPorts project) The guideline is: use a numbered prefix if there's a good reason to. A prefix was not used for the python 2.4 ports because there was no python 2.5 at the time. Now there is, and I think it was just deemed too much of a hassle to rename all the py-* ports to py24-*. From ryandesign at macports.org Sat Feb 2 15:45:35 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 15:45:35 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <18340.48193.193025.467642@montanaro.dyndns.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> Message-ID: <5349F935-4F33-4535-9E08-2697ADC2B1B5@macports.org> On Feb 2, 2008, at 12:53, skip@pobox.com wrote: > As the subject says, can I take advantage my my shiny new dual-core > MacBook > Pro? Something like "port install -j2"? Not exactly. Not all software supports parallel building. Each port must be tested to ensure that it works. As ports are tested, "use_parallel_build yes" is added to the portfile. Then MacPorts will build those ports using -j$jobs (where $jobs is the number of CPU cores in your computer). This was added for MacPorts 1.6. From ryandesign at macports.org Sat Feb 2 15:52:27 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 15:52:23 2008 Subject: Cannot install gimp-app (libgnomeprint fetch problem) In-Reply-To: References: Message-ID: This problem was fixed: http://trac.macosforge.org/projects/macports/changeset/33577 "sudo port selfupdate" and try again. On Jan 30, 2008, at 02:55, Juraj Kubelka wrote: > Hi All! > > May I ask for help? I'm trying to install gimp-app package and it > ends up with error. > Is there a way how can I solve it? > > Thank you in advance. > Jura > > > ############## log: ############## > sudo port install gimp-app > Skipping org.macports.activate (aalib ) since this port is already > active > ---> Cleaning aalib > Skipping org.macports.activate (curl ) since this port is already > active > ---> Cleaning curl > ..... > ---> Fetching libgnomeprint > ---> Attempting to fetch patch-configure.diff from http:// > svn.macports.org/repository/macports/distfiles/libgnomeprint > ---> Attempting to fetch patch-configure.diff from http:// > svn.macports.org/repository/macports/distfiles/general/ > ---> Attempting to fetch patch-configure.diff from http:// > svn.macports.org/repository/macports/downloads/libgnomeprint > Error: Target org.macports.fetch returned: fetch failed > Error: The following dependencies failed to build: gimp2 librsvg > libgnomeprint libgsf libwmf poppler poppler-data > Error: Status 1 encountered during processing. > > > ############## debug mode: ############## > ---> Fetching libgnomeprint > DEBUG: Executing org.macports.fetch (libgnomeprint) > ---> patch-configure.diff doesn't seem to exist in /opt/local/var/ > macports/distfiles/libgnomeprint > ---> Attempting to fetch patch-configure.diff from http:// > svn.macports.org/repository/macports/distfiles/libgnomeprint > % Total % Received % Xferd Average Speed Time Time > Time Current > Dload Upload Total Spent > Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- > --:--:-- 0 > DEBUG: Fetching failed:: HTTP response code said error [snip] From yves at macports.org Sat Feb 2 15:53:56 2008 From: yves at macports.org (Yves de Champlain) Date: Sat Feb 2 15:53:44 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <18340.48193.193025.467642@montanaro.dyndns.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> Message-ID: <812289A8-6554-4B53-AAE4-0A00D928E3DB@macports.org> Le 08-02-02 ? 13:53, skip@pobox.com a ?crit : > As the subject says, can I take advantage my my shiny new dual-core > MacBook > Pro? Something like "port install -j2"? The answer is yes and no ... $prefix/etc/macports/macports.conf lets you specify a -j arg. However, macports will not use it unless the Portfile says it'S OK to do so with each specific port. Now, very few (almost none) Portfiles have this flag defined. It's just too bad because most ports will build fine with -j > 1 (I have tried over 150 ports with -j 8 and 5 have failed because of that, mostly in the destroot phase). yves From ram at macports.org Sat Feb 2 15:59:50 2008 From: ram at macports.org (Adam Mercer) Date: Sat Feb 2 15:59:36 2008 Subject: how to reconfigure f2py In-Reply-To: <877766.27745.qm@web60421.mail.yahoo.com> References: <193244.47362.qm@web60414.mail.yahoo.com> <877766.27745.qm@web60421.mail.yahoo.com> Message-ID: <799406d60802021559l3321879aodb202d1f7ff6ea4a@mail.gmail.com> On Jan 30, 2008 5:13 PM, Dexter Douglas wrote: > Then I modified the linker flags. > In > /opt/local/lib/python2.5/site-packages/numpy/distutils/fcompiler/g95.py > > I changed line 24 from > 'linker_so' : ["","-static"], > to > 'linker_so' : ["","-dynamiclib > -L/opt/local/lib -lpython2.5"], This has been incorporated into py-numpy/py25-numpy version 1.0.4_6, can you update to that version and check that f2py still works with g95? Cheers Adam From ebgssth at gmail.com Sat Feb 2 16:15:41 2008 From: ebgssth at gmail.com (js) Date: Sat Feb 2 16:15:27 2008 Subject: [Proposal ] Name of Python's port In-Reply-To: <090129C0-391A-4987-8D03-6CC79BC46026@macports.org> References: <090129C0-391A-4987-8D03-6CC79BC46026@macports.org> Message-ID: So, now that we have py25-* and even py30-* ports, let's do something about it. Renaming py-* t- py24-*. could be done in a simple perl regex like this $ find dports \! -path '*.svn*' -type f -print0 | xargs -0 perl -i -pe 's/py-/py24-/g' It might be better to leave py-* ports without any changes for a while to avoid confusion. Any comments? On Feb 3, 2008 8:41 AM, Ryan Schmidt wrote: > > On Feb 1, 2008, at 23:45, js wrote: > > > port search python shows me that every python2.5 port has prefix > > "py25" but that of 2.4 is only "py". > > If MacPorts would consider python2.4 is recommended python (due to > > some known problem) > > and called python2.4 port just "python", that would make sense, but > > ,unfortunately, it's not so. > > So IMHO using py24 prefix for 2.4 port would be more intuitive. > > > > What do you think of this? > > I' like to hear some comments on this and > > as a long-term goal, it would be nice to have a portnaming guildeline > > for python (or ALl ports across MacPorts project) > > The guideline is: use a numbered prefix if there's a good reason to. > A prefix was not used for the python 2.4 ports because there was no > python 2.5 at the time. Now there is, and I think it was just deemed > too much of a hassle to rename all the py-* ports to py24-*. > > From raimue at macports.org Sat Feb 2 16:37:32 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sat Feb 2 16:37:20 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <812289A8-6554-4B53-AAE4-0A00D928E3DB@macports.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> <812289A8-6554-4B53-AAE4-0A00D928E3DB@macports.org> Message-ID: <47A50CCC.3040406@macports.org> Yves de Champlain wrote: > However, macports will not use it unless the Portfile says it'S OK to do > so with each specific port. Now, very few (almost none) Portfiles have > this flag defined. It's just too bad because most ports will build fine > with -j > 1 (I have tried over 150 ports with -j 8 and 5 have failed > because of that, mostly in the destroot phase). Why is this opt-in and not opt-out? We could add a flag to ports that they should be built with -j1 instead of what was specified in macports.conf. Is there a reason or some problem I don't know of? Rainer From face at CentosPrime.COM Sat Feb 2 17:01:10 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sat Feb 2 17:01:34 2008 Subject: Error upgrading Apache2 In-Reply-To: <54AD9D13-2F55-43AD-919F-0FD177A99DE4@macports.org> References: <3BE99452-B436-43BF-8D8C-FF117E1C763D@CentosPrime.COM> <54AD9D13-2F55-43AD-919F-0FD177A99DE4@macports.org> Message-ID: <1240AAE3-10AC-4A58-9951-4D91FD9909E7@CentosPrime.COM> On 2008-02-02 , at 16:28 , Ryan Schmidt wrote: > See my response just now to Paul Beard about the same problem: > > http://lists.macosforge.org/pipermail/macports-users/2008-February/ > 008651.html unfortunately I have looked at the response, looked at the 2 different places where the error is, and, I really have no idea what it is, exactly, that I am supposed to do to fix the problem. 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From ryandesign at macports.org Sat Feb 2 17:09:46 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 17:09:43 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <47A50CCC.3040406@macports.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> <812289A8-6554-4B53-AAE4-0A00D928E3DB@macports.org> <47A50CCC.3040406@macports.org> Message-ID: <7F910A9F-AF90-4B5D-A03F-E38E6FC54E6F@macports.org> On Feb 2, 2008, at 18:37, Rainer M?ller wrote: > Yves de Champlain wrote: > >> However, macports will not use it unless the Portfile says it'S OK >> to do so with each specific port. Now, very few (almost none) >> Portfiles have this flag defined. It's just too bad because most >> ports will build fine with -j > 1 (I have tried over 150 ports >> with -j 8 and 5 have failed because of that, mostly in the >> destroot phase). > > Why is this opt-in and not opt-out? We could add a flag to ports that > they should be built with -j1 instead of what was specified in > macports.conf. Is there a reason or some problem I don't know of? Changes in base should not break existing ports, if at all possible. Ports may fail with this option enabled. Therefore it's opt-in on a port-by-port basis. From raimue at macports.org Sat Feb 2 17:25:11 2008 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sat Feb 2 17:24:58 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <7F910A9F-AF90-4B5D-A03F-E38E6FC54E6F@macports.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> <812289A8-6554-4B53-AAE4-0A00D928E3DB@macports.org> <47A50CCC.3040406@macports.org> <7F910A9F-AF90-4B5D-A03F-E38E6FC54E6F@macports.org> Message-ID: <47A517F7.1050104@macports.org> Ryan Schmidt wrote: > Changes in base should not break existing ports, if at all possible. > Ports may fail with this option enabled. Therefore it's opt-in on a > port-by-port basis. So every maintainer has to check for himself if his/her ports built fine with parallel building enabled? With this approach it will last a long time until we get real benefits of parallel building. Although many users already own multi-core Macs and want to have faster builds... I don't think that many ports will break with this. As Yves said, 5 out of 150 failed for him. Tagging 5 ports is easier than tagging 150. And it would be not a real problem if a port fails, there is always the workaround to disable this option in macports.conf again until the Portfile for a failing port is modified accordingly. Rainer From ryandesign at macports.org Sat Feb 2 17:56:10 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat Feb 2 17:56:07 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <47A517F7.1050104@macports.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> <812289A8-6554-4B53-AAE4-0A00D928E3DB@macports.org> <47A50CCC.3040406@macports.org> <7F910A9F-AF90-4B5D-A03F-E38E6FC54E6F@macports.org> <47A517F7.1050104@macports.org> Message-ID: <16C308C5-FA78-453F-8EE9-AB4B8DC6CA0B@macports.org> On Feb 2, 2008, at 19:25, Rainer M?ller wrote: > Ryan Schmidt wrote: > >> Changes in base should not break existing ports, if at all >> possible. Ports may fail with this option enabled. Therefore it's >> opt-in on a port-by-port basis. > > So every maintainer has to check for himself if his/her ports built > fine with parallel building enabled? With this approach it will > last a long time until we get real benefits of parallel building. > Although many users already own multi-core Macs and want to have > faster builds... > > I don't think that many ports will break with this. As Yves said, 5 > out of 150 failed for him. Tagging 5 ports is easier than tagging 150. > And it would be not a real problem if a port fails, there is always > the workaround to disable this option in macports.conf again until > the Portfile for a failing port is modified accordingly. There was a long thread on this topic leading up to the current implementation; please review: http://lists.macosforge.org/pipermail/macports-users/2007-October/ 006479.html In particular Markus's comment here seems to exemplify why it's the way it is: http://lists.macosforge.org/pipermail/macports-users/2007-October/ 006601.html "The point is that ports that are not given 110% love (e.g. unmaintained ones, busy maintainers) will simply break [if parallel builds are enabled by default] probably in spectacular non- deterministic ways." We have enough other problems with ports right now. Let's not make more, especially spectacular non-deterministic ones, by enabling parallel builds by default. From ebgssth at gmail.com Sat Feb 2 19:54:48 2008 From: ebgssth at gmail.com (js) Date: Sat Feb 2 19:54:34 2008 Subject: [Proposal ] Name of Python's port In-Reply-To: References: <090129C0-391A-4987-8D03-6CC79BC46026@macports.org> Message-ID: > A mass renaming of ports would basically cause massive failures during > upgrades (why can't any of my port dependencies activate during upgrade?) > unless every single py-* port was DUPLICATED as a py24-* port and then made > a non-installing dependent of the py24-* port (look in the SVN history of > port abiword to see how we migrated multiple ports to ports with different > names) > I would leave existing python 2.4 ports alone for historical reasons, but > use py[version]-* for all new ports. You're right. So I would like to leave py-* ports *for a while* and treat them as deprecated ports, and user who installed deprecated ports would be warned by warnings like "py- ports is DEPRECATED, which means no update is made in this port. Please install py24-* instead. You're warned!" Luckily, python24 is a bit old (The current stable is 2.5) so I hope this would not impact so many users. From skip at pobox.com Sat Feb 2 16:06:21 2008 From: skip at pobox.com (skip@pobox.com) Date: Sat Feb 2 20:30:47 2008 Subject: [Proposal ] Name of Python's port In-Reply-To: References: Message-ID: <18341.1405.824927.368907@montanaro.dyndns.org> js> So IMHO using py24 prefix for 2.4 port would be more intuitive. js> What do you think of this? +1. In fact, with Python 2.6 and 3.0 on the way I suspect it would be best to add version numbers to all versions of Python for awhile. -- Skip Montanaro - skip@pobox.com - http://www.webfast.com/~skip/ The major difference between Democrats and Republicans is that Republicans don't know that Randy Newman's lyrics are full of sarcasm. From skip at pobox.com Sat Feb 2 16:08:51 2008 From: skip at pobox.com (skip@pobox.com) Date: Sat Feb 2 20:30:50 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <5349F935-4F33-4535-9E08-2697ADC2B1B5@macports.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> <5349F935-4F33-4535-9E08-2697ADC2B1B5@macports.org> Message-ID: <18341.1555.367461.148039@montanaro.dyndns.org> Ryan> As ports are tested, "use_parallel_build yes" is added to the Ryan> portfile. Then MacPorts will build those ports using -j$jobs Ryan> (where $jobs is the number of CPU cores in your computer). This Ryan> was added for MacPorts 1.6. Excellent, thanks. That makes it transparent even. ;-) Skip From afb at macports.org Sun Feb 3 01:32:49 2008 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun Feb 3 01:32:36 2008 Subject: libtool woes In-Reply-To: References: Message-ID: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> paul beard wrote: > Looks like I have some problem with libtool. > libIDL and Apache2 both fail to upgrade.? ... > libtool: compile: unable to infer tagged configuration > libtool: compile: specify a tag with `--tag' This problem is since the change to "/usr/bin/gcc-4.0" for CC. Switching compiler back to "gcc" (or "gcc-4.0") makes it work. Something like: port build configure.cc=gcc configure.cxx=g++ We also have some ports that break when using ccache(*), those can be made to work by using configure.ccache=no when building. * http://ccache.samba.org/ --anders From afb at macports.org Sun Feb 3 02:19:34 2008 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun Feb 3 02:19:20 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <47A517F7.1050104@macports.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> <812289A8-6554-4B53-AAE4-0A00D928E3DB@macports.org> <47A50CCC.3040406@macports.org> <7F910A9F-AF90-4B5D-A03F-E38E6FC54E6F@macports.org> <47A517F7.1050104@macports.org> Message-ID: Rainer M?ller wrote: > And it would be not a real problem if a port fails, there is always > the workaround to disable this option in macports.conf again until the > Portfile for a failing port is modified accordingly. You can also disable it at runtime, by giving the argument build.jobs=1 --anders From afb at macports.org Sun Feb 3 02:50:18 2008 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun Feb 3 02:50:19 2008 Subject: [Proposal ] Name of Python's port In-Reply-To: <090129C0-391A-4987-8D03-6CC79BC46026@macports.org> References: <090129C0-391A-4987-8D03-6CC79BC46026@macports.org> Message-ID: <8383950e0e5ea2c46ea96acde77288a4@macports.org> Ryan Schmidt wrote: >> What do you think of this? >> I' like to hear some comments on this and >> as a long-term goal, it would be nice to have a portnaming guildeline >> for python (or ALl ports across MacPorts project) > > The guideline is: use a numbered prefix if there's a good reason to. A > prefix was not used for the python 2.4 ports because there was no > python 2.5 at the time. Now there is, and I think it was just deemed > too much of a hassle to rename all the py-* ports to py24-*. Fixing the current issues for the python25 port, or with MacPorts having /usr/bin/python as default, would be better than just renaming a lot of deprecated ports... For instance all ports using py-gtk2 was already forced to upgrade to using py25-gtk instead... ? --anders From ryandesign at macports.org Sun Feb 3 08:01:59 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Feb 3 08:01:56 2008 Subject: libtool woes In-Reply-To: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> References: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> Message-ID: <0467D51C-AA42-4A82-A555-F05CFF7876E5@macports.org> On Feb 3, 2008, at 03:32, Anders F Bj?rklund wrote: > paul beard wrote: > >> Looks like I have some problem with libtool. >> libIDL and Apache2 both fail to upgrade. > ... >> libtool: compile: unable to infer tagged configuration >> libtool: compile: specify a tag with `--tag' > > This problem is since the change to "/usr/bin/gcc-4.0" for CC. > Switching compiler back to "gcc" (or "gcc-4.0") makes it work. > > Something like: port build configure.cc=gcc configure.cxx=g++ Can you explain more? Isn't "gcc" the same as "/usr/bin/gcc" which is a symlink to "/usr/bin/gcc-4.0"? Also, I do not experience this problem with apache2; why would some people see it and not others? > We also have some ports that break when using ccache(*), those > can be made to work by using configure.ccache=no when building. > > * http://ccache.samba.org/ From ryandesign at macports.org Sun Feb 3 08:03:01 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Feb 3 08:02:59 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <18341.1555.367461.148039@montanaro.dyndns.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> <5349F935-4F33-4535-9E08-2697ADC2B1B5@macports.org> <18341.1555.367461.148039@montanaro.dyndns.org> Message-ID: <12EE9B11-547C-4B56-B117-87C0F3C2CA7F@macports.org> On Feb 2, 2008, at 18:08, skip@pobox.com wrote: > > Ryan> As ports are tested, "use_parallel_build yes" is added to > the > Ryan> portfile. Then MacPorts will build those ports using -j$jobs > Ryan> (where $jobs is the number of CPU cores in your > computer). This > Ryan> was added for MacPorts 1.6. > > Excellent, thanks. That makes it transparent even. ;-) Well, that's what I thought happened. But now others are saying there's an option in macports.conf that needs to be set. Can someone please clarify? Is there an option, and if so, what does it need to be set to? From ryandesign at macports.org Sun Feb 3 08:10:54 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Feb 3 08:10:55 2008 Subject: [Proposal ] Name of Python's port In-Reply-To: <18341.1405.824927.368907@montanaro.dyndns.org> References: <18341.1405.824927.368907@montanaro.dyndns.org> Message-ID: <66472C4C-2963-40B3-BF67-E06E46719857@macports.org> On Feb 2, 2008, at 18:06, skip@pobox.com wrote: > js> So IMHO using py24 prefix for 2.4 port would be more > intuitive. > > js> What do you think of this? > > +1. In fact, with Python 2.6 and 3.0 on the way I suspect it would > be best > to add version numbers to all versions of Python for awhile. It has already been established that python 2.5 ports shall have the py25 prefix and python 3.0 ports shall have the py30 prefix. If there's a python 2.6 version coming, then these should use the py26 prefix. Python 2.4 ports use the py prefix because we had not established the rules at that time and it is a major hassle to change this now. There are a handful of ports that depend on python 2.3, but none of them are in the python category, so none of them have a py prefix. There are ports for python 2.2 and python 2.1 but I don't see any ports that depend on those. From james.sumners at gmail.com Sun Feb 3 08:17:15 2008 From: james.sumners at gmail.com (James Sumners) Date: Sun Feb 3 08:17:08 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <12EE9B11-547C-4B56-B117-87C0F3C2CA7F@macports.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> <5349F935-4F33-4535-9E08-2697ADC2B1B5@macports.org> <18341.1555.367461.148039@montanaro.dyndns.org> <12EE9B11-547C-4B56-B117-87C0F3C2CA7F@macports.org> Message-ID: It looks to me like all you have to do is set "buildmakejobs" to the number of jobs you want make to use. I assume port will then use that many jobs when a portfile allows it. On Feb 3, 2008 11:03 AM, Ryan Schmidt wrote: > > On Feb 2, 2008, at 18:08, skip@pobox.com wrote: > > > > > Ryan> As ports are tested, "use_parallel_build yes" is added to > > the > > Ryan> portfile. Then MacPorts will build those ports using -j$jobs > > Ryan> (where $jobs is the number of CPU cores in your > > computer). This > > Ryan> was added for MacPorts 1.6. > > > > Excellent, thanks. That makes it transparent even. ;-) > > > Well, that's what I thought happened. But now others are saying > there's an option in macports.conf that needs to be set. Can someone > please clarify? Is there an option, and if so, what does it need to > be set to? -- James Sumners http://james.roomfullofmirrors.com/ "All governments suffer a recurring problem: Power attracts pathological personalities. It is not that power corrupts but that it is magnetic to the corruptible. Such people have a tendency to become drunk on violence, a condition to which they are quickly addicted." Missionaria Protectiva, Text QIV (decto) CH:D 59 From afb at macports.org Sun Feb 3 08:22:01 2008 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun Feb 3 08:21:46 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <12EE9B11-547C-4B56-B117-87C0F3C2CA7F@macports.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> <5349F935-4F33-4535-9E08-2697ADC2B1B5@macports.org> <18341.1555.367461.148039@montanaro.dyndns.org> <12EE9B11-547C-4B56-B117-87C0F3C2CA7F@macports.org> Message-ID: <498b81762b0022440f3702eada0abc9a@macports.org> Ryan Schmidt wrote: >> Ryan> As ports are tested, "use_parallel_build yes" is added to >> the >> Ryan> portfile. Then MacPorts will build those ports using -j$jobs >> Ryan> (where $jobs is the number of CPU cores in your computer). >> This >> Ryan> was added for MacPorts 1.6. >> >> Excellent, thanks. That makes it transparent even. ;-) > > Well, that's what I thought happened. But now others are saying > there's an option in macports.conf that needs to be set. Can someone > please clarify? Is there an option, and if so, what does it need to be > set to? There is a config parameter in macports.conf called "buildmakejobs", that controls the default value for build.jobs (default config is 1) However, this was considered dangerous so the Portfile opt-in setting of "use_parallel_build" was added - with a default setting of no. So in order to get MacPorts to use -j2 or more, you need to both set your local preference and then also each Portfile to opt-in... Opt-in was added in http://trac.macports.org/projects/macports/changeset/30714 before that it assumed opt-out -(by using "build.jobs 1") instead. --anders From skip at pobox.com Sun Feb 3 08:26:11 2008 From: skip at pobox.com (skip@pobox.com) Date: Sun Feb 3 08:25:59 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: References: <18340.48193.193025.467642@montanaro.dyndns.org> <5349F935-4F33-4535-9E08-2697ADC2B1B5@macports.org> <18341.1555.367461.148039@montanaro.dyndns.org> <12EE9B11-547C-4B56-B117-87C0F3C2CA7F@macports.org> Message-ID: <18341.60195.544565.567@montanaro-dyndns-org.local> James> It looks to me like all you have to do is set "buildmakejobs" to James> the number of jobs you want make to use. Where do I set that, on the command line, in a config file? Thanks, -- Skip Montanaro - skip@pobox.com - http://www.webfast.com/~skip/ The major difference between Democrats and Republicans is that Republicans don't know that Randy Newman's lyrics are full of sarcasm. From afb at macports.org Sun Feb 3 08:26:41 2008 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun Feb 3 08:26:25 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: References: <18340.48193.193025.467642@montanaro.dyndns.org> <5349F935-4F33-4535-9E08-2697ADC2B1B5@macports.org> <18341.1555.367461.148039@montanaro.dyndns.org> <12EE9B11-547C-4B56-B117-87C0F3C2CA7F@macports.org> Message-ID: <77ee8ec04983c443a39cff1e2296e93c@macports.org> James Sumners wrote: > It looks to me like all you have to do is set "buildmakejobs" to the > number of jobs you want make to use. I assume port will then use that > many jobs when a portfile allows it. The number of build jobs is ignored, until the port says that it works. (otherwise the above is right, you can also say "0" to mean "# of cores") Setting of "makefile_isnt_buggy" was renamed to "use_parallel_build"... --anders From afb at macports.org Sun Feb 3 08:29:46 2008 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun Feb 3 08:29:39 2008 Subject: libtool woes In-Reply-To: <0467D51C-AA42-4A82-A555-F05CFF7876E5@macports.org> References: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> <0467D51C-AA42-4A82-A555-F05CFF7876E5@macports.org> Message-ID: <2a1b0fecc981505213bd11baac3b04a9@macports.org> Ryan Schmidt wrote: >> This problem is since the change to "/usr/bin/gcc-4.0" for CC. >> Switching compiler back to "gcc" (or "gcc-4.0") makes it work. >> >> Something like: port build configure.cc=gcc configure.cxx=g++ > > Can you explain more? Isn't "gcc" the same as "/usr/bin/gcc" which is > a symlink to "/usr/bin/gcc-4.0"? Also, I do not experience this > problem with apache2; why would some people see it and not others? It's the exact same thing, just that some versions of libtool weren't able to determine what to do with "/usr/bin/gcc-4.0" Haven't yet checked which ports the issue affects, and which are hit by something else - but it would be something to check... Rebuilding libtool might also work, haven't tried that either. --anders From skip at pobox.com Sun Feb 3 08:31:32 2008 From: skip at pobox.com (skip@pobox.com) Date: Sun Feb 3 08:31:20 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <18341.60195.544565.567@montanaro-dyndns-org.local> References: <18340.48193.193025.467642@montanaro.dyndns.org> <5349F935-4F33-4535-9E08-2697ADC2B1B5@macports.org> <18341.1555.367461.148039@montanaro.dyndns.org> <12EE9B11-547C-4B56-B117-87C0F3C2CA7F@macports.org> <18341.60195.544565.567@montanaro-dyndns-org.local> Message-ID: <18341.60516.53232.17168@montanaro-dyndns-org.local> skip> Where do I set that, on the command line, in a config file? Sorry. Saw it in a later message in the thread. I'll be more patient next time. Skip From ryandesign at macports.org Sun Feb 3 08:36:37 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Feb 3 08:36:37 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <77ee8ec04983c443a39cff1e2296e93c@macports.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> <5349F935-4F33-4535-9E08-2697ADC2B1B5@macports.org> <18341.1555.367461.148039@montanaro.dyndns.org> <12EE9B11-547C-4B56-B117-87C0F3C2CA7F@macports.org> <77ee8ec04983c443a39cff1e2296e93c@macports.org> Message-ID: On Feb 3, 2008, at 10:26, Anders F Bj?rklund wrote: > James Sumners wrote: > >> It looks to me like all you have to do is set "buildmakejobs" to the >> number of jobs you want make to use. I assume port will then use that >> many jobs when a portfile allows it. > > The number of build jobs is ignored, until the port says that it > works. > (otherwise the above is right, you can also say "0" to mean "# of > cores") > > Setting of "makefile_isnt_buggy" was renamed to > "use_parallel_build"... Thanks, everyone. I also checked out the code to confirm that it does work this way. http://trac.macosforge.org/projects/macports/browser/trunk/base/src/ port1.0/portbuild.tcl I filed a ticket to request it be documented in the guide. http://trac.macosforge.org/projects/macports/ticket/14164 From paulbeard at gmail.com Sun Feb 3 09:22:17 2008 From: paulbeard at gmail.com (paul beard) Date: Sun Feb 3 09:22:01 2008 Subject: libtool woes In-Reply-To: <2a1b0fecc981505213bd11baac3b04a9@macports.org> References: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> <0467D51C-AA42-4A82-A555-F05CFF7876E5@macports.org> <2a1b0fecc981505213bd11baac3b04a9@macports.org> Message-ID: On Feb 3, 2008 8:29 AM, Anders F Bj?rklund wrote: > > Rebuilding libtool might also work, haven't tried that either. > I have. It doesn't help. How do you use the configure args you posted? Just on the commandline? -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080203/99b22606/attachment.html From paulbeard at gmail.com Sun Feb 3 09:33:29 2008 From: paulbeard at gmail.com (paul beard) Date: Sun Feb 3 09:33:13 2008 Subject: libtool woes In-Reply-To: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> References: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> Message-ID: On Feb 3, 2008 1:32 AM, Anders F Bj?rklund wrote: > paul beard wrote: > > > Looks like I have some problem with libtool. > > libIDL and Apache2 both fail to upgrade. > ... > > libtool: compile: unable to infer tagged configuration > > libtool: compile: specify a tag with `--tag' > > This problem is since the change to "/usr/bin/gcc-4.0" for CC. > Switching compiler back to "gcc" (or "gcc-4.0") makes it work. > what baffles me about this is that the libtool that's being invoked is part of the port's code: /bin/sh ./libtool --tag=CC --mode=link gcc -O2 -no-cpp-precomp -version-info 0:0:0 -L/opt/local/lib -lglib-2.0 -lintl -liconv -no-undefined -L/opt/local/lib -o libIDL-2.la -rpath /opt/local/lib parser.lo lexer.lo ns.lo util.lo if I run port configure (with -d), what's happening here? configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by /usr/bin/g++-4.0... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking whether the /usr/bin/g++-4.0 linker (/usr/bin/ld) supports shared libraries... yes -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080203/d453fc87/attachment-0001.html From nox at macports.org Sun Feb 3 10:47:01 2008 From: nox at macports.org (N_Ox) Date: Sun Feb 3 10:46:49 2008 Subject: [MacPorts] #14163: Endless Avahi system.log errors In-Reply-To: <09262229-63EA-4467-B1BD-5123F436CA17@alum.mit.edu> References: <048.789d990c5906e55edbe72b74012ce83c@macosforge.org> <057.30dcad86c984ce651eb0834924394c46@macosforge.org> <09262229-63EA-4467-B1BD-5123F436CA17@alum.mit.edu> Message-ID: <8ABD930D-75CB-422A-A7F4-89A3D2B747F4@macports.org> Le 3 f?vr. 08 ? 19:15, Adam Dershowitz a ?crit : > I have looked into this a little more. I am not sure, but it looks > to me like org.macports.dbus.plist is disabled by default (at least > when this problem cropped up, I was showing it as disabled, so I > assume it started that way....or something else changed it). In > other words the launchd flag in the plist is set to true for > disabled. While the avahi-dnsconfd and avahi-daemon launchd are > set to enabled (well actually disabled is false). > I googled around some and found that dbus port should say this > during the install (although I didn't notice it at the time): > > ---> Creating launchd control script > ########################################################### > # A startup item has been generated that will aid in > # starting dbus with launchd. It is disabled > # by default. Execute the following command to start it, > # and to cause it to launch at startup: > # > # sudo launchctl load -w /Library/LaunchDaemons/ > org.macports.dbus.plist > ########################################################### > > As I understand it a bunch of launchd stuff is not reconfigured > until a restart of the machine. So the problem could be just that > dbus is disabled and avahi is enabled by default. And, if that is > the case, we probably need a Macports policy to make these things > consistent since one depends on the other one. > Does this make sense, and look likely to you? > > Thanks for handing this port and looking into this problem. It > could be a somewhat insidious problem as it only cropped up when I > did a reboot, which doesn't happen that often. > > --Adam > Please continue any discussion about this issue on the mailing-list. Regards, -- Anthony Ramine, the "Ports tree cleaning Maestro". From peter at pogma.com Sun Feb 3 11:27:30 2008 From: peter at pogma.com (Peter O'Gorman) Date: Sun Feb 3 11:27:13 2008 Subject: libtool woes In-Reply-To: References: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> Message-ID: <47A615A2.5050208@pogma.com> paul beard wrote: > > > On Feb 3, 2008 1:32 AM, Anders F Bj?rklund > wrote: > > paul beard wrote: > > > Looks like I have some problem with libtool. > > libIDL and Apache2 both fail to upgrade. > ... > > libtool: compile: unable to infer tagged configuration > > libtool: compile: specify a tag with `--tag' > > This problem is since the change to "/usr/bin/gcc-4.0" for CC. > Switching compiler back to "gcc" (or "gcc-4.0") makes it work. > > > what baffles me about this is that the libtool that's being invoked is > part of the port's code: > > /bin/sh ./libtool --tag=CC --mode=link gcc -O2 -no-cpp-precomp > -version-info 0:0:0 -L/opt/local/lib -lglib-2.0 -lintl -liconv > -no-undefined -L/opt/local/lib -o libIDL-2.la -rpath /opt/local/lib > parser.lo lexer.lo ns.lo util.lo > > if I run port configure (with -d), what's happening here? > > configure: creating libtool > appending configuration tag "CXX" to libtool > checking for ld used by /usr/bin/g++-4.0... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... no > checking whether the /usr/bin/g++-4.0 linker (/usr/bin/ld) supports > shared libraries... yes libtool is usually built in the build directory by running configure, it is included in the package. I had a quick look at the bugs mentioned: http://trac.macosforge.org/projects/macports/ticket/13653 http://trac.macosforge.org/projects/macports/ticket/13648 In both cases an installed GNU libtool is being called with a different compiler (at least a different compiler name) than it was built with. In these cases the tag *must* be specified --tag=CC or --tag=CXX etc. as GNU libtool can not guess it. Use the CC tag for C sources and the CXX tag for c++. For automake based projects automake adds the --tag when compiling with gnu libtool, for other projects upstream developer should be adding it, please send them patches. Peter -- Peter O'Gorman http://pogma.com From ryandesign at macports.org Sun Feb 3 11:44:26 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Feb 3 11:44:23 2008 Subject: libtool woes In-Reply-To: <47A615A2.5050208@pogma.com> References: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> <47A615A2.5050208@pogma.com> Message-ID: <98149BBD-5480-4C17-A6F7-2B7A75930697@macports.org> On Feb 3, 2008, at 13:27, Peter O'Gorman wrote: > paul beard wrote: > >> On Feb 3, 2008 1:32 AM, Anders F Bj?rklund wrote: >> >>> paul beard wrote: >>> >>>> Looks like I have some problem with libtool. >>>> libIDL and Apache2 both fail to upgrade. >>> ... >>>> libtool: compile: unable to infer tagged configuration >>>> libtool: compile: specify a tag with `--tag' >>> >>> This problem is since the change to "/usr/bin/gcc-4.0" for CC. >>> Switching compiler back to "gcc" (or "gcc-4.0") makes it work. >> >> what baffles me about this is that the libtool that's being >> invoked is >> part of the port's code: >> >> /bin/sh ./libtool --tag=CC --mode=link gcc -O2 -no-cpp-precomp >> -version-info 0:0:0 -L/opt/local/lib -lglib-2.0 -lintl -liconv >> -no-undefined -L/opt/local/lib -o libIDL-2.la -rpath /opt/local/lib >> parser.lo lexer.lo ns.lo util.lo >> >> if I run port configure (with -d), what's happening here? >> >> configure: creating libtool >> appending configuration tag "CXX" to libtool >> checking for ld used by /usr/bin/g++-4.0... /usr/bin/ld >> checking if the linker (/usr/bin/ld) is GNU ld... no >> checking whether the /usr/bin/g++-4.0 linker (/usr/bin/ld) supports >> shared libraries... yes > > libtool is usually built in the build directory by running > configure, it > is included in the package. I had a quick look at the bugs mentioned: > > http://trac.macosforge.org/projects/macports/ticket/13653 > http://trac.macosforge.org/projects/macports/ticket/13648 > > In both cases an installed GNU libtool which installed GNU libtool? you mean the libtool that the project built for itself? > is being called with a different > compiler (at least a different compiler name) than it was built with. what compiler name was it built with, and what compiler name is it being called with? and why are they different? > In > these cases the tag *must* be specified --tag=CC or --tag=CXX etc. as > GNU libtool can not guess it. Use the CC tag for C sources and the CXX > tag for c++. > > For automake based projects automake adds the --tag when compiling > with > gnu libtool, for other projects upstream developer should be adding > it, > please send them patches. From ryandesign at macports.org Sun Feb 3 11:46:46 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Feb 3 11:46:42 2008 Subject: [MacPorts] #14163: Endless Avahi system.log errors In-Reply-To: <8ABD930D-75CB-422A-A7F4-89A3D2B747F4@macports.org> References: <048.789d990c5906e55edbe72b74012ce83c@macosforge.org> <057.30dcad86c984ce651eb0834924394c46@macosforge.org> <09262229-63EA-4467-B1BD-5123F436CA17@alum.mit.edu> <8ABD930D-75CB-422A-A7F4-89A3D2B747F4@macports.org> Message-ID: <99E2DB87-253B-4CDF-8500-78D3CE37E475@macports.org> Le 3 f?vr. 08 ? 19:15, Adam Dershowitz a ?crit : > I have looked into this a little more. I am not sure, but it looks > to me like org.macports.dbus.plist is disabled by default (at least > when this problem cropped up, I was showing it as disabled, so I > assume it started that way....or something else changed it). In > other words the launchd flag in the plist is set to true for > disabled. While the avahi-dnsconfd and avahi-daemon launchd are > set to enabled (well actually disabled is false). > I googled around some and found that dbus port should say this > during the install (although I didn't notice it at the time): > > ---> Creating launchd control script > ########################################################### > # A startup item has been generated that will aid in > # starting dbus with launchd. It is disabled > # by default. Execute the following command to start it, > # and to cause it to launch at startup: > # > # sudo launchctl load -w /Library/LaunchDaemons/ > org.macports.dbus.plist > ########################################################### > > As I understand it a bunch of launchd stuff is not reconfigured > until a restart of the machine. Which part of launchd do you think requires a restart? I thought that one of the advantages of launchd over startupitems was that with launchd you can start and stop services immediately rather than wait for a restart which you had to do with startupitems. > So the problem could be just that dbus is disabled and avahi is > enabled by default. And, if that is the case, we probably need a > Macports policy to make these things consistent since one depends > on the other one. > Does this make sense, and look likely to you? > > Thanks for handing this port and looking into this problem. It > could be a somewhat insidious problem as it only cropped up when I > did a reboot, which doesn't happen that often. From peter at pogma.com Sun Feb 3 11:50:55 2008 From: peter at pogma.com (Peter O'Gorman) Date: Sun Feb 3 11:50:37 2008 Subject: libtool woes In-Reply-To: <98149BBD-5480-4C17-A6F7-2B7A75930697@macports.org> References: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> <47A615A2.5050208@pogma.com> <98149BBD-5480-4C17-A6F7-2B7A75930697@macports.org> Message-ID: <47A61B1F.9000903@pogma.com> Ryan Schmidt wrote: >>> >>> what baffles me about this is that the libtool that's being invoked is >>> part of the port's code: >>> >>> /bin/sh ./libtool --tag=CC --mode=link gcc -O2 -no-cpp-precomp >>> -version-info 0:0:0 -L/opt/local/lib -lglib-2.0 -lintl -liconv >>> -no-undefined -L/opt/local/lib -o libIDL-2.la -rpath /opt/local/lib >>> parser.lo lexer.lo ns.lo util.lo This is failing with 'unable to infer tagged configuration'? Seems pretty strange as it has a --tag argument, it should not even be trying to infer the tag. >>> >>> if I run port configure (with -d), what's happening here? >>> >>> configure: creating libtool >>> appending configuration tag "CXX" to libtool >>> checking for ld used by /usr/bin/g++-4.0... /usr/bin/ld >>> checking if the linker (/usr/bin/ld) is GNU ld... no >>> checking whether the /usr/bin/g++-4.0 linker (/usr/bin/ld) supports >>> shared libraries... yes >> >> libtool is usually built in the build directory by running configure, it >> is included in the package. I had a quick look at the bugs mentioned: >> >> http://trac.macosforge.org/projects/macports/ticket/13653 >> http://trac.macosforge.org/projects/macports/ticket/13648 >> >> In both cases an installed GNU libtool > > which installed GNU libtool? you mean the libtool that the project built > for itself? one is calling /opt/local/bin/glibtool, the other is using apr's libtool (/opt/local/share/apr-1/build/libtool). > >> is being called with a different >> compiler (at least a different compiler name) than it was built with. > > what compiler name was it built with, and what compiler name is it being > called with? and why are they different? I assume it was built with 'gcc' and it is being called with '/usr/bin/gcc-4.0'. Not the same name. Peter -- Peter O'Gorman http://pogma.com From dersh at alum.mit.edu Sun Feb 3 11:56:56 2008 From: dersh at alum.mit.edu (Adam Dershowitz) Date: Sun Feb 3 11:56:40 2008 Subject: [MacPorts] #14163: Endless Avahi system.log errors In-Reply-To: <99E2DB87-253B-4CDF-8500-78D3CE37E475@macports.org> References: <048.789d990c5906e55edbe72b74012ce83c@macosforge.org> <057.30dcad86c984ce651eb0834924394c46@macosforge.org> <09262229-63EA-4467-B1BD-5123F436CA17@alum.mit.edu> <8ABD930D-75CB-422A-A7F4-89A3D2B747F4@macports.org> <99E2DB87-253B-4CDF-8500-78D3CE37E475@macports.org> Message-ID: <2B717704-8696-48C4-BB76-6881401330AD@alum.mit.edu> On Feb 3, 2008, at 11:46 AM, Ryan Schmidt wrote: > Le 3 f?vr. 08 ? 19:15, Adam Dershowitz a ?crit : > >> I have looked into this a little more. I am not sure, but it looks >> to me like org.macports.dbus.plist is disabled by default (at least >> when this problem cropped up, I was showing it as disabled, so I >> assume it started that way....or something else changed it). In >> other words the launchd flag in the plist is set to true for >> disabled. While the avahi-dnsconfd and avahi-daemon launchd are >> set to enabled (well actually disabled is false). >> I googled around some and found that dbus port should say this >> during the install (although I didn't notice it at the time): >> >> ---> Creating launchd control script >> ########################################################### >> # A startup item has been generated that will aid in >> # starting dbus with launchd. It is disabled >> # by default. Execute the following command to start it, >> # and to cause it to launch at startup: >> # >> # sudo launchctl load -w /Library/LaunchDaemons/ >> org.macports.dbus.plist >> ########################################################### >> >> As I understand it a bunch of launchd stuff is not reconfigured >> until a restart of the machine. > > Which part of launchd do you think requires a restart? I thought > that one of the advantages of launchd over startupitems was that > with launchd you can start and stop services immediately rather than > wait for a restart which you had to do with startupitems. I have not played with launchd much. But I did play with Lingon just a little bit. It is a free gui to deal with launchd stuff. And that I how I realized that dbus was disabled. When you make any changes in stuff with that, it says that you have to logout, or restart for the changes to take effect. That is why I thought that might be the case. But I am far from a launchd expert. It could be just a lack in Lingon. But what is clear is that after a reboot, my problem started. And then I used Lingon to see that dbus was disabled while Avahi was not. So perhaps what actually happens is that the files are installed that way, but at the same time when the dbus port is first installed it is also activated, but not through launchd? The above message sure makes it clear that unless you manually enter the above command that dbus is disabled and will not launch at a system start. And I had not issued that command when dbus was first installed at the bottom of a dependency chain. So I had not noticed the above message, and I was not even sure which port installed and required dbus. --Adam From ryandesign at macports.org Sun Feb 3 12:03:26 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Feb 3 12:03:21 2008 Subject: libtool woes In-Reply-To: <47A61B1F.9000903@pogma.com> References: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> <47A615A2.5050208@pogma.com> <98149BBD-5480-4C17-A6F7-2B7A75930697@macports.org> <47A61B1F.9000903@pogma.com> Message-ID: <00D5CE6C-5A99-41BE-A8BE-7609533DEE2E@macports.org> On Feb 3, 2008, at 13:50, Peter O'Gorman wrote: > Ryan Schmidt wrote: > >>>> what baffles me about this is that the libtool that's being >>>> invoked is >>>> part of the port's code: >>>> >>>> /bin/sh ./libtool --tag=CC --mode=link gcc -O2 -no-cpp-precomp >>>> -version-info 0:0:0 -L/opt/local/lib -lglib-2.0 -lintl -liconv >>>> -no-undefined -L/opt/local/lib -o libIDL-2.la -rpath /opt/local/lib >>>> parser.lo lexer.lo ns.lo util.lo > > This is failing with 'unable to infer tagged configuration'? Seems > pretty strange as it has a --tag argument, it should not even be > trying > to infer the tag. I don't know what's going on; I'm just quoting here. >>>> if I run port configure (with -d), what's happening here? >>>> >>>> configure: creating libtool >>>> appending configuration tag "CXX" to libtool >>>> checking for ld used by /usr/bin/g++-4.0... /usr/bin/ld >>>> checking if the linker (/usr/bin/ld) is GNU ld... no >>>> checking whether the /usr/bin/g++-4.0 linker (/usr/bin/ld) supports >>>> shared libraries... yes >>> >>> libtool is usually built in the build directory by running >>> configure, it >>> is included in the package. I had a quick look at the bugs >>> mentioned: >>> >>> http://trac.macosforge.org/projects/macports/ticket/13653 >>> http://trac.macosforge.org/projects/macports/ticket/13648 >>> >>> In both cases an installed GNU libtool >> >> which installed GNU libtool? you mean the libtool that the project >> built >> for itself? > > one is calling /opt/local/bin/glibtool, the other is using apr's > libtool > (/opt/local/share/apr-1/build/libtool). I don't know what "one" or "the other" is. But now you're saying there are three libtools involved -- the one in /opt/local/bin/ glibtool, the one in /opt/local/share/apr-1/build/libtool, and the one in ${worksrcdir}/libtool? I have the libtool port installed and do not see the problem. Maybe I would see the problem if I removed the libtool port? Maybe the problem is that the users experiencing this problem installed either libtool or apr or both before MacPorts 1.6 and are now trying to install apache2 with MacPorts 1.6? Could that be? If so the solution would be to rebuild libtool or apr? >>> is being called with a different >>> compiler (at least a different compiler name) than it was built >>> with. >> >> what compiler name was it built with, and what compiler name is it >> being >> called with? and why are they different? > > I assume it was built with 'gcc' and it is being called with > '/usr/bin/gcc-4.0'. Not the same name. From ryandesign at macports.org Sun Feb 3 12:06:10 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Feb 3 12:06:05 2008 Subject: [MacPorts] #14163: Endless Avahi system.log errors In-Reply-To: <2B717704-8696-48C4-BB76-6881401330AD@alum.mit.edu> References: <048.789d990c5906e55edbe72b74012ce83c@macosforge.org> <057.30dcad86c984ce651eb0834924394c46@macosforge.org> <09262229-63EA-4467-B1BD-5123F436CA17@alum.mit.edu> <8ABD930D-75CB-422A-A7F4-89A3D2B747F4@macports.org> <99E2DB87-253B-4CDF-8500-78D3CE37E475@macports.org> <2B717704-8696-48C4-BB76-6881401330AD@alum.mit.edu> Message-ID: <53204EE3-F14E-447A-90BB-FDAB3C5FA347@macports.org> On Feb 3, 2008, at 13:56, Adam Dershowitz wrote: > On Feb 3, 2008, at 11:46 AM, Ryan Schmidt wrote: > >> Le 3 f?vr. 08 ? 19:15, Adam Dershowitz a ?crit : >> >>> I have looked into this a little more. I am not sure, but it >>> looks to me like org.macports.dbus.plist is disabled by default >>> (at least when this problem cropped up, I was showing it as >>> disabled, so I assume it started that way....or something else >>> changed it). In other words the launchd flag in the plist is set >>> to true for disabled. While the avahi-dnsconfd and avahi-daemon >>> launchd are set to enabled (well actually disabled is false). >>> I googled around some and found that dbus port should say this >>> during the install (although I didn't notice it at the time): >>> >>> ---> Creating launchd control script >>> ########################################################### >>> # A startup item has been generated that will aid in >>> # starting dbus with launchd. It is disabled >>> # by default. Execute the following command to start it, >>> # and to cause it to launch at startup: >>> # >>> # sudo launchctl load -w /Library/LaunchDaemons/ >>> org.macports.dbus.plist >>> ########################################################### >>> >>> As I understand it a bunch of launchd stuff is not reconfigured >>> until a restart of the machine. >> >> Which part of launchd do you think requires a restart? I thought >> that one of the advantages of launchd over startupitems was that >> with launchd you can start and stop services immediately rather >> than wait for a restart which you had to do with startupitems. > > I have not played with launchd much. But I did play with Lingon > just a little bit. It is a free gui to deal with launchd stuff. > And that I how I realized that dbus was disabled. When you make > any changes in stuff with that, it says that you have to logout, or > restart for the changes to take effect. That is why I thought that > might be the case. But I am far from a launchd expert. It could > be just a lack in Lingon. > But what is clear is that after a reboot, my problem started. And > then I used Lingon to see that dbus was disabled while Avahi was > not. So perhaps what actually happens is that the files are > installed that way, but at the same time when the dbus port is > first installed it is also activated, but not through launchd? The > above message sure makes it clear that unless you manually enter > the above command that dbus is disabled and will not launch at a > system start. And I had not issued that command when dbus was > first installed at the bottom of a dependency chain. So I had not > noticed the above message, and I was not even sure which port > installed and required dbus. All I know is that when you say sudo launchctl load -w /Library/LaunchDaemons/org.macports.foo.plist foo is started immediately, and will start at every system startup. And when you say sudo launchctl unload -w /Library/LaunchDaemons/org.macports.foo.plist foo will stop immediately, and will no longer start at system startup. I do know specifically about dbus or Avahi. I have not used Lingon. From face at CentosPrime.COM Sun Feb 3 13:09:54 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sun Feb 3 13:10:21 2008 Subject: libtool woes In-Reply-To: <00D5CE6C-5A99-41BE-A8BE-7609533DEE2E@macports.org> References: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> <47A615A2.5050208@pogma.com> <98149BBD-5480-4C17-A6F7-2B7A75930697@macports.org> <47A61B1F.9000903@pogma.com> <00D5CE6C-5A99-41BE-A8BE-7609533DEE2E@macports.org> Message-ID: <50D255AE-31CB-4023-9724-3E14069BC745@centosprime.com> On 2008-02-03 , at 13:03 , Ryan Schmidt wrote: > Maybe the problem is that the users experiencing this problem > installed either libtool or apr or both before MacPorts 1.6 and are > now trying to install apache2 with MacPorts 1.6? Could that be? If > so the solution would be to rebuild libtool or apr? sudo port -f uninstall libtool sudo port -f uninstall apr sudo port install libtool sudo port install apr sudo port clean apache2 sudo port upgrade apache2 Solved the problem for me on my 10.4 Intel system - no more build errors. I will do the same on my 10.5 system and report back if it fails. 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From David.Epstein at warwick.ac.uk Sun Feb 3 13:24:40 2008 From: David.Epstein at warwick.ac.uk (David Epstein) Date: Sun Feb 3 13:24:22 2008 Subject: libtool woes In-Reply-To: <4E2EFAA0-4AC4-4767-8EE9-B97286A8EE62@macports.org> References: <4E2EFAA0-4AC4-4767-8EE9-B97286A8EE62@macports.org> Message-ID: <15258474.post@talk.nabble.com> Ryan Schmidt-24 wrote: > > "unable to infer tagged configuration" when trying to build apache2 > is already filed: > http://trac.macosforge.org/projects/macports/ticket/13653 > ...[snip]... > Both tickets include lots of discussion. The apache2 ticket includes > patches which someone said worked. > Neither maintainer has responded to the tickets. Looks like it's time > for someone else to commit the fixes. Probably not me, since I'm not > experiencing the issue. > As an inexperienced MacPorter, I would like advice on what to do, in view of my need for apache2. Possible strategies: 1) Wait for someone to put the advertised patches into the official macport distribution. 2) Install the advertised patches. (Are there instructions somewhere for how to do this?) 3) Try rebuilding libtool. (But won't port object to deleting libtool because other packages depend on it?) Pointer to relevant online advice?? David -- View this message in context: http://www.nabble.com/libtool-woes-tp15248567p15258474.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From paulbeard at gmail.com Sun Feb 3 13:33:18 2008 From: paulbeard at gmail.com (paul beard) Date: Sun Feb 3 13:33:03 2008 Subject: libtool woes In-Reply-To: <15258474.post@talk.nabble.com> References: <4E2EFAA0-4AC4-4767-8EE9-B97286A8EE62@macports.org> <15258474.post@talk.nabble.com> Message-ID: On Feb 3, 2008 1:24 PM, David Epstein wrote: > > > Ryan Schmidt-24 wrote: > > > > "unable to infer tagged configuration" when trying to build apache2 > > is already filed: > > http://trac.macosforge.org/projects/macports/ticket/13653 > > ...[snip]... > > Both tickets include lots of discussion. The apache2 ticket includes > > patches which someone said worked. > > Neither maintainer has responded to the tickets. Looks like it's time > > for someone else to commit the fixes. Probably not me, since I'm not > > experiencing the issue. > > > > As an inexperienced MacPorter, I would like advice on what to do, in view > of > my need for apache2. > Possible strategies: > 1) Wait for someone to put the advertised patches into the official > macport > distribution. > 2) Install the advertised patches. (Are there instructions somewhere for > how > to do this?) > 3) Try rebuilding libtool. (But won't port object to deleting libtool > because other packages depend on it?) > I am trying this regime: sudo port -f uninstall libtool sudo port -f uninstall apr sudo port install libtool sudo port install apr sudo port clean apache2 sudo port upgrade apache2 port -f overrides any complaints (on your #3 above). if peter o'gorman's diagnosis above is correct, how can this be fixed in a more systematic manner? -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080203/a809366e/attachment.html From ryandesign at macports.org Sun Feb 3 13:54:34 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun Feb 3 13:54:30 2008 Subject: libtool woes In-Reply-To: <50D255AE-31CB-4023-9724-3E14069BC745@centosprime.com> References: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> <47A615A2.5050208@pogma.com> <98149BBD-5480-4C17-A6F7-2B7A75930697@macports.org> <47A61B1F.9000903@pogma.com> <00D5CE6C-5A99-41BE-A8BE-7609533DEE2E@macports.org> <50D255AE-31CB-4023-9724-3E14069BC745@centosprime.com> Message-ID: On Feb 3, 2008, at 15:09, Chris Janton wrote: > On 2008-02-03 , at 13:03 , Ryan Schmidt wrote: > >> Maybe the problem is that the users experiencing this problem >> installed either libtool or apr or both before MacPorts 1.6 and >> are now trying to install apache2 with MacPorts 1.6? Could that >> be? If so the solution would be to rebuild libtool or apr? > > sudo port -f uninstall libtool > sudo port -f uninstall apr > sudo port install libtool > sudo port install apr > sudo port clean apache2 > sudo port upgrade apache2 > > Solved the problem for me on my 10.4 Intel system - no more build > errors. Good to know! > I will do the same on my 10.5 system and report back if it fails. Can you try just libtool first? Then if that fails, then try apr. From stochashtic at yahoo.ca Sun Feb 3 14:14:08 2008 From: stochashtic at yahoo.ca (Suresh Pillai) Date: Sun Feb 3 14:13:50 2008 Subject: py25-hashlib failing on build Message-ID: As mentioned in my previous thread, I cannot install some required python libs since py25-hashlib is failing: ---> Building py25-hashlib with target build 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-hashlib/work/Python-2.5.1/Modules" && /opt/local/bin/python2.5 setup.py build " returned error 1 Command output: running build running build_ext building '_hashlib' extension -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/opt/local/include -I/opt/local/include/python2.5 -c _hashopenssl.c -o build/temp.macosx-10.3-i386-2.5/_hashopenssl.o unable to execute -DNDEBUG: No such file or directory error: command '-DNDEBUG' failed with exit status 1 Cheers, Suresh From jkorchok at hotmail.com Sun Feb 3 14:14:48 2008 From: jkorchok at hotmail.com (John Korchok) Date: Sun Feb 3 14:14:30 2008 Subject: Oracle Notes In-Reply-To: References: <8e58e692fa3c3c694ea0b0cedda25def@macports.org><47A615A2.5050208@pogma.com><98149BBD-5480-4C17-A6F7-2B7A75930697@macports.org><47A61B1F.9000903@pogma.com><00D5CE6C-5A99-41BE-A8BE-7609533DEE2E@macports.org><50D255AE-31CB-4023-9724-3E14069BC745@centosprime.com> Message-ID: For anyone else who may be struggling with getting Oracle to play with MacPorts PHP, here are my notes after installation on three systems and about 100 hours of tinkering. Start with a PowerPC, as the Oracle Instant Client for Mac does not yet work with Intel machines. 1. Install php5 with oracle support: sudo port install php5 +apache2 +oracle 2. So that the Apache user can find the relevant files, add environment variables to opt/local/apache2/bin/envvars: export LD_LIBRARY_PATH="/opt/local/lib/oracle" export TNS_ADMIN="/Applications/Oracle" (or whatever folder is a convenient spot to store sqlnet.ora and tnsnames.ora) Many web sites refer to setting DYLD_LIBRARY_PATH, you can do that instead of LD_LIBRARY_PATH and it has the same effect. Heck, use 'em both for good measure! Do _not_ use putenv in a PHP script or SetEnv in httpd.conf to set the variables, it won't work. Apache will also not pick up environment variables from /private/etc/profile. Note to Ryan: can MacPorts update envvars? 3. Restart Apache For testing purposes, you can also add support for SQLPlus from the command line by downloading the Instant Client SQLPlus files from http://www.oracle.com/technology/software/tech/oci/instantclient/htdocs/macs oft.html and copying them to opt/local/lib/oracle. In that case you will have to add these variables to /Users/YourUserName/.profile: export LD_LIBRARY_PATH="/opt/local/lib/oracle:$LD_LIBRARY_PATH" export TNS_ADMIN="/Applications/Oracle" export PATH="/opt/local/lib/oracle:$PATH" If you prefer all users to have SQLPlus access, add the variables to /private/etc/profile If you have trouble with errors like "ORA-12154: TNS:could not resolve the connect identifier specified", Oracle may not be able to read your tnsnames.ora file. We had to amend the first line from "ALIG" to "ALIG.revion.com" (appending the url of the host name) to get it to work. Here are connection strings for PHP and SQLPlus, respectively: $con = OCILogon('YourUserName', 'YourPassword', "//your.host.address.com:1521/YourServiceName"); sqlplus YourUserName/YourPassword@//your.host.address.com:1521/YourServiceName If all else fails, you can use a verbose connection string to eliminate any need for tnsnames.ora: $con = oci_connect('YourUserName', 'YourPassword', '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=your.host.address.com)(PORT=1521) )(CONNECT_DATA=(SID=YourServiceName)(SERVER=DEDICATED)))'); Here's the verbose syntax for SQLPlus: sqlplus YourUserName/YourPassword@\(DESCRIPTION=\(ADDRESS=\(PROTOCOL=TCP\)\(HOST=you r.host.address.com\)\(PORT=1521\)\)\(CONNECT_DATA=\(SID=YourServiceName\)\(S ERVER=DEDICATED\)\)\) John Korchok From jeffrey at goldmark.org Sun Feb 3 14:21:34 2008 From: jeffrey at goldmark.org (Jeffrey Goldberg) Date: Sun Feb 3 14:21:16 2008 Subject: gnucash linking wrong libffi.dylib Message-ID: I must confess that I do not even begin to understand prebinding. Nor do I know what the OS X analog of the linux ldconfig command and configuration is. But I suspect that the answer to my problem will lie in those directions. I've installed gnome/gnucash using macports (that was a bit of a trick because of confusion about which guile installation was needed. Gnucash configure couldn't find guile16, but I had other problems with guile 1.8. I also needed to install "+without_docs" because otherwise port tried and failed to install firefox) But I did finally get something compiled and installed. However, it won't run, and this is what I get to standard error. dyld: Library not loaded: /usr/lib/libffi.dylib Referenced from: /System/Library/Frameworks/QuartzCore.framework/Versions/A/ QuartzCore Reason: Incompatible library version: QuartzCore requires version 1.0.0 or later, but libffi.dylib provides version 0.0.0 I note that there is a an /opt/local/lib/libffi.dylib installed, but apparently that's not the dynamic library that gnucash finds. As I've said, I am clueless about dynamic libraries, particularly on OS X. I'm running OS X 10.5.1 with Xcode 3.0 on a G5 PPC. I have also installed the update to X11 from Macosforge. Cheers, -j -- Jeffrey Goldberg http://www.goldmark.org/jeff/ From skip at pobox.com Sun Feb 3 14:34:08 2008 From: skip at pobox.com (skip@pobox.com) Date: Sun Feb 3 14:33:55 2008 Subject: py25-hashlib failing on build In-Reply-To: References: Message-ID: <18342.16736.110860.426839@montanaro-dyndns-org.local> Suresh> As mentioned in my previous thread, I cannot install some Suresh> required python libs since py25-hashlib is failing: I can confirm that, and for the same reason. It's like it doesn't know what the compiler command is. I install various versions of Python from source all the time. I've never seen this problem before. Skip Montanaro From paulbeard at gmail.com Sun Feb 3 14:37:46 2008 From: paulbeard at gmail.com (paul beard) Date: Sun Feb 3 14:37:29 2008 Subject: SOLVED: libtool woes Message-ID: On Feb 3, 2008 1:33 PM, paul beard wrote: > > > I am trying this regime: sudo port -f uninstall libtool > sudo port -f uninstall apr > sudo port install libtool > sudo port install apr > sudo port clean apache2 > sudo port upgrade apache2 > This seems to work. -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080203/2d3dfc5b/attachment.html From face at CentosPrime.COM Sun Feb 3 14:39:23 2008 From: face at CentosPrime.COM (Chris Janton) Date: Sun Feb 3 14:39:46 2008 Subject: libtool woes In-Reply-To: References: <4E2EFAA0-4AC4-4767-8EE9-B97286A8EE62@macports.org> <15258474.post@talk.nabble.com> Message-ID: On 2008-02-03 , at 14:33 , paul beard wrote: > I am trying this regime: sudo port -f uninstall libtool > sudo port -f uninstall apr > sudo port install libtool > sudo port install apr > sudo port clean apache2 > sudo port upgrade apache2 This worked on my 10.5 system where I had the apache2 problem as well. 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From paulbeard at gmail.com Sun Feb 3 15:05:58 2008 From: paulbeard at gmail.com (paul beard) Date: Sun Feb 3 15:05:41 2008 Subject: NOT SOLVED: libtool woes Message-ID: Too hasty, it seems. Apache2 upgraded just fine but libidl is still balking. On Feb 3, 2008 2:37 PM, paul beard wrote: > > > On Feb 3, 2008 1:33 PM, paul beard wrote: > > > > > > > I am trying this regime: sudo port -f uninstall libtool > > sudo port -f uninstall apr > > sudo port install libtool > > sudo port install apr > > sudo port clean apache2 > > sudo port upgrade apache2 > > > > This seems to work. > > > > -- > Paul Beard / www.paulbeard.org/ > -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080203/0d8f2dda/attachment.html From peter at pogma.com Sun Feb 3 15:10:54 2008 From: peter at pogma.com (Peter O'Gorman) Date: Sun Feb 3 15:10:36 2008 Subject: libtool woes In-Reply-To: <00D5CE6C-5A99-41BE-A8BE-7609533DEE2E@macports.org> References: <8e58e692fa3c3c694ea0b0cedda25def@macports.org> <47A615A2.5050208@pogma.com> <98149BBD-5480-4C17-A6F7-2B7A75930697@macports.org> <47A61B1F.9000903@pogma.com> <00D5CE6C-5A99-41BE-A8BE-7609533DEE2E@macports.org> Message-ID: <47A649FE.6020902@pogma.com> Ryan Schmidt wrote: >>>> >>>> libtool is usually built in the build directory by running >>>> configure, it >>>> is included in the package. I had a quick look at the bugs mentioned: >>>> >>>> http://trac.macosforge.org/projects/macports/ticket/13653 >>>> http://trac.macosforge.org/projects/macports/ticket/13648 >>>> >>>> In both cases an installed GNU libtool >>> >>> which installed GNU libtool? you mean the libtool that the project built >>> for itself? >> >> one is calling /opt/local/bin/glibtool, the other is using apr's libtool >> (/opt/local/share/apr-1/build/libtool). > > I don't know what "one" or "the other" is. That's silly - I listed the 2 bugs, two builds, "one" and "the other". But now you're saying there > are three libtools involved -- the one in /opt/local/bin/glibtool, the > one in /opt/local/share/apr-1/build/libtool, and the one in > ${worksrcdir}/libtool? > > I have the libtool port installed and do not see the problem. Maybe I > would see the problem if I removed the libtool port? >From the looks of things MacPorts at some point changed the default setting for CC? If that is the case, it means that people who had built e.g. apr before it was changed, and then tried to build apache after the change will see this breakage. Peter -- Peter O'Gorman http://pogma.com From peter at pogma.com Sun Feb 3 15:13:49 2008 From: peter at pogma.com (Peter O'Gorman) Date: Sun Feb 3 15:13:31 2008 Subject: NOT SOLVED: libtool woes In-Reply-To: References: Message-ID: <47A64AAD.7020408@pogma.com> paul beard wrote: > Too hasty, it seems. Apache2 upgraded just fine but libidl is still > balking. I looked back and saw your original post - this is a different error entirely: /bin/sh ./libtool --tag=CC --mode=link /usr/bin/gcc-4.0 -O2 -no-cpp-precomp -version-info 0:0:0 -L/opt/local/lib -lglib-2.0 -lintl -liconv -no-undefined -L/opt/local/lib -o libIDL-2.la -rpath /opt/local/lib parser.lo lexer.lo ns.lo util.lo /usr/bin/gcc-4.0 -dynamiclib -o .libs/libIDL-2.0.0.0.dylib .libs/parser.o .libs/lexer.o .libs/ns.o .libs/util.o -L/opt/local/lib /opt/local/lib/libglib-2.0.dylib /opt/local/lib/libintl.dylib /opt/local/lib/libiconv.dylib -install_name /opt/local/lib/libIDL-2.0.dylib -compatibility_version 1 -current_version 1.0 ld: Undefined symbols: ___IDL_cur_token_line ___IDL_lex ___IDL_prev_token_line ___IDL_in ___IDL_lex_cleanup ___IDL_lex_init /usr/bin/libtool: internal link edit command failed make[2]: *** [libIDL-2.la] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 From luomo1138 at yahoo.com Sun Feb 3 15:38:51 2008 From: luomo1138 at yahoo.com (Dexter Douglas) Date: Sun Feb 3 15:38:32 2008 Subject: how to reconfigure f2py In-Reply-To: <799406d60802021559l3321879aodb202d1f7ff6ea4a@mail.gmail.com> Message-ID: <742466.90238.qm@web60425.mail.yahoo.com> Hello, I have upgraded my py25-numpy package. It works. Thanks, Jim --- Adam Mercer wrote: > On Jan 30, 2008 5:13 PM, Dexter Douglas > wrote: > > > Then I modified the linker flags. > > In > > > /opt/local/lib/python2.5/site-packages/numpy/distutils/fcompiler/g95.py > > > > I changed line 24 from > > 'linker_so' : ["","-static"], > > to > > 'linker_so' : ["","-dynamiclib > > -L/opt/local/lib -lpython2.5"], > > This has been incorporated into py-numpy/py25-numpy > version 1.0.4_6, > can you update to that version and check that f2py > still works with > g95? > > Cheers > > Adam > ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs From vincent-opdarw at vinc17.org Sun Feb 3 16:48:16 2008 From: vincent-opdarw at vinc17.org (Vincent Lefevre) Date: Sun Feb 3 16:48:00 2008 Subject: Can the port command take advantage of multiple cores? In-Reply-To: <5349F935-4F33-4535-9E08-2697ADC2B1B5@macports.org> References: <18340.48193.193025.467642@montanaro.dyndns.org> <5349F935-4F33-4535-9E08-2697ADC2B1B5@macports.org> Message-ID: <20080204004816.GD17147@prunille.vinc17.org> On 2008-02-02 17:45:35 -0600, Ryan Schmidt wrote: > Not exactly. Not all software supports parallel building. Each port must > be tested to ensure that it works. As ports are tested, > "use_parallel_build yes" is added to the portfile. Then MacPorts will > build those ports using -j$jobs (where $jobs is the number of CPU cores > in your computer). This was added for MacPorts 1.6. Is there any reason why this option isn't documented in the portfile(7) man page? -- Vincent Lef?vre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) From mark at dxradio.demon.co.uk Sun Feb 3 16:53:46 2008 From: mark at dxradio.demon.co.uk (Mark Hattam) Date: Sun Feb 3 16:53:32 2008 Subject: Error upgrading Apache2 In-Reply-To: <3BE99452-B436-43BF-8D8C-FF117E1C763D@CentosPrime.COM> References: <3BE99452-B436-43BF-8D8C-FF117E1C763D@CentosPrime.COM> Message-ID: I can't get Apache 2.2.6 to upgrade to Apache 2.2.8 in MacPorts 1.6 either ... Mac OSX 10.4.11 on a PowerBook Ti 667 (PowerPC) with MacPorts 1.6.0 Quite early on it fails with a error 2 Never had a problem before - everything else has built fine, including previous Apache 2.2.x's Terminal output copy/pasted below Mark Powerbook:~ mark$ sudo port outdated The following installed ports are outdated: apache2 2.2.6_0 < 2.2.8_0 Powerbook:~ mark$ sudo port upgrade outdated ---> Building apache2 with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8" && make all " returned error 2 Command output: Making all in srclib Making all in os Making all in unix /opt/local/share/apr-1/build/libtool --silent --mode=compile /usr/bin/gcc-4.0 -I/opt/local/include -O2 -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp -I/opt/local/include -I. -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/os/unix -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/server/mpm/prefork -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/http -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/filters -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/proxy -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/generators -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/mappers -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/database -I/opt/local/include/apr-1 -I/opt/local/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/server -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/proxy/../generators -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/ssl -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/dav/main -prefer-non-pic -static -c unixd.c && touch unixd.lo libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' make[3]: *** [unixd.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 Error: Unable to upgrade port: 1 === At 10:06 -0700 2/2/08, Chris Janton wrote: >This occurs on both 10.4 and 10.5 with macports version 1.6 or later. >Same error on both systems. > >---> Building apache2 with target all >Error: Target org.macports.build returned: shell command " cd >"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8" >&& make all " returned error 2 >Command output: Making all in srclib >Making all in os >Making all in unix >/opt/local/share/apr-1/build/libtool --silent --mode=compile >/usr/bin/gcc-4.0 -I/opt/local/include -O2 -DDARWIN >-DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp -I/opt/local/include >-I. >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/os/unix >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/server/mpm/prefork >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/http >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/filters >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/proxy >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/include >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/generators >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/mappers >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/database >-I/opt/local/include/apr-1 -I/opt/local/include >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/server >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/proxy/../generators >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/ssl >-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd-2.2.8/modules/dav/main >-prefer-non-pic -static -c unixd.c && touch unixd.lo >libtool: compile: unable to infer tagged configuration >libtool: compile: specify a tag with `--tag' >make[3]: *** [unixd.lo] Error 1 >make[2]: *** [all-recursive] Error 1 >make[1]: *** [all-recursive] Error 1 >make: *** [all-recursive] Error 1 > >Error: Unable to upgrade port: 1 > > >8) >---------------------------------- >Chris Janton - face at CentosPrime dot COM >Netminder for Opus1.COM From dbreiser at gmail.com Sun Feb 3 21:27:32 2008 From: dbreiser at gmail.com (David Reiser) Date: Sun Feb 3 21:27:14 2008 Subject: gnucash linking wrong libffi.dylib In-Reply-To: References: Message-ID: On Feb 3, 2008, at 5:21 PM, Jeffrey Goldberg wrote: > I must confess that I do not even begin to understand prebinding. > Nor do I know what the OS X analog of the linux ldconfig command and > configuration is. But I suspect that the answer to my problem will > lie in those directions. > > I've installed gnome/gnucash using macports (that was a bit of a > trick because of confusion about which guile installation was > needed. Gnucash configure couldn't find guile16, but I had other > problems with guile 1.8. I also needed to install "+without_docs" > because otherwise port tried and failed to install firefox) But I > did finally get something compiled and installed. > > However, it won't run, and this is what I get to standard error. > > dyld: Library not loaded: /usr/lib/libffi.dylib > Referenced from: > /System/Library/Frameworks/QuartzCore.framework/Versions/A/ > QuartzCore > Reason: Incompatible library version: QuartzCore requires version > 1.0.0 or later, > but libffi.dylib provides version 0.0.0 > > I note that there is a an /opt/local/lib/libffi.dylib installed, but > apparently that's not the dynamic library that gnucash finds. > > As I've said, I am clueless about dynamic libraries, particularly on > OS X. > > I'm running OS X 10.5.1 with Xcode 3.0 on a G5 PPC. > > I have also installed the update to X11 from Macosforge. > > Cheers, > > -j > > > > -- > Jeffrey Goldberg http://www.goldmark.org/jeff/ Seems to me that's x11 that's complaining about the version of libffi. Before 2.2, gnucash used g-wrap to to handle some functions, and g- wrap brought in a rather ancient version of libffi. gnucash has since switched to swig for the functions formerly handled by g-wrap, and you don't even need swig if you are building gnucash from a tarball. While I don't know anything else about your system, you might try removing g-wrap, or whatever else is supplying libffi in macports, and see if xquartz will then use the Leopard-provided /usr/lib/libffi.dylib. I use that other packaging system, so I can't swear what needs to be in place, but I don't have any libffi except /usr/lib/libffi.dylib, and gnucash works for me on an almost identical system. Dave From peter at pogma.com Sun Feb 3 22:52:50 2008 From: peter at pogma.com (Peter O'Gorman) Date: Sun Feb 3 22:52:33 2008 Subject: gnucash linking wrong libffi.dylib In-Reply-To: References: Message-ID: On 3-Feb-08, at 11:27 PM, David Reiser wrote: > > On Feb 3, 2008, at 5:21 PM, Jeffrey Goldberg wrote: > >> I must confess that I do not even begin to understand prebinding. >> Nor do I know what the OS X analog of the linux ldconfig command >> and configuration is. But I suspect that the answer to my problem >> will lie in those directions. >> >> I've installed gnome/gnucash using macports (that was a bit of a >> trick because of confusion about which guile installation was >> needed. Gnucash configure couldn't find guile16, but I had other >> problems with guile 1.8. I also needed to install "+without_docs" >> because otherwise port tried and failed to install firefox) But I >> did finally get something compiled and installed. >> >> However, it won't run, and this is what I get to standard error. >> >> dyld: Library not loaded: /usr/lib/libffi.dylib >> Referenced from: >> /System/Library/Frameworks/QuartzCore.framework/Versions/A/ >> QuartzCore >> Reason: Incompatible library version: QuartzCore requires version >> 1.0.0 or later, >> but libffi.dylib provides version 0.0.0 >> >> I note that there is a an /opt/local/lib/libffi.dylib installed, >> but apparently that's not the dynamic library that gnucash finds. >> > > Seems to me that's x11 that's complaining about the version of > libffi. Before 2.2, gnucash used g-wrap to to handle some functions, > and g-wrap brought in a rather ancient version of libffi. gnucash > has since switched to swig for the functions formerly handled by g- > wrap, and you don't even need swig if you are building gnucash from > a tarball. > > While I don't know anything else about your system, you might try > removing g-wrap, or whatever else is supplying libffi in macports, > and see if xquartz will then use the Leopard-provided /usr/lib/ > libffi.dylib. > > I use that other packaging system, so I can't swear what needs to be > in place, but I don't have any libffi except /usr/lib/libffi.dylib, > and gnucash works for me on an almost identical system. Hi David, Something is setting DYLD_LIBRARY_PATH. I know that gnucash used to do it, not sure if it still does. The symptoms are that DYLD_LIBRARY_PATH is set to /opt/local/lib so the dynamic linker is finding the version of libffi.dylib there. I am sure that otool -L will confirm that the libffi in /opt/local has compatibility_version 0.0.0. Does gnucash still have a wrapper script that sets DYLD_LIBRARY_PATH? Peter -- Peter O'Gorman http://pogma.com From David.Epstein at warwick.ac.uk Mon Feb 4 00:02:11 2008 From: David.Epstein at warwick.ac.uk (David Epstein) Date: Mon Feb 4 00:01:54 2008 Subject: libtool woes In-Reply-To: References: <4E2EFAA0-4AC4-4767-8EE9-B97286A8EE62@macports.org> <15258474.post@talk.nabble.com> Message-ID: <15263548.post@talk.nabble.com> Paul Beard-2 wrote: > > I am trying this regime: > > sudo port -f uninstall libtool > sudo port -f uninstall apr > sudo port install libtool > sudo port install apr > sudo port clean apache2 > sudo port upgrade apache2 > > port -f overrides any complaints > This worked for me on Mac Os X 10.4.11, MacPorts 1.600. I include the initial response of port, which shows something, I'm not sure what. When I originally tried to install apache2, port made no attempt to install libtool. Isn't this surprising in view of the first line of the log below? So it seems that apache2 does not list its dependencies correctly, which would explain why everything is fine for some users but not for others. Or maybe the problem is that there are different versions of libtool, as mentioned previously in this thread---I'm not sure if this makes sense. Anyway, here is the initial output from Paul Beard's commands: Error: port uninstall failed: Registry error: libtool not registered as installed. ---> Unable to uninstall apr 1.2.11_0, the following ports depend on it: ---> apr-util ---> subversion Warning: Uninstall forced. Proceeding despite dependencies. ---> Deactivating apr 1.2.11_0 ---> Uninstalling apr 1.2.11_0 ---> Fetching libtool ---> Attempting to fetch libtool-1.5.24.tar.gz fromhttp://ftp.gnu.org/gnu/libtool ---> Verifying checksum(s) for libtool ---> Extracting libtool ---> Configuring libtool---> Building libtool with target all ---> Staging libtool into destroot ---> Installing libtool 1.5.24_1 ---> Activating libtool 1.5.24_1---> Cleaning libtool -- View this message in context: http://www.nabble.com/libtool-woes-tp15248567p15263548.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From bubble_dancer at mac.com Mon Feb 4 00:16:16 2008 From: bubble_dancer at mac.com (=?ISO-2022-JP?B?IhskQjszOH0bKEIgGyRCOS9JVxsoQiI=?=) Date: Mon Feb 4 00:15:56 2008 Subject: gnustep-gui failure to build Message-ID: I've tried to build GWorkspace. But, when building gnustep-gui, gcc-mp-4.2 says, "I cannot recognize option '-weak_framework'.". The error message is following: gcc-mp-4.2 -fgnu-runtime -bundle -L/opt/local/lib -flat_namespace -undefined warning -o ./GSCUPS.bundle/./GSCUPS ./obj/GSCUPSPrincipalClass.o ./obj/GSCUPSPageLayout.o ./obj/GSCUPSPrintInfo.o ./obj/GSCUPSPrintOperation.o ./obj/GSCUPSPrintPanel.o ./obj/GSCUPSPrinter.o -L/opt/local/lib -L../../Source/./obj -L/opt/local/GNUstep/System/Library/Libraries/ -lcups -weak_framework Kerberos -framework CoreFoundation -framework Security -lz -lpthread -framework CoreFoundation -lgnustep-gui -lgnustep-base -lobjc -lm gcc-mp-4.2: Kerberos: No such file or directory gcc-mp-4.2: unrecognized option '-weak_framework' gnumake[3]: *** [GSCUPS.bundle/./GSCUPS] Error 1 gnumake[2]: *** [GSCUPS.all.bundle.variables] Error 2 gnumake[1]: *** [internal-all] Error 2 gnumake: *** [internal-all] Error 2 My system is, PowerBook Pro G5 MacOS X 10.5 Leopard(fresh install). From stochashtic at yahoo.ca Mon Feb 4 02:05:35 2008 From: stochashtic at yahoo.ca (Suresh Pillai) Date: Mon Feb 4 02:05:16 2008 Subject: py25-tkinter failing on build In-Reply-To: References: Message-ID: Same error with py25-tkinter as with py25-hashlib: ---> Building py25-tkinter with target build 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-tkinter/work/Python-2.5.1/Modules" && /opt/local/bin/python2.5 setup.py build " returned error 1 Command output: running build running build_ext building '_tkinter' extension creating build creating build/temp.macosx-10.3-i386-2.5 -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -DWITH_APPINIT=1 -I/opt/local/include -I/opt/local/include/python2.5 -c _tkinter.c -o build/temp.macosx-10.3-i386-2.5/_tkinter.o unable to execute -DNDEBUG: No such file or directory error: command '-DNDEBUG' failed with exit status 1 From darealk at gmail.com Mon Feb 4 02:53:49 2008 From: darealk at gmail.com (realk) Date: Mon Feb 4 02:53:28 2008 Subject: Error while installing Tomcat5 using macports In-Reply-To: <15261125.post@talk.nabble.com> References: <15261125.post@talk.nabble.com> Message-ID: <15265680.post@talk.nabble.com> sandystorm wrote: > > > Dear all, > > Any solution/suggestion/workaround to this issue will be much appreciated > as I am in the midst of a very tight timeline: > > While installing tomcat5 using macports, I get this error. Please find > below the error log: > realk wrote: > > Hello, > > I also got the same problem when trying to install tomcat5 on Leopard OS X > Server with macports. > Please, find enclosed the debug stack. > > Thanks for your help on this, > http://www.nabble.com/file/p15265680/debug_tomcat.txt debug_tomcat.txt -- View this message in context: http://www.nabble.com/Error-while-installing-Tomcat5-using-macports-tp15261125p15265680.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From joh at revier.com Mon Feb 4 03:17:37 2008 From: joh at revier.com (Jochem Huhmann) Date: Mon Feb 4 03:17:20 2008 Subject: libtool and ImageMagick problems Message-ID: <77B5AB3D-116E-4235-B9B6-F23089D57116@revier.com> Hi all, I'm not sure if this is the same problem as in the "libtool woes" thread or not. On both a Tiger system with an existing and upgraded MacPorts system and a Leopard system with freshly installed MacPorts, trying to install ImageMagick results in all ImageMagick tools ending up as libtool-wrappers instead of the actual binaries: $ convert /opt/local/bin/convert: error: `/opt/local/bin/.libs/convert' does not exist This script is just a wrapper for convert. See the libtool documentation for more information. Indeed looking into those scripts seems to indicate that there's some trouble with libtool: $ head /opt/local/bin/convert #! /bin/sh # utilities/convert - temporary wrapper script for .libs/convert # Generated by ltmain.sh (GNU libtool 1.2569 2008/01/24 16:16:26) 2.1a # # The utilities/convert program cannot be directly executed until all the libtool # libraries that it depends on are installed. # # This wrapper script should never be moved out of the build directory. # If it is, it will not operate correctly. Sieving through the build/install output for ImageMagick yields some interesting things. libWand and libMagick have been built, but have not been installed at all: libtool: install: warning: remember to run `libtool --finish /opt/ local/lib' /bin/sh ./libtool --silent --mode=install /usr/bin/install 'utilities/convert' '/opt/local/var/macports/build/ _opt_local_var_macpor