From mark at dxradio.demon.co.uk  Mon Jun  1 03:07:35 2009
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Mon, 1 Jun 2009 11:07:35 +0100 (BST)
Subject: dovecot 1.1.11 vs 1.1.15
In-Reply-To: <B228D38D-94E2-4ED1-ABE0-C7503FEA3387@macports.org>
References: <005B60BC-6E62-48BC-9E4B-56CE6C41B586@dxradio.demon.co.uk>
	<B228D38D-94E2-4ED1-ABE0-C7503FEA3387@macports.org>
Message-ID: <b19e2b37e153ad8eb6524263457fc120.squirrel@dxradio.demon.co.uk>

On Mon, June 1, 2009 06:04, Ryan Schmidt wrote:
>
> On May 31, 2009, at 19:27, Mark Hattam wrote:
>
>> OK ... good to see the version up to date ... only problem is that
>> it doesn't run.
>>
>> Luckily I didn't do the "uninstall inactive" after the "upgrade
>> outdated" which I normally do as a matter of course, so I'm now
>> back on 1.1.11
>>
>> However, even 1.1.11 didn't work again initially.
>>
>> It seemed to lose access to
>> /opt/local/var/run/dovecot/login
>>
>> so I've chmod'd that to 777 and 1.1.11 is now able to work.
>> However, deactivating that and activating 1.1.15 is still "no joy".
>
> Before deactivating 1.1.11, you stop the server process, yes? And
> after activating 1.1.15 you try to start the new one? What error
> message do you get?


The error message I got trying to start 1.1.15 "manually" was that it had permission denied accessing
/opt/local/var/run/dovecot/login

Having chmod'd that to 777, 1.1.11 now runs, and writes its pid in there. But 1.1.15 still can't run. I can't find
where it writes a log, not that it gets far enough to do that.

The machine had several reboots late last night as I was making sure that it had a "clean run". Previous upgrades of
dovecot appear not to have had this type of problem. Initially I was getting port 143 refused from mail clients, so
wasted a fair amount of time re-looking through dovecot's config, the passwd.dovecot file and so on, checking the
dovecot site to ensure that PLAIN was still supported etc etc etc.

I just though it rather strange that the place that it writes its pid file, which clearly used to work, suddenly
became unavailable to it through permissions.

Mark



From tim.visher at gmail.com  Mon Jun  1 07:25:22 2009
From: tim.visher at gmail.com (Tim Visher)
Date: Mon, 1 Jun 2009 10:25:22 -0400
Subject: Using mplayer through Finder
In-Reply-To: <6b32980b0905311505u1f555f0fx7f0cee3504d18fba@mail.gmail.com>
References: <6b32980b0905301212w1ef1e0d9pf1bc603176f7b7e3@mail.gmail.com>
	<6b32980b0905310826nc47c855gf1a7b7b82cd39f2e@mail.gmail.com>
	<2cf4100f0905311451l3e998e49i18eb4caf8d1f0390@mail.gmail.com>
	<6b32980b0905311505u1f555f0fx7f0cee3504d18fba@mail.gmail.com>
Message-ID: <c115fd3c0906010725o2ea3deaao334e99fc296061dd@mail.gmail.com>

Hi Kal,


On Sat, May 30, 2009 at 9:12 PM, Kal <kalounet at gmail.com> wrote:
> I've installed mplayer-svn with MacPorts. However, I can use mplayer
> only through terminal. I can't launch a movie with mplayer when i'm using
> Finder. It's impossible to associate mplayer to an AVI file. Is there a
> trick to get video files associeted with mplyer binary file ?

You've installed the command line version of mplayer and I don't know
of anyway to automatically launch a command line app from the Finder
when you want to open a file.  Possibly cooking up a little
Applescript and compiling it as an app that you can run from the
context menu or from a default handler?

However, despite that there used to be a variant available for the
regular mplayer port that installed MPlayer.app in
/Applications/MacPorts.  IMHO, it was a weaker app at that point but
it did work as a 1st class Mac app so you could select it to open a
file, etc.  I would look into that.

Good luck!

-- 

In Christ,

Timmy V.

http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail

From dluke at geeklair.net  Mon Jun  1 08:04:44 2009
From: dluke at geeklair.net (Daniel J. Luke)
Date: Mon, 1 Jun 2009 11:04:44 -0400
Subject: subversion on 10.4
In-Reply-To: <DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
References: <C7F17FBC-FCE3-4AE0-8990-BF1C9DFFB6E8@free.fr>
	<7FEB6D78-51E7-4E17-9165-ACFF789982E9@macports.org>
	<83E18B9A-23AA-41A3-88EB-7572FC212DFB@free.fr>
	<DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
Message-ID: <A08A027E-523C-40F5-9BC1-71D1FF48F73C@geeklair.net>

On May 31, 2009, at 1:28 AM, Ryan Schmidt wrote:
>>> I know there was a problem compiling 1.6.x while 1.5.x is active.
>>
>> also with 1.4.x
>
> Right, I wouldn't be surprised if the issue exists compiling 1.6.x  
> while any version earlier than 1.6.0 is active, but I have not  
> tested other than the last 1.5.x version.

It's only a problem when the ABI of the installed library is different  
from the ABI of the one that is being built.

So, upgrades work fine for minor versions.

Also, the problem doesn't manifest on 10.5. Since I no longer have a  
10.4 system, it's difficult for me to know what might fix the build  
problem.

If someone with 10.4 can generate a patch (or even just figure out  
what part of the build would need to change, and is willing to test a  
patch), then we can get it fixed.

--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090601/02c385c5/attachment.bin>

From dluke at geeklair.net  Mon Jun  1 08:10:04 2009
From: dluke at geeklair.net (Daniel J. Luke)
Date: Mon, 1 Jun 2009 11:10:04 -0400
Subject: dovecot 1.1.11 vs 1.1.15
In-Reply-To: <b19e2b37e153ad8eb6524263457fc120.squirrel@dxradio.demon.co.uk>
References: <005B60BC-6E62-48BC-9E4B-56CE6C41B586@dxradio.demon.co.uk>
	<B228D38D-94E2-4ED1-ABE0-C7503FEA3387@macports.org>
	<b19e2b37e153ad8eb6524263457fc120.squirrel@dxradio.demon.co.uk>
Message-ID: <FCEDFB12-D0C6-4138-B0A2-DE4A226CCAA4@geeklair.net>

On Jun 1, 2009, at 6:07 AM, Mark Hattam wrote:
> Having chmod'd that to 777, 1.1.11 now runs, and writes its pid in  
> there. But 1.1.15 still can't run. I can't find
> where it writes a log, not that it gets far enough to do that.

http://wiki.dovecot.org/Logging

it should be in /var/log/mail.log by default (but is configurable)

--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090601/107f5422/attachment.bin>

From mark at dxradio.demon.co.uk  Mon Jun  1 15:59:57 2009
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Mon, 1 Jun 2009 23:59:57 +0100
Subject: dovecot 1.1.11 vs 1.1.15
In-Reply-To: <B228D38D-94E2-4ED1-ABE0-C7503FEA3387@macports.org>
References: <005B60BC-6E62-48BC-9E4B-56CE6C41B586@dxradio.demon.co.uk>
	<B228D38D-94E2-4ED1-ABE0-C7503FEA3387@macports.org>
Message-ID: <66687F58-F5B7-4912-8B06-49B299DF577F@dxradio.demon.co.uk>

On 1 Jun 2009, at 06:04, Ryan Schmidt wrote:

>
> On May 31, 2009, at 19:27, Mark Hattam wrote:
>
>> OK ... good to see the version up to date ... only problem is that  
>> it doesn't run.
>>
>> Luckily I didn't do the "uninstall inactive" after the "upgrade  
>> outdated" which I normally do as a matter of course, so I'm now  
>> back on 1.1.11
>>
>> However, even 1.1.11 didn't work again initially.
>>
>> It seemed to lose access to
>> /opt/local/var/run/dovecot/login
>>
>> so I've chmod'd that to 777 and 1.1.11 is now able to work.  
>> However, deactivating that and activating 1.1.15 is still "no joy".
>
> Before deactivating 1.1.11, you stop the server process, yes? And  
> after activating 1.1.15 you try to start the new one? What error  
> message do you get?

Tried again this evening ... deactivated 1.1.11 ... restarted  
machine ... activated 1.1.15 ... restarted machine ... 1.1.15 doesn't  
run ... deactivated 1.1.15 ... restarted machine ... activated  
1.1.11 ... doesn't run but gives permissions error ... chmod the  
folder ... restart machine ... 1.1.11 runs (and is what I'm using now)

Last login: Mon Jun  1 23:37:05 on console

iMac:~ mark$ ps -ef | grep dovecot
   501   202   192   0   0:00.00 ttys000    0:00.00 grep dovecot

iMac:~ mark$ sudo port activate dovecot @1.1.15_0+darwin_9
Password:
--->  Activating dovecot @1.1.15_0+darwin_9

iMac:~ mark$ ps -ef | grep dove
   501   221   192   0   0:00.00 ttys000    0:00.00 grep dove

iMac:~ mark$ dovecot -n
# 1.1.15: /opt/local/etc/dovecot/dovecot.conf
Warning: fd limit 256 is lower than what Dovecot can use under full  
load (more than 640). Either grow the limit or change  
login_max_processes_count and max_mail_processes settings
# OS: Darwin 9.7.0 i386
ssl_disable: yes
disable_plaintext_auth: no
login_dir: /opt/local/var/run/dovecot/login
login_executable: /opt/local/libexec/dovecot/imap-login
mail_location: maildir:~/Maildir
auth default:
   passdb:
     driver: passwd-file
     args: /etc/passwd.dovecot
   passdb:
     driver: pam
   userdb:
     driver: passwd

iMac:~ mark$ ps -ef | grep dovecot
   501   224   192   0   0:00.00 ttys000    0:00.00 grep dovecot

iMac:~ mark$ sudo port activate dovecot @1.1.11_0+darwin_9
--->  Activating dovecot @1.1.11_0+darwin_9

iMac:~ mark$ dovecot -n
# 1.1.11: /opt/local/etc/dovecot/dovecot.conf
Warning: fd limit 256 is lower than what Dovecot can use under full  
load (more than 640). Either grow the limit or change  
login_max_processes_count and max_mail_processes settings
# OS: Darwin 9.7.0 i386
ssl_disable: yes
disable_plaintext_auth: no
login_dir: /opt/local/var/run/dovecot/login
login_executable: /opt/local/libexec/dovecot/imap-login
mail_location: maildir:~/Maildir
auth default:
   passdb:
     driver: passwd-file
     args: /etc/passwd.dovecot
   passdb:
     driver: pam
   userdb:
     driver: passwd

iMac:~ mark$ dovecot
Fatal: open() failed for /opt/local/var/run/dovecot/login: Permission  
denied

iMac:~ mark$ ps -ef | grep dovecot
     0    53     1   0   0:00.00 ??         0:00.00 /opt/local/bin/ 
daemondo --label=dovecot --start-cmd /opt/local/sbin/dovecot ; -- 
pid=fileauto --pidfile /opt/local/var/run/dovecot/master.pid
     0   102     1   0   0:00.00 ??         0:00.00 /opt/local/sbin/ 
dovecot
     0   105   102   0   0:00.00 ??         0:00.00 dovecot-auth
     0   111   102   0   0:00.00 ??         0:00.00 dovecot-auth -w
   501   187   176   0   0:00.00 ttys000    0:00.00 grep dovecot



On 1 Jun 2009, at 16:10, Daniel J. Luke wrote:

> On Jun 1, 2009, at 6:07 AM, Mark Hattam wrote:
>> Having chmod'd that to 777, 1.1.11 now runs, and writes its pid in  
>> there. But 1.1.15 still can't run. I can't find
>> where it writes a log, not that it gets far enough to do that.
>
> http://wiki.dovecot.org/Logging
>
> it should be in /var/log/mail.log by default (but is configurable)
>
> --
> Daniel J. Luke

Yes, they're there ... but it doesn't write anything when it can't run.

1.1.15 doesn't even get as far as the equivalent of

Jun  1 23:47:56 iMac dovecot[102]: dovecot v1.1.11 starting up (core  
dumps disabled)

From brad at pixilla.com  Mon Jun  1 17:43:12 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Mon, 1 Jun 2009 17:43:12 -0700
Subject: port mask
Message-ID: <75FB8909-E274-4952-B730-990317907071@pixilla.com>

Gentoo has package masking to stop their package manager from working  
with certain packages and/or versions.

/etc/portage/package.mask:
 >=devel/openssl-1.0

Is there a way to have port ignore ports/versions?

//Brad


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090601/20afb188/attachment.html>

From raimue at macports.org  Mon Jun  1 18:01:39 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Tue, 02 Jun 2009 03:01:39 +0200
Subject: port mask
In-Reply-To: <75FB8909-E274-4952-B730-990317907071@pixilla.com>
References: <75FB8909-E274-4952-B730-990317907071@pixilla.com>
Message-ID: <4A2479F3.2060706@macports.org>

On 2009-06-02 02:43, Bradley Giesbrecht wrote:
> Gentoo has package masking to stop their package manager from working
> with certain packages and/or versions.
> 
> /etc/portage/package.mask:
>>=devel/openssl-1.0
> 
> Is there a way to have port ignore ports/versions?

MacPorts does only provide and handle one version per port. So to stop
some port from upgrading, you could put the older version into a local
ports tree which takes precedence over the official one. port(1) will
only operate on the first matching port.

http://guide.macports.org/#development.local-repositories
http://trac.macports.org/wiki/howto/InstallingOlderPort

But as we do not track version numbers in dependencies, you would have
to watch out for build errors if ABI changes occur in the library or
other incompatibilities with older versions are introduced.

Rainer

From jberry at macports.org  Mon Jun  1 20:21:12 2009
From: jberry at macports.org (James Berry)
Date: Mon, 1 Jun 2009 20:21:12 -0700
Subject: dovecot 1.1.11 vs 1.1.15
In-Reply-To: <66687F58-F5B7-4912-8B06-49B299DF577F@dxradio.demon.co.uk>
References: <005B60BC-6E62-48BC-9E4B-56CE6C41B586@dxradio.demon.co.uk>
	<B228D38D-94E2-4ED1-ABE0-C7503FEA3387@macports.org>
	<66687F58-F5B7-4912-8B06-49B299DF577F@dxradio.demon.co.uk>
Message-ID: <5542C849-BD64-48BD-AACE-F4546EB4F3ED@macports.org>

Hi Mark,

I just wanted to let you know that I've seen your reports and am  
shaking my head a bit, as I also ran the dovecot update. In my case, I  
had no problem. Is your dovecot user and group installed successfully?

	dscl . -read /users/dovecot; dscl . -read /groups/dovecot

1.1.16 was just released today, and I'll be updating the port to that  
soon, but as far as I know it didn't fix anything on the order of what  
you describe.

James (dovecot mainainer)


On Jun 1, 2009, at 3:59 PM, Mark Hattam wrote:

> On 1 Jun 2009, at 06:04, Ryan Schmidt wrote:
>
>>
>> On May 31, 2009, at 19:27, Mark Hattam wrote:
>>
>>> OK ... good to see the version up to date ... only problem is that  
>>> it doesn't run.
>>>
>>> Luckily I didn't do the "uninstall inactive" after the "upgrade  
>>> outdated" which I normally do as a matter of course, so I'm now  
>>> back on 1.1.11
>>>
>>> However, even 1.1.11 didn't work again initially.
>>>
>>> It seemed to lose access to
>>> /opt/local/var/run/dovecot/login
>>>
>>> so I've chmod'd that to 777 and 1.1.11 is now able to work.  
>>> However, deactivating that and activating 1.1.15 is still "no joy".
>>
>> Before deactivating 1.1.11, you stop the server process, yes? And  
>> after activating 1.1.15 you try to start the new one? What error  
>> message do you get?
>
> Tried again this evening ... deactivated 1.1.11 ... restarted  
> machine ... activated 1.1.15 ... restarted machine ... 1.1.15  
> doesn't run ... deactivated 1.1.15 ... restarted machine ...  
> activated 1.1.11 ... doesn't run but gives permissions error ...  
> chmod the folder ... restart machine ... 1.1.11 runs (and is what  
> I'm using now)
>
> Last login: Mon Jun  1 23:37:05 on console
>
> iMac:~ mark$ ps -ef | grep dovecot
>  501   202   192   0   0:00.00 ttys000    0:00.00 grep dovecot
>
> iMac:~ mark$ sudo port activate dovecot @1.1.15_0+darwin_9
> Password:
> --->  Activating dovecot @1.1.15_0+darwin_9
>
> iMac:~ mark$ ps -ef | grep dove
>  501   221   192   0   0:00.00 ttys000    0:00.00 grep dove
>
> iMac:~ mark$ dovecot -n
> # 1.1.15: /opt/local/etc/dovecot/dovecot.conf
> Warning: fd limit 256 is lower than what Dovecot can use under full  
> load (more than 640). Either grow the limit or change  
> login_max_processes_count and max_mail_processes settings
> # OS: Darwin 9.7.0 i386
> ssl_disable: yes
> disable_plaintext_auth: no
> login_dir: /opt/local/var/run/dovecot/login
> login_executable: /opt/local/libexec/dovecot/imap-login
> mail_location: maildir:~/Maildir
> auth default:
>  passdb:
>    driver: passwd-file
>    args: /etc/passwd.dovecot
>  passdb:
>    driver: pam
>  userdb:
>    driver: passwd
>
> iMac:~ mark$ ps -ef | grep dovecot
>  501   224   192   0   0:00.00 ttys000    0:00.00 grep dovecot
>
> iMac:~ mark$ sudo port activate dovecot @1.1.11_0+darwin_9
> --->  Activating dovecot @1.1.11_0+darwin_9
>
> iMac:~ mark$ dovecot -n
> # 1.1.11: /opt/local/etc/dovecot/dovecot.conf
> Warning: fd limit 256 is lower than what Dovecot can use under full  
> load (more than 640). Either grow the limit or change  
> login_max_processes_count and max_mail_processes settings
> # OS: Darwin 9.7.0 i386
> ssl_disable: yes
> disable_plaintext_auth: no
> login_dir: /opt/local/var/run/dovecot/login
> login_executable: /opt/local/libexec/dovecot/imap-login
> mail_location: maildir:~/Maildir
> auth default:
>  passdb:
>    driver: passwd-file
>    args: /etc/passwd.dovecot
>  passdb:
>    driver: pam
>  userdb:
>    driver: passwd
>
> iMac:~ mark$ dovecot
> Fatal: open() failed for /opt/local/var/run/dovecot/login:  
> Permission denied
>
> iMac:~ mark$ ps -ef | grep dovecot
>    0    53     1   0   0:00.00 ??         0:00.00 /opt/local/bin/ 
> daemondo --label=dovecot --start-cmd /opt/local/sbin/dovecot ; -- 
> pid=fileauto --pidfile /opt/local/var/run/dovecot/master.pid
>    0   102     1   0   0:00.00 ??         0:00.00 /opt/local/sbin/ 
> dovecot
>    0   105   102   0   0:00.00 ??         0:00.00 dovecot-auth
>    0   111   102   0   0:00.00 ??         0:00.00 dovecot-auth -w
>  501   187   176   0   0:00.00 ttys000    0:00.00 grep dovecot
>
>
>
> On 1 Jun 2009, at 16:10, Daniel J. Luke wrote:
>
>> On Jun 1, 2009, at 6:07 AM, Mark Hattam wrote:
>>> Having chmod'd that to 777, 1.1.11 now runs, and writes its pid in  
>>> there. But 1.1.15 still can't run. I can't find
>>> where it writes a log, not that it gets far enough to do that.
>>
>> http://wiki.dovecot.org/Logging
>>
>> it should be in /var/log/mail.log by default (but is configurable)
>>
>> --
>> Daniel J. Luke
>
> Yes, they're there ... but it doesn't write anything when it can't  
> run.
>
> 1.1.15 doesn't even get as far as the equivalent of
>
> Jun  1 23:47:56 iMac dovecot[102]: dovecot v1.1.11 starting up (core  
> dumps disabled)
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From m.c.crockett at roadrunner.com  Mon Jun  1 20:59:49 2009
From: m.c.crockett at roadrunner.com (Merton Campbell Crockett)
Date: Mon, 1 Jun 2009 20:59:49 -0700
Subject: Wireshark Build Problems
In-Reply-To: <4625B781-2631-403C-B288-0EE755638A5E@macports.org>
References: <7A22F928-06D7-4A6D-A134-D43DDC766AAD@roadrunner.com>
	<8c242c590905311421u472379cu5b814aae864bf7cf@mail.gmail.com>
	<4625B781-2631-403C-B288-0EE755638A5E@macports.org>
Message-ID: <6636DE0B-D27A-4227-ACD7-944B5C42F1F0@roadrunner.com>


On 31 May 2009, at 14:27:29, Jeremy Huddleston wrote:

> The error is 'renderproto', not randr.  You seem to not have the  
> xorg-renderproto port active.
>
> gtk2 depends on xorg-libXrandr which depends on xrender which  
> depends on xorg-renderproto


Would this mean that the Wireshark has a sequence error in its  
"install" script?

All of the above are currently installed after letting the install run  
to completion.


> On May 31, 2009, at 14:21, Harry van der Wolf wrote:
>
>> What if you install: xorg-libXrandr and/or xorg-randrproto and/or  
>> xrandr?
>>
>> like "sudo port install xorg-libXrandr xorg-randrproto xrandr"
>>
>> It's just a guess from my side
>>
>>
>> Harry
>>
>> 2009/5/31 Merton Campbell Crockett <m.c.crockett at roadrunner.com>
>>
>>>
>>> I've attempted to upgrade Wireshark to the latest version but keep  
>>> running
>>> into the following problem.  Does anyone know why this is occurring?
>>>
>>>
>>> checking for RANDR... configure: error: Package requirements (x11
>>> randrproto >= 1.3 xext xextproto xrender renderproto) were not met:
>>>
>>> No package 'renderproto' found
>>>
>>> Consider adjusting the PKG_CONFIG_PATH environment variable if you
>>> installed software in a non-standard prefix.
>>>
>>> Alternatively, you may set the environment variables RANDR_CFLAGS
>>> and RANDR_LIBS to avoid the need to call pkg-config.
>>> See the pkg-config man page for more details.
>>>
>>>
>>> Error: The following dependencies failed to build: gtk2 xorg- 
>>> libXrandr
>>> Error: Status 1 encountered during processing.
>>>
>>>
>>>
>>>
>>> Merton Campbell Crockett
>>> m.c.crockett at roadrunner.com
>>>
>>>
>>>
>>> _______________________________________________
>>> macports-users mailing list
>>> macports-users at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>

Merton Campbell Crockett
m.c.crockett at roadrunner.com




From ryandesign at macports.org  Tue Jun  2 02:59:46 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 2 Jun 2009 04:59:46 -0500
Subject: gnutls-devel?
In-Reply-To: <2B85F9C5-0498-4AEB-B84A-1239C149954E@macports.org>
References: <200905290644.21821.jsimmons@goblin.punk.net>
	<200905311054.06015.jsimmons@goblin.punk.net>
	<DD475B21-0FE1-48C5-BE6B-B6392749FEBE@macports.org>
	<200905311313.22777.jsimmons@goblin.punk.net>
	<2B85F9C5-0498-4AEB-B84A-1239C149954E@macports.org>
Message-ID: <73EB5B3E-296E-4848-904B-8CFB62395B62@macports.org>

On Jun 1, 2009, at 00:27, Ryan Schmidt wrote:

> On May 31, 2009, at 15:13, Jeff Simmons wrote:
>
>>> What is the software you're trying to build again, and why are you
>>> not trying to install it using MacPorts?
>>
>> This has got to be some kind of source code bug in OpenVAS.
>
> Perhaps they have never tried to compile on a Mac before.
>
> Which part of OpenVAS are you interested in? There seem to be  
> several parts. I was able to create a MacPorts port for openvas- 
> client without difficulty and could commit it for you if that's the  
> part you wanted. I'm having more difficulty with openvas-libraries  
> though, which are required for openvas-server. I will try to report  
> the problems I encountered to the developers of OpenVAS.

I was able to build ports for openvas-client, openvas-libnasl,  
openvas-libraries and openvas-server. They build for me on Mac OS X  
10.4 Intel. I just committed them so they should be available to you  
within the hour. I didn't test them, except to verify that openvas- 
client opens, because I don't know the software.

Is this what you need? Can you try these ports and let me know if  
they work for you?



From dluke at geeklair.net  Tue Jun  2 07:49:11 2009
From: dluke at geeklair.net (Daniel J. Luke)
Date: Tue, 2 Jun 2009 10:49:11 -0400
Subject: dovecot 1.1.11 vs 1.1.15
In-Reply-To: <66687F58-F5B7-4912-8B06-49B299DF577F@dxradio.demon.co.uk>
References: <005B60BC-6E62-48BC-9E4B-56CE6C41B586@dxradio.demon.co.uk>
	<B228D38D-94E2-4ED1-ABE0-C7503FEA3387@macports.org>
	<66687F58-F5B7-4912-8B06-49B299DF577F@dxradio.demon.co.uk>
Message-ID: <757AD72A-FF3D-4DEB-AE2F-0B94EC1E27A8@geeklair.net>

On Jun 1, 2009, at 6:59 PM, Mark Hattam wrote:
> iMac:~ mark$ dovecot -n
> # 1.1.15: /opt/local/etc/dovecot/dovecot.conf
> Warning: fd limit 256 is lower than what Dovecot can use under full  
> load (more than 640). Either grow the limit or change  
> login_max_processes_count and max_mail_processes settings

you'll probably want to do something about this at some point, but it  
won't be causing dovecot not to run.

> iMac:~ mark$ dovecot
> Fatal: open() failed for /opt/local/var/run/dovecot/login:  
> Permission denied

You need to start dovecot as root.

Try unloading the launchd plist for dovecot, and then running

`sudo dovecot -F`

and see if it spits anything out to your terminal or the log.
--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090602/07f51366/attachment.bin>

From jsimmons at goblin.punk.net  Tue Jun  2 07:55:09 2009
From: jsimmons at goblin.punk.net (Jeff Simmons)
Date: Tue, 2 Jun 2009 07:55:09 -0700
Subject: gnutls-devel?
In-Reply-To: <73EB5B3E-296E-4848-904B-8CFB62395B62@macports.org>
References: <200905290644.21821.jsimmons@goblin.punk.net>
	<2B85F9C5-0498-4AEB-B84A-1239C149954E@macports.org>
	<73EB5B3E-296E-4848-904B-8CFB62395B62@macports.org>
Message-ID: <200906020755.09521.jsimmons@goblin.punk.net>

On Tuesday 02 June 2009 02:59, Ryan Schmidt wrote:
> On Jun 1, 2009, at 00:27, Ryan Schmidt wrote:
> > On May 31, 2009, at 15:13, Jeff Simmons wrote:
> >>> What is the software you're trying to build again, and why are you
> >>> not trying to install it using MacPorts?
> >>
> >> This has got to be some kind of source code bug in OpenVAS.
> >
> > Perhaps they have never tried to compile on a Mac before.
> >
> > Which part of OpenVAS are you interested in? There seem to be
> > several parts. I was able to create a MacPorts port for openvas-
> > client without difficulty and could commit it for you if that's the
> > part you wanted. I'm having more difficulty with openvas-libraries
> > though, which are required for openvas-server. I will try to report
> > the problems I encountered to the developers of OpenVAS.
>
> I was able to build ports for openvas-client, openvas-libnasl,
> openvas-libraries and openvas-server. They build for me on Mac OS X
> 10.4 Intel. I just committed them so they should be available to you
> within the hour. I didn't test them, except to verify that openvas-
> client opens, because I don't know the software.
>
> Is this what you need? Can you try these ports and let me know if
> they work for you?

openvas-libraries, openvas-libnasl, and openvas-server all build fine. 
openvas-client stops here:

--->  Attempting to fetch tiff-3.8.2.tar.gz from 
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/
--->  Verifying checksum(s) for tiff
--->  Extracting tiff
On Mac OS X 10.5, tiff 3.8.2 requires Xcode 3.1 or later but you have  
Xcode 3.0.
Error: Target org.macports.extract returned: incompatible Xcode version
Error: The following dependencies failed to build: gtk2 tiff xorg- 
libXcomposite xorg-compositeproto xorg-libXext xorg-libXfixes xorg- 
fixesproto xorg-libXcursor xorg-libXdamage xorg-damageproto xorg-libXi  
xorg-libXinerama xorg-xineramaproto xorg-libXrandr xorg-randrproto
Error: Status 1 encountered during processing.

There's another package, openvas-plugins, that contains the actual 
vulnerability tests. It shouldn't be necessary to the port, since openvas has 
an update-plugins script that fetches them via rsync, but I haven't tested it 
on an empty plugins installation yet.

BTW many thanks. It's pretty incredible (to me anyway) that you would put a 
port like this together so quickly.

-- 
Jeff Simmons                                   jsimmons at goblin.punk.net
Simmons Consulting - Network Engineering, Administration, Security
"You guys, I don't hear any noise.  Are you sure you're doing it right?"
        --  My Life With The Thrill Kill Kult

From brad at pixilla.com  Tue Jun  2 09:28:47 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Tue, 2 Jun 2009 09:28:47 -0700
Subject: dovecot 1.1.11 vs 1.1.15
In-Reply-To: <757AD72A-FF3D-4DEB-AE2F-0B94EC1E27A8@geeklair.net>
References: <005B60BC-6E62-48BC-9E4B-56CE6C41B586@dxradio.demon.co.uk>
	<B228D38D-94E2-4ED1-ABE0-C7503FEA3387@macports.org>
	<66687F58-F5B7-4912-8B06-49B299DF577F@dxradio.demon.co.uk>
	<757AD72A-FF3D-4DEB-AE2F-0B94EC1E27A8@geeklair.net>
Message-ID: <3F6A4117-1E7C-4AD5-A76F-382BD3A3FBB3@pixilla.com>


On Jun 2, 2009, at 7:49 AM, Daniel J. Luke wrote:

> On Jun 1, 2009, at 6:59 PM, Mark Hattam wrote:
>> iMac:~ mark$ dovecot -n
>> # 1.1.15: /opt/local/etc/dovecot/dovecot.conf
>> Warning: fd limit 256 is lower than what Dovecot can use under full  
>> load (more than 640). Either grow the limit or change  
>> login_max_processes_count and max_mail_processes settings
>
> you'll probably want to do something about this at some point, but  
> it won't be causing dovecot not to run.

As of some version of Leopard you no longer use /etc/sysctl.conf or  
ulimit.

You use launchd.

To make them survive reboots add them to /etc/launchd.conf

Here is mine:
bash-3.2# cat /etc/launchd.conf
limit maxfiles 4096 unlimited
limit maxproc 2048 unlimited

This will squash the dovecot warning.

//Brad

>> iMac:~ mark$ dovecot
>> Fatal: open() failed for /opt/local/var/run/dovecot/login:  
>> Permission denied
>
> You need to start dovecot as root.
>
> Try unloading the launchd plist for dovecot, and then running
>
> `sudo dovecot -F`
>
> and see if it spits anything out to your terminal or the log.
> --
> Daniel J. Luke
> +========================================================+
> | *---------------- dluke at geeklair.net ----------------* |
> | *-------------- http://www.geeklair.net -------------* |
> +========================================================+
> |   Opinions expressed are mine and do not necessarily   |
> |          reflect the opinions of my employer.          |
> +========================================================+
>
>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From ryandesign at macports.org  Tue Jun  2 11:33:43 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 2 Jun 2009 13:33:43 -0500
Subject: gnutls-devel?
In-Reply-To: <200906020755.09521.jsimmons@goblin.punk.net>
References: <200905290644.21821.jsimmons@goblin.punk.net>
	<2B85F9C5-0498-4AEB-B84A-1239C149954E@macports.org>
	<73EB5B3E-296E-4848-904B-8CFB62395B62@macports.org>
	<200906020755.09521.jsimmons@goblin.punk.net>
Message-ID: <471172AF-4776-4CF2-ACEE-8678C95C073A@macports.org>

On Jun 2, 2009, at 09:55, Jeff Simmons wrote:

> On Tuesday 02 June 2009 02:59, Ryan Schmidt wrote:
>> On Jun 1, 2009, at 00:27, Ryan Schmidt wrote:
>>> On May 31, 2009, at 15:13, Jeff Simmons wrote:
>>>>> What is the software you're trying to build again, and why are you
>>>>> not trying to install it using MacPorts?
>>>>
>>>> This has got to be some kind of source code bug in OpenVAS.
>>>
>>> Perhaps they have never tried to compile on a Mac before.
>>>
>>> Which part of OpenVAS are you interested in? There seem to be
>>> several parts. I was able to create a MacPorts port for openvas-
>>> client without difficulty and could commit it for you if that's the
>>> part you wanted. I'm having more difficulty with openvas-libraries
>>> though, which are required for openvas-server. I will try to report
>>> the problems I encountered to the developers of OpenVAS.
>>
>> I was able to build ports for openvas-client, openvas-libnasl,
>> openvas-libraries and openvas-server. They build for me on Mac OS X
>> 10.4 Intel. I just committed them so they should be available to you
>> within the hour. I didn't test them, except to verify that openvas-
>> client opens, because I don't know the software.
>>
>> Is this what you need? Can you try these ports and let me know if
>> they work for you?
>
> openvas-libraries, openvas-libnasl, and openvas-server all build fine.
> openvas-client stops here:
>
> --->  Attempting to fetch tiff-3.8.2.tar.gz from
> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/
> --->  Verifying checksum(s) for tiff
> --->  Extracting tiff
> On Mac OS X 10.5, tiff 3.8.2 requires Xcode 3.1 or later but you have
> Xcode 3.0.

Read the above message again. :)

You can get Xcode 3.1 here:

http://developer.apple.com/technology/xcode.html


> Error: Target org.macports.extract returned: incompatible Xcode  
> version
> Error: The following dependencies failed to build: gtk2 tiff xorg-
> libXcomposite xorg-compositeproto xorg-libXext xorg-libXfixes xorg-
> fixesproto xorg-libXcursor xorg-libXdamage xorg-damageproto xorg-libXi
> xorg-libXinerama xorg-xineramaproto xorg-libXrandr xorg-randrproto
> Error: Status 1 encountered during processing.
>
> There's another package, openvas-plugins, that contains the actual
> vulnerability tests. It shouldn't be necessary to the port, since  
> openvas has
> an update-plugins script that fetches them via rsync, but I haven't  
> tested it
> on an empty plugins installation yet.

I forgot about plugins. I'll see if I can make a port for them too.

> BTW many thanks. It's pretty incredible (to me anyway) that you  
> would put a
> port like this together so quickly.

You're welcome, I hope it works for you. As you've found, compiling  
software with dependencies by hand can get hairy, and that's the  
whole reason we have MacPorts: so only one person has to figure out  
how to compile a given program for Mac OS X, and then encode that  
knowledge into a portfile. Some of the openvas parts needed a little  
help compiling on Mac OS X or within MacPorts and I will send those  
patches back to the developers shortly.


From macports at festus.festusandsimone.org  Tue Jun  2 13:31:00 2009
From: macports at festus.festusandsimone.org (John J. Foster)
Date: Tue, 02 Jun 2009 14:31:00 -0600
Subject: Ability to run Anacron as a user
Message-ID: <1243974660.30649.1318448355@webmail.messagingengine.com>

Good afternoon,

I've got a TrueCrypt volume that I would like to rsync changes to over
an SSH connection daily. I've set up a script that works fine for me
from the command line. However, I can't get this to work with anacron
because I do not have, and do not want to put,  roots ssh public key on
the remote server. I tried to configure the anacrontab file to use su to
accomplish this, but it looks like my local user does not have write
capability to the anacron spool directory. Digging online shows that it
is possible with some versions on anacron to run it under users
credentials and to use the command line option -S to specify a different
spool, ideally in $HOME. But this option isn't available in macports
anacron. Does anyone have any ideas here?

Thanks,
festus

From talklists at newgeo.com  Tue Jun  2 13:47:51 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Tue, 2 Jun 2009 13:47:51 -0700
Subject: Ability to run Anacron as a user
In-Reply-To: <1243974660.30649.1318448355@webmail.messagingengine.com>
References: <1243974660.30649.1318448355@webmail.messagingengine.com>
Message-ID: <434B8A0E-10ED-4289-8972-59D32EB4A12F@newgeo.com>

On Jun 2, 2009, at 1:31 PM, John J. Foster wrote:

> I've got a TrueCrypt volume that I would like to rsync changes to over
> an SSH connection daily. I've set up a script that works fine for me
> from the command line. However, I can't get this to work with anacron
> because I do not have, and do not want to put,  roots ssh public key  
> on
> the remote server. I tried to configure the anacrontab file to use  
> su to
> accomplish this, but it looks like my local user does not have write
> capability to the anacron spool directory. Digging online shows that  
> it
> is possible with some versions on anacron to run it under users
> credentials and to use the command line option -S to specify a  
> different
> spool, ideally in $HOME. But this option isn't available in macports
> anacron. Does anyone have any ideas here?


Perhaps you may want to ditch anacron, and look into launchd?  Lingon  
can be used, I believe, in the same way to shied you from the  
intricacies of OS X scheduling.

If you are able to run interactively your rsync script, which I assume  
asks you for a password to login, then anacron, or launchd are both  
going to need keys on the server no matter what.

Somewhere, you have to have the keys to do a passwordless login.  If  
your machine is compromised, you can always revoke the keys quickly.   
Reading a little about anacron, I can not see there being anything  
launchd can not do, and much more.

Curious also, make sure you use rsync correctly, if you are syncing  
mac files, there are special flags you need to add in order to not  
nuke your Mac OS X resource/data forks, thereby breaking your files  
and having an incomplete backup.

Hope this is a little helpful, not entirely the answer you were after,  
but something I think in the end you will be more happy with.
-- 
Scott * If you contact me off list replace talklists@ with scott@ *


From jsimmons at goblin.punk.net  Tue Jun  2 14:48:10 2009
From: jsimmons at goblin.punk.net (Jeff Simmons)
Date: Tue, 2 Jun 2009 14:48:10 -0700
Subject: gnutls-devel?
In-Reply-To: <471172AF-4776-4CF2-ACEE-8678C95C073A@macports.org>
References: <200905290644.21821.jsimmons@goblin.punk.net>
	<200906020755.09521.jsimmons@goblin.punk.net>
	<471172AF-4776-4CF2-ACEE-8678C95C073A@macports.org>
Message-ID: <200906021448.10678.jsimmons@goblin.punk.net>

On Tuesday 02 June 2009 11:33, Ryan Schmidt wrote:
> > On Mac OS X 10.5, tiff 3.8.2 requires Xcode 3.1 or later but you have
> > Xcode 3.0.
>
> Read the above message again. :)
>
> You can get Xcode 3.1 here:
>
> http://developer.apple.com/technology/xcode.html

Yeah, I know. Just wanted to let you know, since I'm using a fairly new Mac, 
and loaded Xcode straight from the CD. And 3.1 does take a while to download.

And as long as I'm taking advantage of you ...

There's a message that comes up somewhere during the compile process that 
openvas works much better with about 100 bpf devices (Berkeley Packet Filter, 
/dev/bpf*). There's four in there now, do you know if it's safe for me to 
just create 96 more using mknod? Or even better, is there the equivalent of 
the bsd MAKEDEV script hiding somewhere I haven't been able to find it?

-- 
Jeff Simmons                                   jsimmons at goblin.punk.net
Simmons Consulting - Network Engineering, Administration, Security
"You guys, I don't hear any noise.  Are you sure you're doing it right?"
        --  My Life With The Thrill Kill Kult

From ryandesign at macports.org  Tue Jun  2 15:22:24 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 2 Jun 2009 17:22:24 -0500
Subject: gnutls-devel?
In-Reply-To: <200906021448.10678.jsimmons@goblin.punk.net>
References: <200905290644.21821.jsimmons@goblin.punk.net>
	<200906020755.09521.jsimmons@goblin.punk.net>
	<471172AF-4776-4CF2-ACEE-8678C95C073A@macports.org>
	<200906021448.10678.jsimmons@goblin.punk.net>
Message-ID: <8EDDD55D-BD7C-4A6F-8CF4-21405FF2FB61@macports.org>


On Jun 2, 2009, at 16:48, Jeff Simmons wrote:

> On Tuesday 02 June 2009 11:33, Ryan Schmidt wrote:
>>> On Mac OS X 10.5, tiff 3.8.2 requires Xcode 3.1 or later but you  
>>> have
>>> Xcode 3.0.
>>
>> Read the above message again. :)
>>
>> You can get Xcode 3.1 here:
>>
>> http://developer.apple.com/technology/xcode.html
>
> Yeah, I know. Just wanted to let you know, since I'm using a fairly  
> new Mac,
> and loaded Xcode straight from the CD. And 3.1 does take a while to  
> download.

Xcode 3.0 had some bugs, which have fortunately been fixed in 3.1. So  
it's not an effective use of our time to engineer workarounds for  
Xcode 3.0 bugs when you could just install Xcode 3.1 and not  
experience the bugs anymore. Therefore I added that message to the  
tiff port to prevent you from running into the Xcode 3.0 problem and  
advise you of how to solve it. :) There are several ports now which  
either emit the same message, or will fail if you try to build them  
with Xcode 3.0. Therefore you would make your life easier by  
installing the latest Xcode.

> And as long as I'm taking advantage of you ...
>
> There's a message that comes up somewhere during the compile  
> process that
> openvas works much better with about 100 bpf devices (Berkeley  
> Packet Filter,
> /dev/bpf*). There's four in there now, do you know if it's safe for  
> me to
> just create 96 more using mknod? Or even better, is there the  
> equivalent of
> the bsd MAKEDEV script hiding somewhere I haven't been able to find  
> it?

I did see that message but I don't know anything about Berkeley  
Packet Filter devices or creating nodes. You might try asking the  
developers of openvas if they have further advice, since they at  
least know something about that feature since they wrote their  
software to use it.




From jsimmons at goblin.punk.net  Tue Jun  2 18:57:24 2009
From: jsimmons at goblin.punk.net (Jeff Simmons)
Date: Tue, 2 Jun 2009 18:57:24 -0700
Subject: gnutls-devel?
In-Reply-To: <8EDDD55D-BD7C-4A6F-8CF4-21405FF2FB61@macports.org>
References: <200905290644.21821.jsimmons@goblin.punk.net>
	<200906021448.10678.jsimmons@goblin.punk.net>
	<8EDDD55D-BD7C-4A6F-8CF4-21405FF2FB61@macports.org>
Message-ID: <200906021857.24847.jsimmons@goblin.punk.net>

On Tuesday 02 June 2009 15:22, Ryan Schmidt wrote:
> Xcode 3.0 had some bugs, which have fortunately been fixed in 3.1. So
> it's not an effective use of our time to engineer workarounds for
> Xcode 3.0 bugs when you could just install Xcode 3.1 and not
> experience the bugs anymore. Therefore I added that message to the
> tiff port to prevent you from running into the Xcode 3.0 problem and
> advise you of how to solve it. :) There are several ports now which
> either emit the same message, or will fail if you try to build them
> with Xcode 3.0. Therefore you would make your life easier by
> installing the latest Xcode.

Ahhh, you're way ahead of me. (Note to self: never doubt the sensei.)

Once 3.1 was installed everything built without errors.

> > And as long as I'm taking advantage of you ...
> >
> > There's a message that comes up somewhere during the compile
> > process that
> > openvas works much better with about 100 bpf devices (Berkeley
> > Packet Filter,
> > /dev/bpf*). There's four in there now, do you know if it's safe for
> > me to
> > just create 96 more using mknod? Or even better, is there the
> > equivalent of
> > the bsd MAKEDEV script hiding somewhere I haven't been able to find
> > it?
>
> I did see that message but I don't know anything about Berkeley
> Packet Filter devices or creating nodes. You might try asking the
> developers of openvas if they have further advice, since they at
> least know something about that feature since they wrote their
> software to use it.

It's an OS question rather than a software question: how many device nodes of 
that particular type can the OS handle? I've got some questions out with 
Apple - I'll pass the results along.

-- 
Jeff Simmons                                   jsimmons at goblin.punk.net
Simmons Consulting - Network Engineering, Administration, Security
"You guys, I don't hear any noise.  Are you sure you're doing it right?"
        --  My Life With The Thrill Kill Kult

From kuraaku.deibiddo at gmail.com  Tue Jun  2 22:39:05 2009
From: kuraaku.deibiddo at gmail.com (David Clark)
Date: Wed, 3 Jun 2009 01:39:05 -0400
Subject: cdparanoia fails to build on PPC
Message-ID: <33531acd0906022239p278e5c95v2417fa7fb2d8d6ac@mail.gmail.com>

I have not tried this on Intel yet, but on PPC, I get the following errors:

Error: Target org.macports.build returned: shell command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_audio_cdparanoia/work/cdparanoia-III-10.2"
&& make all " returned error 2
Command output: 		-o cdparanoia -lcdda_interface -lcdda_paranoia -lm
Undefined symbols:
  "_cdda_version", referenced from:
      _main in main.o
      _main in main.o
      _main in main.o
  "_paranoia_cachemodel_size", referenced from:
      _analyze_cache in cachetest.o
  "_paranoia_version", referenced from:
      _main in main.o
      _main in main.o
      _main in main.o
      _analyze_cache in cachetest.o
  "_cdda_read_timed", referenced from:
      _time_drive in cachetest.o
      _analyze_cache in cachetest.o
      _analyze_cache in cachetest.o
      _analyze_cache in cachetest.o
      _analyze_cache in cachetest.o
      _analyze_cache in cachetest.o
      _analyze_cache in cachetest.o
      _analyze_cache in cachetest.o
      _analyze_cache in cachetest.o
      _analyze_cache in cachetest.o
      _analyze_cache in cachetest.o
      _analyze_cache in cachetest.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[1]: *** [cdparanoia] Error 1
make: *** [all] Error 2

Error: Unable to upgrade port: 1

Hopefully this will help someone track down the error and sort it out.

Thanks in advance,

david

From blb at macports.org  Tue Jun  2 23:58:15 2009
From: blb at macports.org (Bryan Blackburn)
Date: Wed, 3 Jun 2009 00:58:15 -0600
Subject: cdparanoia fails to build on PPC
In-Reply-To: <33531acd0906022239p278e5c95v2417fa7fb2d8d6ac@mail.gmail.com>
References: <33531acd0906022239p278e5c95v2417fa7fb2d8d6ac@mail.gmail.com>
Message-ID: <20090603065815.GC591@ninagal.withay.com>

On Wed, Jun 03, 2009 at 01:39:05AM -0400, David Clark said:
> I have not tried this on Intel yet, but on PPC, I get the following errors:
> 
> Error: Target org.macports.build returned: shell command " cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_audio_cdparanoia/work/cdparanoia-III-10.2"
> && make all " returned error 2
> Command output: 		-o cdparanoia -lcdda_interface -lcdda_paranoia -lm
> Undefined symbols:
>   "_cdda_version", referenced from:
>       _main in main.o

Sounds like #19831:

<http://trac.macports.org/ticket/19831>

Sounds like deactivating the current one and cleaning then installing
cdparanoia should work.

Bryan

[...]
> 
> Hopefully this will help someone track down the error and sort it out.
> 
> Thanks in advance,
> 
> david

From ryandesign at macports.org  Wed Jun  3 01:24:10 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 3 Jun 2009 03:24:10 -0500
Subject: gnutls-devel?
In-Reply-To: <200906021857.24847.jsimmons@goblin.punk.net>
References: <200905290644.21821.jsimmons@goblin.punk.net>
	<200906021448.10678.jsimmons@goblin.punk.net>
	<8EDDD55D-BD7C-4A6F-8CF4-21405FF2FB61@macports.org>
	<200906021857.24847.jsimmons@goblin.punk.net>
Message-ID: <8A81B616-8D3A-411B-B5AB-3C26315FEF66@macports.org>


On Jun 2, 2009, at 20:57, Jeff Simmons wrote:

>>> There's a message that comes up somewhere during the compile
>>> process that
>>> openvas works much better with about 100 bpf devices (Berkeley
>>> Packet Filter,
>>> /dev/bpf*). There's four in there now, do you know if it's safe for
>>> me to
>>> just create 96 more using mknod? Or even better, is there the
>>> equivalent of
>>> the bsd MAKEDEV script hiding somewhere I haven't been able to find
>>> it?
>>
>> I did see that message but I don't know anything about Berkeley
>> Packet Filter devices or creating nodes. You might try asking the
>> developers of openvas if they have further advice, since they at
>> least know something about that feature since they wrote their
>> software to use it.
>
> It's an OS question rather than a software question: how many  
> device nodes of
> that particular type can the OS handle? I've got some questions out  
> with
> Apple - I'll pass the results along.

I just don't know! :)

In the mean time, I added a port for openvas-plugins, so hopefully  
you can have a fully-functional openvas installation now. If anything  
needs to be tweaked in any of the ports, let me know!



From frstan at bellsouth.net  Wed Jun  3 07:20:34 2009
From: frstan at bellsouth.net (William Davis)
Date: Wed, 3 Jun 2009 10:20:34 -0400
Subject: cdparanoia fails to build on PPC
In-Reply-To: <20090603065815.GC591@ninagal.withay.com>
References: <33531acd0906022239p278e5c95v2417fa7fb2d8d6ac@mail.gmail.com>
	<20090603065815.GC591@ninagal.withay.com>
Message-ID: <CA652BF2-82A8-4163-9E09-B57C41ADD89A@bellsouth.net>


On Jun 3, 2009, at 2:58 AM, Bryan Blackburn wrote:

> On Wed, Jun 03, 2009 at 01:39:05AM -0400, David Clark said:
>> I have not tried this on Intel yet, but on PPC, I get the following  
>> errors:
>>
>> Error: Target org.macports.build returned: shell command " cd
>> "/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_audio_cdparanoia/work/cdparanoia- 
>> III-10.2"
>> && make all " returned error 2
>> Command output: 		-o cdparanoia -lcdda_interface -lcdda_paranoia -lm
>> Undefined symbols:
>>  "_cdda_version", referenced from:
>>      _main in main.o
>
> Sounds like #19831:
>
> <http://trac.macports.org/ticket/19831>
>
> Sounds like deactivating the current one and cleaning then installing
> cdparanoia should work.
>
> Bryan
>

This also fixed the same problem on Intel Leopard. Thanks!
WSD


> [...]
>>
>> Hopefully this will help someone track down the error and sort it  
>> out.
>>
>> Thanks in advance,
>>
>> david
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users



William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.3.3.2 (xorg-server 1.4.2-apple42)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From michaeljdur at yahoo.com  Wed Jun  3 07:27:26 2009
From: michaeljdur at yahoo.com (michaeljdur at yahoo.com)
Date: Wed, 3 Jun 2009 07:27:26 -0700 (PDT)
Subject: Pcap running, but no working?
In-Reply-To: <mailman.13.1244037601.68331.macports-users@lists.macosforge.org>
References: <mailman.13.1244037601.68331.macports-users@lists.macosforge.org>
Message-ID: <528654.13830.qm@web52204.mail.re2.yahoo.com>

I installed CDPR and Wireshark via macports via porticus.
When I launch either no interfaces are detected.  
CDPR gives me the message:
"No interfaces found! Make sure pcap is installed."
I've checked and libpcap is installed and running.  
Does anyone have a suggestion?


Thanks, 
Michael

Macbook pro 1.83/4/200/10.5.7


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090603/146d19b6/attachment.html>

From michaeljdur at yahoo.com  Wed Jun  3 07:30:54 2009
From: michaeljdur at yahoo.com (michaeljdur at yahoo.com)
Date: Wed, 3 Jun 2009 07:30:54 -0700 (PDT)
Subject: pcap intalled but not working?
Message-ID: <931668.14533.qm@web52204.mail.re2.yahoo.com>

I installed CDPR and Wireshark via macports via porticus.
When I launch either no interfaces are detected.  
CDPR gives me the message:
"No interfaces found! Make sure pcap is installed."
I've checked and libpcap is installed and running.  
Does anyone have a suggestion?


Thanks, 
Michael

Macbook pro 1.83/4/200/10.5.7



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090603/2bbc9f24/attachment.html>

From bhirt at mobygames.com  Wed Jun  3 07:50:00 2009
From: bhirt at mobygames.com (Brian Hirt)
Date: Wed, 3 Jun 2009 08:50:00 -0600
Subject: mod_perl / rrdtool conflict
Message-ID: <AA80953B-0157-4D10-8225-56B7BB764176@mobygames.com>

I was installing mod_perl and I got this conflict:

--->  Activating mod_perl @1.30_0
Error: Target org.macports.activate returned: Image error: /opt/local/ 
lib/perl5/5.8.9/darwin-2level/perllocal.pod is being used by the  
active rrdtool port.  Please deactivate this port first, or use 'port - 
f activate mod_perl' to force the activation.
Error: The following dependencies failed to build: mod_perl
Error: Status 1 encountered during processing.

Any advice besides forcing the install?

Thanks for the help

Brian

From mark at dxradio.demon.co.uk  Wed Jun  3 09:53:48 2009
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Wed, 3 Jun 2009 17:53:48 +0100
Subject: dovecot 1.1.11 vs 1.1.15 ... 1.1.16 works fine
In-Reply-To: <66687F58-F5B7-4912-8B06-49B299DF577F@dxradio.demon.co.uk>
References: <005B60BC-6E62-48BC-9E4B-56CE6C41B586@dxradio.demon.co.uk>
	<B228D38D-94E2-4ED1-ABE0-C7503FEA3387@macports.org>
	<66687F58-F5B7-4912-8B06-49B299DF577F@dxradio.demon.co.uk>
Message-ID: <8DC20463-BEA8-41F9-99AA-E1BE39451DC9@dxradio.demon.co.uk>


On 1 Jun 2009, at 23:59, Mark Hattam wrote:

> On 1 Jun 2009, at 06:04, Ryan Schmidt wrote:
>
>>
>> On May 31, 2009, at 19:27, Mark Hattam wrote:
>>
>>> OK ... good to see the version up to date ... only problem is that  
>>> it doesn't run.
>>>
>>> Luckily I didn't do the "uninstall inactive" after the "upgrade  
>>> outdated" which I normally do as a matter of course, so I'm now  
>>> back on 1.1.11
>>>
>>> However, even 1.1.11 didn't work again initially.
>>>
>>> It seemed to lose access to
>>> /opt/local/var/run/dovecot/login
>>>
>>> so I've chmod'd that to 777 and 1.1.11 is now able to work.  
>>> However, deactivating that and activating 1.1.15 is still "no joy".
>>
>> Before deactivating 1.1.11, you stop the server process, yes? And  
>> after activating 1.1.15 you try to start the new one? What error  
>> message do you get?
>
> Tried again this evening ... deactivated 1.1.11 ... restarted  
> machine ... activated 1.1.15 ... restarted machine ... 1.1.15  
> doesn't run ... deactivated 1.1.15 ... restarted machine ...  
> activated 1.1.11 ... doesn't run but gives permissions error ...  
> chmod the folder ... restart machine ... 1.1.11 runs (and is what  
> I'm using now)




Thank you's to Ryan, Bradley, James and Daniel for help and suggestions.

I never did get 1.1.15 to work, but the upgrade from 1.1.11 to 1.1.16  
worked fine without any problem.

The only issue to address is the warning dovecot (any version) spits  
out saying

>> iMac:~ mark$ dovecot -n
>> # 1.1.15: /opt/local/etc/dovecot/dovecot.conf
>> Warning: fd limit 256 is lower than what Dovecot can use under full  
>> load (more than 640). Either grow the limit or change  
>> login_max_processes_count and max_mail_processes settings


On 3 Jun 2009, at 01:04, Daniel J. Luke wrote:

> On Jun 2, 2009, at 7:31 PM, Mark Hattam wrote:
>> whatever the fd limit is, it doesn't seem to stop it working. In my  
>> dovecot.conf, it has the default
>> #login_max_processes_count = 128
>> #max_mail_processes = 512
>>
>> So what should I do ... halve them to 64 and 256 ? Or is there  
>> better method of determining what they need to be? Or what/where is  
>> "fd limit" ?
>
>
> It's a limit that the imposed on processes that keeps them from  
> opening too many files (this helps keep certain kinds of program  
> errors from making your computer unusable).
>
> The default on Mac OS X is 256. The defaults for dovecot are too  
> high for this (or the default fd limit is too low - depending on  
> your perspective).
>
> If you never get near the limit, you won't notice any problems, but  
> it's better to fix it as it's a configuration error.
>
> There is some discussion on the dovecot wiki, but for your setup, I  
> would probably just make them very small since you have a small  
> number of users using the server.
>
> --
> Daniel J. Luke

From dluke at geeklair.net  Wed Jun  3 10:03:24 2009
From: dluke at geeklair.net (Daniel J. Luke)
Date: Wed, 3 Jun 2009 13:03:24 -0400
Subject: mod_perl / rrdtool conflict
In-Reply-To: <AA80953B-0157-4D10-8225-56B7BB764176@mobygames.com>
References: <AA80953B-0157-4D10-8225-56B7BB764176@mobygames.com>
Message-ID: <1980254D-DF2E-4F88-ADDE-3D9538AC8D74@geeklair.net>

On Jun 3, 2009, at 10:50 AM, Brian Hirt wrote:
> I was installing mod_perl and I got this conflict:
>
> --->  Activating mod_perl @1.30_0
> Error: Target org.macports.activate returned: Image error: /opt/ 
> local/lib/perl5/5.8.9/darwin-2level/perllocal.pod is being used by  
> the active rrdtool port.  Please deactivate this port first, or use  
> 'port -f activate mod_perl' to force the activation.
> Error: The following dependencies failed to build: mod_perl
> Error: Status 1 encountered during processing.
>
> Any advice besides forcing the install?


Forcing the install should be OK in this case.

Both the mod_perl and rrdtool ports should be updated to not install  
that file.

If you could file a bug report so that the maintainer(s) know that it  
needs to be fixed, that would be great.

[You can reference the ImageMagick and git-core ports as including  
examples of how to fix it]

--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090603/2be76335/attachment.bin>

From bodaro at gmail.com  Wed Jun  3 10:46:41 2009
From: bodaro at gmail.com (Mike Papper)
Date: Wed, 3 Jun 2009 10:46:41 -0700
Subject: port install db46 MD5 Issue
Message-ID: <9fbe0e780906031046w3ae7acb6u3010b89e704dc30d@mail.gmail.com>

I see the following error when installing:

 sudo port install db46
--->  Verifying checksum(s) for db46
Error: Checksum (md5) mismatch for patch.4.6.21.3
Error: Target org.macports.checksum returned: Unable to verify file
checksums
Error: Status 1 encountered during processing.

This is on MacBook running OSX 10.5.6
It is part of me trying to install the RMagic GEM (which needs imagemagic or
graphicsmagic (which is installed)).

Is there a cmd-line option to bypass the MD5 check and/or how do I get the
maintainers to fix this issue?

Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090603/eb5c56bd/attachment.html>

From macports at festus.festusandsimone.org  Wed Jun  3 11:04:54 2009
From: macports at festus.festusandsimone.org (macports at festus.festusandsimone.org)
Date: Wed, 03 Jun 2009 12:04:54 -0600
Subject: Ability to run Anacron as a user
In-Reply-To: <434B8A0E-10ED-4289-8972-59D32EB4A12F@newgeo.com>
References: <1243974660.30649.1318448355@webmail.messagingengine.com>
	<434B8A0E-10ED-4289-8972-59D32EB4A12F@newgeo.com>
Message-ID: <1244052294.11144.1318621949@webmail.messagingengine.com>



On Tue, 02 Jun 2009 13:47 -0700, "Scott Haneda" <talklists at newgeo.com>
wrote:
> 
> Perhaps you may want to ditch anacron, and look into launchd?  Lingon  
> can be used, I believe, in the same way to shied you from the  
> intricacies of OS X scheduling.

Thanks Scott! Being a fairly recent Mac user (moving from Gentoo), 
this looks like it will work out just perfectly. Consider anacron to be
off this 
machine  soon.
> 
> If you are able to run interactively your rsync script, which I assume  
> asks you for a password to login, then anacron, or launchd are both  
> going to need keys on the server no matter what.
> 
> Somewhere, you have to have the keys to do a passwordless login.  If  
> your machine is compromised, you can always revoke the keys quickly.   
> Reading a little about anacron, I can not see there being anything  
> launchd can not do, and much more.

Yeah, passwordless login is working just fine. That wasn't the issue. It
was 
just getting the script scheduled to run under user credentials.
> 
> Curious also, make sure you use rsync correctly, if you are syncing  
> mac files, there are special flags you need to add in order to not  
> nuke your Mac OS X resource/data forks, thereby breaking your files  
> and having an incomplete backup.

I don't have my rsync command line in front of me right now (at work),
but I've
pulled and consolidated a bunch of rsync scripts for Mac users from the
web. Do 
you have any special flags that you recommend, and I'll compare them
with 
what I have tonight.
> 
> Hope this is a little helpful, not entirely the answer you were after,  
> but something I think in the end you will be more happy with.
> -- 

Thanks,
festus

From talklists at newgeo.com  Wed Jun  3 13:18:36 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 3 Jun 2009 13:18:36 -0700
Subject: Ability to run Anacron as a user
In-Reply-To: <1244052294.11144.1318621949@webmail.messagingengine.com>
References: <1243974660.30649.1318448355@webmail.messagingengine.com>
	<434B8A0E-10ED-4289-8972-59D32EB4A12F@newgeo.com>
	<1244052294.11144.1318621949@webmail.messagingengine.com>
Message-ID: <E7BA0455-80CD-4036-9CEE-FB02DFF91FA5@newgeo.com>

On Jun 3, 2009, at 11:04 AM, macports at festus.festusandsimone.org wrote:

> On Tue, 02 Jun 2009 13:47 -0700, "Scott Haneda" <talklists at newgeo.com>
> wrote:
>>
>> Perhaps you may want to ditch anacron, and look into launchd?  Lingon
>> can be used, I believe, in the same way to shied you from the
>> intricacies of OS X scheduling.
>
> Thanks Scott! Being a fairly recent Mac user (moving from Gentoo),
> this looks like it will work out just perfectly. Consider anacron to  
> be
> off this machine  soon.

I did not mean to bash anacron, I am sure it is great software.  For  
your needs, launchd should give you more granular control.

>> If you are able to run interactively your rsync script, which I  
>> assume
>> asks you for a password to login, then anacron, or launchd are both
>> going to need keys on the server no matter what.
>>
>> Somewhere, you have to have the keys to do a passwordless login.  If
>> your machine is compromised, you can always revoke the keys quickly.
>> Reading a little about anacron, I can not see there being anything
>> launchd can not do, and much more.
>
> Yeah, passwordless login is working just fine. That wasn't the  
> issue. It
> was
> just getting the script scheduled to run under user credentials.

Launchd supports setting users and groups, also supports logging to a  
specific file, as well as setting a working directory so you do not  
have to fight with really long paths and paths with spaces in them  
within the file.

One think about Lingon, which I reco'd to you, is it will in fact  
escape the spaces in a file path, which my experience, and those on  
the launchd mailing list, state to not do.

>> Curious also, make sure you use rsync correctly, if you are syncing
>> mac files, there are special flags you need to add in order to not
>> nuke your Mac OS X resource/data forks, thereby breaking your files
>> and having an incomplete backup.
>
> I don't have my rsync command line in front of me right now (at work),
> but I've
> pulled and consolidated a bunch of rsync scripts for Mac users from  
> the
> web. Do
> you have any special flags that you recommend, and I'll compare them
> with
> what I have tonight.


Yes, I think the single most important flag is:
         -E, --extended-attributes   copy extended attributes,  
resource forks
This is very easy to test.  I am not sure what software you use, so I  
will list a few.  Interarchy bookmarks, those will break if you lose  
the extended attributes, Quark files, not that I use them, but I have  
broken them.  Ahh, what the heck, a .webloc is a forked file. Drag a  
url out of safari onto your desktop, it will make a .webloc file.  Run  
your rsync, and see if that .webloc can open the url again, if it can,  
chances are pretty good you are doing the right thing.

Grab a few random files and do:
md5 /path to original
md5 /path to copy

If those md5's match up, you also know you are doing pretty good.
Hope that was of some help, good luck with your scripts.
-- 
Scott * If you contact me off list replace talklists@ with scott@ *


From ryandesign at macports.org  Wed Jun  3 14:30:40 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 3 Jun 2009 16:30:40 -0500
Subject: port install db46 MD5 Issue
In-Reply-To: <9fbe0e780906031046w3ae7acb6u3010b89e704dc30d@mail.gmail.com>
References: <9fbe0e780906031046w3ae7acb6u3010b89e704dc30d@mail.gmail.com>
Message-ID: <5AD03AA0-37C9-42F0-98A7-A070CB72A3B4@macports.org>


On Jun 3, 2009, at 12:46, Mike Papper wrote:

> I see the following error when installing:
>
>  sudo port install db46
> --->  Verifying checksum(s) for db46
> Error: Checksum (md5) mismatch for patch.4.6.21.3
> Error: Target org.macports.checksum returned: Unable to verify file  
> checksums
> Error: Status 1 encountered during processing.
>
> This is on MacBook running OSX 10.5.6
> It is part of me trying to install the RMagic GEM (which needs  
> imagemagic or graphicsmagic (which is installed)).
>
> Is there a cmd-line option to bypass the MD5 check and/or how do I  
> get the maintainers to fix this issue?

The checksum is correct when I download the file, so you probably  
just got a bad download, and should clean the port and try again. See  
also the FAQ:

http://trac.macports.org/wiki/ 
FAQ#IgetError:checksummd5sha1rmd160mismatchforport.WhatcanIdoaboutit




From John.Hachey at AGR.GC.CA  Wed Jun  3 15:42:29 2009
From: John.Hachey at AGR.GC.CA (Hachey, John)
Date: Wed, 3 Jun 2009 18:42:29 -0400
Subject: install issue
Message-ID: <7B64340A44B6634C814A22BCFA6179D51367FE@onottaxms5.AGR.GC.CA>


Hi

I keep getting this error message 

dyld: lazy symbol binding failed: Symbol not found: _close$UNIX2003
  Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _close$UNIX2003
  Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib
  Expected in: /usr/lib/libSystem.B.dylib

dyld: lazy symbol binding failed: Symbol not found: _close$UNIX2003
  Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _close$UNIX2003
  Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib
  Expected in: /usr/lib/libSystem.B.dylib

any ideas?

Thanks, John

From ryandesign at macports.org  Wed Jun  3 15:49:31 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 3 Jun 2009 17:49:31 -0500
Subject: install issue
In-Reply-To: <7B64340A44B6634C814A22BCFA6179D51367FE@onottaxms5.AGR.GC.CA>
References: <7B64340A44B6634C814A22BCFA6179D51367FE@onottaxms5.AGR.GC.CA>
Message-ID: <D3E02B14-DA8A-46A4-BA37-10F00E33BCB0@macports.org>


On Jun 3, 2009, at 17:42, Hachey, John wrote:

> I keep getting this error message
>
> dyld: lazy symbol binding failed: Symbol not found: _close$UNIX2003
>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/ 
> Pextlib.dylib
>   Expected in: /usr/lib/libSystem.B.dylib
>
> dyld: Symbol not found: _close$UNIX2003
>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/ 
> Pextlib.dylib
>   Expected in: /usr/lib/libSystem.B.dylib
>
> dyld: lazy symbol binding failed: Symbol not found: _close$UNIX2003
>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/ 
> Pextlib.dylib
>   Expected in: /usr/lib/libSystem.B.dylib
>
> dyld: Symbol not found: _close$UNIX2003
>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/ 
> Pextlib.dylib
>   Expected in: /usr/lib/libSystem.B.dylib
>
> any ideas?

On what OS is this?

When do you get this -- when running the "port" command? Any port  
command or only specific commands?

Was this MacPorts installation perhaps copied to this computer from  
another computer, of a different processor architecture or OS  
version? If so, that probably won't work, and you should reinstall  
MacPorts on this computer using the correct dmg for this OS version.

Reinstalling MacPorts from the correct dmg might be something to try  
anyway.

Also make sure you have the latest Xcode: 3.1 for Leopard, or 2.5 for  
Tiger.



From raimue at macports.org  Wed Jun  3 15:52:02 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Thu, 04 Jun 2009 00:52:02 +0200
Subject: install issue
In-Reply-To: <7B64340A44B6634C814A22BCFA6179D51367FE@onottaxms5.AGR.GC.CA>
References: <7B64340A44B6634C814A22BCFA6179D51367FE@onottaxms5.AGR.GC.CA>
Message-ID: <4A26FE92.6020101@macports.org>

On 2009-06-04 00:42, Hachey, John wrote:
> I keep getting this error message 
> 
> dyld: lazy symbol binding failed: Symbol not found: _close$UNIX2003
>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib
>   Expected in: /usr/lib/libSystem.B.dylib
> 
> dyld: Symbol not found: _close$UNIX2003
>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib
>   Expected in: /usr/lib/libSystem.B.dylib
> 
> dyld: lazy symbol binding failed: Symbol not found: _close$UNIX2003
>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib
>   Expected in: /usr/lib/libSystem.B.dylib
> 
> dyld: Symbol not found: _close$UNIX2003
>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib
>   Expected in: /usr/lib/libSystem.B.dylib
> 
> any ideas?

Which version of Mac OS X? How did you install MacPorts (disk image/from
source)?

I can only imagine that this could happen when the disk image and target
OS do not match, e.g. using the Leopard disk image on Tiger. Better
reinstall using the correct disk image.

Rainer

From blb at macports.org  Wed Jun  3 15:53:11 2009
From: blb at macports.org (Bryan Blackburn)
Date: Wed, 3 Jun 2009 16:53:11 -0600
Subject: install issue
In-Reply-To: <7B64340A44B6634C814A22BCFA6179D51367FE@onottaxms5.AGR.GC.CA>
References: <7B64340A44B6634C814A22BCFA6179D51367FE@onottaxms5.AGR.GC.CA>
Message-ID: <20090603225311.GC2355@ninagal.withay.com>

On Wed, Jun 03, 2009 at 06:42:29PM -0400, Hachey, John said:
> 
> Hi
> 
> I keep getting this error message 
> 
> dyld: lazy symbol binding failed: Symbol not found: _close$UNIX2003
>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib
>   Expected in: /usr/lib/libSystem.B.dylib

Do you have any DYLD environment variables set?  See with

$ env |grep DYLD

This kind of thing frequently happens with DYLD_LIBRARY_PATH set, throwing
other software off.

Bryan

[...]
> 
> any ideas?
> 
> Thanks, John

From raimue at macports.org  Wed Jun  3 15:55:58 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Thu, 04 Jun 2009 00:55:58 +0200
Subject: pcap intalled but not working?
In-Reply-To: <931668.14533.qm@web52204.mail.re2.yahoo.com>
References: <931668.14533.qm@web52204.mail.re2.yahoo.com>
Message-ID: <4A26FF7E.5010409@macports.org>

On 2009-06-03 16:30, michaeljdur at yahoo.com wrote:
> I installed CDPR and Wireshark via macports via porticus.
> When I launch either no interfaces are detected.  
> CDPR gives me the message:
> "No interfaces found! Make sure pcap is installed."
> I've checked and libpcap is installed and running.  
> Does anyone have a suggestion?

To use the interfaces in capture mode, superuser privileges are being
required:

  sudo wireshark

Rainer

From Macports at festus.festusandsimone.org  Wed Jun  3 19:12:28 2009
From: Macports at festus.festusandsimone.org (John J. Foster)
Date: Wed, 3 Jun 2009 20:12:28 -0600
Subject: Ability to run Anacron as a user
In-Reply-To: <E7BA0455-80CD-4036-9CEE-FB02DFF91FA5@newgeo.com>
References: <1243974660.30649.1318448355@webmail.messagingengine.com>
	<434B8A0E-10ED-4289-8972-59D32EB4A12F@newgeo.com>
	<1244052294.11144.1318621949@webmail.messagingengine.com>
	<E7BA0455-80CD-4036-9CEE-FB02DFF91FA5@newgeo.com>
Message-ID: <20090604021228.GC685@magpie.local>

On Wed, Jun 03, 2009 at 01:18:36PM -0700, Scott Haneda wrote:
> >
> >Thanks Scott! Being a fairly recent Mac user (moving from Gentoo),
> >this looks like it will work out just perfectly. Consider anacron to
> >be
> >off this machine  soon.
> 
> I did not mean to bash anacron, I am sure it is great software. For
> your needs, launchd should give you more granular control.
> 
Nor did I. The 3 things I have used anacron for can all be done using
launchd. I've always preferred native utilities if they can serve my
needs. Time to learn something new.
> 
> Launchd supports setting users and groups, also supports logging to a
> specific file, as well as setting a working directory so you do nothave
> to fight with really long paths and paths with spaces in themwithin the
> file.
> 
> One think about Lingon, which I reco'd to you, is it will in factescape
> the spaces in a file path, which my experience, and those onthe launchd
> mailing list, state to not do.
> 
Thanks, I'm sure these things will come in handy as I learn more of it's
capabilities.
> 
> Yes, I think the single most important flag is:
>  -E, --extended-attributes copy extended attributes,resource
> forks

from man rsync...
-E, --executability         preserve executability
-X, --xattrs                preserve extended attributes

festus at magpie ~ $ rsync --version
rsync  version 3.0.6  protocol version 30

What version of rsync are you running?

> This is very easy to test. I am not sure what software you use, so I
> will list a few. Interarchy bookmarks, those will break if you losethe
> extended attributes, Quark files, not that I use them, but I havebroken
> them. Ahh, what the heck, a .webloc is a forked file. Drag aurl out of
> safari onto your desktop, it will make a .webloc file. Runyour rsync,
> and see if that .webloc can open the url again, if it can,chances are
> pretty good you are doing the right thing.
> 
> Grab a few random files and do:
> md5 /path to original
> md5 /path to copy
> 
> If those md5's match up, you also know you are doing pretty good.
> Hope that was of some help, good luck with your scripts.

I'll investigate this later.

Thanks,
festus

-- 
I just want to break even.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090603/0dd1cfa0/attachment.bin>

From talklists at newgeo.com  Wed Jun  3 19:49:48 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 3 Jun 2009 19:49:48 -0700
Subject: Ability to run Anacron as a user
In-Reply-To: <20090604021228.GC685@magpie.local>
References: <1243974660.30649.1318448355@webmail.messagingengine.com>
	<434B8A0E-10ED-4289-8972-59D32EB4A12F@newgeo.com>
	<1244052294.11144.1318621949@webmail.messagingengine.com>
	<E7BA0455-80CD-4036-9CEE-FB02DFF91FA5@newgeo.com>
	<20090604021228.GC685@magpie.local>
Message-ID: <DB4CD2E6-410A-42E4-93F0-3BE38BC9E0F5@newgeo.com>

On Jun 3, 2009, at 7:12 PM, John J. Foster wrote:

> from man rsync...
> -E, --executability         preserve executability
> -X, --xattrs                preserve extended attributes
>
> festus at magpie ~ $ rsync --version
> rsync  version 3.0.6  protocol version 30
>
> What version of rsync are you running?


Can not believe they would change key flags like this.  Then again,  
rsync had multiple versions, and I believe a separate version distro'd  
on OS X back in the 10.2/3 days.

$rsync --version
rsync  version 2.6.9  protocol version 29

$which rsync
/usr/bin/rsync

$sudo port install rsync

$which rsync
/opt/local/bin/rsync

$/opt/local/bin/rsync --version
rsync  version 3.0.6  protocol version 30

At least there, I am at the same version as you :)  I guess apple puts  
out a very old version.
-- 
Scott * If you contact me off list replace talklists@ with scott@ *


From tomas.okane at anu.edu.au  Wed Jun  3 21:08:50 2009
From: tomas.okane at anu.edu.au (Tomas O'Kane)
Date: Thu, 4 Jun 2009 14:08:50 +1000
Subject: Installation of GMT
Message-ID: <9691A6BF-BE07-49C8-84DB-CCE8F933DBBF@anu.edu.au>

Hi all,
I am a new user to macports, so am guessing that it is just an error  
of my own but I cannot seem to be able to download GMT, the generic  
mapping tools. I am using terminal, and whenever I try and install it  
I receive the following message, plus the attachment

Error: The following dependencies failed to build: netcdf
Error: Status 1 encountered during processing.

I have tried everything that I can think of. Does anyone have any  
suggestions?
Thanks a lot for your help,
Tom
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config netcdf.txt
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090604/c5444946/attachment.txt>
-------------- next part --------------


From blb at macports.org  Wed Jun  3 21:58:32 2009
From: blb at macports.org (Bryan Blackburn)
Date: Wed, 3 Jun 2009 22:58:32 -0600
Subject: Installation of GMT
In-Reply-To: <9691A6BF-BE07-49C8-84DB-CCE8F933DBBF@anu.edu.au>
References: <9691A6BF-BE07-49C8-84DB-CCE8F933DBBF@anu.edu.au>
Message-ID: <20090604045832.GF2355@ninagal.withay.com>

On Thu, Jun 04, 2009 at 02:08:50PM +1000, Tomas O'Kane said:
> Hi all,
> I am a new user to macports, so am guessing that it is just an error of my 
> own but I cannot seem to be able to download GMT, the generic mapping 
> tools. I am using terminal, and whenever I try and install it I receive 
> the following message, plus the attachment
>
> Error: The following dependencies failed to build: netcdf
> Error: Status 1 encountered during processing.
>
> I have tried everything that I can think of. Does anyone have any  
> suggestions?
> Thanks a lot for your help,
> Tom
> --->  Configuring netcdf
[...]
> configure: finding C compiler
> checking for C compiler default output file name... 
> configure: error: C compiler cannot create executables
> See `config.log' for more details.

Seems a lot like #19772:

<http://trac.macports.org/ticket/19772>

Bryan


From scherom at yahoo.de  Thu Jun  4 02:18:49 2009
From: scherom at yahoo.de (scherom)
Date: Thu, 4 Jun 2009 02:18:49 -0700 (PDT)
Subject: complains about launchd not providing socket path
Message-ID: <23803627.post@talk.nabble.com>


Thanky Marcus,
for providing an overview of what is supposedly the status with dbus.
I am however still having problems with launchd not providing a socket path.

I will write 
a) what system I work on
b) what  I added / tried in .profil 
c) what is the error message I still get
d) ask for help
    
a) System
System: OSX 10.5.7
Clean Install MacPorts 1.7.1
Installed gnucash  2.2.9_3
And when trying to launch it, it failed with following out-put in terminal

b) trials to solve the problem
I did try to make the manual launch
by doing  
  sudo launchctl load -w
/Library/LaunchAgents/org.freedesktop.dbus-session.plist 
and
  sudo launchctl load -w
/Library/LaunchDaemons/org.freedesktop.dbus-system.plist 
org.freedesktop.dbus-system

I included in my file .profile in the directory 
  eval `dbus-launch --auto-syntax`

I had also tried putting the following in my .profil
  #export
DBUS_SESSION_BUS_ADRESS="launchd:env=DBUS_LAUNCHD_SESSION_BUS_SOCKET"

c) Error message
However I STILL GET THE FOLLOWING MESSAGE (and gnucash does not start)...
-------------------------------------
Xlib:  extension "RANDR" missing on display "/tmp/launch-7ckllA/:0".
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!

(gnucash:7018): qof-CRITICAL **: qof_object_shutdown: assertion
`object_is_initialized == TRUE' failed
-------------------------------------

d) Any idea of what I can / have to do to get it work?

Thanks so much
-- 
View this message in context: http://www.nabble.com/Meld-fails-to-start--complains-about-launchd-not-providing-socket--path-tp23618152p23803627.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From jsimmons at goblin.punk.net  Thu Jun  4 11:21:04 2009
From: jsimmons at goblin.punk.net (Jeff Simmons)
Date: Thu, 4 Jun 2009 11:21:04 -0700
Subject: Porting openvas to the Mac (OS X)
In-Reply-To: <471172AF-4776-4CF2-ACEE-8678C95C073A@macports.org>
References: <200905290644.21821.jsimmons@goblin.punk.net>
	<200906020755.09521.jsimmons@goblin.punk.net>
	<471172AF-4776-4CF2-ACEE-8678C95C073A@macports.org>
Message-ID: <200906041121.04615.jsimmons@goblin.punk.net>

There's an interesting problem in getting openvas (specifically 
openvas-server) to run on the Mac.

Background: bpf (Berkeley Packet Filter) is a pseudo-device (it's pretending 
to be a hardware device) residing in /dev. It's basically a way to access the 
datastream flowing through the ethernet card without actually accessing the 
ethernet card (usually at /dev/eth0 or similar) itself. Having multiple bpf's 
makes programs that are doing multiple things with the ethernet data stream, 
such as packet filters and network scanners, simpler to write and more 
efficient to run.

A message when compiling openvas says that the program would like 100 bpf's. 
The Mac has 4. The message threatens dire consequences, such as missed scans, 
for limited bpf's.

The assigned weapon in *nix systems for creating bpf's (or any other device 
node) is the program mknod. Running this program 96 times with the proper 
options (preferably via shell script ;-) successfully gives my MacBook 100 
bpf's. But they don't persist - unlike other *nix systems I've used, they're 
gone after a reboot. So I either have to run that script on boot, or before 
launching openvas-server (it shouldn't affect the client).

There are obvious implications for a mac port of openvas-server. 

-- 
Jeff Simmons                                   jsimmons at goblin.punk.net
Simmons Consulting - Network Engineering, Administration, Security
"You guys, I don't hear any noise.  Are you sure you're doing it right?"
        --  My Life With The Thrill Kill Kult

From mcalhoun at macports.org  Thu Jun  4 12:00:01 2009
From: mcalhoun at macports.org (Marcus Calhoun-Lopez)
Date: Thu, 4 Jun 2009 19:00:01 +0000 (UTC)
Subject: complains about launchd not providing socket path
References: <23803627.post@talk.nabble.com>
Message-ID: <loom.20090604T184546-185@post.gmane.org>

scherom <scherom <at> yahoo.de> writes:

> I included in my file .profile in the directory 
>   eval `dbus-launch --auto-syntax`

Since dbus now uses launchd, dbus-launch should not be called directly.
Please remove it from you .profile.

> 
> I had also tried putting the following in my .profil
>   #export
> DBUS_SESSION_BUS_ADRESS="launchd:env=DBUS_LAUNCHD_SESSION_BUS_SOCKET"
> 

launchd has its own environment, so you should not set this value yourself.
Please remove it from you .profile.

After you have removed these entries from your .profile, restart your machine.

Please let me know if these steps fix your problem.

-Marcus




From mta at umich.edu  Thu Jun  4 12:24:45 2009
From: mta at umich.edu (Mike Alexander)
Date: Thu, 04 Jun 2009 15:24:45 -0400
Subject: complains about launchd not providing socket path
In-Reply-To: <23803627.post@talk.nabble.com>
References: <23803627.post@talk.nabble.com>
Message-ID: <1C909A0F15C5B4D881C30DF2@fitzrovia.msalexander.com>

--On June 4, 2009 2:18:49 AM -0700 scherom <scherom at yahoo.de> wrote:

> b) trials to solve the problem
> I did try to make the manual launch
> by doing
>   sudo launchctl load -w
> /Library/LaunchAgents/org.freedesktop.dbus-session.plist
> and
>   sudo launchctl load -w
> /Library/LaunchDaemons/org.freedesktop.dbus-system.plist
> org.freedesktop.dbus-system

You don't want "sudo" on the first of these (dbus-session.plist).  Run 
it as yourself, not as root.  I think the message produced by dbus when 
you install it is still wrong about this.

-- 
Mike Alexander           mta at umich.edu
Ann Arbor, MI            PGP key ID: BEA343A6


From tyson.brown at usask.ca  Thu Jun  4 14:11:57 2009
From: tyson.brown at usask.ca (Tyson Brown)
Date: Thu, 04 Jun 2009 15:11:57 -0600
Subject: version update/checksum update for HDF5?
Message-ID: <C1CE79D4-DBD8-42B4-B9AE-D81196BBF0CC@usask.ca>

In trying to install Octave using MacPorts, I consistently encounter  
the following error:

--->  Verifying checksum(s) for hdf5
Error: Checksum (md5) mismatch for hdf5-1.6.8.tar.gz
Error: Checksum (sha1) mismatch for hdf5-1.6.8.tar.gz
Error: Checksum (rmd160) mismatch for hdf5-1.6.8.tar.gz
Error: Target org.macports.checksum returned: Unable to verify file  
checksums
Error: Status 1 encountered during processing.

I have done a port sync, AND I have gone and looked at the provider's  
site ( http://www.sfr-fresh.com/unix/misc/ ).  When I do that, I see  
the version of HDF5 has changed from 1.6.8 to 1.6.9.  In reading the  
docs for MacPorts, I see that if there has been a "stealth" version  
update, people should update the checksums to reflect that.   
Unfortunately, I don't know how to do that.  Any hints out there for  
how to fix this issue?


- Tyson.Brown at usask.ca  - Tel: (306) 966-4758, Fax: (306) 966-4938
    U of S Blackboard Coordination: http://blackboard.usask.ca/
    U of S Web Coordination:   http://www.usask.ca/web_project/




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090604/6272dcd3/attachment.html>

From ryandesign at macports.org  Thu Jun  4 14:53:58 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 4 Jun 2009 16:53:58 -0500
Subject: version update/checksum update for HDF5?
In-Reply-To: <C1CE79D4-DBD8-42B4-B9AE-D81196BBF0CC@usask.ca>
References: <C1CE79D4-DBD8-42B4-B9AE-D81196BBF0CC@usask.ca>
Message-ID: <DA09746D-10D1-4A59-9FEF-0974DFF9FE4A@macports.org>


On Jun 4, 2009, at 16:11, Tyson Brown wrote:

> In trying to install Octave using MacPorts, I consistently  
> encounter the following error:
>
> --->  Verifying checksum(s) for hdf5
> Error: Checksum (md5) mismatch for hdf5-1.6.8.tar.gz
> Error: Checksum (sha1) mismatch for hdf5-1.6.8.tar.gz
> Error: Checksum (rmd160) mismatch for hdf5-1.6.8.tar.gz
> Error: Target org.macports.checksum returned: Unable to verify file  
> checksums
> Error: Status 1 encountered during processing.
>
> I have done a port sync, AND I have gone and looked at the  
> provider's site ( http://www.sfr-fresh.com/unix/misc/ ).  When I do  
> that, I see the version of HDF5 has changed from 1.6.8 to 1.6.9.   
> In reading the docs for MacPorts, I see that if there has been a  
> "stealth" version update, people should update the checksums to  
> reflect that.  Unfortunately, I don't know how to do that.  Any  
> hints out there for how to fix this issue?

Thanks for reporting the problem. I have filed a ticket in the issue  
tracker for you:

http://trac.macports.org/ticket/19865

In the future you can file issues there yourself. Here are the  
instructions:

http://guide.macports.org/#project.tickets

FYI: This is not a stealth update because the version number has  
changed. A stealth update is when a distfile is changed without its  
filename changing.




From ryandesign at macports.org  Thu Jun  4 14:55:40 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 4 Jun 2009 16:55:40 -0500
Subject: Ability to run Anacron as a user
In-Reply-To: <DB4CD2E6-410A-42E4-93F0-3BE38BC9E0F5@newgeo.com>
References: <1243974660.30649.1318448355@webmail.messagingengine.com>
	<434B8A0E-10ED-4289-8972-59D32EB4A12F@newgeo.com>
	<1244052294.11144.1318621949@webmail.messagingengine.com>
	<E7BA0455-80CD-4036-9CEE-FB02DFF91FA5@newgeo.com>
	<20090604021228.GC685@magpie.local>
	<DB4CD2E6-410A-42E4-93F0-3BE38BC9E0F5@newgeo.com>
Message-ID: <93CA3462-7FA7-430A-BAAC-629FBB0A13CE@macports.org>


On Jun 3, 2009, at 21:49, Scott Haneda wrote:

> I guess apple puts out a very old version.

Not just of rsync, but of many other components as well. Which is why  
we have MacPorts, to provide more up-to-date versions! :)


From ryandesign at macports.org  Thu Jun  4 14:57:04 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 4 Jun 2009 16:57:04 -0500
Subject: install issue
In-Reply-To: <7B64340A44B6634C814A22BCFA6179D51367FF@onottaxms5.AGR.GC.CA>
References: <7B64340A44B6634C814A22BCFA6179D51367FE@onottaxms5.AGR.GC.CA>
	<D3E02B14-DA8A-46A4-BA37-10F00E33BCB0@macports.org>
	<7B64340A44B6634C814A22BCFA6179D51367FF@onottaxms5.AGR.GC.CA>
Message-ID: <845B2375-D160-4945-91C3-5C52475799A2@macports.org>


On Jun 4, 2009, at 11:40, Hachey, John wrote:

> I must have installed the wrong OS X version. Things seem to be  
> running smoothly now
> after a reinstall.

Great, thanks for letting us know. I'm glad you were able to get up  
and running.




From raimue at macports.org  Thu Jun  4 15:22:59 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Fri, 05 Jun 2009 00:22:59 +0200
Subject: version update/checksum update for HDF5?
In-Reply-To: <C1CE79D4-DBD8-42B4-B9AE-D81196BBF0CC@usask.ca>
References: <C1CE79D4-DBD8-42B4-B9AE-D81196BBF0CC@usask.ca>
Message-ID: <4A284943.4000102@macports.org>

On 2009-06-04 23:11, Tyson Brown wrote:
> In trying to install Octave using MacPorts, I consistently encounter the
> following error:
> 
> --->  Verifying checksum(s) for hdf5
> Error: Checksum (md5) mismatch for hdf5-1.6.8.tar.gz
> Error: Checksum (sha1) mismatch for hdf5-1.6.8.tar.gz
> Error: Checksum (rmd160) mismatch for hdf5-1.6.8.tar.gz
> Error: Target org.macports.checksum returned: Unable to verify file
> checksums
> Error: Status 1 encountered during processing.

The checksum of hdf5 is fine for me. You should use 'port clean --all
hdf5' to remove the broken file and download it again.

--snip--
$ sudo port -v clean --all hdf5
--->  Cleaning hdf5
--->  Removing distfiles for hdf5
--->  Removing archives for hdf5
--->  Removing build directory for hdf5
$ sudo port -v checksum hdf5
--->  Fetching hdf5
--->  hdf5-1.6.8.tar.gz doesn't seem to exist in
/opt/local/var/macports/distfiles/hdf5
--->  Attempting to fetch hdf5-1.6.8.tar.gz from
http://arn.se.distfiles.macports.org/hdf5
  % Total    % Received % Xferd  Average Speed   Time    Time     Time
Current
                                 Dload  Upload   Total   Spent    Left
Speed
100 5221k  100 5221k    0     0   323k      0  0:00:16  0:00:16 --:--:--
 347k
--->  Verifying checksum(s) for hdf5
--->  Checksumming hdf5-1.6.8.tar.gz
$
--snap--

Please see
<http://trac.macports.org/wiki/FAQ#IgetError:checksummd5sha1rmd160mismatchforport>

Rainer

From LenoreHorner at sbcglobal.net  Thu Jun  4 15:41:26 2009
From: LenoreHorner at sbcglobal.net (Lenore Horner)
Date: Thu, 4 Jun 2009 17:41:26 -0500
Subject: gnuplot png
Message-ID: <32F7F514-6607-4DCD-A622-D78712724D9C@sbcglobal.net>

I have gnuplot installed on two machines:
G4 10.5.7 making everything not use x11
Intel 10.5.7

On the second machine I can create png plots with gnuplot.  On the  
first the same command causes gibberish (symbols) to be spewed out in  
the command line and no png file to be created.   I assume disabling  
x11 has somehow mangled png output, but I don't know why or how to fix  
it.   Does anyone have any clue?

Lenore


From rbalfanz at gmail.com  Fri Jun  5 10:36:22 2009
From: rbalfanz at gmail.com (Ryan Matthew Balfanz)
Date: Fri, 5 Jun 2009 12:36:22 -0500
Subject: gnuplot png
In-Reply-To: <32F7F514-6607-4DCD-A622-D78712724D9C@sbcglobal.net>
References: <32F7F514-6607-4DCD-A622-D78712724D9C@sbcglobal.net>
Message-ID: <25604c130906051036oc30bb79t463070630bd658c@mail.gmail.com>

I sounds like the png file might be getting sent to stdout rather than a file.

Are you setting 'output' correctly?

-Ryan

On Thu, Jun 4, 2009 at 5:41 PM, Lenore Horner<LenoreHorner at sbcglobal.net> wrote:
> I have gnuplot installed on two machines:
> G4 10.5.7 making everything not use x11
> Intel 10.5.7
>
> On the second machine I can create png plots with gnuplot. ?On the first the
> same command causes gibberish (symbols) to be spewed out in the command line
> and no png file to be created. ? I assume disabling x11 has somehow mangled
> png output, but I don't know why or how to fix it. ? Does anyone have any
> clue?
>
> Lenore
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>



-- 
Ryan Matthew Balfanz
Graduate Student
Department of Physics
Southern Illinois University Edwardsville
http://www.siue.edu/~rbalfan/

From alejandro.aragon at gmail.com  Fri Jun  5 10:43:42 2009
From: alejandro.aragon at gmail.com (Alejandro Aragon)
Date: Fri, 5 Jun 2009 12:43:42 -0500
Subject: MPICH2 package
Message-ID: <6495AF7E-751C-4AFB-99D1-AA3A094B3A42@gmail.com>

Hello everyone,

I installed the package mpich2 and I'm trying to find out how to use  
it in the mac. This may be a little too complicated, but maybe someone  
faced this issue before and can save me a lot of time trying to find  
out the solution.

I've been using the macports GCC43 compiler to build my code, together  
with autotools. When using autotools, a macro is used to detect the  
presence of mpi in the system. The macro is

ACX_MPI([AC_MSG_NOTICE([MPI enabled])],[AC_MSG_NOTICE([MPI disabled])])

Now, the macro finds mpiCC, which in this case is the one installed  
through macports

aaragon@~/Documents/workspace/xga$which mpiCC
/opt/local/bin/mpiCC
aaragon@~/Documents/workspace/xga$mpiCC --version
i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5490)
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There  
is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR  
PURPOSE.

So far so good, but then the test fails as follows:

configure:17516: checking for mpiCC
configure:17532: found /opt/local/bin/mpiCC
configure:17543: result: mpiCC
configure:17561: checking for MPI_Init
configure:17617: mpiCC -o conftest -g -O3 -I/Users/aaragon/Lib/include  
-I/opt/local/include -L/Users/aaragon/Lib/lib -L/opt/local/lib  
conftest.cpp  >&5
Undefined symbols:
   "___gxx_personality_v0", referenced from:
       ___gxx_personality_v0$non_lazy_ptr in ccCBfhuI.o
ld: symbol(s) not found


So I guess the issue is the use of a much older compiler to the one I  
was using to compile the code (namely GCC43).

Does anybody know how to get around this?

Thank you all,

aa

From dweber at macports.org  Fri Jun  5 11:38:09 2009
From: dweber at macports.org (Darren Weber)
Date: Fri, 5 Jun 2009 11:38:09 -0700
Subject: GDB 6.8 via Mac Ports?
In-Reply-To: <C64EAA5B.51496%kendallb@amainhobbies.com>
References: <C64EAA5B.51496%kendallb@amainhobbies.com>
Message-ID: <b808b3510906051138geb4fe64t91aea0c5a017af69@mail.gmail.com>

Hi Kendall,

I put this Portfile together in the hope that the build and install would be
smooth.  It's not.  I'm a novice at building gdb, so I have a lot to learn
about why this is failing.  It may be that the automatic detection of the
target architecture is wrong, it currently detects

checking build system type... i386-apple-darwin9.7.0
checking host system type... i386-apple-darwin9.7.0

The main concern is this:

checking build system type... i386-apple-darwin9.7.0
checking host system type... i386-apple-darwin9.7.0
checking target system type... i386-apple-darwin9.7.0
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for gcc... /usr/bin/gcc-4.0
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /usr/bin/gcc-4.0 accepts -g... yes
checking for /usr/bin/gcc-4.0 option to accept ANSI C... none needed
checking whether we are using the GNU C++ compiler... yes
checking whether /usr/bin/g++-4.0 accepts -g... yes
checking for gnatbind... no
checking for gnatmake... no
checking whether compiler driver understands Ada... no
checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1
$$f2
*** This configuration is not supported in the following subdirectories:
     bfd opcodes gdb sim
    (Any other directories should still work fine.)


So what is happening is the build and install is working, but only
partially.  It would be preferable that the build fails at this point, but
it does not!

I'm very sorry to waste your time, I wish this was working!  I think the
main thing to get right is the target platform identifier.  I looked into it
briefly, but it's not resolved yet.  I would hope that if the target
platform is identified correctly (and fully supported by gdb 6.8), the port
will be functional.

If you have the motivation and patience to look into it, I can advise you on
how to play around with the Porfile.  The first thing to do is to run port
in debug mode, i.e.:

sudo port -d destroot gdb

This will provide a lot of information on what port is doing.  The destroot
target does the configure and build, then runs make install with a custom
DESTDIR.  MacPorts uses that DESTDIR, called destroot, as a way to parse the
files in the port, install the files into
/opt/local/var/macports/software/gdb/ and then activate the port with hard
links in /opt/local to the files in the software/gdb installation.

The destroot path for this port is

/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gdb/work/destroot

The pitiful truth is that the only files currently installed there are:

.../destroot/
.../destroot//opt
.../destroot//opt/local
.../destroot//opt/local/lib
.../destroot//opt/local/lib/libiberty.a
.../destroot//opt/local/share
.../destroot//opt/local/share/info
.../destroot//opt/local/share/info/configure.info
.../destroot//opt/local/share/info/standards.info

If you want to build everything custom, without MacPorts, you can copy the
distfile into your build path from

/opt/local/var/macports/distfiles/gdb/gdb*.tar.gz

I hope we can fix this one!  I've created a new trac ticket on this issue:
http://trac.macports.org/ticket/19871

Take care,
Darren





On Fri, Jun 5, 2009 at 10:56 AM, Kendall Bennett
<KendallB at amainhobbies.com>wrote:

>  Hi Darren,
>
> I am trying to get an updated version of GDB installed to see if it will
> solve some problems I have found with the one distributed by Apple (seems to
> have issues with breakpoints in some C++ programs, specifically Qt4 stuff).
> Anyway, I tested gdb 6.8 on Windows and it seems to not have these issues,
> so the Mac Ports version of gdb 6.8 seemed like a good option.
>
> Anyway, I did the installed and ran into a snag during the activation,
> saying the following:
>
> --->  Activating gdb
> Error: port activate failed: Image error: /opt/local/share/info/
> standards.info is being used by the active autoconf port.  Please
> deactivate this port first, or use 'port -f activate gdb' to force the
> activation.
>
> I have both tried deactivating autoconf and activating gdb, and leaving
> autoconf activated and forcing the activation of gdb, but there does not
> appear to be any gdb binary located anywhere under the /opt/local tree? I
> was expecting it to show up on /opt/local/bin, but there is nothing there,
> and searching the /opt/local directory does not find anything resembling a
> gdb binary?
>
> What am I missing here?
>
> Regards,
>
> *Kendall Bennett, CEO
> *A Main Hobbies
> 424 Otterson Drive, Suite 160
> Chico, CA 95928
> 1-800-705-2215 (Toll-Free)
> 1-530-894-0797 (Int'l & Local)
> 1-530-894-9049 (Fax)
> *http://www.amainhobbies.com*
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090605/4e979aaf/attachment.html>

From LenoreHorner at sbcglobal.net  Fri Jun  5 12:53:25 2009
From: LenoreHorner at sbcglobal.net (Lenore Horner)
Date: Fri, 5 Jun 2009 14:53:25 -0500
Subject: gnuplot png
In-Reply-To: <25604c130906051036oc30bb79t463070630bd658c@mail.gmail.com>
References: <32F7F514-6607-4DCD-A622-D78712724D9C@sbcglobal.net>
	<25604c130906051036oc30bb79t463070630bd658c@mail.gmail.com>
Message-ID: <738AD52A-AA6C-4FE5-9A22-CDF6568DBE02@sbcglobal.net>


On Jun 5, 2009, at 12:36 , Ryan Matthew Balfanz wrote:

> I sounds like the png file might be getting sent to stdout rather  
> than a file.
>
> Are you setting 'output' correctly?
>
> -Ryan
Hi Ryan,

I don't know that I'm setting the output correctly.  I'm setting it  
the same way on both machines
set terminal png font 'Times' 24 size 640, 580

I'll go have a look at "output".

Lenore

>
> On Thu, Jun 4, 2009 at 5:41 PM, Lenore Horner<LenoreHorner at sbcglobal.net 
> > wrote:
>> I have gnuplot installed on two machines:
>> G4 10.5.7 making everything not use x11
>> Intel 10.5.7
>>
>> On the second machine I can create png plots with gnuplot.  On the  
>> first the
>> same command causes gibberish (symbols) to be spewed out in the  
>> command line
>> and no png file to be created.   I assume disabling x11 has somehow  
>> mangled
>> png output, but I don't know why or how to fix it.   Does anyone  
>> have any
>> clue?
>>
>> Lenore
>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>
>
>
>
> -- 
> Ryan Matthew Balfanz
> Graduate Student
> Department of Physics
> Southern Illinois University Edwardsville
> http://www.siue.edu/~rbalfan/


From markmh at bgsu.edu  Fri Jun  5 14:32:17 2009
From: markmh at bgsu.edu (Mark M Huntress)
Date: Fri, 5 Jun 2009 17:32:17 -0400
Subject: installations not working
Message-ID: <7A2FF6D3217BE244B0B6ADF25F580CF136495ED1A5@MAIL6.bgsu.edu>

I got macports recently and I tried to install molden and gcc44 and neither of them is installing. For Molden, it installed some other things, but never got to the point where Molden was installed. It kind of just ended up sitting there looking like it was working, just for like hours. 
 Now I am trying to install gcc44 and it is doing the same thing. It fetches, and extracts and configures, but then it just sits there building for hours, and I don't think it is ever going to work. 
 Is there something wrong with my macports, or something wrong with me? 
Thanks

From talklists at newgeo.com  Fri Jun  5 14:36:29 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Fri, 5 Jun 2009 14:36:29 -0700
Subject: installations not working
In-Reply-To: <7A2FF6D3217BE244B0B6ADF25F580CF136495ED1A5@MAIL6.bgsu.edu>
References: <7A2FF6D3217BE244B0B6ADF25F580CF136495ED1A5@MAIL6.bgsu.edu>
Message-ID: <C39B9CE7-1C58-4AF2-868C-ABC83A981164@newgeo.com>

Can you add -d to your install line to get debug output?  That will  
give you many clues. You can also post the output here.
-- 
Scott
Iphone says hello.

On Jun 5, 2009, at 2:32 PM, Mark M Huntress <markmh at bgsu.edu> wrote:

> I got macports recently and I tried to install molden and gcc44 and  
> neither of them is installing. For Molden, it installed some other  
> things, but never got to the point where Molden was installed. It  
> kind of just ended up sitting there looking like it was working,  
> just for like hours.
> Now I am trying to install gcc44 and it is doing the same thing. It  
> fetches, and extracts and configures, but then it just sits there  
> building for hours, and I don't think it is ever going to work.
> Is there something wrong with my macports, or something wrong with me?
> Thanks
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

From frstan at bellsouth.net  Fri Jun  5 14:40:44 2009
From: frstan at bellsouth.net (William Davis)
Date: Fri, 5 Jun 2009 17:40:44 -0400
Subject: installations not working
In-Reply-To: <7A2FF6D3217BE244B0B6ADF25F580CF136495ED1A5@MAIL6.bgsu.edu>
References: <7A2FF6D3217BE244B0B6ADF25F580CF136495ED1A5@MAIL6.bgsu.edu>
Message-ID: <F7739F0B-589B-40EE-872E-9D5F6B1D5542@bellsouth.net>


On Jun 5, 2009, at 5:32 PM, Mark M Huntress wrote:

> I got macports recently and I tried to install molden and gcc44 and  
> neither of them is installing. For Molden, it installed some other  
> things, but never got to the point where Molden was installed. It  
> kind of just ended up sitting there looking like it was working,  
> just for like hours.
> Now I am trying to install gcc44 and it is doing the same thing. It  
> fetches, and extracts and configures, but then it just sits there  
> building for hours, and I don't think it is ever going to work.
> Is there something wrong with my macports, or something wrong with me?
> Thanks
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Do what Scott said but gcc is a looooong compile -- it is a compiler  
after all! ;)

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From dweber at macports.org  Fri Jun  5 16:53:05 2009
From: dweber at macports.org (Darren Weber)
Date: Fri, 5 Jun 2009 16:53:05 -0700
Subject: GDB 6.8 via Mac Ports?
In-Reply-To: <C64ED0C6.514E4%kendallb@amainhobbies.com>
References: <b808b3510906051138geb4fe64t91aea0c5a017af69@mail.gmail.com>
	<C64ED0C6.514E4%kendallb@amainhobbies.com>
Message-ID: <b808b3510906051653o4258d246ife089e15e3d50b33@mail.gmail.com>

Hi,

I spent a while looking into this, pretty nearly clueless about how to
resolve the problem.  I've commented on my experience today in the ticket:

http://trac.macports.org/ticket/19871

To save others the trouble, I've committed a change to the trunk of this
port so that the fetch stage just issues a message about the port failing to
build everything, with reference to that ticket.  Hopefully that will save
some trouble for others trying to use the port.  In hindsight, the port
should not have been committed in the first place, but it wasn't clear to me
at the time that it was failing to build everything.  Anyhow, sorry for all
the inconvenience!

Take care,
Darren



On Fri, Jun 5, 2009 at 1:40 PM, Kendall Bennett
<KendallB at amainhobbies.com>wrote:

>  Hi Darren,
>
> Thanks for the update. I am a total newb when it comes to Mac Ports, and
> although I have built GDB in the past on Linux, I never really played much
> with it past just building it (and patching in debugging support for X11
> loadable modules). But that was a while ago.
>
> If I get time, I will play with this a bit and see if I can work it out. If
> you do get it figured out, let me know!
>
> Regards,
>
> *Kendall Bennett, CEO
> *A Main Hobbies
> 424 Otterson Drive, Suite 160
> Chico, CA 95928
> 1-800-705-2215 (Toll-Free)
> 1-530-894-0797 (Int'l & Local)
> 1-530-894-9049 (Fax)
> *http://www.amainhobbies.com
> *
>
> ------------------------------
> *From: *Darren Weber <dweber at macports.org>
> *Date: *Fri, 5 Jun 2009 11:38:09 -0700
> *To: *Kendall Bennett <kendallb at amainhobbies.com>
> *Cc: *MacPorts Users <macports-users at lists.macosforge.org>
> *Subject: *Re: GDB 6.8 via Mac Ports?
>
>
>
> Hi Kendall,
>
> I put this Portfile together in the hope that the build and install would
> be smooth.  It's not.  I'm a novice at building gdb, so I have a lot to
> learn about why this is failing.  It may be that the automatic detection of
> the target architecture is wrong, it currently detects
>
> checking build system type... i386-apple-darwin9.7.0
> checking host system type... i386-apple-darwin9.7.0
>
> The main concern is this:
>
> checking build system type... i386-apple-darwin9.7.0
> checking host system type... i386-apple-darwin9.7.0
> checking target system type... i386-apple-darwin9.7.0
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether ln works... yes
> checking whether ln -s works... yes
> checking for gcc... /usr/bin/gcc-4.0
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether /usr/bin/gcc-4.0 accepts -g... yes
> checking for /usr/bin/gcc-4.0 option to accept ANSI C... none needed
> checking whether we are using the GNU C++ compiler... yes
> checking whether /usr/bin/g++-4.0 accepts -g... yes
> checking for gnatbind... no
> checking for gnatmake... no
> checking whether compiler driver understands Ada... no
> checking how to compare bootstrapped objects... cmp --ignore-initial=16
> $$f1 $$f2
> *** This configuration is not supported in the following subdirectories:
>      bfd opcodes gdb sim
>     (Any other directories should still work fine.)
>
>
> So what is happening is the build and install is working, but only
> partially.  It would be preferable that the build fails at this point, but
> it does not!
>
> I'm very sorry to waste your time, I wish this was working!  I think the
> main thing to get right is the target platform identifier.  I looked into it
> briefly, but it's not resolved yet.  I would hope that if the target
> platform is identified correctly (and fully supported by gdb 6.8), the port
> will be functional.
>
> If you have the motivation and patience to look into it, I can advise you
> on how to play around with the Porfile.  The first thing to do is to run
> port in debug mode, i.e.:
>
> sudo port -d destroot gdb
>
> This will provide a lot of information on what port is doing.  The destroot
> target does the configure and build, then runs make install with a custom
> DESTDIR.  MacPorts uses that DESTDIR, called destroot, as a way to parse the
> files in the port, install the files into
> /opt/local/var/macports/software/gdb/ and then activate the port with hard
> links in /opt/local to the files in the software/gdb installation.
>
> The destroot path for this port is
>
>
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gdb/work/destroot
>
> The pitiful truth is that the only files currently installed there are:
>
> .../destroot/
> .../destroot//opt
> .../destroot//opt/local
> .../destroot//opt/local/lib
> .../destroot//opt/local/lib/libiberty.a
> .../destroot//opt/local/share
> .../destroot//opt/local/share/info
> .../destroot//opt/local/share/info/configure.info <http://configure.info>
> .../destroot//opt/local/share/info/standards.info <http://standards.info>
>
> If you want to build everything custom, without MacPorts, you can copy the
> distfile into your build path from
>
> /opt/local/var/macports/distfiles/gdb/gdb*.tar.gz
>
> I hope we can fix this one!  I've created a new trac ticket on this issue:
> http://trac.macports.org/ticket/19871
>
> Take care,
> Darren
>
>
>
>
>
> On Fri, Jun 5, 2009 at 10:56 AM, Kendall Bennett <
> KendallB at amainhobbies.com> wrote:
>
> Hi Darren,
>
> I am trying to get an updated version of GDB installed to see if it will
> solve some problems I have found with the one distributed by Apple (seems to
> have issues with breakpoints in some C++ programs, specifically Qt4 stuff).
> Anyway, I tested gdb 6.8 on Windows and it seems to not have these issues,
> so the Mac Ports version of gdb 6.8 seemed like a good option.
>
> Anyway, I did the installed and ran into a snag during the activation,
> saying the following:
>
> --->  Activating gdb
> Error: port activate failed: Image error: /opt/local/share/info/
> standards.info <http://standards.info>  is being used by the active
> autoconf port.  Please deactivate this port first, or use 'port -f activate
> gdb' to force the activation.
>
> I have both tried deactivating autoconf and activating gdb, and leaving
> autoconf activated and forcing the activation of gdb, but there does not
> appear to be any gdb binary located anywhere under the /opt/local tree? I
> was expecting it to show up on /opt/local/bin, but there is nothing there,
> and searching the /opt/local directory does not find anything resembling a
> gdb binary?
>
> What am I missing here?
>
> Regards,
>
> *Kendall Bennett, CEO
> *A Main Hobbies
> 424 Otterson Drive, Suite 160
> Chico, CA 95928
> 1-800-705-2215 (Toll-Free)
> 1-530-894-0797 (Int'l & Local)
> 1-530-894-9049 (Fax)
> *http://www.amainhobbies.com
> *
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090605/e4e3d644/attachment.html>

From ryandesign at macports.org  Fri Jun  5 17:53:53 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 5 Jun 2009 19:53:53 -0500
Subject: installations not working
In-Reply-To: <7A2FF6D3217BE244B0B6ADF25F580CF136495ED1A5@MAIL6.bgsu.edu>
References: <7A2FF6D3217BE244B0B6ADF25F580CF136495ED1A5@MAIL6.bgsu.edu>
Message-ID: <3EC97D28-EF8D-480D-8A7B-E2F88BA82C14@macports.org>


On Jun 5, 2009, at 16:32, Mark M Huntress wrote:

> I got macports recently and I tried to install molden and gcc44 and  
> neither of them is installing. For Molden, it installed some other  
> things, but never got to the point where Molden was installed. It  
> kind of just ended up sitting there looking like it was working,  
> just for like hours.
>  Now I am trying to install gcc44 and it is doing the same thing.  
> It fetches, and extracts and configures, but then it just sits  
> there building for hours, and I don't think it is ever going to work.
>  Is there something wrong with my macports, or something wrong with  
> me?

Welcome to MacPorts!


I haven't tried the molden port specifically. But I know gcc4x do  
take a long time. On my 2-core Intel Mac I think it took an hour or  
so, while on my older PowerPC it took over 6 hours.

As scott said, the -d flag will give you more indication of what  
MacPorts is doing, if you care to see that. Or you can just open  
Activity Monitor to confirm that something is in fact happening.




From frstan at bellsouth.net  Sat Jun  6 01:32:16 2009
From: frstan at bellsouth.net (William Davis)
Date: Sat, 6 Jun 2009 04:32:16 -0400
Subject: xpdf v poppler
Message-ID: <4C891A82-82E0-44F3-AF6E-B6E77B19BCCF@bellsouth.net>


xpdf in conflict with poppler:

macintosh:~ frstan$ sudo port -d activate xpdf
--->  Activating xpdf
DEBUG: Image error: /opt/local/bin/pdffonts is being used by the  
active poppler port.  Please deactivate this port first, or use 'port - 
f activate xpdf' to force the activation.
     while executing
"_activate_contents $name $imagefiles $imagedir"
     (procedure "portimage::activate" line 57)
     invoked from within
"portimage::activate $portname [composite_version $portversion [array  
get variations]] [array get options]"
Error: port activate failed: Image error: /opt/local/bin/pdffonts is  
being used by the active poppler port.  Please deactivate this port  
first, or use 'port -f activate xpdf' to force the activation.


William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From jmr at macports.org  Sat Jun  6 01:46:15 2009
From: jmr at macports.org (Joshua Root)
Date: Sat, 06 Jun 2009 18:46:15 +1000
Subject: xpdf v poppler
In-Reply-To: <4C891A82-82E0-44F3-AF6E-B6E77B19BCCF@bellsouth.net>
References: <4C891A82-82E0-44F3-AF6E-B6E77B19BCCF@bellsouth.net>
Message-ID: <4A2A2CD7.7010603@macports.org>

On 2009-6-6 18:32, William Davis wrote:
> 
> xpdf in conflict with poppler:
> 
> macintosh:~ frstan$ sudo port -d activate xpdf
> --->  Activating xpdf
> DEBUG: Image error: /opt/local/bin/pdffonts is being used by the active
> poppler port.  Please deactivate this port first, or use 'port -f
> activate xpdf' to force the activation.
>     while executing
> "_activate_contents $name $imagefiles $imagedir"
>     (procedure "portimage::activate" line 57)
>     invoked from within
> "portimage::activate $portname [composite_version $portversion [array
> get variations]] [array get options]"
> Error: port activate failed: Image error: /opt/local/bin/pdffonts is
> being used by the active poppler port.  Please deactivate this port
> first, or use 'port -f activate xpdf' to force the activation.

There's a ticket open for this.

- Josh

From akiabo at googlemail.com  Sat Jun  6 07:56:43 2009
From: akiabo at googlemail.com (A. Osthoff)
Date: Sat, 06 Jun 2009 16:56:43 +0200
Subject: Updated Gnucash doesn't handle preferences continued
Message-ID: <4A2A83AB.90309@gmail.com>

I am refering to the following discussion:
http://www.nabble.com/Updated-Gnucash-doesn%27t-handle-preferences-to19831050.html#a19832473

Recently I upgraded to Gnucash 2.2.9 and gconf 2.26.2_0. The problem
persists and I had to manually deactive the current gconf and activate
2.24.0_0 for Gnucash to "remember" its preferences.

hth,
	achim

From face at CentosPrime.COM  Sat Jun  6 08:32:45 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sat, 06 Jun 2009 08:32:45 -0700
Subject: Reverting to previous ports - mysql5
Message-ID: <ACDC7F11-A8AA-43AA-9ECF-BA33E281987C@CentosPrime.COM>

This is on my 10.3 system.

I unfortunately installed mysql5-server on my 10.3.9 system after  
getting an "obsolete +server" message.

My startup files have become confused.

I figure one way to get back to where I want to be is to get rid of  
the current mysql5 and replace it with a previous version

   mysql5 @5.0.77_2+server
   mysql5 @5.0.81_0+server
   mysql5 @5.0.82_0+server (active)

so I deactivated .82 and activated .81 -

My attempts to use SystemStarter to start mysql5 failed, but I was  
able to get back where I belong by issuing the start command on its own

  sudo /opt/local/share/mysql5/mysql/mysql.server start

So - besides replacing 10.3.9 (maybe by the end of August, possibly  
end of October) - what should I do about updates to mysql5?

Thanks.

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From face at CentosPrime.COM  Sat Jun  6 08:39:06 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sat, 06 Jun 2009 08:39:06 -0700
Subject: mysql5-devel vs. mysql5-client/mysql5-server
Message-ID: <E7D9F90E-23DE-49CE-BC92-76343B102574@centosprime.com>

At some point I expect that mysql5-client/server will switch to  
version 5.1
At that point I will want to make my "working" system (5.1) not use  
the mysql5-devel port, but the client/server ports.

Is it simply a matter of

  port deactivate mysql5-devel
  port install mysql5-client
  port install mysql5-server

Thanks in advance.

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From brad at pixilla.com  Sat Jun  6 09:03:35 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Sat, 6 Jun 2009 09:03:35 -0700
Subject: Reverting to previous ports - mysql5
In-Reply-To: <ACDC7F11-A8AA-43AA-9ECF-BA33E281987C@CentosPrime.COM>
References: <ACDC7F11-A8AA-43AA-9ECF-BA33E281987C@CentosPrime.COM>
Message-ID: <154F28B4-2983-4E70-9770-EB3F27D77A60@pixilla.com>


On Jun 6, 2009, at 8:32 AM, Chris Janton wrote:

> This is on my 10.3 system.
>
> I unfortunately installed mysql5-server on my 10.3.9 system after  
> getting an "obsolete +server" message.
>
> My startup files have become confused.
>
> I figure one way to get back to where I want to be is to get rid of  
> the current mysql5 and replace it with a previous version
>
>  mysql5 @5.0.77_2+server
>  mysql5 @5.0.81_0+server
>  mysql5 @5.0.82_0+server (active)
>
> so I deactivated .82 and activated .81 -
>
> My attempts to use SystemStarter to start mysql5 failed, but I was  
> able to get back where I belong by issuing the start command on its  
> own
>
> sudo /opt/local/share/mysql5/mysql/mysql.server start

I don't use the SystemStarter command so I can't comment but here is  
what I do.

launchctl load -w /Library/LaunchDaemons/org.macports.mysql5-devel.plist

The -w (write) causes mysql5-devel to be started automatically during  
system boot.

//Brad

From face at CentosPrime.COM  Sat Jun  6 11:41:08 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sat, 06 Jun 2009 11:41:08 -0700
Subject: Reverting to previous ports - mysql5
In-Reply-To: <154F28B4-2983-4E70-9770-EB3F27D77A60@pixilla.com>
References: <ACDC7F11-A8AA-43AA-9ECF-BA33E281987C@CentosPrime.COM>
	<154F28B4-2983-4E70-9770-EB3F27D77A60@pixilla.com>
Message-ID: <480AD013-30C1-4B07-ACB6-093481D7BEDC@CentosPrime.COM>

On 2009-06-06 , at 09:03 , Bradley Giesbrecht wrote:

> I don't use the SystemStarter command so I can't comment but here is  
> what I do.
>
> launchctl load -w /Library/LaunchDaemons/org.macports.mysql5- 
> devel.plist
>
> The -w (write) causes mysql5-devel to be started automatically  
> during system boot.


OS X 10.3.9 uses SystemStarter. launchd (which I use on my 10.5  
system) is OK. I don't have trouble there.

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From frstan at bellsouth.net  Sat Jun  6 21:48:33 2009
From: frstan at bellsouth.net (William Davis)
Date: Sun, 7 Jun 2009 00:48:33 -0400
Subject: ardour2 build fails
Message-ID: <EA87442B-9A88-49C9-8DC1-B3ECA5A1DE7B@bellsouth.net>

install of ardour2 failed with this mesg:

s/ardour/rb_effect.cc", "libs/ardour/audio_unit.cc"])
po_builder(["libs/ardour/el_GR.po"], ["libs/ardour/po/el_GR.po", "libs/ 
ardour/libardour2.pot"])
Updating libs/ardour/el_GR.po
............................................................................................................................... done 
.
msgmerge: `libs/ardour/el_GR.po': No such file or directory
scons: *** [libs/ardour/el_GR.po] Error 1
scons: building terminated because of errors.

Warning: the following items did not execute (for ardour2):  
org.macports.activate org.macports.destroot org.macports.install
Error: Status 1 encountered during processing.
macintosh:~ frstan$


William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From devans at macports.org  Sun Jun  7 09:22:03 2009
From: devans at macports.org (David Evans)
Date: Sun, 07 Jun 2009 09:22:03 -0700
Subject: ardour2 build fails
In-Reply-To: <EA87442B-9A88-49C9-8DC1-B3ECA5A1DE7B@bellsouth.net>
References: <EA87442B-9A88-49C9-8DC1-B3ECA5A1DE7B@bellsouth.net>
Message-ID: <4A2BE92B.3000607@macports.org>

William Davis wrote:
> install of ardour2 failed with this mesg:
>
> s/ardour/rb_effect.cc", "libs/ardour/audio_unit.cc"])
> po_builder(["libs/ardour/el_GR.po"], ["libs/ardour/po/el_GR.po", 
> "libs/ardour/libardour2.pot"])
> Updating libs/ardour/el_GR.po
> ............................................................................................................................... 
> done.
> msgmerge: `libs/ardour/el_GR.po': No such file or directory
> scons: *** [libs/ardour/el_GR.po] Error 1
> scons: building terminated because of errors.
>
> Warning: the following items did not execute (for ardour2): 
> org.macports.activate org.macports.destroot org.macports.install
> Error: Status 1 encountered during processing.
> macintosh:~ frstan$
>
I can't reproduce this error.   Look for this file relative to the ports
${worksrcpath} and if it seems to be missing
then I suggest you clean the port entirely and try again

sudo port clean --all ardour2

If that doesn't work please report as a ticket rather than to the user
list, build with -d option and attach the full output
as an attachment to the ticket so there is some information available to
try and diagnose the problem.

Thanks

Dave


From ryandesign at macports.org  Sun Jun  7 13:17:58 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 7 Jun 2009 15:17:58 -0500
Subject: Reverting to previous ports - mysql5
In-Reply-To: <ACDC7F11-A8AA-43AA-9ECF-BA33E281987C@CentosPrime.COM>
References: <ACDC7F11-A8AA-43AA-9ECF-BA33E281987C@CentosPrime.COM>
Message-ID: <D6FC8DC0-BE5D-4A69-BF66-29BEF4C908F4@macports.org>

On Jun 6, 2009, at 10:32, Chris Janton wrote:

> This is on my 10.3 system.
>
> I unfortunately installed mysql5-server on my 10.3.9 system after  
> getting an "obsolete +server" message.
>
> My startup files have become confused.

Sorry about that. I did not test on 10.3. I can try to do so in a few  
days. What error messages are you encountering?


> I figure one way to get back to where I want to be is to get rid of  
> the current mysql5 and replace it with a previous version
>
>   mysql5 @5.0.77_2+server
>   mysql5 @5.0.81_0+server
>   mysql5 @5.0.82_0+server (active)
>
> so I deactivated .82 and activated .81 -
>
> My attempts to use SystemStarter to start mysql5 failed, but I was  
> able to get back where I belong by issuing the start command on its  
> own
>
>  sudo /opt/local/share/mysql5/mysql/mysql.server start
>
> So - besides replacing 10.3.9 (maybe by the end of August, possibly  
> end of October) - what should I do about updates to mysql5?

As per your hunch, deactivating mysql5 @5.0.82_0 and mysql5-server  
@5.0.82_0 and then activating mysql5 @5.0.81_0 ought to get you back  
to where you were. If this does not work, what happens?


From ryandesign at macports.org  Sun Jun  7 13:23:22 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 7 Jun 2009 15:23:22 -0500
Subject: mysql5-devel vs. mysql5-client/mysql5-server
In-Reply-To: <E7D9F90E-23DE-49CE-BC92-76343B102574@centosprime.com>
References: <E7D9F90E-23DE-49CE-BC92-76343B102574@centosprime.com>
Message-ID: <49CD911D-B727-4A7B-BE67-421FD2F19FA5@macports.org>


On Jun 6, 2009, at 10:39, Chris Janton wrote:

> At some point I expect that mysql5-client/server will switch to  
> version 5.1

Yes, there's probably no reason to hold up this upgrade any longer:

http://trac.macports.org/ticket/19414

> At that point I will want to make my "working" system (5.1) not use  
> the mysql5-devel port, but the client/server ports.
>
> Is it simply a matter of
>
>  port deactivate mysql5-devel
>  port install mysql5-client
>  port install mysql5-server


Yes, except there isn't a "mysql5-client" port as originally  
suggested in the ticket:

http://trac.macports.org/ticket/12313

Rather, it is called just "mysql5" and the server port is "mysql5- 
server". So you can:

sudo port deactivate mysql5-devel
sudo port install mysql5-server



From frstan at bellsouth.net  Sun Jun  7 14:23:59 2009
From: frstan at bellsouth.net (William Davis)
Date: Sun, 7 Jun 2009 17:23:59 -0400
Subject: ardour2 build fails
In-Reply-To: <4A2BE92B.3000607@macports.org>
References: <EA87442B-9A88-49C9-8DC1-B3ECA5A1DE7B@bellsouth.net>
	<4A2BE92B.3000607@macports.org>
Message-ID: <74FA4F94-1D6A-46C8-B9E4-A27701E71D98@bellsouth.net>


On Jun 7, 2009, at 12:22 PM, David Evans wrote:

> William Davis wrote:
>> install of ardour2 failed with this mesg:
>>
>> s/ardour/rb_effect.cc", "libs/ardour/audio_unit.cc"])
>> po_builder(["libs/ardour/el_GR.po"], ["libs/ardour/po/el_GR.po",  
>> "libs/ardour/libardour2.pot"])
>> Updating libs/ardour/el_GR.po
>> ............................................................................................................................... done 
>> .
>> msgmerge: `libs/ardour/el_GR.po': No such file or directory
>> scons: *** [libs/ardour/el_GR.po] Error 1
>> scons: building terminated because of errors.
>>
>> Warning: the following items did not execute (for ardour2):  
>> org.macports.activate org.macports.destroot org.macports.install
>> Error: Status 1 encountered during processing.
>> macintosh:~ frstan$
>>
> I can't reproduce this error.   Look for this file relative to the  
> ports
> ${worksrcpath} and if it seems to be missing
> then I suggest you clean the port entirely and try again
>
> sudo port clean --all ardour2
>
> If that doesn't work please report as a ticket rather than to the user
> list, build with -d option and attach the full output
> as an attachment to the ticket so there is some information  
> available to
> try and diagnose the problem.
>
> Thanks
>
> Dave
>

did that, ticket #19886

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From face at CentosPrime.COM  Sun Jun  7 18:58:44 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sun, 07 Jun 2009 18:58:44 -0700
Subject: Reverting to previous ports - mysql5
In-Reply-To: <D6FC8DC0-BE5D-4A69-BF66-29BEF4C908F4@macports.org>
References: <ACDC7F11-A8AA-43AA-9ECF-BA33E281987C@CentosPrime.COM>
	<D6FC8DC0-BE5D-4A69-BF66-29BEF4C908F4@macports.org>
Message-ID: <578A5253-50D6-4F6A-BF91-DB66B81A564B@CentosPrime.COM>

On 2009-06-07 , at 13:17 , Ryan Schmidt wrote:

> As per your hunch, deactivating mysql5 @5.0.82_0 and mysql5-server  
> @5.0.82_0 and then activating mysql5 @5.0.81_0 ought to get you back  
> to where you were. If this does not work, what happens?


I didn't write down the errors. Basically the "new" startup procedure  
couldn't find things.

I did the deactivate/activate of .81 and I now have a reasonable / 
Library/StartupItems/mysql5

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From face at CentosPrime.COM  Sun Jun  7 19:00:35 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sun, 07 Jun 2009 19:00:35 -0700
Subject: mysql5-devel vs. mysql5-client/mysql5-server
In-Reply-To: <49CD911D-B727-4A7B-BE67-421FD2F19FA5@macports.org>
References: <E7D9F90E-23DE-49CE-BC92-76343B102574@centosprime.com>
	<49CD911D-B727-4A7B-BE67-421FD2F19FA5@macports.org>
Message-ID: <D6B7983E-5B22-431E-BF81-86B052569EC6@CentosPrime.COM>

On 2009-06-07 , at 13:23 , Ryan Schmidt wrote:

>> At that point I will want to make my "working" system (5.1) not use  
>> the mysql5-devel port, but the client/server ports.
>>
>> Is it simply a matter of
>>
>> port deactivate mysql5-devel
>> port install mysql5-client
>> port install mysql5-server
>
>
> Yes, except there isn't a "mysql5-client" port as originally  
> suggested in the ticket:
>
> http://trac.macports.org/ticket/12313
>
> Rather, it is called just "mysql5" and the server port is "mysql5- 
> server". So you can:
>
> sudo port deactivate mysql5-devel
> sudo port install mysql5-server


which should install mysql5 from scratch and then add the server  
startup commands.

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From ryandesign at macports.org  Sun Jun  7 21:04:58 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 7 Jun 2009 23:04:58 -0500
Subject: mysql5-devel vs. mysql5-client/mysql5-server
In-Reply-To: <D6B7983E-5B22-431E-BF81-86B052569EC6@CentosPrime.COM>
References: <E7D9F90E-23DE-49CE-BC92-76343B102574@centosprime.com>
	<49CD911D-B727-4A7B-BE67-421FD2F19FA5@macports.org>
	<D6B7983E-5B22-431E-BF81-86B052569EC6@CentosPrime.COM>
Message-ID: <DA199316-C1CC-4BE4-ACAF-9790A27A5342@macports.org>


On Jun 7, 2009, at 21:00, Chris Janton wrote:

> On 2009-06-07 , at 13:23 , Ryan Schmidt wrote:
>
>>> At that point I will want to make my "working" system (5.1) not  
>>> use the mysql5-devel port, but the client/server ports.
>>>
>>> Is it simply a matter of
>>>
>>> port deactivate mysql5-devel
>>> port install mysql5-client
>>> port install mysql5-server
>>
>> Yes, except there isn't a "mysql5-client" port as originally  
>> suggested in the ticket:
>>
>> http://trac.macports.org/ticket/12313
>>
>> Rather, it is called just "mysql5" and the server port is "mysql5- 
>> server". So you can:
>>
>> sudo port deactivate mysql5-devel
>> sudo port install mysql5-server
>
> which should install mysql5 from scratch and then add the server  
> startup commands.


Yes, exactly.


From qoo-ooq at gmx.de  Mon Jun  8 04:44:55 2009
From: qoo-ooq at gmx.de (Sebastian Wojtowicz)
Date: Mon, 8 Jun 2009 13:44:55 +0200
Subject: PHP 5.3.0RC2 +mysql, no extension_dir = no-debug-non-zts-20090115/
Message-ID: <E853CD1B-5962-46D6-8DBB-8E0089441A33@gmx.de>

Hello,

I'm kind of a newbie in Mac but I have managed to install several PHP  
versions with mysql and stuff like that before.
Only now, I can't install the new PHP version.

Well ok, I can, but somehow php is always looking for the extensions in
/opt/local/lib/php/extensions/no-debug-non-zts-20090115/
This directory doesn't exist. Only
/opt/local/lib/php/
exists. So when I include an extension, by taking away the ";" in the  
php.ini, I get a warning
PHP Warning:  PHP Startup: Unable to load dynamic library '/opt/local/ 
lib/php/extensions/no-debug-non-zts-20090115/....' ....

I also find it strange, that this is the default directory. Where does  
it come from ?! in the php.ini I have
; extension_dir = "./"
I tried to set to other directories, but I have no idea where my  
extensions are.

Last try I installed php like this
sudo port install mysql5 +server
sudo port install apache2
sudo port install php5-devel +apache2+mysql5

and before like this (that would be what I prefer)
sudo port install php5-devel +apache2+macosx+mysql5+pear 
+postgresql83+sqlite
and I also tried with 20 different variations.
I have uninstalled and deleted everything related to macports (like  
written in the FAQ) twice
And I have no Idea what I can do else, I feel very helpless

So the questions would be
Where does /extensions/no-debug-non-zts-20090115/ come from
Where do I really find my extension dir, so that I can use mysql and  
sqlite and stuff like that (also ImageMagick in future, but thats  
another thing)
Or what do I have to change (Portfile ?!) so that there is a  
progress ?!?

Thanks you very much in advance :D

From face at CentosPrime.COM  Mon Jun  8 06:55:17 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Mon, 08 Jun 2009 06:55:17 -0700
Subject: Reverting to previous ports - mysql5
In-Reply-To: <D6FC8DC0-BE5D-4A69-BF66-29BEF4C908F4@macports.org>
References: <ACDC7F11-A8AA-43AA-9ECF-BA33E281987C@CentosPrime.COM>
	<D6FC8DC0-BE5D-4A69-BF66-29BEF4C908F4@macports.org>
Message-ID: <2071BCA6-9BF4-4899-BEC2-032EDF2A469F@CentosPrime.COM>

On 2009-06-07 , at 13:17 , Ryan Schmidt wrote:

>> This is on my 10.3 system.
>>
>> I unfortunately installed mysql5-server on my 10.3.9 system after  
>> getting an "obsolete +server" message.
>>
>> My startup files have become confused.
>
> Sorry about that. I did not test on 10.3. I can try to do so in a  
> few days. What error messages are you encountering?



admin at x:admin:133 $ sudo port upgrade outdated
--->  Fetching mysql5
--->  Attempting to fetch mysql-5.0.82.tar.gz from http://mysql.mirrors.pair.com/Downloads/MySQL-5.0/
--->  Verifying checksum(s) for mysql5
--->  Extracting mysql5
--->  Applying patches to mysql5
--->  Configuring mysql5
The +server variant is obsolete. Please install the mysql5-server port  
instead.
--->  Building mysql5
--->  Staging mysql5 into destroot
--->  Deactivating mysql5 @5.0.81_0+server
--->  Installing mysql5 @5.0.82_0+server
--->  Activating mysql5 @5.0.82_0+server
--->  Cleaning mysql5
admin at x:admin:134 $

at this point I can't "talk" to the previous version of mysql5 using  
mysql or mysqladmin...

admin at x:mysql5:162 $ mysql -u face -p
Enter password:
ERROR 1251: Client does not support authentication protocol requested  
by server; consider upgrading MySQL client
admin at x:mysql5:163 $ ps -axww | grep sql
21334 std  S      0:00.01 sh /opt/local/bin/mysqld_safe --datadir=/var/ 
mysql --pid-file=/var/mysql/FOO.pid
21372 std  S      0:07.13 /opt/local/libexec/mysqld --basedir=/opt/ 
local --datadir=/var/mysql --user=mysql --pid-file=/var/mysql/FOO.pid  
--port=3306 --socket=/tmp/mysql.sock
28761 std  R+     0:00.00 grep sql

There is no way to stop/start the old MySQL5 since the startup item is  
gone...

admin at x:mysql5:166 $ ls /Library/StartupItems
apache2/

OK - so I "kill"ed the old mysql5. Still have no working command line  
tools yet...

admin at x:mysql5:169 $ mysql -u face -p
Enter password:
ERROR 1251: Client does not support authentication protocol requested  
by server; consider upgrading MySQL client

admin at x:admin:134 $ sudo port install mysql5-server
--->  Fetching mysql5-server
--->  Verifying checksum(s) for mysql5-server
--->  Extracting mysql5-server
--->  Configuring mysql5-server
--->  Building mysql5-server
--->  Staging mysql5-server into destroot
--->  Creating systemstarter control script
###########################################################
# A startup item has been generated that will aid in
# starting mysql5-server with SystemStarter. It is disabled
# by default. Add the following line to /etc/hostconfig
# or /opt/local/etc/rc.conf to start it at startup:
#
# MYSQL5-SERVER=-YES-
###########################################################
--->  Installing mysql5-server @5.0.82_0
******************************************************
* In order to setup the database, you might want to run
* sudo -u mysql mysql_install_db5
* if this is a new install
******************************************************
--->  Activating mysql5-server @5.0.82_0
--->  Cleaning mysql5-server
admin at x:admin:135 $

add the MYSQL5-SERVER line to /etc/hostconfig

now we try to start mysql...

admin at x:admin:135 $ sudo SystemStarter start mysql5-server
Welcome to Macintosh.
/System/Library/StartupItems/SecurityServer/SecurityServer: line 41:  
MYSQL5-SERVER=-YES~: command not found
/System/Library/StartupItems/Network/Network: line 41: MYSQL5-SERVER=- 
YES~: command not found
Starting SecurityServer
Initializing network
/System/Library/StartupItems/Disks/Disks: line 41: MYSQL5-SERVER=- 
YES~: command not found
Checking disks
/System/Library/StartupItems/NIS/NIS: line 41: MYSQL5-SERVER=-YES~:  
command not found
/System/Library/StartupItems/NFS/NFS: line 41: MYSQL5-SERVER=-YES~:  
command not found
lockfile: Sorry, giving up on "/var/run/NFS.StartupItem"
/Library/StartupItems/mysql5-server/mysql5-server: line 41: MYSQL5- 
SERVER=-YES~: command not found
Startup complete.
Hangup
admin at x:admin:136 $

I copied/pasted the MYSQL5-SERVER line from the terminal.
This is copied/pasted from /etc/hostconfig

  MYSQL5-SERVER=-YES-

For the time being I have manually started mysql on the 10.3 system  
and will hand start if we have to reboot.

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From ryandesign at macports.org  Mon Jun  8 11:27:34 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 8 Jun 2009 13:27:34 -0500
Subject: Reverting to previous ports - mysql5
In-Reply-To: <2071BCA6-9BF4-4899-BEC2-032EDF2A469F@CentosPrime.COM>
References: <ACDC7F11-A8AA-43AA-9ECF-BA33E281987C@CentosPrime.COM>
	<D6FC8DC0-BE5D-4A69-BF66-29BEF4C908F4@macports.org>
	<2071BCA6-9BF4-4899-BEC2-032EDF2A469F@CentosPrime.COM>
Message-ID: <7A560FF1-110B-49AB-8DB9-79C03949C76A@macports.org>

On Jun 8, 2009, at 08:55, Chris Janton wrote:

> On 2009-06-07 , at 13:17 , Ryan Schmidt wrote:
>
>>> This is on my 10.3 system.
>>>
>>> I unfortunately installed mysql5-server on my 10.3.9 system after  
>>> getting an "obsolete +server" message.
>>>
>>> My startup files have become confused.
>>
>> Sorry about that. I did not test on 10.3. I can try to do so in a  
>> few days. What error messages are you encountering?
>
> admin at x:admin:133 $ sudo port upgrade outdated
> --->  Fetching mysql5
> --->  Attempting to fetch mysql-5.0.82.tar.gz from http:// 
> mysql.mirrors.pair.com/Downloads/MySQL-5.0/
> --->  Verifying checksum(s) for mysql5
> --->  Extracting mysql5
> --->  Applying patches to mysql5
> --->  Configuring mysql5
> The +server variant is obsolete. Please install the mysql5-server  
> port instead.
> --->  Building mysql5
> --->  Staging mysql5 into destroot
> --->  Deactivating mysql5 @5.0.81_0+server
> --->  Installing mysql5 @5.0.82_0+server
> --->  Activating mysql5 @5.0.82_0+server
> --->  Cleaning mysql5
> admin at x:admin:134 $
>
> at this point I can't "talk" to the previous version of mysql5  
> using mysql or mysqladmin...
>
> admin at x:mysql5:162 $ mysql -u face -p
> Enter password:
> ERROR 1251: Client does not support authentication protocol  
> requested by server; consider upgrading MySQL client
> admin at x:mysql5:163 $ ps -axww | grep sql
> 21334 std  S      0:00.01 sh /opt/local/bin/mysqld_safe --datadir=/ 
> var/mysql --pid-file=/var/mysql/FOO.pid
> 21372 std  S      0:07.13 /opt/local/libexec/mysqld --basedir=/opt/ 
> local --datadir=/var/mysql --user=mysql --pid-file=/var/mysql/ 
> FOO.pid --port=3306 --socket=/tmp/mysql.sock
> 28761 std  R+     0:00.00 grep sql
>
> There is no way to stop/start the old MySQL5 since the startup item  
> is gone...
>
> admin at x:mysql5:166 $ ls /Library/StartupItems
> apache2/

Well, you should stop the old version of MySQL (or any server port)  
before installing the new version. To minimize downtime you can

sudo port install mysql5

which will build and install the new version (which is what should  
take the bulk of the time) but will fail to activate it because the  
old version is still active. Then you can

* turn the old MySQL off (if you were on 10.4+ you would use "sudo  
port unload mysql5")
* deactivate the old mysql5
* activate the new mysql5 and mysql5-server
* start the new MySQL ("sudo port load mysql5-server" on 10.4+)

Since < 10.4 doesn't have launchd and systemstarter doesn't have  
dynamic starting and stopping of services you either kill and start  
the processes manually or restart the computer after editing your  
hostconfig.


> OK - so I "kill"ed the old mysql5. Still have no working command  
> line tools yet...
>
> admin at x:mysql5:169 $ mysql -u face -p
> Enter password:
> ERROR 1251: Client does not support authentication protocol  
> requested by server; consider upgrading MySQL client

Hmm. I haven't checked the changelog. Not sure if something about the  
authentication protocol changed in this version.


> admin at x:admin:134 $ sudo port install mysql5-server
> --->  Fetching mysql5-server
> --->  Verifying checksum(s) for mysql5-server
> --->  Extracting mysql5-server
> --->  Configuring mysql5-server
> --->  Building mysql5-server
> --->  Staging mysql5-server into destroot
> --->  Creating systemstarter control script
> ###########################################################
> # A startup item has been generated that will aid in
> # starting mysql5-server with SystemStarter. It is disabled
> # by default. Add the following line to /etc/hostconfig
> # or /opt/local/etc/rc.conf to start it at startup:
> #
> # MYSQL5-SERVER=-YES-
> ###########################################################
> --->  Installing mysql5-server @5.0.82_0
> ******************************************************
> * In order to setup the database, you might want to run
> * sudo -u mysql mysql_install_db5
> * if this is a new install
> ******************************************************
> --->  Activating mysql5-server @5.0.82_0
> --->  Cleaning mysql5-server
> admin at x:admin:135 $
>
> add the MYSQL5-SERVER line to /etc/hostconfig
>
> now we try to start mysql...
>
> admin at x:admin:135 $ sudo SystemStarter start mysql5-server
> Welcome to Macintosh.
> /System/Library/StartupItems/SecurityServer/SecurityServer: line  
> 41: MYSQL5-SERVER=-YES~: command not found
> /System/Library/StartupItems/Network/Network: line 41: MYSQL5- 
> SERVER=-YES~: command not found
> Starting SecurityServer
> Initializing network
> /System/Library/StartupItems/Disks/Disks: line 41: MYSQL5-SERVER=- 
> YES~: command not found
> Checking disks
> /System/Library/StartupItems/NIS/NIS: line 41: MYSQL5-SERVER=-YES~:  
> command not found
> /System/Library/StartupItems/NFS/NFS: line 41: MYSQL5-SERVER=-YES~:  
> command not found
> lockfile: Sorry, giving up on "/var/run/NFS.StartupItem"
> /Library/StartupItems/mysql5-server/mysql5-server: line 41: MYSQL5- 
> SERVER=-YES~: command not found
> Startup complete.
> Hangup
> admin at x:admin:136 $
>
> I copied/pasted the MYSQL5-SERVER line from the terminal.
> This is copied/pasted from /etc/hostconfig
>
>  MYSQL5-SERVER=-YES-
>
> For the time being I have manually started mysql on the 10.3 system  
> and will hand start if we have to reboot.

I am guessing it is using the port name as the key for the hostconfig  
file, and that the hostconfig file does not support hyphens in its  
variable names. So that would be a problem. Perhaps I can tell it to  
continue to use the key "mysql5" ("startupitem.name mysql5"?) You can  
try adding that to the mysql5-server port already if you want, but I  
will also test when I'm back at my Panther machine tonight.


From frstan at bellsouth.net  Mon Jun  8 14:22:58 2009
From: frstan at bellsouth.net (William Davis)
Date: Mon, 8 Jun 2009 17:22:58 -0400
Subject: OT: snowleopard pricing
Message-ID: <6BE11E9F-B882-405A-9171-B0BE27BEA62C@bellsouth.net>

This is off topic and I do it fyi, not expecting discussion though it  
may effect the migration rate which will effect the need for 1.8:
Snow Leopard will cost $39 as an upgrade from Leopard -- news from  
devconf. Didnt see a release date.


William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From erwan at rail.eu.org  Mon Jun  8 14:26:01 2009
From: erwan at rail.eu.org (Erwan David)
Date: Mon, 8 Jun 2009 23:26:01 +0200
Subject: OT: snowleopard pricing
In-Reply-To: <6BE11E9F-B882-405A-9171-B0BE27BEA62C@bellsouth.net>
References: <6BE11E9F-B882-405A-9171-B0BE27BEA62C@bellsouth.net>
Message-ID: <20090608212601.GG1498@rail.eu.org>

Le Mon  8/06/2009, William Davis disait
> This is off topic and I do it fyi, not expecting discussion though it  
> may effect the migration rate which will effect the need for 1.8:
> Snow Leopard will cost $39 as an upgrade from Leopard -- news from  
> devconf. Didnt see a release date.
>

Apple store says September.

And 8,95 ? (should be the same in $ :( for us europeans)) for macs bought 
after today.

-- 
Erwan

From talklists at newgeo.com  Mon Jun  8 14:26:36 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 8 Jun 2009 14:26:36 -0700
Subject: OT: snowleopard pricing
In-Reply-To: <6BE11E9F-B882-405A-9171-B0BE27BEA62C@bellsouth.net>
References: <6BE11E9F-B882-405A-9171-B0BE27BEA62C@bellsouth.net>
Message-ID: <38C8B73F-8802-4ABF-A1DC-EFC972D97EDF@newgeo.com>

Are you sure about that cost?  I was reading http://www.macworld.com/article/140897/2009/06/keynote.html 
  and the price noted there is $29 for Leopard users. Family pack at  
$49.  I was not able to catch a release date either.

On Jun 8, 2009, at 2:22 PM, William Davis wrote:

> This is off topic and I do it fyi, not expecting discussion though  
> it may effect the migration rate which will effect the need for 1.8:
> Snow Leopard will cost $39 as an upgrade from Leopard -- news from  
> devconf. Didnt see a release date.

-- 
Scott * If you contact me off list replace talklists@ with scott@ *


From ram at macports.org  Mon Jun  8 14:32:44 2009
From: ram at macports.org (Adam Mercer)
Date: Mon, 8 Jun 2009 16:32:44 -0500
Subject: OT: snowleopard pricing
In-Reply-To: <6BE11E9F-B882-405A-9171-B0BE27BEA62C@bellsouth.net>
References: <6BE11E9F-B882-405A-9171-B0BE27BEA62C@bellsouth.net>
Message-ID: <799406d60906081432v265cb524n245646ca1431fdb5@mail.gmail.com>

On Mon, Jun 8, 2009 at 16:22, William Davis<frstan at bellsouth.net> wrote:
> This is off topic and I do it fyi, not expecting discussion though it may
> effect the migration rate which will effect the need for 1.8:
> Snow Leopard will cost $39 as an upgrade from Leopard -- news from devconf.
> Didnt see a release date.

Apple have updated there web page with all the details:

<http://www.apple.com/macosx>

It'll be released in September 2009 and will be $29 for Leopard users.

Cheers

Adam

From frstan at bellsouth.net  Mon Jun  8 18:26:23 2009
From: frstan at bellsouth.net (William Davis)
Date: Mon, 8 Jun 2009 21:26:23 -0400
Subject: OT: snowleopard pricing
In-Reply-To: <38C8B73F-8802-4ABF-A1DC-EFC972D97EDF@newgeo.com>
References: <6BE11E9F-B882-405A-9171-B0BE27BEA62C@bellsouth.net>
	<38C8B73F-8802-4ABF-A1DC-EFC972D97EDF@newgeo.com>
Message-ID: <7908C58A-3575-4D51-A4DC-C53FA5150374@bellsouth.net>


On Jun 8, 2009, at 5:26 PM, Scott Haneda wrote:

> Are you sure about that cost?  I was reading http://www.macworld.com/article/140897/2009/06/keynote.html 
>  and the price noted there is $29 for Leopard users. Family pack at  
> $49.  I was not able to catch a release date either.
>
> On Jun 8, 2009, at 2:22 PM, William Davis wrote:
>
>> This is off topic and I do it fyi, not expecting discussion though  
>> it may effect the migration rate which will effect the need for 1.8:
>> Snow Leopard will cost $39 as an upgrade from Leopard -- news from  
>> devconf. Didnt see a release date.
>
> -- 
> Scott * If you contact me off list replace talklists@ with scott@ *
>

You are correct. I believed a news report.  Apple has now posted it on  
their site and it is as you say $29.00. :)

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From ohce86 at kitcarson.net  Mon Jun  8 19:02:05 2009
From: ohce86 at kitcarson.net (Timothy Goins)
Date: Mon, 8 Jun 2009 20:02:05 -0600
Subject: OT: snowleopard pricing
In-Reply-To: <7908C58A-3575-4D51-A4DC-C53FA5150374@bellsouth.net>
References: <6BE11E9F-B882-405A-9171-B0BE27BEA62C@bellsouth.net>
	<38C8B73F-8802-4ABF-A1DC-EFC972D97EDF@newgeo.com>
	<7908C58A-3575-4D51-A4DC-C53FA5150374@bellsouth.net>
Message-ID: <6F2952D2-CC41-4D01-80D2-B53734F89805@kitcarson.net>

$49 for the Family Pack.

Timothy Goins
ohce86 at kitcarson.net




On Jun 8, 2009, at 7:26 PM, William Davis wrote:

>
> On Jun 8, 2009, at 5:26 PM, Scott Haneda wrote:
>
>> Are you sure about that cost?  I was reading http://www.macworld.com/article/140897/2009/06/keynote.html 
>>  and the price noted there is $29 for Leopard users. Family pack at  
>> $49.  I was not able to catch a release date either.
>>
>> On Jun 8, 2009, at 2:22 PM, William Davis wrote:
>>
>>> This is off topic and I do it fyi, not expecting discussion though  
>>> it may effect the migration rate which will effect the need for 1.8:
>>> Snow Leopard will cost $39 as an upgrade from Leopard -- news from  
>>> devconf. Didnt see a release date.
>>
>> -- 
>> Scott * If you contact me off list replace talklists@ with scott@ *
>>
>
> You are correct. I believed a news report.  Apple has now posted it  
> on their site and it is as you say $29.00. :)
>
> William Davis
> frstanATbellsouthDOTnet
> Mac OS X.5.7 Darwin 9.7.0
> XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
> Mac Mini Intel Duo @ 1.86 GHz
>
> Mundus vult decepi, ego non
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090608/76eb7934/attachment.html>

From dweber at macports.org  Mon Jun  8 22:20:06 2009
From: dweber at macports.org (Darren Weber)
Date: Mon, 8 Jun 2009 22:20:06 -0700
Subject: OSX Upgrades: Snow Leopard
Message-ID: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>

What happens to a MacPorts installation when we install a distribution
upgrade to OSX, say Leopard to Snow Leopard?  Do we need to backup the
MacPorts installation, or is the ${prefix} path immune to the upgrade?  What
about startup items (launchd or anything that violates the mtree)?

Thanks in advance,
Darren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090608/6d60f219/attachment.html>

From tim.visher at gmail.com  Tue Jun  9 05:15:51 2009
From: tim.visher at gmail.com (Tim Visher)
Date: Tue, 9 Jun 2009 08:15:51 -0400
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
Message-ID: <c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>

Hi Darren,

On Tue, Jun 9, 2009 at 1:20 AM, Darren Weber<dweber at macports.org> wrote:
> What happens to a MacPorts installation when we install a distribution
> upgrade to OSX, say Leopard to Snow Leopard?  Do we need to backup the
> MacPorts installation, or is the ${prefix} path immune to the upgrade?  What
> about startup items (launchd or anything that violates the mtree)?

I can't be sure technically but I've upgraded OS X for every release
since MacPorts came out (Back when it was called DarwinPorts. Jaguar?)
and I've never had to reinstall it.  So, anecdotally I think you're
safe.  If you care very deeply you should of course back it up just in
case.

-- 

In Christ,

Timmy V.

http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail

From khillig at umich.edu  Tue Jun  9 05:32:11 2009
From: khillig at umich.edu (Kurt Hillig)
Date: Tue, 9 Jun 2009 08:32:11 -0400 (EDT)
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.0906090827400.18688@joust.gpcc.itd.umich.edu>

On the other hand I recently upgraded from 10.4 to 10.5 and my machine was 
horribly unstable until I blew away the MacPorts install.  I'm not sure 
why this was, and I didn't have the time or gumption to run a lot of 
diagnostics, so it could well be that something less drastic would have 
sufficed.

Which I guess really means that it works OK when it works, except for when 
it doesn't...

                             Dr. Kurt Hillig
   UMNet Administration     I always tell the    Fax (734)763-4050
  University of Michigan     absolute truth,    Phone (734)647-8778
Ann Arbor, MI  48105-3640    as I see it.   EMail khillig(at)umich.edu

  > Computers were invented to help people waste more time faster <

On Tue, 9 Jun 2009, Tim Visher wrote:

> Hi Darren,
>
> On Tue, Jun 9, 2009 at 1:20 AM, Darren Weber<dweber at macports.org> wrote:
>> What happens to a MacPorts installation when we install a distribution
>> upgrade to OSX, say Leopard to Snow Leopard?  Do we need to backup the
>> MacPorts installation, or is the ${prefix} path immune to the upgrade?  What
>> about startup items (launchd or anything that violates the mtree)?
>
> I can't be sure technically but I've upgraded OS X for every release
> since MacPorts came out (Back when it was called DarwinPorts. Jaguar?)
> and I've never had to reinstall it.  So, anecdotally I think you're
> safe.  If you care very deeply you should of course back it up just in
> case.
>
> -- 
>
> In Christ,
>
> Timmy V.
>
> http://burningones.com/
> http://five.sentenc.es/ - Spend less time on e-mail
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
> !DSPAM:4a2e528223873798219729!
>
>
>
>

From vince at macports.org  Tue Jun  9 05:45:42 2009
From: vince at macports.org (vincent habchi)
Date: Tue, 9 Jun 2009 14:45:42 +0200
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <Pine.LNX.4.64.0906090827400.18688@joust.gpcc.itd.umich.edu>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
	<Pine.LNX.4.64.0906090827400.18688@joust.gpcc.itd.umich.edu>
Message-ID: <25C36B12-63E2-44EE-9741-FAB0EDD932EA@macports.org>

Le 9 juin 09 ? 14:32, Kurt Hillig a ?crit :

> On the other hand I recently upgraded from 10.4 to 10.5 and my  
> machine was horribly unstable until I blew away the MacPorts  
> install.  I'm not sure why this was, and I didn't have the time or  
> gumption to run a lot of diagnostics, so it could well be that  
> something less drastic would have sufficed.

When you upgrade, the libraries change, so you may have to recompile  
some of your bricks. For example, when SL will be out, we'll have, at  
least, a 64-bit API to QuickTime, so we'll be able to compile  
WxWindows safely in 64-bit mode. But maybe also the old AGL will  
vanished, and all ports that are based on it will have to be rebuild,  
etc.

Vincent

From face at CentosPrime.COM  Tue Jun  9 06:17:12 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Tue, 09 Jun 2009 06:17:12 -0700
Subject: Reverting to previous ports - mysql5
In-Reply-To: <7A560FF1-110B-49AB-8DB9-79C03949C76A@macports.org>
References: <ACDC7F11-A8AA-43AA-9ECF-BA33E281987C@CentosPrime.COM>
	<D6FC8DC0-BE5D-4A69-BF66-29BEF4C908F4@macports.org>
	<2071BCA6-9BF4-4899-BEC2-032EDF2A469F@CentosPrime.COM>
	<7A560FF1-110B-49AB-8DB9-79C03949C76A@macports.org>
Message-ID: <683AB3C2-5003-4802-935A-2480CA03361A@CentosPrime.COM>

On 2009-06-08 , at 11:27 , Ryan Schmidt wrote:

>> I copied/pasted the MYSQL5-SERVER line from the terminal.
>> This is copied/pasted from /etc/hostconfig
>>
>> MYSQL5-SERVER=-YES-
>>
>> For the time being I have manually started mysql on the 10.3 system  
>> and will hand start if we have to reboot.
>
> I am guessing it is using the port name as the key for the  
> hostconfig file, and that the hostconfig file does not support  
> hyphens in its variable names. So that would be a problem. Perhaps I  
> can tell it to continue to use the key "mysql5" ("startupitem.name  
> mysql5"?) You can try adding that to the mysql5-server port already  
> if you want, but I will also test when I'm back at my Panther  
> machine tonight.


That certainly did the trick - to think a "-" in a name should be such  
a problem...


$ diff Portfile Portfile~
33d32
< startupitem.name	mysql5

add MYSQL5=-YES- to /etc/hostconfig


$ sudo SystemStarter -v start mysql5
Welcome to Macintosh.
Starting SecurityServer
Initializing network
Checking disks
lockfile: Sorry, giving up on "/var/run/NFS.StartupItem"
Starting mysql5
Starting MySQL. SUCCESS!
Startup complete.
Hangup
$ ps -axww | grep sql
13682  ??  S      0:00.03 sh /opt/local/bin/mysqld_safe
13720  ??  S      0:00.44 /opt/local/libexec/mysqld --basedir=/opt/local
13722 std  R+     0:00.01 grep sql
$ sudo SystemStarter -v restart mysql5
Welcome to Macintosh.
Restarting mysql5
Stopping mysql5
Shutting down MySQL.. SUCCESS!
Starting mysql5
Starting MySQL.Waiting for mysql5
  SUCCESS!
Startup complete.
Hangup

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From jdmuys at kleegroup.com  Tue Jun  9 06:57:46 2009
From: jdmuys at kleegroup.com (Jean-Denis Muys)
Date: Tue, 09 Jun 2009 15:57:46 +0200
Subject: MacPorts on Snow Leopard
Message-ID: <C65436FA.4AD4%jdmuys@kleegroup.com>

Hello,

I am a Mac developer, and a MacPorts user, though not a Unix programmer to
any large extent.

Since the release of the WWDC developer release of Snow Leopard, I have
found it stable enough that I'm probably going to spend most of my time
running it.

So I would like to install MacPorts on it. Yet, very wisely, the current
installer refuses to do that.

So is it possible to use MacPorts on Snow Leopard yet?
What would that involve?

Of course, as you can guess, I am ready to live on the bleeding edge.

Many thanks,

Jean-Denis

PS: I don't think this request does or most answers would violate the NDA,
but I'm ready to move this conversation to private mail and/or to the Apple
developer forums. Actually, now that I mention it, I will cross post this
request over there :-)



From jmr at macports.org  Tue Jun  9 08:19:18 2009
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Jun 2009 01:19:18 +1000
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
Message-ID: <4A2E7D76.10500@macports.org>

On 2009-6-9 22:15, Tim Visher wrote:
> Hi Darren,
> 
> On Tue, Jun 9, 2009 at 1:20 AM, Darren Weber<dweber at macports.org> wrote:
>> What happens to a MacPorts installation when we install a distribution
>> upgrade to OSX, say Leopard to Snow Leopard?  Do we need to backup the
>> MacPorts installation, or is the ${prefix} path immune to the upgrade?  What
>> about startup items (launchd or anything that violates the mtree)?
> 
> I can't be sure technically but I've upgraded OS X for every release
> since MacPorts came out (Back when it was called DarwinPorts. Jaguar?)
> and I've never had to reinstall it.  So, anecdotally I think you're
> safe.  If you care very deeply you should of course back it up just in
> case.

Both MacPorts base and each port are built for a specific major OS
version. Maybe they'll work acceptably on a newer version, maybe they
won't. The only safe option has always been to record your installed
ports, uninstall MacPorts entirely, install the correct base version for
your OS, then install your ports again.

- Josh

From jmr at macports.org  Tue Jun  9 08:21:40 2009
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Jun 2009 01:21:40 +1000
Subject: MacPorts on Snow Leopard
In-Reply-To: <C65436FA.4AD4%jdmuys@kleegroup.com>
References: <C65436FA.4AD4%jdmuys@kleegroup.com>
Message-ID: <4A2E7E04.6050406@macports.org>

On 2009-6-9 23:57, Jean-Denis Muys wrote:
> Hello,
> 
> I am a Mac developer, and a MacPorts user, though not a Unix programmer to
> any large extent.
> 
> Since the release of the WWDC developer release of Snow Leopard, I have
> found it stable enough that I'm probably going to spend most of my time
> running it.
> 
> So I would like to install MacPorts on it. Yet, very wisely, the current
> installer refuses to do that.
> 
> So is it possible to use MacPorts on Snow Leopard yet?
> What would that involve?
> 
> Of course, as you can guess, I am ready to live on the bleeding edge.

If you install from svn trunk, that has a much better chance of working
well on Snow Leopard than the current release:

<http://svn.macports.org/repository/macports/trunk/base/>

- Josh

From vince at macports.org  Tue Jun  9 10:16:23 2009
From: vince at macports.org (vincent habchi)
Date: Tue, 9 Jun 2009 19:16:23 +0200
Subject: MacPorts on Snow Leopard
In-Reply-To: <C65436FA.4AD4%jdmuys@kleegroup.com>
References: <C65436FA.4AD4%jdmuys@kleegroup.com>
Message-ID: <18150B49-E52C-4414-AE17-1E90611260F4@macports.org>

(repost)

Hello,

Le 9 juin 09 ? 15:57, Jean-Denis Muys a ?crit :

> PS: I don't think this request does or most answers would violate  
> the NDA,
> but I'm ready to move this conversation to private mail and/or to  
> the Apple
> developer forums. Actually, now that I mention it, I will cross post  
> this
> request over there :-)

I am wondering how many macports developers out there have access to  
Snow L.

Vincent

From dweber at macports.org  Tue Jun  9 13:36:54 2009
From: dweber at macports.org (Darren Weber)
Date: Tue, 9 Jun 2009 13:36:54 -0700
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <4A2E7D76.10500@macports.org>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
	<4A2E7D76.10500@macports.org>
Message-ID: <b808b3510906091336v59bc5c5cnbea2cf34d937472c@mail.gmail.com>

What's the recommended series of command lines for that?

Thanks!
Darren

On Tue, Jun 9, 2009 at 8:19 AM, Joshua Root <jmr at macports.org> wrote:

> On 2009-6-9 22:15, Tim Visher wrote:
> > Hi Darren,
> >
> > On Tue, Jun 9, 2009 at 1:20 AM, Darren Weber<dweber at macports.org> wrote:
> >> What happens to a MacPorts installation when we install a distribution
> >> upgrade to OSX, say Leopard to Snow Leopard?  Do we need to backup the
> >> MacPorts installation, or is the ${prefix} path immune to the upgrade?
>  What
> >> about startup items (launchd or anything that violates the mtree)?
> >
> > I can't be sure technically but I've upgraded OS X for every release
> > since MacPorts came out (Back when it was called DarwinPorts. Jaguar?)
> > and I've never had to reinstall it.  So, anecdotally I think you're
> > safe.  If you care very deeply you should of course back it up just in
> > case.
>
> Both MacPorts base and each port are built for a specific major OS
> version. Maybe they'll work acceptably on a newer version, maybe they
> won't. The only safe option has always been to record your installed
> ports, uninstall MacPorts entirely, install the correct base version for
> your OS, then install your ports again.
>
> - Josh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090609/5935c42c/attachment.html>

From jeremyhu at macports.org  Tue Jun  9 15:07:55 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Tue, 9 Jun 2009 15:07:55 -0700
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <b808b3510906091336v59bc5c5cnbea2cf34d937472c@mail.gmail.com>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
	<4A2E7D76.10500@macports.org>
	<b808b3510906091336v59bc5c5cnbea2cf34d937472c@mail.gmail.com>
Message-ID: <D4C2C9E9-8044-41E4-B210-99868D528E59@macports.org>

Here's what I did:

cd /opt/local/var/macports/software
/bin/ls -1d * > ~/todo.mp
cd
sudo mv /opt/local /var/tmp/old_macports
cd src/macports/trunk/base
./configure && make && sudo make install
for f in $(cat todo.mp ); do [[ -d /opt/local/var/macports/software/ 
$f ]] || sudo port -v install $f; done

I'm sure there's something ports option to do that, but /shrug...


On Jun 9, 2009, at 13:36, Darren Weber wrote:

> What's the recommended series of command lines for that?
>
> Thanks!
> Darren
>
> On Tue, Jun 9, 2009 at 8:19 AM, Joshua Root <jmr at macports.org> wrote:
>
>> On 2009-6-9 22:15, Tim Visher wrote:
>>> Hi Darren,
>>>
>>> On Tue, Jun 9, 2009 at 1:20 AM, Darren Weber<dweber at macports.org>  
>>> wrote:
>>>> What happens to a MacPorts installation when we install a  
>>>> distribution
>>>> upgrade to OSX, say Leopard to Snow Leopard?  Do we need to  
>>>> backup the
>>>> MacPorts installation, or is the ${prefix} path immune to the  
>>>> upgrade?
>> What
>>>> about startup items (launchd or anything that violates the mtree)?
>>>
>>> I can't be sure technically but I've upgraded OS X for every release
>>> since MacPorts came out (Back when it was called DarwinPorts.  
>>> Jaguar?)
>>> and I've never had to reinstall it.  So, anecdotally I think you're
>>> safe.  If you care very deeply you should of course back it up  
>>> just in
>>> case.
>>
>> Both MacPorts base and each port are built for a specific major OS
>> version. Maybe they'll work acceptably on a newer version, maybe they
>> won't. The only safe option has always been to record your installed
>> ports, uninstall MacPorts entirely, install the correct base  
>> version for
>> your OS, then install your ports again.
>>
>> - Josh
>>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From sck at nogas.org  Tue Jun  9 15:41:05 2009
From: sck at nogas.org (Scott C. Kennedy)
Date: Tue, 09 Jun 2009 15:41:05 -0700
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <D4C2C9E9-8044-41E4-B210-99868D528E59@macports.org>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>	<4A2E7D76.10500@macports.org>	<b808b3510906091336v59bc5c5cnbea2cf34d937472c@mail.gmail.com>
	<D4C2C9E9-8044-41E4-B210-99868D528E59@macports.org>
Message-ID: <4A2EE501.4070303@nogas.org>

You will lose your variants, if you made any custom builds. I keep a
shell script with the variants and ports that I use up to date, plus I
keep and compare the "port installed" output from before and after to
ensure I didn't miss anything.

Scott

Jeremy Huddleston wrote:
> Here's what I did:
>
> cd /opt/local/var/macports/software
> /bin/ls -1d * > ~/todo.mp
> cd
> sudo mv /opt/local /var/tmp/old_macports
> cd src/macports/trunk/base
> ./configure && make && sudo make install
> for f in $(cat todo.mp ); do [[ -d /opt/local/var/macports/software/$f
> ]] || sudo port -v install $f; done
>
> I'm sure there's something ports option to do that, but /shrug...
>
>
> On Jun 9, 2009, at 13:36, Darren Weber wrote:
>
>> What's the recommended series of command lines for that?
>>
>> Thanks!
>> Darren
>>
>> On Tue, Jun 9, 2009 at 8:19 AM, Joshua Root <jmr at macports.org> wrote:
>>
>>> On 2009-6-9 22:15, Tim Visher wrote:
>>>> Hi Darren,
>>>>
>>>> On Tue, Jun 9, 2009 at 1:20 AM, Darren Weber<dweber at macports.org>
>>>> wrote:
>>>>> What happens to a MacPorts installation when we install a
>>>>> distribution
>>>>> upgrade to OSX, say Leopard to Snow Leopard?  Do we need to backup
>>>>> the
>>>>> MacPorts installation, or is the ${prefix} path immune to the
>>>>> upgrade?
>>> What
>>>>> about startup items (launchd or anything that violates the mtree)?
>>>>
>>>> I can't be sure technically but I've upgraded OS X for every release
>>>> since MacPorts came out (Back when it was called DarwinPorts. Jaguar?)
>>>> and I've never had to reinstall it.  So, anecdotally I think you're
>>>> safe.  If you care very deeply you should of course back it up just in
>>>> case.
>>>
>>> Both MacPorts base and each port are built for a specific major OS
>>> version. Maybe they'll work acceptably on a newer version, maybe they
>>> won't. The only safe option has always been to record your installed
>>> ports, uninstall MacPorts entirely, install the correct base version
>>> for
>>> your OS, then install your ports again.
>>>
>>> - Josh
>>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From ryandesign at macports.org  Tue Jun  9 17:32:53 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 9 Jun 2009 19:32:53 -0500
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <D4C2C9E9-8044-41E4-B210-99868D528E59@macports.org>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
	<4A2E7D76.10500@macports.org>
	<b808b3510906091336v59bc5c5cnbea2cf34d937472c@mail.gmail.com>
	<D4C2C9E9-8044-41E4-B210-99868D528E59@macports.org>
Message-ID: <70082B35-E9EF-4D12-982C-15B17C8C9B6B@macports.org>

On Jun 9, 2009, at 17:07, Jeremy Huddleston wrote:

> On Jun 9, 2009, at 13:36, Darren Weber wrote:
>
>> What's the recommended series of command lines for that?
>
> Here's what I did:
>
> cd /opt/local/var/macports/software
> /bin/ls -1d * > ~/todo.mp
> cd
> sudo mv /opt/local /var/tmp/old_macports

Moving /opt/local aside is not sufficient to uninstall MacPorts. See  
proper uninstall instructions here:

http://trac.macports.org/wiki/FAQ#HowdoIremoveoruninstallMacPorts


> cd src/macports/trunk/base
> ./configure && make && sudo make install
> for f in $(cat todo.mp ); do [[ -d /opt/local/var/macports/software/ 
> $f ]] || sudo port -v install $f; done
>
> I'm sure there's something ports option to do that, but /shrug...

MacPorts doesn't include a command to help you rebuild an entire  
installation like this. This is unfortunate and makes it a rather  
involved process. But since upgrading to a new major OS version is a  
task users don't perform often, I don't think any work has gone into  
making this easier.


I think the key to solving this would be to have MacPorts record more  
information in the registry about each port that was installed,  
including what version of Mac OS X it was done on, with what version  
of Xcode, and even record several of the settings from macports.conf  
that were in effect at the time. Then we can make "port outdated"  
recognize that if the current OS is a major version later than the  
one a port was installed with, the port needs to be rebuilt.


From ryandesign at macports.org  Tue Jun  9 17:44:04 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 9 Jun 2009 19:44:04 -0500
Subject: PHP 5.3.0RC2 +mysql, no extension_dir = no-debug-non-zts-20090115/
In-Reply-To: <E853CD1B-5962-46D6-8DBB-8E0089441A33@gmx.de>
References: <E853CD1B-5962-46D6-8DBB-8E0089441A33@gmx.de>
Message-ID: <DEBE4B0D-8811-4A2F-88D1-94FB21D87C7E@macports.org>

On Jun 8, 2009, at 06:44, Sebastian Wojtowicz wrote:

> I'm kind of a newbie in Mac but I have managed to install several  
> PHP versions with mysql and stuff like that before.
> Only now, I can't install the new PHP version.
>
> Well ok, I can, but somehow php is always looking for the  
> extensions in
> /opt/local/lib/php/extensions/no-debug-non-zts-20090115/
> This directory doesn't exist. Only
> /opt/local/lib/php/
> exists. So when I include an extension, by taking away the ";" in  
> the php.ini, I get a warning
> PHP Warning:  PHP Startup: Unable to load dynamic library '/opt/ 
> local/lib/php/extensions/no-debug-non-zts-20090115/....' ....
>
> I also find it strange, that this is the default directory. Where  
> does it come from ?! in the php.ini I have
> ; extension_dir = "./"
> I tried to set to other directories, but I have no idea where my  
> extensions are.
>
> Last try I installed php like this
> sudo port install mysql5 +server
> sudo port install apache2
> sudo port install php5-devel +apache2+mysql5
>
> and before like this (that would be what I prefer)
> sudo port install php5-devel +apache2+macosx+mysql5+pear 
> +postgresql83+sqlite
> and I also tried with 20 different variations.
> I have uninstalled and deleted everything related to macports (like  
> written in the FAQ) twice
> And I have no Idea what I can do else, I feel very helpless
>
> So the questions would be
> Where does /extensions/no-debug-non-zts-20090115/ come from
> Where do I really find my extension dir, so that I can use mysql  
> and sqlite and stuff like that (also ImageMagick in future, but  
> thats another thing)
> Or what do I have to change (Portfile ?!) so that there is a  
> progress ?!?

Welcome!

/opt/local/lib/php/extensions/no-debug-non-zts-20090115/ is the  
directory where PHP 5.3 extensions would be stored, if you had  
installed any. You haven't installed any extensions. All the variants  
you selected, such as +mysql5 and +postgresql83, currently build  
themselves into the php programs and libraries directly. They're  
always on. You don't need to change anything in the php.ini to enable  
them.

These variants will be removed from the php ports in the future to be  
replaced with separate ports which will install as extensions in the  
above mentioned directory. You still won't have to change anything in  
php.ini to enable them, since they will install small ini files of  
their own in /opt/local/var/db/php5 which PHP reads automatically in  
addition to the regular php.ini. If you're interested in more about  
this upcoming change, you can read the ticket:

http://trac.macports.org/ticket/19091







From lists+macports.org at elitists.org  Wed Jun 10 01:27:01 2009
From: lists+macports.org at elitists.org (Frank Even)
Date: Wed, 10 Jun 2009 03:27:01 -0500
Subject: error on trying to upgrade really old darwinports install
Message-ID: <5d62325b0906100127oe95cfb8h90a2aae00f193e99@mail.gmail.com>

Is there a method for upgrading an old darwinports install that was
installed on a MacBookPro that has been upgraded from 10.4 to 10.5?

I'm trying to run the selfupdate, it fails.  I've found some
references to changing "darwinports" in the rsync commands to
"macports," I've done that, but I'm failing with the same error
basically.

bash-3.2# port version
Version: 1.320

Here are the results of a failed "port -vd selfupdate"

DEBUG: couldn't open
"/opt/local/var/db/dports/sources/rsync.rsync.macports.org_dpupdate1/base/config/dp_version":
no such file or directory
    while executing
"open [file join $dp_base_path config/dp_version] r"
    (procedure "darwinports::selfupdate" line 45)
    invoked from within
"darwinports::selfupdate [array get global_options]"
Error: /opt/local/bin/port: selfupdate failed: couldn't open
"/opt/local/var/db/dports/sources/rsync.rsync.macports.org_dpupdate1/base/config/dp_version":
no such file or directory


I'd prefer not to have to blow it away and start from scratch, but if
needed, I can.  If so, then I would ask what is the best/standard
method for cleaning up the ports and installing a fresh "MacPorts?"

Thanks,
Frank

From jmr at macports.org  Wed Jun 10 02:41:19 2009
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Jun 2009 19:41:19 +1000
Subject: error on trying to upgrade really old darwinports install
In-Reply-To: <5d62325b0906100127oe95cfb8h90a2aae00f193e99@mail.gmail.com>
References: <5d62325b0906100127oe95cfb8h90a2aae00f193e99@mail.gmail.com>
Message-ID: <4A2F7FBF.3050906@macports.org>

On 2009-6-10 18:27, Frank Even wrote:
> Is there a method for upgrading an old darwinports install that was
> installed on a MacBookPro that has been upgraded from 10.4 to 10.5?
> 
> I'm trying to run the selfupdate, it fails.  I've found some
> references to changing "darwinports" in the rsync commands to
> "macports," I've done that, but I'm failing with the same error
> basically.
> 
> bash-3.2# port version
> Version: 1.320
> 
> Here are the results of a failed "port -vd selfupdate"
> 
> DEBUG: couldn't open
> "/opt/local/var/db/dports/sources/rsync.rsync.macports.org_dpupdate1/base/config/dp_version":
> no such file or directory
>     while executing
> "open [file join $dp_base_path config/dp_version] r"
>     (procedure "darwinports::selfupdate" line 45)
>     invoked from within
> "darwinports::selfupdate [array get global_options]"
> Error: /opt/local/bin/port: selfupdate failed: couldn't open
> "/opt/local/var/db/dports/sources/rsync.rsync.macports.org_dpupdate1/base/config/dp_version":
> no such file or directory
> 
> 
> I'd prefer not to have to blow it away and start from scratch, but if
> needed, I can.  If so, then I would ask what is the best/standard
> method for cleaning up the ports and installing a fresh "MacPorts?"

You could try editing darwinports.tcl and replacing dp_version with
mp_version. But since you've changed your major OS version as well, your
installed ports will likely have incorrect platform variants set, so the
"blow it away and start from scratch" approach is the best one.

- Josh

From macports at tprfct.net  Wed Jun 10 11:47:43 2009
From: macports at tprfct.net (Kastus Shchuka)
Date: Wed, 10 Jun 2009 11:47:43 -0700
Subject: texlive_base @2007_7+nox11 upgrade problem
Message-ID: <C3C770DA-F5D6-47BF-B23B-88BE49766C57@tprfct.net>

Hi,

I do have texlive_base installed with no_x11 variant, version 2007_6.  
Now 2007_7 is available but when I try
to upgrade texlive_base specifically selecting no_x11 variant it still  
pulls openmotif as a dependency.

The command I am using is this:

sudo port upgrade texlive_base +no_x11

When I query dependencies of texlive_base it does not show openmotif:

port deps texlive_base +no_x11
texlive_base has build dependencies on:
	perl5
texlive_base has library dependencies on:
	freetype
	fontconfig
	ncurses
	zlib
	libpng
	texinfo
	texi2html
	ghostscript
	texlive_texmf-minimal
	texlive_texmf-full

So how do I upgrade texlive_base without bringing in openmotif? Is it  
a bug in portfile?

Thanks, -Kastus

From d.l.tDeContes at free.fr  Wed Jun 10 13:49:52 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Wed, 10 Jun 2009 22:49:52 +0200
Subject: subversion on 10.4
In-Reply-To: <DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
References: <C7F17FBC-FCE3-4AE0-8990-BF1C9DFFB6E8@free.fr>
	<7FEB6D78-51E7-4E17-9165-ACFF789982E9@macports.org>
	<83E18B9A-23AA-41A3-88EB-7572FC212DFB@free.fr>
	<DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
Message-ID: <14969FAC-79FB-435F-9F10-7CBFBDCDD460@free.fr>


Le 31 mai 09 ? 07:28, Ryan Schmidt a ?crit :

>
> On May 30, 2009, at 15:33, Thomas De Contes wrote:
>
>> Le 30 mai 09 ? 20:35, Ryan Schmidt a ?crit :
>>
>>> On May 30, 2009, at 08:06, Thomas De Contes wrote:
>>>
>>>> could somebody help subversion maintainer to make it compile on  
>>>> 10.4 please ?
>>>>
>>>> it's all the more annoying that there is no subversion at all in  
>>>> 10.4, contrary to 10.5
>>>
>>> I have no problem compiling Subversion on Mac OS X 10.4. What  
>>> problem are you experiencing?
>>
>> I believed that the problem was in the build operation
>>
>> do you know why this error happens when upgrade but not when  
>> install ?
>> isn't build operation the same ?
>
> Subversion needs to link to other libraries, such as apr and neon,  
> which were also installed with MacPorts. One way to do this is to  
> add -I/opt/local/include to the CPPFLAGS variable and -L/opt/local/ 
> lib to the LDFLAGS variable. Since many ports have this need,  
> MacPorts does this automatically for all ports. But Subversion is  
> composed of several libraries which are based on each other. For  
> example, libsvn_delta depends on libsvn_subr. When Subversion is  
> being built, libsvn_subr is built first, then some time later  
> libsvn_delta is built and is supposed to be linked with the new  
> version of libsvn_subr that was just built but has not yet been  
> installed. But because of the -L/opt/local/lib directive, it tries  
> erroneously to link the new libsvn_delta library with the old  
> libsvn_subr that is in /opt/local/lib instead of the one that was  
> just built. The old version of libsvn_subr does not have the  
> capabilities the new version of libsvn_delta requires and so an  
> error occurs. By deactivating the old version of subversion first,  
> you remove the old libraries from /opt/local/lib and thus prevent  
> the problem.

i don't understand all these details, but ...

>
>
>>> The workaround is to deactivate or uninstall 1.5.x and then clean  
>>> and install 1.6.x.

... why not simply add the deactivate operation in portfile, to  
upgrade ? :-)

on top of that it is done anyway, but usually it is done after  
building, not before,
and if there is an (other) problem while building, the user can steel  
manually reactivate subversion (that he can't do if it is uninstalled)

(clean is not needed :-) )

>>
>> thank you :-)
>
> Did that work for you? If not, please post the error you got.

yes it worked :-)


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Wed Jun 10 13:54:12 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Wed, 10 Jun 2009 22:54:12 +0200
Subject: subversion on 10.4
In-Reply-To: <A08A027E-523C-40F5-9BC1-71D1FF48F73C@geeklair.net>
References: <C7F17FBC-FCE3-4AE0-8990-BF1C9DFFB6E8@free.fr>
	<7FEB6D78-51E7-4E17-9165-ACFF789982E9@macports.org>
	<83E18B9A-23AA-41A3-88EB-7572FC212DFB@free.fr>
	<DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
	<A08A027E-523C-40F5-9BC1-71D1FF48F73C@geeklair.net>
Message-ID: <E7A1DCF2-EE64-4F6B-8510-EC3DE4DEB3E4@free.fr>


Le 1 juin 09 ? 17:04, Daniel J. Luke a ?crit :

> On May 31, 2009, at 1:28 AM, Ryan Schmidt wrote:
>>>> I know there was a problem compiling 1.6.x while 1.5.x is active.
>>>
>>> also with 1.4.x
>>
>> Right, I wouldn't be surprised if the issue exists compiling 1.6.x  
>> while any version earlier than 1.6.0 is active, but I have not  
>> tested other than the last 1.5.x version.
>
> It's only a problem when the ABI of the installed library is  
> different from the ABI of the one that is being built.
>
> So, upgrades work fine for minor versions.
>
> Also, the problem doesn't manifest on 10.5. Since I no longer have  
> a 10.4 system, it's difficult for me to know what might fix the  
> build problem.
>
> If someone with 10.4 can generate a patch (or even just figure out  
> what part of the build would need to change, and is willing to test  
> a patch), then we can get it fixed.

i have 10.4, but i don't know the build process at all,
so i can't locate the problem in an autonomous way
i need that you guide me step by step

i can test a patch or anything you need :-)


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From ryandesign at macports.org  Wed Jun 10 14:09:06 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 10 Jun 2009 16:09:06 -0500
Subject: subversion on 10.4
In-Reply-To: <14969FAC-79FB-435F-9F10-7CBFBDCDD460@free.fr>
References: <C7F17FBC-FCE3-4AE0-8990-BF1C9DFFB6E8@free.fr>
	<7FEB6D78-51E7-4E17-9165-ACFF789982E9@macports.org>
	<83E18B9A-23AA-41A3-88EB-7572FC212DFB@free.fr>
	<DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
	<14969FAC-79FB-435F-9F10-7CBFBDCDD460@free.fr>
Message-ID: <78A44A99-01CE-4CC4-8AD1-B369F8F25590@macports.org>

On Jun 10, 2009, at 15:49, Thomas De Contes wrote:

> Le 31 mai 09 ? 07:28, Ryan Schmidt a ?crit :
>
>>>> The workaround is to deactivate or uninstall 1.5.x and then  
>>>> clean and install 1.6.x.
>
> ... why not simply add the deactivate operation in portfile, to  
> upgrade ? :-)
>
> on top of that it is done anyway, but usually it is done after  
> building, not before,

I'm sorry, that cannot be changed by a port.

The order in which MacPorts base runs the phases is correct.

What we need to do is make Subversion build a new version correctly  
even if an old version is active.


From d.l.tDeContes at free.fr  Wed Jun 10 14:26:39 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Wed, 10 Jun 2009 23:26:39 +0200
Subject: python25
In-Reply-To: <EC944374-2D60-494F-B1F7-CC0DCBC7C3D9@macports.org>
References: <3860C771-9EE4-4549-828C-7D13CAAD2D69@free.fr>	<49F472A6.7030307@macports.org>	<CBA597D7-E190-4873-BD36-FBAC52756B01@free.fr>	<49F47BED.5010708@macports.org>	<5D2365F4-3631-48A7-A993-C357EE516F13@macports.org>
	<EFDA7A12-4784-4A33-ABC3-2B213CF5E845@free.fr>
	<49FC738D.3090305@macports.org>
	<138F1380-C23C-431F-8E97-65B4D155C370@free.fr>
	<49FCA592.90403@macports.org>
	<008AB901-2C56-41EA-BF89-02D2ACF38FA3@free.fr>
	<EC944374-2D60-494F-B1F7-CC0DCBC7C3D9@macports.org>
Message-ID: <D214B7CB-254E-48E3-AF30-DBC982054145@free.fr>


Le 30 mai 09 ? 20:49, Ryan Schmidt a ?crit :

> On May 30, 2009, at 08:47, Thomas De Contes wrote:
>
>> Le 2 mai 09 ? 21:57, Joshua Root a ?crit :
>>
>>> Thomas De Contes wrote:
>>>
>>>> is there a way to set an other path than /Applications/MacPorts  
>>>> please ?
>>>> like with "./configure --prefix="
>>>
>>> If you run `./configure --help` you will see the --with- 
>>> applications-dir
>>> option.
>>
>> thank you :-)
>> i find help not explicit enough, about what each option is used for
>
> You can also read the Guide:
>
> http://guide.macports.org/chunked/internals.configuration-files.html

thank you :-)

>
>> i can't confirm that it works,

it works fine :-))

>> because it tries to Activate the aleady compiled python25, despite  
>> the fact that i recompiled MacPorts with differents options
>
> Then you will need to uninstall that python25 and recompile it.
>
> Note that you don't need to recompile MacPorts to change  
> applications_dir or most of the other variables. All it does when  
> you use --with-applications-dir is that it writes the value of that  
> argument to the macports.conf file. So you can edit that file  
> yourself later to change the values.

ok, thank you :-)


but i want to maintain a script which is able to install MacPorts or  
update it, according to that which it needs

well, is it possible to update macports.conf with ./configure (except  
deleting it) ?
i looked at "./configure --help" but i didn't find anything (but i  
don't know it very well)


>
>> on top of that, it don't want to recompile python25 even if i do  
>> "port clean python25" before !
>> what should i do ?
>
>
> Since the port is already installed (though not activated), you  
> need to uninstall it in order to get it to recompile.

thank you :-)


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From fonvitale at gmail.com  Wed Jun 10 14:54:59 2009
From: fonvitale at gmail.com (Fon Vitale)
Date: Wed, 10 Jun 2009 22:54:59 +0100
Subject: How does Macport work?
Message-ID: <18e4074f0906101454o37a40a97r4c4f13ffdac85be8@mail.gmail.com>

Hi everybody!
I'm a new Macport user and I have a basic question. I would like to know
what happens when you want to install one thing that it's alredy installed.

For instance, supose that C compiler is alredy installed in your computer
(not installed using macport) and you install it using macport:

sudo port install gcc43 (for example)

What is macport installing?
Where is macport installing C compiler?
What happens with C files installed before?
If we want to uninstall C compiler... ?

Thank you so much.


-- 
Fon Vitale
fonvitale at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090610/e3101ec4/attachment.html>

From d.l.tDeContes at free.fr  Wed Jun 10 15:10:51 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Thu, 11 Jun 2009 00:10:51 +0200
Subject: subversion on 10.4
In-Reply-To: <78A44A99-01CE-4CC4-8AD1-B369F8F25590@macports.org>
References: <C7F17FBC-FCE3-4AE0-8990-BF1C9DFFB6E8@free.fr>
	<7FEB6D78-51E7-4E17-9165-ACFF789982E9@macports.org>
	<83E18B9A-23AA-41A3-88EB-7572FC212DFB@free.fr>
	<DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
	<14969FAC-79FB-435F-9F10-7CBFBDCDD460@free.fr>
	<78A44A99-01CE-4CC4-8AD1-B369F8F25590@macports.org>
Message-ID: <7CDE2DAC-5E87-4993-9571-FD06D4F1581D@free.fr>


Le 10 juin 09 ? 23:09, Ryan Schmidt a ?crit :

> On Jun 10, 2009, at 15:49, Thomas De Contes wrote:
>
>> Le 31 mai 09 ? 07:28, Ryan Schmidt a ?crit :
>>
>>>>> The workaround is to deactivate or uninstall 1.5.x and then  
>>>>> clean and install 1.6.x.
>>
>> ... why not simply add the deactivate operation in portfile, to  
>> upgrade ? :-)
>>
>> on top of that it is done anyway, but usually it is done after  
>> building, not before,
>
> I'm sorry, that cannot be changed by a port.
>
> The order in which MacPorts base runs the phases is correct.
>
> What we need to do is make Subversion build a new version correctly  
> even if an old version is active.

but there is also a problem with cyrus-sasl2,
isn't it the same ?


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From talklists at newgeo.com  Wed Jun 10 15:27:33 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 10 Jun 2009 15:27:33 -0700
Subject: How does Macport work?
In-Reply-To: <18e4074f0906101454o37a40a97r4c4f13ffdac85be8@mail.gmail.com>
References: <18e4074f0906101454o37a40a97r4c4f13ffdac85be8@mail.gmail.com>
Message-ID: <7118FE3E-6288-4262-BA5F-57717031092A@newgeo.com>

Hello, welcome to MacPorts...

On Jun 10, 2009, at 2:54 PM, Fon Vitale wrote:

> I'm a new Macport user and I have a basic question. I would like to  
> know what happens when you want to install one thing that it's  
> alredy installed.
>
> For instance, supose that C compiler is alredy installed in your  
> computer (not installed using macport) and you install it using  
> macport:

Any software isntalled prior to MacPorts is going to be installed  
where that software decided to isntall itself.  Since MacPorts was not  
installed prior, it will not be anywhere near MacPorts.

By default, MacPorts installs 99% of everything in /opt/local though  
you can change that location, most people never do, nor would I  
recommend it.

> sudo port install gcc43 (for example)

If you run
	port info gcc43
That will give you some details on that port

Running
	port dir gcc43
Returns
/opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/ 
gcc43
At that path, you can see the portfile that is used, and look at it to  
see what it is going to do.  A shortcut woudld be:
	port edit gcc43
This will read in the portfile for you to see, or you can also
	cd `port dir gcc43`
Which will get you right to the portfile.

> What is macport installing?

Macports, in your case, would install gcc43 (The GNU compiler  
collection) into /opt/local.

> Where is macport installing C compiler?

Look at the portfile, and look at the configure args, you can see  
where all the bits and pieces are going to end up.

> What happens with C files installed before?

They will be untouched.

> If we want to uninstall C compiler... ?

Your old C compiler would also be untouched.

* I am pretty new to MacPorts, but the questions you ask seem to be  
general to how MacPorts works, which is that, in almost all cases,  
data outside of /opt/local is the only place MacPorts will touch.   
There are exceptions, but those are few.
-- 
Scott * If you contact me off list replace talklists@ with scott@ *


From fonvitale at gmail.com  Wed Jun 10 16:06:10 2009
From: fonvitale at gmail.com (Fon Vitale)
Date: Thu, 11 Jun 2009 00:06:10 +0100
Subject: How does Macport work?
In-Reply-To: <18e4074f0906101454o37a40a97r4c4f13ffdac85be8@mail.gmail.com>
References: <18e4074f0906101454o37a40a97r4c4f13ffdac85be8@mail.gmail.com>
Message-ID: <18e4074f0906101606n7b96c687x98c23a4cbdaa28fd@mail.gmail.com>

Hi!
Ok. Thank you, but I don't understand why Macports installs things which are
installed. I made the question because I need a program to make diagrams, so
I run:

sudo port -v install dia

One of the dependences of the dependences is perl5.8 and Macports needs
install it, but perl5.8 is alredy installed in my computer (a Macbook).

Coming back whit the C compiler example, if Macports installs the compiler
when I run it what compiler is being running: Macports installed or prior
Macports one?

Thank you.
-- 
Fon Vitale
fonvitale at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090611/474cf8fb/attachment.html>

From mdcrawford at gmail.com  Wed Jun 10 16:14:00 2009
From: mdcrawford at gmail.com (Michael Crawford)
Date: Wed, 10 Jun 2009 16:14:00 -0700
Subject: How does Macport work?
In-Reply-To: <18e4074f0906101606n7b96c687x98c23a4cbdaa28fd@mail.gmail.com>
References: <18e4074f0906101454o37a40a97r4c4f13ffdac85be8@mail.gmail.com>
	<18e4074f0906101606n7b96c687x98c23a4cbdaa28fd@mail.gmail.com>
Message-ID: <dc9f86e80906101614i6a1506beqac513bf6dfff3c9@mail.gmail.com>

On Wed, Jun 10, 2009 at 4:06 PM, Fon Vitale<fonvitale at gmail.com> wrote:
> Coming back whit the C compiler example, if Macports installs the compiler
> when I run it what compiler is being running: Macports installed or prior
> Macports one?

That depends on the value of your PATH environment variable.  Give the
following command in the Terminal:

   echo $PATH

You'll see a list of directories.  If /opt/local comes before
/usr/bin, then the MacPorts version will be run; otherwise the
previously installed one will be run.

You can also do:

  which gcc

... and it will give you the pathname of the gcc that will actually be
run if you simply give the "gcc" command.  Which does its work by
examining each of the directories in your PATH.

If you're not hip to PATH and other environment variables, try the
following Google search:

   UNIX shell tutorial

There's lots of good ones, and if you're going to be working with the
command line on Mac OS X, you would do well to read one or two.

Mike
\
-- 
Michael David Crawford
mdcrawford at gmail dot com

   GoingWare's Bag of Programming Tricks
      http://www.goingware.com/tips/

From talklists at newgeo.com  Wed Jun 10 16:23:41 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 10 Jun 2009 16:23:41 -0700
Subject: How does Macport work?
In-Reply-To: <18e4074f0906101606n7b96c687x98c23a4cbdaa28fd@mail.gmail.com>
References: <18e4074f0906101454o37a40a97r4c4f13ffdac85be8@mail.gmail.com>
	<18e4074f0906101606n7b96c687x98c23a4cbdaa28fd@mail.gmail.com>
Message-ID: <DCFB0451-899B-4A7F-AEA1-D755D6DF140F@newgeo.com>

On Jun 10, 2009, at 4:06 PM, Fon Vitale wrote:

> Ok. Thank you, but I don't understand why Macports installs things  
> which are installed. I made the question because I need a program to  
> make diagrams, so I run:
>
> sudo port -v install dia
>
> One of the dependences of the dependences is perl5.8 and Macports  
> needs install it, but perl5.8 is alredy installed in my computer (a  
> Macbook).

Because macports has no way of knowing that your perl5.8 is the one  
that will work.  At least with dia knowing it needs perl5.8, and  
knowing that the maintainer had to build it with macports perl5.8,  
that much is known to more than likely work.

Apple's installed perl, may or may not work, and may or may not be  
updated.  What if apple releases perl 6, nukes perl 5, then your dia  
would stop working.

> Coming back whit the C compiler example, if Macports installs the  
> compiler when I run it what compiler is being running: Macports  
> installed or prior Macports one?


Whatever one is listed first when you run
	 echo $PATH
in your terminal.

Hope that helps.
-- 
Scott * If you contact me off list replace talklists@ with scott@ *


From d.l.tDeContes at free.fr  Wed Jun 10 16:28:41 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Thu, 11 Jun 2009 01:28:41 +0200
Subject: binpath
Message-ID: <EC4D6790-2149-417A-A409-DD4768427A9A@free.fr>

hi :-)


i want to install the port "gnat-gcc"
for that, it needs to use an other (older) gnat

i have http://homepage.mac.com/awreynolds/.Public/Ada/PowerPC/fsf-ppc- 
ada-4.3-20080203-10.4-most-langs.tgz
but i want to put it at a personal location, to not merge it with  
other stuff and be able to remove it esier

i found binpath in macports.conf


i think it's what i need :-)

i would like just to not have to edit macports.conf (if i have to  
reinstall MacPorts, for any reason)

is it possible to set binpath with ./configure ?
i didn't find anything in "./configure --help"

if yes, is it possible to add a path to binpath, like we do for PATH  
in .profile, rather than set it from scratch ?


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Wed Jun 10 16:49:21 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Thu, 11 Jun 2009 01:49:21 +0200
Subject: checking for gcc
In-Reply-To: <4A215383.9080301@macports.org>
References: <675B1A6E-67F6-4E53-93B6-5C5EB56F7B07@free.fr>	<E63B84F6-3A00-4DD3-BC6D-A0C67A136874@macports.org>	<FF7EA160-0957-44FB-B331-01CFFEE84F36@free.fr>	<5BCA1EB2-FEC2-4296-A8F9-0A92330D006F@macports.org>	<5E8AF47F-A3B2-4FD0-A2AB-8EE7420A59A5@free.fr>	<924BD5D8-DB5F-4197-ACAA-1A2035B4A1BC@macports.org>
	<E2CD7888-0F10-41C8-890F-CA98FF4B34C6@free.fr>
	<49FC5405.5000606@macports.org>
	<0DA2076E-98CA-445E-9853-A72398328D8B@free.fr>
	<49FCC9F6.9000909@macports.org>
	<D4513BED-17AD-41AA-9944-520C0698188E@free.fr>
	<4A215383.9080301@macports.org>
Message-ID: <51274091-0441-44ED-9C4C-674E8C388293@free.fr>


Le 30 mai 09 ? 17:40, Rainer M?ller a ?crit :

> On 2009-05-30 17:12, Thomas De Contes wrote:
>
> [...]
>
>> ... i don't understand why you prefer (1) for MacPorts itself
>>
>> since Ryan Schmidt uses (2) for ports, i don't see what kind of
>> avantage you get using (1) for MacPorts itself
>
> It allows to build base with another compiler and it makes it more  
> portable.
>
>> i fully understand Ryan's choice, and finally I agree with him
>> what aren't you agreement in what he said with ?
>
> As I explained in my previous mail ...
>
>> and anyway, i find that it's better to have MacPorts homogeneous,
>> between itself and its ports, don't you think ?
>
> ... I still see no reason to restrict building MacPorts itself to a
> specific compiler. Users building MacPorts from source are expected to
> know what they are doing.

ah, ok,
i just understand why what Ryan Schmidt says about ports is not  
applicable to MacPorts itself ...

basic users are expected to compile ports but not MacPorts itself,  
they are expected to install binaries of MacPorts itself :-)
sorry, i forgot it :-)

>
> Having MacPorts installation with a different prefix in PATH during
> configure might fail anyway if certain ports are installed (e.g. tcl).
> Therefore, use a clean environment with the system's default PATH  
> if you
> don't want to use MacPorts for that.

well, i need to compile MacPorts because i don't want to give it root  
rights

it's not very constraining,
just, sometimes i have tinny problems, and in general there is a  
solution :-)


but it may be very annoying, if the installation of some ports avoids  
to rebuild MacPorts :-(

is there a simple way to use the system's default PATH, just for the  
time to build MacPorts ?

(note that i don't ask that it would be the defaut, so developers who  
want to make any kind of tests with MacPorts are able to continue  
it :-) )


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From ohce86 at kitcarson.net  Wed Jun 10 17:08:37 2009
From: ohce86 at kitcarson.net (Timothy Goins)
Date: Wed, 10 Jun 2009 18:08:37 -0600
Subject: How does Macport work?
In-Reply-To: <dc9f86e80906101614i6a1506beqac513bf6dfff3c9@mail.gmail.com>
References: <18e4074f0906101454o37a40a97r4c4f13ffdac85be8@mail.gmail.com>
	<18e4074f0906101606n7b96c687x98c23a4cbdaa28fd@mail.gmail.com>
	<dc9f86e80906101614i6a1506beqac513bf6dfff3c9@mail.gmail.com>
Message-ID: <30F94D15-D898-46B8-B39D-E8850DA3A864@kitcarson.net>

Fon's question got me thinking.  While /opt/local/bin precedes /usr/ 
bin in my $PATH, when I `which gcc` I get /usr/bin/gcc.  Huh?  Since  
I've never had insurmountable compiler glitches, I'd lost track of how  
I'd worked around previous issues.  I have created a mess!  In /usr/ 
bin/ I've got two executables, gcc-4.0 and gcc-4.2 (renamed mp files,  
if I recall correctly) and two links:

gcc -> /usr/bin/gcc-4.0 and
gcc-4.3 -> /opt/local/bin/gcc-mp-4.3

In /opt/local/bin, I've got gcc-mp-4.3 and gcc-mp-4.4 (and the gccbug  
executables).

I would like to be able to type gcc and fire up the latest C compiler  
(gcc-mp-4.4?), which is not as problem; however, I don't want to try  
to compile older code that might (?) not be compatible with gcc-mp 4.4.

What is the "clean", correct way to manage my C compiler(s)?

Thanks.

Tim

On Jun 10, 2009, at 5:14 PM, Michael Crawford wrote:

> On Wed, Jun 10, 2009 at 4:06 PM, Fon Vitale<fonvitale at gmail.com>  
> wrote:
>> Coming back whit the C compiler example, if Macports installs the  
>> compiler
>> when I run it what compiler is being running: Macports installed or  
>> prior
>> Macports one?
>
> That depends on the value of your PATH environment variable.  Give the
> following command in the Terminal:
>
>   echo $PATH
>
> You'll see a list of directories.  If /opt/local comes before
> /usr/bin, then the MacPorts version will be run; otherwise the
> previously installed one will be run.
>
> You can also do:
>
>  which gcc
>
> ... and it will give you the pathname of the gcc that will actually be
> run if you simply give the "gcc" command.  Which does its work by
> examining each of the directories in your PATH.
>
> If you're not hip to PATH and other environment variables, try the
> following Google search:
>
>   UNIX shell tutorial
>
> There's lots of good ones, and if you're going to be working with the
> command line on Mac OS X, you would do well to read one or two.
>
> Mike
> \
> -- 
> Michael David Crawford
> mdcrawford at gmail dot com
>
>   GoingWare's Bag of Programming Tricks
>      http://www.goingware.com/tips/
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From ryandesign at macports.org  Wed Jun 10 21:48:41 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 10 Jun 2009 23:48:41 -0500
Subject: How does Macport work?
In-Reply-To: <30F94D15-D898-46B8-B39D-E8850DA3A864@kitcarson.net>
References: <18e4074f0906101454o37a40a97r4c4f13ffdac85be8@mail.gmail.com>
	<18e4074f0906101606n7b96c687x98c23a4cbdaa28fd@mail.gmail.com>
	<dc9f86e80906101614i6a1506beqac513bf6dfff3c9@mail.gmail.com>
	<30F94D15-D898-46B8-B39D-E8850DA3A864@kitcarson.net>
Message-ID: <3D1126E2-80D2-4E35-A8AF-495F412235BD@macports.org>


On Jun 10, 2009, at 19:08, Timothy Goins wrote:

> Fon's question got me thinking.  While /opt/local/bin precedes /usr/ 
> bin in my $PATH, when I `which gcc` I get /usr/bin/gcc.  Huh?   
> Since I've never had insurmountable compiler glitches, I'd lost  
> track of how I'd worked around previous issues.  I have created a  
> mess!  In /usr/bin/ I've got two executables, gcc-4.0 and gcc-4.2  
> (renamed mp files, if I recall correctly) and two links:
>
> gcc -> /usr/bin/gcc-4.0 and
> gcc-4.3 -> /opt/local/bin/gcc-mp-4.3
>
> In /opt/local/bin, I've got gcc-mp-4.3 and gcc-mp-4.4 (and the  
> gccbug executables).
>
> I would like to be able to type gcc and fire up the latest C  
> compiler (gcc-mp-4.4?), which is not as problem; however, I don't  
> want to try to compile older code that might (?) not be compatible  
> with gcc-mp 4.4.
>
> What is the "clean", correct way to manage my C compiler(s)?

The gcc_select port exists to help you create a symlink called "gcc"  
in /opt/local/bin pointing to whatever version of MacPorts-installed  
gcc you would like to use.



From ryandesign at macports.org  Wed Jun 10 21:51:18 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 10 Jun 2009 23:51:18 -0500
Subject: checking for gcc
In-Reply-To: <51274091-0441-44ED-9C4C-674E8C388293@free.fr>
References: <675B1A6E-67F6-4E53-93B6-5C5EB56F7B07@free.fr>	<E63B84F6-3A00-4DD3-BC6D-A0C67A136874@macports.org>	<FF7EA160-0957-44FB-B331-01CFFEE84F36@free.fr>	<5BCA1EB2-FEC2-4296-A8F9-0A92330D006F@macports.org>	<5E8AF47F-A3B2-4FD0-A2AB-8EE7420A59A5@free.fr>	<924BD5D8-DB5F-4197-ACAA-1A2035B4A1BC@macports.org>
	<E2CD7888-0F10-41C8-890F-CA98FF4B34C6@free.fr>
	<49FC5405.5000606@macports.org>
	<0DA2076E-98CA-445E-9853-A72398328D8B@free.fr>
	<49FCC9F6.9000909@macports.org>
	<D4513BED-17AD-41AA-9944-520C0698188E@free.fr>
	<4A215383.9080301@macports.org>
	<51274091-0441-44ED-9C4C-674E8C388293@free.fr>
Message-ID: <76132DA4-9574-42CE-BAB5-BED6C81AC5B9@macports.org>

On Jun 10, 2009, at 18:49, Thomas De Contes wrote:

> basic users are expected to compile ports but not MacPorts itself,  
> they are expected to install binaries of MacPorts itself :-)
> sorry, i forgot it :-)

Well, a user who types "sudo port selfupdate" causes MacPorts to  
build itself from source...


>> Having MacPorts installation with a different prefix in PATH during
>> configure might fail anyway if certain ports are installed (e.g.  
>> tcl).
>> Therefore, use a clean environment with the system's default PATH  
>> if you
>> don't want to use MacPorts for that.
>
> well, i need to compile MacPorts because i don't want to give it  
> root rights

Same here.


> it's not very constraining,
> just, sometimes i have tinny problems, and in general there is a  
> solution :-)
>
>
> but it may be very annoying, if the installation of some ports  
> avoids to rebuild MacPorts :-(
>
> is there a simple way to use the system's default PATH, just for  
> the time to build MacPorts ?

Just do it! Run

export PATH="/bin:/sbin:/usr/bin:/usr/sbin"

before you run the configure, make and make install commands. That's  
what I do. Then close the Terminal window to get your previous PATH  
back.





From ryandesign at macports.org  Wed Jun 10 21:54:03 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 10 Jun 2009 23:54:03 -0500
Subject: binpath
In-Reply-To: <EC4D6790-2149-417A-A409-DD4768427A9A@free.fr>
References: <EC4D6790-2149-417A-A409-DD4768427A9A@free.fr>
Message-ID: <1592A4A7-C99D-4598-BCB4-01781591A829@macports.org>


On Jun 10, 2009, at 18:28, Thomas De Contes wrote:

> i want to install the port "gnat-gcc"
> for that, it needs to use an other (older) gnat

IMHO this port is in violation of the basic requirement that a port  
should install everything it needs. If gnat needs an older version of  
gnat to build, gnat must download and use an older version of gnat.  
The port ghc gives an example of how such a bootstrap can be done.


> i have http://homepage.mac.com/awreynolds/.Public/Ada/PowerPC/fsf- 
> ppc-ada-4.3-20080203-10.4-most-langs.tgz
> but i want to put it at a personal location, to not merge it with  
> other stuff and be able to remove it esier
>
> i found binpath in macports.conf
>
>
> i think it's what i need :-)
>
> i would like just to not have to edit macports.conf (if i have to  
> reinstall MacPorts, for any reason)
>
> is it possible to set binpath with ./configure ?
> i didn't find anything in "./configure --help"
>
> if yes, is it possible to add a path to binpath, like we do for  
> PATH in .profile, rather than set it from scratch ?

I do not know if it is possible to do what you ask. It is not  
something I would want a user to do. In fact, I usually don't want a  
user to edit binpath at all. I was rather apprehensive when the  
option to change it in macports.conf was initially added.


From ryandesign at macports.org  Wed Jun 10 21:54:59 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 10 Jun 2009 23:54:59 -0500
Subject: subversion on 10.4
In-Reply-To: <7CDE2DAC-5E87-4993-9571-FD06D4F1581D@free.fr>
References: <C7F17FBC-FCE3-4AE0-8990-BF1C9DFFB6E8@free.fr>
	<7FEB6D78-51E7-4E17-9165-ACFF789982E9@macports.org>
	<83E18B9A-23AA-41A3-88EB-7572FC212DFB@free.fr>
	<DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
	<14969FAC-79FB-435F-9F10-7CBFBDCDD460@free.fr>
	<78A44A99-01CE-4CC4-8AD1-B369F8F25590@macports.org>
	<7CDE2DAC-5E87-4993-9571-FD06D4F1581D@free.fr>
Message-ID: <E61ECED4-BB20-4A22-8B35-15FDB70B29D3@macports.org>


On Jun 10, 2009, at 17:10, Thomas De Contes wrote:

>
> Le 10 juin 09 ? 23:09, Ryan Schmidt a ?crit :
>
>> On Jun 10, 2009, at 15:49, Thomas De Contes wrote:
>>
>>> Le 31 mai 09 ? 07:28, Ryan Schmidt a ?crit :
>>>
>>>>>> The workaround is to deactivate or uninstall 1.5.x and then  
>>>>>> clean and install 1.6.x.
>>>
>>> ... why not simply add the deactivate operation in portfile, to  
>>> upgrade ? :-)
>>>
>>> on top of that it is done anyway, but usually it is done after  
>>> building, not before,
>>
>> I'm sorry, that cannot be changed by a port.
>>
>> The order in which MacPorts base runs the phases is correct.
>>
>> What we need to do is make Subversion build a new version  
>> correctly even if an old version is active.
>
> but there is also a problem with cyrus-sasl2,
> isn't it the same ?

I see the same symptom, yes. A similar solution would need to be  
applied to the cyrus-sasl2 port. If you can come up with a general  
change that should be made to MacPorts base that will not adversely  
affect too many other ports, we can certainly consider it.



From ryandesign at macports.org  Wed Jun 10 21:55:52 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 10 Jun 2009 23:55:52 -0500
Subject: python25
In-Reply-To: <D214B7CB-254E-48E3-AF30-DBC982054145@free.fr>
References: <3860C771-9EE4-4549-828C-7D13CAAD2D69@free.fr>	<49F472A6.7030307@macports.org>	<CBA597D7-E190-4873-BD36-FBAC52756B01@free.fr>	<49F47BED.5010708@macports.org>	<5D2365F4-3631-48A7-A993-C357EE516F13@macports.org>
	<EFDA7A12-4784-4A33-ABC3-2B213CF5E845@free.fr>
	<49FC738D.3090305@macports.org>
	<138F1380-C23C-431F-8E97-65B4D155C370@free.fr>
	<49FCA592.90403@macports.org>
	<008AB901-2C56-41EA-BF89-02D2ACF38FA3@free.fr>
	<EC944374-2D60-494F-B1F7-CC0DCBC7C3D9@macports.org>
	<D214B7CB-254E-48E3-AF30-DBC982054145@free.fr>
Message-ID: <3A3FEF56-18F3-4AB2-87E9-8C00C9553146@macports.org>


On Jun 10, 2009, at 16:26, Thomas De Contes wrote:

>>> because it tries to Activate the aleady compiled python25,  
>>> despite the fact that i recompiled MacPorts with differents options
>>
>> Then you will need to uninstall that python25 and recompile it.
>>
>> Note that you don't need to recompile MacPorts to change  
>> applications_dir or most of the other variables. All it does when  
>> you use --with-applications-dir is that it writes the value of  
>> that argument to the macports.conf file. So you can edit that file  
>> yourself later to change the values.
>
> but i want to maintain a script which is able to install MacPorts  
> or update it, according to that which it needs

Good idea, I have one of those too!


> well, is it possible to update macports.conf with ./configure  
> (except deleting it) ?
> i looked at "./configure --help" but i didn't find anything (but i  
> don't know it very well)

I don't believe running ./configure will modify an existing  
macports.conf.



From ryandesign at macports.org  Wed Jun 10 21:58:03 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 10 Jun 2009 23:58:03 -0500
Subject: texlive_base @2007_7+nox11 upgrade problem
In-Reply-To: <C3C770DA-F5D6-47BF-B23B-88BE49766C57@tprfct.net>
References: <C3C770DA-F5D6-47BF-B23B-88BE49766C57@tprfct.net>
Message-ID: <A59B4D9C-9C71-40FE-9EA7-D823D517E702@macports.org>

On Jun 10, 2009, at 13:47, Kastus Shchuka wrote:

> I do have texlive_base installed with no_x11 variant, version  
> 2007_6. Now 2007_7 is available but when I try
> to upgrade texlive_base specifically selecting no_x11 variant it  
> still pulls openmotif as a dependency.
>
> The command I am using is this:
>
> sudo port upgrade texlive_base +no_x11
>
> When I query dependencies of texlive_base it does not show openmotif:
>
> port deps texlive_base +no_x11
> texlive_base has build dependencies on:
> 	perl5
> texlive_base has library dependencies on:
> 	freetype
> 	fontconfig
> 	ncurses
> 	zlib
> 	libpng
> 	texinfo
> 	texi2html
> 	ghostscript
> 	texlive_texmf-minimal
> 	texlive_texmf-full
>
> So how do I upgrade texlive_base without bringing in openmotif? Is  
> it a bug in portfile?

Short answer: sync your ports and try again.

Longer answer: for about a day between June 8 and June 9,  
texlive_base always brought in the openmotif dependency. Then it was  
changed to only bring it in if you use the +motif variant.



From ryandesign at macports.org  Wed Jun 10 22:17:06 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 11 Jun 2009 00:17:06 -0500
Subject: Reverting to previous ports - mysql5
In-Reply-To: <683AB3C2-5003-4802-935A-2480CA03361A@CentosPrime.COM>
References: <ACDC7F11-A8AA-43AA-9ECF-BA33E281987C@CentosPrime.COM>
	<D6FC8DC0-BE5D-4A69-BF66-29BEF4C908F4@macports.org>
	<2071BCA6-9BF4-4899-BEC2-032EDF2A469F@CentosPrime.COM>
	<7A560FF1-110B-49AB-8DB9-79C03949C76A@macports.org>
	<683AB3C2-5003-4802-935A-2480CA03361A@CentosPrime.COM>
Message-ID: <97886453-D279-4377-87C2-E762CCFAA797@macports.org>


On Jun 9, 2009, at 08:17, Chris Janton wrote:

> On 2009-06-08 , at 11:27 , Ryan Schmidt wrote:
>
>>> I copied/pasted the MYSQL5-SERVER line from the terminal.
>>> This is copied/pasted from /etc/hostconfig
>>>
>>> MYSQL5-SERVER=-YES-
>>>
>>> For the time being I have manually started mysql on the 10.3  
>>> system and will hand start if we have to reboot.
>>
>> I am guessing it is using the port name as the key for the  
>> hostconfig file, and that the hostconfig file does not support  
>> hyphens in its variable names. So that would be a problem. Perhaps  
>> I can tell it to continue to use the key  
>> "mysql5" ("startupitem.name mysql5"?) You can try adding that to  
>> the mysql5-server port already if you want, but I will also test  
>> when I'm back at my Panther machine tonight.
>
> That certainly did the trick - to think a "-" in a name should be  
> such a problem...

I committed this change in r52144. I didn't test on Panther yet so  
please let me know if that works now.



From blb at macports.org  Wed Jun 10 22:43:08 2009
From: blb at macports.org (Bryan Blackburn)
Date: Wed, 10 Jun 2009 23:43:08 -0600
Subject: cyrus-sasl2 upgrading (was Re: subversion on 10.4)
In-Reply-To: <E61ECED4-BB20-4A22-8B35-15FDB70B29D3@macports.org>
References: <C7F17FBC-FCE3-4AE0-8990-BF1C9DFFB6E8@free.fr>
	<7FEB6D78-51E7-4E17-9165-ACFF789982E9@macports.org>
	<83E18B9A-23AA-41A3-88EB-7572FC212DFB@free.fr>
	<DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
	<14969FAC-79FB-435F-9F10-7CBFBDCDD460@free.fr>
	<78A44A99-01CE-4CC4-8AD1-B369F8F25590@macports.org>
	<7CDE2DAC-5E87-4993-9571-FD06D4F1581D@free.fr>
	<E61ECED4-BB20-4A22-8B35-15FDB70B29D3@macports.org>
Message-ID: <20090611054308.GM32363@ninagal.withay.com>

On Wed, Jun 10, 2009 at 11:54:59PM -0500, Ryan Schmidt said:
[...]
>
> I see the same symptom, yes. A similar solution would need to be applied 
> to the cyrus-sasl2 port. If you can come up with a general change that 
> should be made to MacPorts base that will not adversely affect too many 
> other ports, we can certainly consider it.

Does anyone know why cyrus-sasl2 has that pre-configure check?  I found
tickets #17158 and #17328, the former being the one which added it but with
no description of why.  Having just commented-out the pre-configure bit,
upgrading from 2.1.22 to 2.1.23 worked just fine.  Is it
OS-version-specific, arch-specific, or MacPorts-version-specific?

Bryan


From ryandesign at macports.org  Wed Jun 10 23:11:22 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 11 Jun 2009 01:11:22 -0500
Subject: cyrus-sasl2 upgrading (was Re: subversion on 10.4)
In-Reply-To: <20090611054308.GM32363@ninagal.withay.com>
References: <C7F17FBC-FCE3-4AE0-8990-BF1C9DFFB6E8@free.fr>
	<7FEB6D78-51E7-4E17-9165-ACFF789982E9@macports.org>
	<83E18B9A-23AA-41A3-88EB-7572FC212DFB@free.fr>
	<DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
	<14969FAC-79FB-435F-9F10-7CBFBDCDD460@free.fr>
	<78A44A99-01CE-4CC4-8AD1-B369F8F25590@macports.org>
	<7CDE2DAC-5E87-4993-9571-FD06D4F1581D@free.fr>
	<E61ECED4-BB20-4A22-8B35-15FDB70B29D3@macports.org>
	<20090611054308.GM32363@ninagal.withay.com>
Message-ID: <AE30D0B2-9ED1-4874-AC72-673432861F82@macports.org>


On Jun 11, 2009, at 00:43, Bryan Blackburn wrote:

> On Wed, Jun 10, 2009 at 11:54:59PM -0500, Ryan Schmidt said:
> [...]
>>
>> I see the same symptom, yes. A similar solution would need to be  
>> applied
>> to the cyrus-sasl2 port. If you can come up with a general change  
>> that
>> should be made to MacPorts base that will not adversely affect too  
>> many
>> other ports, we can certainly consider it.
>
> Does anyone know why cyrus-sasl2 has that pre-configure check?  I  
> found
> tickets #17158 and #17328, the former being the one which added it  
> but with
> no description of why.  Having just commented-out the pre-configure  
> bit,
> upgrading from 2.1.22 to 2.1.23 worked just fine.  Is it
> OS-version-specific, arch-specific, or MacPorts-version-specific?

I also have no problem upgrading from 2.1.22 to 2.1.23, on Mac OS X  
10.4.11 Intel with Xcode 2.5 and MacPorts 1.7.1.

But if you downgrade your cyrus-sasl2 to 2.1.21 first, then try to  
upgrade, you should get the failure I got (see below).

Presumably the ABI changed between 2.1.21 and 2.1.22 but not between  
2.1.22 and 2.1.23, and as we see it's trying to link with the already- 
installed older version of the libraries before trying to use the  
newer ones it just build (-L/opt/local/lib appears in the link  
command before -L../lib/.libs).

/bin/sh ../libtool --mode=link /usr/bin/gcc-4.0  -Wall -W -O2  -L/opt/ 
local/lib -L/opt/local/lib -o pluginviewer  pluginviewer.o ../lib/ 
libsasl2.la   -lresolv -lresolv  -lpam
/usr/bin/gcc-4.0 -Wall -W -O2 -L/opt/local/lib -L/opt/local/lib - 
o .libs/pluginviewer pluginviewer.o -L../lib/.libs -lsasl2 -ldl - 
lresolv -lresolv -lpam -lresolv -lresolv -lpam
/usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
_auxprop_plugin_info
collect2: ld returned 1 exit status
make[2]: *** [pluginviewer] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2



From blb at macports.org  Thu Jun 11 00:26:34 2009
From: blb at macports.org (Bryan Blackburn)
Date: Thu, 11 Jun 2009 01:26:34 -0600
Subject: cyrus-sasl2 upgrading (was Re: subversion on 10.4)
In-Reply-To: <AE30D0B2-9ED1-4874-AC72-673432861F82@macports.org>
References: <C7F17FBC-FCE3-4AE0-8990-BF1C9DFFB6E8@free.fr>
	<7FEB6D78-51E7-4E17-9165-ACFF789982E9@macports.org>
	<83E18B9A-23AA-41A3-88EB-7572FC212DFB@free.fr>
	<DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
	<14969FAC-79FB-435F-9F10-7CBFBDCDD460@free.fr>
	<78A44A99-01CE-4CC4-8AD1-B369F8F25590@macports.org>
	<7CDE2DAC-5E87-4993-9571-FD06D4F1581D@free.fr>
	<E61ECED4-BB20-4A22-8B35-15FDB70B29D3@macports.org>
	<20090611054308.GM32363@ninagal.withay.com>
	<AE30D0B2-9ED1-4874-AC72-673432861F82@macports.org>
Message-ID: <20090611072634.GN32363@ninagal.withay.com>

On Thu, Jun 11, 2009 at 01:11:22AM -0500, Ryan Schmidt said:
> On Jun 11, 2009, at 00:43, Bryan Blackburn wrote:
[...]
>>
>> Does anyone know why cyrus-sasl2 has that pre-configure check?  I found
>> tickets #17158 and #17328, the former being the one which added it but 
>> with
>> no description of why.  Having just commented-out the pre-configure  
>> bit,
>> upgrading from 2.1.22 to 2.1.23 worked just fine.  Is it
>> OS-version-specific, arch-specific, or MacPorts-version-specific?
>
> I also have no problem upgrading from 2.1.22 to 2.1.23, on Mac OS X  
> 10.4.11 Intel with Xcode 2.5 and MacPorts 1.7.1.
>
> But if you downgrade your cyrus-sasl2 to 2.1.21 first, then try to  
> upgrade, you should get the failure I got (see below).

Ah, so the secret is to come from the .21 version...okay I've attached a
patch to ticket #17328 which should deal with this.  The patch is a bit
kludgy but without messing around with the autoconf stuff (which is pretty
old), this is the simplest way to deal with it.

Bryan

[...]


From d.l.tDeContes at free.fr  Thu Jun 11 04:54:32 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Thu, 11 Jun 2009 13:54:32 +0200
Subject: checking for gcc
In-Reply-To: <76132DA4-9574-42CE-BAB5-BED6C81AC5B9@macports.org>
References: <675B1A6E-67F6-4E53-93B6-5C5EB56F7B07@free.fr>	<E63B84F6-3A00-4DD3-BC6D-A0C67A136874@macports.org>	<FF7EA160-0957-44FB-B331-01CFFEE84F36@free.fr>	<5BCA1EB2-FEC2-4296-A8F9-0A92330D006F@macports.org>	<5E8AF47F-A3B2-4FD0-A2AB-8EE7420A59A5@free.fr>	<924BD5D8-DB5F-4197-ACAA-1A2035B4A1BC@macports.org>
	<E2CD7888-0F10-41C8-890F-CA98FF4B34C6@free.fr>
	<49FC5405.5000606@macports.org>
	<0DA2076E-98CA-445E-9853-A72398328D8B@free.fr>
	<49FCC9F6.9000909@macports.org>
	<D4513BED-17AD-41AA-9944-520C0698188E@free.fr>
	<4A215383.9080301@macports.org>
	<51274091-0441-44ED-9C4C-674E8C388293@free.fr>
	<76132DA4-9574-42CE-BAB5-BED6C81AC5B9@macports.org>
Message-ID: <9C7C8AB2-8029-4573-8EE4-3DE91E09BF51@free.fr>


Le 11 juin 09 ? 06:51, Ryan Schmidt a ?crit :

> On Jun 10, 2009, at 18:49, Thomas De Contes wrote:
>
>> basic users are expected to compile ports but not MacPorts itself,  
>> they are expected to install binaries of MacPorts itself :-)
>> sorry, i forgot it :-)
>
> Well, a user who types "sudo port selfupdate" causes MacPorts to  
> build itself from source...

yes but in a "closed" environement (for example i suppose that PATH  
is replaced by binpath), like for ports

>
>
>>> Having MacPorts installation with a different prefix in PATH during
>>> configure might fail anyway if certain ports are installed (e.g.  
>>> tcl).
>>> Therefore, use a clean environment with the system's default PATH  
>>> if you
>>> don't want to use MacPorts for that.
>>
>> well, i need to compile MacPorts because i don't want to give it  
>> root rights
>
> Same here.

ok :-)

>
>
>> it's not very constraining,
>> just, sometimes i have tinny problems, and in general there is a  
>> solution :-)
>>
>>
>> but it may be very annoying, if the installation of some ports  
>> avoids to rebuild MacPorts :-(
>>
>> is there a simple way to use the system's default PATH, just for  
>> the time to build MacPorts ?
>
> Just do it! Run
>
> export PATH="/bin:/sbin:/usr/bin:/usr/sbin"
>
> before you run the configure, make and make install commands.  
> That's what I do. Then close the Terminal window to get your  
> previous PATH back.

ok :-)
i don't like very much to have fixed things (for example binpath uses  
a x11prefix path which can vary (i think)),
but if you do that, it must be right :-)

thank you :-)


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Thu Jun 11 04:56:58 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Thu, 11 Jun 2009 13:56:58 +0200
Subject: binpath
In-Reply-To: <1592A4A7-C99D-4598-BCB4-01781591A829@macports.org>
References: <EC4D6790-2149-417A-A409-DD4768427A9A@free.fr>
	<1592A4A7-C99D-4598-BCB4-01781591A829@macports.org>
Message-ID: <0D66CED9-2A20-4D38-B9F4-4AC71046EC02@free.fr>


Le 11 juin 09 ? 06:54, Ryan Schmidt a ?crit :

>
> On Jun 10, 2009, at 18:28, Thomas De Contes wrote:
>
>> i want to install the port "gnat-gcc"
>> for that, it needs to use an other (older) gnat
>
> IMHO this port is in violation of the basic requirement that a port  
> should install everything it needs. If gnat needs an older version  
> of gnat to build, gnat must download and use an older version of gnat.

a port can download and use binaries ?
i thought that it has to download only sources and compile all

> The port ghc gives an example of how such a bootstrap can be done.

thank you, i'll report it :-)


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Thu Jun 11 05:02:03 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Thu, 11 Jun 2009 14:02:03 +0200
Subject: python25
In-Reply-To: <3A3FEF56-18F3-4AB2-87E9-8C00C9553146@macports.org>
References: <3860C771-9EE4-4549-828C-7D13CAAD2D69@free.fr>	<49F472A6.7030307@macports.org>	<CBA597D7-E190-4873-BD36-FBAC52756B01@free.fr>	<49F47BED.5010708@macports.org>	<5D2365F4-3631-48A7-A993-C357EE516F13@macports.org>
	<EFDA7A12-4784-4A33-ABC3-2B213CF5E845@free.fr>
	<49FC738D.3090305@macports.org>
	<138F1380-C23C-431F-8E97-65B4D155C370@free.fr>
	<49FCA592.90403@macports.org>
	<008AB901-2C56-41EA-BF89-02D2ACF38FA3@free.fr>
	<EC944374-2D60-494F-B1F7-CC0DCBC7C3D9@macports.org>
	<D214B7CB-254E-48E3-AF30-DBC982054145@free.fr>
	<3A3FEF56-18F3-4AB2-87E9-8C00C9553146@macports.org>
Message-ID: <902BD87F-586C-4665-92CA-DBC3A7F97E70@free.fr>


Le 11 juin 09 ? 06:55, Ryan Schmidt a ?crit :

>
> On Jun 10, 2009, at 16:26, Thomas De Contes wrote:
>
>>>> because it tries to Activate the aleady compiled python25,  
>>>> despite the fact that i recompiled MacPorts with differents options
>>>
>>> Then you will need to uninstall that python25 and recompile it.
>>>
>>> Note that you don't need to recompile MacPorts to change  
>>> applications_dir or most of the other variables. All it does when  
>>> you use --with-applications-dir is that it writes the value of  
>>> that argument to the macports.conf file. So you can edit that  
>>> file yourself later to change the values.
>>
>> but i want to maintain a script which is able to install MacPorts  
>> or update it, according to that which it needs
>
> Good idea, I have one of those too!
>
>
>> well, is it possible to update macports.conf with ./configure  
>> (except deleting it) ?
>> i looked at "./configure --help" but i didn't find anything (but i  
>> don't know it very well)
>
> I don't believe running ./configure will modify an existing  
> macports.conf.

ok, i will remove it

have i also to remove all macports/etc/macports/*.conf files ? and  
other files ?


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Thu Jun 11 05:27:43 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Thu, 11 Jun 2009 14:27:43 +0200
Subject: subversion on 10.4
In-Reply-To: <E61ECED4-BB20-4A22-8B35-15FDB70B29D3@macports.org>
References: <C7F17FBC-FCE3-4AE0-8990-BF1C9DFFB6E8@free.fr>
	<7FEB6D78-51E7-4E17-9165-ACFF789982E9@macports.org>
	<83E18B9A-23AA-41A3-88EB-7572FC212DFB@free.fr>
	<DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
	<14969FAC-79FB-435F-9F10-7CBFBDCDD460@free.fr>
	<78A44A99-01CE-4CC4-8AD1-B369F8F25590@macports.org>
	<7CDE2DAC-5E87-4993-9571-FD06D4F1581D@free.fr>
	<E61ECED4-BB20-4A22-8B35-15FDB70B29D3@macports.org>
Message-ID: <BE8606C5-1EEF-485A-9C38-CB7BE4E553AE@free.fr>


Le 11 juin 09 ? 06:54, Ryan Schmidt a ?crit :

>
> On Jun 10, 2009, at 17:10, Thomas De Contes wrote:
>
>>
>> Le 10 juin 09 ? 23:09, Ryan Schmidt a ?crit :
>>
>>> On Jun 10, 2009, at 15:49, Thomas De Contes wrote:
>>>
>>>> Le 31 mai 09 ? 07:28, Ryan Schmidt a ?crit :
>>>>
>>>>>>> The workaround is to deactivate or uninstall 1.5.x and then  
>>>>>>> clean and install 1.6.x.
>>>>
>>>> ... why not simply add the deactivate operation in portfile, to  
>>>> upgrade ? :-)
>>>>
>>>> on top of that it is done anyway, but usually it is done after  
>>>> building, not before,
>>>
>>> I'm sorry, that cannot be changed by a port.
>>>
>>> The order in which MacPorts base runs the phases is correct.
>>>
>>> What we need to do is make Subversion build a new version  
>>> correctly even if an old version is active.
>>
>> but there is also a problem with cyrus-sasl2,
>> isn't it the same ?
>
> I see the same symptom, yes. A similar solution would need to be  
> applied to the cyrus-sasl2 port. If you can come up with a general  
> change that should be made to MacPorts base that will not adversely  
> affect too many other ports, we can certainly consider it.

i'm not sure to understand the proposal

i suggest that a port would be allowed to deactivate the old version  
before build the new version, even if there is always a better solution
it would allow to have a workaroud, waiting to find the famous better  
solution, since, anyway, if it is not done automatically, users have  
to do the same manually .... so why prohibit it?

of course, the default should not be changed, and you can disadvise  
it (like for changing compiler, for example)


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From face at CentosPrime.COM  Thu Jun 11 07:49:04 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Thu, 11 Jun 2009 07:49:04 -0700
Subject: Reverting to previous ports - mysql5
In-Reply-To: <97886453-D279-4377-87C2-E762CCFAA797@macports.org>
References: <ACDC7F11-A8AA-43AA-9ECF-BA33E281987C@CentosPrime.COM>
	<D6FC8DC0-BE5D-4A69-BF66-29BEF4C908F4@macports.org>
	<2071BCA6-9BF4-4899-BEC2-032EDF2A469F@CentosPrime.COM>
	<7A560FF1-110B-49AB-8DB9-79C03949C76A@macports.org>
	<683AB3C2-5003-4802-935A-2480CA03361A@CentosPrime.COM>
	<97886453-D279-4377-87C2-E762CCFAA797@macports.org>
Message-ID: <C59975AF-577D-487F-BE43-65D2B95938EF@CentosPrime.COM>

On 2009-06-10 , at 22:17 , Ryan Schmidt wrote:

>>> I am guessing it is using the port name as the key for the  
>>> hostconfig file, and that the hostconfig file does not support  
>>> hyphens in its variable names. So that would be a problem. Perhaps  
>>> I can tell it to continue to use the key  
>>> "mysql5" ("startupitem.name mysql5"?) You can try adding that to  
>>> the mysql5-server port already if you want, but I will also test  
>>> when I'm back at my Panther machine tonight.
>>
>> That certainly did the trick - to think a "-" in a name should be  
>> such a problem...
>
> I committed this change in r52144. I didn't test on Panther yet so  
> please let me know if that works now.


sudo SystemStarter -d restart mysql5

Running command (13345): /Library/StartupItems/mysql5/mysql5 restart
Unable to load localization strings for /Library/StartupItems/mysql5
Restarting mysql5
Unable to load localization strings for /Library/StartupItems/mysql5
Stopping mysql5
Shutting down MySQL. SUCCESS!
Unable to load localization strings for /Library/StartupItems/mysql5
Starting mysql5
Starting MySQL..Unable to load localization strings for /Library/ 
StartupItems/mysql5
Waiting for mysql5
  SUCCESS!
Finished mysql5 (13345)

I don't recall ever seeing the bit about localization strings.

mysql5 restarts properly, thus both "stop" and "start" work.

Thanks.

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From macports at tprfct.net  Thu Jun 11 09:52:57 2009
From: macports at tprfct.net (Kastus Shchuka)
Date: Thu, 11 Jun 2009 09:52:57 -0700
Subject: texlive_base @2007_7+nox11 upgrade problem
In-Reply-To: <A59B4D9C-9C71-40FE-9EA7-D823D517E702@macports.org>
References: <C3C770DA-F5D6-47BF-B23B-88BE49766C57@tprfct.net>
	<A59B4D9C-9C71-40FE-9EA7-D823D517E702@macports.org>
Message-ID: <7661A3C8-BCC7-4EA0-BEAA-DA589F232A84@tprfct.net>


On Jun 10, 2009, at 9:58 PM, Ryan Schmidt wrote:

> On Jun 10, 2009, at 13:47, Kastus Shchuka wrote:
>
>> I do have texlive_base installed with no_x11 variant, version  
>> 2007_6. Now 2007_7 is available but when I try
>> to upgrade texlive_base specifically selecting no_x11 variant it  
>> still pulls openmotif as a dependency.
>>
>> The command I am using is this:
>>
>> sudo port upgrade texlive_base +no_x11
>>
>> When I query dependencies of texlive_base it does not show openmotif:
>>
>> port deps texlive_base +no_x11
>> texlive_base has build dependencies on:
>> 	perl5
>> texlive_base has library dependencies on:
>> 	freetype
>> 	fontconfig
>> 	ncurses
>> 	zlib
>> 	libpng
>> 	texinfo
>> 	texi2html
>> 	ghostscript
>> 	texlive_texmf-minimal
>> 	texlive_texmf-full
>>
>> So how do I upgrade texlive_base without bringing in openmotif? Is  
>> it a bug in portfile?
>
> Short answer: sync your ports and try again.
>
> Longer answer: for about a day between June 8 and June 9,  
> texlive_base always brought in the openmotif dependency. Then it was  
> changed to only bring it in if you use the +motif variant.
>
>

Sorry, it does not help. I synced, got portfile r52085 which is  
supposed to fix the issue but it still attempts to pull in openmotif:

Kastus-iBook:~ pike$ sudo port upgrade texlive_base +no_x11
Password:
--->  Building openmotif

Should "lib:libXm:openmotif" be appended to line 89 of the port file?

Thanks, -Kastus






From ryandesign at macports.org  Thu Jun 11 11:03:27 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 11 Jun 2009 13:03:27 -0500
Subject: python25
In-Reply-To: <902BD87F-586C-4665-92CA-DBC3A7F97E70@free.fr>
References: <3860C771-9EE4-4549-828C-7D13CAAD2D69@free.fr>	<49F472A6.7030307@macports.org>	<CBA597D7-E190-4873-BD36-FBAC52756B01@free.fr>	<49F47BED.5010708@macports.org>	<5D2365F4-3631-48A7-A993-C357EE516F13@macports.org>
	<EFDA7A12-4784-4A33-ABC3-2B213CF5E845@free.fr>
	<49FC738D.3090305@macports.org>
	<138F1380-C23C-431F-8E97-65B4D155C370@free.fr>
	<49FCA592.90403@macports.org>
	<008AB901-2C56-41EA-BF89-02D2ACF38FA3@free.fr>
	<EC944374-2D60-494F-B1F7-CC0DCBC7C3D9@macports.org>
	<D214B7CB-254E-48E3-AF30-DBC982054145@free.fr>
	<3A3FEF56-18F3-4AB2-87E9-8C00C9553146@macports.org>
	<902BD87F-586C-4665-92CA-DBC3A7F97E70@free.fr>
Message-ID: <A9FB31F5-88F3-48B6-9AC1-0F04F0390AC5@macports.org>

On Jun 11, 2009, at 07:02, Thomas De Contes wrote:

> Le 11 juin 09 ? 06:55, Ryan Schmidt a ?crit :
>
>> I don't believe running ./configure will modify an existing  
>> macports.conf.
>
> ok, i will remove it
>
> have i also to remove all macports/etc/macports/*.conf files ?

You don't have to remove them, but I don't believe MacPorts updates  
them if they exist.

> and other files ?

Which other files?



From ryandesign at macports.org  Thu Jun 11 11:17:40 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 11 Jun 2009 13:17:40 -0500
Subject: binpath
In-Reply-To: <0D66CED9-2A20-4D38-B9F4-4AC71046EC02@free.fr>
References: <EC4D6790-2149-417A-A409-DD4768427A9A@free.fr>
	<1592A4A7-C99D-4598-BCB4-01781591A829@macports.org>
	<0D66CED9-2A20-4D38-B9F4-4AC71046EC02@free.fr>
Message-ID: <09A3D83A-D42A-499D-A638-7AE64FDC6C5F@macports.org>


On Jun 11, 2009, at 06:56, Thomas De Contes wrote:

> Le 11 juin 09 ? 06:54, Ryan Schmidt a ?crit :
>
>> On Jun 10, 2009, at 18:28, Thomas De Contes wrote:
>>
>>> i want to install the port "gnat-gcc"
>>> for that, it needs to use an other (older) gnat
>>
>> IMHO this port is in violation of the basic requirement that a  
>> port should install everything it needs. If gnat needs an older  
>> version of gnat to build, gnat must download and use an older  
>> version of gnat.
>
> a port can download and use binaries ?
> i thought that it has to download only sources and compile all

Some ports download and install a binary. My ports oracle- 
instantclient, isightcapture and sleepwatcher do this because source  
is not available. istumbler and blender presumably do this because  
the person who contributed the ports encountered insurmountable  
obstacles trying to build from source.

But I was talking about ports that need to use a binary to build  
themselves from source. This is common with compilers like gnat-gcc  
and ghc which need an earlier version of themselves to compile the  
newer version. This is not a problem for gcc because an older version  
of gcc is included with Xcode. But gnat-gcc and ghc do not exist  
already on OS X, therefore the ports must somehow provide one. ghc  
does this the correct way, IMHO: It downloads a binary version of ghc  
specific to the OS and processor, unpacks it, and uses it to build  
the final version of ghc that gets installed. The gnat-gcc port does  
this in a poor way, IMHO: it requires the user to either have a prior  
version of the gnat-gcc port installed (obviously not possible the  
first time a user tries to install the port), or to manually download  
and install a binary version of gnat-gcc to a specific location  
outside the MacPorts prefix.


From ryandesign at macports.org  Thu Jun 11 11:20:47 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 11 Jun 2009 13:20:47 -0500
Subject: checking for gcc
In-Reply-To: <9C7C8AB2-8029-4573-8EE4-3DE91E09BF51@free.fr>
References: <675B1A6E-67F6-4E53-93B6-5C5EB56F7B07@free.fr>	<E63B84F6-3A00-4DD3-BC6D-A0C67A136874@macports.org>	<FF7EA160-0957-44FB-B331-01CFFEE84F36@free.fr>	<5BCA1EB2-FEC2-4296-A8F9-0A92330D006F@macports.org>	<5E8AF47F-A3B2-4FD0-A2AB-8EE7420A59A5@free.fr>	<924BD5D8-DB5F-4197-ACAA-1A2035B4A1BC@macports.org>
	<E2CD7888-0F10-41C8-890F-CA98FF4B34C6@free.fr>
	<49FC5405.5000606@macports.org>
	<0DA2076E-98CA-445E-9853-A72398328D8B@free.fr>
	<49FCC9F6.9000909@macports.org>
	<D4513BED-17AD-41AA-9944-520C0698188E@free.fr>
	<4A215383.9080301@macports.org>
	<51274091-0441-44ED-9C4C-674E8C388293@free.fr>
	<76132DA4-9574-42CE-BAB5-BED6C81AC5B9@macports.org>
	<9C7C8AB2-8029-4573-8EE4-3DE91E09BF51@free.fr>
Message-ID: <43359CE0-B3FF-47C0-ABF0-51277F12D02F@macports.org>

On Jun 11, 2009, at 06:54, Thomas De Contes wrote:

> Le 11 juin 09 ? 06:51, Ryan Schmidt a ?crit :
>
>> Well, a user who types "sudo port selfupdate" causes MacPorts to  
>> build itself from source...
>
> yes but in a "closed" environement (for example i suppose that PATH  
> is replaced by binpath), like for ports

True. MacPorts clears the environment, and then sets only specific  
environment variables, such as PATH=binpath.


>>> is there a simple way to use the system's default PATH, just for  
>>> the time to build MacPorts ?
>>
>> Just do it! Run
>>
>> export PATH="/bin:/sbin:/usr/bin:/usr/sbin"
>>
>> before you run the configure, make and make install commands.  
>> That's what I do. Then close the Terminal window to get your  
>> previous PATH back.
>
> ok :-)
> i don't like very much to have fixed things (for example binpath  
> uses a x11prefix path which can vary (i think)),

x11prefix was /usr/X11R6 in Tiger and earlier and /usr/X11 in Leopard  
and later. But x11prefix has been removed entirely from MacPorts  
trunk and will not exist anymore in MacPorts 1.8.0 and later. Any  
required parts of X11 are now installed using MacPorts just like any  
other port.

> but if you do that, it must be right :-)

Well, it works for me. :)



From macports at tprfct.net  Thu Jun 11 13:26:16 2009
From: macports at tprfct.net (Kastus Shchuka)
Date: Thu, 11 Jun 2009 13:26:16 -0700
Subject: texlive_base @2007_7+nox11 upgrade problem
In-Reply-To: <7661A3C8-BCC7-4EA0-BEAA-DA589F232A84@tprfct.net>
References: <C3C770DA-F5D6-47BF-B23B-88BE49766C57@tprfct.net>
	<A59B4D9C-9C71-40FE-9EA7-D823D517E702@macports.org>
	<7661A3C8-BCC7-4EA0-BEAA-DA589F232A84@tprfct.net>
Message-ID: <CB0A1FB7-7A4C-41A2-B895-26D41BD7A4A2@tprfct.net>

On Jun 11, 2009, at 9:52 AM, Kastus Shchuka wrote:

>
> Should "lib:libXm:openmotif" be appended to line 89 of the port file?

Sorry, I meant line 83, looked at the wrong place. And that is where  
this string was in the previous revision r52043 (line 79 there).

I am still puzzled what brings in openmotif as dependency while it is  
not reported by port deps command. Do we need to explicitly  
depends_lib-delete it in no_x11 variant?

Thanks, -Kastus

From mailinglists at cserb.net  Thu Jun 11 13:47:00 2009
From: mailinglists at cserb.net (Cristian Serb)
Date: Thu, 11 Jun 2009 22:47:00 +0200
Subject: Xorg/X11 for every second port
Message-ID: <ECA43A0F-E5E4-4F66-B51C-6B034EF4D87E@cserb.net>

Hi there,

ever since I use macports I notice that it tries very often to install  
Xorg along with ports that actually don't need it. Today I tried to  
install trac and again ... Xorg. I can't even remember the numerous  
other trials I <Ctrl-C>ed because of Xorg. I'm surprised that I can  
install nmap without Xorg...

So what is this? Is there a way to spot it?

Many Thanks,
Cristian 

From blb at macports.org  Thu Jun 11 14:05:42 2009
From: blb at macports.org (Bryan Blackburn)
Date: Thu, 11 Jun 2009 15:05:42 -0600
Subject: Xorg/X11 for every second port
In-Reply-To: <ECA43A0F-E5E4-4F66-B51C-6B034EF4D87E@cserb.net>
References: <ECA43A0F-E5E4-4F66-B51C-6B034EF4D87E@cserb.net>
Message-ID: <20090611210542.GD4205@ninagal.withay.com>

On Thu, Jun 11, 2009 at 10:47:00PM +0200, Cristian Serb said:
> Hi there,
>
> ever since I use macports I notice that it tries very often to install  
> Xorg along with ports that actually don't need it. Today I tried to  
> install trac and again ... Xorg. I can't even remember the numerous other 
> trials I <Ctrl-C>ed because of Xorg. I'm surprised that I can install nmap 
> without Xorg...
>
> So what is this? Is there a way to spot it?

trac uses python26 (since trac is python-based), and python26 needs tk which
is where the xorg stuff originates.  See

<http://trac.macports.org/wiki/FAQ#WhyisMacPortsusingitsownlibraries>

and

<http://trac.macports.org/wiki/FAQ#pydeps>

Bryan


>
> Many Thanks,
> Cristian_______________________________________________

From mailinglists at cserb.net  Thu Jun 11 14:12:33 2009
From: mailinglists at cserb.net (Cristian Serb)
Date: Thu, 11 Jun 2009 23:12:33 +0200
Subject: Xorg/X11 for every second port
In-Reply-To: <20090611210542.GD4205@ninagal.withay.com>
References: <ECA43A0F-E5E4-4F66-B51C-6B034EF4D87E@cserb.net>
	<20090611210542.GD4205@ninagal.withay.com>
Message-ID: <BC446AE8-D57B-4C45-9A36-E6280AEEE3DA@cserb.net>

But on gentoo e.g. I could specify not to install certain deps. Is  
there a way to do this for macports?

On Jun 11, 2009, at 11:05 PM, Bryan Blackburn wrote:

> On Thu, Jun 11, 2009 at 10:47:00PM +0200, Cristian Serb said:
>> Hi there,
>>
>> ever since I use macports I notice that it tries very often to  
>> install
>> Xorg along with ports that actually don't need it. Today I tried to
>> install trac and again ... Xorg. I can't even remember the numerous  
>> other
>> trials I <Ctrl-C>ed because of Xorg. I'm surprised that I can  
>> install nmap
>> without Xorg...
>>
>> So what is this? Is there a way to spot it?
>
> trac uses python26 (since trac is python-based), and python26 needs  
> tk which
> is where the xorg stuff originates.  See
>
> <http://trac.macports.org/wiki/FAQ#WhyisMacPortsusingitsownlibraries>
>
> and
>
> <http://trac.macports.org/wiki/FAQ#pydeps>
>
> Bryan
>
>
>>
>> Many Thanks,
>> Cristian_______________________________________________
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From blb at macports.org  Thu Jun 11 14:29:36 2009
From: blb at macports.org (Bryan Blackburn)
Date: Thu, 11 Jun 2009 15:29:36 -0600
Subject: Xorg/X11 for every second port
In-Reply-To: <BC446AE8-D57B-4C45-9A36-E6280AEEE3DA@cserb.net>
References: <ECA43A0F-E5E4-4F66-B51C-6B034EF4D87E@cserb.net>
	<20090611210542.GD4205@ninagal.withay.com>
	<BC446AE8-D57B-4C45-9A36-E6280AEEE3DA@cserb.net>
Message-ID: <20090611212936.GE4205@ninagal.withay.com>

On Thu, Jun 11, 2009 at 11:12:33PM +0200, Cristian Serb said:
> But on gentoo e.g. I could specify not to install certain deps. Is there a 
> way to do this for macports?

No, the python ports used to try and use variants or separate ports to break
things out (see that pydeps anchor on the FAQ) but there have been issues,
also see ticket #12369:

<http://trac.macports.org/ticket/12369>

Bryan


>
> On Jun 11, 2009, at 11:05 PM, Bryan Blackburn wrote:
>
>> On Thu, Jun 11, 2009 at 10:47:00PM +0200, Cristian Serb said:
>>> Hi there,
>>>
>>> ever since I use macports I notice that it tries very often to  
>>> install
>>> Xorg along with ports that actually don't need it. Today I tried to
>>> install trac and again ... Xorg. I can't even remember the numerous  
>>> other
>>> trials I <Ctrl-C>ed because of Xorg. I'm surprised that I can install 
>>> nmap
>>> without Xorg...
>>>
>>> So what is this? Is there a way to spot it?
>>
>> trac uses python26 (since trac is python-based), and python26 needs tk 
>> which
>> is where the xorg stuff originates.  See
>>
>> <http://trac.macports.org/wiki/FAQ#WhyisMacPortsusingitsownlibraries>
>>
>> and
>>
>> <http://trac.macports.org/wiki/FAQ#pydeps>
>>
>> Bryan
>>
>>
>>>
>>> Many Thanks,
>>> Cristian_______________________________________________

From ryandesign at macports.org  Thu Jun 11 14:30:04 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 11 Jun 2009 16:30:04 -0500
Subject: Xorg/X11 for every second port
In-Reply-To: <BC446AE8-D57B-4C45-9A36-E6280AEEE3DA@cserb.net>
References: <ECA43A0F-E5E4-4F66-B51C-6B034EF4D87E@cserb.net>
	<20090611210542.GD4205@ninagal.withay.com>
	<BC446AE8-D57B-4C45-9A36-E6280AEEE3DA@cserb.net>
Message-ID: <A2E4F38A-D044-414E-A585-EA83EA17B848@macports.org>


On Jun 11, 2009, at 16:12, Cristian Serb wrote:

> But on gentoo e.g. I could specify not to install certain deps. Is  
> there a way to do this for macports?

Some ports have variants you can use. Type "port variants PORTNAME"  
to find the available variants for port PORTNAME. For example, you  
might find a variant called no_x11 to disable X11 stuff.


From ryandesign at macports.org  Thu Jun 11 14:34:38 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 11 Jun 2009 16:34:38 -0500
Subject: subversion on 10.4
In-Reply-To: <BE8606C5-1EEF-485A-9C38-CB7BE4E553AE@free.fr>
References: <C7F17FBC-FCE3-4AE0-8990-BF1C9DFFB6E8@free.fr>
	<7FEB6D78-51E7-4E17-9165-ACFF789982E9@macports.org>
	<83E18B9A-23AA-41A3-88EB-7572FC212DFB@free.fr>
	<DA4C03DE-D3D0-4D32-9FA9-D83503F64C65@macports.org>
	<14969FAC-79FB-435F-9F10-7CBFBDCDD460@free.fr>
	<78A44A99-01CE-4CC4-8AD1-B369F8F25590@macports.org>
	<7CDE2DAC-5E87-4993-9571-FD06D4F1581D@free.fr>
	<E61ECED4-BB20-4A22-8B35-15FDB70B29D3@macports.org>
	<BE8606C5-1EEF-485A-9C38-CB7BE4E553AE@free.fr>
Message-ID: <56E9DF2A-7E61-44EF-8511-9EFEE4EFD5BD@macports.org>

On Jun 11, 2009, at 07:27, Thomas De Contes wrote:

> Le 11 juin 09 ? 06:54, Ryan Schmidt a ?crit :
>
>> On Jun 10, 2009, at 17:10, Thomas De Contes wrote:
>>
>>> Le 10 juin 09 ? 23:09, Ryan Schmidt a ?crit :
>>>
>>>> On Jun 10, 2009, at 15:49, Thomas De Contes wrote:
>>>>
>>>>> Le 31 mai 09 ? 07:28, Ryan Schmidt a ?crit :
>>>>>
>>>>>>>> The workaround is to deactivate or uninstall 1.5.x and then  
>>>>>>>> clean and install 1.6.x.
>>>>>
>>>>> ... why not simply add the deactivate operation in portfile, to  
>>>>> upgrade ? :-)
>>>>>
>>>>> on top of that it is done anyway, but usually it is done after  
>>>>> building, not before,
>>>>
>>>> I'm sorry, that cannot be changed by a port.
>>>>
>>>> The order in which MacPorts base runs the phases is correct.
>>>>
>>>> What we need to do is make Subversion build a new version  
>>>> correctly even if an old version is active.
>>>
>>> but there is also a problem with cyrus-sasl2,
>>> isn't it the same ?
>>
>> I see the same symptom, yes. A similar solution would need to be  
>> applied to the cyrus-sasl2 port. If you can come up with a general  
>> change that should be made to MacPorts base that will not  
>> adversely affect too many other ports, we can certainly consider it.
>
> i'm not sure to understand the proposal
>
> i suggest that a port would be allowed to deactivate the old  
> version before build the new version, even if there is always a  
> better solution
> it would allow to have a workaroud, waiting to find the famous  
> better solution, since, anyway, if it is not done automatically,  
> users have to do the same manually .... so why prohibit it?
>
> of course, the default should not be changed, and you can disadvise  
> it (like for changing compiler, for example)

Allowing a port to deactivate the old version before building the new  
version, instead of after, would require new code in MacPorts base to  
allow that to happen. Someone would have to write this code. I would  
rather not expend developer time to do that when it is arguably a bug  
in the software, in this case a bug in cyrus-sasl2. We could either  
figure out how to fix cyrus-sasl2 so it can build properly even when  
an older version is already present, and then send that patch to the  
developers, or we could just report the problem to the developers and  
let them work out the correct fix. If you can help with either of  
these tasks I'm sure that would be appreciated.





From d.l.tDeContes at free.fr  Thu Jun 11 18:29:54 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Fri, 12 Jun 2009 03:29:54 +0200
Subject: Xcode 2.5
Message-ID: <069790F3-B135-4A43-929B-C9F9774445B8@free.fr>

hi :-)


it doesn't compile with Xcode 2.5, whereas it did compile with Xcode 2.5


+ PATH=/bin:/sbin:/usr/bin:/usr/sbin

+ ./configure --prefix=/Users/thomas/Documents/prgm/bin/autoinstall/ 
macports --with-install-user=thomas --with-install-group=thomas -- 
with-applications-dir=/Users/thomas/Documents/prgm/bin/autoinstall/ 
macports/Applications --with-tclpackage=/Users/thomas/Documents/prgm/ 
bin/autoinstall/macports/tcl --enable-readline
checking build system type... powerpc-apple-darwin8.11.0
checking host system type... powerpc-apple-darwin8.11.0
checking target system type... powerpc-apple-darwin8.11.0
checking MacPorts version... 1.7.1
checking for sw_vers... sw_vers
checking Mac OS X version... 10.4.11
checking Xcode version... 2.5
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: in `/Users/thomas/Documents/prgm/temporaire/macports':
configure: error: C compiler cannot create executables
See `config.log' for more details.
+ exit 77

http://dl.free.fr/lEckK6nnn


what's wrong ?


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From michaelgrunewald at yahoo.fr  Fri Jun 12 02:18:06 2009
From: michaelgrunewald at yahoo.fr (=?ISO-8859-1?Q?Gr=FCnewald_Micha=EBl?=)
Date: Fri, 12 Jun 2009 11:18:06 +0200
Subject: How to process docbook files ?
Message-ID: <B79250B3-D65D-411F-9811-635E32C5ADD6@yahoo.fr>

Dear list,

I recently installed openjade with macports, but whenever it is run,  
the program fails with a `message bus' error. An appropriate ticket  
has been filled on trac, and the bug was then reported to upstream  
maintainers. This history is rather old (about 1 year IIRC) and  
openjade is still unusable on macports.

(I have OS X 10.5.7 and macports 1.7.)

I was looking for a replacement solution, but did not find anything  
suitable. Any suggestion would be very much appreciated!

For instance, I can step back in the past and use a pre-1.3.2 openjade  
version, that may work with macports. Does anyone know which version  
would be suitable?
-- 
Cheers,
Micha?l


From ryandesign at macports.org  Fri Jun 12 03:40:18 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 12 Jun 2009 05:40:18 -0500
Subject: Xcode 2.5
In-Reply-To: <069790F3-B135-4A43-929B-C9F9774445B8@free.fr>
References: <069790F3-B135-4A43-929B-C9F9774445B8@free.fr>
Message-ID: <64831E57-A8EC-4F5A-8C17-EFC0C0A55C24@macports.org>

On Jun 11, 2009, at 20:29, Thomas De Contes wrote:

> it doesn't compile with Xcode 2.5, whereas it did compile with  
> Xcode 2.5
>
>
> + PATH=/bin:/sbin:/usr/bin:/usr/sbin
>
> + ./configure --prefix=/Users/thomas/Documents/prgm/bin/autoinstall/ 
> macports --with-install-user=thomas --with-install-group=thomas -- 
> with-applications-dir=/Users/thomas/Documents/prgm/bin/autoinstall/ 
> macports/Applications --with-tclpackage=/Users/thomas/Documents/ 
> prgm/bin/autoinstall/macports/tcl --enable-readline
> checking build system type... powerpc-apple-darwin8.11.0
> checking host system type... powerpc-apple-darwin8.11.0
> checking target system type... powerpc-apple-darwin8.11.0
> checking MacPorts version... 1.7.1
> checking for sw_vers... sw_vers
> checking Mac OS X version... 10.4.11
> checking Xcode version... 2.5
> checking for gcc... gcc
> checking for C compiler default output file name...
> configure: error: in `/Users/thomas/Documents/prgm/temporaire/ 
> macports':
> configure: error: C compiler cannot create executables
> See `config.log' for more details.
> + exit 77
>
> http://dl.free.fr/lEckK6nnn
>
>
> what's wrong ?


Can you attach the config.log so we can take a look at what it says?


From ryandesign at macports.org  Fri Jun 12 03:47:49 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 12 Jun 2009 05:47:49 -0500
Subject: Xcode 2.5
In-Reply-To: <64831E57-A8EC-4F5A-8C17-EFC0C0A55C24@macports.org>
References: <069790F3-B135-4A43-929B-C9F9774445B8@free.fr>
	<64831E57-A8EC-4F5A-8C17-EFC0C0A55C24@macports.org>
Message-ID: <DA016B23-737E-414E-964E-2BB3703D34D2@macports.org>


On Jun 12, 2009, at 05:40, Ryan Schmidt wrote:

> On Jun 11, 2009, at 20:29, Thomas De Contes wrote:
>
>> it doesn't compile with Xcode 2.5, whereas it did compile with  
>> Xcode 2.5
>>
>>
>> + PATH=/bin:/sbin:/usr/bin:/usr/sbin
>>
>> + ./configure --prefix=/Users/thomas/Documents/prgm/bin/ 
>> autoinstall/macports --with-install-user=thomas --with-install- 
>> group=thomas --with-applications-dir=/Users/thomas/Documents/prgm/ 
>> bin/autoinstall/macports/Applications --with-tclpackage=/Users/ 
>> thomas/Documents/prgm/bin/autoinstall/macports/tcl --enable-readline
>> checking build system type... powerpc-apple-darwin8.11.0
>> checking host system type... powerpc-apple-darwin8.11.0
>> checking target system type... powerpc-apple-darwin8.11.0
>> checking MacPorts version... 1.7.1
>> checking for sw_vers... sw_vers
>> checking Mac OS X version... 10.4.11
>> checking Xcode version... 2.5
>> checking for gcc... gcc
>> checking for C compiler default output file name...
>> configure: error: in `/Users/thomas/Documents/prgm/temporaire/ 
>> macports':
>> configure: error: C compiler cannot create executables
>> See `config.log' for more details.
>> + exit 77
>>
>> http://dl.free.fr/lEckK6nnn
>>
>>
>> what's wrong ?
>
>
> Can you attach the config.log so we can take a look at what it says?


Oh, that's what the link was. The first time I clicked it, it showed  
me stuff I couldn't read in French, but the second time it downloaded  
the config log. Ok.


It says:

can't locate file for: -lcrt1.o

This is an error I see mentioned in several places on Google. Many  
are for Panther, but some ask: do you have the file /usr/lib/crt1.o?  
You should, and I do on my system. If you don't, some part of your  
system isn't installed right. Grepping through receipts, it appears  
this file is provided by DevSDK.pkg, if you want to try to reinstall it.



From d.l.tDeContes at free.fr  Fri Jun 12 10:21:08 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Fri, 12 Jun 2009 19:21:08 +0200
Subject: python25
In-Reply-To: <A9FB31F5-88F3-48B6-9AC1-0F04F0390AC5@macports.org>
References: <3860C771-9EE4-4549-828C-7D13CAAD2D69@free.fr>	<49F472A6.7030307@macports.org>	<CBA597D7-E190-4873-BD36-FBAC52756B01@free.fr>	<49F47BED.5010708@macports.org>	<5D2365F4-3631-48A7-A993-C357EE516F13@macports.org>
	<EFDA7A12-4784-4A33-ABC3-2B213CF5E845@free.fr>
	<49FC738D.3090305@macports.org>
	<138F1380-C23C-431F-8E97-65B4D155C370@free.fr>
	<49FCA592.90403@macports.org>
	<008AB901-2C56-41EA-BF89-02D2ACF38FA3@free.fr>
	<EC944374-2D60-494F-B1F7-CC0DCBC7C3D9@macports.org>
	<D214B7CB-254E-48E3-AF30-DBC982054145@free.fr>
	<3A3FEF56-18F3-4AB2-87E9-8C00C9553146@macports.org>
	<902BD87F-586C-4665-92CA-DBC3A7F97E70@free.fr>
	<A9FB31F5-88F3-48B6-9AC1-0F04F0390AC5@macports.org>
Message-ID: <15627CE4-7497-4EE1-86AF-04091EFDA3E6@free.fr>


Le 11 juin 09 ? 20:03, Ryan Schmidt a ?crit :

> On Jun 11, 2009, at 07:02, Thomas De Contes wrote:
>
>> Le 11 juin 09 ? 06:55, Ryan Schmidt a ?crit :
>>
>>> I don't believe running ./configure will modify an existing  
>>> macports.conf.
>>
>> ok, i will remove it
>>
>> have i also to remove all macports/etc/macports/*.conf files ?
>
> You don't have to remove them, but I don't believe MacPorts updates  
> them if they exist.

MacPorts does not update them by default


the best would be that MacPorts updates them regarding what's on ./ 
configure cli, and preserve what has been manually set and not  
specified on ./configure cli

if it's not possible, no matter, i can remove them :-)
I hesitate simply between removing only macports/etc/macports/ 
macports.conf or all macports/etc/macports/*.conf


>
>> and other files ?
>
> Which other files?


in case where there would be some other files that MacPorts wouldn't  
update, and that may cause some things broken



ps : thank you for answers on other threads :-)
(i won't reply to each)


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Fri Jun 12 14:45:41 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Fri, 12 Jun 2009 23:45:41 +0200
Subject: date of installation of ports
Message-ID: <CFA4E8E8-58F9-47D8-8813-2CAEBDBF203C@free.fr>

hi :-)


is it possible to have a list of installed ports, like "port  
installed", with the date of installation (or upgrade)  of each port ?


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From ryandesign at macports.org  Fri Jun 12 16:58:08 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 12 Jun 2009 18:58:08 -0500
Subject: date of installation of ports
In-Reply-To: <CFA4E8E8-58F9-47D8-8813-2CAEBDBF203C@free.fr>
References: <CFA4E8E8-58F9-47D8-8813-2CAEBDBF203C@free.fr>
Message-ID: <F8268450-7BEF-4E6C-BE73-450A1F532F40@macports.org>

On Jun 12, 2009, at 16:45, Thomas De Contes wrote:

> is it possible to have a list of installed ports, like "port  
> installed", with the date of installation (or upgrade)  of each port ?

MacPorts doesn't have a command to show you that list, but you can  
get a listing of all the software directories. The date the directory  
was created is the date that software was installed or last upgraded.


ls -ld /opt/local/var/macports/software/*/*


Example from my system:


$ ls -ld /mp/var/macports/software/*/* | head
drwxr-xr-x   3 rschmidt  rschmidt      102 Jul 30  2008 /mp/var/ 
macports/software/CronniX/3.0.2_0+universal
drwxr-xr-x   3 rschmidt  rschmidt      102 Jun  1 19:55 /mp/var/ 
macports/software/ImageMagick/6.5.2-9_0+q8
drwxr-xr-x   3 rschmidt  rschmidt      102 Jan 16 04:45 /mp/var/ 
macports/software/Xft2/2.1.13_1+universal
drwxr-xr-x   3 rschmidt  rschmidt      102 Jun 11 14:15 /mp/var/ 
macports/software/XviD/1.2.0_0
drwxr-xr-x   3 rschmidt  rschmidt      102 Jun  9 23:04 /mp/var/ 
macports/software/aalib/1.4rc5_4
drwxr-xr-x   4 root      rschmidt      136 Dec 20 01:26 /mp/var/ 
macports/software/apache2/2.2.11_0
drwxr-xr-x   3 rschmidt  rschmidt      102 Jun  7 02:09 /mp/var/ 
macports/software/apr-util/1.3.7_0
drwxr-xr-x   3 rschmidt  rschmidt      102 Jun  7 02:08 /mp/var/ 
macports/software/apr/1.3.5_0
drwxr-xr-x   3 rschmidt  rschmidt      102 Jun  5 19:52 /mp/var/ 
macports/software/ardour2/2.5_1
drwxr-xr-x   3 rschmidt  rschmidt      102 Jun 12 00:07 /mp/var/ 
macports/software/ardour2/2.8_0


From blb at macports.org  Fri Jun 12 17:22:05 2009
From: blb at macports.org (Bryan Blackburn)
Date: Fri, 12 Jun 2009 18:22:05 -0600
Subject: How to process docbook files ?
In-Reply-To: <B79250B3-D65D-411F-9811-635E32C5ADD6@yahoo.fr>
References: <B79250B3-D65D-411F-9811-635E32C5ADD6@yahoo.fr>
Message-ID: <20090613002204.GF65270@ninagal.withay.com>

On Fri, Jun 12, 2009 at 11:18:06AM +0200, Gr?newald Micha?l said:
> Dear list,
>
> I recently installed openjade with macports, but whenever it is run, the 
> program fails with a `message bus' error. An appropriate ticket has been 
> filled on trac, and the bug was then reported to upstream maintainers. 
> This history is rather old (about 1 year IIRC) and openjade is still 
> unusable on macports.

It's usable, you just have to be sure to give it the right command line
arguments; see the comment at #15859 for how to use it without getting a bus
error:

<http://trac.macports.org/ticket/15859#comment:6>

Bryan


>
> (I have OS X 10.5.7 and macports 1.7.)
>
> I was looking for a replacement solution, but did not find anything  
> suitable. Any suggestion would be very much appreciated!
>
> For instance, I can step back in the past and use a pre-1.3.2 openjade  
> version, that may work with macports. Does anyone know which version  
> would be suitable?
> -- 
> Cheers,
> Micha?l

From d.l.tDeContes at free.fr  Fri Jun 12 17:20:29 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Sat, 13 Jun 2009 02:20:29 +0200
Subject: pkgconfig / dependencies in xorg ?
Message-ID: <1E44991E-5203-4CA6-B47E-15A409EFC660@free.fr>

hi :-)


here is what i get when i upgrade ports on a very old installation :
port -u upgrade outdated


--->  Configuring xorg-libX11
Error: Target org.macports.configure returned: configure failure:  
shell command " cd "/Users/thomas/Documents/prgm/bin/autoinstall/ 
macports/var/macports/build/ 
_Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sourc 
es_rsync.macports.org_release_ports_x11_xorg-libX11/work/ 
libX11-1.2.1" && ./configure --prefix=/Users/thomas/Documents/prgm/ 
bin/autoinstall/macports --without-xcb " returned error 1
Command output: checking if the linker (/usr/libexec/gcc/powerpc- 
apple-darwin8/4.0.1/ld) is GNU ld... no
checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/ 
powerpc-apple-darwin8/4.0.1/ld) supports shared libraries... yes
checking for /usr/bin/g++-4.0 option to produce PIC... -fno-common
checking if /usr/bin/g++-4.0 PIC flag -fno-common works... yes
checking if /usr/bin/g++-4.0 static flag -static works... no
checking if /usr/bin/g++-4.0 supports -c -o file.o... yes
checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/ 
powerpc-apple-darwin8/4.0.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin8.11.0 dyld
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for bash... /bin/bash
checking if dolt supports this host... no, falling back to libtool
checking for gcc... (cached) /usr/bin/gcc-4.0
checking whether we are using the GNU C compiler... (cached) yes
checking whether /usr/bin/gcc-4.0 accepts -g... (cached) yes
checking for /usr/bin/gcc-4.0 option to accept ISO C89... (cached)  
none needed
checking dependency style of /usr/bin/gcc-4.0... (cached) gcc3
checking for cpp... /usr/bin/cpp
checking if /usr/bin/cpp requires -undef... no
checking if /usr/bin/cpp requires -traditional... no
checking whether to use XCB... (cached) no
checking for pkg-config... /Users/thomas/Documents/prgm/bin/ 
autoinstall/macports/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for XPROTO... configure: error: Package requirements (xproto  
 >= 7.0.13) were not met.
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively you may set the XPROTO_CFLAGS and XPROTO_LIBS  
environment variables
to avoid the need to call pkg-config.  See the pkg-config man page for
more details.


and it built fine just after it upgraded xorg-xproto (continuing port  
-u upgrade outdated)

and then :


--->  Configuring xorg-libXrandr
Error: Target org.macports.configure returned: configure failure:  
shell command " cd "/Users/thomas/Documents/prgm/bin/autoinstall/ 
macports/var/macports/build/ 
_Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sourc 
es_rsync.macports.org_release_ports_x11_xorg-libXrandr/work/ 
libXrandr-1.3.0" && ./configure --prefix=/Users/thomas/Documents/prgm/ 
bin/autoinstall/macports " returned error 1
Command output: checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if /usr/bin/gcc-4.0 supports -fno-rtti -fno-exceptions... no
checking for /usr/bin/gcc-4.0 option to produce PIC... -fno-common -DPIC
checking if /usr/bin/gcc-4.0 PIC flag -fno-common -DPIC works... yes
checking if /usr/bin/gcc-4.0 static flag -static works... no
checking if /usr/bin/gcc-4.0 supports -c -o file.o... yes
checking if /usr/bin/gcc-4.0 supports -c -o file.o... (cached) yes
checking whether the /usr/bin/gcc-4.0 linker (/usr/libexec/gcc/ 
powerpc-apple-darwin8/4.0.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin8.11.0 dyld
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for pkg-config... /Users/thomas/Documents/prgm/bin/ 
autoinstall/macports/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for RANDR... configure: error: Package requirements (x11  
randrproto >= 1.3 xext xextproto xrender renderproto) were not met:

No package 'renderproto' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables RANDR_CFLAGS
and RANDR_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


after doing
port deactivate render
and redo
port -u upgrade outdated

it activates xorg-renderproto (right)
it upgrades xrender
and it builds xorg-libXrandr fine


well, seeing the end of the errors, it may be a problem with pkgconfig,
and regarding on how to get them around, it may be a problem about  
dependencies

what do you think about it ?


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Fri Jun 12 17:51:08 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Sat, 13 Jun 2009 02:51:08 +0200
Subject: port -u upgrade outdated
Message-ID: <CABC9566-FB1D-4F99-BF14-AB6681D0785B@free.fr>

hi :-)


when we use "port upgrade outdated" to upgrade, it leaves a lot of  
inactive ports behind it

after that, when we use "port -u upgrade outdated",
it uninstalls only the one which was active and deactivated, not all  
inactives versions of the same port


why ?
is there a good reason ?


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From ryandesign at macports.org  Sat Jun 13 00:26:26 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sat, 13 Jun 2009 02:26:26 -0500
Subject: port -u upgrade outdated
In-Reply-To: <CABC9566-FB1D-4F99-BF14-AB6681D0785B@free.fr>
References: <CABC9566-FB1D-4F99-BF14-AB6681D0785B@free.fr>
Message-ID: <C75A8C54-48D5-43C8-AA8D-CC0E7ADC8E80@macports.org>


On Jun 12, 2009, at 19:51, Thomas De Contes wrote:

> when we use "port upgrade outdated" to upgrade, it leaves a lot of  
> inactive ports behind it
>
> after that, when we use "port -u upgrade outdated",
> it uninstalls only the one which was active and deactivated, not  
> all inactives versions of the same port
>
>
> why ?
> is there a good reason ?

I believe this has already been fixed on trunk and will be in  
MacPorts 1.8.0.




From krischik at macports.org  Sat Jun 13 03:54:12 2009
From: krischik at macports.org (Martin Krischik)
Date: Sat, 13 Jun 2009 12:54:12 +0200
Subject: port install gnat-gcc
In-Reply-To: <E5413A52-CE7B-4FE7-86A8-2AC7523F91AB@free.fr>
References: <C030B322-9742-4589-A259-D185CB3B713B@free.fr>
	<4A326895.4050709@users.sourceforge.net>
	<E5413A52-CE7B-4FE7-86A8-2AC7523F91AB@free.fr>
Message-ID: <4A338554.4040602@macports.org>

Hello Thomas

Am 12.06.2009 um 18:49 schrieb Thomas De Contes:

>
> Le 12 juin 09 ? 16:39, Martin Krischik a ?crit :
>
>> Thomas De Contes schrieb:
>>> i have some problems with
>>> port install gnat-gcc
>>
>> This error description is to short so I can't help you ;-).
>
> i described my problem on discussion lists :-)

Strange  - I can't find it. And Apple-Mail has a very reliable search
function - unlike the competition spotlight actually works.

>
>> Note that
>> GNAT GPL 2009 is out and it does support Max OSX as well.
>
> i don't know this software,
http://libre.adacore.com/libre/

That is strange as it is one of the three the offical releases of GNAT:
GNAT GPL (the free beer version), GNAT GAP (the accademic version) and
GNAT PRO (the fully supported version).

Beginners should consider GNAT GPL - gnat-gcc in MacPorts is more for
advaned users. Also GNAT GPL 2009 now comes with an 64 bit compiler.
That is pretty cool.

> for yet, i want only to update gnat

There is only one version if GNAT for MacPorts so there is nothing to
update. I am working on the 4.4 version but project manager can't create
library yet - and I won't commit until that works. So why update if
there is nothing to update to?

Martin

-- 
Martin Krischik
mailto://krischik at macports.org
http://trac.macports.org/wiki/krischik


From ryandesign at macports.org  Sat Jun 13 04:17:48 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sat, 13 Jun 2009 06:17:48 -0500
Subject: port -u upgrade outdated
In-Reply-To: <C75A8C54-48D5-43C8-AA8D-CC0E7ADC8E80@macports.org>
References: <CABC9566-FB1D-4F99-BF14-AB6681D0785B@free.fr>
	<C75A8C54-48D5-43C8-AA8D-CC0E7ADC8E80@macports.org>
Message-ID: <CE44CB8F-5C40-45A8-9EE8-BAD8F698F653@macports.org>


On Jun 13, 2009, at 02:26, Ryan Schmidt wrote:

> On Jun 12, 2009, at 19:51, Thomas De Contes wrote:
>
>> when we use "port upgrade outdated" to upgrade, it leaves a lot of  
>> inactive ports behind it
>>
>> after that, when we use "port -u upgrade outdated",
>> it uninstalls only the one which was active and deactivated, not  
>> all inactives versions of the same port
>>
>>
>> why ?
>> is there a good reason ?
>
> I believe this has already been fixed on trunk and will be in  
> MacPorts 1.8.0.

This is the change I was thinking of:

http://trac.macports.org/changeset/47781



From d.l.tDeContes at free.fr  Sat Jun 13 05:02:51 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Sat, 13 Jun 2009 14:02:51 +0200
Subject: dbus
Message-ID: <F9D8A859-E3BD-4AD6-91CD-DB4EC0CDCC7D@free.fr>

hi :-)


--->  Installing dbus @1.2.12_5
Error: Target org.macports.activate returned: <main> attribute  
status: eDSPermissionError

what's the problem ?


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From raimue at macports.org  Sat Jun 13 06:17:46 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Sat, 13 Jun 2009 15:17:46 +0200
Subject: port -u upgrade outdated
In-Reply-To: <CABC9566-FB1D-4F99-BF14-AB6681D0785B@free.fr>
References: <CABC9566-FB1D-4F99-BF14-AB6681D0785B@free.fr>
Message-ID: <4A33A6FA.10707@macports.org>

On 2009-06-13 02:51, Thomas De Contes wrote:
> when we use "port upgrade outdated" to upgrade, it leaves a lot of  
> inactive ports behind it
> 
> after that, when we use "port -u upgrade outdated",
> it uninstalls only the one which was active and deactivated, not all  
> inactives versions of the same port

As a workaround you can use
  sudo port uninstall inactive
to get rid of all inactive versions.

Rainer

From face at CentosPrime.COM  Sat Jun 13 10:34:48 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sat, 13 Jun 2009 10:34:48 -0700
Subject: apr-util dependencies
Message-ID: <E8A95942-23EB-44C8-A170-041832668140@centosprime.com>

Every time apr-util is upgraded it winds up trying to install mysql5  
on my system

from apr-util Portfile

variant mysql5	description {Build with MySQL5 suppoprt} {
		depends_lib-append port:mysql5
		configure.args-delete --without-mysql
		configure.args-append --with-mysql=yes
		configure.env-append MYSQL_CONFIG=${prefix}/bin/mysql_config5
		}

from php5 Portfile

variant mysql5 conflicts mysql3 mysql4 description {build MySQL 5  
support} {
     depends_lib-append \
         path:bin/mysql_config5:mysql5

I'm actually using mysql5-devel, so I don't need a fresh install of  
mysql5 ;-)

Is it simply a matter of changing the

	depends_lib-append port:mysql5

to

	depends_lib-append path:bin/mysql_config5:mysql5

so it will recognize that I already have mysql5 installed?

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From nox at macports.org  Sat Jun 13 12:04:45 2009
From: nox at macports.org (nox)
Date: Sat, 13 Jun 2009 21:04:45 +0200
Subject: --enable-gnome not selected on dia Port
In-Reply-To: <6a819a10905302024u7dfca267k45112eb4a570248e@mail.gmail.com>
References: <6a819a10905302024u7dfca267k45112eb4a570248e@mail.gmail.com>
Message-ID: <8EC1A4F3-C7EC-45C2-825A-287E11046C85@macports.org>

Le 31 mai 09 ? 05:24, Charles A. Templeton III a ?crit :

> Dia is installed with the gnome +office variant. But if you look at  
> the configure args --enable-gnome isn't passed to configure. Does  
> anybody know if there is a reason for this?
>
> -Charles III
>

I'm the maintainer of the dia port. I haven't enabled GNOME support  
because it pulls in other dependencies.
Which features does GNOME support enable?

Regards,
Anthony.


From mailinglists at cserb.net  Sat Jun 13 12:46:41 2009
From: mailinglists at cserb.net (Cristian Serb)
Date: Sat, 13 Jun 2009 21:46:41 +0200
Subject: Trac and Python -> Bus Error
Message-ID: <BC55D640-81E3-4184-BD88-E553540E420A@cserb.net>

Hi,

I installed Trac and after setting it up I start the server with:  
tracd -s --port 8000 ./
Then I try to open the page in safari. It looks like text is loading  
but every time it tries to load pictures I get a "Bus Error". I'm not  
sure if this is really related to the pictures.
Any idea why this happens? Might this be related to the packages  
installed by  MacPorts or should I rather ask the Trac guys?

Many thanks,
Cristian



Process:         Python [972]
Path:            /opt/local/Library/Frameworks/Python.framework/ 
Versions/2.6/Resources/Python.app/Contents/MacOS/Python
Identifier:      Python
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  bash [921]

Interval Since Last Report:          297 sec
Crashes Since Last Report:           4
Per-App Interval Since Last Report:  0 sec
Per-App Crashes Since Last Report:   4

Date/Time:       2009-06-13 21:38:50.707 +0200
OS Version:      Mac OS X 10.5.7 (9J61)
Report Version:  6
Anonymous UUID:  478BC0E7-CF1C-4E8D-B47A-FEE7B058626D

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000b0000ffc
Crashed Thread:  1

Thread 0:
0   libSystem.B.dylib             	0x939be6fa select$DARWIN_EXTSN + 10
1   org.python.python             	0x0029209c PyEval_EvalFrameEx + 19212
2   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
3   org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
4   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
5   org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
6   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
7   org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
8   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
9   org.python.python             	0x00294067 PyEval_EvalCode + 87
10  org.python.python             	0x002b8ac8 PyRun_FileExFlags + 168
11  org.python.python             	0x002b99b3 PyRun_SimpleFileExFlags  
+ 867
12  org.python.python             	0x002cb45a Py_Main + 3130
13  org.python.python             	0x00001fb6 0x1000 + 4022

Thread 1 Crashed:
0   org.python.python             	0x002252d2 lookdict_string + 18
1   org.python.python             	0x00291493 PyEval_EvalFrameEx + 16131
2   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
3   org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
4   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
5   org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
6   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
7   org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
8   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
9   org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
10  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
11  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
12  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
13  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
14  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
15  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
16  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
17  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
18  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
19  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
20  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
21  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
22  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
23  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
24  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
25  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
26  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
27  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
28  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
29  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
30  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
31  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
32  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
33  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
34  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
35  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
36  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
37  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
38  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
39  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
40  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
41  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
42  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
43  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
44  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
45  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
46  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
47  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
48  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
49  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
50  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
51  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
52  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
53  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
54  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
55  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
56  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
57  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
58  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
59  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
60  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
61  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
62  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
63  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
64  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
65  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
66  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
67  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
68  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
69  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
70  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
71  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
72  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
73  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
74  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
75  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
76  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
77  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
78  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
79  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
80  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
81  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
82  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
83  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
84  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
85  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
86  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
87  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
88  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
89  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
90  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
91  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
92  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
93  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
94  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
95  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
96  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
97  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
98  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
99  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
100 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
101 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
102 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
103 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
104 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
105 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
106 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
107 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
108 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
109 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
110 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
111 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
112 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
113 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
114 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
115 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
116 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
117 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
118 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
119 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
120 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
121 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
122 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
123 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
124 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
125 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
126 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
127 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
128 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
129 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
130 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
131 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
132 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
133 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
134 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
135 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
136 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
137 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
138 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
139 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
140 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
141 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
142 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
143 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
144 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
145 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
146 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
147 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
148 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
149 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
150 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
151 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
152 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
153 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
154 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
155 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
156 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
157 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
158 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
159 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
160 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
161 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
162 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
163 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
164 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
165 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
166 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
167 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
168 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
169 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
170 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
171 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
172 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
173 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
174 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
175 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
176 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
177 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
178 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
179 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
180 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
181 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
182 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
183 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
184 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
185 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
186 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
187 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
188 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
189 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
190 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
191 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
192 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
193 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
194 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
195 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
196 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
197 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
198 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
199 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
200 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
201 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
202 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
203 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
204 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
205 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
206 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
207 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
208 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
209 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
210 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
211 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
212 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
213 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
214 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
215 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
216 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
217 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
218 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
219 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
220 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
221 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
222 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
223 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
224 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
225 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
226 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
227 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
228 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
229 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
230 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
231 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
232 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
233 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
234 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
235 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
236 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
237 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
238 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
239 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
240 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
241 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
242 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
243 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
244 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
245 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
246 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
247 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
248 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
249 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
250 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
251 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
252 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
253 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
254 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
255 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
256 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
257 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
258 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
259 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
260 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
261 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
262 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
263 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
264 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
265 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
266 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
267 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
268 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
269 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
270 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
271 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
272 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
273 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
274 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
275 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
276 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
277 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
278 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
279 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
280 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
281 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
282 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
283 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
284 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
285 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
286 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
287 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
288 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
289 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
290 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
291 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
292 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
293 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
294 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
295 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
296 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
297 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
298 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
299 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
300 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
301 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
302 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
303 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
304 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
305 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
306 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
307 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
308 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
309 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
310 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
311 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
312 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
313 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
314 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
315 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
316 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
317 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
318 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
319 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
320 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
321 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
322 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
323 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
324 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
325 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
326 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
327 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
328 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
329 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
330 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
331 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
332 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
333 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
334 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
335 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
336 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
337 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
338 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
339 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
340 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
341 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
342 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
343 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
344 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
345 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
346 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
347 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
348 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
349 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
350 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
351 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
352 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
353 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
354 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
355 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
356 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
357 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
358 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
359 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
360 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
361 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
362 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
363 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
364 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
365 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
366 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
367 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
368 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
369 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
370 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
371 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
372 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
373 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
374 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
375 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
376 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
377 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
378 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
379 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
380 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
381 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
382 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
383 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
384 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
385 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
386 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
387 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
388 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
389 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
390 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
391 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
392 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
393 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
394 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
395 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
396 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
397 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
398 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
399 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
400 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
401 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
402 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
403 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
404 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
405 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
406 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
407 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
408 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
409 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
410 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
411 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
412 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
413 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
414 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
415 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
416 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
417 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
418 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
419 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
420 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
421 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
422 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
423 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
424 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
425 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
426 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
427 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
428 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
429 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
430 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
431 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
432 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
433 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
434 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
435 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
436 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
437 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
438 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
439 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
440 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
441 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
442 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
443 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
444 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
445 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
446 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
447 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
448 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
449 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
450 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
451 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
452 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
453 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
454 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
455 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
456 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
457 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
458 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
459 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
460 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
461 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
462 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
463 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
464 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
465 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
466 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
467 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
468 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
469 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
470 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
471 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
472 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
473 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
474 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
475 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
476 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
477 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
478 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
479 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
480 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
481 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
482 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
483 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
484 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
485 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
486 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
487 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
488 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
489 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
490 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
491 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
492 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
493 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
494 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
495 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
496 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
497 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
498 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
499 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
500 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
501 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
502 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
503 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
504 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
505 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
506 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
507 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
508 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
509 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
510 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
511 org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558

Thread 2:
0   libSystem.B.dylib             	0x9397646e __semwait_signal + 10
1   libSystem.B.dylib             	0x939a0dcd pthread_cond_wait 
$UNIX2003 + 73
2   org.python.python             	0x002c856c PyThread_acquire_lock +  
172
3   org.python.python             	0x0028e099 PyEval_EvalFrameEx + 2825
4   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
5   org.python.python             	0x00212206 function_call + 166
6   org.python.python             	0x001e1a25 PyObject_Call + 85
7   org.python.python             	0x001f3806 instancemethod_call + 422
8   org.python.python             	0x001e1a25 PyObject_Call + 85
9   org.python.python             	0x0028c5ce  
PyEval_CallObjectWithKeywords + 78
10  org.python.python             	0x001f66d2 PyInstance_New + 114
11  org.python.python             	0x001e1a25 PyObject_Call + 85
12  org.python.python             	0x00290abe PyEval_EvalFrameEx + 13614
13  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
14  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
15  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
16  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
17  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
18  org.python.python             	0x00212206 function_call + 166
19  org.python.python             	0x001e1a25 PyObject_Call + 85
20  org.python.python             	0x001f3806 instancemethod_call + 422
21  org.python.python             	0x001e1a25 PyObject_Call + 85
22  org.python.python             	0x00247a67 slot_tp_init + 87
23  org.python.python             	0x00246490 type_call + 176
24  org.python.python             	0x001e1a25 PyObject_Call + 85
25  org.python.python             	0x00290abe PyEval_EvalFrameEx + 13614
26  org.python.python             	0x002055c7 gen_send_ex + 135
27  org.python.python             	0x0021acc9 listextend + 553
28  org.python.python             	0x0021b10d list_init + 237
29  org.python.python             	0x00246490 type_call + 176
30  org.python.python             	0x001e1a25 PyObject_Call + 85
31  org.python.python             	0x00290abe PyEval_EvalFrameEx + 13614
32  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
33  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
34  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
35  org.python.python             	0x00212206 function_call + 166
36  org.python.python             	0x001e1a25 PyObject_Call + 85
37  org.python.python             	0x001f3806 instancemethod_call + 422
38  org.python.python             	0x001e1a25 PyObject_Call + 85
39  org.python.python             	0x00247a67 slot_tp_init + 87
40  org.python.python             	0x00246490 type_call + 176
41  org.python.python             	0x001e1a25 PyObject_Call + 85
42  org.python.python             	0x00290abe PyEval_EvalFrameEx + 13614
43  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
44  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
45  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
46  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
47  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
48  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
49  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
50  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
51  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
52  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
53  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
54  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
55  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
56  org.python.python             	0x00212206 function_call + 166
57  org.python.python             	0x001e1a25 PyObject_Call + 85
58  org.python.python             	0x001f3806 instancemethod_call + 422
59  org.python.python             	0x001e1a25 PyObject_Call + 85
60  org.python.python             	0x00247e37 slot_tp_call + 71
61  org.python.python             	0x001e1a25 PyObject_Call + 85
62  org.python.python             	0x00290abe PyEval_EvalFrameEx + 13614
63  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
64  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
65  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
66  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
67  org.python.python             	0x00212206 function_call + 166
68  org.python.python             	0x001e1a25 PyObject_Call + 85
69  org.python.python             	0x001f3806 instancemethod_call + 422
70  org.python.python             	0x001e1a25 PyObject_Call + 85
71  org.python.python             	0x0028c5ce  
PyEval_CallObjectWithKeywords + 78
72  org.python.python             	0x001f66d2 PyInstance_New + 114
73  org.python.python             	0x001e1a25 PyObject_Call + 85
74  org.python.python             	0x00290abe PyEval_EvalFrameEx + 13614
75  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
76  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
77  org.python.python             	0x00212206 function_call + 166
78  org.python.python             	0x001e1a25 PyObject_Call + 85
79  org.python.python             	0x0028ff21 PyEval_EvalFrameEx + 10641
80  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
81  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
82  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
83  org.python.python             	0x00212206 function_call + 166
84  org.python.python             	0x001e1a25 PyObject_Call + 85
85  org.python.python             	0x001f3806 instancemethod_call + 422
86  org.python.python             	0x001e1a25 PyObject_Call + 85
87  org.python.python             	0x0028c5ce  
PyEval_CallObjectWithKeywords + 78
88  org.python.python             	0x002cd70f t_bootstrap + 63
89  libSystem.B.dylib             	0x939a0155 _pthread_start + 321
90  libSystem.B.dylib             	0x939a0012 thread_start + 34

Thread 3:
0   libSystem.B.dylib             	0x9397646e __semwait_signal + 10
1   libSystem.B.dylib             	0x939a0dcd pthread_cond_wait 
$UNIX2003 + 73
2   org.python.python             	0x002c856c PyThread_acquire_lock +  
172
3   org.python.python             	0x0028e099 PyEval_EvalFrameEx + 2825
4   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
5   org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
6   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
7   org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
8   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
9   org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
10  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
11  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
12  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
13  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
14  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
15  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
16  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
17  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
18  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
19  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
20  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
21  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
22  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
23  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
24  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
25  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
26  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
27  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
28  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
29  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
30  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
31  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
32  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
33  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
34  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
35  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
36  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
37  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
38  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
39  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
40  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
41  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
42  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
43  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
44  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
45  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
46  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
47  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
48  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
49  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
50  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
51  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
52  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
53  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
54  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
55  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
56  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
57  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
58  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
59  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
60  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
61  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
62  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
63  org.python.python             	0x00212206 function_call + 166
64  org.python.python             	0x001e1a25 PyObject_Call + 85
65  org.python.python             	0x001f3806 instancemethod_call + 422
66  org.python.python             	0x001e1a25 PyObject_Call + 85
67  org.python.python             	0x00247e37 slot_tp_call + 71
68  org.python.python             	0x001e1a25 PyObject_Call + 85
69  org.python.python             	0x00290abe PyEval_EvalFrameEx + 13614
70  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
71  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
72  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
73  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
74  org.python.python             	0x00212206 function_call + 166
75  org.python.python             	0x001e1a25 PyObject_Call + 85
76  org.python.python             	0x001f3806 instancemethod_call + 422
77  org.python.python             	0x001e1a25 PyObject_Call + 85
78  org.python.python             	0x0028c5ce  
PyEval_CallObjectWithKeywords + 78
79  org.python.python             	0x001f66d2 PyInstance_New + 114
80  org.python.python             	0x001e1a25 PyObject_Call + 85
81  org.python.python             	0x00290abe PyEval_EvalFrameEx + 13614
82  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
83  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
84  org.python.python             	0x00212206 function_call + 166
85  org.python.python             	0x001e1a25 PyObject_Call + 85
86  org.python.python             	0x0028ff21 PyEval_EvalFrameEx + 10641
87  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
88  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
89  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
90  org.python.python             	0x00212206 function_call + 166
91  org.python.python             	0x001e1a25 PyObject_Call + 85
92  org.python.python             	0x001f3806 instancemethod_call + 422
93  org.python.python             	0x001e1a25 PyObject_Call + 85
94  org.python.python             	0x0028c5ce  
PyEval_CallObjectWithKeywords + 78
95  org.python.python             	0x002cd70f t_bootstrap + 63
96  libSystem.B.dylib             	0x939a0155 _pthread_start + 321
97  libSystem.B.dylib             	0x939a0012 thread_start + 34

Thread 4:
0   libSystem.B.dylib             	0x9397646e __semwait_signal + 10
1   libSystem.B.dylib             	0x939a0dcd pthread_cond_wait 
$UNIX2003 + 73
2   org.python.python             	0x002c856c PyThread_acquire_lock +  
172
3   org.python.python             	0x0028c2f3 PyEval_RestoreThread + 67
4   org.python.python             	0x00206c63 get_line + 259
5   org.python.python             	0x00208e1c file_readline + 108
6   org.python.python             	0x0029209c PyEval_EvalFrameEx + 19212
7   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
8   org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
9   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
10  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
11  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
12  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
13  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
14  org.python.python             	0x002921f6 PyEval_EvalFrameEx + 19558
15  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
16  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
17  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
18  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
19  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
20  org.python.python             	0x00212206 function_call + 166
21  org.python.python             	0x001e1a25 PyObject_Call + 85
22  org.python.python             	0x001f3806 instancemethod_call + 422
23  org.python.python             	0x001e1a25 PyObject_Call + 85
24  org.python.python             	0x00247e37 slot_tp_call + 71
25  org.python.python             	0x001e1a25 PyObject_Call + 85
26  org.python.python             	0x00290abe PyEval_EvalFrameEx + 13614
27  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
28  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
29  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
30  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
31  org.python.python             	0x00212206 function_call + 166
32  org.python.python             	0x001e1a25 PyObject_Call + 85
33  org.python.python             	0x001f3806 instancemethod_call + 422
34  org.python.python             	0x001e1a25 PyObject_Call + 85
35  org.python.python             	0x0028c5ce  
PyEval_CallObjectWithKeywords + 78
36  org.python.python             	0x001f66d2 PyInstance_New + 114
37  org.python.python             	0x001e1a25 PyObject_Call + 85
38  org.python.python             	0x00290abe PyEval_EvalFrameEx + 13614
39  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
40  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
41  org.python.python             	0x00212206 function_call + 166
42  org.python.python             	0x001e1a25 PyObject_Call + 85
43  org.python.python             	0x0028ff21 PyEval_EvalFrameEx + 10641
44  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
45  org.python.python             	0x00292df9 PyEval_EvalFrameEx + 22633
46  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
47  org.python.python             	0x00212206 function_call + 166
48  org.python.python             	0x001e1a25 PyObject_Call + 85
49  org.python.python             	0x001f3806 instancemethod_call + 422
50  org.python.python             	0x001e1a25 PyObject_Call + 85
51  org.python.python             	0x0028c5ce  
PyEval_CallObjectWithKeywords + 78
52  org.python.python             	0x002cd70f t_bootstrap + 63
53  libSystem.B.dylib             	0x939a0155 _pthread_start + 321
54  libSystem.B.dylib             	0x939a0012 thread_start + 34

Thread 1 crashed with X86 Thread State (32-bit):
   eax: 0x0107e680  ebx: 0x0028d59b  ecx: 0xc7013ef7  edx: 0x010811e0
   edi: 0x016ef2b0  esi: 0xc7013ef7  ebp: 0xb0001048  esp: 0xb0001000
    ss: 0x0000001f  efl: 0x00010286  eip: 0x002252d2   cs: 0x00000017
    ds: 0x0000001f   es: 0x0000001f   fs: 0x0000001f   gs: 0x00000037
   cr2: 0xb0000ffc

Binary Images:
     0x1000 -     0x1ff8 +org.python.python 2.6.2 (2.6.2)  
<367715e0918b9027adecf6daa9c9c0b4> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python
    0x8e000 -    0x8fff5 +_locale.so ??? (???)  
<7ef9b91f44c9fdcd161b25b66dfc6043> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_locale.so
    0x94000 -    0x9bff3 +libintl.8.dylib ??? (???)  
<49bae84b06c07fc238d729e582c22694> /opt/local/lib/libintl.8.dylib
    0xba000 -    0xbbfff +time.so ??? (???)  
<b4df08b447c576d1d3ed44c7cff3c0eb> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/time.so
    0xc1000 -    0xc4ff9 +strop.so ??? (???)  
<b2d9a8bdc5769775f370e9fbf5a8e7a6> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/strop.so
   0x113000 -   0x11aff7 +_socket.so ??? (???)  
<6bf5330ff6a0351600ceed5b4bb18ace> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_socket.so
   0x123000 -   0x124fff +_random.so ??? (???)  
<0973aa42af1925a5907a5b4a06847401> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_random.so
   0x1d7000 -   0x2fefeb +org.python.python 2.6.2, (c) 2004-2008  
Python Software Foundation. (2.6.2)  
<744ac9a0c227b426812ec43bf65fa2a9> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/Python
   0x3ee000 -   0x3f1ff7 +_ssl.so ??? (???)  
<7e27f76cc0fdea2eb0f2d55b4e00c99d> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_ssl.so
   0x3f7000 -   0x3f8ff9 +cStringIO.so ??? (???)  
<58e93c29e736b9125720908b3966aefa> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/cStringIO.so
   0x600000 -   0x638feb +libssl.0.9.8.dylib ??? (???)  
<048da2db2c9a6df30b609d912e51d136> /opt/local/lib/libssl.0.9.8.dylib
   0x64c000 -   0x74efe7 +libcrypto.0.9.8.dylib ??? (???)  
<294465ec0f38141274d3f34f7fd28e72> /opt/local/lib/libcrypto.0.9.8.dylib
   0x7ac000 -   0x7bcffd +libz.1.dylib ??? (???)  
<a3bea29149481a5c9fd056566c80b4df> /opt/local/lib/libz.1.dylib
   0x7c1000 -   0x7c3fff +math.so ??? (???)  
<9359a4f723aad09ae871d802ac773000> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/math.so
   0x7c9000 -   0x7cbffa +binascii.so ??? (???)  
<ef0519e1b4ec1649e28e68282e5eece7> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/binascii.so
   0x7d0000 -   0x7d1ff0 +fcntl.so ??? (???)  
<72ddc90c1bf5c0acfd389f01a555bc05> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/fcntl.so
   0x7d5000 -   0x7d7fff +select.so ??? (???)  
<cc436a4ca34e37552d4f80bf216a3d54> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/select.so
   0x7dc000 -   0x7dcffc +_functools.so ??? (???)  
<ac084464c78f6e726eeb10a4770dcffc> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_functools.so
   0x7e0000 -   0x7e3ff3 +_collections.so ??? (???)  
<57ffefd49b96c09178156f8362b7851c> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_collections.so
   0x7e9000 -   0x7ecfff +operator.so ??? (???)  
<c63986aaac35569416805028a5b54242> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/operator.so
  0x1040000 -  0x104efff +cPickle.so ??? (???)  
<6896611538f2c5df6fdd88a57b7c2675> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/cPickle.so
  0x1056000 -  0x1059ff7 +_struct.so ??? (???)  
<cb30abbfff6792a1b8c6218f2a302c04> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_struct.so
  0x1060000 -  0x1060ff5 +_bisect.so ??? (???)  
<7dc80fbd952625e518d23916d581384c> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_bisect.so
  0x10a5000 -  0x10b1fff +datetime.so ??? (???)  
<43f21dd5c25911e6e00dde9dc7c2602a> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/datetime.so
  0x1168000 -  0x125fff0 +libiconv.2.dylib ??? (???)  
<3d3d7700af270c0ac25b5c30ca04e952> /opt/local/lib/libiconv.2.dylib
  0x126c000 -  0x1270ffe +itertools.so ??? (???)  
<94489dcda7de5db9bee12468c6be9d1a> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/itertools.so
  0x1279000 -  0x127aff5 +_hashlib.so ??? (???)  
<1c460b598de08c8ecf73fe464bc583ba> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_hashlib.so
  0x127f000 -  0x12adfe7 +pyexpat.so ??? (???)  
<7990f544f2de907fde877c99c09300f5> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/pyexpat.so
  0x133e000 -  0x134cffe +parser.so ??? (???)  
<e726ed3dde5de9af8c95c4a047408b1a> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/parser.so
  0x1399000 -  0x1399ff5 +_weakref.so ??? (???)  
<fc73ab3ae50b4f6432972b6e7b1aebe2> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_weakref.so
  0x139d000 -  0x139ffff +_multiprocessing.so ??? (???)  
<76068fbaed61f131616a40ae2217a965> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/ 
_multiprocessing.so
  0x13a5000 -  0x13a5ffa +libsvn_fs_util-1.0.dylib ??? (???)  
<a49fcc057649e29810650021911f6d4f> /opt/local/lib/ 
libsvn_fs_util-1.0.dylib
  0x156a000 -  0x156dfef +unicodedata.so ??? (???)  
<7beba7d8b827b0d1914d198e8660ac8c> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/unicodedata.so
  0x1700000 -  0x1702ff5 +_csv.so ??? (???)  
<0b0f6778f7cbf66ad699b67a7905716e> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_csv.so
  0x1708000 -  0x1709ff9 +_heapq.so ??? (???)  
<68e1903048d0ce6866ff42e034499aa4> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_heapq.so
  0x170e000 -  0x170fff6 +termios.so ??? (???)  
<0a51ed431f047cf8b022b474582bbfa6> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/termios.so
  0x17d8000 -  0x17e0fff +_sqlite3.so ??? (???)  
<07aae450ad98e3648209a53e3d9bdf6a> /opt/local/Library/Frameworks/ 
Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_sqlite3.so
  0x17eb000 -  0x184bfeb +libsqlite3.0.dylib ??? (???)  
<0d535262194ffad788aa7cc1b7af4c7c> /opt/local/lib/libsqlite3.0.dylib
  0x18ea000 -  0x1900ff3 +_fs.so ??? (???)  
<534edd5bb88032d0b74c5e686616a2fd> /opt/local/lib/svn-python2.6/libsvn/ 
_fs.so
  0x190d000 -  0x1916ffe +libsvn_swig_py26-1.0.dylib ??? (???)  
<60071292edee6b15ed8bd07c37ba3973> /opt/local/lib/ 
libsvn_swig_py26-1.0.dylib
  0x191d000 -  0x1951ff3 +libsvn_client-1.0.dylib ??? (???)  
<1a1edd2dfabda198ebcdb546b4d38db4> /opt/local/lib/ 
libsvn_client-1.0.dylib
  0x195d000 -  0x1995fff +libsvn_wc-1.0.dylib ??? (???)  
<22a68658c1cdb8b52ecb3a1e8a56fb8b> /opt/local/lib/libsvn_wc-1.0.dylib
  0x19a1000 -  0x19a9ff3 +libsvn_diff-1.0.dylib ??? (???)  
<34f9b940408ff97acbeb71dd74ca86c4> /opt/local/lib/libsvn_diff-1.0.dylib
  0x19ae000 -  0x19b3ff2 +libsvn_ra-1.0.dylib ??? (???)  
<b70163f74da3128d9eb0ae56a761a476> /opt/local/lib/libsvn_ra-1.0.dylib
  0x19b8000 -  0x19bbffe +libsvn_ra_local-1.0.dylib ??? (???)  
<721a6296510fe05d10c9a3dcd0c97014> /opt/local/lib/ 
libsvn_ra_local-1.0.dylib
  0x19c0000 -  0x19dfff3 +libsvn_repos-1.0.dylib ??? (???)  
<5fb8530ec65dd31520780187a5d44543> /opt/local/lib/libsvn_repos-1.0.dylib
  0x19e7000 -  0x19e9ff8 +libsvn_fs-1.0.dylib ??? (???)  
<4fea2da5392497b82785b5b9febac38e> /opt/local/lib/libsvn_fs-1.0.dylib
  0x19ee000 -  0x1a0affc +libsvn_fs_fs-1.0.dylib ??? (???)  
<c84cd7248b719ed847d512e92f33953d> /opt/local/lib/libsvn_fs_fs-1.0.dylib
  0x1a13000 -  0x1a33ffb +libsvn_fs_base-1.0.dylib ??? (???)  
<4a7492969c63d2ec0bd265f786c31129> /opt/local/lib/ 
libsvn_fs_base-1.0.dylib
  0x1a3d000 -  0x1b37fef +libdb-4.6.dylib ??? (???)  
<c38bbde94d43ef6c1592ddb2392521cc> /opt/local/lib/db46/libdb-4.6.dylib
  0x1b4c000 -  0x1b5bfff +libsvn_ra_svn-1.0.dylib ??? (???)  
<5859aee58d810feb97afca0d816598a5> /opt/local/lib/ 
libsvn_ra_svn-1.0.dylib
  0x1b62000 -  0x1b74ff3 +libsasl2.2.dylib ??? (???)  
<2b2b9d429b833b94972b46568307aa2c> /opt/local/lib/libsasl2.2.dylib
  0x1b7a000 -  0x1b91ff3 +libsvn_ra_neon-1.0.dylib ??? (???)  
<e77ff3693c54fa6c614f79c392b8045b> /opt/local/lib/ 
libsvn_ra_neon-1.0.dylib
  0x1b9a000 -  0x1bb1fff +libneon.27.dylib ??? (???)  
<f648ad7430e4152c0b7eafae24d87854> /opt/local/lib/libneon.27.dylib
  0x1bba000 -  0x1bd4fff +libsvn_ra_serf-1.0.dylib ??? (???)  
<1aa768029afa839db831eeae0e16ac9d> /opt/local/lib/ 
libsvn_ra_serf-1.0.dylib
  0x1bdd000 -  0x1be4ff9 +libserf-0.0.dylib ??? (???)  
<02969d31742a69f480404b73210de14f> /opt/local/lib/libserf-0.0.dylib
  0x1beb000 -  0x1bf2ff6 +libsvn_delta-1.0.dylib ??? (???)  
<1e863655a59c9bbbcda07229c9503003> /opt/local/lib/libsvn_delta-1.0.dylib
  0x1bf7000 -  0x1c2dfff +libsvn_subr-1.0.dylib ??? (???)  
<7bda66e5e09ba4347e9a6b977c09815a> /opt/local/lib/libsvn_subr-1.0.dylib
  0x1c3d000 -  0x1c51ff3 +libaprutil-1.0.dylib ??? (???)  
<8df1469df11db34d546ffdb359b67f31> /opt/local/lib/libaprutil-1.0.dylib
  0x1c5a000 -  0x1c76fe3 +libexpat.1.dylib ??? (???)  
<86bb4cce4c61a5db862ebfb991656809> /opt/local/lib/libexpat.1.dylib
  0x1c7e000 -  0x1c97fef +libapr-1.0.dylib ??? (???)  
<c3bb262cf2e00913bad332b9bae21564> /opt/local/lib/libapr-1.0.dylib
  0x1ca2000 -  0x1cabfe3  libpam.1.dylib ??? (???)  
<a504882e2e8a81210edd1ac438597e37> /usr/lib/libpam.1.dylib
  0x1cc3000 -  0x1cd6ff5 +_delta.so ??? (???)  
<36d25ae3e277e49b59e581476680b1ec> /opt/local/lib/svn-python2.6/libsvn/ 
_delta.so
  0x1d2f000 -  0x1d72ff3 +_core.so ??? (???)  
<75144aa0980fb2382d7f3cdfb56bbc68> /opt/local/lib/svn-python2.6/libsvn/ 
_core.so
  0x1e1d000 -  0x1e3fff2 +_repos.so ??? (???)  
<a2f3b0beb81a86b388decf2e1201d8dc> /opt/local/lib/svn-python2.6/libsvn/ 
_repos.so
0x8fe00000 - 0x8fe2db43  dyld 97.1 (???)  
<100d362e03410f181a34e04e94189ae5> /usr/lib/dyld
0x90499000 - 0x90525ff7  com.apple.LaunchServices 290.3 (290.6)  
<bdba267184df88bd5b8e2116ea903872> /System/Library/Frameworks/ 
CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/ 
Versions/A/LaunchServices
0x90526000 - 0x90800ff3  com.apple.CoreServices.CarbonCore 786.11  
(786.13) <9e2d85d52e5e2951aa4dd53c48ccc52f> /System/Library/Frameworks/ 
CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/ 
Versions/A/CarbonCore
0x91be5000 - 0x91d18fef  com.apple.CoreFoundation 6.5.6 (476.18)  
<2d52bab73660117571bd6486dc318f8e> /System/Library/Frameworks/ 
CoreFoundation.framework/Versions/A/CoreFoundation
0x91fbe000 - 0x92045ff7  libsqlite3.0.dylib ??? (???)  
<3334ea5af7a911637413334154bb4100> /usr/lib/libsqlite3.0.dylib
0x92046000 - 0x9205cfff  com.apple.DictionaryServices 1.0.0 (1.0.0)  
<7d20b8d1fb238c3e71d0fa6fda18c4f7> /System/Library/Frameworks/ 
CoreServices.framework/Versions/A/Frameworks/ 
DictionaryServices.framework/Versions/A/DictionaryServices
0x921a4000 - 0x92254fff  edu.mit.Kerberos 6.0.13 (6.0.13)  
<804bd1b3f08fb57396781f012006367c> /System/Library/Frameworks/ 
Kerberos.framework/Versions/A/Kerberos
0x92255000 - 0x9238eff7  libicucore.A.dylib ??? (???)  
<cac059ebdac7d9a63ee0f7a648c9f6cf> /usr/lib/libicucore.A.dylib
0x92395000 - 0x923b9fff  libxslt.1.dylib ??? (???)  
<0a9778d6368ae668826f446878deb99b> /usr/lib/libxslt.1.dylib
0x92480000 - 0x92480ffa  com.apple.CoreServices 32 (32)  
<373d6a888f9204641f313bc6070ae065> /System/Library/Frameworks/ 
CoreServices.framework/Versions/A/CoreServices
0x925b8000 - 0x925bfffe  libbsm.dylib ??? (???)  
<fa7ae5f1a621d9b69e7e18747c9405fb> /usr/lib/libbsm.dylib
0x92654000 - 0x9265cfff  com.apple.DiskArbitration 2.2.1 (2.2.1)  
<2664eeb3a4d0c95a21c089892a0ae8d0> /System/Library/Frameworks/ 
DiskArbitration.framework/Versions/A/DiskArbitration
0x92c2f000 - 0x92cbbff7  com.apple.framework.IOKit 1.5.2 (???)  
<97b9f9d584f48891377f0481b9104434> /System/Library/Frameworks/ 
IOKit.framework/Versions/A/IOKit
0x9332f000 - 0x9340ffff  libobjc.A.dylib ??? (???)  
<400e943f9e8a678eea22a1d1205490ee> /usr/lib/libobjc.A.dylib
0x93480000 - 0x9349efff  libresolv.9.dylib ??? (???)  
<9ed809256ce8913cddc3269c2e364654> /usr/lib/libresolv.9.dylib
0x9349f000 - 0x93580ff7  libxml2.2.dylib ??? (???)  
<2f6b294896866822330a8888b7f53b75> /usr/lib/libxml2.2.dylib
0x9396e000 - 0x93ad5ff3  libSystem.B.dylib ??? (???)  
<b47c8e6e45aef620730710a732bf1930> /usr/lib/libSystem.B.dylib
0x93b64000 - 0x93c1efe3  com.apple.CoreServices.OSServices 227 (227)  
<30cebcb68b1b571df7d77474e0c31556> /System/Library/Frameworks/ 
CoreServices.framework/Versions/A/Frameworks/OSServices.framework/ 
Versions/A/OSServices
0x93c1f000 - 0x93c4efe3  com.apple.AE 402.3 (402.3)  
<b13bfda0ad9314922ee37c0d018d7de9> /System/Library/Frameworks/ 
CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x9453b000 - 0x94549ffd  libz.1.dylib ??? (???)  
<a98b3b221a72b54faf73ded3dd7000e5> /usr/lib/libz.1.dylib
0x95891000 - 0x95935fec  com.apple.CFNetwork 438.10 (438.12)  
<fde64bbb20532794396fb21911ccaa98> /System/Library/Frameworks/ 
CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/ 
Versions/A/CFNetwork
0x959d2000 - 0x95a09fff  com.apple.SystemConfiguration 1.9.2 (1.9.2)  
<eab546255ac099b9616df999c9359d0e> /System/Library/Frameworks/ 
SystemConfiguration.framework/Versions/A/SystemConfiguration
0x95a0f000 - 0x95a3afe7  libauto.dylib ??? (???)  
<2e44c523b851e8e25f05d13a48070a58> /usr/lib/libauto.dylib
0x96b58000 - 0x96b5cfff  libmathCommon.A.dylib ??? (???) /usr/lib/ 
system/libmathCommon.A.dylib
0x96fc9000 - 0x97012fef  com.apple.Metadata 10.5.2 (398.25)  
<e0572f20350523116f23000676122a8d> /System/Library/Frameworks/ 
CoreServices.framework/Versions/A/Frameworks/Metadata.framework/ 
Versions/A/Metadata
0x970f9000 - 0x97156ffb  libstdc++.6.dylib ??? (???)  
<f75e5133d72769de5ce6c06153fc65f6> /usr/lib/libstdc++.6.dylib
0x97198000 - 0x9719ffe9  libgcc_s.1.dylib ??? (???)  
<e280ddf3f5fb3049e674edcb109f389a> /usr/lib/libgcc_s.1.dylib
0x97220000 - 0x9729fff5  com.apple.SearchKit 1.2.1 (1.2.1)  
<f28f8dd0f155a6453411a0c9b5702764> /System/Library/Frameworks/ 
CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/ 
Versions/A/SearchKit
0x972fc000 - 0x974cdffb  com.apple.security 5.0.5 (36371)  
<c13e0bb1acfdcf94be4d3ee118ef190e> /System/Library/Frameworks/ 
Security.framework/Versions/A/Security
0xfffe8000 - 0xfffebfff  libobjc.A.dylib ??? (???) /usr/lib/ 
libobjc.A.dylib
0xffff0000 - 0xffff1780  libSystem.B.dylib ??? (???) /usr/lib/ 
libSystem.B.dylib


From ryandesign at macports.org  Sat Jun 13 14:51:19 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sat, 13 Jun 2009 16:51:19 -0500
Subject: dbus
In-Reply-To: <F9D8A859-E3BD-4AD6-91CD-DB4EC0CDCC7D@free.fr>
References: <F9D8A859-E3BD-4AD6-91CD-DB4EC0CDCC7D@free.fr>
Message-ID: <D84A8471-F8BD-40E8-A313-5C4FE81D5978@macports.org>


On Jun 13, 2009, at 07:02, Thomas De Contes wrote:

> --->  Installing dbus @1.2.12_5
> Error: Target org.macports.activate returned: <main> attribute  
> status: eDSPermissionError
>
> what's the problem ?

I assume you're doing this in a non-root MacPorts installation. dbus  
wants to install a startupitem so you need to either use sudo to  
install it, or use the no_startupitem variant.


From frstan at bellsouth.net  Sat Jun 13 14:59:18 2009
From: frstan at bellsouth.net (William Davis)
Date: Sat, 13 Jun 2009 17:59:18 -0400
Subject: kdelibs4 checksum wrong
Message-ID: <2385045D-BF1A-4E7A-8762-4B71565C6A01@bellsouth.net>

as is new version kdelibs4 has wrong checksum.
substituted m5      9ed29086c33bc73256a7fa5268df560b  in portfile and  
it builds ok
the remaining kde upgrades need this fixed first to build or rather,  
to configure


William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090613/8a5baf42/attachment.html>

From jmr at macports.org  Sat Jun 13 16:33:35 2009
From: jmr at macports.org (Joshua Root)
Date: Sun, 14 Jun 2009 09:33:35 +1000
Subject: dbus
In-Reply-To: <D84A8471-F8BD-40E8-A313-5C4FE81D5978@macports.org>
References: <F9D8A859-E3BD-4AD6-91CD-DB4EC0CDCC7D@free.fr>
	<D84A8471-F8BD-40E8-A313-5C4FE81D5978@macports.org>
Message-ID: <4A34374F.9020607@macports.org>

On 2009-6-14 07:51, Ryan Schmidt wrote:
> 
> On Jun 13, 2009, at 07:02, Thomas De Contes wrote:
> 
>> --->  Installing dbus @1.2.12_5
>> Error: Target org.macports.activate returned: <main> attribute status:
>> eDSPermissionError
>>
>> what's the problem ?
> 
> I assume you're doing this in a non-root MacPorts installation. dbus
> wants to install a startupitem so you need to either use sudo to install
> it, or use the no_startupitem variant.

Or set 'startupitem_type none' in macports.conf, which will take care of
this for all ports.

- Josh

From d.l.tDeContes at free.fr  Sat Jun 13 16:43:53 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Sun, 14 Jun 2009 01:43:53 +0200
Subject: dbus
In-Reply-To: <D84A8471-F8BD-40E8-A313-5C4FE81D5978@macports.org>
References: <F9D8A859-E3BD-4AD6-91CD-DB4EC0CDCC7D@free.fr>
	<D84A8471-F8BD-40E8-A313-5C4FE81D5978@macports.org>
Message-ID: <22DF0311-111E-43EB-996F-2B8A518A4591@free.fr>


Le 13 juin 09 ? 23:51, Ryan Schmidt a ?crit :

>
> On Jun 13, 2009, at 07:02, Thomas De Contes wrote:
>
>> --->  Installing dbus @1.2.12_5
>> Error: Target org.macports.activate returned: <main> attribute  
>> status: eDSPermissionError
>>
>> what's the problem ?
>
> I assume you're doing this in a non-root MacPorts installation.

yes ;-)

> dbus wants to install a startupitem so you need to either use sudo  
> to install it, or use the no_startupitem variant.

thank you :-)

well, is it possible to make MacPorts to automatically switch to the  
appropriate variant, in a such case ?


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From ryandesign at macports.org  Sat Jun 13 17:20:09 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sat, 13 Jun 2009 19:20:09 -0500
Subject: dbus
In-Reply-To: <22DF0311-111E-43EB-996F-2B8A518A4591@free.fr>
References: <F9D8A859-E3BD-4AD6-91CD-DB4EC0CDCC7D@free.fr>
	<D84A8471-F8BD-40E8-A313-5C4FE81D5978@macports.org>
	<22DF0311-111E-43EB-996F-2B8A518A4591@free.fr>
Message-ID: <7AC8D49B-A86A-473E-8A4A-8E2DD3E95B28@macports.org>


On Jun 13, 2009, at 18:43, Thomas De Contes wrote:

>> dbus wants to install a startupitem so you need to either use sudo  
>> to install it, or use the no_startupitem variant.
>
> thank you :-)
>
> well, is it possible to make MacPorts to automatically switch to  
> the appropriate variant, in a such case ?

No, but if you are certain you never want any port to install a  
startup item, you can set the startup item type to none as Josh  
explained.



From d.l.tDeContes at free.fr  Sat Jun 13 17:20:52 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Sun, 14 Jun 2009 02:20:52 +0200
Subject: purge
Message-ID: <09BA39C3-895A-4F1D-BEF2-D4362D87EE9D@free.fr>

hi :-)


i think it would be very useful to be able to make a purging,

given that the user knows which ports he needs, but he doesn't  
control the dependencies



I propose:


a new state : "locked"

when the user installs a port, it becomes locked, but not its  
dependencies
when the user installs a port which is already installed, it locks it

locking wouldn't have effect on operations manually done by the  
user : if he wants to uninstall a port, it unlocks and uninstalls it


when the user makes a purging :

- it lists all locked ports
- it makes the tree of dependencies of this list
- it uninstalls ports which are not in this tree



the "locked" state represents the ports that the user knows and  
directly needs


it's usefull to remember the list of ports declared needed, and then  
say "oh, this one, i don't need it any more"
and then a purging uninstalls all dependencies of this port which are  
not used by an other port :-)


it can also be usefull in the case where :

a port A and a port B exist
C depends on A
then, the author of C finds that B is better, so C doesn't depend on  
A longer
but A still exists ...
then A isn't very usefull and waste space, entries, ... :-)



what do you think about this ? :-)


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From raimue at macports.org  Sat Jun 13 18:18:00 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Sun, 14 Jun 2009 03:18:00 +0200
Subject: purge
In-Reply-To: <09BA39C3-895A-4F1D-BEF2-D4362D87EE9D@free.fr>
References: <09BA39C3-895A-4F1D-BEF2-D4362D87EE9D@free.fr>
Message-ID: <4A344FC8.20005@macports.org>

On 2009-06-14 02:20, Thomas De Contes wrote:
> what do you think about this ? :-)

You want #15260 [1] to be implemented, which covers exactly what you
propose here.

Until that, you can use port_cutleaves [2] to identify and uninstall no
longer needed ports.

Rainer

[1] http://trac.macports.org/ticket/15260
[2] Available as port named port_cutleaves, see also
http://svn.macports.org/repository/macports/contrib/port_cutleaves/README

From jeremyhu at macports.org  Sat Jun 13 22:14:52 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Sat, 13 Jun 2009 22:14:52 -0700
Subject: pkgconfig / dependencies in xorg ?
In-Reply-To: <1E44991E-5203-4CA6-B47E-15A409EFC660@free.fr>
References: <1E44991E-5203-4CA6-B47E-15A409EFC660@free.fr>
Message-ID: <CCB3A7F3-16F0-4895-8871-4157181545EF@macports.org>

Well xorg-libX11 has depends_lib on xorg-xproto ... so it should be  
getting updated before xorg-libX11 ... what version of xorg-xproto do  
you have on your system?

On Jun 12, 2009, at 17:20, Thomas De Contes wrote:

> hi :-)
>
>
> here is what i get when i upgrade ports on a very old installation :
> port -u upgrade outdated
>
>
> --->  Configuring xorg-libX11
> Error: Target org.macports.configure returned: configure failure:  
> shell command " cd "/Users/thomas/Documents/prgm/bin/autoinstall/ 
> macports/var/macports/build/ 
> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync.macports.org_release_ports_x11_xorg 
> -libX11/work/libX11-1.2.1" && ./configure --prefix=/Users/thomas/ 
> Documents/prgm/bin/autoinstall/macports --without-xcb " returned  
> error 1
> Command output: checking if the linker (/usr/libexec/gcc/powerpc- 
> apple-darwin8/4.0.1/ld) is GNU ld... no
> checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/ 
> powerpc-apple-darwin8/4.0.1/ld) supports shared libraries... yes
> checking for /usr/bin/g++-4.0 option to produce PIC... -fno-common
> checking if /usr/bin/g++-4.0 PIC flag -fno-common works... yes
> checking if /usr/bin/g++-4.0 static flag -static works... no
> checking if /usr/bin/g++-4.0 supports -c -o file.o... yes
> checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/ 
> powerpc-apple-darwin8/4.0.1/ld) supports shared libraries... yes
> checking dynamic linker characteristics... darwin8.11.0 dyld
> checking how to hardcode library paths into programs... immediate
> appending configuration tag "F77" to libtool
> checking for bash... /bin/bash
> checking if dolt supports this host... no, falling back to libtool
> checking for gcc... (cached) /usr/bin/gcc-4.0
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether /usr/bin/gcc-4.0 accepts -g... (cached) yes
> checking for /usr/bin/gcc-4.0 option to accept ISO C89... (cached)  
> none needed
> checking dependency style of /usr/bin/gcc-4.0... (cached) gcc3
> checking for cpp... /usr/bin/cpp
> checking if /usr/bin/cpp requires -undef... no
> checking if /usr/bin/cpp requires -traditional... no
> checking whether to use XCB... (cached) no
> checking for pkg-config... /Users/thomas/Documents/prgm/bin/ 
> autoinstall/macports/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for XPROTO... configure: error: Package requirements  
> (xproto >= 7.0.13) were not met.
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively you may set the XPROTO_CFLAGS and XPROTO_LIBS  
> environment variables
> to avoid the need to call pkg-config.  See the pkg-config man page for
> more details.
>
>
> and it built fine just after it upgraded xorg-xproto (continuing  
> port -u upgrade outdated)
>
> and then :
>
>
> --->  Configuring xorg-libXrandr
> Error: Target org.macports.configure returned: configure failure:  
> shell command " cd "/Users/thomas/Documents/prgm/bin/autoinstall/ 
> macports/var/macports/build/ 
> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync.macports.org_release_ports_x11_xorg 
> -libXrandr/work/libXrandr-1.3.0" && ./configure --prefix=/Users/ 
> thomas/Documents/prgm/bin/autoinstall/macports " returned error 1
> Command output: checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking for objdir... .libs
> checking if /usr/bin/gcc-4.0 supports -fno-rtti -fno-exceptions... no
> checking for /usr/bin/gcc-4.0 option to produce PIC... -fno-common - 
> DPIC
> checking if /usr/bin/gcc-4.0 PIC flag -fno-common -DPIC works... yes
> checking if /usr/bin/gcc-4.0 static flag -static works... no
> checking if /usr/bin/gcc-4.0 supports -c -o file.o... yes
> checking if /usr/bin/gcc-4.0 supports -c -o file.o... (cached) yes
> checking whether the /usr/bin/gcc-4.0 linker (/usr/libexec/gcc/ 
> powerpc-apple-darwin8/4.0.1/ld) supports shared libraries... yes
> checking dynamic linker characteristics... darwin8.11.0 dyld
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> checking for pkg-config... /Users/thomas/Documents/prgm/bin/ 
> autoinstall/macports/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for RANDR... configure: error: Package requirements (x11  
> randrproto >= 1.3 xext xextproto xrender renderproto) were not met:
>
> No package 'renderproto' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables RANDR_CFLAGS
> and RANDR_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
>
> after doing
> port deactivate render
> and redo
> port -u upgrade outdated
>
> it activates xorg-renderproto (right)
> it upgrades xrender
> and it builds xorg-libXrandr fine
>
>
> well, seeing the end of the errors, it may be a problem with  
> pkgconfig,
> and regarding on how to get them around, it may be a problem about  
> dependencies
>
> what do you think about it ?
>
>
> -- 
> T?l?assistance / T?l?maintenance
> http://www.portparallele.com/ThomasDECONTES/
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From jeremyhu at macports.org  Sat Jun 13 22:18:16 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Sat, 13 Jun 2009 22:18:16 -0700
Subject: texlive_base @2007_7+nox11 upgrade problem
In-Reply-To: <CB0A1FB7-7A4C-41A2-B895-26D41BD7A4A2@tprfct.net>
References: <C3C770DA-F5D6-47BF-B23B-88BE49766C57@tprfct.net>
	<A59B4D9C-9C71-40FE-9EA7-D823D517E702@macports.org>
	<7661A3C8-BCC7-4EA0-BEAA-DA589F232A84@tprfct.net>
	<CB0A1FB7-7A4C-41A2-B895-26D41BD7A4A2@tprfct.net>
Message-ID: <F747244C-1A0A-470E-9FD1-8A7E95171E57@macports.org>

You want the "no_x11" variant... not the "nox11" variant...

On Jun 11, 2009, at 13:26, Kastus Shchuka wrote:

> On Jun 11, 2009, at 9:52 AM, Kastus Shchuka wrote:
>
>>
>> Should "lib:libXm:openmotif" be appended to line 89 of the port file?
>
> Sorry, I meant line 83, looked at the wrong place. And that is where  
> this string was in the previous revision r52043 (line 79 there).
>
> I am still puzzled what brings in openmotif as dependency while it  
> is not reported by port deps command. Do we need to explicitly  
> depends_lib-delete it in no_x11 variant?
>
> Thanks, -Kastus
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From d.l.tDeContes at free.fr  Sun Jun 14 07:08:21 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Sun, 14 Jun 2009 16:08:21 +0200
Subject: pkgconfig / dependencies in xorg ?
In-Reply-To: <CCB3A7F3-16F0-4895-8871-4157181545EF@macports.org>
References: <1E44991E-5203-4CA6-B47E-15A409EFC660@free.fr>
	<CCB3A7F3-16F0-4895-8871-4157181545EF@macports.org>
Message-ID: <895D03FF-4C6A-499C-AE88-AAF2A31BF502@free.fr>


Le 14 juin 09 ? 07:14, Jeremy Huddleston a ?crit :

> Well xorg-libX11 has depends_lib on xorg-xproto ... so it should be  
> getting updated before xorg-libX11 ... what version of xorg-xproto  
> do you have on your system?

xorg-xproto @7.0.15_0
but i don't see the report


>
> On Jun 12, 2009, at 17:20, Thomas De Contes wrote:
>
>> hi :-)
>>
>>
>> here is what i get when i upgrade ports on a very old installation :
>> port -u upgrade outdated
>>
>>
>> --->  Configuring xorg-libX11
>> Error: Target org.macports.configure returned: configure failure:  
>> shell command " cd "/Users/thomas/Documents/prgm/bin/autoinstall/ 
>> macports/var/macports/build/ 
>> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_so 
>> urces_rsync.macports.org_release_ports_x11_xorg-libX11/work/ 
>> libX11-1.2.1" && ./configure --prefix=/Users/thomas/Documents/prgm/ 
>> bin/autoinstall/macports --without-xcb " returned error 1
>> Command output: checking if the linker (/usr/libexec/gcc/powerpc- 
>> apple-darwin8/4.0.1/ld) is GNU ld... no
>> checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/ 
>> powerpc-apple-darwin8/4.0.1/ld) supports shared libraries... yes
>> checking for /usr/bin/g++-4.0 option to produce PIC... -fno-common
>> checking if /usr/bin/g++-4.0 PIC flag -fno-common works... yes
>> checking if /usr/bin/g++-4.0 static flag -static works... no
>> checking if /usr/bin/g++-4.0 supports -c -o file.o... yes
>> checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/ 
>> powerpc-apple-darwin8/4.0.1/ld) supports shared libraries... yes
>> checking dynamic linker characteristics... darwin8.11.0 dyld
>> checking how to hardcode library paths into programs... immediate
>> appending configuration tag "F77" to libtool
>> checking for bash... /bin/bash
>> checking if dolt supports this host... no, falling back to libtool
>> checking for gcc... (cached) /usr/bin/gcc-4.0
>> checking whether we are using the GNU C compiler... (cached) yes
>> checking whether /usr/bin/gcc-4.0 accepts -g... (cached) yes
>> checking for /usr/bin/gcc-4.0 option to accept ISO C89... (cached)  
>> none needed
>> checking dependency style of /usr/bin/gcc-4.0... (cached) gcc3
>> checking for cpp... /usr/bin/cpp
>> checking if /usr/bin/cpp requires -undef... no
>> checking if /usr/bin/cpp requires -traditional... no
>> checking whether to use XCB... (cached) no
>> checking for pkg-config... /Users/thomas/Documents/prgm/bin/ 
>> autoinstall/macports/bin/pkg-config
>> checking pkg-config is at least version 0.9.0... yes
>> checking for XPROTO... configure: error: Package requirements  
>> (xproto >= 7.0.13) were not met.
>> Consider adjusting the PKG_CONFIG_PATH environment variable if you
>> installed software in a non-standard prefix.
>>
>> Alternatively you may set the XPROTO_CFLAGS and XPROTO_LIBS  
>> environment variables
>> to avoid the need to call pkg-config.  See the pkg-config man page  
>> for
>> more details.
>>
>>
>> and it built fine just after it upgraded xorg-xproto (continuing  
>> port -u upgrade outdated)
>>
>> and then :
>>
>>
>> --->  Configuring xorg-libXrandr
>> Error: Target org.macports.configure returned: configure failure:  
>> shell command " cd "/Users/thomas/Documents/prgm/bin/autoinstall/ 
>> macports/var/macports/build/ 
>> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_so 
>> urces_rsync.macports.org_release_ports_x11_xorg-libXrandr/work/ 
>> libXrandr-1.3.0" && ./configure --prefix=/Users/thomas/Documents/ 
>> prgm/bin/autoinstall/macports " returned error 1
>> Command output: checking for stdint.h... yes
>> checking for unistd.h... yes
>> checking for dlfcn.h... yes
>> checking for objdir... .libs
>> checking if /usr/bin/gcc-4.0 supports -fno-rtti -fno-exceptions... no
>> checking for /usr/bin/gcc-4.0 option to produce PIC... -fno-common  
>> -DPIC
>> checking if /usr/bin/gcc-4.0 PIC flag -fno-common -DPIC works... yes
>> checking if /usr/bin/gcc-4.0 static flag -static works... no
>> checking if /usr/bin/gcc-4.0 supports -c -o file.o... yes
>> checking if /usr/bin/gcc-4.0 supports -c -o file.o... (cached) yes
>> checking whether the /usr/bin/gcc-4.0 linker (/usr/libexec/gcc/ 
>> powerpc-apple-darwin8/4.0.1/ld) supports shared libraries... yes
>> checking dynamic linker characteristics... darwin8.11.0 dyld
>> checking how to hardcode library paths into programs... immediate
>> checking whether stripping libraries is possible... yes
>> checking if libtool supports shared libraries... yes
>> checking whether to build shared libraries... yes
>> checking whether to build static libraries... yes
>> checking for pkg-config... /Users/thomas/Documents/prgm/bin/ 
>> autoinstall/macports/bin/pkg-config
>> checking pkg-config is at least version 0.9.0... yes
>> checking for RANDR... configure: error: Package requirements (x11  
>> randrproto >= 1.3 xext xextproto xrender renderproto) were not met:
>>
>> No package 'renderproto' found
>>
>> Consider adjusting the PKG_CONFIG_PATH environment variable if you
>> installed software in a non-standard prefix.
>>
>> Alternatively, you may set the environment variables RANDR_CFLAGS
>> and RANDR_LIBS to avoid the need to call pkg-config.
>> See the pkg-config man page for more details.
>>
>>
>> after doing
>> port deactivate render
>> and redo
>> port -u upgrade outdated
>>
>> it activates xorg-renderproto (right)
>> it upgrades xrender
>> and it builds xorg-libXrandr fine
>>
>>
>> well, seeing the end of the errors, it may be a problem with  
>> pkgconfig,
>> and regarding on how to get them around, it may be a problem about  
>> dependencies
>>
>> what do you think about it ?
>>
>>
>> -- 
>> T?l?assistance / T?l?maintenance
>> http://www.portparallele.com/ThomasDECONTES/
>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
>

-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Sun Jun 14 07:15:10 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Sun, 14 Jun 2009 16:15:10 +0200
Subject: purge
In-Reply-To: <4A344FC8.20005@macports.org>
References: <09BA39C3-895A-4F1D-BEF2-D4362D87EE9D@free.fr>
	<4A344FC8.20005@macports.org>
Message-ID: <5E61EA4A-73D6-4670-99C8-A2F91F96D6FE@free.fr>


Le 14 juin 09 ? 03:18, Rainer M?ller a ?crit :

> On 2009-06-14 02:20, Thomas De Contes wrote:
>> what do you think about this ? :-)
>
> You want #15260 [1] to be implemented, which covers exactly what you
> propose here.

very nice :-)))

do you know if this will be in MacPorts 1.8.0 ?
and when it will be available ?

>
> Until that, you can use port_cutleaves [2] to identify and  
> uninstall no
> longer needed ports.

it seems to be nice too :-)

but i get
+ port_cutleaves
Error: couldn't read file "/Library/Tcl/macports1.0/ 
macports_fastload.tcl": no such file or directory

my tcl directory is /Users/thomas/Documents/prgm/bin/autoinstall/ 
macports/tcl ,
and before that it was /Users/thomas/Library/Tcl

is it possible to correct that please ? :-)

>
> Rainer
>
> [1] http://trac.macports.org/ticket/15260
> [2] Available as port named port_cutleaves, see also
> http://svn.macports.org/repository/macports/contrib/port_cutleaves/ 
> README
>

-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Sun Jun 14 07:28:52 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Sun, 14 Jun 2009 16:28:52 +0200
Subject: port install subversion over subversion already installed
Message-ID: <F16768CF-09BC-4DF8-A78E-414F41E9EC1C@free.fr>

hi :-)


i get

+ port install subversion
--->  Installing subversion @1.6.2_0
Error: Target org.macports.install returned: Registry error:  
subversion @1.6.2_0 already registered as installed.  Please  
uninstall it first.
Error: Status 1 encountered during processing.
+ port install gtk2
Skipping org.macports.activate (gtk2 +darwin_8+x11) since this port  
is already active
--->  Cleaning gtk2

why does it make an error for subversion and then not for gtk2 ?


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From jmr at macports.org  Sun Jun 14 07:42:57 2009
From: jmr at macports.org (Joshua Root)
Date: Mon, 15 Jun 2009 00:42:57 +1000
Subject: port install subversion over subversion already installed
In-Reply-To: <F16768CF-09BC-4DF8-A78E-414F41E9EC1C@free.fr>
References: <F16768CF-09BC-4DF8-A78E-414F41E9EC1C@free.fr>
Message-ID: <4A350C71.1030208@macports.org>

On 2009-6-15 00:28, Thomas De Contes wrote:
> hi :-)
> 
> 
> i get
> 
> + port install subversion
> --->  Installing subversion @1.6.2_0
> Error: Target org.macports.install returned: Registry error: subversion
> @1.6.2_0 already registered as installed.  Please uninstall it first.
> Error: Status 1 encountered during processing.
> + port install gtk2
> Skipping org.macports.activate (gtk2 +darwin_8+x11) since this port is
> already active
> --->  Cleaning gtk2
> 
> why does it make an error for subversion and then not for gtk2 ?

Probably the strange logic that is used to check whether phases can be
skipped. If the Portfile has been changed since the port was installed
(even if the version/revision was not increased) then it will try to
install again instead of telling you that it's already installed. This
is fixed in trunk and will be in the 1.8 release.

- Josh

From jmr at macports.org  Sun Jun 14 07:49:23 2009
From: jmr at macports.org (Joshua Root)
Date: Mon, 15 Jun 2009 00:49:23 +1000
Subject: purge
In-Reply-To: <5E61EA4A-73D6-4670-99C8-A2F91F96D6FE@free.fr>
References: <09BA39C3-895A-4F1D-BEF2-D4362D87EE9D@free.fr>	<4A344FC8.20005@macports.org>
	<5E61EA4A-73D6-4670-99C8-A2F91F96D6FE@free.fr>
Message-ID: <4A350DF3.7010202@macports.org>

On 2009-6-15 00:15, Thomas De Contes wrote:
> 
> Le 14 juin 09 ? 03:18, Rainer M?ller a ?crit :
> 
>> On 2009-06-14 02:20, Thomas De Contes wrote:
>>> what do you think about this ? :-)
>>
>> You want #15260 [1] to be implemented, which covers exactly what you
>> propose here.
> 
> very nice :-)))
> 
> do you know if this will be in MacPorts 1.8.0 ?

No work has been done to implement it yet, so probably not.

> and when it will be available ?

1.8 will hopefully not be too much longer. We're not setting any
deadlines, since it's a small, completely volunteer effort.

>>
>> Until that, you can use port_cutleaves [2] to identify and uninstall no
>> longer needed ports.
> 
> it seems to be nice too :-)
> 
> but i get
> + port_cutleaves
> Error: couldn't read file
> "/Library/Tcl/macports1.0/macports_fastload.tcl": no such file or directory
> 
> my tcl directory is
> /Users/thomas/Documents/prgm/bin/autoinstall/macports/tcl ,
> and before that it was /Users/thomas/Library/Tcl
> 
> is it possible to correct that please ? :-)

>From the manual:

-t path
              Specify a different location for  the  base  MacPorts  Tcl
	      file </Library/Tcl>

- Josh

From d.l.tDeContes at free.fr  Sun Jun 14 07:56:44 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Sun, 14 Jun 2009 16:56:44 +0200
Subject: dbus
In-Reply-To: <7AC8D49B-A86A-473E-8A4A-8E2DD3E95B28@macports.org>
References: <F9D8A859-E3BD-4AD6-91CD-DB4EC0CDCC7D@free.fr>
	<D84A8471-F8BD-40E8-A313-5C4FE81D5978@macports.org>
	<22DF0311-111E-43EB-996F-2B8A518A4591@free.fr>
	<7AC8D49B-A86A-473E-8A4A-8E2DD3E95B28@macports.org>
Message-ID: <811D0B03-3894-4876-894F-3CB6177006C2@free.fr>


Le 14 juin 09 ? 02:20, Ryan Schmidt a ?crit :

>
> On Jun 13, 2009, at 18:43, Thomas De Contes wrote:
>
>>> dbus wants to install a startupitem so you need to either use  
>>> sudo to install it, or use the no_startupitem variant.
>>
>> thank you :-)
>>
>> well, is it possible to make MacPorts to automatically switch to  
>> the appropriate variant, in a such case ?
>
> No,

i was not spoking about "do it right now", but rather "is it possible  
to improve MacPorts, so it will be able to do it later"
possibly with adding an option to ./configure or to port command, to  
allow it to do so

still no ?


> but if you are certain you never want any port to install a startup  
> item, you can set the startup item type to none as Josh explained.

the problem is that i remove macports.conf in my script (see my last  
post in "python25")

it can't be set via ./configure, can it ?


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From macports at tprfct.net  Sun Jun 14 11:44:59 2009
From: macports at tprfct.net (Kastus Shchuka)
Date: Sun, 14 Jun 2009 11:44:59 -0700
Subject: texlive_base @2007_7+nox11 upgrade problem
In-Reply-To: <F747244C-1A0A-470E-9FD1-8A7E95171E57@macports.org>
References: <C3C770DA-F5D6-47BF-B23B-88BE49766C57@tprfct.net>
	<A59B4D9C-9C71-40FE-9EA7-D823D517E702@macports.org>
	<7661A3C8-BCC7-4EA0-BEAA-DA589F232A84@tprfct.net>
	<CB0A1FB7-7A4C-41A2-B895-26D41BD7A4A2@tprfct.net>
	<F747244C-1A0A-470E-9FD1-8A7E95171E57@macports.org>
Message-ID: <B05777BF-FAD1-4718-A649-BF6C4E3CB984@tprfct.net>


On Jun 13, 2009, at 10:18 PM, Jeremy Huddleston wrote:

> You want the "no_x11" variant... not the "nox11" variant...
>

Yes, this is what I want, no_x11, and I typed +no_x11 in command line.

Just for the record, the issue was solved by uninstalling my existing  
texlive_base which cleaned the registry.

Apparently, I tried and canceled an upgrade of texlive_base without   
any variant earlier which poisoned the registry and was bringing in  
openmotif no matter what variant I specified in later upgrade commands.

Thanks, -Kastus


From tarkawebfoot at charter.net  Sun Jun 14 13:00:24 2009
From: tarkawebfoot at charter.net (Brian Myers)
Date: Sun, 14 Jun 2009 13:00:24 -0700
Subject: macports-users Digest, Vol 34, Issue 10
In-Reply-To: <mailman.11.1244988001.18299.macports-users@lists.macosforge.org>
References: <mailman.11.1244988001.18299.macports-users@lists.macosforge.org>
Message-ID: <2B4739A4-2D7A-4CF4-8490-F92DC4EC2E32@charter.net>

Well his account is disabled on my site.

On Jun 14, 2009, at 7:00 AM, macports-users- 
request at lists.macosforge.org wrote:

> Send macports-users mailing list submissions to
> 	macports-users at lists.macosforge.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> or, via email, send a message with subject or body 'help' to
> 	macports-users-request at lists.macosforge.org
>
> You can reach the person managing the list at
> 	macports-users-owner at lists.macosforge.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of macports-users digest..."
>
>
> Today's Topics:
>
>   1. apr-util dependencies (Chris Janton)
>   2. Re: --enable-gnome not selected on dia Port (nox)
>   3. Trac and Python -> Bus Error (Cristian Serb)
>   4. Re: dbus (Ryan Schmidt)
>   5. kdelibs4 checksum wrong (William Davis)
>   6. Re: dbus (Joshua Root)
>   7. Re: dbus (Thomas De?Contes)
>   8. Re: dbus (Ryan Schmidt)
>   9. purge (Thomas De?Contes)
>  10. Re: purge (Rainer M?ller)
>  11. Re: pkgconfig / dependencies in xorg ? (Jeremy Huddleston)
>  12. Re: texlive_base @2007_7+nox11 upgrade problem (Jeremy  
> Huddleston)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 13 Jun 2009 10:34:48 -0700
> From: Chris Janton <face at CentosPrime.COM>
> To: MacPorts Users <macports-users at lists.macosforge.org>
> Subject: apr-util dependencies
> Message-ID: <E8A95942-23EB-44C8-A170-041832668140 at centosprime.com>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
> Every time apr-util is upgraded it winds up trying to install mysql5
> on my system
>
> from apr-util Portfile
>
> variant mysql5	description {Build with MySQL5 suppoprt} {
> 		depends_lib-append port:mysql5
> 		configure.args-delete --without-mysql
> 		configure.args-append --with-mysql=yes
> 		configure.env-append MYSQL_CONFIG=${prefix}/bin/mysql_config5
> 		}
>
> from php5 Portfile
>
> variant mysql5 conflicts mysql3 mysql4 description {build MySQL 5
> support} {
>     depends_lib-append \
>         path:bin/mysql_config5:mysql5
>
> I'm actually using mysql5-devel, so I don't need a fresh install of
> mysql5 ;-)
>
> Is it simply a matter of changing the
>
> 	depends_lib-append port:mysql5
>
> to
>
> 	depends_lib-append path:bin/mysql_config5:mysql5
>
> so it will recognize that I already have mysql5 installed?
>
> 8)
> ----------------------------------
> Chris Janton  - face at CentosPrime dot COM
> Netminder for Opus1.COM
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 13 Jun 2009 21:04:45 +0200
> From: nox <nox at macports.org>
> To: Charles A. Templeton III <ctempleton3 at gmail.com>
> Cc: macports-users at lists.macosforge.org
> Subject: Re: --enable-gnome not selected on dia Port
> Message-ID: <8EC1A4F3-C7EC-45C2-825A-287E11046C85 at macports.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
>
> Le 31 mai 09 ? 05:24, Charles A. Templeton III a ?crit :
>
>> Dia is installed with the gnome +office variant. But if you look at
>> the configure args --enable-gnome isn't passed to configure. Does
>> anybody know if there is a reason for this?
>>
>> -Charles III
>>
>
> I'm the maintainer of the dia port. I haven't enabled GNOME support
> because it pulls in other dependencies.
> Which features does GNOME support enable?
>
> Regards,
> Anthony.
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 13 Jun 2009 21:46:41 +0200
> From: Cristian Serb <mailinglists at cserb.net>
> To: macports-users at lists.macosforge.org
> Subject: Trac and Python -> Bus Error
> Message-ID: <BC55D640-81E3-4184-BD88-E553540E420A at cserb.net>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
> Hi,
>
> I installed Trac and after setting it up I start the server with:
> tracd -s --port 8000 ./
> Then I try to open the page in safari. It looks like text is loading
> but every time it tries to load pictures I get a "Bus Error". I'm not
> sure if this is really related to the pictures.
> Any idea why this happens? Might this be related to the packages
> installed by  MacPorts or should I rather ask the Trac guys?
>
> Many thanks,
> Cristian
>
>
>
> Process:         Python [972]
> Path:            /opt/local/Library/Frameworks/Python.framework/
> Versions/2.6/Resources/Python.app/Contents/MacOS/Python
> Identifier:      Python
> Version:         ??? (???)
> Code Type:       X86 (Native)
> Parent Process:  bash [921]
>
> Interval Since Last Report:          297 sec
> Crashes Since Last Report:           4
> Per-App Interval Since Last Report:  0 sec
> Per-App Crashes Since Last Report:   4
>
> Date/Time:       2009-06-13 21:38:50.707 +0200
> OS Version:      Mac OS X 10.5.7 (9J61)
> Report Version:  6
> Anonymous UUID:  478BC0E7-CF1C-4E8D-B47A-FEE7B058626D
>
> Exception Type:  EXC_BAD_ACCESS (SIGBUS)
> Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000b0000ffc
> Crashed Thread:  1
>
> Thread 0:
> 0   libSystem.B.dylib             	0x939be6fa select$DARWIN_EXTSN + 10
> 1   org.python.python             	0x0029209c PyEval_EvalFrameEx +  
> 19212
> 2   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 3   org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 4   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 5   org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 6   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 7   org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 8   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 9   org.python.python             	0x00294067 PyEval_EvalCode + 87
> 10  org.python.python             	0x002b8ac8 PyRun_FileExFlags + 168
> 11  org.python.python             	0x002b99b3 PyRun_SimpleFileExFlags
> + 867
> 12  org.python.python             	0x002cb45a Py_Main + 3130
> 13  org.python.python             	0x00001fb6 0x1000 + 4022
>
> Thread 1 Crashed:
> 0   org.python.python             	0x002252d2 lookdict_string + 18
> 1   org.python.python             	0x00291493 PyEval_EvalFrameEx +  
> 16131
> 2   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 3   org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 4   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 5   org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 6   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 7   org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 8   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 9   org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 10  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 11  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 12  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 13  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 14  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 15  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 16  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 17  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 18  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 19  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 20  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 21  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 22  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 23  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 24  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 25  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 26  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 27  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 28  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 29  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 30  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 31  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 32  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 33  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 34  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 35  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 36  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 37  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 38  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 39  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 40  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 41  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 42  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 43  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 44  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 45  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 46  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 47  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 48  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 49  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 50  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 51  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 52  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 53  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 54  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 55  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 56  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 57  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 58  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 59  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 60  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 61  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 62  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 63  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 64  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 65  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 66  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 67  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 68  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 69  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 70  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 71  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 72  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 73  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 74  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 75  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 76  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 77  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 78  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 79  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 80  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 81  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 82  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 83  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 84  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 85  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 86  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 87  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 88  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 89  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 90  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 91  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 92  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 93  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 94  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 95  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 96  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 97  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 98  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 99  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 100 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 101 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 102 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 103 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 104 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 105 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 106 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 107 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 108 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 109 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 110 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 111 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 112 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 113 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 114 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 115 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 116 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 117 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 118 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 119 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 120 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 121 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 122 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 123 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 124 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 125 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 126 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 127 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 128 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 129 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 130 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 131 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 132 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 133 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 134 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 135 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 136 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 137 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 138 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 139 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 140 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 141 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 142 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 143 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 144 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 145 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 146 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 147 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 148 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 149 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 150 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 151 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 152 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 153 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 154 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 155 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 156 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 157 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 158 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 159 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 160 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 161 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 162 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 163 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 164 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 165 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 166 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 167 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 168 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 169 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 170 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 171 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 172 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 173 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 174 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 175 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 176 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 177 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 178 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 179 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 180 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 181 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 182 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 183 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 184 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 185 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 186 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 187 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 188 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 189 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 190 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 191 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 192 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 193 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 194 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 195 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 196 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 197 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 198 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 199 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 200 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 201 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 202 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 203 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 204 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 205 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 206 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 207 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 208 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 209 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 210 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 211 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 212 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 213 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 214 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 215 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 216 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 217 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 218 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 219 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 220 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 221 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 222 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 223 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 224 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 225 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 226 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 227 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 228 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 229 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 230 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 231 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 232 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 233 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 234 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 235 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 236 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 237 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 238 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 239 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 240 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 241 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 242 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 243 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 244 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 245 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 246 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 247 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 248 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 249 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 250 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 251 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 252 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 253 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 254 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 255 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 256 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 257 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 258 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 259 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 260 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 261 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 262 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 263 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 264 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 265 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 266 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 267 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 268 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 269 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 270 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 271 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 272 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 273 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 274 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 275 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 276 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 277 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 278 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 279 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 280 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 281 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 282 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 283 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 284 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 285 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 286 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 287 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 288 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 289 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 290 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 291 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 292 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 293 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 294 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 295 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 296 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 297 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 298 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 299 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 300 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 301 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 302 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 303 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 304 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 305 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 306 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 307 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 308 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 309 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 310 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 311 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 312 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 313 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 314 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 315 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 316 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 317 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 318 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 319 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 320 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 321 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 322 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 323 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 324 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 325 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 326 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 327 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 328 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 329 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 330 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 331 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 332 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 333 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 334 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 335 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 336 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 337 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 338 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 339 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 340 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 341 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 342 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 343 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 344 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 345 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 346 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 347 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 348 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 349 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 350 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 351 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 352 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 353 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 354 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 355 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 356 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 357 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 358 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 359 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 360 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 361 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 362 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 363 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 364 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 365 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 366 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 367 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 368 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 369 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 370 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 371 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 372 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 373 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 374 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 375 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 376 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 377 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 378 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 379 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 380 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 381 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 382 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 383 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 384 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 385 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 386 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 387 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 388 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 389 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 390 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 391 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 392 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 393 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 394 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 395 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 396 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 397 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 398 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 399 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 400 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 401 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 402 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 403 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 404 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 405 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 406 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 407 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 408 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 409 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 410 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 411 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 412 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 413 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 414 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 415 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 416 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 417 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 418 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 419 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 420 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 421 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 422 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 423 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 424 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 425 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 426 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 427 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 428 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 429 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 430 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 431 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 432 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 433 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 434 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 435 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 436 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 437 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 438 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 439 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 440 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 441 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 442 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 443 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 444 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 445 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 446 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 447 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 448 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 449 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 450 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 451 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 452 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 453 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 454 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 455 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 456 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 457 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 458 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 459 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 460 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 461 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 462 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 463 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 464 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 465 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 466 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 467 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 468 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 469 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 470 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 471 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 472 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 473 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 474 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 475 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 476 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 477 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 478 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 479 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 480 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 481 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 482 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 483 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 484 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 485 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 486 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 487 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 488 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 489 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 490 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 491 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 492 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 493 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 494 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 495 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 496 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 497 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 498 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 499 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 500 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 501 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 502 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 503 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 504 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 505 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 506 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 507 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 508 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 509 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 510 org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 511 org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
>
> Thread 2:
> 0   libSystem.B.dylib             	0x9397646e __semwait_signal + 10
> 1   libSystem.B.dylib             	0x939a0dcd pthread_cond_wait
> $UNIX2003 + 73
> 2   org.python.python             	0x002c856c PyThread_acquire_lock +
> 172
> 3   org.python.python             	0x0028e099 PyEval_EvalFrameEx +  
> 2825
> 4   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 5   org.python.python             	0x00212206 function_call + 166
> 6   org.python.python             	0x001e1a25 PyObject_Call + 85
> 7   org.python.python             	0x001f3806 instancemethod_call +  
> 422
> 8   org.python.python             	0x001e1a25 PyObject_Call + 85
> 9   org.python.python             	0x0028c5ce
> PyEval_CallObjectWithKeywords + 78
> 10  org.python.python             	0x001f66d2 PyInstance_New + 114
> 11  org.python.python             	0x001e1a25 PyObject_Call + 85
> 12  org.python.python             	0x00290abe PyEval_EvalFrameEx +  
> 13614
> 13  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 14  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 15  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 16  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 17  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 18  org.python.python             	0x00212206 function_call + 166
> 19  org.python.python             	0x001e1a25 PyObject_Call + 85
> 20  org.python.python             	0x001f3806 instancemethod_call +  
> 422
> 21  org.python.python             	0x001e1a25 PyObject_Call + 85
> 22  org.python.python             	0x00247a67 slot_tp_init + 87
> 23  org.python.python             	0x00246490 type_call + 176
> 24  org.python.python             	0x001e1a25 PyObject_Call + 85
> 25  org.python.python             	0x00290abe PyEval_EvalFrameEx +  
> 13614
> 26  org.python.python             	0x002055c7 gen_send_ex + 135
> 27  org.python.python             	0x0021acc9 listextend + 553
> 28  org.python.python             	0x0021b10d list_init + 237
> 29  org.python.python             	0x00246490 type_call + 176
> 30  org.python.python             	0x001e1a25 PyObject_Call + 85
> 31  org.python.python             	0x00290abe PyEval_EvalFrameEx +  
> 13614
> 32  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 33  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 34  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 35  org.python.python             	0x00212206 function_call + 166
> 36  org.python.python             	0x001e1a25 PyObject_Call + 85
> 37  org.python.python             	0x001f3806 instancemethod_call +  
> 422
> 38  org.python.python             	0x001e1a25 PyObject_Call + 85
> 39  org.python.python             	0x00247a67 slot_tp_init + 87
> 40  org.python.python             	0x00246490 type_call + 176
> 41  org.python.python             	0x001e1a25 PyObject_Call + 85
> 42  org.python.python             	0x00290abe PyEval_EvalFrameEx +  
> 13614
> 43  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 44  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 45  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 46  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 47  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 48  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 49  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 50  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 51  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 52  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 53  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 54  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 55  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 56  org.python.python             	0x00212206 function_call + 166
> 57  org.python.python             	0x001e1a25 PyObject_Call + 85
> 58  org.python.python             	0x001f3806 instancemethod_call +  
> 422
> 59  org.python.python             	0x001e1a25 PyObject_Call + 85
> 60  org.python.python             	0x00247e37 slot_tp_call + 71
> 61  org.python.python             	0x001e1a25 PyObject_Call + 85
> 62  org.python.python             	0x00290abe PyEval_EvalFrameEx +  
> 13614
> 63  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 64  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 65  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 66  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 67  org.python.python             	0x00212206 function_call + 166
> 68  org.python.python             	0x001e1a25 PyObject_Call + 85
> 69  org.python.python             	0x001f3806 instancemethod_call +  
> 422
> 70  org.python.python             	0x001e1a25 PyObject_Call + 85
> 71  org.python.python             	0x0028c5ce
> PyEval_CallObjectWithKeywords + 78
> 72  org.python.python             	0x001f66d2 PyInstance_New + 114
> 73  org.python.python             	0x001e1a25 PyObject_Call + 85
> 74  org.python.python             	0x00290abe PyEval_EvalFrameEx +  
> 13614
> 75  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 76  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 77  org.python.python             	0x00212206 function_call + 166
> 78  org.python.python             	0x001e1a25 PyObject_Call + 85
> 79  org.python.python             	0x0028ff21 PyEval_EvalFrameEx +  
> 10641
> 80  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 81  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 82  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 83  org.python.python             	0x00212206 function_call + 166
> 84  org.python.python             	0x001e1a25 PyObject_Call + 85
> 85  org.python.python             	0x001f3806 instancemethod_call +  
> 422
> 86  org.python.python             	0x001e1a25 PyObject_Call + 85
> 87  org.python.python             	0x0028c5ce
> PyEval_CallObjectWithKeywords + 78
> 88  org.python.python             	0x002cd70f t_bootstrap + 63
> 89  libSystem.B.dylib             	0x939a0155 _pthread_start + 321
> 90  libSystem.B.dylib             	0x939a0012 thread_start + 34
>
> Thread 3:
> 0   libSystem.B.dylib             	0x9397646e __semwait_signal + 10
> 1   libSystem.B.dylib             	0x939a0dcd pthread_cond_wait
> $UNIX2003 + 73
> 2   org.python.python             	0x002c856c PyThread_acquire_lock +
> 172
> 3   org.python.python             	0x0028e099 PyEval_EvalFrameEx +  
> 2825
> 4   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 5   org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 6   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 7   org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 8   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 9   org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 10  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 11  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 12  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 13  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 14  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 15  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 16  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 17  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 18  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 19  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 20  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 21  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 22  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 23  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 24  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 25  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 26  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 27  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 28  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 29  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 30  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 31  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 32  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 33  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 34  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 35  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 36  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 37  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 38  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 39  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 40  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 41  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 42  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 43  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 44  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 45  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 46  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 47  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 48  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 49  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 50  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 51  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 52  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 53  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 54  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 55  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 56  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 57  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 58  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 59  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 60  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 61  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 62  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 63  org.python.python             	0x00212206 function_call + 166
> 64  org.python.python             	0x001e1a25 PyObject_Call + 85
> 65  org.python.python             	0x001f3806 instancemethod_call +  
> 422
> 66  org.python.python             	0x001e1a25 PyObject_Call + 85
> 67  org.python.python             	0x00247e37 slot_tp_call + 71
> 68  org.python.python             	0x001e1a25 PyObject_Call + 85
> 69  org.python.python             	0x00290abe PyEval_EvalFrameEx +  
> 13614
> 70  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 71  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 72  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 73  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 74  org.python.python             	0x00212206 function_call + 166
> 75  org.python.python             	0x001e1a25 PyObject_Call + 85
> 76  org.python.python             	0x001f3806 instancemethod_call +  
> 422
> 77  org.python.python             	0x001e1a25 PyObject_Call + 85
> 78  org.python.python             	0x0028c5ce
> PyEval_CallObjectWithKeywords + 78
> 79  org.python.python             	0x001f66d2 PyInstance_New + 114
> 80  org.python.python             	0x001e1a25 PyObject_Call + 85
> 81  org.python.python             	0x00290abe PyEval_EvalFrameEx +  
> 13614
> 82  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 83  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 84  org.python.python             	0x00212206 function_call + 166
> 85  org.python.python             	0x001e1a25 PyObject_Call + 85
> 86  org.python.python             	0x0028ff21 PyEval_EvalFrameEx +  
> 10641
> 87  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 88  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 89  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 90  org.python.python             	0x00212206 function_call + 166
> 91  org.python.python             	0x001e1a25 PyObject_Call + 85
> 92  org.python.python             	0x001f3806 instancemethod_call +  
> 422
> 93  org.python.python             	0x001e1a25 PyObject_Call + 85
> 94  org.python.python             	0x0028c5ce
> PyEval_CallObjectWithKeywords + 78
> 95  org.python.python             	0x002cd70f t_bootstrap + 63
> 96  libSystem.B.dylib             	0x939a0155 _pthread_start + 321
> 97  libSystem.B.dylib             	0x939a0012 thread_start + 34
>
> Thread 4:
> 0   libSystem.B.dylib             	0x9397646e __semwait_signal + 10
> 1   libSystem.B.dylib             	0x939a0dcd pthread_cond_wait
> $UNIX2003 + 73
> 2   org.python.python             	0x002c856c PyThread_acquire_lock +
> 172
> 3   org.python.python             	0x0028c2f3 PyEval_RestoreThread +  
> 67
> 4   org.python.python             	0x00206c63 get_line + 259
> 5   org.python.python             	0x00208e1c file_readline + 108
> 6   org.python.python             	0x0029209c PyEval_EvalFrameEx +  
> 19212
> 7   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 8   org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 9   org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 10  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 11  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 12  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 13  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 14  org.python.python             	0x002921f6 PyEval_EvalFrameEx +  
> 19558
> 15  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 16  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 17  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 18  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 19  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 20  org.python.python             	0x00212206 function_call + 166
> 21  org.python.python             	0x001e1a25 PyObject_Call + 85
> 22  org.python.python             	0x001f3806 instancemethod_call +  
> 422
> 23  org.python.python             	0x001e1a25 PyObject_Call + 85
> 24  org.python.python             	0x00247e37 slot_tp_call + 71
> 25  org.python.python             	0x001e1a25 PyObject_Call + 85
> 26  org.python.python             	0x00290abe PyEval_EvalFrameEx +  
> 13614
> 27  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 28  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 29  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 30  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 31  org.python.python             	0x00212206 function_call + 166
> 32  org.python.python             	0x001e1a25 PyObject_Call + 85
> 33  org.python.python             	0x001f3806 instancemethod_call +  
> 422
> 34  org.python.python             	0x001e1a25 PyObject_Call + 85
> 35  org.python.python             	0x0028c5ce
> PyEval_CallObjectWithKeywords + 78
> 36  org.python.python             	0x001f66d2 PyInstance_New + 114
> 37  org.python.python             	0x001e1a25 PyObject_Call + 85
> 38  org.python.python             	0x00290abe PyEval_EvalFrameEx +  
> 13614
> 39  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 40  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 41  org.python.python             	0x00212206 function_call + 166
> 42  org.python.python             	0x001e1a25 PyObject_Call + 85
> 43  org.python.python             	0x0028ff21 PyEval_EvalFrameEx +  
> 10641
> 44  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 45  org.python.python             	0x00292df9 PyEval_EvalFrameEx +  
> 22633
> 46  org.python.python             	0x00293f4d PyEval_EvalCodeEx + 2109
> 47  org.python.python             	0x00212206 function_call + 166
> 48  org.python.python             	0x001e1a25 PyObject_Call + 85
> 49  org.python.python             	0x001f3806 instancemethod_call +  
> 422
> 50  org.python.python             	0x001e1a25 PyObject_Call + 85
> 51  org.python.python             	0x0028c5ce
> PyEval_CallObjectWithKeywords + 78
> 52  org.python.python             	0x002cd70f t_bootstrap + 63
> 53  libSystem.B.dylib             	0x939a0155 _pthread_start + 321
> 54  libSystem.B.dylib             	0x939a0012 thread_start + 34
>
> Thread 1 crashed with X86 Thread State (32-bit):
>   eax: 0x0107e680  ebx: 0x0028d59b  ecx: 0xc7013ef7  edx: 0x010811e0
>   edi: 0x016ef2b0  esi: 0xc7013ef7  ebp: 0xb0001048  esp: 0xb0001000
>    ss: 0x0000001f  efl: 0x00010286  eip: 0x002252d2   cs: 0x00000017
>    ds: 0x0000001f   es: 0x0000001f   fs: 0x0000001f   gs: 0x00000037
>   cr2: 0xb0000ffc
>
> Binary Images:
>     0x1000 -     0x1ff8 +org.python.python 2.6.2 (2.6.2)
> <367715e0918b9027adecf6daa9c9c0b4> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/ 
> Python
>    0x8e000 -    0x8fff5 +_locale.so ??? (???)
> <7ef9b91f44c9fdcd161b25b66dfc6043> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_locale.so
>    0x94000 -    0x9bff3 +libintl.8.dylib ??? (???)
> <49bae84b06c07fc238d729e582c22694> /opt/local/lib/libintl.8.dylib
>    0xba000 -    0xbbfff +time.so ??? (???)
> <b4df08b447c576d1d3ed44c7cff3c0eb> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/time.so
>    0xc1000 -    0xc4ff9 +strop.so ??? (???)
> <b2d9a8bdc5769775f370e9fbf5a8e7a6> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/strop.so
>   0x113000 -   0x11aff7 +_socket.so ??? (???)
> <6bf5330ff6a0351600ceed5b4bb18ace> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_socket.so
>   0x123000 -   0x124fff +_random.so ??? (???)
> <0973aa42af1925a5907a5b4a06847401> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_random.so
>   0x1d7000 -   0x2fefeb +org.python.python 2.6.2, (c) 2004-2008
> Python Software Foundation. (2.6.2)
> <744ac9a0c227b426812ec43bf65fa2a9> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/Python
>   0x3ee000 -   0x3f1ff7 +_ssl.so ??? (???)
> <7e27f76cc0fdea2eb0f2d55b4e00c99d> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_ssl.so
>   0x3f7000 -   0x3f8ff9 +cStringIO.so ??? (???)
> <58e93c29e736b9125720908b3966aefa> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/cStringIO.so
>   0x600000 -   0x638feb +libssl.0.9.8.dylib ??? (???)
> <048da2db2c9a6df30b609d912e51d136> /opt/local/lib/libssl.0.9.8.dylib
>   0x64c000 -   0x74efe7 +libcrypto.0.9.8.dylib ??? (???)
> <294465ec0f38141274d3f34f7fd28e72> /opt/local/lib/libcrypto. 
> 0.9.8.dylib
>   0x7ac000 -   0x7bcffd +libz.1.dylib ??? (???)
> <a3bea29149481a5c9fd056566c80b4df> /opt/local/lib/libz.1.dylib
>   0x7c1000 -   0x7c3fff +math.so ??? (???)
> <9359a4f723aad09ae871d802ac773000> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/math.so
>   0x7c9000 -   0x7cbffa +binascii.so ??? (???)
> <ef0519e1b4ec1649e28e68282e5eece7> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/binascii.so
>   0x7d0000 -   0x7d1ff0 +fcntl.so ??? (???)
> <72ddc90c1bf5c0acfd389f01a555bc05> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/fcntl.so
>   0x7d5000 -   0x7d7fff +select.so ??? (???)
> <cc436a4ca34e37552d4f80bf216a3d54> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/select.so
>   0x7dc000 -   0x7dcffc +_functools.so ??? (???)
> <ac084464c78f6e726eeb10a4770dcffc> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_functools.so
>   0x7e0000 -   0x7e3ff3 +_collections.so ??? (???)
> <57ffefd49b96c09178156f8362b7851c> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/ 
> _collections.so
>   0x7e9000 -   0x7ecfff +operator.so ??? (???)
> <c63986aaac35569416805028a5b54242> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/operator.so
>  0x1040000 -  0x104efff +cPickle.so ??? (???)
> <6896611538f2c5df6fdd88a57b7c2675> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/cPickle.so
>  0x1056000 -  0x1059ff7 +_struct.so ??? (???)
> <cb30abbfff6792a1b8c6218f2a302c04> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_struct.so
>  0x1060000 -  0x1060ff5 +_bisect.so ??? (???)
> <7dc80fbd952625e518d23916d581384c> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_bisect.so
>  0x10a5000 -  0x10b1fff +datetime.so ??? (???)
> <43f21dd5c25911e6e00dde9dc7c2602a> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/datetime.so
>  0x1168000 -  0x125fff0 +libiconv.2.dylib ??? (???)
> <3d3d7700af270c0ac25b5c30ca04e952> /opt/local/lib/libiconv.2.dylib
>  0x126c000 -  0x1270ffe +itertools.so ??? (???)
> <94489dcda7de5db9bee12468c6be9d1a> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/itertools.so
>  0x1279000 -  0x127aff5 +_hashlib.so ??? (???)
> <1c460b598de08c8ecf73fe464bc583ba> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_hashlib.so
>  0x127f000 -  0x12adfe7 +pyexpat.so ??? (???)
> <7990f544f2de907fde877c99c09300f5> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/pyexpat.so
>  0x133e000 -  0x134cffe +parser.so ??? (???)
> <e726ed3dde5de9af8c95c4a047408b1a> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/parser.so
>  0x1399000 -  0x1399ff5 +_weakref.so ??? (???)
> <fc73ab3ae50b4f6432972b6e7b1aebe2> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_weakref.so
>  0x139d000 -  0x139ffff +_multiprocessing.so ??? (???)
> <76068fbaed61f131616a40ae2217a965> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/
> _multiprocessing.so
>  0x13a5000 -  0x13a5ffa +libsvn_fs_util-1.0.dylib ??? (???)
> <a49fcc057649e29810650021911f6d4f> /opt/local/lib/
> libsvn_fs_util-1.0.dylib
>  0x156a000 -  0x156dfef +unicodedata.so ??? (???)
> <7beba7d8b827b0d1914d198e8660ac8c> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/unicodedata.so
>  0x1700000 -  0x1702ff5 +_csv.so ??? (???)
> <0b0f6778f7cbf66ad699b67a7905716e> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_csv.so
>  0x1708000 -  0x1709ff9 +_heapq.so ??? (???)
> <68e1903048d0ce6866ff42e034499aa4> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_heapq.so
>  0x170e000 -  0x170fff6 +termios.so ??? (???)
> <0a51ed431f047cf8b022b474582bbfa6> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/termios.so
>  0x17d8000 -  0x17e0fff +_sqlite3.so ??? (???)
> <07aae450ad98e3648209a53e3d9bdf6a> /opt/local/Library/Frameworks/
> Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_sqlite3.so
>  0x17eb000 -  0x184bfeb +libsqlite3.0.dylib ??? (???)
> <0d535262194ffad788aa7cc1b7af4c7c> /opt/local/lib/libsqlite3.0.dylib
>  0x18ea000 -  0x1900ff3 +_fs.so ??? (???)
> <534edd5bb88032d0b74c5e686616a2fd> /opt/local/lib/svn-python2.6/ 
> libsvn/
> _fs.so
>  0x190d000 -  0x1916ffe +libsvn_swig_py26-1.0.dylib ??? (???)
> <60071292edee6b15ed8bd07c37ba3973> /opt/local/lib/
> libsvn_swig_py26-1.0.dylib
>  0x191d000 -  0x1951ff3 +libsvn_client-1.0.dylib ??? (???)
> <1a1edd2dfabda198ebcdb546b4d38db4> /opt/local/lib/
> libsvn_client-1.0.dylib
>  0x195d000 -  0x1995fff +libsvn_wc-1.0.dylib ??? (???)
> <22a68658c1cdb8b52ecb3a1e8a56fb8b> /opt/local/lib/libsvn_wc-1.0.dylib
>  0x19a1000 -  0x19a9ff3 +libsvn_diff-1.0.dylib ??? (???)
> <34f9b940408ff97acbeb71dd74ca86c4> /opt/local/lib/ 
> libsvn_diff-1.0.dylib
>  0x19ae000 -  0x19b3ff2 +libsvn_ra-1.0.dylib ??? (???)
> <b70163f74da3128d9eb0ae56a761a476> /opt/local/lib/libsvn_ra-1.0.dylib
>  0x19b8000 -  0x19bbffe +libsvn_ra_local-1.0.dylib ??? (???)
> <721a6296510fe05d10c9a3dcd0c97014> /opt/local/lib/
> libsvn_ra_local-1.0.dylib
>  0x19c0000 -  0x19dfff3 +libsvn_repos-1.0.dylib ??? (???)
> <5fb8530ec65dd31520780187a5d44543> /opt/local/lib/ 
> libsvn_repos-1.0.dylib
>  0x19e7000 -  0x19e9ff8 +libsvn_fs-1.0.dylib ??? (???)
> <4fea2da5392497b82785b5b9febac38e> /opt/local/lib/libsvn_fs-1.0.dylib
>  0x19ee000 -  0x1a0affc +libsvn_fs_fs-1.0.dylib ??? (???)
> <c84cd7248b719ed847d512e92f33953d> /opt/local/lib/ 
> libsvn_fs_fs-1.0.dylib
>  0x1a13000 -  0x1a33ffb +libsvn_fs_base-1.0.dylib ??? (???)
> <4a7492969c63d2ec0bd265f786c31129> /opt/local/lib/
> libsvn_fs_base-1.0.dylib
>  0x1a3d000 -  0x1b37fef +libdb-4.6.dylib ??? (???)
> <c38bbde94d43ef6c1592ddb2392521cc> /opt/local/lib/db46/libdb-4.6.dylib
>  0x1b4c000 -  0x1b5bfff +libsvn_ra_svn-1.0.dylib ??? (???)
> <5859aee58d810feb97afca0d816598a5> /opt/local/lib/
> libsvn_ra_svn-1.0.dylib
>  0x1b62000 -  0x1b74ff3 +libsasl2.2.dylib ??? (???)
> <2b2b9d429b833b94972b46568307aa2c> /opt/local/lib/libsasl2.2.dylib
>  0x1b7a000 -  0x1b91ff3 +libsvn_ra_neon-1.0.dylib ??? (???)
> <e77ff3693c54fa6c614f79c392b8045b> /opt/local/lib/
> libsvn_ra_neon-1.0.dylib
>  0x1b9a000 -  0x1bb1fff +libneon.27.dylib ??? (???)
> <f648ad7430e4152c0b7eafae24d87854> /opt/local/lib/libneon.27.dylib
>  0x1bba000 -  0x1bd4fff +libsvn_ra_serf-1.0.dylib ??? (???)
> <1aa768029afa839db831eeae0e16ac9d> /opt/local/lib/
> libsvn_ra_serf-1.0.dylib
>  0x1bdd000 -  0x1be4ff9 +libserf-0.0.dylib ??? (???)
> <02969d31742a69f480404b73210de14f> /opt/local/lib/libserf-0.0.dylib
>  0x1beb000 -  0x1bf2ff6 +libsvn_delta-1.0.dylib ??? (???)
> <1e863655a59c9bbbcda07229c9503003> /opt/local/lib/ 
> libsvn_delta-1.0.dylib
>  0x1bf7000 -  0x1c2dfff +libsvn_subr-1.0.dylib ??? (???)
> <7bda66e5e09ba4347e9a6b977c09815a> /opt/local/lib/ 
> libsvn_subr-1.0.dylib
>  0x1c3d000 -  0x1c51ff3 +libaprutil-1.0.dylib ??? (???)
> <8df1469df11db34d546ffdb359b67f31> /opt/local/lib/libaprutil-1.0.dylib
>  0x1c5a000 -  0x1c76fe3 +libexpat.1.dylib ??? (???)
> <86bb4cce4c61a5db862ebfb991656809> /opt/local/lib/libexpat.1.dylib
>  0x1c7e000 -  0x1c97fef +libapr-1.0.dylib ??? (???)
> <c3bb262cf2e00913bad332b9bae21564> /opt/local/lib/libapr-1.0.dylib
>  0x1ca2000 -  0x1cabfe3  libpam.1.dylib ??? (???)
> <a504882e2e8a81210edd1ac438597e37> /usr/lib/libpam.1.dylib
>  0x1cc3000 -  0x1cd6ff5 +_delta.so ??? (???)
> <36d25ae3e277e49b59e581476680b1ec> /opt/local/lib/svn-python2.6/ 
> libsvn/
> _delta.so
>  0x1d2f000 -  0x1d72ff3 +_core.so ??? (???)
> <75144aa0980fb2382d7f3cdfb56bbc68> /opt/local/lib/svn-python2.6/ 
> libsvn/
> _core.so
>  0x1e1d000 -  0x1e3fff2 +_repos.so ??? (???)
> <a2f3b0beb81a86b388decf2e1201d8dc> /opt/local/lib/svn-python2.6/ 
> libsvn/
> _repos.so
> 0x8fe00000 - 0x8fe2db43  dyld 97.1 (???)
> <100d362e03410f181a34e04e94189ae5> /usr/lib/dyld
> 0x90499000 - 0x90525ff7  com.apple.LaunchServices 290.3 (290.6)
> <bdba267184df88bd5b8e2116ea903872> /System/Library/Frameworks/
> CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/
> Versions/A/LaunchServices
> 0x90526000 - 0x90800ff3  com.apple.CoreServices.CarbonCore 786.11
> (786.13) <9e2d85d52e5e2951aa4dd53c48ccc52f> /System/Library/ 
> Frameworks/
> CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/
> Versions/A/CarbonCore
> 0x91be5000 - 0x91d18fef  com.apple.CoreFoundation 6.5.6 (476.18)
> <2d52bab73660117571bd6486dc318f8e> /System/Library/Frameworks/
> CoreFoundation.framework/Versions/A/CoreFoundation
> 0x91fbe000 - 0x92045ff7  libsqlite3.0.dylib ??? (???)
> <3334ea5af7a911637413334154bb4100> /usr/lib/libsqlite3.0.dylib
> 0x92046000 - 0x9205cfff  com.apple.DictionaryServices 1.0.0 (1.0.0)
> <7d20b8d1fb238c3e71d0fa6fda18c4f7> /System/Library/Frameworks/
> CoreServices.framework/Versions/A/Frameworks/
> DictionaryServices.framework/Versions/A/DictionaryServices
> 0x921a4000 - 0x92254fff  edu.mit.Kerberos 6.0.13 (6.0.13)
> <804bd1b3f08fb57396781f012006367c> /System/Library/Frameworks/
> Kerberos.framework/Versions/A/Kerberos
> 0x92255000 - 0x9238eff7  libicucore.A.dylib ??? (???)
> <cac059ebdac7d9a63ee0f7a648c9f6cf> /usr/lib/libicucore.A.dylib
> 0x92395000 - 0x923b9fff  libxslt.1.dylib ??? (???)
> <0a9778d6368ae668826f446878deb99b> /usr/lib/libxslt.1.dylib
> 0x92480000 - 0x92480ffa  com.apple.CoreServices 32 (32)
> <373d6a888f9204641f313bc6070ae065> /System/Library/Frameworks/
> CoreServices.framework/Versions/A/CoreServices
> 0x925b8000 - 0x925bfffe  libbsm.dylib ??? (???)
> <fa7ae5f1a621d9b69e7e18747c9405fb> /usr/lib/libbsm.dylib
> 0x92654000 - 0x9265cfff  com.apple.DiskArbitration 2.2.1 (2.2.1)
> <2664eeb3a4d0c95a21c089892a0ae8d0> /System/Library/Frameworks/
> DiskArbitration.framework/Versions/A/DiskArbitration
> 0x92c2f000 - 0x92cbbff7  com.apple.framework.IOKit 1.5.2 (???)
> <97b9f9d584f48891377f0481b9104434> /System/Library/Frameworks/
> IOKit.framework/Versions/A/IOKit
> 0x9332f000 - 0x9340ffff  libobjc.A.dylib ??? (???)
> <400e943f9e8a678eea22a1d1205490ee> /usr/lib/libobjc.A.dylib
> 0x93480000 - 0x9349efff  libresolv.9.dylib ??? (???)
> <9ed809256ce8913cddc3269c2e364654> /usr/lib/libresolv.9.dylib
> 0x9349f000 - 0x93580ff7  libxml2.2.dylib ??? (???)
> <2f6b294896866822330a8888b7f53b75> /usr/lib/libxml2.2.dylib
> 0x9396e000 - 0x93ad5ff3  libSystem.B.dylib ??? (???)
> <b47c8e6e45aef620730710a732bf1930> /usr/lib/libSystem.B.dylib
> 0x93b64000 - 0x93c1efe3  com.apple.CoreServices.OSServices 227 (227)
> <30cebcb68b1b571df7d77474e0c31556> /System/Library/Frameworks/
> CoreServices.framework/Versions/A/Frameworks/OSServices.framework/
> Versions/A/OSServices
> 0x93c1f000 - 0x93c4efe3  com.apple.AE 402.3 (402.3)
> <b13bfda0ad9314922ee37c0d018d7de9> /System/Library/Frameworks/
> CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/ 
> AE
> 0x9453b000 - 0x94549ffd  libz.1.dylib ??? (???)
> <a98b3b221a72b54faf73ded3dd7000e5> /usr/lib/libz.1.dylib
> 0x95891000 - 0x95935fec  com.apple.CFNetwork 438.10 (438.12)
> <fde64bbb20532794396fb21911ccaa98> /System/Library/Frameworks/
> CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/
> Versions/A/CFNetwork
> 0x959d2000 - 0x95a09fff  com.apple.SystemConfiguration 1.9.2 (1.9.2)
> <eab546255ac099b9616df999c9359d0e> /System/Library/Frameworks/
> SystemConfiguration.framework/Versions/A/SystemConfiguration
> 0x95a0f000 - 0x95a3afe7  libauto.dylib ??? (???)
> <2e44c523b851e8e25f05d13a48070a58> /usr/lib/libauto.dylib
> 0x96b58000 - 0x96b5cfff  libmathCommon.A.dylib ??? (???) /usr/lib/
> system/libmathCommon.A.dylib
> 0x96fc9000 - 0x97012fef  com.apple.Metadata 10.5.2 (398.25)
> <e0572f20350523116f23000676122a8d> /System/Library/Frameworks/
> CoreServices.framework/Versions/A/Frameworks/Metadata.framework/
> Versions/A/Metadata
> 0x970f9000 - 0x97156ffb  libstdc++.6.dylib ??? (???)
> <f75e5133d72769de5ce6c06153fc65f6> /usr/lib/libstdc++.6.dylib
> 0x97198000 - 0x9719ffe9  libgcc_s.1.dylib ??? (???)
> <e280ddf3f5fb3049e674edcb109f389a> /usr/lib/libgcc_s.1.dylib
> 0x97220000 - 0x9729fff5  com.apple.SearchKit 1.2.1 (1.2.1)
> <f28f8dd0f155a6453411a0c9b5702764> /System/Library/Frameworks/
> CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/
> Versions/A/SearchKit
> 0x972fc000 - 0x974cdffb  com.apple.security 5.0.5 (36371)
> <c13e0bb1acfdcf94be4d3ee118ef190e> /System/Library/Frameworks/
> Security.framework/Versions/A/Security
> 0xfffe8000 - 0xfffebfff  libobjc.A.dylib ??? (???) /usr/lib/
> libobjc.A.dylib
> 0xffff0000 - 0xffff1780  libSystem.B.dylib ??? (???) /usr/lib/
> libSystem.B.dylib
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 13 Jun 2009 16:51:19 -0500
> From: Ryan Schmidt <ryandesign at macports.org>
> To: Thomas De?Contes <d.l.tDeContes at free.fr>
> Cc: liste macports <macports-users at lists.macosforge.org>
> Subject: Re: dbus
> Message-ID: <D84A8471-F8BD-40E8-A313-5C4FE81D5978 at macports.org>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
>
> On Jun 13, 2009, at 07:02, Thomas De Contes wrote:
>
>> --->  Installing dbus @1.2.12_5
>> Error: Target org.macports.activate returned: <main> attribute
>> status: eDSPermissionError
>>
>> what's the problem ?
>
> I assume you're doing this in a non-root MacPorts installation. dbus
> wants to install a startupitem so you need to either use sudo to
> install it, or use the no_startupitem variant.
>
>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 13 Jun 2009 17:59:18 -0400
> From: William Davis <frstan at bellsouth.net>
> To: macports-users at lists.macosforge.org
> Subject: kdelibs4 checksum wrong
> Message-ID: <2385045D-BF1A-4E7A-8762-4B71565C6A01 at bellsouth.net>
> Content-Type: text/plain; charset="us-ascii"; Format="flowed";
> 	DelSp="yes"
>
> as is new version kdelibs4 has wrong checksum.
> substituted m5      9ed29086c33bc73256a7fa5268df560b  in portfile and
> it builds ok
> the remaining kde upgrades need this fixed first to build or rather,
> to configure
>
>
> William Davis
> frstanATbellsouthDOTnet
> Mac OS X.5.7 Darwin 9.7.0
> XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
> Mac Mini Intel Duo @ 1.86 GHz
>
> Mundus vult decepi, ego non
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090613/8a5baf42/attachment-0001.html 
> >
>
> ------------------------------
>
> Message: 6
> Date: Sun, 14 Jun 2009 09:33:35 +1000
> From: Joshua Root <jmr at macports.org>
> To: Ryan Schmidt <ryandesign at macports.org>
> Cc: liste macports <macports-users at lists.macosforge.org>
> Subject: Re: dbus
> Message-ID: <4A34374F.9020607 at macports.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 2009-6-14 07:51, Ryan Schmidt wrote:
>>
>> On Jun 13, 2009, at 07:02, Thomas De Contes wrote:
>>
>>> --->  Installing dbus @1.2.12_5
>>> Error: Target org.macports.activate returned: <main> attribute  
>>> status:
>>> eDSPermissionError
>>>
>>> what's the problem ?
>>
>> I assume you're doing this in a non-root MacPorts installation. dbus
>> wants to install a startupitem so you need to either use sudo to  
>> install
>> it, or use the no_startupitem variant.
>
> Or set 'startupitem_type none' in macports.conf, which will take  
> care of
> this for all ports.
>
> - Josh
>
>
> ------------------------------
>
> Message: 7
> Date: Sun, 14 Jun 2009 01:43:53 +0200
> From: Thomas De?Contes <d.l.tDeContes at free.fr>
> To: Ryan Schmidt <ryandesign at macports.org>
> Cc: liste macports <macports-users at lists.macosforge.org>
> Subject: Re: dbus
> Message-ID: <22DF0311-111E-43EB-996F-2B8A518A4591 at free.fr>
> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
>
>
> Le 13 juin 09 ? 23:51, Ryan Schmidt a ?crit :
>
>>
>> On Jun 13, 2009, at 07:02, Thomas De Contes wrote:
>>
>>> --->  Installing dbus @1.2.12_5
>>> Error: Target org.macports.activate returned: <main> attribute
>>> status: eDSPermissionError
>>>
>>> what's the problem ?
>>
>> I assume you're doing this in a non-root MacPorts installation.
>
> yes ;-)
>
>> dbus wants to install a startupitem so you need to either use sudo
>> to install it, or use the no_startupitem variant.
>
> thank you :-)
>
> well, is it possible to make MacPorts to automatically switch to the
> appropriate variant, in a such case ?
>
>
> -- 
> T?l?assistance / T?l?maintenance
> http://www.portparallele.com/ThomasDECONTES/
>
>
>
> ------------------------------
>
> Message: 8
> Date: Sat, 13 Jun 2009 19:20:09 -0500
> From: Ryan Schmidt <ryandesign at macports.org>
> To: Thomas De?Contes <d.l.tDeContes at free.fr>
> Cc: liste macports <macports-users at lists.macosforge.org>
> Subject: Re: dbus
> Message-ID: <7AC8D49B-A86A-473E-8A4A-8E2DD3E95B28 at macports.org>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
>
> On Jun 13, 2009, at 18:43, Thomas De Contes wrote:
>
>>> dbus wants to install a startupitem so you need to either use sudo
>>> to install it, or use the no_startupitem variant.
>>
>> thank you :-)
>>
>> well, is it possible to make MacPorts to automatically switch to
>> the appropriate variant, in a such case ?
>
> No, but if you are certain you never want any port to install a
> startup item, you can set the startup item type to none as Josh
> explained.
>
>
>
>
> ------------------------------
>
> Message: 9
> Date: Sun, 14 Jun 2009 02:20:52 +0200
> From: Thomas De?Contes <d.l.tDeContes at free.fr>
> To: liste macports <macports-users at lists.macosforge.org>
> Subject: purge
> Message-ID: <09BA39C3-895A-4F1D-BEF2-D4362D87EE9D at free.fr>
> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
>
> hi :-)
>
>
> i think it would be very useful to be able to make a purging,
>
> given that the user knows which ports he needs, but he doesn't
> control the dependencies
>
>
>
> I propose:
>
>
> a new state : "locked"
>
> when the user installs a port, it becomes locked, but not its
> dependencies
> when the user installs a port which is already installed, it locks it
>
> locking wouldn't have effect on operations manually done by the
> user : if he wants to uninstall a port, it unlocks and uninstalls it
>
>
> when the user makes a purging :
>
> - it lists all locked ports
> - it makes the tree of dependencies of this list
> - it uninstalls ports which are not in this tree
>
>
>
> the "locked" state represents the ports that the user knows and
> directly needs
>
>
> it's usefull to remember the list of ports declared needed, and then
> say "oh, this one, i don't need it any more"
> and then a purging uninstalls all dependencies of this port which are
> not used by an other port :-)
>
>
> it can also be usefull in the case where :
>
> a port A and a port B exist
> C depends on A
> then, the author of C finds that B is better, so C doesn't depend on
> A longer
> but A still exists ...
> then A isn't very usefull and waste space, entries, ... :-)
>
>
>
> what do you think about this ? :-)
>
>
> -- 
> T?l?assistance / T?l?maintenance
> http://www.portparallele.com/ThomasDECONTES/
>
>
>
> ------------------------------
>
> Message: 10
> Date: Sun, 14 Jun 2009 03:18:00 +0200
> From: Rainer M?ller <raimue at macports.org>
> To: Thomas De?Contes <d.l.tDeContes at free.fr>
> Cc: liste macports <macports-users at lists.macosforge.org>
> Subject: Re: purge
> Message-ID: <4A344FC8.20005 at macports.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 2009-06-14 02:20, Thomas De Contes wrote:
>> what do you think about this ? :-)
>
> You want #15260 [1] to be implemented, which covers exactly what you
> propose here.
>
> Until that, you can use port_cutleaves [2] to identify and uninstall  
> no
> longer needed ports.
>
> Rainer
>
> [1] http://trac.macports.org/ticket/15260
> [2] Available as port named port_cutleaves, see also
> http://svn.macports.org/repository/macports/contrib/port_cutleaves/README
>
>
> ------------------------------
>
> Message: 11
> Date: Sat, 13 Jun 2009 22:14:52 -0700
> From: Jeremy Huddleston <jeremyhu at macports.org>
> To: Thomas De?Contes <d.l.tDeContes at free.fr>
> Cc: liste macports <macports-users at lists.macosforge.org>
> Subject: Re: pkgconfig / dependencies in xorg ?
> Message-ID: <CCB3A7F3-16F0-4895-8871-4157181545EF at macports.org>
> Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes
>
> Well xorg-libX11 has depends_lib on xorg-xproto ... so it should be
> getting updated before xorg-libX11 ... what version of xorg-xproto do
> you have on your system?
>
> On Jun 12, 2009, at 17:20, Thomas De Contes wrote:
>
>> hi :-)
>>
>>
>> here is what i get when i upgrade ports on a very old installation :
>> port -u upgrade outdated
>>
>>
>> --->  Configuring xorg-libX11
>> Error: Target org.macports.configure returned: configure failure:
>> shell command " cd "/Users/thomas/Documents/prgm/bin/autoinstall/
>> macports/var/macports/build/
>> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync 
>> .macports.org_release_ports_x11_xorg
>> -libX11/work/libX11-1.2.1" && ./configure --prefix=/Users/thomas/
>> Documents/prgm/bin/autoinstall/macports --without-xcb " returned
>> error 1
>> Command output: checking if the linker (/usr/libexec/gcc/powerpc-
>> apple-darwin8/4.0.1/ld) is GNU ld... no
>> checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/
>> powerpc-apple-darwin8/4.0.1/ld) supports shared libraries... yes
>> checking for /usr/bin/g++-4.0 option to produce PIC... -fno-common
>> checking if /usr/bin/g++-4.0 PIC flag -fno-common works... yes
>> checking if /usr/bin/g++-4.0 static flag -static works... no
>> checking if /usr/bin/g++-4.0 supports -c -o file.o... yes
>> checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/
>> powerpc-apple-darwin8/4.0.1/ld) supports shared libraries... yes
>> checking dynamic linker characteristics... darwin8.11.0 dyld
>> checking how to hardcode library paths into programs... immediate
>> appending configuration tag "F77" to libtool
>> checking for bash... /bin/bash
>> checking if dolt supports this host... no, falling back to libtool
>> checking for gcc... (cached) /usr/bin/gcc-4.0
>> checking whether we are using the GNU C compiler... (cached) yes
>> checking whether /usr/bin/gcc-4.0 accepts -g... (cached) yes
>> checking for /usr/bin/gcc-4.0 option to accept ISO C89... (cached)
>> none needed
>> checking dependency style of /usr/bin/gcc-4.0... (cached) gcc3
>> checking for cpp... /usr/bin/cpp
>> checking if /usr/bin/cpp requires -undef... no
>> checking if /usr/bin/cpp requires -traditional... no
>> checking whether to use XCB... (cached) no
>> checking for pkg-config... /Users/thomas/Documents/prgm/bin/
>> autoinstall/macports/bin/pkg-config
>> checking pkg-config is at least version 0.9.0... yes
>> checking for XPROTO... configure: error: Package requirements
>> (xproto >= 7.0.13) were not met.
>> Consider adjusting the PKG_CONFIG_PATH environment variable if you
>> installed software in a non-standard prefix.
>>
>> Alternatively you may set the XPROTO_CFLAGS and XPROTO_LIBS
>> environment variables
>> to avoid the need to call pkg-config.  See the pkg-config man page  
>> for
>> more details.
>>
>>
>> and it built fine just after it upgraded xorg-xproto (continuing
>> port -u upgrade outdated)
>>
>> and then :
>>
>>
>> --->  Configuring xorg-libXrandr
>> Error: Target org.macports.configure returned: configure failure:
>> shell command " cd "/Users/thomas/Documents/prgm/bin/autoinstall/
>> macports/var/macports/build/
>> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync 
>> .macports.org_release_ports_x11_xorg
>> -libXrandr/work/libXrandr-1.3.0" && ./configure --prefix=/Users/
>> thomas/Documents/prgm/bin/autoinstall/macports " returned error 1
>> Command output: checking for stdint.h... yes
>> checking for unistd.h... yes
>> checking for dlfcn.h... yes
>> checking for objdir... .libs
>> checking if /usr/bin/gcc-4.0 supports -fno-rtti -fno-exceptions... no
>> checking for /usr/bin/gcc-4.0 option to produce PIC... -fno-common -
>> DPIC
>> checking if /usr/bin/gcc-4.0 PIC flag -fno-common -DPIC works... yes
>> checking if /usr/bin/gcc-4.0 static flag -static works... no
>> checking if /usr/bin/gcc-4.0 supports -c -o file.o... yes
>> checking if /usr/bin/gcc-4.0 supports -c -o file.o... (cached) yes
>> checking whether the /usr/bin/gcc-4.0 linker (/usr/libexec/gcc/
>> powerpc-apple-darwin8/4.0.1/ld) supports shared libraries... yes
>> checking dynamic linker characteristics... darwin8.11.0 dyld
>> checking how to hardcode library paths into programs... immediate
>> checking whether stripping libraries is possible... yes
>> checking if libtool supports shared libraries... yes
>> checking whether to build shared libraries... yes
>> checking whether to build static libraries... yes
>> checking for pkg-config... /Users/thomas/Documents/prgm/bin/
>> autoinstall/macports/bin/pkg-config
>> checking pkg-config is at least version 0.9.0... yes
>> checking for RANDR... configure: error: Package requirements (x11
>> randrproto >= 1.3 xext xextproto xrender renderproto) were not met:
>>
>> No package 'renderproto' found
>>
>> Consider adjusting the PKG_CONFIG_PATH environment variable if you
>> installed software in a non-standard prefix.
>>
>> Alternatively, you may set the environment variables RANDR_CFLAGS
>> and RANDR_LIBS to avoid the need to call pkg-config.
>> See the pkg-config man page for more details.
>>
>>
>> after doing
>> port deactivate render
>> and redo
>> port -u upgrade outdated
>>
>> it activates xorg-renderproto (right)
>> it upgrades xrender
>> and it builds xorg-libXrandr fine
>>
>>
>> well, seeing the end of the errors, it may be a problem with
>> pkgconfig,
>> and regarding on how to get them around, it may be a problem about
>> dependencies
>>
>> what do you think about it ?
>>
>>
>> -- 
>> T?l?assistance / T?l?maintenance
>> http://www.portparallele.com/ThomasDECONTES/
>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
>
>
> ------------------------------
>
> Message: 12
> Date: Sat, 13 Jun 2009 22:18:16 -0700
> From: Jeremy Huddleston <jeremyhu at macports.org>
> To: MacPorts Users <macports-users at lists.macosforge.org>
> Subject: Re: texlive_base @2007_7+nox11 upgrade problem
> Message-ID: <F747244C-1A0A-470E-9FD1-8A7E95171E57 at macports.org>
> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
>
> You want the "no_x11" variant... not the "nox11" variant...
>
> On Jun 11, 2009, at 13:26, Kastus Shchuka wrote:
>
>> On Jun 11, 2009, at 9:52 AM, Kastus Shchuka wrote:
>>
>>>
>>> Should "lib:libXm:openmotif" be appended to line 89 of the port  
>>> file?
>>
>> Sorry, I meant line 83, looked at the wrong place. And that is where
>> this string was in the previous revision r52043 (line 79 there).
>>
>> I am still puzzled what brings in openmotif as dependency while it
>> is not reported by port deps command. Do we need to explicitly
>> depends_lib-delete it in no_x11 variant?
>>
>> Thanks, -Kastus
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
>
>
> ------------------------------
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
>
> End of macports-users Digest, Vol 34, Issue 10
> **********************************************


From chrislandalusa at gmail.com  Sun Jun 14 16:58:02 2009
From: chrislandalusa at gmail.com (Chris Laurenzano)
Date: Sun, 14 Jun 2009 19:58:02 -0400
Subject: uninstalling Macports
Message-ID: <4E7F521F-90C3-413C-AB2E-08E630F4BA2B@gmail.com>

I downloaded macports because I want to get Alpine, but after I  
downloaded and clicked on the .dmg icon, I don't know what to do  
next.  How do I get it to work and download Alpine?



From blb at macports.org  Sun Jun 14 17:21:17 2009
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 14 Jun 2009 18:21:17 -0600
Subject: uninstalling Macports
In-Reply-To: <4E7F521F-90C3-413C-AB2E-08E630F4BA2B@gmail.com>
References: <4E7F521F-90C3-413C-AB2E-08E630F4BA2B@gmail.com>
Message-ID: <20090615002117.GF83764@ninagal.withay.com>

On Sun, Jun 14, 2009 at 07:58:02PM -0400, Chris Laurenzano said:
> I downloaded macports because I want to get Alpine, but after I  
> downloaded and clicked on the .dmg icon, I don't know what to do next.  
> How do I get it to work and download Alpine?

Opening a Terminal window and running 'sudo port install alpine' should do
it.  You may want to have a look at the MacPorts guide on use:

<http://guide.macports.org/#using>

Bryan


From raimue at macports.org  Sun Jun 14 17:26:45 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Mon, 15 Jun 2009 02:26:45 +0200
Subject: macports-users Digest, Vol 34, Issue 10
In-Reply-To: <2B4739A4-2D7A-4CF4-8490-F92DC4EC2E32@charter.net>
References: <mailman.11.1244988001.18299.macports-users@lists.macosforge.org>
	<2B4739A4-2D7A-4CF4-8490-F92DC4EC2E32@charter.net>
Message-ID: <4A359545.8020309@macports.org>

Hello Brian,

On 2009-06-14 22:00, Brian Myers wrote:
> Well his account is disabled on my site.

You just replied to a digest message of the macports-users mailing list
which included 12 mails on different topics. But you did not say to
which message you actually refer to. Whose account is disabled?

Rainer


PS: Following the list with the digest option is probably a bit hard as
threads are being split into single mails without context. It is better
to set up mail filters to collect the mails in a single folder an read
them there.

See <http://trac.macports.org/wiki/MailingLists#intro.filter> for more
details.

From ryandesign at macports.org  Sun Jun 14 17:44:21 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 14 Jun 2009 19:44:21 -0500
Subject: apr-util dependencies
In-Reply-To: <E8A95942-23EB-44C8-A170-041832668140@centosprime.com>
References: <E8A95942-23EB-44C8-A170-041832668140@centosprime.com>
Message-ID: <71EABF3F-5E31-4348-93C7-8874C916AF5A@macports.org>


On Jun 13, 2009, at 12:34, Chris Janton wrote:

> Every time apr-util is upgraded it winds up trying to install  
> mysql5 on my system

[snip]

> I'm actually using mysql5-devel, so I don't need a fresh install of  
> mysql5 ;-)
>
> Is it simply a matter of changing the
>
> 	depends_lib-append port:mysql5
>
> to
>
> 	depends_lib-append path:bin/mysql_config5:mysql5
>
> so it will recognize that I already have mysql5 installed?

I hope so. I filed a ticket requesting this change:

http://trac.macports.org/ticket/19948



From boeyms at macports.org  Sun Jun 14 22:36:53 2009
From: boeyms at macports.org (Boey Maun Suang)
Date: Mon, 15 Jun 2009 15:36:53 +1000
Subject: port install gnat-gcc
In-Reply-To: <4A338554.4040602@macports.org>
References: <C030B322-9742-4589-A259-D185CB3B713B@free.fr>
	<4A326895.4050709@users.sourceforge.net>
	<E5413A52-CE7B-4FE7-86A8-2AC7523F91AB@free.fr>
	<4A338554.4040602@macports.org>
Message-ID: <CE33F78C-E679-4A8F-8EEA-8ED592FB7673@macports.org>

On 13/06/2009, at 8:54 PM, Martin Krischik wrote:

> That is strange as it is one of the three the offical releases of  
> GNAT:
> GNAT GPL (the free beer version), GNAT GAP (the accademic version) and
> GNAT PRO (the fully supported version).
>
> Beginners should consider GNAT GPL - gnat-gcc in MacPorts is more for
> advaned users. Also GNAT GPL 2009 now comes with an 64 bit compiler.
> That is pretty cool.

Just a couple of quick notes on the various GNAT versions that might  
be useful to know:

1. GNAT GAP is only available on application to professors/lecturers  
at accredited tertiary education institutions for the purposes of  
teaching;
2. GNAT GPL requires that any software compiled with it be released  
under GPLv3, while software compiled with the Ada compiler in GCC can  
be released under non-GPL licences;
3. GNAT GPL is a superset of the GCC Ada compiler -- the Ada support  
in GCC is made available by AdaCore under a modified GPL licence that  
allows binaries compiled with it to be released under non-GPL  
licences, whereas software compiled with GNAT GPL links to AdaCore  
libraries that are GPL-licensed (this is the reason for point 2 above);
4. GNAT GPL on Mac OS X is currently available for 32-bit and 64-bit  
PowerPC and 64-bit Intel (x86_64), but not 32-bit Intel (i386), while  
the GCC Ada compiler is should run on all four architectures;

> There is only one version if GNAT for MacPorts so there is nothing to
> update.

If it's of any interest to anyone, I've been having a go at creating a  
port that builds in the recommended way by downloading a bootstrap  
compiler and uses that to build GCC with Ada support, as the ghc port  
does.  (Because of the way that GCC builds and installs itself with  
absolute path references, the only way that I can see to get that to  
work would be to have the bootstrap built for installation into a  
temporary subdirectory of /var/tmp, have that build and install GCC  
with Ada support on the local machine, and then delete the bootstrap  
compiler -- though that may mean that it won't work with trace mode on).

I'm in the middle of exams right now, so I won't have much time to  
work on it until the end of the month, but I'd be happy to talk to you  
about it, either in macports-dev or off-list.

Kind regards,


Maun Suang

-- 
Boey Maun Suang
Email: boeyms at macports dot org


From retuow at gmail.com  Mon Jun 15 02:55:06 2009
From: retuow at gmail.com (Wouter Eerdekens)
Date: Mon, 15 Jun 2009 11:55:06 +0200
Subject: MacPorts .mp_* files
Message-ID: <867387cd0906150255r7e7313f0y4d771fc9d77ce622@mail.gmail.com>

Hi,

While browsing my MacPorts tree in /opt/local, I found a lot of files
with an .mp_* extension. For example in /opt/local/bin, there's

> ls *.mp_*
a2p.mp_1226917442        perl5.8.8.mp_1226917442  pod2usage.mp_1226917443
c2ph.mp_1226917442       perlbug.mp_1226917442    podchecker.mp_1226917443
cpan.mp_1226917442       perlcc.mp_1226917442     podselect.mp_1226917443
dprofpp.mp_1226917442    perldoc.mp_1226917443    prove.mp_1226917443
enc2xs.mp_1226917442     perlivp.mp_1226917443    psed.mp_1226917443
find2perl.mp_1226917442  piconv.mp_1226917443     pstruct.mp_1226917443
h2ph.mp_1226917442       pl2pm.mp_1226917443      s2p.mp_1226917443
h2xs.mp_1226917442       pod2html.mp_1226917443   splain.mp_1226917443
instmodsh.mp_1226917442  pod2latex.mp_1226917443  xsubpp.mp_1226917443
libnetcfg.mp_1226917442  pod2man.mp_1226917443
perl.mp_1226917442       pod2text.mp_1226917443

and throughout the entire /opt/local tree, there's about 1300 files
with that extension, totalling 31 MB. What are these? I can only
assume they're some kind of backup (made during an upgrade of a
certain port?)

For example, there's perl5.8.8.mp_1226917442, but I don't have a perl
5.8.8 port installed, it's at 5.8.9.

port provides /opt/local/bin/perl5.8.8.mp_1226917442

also tells me the file is not owned by any port I have installed.

Are these files safe to delete blindly, and why are they there in the
first place?

I'm running MacPorts 1.710, btw.

Thanks for any info...

Cheers,
Wouter

-- 
Murphy's Law is recursive.
Washing your car to make it rain doesn't work.

From ryandesign at macports.org  Mon Jun 15 03:41:41 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 15 Jun 2009 05:41:41 -0500
Subject: MacPorts .mp_* files
In-Reply-To: <867387cd0906150255r7e7313f0y4d771fc9d77ce622@mail.gmail.com>
References: <867387cd0906150255r7e7313f0y4d771fc9d77ce622@mail.gmail.com>
Message-ID: <180F7E20-0AE6-4F1F-89BD-D92B6274E8D7@macports.org>


On Jun 15, 2009, at 04:55, Wouter Eerdekens wrote:

> While browsing my MacPorts tree in /opt/local, I found a lot of files
> with an .mp_* extension.

[snip]

> What are these? I can only
> assume they're some kind of backup (made during an upgrade of a
> certain port?)

[snip]

> Are these files safe to delete blindly, and why are they there in the
> first place?


When you use the -f flag to force a port install because some files  
were in the way, the files that were in the way get renamed with  
a .mp_* extension. You're probably safe deleting these files.


From retuow at gmail.com  Mon Jun 15 06:45:39 2009
From: retuow at gmail.com (Wouter Eerdekens)
Date: Mon, 15 Jun 2009 15:45:39 +0200
Subject: MacPorts .mp_* files
In-Reply-To: <180F7E20-0AE6-4F1F-89BD-D92B6274E8D7@macports.org>
References: <867387cd0906150255r7e7313f0y4d771fc9d77ce622@mail.gmail.com>
	<180F7E20-0AE6-4F1F-89BD-D92B6274E8D7@macports.org>
Message-ID: <867387cd0906150645t4a590acbwab9b891fa723c35d@mail.gmail.com>

2009/6/15 Ryan Schmidt <ryandesign at macports.org>:
> When you use the -f flag to force a port install because some files were in
> the way, the files that were in the way get renamed with a .mp_* extension.
> You're probably safe deleting these files.

Ah yes, now I remember... a while ago I had to force-install perl5.8
for some reason. That's probably it. Thanks!

Cheers,
Wouter

-- 
Murphy's Law is recursive.
Washing your car to make it rain doesn't work.

From dweber at macports.org  Mon Jun 15 15:05:12 2009
From: dweber at macports.org (Darren Weber)
Date: Mon, 15 Jun 2009 15:05:12 -0700
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <70082B35-E9EF-4D12-982C-15B17C8C9B6B@macports.org>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
	<4A2E7D76.10500@macports.org>
	<b808b3510906091336v59bc5c5cnbea2cf34d937472c@mail.gmail.com>
	<D4C2C9E9-8044-41E4-B210-99868D528E59@macports.org>
	<70082B35-E9EF-4D12-982C-15B17C8C9B6B@macports.org>
Message-ID: <b808b3510906151505jaa23664k4842f61c9c732c72@mail.gmail.com>

On Tue, Jun 9, 2009 at 5:32 PM, Ryan Schmidt <ryandesign at macports.org>wrote:

> On Jun 9, 2009, at 17:07, Jeremy Huddleston wrote:
>
>  On Jun 9, 2009, at 13:36, Darren Weber wrote:
>>
>>  What's the recommended series of command lines for that?
>>>
>>
>> Here's what I did:
>>
>> cd /opt/local/var/macports/software
>> /bin/ls -1d * > ~/todo.mp
>> cd
>> sudo mv /opt/local /var/tmp/old_macports
>>
>
> Moving /opt/local aside is not sufficient to uninstall MacPorts. See proper
> uninstall instructions here:
>
> http://trac.macports.org/wiki/FAQ#HowdoIremoveoruninstallMacPorts
>
>
>  cd src/macports/trunk/base
>> ./configure && make && sudo make install
>> for f in $(cat todo.mp ); do [[ -d /opt/local/var/macports/software/$f ]]
>> || sudo port -v install $f; done
>>
>> I'm sure there's something ports option to do that, but /shrug...
>>
>
> MacPorts doesn't include a command to help you rebuild an entire
> installation like this. This is unfortunate and makes it a rather involved
> process. But since upgrading to a new major OS version is a task users don't
> perform often, I don't think any work has gone into making this easier.
>
>
> I think the key to solving this would be to have MacPorts record more
> information in the registry about each port that was installed, including
> what version of Mac OS X it was done on, with what version of Xcode, and
> even record several of the settings from macports.conf that were in effect
> at the time. Then we can make "port outdated" recognize that if the current
> OS is a major version later than the one a port was installed with, the port
> needs to be rebuilt.
>
>
Interesting suggestion.  Does the receipt include the variants installed?
Is this process likely to be available in 1.8?

Take care, Darren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090615/c6724780/attachment.html>

From dweber at macports.org  Mon Jun 15 15:26:49 2009
From: dweber at macports.org (Darren Weber)
Date: Mon, 15 Jun 2009 15:26:49 -0700
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <25C36B12-63E2-44EE-9741-FAB0EDD932EA@macports.org>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
	<Pine.LNX.4.64.0906090827400.18688@joust.gpcc.itd.umich.edu>
	<25C36B12-63E2-44EE-9741-FAB0EDD932EA@macports.org>
Message-ID: <b808b3510906151526w2d79f2e3h4b19cf7dc4f96ec3@mail.gmail.com>

On Tue, Jun 9, 2009 at 5:45 AM, vincent habchi <vince at macports.org> wrote:

> Le 9 juin 09 ? 14:32, Kurt Hillig a ?crit :
>
>  On the other hand I recently upgraded from 10.4 to 10.5 and my machine was
>> horribly unstable until I blew away the MacPorts install.  I'm not sure why
>> this was, and I didn't have the time or gumption to run a lot of
>> diagnostics, so it could well be that something less drastic would have
>> sufficed.
>>
>
> When you upgrade, the libraries change, so you may have to recompile some
> of your bricks. For example, when SL will be out, we'll have, at least, a
> 64-bit API to QuickTime, so we'll be able to compile WxWindows safely in
> 64-bit mode. But maybe also the old AGL will vanished, and all ports that
> are based on it will have to be rebuild, etc.
>
>
Ah, right.

There will be changes to the default compiler in xcode, with an upgrade to a
newer version of gcc and some performance improvements with llvm.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090615/899a4445/attachment.html>

From kuraaku.deibiddo at gmail.com  Mon Jun 15 19:18:55 2009
From: kuraaku.deibiddo at gmail.com (David Clark)
Date: Mon, 15 Jun 2009 22:18:55 -0400
Subject: boost fails to compile on Leopard PPC
Message-ID: <33531acd0906151918h7e33c2f6gc38a4a69c497f463@mail.gmail.com>

I've attempted to build boost twice now, once via 'port upgrade
installed', and once after removing it, cleaning it, and building it
anew...both failed, with similar errors:

[root at entropy ~]# port install boost
--->  Fetching boost
--->  Verifying checksum(s) for boost
--->  Extracting boost
--->  Applying patches to boost
--->  Configuring boost
--->  Building boost
Error: Target org.macports.build returned: shell command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/boost_1_39_0"
&& bjam -j1 --toolset=darwin --debug-configuration
--ignore-site-config --user-config=user-config.jam --without-python
--without-mpi -sBZIP2_INCLUDE=/opt/local/include
-sBZIP2_LIBPATH=/opt/local/lib -sZLIB_INCLUDE=/opt/local/include
-sZLIB_LIBPATH=/opt/local/lib " returned error 1
Command output:
./boost/spirit/home/support/iterators/multi_pass.hpp:151: warning:
'boost::spirit::multi_pass<std::pair<boost::wave::cpplexer::impl::lex_iterator_functor_shim<token_type>,
boost::wave::cpplexer::lex_input_interface<token_type>*>,
boost::spirit::multi_pass_policies::default_policy<boost::spirit::multi_pass_policies::ref_counted,
boost::spirit::multi_pass_policies::no_check,
boost::spirit::multi_pass_policies::split_functor_input,
boost::spirit::multi_pass_policies::split_std_deque> >::shared' will
be initialized after
./boost/spirit/home/support/iterators/multi_pass.hpp:82: warning:
base 'boost::spirit::multi_pass_policies::default_policy<boost::spirit::multi_pass_policies::ref_counted,
boost::spirit::multi_pass_policies::no_check,
boost::spirit::multi_pass_policies::split_functor_input,
boost::spirit::multi_pass_policies::split_std_deque>::unique<std::pair<boost::wave::cpplexer::impl::lex_iterator_functor_shim<token_type>,
boost::wave::cpplexer::lex_input_interface<token_type>*> >'
./boost/spirit/home/support/iterators/multi_pass.hpp:81: warning:
when initialized here
darwin.compile.c++
bin.v2/libs/wave/build/darwin-4.0.1/debug/instantiate_cpp_literalgrs.o
darwin.compile.c++
bin.v2/libs/wave/build/darwin-4.0.1/debug/instantiate_defined_grammar.o
./boost/spirit/home/support/iterators/multi_pass.hpp: In copy
constructor 'boost::spirit::multi_pass<T, Policies>::multi_pass(const
boost::spirit::multi_pass<T, Policies>&) [with T =
std::pair<boost::wave::cpplexer::impl::lex_iterator_functor_shim<token_type>,
boost::wave::cpplexer::lex_input_interface<token_type>*>, Policies =
boost::spirit::multi_pass_policies::default_policy<boost::spirit::multi_pass_policies::ref_counted,
boost::spirit::multi_pass_policies::no_check,
boost::spirit::multi_pass_policies::split_functor_input,
boost::spirit::multi_pass_policies::split_std_deque>]':
./boost/wave/cpplexer/cpp_lex_iterator.hpp:170:   instantiated from
'static boost::spirit::classic::parse_info<typename
boost::wave::grammars::defined_grammar_gen<LexIteratorT>::iterator2_type>
boost::wave::grammars::defined_grammar_gen<LexIteratorT>::parse_operator_defined(const
boost::wave::util::unput_queue_iterator<LexIteratorT, typename
LexIteratorT::token_type, std::list<typename LexIteratorT::token_type,
boost::fast_pool_allocator<typename LexIteratorT::token_type,
boost::default_user_allocator_new_delete,
boost::details::pool::default_mutex, 32u> > >&, const
boost::wave::util::unput_queue_iterator<LexIteratorT, typename
LexIteratorT::token_type, std::list<typename LexIteratorT::token_type,
boost::fast_pool_allocator<typename LexIteratorT::token_type,
boost::default_user_allocator_new_delete,
boost::details::pool::default_mutex, 32u> > >&, std::list<typename
LexIteratorT::token_type, boost::fast_pool_allocator<typename
LexIteratorT::token_type, boost::default_user_allocator_new_delete,
boost::details::pool::default_mutex, 32u> >&) [with LexIteratorT =
lexer_type]'
libs/wave/src/instantiate_defined_grammar.cpp:41:   instantiated from here
./boost/spirit/home/support/iterators/multi_pass.hpp:151: warning:
'boost::spirit::multi_pass<std::pair<boost::wave::cpplexer::impl::lex_iterator_functor_shim<token_type>,
boost::wave::cpplexer::lex_input_interface<token_type>*>,
boost::spirit::multi_pass_policies::default_policy<boost::spirit::multi_pass_policies::ref_counted,
boost::spirit::multi_pass_policies::no_check,
boost::spirit::multi_pass_policies::split_functor_input,
boost::spirit::multi_pass_policies::split_std_deque> >::shared' will
be initialized after
./boost/spirit/home/support/iterators/multi_pass.hpp:82: warning:
base 'boost::spirit::multi_pass_policies::default_policy<boost::spirit::multi_pass_policies::ref_counted,
boost::spirit::multi_pass_policies::no_check,
boost::spirit::multi_pass_policies::split_functor_input,
boost::spirit::multi_pass_policies::split_std_deque>::unique<std::pair<boost::wave::cpplexer::impl::lex_iterator_functor_shim<token_type>,
boost::wave::cpplexer::lex_input_interface<token_type>*> >'
./boost/spirit/home/support/iterators/multi_pass.hpp:81: warning:
when initialized here
darwin.compile.c++
bin.v2/libs/wave/build/darwin-4.0.1/debug/instantiate_predef_macros.o
./boost/spirit/home/support/iterators/multi_pass.hpp: In copy
constructor 'boost::spirit::multi_pass<T, Policies>::multi_pass(const
boost::spirit::multi_pass<T, Policies>&) [with T =
std::pair<boost::wave::cpplexer::impl::lex_iterator_functor_shim<token_type>,
boost::wave::cpplexer::lex_input_interface<token_type>*>, Policies =
boost::spirit::multi_pass_policies::default_policy<boost::spirit::multi_pass_policies::ref_counted,
boost::spirit::multi_pass_policies::no_check,
boost::spirit::multi_pass_policies::split_functor_input,
boost::spirit::multi_pass_policies::split_std_deque>]':
./boost/wave/cpplexer/cpp_lex_iterator.hpp:170:   instantiated from
'static boost::spirit::classic::tree_parse_info<IteratorT,
boost::spirit::classic::node_val_data_factory<boost::spirit::classic::nil_t>,
boost::spirit::classic::nil_t>
boost::wave::grammars::predefined_macros_grammar_gen<LexIteratorT>::parse_predefined_macro(const
LexIteratorT&, const LexIteratorT&) [with LexIteratorT = lexer_type]'
libs/wave/src/instantiate_predef_macros.cpp:41:   instantiated from here
./boost/spirit/home/support/iterators/multi_pass.hpp:151: warning:
'boost::spirit::multi_pass<std::pair<boost::wave::cpplexer::impl::lex_iterator_functor_shim<token_type>,
boost::wave::cpplexer::lex_input_interface<token_type>*>,
boost::spirit::multi_pass_policies::default_policy<boost::spirit::multi_pass_policies::ref_counted,
boost::spirit::multi_pass_policies::no_check,
boost::spirit::multi_pass_policies::split_functor_input,
boost::spirit::multi_pass_policies::split_std_deque> >::shared' will
be initialized after
./boost/spirit/home/support/iterators/multi_pass.hpp:82: warning:
base 'boost::spirit::multi_pass_policies::default_policy<boost::spirit::multi_pass_policies::ref_counted,
boost::spirit::multi_pass_policies::no_check,
boost::spirit::multi_pass_policies::split_functor_input,
boost::spirit::multi_pass_policies::split_std_deque>::unique<std::pair<boost::wave::cpplexer::impl::lex_iterator_functor_shim<token_type>,
boost::wave::cpplexer::lex_input_interface<token_type>*> >'
./boost/spirit/home/support/iterators/multi_pass.hpp:81: warning:
when initialized here
darwin.compile.c++
bin.v2/libs/wave/build/darwin-4.0.1/debug/instantiate_re2c_lexer.o
darwin.compile.c++
bin.v2/libs/wave/build/darwin-4.0.1/debug/instantiate_re2c_lexer_str.o
darwin.compile.c++ bin.v2/libs/wave/build/darwin-4.0.1/debug/token_ids.o
darwin.compile.c++
bin.v2/libs/wave/build/darwin-4.0.1/debug/wave_config_constant.o
common.mkdir bin.v2/libs/wave/build/darwin-4.0.1/debug/cpplexer
common.mkdir bin.v2/libs/wave/build/darwin-4.0.1/debug/cpplexer/re2clex
darwin.compile.c++
bin.v2/libs/wave/build/darwin-4.0.1/debug/cpplexer/re2clex/aq.o
darwin.compile.c++
bin.v2/libs/wave/build/darwin-4.0.1/debug/cpplexer/re2clex/cpp_re.o
darwin.link.dll
bin.v2/libs/wave/build/darwin-4.0.1/debug/libboost_wave-xgcc40-d-1_39.dylib
...failed updating 3 targets...
...skipped 143 targets...
...updated 886 targets...

Error: Status 1 encountered during processing.

...does anyone have any suggestions on how to fix this, if possible?

Thanks in advance,

david

From n.oxyde at gmail.com  Mon Jun 15 19:57:39 2009
From: n.oxyde at gmail.com (nox)
Date: Tue, 16 Jun 2009 04:57:39 +0200
Subject: boost fails to compile on Leopard PPC
In-Reply-To: <33531acd0906151918h7e33c2f6gc38a4a69c497f463@mail.gmail.com>
References: <33531acd0906151918h7e33c2f6gc38a4a69c497f463@mail.gmail.com>
Message-ID: <7467C228-13E4-4076-9C0F-271EFD50366E@gmail.com>

Please paste the full output of sudo port -d build boost.

Le 16 juin 09 ? 04:18, David Clark a ?crit :

> I've attempted to build boost twice now, once via 'port upgrade
> installed', and once after removing it, cleaning it, and building it
> anew...both failed, with similar errors:
> <snip/>


From frstan at bellsouth.net  Mon Jun 15 21:51:54 2009
From: frstan at bellsouth.net (William Davis)
Date: Tue, 16 Jun 2009 00:51:54 -0400
Subject: boost fails to compile on Leopard PPC
In-Reply-To: <33531acd0906151918h7e33c2f6gc38a4a69c497f463@mail.gmail.com>
References: <33531acd0906151918h7e33c2f6gc38a4a69c497f463@mail.gmail.com>
Message-ID: <FC0853B3-B062-4A5D-974C-0053D671A0C6@bellsouth.net>


On Jun 15, 2009, at 10:18 PM, David Clark wrote:

> I've attempted to build boost twice now, once via 'port upgrade
> installed', and once after removing it, cleaning it, and building it
> anew...both failed, with similar errors:
>
> [root at entropy ~]# port install boost
> --->  Fetching boost
> --->  Verifying checksum(s) for boost
> --->  Extracting boost
> --->  Applying patches to boost
> --->  Configuring boost
> --->  Building boost
> Error: Target org.macports.build returned: shell command " cd
> "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_devel_boost/work/boost_1_39_0"

/snip/
> /cpplexer/re2clex/cpp_re.o
> darwin.link.dll
> bin.v2/libs/wave/build/darwin-4.0.1/debug/libboost_wave-xgcc40- 
> d-1_39.dylib
> ...failed updating 3 targets...
> ...skipped 143 targets...
> ...updated 886 targets...
>
> Error: Status 1 encountered during processing.
>
> ...does anyone have any suggestions on how to fix this, if possible?
>
> Thanks in advance,
>
> david


built for me...

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From mc at macports.org  Mon Jun 15 03:02:24 2009
From: mc at macports.org (Marc Chantreux)
Date: Mon, 15 Jun 2009 12:02:24 +0200
Subject: Koha via macports
In-Reply-To: <4A3583C9.1010504@macports.org>
References: <469B32D1-E771-4129-8DE7-E8AEDBFC327F@mac.com>
	<4A3583C9.1010504@macports.org>
Message-ID: <20090615100224.GA5971@auckland.lan>

hello,

i read more and more mails about koha on macports so 

- i cc my last answer to the list (hope that it's a good idea)
- i redirected mc.koha-fr.org to 
    http://www.tinybox.net/content/state-koha-macports
- i'll publish my "plan for koha on macports" on my blog soon (yeah! i
  really had one).


On Mon, Jun 15, 2009 at 01:12:09AM +0200, Rainer M?ller wrote:
> As far as I know the domain mc.koha-fr.org (although unreachable at the
> moment for me) is maintained by Marc Chantreux, so I put him to CC in
> this mail.

I apologize! please read:
http://www.tinybox.net/content/state-koha-macports

I really have to document and i will soon! i'll push instructions
directly in the koha sources (i have permission from the koha RM for
this). I will also post soon about my "plan for koha macports". 

> > To get DBD::mysql to install

i have no mac there (that's the major reason i don't put my work on the
trunk) but i'm pretty sure there is a macport for that! please search
for it and install this way! 

port search mysql | grep p5 

should give you clues 

> > If there is anything I can do to help test, or document let me know.

OMG! Yesssss! Please
- stop your install now 
- back to a fresh state if possible 
- wait for my doc (this week, i'm almost able to promise) 
- report problems reading it and following instructions 

regards

From kuraaku.deibiddo at gmail.com  Mon Jun 15 22:46:23 2009
From: kuraaku.deibiddo at gmail.com (David Clark)
Date: Tue, 16 Jun 2009 01:46:23 -0400
Subject: boost fails to compile on Leopard PPC
In-Reply-To: <7467C228-13E4-4076-9C0F-271EFD50366E@gmail.com>
References: <33531acd0906151918h7e33c2f6gc38a4a69c497f463@mail.gmail.com>
	<7467C228-13E4-4076-9C0F-271EFD50366E@gmail.com>
Message-ID: <33531acd0906152246l46c71dd6jfb4323ce36727d94@mail.gmail.com>

On Mon, Jun 15, 2009 at 10:57 PM, nox <n.oxyde at gmail.com> wrote:

> Please paste the full output of sudo port -d build boost.


DEBUG: Found port in file:///opt/local/var/macports/sources/
rsync.macports.org/release/ports/devel/boost
DEBUG: Changing to port directory: /opt/local/var/macports/sources/
rsync.macports.org/release/ports/devel/boost
DEBUG: setting option os.universal_supported to yes
DEBUG: org.macports.load registered provides 'load', a pre-existing
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a
pre-existing procedure. Target override will not be provided
DEBUG: universal variant already exists, so not adding the default one
DEBUG: Requested variant powerpc is not provided by port boost.
DEBUG: Requested variant darwin is not provided by port boost.
DEBUG: Requested variant macosx is not provided by port boost.
DEBUG: Found port in file:///opt/local/var/macports/sources/
rsync.macports.org/release/ports/archivers/zlib
DEBUG: Changing to port directory: /opt/local/var/macports/sources/
rsync.macports.org/release/ports/archivers/zlib
DEBUG: setting option os.universal_supported to yes
DEBUG: org.macports.load registered provides 'load', a pre-existing
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a
pre-existing procedure. Target override will not be provided
DEBUG: adding the default universal variant
DEBUG: Requested variant powerpc is not provided by port zlib.
DEBUG: Requested variant darwin is not provided by port zlib.
DEBUG: Requested variant macosx is not provided by port zlib.
DEBUG: Searching for dependency: zlib
DEBUG: Found Dependency: receipt exists for zlib
DEBUG: Found port in file:///opt/local/var/macports/sources/
rsync.macports.org/release/ports/archivers/bzip2
DEBUG: Changing to port directory: /opt/local/var/macports/sources/
rsync.macports.org/release/ports/archivers/bzip2
DEBUG: setting option os.universal_supported to yes
DEBUG: org.macports.load registered provides 'load', a pre-existing
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a
pre-existing procedure. Target override will not be provided
DEBUG: universal variant already exists, so not adding the default one
DEBUG: Requested variant powerpc is not provided by port bzip2.
DEBUG: Requested variant macosx is not provided by port bzip2.
DEBUG: Executing variant darwin provides darwin
DEBUG: Searching for dependency: bzip2
DEBUG: Found Dependency: receipt exists for bzip2
DEBUG: Found port in file:///opt/local/var/macports/sources/
rsync.macports.org/release/ports/devel/boost-jam
DEBUG: Changing to port directory: /opt/local/var/macports/sources/
rsync.macports.org/release/ports/devel/boost-jam
DEBUG: setting option os.universal_supported to yes
DEBUG: org.macports.load registered provides 'load', a pre-existing
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a
pre-existing procedure. Target override will not be provided
DEBUG: adding the default universal variant
DEBUG: Requested variant powerpc is not provided by port boost-jam.
DEBUG: Requested variant darwin is not provided by port boost-jam.
DEBUG: Requested variant macosx is not provided by port boost-jam.
DEBUG: Searching for dependency: boost-jam
DEBUG: Found Dependency: receipt exists for boost-jam
DEBUG: Executing org.macports.main (boost)
DEBUG: Skipping completed org.macports.fetch (boost)
DEBUG: Skipping completed org.macports.checksum (boost)
DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
DEBUG: Skipping completed org.macports.extract (boost)
DEBUG: Skipping completed org.macports.patch (boost)
DEBUG: Skipping completed org.macports.configure (boost)
--->  Building boost
DEBUG: Executing proc-pre-org.macports.build-build-0
DEBUG: Executing org.macports.build (boost)
DEBUG: port allows a parallel build
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'
DEBUG: Assembled command: 'cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/boost_1_39_0"
&& bjam -j1 --toolset=darwin --debug-configuration --ignore-site-config
--user-config=user-config.jam --without-python --without-mpi
-sBZIP2_INCLUDE=/opt/local/include -sBZIP2_LIBPATH=/opt/local/lib
-sZLIB_INCLUDE=/opt/local/include -sZLIB_LIBPATH=/opt/local/lib'
notice: found boost-build.jam at
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/boost_1_39_0/boost-build.jam
notice: loading Boost.Build from
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/boost_1_39_0/tools/build/v2
notice: Loading explicitly specified user configuration file:

/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/boost_1_39_0/user-config.jam
notice: Searching
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/boost_1_39_0
for user-config configuration file user-config.jam .
notice: Loading user-config configuration file user-config.jam from
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/boost_1_39_0/user-config.jam
.
notice: [cmdline-cfg] Detected command-line request for darwin: toolset=
darwin version=
notice: [cmdline-cfg] toolset darwin not previously configured; attempting
to auto-configure now
notice: will use 'g++' for darwin, condition <toolset>darwin-4.0.1
notice: using strip :: <toolset>darwin-4.0.1 :: /usr/bin/strip
notice: using archiver :: <toolset>darwin-4.0.1 :: /usr/bin/libtool
notice: available sdk :: <toolset>darwin-4.0.1/<macosx-version>10.4 ::
/Developer/SDKs/MacOSX10.4u.sdk
notice: available sdk :: <toolset>darwin-4.0.1/<macosx-version>10.5 ::
/Developer/SDKs/MacOSX10.5.sdk
notice: [cmdline-cfg] adding toolset=darwin to the build request.
notice: iostreams: using prebuilt zlib
notice: iostreams: using prebuilt bzip2

Building C++ Boost.

After the build, the headers will be located at


/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/boost_1_39_0

The libraries will be located at


/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/boost_1_39_0/stage/lib

Use 'bjam install --prefix=<path>' if you wish to install headers and
libraries to a different location and remove the source tree.

warning: Graph library does not contain optional GraphML reader.
note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the
note: directories containing the Expat headers and libraries, respectively.
warning: Building Boost.Regex with the optional Unicode/ICU support
disabled.
note: Please refer to the Boost.Regex documentation for more information
note: this is a strictly optional feature.
...patience...
...patience...
...patience...
...found 5123 targets...
...updating 146 targets...
darwin.compile.c++
bin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi/has_long_double_support.o
libs/math/build/has_long_double_support.cpp:9:2: error: #error "long double
support is not supported by Boost.Math on this Plaform: the long double
version of the TR1 library will not be built."

    "g++"  -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall
-dynamic -no-cpp-precomp -gdwarf-2 -Wno-long-double -fPIC
-DBOOST_ALL_NO_LIB=1 -DNDEBUG  -I"." -c -o
"bin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi/has_long_double_support.o"
"libs/math/build/has_long_double_support.cpp"

...failed darwin.compile.c++
bin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi/has_long_double_support.o...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>acoshl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>asinhl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>atanhl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>cbrtl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>copysignl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>erfcl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>erfl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>expm1l.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>fmaxl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>fminl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>fpclassifyl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>hypotl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>lgammal.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>llroundl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>log1pl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>lroundl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>nextafterl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>nexttowardl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>roundl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>tgammal.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>truncl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>libboost_math_c99l-xgcc40-mt-1_39.dylib
for lack of
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>acoshl.o...
...skipped <pstage/lib>libboost_math_c99l-xgcc40-mt-1_39.dylib for lack of
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>libboost_math_c99l-xgcc40-mt-1_39.dylib...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>assoc_laguerrel.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>assoc_legendrel.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>betal.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>comp_ellint_1l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>comp_ellint_2l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>comp_ellint_3l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>cyl_bessel_il.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>cyl_bessel_jl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>cyl_bessel_kl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>cyl_neumannl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>ellint_1l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>ellint_2l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>ellint_3l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>expintl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>hermitel.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>laguerrel.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>legendrel.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>riemann_zetal.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>sph_bessell.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>sph_legendrel.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>sph_neumannl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>libboost_math_tr1l-xgcc40-mt-1_39.dylib
for lack of
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>assoc_laguerrel.o...
...skipped <pstage/lib>libboost_math_tr1l-xgcc40-mt-1_39.dylib for lack of
<pbin.v2/libs/math/build/darwin-4.0.1/release/threading-multi>libboost_math_tr1l-xgcc40-mt-1_39.dylib...
...skipped <pstage/lib>libboost_math_c99l-xgcc40-mt.dylib for lack of
<pstage/lib>libboost_math_c99l-xgcc40-mt-1_39.dylib...
...skipped <pstage/lib>libboost_math_tr1l-xgcc40-mt.dylib for lack of
<pstage/lib>libboost_math_tr1l-xgcc40-mt-1_39.dylib...
darwin.compile.c++
bin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi/has_long_double_support.o
libs/math/build/has_long_double_support.cpp:9:2: error: #error "long double
support is not supported by Boost.Math on this Plaform: the long double
version of the TR1 library will not be built."

    "g++"  -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall
-no-cpp-precomp -gdwarf-2 -Wno-long-double  -DBOOST_ALL_NO_LIB=1 -DNDEBUG
-I"." -c -o
"bin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi/has_long_double_support.o"
"libs/math/build/has_long_double_support.cpp"

...failed darwin.compile.c++
bin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi/has_long_double_support.o...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>assoc_laguerrel.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>assoc_legendrel.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>betal.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>comp_ellint_1l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>comp_ellint_2l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>comp_ellint_3l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>cyl_bessel_il.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>cyl_bessel_jl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>cyl_bessel_kl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>cyl_neumannl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>ellint_1l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>ellint_2l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>ellint_3l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>expintl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>hermitel.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>laguerrel.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>legendrel.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>riemann_zetal.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>sph_bessell.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>sph_legendrel.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>sph_neumannl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>libboost_math_tr1l-xgcc40-mt-1_39.a
for lack of
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>assoc_laguerrel.o...
...skipped <pstage/lib>libboost_math_tr1l-xgcc40-mt-1_39.a for lack of
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>libboost_math_tr1l-xgcc40-mt-1_39.a...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>acoshl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>asinhl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>atanhl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>cbrtl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>copysignl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>erfcl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>erfl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>expm1l.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>fmaxl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>fminl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>fpclassifyl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>hypotl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>lgammal.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>llroundl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>log1pl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>lroundl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>nextafterl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>nexttowardl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>roundl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>tgammal.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>truncl.o
for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/release/link-static/threading-multi>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>libboost_math_c99l-xgcc40-mt-1_39.a
for lack of
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>acoshl.o...
...skipped <pstage/lib>libboost_math_c99l-xgcc40-mt-1_39.a for lack of
<pbin.v2/libs/math/build/darwin-4.0.1/release/link-static/threading-multi>libboost_math_c99l-xgcc40-mt-1_39.a...
...skipped <pstage/lib>libboost_math_tr1l-xgcc40-mt.a for lack of
<pstage/lib>libboost_math_tr1l-xgcc40-mt-1_39.a...
...skipped <pstage/lib>libboost_math_c99l-xgcc40-mt.a for lack of
<pstage/lib>libboost_math_c99l-xgcc40-mt-1_39.a...
darwin.compile.c++
bin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug/has_long_double_support.o
libs/math/build/has_long_double_support.cpp:9:2: error: #error "long double
support is not supported by Boost.Math on this Plaform: the long double
version of the TR1 library will not be built."

    "g++"  -ftemplate-depth-128 -O0 -fno-inline -Wall -g -dynamic
-no-cpp-precomp -gdwarf-2 -Wno-long-double -fPIC  -DBOOST_ALL_NO_LIB=1
-I"." -c -o
"bin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug/has_long_double_support.o"
"libs/math/build/has_long_double_support.cpp"

...failed darwin.compile.c++
bin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug/has_long_double_support.o...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>assoc_laguerrel.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>assoc_legendrel.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>betal.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>comp_ellint_1l.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>comp_ellint_2l.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>comp_ellint_3l.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>cyl_bessel_il.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>cyl_bessel_jl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>cyl_bessel_kl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>cyl_neumannl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>ellint_1l.o for lack
of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>ellint_2l.o for lack
of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>ellint_3l.o for lack
of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>expintl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>hermitel.o for lack
of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>laguerrel.o for lack
of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>legendrel.o for lack
of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>riemann_zetal.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>sph_bessell.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>sph_legendrel.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>sph_neumannl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/debug>libboost_math_tr1l-xgcc40-d-1_39.dylib
for lack of <pbin.v2/libs/math/build/darwin-4.0.1/debug>assoc_laguerrel.o...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>acoshl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>asinhl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>atanhl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>cbrtl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>copysignl.o for lack
of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>erfcl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>erfl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>expm1l.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>fmaxl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>fminl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>fpclassifyl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>hypotl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>lgammal.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>llroundl.o for lack
of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>log1pl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>lroundl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>nextafterl.o for lack
of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>nexttowardl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>roundl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>tgammal.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>truncl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/debug>libboost_math_c99l-xgcc40-d-1_39.dylib
for lack of <pbin.v2/libs/math/build/darwin-4.0.1/debug>acoshl.o...
...failed updating 3 targets...
...skipped 143 targets...
Error: Target org.macports.build returned: shell command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/boost_1_39_0"
&& bjam -j1 --toolset=darwin --debug-configuration --ignore-site-config
--user-config=user-config.jam --without-python --without-mpi
-sBZIP2_INCLUDE=/opt/local/include -sBZIP2_LIBPATH=/opt/local/lib
-sZLIB_INCLUDE=/opt/local/include -sZLIB_LIBPATH=/opt/local/lib " returned
error 1
Command output: ...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/debug>legendrel.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>riemann_zetal.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>sph_bessell.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>sph_legendrel.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>sph_neumannl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/debug>libboost_math_tr1l-xgcc40-d-1_39.dylib
for lack of <pbin.v2/libs/math/build/darwin-4.0.1/debug>assoc_laguerrel.o...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>acoshl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>asinhl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>atanhl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>cbrtl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>copysignl.o for lack
of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>erfcl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>erfl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>expm1l.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>fmaxl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>fminl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>fpclassifyl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>hypotl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>lgammal.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>llroundl.o for lack
of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>log1pl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>lroundl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>nextafterl.o for lack
of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>nexttowardl.o for
lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>roundl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>tgammal.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped <pbin.v2/libs/math/build/darwin-4.0.1/debug>truncl.o for lack of
<pbin.v2/libs/math/build/has_long_double_support.test/darwin-4.0.1/debug>has_long_double_support.test...
...skipped
<pbin.v2/libs/math/build/darwin-4.0.1/debug>libboost_math_c99l-xgcc40-d-1_39.dylib
for lack of <pbin.v2/libs/math/build/darwin-4.0.1/debug>acoshl.o...
...failed updating 3 targets...
...skipped 143 targets...

Warning: the following items did not execute (for boost): org.macports.build
Error: Status 1 encountered during processing.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090616/ec90b17f/attachment.html>

From ryandesign at macports.org  Tue Jun 16 03:16:33 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 16 Jun 2009 05:16:33 -0500
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <b808b3510906151505jaa23664k4842f61c9c732c72@mail.gmail.com>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
	<4A2E7D76.10500@macports.org>
	<b808b3510906091336v59bc5c5cnbea2cf34d937472c@mail.gmail.com>
	<D4C2C9E9-8044-41E4-B210-99868D528E59@macports.org>
	<70082B35-E9EF-4D12-982C-15B17C8C9B6B@macports.org>
	<b808b3510906151505jaa23664k4842f61c9c732c72@mail.gmail.com>
Message-ID: <E0BD11B3-75B4-45B4-87FE-F93308323A0D@macports.org>

On Jun 15, 2009, at 17:05, Darren Weber wrote:

>> MacPorts doesn't include a command to help you rebuild an entire  
>> installation like this. This is unfortunate and makes it a rather  
>> involved process. But since upgrading to a new major OS version is  
>> a task users don't perform often, I don't think any work has gone  
>> into making this easier.
>>
>>
>> I think the key to solving this would be to have MacPorts record  
>> more information in the registry about each port that was  
>> installed, including what version of Mac OS X it was done on, with  
>> what version of Xcode, and even record several of the settings  
>> from macports.conf that were in effect at the time. Then we can  
>> make "port outdated" recognize that if the current OS is a major  
>> version later than the one a port was installed with, the port  
>> needs to be rebuilt.
>>
>
> Interesting suggestion.  Does the receipt include the variants  
> installed?

Yes; you can bunzip2 a port's receipt and look at it in a text editor  
if you want to see what's in it. But all it seems to contain now is  
the variants that were selected, the files that got installed, and  
some info copied out of the portfile, including its name, version,  
revision, description, etc.

> Is this process likely to be available in 1.8?

I wouldn't count on it, since it's just an idea at this point, and  
there has been no code written yet. And we do want to get 1.8 out the  
door quickly now, since Snow Leopard is in developer hands, and it  
requires 1.8.

Just getting the info (Mac OS X version, Xcode version, build machine  
arch, universal archs, etc?) stored in the receipt shouldn't be hard  
and could perhaps occur for 1.8 already. And then later we can  
rewrite "port outdated" so it makes use of this information.



From ryandesign at macports.org  Tue Jun 16 03:18:35 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 16 Jun 2009 05:18:35 -0500
Subject: port install gnat-gcc
In-Reply-To: <CE33F78C-E679-4A8F-8EEA-8ED592FB7673@macports.org>
References: <C030B322-9742-4589-A259-D185CB3B713B@free.fr>
	<4A326895.4050709@users.sourceforge.net>
	<E5413A52-CE7B-4FE7-86A8-2AC7523F91AB@free.fr>
	<4A338554.4040602@macports.org>
	<CE33F78C-E679-4A8F-8EEA-8ED592FB7673@macports.org>
Message-ID: <A9698F62-9A97-4C9C-9716-82A5A261E2A5@macports.org>


On Jun 15, 2009, at 00:36, Boey Maun Suang wrote:

> If it's of any interest to anyone, I've been having a go at  
> creating a port that builds in the recommended way by downloading a  
> bootstrap compiler and uses that to build GCC with Ada support, as  
> the ghc port does.  (Because of the way that GCC builds and  
> installs itself with absolute path references, the only way that I  
> can see to get that to work would be to have the bootstrap built  
> for installation into a temporary subdirectory of /var/tmp, have  
> that build and install GCC with Ada support on the local machine,  
> and then delete the bootstrap compiler -- though that may mean that  
> it won't work with trace mode on).

Why /var/tmp and not ${destroot}?



From ryandesign at macports.org  Tue Jun 16 03:38:27 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 16 Jun 2009 05:38:27 -0500
Subject: dbus
In-Reply-To: <811D0B03-3894-4876-894F-3CB6177006C2@free.fr>
References: <F9D8A859-E3BD-4AD6-91CD-DB4EC0CDCC7D@free.fr>
	<D84A8471-F8BD-40E8-A313-5C4FE81D5978@macports.org>
	<22DF0311-111E-43EB-996F-2B8A518A4591@free.fr>
	<7AC8D49B-A86A-473E-8A4A-8E2DD3E95B28@macports.org>
	<811D0B03-3894-4876-894F-3CB6177006C2@free.fr>
Message-ID: <0EE2D8CF-D70B-4355-A4CD-2CD154285C82@macports.org>

On Jun 14, 2009, at 09:56, Thomas De Contes wrote:

> Le 14 juin 09 ? 02:20, Ryan Schmidt a ?crit :
>
>> On Jun 13, 2009, at 18:43, Thomas De Contes wrote:
>>
>>>> dbus wants to install a startupitem so you need to either use  
>>>> sudo to install it, or use the no_startupitem variant.
>>>
>>> thank you :-)
>>>
>>> well, is it possible to make MacPorts to automatically switch to  
>>> the appropriate variant, in a such case ?
>>
>> No,
>
> i was not spoking about "do it right now", but rather "is it  
> possible to improve MacPorts, so it will be able to do it later"
> possibly with adding an option to ./configure or to port command,  
> to allow it to do so
>
> still no ?

dbus, apache2 and apache20 are the only ports that have a  
no_startupitem variant. vnc and tightvnc have similar no_server  
variants, but I think that's all. So I don't think we should invest  
time in changing MacPorts base for something that would only be used  
by five ports.


>> but if you are certain you never want any port to install a  
>> startup item, you can set the startup item type to none as Josh  
>> explained.
>
> the problem is that i remove macports.conf in my script (see my  
> last post in "python25")
>
> it can't be set via ./configure, can it ?

I don't see a configure switch for that, no. Most of the things you  
can set in macports.conf cannot be set by configure switches. Rather  
than add configure switches, we should probably add code to upgrade a  
macports.conf.



From n.oxyde at gmail.com  Tue Jun 16 07:32:32 2009
From: n.oxyde at gmail.com (nox)
Date: Tue, 16 Jun 2009 16:32:32 +0200
Subject: boost fails to compile on Leopard PPC
In-Reply-To: <FC0853B3-B062-4A5D-974C-0053D671A0C6@bellsouth.net>
References: <33531acd0906151918h7e33c2f6gc38a4a69c497f463@mail.gmail.com>
	<FC0853B3-B062-4A5D-974C-0053D671A0C6@bellsouth.net>
Message-ID: <0EFB5913-4258-425D-9757-D2768E8EDF9A@gmail.com>

It built, but you are not on PPC ;)

Le 16 juin 09 ? 06:51, William Davis a ?crit :

>
> On Jun 15, 2009, at 10:18 PM, David Clark wrote:
>
>> <snip/>
>
>
> built for me...
>
> William Davis
> frstanATbellsouthDOTnet
> Mac OS X.5.7 Darwin 9.7.0
> XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
> Mac Mini Intel Duo @ 1.86 GHz
>
> Mundus vult decepi, ego non
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From h8spawn at googlemail.com  Tue Jun 16 09:14:02 2009
From: h8spawn at googlemail.com (=?UTF-8?B?Uy4gR8O8bnRoZXI=?=)
Date: Tue, 16 Jun 2009 18:14:02 +0200
Subject: Error building ghc 6.10.3
Message-ID: <e4302e380906160914n64fc9fe8j4734261ac30faf01@mail.gmail.com>

Hello,

I'm trying to install ghc 6.10.3 for quite a while now on my
system (Mac OS X Tiger, Intel, Xcode 2.5) but I keep getting
the error:

Preprocessing library ghc-6.10.3...
/usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: can't locate file for: -lgmp

during the build phase. I went so far as to do:

sudo port -f uninstall installed
sudo rm -rf /opt/ /Library/Tcl/macports1.0/
/Library/Receipts/MacPorts*.pkg ~/.macports/

and reinstall MacPorts from scratch.
I'm reluctant to file a bug report because the last time I filed
one, it was an error on my side and not a bug in the ports
system and since a few bugs with this error message have
been filed but have been considered fixed, I presume there
is a high probability that I messed up. So I would like to ask
for pointers on where to look for things in the system which
might lead to such an error message, and which can be fixed
by myself.

Thanks in advance
Stephan G?nther
---------------------------------------------------------------------------

From h8spawn at googlemail.com  Tue Jun 16 09:19:52 2009
From: h8spawn at googlemail.com (=?UTF-8?B?Uy4gR8O8bnRoZXI=?=)
Date: Tue, 16 Jun 2009 18:19:52 +0200
Subject: Problems with ghc 6.10.3
Message-ID: <e4302e380906160919t463430c8kfcb6c951d2d24e0c@mail.gmail.com>

Hello,

I'm trying to install ghc 6.10.3 for quite a while now on my
system (Mac OS X Tiger, Intel, Xcode 2.5) but I keep getting
the error:

Preprocessing library ghc-6.10.3...
/usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: can't locate file for: -lgmp

during the build phase. I went so far as to do:

sudo port -f uninstall installed
sudo rm -rf /opt/ /Library/Tcl/macports1.0/
/Library/Receipts/MacPorts*.pkg ~/.macports/

and reinstall MacPorts from scratch.
I'm reluctant to file a bug report because the last time I filed
one, it was an error on my side and not a bug in the ports
system and since a few bugs with this error message have
been filed but have been considered fixed, I presume there
is a high probability that I messed up. So I would like to ask
for pointers on where to look for things in the system which
might lead to such an error message, and which can be fixed
by myself.

Thanks in advance
Stephan G?nther

From kuraaku.deibiddo at gmail.com  Tue Jun 16 12:54:00 2009
From: kuraaku.deibiddo at gmail.com (David Clark)
Date: Tue, 16 Jun 2009 15:54:00 -0400
Subject: boost fails to compile on Leopard PPC
In-Reply-To: <0EFB5913-4258-425D-9757-D2768E8EDF9A@gmail.com>
References: <33531acd0906151918h7e33c2f6gc38a4a69c497f463@mail.gmail.com>
	<FC0853B3-B062-4A5D-974C-0053D671A0C6@bellsouth.net>
	<0EFB5913-4258-425D-9757-D2768E8EDF9A@gmail.com>
Message-ID: <33531acd0906161254w57420ba9r642fdd8479ace068@mail.gmail.com>

On Tue, Jun 16, 2009 at 10:32 AM, nox <n.oxyde at gmail.com> wrote:

> It built, but you are not on PPC ;)


Actually, yes I am:

[root at entropy ~]# uname -a
Darwin entropy 9.7.0 Darwin Kernel Version 9.7.0: Tue Mar 31 22:54:29 PDT
2009; root:xnu-1228.12.14~1/RELEASE_PPC Power Macintosh
[root at entropy ~]# arch
ppc

entropy is a dual-2.5GHz G5 PowerMac.

Anyone have any clue how to get boost to install?

Thanks in advance,

david
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090616/42381779/attachment.html>

From n.oxyde at gmail.com  Tue Jun 16 13:00:03 2009
From: n.oxyde at gmail.com (nox)
Date: Tue, 16 Jun 2009 22:00:03 +0200
Subject: boost fails to compile on Leopard PPC
In-Reply-To: <33531acd0906161254w57420ba9r642fdd8479ace068@mail.gmail.com>
References: <33531acd0906151918h7e33c2f6gc38a4a69c497f463@mail.gmail.com>
	<FC0853B3-B062-4A5D-974C-0053D671A0C6@bellsouth.net>
	<0EFB5913-4258-425D-9757-D2768E8EDF9A@gmail.com>
	<33531acd0906161254w57420ba9r642fdd8479ace068@mail.gmail.com>
Message-ID: <8A611088-74A8-41C8-99E0-372134C9DE25@gmail.com>

You are, but I was replying to William.

Concerning your problem, I know where it comes from, I'm looking into  
it.
The problem comes from Boost not handling double double on PPC.

Le 16 juin 09 ? 21:54, David Clark a ?crit :

> On Tue, Jun 16, 2009 at 10:32 AM, nox <n.oxyde at gmail.com> wrote:
> It built, but you are not on PPC ;)
>
> Actually, yes I am:
>
> [root at entropy ~]# uname -a
> Darwin entropy 9.7.0 Darwin Kernel Version 9.7.0: Tue Mar 31  
> 22:54:29 PDT 2009; root:xnu-1228.12.14~1/RELEASE_PPC Power Macintosh
> [root at entropy ~]# arch
> ppc
>
> entropy is a dual-2.5GHz G5 PowerMac.
>
> Anyone have any clue how to get boost to install?
>
> Thanks in advance,
>
> david
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From frstan at bellsouth.net  Tue Jun 16 13:11:59 2009
From: frstan at bellsouth.net (William Davis)
Date: Tue, 16 Jun 2009 16:11:59 -0400
Subject: boost fails to compile on Leopard PPC
In-Reply-To: <33531acd0906161254w57420ba9r642fdd8479ace068@mail.gmail.com>
References: <33531acd0906151918h7e33c2f6gc38a4a69c497f463@mail.gmail.com>
	<FC0853B3-B062-4A5D-974C-0053D671A0C6@bellsouth.net>
	<0EFB5913-4258-425D-9757-D2768E8EDF9A@gmail.com>
	<33531acd0906161254w57420ba9r642fdd8479ace068@mail.gmail.com>
Message-ID: <014665D0-7BC1-4348-A184-F7FD2759D77E@bellsouth.net>


On Jun 16, 2009, at 3:54 PM, David Clark wrote:

> On Tue, Jun 16, 2009 at 10:32 AM, nox <n.oxyde at gmail.com> wrote:
> It built, but you are not on PPC ;)
>
> Actually, yes I am:
>
> [root at entropy ~]# uname -a
> Darwin entropy 9.7.0 Darwin Kernel Version 9.7.0: Tue Mar 31  
> 22:54:29 PDT 2009; root:xnu-1228.12.14~1/RELEASE_PPC Power Macintosh
> [root at entropy ~]# arch
> ppc
>
> entropy is a dual-2.5GHz G5 PowerMac.
>
> Anyone have any clue how to get boost to install?
>
> Thanks in advance,
>
> david
>

Actually David, that remark was intended for me.....

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090616/f70f09c1/attachment.html>

From n.oxyde at gmail.com  Tue Jun 16 16:04:07 2009
From: n.oxyde at gmail.com (nox)
Date: Wed, 17 Jun 2009 01:04:07 +0200
Subject: boost fails to compile on Leopard PPC
In-Reply-To: <8A611088-74A8-41C8-99E0-372134C9DE25@gmail.com>
References: <33531acd0906151918h7e33c2f6gc38a4a69c497f463@mail.gmail.com>
	<FC0853B3-B062-4A5D-974C-0053D671A0C6@bellsouth.net>
	<0EFB5913-4258-425D-9757-D2768E8EDF9A@gmail.com>
	<33531acd0906161254w57420ba9r642fdd8479ace068@mail.gmail.com>
	<8A611088-74A8-41C8-99E0-372134C9DE25@gmail.com>
Message-ID: <AE260FA5-AFBC-4238-AB04-C290AF063063@gmail.com>

Should be fixed by r52445.

Le 16 juin 09 ? 22:00, nox a ?crit :

> You are, but I was replying to William.
>
> Concerning your problem, I know where it comes from, I'm looking  
> into it.
> The problem comes from Boost not handling double double on PPC.
>
> Le 16 juin 09 ? 21:54, David Clark a ?crit :
>
>> On Tue, Jun 16, 2009 at 10:32 AM, nox <n.oxyde at gmail.com> wrote:
>> It built, but you are not on PPC ;)
>>
>> Actually, yes I am:
>>
>> [root at entropy ~]# uname -a
>> Darwin entropy 9.7.0 Darwin Kernel Version 9.7.0: Tue Mar 31  
>> 22:54:29 PDT 2009; root:xnu-1228.12.14~1/RELEASE_PPC Power Macintosh
>> [root at entropy ~]# arch
>> ppc
>>
>> entropy is a dual-2.5GHz G5 PowerMac.
>>
>> Anyone have any clue how to get boost to install?
>>
>> Thanks in advance,
>>
>> david
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>


From ryandesign at macports.org  Tue Jun 16 16:34:17 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 16 Jun 2009 18:34:17 -0500
Subject: port install gnat-gcc
In-Reply-To: <E9129CE8-BEC9-4299-9817-A84DF347B21E@me.com>
References: <C030B322-9742-4589-A259-D185CB3B713B@free.fr>
	<4A326895.4050709@users.sourceforge.net>
	<E5413A52-CE7B-4FE7-86A8-2AC7523F91AB@free.fr>
	<4A338554.4040602@macports.org>
	<CE33F78C-E679-4A8F-8EEA-8ED592FB7673@macports.org>
	<A9698F62-9A97-4C9C-9716-82A5A261E2A5@macports.org>
	<E9129CE8-BEC9-4299-9817-A84DF347B21E@me.com>
Message-ID: <51609353-10BD-4A44-8DA7-325F62606473@macports.org>


On Jun 16, 2009, at 06:32, Martin Krischik wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Am 16.06.2009 um 12:18 schrieb Ryan Schmidt:
>
>>
>> On Jun 15, 2009, at 00:36, Boey Maun Suang wrote:
>>
>>> If it's of any interest to anyone, I've been having a go at  
>>> creating a port that builds in the recommended way by downloading  
>>> a bootstrap compiler and uses that to build GCC with Ada support,  
>>> as the ghc port does.  (Because of the way that GCC builds and  
>>> installs itself with absolute path references, the only way that  
>>> I can see to get that to work would be to have the bootstrap  
>>> built for installation into a temporary subdirectory of /var/tmp,  
>>> have that build and install GCC with Ada support on the local  
>>> machine, and then delete the bootstrap compiler -- though that  
>>> may mean that it won't work with trace mode on).
>>
>> Why /var/tmp and not ${destroot}?
>
> Maybe he can't write to /opt. I often compile from / to /var/tmp on  
> systems when I don't have root access.

If you can't write to /opt/local, you wouldn't put your MacPorts  
there, and destroot is inside wherever your MacPorts prefix is, so  
that's not a reason not to use destroot.


From ryandesign at macports.org  Tue Jun 16 21:06:21 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 16 Jun 2009 23:06:21 -0500
Subject: Error building ghc 6.10.3
In-Reply-To: <e4302e380906160914n64fc9fe8j4734261ac30faf01@mail.gmail.com>
References: <e4302e380906160914n64fc9fe8j4734261ac30faf01@mail.gmail.com>
Message-ID: <8ED71FE9-762C-4C17-A81C-6C0B5071B241@macports.org>

On Jun 16, 2009, at 11:14, S. G?nther wrote:

> I'm trying to install ghc 6.10.3 for quite a while now on my
> system (Mac OS X Tiger, Intel, Xcode 2.5) but I keep getting
> the error:
>
> Preprocessing library ghc-6.10.3...
> /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: can't locate file  
> for: -lgmp
>
> during the build phase. I went so far as to do:
>
> sudo port -f uninstall installed
> sudo rm -rf /opt/ /Library/Tcl/macports1.0/
> /Library/Receipts/MacPorts*.pkg ~/.macports/
>
> and reinstall MacPorts from scratch.

Be aware that the MacPorts prefix is /opt/local, not /opt. There may  
be other things in /opt, outside of /opt/local, which are not related  
to MacPorts. Correct uninstall instructions are in the FAQ:

http://trac.macports.org/wiki/FAQ#HowdoIremoveoruninstallMacPorts


> I'm reluctant to file a bug report because the last time I filed
> one, it was an error on my side and not a bug in the ports
> system and since a few bugs with this error message have
> been filed but have been considered fixed, I presume there
> is a high probability that I messed up. So I would like to ask
> for pointers on where to look for things in the system which
> might lead to such an error message, and which can be fixed
> by myself.

Don't worry, I get the error too. This is the ticket:

http://trac.macports.org/ticket/19747

The ticket was for an error when prefix is not /opt/local, and I  
fixed that, but curiously, when prefix is /opt/local, as it is for  
most users, the problem remains.



From cjsvance at gmail.com  Wed Jun 17 05:54:20 2009
From: cjsvance at gmail.com (Christopher Vance)
Date: Wed, 17 Jun 2009 22:54:20 +1000
Subject: scons
Message-ID: <ace45c0a0906170554r31c084e6t5079d7b5cade7b39@mail.gmail.com>

Is there a simple way to enable scons to use Python 2.6 instead of
requiring 2.5?

-- 
Christopher Vance

From face at CentosPrime.COM  Wed Jun 17 08:00:11 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Wed, 17 Jun 2009 08:00:11 -0700
Subject: Python errors from Apache?
Message-ID: <8E65437A-D8A3-499E-87BC-0973EFEF3216@centosprime.com>

I noticed that my apache error log ''/opt/local/apache2/logs/ 
error_log'' now shows many errors like the following

Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
'import site' failed; use -v for traceback

It's kind of hard to figure out where these are coming from, and what  
to do about them

$ uname -a
Darwin mac.centosprime.com 9.7.0 Darwin Kernel Version 9.7.0: Tue Mar  
31 22:52:17 PDT 2009; root:xnu-1228.12.14~1/RELEASE_I386 i386

$ python_select -s
python25

sorry for the long list - not sure which ports are relevant to the  
problem

$ port installed
The following ports are currently installed:
   a52dec @0.7.4_0 (active)
   adns @1.4_0 (active)
   adodb @5.04_0 (active)
   analog @6.0_0 (active)
   apache-ant @1.7.1_0 (active)
   apache2 @2.2.11_0+darwin_9 (active)
   apachetop @0.12.5_0 (active)
   apr @1.3.5_0 (active)
   apr-util @1.3.7_0 (active)
   aspell @0.60.6_1+macosx (active)
   aspell-dict-en @6.0_0 (active)
   aspell-dict-it @0.53_0 (active)
   atk @1.26.0_1 (active)
   AtomicParsley @0.9.0_0 (active)
   audiofile @0.2.6_2 (active)
   autoconf @2.63_0 (active)
   autoconf213 @2.13_1 (active)
   automake @1.11_0 (active)
   base64 @1.3_0 (active)
   bash-completion @1.0_1 (active)
   bison @2.4.1_0 (active)
   bzip2 @1.0.5_2 (active)
   cairo @1.8.6_4+macosx
   cairo @1.8.8_0+macosx (active)
   ccache @2.4_2 (active)
   cdparanoia @10.2_0 (active)
   cidr @2.3.2_0 (active)
   clucene @0.9.20_0 (active)
   commons-beanutils @1.8.0_0 (active)
   commons-codec @1.3_1 (active)
   commons-collections @3.2.1_0 (active)
   commons-daemon @1.0.1_0 (active)
   commons-dbcp @1.2.2_0 (active)
   commons-digester @1.8_0 (active)
   commons-el @1.0_1 (active)
   commons-fileupload @1.2.1_0 (active)
   commons-httpclient @3.1_0 (active)
   commons-io @1.4_0 (active)
   commons-launcher @1.1_0 (active)
   commons-logging @1.1.1_0 (active)
   commons-modeler @2.0.1_0 (active)
   commons-pool @1.4_0 (active)
   coreutils @7.4_0 (active)
   cppunit @1.12.1_0 (active)
   csv2xml @0.6_0 (active)
   ctags @5.7_0 (active)
   curl @7.19.5_0+doc+sftp_scp+ssl (active)
   curl-ca-bundle @7.19.5_0 (active)
   cyrus-sasl2 @2.1.22_0+kerberos
   cyrus-sasl2 @2.1.23_0+kerberos (active)
   db44 @4.4.20_1 (active)
   db46 @4.6.21_5 (active)
   dbus @1.2.12_5
   dbus @1.2.14_0 (active)
   dbus-glib @0.80_0 (active)
   desktop-file-utils @0.15_1 (active)
   dirac @1.0.2_0 (active)
   dnstracer @1.9_0 (active)
   docbook-xml @5.0_0 (active)
   docbook-xml-4.1.2 @4.1.2_1 (active)
   docbook-xml-4.2 @4.2_0 (active)
   docbook-xml-4.3 @4.3_0 (active)
   docbook-xml-4.4 @4.4_0 (active)
   docbook-xml-4.5 @4.5_0 (active)
   docbook-xml-5.0 @5.0_0 (active)
   docbook-xsl @1.75.0_0
   docbook-xsl @1.75.1_0 (active)
   dom4j @1.6.1_1 (active)
   dos2unix @3.1_1 (active)
   doxygen @1.5.9_0 (active)
   emacs @22.3_1+atsui+carbon (active)
   esound @0.2.41_1 (active)
   expat @2.0.1_0 (active)
   expect @5.43.0_4 (active)
   faac @1.28_1 (active)
   faad2 @2.6.1_1 (active)
   ffmpeg @0.5_2 (active)
   flac @1.2.1_0+darwin_i386 (active)
   flex @2.5.35_0 (active)
   fontconfig @2.6.0_2+macosx (active)
   fortune @6.2.0-RELEASE_0 (active)
   freetype @2.3.9_0+macosx (active)
   gawk @3.1.6_0 (active)
   gconf @2.26.2_0 (active)
   gd2 @2.0.35_5 (active)
   gdbm @1.8.3_1 (active)
   getopt @1.1.4_1 (active)
   gettext @0.17_4 (active)
   ghostscript @8.64_3 (active)
   giflib @4.1.6_1 (active)
   glib2 @2.20.3_0 (active)
   glut @3.7_3 (active)
   gmake @3.81_0 (active)
   gmp @4.3.1_0 (active)
   gnome-common @2.26.0_0 (active)
   gnome-doc-utils @0.16.1_0 (active)
   gnome-mime-data @2.18.0_3 (active)
   gnome-vfs @2.24.1_0 (active)
   gperf @3.0.4_0 (active)
   graphviz @2.22.2_0+macosx
   graphviz @2.24.0_0+macosx (active)
   gsed @4.2_0 (active)
   gst-plugins-base @0.10.23_0 (active)
   gstreamer @0.10.23_0 (active)
   gtk-doc @1.11_0 (active)
   gtk2 @2.16.1_4+x11
   gtk2 @2.16.2_0+x11 (active)
   gzip @1.3.12_0 (active)
   hamcrest-core @1.1_2
   hamcrest-core @1.2_0 (active)
   help2man @1.36.4_1 (active)
   html2text @1.3.2a_3 (active)
   id3lib @3.8.3_0 (active)
   id3v2 @0.1.11_1 (active)
   ImageMagick @6.5.2-9_0+no_x11+q16 (active)
   imap-uw @2007_1 (active)
   intltool @0.40.6_0 (active)
   iso-codes @3.5_0
   iso-codes @3.10_0 (active)
   jakarta-bcel @5.1_1 (active)
   jakarta-log4j @1.2.15_0 (active)
   jakarta-regexp @1.4_0 (active)
   jakarta-taglibs-standard-11 @1.1.2_1 (active)
   jasper @1.900.1_4 (active)
   jaxen @1.1-beta-9_0 (active)
   jdom @1.0_0 (active)
   jpeg @6b_3 (active)
   junit @4.6_0
   junit @4.6_1 (active)
   lame @3.98.2_0 (active)
   libart_lgpl @2.3.20_0 (active)
   libdvdcss @1.2.10_0 (active)
   libdvdread @4.1.3_2+libdvdcss (active)
   libexif @0.6.17_0 (active)
   libgdiplus @2.4_0 (active)
   libiconv @1.12_2
   libiconv @1.13_0 (active)
   libidl @0.8.13_0 (active)
   libmcrypt @2.5.8_1 (active)
   libmikmod @3.2.0-beta2_1 (active)
   libmp4v2 @1.5.0.1_0 (active)
   libogg @1.1.3_2 (active)
   liboil @0.3.16_0 (active)
   libpcap @1.0.0_0 (active)
   libpixman @0.14.0_0 (active)
   libpng @1.2.35_0
   libpng @1.2.37_0 (active)
   librsync @0.9.7_1 (active)
   libsdl @1.2.13_6 (active)
   libsdl_image @1.2.7_0 (active)
   libsdl_mixer @1.2.8_1 (active)
   libssh2 @1.0_0
   libssh2 @1.1_0 (active)
   libtheora @1.0_0+darwin_9_i386 (active)
   libtool @2.2.6a_0 (active)
   libvorbis @1.2.0_1 (active)
   libxml2 @2.7.3_0 (active)
   libxslt @1.1.24_2 (active)
   lighttpd @1.4.20_0
   lighttpd @1.4.22_0 (active)
   lynx @2.8.6rel.5_1+ssl (active)
   lzmautils @4.32.7_1 (active)
   m4 @1.4.13_0+with_default_names (active)
   macfuse @1.7_1 (active)
   makedepend @1.0.1_0 (active)
   mercurial @1.2.1_1 (active)
   mesa @7.4_1+hw_render
   mesa @7.4.2_0+hw_render (active)
   mg @20090107_0 (active)
   mhash @0.9.9.9_0 (active)
   mod_python25 @3.3.1_3+universal (active)
   mono @2.4_0+darwin_9 (active)
   mx4j @3.0.1_0 (active)
   mysql-connector-java @5.0.7_0 (active)
   mysql5 @5.0.83_0
   mysql5-devel @5.1.34_0+server
   mysql5-devel @5.1.35_0 (active)
   mysql5-devel @5.1.35_0+server
   mysql5-server-devel @5.1.35_1 (active)
   ncurses @5.7_0 (active)
   ncursesw @5.7_0 (active)
   neon @0.28.4_0 (active)
   netpbm @10.26.61_0 (active)
   nmap @4.76_0 (active)
   openmotif @2.3.1-1_2 (active)
   openssl @0.9.8k_0 (active)
   orbit2 @2.14.17_0 (active)
   p5-compress-raw-zlib @2.015_0 (active)
   p5-compress-zlib @2.015_0 (active)
   p5-crypt-ssleay @0.57_0 (active)
   p5-dbi @1.607_0 (active)
   p5-html-parser @3.60_0 (active)
   p5-html-tableextract @2.10_0 (active)
   p5-html-tagset @3.20_0 (active)
   p5-io-compress-base @2.015_0 (active)
   p5-io-compress-zlib @2.015_0 (active)
   p5-libwww-perl @5.826_0 (active)
   p5-locale-gettext @1.05_0 (active)
   p5-mime-base64 @3.07_0 (active)
   p5-uri @1.37_0
   p5-uri @1.38_0 (active)
   p5-xml-parser @2.36_0 (active)
   p7zip @4.65_0
   p7zip @9.04_0 (active)
   palm-db-tools @0.3.6_1 (active)
   pango @1.24.2_0+macosx (active)
   pcre @7.9_0 (active)
   perl5.8 @5.8.9_3 (active)
   php5 @5.2.9_2+apache2+macosx+mysql5+pear
   php5 @5.2.9_3+apache2+macosx+mysql5+pear (active)
   phpicalendar @2.24_0 (active)
   pkgconfig @0.23_1 (active)
   policykit @0.9_0 (active)
   popt @1.15_0 (active)
   port_cutleaves @0.1.1_0 (active)
   pstree @2.32_0 (active)
   py-markdown @1.7_0 (active)
   py25-beautifulsoup @3.0.7a_0 (active)
   py25-bz2 @2.5.4_1 (active)
   py25-cherrypy3 @3.1.1_0 (active)
   py25-django-devel @0.96.1_1 (active)
   py25-feedparser @4.1_0 (active)
   py25-genshi @0.5.1_0 (active)
   py25-gobject @2.16.1_0+darwin_9
   py25-gobject @2.18.0_0+darwin_9 (active)
   py25-hashlib @2.5.4_1 (active)
   py25-libxml2 @2.6.21_1 (active)
   py25-lxml @2.2_0 (active)
   py25-mysql @1.2.2_0+mysql5 (active)
   py25-numeric @24.2_1+macosx (active)
   py25-paste @1.7.1_0 (active)
   py25-setuptools @0.6c9_0 (active)
   py25-sqlite3 @2.5.4_1 (active)
   py25-xml @0.8.4_0 (active)
   py25-zlib @2.5.4_1 (active)
   python24 @2.4.6_4+darwin_9+macosx (active)
   python25 @2.5.4_4+darwin_9+macosx+universal
   python25 @2.5.4_5+darwin_9+macosx+universal
   python25 @2.5.4_6+darwin_9+macosx+universal (active)
   python26 @2.6.2_2
   python26 @2.6.2_3 (active)
   python_select @0.2.1_0+darwin_9 (active)
   rarian @0.8.1_0 (active)
   readline @6.0.000_1 (active)
   render @0.9.2_0 (active)
   saxpath @1.0_0 (active)
   schroedinger @1.0.7_0 (active)
   serf @0.3.0_0 (active)
   servlet23-api @1_0 (active)
   servlet24-api @5.5.25_0 (active)
   shared-mime-info @0.60_0 (active)
   shorten @3.6.1_0 (active)
   sipcalc @1.1.4_0 (active)
   smpeg @0.4.4_8 (active)
   sqlite3 @3.6.14.2_0 (active)
   subversion @1.6.2_0+bash_completion+mod_dav_svn+no_bdb+tools (active)
   tcl @8.5.6_0 (active)
   texi2html @1.80_0
   texi2html @1.82_0 (active)
   texinfo @4.13_0 (active)
   texlive @2007_6 (active)
   texlive_base @2007_6
   texlive_base @2007_7+motif (active)
   texlive_texmf-full @2007_3 (active)
   texlive_texmf-minimal @2007_2 (active)
   tiff @3.8.2_3+macosx (active)
   tk @8.5.6_1 (active)
   tomcat-native @1.1.14_0 (active)
   tomcat5 @5.5.25_0 (active)
   tree @1.5.2.2_0 (active)
   ttcp @1.10_0 (active)
   urw-fonts @1.0.7pre44_0 (active)
   vms-empire @1.7_0 (active)
   vobcopy @1.1.1_0 (active)
   waitfor @0.5_0 (active)
   watch @3.2.7_0 (active)
   wget @1.11.4_3 (active)
   wtf @20080926_0 (active)
   x264 @20090408_0 (active)
   xalanj @2.7.0_1 (active)
   xbitmaps @1.0.1_1 (active)
   xercesj @2.9.1_0 (active)
   Xft2 @2.1.13_1 (active)
   xmlcatmgr @2.2_1 (active)
   xom @1.0_0 (active)
   xorg-applewmproto @1.2.0_0 (active)
   xorg-bigreqsproto @1.0.2_0 (active)
   xorg-compositeproto @0.4_0 (active)
   xorg-damageproto @1.1.0_0 (active)
   xorg-dmxproto @2.2.2_0 (active)
   xorg-dri2proto @1.99.3_0
   xorg-dri2proto @2.0_0
   xorg-dri2proto @2.1_0 (active)
   xorg-evieproto @1.0.2_0 (active)
   xorg-fixesproto @4.0_0 (active)
   xorg-fontcacheproto @0.1.2_0 (active)
   xorg-fontsproto @2.0.2_0 (active)
   xorg-glproto @1.4.10_0 (active)
   xorg-inputproto @1.5.0_0 (active)
   xorg-kbproto @1.0.3_0 (active)
   xorg-libAppleWM @1.2.0_0 (active)
   xorg-libdmx @1.0.2_1 (active)
   xorg-libfontenc @1.0.4_0 (active)
   xorg-libFS @1.0.1_0 (active)
   xorg-libice @1.0.5_0 (active)
   xorg-liblbxutil @1.0.1_0 (active)
   xorg-liboldX @1.0.1_0 (active)
   xorg-libpthread-stubs @0.1_0 (active)
   xorg-libs @20090224_0 (active)
   xorg-libsm @1.1.0_0 (active)
   xorg-libX11 @1.2.1_0 (active)
   xorg-libXau @1.0.4_0 (active)
   xorg-libXaw @1.0.5_0 (active)
   xorg-libxcb @1.3_0+python26 (active)
   xorg-libXcomposite @0.4.0_0 (active)
   xorg-libXcursor @1.1.9_0 (active)
   xorg-libXdamage @1.1.1_0 (active)
   xorg-libXdmcp @1.0.2_0 (active)
   xorg-libXevie @1.0.2_1 (active)
   xorg-libXext @1.0.5_1 (active)
   xorg-libXfixes @4.0.3_0 (active)
   xorg-libXfont @1.4.0_1 (active)
   xorg-libXfontcache @1.0.4_0 (active)
   xorg-libXi @1.2.1_0 (active)
   xorg-libXinerama @1.0.3_0 (active)
   xorg-libxkbfile @1.0.5_0 (active)
   xorg-libxkbui @1.0.2_0 (active)
   xorg-libXmu @1.0.4_0 (active)
   xorg-libXp @1.0.0_2 (active)
   xorg-libXrandr @1.3.0_0 (active)
   xorg-libXres @1.0.3_0 (active)
   xorg-libXScrnSaver @1.1.3_0 (active)
   xorg-libXt @1.0.5_2 (active)
   xorg-libXTrap @1.0.0_1
   xorg-libXTrap @1.0.0_2 (active)
   xorg-libXtst @1.0.3_0 (active)
   xorg-libXv @1.0.4_0 (active)
   xorg-libXvMC @1.0.4_0 (active)
   xorg-libXxf86dga @1.0.2_0 (active)
   xorg-libXxf86misc @1.0.1_1 (active)
   xorg-libXxf86vm @1.0.2_0 (active)
   xorg-printproto @1.0.4_0 (active)
   xorg-randrproto @1.3.0_0 (active)
   xorg-recordproto @1.13.2_0 (active)
   xorg-renderproto @0.9.3_0 (active)
   xorg-resourceproto @1.0.2_0 (active)
   xorg-scrnsaverproto @1.1.0_0 (active)
   xorg-trapproto @3.4.3_0 (active)
   xorg-util-macros @1.2.1_1 (active)
   xorg-videoproto @2.2.2_0 (active)
   xorg-xcb-proto @1.5_0+python26
   xorg-xcb-proto @1.5_1+python26 (active)
   xorg-xcb-util @0.3.5_0 (active)
   xorg-xcmiscproto @1.1.2_0 (active)
   xorg-xextproto @7.0.5_0 (active)
   xorg-xf86bigfontproto @1.1.2_0 (active)
   xorg-xf86dgaproto @2.0.3_0 (active)
   xorg-xf86miscproto @0.9.2_0 (active)
   xorg-xf86vidmodeproto @2.2.2_0 (active)
   xorg-xineramaproto @1.1.2_0 (active)
   xorg-xproto @7.0.15_0 (active)
   xorg-xtrans @1.2.3_0 (active)
   xpm @3.5.7_0 (active)
   xrender @0.9.4_5 (active)
   XviD @1.1.3_1
   XviD @1.2.2_0 (active)
   yasm @0.8.0_0 (active)
   ZendFramework @1.7.4_0 (active)
   zlib @1.2.3_2 (active)

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From jjstickel at vcn.com  Wed Jun 17 11:14:12 2009
From: jjstickel at vcn.com (Jonathan Stickel)
Date: Wed, 17 Jun 2009 12:14:12 -0600
Subject: VTK 5.2 and GL2PS export
Message-ID: <4A393274.5080201@vcn.com>

I'm experiencing a problem using the GL2PS export feature of VTK, where 
VTK was installed via Macports (vtk5 @5.2.1_2+carbon+darwin_8+python). 
When I have a textActor in my render window, e.g. some arbitrary title 
or note, then that text does not show in the exported pdf/eps.

I suspect the problem might be related to the OpenGL library that VTK 
links to, in this case 
/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL since I am 
using the Carbon variant.  Can someone verify that they see this problem 
also?  Any knowledge about how to resolve this?  I am currently on Tiger.

Thanks,
Jonathan

From jeremyhu at macports.org  Wed Jun 17 11:36:31 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Wed, 17 Jun 2009 11:36:31 -0700
Subject: VTK 5.2 and GL2PS export
In-Reply-To: <4A393274.5080201@vcn.com>
References: <4A393274.5080201@vcn.com>
Message-ID: <C922BA9B-A76D-4D31-9B66-9C7E231290C0@macports.org>

Interesting.  We were just talking about some vtk oddities in the x11- 
users and xquartz-dev mailing list.

Check out:
http://www.ctcms.nist.gov/oof/renderingbug

Since you're seeing this purely in carbon, my guess now is that this  
is an issue with either OpenGL.framework (which would mean it's in  
both Tiger and Leopard... which I think isn't too likely) or with VTK  
itself.

On Jun 17, 2009, at 11:14, Jonathan Stickel wrote:

> I'm experiencing a problem using the GL2PS export feature of VTK,  
> where VTK was installed via Macports (vtk5 @5.2.1_2+carbon 
> +darwin_8+python). When I have a textActor in my render window, e.g.  
> some arbitrary title or note, then that text does not show in the  
> exported pdf/eps.
>
> I suspect the problem might be related to the OpenGL library that  
> VTK links to, in this case /System/Library/Frameworks/ 
> OpenGL.framework/Versions/A/OpenGL since I am using the Carbon  
> variant.  Can someone verify that they see this problem also?  Any  
> knowledge about how to resolve this?  I am currently on Tiger.
>
> Thanks,
> Jonathan
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From artie.ziff at gmail.com  Wed Jun 17 21:07:10 2009
From: artie.ziff at gmail.com (Artie Ziff)
Date: Wed, 17 Jun 2009 21:07:10 -0700
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <4A2EE501.4070303@nogas.org>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>	<4A2E7D76.10500@macports.org>	<b808b3510906091336v59bc5c5cnbea2cf34d937472c@mail.gmail.com>	<D4C2C9E9-8044-41E4-B210-99868D528E59@macports.org>
	<4A2EE501.4070303@nogas.org>
Message-ID: <4A39BD6E.3060603@gmail.com>

Scott C. Kennedy wrote:
> You will lose your variants, if you made any custom builds. I keep a
> shell script with the variants and ports that I use up to date, plus I
> keep and compare the "port installed" output from before and after to
> ensure I didn't miss anything.
>   

How is that script organized.?
I'd like to know this methodology.

Cheers!


From artie.ziff at gmail.com  Wed Jun 17 21:15:23 2009
From: artie.ziff at gmail.com (Artie Ziff)
Date: Wed, 17 Jun 2009 21:15:23 -0700
Subject: Announcing: port_upgrade
In-Reply-To: <764C8BB9-D179-4B1B-B637-4E1087FBB57B@tdoan.com>
References: <764C8BB9-D179-4B1B-B637-4E1087FBB57B@tdoan.com>
Message-ID: <4A39BF5B.6090003@gmail.com>

Hello,

It seems I have managed to break my system.
How to recover from a borked upgrade?

Cheers!

####################

$ sudo ./upgrade.sh
full run
Error: port uninstall failed: Registry error: dbus 1.2.12_5 not
registered as installed.
--->  Unable to uninstall gettext 0.17_4, the following ports depend on it:
--->      lzmautils
Error: port uninstall failed: Please uninstall the ports that depend on
gettext first.
Error: port uninstall failed: Registry error: mysql5 5.0.83_0+server not
registered as installed.
Error: port uninstall failed: Registry error: mysql5 5.0.81_0+server not
registered as installed.
Error: port uninstall failed: Registry error: postgresql83 8.3.7_0 not
registered as installed.
Error: port uninstall failed: Registry error: rb-actionwebservice
1.2.6_0 not registered as installed.
Error: port uninstall failed: Registry error: struts 1.2.7_0 not
registered as installed.
Error: port uninstall failed: Registry error: unixODBC 2.2.14_1 not
registered as installed.
Error: port uninstall failed: Registry error: commons-fileupload 1.2.1_0
not registered as installed.
Error: port uninstall failed: Registry error: commons-validator 1.3.1_1
not registered as installed.
Error: port uninstall failed: Registry error:
jakarta-taglibs-standard-11 1.1.2_1 not registered as installed.
Error: port uninstall failed: Registry error: libxslt 1.1.24_2 not
registered as installed.
Error: port uninstall failed: Registry error: rb-actionpack 2.2.2_0 not
registered as installed.
Error: port uninstall failed: Registry error: rb-activerecord 2.2.2_0
not registered as installed.
Error: port uninstall failed: Registry error: commons-digester 1.8_0 not
registered as installed.
Error: port uninstall failed: Registry error: libxml2 2.7.3_0 not
registered as installed.
Error: port uninstall failed: Registry error: rb-activesupport 2.2.2_0
not registered as installed.
Error: port uninstall failed: Registry error: commons-beanutils 1.8.0_0
not registered as installed.
Error: port uninstall failed: Registry error: rb-rubygems 1.3.1_0 not
registered as installed.
Error: port uninstall failed: Registry error: commons-collections
3.2.1_0 not registered as installed.
Error: port uninstall failed: Registry error: ruby
1.8.7-p173_0+thread_hooks not registered as installed.
Error: port uninstall failed: Registry error: ruby
1.8.7-p160_1+thread_hooks not registered as installed.
Error: port uninstall failed: Registry error: junit 4.6_1 not registered
as installed.
Error: port uninstall failed: Registry error: junit 4.6_0 not registered
as installed.
--->  Uninstalling libiconv @1.13_0
--->  Unable to uninstall libiconv 1.12_2, the following ports depend on it:
--->      gettext
--->      lzmautils
Error: port uninstall failed: Please uninstall the ports that depend on
libiconv first.
--->  Deactivating hamcrest-core @1.2_0
--->  Uninstalling hamcrest-core @1.2_0
Error: port uninstall failed: Registry error: hamcrest-core 1.1_2 not
registered as installed.
--->  Fetching hamcrest-core
--->  Verifying checksum(s) for hamcrest-core
--->  Extracting hamcrest-core
--->  Configuring hamcrest-core
--->  Building hamcrest-core
--->  Staging hamcrest-core into destroot
--->  Installing hamcrest-core @1.2_0
--->  Activating hamcrest-core @1.2_0
--->  Cleaning hamcrest-core
--->  Installing libiconv @1.13_0
--->  Activating libiconv @1.13_0
Error: Target org.macports.activate returned: Image error: Another
version of this port (libiconv @1.12_2) is already active.
Error: Status 1 encountered during processing.


and


$ ./port_upgrade -o upgrade.sh
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require': no such file to load -- bz2 (LoadError)
    from
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
`require'
    from /opt/local/port_upgrade/lib/port_upgrade.rb:20
    from
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require'
    from
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
`require'
    from ./port_upgrade:7




From boeyms at macports.org  Thu Jun 18 02:17:39 2009
From: boeyms at macports.org (Boey Maun Suang)
Date: Thu, 18 Jun 2009 19:17:39 +1000
Subject: port install gnat-gcc
In-Reply-To: <A9698F62-9A97-4C9C-9716-82A5A261E2A5@macports.org>
References: <C030B322-9742-4589-A259-D185CB3B713B@free.fr>
	<4A326895.4050709@users.sourceforge.net>
	<E5413A52-CE7B-4FE7-86A8-2AC7523F91AB@free.fr>
	<4A338554.4040602@macports.org>
	<CE33F78C-E679-4A8F-8EEA-8ED592FB7673@macports.org>
	<A9698F62-9A97-4C9C-9716-82A5A261E2A5@macports.org>
Message-ID: <0F909060-156F-4066-B98F-A13ACB1AB22A@macports.org>

Hi Ryan,

On 16/06/2009, at 8:18 PM, Ryan Schmidt wrote:

> On Jun 15, 2009, at 00:36, Boey Maun Suang wrote:
>
>> If it's of any interest to anyone, I've been having a go at  
>> creating a port that builds in the recommended way by downloading a  
>> bootstrap compiler and uses that to build GCC with Ada support, as  
>> the ghc port does.  (Because of the way that GCC builds and  
>> installs itself with absolute path references, the only way that I  
>> can see to get that to work would be to have the bootstrap built  
>> for installation into a temporary subdirectory of /var/tmp, have  
>> that build and install GCC with Ada support on the local machine,  
>> and then delete the bootstrap compiler -- though that may mean that  
>> it won't work with trace mode on).
>
> Why /var/tmp and not ${destroot}?


I know what I want to say, but I'm not sure about the best way to  
explain it, so please ask questions about anything that isn't clear.   
I also apologise for the redundancy if I mention anything that you  
already know about.

Firstly, I just want to make clear that it's the bootstrap compiler  
that I'm talking about extracting into a subdirectory of /var/tmp, for  
use to build and install a new GCC into ${prefix}.  That is, during  
the extract phase, the bootstrap compiler gets extracted into  
subdirectory of /var/tmp, and the source gets extracted into $ 
{workpath} as usual; the configure and build phases will then use the  
bootstrap in /var/tmp to build a new GCC that will be destrooted into $ 
{destroot}${prefix} and finally installed into ${prefix}.

The problem is that the GCC build process requires its final install  
prefix to be an absolute one; configure refuses to accept any relative  
components in the argument to --prefix.  Consequently, all of the path  
references within the files in any GCC build are absolute ones.  This  
includes references to required dynamic libraries, but there are  
probably other path references elsewhere that I haven't yet found  
(e.g. in internal configuration files).  It is the latter that means  
that I cannot be sure that changing the paths to dynamic libraries in  
GCC's executables and dynamic libraries using install_name_tool will  
be sufficient; that could break the compiler in ways that are not easy  
to detect or fix.

Thus, to be sure that a build of GCC can be reliably used as a  
bootstrap compiler, it has to be installed (temporarily) in the same  
absolute location on every machine.  ${destroot} won't work because it  
depends on ${prefix}, which is allowed to vary.  The bootstrap  
compiler also needs to be installed in a place where we can be sure  
that it won't interfere with other parts of the system, and can be  
easily deleted when it's finished with, and as far as I know, /var/tmp  
is the best place for such things.

(Of course, one could theoretically change the GCC build process to  
enable it to accept relative path installations, but I'm confident  
that that would be far more effort than it would be worth.  It's  
certainly beyond my ability and pain threshold.)

Consequently, I can't see any relative location to which we can  
extract a GCC bootstrap, and /var/tmp is the best absolute path that I  
can think of for this purpose.

Incidentally, I used otool on the executables in the current ghc  
bootstrap compiler, and they contain _absolute_ references to /opt/ 
local/lib/libgmp.3.dylib, so for those who try to install MacPorts ghc  
and who have configured ${prefix} to be other than /opt/local, the  
build will either fail due to the non-existence of /opt/local/lib/ 
libgmp.3.dylib, or (in accordance with the dyld(1) man page's  
description of the DYLD_LIBRARY_PATH and DYLD_FALLBACK_LIBRARY_PATH  
variables), it will silently pick up libgmp.3.dylib in another  
location, such as /usr/local/lib, when it is run.  I haven't looked  
into it, but we may find that the ghc bootstrap actually has this same  
problem, just not in such an obvious or severe form.

As always, your thoughts (and those of others on the list) would be  
appreciated.

Kind regards,


Maun Suang

-- 
Boey Maun Suang
Email: boeyms at macports dot org


From sck at nogas.org  Thu Jun 18 06:53:55 2009
From: sck at nogas.org (Scott C. Kennedy)
Date: Thu, 18 Jun 2009 06:53:55 -0700 (PDT)
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <4A39BD6E.3060603@gmail.com>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
	<4A2E7D76.10500@macports.org>
	<b808b3510906091336v59bc5c5cnbea2cf34d937472c@mail.gmail.com>
	<D4C2C9E9-8044-41E4-B210-99868D528E59@macports.org>
	<4A2EE501.4070303@nogas.org> <4A39BD6E.3060603@gmail.com>
Message-ID: <40016.99.171.186.102.1245333235.squirrel@email.powweb.com>

Well, I choose to compile my variants first, like +ipv6, so that any
dependancies don't get hosed. As in, if you need to install "curl +ipv6"
but, another port needs "curl" then if you don't compile the variant
first, then you will compile the non-ipv6 version to satisfy the
dependancy and then have to uninstall/install or "install -f" to install
the variant you want.

So, that's how I organize it.

Scott

On Wed, June 17, 2009 9:07 pm, Artie Ziff wrote:
> Scott C. Kennedy wrote:
>> You will lose your variants, if you made any custom builds. I keep a
>> shell script with the variants and ports that I use up to date, plus I
>> keep and compare the "port installed" output from before and after to
>> ensure I didn't miss anything.
>>
>
> How is that script organized.?
> I'd like to know this methodology.
>
> Cheers!
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>


From drowe at roden.myzen.co.uk  Thu Jun 18 07:21:40 2009
From: drowe at roden.myzen.co.uk (David Rowe)
Date: Thu, 18 Jun 2009 15:21:40 +0100
Subject: GnuGash won't start: The return of gconf/dbus issues.
Message-ID: <4A3A4D74.9080003@roden.myzen.co.uk>

After the latest MacPorts upgrades, my GnuCash installation won't start:

GnuCash brings up alert boxes saying: "Cannot find default values - The 
configuration data used to specify default values for GnuCash cannot be 
found in the default system location. . . " and "An error occurred 
whilst loading or saving configuration information for gnucash . . ."
The terminal log says "Dynamic session lookup supported but failed: 
launchd did not provide a socket path, verify that 
org.freedesktop.dbus-session.plist is loaded!" (this message is repeated 
6 times).

Gramps does eventually startup, but the following appears on the 
terminal log: "Dynamic session lookup supported but failed: launchd did 
not provide a socket path, verify that 
org.freedesktop.dbus-session.plist is loaded!
GConf Error: Failed to contact configuration server; some possible 
causes are that you need to enable TCP/IP networking for ORBit, or you 
have stale NFS locks due to a system crash. See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed 
to get connection to session: Not enough memory)".

Gimp is similar to Gramps - it does start but puts the following message 
in the log: "Dynamic session lookup supported but failed: launchd did 
not provide a socket path, verify that 
org.freedesktop.dbus-session.plist is loaded!
Not enough memory"

In my installation, there is a file called 
org.freedesktop.dbus-session.plist in /opt/local/Library/LaunchAgents

This looks very much like a rerun of the gconf/dbus  incompatibilities 
that caused similar problems towards the end of 2008.

I tried reverting gconf from the current gconf @2.26.2_0 to the previous 
gconf @2.26.1_0 and the problem was still there. I also tried reverting 
to gconf @2.24.0_2 and that also didn't help (though I see now that the 
workaround for the earlier problems was to revert to gconf @2.22.0_0).
(By reverting I mean deactivating the new version and then activating 
the old)

However, reverting dbus from the current dbus @1.2.14_0 to the previous 
dbus @1.2.12_5 seems to make the problem seem to go away (but I have not 
done exhaustive tests).

So: Is this a problem with my installation or are others hitting the 
same issue?
If it a general problem, should I raise a ticket?
Sorry - I am not experienced at raising tickets - so should it for gconf 
or dbus and should it be on Macports or gnome?

Thanks

David Rowe


From drowe at roden.myzen.co.uk  Thu Jun 18 07:40:44 2009
From: drowe at roden.myzen.co.uk (David Rowe)
Date: Thu, 18 Jun 2009 15:40:44 +0100
Subject: GnuGash won't start: The return of gconf/dbus issues - PS
Message-ID: <4A3A51EC.8050702@roden.myzen.co.uk>

Re my previous message:

For the workaround (deactivating dbus @1.2.14_0 and then activating the 
previous dbus @1.2.12_5) - I should have mentioned that you have to 
reboot your system afterwards - as dbus runs a daemon that must be 
restarted with the old version. There may be a more elegant way - but 
that worked for me.

DR

From akiabo at googlemail.com  Thu Jun 18 09:01:55 2009
From: akiabo at googlemail.com (A. Osthoff)
Date: Thu, 18 Jun 2009 18:01:55 +0200
Subject: GnuGash won't start: The return of gconf/dbus issues.
In-Reply-To: <4A3A4D74.9080003@roden.myzen.co.uk>
References: <4A3A4D74.9080003@roden.myzen.co.uk>
Message-ID: <4A3A64F3.4000507@gmail.com>

David Rowe schrieb:

Hi,

> After the latest MacPorts upgrades, my GnuCash installation won't start:
> 
> GnuCash brings up alert boxes saying: "Cannot find default values - The
> configuration data used to specify default values for GnuCash cannot be
> found in the default system location. . . " and "An error occurred
> whilst loading or saving configuration information for gnucash . . ."
> The terminal log says "Dynamic session lookup supported but failed:
> launchd did not provide a socket path, verify that
> org.freedesktop.dbus-session.plist is loaded!" (this message is repeated
> 6 times).
> 
> Gramps does eventually startup, but the following appears on the
> terminal log: "Dynamic session lookup supported but failed: launchd did
> not provide a socket path, verify that
> org.freedesktop.dbus-session.plist is loaded!
> GConf Error: Failed to contact configuration server; some possible
> causes are that you need to enable TCP/IP networking for ORBit, or you
> have stale NFS locks due to a system crash. See
> http://projects.gnome.org/gconf/ for information. (Details -  1: Failed
> to get connection to session: Not enough memory)".
> 
> Gimp is similar to Gramps - it does start but puts the following message
> in the log: "Dynamic session lookup supported but failed: launchd did
> not provide a socket path, verify that
> org.freedesktop.dbus-session.plist is loaded!
> Not enough memory"
> 
> In my installation, there is a file called
> org.freedesktop.dbus-session.plist in /opt/local/Library/LaunchAgents
> 
> This looks very much like a rerun of the gconf/dbus  incompatibilities
> that caused similar problems towards the end of 2008.
> 
> I tried reverting gconf from the current gconf @2.26.2_0 to the previous
> gconf @2.26.1_0 and the problem was still there. I also tried reverting
> to gconf @2.24.0_2 and that also didn't help (though I see now that the
> workaround for the earlier problems was to revert to gconf @2.22.0_0).
> (By reverting I mean deactivating the new version and then activating
> the old)
> 
> However, reverting dbus from the current dbus @1.2.14_0 to the previous
> dbus @1.2.12_5 seems to make the problem seem to go away (but I have not
> done exhaustive tests).
> 
> So: Is this a problem with my installation or are others hitting the
> same issue?

I already pointed this out on the mailing list on June 6th. ;)
I was able to "re"activate gconf 2.24.0_0 to resolve the issue. (The
current dbus is working fine here).

> If it a general problem, should I raise a ticket?

If I recall the previous discussion correctly a ticket has been already
filed. See
http://www.nabble.com/Updated-Gnucash-doesn%27t-handle-preferences-to19831050.html#a19832473

cheers,
	achim

From drowe at roden.myzen.co.uk  Thu Jun 18 09:46:35 2009
From: drowe at roden.myzen.co.uk (David Rowe)
Date: Thu, 18 Jun 2009 17:46:35 +0100
Subject: GnuGash won't start: The return of gconf/dbus issues.
In-Reply-To: <4A3A64F3.4000507@gmail.com>
References: <4A3A4D74.9080003@roden.myzen.co.uk> <4A3A64F3.4000507@gmail.com>
Message-ID: <4A3A6F6B.4050302@roden.myzen.co.uk>

A. Osthoff wrote:
> David Rowe schrieb:
>
> Hi,
>
>   
>> After the latest MacPorts upgrades, my GnuCash installation won't start:
>>
>> . . . . 
>>     
>
> I already pointed this out on the mailing list on June 6th. ;)
> I was able to "re"activate gconf 2.24.0_0 to resolve the issue. (The
> current dbus is working fine here).
>
>   
>> If it a general problem, should I raise a ticket?
>>     
>
> If I recall the previous discussion correctly a ticket has been already
> filed. See
> http://www.nabble.com/Updated-Gnucash-doesn%27t-handle-preferences-to19831050.html#a19832473
>
> cheers,
> 	achim
>
>   
I was aware of the above - I had that problem myself at the end of last 
year, but it seems to have been fixed fixed months ago.

I normally update my system two or three times a week and this new 
version of the problem has only arisen in the last two or three days.
I see that gconf was last updated on 23 May 09, but dbus was last 
updated (to @1.2.14) on 15 June 09 - so it looks to me like it is this 
dbus update that is causing the problem. The symptoms may look like last 
year's problem (i.e. gconf can't talk to dbus) - it it probably has a 
different cause.

DR



From jjstickel at vcn.com  Thu Jun 18 10:19:13 2009
From: jjstickel at vcn.com (Jonathan Stickel)
Date: Thu, 18 Jun 2009 11:19:13 -0600
Subject: VTK 5.2 and GL2PS export
In-Reply-To: <C922BA9B-A76D-4D31-9B66-9C7E231290C0@macports.org>
References: <4A393274.5080201@vcn.com>
	<C922BA9B-A76D-4D31-9B66-9C7E231290C0@macports.org>
Message-ID: <4A3A7711.8080502@vcn.com>

I reinstalled vtk5 with the +x11 variant, and now the vtk rendering 
library is linked to

/opt/local/lib/libGL.1.dylib

However, I still have the same problem of textActors not exporting. 
Labels on axes export fine, though.  I suppose this could be reported 
upstream to VTK.  Maybe I'll try vtk-devel (vtk-5.4) when I have some 
more time and see if the problem persists.

Jonathan


Jeremy Huddleston wrote:
> Interesting.  We were just talking about some vtk oddities in the 
> x11-users and xquartz-dev mailing list.
> 
> Check out:
> http://www.ctcms.nist.gov/oof/renderingbug
> 
> Since you're seeing this purely in carbon, my guess now is that this is 
> an issue with either OpenGL.framework (which would mean it's in both 
> Tiger and Leopard... which I think isn't too likely) or with VTK itself.
> 
> On Jun 17, 2009, at 11:14, Jonathan Stickel wrote:
> 
>> I'm experiencing a problem using the GL2PS export feature of VTK, 
>> where VTK was installed via Macports (vtk5 
>> @5.2.1_2+carbon+darwin_8+python). When I have a textActor in my render 
>> window, e.g. some arbitrary title or note, then that text does not 
>> show in the exported pdf/eps.
>>
>> I suspect the problem might be related to the OpenGL library that VTK 
>> links to, in this case 
>> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL since I 
>> am using the Carbon variant.  Can someone verify that they see this 
>> problem also?  Any knowledge about how to resolve this?  I am 
>> currently on Tiger.
>>
>> Thanks,
>> Jonathan
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> 
> 
> 

From dweber at macports.org  Thu Jun 18 10:27:23 2009
From: dweber at macports.org (Darren Weber)
Date: Thu, 18 Jun 2009 10:27:23 -0700
Subject: VTK 5.2 and GL2PS export
In-Reply-To: <4A3A7711.8080502@vcn.com>
References: <4A393274.5080201@vcn.com>
	<C922BA9B-A76D-4D31-9B66-9C7E231290C0@macports.org>
	<4A3A7711.8080502@vcn.com>
Message-ID: <b808b3510906181027x202d3f4bw7499b0701d1dcc22@mail.gmail.com>

I've done a bit of work on vtk-devel to make some things in the installation
version specific.  I have not tested whether vtk-devel can co-exist with
vtk5.

All the work on vtk-devel was based on the default variants (cocoa shared
wrap) plus testing and examples.  Nothing has been tested extensively, and
very little has been done with x11.

If you have time to run the build and install, I suggest the huge variant,
or no variants at all will give you a default set of variants.

vtk-devel has the variants:
    darwin_9: Platform variant, do not select manually
    huge: provide cocoa data doc examples shared testing wrap database mpi
boost
    data: provide example data in: /opt/local/share/vtk-5.4/data
    doc: provide doxygen documentation in: /opt/local/share/vtk-5.4/doc
    examples: provide VTK examples in: /opt/local/share/vtk-5.4/examples
    shared: build shared libraries (default)
    testing: provide VTK tests in: /opt/local/share/vtk-5.4/testing
    carbon: build with Carbon
    cocoa: build with Cocoa (default)
    x11: build with X11
    wrap: provide java, py26, & tcl
    java: java wrapper
    py25: python 2.5 wrapper
    py26: python 2.6 wrapper
    tcl: tcl wrapper (MacPorts tcl/tk)
    tcl_apple: tcl wrapper (apple tcl/tk framework)
    database: provide all database variants
    mysql5: build the MySQL driver for vtkSQLDatabase
    pgsql83: build the PostgreSQL 8.3 driver for vtkSQLDatabase
    odbc: build the ODBC database interface
    mpi: use message passing interface (mpich2) for parallel support
    boost: use Boost libraries - www.boost.org
    universal: Build for multiple architectures


Regards,
Darren




On Thu, Jun 18, 2009 at 10:19 AM, Jonathan Stickel <jjstickel at vcn.com>wrote:

> I reinstalled vtk5 with the +x11 variant, and now the vtk rendering library
> is linked to
>
> /opt/local/lib/libGL.1.dylib
>
> However, I still have the same problem of textActors not exporting. Labels
> on axes export fine, though.  I suppose this could be reported upstream to
> VTK.  Maybe I'll try vtk-devel (vtk-5.4) when I have some more time and see
> if the problem persists.
>
> Jonathan
>
>
>
> Jeremy Huddleston wrote:
>
>> Interesting.  We were just talking about some vtk oddities in the
>> x11-users and xquartz-dev mailing list.
>>
>> Check out:
>> http://www.ctcms.nist.gov/oof/renderingbug
>>
>> Since you're seeing this purely in carbon, my guess now is that this is an
>> issue with either OpenGL.framework (which would mean it's in both Tiger and
>> Leopard... which I think isn't too likely) or with VTK itself.
>>
>> On Jun 17, 2009, at 11:14, Jonathan Stickel wrote:
>>
>>  I'm experiencing a problem using the GL2PS export feature of VTK, where
>>> VTK was installed via Macports (vtk5 @5.2.1_2+carbon+darwin_8+python). When
>>> I have a textActor in my render window, e.g. some arbitrary title or note,
>>> then that text does not show in the exported pdf/eps.
>>>
>>> I suspect the problem might be related to the OpenGL library that VTK
>>> links to, in this case
>>> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL since I am
>>> using the Carbon variant.  Can someone verify that they see this problem
>>> also?  Any knowledge about how to resolve this?  I am currently on Tiger.
>>>
>>> Thanks,
>>> Jonathan
>>> _______________________________________________
>>> macports-users mailing list
>>> macports-users at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>>
>>
>>
>>
>>  _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090618/866bcd31/attachment.html>

From dweber at macports.org  Thu Jun 18 10:32:56 2009
From: dweber at macports.org (Darren Weber)
Date: Thu, 18 Jun 2009 10:32:56 -0700
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <E0BD11B3-75B4-45B4-87FE-F93308323A0D@macports.org>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
	<4A2E7D76.10500@macports.org>
	<b808b3510906091336v59bc5c5cnbea2cf34d937472c@mail.gmail.com>
	<D4C2C9E9-8044-41E4-B210-99868D528E59@macports.org>
	<70082B35-E9EF-4D12-982C-15B17C8C9B6B@macports.org>
	<b808b3510906151505jaa23664k4842f61c9c732c72@mail.gmail.com>
	<E0BD11B3-75B4-45B4-87FE-F93308323A0D@macports.org>
Message-ID: <b808b3510906181032j57fd58en53a87ad239aac594@mail.gmail.com>

On Tue, Jun 16, 2009 at 3:16 AM, Ryan Schmidt <ryandesign at macports.org>wrote:

> On Jun 15, 2009, at 17:05, Darren Weber wrote:
>
>  MacPorts doesn't include a command to help you rebuild an entire
>>> installation like this. This is unfortunate and makes it a rather involved
>>> process. But since upgrading to a new major OS version is a task users don't
>>> perform often, I don't think any work has gone into making this easier.
>>>
>>>
>>> I think the key to solving this would be to have MacPorts record more
>>> information in the registry about each port that was installed, including
>>> what version of Mac OS X it was done on, with what version of Xcode, and
>>> even record several of the settings from macports.conf that were in effect
>>> at the time. Then we can make "port outdated" recognize that if the current
>>> OS is a major version later than the one a port was installed with, the port
>>> needs to be rebuilt.
>>>
>>>
>> Interesting suggestion.  Does the receipt include the variants installed?
>>
>
> Yes; you can bunzip2 a port's receipt and look at it in a text editor if
> you want to see what's in it. But all it seems to contain now is the
> variants that were selected, the files that got installed, and some info
> copied out of the portfile, including its name, version, revision,
> description, etc.
>
>  Is this process likely to be available in 1.8?
>>
>
> I wouldn't count on it, since it's just an idea at this point, and there
> has been no code written yet. And we do want to get 1.8 out the door quickly
> now, since Snow Leopard is in developer hands, and it requires 1.8.
>
> Just getting the info (Mac OS X version, Xcode version, build machine arch,
> universal archs, etc?) stored in the receipt shouldn't be hard and could
> perhaps occur for 1.8 already. And then later we can rewrite "port outdated"
> so it makes use of this information.
>


I have attended WWDC2009, where I got access to a developer version of Snow
Leopard (and SL server) and the latest Xcode tools bundled with the SDK for
iPhone 3.0.

If I can learn how to create a dual-boot system (so I can hang onto
everything on my Leopard Server), then I may be able to test some things
(any tips on the best way to do this?).  I can't give it a high priority in
my position, but I expect it will have to be done sooner or later for me to
make a move to development on Snow Leopard in Sept.

Take care,
Darren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090618/efda88e9/attachment.html>

From jeremyhu at macports.org  Thu Jun 18 10:46:30 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Thu, 18 Jun 2009 10:46:30 -0700
Subject: VTK 5.2 and GL2PS export
In-Reply-To: <b808b3510906181027x202d3f4bw7499b0701d1dcc22@mail.gmail.com>
References: <4A393274.5080201@vcn.com>
	<C922BA9B-A76D-4D31-9B66-9C7E231290C0@macports.org>
	<4A3A7711.8080502@vcn.com>
	<b808b3510906181027x202d3f4bw7499b0701d1dcc22@mail.gmail.com>
Message-ID: <3A79F75D-E385-4929-B63B-F14508109F0B@macports.org>


On Jun 18, 2009, at 10:27, Darren Weber wrote:

> vtk-devel has the variants:
>    darwin_9: Platform variant, do not select manually
...
>    py25: python 2.5 wrapper
>    py26: python 2.6 wrapper

Shouldn't these be "python2[56]" for consistency sake?

From jeremyhu at macports.org  Thu Jun 18 10:51:14 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Thu, 18 Jun 2009 10:51:14 -0700
Subject: OSX Upgrades: Snow Leopard
In-Reply-To: <b808b3510906181032j57fd58en53a87ad239aac594@mail.gmail.com>
References: <b808b3510906082220i4a94d48emdf1fb1a3a34e59f9@mail.gmail.com>
	<c115fd3c0906090515i6edf7e5fxeac176f0caa5c752@mail.gmail.com>
	<4A2E7D76.10500@macports.org>
	<b808b3510906091336v59bc5c5cnbea2cf34d937472c@mail.gmail.com>
	<D4C2C9E9-8044-41E4-B210-99868D528E59@macports.org>
	<70082B35-E9EF-4D12-982C-15B17C8C9B6B@macports.org>
	<b808b3510906151505jaa23664k4842f61c9c732c72@mail.gmail.com>
	<E0BD11B3-75B4-45B4-87FE-F93308323A0D@macports.org>
	<b808b3510906181032j57fd58en53a87ad239aac594@mail.gmail.com>
Message-ID: <85B2CC05-0DD3-463C-8E8B-88039C2F7A6E@macports.org>


On Jun 18, 2009, at 10:32, Darren Weber wrote:
> I have attended WWDC2009, where I got access to a developer version  
> of Snow
> Leopard (and SL server) and the latest Xcode tools bundled with the  
> SDK for
> iPhone 3.0.
>
> If I can learn how to create a dual-boot system (so I can hang onto
> everything on my Leopard Server), then I may be able to test some  
> things
> (any tips on the best way to do this?).  I can't give it a high  
> priority in
> my position, but I expect it will have to be done sooner or later  
> for me to
> make a move to development on Snow Leopard in Sept.

1) Boot off the DVD.
2) select "Disk Utility" from the "Utilities" menu.
3) Select your disk and click on "Partition"
4) Click on the little "+" at the bottom.  This will "split" your  
Leopard partition and allow you to install SL on a separate partition.

You can then hold down opt at boot to choose your boot disk or install  
something like rEFIt.



From jjstickel at vcn.com  Thu Jun 18 13:02:08 2009
From: jjstickel at vcn.com (Jonathan Stickel)
Date: Thu, 18 Jun 2009 14:02:08 -0600
Subject: VTK 5.2 and GL2PS export
In-Reply-To: <b808b3510906181027x202d3f4bw7499b0701d1dcc22@mail.gmail.com>
References: <4A393274.5080201@vcn.com>	
	<C922BA9B-A76D-4D31-9B66-9C7E231290C0@macports.org>	
	<4A3A7711.8080502@vcn.com>
	<b808b3510906181027x202d3f4bw7499b0701d1dcc22@mail.gmail.com>
Message-ID: <4A3A9D40.9020800@vcn.com>

I found some bugs in the vtk-devel Portfile that hindered me from 
installing on Tiger.  See:

https://trac.macports.org/ticket/20002

Jonathan



Darren Weber wrote:
> 
> I've done a bit of work on vtk-devel to make some things in the 
> installation version specific.  I have not tested whether vtk-devel can 
> co-exist with vtk5.
> 
> All the work on vtk-devel was based on the default variants (cocoa 
> shared wrap) plus testing and examples.  Nothing has been tested 
> extensively, and very little has been done with x11.
> 
> If you have time to run the build and install, I suggest the huge 
> variant, or no variants at all will give you a default set of variants.
> 
> vtk-devel has the variants:
>     darwin_9: Platform variant, do not select manually
>     huge: provide cocoa data doc examples shared testing wrap database 
> mpi boost
>     data: provide example data in: /opt/local/share/vtk-5.4/data
>     doc: provide doxygen documentation in: /opt/local/share/vtk-5.4/doc
>     examples: provide VTK examples in: /opt/local/share/vtk-5.4/examples
>     shared: build shared libraries (default)
>     testing: provide VTK tests in: /opt/local/share/vtk-5.4/testing
>     carbon: build with Carbon
>     cocoa: build with Cocoa (default)
>     x11: build with X11
>     wrap: provide java, py26, & tcl
>     java: java wrapper
>     py25: python 2.5 wrapper
>     py26: python 2.6 wrapper
>     tcl: tcl wrapper (MacPorts tcl/tk)
>     tcl_apple: tcl wrapper (apple tcl/tk framework)
>     database: provide all database variants
>     mysql5: build the MySQL driver for vtkSQLDatabase
>     pgsql83: build the PostgreSQL 8.3 driver for vtkSQLDatabase
>     odbc: build the ODBC database interface
>     mpi: use message passing interface (mpich2) for parallel support
>     boost: use Boost libraries - www.boost.org <http://www.boost.org>
>     universal: Build for multiple architectures
> 
> 
> Regards,
> Darren
> 
> 
> 
> 
> On Thu, Jun 18, 2009 at 10:19 AM, Jonathan Stickel <jjstickel at vcn.com 
> <mailto:jjstickel at vcn.com>> wrote:
> 
>     I reinstalled vtk5 with the +x11 variant, and now the vtk rendering
>     library is linked to
> 
>     /opt/local/lib/libGL.1.dylib
> 
>     However, I still have the same problem of textActors not exporting.
>     Labels on axes export fine, though.  I suppose this could be
>     reported upstream to VTK.  Maybe I'll try vtk-devel (vtk-5.4) when I
>     have some more time and see if the problem persists.
> 
>     Jonathan
> 
> 
> 
>     Jeremy Huddleston wrote:
> 
>         Interesting.  We were just talking about some vtk oddities in
>         the x11-users and xquartz-dev mailing list.
> 
>         Check out:
>         http://www.ctcms.nist.gov/oof/renderingbug
> 
>         Since you're seeing this purely in carbon, my guess now is that
>         this is an issue with either OpenGL.framework (which would mean
>         it's in both Tiger and Leopard... which I think isn't too
>         likely) or with VTK itself.
> 
>         On Jun 17, 2009, at 11:14, Jonathan Stickel wrote:
> 
>             I'm experiencing a problem using the GL2PS export feature of
>             VTK, where VTK was installed via Macports (vtk5
>             @5.2.1_2+carbon+darwin_8+python). When I have a textActor in
>             my render window, e.g. some arbitrary title or note, then
>             that text does not show in the exported pdf/eps.
> 
>             I suspect the problem might be related to the OpenGL library
>             that VTK links to, in this case
>             /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
>             since I am using the Carbon variant.  Can someone verify
>             that they see this problem also?  Any knowledge about how to
>             resolve this?  I am currently on Tiger.
> 
>             Thanks,
>             Jonathan
>             _______________________________________________
>             macports-users mailing list
>             macports-users at lists.macosforge.org
>             <mailto:macports-users at lists.macosforge.org>
>             http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> 
> 
> 
> 
>     _______________________________________________
>     macports-users mailing list
>     macports-users at lists.macosforge.org
>     <mailto:macports-users at lists.macosforge.org>
>     http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> 
> 

From dluke at geeklair.net  Thu Jun 18 13:06:54 2009
From: dluke at geeklair.net (Daniel J. Luke)
Date: Thu, 18 Jun 2009 16:06:54 -0400
Subject: port install gnat-gcc
In-Reply-To: <0F909060-156F-4066-B98F-A13ACB1AB22A@macports.org>
References: <C030B322-9742-4589-A259-D185CB3B713B@free.fr>
	<4A326895.4050709@users.sourceforge.net>
	<E5413A52-CE7B-4FE7-86A8-2AC7523F91AB@free.fr>
	<4A338554.4040602@macports.org>
	<CE33F78C-E679-4A8F-8EEA-8ED592FB7673@macports.org>
	<A9698F62-9A97-4C9C-9716-82A5A261E2A5@macports.org>
	<0F909060-156F-4066-B98F-A13ACB1AB22A@macports.org>
Message-ID: <DD3B7039-6999-490D-9DED-030998E9C4F1@geeklair.net>

On Jun 18, 2009, at 5:17 AM, Boey Maun Suang wrote:
> Consequently, I can't see any relative location to which we can  
> extract a GCC bootstrap, and /var/tmp is the best absolute path that  
> I can think of for this purpose.
>
> Incidentally, I used otool on the executables in the current ghc  
> bootstrap compiler, and they contain _absolute_ references to /opt/ 
> local/lib/libgmp.3.dylib, so for those who try to install MacPorts  
> ghc and who have configured ${prefix} to be other than /opt/local,  
> the build will either fail due to the non-existence of /opt/local/ 
> lib/libgmp.3.dylib, or (in accordance with the dyld(1) man page's  
> description of the DYLD_LIBRARY_PATH and DYLD_FALLBACK_LIBRARY_PATH  
> variables), it will silently pick up libgmp.3.dylib in another  
> location, such as /usr/local/lib, when it is run.  I haven't looked  
> into it, but we may find that the ghc bootstrap actually has this  
> same problem, just not in such an obvious or severe form.
>
> As always, your thoughts (and those of others on the list) would be  
> appreciated.


If it's just the libraries in the bootstrap compiler that are a  
problem, then you could do the temp install into somewhere like $ 
{worksrcpath} and set DYLD_FALLBACK_LIBRARY_PATH ...

--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090618/30c36dce/attachment.bin>

From frstan at bellsouth.net  Thu Jun 18 14:06:28 2009
From: frstan at bellsouth.net (William Davis)
Date: Thu, 18 Jun 2009 17:06:28 -0400
Subject: port install gnat-gcc
In-Reply-To: <DD3B7039-6999-490D-9DED-030998E9C4F1@geeklair.net>
References: <C030B322-9742-4589-A259-D185CB3B713B@free.fr>
	<4A326895.4050709@users.sourceforge.net>
	<E5413A52-CE7B-4FE7-86A8-2AC7523F91AB@free.fr>
	<4A338554.4040602@macports.org>
	<CE33F78C-E679-4A8F-8EEA-8ED592FB7673@macports.org>
	<A9698F62-9A97-4C9C-9716-82A5A261E2A5@macports.org>
	<0F909060-156F-4066-B98F-A13ACB1AB22A@macports.org>
	<DD3B7039-6999-490D-9DED-030998E9C4F1@geeklair.net>
Message-ID: <860CBFB2-D549-4F8A-A4C7-D27590817B3E@bellsouth.net>


On Jun 18, 2009, at 4:06 PM, Daniel J. Luke wrote:

> On Jun 18, 2009, at 5:17 AM, Boey Maun Suang wrote:
>> Consequently, I can't see any relative location to which we can  
>> extract a GCC bootstrap, and /var/tmp is the best absolute path  
>> that I can think of for this purpose.
>>
>> Incidentally, I used otool on the executables in the current ghc  
>> bootstrap compiler, and they contain _absolute_ references to /opt/ 
>> local/lib/libgmp.3.dylib, so for those who try to install MacPorts  
>> ghc and who have configured ${prefix} to be other than /opt/local,  
>> the build will either fail due to the non-existence of /opt/local/ 
>> lib/libgmp.3.dylib, or (in accordance with the dyld(1) man page's  
>> description of the DYLD_LIBRARY_PATH and DYLD_FALLBACK_LIBRARY_PATH  
>> variables), it will silently pick up libgmp.3.dylib in another  
>> location, such as /usr/local/lib, when it is run.  I haven't looked  
>> into it, but we may find that the ghc bootstrap actually has this  
>> same problem, just not in such an obvious or severe form.
>>
>> As always, your thoughts (and those of others on the list) would be  
>> appreciated.
>
>
> If it's just the libraries in the bootstrap compiler that are a  
> problem, then you could do the temp install into somewhere like $ 
> {worksrcpath} and set DYLD_FALLBACK_LIBRARY_PATH ...
>
> --
> Daniel J. Luke


Daniel:
I understood Boey Maun Suang to be saying the paths had to be hard  
coded, and /var/tmp was the only thing he could rely on to be the same  
on all machines.

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090618/6a6fb256/attachment.html>

From dluke at geeklair.net  Thu Jun 18 15:29:45 2009
From: dluke at geeklair.net (Daniel J. Luke)
Date: Thu, 18 Jun 2009 18:29:45 -0400
Subject: port install gnat-gcc
In-Reply-To: <860CBFB2-D549-4F8A-A4C7-D27590817B3E@bellsouth.net>
References: <C030B322-9742-4589-A259-D185CB3B713B@free.fr>
	<4A326895.4050709@users.sourceforge.net>
	<E5413A52-CE7B-4FE7-86A8-2AC7523F91AB@free.fr>
	<4A338554.4040602@macports.org>
	<CE33F78C-E679-4A8F-8EEA-8ED592FB7673@macports.org>
	<A9698F62-9A97-4C9C-9716-82A5A261E2A5@macports.org>
	<0F909060-156F-4066-B98F-A13ACB1AB22A@macports.org>
	<DD3B7039-6999-490D-9DED-030998E9C4F1@geeklair.net>
	<860CBFB2-D549-4F8A-A4C7-D27590817B3E@bellsouth.net>
Message-ID: <48269E5A-B61A-4580-A2E6-D783ECC3BC04@geeklair.net>

On Jun 18, 2009, at 5:06 PM, William Davis wrote:
>> If it's just the libraries in the bootstrap compiler that are a  
>> problem, then you could do the temp install into somewhere like $ 
>> {worksrcpath} and set DYLD_FALLBACK_LIBRARY_PATH ...
>
>
> I understood Boey Maun Suang to be saying the paths had to be hard  
> coded, and /var/tmp was the only thing he could rely on to be the  
> same on all machines.


If the reason why it needs to be the same path everywhere is because  
of the install name for the shared libraries that come with the  
bootstrap compiler, then the DYLD_* variables can be used to make it a  
non-issue.

(in fact, this is one of the few instances where those environment  
variables are a good idea to use).

--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090618/7d73306f/attachment.bin>

From d.l.tDeContes at free.fr  Thu Jun 18 16:47:52 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Fri, 19 Jun 2009 01:47:52 +0200
Subject: dbus
In-Reply-To: <D84A8471-F8BD-40E8-A313-5C4FE81D5978@macports.org>
References: <F9D8A859-E3BD-4AD6-91CD-DB4EC0CDCC7D@free.fr>
	<D84A8471-F8BD-40E8-A313-5C4FE81D5978@macports.org>
Message-ID: <AD7E2A70-8AD4-4E92-8C75-17C3023AE19C@free.fr>


Le 13 juin 09 ? 23:51, Ryan Schmidt a ?crit :

>
> On Jun 13, 2009, at 07:02, Thomas De Contes wrote:
>
>> --->  Installing dbus @1.2.12_5
>> Error: Target org.macports.activate returned: <main> attribute  
>> status: eDSPermissionError
>>
>> what's the problem ?
>
> I assume you're doing this in a non-root MacPorts installation.

yes
(like you, if i remember ;-) )

> dbus wants to install a startupitem so you need to either use sudo  
> to install it, or use the no_startupitem variant.

+ port install dbus +no_startupitem
--->  Fetching dbus
--->  Verifying checksum(s) for dbus
--->  Extracting dbus
--->  Applying patches to dbus
--->  Configuring dbus
--->  Building dbus
--->  Staging dbus into destroot
--->  Installing dbus @1.2.14_0+no_startupitem
Error: Target org.macports.activate returned: <main> attribute  
status: eDSPermissionError
Error: Status 1 encountered during processing.


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Thu Jun 18 17:12:48 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Fri, 19 Jun 2009 02:12:48 +0200
Subject: purge
In-Reply-To: <4A350DF3.7010202@macports.org>
References: <09BA39C3-895A-4F1D-BEF2-D4362D87EE9D@free.fr>	<4A344FC8.20005@macports.org>
	<5E61EA4A-73D6-4670-99C8-A2F91F96D6FE@free.fr>
	<4A350DF3.7010202@macports.org>
Message-ID: <6FCAC47A-275C-4AF9-808D-5CD687AB32DE@free.fr>


Le 14 juin 09 ? 16:49, Joshua Root a ?crit :

> On 2009-6-15 00:15, Thomas De Contes wrote:
>>
>> Le 14 juin 09 ? 03:18, Rainer M?ller a ?crit :
>>
>>> On 2009-06-14 02:20, Thomas De Contes wrote:
>>>> what do you think about this ? :-)
>>>
>>> You want #15260 [1] to be implemented, which covers exactly what you
>>> propose here.
>>
>> very nice :-)))
>>
>> do you know if this will be in MacPorts 1.8.0 ?
>
> No work has been done to implement it yet, so probably not.

ok
it's nice that other people has the same wish than me :-)
now, it will be coded when it will be possible ... :-)

>
>> and when it will be available ?
>
> 1.8 will hopefully not be too much longer. We're not setting any
> deadlines, since it's a small, completely volunteer effort.

no problem :-)
nice that it will be soon :-)

>
>>>
>>> Until that, you can use port_cutleaves [2] to identify and  
>>> uninstall no
>>> longer needed ports.
>>
>> it seems to be nice too :-)

there is sth strange
(i think it's better to open a new thread)

>>
>> but i get
>> + port_cutleaves
>> Error: couldn't read file
>> "/Library/Tcl/macports1.0/macports_fastload.tcl": no such file or  
>> directory
>>
>> my tcl directory is
>> /Users/thomas/Documents/prgm/bin/autoinstall/macports/tcl ,
>> and before that it was /Users/thomas/Library/Tcl
>>
>> is it possible to correct that please ? :-)
>
> From the manual:
>
> -t path
>               Specify a different location for  the  base   
> MacPorts  Tcl
> 	      file </Library/Tcl>
>
> - Josh


thank you :-)


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Thu Jun 18 17:22:23 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Fri, 19 Jun 2009 02:22:23 +0200
Subject: dbus
In-Reply-To: <0EE2D8CF-D70B-4355-A4CD-2CD154285C82@macports.org>
References: <F9D8A859-E3BD-4AD6-91CD-DB4EC0CDCC7D@free.fr>
	<D84A8471-F8BD-40E8-A313-5C4FE81D5978@macports.org>
	<22DF0311-111E-43EB-996F-2B8A518A4591@free.fr>
	<7AC8D49B-A86A-473E-8A4A-8E2DD3E95B28@macports.org>
	<811D0B03-3894-4876-894F-3CB6177006C2@free.fr>
	<0EE2D8CF-D70B-4355-A4CD-2CD154285C82@macports.org>
Message-ID: <A091BD2B-FF68-4388-93FD-8E58580D44EE@free.fr>


Le 16 juin 09 ? 12:38, Ryan Schmidt a ?crit :

> On Jun 14, 2009, at 09:56, Thomas De Contes wrote:
>
>> Le 14 juin 09 ? 02:20, Ryan Schmidt a ?crit :
>>
>>> On Jun 13, 2009, at 18:43, Thomas De Contes wrote:
>>>
>>>>> dbus wants to install a startupitem so you need to either use  
>>>>> sudo to install it, or use the no_startupitem variant.
>>>>
>>>> thank you :-)
>>>>
>>>> well, is it possible to make MacPorts to automatically switch to  
>>>> the appropriate variant, in a such case ?
>>>
>>> No,
>>
>> i was not spoking about "do it right now", but rather "is it  
>> possible to improve MacPorts, so it will be able to do it later"
>> possibly with adding an option to ./configure or to port command,  
>> to allow it to do so
>>
>> still no ?
>
> dbus, apache2 and apache20 are the only ports that have a  
> no_startupitem variant. vnc and tightvnc have similar no_server  
> variants, but I think that's all. So I don't think we should invest  
> time in changing MacPorts base for something that would only be  
> used by five ports.

ok :-)

>
>
>>> but if you are certain you never want any port to install a  
>>> startup item, you can set the startup item type to none as Josh  
>>> explained.
>>
>> the problem is that i remove macports.conf in my script (see my  
>> last post in "python25")
>>
>> it can't be set via ./configure, can it ?
>
> I don't see a configure switch for that, no.

no matter, for five ports i can put "port install dbus  
+no_startupitem" in my script :-)

> Most of the things you can set in macports.conf cannot be set by  
> configure switches.

for essential parts, i'm happy to be able to make a script which is  
able to install on a new machine all that i need without human  
intervention


> Rather than add configure switches, we should probably add code to  
> upgrade a macports.conf.


anyway it's a good idea :-)


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Thu Jun 18 17:28:57 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Fri, 19 Jun 2009 02:28:57 +0200
Subject: clean old ports
Message-ID: <7A048C4F-D7F3-4983-81D6-B783A5A34356@free.fr>

hi :-)


is there a way to do so that all ports which are not curently  
installed are as clean as they never were installed ?

i think there is a command to really clean a port, but i don't want  
to apply to those which are still installed


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Thu Jun 18 18:34:08 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Fri, 19 Jun 2009 03:34:08 +0200
Subject: port_cutleaves
Message-ID: <DF9C8400-CA5D-4DB9-950D-82DB00B5AF63@free.fr>

hi :-)


it's strange :


thanks to port_cutleaves, i uninstalled all ports that i didn't need :-)

and today, doing "port -u upgrade outdated", it reinstalls them :-/

xorg-xtrans
xorg-bigreqsproto
xorg-xcmiscproto
xorg-xextproto
xorg-xf86bigfontproto
xorg-inputproto
xorg-kbproto
gperf


port_cutleaves still find them as "leaves"


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From perry at macports.org  Thu Jun 18 18:37:13 2009
From: perry at macports.org (Perry Lee)
Date: Fri, 19 Jun 2009 09:37:13 +0800
Subject: clean old ports
In-Reply-To: <7A048C4F-D7F3-4983-81D6-B783A5A34356@free.fr>
References: <7A048C4F-D7F3-4983-81D6-B783A5A34356@free.fr>
Message-ID: <8C013681-E231-4140-8CBD-F5B5CF934485@macports.org>

On Jun 19, 2009, at 8:28 AM, Thomas De Contes wrote:
> is there a way to do so that all ports which are not curently  
> installed are as clean as they never were installed ?

`port clean --all not installed`

From perry at macports.org  Thu Jun 18 18:40:39 2009
From: perry at macports.org (Perry Lee)
Date: Fri, 19 Jun 2009 09:40:39 +0800
Subject: port_cutleaves
In-Reply-To: <DF9C8400-CA5D-4DB9-950D-82DB00B5AF63@free.fr>
References: <DF9C8400-CA5D-4DB9-950D-82DB00B5AF63@free.fr>
Message-ID: <AA337CE8-180C-4629-82C4-92FB43AB99E2@macports.org>

On Jun 19, 2009, at 9:34 AM, Thomas De Contes wrote:
> thanks to port_cutleaves, i uninstalled all ports that i didn't  
> need :-)
>
> and today, doing "port -u upgrade outdated", it reinstalls them :-/
>
> xorg-xtrans
> xorg-bigreqsproto
> xorg-xcmiscproto
> xorg-xextproto
> xorg-xf86bigfontproto
> xorg-inputproto
> xorg-kbproto
> gperf
>
>
> port_cutleaves still find them as "leaves"

I'd guess those are build dependencies rather than library dependencies.

From boeyms at macports.org  Thu Jun 18 22:04:50 2009
From: boeyms at macports.org (Boey Maun Suang)
Date: Fri, 19 Jun 2009 15:04:50 +1000
Subject: port install gnat-gcc
In-Reply-To: <48269E5A-B61A-4580-A2E6-D783ECC3BC04@geeklair.net>
References: <C030B322-9742-4589-A259-D185CB3B713B@free.fr>
	<4A326895.4050709@users.sourceforge.net>
	<E5413A52-CE7B-4FE7-86A8-2AC7523F91AB@free.fr>
	<4A338554.4040602@macports.org>
	<CE33F78C-E679-4A8F-8EEA-8ED592FB7673@macports.org>
	<A9698F62-9A97-4C9C-9716-82A5A261E2A5@macports.org>
	<0F909060-156F-4066-B98F-A13ACB1AB22A@macports.org>
	<DD3B7039-6999-490D-9DED-030998E9C4F1@geeklair.net>
	<860CBFB2-D549-4F8A-A4C7-D27590817B3E@bellsouth.net>
	<48269E5A-B61A-4580-A2E6-D783ECC3BC04@geeklair.net>
Message-ID: <5B02A198-BDA6-458A-A0F2-AD1C649180FA@macports.org>

Hi Daniel,

On 19/06/2009, at 8:29 AM, Daniel J. Luke wrote:

> If the reason why it needs to be the same path everywhere is because  
> of the install name for the shared libraries that come with the  
> bootstrap compiler, then the DYLD_* variables can be used to make it  
> a non-issue.


Ah, I'd forgotten that DYLD_LIBRARY_PATH is checked before the install  
path name, but unfortunately that's not the only reason why the prefix  
matters, and I'm not confident that the other reason that I have found  
is the only one.  (The other place in which I've found it is libexec/ 
gcc/i386-apple-darwin9.6.0/4.3.3/install-tools/mkheaders, which is a  
shell script, and it looks like patching it or setting an environment  
variable should take care of the prefix there.)

If someone can confirm that those are the only ways in which the  
prefix matters in GCC, then I'd be confident that using  
DYLD_LIBRARY_PATH and patching/setting a variable for mkheaders would  
be fine, and thus that we could put the bootstrap in ${destroot}.   
Until then, though, I'm inclined to stick with putting it in /var/tmp.

Kind regards,


Maun Suang

-- 
Boey Maun Suang
Email: boeyms at macports dot org


From steve at asklater.com  Fri Jun 19 07:07:45 2009
From: steve at asklater.com (SteveC)
Date: Fri, 19 Jun 2009 07:07:45 -0700
Subject: rake failure
Message-ID: <DBF3A6B7-CDC4-484E-957E-6BA0C5A88687@asklater.com>

Help. This is on a new install of macports.


$ sudo port install rb-rails
Password:
--->  Activating rb-rake @0.8.3_0
Error: Target org.macports.activate returned: Image error: /opt/local/ 
bin/rake already exists and does not belong to a registered port.   
Unable to activate port rb-rake.
Error: The following dependencies failed to build: rb-rake rb-sqlite3
Error: Status 1 encountered during processing.




Best

Steve


From dluke at geeklair.net  Fri Jun 19 07:18:42 2009
From: dluke at geeklair.net (Daniel J. Luke)
Date: Fri, 19 Jun 2009 10:18:42 -0400
Subject: port install gnat-gcc
In-Reply-To: <5B02A198-BDA6-458A-A0F2-AD1C649180FA@macports.org>
References: <C030B322-9742-4589-A259-D185CB3B713B@free.fr>
	<4A326895.4050709@users.sourceforge.net>
	<E5413A52-CE7B-4FE7-86A8-2AC7523F91AB@free.fr>
	<4A338554.4040602@macports.org>
	<CE33F78C-E679-4A8F-8EEA-8ED592FB7673@macports.org>
	<A9698F62-9A97-4C9C-9716-82A5A261E2A5@macports.org>
	<0F909060-156F-4066-B98F-A13ACB1AB22A@macports.org>
	<DD3B7039-6999-490D-9DED-030998E9C4F1@geeklair.net>
	<860CBFB2-D549-4F8A-A4C7-D27590817B3E@bellsouth.net>
	<48269E5A-B61A-4580-A2E6-D783ECC3BC04@geeklair.net>
	<5B02A198-BDA6-458A-A0F2-AD1C649180FA@macports.org>
Message-ID: <601E48C6-C844-4627-B2B2-60F9F5F76F1C@geeklair.net>

On Jun 19, 2009, at 1:04 AM, Boey Maun Suang wrote:
> If someone can confirm that those are the only ways in which the  
> prefix matters in GCC, then I'd be confident that using  
> DYLD_LIBRARY_PATH and patching/setting a variable for mkheaders  
> would be fine, and thus that we could put the bootstrap in $ 
> {destroot}.  Until then, though, I'm inclined to stick with putting  
> it in /var/tmp.


It seems like testing with DYLD_LIBRARY_PATH and that other  
environment variable set should be fairly easy. I think it would be a  
good idea to do so if at all possible.
--
Daniel J. Luke
+========================================================+
| *---------------- dluke at geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090619/8ac7f0de/attachment.bin>

From d.l.tDeContes at free.fr  Fri Jun 19 07:22:21 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Fri, 19 Jun 2009 16:22:21 +0200
Subject: port install gnat-gcc
In-Reply-To: <5B02A198-BDA6-458A-A0F2-AD1C649180FA@macports.org>
References: <C030B322-9742-4589-A259-D185CB3B713B@free.fr>
	<4A326895.4050709@users.sourceforge.net>
	<E5413A52-CE7B-4FE7-86A8-2AC7523F91AB@free.fr>
	<4A338554.4040602@macports.org>
	<CE33F78C-E679-4A8F-8EEA-8ED592FB7673@macports.org>
	<A9698F62-9A97-4C9C-9716-82A5A261E2A5@macports.org>
	<0F909060-156F-4066-B98F-A13ACB1AB22A@macports.org>
	<DD3B7039-6999-490D-9DED-030998E9C4F1@geeklair.net>
	<860CBFB2-D549-4F8A-A4C7-D27590817B3E@bellsouth.net>
	<48269E5A-B61A-4580-A2E6-D783ECC3BC04@geeklair.net>
	<5B02A198-BDA6-458A-A0F2-AD1C649180FA@macports.org>
Message-ID: <26AC41E2-2522-4715-AD6C-FBD6E53463B6@free.fr>


Le 19 juin 09 ? 07:04, Boey Maun Suang a ?crit :

> Hi Daniel,
>
> On 19/06/2009, at 8:29 AM, Daniel J. Luke wrote:
>
>> If the reason why it needs to be the same path everywhere is  
>> because of the install name for the shared libraries that come  
>> with the bootstrap compiler, then the DYLD_* variables can be used  
>> to make it a non-issue.
>
>
> Ah, I'd forgotten that DYLD_LIBRARY_PATH is checked before the  
> install path name, but unfortunately that's not the only reason why  
> the prefix matters, and I'm not confident that the other reason  
> that I have found is the only one.  (The other place in which I've  
> found it is libexec/gcc/i386-apple-darwin9.6.0/4.3.3/install-tools/ 
> mkheaders, which is a shell script, and it looks like patching it  
> or setting an environment variable should take care of the prefix  
> there.)
>
> If someone can confirm that those are the only ways in which the  
> prefix matters in GCC, then I'd be confident that using  
> DYLD_LIBRARY_PATH and patching/setting a variable for mkheaders  
> would be fine, and thus that we could put the bootstrap in $ 
> {destroot}.  Until then, though, I'm inclined to stick with putting  
> it in /var/tmp.

i don't know entrails of gcc, but


i can use http://homepage.mac.com/awreynolds/.Public/Ada/PowerPC/fsf- 
ppc-ada-4.3-20071215-10.4-most-langs.tgz
where i want without any problem :-)


http://homepage.mac.com/awreynolds/.Public/Ada/PowerPC/fsf-ppc- 
ada-4.3-20080203-10.4-most-langs.tgz
asks for /usr/local/lib/libmpfr.1.dylib,
which is not provided by itself,

but with DYLD_FALLBACK_LIBRARY_PATH=my-path-to-macports/lib ,
i can use it where i want without any problem :-)


-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From d.l.tDeContes at free.fr  Fri Jun 19 08:14:13 2009
From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=)
Date: Fri, 19 Jun 2009 17:14:13 +0200
Subject: port_cutleaves
In-Reply-To: <AA337CE8-180C-4629-82C4-92FB43AB99E2@macports.org>
References: <DF9C8400-CA5D-4DB9-950D-82DB00B5AF63@free.fr>
	<AA337CE8-180C-4629-82C4-92FB43AB99E2@macports.org>
Message-ID: <0A4A4A56-3617-460D-880A-A70DC2B7B941@free.fr>


Le 19 juin 09 ? 03:40, Perry Lee a ?crit :

> On Jun 19, 2009, at 9:34 AM, Thomas De Contes wrote:
>> thanks to port_cutleaves, i uninstalled all ports that i didn't  
>> need :-)
>>
>> and today, doing "port -u upgrade outdated", it reinstalls them :-/
>>
>> xorg-xtrans
>> xorg-bigreqsproto
>> xorg-xcmiscproto
>> xorg-xextproto
>> xorg-xf86bigfontproto
>> xorg-inputproto
>> xorg-kbproto
>> gperf
>>
>>
>> port_cutleaves still find them as "leaves"
>
> I'd guess those are build dependencies rather than library  
> dependencies.

ok,
so why uninstall them, since i'll need it later ?

-- 
T?l?assistance / T?l?maintenance
http://www.portparallele.com/ThomasDECONTES/


From jmr at macports.org  Fri Jun 19 08:20:49 2009
From: jmr at macports.org (Joshua Root)
Date: Sat, 20 Jun 2009 01:20:49 +1000
Subject: port_cutleaves
In-Reply-To: <0A4A4A56-3617-460D-880A-A70DC2B7B941@free.fr>
References: <DF9C8400-CA5D-4DB9-950D-82DB00B5AF63@free.fr>	<AA337CE8-180C-4629-82C4-92FB43AB99E2@macports.org>
	<0A4A4A56-3617-460D-880A-A70DC2B7B941@free.fr>
Message-ID: <4A3BACD1.9090900@macports.org>

On 2009-6-20 01:14, Thomas De Contes wrote:
> ok,
> so why uninstall them, since i'll need it later ?

How is the program meant to know what you will do later?

- Josh

From jjstickel at vcn.com  Fri Jun 19 09:26:55 2009
From: jjstickel at vcn.com (Jonathan Stickel)
Date: Fri, 19 Jun 2009 10:26:55 -0600
Subject: VTK 5.2 and GL2PS export
In-Reply-To: <b808b3510906181027x202d3f4bw7499b0701d1dcc22@mail.gmail.com>
References: <4A393274.5080201@vcn.com>	
	<C922BA9B-A76D-4D31-9B66-9C7E231290C0@macports.org>	
	<4A3A7711.8080502@vcn.com>
	<b808b3510906181027x202d3f4bw7499b0701d1dcc22@mail.gmail.com>
Message-ID: <4A3BBC4F.7090805@vcn.com>

I managed to install vtk-devel without the doc and data variants (issues 
on Tiger).  However, I still see the same problem of textActors not 
exporting to ps/eps/pdf.  Just a blank box.

So, this problem exists for me on vtk-5.2, vtk-5.4, with both carbon and 
x11 on Tiger.  Can someone else confirm?  Does it happen on Cocoa? 
Leopard?  I can send a python-vtk test script offlist if someone will 
test it.

Thanks,
Jonathan


Darren Weber wrote:
> 
> I've done a bit of work on vtk-devel to make some things in the 
> installation version specific.  I have not tested whether vtk-devel can 
> co-exist with vtk5.
> 
> All the work on vtk-devel was based on the default variants (cocoa 
> shared wrap) plus testing and examples.  Nothing has been tested 
> extensively, and very little has been done with x11.
> 
> If you have time to run the build and install, I suggest the huge 
> variant, or no variants at all will give you a default set of variants.
> 
> vtk-devel has the variants:
>     darwin_9: Platform variant, do not select manually
>     huge: provide cocoa data doc examples shared testing wrap database 
> mpi boost
>     data: provide example data in: /opt/local/share/vtk-5.4/data
>     doc: provide doxygen documentation in: /opt/local/share/vtk-5.4/doc
>     examples: provide VTK examples in: /opt/local/share/vtk-5.4/examples
>     shared: build shared libraries (default)
>     testing: provide VTK tests in: /opt/local/share/vtk-5.4/testing
>     carbon: build with Carbon
>     cocoa: build with Cocoa (default)
>     x11: build with X11
>     wrap: provide java, py26, & tcl
>     java: java wrapper
>     py25: python 2.5 wrapper
>     py26: python 2.6 wrapper
>     tcl: tcl wrapper (MacPorts tcl/tk)
>     tcl_apple: tcl wrapper (apple tcl/tk framework)
>     database: provide all database variants
>     mysql5: build the MySQL driver for vtkSQLDatabase
>     pgsql83: build the PostgreSQL 8.3 driver for vtkSQLDatabase
>     odbc: build the ODBC database interface
>     mpi: use message passing interface (mpich2) for parallel support
>     boost: use Boost libraries - www.boost.org <http://www.boost.org>
>     universal: Build for multiple architectures
> 
> 
> Regards,
> Darren
> 
> 
> 
> 
> On Thu, Jun 18, 2009 at 10:19 AM, Jonathan Stickel <jjstickel at vcn.com 
> <mailto:jjstickel at vcn.com>> wrote:
> 
>     I reinstalled vtk5 with the +x11 variant, and now the vtk rendering
>     library is linked to
> 
>     /opt/local/lib/libGL.1.dylib
> 
>     However, I still have the same problem of textActors not exporting.
>     Labels on axes export fine, though.  I suppose this could be
>     reported upstream to VTK.  Maybe I'll try vtk-devel (vtk-5.4) when I
>     have some more time and see if the problem persists.
> 
>     Jonathan
> 
> 
> 
>     Jeremy Huddleston wrote:
> 
>         Interesting.  We were just talking about some vtk oddities in
>         the x11-users and xquartz-dev mailing list.
> 
>         Check out:
>         http://www.ctcms.nist.gov/oof/renderingbug
> 
>         Since you're seeing this purely in carbon, my guess now is that
>         this is an issue with either OpenGL.framework (which would mean
>         it's in both Tiger and Leopard... which I think isn't too
>         likely) or with VTK itself.
> 
>         On Jun 17, 2009, at 11:14, Jonathan Stickel wrote:
> 
>             I'm experiencing a problem using the GL2PS export feature of
>             VTK, where VTK was installed via Macports (vtk5
>             @5.2.1_2+carbon+darwin_8+python). When I have a textActor in
>             my render window, e.g. some arbitrary title or note, then
>             that text does not show in the exported pdf/eps.
> 
>             I suspect the problem might be related to the OpenGL library
>             that VTK links to, in this case
>             /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
>             since I am using the Carbon variant.  Can someone verify
>             that they see this problem also?  Any knowledge about how to
>             resolve this?  I am currently on Tiger.
> 
>             Thanks,
>             Jonathan
>             _______________________________________________
>             macports-users mailing list
>             macports-users at lists.macosforge.org
>             <mailto:macports-users at lists.macosforge.org>
>             http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> 
> 
> 
> 
>     _______________________________________________
>     macports-users mailing list
>     macports-users at lists.macosforge.org
>     <mailto:macports-users at lists.macosforge.org>
>     http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> 
> 

From jeremyhu at macports.org  Fri Jun 19 10:44:44 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Fri, 19 Jun 2009 10:44:44 -0700
Subject: port_cutleaves
In-Reply-To: <0A4A4A56-3617-460D-880A-A70DC2B7B941@free.fr>
References: <DF9C8400-CA5D-4DB9-950D-82DB00B5AF63@free.fr>
	<AA337CE8-180C-4629-82C4-92FB43AB99E2@macports.org>
	<0A4A4A56-3617-460D-880A-A70DC2B7B941@free.fr>
Message-ID: <2BE82EAF-0203-420F-8436-BD19BE42B930@macports.org>

They *were* build deps, but they were moved into lib deps.  This is  
because too many ports need them to build, and adding build deps for  
all those X11 protocol headers in each port that needs them was  
overkill.


On Jun 19, 2009, at 08:14, Thomas De Contes wrote:

>
> Le 19 juin 09 ? 03:40, Perry Lee a ?crit :
>
>> On Jun 19, 2009, at 9:34 AM, Thomas De Contes wrote:
>>> thanks to port_cutleaves, i uninstalled all ports that i didn't  
>>> need :-)
>>>
>>> and today, doing "port -u upgrade outdated", it reinstalls them :-/
>>>
>>> xorg-xtrans
>>> xorg-bigreqsproto
>>> xorg-xcmiscproto
>>> xorg-xextproto
>>> xorg-xf86bigfontproto
>>> xorg-inputproto
>>> xorg-kbproto
>>> gperf
>>>
>>>
>>> port_cutleaves still find them as "leaves"
>>
>> I'd guess those are build dependencies rather than library  
>> dependencies.
>
> ok,
> so why uninstall them, since i'll need it later ?
>
> -- 
> T?l?assistance / T?l?maintenance
> http://www.portparallele.com/ThomasDECONTES/
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From raimue at macports.org  Fri Jun 19 11:07:18 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Fri, 19 Jun 2009 20:07:18 +0200
Subject: rake failure
In-Reply-To: <DBF3A6B7-CDC4-484E-957E-6BA0C5A88687@asklater.com>
References: <DBF3A6B7-CDC4-484E-957E-6BA0C5A88687@asklater.com>
Message-ID: <4A3BD3D6.7040602@macports.org>

On 2009-06-19 16:07, SteveC wrote:
> Help. This is on a new install of macports.

If this would be a totally new install there would not be such
conflicts. :-)

> $ sudo port install rb-rails
> Password:
> --->  Activating rb-rake @0.8.3_0
> Error: Target org.macports.activate returned: Image error: /opt/local/ 
> bin/rake already exists and does not belong to a registered port.   
> Unable to activate port rb-rake.
> Error: The following dependencies failed to build: rb-rake rb-sqlite3
> Error: Status 1 encountered during processing.

In general this error means you installed something into the MacPorts
prefix without using the port command. 'sudo port -f activate rb-rake'
will rename the conflicting files.

Did you use gem directly? You should avoid that.

Rainer

From steve at asklater.com  Fri Jun 19 11:18:09 2009
From: steve at asklater.com (SteveC)
Date: Fri, 19 Jun 2009 11:18:09 -0700
Subject: rake failure
In-Reply-To: <4A3BD3D6.7040602@macports.org>
References: <DBF3A6B7-CDC4-484E-957E-6BA0C5A88687@asklater.com>
	<4A3BD3D6.7040602@macports.org>
Message-ID: <2F57D69E-3EDB-4055-99FB-D3A54F5D6215@asklater.com>

Thanks. I think I put the mac to sleep half way through the install  
and it got confused.

Now on installing postgres83-server, and following the instructions  
post install, I get this

$ sudo su postgres -c '/opt/local/lib/postgresql83/bin/initdb -D /opt/ 
local/var/db/postgresql83/defaultdb'
shell-init: error retrieving current directory: getcwd: cannot access  
parent directories: Permission denied
could not identify current directory: Permission denied
could not identify current directory: Permission denied
could not identify current directory: Permission denied
The program "postgres" is needed by initdb but was not found in the
same directory as "initdb".
Check your installation.


Anyone have any clue?

The two other commands it said to do worked fine:

  sudo mkdir -p /opt/local/var/db/postgresql83/defaultdb
  sudo chown postgres:postgres /opt/local/var/db/postgresql83/defaultdb



On 19 Jun 2009, at 11:07, Rainer M?ller wrote:

> On 2009-06-19 16:07, SteveC wrote:
>> Help. This is on a new install of macports.
>
> If this would be a totally new install there would not be such
> conflicts. :-)
>
>> $ sudo port install rb-rails
>> Password:
>> --->  Activating rb-rake @0.8.3_0
>> Error: Target org.macports.activate returned: Image error: /opt/ 
>> local/
>> bin/rake already exists and does not belong to a registered port.
>> Unable to activate port rb-rake.
>> Error: The following dependencies failed to build: rb-rake rb-sqlite3
>> Error: Status 1 encountered during processing.
>
> In general this error means you installed something into the MacPorts
> prefix without using the port command. 'sudo port -f activate rb-rake'
> will rename the conflicting files.
>
> Did you use gem directly? You should avoid that.
>
> Rainer
>

Best

Steve


From n.oxyde at gmail.com  Fri Jun 19 13:34:23 2009
From: n.oxyde at gmail.com (nox)
Date: Fri, 19 Jun 2009 22:34:23 +0200
Subject: port_cutleaves
In-Reply-To: <2BE82EAF-0203-420F-8436-BD19BE42B930@macports.org>
References: <DF9C8400-CA5D-4DB9-950D-82DB00B5AF63@free.fr>
	<AA337CE8-180C-4629-82C4-92FB43AB99E2@macports.org>
	<0A4A4A56-3617-460D-880A-A70DC2B7B941@free.fr>
	<2BE82EAF-0203-420F-8436-BD19BE42B930@macports.org>
Message-ID: <D27B055A-490C-4549-A915-D52C16EB4A74@gmail.com>

Why is that overkill? I thought the ultimate goal of MacPorts was  
binary packages. Binary packages won't need the *proto packages. I  
think we should not move these to lib deps.

Le 19 juin 09 ? 19:44, Jeremy Huddleston a ?crit :

> They *were* build deps, but they were moved into lib deps.  This is  
> because too many ports need them to build, and adding build deps for  
> all those X11 protocol headers in each port that needs them was  
> overkill.
>
>
> On Jun 19, 2009, at 08:14, Thomas De Contes wrote:
>
>>
>> Le 19 juin 09 ? 03:40, Perry Lee a ?crit :
>>
>>> On Jun 19, 2009, at 9:34 AM, Thomas De Contes wrote:
>>>> thanks to port_cutleaves, i uninstalled all ports that i didn't  
>>>> need :-)
>>>>
>>>> and today, doing "port -u upgrade outdated", it reinstalls them :-/
>>>>
>>>> xorg-xtrans
>>>> xorg-bigreqsproto
>>>> xorg-xcmiscproto
>>>> xorg-xextproto
>>>> xorg-xf86bigfontproto
>>>> xorg-inputproto
>>>> xorg-kbproto
>>>> gperf
>>>>
>>>>
>>>> port_cutleaves still find them as "leaves"
>>>
>>> I'd guess those are build dependencies rather than library  
>>> dependencies.
>>
>> ok,
>> so why uninstall them, since i'll need it later ?
>>
>> -- 
>> T?l?assistance / T?l?maintenance
>> http://www.portparallele.com/ThomasDECONTES/
>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From jeremyhu at macports.org  Fri Jun 19 13:43:07 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Fri, 19 Jun 2009 13:43:07 -0700
Subject: port_cutleaves
In-Reply-To: <D27B055A-490C-4549-A915-D52C16EB4A74@gmail.com>
References: <DF9C8400-CA5D-4DB9-950D-82DB00B5AF63@free.fr>
	<AA337CE8-180C-4629-82C4-92FB43AB99E2@macports.org>
	<0A4A4A56-3617-460D-880A-A70DC2B7B941@free.fr>
	<2BE82EAF-0203-420F-8436-BD19BE42B930@macports.org>
	<D27B055A-490C-4549-A915-D52C16EB4A74@gmail.com>
Message-ID: <0A9DF492-7AA9-4810-B807-125D5514EF50@macports.org>

Because it would require adding maybe 10 ports to depends_build to  
EVERY port that depends on X11.

True that binary packages don't need the *proto packages, but (for  
example) every package that has depends_lib port:gtk2 is going to need  
to add about 10 ports to depends_build if you make the protocol  
headers build dependencies.  Do you want to manage that?  I sure  
don't.  That's why they were added to depends_lib to the xorg-libs  
that need them to build.  That way anything that needs that lib will  
have the headers it needs as well.


On Jun 19, 2009, at 13:34, nox wrote:

> Why is that overkill? I thought the ultimate goal of MacPorts was  
> binary packages. Binary packages won't need the *proto packages. I  
> think we should not move these to lib deps.
>
> Le 19 juin 09 ? 19:44, Jeremy Huddleston a ?crit :
>
>> They *were* build deps, but they were moved into lib deps.  This is  
>> because too many ports need them to build, and adding build deps  
>> for all those X11 protocol headers in each port that needs them was  
>> overkill.
>>
>>
>> On Jun 19, 2009, at 08:14, Thomas De Contes wrote:
>>
>>>
>>> Le 19 juin 09 ? 03:40, Perry Lee a ?crit :
>>>
>>>> On Jun 19, 2009, at 9:34 AM, Thomas De Contes wrote:
>>>>> thanks to port_cutleaves, i uninstalled all ports that i didn't  
>>>>> need :-)
>>>>>
>>>>> and today, doing "port -u upgrade outdated", it reinstalls  
>>>>> them :-/
>>>>>
>>>>> xorg-xtrans
>>>>> xorg-bigreqsproto
>>>>> xorg-xcmiscproto
>>>>> xorg-xextproto
>>>>> xorg-xf86bigfontproto
>>>>> xorg-inputproto
>>>>> xorg-kbproto
>>>>> gperf
>>>>>
>>>>>
>>>>> port_cutleaves still find them as "leaves"
>>>>
>>>> I'd guess those are build dependencies rather than library  
>>>> dependencies.
>>>
>>> ok,
>>> so why uninstall them, since i'll need it later ?
>>>
>>> -- 
>>> T?l?assistance / T?l?maintenance
>>> http://www.portparallele.com/ThomasDECONTES/
>>>
>>> _______________________________________________
>>> macports-users mailing list
>>> macports-users at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>


From lovecraftian at mac.com  Sat Jun 20 00:13:59 2009
From: lovecraftian at mac.com (Scott)
Date: Sat, 20 Jun 2009 07:13:59 +0000 (UTC)
Subject: How to request MacPorts to add a port?
Message-ID: <loom.20090620T070846-88@post.gmane.org>

How to request MacPorts to add a port?

I have urltoys -- extremely useful.
I'd like it added into the MacPorts directory universe,
where it can be neatly killed, etc.

How to do this?


From brad at pixilla.com  Sat Jun 20 06:27:23 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Sat, 20 Jun 2009 06:27:23 -0700
Subject: How to request MacPorts to add a port?
In-Reply-To: <loom.20090620T070846-88@post.gmane.org>
References: <loom.20090620T070846-88@post.gmane.org>
Message-ID: <C39D1581-571D-485A-8C4F-BC47CFF37074@pixilla.com>

Hi Scott,


Are you referring to WWW:URLToys the perl module?

A bit more info would be nice as it may exist in ports or someone may  
be working on it. A url to the homepage as an example.

If it doesn't exist in ports create a local port repo and create the  
port yourself. Using a similar port as a starting point is always  
popular.
When you have finished create a new trak ticket and attach your files.  
Your port will get reviewed by MacPorts maintainers and someone with  
commit rights will commit it when appropriate.

http://guide.macports.org/chunked/development.local-repositories.html

https://trac.macports.org/auth/login/

Thanks for you interest in MacPorts.


// Brad

On Jun 20, 2009, at 12:13 AM, Scott wrote:

> How to request MacPorts to add a port?
>
> I have urltoys -- extremely useful.
> I'd like it added into the MacPorts directory universe,
> where it can be neatly killed, etc.
>
> How to do this?
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From ben at cogs.com  Sat Jun 20 06:50:53 2009
From: ben at cogs.com (Ben Greenfield)
Date: Sat, 20 Jun 2009 09:50:53 -0400
Subject: How to request MacPorts to add a port?
In-Reply-To: <loom.20090620T070846-88@post.gmane.org>
References: <loom.20090620T070846-88@post.gmane.org>
Message-ID: <077D113B-4632-4E8E-A509-0E57CAAC4E54@cogs.com>

hey Scott,

Currently the people officially in charge of macports are overworked  
volunteers. So the best way to get a port into macports is do as much  
as you can on your own and then ask the list for help when you have  
very specific questions.

Something like...

I'm follwoing the directions here found here
http://guide.macports.org/#development.introduction

and when I get to this step

http://trac.macports.org/wiki/PortfileRecipes

I can't figure out how to add a perl module to macports.

I noticed that urltoys is a perl module which is a good detail. I  
think you might be able to look at other perl modules that are in  
macports and see how they are handled. Then copy their portfile and  
try to make a urltoy port file.

Good luck and maybe someone else has better advice.

Ben




On Jun 20, 2009, at 3:13 AM, Scott wrote:

> How to request MacPorts to add a port?
>
> I have urltoys -- extremely useful.
> I'd like it added into the MacPorts directory universe,
> where it can be neatly killed, etc.
>
> How to do this?
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From milosh at macports.org  Sat Jun 20 11:47:53 2009
From: milosh at macports.org (Emmanuel Hainry)
Date: Sat, 20 Jun 2009 20:47:53 +0200
Subject: port_cutleaves
In-Reply-To: <0A9DF492-7AA9-4810-B807-125D5514EF50@macports.org>
References: <DF9C8400-CA5D-4DB9-950D-82DB00B5AF63@free.fr>
	<AA337CE8-180C-4629-82C4-92FB43AB99E2@macports.org>
	<0A4A4A56-3617-460D-880A-A70DC2B7B941@free.fr>
	<2BE82EAF-0203-420F-8436-BD19BE42B930@macports.org>
	<D27B055A-490C-4549-A915-D52C16EB4A74@gmail.com>
	<0A9DF492-7AA9-4810-B807-125D5514EF50@macports.org>
Message-ID: <20090620184753.GA6898@weetamoe.loria.fr>

Citando Jeremy Huddleston :
>
> Because it would require adding maybe 10 ports to depends_build to EVERY 
> port that depends on X11.
>
> True that binary packages don't need the *proto packages, but (for  
> example) every package that has depends_lib port:gtk2 is going to need  
> to add about 10 ports to depends_build if you make the protocol headers 
> build dependencies.  Do you want to manage that?  I sure don't.  That's 
> why they were added to depends_lib to the xorg-libs that need them to 
> build.  That way anything that needs that lib will have the headers it 
> needs as well.
>

Don't we have portgroups to take care of problems that are common to lots of
ports and are to be settled in a uniform way?

Emmanuel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090620/0a4059bf/attachment.bin>

From talklists at newgeo.com  Sat Jun 20 12:34:28 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Sat, 20 Jun 2009 12:34:28 -0700
Subject: How to request MacPorts to add a port?
In-Reply-To: <loom.20090620T070846-88@post.gmane.org>
References: <loom.20090620T070846-88@post.gmane.org>
Message-ID: <A1B3A6C0-802C-488F-B995-63F924A58DFE@newgeo.com>

It does not look like it exists. I went ahead and made a port file for  
you.  When I get some time, I will submit it to the port trac.

In the meantime, you can do this:
http://guide.macports.org/chunked/development.local-repositories.html

Then, in your local repo you just made, make a dir called "perl" and  
in that make a dir called "p5-www-urltoys", and cd into it.

Put this in a file called "p5-www-urltoys"
http://files.getdropbox.com/u/340087/drops/06.20.09/Portfile

Contents of the file pasted below, careful of the line breaks and  
wrapping that email is going to do to it.

 From inside the "p5-www-urltoys" run `sudo port install`

$sudo port install
--->  Fetching p5-www-urltoys
--->  Verifying checksum(s) for p5-www-urltoys
--->  Extracting p5-www-urltoys
--->  Configuring p5-www-urltoys
--->  Building p5-www-urltoys
--->  Staging p5-www-urltoys into destroot
--->  Installing p5-www-urltoys @1.28_0
--->  Activating p5-www-urltoys @1.28_0
--->  Cleaning p5-www-urltoys

Showing that it was installed
$port installed | grep urltoys
   p5-www-urltoys @1.28_0 (active)

I know little about perl, so just to make sure it is installed:
/opt/local/bin/perl -MWWW::URLToys -e 1
returns nothing, which I believe means it is now installed.

# $Id$

PortSystem               1.0
PortGroup                perl5 1.0

perl5.setup              WWW-URLToys 1.28
maintainers              hostwizard.com:scott

description              WWW::URLToys - gather and download URLs from  
URLs

long_description         WWW::URLToys is a separation of the program  
URLToys \
                          into its core code (this module), and the  
programs \
                          that use it (urltoys and urltoysw). This  
module has \
                          been made available via CPAN to allow others  
to use \
                          URLToys commands on their Perl arrays, and  
to create \
                          interfaces for URLToys that far surpass  
those of the \
                          original creator.

homepage		 http://search.cpan.org/~jdrago/WWW-URLToys-1.28/URLToys.pm

checksums                md5     de1951e1a3a1f7095631376f115ed7b9 \
                          sha1     
7011e9e28fb0374fea0dc29423c2bded4a099b22 \
                          rmd160   
fe3e805fc7319b100ab29056cac3c02d312d1e5b

platforms               darwin


On Jun 20, 2009, at 12:13 AM, Scott wrote:

> How to request MacPorts to add a port?
>
> I have urltoys -- extremely useful.
> I'd like it added into the MacPorts directory universe,
> where it can be neatly killed, etc.
>
> How to do this?

-- 
Scott * If you contact me off list replace talklists@ with scott@ *


From ryandesign at macports.org  Sat Jun 20 14:01:42 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sat, 20 Jun 2009 16:01:42 -0500
Subject: rake failure
In-Reply-To: <2F57D69E-3EDB-4055-99FB-D3A54F5D6215@asklater.com>
References: <DBF3A6B7-CDC4-484E-957E-6BA0C5A88687@asklater.com>
	<4A3BD3D6.7040602@macports.org>
	<2F57D69E-3EDB-4055-99FB-D3A54F5D6215@asklater.com>
Message-ID: <F041AA7B-B5C6-4316-900E-E90B83E554A8@macports.org>

On Jun 19, 2009, at 13:18, SteveC wrote:

> Thanks. I think I put the mac to sleep half way through the install  
> and it got confused.

In general that shouldn't cause problems though.


> Now on installing postgres83-server, and following the instructions  
> post install, I get this
>
> $ sudo su postgres -c '/opt/local/lib/postgresql83/bin/initdb -D / 
> opt/local/var/db/postgresql83/defaultdb'
> shell-init: error retrieving current directory: getcwd: cannot  
> access parent directories: Permission denied
> could not identify current directory: Permission denied
> could not identify current directory: Permission denied
> could not identify current directory: Permission denied
> The program "postgres" is needed by initdb but was not found in the
> same directory as "initdb".
> Check your installation.
>
>
> Anyone have any clue?

You might want to re-post this question in a new thread with  
"postgresql" somewhere in the subject line, so people with expertise  
on this subject will be more likely to see it.


From ryandesign at macports.org  Sat Jun 20 14:05:01 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sat, 20 Jun 2009 16:05:01 -0500
Subject: clean old ports
In-Reply-To: <7A048C4F-D7F3-4983-81D6-B783A5A34356@free.fr>
References: <7A048C4F-D7F3-4983-81D6-B783A5A34356@free.fr>
Message-ID: <BB609D0E-1246-49E6-BE26-04412828AB1C@macports.org>


On Jun 18, 2009, at 19:28, Thomas De Contes wrote:

> is there a way to do so that all ports which are not curently  
> installed are as clean as they never were installed ?
>
> i think there is a command to really clean a port, but i don't want  
> to apply to those which are still installed

"sudo port clean --all PORTNAME" will clean the work area, distfiles  
and archives of a port. You can use this on any port, installed or  
not. It will not uninstall an installed port.

"sudo port uninstall PORTNAME" will of course uninstall the port and  
all its registered files.

There may still be unregistered files associated with a port. For  
example, some ports copy their default configuration files for you;  
these copies will be left behind. You must manually locate and remove  
them if you want them gone.


From rolf at squarebox.co.uk  Sun Jun 21 01:30:57 2009
From: rolf at squarebox.co.uk (Rolf Howarth)
Date: Sun, 21 Jun 2009 09:30:57 +0100
Subject: i386-mingw32-runtime fails
Message-ID: <p06240803c6639dd83b86@[192.168.1.66]>

I'm new to MacPorts but having a few problems.

% sudo port sync
% sudo port install i386-mingw32-runtime
--->  Fetching i386-mingw32-runtime
--->  Attempting to fetch mingwrt-3.15.2-mingw32-dev.tar.gz from 
http://kent.dl.sourceforge.net/mingw
--->  Verifying checksum(s) for i386-mingw32-runtime
Error: Checksum (md5) mismatch for mingwrt-3.15.2-mingw32-dev.tar.gz
Error: Checksum (sha1) mismatch for mingwrt-3.15.2-mingw32-dev.tar.gz
Error: Checksum (rmd160) mismatch for mingwrt-3.15.2-mingw32-dev.tar.gz
Error: Target org.macports.checksum returned: Unable to verify file checksums
Error: Status 1 encountered during processing.

There's a trac ticket http://trac.macports.org/ticket/19582 on this 
which shows the correct checksums but the patch hasn't been applied 
and despite a sync my Portfile still has the incorrect old checksum.

If I try to edit Portfile myself I then get
Error: Unable to open port: Usage: sha1 file ?file?

-Rolf

From ryandesign at macports.org  Sun Jun 21 11:12:26 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 21 Jun 2009 13:12:26 -0500
Subject: i386-mingw32-runtime fails
In-Reply-To: <p06240803c6639dd83b86@[192.168.1.66]>
References: <p06240803c6639dd83b86@[192.168.1.66]>
Message-ID: <ABEE45C6-30F9-4388-B3C6-74D645CB9EB1@macports.org>


On Jun 21, 2009, at 03:30, Rolf Howarth wrote:

> I'm new to MacPorts but having a few problems.
>
> % sudo port sync
> % sudo port install i386-mingw32-runtime
> --->  Fetching i386-mingw32-runtime
> --->  Attempting to fetch mingwrt-3.15.2-mingw32-dev.tar.gz from  
> http://kent.dl.sourceforge.net/mingw
> --->  Verifying checksum(s) for i386-mingw32-runtime
> Error: Checksum (md5) mismatch for mingwrt-3.15.2-mingw32-dev.tar.gz
> Error: Checksum (sha1) mismatch for mingwrt-3.15.2-mingw32-dev.tar.gz
> Error: Checksum (rmd160) mismatch for mingwrt-3.15.2-mingw32- 
> dev.tar.gz
> Error: Target org.macports.checksum returned: Unable to verify file  
> checksums
> Error: Status 1 encountered during processing.
>
> There's a trac ticket http://trac.macports.org/ticket/19582 on this  
> which shows the correct checksums but the patch hasn't been applied  
> and despite a sync my Portfile still has the incorrect old checksum.

Thanks for the reminder. I just committed the fix, so if you "port  
sync" in a little while and try again it should work.


From talklists at newgeo.com  Sun Jun 21 11:48:35 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Sun, 21 Jun 2009 11:48:35 -0700
Subject: How to request MacPorts to add a port?
In-Reply-To: <A1B3A6C0-802C-488F-B995-63F924A58DFE@newgeo.com>
References: <loom.20090620T070846-88@post.gmane.org>
	<A1B3A6C0-802C-488F-B995-63F924A58DFE@newgeo.com>
Message-ID: <F18221E1-36CF-4E4E-8FE4-A85043C853FF@newgeo.com>

That should have been, put the downloaded Portfile into the "p5-www- 
urltoys" directory.  Keep the name "Portfile" as is, which is a  
requirement of MacPorts as far as I know.

On Jun 20, 2009, at 12:34 PM, Scott Haneda wrote:

> Put this in a file called "p5-www-urltoys"
> http://files.getdropbox.com/u/340087/drops/06.20.09/Portfile
>
> Contents of the file pasted below, careful of the line breaks and  
> wrapping that email is going to do to it.
>
> From inside the "p5-www-urltoys" run `sudo port install`

-- 
Scott * If you contact me off list replace talklists@ with scott@ *


From lovecraftian at mac.com  Mon Jun 22 02:24:37 2009
From: lovecraftian at mac.com (Scott)
Date: Mon, 22 Jun 2009 09:24:37 +0000 (UTC)
Subject: How to request MacPorts to add a port?
References: <loom.20090620T070846-88@post.gmane.org>
Message-ID: <loom.20090622T091151-354@post.gmane.org>

Hey guys thanks so much for your help, and for actually making 
a MacPorts port for URLtoys.

I went through HELL doing it myself.  And I still can't get
URLtoysw (the GUI version) to work.

I'd like to share my story, which is embedded with THREE questions:

(1)
I ended up doing it manually.  Below were the steps.  I'm sad that I 
had to put these OUTSIDE the /opt/local/ directory:

* get archive of URLtoys stuff at:
  http://search.cpan.org/~jdrago/WWW-URLToys-1.28/URLToys.pm
* make new directory WWW/ in /Library/Perl/Updates/5.8.8
* dig inside the archive, put URLtoys.pm in the above
* same for URLtoys.pod
* put URLtoys.pl in my_commands (the dir for my own stuff, placed in 
  PATH); kill the `.pl' extension; chmod +x

QUESTION 1: Could I have done this more easily?

(2)
You see that I decided to install the MODULAR version, which relies on 
UTLtoys.pm, which module can be used by other perl scripts.

QUESTION 2: I know NOTHING about perl.  Can MacPorts handl perl stuff?
Does it then properly modify the @INC variable?

(3) 
I had a really, really sick time trying to get the GUI version of 
URLtoys to work.  It needs the following things:

* Tk for Perl (only if you want the GUI downloader)
* LWP::TkIO (only if you want the GUI downloader)

First, I did:
$ perl -MCPAN -e 'install "WWW::URLToys"'
see:
http://search.cpan.org/~jdrago/WWW-URLToys-1.28/URLToys.pm

Then I got LWP::TkIO and did the "perl routine" on it:
[perl routine =
 $ perl Makefile.PL
 $ make
 $ make test
 $ make install]
see:
http://search.cpan.org/~rse/lcwa-1.0.0/lib/lwp/lib/LWP/TkIO.pm

Then I moved the urltoysw file (notice the final `w': this is the GUI
script; the regular one is plain `URLtoys') to /opt/local/bin, did
chmod + x, and ran it.

OH NO!  ERROR: "Can't locate Tk.pm in @INC ..."
    
Then:
$ sudo port install tk

This didn???t work.  So I tried:
$ perl -MCPAN -e 'install "Tk"'

Then I did:
$ perl Makefile.PL
$ make
$ make test
$ make install

Then I tried running URLtoysw again.  Same error.

Then I dug in one of the tk archives, found LWP::TkIO, and placed it 
EVERYWHERE it might be of help.

Then I tried running URLtoysw again.  Same error.

Then I downloaded tk-804
see:
http://search.cpan.org/~srezic/Tk-804.028_500/

Then I tried pTk, and any other package that sounded like "tk".

...

I did this for 9 (NINE) hours.

Really.

QUESTION 3:
Can anyone just point me to an explanation?  Can anyone use URLtoys 
on Mac OS X?  If you look around you'll see that lots of Mac folks 
have tk problems:

http://rt.cpan.org/Public/Bug/Display.html?id=39593

http://www.lehigh.edu/~sol0/Macintosh/X/ptk/

http://www.lehigh.edu/~sol0/Macintosh/X/ptk/PerlTK-under-Tiger.txt

http://search.cpan.org/~ni-s/Tk-804.027/pod/UserGuide.pod




From ms at mac-specialist.com  Mon Jun 22 06:26:22 2009
From: ms at mac-specialist.com (Bill Hernandez)
Date: Mon, 22 Jun 2009 08:26:22 -0500
Subject: mysql5-server install - FATAL ERROR: Could not find
	fill_help_tables.sql inside --basedir
Message-ID: <8F033F3C-E5DA-4308-A267-6CDFAB1FE01A@mac-specialist.com>

In setting up a brand new machine:

I followed exactly : http://trac.macports.org/wiki/howto/MAMP

Step 1: Turn off Apple's "Personal Web Sharing"
---> This went well (it wasn't on)...

Step 2: Install Apache
$ sudo port install apache2
---> This went well...

Step 3: Install MySQL
$ sudo port install mysql5-server
---> This did not go well...

[2009.22.06](07:48AM) -> [roscoe] ~	 $ sudo port install mysql5-server
---> Fetching mysql5
---> Attempting to fetch mysql-5.0.83.tar.gz from http://mysql.orst.edu/Downloads/MySQL-5.0
---> Attempting to fetch mysql-5.0.83.tar.gz from http://mysql.he.net/Downloads/MySQL-5.0/
---> Verifying checksum(s) for mysql5
---> Extracting mysql5
---> Applying patches to mysql5
---> Configuring mysql5
---> Building mysql5
---> Staging mysql5 into destroot
---> Installing mysql5 @5.0.83_0
---> Activating mysql5 @5.0.83_0
---> Cleaning mysql5
---> Fetching mysql5-server
---> Verifying checksum(s) for mysql5-server
---> Extracting mysql5-server
---> Configuring mysql5-server
---> Building mysql5-server
---> Staging mysql5-server into destroot
---> Creating launchd control script
###########################################################
# A startup item has been generated that will aid in
# starting mysql5-server 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.mysql5.plist
###########################################################
---> Installing mysql5-server @5.0.83_0
******************************************************
* In order to setup the database, you might want to run
* sudo -u mysql mysql_install_db5
* if this is a new install
******************************************************
---> Activating mysql5-server @5.0.83_0
---> Cleaning mysql5-server

[2009.22.06](07:55AM) -> [roscoe] ~	 $


TRY THE PRIMARY METHOD :
[2009.22.06](07:59AM) -> [roscoe] ~	 $ sudo -u mysql mysql_install_db5
Password:

FATAL ERROR: Could not find fill_help_tables.sql inside --basedir

When using --basedir you must point either into a MySQL binary
distribution directory or a compiled tree previously populated
by 'make install'


TRY THE ALTERNATE METHOD :
[2009.22.06](07:59AM) -> [roscoe] ~	 $ sudo mysql_install_db5

FATAL ERROR: Could not find fill_help_tables.sql inside --basedir

When using --basedir you must point either into a MySQL binary
distribution directory or a compiled tree previously populated
by 'make install'

[2009.22.06](08:01AM) -> [roscoe] ~	 $

Any ideas ?

From ms at mac-specialist.com  Mon Jun 22 08:01:51 2009
From: ms at mac-specialist.com (Bill Hernandez)
Date: Mon, 22 Jun 2009 10:01:51 -0500
Subject: mysql5-server install - FATAL ERROR: Could not find
	fill_help_tables.sql inside --basedir
Message-ID: <5EDBD68B-46B6-453E-BE9E-C982206A9886@mac-specialist.com>

Not sure if this made it through, sorry if it is a repeat...

For some reason I got a message : Your membership in the mailing list  
macports-users has been disabled
due to excessive bounces The last bounce received from you was dated  
14-Jun-2009

Anyway, In setting up a brand new machine:

I followed exactly : http://trac.macports.org/wiki/howto/MAMP

Step 1: Turn off Apple's "Personal Web Sharing"
---> This went well (it wasn't on)...

Step 2: Install Apache
$ sudo port install apache2
---> This went well...

Step 3: Install MySQL
$ sudo port install mysql5-server
---> This did not go well...

[2009.22.06](07:48AM) -> [roscoe] ~	 $ sudo port install mysql5-server
---> Fetching mysql5
---> Attempting to fetch mysql-5.0.83.tar.gz from http://mysql.orst.edu/Downloads/MySQL-5.0
---> Attempting to fetch mysql-5.0.83.tar.gz from http://mysql.he.net/Downloads/MySQL-5.0/
---> Verifying checksum(s) for mysql5
---> Extracting mysql5
---> Applying patches to mysql5
---> Configuring mysql5
---> Building mysql5
---> Staging mysql5 into destroot
---> Installing mysql5 @5.0.83_0
---> Activating mysql5 @5.0.83_0
---> Cleaning mysql5
---> Fetching mysql5-server
---> Verifying checksum(s) for mysql5-server
---> Extracting mysql5-server
---> Configuring mysql5-server
---> Building mysql5-server
---> Staging mysql5-server into destroot
---> Creating launchd control script
###########################################################
# A startup item has been generated that will aid in
# starting mysql5-server 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.mysql5.plist
###########################################################
---> Installing mysql5-server @5.0.83_0
******************************************************
* In order to setup the database, you might want to run
* sudo -u mysql mysql_install_db5
* if this is a new install
******************************************************
---> Activating mysql5-server @5.0.83_0
---> Cleaning mysql5-server

[2009.22.06](07:55AM) -> [roscoe] ~	 $


TRY THE PRIMARY METHOD :
[2009.22.06](07:59AM) -> [roscoe] ~	 $ sudo -u mysql mysql_install_db5
Password:

FATAL ERROR: Could not find fill_help_tables.sql inside --basedir

When using --basedir you must point either into a MySQL binary
distribution directory or a compiled tree previously populated
by 'make install'


TRY THE ALTERNATE METHOD :
[2009.22.06](07:59AM) -> [roscoe] ~	 $ sudo mysql_install_db5

FATAL ERROR: Could not find fill_help_tables.sql inside --basedir

When using --basedir you must point either into a MySQL binary
distribution directory or a compiled tree previously populated
by 'make install'

[2009.22.06](08:01AM) -> [roscoe] ~	 $

Any ideas ?

From payam.minoofar at meissner.com  Mon Jun 22 09:37:05 2009
From: payam.minoofar at meissner.com (Payam Minoofar)
Date: Mon, 22 Jun 2009 09:37:05 -0700
Subject: Wine versions
Message-ID: <C6650141.918%payam.minoofar@meissner.com>

Hi,

I am new to Macports, and I am not sure about how packages are identified. How does port distinguish between stable and unstable packages of a distribution? Is it simply the "-devel" suffix?

In other words, is wine-devel the beta version of wine?

Thank you.

Payam
--
Payam Minoofar, Ph.D.
Scientist
Meissner Filtration Products
4181 Calle Tesoro
Camarillo, CA 93012
USA
+1 805 388 9911
+1 805 388 5948 fax
Payam.minoofar at meissner.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090622/b98b2c4f/attachment.html>

From ryandesign at macports.org  Mon Jun 22 10:01:54 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 22 Jun 2009 12:01:54 -0500
Subject: Wine versions
In-Reply-To: <C6650141.918%payam.minoofar@meissner.com>
References: <C6650141.918%payam.minoofar@meissner.com>
Message-ID: <238DD24D-5AA6-442C-8A9C-F0E69EA84328@macports.org>


On Jun 22, 2009, at 11:37, Payam Minoofar wrote:

> I am new to Macports, and I am not sure about how packages are  
> identified. How does port distinguish between stable and unstable  
> packages of a distribution? Is it simply the ?-devel? suffix?

Yes, that's right. This has not yet been properly documented in the  
guide, but you can read about it here

http://trac.macports.org/ticket/14540


> In other words, is wine-devel the beta version of wine?


Not beta, but development snapshot. :)


From payam.minoofar at meissner.com  Mon Jun 22 10:14:50 2009
From: payam.minoofar at meissner.com (Payam Minoofar)
Date: Mon, 22 Jun 2009 10:14:50 -0700
Subject: Wine versions
In-Reply-To: <238DD24D-5AA6-442C-8A9C-F0E69EA84328@macports.org>
Message-ID: <C6650A1A.91C%payam.minoofar@meissner.com>

On 6/22/09 10:01 AM, "Ryan Schmidt" <ryandesign at macports.org> wrote:

Yes, that's right. This has not yet been properly documented in the
guide, but you can read about it here

http://trac.macports.org/ticket/14540

Thank you very much. My other question is then how do I get port to list the devel packages as well. Executing
Port list wine
Will only bring up wine 1.0. How do I force port to do a substring search so that the developer snapshots of a particular package also show up?

Thank you.

Payam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090622/d684de55/attachment.html>

From talklists at newgeo.com  Mon Jun 22 10:25:48 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 22 Jun 2009 10:25:48 -0700
Subject: Wine versions
In-Reply-To: <C6650A1A.91C%payam.minoofar@meissner.com>
References: <C6650A1A.91C%payam.minoofar@meissner.com>
Message-ID: <48C5C3D9-AA71-49EC-A311-45DAE93AFE03@newgeo.com>

I use "port search ?" which casts a much wider and more controllable  
net.
-- 
Scott
Iphone says hello.

On Jun 22, 2009, at 10:14 AM, Payam Minoofar <payam.minoofar at meissner.com 
 > wrote:

> On 6/22/09 10:01 AM, "Ryan Schmidt" <ryandesign at macports.org> wrote:
>
> Yes, that's right. This has not yet been properly documented in the
> guide, but you can read about it here
>
> http://trac.macports.org/ticket/14540
>
> Thank you very much. My other question is then how do I get port to  
> list the devel packages as well. Executing
> Port list wine
> Will only bring up wine 1.0. How do I force port to do a substring  
> search so that the developer snapshots of a particular package also  
> show up?
>
> Thank you.
>
> Payam
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090622/2e2dfbb8/attachment.html>

From dersh at alum.mit.edu  Mon Jun 22 13:34:00 2009
From: dersh at alum.mit.edu (Adam Dershowitz)
Date: Mon, 22 Jun 2009 13:34:00 -0700
Subject: wxWidgets version?
Message-ID: <1C2B2138-B490-40A3-A433-9E9D8F9A2F0B@alum.mit.edu>

Something is odd about wxWidgets and the versions.

I just did a sync and outdated and macports reported:
wxWidgets 2.8.10_0 < 2.8.9_0  (hmmm?)
Then I did port upgrade and got this:

--->  Fetching wxWidgets
--->  Verifying checksum(s) for wxWidgets
--->  Extracting wxWidgets
--->  Applying patches to wxWidgets
--->  Configuring wxWidgets
--->  Building wxWidgets
--->  Staging wxWidgets into destroot
--->  Deactivating wxWidgets @2.8.10_0
--->  Uninstalling wxWidgets @2.8.10_0
--->  Installing wxWidgets @2.8.9_0
Error: Target org.macports.install returned: Registry error: wxWidgets  
@2.8.9_0 already registered as installed.  Please uninstall it first.


And I then did this:
sudo port uninstall wxWidgets @2.8.9_0
--->  Uninstalling wxWidgets @2.8.9_0

and this:   sudo port install wxWidgets @2.8.10_0
--->  Installing wxWidgets @2.8.9_0
--->  Activating wxWidgets @2.8.9_0
--->  Cleaning wxWidgets


I did find this:  https://trac.macports.org/changeset/52662 but it  
doesn't really explain the story.  So, I don't get it about which one  
should be installed.

So, what's the story?  And what is the fix to it?

--Adam




From blb at macports.org  Mon Jun 22 14:01:13 2009
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 22 Jun 2009 15:01:13 -0600
Subject: wxWidgets version?
In-Reply-To: <1C2B2138-B490-40A3-A433-9E9D8F9A2F0B@alum.mit.edu>
References: <1C2B2138-B490-40A3-A433-9E9D8F9A2F0B@alum.mit.edu>
Message-ID: <20090622210113.GG599@ninagal.withay.com>

On Mon, Jun 22, 2009 at 01:34:00PM -0700, Adam Dershowitz said:
> Something is odd about wxWidgets and the versions.
>
> I just did a sync and outdated and macports reported:
> wxWidgets 2.8.10_0 < 2.8.9_0  (hmmm?)

>From what I understand, there were some incompatibilities with 2.8.10 so it
was back-rev'd with an increase in epoch (hence the newer version being
claimed as outdated).

> Then I did port upgrade and got this:
>
> --->  Fetching wxWidgets
> --->  Verifying checksum(s) for wxWidgets
> --->  Extracting wxWidgets
> --->  Applying patches to wxWidgets
> --->  Configuring wxWidgets
> --->  Building wxWidgets
> --->  Staging wxWidgets into destroot
> --->  Deactivating wxWidgets @2.8.10_0
> --->  Uninstalling wxWidgets @2.8.10_0
> --->  Installing wxWidgets @2.8.9_0
> Error: Target org.macports.install returned: Registry error: wxWidgets  
> @2.8.9_0 already registered as installed.  Please uninstall it first.

Hmm, it sounds like port got a little confused since I'm guessing you had
the original 2.8.9 installed (with epoch 0, the default) then the upgrade
appears to have not taken the newer epoch value into account.  If that's the
case that would definitely be a bug with base.

>
>
> And I then did this:
> sudo port uninstall wxWidgets @2.8.9_0
> --->  Uninstalling wxWidgets @2.8.9_0
>
> and this:   sudo port install wxWidgets @2.8.10_0
> --->  Installing wxWidgets @2.8.9_0
> --->  Activating wxWidgets @2.8.9_0
> --->  Cleaning wxWidgets

'port install' doesn't use the @version nomenclature, so it installed
whatever version is current, 2.8.9 in this case.  2.8.9 should be the right
one to have, and you got around the original bug by uninstalling 2.8.9
before the new install.

Bryan

>
>
> I did find this:  https://trac.macports.org/changeset/52662 but it  
> doesn't really explain the story.  So, I don't get it about which one  
> should be installed.
>
> So, what's the story?  And what is the fix to it?
>
> --Adam

From mpd at nees.rpi.edu  Mon Jun 22 14:01:35 2009
From: mpd at nees.rpi.edu (Michael Dippery)
Date: Mon, 22 Jun 2009 17:01:35 -0400
Subject: python26 can't import socket module
Message-ID: <B415C50B-3671-4428-B3AF-CF1D42B6AAD3@nees.rpi.edu>

I recently installed MacPort's python26 port. I am now unable to use  
Django's manage.py script; it fails with the error "Error: cannot  
import name SSLError" (I have tried with both py25-django and py26- 
django installed).

The problem occurs when a piece of Django code tries to access  
socket.sslerror. I fired up Python 2.6, and got the following error  
when I tried to "import socket":

Python 2.6.2 (r262:71600, Jun 22 2009, 15:02:00)
[GCC 4.0.1 (Apple Computer, Inc. build 5367)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
 >>> import socket
Traceback (most recent call last):
   File "<stdin>", line 1, in <module>
   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/ 
lib/python2.6/socket.py", line 64, in <module>
     from _ssl import SSLError as sslerror
ImportError: cannot import name SSLError

The python25 port used to have a py25-socket-ssl port which I believe  
may have fixed this problem, but, of course, that port no longer  
exists for python26 (the SSL socket stuff is supposedly included in  
python26). Is there a reason this doesn't work, and moreover, how do  
I fix it?



=====================
Michael Dippery
Systems Programmer
CEES, Rensselaer Polytechnic Institute
W: (518) 276-8143
E: mpd at nees.rpi.edu

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090622/e122fa80/attachment.bin>

From blb at macports.org  Mon Jun 22 14:24:49 2009
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 22 Jun 2009 15:24:49 -0600
Subject: python26 can't import socket module
In-Reply-To: <B415C50B-3671-4428-B3AF-CF1D42B6AAD3@nees.rpi.edu>
References: <B415C50B-3671-4428-B3AF-CF1D42B6AAD3@nees.rpi.edu>
Message-ID: <20090622212449.GH599@ninagal.withay.com>

On Mon, Jun 22, 2009 at 05:01:35PM -0400, Michael Dippery said:
> I recently installed MacPort's python26 port. I am now unable to use  
> Django's manage.py script; it fails with the error "Error: cannot import 
> name SSLError" (I have tried with both py25-django and py26-django 
> installed).
>
> The problem occurs when a piece of Django code tries to access  
> socket.sslerror. I fired up Python 2.6, and got the following error when I 
> tried to "import socket":
>
> Python 2.6.2 (r262:71600, Jun 22 2009, 15:02:00)
> [GCC 4.0.1 (Apple Computer, Inc. build 5367)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import socket
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
>   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/ 
> lib/python2.6/socket.py", line 64, in <module>
>     from _ssl import SSLError as sslerror
> ImportError: cannot import name SSLError
>
> The python25 port used to have a py25-socket-ssl port which I believe may 
> have fixed this problem, but, of course, that port no longer exists for 
> python26 (the SSL socket stuff is supposedly included in python26). Is 
> there a reason this doesn't work, and moreover, how do I fix it?

It is included in python26, but it sounds like an issue occurred when it was
being built.  What version of OpenSSL did you have installed and active when
you built python26 (port installed openssl)?  This usually occurs when
python's build system fails to link to OpenSSL, and instead of simply
failing with an error message, it just continues on and doesn't install all
the needed modules.

Bryan


>
>
>
> =====================
> Michael Dippery
> Systems Programmer
> CEES, Rensselaer Polytechnic Institute
> W: (518) 276-8143
> E: mpd at nees.rpi.edu
>

From mpd at nees.rpi.edu  Mon Jun 22 14:32:49 2009
From: mpd at nees.rpi.edu (Michael Dippery)
Date: Mon, 22 Jun 2009 17:32:49 -0400
Subject: python26 can't import socket module
In-Reply-To: <20090622212449.GH599@ninagal.withay.com>
References: <B415C50B-3671-4428-B3AF-CF1D42B6AAD3@nees.rpi.edu>
	<20090622212449.GH599@ninagal.withay.com>
Message-ID: <3A3B2DB2-67D2-45EC-95E4-2528984D4121@nees.rpi.edu>

> What version of OpenSSL did you have installed and active when
> you built python26 (port installed openssl)?

I have openssl @0.9.8k_0 installed via MacPorts.



=====================
Michael Dippery
Systems Programmer
CEES, Rensselaer Polytechnic Institute
W: (518) 276-8143
E: mpd at nees.rpi.edu


From talklists at newgeo.com  Mon Jun 22 14:55:03 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 22 Jun 2009 14:55:03 -0700
Subject: How to request MacPorts to add a port?
In-Reply-To: <loom.20090622T091151-354@post.gmane.org>
References: <loom.20090620T070846-88@post.gmane.org>
	<loom.20090622T091151-354@post.gmane.org>
Message-ID: <B620BDDD-4E8C-41C3-B66D-39661CD20882@newgeo.com>

On Jun 22, 2009, at 2:24 AM, Scott wrote:

> Hey guys thanks so much for your help, and for actually making
> a MacPorts port for URLtoys.

Seems the portfile I made was missing some dependencies, you can  
follow the progress here:
http://trac.macports.org/ticket/20021

> (1)
> I ended up doing it manually.  Below were the steps.  I'm sad that I
> had to put these OUTSIDE the /opt/local/ directory:
>
> * get archive of URLtoys stuff at:
>  http://search.cpan.org/~jdrago/WWW-URLToys-1.28/URLToys.pm
> * make new directory WWW/ in /Library/Perl/Updates/5.8.8
> * dig inside the archive, put URLtoys.pm in the above
> * same for URLtoys.pod
> * put URLtoys.pl in my_commands (the dir for my own stuff, placed in
>  PATH); kill the `.pl' extension; chmod +x

I am not familiar with perl enough to say whether that was good or bad.

> QUESTION 1: Could I have done this more easily?

I think so, I believe by sticking with MacPorts, exclusively, this  
would have been much easier, though you would have to wait for someone  
to make the portfile, and for it to be approved, unless you want to  
follow previous steps to set up a local repo.  Doing so takes about 5  
minutes, which is a lot shorter than what you are putting into it now :)

> (2)
> You see that I decided to install the MODULAR version, which relies on
> UTLtoys.pm, which module can be used by other perl scripts.
>
> QUESTION 2: I know NOTHING about perl.  Can MacPorts handl perl stuff?
> Does it then properly modify the @INC variable?

MacPorts has had a lot of discussion about perl in the past, most of  
which is over my head.  I can say, that I have installed and used  
software that relies on perl modules that rely on a chain of perl  
modules that is very deep.  I was making the portfile, so it was a  
little different, but the end result for an end user is a one command  
install that just works.

> (3)
> I had a really, really sick time trying to get the GUI version of
> URLtoys to work.  It needs the following things:

Where do you get this GUI version?  I am guessing, this just inspires  
some window manager or something?

> * Tk for Perl (only if you want the GUI downloader)
> * LWP::TkIO (only if you want the GUI downloader)
>
> First, I did:
> $ perl -MCPAN -e 'install "WWW::URLToys"'
> see:
> http://search.cpan.org/~jdrago/WWW-URLToys-1.28/URLToys.pm

As far as I know, the port file at the above trac listing should work  
to get that far.  You need to set up the local repo part, then just run:
sudo port -d install p5-www-toys

> Then I got LWP::TkIO and did the "perl routine" on it:
> [perl routine =
> $ perl Makefile.PL
> $ make
> $ make test
> $ make install]
> see:
> http://search.cpan.org/~rse/lcwa-1.0.0/lib/lwp/lib/LWP/TkIO.pm

This also seems to be in MacPorts.  Is urltoys dependent on this?  The  
docs do not seem to state so.  If it is, the portfile above should be  
modified to include it.

MacPorts seems to have it
p5-tk @804.028 (perl)
     p5-tk is a Perl interface to Tk

> Then I moved the urltoysw file (notice the final `w': this is the GUI
> script; the regular one is plain `URLtoys') to /opt/local/bin, did
> chmod + x, and ran it.

CPAN does not have a "w" version
http://search.cpan.org/search?query=urltoys&mode=all
Can you elaborate?

I do not think you should manually move files in and out of /opt/local  
unless you specifically know how those will interact.  Moving apache  
http files in and out, yes, fine, but in this case, not sure it would  
work.  At the least, the files will not be registered with MacPorts.

> OH NO!  ERROR: "Can't locate Tk.pm in @INC ..."
>
> Then:
> $ sudo port install tk

I believe the correct command is to use p5-tk, as seen above, so I  
tested with:
sudo port -d install p5-tk
-d enabled debugging lines to show on the screen, which can give you  
hints on how to solve problems.

Try `man port` as well as read up on `port search` to help you find  
things. All perl modules will start with "p5-"

> This didn???t work.  So I tried:
> $ perl -MCPAN -e 'install "Tk"'
>
> Then I did:
> $ perl Makefile.PL
> $ make
> $ make test
> $ make install

I may be stepping out on a limb here, but the idea of using MacPorts  
for perl modules is to never have to use CPAN again. At least, that is  
how I look at it. I do not trust Apple to not nuke my installations,  
CPAN is going to drop the builds into pretty standard places, the  
chances of those files getting nuked are too high for my comfort levels.

> Then I tried running URLtoysw again.  Same error.

Can you explain "running", as I do not understand, so I can not try to  
replicate it on my end.

> Then I dug in one of the tk archives, found LWP::TkIO, and placed it
> EVERYWHERE it might be of help.

$port info p5-lwp-tkio
Error: Port p5-lwp-tkio not found

If you absolutely need this, it looks like MacPorts does not have it,  
and will need it, though it should not be hard to add in as well.  Is  
the non "w" version of urltoys dependent on this as well?

Also, there my be a chance it is part of p5-tk. I should know soon  
enough...

> Then I tried running URLtoysw again.  Same error.

Just poking around, I downloaded the "w" file from here:
http://web.archive.org/web/20041011105122/http://urltoys.com/urltoysw

Opened it and edited the first line to
#!/opt/local/bin/perl

I ran `chmod +x urltoysw.pl` on the file, and then ran:
/opt/local/bin/perl urltoysw.pl
to run the file.

I get an error of
Can't locate Tk.pm in @INC

However, as I was writing this, I was also running:
sudo port -d install p5-tk
This install takes ages, I guess there is a ton of xorg stuff that it  
pulls in.

I had also already installed the portfile referenced in the ticket at  
the top of this email.

I have to run out, and the install is not done yet.  Setting this  
laptop to not go to sleep, and I will report back when I get home in a  
hour.

> I did this for 9 (NINE) hours.


At some point, you may have wanted to stop, and come back here and  
start asking shorter and more specific questions.  I think it may take  
longer in time, but use less of your time :)
-- 
Scott * If you contact me off list replace talklists@ with scott@ *


From jmr at macports.org  Mon Jun 22 15:58:07 2009
From: jmr at macports.org (Joshua Root)
Date: Tue, 23 Jun 2009 08:58:07 +1000
Subject: wxWidgets version?
In-Reply-To: <20090622210113.GG599@ninagal.withay.com>
References: <1C2B2138-B490-40A3-A433-9E9D8F9A2F0B@alum.mit.edu>
	<20090622210113.GG599@ninagal.withay.com>
Message-ID: <4A400C7F.4050209@macports.org>

On 2009-6-23 07:01, Bryan Blackburn wrote:
> On Mon, Jun 22, 2009 at 01:34:00PM -0700, Adam Dershowitz said:
>> Then I did port upgrade and got this:
>>
>> --->  Fetching wxWidgets
>> --->  Verifying checksum(s) for wxWidgets
>> --->  Extracting wxWidgets
>> --->  Applying patches to wxWidgets
>> --->  Configuring wxWidgets
>> --->  Building wxWidgets
>> --->  Staging wxWidgets into destroot
>> --->  Deactivating wxWidgets @2.8.10_0
>> --->  Uninstalling wxWidgets @2.8.10_0
>> --->  Installing wxWidgets @2.8.9_0
>> Error: Target org.macports.install returned: Registry error: wxWidgets  
>> @2.8.9_0 already registered as installed.  Please uninstall it first.
> 
> Hmm, it sounds like port got a little confused since I'm guessing you had
> the original 2.8.9 installed (with epoch 0, the default) then the upgrade
> appears to have not taken the newer epoch value into account.  If that's the
> case that would definitely be a bug with base.

Pretty sure this is fixed for 1.8.

- Josh

From talklists at newgeo.com  Mon Jun 22 17:12:01 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 22 Jun 2009 17:12:01 -0700
Subject: How to request MacPorts to add a port?
In-Reply-To: <loom.20090622T091151-354@post.gmane.org>
References: <loom.20090620T070846-88@post.gmane.org>
	<loom.20090622T091151-354@post.gmane.org>
Message-ID: <DB772AB7-CF3F-4CEA-8CCD-B7B087F4E571@newgeo.com>

On Jun 22, 2009, at 2:24 AM, Scott wrote:

> QUESTION 3:
> Can anyone just point me to an explanation?  Can anyone use URLtoys
> on Mac OS X?  If you look around you'll see that lots of Mac folks
> have tk problems:
>
> http://rt.cpan.org/Public/Bug/Display.html?id=39593


I think that link more or less explains it, this is not a MacPorts  
issue, or a CPAN issue.

I installed as per these instructions:
http://www.urltoys.com/linux.php

libwww-perl
libterm-readline-gnu-perl
perl-tk

In MacPorts terminology, that means:
   p5-libwww-perl @5.826_0 (active)
   p5-term-readline-gnu @1.16_0 (active)
   p5-tk @804.028_0 (active)

And of course
   p5-www-urltoys @1.28_0 (active)

Downloaded the urltoysw.pl file, and ran it, after altering the  
starting line to point to MacPorts perl.

I get ./urltoysw.pl
Bus error

This is consistent with the problems listed at this url:
http://rt.cpan.org/Public/Bug/Display.html?id=39593

The last comment, only 2 months old, shows the same issue.  Everyone  
seems to get a bus error.  You will need to report this bug to the tk  
developers, and have them work it out, then update tk.

Seems MacPorts knows about this as well:
   http://trac.macports.org/ticket/18391
That just points back to the links you found
   http://rt.cpan.org/Public/Bug/Display.html?id=39593

At this point, this is nothing you are doing wrong, but something that  
the people behind the upstream software are going to need to fix.
-- 
Scott * If you contact me off list replace talklists@ with scott@ *


From artie.ziff at gmail.com  Mon Jun 22 17:35:01 2009
From: artie.ziff at gmail.com (Artie Ziff)
Date: Mon, 22 Jun 2009 17:35:01 -0700
Subject: dbus looking for libtool?
Message-ID: <4A402335.8080703@gmail.com>

Hello port users!

Any suggestions to get around this build of dbus?


--->  Building dbus
Error: Target org.macports.build returned: shell command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_dbus/work/dbus-1.2.14"
&& make all " returned error 2
Command output: make  all-recursive
Making all in dbus
make  all-am
/bin/sh ../libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0
-DHAVE_CONFIG_H -I. -I.. -I.. -I..  -fPIC -DDBUS_COMPILATION
-DDBUS_MACHINE_UUID_FILE=\""/opt/local/var/lib/dbus/machine-id"\"
-DDBUS_SYSTEM_CONFIG_FILE=\""/opt/local/etc/dbus-1/system.conf"\"
-DDBUS_SESSION_CONFIG_FILE=\""/opt/local/etc/dbus-1/session.conf"\"
-I/opt/local/include  -O2 -Wall -Wchar-subscripts -Wmissing-declarations
-Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align
-Wdeclaration-after-statement -fno-common -Wno-unused -Wno-sign-compare
-Wno-pointer-sign -Wno-format -fno-strict-aliasing -MT dbus-address.lo
-MD -MP -MF .deps/dbus-address.Tpo -c -o dbus-address.lo dbus-address.c
../libtool: line 838: X--tag=CC: command not found
../libtool: line 871: libtool: ignoring unknown tag : command not found
../libtool: line 838: X--mode=compile: command not found
../libtool: line 1005: *** Warning: inferring the mode of operation is
deprecated.: command not found
../libtool: line 1006: *** Future versions of Libtool will require
--mode=MODE be specified.: command not found
../libtool: line 1036: libtool: warning: cannot infer operation mode
from `/usr/bin/gcc-4.0': No such file or directory
../libtool: line 7119: libtool: you must specify a MODE: command not found
../libtool: line 7120: Try `libtool --help' for more information.:
command not found
make[3]: *** [dbus-address.lo] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2




Cheers,
AZ


From peter at pogma.com  Mon Jun 22 20:10:18 2009
From: peter at pogma.com (Peter O'Gorman)
Date: Mon, 22 Jun 2009 22:10:18 -0500
Subject: dbus looking for libtool?
In-Reply-To: <4A402335.8080703@gmail.com>
References: <4A402335.8080703@gmail.com>
Message-ID: <4A40479A.9090700@pogma.com>

Artie Ziff wrote:
> Hello port users!
> 
> Any suggestions to get around this build of dbus?

> ../libtool: line 838: X--tag=CC: command not found
> ../libtool: line 871: libtool: ignoring unknown tag : command not found
> ../libtool: line 838: X--mode=compile: command not found

The variable SED is unset in the generated libtool script. This is
usually due to the ltmain.sh being from a different version of libtool
than the libtool.m4 that aclocal found. Which is a little odd as the
port has use_autoreconf yes, and depends_build on autoconf, automake and
libtool.

Do you have a more complete build log? I'd like to see what happens at
the autoreconf stage.

Thanks,
Peter
-- 
Peter O'Gorman
http://pogma.com

From jeremyhu at macports.org  Mon Jun 22 22:24:20 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Mon, 22 Jun 2009 22:24:20 -0700
Subject: dbus looking for libtool?
In-Reply-To: <4A402335.8080703@gmail.com>
References: <4A402335.8080703@gmail.com>
Message-ID: <2CC5F772-B708-4F7F-8399-504A3CB66078@macports.org>

This looks like a case of conflicting versions of libtool.  Try doing:

sudo port deactivate libtool1

--Jeremy

On Jun 22, 2009, at 17:35, Artie Ziff wrote:

> Hello port users!
>
> Any suggestions to get around this build of dbus?
>
>
> --->  Building dbus
> Error: Target org.macports.build returned: shell command " cd
> "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_devel_dbus/work/dbus-1.2.14"
> && make all " returned error 2
> Command output: make  all-recursive
> Making all in dbus
> make  all-am
> /bin/sh ../libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0
> -DHAVE_CONFIG_H -I. -I.. -I.. -I..  -fPIC -DDBUS_COMPILATION
> -DDBUS_MACHINE_UUID_FILE=\""/opt/local/var/lib/dbus/machine-id"\"
> -DDBUS_SYSTEM_CONFIG_FILE=\""/opt/local/etc/dbus-1/system.conf"\"
> -DDBUS_SESSION_CONFIG_FILE=\""/opt/local/etc/dbus-1/session.conf"\"
> -I/opt/local/include  -O2 -Wall -Wchar-subscripts -Wmissing- 
> declarations
> -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align
> -Wdeclaration-after-statement -fno-common -Wno-unused -Wno-sign- 
> compare
> -Wno-pointer-sign -Wno-format -fno-strict-aliasing -MT dbus-address.lo
> -MD -MP -MF .deps/dbus-address.Tpo -c -o dbus-address.lo dbus- 
> address.c
> ../libtool: line 838: X--tag=CC: command not found
> ../libtool: line 871: libtool: ignoring unknown tag : command not  
> found
> ../libtool: line 838: X--mode=compile: command not found
> ../libtool: line 1005: *** Warning: inferring the mode of operation is
> deprecated.: command not found
> ../libtool: line 1006: *** Future versions of Libtool will require
> --mode=MODE be specified.: command not found
> ../libtool: line 1036: libtool: warning: cannot infer operation mode
> from `/usr/bin/gcc-4.0': No such file or directory
> ../libtool: line 7119: libtool: you must specify a MODE: command not  
> found
> ../libtool: line 7120: Try `libtool --help' for more information.:
> command not found
> make[3]: *** [dbus-address.lo] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
>
>
>
> Cheers,
> AZ
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From artie.ziff at gmail.com  Mon Jun 22 23:02:25 2009
From: artie.ziff at gmail.com (Artie Ziff)
Date: Mon, 22 Jun 2009 23:02:25 -0700
Subject: dbus looking for libtool?
In-Reply-To: <FA16B7E4-D5DE-4A5B-83D3-F859CA958863@apple.com>
References: <4A402335.8080703@gmail.com> <4A40479A.9090700@pogma.com>
	<FA16B7E4-D5DE-4A5B-83D3-F859CA958863@apple.com>
Message-ID: <4A406FF1.2040406@gmail.com>

Hi!

Many thanks for the interest to help.

Jeremy Huddleston wrote:
> Do you have both the "libtool" and "libtool1" ports installed?
>

I do not think so...

$ port list installed | grep libtool
libtool                        @2.2.6a         devel/libtool
$ sudo port deactivate libtool1
Error: port deactivate failed: Registry error: libtool1 not registered
as installed & active.
$


There appears to be a libtool in this build directory:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_dbus/work/dbus-1.2.14

I cannot find a log file that shows detailed build output. How can I
make that happen?

Cheers!


From frstan at bellsouth.net  Tue Jun 23 09:03:54 2009
From: frstan at bellsouth.net (William Davis)
Date: Tue, 23 Jun 2009 12:03:54 -0400
Subject: dbus looking for libtool?
In-Reply-To: <4A406FF1.2040406@gmail.com>
References: <4A402335.8080703@gmail.com> <4A40479A.9090700@pogma.com>
	<FA16B7E4-D5DE-4A5B-83D3-F859CA958863@apple.com>
	<4A406FF1.2040406@gmail.com>
Message-ID: <02D0CC6D-5075-4958-95EE-7F6C9571D099@bellsouth.net>


On Jun 23, 2009, at 2:02 AM, Artie Ziff wrote:

> Hi!
>
> Many thanks for the interest to help.
>
> Jeremy Huddleston wrote:
>> Do you have both the "libtool" and "libtool1" ports installed?
>>
>
> I do not think so...
>
> $ port list installed | grep libtool
> libtool                        @2.2.6a         devel/libtool
> $ sudo port deactivate libtool1
> Error: port deactivate failed: Registry error: libtool1 not registered
> as installed & active.
> $
>
>
> There appears to be a libtool in this build directory:
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_devel_dbus/work/dbus-1.2.14
>
> I cannot find a log file that shows detailed build output. How can I
> make that happen?


sudo  port -d install foo  [thats d for debug] or sudo port -du  
upgrade foo [the u makes port delete the older version afterward, not  
just deactivate it if the upgrade succeeds]

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From protsman at mac.com  Tue Jun 23 10:46:01 2009
From: protsman at mac.com (Shawn Protsman)
Date: Tue, 23 Jun 2009 10:46:01 -0700
Subject: deb script tools
Message-ID: <6FCDD168-E989-4D5E-9A60-64B9E605E208@mac.com>

I created a debian package (dpkg --build) recently and then moved it  
over to my Ubuntu dev box. Everything worked fine. However, I don't  
have access to tools like dch (debchange) and others which allow me to  
bump version numbers, build numbers, etc., like I do on a Debian  
system. These tools are included in the devscripts package:

http://packages.ubuntu.com/hardy/devel/devscripts

I did a port search for debchange but it is not in the port tree. Are  
there any equivalents to these apps in macports? If not, I'll just  
have to use my Ubuntu box.

--Shawn




From macports at luros.org  Tue Jun 23 10:59:47 2009
From: macports at luros.org (Jason Luros)
Date: Tue, 23 Jun 2009 10:59:47 -0700
Subject: MacPorts & perl path
Message-ID: <b1a66bb40906231059u56b46751u7d3d5a84ec70c9ab@mail.gmail.com>

This worked great. Thank you so much for your help. It begs the question,
why
isn't this the default for the Movable Type installation? Is there a
security risk in getting the path to perl from /usr/bin/env?

Daniel J. Luke wrote:
>
> On Apr 8, 2008, at 5:53 PM, Stephan Jaeger wrote:
>> I just installed  via macports the ports apache2, mysql5, php5 and
>> perl5.8.8 on my computer.
>> The reason for doing so is to set up a local development server for
>> my MovableType development.
>>
>> When I run a check (mt-check.cgi) in order to see which perl modules
>> I have to install, the module DBD::mysql is listed as "not
>> installed", although I installed it explicitly.
>
>
> The moveabletype scripts all unfortunately have #!/usr/bin/perl at the
> top, so they run the system perl instead of the macports perl.
>
> You can either change them all to #!/opt/local/bin/perl (or whatever
> your macports ${prefix} is set to) or #!/usr/bin/env perl (and then
> set up the script environment so that the macports perl is first in
> the path search).
>
> --
> Daniel J. Luke
> +========================================================+
> | *---------------- dluke at geeklair.net ----------------* |
> | *-------------- http://www.geeklair.net -------------* |
> +========================================================+
> |   Opinions expressed are mine and do not necessarily   |
> |          reflect the opinions of my employer.          |
> +========================================================+
>
>
>
>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090623/3d8fea4b/attachment.html>

From artie.ziff at gmail.com  Tue Jun 23 17:16:25 2009
From: artie.ziff at gmail.com (Artie Ziff)
Date: Tue, 23 Jun 2009 17:16:25 -0700
Subject: dbus looking for libtool?
In-Reply-To: <02D0CC6D-5075-4958-95EE-7F6C9571D099@bellsouth.net>
References: <4A402335.8080703@gmail.com> <4A40479A.9090700@pogma.com>
	<FA16B7E4-D5DE-4A5B-83D3-F859CA958863@apple.com>
	<4A406FF1.2040406@gmail.com>
	<02D0CC6D-5075-4958-95EE-7F6C9571D099@bellsouth.net>
Message-ID: <4A417059.9060003@gmail.com>


>
> sudo  port -d install foo  [thats d for debug] or sudo port -du
> upgrade foo [the u makes port delete the older version afterward, not
> just deactivate it if the upgrade succeeds]
>


Very (very!) helpful!!!


And the answer is....

gsed!

It was missing, somehow.
Prolly caused by my new tool, port_upgrade.
Thanks (to everybody!) for helping me out of that problem.

dbus is happy once again...




From tangle1 at mindspring.com  Tue Jun 23 18:35:11 2009
From: tangle1 at mindspring.com (tangle1 at mindspring.com)
Date: Tue, 23 Jun 2009 18:35:11 -0700 (GMT-07:00)
Subject: very long time 2 port install py25-pyqt4
Message-ID: <8924450.1245807311754.JavaMail.root@elwamui-polski.atl.sa.earthlink.net>

Hello:

I am using macports for the first time ... trying to "sudo port install py25-pyqt4". It has been running for more than 2 hours:

I have already successfully run "sudo port install" on these portfiles: python25,python_select,sip
and I ran sudo python_select python25 before installing sip.

Here are last few lines from terminal window:

--->  Attempting to fetch qt-mac-opensource-src-4.5.1.tar.gz from http://distfiles.macports.org/qt4-mac
--->  Verifying checksum(s) for qt4-mac
--->  Extracting qt4-mac
--->  Applying patches to qt4-mac
--->  Configuring qt4-mac
--->  Building qt4-mac

And here is ps -ef for relevant processes:

0 45301   704   0   0:17.70 ttys001    0:32.36 /usr/bin/tclsh /opt/local/bin/port install py25-pyqt4
    0 47078 45301   0   0:00.00 ttys001    0:00.00 sh -c  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_qt4-mac/work/qt-mac-opensource-src-4.5.1" && make first 
    0 47079 47078   0   0:00.01 ttys001    0:00.09 make first
    0 66360 47079   0   0:00.00 ttys001    0:00.00 /bin/sh -c cd src/3rdparty/webkit/WebCore/ && make -f Makefile 
    0 66361 66360   0   0:00.00 ttys001    0:00.03 make -f Makefile
    0 73778 66361   0   0:00.30 ttys001    0:01.33 make -f Makefile.Release all
    0 78024 73778   0   0:00.00 ttys001    0:00.00 /usr/bin/g++-4.0 -c -include .pch/debug-shared/QtWebKit -O2 -isystem/opt/local/include -Xarch_i386 -mmacosx-version-min=10.4 -fconstant-cfstrings -Wreturn-type -fno-stri
    0 78025 78024   0   0:00.00 ttys001    0:00.00 /usr/bin/i686-apple-darwin9-g++-4.0.1 -c -include .pch/debug-shared/QtWebKit -O2 -isystem/opt/local/include -mmacosx-version-min=10.4 -fconstant-cfstrings -Wreturn-type 
    0 78026 78025   0   0:00.10 ttys001    0:00.47 /usr/libexec/gcc/i686-apple-darwin9/4.0.1/cc1plus -quiet -I/opt/local/include -I../../../../mkspecs/macx-g++ -I. -I../../../../include/QtCore -I../../../../include/QtNet
    0 72205   125   0   0:00.01 ttys002    0:00.02 login -pf dev

I guess I should just leave this running? How long should this take? I am on a 2.93 GHz MacBook Pro Intel Duo Core OS 10.5.6. 

Thanks,

Suzanne

From ryandesign at macports.org  Tue Jun 23 18:42:20 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 23 Jun 2009 20:42:20 -0500
Subject: very long time 2 port install py25-pyqt4
In-Reply-To: <8924450.1245807311754.JavaMail.root@elwamui-polski.atl.sa.earthlink.net>
References: <8924450.1245807311754.JavaMail.root@elwamui-polski.atl.sa.earthlink.net>
Message-ID: <F7971A17-943C-4ED9-9717-CB84291180DA@macports.org>

On Jun 23, 2009, at 20:35, tangle1 at mindspring.com wrote:

> I am using macports for the first time ... trying to "sudo port  
> install py25-pyqt4". It has been running for more than 2 hours:
>
> I have already successfully run "sudo port install" on these  
> portfiles: python25,python_select,sip
> and I ran sudo python_select python25 before installing sip.
>
> Here are last few lines from terminal window:
>
> --->  Attempting to fetch qt-mac-opensource-src-4.5.1.tar.gz from  
> http://distfiles.macports.org/qt4-mac
> --->  Verifying checksum(s) for qt4-mac
> --->  Extracting qt4-mac
> --->  Applying patches to qt4-mac
> --->  Configuring qt4-mac
> --->  Building qt4-mac

[snip]

> I guess I should just leave this running? How long should this  
> take? I am on a 2.93 GHz MacBook Pro Intel Duo Core OS 10.5.6.


Welcome to MacPorts!

I don't remember how long it should take, but qt4-mac is one of the  
larger ports. Hours is certainly within the realm of possibility, but  
it shouldn't take days.



From ryandesign at macports.org  Tue Jun 23 18:44:29 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 23 Jun 2009 20:44:29 -0500
Subject: scons
In-Reply-To: <ace45c0a0906170554r31c084e6t5079d7b5cade7b39@mail.gmail.com>
References: <ace45c0a0906170554r31c084e6t5079d7b5cade7b39@mail.gmail.com>
Message-ID: <6D5DAE99-EDC9-4410-8356-3156A0B809EE@macports.org>


On Jun 17, 2009, at 07:54, Christopher Vance wrote:

> Is there a simple way to enable scons to use Python 2.6 instead of
> requiring 2.5?

scons uses python 2.5 because it uses the python25 portgroup. I do  
not know if it's as easy as changing it to use the python26 portgroup  
or if there is a specific reason why python 2.5 is required. You  
could ask the port's maintainer, or try this change yourself and see  
what happens. If you try the latter, let us know what you find.



From ms at mac-specialist.com  Tue Jun 23 18:58:37 2009
From: ms at mac-specialist.com (Bill Hernandez)
Date: Tue, 23 Jun 2009 20:58:37 -0500
Subject: mysql5-server install - FATAL ERROR: Could not find
	fill_help_tables.sql inside --basedir
In-Reply-To: <5EDBD68B-46B6-453E-BE9E-C982206A9886@mac-specialist.com>
References: <5EDBD68B-46B6-453E-BE9E-C982206A9886@mac-specialist.com>
Message-ID: <79751DC4-4E5B-4B12-B422-2376A844CDA4@mac-specialist.com>

Several days ago I posted this message but received no response, Does  
anybody know who the mySQL maintainer might be ?

I really would like to get this installed if possible.

Any ideas ?


From LenoreHorner at sbcglobal.net  Tue Jun 23 19:09:14 2009
From: LenoreHorner at sbcglobal.net (Lenore Horner)
Date: Tue, 23 Jun 2009 21:09:14 -0500
Subject: mysql5-server install - FATAL ERROR: Could not find
	fill_help_tables.sql inside --basedir
In-Reply-To: <79751DC4-4E5B-4B12-B422-2376A844CDA4@mac-specialist.com>
References: <5EDBD68B-46B6-453E-BE9E-C982206A9886@mac-specialist.com>
	<79751DC4-4E5B-4B12-B422-2376A844CDA4@mac-specialist.com>
Message-ID: <08E9E016-04A5-4936-9E36-707C040E6FDE@sbcglobal.net>


On Jun 23, 2009, at 20:58 , Bill Hernandez wrote:

> Several days ago I posted this message but received no response,  
> Does anybody know who the mySQL maintainer might be ?

$port info mysql5-server
mysql5-server @5.0.82 (databases)

MySQL is an open-source, multi-threaded SQL database with a command  
syntax very
similar to mSQL.
Homepage:    http://www.mysql.com/

Runtime Dependencies: mysql5
Platforms:            darwin
Maintainers:          ryandesign at macports.org
$


From blb at macports.org  Tue Jun 23 19:13:37 2009
From: blb at macports.org (Bryan Blackburn)
Date: Tue, 23 Jun 2009 20:13:37 -0600
Subject: mysql5-server install - FATAL ERROR: Could not find
	fill_help_tables.sql inside --basedir
In-Reply-To: <79751DC4-4E5B-4B12-B422-2376A844CDA4@mac-specialist.com>
References: <5EDBD68B-46B6-453E-BE9E-C982206A9886@mac-specialist.com>
	<79751DC4-4E5B-4B12-B422-2376A844CDA4@mac-specialist.com>
Message-ID: <20090624021337.GR64377@ninagal.withay.com>

On Tue, Jun 23, 2009 at 08:58:37PM -0500, Bill Hernandez said:
> Several days ago I posted this message but received no response, Does  
> anybody know who the mySQL maintainer might be ?
>
> I really would like to get this installed if possible.
>
> Any ideas ?

'port info' usually reveals who maintains a given port, unless of course it
comes up with 'nomaintainer'.

Do you have /opt/local/share/mysql5/mysql/fill_help_tables.sql ?  I'm
guessing that's what it is complaining about...

Bryan


From ryandesign at macports.org  Wed Jun 24 00:53:08 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 24 Jun 2009 02:53:08 -0500
Subject: mysql5-server install - FATAL ERROR: Could not find
	fill_help_tables.sql inside --basedir
In-Reply-To: <79751DC4-4E5B-4B12-B422-2376A844CDA4@mac-specialist.com>
References: <5EDBD68B-46B6-453E-BE9E-C982206A9886@mac-specialist.com>
	<79751DC4-4E5B-4B12-B422-2376A844CDA4@mac-specialist.com>
Message-ID: <86434470-9314-4F67-A766-F8BA043EF728@macports.org>


On Jun 23, 2009, at 20:58, Bill Hernandez wrote:

> Several days ago I posted this message but received no response,  
> Does anybody know who the mySQL maintainer might be ?

I am the maintainer, and I read your message and meant to respond but  
was on vacation. It has been a very long time since I set up my own  
MySQL installation so it was obviously done with a much earlier  
version of MySQL. I have not tested the new database setup in a very  
long time. I will see if I can test that for you later but for the  
rest of this week there's a non-MacPorts project that really needs to  
take priority for me.


From alakazam at macports.org  Wed Jun 24 04:42:11 2009
From: alakazam at macports.org (Olivier Le Floch)
Date: Wed, 24 Jun 2009 13:42:11 +0200
Subject: very long time 2 port install py25-pyqt4
In-Reply-To: <8924450.1245807311754.JavaMail.root@elwamui-polski.atl.sa.earthlink.net>
References: <8924450.1245807311754.JavaMail.root@elwamui-polski.atl.sa.earthlink.net>
Message-ID: <85ACA778-60E6-46BF-96F8-0DDE5964C5AD@macports.org>

Hi !

On 24 juin 09, at 03:35, tangle1 at mindspring.com wrote:

> I guess I should just leave this running? How long should this take?  
> I am on a 2.93 GHz MacBook Pro Intel Duo Core OS 10.5.6.

Depending on your RAM, simultaneous usage of the machine, and the  
accuracy of my memory, compiling Qt is going to take somewhere between  
3 and 6 hours I think.

Regards,

-- 
Olivier Le Floch

From skunkmeadowjr at gmail.com  Wed Jun 24 09:46:15 2009
From: skunkmeadowjr at gmail.com (James Gifford)
Date: Wed, 24 Jun 2009 16:46:15 +0000
Subject: No subject
Message-ID: <e9a1a8b60906240946g26727e1fvae626edfac8f07c4@mail.gmail.com>

it will take a long time to build - perl took all night with me.
-James
twitter.com/jrgifford
skunkmeadowjr at gmail.com
---------- Forwarded message ----------
From: tangle1 at mindspring.com
To: macports-users at lists.macosforge.org
Date: Tue, 23 Jun 2009 18:35:11 -0700 (GMT-07:00)
Subject: very long time 2 port install py25-pyqt4
Hello:

I am using macports for the first time ... trying to "sudo port
install py25-pyqt4". It has been running for more than 2 hours:

I have already successfully run "sudo port install" on these
portfiles: python25,python_select,sip
and I ran sudo python_select python25 before installing sip.

Here are last few lines from terminal window:

--->  Attempting to fetch qt-mac-opensource-src-4.5.1.tar.gz from
http://distfiles.macports.org/qt4-mac
--->  Verifying checksum(s) for qt4-mac
--->  Extracting qt4-mac
--->  Applying patches to qt4-mac
--->  Configuring qt4-mac
--->  Building qt4-mac

And here is ps -ef for relevant processes:

0 45301   704   0   0:17.70 ttys001    0:32.36 /usr/bin/tclsh
/opt/local/bin/port install py25-pyqt4
   0 47078 45301   0   0:00.00 ttys001    0:00.00 sh -c  cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_qt4-mac/work/qt-mac-opensource-src-4.5.1"
&& make first
   0 47079 47078   0   0:00.01 ttys001    0:00.09 make first
   0 66360 47079   0   0:00.00 ttys001    0:00.00 /bin/sh -c cd
src/3rdparty/webkit/WebCore/ && make -f Makefile
   0 66361 66360   0   0:00.00 ttys001    0:00.03 make -f Makefile
   0 73778 66361   0   0:00.30 ttys001    0:01.33 make -f Makefile.Release all
   0 78024 73778   0   0:00.00 ttys001    0:00.00 /usr/bin/g++-4.0 -c
-include .pch/debug-shared/QtWebKit -O2 -isystem/opt/local/include
-Xarch_i386 -mmacosx-version-min=10.4 -fconstant-cfstrings
-Wreturn-type -fno-stri
   0 78025 78024   0   0:00.00 ttys001    0:00.00
/usr/bin/i686-apple-darwin9-g++-4.0.1 -c -include
.pch/debug-shared/QtWebKit -O2 -isystem/opt/local/include
-mmacosx-version-min=10.4 -fconstant-cfstrings -Wreturn-type
   0 78026 78025   0   0:00.10 ttys001    0:00.47
/usr/libexec/gcc/i686-apple-darwin9/4.0.1/cc1plus -quiet
-I/opt/local/include -I../../../../mkspecs/macx-g++ -I.
-I../../../../include/QtCore -I../../../../include/QtNet
   0 72205   125   0   0:00.01 ttys002    0:00.02 login -pf dev

I guess I should just leave this running? How long should this take? I
am on a 2.93 GHz MacBook Pro Intel Duo Core OS 10.5.6.

Thanks,

Suzanne

From hal at halblog.com  Wed Jun 24 11:05:26 2009
From: hal at halblog.com (Hal Vaughan)
Date: Wed, 24 Jun 2009 14:05:26 -0400
Subject: Problem installing KDE/Amarok
Message-ID: <54522AA8-7FA1-4C45-AE58-FD15C433A27A@halblog.com>

I just installed MacPorts yesterday.  I'm trying to install Amarok and  
yesterday I typed "sudo port install amarok" yesterday.  It took qt  
hours to build.  Last night, when I got home about 9 pm, the terminal  
was not responding and clicking it gave me the spinning pinwheel.  I  
can't scroll or anything.  Ports has a message displayed: Installing  
kdebase4-runtime @4.2.4_0."  It's been at that stage since 9 pm last  
night (it's now about 2 pm the next day).  The terminal is locked up  
and I don't know if it's still building KDE and installing or if it's  
locked up.

I've asked for help on #kde-mac, but with 20 people in that group,  
nobody seems active.

I don't know if I should kill the terminal and therefore the ports  
process or if it just takes that long.  My guess is that KDE is big  
and it takes a lot of time and may take notable CPU resources, thus  
locking up the terminal for a while.  If that's so, I can deal with  
it, but for now, I can't run another instance of Terminal unless I  
reboot, and I don't know if restarting the port command will just put  
me in the same fix before.

I'm on an iMac with OS X 10.5.7, a 2.4 Ghz Intel 2 core CPU with 4 GB  
of 667 Mhz DDR2 SDRAM.  Not the latest, but no slouch either.  Does it  
take over 17 hours to install KDE with such a system?

Also I know that there are messages of commands I have to run on the  
terminal, but I only see a few, so I don't know if rebooting will mean  
I can't access any that have scrolled off the top yet.

Thanks for any guidance or help on this.


Hal

From ajmas at sympatico.ca  Wed Jun 24 11:50:25 2009
From: ajmas at sympatico.ca (Andre-John Mas)
Date: Wed, 24 Jun 2009 14:50:25 -0400
Subject: MacPorts and x86_64?
Message-ID: <BLU0-SMTP872E265D84EA6AD00C6712C5370@phx.gbl>

Hi,

 From what I read (accuracy of information can be disputed) we should  
expect Snow Leopard release in the third quater of this year. Taking  
this into account, I am curious to know when the general mandate is to  
64-bit compilation and Snow Leopard? For example will all ports be  
encouraged to build 64-bit by default on Snow Leopard, or will it be  
whatever the port maintainer feels like?

Andr?-John

From jmr at macports.org  Wed Jun 24 12:12:23 2009
From: jmr at macports.org (Joshua Root)
Date: Thu, 25 Jun 2009 05:12:23 +1000
Subject: MacPorts and x86_64?
In-Reply-To: <BLU0-SMTP872E265D84EA6AD00C6712C5370@phx.gbl>
References: <BLU0-SMTP872E265D84EA6AD00C6712C5370@phx.gbl>
Message-ID: <4A427A97.9020409@macports.org>

On 2009-6-25 04:50, Andre-John Mas wrote:
> Hi,
> 
> From what I read (accuracy of information can be disputed) we should
> expect Snow Leopard release in the third quater of this year. Taking
> this into account, I am curious to know when the general mandate is to
> 64-bit compilation and Snow Leopard? For example will all ports be
> encouraged to build 64-bit by default on Snow Leopard, or will it be
> whatever the port maintainer feels like?

I'm told that the compiler on Snow Leopard generates x86_64 binaries by
default. So with the current MacPorts code, that is what you'll get
(unless you build universal, or the port adds -arch flags itself).

The plan is to add a setting for the default target arch. MacPorts would
then attempt to always pass a -arch flag to the compiler (or -m32/-m64
for non-Apple compilers), and individual ports would need to make sure
that this is picked up by their build system if the default methods
don't suffice. The "sensible default" for this option would appear to be
x86_64 on Snow Leopard, and i386 or ppc on earlier OS releases according
to the hardware arch.

BTW, there is no question about accuracy. Barring large-scale disaster,
Snow Leopard *will* ship in September. :-)

- Josh

From ajmas at sympatico.ca  Wed Jun 24 13:03:24 2009
From: ajmas at sympatico.ca (Andre-John Mas)
Date: Wed, 24 Jun 2009 16:03:24 -0400
Subject: MacPorts and x86_64?
In-Reply-To: <4A427A97.9020409@macports.org>
References: <BLU0-SMTP872E265D84EA6AD00C6712C5370@phx.gbl>
	<4A427A97.9020409@macports.org>
Message-ID: <BLU0-SMTP354489A052CCBC9C70057FC5370@phx.gbl>


On 24-Jun-2009, at 15:12, Joshua Root wrote:

> On 2009-6-25 04:50, Andre-John Mas wrote:
>> Hi,
>>
>> From what I read (accuracy of information can be disputed) we should
>> expect Snow Leopard release in the third quater of this year. Taking
>> this into account, I am curious to know when the general mandate is  
>> to
>> 64-bit compilation and Snow Leopard? For example will all ports be
>> encouraged to build 64-bit by default on Snow Leopard, or will it be
>> whatever the port maintainer feels like?
>
> I'm told that the compiler on Snow Leopard generates x86_64 binaries  
> by
> default. So with the current MacPorts code, that is what you'll get
> (unless you build universal, or the port adds -arch flags itself).
>
> The plan is to add a setting for the default target arch. MacPorts  
> would
> then attempt to always pass a -arch flag to the compiler (or -m32/-m64
> for non-Apple compilers), and individual ports would need to make sure
> that this is picked up by their build system if the default methods
> don't suffice. The "sensible default" for this option would appear  
> to be
> x86_64 on Snow Leopard, and i386 or ppc on earlier OS releases  
> according
> to the hardware arch.

Will this option be specifiable in a configuration, so that in the short
term we can test 64-bit compatibility in Leopard?

> BTW, there is no question about accuracy. Barring large-scale  
> disaster,
> Snow Leopard *will* ship in September. :-)


Good to know, I couldn't find any source for dates, so I didn't want to
commit myself.

Andre

From ryandesign at macports.org  Wed Jun 24 13:57:22 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 24 Jun 2009 15:57:22 -0500
Subject: MacPorts and x86_64?
In-Reply-To: <BLU0-SMTP354489A052CCBC9C70057FC5370@phx.gbl>
References: <BLU0-SMTP872E265D84EA6AD00C6712C5370@phx.gbl>
	<4A427A97.9020409@macports.org>
	<BLU0-SMTP354489A052CCBC9C70057FC5370@phx.gbl>
Message-ID: <164866F9-CEF5-44FE-AD55-E932D3A5C88B@macports.org>


On Jun 24, 2009, at 15:03, Andre-John Mas wrote:

> On 24-Jun-2009, at 15:12, Joshua Root wrote:
>
>> I'm told that the compiler on Snow Leopard generates x86_64  
>> binaries by
>> default. So with the current MacPorts code, that is what you'll get
>> (unless you build universal, or the port adds -arch flags itself).
>>
>> The plan is to add a setting for the default target arch. MacPorts  
>> would
>> then attempt to always pass a -arch flag to the compiler (or -m32/- 
>> m64
>> for non-Apple compilers), and individual ports would need to make  
>> sure
>> that this is picked up by their build system if the default methods
>> don't suffice. The "sensible default" for this option would appear  
>> to be
>> x86_64 on Snow Leopard, and i386 or ppc on earlier OS releases  
>> according
>> to the hardware arch.
>
> Will this option be specifiable in a configuration, so that in the  
> short
> term we can test 64-bit compatibility in Leopard?

I think you can already test this by using the +universal variant and  
setting universal_archs to x86_64 in macports.conf.



From ryandesign at macports.org  Wed Jun 24 14:21:42 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 24 Jun 2009 16:21:42 -0500
Subject: Problem installing KDE/Amarok
In-Reply-To: <54522AA8-7FA1-4C45-AE58-FD15C433A27A@halblog.com>
References: <54522AA8-7FA1-4C45-AE58-FD15C433A27A@halblog.com>
Message-ID: <F1A9EF49-9E80-470F-9102-EEC478B1F8BB@macports.org>


On Jun 24, 2009, at 13:05, Hal Vaughan wrote:

> I just installed MacPorts yesterday.  I'm trying to install Amarok  
> and yesterday I typed "sudo port install amarok" yesterday.  It  
> took qt hours to build.  Last night, when I got home about 9 pm,  
> the terminal was not responding and clicking it gave me the  
> spinning pinwheel.  I can't scroll or anything.  Ports has a  
> message displayed: Installing kdebase4-runtime @4.2.4_0."  It's  
> been at that stage since 9 pm last night (it's now about 2 pm the  
> next day).  The terminal is locked up and I don't know if it's  
> still building KDE and installing or if it's locked up.
>
> I've asked for help on #kde-mac, but with 20 people in that group,  
> nobody seems active.
>
> I don't know if I should kill the terminal and therefore the ports  
> process or if it just takes that long.  My guess is that KDE is big  
> and it takes a lot of time and may take notable CPU resources, thus  
> locking up the terminal for a while.  If that's so, I can deal with  
> it, but for now, I can't run another instance of Terminal unless I  
> reboot, and I don't know if restarting the port command will just  
> put me in the same fix before.
>
> I'm on an iMac with OS X 10.5.7, a 2.4 Ghz Intel 2 core CPU with 4  
> GB of 667 Mhz DDR2 SDRAM.  Not the latest, but no slouch either.   
> Does it take over 17 hours to install KDE with such a system?
>
> Also I know that there are messages of commands I have to run on  
> the terminal, but I only see a few, so I don't know if rebooting  
> will mean I can't access any that have scrolled off the top yet.

Hmm. First, welcome to MacPorts!

qt4-mac does take hours to build, even on a nice system like that.  
KDE probably also takes hours, but that time should mostly be taken  
in the build phase. Once it reaches the installation phase, the port  
isn't even in control; MacPorts base is, and all it's doing is  
copying the contents of /opt/local/var/macports/build/(PORT)/work/ 
destroot into /opt/local/var/macports/software/(PORT)/(VERSION)_ 
(REVISION)_(VARIANTS). kdebase4-runtime could add something to that  
with a pre-install or post-install phase, but that port doesn't have  
one. In any case, I don't think the Terminal app itself should ever  
become unresponsive, no matter how much work MacPorts is doing. So  
I'm afraid something has gone wrong. If you cannot interact with the  
Terminal, you'll have to force-quit it or restart the computer as you  
said. Unfortunately, MacPorts does not save the output of its build  
progress, so if there are messages scrolled off the top that you  
cannot see or scroll up to now, they are lost.

After restarting Terminal or the computer, you can try again. You can  
use the "-d" flag ("port -d install amarok") to get a lot more  
information printed out. This will let you see what exactly a port  
was doing if and when it gets hung up. On the other hand, the vast  
quantity of output you will get means you will very likely miss any  
"you must do this after installing the port"-type messages that some  
ports print.


From jmr at macports.org  Wed Jun 24 14:33:34 2009
From: jmr at macports.org (Joshua Root)
Date: Thu, 25 Jun 2009 07:33:34 +1000
Subject: MacPorts and x86_64?
In-Reply-To: <164866F9-CEF5-44FE-AD55-E932D3A5C88B@macports.org>
References: <BLU0-SMTP872E265D84EA6AD00C6712C5370@phx.gbl>
	<4A427A97.9020409@macports.org>
	<BLU0-SMTP354489A052CCBC9C70057FC5370@phx.gbl>
	<164866F9-CEF5-44FE-AD55-E932D3A5C88B@macports.org>
Message-ID: <4A429BAE.8010104@macports.org>

On 2009-6-25 06:57, Ryan Schmidt wrote:
> 
> On Jun 24, 2009, at 15:03, Andre-John Mas wrote:
> 
>> On 24-Jun-2009, at 15:12, Joshua Root wrote:
>>
>>> I'm told that the compiler on Snow Leopard generates x86_64 binaries by
>>> default. So with the current MacPorts code, that is what you'll get
>>> (unless you build universal, or the port adds -arch flags itself).
>>>
>>> The plan is to add a setting for the default target arch. MacPorts would
>>> then attempt to always pass a -arch flag to the compiler (or -m32/-m64
>>> for non-Apple compilers), and individual ports would need to make sure
>>> that this is picked up by their build system if the default methods
>>> don't suffice. The "sensible default" for this option would appear to be
>>> x86_64 on Snow Leopard, and i386 or ppc on earlier OS releases according
>>> to the hardware arch.
>>
>> Will this option be specifiable in a configuration, so that in the short
>> term we can test 64-bit compatibility in Leopard?

The setting won't be exclusive to Snow Leopard once it exists.

- Josh

From hal at halblog.com  Wed Jun 24 14:47:52 2009
From: hal at halblog.com (Hal Vaughan)
Date: Wed, 24 Jun 2009 17:47:52 -0400
Subject: Problem installing KDE/Amarok
In-Reply-To: <F1A9EF49-9E80-470F-9102-EEC478B1F8BB@macports.org>
References: <54522AA8-7FA1-4C45-AE58-FD15C433A27A@halblog.com>
	<F1A9EF49-9E80-470F-9102-EEC478B1F8BB@macports.org>
Message-ID: <5F8AD1F2-747C-4ADA-889D-ABB2111138B2@halblog.com>


On Jun 24, 2009, at 5:21 PM, Ryan Schmidt wrote:

>
> On Jun 24, 2009, at 13:05, Hal Vaughan wrote:
>
>> I just installed MacPorts yesterday.  I'm trying to install Amarok  
>> and yesterday I typed "sudo port install amarok" yesterday.  It  
>> took qt hours to build.  Last night, when I got home about 9 pm,  
>> the terminal was not responding and clicking it gave me the  
>> spinning pinwheel.  I can't scroll or anything.  Ports has a  
>> message displayed: Installing kdebase4-runtime @4.2.4_0."  It's  
>> been at that stage since 9 pm last night (it's now about 2 pm the  
>> next day).  The terminal is locked up and I don't know if it's  
>> still building KDE and installing or if it's locked up.
>>
>> I've asked for help on #kde-mac, but with 20 people in that group,  
>> nobody seems active.
>>
>> I don't know if I should kill the terminal and therefore the ports  
>> process or if it just takes that long.  My guess is that KDE is big  
>> and it takes a lot of time and may take notable CPU resources, thus  
>> locking up the terminal for a while.  If that's so, I can deal with  
>> it, but for now, I can't run another instance of Terminal unless I  
>> reboot, and I don't know if restarting the port command will just  
>> put me in the same fix before.
>>
>> I'm on an iMac with OS X 10.5.7, a 2.4 Ghz Intel 2 core CPU with 4  
>> GB of 667 Mhz DDR2 SDRAM.  Not the latest, but no slouch either.   
>> Does it take over 17 hours to install KDE with such a system?
>>
>> Also I know that there are messages of commands I have to run on  
>> the terminal, but I only see a few, so I don't know if rebooting  
>> will mean I can't access any that have scrolled off the top yet.
>
> Hmm. First, welcome to MacPorts!
>
> qt4-mac does take hours to build, even on a nice system like that.  
> KDE probably also takes hours, but that time should mostly be taken  
> in the build phase. Once it reaches the installation phase, the port  
> isn't even in control; MacPorts base is, and all it's doing is  
> copying the contents of /opt/local/var/macports/build/(PORT)/work/ 
> destroot into /opt/local/var/macports/software/(PORT)/ 
> (VERSION)_(REVISION)_(VARIANTS). kdebase4-runtime could add  
> something to that with a pre-install or post-install phase, but that  
> port doesn't have one. In any case, I don't think the Terminal app  
> itself should ever become unresponsive, no matter how much work  
> MacPorts is doing. So I'm afraid something has gone wrong. If you  
> cannot interact with the Terminal, you'll have to force-quit it or  
> restart the computer as you said. Unfortunately, MacPorts does not  
> save the output of its build progress, so if there are messages  
> scrolled off the top that you cannot see or scroll up to now, they  
> are lost.

I figured they'd be lost if I had to kill the terminal.  Of course,  
I'm not 100% sure that this is the issue.  For all I know, the process  
could have been okay and it could be something else that crashed it.   
(Come to think of it, there was an ssh connection, but it's a program  
I'm always running in the b.g.)  I figure in worst case, since it's  
the first thing I'm installing, I could wipe out any KDE directory in  
Applications and just wipe all of /opt, reinstall MacPorts and restart.

Is there any place else KDE would store files that I'd have to clear  
out if I do that?

> After restarting Terminal or the computer, you can try again. You  
> can use the "-d" flag ("port -d install amarok") to get a lot more  
> information printed out. This will let you see what exactly a port  
> was doing if and when it gets hung up. On the other hand, the vast  
> quantity of output you will get means you will very likely miss any  
> "you must do this after installing the port"-type messages that some  
> ports print.

I was also going to see if I could find a list somewhere of all the  
messages from KDE.  It looks like each package is giving me the same  
message at the start and the end.

I'll most likely wipe out /opt and just start clean, since I don't  
have any other packages done with MacPorts yet.  I don't mind letting  
it rebuild qt overnight.

Thanks for the help on this!


Hal

From ryandesign at macports.org  Wed Jun 24 15:02:21 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 24 Jun 2009 17:02:21 -0500
Subject: Problem installing KDE/Amarok
In-Reply-To: <5F8AD1F2-747C-4ADA-889D-ABB2111138B2@halblog.com>
References: <54522AA8-7FA1-4C45-AE58-FD15C433A27A@halblog.com>
	<F1A9EF49-9E80-470F-9102-EEC478B1F8BB@macports.org>
	<5F8AD1F2-747C-4ADA-889D-ABB2111138B2@halblog.com>
Message-ID: <44B08E94-FBA8-4E16-9635-54D8EA225DD9@macports.org>

On Jun 24, 2009, at 16:47, Hal Vaughan wrote:

> I figured they'd be lost if I had to kill the terminal.  Of course,  
> I'm not 100% sure that this is the issue.  For all I know, the  
> process could have been okay and it could be something else that  
> crashed it.  (Come to think of it, there was an ssh connection, but  
> it's a program I'm always running in the b.g.)  I figure in worst  
> case, since it's the first thing I'm installing, I could wipe out  
> any KDE directory in Applications and just wipe all of /opt,  
> reinstall MacPorts and restart.
>
> Is there any place else KDE would store files that I'd have to  
> clear out if I do that?
>
>> After restarting Terminal or the computer, you can try again. You  
>> can use the "-d" flag ("port -d install amarok") to get a lot more  
>> information printed out. This will let you see what exactly a port  
>> was doing if and when it gets hung up. On the other hand, the vast  
>> quantity of output you will get means you will very likely miss  
>> any "you must do this after installing the port"-type messages  
>> that some ports print.
>
> I was also going to see if I could find a list somewhere of all the  
> messages from KDE.  It looks like each package is giving me the  
> same message at the start and the end.
>
> I'll most likely wipe out /opt and just start clean, since I don't  
> have any other packages done with MacPorts yet.  I don't mind  
> letting it rebuild qt overnight.

If you want to do that, you should follow the uninstall instructions  
shown here:

http://trac.macports.org/wiki/FAQ#HowdoIremoveoruninstallMacPorts



From hal at halblog.com  Wed Jun 24 15:18:45 2009
From: hal at halblog.com (Hal Vaughan)
Date: Wed, 24 Jun 2009 18:18:45 -0400
Subject: Problem installing KDE/Amarok
In-Reply-To: <44B08E94-FBA8-4E16-9635-54D8EA225DD9@macports.org>
References: <54522AA8-7FA1-4C45-AE58-FD15C433A27A@halblog.com>
	<F1A9EF49-9E80-470F-9102-EEC478B1F8BB@macports.org>
	<5F8AD1F2-747C-4ADA-889D-ABB2111138B2@halblog.com>
	<44B08E94-FBA8-4E16-9635-54D8EA225DD9@macports.org>
Message-ID: <B2C75739-15EC-481D-AC05-AFECFE539149@halblog.com>


On Jun 24, 2009, at 6:02 PM, Ryan Schmidt wrote:

> On Jun 24, 2009, at 16:47, Hal Vaughan wrote:
>
>> I figured they'd be lost if I had to kill the terminal.  Of course,  
>> I'm not 100% sure that this is the issue.  For all I know, the  
>> process could have been okay and it could be something else that  
>> crashed it.  (Come to think of it, there was an ssh connection, but  
>> it's a program I'm always running in the b.g.)  I figure in worst  
>> case, since it's the first thing I'm installing, I could wipe out  
>> any KDE directory in Applications and just wipe all of /opt,  
>> reinstall MacPorts and restart.
>>
>> Is there any place else KDE would store files that I'd have to  
>> clear out if I do that?
>>
>>> After restarting Terminal or the computer, you can try again. You  
>>> can use the "-d" flag ("port -d install amarok") to get a lot more  
>>> information printed out. This will let you see what exactly a port  
>>> was doing if and when it gets hung up. On the other hand, the vast  
>>> quantity of output you will get means you will very likely miss  
>>> any "you must do this after installing the port"-type messages  
>>> that some ports print.
>>
>> I was also going to see if I could find a list somewhere of all the  
>> messages from KDE.  It looks like each package is giving me the  
>> same message at the start and the end.
>>
>> I'll most likely wipe out /opt and just start clean, since I don't  
>> have any other packages done with MacPorts yet.  I don't mind  
>> letting it rebuild qt overnight.
>
> If you want to do that, you should follow the uninstall instructions  
> shown here:
>
> http://trac.macports.org/wiki/FAQ#HowdoIremoveoruninstallMacPorts

How is that at dealing with partially installed packages, like the kde  
one I'm dealing with?


Hal

From tangle1 at mindspring.com  Wed Jun 24 16:34:20 2009
From: tangle1 at mindspring.com (tangle1 at mindspring.com)
Date: Wed, 24 Jun 2009 19:34:20 -0400 (EDT)
Subject: problem with py2app and Qt/PyQt
Message-ID: <6921115.1245886461057.JavaMail.root@elwamui-chisos.atl.sa.earthlink.net>

Thank you Ryan, Olivier, James for your feedback. When I came in this morning, the port install of py25-pyqt4 was complete. 

I have a problem with my app build using py2app ... perhaps you can help. Its related to Qt/PyQt and possibly an issue with QImage and missing jpg encoder. 

My python script uses PyQt to display 8 jpg image sequences in a multi-panel viewport. These images are generated from 8 cameras. I have a feeling the app cannot find jpg encoder. However everything works perfectly when I run same script directly from python. 
This works: 
----------------------------
> which python
/opt/local/bin/python
>python mvrv.py
----------------------

But app created from py2app does not display images:
I created setup.py file according to instructions on the web and ran "python setup.py py2app".  
---------------------------------------------------------
from setuptools import setup

APP = ['mvrv.py']
OPTIONS = {'argv_emulation': True, 'includes': ['sip','PyQt4._qt','PyQt4.QtCore','PyQt4.QtGui'],
			'excludes':['PyQt4.QtDesigner','PyQt4.QtNetwork','PyQt4.QtOpenGl','PyQt4.QtScript','PyQt4.QtSql','PyQt4.QtTest','PyQt4.QtWebKit','PyQt4.QtXml','PyQt4.phonon']}
			
setup(
	app=APP,
	options={'py2app': OPTIONS},
	setup_requires=['py2app'],
)

------------------------------------

... so when I double-click mvrv.app under dist folder, the GUI launches fine. The interface shows image frame numbers as caching progresses, but the numbers change fast and no images are displayed. I saw this behavior when I first began development on Windows. In that case, I was getting output from terminal shell ... something like "QImage() called with null image". Someone said this was due to missing jpg encoder and our windows build engineer rebuilt my python environment ... and everything worked. 

Back in mac land, I ran my script, mvrv.py, via python interpreter. In this case, caching proceeded as expected and image playback worked. Since I don't get broken behavior from python interpreter I can only guess that somehow in the app build something is missing with respect to jpg encoding ... because the GUI behaviour totally works in all other respects.

Any help, hints would be greatly appreciated. 

Thanks,

Suzanne 

From ryandesign at macports.org  Wed Jun 24 20:06:53 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 24 Jun 2009 22:06:53 -0500
Subject: Problem installing KDE/Amarok
In-Reply-To: <B2C75739-15EC-481D-AC05-AFECFE539149@halblog.com>
References: <54522AA8-7FA1-4C45-AE58-FD15C433A27A@halblog.com>
	<F1A9EF49-9E80-470F-9102-EEC478B1F8BB@macports.org>
	<5F8AD1F2-747C-4ADA-889D-ABB2111138B2@halblog.com>
	<44B08E94-FBA8-4E16-9635-54D8EA225DD9@macports.org>
	<B2C75739-15EC-481D-AC05-AFECFE539149@halblog.com>
Message-ID: <C915200C-6679-4A03-846E-4C61B281C1BE@macports.org>


On Jun 24, 2009, at 17:18, Hal Vaughan wrote:

> On Jun 24, 2009, at 6:02 PM, Ryan Schmidt wrote:
>
>> If you want to do that, you should follow the uninstall  
>> instructions shown here:
>>
>> http://trac.macports.org/wiki/FAQ#HowdoIremoveoruninstallMacPorts
>
> How is that at dealing with partially installed packages, like the  
> kde one I'm dealing with?

It should work correctly.


From napu at mac.com  Thu Jun 25 01:41:04 2009
From: napu at mac.com (Panu Korpela)
Date: Thu, 25 Jun 2009 11:41:04 +0300
Subject: apr-util-1.3.4: checksum error when trying to install
Message-ID: <E14D2515-BFD7-4C17-800E-47AB82D40BC5@mac.com>

Hi!

I tried to install subversion port and it requires apr-util-1.3.4.  
However the latter one refuses to install:

--->  Verifying checksum(s) for apr-util
Error: Checksum (md5) mismatch for apr-util-1.3.4.tar.bz2
Error: Checksum (sha1) mismatch for apr-util-1.3.4.tar.bz2
Error: Checksum (rmd160) mismatch for apr-util-1.3.4.tar.bz2
Error: Target org.macports.checksum returned: Unable to verify file  
checksums
Error: The following dependencies failed to build: apr-util serf
Error: Status 1 encountered during processing.

Br,
      Mr Panu Korpela


From mdcrawford at gmail.com  Thu Jun 25 03:08:08 2009
From: mdcrawford at gmail.com (Michael Crawford)
Date: Thu, 25 Jun 2009 03:08:08 -0700
Subject: MacPorts and x86_64?
In-Reply-To: <4A429BAE.8010104@macports.org>
References: <BLU0-SMTP872E265D84EA6AD00C6712C5370@phx.gbl>
	<4A427A97.9020409@macports.org>
	<BLU0-SMTP354489A052CCBC9C70057FC5370@phx.gbl>
	<164866F9-CEF5-44FE-AD55-E932D3A5C88B@macports.org>
	<4A429BAE.8010104@macports.org>
Message-ID: <dc9f86e80906250308s362c7837t4703f50e0331634a@mail.gmail.com>

It's likely that some software either won't build as 64-bit, or if it
builds it won't work right.

It's not in MacPorts (yet), but ZooLib won't build as 64-bit, because
it has a header file that sets up macros to identity the target
platform and processor, and we just haven't implemented 64-bit builds
yet.  I don't think the code itself would have any problems with
64-bit, bit if you try to compile it that way, the header gives you a
#error.

(http://www.zoolib.org/)

If there are any such programs in MacPorts, you'll need to identify
them and restrict their builds to 32-bit until they can be updated.

(I would be happy to maintain a ZooLib port for MacPorts, but not quite yet.)

Mike
-- 
Michael David Crawford
mdcrawford at gmail dot com

   GoingWare's Bag of Programming Tricks
      http://www.goingware.com/tips/

From peteo at oakleystudio.com  Thu Jun 25 07:09:23 2009
From: peteo at oakleystudio.com (Peter Oakley)
Date: Thu, 25 Jun 2009 10:09:23 -0400
Subject: PHP upgrade to v5.2.10
Message-ID: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>

Last night I was upgrading my web server to PHP v5.2.10 (from v5.2.8)  
and everything seemed to go ok, no warnings or major gotchas. But  
once I began using it, I could see there were some real problems with  
the time() and date() functions. It's possible that I'm just using  
these two functions in ways that are either wrong (but have up to now  
served to accomplish the task I was seeking to do) or are no longer  
allowed, for security reasons, in which case I will need to develop a  
work-around. Or something is going wrong with the update. I'm writing  
to this list to see if anyone else has experienced this same problem,  
or if you all might have some ideas as to what's going on here.

Some additional info: I am running PHP on a Dual G4 PPC Mac, Apache  
(that comes with Mac OS X, not Apache 2), and MySQL from MacPorts.


    - Pete O




From brad at pixilla.com  Thu Jun 25 07:12:30 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Thu, 25 Jun 2009 07:12:30 -0700
Subject: PHP upgrade to v5.2.10
In-Reply-To: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>
Message-ID: <C7C0DDF1-4FCA-4D51-8F96-B83CECABF221@pixilla.com>


On Jun 25, 2009, at 7:09 AM, Peter Oakley wrote:

> Last night I was upgrading my web server to PHP v5.2.10 (from  
> v5.2.8) and everything seemed to go ok, no warnings or major  
> gotchas. But once I began using it, I could see there were some real  
> problems with the time() and date() functions. It's possible that  
> I'm just using these two functions in ways that are either wrong  
> (but have up to now served to accomplish the task I was seeking to  
> do) or are no longer allowed, for security reasons, in which case I  
> will need to develop a work-around. Or something is going wrong with  
> the update. I'm writing to this list to see if anyone else has  
> experienced this same problem, or if you all might have some ideas  
> as to what's going on here.

Give an example of your usage of time() and date(), what you expect  
and what you are getting.

// Brad

From macsforever2000 at macports.org  Thu Jun 25 07:29:59 2009
From: macsforever2000 at macports.org (Frank Schima)
Date: Thu, 25 Jun 2009 08:29:59 -0600
Subject: apr-util-1.3.4: checksum error when trying to install
In-Reply-To: <E14D2515-BFD7-4C17-800E-47AB82D40BC5@mac.com>
References: <E14D2515-BFD7-4C17-800E-47AB82D40BC5@mac.com>
Message-ID: <8540C544-715E-4031-933D-D7B8156B1552@macports.org>


On Jun 25, 2009, at 2:41 AM, Panu Korpela wrote:

> I tried to install subversion port and it requires apr-util-1.3.4.
> However the latter one refuses to install:
>
> --->  Verifying checksum(s) for apr-util
> Error: Checksum (md5) mismatch for apr-util-1.3.4.tar.bz2
> Error: Checksum (sha1) mismatch for apr-util-1.3.4.tar.bz2
> Error: Checksum (rmd160) mismatch for apr-util-1.3.4.tar.bz2
> Error: Target org.macports.checksum returned: Unable to verify file
> checksums
> Error: The following dependencies failed to build: apr-util serf
> Error: Status 1 encountered during processing.

You need to update your ports tree, the current version of apr-util is  
1.3.7.

sudo port selfupdate
sudo port install subversion


Cheers!
Frank


From peteo at oakleystudio.com  Thu Jun 25 07:43:07 2009
From: peteo at oakleystudio.com (Peter Oakley)
Date: Thu, 25 Jun 2009 10:43:07 -0400
Subject: PHP upgrade to v5.2.10
In-Reply-To: <C7C0DDF1-4FCA-4D51-8F96-B83CECABF221@pixilla.com>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>
	<C7C0DDF1-4FCA-4D51-8F96-B83CECABF221@pixilla.com>
Message-ID: <C37A006E-3407-4461-80D0-F1CD37EECDE3@oakleystudio.com>

Here is an example usage of the date() and time() functions:

snippetStart - - - - - -

$timestamp = time();
//echo $timestamp;
$thisYear = date('Y', $timestamp);
echo $thisYear;

- - - - - - snippetEnd

After the PHP upgrade to v5.2.10, this yields "0000" for $thisYear.  
Prior to the upgrade, $thisYear would be set to "2009". I also tried  
using the time function directly within the date function: $thisYear  
= date('Y', time()); Same result.

One other possibly important detail: I've installed a variant: php5  
+apache +macosx +mysql5 +t1lib

    - Pete O



On Jun 25, 2009, at 10:12 AM, Bradley Giesbrecht wrote:

>
> On Jun 25, 2009, at 7:09 AM, Peter Oakley wrote:
>
>> Last night I was upgrading my web server to PHP v5.2.10 (from  
>> v5.2.8) and everything seemed to go ok, no warnings or major  
>> gotchas. But once I began using it, I could see there were some  
>> real problems with the time() and date() functions. It's possible  
>> that I'm just using these two functions in ways that are either  
>> wrong (but have up to now served to accomplish the task I was  
>> seeking to do) or are no longer allowed, for security reasons, in  
>> which case I will need to develop a work-around. Or something is  
>> going wrong with the update. I'm writing to this list to see if  
>> anyone else has experienced this same problem, or if you all might  
>> have some ideas as to what's going on here.
>
> Give an example of your usage of time() and date(), what you expect  
> and what you are getting.
>
> // Brad


From devans at macports.org  Thu Jun 25 07:56:08 2009
From: devans at macports.org (David Evans)
Date: Thu, 25 Jun 2009 07:56:08 -0700
Subject: PHP upgrade to v5.2.10
In-Reply-To: <C37A006E-3407-4461-80D0-F1CD37EECDE3@oakleystudio.com>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>	<C7C0DDF1-4FCA-4D51-8F96-B83CECABF221@pixilla.com>
	<C37A006E-3407-4461-80D0-F1CD37EECDE3@oakleystudio.com>
Message-ID: <4A439008.7020705@macports.org>

Peter Oakley wrote:
> Here is an example usage of the date() and time() functions:
>
> snippetStart - - - - - -
>
> $timestamp = time();
> //echo $timestamp;
> $thisYear = date('Y', $timestamp);
> echo $thisYear;
>
> - - - - - - snippetEnd
>
> After the PHP upgrade to v5.2.10, this yields "0000" for $thisYear. 
> Prior to the upgrade, $thisYear would be set to "2009". I also tried 
> using the time function directly within the date function: $thisYear = 
> date('Y', time()); Same result.
>
> One other possibly important detail: I've installed a variant: php5 
> +apache +macosx +mysql5 +t1lib
>
>    - Pete O
>
>
>
> On Jun 25, 2009, at 10:12 AM, Bradley Giesbrecht wrote:
>
>>
>> On Jun 25, 2009, at 7:09 AM, Peter Oakley wrote:
>>
>>> Last night I was upgrading my web server to PHP v5.2.10 (from 
>>> v5.2.8) and everything seemed to go ok, no warnings or major 
>>> gotchas. But once I began using it, I could see there were some real 
>>> problems with the time() and date() functions. It's possible that 
>>> I'm just using these two functions in ways that are either wrong 
>>> (but have up to now served to accomplish the task I was seeking to 
>>> do) or are no longer allowed, for security reasons, in which case I 
>>> will need to develop a work-around. Or something is going wrong with 
>>> the update. I'm writing to this list to see if anyone else has 
>>> experienced this same problem, or if you all might have some ideas 
>>> as to what's going on here.
>>
>> Give an example of your usage of time() and date(), what you expect 
>> and what you are getting.
>>
>> // Brad
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
You should not specify +macosx on the command line.  It is selected
automatically based on your current platform.


From face at CentosPrime.COM  Thu Jun 25 09:07:16 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Thu, 25 Jun 2009 09:07:16 -0700
Subject: PHP upgrade to v5.2.10
In-Reply-To: <C37A006E-3407-4461-80D0-F1CD37EECDE3@oakleystudio.com>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>
	<C7C0DDF1-4FCA-4D51-8F96-B83CECABF221@pixilla.com>
	<C37A006E-3407-4461-80D0-F1CD37EECDE3@oakleystudio.com>
Message-ID: <FC9F2566-6EB4-454D-80A8-F2AFD64B77C3@centosprime.com>

On 2009-06-25 , at 07:43 , Peter Oakley wrote:

> snippetStart - - - - - -
>
> $timestamp = time();
> //echo $timestamp;
> $thisYear = date('Y', $timestamp);
> echo $thisYear;
>
> - - - - - - snippetEnd
>
> After the PHP upgrade to v5.2.10, this yields "0000" for $thisYear.  
> Prior to the upgrade, $thisYear would be set to "2009". I also tried  
> using the time function directly within the date function: $thisYear  
> = date('Y', time()); Same result.
>
> One other possibly important detail: I've installed a variant: php5  
> +apache +macosx +mysql5 +t1lib


face at mac:~:129 $ cat foo.php
<?php
$timestamp = time();
$thisYear = date('Y', $timestamp);
echo $thisYear . "\n";
?>
face at mac:~:130 $ which php
/opt/local/bin/php
face at mac:~:131 $ php --version
PHP 5.2.10 (cli) (built: Jun 20 2009 08:25:00)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies
face at mac:~:132 $ php <foo.php
2009
face at mac:~:133 $

My php is

     php5 @5.2.10_0+apache2+macosx+mysql5+pear (active)

face at mac:~:134 $ uname -a
Darwin mac.centosprime.com 9.7.0 Darwin Kernel Version 9.7.0: Tue Mar  
31 22:52:17 PDT 2009; root:xnu-1228.12.14~1/RELEASE_I386 i386

Which version of OS X are you running?

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From brad at pixilla.com  Thu Jun 25 09:30:30 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Thu, 25 Jun 2009 09:30:30 -0700
Subject: PHP upgrade to v5.2.10
In-Reply-To: <C37A006E-3407-4461-80D0-F1CD37EECDE3@oakleystudio.com>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>
	<C7C0DDF1-4FCA-4D51-8F96-B83CECABF221@pixilla.com>
	<C37A006E-3407-4461-80D0-F1CD37EECDE3@oakleystudio.com>
Message-ID: <C8B02665-65EA-4F49-A70A-80A7B4CCFD4C@pixilla.com>


On Jun 25, 2009, at 7:43 AM, Peter Oakley wrote:

> Here is an example usage of the date() and time() functions:
>
> snippetStart - - - - - -
>
> $timestamp = time();
> //echo $timestamp;
> $thisYear = date('Y', $timestamp);
> echo $thisYear;
>
> - - - - - - snippetEnd
>
> After the PHP upgrade to v5.2.10, this yields "0000" for $thisYear.  
> Prior to the upgrade, $thisYear would be set to "2009". I also tried  
> using the time function directly within the date function: $thisYear  
> = date('Y', time()); Same result.
>
> One other possibly important detail: I've installed a variant: php5  
> +apache +macosx +mysql5 +t1lib

bash-3.2# port installed php5
The following ports are currently installed:
   php5 @5.2.10_0+apache2+imap+macosx+mysql5+pear+pspell+readline 
+sqlite+tidy (active)
bash-3.2# which php
/opt/local/bin/php
bash-3.2# php --version
PHP 5.2.10 (cli) (built: Jun 25 2009 09:13:39)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies
bash-3.2# php -r '$timestamp=time();echo "{$timestamp}\n"; 
$thisYear=date("Y", $timestamp);echo "{$thisYear}\n";'
1245947391
2009
bash-3.2#


From peteo at oakleystudio.com  Thu Jun 25 10:41:21 2009
From: peteo at oakleystudio.com (Peter Oakley)
Date: Thu, 25 Jun 2009 13:41:21 -0400
Subject: PHP upgrade to v5.2.10
In-Reply-To: <FC9F2566-6EB4-454D-80A8-F2AFD64B77C3@centosprime.com>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>
	<C7C0DDF1-4FCA-4D51-8F96-B83CECABF221@pixilla.com>
	<C37A006E-3407-4461-80D0-F1CD37EECDE3@oakleystudio.com>
	<FC9F2566-6EB4-454D-80A8-F2AFD64B77C3@centosprime.com>
Message-ID: <DAB12ED9-847B-4114-89E4-F28AC11492A3@oakleystudio.com>

Bradley, and Chris, you've both suggested some good ways to determine  
whether these two PHP functions are working right via command line --  
thanks.

My web server is running Mac OS X v10.4.11 with all available  
Software Updates installed. I am now beginning the process of setting  
up a test server to try these things...

    - Pete O



On Jun 25, 2009, at 12:07 PM, Chris Janton wrote:

> Which version of OS X are you running?


From jmr at macports.org  Thu Jun 25 15:03:46 2009
From: jmr at macports.org (Joshua Root)
Date: Fri, 26 Jun 2009 08:03:46 +1000
Subject: apr-util-1.3.4: checksum error when trying to install
In-Reply-To: <8540C544-715E-4031-933D-D7B8156B1552@macports.org>
References: <E14D2515-BFD7-4C17-800E-47AB82D40BC5@mac.com>
	<8540C544-715E-4031-933D-D7B8156B1552@macports.org>
Message-ID: <4A43F442.4020107@macports.org>

On 2009-6-26 00:29, Frank Schima wrote:
> 
> On Jun 25, 2009, at 2:41 AM, Panu Korpela wrote:
> 
>> I tried to install subversion port and it requires apr-util-1.3.4.
>> However the latter one refuses to install:
>>
>> --->  Verifying checksum(s) for apr-util
>> Error: Checksum (md5) mismatch for apr-util-1.3.4.tar.bz2
>> Error: Checksum (sha1) mismatch for apr-util-1.3.4.tar.bz2
>> Error: Checksum (rmd160) mismatch for apr-util-1.3.4.tar.bz2
>> Error: Target org.macports.checksum returned: Unable to verify file
>> checksums
>> Error: The following dependencies failed to build: apr-util serf
>> Error: Status 1 encountered during processing.
> 
> You need to update your ports tree, the current version of apr-util is
> 1.3.7.
> 
> sudo port selfupdate
> sudo port install subversion

I'd also do a `sudo port upgrade outdated` in between those commands.

- Josh

From peteo at oakleystudio.com  Thu Jun 25 15:10:36 2009
From: peteo at oakleystudio.com (Peter Oakley)
Date: Thu, 25 Jun 2009 18:10:36 -0400
Subject: PHP upgrade to v5.2.10
In-Reply-To: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>
Message-ID: <0DC19D17-8CB2-460F-876A-B9706821651F@oakleystudio.com>

Looks like this problem with the date('Y') function was a PHP bug. It  
showed up on Mac OS X (my system) and on Mac OS X Server, both  
v10.4.11, when upgrading from PHP v5.2.8 or v5.2.9 to v5.2.10, and  
the bug also existed in v5.3.0 RC2. Similar problem with the DateTime 
() function. The issue has also been demonstrated on Debian Lenny PPC  
and on Solaris Sparc version 9. Here's a link for reference:
http://bugs.php.net/bug.php?id=48276

See the last message of the bug track dated [21 Jun 10:20pm UTC] from  
scottmac at php.net (four days ago). This bug has been fixed in current  
builds of PHP v5.2.10. Now I'm wondering: How long is it likely to  
take for this fixed version of PHP5 v5.2.10 to make its way into  
MacPorts?

    - Pete O



On Jun 25, 2009, at 10:09 AM, Peter Oakley wrote:

> Last night I was upgrading my web server to PHP v5.2.10 (from  
> v5.2.8) and everything seemed to go ok, no warnings or major  
> gotchas. But once I began using it, I could see there were some  
> real problems with the time() and date() functions. It's possible  
> that I'm just using these two functions in ways that are either  
> wrong (but have up to now served to accomplish the task I was  
> seeking to do) or are no longer allowed, for security reasons, in  
> which case I will need to develop a work-around. Or something is  
> going wrong with the update. I'm writing to this list to see if  
> anyone else has experienced this same problem, or if you all might  
> have some ideas as to what's going on here.
>
> Some additional info: I am running PHP on a Dual G4 PPC Mac, Apache  
> (that comes with Mac OS X, not Apache 2), and MySQL from MacPorts.
>
>
>    - Pete O
>
>
>


From ryandesign at macports.org  Thu Jun 25 15:21:18 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 25 Jun 2009 17:21:18 -0500
Subject: PHP upgrade to v5.2.10
In-Reply-To: <0DC19D17-8CB2-460F-876A-B9706821651F@oakleystudio.com>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>
	<0DC19D17-8CB2-460F-876A-B9706821651F@oakleystudio.com>
Message-ID: <456B4EFB-F869-483D-AD48-CA4D9EA928EA@macports.org>

On Jun 25, 2009, at 17:10, Peter Oakley wrote:

> Looks like this problem with the date('Y') function was a PHP bug.  
> It showed up on Mac OS X (my system) and on Mac OS X Server, both  
> v10.4.11, when upgrading from PHP v5.2.8 or v5.2.9 to v5.2.10, and  
> the bug also existed in v5.3.0 RC2. Similar problem with the  
> DateTime() function. The issue has also been demonstrated on Debian  
> Lenny PPC and on Solaris Sparc version 9. Here's a link for reference:
> http://bugs.php.net/bug.php?id=48276
>
> See the last message of the bug track dated [21 Jun 10:20pm UTC]  
> from scottmac at php.net (four days ago). This bug has been fixed in  
> current builds of PHP v5.2.10. Now I'm wondering: How long is it  
> likely to take for this fixed version of PHP5 v5.2.10 to make its  
> way into MacPorts?

I see they have fixed the problem in CVS, but they have not told us  
how they fixed it. So we either wait for 5.2.11 and update the port  
to that version, or someone has to find out what patch fixed the  
problem and I can apply that patch in the portfile.



From face at CentosPrime.COM  Thu Jun 25 15:55:47 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Thu, 25 Jun 2009 15:55:47 -0700
Subject: PHP upgrade to v5.2.10
In-Reply-To: <C37A006E-3407-4461-80D0-F1CD37EECDE3@oakleystudio.com>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>
	<C7C0DDF1-4FCA-4D51-8F96-B83CECABF221@pixilla.com>
	<C37A006E-3407-4461-80D0-F1CD37EECDE3@oakleystudio.com>
Message-ID: <6FDCF6F8-149F-439F-8BD1-BDE6D6531356@centosprime.com>

On 2009-06-25 , at 07:43 , Peter Oakley wrote:

> After the PHP upgrade to v5.2.10, this yields "0000" for $thisYear.  
> Prior to the upgrade, $thisYear would be set to "2009". I also tried  
> using the time function directly within the date function: $thisYear  
> = date('Y', time()); Same result.
>
> One other possibly important detail: I've installed a variant: php5  
> +apache +macosx +mysql5 +t1lib


Looks like a PPC only problem? From my G4

admin at x:macports:133 $ which php
/opt/local/bin/php
admin at x:macports:134 $ php --version
PHP 5.2.10 (cli) (built: Jun 25 2009 09:22:38)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies
admin at x:macports:135 $ php <foo.php
0000
admin at x:macports:136 $ sudo port deactivate php5 @5.2.10_0+apache 
+darwin_7+macosx+mysql5+pear
Password:
--->  Deactivating php5 @5.2.10_0+apache+darwin_7+macosx+mysql5+pear
admin at x:macports:137 $ sudo port activate php5 @5.2.6_2+apache 
+darwin_7+macosx+mysql5+pear
--->  Activating php5 @5.2.6_2+apache+darwin_7+macosx+mysql5+pear
admin at x:macports:138 $ php <foo.php
2009

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From hal at halblog.com  Thu Jun 25 17:24:36 2009
From: hal at halblog.com (Hal Vaughan)
Date: Thu, 25 Jun 2009 20:24:36 -0400
Subject: Yet Another Problem Installing Amarok
Message-ID: <FDDD2DD9-34AF-424C-A786-185A14977702@halblog.com>

My last problem is cleared now -- it froze on installing kdebase4- 
runtime.  When I got it all working (as in rebooted and updated some  
stuff from Apple), I ran "sudo port install amarok" and it went  
through a lot of stuff, then I'm stuck with this:

--->  Fetching taglib-devel
Error: Target org.macports.fetch returned: Subversion check out failed
Error: The following dependencies failed to build: taglib-devel taglib- 
extras
Error: Status 1 encountered during processing.

When I saw that, it sounded like it had a problem reading data from an  
svn repository, so I waited and tried it again, in case a site was  
down.  Still no luck.

So what is actually going on here and how can I fix it?  I tried  
Google, but didn't see much info on it and when I googled the error  
message, I found no hits!

I'm on an iMac with OS X 10.5.7, a 2.4 Ghz Intel 2 core CPU with 4 GB  
of 667 Mhz DDR2 SDRAM.

Thanks for any insight or info on this!



Hal

From ryandesign at macports.org  Thu Jun 25 17:24:56 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 25 Jun 2009 19:24:56 -0500
Subject: PHP upgrade to v5.2.10
In-Reply-To: <6FDCF6F8-149F-439F-8BD1-BDE6D6531356@centosprime.com>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>
	<C7C0DDF1-4FCA-4D51-8F96-B83CECABF221@pixilla.com>
	<C37A006E-3407-4461-80D0-F1CD37EECDE3@oakleystudio.com>
	<6FDCF6F8-149F-439F-8BD1-BDE6D6531356@centosprime.com>
Message-ID: <852CA183-7C70-44CD-9231-B1B898C79189@macports.org>


On Jun 25, 2009, at 17:55, Chris Janton wrote:

> On 2009-06-25 , at 07:43 , Peter Oakley wrote:
>
>> After the PHP upgrade to v5.2.10, this yields "0000" for  
>> $thisYear. Prior to the upgrade, $thisYear would be set to "2009".  
>> I also tried using the time function directly within the date  
>> function: $thisYear = date('Y', time()); Same result.

> Looks like a PPC only problem?

Yes, that seems to be the consensus.



From ryandesign at macports.org  Thu Jun 25 17:52:01 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 25 Jun 2009 19:52:01 -0500
Subject: Yet Another Problem Installing Amarok
In-Reply-To: <FDDD2DD9-34AF-424C-A786-185A14977702@halblog.com>
References: <FDDD2DD9-34AF-424C-A786-185A14977702@halblog.com>
Message-ID: <0A14CD35-0CD7-4A84-B86C-4A6DBBC2C954@macports.org>


On Jun 25, 2009, at 19:24, Hal Vaughan wrote:

> My last problem is cleared now -- it froze on installing kdebase4- 
> runtime.  When I got it all working (as in rebooted and updated  
> some stuff from Apple), I ran "sudo port install amarok" and it  
> went through a lot of stuff, then I'm stuck with this:
>
> --->  Fetching taglib-devel
> Error: Target org.macports.fetch returned: Subversion check out failed
> Error: The following dependencies failed to build: taglib-devel  
> taglib-extras
> Error: Status 1 encountered during processing.
>
> When I saw that, it sounded like it had a problem reading data from  
> an svn repository, so I waited and tried it again, in case a site  
> was down.  Still no luck.
>
> So what is actually going on here and how can I fix it?  I tried  
> Google, but didn't see much info on it and when I googled the error  
> message, I found no hits!

taglib-devel wants to check out its files from the KDE project's  
anonymous Subversion repository, which seems not to be working for  
you. This has been reported before, with no solution listed so far:

http://trac.macports.org/ticket/18583

If you can figure out the solution let us know.

What happens if you type

svn ls svn://anonsvn.kde.org/home/kde/trunk/kdesupport

in the terminal? If it's working, it should list the contents of that  
directory.

I should note that fetching taglib-devel works fine for me, so maybe  
there is a problem using the svn protocol (port 3690) on your network.



From ryandesign at macports.org  Thu Jun 25 17:59:37 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 25 Jun 2009 19:59:37 -0500
Subject: Yet Another Problem Installing Amarok
In-Reply-To: <0A14CD35-0CD7-4A84-B86C-4A6DBBC2C954@macports.org>
References: <FDDD2DD9-34AF-424C-A786-185A14977702@halblog.com>
	<0A14CD35-0CD7-4A84-B86C-4A6DBBC2C954@macports.org>
Message-ID: <B8C6502E-AAA4-46FF-851B-DAB2FCE43AA8@macports.org>

On Jun 25, 2009, at 19:52, Ryan Schmidt wrote:

> On Jun 25, 2009, at 19:24, Hal Vaughan wrote:
>
>> My last problem is cleared now -- it froze on installing kdebase4- 
>> runtime.  When I got it all working (as in rebooted and updated  
>> some stuff from Apple), I ran "sudo port install amarok" and it  
>> went through a lot of stuff, then I'm stuck with this:
>>
>> --->  Fetching taglib-devel
>> Error: Target org.macports.fetch returned: Subversion check out  
>> failed
>> Error: The following dependencies failed to build: taglib-devel  
>> taglib-extras
>> Error: Status 1 encountered during processing.
>>
>> When I saw that, it sounded like it had a problem reading data  
>> from an svn repository, so I waited and tried it again, in case a  
>> site was down.  Still no luck.
>>
>> So what is actually going on here and how can I fix it?  I tried  
>> Google, but didn't see much info on it and when I googled the  
>> error message, I found no hits!
>
> taglib-devel wants to check out its files from the KDE project's  
> anonymous Subversion repository, which seems not to be working for  
> you. This has been reported before, with no solution listed so far:
>
> http://trac.macports.org/ticket/18583
>
> If you can figure out the solution let us know.
>
> What happens if you type
>
> svn ls svn://anonsvn.kde.org/home/kde/trunk/kdesupport
>
> in the terminal? If it's working, it should list the contents of  
> that directory.
>
> I should note that fetching taglib-devel works fine for me, so  
> maybe there is a problem using the svn protocol (port 3690) on your  
> network.

Correction: according to the ticket, the problem is not the initial  
svn checkout but an external it then wants to check out afterward.  
The fetch does not fail for me, yet if I use debug mode I see that  
the external did not get fetched:

svn: warning: Error handling externals definition for 'taglib/admin':
svn: warning: OPTIONS of 'https://svn.kde.org/home/kde/branches/KDE/ 
3.5/kde-common/admin': Server certificate verification failed: issuer  
is not trusted (https://svn.kde.org)

I do not know why port did not recognize that this was a fatal error.

Taking a cue from the above ticket, I ran

svn ls https://svn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin

in the terminal and answered "p" to get it to accept the certificate  
permanently. Then the port fetch worked correctly.



From hal at halblog.com  Thu Jun 25 20:03:53 2009
From: hal at halblog.com (Hal Vaughan)
Date: Thu, 25 Jun 2009 23:03:53 -0400
Subject: Yet Another Problem Installing Amarok
In-Reply-To: <B8C6502E-AAA4-46FF-851B-DAB2FCE43AA8@macports.org>
References: <FDDD2DD9-34AF-424C-A786-185A14977702@halblog.com>
	<0A14CD35-0CD7-4A84-B86C-4A6DBBC2C954@macports.org>
	<B8C6502E-AAA4-46FF-851B-DAB2FCE43AA8@macports.org>
Message-ID: <E8AA22D5-C54F-4323-982E-35BD9A7AFEAF@halblog.com>


On Jun 25, 2009, at 8:59 PM, Ryan Schmidt wrote:

> On Jun 25, 2009, at 19:52, Ryan Schmidt wrote:
>
>> On Jun 25, 2009, at 19:24, Hal Vaughan wrote:
>>
>>> My last problem is cleared now -- it froze on installing kdebase4- 
>>> runtime.  When I got it all working (as in rebooted and updated  
>>> some stuff from Apple), I ran "sudo port install amarok" and it  
>>> went through a lot of stuff, then I'm stuck with this:
>>>
>>> --->  Fetching taglib-devel
>>> Error: Target org.macports.fetch returned: Subversion check out  
>>> failed
>>> Error: The following dependencies failed to build: taglib-devel  
>>> taglib-extras
>>> Error: Status 1 encountered during processing.
>>>
>>> When I saw that, it sounded like it had a problem reading data  
>>> from an svn repository, so I waited and tried it again, in case a  
>>> site was down.  Still no luck.
>>>
>>> So what is actually going on here and how can I fix it?  I tried  
>>> Google, but didn't see much info on it and when I googled the  
>>> error message, I found no hits!
>>
>> taglib-devel wants to check out its files from the KDE project's  
>> anonymous Subversion repository, which seems not to be working for  
>> you. This has been reported before, with no solution listed so far:
>>
>> http://trac.macports.org/ticket/18583
>>
>> If you can figure out the solution let us know.
>>
>> What happens if you type
>>
>> svn ls svn://anonsvn.kde.org/home/kde/trunk/kdesupport
>>
>> in the terminal? If it's working, it should list the contents of  
>> that directory.

That works and I see the contents of the directory.  And, just in  
case, since I'm using sudo to run Macports, I tried it with sudo and  
it worked as well.  I even logged into a terminal tab as root and  
tried it from there, just to be clear there was no user issue there.

>> I should note that fetching taglib-devel works fine for me, so  
>> maybe there is a problem using the svn protocol (port 3690) on your  
>> network.
>
> Correction: according to the ticket, the problem is not the initial  
> svn checkout but an external it then wants to check out afterward.  
> The fetch does not fail for me, yet if I use debug mode I see that  
> the external did not get fetched:
>
> svn: warning: Error handling externals definition for 'taglib/admin':
> svn: warning: OPTIONS of 'https://svn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin' 
> : Server certificate verification failed: issuer is not trusted (https://svn.kde.org 
> )
>
> I do not know why port did not recognize that this was a fatal error.
>
> Taking a cue from the above ticket, I ran
>
> svn ls https://svn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin
>
> in the terminal and answered "p" to get it to accept the certificate  
> permanently. Then the port fetch worked correctly.

I ran it, both as root and as my user name, again in case there's an  
issue with user rights or anything like that.  Then I ran it again  
under my user account and it asked for the question again.  So I ran  
it another time.  Each time I run it, I pick "p" yet the next time it  
still asks again.

However, I went on and tried to install Amarok again after that and as  
I write this it is configuring taglib.

Ok, I'm lying.  Now it's building taglib.  Anyway, it's working.

It appears like there is a problem with the certificate, since I got  
that message each time I ran the command above.  It wasn't a problem  
with the first command, but is with the 2nd one.

Is it possible you have something else already installed that is  
making use of something similar?

And thanks for the help on this!  I just checked the status and now  
it's building Amarok.  Since that's what I was trying to install in  
the first place, I would expect that to be the last package for it to  
fetch.


Hal


From hal at halblog.com  Thu Jun 25 20:29:29 2009
From: hal at halblog.com (Hal Vaughan)
Date: Thu, 25 Jun 2009 23:29:29 -0400
Subject: Yet Another Problem Installing Amarok
In-Reply-To: <0A14CD35-0CD7-4A84-B86C-4A6DBBC2C954@macports.org>
References: <FDDD2DD9-34AF-424C-A786-185A14977702@halblog.com>
	<0A14CD35-0CD7-4A84-B86C-4A6DBBC2C954@macports.org>
Message-ID: <CF21BD11-6A15-4865-BE4E-7EE3B7FB0415@halblog.com>

Okay, Amarok is installed now.  There's another problem, but since  
that's an entirely new issue, I'm going back to the other thread,  
since I think it's connected with that time my terminal locked up.


Hal

On Jun 25, 2009, at 8:52 PM, Ryan Schmidt wrote:

>
> On Jun 25, 2009, at 19:24, Hal Vaughan wrote:
>
>> My last problem is cleared now -- it froze on installing kdebase4- 
>> runtime.  When I got it all working (as in rebooted and updated  
>> some stuff from Apple), I ran "sudo port install amarok" and it  
>> went through a lot of stuff, then I'm stuck with this:
>>
>> --->  Fetching taglib-devel
>> Error: Target org.macports.fetch returned: Subversion check out  
>> failed
>> Error: The following dependencies failed to build: taglib-devel  
>> taglib-extras
>> Error: Status 1 encountered during processing.
>>
>> When I saw that, it sounded like it had a problem reading data from  
>> an svn repository, so I waited and tried it again, in case a site  
>> was down.  Still no luck.
>>
>> So what is actually going on here and how can I fix it?  I tried  
>> Google, but didn't see much info on it and when I googled the error  
>> message, I found no hits!
>
> taglib-devel wants to check out its files from the KDE project's  
> anonymous Subversion repository, which seems not to be working for  
> you. This has been reported before, with no solution listed so far:
>
> http://trac.macports.org/ticket/18583
>
> If you can figure out the solution let us know.
>
> What happens if you type
>
> svn ls svn://anonsvn.kde.org/home/kde/trunk/kdesupport
>
> in the terminal? If it's working, it should list the contents of  
> that directory.
>
> I should note that fetching taglib-devel works fine for me, so maybe  
> there is a problem using the svn protocol (port 3690) on your network.
>
>


From ryandesign at macports.org  Thu Jun 25 20:49:11 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 25 Jun 2009 22:49:11 -0500
Subject: Problem installing KDE/Amarok
In-Reply-To: <689EDC2A-FD01-4BE6-80D5-5C55B303C0EB@halblog.com>
References: <54522AA8-7FA1-4C45-AE58-FD15C433A27A@halblog.com>
	<F1A9EF49-9E80-470F-9102-EEC478B1F8BB@macports.org>
	<5F8AD1F2-747C-4ADA-889D-ABB2111138B2@halblog.com>
	<44B08E94-FBA8-4E16-9635-54D8EA225DD9@macports.org>
	<689EDC2A-FD01-4BE6-80D5-5C55B303C0EB@halblog.com>
Message-ID: <82CB7E0E-3776-4877-8CA5-B14FF09BC55D@macports.org>


On Jun 25, 2009, at 22:38, Hal Vaughan wrote:

> On Jun 24, 2009, at 6:02 PM, Ryan Schmidt wrote:
>
>> On Jun 24, 2009, at 16:47, Hal Vaughan wrote:
>>
>>> I figured they'd be lost if I had to kill the terminal.  Of  
>>> course, I'm not 100% sure that this is the issue.  For all I  
>>> know, the process could have been okay and it could be something  
>>> else that crashed it.  (Come to think of it, there was an ssh  
>>> connection, but it's a program I'm always running in the b.g.)  I  
>>> figure in worst case, since it's the first thing I'm installing,  
>>> I could wipe out any KDE directory in Applications and just wipe  
>>> all of /opt, reinstall MacPorts and restart.
>>>
>>> Is there any place else KDE would store files that I'd have to  
>>> clear out if I do that?
>>>
>>>> After restarting Terminal or the computer, you can try again.  
>>>> You can use the "-d" flag ("port -d install amarok") to get a  
>>>> lot more information printed out. This will let you see what  
>>>> exactly a port was doing if and when it gets hung up. On the  
>>>> other hand, the vast quantity of output you will get means you  
>>>> will very likely miss any "you must do this after installing the  
>>>> port"-type messages that some ports print.
>>>
>>> I was also going to see if I could find a list somewhere of all  
>>> the messages from KDE.  It looks like each package is giving me  
>>> the same message at the start and the end.
>>>
>>> I'll most likely wipe out /opt and just start clean, since I  
>>> don't have any other packages done with MacPorts yet.  I don't  
>>> mind letting it rebuild qt overnight.
>>
>> If you want to do that, you should follow the uninstall  
>> instructions shown here:
>>
>> http://trac.macports.org/wiki/FAQ#HowdoIremoveoruninstallMacPorts
>
> As noted elsewhere, I went on with the install and eventually  
> (after fixing the svn issue - thanks, Ryan!), I'm dealing with a  
> problem I think is related to this issue.  After it was all  
> installed properly, I ran the following commands:
>
> sudo chown -R $USER ~/Library/Preferences/KDE
> open /Applications/MacPorts/KDE4/kdeinit4.app
>
> launchctl load /Library/LaunchAgents/org.freedesktop.dbus- 
> session.plist
>
> The first two were the instructions given at the start of most  
> packages as they were installed and the last one was given at the  
> end.  When I ran the last one, I got this:
>
> nothing found to load
>
> I suspect that when my terminal locked up previously, there were  
> some messages on what to run that I didn't get to see.  Is there a  
> resource somewhere that would give me an output of that install  
> command or a list of command lines I have to run after KDE is  
> installed?
>
> Also, would I have to run the last 2 commands each time my iMac  
> boots or is it like some Linux systems -- that once a service is  
> running, it restarts on boot until a user stops it?

I'll let someone else answer what is required to get KDE to run. I  
don't know.

"chown" would permanently set the ownership; it won't get unset.

"open" is the same as double-clicking something in the Finder.

"launchctl load -w" loads a service and tells it to launch at every  
system startup. "launchctl unload -w" unloads a service and tells it  
not to load at every system startup. If you don't use the "-w"  
option, then the service is started or stopped, but nothing is  
changed about what happens at system startup.



From nuvolare at email.it  Sat Jun 27 01:59:55 2009
From: nuvolare at email.it (nuvolare)
Date: Sat, 27 Jun 2009 10:59:55 +0200
Subject: Error for installation glade in Tiger
Message-ID: <7DD6FA00-0654-4C2C-A120-2EC74261DF37@email.it>

Hello, I'm writing becuase I need to have glade on my macbook pro and  
I've a week that I'm tring to install it, but I find lot's of error,  
and now
I don't know how to resolve it, could you tell me what I've to do?
This is the error:

--->  Configuring gst-plugins-base
--->  Building gst-plugins-base
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_g 
st-plugins-base/work/gst-plugins-base-0.10.23" && make all " returned  
error 2
Command output:   CC    vs_4tap.o
   LINK  libgstvideoscale.la
warning: no debug map in executable (-arch i386)
Making all in volume
   CC    gstvolume.o
   LINK  libgstvolume.la
warning: no debug map in executable (-arch i386)
Making all in sys
Making all in ximage
   CC    ximagesink.o
   CC    ximage.o
   LINK  libgstximagesink.la
warning: no debug map in executable (-arch i386)
Making all in xvimage
   CC    xvimagesink.o
   LINK  libgstxvimagesink.la
warning: no debug map in executable (-arch i386)
Making all in ext
Making all in cdparanoia
   CC    gstcdparanoiasrc.o
/opt/local/include/cdda_interface.h:175: warning: 'strerror_tr'  
defined but not used
   LINK  libgstcdparanoia.la
/usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
_cdda_identify
_cdda_identify_scsi
collect2: ld returned 1 exit status
make[3]: *** [libgstcdparanoia.la] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Error: The following dependencies failed to build: devhelp webkit-gtk  
gst-plugins-base icu libsoup gnutls libgcrypt libgpg-error libtasn1  
lzo opencdk libproxy xorg-libXmu xorg-libXt xorg-util-macros hicolor- 
icon-theme libgnomeui gnome-icon-theme icon-naming-utils p5-xml- 
simple p5-xml-namespacesupport p5-xml-sax gnome-keyring libbonoboui  
libbonobo libgnome esound audiofile py25-gtk py25-cairo py25-numpy  
fftw-3 py25-nose py25-setuptools py25-gobject
Error: Status 1 encountered during processing.
MacbookPro:~ nuvolare$


And also, in this week my macbook pro it's going much slowly, it's  
possible that with this work, by Terminal, my mac is going to have  
problem?
Thank you



 
 
 --
 Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
 
 Sponsor:
 Last Minute a Riccione. Scopri le offerte su vacanzedivertenti.it  
* Buona Vacanza!
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=9213&d=27-6
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090627/da25974a/attachment.html>

From face at CentosPrime.COM  Sat Jun 27 10:16:27 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sat, 27 Jun 2009 10:16:27 -0700
Subject: php.ini removed
Message-ID: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>

hmmm - my brain has been hurting for quite some time.

On my G4 Panther system I upgraded php5 to 5.2.10

I ran a test that demonstrated that I could see a problem with date/ 
time, so go back to the older version

sudo port deactivate php5 @5.2.10_0+apache+darwin_7+macosx+mysql5+pear
sudo port activate php5 @5.2.6_2+apache+darwin_7+macosx+mysql5+pear

Things seemed OK from the command line.

I was notified on Friday evening that all of my Wordpress blogs were  
failing.
Chased my tail - mysql5 is fine, php seems to work fine, just no PHP -  
MySQL connections working

short answer

in /opt/local/etc/php.ini I had specified a different socket for the  
MySQL connection
/opt/local/etc/php.ini was gone

The only things I can pin it on are one of the port upgrade/port  
deactivate/port activate commands.

It's fixed now, just wondering who the culprit is.

My brain *really* hurts...

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From devans at macports.org  Sat Jun 27 10:32:30 2009
From: devans at macports.org (David Evans)
Date: Sat, 27 Jun 2009 10:32:30 -0700
Subject: Error for installation glade in Tiger
In-Reply-To: <7DD6FA00-0654-4C2C-A120-2EC74261DF37@email.it>
References: <7DD6FA00-0654-4C2C-A120-2EC74261DF37@email.it>
Message-ID: <4A4657AE.9020900@macports.org>

nuvolare wrote:
> Hello, I'm writing becuase I need to have glade on my macbook pro and 
> I've a week that I'm tring to install it, but I find lot's of error, 
> and now 
> I don't know how to resolve it, could you tell me what I've to do?
> This is the error:
>
> --->  Configuring gst-plugins-base
> --->  Building gst-plugins-base
> Error: Target org.macports.build returned: shell command " cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gst-plugins-base/work/gst-plugins-base-0.10.23" 
> && make all " returned error 2
> Command output:   CC    vs_4tap.o
>   LINK  libgstvideoscale.la
> warning: no debug map in executable (-arch i386)
> Making all in volume
>   CC    gstvolume.o
>   LINK  libgstvolume.la
> warning: no debug map in executable (-arch i386)
> Making all in sys
> Making all in ximage
>   CC    ximagesink.o
>   CC    ximage.o
>   LINK  libgstximagesink.la
> warning: no debug map in executable (-arch i386)
> Making all in xvimage
>   CC    xvimagesink.o
>   LINK  libgstxvimagesink.la
> warning: no debug map in executable (-arch i386)
> Making all in ext
> Making all in cdparanoia
>   CC    gstcdparanoiasrc.o
> /opt/local/include/cdda_interface.h:175: warning: 'strerror_tr' 
> defined but not used
>   LINK  libgstcdparanoia.la
> /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
> _cdda_identify
> _cdda_identify_scsi
> collect2: ld returned 1 exit status
> make[3]: *** [libgstcdparanoia.la] Error 1
> make[2]: *** [all-recursive] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> Error: The following dependencies failed to build: devhelp webkit-gtk 
> gst-plugins-base icu libsoup gnutls libgcrypt libgpg-error libtasn1 
> lzo opencdk libproxy xorg-libXmu xorg-libXt xorg-util-macros 
> hicolor-icon-theme libgnomeui gnome-icon-theme icon-naming-utils 
> p5-xml-simple p5-xml-namespacesupport p5-xml-sax gnome-keyring 
> libbonoboui libbonobo libgnome esound audiofile py25-gtk py25-cairo 
> py25-numpy fftw-3 py25-nose py25-setuptools py25-gobject
> Error: Status 1 encountered during processing.
> MacbookPro:~ nuvolare$
This appears to be the problem reported in

http://trac.macports.org/ticket/19843

The problem is not with glade but with its dependency gst-plugins-base.

The cdparanoia plugin in that port is not compatible with
the latest version of cdparanoia provided by MacPorts.

The problem was fixed by disabling the build of this plugin by default.

http://trac.macports.org/changeset/52743

The fact that you are seeing this error indicates that you do not have
the latest version of port gst-plugins-base.

Please update your ports by doing the following

sudo port clean gst-plugins-base
sudo port selfupdate
sudo port upgrade outdated

then try installing glade again.

By the way, the port glade is an obsolete version (2.12.2) which is not
currently recommended nor maintained by the upstream developers.  Port 
glade3 (version 3.6.6) is the current stable release and is to be preferred.

sudo port install glade3





From ryandesign at macports.org  Sat Jun 27 15:51:21 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sat, 27 Jun 2009 17:51:21 -0500
Subject: php.ini removed
In-Reply-To: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
References: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
Message-ID: <786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>

On Jun 27, 2009, at 12:16, Chris Janton wrote:

> hmmm - my brain has been hurting for quite some time.
>
> On my G4 Panther system I upgraded php5 to 5.2.10
>
> I ran a test that demonstrated that I could see a problem with date/ 
> time, so go back to the older version
>
> sudo port deactivate php5 @5.2.10_0+apache+darwin_7+macosx+mysql5+pear
> sudo port activate php5 @5.2.6_2+apache+darwin_7+macosx+mysql5+pear
>
> Things seemed OK from the command line.
>
> I was notified on Friday evening that all of my Wordpress blogs  
> were failing.
> Chased my tail - mysql5 is fine, php seems to work fine, just no  
> PHP - MySQL connections working
>
> short answer
>
> in /opt/local/etc/php.ini I had specified a different socket for  
> the MySQL connection
> /opt/local/etc/php.ini was gone
>
> The only things I can pin it on are one of the port upgrade/port  
> deactivate/port activate commands.
>
> It's fixed now, just wondering who the culprit is.
>
> My brain *really* hurts...

Sorry about the problem, but I'm not sure how it happened. As far as  
I can tell, php5 does not touch your php.ini, and never has. It only  
installs sample files named php.ini-dist and php.ini-recommended and  
prints a message advising you to copy one of these to the proper  
location.


From face at CentosPrime.COM  Sat Jun 27 16:59:48 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sat, 27 Jun 2009 16:59:48 -0700
Subject: php.ini removed
In-Reply-To: <786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
References: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
	<786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
Message-ID: <FBB57EFC-C1A8-4905-947C-10FD69DE1FA1@CentosPrime.COM>

On 2009-06-27 , at 15:51 , Ryan Schmidt wrote:

> Sorry about the problem, but I'm not sure how it happened. As far as  
> I can tell, php5 does not touch your php.ini, and never has. It only  
> installs sample files named php.ini-dist and php.ini-recommended and  
> prints a message advising you to copy one of these to the proper  
> location.


thanks.

I *know* nothing is supposed to touch the php.ini file

I had a copy lurking somewhere - it just took me an hour to test  
everything, and to figure out that just because phpMyAdmin works from  
one server doesn't necessarily mean it works from all servers -  
localhost goes to the socket, everyone else uses port 3306.

Mostly this is a heads-up

Hey there Bunky! PHP/MySQL connections not workin' on yer website?  
Check php.ini ;-) sockets vs. ports.

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From brad at pixilla.com  Sun Jun 28 08:39:49 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Sun, 28 Jun 2009 08:39:49 -0700
Subject: php.ini removed
In-Reply-To: <786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
References: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
	<786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
Message-ID: <76709EDC-6AD3-475D-9CBA-659F7063AD3B@pixilla.com>


On Jun 27, 2009, at 3:51 PM, Ryan Schmidt wrote:

> On Jun 27, 2009, at 12:16, Chris Janton wrote:
>
>> hmmm - my brain has been hurting for quite some time.
>>
>> On my G4 Panther system I upgraded php5 to 5.2.10
>>
>> I ran a test that demonstrated that I could see a problem with date/ 
>> time, so go back to the older version
>>
>> sudo port deactivate php5 @5.2.10_0+apache+darwin_7+macosx 
>> +mysql5+pear
>> sudo port activate php5 @5.2.6_2+apache+darwin_7+macosx+mysql5+pear
>>
>> Things seemed OK from the command line.
>>
>> I was notified on Friday evening that all of my Wordpress blogs  
>> were failing.
>> Chased my tail - mysql5 is fine, php seems to work fine, just no  
>> PHP - MySQL connections working
>>
>> short answer
>>
>> in /opt/local/etc/php.ini I had specified a different socket for  
>> the MySQL connection
>> /opt/local/etc/php.ini was gone
>>
>> The only things I can pin it on are one of the port upgrade/port  
>> deactivate/port activate commands.
>>
>> It's fixed now, just wondering who the culprit is.
>>
>> My brain *really* hurts...
>
> Sorry about the problem, but I'm not sure how it happened. As far as  
> I can tell, php5 does not touch your php.ini, and never has. It only  
> installs sample files named php.ini-dist and php.ini-recommended and  
> prints a message advising you to copy one of these to the proper  
> location.

I think the location of php.ini may have been moved to etc/php5 with  
php5 @5.2.10. I was paying that much attention when I upgraded.

Ryan, I see you are one of the maintainers of php5.

Would you consider adding:
variant ming description {Add library to create SWF ("Flash") format  
movies} {
     depends_lib-append \
         port:ming
     configure.args-append \
         --with-ming \
}


// Brad

From face at CentosPrime.COM  Sun Jun 28 09:08:34 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sun, 28 Jun 2009 09:08:34 -0700
Subject: php.ini removed
In-Reply-To: <76709EDC-6AD3-475D-9CBA-659F7063AD3B@pixilla.com>
References: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
	<786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
	<76709EDC-6AD3-475D-9CBA-659F7063AD3B@pixilla.com>
Message-ID: <8CEB700D-136C-4ECA-9B1E-19CFB104C3BD@CentosPrime.COM>

On 2009-06-28 , at 08:39 , Bradley Giesbrecht wrote:

>> Sorry about the problem, but I'm not sure how it happened. As far  
>> as I can tell, php5 does not touch your php.ini, and never has. It  
>> only installs sample files named php.ini-dist and php.ini- 
>> recommended and prints a message advising you to copy one of these  
>> to the proper location.
>
> I think the location of php.ini may have been moved to etc/php5 with  
> php5 @5.2.10. I was paying that much attention when I upgraded.


ahhh, the mystery is solved.

the upgrade to php5 @5.2.10 moved the php.ini file to /opt/local/etc/ 
php5/php.ini
the deactivate didn't touch anything
the activate php5 @5.2.6 didn't do anything to php.ini either, since  
there now is no php.ini in /opt/local/etc

hmmm, maybe the "right" thing for php5 @5.2.10 to do is copy the  
php.ini file as opposed to moving it?

my brain hurts less now.

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From julien.isorce at gmail.com  Sun Jun 28 09:55:16 2009
From: julien.isorce at gmail.com (Julien Isorce)
Date: Sun, 28 Jun 2009 18:55:16 +0200
Subject: objc_mutex_t
Message-ID: <180a127d0906280955q4749e66bq6e47bc5ae3eb4e96@mail.gmail.com>

Hi,
I need to use objc_mutex_t. (so I have to include objc/thr.h)

Using default gcc (i686-apple-darwin9-gcc-4.0.1) that comes with Leopard,
there is no thr.h  in /usr/include/objc

Do I need to install gcc from macports or is there any other way to have
this thr.h ?

Sincerely

Julien
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090628/673aa14b/attachment.html>

From talklists at newgeo.com  Sun Jun 28 10:05:23 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Sun, 28 Jun 2009 10:05:23 -0700
Subject: php.ini removed
In-Reply-To: <8CEB700D-136C-4ECA-9B1E-19CFB104C3BD@CentosPrime.COM>
References: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
	<786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
	<76709EDC-6AD3-475D-9CBA-659F7063AD3B@pixilla.com>
	<8CEB700D-136C-4ECA-9B1E-19CFB104C3BD@CentosPrime.COM>
Message-ID: <63E98AA4-72B8-4DFD-83EA-DB59798E1407@newgeo.com>

Why did moving it break things is I think what first needs to be  
learned.

Why was ini put in a php5 directory? As far as I know php wants to  
look in some standard locations. /etc is one if them so that would  
translate to /opt/local/etc/php.ini.

Of cource there are a few other locations but I believe etc is pretty  
normal. I think it should have just kep working. Any idea why it did  
not work for you? What did you have to change to get it to work?

You can also run 'port contents portname' to see where all the files  
registered to that port are.

-- 
Scott
Iphone says hello.

On Jun 28, 2009, at 9:08 AM, Chris Janton <face at CentosPrime.COM> wrote:

> On 2009-06-28 , at 08:39 , Bradley Giesbrecht wrote:
>
>>> Sorry about the problem, but I'm not sure how it happened. As far  
>>> as I can tell, php5 does not touch your php.ini, and never has. It  
>>> only installs sample files named php.ini-dist and php.ini- 
>>> recommended and prints a message advising you to copy one of these  
>>> to the proper location.
>>
>> I think the location of php.ini may have been moved to etc/php5  
>> with php5 @5.2.10. I was paying that much attention when I upgraded.
>
>
> ahhh, the mystery is solved.
>
> the upgrade to php5 @5.2.10 moved the php.ini file to /opt/local/etc/ 
> php5/php.ini
> the deactivate didn't touch anything
> the activate php5 @5.2.6 didn't do anything to php.ini either, since  
> there now is no php.ini in /opt/local/etc
>
> hmmm, maybe the "right" thing for php5 @5.2.10 to do is copy the  
> php.ini file as opposed to moving it?
>
> my brain hurts less now.
>
> 8)
> ----------------------------------
> Chris Janton  - face at CentosPrime dot COM
> Netminder for Opus1.COM
>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

From brad at pixilla.com  Sun Jun 28 10:27:25 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Sun, 28 Jun 2009 10:27:25 -0700
Subject: php.ini removed
In-Reply-To: <63E98AA4-72B8-4DFD-83EA-DB59798E1407@newgeo.com>
References: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
	<786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
	<76709EDC-6AD3-475D-9CBA-659F7063AD3B@pixilla.com>
	<8CEB700D-136C-4ECA-9B1E-19CFB104C3BD@CentosPrime.COM>
	<63E98AA4-72B8-4DFD-83EA-DB59798E1407@newgeo.com>
Message-ID: <8BBA3EC1-F464-458E-A337-CBBE6C2CC828@pixilla.com>


On Jun 28, 2009, at 10:05 AM, Scott Haneda wrote:

> Why did moving it break things is I think what first needs to be  
> learned.
>
> Why was ini put in a php5 directory? As far as I know php wants to  
> look in some standard locations. /etc is one if them so that would  
> translate to /opt/local/etc/php.ini.

I don't think it's a bad idea to subdir php.ini into version. When  
people upgrade to php6 down the road they may need to revert back.  
Leaving php5/php.ini untouched gives the possibility to quickly revert  
back to php5 if php6 breaks your scripts.

// Brad


From face at CentosPrime.COM  Sun Jun 28 11:09:53 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sun, 28 Jun 2009 11:09:53 -0700
Subject: php.ini removed
In-Reply-To: <63E98AA4-72B8-4DFD-83EA-DB59798E1407@newgeo.com>
References: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
	<786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
	<76709EDC-6AD3-475D-9CBA-659F7063AD3B@pixilla.com>
	<8CEB700D-136C-4ECA-9B1E-19CFB104C3BD@CentosPrime.COM>
	<63E98AA4-72B8-4DFD-83EA-DB59798E1407@newgeo.com>
Message-ID: <6CAF4B16-4B36-4E6D-ADF5-D2C76904A03B@CentosPrime.COM>

On 2009-06-28 , at 10:05 , Scott Haneda wrote:

> Why did moving it break things is I think what first needs to be  
> learned.

Because it didn't "move back" when I switched back to an older version  
of php5


> Why was ini put in a php5 directory? As far as I know php wants to  
> look in some standard locations. /etc is one if them so that would  
> translate to /opt/local/etc/php.ini.

That would be as standard location - especially if there is an  
expectation that a php6 (or php7) might also be made available on the  
system.

> Of cource there are a few other locations but I believe etc is  
> pretty normal. I think it should have just kep working. Any idea why  
> it did not work for you? What did you have to change to get it to  
> work?

I don't use the "standard" socket location for MySQL5 as provided in  
MacPorts - I set the socket values for PHP to use in the .ini file  
like this...

; Default socket name for local MySQL connects.  If empty, uses the  
built-in
mysql.default_socket = /tmp/mysql.sock
; Default socket name for local MySQL connects.  If empty, uses the  
built-in
mysqli.default_socket = /tmp/mysql.sock

> You can also run 'port contents portname' to see where all the files  
> registered to that port are.


The "answer" to the change is here

  http://trac.macports.org/changeset/50173/trunk/dports/lang/php5/Portfile

When I did the port upgrade php5 I didn't "see" the message that was  
output

  ui_msg "Your ${prefix}/etc/php.ini has been moved to ${phpinidir}/ 
php.ini"

I guess for me that something like this

  COPY ${prefix}/etc/php.ini ${phpinidir}

as opposed to

  move ${prefix}/etc/php.ini ${phpinidir}

would have made it transparent (assuming that there is a copy function  
like move in the port language)

It's my bad, since I didn't read the message when I did the upgrade.

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From ryandesign at macports.org  Sun Jun 28 13:34:41 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 28 Jun 2009 15:34:41 -0500
Subject: php.ini removed
In-Reply-To: <76709EDC-6AD3-475D-9CBA-659F7063AD3B@pixilla.com>
References: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
	<786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
	<76709EDC-6AD3-475D-9CBA-659F7063AD3B@pixilla.com>
Message-ID: <07A58E32-3E1E-4ECC-9138-5F5650816801@macports.org>

On Jun 28, 2009, at 10:39, Bradley Giesbrecht wrote:

> Ryan, I see you are one of the maintainers of php5.
>
> Would you consider adding:
> variant ming description {Add library to create SWF ("Flash")  
> format movies} {
>     depends_lib-append \
>         port:ming
>     configure.args-append \
>         --with-ming \
> }

I have filed a ticket for your request:

http://trac.macports.org/ticket/20093



From ryandesign at macports.org  Sun Jun 28 13:38:15 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 28 Jun 2009 15:38:15 -0500
Subject: php.ini removed
In-Reply-To: <8CEB700D-136C-4ECA-9B1E-19CFB104C3BD@CentosPrime.COM>
References: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
	<786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
	<76709EDC-6AD3-475D-9CBA-659F7063AD3B@pixilla.com>
	<8CEB700D-136C-4ECA-9B1E-19CFB104C3BD@CentosPrime.COM>
Message-ID: <1FEB9B48-D7D8-43F6-AF28-FBA93283E44D@macports.org>


On Jun 28, 2009, at 11:08, Chris Janton wrote:

> On 2009-06-28 , at 08:39 , Bradley Giesbrecht wrote:
>
>>> Sorry about the problem, but I'm not sure how it happened. As far  
>>> as I can tell, php5 does not touch your php.ini, and never has.  
>>> It only installs sample files named php.ini-dist and php.ini- 
>>> recommended and prints a message advising you to copy one of  
>>> these to the proper location.
>>
>> I think the location of php.ini may have been moved to etc/php5  
>> with php5 @5.2.10. I was paying that much attention when I upgraded.
>
> ahhh, the mystery is solved.
>
> the upgrade to php5 @5.2.10 moved the php.ini file to /opt/local/ 
> etc/php5/php.ini
> the deactivate didn't touch anything
> the activate php5 @5.2.6 didn't do anything to php.ini either,  
> since there now is no php.ini in /opt/local/etc

Oooh, yes, that was it. Sorry, I forgot about that change; it  
happened 2 months ago with 5.2.9_2.


> hmmm, maybe the "right" thing for php5 @5.2.10 to do is copy the  
> php.ini file as opposed to moving it?

I don't know... if you didn't see the message about the php.ini  
having been moved (or now copied), wouldn't it be more confusing to  
still have the php.ini at the old location? You'd be making changes  
to the file and scratching your head why those changes weren't having  
any effect.

I could move the file and then put a symlink to it at the old  
location...



From ryandesign at macports.org  Sun Jun 28 13:39:58 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 28 Jun 2009 15:39:58 -0500
Subject: php.ini removed
In-Reply-To: <8BBA3EC1-F464-458E-A337-CBBE6C2CC828@pixilla.com>
References: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
	<786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
	<76709EDC-6AD3-475D-9CBA-659F7063AD3B@pixilla.com>
	<8CEB700D-136C-4ECA-9B1E-19CFB104C3BD@CentosPrime.COM>
	<63E98AA4-72B8-4DFD-83EA-DB59798E1407@newgeo.com>
	<8BBA3EC1-F464-458E-A337-CBBE6C2CC828@pixilla.com>
Message-ID: <359A5D14-D3AE-4D5E-8A61-C42060AF0F97@macports.org>


On Jun 28, 2009, at 12:27, Bradley Giesbrecht wrote:

> On Jun 28, 2009, at 10:05 AM, Scott Haneda wrote:
>
>> Why did moving it break things is I think what first needs to be  
>> learned.
>>
>> Why was ini put in a php5 directory? As far as I know php wants to  
>> look in some standard locations. /etc is one if them so that would  
>> translate to /opt/local/etc/php.ini.
>
> I don't think it's a bad idea to subdir php.ini into version. When  
> people upgrade to php6 down the road they may need to revert back.  
> Leaving php5/php.ini untouched gives the possibility to quickly  
> revert back to php5 if php6 breaks your scripts.

Yes, but it's not just a matter of switching back; it's a matter of  
being able to install simultaneously. Due to this change, it is now  
possible to install and activate php4 and php5 at the same time,  
which I intend to carry forward to php6 when that becomes available.


From face at CentosPrime.COM  Sun Jun 28 14:49:37 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sun, 28 Jun 2009 14:49:37 -0700
Subject: php.ini removed
In-Reply-To: <1FEB9B48-D7D8-43F6-AF28-FBA93283E44D@macports.org>
References: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
	<786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
	<76709EDC-6AD3-475D-9CBA-659F7063AD3B@pixilla.com>
	<8CEB700D-136C-4ECA-9B1E-19CFB104C3BD@CentosPrime.COM>
	<1FEB9B48-D7D8-43F6-AF28-FBA93283E44D@macports.org>
Message-ID: <A8E2E88A-2EC9-4BF2-96DC-614E0A1526B7@CentosPrime.COM>

On 2009-06-28 , at 13:38 , Ryan Schmidt wrote:

>> hmmm, maybe the "right" thing for php5 @5.2.10 to do is copy the  
>> php.ini file as opposed to moving it?
>
> I don't know... if you didn't see the message about the php.ini  
> having been moved (or now copied), wouldn't it be more confusing to  
> still have the php.ini at the old location? You'd be making changes  
> to the file and scratching your head why those changes weren't  
> having any effect.
>
> I could move the file and then put a symlink to it at the old  
> location...


A symlink should solve the problem nicely. That and a new pair of  
reading glasses for me ;-)

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From allbery at kf8nh.com  Mon Jun 29 07:56:57 2009
From: allbery at kf8nh.com (Brandon Allbery)
Date: Mon, 29 Jun 2009 10:56:57 -0400
Subject: php.ini removed
In-Reply-To: <1FEB9B48-D7D8-43F6-AF28-FBA93283E44D@macports.org>
References: <A4ED4622-17E2-416D-91CA-BB4A39A0D68E@centosprime.com>
	<786CC583-86E1-45F9-8ECB-57423E5358B4@macports.org>
	<76709EDC-6AD3-475D-9CBA-659F7063AD3B@pixilla.com>
	<8CEB700D-136C-4ECA-9B1E-19CFB104C3BD@CentosPrime.COM>
	<1FEB9B48-D7D8-43F6-AF28-FBA93283E44D@macports.org>
Message-ID: <F4DC79FC-5998-4928-9539-7BB642F38B7E@kf8nh.com>

On Jun 28, 2009, at 16:38 , Ryan Schmidt wrote:
> I could move the file and then put a symlink to it at the old  
> location...


Copy, then rename the old to php.ini.old or similar.

-- 
brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com
system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu
electrical and computer engineering, carnegie mellon university    KF8NH



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090629/feefe9ee/attachment.bin>

From nuvolare at email.it  Mon Jun 29 10:24:03 2009
From: nuvolare at email.it (nuvolare)
Date: Mon, 29 Jun 2009 19:24:03 +0200
Subject: Error for installation glade in Tiger
Message-ID: <7042D9C8-F7ED-4FE1-9663-05AB807ABBC4@email.it>

Hello, I did what you told me and it installed succecfully, but now  
how I've to run gale3?
I tryed by Terminal e by X11 but with out resul
What I've to do?
Thank you
 
 
 --
 Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
 
 Sponsor:
 Speciale Hotel + Parco Divertimento. Tanti pacchetti per le tue vacanze divertenti su 
* vacanzedivertenti.it 
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=9214&d=29-6

From devans at macports.org  Mon Jun 29 11:07:56 2009
From: devans at macports.org (David Evans)
Date: Mon, 29 Jun 2009 11:07:56 -0700
Subject: Error for installation glade in Tiger
In-Reply-To: <7042D9C8-F7ED-4FE1-9663-05AB807ABBC4@email.it>
References: <7042D9C8-F7ED-4FE1-9663-05AB807ABBC4@email.it>
Message-ID: <4A4902FC.7010700@macports.org>

nuvolare wrote:
> Hello, I did what you told me and it installed succecfully, but now 
> how I've to run gale3?
> I tryed by Terminal e by X11 but with out resul
> What I've to do?
> Thank you
>
>
Assuming that the port is installed in the default prefix path 
(/opt/local), the glade executable is installed as

/opt/local/bin/glade-3

To confirm on your system try

devans% port contents glade3
Port glade3 contains:
  /opt/local/bin/glade-3
  /opt/local/include/libgladeui-1.0/gladeui/glade-accels.h
  /opt/local/include/libgladeui-1.0/gladeui/glade-activatable-editor.h
  /opt/local/include/libgladeui-1.0/gladeui/glade-app.h
  /opt/local/include/libgladeui-1.0/gladeui/glade-attributes.h
...

make sure that this is in your path by typing

devans% which glade-3
/opt/local/bin/glade-3

if not edit your path to include /opt/local/bin

Since this is an X11 application, be sure your X11 server is running and 
type

glade-3

from xterm or

open-x11 glade-3

from the Terminal which will start X11 for you if necessary



From stefan at nowy.de  Mon Jun 29 12:57:00 2009
From: stefan at nowy.de (Stefan Nowy)
Date: Mon, 29 Jun 2009 21:57:00 +0200
Subject: Kile
Message-ID: <4A491C8C.50000@nowy.de>

Hi!

I'm relatively new to macports... trying to install the latex editor "kile".

I found an howto here (sorry, in german only):
http://www.rz.uni-konstanz.de/activekb/questions/175/Kile+als+LaTeX+Editor+auf+dem+Mac

What I basically did is the following:


sudo port selfupdate && sudo port sync
sudo port install kdelibs4 kdebase4-runtime
sudo chown -R $USER ~/Library/Preferences/KDE
launchctl load -F /Library/LaunchAgents/org.freedesktop.dbus-session.plist

after the last command nothing visible happened. Is this normal?

open /Applications/MacPorts/KDE4/kdeinit4.app

some icon appears jumping and disappears again. Nothing more.

svn co svn://anonsvn.kde.org/home/kde/trunk/extragear/office/kile
cd kile
cmake -DQT_QMAKE_EXECUTABLE=/opt/local/bin/qmake-mac
-DCMAKE_INSTALL_PREFIX=/opt/local .
make
sudo make install
cd  /opt/local/bin/kile.app/Contents/MacOS
sudo mv kile kile-bin

sudo nano kile
with this content:
#!/bin/bash
PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
/Applications/kile.app/Contents/MacOS/kile-bin

cd /opt/local/bin
sudo mv kile.app /Applications/


When I now click on the kile-icon, it appears jumping and disappears
again. Nothing more is happening...

I hope that somebody can help me!

Thank you
Stefan


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090629/6bafb5e0/attachment.bin>

From nuvolare at email.it  Mon Jun 29 13:31:42 2009
From: nuvolare at email.it (nuvolare)
Date: Mon, 29 Jun 2009 22:31:42 +0200
Subject: Error for installation glade in Tiger
In-Reply-To: <4A4902FC.7010700@macports.org>
References: <7042D9C8-F7ED-4FE1-9663-05AB807ABBC4@email.it>
	<4A4902FC.7010700@macports.org>
Message-ID: <DDE19A6B-9F29-41C1-84D1-B5864D38D65C@email.it>

Ok, I did everithing and all are as you told me the only thing that I  
didn't find is the port in (/opt/local) there is not port here.

I run glade by typing glade-3 on Terminal with X11 open and glade  
it's running but with out push-buttons, and in Terminal I find this  
message
I pasted only the last message

glade-3:23375): GladeUI-WARNING **: No icon named 'widget-gnome- 
iconlist' was found for object class 'GnomeIconList'.
GladeUI-Message: No displayable values for property  
GnomeIconList::selection-mode

(glade-3:23375): GladeUI-WARNING **: No icon named 'widget-bonobo- 
dock' was found for object class 'BonoboDock'.

(glade-3:23375): GladeUI-WARNING **: No icon named 'widget-bonobo- 
dockitem' was found for object class 'BonoboDockItem'.
Xlib:  extension "RANDR" missing on display ":0.0".

(glade-3:23375): Gtk-WARNING **: Impossibile trovare l'icona ?widget- 
gtk-frame?. Il tema ?hicolor?
non ? stato trovato e potrebbe essere necessario installarlo.
? possibile recuperarne una copia presso:
         http://icon-theme.freedesktop.org/releases




Il giorno 29/giu/09, alle ore 20:07, David Evans ha scritto:

> nuvolare wrote:
>> Hello, I did what you told me and it installed succecfully, but  
>> now how I've to run gale3?
>> I tryed by Terminal e by X11 but with out resul
>> What I've to do?
>> Thank you
>>
>>
> Assuming that the port is installed in the default prefix path (/ 
> opt/local), the glade executable is installed as
>
> /opt/local/bin/glade-3
>
> To confirm on your system try
>
> devans% port contents glade3
> Port glade3 contains:
>  /opt/local/bin/glade-3
>  /opt/local/include/libgladeui-1.0/gladeui/glade-accels.h
>  /opt/local/include/libgladeui-1.0/gladeui/glade-activatable-editor.h
>  /opt/local/include/libgladeui-1.0/gladeui/glade-app.h
>  /opt/local/include/libgladeui-1.0/gladeui/glade-attributes.h
> ...
>
> make sure that this is in your path by typing
>
> devans% which glade-3
> /opt/local/bin/glade-3
>
> if not edit your path to include /opt/local/bin
>
> Since this is an X11 application, be sure your X11 server is  
> running and type
>
> glade-3
>
> from xterm or
>
> open-x11 glade-3
>
> from the Terminal which will start X11 for you if necessary
>
>


 
 
 --
 Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
 
 Sponsor:
 OLTREMARE HOTELS:
* Cerchi un hotel a Riccione, Rimini o Misano Adriatico ? Visita il sito www.rivieraparkhotels.it . Gli alberghi dei parchi divertimento.
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=9284&d=29-6
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090629/1022bebf/attachment.html>

From raimue at macports.org  Mon Jun 29 17:25:41 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Tue, 30 Jun 2009 02:25:41 +0200
Subject: PHP upgrade to v5.2.10
In-Reply-To: <456B4EFB-F869-483D-AD48-CA4D9EA928EA@macports.org>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>	<0DC19D17-8CB2-460F-876A-B9706821651F@oakleystudio.com>
	<456B4EFB-F869-483D-AD48-CA4D9EA928EA@macports.org>
Message-ID: <4A495B85.3000203@macports.org>

On 2009-06-26 00:21, Ryan Schmidt wrote:
> I see they have fixed the problem in CVS, but they have not told us  
> how they fixed it. So we either wait for 5.2.11 and update the port  
> to that version, or someone has to find out what patch fixed the  
> problem and I can apply that patch in the portfile.

Digged a bit in their CVS and this should be the fix:
<http://cvs.php.net/viewvc.cgi/php-src/ext/date/php_date.c?r1=1.237&r2=1.238&view=patch>

Rainer

From ryandesign at macports.org  Mon Jun 29 21:56:27 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 29 Jun 2009 23:56:27 -0500
Subject: PHP upgrade to v5.2.10
In-Reply-To: <4A495B85.3000203@macports.org>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>	<0DC19D17-8CB2-460F-876A-B9706821651F@oakleystudio.com>
	<456B4EFB-F869-483D-AD48-CA4D9EA928EA@macports.org>
	<4A495B85.3000203@macports.org>
Message-ID: <09A616C2-667E-4153-97A8-8A2B28EBD3AB@macports.org>


On Jun 29, 2009, at 19:25, Rainer M?ller wrote:

> On 2009-06-26 00:21, Ryan Schmidt wrote:
>
>> I see they have fixed the problem in CVS, but they have not told us
>> how they fixed it. So we either wait for 5.2.11 and update the port
>> to that version, or someone has to find out what patch fixed the
>> problem and I can apply that patch in the portfile.
>
> Digged a bit in their CVS and this should be the fix:
> <http://cvs.php.net/viewvc.cgi/php-src/ext/date/php_date.c? 
> r1=1.237&r2=1.238&view=patch>

Thanks for finding that. I haven't had a chance to test on PowerPC  
but I added the patch and it's in php5 @5.2.10_1 and php5-devel  
@5.3.0RC4_1. PowerPC users are invited to see whether that works now.


From face at CentosPrime.COM  Tue Jun 30 06:05:53 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Tue, 30 Jun 2009 06:05:53 -0700
Subject: PHP upgrade to v5.2.10
In-Reply-To: <09A616C2-667E-4153-97A8-8A2B28EBD3AB@macports.org>
References: <2E1EBCE2-9CD7-4D91-9786-A0E7A9DDD64C@oakleystudio.com>
	<0DC19D17-8CB2-460F-876A-B9706821651F@oakleystudio.com>
	<456B4EFB-F869-483D-AD48-CA4D9EA928EA@macports.org>
	<4A495B85.3000203@macports.org>
	<09A616C2-667E-4153-97A8-8A2B28EBD3AB@macports.org>
Message-ID: <B809FCE1-F2BF-4ECA-9453-450388E227AF@centosprime.com>

On 2009-06-29 , at 21:56 , Ryan Schmidt wrote:

>> Digged a bit in their CVS and this should be the fix:
>> <http://cvs.php.net/viewvc.cgi/php-src/ext/date/php_date.c?r1=1.237&r2=1.238&view=patch 
>> >
>
> Thanks for finding that. I haven't had a chance to test on PowerPC  
> but I added the patch and it's in php5 @5.2.10_1 and php5-devel  
> @5.3.0RC4_1. PowerPC users are invited to see whether that works now.


face at x:face:125 $ which php
/opt/local/bin/php
face at x:face:126 $ php --version
PHP 5.2.10 (cli) (built: Jun 30 2009 05:44:33)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies
face at x:face:127 $ php <./foo.php
2009

Works here.

8)
----------------------------------
Chris Janton  - face at CentosPrime dot COM
Netminder for Opus1.COM



From inky788 at gmail.com  Tue Jun 30 07:03:22 2009
From: inky788 at gmail.com (Inky 788)
Date: Tue, 30 Jun 2009 10:03:22 -0400
Subject: installing ghc fails
Message-ID: <8b2374350906300703r63fc316as244e7234abcffc26@mail.gmail.com>

Hi,

I just tried installing pandoc, which requires ghc (among other things), and
it seems that there was a problem configuring ghc.

I'm on Mac OS X 10.5.7, Intel. This is just after a fresh install of
MacPorts 1.7.1-10.5-Leopard. I'm brand new to MacPorts. Xcode tools is
installed on this machine, as is X11, and OS X's Software Update says
everything is up to date.

Here's the terminal output:

~~~ snip ~~~
-->  Building ghc
Error: Target org.macports.build returned: shell command "cd
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ghc/work/ghc-6.10.3
&& env DYLD_FALLBACK_LIBRARY_PATH=/opt/local/lib make" returned error 2
Command output:                        --flags=-stage1 --flags=ncg
--flags=ghci --ghc-option=-DGHCI_TABLES_NEXT_TO_CODE
--enable-library-profiling
--with-compiler=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ghc/work/ghc-6.10.3/ghc/stage1-inplace/ghc
--with-hc-pkg=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ghc/work/ghc-6.10.3/utils/ghc-pkg/install-inplace/bin/ghc-pkg
\
                       --prefix=/NONEXISTENT --bindir=/NONEXISTENT
--libdir=/NONEXISTENT --libexecdir=/NONEXISTENT --datadir=/NONEXISTENT
--docdir=/NONEXISTENT --haddockdir=/NONEXISTENT --htmldir=/NONEXISTENT \
                       --libsubdir='$pkgid' --with-gcc=gcc
--with-ld=/usr/bin/ld --hsc2hs-option=-I/opt/local/include
--configure-option='--prefix=/opt/local'
--configure-option='--prefix=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ghc/work/destroot/opt/local'
--configure-option='--datadir=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ghc/work/destroot/opt/local/share/ghc-6.10.3'
--configure-option='--with-gmp-includes=/opt/local/include'
--configure-option='--with-gmp-libraries=/opt/local/lib'
--configure-option='--with-ghc=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ghc/work/ghc-bootstrap/bin/ghc'
--configure-option='CC=/usr/bin/gcc-4.0'  --configure-option='CFLAGS=-O2
-I/opt/local/include'  --configure-option='LDFLAGS=-L/opt/local/lib
-L/usr/lib'  --configure-option='CPPFLAGS=-I/opt/local/include'
--configure-option='CPP=/usr/bin/cpp-4.0' --configure-option=--with-cc="gcc"
--with-hsc2hs=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ghc/work/ghc-6.10.3/utils/hsc2hs/install-inplace/bin/hsc2hs
\
                       --ghc-option=-DSTAGE=2
Configuring ghc-6.10.3...
Warning: 'include-dirs: ../libffi/build/include' is a relative path outside
of
the source tree. This will not work when generating a tarball with 'sdist'.
Warning: 'include-dirs: ../libraries/base/cbits' is a relative path outside
of
the source tree. This will not work when generating a tarball with 'sdist'.
Warning: 'include-dirs: ../libraries/base/include' is a relative path
outside
of the source tree. This will not work when generating a tarball with
'sdist'.
Warning: 'include-dirs: stage2plus' directory does not exist.
rm -f -f Makefile-stage2
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ghc/work/ghc-6.10.3/libraries/cabal-bin
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ghc/work/ghc-bootstrap/bin/ghc
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ghc/work/ghc-6.10.3/libraries/bootstrapping.conf
1.6.0.3 makefile  --distpref dist-stage2 -f Makefile-stage2
Preprocessing library ghc-6.10.3...
Generating Makefile ghc-6.10.3...
../utils/mkdirhier/mkdirhier stage2plus
mkdir stage2plus
Creating stage2plus/ghc_boot_platform.h...
Done.
make -C compiler stage=2
make -f Makefile-stage2 stage=2
Makefile-stage2:86: dist-stage2/build/.depend: No such file or directory
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ghc/work/ghc-6.10.3/ghc/stage1-inplace/ghc
-M -dep-makefile dist-stage2/build/.depend -dep-suffix-s -dep-suffixp
-DGHCI_TABLES_NEXT_TO_CODE -DSTAGE=2 -package-name ghc-6.10.3
-hide-all-packages -no-user-package-conf -i -idist-stage2/build -inativeGen
-ibasicTypes -icmm -icodeGen -icoreSyn -icprAnalysis -ideSugar -ighci
-ihsSyn -iiface -imain -iparser -iprelude -iprofiling -irename -isimplCore
-isimplStg -ispecialise -istgSyn -istranal -itypecheck -itypes -iutils
-ivectorise -idist-stage2/build/autogen -Idist-stage2/build/autogen
-Idist-stage2/build -I../libffi/build/include -Istage2plus
-I../libraries/base/cbits -I../libraries/base/include -I. -Iparser -Iutils
-optP-DGHCI -optP-include -optPdist-stage2/build/autogen/cabal_macros.h
-odir dist-stage2/build -hidir dist-stage2/build -stubdir dist-stage2/build
-package Cabal-1.6.0.3 -package array-0.2.0.0 -package base-4.1.0.0 -package
bytestring-0.9.1.4 -package containers-0.2.0.1 -package directory-1.0.0.3
-package filepath-1.1.0.2 -package haskell98-1.0.1.0 -package hpc-0.5.0.3
-package old-time-1.0.0.2 -package process-1.0.1.1 -package
template-haskell-2.3.0.1 -package unix-2.3.2.0 -O -Wall
-fno-warn-name-shadowing -fno-warn-orphans -XCPP -XMagicHash -XUnboxedTuples
-XPatternGuards -XForeignFunctionInterface -XEmptyDataDecls
-XTypeSynonymInstances -XMultiParamTypeClasses -XFlexibleInstances
-XRank2Types -XScopedTypeVariables -XDeriveDataTypeable -idist-stage2/build
-H32m -O -I/opt/local/include -L/opt/local/lib -Rghc-timing -O2 AsmCodeGen
MachCodeGen MachInstrs MachRegs NCGMonad PositionIndependentCode PprMach
RegAllocColor RegAllocInfo RegAllocLinear RegAllocStats RegArchBase
RegArchX86 RegCoalesce RegLiveness RegSpill RegSpillClean RegSpillCost
DsMeta TcSplice Convert ByteCodeAsm ByteCodeFFI ByteCodeGen ByteCodeInstr
ByteCodeItbls ByteCodeLink Debugger LibFFI Linker ObjLink RtClosureInspect
BasicTypes DataCon Demand Exception Id IdInfo Literal MkId Module Name
NameEnv NameSet NewDemand OccName RdrName SrcLoc UniqSupply Unique Var
VarEnv VarSet BlockId CLabel Cmm CmmBrokenBlock CmmCPS CmmCPSGen CmmCPSZ
CmmCallConv CmmCommonBlockElimZ CmmContFlowOpt CmmCvt CmmExpr CmmInfo CmmLex
CmmLint CmmLive CmmLiveZ CmmOpt CmmParse CmmProcPoint CmmProcPointZ
CmmSpillReload CmmTx CmmUtils CmmZipUtil DFMonad Dataflow MachOp MkZipCfg
MkZipCfgCmm OptimizationFuel PprC PprCmm PprCmmZ StackColor StackPlacements
ZipCfg ZipCfgCmmRep ZipCfgExtras ZipDataflow Bitmap CgBindery CgCallConv
CgCase CgClosure CgCon CgExpr CgForeignCall CgHeapery CgHpc CgInfoTbls
CgLetNoEscape CgMonad CgParallel CgPrimOp CgProf CgStackery CgTailCall
CgTicky CgUtils ClosureInfo CodeGen SMRep CoreFVs CoreLint CorePrep
CoreSubst CoreSyn CoreTidy CoreUnfold CoreUtils ExternalCore MkCore
MkExternalCore PprCore PprExternalCore CprAnalyse Check Coverage Desugar
DsArrows DsBinds DsCCall DsExpr DsForeign DsGRHSs DsListComp DsMonad DsUtils
Match MatchCon MatchLit HsBinds HsDecls HsDoc HsExpr HsImpExp HsLit HsPat
HsSyn HsTypes HsUtils BinIface BuildTyCl IfaceEnv IfaceSyn IfaceType
LoadIface MkIface TcIface BreakArray CmdLineParser CodeOutput Config
Constants DriverMkDepend DriverPhases DriverPipeline DynFlags ErrUtils
Finder GHC HeaderInfo HscMain HscStats HscTypes InteractiveEval
PackageConfig Packages ParsePkgConf PprTyThing StaticFlags StaticFlagParser
SysTools TidyPgm Ctype HaddockLex HaddockParse HaddockUtils LexCore Lexer
Parser ParserCore ParserCoreUtils RdrHsSyn ForeignCall PrelInfo PrelNames
PrelRules PrimOp TysPrim TysWiredIn CostCentre SCCfinal RnBinds RnEnv RnExpr
RnHsDoc RnHsSyn RnNames RnPat RnSource RnTypes CSE FloatIn FloatOut
LiberateCase OccurAnal SAT SetLevels SimplCore SimplEnv SimplMonad
SimplUtils Simplify SRT SimplStg StgStats Rules SpecConstr Specialise
CoreToStg StgLint StgSyn DmdAnal SaAbsInt SaLib StrictAnal WorkWrap WwLib
FamInst Inst TcArrows TcBinds TcClassDcl TcDefaults TcDeriv TcEnv TcExpr
TcForeign TcGenDeriv TcHsSyn TcHsType TcInstDcls TcMType TcMatches TcPat
TcRnDriver TcRnMonad TcRnTypes TcRules TcSimplify TcTyClsDecls TcTyDecls
TcTyFuns TcType TcUnify Class Coercion FamInstEnv FunDeps Generics InstEnv
TyCon Type TypeRep Unify Bag Binary BufWrite Digraph Encoding FastBool
FastFunctions FastMutInt FastString FastTypes Fingerprint FiniteMap
GraphBase GraphColor GraphOps GraphPpr IOEnv Interval LazyUniqFM ListSetOps
Maybes MonadUtils OrdList Outputable Panic Pretty State StringBuffer Unicode
UniqFM UniqSet Util VectBuiltIn VectCore VectMonad VectType VectUtils
Vectorise
cmm/OptimizationFuel.hs: openBinaryFile: resource busy (file is locked)
<<ghc: 151205468 bytes, 23 GCs, 1713493/3493888 avg/max bytes residency (3
samples), 34M in use, 0.00 INIT (0.00 elapsed), 0.16 MUT (1.34 elapsed),
0.04 GC (0.05 elapsed) :ghc>>
make[3]: *** [dist-stage2/build/.depend] Error 1
make[2]: *** [build.stage.2] Error 2
make[1]: *** [stage2] Error 2
make: *** [bootstrap2] Error 2

Error: The following dependencies failed to build: ghc haddock hs-ghc-paths
Error: Status 1 encountered during processing.
~~~ /snip ~~~

Please let me know if there's any more useful info I can provide.

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090630/57a37963/attachment.html>

From nuvolare at email.it  Tue Jun 30 07:11:42 2009
From: nuvolare at email.it (nuvolare)
Date: Tue, 30 Jun 2009 16:11:42 +0200
Subject: Error for installation glade in Tiger
Message-ID: <4D73E18D-5454-49B0-843E-80A6911E94A7@email.it>

Hello, after I installed the glade I've problem with the icon in glade.
Terminal show some error like:

MacbookPro:~ nuvolare$ glade-3
Xlib:  extension "RANDR" missing on display ":0.0".

(glade-3:24053): GladeUI-CRITICAL **: Impossibile caricare l'immagine  
(Impossibile riconoscere il formato di immagine per il file ?/opt/ 
local/share/glade3/pixmaps/plus.png?)
Dynamic session lookup supported but failed: launchd did not provide  
a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide  
a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide  
a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide  
a socket path, verify that org.freedesktop.dbus-session.plist is loaded!

..............

(glade-3:24053): GladeUI-WARNING **: No icon named 'widget-gnome- 
canvas' was found for object class 'GnomeCanvas'.

(glade-3:24053): GladeUI-WARNING **: No icon named 'widget-gnome- 
iconlist' was found for object class 'GnomeIconList'.
GladeUI-Message: No displayable values for property  
GnomeIconList::selection-mode

(glade-3:24053): GladeUI-WARNING **: No icon named 'widget-bonobo- 
dock' was found for object class 'BonoboDock'.

(glade-3:24053): GladeUI-WARNING **: No icon named 'widget-bonobo- 
dockitem' was found for object class 'BonoboDockItem'.
Xlib:  extension "RANDR" missing on display ":0.0".

(glade-3:24053): Gtk-WARNING **: Impossibile trovare l'icona ?widget- 
gtk-frame?. Il tema ?hicolor?
non ? stato trovato e potrebbe essere necessario installarlo.
? possibile recuperarne una copia presso:
         http://icon-theme.freedesktop.org/releases

How I can do to resolve it?
Thank you
 
 
 --
 Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
 
 Sponsor:
 250 Biglietti da Visita gratuiti + 1 elegante Porta biglietti metallico! Spese di spedizione escluse. Offerta limitata, fai in fretta!
 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=8957&d=30-6