From cedayiv at gmail.com  Thu Jan  1 01:57:14 2009
From: cedayiv at gmail.com (Charles Day)
Date: Thu, 1 Jan 2009 01:57:14 -0800
Subject: GnuCash packaging
Message-ID: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>

Olaf,
Before I joined the list, I saw an email from you in October (see
http://lists.macosforge.org/pipermail/macports-users/2008-October/012020.html)
about
trying to package gnucash with "port mdmg". Were you ever successful in
working around the error? I ask because I now have the same problem.
$ sudo port mdmg gnucash +no_x11
--->  Creating pkg for gnucash-2.2.8
Error: Target org.macports.pkg returned: shell command
"PMResourceLocale=English
/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker
-AppleLanguages "(English)" --root
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gnucash/work/destroot
--out
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gnucash/work/gnucash-2.2.8.pkg
 --resources
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gnucash/work/pkg_resources
--title "gnucash-2.2.8" --info
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gnucash/work/Info.plist
--target 10.3 --domain system --id org.macports.gnucash" returned error 1
Command output: Warning: Unknown argument: -AppleLanguages
Warning: Unknown argument: (English)
ERROR: The specified root is invalid:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gnucash/work/destroot

Error: Status 1 encountered during processing.


Cheers,
Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090101/e66c8465/attachment.html>

From olaf at foellinger.de  Thu Jan  1 10:02:17 2009
From: olaf at foellinger.de (Olaf Foellinger)
Date: Thu, 1 Jan 2009 19:02:17 +0100
Subject: GnuCash packaging
In-Reply-To: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
Message-ID: <20090101180217.GA25138@foellinger.de>

Hi Charles,

* Charles Day <cedayiv at gmail.com> [01.01.09 12:30]wrote:

>    Olaf,
> 
>    Before I joined the list, I saw an email from you in October
>    (see [1]http://lists.macosforge.org/pipermail/macports-users/2008-Octob
>    er/012020.html) about trying to package gnucash with "port mdmg". Were
>    you ever successful in working around the error? I ask because I now
>    have the same problem.
>    $ sudo port mdmg gnucash +no_x11
>    --->  Creating pkg for gnucash-2.2.8
>    Error: Target org.macports.pkg returned: shell command

no I wasn't successful yet. I'm eve not sure what wold be the content of
the mdmg file. I take your mail as a starter to update my port system to
1.7 and investigate this further. Currently 

$ sudo port upgrade outdated

is running which will take some time since there are some outdated
packages. Afterwards I'll try the packaging again.

Gru? Olaf

From cedayiv at gmail.com  Thu Jan  1 15:19:55 2009
From: cedayiv at gmail.com (Charles Day)
Date: Thu, 1 Jan 2009 15:19:55 -0800
Subject: GnuCash packaging
In-Reply-To: <20090101180217.GA25138@foellinger.de>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<20090101180217.GA25138@foellinger.de>
Message-ID: <1d6843d80901011519u182c188ei4dc4be06da8fb360@mail.gmail.com>

On Thu, Jan 1, 2009 at 10:02 AM, Olaf Foellinger <olaf at foellinger.de> wrote:

> Hi Charles,
>
> * Charles Day <cedayiv at gmail.com> [01.01.09 12:30]wrote:
>
> >    Olaf,
> >
> >    Before I joined the list, I saw an email from you in October
> >    (see [1]
> http://lists.macosforge.org/pipermail/macports-users/2008-Octob
> >    er/012020.html) about trying to package gnucash with "port mdmg". Were
> >    you ever successful in working around the error? I ask because I now
> >    have the same problem.
> >    $ sudo port mdmg gnucash +no_x11
> >    --->  Creating pkg for gnucash-2.2.8
> >    Error: Target org.macports.pkg returned: shell command
>
> no I wasn't successful yet. I'm eve not sure what wold be the content of
> the mdmg file. I take your mail as a starter to update my port system to
> 1.7 and investigate this further. Currently
>
> $ sudo port upgrade outdated
>

I noticed that the portfile for gnucash 2.2.8 automatically throws out the
dependency on evince if you use the +no_x11 variant. If fact all I had to do
by hand now was to change the aqbanking portfile to get rid of the qbanking
and cbanking front ends. I wonder if there could be a +no_x11 variant
created for aqbanking which would do this automatically? But I don't really
understand aqbanking, so maybe that isn't really correct except for gnucash
users - I don't know.


> is running which will take some time since there are some outdated
> packages. Afterwards I'll try the packaging again.
>
> Gru? Olaf
>

Cheers,
Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090101/25f78a40/attachment.html>

From john_owens at yahoo.com  Thu Jan  1 19:41:15 2009
From: john_owens at yahoo.com (John Owens)
Date: Fri, 2 Jan 2009 03:41:15 +0000 (UTC)
Subject: tex wanting to install even though it's not outdated
Message-ID: <loom.20090102T033847-831@post.gmane.org>

classico 8914$ port outdated
No installed ports are outdated.
classico 8914$ sudo port upgrade installed
--->  Extracting texlive_texmf-full

So I'm using MacTeX (in /usr/texbin) for my TeX distribution
now, and have set binpath in macports.conf accordingly. This
works fine. How can I keep "port upgrade installed" from
wanting to install a macports texlive? (Perhaps one of my
ports depends on it; how could I figure that out?)

JDO


From lists at sequestered.net  Thu Jan  1 20:51:15 2009
From: lists at sequestered.net (Corey Chandler)
Date: Thu, 01 Jan 2009 20:51:15 -0800
Subject: tex wanting to install even though it's not outdated
In-Reply-To: <loom.20090102T033847-831@post.gmane.org>
References: <loom.20090102T033847-831@post.gmane.org>
Message-ID: <495D9D43.7020807@sequestered.net>

John Owens wrote:
> classico 8914$ port outdated
> No installed ports are outdated.
> classico 8914$ sudo port upgrade installed
> --->  Extracting texlive_texmf-full
>
> So I'm using MacTeX (in /usr/texbin) for my TeX distribution
> now, and have set binpath in macports.conf accordingly. This
> works fine. How can I keep "port upgrade installed" from
> wanting to install a macports texlive? (Perhaps one of my
> ports depends on it; how could I figure that out?)
>
> JDO
>   
I've never attempted "port upgrade installed", I've always done "port 
upgrade outdated."

From frstan at bellsouth.net  Thu Jan  1 22:15:12 2009
From: frstan at bellsouth.net (William Davis)
Date: Fri, 2 Jan 2009 01:15:12 -0500
Subject: upgrading vim and vim-app
Message-ID: <58474D55-785B-442C-8E79-A8C028B60B06@bellsouth.net>

upgrading vim-app

  _get_locale_val in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _main in main.o
       _main in main.o
       _enc_locale in mbyte.o
       _mac_lang_init in os_mac_conv.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[1]: *** [Vim] Error 1
make: *** [all] Error 2

Warning: the following items did not execute (for vim-app):  
org.macports.destroot org.macports.build
DEBUG: Registry error: grep not registered as installed & active.
     invoked from within
"registry_active ${portname}"
     invoked from within
"$workername eval registry_active \${portname}"
Error: Unable to upgrade port: 1
macintosh:~ frstan$ which grep
/usr/bin/grep

upgrading vim

  "__Xsetlocale", referenced from:
       _get_locale_val in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _main in main.o
       _main in main.o
       _enc_locale in mbyte.o
       _mac_lang_init in os_mac_conv.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[1]: *** [vim] Error 1
make: *** [all] Error 2

Warning: the following items did not execute (for vim):  
org.macports.destroot org.macports.build
DEBUG: invalid command name "::ui_init"
     while executing
"::ui_init $priority $prefix $channels $message"
     ("uplevel" body line 2)
     invoked from within
"uplevel 1 $body"
Error: Unable to upgrade port: 1


MacPorts 1.7


William Davis
frstanATbellsouthDOTnet
Mac OS X.5.6 Darwin 9.5.0
XQuartz 2.3.2_rc5 (xorg-server 1.4.2-apple30)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From eravin at panix.com  Fri Jan  2 00:03:24 2009
From: eravin at panix.com (Ed Ravin)
Date: Fri, 2 Jan 2009 03:03:24 -0500
Subject: skey uninstallable again
Message-ID: <20090102080324.GA23722@panix.com>

I see from the archive that this problem also happened last year around
this time.  The fix then was to add the Fink mirror to the portfolio,
but skey isn't on that server anymore either.

Why did skey disappear from all those sites in the first place?

	-- Ed

---------------------------------------------------------------
# port upgrade skey
--->  Fetching skey
--->  Attempting to fetch skey-1.1.5.tar.gz from
http://distfiles.macports.org/skey
--->  Attempting to fetch skey-1.1.5.tar.gz from
http://master.us.finkmirrors.net/distfiles/md5/c4bc3be60fe1aa8961537fb4b3708568/
--->  Attempting to fetch skey-1.1.5.tar.gz from
http://trd.no.distfiles.macports.org/skey
--->  Attempting to fetch skey-1.1.5.tar.gz from
ftp://ftp.ayamura.org/pub/misc/
--->  Attempting to fetch skey-1.1.5.tar.gz from
http://svn.macports.org/repository/macports/distfiles/skey
--->  Attempting to fetch skey-1.1.5.tar.gz from
http://svn.macports.org/repository/macports/distfiles/general/
--->  Attempting to fetch skey-1.1.5.tar.gz from
http://svn.macports.org/repository/macports/downloads/skey
Error: Target org.macports.fetch returned: fetch failed
Error: Unable to upgrade port: 1


From fbartolom at gmail.com  Fri Jan  2 03:37:06 2009
From: fbartolom at gmail.com (Fabrizio Bartolomucci)
Date: Fri, 02 Jan 2009 12:37:06 +0100
Subject: New Mac user and gdk-pixbuf-2-0
In-Reply-To: <495BC864.9000708@macports.org>
References: <495BAEDB.8050809@gmail.com> <495BC864.9000708@macports.org>
Message-ID: <495DFC62.8050102@gmail.com>

An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090102/d16533a3/attachment.html>

From raimue at macports.org  Fri Jan  2 05:29:01 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Fri, 02 Jan 2009 14:29:01 +0100
Subject: upgrading vim and vim-app
In-Reply-To: <58474D55-785B-442C-8E79-A8C028B60B06@bellsouth.net>
References: <58474D55-785B-442C-8E79-A8C028B60B06@bellsouth.net>
Message-ID: <495E169D.8050306@macports.org>

William Davis wrote:
> upgrading vim-app
> 
>   _get_locale_val in ex_cmds2.o
>        _ex_language in ex_cmds2.o
>        _ex_language in ex_cmds2.o
>        _ex_language in ex_cmds2.o
>        _main in main.o
>        _main in main.o
>        _enc_locale in mbyte.o
>        _mac_lang_init in os_mac_conv.o
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[1]: *** [Vim] Error 1
> make: *** [all] Error 2
> 
> Warning: the following items did not execute (for vim-app):  
> org.macports.destroot org.macports.build
> DEBUG: Registry error: grep not registered as installed & active.
>      invoked from within
> "registry_active ${portname}"
>      invoked from within
> "$workername eval registry_active \${portname}"
> Error: Unable to upgrade port: 1
> macintosh:~ frstan$ which grep
> /usr/bin/grep

The dependency is just bin:grep:grep, so it should not fail here on
this. I don't know why it tries to find grep in the registry.

> upgrading vim
> 
>   "__Xsetlocale", referenced from:
>        _get_locale_val in ex_cmds2.o
>        _ex_language in ex_cmds2.o
>        _ex_language in ex_cmds2.o
>        _ex_language in ex_cmds2.o
>        _main in main.o
>        _main in main.o
>        _enc_locale in mbyte.o
>        _mac_lang_init in os_mac_conv.o
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[1]: *** [vim] Error 1
> make: *** [all] Error 2
> 
> Warning: the following items did not execute (for vim):  
> org.macports.destroot org.macports.build
> DEBUG: invalid command name "::ui_init"
>      while executing
> "::ui_init $priority $prefix $channels $message"
>      ("uplevel" body line 2)
>      invoked from within
> "uplevel 1 $body"
> Error: Unable to upgrade port: 1

This looks like #17606. I was unable to reproduce this. Do you have X11
and the X11SDK installed?

Rainer

[1] https://trac.macports.org/ticket/17606

From devans at macports.org  Fri Jan  2 07:49:27 2009
From: devans at macports.org (David Evans)
Date: Fri, 02 Jan 2009 07:49:27 -0800
Subject: New Mac user and gdk-pixbuf-2-0
In-Reply-To: <495DFC62.8050102@gmail.com>
References: <495BAEDB.8050809@gmail.com> <495BC864.9000708@macports.org>
	<495DFC62.8050102@gmail.com>
Message-ID: <495E3787.3040303@macports.org>

Fabrizio Bartolomucci wrote:
> Thanks, but if I do so it asks me for a version; if I specify one at
> random it says it is not installed:
> $ sudo ./port activate gtk2
> --->  The following versions of gtk2 are currently installed:
> --->      gtk2 @2.12.9_0+x11
> --->      gtk2 @2.14.3_2+x11
> --->      gtk2 @2.14.5_0+x11
> Error: port activate failed: Registry error: Please specify the full
> version as recorded in the port registry.
>
> $ sudo ./port activate "gtk2 @2.14.5_0+x11"
> Error: port activate failed: Registry error: gtk2  2.14.5_0+x11 not
> registered as installed.
>
This is because you have more than one version installed. 

To activate the latest version:

sudo port activate gtk2 @2.14.5_0+x11

To remove a previous version (if you don't need it anymore)

sudo port uninstall gtk2 @2.12.9_0+x11

Dave


From devans at macports.org  Fri Jan  2 08:35:01 2009
From: devans at macports.org (David Evans)
Date: Fri, 02 Jan 2009 08:35:01 -0800
Subject: skey uninstallable again
In-Reply-To: <20090102080324.GA23722@panix.com>
References: <20090102080324.GA23722@panix.com>
Message-ID: <495E4235.2080102@macports.org>

Ed Ravin wrote:
> I see from the archive that this problem also happened last year around
> this time.  The fix then was to add the Fink mirror to the portfolio,
> but skey isn't on that server anymore either.
>
> Why did skey disappear from all those sites in the first place?
>
>   
No idea but it looks like it is available from gentoo mirrors in bz2
format.

Updated master_sites list in r44725.  Try again after next port sync.

Dave


From eravin at panix.com  Fri Jan  2 08:55:15 2009
From: eravin at panix.com (Ed Ravin)
Date: Fri, 2 Jan 2009 11:55:15 -0500
Subject: skey uninstallable again
In-Reply-To: <495E4115.6060404@orindasoftware.com>
References: <20090102080324.GA23722@panix.com>
	<495E4115.6060404@orindasoftware.com>
Message-ID: <20090102165514.GA8349@panix.com>

On Fri, Jan 02, 2009 at 08:30:13AM -0800, David Evans wrote:
> Ed Ravin wrote:
> > I see from the archive that this problem also happened last year around
> > this time.  The fix then was to add the Fink mirror to the portfolio,
> > but skey isn't on that server anymore either.
> >
> > Why did skey disappear from all those sites in the first place?
> >
> >   
> No idea but it looks like it is available from gentoo mirrors in bz2
> format. 
> 
> Updated master_sites list in r44725.  Try again after next port sync.

Thanks!  But it still won't install, at least not on my Mac Mini PPC
running 10.4.  See the output below.  Note that sha1.h is indeed in
the work dir, but it's not being found.

Also, I see this skey tarball has a bug that generates incorrect
SHA1 passwords.  It's been fixed in the NetBSD distribution that the
code originated from.

----------------------------------------------
Command output: /usr/bin/gcc-4.0 -O2 -DHAVE_CONFIG_H
-DSENDMAIL=\"/usr/sbin/sendmail\" -DSKEYKEYS=\"/opt/local/etc/skeykeys\"
-c -o skeylogin.o skeylogin.c
skeylogin.c:43:18: error: sha1.h: No such file or directory
skeylogin.c: In function 'hash_collapse':
skeylogin.c:421: warning: pointer targets in passing argument 1 of 'strlen'
differ in signedness
skeylogin.c:422: warning: pointer targets in passing argument 1 of 'strlen'
differ in signedness
skeylogin.c:424: warning: pointer targets in passing argument 1 of 'strlen'
differ in signedness
skeylogin.c:424: warning: pointer targets in passing argument 1 of 'strlen'
differ in signedness
skeylogin.c: In function 'skey_authenticate':
skeylogin.c:452: error: 'SHA1_CTX' undeclared (first use in this function)
skeylogin.c:452: error: (Each undeclared identifier is reported only once
skeylogin.c:452: error: for each function it appears in.)
skeylogin.c:452: error: parse error before 'ctx'
skeylogin.c:476: warning: assignment makes pointer from integer without a
cast
skeylogin.c:483: warning: pointer targets in passing argument 1 of 'strlen'
differ in signedness
skeylogin.c:493: warning: pointer targets in assignment differ in
signedness
skeylogin.c:507: error: 'ctx' undeclared (first use in this function)
skeylogin.c:517: warning: pointer targets in passing argument 1 of 'strlen'
differ in signedness
make: *** [skeylogin.o] Error 1

Error: Unable to upgrade port: 1


From frstan at bellsouth.net  Fri Jan  2 10:10:44 2009
From: frstan at bellsouth.net (William Davis)
Date: Fri, 2 Jan 2009 13:10:44 -0500
Subject: upgrading vim and vim-app
In-Reply-To: <495E169D.8050306@macports.org>
References: <58474D55-785B-442C-8E79-A8C028B60B06@bellsouth.net>
	<495E169D.8050306@macports.org>
Message-ID: <5C29914C-9DC5-452E-875F-DF00B337347A@bellsouth.net>


On Jan 2, 2009, at 8:29 AM, Rainer M?ller wrote:

> William Davis wrote:
>> upgrading vim-app
>>
>>  _get_locale_val in ex_cmds2.o
>>       _ex_language in ex_cmds2.o
>>       _ex_language in ex_cmds2.o
>>       _ex_language in ex_cmds2.o
>>       _main in main.o
>>       _main in main.o
>>       _enc_locale in mbyte.o
>>       _mac_lang_init in os_mac_conv.o
>> ld: symbol(s) not found
>> collect2: ld returned 1 exit status
>> make[1]: *** [Vim] Error 1
>> make: *** [all] Error 2
>>
>> Warning: the following items did not execute (for vim-app):
>> org.macports.destroot org.macports.build
>> DEBUG: Registry error: grep not registered as installed & active.
>>     invoked from within
>> "registry_active ${portname}"
>>     invoked from within
>> "$workername eval registry_active \${portname}"
>> Error: Unable to upgrade port: 1
>> macintosh:~ frstan$ which grep
>> /usr/bin/grep
>
> The dependency is just bin:grep:grep, so it should not fail here on
> this. I don't know why it tries to find grep in the registry.
>
>> upgrading vim
>>
>>  "__Xsetlocale", referenced from:
>>       _get_locale_val in ex_cmds2.o
>>       _ex_language in ex_cmds2.o
>>       _ex_language in ex_cmds2.o
>>       _ex_language in ex_cmds2.o
>>       _main in main.o
>>       _main in main.o
>>       _enc_locale in mbyte.o
>>       _mac_lang_init in os_mac_conv.o
>> ld: symbol(s) not found
>> collect2: ld returned 1 exit status
>> make[1]: *** [vim] Error 1
>> make: *** [all] Error 2
>>
>> Warning: the following items did not execute (for vim):
>> org.macports.destroot org.macports.build
>> DEBUG: invalid command name "::ui_init"
>>     while executing
>> "::ui_init $priority $prefix $channels $message"
>>     ("uplevel" body line 2)
>>     invoked from within
>> "uplevel 1 $body"
>> Error: Unable to upgrade port: 1
>
> This looks like #17606. I was unable to reproduce this. Do you have  
> X11
> and the X11SDK installed?
>
> Rainer
>
> [1] https://trac.macports.org/ticket/17606

yes I do, and have upgraded vim many times without problems previously.

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.6 Darwin 9.5.0
XQuartz 2.3.2_rc5 (xorg-server 1.4.2-apple30)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From devans at macports.org  Fri Jan  2 10:15:14 2009
From: devans at macports.org (David Evans)
Date: Fri, 02 Jan 2009 10:15:14 -0800
Subject: skey uninstallable again
In-Reply-To: <20090102165514.GA8349@panix.com>
References: <20090102080324.GA23722@panix.com>	<495E4115.6060404@orindasoftware.com>
	<20090102165514.GA8349@panix.com>
Message-ID: <495E59B2.2070107@macports.org>

Ed Ravin wrote:
> On Fri, Jan 02, 2009 at 08:30:13AM -0800, David Evans wrote:
>   
>> Ed Ravin wrote:
>>     
>>> I see from the archive that this problem also happened last year around
>>> this time.  The fix then was to add the Fink mirror to the portfolio,
>>> but skey isn't on that server anymore either.
>>>
>>> Why did skey disappear from all those sites in the first place?
>>>
>>>   
>>>       
>> No idea but it looks like it is available from gentoo mirrors in bz2
>> format. 
>>
>> Updated master_sites list in r44725.  Try again after next port sync.
>>     
>
> Thanks!  But it still won't install, at least not on my Mac Mini PPC
> running 10.4.  See the output below.  Note that sha1.h is indeed in
> the work dir, but it's not being found.
>   
On my machine (10.4.11 ppc) configure correctly determines that there is
no sha1.h installed
and it subsequently builds without error and installs one as part of the
port.
> Also, I see this skey tarball has a bug that generates incorrect
> SHA1 passwords.  It's been fixed in the NetBSD distribution that the
> code originated from.
>   
Do you have a reference for this?  I downloaded a copy of the tarball from

http://ftp.netbsd.org/pub/NetBSD/packages/distfiles/

and it has the same checksums as the gentoo tarball. 


From eravin at panix.com  Fri Jan  2 10:40:48 2009
From: eravin at panix.com (Ed Ravin)
Date: Fri, 2 Jan 2009 13:40:48 -0500
Subject: skey uninstallable again
In-Reply-To: <495E59B2.2070107@macports.org>
References: <20090102080324.GA23722@panix.com>
	<495E4115.6060404@orindasoftware.com>
	<20090102165514.GA8349@panix.com> <495E59B2.2070107@macports.org>
Message-ID: <20090102184048.GB8028@panix.com>

On Fri, Jan 02, 2009 at 10:15:14AM -0800, David Evans wrote:
...
> > Thanks!  But it still won't install, at least not on my Mac Mini PPC
> > running 10.4.  See the output below.  Note that sha1.h is indeed in
> > the work dir, but it's not being found.
> >   
> On my machine (10.4.11 ppc) configure correctly determines that there is
> no sha1.h installed
> and it subsequently builds without error and installs one as part of the
> port.

I already have sha1.h since it came in from the previous install of skey:

$ locate sha1.h | grep sha1.h$
/Developer/SDKs/MacOSX10.3.9.sdk/usr/include/httpd/ap_sha1.h
/Developer/SDKs/MacOSX10.3.9.sdk/usr/include/php/ext/standard/sha1.h
/Developer/SDKs/MacOSX10.4u.sdk/usr/include/httpd/ap_sha1.h
/Developer/SDKs/MacOSX10.4u.sdk/usr/include/php/ext/standard/sha1.h
/opt/local/include/sha1.h
/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_aqua_qt4-mac/work/qt-mac-opensource-src-4.2.2/examples/network/torrent/3rdparty/sha1.h
/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_net_ethereal/work/ethereal-0.99.0/epan/sha1.h
/opt/local/var/macports/software/skey/1.1.5_0/opt/local/include/sha1.h
/usr/include/httpd/ap_sha1.h
/usr/include/php/ext/standard/sha1.h

> > Also, I see this skey tarball has a bug that generates incorrect
> > SHA1 passwords.  It's been fixed in the NetBSD distribution that the
> > code originated from.
> >   
> Do you have a reference for this?  I downloaded a copy of the tarball from
> 
> http://ftp.netbsd.org/pub/NetBSD/packages/distfiles/
> 
> and it has the same checksums as the gentoo tarball. 

It was fixed in the NetBSD OS distribution back in 2001:

   http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=12045
   >Number:         12045
   >Category:       lib
   >Synopsis:       skey generates incorrect passwords when using SHA-1

but the fix never seems to have made it out of the OS and into pkgsrc.
I'll have to ask about this on pkgsrc-users.

From devans at macports.org  Fri Jan  2 12:34:54 2009
From: devans at macports.org (David Evans)
Date: Fri, 02 Jan 2009 12:34:54 -0800
Subject: skey uninstallable again
In-Reply-To: <20090102184048.GB8028@panix.com>
References: <20090102080324.GA23722@panix.com>
	<495E4115.6060404@orindasoftware.com>
	<20090102165514.GA8349@panix.com> <495E59B2.2070107@macports.org>
	<20090102184048.GB8028@panix.com>
Message-ID: <495E7A6E.1070407@macports.org>

Ed Ravin wrote:
> I already have sha1.h since it came in from the previous install of skey:
>
> $ locate sha1.h | grep sha1.h$
> /Developer/SDKs/MacOSX10.3.9.sdk/usr/include/httpd/ap_sha1.h
> /Developer/SDKs/MacOSX10.3.9.sdk/usr/include/php/ext/standard/sha1.h
> /Developer/SDKs/MacOSX10.4u.sdk/usr/include/httpd/ap_sha1.h
> /Developer/SDKs/MacOSX10.4u.sdk/usr/include/php/ext/standard/sha1.h
> /opt/local/include/sha1.h
> /opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_aqua_qt4-mac/work/qt-mac-opensource-src-4.2.2/examples/network/torrent/3rdparty/sha1.h
> /opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_net_ethereal/work/ethereal-0.99.0/epan/sha1.h
> /opt/local/var/macports/software/skey/1.1.5_0/opt/local/include/sha1.h
> /usr/include/httpd/ap_sha1.h
> /usr/include/php/ext/standard/sha1.h
>   
So if you deactivate (or otherwise remove) the old version does the
package install properly?  Was the old
version installed with MacPorts or otherwise?
>
>   
> It was fixed in the NetBSD OS distribution back in 2001:
>
>    http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=12045
>    >Number:         12045
>    >Category:       lib
>    >Synopsis:       skey generates incorrect passwords when using SHA-1
>
> but the fix never seems to have made it out of the OS and into pkgsrc.
> I'll have to ask about this on pkgsrc-users.
>
>   
OK, let us know what you find out.  Since you have an interest in this,
if you want, once you have the
port working correctly locally, make a patch relative to the old one and
post it as a ticket on trac.  Since
there is currently no maintainer, you can be it if you like.

From bcbarnes at gmail.com  Fri Jan  2 14:40:56 2009
From: bcbarnes at gmail.com (Brian Barnes)
Date: Fri, 2 Jan 2009 16:40:56 -0600
Subject: python 2.6 port questions
Message-ID: <12D4B020-77D4-433F-BBCC-3FF0CA172A9A@gmail.com>

Hello,

I am considering upgrading my macports install, and part of that would  
likely involve going from py25-* to py26-*.  However, when looking at  
available ports, I see that py25-pyx, py25-zlib, and py25-tkinter all  
exist, but their py26- equivalents are not listed.  In some cases  
(zlib, tkinter), a 3.0 port is listed.  However, a message on macports- 
dev suggests that perhaps something is fundamentally changed with zlib  
in the py26 ports [1].

For anyone who's already taken the plunge, will the py26- ports do  
everything py25- does?  Or will I be missing pyx, tkinter, and zlib?   
As someone who has submitted a change to the py25-pyx portfile  
previously, I may suggest that the pyx-specific parts of the py25-pyx  
portfile could probably be copied straight over to a py26 port, and  
encourage someone with cvs access to give it a shot (please!).

Thought I'd ask here before trying to install stuff or filing tickets...

thanks,

Brian
[1] http://lists.macosforge.org/pipermail/macports-dev/2009-January/006850.html

From ben at cogs.com  Fri Jan  2 06:43:12 2009
From: ben at cogs.com (Ben Greenfield)
Date: Fri, 2 Jan 2009 09:43:12 -0500
Subject: GnuCash packaging
In-Reply-To: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
Message-ID: <3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>


On Jan 1, 2009, at 4:57 AM, Charles Day wrote:

> Olaf,
>
> Before I joined the list, I saw an email from you in October (see http://lists.macosforge.org/pipermail/macports-users/2008-October/012020.html) 
>  about trying to package gnucash with "port mdmg". Were you ever  
> successful in working around the error? I ask because I now have the  
> same problem.
>
> $ sudo port mdmg gnucash +no_x11
> --->  Creating pkg for gnucash-2.2.8
> Error: Target org.macports.pkg returned: shell command  
> "PMResourceLocale=English /Developer/Applications/Utilities/ 
> PackageMaker.app/Contents/MacOS/PackageMaker -AppleLanguages  
> "(English)"

I just tried

slip:~ slipadmin$ sudo port -d pkg gnucash +no_x11

and got this...

DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/gnucash
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/gnome/gnucash
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 darwin is not provided by port gnucash.
DEBUG: Requested variant i386 is not provided by port gnucash.
DEBUG: Requested variant macosx is not provided by port gnucash.
DEBUG: Executing variant no_x11 provides no_x11
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/perl/p5-xml-parser
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/perl/p5-xml-parser
DEBUG: 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: Using group file /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/_resources/port1.0/group/perl5-1.0.tcl
DEBUG: adding the default universal variant
DEBUG: Requested variant darwin is not provided by port p5-xml-parser.
DEBUG: Requested variant i386 is not provided by port p5-xml-parser.
DEBUG: Requested variant no_x11 is not provided by port p5-xml-parser.
DEBUG: Requested variant macosx is not provided by port p5-xml-parser.
DEBUG: Searching for dependency: p5-xml-parser
DEBUG: Found Dependency: receipt exists for p5-xml-parser
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/glib2
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/devel/glib2
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 i386 is not provided by port glib2.
DEBUG: Requested variant no_x11 is not provided by port glib2.
DEBUG: Requested variant macosx is not provided by port glib2.
DEBUG: Executing variant darwin provides darwin
DEBUG: Executing variant darwin_9 provides darwin_9
DEBUG: Searching for dependency: glib2
DEBUG: Found Dependency: receipt exists for glib2
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/gconf
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/gnome/gconf
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 no' specified, so not adding the default  
universal variant
DEBUG: Requested variant darwin is not provided by port gconf.
DEBUG: Requested variant i386 is not provided by port gconf.
DEBUG: Requested variant no_x11 is not provided by port gconf.
DEBUG: Requested variant macosx is not provided by port gconf.
DEBUG: Searching for dependency: gconf
DEBUG: Found Dependency: receipt exists for gconf
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/guile16
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/lang/guile16
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 i386 is not provided by port guile16.
DEBUG: Requested variant no_x11 is not provided by port guile16.
DEBUG: Requested variant macosx is not provided by port guile16.
DEBUG: Executing variant darwin provides darwin
DEBUG: Searching for dependency: guile16
DEBUG: Found Dependency: receipt exists for guile16
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/slib
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/devel/slib
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: not using configure, so not adding the default universal variant
DEBUG: Requested variant darwin is not provided by port slib.
DEBUG: Requested variant i386 is not provided by port slib.
DEBUG: Requested variant no_x11 is not provided by port slib.
DEBUG: Requested variant macosx is not provided by port slib.
DEBUG: Searching for dependency: slib
DEBUG: Found Dependency: receipt exists for slib
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/slib-guile16
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/devel/slib-guile16
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: not using configure, so not adding the default universal variant
DEBUG: Requested variant darwin is not provided by port slib-guile16.
DEBUG: Requested variant i386 is not provided by port slib-guile16.
DEBUG: Requested variant no_x11 is not provided by port slib-guile16.
DEBUG: Requested variant macosx is not provided by port slib-guile16.
DEBUG: Searching for dependency: slib-guile16
DEBUG: Found Dependency: receipt exists for slib-guile16
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/popt
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/devel/popt
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 darwin is not provided by port popt.
DEBUG: Requested variant i386 is not provided by port popt.
DEBUG: Requested variant no_x11 is not provided by port popt.
DEBUG: Requested variant macosx is not provided by port popt.
DEBUG: Searching for dependency: popt
DEBUG: Found Dependency: receipt exists for popt
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/libgnomeui
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/gnome/libgnomeui
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 darwin is not provided by port libgnomeui.
DEBUG: Requested variant i386 is not provided by port libgnomeui.
DEBUG: Requested variant macosx is not provided by port libgnomeui.
DEBUG: Executing variant no_x11 provides no_x11
DEBUG: Searching for dependency: libgnomeui
DEBUG: Found Dependency: receipt exists for libgnomeui
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/libgnomeprintui
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/gnome/libgnomeprintui
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 darwin is not provided by port libgnomeprintui.
DEBUG: Requested variant i386 is not provided by port libgnomeprintui.
DEBUG: Requested variant no_x11 is not provided by port libgnomeprintui.
DEBUG: Requested variant macosx is not provided by port libgnomeprintui.
DEBUG: Searching for dependency: libgnomeprintui
DEBUG: Found Dependency: receipt exists for libgnomeprintui
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/libgtkhtml3
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/gnome/libgtkhtml3
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 darwin is not provided by port libgtkhtml3.
DEBUG: Requested variant i386 is not provided by port libgtkhtml3.
DEBUG: Requested variant no_x11 is not provided by port libgtkhtml3.
DEBUG: Requested variant macosx is not provided by port libgtkhtml3.
DEBUG: Searching for dependency: libgtkhtml3
DEBUG: Found Dependency: receipt exists for libgtkhtml3
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/libgsf
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/gnome/libgsf
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 darwin is not provided by port libgsf.
DEBUG: Requested variant i386 is not provided by port libgsf.
DEBUG: Requested variant no_x11 is not provided by port libgsf.
DEBUG: Requested variant macosx is not provided by port libgsf.
DEBUG: Searching for dependency: libgsf
DEBUG: Found Dependency: receipt exists for libgsf
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/goffice
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/gnome/goffice
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 darwin is not provided by port goffice.
DEBUG: Requested variant i386 is not provided by port goffice.
DEBUG: Requested variant no_x11 is not provided by port goffice.
DEBUG: Requested variant macosx is not provided by port goffice.
DEBUG: Searching for dependency: goffice
DEBUG: Found Dependency: receipt exists for goffice
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/aqbanking
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/devel/aqbanking
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 darwin is not provided by port aqbanking.
DEBUG: Requested variant i386 is not provided by port aqbanking.
DEBUG: Requested variant no_x11 is not provided by port aqbanking.
DEBUG: Requested variant macosx is not provided by port aqbanking.
DEBUG: Searching for dependency: aqbanking
DEBUG: Found Dependency: receipt exists for aqbanking
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/libofx
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/devel/libofx
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 darwin is not provided by port libofx.
DEBUG: Requested variant i386 is not provided by port libofx.
DEBUG: Requested variant no_x11 is not provided by port libofx.
DEBUG: Requested variant macosx is not provided by port libofx.
DEBUG: Searching for dependency: libofx
DEBUG: Found Dependency: receipt exists for libofx
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/perl/p5-finance-quote
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/perl/p5-finance-quote
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: Using group file /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/_resources/port1.0/group/perl5-1.0.tcl
DEBUG: adding the default universal variant
DEBUG: Requested variant darwin is not provided by port p5-finance- 
quote.
DEBUG: Requested variant i386 is not provided by port p5-finance-quote.
DEBUG: Requested variant no_x11 is not provided by port p5-finance- 
quote.
DEBUG: Requested variant macosx is not provided by port p5-finance- 
quote.
DEBUG: Searching for dependency: p5-finance-quote
DEBUG: Found Dependency: receipt exists for p5-finance-quote
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/libtool
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/devel/libtool
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 darwin is not provided by port libtool.
DEBUG: Requested variant i386 is not provided by port libtool.
DEBUG: Requested variant no_x11 is not provided by port libtool.
DEBUG: Requested variant macosx is not provided by port libtool.
DEBUG: Searching for dependency: libtool
DEBUG: Found Dependency: receipt exists for libtool
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/archivers/lzmautils
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/archivers/lzmautils
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 darwin is not provided by port lzmautils.
DEBUG: Requested variant i386 is not provided by port lzmautils.
DEBUG: Requested variant no_x11 is not provided by port lzmautils.
DEBUG: Requested variant macosx is not provided by port lzmautils.
DEBUG: Searching for dependency: lzmautils
DEBUG: Found Dependency: receipt exists for lzmautils
DEBUG: Skipping org.macports.main (gnucash) since this port is already  
installed
DEBUG: Skipping org.macports.fetch (gnucash) since this port is  
already installed
DEBUG: Skipping org.macports.checksum (gnucash) since this port is  
already installed
DEBUG: setting option extract.cmd to /opt/local/bin/lzma
DEBUG: Skipping org.macports.extract (gnucash) since this port is  
already installed
DEBUG: Skipping org.macports.patch (gnucash) since this port is  
already installed
DEBUG: Skipping org.macports.configure (gnucash) since this port is  
already installed
DEBUG: Skipping org.macports.build (gnucash) since this port is  
already installed
DEBUG: Skipping org.macports.destroot (gnucash) since this port is  
already installed
DEBUG: Executing org.macports.pkg (gnucash)
--->  Creating pkg for gnucash-2.2.8
DEBUG: Calling /Developer/Applications/Utilities/PackageMaker.app/ 
Contents/MacOS/PackageMaker for gnucash pkg
Warning: Unknown argument: -AppleLanguages
Warning: Unknown argument: (English)
ERROR: The specified root is invalid: /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_gnome_gnucash/work/destroot
Error: Target org.macports.pkg returned: shell command  
"PMResourceLocale=English /Developer/Applications/Utilities/ 
PackageMaker.app/Contents/MacOS/PackageMaker -AppleLanguages  
"(English)" --root /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_gnome_gnucash/work/destroot --out /opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_gnome_gnucash/work/gnucash-2.2.8.pkg  -- 
resources /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_gnome_gnucash/work/pkg_resources --title  
"gnucash-2.2.8" --info /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_gnome_gnucash/work/Info.plist --target  
10.3 --domain system --id org.macports.gnucash" returned error 1
Command output: Warning: Unknown argument: -AppleLanguages
Warning: Unknown argument: (English)
ERROR: The specified root is invalid: /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_gnome_gnucash/work/destroot
Warning: the following items did not execute (for gnucash):  
org.macports.pkg
Error: Status 1 encountered during processing.

It is the same error I checked the the Apple docs on Packagmaker.app  
and they describe how Packmaker has been recreated for leopard. I  
suspect that the problem is that Packmaker no longer has an - 
AppleLanguages option. I will dig around and see if I can figure out  
how macports uses Packagmaker.app.

Ben


> --root /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_gnome_gnucash/work/destroot --out /opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_gnome_gnucash/work/gnucash-2.2.8.pkg  -- 
> resources /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_gnome_gnucash/work/pkg_resources --title  
> "gnucash-2.2.8" --info /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_gnome_gnucash/work/Info.plist --target  
> 10.3 --domain system --id org.macports.gnucash" returned error 1
> Command output: Warning: Unknown argument: -AppleLanguages
> Warning: Unknown argument: (English)
> ERROR: The specified root is invalid: /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_gnome_gnucash/work/destroot
>
> Error: Status 1 encountered during processing



>
>
> Cheers,
> Charles
> _______________________________________________
> 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/20090102/a2d93a99/attachment.html>

From blb at macports.org  Fri Jan  2 15:08:14 2009
From: blb at macports.org (Bryan Blackburn)
Date: Fri, 2 Jan 2009 16:08:14 -0700
Subject: python 2.6 port questions
In-Reply-To: <12D4B020-77D4-433F-BBCC-3FF0CA172A9A@gmail.com>
References: <12D4B020-77D4-433F-BBCC-3FF0CA172A9A@gmail.com>
Message-ID: <20090102230814.GE1008@ninagal.withay.com>

On Fri, Jan 02, 2009 at 04:40:56PM -0600, Brian Barnes said:
> Hello,
>
> I am considering upgrading my macports install, and part of that would  
> likely involve going from py25-* to py26-*.  However, when looking at  
> available ports, I see that py25-pyx, py25-zlib, and py25-tkinter all  
> exist, but their py26- equivalents are not listed.  In some cases (zlib, 
> tkinter), a 3.0 port is listed.  However, a message on macports-dev 
> suggests that perhaps something is fundamentally changed with zlib in the 
> py26 ports [1].
>
> For anyone who's already taken the plunge, will the py26- ports do  
> everything py25- does?  Or will I be missing pyx, tkinter, and zlib?  As 
> someone who has submitted a change to the py25-pyx portfile previously, I 
> may suggest that the pyx-specific parts of the py25-pyx portfile could 
> probably be copied straight over to a py26 port, and encourage someone 
> with cvs access to give it a shot (please!).

python26 builds with itself several modules that are separate ports for
other versions of python: py*-bsddb, py*-bz2, py*-curses, py*-gdbm,
py*-hashlib, py*-readline, py*-socket-ssl, py*-sqlite3, py*-tkinter, and
py*-zlib.

So in your list, the only one that's needed would be py26-pyx, I'd try it
but don't currently have texlive installed.

Bryan


>
> Thought I'd ask here before trying to install stuff or filing tickets...
>
> thanks,
>
> Brian
> [1] http://lists.macosforge.org/pipermail/macports-dev/2009-January/006850.html

From ryandesign at macports.org  Fri Jan  2 16:39:32 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 2 Jan 2009 18:39:32 -0600
Subject: tex wanting to install even though it's not outdated
In-Reply-To: <loom.20090102T033847-831@post.gmane.org>
References: <loom.20090102T033847-831@post.gmane.org>
Message-ID: <03B9BA12-8816-48AC-BDA4-AEF9421B75A6@macports.org>


On Jan 1, 2009, at 21:41, John Owens wrote:

> classico 8914$ port outdated
> No installed ports are outdated.
> classico 8914$ sudo port upgrade installed
> --->  Extracting texlive_texmf-full
>
> So I'm using MacTeX (in /usr/texbin) for my TeX distribution
> now, and have set binpath in macports.conf accordingly. This
> works fine. How can I keep "port upgrade installed" from
> wanting to install a macports texlive? (Perhaps one of my
> ports depends on it; how could I figure that out?)

I believe the fix for that problem will be in MacPorts 1.8.0:

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




From jmr at macports.org  Fri Jan  2 19:02:23 2009
From: jmr at macports.org (Joshua Root)
Date: Sat, 03 Jan 2009 14:02:23 +1100
Subject: GnuCash packaging
In-Reply-To: <3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
Message-ID: <495ED53F.2020303@macports.org>

Ben Greenfield wrote:
> 
> On Jan 1, 2009, at 4:57 AM, Charles Day wrote:
> 
>> Olaf,
>>
>> Before I joined the list, I saw an email from you in October
>> (see http://lists.macosforge.org/pipermail/macports-users/2008-October/012020.html) about
>> trying to package gnucash with "port mdmg". Were you ever successful
>> in working around the error? I ask because I now have the same problem.
>>
>> $ sudo port mdmg gnucash +no_x11
>> --->  Creating pkg for gnucash-2.2.8
>> Error: Target org.macports.pkg returned: shell command
>> "PMResourceLocale=English
>> /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker
>> -AppleLanguages "(English)" 
> 
> I just tried
> 
> slip:~ slipadmin$ sudo port -d pkg gnucash +no_x11
> 
> and got this...
<snip>
> DEBUG: Found Dependency: receipt exists for lzmautils
> DEBUG: Skipping org.macports.main (gnucash) since this port is already
> installed
> DEBUG: Skipping org.macports.fetch (gnucash) since this port is already
> installed
> DEBUG: Skipping org.macports.checksum (gnucash) since this port is
> already installed
> DEBUG: setting option extract.cmd to /opt/local/bin/lzma
> DEBUG: Skipping org.macports.extract (gnucash) since this port is
> already installed
> DEBUG: Skipping org.macports.patch (gnucash) since this port is already
> installed
> DEBUG: Skipping org.macports.configure (gnucash) since this port is
> already installed
> DEBUG: Skipping org.macports.build (gnucash) since this port is already
> installed
> DEBUG: Skipping org.macports.destroot (gnucash) since this port is
> already installed
> DEBUG: Executing org.macports.pkg (gnucash)
> --->  Creating pkg for gnucash-2.2.8
> DEBUG: Calling
> /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker
> for gnucash pkg
> Warning: Unknown argument: -AppleLanguages
> Warning: Unknown argument: (English)
> ERROR: The specified root is invalid:
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gnucash/work/destroot

> It is the same error I checked the the Apple docs on Packagmaker.app and
> they describe how Packmaker has been recreated for leopard. I suspect
> that the problem is that Packmaker no longer has an -AppleLanguages
> option. I will dig around and see if I can figure out how macports uses
> Packagmaker.app.

The -AppleLanguages warning is harmless. The real problem is this bug:
<http://trac.macports.org/ticket/10881>

- Josh

From frstan at bellsouth.net  Fri Jan  2 22:09:54 2009
From: frstan at bellsouth.net (William Davis)
Date: Sat, 3 Jan 2009 01:09:54 -0500
Subject: python_select fetch fails
Message-ID: <5FC8CBB5-C9FC-49B2-844E-EDFBA83696BB@bellsouth.net>

python_select fetch fails

--->  Attempting to fetch select-0.2.1.tar.gz from http://trd.no.distfiles.macports.org/python_select
   % Total    % Received % Xferd  Average Speed   Time    Time      
Time  Current
                                  Dload  Upload   Total   Spent     
Left  Speed
   0     0    0     0    0     0      0      0 --:--:-- --:--:--  
--:--:--     0
DEBUG: Fetching failed:: HTTP response code said error

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.6 Darwin 9.5.0
XQuartz 2.3.2 (xorg-server 1.4.2-apple31)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From cedayiv at gmail.com  Fri Jan  2 22:24:05 2009
From: cedayiv at gmail.com (Charles Day)
Date: Fri, 2 Jan 2009 22:24:05 -0800
Subject: GnuCash packaging
In-Reply-To: <495ED53F.2020303@macports.org>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
	<495ED53F.2020303@macports.org>
Message-ID: <1d6843d80901022224k3a831e91g8d95a8f6ba2861dc@mail.gmail.com>

On Fri, Jan 2, 2009 at 7:02 PM, Joshua Root <jmr at macports.org> wrote:

> Ben Greenfield wrote:
> >
> > On Jan 1, 2009, at 4:57 AM, Charles Day wrote:
> >
> >> Olaf,
> >>
> >> Before I joined the list, I saw an email from you in October
> >> (see
> http://lists.macosforge.org/pipermail/macports-users/2008-October/012020.html)
> about
> >> trying to package gnucash with "port mdmg". Were you ever successful
> >> in working around the error? I ask because I now have the same problem.
> >>
> >> $ sudo port mdmg gnucash +no_x11
> >> --->  Creating pkg for gnucash-2.2.8
> >> Error: Target org.macports.pkg returned: shell command
> >> "PMResourceLocale=English
> >>
> /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker
> >> -AppleLanguages "(English)"
> >
> > I just tried
> >
> > slip:~ slipadmin$ sudo port -d pkg gnucash +no_x11
> >
> > and got this...
> <snip>
> > DEBUG: Found Dependency: receipt exists for lzmautils
> > DEBUG: Skipping org.macports.main (gnucash) since this port is already
> > installed
> > DEBUG: Skipping org.macports.fetch (gnucash) since this port is already
> > installed
> > DEBUG: Skipping org.macports.checksum (gnucash) since this port is
> > already installed
> > DEBUG: setting option extract.cmd to /opt/local/bin/lzma
> > DEBUG: Skipping org.macports.extract (gnucash) since this port is
> > already installed
> > DEBUG: Skipping org.macports.patch (gnucash) since this port is already
> > installed
> > DEBUG: Skipping org.macports.configure (gnucash) since this port is
> > already installed
> > DEBUG: Skipping org.macports.build (gnucash) since this port is already
> > installed
> > DEBUG: Skipping org.macports.destroot (gnucash) since this port is
> > already installed
> > DEBUG: Executing org.macports.pkg (gnucash)
> > --->  Creating pkg for gnucash-2.2.8
> > DEBUG: Calling
> >
> /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker
> > for gnucash pkg
> > Warning: Unknown argument: -AppleLanguages
> > Warning: Unknown argument: (English)
> > ERROR: The specified root is invalid:
> >
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gnucash/work/destroot
>
> > It is the same error I checked the the Apple docs on Packagmaker.app and
> > they describe how Packmaker has been recreated for leopard. I suspect
> > that the problem is that Packmaker no longer has an -AppleLanguages
> > option. I will dig around and see if I can figure out how macports uses
> > Packagmaker.app.
>
> The -AppleLanguages warning is harmless. The real problem is this bug:
> <http://trac.macports.org/ticket/10881>
>

Well I tried the following workaround for ticket 10881, but macports started
trying to include the wrong dependencies. For example, it tried to include
dependencies based on X11 when I specified gnucash +no_x11 (see
gnome-desktop at the end as an example).

In addition, it seems that some dependencies are required to be built into
their own destroots in advance (see the error message for aqbanking below).

So I'm not sure how I should try again to make it work.

Here's what I did:

(I'm not sure this first step is necessary, but I did it anyway.)

$ sudo port uninstall gnucash
Password:
--->  Deactivating gnucash @2.2.8_0+no_x11
--->  Uninstalling gnucash @2.2.8_0+no_x11

$ sudo port -f destroot gnucash +no_x11
--->  Fetching gnucash
--->  Verifying checksum(s) for gnucash
--->  Extracting gnucash
--->  Applying patches to gnucash
--->  Configuring gnucash
--->  Building gnucash
--->  Staging gnucash into destroot

$ sudo port mdmg gnucash +no_x11
sudo port mdmg gnucash +no_x11
Password:
--->  Creating pkg for gnucash-2.2.8
--->  Fetching xorg-xproto
--->  Attempting to fetch xproto-7.0.14.tar.bz2 from
http://distfiles.macports.org/xorg-xproto
--->  Verifying checksum(s) for xorg-xproto
--->  Extracting xorg-xproto
--->  Configuring xorg-xproto
--->  Building xorg-xproto
--->  Staging xorg-xproto into destroot
--->  Installing xorg-xproto @7.0.14_1
--->  Activating xorg-xproto @7.0.14_1
--->  Cleaning xorg-xproto
--->  Fetching Xft2
--->  Attempting to fetch libXft-2.1.13.tar.bz2 from
http://distfiles.macports.org/Xft2
--->  Verifying checksum(s) for Xft2
--->  Extracting Xft2
--->  Configuring Xft2
--->  Building Xft2
--->  Staging Xft2 into destroot
--->  Creating pkg for Xft2-2.1.13
--->  Creating pkg for aqbanking-3.7.2
Error: Target org.macports.pkg returned: shell command
"PMResourceLocale=English
/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker
-AppleLanguages "(English)" --root
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_aqbanking/work/destroot
--out
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gnucash/work/gnucash-2.2.8.mpkg/Contents/Packages/aqbanking-3.7.2.pkg
 --resources
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_aqbanking/work/pkg_resources
--title "aqbanking-3.7.2" --info
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_aqbanking/work/Info.plist
--target 10.3 --domain system --id org.macports.aqbanking" returned error 1
Command output: Warning: Unknown argument: -AppleLanguages
Warning: Unknown argument: (English)
ERROR: The specified root is invalid:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_aqbanking/work/destroot

--->  Fetching atk
--->  Verifying checksum(s) for atk
--->  Extracting atk
--->  Configuring atk
--->  Building atk
--->  Staging atk into destroot
--->  Creating pkg for atk-1.24.0
--->  Creating pkg for audiofile-0.2.6
Error: Target org.macports.pkg returned: shell command
"PMResourceLocale=English
/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker
-AppleLanguages "(English)" --root
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_audio_audiofile/work/destroot
--out
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gnucash/work/gnucash-2.2.8.mpkg/Contents/Packages/audiofile-0.2.6.pkg
 --resources
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_audio_audiofile/work/pkg_resources
--title "audiofile-0.2.6" --info
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_audio_audiofile/work/Info.plist
--target 10.3 --domain system --id org.macports.audiofile" returned error 1
Command output: Warning: Unknown argument: -AppleLanguages
Warning: Unknown argument: (English)
ERROR: The specified root is invalid:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_audio_audiofile/work/destroot

--->  Fetching bzip2
--->  Verifying checksum(s) for bzip2
--->  Extracting bzip2
--->  Applying patches to bzip2
--->  Configuring bzip2
--->  Building bzip2
--->  Staging bzip2 into destroot
--->  Creating pkg for bzip2-1.0.5
--->  Fetching cairo
--->  Attempting to fetch cairo-1.8.6.tar.gz from
http://distfiles.macports.org/cairo
--->  Verifying checksum(s) for cairo
--->  Extracting cairo
--->  Applying patches to cairo
--->  Configuring cairo
--->  Building cairo
--->  Staging cairo into destroot
--->  Creating pkg for cairo-1.8.6
--->  Fetching dbus-glib
--->  Attempting to fetch dbus-glib-0.78.tar.gz from
http://distfiles.macports.org/dbus-glib
--->  Verifying checksum(s) for dbus-glib
--->  Extracting dbus-glib
--->  Configuring dbus-glib
--->  Building dbus-glib
--->  Staging dbus-glib into destroot
--->  Creating pkg for dbus-glib-0.78
--->  Fetching dbus
--->  Attempting to fetch dbus-1.2.10.tar.gz from
http://distfiles.macports.org/dbus
--->  Verifying checksum(s) for dbus
--->  Extracting dbus
--->  Applying patches to dbus
--->  Configuring dbus
--->  Building dbus
--->  Staging dbus into destroot
--->  Creating launchd control script
###########################################################
# A startup item has been generated that will aid in
# starting dbus with launchd. It is disabled
# by default. Execute the following command to start it,
# and to cause it to launch at startup:
#
# sudo launchctl load -w /Library/LaunchDaemons/org.macports.dbus.plist
###########################################################
--->  Creating pkg for dbus-1.2.10
--->  Fetching desktop-file-utils
--->  Verifying checksum(s) for desktop-file-utils
--->  Extracting desktop-file-utils
--->  Configuring desktop-file-utils
--->  Building desktop-file-utils
--->  Staging desktop-file-utils into destroot
--->  Creating pkg for desktop-file-utils-0.15
--->  Fetching xmlcatmgr
--->  Verifying checksum(s) for xmlcatmgr
--->  Extracting xmlcatmgr
--->  Configuring xmlcatmgr
--->  Building xmlcatmgr
--->  Staging xmlcatmgr into destroot
--->  Installing xmlcatmgr @2.2_1
--->  Activating xmlcatmgr @2.2_1
--->  Cleaning xmlcatmgr
--->  Fetching docbook-xsl
--->  Verifying checksum(s) for docbook-xsl
--->  Extracting docbook-xsl
--->  Configuring docbook-xsl
--->  Building docbook-xsl
--->  Staging docbook-xsl into destroot
--->  Installing docbook-xsl @1.74.0_0
--->  Activating docbook-xsl @1.74.0_0
######################################################################
# As MacPorts does not currently have a post-deactivate hook,
# you will need to ensure that you manually remove the catalog
# entry for this port when you uninstall it.  To do so, run
# "xmlcatmgr remove nextCatalog
/opt/local/share/xsl/docbook-xsl/catalog.xml".
######################################################################
--->  Cleaning docbook-xsl
--->  Fetching gnome-doc-utils
--->  Verifying checksum(s) for gnome-doc-utils
--->  Extracting gnome-doc-utils
--->  Configuring gnome-doc-utils
--->  Building gnome-doc-utils
--->  Staging gnome-doc-utils into destroot
--->  Installing gnome-doc-utils @0.14.1_0
--->  Activating gnome-doc-utils @0.14.1_0
--->  Cleaning gnome-doc-utils
--->  Fetching gtk-engines2
--->  Verifying checksum(s) for gtk-engines2
--->  Extracting gtk-engines2
--->  Configuring gtk-engines2
--->  Building gtk-engines2
--->  Staging gtk-engines2 into destroot
--->  Installing gtk-engines2 @2.16.1_0
--->  Activating gtk-engines2 @2.16.1_0
--->  Cleaning gtk-engines2
--->  Fetching gnome-themes
--->  Verifying checksum(s) for gnome-themes
--->  Extracting gnome-themes
--->  Configuring gnome-themes
--->  Building gnome-themes
--->  Staging gnome-themes into destroot
--->  Installing gnome-themes @2.24.1_1
--->  Activating gnome-themes @2.24.1_1
--->  Cleaning gnome-themes
--->  Fetching fftw-3
--->  Attempting to fetch fftw-3.2.tar.gz from
http://distfiles.macports.org/fftw-3
--->  Verifying checksum(s) for fftw-3
--->  Extracting fftw-3
--->  Configuring fftw-3
--->  Building fftw-3
--->  Staging fftw-3 into destroot
--->  Installing fftw-3 @3.2_1
--->  Activating fftw-3 @3.2_1
--->  Cleaning fftw-3
--->  Fetching py25-zlib
--->  Attempting to fetch Python-2.5.4.tar.bz2 from
http://distfiles.macports.org/python25
--->  Verifying checksum(s) for py25-zlib
--->  Extracting py25-zlib
--->  Configuring py25-zlib
--->  Building py25-zlib
--->  Staging py25-zlib into destroot
--->  Installing py25-zlib @2.5.4_0
--->  Activating py25-zlib @2.5.4_0
--->  Cleaning py25-zlib
--->  Fetching py25-setuptools
--->  Attempting to fetch setuptools-0.6c9.tar.gz from
http://distfiles.macports.org/python
--->  Verifying checksum(s) for py25-setuptools
--->  Extracting py25-setuptools
--->  Configuring py25-setuptools
--->  Building py25-setuptools
--->  Staging py25-setuptools into destroot
--->  Installing py25-setuptools @0.6c9_0
--->  Activating py25-setuptools @0.6c9_0
--->  Cleaning py25-setuptools
--->  Fetching py25-nose
--->  Verifying checksum(s) for py25-nose
--->  Extracting py25-nose
--->  Configuring py25-nose
--->  Building py25-nose
--->  Staging py25-nose into destroot
--->  Installing py25-nose @0.10.4_0
--->  Activating py25-nose @0.10.4_0
--->  Cleaning py25-nose
--->  Fetching py25-numpy
--->  Verifying checksum(s) for py25-numpy
--->  Extracting py25-numpy
--->  Applying patches to py25-numpy
--->  Configuring py25-numpy
--->  Building py25-numpy
--->  Staging py25-numpy into destroot
--->  Installing py25-numpy @1.2.1_0
--->  Activating py25-numpy @1.2.1_0
--->  Cleaning py25-numpy
--->  Fetching py25-cairo
--->  Attempting to fetch pycairo-1.8.0.tar.gz from
http://distfiles.macports.org/py25-cairo
--->  Verifying checksum(s) for py25-cairo
--->  Extracting py25-cairo
--->  Configuring py25-cairo
--->  Building py25-cairo
--->  Staging py25-cairo into destroot
--->  Installing py25-cairo @1.8.0_0+darwin_9
--->  Activating py25-cairo @1.8.0_0+darwin_9
--->  Cleaning py25-cairo
--->  Fetching py25-gobject
--->  Verifying checksum(s) for py25-gobject
--->  Extracting py25-gobject
--->  Configuring py25-gobject
--->  Building py25-gobject
--->  Staging py25-gobject into destroot
--->  Installing py25-gobject @2.14.2_0+darwin_9
--->  Activating py25-gobject @2.14.2_0+darwin_9
--->  Cleaning py25-gobject
--->  Fetching py25-gtk
--->  Verifying checksum(s) for py25-gtk
--->  Extracting py25-gtk
--->  Configuring py25-gtk
--->  Building py25-gtk
--->  Staging py25-gtk into destroot
--->  Installing py25-gtk @2.12.1_0+darwin_9
--->  Activating py25-gtk @2.12.1_0+darwin_9
--->  Cleaning py25-gtk
--->  Fetching py25-orbit
--->  Attempting to fetch pyorbit-2.24.0.tar.bz2 from
http://mirror.aarnet.edu.au/pub/GNOME/sources/pyorbit/2.24/
--->  Verifying checksum(s) for py25-orbit
--->  Extracting py25-orbit
--->  Configuring py25-orbit
--->  Building py25-orbit
--->  Staging py25-orbit into destroot
--->  Installing py25-orbit @2.24.0_0+darwin_9
--->  Activating py25-orbit @2.24.0_0+darwin_9
--->  Cleaning py25-orbit
--->  Fetching py25-gnome
--->  Attempting to fetch gnome-python-2.22.3.tar.bz2 from
http://mirror.internode.on.net/pub/gnome/sources/gnome-python/2.22/
--->  Verifying checksum(s) for py25-gnome
--->  Extracting py25-gnome
--->  Configuring py25-gnome
--->  Building py25-gnome
--->  Staging py25-gnome into destroot
--->  Installing py25-gnome @2.22.3_0+darwin_9
--->  Activating py25-gnome @2.22.3_0+darwin_9
--->  Cleaning py25-gnome
--->  Fetching startup-notification
--->  Verifying checksum(s) for startup-notification
--->  Extracting startup-notification
--->  Configuring startup-notification
--->  Building startup-notification
--->  Staging startup-notification into destroot
--->  Installing startup-notification @0.9_0
--->  Activating startup-notification @0.9_0
--->  Cleaning startup-notification
--->  Fetching gnome-desktop
--->  Attempting to fetch gnome-desktop-2.24.2.tar.bz2 from
http://mirror.internode.on.net/pub/gnome/sources/gnome-desktop/2.24/
--->  Verifying checksum(s) for gnome-desktop
--->  Extracting gnome-desktop
--->  Applying patches to gnome-desktop
--->  Configuring gnome-desktop
Error: Target org.macports.configure returned: +x11 variant selected, but
gtk2+quartz is installed
Error: The following dependencies failed to build: gnome-desktop gnome-menus
librsvg libcroco



>
> - Josh
>

-Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090102/ce27cb33/attachment.html>

From raimue at macports.org  Fri Jan  2 22:25:34 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Sat, 03 Jan 2009 07:25:34 +0100
Subject: python_select fetch fails
In-Reply-To: <5FC8CBB5-C9FC-49B2-844E-EDFBA83696BB@bellsouth.net>
References: <5FC8CBB5-C9FC-49B2-844E-EDFBA83696BB@bellsouth.net>
Message-ID: <495F04DE.4040201@macports.org>

William Davis wrote:
> python_select fetch fails
> 
> --->  Attempting to fetch select-0.2.1.tar.gz from http://trd.no.distfiles.macports.org/python_select
>    % Total    % Received % Xferd  Average Speed   Time    Time      
> Time  Current
>                                   Dload  Upload   Total   Spent     
> Left  Speed
>    0     0    0     0    0     0      0      0 --:--:-- --:--:--  
> --:--:--     0
> DEBUG: Fetching failed:: HTTP response code said error

Sorry, I forgot to svn add the new tarball for 0.2.1.
Should be fixed now, r44806.

It will still take some time until the file is also available from the
mirrors, but it will be fetched from the original location in the
repository.

Rainer

From afb at macports.org  Sat Jan  3 00:39:05 2009
From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=)
Date: Sat, 3 Jan 2009 09:39:05 +0100
Subject: GnuCash packaging
In-Reply-To: <1d6843d80901022224k3a831e91g8d95a8f6ba2861dc@mail.gmail.com>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
	<495ED53F.2020303@macports.org>
	<1d6843d80901022224k3a831e91g8d95a8f6ba2861dc@mail.gmail.com>
Message-ID: <55476680-A7AE-4647-B851-97DEF60F5C21@macports.org>

Charles Day wrote:

> Well I tried the following workaround for ticket 10881, but  
> macports started trying to include the wrong dependencies. For  
> example, it tried to include dependencies based on X11 when I  
> specified gnucash +no_x11 (see gnome-desktop at the end as an  
> example).
>
> In addition, it seems that some dependencies are required to be  
> built into their own destroots in advance (see the error message  
> for aqbanking below).
>
> So I'm not sure how I should try again to make it work.

Disable autoclean in macports.conf, uninstall and clean everything,  
and start over ?

The "force destroot" workaround requires that you do it for every  
single port,
including all dependencies and making sure all needed variants are  
included...

"Given that this has been around for 2 years, is this considered a  
bug or a feature?"

--anders


From olaf at foellinger.de  Sat Jan  3 00:39:12 2009
From: olaf at foellinger.de (Olaf Foellinger)
Date: Sat, 3 Jan 2009 09:39:12 +0100
Subject: GnuCash packaging
In-Reply-To: <3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
Message-ID: <20090103083912.GA28385@foellinger.de>

Hi,

* Ben Greenfield <ben at cogs.com> [03.01.09 09:30]wrote:

>    On Jan 1, 2009, at 4:57 AM, Charles Day wrote:
> 
>      Olaf,
> 
>    Before I joined the list, I saw an email from you in October
>    (see [1]http://lists.macosforge.org/pipermail/macports-users/2008-Octob
>    er/012020.html) about trying to package gnucash with "port mdmg". Were
>    you ever successful in working around the error? I ask because I now
>    have the same problem.
>    $ sudo port mdmg gnucash +no_x11
>    --->  Creating pkg for gnucash-2.2.8
>    Error: Target org.macports.pkg returned: shell command
>    "PMResourceLocale=English
>    /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/Packa
>    geMaker -AppleLanguages "(English)"
> 
>    I just tried
>    slip:~ slipadmin$ sudo port -d pkg gnucash +no_x11
>    and got this...
>    DEBUG: Found port in
>    [2]file:///opt/local/var/macports/sources/rsync.macports.org/release/po
>    rts/gnome/gnucash
>    DEBUG: Changing to port directory:
...
>    ports.org_release_ports_gnome_gnucash/work/destroot
>    Warning: the following items did not execute (for gnucash):
>    org.macports.pkg
>    Error: Status 1 encountered during processing.
>    It is the same error I checked the the Apple docs on Packagmaker.app
>    and they describe how Packmaker has been recreated for leopard. I
>    suspect that the problem is that Packmaker no longer has an
>    -AppleLanguages option. I will dig around and see if I can figure out
>    how macports uses Packagmaker.app.
>    Ben

here 

$ sudo port mdmg gnucash

<lots of log>
...
The package could not be created because of the following errors:
Root directory
"/opt/quartz/var/macports/build/_opt_quartz_var_macports_sources_rsync.macports.org_release_ports_archivers_zlib/work/destroot"
is not valid.

--->  Creating disk image for gnucash-2.2.8

The image has been created, but I'm not sure about the content because
lots of packages showed the error above. Maybe for package creation one
needs the archiving mode enabled.

Btw, I'm o 1.4.11 if this matters.

Gru? Olaf

From afb at macports.org  Sat Jan  3 00:54:39 2009
From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=)
Date: Sat, 3 Jan 2009 09:54:39 +0100
Subject: GnuCash packaging
In-Reply-To: <495ED53F.2020303@macports.org>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
	<495ED53F.2020303@macports.org>
Message-ID: <F6023E98-B514-44BB-90EE-FF39C21914DC@macports.org>

Joshua Root wrote:

>> DEBUG: Calling
>> /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/ 
>> PackageMaker
>> for gnucash pkg
>> Warning: Unknown argument: -AppleLanguages
>> Warning: Unknown argument: (English)
>>
>> It is the same error I checked the the Apple docs on  
>> Packagmaker.app and
>> they describe how Packmaker has been recreated for leopard. I suspect
>> that the problem is that Packmaker no longer has an -AppleLanguages
>> option. I will dig around and see if I can figure out how macports  
>> uses
>> Packagmaker.app.
>
> The -AppleLanguages warning is harmless.

It's a workaround for Leopard's PackageMaker - which creates package
description in the local language, rather than in English, by default.
Metapackages are totally broken, so can't use PackageMaker for those.
Then again "Uninstall" is still broken too, so maybe that's expected ?

--anders


From zabouti at gmail.com  Sat Jan  3 07:51:53 2009
From: zabouti at gmail.com (George Entenman)
Date: Sat, 3 Jan 2009 10:51:53 -0500
Subject: dbd-mysql - where is it?
Message-ID: <87c6dde70901030751q76374bbbs99fa3692ee688f3b@mail.gmail.com>

On this page (
http://www.macports.org/ports.php?by=category&substr=databases&page=3&pagesize=50)
there is a message concerning rb-dbd-mysql:

    rb-dbd-mysql 0.0.23
        Ruby DBI driver for Mysql. OBSOLETE: please use dbd_mysql variant of
rb-dbi
        Maintained by: robertoatfreebsd.org
        Categories: databases
        Platforms: darwin

How do I find it?

And, has it been ported to work with mysql5-devel?

(I'm trying to get ruby-dbi working with MySQL 5.1.30 and have failed with
my normal OSX 10.5 version of ruby.  Any help would be appreciated.)

Thanks
George Entenman
Chapel Hill, NC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090103/7c462015/attachment.html>

From takashi at takashiyoshida.org  Sat Jan  3 08:10:55 2009
From: takashi at takashiyoshida.org (Takashi Yoshida)
Date: Sun, 4 Jan 2009 00:10:55 +0800
Subject: dbd-mysql - where is it?
In-Reply-To: <87c6dde70901030751q76374bbbs99fa3692ee688f3b@mail.gmail.com>
References: <87c6dde70901030751q76374bbbs99fa3692ee688f3b@mail.gmail.com>
Message-ID: <B36A0F43-865A-4A45-B2AF-253300E7D3AA@takashiyoshida.org>

Did you try running 'port search rb-dbi'?

$ port search rb-dbi
rb-dbd-mysql @0.0.23 (databases)
     Ruby DBI driver for Mysql. OBSOLETE: please use dbd_mysql variant  
of rb-dbi

rb-dbd-pg @0.0.23 (databases)
     Ruby DBI driver for PostgreSQL. OBSOLETE: please use dbd_pg  
variant of
     rb-dbi

rb-dbi @0.1.1 (ruby, databases)
     The Ruby port of DBI

Found 3 ports.

You can get more information about rb-dbi by running 'port info rb-dbi'.

$ port info rb-dbi
rb-dbi @0.1.1, Revision 1 (ruby, databases)
Variants:    dbd_mysql, dbd_odbc, dbd_pg, dbd_proxy, universal

A database independent interface for accessing databases, similar to  
Perl's DBI.
Database drivers for it are now available as variants of this package.
Homepage:    http://rubyforge.org/projects/ruby-dbi

Library Dependencies: ruby
Platforms:            darwin
Maintainers:          nomaintainer at macports.org

If you need to install rb-dbi that works with MySQL, you should be  
able to install it by running:
'sudo port install rb-dbi +dbd_mysql'.



--
Takashi Yoshida

email: takashi at takashiyoshida.org
web: http://takashiyoshida.org

On Jan 3, 2009, at 11:51 PM, George Entenman wrote:

> On this page (http://www.macports.org/ports.php?by=category&substr=databases&page=3&pagesize=50 
> ) there is a message concerning rb-dbd-mysql:
>
>     rb-dbd-mysql 0.0.23
>         Ruby DBI driver for Mysql. OBSOLETE: please use dbd_mysql  
> variant of rb-dbi
>         Maintained by: robertoatfreebsd.org
>         Categories: databases
>         Platforms: darwin
>
> How do I find it?
>
> And, has it been ported to work with mysql5-devel?
>
> (I'm trying to get ruby-dbi working with MySQL 5.1.30 and have  
> failed with my normal OSX 10.5 version of ruby.  Any help would be  
> appreciated.)
>
> Thanks
> George Entenman
> Chapel Hill, NC
>
> _______________________________________________
> 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/20090104/479c1677/attachment.html>

From ben at cogs.com  Sat Jan  3 11:36:12 2009
From: ben at cogs.com (Ben Greenfield)
Date: Sat, 3 Jan 2009 14:36:12 -0500
Subject: Fwd: GnuCash packaging
References: <5F9A2186-96EA-4FC1-A3C8-E95801EC1B0E@cogs.com>
Message-ID: <C3D2C8AD-5D5C-4FBC-B5A1-8007359B4FFF@cogs.com>



Begin forwarded message:

> From: Ben Greenfield <ben at cogs.com>
> Date: January 3, 2009 9:24:57 AM EST
> To: Anders F Bj?rklund <afb at macports.org>
> Subject: Re: GnuCash packaging
>
>
> On Jan 3, 2009, at 3:39 AM, Anders F Bj?rklund wrote:
>
>> Charles Day wrote:
>>
>>> Well I tried the following workaround for ticket 10881, but  
>>> macports started trying to include the wrong dependencies. For  
>>> example, it tried to include dependencies based on X11 when I  
>>> specified gnucash +no_x11 (see gnome-desktop at the end as an  
>>> example).
>>>
>>> In addition, it seems that some dependencies are required to be  
>>> built into their own destroots in advance (see the error message  
>>> for aqbanking below).
>>>
>>> So I'm not sure how I should try again to make it work.
>>
>> Disable autoclean in macports.conf, uninstall and clean everything,  
>> and start over ?
>>
>> The "force destroot" workaround requires that you do it for every  
>> single port,
>> including all dependencies and making sure all needed variants are  
>> included...
>>
>> "Given that this has been around for 2 years, is this considered a  
>> bug or a feature?"
>
> I think it is a requirement and should be documented as such.
>
> It seems pretty straight forward if you want to use mdmg or pkg on  
> needs to build with autoclean disabled in macports.conf
>
> The next question is what else does it effect. Without doing any  
> research these are my guesses.
>
> dmg, dpkg, mpkg, ...
>
> Still Digging,
>
> Ben
>
>
>
>
>>
>>
>> --anders
>>
>> _______________________________________________
>> 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/20090103/02b2027f/attachment.html>

From lars.sonchocky-helldorf at hamburg.de  Sat Jan  3 11:43:12 2009
From: lars.sonchocky-helldorf at hamburg.de (Lars Sonchocky-Helldorf)
Date: Sat, 3 Jan 2009 20:43:12 +0100
Subject: Unable to upgrade tcl port on Tiger
Message-ID: <323ADF19-08B4-45F2-AACA-3900B276520D@hamburg.de>

Hi,

I am experiencing problems when trying to update the tcl port:


Lars-Sonchocky-Helldorfs-Computer:~ lars$ sudo port clean --all tcl
Password:
--->  Cleaning tcl
Warning: Distfiles directory '/opt/local/var/macports/distfiles/ 
tcltk' may contain distfiles needed for other ports, use the -f flag  
to force removal
Lars-Sonchocky-Helldorfs-Computer:~ lars$ sudo port upgrade outdated
--->  Fetching tcl
--->  Attempting to fetch tcl8.5.5-src.tar.gz from http:// 
mesh.dl.sourceforge.net/tcl
--->  Verifying checksum(s) for tcl
--->  Extracting tcl
--->  Configuring tcl
Error: Target org.macports.configure returned: can't read  
"configure.cppflags": no such variable
Error: Unable to upgrade port: 1
Lars-Sonchocky-Helldorfs-Computer:~ lars$


I recently installed Xcode 2.5 and did a sudo port -vf selfupdate  
just before to force a recompile (now I am at 1.700)

my Mac OS X version is 10.4.11 (Darwin 8.11.0)


what can I do about it?


Thanks,

	Lars

From blb at macports.org  Sat Jan  3 13:35:17 2009
From: blb at macports.org (Bryan Blackburn)
Date: Sat, 3 Jan 2009 14:35:17 -0700
Subject: Unable to upgrade tcl port on Tiger
In-Reply-To: <323ADF19-08B4-45F2-AACA-3900B276520D@hamburg.de>
References: <323ADF19-08B4-45F2-AACA-3900B276520D@hamburg.de>
Message-ID: <20090103213517.GE755@ninagal.withay.com>

On Sat, Jan 03, 2009 at 08:43:12PM +0100, Lars Sonchocky-Helldorf said:
> Hi,
>
> I am experiencing problems when trying to update the tcl port:
>
[...]
> --->  Configuring tcl
> Error: Target org.macports.configure returned: can't read  
> "configure.cppflags": no such variable
> Error: Unable to upgrade port: 1
> Lars-Sonchocky-Helldorfs-Computer:~ lars$

Looks like an odd issue which we'll have to investigate; for now, however,
I've added a bit of a kludge to get the port to work, in r44859.  Wait at
least 30 minutes, then 'sudo port sync' and try to do the upgrade again.

Bryan


>
>
> I recently installed Xcode 2.5 and did a sudo port -vf selfupdate just 
> before to force a recompile (now I am at 1.700)
>
> my Mac OS X version is 10.4.11 (Darwin 8.11.0)
>
>
> what can I do about it?
>
>
> Thanks,
>
> 	Lars

From olaf at foellinger.de  Sun Jan  4 03:30:53 2009
From: olaf at foellinger.de (Olaf Foellinger)
Date: Sun, 4 Jan 2009 12:30:53 +0100
Subject: GnuCash packaging - the good, the bad and the ugly
In-Reply-To: <20090103083912.GA28385@foellinger.de>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
	<20090103083912.GA28385@foellinger.de>
Message-ID: <20090104113053.GA25078@foellinger.de>

Hi,

here are the results of my investigation of the gnucash packaging.

First the good message: I've installed a clean version of macports,
added +no_x11 and +quartz to the variants.conf, changed the archiving to
yes and the autoclean to no in macports.conf, deleted the qt3 parts and
the cbanking an qbanking in the aqbanking portfile and - gnucash has
been build without problems as quartz variant.

The bad message: Packaging still doesn't work.

The ugly: the command

$ sudo port mdmg gnucash

fetched a lot of additional packages, most of the x related. I'll
attache the logfile. Why does this happen? Gnucash has been built with
all dependencies, so why does the packaging need additional packages?
Does it use a different dependency method or does it ognore the global
variants? Just guessing.


Gru? Olaf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gnucash-quartz-package.log.zip
Type: application/x-zip-compressed
Size: 13496 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090104/bb0210ea/attachment.bin>

From fbartolom at gmail.com  Sun Jan  4 04:10:57 2009
From: fbartolom at gmail.com (Fabrizio Bartolomucci)
Date: Sun, 04 Jan 2009 13:10:57 +0100
Subject: New Mac user and gdk-pixbuf-2-0
In-Reply-To: <495E3787.3040303@macports.org>
References: <495BAEDB.8050809@gmail.com> <495BC864.9000708@macports.org>
	<495DFC62.8050102@gmail.com> <495E3787.3040303@macports.org>
Message-ID: <4960A751.8070905@gmail.com>

An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090104/94d33111/attachment.html>

From jmr at macports.org  Sun Jan  4 04:26:38 2009
From: jmr at macports.org (Joshua Root)
Date: Sun, 04 Jan 2009 23:26:38 +1100
Subject: GnuCash packaging
In-Reply-To: <55476680-A7AE-4647-B851-97DEF60F5C21@macports.org>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>	<495ED53F.2020303@macports.org>	<1d6843d80901022224k3a831e91g8d95a8f6ba2861dc@mail.gmail.com>
	<55476680-A7AE-4647-B851-97DEF60F5C21@macports.org>
Message-ID: <4960AAFE.9080305@macports.org>

Anders F Bj?rklund wrote:
> Charles Day wrote:
> 
>> Well I tried the following workaround for ticket 10881, but macports
>> started trying to include the wrong dependencies. For example, it
>> tried to include dependencies based on X11 when I specified gnucash
>> +no_x11 (see gnome-desktop at the end as an example).
>>
>> In addition, it seems that some dependencies are required to be built
>> into their own destroots in advance (see the error message for
>> aqbanking below).
>>
>> So I'm not sure how I should try again to make it work.
> 
> Disable autoclean in macports.conf, uninstall and clean everything, and
> start over ?
> 
> The "force destroot" workaround requires that you do it for every single
> port,
> including all dependencies and making sure all needed variants are
> included...
> 
> "Given that this has been around for 2 years, is this considered a bug
> or a feature?"

Heh, there are bugs that have been around longer... it just appears that
relatively few people care about building binaries.

- Josh

From jmr at macports.org  Sun Jan  4 04:35:09 2009
From: jmr at macports.org (Joshua Root)
Date: Sun, 04 Jan 2009 23:35:09 +1100
Subject: New Mac user and gdk-pixbuf-2-0
In-Reply-To: <4960A751.8070905@gmail.com>
References: <495BAEDB.8050809@gmail.com>
	<495BC864.9000708@macports.org>	<495DFC62.8050102@gmail.com>
	<495E3787.3040303@macports.org> <4960A751.8070905@gmail.com>
Message-ID: <4960ACFD.4010603@macports.org>

Fabrizio Bartolomucci wrote:
> I did both but still I am no longer able to execute the upgrade outdate:
> 
> macbook-di-fabrizio-bartolomucci:bin fbartolom$ !529
> sudo ./port activate gtk2 @2.14.5_0+x11
> --->  Activating gtk2 @2.14.5_0+x11
> Error: port activate failed: Image error: gtk2 @2.14.5_0+x11 is already
> active.
> macbook-di-fabrizio-bartolomucci:bin fbartolom$ !531
> sudo ./port upgrade outdate
> Error: No port outdate found.

It's "outdated", not "outdate".

- Josh

From face at CentosPrime.COM  Sun Jan  4 05:42:01 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sun, 04 Jan 2009 06:42:01 -0700
Subject: Upgrading PHP5/MySQL ?
Message-ID: <57701359-8A46-42DF-A4FD-E019C7E165F1@centosprime.com>

Running from trunk.

Why is the mysql port being "upgraded"? I have mysql5-devel installed.  
The latest updates
(looked like bison, perl5.8, php5) are causing mysql5 to be installed?  
I'm confused.
Maybe one or more of bison, perl, or php5 doesn't know that mysql5- 
devel and mysql5 should be equivalent in terms
of dependencies?

Here's what is outdated...

mac 9 # port outdated
The following installed ports are outdated:
bison                          2.4_1 < 2.4.1_0
perl5.8                        5.8.8_3 < 5.8.9_0
php5                           5.2.8_0 < 5.2.8_1
python_select                  0.2_0 < 0.2.1_0

Here's what's installed
face at mac:~:123 $ 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.3_0 (active)
   apr-util @1.3.4_1 (active)
   aspell @0.60.6_1+macosx (active)
   aspell-dict-en @6.0_0 (active)
   aspell-dict-it @0.53_0 (active)
   atk @1.24.0_0 (active)
   AtomicParsley @0.9.0_0 (active)
   audiofile @0.2.6_2 (active)
   autoconf @2.63_0 (active)
   autoconf213 @2.13_0 (active)
   automake @1.10.2_0 (active)
   bash-completion @20060301_1 (active)
   bison @2.4_1
   bison @2.4.1_0 (active)
   bzip2 @1.0.5_1 (active)
   cairo @1.8.6_1+macosx (active)
   ccache @2.4_2 (active)
   cidr @2.3.2_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 @6.12_0+darwin_9 (active)
   csv2xml @0.6_0 (active)
   ctags @5.7_0 (active)
   curl @7.19.2_0+doc+sftp_scp+ssl (active)
   curl-ca-bundle @7.19.2_0 (active)
   cyrus-sasl2 @2.1.22_0+kerberos (active)
   db44 @4.4.20_1 (active)
   db46 @4.6.21_3 (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.74.0_0 (active)
   dom4j @1.6.1_1 (active)
   dos2unix @3.1_0 (active)
   emacs @22.3_0+atsui+carbon (active)
   esound @0.2.41_1 (active)
   expat @2.0.1_0 (active)
   faac @1.26_1 (active)
   faad2 @2.6.1_0 (active)
   ffmpeg @15261_1+a52+darwin_i386+extvorbis+faac+faad+gpl+lame 
+x264+xvid (active)
   flex @2.5.35_0 (active)
   fontconfig @2.6.0_1+macosx (active)
   fortune @6.2.0-RELEASE_0 (active)
   freetype @2.3.7_3+macosx (active)
   gawk @3.1.6_0 (active)
   gd2 @2.0.35_2 (active)
   gdbm @1.8.3_1 (active)
   getopt @1.1.4_1 (active)
   gettext @0.17_3 (active)
   glib2 @2.18.3_0+darwin_9 (active)
   gmake @3.81_0 (active)
   gmp @4.2.4_0 (active)
   gnome-common @2.24.0_1 (active)
   gnome-doc-utils @0.14.1_0 (active)
   gperf @3.0.3_0 (active)
   gtk-doc @1.11_0 (active)
   hamcrest-core @1.1_0 (active)
   help2man @1.36.4_1+darwin_8 (active)
   html2text @1.3.2a_3 (active)
   id3lib @3.8.3_0 (active)
   id3v2 @0.1.11_1 (active)
   ImageMagick @6.4.8-1_0+no_x11+q16 (active)
   imap-uw @2007_0 (active)
   intltool @0.40.5_0 (active)
   iso-codes @3.5_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)
   jaxen @1.1-beta-9_0 (active)
   jdom @1.0_0 (active)
   jpeg @6b_3 (active)
   junit @4.5_0 (active)
   lame @3.98.2_0 (active)
   libart_lgpl @2.3.20_0 (active)
   libiconv @1.12_0+darwin_8 (active)
   libmcrypt @2.5.8_1 (active)
   libmikmod @3.2.0-beta2_0 (active)
   libmp4v2 @1.5.0.1_0 (active)
   libogg @1.1.3_2 (active)
   libpcap @1.0.0_0 (active)
   libpixman @0.12.0_1 (active)
   libpng @1.2.34_0 (active)
   librsync @0.9.7_1 (active)
   libsdl @1.2.13_2+darwin_8 (active)
   libsdl_image @1.2.6_3 (active)
   libsdl_mixer @1.2.8_1 (active)
   libssh2 @0.18_0 (active)
   libtool @1.5.26_0
   libtool @2.2.6a_0 (active)
   libvorbis @1.2.0_1 (active)
   libxml2 @2.7.2_1+darwin_9 (active)
   libxslt @1.1.24_1+darwin_9 (active)
   lighttpd @1.4.19_0 (active)
   lynx @2.8.6rel.5_1+ssl (active)
   lzmautils @4.32.7_0 (active)
   m4 @1.4.12_1+with_default_names (active)
   macfuse @1.7_1 (active)
   mhash @0.9.9.9_0 (active)
   mod_python25 @3.3.1_1+universal (active)
   mx4j @3.0.1_0 (active)
   mysql-connector-java @5.0.7_0 (active)
   mysql5-devel @5.1.30_0+server (active)
   ncurses @5.7_0 (active)
   ncursesw @5.7_0 (active)
   neon @0.28.3_0 (active)
   nmap @4.76_0 (active)
   openssl @0.9.8i_0 (active)
   p5-html-tableextract @2.10_0 (active)
   p5-locale-gettext @1.05_0 (active)
   p5-mime-base64 @3.07_0 (active)
   p5-xml-parser @2.36_0 (active)
   palm-db-tools @0.3.6_1+darwin_8 (active)
   pcre @7.8_1 (active)
   perl5.8 @5.8.8_3+darwin_8+darwin_9
   perl5.8 @5.8.9_0 (active)
   php5 @5.2.8_0+apache2+macosx+mysql5+pear (active)
   phpicalendar @2.24_0 (active)
   pkgconfig @0.23_1 (active)
   popt @1.14_0 (active)
   pstree @2.32_0 (active)
   py-markdown @1.7_0 (active)
   py25-beautifulsoup @3.0.7a_0 (active)
   py25-cherrypy3 @3.0.3_0 (active)
   py25-django-devel @0.96.1_1 (active)
   py25-feedparser @4.1_0 (active)
   py25-genshi @0.5_0 (active)
   py25-gobject @2.14.2_0+darwin_9 (active)
   py25-hashlib @2.5.2_0
   py25-hashlib @2.5.4_0 (active)
   py25-libxml2 @2.6.21_1 (active)
   py25-lxml @2.1.4_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.2_0
   py25-sqlite3 @2.5.4_0 (active)
   py25-xml @0.8.4_0 (active)
   py25-zlib @2.5.2_0
   py25-zlib @2.5.4_0 (active)
   python24 @2.4.6_0+darwin_9 (active)
   python25 @2.5.2_7+darwin_9
   python25 @2.5.4_0+darwin_9 (active)
   python_select @0.1_4+darwin_9
   python_select @0.2_0+darwin_9 (active)
   rarian @0.8.1_0 (active)
   readline @5.2.012_1 (active)
   render @0.9.2_0 (active)
   saxpath @1.0_0 (active)
   serf @0.2.0_0 (active)
   servlet23-api @1_0 (active)
   servlet24-api @5.5.25_0 (active)
   shared-mime-info @0.51_0 (active)
   sipcalc @1.1.4_0 (active)
   smpeg @0.4.4_6+darwin_8 (active)
   sqlite3 @3.6.6.2_0 (active)
   subversion @1.5.5_0+bash_completion+mod_dav_svn+no_bdb+tools (active)
   texinfo @4.13_0 (active)
   tiff @3.8.2_2+darwin_9+macosx (active)
   tomcat-native @1.1.14_0 (active)
   tomcat5 @5.5.25_0 (active)
   tree @1.5.2.1_0 (active)
   ttcp @1.10_0 (active)
   vms-empire @1.7_0 (active)
   waitfor @0.5_0 (active)
   watch @3.2.7_0 (active)
   wtf @20080926_0 (active)
   x264 @20080724_1 (active)
   xalanj @2.7.0_1 (active)
   xercesj @2.9.1_0 (active)
   Xft2 @2.1.13_0 (active)
   xmlcatmgr @2.2_1 (active)
   xom @1.0_0 (active)
   xorg-renderproto @0.9.3_0 (active)
   xorg-util-macros @1.2.1_0 (active)
   xorg-xproto @7.0.14_1 (active)
   xrender @0.9.4_4+macosx (active)
   XviD @1.1.3_1 (active)
   yasm @0.7.2_0 (active)
   zlib @1.2.3_2 (active)

Here's what's happening

mac 24 # sudo port upgrade outdated
Password:
--->  Fetching bison
--->  Attempting to fetch bison-2.4.1.tar.bz2 from http://distfiles.macports.org/bison
--->  Verifying checksum(s) for bison
--->  Extracting bison
--->  Configuring bison
--->  Building bison
--->  Staging bison into destroot
--->  Deactivating bison @2.4_1
--->  Installing bison @2.4.1_0
--->  Activating bison @2.4.1_0
--->  Cleaning bison
--->  Fetching perl5.8
--->  Attempting to fetch perl-5.8.9.tar.bz2 from http://distfiles.macports.org/perl5.8
--->  Verifying checksum(s) for perl5.8
--->  Extracting perl5.8
--->  Configuring perl5.8
--->  Building perl5.8
--->  Staging perl5.8 into destroot
--->  Deactivating perl5.8 @5.8.8_3+darwin_8+darwin_9
--->  Installing perl5.8 @5.8.9_0
--->  Activating perl5.8 @5.8.9_0
--->  Cleaning perl5.8
Warning: Skipping upgrade since help2man 1.36.4_1 >= help2man  
1.36.4_1, even though installed variant +darwin_8 does not match .  
Specify -f to force upgrade.
Warning: Skipping upgrade since libxslt 1.1.24_1 >= libxslt 1.1.24_1,  
even though installed variant +darwin_9 does not match . Specify -f to  
force upgrade.
Portfile changed since last build; discarding previous state.
--->  Fetching mysql5
--->  Attempting to fetch mysql-5.0.67.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

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



From face at CentosPrime.COM  Sun Jan  4 06:06:30 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Sun, 04 Jan 2009 07:06:30 -0700
Subject: Upgrading PHP5/MySQL ?
In-Reply-To: <57701359-8A46-42DF-A4FD-E019C7E165F1@centosprime.com>
References: <57701359-8A46-42DF-A4FD-E019C7E165F1@centosprime.com>
Message-ID: <C71830AE-A0F0-4E53-AEDC-E6567B5A3AAD@centosprime.com>

On 2009-01-04 , at 06:42 , Chris Janton wrote:

> --->  Building mysql5


here's the rest of the upgrade...

--->  Staging mysql5 into destroot
--->  Installing mysql5 @5.0.67_1
--->  Activating mysql5 @5.0.67_1
Error: Target org.macports.activate returned: Image error: /opt/local/ 
bin/my_print_defaults5 is being used by the active mysql5-devel port.   
Please deactivate this port first, or use the -f flag to force the  
activation.
Error: Problem while installing mysql5
Warning: Skipping upgrade since apr-util 1.3.4_1 >= apr-util 1.3.4_1,  
even though installed variant  does not match +mysql5. Specify -f to  
force upgrade.
--->  Activating mysql5 @5.0.67_1
Error: Activating mysql5 @5.0.67_1 failed: Image error: /opt/local/bin/ 
my_print_defaults5 is being used by the active mysql5-devel port.   
Please deactivate this port first, or use the -f flag to force the  
activation.
--->  Fetching php5
--->  Verifying checksum(s) for php5
--->  Extracting php5
--->  Applying patches to php5
--->  Configuring php5
--->  Building php5
--->  Staging php5 into destroot
Warning: php5 requests to install files outside the common directory  
structure!
--->  Deactivating php5 @5.2.8_0+apache2+macosx+mysql5+pear
--->  Installing php5 @5.2.8_1+apache2+macosx+mysql5+pear

If this is your first install, you might want
cd /opt/local/apache2/modules
/opt/local/apache2/bin/apxs -a -e -n "php5" libphp5.so

* copy  /opt/local/etc/php.ini-dist to  /opt/local/etc/php.ini
--->  Activating php5 @5.2.8_1+apache2+macosx+mysql5+pear
--->  Cleaning php5
--->  Fetching python_select
--->  Attempting to fetch select-0.2.1.tar.gz from http://svn.macports.org/repository/macports/contrib/select/
--->  Verifying checksum(s) for python_select
--->  Extracting python_select
--->  Configuring python_select
--->  Building python_select
--->  Staging python_select into destroot
--->  Deactivating python_select @0.2_0+darwin_9
--->  Installing python_select @0.2.1_0+darwin_9
--->  Activating python_select @0.2.1_0+darwin_9
--->  Cleaning python_select

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



From fbartolom at gmail.com  Sun Jan  4 08:33:30 2009
From: fbartolom at gmail.com (Fabrizio Bartolomucci)
Date: Sun, 04 Jan 2009 17:33:30 +0100
Subject: New Mac user and gdk-pixbuf-2-0
In-Reply-To: <4960ACFD.4010603@macports.org>
References: <495BAEDB.8050809@gmail.com>
	<495BC864.9000708@macports.org>	<495DFC62.8050102@gmail.com>
	<495E3787.3040303@macports.org> <4960A751.8070905@gmail.com>
	<4960ACFD.4010603@macports.org>
Message-ID: <4960E4DA.6020709@gmail.com>

An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090104/d92e87ac/attachment.html>

From ryandesign at macports.org  Sun Jan  4 12:42:53 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 4 Jan 2009 14:42:53 -0600
Subject: Upgrading PHP5/MySQL ?
In-Reply-To: <57701359-8A46-42DF-A4FD-E019C7E165F1@centosprime.com>
References: <57701359-8A46-42DF-A4FD-E019C7E165F1@centosprime.com>
Message-ID: <8DA3704B-FF2A-4833-B895-21E0E2893A83@macports.org>


On Jan 4, 2009, at 07:42, Chris Janton wrote:

> Running from trunk.
>
> Why is the mysql port being "upgraded"? I have mysql5-devel  
> installed. The latest updates
> (looked like bison, perl5.8, php5) are causing mysql5 to be  
> installed? I'm confused.
> Maybe one or more of bison, perl, or php5 doesn't know that mysql5- 
> devel and mysql5 should be equivalent in terms
> of dependencies?

I believe it's rather a bug in MacPorts base.

I thought it might be this:

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

But if you're running from a recent-enough trunk which includes the  
fix for that, then it's a different bug. I don't know if an issue has  
been filed for it.


From ryandesign at macports.org  Sun Jan  4 12:47:58 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 4 Jan 2009 14:47:58 -0600
Subject: New Mac user and gdk-pixbuf-2-0
In-Reply-To: <4960E4DA.6020709@gmail.com>
References: <495BAEDB.8050809@gmail.com>
	<495BC864.9000708@macports.org>	<495DFC62.8050102@gmail.com>
	<495E3787.3040303@macports.org> <4960A751.8070905@gmail.com>
	<4960ACFD.4010603@macports.org> <4960E4DA.6020709@gmail.com>
Message-ID: <D4B74977-7513-407D-B461-376F38A31EC2@macports.org>

On Jan 4, 2009, at 10:33, Fabrizio Bartolomucci wrote:

> On passing, is there a way by which I can skip the ./ and still get  
> 'port'?

Yes, you should be able to do so. If you get the message that the  
port command cannot be found, then you need to fix your PATH  
environment variable to include /opt/local/bin and /opt/local/sbin.  
The MacPorts installer takes care of this for you, except that there  
was a bug with the 1.6.0 installer such that it did not do this. So  
if you originally installed MacPorts via the 1.6.0 installer, that  
would explain the problem.

The fix is here:

http://trac.macports.org/wiki/ProblemHotlist#a.profilenotsetup



From cedayiv at gmail.com  Sun Jan  4 16:13:54 2009
From: cedayiv at gmail.com (Charles Day)
Date: Sun, 4 Jan 2009 16:13:54 -0800
Subject: GnuCash packaging
In-Reply-To: <4960AAFE.9080305@macports.org>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
	<495ED53F.2020303@macports.org>
	<1d6843d80901022224k3a831e91g8d95a8f6ba2861dc@mail.gmail.com>
	<55476680-A7AE-4647-B851-97DEF60F5C21@macports.org>
	<4960AAFE.9080305@macports.org>
Message-ID: <1d6843d80901041613k4f4d781xc19f9fa1a45ff1c7@mail.gmail.com>

On Sun, Jan 4, 2009 at 4:26 AM, Joshua Root <jmr at macports.org> wrote:

> Anders F Bj?rklund wrote:
> > Charles Day wrote:
> >
> >> Well I tried the following workaround for ticket 10881, but macports
> >> started trying to include the wrong dependencies. For example, it
> >> tried to include dependencies based on X11 when I specified gnucash
> >> +no_x11 (see gnome-desktop at the end as an example).
> >>
> >> In addition, it seems that some dependencies are required to be built
> >> into their own destroots in advance (see the error message for
> >> aqbanking below).
> >>
> >> So I'm not sure how I should try again to make it work.
> >
> > Disable autoclean in macports.conf, uninstall and clean everything, and
> > start over ?
> >
> > The "force destroot" workaround requires that you do it for every single
> > port,
> > including all dependencies and making sure all needed variants are
> > included...
> >
> > "Given that this has been around for 2 years, is this considered a bug
> > or a feature?"
>
> Heh, there are bugs that have been around longer... it just appears that
> relatively few people care about building binaries.
>

Maybe not too many care about building them, but a lot care about
distributing them once they are built. A distribution of GnuCash for Mac in
binary form is one of the more requested features (especially recently) I
see as a GnuCash developer. Going through the steps of installing GnuCash
via MacPorts or Fink is unfortunately beyond what many users are able or
willing to do.

So that's why I'm looking into building a binary...


> - Josh
>

-Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090104/514eb392/attachment.html>

From afb at macports.org  Sun Jan  4 16:23:37 2009
From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=)
Date: Mon, 5 Jan 2009 01:23:37 +0100
Subject: GnuCash packaging
In-Reply-To: <1d6843d80901041613k4f4d781xc19f9fa1a45ff1c7@mail.gmail.com>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
	<495ED53F.2020303@macports.org>
	<1d6843d80901022224k3a831e91g8d95a8f6ba2861dc@mail.gmail.com>
	<55476680-A7AE-4647-B851-97DEF60F5C21@macports.org>
	<4960AAFE.9080305@macports.org>
	<1d6843d80901041613k4f4d781xc19f9fa1a45ff1c7@mail.gmail.com>
Message-ID: <2AD86DD6-D594-492E-8685-EAA5929CC097@macports.org>

Charles Day wrote:

>> ... it just appears that
>> relatively few people care about building binaries.
>
> Maybe not too many care about building them, but a lot care about  
> distributing them once they are built. A distribution of GnuCash  
> for Mac in binary form is one of the more requested features  
> (especially recently) I see as a GnuCash developer. Going through  
> the steps of installing GnuCash via MacPorts or Fink is  
> unfortunately beyond what many users are able or willing to do.
>
> So that's why I'm looking into building a binary...

Pretty much the only port "supported" as a stand-alone binary package  
is sysutils/MacPorts...

If your users are unwilling to install MacPorts or Fink, maybe you  
need a stand-alone GnuCash ?

--anders


From afb at macports.org  Sun Jan  4 16:28:58 2009
From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=)
Date: Mon, 5 Jan 2009 01:28:58 +0100
Subject: GnuCash packaging
In-Reply-To: <4960AAFE.9080305@macports.org>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>	<495ED53F.2020303@macports.org>	<1d6843d80901022224k3a831e91g8d95a8f6ba2861dc@mail.gmail.com>
	<55476680-A7AE-4647-B851-97DEF60F5C21@macports.org>
	<4960AAFE.9080305@macports.org>
Message-ID: <90BBA906-39AA-46F1-8859-29D7FBC2281F@macports.org>

Joshua Root wrote:

>> "Given that this has been around for 2 years, is this considered a  
>> bug
>> or a feature?"
>
> Heh, there are bugs that have been around longer... it just appears  
> that
> relatively few people care about building binaries.

Was referring to http://trac.macports.org/ticket/10881#comment:20

--anders


From jmr at macports.org  Mon Jan  5 00:52:54 2009
From: jmr at macports.org (Joshua Root)
Date: Mon, 05 Jan 2009 19:52:54 +1100
Subject: GnuCash packaging
In-Reply-To: <1d6843d80901041613k4f4d781xc19f9fa1a45ff1c7@mail.gmail.com>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>	
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>	
	<495ED53F.2020303@macports.org>	
	<1d6843d80901022224k3a831e91g8d95a8f6ba2861dc@mail.gmail.com>	
	<55476680-A7AE-4647-B851-97DEF60F5C21@macports.org>	
	<4960AAFE.9080305@macports.org>
	<1d6843d80901041613k4f4d781xc19f9fa1a45ff1c7@mail.gmail.com>
Message-ID: <4961CA66.5040604@macports.org>

Charles Day wrote:
> On Sun, Jan 4, 2009 at 4:26 AM, Joshua Root <jmr at macports.org
> <mailto:jmr at macports.org>> wrote:
> 
>     Anders F Bj?rklund wrote:
>     > Charles Day wrote:
>     >
>     >> Well I tried the following workaround for ticket 10881, but macports
>     >> started trying to include the wrong dependencies. For example, it
>     >> tried to include dependencies based on X11 when I specified gnucash
>     >> +no_x11 (see gnome-desktop at the end as an example).
>     >>
>     >> In addition, it seems that some dependencies are required to be built
>     >> into their own destroots in advance (see the error message for
>     >> aqbanking below).
>     >>
>     >> So I'm not sure how I should try again to make it work.
>     >
>     > Disable autoclean in macports.conf, uninstall and clean
>     everything, and
>     > start over ?
>     >
>     > The "force destroot" workaround requires that you do it for every
>     single
>     > port,
>     > including all dependencies and making sure all needed variants are
>     > included...
>     >
>     > "Given that this has been around for 2 years, is this considered a bug
>     > or a feature?"
> 
>     Heh, there are bugs that have been around longer... it just appears that
>     relatively few people care about building binaries.
> 
> 
> Maybe not too many care about building them, but a lot care about
> distributing them once they are built. A distribution of GnuCash for Mac
> in binary form is one of the more requested features (especially
> recently) I see as a GnuCash developer. Going through the steps of
> installing GnuCash via MacPorts or Fink is unfortunately beyond what
> many users are able or willing to do.
> 
> So that's why I'm looking into building a binary...

I wasn't disparaging anyone's desire to build binaries, just explaining
why the bug is still unfixed.

- Josh

From dave.evans55 at googlemail.com  Mon Jan  5 03:23:24 2009
From: dave.evans55 at googlemail.com (David Evans)
Date: Mon, 05 Jan 2009 11:23:24 +0000
Subject: Perl 5.8 @5.8.9 does not get on with Ccache during configure
Message-ID: <4961EDAC.7010108@googlemail.com>

Perl does not get on with CCACHE during the configure phase.
It works if ccache is disabled.
With ccache enabled in the macports config file I get:

two:~ davidevans$ sudo port -df configure perl5.8
DEBUG: Found port in 
file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5.8
DEBUG: Changing to port directory: 
/opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5.8
DEBUG: 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 no' specified, so not adding the default 
universal variant
DEBUG: Requested variant darwin is not provided by port perl5.8.
DEBUG: Requested variant i386 is not provided by port perl5.8.
DEBUG: Requested variant macosx is not provided by port perl5.8.
DEBUG: Executing org.macports.main (perl5.8)
DEBUG: Skipping completed org.macports.fetch (perl5.8)
DEBUG: Skipping completed org.macports.checksum (perl5.8)
DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
DEBUG: Skipping completed org.macports.extract (perl5.8)
DEBUG: Skipping completed org.macports.patch (perl5.8)
--->  Configuring perl5.8
DEBUG: Using compiler 'Mac OS X gcc 4.0'
DEBUG: Executing org.macports.configure (perl5.8)
DEBUG: Environment: CFLAGS='-O2' CPPFLAGS='-I/opt/local/include' 
CXXFLAGS='-O2' MACOSX_DEPLOYMENT_TARGET='10.5' CPP='ccache 
/usr/bin/cpp-4.0' CXX='ccache /usr/bin/g++-4.0' F90FLAGS='-O2' 
LDFLAGS='-L/opt/local/lib' FCFLAGS='-O2' OBJC='ccache /usr/bin/gcc-4.0' 
INSTALL='/usr/bin/install -c' OBJCFLAGS='-O2' FFLAGS='-O2' CC='ccache 
/usr/bin/gcc-4.0' LC_ALL='C'
DEBUG: Assembled command: 'cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_perl5.8/work/perl-5.8.9" 
&& /bin/sh Configure -des -D prefix='/opt/local' -D 
cppflags="${CPPFLAGS}" -D ldflags="${LDFLAGS}" -D 
vendorprefix='/opt/local' -D man3ext='3pm' -D cc=${CC} -D ld=${CC}'
First let's make sure your kit is complete.  Checking...
Would you like to see the instructions? [n] 
Locating common programs...
Checking compatibility between /bin/echo and builtin echo (if any)...
Symbolic links are supported.
Checking how to test for symbolic links...
You can test for symbolic links with 'test -h'.
Good, your tr supports [:lower:] and [:upper:] to convert case.
Using [:upper:] and [:lower:] to convert case.
ccache: illegal option -- o
You need to find a working C compiler.
Either (purchase and) install the C compiler supplied by your OS vendor,
or for a free C compiler try http://gcc.gnu.org/
I cannot continue any further, aborting.





From brian at newmedio.com  Mon Jan  5 08:28:46 2009
From: brian at newmedio.com (Brian Dunn)
Date: Mon, 5 Jan 2009 10:28:46 -0600
Subject: wordpress portfile should build php with mysql support
Message-ID: <2C39BDF5-F9C8-43B3-8E01-06B6A9600E40@newmedio.com>

would have posted this on the trac site, but it is down.
is there a way for one port to require another to use a certain  
variant? how should this be handled?

From jmr at macports.org  Mon Jan  5 09:04:46 2009
From: jmr at macports.org (Joshua Root)
Date: Tue, 06 Jan 2009 04:04:46 +1100
Subject: wordpress portfile should build php with mysql support
In-Reply-To: <2C39BDF5-F9C8-43B3-8E01-06B6A9600E40@newmedio.com>
References: <2C39BDF5-F9C8-43B3-8E01-06B6A9600E40@newmedio.com>
Message-ID: <49623DAE.6000305@macports.org>

Brian Dunn wrote:
> would have posted this on the trac site, but it is down.
> is there a way for one port to require another to use a certain variant?
> how should this be handled?

No, that's bug #126. About the best you can do at present is to detect
that the required functionality is missing and tell the user how to fix it.

- Josh

From whodoctor at gmail.com  Mon Jan  5 09:10:58 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Mon, 5 Jan 2009 12:10:58 -0500
Subject: Claws-mail port question
Message-ID: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>

Not sure if this is the right list, so let me know if this is not the
case.  I installed MacPorts yesterday and used it to install
claws-mail from ports.

Everything went well with the install, and I can launch claws-mail and
view messages, etc.

However, only a few plugins appear to be built.  I don't have plugins
for gtkhtml2-viewer or attach_reminder, for example.

There is not a separate port for the plugins that I can see.  And
there is no maintainer listed on the ports.

I'm hoping someone can help me with this.

Thanks!

From cedayiv at gmail.com  Mon Jan  5 13:02:29 2009
From: cedayiv at gmail.com (Charles Day)
Date: Mon, 5 Jan 2009 13:02:29 -0800
Subject: GnuCash packaging
In-Reply-To: <4961CA66.5040604@macports.org>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
	<495ED53F.2020303@macports.org>
	<1d6843d80901022224k3a831e91g8d95a8f6ba2861dc@mail.gmail.com>
	<55476680-A7AE-4647-B851-97DEF60F5C21@macports.org>
	<4960AAFE.9080305@macports.org>
	<1d6843d80901041613k4f4d781xc19f9fa1a45ff1c7@mail.gmail.com>
	<4961CA66.5040604@macports.org>
Message-ID: <1d6843d80901051302u3e4ec600v7c6b9406073de42e@mail.gmail.com>

On Mon, Jan 5, 2009 at 12:52 AM, Joshua Root <jmr at macports.org> wrote:

> Charles Day wrote:
> > On Sun, Jan 4, 2009 at 4:26 AM, Joshua Root <jmr at macports.org
> > <mailto:jmr at macports.org>> wrote:
> >
> >     Anders F Bj?rklund wrote:
> >     > Charles Day wrote:
> >     >
> >     >> Well I tried the following workaround for ticket 10881, but
> macports
> >     >> started trying to include the wrong dependencies. For example, it
> >     >> tried to include dependencies based on X11 when I specified
> gnucash
> >     >> +no_x11 (see gnome-desktop at the end as an example).
> >     >>
> >     >> In addition, it seems that some dependencies are required to be
> built
> >     >> into their own destroots in advance (see the error message for
> >     >> aqbanking below).
> >     >>
> >     >> So I'm not sure how I should try again to make it work.
> >     >
> >     > Disable autoclean in macports.conf, uninstall and clean
> >     everything, and
> >     > start over ?
> >     >
> >     > The "force destroot" workaround requires that you do it for every
> >     single
> >     > port,
> >     > including all dependencies and making sure all needed variants are
> >     > included...
> >     >
> >     > "Given that this has been around for 2 years, is this considered a
> bug
> >     > or a feature?"
> >
> >     Heh, there are bugs that have been around longer... it just appears
> that
> >     relatively few people care about building binaries.
> >
> >
> > Maybe not too many care about building them, but a lot care about
> > distributing them once they are built. A distribution of GnuCash for Mac
> > in binary form is one of the more requested features (especially
> > recently) I see as a GnuCash developer. Going through the steps of
> > installing GnuCash via MacPorts or Fink is unfortunately beyond what
> > many users are able or willing to do.
> >
> > So that's why I'm looking into building a binary...
>
> I wasn't disparaging anyone's desire to build binaries, just explaining
> why the bug is still unfixed.
>

I never took it that way. Heck, I'm not even sure what the package would
contain or how useful it would be. This is still experimentation on my part
at this point to see what's possible.


> - Josh
>

Cheers,
Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090105/eabae0df/attachment.html>

From face at CentosPrime.COM  Mon Jan  5 15:24:09 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Mon, 05 Jan 2009 16:24:09 -0700
Subject: Upgrading PHP5/MySQL ?
In-Reply-To: <8DA3704B-FF2A-4833-B895-21E0E2893A83@macports.org>
References: <57701359-8A46-42DF-A4FD-E019C7E165F1@centosprime.com>
	<8DA3704B-FF2A-4833-B895-21E0E2893A83@macports.org>
Message-ID: <437F791D-0EAB-4834-A359-C403B652A2B2@centosprime.com>

On 2009-01-04 , at 13:42 , Ryan Schmidt wrote:

> But if you're running from a recent-enough trunk which includes the  
> fix for that, then it's a different bug. I don't know if an issue  
> has been filed for it.


mac 2 # cd /opt/mports/trunk
mac 3 # svn update
Updated to revision 44971.

Well, I wound up with an updated mysql5-devel, not sure what to do  
other than be happy and get back to work.

Thanks.

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



From sheldon at oneblackbear.com  Tue Jan  6 07:25:59 2009
From: sheldon at oneblackbear.com (sheldon)
Date: Tue, 6 Jan 2009 15:25:59 +0000 (UTC)
Subject: apache2 env path
Message-ID: <loom.20090106T152350-866@post.gmane.org>

Hi

I'm using apache2 installed and running via macports in /opt/local. I'm using
php to run a exec() function via a script and would like to set the path apache
has access to so I can run ImageMagick commands to convert images via php. Since
ImageMagick was installed via macports too, it's executables are outside the
default path (which seems to be only /bin:/sbin:/usr/bin:/usr/sbin) and I need
to be able to set apache's running path. Can Anyone please help?

Kind Regards
Sheldon


From ndiscreet at gmail.com  Tue Jan  6 14:48:54 2009
From: ndiscreet at gmail.com (Altoine Barker)
Date: Tue, 06 Jan 2009 16:48:54 -0600
Subject: ufraw Not Build
Message-ID: <4963DFD6.3090402@GmAiL.cOm>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I am running Mac OSX 10.5.6 on a G5 Dual 2GHz.
I have MacPorts 1.700 (Binary) with XCode 3.1.1 (gcc version 4.0.1).

I received the following error when I attempted to upgrade my outdated
ports:
<snip>
The MacPorts installation is not outdated so it was not updated>
Building ufraw
make  all-recursive
Making all in po
make[2]: Nothing to be done for `all'.
Making all in icons
make[2]: Nothing to be done for `all'.
/usr/bin/g++-4.0  -O2   -L/opt/local/lib -o ufraw ufraw.o libufraw.a
- -R/opt/local/lib -Wl,-framework -Wl,CoreFoundation -L/opt/local/lib
- -lexiv2 -lintl -lc -liconv -lz -lexpat   -L/opt/local/lib -lglib-2.0
- -lintl -liconv   -L/opt/local/lib -llcms    -L/opt/local/lib -lpng12 -lz
  -L/opt/local/lib -lgtkimageview -lgtk-quartz-2.0 -lgdk-quartz-2.0
- -latk-1.0 -lgio-2.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo
- -lpangoft2-1.0 -lpango-1.0 -lm -lpixman-1 -lfontconfig -lexpat
- -lfreetype -lpng12 -lz -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl
- -liconv   -ltiff -ljpeg -lbz2 -lz  -lintl
Undefined symbols:
  "_CMCloseProfile", referenced from:
      _uf_get_display_profile in libufraw.a(uf_gtk.o)
  "_CMFlattenProfile", referenced from:
      _uf_get_display_profile in libufraw.a(uf_gtk.o)
  "_CMGetProfileByAVID", referenced from:
      _uf_get_display_profile in libufraw.a(uf_gtk.o)
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[2]: *** [ufraw] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Error: Target org.macports.build returned: shell command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_ufraw/work/ufraw-0.15"
&& make all " returned error 2
Command output: make  all-recursive
Making all in po
make[2]: Nothing to be done for `all'.
Making all in icons
make[2]: Nothing to be done for `all'.
/usr/bin/g++-4.0  -O2   -L/opt/local/lib -o ufraw ufraw.o libufraw.a
- -R/opt/local/lib -Wl,-framework -Wl,CoreFoundation -L/opt/local/lib
- -lexiv2 -lintl -lc -liconv -lz -lexpat   -L/opt/local/lib -lglib-2.0
- -lintl -liconv   -L/opt/local/lib -llcms    -L/opt/local/lib -lpng12 -lz
  -L/opt/local/lib -lgtkimageview -lgtk-quartz-2.0 -lgdk-quartz-2.0
- -latk-1.0 -lgio-2.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo
- -lpangoft2-1.0 -lpango-1.0 -lm -lpixman-1 -lfontconfig -lexpat
- -lfreetype -lpng12 -lz -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl
- -liconv   -ltiff -ljpeg -lbz2 -lz  -lintl
Undefined symbols:
  "_CMCloseProfile", referenced from:
      _uf_get_display_profile in libufraw.a(uf_gtk.o)
  "_CMFlattenProfile", referenced from:
      _uf_get_display_profile in libufraw.a(uf_gtk.o)
  "_CMGetProfileByAVID", referenced from:
      _uf_get_display_profile in libufraw.a(uf_gtk.o)
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[2]: *** [ufraw] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Warning: the following items did not execute (for ufraw):
org.macports.destroot org.macports.build
Error: Unable to upgrade port: 1
</snip>

I upgraded my XCode SDK to XCode 3.1.2 and the problem is the same. TIA

- -Altoine

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAklj39YACgkQQlfc9y4ObkOlSwCfRlL//Wc3vW2UK9TLHBSMDvr7
WXEAoIc5iuXh3vM03sxQnKvupHSXv3SG
=nscx
-----END PGP SIGNATURE-----

From olaf at foellinger.de  Wed Jan  7 00:06:15 2009
From: olaf at foellinger.de (Olaf Foellinger)
Date: Wed, 7 Jan 2009 09:06:15 +0100
Subject: GnuCash packaging
In-Reply-To: <1d6843d80901041613k4f4d781xc19f9fa1a45ff1c7@mail.gmail.com>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
	<495ED53F.2020303@macports.org>
	<1d6843d80901022224k3a831e91g8d95a8f6ba2861dc@mail.gmail.com>
	<55476680-A7AE-4647-B851-97DEF60F5C21@macports.org>
	<4960AAFE.9080305@macports.org>
	<1d6843d80901041613k4f4d781xc19f9fa1a45ff1c7@mail.gmail.com>
Message-ID: <20090107080615.GA22981@foellinger.de>

Hi,

* Charles Day <cedayiv at gmail.com> [05.01.09 01:14]wrote:

>    Maybe not too many care about building them, but a lot care about
>    distributing them once they are built. A distribution of GnuCash for
>    Mac in binary form is one of the more requested features (especially
>    recently) I see as a GnuCash developer. Going through the steps of
>    installing GnuCash via MacPorts or Fink is unfortunately beyond what
>    many users are able or willing to do.
>    So that's why I'm looking into building a binary...

the OS X native Gimp.app has been built based on MacPorts IIRC. Maybe
that's another good starting point for the goal.


Gru? Olaf

From frstan at bellsouth.net  Wed Jan  7 07:34:53 2009
From: frstan at bellsouth.net (William Davis)
Date: Wed, 7 Jan 2009 10:34:53 -0500
Subject: ::ui_init
Message-ID: <C5588181-129C-417A-A1E6-3FE1A84AF286@bellsouth.net>

Warning: the following items did not execute (for xorg-libice):  
org.macports.destroot org.macports.build
DEBUG: invalid command name "::ui_init"
     while executing
"::ui_init $priority $prefix $channels $message"
     ("uplevel" body line 2)
     invoked from within
"uplevel 1 $body"
Error: Unable to upgrade port: 1
macintosh:~ frstan$

There are now something like 5 ports which fail update with 'invalid  
command name "::ui_init".
What's the story?


William Davis
frstanATbellsouthDOTnet
Mac OS X.5.6 Darwin 9.5.0
XQuartz 2.3.2 (xorg-server 1.4.2-apple31)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From jmr at macports.org  Wed Jan  7 07:58:35 2009
From: jmr at macports.org (Joshua Root)
Date: Thu, 08 Jan 2009 02:58:35 +1100
Subject: ::ui_init
In-Reply-To: <C5588181-129C-417A-A1E6-3FE1A84AF286@bellsouth.net>
References: <C5588181-129C-417A-A1E6-3FE1A84AF286@bellsouth.net>
Message-ID: <4964D12B.7030600@macports.org>

William Davis wrote:
> Warning: the following items did not execute (for xorg-libice):
> org.macports.destroot org.macports.build
> DEBUG: invalid command name "::ui_init"
>     while executing
> "::ui_init $priority $prefix $channels $message"
>     ("uplevel" body line 2)
>     invoked from within
> "uplevel 1 $body"
> Error: Unable to upgrade port: 1
> macintosh:~ frstan$
> 
> There are now something like 5 ports which fail update with 'invalid
> command name "::ui_init".
> What's the story?

The ui_init thing is not what is causing the failure, you'll notice that
it happens after another error. Previous mention on the list:
<http://lists.macosforge.org/pipermail/macports-dev/2008-December/006786.html>

- Josh

From cedayiv at gmail.com  Wed Jan  7 15:09:05 2009
From: cedayiv at gmail.com (Charles Day)
Date: Wed, 7 Jan 2009 15:09:05 -0800
Subject: GnuCash packaging
In-Reply-To: <20090107080615.GA22981@foellinger.de>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
	<495ED53F.2020303@macports.org>
	<1d6843d80901022224k3a831e91g8d95a8f6ba2861dc@mail.gmail.com>
	<55476680-A7AE-4647-B851-97DEF60F5C21@macports.org>
	<4960AAFE.9080305@macports.org>
	<1d6843d80901041613k4f4d781xc19f9fa1a45ff1c7@mail.gmail.com>
	<20090107080615.GA22981@foellinger.de>
Message-ID: <1d6843d80901071509m4aec083ehe6251cb13e793dc7@mail.gmail.com>

On Wed, Jan 7, 2009 at 12:06 AM, Olaf Foellinger <olaf at foellinger.de> wrote:

> Hi,
>
> * Charles Day <cedayiv at gmail.com> [05.01.09 01:14]wrote:
>
> >    Maybe not too many care about building them, but a lot care about
> >    distributing them once they are built. A distribution of GnuCash for
> >    Mac in binary form is one of the more requested features (especially
> >    recently) I see as a GnuCash developer. Going through the steps of
> >    installing GnuCash via MacPorts or Fink is unfortunately beyond what
> >    many users are able or willing to do.
> >    So that's why I'm looking into building a binary...
>
> the OS X native Gimp.app has been built based on MacPorts IIRC. Maybe
> that's another good starting point for the goal.
>

I don't know if this is up to date, but I found a procedure for building a
Gimp .app using MacPorts:
http://darwingimp.sourceforge.net/buildgimp.html

This may give some interesting clues.


>
> Gru? Olaf
>

Cheers,
Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090107/ce8c8d5f/attachment.html>

From ryandesign at macports.org  Wed Jan  7 16:57:50 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 7 Jan 2009 18:57:50 -0600
Subject: apache2 env path
In-Reply-To: <loom.20090106T152350-866@post.gmane.org>
References: <loom.20090106T152350-866@post.gmane.org>
Message-ID: <BDB601EB-2AF0-4EA0-A542-4BB344D8A785@macports.org>


On Jan 6, 2009, at 09:25, sheldon wrote:

> I'm using apache2 installed and running via macports in /opt/local.  
> I'm using
> php to run a exec() function via a script and would like to set the  
> path apache
> has access to so I can run ImageMagick commands to convert images  
> via php. Since
> ImageMagick was installed via macports too, it's executables are  
> outside the
> default path (which seems to be only /bin:/sbin:/usr/bin:/usr/sbin)  
> and I need
> to be able to set apache's running path. Can Anyone please help?

Can you just specify the absolute path to ImageMagick? It works for me:


<html>
<head>
<title>identify</title>
</head>
<body>
<?php

exec("/opt/local/bin/identify 2>&1", $output, $error_code);
if ($error_code) {
	"Error $error_code occurred<br />\n";
}
echo nl2br(htmlspecialchars(implode("\n", $output)));

?>
</body>
</html>




From raimue at macports.org  Wed Jan  7 23:55:04 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Thu, 08 Jan 2009 08:55:04 +0100
Subject: apache2 env path
In-Reply-To: <loom.20090106T152350-866@post.gmane.org>
References: <loom.20090106T152350-866@post.gmane.org>
Message-ID: <4965B158.8020400@macports.org>

sheldon wrote:
> I'm using apache2 installed and running via macports in /opt/local. I'm using
> php to run a exec() function via a script and would like to set the path apache
> has access to so I can run ImageMagick commands to convert images via php. Since
> ImageMagick was installed via macports too, it's executables are outside the
> default path (which seems to be only /bin:/sbin:/usr/bin:/usr/sbin) and I need
> to be able to set apache's running path. Can Anyone please help?

Try to set PATH including /opt/local/bin in the httpd.conf for the
corresponding vhost (or even global).

See <http://httpd.apache.org/docs/2.2/mod/mod_env.html#setenv>

HTH,
Rainer

From sheldon at oneblackbear.com  Thu Jan  8 02:53:01 2009
From: sheldon at oneblackbear.com (sheldon)
Date: Thu, 8 Jan 2009 10:53:01 +0000 (UTC)
Subject: apache2 env path
References: <loom.20090106T152350-866@post.gmane.org>
	<BDB601EB-2AF0-4EA0-A542-4BB344D8A785@macports.org>
Message-ID: <loom.20090108T104831-550@post.gmane.org>

Ryan Schmidt <ryandesign <at> macports.org> writes:

> exec("/opt/local/bin/identify 2>&1", $output, $error_code);

Thanks for the idea, it does work if I use an absolute path.

Unfortunately this approach isn't very practical since it would
hard code the path to Imagemagick in my web framework. It would
mean having to change that path each time I deploy to a different
server. I know it's being a bit anal since this does actually work,
but with no way to amend the path externally it would make deployment
a nightmare.


From sheldon at oneblackbear.com  Thu Jan  8 02:56:23 2009
From: sheldon at oneblackbear.com (sheldon)
Date: Thu, 8 Jan 2009 10:56:23 +0000 (UTC)
Subject: apache2 env path
References: <loom.20090106T152350-866@post.gmane.org>
	<4965B158.8020400@macports.org>
Message-ID: <loom.20090108T105329-634@post.gmane.org>

Rainer M?ller <raimue <at> macports.org> writes:

> Try to set PATH including /opt/local/bin in the httpd.conf for the
> corresponding vhost (or even global).
> 
> See <http://httpd.apache.org/docs/2.2/mod/mod_env.html#setenv>
> 
> HTH,
> Rainer

Thanks for the idea, I've tried this approach. Unfortunately it seems to have
no effect on the path that mod_php actually sees. I'm not sure if it's an apache
security thing or something else.

Is there any chance anyone would know why this wouldn't work?

SetEnv PATH $PATH:/opt/local/bin


From whodoctor at gmail.com  Thu Jan  8 06:20:10 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Thu, 8 Jan 2009 08:20:10 -0600
Subject: Claws-mail port question
In-Reply-To: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>
References: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>
Message-ID: <4b75340e0901080620j29c62f77i7efdef3c9908db3@mail.gmail.com>

Anyone??


On Mon, Jan 5, 2009 at 11:10 AM, Doctor Who <whodoctor at gmail.com> wrote:
> Not sure if this is the right list, so let me know if this is not the
> case.  I installed MacPorts yesterday and used it to install
> claws-mail from ports.
>
> Everything went well with the install, and I can launch claws-mail and
> view messages, etc.
>
> However, only a few plugins appear to be built.  I don't have plugins
> for gtkhtml2-viewer or attach_reminder, for example.
>
> There is not a separate port for the plugins that I can see.  And
> there is no maintainer listed on the ports.
>
> I'm hoping someone can help me with this.
>
> Thanks!
>

From protsman at mac.com  Thu Jan  8 08:44:35 2009
From: protsman at mac.com (Shawn Protsman)
Date: Thu, 08 Jan 2009 08:44:35 -0800
Subject: Perl 5.8.9 port activation failed
Message-ID: <87DCEFCA-7115-4951-9696-2FDEF82E3B51@mac.com>

This repeats a number of times.

The MacPorts installation is not outdated so it was not updated
--->  Activating perl5.8 @5.8.9_1
Error: Activating perl5.8 @5.8.9_1 failed: Image error: /opt/local/bin/ 
corelist already exists and does not belong to a registered port.   
Unable to activate port perl5.8.
--->  Activating perl5.8 @5.8.9_1


How can I resolve this issue?

From macsforever2000 at macports.org  Thu Jan  8 08:51:23 2009
From: macsforever2000 at macports.org (Frank Schima)
Date: Thu, 8 Jan 2009 09:51:23 -0700
Subject: Perl 5.8.9 port activation failed
In-Reply-To: <87DCEFCA-7115-4951-9696-2FDEF82E3B51@mac.com>
References: <87DCEFCA-7115-4951-9696-2FDEF82E3B51@mac.com>
Message-ID: <D080BFC9-A122-4430-894D-576B8E40CD0E@macports.org>

Hi Shawn,


On Jan 8, 2009, at 9:44 AM, Shawn Protsman wrote:

> This repeats a number of times.
>
> The MacPorts installation is not outdated so it was not updated
> --->  Activating perl5.8 @5.8.9_1
> Error: Activating perl5.8 @5.8.9_1 failed: Image error: /opt/local/ 
> bin/corelist already exists and does not belong to a registered  
> port.  Unable to activate port perl5.8.
> --->  Activating perl5.8 @5.8.9_1
>
>
> How can I resolve this issue?

Just force the activate:

sudo port -f activate perl5.8

You must have encountered an error of some kind in the past which left  
the files installed but not in the registry.


Cheers!
Frank


From olaf at foellinger.de  Thu Jan  8 09:58:23 2009
From: olaf at foellinger.de (Olaf Foellinger)
Date: Thu, 8 Jan 2009 18:58:23 +0100
Subject: GnuCash packaging
In-Reply-To: <1d6843d80901071509m4aec083ehe6251cb13e793dc7@mail.gmail.com>
References: <1d6843d80901010157j7c96838ax32a1f2e5c7425320@mail.gmail.com>
	<3597B56E-4D25-41AF-8F71-8A0810DC46A9@cogs.com>
	<495ED53F.2020303@macports.org>
	<1d6843d80901022224k3a831e91g8d95a8f6ba2861dc@mail.gmail.com>
	<55476680-A7AE-4647-B851-97DEF60F5C21@macports.org>
	<4960AAFE.9080305@macports.org>
	<1d6843d80901041613k4f4d781xc19f9fa1a45ff1c7@mail.gmail.com>
	<20090107080615.GA22981@foellinger.de>
	<1d6843d80901071509m4aec083ehe6251cb13e793dc7@mail.gmail.com>
Message-ID: <20090108175823.GA29364@foellinger.de>

* Charles Day <cedayiv at gmail.com> [08.01.09 08:23]wrote:

>    On Wed, Jan 7, 2009 at 12:06 AM, Olaf Foellinger
>    <[1]olaf at foellinger.de> wrote:
> 
>      Hi,
>      * Charles Day <[2]cedayiv at gmail.com> [05.01.09 01:14]wrote:
> 
>    >    Maybe not too many care about building them, but a lot care about
>    >    distributing them once they are built. A distribution of GnuCash
>    for
>    >    Mac in binary form is one of the more requested features
>    (especially
>    >    recently) I see as a GnuCash developer. Going through the steps of
>    >    installing GnuCash via MacPorts or Fink is unfortunately beyond
>    what
>    >    many users are able or willing to do.
>    >    So that's why I'm looking into building a binary...
> 
>      the OS X native Gimp.app has been built based on MacPorts IIRC.
>      Maybe
>      that's another good starting point for the goal.
> 
>    I don't know if this is up to date, but I found a procedure for
>    building a Gimp .app using MacPorts:
>    [3]http://darwingimp.sourceforge.net/buildgimp.html
>    This may give some interesting clues.

Yes, that was it what I was thinking of. Mixed it up.

Gru? Olaf

From devans at macports.org  Thu Jan  8 10:17:33 2009
From: devans at macports.org (David Evans)
Date: Thu, 08 Jan 2009 10:17:33 -0800
Subject: ufraw Not Build
In-Reply-To: <4963DFD6.3090402@GmAiL.cOm>
References: <4963DFD6.3090402@GmAiL.cOm>
Message-ID: <4966433D.4080402@macports.org>

Altoine Barker wrote:
> /usr/bin/g++-4.0  -O2   -L/opt/local/lib -o ufraw ufraw.o libufraw.a
> -R/opt/local/lib -Wl,-framework -Wl,CoreFoundation -L/opt/local/lib
> -lexiv2 -lintl -lc -liconv -lz -lexpat   -L/opt/local/lib -lglib-2.0
> -lintl -liconv   -L/opt/local/lib -llcms    -L/opt/local/lib -lpng12 -lz
>   -L/opt/local/lib -lgtkimageview -lgtk-quartz-2.0 -lgdk-quartz-2.0
> -latk-1.0 -lgio-2.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo
> -lpangoft2-1.0 -lpango-1.0 -lm -lpixman-1 -lfontconfig -lexpat
> -lfreetype -lpng12 -lz -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl
> -liconv   -ltiff -ljpeg -lbz2 -lz  -lintl
> Undefined symbols:
>   "_CMCloseProfile", referenced from:
>       _uf_get_display_profile in libufraw.a(uf_gtk.o)
>   "_CMFlattenProfile", referenced from:
>       _uf_get_display_profile in libufraw.a(uf_gtk.o)
>   "_CMGetProfileByAVID", referenced from:
>       _uf_get_display_profile in libufraw.a(uf_gtk.o)
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[2]: *** [ufraw] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> Warning: the following items did not execute (for ufraw):
> org.macports.destroot org.macports.build
> Error: Unable to upgrade port: 1
> </snip>
>
> I upgraded my XCode SDK to XCode 3.1.2 and the problem is the same. TIA
>
> -Altoine
>
Altoine -

>From this I assume that you are building against gtk2 +quartz variant as
the code referenced above is
only built in that case.   The offending symbols are from ColorSync Manager
provided by the ApplicationServices framework which is not referenced by
this link
command.

I just tried building the current ufraw port (0.15) in the gtk2 +quartz
environment
and was unable to reproduce your problem.  The corresponding link command
included the ApplicationServices framework.

So I wonder if you are using the latest version of ufraw?

Please try

sudo port selfupdate
sudo port clean --all ufraw
sudo port upgrade ufraw

and see if you still have the problem.  If so you should probably file a
ticket against ufraw
citing the details.

Dave

From protsman at mac.com  Thu Jan  8 10:22:52 2009
From: protsman at mac.com (Shawn Protsman)
Date: Thu, 08 Jan 2009 10:22:52 -0800
Subject: Perl 5.8.9 port activation failed
In-Reply-To: <D080BFC9-A122-4430-894D-576B8E40CD0E@macports.org>
References: <87DCEFCA-7115-4951-9696-2FDEF82E3B51@mac.com>
	<D080BFC9-A122-4430-894D-576B8E40CD0E@macports.org>
Message-ID: <D6D855BB-D7C7-423D-9C56-771EAAA6A40A@mac.com>

On Jan 8, 2009, at 8:51 AM, Frank Schima wrote:

> sudo port -f activate perl5.8

Thanks for the tip, Frank. Unless I'm doing something wrong, it didn't  
work out for me:

@naiad ~] sudo port -f activate perl5.8
Password:
--->  The following versions of perl5.8 are currently installed:
--->  	perl5.8 @5.8.8_3+darwin_9
--->  	perl5.8 @5.8.9_1
Error: port activate failed: Registry error: Please specify the full  
version as recorded in the port registry.

@naiad ~] sudo port -f activate perl5.8.9_1
Error: port activate failed: Registry error: perl5.8.9_1 not  
registered as installed.

Ideas?

From devans at macports.org  Thu Jan  8 10:33:58 2009
From: devans at macports.org (David Evans)
Date: Thu, 08 Jan 2009 10:33:58 -0800
Subject: Perl 5.8.9 port activation failed
In-Reply-To: <D6D855BB-D7C7-423D-9C56-771EAAA6A40A@mac.com>
References: <87DCEFCA-7115-4951-9696-2FDEF82E3B51@mac.com>	<D080BFC9-A122-4430-894D-576B8E40CD0E@macports.org>
	<D6D855BB-D7C7-423D-9C56-771EAAA6A40A@mac.com>
Message-ID: <49664716.4030700@macports.org>

Shawn Protsman wrote:
> On Jan 8, 2009, at 8:51 AM, Frank Schima wrote:
>
>> sudo port -f activate perl5.8
>
> Thanks for the tip, Frank. Unless I'm doing something wrong, it didn't
> work out for me:
>
> @naiad ~] sudo port -f activate perl5.8
> Password:
> --->  The following versions of perl5.8 are currently installed:
> --->      perl5.8 @5.8.8_3+darwin_9
> --->      perl5.8 @5.8.9_1
> Error: port activate failed: Registry error: Please specify the full
> version as recorded in the port registry.
>
> @naiad ~] sudo port -f activate perl5.8.9_1
> Error: port activate failed: Registry error: perl5.8.9_1 not
> registered as installed.
>
> Ideas?
Try

sudo port -f activate perl5.8 @5.8.9_1

From protsman at mac.com  Thu Jan  8 10:34:56 2009
From: protsman at mac.com (Shawn Protsman)
Date: Thu, 08 Jan 2009 10:34:56 -0800
Subject: Perl 5.8.9 port activation failed
In-Reply-To: <D6D855BB-D7C7-423D-9C56-771EAAA6A40A@mac.com>
References: <87DCEFCA-7115-4951-9696-2FDEF82E3B51@mac.com>
	<D080BFC9-A122-4430-894D-576B8E40CD0E@macports.org>
	<D6D855BB-D7C7-423D-9C56-771EAAA6A40A@mac.com>
Message-ID: <B7F4690A-9CDC-4CE3-8FA2-FD3C3F6D0464@mac.com>

On Jan 8, 2009, at 10:22 AM, Shawn Protsman wrote:

> Thanks for the tip, Frank. Unless I'm doing something wrong, it  
> didn't work out for me:
>
> @naiad ~] sudo port -f activate perl5.8
> Password:
> --->  The following versions of perl5.8 are currently installed:
> --->  	perl5.8 @5.8.8_3+darwin_9
> --->  	perl5.8 @5.8.9_1
> Error: port activate failed: Registry error: Please specify the full  
> version as recorded in the port registry.
>
> @naiad ~] sudo port -f activate perl5.8.9_1
> Error: port activate failed: Registry error: perl5.8.9_1 not  
> registered as installed.
>
> Ideas?

I believe I figured it out:

@naiad ~] sudo port -f activate perl5.8 @5.8.9_1
Password:
--->  Activating perl5.8 @5.8.9_1
Warning: File /opt/local/bin/corelist already exists.  Moving to: /opt/ 
local/bin/corelist.mp_1231439641.


From lanceboyle at qwest.net  Thu Jan  8 10:44:23 2009
From: lanceboyle at qwest.net (Jerry)
Date: Thu, 8 Jan 2009 11:44:23 -0700
Subject: wxMaxima fails to install
Message-ID: <ACC64489-42ED-40EA-9AEB-1773F4D6B270@qwest.net>

Hi,

wxMaxima failed to install on my Powerbook, 10.4.11, while attempting  
a universal build. Below is the installation log followed by the  
crash report.

Any ideas?

Jerry




Port command started with PID 391
Fetching gperf
Attempting to fetch gperf-3.0.3.tar.gz from http://mirrors.kernel.org/ 
gnu/gperf
Verifying checksum(s) for gperf
Extracting gperf
Configuring gperf
Building gperf
Staging gperf into destroot
Installing gperf @3.0.3_0+universal
Activating gperf @3.0.3_0+universal
Cleaning gperf
Fetching libiconv
Attempting to fetch libiconv-1.12.tar.gz from http:// 
mirrors.kernel.org/gnu/libiconv
Verifying checksum(s) for libiconv
Extracting libiconv
Applying patches to libiconv
Configuring libiconv
Building libiconv
Staging libiconv into destroot
Installing libiconv @1.12_0+darwin_8+universal
Activating libiconv @1.12_0+darwin_8+universal
Cleaning libiconv
Fetching libsdl
Attempting to fetch SDL-1.2.13.tar.gz from http://www.libsdl.org/ 
release/
Verifying checksum(s) for libsdl
Extracting libsdl
Configuring libsdl
Building libsdl
Staging libsdl into destroot
Installing libsdl @1.2.13_2+darwin_8+universal
Activating libsdl @1.2.13_2+darwin_8+universal
Cleaning libsdl
Fetching zlib
Attempting to fetch zlib-1.2.3.tar.bz2 from http:// 
internap.dl.sourceforge.net/libpng
Verifying checksum(s) for zlib
Extracting zlib
Applying patches to zlib
Configuring zlib
Building zlib
Staging zlib into destroot
Installing zlib @1.2.3_2+universal
Activating zlib @1.2.3_2+universal
Cleaning zlib
Fetching libxml2
Attempting to fetch libxml2-2.7.2.tar.gz from http:// 
distfiles.macports.org/libxml2
Verifying checksum(s) for libxml2
Extracting libxml2
Configuring libxml2
Building libxml2
Staging libxml2 into destroot
Installing libxml2 @2.7.2_1+darwin_8+universal
Activating libxml2 @2.7.2_1+darwin_8+universal
Cleaning libxml2
Fetching aquaterm
Attempting to fetch aquaterm_src.1.0.1.tar.gz from http:// 
voxel.dl.sourceforge.net/aquaterm
Verifying checksum(s) for aquaterm
Extracting aquaterm
Applying patches to aquaterm
Configuring aquaterm
Building aquaterm
Staging aquaterm into destroot
Installing aquaterm @1.0.1_3+universal
Activating aquaterm @1.0.1_3+universal
Cleaning aquaterm
Fetching expat
Attempting to fetch expat-2.0.1.tar.gz from http:// 
internap.dl.sourceforge.net/expat
Verifying checksum(s) for expat
Extracting expat
Configuring expat
Building expat
Staging expat into destroot
Installing expat @2.0.1_0+universal
Activating expat @2.0.1_0+universal
Cleaning expat
Fetching freetype
Attempting to fetch freetype-2.3.7.tar.bz2 from http:// 
internap.dl.sourceforge.net/freetype
Attempting to fetch freetype-doc-2.3.7.tar.bz2 from http:// 
internap.dl.sourceforge.net/freetype
Verifying checksum(s) for freetype
Extracting freetype
Applying patches to freetype
Configuring freetype
Building freetype
Staging freetype into destroot
Installing freetype @2.3.7_3+macosx+universal
Activating freetype @2.3.7_3+macosx+universal
Cleaning freetype
Fetching fontconfig
Attempting to fetch fontconfig-2.6.0.tar.gz from http:// 
distfiles.macports.org/fontconfig
Verifying checksum(s) for fontconfig
Extracting fontconfig
Configuring fontconfig
Building fontconfig
Staging fontconfig into destroot
Installing fontconfig @2.6.0_1+macosx+universal
Activating fontconfig @2.6.0_1+macosx+universal
Cleaning fontconfig
Fetching ncursesw
Attempting to fetch ncurses-5.7.tar.gz from http://mirrors.kernel.org/ 
gnu/ncurses
Verifying checksum(s) for ncursesw
Extracting ncursesw
Configuring ncursesw
Building ncursesw
Staging ncursesw into destroot
Installing ncursesw @5.7_0+universal
Activating ncursesw @5.7_0+universal
Cleaning ncursesw
Fetching ncurses
Verifying checksum(s) for ncurses
Extracting ncurses
Configuring ncurses
Building ncurses
Staging ncurses into destroot
Installing ncurses @5.7_0+universal
Activating ncurses @5.7_0+universal
Cleaning ncurses
Fetching gettext
Attempting to fetch gettext-0.17.tar.gz from http:// 
mirrors.kernel.org/gnu/gettext
Verifying checksum(s) for gettext
Extracting gettext
Applying patches to gettext
Configuring gettext
Building gettext
Staging gettext into destroot
Installing gettext @0.17_3+universal
Activating gettext @0.17_3+universal
Cleaning gettext
Fetching perl5.8
Attempting to fetch perl-5.8.9.tar.bz2 from http:// 
distfiles.macports.org/perl5.8
Verifying checksum(s) for perl5.8
Extracting perl5.8
Configuring perl5.8
Building perl5.8
Staging perl5.8 into destroot
Installing perl5.8 @5.8.9_1
Activating perl5.8 @5.8.9_1
Cleaning perl5.8
Fetching perl5
Verifying checksum(s) for perl5
Extracting perl5
Configuring perl5
Building perl5
Staging perl5 into destroot
Installing perl5 @5.8.9_0
Activating perl5 @5.8.9_0
Cleaning perl5
Fetching p5-locale-gettext
Attempting to fetch gettext-1.05.tar.gz from ftp:// 
ftp.cs.colorado.edu/pub/perl/CPAN/modules/by-module/Locale
Verifying checksum(s) for p5-locale-gettext
Extracting p5-locale-gettext
Applying patches to p5-locale-gettext
Configuring p5-locale-gettext
Building p5-locale-gettext
Staging p5-locale-gettext into destroot
Installing p5-locale-gettext @1.05_0+universal
Activating p5-locale-gettext @1.05_0+universal
Cleaning p5-locale-gettext
Fetching help2man
Attempting to fetch help2man-1.36.4.tar.gz from http:// 
mirrors.kernel.org/gnu/help2man
Verifying checksum(s) for help2man
Extracting help2man
Applying patches to help2man
Configuring help2man
Building help2man
Staging help2man into destroot
Installing help2man @1.36.4_1+universal
Activating help2man @1.36.4_1+universal
Cleaning help2man
Fetching m4
Attempting to fetch m4-1.4.12.tar.bz2 from http://mirrors.kernel.org/ 
gnu/m4
Verifying checksum(s) for m4
Extracting m4
Applying patches to m4
Configuring m4
Building m4
Staging m4 into destroot
Installing m4 @1.4.12_1+universal
Activating m4 @1.4.12_1+universal
Cleaning m4
Fetching autoconf
Attempting to fetch autoconf-2.63.tar.bz2 from http:// 
mirrors.kernel.org/gnu/autoconf
Verifying checksum(s) for autoconf
Extracting autoconf
Configuring autoconf
Building autoconf
Staging autoconf into destroot
Installing autoconf @2.63_0+universal
Activating autoconf @2.63_0+universal
Cleaning autoconf
Fetching automake
Attempting to fetch automake-1.10.2.tar.bz2 from http:// 
mirrors.kernel.org/gnu/automake
Verifying checksum(s) for automake
Extracting automake
Configuring automake
Building automake
Staging automake into destroot
Installing automake @1.10.2_0+universal
Activating automake @1.10.2_0+universal
Cleaning automake
Fetching jpeg
Attempting to fetch jpegsrc.v6b.tar.gz from http:// 
distfiles.macports.org/jpeg
Attempting to fetch droppatch.tar.gz from http:// 
distfiles.macports.org/jpeg
Verifying checksum(s) for jpeg
Extracting jpeg
Applying patches to jpeg
Configuring jpeg
Building jpeg
Staging jpeg into destroot
Installing jpeg @6b_3+universal
Activating jpeg @6b_3+universal
Cleaning jpeg
Fetching libpng
Attempting to fetch libpng-1.2.34.tar.bz2 from http:// 
internap.dl.sourceforge.net/libpng
Verifying checksum(s) for libpng
Extracting libpng
Configuring libpng
Building libpng
Staging libpng into destroot
Installing libpng @1.2.34_0+universal
Activating libpng @1.2.34_0+universal
Cleaning libpng
Fetching libtool
Attempting to fetch libtool-2.2.6a.tar.gz from http:// 
mirrors.kernel.org/gnu/libtool
Verifying checksum(s) for libtool
Extracting libtool
Configuring libtool
Building libtool
Staging libtool into destroot
Installing libtool @2.2.6a_0+universal
Activating libtool @2.2.6a_0+universal
Cleaning libtool
Fetching gd2
Attempting to fetch gd-2.0.35.tar.bz2 from http:// 
distfiles.macports.org/gd2
Verifying checksum(s) for gd2
Extracting gd2
Applying patches to gd2
Configuring gd2
Building gd2
Staging gd2 into destroot
Installing gd2 @2.0.35_2+universal
Activating gd2 @2.0.35_2+universal
Cleaning gd2
Fetching pdflib
Attempting to fetch PDFlib-Lite-7.0.3.tar.gz from http:// 
www.pdflib.com/binaries/PDFlib/703/
Verifying checksum(s) for pdflib
Extracting pdflib
Applying patches to pdflib
Configuring pdflib
Building pdflib
Staging pdflib into destroot
Installing pdflib @7.0.3_3+darwin_8+universal
Activating pdflib @7.0.3_3+darwin_8+universal
Cleaning pdflib
Fetching readline
Attempting to fetch readline52-001 from http://mirrors.kernel.org/gnu/ 
readline/readline-5.2-patches/
Attempting to fetch readline52-002 from http://mirrors.kernel.org/gnu/ 
readline/readline-5.2-patches/
Attempting to fetch readline52-003 from http://mirrors.kernel.org/gnu/ 
readline/readline-5.2-patches/
Attempting to fetch readline52-004 from http://mirrors.kernel.org/gnu/ 
readline/readline-5.2-patches/
Attempting to fetch readline52-005 from http://mirrors.kernel.org/gnu/ 
readline/readline-5.2-patches/
Attempting to fetch readline52-006 from http://mirrors.kernel.org/gnu/ 
readline/readline-5.2-patches/
Attempting to fetch readline52-007 from http://mirrors.kernel.org/gnu/ 
readline/readline-5.2-patches/
Attempting to fetch readline52-008 from http://mirrors.kernel.org/gnu/ 
readline/readline-5.2-patches/
Attempting to fetch readline52-009 from http://mirrors.kernel.org/gnu/ 
readline/readline-5.2-patches/
Attempting to fetch readline52-010 from http://mirrors.kernel.org/gnu/ 
readline/readline-5.2-patches/
Attempting to fetch readline52-011 from http://mirrors.kernel.org/gnu/ 
readline/readline-5.2-patches/
Attempting to fetch readline52-012 from http://mirrors.kernel.org/gnu/ 
readline/readline-5.2-patches/
Attempting to fetch readline-5.2.tar.gz from http:// 
mirrors.kernel.org/gnu/readline
Verifying checksum(s) for readline
Extracting readline
Applying patches to readline
Configuring readline
Building readline
Staging readline into destroot
Installing readline @5.2.012_1+universal
Activating readline @5.2.012_1+universal
Cleaning readline
Fetching gnuplot
Attempting to fetch gnuplot-4.2.4.tar.gz from http:// 
internap.dl.sourceforge.net/gnuplot
Attempting to fetch gnuplot.pdf from http:// 
internap.dl.sourceforge.net/gnuplot
Verifying checksum(s) for gnuplot
Extracting gnuplot
Applying patches to gnuplot
Configuring gnuplot
Building gnuplot
Staging gnuplot into destroot
Installing gnuplot @4.2.4_0+universal
Activating gnuplot @4.2.4_0+universal
Cleaning gnuplot
Fetching recode
Attempting to fetch recode-3.6.tar.gz from http://mirrors.kernel.org/ 
gnu/recode
Verifying checksum(s) for recode
Extracting recode
Applying patches to recode
Configuring recode
Building recode
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_textpro 
c_recode/work/recode-3.6" && make all " returned error 2
Command output: /bin/sh ../libtool --mode=compile /usr/bin/gcc-4.0 - 
DLIBDIR=\"/opt/local/lib\" -DHAVE_CONFIG_H -I.. -I. -I../lib -I../ 
libiconv  -I/opt/local/include -isysroot /Developer/SDKs/ 
MacOSX10.4u.sdk  -O2 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch  
ppc -arch i386 -c quoted.c
/
usr/bin/gcc-4.0 -DLIBDIR=\"/opt/local/lib\" -DHAVE_CONFIG_H -I.. -I. - 
I../lib -I../libiconv -I/opt/local/include -isysroot /Developer/SDKs/ 
MacOSX10.4u.sdk -O2 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch  
ppc -arch i386 -c quoted.c -o quoted.o
echo timestamp > quoted.lo
/bin/sh ../libtool --mode=link /usr/bin/gcc-4.0  -O2 -isysroot / 
Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386 -L/opt/local/lib - 
Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386 - 
o librecode.la -rpath /opt/local/lib -version-info 0:0:0 argmatch.lo  
charname.lo combine.lo fr-charname.lo hash.lo iconv.lo libiconv.lo  
localcharset.lo merged.lo names.lo outer.lo quotearg.lo recode.lo  
request.lo strip-pool.lo task.lo xmalloc.lo african.lo afrtran.lo  
applemac.lo atarist.lo bangbang.lo cdcnos.lo ebcdic.lo ibmpc.lo  
iconqnx.lo lat1asci.lo mule.lo strip-data.lo testdump.lo ucs.lo  
utf16.lo utf7.lo utf8.lo varia.lo vn.lo flat.lo html.lo lat1ltex.lo  
lat1txte.lo rfc1345.lo texinfo.lo base64.lo dump.lo endline.lo  
permut.lo quoted.lo
mkdir .libs
ar cru .libs/librecode.a  argmatch.o charname.o combine.o fr- 
charname.o hash.o iconv.o libiconv.o localcharset.o merged.o names.o  
outer.o quotearg.o recode.o request.o strip-pool.o task.o xmalloc.o  
african.o afrtran.o applemac.o atarist.o bangbang.o cdcnos.o ebcdic.o  
ibmpc.o iconqnx.o lat1asci.o mule.o strip-data.o testdump.o ucs.o  
utf16.o utf7.o utf8.o varia.o vn.o flat.o html.o lat1ltex.o  
lat1txte.o rfc1345.o texinfo.o base64.o dump.o endline.o permut.o  
quoted.o
ranlib .libs/librecode.a
creating librecode.la
(cd .libs && rm -f librecode.la && ln -s ../librecode.la librecode.la)
/usr/bin/gcc-4.0 -DLIBDIR=\"/opt/local/lib\" -DHAVE_CONFIG_H -I.. -I.  
-I../lib -I../libiconv  -I/opt/local/include -isysroot /Developer/ 
SDKs/MacOSX10.4u.sdk  -O2 -isysroot /Developer/SDKs/MacOSX10.4u.sdk - 
arch ppc -arch i386 -c main.c
/usr/bin/gcc-4.0 -DLIBDIR=\"/opt/local/lib\" -DHAVE_CONFIG_H -I.. -I.  
-I../lib -I../libiconv  -I/opt/local/include -isysroot /Developer/ 
SDKs/MacOSX10.4u.sdk  -O2 -isysroot /Developer/SDKs/MacOSX10.4u.sdk - 
arch ppc -arch i386 -c freeze.c
/usr/bin/gcc-4.0 -DLIBDIR=\"/opt/local/lib\" -DHAVE_CONFIG_H -I.. -I.  
-I../lib -I../libiconv  -I/opt/local/include -isysroot /Developer/ 
SDKs/MacOSX10.4u.sdk  -O2 -isysroot /Developer/SDKs/MacOSX10.4u.sdk - 
arch ppc -arch i386 -c mixed.c
/bin/sh ../libtool --mode=link /usr/bin/gcc-4.0  -O2 -isysroot / 
Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386 -L/opt/local/lib - 
Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386 - 
o recode  main.o freeze.o mixed.o librecode.la ../lib/libreco.a
/usr/bin/gcc-4.0 -O2 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch  
ppc -arch i386 -L/opt/local/lib -Wl,-syslibroot,/Developer/SDKs/ 
MacOSX10.4u.sdk -arch ppc -arch i386 -o recode main.o freeze.o  
mixed.o .libs/librecode.a ../lib/libreco.a
/usr/bin/ld: for architecture i386
/usr/bin/ld: Undefined symbols:
_libintl_bindtextdomain
_libintl_gettext
_libintl_textdomain
collect2: ld returned 1 exit status
/usr/bin/ld: for architecture ppc
/usr/bin/ld: Undefined symbols:
_libintl_bindtextdomain
_libintl_gettext
_libintl_textdomain
collect2: ld returned 1 exit status
lipo: can't open input file: /var/tmp//ccYkcFNd.out (No such file or  
directory)
make[2]: *** [recode] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive-am] Error 2
Error: The following dependencies failed to build: maxima recode sbcl  
wxWidgets libsdl_mixer libogg libvorbis pkgconfig smpeg tiff
Error: Status 1 encountered during processing.
Executing: /opt/local/bin/port install wxMaxima +universal














Date/Time:      2009-01-08 03:36:47.707 -0700
OS Version:     10.4.11 (Build 8S165)
Report Version: 4

Command: conftest
Path:    ./conftest
Parent:  sh [9886]

Version: ??? (???)

PID:    9887
Thread: 0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_INVALID_ADDRESS (0x0001) at 0xbf7ffff8

Thread 0 Crashed:
0   conftest 	0x00001d34 recurse_1 + 4
1   conftest 	0x00001d64 recurse_1 + 52
2   conftest 	0x00001d64 recurse_1 + 52
3   conftest 	0x00001d64 recurse_1 + 52
4   conftest 	0x00001d64 recurse_1 + 52
5   conftest 	0x00001d64 recurse_1 + 52
6   conftest 	0x00001d64 recurse_1 + 52
7   conftest 	0x00001d64 recurse_1 + 52
8   conftest 	0x00001d64 recurse_1 + 52
9   conftest 	0x00001d64 recurse_1 + 52
10  conftest 	0x00001d64 recurse_1 + 52
11  conftest 	0x00001d64 recurse_1 + 52
12  conftest 	0x00001d64 recurse_1 + 52
13  conftest 	0x00001d64 recurse_1 + 52
14  conftest 	0x00001d64 recurse_1 + 52
15  conftest 	0x00001d64 recurse_1 + 52
16  conftest 	0x00001d64 recurse_1 + 52
17  conftest 	0x00001d64 recurse_1 + 52
18  conftest 	0x00001d64 recurse_1 + 52
19  conftest 	0x00001d64 recurse_1 + 52
20  conftest 	0x00001d64 recurse_1 + 52
21  conftest 	0x00001d64 recurse_1 + 52
22  conftest 	0x00001d64 recurse_1 + 52
23  conftest 	0x00001d64 recurse_1 + 52
24  conftest 	0x00001d64 recurse_1 + 52
25  conftest 	0x00001d64 recurse_1 + 52
26  conftest 	0x00001d64 recurse_1 + 52
27  conftest 	0x00001d64 recurse_1 + 52
28  conftest 	0x00001d64 recurse_1 + 52
29  conftest 	0x00001d64 recurse_1 + 52
30  conftest 	0x00001d64 recurse_1 + 52
31  conftest 	0x00001d64 recurse_1 + 52
32  conftest 	0x00001d64 recurse_1 + 52
33  conftest 	0x00001d64 recurse_1 + 52
34  conftest 	0x00001d64 recurse_1 + 52
35  conftest 	0x00001d64 recurse_1 + 52
36  conftest 	0x00001d64 recurse_1 + 52
37  conftest 	0x00001d64 recurse_1 + 52
38  conftest 	0x00001d64 recurse_1 + 52
39  conftest 	0x00001d64 recurse_1 + 52
40  conftest 	0x00001d64 recurse_1 + 52
41  conftest 	0x00001d64 recurse_1 + 52
42  conftest 	0x00001d64 recurse_1 + 52
43  conftest 	0x00001d64 recurse_1 + 52
44  conftest 	0x00001d64 recurse_1 + 52
45  conftest 	0x00001d64 recurse_1 + 52
46  conftest 	0x00001d64 recurse_1 + 52
47  conftest 	0x00001d64 recurse_1 + 52
48  conftest 	0x00001d64 recurse_1 + 52
49  conftest 	0x00001d64 recurse_1 + 52
50  conftest 	0x00001d64 recurse_1 + 52
51  conftest 	0x00001d64 recurse_1 + 52
52  conftest 	0x00001d64 recurse_1 + 52
53  conftest 	0x00001d64 recurse_1 + 52
54  conftest 	0x00001d64 recurse_1 + 52
55  conftest 	0x00001d64 recurse_1 + 52
56  conftest 	0x00001d64 recurse_1 + 52
57  conftest 	0x00001d64 recurse_1 + 52
58  conftest 	0x00001d64 recurse_1 + 52
59  conftest 	0x00001d64 recurse_1 + 52
60  conftest 	0x00001d64 recurse_1 + 52
61  conftest 	0x00001d64 recurse_1 + 52
62  conftest 	0x00001d64 recurse_1 + 52
63  conftest 	0x00001d64 recurse_1 + 52
64  conftest 	0x00001d64 recurse_1 + 52
65  conftest 	0x00001d64 recurse_1 + 52
66  conftest 	0x00001d64 recurse_1 + 52
67  conftest 	0x00001d64 recurse_1 + 52
68  conftest 	0x00001d64 recurse_1 + 52
69  conftest 	0x00001d64 recurse_1 + 52
70  conftest 	0x00001d64 recurse_1 + 52
71  conftest 	0x00001d64 recurse_1 + 52
72  conftest 	0x00001d64 recurse_1 + 52
73  conftest 	0x00001d64 recurse_1 + 52
74  conftest 	0x00001d64 recurse_1 + 52
75  conftest 	0x00001d64 recurse_1 + 52
76  conftest 	0x00001d64 recurse_1 + 52
77  conftest 	0x00001d64 recurse_1 + 52
78  conftest 	0x00001d64 recurse_1 + 52
79  conftest 	0x00001d64 recurse_1 + 52
80  conftest 	0x00001d64 recurse_1 + 52
81  conftest 	0x00001d64 recurse_1 + 52
82  conftest 	0x00001d64 recurse_1 + 52
83  conftest 	0x00001d64 recurse_1 + 52
84  conftest 	0x00001d64 recurse_1 + 52
85  conftest 	0x00001d64 recurse_1 + 52
86  conftest 	0x00001d64 recurse_1 + 52
87  conftest 	0x00001d64 recurse_1 + 52
88  conftest 	0x00001d64 recurse_1 + 52
89  conftest 	0x00001d64 recurse_1 + 52
90  conftest 	0x00001d64 recurse_1 + 52
91  conftest 	0x00001d64 recurse_1 + 52
92  conftest 	0x00001d64 recurse_1 + 52
93  conftest 	0x00001d64 recurse_1 + 52
94  conftest 	0x00001d64 recurse_1 + 52
95  conftest 	0x00001d64 recurse_1 + 52
96  conftest 	0x00001d64 recurse_1 + 52
97  conftest 	0x00001d64 recurse_1 + 52
98  conftest 	0x00001d64 recurse_1 + 52
99  conftest 	0x00001d64 recurse_1 + 52
100 conftest 	0x00001d64 recurse_1 + 52
101 conftest 	0x00001d64 recurse_1 + 52
102 conftest 	0x00001d64 recurse_1 + 52
103 conftest 	0x00001d64 recurse_1 + 52
104 conftest 	0x00001d64 recurse_1 + 52
105 conftest 	0x00001d64 recurse_1 + 52
106 conftest 	0x00001d64 recurse_1 + 52
107 conftest 	0x00001d64 recurse_1 + 52
108 conftest 	0x00001d64 recurse_1 + 52
109 conftest 	0x00001d64 recurse_1 + 52
110 conftest 	0x00001d64 recurse_1 + 52
111 conftest 	0x00001d64 recurse_1 + 52
112 conftest 	0x00001d64 recurse_1 + 52
113 conftest 	0x00001d64 recurse_1 + 52
114 conftest 	0x00001d64 recurse_1 + 52
115 conftest 	0x00001d64 recurse_1 + 52
116 conftest 	0x00001d64 recurse_1 + 52
117 conftest 	0x00001d64 recurse_1 + 52
118 conftest 	0x00001d64 recurse_1 + 52
119 conftest 	0x00001d64 recurse_1 + 52
120 conftest 	0x00001d64 recurse_1 + 52
121 conftest 	0x00001d64 recurse_1 + 52
122 conftest 	0x00001d64 recurse_1 + 52
123 conftest 	0x00001d64 recurse_1 + 52
124 conftest 	0x00001d64 recurse_1 + 52
125 conftest 	0x00001d64 recurse_1 + 52
126 conftest 	0x00001d64 recurse_1 + 52
127 conftest 	0x00001d64 recurse_1 + 52
128 conftest 	0x00001d64 recurse_1 + 52
129 conftest 	0x00001d64 recurse_1 + 52
130 conftest 	0x00001d64 recurse_1 + 52
131 conftest 	0x00001d64 recurse_1 + 52
132 conftest 	0x00001d64 recurse_1 + 52
133 conftest 	0x00001d64 recurse_1 + 52
134 conftest 	0x00001d64 recurse_1 + 52
135 conftest 	0x00001d64 recurse_1 + 52
136 conftest 	0x00001d64 recurse_1 + 52
137 conftest 	0x00001d64 recurse_1 + 52
138 conftest 	0x00001d64 recurse_1 + 52
139 conftest 	0x00001d64 recurse_1 + 52
140 conftest 	0x00001d64 recurse_1 + 52
141 conftest 	0x00001d64 recurse_1 + 52
142 conftest 	0x00001d64 recurse_1 + 52
143 conftest 	0x00001d64 recurse_1 + 52
144 conftest 	0x00001d64 recurse_1 + 52
145 conftest 	0x00001d64 recurse_1 + 52
146 conftest 	0x00001d64 recurse_1 + 52
147 conftest 	0x00001d64 recurse_1 + 52
148 conftest 	0x00001d64 recurse_1 + 52
149 conftest 	0x00001d64 recurse_1 + 52
150 conftest 	0x00001d64 recurse_1 + 52
151 conftest 	0x00001d64 recurse_1 + 52
152 conftest 	0x00001d64 recurse_1 + 52
153 conftest 	0x00001d64 recurse_1 + 52
154 conftest 	0x00001d64 recurse_1 + 52
155 conftest 	0x00001d64 recurse_1 + 52
156 conftest 	0x00001d64 recurse_1 + 52
157 conftest 	0x00001d64 recurse_1 + 52
158 conftest 	0x00001d64 recurse_1 + 52
159 conftest 	0x00001d64 recurse_1 + 52
160 conftest 	0x00001d64 recurse_1 + 52
161 conftest 	0x00001d64 recurse_1 + 52
162 conftest 	0x00001d64 recurse_1 + 52
163 conftest 	0x00001d64 recurse_1 + 52
164 conftest 	0x00001d64 recurse_1 + 52
165 conftest 	0x00001d64 recurse_1 + 52
166 conftest 	0x00001d64 recurse_1 + 52
167 conftest 	0x00001d64 recurse_1 + 52
168 conftest 	0x00001d64 recurse_1 + 52
169 conftest 	0x00001d64 recurse_1 + 52
170 conftest 	0x00001d64 recurse_1 + 52
171 conftest 	0x00001d64 recurse_1 + 52
172 conftest 	0x00001d64 recurse_1 + 52
173 conftest 	0x00001d64 recurse_1 + 52
174 conftest 	0x00001d64 recurse_1 + 52
175 conftest 	0x00001d64 recurse_1 + 52
176 conftest 	0x00001d64 recurse_1 + 52
177 conftest 	0x00001d64 recurse_1 + 52
178 conftest 	0x00001d64 recurse_1 + 52
179 conftest 	0x00001d64 recurse_1 + 52
180 conftest 	0x00001d64 recurse_1 + 52
181 conftest 	0x00001d64 recurse_1 + 52
182 conftest 	0x00001d64 recurse_1 + 52
183 conftest 	0x00001d64 recurse_1 + 52
184 conftest 	0x00001d64 recurse_1 + 52
185 conftest 	0x00001d64 recurse_1 + 52
186 conftest 	0x00001d64 recurse_1 + 52
187 conftest 	0x00001d64 recurse_1 + 52
188 conftest 	0x00001d64 recurse_1 + 52
189 conftest 	0x00001d64 recurse_1 + 52
190 conftest 	0x00001d64 recurse_1 + 52
191 conftest 	0x00001d64 recurse_1 + 52
192 conftest 	0x00001d64 recurse_1 + 52
193 conftest 	0x00001d64 recurse_1 + 52
194 conftest 	0x00001d64 recurse_1 + 52
195 conftest 	0x00001d64 recurse_1 + 52
196 conftest 	0x00001d64 recurse_1 + 52
197 conftest 	0x00001d64 recurse_1 + 52
198 conftest 	0x00001d64 recurse_1 + 52
199 conftest 	0x00001d64 recurse_1 + 52
200 conftest 	0x00001d64 recurse_1 + 52
201 conftest 	0x00001d64 recurse_1 + 52
202 conftest 	0x00001d64 recurse_1 + 52
203 conftest 	0x00001d64 recurse_1 + 52
204 conftest 	0x00001d64 recurse_1 + 52
205 conftest 	0x00001d64 recurse_1 + 52
206 conftest 	0x00001d64 recurse_1 + 52
207 conftest 	0x00001d64 recurse_1 + 52
208 conftest 	0x00001d64 recurse_1 + 52
209 conftest 	0x00001d64 recurse_1 + 52
210 conftest 	0x00001d64 recurse_1 + 52
211 conftest 	0x00001d64 recurse_1 + 52
212 conftest 	0x00001d64 recurse_1 + 52
213 conftest 	0x00001d64 recurse_1 + 52
214 conftest 	0x00001d64 recurse_1 + 52
215 conftest 	0x00001d64 recurse_1 + 52
216 conftest 	0x00001d64 recurse_1 + 52
217 conftest 	0x00001d64 recurse_1 + 52
218 conftest 	0x00001d64 recurse_1 + 52
219 conftest 	0x00001d64 recurse_1 + 52
220 conftest 	0x00001d64 recurse_1 + 52
221 conftest 	0x00001d64 recurse_1 + 52
222 conftest 	0x00001d64 recurse_1 + 52
223 conftest 	0x00001d64 recurse_1 + 52
224 conftest 	0x00001d64 recurse_1 + 52
225 conftest 	0x00001d64 recurse_1 + 52
226 conftest 	0x00001d64 recurse_1 + 52
227 conftest 	0x00001d64 recurse_1 + 52
228 conftest 	0x00001d64 recurse_1 + 52
229 conftest 	0x00001d64 recurse_1 + 52
230 conftest 	0x00001d64 recurse_1 + 52
231 conftest 	0x00001d64 recurse_1 + 52
232 conftest 	0x00001d64 recurse_1 + 52
233 conftest 	0x00001d64 recurse_1 + 52
234 conftest 	0x00001d64 recurse_1 + 52
235 conftest 	0x00001d64 recurse_1 + 52
236 conftest 	0x00001d64 recurse_1 + 52
237 conftest 	0x00001d64 recurse_1 + 52
238 conftest 	0x00001d64 recurse_1 + 52
239 conftest 	0x00001d64 recurse_1 + 52
240 conftest 	0x00001d64 recurse_1 + 52
241 conftest 	0x00001d64 recurse_1 + 52
242 conftest 	0x00001d64 recurse_1 + 52
243 conftest 	0x00001d64 recurse_1 + 52
244 conftest 	0x00001d64 recurse_1 + 52
245 conftest 	0x00001d64 recurse_1 + 52
246 conftest 	0x00001d64 recurse_1 + 52
247 conftest 	0x00001d64 recurse_1 + 52
248 conftest 	0x00001d64 recurse_1 + 52
249 conftest 	0x00001d64 recurse_1 + 52
250 conftest 	0x00001d64 recurse_1 + 52
251 conftest 	0x00001d64 recurse_1 + 52
252 conftest 	0x00001d64 recurse_1 + 52
253 conftest 	0x00001d64 recurse_1 + 52
254 conftest 	0x00001d64 recurse_1 + 52
255 conftest 	0x00001d64 recurse_1 + 52
256 conftest 	0x00001d64 recurse_1 + 52
257 conftest 	0x00001d64 recurse_1 + 52
258 conftest 	0x00001d64 recurse_1 + 52
259 conftest 	0x00001d64 recurse_1 + 52
260 conftest 	0x00001d64 recurse_1 + 52
261 conftest 	0x00001d64 recurse_1 + 52
262 conftest 	0x00001d64 recurse_1 + 52
263 conftest 	0x00001d64 recurse_1 + 52
264 conftest 	0x00001d64 recurse_1 + 52
265 conftest 	0x00001d64 recurse_1 + 52
266 conftest 	0x00001d64 recurse_1 + 52
267 conftest 	0x00001d64 recurse_1 + 52
268 conftest 	0x00001d64 recurse_1 + 52
269 conftest 	0x00001d64 recurse_1 + 52
270 conftest 	0x00001d64 recurse_1 + 52
271 conftest 	0x00001d64 recurse_1 + 52
272 conftest 	0x00001d64 recurse_1 + 52
273 conftest 	0x00001d64 recurse_1 + 52
274 conftest 	0x00001d64 recurse_1 + 52
275 conftest 	0x00001d64 recurse_1 + 52
276 conftest 	0x00001d64 recurse_1 + 52
277 conftest 	0x00001d64 recurse_1 + 52
278 conftest 	0x00001d64 recurse_1 + 52
279 conftest 	0x00001d64 recurse_1 + 52
280 conftest 	0x00001d64 recurse_1 + 52
281 conftest 	0x00001d64 recurse_1 + 52
282 conftest 	0x00001d64 recurse_1 + 52
283 conftest 	0x00001d64 recurse_1 + 52
284 conftest 	0x00001d64 recurse_1 + 52
285 conftest 	0x00001d64 recurse_1 + 52
286 conftest 	0x00001d64 recurse_1 + 52
287 conftest 	0x00001d64 recurse_1 + 52
288 conftest 	0x00001d64 recurse_1 + 52
289 conftest 	0x00001d64 recurse_1 + 52
290 conftest 	0x00001d64 recurse_1 + 52
291 conftest 	0x00001d64 recurse_1 + 52
292 conftest 	0x00001d64 recurse_1 + 52
293 conftest 	0x00001d64 recurse_1 + 52
294 conftest 	0x00001d64 recurse_1 + 52
295 conftest 	0x00001d64 recurse_1 + 52
296 conftest 	0x00001d64 recurse_1 + 52
297 conftest 	0x00001d64 recurse_1 + 52
298 conftest 	0x00001d64 recurse_1 + 52
299 conftest 	0x00001d64 recurse_1 + 52
300 conftest 	0x00001d64 recurse_1 + 52
301 conftest 	0x00001d64 recurse_1 + 52
302 conftest 	0x00001d64 recurse_1 + 52
303 conftest 	0x00001d64 recurse_1 + 52
304 conftest 	0x00001d64 recurse_1 + 52
305 conftest 	0x00001d64 recurse_1 + 52
306 conftest 	0x00001d64 recurse_1 + 52
307 conftest 	0x00001d64 recurse_1 + 52
308 conftest 	0x00001d64 recurse_1 + 52
309 conftest 	0x00001d64 recurse_1 + 52
310 conftest 	0x00001d64 recurse_1 + 52
311 conftest 	0x00001d64 recurse_1 + 52
312 conftest 	0x00001d64 recurse_1 + 52
313 conftest 	0x00001d64 recurse_1 + 52
314 conftest 	0x00001d64 recurse_1 + 52
315 conftest 	0x00001d64 recurse_1 + 52
316 conftest 	0x00001d64 recurse_1 + 52
317 conftest 	0x00001d64 recurse_1 + 52
318 conftest 	0x00001d64 recurse_1 + 52
319 conftest 	0x00001d64 recurse_1 + 52
320 conftest 	0x00001d64 recurse_1 + 52
321 conftest 	0x00001d64 recurse_1 + 52
322 conftest 	0x00001d64 recurse_1 + 52
323 conftest 	0x00001d64 recurse_1 + 52
324 conftest 	0x00001d64 recurse_1 + 52
325 conftest 	0x00001d64 recurse_1 + 52
326 conftest 	0x00001d64 recurse_1 + 52
327 conftest 	0x00001d64 recurse_1 + 52
328 conftest 	0x00001d64 recurse_1 + 52
329 conftest 	0x00001d64 recurse_1 + 52
330 conftest 	0x00001d64 recurse_1 + 52
331 conftest 	0x00001d64 recurse_1 + 52
332 conftest 	0x00001d64 recurse_1 + 52
333 conftest 	0x00001d64 recurse_1 + 52
334 conftest 	0x00001d64 recurse_1 + 52
335 conftest 	0x00001d64 recurse_1 + 52
336 conftest 	0x00001d64 recurse_1 + 52
337 conftest 	0x00001d64 recurse_1 + 52
338 conftest 	0x00001d64 recurse_1 + 52
339 conftest 	0x00001d64 recurse_1 + 52
340 conftest 	0x00001d64 recurse_1 + 52
341 conftest 	0x00001d64 recurse_1 + 52
342 conftest 	0x00001d64 recurse_1 + 52
343 conftest 	0x00001d64 recurse_1 + 52
344 conftest 	0x00001d64 recurse_1 + 52
345 conftest 	0x00001d64 recurse_1 + 52
346 conftest 	0x00001d64 recurse_1 + 52
347 conftest 	0x00001d64 recurse_1 + 52
348 conftest 	0x00001d64 recurse_1 + 52
349 conftest 	0x00001d64 recurse_1 + 52
350 conftest 	0x00001d64 recurse_1 + 52
351 conftest 	0x00001d64 recurse_1 + 52
352 conftest 	0x00001d64 recurse_1 + 52
353 conftest 	0x00001d64 recurse_1 + 52
354 conftest 	0x00001d64 recurse_1 + 52
355 conftest 	0x00001d64 recurse_1 + 52
356 conftest 	0x00001d64 recurse_1 + 52
357 conftest 	0x00001d64 recurse_1 + 52
358 conftest 	0x00001d64 recurse_1 + 52
359 conftest 	0x00001d64 recurse_1 + 52
360 conftest 	0x00001d64 recurse_1 + 52
361 conftest 	0x00001d64 recurse_1 + 52
362 conftest 	0x00001d64 recurse_1 + 52
363 conftest 	0x00001d64 recurse_1 + 52
364 conftest 	0x00001d64 recurse_1 + 52
365 conftest 	0x00001d64 recurse_1 + 52
366 conftest 	0x00001d64 recurse_1 + 52
367 conftest 	0x00001d64 recurse_1 + 52
368 conftest 	0x00001d64 recurse_1 + 52
369 conftest 	0x00001d64 recurse_1 + 52
370 conftest 	0x00001d64 recurse_1 + 52
371 conftest 	0x00001d64 recurse_1 + 52
372 conftest 	0x00001d64 recurse_1 + 52
373 conftest 	0x00001d64 recurse_1 + 52
374 conftest 	0x00001d64 recurse_1 + 52
375 conftest 	0x00001d64 recurse_1 + 52
376 conftest 	0x00001d64 recurse_1 + 52
377 conftest 	0x00001d64 recurse_1 + 52
378 conftest 	0x00001d64 recurse_1 + 52
379 conftest 	0x00001d64 recurse_1 + 52
380 conftest 	0x00001d64 recurse_1 + 52
381 conftest 	0x00001d64 recurse_1 + 52
382 conftest 	0x00001d64 recurse_1 + 52
383 conftest 	0x00001d64 recurse_1 + 52
384 conftest 	0x00001d64 recurse_1 + 52
385 conftest 	0x00001d64 recurse_1 + 52
386 conftest 	0x00001d64 recurse_1 + 52
387 conftest 	0x00001d64 recurse_1 + 52
388 conftest 	0x00001d64 recurse_1 + 52
389 conftest 	0x00001d64 recurse_1 + 52
390 conftest 	0x00001d64 recurse_1 + 52
391 conftest 	0x00001d64 recurse_1 + 52
392 conftest 	0x00001d64 recurse_1 + 52
393 conftest 	0x00001d64 recurse_1 + 52
394 conftest 	0x00001d64 recurse_1 + 52
395 conftest 	0x00001d64 recurse_1 + 52
396 conftest 	0x00001d64 recurse_1 + 52
397 conftest 	0x00001d64 recurse_1 + 52
398 conftest 	0x00001d64 recurse_1 + 52
399 conftest 	0x00001d64 recurse_1 + 52
400 conftest 	0x00001d64 recurse_1 + 52
401 conftest 	0x00001d64 recurse_1 + 52
402 conftest 	0x00001d64 recurse_1 + 52
403 conftest 	0x00001d64 recurse_1 + 52
404 conftest 	0x00001d64 recurse_1 + 52
405 conftest 	0x00001d64 recurse_1 + 52
406 conftest 	0x00001d64 recurse_1 + 52
407 conftest 	0x00001d64 recurse_1 + 52
408 conftest 	0x00001d64 recurse_1 + 52
409 conftest 	0x00001d64 recurse_1 + 52
410 conftest 	0x00001d64 recurse_1 + 52
411 conftest 	0x00001d64 recurse_1 + 52
412 conftest 	0x00001d64 recurse_1 + 52
413 conftest 	0x00001d64 recurse_1 + 52
414 conftest 	0x00001d64 recurse_1 + 52
415 conftest 	0x00001d64 recurse_1 + 52
416 conftest 	0x00001d64 recurse_1 + 52
417 conftest 	0x00001d64 recurse_1 + 52
418 conftest 	0x00001d64 recurse_1 + 52
419 conftest 	0x00001d64 recurse_1 + 52
420 conftest 	0x00001d64 recurse_1 + 52
421 conftest 	0x00001d64 recurse_1 + 52
422 conftest 	0x00001d64 recurse_1 + 52
423 conftest 	0x00001d64 recurse_1 + 52
424 conftest 	0x00001d64 recurse_1 + 52
425 conftest 	0x00001d64 recurse_1 + 52
426 conftest 	0x00001d64 recurse_1 + 52
427 conftest 	0x00001d64 recurse_1 + 52
428 conftest 	0x00001d64 recurse_1 + 52
429 conftest 	0x00001d64 recurse_1 + 52
430 conftest 	0x00001d64 recurse_1 + 52
431 conftest 	0x00001d64 recurse_1 + 52
432 conftest 	0x00001d64 recurse_1 + 52
433 conftest 	0x00001d64 recurse_1 + 52
434 conftest 	0x00001d64 recurse_1 + 52
435 conftest 	0x00001d64 recurse_1 + 52
436 conftest 	0x00001d64 recurse_1 + 52
437 conftest 	0x00001d64 recurse_1 + 52
438 conftest 	0x00001d64 recurse_1 + 52
439 conftest 	0x00001d64 recurse_1 + 52
440 conftest 	0x00001d64 recurse_1 + 52
441 conftest 	0x00001d64 recurse_1 + 52
442 conftest 	0x00001d64 recurse_1 + 52
443 conftest 	0x00001d64 recurse_1 + 52
444 conftest 	0x00001d64 recurse_1 + 52
445 conftest 	0x00001d64 recurse_1 + 52
446 conftest 	0x00001d64 recurse_1 + 52
447 conftest 	0x00001d64 recurse_1 + 52
448 conftest 	0x00001d64 recurse_1 + 52
449 conftest 	0x00001d64 recurse_1 + 52
450 conftest 	0x00001d64 recurse_1 + 52
451 conftest 	0x00001d64 recurse_1 + 52
452 conftest 	0x00001d64 recurse_1 + 52
453 conftest 	0x00001d64 recurse_1 + 52
454 conftest 	0x00001d64 recurse_1 + 52
455 conftest 	0x00001d64 recurse_1 + 52
456 conftest 	0x00001d64 recurse_1 + 52
457 conftest 	0x00001d64 recurse_1 + 52
458 conftest 	0x00001d64 recurse_1 + 52
459 conftest 	0x00001d64 recurse_1 + 52
460 conftest 	0x00001d64 recurse_1 + 52
461 conftest 	0x00001d64 recurse_1 + 52
462 conftest 	0x00001d64 recurse_1 + 52
463 conftest 	0x00001d64 recurse_1 + 52
464 conftest 	0x00001d64 recurse_1 + 52
465 conftest 	0x00001d64 recurse_1 + 52
466 conftest 	0x00001d64 recurse_1 + 52
467 conftest 	0x00001d64 recurse_1 + 52
468 conftest 	0x00001d64 recurse_1 + 52
469 conftest 	0x00001d64 recurse_1 + 52
470 conftest 	0x00001d64 recurse_1 + 52
471 conftest 	0x00001d64 recurse_1 + 52
472 conftest 	0x00001d64 recurse_1 + 52
473 conftest 	0x00001d64 recurse_1 + 52
474 conftest 	0x00001d64 recurse_1 + 52
475 conftest 	0x00001d64 recurse_1 + 52
476 conftest 	0x00001d64 recurse_1 + 52
477 conftest 	0x00001d64 recurse_1 + 52
478 conftest 	0x00001d64 recurse_1 + 52
479 conftest 	0x00001d64 recurse_1 + 52
480 conftest 	0x00001d64 recurse_1 + 52
481 conftest 	0x00001d64 recurse_1 + 52
482 conftest 	0x00001d64 recurse_1 + 52
483 conftest 	0x00001d64 recurse_1 + 52
484 conftest 	0x00001d64 recurse_1 + 52
485 conftest 	0x00001d64 recurse_1 + 52
486 conftest 	0x00001d64 recurse_1 + 52
487 conftest 	0x00001d64 recurse_1 + 52
488 conftest 	0x00001d64 recurse_1 + 52
489 conftest 	0x00001d64 recurse_1 + 52
490 conftest 	0x00001d64 recurse_1 + 52
491 conftest 	0x00001d64 recurse_1 + 52
492 conftest 	0x00001d64 recurse_1 + 52
493 conftest 	0x00001d64 recurse_1 + 52
494 conftest 	0x00001d64 recurse_1 + 52
495 conftest 	0x00001d64 recurse_1 + 52
496 conftest 	0x00001d64 recurse_1 + 52
497 conftest 	0x00001d64 recurse_1 + 52
498 conftest 	0x00001d64 recurse_1 + 52
499 conftest 	0x00001d64 recurse_1 + 52
500 conftest 	0x00001d64 recurse_1 + 52
501 conftest 	0x00001d64 recurse_1 + 52
502 conftest 	0x00001d64 recurse_1 + 52
503 conftest 	0x00001d64 recurse_1 + 52
504 conftest 	0x00001d64 recurse_1 + 52
505 conftest 	0x00001d64 recurse_1 + 52
506 conftest 	0x00001d64 recurse_1 + 52
507 conftest 	0x00001d64 recurse_1 + 52
508 conftest 	0x00001d64 recurse_1 + 52

Thread 0 crashed with PPC Thread State 64:
   srr0: 0x0000000000001d34 srr1:  
0x000000000000d030                        vrsave: 0x0000000000000000
     cr: 0x22000424          xer: 0x0000000000000004   lr:  
0x0000000000001d64  ctr: 0x0000000090005de0
     r0: 0x0000000000001d64   r1: 0x00000000bf800000   r2:  
0x0000000000000000   r3: 0x000000000001997e
     r4: 0x00000000bffff798   r5: 0x00000000bffff738   r6:  
0x0000000000000000   r7: 0x0000000000000000
     r8: 0x000000008fe072a4   r9: 0x0000000000000000  r10:  
0x0000000000100000  r11: 0x00000000a0006110
    r12: 0x0000000090005de0  r13: 0x0000000000000000  r14:  
0x0000000000000000  r15: 0x0000000000000000
    r16: 0x0000000000000000  r17: 0x0000000000000000  r18:  
0x0000000000000000  r19: 0x0000000000000000
    r20: 0x0000000000000000  r21: 0x0000000000000000  r22:  
0x0000000000000000  r23: 0x0000000000000000
    r24: 0x0000000000000000  r25: 0x0000000000000001  r26:  
0x00000000bffff920  r27: 0x00000000bffff8b8
    r28: 0x00000000bffff8b0  r29: 0x0000000000001f5c  r30:  
0x00000000bffff798  r31: 0x0000000000001da4

Binary Images Description:
     0x1000 -     0x1fff conftest 	/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_m 
4/work/m4-1.4.12/conftest
0x8fe00000 - 0x8fe52fff dyld 46.16	/usr/lib/dyld
0x90000000 - 0x901bcfff libSystem.B.dylib 	/usr/lib/libSystem.B.dylib
0x90214000 - 0x90219fff libmathCommon.A.dylib 	/usr/lib/system/ 
libmathCommon.A.dylib
0x91433000 - 0x9143efff libgcc_s.1.dylib 	/usr/lib/libgcc_s.1.dylib

Model: PowerBook5,6, BootROM 4.9.1f3, 1 processors, PowerPC G4   
(1.2), 1.5 GHz, 2 GB
Graphics: ATI Mobility Radeon 9700, ATY,RV360M11, AGP, 64 MB
Memory Module: SODIMM0/J25LOWER, 1 GB, DDR SDRAM, PC2700U-25330
Memory Module: SODIMM1/J25UPPER, 1 GB, DDR SDRAM, PC2700U-25330
AirPort: AirPort Extreme, 405.1 (3.90.34.0.p18)
Modem: Jump, V.92, Version 1.0
Bluetooth: Version 1.9.5f4, 2 service, 0 devices, 1 incoming serial  
ports
Network Service: Built-in Ethernet, Ethernet, en0
PCI Card: TXN,PCIXXXX-00, cardbus, PC Card
Parallel ATA Device: MATSHITACD-RW  CW-8123
Parallel ATA Device: TOSHIBA MK8026GAX, 74.53 GB
USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/ 
sec, 500 mA
USB Device: Apple Internal Keyboard/Trackpad, Apple Computer, Up to  
12 Mb/sec, 500 mA
USB Device: CTE-430-UV3.1-4, WACOM, Up to 1.5 Mb/sec, 500 mA
FireWire Device: d2 Quadra (button), LaCie SA, Up to 800 Mb/sec
FireWire Device: LaCie d2 Extreme LUN 0, LaCie Group SA, Up to 800 Mb/ 
sec


From chomiak at charter.net  Thu Jan  8 11:33:11 2009
From: chomiak at charter.net (Cheryl Homiak)
Date: Thu, 8 Jan 2009 13:33:11 -0600 (CST)
Subject: Perl 5.8.9 port activation failed
In-Reply-To: <D6D855BB-D7C7-423D-9C56-771EAAA6A40A@mac.com>
References: <87DCEFCA-7115-4951-9696-2FDEF82E3B51@mac.com>
	<D080BFC9-A122-4430-894D-576B8E40CD0E@macports.org>
	<D6D855BB-D7C7-423D-9C56-771EAAA6A40A@mac.com>
Message-ID: <alpine.DEB.2.00.0901081329390.1632@maranatha.local>

This happened to me when I was upgrading installed. I finally just deleted 
the directory it was complaining about and then when I continued with the 
upgrade the directory was replaced and apparently registered. However, I 
realize if it doesn't work the resulting absence of a directory could 
cause problems with other programs. It did work for me though and I was 
able to finish the upgrade and everything works fine.


-- 
Cheryl

"Where your treasure is, there will your heart be also."


From vincent-opdarw at vinc17.org  Thu Jan  8 16:52:39 2009
From: vincent-opdarw at vinc17.org (Vincent Lefevre)
Date: Fri, 9 Jan 2009 01:52:39 +0100
Subject: Perl 5.8.9 port activation failed
In-Reply-To: <D080BFC9-A122-4430-894D-576B8E40CD0E@macports.org>
References: <87DCEFCA-7115-4951-9696-2FDEF82E3B51@mac.com>
	<D080BFC9-A122-4430-894D-576B8E40CD0E@macports.org>
Message-ID: <20090109005239.GH14649@prunille.vinc17.org>

On 2009-01-08 09:51:23 -0700, Frank Schima wrote:
> Hi Shawn,
>
> On Jan 8, 2009, at 9:44 AM, Shawn Protsman wrote:
>
>> This repeats a number of times.
>>
>> The MacPorts installation is not outdated so it was not updated
>> --->  Activating perl5.8 @5.8.9_1
>> Error: Activating perl5.8 @5.8.9_1 failed: Image error: /opt/local/ 
>> bin/corelist already exists and does not belong to a registered port.  
>> Unable to activate port perl5.8.
>> --->  Activating perl5.8 @5.8.9_1
>>
>> How can I resolve this issue?
>
> Just force the activate:
>
> sudo port -f activate perl5.8

Do NOT do that! Using -f can also hide other problems. It's much better
to remove the file and retry without -f.

-- 
Vincent Lef?vre <vincent at vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

From ryandesign at macports.org  Thu Jan  8 19:20:10 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 8 Jan 2009 21:20:10 -0600
Subject: wxMaxima fails to install
In-Reply-To: <ACC64489-42ED-40EA-9AEB-1773F4D6B270@qwest.net>
References: <ACC64489-42ED-40EA-9AEB-1773F4D6B270@qwest.net>
Message-ID: <9A133944-B28A-4FC5-9692-34AC5BF0B61C@macports.org>


On Jan 8, 2009, at 12:44, Jerry wrote:

> wxMaxima failed to install on my Powerbook, 10.4.11, while  
> attempting a universal build. Below is the installation log  
> followed by the crash report.

[snip]

> Fetching gettext
> Attempting to fetch gettext-0.17.tar.gz from http:// 
> mirrors.kernel.org/gnu/gettext
> Verifying checksum(s) for gettext
> Extracting gettext
> Applying patches to gettext
> Configuring gettext
> Building gettext
> Staging gettext into destroot
> Installing gettext @0.17_3+universal
> Activating gettext @0.17_3+universal
> Cleaning gettext

[snip]

> Fetching recode
> Attempting to fetch recode-3.6.tar.gz from http:// 
> mirrors.kernel.org/gnu/recode
> Verifying checksum(s) for recode
> Extracting recode
> Applying patches to recode
> Configuring recode
> Building recode
> Error: Target org.macports.build returned: shell command " cd "/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_textp 
> roc_recode/work/recode-3.6" && make all " returned error 2

[snip]

> /bin/sh ../libtool --mode=link /usr/bin/gcc-4.0  -O2 -isysroot / 
> Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386 -L/opt/local/ 
> lib -Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch  
> i386 -o recode  main.o freeze.o mixed.o librecode.la ../lib/libreco.a
> /usr/bin/gcc-4.0 -O2 -isysroot /Developer/SDKs/MacOSX10.4u.sdk - 
> arch ppc -arch i386 -L/opt/local/lib -Wl,-syslibroot,/Developer/ 
> SDKs/MacOSX10.4u.sdk -arch ppc -arch i386 -o recode main.o freeze.o  
> mixed.o .libs/librecode.a ../lib/libreco.a
> /usr/bin/ld: for architecture i386
> /usr/bin/ld: Undefined symbols:
> _libintl_bindtextdomain
> _libintl_gettext
> _libintl_textdomain
> collect2: ld returned 1 exit status
> /usr/bin/ld: for architecture ppc
> /usr/bin/ld: Undefined symbols:
> _libintl_bindtextdomain
> _libintl_gettext
> _libintl_textdomain
> collect2: ld returned 1 exit status
> lipo: can't open input file: /var/tmp//ccYkcFNd.out (No such file  
> or directory)
> make[2]: *** [recode] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all-recursive-am] Error 2


[snip]

This is either a problem in the recode port (it doesn't know how to  
find the functions gettext provides) or a problem in the gettext port  
(it doesn't provide the functions recode needs). I can try to look  
into this. To start with, I filed a ticket for the problem:

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



From ryandesign at macports.org  Thu Jan  8 19:35:47 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 8 Jan 2009 21:35:47 -0600
Subject: apache2 env path
In-Reply-To: <loom.20090108T105329-634@post.gmane.org>
References: <loom.20090106T152350-866@post.gmane.org>
	<4965B158.8020400@macports.org>
	<loom.20090108T105329-634@post.gmane.org>
Message-ID: <FE5B18FE-F51D-423D-8D5F-D57868641A22@macports.org>

On Jan 8, 2009, at 04:56, sheldon wrote:

> Rainer M?ller <raimue <at> macports.org> writes:
>
>> Try to set PATH including /opt/local/bin in the httpd.conf for the
>> corresponding vhost (or even global).
>>
>> See <http://httpd.apache.org/docs/2.2/mod/mod_env.html#setenv>
>>
>> HTH,
>> Rainer
>
> Thanks for the idea, I've tried this approach. Unfortunately it  
> seems to have
> no effect on the path that mod_php actually sees. I'm not sure if  
> it's an apache
> security thing or something else.
>
> Is there any chance anyone would know why this wouldn't work?
>
> SetEnv PATH $PATH:/opt/local/bin

I do not know. Perhaps Apache does not pass the PATH to mod_php. You  
should probably ask in a PHP support forum if you want to pursue this.


When I used to write web pages that used binaries which could be in  
different locations, I would use constants, e.g. in a config file:

<?php
define('IDENTIFY', '/opt/local/bin/identify');
?>

Then in the code where I wanted to run identify:

<?php
require_once 'config.php';
exec(IDENTIFY . ' 2>&1', $output, $error_code);
?>

This way there's only one place (the config file) where you have to  
change the paths and not hunt all over your code.


In addition, you can write the config file in such a way that it  
adapts itself to the machine it's running on:

<?php
if (defined('PRODUCTION_SERVER') && PRODUCTION_SERVER) {
	define('IDENTIFY', '/usr/local/bin/identify';
} else if (defined('DEVELOPMENT_SERVER') && DEVELOPMENT_SERVER) {
	define('IDENTIFY', '/opt/local/bin/identify';
} else {
	trigger_error('Unknown server; please modify config file');
}
?>

PRODUCTION_SERVER and DEVELOPMENT_SERVER can be defined in each  
server's auto-prepend file; see:

http://www.php.net/ini.core#ini.auto-prepend-file



From ryandesign at macports.org  Thu Jan  8 19:41:18 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 8 Jan 2009 21:41:18 -0600
Subject: Claws-mail port question
In-Reply-To: <4b75340e0901080620j29c62f77i7efdef3c9908db3@mail.gmail.com>
References: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>
	<4b75340e0901080620j29c62f77i7efdef3c9908db3@mail.gmail.com>
Message-ID: <22468929-C875-46BA-8BB2-264897687D4D@macports.org>

It looks like Guido Soranzio (gui_dos at macports dot org) first  
added the port in February 2008, and Rainer Mueller (raimue at  
macports dot org) updated it in January 2009. You could ask them if  
they have any guidance. But since they are not listed as the  
maintainer, perhaps they are not able to answer such questions. If  
you would like to investigate what needs to be done to fix it (talk  
with the authors of the software, or their support list if they have  
one), please feel free to report back your findings so that the port  
can be improved. If you can supply a patch to fix the port, or to add  
separate ports for the plugins, if that's appropriate, even better.  
If you would like to be the port's maintainer, let us know.


On Jan 8, 2009, at 08:20, Doctor Who wrote:

> Anyone??
>
>
> On Mon, Jan 5, 2009 at 11:10 AM, Doctor Who wrote:
>
>> Not sure if this is the right list, so let me know if this is not the
>> case.  I installed MacPorts yesterday and used it to install
>> claws-mail from ports.
>>
>> Everything went well with the install, and I can launch claws-mail  
>> and
>> view messages, etc.
>>
>> However, only a few plugins appear to be built.  I don't have plugins
>> for gtkhtml2-viewer or attach_reminder, for example.
>>
>> There is not a separate port for the plugins that I can see.  And
>> there is no maintainer listed on the ports.
>>
>> I'm hoping someone can help me with this.
>>
>> Thanks!



From opendarwin.org at darkart.com  Thu Jan  8 19:47:57 2009
From: opendarwin.org at darkart.com (Eric Hall)
Date: Fri, 9 Jan 2009 03:47:57 +0000
Subject: Perl 5.8 @5.8.9 does not get on with Ccache during configure
In-Reply-To: <4961EDAC.7010108@googlemail.com>
References: <4961EDAC.7010108@googlemail.com>
Message-ID: <20090109034757.GQ1155@darkart.com>

On Mon, Jan 05, 2009 at 11:23:24AM +0000, David Evans wrote:
> Perl does not get on with CCACHE during the configure phase.
> It works if ccache is disabled.

[snip]

	This was fixed a few days ago, you should be able to:

	sudo port selfupdate

	and then it should work.

	See http://trac.macports.org/ticket/17890 for more info.

		-eric


From christopher.rob.jones at cern.ch  Fri Jan  9 01:41:18 2009
From: christopher.rob.jones at cern.ch (Chris Jones)
Date: Fri, 9 Jan 2009 09:41:18 +0000
Subject: xine-libs compilation failure
Message-ID: <A364DBFC-0ECD-4C4C-A91A-171272259FBA@cern.ch>

HI,

I just ran

  > sudo port sync ; sudo port upgrade outdated

This appears to try and bring in a new port for me, xine-lib -  
Unfortunately this port fails with the error below. This has been  
going on for sometime now. Is anyone else seeing this, in which case  
I'll file a ticket ?

cheers Chris

/bin/sh ../../../libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0 - 
DHAVE_CONFIG_H -I. -I../../../include -I../../.. -I../../../include - 
I../../../include -I../../../src -I../../../src/xine-engine -I../../../ 
src/xine-engine -I../../../src/xine-utils  -I../../../src/input - 
I../../../src/input  -I../../../lib -I../../../lib  -I/opt/local/ 
include -DCONFIG_DARWIN  -fvisibility=hidden -I/opt/local/include   -I/ 
opt/local/include   -fomit-frame-pointer -D_REENTRANT - 
D_FILE_OFFSET_BITS=64 -DXINE_COMPILE   -Wformat=2 -Wno-format-zero- 
length -Wmissing-format-attribute -Werror-implicit-function- 
declaration -Wstrict-aliasing=2 -mtune=i386 -O3 -pipe -fomit-frame- 
pointer -falign-functions=4 -falign-loops=4 -falign-jumps=4   - 
fexpensive-optimizations -fschedule-insns2 -ffast-math -finline- 
functions -Wall -Wpointer-arith -Wnested-externs -Wcast-align -Wchar- 
subscripts -Wmissing-declarations -Wmissing-prototypes -O2 -DNDEBUG - 
MT xineplug_post_planar_la-pp.lo -MD -MP -MF .deps/ 
xineplug_post_planar_la-pp.Tpo -c -o xineplug_post_planar_la-pp.lo  
`test -f 'pp.c' || echo './'`pp.c
  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I../../../include -I../../.. - 
I../../../include -I../../../include -I../../../src -I../../../src/ 
xine-engine -I../../../src/xine-engine -I../../../src/xine-utils - 
I../../../src/input -I../../../src/input -I../../../lib -I../../../lib  
-I/opt/local/include -DCONFIG_DARWIN -fvisibility=hidden -I/opt/local/ 
include -I/opt/local/include -fomit-frame-pointer -D_REENTRANT - 
D_FILE_OFFSET_BITS=64 -DXINE_COMPILE -Wformat=2 -Wno-format-zero- 
length -Wmissing-format-attribute -Werror-implicit-function- 
declaration -Wstrict-aliasing=2 -mtune=i386 -O3 -pipe -fomit-frame- 
pointer -falign-functions=4 -falign-loops=4 -falign-jumps=4 - 
fexpensive-optimizations -fschedule-insns2 -ffast-math -finline- 
functions -Wall -Wpointer-arith -Wnested-externs -Wcast-align -Wchar- 
subscripts -Wmissing-declarations -Wmissing-prototypes -O2 -DNDEBUG - 
MT xineplug_post_planar_la-pp.lo -MD -MP -MF .deps/ 
xineplug_post_planar_la-pp.Tpo -c pp.c  -fno-common -DPIC -o .libs/ 
xineplug_post_planar_la-pp.o
In file included from ../../../src/xine-engine/xine_internal.h:33,
                  from pp.c:27:
../../../include/xine.h:2230: warning: 'xine_tvsystem' is deprecated
In file included from ../../../src/input/input_plugin.h:29,
                  from ../../../src/xine-engine/xine_internal.h:35,
                  from pp.c:27:
../../../src/xine-engine/buffer.h:679: warning: return type defaults  
to 'int'
pp.c:33:27: error: postprocess.h: No such file or directory
pp.c:59: error: 'PP_QUALITY_MAX' undeclared here (not in a function)
pp.c:79: error: syntax error before 'pp_context_t'
pp.c:79: warning: no semicolon at end of struct or union
pp.c:80: warning: type defaults to 'int' in declaration of 'pp_mode'
pp.c:80: warning: data definition has no type or storage class
pp.c:83: error: syntax error before '}' token
pp.c: In function 'set_parameters':
pp.c:90: error: dereferencing pointer to incomplete type
pp.c:90: error: request for member 'lock' in something not a structure  
or union
pp.c:90: warning: passing argument 1 of 'pthread_mutex_lock' from  
incompatible pointer type
pp.c:92: error: dereferencing pointer to incomplete type
pp.c:92: error: request for member 'params' in something not a  
structure or union
pp.c:94: error: dereferencing pointer to incomplete type
pp.c:94: error: request for member 'lock' in something not a structure  
or union
pp.c:94: warning: passing argument 1 of 'pthread_mutex_unlock' from  
incompatible pointer type
pp.c: In function 'get_parameters':
pp.c:104: error: dereferencing pointer to incomplete type
pp.c:104: error: request for member 'params' in something not a  
structure or union
pp.c: In function 'get_help':
pp.c:127: error: 'pp_help' undeclared (first use in this function)
pp.c:127: error: (Each undeclared identifier is reported only once
pp.c:127: error: for each function it appears in.)
pp.c: In function 'pp_open_plugin':
pp.c:178: error: invalid application of 'sizeof' to incomplete type  
'post_plugin_pp_t'
pp.c:190: error: dereferencing pointer to incomplete type
pp.c:190: error: request for member 'post' in something not a  
structure or union
pp.c:190: warning: passing argument 1 of '_x_post_init' from  
incompatible pointer type
pp.c:192: error: dereferencing pointer to incomplete type
pp.c:192: error: request for member 'params' in something not a  
structure or union
pp.c:192: error: request for member 'quality' in something not a  
structure or union
pp.c:192: warning: statement with no effect
pp.c:193: error: dereferencing pointer to incomplete type
pp.c:193: error: request for member 'params' in something not a  
structure or union
pp.c:193: error: request for member 'mode' in something not a  
structure or union
pp.c:193: warning: passing argument 1 of 'strcpy' from incompatible  
pointer type
pp.c:197: error: dereferencing pointer to incomplete type
pp.c:197: error: request for member 'pp_flags' in something not a  
structure or union
pp.c:197: error: 'PP_FORMAT_420' undeclared (first use in this function)
pp.c:197: warning: statement with no effect
pp.c:199: error: dereferencing pointer to incomplete type
pp.c:199: error: request for member 'pp_flags' in something not a  
structure or union
pp.c:199: error: 'PP_CPU_CAPS_MMX' undeclared (first use in this  
function)
pp.c:199: warning: statement with no effect
pp.c:201: error: dereferencing pointer to incomplete type
pp.c:201: error: request for member 'pp_flags' in something not a  
structure or union
pp.c:201: error: 'PP_CPU_CAPS_MMX2' undeclared (first use in this  
function)
pp.c:201: warning: statement with no effect
pp.c:203: error: dereferencing pointer to incomplete type
pp.c:203: error: request for member 'pp_flags' in something not a  
structure or union
pp.c:203: error: 'PP_CPU_CAPS_3DNOW' undeclared (first use in this  
function)
pp.c:203: warning: statement with no effect
pp.c:205: error: dereferencing pointer to incomplete type
pp.c:205: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:205: warning: statement with no effect
pp.c:206: error: dereferencing pointer to incomplete type
pp.c:206: error: request for member 'pp_context' in something not a  
structure or union
pp.c:206: warning: statement with no effect
pp.c:208: error: dereferencing pointer to incomplete type
pp.c:208: error: request for member 'lock' in something not a  
structure or union
pp.c:208: warning: passing argument 1 of 'pthread_mutex_init' from  
incompatible pointer type
pp.c:210: error: dereferencing pointer to incomplete type
pp.c:210: error: request for member 'post' in something not a  
structure or union
pp.c:210: warning: passing argument 1 of  
'_x_post_intercept_video_port' from incompatible pointer type
pp.c:214: error: dereferencing pointer to incomplete type
pp.c:214: error: request for member 'params_input' in something not a  
structure or union
pp.c:214: warning: assignment from incompatible pointer type
pp.c:218: error: dereferencing pointer to incomplete type
pp.c:218: error: request for member 'post' in something not a  
structure or union
pp.c:218: error: request for member 'input' in something not a  
structure or union
pp.c:218: warning: passing argument 1 of 'xine_list_push_back' from  
incompatible pointer type
pp.c:223: error: dereferencing pointer to incomplete type
pp.c:223: error: request for member 'post' in something not a  
structure or union
pp.c:223: error: request for member 'xine_post' in something not a  
structure or union
pp.c:223: error: request for member 'video_input' in something not a  
structure or union
pp.c:223: error: incompatible types in assignment
pp.c:223: warning: statement with no effect
pp.c:225: error: dereferencing pointer to incomplete type
pp.c:225: error: request for member 'post' in something not a  
structure or union
pp.c:225: error: request for member 'dispose' in something not a  
structure or union
pp.c:225: warning: statement with no effect
pp.c:227: error: dereferencing pointer to incomplete type
pp.c:227: error: request for member 'post' in something not a  
structure or union
pp.c:227: warning: return from incompatible pointer type
pp.c: In function 'pp_dispose':
pp.c:251: error: dereferencing pointer to incomplete type
pp.c:251: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:252: error: implicit declaration of function 'pp_free_mode'
pp.c:252: warning: nested extern declaration of 'pp_free_mode'
pp.c:252: error: dereferencing pointer to incomplete type
pp.c:252: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:253: error: dereferencing pointer to incomplete type
pp.c:253: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:253: warning: statement with no effect
pp.c:255: error: dereferencing pointer to incomplete type
pp.c:255: error: request for member 'pp_context' in something not a  
structure or union
pp.c:256: error: implicit declaration of function 'pp_free_context'
pp.c:256: warning: nested extern declaration of 'pp_free_context'
pp.c:256: error: dereferencing pointer to incomplete type
pp.c:256: error: request for member 'pp_context' in something not a  
structure or union
pp.c:257: error: dereferencing pointer to incomplete type
pp.c:257: error: request for member 'pp_context' in something not a  
structure or union
pp.c:257: warning: statement with no effect
pp.c: In function 'pp_draw':
pp.c:305: error: dereferencing pointer to incomplete type
pp.c:305: error: request for member 'lock' in something not a  
structure or union
pp.c:305: warning: passing argument 1 of 'pthread_mutex_lock' from  
incompatible pointer type
pp.c:307: error: dereferencing pointer to incomplete type
pp.c:307: error: request for member 'pp_context' in something not a  
structure or union
pp.c:308: error: dereferencing pointer to incomplete type
pp.c:308: error: request for member 'frame_width' in something not a  
structure or union
pp.c:308: warning: comparison between pointer and integer
pp.c:309: error: dereferencing pointer to incomplete type
pp.c:309: error: request for member 'frame_height' in something not a  
structure or union
pp.c:309: warning: comparison between pointer and integer
pp.c:311: error: dereferencing pointer to incomplete type
pp.c:311: error: request for member 'frame_width' in something not a  
structure or union
pp.c:311: warning: statement with no effect
pp.c:312: error: dereferencing pointer to incomplete type
pp.c:312: error: request for member 'frame_height' in something not a  
structure or union
pp.c:312: warning: statement with no effect
pp.c:313: error: dereferencing pointer to incomplete type
pp.c:313: error: request for member 'pp_flags' in something not a  
structure or union
pp.c:313: warning: statement with no effect
pp.c:315: error: dereferencing pointer to incomplete type
pp.c:315: error: request for member 'pp_context' in something not a  
structure or union
pp.c:316: error: dereferencing pointer to incomplete type
pp.c:316: error: request for member 'pp_context' in something not a  
structure or union
pp.c:318: error: dereferencing pointer to incomplete type
pp.c:318: error: request for member 'pp_context' in something not a  
structure or union
pp.c:318: error: implicit declaration of function 'pp_get_context'
pp.c:318: warning: nested extern declaration of 'pp_get_context'
pp.c:318: warning: statement with no effect
pp.c:320: error: dereferencing pointer to incomplete type
pp.c:320: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:321: error: dereferencing pointer to incomplete type
pp.c:321: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:322: error: dereferencing pointer to incomplete type
pp.c:322: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:322: warning: statement with no effect
pp.c:326: error: dereferencing pointer to incomplete type
pp.c:326: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:327: error: dereferencing pointer to incomplete type
pp.c:327: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:327: error: implicit declaration of function  
'pp_get_mode_by_name_and_quality'
pp.c:327: warning: nested extern declaration of  
'pp_get_mode_by_name_and_quality'
pp.c:327: error: dereferencing pointer to incomplete type
pp.c:327: error: request for member 'params' in something not a  
structure or union
pp.c:327: error: request for member 'mode' in something not a  
structure or union
pp.c:328: error: dereferencing pointer to incomplete type
pp.c:328: error: request for member 'params' in something not a  
structure or union
pp.c:328: error: request for member 'quality' in something not a  
structure or union
pp.c:328: warning: statement with no effect
pp.c:330: error: dereferencing pointer to incomplete type
pp.c:330: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:331: error: implicit declaration of function 'pp_postprocess'
pp.c:331: warning: nested extern declaration of 'pp_postprocess'
pp.c:335: error: dereferencing pointer to incomplete type
pp.c:335: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:335: error: dereferencing pointer to incomplete type
pp.c:335: error: request for member 'pp_context' in something not a  
structure or union
pp.c:338: error: dereferencing pointer to incomplete type
pp.c:338: error: request for member 'lock' in something not a  
structure or union
pp.c:338: warning: passing argument 1 of 'pthread_mutex_unlock' from  
incompatible pointer type
pp.c:340: error: dereferencing pointer to incomplete type
pp.c:340: error: request for member 'pp_mode' in something not a  
structure or union
make[3]: *** [xineplug_post_planar_la-pp.lo] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_multimedia_xine-lib/work/xine-lib-1.1.15"  
&& make all " returned error 2
Command output: pp.c:326: error: dereferencing pointer to incomplete  
type
pp.c:326: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:327: error: dereferencing pointer to incomplete type
pp.c:327: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:327: error: implicit declaration of function  
'pp_get_mode_by_name_and_quality'
pp.c:327: warning: nested extern declaration of  
'pp_get_mode_by_name_and_quality'
pp.c:327: error: dereferencing pointer to incomplete type
pp.c:327: error: request for member 'params' in something not a  
structure or union
pp.c:327: error: request for member 'mode' in something not a  
structure or union
pp.c:328: error: dereferencing pointer to incomplete type
pp.c:328: error: request for member 'params' in something not a  
structure or union
pp.c:328: error: request for member 'quality' in something not a  
structure or union
pp.c:328: warning: statement with no effect
pp.c:330: error: dereferencing pointer to incomplete type
pp.c:330: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:331: error: implicit declaration of function 'pp_postprocess'
pp.c:331: warning: nested extern declaration of 'pp_postprocess'
pp.c:335: error: dereferencing pointer to incomplete type
pp.c:335: error: request for member 'pp_mode' in something not a  
structure or union
pp.c:335: error: dereferencing pointer to incomplete type
pp.c:335: error: request for member 'pp_context' in something not a  
structure or union
pp.c:338: error: dereferencing pointer to incomplete type
pp.c:338: error: request for member 'lock' in something not a  
structure or union
pp.c:338: warning: passing argument 1 of 'pthread_mutex_unlock' from  
incompatible pointer type
pp.c:340: error: dereferencing pointer to incomplete type
pp.c:340: error: request for member 'pp_mode' in something not a  
structure or union
make[3]: *** [xineplug_post_planar_la-pp.lo] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

Warning: the following items did not execute (for xine-lib):  
org.macports.destroot org.macports.build
Error: Unable to upgrade port: 1


From raimue at macports.org  Fri Jan  9 02:07:10 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Fri, 09 Jan 2009 11:07:10 +0100
Subject: Claws-mail port question
In-Reply-To: <22468929-C875-46BA-8BB2-264897687D4D@macports.org>
References: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>	<4b75340e0901080620j29c62f77i7efdef3c9908db3@mail.gmail.com>
	<22468929-C875-46BA-8BB2-264897687D4D@macports.org>
Message-ID: <496721CE.3060600@macports.org>

Ryan Schmidt wrote:
> It looks like Guido Soranzio (gui_dos at macports dot org) first  
> added the port in February 2008, and Rainer Mueller (raimue at  
> macports dot org) updated it in January 2009. You could ask them if  
> they have any guidance. But since they are not listed as the  
> maintainer, perhaps they are not able to answer such questions. If  
> you would like to investigate what needs to be done to fix it (talk  
> with the authors of the software, or their support list if they have  
> one), please feel free to report back your findings so that the port  
> can be improved. If you can supply a patch to fix the port, or to add  
> separate ports for the plugins, if that's appropriate, even better.  
> If you would like to be the port's maintainer, let us know.

I just wanted to give claws-mail a try and therefore updated the port to
the latest version. But I don't use claws-mail regularly, so I have no
idea about these plugins. I only tried the GnuPG plugins, which worked fine.

Rainer


From sheldon at oneblackbear.com  Fri Jan  9 02:20:39 2009
From: sheldon at oneblackbear.com (sheldon)
Date: Fri, 9 Jan 2009 10:20:39 +0000 (UTC)
Subject: apache2 env path
References: <loom.20090106T152350-866@post.gmane.org>
	<4965B158.8020400@macports.org>
	<loom.20090108T105329-634@post.gmane.org>
	<FE5B18FE-F51D-423D-8D5F-D57868641A22@macports.org>
Message-ID: <loom.20090109T101916-88@post.gmane.org>

Thanks very much for all the help, I'm convinced the right place to be asking is
the php maillist.

Sheldon


From rowen at u.washington.edu  Fri Jan  9 16:00:09 2009
From: rowen at u.washington.edu (Russell E. Owen)
Date: Fri, 09 Jan 2009 16:00:09 -0800
Subject: building tcl with macports gcc: unrecognized option
Message-ID: <rowen-362F32.16000909012009@news.gmane.org>

I'm trying to build tcl on MacOS X 10.5.6 using the macports gcc 4.3.2. 
I know a tcl is available from macports, but for obscure reasons I need 
my own non-framework version. When I do the standard:
  ./configure
  make
I eventually get this error:
cc1: error: unrecognized command line option "-mdynamic-no-pic"

I am guessing this flag is an Apple extension that is not available in 
the macports compiler. Surely this must come up when the macports tcl 
port (and perhaps other software), yet I can't find anything about it in 
the tcl port file, nor anywhere else for that matter.

Can anyone tell me how to avoid the problem?

-- Russell


From blb at macports.org  Fri Jan  9 16:36:59 2009
From: blb at macports.org (Bryan Blackburn)
Date: Fri, 9 Jan 2009 17:36:59 -0700
Subject: building tcl with macports gcc: unrecognized option
In-Reply-To: <rowen-362F32.16000909012009@news.gmane.org>
References: <rowen-362F32.16000909012009@news.gmane.org>
Message-ID: <20090110003659.GC890@ninagal.withay.com>

On Fri, Jan 09, 2009 at 04:00:09PM -0800, Russell E. Owen said:
> I'm trying to build tcl on MacOS X 10.5.6 using the macports gcc 4.3.2. 
> I know a tcl is available from macports, but for obscure reasons I need 
> my own non-framework version. When I do the standard:

Note that the tcl port does not install a framework, just the *nix-style
include/lib stuff.

>   ./configure
>   make
> I eventually get this error:
> cc1: error: unrecognized command line option "-mdynamic-no-pic"
> 
> I am guessing this flag is an Apple extension that is not available in 
> the macports compiler. Surely this must come up when the macports tcl 
> port (and perhaps other software), yet I can't find anything about it in 
> the tcl port file, nor anywhere else for that matter.

The vast majority of ports use the gcc which comes with Xcode, and the vast
majority of those use gcc-4.0, so they don't have to work around such issues
for the most part.

> 
> Can anyone tell me how to avoid the problem?

In your case, it looks like you'll need to edit unix/configure to remove
that flag from EXTRA_APP_CC_SWITCHES, then do the configure and make again;
though I haven't tried it myself.

Bryan


> 
> -- Russell

From cleonello at yahoo.com  Fri Jan  9 17:18:27 2009
From: cleonello at yahoo.com (Chris Leonello)
Date: Fri, 9 Jan 2009 17:18:27 -0800 (PST)
Subject: selfupdate failed: Error installing new MacPorts base
Message-ID: <21378412.post@talk.nabble.com>


Hi,

When trying to update from 1.6 to 1.7 doing a "sudo port -d selfupdate", I
get the following error:

===> making all in src/tclobjc1.0
gcc -c -DUSE_TCL_STUBS -g -O2  -g -Os -DHAVE_CONFIG_H -I.. -I. 
-I"/usr/include"  -DTCL_THREADS=1 -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1
-D_THREAD_SAFE=1 -DHAVE_PTHREAD_ATTR_SETSTACKSIZE=1 -DHAVE_PTHREAD_ATFORK=1
-DHAVE_READDIR_R=1 -DMAC_OSX_TCL=1 -DHAVE_CFBUNDLE=1 -DUSE_VFORK=1
-DTCL_DEFAULT_ENCODING=\"utf-8\" -DHAVE_GETCWD=1 -DHAVE_OPENDIR=1
-DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1
-DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 -DNO_VALUES_H=1 -DHAVE_LIMITS_H=1
-DHAVE_UNISTD_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TIME_H=1
-DTIME_WITH_SYS_TIME=1 -DHAVE_TM_ZONE=1 -DHAVE_GMTIME_R=1
-DHAVE_LOCALTIME_R=1 -DHAVE_TM_GMTOFF=1 -DHAVE_TIMEZONE_VAR=1
-DHAVE_ST_BLKSIZE=1 -DSTDC_HEADERS=1 -DHAVE_SIGNED_CHAR=1 -DHAVE_LANGINFO=1
-DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_FILIO_H=1 -include tclArch.h  -UPACKAGE_NAME
-UPACKAGE_TARNAME -UPACKAGE_VERSION -UPACKAGE_STRING -UPACKAGE_BUGREPORT
-fno-common tclobjc.m -o tclobjc.o
In file included from
/System/Library/Frameworks/Foundation.framework/Headers/NSAffineTransform.h:5,
                 from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:13,
                 from tclobjc.m:42:
/System/Library/Frameworks/Foundation.framework/Headers/NSObject.h:122:
error: expected ';' before '__attribute__'
In file included from
/System/Library/Frameworks/Foundation.framework/Headers/NSGeometry.h:7,
                 from
/System/Library/Frameworks/Foundation.framework/Headers/NSAffineTransform.h:6,
                 from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:13,
                 from tclobjc.m:42:
/System/Library/Frameworks/Foundation.framework/Headers/NSCoder.h:79: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSCoder.h:87: error:
expected ';' before '__attribute__'
In file included from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:15,
                 from tclobjc.m:42:
/System/Library/Frameworks/Foundation.framework/Headers/NSArray.h:62: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSArray.h:66: error:
expected ';' before '__attribute__'
In file included from
/System/Library/Frameworks/Foundation.framework/Headers/NSAttributedString.h:5,
                 from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:16,
                 from tclobjc.m:42:
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:345:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:346:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:347:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:348:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:349:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:350:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:352:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:353:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:355:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:356:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:357:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:358:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:360:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:361:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:362:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:363:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSString.h:364:
error: expected ';' before '__attribute__'
In file included from
/System/Library/Frameworks/Foundation.framework/Headers/NSAttributedString.h:6,
                 from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:16,
                 from tclobjc.m:42:
/System/Library/Frameworks/Foundation.framework/Headers/NSDictionary.h:45:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSDictionary.h:50:
error: expected ';' before '__attribute__'
In file included from
/System/Library/Frameworks/Foundation.framework/Headers/NSHashTable.h:5,
                 from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:43,
                 from tclobjc.m:42:
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:59:
error: stray '@' in program
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:59:
error: expected '=', ',', ';', 'asm' or '__attribute__' before 'NSUInteger'
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:60:
error: stray '@' in program
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:60:
error: expected '=', ',', ';', 'asm' or '__attribute__' before 'BOOL'
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:61:
error: stray '@' in program
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:61:
error: expected '=', ',', ';', 'asm' or '__attribute__' before 'NSUInteger'
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:62:
error: stray '@' in program
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:62:
error: expected '=', ',', ';', 'asm' or '__attribute__' before 'NSString'
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:65:
error: stray '@' in program
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:65:
error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:66:
error: stray '@' in program
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:66:
error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:69:
error: stray '@' in program
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:69:
error: expected '=', ',', ';', 'asm' or '__attribute__' before 'BOOL'
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:70:
error: stray '@' in program
/System/Library/Frameworks/Foundation.framework/Headers/NSPointerFunctions.h:70:
error: expected '=', ',', ';', 'asm' or '__attribute__' before 'BOOL'
In file included from
/System/Library/Frameworks/Foundation.framework/Headers/NSKeyValueCoding.h:9,
                 from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:49,
                 from tclobjc.m:42:
/System/Library/Frameworks/Foundation.framework/Headers/NSSet.h:45: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSSet.h:50: error:
expected ';' before '__attribute__'
In file included from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:76,
                 from tclobjc.m:42:
/System/Library/Frameworks/Foundation.framework/Headers/NSRunLoop.h:44:
error: expected ';' before '__attribute__'
In file included from
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:6,
                 from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:88,
                 from tclobjc.m:42:
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:52:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:53:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:54:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:55:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:56:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:67:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:68:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:70:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:71:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:73:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:74:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:76:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:77:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:79:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:80:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:83:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:86:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:89:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:90:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:93:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:94:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:95:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:97:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:98:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:99:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:100:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:102:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:103:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:104:
error: expected ';' before '__attribute__'
In file included from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:88,
                 from tclobjc.m:42:
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:75: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:76: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:77: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:78: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:83: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:84: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:85: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:88: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:89: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:91: error:
expected ';' before '__attribute__'
make[2]: *** [tclobjc.o] Error 1
make[1]: *** [all] Error 1
make: *** [all] Error 1
DEBUG: Error installing new MacPorts base: shell command "cd
/opt/local/var/macports/sources/rsync.macports.org/release/base &&
./configure --prefix=/opt/local --with-install-user=root
--with-install-group=admin --with-tclpackage=/Library/Tcl && make && make
install" returned error 2
Command output:
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:80:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:83:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:86:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:89:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:90:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:93:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:94:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:95:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:97:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:98:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:99:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:100:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:102:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:103:
error: expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURLHandle.h:104:
error: expected ';' before '__attribute__'
In file included from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:88,
                 from tclobjc.m:42:
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:75: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:76: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:77: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:78: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:83: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:84: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:85: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:88: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:89: error:
expected ';' before '__attribute__'
/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:91: error:
expected ';' before '__attribute__'
make[2]: *** [tclobjc.o] Error 1
make[1]: *** [all] Error 1
make: *** [all] Error 1

I'm on a MacBook Pro with 10.5.6 and XCode 3.1.1 installed.  I have up to
date macports versions of tcl and gcc installed.

Any Ideas???
-- 
View this message in context: http://www.nabble.com/selfupdate-failed%3A-Error-installing-new-MacPorts-base-tp21378412p21378412.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From vr8ce at yahoo.com  Sat Jan 10 12:07:43 2009
From: vr8ce at yahoo.com (Vince Rice)
Date: Sat, 10 Jan 2009 12:07:43 -0800 (PST)
Subject: Using Macports libraries in Xcode gcc
Message-ID: <758644.11599.qm@web65703.mail.ac4.yahoo.com>

OS X 10.5.6, Macports 1.7, gcc 4.0.1 from Xcode 3.1.2

The FAQ address why Macports installs its own libraries, etc. I have the opposite question, and I read the FAQ and tried searching a couple of months of maillist archives and couldn't find it. My apologies if I missed it.

I have a program I want to compile that needs popt. I've downloaded the Macports popt package, and now have the popt.h in /opt/local/include, the library in /opt/local/lib, etc.

My question is what I have to do to my gcc setup to get it to "see" the Macport installed libraries (not just popt, but any other libraries I might download). I've tried adding the -I and -L's to the gcc command, and the popt.h is found, but it complains about the library, e.g.
ld: library not found for -l/opt/local/lib/popt

I see that /opt/local/lib has libpopt.a, libpopt.la, and libpopt.0.0.0.dylib, which is similar to the other libraries. I didn't think I needed to specify "-L libpopt", but that gcc automatically added the lib prefix to the library. But, just in case, I tried adding it myself, but that didn't work, either.

An example command line of something I'm trying to compile:
gcc -g -O2 -o src/ascii/ascii src/ascii/ascii.o  -l/opt/local/lib/libpopt

Please don't point out that there's a version of ascii in Macport -- I know that, I'm just using this as an example of trying to get a Macport library working in general gcc. :)

Thanks very much for your help.


      

From raimue at macports.org  Sat Jan 10 12:17:07 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Sat, 10 Jan 2009 21:17:07 +0100
Subject: Using Macports libraries in Xcode gcc
In-Reply-To: <758644.11599.qm@web65703.mail.ac4.yahoo.com>
References: <758644.11599.qm@web65703.mail.ac4.yahoo.com>
Message-ID: <49690243.8080607@macports.org>

Vince Rice wrote:
> My question is what I have to do to my gcc setup to get it to "see"
> the Macport installed libraries (not just popt, but any other
> libraries I might download). I've tried adding the -I and -L's to the
> gcc command, and the popt.h is found, but it complains about the
> library, e.g. ld: library not found for -l/opt/local/lib/popt

gcc flags don't work like that. You need to specify the search path for
libraries using -L and then the library itself using -l.
In your case this should be:

  gcc ... -L/opt/local/lib -lpopt ...

HTH,
Rainer

From jmr at macports.org  Sat Jan 10 12:17:47 2009
From: jmr at macports.org (Joshua Root)
Date: Sun, 11 Jan 2009 07:17:47 +1100
Subject: Using Macports libraries in Xcode gcc
In-Reply-To: <758644.11599.qm@web65703.mail.ac4.yahoo.com>
References: <758644.11599.qm@web65703.mail.ac4.yahoo.com>
Message-ID: <4969026B.1050401@macports.org>

Vince Rice wrote:
> OS X 10.5.6, Macports 1.7, gcc 4.0.1 from Xcode 3.1.2
> 
> The FAQ address why Macports installs its own libraries, etc. I have the opposite question, and I read the FAQ and tried searching a couple of months of maillist archives and couldn't find it. My apologies if I missed it.
> 
> I have a program I want to compile that needs popt. I've downloaded the Macports popt package, and now have the popt.h in /opt/local/include, the library in /opt/local/lib, etc.
> 
> My question is what I have to do to my gcc setup to get it to "see" the Macport installed libraries (not just popt, but any other libraries I might download). I've tried adding the -I and -L's to the gcc command, and the popt.h is found, but it complains about the library, e.g.
> ld: library not found for -l/opt/local/lib/popt
> 
> I see that /opt/local/lib has libpopt.a, libpopt.la, and libpopt.0.0.0.dylib, which is similar to the other libraries. I didn't think I needed to specify "-L libpopt", but that gcc automatically added the lib prefix to the library. But, just in case, I tried adding it myself, but that didn't work, either.
> 
> An example command line of something I'm trying to compile:
> gcc -g -O2 -o src/ascii/ascii src/ascii/ascii.o  -l/opt/local/lib/libpopt
> 
> Please don't point out that there's a version of ascii in Macport -- I know that, I'm just using this as an example of trying to get a Macport library working in general gcc. :)
> 
> Thanks very much for your help.

Looks like you're mixing up -l and -L. The former is used like '-lpopt',
the latter like '-L/opt/local/lib'.

- Josh

From masschel at gmail.com  Sun Jan 11 10:58:06 2009
From: masschel at gmail.com (Bart Masschelein)
Date: Sun, 11 Jan 2009 19:58:06 +0100
Subject: Two MacPorts installs: problem with Python
Message-ID: <34CD44B1-F74C-4D3B-BC61-E516B3B00AFB@gmail.com>

Hi all,

I needed another MacPorts install for some development testing, so I  
installed a version of the trunk in a new location. Python appears to  
be required as dependency, but I get the following error:

--->  Activating python25 @2.5.4_0+darwin_9+macosx
Error: Target org.macports.activate returned: Image error: / 
Applications/MacPorts/MacPython 2.5/Build Applet.app/Contents/ 
Info.plist already exists and does not belong to a registered port.   
Unable to activate port python25.

Probably it is related to the fact | have a 'normal' MacPorts in my / 
opt/local, which previously has created these files.

How can I get around this? I don't think deactivating the Python from  
my original MacPorts will solve the problem.

Thanks in advance,

Bart

PS: I use the trunk, because the tarball for 1.7 gave me consistent  
errors about 'violation of the path structure' for each port. This was  
solved by using the trunk.


From brad at pixilla.com  Sun Jan 11 11:30:48 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Sun, 11 Jan 2009 11:30:48 -0800
Subject: gd2 fails on perl5
Message-ID: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>

I have recently been working at using macports to build my servers  
rather then compiling on my own.

I understood, possibly incorrectly, that I should be able to remove / 
opt and everything related to macports would be gone.

So I removed /opt and then reinstalled macports.

Attempting to get gd2 compiled fails on perl5 dependancy.

Any help would be appreciated.

bash-3.2# port -v install perl5
--->  Activating perl5.8 @5.8.9_1
Error: Target org.macports.activate returned: Image error: /usr/share/ 
bin/c2ph already exists and does not belong to a registered port.   
Unable to activate port perl5.8.
Warning: the following items did not execute (for perl5.8):  
org.macports.activate
Error: The following dependencies failed to build: perl5.8

bash-3.2# /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_lang_perl5.8/work/perl-5.8.9/perl -v

This is perl, v5.8.9 built for darwin-2level


//brad

From mcalhoun at macports.org  Sun Jan 11 12:05:05 2009
From: mcalhoun at macports.org (Marcus Calhoun-Lopez)
Date: Sun, 11 Jan 2009 20:05:05 +0000 (UTC)
Subject: gd2 fails on perl5
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
Message-ID: <loom.20090111T194548-104@post.gmane.org>

Bradley Giesbrecht <brad <at> pixilla.com> writes:

> 
> I understood, possibly incorrectly, that I should be able to remove / 
> opt and everything related to macports would be gone.
Not quite.
Some ports install startup items (and even new users).
By default, MacPorts may also have installed stuff in
/Library/Tcl and /Applications/MacPorts.
When installing MacPorts, you can put everything in /opt/local (as I do)
by using the options seen with configure --help.

> Error: Target org.macports.activate returned: Image error: /usr/share/ 
> bin/c2ph already exists and does not belong to a registered port.
By default, MacPorts should not try to install anything in /usr/share.
Try the following:
   *  which port
   * The command should result in /opt/local/bin/port
   * If so, open the file /opt/local/etc/macports/macports.conf
   * Look at the value of prefix

The value of prefix should be /opt/local.

-Marcus


From ohce86 at kitcarson.net  Sun Jan 11 12:10:54 2009
From: ohce86 at kitcarson.net (Timothy Goins)
Date: Sun, 11 Jan 2009 13:10:54 -0700
Subject: Upgrading vim
Message-ID: <BEB33F49-81F0-4180-82E8-203E406F05F6@kitcarson.net>

I am having a problem upgrading three of my active but outdated ports  
[10.5.6; Xcode 3.1; user/bin/gcc-4.0]; I am much more familiar with  
the configure-make-make install routine and am new to MacPorts.

Running ~$ sudo port outdated produces the following:

The following installed ports are outdated:
vim                            7.2.021_0 < 7.2.065_0
xorg-libxcb                    1.0_0 < 1.1_0
xorg-xcb-proto                 1.0_0 < 1.3_0

All my remaining active ports are current.

However, when I run ~$ sudo port -R upgrade vim I get the following:

--->  Building vim
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_editors_vim/work/vim72" && make all "  
returned error 2
Command output: Starting make in the src directory.
If there are problems, cd to the src directory and run make there
cd src && make all
/usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/include  
-DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/FlatCarbon  -O - 
D_FORTIFY_SOURCE=1         version.c -o objects/version.o
   /usr/bin/gcc-4.0   -L/opt/local/lib -L/usr/local/lib 	-o vim  
objects/buffer.o objects/charset.o objects/diff.o objects/digraph.o  
objects/edit.o objects/eval.o objects/ex_cmds.o objects/ex_cmds2.o  
objects/ex_docmd.o objects/ex_eval.o objects/ex_getln.o objects/ 
fileio.o objects/fold.o objects/getchar.o objects/hardcopy.o objects/ 
hashtab.o  objects/if_cscope.o objects/if_xcmdsrv.o objects/main.o  
objects/mark.o objects/memfile.o objects/memline.o objects/menu.o  
objects/message.o objects/misc1.o objects/misc2.o objects/move.o  
objects/mbyte.o objects/normal.o objects/ops.o objects/option.o  
objects/os_unix.o objects/pathdef.o objects/popupmnu.o objects/ 
quickfix.o objects/regexp.o objects/screen.o objects/search.o objects/ 
spell.o objects/syntax.o  objects/tag.o objects/term.o objects/ui.o  
objects/undo.o objects/window.o       objects/os_macosx.o objects/ 
os_mac_conv.o  objects/netbeans.o  objects/version.o       -lm  - 
lncurses -liconv -framework Carbon
Undefined symbols:
   "__Xsetlocale", referenced from:
       _get_locale_val in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _main in main.o
       _main in main.o
       _enc_locale in mbyte.o
       _mac_lang_init in os_mac_conv.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[1]: *** [vim] Error 1
make: *** [all] Error 2

Error: Unable to upgrade port: 1

I'm sure that it's something simple that I'm missing (dependencies?   
Python?); all other ports that were outdated I was able to upgrade.

Thanks,

Tim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090111/5340505f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2116 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090111/5340505f/attachment.bin>

From whodoctor at gmail.com  Sun Jan 11 12:13:40 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Sun, 11 Jan 2009 15:13:40 -0500
Subject: Error on environment?
Message-ID: <4b75340e0901111213y4659d0cayf735dd3ff8306d2d@mail.gmail.com>

I installed the findutils and coreutils packages so that I could use
locate on my Mac.  When I attempt to update the database using
'updatedb', I get:

/usr/bin/sort: string comparison failed: Illegal byte sequence
/usr/bin/sort: Set LC_ALL='C' to work around the problem.
/usr/bin/sort: The strings compared were
`/APPLICATIONS/BURN.APP/CONTENTS/RESOURCES/JAPANESE.LPROJ/BURN
?\230?\253?\225?\232/TY/TASK_STYLE.CSS' and
`/APPLICATIONS/BURN.APP/CONTENTS/RESOURCES/JAPANESE.LPROJ/CREDITS.HTML'.

Hopefully someone can tell me how to fix this.

Thanks!

From blb at macports.org  Sun Jan 11 13:24:56 2009
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 11 Jan 2009 14:24:56 -0700
Subject: Two MacPorts installs: problem with Python
In-Reply-To: <34CD44B1-F74C-4D3B-BC61-E516B3B00AFB@gmail.com>
References: <34CD44B1-F74C-4D3B-BC61-E516B3B00AFB@gmail.com>
Message-ID: <20090111212456.GE656@ninagal.withay.com>

On Sun, Jan 11, 2009 at 07:58:06PM +0100, Bart Masschelein said:
> Hi all,
>
> I needed another MacPorts install for some development testing, so I  
> installed a version of the trunk in a new location. Python appears to be 
> required as dependency, but I get the following error:
>
> --->  Activating python25 @2.5.4_0+darwin_9+macosx
> Error: Target org.macports.activate returned: Image error: / 
> Applications/MacPorts/MacPython 2.5/Build Applet.app/Contents/Info.plist 
> already exists and does not belong to a registered port.  Unable to 
> activate port python25.
>
> Probably it is related to the fact | have a 'normal' MacPorts in my / 
> opt/local, which previously has created these files.
>
> How can I get around this? I don't think deactivating the Python from my 
> original MacPorts will solve the problem.

When you install from source, and want to avoid conflicts with a standard
MacPorts install, use the --with-tclpackage, --with-applications-dir, and
--with-frameworks-dir to point to subdirectories within your chosen prefix.
This way, everything gets placed into ${prefix}; for example,

$ ./configure --prefix=/other --with-tclpackage=/other/Library/Tcl
--with-applications-dir=/other/Applications
--with-frameworks-dir=/other/Library/Frameworks

>
> Thanks in advance,
>
> Bart
>
> PS: I use the trunk, because the tarball for 1.7 gave me consistent  
> errors about 'violation of the path structure' for each port. This was  
> solved by using the trunk.

Probably ticket #13789

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

which as you've discovered is fixed on trunk.  If it is that, you should be
able to still use 1.7 just make sure there's no slash at the end of prefix.

Bryan


From blb at macports.org  Sun Jan 11 13:28:45 2009
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 11 Jan 2009 14:28:45 -0700
Subject: Upgrading vim
In-Reply-To: <BEB33F49-81F0-4180-82E8-203E406F05F6@kitcarson.net>
References: <BEB33F49-81F0-4180-82E8-203E406F05F6@kitcarson.net>
Message-ID: <20090111212845.GF656@ninagal.withay.com>

On Sun, Jan 11, 2009 at 01:10:54PM -0700, Timothy Goins said:
> I am having a problem upgrading three of my active but outdated ports  
> [10.5.6; Xcode 3.1; user/bin/gcc-4.0]; I am much more familiar with the 
> configure-make-make install routine and am new to MacPorts.
[...]
>
> However, when I run ~$ sudo port -R upgrade vim I get the following:
[...]
> Undefined symbols:
>   "__Xsetlocale", referenced from:
>       _get_locale_val in ex_cmds2.o

Probably ticket #17606:

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

Bryan

[...]
>
> Thanks,
>
> Tim
>

From raimue at macports.org  Sun Jan 11 13:42:57 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Sun, 11 Jan 2009 22:42:57 +0100
Subject: Upgrading vim
In-Reply-To: <BEB33F49-81F0-4180-82E8-203E406F05F6@kitcarson.net>
References: <BEB33F49-81F0-4180-82E8-203E406F05F6@kitcarson.net>
Message-ID: <496A67E1.9030500@macports.org>

Timothy Goins wrote:
> Undefined symbols:
>    "__Xsetlocale", referenced from:
>        _get_locale_val in ex_cmds2.o
>        _ex_language in ex_cmds2.o
>        _ex_language in ex_cmds2.o
>        _ex_language in ex_cmds2.o
>        _main in main.o
>        _main in main.o
>        _enc_locale in mbyte.o
>        _mac_lang_init in os_mac_conv.o
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[1]: *** [vim] Error 1
> make: *** [all] Error 2

I've got several reports for this now, but was still unable to reproduce
it or track it down further than that it happens It works fine for me on
Mac OS X 10.5.6 with Xcode 3.1.2 and Xquartz 2.3.2.1.

Which versions of Xcode and Xquartz do you use?

Rainer

From brad at pixilla.com  Sun Jan 11 13:52:05 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Sun, 11 Jan 2009 13:52:05 -0800
Subject: gd2 fails on perl5
In-Reply-To: <loom.20090111T194548-104@post.gmane.org>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<loom.20090111T194548-104@post.gmane.org>
Message-ID: <836186E2-BD65-4879-A2E2-0D8CC8310D66@pixilla.com>


On Jan 11, 2009, at 12:05 PM, Marcus Calhoun-Lopez wrote:

> Bradley Giesbrecht <brad <at> pixilla.com> writes:
>
>>
>> I understood, possibly incorrectly, that I should be able to remove /
>> opt and everything related to macports would be gone.
> Not quite.
> Some ports install startup items (and even new users).
> By default, MacPorts may also have installed stuff in
> /Library/Tcl and /Applications/MacPorts.
> When installing MacPorts, you can put everything in /opt/local (as I  
> do)
> by using the options seen with configure --help.

I misspoke. I do understand that users and groups may be left as well  
as startup/launchd items.
That said, I see this being part of my problem.

>> Error: Target org.macports.activate returned: Image error: /usr/ 
>> share/
>> bin/c2ph already exists and does not belong to a registered port.
> By default, MacPorts should not try to install anything in /usr/share.
> Try the following:
>   *  which port
>   * The command should result in /opt/local/bin/port
>   * If so, open the file /opt/local/etc/macports/macports.conf
>   * Look at the value of prefix

Everything is as you state. I didn't alter prefix in my previous  
install nor my new install.

I just uninstalled everything using "port uninstall installed".
Removed "/opt" and "/Libraray/LaunchDaemons/org.macports*" and  
reinstalled macports.

	port -v install perl5

ends with this

	Warning: violation by /usr
	Warning: perl5.8 violates the layout of the ports-filesystems!
	Warning: Please fix or indicate this misbehavior (if it is intended),  
it will be an error in future releases!
	--->  Installing perl5.8 @5.8.9_1
	--->  Activating perl5.8 @5.8.9_1
	Error: Target org.macports.activate returned: Image error: /usr/share/ 
bin/c2ph already exists and does not belong to a registered port.   
Unable to activate port perl5.8.
	Warning: the following items did not execute (for perl5.8):  
org.macports.activate
	Error: The following dependencies failed to build: perl5.8
	Error: Status 1 encountered during processing.


If someone can shed some light I would be very grateful.

Thank you for the reply,
Bradley

From masschel at gmail.com  Sun Jan 11 15:49:44 2009
From: masschel at gmail.com (Bart Masschelein)
Date: Mon, 12 Jan 2009 00:49:44 +0100
Subject: Two MacPorts installs: problem with Python
In-Reply-To: <20090111212456.GE656@ninagal.withay.com>
References: <34CD44B1-F74C-4D3B-BC61-E516B3B00AFB@gmail.com>
	<20090111212456.GE656@ninagal.withay.com>
Message-ID: <06D9416F-1DDB-46CC-929B-09B769BD4683@gmail.com>

>> How can I get around this? I don't think deactivating the Python  
>> from my
>> original MacPorts will solve the problem.
>
> When you install from source, and want to avoid conflicts with a  
> standard
> MacPorts install, use the --with-tclpackage, --with-applications- 
> dir, and
> --with-frameworks-dir to point to subdirectories within your chosen  
> prefix.
> This way, everything gets placed into ${prefix}; for example,
>
> $ ./configure --prefix=/other --with-tclpackage=/other/Library/Tcl
> --with-applications-dir=/other/Applications
> --with-frameworks-dir=/other/Library/Frameworks

Thanks, that was what I needed.

>> PS: I use the trunk, because the tarball for 1.7 gave me consistent
>> errors about 'violation of the path structure' for each port. This  
>> was
>> solved by using the trunk.
>
> Probably ticket #13789
>
> <http://trac.macports.org/ticket/13789>
>
> which as you've discovered is fixed on trunk.  If it is that, you  
> should be
> able to still use 1.7 just make sure there's no slash at the end of  
> prefix.

Thanks, I will remember this when I use the tarball in the future.  
Will the tarball reflect this change in the future, for a minor  
version update?

Cheers,

Bart


From blb at macports.org  Sun Jan 11 16:27:44 2009
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 11 Jan 2009 17:27:44 -0700
Subject: Two MacPorts installs: problem with Python
In-Reply-To: <06D9416F-1DDB-46CC-929B-09B769BD4683@gmail.com>
References: <34CD44B1-F74C-4D3B-BC61-E516B3B00AFB@gmail.com>
	<20090111212456.GE656@ninagal.withay.com>
	<06D9416F-1DDB-46CC-929B-09B769BD4683@gmail.com>
Message-ID: <20090112002744.GG656@ninagal.withay.com>

On Mon, Jan 12, 2009 at 12:49:44AM +0100, Bart Masschelein said:
[...]
>> Probably ticket #13789
>>
>> <http://trac.macports.org/ticket/13789>
>>
>> which as you've discovered is fixed on trunk.  If it is that, you  
>> should be
>> able to still use 1.7 just make sure there's no slash at the end of  
>> prefix.
>
> Thanks, I will remember this when I use the tarball in the future. Will 
> the tarball reflect this change in the future, for a minor version update?

Whenever 1.8 is released, that will definitely have the change; I haven't
updated the 1.7 branch to use a newer configure however, since this is a
small issue with an easy workaround.  Though watching what effect the newer
configure for 1.8 has for people, it could be updated on 1.7 as well if
there are no issues with it.

Bryan


>
> Cheers,
>
> Bart

From whodoctor at gmail.com  Sun Jan 11 16:51:11 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Sun, 11 Jan 2009 19:51:11 -0500
Subject: Claws-mail port question
In-Reply-To: <496721CE.3060600@macports.org>
References: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>
	<4b75340e0901080620j29c62f77i7efdef3c9908db3@mail.gmail.com>
	<22468929-C875-46BA-8BB2-264897687D4D@macports.org>
	<496721CE.3060600@macports.org>
Message-ID: <4b75340e0901111651xda5c43br58749f62baa93ace@mail.gmail.com>

On Fri, Jan 9, 2009 at 5:07 AM, Rainer M?ller <raimue at macports.org> wrote:
> Ryan Schmidt wrote:
>> It looks like Guido Soranzio (gui_dos at macports dot org) first
>> added the port in February 2008, and Rainer Mueller (raimue at
>> macports dot org) updated it in January 2009. You could ask them if
>> they have any guidance. But since they are not listed as the
>> maintainer, perhaps they are not able to answer such questions. If
>> you would like to investigate what needs to be done to fix it (talk
>> with the authors of the software, or their support list if they have
>> one), please feel free to report back your findings so that the port
>> can be improved. If you can supply a patch to fix the port, or to add
>> separate ports for the plugins, if that's appropriate, even better.
>> If you would like to be the port's maintainer, let us know.
>
> I just wanted to give claws-mail a try and therefore updated the port to
> the latest version. But I don't use claws-mail regularly, so I have no
> idea about these plugins. I only tried the GnuPG plugins, which worked fine.
>
> Rainer
>
>

Thanks...I just compiled all the plugins I needed from source.

However, I can't figure out how to get the spell check feature
working.  I have no dictionary listed in the Configuration
preferences.  Can anyone help with that?  I have enchant and gtkspell2
installed.

Thanks!

From mark at mark100.net  Sun Jan 11 17:54:52 2009
From: mark at mark100.net (Mark Fraser)
Date: Sun, 11 Jan 2009 20:54:52 -0500
Subject: Ruby 1.9.1 and Rails 2.2.2 using MacPorts
Message-ID: <496AA2EC.7000408@mark100.net>

Has anyone here been able to successfully install Ruby on Rails with 
Ruby 1.9.1 using MacPorts (on Tiger)?

First I tried installing Ruby 1.9.1 and it installed fine.

Then installing rails using 'gem install rails' led to a rails 
installation where all of the generate scripts and rake tasks were broken.

So I started over and this time I tried using MacPorts to install rails 
(rb-rails).  In this case MacPorts installed a 1.8.x version of Ruby 
(and put the rails gems under that).

Any info or help would be appreciated.


From brad at pixilla.com  Sun Jan 11 21:18:52 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Sun, 11 Jan 2009 21:18:52 -0800
Subject: perl5 install errors
Message-ID: <798A7176-D7F1-4F46-AFFC-19445220CDBC@pixilla.com>

While struggling to get perl5 reinstalled I noticed a lot of files  
referencing /opt/local/bin/perl in /usr/share/bin.

Does anyone know if this is normal?

I haven't changed any prefix settings, at least not intentionally.


//Brad

From jmr at macports.org  Sun Jan 11 21:28:59 2009
From: jmr at macports.org (Joshua Root)
Date: Mon, 12 Jan 2009 16:28:59 +1100
Subject: gd2 fails on perl5
In-Reply-To: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
Message-ID: <496AD51B.4020605@macports.org>

Bradley Giesbrecht wrote:
> I have recently been working at using macports to build my servers
> rather then compiling on my own.
> 
> I understood, possibly incorrectly, that I should be able to remove /opt
> and everything related to macports would be gone.
> 
> So I removed /opt and then reinstalled macports.

You should run `sudo port -f uninstall installed` first to be sure to
get everything. See also the FAQ entry:
<http://trac.macports.org/wiki/FAQ#HowdoIremoveoruninstallMacPorts>

Note also that the default prefix is /opt/local, not /opt, a small but
significant difference.

- Josh

From jmr at macports.org  Sun Jan 11 23:36:43 2009
From: jmr at macports.org (Joshua Root)
Date: Mon, 12 Jan 2009 18:36:43 +1100
Subject: gd2 fails on perl5
In-Reply-To: <DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
Message-ID: <496AF30B.2070006@macports.org>

Bradley Giesbrecht wrote:
> I still don't understand why perl5 is writing anything to
> /usr/share/bin. I've used fink, darwinports and now macports for years
> and I thought they installed in complete isolation under /sw or /opt/local.

Everything being under /opt/local is indeed the expected behaviour, bar
the few exceptions that have a good reason to install files elsewhere.
And indeed that is the case for perl5.8 here, according to 'port
contents perl5.8'.

It really does look as though your prefix has somehow been set to
/usr/share.

- Josh

From adrian at lobstersoft.com  Wed Jan  7 08:31:04 2009
From: adrian at lobstersoft.com (Adrian Grigore)
Date: Wed, 07 Jan 2009 17:31:04 +0100
Subject: Reconfiguring WxWidgets
Message-ID: <4964D8C8.2060509@lobstersoft.com>

Hi,

I have successfully installed wxwidgets 2.8 using macports. I
need a slightly different configuration of wxwidgets and have
therefore edited the setup.h file accordingly. What's the easyest
way to apply the new settings (i.e. recompile wxwidgets with the
new setup.h file)?

Thanks,

Adrian



From raimue at macports.org  Mon Jan 12 01:24:37 2009
From: raimue at macports.org (=?UTF-8?B?UmFpbmVyIE3DvGxsZXI=?=)
Date: Mon, 12 Jan 2009 10:24:37 +0100
Subject: Claws-mail port question
In-Reply-To: <4b75340e0901111651xda5c43br58749f62baa93ace@mail.gmail.com>
References: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>	
	<4b75340e0901080620j29c62f77i7efdef3c9908db3@mail.gmail.com>	
	<22468929-C875-46BA-8BB2-264897687D4D@macports.org>	
	<496721CE.3060600@macports.org>
	<4b75340e0901111651xda5c43br58749f62baa93ace@mail.gmail.com>
Message-ID: <496B0C55.80604@macports.org>

Doctor Who wrote:
> However, I can't figure out how to get the spell check feature
> working.  I have no dictionary listed in the Configuration
> preferences.  Can anyone help with that?  I have enchant and gtkspell2
> installed.

enchant uses the aspell dictionaries, just install any of the
aspell-dict-* ports and they will appear in this list.

Rainer

From ryandesign at macports.org  Mon Jan 12 03:47:56 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 12 Jan 2009 05:47:56 -0600
Subject: sudo: port: command not found
In-Reply-To: <dc98b4380901120330s5163ffc7wfcd63d6d22cffec6@mail.gmail.com>
References: <dc98b4380901120330s5163ffc7wfcd63d6d22cffec6@mail.gmail.com>
Message-ID: <0E67C0A4-5D04-4295-A7A4-0F450DDE8DBD@macports.org>

On Jan 12, 2009, at 05:30, Marion Dumas wrote:

> Hello,
> I just installed the latest version of MacPorts for Leopard, but the
> command port does not work (error message; sudo: port: command not
> found). I am not very experienced with Unix, so I am not too sure what
> is going wrong. Could anybody help?
> Thank you very much
> Marion

Welcome to MacPorts, Marion. I'm sending this reply to the macports- 
users mailing list, where you should continue the topic if necessary.  
Subscribe to the list first so that your posts will be accepted. The  
address macports-users-owner at lists.macosforge.org only reaches the  
owners of the list and you would be better served by interacting with  
the entire community.

What you describe was a problem with the MacPorts 1.6.0 installer,  
but if you are using the latest version of MacPorts, 1.7.0, you  
should not see this problem anymore. You can read about the problem  
and the various ways to fix it in the problem hotlist in the wiki:

http://trac.macports.org/wiki/ProblemHotlist#a.profilenotsetup



From vincent-opdarw at vinc17.org  Mon Jan 12 04:09:15 2009
From: vincent-opdarw at vinc17.org (Vincent Lefevre)
Date: Mon, 12 Jan 2009 13:09:15 +0100
Subject: perl5 install errors
In-Reply-To: <798A7176-D7F1-4F46-AFFC-19445220CDBC@pixilla.com>
References: <798A7176-D7F1-4F46-AFFC-19445220CDBC@pixilla.com>
Message-ID: <20090112120915.GQ14649@prunille.vinc17.org>

On 2009-01-11 21:18:52 -0800, Bradley Giesbrecht wrote:
> While struggling to get perl5 reinstalled I noticed a lot of files  
> referencing /opt/local/bin/perl in /usr/share/bin.

What do you mean by "referencing"? Do you have an example?

-- 
Vincent Lef?vre <vincent at vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

From jmr at macports.org  Mon Jan 12 04:59:04 2009
From: jmr at macports.org (Joshua Root)
Date: Mon, 12 Jan 2009 23:59:04 +1100
Subject: [SOLVED] Re: sudo: port: command not found
In-Reply-To: <dc98b4380901120449v73f8603cv74c3abe4454f8fee@mail.gmail.com>
References: <dc98b4380901120330s5163ffc7wfcd63d6d22cffec6@mail.gmail.com>	
	<496B2D6C.2060100@macports.org>
	<dc98b4380901120449v73f8603cv74c3abe4454f8fee@mail.gmail.com>
Message-ID: <496B3E98.8000505@macports.org>

Forwarding to the list so everyone else knows this is solved.

Marion Dumas wrote:
> Dear Joshua,
> Thank you. Indeed, I thought I had the latest version, but it was
> indeed 1.6.0. The command port now works.
> Best
> Marion
> 
> On Mon, Jan 12, 2009 at 12:45 PM, Joshua Root <jmr at macports.org> wrote:
>> Marion Dumas wrote:
>>> Hello,
>>> I just installed the latest version of MacPorts for Leopard, but the
>>> command port does not work (error message; sudo: port: command not
>>> found). I am not very experienced with Unix, so I am not too sure what
>>> is going wrong. Could anybody help?
>> Just to check, the latest version is 1.7.0, is that what you have? There
>> was a common problem with 1.6.0 that could cause this.
>>
>> If you do have 1.7.0, you probably have a .bash_profile or .bash_login
>> file in your home folder, which will override the .profile that the
>> MacPorts installer uses. Possible solutions are to copy the contents of
>> .profile to the whichever config file that you are using, or just
>> include .profile in the other file by adding a line like so:
>>
>> . ~/.profile
>>
>> - Josh

From face at CentosPrime.COM  Mon Jan 12 06:10:12 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Mon, 12 Jan 2009 07:10:12 -0700
Subject: trying to build 'mg' on Panther
Message-ID: <0CF972FB-264E-4285-AA05-5500A19FEB60@centosprime.com>

fi_mtime is a "timespec"

can't see any options/variants that might indicate a setting I can  
change.

admin at x:admin:200 $ sudo port install mg
--->  Building mg
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_editors_mg/work/mg-20081211" && make all "  
returned error 2
Command output: gcc -O2 -pipe -g -Wall -Werror -Wno-strict-aliasing -c  
autoexec.c
In file included from def.h:13,
                  from autoexec.c:5:
sysdef.h:49: error: field `fi_mtime' has incomplete type
make: *** [autoexec.o] Error 1

Error: Status 1 encountered during processing.

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



From stonesoupandboiledfrogs at gmail.com  Mon Jan 12 06:39:58 2009
From: stonesoupandboiledfrogs at gmail.com (jason white)
Date: Mon, 12 Jan 2009 08:39:58 -0600
Subject: install trouble Mac OSX 10.4
Message-ID: <80a464360901120639t5f1e63c8mcecb4f7007d8a50a@mail.gmail.com>

hello all,   I have installed X Code 2.5, and then MacPorts 1.7 on my Mac,
and when i run sudo port selfupdate, I get the error listed below

wbp-user10:~ silliemunkie$ sudo port selfupdate
sudo: port: command not found

the entry in my .bash_profile is:

export PATH=" opt/local/bin: /opt/local/sbin:$PATH"



any guidance would be greatly appreciated


Cheers,

Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090112/33a3dd30/attachment.html>

From christopher.rob.jones at cern.ch  Mon Jan 12 06:43:25 2009
From: christopher.rob.jones at cern.ch (Chris Jones)
Date: Mon, 12 Jan 2009 14:43:25 +0000
Subject: install trouble Mac OSX 10.4
In-Reply-To: <80a464360901120639t5f1e63c8mcecb4f7007d8a50a@mail.gmail.com>
References: <80a464360901120639t5f1e63c8mcecb4f7007d8a50a@mail.gmail.com>
Message-ID: <15E3CA49-71A4-4028-998B-D24C91A30CFD@cern.ch>

>
Hi,

> the entry in my .bash_profile is:
>
> export PATH=" opt/local/bin: /opt/local/sbin:$PATH"
>

You are missing an initial / on the first path. That line should be

> export PATH=" /opt/local/bin: /opt/local/sbin:$PATH"

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090112/9e1f1953/attachment.html>

From jmr at macports.org  Mon Jan 12 07:06:10 2009
From: jmr at macports.org (Joshua Root)
Date: Tue, 13 Jan 2009 02:06:10 +1100
Subject: trying to build 'mg' on Panther
In-Reply-To: <0CF972FB-264E-4285-AA05-5500A19FEB60@centosprime.com>
References: <0CF972FB-264E-4285-AA05-5500A19FEB60@centosprime.com>
Message-ID: <496B5C62.6030306@macports.org>

Chris Janton wrote:
> fi_mtime is a "timespec"
> 
> can't see any options/variants that might indicate a setting I can change.
> 
> admin at x:admin:200 $ sudo port install mg
> --->  Building mg
> Error: Target org.macports.build returned: shell command " cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_mg/work/mg-20081211"
> && make all " returned error 2
> Command output: gcc -O2 -pipe -g -Wall -Werror -Wno-strict-aliasing -c
> autoexec.c
> In file included from def.h:13,
>                  from autoexec.c:5:
> sysdef.h:49: error: field `fi_mtime' has incomplete type
> make: *** [autoexec.o] Error 1

You'll pick up a definition for struct timespec if you #include <time.h>
(or <sys/time.h>), if that helps.

- Josh

From face at CentosPrime.COM  Mon Jan 12 07:15:08 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Mon, 12 Jan 2009 08:15:08 -0700
Subject: trying to build 'mg' on Panther
In-Reply-To: <496B5C62.6030306@macports.org>
References: <0CF972FB-264E-4285-AA05-5500A19FEB60@centosprime.com>
	<496B5C62.6030306@macports.org>
Message-ID: <0CD19CDF-BD73-42DD-B774-03AE5ABF399F@CentosPrime.COM>

On 2009-01-12 , at 08:06 , Joshua Root wrote:

> You'll pick up a definition for struct timespec if you #include  
> <time.h>
> (or <sys/time.h>), if that helps.


Yes, that will do for now. As long as mg doesn't change too much ;-)

I modified the source file with "#include <time.h>" and mg built and  
installed.

Thanks.

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



From jmr at macports.org  Mon Jan 12 07:29:26 2009
From: jmr at macports.org (Joshua Root)
Date: Tue, 13 Jan 2009 02:29:26 +1100
Subject: trying to build 'mg' on Panther
In-Reply-To: <0CD19CDF-BD73-42DD-B774-03AE5ABF399F@CentosPrime.COM>
References: <0CF972FB-264E-4285-AA05-5500A19FEB60@centosprime.com>
	<496B5C62.6030306@macports.org>
	<0CD19CDF-BD73-42DD-B774-03AE5ABF399F@CentosPrime.COM>
Message-ID: <496B61D6.7000503@macports.org>

Chris Janton wrote:
> On 2009-01-12 , at 08:06 , Joshua Root wrote:
> 
>> You'll pick up a definition for struct timespec if you #include <time.h>
>> (or <sys/time.h>), if that helps.
> 
> 
> Yes, that will do for now. As long as mg doesn't change too much ;-)
> 
> I modified the source file with "#include <time.h>" and mg built and
> installed.

Might as well open a ticket requesting that it be patched in that way on
darwin 7.

- Josh

From j.van_den_hoff at fzd.de  Mon Jan 12 08:23:04 2009
From: j.van_den_hoff at fzd.de (Joerg van den Hoff)
Date: Mon, 12 Jan 2009 17:23:04 +0100
Subject: no x11 support for graphicsmagick?
Message-ID: <20090112162304.GC26702@marco.fz-rossendorf.de>

hi,

today I installed graphicsmagick for the first time in order
to evaluate it against imagemagick (seems to be much faster for
several operations).

now I do not find the `display' command (or `animate', for that matter)
in the `gm' help list -- they simply are missing.

consequently, `gm display something.jpg'

yields "Unrecognized command 'display'"

the provided variants of the package are

q8: Use 8 bits per pixel quantum (default)
q16: Use 16 bits per pixel quantum
q32: Use 32 bits per pixel quantum
universal: Build for multiple architectures

especially, there is no 'with_x11' variant or something. 

with `imagemagick' the default is to use x11 (but there is a 
variant `no_x11' to switch it off).

question: is there a way to get the `display' command working?
should the default installation not be with x11?

best regards,

joerg

From masschel at gmail.com  Mon Jan 12 10:18:42 2009
From: masschel at gmail.com (Bart Masschelein)
Date: Mon, 12 Jan 2009 19:18:42 +0100
Subject: Two MacPorts installs: problem with Python
In-Reply-To: <20090112002744.GG656@ninagal.withay.com>
References: <34CD44B1-F74C-4D3B-BC61-E516B3B00AFB@gmail.com>
	<20090111212456.GE656@ninagal.withay.com>
	<06D9416F-1DDB-46CC-929B-09B769BD4683@gmail.com>
	<20090112002744.GG656@ninagal.withay.com>
Message-ID: <E5174DFC-1DF3-4D6A-80FB-166439030795@gmail.com>

Hi,

I shouted victory to soon, as I get the following error when  
installing gtk2:

i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libXdamage.1.1.0.dylib: No  
such file or directory

I have a libXdamage.1.dylib in /Developer/SDKs/MacOSX10.5.sdk/usr/X11/ 
lib. Should I include this path in my environment library variable? I  
didn't have this problem with the installer...

Bart

From whodoctor at gmail.com  Mon Jan 12 10:27:22 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Mon, 12 Jan 2009 13:27:22 -0500
Subject: Claws-mail port question
In-Reply-To: <496B0C55.80604@macports.org>
References: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>
	<4b75340e0901080620j29c62f77i7efdef3c9908db3@mail.gmail.com>
	<22468929-C875-46BA-8BB2-264897687D4D@macports.org>
	<496721CE.3060600@macports.org>
	<4b75340e0901111651xda5c43br58749f62baa93ace@mail.gmail.com>
	<496B0C55.80604@macports.org>
Message-ID: <4b75340e0901121027k190b3b02m6f439d9ccef83362@mail.gmail.com>

On Mon, Jan 12, 2009 at 4:24 AM, Rainer M?ller <raimue at macports.org> wrote:
> Doctor Who wrote:
>> However, I can't figure out how to get the spell check feature
>> working.  I have no dictionary listed in the Configuration
>> preferences.  Can anyone help with that?  I have enchant and gtkspell2
>> installed.
>
> enchant uses the aspell dictionaries, just install any of the
> aspell-dict-* ports and they will appear in this list.
>
> Rainer
>


I have the aspell-dict-en port installed, but it may have been done
*after* I installed claws-mail.

Perhaps I need to uninstall and reinstall the claws-mail port for it
to pick up the aspell dictionary?

From jmr at macports.org  Mon Jan 12 10:42:18 2009
From: jmr at macports.org (Joshua Root)
Date: Tue, 13 Jan 2009 05:42:18 +1100
Subject: Two MacPorts installs: problem with Python
In-Reply-To: <E5174DFC-1DF3-4D6A-80FB-166439030795@gmail.com>
References: <34CD44B1-F74C-4D3B-BC61-E516B3B00AFB@gmail.com>	<20090111212456.GE656@ninagal.withay.com>	<06D9416F-1DDB-46CC-929B-09B769BD4683@gmail.com>	<20090112002744.GG656@ninagal.withay.com>
	<E5174DFC-1DF3-4D6A-80FB-166439030795@gmail.com>
Message-ID: <496B8F0A.8040503@macports.org>

Bart Masschelein wrote:
> Hi,
> 
> I shouted victory to soon, as I get the following error when installing
> gtk2:
> 
> i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libXdamage.1.1.0.dylib: No
> such file or directory
> 
> I have a libXdamage.1.dylib in
> /Developer/SDKs/MacOSX10.5.sdk/usr/X11/lib. Should I include this path
> in my environment library variable? I didn't have this problem with the
> installer...

<http://trac.macports.org/wiki/LeopardProblems#usrX11liblibXrandr.2.0.0.dylib:Nosuchfileordirectory>

- Josh

From masschel at gmail.com  Mon Jan 12 11:16:56 2009
From: masschel at gmail.com (Bart Masschelein)
Date: Mon, 12 Jan 2009 20:16:56 +0100
Subject: Two MacPorts installs: problem with Python
In-Reply-To: <496B8F0A.8040503@macports.org>
References: <34CD44B1-F74C-4D3B-BC61-E516B3B00AFB@gmail.com>	<20090111212456.GE656@ninagal.withay.com>	<06D9416F-1DDB-46CC-929B-09B769BD4683@gmail.com>	<20090112002744.GG656@ninagal.withay.com>
	<E5174DFC-1DF3-4D6A-80FB-166439030795@gmail.com>
	<496B8F0A.8040503@macports.org>
Message-ID: <E3B56404-64C8-4AB7-947D-0017AEE5B8D2@gmail.com>

>> i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libXdamage.1.1.0.dylib: No
>> such file or directory
>>
>> I have a libXdamage.1.dylib in
>> /Developer/SDKs/MacOSX10.5.sdk/usr/X11/lib. Should I include this  
>> path
>> in my environment library variable? I didn't have this problem with  
>> the
>> installer...
>
> <http://trac.macports.org/wiki/LeopardProblems#usrX11liblibXrandr.2.0.0.dylib:Nosuchfileordirectory 
> >

Solved the problem (installing the latest xQuarz). Does this means  
that I would eventually also have gotten problems with the MacPorts  
installer version? I did a full reinstall of my ports when 1.7 came  
out, without this error, so this would mean the problem must have  
occurred between now and some weeks ago then.

Thanks again!

Bart

From masschel at gmail.com  Mon Jan 12 11:18:42 2009
From: masschel at gmail.com (Bart Masschelein)
Date: Mon, 12 Jan 2009 20:18:42 +0100
Subject: Two MacPorts installs: problem with Python
In-Reply-To: <496B8F0A.8040503@macports.org>
References: <34CD44B1-F74C-4D3B-BC61-E516B3B00AFB@gmail.com>	<20090111212456.GE656@ninagal.withay.com>	<06D9416F-1DDB-46CC-929B-09B769BD4683@gmail.com>	<20090112002744.GG656@ninagal.withay.com>
	<E5174DFC-1DF3-4D6A-80FB-166439030795@gmail.com>
	<496B8F0A.8040503@macports.org>
Message-ID: <2BEFBA19-1E6D-4A22-90B1-F28601BE5A1B@gmail.com>

Too hasty... I recall that I have installed the gtk2 without x11  
(+quartz variant) previously, so that probably explains why I didn't  
have a problem.

Bart

From rowen at u.washington.edu  Mon Jan 12 12:24:40 2009
From: rowen at u.washington.edu (Russell E. Owen)
Date: Mon, 12 Jan 2009 12:24:40 -0800
Subject: building tcl with macports gcc: unrecognized option
References: <rowen-362F32.16000909012009@news.gmane.org>
	<20090110003659.GC890@ninagal.withay.com>
Message-ID: <rowen-DBA1D0.12244012012009@news.gmane.org>

In article <20090110003659.GC890 at ninagal.withay.com>,
 Bryan Blackburn <blb at macports.org> wrote:

> On Fri, Jan 09, 2009 at 04:00:09PM -0800, Russell E. Owen said:
> > I'm trying to build tcl on MacOS X 10.5.6 using the macports gcc 4.3.2. 
> > I know a tcl is available from macports, but for obscure reasons I need 
> > my own non-framework version. When I do the standard:
> 
> Note that the tcl port does not install a framework, just the *nix-style
> include/lib stuff.

Yes. That is exactly what I want.

> >   ./configure
> >   make
> > I eventually get this error:
> > cc1: error: unrecognized command line option "-mdynamic-no-pic"
> > 
> > I am guessing this flag is an Apple extension that is not available in 
> > the macports compiler. Surely this must come up when the macports tcl 
> > port (and perhaps other software), yet I can't find anything about it in 
> > the tcl port file, nor anywhere else for that matter.
> 
> The vast majority of ports use the gcc which comes with Xcode, and the vast
> majority of those use gcc-4.0, so they don't have to work around such issues
> for the most part.

Oh, of course! I should have realized that.

> > Can anyone tell me how to avoid the problem?
> 
> In your case, it looks like you'll need to edit unix/configure to remove
> that flag from EXTRA_APP_CC_SWITCHES, then do the configure and make again;
> though I haven't tried it myself.

Thank you very much.

-- Russell


From macports at logicx.us  Mon Jan 12 12:33:44 2009
From: macports at logicx.us (Mike Schroll)
Date: Mon, 12 Jan 2009 15:33:44 -0500
Subject: Macports in a sparsebundle
Message-ID: <43e3d44c0901121233y30d4af8le48fd85a0d8fbb05@mail.gmail.com>

Since macports include the huge ports tree, with many thousands of
files (which could be better stored compressed); and for those who use
macports not very often -- I was curious if anyone has considered or
attempted keeping macports in a sparsebundle?

In this way; you could keep the sparsebundle tucked away when not
needed; mount it and update/install ports as required.

Any thoughts on how best to accomplish this?

I'm particularly interested in doing this with dropbox
(www.getdropbox.com).  In this way I could have a single macports tree
that I access from all my macs; and not have to do updates everywhere.

Thanks in advance for any thoughts.

-Mike Schroll

From evert.rol at gmail.com  Mon Jan 12 12:46:26 2009
From: evert.rol at gmail.com (Evert Rol)
Date: Mon, 12 Jan 2009 21:46:26 +0100
Subject: installing boost-python
Message-ID: <68c840280901121246p70d1bd4blbd147a7eae47e480@mail.gmail.com>

  Hi all,

I have a problem installing the boost python libraries over macports.
It actually installs fine, but it looks like the libboost_python*
libraries don't pick up the macport python headers/libraries, but the
system ones. Eg:
$> otool -L libboost_python-mt.dylib
libboost_python-mt.dylib:
	/opt/local/lib/libboost_python-mt.dylib (compatibility version 0.0.0,
current version 0.0.0)
	/System/Library/Frameworks/Python.framework/Versions/2.5/Python
(compatibility version 2.5.0, current version 2.5.1)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0)
	/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 111.0.0

where I would have expected the python line to be prepended with
/opt/local at least.

The problem shows up once I try to compile a file with libboost_python
into a python so module, because the python interpreter (which is the
/opt/local/bin/python25 one) doesn't agree with the version number:
the module was linked with 2.5.1 system libraries, not with the 2.5.4
macport ones.
I've tried uninstalling and installing boost, but that doesn't appear
to work. The boost portfile does explicitly seem to link to the
macport python libraries, so I cannot see any problem there.

I realise this may not completely be a macports issue, but possibly
something to ask the maintainer, but if anyone on the list has some
suggestions where to look or what to change, I'd appreciate that.
For the record, the system is a G5 pro running Leopard.

  Evert

From whodoctor at gmail.com  Mon Jan 12 13:20:37 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Mon, 12 Jan 2009 16:20:37 -0500
Subject: Claws-mail port question
In-Reply-To: <496B0C55.80604@macports.org>
References: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>
	<4b75340e0901080620j29c62f77i7efdef3c9908db3@mail.gmail.com>
	<22468929-C875-46BA-8BB2-264897687D4D@macports.org>
	<496721CE.3060600@macports.org>
	<4b75340e0901111651xda5c43br58749f62baa93ace@mail.gmail.com>
	<496B0C55.80604@macports.org>
Message-ID: <4b75340e0901121320l7ec039c5r3e62ff64f9148bdd@mail.gmail.com>

On Mon, Jan 12, 2009 at 4:24 AM, Rainer M?ller <raimue at macports.org> wrote:
> Doctor Who wrote:
>> However, I can't figure out how to get the spell check feature
>> working.  I have no dictionary listed in the Configuration
>> preferences.  Can anyone help with that?  I have enchant and gtkspell2
>> installed.
>
> enchant uses the aspell dictionaries, just install any of the
> aspell-dict-* ports and they will appear in this list.
>
> Rainer
>

So, I want to try to remove and then re-install claws-mail so that it
picks up the aspell dictionary.  I tried:

sudo port deactivate claws-mail
sudo port uninstall claws-mail

I then re-installed claws-mail but all of my previous account settings
were still there and the drop-down for dictionaries was still blank.

So how do I do this 'correctly'?

From mcalhoun at macports.org  Mon Jan 12 13:28:32 2009
From: mcalhoun at macports.org (Marcus Calhoun-Lopez)
Date: Mon, 12 Jan 2009 21:28:32 +0000 (UTC)
Subject: installing boost-python
References: <68c840280901121246p70d1bd4blbd147a7eae47e480@mail.gmail.com>
Message-ID: <loom.20090112T211916-943@post.gmane.org>

Evert Rol <evert.rol <at> gmail.com> writes:

> it looks like the libboost_python*
> libraries don't pick up the macport python headers/libraries, but the
> system ones.

Did you install boost with any of the python variants
(python24, python25, or python26)?

If yes, then this is a boost bug you should report.
I use the python26 variant, and it finds the correct MacPorts python.

If no, then this is also a bug you should report, but an easy workaround would be
to reinstall boost with the python variant of your choice.

-Marcus





From evert.rol at gmail.com  Mon Jan 12 13:39:36 2009
From: evert.rol at gmail.com (Evert Rol)
Date: Mon, 12 Jan 2009 22:39:36 +0100
Subject: installing boost-python
In-Reply-To: <loom.20090112T211916-943@post.gmane.org>
References: <68c840280901121246p70d1bd4blbd147a7eae47e480@mail.gmail.com>
	<loom.20090112T211916-943@post.gmane.org>
Message-ID: <68c840280901121339i166ce3eese717bf46556ab23f@mail.gmail.com>

>> it looks like the libboost_python*
>> libraries don't pick up the macport python headers/libraries, but the
>> system ones.
>
> Did you install boost with any of the python variants
> (python24, python25, or python26)?

Yes (sorry, forgot to mention that earlier):
$> port install boost +python25+icu

(well, the icu isn't necessary, and shouldn't matter anyways)


> If yes, then this is a boost bug you should report.

Ok, I'll file a ticket at the macports website.


> I use the python26 variant, and it finds the correct MacPorts python.

Which does make me suspicious that it doesn't work me.

I wonder if it's worth uninstalling/deactiving the python25 variant,
and installing the python26 variant, to see what happens for me.


> If no, then this is also a bug you should report, but an easy workaround would be
> to reinstall boost with the python variant of your choice.
>
> -Marcus
>

From kw at codebykevin.com  Mon Jan 12 15:07:52 2009
From: kw at codebykevin.com (Kevin Walzer)
Date: Mon, 12 Jan 2009 18:07:52 -0500
Subject: PortAuthority 2.7 released
Message-ID: <496BCD48.1010605@codebykevin.com>

Code by Kevin has released PortAuthority 2.7, a GUI for the MacPorts 
package management system for Mac OS X.

PortAuthority provides a graphical user interface for the MacPorts 
package management system for Mac OS X. MacPorts is a powerful 
command-line tool for installing and updating a variety of Unix-based 
applications for the Mac. Its power, though, comes at the cost of some 
complexity; in the past the only way to utilize MacPorts was to type in 
various commands into the Mac's Terminal application, which can be 
intimidating for those users without a Unix background.

PortAuthority aims to bring the power of MacPorts to the traditional Mac 
user by providing a user-friendly graphical interface to MacPorts. Using 
a familiar combination of windows, icons, and menus, PortAuthority users 
can search, install, update, and remove MacPorts programs and the 
MacPorts infrastructure itself.

Among the features and improvements in this release:

* Bug fix: Demo version no longer crashes on initial startup.

* Can now print log output to default printer.

* Now uses integrated help viewer.

* Saves window position on application close.

* New graphics engine for improved UI appearance.

PortAuthority is shareware; a license costs $24.95 and a 30-day demo is 
available. Mac OS X 10.4 is the minimum supported OS. PortAuthority is a 
universal binary.

For more information about PortAuthority, including download links, see 
http://www.codebykevin.com/portauthority.html.
-- 
Kevin Walzer
Code by Kevin
http://www.codebykevin.com

From raimue at macports.org  Mon Jan 12 15:48:35 2009
From: raimue at macports.org (=?UTF-8?B?UmFpbmVyIE3DvGxsZXI=?=)
Date: Tue, 13 Jan 2009 00:48:35 +0100
Subject: Claws-mail port question
In-Reply-To: <4b75340e0901121027k190b3b02m6f439d9ccef83362@mail.gmail.com>
References: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>	
	<4b75340e0901080620j29c62f77i7efdef3c9908db3@mail.gmail.com>	
	<22468929-C875-46BA-8BB2-264897687D4D@macports.org>	
	<496721CE.3060600@macports.org>	
	<4b75340e0901111651xda5c43br58749f62baa93ace@mail.gmail.com>	
	<496B0C55.80604@macports.org>
	<4b75340e0901121027k190b3b02m6f439d9ccef83362@mail.gmail.com>
Message-ID: <496BD6D3.8010806@macports.org>

Doctor Who wrote:
> I have the aspell-dict-en port installed, but it may have been done
> *after* I installed claws-mail.
> 
> Perhaps I need to uninstall and reinstall the claws-mail port for it
> to pick up the aspell dictionary?

No, there should not be any need to reinstall things. I just installed
additional aspell-dict-* ports and they are shown in preferences in
claws-mail.

Rainer

From whodoctor at gmail.com  Mon Jan 12 17:32:57 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Mon, 12 Jan 2009 20:32:57 -0500
Subject: Claws-mail port question
In-Reply-To: <496BD6D3.8010806@macports.org>
References: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>
	<4b75340e0901080620j29c62f77i7efdef3c9908db3@mail.gmail.com>
	<22468929-C875-46BA-8BB2-264897687D4D@macports.org>
	<496721CE.3060600@macports.org>
	<4b75340e0901111651xda5c43br58749f62baa93ace@mail.gmail.com>
	<496B0C55.80604@macports.org>
	<4b75340e0901121027k190b3b02m6f439d9ccef83362@mail.gmail.com>
	<496BD6D3.8010806@macports.org>
Message-ID: <4b75340e0901121732x3d5ec59sc8bebc90653b005c@mail.gmail.com>

On Mon, Jan 12, 2009 at 6:48 PM, Rainer M?ller <raimue at macports.org> wrote:
> Doctor Who wrote:
>> I have the aspell-dict-en port installed, but it may have been done
>> *after* I installed claws-mail.
>>
>> Perhaps I need to uninstall and reinstall the claws-mail port for it
>> to pick up the aspell dictionary?
>
> No, there should not be any need to reinstall things. I just installed
> additional aspell-dict-* ports and they are shown in preferences in
> claws-mail.
>
> Rainer
>

Hmmm...not sure why it's not working for me :-(

Any ideas?

From ryandesign at macports.org  Mon Jan 12 21:59:59 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 12 Jan 2009 23:59:59 -0600
Subject: install trouble Mac OSX 10.4
In-Reply-To: <15E3CA49-71A4-4028-998B-D24C91A30CFD@cern.ch>
References: <80a464360901120639t5f1e63c8mcecb4f7007d8a50a@mail.gmail.com>
	<15E3CA49-71A4-4028-998B-D24C91A30CFD@cern.ch>
Message-ID: <06249CBC-ED84-404E-A242-4FB055A903C4@macports.org>


On Jan 12, 2009, at 08:43, Chris Jones wrote:

>> the entry in my .bash_profile is:
>>
>> export PATH=" opt/local/bin: /opt/local/sbin:$PATH"
>
> You are missing an initial / on the first path. That line should be
>
>> export PATH=" /opt/local/bin: /opt/local/sbin:$PATH"

Actually there should not be spaces there. The line should read:

export PATH="/opt/local/bin:/opt/local/sbin:$PATH"

Did the MacPorts installer do this to your .bash_profile or did you  
set it up manually? If the former, then we have a bug in the setup  
script somewhere....


From ryandesign at macports.org  Mon Jan 12 22:02:39 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 13 Jan 2009 00:02:39 -0600
Subject: Reconfiguring WxWidgets
In-Reply-To: <4964D8C8.2060509@lobstersoft.com>
References: <4964D8C8.2060509@lobstersoft.com>
Message-ID: <6EB4E98E-58F9-485B-A975-9309BD0B1AE7@macports.org>


On Jan 7, 2009, at 10:31, Adrian Grigore wrote:

> I have successfully installed wxwidgets 2.8 using macports. I
> need a slightly different configuration of wxwidgets and have
> therefore edited the setup.h file accordingly. What's the easyest
> way to apply the new settings (i.e. recompile wxwidgets with the
> new setup.h file)?

You could:

port deactivate wxWidgets
port clean wxWidgets
port extract wxWidgets

Make whatever changes you want to the files in `port dir wxWidgets`/ 
work, then:

port install wxWidgets

These changes will of course not persist next time you reinstall or  
update wxWidgets.

What changes are you making? Would they be generally useful to the  
MacPorts population? If so, perhaps they can be incorporated into the  
wxWidgets portfile.



From ryandesign at macports.org  Mon Jan 12 22:06:56 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 13 Jan 2009 00:06:56 -0600
Subject: Error on environment?
In-Reply-To: <4b75340e0901111213y4659d0cayf735dd3ff8306d2d@mail.gmail.com>
References: <4b75340e0901111213y4659d0cayf735dd3ff8306d2d@mail.gmail.com>
Message-ID: <620755E6-E0FA-4A9B-B032-D048E268D507@macports.org>


On Jan 11, 2009, at 14:13, Doctor Who wrote:

> I installed the findutils and coreutils packages so that I could use
> locate on my Mac.

FYI, locate works fine on my Mac without installing anything extra  
with MacPorts... I'm on Tiger, though I've probably enabled something  
somewhere along the way to get this to work.


> When I attempt to update the database using
> 'updatedb', I get:
>
> /usr/bin/sort: string comparison failed: Illegal byte sequence
> /usr/bin/sort: Set LC_ALL='C' to work around the problem.
> /usr/bin/sort: The strings compared were
> `/APPLICATIONS/BURN.APP/CONTENTS/RESOURCES/JAPANESE.LPROJ/BURN
> ?\230?\253?\225?\232/TY/TASK_STYLE.CSS' and
> `/APPLICATIONS/BURN.APP/CONTENTS/RESOURCES/JAPANESE.LPROJ/ 
> CREDITS.HTML'.
>
> Hopefully someone can tell me how to fix this.

Is your LANG environment variable set to anything? If so, what? I  
assume you need to set it to a reasonable value for your terminal.  
For example, I set LANG to "en_US.UTF-8".




From brad at pixilla.com  Mon Jan 12 23:52:05 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Mon, 12 Jan 2009 23:52:05 -0800
Subject: perl5 install errors
In-Reply-To: <20090112120915.GQ14649@prunille.vinc17.org>
References: <798A7176-D7F1-4F46-AFFC-19445220CDBC@pixilla.com>
	<20090112120915.GQ14649@prunille.vinc17.org>
Message-ID: <19A0BA15-EDA5-40CD-B4EB-66D48CE118DF@pixilla.com>


On Jan 12, 2009, at 4:09 AM, Vincent Lefevre wrote:

> On 2009-01-11 21:18:52 -0800, Bradley Giesbrecht wrote:
>> While struggling to get perl5 reinstalled I noticed a lot of files
>> referencing /opt/local/bin/perl in /usr/share/bin.
>
> What do you mean by "referencing"? Do you have an example?

Sure, heres what surprises me:

bash-3.2# grep -R /opt/local/bin/ /usr/share/bin/
/usr/share/bin/c2ph:#!/opt/local/bin/perl
/usr/share/bin/c2ph:    eval 'exec /opt/local/bin/perl -S $0 ${1+"$@"}'
/usr/share/bin/corelist:#!/opt/local/bin/perl
/usr/share/bin/corelist:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/cpan:#!/opt/local/bin/perl
/usr/share/bin/cpan:    eval 'exec /opt/local/bin/perl -S $0 ${1+"$@"}'
/usr/share/bin/dprofpp:#!/opt/local/bin/perl
/usr/share/bin/enc2xs:#!/opt/local/bin/perl
/usr/share/bin/enc2xs:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/enc2xs.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/enc2xs.mp_1231737032:    eval 'exec /opt/local/bin/perl  
-S $0 ${1+"$@"}'
/usr/share/bin/find2perl:#!/opt/local/bin/perl
/usr/share/bin/find2perl:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/find2perl:/opt/local/bin/perl
/usr/share/bin/find2perl.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/find2perl.mp_1231737032:    eval 'exec /opt/local/bin/ 
perl -S $0 ${1+"$@"}'
/usr/share/bin/find2perl.mp_1231737032:/opt/local/bin/perl
/usr/share/bin/h2ph:#!/opt/local/bin/perl
/usr/share/bin/h2ph:    eval 'exec /opt/local/bin/perl -S $0 ${1+"$@"}'
/usr/share/bin/h2ph.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/h2ph.mp_1231737032:    eval 'exec /opt/local/bin/perl - 
S $0 ${1+"$@"}'
/usr/share/bin/h2xs:#!/opt/local/bin/perl
/usr/share/bin/h2xs:    eval 'exec /opt/local/bin/perl -S $0 ${1+"$@"}'
/usr/share/bin/h2xs.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/h2xs.mp_1231737032:    eval 'exec /opt/local/bin/perl - 
S $0 ${1+"$@"}'
/usr/share/bin/instmodsh:#!/opt/local/bin/perl
/usr/share/bin/instmodsh:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/instmodsh.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/instmodsh.mp_1231737032:    eval 'exec /opt/local/bin/ 
perl -S $0 ${1+"$@"}'
/usr/share/bin/libnetcfg:#!/opt/local/bin/perl
/usr/share/bin/libnetcfg:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/libnetcfg.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/libnetcfg.mp_1231737032:    eval 'exec /opt/local/bin/ 
perl -S $0 ${1+"$@"}'
/usr/share/bin/perlbug:#!/opt/local/bin/perl
/usr/share/bin/perlbug:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/perlbug.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/perlbug.mp_1231737032:    eval 'exec /opt/local/bin/ 
perl -S $0 ${1+"$@"}'
/usr/share/bin/perlcc:#!/opt/local/bin/perl
/usr/share/bin/perlcc:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/perlcc.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/perlcc.mp_1231737032:    eval 'exec /opt/local/bin/perl  
-S $0 ${1+"$@"}'
/usr/share/bin/perldoc:#!/opt/local/bin/perl
/usr/share/bin/perldoc:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/perldoc.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/perldoc.mp_1231737032:    eval 'exec /opt/local/bin/ 
perl -S $0 ${1+"$@"}'
/usr/share/bin/perlivp:#!/opt/local/bin/perl
/usr/share/bin/perlivp:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/perlivp:my $perlpath = '/opt/local/bin/perl';
/usr/share/bin/perlivp.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/perlivp.mp_1231737032:    eval 'exec /opt/local/bin/ 
perl -S $0 ${1+"$@"}'
/usr/share/bin/perlivp.mp_1231737032:my $perlpath = '/opt/local/bin/ 
perl';
/usr/share/bin/perlthanks:#!/opt/local/bin/perl
/usr/share/bin/perlthanks:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/piconv:#!/opt/local/bin/perl
/usr/share/bin/piconv:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/piconv.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/piconv.mp_1231737032:    eval 'exec /opt/local/bin/perl  
-S $0 ${1+"$@"}'
/usr/share/bin/pl2pm:#!/opt/local/bin/perl
/usr/share/bin/pl2pm:    eval 'exec /opt/local/bin/perl -S $0 ${1+"$@"}'
/usr/share/bin/pl2pm.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/pl2pm.mp_1231737032:    eval 'exec /opt/local/bin/perl - 
S $0 ${1+"$@"}'
/usr/share/bin/pod2html:#!/opt/local/bin/perl
/usr/share/bin/pod2html:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/pod2html.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/pod2html.mp_1231737032:    eval 'exec /opt/local/bin/ 
perl -S $0 ${1+"$@"}'
/usr/share/bin/pod2latex:#!/opt/local/bin/perl
/usr/share/bin/pod2latex:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/pod2latex.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/pod2latex.mp_1231737032:    eval 'exec /opt/local/bin/ 
perl -S $0 ${1+"$@"}'
/usr/share/bin/pod2man:#!/opt/local/bin/perl
/usr/share/bin/pod2man:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/pod2man.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/pod2man.mp_1231737032:    eval 'exec /opt/local/bin/ 
perl -S $0 ${1+"$@"}'
/usr/share/bin/pod2text:#!/opt/local/bin/perl
/usr/share/bin/pod2text:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/pod2text.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/pod2text.mp_1231737032:    eval 'exec /opt/local/bin/ 
perl -S $0 ${1+"$@"}'
/usr/share/bin/pod2usage:#!/opt/local/bin/perl
/usr/share/bin/pod2usage.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/podchecker:#!/opt/local/bin/perl
/usr/share/bin/podchecker.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/podselect:#!/opt/local/bin/perl
/usr/share/bin/podselect.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/prove:#!/opt/local/bin/perl
/usr/share/bin/prove:    eval 'exec /opt/local/bin/perl -S $0 ${1+"$@"}'
/usr/share/bin/prove.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/prove.mp_1231737032:    eval 'exec /opt/local/bin/perl - 
S $0 ${1+"$@"}'
/usr/share/bin/psed:#!/opt/local/bin/perl
/usr/share/bin/psed:    eval 'exec /opt/local/bin/perl -S $0 ${1+"$@"}'
/usr/share/bin/psed:#!/opt/local/bin/perl
/usr/share/bin/psed:/opt/local/bin/perl
/usr/share/bin/psed.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/psed.mp_1231737032:    eval 'exec /opt/local/bin/perl - 
S $0 ${1+"$@"}'
/usr/share/bin/psed.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/psed.mp_1231737032:/opt/local/bin/perl
/usr/share/bin/pstruct:#!/opt/local/bin/perl
/usr/share/bin/pstruct:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/pstruct.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/pstruct.mp_1231737032:    eval 'exec /opt/local/bin/ 
perl -S $0 ${1+"$@"}'
/usr/share/bin/s2p:#!/opt/local/bin/perl
/usr/share/bin/s2p:    eval 'exec /opt/local/bin/perl -S $0 ${1+"$@"}'
/usr/share/bin/s2p:#!/opt/local/bin/perl
/usr/share/bin/s2p:/opt/local/bin/perl
/usr/share/bin/s2p.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/s2p.mp_1231737032:    eval 'exec /opt/local/bin/perl -S  
$0 ${1+"$@"}'
/usr/share/bin/s2p.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/s2p.mp_1231737032:/opt/local/bin/perl
/usr/share/bin/splain:#!/opt/local/bin/perl
/usr/share/bin/splain:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/splain.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/splain.mp_1231737032:    eval 'exec /opt/local/bin/perl  
-S $0 ${1+"$@"}'
/usr/share/bin/xsubpp:#!/opt/local/bin/perl
/usr/share/bin/xsubpp:    eval 'exec /opt/local/bin/perl -S $0  
${1+"$@"}'
/usr/share/bin/xsubpp.mp_1231737032:#!/opt/local/bin/perl
/usr/share/bin/xsubpp.mp_1231737032:    eval 'exec /opt/local/bin/perl  
-S $0 ${1+"$@"}'
bash-3.2#

From brad at pixilla.com  Mon Jan 12 23:54:08 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Mon, 12 Jan 2009 23:54:08 -0800
Subject: gd2 fails on perl5
In-Reply-To: <496AF30B.2070006@macports.org>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
	<496AF30B.2070006@macports.org>
Message-ID: <86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>

On Jan 11, 2009, at 11:36 PM, Joshua Root wrote:

> Bradley Giesbrecht wrote:
>> I still don't understand why perl5 is writing anything to
>> /usr/share/bin. I've used fink, darwinports and now macports for  
>> years
>> and I thought they installed in complete isolation under /sw or / 
>> opt/local.
>
> Everything being under /opt/local is indeed the expected behaviour,  
> bar
> the few exceptions that have a good reason to install files elsewhere.
> And indeed that is the case for perl5.8 here, according to 'port
> contents perl5.8'.
>
> It really does look as though your prefix has somehow been set to
> /usr/share.



If it is I don't know where.

bash-3.2# env
SHELL=/bin/bash
TERM=xterm-color
USER=root
SUDO_USER=brad
SUDO_UID=501
SSH_AUTH_SOCK=/tmp/501/nl.uu.phil.SSHAgent.socket
__CF_USER_TEXT_ENCODING=0x1F5:0:0
PATH=/Users/brad/bin:/usr/local/mysql/bin:/opt/local/bin:/opt/local/ 
sbin:/usr/local/bin:/usr/local/sbin:/usr/share/bin:/usr/local/php5/ 
bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
PWD=/Users/brad/Sandbox/pecl/runkit
LANG=en_US.UTF-8
SHLVL=1
SUDO_COMMAND=/bin/bash
HOME=/Users/brad
LOGNAME=root
SUDO_GID=501
DISPLAY=/tmp/launch-UjAiw0/:0
_=/usr/bin/env
OLDPWD=/Users/brad


bash-3.2# grep -R prefix /opt/local/etc/macports/
/opt/local/etc/macports/macports.conf:prefix			/opt/local
/opt/local/etc/macports/macports.conf:x11prefix		/usr/X11
/opt/local/etc/macports/variants.conf:# in the system wide ${prefix}/ 
etc/macports/macports.conf


bash-3.2# grep -R /usr/share /opt/local/etc/macports/


bash-3.2# cat ~/.profile
bind -x '"\C-p"':'echo $PWD'

PS1='\h: \u\$ '

alias ls='ls -G'
alias tclsh='rlwrap tclsh'

export PATH=~/bin:/usr/local/mysql/bin:/opt/local/bin:/opt/local/sbin:/ 
usr/local/bin:/usr/local/sbin:/usr/share/bin:/usr/local/php5/bin:$PATH
export MANPATH=/opt/local/share/man:/usr/local/ch5.5.0/docs/man:$MANPATH


bash-3.2# cat /etc/profile
# System-wide .profile for sh(1)

if [ -x /usr/libexec/path_helper ]; then
	eval `/usr/libexec/path_helper -s`
fi

if [ "${BASH-no}" != "no" ]; then
	[ -r /etc/bashrc ] && . /etc/bashrc
fi


bash-3.2# cat /etc/bashrc
# System-wide .bashrc file for interactive bash(1) shells.
if [ -z "$PS1" ]; then
   return
fi

PS1='\h:\W \u\$ '
# Make bash check its window size after a process completes
shopt -s checkwinsize

From kngspook at gmail.com  Tue Jan 13 01:32:44 2009
From: kngspook at gmail.com (Neil)
Date: Tue, 13 Jan 2009 01:32:44 -0800
Subject: Using Macports libraries in Xcode gcc
In-Reply-To: <4969026B.1050401@macports.org>
References: <758644.11599.qm@web65703.mail.ac4.yahoo.com>
	<4969026B.1050401@macports.org>
Message-ID: <77e4079b0901130132u65ccb42dv8ec8c260871d338b@mail.gmail.com>

On Sat, Jan 10, 2009 at 12:17 PM, Joshua Root <jmr at macports.org> wrote:
> Vince Rice wrote:
>> OS X 10.5.6, Macports 1.7, gcc 4.0.1 from Xcode 3.1.2
>>
>> The FAQ address why Macports installs its own libraries, etc. I have the opposite question, and I read the FAQ and tried searching a couple of months of maillist archives and couldn't find it. My apologies if I missed it.
>>
>> I have a program I want to compile that needs popt. I've downloaded the Macports popt package, and now have the popt.h in /opt/local/include, the library in /opt/local/lib, etc.
>>
>> My question is what I have to do to my gcc setup to get it to "see" the Macport installed libraries (not just popt, but any other libraries I might download). I've tried adding the -I and -L's to the gcc command, and the popt.h is found, but it complains about the library, e.g.
>> ld: library not found for -l/opt/local/lib/popt
>>
>> I see that /opt/local/lib has libpopt.a, libpopt.la, and libpopt.0.0.0.dylib, which is similar to the other libraries. I didn't think I needed to specify "-L libpopt", but that gcc automatically added the lib prefix to the library. But, just in case, I tried adding it myself, but that didn't work, either.
>>
>> An example command line of something I'm trying to compile:
>> gcc -g -O2 -o src/ascii/ascii src/ascii/ascii.o  -l/opt/local/lib/libpopt
>>
>> Please don't point out that there's a version of ascii in Macport -- I know that, I'm just using this as an example of trying to get a Macport library working in general gcc. :)
>>
>> Thanks very much for your help.
>
> Looks like you're mixing up -l and -L. The former is used like '-lpopt',
> the latter like '-L/opt/local/lib'.
>

My .bash_profile :
# Add MacPorts directories, if they exist.
if [ -d /opt/local ]; then
	export PATH=/opt/local/bin:/opt/local/sbin:$PATH
	export MANPATH=/opt/local/share/man:$MANPATH
	export C_INCLUDE_PATH=/opt/local/include
	export CPLUS_INCLUDE_PATH=/opt/local/include
	alias gcc="gcc -I/opt/local/include -L/opt/local/lib"
	alias g++="g++ -I/opt/local/include -L/opt/local/lib"
	# if [ -f /opt/local/etc/bash_completion ]; then
	# 	. /opt/local/etc/bash_completion
	# fi
fi

IIRC, C_INCLUDE_PATH/CPLUS_INCLUDE_PATH alone didn't work, and thus I
added the aliases.  But now that I think about it, I should be able to
remove the former and the later should do everything on it's own.  I'm
going to try that, I think...

Naturally, YMMV/UAYOR/IANAL/etc.

-Neil.

From whodoctor at gmail.com  Tue Jan 13 06:50:45 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Tue, 13 Jan 2009 09:50:45 -0500
Subject: Error on environment?
In-Reply-To: <620755E6-E0FA-4A9B-B032-D048E268D507@macports.org>
References: <4b75340e0901111213y4659d0cayf735dd3ff8306d2d@mail.gmail.com>
	<620755E6-E0FA-4A9B-B032-D048E268D507@macports.org>
Message-ID: <4b75340e0901130650i325adfb4i978547e8e03979f7@mail.gmail.com>

On Tue, Jan 13, 2009 at 1:06 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
>
> On Jan 11, 2009, at 14:13, Doctor Who wrote:
>
>> I installed the findutils and coreutils packages so that I could use
>> locate on my Mac.
>
> FYI, locate works fine on my Mac without installing anything extra with
> MacPorts... I'm on Tiger, though I've probably enabled something somewhere
> along the way to get this to work.
>
>
>> When I attempt to update the database using
>> 'updatedb', I get:
>>
>> /usr/bin/sort: string comparison failed: Illegal byte sequence
>> /usr/bin/sort: Set LC_ALL='C' to work around the problem.
>> /usr/bin/sort: The strings compared were
>> `/APPLICATIONS/BURN.APP/CONTENTS/RESOURCES/JAPANESE.LPROJ/BURN
>> ?\230?\253?\225?\232/TY/TASK_STYLE.CSS' and
>> `/APPLICATIONS/BURN.APP/CONTENTS/RESOURCES/JAPANESE.LPROJ/CREDITS.HTML'.
>>
>> Hopefully someone can tell me how to fix this.
>
> Is your LANG environment variable set to anything? If so, what? I assume you
> need to set it to a reasonable value for your terminal. For example, I set
> LANG to "en_US.UTF-8".
>

Thanks, where should this setting be?

From ryandesign at macports.org  Tue Jan 13 16:40:45 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 13 Jan 2009 18:40:45 -0600
Subject: install trouble Mac OSX 10.4
In-Reply-To: <80a464360901130732l2ff27fqe8dcb3286898cb85@mail.gmail.com>
References: <80a464360901120639t5f1e63c8mcecb4f7007d8a50a@mail.gmail.com>
	<15E3CA49-71A4-4028-998B-D24C91A30CFD@cern.ch>
	<06249CBC-ED84-404E-A242-4FB055A903C4@macports.org>
	<80a464360901130732l2ff27fqe8dcb3286898cb85@mail.gmail.com>
Message-ID: <8F85279E-5351-4347-9DA0-12B1DECCDFCB@macports.org>


On Jan 13, 2009, at 09:32, jason white wrote:

> On Mon, Jan 12, 2009 at 11:59 PM, Ryan Schmidt wrote:
>
>>>> the entry in my .bash_profile is:
>>>>
>>>> export PATH=" opt/local/bin: /opt/local/sbin:$PATH"
>>>
>>> You are missing an initial / on the first path. That line should be
>>>
>>> export PATH=" /opt/local/bin: /opt/local/sbin:$PATH"
>>
>> Actually there should not be spaces there. The line should read:
>>
>> export PATH="/opt/local/bin:/opt/local/sbin:$PATH"
>>
>> Did the MacPorts installer do this to your .bash_profile or did  
>> you set it up manually? If the former, then we have a bug in the  
>> setup script somewhere....
>
> I did a complete reinstall of MacOS 10.4 and applied all of the  
> updates. Then I installed XCode, and used all of the defaults for  
> the install. After that I installed MacPorts 1.6 using the  
> installer from the MacPorts site. After the install was completed I  
> looked for the .bash_profile file, and could not find it. Should i  
> create a new file? I believe i created the file manually last time.

The MacPorts 1.6.0 installer has a bug that it does not set up  
the .profile for you. This was fixed in MacPorts 1.7.0, which is the  
version you should be using. Please see:

http://trac.macports.org/wiki/ProblemHotlist#a.profilenotsetup

P.S: Use Reply All so your reply goes to the list too, not just to me.


From ryandesign at macports.org  Tue Jan 13 16:45:44 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 13 Jan 2009 18:45:44 -0600
Subject: Error on environment?
In-Reply-To: <4b75340e0901130650i325adfb4i978547e8e03979f7@mail.gmail.com>
References: <4b75340e0901111213y4659d0cayf735dd3ff8306d2d@mail.gmail.com>
	<620755E6-E0FA-4A9B-B032-D048E268D507@macports.org>
	<4b75340e0901130650i325adfb4i978547e8e03979f7@mail.gmail.com>
Message-ID: <649A10D1-E8D8-4579-940B-1650A655E3BA@macports.org>

On Jan 13, 2009, at 08:50, Doctor Who wrote:

> On Tue, Jan 13, 2009 at 1:06 AM, Ryan Schmidt wrote:
>
>> On Jan 11, 2009, at 14:13, Doctor Who wrote:
>>
>>> I installed the findutils and coreutils packages so that I could use
>>> locate on my Mac.
>>
>> FYI, locate works fine on my Mac without installing anything extra  
>> with
>> MacPorts... I'm on Tiger, though I've probably enabled something  
>> somewhere
>> along the way to get this to work.
>>
>>
>>> When I attempt to update the database using
>>> 'updatedb', I get:
>>>
>>> /usr/bin/sort: string comparison failed: Illegal byte sequence
>>> /usr/bin/sort: Set LC_ALL='C' to work around the problem.
>>> /usr/bin/sort: The strings compared were
>>> `/APPLICATIONS/BURN.APP/CONTENTS/RESOURCES/JAPANESE.LPROJ/BURN
>>> ?\230?\253?\225?\232/TY/TASK_STYLE.CSS' and
>>> `/APPLICATIONS/BURN.APP/CONTENTS/RESOURCES/JAPANESE.LPROJ/ 
>>> CREDITS.HTML'.
>>>
>>> Hopefully someone can tell me how to fix this.
>>
>> Is your LANG environment variable set to anything? If so, what? I  
>> assume you
>> need to set it to a reasonable value for your terminal. For  
>> example, I set
>> LANG to "en_US.UTF-8".
>
> Thanks, where should this setting be?

Type "export LANG=en_US.UTF-8". Then try updatedb again. If it works,  
you'll know that was it, and it would be a good idea to modify your  
shell startup file to include that line to set LANG for you. Your  
shell startup file might be ~/.profile or ~/.bash_profile or possibly  
others; I'm sure the Bash documentation has a complete list of all  
the files it checks at launch time.



From ryandesign at macports.org  Tue Jan 13 16:47:21 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 13 Jan 2009 18:47:21 -0600
Subject: perl5 install errors
In-Reply-To: <19A0BA15-EDA5-40CD-B4EB-66D48CE118DF@pixilla.com>
References: <798A7176-D7F1-4F46-AFFC-19445220CDBC@pixilla.com>
	<20090112120915.GQ14649@prunille.vinc17.org>
	<19A0BA15-EDA5-40CD-B4EB-66D48CE118DF@pixilla.com>
Message-ID: <8190FDD1-E826-495F-AF15-273B79D1B5C6@macports.org>


On Jan 13, 2009, at 01:52, Bradley Giesbrecht wrote:

> On Jan 12, 2009, at 4:09 AM, Vincent Lefevre wrote:
>
>> On 2009-01-11 21:18:52 -0800, Bradley Giesbrecht wrote:
>>> While struggling to get perl5 reinstalled I noticed a lot of files
>>> referencing /opt/local/bin/perl in /usr/share/bin.
>>
>> What do you mean by "referencing"? Do you have an example?
>
> Sure, heres what surprises me:
>
> bash-3.2# grep -R /opt/local/bin/ /usr/share/bin/
> /usr/share/bin/c2ph:#!/opt/local/bin/perl
> /usr/share/bin/c2ph:    eval 'exec /opt/local/bin/perl -S $0 ${1 
> +"$@"}'

[snip]

You've got it the other way around: you're searching for the string "/ 
opt/local/bin/" inside all the files located in the directory /usr/ 
share/bin/, and are finding lots of matches.

It looks to me like you have MacPorts installed in /opt/local/bin,  
but for some reason have set a symlink /usr/share/bin pointing to / 
opt/local/bin. You should delete that symlink.


From ryandesign at macports.org  Tue Jan 13 16:52:07 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 13 Jan 2009 18:52:07 -0600
Subject: gd2 fails on perl5
In-Reply-To: <86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
	<496AF30B.2070006@macports.org>
	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>
Message-ID: <DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>

On Jan 13, 2009, at 01:54, Bradley Giesbrecht wrote:

> On Jan 11, 2009, at 11:36 PM, Joshua Root wrote:
>
>> It really does look as though your prefix has somehow been set to
>> /usr/share.
>
> If it is I don't know where.
>
> bash-3.2# env
> SHELL=/bin/bash
> TERM=xterm-color
> USER=root
> SUDO_USER=brad
> SUDO_UID=501
> SSH_AUTH_SOCK=/tmp/501/nl.uu.phil.SSHAgent.socket
> __CF_USER_TEXT_ENCODING=0x1F5:0:0
> PATH=/Users/brad/bin:/usr/local/mysql/bin:/opt/local/bin:/opt/local/ 
> sbin:/usr/local/bin:/usr/local/sbin:/usr/share/bin:/usr/local/php5/ 
> bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin

I see /usr/share/bin in your PATH.



> bash-3.2# cat ~/.profile
> bind -x '"\C-p"':'echo $PWD'
>
> PS1='\h: \u\$ '
>
> alias ls='ls -G'
> alias tclsh='rlwrap tclsh'
>
> export PATH=~/bin:/usr/local/mysql/bin:/opt/local/bin:/opt/local/ 
> sbin:/usr/local/bin:/usr/local/sbin:/usr/share/bin:/usr/local/php5/ 
> bin:$PATH
> export MANPATH=/opt/local/share/man:/usr/local/ch5.5.0/docs/man: 
> $MANPATH

You should get /usr/share/bin out of that PATH statement.

Also, remove /usr/local/bin and /usr/local/sbin. It is not supported  
to have anything installed in the prefix /usr/local while using  
MacPorts; it causes problems for many ports. You should remove any  
software in /usr/local/{bin,include,lib,man,share} and install it  
using MacPorts instead. (Any other prefix, including any subdirectory  
of /usr/local, is fine; it's just /usr/local itself that's  
problematic. So there's no problem with keeping /usr/local/php5/bin  
or /usr/local/mysql/bin in the PATH. Though php5 and mysql5 are of  
course available through MacPorts as well.)



From mouse9911 at gmail.com  Tue Jan 13 22:51:21 2009
From: mouse9911 at gmail.com (Michael Dzamba)
Date: Wed, 14 Jan 2009 06:51:21 +0000 (UTC)
Subject: openMP support
Message-ID: <loom.20090114T064744-676@post.gmane.org>

Hi Everyone,
This is my first time posting here, not sure how this really works. 
I am having trouble compiling and 
application I wrote that uses openMP under OSX. 
I have installed GCC 4.3.2 and tried to compile with 
this, but during linking i get an error,

gcc-mp-4.3  -fopenmp -lm -w -DNDEBUG ../bin/simpleStack.o 
../bin/nodeArray.o ../bin/reader.o 
../bin/nodeMarker.o ../bin/suffixTreePrinter.o ../bin/suffixTree.o 
../bin/readAndScore.o ../bin/score.o 
../bin/weeder_score.o ../bin/common.o ../bin/display.o ../bin/sad.o 
../bin/generalTable.o 
../bin/bitString.o ../bin/suffixTreeSA.o -o ../bin/suffixTreeSA
Undefined symbols:
  "___emutls_get_address", referenced from:
      _sc_mem2mem in readAndScore.o
      _sc_mem2mem.omp_fn.0 in readAndScore.o
      _sc_mem2mem.omp_fn.0 in readAndScore.o
      _score_freqWild in score.o
      _score_freqWild in score.o
      _score_freqWild in score.o
      _score_freqWild in score.o
      _score_freqWild in score.o
      _score_freqWild in score.o
      _score_freqWild in score.o
      _score_freqWild in score.o
      _weeder_freqWild in weeder_score.o
      _weeder_freqWild in weeder_score.o
      _weeder_freqWild in weeder_score.o
      _weeder_freqWild in weeder_score.o
      _weeder_freqWild in weeder_score.o
      _weeder_freqWild in weeder_score.o
      _weeder_freqWild in weeder_score.o
      _weeder_freqWild in weeder_score.o
      _weeder_freqWild in weeder_score.o
      _common_compressScoreData in common.o
      _common_compressScoreData in common.o
      _common_compressScoreData in common.o
      _common_compressScoreData in common.o
      _common_findStart in common.o
      _common_addToPrintQ in common.o
      _common_addToPrintQ in common.o
      _common_addToPrintQ in common.o
      _main.omp_fn.0 in suffixTreeSA.o
      _main.omp_fn.0 in suffixTreeSA.o
      _main.omp_fn.0 in suffixTreeSA.o
      _main.omp_fn.0 in suffixTreeSA.o
  "___emutls_register_common", referenced from:
      global constructors keyed to 65535_0_readAndScore.c in readAndScore.o
      global constructors keyed to 65535_0_score.c in score.o
      global constructors keyed to 65535_0_weeder_score.c in weeder_score.o
      global constructors keyed to 65535_0_common.c in common.o
      global constructors keyed to 65535_0_sad.c in sad.o
      global constructors keyed to 65535_0_suffixTreeSA.c in suffixTreeSA.o
ld: symbol(s) not found
collect2: ld returned 1 exit status

I have read this post here http://gcc.gnu.org/ml/gcc/2008-12/msg00145.html ,
 and it seems to be 
similar, does anyone know how I can overcome this problem?

Thanks!


From jmr at macports.org  Tue Jan 13 23:57:33 2009
From: jmr at macports.org (Joshua Root)
Date: Wed, 14 Jan 2009 18:57:33 +1100
Subject: Error on environment?
In-Reply-To: <649A10D1-E8D8-4579-940B-1650A655E3BA@macports.org>
References: <4b75340e0901111213y4659d0cayf735dd3ff8306d2d@mail.gmail.com>	<620755E6-E0FA-4A9B-B032-D048E268D507@macports.org>	<4b75340e0901130650i325adfb4i978547e8e03979f7@mail.gmail.com>
	<649A10D1-E8D8-4579-940B-1650A655E3BA@macports.org>
Message-ID: <496D9AED.3020505@macports.org>

Ryan Schmidt wrote:
> On Jan 13, 2009, at 08:50, Doctor Who wrote:
> 
>> On Tue, Jan 13, 2009 at 1:06 AM, Ryan Schmidt wrote:
>>
>>> On Jan 11, 2009, at 14:13, Doctor Who wrote:
>>>
>>>> I installed the findutils and coreutils packages so that I could use
>>>> locate on my Mac.
>>>
>>> FYI, locate works fine on my Mac without installing anything extra with
>>> MacPorts... I'm on Tiger, though I've probably enabled something
>>> somewhere
>>> along the way to get this to work.
>>>
>>>
>>>> When I attempt to update the database using
>>>> 'updatedb', I get:
>>>>
>>>> /usr/bin/sort: string comparison failed: Illegal byte sequence
>>>> /usr/bin/sort: Set LC_ALL='C' to work around the problem.
>>>> /usr/bin/sort: The strings compared were
>>>> `/APPLICATIONS/BURN.APP/CONTENTS/RESOURCES/JAPANESE.LPROJ/BURN
>>>> ?\230?\253?\225?\232/TY/TASK_STYLE.CSS' and
>>>> `/APPLICATIONS/BURN.APP/CONTENTS/RESOURCES/JAPANESE.LPROJ/CREDITS.HTML'.
>>>>
>>>>
>>>> Hopefully someone can tell me how to fix this.
>>>
>>> Is your LANG environment variable set to anything? If so, what? I
>>> assume you
>>> need to set it to a reasonable value for your terminal. For example,
>>> I set
>>> LANG to "en_US.UTF-8".
>>
>> Thanks, where should this setting be?
> 
> Type "export LANG=en_US.UTF-8". Then try updatedb again. If it works,
> you'll know that was it, and it would be a good idea to modify your
> shell startup file to include that line to set LANG for you. Your shell
> startup file might be ~/.profile or ~/.bash_profile or possibly others;
> I'm sure the Bash documentation has a complete list of all the files it
> checks at launch time.

There are a couple of relevant settings in Terminal.app's preferences
which may be preferable to setting LANG manually.

- Josh

From brad at pixilla.com  Wed Jan 14 00:15:56 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Wed, 14 Jan 2009 00:15:56 -0800
Subject: gd2 fails on perl5
In-Reply-To: <DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
	<496AF30B.2070006@macports.org>
	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>
	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
Message-ID: <E64CACC4-E227-4E6D-8A96-80190EA362B8@pixilla.com>


On Jan 13, 2009, at 4:52 PM, Ryan Schmidt wrote:

> On Jan 13, 2009, at 01:54, Bradley Giesbrecht wrote:
>
>> On Jan 11, 2009, at 11:36 PM, Joshua Root wrote:
>>
>>> It really does look as though your prefix has somehow been set to
>>> /usr/share.
>>
>> If it is I don't know where.
>>
>> bash-3.2# env
>> SHELL=/bin/bash
>> TERM=xterm-color
>> USER=root
>> SUDO_USER=brad
>> SUDO_UID=501
>> SSH_AUTH_SOCK=/tmp/501/nl.uu.phil.SSHAgent.socket
>> __CF_USER_TEXT_ENCODING=0x1F5:0:0
>> PATH=/Users/brad/bin:/usr/local/mysql/bin:/opt/local/bin:/opt/local/ 
>> sbin:/usr/local/bin:/usr/local/sbin:/usr/share/bin:/usr/local/php5/ 
>> bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
>
> I see /usr/share/bin in your PATH.
>
>
>
>> bash-3.2# cat ~/.profile
>> bind -x '"\C-p"':'echo $PWD'
>>
>> PS1='\h: \u\$ '
>>
>> alias ls='ls -G'
>> alias tclsh='rlwrap tclsh'
>>
>> export PATH=~/bin:/usr/local/mysql/bin:/opt/local/bin:/opt/local/ 
>> sbin:/usr/local/bin:/usr/local/sbin:/usr/share/bin:/usr/local/php5/ 
>> bin:$PATH
>> export MANPATH=/opt/local/share/man:/usr/local/ch5.5.0/docs/man: 
>> $MANPATH
>
> You should get /usr/share/bin out of that PATH statement.
>
> Also, remove /usr/local/bin and /usr/local/sbin. It is not supported  
> to have anything installed in the prefix /usr/local while using  
> MacPorts; it causes problems for many ports. You should remove any  
> software in /usr/local/{bin,include,lib,man,share} and install it  
> using MacPorts instead. (Any other prefix, including any  
> subdirectory of /usr/local, is fine; it's just /usr/local itself  
> that's problematic. So there's no problem with keeping /usr/local/ 
> php5/bin or /usr/local/mysql/bin in the PATH. Though php5 and mysql5  
> are of course available through MacPorts as well.)



BlackBook: brad$ env
MANPATH=/opt/local/share/man:/usr/share/man:/usr/local/share/man:/usr/ 
X11/man
TERM_PROGRAM=Apple_Terminal
TERM=xterm-color
SHELL=/bin/bash
TMPDIR=/var/folders/ix/ix1uNqEcEqms60M75qQFVE+++TI/-Tmp-/
Apple_PubSub_Socket_Render=/tmp/launch-0KI1Ha/Render
TERM_PROGRAM_VERSION=240
USER=brad
COMMAND_MODE=unix2003
SSH_AUTH_SOCK=/tmp/501/nl.uu.phil.SSHAgent.socket
__CF_USER_TEXT_ENCODING=0x1F5:0:0
PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/ 
X11/bin
PWD=/Users/brad
LANG=en_US.UTF-8
SHLVL=1
HOME=/Users/brad
LOGNAME=brad
DISPLAY=/tmp/launch-UjAiw0/:0
SECURITYSESSIONID=d3a430
_=/usr/bin/env

BlackBook: brad$ ls /usr/share/bin/
pear_osx

BlackBook: brad$ port installed
No ports are installed.

BlackBook: brad$ sudo port install perl5
--->  Fetching perl5.8
--->  Attempting to fetch perl-5.8.9.tar.bz2 from http://www.cpan.org/src/
--->  Verifying checksum(s) for perl5.8
--->  Extracting perl5.8
--->  Configuring perl5.8
--->  Building perl5.8
--->  Staging perl5.8 into destroot
Warning: violation by /usr
Warning: perl5.8 violates the layout of the ports-filesystems!
Warning: Please fix or indicate this misbehavior (if it is intended),  
it will be an error in future releases!
--->  Installing perl5.8 @5.8.9_1
--->  Activating perl5.8 @5.8.9_1
--->  Cleaning perl5.8
--->  Fetching perl5
--->  Verifying checksum(s) for perl5
--->  Extracting perl5
--->  Configuring perl5
--->  Building perl5
--->  Staging perl5 into destroot
--->  Installing perl5 @5.8.9_0
--->  Activating perl5 @5.8.9_0
--->  Cleaning perl5

BlackBook: brad$ ls /usr/share/bin/
c2ph       dprofpp    h2ph       libnetcfg  perlcc     perlthanks  
pod2html   pod2text   podselect  pstruct    xsubpp
corelist   enc2xs     h2xs       pear_osx   perldoc    piconv      
pod2latex  pod2usage  prove      s2p
cpan       find2perl  instmodsh  perlbug    perlivp    pl2pm       
pod2man    podchecker psed       splain
BlackBook: brad$


From brad at pixilla.com  Wed Jan 14 00:16:46 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Wed, 14 Jan 2009 00:16:46 -0800
Subject: gd2 fails on perl5
In-Reply-To: <DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
	<496AF30B.2070006@macports.org>
	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>
	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
Message-ID: <B681B217-F416-47D4-823B-70B258877268@pixilla.com>


On Jan 13, 2009, at 4:52 PM, Ryan Schmidt wrote:

> On Jan 13, 2009, at 01:54, Bradley Giesbrecht wrote:
>
>> On Jan 11, 2009, at 11:36 PM, Joshua Root wrote:
>>
>>> It really does look as though your prefix has somehow been set to
>>> /usr/share.
>>
>> If it is I don't know where.
>>
>> bash-3.2# env
>> SHELL=/bin/bash
>> TERM=xterm-color
>> USER=root
>> SUDO_USER=brad
>> SUDO_UID=501
>> SSH_AUTH_SOCK=/tmp/501/nl.uu.phil.SSHAgent.socket
>> __CF_USER_TEXT_ENCODING=0x1F5:0:0
>> PATH=/Users/brad/bin:/usr/local/mysql/bin:/opt/local/bin:/opt/local/ 
>> sbin:/usr/local/bin:/usr/local/sbin:/usr/share/bin:/usr/local/php5/ 
>> bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
>
> I see /usr/share/bin in your PATH.
>
>
>
>> bash-3.2# cat ~/.profile
>> bind -x '"\C-p"':'echo $PWD'
>>
>> PS1='\h: \u\$ '
>>
>> alias ls='ls -G'
>> alias tclsh='rlwrap tclsh'
>>
>> export PATH=~/bin:/usr/local/mysql/bin:/opt/local/bin:/opt/local/ 
>> sbin:/usr/local/bin:/usr/local/sbin:/usr/share/bin:/usr/local/php5/ 
>> bin:$PATH
>> export MANPATH=/opt/local/share/man:/usr/local/ch5.5.0/docs/man: 
>> $MANPATH
>
> You should get /usr/share/bin out of that PATH statement.
>
> Also, remove /usr/local/bin and /usr/local/sbin. It is not supported  
> to have anything installed in the prefix /usr/local while using  
> MacPorts; it causes problems for many ports. You should remove any  
> software in /usr/local/{bin,include,lib,man,share} and install it  
> using MacPorts instead. (Any other prefix, including any  
> subdirectory of /usr/local, is fine; it's just /usr/local itself  
> that's problematic. So there's no problem with keeping /usr/local/ 
> php5/bin or /usr/local/mysql/bin in the PATH. Though php5 and mysql5  
> are of course available through MacPorts as well.)

Macports versions and variants of mysql and php do not get me what I  
need.

The use of /usr/local is so prevalent I'm surprised to hear that I  
should not use /usr/local and macports at the same time. Seems  
everything I build on freebsd using freebsd ports installs there to / 
usr/local. Most unix software that isn't available using macports  
installs to /usr/local.

If a macports package want's to use something outside /opt/local that  
is available and fit's the need I think that's fine.

Is it possible to keep macports file writes confined to /opt/local  
regardless of where the files it uses to build are located?

Do you have this file on your system which on mine is called called  
from /etc/profile?
/usr/libexec/path_helper
This script reads paths to env from /etc/paths.

I don't ever remembering editing it but along with /bin and /usr/bin  
was /usr/local/bin.

//brad

From simon at hitzemann.org  Wed Jan 14 00:29:19 2009
From: simon at hitzemann.org (Simon Hitzemann)
Date: Wed, 14 Jan 2009 09:29:19 +0100 (CET)
Subject: openMP support
In-Reply-To: <loom.20090114T064744-676@post.gmane.org>
References: <loom.20090114T064744-676@post.gmane.org>
Message-ID: <3ad1f57de4f8dd243fac2402c27f8439.squirrel@www.hitzemann.org>

Hi Michael,

On Wed, January 14, 2009 7:51 am, Michael Dzamba wrote:
> Hi Everyone,
> This is my first time posting here, not sure how this really works.
> I am having trouble compiling and
> application I wrote that uses openMP under OSX.
> I have installed GCC 4.3.2 and tried to compile with
> this, but during linking i get an error,
>
> gcc-mp-4.3  -fopenmp -lm -w -DNDEBUG ../bin/simpleStack.o
> ../bin/nodeArray.o ../bin/reader.o
> ../bin/nodeMarker.o ../bin/suffixTreePrinter.o ../bin/suffixTree.o
> ../bin/readAndScore.o ../bin/score.o
> ../bin/weeder_score.o ../bin/common.o ../bin/display.o ../bin/sad.o
> ../bin/generalTable.o
> ../bin/bitString.o ../bin/suffixTreeSA.o -o ../bin/suffixTreeSA

I didn't have any such problems with gcc-mp-4.3. Please try linking your
result against an OpenMP librarly (e.g. adding -lgomp to your
compiler/linker flags). I guess the errors will go away then.

Regards,
Simon


From jmr at macports.org  Wed Jan 14 01:22:43 2009
From: jmr at macports.org (Joshua Root)
Date: Wed, 14 Jan 2009 20:22:43 +1100
Subject: gd2 fails on perl5
In-Reply-To: <E64CACC4-E227-4E6D-8A96-80190EA362B8@pixilla.com>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>	<496AD51B.4020605@macports.org>	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>	<496AF30B.2070006@macports.org>	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
	<E64CACC4-E227-4E6D-8A96-80190EA362B8@pixilla.com>
Message-ID: <496DAEE3.2060204@macports.org>

Bradley Giesbrecht wrote:
> BlackBook: brad$ env
> MANPATH=/opt/local/share/man:/usr/share/man:/usr/local/share/man:/usr/X11/man
> 
> TERM_PROGRAM=Apple_Terminal
> TERM=xterm-color
> SHELL=/bin/bash
> TMPDIR=/var/folders/ix/ix1uNqEcEqms60M75qQFVE+++TI/-Tmp-/
> Apple_PubSub_Socket_Render=/tmp/launch-0KI1Ha/Render
> TERM_PROGRAM_VERSION=240
> USER=brad
> COMMAND_MODE=unix2003
> SSH_AUTH_SOCK=/tmp/501/nl.uu.phil.SSHAgent.socket
> __CF_USER_TEXT_ENCODING=0x1F5:0:0
> PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin
> 
> PWD=/Users/brad
> LANG=en_US.UTF-8
> SHLVL=1
> HOME=/Users/brad
> LOGNAME=brad
> DISPLAY=/tmp/launch-UjAiw0/:0
> SECURITYSESSIONID=d3a430
> _=/usr/bin/env
> 
> BlackBook: brad$ ls /usr/share/bin/
> pear_osx
> 
> BlackBook: brad$ port installed
> No ports are installed.
> 
> BlackBook: brad$ sudo port install perl5
> --->  Fetching perl5.8
> --->  Attempting to fetch perl-5.8.9.tar.bz2 from http://www.cpan.org/src/
> --->  Verifying checksum(s) for perl5.8
> --->  Extracting perl5.8
> --->  Configuring perl5.8
> --->  Building perl5.8
> --->  Staging perl5.8 into destroot
> Warning: violation by /usr
> Warning: perl5.8 violates the layout of the ports-filesystems!
> Warning: Please fix or indicate this misbehavior (if it is intended), it
> will be an error in future releases!
> --->  Installing perl5.8 @5.8.9_1
> --->  Activating perl5.8 @5.8.9_1
> --->  Cleaning perl5.8
> --->  Fetching perl5
> --->  Verifying checksum(s) for perl5
> --->  Extracting perl5
> --->  Configuring perl5
> --->  Building perl5
> --->  Staging perl5 into destroot
> --->  Installing perl5 @5.8.9_0
> --->  Activating perl5 @5.8.9_0
> --->  Cleaning perl5
> 
> BlackBook: brad$ ls /usr/share/bin/
> c2ph       dprofpp    h2ph       libnetcfg  perlcc     perlthanks
> pod2html   pod2text   podselect  pstruct    xsubpp
> corelist   enc2xs     h2xs       pear_osx   perldoc    piconv    
> pod2latex  pod2usage  prove      s2p
> cpan       find2perl  instmodsh  perlbug    perlivp    pl2pm     
> pod2man    podchecker psed       splain
> BlackBook: brad$

How about `ls -ld /usr/share/bin /opt/local /opt/local/bin`?

- Josh

From jmr at macports.org  Wed Jan 14 01:26:46 2009
From: jmr at macports.org (Joshua Root)
Date: Wed, 14 Jan 2009 20:26:46 +1100
Subject: gd2 fails on perl5
In-Reply-To: <496DAEE3.2060204@macports.org>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>	<496AD51B.4020605@macports.org>	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>	<496AF30B.2070006@macports.org>	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>	<E64CACC4-E227-4E6D-8A96-80190EA362B8@pixilla.com>
	<496DAEE3.2060204@macports.org>
Message-ID: <496DAFD6.9040402@macports.org>

Joshua Root wrote:
> Bradley Giesbrecht wrote:
>> BlackBook: brad$ env
>> MANPATH=/opt/local/share/man:/usr/share/man:/usr/local/share/man:/usr/X11/man
>>
>> TERM_PROGRAM=Apple_Terminal
>> TERM=xterm-color
>> SHELL=/bin/bash
>> TMPDIR=/var/folders/ix/ix1uNqEcEqms60M75qQFVE+++TI/-Tmp-/
>> Apple_PubSub_Socket_Render=/tmp/launch-0KI1Ha/Render
>> TERM_PROGRAM_VERSION=240
>> USER=brad
>> COMMAND_MODE=unix2003
>> SSH_AUTH_SOCK=/tmp/501/nl.uu.phil.SSHAgent.socket
>> __CF_USER_TEXT_ENCODING=0x1F5:0:0
>> PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin
>>
>> PWD=/Users/brad
>> LANG=en_US.UTF-8
>> SHLVL=1
>> HOME=/Users/brad
>> LOGNAME=brad
>> DISPLAY=/tmp/launch-UjAiw0/:0
>> SECURITYSESSIONID=d3a430
>> _=/usr/bin/env
>>
>> BlackBook: brad$ ls /usr/share/bin/
>> pear_osx
>>
>> BlackBook: brad$ port installed
>> No ports are installed.
>>
>> BlackBook: brad$ sudo port install perl5
>> --->  Fetching perl5.8
>> --->  Attempting to fetch perl-5.8.9.tar.bz2 from http://www.cpan.org/src/
>> --->  Verifying checksum(s) for perl5.8
>> --->  Extracting perl5.8
>> --->  Configuring perl5.8
>> --->  Building perl5.8
>> --->  Staging perl5.8 into destroot
>> Warning: violation by /usr
>> Warning: perl5.8 violates the layout of the ports-filesystems!
>> Warning: Please fix or indicate this misbehavior (if it is intended), it
>> will be an error in future releases!
>> --->  Installing perl5.8 @5.8.9_1
>> --->  Activating perl5.8 @5.8.9_1
>> --->  Cleaning perl5.8
>> --->  Fetching perl5
>> --->  Verifying checksum(s) for perl5
>> --->  Extracting perl5
>> --->  Configuring perl5
>> --->  Building perl5
>> --->  Staging perl5 into destroot
>> --->  Installing perl5 @5.8.9_0
>> --->  Activating perl5 @5.8.9_0
>> --->  Cleaning perl5
>>
>> BlackBook: brad$ ls /usr/share/bin/
>> c2ph       dprofpp    h2ph       libnetcfg  perlcc     perlthanks
>> pod2html   pod2text   podselect  pstruct    xsubpp
>> corelist   enc2xs     h2xs       pear_osx   perldoc    piconv    
>> pod2latex  pod2usage  prove      s2p
>> cpan       find2perl  instmodsh  perlbug    perlivp    pl2pm     
>> pod2man    podchecker psed       splain
>> BlackBook: brad$
> 
> How about `ls -ld /usr/share/bin /opt/local /opt/local/bin`?

Also the debug output for a port that is installing into /usr would be
helpful. E.g. `sudo port -d install perl5.8`.

- Josh

From apple at frinabulax.org  Wed Jan 14 04:29:30 2009
From: apple at frinabulax.org (robert delius royar)
Date: Wed, 14 Jan 2009 07:29:30 -0500
Subject: gd2 fails on perl5
In-Reply-To: <496DAFD6.9040402@macports.org>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
	<496AF30B.2070006@macports.org>
	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>
	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
	<E64CACC4-E227-4E6D-8A96-80190EA362B8@pixilla.com>
	<496DAEE3.2060204@macports.org> <496DAFD6.9040402@macports.org>
Message-ID: <alpine.OSX.2.00L.0901140642260.98771@teraqry.sevanohynk.bet>

Wed, 14 Jan 2009 (20:26 +1100 UTC) Joshua Root wrote:

> Joshua Root wrote:
>> Bradley Giesbrecht wrote:
>>> BlackBook: brad$ ls /usr/share/bin/
>>> c2ph       dprofpp    h2ph       libnetcfg  perlcc     perlthanks
>>> pod2html   pod2text   podselect  pstruct    xsubpp
>>> corelist   enc2xs     h2xs       pear_osx   perldoc    piconv
>>> pod2latex  pod2usage  prove      s2p
>>> cpan       find2perl  instmodsh  perlbug    perlivp    pl2pm
>>> pod2man    podchecker psed       splain
>>> BlackBook: brad$
>>
>> How about `ls -ld /usr/share/bin /opt/local /opt/local/bin`?
>
> Also the debug output for a port that is installing into /usr would be
> helpful. E.g. `sudo port -d install perl5.8`.
>
> - Josh
How about the following that clearly shows that the port does not 
properly sanitize against this problem:
[Long lines ahead; expect line mangling.]
grendel% port patch perl5.8
--->  Fetching perl5.8
--->  Attempting to fetch perl-5.8.9.tar.bz2 from http://www.cpan.org/src/
--->  Verifying checksum(s) for perl5.8
--->  Extracting perl5.8
grendel% grep -R /share/bin /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_perl5.8
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_perl5.8/work/perl-5.8.9/Configure:  $test -d /usr/share/bin     && dflt=/usr/share/bin

So the maintainer might add
-D scriptdir='${prefix}/share/scripts'
to the configure.args values.  I am leary of replacing a large, working 
perl 5.8.8 Macports installation to see if this is the correct.  The 
problem only shows up if a users has a directory (not a link) in
/usr/share/scripts
/usr/share/bin
/usr/local/script or
/usr/local/scripts
Lines 8791-8808 of Configure
: determine where public executable scripts go
set scriptdir scriptdir
eval $prefixit
case "$scriptdir" in
'')
 	dflt="$bin"
 	: guess some guesses
 	$test -d /usr/share/scripts && dflt=/usr/share/scripts
 	$test -d /usr/share/bin     && dflt=/usr/share/bin
 	$test -d /usr/local/script  && dflt=/usr/local/script
 	$test -d /usr/local/scripts && dflt=/usr/local/scripts
 	$test -d $prefixexp/script  && dflt=$prefixexp/script
 	set dflt
 	eval $prefixup
 	;;
*)  dflt="$scriptdir"
 	;;
esac

Actually, it would make sense, if possible (at least with an upgrade 
installation) to check the current configuration for perl5.8 and set 
those values to be the same in the new one.  I use perl extensively, but 
I am not proficient at configuring it. The maintainer might figure out 
something by parsing the output of `perl -V` searching for the values 
for "config_args".  Perhaps this is already being done?

Here is a patch for the Portfile:

--- /opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5.8/Portfile.~1~  2009-01-07 06:48:14.000000000 -0500
+++ /opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5.8/Portfile      2009-01-14 07:01:14.000000000 -0500
@@ -40,6 +40,7 @@
  configure.args \
      -des \
      -D prefix='${prefix}' \
+    -D scriptdir='${prefix}/share/scripts' \
      -D cppflags="\${CPPFLAGS}" \
      -D ldflags="\${LDFLAGS}" \
      -D vendorprefix='${prefix}' \

-- 
Dr. Robert Delius Royar                   Associate Professor of English
Morehead State University                             Morehead, Kentucky


From jmr at macports.org  Wed Jan 14 05:22:13 2009
From: jmr at macports.org (Joshua Root)
Date: Thu, 15 Jan 2009 00:22:13 +1100
Subject: [macports-mgr] port status question
In-Reply-To: <8ED158A4-656F-44F8-8AB3-4B8B979E5626@kiwanda.nl>
References: <8ED158A4-656F-44F8-8AB3-4B8B979E5626@kiwanda.nl>
Message-ID: <496DE705.5000702@macports.org>

Ewout Boks wrote:
> Hi,
> 
> I was wondering about the kcvs 7.2.1 port. The web page says "no
> maintainer" .
> 
> There is a newer version of the port available, but it cannot be loaded
> through macports. Who arranges the port update?
> 
> Thanks for your great effort (I am a FreeBSD user turning more and more
> to using my Mac) !
> 
> Ewout Boks

The macports-users list is the right place for this sort of question,
since it's not something that only the project managers can address.

No maintainer means precisely that - nobody is responsible for updating
the port. If you have an update that you would like applied, you can
open a ticket on Trac and attach the patch, and then any committer can
apply it for you. If you'd like to become the port's maintainer, that's
even better. ;-)

- Josh

From whodoctor at gmail.com  Wed Jan 14 08:02:29 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Wed, 14 Jan 2009 11:02:29 -0500
Subject: Error on environment?
In-Reply-To: <496D9AED.3020505@macports.org>
References: <4b75340e0901111213y4659d0cayf735dd3ff8306d2d@mail.gmail.com>
	<620755E6-E0FA-4A9B-B032-D048E268D507@macports.org>
	<4b75340e0901130650i325adfb4i978547e8e03979f7@mail.gmail.com>
	<649A10D1-E8D8-4579-940B-1650A655E3BA@macports.org>
	<496D9AED.3020505@macports.org>
Message-ID: <4b75340e0901140802v1367d335kd36c6cdc550ca5f@mail.gmail.com>

On Wed, Jan 14, 2009 at 2:57 AM, Joshua Root <jmr at macports.org> wrote:
.
>
> There are a couple of relevant settings in Terminal.app's preferences
> which may be preferable to setting LANG manually.
>
> - Josh
>

Such as?

From jmr at macports.org  Wed Jan 14 08:06:31 2009
From: jmr at macports.org (Joshua Root)
Date: Thu, 15 Jan 2009 03:06:31 +1100
Subject: Error on environment?
In-Reply-To: <4b75340e0901140802v1367d335kd36c6cdc550ca5f@mail.gmail.com>
References: <4b75340e0901111213y4659d0cayf735dd3ff8306d2d@mail.gmail.com>	
	<620755E6-E0FA-4A9B-B032-D048E268D507@macports.org>	
	<4b75340e0901130650i325adfb4i978547e8e03979f7@mail.gmail.com>	
	<649A10D1-E8D8-4579-940B-1650A655E3BA@macports.org>	
	<496D9AED.3020505@macports.org>
	<4b75340e0901140802v1367d335kd36c6cdc550ca5f@mail.gmail.com>
Message-ID: <496E0D87.2070301@macports.org>

Doctor Who wrote:
> On Wed, Jan 14, 2009 at 2:57 AM, Joshua Root <jmr at macports.org> wrote:
> .
>> There are a couple of relevant settings in Terminal.app's preferences
>> which may be preferable to setting LANG manually.
>>
>> - Josh
>>
> 
> Such as?

Such as the International section in the Advanced tab.

- Josh

From blb at macports.org  Wed Jan 14 13:24:06 2009
From: blb at macports.org (Bryan Blackburn)
Date: Wed, 14 Jan 2009 14:24:06 -0700
Subject: gd2 fails on perl5
In-Reply-To: <alpine.OSX.2.00L.0901140642260.98771@teraqry.sevanohynk.bet>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
	<496AF30B.2070006@macports.org>
	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>
	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
	<E64CACC4-E227-4E6D-8A96-80190EA362B8@pixilla.com>
	<496DAEE3.2060204@macports.org> <496DAFD6.9040402@macports.org>
	<alpine.OSX.2.00L.0901140642260.98771@teraqry.sevanohynk.bet>
Message-ID: <20090114212406.GE711@ninagal.withay.com>

On Wed, Jan 14, 2009 at 07:29:30AM -0500, robert delius royar said:
[...]
> So the maintainer might add
> -D scriptdir='${prefix}/share/scripts'
> to the configure.args values.  I am leary of replacing a large, working  
> perl 5.8.8 Macports installation to see if this is the correct.  The  
> problem only shows up if a users has a directory (not a link) in
> /usr/share/scripts
> /usr/share/bin
> /usr/local/script or
> /usr/local/scripts

This should be fixed in r45373, though scriptdir is pointed to just
${prefix}/bin since that's consistent with where it goes when no scriptdir
is otherwise defined by configure.

Bryan

[...]
> -- 
> Dr. Robert Delius Royar                   Associate Professor of English
> Morehead State University                             Morehead, Kentucky


From opendarwin.org at darkart.com  Wed Jan 14 13:42:48 2009
From: opendarwin.org at darkart.com (Eric Hall)
Date: Wed, 14 Jan 2009 21:42:48 +0000
Subject: gd2 fails on perl5
In-Reply-To: <B681B217-F416-47D4-823B-70B258877268@pixilla.com>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
	<496AF30B.2070006@macports.org>
	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>
	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
	<B681B217-F416-47D4-823B-70B258877268@pixilla.com>
Message-ID: <20090114214248.GW1155@darkart.com>

On Wed, Jan 14, 2009 at 12:16:46AM -0800, Bradley Giesbrecht wrote:
> 
> On Jan 13, 2009, at 4:52 PM, Ryan Schmidt wrote:
> 
> >On Jan 13, 2009, at 01:54, Bradley Giesbrecht wrote:
> >
> >>On Jan 11, 2009, at 11:36 PM, Joshua Root wrote:
> >>
[snip]
> >>
> >>export PATH=~/bin:/usr/local/mysql/bin:/opt/local/bin:/opt/local/ 
> >>sbin:/usr/local/bin:/usr/local/sbin:/usr/share/bin:/usr/local/php5/ 
> >>bin:$PATH
> >>export MANPATH=/opt/local/share/man:/usr/local/ch5.5.0/docs/man: 
> >>$MANPATH
> >
> >You should get /usr/share/bin out of that PATH statement.
> >
> >Also, remove /usr/local/bin and /usr/local/sbin. It is not supported  
> >to have anything installed in the prefix /usr/local while using  
> >MacPorts; it causes problems for many ports. You should remove any  
> >software in /usr/local/{bin,include,lib,man,share} and install it  
> >using MacPorts instead. (Any other prefix, including any  
> >subdirectory of /usr/local, is fine; it's just /usr/local itself  
> >that's problematic. So there's no problem with keeping /usr/local/ 
> >php5/bin or /usr/local/mysql/bin in the PATH. Though php5 and mysql5  
> >are of course available through MacPorts as well.)
> 
> Macports versions and variants of mysql and php do not get me what I  
> need.
> 
> The use of /usr/local is so prevalent I'm surprised to hear that I  
> should not use /usr/local and macports at the same time. Seems  
> everything I build on freebsd using freebsd ports installs there to / 
> usr/local. Most unix software that isn't available using macports  
> installs to /usr/local.
> 
> If a macports package want's to use something outside /opt/local that  
> is available and fit's the need I think that's fine.
> 
> Is it possible to keep macports file writes confined to /opt/local  
> regardless of where the files it uses to build are located?
> 
> Do you have this file on your system which on mine is called called  
> from /etc/profile?
> /usr/libexec/path_helper
> This script reads paths to env from /etc/paths.
> 
> I don't ever remembering editing it but along with /bin and /usr/bin  
> was /usr/local/bin.
> 

	I think its impractical to expect people using macports to
never use /usr/local/{bin,sbin}.  There is a problem with some
ports automatically finding things installed under /usr/local,
and it is impractical to expect port authors to catch every
instance of that - that should be made clear to people (if it
isn't already).

	Also, if the MacPorts versions of software (mysql and php
as pointed out above) don't provided what you need, asking for
enhancements so that they do will (nominally) benefit you and
others, please file tickets (http://trac.macports.org) requesting 
such.



			-eric


From brad at pixilla.com  Wed Jan 14 13:54:39 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Wed, 14 Jan 2009 13:54:39 -0800
Subject: gd2 fails on perl5
In-Reply-To: <alpine.OSX.2.00L.0901140642260.98771@teraqry.sevanohynk.bet>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
	<496AF30B.2070006@macports.org>
	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>
	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
	<E64CACC4-E227-4E6D-8A96-80190EA362B8@pixilla.com>
	<496DAEE3.2060204@macports.org> <496DAFD6.9040402@macports.org>
	<alpine.OSX.2.00L.0901140642260.98771@teraqry.sevanohynk.bet>
Message-ID: <975009C2-F32E-40D6-8EEC-4B378452554F@pixilla.com>


On Jan 14, 2009, at 4:29 AM, robert delius royar wrote:

> Wed, 14 Jan 2009 (20:26 +1100 UTC) Joshua Root wrote:
>
>> Joshua Root wrote:
>>> Bradley Giesbrecht wrote:
>>>> BlackBook: brad$ ls /usr/share/bin/
>>>> c2ph       dprofpp    h2ph       libnetcfg  perlcc     perlthanks
>>>> pod2html   pod2text   podselect  pstruct    xsubpp
>>>> corelist   enc2xs     h2xs       pear_osx   perldoc    piconv
>>>> pod2latex  pod2usage  prove      s2p
>>>> cpan       find2perl  instmodsh  perlbug    perlivp    pl2pm
>>>> pod2man    podchecker psed       splain
>>>> BlackBook: brad$
>>>
>>> How about `ls -ld /usr/share/bin /opt/local /opt/local/bin`?
>>
>> Also the debug output for a port that is installing into /usr would  
>> be
>> helpful. E.g. `sudo port -d install perl5.8`.
>>
>> - Josh
> How about the following that clearly shows that the port does not  
> properly sanitize against this problem:
> [Long lines ahead; expect line mangling.]
> grendel% port patch perl5.8
> --->  Fetching perl5.8
> --->  Attempting to fetch perl-5.8.9.tar.bz2 from http://www.cpan.org/src/
> --->  Verifying checksum(s) for perl5.8
> --->  Extracting perl5.8
> grendel% grep -R /share/bin /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_lang_perl5.8
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_lang_perl5.8/work/perl-5.8.9/Configure:   
> $test -d /usr/share/bin     && dflt=/usr/share/bin
>
> So the maintainer might add
> -D scriptdir='${prefix}/share/scripts'
> to the configure.args values.  I am leary of replacing a large,  
> working perl 5.8.8 Macports installation to see if this is the  
> correct.  The problem only shows up if a users has a directory (not  
> a link) in
> /usr/share/scripts
> /usr/share/bin
> /usr/local/script or
> /usr/local/scripts
> Lines 8791-8808 of Configure
> : determine where public executable scripts go
> set scriptdir scriptdir
> eval $prefixit
> case "$scriptdir" in
> '')
> 	dflt="$bin"
> 	: guess some guesses
> 	$test -d /usr/share/scripts && dflt=/usr/share/scripts
> 	$test -d /usr/share/bin     && dflt=/usr/share/bin
> 	$test -d /usr/local/script  && dflt=/usr/local/script
> 	$test -d /usr/local/scripts && dflt=/usr/local/scripts
> 	$test -d $prefixexp/script  && dflt=$prefixexp/script
> 	set dflt
> 	eval $prefixup
> 	;;
> *)  dflt="$scriptdir"
> 	;;
> esac
>
> Actually, it would make sense, if possible (at least with an upgrade  
> installation) to check the current configuration for perl5.8 and set  
> those values to be the same in the new one.  I use perl extensively,  
> but I am not proficient at configuring it. The maintainer might  
> figure out something by parsing the output of `perl -V` searching  
> for the values for "config_args".  Perhaps this is already being done?
>
> Here is a patch for the Portfile:
>
> --- /opt/local/var/macports/sources/rsync.macports.org/release/ports/ 
> lang/perl5.8/Portfile.~1~  2009-01-07 06:48:14.000000000 -0500
> +++ /opt/local/var/macports/sources/rsync.macports.org/release/ports/ 
> lang/perl5.8/Portfile      2009-01-14 07:01:14.000000000 -0500
> @@ -40,6 +40,7 @@
> configure.args \
>     -des \
>     -D prefix='${prefix}' \
> +    -D scriptdir='${prefix}/share/scripts' \
>     -D cppflags="\${CPPFLAGS}" \
>     -D ldflags="\${LDFLAGS}" \
>     -D vendorprefix='${prefix}' \
>
> -- 
> Dr. Robert Delius Royar                   Associate Professor of  
> English
> Morehead State University                             Morehead,  
> Kentucky

Thank you so much Robert. Finally something that supports my position  
that the port is violating macports file space.

Regarding the existence of /usr/share/bin, Apple php is installed at / 
usr/bin so if you install pear and don't change defaults it installs  
to /usr/share/bin.


From brad at pixilla.com  Wed Jan 14 14:01:43 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Wed, 14 Jan 2009 14:01:43 -0800
Subject: gd2 fails on perl5
In-Reply-To: <alpine.OSX.2.00L.0901140642260.98771@teraqry.sevanohynk.bet>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
	<496AF30B.2070006@macports.org>
	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>
	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
	<E64CACC4-E227-4E6D-8A96-80190EA362B8@pixilla.com>
	<496DAEE3.2060204@macports.org> <496DAFD6.9040402@macports.org>
	<alpine.OSX.2.00L.0901140642260.98771@teraqry.sevanohynk.bet>
Message-ID: <4D088A7C-D92D-48FC-ABAF-58AA8C29ADB9@pixilla.com>


On Jan 14, 2009, at 4:29 AM, robert delius royar wrote:

> Wed, 14 Jan 2009 (20:26 +1100 UTC) Joshua Root wrote:
>
>> Joshua Root wrote:
>>> Bradley Giesbrecht wrote:
>>>> BlackBook: brad$ ls /usr/share/bin/
>>>> c2ph       dprofpp    h2ph       libnetcfg  perlcc     perlthanks
>>>> pod2html   pod2text   podselect  pstruct    xsubpp
>>>> corelist   enc2xs     h2xs       pear_osx   perldoc    piconv
>>>> pod2latex  pod2usage  prove      s2p
>>>> cpan       find2perl  instmodsh  perlbug    perlivp    pl2pm
>>>> pod2man    podchecker psed       splain
>>>> BlackBook: brad$
>>>
>>> How about `ls -ld /usr/share/bin /opt/local /opt/local/bin`?
>>
>> Also the debug output for a port that is installing into /usr would  
>> be
>> helpful. E.g. `sudo port -d install perl5.8`.
>>
>> - Josh
> How about the following that clearly shows that the port does not  
> properly sanitize against this problem:
> [Long lines ahead; expect line mangling.]
> grendel% port patch perl5.8
> --->  Fetching perl5.8
> --->  Attempting to fetch perl-5.8.9.tar.bz2 from http://www.cpan.org/src/
> --->  Verifying checksum(s) for perl5.8
> --->  Extracting perl5.8
> grendel% grep -R /share/bin /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_lang_perl5.8
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_lang_perl5.8/work/perl-5.8.9/Configure:   
> $test -d /usr/share/bin     && dflt=/usr/share/bin
>
> So the maintainer might add
> -D scriptdir='${prefix}/share/scripts'
> to the configure.args values.  I am leary of replacing a large,  
> working perl 5.8.8 Macports installation to see if this is the  
> correct.  The problem only shows up if a users has a directory (not  
> a link) in
> /usr/share/scripts
> /usr/share/bin
> /usr/local/script or
> /usr/local/scripts
> Lines 8791-8808 of Configure
> : determine where public executable scripts go
> set scriptdir scriptdir
> eval $prefixit
> case "$scriptdir" in
> '')
> 	dflt="$bin"
> 	: guess some guesses
> 	$test -d /usr/share/scripts && dflt=/usr/share/scripts
> 	$test -d /usr/share/bin     && dflt=/usr/share/bin
> 	$test -d /usr/local/script  && dflt=/usr/local/script
> 	$test -d /usr/local/scripts && dflt=/usr/local/scripts
> 	$test -d $prefixexp/script  && dflt=$prefixexp/script
> 	set dflt
> 	eval $prefixup
> 	;;
> *)  dflt="$scriptdir"
> 	;;
> esac
>
> Actually, it would make sense, if possible (at least with an upgrade  
> installation) to check the current configuration for perl5.8 and set  
> those values to be the same in the new one.  I use perl extensively,  
> but I am not proficient at configuring it. The maintainer might  
> figure out something by parsing the output of `perl -V` searching  
> for the values for "config_args".  Perhaps this is already being done?
>
> Here is a patch for the Portfile:
>
> --- /opt/local/var/macports/sources/rsync.macports.org/release/ports/ 
> lang/perl5.8/Portfile.~1~  2009-01-07 06:48:14.000000000 -0500
> +++ /opt/local/var/macports/sources/rsync.macports.org/release/ports/ 
> lang/perl5.8/Portfile      2009-01-14 07:01:14.000000000 -0500
> @@ -40,6 +40,7 @@
> configure.args \
>     -des \
>     -D prefix='${prefix}' \
> +    -D scriptdir='${prefix}/share/scripts' \
>     -D cppflags="\${CPPFLAGS}" \
>     -D ldflags="\${LDFLAGS}" \
>     -D vendorprefix='${prefix}' \
>
> -- 
> Dr. Robert Delius Royar                   Associate Professor of  
> English
> Morehead State University                             Morehead,  
> Kentucky

Adding scritpdir works as expected.
Thank you Dr. Royar.
I see Bryan fixed this in r45373. Thank you Bryan.

bash-3.2# env
SHELL=/bin/bash
TERM=xterm-color
USER=root
SUDO_USER=brad
SUDO_UID=501
SSH_AUTH_SOCK=/tmp/501/nl.uu.phil.SSHAgent.socket
__CF_USER_TEXT_ENCODING=0x1F5:0:0
PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/ 
X11/bin
PWD=/Users/brad/ports/lang/perl5.8
LANG=en_US.UTF-8
SHLVL=1
SUDO_COMMAND=/bin/bash
HOME=/Users/brad
LOGNAME=root
SUDO_GID=501
DISPLAY=/tmp/launch-UjAiw0/:0
_=/usr/bin/env
OLDPWD=/Users/brad/ports/lang/perl5.10

bash-3.2# port installed
No ports are installed.

bash-3.2# ls /usr/share/bin/
pear_osx

bash-3.2# grep scriptdir Portfile
     -D scriptdir='${prefix}/share/scripts' \

bash-3.2# port install perl5
--->  Fetching perl5.8
--->  Attempting to fetch perl-5.8.9.tar.bz2 from http://www.cpan.org/src/
--->  Verifying checksum(s) for perl5.8
--->  Extracting perl5.8
--->  Configuring perl5.8
--->  Building perl5.8
--->  Staging perl5.8 into destroot
--->  Installing perl5.8 @5.8.9_1
--->  Activating perl5.8 @5.8.9_1
--->  Cleaning perl5.8
--->  Fetching perl5
--->  Verifying checksum(s) for perl5
--->  Extracting perl5
--->  Configuring perl5
--->  Building perl5
--->  Staging perl5 into destroot
--->  Installing perl5 @5.8.9_0
--->  Activating perl5 @5.8.9_0
--->  Cleaning perl5

bash-3.2# ls /usr/share/bin/
pear_osx

bash-3.2# ls -l /opt/local/share/scripts/
total 1272
-rwxr-xr-x  2 root  admin  36613 Jan 14 13:53 c2ph

//Brad

From apple at frinabulax.org  Wed Jan 14 14:03:11 2009
From: apple at frinabulax.org (robert delius royar)
Date: Wed, 14 Jan 2009 17:03:11 -0500
Subject: gd2 fails on perl5
In-Reply-To: <20090114212406.GE711@ninagal.withay.com>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
	<496AF30B.2070006@macports.org>
	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>
	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
	<E64CACC4-E227-4E6D-8A96-80190EA362B8@pixilla.com>
	<496DAEE3.2060204@macports.org> <496DAFD6.9040402@macports.org>
	<alpine.OSX.2.00L.0901140642260.98771@teraqry.sevanohynk.bet>
	<20090114212406.GE711@ninagal.withay.com>
Message-ID: <alpine.DEB.2.00L.0901141656490.871@plarjhys.sevanohynk.bet>

Wed, 14 Jan 2009 (14:24 -0700 UTC) Bryan Blackburn wrote:

> On Wed, Jan 14, 2009 at 07:29:30AM -0500, robert delius royar said:
> [...]
>> So the maintainer might add
>> -D scriptdir='${prefix}/share/scripts'
[...]
>
> This should be fixed in r45373, though scriptdir is pointed to just
> ${prefix}/bin since that's consistent with where it goes when no scriptdir
> is otherwise defined by configure.
>
> Bryan

That would do it.  At some point the folks who confer about Macports 
port directory hierarchy might also consider some of the changes to the 
suggested GNU directory hierarchy [hope I have that correct].  I know in 
the XEmacs development that there was recently a restructuring of 
libraries and scripts to move a number of scripts into directories under 
share.  I believe this was to make the software align better with GNU 
systems.

-- 
Dr. Robert Delius Royar
Sent from an Eee PC

From brad at pixilla.com  Wed Jan 14 14:28:51 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Wed, 14 Jan 2009 14:28:51 -0800
Subject: gd2 fails on perl5
In-Reply-To: <20090114214248.GW1155@darkart.com>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
	<496AF30B.2070006@macports.org>
	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>
	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
	<B681B217-F416-47D4-823B-70B258877268@pixilla.com>
	<20090114214248.GW1155@darkart.com>
Message-ID: <A4B13498-1CD1-44AC-9EBA-5DBFA037D4D1@pixilla.com>


On Jan 14, 2009, at 1:42 PM, Eric Hall wrote:

> On Wed, Jan 14, 2009 at 12:16:46AM -0800, Bradley Giesbrecht wrote:
>>
>> On Jan 13, 2009, at 4:52 PM, Ryan Schmidt wrote:
>>
>>> On Jan 13, 2009, at 01:54, Bradley Giesbrecht wrote:
>>>
>>>> On Jan 11, 2009, at 11:36 PM, Joshua Root wrote:
>>>>
> [snip]
>>>>
>>>> export PATH=~/bin:/usr/local/mysql/bin:/opt/local/bin:/opt/local/
>>>> sbin:/usr/local/bin:/usr/local/sbin:/usr/share/bin:/usr/local/php5/
>>>> bin:$PATH
>>>> export MANPATH=/opt/local/share/man:/usr/local/ch5.5.0/docs/man:
>>>> $MANPATH
>>>
>>> You should get /usr/share/bin out of that PATH statement.
>>>
>>> Also, remove /usr/local/bin and /usr/local/sbin. It is not supported
>>> to have anything installed in the prefix /usr/local while using
>>> MacPorts; it causes problems for many ports. You should remove any
>>> software in /usr/local/{bin,include,lib,man,share} and install it
>>> using MacPorts instead. (Any other prefix, including any
>>> subdirectory of /usr/local, is fine; it's just /usr/local itself
>>> that's problematic. So there's no problem with keeping /usr/local/
>>> php5/bin or /usr/local/mysql/bin in the PATH. Though php5 and mysql5
>>> are of course available through MacPorts as well.)
>>
>> Macports versions and variants of mysql and php do not get me what I
>> need.
>>
>> The use of /usr/local is so prevalent I'm surprised to hear that I
>> should not use /usr/local and macports at the same time. Seems
>> everything I build on freebsd using freebsd ports installs there to /
>> usr/local. Most unix software that isn't available using macports
>> installs to /usr/local.
>>
>> If a macports package want's to use something outside /opt/local that
>> is available and fit's the need I think that's fine.
>>
>> Is it possible to keep macports file writes confined to /opt/local
>> regardless of where the files it uses to build are located?
>>
>> Do you have this file on your system which on mine is called called
>> from /etc/profile?
>> /usr/libexec/path_helper
>> This script reads paths to env from /etc/paths.
>>
>> I don't ever remembering editing it but along with /bin and /usr/bin
>> was /usr/local/bin.
>>
>
> 	I think its impractical to expect people using macports to
> never use /usr/local/{bin,sbin}.

We agree.

> There is a problem with some
> ports automatically finding things installed under /usr/local,
> and it is impractical to expect port authors to catch every
> instance of that - that should be made clear to people (if it
> isn't already).

We agree. Also, if I already have mysql(d) installed somewhere else  
(like os x server) and would like to keep what I have I'd be happy if  
macports would use what I already have rather then build another  
mysql(d) and force me to use this.

> 	Also, if the MacPorts versions of software (mysql and php
> as pointed out above) don't provided what you need, asking for
> enhancements so that they do will (nominally) benefit you and
> others, please file tickets (http://trac.macports.org) requesting
> such.

I did, and submitted a patch to add variants to bind9 and dovecot. I  
have heard nothing back.

//Brad


From jmr at macports.org  Wed Jan 14 14:56:41 2009
From: jmr at macports.org (Joshua Root)
Date: Thu, 15 Jan 2009 09:56:41 +1100
Subject: gd2 fails on perl5
In-Reply-To: <A4B13498-1CD1-44AC-9EBA-5DBFA037D4D1@pixilla.com>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>	<496AD51B.4020605@macports.org>	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>	<496AF30B.2070006@macports.org>	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>	<B681B217-F416-47D4-823B-70B258877268@pixilla.com>	<20090114214248.GW1155@darkart.com>
	<A4B13498-1CD1-44AC-9EBA-5DBFA037D4D1@pixilla.com>
Message-ID: <496E6DA9.4030107@macports.org>

Bradley Giesbrecht wrote:
> 
> On Jan 14, 2009, at 1:42 PM, Eric Hall wrote:
>> There is a problem with some
>> ports automatically finding things installed under /usr/local,
>> and it is impractical to expect port authors to catch every
>> instance of that - that should be made clear to people (if it
>> isn't already).
> 
> We agree. Also, if I already have mysql(d) installed somewhere else
> (like os x server) and would like to keep what I have I'd be happy if
> macports would use what I already have rather then build another
> mysql(d) and force me to use this.

Feel free to delete or modify dependencies in your copies of portfiles
as you see fit. Just understand that such a configuration is an unknown
quantity and we can't help you if it breaks.

- Josh

From ryandesign at macports.org  Wed Jan 14 15:52:40 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 14 Jan 2009 17:52:40 -0600
Subject: Using Macports libraries in Xcode gcc
In-Reply-To: <77e4079b0901130132u65ccb42dv8ec8c260871d338b@mail.gmail.com>
References: <758644.11599.qm@web65703.mail.ac4.yahoo.com>
	<4969026B.1050401@macports.org>
	<77e4079b0901130132u65ccb42dv8ec8c260871d338b@mail.gmail.com>
Message-ID: <E865C94A-12ED-4F3B-AA03-2384A2DD252F@macports.org>

On Jan 13, 2009, at 03:32, Neil wrote:

> My .bash_profile :
> # Add MacPorts directories, if they exist.
> if [ -d /opt/local ]; then
> 	export PATH=/opt/local/bin:/opt/local/sbin:$PATH
> 	export MANPATH=/opt/local/share/man:$MANPATH
> 	export C_INCLUDE_PATH=/opt/local/include
> 	export CPLUS_INCLUDE_PATH=/opt/local/include
> 	alias gcc="gcc -I/opt/local/include -L/opt/local/lib"
> 	alias g++="g++ -I/opt/local/include -L/opt/local/lib"
> 	# if [ -f /opt/local/etc/bash_completion ]; then
> 	# 	. /opt/local/etc/bash_completion
> 	# fi
> fi
>
> IIRC, C_INCLUDE_PATH/CPLUS_INCLUDE_PATH alone didn't work, and thus I
> added the aliases.  But now that I think about it, I should be able to
> remove the former and the later should do everything on it's own.  I'm
> going to try that, I think...

As I understand it, it should be sufficient to set EITHER:

	export C_INCLUDE_PATH=/opt/local/include
	export CPLUS_INCLUDE_PATH=/opt/local/include
	export LIBRARY_PATH=/opt/local/lib

OR:

	export CPPFLAGS=-I/opt/local/include
	export LDFLAGS=-L/opt/local/lib

It should not be necessary in either case to have gcc or g++ be  
aliases to anything.

I'm not sure what the difference is between the above two methods --  
if one is preferable, or if they are for different situations, or  
what. MacPorts uses the CPPFLAGS / LDFLAGS method internally.



From ryandesign at macports.org  Wed Jan 14 15:56:14 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 14 Jan 2009 17:56:14 -0600
Subject: Error on environment?
In-Reply-To: <496E0D87.2070301@macports.org>
References: <4b75340e0901111213y4659d0cayf735dd3ff8306d2d@mail.gmail.com>	
	<620755E6-E0FA-4A9B-B032-D048E268D507@macports.org>	
	<4b75340e0901130650i325adfb4i978547e8e03979f7@mail.gmail.com>	
	<649A10D1-E8D8-4579-940B-1650A655E3BA@macports.org>	
	<496D9AED.3020505@macports.org>
	<4b75340e0901140802v1367d335kd36c6cdc550ca5f@mail.gmail.com>
	<496E0D87.2070301@macports.org>
Message-ID: <874CE29A-4CF5-4B96-A66F-B969777F96CF@macports.org>


On Jan 14, 2009, at 10:06, Joshua Root wrote:

> Doctor Who wrote:
>
>> On Wed, Jan 14, 2009 at 2:57 AM, Joshua Root wrote:
>>
>>> There are a couple of relevant settings in Terminal.app's  
>>> preferences
>>> which may be preferable to setting LANG manually.
>>
>> Such as?
>
> Such as the International section in the Advanced tab.

You must be on Leopard. :)

On my Tiger system I have in Terminal's Inspector window a Display  
section where I can set the Character Set Encoding (and I have it set  
to Unicode UTF-8). I understood that I must then set the LANG  
variable to correspond to this encoding, so I set LANG to en_US.UTF-8.

Maybe Leopard does this automatically?


From jmr at macports.org  Wed Jan 14 16:12:21 2009
From: jmr at macports.org (Joshua Root)
Date: Thu, 15 Jan 2009 11:12:21 +1100
Subject: Error on environment?
In-Reply-To: <874CE29A-4CF5-4B96-A66F-B969777F96CF@macports.org>
References: <4b75340e0901111213y4659d0cayf735dd3ff8306d2d@mail.gmail.com>	
	<620755E6-E0FA-4A9B-B032-D048E268D507@macports.org>	
	<4b75340e0901130650i325adfb4i978547e8e03979f7@mail.gmail.com>	
	<649A10D1-E8D8-4579-940B-1650A655E3BA@macports.org>	
	<496D9AED.3020505@macports.org>
	<4b75340e0901140802v1367d335kd36c6cdc550ca5f@mail.gmail.com>
	<496E0D87.2070301@macports.org>
	<874CE29A-4CF5-4B96-A66F-B969777F96CF@macports.org>
Message-ID: <496E7F65.9040807@macports.org>

Ryan Schmidt wrote:
> 
> On Jan 14, 2009, at 10:06, Joshua Root wrote:
> 
>> Doctor Who wrote:
>>
>>> On Wed, Jan 14, 2009 at 2:57 AM, Joshua Root wrote:
>>>
>>>> There are a couple of relevant settings in Terminal.app's preferences
>>>> which may be preferable to setting LANG manually.
>>>
>>> Such as?
>>
>> Such as the International section in the Advanced tab.
> 
> You must be on Leopard. :)
> 
> On my Tiger system I have in Terminal's Inspector window a Display
> section where I can set the Character Set Encoding (and I have it set to
> Unicode UTF-8). I understood that I must then set the LANG variable to
> correspond to this encoding, so I set LANG to en_US.UTF-8.
> 
> Maybe Leopard does this automatically?

Yes, on Leopard there's a checkbox "Set LANG environment variable on
startup" which is checked by default.

- Josh

From h8spawn at googlemail.com  Wed Jan 14 16:14:15 2009
From: h8spawn at googlemail.com (=?UTF-8?Q?S._G=C3=BCnther?=)
Date: Thu, 15 Jan 2009 11:14:15 +1100
Subject: Updating to 1.700
Message-ID: <e4302e380901141614w72caeb6ao7b58a6d02bea836b@mail.gmail.com>

Hi,

I know I'm late to the party but I just discovered that
MacPorts has bumped to version 1.700. Since I'm a very
happy MacPorts user since quite some time I would
definitley like to upgrade to the newest version, but I'm
one of the few who are behind a proxy which makes
port selfupdate
not an option. This puts me in some kind of predicament
because in the FAQ I only found a description on how to
upgrade without selfupdate which requires 1.700 or later.
I know there has been a way to do this manually by down -
loading and unpacking a tarball, but I can't find it anymore.
So in essence my question is this: what's the recommended
way for updating to 1.700 without using selfupdate or
compiling from source.
I'm on Mac OS X Tiger, Intel.

Kind regards
Stephan
----------------------------------------------------------------------------

From ryandesign at macports.org  Wed Jan 14 16:17:25 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 14 Jan 2009 18:17:25 -0600
Subject: Error on environment?
In-Reply-To: <496E7F65.9040807@macports.org>
References: <4b75340e0901111213y4659d0cayf735dd3ff8306d2d@mail.gmail.com>	
	<620755E6-E0FA-4A9B-B032-D048E268D507@macports.org>	
	<4b75340e0901130650i325adfb4i978547e8e03979f7@mail.gmail.com>	
	<649A10D1-E8D8-4579-940B-1650A655E3BA@macports.org>	
	<496D9AED.3020505@macports.org>
	<4b75340e0901140802v1367d335kd36c6cdc550ca5f@mail.gmail.com>
	<496E0D87.2070301@macports.org>
	<874CE29A-4CF5-4B96-A66F-B969777F96CF@macports.org>
	<496E7F65.9040807@macports.org>
Message-ID: <4E75774B-F1CB-4861-8FF9-61B8A7F33AC0@macports.org>

On Jan 14, 2009, at 18:12, Joshua Root wrote:

> Ryan Schmidt wrote:
>
>> On my Tiger system I have in Terminal's Inspector window a Display
>> section where I can set the Character Set Encoding (and I have it  
>> set to
>> Unicode UTF-8). I understood that I must then set the LANG  
>> variable to
>> correspond to this encoding, so I set LANG to en_US.UTF-8.
>>
>> Maybe Leopard does this automatically?
>
> Yes, on Leopard there's a checkbox "Set LANG environment variable on
> startup" which is checked by default.

That's cool! Add that to the column of things I like about Leopard.

Firmly in the other column, though, is what they did to folders in  
the Dock.


From stonesoupandboiledfrogs at gmail.com  Wed Jan 14 16:20:49 2009
From: stonesoupandboiledfrogs at gmail.com (jason white)
Date: Wed, 14 Jan 2009 18:20:49 -0600
Subject: install trouble Mac OSX 10.4
In-Reply-To: <8F85279E-5351-4347-9DA0-12B1DECCDFCB@macports.org>
References: <80a464360901120639t5f1e63c8mcecb4f7007d8a50a@mail.gmail.com>
	<15E3CA49-71A4-4028-998B-D24C91A30CFD@cern.ch>
	<06249CBC-ED84-404E-A242-4FB055A903C4@macports.org>
	<80a464360901130732l2ff27fqe8dcb3286898cb85@mail.gmail.com>
	<8F85279E-5351-4347-9DA0-12B1DECCDFCB@macports.org>
Message-ID: <80a464360901141620s553aa7b1m3ccbf57ff4f5982a@mail.gmail.com>

Thank you all for your help.
I did a complete reinstall of MacOSX 10.4, and installed all of the updates.
Then i installed XCode 2.5, followed by MacPorts 1.6.1
After all of this, i still got the error about the port command. I updated
to MacPorts 1.7, and ran the port command again. This time it worked!!!
Turns out that by using MacPorts 1.6, and creating my own .profile, i broke
the configuration. After the complete reinstall, and upgrade to MacPorts 1.7
everything worked fine.

thank you again for all of your help,
Jason

On Tue, Jan 13, 2009 at 6:40 PM, Ryan Schmidt <ryandesign at macports.org>wrote:

>
> On Jan 13, 2009, at 09:32, jason white wrote:
>
>  On Mon, Jan 12, 2009 at 11:59 PM, Ryan Schmidt wrote:
>>
>>  the entry in my .bash_profile is:
>>>>>
>>>>> export PATH=" opt/local/bin: /opt/local/sbin:$PATH"
>>>>>
>>>>
>>>> You are missing an initial / on the first path. That line should be
>>>>
>>>> export PATH=" /opt/local/bin: /opt/local/sbin:$PATH"
>>>>
>>>
>>> Actually there should not be spaces there. The line should read:
>>>
>>> export PATH="/opt/local/bin:/opt/local/sbin:$PATH"
>>>
>>> Did the MacPorts installer do this to your .bash_profile or did you set
>>> it up manually? If the former, then we have a bug in the setup script
>>> somewhere....
>>>
>>
>> I did a complete reinstall of MacOS 10.4 and applied all of the updates.
>> Then I installed XCode, and used all of the defaults for the install. After
>> that I installed MacPorts 1.6 using the installer from the MacPorts site.
>> After the install was completed I looked for the .bash_profile file, and
>> could not find it. Should i create a new file? I believe i created the file
>> manually last time.
>>
>
> The MacPorts 1.6.0 installer has a bug that it does not set up the .profile
> for you. This was fixed in MacPorts 1.7.0, which is the version you should
> be using. Please see:
>
> http://trac.macports.org/wiki/ProblemHotlist#a.profilenotsetup
>
> P.S: Use Reply All so your reply goes to the list too, not just to me.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090114/40c95f2e/attachment.html>

From blb at macports.org  Wed Jan 14 16:30:35 2009
From: blb at macports.org (Bryan Blackburn)
Date: Wed, 14 Jan 2009 17:30:35 -0700
Subject: Updating to 1.700
In-Reply-To: <e4302e380901141614w72caeb6ao7b58a6d02bea836b@mail.gmail.com>
References: <e4302e380901141614w72caeb6ao7b58a6d02bea836b@mail.gmail.com>
Message-ID: <20090115003035.GG711@ninagal.withay.com>

On Thu, Jan 15, 2009 at 11:14:15AM +1100, S. G?nther said:
> Hi,
> 
> I know I'm late to the party but I just discovered that
> MacPorts has bumped to version 1.700. Since I'm a very
> happy MacPorts user since quite some time I would
> definitley like to upgrade to the newest version, but I'm
> one of the few who are behind a proxy which makes
> port selfupdate
> not an option. This puts me in some kind of predicament
> because in the FAQ I only found a description on how to
> upgrade without selfupdate which requires 1.700 or later.
> I know there has been a way to do this manually by down -
> loading and unpacking a tarball, but I can't find it anymore.
> So in essence my question is this: what's the recommended
> way for updating to 1.700 without using selfupdate or
> compiling from source.
> I'm on Mac OS X Tiger, Intel.

You can simply grab the DMG [1] for your OS version and install that,
assuming your current install is in /opt/local.  Doing so doesn't mess with
the ports you already have installed as it simply replaces the base MacPorts
code.  If you don't use /opt/local your only choice would be to grab a
source tarball and build that.

Bryan

[1] - <http://www.macports.org/install.php>

> 
> Kind regards
> Stephan

From whodoctor at gmail.com  Wed Jan 14 18:27:27 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Wed, 14 Jan 2009 21:27:27 -0500
Subject: Error trying to upgrade
Message-ID: <4b75340e0901141827y1116d55fgda38b62d00651d59@mail.gmail.com>

I'm getting the following error when trying to upgrade my installed ports:

sudo port upgrade installed -f
--->  Activating libtool-devel @2.3a_0
Error: Activating libtool-devel @2.3a_0 failed: Image error:
/opt/local/bin/glibtool is being used by the active libtool port.
Please deactivate this port first, or use the -f flag to force the
activation.
--->  Activating p5-digest-md5 @2.38_0
Error: Activating p5-digest-md5 @2.38_0 failed: Image error:
/opt/local/share/man/man3/Digest::MD5.3pm.gz is being used by the
active perl5.8 port.  Please deactivate this port first, or use the -f
flag to force the activation.

What's the right way to address this?  It appears trying to deactivate
the ports or using '-f' don't work.

Thanks.

From ryandesign at macports.org  Wed Jan 14 19:55:59 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 14 Jan 2009 21:55:59 -0600
Subject: Error trying to upgrade
In-Reply-To: <4b75340e0901141827y1116d55fgda38b62d00651d59@mail.gmail.com>
References: <4b75340e0901141827y1116d55fgda38b62d00651d59@mail.gmail.com>
Message-ID: <D1124080-9616-4EED-80F8-2D8EF0B88B90@macports.org>

On Jan 14, 2009, at 20:27, Doctor Who wrote:

> I'm getting the following error when trying to upgrade my installed  
> ports:
>
> sudo port upgrade installed -f
> --->  Activating libtool-devel @2.3a_0
> Error: Activating libtool-devel @2.3a_0 failed: Image error:
> /opt/local/bin/glibtool is being used by the active libtool port.
> Please deactivate this port first, or use the -f flag to force the
> activation.
> --->  Activating p5-digest-md5 @2.38_0
> Error: Activating p5-digest-md5 @2.38_0 failed: Image error:
> /opt/local/share/man/man3/Digest::MD5.3pm.gz is being used by the
> active perl5.8 port.  Please deactivate this port first, or use the -f
> flag to force the activation.
>
> What's the right way to address this?  It appears trying to deactivate
> the ports or using '-f' don't work.

You should not be using the -f option unless absolutely necessary. In  
many cases, a port will tell you if it is necessary. And in those  
cases, only use -f with the port in question, not with a command that  
affects many ports, such as "upgrade installed".

You probably never want to "upgrade installed" either. "upgrade  
outdated" is probably what you were looking for.

You appear to be trying to activate libtool-devel but already have  
libtool activated. These ports are mutually exclusive; you must  
decide which one you want to activate, and not activate the other  
one. -devel ports are development versions of software, as opposed to  
stable versions. Usually the -devel versions are newer, but not  
always. Usually the -devel ports are less well tested. Unless you  
have a specific need for features that are not in the released  
version, you should avoid -devel ports.

p5-digest-md5, on the other hand, is a perl module, and it happens to  
provide a module (Digest::MD5) which perl itself already provides.  
Perhaps that was added with the recent update to perl 5.8.9. So you  
may not need the p5-digest-md5 port at all; you may be just fine with  
just the perl5.8 port. You can try uninstalling p5-digest-md5, or  
just leave it deactivated.

I see there are a number of ports that declare dependencies on p5- 
digest-md5:

argus-monitor
gnupod
imapsync
p5-convert-pem
p5-flickr-api
p5-image-exiftool
p5-net-dict
p5-net-ssh-perl
p5-perl-ldap

Are you using one of these? Perhaps these ports need to be updated to  
no longer list p5-digest-md5 as a dependency.


From h8spawn at googlemail.com  Wed Jan 14 20:37:39 2009
From: h8spawn at googlemail.com (=?UTF-8?Q?S._G=C3=BCnther?=)
Date: Thu, 15 Jan 2009 15:37:39 +1100
Subject: Updating to 1.700
In-Reply-To: <20090115003035.GG711@ninagal.withay.com>
References: <e4302e380901141614w72caeb6ao7b58a6d02bea836b@mail.gmail.com>
	<20090115003035.GG711@ninagal.withay.com>
Message-ID: <e4302e380901142037q76ae1577s2f14a8b98e7e33ee@mail.gmail.com>

Ah, thanks. I was suspecting something like that but since
I didn't find anything saying that doing so wouldn't mess
up the installation I wanted to ask before making an
avoidable mistake.
Thanks for the answer.
Worked like a charm.

Kind regards
Stephan
----------------------------------------------------------------------------



On Thu, Jan 15, 2009 at 11:30 AM, Bryan Blackburn <blb at macports.org> wrote:
> On Thu, Jan 15, 2009 at 11:14:15AM +1100, S. G?nther said:
>> Hi,
>>
>> I know I'm late to the party but I just discovered that
>> MacPorts has bumped to version 1.700. Since I'm a very
>> happy MacPorts user since quite some time I would
>> definitley like to upgrade to the newest version, but I'm
>> one of the few who are behind a proxy which makes
>> port selfupdate
>> not an option. This puts me in some kind of predicament
>> because in the FAQ I only found a description on how to
>> upgrade without selfupdate which requires 1.700 or later.
>> I know there has been a way to do this manually by down -
>> loading and unpacking a tarball, but I can't find it anymore.
>> So in essence my question is this: what's the recommended
>> way for updating to 1.700 without using selfupdate or
>> compiling from source.
>> I'm on Mac OS X Tiger, Intel.
>
> You can simply grab the DMG [1] for your OS version and install that,
> assuming your current install is in /opt/local.  Doing so doesn't mess with
> the ports you already have installed as it simply replaces the base MacPorts
> code.  If you don't use /opt/local your only choice would be to grab a
> source tarball and build that.
>
> Bryan
>
> [1] - <http://www.macports.org/install.php>
>
>>
>> Kind regards
>> Stephan
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>

From blb at macports.org  Wed Jan 14 21:11:28 2009
From: blb at macports.org (Bryan Blackburn)
Date: Wed, 14 Jan 2009 22:11:28 -0700
Subject: Error trying to upgrade
In-Reply-To: <D1124080-9616-4EED-80F8-2D8EF0B88B90@macports.org>
References: <4b75340e0901141827y1116d55fgda38b62d00651d59@mail.gmail.com>
	<D1124080-9616-4EED-80F8-2D8EF0B88B90@macports.org>
Message-ID: <20090115051128.GK711@ninagal.withay.com>

On Wed, Jan 14, 2009 at 09:55:59PM -0600, Ryan Schmidt said:
[...]
> p5-digest-md5, on the other hand, is a perl module, and it happens to  
> provide a module (Digest::MD5) which perl itself already provides.  
> Perhaps that was added with the recent update to perl 5.8.9. So you may 
> not need the p5-digest-md5 port at all; you may be just fine with just the 
> perl5.8 port. You can try uninstalling p5-digest-md5, or just leave it 
> deactivated.

Don't for get about #12710,

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

where several modules replace what comes with perl.

Bryan


From ryandesign at macports.org  Wed Jan 14 22:11:55 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 15 Jan 2009 00:11:55 -0600
Subject: Error trying to upgrade
In-Reply-To: <20090115051128.GK711@ninagal.withay.com>
References: <4b75340e0901141827y1116d55fgda38b62d00651d59@mail.gmail.com>
	<D1124080-9616-4EED-80F8-2D8EF0B88B90@macports.org>
	<20090115051128.GK711@ninagal.withay.com>
Message-ID: <122FA984-21D7-4640-949B-3D2116726075@macports.org>

On Jan 14, 2009, at 23:11, Bryan Blackburn wrote:

> On Wed, Jan 14, 2009 at 09:55:59PM -0600, Ryan Schmidt said:
> [...]
>> p5-digest-md5, on the other hand, is a perl module, and it happens to
>> provide a module (Digest::MD5) which perl itself already provides.
>> Perhaps that was added with the recent update to perl 5.8.9. So  
>> you may
>> not need the p5-digest-md5 port at all; you may be just fine with  
>> just the
>> perl5.8 port. You can try uninstalling p5-digest-md5, or just  
>> leave it
>> deactivated.
>
> Don't for get about #12710,
>
> <http://trac.macports.org/ticket/12710>
>
> where several modules replace what comes with perl.

Indeed. I didn't think p5-digest-md5 was one of those that  
traditionally did this, but I see in #12710 that it is. It's just  
missing the classic

post-destroot {
     ui_msg "You must install or activate this package with '- 
f' (force) as it needs to overwrite files installed by the perl5.8 port"
}

block.


From evert.rol at gmail.com  Thu Jan 15 00:42:30 2009
From: evert.rol at gmail.com (Evert Rol)
Date: Thu, 15 Jan 2009 09:42:30 +0100
Subject: installing boost-python
In-Reply-To: <68c840280901121339i166ce3eese717bf46556ab23f@mail.gmail.com>
References: <68c840280901121246p70d1bd4blbd147a7eae47e480@mail.gmail.com>
	<loom.20090112T211916-943@post.gmane.org>
	<68c840280901121339i166ce3eese717bf46556ab23f@mail.gmail.com>
Message-ID: <1878DE78-CA20-4D25-820E-2F68816F1FBE@gmail.com>

To follow up on this, I think it's an issue related a broken symlink  
in the python installation, not boost itself. See http://trac.macports.org/ticket/17998


>>> it looks like the libboost_python*
>>> libraries don't pick up the macport python headers/libraries, but  
>>> the
>>> system ones.
>>
>> Did you install boost with any of the python variants
>> (python24, python25, or python26)?
>
> Yes (sorry, forgot to mention that earlier):
> $> port install boost +python25+icu
>
> (well, the icu isn't necessary, and shouldn't matter anyways)
>
>
>> If yes, then this is a boost bug you should report.
>
> Ok, I'll file a ticket at the macports website.
>
>
>> I use the python26 variant, and it finds the correct MacPorts python.
>
> Which does make me suspicious that it doesn't work me.
>
> I wonder if it's worth uninstalling/deactiving the python25 variant,
> and installing the python26 variant, to see what happens for me.
>
>
>> If no, then this is also a bug you should report, but an easy  
>> workaround would be
>> to reinstall boost with the python variant of your choice.
>>
>> -Marcus
>>


From whodoctor at gmail.com  Thu Jan 15 03:49:10 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Thu, 15 Jan 2009 06:49:10 -0500
Subject: Error trying to upgrade
In-Reply-To: <122FA984-21D7-4640-949B-3D2116726075@macports.org>
References: <4b75340e0901141827y1116d55fgda38b62d00651d59@mail.gmail.com>
	<D1124080-9616-4EED-80F8-2D8EF0B88B90@macports.org>
	<20090115051128.GK711@ninagal.withay.com>
	<122FA984-21D7-4640-949B-3D2116726075@macports.org>
Message-ID: <4b75340e0901150349y1b71a49cif7a607491f941ee3@mail.gmail.com>

On Thu, Jan 15, 2009 at 1:11 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Jan 14, 2009, at 23:11, Bryan Blackburn wrote:
>
>> On Wed, Jan 14, 2009 at 09:55:59PM -0600, Ryan Schmidt said:
>> [...]
>>>
>>> p5-digest-md5, on the other hand, is a perl module, and it happens to
>>> provide a module (Digest::MD5) which perl itself already provides.
>>> Perhaps that was added with the recent update to perl 5.8.9. So you may
>>> not need the p5-digest-md5 port at all; you may be just fine with just
>>> the
>>> perl5.8 port. You can try uninstalling p5-digest-md5, or just leave it
>>> deactivated.
>>
>> Don't for get about #12710,
>>
>> <http://trac.macports.org/ticket/12710>
>>
>> where several modules replace what comes with perl.
>
> Indeed. I didn't think p5-digest-md5 was one of those that traditionally did
> this, but I see in #12710 that it is. It's just missing the classic
>
> post-destroot {
>    ui_msg "You must install or activate this package with '-f' (force) as it
> needs to overwrite files installed by the perl5.8 port"
> }
>
> block.
>


So does that mean that there's nothing I can do until the bug is addressed?

From mmensinger at mail.bradley.edu  Thu Jan 15 13:18:40 2009
From: mmensinger at mail.bradley.edu (Michael Mensinger)
Date: Thu, 15 Jan 2009 15:18:40 -0600
Subject: dpkg problems
Message-ID: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>

hey there everybody.
So, I'm a new linux person, and I love my mac, so I want to open  
a .deb file on my mac, and install it.
But, apparently I need   dpkg   to do so.
I have an intel mac, 10.5.6.
Xcode 3.1.1
some third part apps that are in my /usr/local directory are "ntfs-3g"  
which allows the mac to see ntfs partitions,
and fuse stuff which i don't know anything about.

Menz-MacBook:~ Mike$ uname -a
Darwin Menz-MacBook.local 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov  
24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386 i386

Menz-MacBook:~ Mike$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.5.6
BuildVersion:	9G55


so in the terminal, this is what happens:

Menz-MacBook:~ Mike$ sudo port install dpkg
Password:
--->  Configuring expat
Error: Target org.macports.configure returned: configure failure:  
shell command " cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_textproc_expat/work/expat-2.0.1" && ./ 
configure --prefix=/opt/local --mandir=/opt/local/share/man " returned  
error 77
Command output: checking build system type... i386-apple-darwin9.6.0
checking host system type... i386-apple-darwin9.6.0
checking for gcc... /usr/bin/gcc-4.0
checking for C compiler default output file name... configure: error:  
C compiler cannot create executables
See `config.log' for more details.

Error: The following dependencies failed to build: gettext expat  
libiconv gperf ncurses ncursesw gmake
Error: Status 1 encountered during processing.


What do I do to get dpkg to install correctly, or to open these .deb  
files in mac?
Also, I'm running Ubuntu in VMware Fusion, so I have access to all the  
dpkg directories in there...
any help would be TOO great.


Michael Mensinger
Theta Xi Fraternity
Electrical Engineer
Bradley University
mmensinger at mail.bradley.edu
630-297-6979


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090115/53ff0370/attachment.html>

From jmr at macports.org  Thu Jan 15 13:24:18 2009
From: jmr at macports.org (Joshua Root)
Date: Fri, 16 Jan 2009 08:24:18 +1100
Subject: dpkg problems
In-Reply-To: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
Message-ID: <496FA982.70407@macports.org>

Michael Mensinger wrote:
> hey there everybody.
> So, I'm a new linux person, and I love my mac, so I want to open a .deb
> file on my mac, and install it.
> But, apparently I need   dpkg   to do so.
> I have an intel mac, 10.5.6.
> Xcode 3.1.1
> some third part apps that are in my /usr/local directory are "ntfs-3g"
> which allows the mac to see ntfs partitions,
> and fuse stuff which i don't know anything about.
> 
> Menz-MacBook:~ Mike$ uname -a
> Darwin Menz-MacBook.local 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24
> 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386 i386
> 
> Menz-MacBook:~ Mike$ sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.5.6
> BuildVersion: 9G55
> 
> 
> so in the terminal, this is what happens:
> 
> Menz-MacBook:~ Mike$ sudo port install dpkg
> Password:
> --->  Configuring expat
> Error: Target org.macports.configure returned: configure failure: shell
> command " cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_expat/work/expat-2.0.1"
> && ./configure --prefix=/opt/local --mandir=/opt/local/share/man "
> returned error 77
> Command output: checking build system type... i386-apple-darwin9.6.0
> checking host system type... i386-apple-darwin9.6.0
> checking for gcc... /usr/bin/gcc-4.0
> checking for C compiler default output file name... configure: error: C
> compiler cannot create executables
> See `config.log' for more details.

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

- Josh

From jeremyhu at macports.org  Thu Jan 15 13:33:04 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Thu, 15 Jan 2009 13:33:04 -0800
Subject: dpkg problems
In-Reply-To: <496FA982.70407@macports.org>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
	<496FA982.70407@macports.org>
Message-ID: <E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>


On Jan 15, 2009, at 13:24, Joshua Root wrote:
>> checking for C compiler default output file name... configure:  
>> error: C
>> compiler cannot create executables
>> See `config.log' for more details.
>
> <http://trac.macports.org/wiki/FAQ#IgettheerrorCcompilercannotcreateexecutableswhenItrytoinstallaport 
> >

And if that doesn't work, look through config.log "for more details".   
It'll be somewhere in $prefix/var/macports/build/*expat/work ...  
likely /opt/local/var/macports/build/*expat/work/expat-*/config.log

--Jeremy

From christopher.rob.jones at cern.ch  Thu Jan 15 13:43:05 2009
From: christopher.rob.jones at cern.ch (Chris Jones)
Date: Thu, 15 Jan 2009 22:43:05 +0100
Subject: dpkg problems
In-Reply-To: <E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
	<496FA982.70407@macports.org>
	<E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
Message-ID: <9C11B4F9-0245-4F2B-8902-10CD631212AE@cern.ch>


Hi,

Slightly OT, but what packages can be installed on the mac using  
dpkg ? - Coming from a linux background myself quite recently to OSX,  
I'm just curious ;)

Chris

On 15 Jan 2009, at 10:33PM, Jeremy Huddleston wrote:

>
> On Jan 15, 2009, at 13:24, Joshua Root wrote:
>>> checking for C compiler default output file name... configure:  
>>> error: C
>>> compiler cannot create executables
>>> See `config.log' for more details.
>>
>> <http://trac.macports.org/wiki/FAQ#IgettheerrorCcompilercannotcreateexecutableswhenItrytoinstallaport 
>> >
>
> And if that doesn't work, look through config.log "for more  
> details".  It'll be somewhere in $prefix/var/macports/build/*expat/ 
> work ... likely /opt/local/var/macports/build/*expat/work/expat-*/ 
> config.log


From afb at macports.org  Thu Jan 15 13:48:39 2009
From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=)
Date: Thu, 15 Jan 2009 22:48:39 +0100
Subject: dpkg problems
In-Reply-To: <9C11B4F9-0245-4F2B-8902-10CD631212AE@cern.ch>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
	<496FA982.70407@macports.org>
	<E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
	<9C11B4F9-0245-4F2B-8902-10CD631212AE@cern.ch>
Message-ID: <EFF5A82B-379C-4D87-A6B8-9F9E13322846@macports.org>

Chris Jones wrote:

> Slightly OT, but what packages can be installed on the mac using  
> dpkg ?

Fink ones ? MacPorts has better support for RPM than what it does for  
DEB.

--anders


From martin at siarp.de  Thu Jan 15 13:51:44 2009
From: martin at siarp.de (Martin Stadler)
Date: Thu, 15 Jan 2009 22:51:44 +0100
Subject: zope2.10
Message-ID: <182B9E0C-2EAF-48E5-B39C-946386EE763B@siarp.de>

Hi!

I'd like to have a zope2.10 port.

There's a "zope" port which is currently at version 2.8.7. I think it  
would be reasonable to have multiple Zope ports like 2.9, 2.10, 2.11  
etc. as it is the case with the Python ports for instance.

I had a look at the current Zope port and it also creates Zope  
instance. Linux distributions like Debian have a separate package  
called zope2.10-sandbox or zope2.9-instance or so. I like this concept  
more since I personally don't need a prepared instance.

The existing Zope port installs Zope into ${prefix}/libexec, Debian  
in /usr/lib. I don't know much about Unix directory structure  
conventions so I can't tell what fits better.

Here's my quick version of a zope2.10 port:

----------
# $Id$

PortSystem        1.0
name              zope2.10
version           2.10.7
categories        www zope python
maintainers       nomaintainer
description       Object-Oriented Python Web Application Server
long_description  Zope is a leading open source application server, \
                   specializing in content management, portals, and \
                   custom applications.
platforms         darwin
homepage          http://www.zope.org
master_sites      ${homepage}/Products/Zope/${version}/${version}
distname          Zope-${version}-final
extract.suffix    .tgz
checksums         md5 add70c8b46ef8ab6f43780344478f3f7
depends_build     port:python24
extract.post_args | gnutar -xf -
configure.args    --prefix=${prefix}/libexec/zope2.10 --with-python=$ 
{prefix}/bin/python2.4
build.target      default
destroot.destdir  PREFIX=${destroot}${prefix}/libexec/zope2.10

----------

I'd be happy to get some comments.

Cheers,
Martin


From mmensinger at mail.bradley.edu  Thu Jan 15 13:55:20 2009
From: mmensinger at mail.bradley.edu (Michael Mensinger)
Date: Thu, 15 Jan 2009 15:55:20 -0600
Subject: dpkg problems
In-Reply-To: <9C11B4F9-0245-4F2B-8902-10CD631212AE@cern.ch>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
	<496FA982.70407@macports.org>
	<E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
	<9C11B4F9-0245-4F2B-8902-10CD631212AE@cern.ch>
Message-ID: <444C3542-EF83-45CC-A191-C1BDD7640D4A@bradley.edu>

haha yea of course. It's a printer driver hidden inside a deb file.  
wouldn't ya know it. Mac has no support for network printing, but I  
was able to do it using linux. So i'm trying to rig this driver to  
work in mac too.
it beats doing homework, let me tell ya that.
oh thanks everyone for the replies, i'll see what happens and post the  
config.log file


On Jan 15, 2009, at 3:43 PM, Chris Jones wrote:

>
> Hi,
>
> Slightly OT, but what packages can be installed on the mac using  
> dpkg ? - Coming from a linux background myself quite recently to  
> OSX, I'm just curious ;)
>
> Chris
>
> On 15 Jan 2009, at 10:33PM, Jeremy Huddleston wrote:
>
>>
>> On Jan 15, 2009, at 13:24, Joshua Root wrote:
>>>> checking for C compiler default output file name... configure:  
>>>> error: C
>>>> compiler cannot create executables
>>>> See `config.log' for more details.
>>>
>>> <http://trac.macports.org/wiki/FAQ#IgettheerrorCcompilercannotcreateexecutableswhenItrytoinstallaport 
>>> >
>>
>> And if that doesn't work, look through config.log "for more  
>> details".  It'll be somewhere in $prefix/var/macports/build/*expat/ 
>> work ... likely /opt/local/var/macports/build/*expat/work/expat-*/ 
>> config.log
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Michael Mensinger
Theta Xi Fraternity
Electrical Engineer
Bradley University
mmensinger at bradley.edu
630-297-6979




From blb at macports.org  Thu Jan 15 14:01:35 2009
From: blb at macports.org (Bryan Blackburn)
Date: Thu, 15 Jan 2009 15:01:35 -0700
Subject: dpkg problems
In-Reply-To: <E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
	<496FA982.70407@macports.org>
	<E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
Message-ID: <20090115220135.GB805@ninagal.withay.com>

On Thu, Jan 15, 2009 at 01:33:04PM -0800, Jeremy Huddleston said:
>
> On Jan 15, 2009, at 13:24, Joshua Root wrote:
>>> checking for C compiler default output file name... configure: error: 
>>> C
>>> compiler cannot create executables
>>> See `config.log' for more details.
>>
 
>> <http://trac.macports.org/wiki/FAQ#IgettheerrorCcompilercannotcreateexecutableswhenItrytoinstallaport 
>> >
>
> And if that doesn't work, look through config.log "for more details".   
> It'll be somewhere in $prefix/var/macports/build/*expat/work ... likely 
> /opt/local/var/macports/build/*expat/work/expat-*/config.log

Or just 'cd `port work expat`/*'.

Bryan


>
> --Jeremy

From mmensinger at mail.bradley.edu  Thu Jan 15 14:18:09 2009
From: mmensinger at mail.bradley.edu (Michael Mensinger)
Date: Thu, 15 Jan 2009 16:18:09 -0600
Subject: dpkg problems
In-Reply-To: <20090115220135.GB805@ninagal.withay.com>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
	<496FA982.70407@macports.org>
	<E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
	<20090115220135.GB805@ninagal.withay.com>
Message-ID: <9B3D1A1E-625D-41C4-841F-2FCF2204E5A4@bradley.edu>

what do I do with 'cd `port work expat`/*'    ???
all it did was put my directory to Applications

Menz-MacBook:~ Mike$ cd `port work expat`/*
Menz-MacBook:Applications Mike$
now what? sorry i'm new....

On Jan 15, 2009, at 4:01 PM, Bryan Blackburn wrote:

> On Thu, Jan 15, 2009 at 01:33:04PM -0800, Jeremy Huddleston said:
>>
>> On Jan 15, 2009, at 13:24, Joshua Root wrote:
>>>> checking for C compiler default output file name... configure:  
>>>> error:
>>>> C
>>>> compiler cannot create executables
>>>> See `config.log' for more details.
>>>
>
>>> <http://trac.macports.org/wiki/FAQ#IgettheerrorCcompilercannotcreateexecutableswhenItrytoinstallaport
>>>>
>>
>> And if that doesn't work, look through config.log "for more details".
>> It'll be somewhere in $prefix/var/macports/build/*expat/work ...  
>> likely
>> /opt/local/var/macports/build/*expat/work/expat-*/config.log
>
> Or just 'cd `port work expat`/*'.
>
> Bryan
>
>
>>
>> --Jeremy
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Michael Mensinger
Theta Xi Fraternity
Electrical Engineer
Bradley University
mmensinger at bradley.edu
630-297-6979




From ryandesign at macports.org  Thu Jan 15 15:49:57 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 15 Jan 2009 17:49:57 -0600
Subject: Error trying to upgrade
In-Reply-To: <4b75340e0901150349y1b71a49cif7a607491f941ee3@mail.gmail.com>
References: <4b75340e0901141827y1116d55fgda38b62d00651d59@mail.gmail.com>
	<D1124080-9616-4EED-80F8-2D8EF0B88B90@macports.org>
	<20090115051128.GK711@ninagal.withay.com>
	<122FA984-21D7-4640-949B-3D2116726075@macports.org>
	<4b75340e0901150349y1b71a49cif7a607491f941ee3@mail.gmail.com>
Message-ID: <6511BF6E-864B-4166-A051-4ADF16BFF5EE@macports.org>

On Jan 15, 2009, at 05:49, Doctor Who wrote:

> On Thu, Jan 15, 2009 at 1:11 AM, Ryan Schmidt wrote:
>
>> On Jan 14, 2009, at 23:11, Bryan Blackburn wrote:
>>
>>> On Wed, Jan 14, 2009 at 09:55:59PM -0600, Ryan Schmidt said:
>>> [...]
>>>>
>>>> p5-digest-md5, on the other hand, is a perl module, and it  
>>>> happens to
>>>> provide a module (Digest::MD5) which perl itself already provides.
>>>> Perhaps that was added with the recent update to perl 5.8.9. So  
>>>> you may
>>>> not need the p5-digest-md5 port at all; you may be just fine  
>>>> with just
>>>> the
>>>> perl5.8 port. You can try uninstalling p5-digest-md5, or just  
>>>> leave it
>>>> deactivated.
>>>
>>> Don't for get about #12710,
>>>
>>> <http://trac.macports.org/ticket/12710>
>>>
>>> where several modules replace what comes with perl.
>>
>> Indeed. I didn't think p5-digest-md5 was one of those that  
>> traditionally did
>> this, but I see in #12710 that it is. It's just missing the classic
>>
>> post-destroot {
>>    ui_msg "You must install or activate this package with '- 
>> f' (force) as it
>> needs to overwrite files installed by the perl5.8 port"
>> }
>>
>> block.
>
> So does that mean that there's nothing I can do until the bug is  
> addressed?

It means if you need p5-digest-md5, you can force its activation, and  
it will overwrite the similar files that had been provided by the  
perl5.8 port:

sudo port -f activate p5-digest-md5



From blb at macports.org  Thu Jan 15 16:09:42 2009
From: blb at macports.org (Bryan Blackburn)
Date: Thu, 15 Jan 2009 17:09:42 -0700
Subject: dpkg problems
In-Reply-To: <9B3D1A1E-625D-41C4-841F-2FCF2204E5A4@bradley.edu>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
	<496FA982.70407@macports.org>
	<E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
	<20090115220135.GB805@ninagal.withay.com>
	<9B3D1A1E-625D-41C4-841F-2FCF2204E5A4@bradley.edu>
Message-ID: <20090116000942.GD805@ninagal.withay.com>

On Thu, Jan 15, 2009 at 04:18:09PM -0600, Michael Mensinger said:
> what do I do with 'cd `port work expat`/*'    ???
> all it did was put my directory to Applications
>
> Menz-MacBook:~ Mike$ cd `port work expat`/*
> Menz-MacBook:Applications Mike$
> now what? sorry i'm new....

Sounds like maybe the work dir was cleaned, though cd'ing to multiple
directories should have resulted in an error...

If just 'port work expat' returns nothing at all, then it was cleaned,
though I thought autoclean only kicked in when things were successful.

Bryan


>
> On Jan 15, 2009, at 4:01 PM, Bryan Blackburn wrote:
>
>> On Thu, Jan 15, 2009 at 01:33:04PM -0800, Jeremy Huddleston said:
>>>
>>> On Jan 15, 2009, at 13:24, Joshua Root wrote:
>>>>> checking for C compiler default output file name... configure:  
>>>>> error:
>>>>> C
>>>>> compiler cannot create executables
>>>>> See `config.log' for more details.
>>>>
>>
>>>> <http://trac.macports.org/wiki/FAQ#IgettheerrorCcompilercannotcreateexecutableswhenItrytoinstallaport
>>>>>
>>>
>>> And if that doesn't work, look through config.log "for more details".
>>> It'll be somewhere in $prefix/var/macports/build/*expat/work ...  
>>> likely
>>> /opt/local/var/macports/build/*expat/work/expat-*/config.log
>>
>> Or just 'cd `port work expat`/*'.
>>
>> Bryan
>>
>>
>>>
>>> --Jeremy
>
> Michael Mensinger
> Theta Xi Fraternity
> Electrical Engineer
> Bradley University
> mmensinger at bradley.edu
> 630-297-6979
>

From ryandesign at macports.org  Thu Jan 15 16:20:44 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 15 Jan 2009 18:20:44 -0600
Subject: dpkg problems
In-Reply-To: <20090116000942.GD805@ninagal.withay.com>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
	<496FA982.70407@macports.org>
	<E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
	<20090115220135.GB805@ninagal.withay.com>
	<9B3D1A1E-625D-41C4-841F-2FCF2204E5A4@bradley.edu>
	<20090116000942.GD805@ninagal.withay.com>
Message-ID: <1EB0E09A-649D-48D9-8A22-12FD89604998@macports.org>


On Jan 15, 2009, at 18:09, Bryan Blackburn wrote:

> On Thu, Jan 15, 2009 at 04:18:09PM -0600, Michael Mensinger said:
>
>> what do I do with 'cd `port work expat`/*'    ???
>> all it did was put my directory to Applications
>>
>> Menz-MacBook:~ Mike$ cd `port work expat`/*
>> Menz-MacBook:Applications Mike$
>> now what? sorry i'm new....
>
> Sounds like maybe the work dir was cleaned, though cd'ing to multiple
> directories should have resulted in an error...

Doesn't look like it; looks like it cd's to the first item provided.

> If just 'port work expat' returns nothing at all, then it was cleaned,

I think it must have been.

> though I thought autoclean only kicked in when things were successful.

That's correct.


From blb at macports.org  Thu Jan 15 16:34:55 2009
From: blb at macports.org (Bryan Blackburn)
Date: Thu, 15 Jan 2009 17:34:55 -0700
Subject: dpkg problems
In-Reply-To: <1EB0E09A-649D-48D9-8A22-12FD89604998@macports.org>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
	<496FA982.70407@macports.org>
	<E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
	<20090115220135.GB805@ninagal.withay.com>
	<9B3D1A1E-625D-41C4-841F-2FCF2204E5A4@bradley.edu>
	<20090116000942.GD805@ninagal.withay.com>
	<1EB0E09A-649D-48D9-8A22-12FD89604998@macports.org>
Message-ID: <20090116003455.GE805@ninagal.withay.com>

On Thu, Jan 15, 2009 at 06:20:44PM -0600, Ryan Schmidt said:
>
> On Jan 15, 2009, at 18:09, Bryan Blackburn wrote:
>
>> On Thu, Jan 15, 2009 at 04:18:09PM -0600, Michael Mensinger said:
>>
>>> what do I do with 'cd `port work expat`/*'    ???
>>> all it did was put my directory to Applications
>>>
>>> Menz-MacBook:~ Mike$ cd `port work expat`/*
>>> Menz-MacBook:Applications Mike$
>>> now what? sorry i'm new....
>>
>> Sounds like maybe the work dir was cleaned, though cd'ing to multiple
>> directories should have resulted in an error...
>
> Doesn't look like it; looks like it cd's to the first item provided.

At least in my bash:

$ cd /*
-bash: cd: /Applications /Desktop DB /Desktop DF /Developer /Library
/Network /System /Users /Volumes /bin /cores /dev /etc /home /mach_kernel
/mach_kernel.ctfsys /mp /net /opt /private /sbin /tmp /usr /var: No such
file or directory

hence my thinking it'd be an error...maybe some shells just ignore later
arguments?

Bryan


From mmensinger at mail.bradley.edu  Thu Jan 15 16:54:15 2009
From: mmensinger at mail.bradley.edu (Michael Mensinger)
Date: Thu, 15 Jan 2009 18:54:15 -0600
Subject: dpkg problems
In-Reply-To: <20090116003455.GE805@ninagal.withay.com>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
	<496FA982.70407@macports.org>
	<E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
	<20090115220135.GB805@ninagal.withay.com>
	<9B3D1A1E-625D-41C4-841F-2FCF2204E5A4@bradley.edu>
	<20090116000942.GD805@ninagal.withay.com>
	<1EB0E09A-649D-48D9-8A22-12FD89604998@macports.org>
	<20090116003455.GE805@ninagal.withay.com>
Message-ID: <50E53EA0-E7E3-4F3D-AE68-2D0C40559C80@bradley.edu>

hey guys, :) well , as the saying goes,  "ooh, 'Biker'... I'm an Idiot!"
apparently my Xcode just wasn't properly installed or something, or  
the update I got it fixed it. version 3.1.2
So now, macports can properly compile things!
Thanks for your inputs, I can finally move on to important things  
like .....college.   :(
-Mike

On Jan 15, 2009, at 6:34 PM, Bryan Blackburn wrote:

> On Thu, Jan 15, 2009 at 06:20:44PM -0600, Ryan Schmidt said:
>>
>> On Jan 15, 2009, at 18:09, Bryan Blackburn wrote:
>>
>>> On Thu, Jan 15, 2009 at 04:18:09PM -0600, Michael Mensinger said:
>>>
>>>> what do I do with 'cd `port work expat`/*'    ???
>>>> all it did was put my directory to Applications
>>>>
>>>> Menz-MacBook:~ Mike$ cd `port work expat`/*
>>>> Menz-MacBook:Applications Mike$
>>>> now what? sorry i'm new....
>>>
>>> Sounds like maybe the work dir was cleaned, though cd'ing to  
>>> multiple
>>> directories should have resulted in an error...
>>
>> Doesn't look like it; looks like it cd's to the first item provided.
>
> At least in my bash:
>
> $ cd /*
> -bash: cd: /Applications /Desktop DB /Desktop DF /Developer /Library
> /Network /System /Users /Volumes /bin /cores /dev /etc /home / 
> mach_kernel
> /mach_kernel.ctfsys /mp /net /opt /private /sbin /tmp /usr /var: No  
> such
> file or directory
>
> hence my thinking it'd be an error...maybe some shells just ignore  
> later
> arguments?
>
> Bryan
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Michael Mensinger
Theta Xi Fraternity
Electrical Engineer
Bradley University
mmensinger at bradley.edu
630-297-6979




From ryandesign at macports.org  Thu Jan 15 18:25:37 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 15 Jan 2009 20:25:37 -0600
Subject: dpkg problems
In-Reply-To: <20090116003455.GE805@ninagal.withay.com>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
	<496FA982.70407@macports.org>
	<E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
	<20090115220135.GB805@ninagal.withay.com>
	<9B3D1A1E-625D-41C4-841F-2FCF2204E5A4@bradley.edu>
	<20090116000942.GD805@ninagal.withay.com>
	<1EB0E09A-649D-48D9-8A22-12FD89604998@macports.org>
	<20090116003455.GE805@ninagal.withay.com>
Message-ID: <F9932802-AED4-4CFF-8935-5022B268D3BF@macports.org>

On Jan 15, 2009, at 18:34, Bryan Blackburn wrote:

> At least in my bash:
>
> $ cd /*
> -bash: cd: /Applications /Desktop DB /Desktop DF /Developer /Library
> /Network /System /Users /Volumes /bin /cores /dev /etc /home / 
> mach_kernel
> /mach_kernel.ctfsys /mp /net /opt /private /sbin /tmp /usr /var: No  
> such
> file or directory
>
> hence my thinking it'd be an error...maybe some shells just ignore  
> later
> arguments?

How odd -- I can't make bash do that on any of my systems. I've tried  
the bash that comes with Tiger, the one that comes with Leopard, and  
I've tried installing the bash port. They all just try to cd to the  
first argument.

Maybe there's a setting that influences this that you have set?



From blb at macports.org  Thu Jan 15 18:37:44 2009
From: blb at macports.org (Bryan Blackburn)
Date: Thu, 15 Jan 2009 19:37:44 -0700
Subject: dpkg problems
In-Reply-To: <F9932802-AED4-4CFF-8935-5022B268D3BF@macports.org>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>
	<496FA982.70407@macports.org>
	<E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>
	<20090115220135.GB805@ninagal.withay.com>
	<9B3D1A1E-625D-41C4-841F-2FCF2204E5A4@bradley.edu>
	<20090116000942.GD805@ninagal.withay.com>
	<1EB0E09A-649D-48D9-8A22-12FD89604998@macports.org>
	<20090116003455.GE805@ninagal.withay.com>
	<F9932802-AED4-4CFF-8935-5022B268D3BF@macports.org>
Message-ID: <20090116023744.GH805@ninagal.withay.com>

On Thu, Jan 15, 2009 at 08:25:37PM -0600, Ryan Schmidt said:
> On Jan 15, 2009, at 18:34, Bryan Blackburn wrote:
>
>> At least in my bash:
>>
>> $ cd /*
>> -bash: cd: /Applications /Desktop DB /Desktop DF /Developer /Library
>> /Network /System /Users /Volumes /bin /cores /dev /etc /home / 
>> mach_kernel
>> /mach_kernel.ctfsys /mp /net /opt /private /sbin /tmp /usr /var: No  
>> such
>> file or directory
>>
>> hence my thinking it'd be an error...maybe some shells just ignore  
>> later
>> arguments?
>
> How odd -- I can't make bash do that on any of my systems. I've tried the 
> bash that comes with Tiger, the one that comes with Leopard, and I've 
> tried installing the bash port. They all just try to cd to the first 
> argument.
>
> Maybe there's a setting that influences this that you have set?

Ah, of course; I have cd aliased to set the window title...clearing that I
do see /* sets cwd to /Applications.  Configurability is fun.

Bryan


From jmr at macports.org  Fri Jan 16 00:35:14 2009
From: jmr at macports.org (Joshua Root)
Date: Fri, 16 Jan 2009 19:35:14 +1100
Subject: dpkg problems
In-Reply-To: <444C3542-EF83-45CC-A191-C1BDD7640D4A@bradley.edu>
References: <E7FD028A-0A4B-4FDC-AAC5-9832C7F44386@bradley.edu>	<496FA982.70407@macports.org>	<E00E620C-CAF8-4E4C-BCFA-497D0F813A54@macports.org>	<9C11B4F9-0245-4F2B-8902-10CD631212AE@cern.ch>
	<444C3542-EF83-45CC-A191-C1BDD7640D4A@bradley.edu>
Message-ID: <497046C2.50805@macports.org>

Michael Mensinger wrote:
> Mac has no support for network printing,

I'm not sure where you got that idea. There's a Printer Sharing setting
in the Sharing pane of System Preferences, and printers shared by other
platforms also show up in the list of printers in the Print dialog box.

- Josh

From cedayiv at gmail.com  Fri Jan 16 01:50:37 2009
From: cedayiv at gmail.com (Charles Day)
Date: Fri, 16 Jan 2009 01:50:37 -0800
Subject: install slib-guile hangs on activation
Message-ID: <1d6843d80901160150p3b638a79i64c96ee2a15b4733@mail.gmail.com>

I can't seem to install slib-guile without a hang during the activation
stage. Any ideas? I looked through the tickets but they all seemed to be
focused on slib-guile16.

Cheers,
Charles

$ sudo port -d install slib-guile
DEBUG: Found port in file:///opt/local/var/macports/sources/
rsync.macports.org/release/ports/devel/slib-guile
DEBUG: Changing to port directory: /opt/local/var/macports/sources/
rsync.macports.org/release/ports/devel/slib-guile
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: not using configure, so not adding the default universal variant
DEBUG: Requested variant darwin is not provided by port slib-guile.
DEBUG: Requested variant i386 is not provided by port slib-guile.
DEBUG: Requested variant no_x11 is not provided by port slib-guile.
DEBUG: Requested variant macosx is not provided by port slib-guile.
DEBUG: Requested variant quartz is not provided by port slib-guile.
DEBUG: Found port in file:///opt/local/var/macports/sources/
rsync.macports.org/release/ports/devel/slib
DEBUG: Changing to port directory: /opt/local/var/macports/sources/
rsync.macports.org/release/ports/devel/slib
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: not using configure, so not adding the default universal variant
DEBUG: Requested variant darwin is not provided by port slib.
DEBUG: Requested variant i386 is not provided by port slib.
DEBUG: Requested variant no_x11 is not provided by port slib.
DEBUG: Requested variant macosx is not provided by port slib.
DEBUG: Requested variant quartz is not provided by port slib.
DEBUG: Searching for dependency: slib
DEBUG: Found Dependency: receipt exists for slib
DEBUG: Found port in file:///opt/local/var/macports/sources/
rsync.macports.org/release/ports/lang/guile
DEBUG: Changing to port directory: /opt/local/var/macports/sources/
rsync.macports.org/release/ports/lang/guile
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 darwin is not provided by port guile.
DEBUG: Requested variant i386 is not provided by port guile.
DEBUG: Requested variant no_x11 is not provided by port guile.
DEBUG: Requested variant macosx is not provided by port guile.
DEBUG: Requested variant quartz is not provided by port guile.
DEBUG: Searching for dependency: guile
DEBUG: Found Dependency: receipt exists for guile
DEBUG: Executing org.macports.main (slib-guile)
DEBUG: Skipping completed org.macports.fetch (slib-guile)
DEBUG: Skipping completed org.macports.checksum (slib-guile)
DEBUG: Skipping completed org.macports.extract (slib-guile)
DEBUG: Skipping completed org.macports.patch (slib-guile)
DEBUG: Skipping completed org.macports.configure (slib-guile)
DEBUG: Skipping completed org.macports.build (slib-guile)
DEBUG: Skipping completed org.macports.destroot (slib-guile)
--->  Installing slib-guile @1.0_2
DEBUG: Executing org.macports.install (slib-guile)
DEBUG: installing directory:
/opt/local/var/macports/software/slib-guile/1.0_2/opt
DEBUG: installing directory:
/opt/local/var/macports/software/slib-guile/1.0_2/opt/local
DEBUG: installing directory:
/opt/local/var/macports/software/slib-guile/1.0_2/opt/local/share
DEBUG: installing directory:
/opt/local/var/macports/software/slib-guile/1.0_2/opt/local/share/guile
DEBUG: installing directory:
/opt/local/var/macports/software/slib-guile/1.0_2/opt/local/share/guile/1.8
DEBUG: installing link:
/opt/local/var/macports/software/slib-guile/1.0_2/opt/local/share/guile/1.8/slib
DEBUG: installing link:
/opt/local/var/macports/software/slib-guile/1.0_2/opt/local/share/guile/slib
DEBUG: Executing org.macports.activate (slib-guile)
--->  Activating slib-guile @1.0_2
DEBUG: activating directory: /
DEBUG: activating directory: /opt
DEBUG: activating directory: /opt/local
DEBUG: activating directory: /opt/local/share
DEBUG: activating directory: /opt/local/share/guile
DEBUG: activating directory: /opt/local/share/guile/1.8
DEBUG: activating link: /opt/local/share/guile/1.8/slib
DEBUG: activating link: /opt/local/share/guile/slib
DEBUG: Adding link to file_map: /opt/local/share/guile/1.8/slib for:
slib-guile
DEBUG: Adding link to file_map: /opt/local/share/guile/slib for: slib-guile
DEBUG: Executing proc-post-org.macports.activate-activate-0
(hang)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090116/b06bbbf9/attachment.html>

From face at CentosPrime.COM  Fri Jan 16 04:19:25 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Fri, 16 Jan 2009 05:19:25 -0700
Subject: libiconv fails to upgrade on Panther
Message-ID: <9439FC96-9220-4609-8360-623BEA07C40A@centosprime.com>


--->  Configuring libiconv
Error: Target org.macports.configure returned: shell command "cd /opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_textproc_libiconv/work/libiconv-1.12 &&  
patch -b -p0 < /opt/local/var/macports/sources/rsync.macports.org/ 
release/ports/textproc/libiconv/files/patch-64-bit.diff && touch stamp- 
h1" returned error 1
Command output: patching file config.h
Hunk #1 FAILED at 2.
1 out of 2 hunks FAILED -- saving rejects to file config.h.rej
patching file srclib/stdint.in.h

Error: Unable to upgrade port: 1

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



From face at CentosPrime.COM  Fri Jan 16 04:23:15 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Fri, 16 Jan 2009 05:23:15 -0700
Subject: libiconv fails to upgrade on Leopard
Message-ID: <832A6BC0-9D4A-4366-ABC4-76BD3906454F@centosprime.com>

running from trunk

mac 10 # sudo port upgrade libiconv
--->  Fetching libiconv
--->  Verifying checksum(s) for libiconv
--->  Extracting libiconv
--->  Applying patches to libiconv
--->  Configuring libiconv
Error: Target org.macports.configure returned: shell command "cd /opt/ 
local/var/macports/build/_opt_mports_trunk_dports_textproc_libiconv/ 
work/libiconv-1.12 && patch -b -p0 < /opt/mports/trunk/dports/textproc/ 
libiconv/files/patch-64-bit.diff && touch stamp-h1" returned error 1
Command output: patching file config.h
Hunk #1 FAILED at 2.
1 out of 2 hunks FAILED -- saving rejects to file config.h.rej
patching file srclib/stdint.in.h

Error: Unable to upgrade port: 1

at least it's just as broke as my Panther system.

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



From ryandesign at macports.org  Fri Jan 16 07:30:37 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 16 Jan 2009 09:30:37 -0600
Subject: libiconv fails to upgrade on Panther
In-Reply-To: <9439FC96-9220-4609-8360-623BEA07C40A@centosprime.com>
References: <9439FC96-9220-4609-8360-623BEA07C40A@centosprime.com>
Message-ID: <F32E445E-7B6A-484D-A2AE-107F8FB3ED39@macports.org>

Yes, I'm sorry, I screwed it up:

http://trac.macports.org/ticket/17982#comment:4


On Jan 16, 2009, at 06:19, Chris Janton wrote:

> --->  Configuring libiconv
> Error: Target org.macports.configure returned: shell command "cd / 
> opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_textp 
> roc_libiconv/work/libiconv-1.12 && patch -b -p0 < /opt/local/var/ 
> macports/sources/rsync.macports.org/release/ports/textproc/libiconv/ 
> files/patch-64-bit.diff && touch stamp-h1" returned error 1
> Command output: patching file config.h
> Hunk #1 FAILED at 2.
> 1 out of 2 hunks FAILED -- saving rejects to file config.h.rej
> patching file srclib/stdint.in.h
>
> Error: Unable to upgrade port: 1


From ryandesign at macports.org  Fri Jan 16 07:30:48 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 16 Jan 2009 09:30:48 -0600
Subject: libiconv fails to upgrade on Leopard
In-Reply-To: <832A6BC0-9D4A-4366-ABC4-76BD3906454F@centosprime.com>
References: <832A6BC0-9D4A-4366-ABC4-76BD3906454F@centosprime.com>
Message-ID: <4B733057-67A6-46E2-9CF8-ADF26BF73727@macports.org>

Yes, I'm sorry, I screwed it up:

http://trac.macports.org/ticket/17982#comment:4


On Jan 16, 2009, at 06:23, Chris Janton wrote:

> running from trunk
>
> mac 10 # sudo port upgrade libiconv
> --->  Fetching libiconv
> --->  Verifying checksum(s) for libiconv
> --->  Extracting libiconv
> --->  Applying patches to libiconv
> --->  Configuring libiconv
> Error: Target org.macports.configure returned: shell command "cd / 
> opt/local/var/macports/build/ 
> _opt_mports_trunk_dports_textproc_libiconv/work/libiconv-1.12 &&  
> patch -b -p0 < /opt/mports/trunk/dports/textproc/libiconv/files/ 
> patch-64-bit.diff && touch stamp-h1" returned error 1
> Command output: patching file config.h
> Hunk #1 FAILED at 2.
> 1 out of 2 hunks FAILED -- saving rejects to file config.h.rej
> patching file srclib/stdint.in.h
>
> Error: Unable to upgrade port: 1
>
> at least it's just as broke as my Panther system.




From e_wiemann at gmx.de  Fri Jan 16 07:57:35 2009
From: e_wiemann at gmx.de (Eckhard Wiemann)
Date: Fri, 16 Jan 2009 16:57:35 +0100
Subject: History in port's cmd line available?
Message-ID: <F952F5A2-FF6F-43B2-BF84-3B840A9062F3@gmx.de>

Hi all,

does anybody know if a command history is available in port's  
interactive mode? It would be nice if I could correct type-errors in  
a more comfortable way than typing the line again. Tab-completion  
would be appreciated, too.

Thanks!

Eckhard.

Using Mac OS 10.4.11 on a MacBook with X11 1.1.3 (installed with  
XCode via DVD) and ratpoison window manager.

From jmr at macports.org  Fri Jan 16 08:23:19 2009
From: jmr at macports.org (Joshua Root)
Date: Sat, 17 Jan 2009 03:23:19 +1100
Subject: History in port's cmd line available?
In-Reply-To: <F952F5A2-FF6F-43B2-BF84-3B840A9062F3@gmx.de>
References: <F952F5A2-FF6F-43B2-BF84-3B840A9062F3@gmx.de>
Message-ID: <4970B477.8090801@macports.org>

Eckhard Wiemann wrote:
> Hi all,
> 
> does anybody know if a command history is available in port's
> interactive mode? It would be nice if I could correct type-errors in a
> more comfortable way than typing the line again. Tab-completion would be
> appreciated, too.

It is available, but only if you install from the dmg, or build from
source and pass --enable-readline to configure. (IOW, you lose readline
support when you selfupdate.)

An alternative would be to not use interactive mode and install the
bash-completion port, which gives you tab completion for the port command.

- Josh

From ryandesign at macports.org  Fri Jan 16 08:29:15 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 16 Jan 2009 10:29:15 -0600
Subject: libiconv fails to upgrade on Leopard
In-Reply-To: <4B733057-67A6-46E2-9CF8-ADF26BF73727@macports.org>
References: <832A6BC0-9D4A-4366-ABC4-76BD3906454F@centosprime.com>
	<4B733057-67A6-46E2-9CF8-ADF26BF73727@macports.org>
Message-ID: <37B47D3E-6A12-427C-B972-1955B73B878E@macports.org>

Should be fixed now. You'll need to "port sync" first, of course.


On Jan 16, 2009, at 09:30, Ryan Schmidt wrote:

> Yes, I'm sorry, I screwed it up:
>
> http://trac.macports.org/ticket/17982#comment:4
>
>
> On Jan 16, 2009, at 06:23, Chris Janton wrote:
>
>> running from trunk
>>
>> mac 10 # sudo port upgrade libiconv
>> --->  Fetching libiconv
>> --->  Verifying checksum(s) for libiconv
>> --->  Extracting libiconv
>> --->  Applying patches to libiconv
>> --->  Configuring libiconv
>> Error: Target org.macports.configure returned: shell command "cd / 
>> opt/local/var/macports/build/ 
>> _opt_mports_trunk_dports_textproc_libiconv/work/libiconv-1.12 &&  
>> patch -b -p0 < /opt/mports/trunk/dports/textproc/libiconv/files/ 
>> patch-64-bit.diff && touch stamp-h1" returned error 1
>> Command output: patching file config.h
>> Hunk #1 FAILED at 2.
>> 1 out of 2 hunks FAILED -- saving rejects to file config.h.rej
>> patching file srclib/stdint.in.h
>>
>> Error: Unable to upgrade port: 1
>>
>> at least it's just as broke as my Panther system.



From jberry at macports.org  Fri Jan 16 08:29:31 2009
From: jberry at macports.org (James Berry)
Date: Fri, 16 Jan 2009 08:29:31 -0800
Subject: History in port's cmd line available?
In-Reply-To: <4970B477.8090801@macports.org>
References: <F952F5A2-FF6F-43B2-BF84-3B840A9062F3@gmx.de>
	<4970B477.8090801@macports.org>
Message-ID: <081D04EC-4FE5-4CDD-A669-1FE05B9B2AF3@macports.org>


On Jan 16, 2009, at 8:23 AM, Joshua Root wrote:

> Eckhard Wiemann wrote:
>> Hi all,
>>
>> does anybody know if a command history is available in port's
>> interactive mode? It would be nice if I could correct type-errors  
>> in a
>> more comfortable way than typing the line again. Tab-completion  
>> would be
>> appreciated, too.
>
> It is available, but only if you install from the dmg, or build from
> source and pass --enable-readline to configure. (IOW, you lose  
> readline
> support when you selfupdate.)

Hmm, kindof tweaky, but maybe we need a setting for extra  
configuration to be passed into the selfupdate build?

James

>
>
> An alternative would be to not use interactive mode and install the
> bash-completion port, which gives you tab completion for the port  
> command.
>
> - Josh
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From jberry at macports.org  Fri Jan 16 08:33:54 2009
From: jberry at macports.org (James Berry)
Date: Fri, 16 Jan 2009 08:33:54 -0800
Subject: History in port's cmd line available?
In-Reply-To: <081D04EC-4FE5-4CDD-A669-1FE05B9B2AF3@macports.org>
References: <F952F5A2-FF6F-43B2-BF84-3B840A9062F3@gmx.de>
	<4970B477.8090801@macports.org>
	<081D04EC-4FE5-4CDD-A669-1FE05B9B2AF3@macports.org>
Message-ID: <B9EBDC29-947B-4884-8A62-80A963465B34@macports.org>


On Jan 16, 2009, at 8:29 AM, James Berry wrote:

>
> On Jan 16, 2009, at 8:23 AM, Joshua Root wrote:
>
>> Eckhard Wiemann wrote:
>>> Hi all,
>>>
>>> does anybody know if a command history is available in port's
>>> interactive mode? It would be nice if I could correct type-errors  
>>> in a
>>> more comfortable way than typing the line again. Tab-completion  
>>> would be
>>> appreciated, too.
>>
>> It is available, but only if you install from the dmg, or build from
>> source and pass --enable-readline to configure. (IOW, you lose  
>> readline
>> support when you selfupdate.)
>
> Hmm, kindof tweaky, but maybe we need a setting for extra  
> configuration to be passed into the selfupdate build?

Even better, maybe we can fix the readline and broader /usr/local  
issue by using the (new in gcc 4.3?) option -nostdinc?

James

>
>
> James
>
>>
>>
>> An alternative would be to not use interactive mode and install the
>> bash-completion port, which gives you tab completion for the port  
>> command.
>>
>> - 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 brad at pixilla.com  Fri Jan 16 09:07:59 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Fri, 16 Jan 2009 09:07:59 -0800
Subject: History in port's cmd line available?
In-Reply-To: <4970B477.8090801@macports.org>
References: <F952F5A2-FF6F-43B2-BF84-3B840A9062F3@gmx.de>
	<4970B477.8090801@macports.org>
Message-ID: <CB12BCA4-AA70-4408-9644-DEE734BB421C@pixilla.com>


On Jan 16, 2009, at 8:23 AM, Joshua Root wrote:

> Eckhard Wiemann wrote:
>> Hi all,
>>
>> does anybody know if a command history is available in port's
>> interactive mode? It would be nice if I could correct type-errors  
>> in a
>> more comfortable way than typing the line again. Tab-completion  
>> would be
>> appreciated, too.
>
> It is available, but only if you install from the dmg, or build from
> source and pass --enable-readline to configure. (IOW, you lose  
> readline
> support when you selfupdate.)
>
> An alternative would be to not use interactive mode and install the
> bash-completion port, which gives you tab completion for the port  
> command.

That's a very nice tip. Thank you.

From face at CentosPrime.COM  Fri Jan 16 11:42:37 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Fri, 16 Jan 2009 12:42:37 -0700
Subject: libiconv fails to upgrade on Leopard
In-Reply-To: <37B47D3E-6A12-427C-B972-1955B73B878E@macports.org>
References: <832A6BC0-9D4A-4366-ABC4-76BD3906454F@centosprime.com>
	<4B733057-67A6-46E2-9CF8-ADF26BF73727@macports.org>
	<37B47D3E-6A12-427C-B972-1955B73B878E@macports.org>
Message-ID: <5846E63D-737D-481A-AC1B-ED605916468B@CentosPrime.COM>

On 2009-01-16 , at 09:29 , Ryan Schmidt wrote:

> Should be fixed now. You'll need to "port sync" first, of course.


libiconv upgrade now works on both Panther and Leopard.

Thanks.

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



From raimue at macports.org  Fri Jan 16 12:31:49 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Fri, 16 Jan 2009 21:31:49 +0100
Subject: History in port's cmd line available?
In-Reply-To: <B9EBDC29-947B-4884-8A62-80A963465B34@macports.org>
References: <F952F5A2-FF6F-43B2-BF84-3B840A9062F3@gmx.de>	<4970B477.8090801@macports.org>	<081D04EC-4FE5-4CDD-A669-1FE05B9B2AF3@macports.org>
	<B9EBDC29-947B-4884-8A62-80A963465B34@macports.org>
Message-ID: <4970EEB5.10901@macports.org>

James Berry wrote:
> Even better, maybe we can fix the readline and broader /usr/local  
> issue by using the (new in gcc 4.3?) option -nostdinc?

Apple is currently providing gcc 4.0 as default in Xcode and
additionally gcc 4.2. I don't think it is a good idea to add gcc >=4.3
as a dependency for selfupdate.

Rainer

From jberry at macports.org  Fri Jan 16 12:43:14 2009
From: jberry at macports.org (James Berry)
Date: Fri, 16 Jan 2009 12:43:14 -0800
Subject: History in port's cmd line available?
In-Reply-To: <4970EEB5.10901@macports.org>
References: <F952F5A2-FF6F-43B2-BF84-3B840A9062F3@gmx.de>	<4970B477.8090801@macports.org>	<081D04EC-4FE5-4CDD-A669-1FE05B9B2AF3@macports.org>
	<B9EBDC29-947B-4884-8A62-80A963465B34@macports.org>
	<4970EEB5.10901@macports.org>
Message-ID: <1E1F4734-5BCC-4F64-9C1C-553FD8019BFD@macports.org>


On Jan 16, 2009, at 12:31 PM, Rainer M?ller wrote:

> James Berry wrote:
>> Even better, maybe we can fix the readline and broader /usr/local
>> issue by using the (new in gcc 4.3?) option -nostdinc?
>
> Apple is currently providing gcc 4.0 as default in Xcode and
> additionally gcc 4.2. I don't think it is a good idea to add gcc >=4.3
> as a dependency for selfupdate.

Actually, looking around, it looks ilke maybe -nostdinc has been  
around since before 3.0.

James

From whodoctor at gmail.com  Fri Jan 16 12:30:43 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Fri, 16 Jan 2009 15:30:43 -0500
Subject: Claws-mail port question
In-Reply-To: <4b75340e0901121732x3d5ec59sc8bebc90653b005c@mail.gmail.com>
References: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>
	<4b75340e0901080620j29c62f77i7efdef3c9908db3@mail.gmail.com>
	<22468929-C875-46BA-8BB2-264897687D4D@macports.org>
	<496721CE.3060600@macports.org>
	<4b75340e0901111651xda5c43br58749f62baa93ace@mail.gmail.com>
	<496B0C55.80604@macports.org>
	<4b75340e0901121027k190b3b02m6f439d9ccef83362@mail.gmail.com>
	<496BD6D3.8010806@macports.org>
	<4b75340e0901121732x3d5ec59sc8bebc90653b005c@mail.gmail.com>
Message-ID: <4b75340e0901161230w61684432k845b4d0e877bd3e3@mail.gmail.com>

On Mon, Jan 12, 2009 at 8:32 PM, Doctor Who <whodoctor at gmail.com> wrote:
> On Mon, Jan 12, 2009 at 6:48 PM, Rainer M?ller <raimue at macports.org> wrote:
>> Doctor Who wrote:
>>> I have the aspell-dict-en port installed, but it may have been done
>>> *after* I installed claws-mail.
>>>
>>> Perhaps I need to uninstall and reinstall the claws-mail port for it
>>> to pick up the aspell dictionary?
>>
>> No, there should not be any need to reinstall things. I just installed
>> additional aspell-dict-* ports and they are shown in preferences in
>> claws-mail.
>>
>> Rainer
>>
>
> Hmmm...not sure why it's not working for me :-(
>
> Any ideas?
>

I have both aspell and aspell-dict-en installed and both are active.
Any reason why no dictionary appears in claws-mail for me?

From blb at macports.org  Fri Jan 16 13:22:00 2009
From: blb at macports.org (Bryan Blackburn)
Date: Fri, 16 Jan 2009 14:22:00 -0700
Subject: install slib-guile hangs on activation
In-Reply-To: <1d6843d80901160150p3b638a79i64c96ee2a15b4733@mail.gmail.com>
References: <1d6843d80901160150p3b638a79i64c96ee2a15b4733@mail.gmail.com>
Message-ID: <20090116212200.GC995@ninagal.withay.com>

On Fri, Jan 16, 2009 at 01:50:37AM -0800, Charles Day said:
> I can't seem to install slib-guile without a hang during the activation
> stage. Any ideas? I looked through the tickets but they all seemed to be
> focused on slib-guile16.

It appears to be hanging on the post-activate code:

post-activate {
    system "${prefix}/bin/guile -c \"(use-modules (ice-9 slib)) (require
'new-catalog)\""
}

Why, however, I can't answer so I think we need someone who knows guile.

Bryan


> 
> Cheers,
> Charles
> 
[...]

From cedayiv at gmail.com  Fri Jan 16 15:29:15 2009
From: cedayiv at gmail.com (Charles Day)
Date: Fri, 16 Jan 2009 15:29:15 -0800
Subject: install slib-guile hangs on activation
In-Reply-To: <20090116212200.GC995@ninagal.withay.com>
References: <1d6843d80901160150p3b638a79i64c96ee2a15b4733@mail.gmail.com>
	<20090116212200.GC995@ninagal.withay.com>
Message-ID: <1d6843d80901161529p7db191b0qc8cca47f5b3be514@mail.gmail.com>

On Fri, Jan 16, 2009 at 1:22 PM, Bryan Blackburn <blb at macports.org> wrote:

> On Fri, Jan 16, 2009 at 01:50:37AM -0800, Charles Day said:
> > I can't seem to install slib-guile without a hang during the activation
> > stage. Any ideas? I looked through the tickets but they all seemed to be
> > focused on slib-guile16.
>
> It appears to be hanging on the post-activate code:
>
> post-activate {
>    system "${prefix}/bin/guile -c \"(use-modules (ice-9 slib)) (require
> 'new-catalog)\""
> }
>
> Why, however, I can't answer so I think we need someone who knows guile.
>

It hangs on the first part of the code:  (use-modules (ice-9 slib))

The "require" part never gets executed.

I can reproduce this on the command line:
$ guile
> (use-modules (ice-9 slib))
hangs...

-Charles


> Bryan
>
>
> >
> > Cheers,
> > Charles
> >
> [...]
> _______________________________________________
> 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/20090116/e896a46b/attachment.html>

From ryandesign at macports.org  Fri Jan 16 17:17:24 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 16 Jan 2009 19:17:24 -0600
Subject: zope2.10
In-Reply-To: <182B9E0C-2EAF-48E5-B39C-946386EE763B@siarp.de>
References: <182B9E0C-2EAF-48E5-B39C-946386EE763B@siarp.de>
Message-ID: <454D44FD-3017-430D-BC95-EECB942EED14@macports.org>

Hi Martin. Thanks for your interest in Zope! It looks like the port  
hasn't been updated in some time and it could use some attention from  
someone such as yourself with an interest in the software.


On Jan 15, 2009, at 15:51, Martin Stadler wrote:

> I'd like to have a zope2.10 port.
>
> There's a "zope" port which is currently at version 2.8.7. I think  
> it would be reasonable to have multiple Zope ports like 2.9, 2.10,  
> 2.11 etc. as it is the case with the Python ports for instance.

The reasons why we typically have multiple versioned ports are  
because of incompatibilities between those versions of the software.  
For example, Apache modules are different for Apache 1.x, 2.0.x and  
2.2.x, so we have ports apache (1.x), apache20 (2.0.x) and apache2  
(2.2.x). Python modules build differently for different versions, so  
we have ports python21, python22, python23, python24, python25,  
python26, and python30, and every individual Python module port must  
also be duplicated, e.g. py-setuptools (for 2.4), py25-setuptools  
(for 2.5) and py26-setuptools (for 2.6).

There are also ports for databases like PostgreSQL and MySQL that are  
available in different versions, because the user must convert their  
database data from one version to another, and we want the user to be  
free to do that conversion at a time of their choosing, after they've  
made sufficient backups of their data, and not have it forced on them  
by "port upgrade outdated".

And then we also have ports that exist just to be used as  
dependencies. For example, we have the autoconf port which provides  
the current version 2.63, but PHP requires the much older autoconf  
2.13, so we have the autoconf213 port just for that.

This strategy should be the exception and not the rule. Most ports  
should just exist once in the tree and be updated to the latest version.

Do any of the above scenarios apply to Zope?


> I had a look at the current Zope port and it also creates Zope  
> instance. Linux distributions like Debian have a separate package  
> called zope2.10-sandbox or zope2.9-instance or so. I like this  
> concept more since I personally don't need a prepared instance.

I don't know Zope so I don't know what's appropriate. MacPorts  
usually offers ports that are full-featured if possible. But if the  
prepared instance is a large entity, or requires additional  
downloads, or lots of time to compile, and users will likely want to  
omit it, then MacPorts should offer that option. One way to do that  
would be with variants, but I like multiple smaller ports, as you  
suggest, better, because you can't declare dependencies on variants  
of a port, and it's more trouble to reinstall a port with additional  
variants than it is to just install another port with the additional  
features.


> The existing Zope port installs Zope into ${prefix}/libexec, Debian  
> in /usr/lib. I don't know much about Unix directory structure  
> conventions so I can't tell what fits better.

According to "man porthier", ${prefix}/lib is for libraries --  
generally dynamic libraries (.dylib), static libraries (.a) and  
libtool files (.la) -- while ${prefix}/libexec is for executable  
programs that the user is not meant to execute directly, but which  
are instead executed by some other process.



From HerrPoetry at HailMail.net  Fri Jan 16 22:44:38 2009
From: HerrPoetry at HailMail.net (Mark)
Date: Sat, 17 Jan 2009 01:44:38 -0500
Subject: GnuCash Launcher
Message-ID: <49717E56.5070105@HailMail.net>

I'm looking for a way to launch native Quartz GnuCash without using 
Terminal.

I have just finished a complete fresh install of Macports, followed by a 
native Quartz, minimal (+without_hbci +without_ofx +without_quotes) 
install of GnuCash on MBP 10.5.6.

I used to run, and still have installed, GnuCash2 on Fink. The Fink 
installation broke when I upgraded GnuCash2: started getting the error 
message reported here <http://trac.macports.org/ticket/16755> --

    "Two error windows every time gnucash is launched. One says: "The
    configuration data used to specify default values for GnuCash cannot
    be found in the default system locations. Without this data GnuCash
    will still operate properly but it may require some extra time to
    setup. Do you wish to setup the configuration data?"

    "The other says: "An error occurred while loading or saving
    configuration information for gnucash. Some of your configuration
    settings may not work properly."

    "When I click "Details" on the second window, it says: "Failed to
    contact configuration server..."

I'm pleased to say my Macports installation of native Quartz GnuCash 
works fine IF I open a Terminal and start it from the command line.

I wrote an embarrassingly simplistic Applescript using "do shell script":
    do shell script "/opt/local/bin/gnucash"
which starts GnuCash without launching Terminal.app. But this method 
always results in the two-window error quoted above. By contrast, the 
Applescript:
    tell application "Terminal"
        do script "/opt/local/bin/gnucash >& /dev/null &"
    end tell
opens a Terminal window and GnuCash fires up perfectly.

I've tried incorporating the suggestions in Comment 17 
<http://trac.macports.org/ticket/16755#comment:17> of the above-quoted 
ticket into my "do shell script," but either it doesn't work or it 
requires some Applescript finesse (I have none).

Is there any hope of launching native Quartz GnuCash without wrapping it 
in Terminal?

- Mark (Newbie-ish)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090117/68241dab/attachment.html>

From HerrPoetry at HailMail.net  Fri Jan 16 22:59:52 2009
From: HerrPoetry at HailMail.net (Mark)
Date: Sat, 17 Jan 2009 01:59:52 -0500
Subject: GnuCash Default Font
Message-ID: <497181E8.5070606@HailMail.net>

(I just posted on a related GnuCash topic, so please forgive the 
repetition of my system details.) I have just finished a complete fresh 
install of Macports, followed by a native Quartz, minimal (+without_hbci 
+without_ofx +without_quotes) install of GnuCash on MBP 10.5.6.

I can't figure out how to change the default font for the program. When 
I used to run GnuCash under X11 (Fink package GnuCash2), I had -- and 
still have -- a file in my home directory named .gtkrc-2.0 which 
contains a single line: gtk-font-name = "Luxi Mono 16" -- and that used 
to cause GnuCash to use that font in all its windows.

But not anymore! Apparently native Quartz GnuCash installed via MacPorts 
isn't consulting ~/gtkrc-2.0, or is somehow overriding it? Anything I 
can do to get my big beautiful font back?

- Mark

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090117/4a131771/attachment.html>

From HerrPoetry at HailMail.net  Fri Jan 16 23:10:53 2009
From: HerrPoetry at HailMail.net (Mark)
Date: Sat, 17 Jan 2009 02:10:53 -0500
Subject: GnuCash Launcher
In-Reply-To: <213499.1148.qm@web51910.mail.re2.yahoo.com>
References: <213499.1148.qm@web51910.mail.re2.yahoo.com>
Message-ID: <4971847D.6070206@HailMail.net>

Genius! That worked. Thank you!

- Mark


David T. wrote:
> The errors you describe remind me of the problems I see with the fink version of 2.2.8 under my 10.5.6. The solution here was to follow the instruction to issue the following commands at the terminal prompt:
>
> source /sw/bin/init.sh ; /sw/bin/gnucash &
>
> I created an Automator app that does this in a shell script successfully.
>
> David
>
> --- On Fri, 1/16/09, Mark <HerrPoetry at hailmail.net> wrote:
>
>   
>> From: Mark <HerrPoetry at hailmail.net>
>> Subject: GnuCash Launcher
>> To: macports-users at lists.macosforge.org, gnucash-user at gnucash.org
>> Date: Friday, January 16, 2009, 10:44 PM
>> I'm looking for a way to launch native Quartz GnuCash
>> without using 
>> Terminal.
>>
>> I have just finished a complete fresh install of Macports,
>> followed by a 
>> native Quartz, minimal (+without_hbci +without_ofx
>> +without_quotes) 
>> install of GnuCash on MBP 10.5.6.
>>
>> I used to run, and still have installed, GnuCash2 on Fink.
>> The Fink 
>> installation broke when I upgraded GnuCash2: started
>> getting the error 
>> message reported here
>> <http://trac.macports.org/ticket/16755> --
>>
>>     "Two error windows every time gnucash is launched.
>> One says: "The
>>     configuration data used to specify default values for
>> GnuCash cannot
>>     be found in the default system locations. Without this
>> data GnuCash
>>     will still operate properly but it may require some
>> extra time to
>>     setup. Do you wish to setup the configuration
>> data?"
>>
>>     "The other says: "An error occurred while
>> loading or saving
>>     configuration information for gnucash. Some of your
>> configuration
>>     settings may not work properly."
>>
>>     "When I click "Details" on the second
>> window, it says: "Failed to
>>     contact configuration server..."
>>
>> I'm pleased to say my Macports installation of native
>> Quartz GnuCash 
>> works fine IF I open a Terminal and start it from the
>> command line.
>>
>> I wrote an embarrassingly simplistic Applescript using
>> "do shell script":
>>     do shell script "/opt/local/bin/gnucash"
>> which starts GnuCash without launching Terminal.app. But
>> this method 
>> always results in the two-window error quoted above. By
>> contrast, the 
>> Applescript:
>>     tell application "Terminal"
>>         do script "/opt/local/bin/gnucash >&
>> /dev/null &"
>>     end tell
>> opens a Terminal window and GnuCash fires up perfectly.
>>
>> I've tried incorporating the suggestions in Comment 17 
>> <http://trac.macports.org/ticket/16755#comment:17> of
>> the above-quoted 
>> ticket into my "do shell script," but either it
>> doesn't work or it 
>> requires some Applescript finesse (I have none).
>>
>> Is there any hope of launching native Quartz GnuCash
>> without wrapping it 
>> in Terminal?
>>
>> - Mark (Newbie-ish)
>> _______________________________________________
>> gnucash-user mailing list
>> gnucash-user at gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> -----
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>>     
>
>
>       
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090117/1a416120/attachment.html>

From sunfish62 at yahoo.com  Fri Jan 16 23:12:08 2009
From: sunfish62 at yahoo.com (David T.)
Date: Fri, 16 Jan 2009 23:12:08 -0800 (PST)
Subject: Steps to ensure compatibility between fink and macports
Message-ID: <391652.36615.qm@web51909.mail.re2.yahoo.com>

I am new to this list. I have had a macbook for three years now after moving from 20+years in the PC world with a smattering of Linux. I am running 10.5.6, and I have used fink for my limited open-source software needs (gnucash), but recently saw that others have been able to use MacPorts to create a Quartz version of Gnucash. Since I have a working version of Gnucash using fink, I am leery about just firing up Macports and trying the steps listed by others. Before I do this, I'd like to know with some certainty the steps I need to take to insulate the functional fink package from my fiddling around with MacPorts. I searched for guidance on fink/macports compatibility, but didn't find any clear outlines of how to ensure this. Has anyone got a clear set of steps and guidelines for me to follow to try using macports without messing up fink?

TIA,
David


      

From ryandesign at macports.org  Sat Jan 17 00:58:22 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sat, 17 Jan 2009 02:58:22 -0600
Subject: Steps to ensure compatibility between fink and macports
In-Reply-To: <391652.36615.qm@web51909.mail.re2.yahoo.com>
References: <391652.36615.qm@web51909.mail.re2.yahoo.com>
Message-ID: <AFC4F6B4-AC32-46FA-BE76-2F1780E7C3C7@macports.org>

On Jan 17, 2009, at 01:12, David T. wrote:

> I am new to this list. I have had a macbook for three years now  
> after moving from 20+years in the PC world with a smattering of  
> Linux. I am running 10.5.6, and I have used fink for my limited  
> open-source software needs (gnucash), but recently saw that others  
> have been able to use MacPorts to create a Quartz version of  
> Gnucash. Since I have a working version of Gnucash using fink, I am  
> leery about just firing up Macports and trying the steps listed by  
> others. Before I do this, I'd like to know with some certainty the  
> steps I need to take to insulate the functional fink package from  
> my fiddling around with MacPorts. I searched for guidance on fink/ 
> macports compatibility, but didn't find any clear outlines of how  
> to ensure this. Has anyone got a clear set of steps and guidelines  
> for me to follow to try using macports without messing up fink?

Rename fink's /sw directory to something else. That should ensure it  
does not interfere with MacPorts.

You should only use software installed via one package manager at a  
time -- either Fink, or MacPorts, not both.


From raimue at macports.org  Sat Jan 17 05:38:55 2009
From: raimue at macports.org (=?UTF-8?B?UmFpbmVyIE3DvGxsZXI=?=)
Date: Sat, 17 Jan 2009 14:38:55 +0100
Subject: Claws-mail port question
In-Reply-To: <4b75340e0901161230w61684432k845b4d0e877bd3e3@mail.gmail.com>
References: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>	
	<4b75340e0901080620j29c62f77i7efdef3c9908db3@mail.gmail.com>	
	<22468929-C875-46BA-8BB2-264897687D4D@macports.org>	
	<496721CE.3060600@macports.org>	
	<4b75340e0901111651xda5c43br58749f62baa93ace@mail.gmail.com>	
	<496B0C55.80604@macports.org>	
	<4b75340e0901121027k190b3b02m6f439d9ccef83362@mail.gmail.com>	
	<496BD6D3.8010806@macports.org>	
	<4b75340e0901121732x3d5ec59sc8bebc90653b005c@mail.gmail.com>
	<4b75340e0901161230w61684432k845b4d0e877bd3e3@mail.gmail.com>
Message-ID: <4971DF6F.7010100@macports.org>

Doctor Who wrote:
> I have both aspell and aspell-dict-en installed and both are active.
> Any reason why no dictionary appears in claws-mail for me?

Do you have the enchant port installed? It seems like claws-mail is
using this for spell checking. If not, try installing it and rebuild
claws-mail.

Maybe the dependencies should include enchant, as claws-mail is really
linking to it if available, but I was unable to track it down using
trace mode.

Rainer

From macports.users at gmail.com  Sat Jan 17 08:28:07 2009
From: macports.users at gmail.com (Charles Darwin)
Date: Sat, 17 Jan 2009 11:28:07 -0500
Subject: Is xprobe2 broken?
Message-ID: <C3159964-B770-4C09-845D-796F4542BF40@gmail.com>

-bash-3.2$ sudo xprobe2 -T 1-1024 127.0.0.1

Xprobe2 v.0.3 Copyright (c) 2002-2005 fyodor at o0o.nu, ofir at sys-security.com 
, meder at o0o.nu

[+] Target is 127.0.0.1
[+] Loading modules.
[+] Following modules are loaded:
[x] [1] ping:icmp_ping  -  ICMP echo discovery module
[x] [2] ping:tcp_ping  -  TCP-based ping discovery module
[x] [3] ping:udp_ping  -  UDP-based ping discovery module
[x] [4] infogather:ttl_calc  -  TCP and UDP based TTL distance  
calculation
[x] [5] infogather:portscan  -  TCP and UDP PortScanner
[x] [6] fingerprint:icmp_echo  -  ICMP Echo request fingerprinting  
module
[x] [7] fingerprint:icmp_tstamp  -  ICMP Timestamp request  
fingerprinting module
[x] [8] fingerprint:icmp_amask  -  ICMP Address mask request  
fingerprinting module
[x] [9] fingerprint:icmp_port_unreach  -  ICMP port unreachable  
fingerprinting module
[x] [10] fingerprint:tcp_hshake  -  TCP Handshake fingerprinting module
[x] [11] fingerprint:tcp_rst  -  TCP RST fingerprinting module
[x] [12] fingerprint:smb  -  SMB fingerprinting module
[x] [13] fingerprint:snmp  -  SNMPv2c fingerprinting module
[+] 13 modules registered
[+] Initializing scan engine
[+] Running scan engine
TX_IP::sendpack::sendto: Invalid argument


From pmq at macports.org  Sat Jan 17 10:00:15 2009
From: pmq at macports.org (Pierre Queinnec)
Date: Sat, 17 Jan 2009 19:00:15 +0100
Subject: Is xprobe2 broken?
In-Reply-To: <C3159964-B770-4C09-845D-796F4542BF40@gmail.com>
References: <C3159964-B770-4C09-845D-796F4542BF40@gmail.com>
Message-ID: <49721CAF.7000805@macports.org>

File a bug perhaps?
-- Pierre


Charles Darwin wrote:
> -bash-3.2$ sudo xprobe2 -T 1-1024 127.0.0.1
> 
> Xprobe2 v.0.3 Copyright (c) 2002-2005 fyodor at o0o.nu, 
> ofir at sys-security.com, meder at o0o.nu
> 
> [+] Target is 127.0.0.1
> [+] Loading modules.
> [+] Following modules are loaded:
> [x] [1] ping:icmp_ping  -  ICMP echo discovery module
> [x] [2] ping:tcp_ping  -  TCP-based ping discovery module
> [x] [3] ping:udp_ping  -  UDP-based ping discovery module
> [x] [4] infogather:ttl_calc  -  TCP and UDP based TTL distance calculation
> [x] [5] infogather:portscan  -  TCP and UDP PortScanner
> [x] [6] fingerprint:icmp_echo  -  ICMP Echo request fingerprinting module
> [x] [7] fingerprint:icmp_tstamp  -  ICMP Timestamp request 
> fingerprinting module
> [x] [8] fingerprint:icmp_amask  -  ICMP Address mask request 
> fingerprinting module
> [x] [9] fingerprint:icmp_port_unreach  -  ICMP port unreachable 
> fingerprinting module
> [x] [10] fingerprint:tcp_hshake  -  TCP Handshake fingerprinting module
> [x] [11] fingerprint:tcp_rst  -  TCP RST fingerprinting module
> [x] [12] fingerprint:smb  -  SMB fingerprinting module
> [x] [13] fingerprint:snmp  -  SNMPv2c fingerprinting module
> [+] 13 modules registered
> [+] Initializing scan engine
> [+] Running scan engine
> TX_IP::sendpack::sendto: Invalid argument
> 
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From whodoctor at gmail.com  Sat Jan 17 12:26:15 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Sat, 17 Jan 2009 15:26:15 -0500
Subject: Claws-mail port question
In-Reply-To: <4971DF6F.7010100@macports.org>
References: <4b75340e0901050910t545cbd9fnf7e4e8a93aab4d31@mail.gmail.com>
	<22468929-C875-46BA-8BB2-264897687D4D@macports.org>
	<496721CE.3060600@macports.org>
	<4b75340e0901111651xda5c43br58749f62baa93ace@mail.gmail.com>
	<496B0C55.80604@macports.org>
	<4b75340e0901121027k190b3b02m6f439d9ccef83362@mail.gmail.com>
	<496BD6D3.8010806@macports.org>
	<4b75340e0901121732x3d5ec59sc8bebc90653b005c@mail.gmail.com>
	<4b75340e0901161230w61684432k845b4d0e877bd3e3@mail.gmail.com>
	<4971DF6F.7010100@macports.org>
Message-ID: <4b75340e0901171226i58a626f3sb6b97382a8079b6c@mail.gmail.com>

On Sat, Jan 17, 2009 at 8:38 AM, Rainer M?ller <raimue at macports.org> wrote:
> Doctor Who wrote:
>> I have both aspell and aspell-dict-en installed and both are active.
>> Any reason why no dictionary appears in claws-mail for me?
>
> Do you have the enchant port installed? It seems like claws-mail is
> using this for spell checking. If not, try installing it and rebuild
> claws-mail.
>
> Maybe the dependencies should include enchant, as claws-mail is really
> linking to it if available, but I was unable to track it down using
> trace mode.
>
> Rainer
>

Yes, I should mention that I have enchant installed as well. :-(

Not sure why I can't see the aspell dictionaries I have installed.  Very odd.

What would be the easiest way to totally remove and then re-install
claws-mail?  I tried 'sudo port uninstall claws-mail' , a 'sudo port
clean claws-mail' and a 'sudo port install claws-mail' but still no
dictionaries and my IMAP accounts were still setup when I launched
claws-mail

Thanks.

From liz at panton.me.uk  Sat Jan 17 13:20:32 2009
From: liz at panton.me.uk (Liz Panton)
Date: Sat, 17 Jan 2009 21:20:32 +0000
Subject: MacPorts-1.7.0-10.5-Leopard.dmg.asc or MacPorts-1.7.0-10.5-Leopard.dmg
Message-ID: <d4cfbb5c0901171320m1383547fxc55eb42c8ddf15a4@mail.gmail.com>

I have got as far as the list of downloads, but there are two for Leopard:

MacPorts-1.7.0-10.5-Leopard.dmg.asc<http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0-10.5-Leopard.dmg.asc>

and

MacPorts-1.7.0-10.5-Leopard.dmg.asc<http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0-10.5-Leopard.dmg.asc>

Please could someone tell me how I can tell which one I need to download?

Or, if either would work, what the difference is between the two versions?

Many thanks,

Best wishes,

Lizzie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090117/e3235b94/attachment.html>

From jeremyhu at macports.org  Sat Jan 17 13:42:21 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Sat, 17 Jan 2009 13:42:21 -0800
Subject: MacPorts-1.7.0-10.5-Leopard.dmg.asc or
	MacPorts-1.7.0-10.5-Leopard.dmg
In-Reply-To: <d4cfbb5c0901171320m1383547fxc55eb42c8ddf15a4@mail.gmail.com>
References: <d4cfbb5c0901171320m1383547fxc55eb42c8ddf15a4@mail.gmail.com>
Message-ID: <04E9305E-B5C9-4E53-B876-B91C3A0C2D03@macports.org>

The .asc is a GPG signature to verify your download.  Just grab the dmg.

On Jan 17, 2009, at 13:20, Liz Panton wrote:

> I have got as far as the list of downloads, but there are two for  
> Leopard:
>
> MacPorts-1.7.0-10.5-Leopard.dmg.asc<http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0-10.5-Leopard.dmg.asc 
> >
>
> and
>
> MacPorts-1.7.0-10.5-Leopard.dmg.asc<http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0-10.5-Leopard.dmg.asc 
> >
>
> Please could someone tell me how I can tell which one I need to  
> download?
>
> Or, if either would work, what the difference is between the two  
> versions?
>
> Many thanks,
>
> Best wishes,
>
> Lizzie
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From liz at panton.me.uk  Sat Jan 17 14:06:59 2009
From: liz at panton.me.uk (Liz Panton)
Date: Sat, 17 Jan 2009 22:06:59 +0000
Subject: MacPorts-1.7.0-10.5-Leopard.dmg.asc or
	MacPorts-1.7.0-10.5-Leopard.dmg
In-Reply-To: <04E9305E-B5C9-4E53-B876-B91C3A0C2D03@macports.org>
References: <d4cfbb5c0901171320m1383547fxc55eb42c8ddf15a4@mail.gmail.com>
	<04E9305E-B5C9-4E53-B876-B91C3A0C2D03@macports.org>
Message-ID: <d4cfbb5c0901171406t6d8107c0h1ad18cbea8788d67@mail.gmail.com>

Best wishes,

Liz
Cheers Jeremy :-)

Best wishes,

Liz


2009/1/17 Jeremy Huddleston <jeremyhu at macports.org>

> The .asc is a GPG signature to verify your download.  Just grab the dmg.
>
> On Jan 17, 2009, at 13:20, Liz Panton wrote:
>
>  I have got as far as the list of downloads, but there are two for Leopard:
>>
>> MacPorts-1.7.0-10.5-Leopard.dmg.asc<
>> http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0-10.5-Leopard.dmg.asc
>> >
>>
>> and
>>
>> MacPorts-1.7.0-10.5-Leopard.dmg.asc<
>> http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0-10.5-Leopard.dmg.asc
>> >
>>
>> Please could someone tell me how I can tell which one I need to download?
>>
>> Or, if either would work, what the difference is between the two versions?
>>
>> Many thanks,
>>
>> Best wishes,
>>
>> Lizzie
>> _______________________________________________
>> 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/20090117/dc85eab0/attachment.html>

From HerrPoetry at HailMail.net  Sat Jan 17 19:33:53 2009
From: HerrPoetry at HailMail.net (Mark)
Date: Sat, 17 Jan 2009 22:33:53 -0500
Subject: GnuCash Default Font
In-Reply-To: <F0B8959F-9137-4047-A00E-3C3797944EC5@jrcarter.com>
References: <497181E8.5070606@HailMail.net>
	<F0B8959F-9137-4047-A00E-3C3797944EC5@jrcarter.com>
Message-ID: <4972A321.70807@HailMail.net>

John R. Carter, Sr. wrote:
> On a Mac:
>
> $ sudo nano -w `which startx`
>
> (Use back quotes in the above.)
> Change the first occurrence of defaultserverargs to read as follows:
>
> defaultserverargs=?-dpi 96?
>
> You will have to restart X11 if it is already active.
>
> All this does is ensure that the X11 display resolution is the same as 
> the default system font.
>
> On Jan 16, 2009, at 11:59 PM, Mark wrote:
>
>> (I just posted on a related GnuCash topic, so please forgive the
>> repetition of my system details.) I have just finished a complete fresh
>> install of Macports, followed by a native Quartz, minimal (+without_hbci
>> +without_ofx +without_quotes) install of GnuCash on MBP 10.5.6.
>>
>> I can't figure out how to change the default font for the program. When
>> I used to run GnuCash under X11 (Fink package GnuCash2), I had -- and
>> still have -- a file in my home directory named .gtkrc-2.0 which
>> contains a single line: gtk-font-name = "Luxi Mono 16" -- and that used
>> to cause GnuCash to use that font in all its windows.
>>
>> But not anymore! Apparently native Quartz GnuCash installed via MacPorts
>> isn't consulting ~/gtkrc-2.0, or is somehow overriding it? Anything I
>> can do to get my big beautiful font back?
>>
>> - Mark

I made the proposed edit, but to no avail. I'm not running GnuCash in 
X11, but natively using Quartz, using the MacPorts installation 
<http://wiki.gnucash.org/wiki/MacOSX/MacPortsDetail#Using_MacPorts_to_install_the_native_Quartz_version_of_GnuCash>. 
There's gotta be a way to modify the installation -- even if I have to 
add more Gnome components -- to change the font GnuCash uses. I just 
don't have the Unix chops to figure it out.

- Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090117/c7adc88f/attachment.html>

From brad at pixilla.com  Sat Jan 17 19:57:52 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Sat, 17 Jan 2009 19:57:52 -0800
Subject: GnuCash Default Font
In-Reply-To: <4972A321.70807@HailMail.net>
References: <497181E8.5070606@HailMail.net>
	<F0B8959F-9137-4047-A00E-3C3797944EC5@jrcarter.com>
	<4972A321.70807@HailMail.net>
Message-ID: <822C2BDF-E94B-47FB-8527-142BCB8CF4D4@pixilla.com>


On Jan 17, 2009, at 7:33 PM, Mark wrote:

> John R. Carter, Sr. wrote:
>>
>> On a Mac:
>>
>> $ sudo nano -w `which startx`
>>
>> (Use back quotes in the above.)
>> Change the first occurrence of defaultserverargs to read as follows:
>>
>> defaultserverargs=?-dpi 96?
>>
>> You will have to restart X11 if it is already active.
>>
>> All this does is ensure that the X11 display resolution is the same  
>> as the default system font.
>>
>> On Jan 16, 2009, at 11:59 PM, Mark wrote:
>>
>>> (I just posted on a related GnuCash topic, so please forgive the
>>> repetition of my system details.) I have just finished a complete  
>>> fresh
>>> install of Macports, followed by a native Quartz, minimal  
>>> (+without_hbci
>>> +without_ofx +without_quotes) install of GnuCash on MBP 10.5.6.
>>>
>>> I can't figure out how to change the default font for the program.  
>>> When
>>> I used to run GnuCash under X11 (Fink package GnuCash2), I had --  
>>> and
>>> still have -- a file in my home directory named .gtkrc-2.0 which
>>> contains a single line: gtk-font-name = "Luxi Mono 16" -- and that  
>>> used
>>> to cause GnuCash to use that font in all its windows.
>>>
>>> But not anymore! Apparently native Quartz GnuCash installed via  
>>> MacPorts
>>> isn't consulting ~/gtkrc-2.0, or is somehow overriding it?  
>>> Anything I
>>> can do to get my big beautiful font back?

How do you build the Quartz version?
I see no Quartz variant.


From HerrPoetry at HailMail.net  Sat Jan 17 22:15:49 2009
From: HerrPoetry at HailMail.net (Mark)
Date: Sun, 18 Jan 2009 01:15:49 -0500
Subject: GnuCash Default Font
In-Reply-To: <822C2BDF-E94B-47FB-8527-142BCB8CF4D4@pixilla.com>
References: <497181E8.5070606@HailMail.net>	<F0B8959F-9137-4047-A00E-3C3797944EC5@jrcarter.com>	<4972A321.70807@HailMail.net>
	<822C2BDF-E94B-47FB-8527-142BCB8CF4D4@pixilla.com>
Message-ID: <4972C915.7020404@HailMail.net>

Bradley Giesbrecht wrote:
>> native Quartz GnuCash installed via MacPorts . . .
>
> How do you build the Quartz version?
> I see no Quartz variant. 

There are two methods. Here are the links:

http://wiki.gnucash.org/wiki/MacOSX/MacPortsDetail#Using_MacPorts_to_install_the_native_Quartz_version_of_GnuCash

http://wiki.gnucash.org/wiki/MacOSX/Quartz

I first tried the second of these, without MacPorts, but I couldn't get 
it to work -- got stuck in the libgnomeprint installation. So I deleted 
that failed installation and tried a fresh install of MacPorts and the 
first of the above links, and it works: no X11. With a little help from 
David T., I wrote a one-line Applescript app to be able to launch 
GnuCash directly from the Dock:

do shell script "source /sw/bin/init.sh ; /opt/local/bin/gnucash >& 
/dev/null & ; echo"

I haven't tested this native GnuCash yet; I've been trying to tweak the 
installation, including the default font:

> I can't figure out how to change the default font for the program. 
> When I used to run GnuCash under X11 (Fink package GnuCash2), I had -- 
> and still have -- a file in my home directory named .gtkrc-2.0 which 
> contains a single line: gtk-font-name = "Luxi Mono 16" -- and that 
> used to cause GnuCash to use that font in all its windows.
>
> But not anymore! Apparently native Quartz GnuCash installed via 
> MacPorts isn't consulting ~/gtkrc-2.0, or is somehow overriding it? 
> Anything I can do to get my big beautiful font back?

Any ideas?

- Mark

From olaf at foellinger.de  Sun Jan 18 03:01:54 2009
From: olaf at foellinger.de (Olaf Foellinger)
Date: Sun, 18 Jan 2009 12:01:54 +0100
Subject: GnuCash Default Font
In-Reply-To: <822C2BDF-E94B-47FB-8527-142BCB8CF4D4@pixilla.com>
References: <497181E8.5070606@HailMail.net>
	<F0B8959F-9137-4047-A00E-3C3797944EC5@jrcarter.com>
	<4972A321.70807@HailMail.net>
	<822C2BDF-E94B-47FB-8527-142BCB8CF4D4@pixilla.com>
Message-ID: <20090118110154.GA646@foellinger.de>

* Bradley Giesbrecht <brad at pixilla.com> [18.01.09 04:58]wrote:

>
> On Jan 17, 2009, at 7:33 PM, Mark wrote:
>
>> John R. Carter, Sr. wrote:
>>>
>>> On a Mac:
>>>
>>> $ sudo nano -w `which startx`
>>>
>>> (Use back quotes in the above.)
>>> Change the first occurrence of defaultserverargs to read as follows:
>>>
>>> defaultserverargs=?-dpi 96?
>>>
>>> You will have to restart X11 if it is already active.
>>>
>>> All this does is ensure that the X11 display resolution is the same  
>>> as the default system font.
>>>
>>> On Jan 16, 2009, at 11:59 PM, Mark wrote:
>>>
>>>> (I just posted on a related GnuCash topic, so please forgive the
>>>> repetition of my system details.) I have just finished a complete  
>>>> fresh
>>>> install of Macports, followed by a native Quartz, minimal  
>>>> (+without_hbci
>>>> +without_ofx +without_quotes) install of GnuCash on MBP 10.5.6.
>>>>
>>>> I can't figure out how to change the default font for the program.  
>>>> When
>>>> I used to run GnuCash under X11 (Fink package GnuCash2), I had --  
>>>> and
>>>> still have -- a file in my home directory named .gtkrc-2.0 which
>>>> contains a single line: gtk-font-name = "Luxi Mono 16" -- and that  
>>>> used
>>>> to cause GnuCash to use that font in all its windows.
>>>>
>>>> But not anymore! Apparently native Quartz GnuCash installed via  
>>>> MacPorts
>>>> isn't consulting ~/gtkrc-2.0, or is somehow overriding it?  
>>>> Anything I
>>>> can do to get my big beautiful font back?
>
> How do you build the Quartz version?
> I see no Quartz variant.


Sorry, only in German:
http://blog.foellinger.de/2009/01/04/gnucash-fur-mac-os-x-mit-quartz-oberflache-stark-vereinfacht/

Gru? Olaf

From hirshj at att.net  Sun Jan 18 13:13:23 2009
From: hirshj at att.net (Jason Hirsh)
Date: Sun, 18 Jan 2009 17:13:23 -0400
Subject: error apache2 from macports 1.70
Message-ID: <398AFC69-FD3F-4A96-827F-D792B4EB7036@att.net>

I am trying to install Apache 2.0 on a Power Mac G5 running Leopard  
10.5.4
I get  the folowing error

--->  Fetching apache2
--->  Attempting to fetch httpd-2.2.11.tar.bz2 from http://www.ibiblio.org/pub/mirrors/apache/httpd
--->  Verifying checksum(s) for apache2
--->  Extracting apache2
Error: reinplace: couldn't read file "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_apache2/work/httpd-2.2.11/configure":  
no such file or directory
Error: Target org.macports.extract returned: reinplace sed(1) failed
Error: Status 1 encountered during processing.


It would seem there is an issue with the what I fetched??




From blb at macports.org  Sun Jan 18 13:29:18 2009
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 18 Jan 2009 14:29:18 -0700
Subject: error apache2 from macports 1.70
In-Reply-To: <398AFC69-FD3F-4A96-827F-D792B4EB7036@att.net>
References: <398AFC69-FD3F-4A96-827F-D792B4EB7036@att.net>
Message-ID: <20090118212918.GC741@ninagal.withay.com>

On Sun, Jan 18, 2009 at 05:13:23PM -0400, Jason Hirsh said:
> I am trying to install Apache 2.0 on a Power Mac G5 running Leopard  
> 10.5.4
> I get  the folowing error
>
> --->  Fetching apache2
> --->  Attempting to fetch httpd-2.2.11.tar.bz2 from http://www.ibiblio.org/pub/mirrors/apache/httpd
> --->  Verifying checksum(s) for apache2
> --->  Extracting apache2
> Error: reinplace: couldn't read file "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_www_apache2/work/httpd-2.2.11/configure": no 
> such file or directory
> Error: Target org.macports.extract returned: reinplace sed(1) failed
> Error: Status 1 encountered during processing.
>
>
> It would seem there is an issue with the what I fetched??

If the file downloaded wasn't right, it would have failed during the
checksum, so the download should be okay.  Try running

$ sudo port clean --work apache2
$ sudo port -d extract apache2

and see if that gives us some more information on what's going on.  FWIW, I
have that version of apache2 installed here without such issues.

Bryan


From hirshj at att.net  Sun Jan 18 15:12:45 2009
From: hirshj at att.net (Jason Hirsh)
Date: Sun, 18 Jan 2009 19:12:45 -0400
Subject: Fwd: error apache2 from macports 1.70
References: <E5726279-A56F-4F78-9EA1-98BCC7CD21EC@att.net>
Message-ID: <362B5877-C1F4-429A-8E9B-1C78BEF72995@att.net>



Begin forwarded message:

> From: Jason Hirsh <hirshj at att.net>
> Date: January 18, 2009 5:59:06 PM GMT-04:00
> To: Bryan Blackburn <blb at macports.org>
> Subject: Re: error apache2 from macports 1.70
>
>
> On Jan 18, 2009, at 5:29 PM, Bryan Blackburn wrote:
>
>> On Sun, Jan 18, 2009 at 05:13:23PM -0400, Jason Hirsh said:
>>> I am trying to install Apache 2.0 on a Power Mac G5 running Leopard
>>> 10.5.4
>>> I get  the folowing error
>>>
>>> --->  Fetching apache2
>>> --->  Attempting to fetch httpd-2.2.11.tar.bz2 from http://www.ibiblio.org/pub/mirrors/apache/httpd
>>> --->  Verifying checksum(s) for apache2
>>> --->  Extracting apache2
>>> Error: reinplace: couldn't read file "/opt/local/var/macports/build/
>>> _opt_local_var_macports_sources_rsync
>>> .macports.org_release_ports_www_apache2/work/httpd-2.2.11/ 
>>> configure": no
>>> such file or directory
>>> Error: Target org.macports.extract returned: reinplace sed(1) failed
>>> Error: Status 1 encountered during processing.
>>>
>>>
>>> It would seem there is an issue with the what I fetched??
>>
>> If the file downloaded wasn't right, it would have failed during the
>> checksum, so the download should be okay.  Try running
>>
>> $ sudo port clean --work apache2
>> $ sudo port -d extract apache2
>>
>> and see if that gives us some more information on what's going on.   
>> FWIW, I
>> have that version of apache2 installed here without such issues.
>>
>> Bryan
>
> Ok ther still seems to be an issue with that configure directory not  
> being created
> I took a llok and I have nothing in the tree under work in the path  
> shown in the error
>
> [Bluefish:/opt/local] jason% sudo port -d extract apache2
> DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/www/apache2
> DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
> rsync.macports.org/release/ports/www/apache2
> 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 apache2.
> DEBUG: Requested variant macosx is not provided by port apache2.
> DEBUG: Executing variant darwin provides darwin
> DEBUG: Executing variant darwin_9 provides darwin_9
> DEBUG: Executing org.macports.main (apache2)
> --->  Fetching apache2
> DEBUG: Executing org.macports.fetch (apache2)
> --->  Verifying checksum(s) for apache2
> DEBUG: Executing org.macports.checksum (apache2)
> --->  Checksumming httpd-2.2.11.tar.bz2
> DEBUG: Correct (md5) checksum for httpd-2.2.11.tar.bz2
> DEBUG: Correct (sha1) checksum for httpd-2.2.11.tar.bz2
> DEBUG: Correct (rmd160) checksum for httpd-2.2.11.tar.bz2
> DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
> --->  Extracting apache2
> DEBUG: Executing org.macports.extract (apache2)
> --->  Extracting httpd-2.2.11.tar.bz2
> DEBUG: setting option extract.args to /opt/local/var/macports/ 
> distfiles/apache2/httpd-2.2.11.tar.bz2
> 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_www_apache2/work" && /opt/local/bin/ 
> bzip2 -dc /opt/local/var/macports/distfiles/apache2/ 
> httpd-2.2.11.tar.bz2 | /usr/bin/gnutar --no-same-owner -xf -'
> sh: /opt/local/bin/bzip2: Bad CPU type in executable
> DEBUG: Executing proc-post-org.macports.extract-extract-0
> DEBUG: couldn't read file "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_www_apache2/work/httpd-2.2.11/ 
> configure": no such file or directory
>    while executing
> "exec /usr/bin/sed {s|-export-symbols-regex ssl_module||g} < /opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_p..."
>    ("eval" body line 1)
>    invoked from within
> "eval exec $cmdline"
> Error: reinplace: couldn't read file "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_www_apache2/work/httpd-2.2.11/ 
> configure": no such file or directory
> Error: Target org.macports.extract returned: reinplace sed(1) failed
> Warning: the following items did not execute (for apache2):  
> org.macports.extract
> Error: Status 1 encountered during processing.
>
>
> Its probably me... but can't figure how I screwed up
>
>>
>>
>> _______________________________________________
>> 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/20090118/f201890d/attachment.html>

From whodoctor at gmail.com  Sun Jan 18 15:30:53 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Sun, 18 Jan 2009 18:30:53 -0500
Subject: Error after trying to upgrade installed
Message-ID: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>

I have MacPorts 1.7.0 installed.  I did a 'sudo port outdated' and had
5 or 6 ports that needed updating.  I then ran a 'sudo port upgrade
outdated' and it failed after a while with errors like:

sudo port upgrade outdated
--->  Deactivating gettext @0.17_3
Error: Deactivating gettext 0.17_3 failed:
--->  Activating perl5.8 @5.8.9_2
Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/touch
  Reason: image not found
--->  Deactivating gettext @0.17_3
Error: Deactivating gettext 0.17_3 failed:
Error: Unable to upgrade port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to upgrade port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to upgrade port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to upgrade port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
--->  Deactivating gettext @0.17_3
Error: Deactivating gettext 0.17_3 failed:
--->  Activating perl5.8 @5.8.9_2
Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/touch
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to upgrade port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found

What is the issue here and how can I fix?  Any command I now run from
Terminal.app gives an error such as:

$ ls
dyld: Library not loaded: /opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ls
  Reason: image not found
Trace/BPT trap

$ uptime
dyld: Library not loaded: /opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/uptime
  Reason: image not found
Trace/BPT trap

Thanks for any help!

From ohce86 at kitcarson.net  Sun Jan 18 15:41:17 2009
From: ohce86 at kitcarson.net (Timothy Goins)
Date: Sun, 18 Jan 2009 16:41:17 -0700
Subject: error apache2 from macports 1.70
In-Reply-To: <362B5877-C1F4-429A-8E9B-1C78BEF72995@att.net>
References: <E5726279-A56F-4F78-9EA1-98BCC7CD21EC@att.net>
	<362B5877-C1F4-429A-8E9B-1C78BEF72995@att.net>
Message-ID: <89993DDD-F3DA-4602-AF36-4EBC5E3BE46D@kitcarson.net>

Here's what I got when I installed Apache2.0 on my Mac Pro running  
10.5.6 (being a dodo, I am wondering why my port command fetched from http://distfiles.macports.org/apache2 
  rather than from http://www.ibiblio.org/pub/mirrors/apache/httpd):

tim at cotopaxi:~$ sudo port install apache2
Password:
--->  Fetching apr
--->  Attempting to fetch apr-1.3.3.tar.bz2 from http://distfiles.macports.org/apr
--->  Verifying checksum(s) for apr
--->  Extracting apr
--->  Configuring apr
--->  Building apr
--->  Staging apr into destroot
--->  Installing apr @1.3.3_1
--->  Activating apr @1.3.3_1
--->  Cleaning apr
--->  Fetching apr-util
--->  Attempting to fetch apr-util-1.3.4.tar.bz2 from http://distfiles.macports.org/apr-util
--->  Verifying checksum(s) for apr-util
--->  Extracting apr-util
--->  Configuring apr-util
--->  Building apr-util
--->  Staging apr-util into destroot
--->  Installing apr-util @1.3.4_1
--->  Activating apr-util @1.3.4_1
--->  Cleaning apr-util
--->  Fetching apache2
--->  Attempting to fetch httpd-2.2.11.tar.bz2 from http://distfiles.macports.org/apache2
--->  Verifying checksum(s) for apache2
--->  Extracting apache2
--->  Applying patches to apache2
--->  Configuring apache2
--->  Building apache2
--->  Staging apache2 into destroot
--->  Creating launchd control script
###########################################################
# A startup item has been generated that will aid in
# starting apache2 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.apache2.plist
###########################################################
Warning: apache2 requests to install files outside the common  
directory structure!
--->  Installing apache2 @2.2.11_0+darwin_9
--->  Activating apache2 @2.2.11_0+darwin_9
--->  Cleaning apache2

Tim

On Jan 18, 2009, at 4:12 PM, Jason Hirsh wrote:

>
>
> Begin forwarded message:
>
>> From: Jason Hirsh <hirshj at att.net>
>> Date: January 18, 2009 5:59:06 PM GMT-04:00
>> To: Bryan Blackburn <blb at macports.org>
>> Subject: Re: error apache2 from macports 1.70
>>
>>
>> On Jan 18, 2009, at 5:29 PM, Bryan Blackburn wrote:
>>
>>> On Sun, Jan 18, 2009 at 05:13:23PM -0400, Jason Hirsh said:
>>>> I am trying to install Apache 2.0 on a Power Mac G5 running Leopard
>>>> 10.5.4
>>>> I get  the folowing error
>>>>
>>>> --->  Fetching apache2
>>>> --->  Attempting to fetch httpd-2.2.11.tar.bz2 from http://www.ibiblio.org/pub/mirrors/apache/httpd
>>>> --->  Verifying checksum(s) for apache2
>>>> --->  Extracting apache2
>>>> Error: reinplace: couldn't read file "/opt/local/var/macports/ 
>>>> build/
>>>> _opt_local_var_macports_sources_rsync
>>>> .macports.org_release_ports_www_apache2/work/httpd-2.2.11/ 
>>>> configure": no
>>>> such file or directory
>>>> Error: Target org.macports.extract returned: reinplace sed(1)  
>>>> failed
>>>> Error: Status 1 encountered during processing.
>>>>
>>>>
>>>> It would seem there is an issue with the what I fetched??
>>>
>>> If the file downloaded wasn't right, it would have failed during the
>>> checksum, so the download should be okay.  Try running
>>>
>>> $ sudo port clean --work apache2
>>> $ sudo port -d extract apache2
>>>
>>> and see if that gives us some more information on what's going  
>>> on.  FWIW, I
>>> have that version of apache2 installed here without such issues.
>>>
>>> Bryan
>>
>> Ok ther still seems to be an issue with that configure directory  
>> not being created
>> I took a llok and I have nothing in the tree under work in the path  
>> shown in the error
>>
>> [Bluefish:/opt/local] jason% sudo port -d extract apache2
>> DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/www/apache2
>> DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
>> rsync.macports.org/release/ports/www/apache2
>> 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 apache2.
>> DEBUG: Requested variant macosx is not provided by port apache2.
>> DEBUG: Executing variant darwin provides darwin
>> DEBUG: Executing variant darwin_9 provides darwin_9
>> DEBUG: Executing org.macports.main (apache2)
>> --->  Fetching apache2
>> DEBUG: Executing org.macports.fetch (apache2)
>> --->  Verifying checksum(s) for apache2
>> DEBUG: Executing org.macports.checksum (apache2)
>> --->  Checksumming httpd-2.2.11.tar.bz2
>> DEBUG: Correct (md5) checksum for httpd-2.2.11.tar.bz2
>> DEBUG: Correct (sha1) checksum for httpd-2.2.11.tar.bz2
>> DEBUG: Correct (rmd160) checksum for httpd-2.2.11.tar.bz2
>> DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
>> --->  Extracting apache2
>> DEBUG: Executing org.macports.extract (apache2)
>> --->  Extracting httpd-2.2.11.tar.bz2
>> DEBUG: setting option extract.args to /opt/local/var/macports/ 
>> distfiles/apache2/httpd-2.2.11.tar.bz2
>> 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_www_apache2/work" && /opt/local/bin/ 
>> bzip2 -dc /opt/local/var/macports/distfiles/apache2/ 
>> httpd-2.2.11.tar.bz2 | /usr/bin/gnutar --no-same-owner -xf -'
>> sh: /opt/local/bin/bzip2: Bad CPU type in executable
>> DEBUG: Executing proc-post-org.macports.extract-extract-0
>> DEBUG: couldn't read file "/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_www_apache2/work/httpd-2.2.11/ 
>> configure": no such file or directory
>>    while executing
>> "exec /usr/bin/sed {s|-export-symbols-regex ssl_module||g} < /opt/ 
>> local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync.macports.org_release_p..."
>>    ("eval" body line 1)
>>    invoked from within
>> "eval exec $cmdline"
>> Error: reinplace: couldn't read file "/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_www_apache2/work/httpd-2.2.11/ 
>> configure": no such file or directory
>> Error: Target org.macports.extract returned: reinplace sed(1) failed
>> Warning: the following items did not execute (for apache2):  
>> org.macports.extract
>> Error: Status 1 encountered during processing.
>>
>>
>> Its probably me... but can't figure how I screwed up
>>
>>>
>>>
>>> _______________________________________________
>>> 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/20090118/a70db90e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2116 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090118/a70db90e/attachment.bin>

From raimue at macports.org  Sun Jan 18 15:46:45 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Mon, 19 Jan 2009 00:46:45 +0100
Subject: Error after trying to upgrade installed
In-Reply-To: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
Message-ID: <4973BF65.7050700@macports.org>

Doctor Who wrote:
> I have MacPorts 1.7.0 installed.  I did a 'sudo port outdated' and had
> 5 or 6 ports that needed updating.  I then ran a 'sudo port upgrade
> outdated' and it failed after a while with errors like:
> 
> sudo port upgrade outdated
> --->  Deactivating gettext @0.17_3
> Error: Deactivating gettext 0.17_3 failed:
> --->  Activating perl5.8 @5.8.9_2
> Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/touch
>   Reason: image not found
> --->  Deactivating gettext @0.17_3
> Error: Deactivating gettext 0.17_3 failed:
> Error: Unable to upgrade port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> Error: Unable to exec port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> Error: Unable to upgrade port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> Error: Unable to exec port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> Error: Unable to exec port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> Error: Unable to exec port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> Error: Unable to exec port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> Error: Unable to exec port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> Error: Unable to exec port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> Error: Unable to exec port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> Error: Unable to upgrade port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> Error: Unable to upgrade port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> --->  Deactivating gettext @0.17_3
> Error: Deactivating gettext 0.17_3 failed:
> --->  Activating perl5.8 @5.8.9_2
> Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/touch
>   Reason: image not found
> Error: Unable to exec port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found
> Error: Unable to upgrade port: dyld: Library not loaded:
> /opt/local/lib/libintl.8.dylib
>   Referenced from: /opt/local/bin/ln
>   Reason: image not found

Looks like you have coreutils +with_default_names installed, but you
broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
some reason it seems not to be active.

Try to fix it by
  sudo port activate gettext

Rainer

From talklists at newgeo.com  Sun Jan 18 15:47:23 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Sun, 18 Jan 2009 15:47:23 -0800
Subject: ASSP out of date
In-Reply-To: <20081112025226.GM596@ninagal.withay.com>
References: <33DB3AA3-3AB2-408F-9CEC-07AFBD55E857@newgeo.com>
	<188585BA-078E-4D06-9930-7DAE321B1901@macports.org>
	<D95268B0-57B6-43A7-A5A8-801667CE078B@newgeo.com>
	<864EDFE1-9031-457F-831C-1C560219B380@macports.org>
	<323629E3-14C3-42CE-8EA8-B34EC785C059@newgeo.com>
	<20081111095733.GY747@ninagal.withay.com>
	<DF7AF73D-5A61-44CB-807B-5B044F663F4E@macports.org>
	<9A5136AD-CAAB-44B1-9BEB-DA6CDAD36558@newgeo.com>
	<5F4F8D22-03BC-4670-98F5-A48FD07D17A4@macports.org>
	<3B673105-B884-4954-87E4-435F73A2C25E@newgeo.com>
	<20081112025226.GM596@ninagal.withay.com>
Message-ID: <51069ED4-F375-4B26-8DC2-974504DA2F26@newgeo.com>

Hello, I am back on this again.  Had to get a new computer.  I  
remember I used to do `edit port ASSP` and it would open a file, that  
I had done some work on.  I have MacPorts installed on my new machine  
now, but how do I get the old edited port over to my new machine, so I  
can work where I left off?

I also want to rename it, so I can `edit port ASSP-new` or whatever,  
and not conflict with the current port for the time being.

Thank you.
--
Scott


From whodoctor at gmail.com  Sun Jan 18 15:48:42 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Sun, 18 Jan 2009 18:48:42 -0500
Subject: Error after trying to upgrade installed
In-Reply-To: <4973BF65.7050700@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
Message-ID: <4b75340e0901181548s45dacc4bveeee8d391a0096fa@mail.gmail.com>

On Sun, Jan 18, 2009 at 6:46 PM, Rainer M?ller <raimue at macports.org> wrote:
> Doctor Who wrote:
>> I have MacPorts 1.7.0 installed.  I did a 'sudo port outdated' and had
>> 5 or 6 ports that needed updating.  I then ran a 'sudo port upgrade
>> outdated' and it failed after a while with errors like:
>>
>> sudo port upgrade outdated
>> --->  Deactivating gettext @0.17_3
>> Error: Deactivating gettext 0.17_3 failed:
>> --->  Activating perl5.8 @5.8.9_2
>> Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/touch
>>   Reason: image not found
>> --->  Deactivating gettext @0.17_3
>> Error: Deactivating gettext 0.17_3 failed:
>> Error: Unable to upgrade port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> Error: Unable to exec port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> Error: Unable to upgrade port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> Error: Unable to exec port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> Error: Unable to exec port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> Error: Unable to exec port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> Error: Unable to exec port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> Error: Unable to exec port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> Error: Unable to exec port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> Error: Unable to exec port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> Error: Unable to upgrade port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> Error: Unable to upgrade port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> --->  Deactivating gettext @0.17_3
>> Error: Deactivating gettext 0.17_3 failed:
>> --->  Activating perl5.8 @5.8.9_2
>> Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/touch
>>   Reason: image not found
>> Error: Unable to exec port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>> Error: Unable to upgrade port: dyld: Library not loaded:
>> /opt/local/lib/libintl.8.dylib
>>   Referenced from: /opt/local/bin/ln
>>   Reason: image not found
>
> Looks like you have coreutils +with_default_names installed, but you
> broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
> some reason it seems not to be active.
>
> Try to fix it by
>  sudo port activate gettext
>
> Rainer
>

sudo port activate gettext
Password:
--->  Activating gettext
Error: port activate failed: Image error: gettext @0.17_3 is already active.

From blb at macports.org  Sun Jan 18 15:54:53 2009
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 18 Jan 2009 16:54:53 -0700
Subject: Fwd: error apache2 from macports 1.70
In-Reply-To: <362B5877-C1F4-429A-8E9B-1C78BEF72995@att.net>
References: <E5726279-A56F-4F78-9EA1-98BCC7CD21EC@att.net>
	<362B5877-C1F4-429A-8E9B-1C78BEF72995@att.net>
Message-ID: <20090118235453.GD741@ninagal.withay.com>

On Sun, Jan 18, 2009 at 07:12:45PM -0400, Jason Hirsh said:
[...]
>>
>> Ok ther still seems to be an issue with that configure directory not  
>> being created
>> I took a llok and I have nothing in the tree under work in the path  
>> shown in the error
>>
>> [Bluefish:/opt/local] jason% sudo port -d extract apache2
[...]
>> DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
>> --->  Extracting apache2
>> DEBUG: Executing org.macports.extract (apache2)
>> --->  Extracting httpd-2.2.11.tar.bz2
>> DEBUG: setting option extract.args to /opt/local/var/macports/ 
>> distfiles/apache2/httpd-2.2.11.tar.bz2
>> 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_www_apache2/work" && /opt/local/bin/bzip2 
>> -dc /opt/local/var/macports/distfiles/apache2/httpd-2.2.11.tar.bz2 | 
>> /usr/bin/gnutar --no-same-owner -xf -'
>> sh: /opt/local/bin/bzip2: Bad CPU type in executable

Was this MacPorts install copied over from a different architecture (eg from
a PowerPC to Intel)?

Odd though that it continued on after that as it should have failed at this
point instead of continuing.

Bryan

[...]

From blb at macports.org  Sun Jan 18 15:58:37 2009
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 18 Jan 2009 16:58:37 -0700
Subject: Error after trying to upgrade installed
In-Reply-To: <4973BF65.7050700@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
Message-ID: <20090118235837.GE741@ninagal.withay.com>

On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer M?ller said:
> Doctor Who wrote:
> > I have MacPorts 1.7.0 installed.  I did a 'sudo port outdated' and had
> > 5 or 6 ports that needed updating.  I then ran a 'sudo port upgrade
> > outdated' and it failed after a while with errors like:
> > 
> > sudo port upgrade outdated
> > --->  Deactivating gettext @0.17_3
> > Error: Deactivating gettext 0.17_3 failed:
> > --->  Activating perl5.8 @5.8.9_2
[...]
> 
> Looks like you have coreutils +with_default_names installed, but you
> broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
> some reason it seems not to be active.

Somebody reported this same issue last night on IRC, where it fails to
deactivate gettext but not giving any actual error message.  It ends up
removing all files from ${prefix} but then fails to set the port as not
active, and ends up confused.

You can't force-activate as it complains that it is already active, and any
further deactivate results in the same output above.

Unfortunately I didn't see any way to deal with this or what the cause was,
and was hoping it was a one-off issue.  This is two now this weekend, so
maybe something strange is going on in base...

Bryan


> 
> Try to fix it by
>   sudo port activate gettext
> 
> Rainer

From brad at pixilla.com  Sun Jan 18 16:02:39 2009
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Sun, 18 Jan 2009 16:02:39 -0800
Subject: ASSP out of date
In-Reply-To: <51069ED4-F375-4B26-8DC2-974504DA2F26@newgeo.com>
References: <33DB3AA3-3AB2-408F-9CEC-07AFBD55E857@newgeo.com>
	<188585BA-078E-4D06-9930-7DAE321B1901@macports.org>
	<D95268B0-57B6-43A7-A5A8-801667CE078B@newgeo.com>
	<864EDFE1-9031-457F-831C-1C560219B380@macports.org>
	<323629E3-14C3-42CE-8EA8-B34EC785C059@newgeo.com>
	<20081111095733.GY747@ninagal.withay.com>
	<DF7AF73D-5A61-44CB-807B-5B044F663F4E@macports.org>
	<9A5136AD-CAAB-44B1-9BEB-DA6CDAD36558@newgeo.com>
	<5F4F8D22-03BC-4670-98F5-A48FD07D17A4@macports.org>
	<3B673105-B884-4954-87E4-435F73A2C25E@newgeo.com>
	<20081112025226.GM596@ninagal.withay.com>
	<51069ED4-F375-4B26-8DC2-974504DA2F26@newgeo.com>
Message-ID: <693C4C90-970D-4B53-A52A-07288AC7365B@pixilla.com>

On Jan 18, 2009, at 3:47 PM, Scott Haneda wrote:

> Hello, I am back on this again.  Had to get a new computer.  I  
> remember I used to do `edit port ASSP` and it would open a file,  
> that I had done some work on.  I have MacPorts installed on my new  
> machine now, but how do I get the old edited port over to my new  
> machine, so I can work where I left off?

There are so many ways to get a file from one machine to another. You  
must mean something else.

If it's a Mac you want to copy the file from on Leopard you should be  
able to see the machine in a Finder window in the sidebar under  
"SHARED".
Just click the computer name and "Connect As" and type in your  
credentials when prompted.
Then find your Portfile and copy it over.

If you are just looking for your port file.

port dir <port name>


> I also want to rename it, so I can `edit port ASSP-new` or whatever,  
> and not conflict with the current port for the time being.


This is what I do.

http://guide.macports.org/#development.local-repositories

From mark at dxradio.demon.co.uk  Sun Jan 18 16:06:38 2009
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Mon, 19 Jan 2009 00:06:38 +0000
Subject: upgrading VIM errors
Message-ID: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>

Did a selfupdate on Macports 1.7 running on OSX 10.5.6, then a port  
outdated ...

iMac:~ mark$ sudo port outdated
The following installed ports are outdated:
vim                            7.2.077_0 < 7.2.077_1


iMac:~ mark$ sudo port upgrade outdated
--->  Fetching vim
--->  Verifying checksum(s) for vim
--->  Extracting vim
--->  Applying patches to vim
--->  Configuring vim
--->  Building vim
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_editors_vim/work/vim72" && make all "  
returned error 2
Command output: /usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/ 
opt/local/include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/ 
FlatCarbon  -O -D_FORTIFY_SOURCE=1         -o objects/quickfix.o  
quickfix.c
/usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/include  
-DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/FlatCarbon  -O - 
D_FORTIFY_SOURCE=1         -o objects/regexp.o regexp.c

[lots more of these FORTIFY_SOURCE lines ending with ...]

/usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/include  
-DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/FlatCarbon  -O - 
D_FORTIFY_SOURCE=1         version.c -o objects/version.o
   /usr/bin/gcc-4.0   -L/opt/local/lib 	-o vim objects/buffer.o  
objects/charset.o objects/diff.o objects/digraph.o objects/edit.o  
objects/eval.o objects/ex_cmds.o objects/ex_cmds2.o objects/ex_docmd.o  
objects/ex_eval.o objects/ex_getln.o objects/fileio.o objects/fold.o  
objects/getchar.o objects/hardcopy.o objects/hashtab.o  objects/ 
if_cscope.o objects/if_xcmdsrv.o objects/main.o objects/mark.o objects/ 
memfile.o objects/memline.o objects/menu.o objects/message.o objects/ 
misc1.o objects/misc2.o objects/move.o objects/mbyte.o objects/ 
normal.o objects/ops.o objects/option.o objects/os_unix.o objects/ 
pathdef.o objects/popupmnu.o objects/quickfix.o objects/regexp.o  
objects/screen.o objects/search.o objects/spell.o objects/syntax.o   
objects/tag.o objects/term.o objects/ui.o objects/undo.o objects/ 
window.o       objects/os_macosx.o objects/os_mac_conv.o  objects/ 
netbeans.o  objects/version.o       -lm  -lncurses -liconv -framework  
Carbon
Undefined symbols:
   "__Xsetlocale", referenced from:
       _get_locale_val in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _main in main.o
       _main in main.o
       _enc_locale in mbyte.o
       _mac_lang_init in os_mac_conv.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[1]: *** [vim] Error 1
make: *** [all] Error 2

Error: Unable to upgrade port: 1


Previous updates to VIM have worked OK.

iMac:~ mark$ sudo port installed | grep vim
   vim @7.2.077_0 (active)


Previously today, gd2 was updated
--->  Deactivating gd2 @2.0.35_2
--->  Installing gd2 @2.0.35_3

whose upgrade process downloaded, built, installed and activated 70  
(seventy) xorg- packages ...


Mark


From blb at macports.org  Sun Jan 18 16:20:25 2009
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 18 Jan 2009 17:20:25 -0700
Subject: upgrading VIM errors
In-Reply-To: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
Message-ID: <20090119002025.GF741@ninagal.withay.com>

On Mon, Jan 19, 2009 at 12:06:38AM +0000, Mark Hattam said:
[...]
> iMac:~ mark$ sudo port upgrade outdated
> --->  Fetching vim
> --->  Verifying checksum(s) for vim
> --->  Extracting vim
> --->  Applying patches to vim
> --->  Configuring vim
> --->  Building vim
[...]
> Undefined symbols:
>   "__Xsetlocale", referenced from:

Looks like #17606:

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

Bryan

[...]
>
> Mark

From mark at dxradio.demon.co.uk  Sun Jan 18 16:26:47 2009
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Mon, 19 Jan 2009 00:26:47 +0000
Subject: upgrading VIM errors
In-Reply-To: <20090119002025.GF741@ninagal.withay.com>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
	<20090119002025.GF741@ninagal.withay.com>
Message-ID: <D62C979A-C05C-474E-8366-2CFB16502AE7@dxradio.demon.co.uk>


On 19 Jan 2009, at 00:20, Bryan Blackburn wrote:

> On Mon, Jan 19, 2009 at 12:06:38AM +0000, Mark Hattam said:
> [...]
>> iMac:~ mark$ sudo port upgrade outdated
>> --->  Fetching vim
>> --->  Verifying checksum(s) for vim
>> --->  Extracting vim
>> --->  Applying patches to vim
>> --->  Configuring vim
>> --->  Building vim
> [...]
>> Undefined symbols:
>>  "__Xsetlocale", referenced from:
>
> Looks like #17606:
>
> <http://trac.macports.org/ticket/17606>
>
> Bryan
>
> [...]
>>
>> Mark


The previous version upgrade built without a problem ... so this seems  
a newer problem - or a problem that didn't affect 7.2.077_0

vim                            7.2.077_0 < 7.2.077_1

Today "update" seems to have been forced as a result of the X11  
changes detailed in the email
subject: [45603] trunk/dports
x11 dependent ports: Force port: based X11 dependencies

Mark

From mark at dxradio.demon.co.uk  Sun Jan 18 16:37:23 2009
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Mon, 19 Jan 2009 00:37:23 +0000
Subject: Fwd: upgrading VIM errors
References: <4B2C90F2-9D02-4179-950B-3F3B5DAA4956@alum.mit.edu>
Message-ID: <CE2B74E2-D9B8-4AE0-B323-9454E740DB06@dxradio.demon.co.uk>


Begin forwarded message:

> From: Adam Dershowitz <>
> Date: 19 January 2009 00:28:44 GMT
> To: Mark Hattam <mark at dxradio.demon.co.uk>
> Subject: Re: upgrading VIM errors
>
>
> On Jan 18, 2009, at 4:06 PM, Mark Hattam wrote:
>
>> Did a selfupdate on Macports 1.7 running on OSX 10.5.6, then a port  
>> outdated ...
>>
>> iMac:~ mark$ sudo port outdated
>> The following installed ports are outdated:
>> vim                            7.2.077_0 < 7.2.077_1
>>
>>
>> iMac:~ mark$ sudo port upgrade outdated
>>
>>
>>
>> Previously today, gd2 was updated
>> --->  Deactivating gd2 @2.0.35_2
>> --->  Installing gd2 @2.0.35_3
>>
>> whose upgrade process downloaded, built, installed and activated 70  
>> (seventy) xorg- packages ...
>>
>>
>> Mark
>
> I also did an upgrade that is still going...with a whole bunch of  
> xorg packages (I didn't count, like you did).  I think that some of  
> these got installed also because of a change in xrender.  So some  
> got installed as that was upgrading.
> Along the way it also installed python26!  It looks like this is  
> because it installed xorg-xcb-proto @1.3_0+python26.  I am not sure  
> if this will work or not because I have not, and was not planning to  
> run:  sudo python_select python26.
>


 >I< didn't count ... computers are good at that :-)

iMac:~ mark$ sudo port installed | grep xorg -c
70


Mark

From whodoctor at gmail.com  Sun Jan 18 16:25:01 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Sun, 18 Jan 2009 19:25:01 -0500
Subject: Error after trying to upgrade installed
In-Reply-To: <20090118235837.GE741@ninagal.withay.com>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
Message-ID: <4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>

On Sun, Jan 18, 2009 at 6:58 PM, Bryan Blackburn <blb at macports.org> wrote:
> On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer M?ller said:
>> Doctor Who wrote:
>> > I have MacPorts 1.7.0 installed.  I did a 'sudo port outdated' and had
>> > 5 or 6 ports that needed updating.  I then ran a 'sudo port upgrade
>> > outdated' and it failed after a while with errors like:
>> >
>> > sudo port upgrade outdated
>> > --->  Deactivating gettext @0.17_3
>> > Error: Deactivating gettext 0.17_3 failed:
>> > --->  Activating perl5.8 @5.8.9_2
> [...]
>>
>> Looks like you have coreutils +with_default_names installed, but you
>> broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
>> some reason it seems not to be active.
>
> Somebody reported this same issue last night on IRC, where it fails to
> deactivate gettext but not giving any actual error message.  It ends up
> removing all files from ${prefix} but then fails to set the port as not
> active, and ends up confused.
>
> You can't force-activate as it complains that it is already active, and any
> further deactivate results in the same output above.
>
> Unfortunately I didn't see any way to deal with this or what the cause was,
> and was hoping it was a one-off issue.  This is two now this weekend, so
> maybe something strange is going on in base...
>
> Bryan
>
>

Well, I hope there is some way to fix/recover from this.  I cannot
even list files on my file system in Terminal.app (as evidenced by the
attempt at the ls command above).

Can I totally uninstall MacPorts and reinstall?  If so, how?

From dersh at alum.mit.edu  Sun Jan 18 16:51:58 2009
From: dersh at alum.mit.edu (Adam Dershowitz)
Date: Sun, 18 Jan 2009 16:51:58 -0800
Subject: upgrading VIM errors
In-Reply-To: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
Message-ID: <6C2839F1-EC02-4C06-A25E-F0BCE34D1F35@alum.mit.edu>


On Jan 18, 2009, at 4:06 PM, Mark Hattam wrote:

> Did a selfupdate on Macports 1.7 running on OSX 10.5.6, then a port  
> outdated ...
>
>
>
> iMac:~ mark$ sudo port upgrade outdated

>
>
>
> Previously today, gd2 was updated
> --->  Deactivating gd2 @2.0.35_2
> --->  Installing gd2 @2.0.35_3
>
> whose upgrade process downloaded, built, installed and activated 70  
> (seventy) xorg- packages ...
>
>
> Mark
>

I also did an upgrade that is still going...with a whole bunch of xorg  
packages (I didn't count, like you did).  I think that some of these  
got installed also because of a change in xrender.  So some got  
installed as that was upgrading.
Along the way it also installed python26!  It looks like this is  
because it installed xorg-xcb-proto @1.3_0+python26.  I am not sure if  
this will work or not because I have not, and was not planning to  
run:  sudo python_select python26.

--Adam

From raimue at macports.org  Sun Jan 18 17:10:40 2009
From: raimue at macports.org (=?UTF-8?B?UmFpbmVyIE3DvGxsZXI=?=)
Date: Mon, 19 Jan 2009 02:10:40 +0100
Subject: Error after trying to upgrade installed
In-Reply-To: <4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>	<4973BF65.7050700@macports.org>	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
Message-ID: <4973D310.1090300@macports.org>

Doctor Who wrote:
> On Sun, Jan 18, 2009 at 6:58 PM, Bryan Blackburn <blb at macports.org> wrote:
>> On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer M?ller said:
>>> Doctor Who wrote:
>>>> I have MacPorts 1.7.0 installed.  I did a 'sudo port outdated' and had
>>>> 5 or 6 ports that needed updating.  I then ran a 'sudo port upgrade
>>>> outdated' and it failed after a while with errors like:
>>>>
>>>> sudo port upgrade outdated
>>>> --->  Deactivating gettext @0.17_3
>>>> Error: Deactivating gettext 0.17_3 failed:
>>>> --->  Activating perl5.8 @5.8.9_2
>> [...]
>>> Looks like you have coreutils +with_default_names installed, but you
>>> broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
>>> some reason it seems not to be active.
>> Somebody reported this same issue last night on IRC, where it fails to
>> deactivate gettext but not giving any actual error message.  It ends up
>> removing all files from ${prefix} but then fails to set the port as not
>> active, and ends up confused.
>>
>> You can't force-activate as it complains that it is already active, and any
>> further deactivate results in the same output above.
>>
>> Unfortunately I didn't see any way to deal with this or what the cause was,
>> and was hoping it was a one-off issue.  This is two now this weekend, so
>> maybe something strange is going on in base...
>>
>> Bryan
>>
>>
> 
> Well, I hope there is some way to fix/recover from this.  I cannot
> even list files on my file system in Terminal.app (as evidenced by the
> attempt at the ls command above).

It is trying to use /opt/local/bin/ls which is broken. You can still use
/bin/ls.

You can now either always type the full path /bin/ls, remove
/opt/local/bin from your PATH or deactivate the broken coreutils:
  sudo port deactivate coreutils

Then you should at least have working ls/cp/mv etc. again.

Now to fix the gettext issue, please try if this works now:
  sudo port deactivate gettext
  sudo port activate gettext

registry1.0 uses calls like 'system "rm -rf ${receipt_file}"' to work
with receipt files, so it was unable to operate with the broken
coreutils in PATH.

Rainer

From ohce86 at kitcarson.net  Sun Jan 18 17:11:55 2009
From: ohce86 at kitcarson.net (Timothy Goins)
Date: Sun, 18 Jan 2009 18:11:55 -0700
Subject: upgrading VIM errors
In-Reply-To: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
Message-ID: <CE8A190E-D573-4AA8-845A-07D0FDE70CA0@kitcarson.net>

I get exactly the same error output; however, I'm upgrading (or trying  
to) from "vim @7.2.021_0 (active)".  Also lots of xorg upgrades that  
succeed and a python that doesn't.  Frustrating!  openssl and vim are  
the only active ports that are outdated and won't upgrade on my system.

Tim
On Jan 18, 2009, at 5:06 PM, Mark Hattam wrote:

> Did a selfupdate on Macports 1.7 running on OSX 10.5.6, then a port  
> outdated ...
>
> iMac:~ mark$ sudo port outdated
> The following installed ports are outdated:
> vim                            7.2.077_0 < 7.2.077_1
>
>
> iMac:~ mark$ sudo port upgrade outdated
> --->  Fetching vim
> --->  Verifying checksum(s) for vim
> --->  Extracting vim
> --->  Applying patches to vim
> --->  Configuring vim
> --->  Building vim
> Error: Target org.macports.build returned: shell command " cd "/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_editors_vim/work/vim72" && make all "  
> returned error 2
> Command output: /usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/ 
> opt/local/include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/ 
> Headers/FlatCarbon  -O -D_FORTIFY_SOURCE=1         -o objects/ 
> quickfix.o quickfix.c
> /usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/ 
> include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/ 
> FlatCarbon  -O -D_FORTIFY_SOURCE=1         -o objects/regexp.o  
> regexp.c
>
> [lots more of these FORTIFY_SOURCE lines ending with ...]
>
> /usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/ 
> include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/ 
> FlatCarbon  -O -D_FORTIFY_SOURCE=1         version.c -o objects/ 
> version.o
>  /usr/bin/gcc-4.0   -L/opt/local/lib 	-o vim objects/buffer.o  
> objects/charset.o objects/diff.o objects/digraph.o objects/edit.o  
> objects/eval.o objects/ex_cmds.o objects/ex_cmds2.o objects/ 
> ex_docmd.o objects/ex_eval.o objects/ex_getln.o objects/fileio.o  
> objects/fold.o objects/getchar.o objects/hardcopy.o objects/ 
> hashtab.o  objects/if_cscope.o objects/if_xcmdsrv.o objects/main.o  
> objects/mark.o objects/memfile.o objects/memline.o objects/menu.o  
> objects/message.o objects/misc1.o objects/misc2.o objects/move.o  
> objects/mbyte.o objects/normal.o objects/ops.o objects/option.o  
> objects/os_unix.o objects/pathdef.o objects/popupmnu.o objects/ 
> quickfix.o objects/regexp.o objects/screen.o objects/search.o  
> objects/spell.o objects/syntax.o  objects/tag.o objects/term.o  
> objects/ui.o objects/undo.o objects/window.o       objects/ 
> os_macosx.o objects/os_mac_conv.o  objects/netbeans.o  objects/ 
> version.o       -lm  -lncurses -liconv -framework Carbon
> Undefined symbols:
>  "__Xsetlocale", referenced from:
>      _get_locale_val in ex_cmds2.o
>      _ex_language in ex_cmds2.o
>      _ex_language in ex_cmds2.o
>      _ex_language in ex_cmds2.o
>      _main in main.o
>      _main in main.o
>      _enc_locale in mbyte.o
>      _mac_lang_init in os_mac_conv.o
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[1]: *** [vim] Error 1
> make: *** [all] Error 2
>
> Error: Unable to upgrade port: 1
>
>
> Previous updates to VIM have worked OK.
>
> iMac:~ mark$ sudo port installed | grep vim
>  vim @7.2.077_0 (active)
>
>
> Previously today, gd2 was updated
> --->  Deactivating gd2 @2.0.35_2
> --->  Installing gd2 @2.0.35_3
>
> whose upgrade process downloaded, built, installed and activated 70  
> (seventy) xorg- packages ...
>
>
> Mark
>
> _______________________________________________
> 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/20090118/133186e6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2116 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090118/133186e6/attachment.bin>

From ryandesign at macports.org  Sun Jan 18 17:45:20 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 18 Jan 2009 19:45:20 -0600
Subject: error apache2 from macports 1.70
In-Reply-To: <20090118235453.GD741@ninagal.withay.com>
References: <E5726279-A56F-4F78-9EA1-98BCC7CD21EC@att.net>
	<362B5877-C1F4-429A-8E9B-1C78BEF72995@att.net>
	<20090118235453.GD741@ninagal.withay.com>
Message-ID: <6735C97F-AF52-48C3-BDD2-64DF9C5C3DD6@macports.org>


On Jan 18, 2009, at 17:54, Bryan Blackburn wrote:

> On Sun, Jan 18, 2009 at 07:12:45PM -0400, Jason Hirsh said:
>
>> sh: /opt/local/bin/bzip2: Bad CPU type in executable
>
> Was this MacPorts install copied over from a different architecture  
> (eg from
> a PowerPC to Intel)?

I would have thought that a PowerPC binary on an Intel Mac would work  
correctly through Rosetta.


> Odd though that it continued on after that as it should have failed  
> at this
> point instead of continuing.

No, unfortunately, that is a known problem that it does not error out  
at this point if the decompression program is faulty. We need to fix  
that.

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

I have thought that it would be nice to separate extraction from  
decompression instead of putting them in a single phase. Besides  
being cleaner and fixing the above issue, it would enable us to  
handle formats that cannot be decompressed and extracted in a single  
step, such as .dmg.zip. Unfortunately, so many ports have hacked the  
arguments of the existing extract phase that changing it at all at  
this point may be problematic.



From ryandesign at macports.org  Sun Jan 18 17:49:16 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 18 Jan 2009 19:49:16 -0600
Subject: upgrading VIM errors
In-Reply-To: <6C2839F1-EC02-4C06-A25E-F0BCE34D1F35@alum.mit.edu>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
	<6C2839F1-EC02-4C06-A25E-F0BCE34D1F35@alum.mit.edu>
Message-ID: <43B8AA3B-5BE3-473C-8099-4A0A624DE1C4@macports.org>


On Jan 18, 2009, at 18:51, Adam Dershowitz wrote:

> Along the way it also installed python26!  It looks like this is  
> because it installed xorg-xcb-proto @1.3_0+python26.  I am not sure  
> if this will work or not because I have not, and was not planning  
> to run:  sudo python_select python26.

It is not necessary to run "sudo python_select python26" unless you  
want to be able to type "python" and have it run python26. Any port  
that depends on python26 (or any other python) should function  
correctly without using python_select. Perhaps the message printed by  
the python ports could be worded differently, so that it is not  
implied that running python_select is necessary.



From whodoctor at gmail.com  Sun Jan 18 17:59:44 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Sun, 18 Jan 2009 20:59:44 -0500
Subject: Error after trying to upgrade installed
In-Reply-To: <4973D310.1090300@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
Message-ID: <4b75340e0901181759x7133a3abm435e6588a4753beb@mail.gmail.com>

On Sun, Jan 18, 2009 at 8:10 PM, Rainer M?ller <raimue at macports.org> wrote:
> Doctor Who wrote:
>> On Sun, Jan 18, 2009 at 6:58 PM, Bryan Blackburn <blb at macports.org> wrote:
>>> On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer M?ller said:
>>>> Doctor Who wrote:
>>>>> I have MacPorts 1.7.0 installed.  I did a 'sudo port outdated' and had
>>>>> 5 or 6 ports that needed updating.  I then ran a 'sudo port upgrade
>>>>> outdated' and it failed after a while with errors like:
>>>>>
>>>>> sudo port upgrade outdated
>>>>> --->  Deactivating gettext @0.17_3
>>>>> Error: Deactivating gettext 0.17_3 failed:
>>>>> --->  Activating perl5.8 @5.8.9_2
>>> [...]
>>>> Looks like you have coreutils +with_default_names installed, but you
>>>> broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
>>>> some reason it seems not to be active.
>>> Somebody reported this same issue last night on IRC, where it fails to
>>> deactivate gettext but not giving any actual error message.  It ends up
>>> removing all files from ${prefix} but then fails to set the port as not
>>> active, and ends up confused.
>>>
>>> You can't force-activate as it complains that it is already active, and any
>>> further deactivate results in the same output above.
>>>
>>> Unfortunately I didn't see any way to deal with this or what the cause was,
>>> and was hoping it was a one-off issue.  This is two now this weekend, so
>>> maybe something strange is going on in base...
>>>
>>> Bryan
>>>
>>>
>>
>> Well, I hope there is some way to fix/recover from this.  I cannot
>> even list files on my file system in Terminal.app (as evidenced by the
>> attempt at the ls command above).
>
> It is trying to use /opt/local/bin/ls which is broken. You can still use
> /bin/ls.
>
> You can now either always type the full path /bin/ls, remove
> /opt/local/bin from your PATH or deactivate the broken coreutils:
>  sudo port deactivate coreutils
>
> Then you should at least have working ls/cp/mv etc. again.
>
> Now to fix the gettext issue, please try if this works now:
>  sudo port deactivate gettext
>  sudo port activate gettext
>
> registry1.0 uses calls like 'system "rm -rf ${receipt_file}"' to work
> with receipt files, so it was unable to operate with the broken
> coreutils in PATH.
>
> Rainer
>

I get this when trying to deactivate:

$ sudo port deactivate gettext
Password:
--->  Deactivating gettext
Error: port deactivate failed:

From ryandesign at macports.org  Sun Jan 18 18:01:57 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 18 Jan 2009 20:01:57 -0600
Subject: Error after trying to upgrade installed
In-Reply-To: <4973D310.1090300@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>	<4973BF65.7050700@macports.org>	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
Message-ID: <69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>

On Jan 18, 2009, at 19:10, Rainer M?ller wrote:

> Doctor Who wrote:
>
>> Well, I hope there is some way to fix/recover from this.  I cannot
>> even list files on my file system in Terminal.app (as evidenced by  
>> the
>> attempt at the ls command above).
>
> It is trying to use /opt/local/bin/ls which is broken. You can  
> still use
> /bin/ls.
>
> You can now either always type the full path /bin/ls, remove
> /opt/local/bin from your PATH or deactivate the broken coreutils:
>   sudo port deactivate coreutils
>
> Then you should at least have working ls/cp/mv etc. again.

Yes, fixing the PATH in ~/.profile or ~/.bash_profile or just  
temporarily in the Terminal would allow you to now type "ls" or  
"touch" in the Terminal, however:


> Now to fix the gettext issue, please try if this works now:
>   sudo port deactivate gettext
>   sudo port activate gettext
>
> registry1.0 uses calls like 'system "rm -rf ${receipt_file}"' to work
> with receipt files, so it was unable to operate with the broken
> coreutils in PATH.

Note that the user's PATH is not used by MacPorts, so this will still  
fail until you also change the PATH that MacPorts uses while running,  
which is set in the variable binpath in the file /opt/local/etc/ 
macports/macports.conf

You could change the binpath so that /bin and /usr/bin precede /opt/ 
local/bin. Then MacPorts will use the system's file manipulation  
utilities (ln, touch, etc.) you will hopefully be able to deactivate  
the old gettext and activate the new one, at which point your  
coreutils versions of ln and touch will work again and you can (and  
should) revert binpath in macports.conf and PATH in .profile  
or .bash_profile to what they were.

Then, you should probably uninstall coreutils +with_default_names  
because it's probably not good to override those default Mac OS X  
utilities.

We could consider removing the +with_default_names capability from  
the coreutils port.

We should also consider forcing MacPorts base to always use vital  
utilities like ln and touch via their absolute paths in /bin or /usr/ 
bin and not allow a MacPorts version to interfere. We might consider  
the same for tar, gzip, bzip2, etc, to avoid the occasional problem  
with the MacPorts versions of those utilities, e.g. the thread "error  
apache2 from macports 1.70" earlier today:

http://lists.macosforge.org/pipermail/macports-users/2009-January/ 
013335.html



From whodoctor at gmail.com  Sun Jan 18 18:18:54 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Sun, 18 Jan 2009 21:18:54 -0500
Subject: Error after trying to upgrade installed
In-Reply-To: <69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
Message-ID: <4b75340e0901181818l1de65967q1fd1610143d49830@mail.gmail.com>

On Sun, Jan 18, 2009 at 9:01 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Jan 18, 2009, at 19:10, Rainer M?ller wrote:
>
>> Doctor Who wrote:
>>
>>> Well, I hope there is some way to fix/recover from this.  I cannot
>>> even list files on my file system in Terminal.app (as evidenced by the
>>> attempt at the ls command above).
>>
>> It is trying to use /opt/local/bin/ls which is broken. You can still use
>> /bin/ls.
>>
>> You can now either always type the full path /bin/ls, remove
>> /opt/local/bin from your PATH or deactivate the broken coreutils:
>>  sudo port deactivate coreutils
>>
>> Then you should at least have working ls/cp/mv etc. again.
>
> Yes, fixing the PATH in ~/.profile or ~/.bash_profile or just temporarily in
> the Terminal would allow you to now type "ls" or "touch" in the Terminal,
> however:
>
>
>> Now to fix the gettext issue, please try if this works now:
>>  sudo port deactivate gettext
>>  sudo port activate gettext
>>
>> registry1.0 uses calls like 'system "rm -rf ${receipt_file}"' to work
>> with receipt files, so it was unable to operate with the broken
>> coreutils in PATH.
>
> Note that the user's PATH is not used by MacPorts, so this will still fail
> until you also change the PATH that MacPorts uses while running, which is
> set in the variable binpath in the file
> /opt/local/etc/macports/macports.conf
>
> You could change the binpath so that /bin and /usr/bin precede
> /opt/local/bin. Then MacPorts will use the system's file manipulation
> utilities (ln, touch, etc.) you will hopefully be able to deactivate the old
> gettext and activate the new one, at which point your coreutils versions of
> ln and touch will work again and you can (and should) revert binpath in
> macports.conf and PATH in .profile or .bash_profile to what they were.
>
> Then, you should probably uninstall coreutils +with_default_names because
> it's probably not good to override those default Mac OS X utilities.
>
> We could consider removing the +with_default_names capability from the
> coreutils port.
>
> We should also consider forcing MacPorts base to always use vital utilities
> like ln and touch via their absolute paths in /bin or /usr/bin and not allow
> a MacPorts version to interfere. We might consider the same for tar, gzip,
> bzip2, etc, to avoid the occasional problem with the MacPorts versions of
> those utilities, e.g. the thread "error apache2 from macports 1.70" earlier
> today:
>
> http://lists.macosforge.org/pipermail/macports-users/2009-January/013335.html
>
>
>

Not to be a pain, but I'm pretty new to MacPorts and I don't want to
mess my system up more.  Would you please outline the steps I should
take one by one to (hopefully) restore my system back to 'normal'?

Thanks!

From ryandesign at macports.org  Sun Jan 18 18:28:16 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 18 Jan 2009 20:28:16 -0600
Subject: Error after trying to upgrade installed
In-Reply-To: <4b75340e0901181818l1de65967q1fd1610143d49830@mail.gmail.com>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<4b75340e0901181818l1de65967q1fd1610143d49830@mail.gmail.com>
Message-ID: <944BC661-E2A4-4AE2-B54D-CD6EAADD610F@macports.org>

On Jan 18, 2009, at 20:18, Doctor Who wrote:

> On Sun, Jan 18, 2009 at 9:01 PM, Ryan Schmidt wrote:
>
>> On Jan 18, 2009, at 19:10, Rainer M?ller wrote:
>>
>>> Doctor Who wrote:
>>>
>>>> Well, I hope there is some way to fix/recover from this.  I cannot
>>>> even list files on my file system in Terminal.app (as evidenced  
>>>> by the
>>>> attempt at the ls command above).
>>>
>>> It is trying to use /opt/local/bin/ls which is broken. You can  
>>> still use
>>> /bin/ls.
>>>
>>> You can now either always type the full path /bin/ls, remove
>>> /opt/local/bin from your PATH or deactivate the broken coreutils:
>>>  sudo port deactivate coreutils
>>>
>>> Then you should at least have working ls/cp/mv etc. again.
>>
>> Yes, fixing the PATH in ~/.profile or ~/.bash_profile or just  
>> temporarily in
>> the Terminal would allow you to now type "ls" or "touch" in the  
>> Terminal,
>> however:
>>
>>
>>> Now to fix the gettext issue, please try if this works now:
>>>  sudo port deactivate gettext
>>>  sudo port activate gettext
>>>
>>> registry1.0 uses calls like 'system "rm -rf ${receipt_file}"' to  
>>> work
>>> with receipt files, so it was unable to operate with the broken
>>> coreutils in PATH.
>>
>> Note that the user's PATH is not used by MacPorts, so this will  
>> still fail
>> until you also change the PATH that MacPorts uses while running,  
>> which is
>> set in the variable binpath in the file
>> /opt/local/etc/macports/macports.conf
>>
>> You could change the binpath so that /bin and /usr/bin precede
>> /opt/local/bin. Then MacPorts will use the system's file manipulation
>> utilities (ln, touch, etc.) you will hopefully be able to  
>> deactivate the old
>> gettext and activate the new one, at which point your coreutils  
>> versions of
>> ln and touch will work again and you can (and should) revert  
>> binpath in
>> macports.conf and PATH in .profile or .bash_profile to what they  
>> were.
>>
>> Then, you should probably uninstall coreutils +with_default_names  
>> because
>> it's probably not good to override those default Mac OS X utilities.
>>
>> We could consider removing the +with_default_names capability from  
>> the
>> coreutils port.
>>
>> We should also consider forcing MacPorts base to always use vital  
>> utilities
>> like ln and touch via their absolute paths in /bin or /usr/bin and  
>> not allow
>> a MacPorts version to interfere. We might consider the same for  
>> tar, gzip,
>> bzip2, etc, to avoid the occasional problem with the MacPorts  
>> versions of
>> those utilities, e.g. the thread "error apache2 from macports  
>> 1.70" earlier
>> today:
>>
>> http://lists.macosforge.org/pipermail/macports-users/2009-January/ 
>> 013335.html
>
> Not to be a pain, but I'm pretty new to MacPorts and I don't want to
> mess my system up more.  Would you please outline the steps I should
> take one by one to (hopefully) restore my system back to 'normal'?

I'm not certain, as I haven't encountered this problem before.

But my suggestion is exactly as I outlined above.

1. Edit /opt/local/etc/macports/macports.conf and change this line:

#binpath		/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/ 
sbin:/usr/X11R6/bin

Remove the hash at the beginning and change the order so that it reads:

binpath		/bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/ 
sbin:/usr/X11R6/bin

2. Deactivate your old gettext:

sudo port deactivate gettext @0.17_3

3. Activate your new gettext:

sudo port activate gettext @0.17_4

4. Uninstall coreutils because it is not a good idea to override the  
default Mac OS X file utilities:

sudo port uninstall coreutils

5. Edit /opt/local/etc/macports/macporst.conf and put the binpath  
line back the way it was before, including the order of the paths and  
the hash at the beginning of the line.




From whodoctor at gmail.com  Sun Jan 18 18:39:20 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Sun, 18 Jan 2009 21:39:20 -0500
Subject: Error after trying to upgrade installed
In-Reply-To: <944BC661-E2A4-4AE2-B54D-CD6EAADD610F@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<4b75340e0901181818l1de65967q1fd1610143d49830@mail.gmail.com>
	<944BC661-E2A4-4AE2-B54D-CD6EAADD610F@macports.org>
Message-ID: <4b75340e0901181839u4a5cf010uaca6a02c8911f648@mail.gmail.com>

On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Jan 18, 2009, at 20:18, Doctor Who wrote:
>
>> On Sun, Jan 18, 2009 at 9:01 PM, Ryan Schmidt wrote:
>>
>>> On Jan 18, 2009, at 19:10, Rainer M?ller wrote:
>>>
>>>> Doctor Who wrote:
>>>>
>>>>> Well, I hope there is some way to fix/recover from this.  I cannot
>>>>> even list files on my file system in Terminal.app (as evidenced by the
>>>>> attempt at the ls command above).
>>>>
>>>> It is trying to use /opt/local/bin/ls which is broken. You can still use
>>>> /bin/ls.
>>>>
>>>> You can now either always type the full path /bin/ls, remove
>>>> /opt/local/bin from your PATH or deactivate the broken coreutils:
>>>>  sudo port deactivate coreutils
>>>>
>>>> Then you should at least have working ls/cp/mv etc. again.
>>>
>>> Yes, fixing the PATH in ~/.profile or ~/.bash_profile or just temporarily
>>> in
>>> the Terminal would allow you to now type "ls" or "touch" in the Terminal,
>>> however:
>>>
>>>
>>>> Now to fix the gettext issue, please try if this works now:
>>>>  sudo port deactivate gettext
>>>>  sudo port activate gettext
>>>>
>>>> registry1.0 uses calls like 'system "rm -rf ${receipt_file}"' to work
>>>> with receipt files, so it was unable to operate with the broken
>>>> coreutils in PATH.
>>>
>>> Note that the user's PATH is not used by MacPorts, so this will still
>>> fail
>>> until you also change the PATH that MacPorts uses while running, which is
>>> set in the variable binpath in the file
>>> /opt/local/etc/macports/macports.conf
>>>
>>> You could change the binpath so that /bin and /usr/bin precede
>>> /opt/local/bin. Then MacPorts will use the system's file manipulation
>>> utilities (ln, touch, etc.) you will hopefully be able to deactivate the
>>> old
>>> gettext and activate the new one, at which point your coreutils versions
>>> of
>>> ln and touch will work again and you can (and should) revert binpath in
>>> macports.conf and PATH in .profile or .bash_profile to what they were.
>>>
>>> Then, you should probably uninstall coreutils +with_default_names because
>>> it's probably not good to override those default Mac OS X utilities.
>>>
>>> We could consider removing the +with_default_names capability from the
>>> coreutils port.
>>>
>>> We should also consider forcing MacPorts base to always use vital
>>> utilities
>>> like ln and touch via their absolute paths in /bin or /usr/bin and not
>>> allow
>>> a MacPorts version to interfere. We might consider the same for tar,
>>> gzip,
>>> bzip2, etc, to avoid the occasional problem with the MacPorts versions of
>>> those utilities, e.g. the thread "error apache2 from macports 1.70"
>>> earlier
>>> today:
>>>
>>>
>>> http://lists.macosforge.org/pipermail/macports-users/2009-January/013335.html
>>
>> Not to be a pain, but I'm pretty new to MacPorts and I don't want to
>> mess my system up more.  Would you please outline the steps I should
>> take one by one to (hopefully) restore my system back to 'normal'?
>
> I'm not certain, as I haven't encountered this problem before.
>
> But my suggestion is exactly as I outlined above.
>
> 1. Edit /opt/local/etc/macports/macports.conf and change this line:
>
> #binpath
>  /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
>
> Remove the hash at the beginning and change the order so that it reads:
>
> binpath
> /bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin:/usr/X11R6/bin
>
> 2. Deactivate your old gettext:
>
> sudo port deactivate gettext @0.17_3
>
> 3. Activate your new gettext:
>
> sudo port activate gettext @0.17_4
>
> 4. Uninstall coreutils because it is not a good idea to override the default
> Mac OS X file utilities:
>
> sudo port uninstall coreutils
>
> 5. Edit /opt/local/etc/macports/macporst.conf and put the binpath line back
> the way it was before, including the order of the paths and the hash at the
> beginning of the line.
>
>
>
>

OK, when I get to the point of activating the later version of
gettext, it's not installed:

tbook:~ who$ sudo port deactivate gettext @0.17_3
--->  Deactivating gettext @0.17_3
tbook:~ who$ sudo port activate gettext @0.17_4
Error: port activate failed: Registry error: gettext 0.17_4 not
registered as installed.

What should I do at this point to install this version correctly?

From ryandesign at macports.org  Sun Jan 18 18:43:22 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 18 Jan 2009 20:43:22 -0600
Subject: Error after trying to upgrade installed
In-Reply-To: <4b75340e0901181839u4a5cf010uaca6a02c8911f648@mail.gmail.com>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<4b75340e0901181818l1de65967q1fd1610143d49830@mail.gmail.com>
	<944BC661-E2A4-4AE2-B54D-CD6EAADD610F@macports.org>
	<4b75340e0901181839u4a5cf010uaca6a02c8911f648@mail.gmail.com>
Message-ID: <D2F037C9-308C-4EBE-B70C-1950D85C9511@macports.org>


On Jan 18, 2009, at 20:39, Doctor Who wrote:

> On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:
>
>> On Jan 18, 2009, at 20:18, Doctor Who wrote:
>>
>>> Not to be a pain, but I'm pretty new to MacPorts and I don't want to
>>> mess my system up more.  Would you please outline the steps I should
>>> take one by one to (hopefully) restore my system back to 'normal'?

I meant to say earlier, but don't feel that you're bothering us:  
you've clearly found a problem and we need to first get you out of it  
and then figure out how to not make it affect others. Sorry this  
happened; I know it's not a pleasant experience, especially when  
you're just trying to get used to MacPorts. It's not usually like  
this. :)


>> I'm not certain, as I haven't encountered this problem before.
>>
>> But my suggestion is exactly as I outlined above.
>>
>> 1. Edit /opt/local/etc/macports/macports.conf and change this line:
>>
>> #binpath
>>  /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/ 
>> X11R6/bin
>>
>> Remove the hash at the beginning and change the order so that it  
>> reads:
>>
>> binpath
>> /bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin:/usr/ 
>> X11R6/bin
>>
>> 2. Deactivate your old gettext:
>>
>> sudo port deactivate gettext @0.17_3
>>
>> 3. Activate your new gettext:
>>
>> sudo port activate gettext @0.17_4
>>
>> 4. Uninstall coreutils because it is not a good idea to override  
>> the default
>> Mac OS X file utilities:
>>
>> sudo port uninstall coreutils
>>
>> 5. Edit /opt/local/etc/macports/macporst.conf and put the binpath  
>> line back
>> the way it was before, including the order of the paths and the  
>> hash at the
>> beginning of the line.
>
> OK, when I get to the point of activating the later version of
> gettext, it's not installed:
>
> tbook:~ who$ sudo port deactivate gettext @0.17_3
> --->  Deactivating gettext @0.17_3
> tbook:~ who$ sudo port activate gettext @0.17_4
> Error: port activate failed: Registry error: gettext 0.17_4 not
> registered as installed.
>
> What should I do at this point to install this version correctly?


Try:

sudo port install gettext


From ryandesign at macports.org  Sun Jan 18 18:57:32 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 18 Jan 2009 20:57:32 -0600
Subject: Error after trying to upgrade installed
In-Reply-To: <4b75340e0901181853x6563015fkd011e95367e10cdc@mail.gmail.com>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<4b75340e0901181818l1de65967q1fd1610143d49830@mail.gmail.com>
	<944BC661-E2A4-4AE2-B54D-CD6EAADD610F@macports.org>
	<4b75340e0901181839u4a5cf010uaca6a02c8911f648@mail.gmail.com>
	<D2F037C9-308C-4EBE-B70C-1950D85C9511@macports.org>
	<4b75340e0901181853x6563015fkd011e95367e10cdc@mail.gmail.com>
Message-ID: <B297D05C-1E62-441D-B8BA-63F2833A6F72@macports.org>


On Jan 18, 2009, at 20:53, Doctor Who wrote:

> Also, does removing coreutils cause a problems with paths for tools
> like 'ls' now?  How do I fix the paths so I can use the tools again?
>
> tbook:~ who$ ls
> -bash: /opt/local/bin/ls: No such file or directory

Since /opt/local/bin/ls doesn't exist, the shell should now look for  
ls in other paths, and find it in /bin.

You must have it set up differently.... What does "which ls" say?  
What does "alias | grep ls" say?


From whodoctor at gmail.com  Sun Jan 18 18:53:32 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Sun, 18 Jan 2009 21:53:32 -0500
Subject: Error after trying to upgrade installed
In-Reply-To: <D2F037C9-308C-4EBE-B70C-1950D85C9511@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<4b75340e0901181818l1de65967q1fd1610143d49830@mail.gmail.com>
	<944BC661-E2A4-4AE2-B54D-CD6EAADD610F@macports.org>
	<4b75340e0901181839u4a5cf010uaca6a02c8911f648@mail.gmail.com>
	<D2F037C9-308C-4EBE-B70C-1950D85C9511@macports.org>
Message-ID: <4b75340e0901181853x6563015fkd011e95367e10cdc@mail.gmail.com>

On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
>
> On Jan 18, 2009, at 20:39, Doctor Who wrote:
>
>> On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:
>>
>>> On Jan 18, 2009, at 20:18, Doctor Who wrote:
>>>
>>>> Not to be a pain, but I'm pretty new to MacPorts and I don't want to
>>>> mess my system up more.  Would you please outline the steps I should
>>>> take one by one to (hopefully) restore my system back to 'normal'?
>
> I meant to say earlier, but don't feel that you're bothering us: you've
> clearly found a problem and we need to first get you out of it and then
> figure out how to not make it affect others. Sorry this happened; I know
> it's not a pleasant experience, especially when you're just trying to get
> used to MacPorts. It's not usually like this. :)
>
>
>>> I'm not certain, as I haven't encountered this problem before.
>>>
>>> But my suggestion is exactly as I outlined above.
>>>
>>> 1. Edit /opt/local/etc/macports/macports.conf and change this line:
>>>
>>> #binpath
>>>
>>>  /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
>>>
>>> Remove the hash at the beginning and change the order so that it reads:
>>>
>>> binpath
>>>
>>> /bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin:/usr/X11R6/bin
>>>
>>> 2. Deactivate your old gettext:
>>>
>>> sudo port deactivate gettext @0.17_3
>>>
>>> 3. Activate your new gettext:
>>>
>>> sudo port activate gettext @0.17_4
>>>
>>> 4. Uninstall coreutils because it is not a good idea to override the
>>> default
>>> Mac OS X file utilities:
>>>
>>> sudo port uninstall coreutils
>>>
>>> 5. Edit /opt/local/etc/macports/macporst.conf and put the binpath line
>>> back
>>> the way it was before, including the order of the paths and the hash at
>>> the
>>> beginning of the line.
>>
>> OK, when I get to the point of activating the later version of
>> gettext, it's not installed:
>>
>> tbook:~ who$ sudo port deactivate gettext @0.17_3
>> --->  Deactivating gettext @0.17_3
>> tbook:~ who$ sudo port activate gettext @0.17_4
>> Error: port activate failed: Registry error: gettext 0.17_4 not
>> registered as installed.
>>
>> What should I do at this point to install this version correctly?
>
>
> Try:
>
> sudo port install gettext
>
>

Also, does removing coreutils cause a problems with paths for tools
like 'ls' now?  How do I fix the paths so I can use the tools again?

tbook:~ who$ ls
-bash: /opt/local/bin/ls: No such file or directory

From ryandesign at macports.org  Sun Jan 18 19:04:40 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 18 Jan 2009 21:04:40 -0600
Subject: Error after trying to upgrade installed
In-Reply-To: <4b75340e0901181850tab7b12encfb467be8e4f1a41@mail.gmail.com>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<4b75340e0901181818l1de65967q1fd1610143d49830@mail.gmail.com>
	<944BC661-E2A4-4AE2-B54D-CD6EAADD610F@macports.org>
	<4b75340e0901181839u4a5cf010uaca6a02c8911f648@mail.gmail.com>
	<D2F037C9-308C-4EBE-B70C-1950D85C9511@macports.org>
	<4b75340e0901181850tab7b12encfb467be8e4f1a41@mail.gmail.com>
Message-ID: <B57CF743-6D2D-4794-9306-F694A6B37EEC@macports.org>

On Jan 18, 2009, at 20:50, Doctor Who wrote:

> On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt  wrote:
>>
>
>> Try:
>>
>> sudo port install gettext
>
> Thanks...that worked.

Great!

> Should I now try to update with 'sudo port upgrade outdated'?

Sure, go ahead. I know there have been a lot of X11/xorg-related  
changes lately, and I haven't tried them myself yet, so good luck!


From whodoctor at gmail.com  Sun Jan 18 18:59:48 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Sun, 18 Jan 2009 21:59:48 -0500
Subject: Error after trying to upgrade installed
In-Reply-To: <B297D05C-1E62-441D-B8BA-63F2833A6F72@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<4b75340e0901181818l1de65967q1fd1610143d49830@mail.gmail.com>
	<944BC661-E2A4-4AE2-B54D-CD6EAADD610F@macports.org>
	<4b75340e0901181839u4a5cf010uaca6a02c8911f648@mail.gmail.com>
	<D2F037C9-308C-4EBE-B70C-1950D85C9511@macports.org>
	<4b75340e0901181853x6563015fkd011e95367e10cdc@mail.gmail.com>
	<B297D05C-1E62-441D-B8BA-63F2833A6F72@macports.org>
Message-ID: <4b75340e0901181859p4a68e934j357c45a6930fd811@mail.gmail.com>

On Sun, Jan 18, 2009 at 9:57 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
>
> On Jan 18, 2009, at 20:53, Doctor Who wrote:
>
>> Also, does removing coreutils cause a problems with paths for tools
>> like 'ls' now?  How do I fix the paths so I can use the tools again?
>>
>> tbook:~ who$ ls
>> -bash: /opt/local/bin/ls: No such file or directory
>
> Since /opt/local/bin/ls doesn't exist, the shell should now look for ls in
> other paths, and find it in /bin.
>
> You must have it set up differently.... What does "which ls" say? What does
> "alias | grep ls" say?
>
>

It's working now, once I started another shell.

Thanks.

From whodoctor at gmail.com  Sun Jan 18 18:50:52 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Sun, 18 Jan 2009 21:50:52 -0500
Subject: Error after trying to upgrade installed
In-Reply-To: <D2F037C9-308C-4EBE-B70C-1950D85C9511@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<4b75340e0901181818l1de65967q1fd1610143d49830@mail.gmail.com>
	<944BC661-E2A4-4AE2-B54D-CD6EAADD610F@macports.org>
	<4b75340e0901181839u4a5cf010uaca6a02c8911f648@mail.gmail.com>
	<D2F037C9-308C-4EBE-B70C-1950D85C9511@macports.org>
Message-ID: <4b75340e0901181850tab7b12encfb467be8e4f1a41@mail.gmail.com>

On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
>
> On Jan 18, 2009, at 20:39, Doctor Who wrote:
>
>> On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:
>>
>>> On Jan 18, 2009, at 20:18, Doctor Who wrote:
>>>
>>>> Not to be a pain, but I'm pretty new to MacPorts and I don't want to
>>>> mess my system up more.  Would you please outline the steps I should
>>>> take one by one to (hopefully) restore my system back to 'normal'?
>
> I meant to say earlier, but don't feel that you're bothering us: you've
> clearly found a problem and we need to first get you out of it and then
> figure out how to not make it affect others. Sorry this happened; I know
> it's not a pleasant experience, especially when you're just trying to get
> used to MacPorts. It's not usually like this. :)
>
>
>>> I'm not certain, as I haven't encountered this problem before.
>>>
>>> But my suggestion is exactly as I outlined above.
>>>
>>> 1. Edit /opt/local/etc/macports/macports.conf and change this line:
>>>
>>> #binpath
>>>
>>>  /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin
>>>
>>> Remove the hash at the beginning and change the order so that it reads:
>>>
>>> binpath
>>>
>>> /bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin:/usr/X11R6/bin
>>>
>>> 2. Deactivate your old gettext:
>>>
>>> sudo port deactivate gettext @0.17_3
>>>
>>> 3. Activate your new gettext:
>>>
>>> sudo port activate gettext @0.17_4
>>>
>>> 4. Uninstall coreutils because it is not a good idea to override the
>>> default
>>> Mac OS X file utilities:
>>>
>>> sudo port uninstall coreutils
>>>
>>> 5. Edit /opt/local/etc/macports/macporst.conf and put the binpath line
>>> back
>>> the way it was before, including the order of the paths and the hash at
>>> the
>>> beginning of the line.
>>
>> OK, when I get to the point of activating the later version of
>> gettext, it's not installed:
>>
>> tbook:~ who$ sudo port deactivate gettext @0.17_3
>> --->  Deactivating gettext @0.17_3
>> tbook:~ who$ sudo port activate gettext @0.17_4
>> Error: port activate failed: Registry error: gettext 0.17_4 not
>> registered as installed.
>>
>> What should I do at this point to install this version correctly?
>
>
> Try:
>
> sudo port install gettext
>
>

Thanks...that worked.  Should I now try to update with 'sudo port
upgrade outdated'?

From hirshj at att.net  Sun Jan 18 19:23:19 2009
From: hirshj at att.net (Jason Hirsh)
Date: Sun, 18 Jan 2009 23:23:19 -0400
Subject: error apache2 from macports 1.70
In-Reply-To: <20090118235453.GD741@ninagal.withay.com>
References: <E5726279-A56F-4F78-9EA1-98BCC7CD21EC@att.net>
	<362B5877-C1F4-429A-8E9B-1C78BEF72995@att.net>
	<20090118235453.GD741@ninagal.withay.com>
Message-ID: <605E2F31-C7B0-4F85-A2B5-F91D61EA3F6F@att.net>


On Jan 18, 2009, at 7:54 PM, Bryan Blackburn wrote:

> On Sun, Jan 18, 2009 at 07:12:45PM -0400, Jason Hirsh said:
> [...]
>>>
>>> Ok ther still seems to be an issue with that configure directory not
>>> being created
>>> I took a llok and I have nothing in the tree under work in the path
>>> shown in the error
>>>
>>> [Bluefish:/opt/local] jason% sudo port -d extract apache2
> [...]
>>> DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
>>> --->  Extracting apache2
>>> DEBUG: Executing org.macports.extract (apache2)
>>> --->  Extracting httpd-2.2.11.tar.bz2
>>> DEBUG: setting option extract.args to /opt/local/var/macports/
>>> distfiles/apache2/httpd-2.2.11.tar.bz2
>>> 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_www_apache2/work" && /opt/local/bin/ 
>>> bzip2
>>> -dc /opt/local/var/macports/distfiles/apache2/httpd-2.2.11.tar.bz2 |
>>> /usr/bin/gnutar --no-same-owner -xf -'
>>> sh: /opt/local/bin/bzip2: Bad CPU type in executable
>
> Was this MacPorts install copied over from a different architecture  
> (eg from
> a PowerPC to Intel)?
>
> Odd though that it continued on after that as it should have failed  
> at this
> point instead of continuing.
>
> Bryan
>

presuming wrong type  howdoI correct
> [...]
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From ryandesign at macports.org  Sun Jan 18 19:53:27 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 18 Jan 2009 21:53:27 -0600
Subject: error apache2 from macports 1.70
In-Reply-To: <605E2F31-C7B0-4F85-A2B5-F91D61EA3F6F@att.net>
References: <E5726279-A56F-4F78-9EA1-98BCC7CD21EC@att.net>
	<362B5877-C1F4-429A-8E9B-1C78BEF72995@att.net>
	<20090118235453.GD741@ninagal.withay.com>
	<605E2F31-C7B0-4F85-A2B5-F91D61EA3F6F@att.net>
Message-ID: <9410125F-664E-4894-BA3D-6D739D7AD0EF@macports.org>

On Jan 18, 2009, at 21:23, Jason Hirsh wrote:

> On Jan 18, 2009, at 7:54 PM, Bryan Blackburn wrote:
>
>> On Sun, Jan 18, 2009 at 07:12:45PM -0400, Jason Hirsh said:
>>
>>> sh: /opt/local/bin/bzip2: Bad CPU type in executable
>>
>> Was this MacPorts install copied over from a different  
>> architecture (eg from
>> a PowerPC to Intel)?
>
> presuming wrong type  howdoI correct
>>

sudo port -nf upgrade bzip2

That will cause bzip2 to be rebuilt.

But if you copied this MacPorts installation from another machine,  
it's likely most or all of your other ports are also affected by this  
problem and you should do the same for all of them. But you would  
have to do it in the right order. It may be easier to uninstall all  
ports first, then install again what you need, which will do it in  
the right order for you.


From blb at macports.org  Sun Jan 18 20:29:23 2009
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 18 Jan 2009 21:29:23 -0700
Subject: Error after trying to upgrade installed
In-Reply-To: <69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
Message-ID: <20090119042923.GK741@ninagal.withay.com>

On Sun, Jan 18, 2009 at 08:01:57PM -0600, Ryan Schmidt said:
[...]
>
> We should also consider forcing MacPorts base to always use vital  
> utilities like ln and touch via their absolute paths in /bin or /usr/bin 
> and not allow a MacPorts version to interfere. We might consider the same 
> for tar, gzip, bzip2, etc, to avoid the occasional problem with the 
> MacPorts versions of those utilities, e.g. the thread "error apache2 from 
> macports 1.70" earlier today:

For some tools (eg, rm) which are definitely guaranteed to be
system-installed and acceptable, that makes sense.  For others, there's
#15868:

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

So using the system-installed version (svn in that case) would make things
worse...

Bryan


>
> http://lists.macosforge.org/pipermail/macports-users/2009-January/013335.html
>

From blb at macports.org  Sun Jan 18 20:32:09 2009
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 18 Jan 2009 21:32:09 -0700
Subject: upgrading VIM errors
In-Reply-To: <43B8AA3B-5BE3-473C-8099-4A0A624DE1C4@macports.org>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
	<6C2839F1-EC02-4C06-A25E-F0BCE34D1F35@alum.mit.edu>
	<43B8AA3B-5BE3-473C-8099-4A0A624DE1C4@macports.org>
Message-ID: <20090119043209.GL741@ninagal.withay.com>

On Sun, Jan 18, 2009 at 07:49:16PM -0600, Ryan Schmidt said:
>
> On Jan 18, 2009, at 18:51, Adam Dershowitz wrote:
>
>> Along the way it also installed python26!  It looks like this is  
>> because it installed xorg-xcb-proto @1.3_0+python26.  I am not sure if 
>> this will work or not because I have not, and was not planning to run:  
>> sudo python_select python26.
>
> It is not necessary to run "sudo python_select python26" unless you want 
> to be able to type "python" and have it run python26. Any port that 
> depends on python26 (or any other python) should function correctly 
> without using python_select. Perhaps the message printed by the python 
> ports could be worded differently, so that it is not implied that running 
> python_select is necessary.

There could be some ports which do in fact need a version selected as the
Current version setting for the framework
(${prefix}/Library/Frameworks/Python.framework/Version/Current and the
symlinks in just Python.framework/) are used when linking to it.

Thought I believe it's been suggested before that the first python port
installed should probably be automatically python_select'd...

Bryan


From HerrPoetry at HailMail.net  Sun Jan 18 22:24:16 2009
From: HerrPoetry at HailMail.net (Mark)
Date: Mon, 19 Jan 2009 01:24:16 -0500
Subject: Error building nspr during Gnome-Control Center install
Message-ID: <49741C90.4050602@HailMail.net>

Could someone help me interpret this error? I tried installing 
Gnome-Control-Center, and early it bombed on this:

> --->  Building nspr
> 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_nspr/work/nspr-4.7.3/mozilla/nsprpub" 
> && make all " returned error 2
> Command output: /usr/include/mach/processor_info.h:99: error: syntax 
> error before 'cpu_type_t'
> /usr/include/mach/processor_info.h:104: error: syntax error before '}' 
> token
> In file included from /usr/include/mach-o/dyld.h:31,
>                  from prlink.c:85:
> /usr/include/mach-o/loader.h:56: error: syntax error before 'cpu_type_t'
> /usr/include/mach-o/loader.h:62: error: syntax error before '}' token
> /usr/include/mach-o/loader.h:74: error: syntax error before 'cpu_type_t'
> /usr/include/mach-o/loader.h:81: error: syntax error before '}' token
> prlink.c: In function 'pr_LoadMachDyldModule':
> prlink.c:613: warning: 'NSCreateObjectFileImageFromFile' is deprecated 
> (declared at /usr/include/mach-o/dyld.h:145)
> prlink.c:615: warning: 'NSLinkModule' is deprecated (declared at 
> /usr/include/mach-o/dyld.h:161)
> prlink.c:621: warning: 'NSDestroyObjectFileImage' is deprecated 
> (declared at /usr/include/mach-o/dyld.h:147)
> prlink.c:623: warning: 'NSUnLinkModule' is deprecated (declared at 
> /usr/include/mach-o/dyld.h:169)
> prlink.c: In function 'pr_LoadViaDyld':
> prlink.c:775: warning: 'NSAddImage' is deprecated (declared at 
> /usr/include/mach-o/dyld.h:230)
> prlink.c:782: warning: 'NSLinkEditError' is deprecated (declared at 
> /usr/include/mach-o/dyld.h:217)
> prlink.c: In function 'PR_UnloadLibrary':
> prlink.c:1289: warning: 'NSUnLinkModule' is deprecated (declared at 
> /usr/include/mach-o/dyld.h:169)
> prlink.c:1305: warning: 'CloseConnection' is deprecated (declared at 
> /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CodeFragments.h:382)
> prlink.c: In function 'pr_FindSymbolInLib':
> prlink.c:1418: warning: 'c2pstrcpy' is deprecated (declared at 
> /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/TextUtils.h:578)
> prlink.c:1420: warning: 'FindSymbol' is deprecated (declared at 
> /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CodeFragments.h:401)
> prlink.c:1433: warning: 'NSLookupSymbolInImage' is deprecated 
> (declared at /usr/include/mach-o/dyld.h:182)
> prlink.c:1437: warning: 'NSAddressOfSymbol' is deprecated (declared at 
> /usr/include/mach-o/dyld.h:188)
> prlink.c:1461: warning: 'NSLookupSymbolInModule' is deprecated 
> (declared at /usr/include/mach-o/dyld.h:181)
> prlink.c:1463: warning: 'NSAddressOfSymbol' is deprecated (declared at 
> /usr/include/mach-o/dyld.h:188)
> make[3]: *** [prlink.o] Error 1
> make[2]: *** [export] Error 2
> make[1]: *** [export] Error 2
> make: *** [export] Error 2
>
> Error: The following dependencies failed to build: 
> evolution-data-server nspr nss sqlite3 gnome-desktop gnome-themes 
> gtk-engines2 py25-gnome py25-gtk py25-cairo py25-numpy fftw-3 
> py25-nose py25-setuptools py25-zlib py25-gobject py25-orbit 
> gnome-menus gnome-panel libgweather librsvg libcroco libwnck 
> startup-notification gnome-settings-daemon gst-plugins-good aalib flac 
> libogg gst-plugins-base cdparanoia gstreamer flex gzip liboil 
> libtheora libvorbis libcaca libcdio libcddb libdv libshout2 speex 
> taglib wavpack libgnomekbd libxklavier libcanberra metacity nautilus 
> eel libexif
> Error: Status 1 encountered during processing.

- Mark

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090119/27838f90/attachment.html>

From ryandesign at macports.org  Mon Jan 19 02:25:27 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 19 Jan 2009 04:25:27 -0600
Subject: Error building nspr during Gnome-Control Center install
In-Reply-To: <49741C90.4050602@HailMail.net>
References: <49741C90.4050602@HailMail.net>
Message-ID: <44505526-923A-4D06-AD95-33498942267C@macports.org>


On Jan 19, 2009, at 00:24, Mark wrote:

> Could someone help me interpret this error? I tried installing  
> Gnome-Control-Center, and early it bombed on this:
>
>> --->  Building nspr
>> Error: Target org.macports.build returned: shell command " cd "/ 
>> opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_deve 
>> l_nspr/work/nspr-4.7.3/mozilla/nsprpub" && make all " returned  
>> error 2
>> Command output: /usr/include/mach/processor_info.h:99: error:  
>> syntax error before 'cpu_type_t'
>> /usr/include/mach/processor_info.h:104: error: syntax error before  
>> '}' token
>> In file included from /usr/include/mach-o/dyld.h:31,
>>                  from prlink.c:85:

I'm not sure we're seeing the first error here. MacPorts only shows  
you the last 40 (I think) lines of error. Try "sudo port clean nspr"  
and then "sudo port -d install nspr" and see what the first error is.  
That may tell us more.


From talklists at newgeo.com  Mon Jan 19 03:39:02 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 19 Jan 2009 03:39:02 -0800
Subject: many perl modules I need
Message-ID: <40BE89BB-D341-4984-8A15-681D7F865440@newgeo.com>

Let's start here, new install of MacPorts, dev tools is in, X11 is in.
I ran sudo port install perl5 and went to the next one I needed:

me at memacbook:~/ $sudo port install -f p5-Email-MIME-Modifier
--->  Fetching p5-test-simple
--->  Verifying checksum(s) for p5-test-simple
--->  Extracting p5-test-simple
--->  Configuring p5-test-simple
--->  Building p5-test-simple
--->  Staging p5-test-simple into destroot
You must install or activate this package with '-f' (force) as it  
needs to overwrite files installed by the perl5.8 port
--->  Installing p5-test-simple @0.86_0
Error: Target org.macports.install returned: Registry error: p5-test- 
simple @0.86_0 already registered as installed.  Please uninstall it  
first.
Error: The following dependencies failed to build: p5-test-pod p5-test- 
simple
Error: Status 1 encountered during processing.

--
Scott


From j.van_den_hoff at fzd.de  Mon Jan 19 03:50:56 2009
From: j.van_den_hoff at fzd.de (Joerg van den Hoff)
Date: Mon, 19 Jan 2009 12:50:56 +0100
Subject: maxima installation failed
Message-ID: <20090119115056.GA17265@marco.fz-rossendorf.de>

dear all,

my attempt to install `maxima' failed with

=================CUT=================================
 sudo port install maxima
 --->  Building recode
 --->  Staging recode into destroot
 --->  Packaging tgz archive for recode 3.6_3
 --->  Installing recode @3.6_3
 --->  Activating recode @3.6_3
 --->  Cleaning recode
 --->  Fetching sbcl
 --->  Attempting to fetch sbcl-1.0.24-source.tar.bz2 from
 http://dfn.dl.sourceforge.net/sbcl
 --->  Attempting to fetch sbcl-1.0.22-powerpc-darwin-binary.tar.bz2
 from http://dfn.dl.sourceforge.net/sbcl
 --->  Verifying checksum(s) for sbcl
 --->  Extracting sbcl
 --->  Applying patches to sbcl
 --->  Configuring sbcl
 --->  Building sbcl
 Error: Target org.macports.build returned: shell command "unset
 LD_PREBIND && unset LD_PREBIND_ALLOW_OVERLAP && sh make.sh
 "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_sbcl/work/sbcl-1.0.22-powerpc-darwin/src/runtime/sbcl
 --core
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_sbcl/work/sbcl-1.0.22-powerpc-darwin/output/sbcl.core
 --disable-debugger --sysinit /dev/null --userinit /dev/null" " returned
 error 1
 Command output: //starting build: Mon Jan 19 12:42:39 CET 2009
 //SBCL_XC_HOST="/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_sbcl/work/sbcl-1.0.22-powerpc-darwin/src/runtime/sbcl
 --core
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_sbcl/work/sbcl-1.0.22-powerpc-darwin/output/sbcl.core
 --disable-debugger --sysinit /dev/null --userinit /dev/null"
 //entering make-config.sh
 //ensuring the existence of output/ directory
 //initializing
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_sbcl/work/sbcl-1.0.24/local-target-features.lisp-expr
 //guessing default target CPU architecture from host architecture
 //setting up CPU-architecture-dependent information
 sbcl_arch="ppc"
 //setting up symlink src/compiler/target
 //setting up symlink src/assembly/target
 //setting up symlink src/compiler/assembly
 //setting up OS-dependent information
 //finishing
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_sbcl/work/sbcl-1.0.24/local-target-features.lisp-expr
 /in canonicalize-whitespace-1
 /$*=./customize-target-features.lisp ./local-target-features.lisp-expr
 ./tests/test-status.lisp-expr ./contrib/sb-bsd-sockets/foo.c
 ./contrib/sb-posix/foo.c ./src/runtime/runtime.c
 ./src/runtime/target-arch-os.h ./src/runtime/target-arch.h
 ./src/runtime/target-lispregs.h ./src/runtime/target-os.h
 /$scratchfilename=/tmp/canonicalize-whitespace-1.17069.tmp
 //entering make-host-1.sh
 //building cross-compiler, and doing first genesis
 make-host-1.sh: line 31: 17083 Bus error               $SBCL_XC_HOST
 <make-host-1.lisp
=================CUT=================================

i.e. a bus error during `sbcl' install. 

this is on a PPC G5, MacOSX 10.4.11 and with `port' version 1.700

any help would be appreciated.

regards,

joerg

From talklists at newgeo.com  Mon Jan 19 04:14:59 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 19 Jan 2009 04:14:59 -0800
Subject: Walk through on perl modules
Message-ID: <82527D45-1CC8-41BF-91B9-14B82E5BAFAB@newgeo.com>

I have a rather large list of small p5 modules I am going to need.   
Can someone walk me through the creation of one, and I can do the  
rest, and send them in for addition?

This should get me going.
Net::Syslog

I have a new ports install, so step from there, to where to put the  
local port file, and how to register it and take it forward would be  
highly helpful.  If there are good docs on this, please just point me  
to them.

Thank you.
--
Scott

--
Scott


From talklists at newgeo.com  Mon Jan 19 04:22:23 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 19 Jan 2009 04:22:23 -0800
Subject: ASSP out of date
In-Reply-To: <693C4C90-970D-4B53-A52A-07288AC7365B@pixilla.com>
References: <33DB3AA3-3AB2-408F-9CEC-07AFBD55E857@newgeo.com>
	<188585BA-078E-4D06-9930-7DAE321B1901@macports.org>
	<D95268B0-57B6-43A7-A5A8-801667CE078B@newgeo.com>
	<864EDFE1-9031-457F-831C-1C560219B380@macports.org>
	<323629E3-14C3-42CE-8EA8-B34EC785C059@newgeo.com>
	<20081111095733.GY747@ninagal.withay.com>
	<DF7AF73D-5A61-44CB-807B-5B044F663F4E@macports.org>
	<9A5136AD-CAAB-44B1-9BEB-DA6CDAD36558@newgeo.com>
	<5F4F8D22-03BC-4670-98F5-A48FD07D17A4@macports.org>
	<3B673105-B884-4954-87E4-435F73A2C25E@newgeo.com>
	<20081112025226.GM596@ninagal.withay.com>
	<51069ED4-F375-4B26-8DC2-974504DA2F26@newgeo.com>
	<693C4C90-970D-4B53-A52A-07288AC7365B@pixilla.com>
Message-ID: <0B861D9F-D94E-4C66-98E7-30A9F8A1A955@newgeo.com>

On Jan 18, 2009, at 4:02 PM, Bradley Giesbrecht wrote:

> This is what I do.
>
> http://guide.macports.org/#development.local-repositories

Are there any more specific notes on perl mods, and the perl.sources  
file?  Mainly, how it works, and what you use as filenames?  I am  
looking at port edit p5-something_already_installed and they are  
pretty bare, but they do have checksums which I do not know how to get  
at.

I am also not entirely clear on file names, and how the entire process  
works with these small simple modules.

Curious, how come MacPorts does not have 100% parity with CPAN?  CPAN  
seems to work fine on OS X, other than it is a little scary and  
strange at times, but is there not a layer to MacPorts that translates  
CPAN into a portfile, or even does so automatically?
--
Scott

From hirshj at att.net  Mon Jan 19 05:05:17 2009
From: hirshj at att.net (Jason Hirsh)
Date: Mon, 19 Jan 2009 09:05:17 -0400
Subject: error apache2 from macports 1.70 (RESOLVED)
In-Reply-To: <9410125F-664E-4894-BA3D-6D739D7AD0EF@macports.org>
References: <E5726279-A56F-4F78-9EA1-98BCC7CD21EC@att.net>
	<362B5877-C1F4-429A-8E9B-1C78BEF72995@att.net>
	<20090118235453.GD741@ninagal.withay.com>
	<605E2F31-C7B0-4F85-A2B5-F91D61EA3F6F@att.net>
	<9410125F-664E-4894-BA3D-6D739D7AD0EF@macports.org>
Message-ID: <DD1A7F18-E82B-4CD5-9BA2-FB06119E7C90@att.net>

OK I deinstalled and re-installed.  Although I had done this before  
this time was much different and worked great

I have two machines really interlaced   so I guess I screwed up along  
the way

thanks for the help...

Jason

On Jan 18, 2009, at 11:53 PM, Ryan Schmidt wrote:

> On Jan 18, 2009, at 21:23, Jason Hirsh wrote:
>
>> On Jan 18, 2009, at 7:54 PM, Bryan Blackburn wrote:
>>
>>> On Sun, Jan 18, 2009 at 07:12:45PM -0400, Jason Hirsh said:
>>>
>>>> sh: /opt/local/bin/bzip2: Bad CPU type in executable
>>>
>>> Was this MacPorts install copied over from a different  
>>> architecture (eg from
>>> a PowerPC to Intel)?
>>
>> presuming wrong type  howdoI correct
>>>
>
> sudo port -nf upgrade bzip2
>
> That will cause bzip2 to be rebuilt.
>
> But if you copied this MacPorts installation from another machine,  
> it's likely most or all of your other ports are also affected by  
> this problem and you should do the same for all of them. But you  
> would have to do it in the right order. It may be easier to  
> uninstall all ports first, then install again what you need, which  
> will do it in the right order for you.
>


From face at CentosPrime.COM  Mon Jan 19 05:08:15 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Mon, 19 Jan 2009 06:08:15 -0700
Subject: freetype fails to build on Panther
Message-ID: <580177FE-097C-4496-AF73-752D9B8C9AB3@centosprime.com>

MacPorts 1.7 - Panther

--->  Fetching freetype
--->  Attempting to fetch freetype-2.3.8.tar.bz2 from http://download.savannah.gnu.org/releases/freetype/
--->  Attempting to fetch freetype-2.3.8.tar.bz2 from http://downloads.sourceforge.net/freetype
--->  Attempting to fetch freetype-doc-2.3.8.tar.bz2 from http://download.savannah.gnu.org/releases/freetype/
--->  Verifying checksum(s) for freetype
--->  Extracting freetype
--->  Applying patches to freetype
--->  Configuring freetype
Error: Target org.macports.configure returned: configure failure:  
shell command " cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_print_freetype/work/freetype-2.3.8" && ./ 
configure --prefix=/opt/local --with-old-mac-fonts " returned error 2
Command output: builds/toplevel.mk:43: *** FreeType's build system  
needs a Make program which supports $(value).  Stop.

Error: Unable to upgrade port: 1

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



From apple at frinabulax.org  Mon Jan 19 05:37:05 2009
From: apple at frinabulax.org (robert delius royar)
Date: Mon, 19 Jan 2009 08:37:05 -0500
Subject: Error after trying to upgrade installed
In-Reply-To: <69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
Message-ID: <alpine.OSX.2.00L.0901190811250.80957@teraqry.sevanohynk.bet>

So much traffic on this thread, so much time spent answering questions. 
But I do not recall any of the answerers trying
port provides /opt/local/lib/libintl.dylib

That would have pointerd out that the initial problem of gettext wanting 
to reinstall itself (perhaps for no good reason) had removed the dylibs 
that gettext provides and uses, itself.

I believe this highlights some error in the 1.70 base.  I say this 
because it seems to be faulty UI that allows a user to specify a variant 
that when in place the port command can be broken in a simple upgrade.

I mention above "perhaps for no good reason" because last week when I 
upgraded graphviz which upgraded gd2, I got into a loop of trying to 
upgrade freetype, zlib and gettext, none of which were outdated 
according to port.  I finally had to force the reinstallation of zlib 
and gettext, force uninstall gd2, freetype, zlib, and gettext and start 
over.

That was not the first time I had seen this loop of upgrading a port 
that was the same version as the curreny installed version, followed by 
failing to install the "new" version because a version was already in 
place (the same version).  In some cases the process stopps there; in 
others it moves to the next port that it either "thinks" should be 
upgraded or really should be.  Then if that port depends on one of the 
ports it has mistakenly identified as outdated, it goes into the same 
pattern.  On a few occassions I have found libraries from those ports 
which wer not in need of replacement--but replaced anyway--missing. 
TimeMachine is useful, then,

I have the last model of the G5 iMac running 10.5.6, and the 
portinstalltype is direct, and portarchivemode is no.  1.7 seems as 
though it has sections that are not sure what "direct" mode is by the 
way; some ports I have upgraded recently report "activating."  I have 
not used image mode on this machine at all.

-- 
Dr. Robert Delius Royar                   Associate Professor of English
Morehead State University                             Morehead, Kentucky

From face at CentosPrime.COM  Mon Jan 19 06:22:00 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Mon, 19 Jan 2009 07:22:00 -0700
Subject: error upgrading freetype / xorg-libxcb et al on Panther
Message-ID: <4F182005-88CD-4673-8CB5-FCEC0B8DA8D0@centosprime.com>

admin at x:admin:139 $ sudo port upgrade xorg-libxcb
--->  Fetching xorg-libxcb
--->  Verifying checksum(s) for xorg-libxcb
--->  Extracting xorg-libxcb
--->  Applying patches to xorg-libxcb
--->  Configuring xorg-libxcb
Error: Target org.macports.configure returned: configure failure:  
shell command " cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_x11_xorg-libxcb/work/libxcb-1.1" && ./ 
configure --prefix=/opt/local " returned error 1
Command output: checking for /usr/bin/gcc-3.3 option to produce PIC...  
-fno-common -DPIC
checking if /usr/bin/gcc-3.3 PIC flag -fno-common -DPIC works... yes
checking if /usr/bin/gcc-3.3 static flag -static works... no
checking if /usr/bin/gcc-3.3 supports -c -o file.o... yes
checking if /usr/bin/gcc-3.3 supports -c -o file.o... (cached) yes
checking whether the /usr/bin/gcc-3.3 linker (/usr/bin/ld) supports  
shared libraries... yes
checking dynamic linker characteristics... darwin7.9.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 gcc... (cached) /usr/bin/gcc-3.3
checking whether we are using the GNU C compiler... (cached) yes
checking whether /usr/bin/gcc-3.3 accepts -g... (cached) yes
checking for /usr/bin/gcc-3.3 option to accept ISO C89... (cached)  
none needed
checking dependency style of /usr/bin/gcc-3.3... (cached) gcc3
checking for xsltproc... /opt/local/bin/xsltproc
checking for XCBPROTO... yes
checking for NEEDED... configure: error: Package requirements (pthread- 
stubs xau >= 0.99.2) were not met:

No package 'pthread-stubs' 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 NEEDED_CFLAGS
and NEEDED_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


--->  Configuring freetype
Error: Target org.macports.configure returned: configure failure:  
shell command " cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_print_freetype/work/freetype-2.3.8" && ./ 
configure --prefix=/opt/local --with-old-mac-fonts " returned error 2
Command output: builds/toplevel.mk:43: *** FreeType's build system  
needs a Make program which supports $(value).  Stop.

Error: Unable to upgrade port: 1
admin at x:admin:140 $

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



From shreevatsa.public at gmail.com  Mon Jan 19 08:01:53 2009
From: shreevatsa.public at gmail.com (Shreevatsa R)
Date: Mon, 19 Jan 2009 11:01:53 -0500
Subject: Steps to ensure compatibility between fink and macports
In-Reply-To: <AFC4F6B4-AC32-46FA-BE76-2F1780E7C3C7@macports.org>
References: <391652.36615.qm@web51909.mail.re2.yahoo.com>
	<AFC4F6B4-AC32-46FA-BE76-2F1780E7C3C7@macports.org>
Message-ID: <7675454e0901190801q669586a2hc7473e960342dc15@mail.gmail.com>

On Sat, Jan 17, 2009 at 3:58 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Jan 17, 2009, at 01:12, David T. wrote:
>
>> I am new to this list. I have had a macbook for three years now after
>> moving from 20+years in the PC world with a smattering of Linux. I am
>> running 10.5.6, and I have used fink for my limited open-source software
>> needs (gnucash), but recently saw that others have been able to use MacPorts
>> to create a Quartz version of Gnucash. Since I have a working version of
>> Gnucash using fink, I am leery about just firing up Macports and trying the
>> steps listed by others. Before I do this, I'd like to know with some
>> certainty the steps I need to take to insulate the functional fink package
>> from my fiddling around with MacPorts. I searched for guidance on
>> fink/macports compatibility, but didn't find any clear outlines of how to
>> ensure this. Has anyone got a clear set of steps and guidelines for me to
>> follow to try using macports without messing up fink?
>
> Rename fink's /sw directory to something else. That should ensure it does
> not interfere with MacPorts.
>
> You should only use software installed via one package manager at a time --
> either Fink, or MacPorts, not both.

Er, I don't think this is true. You don't have to do *anything* to
ensure Fink and MacPorts don't intefere with each other. They are both
designed to not interfere with the rest of the system, so if they do
interfere with each other, it's a bug in one of them.

In my experience (and that of others) it works perfectly to use both
Fink and MacPorts simultaneously; installing packages from whichever
of the two happens to have a working version. (But do care about what
you do to your environment variables like $PATH: Fink's
/sw/bin/init.sh is a bit heavy-handed.)

Of course I'm just a user and don't know very much of the internals of
either, so maybe someone can correct me if I'm wrong.

From HerrPoetry at HailMail.net  Mon Jan 19 08:35:21 2009
From: HerrPoetry at HailMail.net (Mark)
Date: Mon, 19 Jan 2009 11:35:21 -0500
Subject: Error building nspr during Gnome-Control Center install
In-Reply-To: <44505526-923A-4D06-AD95-33498942267C@macports.org>
References: <49741C90.4050602@HailMail.net>
	<44505526-923A-4D06-AD95-33498942267C@macports.org>
Message-ID: <4974ABC9.3050006@HailMail.net>

Ryan Schmidt wrote:
>
> On Jan 19, 2009, at 00:24, Mark wrote:
>
>> Could someone help me interpret this error? I tried installing 
>> Gnome-Control-Center, and early it bombed.
>
> I'm not sure we're seeing the first error here. MacPorts only shows 
> you the last 40 (I think) lines of error. Try "sudo port clean nspr" 
> and then "sudo port -d install nspr" and see what the first error is. 
> That may tell us more.

I should add that the only reason I'm trying to install 
gnome-control-center is to give myself a way to change the default font 
for my native-Quartz-GnuCash (i.e. doesn't use X11). So if there's a 
more efficient way of doing that, I can sidestep gnome-control-center -- 
but I've posted about GnuCash's default font in the past few days and it 
seems native-Quartz GnuCash is too new, and no one has proposed a 
method. Here is that original GnuCash font post:

> /I have just finished a complete fresh 
> install of Macports, followed by a native Quartz, minimal (+without_hbci 
> +without_ofx +without_quotes) install of GnuCash on MBP 10.5.6.
>
> I can't figure out how to change the default font for the program. When 
> I used to run GnuCash under X11 (Fink package GnuCash2), I had -- and 
> still have -- a file in my home directory named .gtkrc-2.0 which 
> contains a single line: gtk-font-name = "Luxi Mono 16" -- and that used 
> to cause GnuCash to use that font in all its windows.
>
> But not anymore! Apparently native Quartz GnuCash installed via MacPorts 
> isn't consulting ~/gtkrc-2.0, or is somehow overriding it? Anything I 
> can do to get my big beautiful font back?/

Back to nspr. I did what you said. Here's the entire nspr build phase 
output:

--->  Building nspr
DEBUG: Executing org.macports.build (nspr)
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_nspr/work/nspr-4.7.3/mozilla/nsprpub" 
&& make all'
cd config; make -j1 export
/usr/bin/gcc-4.0 -o now.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM   now.c
/usr/bin/gcc-4.0  now.o -L/opt/local/lib  -o now
/usr/bin/gcc-4.0 -o nsinstall.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM   nsinstall.c
/usr/bin/gcc-4.0  nsinstall.o -L/opt/local/lib  -o nsinstall
rm -f nfspwd; cp nfspwd.pl nfspwd; chmod +x nfspwd
rm -f ../dist/bin/nspr-config
cd pr; make -j1 export
cd include; make export
cd md; make export
../../../config/./nsinstall -R -m 444 ./_aix32.cfg ./_aix64.cfg 
./_beos.cfg ./_bsdi.cfg ./_darwin.cfg ./_dgux.cfg ./_freebsd.cfg 
./_hpux32.cfg ./_hpux64.cfg ./_irix32.cfg ./_irix64.cfg ./_linux.cfg 
./_ncr.cfg ./_nec.cfg ./_netbsd.cfg ./_nextstep.cfg ./_nto.cfg 
./_openbsd.cfg ./_openvms.cfg ./_os2.cfg ./_osf1.cfg ./_qnx.cfg 
./_reliantunix.cfg ./_riscos.cfg ./_scoos.cfg ./_solaris.cfg ./_sony.cfg 
./_sunos4.cfg ./_symbian.cfg ./_unixware.cfg ./_unixware7.cfg 
./_win16.cfg ./_win95.cfg ./_winnt.cfg ../../../dist/include/nspr/md
../../../config/./nsinstall -R -m 444 ./_darwin.cfg 
../../../dist/include/nspr
mv -f ../../../dist/include/nspr/_darwin.cfg 
../../../dist/include/nspr/prcpucfg.h
cd private; make export
../../../config/./nsinstall -R -m 444 ./pprio.h ./pprthred.h ./prpriv.h 
../../../dist/include/nspr/private
cd obsolete; make export
../../../config/./nsinstall -R -m 444 ./pralarm.h ./probslet.h 
./protypes.h ./prsem.h ../../../dist/include/nspr/obsolete
../../config/./nsinstall -R -m 444 ./nspr.h ./pratom.h ./prbit.h 
./prclist.h ./prcmon.h ./prcountr.h ./prcvar.h ./prdtoa.h ./prenv.h 
./prerr.h ./prerror.h ./prinet.h ./prinit.h ./prinrval.h ./prio.h 
./pripcsem.h ./prlink.h ./prlock.h ./prlog.h ./prlong.h ./prmem.h 
./prmon.h ./prmwait.h ./prnetdb.h ./prolock.h ./prpdce.h ./prprf.h 
./prproces.h ./prrng.h ./prrwlock.h ./prshm.h ./prshma.h ./prsystem.h 
./prthread.h ./prtime.h ./prtpool.h ./prtrace.h ./prtypes.h ./prvrsion.h 
./prwin16.h ../../dist/include/nspr
cd src; make export
cd io; make export
/usr/bin/gcc-4.0 -o prfdcach.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private  prfdcach.c
/usr/bin/gcc-4.0 -o prmwait.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private  prmwait.c
/usr/bin/gcc-4.0 -o priometh.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private  priometh.c
/usr/bin/gcc-4.0 -o pripv6.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private  pripv6.c
/usr/bin/gcc-4.0 -o prmapopt.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private  prmapopt.c
/usr/bin/gcc-4.0 -o prlayer.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private  prlayer.c
/usr/bin/gcc-4.0 -o prlog.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private  prlog.c
/usr/bin/gcc-4.0 -o prmmap.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private  prmmap.c
/usr/bin/gcc-4.0 -o prpolevt.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private  prpolevt.c
/usr/bin/gcc-4.0 -o prprf.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private  prprf.c
prprf.c: In function 'dosprintf':
prprf.c:700: warning: 'nap' may be used uninitialized in this function
/usr/bin/gcc-4.0 -o prscanf.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private  prscanf.c
prscanf.c: In function 'PR_sscanf':
prscanf.c:342: warning: 'ch' may be used uninitialized in this function
prscanf.c:232: warning: 'ch' may be used uninitialized in this function
/usr/bin/gcc-4.0 -o prstdio.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private  prstdio.c
cd linking; make export
/usr/bin/gcc-4.0 -o prlink.o -c    -I/opt/local/include -O2 -Wmost 
-fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 -DDARWIN=1 
-DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 -DHAVE_LCHOWN=1 
-DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
-UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
-I../../../pr/include -I../../../pr/include/private 
-I/Developer/Headers/FlatCarbon  prlink.c
In file included from /usr/include/mach/mach_types.h:80,
                 from 
/System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:41,
                 from 
/System/Library/Frameworks/DiskArbitration.framework/Headers/DADisk.h:28,
                 from 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Files.h:62,
                 from 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Components.h:32,
                 from 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:85,
                 from 
/System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20,
                 from 
/System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:21,
                 from /Developer/Headers/FlatCarbon/CodeFragments.h:1,
                 from prlink.c:48:
/usr/include/mach/host_info.h:70:26: error: /usr/include/mach/machine.h: 
Input/output error
In file included from /usr/include/mach/mach_types.h:80,
                 from 
/System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:41,
                 from 
/System/Library/Frameworks/DiskArbitration.framework/Headers/DADisk.h:28,
                 from 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Files.h:62,
                 from 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Components.h:32,
                 from 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:85,
                 from 
/System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20,
                 from 
/System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:21,
                 from /Developer/Headers/FlatCarbon/CodeFragments.h:1,
                 from prlink.c:48:
/usr/include/mach/host_info.h:109: error: syntax error before 'cpu_type_t'
/usr/include/mach/host_info.h:111: error: syntax error before 
'cpu_threadtype'
/usr/include/mach/host_info.h:117: error: syntax error before '}' token
/usr/include/mach/host_info.h:196: error: 'CPU_STATE_MAX' undeclared 
here (not in a function)
In file included from /usr/include/mach/mach_types.h:89,
                 from 
/System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:41,
                 from 
/System/Library/Frameworks/DiskArbitration.framework/Headers/DADisk.h:28,
                 from 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Files.h:62,
                 from 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Components.h:32,
                 from 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:85,
                 from 
/System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20,
                 from 
/System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:21,
                 from /Developer/Headers/FlatCarbon/CodeFragments.h:1,
                 from prlink.c:48:
/usr/include/mach/processor_info.h:99: error: syntax error before 
'cpu_type_t'
/usr/include/mach/processor_info.h:104: error: syntax error before '}' token
In file included from /usr/include/mach-o/dyld.h:31,
                 from prlink.c:85:
/usr/include/mach-o/loader.h:56: error: syntax error before 'cpu_type_t'
/usr/include/mach-o/loader.h:62: error: syntax error before '}' token
/usr/include/mach-o/loader.h:74: error: syntax error before 'cpu_type_t'
/usr/include/mach-o/loader.h:81: error: syntax error before '}' token
prlink.c: In function 'pr_LoadMachDyldModule':
prlink.c:613: warning: 'NSCreateObjectFileImageFromFile' is deprecated 
(declared at /usr/include/mach-o/dyld.h:145)
prlink.c:615: warning: 'NSLinkModule' is deprecated (declared at 
/usr/include/mach-o/dyld.h:161)
prlink.c:621: warning: 'NSDestroyObjectFileImage' is deprecated 
(declared at /usr/include/mach-o/dyld.h:147)
prlink.c:623: warning: 'NSUnLinkModule' is deprecated (declared at 
/usr/include/mach-o/dyld.h:169)
prlink.c: In function 'pr_LoadViaDyld':
prlink.c:775: warning: 'NSAddImage' is deprecated (declared at 
/usr/include/mach-o/dyld.h:230)
prlink.c:782: warning: 'NSLinkEditError' is deprecated (declared at 
/usr/include/mach-o/dyld.h:217)
prlink.c: In function 'PR_UnloadLibrary':
prlink.c:1289: warning: 'NSUnLinkModule' is deprecated (declared at 
/usr/include/mach-o/dyld.h:169)
prlink.c:1305: warning: 'CloseConnection' is deprecated (declared at 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CodeFragments.h:382)
prlink.c: In function 'pr_FindSymbolInLib':
prlink.c:1418: warning: 'c2pstrcpy' is deprecated (declared at 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/TextUtils.h:578)
prlink.c:1420: warning: 'FindSymbol' is deprecated (declared at 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CodeFragments.h:401)
prlink.c:1433: warning: 'NSLookupSymbolInImage' is deprecated (declared 
at /usr/include/mach-o/dyld.h:182)
prlink.c:1437: warning: 'NSAddressOfSymbol' is deprecated (declared at 
/usr/include/mach-o/dyld.h:188)
prlink.c:1461: warning: 'NSLookupSymbolInModule' is deprecated (declared 
at /usr/include/mach-o/dyld.h:181)
prlink.c:1463: warning: 'NSAddressOfSymbol' is deprecated (declared at 
/usr/include/mach-o/dyld.h:188)
make[3]: *** [prlink.o] Error 1
make[2]: *** [export] Error 2
make[1]: *** [export] Error 2
make: *** [export] Error 2
Error: Target org.macports.build returned: shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_nspr/work/nspr-4.7.3/mozilla/nsprpub" 
&& make all " returned error 2
Command output: /usr/include/mach/processor_info.h:99: error: syntax 
error before 'cpu_type_t'
/usr/include/mach/processor_info.h:104: error: syntax error before '}' token
In file included from /usr/include/mach-o/dyld.h:31,
                 from prlink.c:85:
/usr/include/mach-o/loader.h:56: error: syntax error before 'cpu_type_t'
/usr/include/mach-o/loader.h:62: error: syntax error before '}' token
/usr/include/mach-o/loader.h:74: error: syntax error before 'cpu_type_t'
/usr/include/mach-o/loader.h:81: error: syntax error before '}' token
prlink.c: In function 'pr_LoadMachDyldModule':
prlink.c:613: warning: 'NSCreateObjectFileImageFromFile' is deprecated 
(declared at /usr/include/mach-o/dyld.h:145)
prlink.c:615: warning: 'NSLinkModule' is deprecated (declared at 
/usr/include/mach-o/dyld.h:161)
prlink.c:621: warning: 'NSDestroyObjectFileImage' is deprecated 
(declared at /usr/include/mach-o/dyld.h:147)
prlink.c:623: warning: 'NSUnLinkModule' is deprecated (declared at 
/usr/include/mach-o/dyld.h:169)
prlink.c: In function 'pr_LoadViaDyld':
prlink.c:775: warning: 'NSAddImage' is deprecated (declared at 
/usr/include/mach-o/dyld.h:230)
prlink.c:782: warning: 'NSLinkEditError' is deprecated (declared at 
/usr/include/mach-o/dyld.h:217)
prlink.c: In function 'PR_UnloadLibrary':
prlink.c:1289: warning: 'NSUnLinkModule' is deprecated (declared at 
/usr/include/mach-o/dyld.h:169)
prlink.c:1305: warning: 'CloseConnection' is deprecated (declared at 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CodeFragments.h:382)
prlink.c: In function 'pr_FindSymbolInLib':
prlink.c:1418: warning: 'c2pstrcpy' is deprecated (declared at 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/TextUtils.h:578)
prlink.c:1420: warning: 'FindSymbol' is deprecated (declared at 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CodeFragments.h:401)
prlink.c:1433: warning: 'NSLookupSymbolInImage' is deprecated (declared 
at /usr/include/mach-o/dyld.h:182)
prlink.c:1437: warning: 'NSAddressOfSymbol' is deprecated (declared at 
/usr/include/mach-o/dyld.h:188)
prlink.c:1461: warning: 'NSLookupSymbolInModule' is deprecated (declared 
at /usr/include/mach-o/dyld.h:181)
prlink.c:1463: warning: 'NSAddressOfSymbol' is deprecated (declared at 
/usr/include/mach-o/dyld.h:188)
make[3]: *** [prlink.o] Error 1
make[2]: *** [export] Error 2
make[1]: *** [export] Error 2
make: *** [export] Error 2

Warning: the following items did not execute (for nspr): 
org.macports.activate org.macports.build org.macports.destroot 
org.macports.install
Error: Status 1 encountered during processing.

TIA,
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090119/599e6043/attachment.html>

From jmr at macports.org  Mon Jan 19 09:42:30 2009
From: jmr at macports.org (Joshua Root)
Date: Tue, 20 Jan 2009 04:42:30 +1100
Subject: Error building nspr during Gnome-Control Center install
In-Reply-To: <4974ABC9.3050006@HailMail.net>
References: <49741C90.4050602@HailMail.net>	<44505526-923A-4D06-AD95-33498942267C@macports.org>
	<4974ABC9.3050006@HailMail.net>
Message-ID: <4974BB86.9000904@macports.org>

Mark wrote:
> Back to nspr. I did what you said. Here's the entire nspr build phase
> output:
> 
[...]
> /usr/include/mach/host_info.h:70:26: error: /usr/include/mach/machine.h: Input/output error

That looks fairly dire.

- Josh

From jmr at macports.org  Mon Jan 19 09:44:25 2009
From: jmr at macports.org (Joshua Root)
Date: Tue, 20 Jan 2009 04:44:25 +1100
Subject: many perl modules I need
In-Reply-To: <40BE89BB-D341-4984-8A15-681D7F865440@newgeo.com>
References: <40BE89BB-D341-4984-8A15-681D7F865440@newgeo.com>
Message-ID: <4974BBF9.5020001@macports.org>

Scott Haneda wrote:
> Let's start here, new install of MacPorts, dev tools is in, X11 is in.
> I ran sudo port install perl5 and went to the next one I needed:
> 
> me at memacbook:~/ $sudo port install -f p5-Email-MIME-Modifier
> --->  Fetching p5-test-simple
> --->  Verifying checksum(s) for p5-test-simple
> --->  Extracting p5-test-simple
> --->  Configuring p5-test-simple
> --->  Building p5-test-simple
> --->  Staging p5-test-simple into destroot
> You must install or activate this package with '-f' (force) as it needs
> to overwrite files installed by the perl5.8 port
> --->  Installing p5-test-simple @0.86_0
> Error: Target org.macports.install returned: Registry error:
> p5-test-simple @0.86_0 already registered as installed.  Please
> uninstall it first.
> Error: The following dependencies failed to build: p5-test-pod
> p5-test-simple
> Error: Status 1 encountered during processing.

As it says in the error message:
> You must install or activate this package with '-f' (force) as it needs
> to overwrite files installed by the perl5.8 port

i.e. you need to run: `sudo port -f activate p5-test-simple`

This is <http://trac.macports.org/ticket/12710>.

- Josh

From jmr at macports.org  Mon Jan 19 09:46:41 2009
From: jmr at macports.org (Joshua Root)
Date: Tue, 20 Jan 2009 04:46:41 +1100
Subject: Walk through on perl modules
In-Reply-To: <82527D45-1CC8-41BF-91B9-14B82E5BAFAB@newgeo.com>
References: <82527D45-1CC8-41BF-91B9-14B82E5BAFAB@newgeo.com>
Message-ID: <4974BC81.7070202@macports.org>

Scott Haneda wrote:
> I have a rather large list of small p5 modules I am going to need.  Can
> someone walk me through the creation of one, and I can do the rest, and
> send them in for addition?
> 
> This should get me going.
> Net::Syslog
> 
> I have a new ports install, so step from there, to where to put the
> local port file, and how to register it and take it forward would be
> highly helpful.  If there are good docs on this, please just point me to
> them.

See <http://guide.macports.org/#development.local-repositories>.

You should find this tool useful: <http://mc.koha-fr.org/mac/cpan2port/>

- Josh

From jeremyhu at macports.org  Mon Jan 19 10:53:08 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Mon, 19 Jan 2009 10:53:08 -0800
Subject: error upgrading freetype / xorg-libxcb et al on Panther
In-Reply-To: <4F182005-88CD-4673-8CB5-FCEC0B8DA8D0@centosprime.com>
References: <4F182005-88CD-4673-8CB5-FCEC0B8DA8D0@centosprime.com>
Message-ID: <643C78AD-5169-4A06-BE51-3F1765F90A3E@macports.org>

On Jan 19, 2009, at 06:22, Chris Janton wrote:

> checking for NEEDED... configure: error: Package requirements  
> (pthread-stubs xau >= 0.99.2) were not met:
>
> No package 'pthread-stubs' found

Ok, I added xorg-libpthread-stubs to libxcb's build time dependencies.


> --->  Configuring freetype
> Error: Target org.macports.configure returned: configure failure:  
> shell command " cd "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_print_freetype/work/freetype-2.3.8" && ./ 
> configure --prefix=/opt/local --with-old-mac-fonts " returned error 2
> Command output: builds/toplevel.mk:43: *** FreeType's build system  
> needs a Make program which supports $(value).  Stop.
>
> Error: Unable to upgrade port: 1
> admin at x:admin:140 $

You'll need to provide more output than that.  What were the lines  
before the failure?  Do you have gmake installed?


What are the others that you mention in the subject?

From lanceboyle at qwest.net  Mon Jan 19 11:36:52 2009
From: lanceboyle at qwest.net (Jerry)
Date: Mon, 19 Jan 2009 12:36:52 -0700
Subject: maxima installation failed
In-Reply-To: <20090119115056.GA17265@marco.fz-rossendorf.de>
References: <20090119115056.GA17265@marco.fz-rossendorf.de>
Message-ID: <BBDEC271-8FE3-4B91-86DC-28B9B63ACEC1@qwest.net>

This looks like it could be related to the problem that I reported on  
the list on January 9, 2009. Ryan filed a ticket at that time: http:// 
trac.macports.org/ticket/17925. Hope this gets cleared up.

Jerry


On Jan 19, 2009, at 4:50 AM, Joerg van den Hoff wrote:

> dear all,
>
> my attempt to install `maxima' failed with
>
> =================CUT=================================
>  sudo port install maxima
>  --->  Building recode
>  --->  Staging recode into destroot
>  --->  Packaging tgz archive for recode 3.6_3
>  --->  Installing recode @3.6_3
>  --->  Activating recode @3.6_3
>  --->  Cleaning recode
>  --->  Fetching sbcl
>  --->  Attempting to fetch sbcl-1.0.24-source.tar.bz2 from
>  http://dfn.dl.sourceforge.net/sbcl
>  --->  Attempting to fetch sbcl-1.0.22-powerpc-darwin-binary.tar.bz2
>  from http://dfn.dl.sourceforge.net/sbcl
>  --->  Verifying checksum(s) for sbcl
>  --->  Extracting sbcl
>  --->  Applying patches to sbcl
>  --->  Configuring sbcl
>  --->  Building sbcl
>  Error: Target org.macports.build returned: shell command "unset
>  LD_PREBIND && unset LD_PREBIND_ALLOW_OVERLAP && sh make.sh
>  "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ 
> sbcl/work/sbcl-1.0.22-powerpc-darwin/src/runtime/sbcl
>  --core
>  /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ 
> sbcl/work/sbcl-1.0.22-powerpc-darwin/output/sbcl.core
>  --disable-debugger --sysinit /dev/null --userinit /dev/null" "  
> returned
>  error 1
>  Command output: //starting build: Mon Jan 19 12:42:39 CET 2009
>  //SBCL_XC_HOST="/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ 
> sbcl/work/sbcl-1.0.22-powerpc-darwin/src/runtime/sbcl
>  --core
>  /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ 
> sbcl/work/sbcl-1.0.22-powerpc-darwin/output/sbcl.core
>  --disable-debugger --sysinit /dev/null --userinit /dev/null"
>  //entering make-config.sh
>  //ensuring the existence of output/ directory
>  //initializing
>  /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ 
> sbcl/work/sbcl-1.0.24/local-target-features.lisp-expr
>  //guessing default target CPU architecture from host architecture
>  //setting up CPU-architecture-dependent information
>  sbcl_arch="ppc"
>  //setting up symlink src/compiler/target
>  //setting up symlink src/assembly/target
>  //setting up symlink src/compiler/assembly
>  //setting up OS-dependent information
>  //finishing
>  /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ 
> sbcl/work/sbcl-1.0.24/local-target-features.lisp-expr
>  /in canonicalize-whitespace-1
>  /$*=./customize-target-features.lisp ./local-target-features.lisp- 
> expr
>  ./tests/test-status.lisp-expr ./contrib/sb-bsd-sockets/foo.c
>  ./contrib/sb-posix/foo.c ./src/runtime/runtime.c
>  ./src/runtime/target-arch-os.h ./src/runtime/target-arch.h
>  ./src/runtime/target-lispregs.h ./src/runtime/target-os.h
>  /$scratchfilename=/tmp/canonicalize-whitespace-1.17069.tmp
>  //entering make-host-1.sh
>  //building cross-compiler, and doing first genesis
>  make-host-1.sh: line 31: 17083 Bus error               $SBCL_XC_HOST
>  <make-host-1.lisp
> =================CUT=================================
>
> i.e. a bus error during `sbcl' install.
>
> this is on a PPC G5, MacOSX 10.4.11 and with `port' version 1.700
>
> any help would be appreciated.
>
> regards,
>
> joerg
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>


From HerrPoetry at HailMail.net  Mon Jan 19 12:12:53 2009
From: HerrPoetry at HailMail.net (Mark)
Date: Mon, 19 Jan 2009 15:12:53 -0500
Subject: Error building nspr during Gnome-Control Center install
In-Reply-To: <4974BB86.9000904@macports.org>
References: <49741C90.4050602@HailMail.net>	<44505526-923A-4D06-AD95-33498942267C@macports.org>
	<4974ABC9.3050006@HailMail.net> <4974BB86.9000904@macports.org>
Message-ID: <4974DEC5.8080205@HailMail.net>

Joshua Root wrote:
> Mark wrote:
>   
>> Back to nspr. I did what you said. Here's the entire nspr build phase
>> output:
>>     
> [...]
>   
>> /usr/include/mach/host_info.h:70:26: error: /usr/include/mach/machine.h: Input/output error
>>     
>
> That looks fairly dire.
>
> - Josh
>   

Is there anything I can do about it? Put more locks on my house? Buy 
small handgun? /Any/thing computer-related? I'm mostly a newbie: I know 
that ".h" signifies header file, but I couldn't read through one with 
any comprehension.

- Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090119/894ae033/attachment.html>

From jmr at macports.org  Mon Jan 19 12:33:07 2009
From: jmr at macports.org (Joshua Root)
Date: Tue, 20 Jan 2009 07:33:07 +1100
Subject: Error building nspr during Gnome-Control Center install
In-Reply-To: <4974DEC5.8080205@HailMail.net>
References: <49741C90.4050602@HailMail.net>	<44505526-923A-4D06-AD95-33498942267C@macports.org>
	<4974ABC9.3050006@HailMail.net> <4974BB86.9000904@macports.org>
	<4974DEC5.8080205@HailMail.net>
Message-ID: <4974E383.2070108@macports.org>

Mark wrote:
> Joshua Root wrote:
>> Mark wrote:
>>   
>>> Back to nspr. I did what you said. Here's the entire nspr build phase
>>> output:
>>>     
>> [...]
>>   
>>> /usr/include/mach/host_info.h:70:26: error: /usr/include/mach/machine.h: Input/output error
>>>     
>>
>> That looks fairly dire.
>>
>> - Josh
>>   
> 
> Is there anything I can do about it? Put more locks on my house? Buy
> small handgun? /Any/thing computer-related? I'm mostly a newbie: I know
> that ".h" signifies header file, but I couldn't read through one with
> any comprehension.

The particular file isn't important, what's worrying is the
"Input/output error", which means the OS could not read it. Worst case,
it means you have a corrupted filesystem or your hard drive is dying.

Can you open that file at all?

- Josh

From face at CentosPrime.COM  Mon Jan 19 12:38:38 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Mon, 19 Jan 2009 13:38:38 -0700
Subject: error upgrading freetype / xorg-libxcb et al on Panther
In-Reply-To: <643C78AD-5169-4A06-BE51-3F1765F90A3E@macports.org>
References: <4F182005-88CD-4673-8CB5-FCEC0B8DA8D0@centosprime.com>
	<643C78AD-5169-4A06-BE51-3F1765F90A3E@macports.org>
Message-ID: <F96368F9-9995-44A4-8DE8-A23A43B075CD@CentosPrime.COM>

On 2009-01-19 , at 11:53 , Jeremy Huddleston wrote:

>> --->  Configuring freetype
>> Error: Target org.macports.configure returned: configure failure:  
>> shell command " cd "/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_print_freetype/work/freetype-2.3.8"  
>> && ./configure --prefix=/opt/local --with-old-mac-fonts " returned  
>> error 2
>> Command output: builds/toplevel.mk:43: *** FreeType's build system  
>> needs a Make program which supports $(value).  Stop.
>>
>> Error: Unable to upgrade port: 1
>> admin at x:admin:140 $
>
> You'll need to provide more output than that.  What were the lines  
> before the failure?  Do you have gmake installed?


admin at x:admin:130 $ which gmake
/opt/local/bin/gmake
admin at x:admin:131 $ gmake --version
GNU Make 3.81
Copyright (C) 2006  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.

This program built for powerpc-apple-darwin7.9.0


admin at x:admin:129 $ sudo port upgrade outdated
Password:
--->  Configuring freetype
Error: Target org.macports.configure returned: configure failure:  
shell command " cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_print_freetype/work/freetype-2.3.8" && ./ 
configure --prefix=/opt/local --with-old-mac-fonts " returned error 2
Command output: builds/toplevel.mk:43: *** FreeType's build system  
needs a Make program which supports $(value).  Stop.

Error: Unable to upgrade port: 1



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



From HerrPoetry at HailMail.net  Mon Jan 19 13:28:30 2009
From: HerrPoetry at HailMail.net (Mark)
Date: Mon, 19 Jan 2009 16:28:30 -0500
Subject: Error building nspr during Gnome-Control Center install
In-Reply-To: <4974E383.2070108@macports.org>
References: <49741C90.4050602@HailMail.net>	<44505526-923A-4D06-AD95-33498942267C@macports.org>
	<4974ABC9.3050006@HailMail.net> <4974BB86.9000904@macports.org>
	<4974DEC5.8080205@HailMail.net> <4974E383.2070108@macports.org>
Message-ID: <4974F07E.1090604@HailMail.net>

Joshua Root wrote:
> Mark wrote:
>   
>> Joshua Root wrote:
>>     
>>> Mark wrote:
>>>   
>>>       
>>>> Back to nspr. I did what you said. Here's the entire nspr build phase
>>>> output:
>>>>         
>>> [...]
>>>   
>>>       
>>>> /usr/include/mach/host_info.h:70:26: error: /usr/include/mach/machine.h: Input/output error
>>>>         
>>> That looks fairly dire.
>>>
>>> - Josh
>>>       
>> Is there anything I can do about it? Put more locks on my house? Buy
>> small handgun? /Any/thing computer-related? I'm mostly a newbie: I know
>> that ".h" signifies header file, but I couldn't read through one with
>> any comprehension.
>>     
>
> The particular file isn't important, what's worrying is the
> "Input/output error", which means the OS could not read it. Worst case,
> it means you have a corrupted filesystem or your hard drive is dying.
>
> Can you open that file at all?
>
> - Josh

Oh, !#^% me. I'm taking deep breaths. Okay, a preliminary question: what 
low-impact tool(s) can I use to check out my file system & hard drive? 
(I'm doing a full backup as I type.)

Back to machine.h. When I select the file in Path Finder (which I use 
instead of Finder), I cannot get a preview of the text. However, I can 
open the file in BBedit. But notice what happens to the text at line 202 
(I added line numbers just for your reading convenience) -- I'm guessing 
that kind of goop is not normal? Here's the entire machine.h file:

> 1 /*
> 2  * Copyright (c) 2000-2007 Apple Computer, Inc. All rights reserved.
> 3  *
> 4  * @APPLE_OSREFERENCE_LICENSE_HEADER_START@
> 5  *
> 6  * This file contains Original Code and/or Modifications of Original 
> Code
> 7  * as defined in and that are subject to the Apple Public Source License
> 8  * Version 2.0 (the 'License'). You may not use this file except in
> 9  * compliance with the License. The rights granted to you under the 
> License
> 10  * may not be used to create, or enable the creation or 
> redistribution of,
> 11  * unlawful or unlicensed copies of an Apple operating system, or to
> 12  * circumvent, violate, or enable the circumvention or violation 
> of, any
> 13  * terms of an Apple operating system software license agreement.
> 14  *
> 15  * Please obtain a copy of the License at
> 16  * http://www.opensource.apple.com/apsl/ and read it before using 
> this file.
> 17  *
> 18  * The Original Code and all software distributed under the License are
> 19  * distributed on an 'AS IS' basis, WITHOUT WARRANTY OF ANY KIND, 
> EITHER
> 20  * EXPRESS OR IMPLIED, AND APPLE HEREBY DISCLAIMS ALL SUCH WARRANTIES,
> 21  * INCLUDING WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY,
> 22  * FITNESS FOR A PARTICULAR PURPOSE, QUIET ENJOYMENT OR 
> NON-INFRINGEMENT.
> 23  * Please see the License for the specific language governing 
> rights and
> 24  * limitations under the License.
> 25  *
> 26  * @APPLE_OSREFERENCE_LICENSE_HEADER_END@
> 27  */
> 28 /*
> 29  * Mach Operating System
> 30  * Copyright (c) 1991,1990,1989,1988,1987 Carnegie Mellon University
> 31  * All Rights Reserved.
> 32  *
> 33  * Permission to use, copy, modify and distribute this software and its
> 34  * documentation is hereby granted, provided that both the copyright
> 35  * notice and this permission notice appear in all copies of the
> 36  * software, derivative works or modified versions, and any portions
> 37  * thereof, and that both notices appear in supporting documentation.
> 38  *
> 39  * CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
> 40  * CONDITION.  CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR
> 41  * ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
> 42  *
> 43  * Carnegie Mellon requests users of this software to return to
> 44  *
> 45  *  Software Distribution Coordinator  or  
> Software.Distribution at CS.CMU.EDU
> 46  *  School of Computer Science
> 47  *  Carnegie Mellon University
> 48  *  Pittsburgh PA 15213-3890
> 49  *
> 50  * any improvements or extensions that they make and grant Carnegie 
> Mellon
> 51  * the rights to redistribute these changes.
> 52  */
> 53 /*    File:    machine.h
> 54  *    Author:    Avadis Tevanian, Jr.
> 55  *    Date:    1986
> 56  *
> 57  *    Machine independent machine abstraction.
> 58  */
> 59
> 60 #ifndef    _MACH_MACHINE_H_
> 61 #define _MACH_MACHINE_H_
> 62
> 63 #include <stdint.h>
> 64 #include <mach/machine/vm_types.h>
> 65 #include <mach/boolean.h>
> 66
> 67 typedef integer_t    cpu_type_t;
> 68 typedef integer_t    cpu_subtype_t;
> 69 typedef integer_t    cpu_threadtype_t;
> 70
> 71 #define CPU_STATE_MAX        4
> 72
> 73 #define CPU_STATE_USER        0
> 74 #define CPU_STATE_SYSTEM    1
> 75 #define CPU_STATE_IDLE        2
> 76 #define CPU_STATE_NICE        3
> 77
> 78
> 79
> 80 /*
> 81  * Capability bits used in the definition of cpu_type.
> 82  */
> 83 #define    CPU_ARCH_MASK    0xff000000        /* mask for 
> architecture bits */
> 84 #define CPU_ARCH_ABI64    0x01000000        /* 64 bit ABI */
> 85
> 86 /*
> 87  *    Machine types known by all.
> 88  */
> 89  
> 90 #define CPU_TYPE_ANY        ((cpu_type_t) -1)
> 91
> 92 #define CPU_TYPE_VAX        ((cpu_type_t) 1)
> 93 /* skip                ((cpu_type_t) 2)    */
> 94 /* skip                ((cpu_type_t) 3)    */
> 95 /* skip                ((cpu_type_t) 4)    */
> 96 /* skip                ((cpu_type_t) 5)    */
> 97 #define    CPU_TYPE_MC680x0    ((cpu_type_t) 6)
> 98 #define CPU_TYPE_X86        ((cpu_type_t) 7)
> 99 #define CPU_TYPE_I386        CPU_TYPE_X86        /* compatibility */
> 100 #define    CPU_TYPE_X86_64        (CPU_TYPE_X86 | CPU_ARCH_ABI64)
> 101
> 102 /* skip CPU_TYPE_MIPS        ((cpu_type_t) 8)    */
> 103 /* skip             ((cpu_type_t) 9)    */
> 104 #define CPU_TYPE_MC98000    ((cpu_type_t) 10)
> 105 #define CPU_TYPE_HPPA           ((cpu_type_t) 11)
> 106 #define CPU_TYPE_ARM        ((cpu_type_t) 12)
> 107 #define CPU_TYPE_MC88000    ((cpu_type_t) 13)
> 108 #define CPU_TYPE_SPARC        ((cpu_type_t) 14)
> 109 #define CPU_TYPE_I860        ((cpu_type_t) 15)
> 110 /* skip    CPU_TYPE_ALPHA        ((cpu_type_t) 16)    */
> 111 /* skip                ((cpu_type_t) 17)    */
> 112 #define CPU_TYPE_POWERPC        ((cpu_type_t) 18)
> 113 #define CPU_TYPE_POWERPC64        (CPU_TYPE_POWERPC | CPU_ARCH_ABI64)
> 114
> 115 /*
> 116  *    Machine subtypes (these are defined here, instead of in a 
> machine
> 117  *    dependent directory, so that any program can get all definitions
> 118  *    regardless of where is it compiled).
> 119  */
> 120
> 121 /*
> 122  * Capability bits used in the definition of cpu_subtype.
> 123  */
> 124 #define CPU_SUBTYPE_MASK    0xff000000    /* mask for feature flags */
> 125 #define CPU_SUBTYPE_LIB64    0x80000000    /* 64 bit libraries */
> 126
> 127
> 128 /*
> 129  *    Object files that are hand-crafted to run on any
> 130  *    implementation of an architecture are tagged with
> 131  *    CPU_SUBTYPE_MULTIPLE.  This functions essentially the same as
> 132  *    the "ALL" subtype of an architecture except that it allows us
> 133  *    to easily find object files that may need to be modified
> 134  *    whenever a new implementation of an architecture comes out.
> 135  *
> 136  *    It is the responsibility of the implementor to make sure the
> 137  *    software handles unsupported implementations elegantly.
> 138  */
> 139 #define    CPU_SUBTYPE_MULTIPLE        ((cpu_subtype_t) -1)
> 140 #define CPU_SUBTYPE_LITTLE_ENDIAN    ((cpu_subtype_t) 0)
> 141 #define CPU_SUBTYPE_BIG_ENDIAN        ((cpu_subtype_t) 1)
> 142
> 143 /*
> 144  *     Machine threadtypes.
> 145  *     This is none - not defined - for most machine types/subtypes.
> 146  */
> 147 #define CPU_THREADTYPE_NONE        ((cpu_threadtype_t) 0)
> 148
> 149 /*
> 150  *    VAX subtypes (these do *not* necessary conform to the actual cpu
> 151  *    ID assigned by DEC available via the SID register).
> 152  */
> 153
> 154 #define    CPU_SUBTYPE_VAX_ALL    ((cpu_subtype_t) 0)
> 155 #define CPU_SUBTYPE_VAX780    ((cpu_subtype_t) 1)
> 156 #define CPU_SUBTYPE_VAX785    ((cpu_subtype_t) 2)
> 157 #define CPU_SUBTYPE_VAX750    ((cpu_subtype_t) 3)
> 158 #define CPU_SUBTYPE_VAX730    ((cpu_subtype_t) 4)
> 159 #define CPU_SUBTYPE_UVAXI    ((cpu_subtype_t) 5)
> 160 #define CPU_SUBTYPE_UVAXII    ((cpu_subtype_t) 6)
> 161 #define CPU_SUBTYPE_VAX8200    ((cpu_subtype_t) 7)
> 162 #define CPU_SUBTYPE_VAX8500    ((cpu_subtype_t) 8)
> 163 #define CPU_SUBTYPE_VAX8600    ((cpu_subtype_t) 9)
> 164 #define CPU_SUBTYPE_VAX8650    ((cpu_subtype_t) 10)
> 165 #define CPU_SUBTYPE_VAX8800    ((cpu_subtype_t) 11)
> 166 #define CPU_SUBTYPE_UVAXIII    ((cpu_subtype_t) 12)
> 167
> 168 /*
> 169  *     680x0 subtypes
> 170  *
> 171  * The subtype definitions here are unusual for historical reasons.
> 172  * NeXT used to consider 68030 code as generic 68000 code.  For
> 173  * backwards compatability:
> 174  *
> 175  *    CPU_SUBTYPE_MC68030 symbol has been preserved for source code
> 176  *    compatability.
> 177  *
> 178  *    CPU_SUBTYPE_MC680x0_ALL has been defined to be the same
> 179  *    subtype as CPU_SUBTYPE_MC68030 for binary comatability.
> 180  *
> 181  *    CPU_SUBTYPE_MC68030_ONLY has been added to allow new object
> 182  *    files to be tagged as containing 68030-specific instructions.
> 183  */
> 184
> 185 #define    CPU_SUBTYPE_MC680x0_ALL        ((cpu_subtype_t) 1)
> 186 #define CPU_SUBTYPE_MC68030        ((cpu_subtype_t) 1) /* compat */
> 187 #define CPU_SUBTYPE_MC68040        ((cpu_subtype_t) 2)
> 188 #define    CPU_SUBTYPE_MC68030_ONLY    ((cpu_subtype_t) 3)
> 189
> 190 /*
> 191  *    I386 subtypes
> 192  */
> 193
> 194 #define CPU_SUBTYPE_INTEL(f, m)    ((cpu_subtype_t) (f) + ((m) << 4))
> 195
> 196 #define    CPU_SUBTYPE_I386_ALL            CPU_SUBTYPE_INTEL(3, 0)
> 197 #define CPU_SUBTYPE_386                    CPU_SUBTYPE_INTEL(3, 0)
> 198 #define CPU_SUBTYPE_486                    CPU_SUBTYPE_INTEL(4, 0)
> 199 #define CPU_SUBTYPE_486SX                CPU_SUBTYPE_INTEL(4, 8)   
>  // 8 << 4 = 128
> 200 #define CPU_SUBTYPE_586                    CPU_SUBTYPE_INTEL(5, 0)
> 201 #define CPU_SUBTYPE_PENT    CPU_SUBTYPE_INTEL(5, 0)
> 202 #define CPU_SUBTYPE_PENTPRO    CPU_SUBTYPE_INTEL(6, 
> 1)c?w???    ??}(F*???rs??j?V??
> 203 I????O?a???S???Y?5
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090119/ed7611c2/attachment.html>

From blb at macports.org  Mon Jan 19 13:31:47 2009
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 19 Jan 2009 14:31:47 -0700
Subject: freetype fails to build on Panther
In-Reply-To: <580177FE-097C-4496-AF73-752D9B8C9AB3@centosprime.com>
References: <580177FE-097C-4496-AF73-752D9B8C9AB3@centosprime.com>
Message-ID: <20090119213147.GE785@ninagal.withay.com>

On Mon, Jan 19, 2009 at 06:08:15AM -0700, Chris Janton said:
> MacPorts 1.7 - Panther
>
> --->  Fetching freetype
> --->  Attempting to fetch freetype-2.3.8.tar.bz2 from http://download.savannah.gnu.org/releases/freetype/
> --->  Attempting to fetch freetype-2.3.8.tar.bz2 from http://downloads.sourceforge.net/freetype
> --->  Attempting to fetch freetype-doc-2.3.8.tar.bz2 from http://download.savannah.gnu.org/releases/freetype/
> --->  Verifying checksum(s) for freetype
> --->  Extracting freetype
> --->  Applying patches to freetype
> --->  Configuring freetype
> Error: Target org.macports.configure returned: configure failure: shell 
> command " cd "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_print_freetype/work/freetype-2.3.8" && ./ 
> configure --prefix=/opt/local --with-old-mac-fonts " returned error 2
> Command output: builds/toplevel.mk:43: *** FreeType's build system needs a 
> Make program which supports $(value).  Stop.

10.3's make wasn't gnumake right?  Maybe freetype needs a 'build.type gnu'
so freetype is told to use that instead?

Bryan


>
> Error: Unable to upgrade port: 1
>
> 8)
> ----------------------------------
> Chris Janton  - face at CentosPrime dot COM
> Netminder for Opus1.COM
>

From whodoctor at gmail.com  Mon Jan 19 05:03:21 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Mon, 19 Jan 2009 08:03:21 -0500
Subject: Error after trying to upgrade installed
In-Reply-To: <B57CF743-6D2D-4794-9306-F694A6B37EEC@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<4b75340e0901181818l1de65967q1fd1610143d49830@mail.gmail.com>
	<944BC661-E2A4-4AE2-B54D-CD6EAADD610F@macports.org>
	<4b75340e0901181839u4a5cf010uaca6a02c8911f648@mail.gmail.com>
	<D2F037C9-308C-4EBE-B70C-1950D85C9511@macports.org>
	<4b75340e0901181850tab7b12encfb467be8e4f1a41@mail.gmail.com>
	<B57CF743-6D2D-4794-9306-F694A6B37EEC@macports.org>
Message-ID: <4b75340e0901190503i6e8b1106mf5e447b01ff68cbd@mail.gmail.com>

On Sun, Jan 18, 2009 at 10:04 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Jan 18, 2009, at 20:50, Doctor Who wrote:
>
>> On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt  wrote:
>>>
>>
>>> Try:
>>>
>>> sudo port install gettext
>>
>> Thanks...that worked.
>
> Great!
>
>> Should I now try to update with 'sudo port upgrade outdated'?
>
> Sure, go ahead. I know there have been a lot of X11/xorg-related changes
> lately, and I haven't tried them myself yet, so good luck!
>
>

Just wanted to report back that the update proceeded without issues.

Thanks.

From jeremyhu at macports.org  Mon Jan 19 14:01:09 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Mon, 19 Jan 2009 14:01:09 -0800
Subject: error upgrading freetype / xorg-libxcb et al on Panther
In-Reply-To: <F96368F9-9995-44A4-8DE8-A23A43B075CD@CentosPrime.COM>
References: <4F182005-88CD-4673-8CB5-FCEC0B8DA8D0@centosprime.com>
	<643C78AD-5169-4A06-BE51-3F1765F90A3E@macports.org>
	<F96368F9-9995-44A4-8DE8-A23A43B075CD@CentosPrime.COM>
Message-ID: <EE8D6E03-2924-426D-A26B-BEBBEC662993@macports.org>


On Jan 19, 2009, at 12:38, Chris Janton wrote:

> On 2009-01-19 , at 11:53 , Jeremy Huddleston wrote:
>>
>>
>> You'll need to provide more output than that.  What were the lines  
>> before the failure?  Do you have gmake installed?
>
> admin at x:admin:129 $ sudo port upgrade outdated

Yes, try doing 'sudo port -v upgrade outdated' and send us the verbose  
messages... 

From LenoreHorner at sbcglobal.net  Mon Jan 19 14:14:37 2009
From: LenoreHorner at sbcglobal.net (Lenore Horner)
Date: Mon, 19 Jan 2009 16:14:37 -0600
Subject: upgrading Gnucash
Message-ID: <1CBDC8F8-E155-4C2C-861A-07AB17E81890@sbcglobal.net>

Gnucash ate a bunch of data _again_ (I've asked the Gnucash user group  
about that, so far without much luck) so I thought perhaps I should  
upgrade my current installation to the latest release.

I had the following installed.
gnucash @2.2.7_2+without_hbci+without_ofx+without_quotes (active)

I upgraded with the following command.
sudo port upgrade gnucash +without_hbci+without_ofx+without_quotes

Now it's installing gwenhywfar which I thought wasn't supposed to be  
needed with all the withouts I installed with.  In fact gwenhywfar was  
inactive under the previous installation.  Does upgrading kill off the  
options?  Does the new version no longer have those options?

gwenhywfar @3.5.1_0
(It was there because I misspelled before and had without_hcbi and  
then inactivated that and installed as above.)

Lenore

From jmr at macports.org  Mon Jan 19 14:39:14 2009
From: jmr at macports.org (Joshua Root)
Date: Tue, 20 Jan 2009 09:39:14 +1100
Subject: upgrading Gnucash
In-Reply-To: <1CBDC8F8-E155-4C2C-861A-07AB17E81890@sbcglobal.net>
References: <1CBDC8F8-E155-4C2C-861A-07AB17E81890@sbcglobal.net>
Message-ID: <49750112.2010508@macports.org>

Lenore Horner wrote:
> Gnucash ate a bunch of data _again_ (I've asked the Gnucash user group
> about that, so far without much luck) so I thought perhaps I should
> upgrade my current installation to the latest release.
> 
> I had the following installed.
> gnucash @2.2.7_2+without_hbci+without_ofx+without_quotes (active)
> 
> I upgraded with the following command.
> sudo port upgrade gnucash +without_hbci+without_ofx+without_quotes
> 
> Now it's installing gwenhywfar which I thought wasn't supposed to be
> needed with all the withouts I installed with.  In fact gwenhywfar was
> inactive under the previous installation.  Does upgrading kill off the
> options?  Does the new version no longer have those options?
> 
> gwenhywfar @3.5.1_0
> (It was there because I misspelled before and had without_hcbi and then
> inactivated that and installed as above.)

You're hitting this bug: <http://trac.macports.org/ticket/8221> (fixed
in trunk). Uninstall/install instead of using upgrade will work around it.

You don't have to specify the same variants when you upgrade BTW, your
selected variants will be preserved.

- Josh

From LenoreHorner at sbcglobal.net  Mon Jan 19 14:44:28 2009
From: LenoreHorner at sbcglobal.net (Lenore Horner)
Date: Mon, 19 Jan 2009 16:44:28 -0600
Subject: Gnucash upgrade ignores variants
Message-ID: <F2F1C83F-39A0-4F5C-A4FD-1BC0CD9D2E0A@sbcglobal.net>

The gnucash upgrade is definitely ignoring variants.

old version
gnucash @2.2.7_2+without_hbci+without_ofx+without_quotes (active)

upgrade command
sudo port upgrade gnucash +without_hbci+without_ofx+without_quotes

...
--->  Fetching libofx
--->  Verifying checksum(s) for libofx
--->  Extracting libofx
--->  Configuring libofx
--->  Building libofx
--->  Staging libofx into destroot
--->  Installing libofx @0.8.3_0
--->  Activating libofx @0.8.3_0
--->  Cleaning libofx
--->  Fetching qt3
--->  Verifying checksum(s) for qt3
--->  Extracting qt3
--->  Configuring qt3
--->  Building qt3
killed because it's clearly doing the wrong thing.

A) How do I get the upgrade without all the extra stuff?

I'm guessing my current installation is toast now because a  
significant fraction of its dependencies have been upgraded.

Lenore

From ryandesign at macports.org  Mon Jan 19 15:21:05 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 19 Jan 2009 17:21:05 -0600
Subject: Error building nspr during Gnome-Control Center install
In-Reply-To: <4974ABC9.3050006@HailMail.net>
References: <49741C90.4050602@HailMail.net>
	<44505526-923A-4D06-AD95-33498942267C@macports.org>
	<4974ABC9.3050006@HailMail.net>
Message-ID: <9D8BBD83-C6FC-4C0E-A038-730E389846A3@macports.org>

On Jan 19, 2009, at 10:35, Mark wrote:

> Ryan Schmidt wrote:
>
>> On Jan 19, 2009, at 00:24, Mark wrote:
>>
>>> Could someone help me interpret this error? I tried installing  
>>> Gnome-Control-Center, and early it bombed.
>>
>> I'm not sure we're seeing the first error here. MacPorts only  
>> shows you the last 40 (I think) lines of error. Try "sudo port  
>> clean nspr" and then "sudo port -d install nspr" and see what the  
>> first error is. That may tell us more.

[snip]

> /usr/bin/gcc-4.0 -o prlink.o -c    -I/opt/local/include -O2 -Wmost - 
> fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 - 
> DDARWIN=1 -DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 - 
> DHAVE_LCHOWN=1 -DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS - 
> UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr  
> -I../../../pr/include -I../../../pr/include/private -I/Developer/ 
> Headers/FlatCarbon  prlink.c
> In file included from /usr/include/mach/mach_types.h:80,
>                  from /System/Library/Frameworks/IOKit.framework/ 
> Headers/IOKitLib.h:41,
>                  from /System/Library/Frameworks/ 
> DiskArbitration.framework/Headers/DADisk.h:28,
>                  from /System/Library/Frameworks/ 
> CoreServices.framework/Frameworks/CarbonCore.framework/Headers/ 
> Files.h:62,
>                  from /System/Library/Frameworks/ 
> CoreServices.framework/Frameworks/CarbonCore.framework/Headers/ 
> Components.h:32,
>                  from /System/Library/Frameworks/ 
> CoreServices.framework/Frameworks/CarbonCore.framework/Headers/ 
> CarbonCore.h:85,
>                  from /System/Library/Frameworks/ 
> CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20,
>                  from /System/Library/Frameworks/ 
> CoreServices.framework/Headers/CoreServices.h:21,
>                  from /Developer/Headers/FlatCarbon/CodeFragments.h:1,
>                  from prlink.c:48:
> /usr/include/mach/host_info.h:70:26: error: /usr/include/mach/ 
> machine.h: Input/output error

There's the first error. It can't open /usr/include/mach/machine.h  
due to an input/output error. That usually only occurs if your disk  
is failing! Can you open this file manually? I expect not. You should  
back up your data immediately, preferrably onto a second set of  
backup media so that you don't overwrite a previous backup, in case  
the disk is already gone. I'm not sure how best to test the disk, but  
you can try verifying the disk in Disk Utility and also check its  
S.M.A.R.T. status at the bottom of the Disk Utility window. A healthy  
disk should have the status "verified".



From ryandesign at macports.org  Mon Jan 19 15:26:12 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 19 Jan 2009 17:26:12 -0600
Subject: Steps to ensure compatibility between fink and macports
In-Reply-To: <7675454e0901190801q669586a2hc7473e960342dc15@mail.gmail.com>
References: <391652.36615.qm@web51909.mail.re2.yahoo.com>
	<AFC4F6B4-AC32-46FA-BE76-2F1780E7C3C7@macports.org>
	<7675454e0901190801q669586a2hc7473e960342dc15@mail.gmail.com>
Message-ID: <04352A2A-9380-447A-9FB3-7F5CEBC30921@macports.org>

On Jan 19, 2009, at 10:01, Shreevatsa R wrote:

> On Sat, Jan 17, 2009 at 3:58 AM, Ryan Schmidt wrote:
>
>> On Jan 17, 2009, at 01:12, David T. wrote:
>>
>>> Has anyone got a clear set of steps and guidelines for me to
>>> follow to try using macports without messing up fink?
>>
>> Rename fink's /sw directory to something else. That should ensure  
>> it does
>> not interfere with MacPorts.
>>
>> You should only use software installed via one package manager at  
>> a time --
>> either Fink, or MacPorts, not both.
>
> Er, I don't think this is true. You don't have to do *anything* to
> ensure Fink and MacPorts don't intefere with each other. They are both
> designed to not interfere with the rest of the system, so if they do
> interfere with each other, it's a bug in one of them.
>
> In my experience (and that of others) it works perfectly to use both
> Fink and MacPorts simultaneously; installing packages from whichever
> of the two happens to have a working version. (But do care about what
> you do to your environment variables like $PATH: Fink's
> /sw/bin/init.sh is a bit heavy-handed.)
>
> Of course I'm just a user and don't know very much of the internals of
> either, so maybe someone can correct me if I'm wrong.

There are software packages out there, for which we have ports in  
MacPorts, that will, in an attempt to find the dependent libraries  
they need, always look in /opt/local and /sw to find them. So if you  
have the same library installed with both Fink and MacPorts, it's  
possible a MacPorts port will link with the library from Fink, or the  
other way around. To prevent that, we would have to know which  
software packages do this and patch them in MacPorts to not do that.  
Since we do not know which software packages do this, the safe course  
of action is to explain that it is not supported to use Fink and  
MacPorts at the same time. "Not supported" means you can still do it,  
but we will not necessarily help you with problems you encounter as a  
result.




From ryandesign at macports.org  Mon Jan 19 15:35:40 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 19 Jan 2009 17:35:40 -0600
Subject: freetype fails to build on Panther
In-Reply-To: <20090119213147.GE785@ninagal.withay.com>
References: <580177FE-097C-4496-AF73-752D9B8C9AB3@centosprime.com>
	<20090119213147.GE785@ninagal.withay.com>
Message-ID: <386C9819-50C1-47AA-A8B3-8FE4DA1414F1@macports.org>

On Jan 19, 2009, at 15:31, Bryan Blackburn wrote:

> On Mon, Jan 19, 2009 at 06:08:15AM -0700, Chris Janton said:
>
>> MacPorts 1.7 - Panther
>>
>> --->  Fetching freetype
>> --->  Attempting to fetch freetype-2.3.8.tar.bz2 from http:// 
>> download.savannah.gnu.org/releases/freetype/
>> --->  Attempting to fetch freetype-2.3.8.tar.bz2 from http:// 
>> downloads.sourceforge.net/freetype
>> --->  Attempting to fetch freetype-doc-2.3.8.tar.bz2 from http:// 
>> download.savannah.gnu.org/releases/freetype/
>> --->  Verifying checksum(s) for freetype
>> --->  Extracting freetype
>> --->  Applying patches to freetype
>> --->  Configuring freetype
>> Error: Target org.macports.configure returned: configure failure:  
>> shell
>> command " cd "/opt/local/var/macports/build/
>> _opt_local_var_macports_sources_rsync
>> .macports.org_release_ports_print_freetype/work/freetype-2.3.8" && ./
>> configure --prefix=/opt/local --with-old-mac-fonts " returned error 2
>> Command output: builds/toplevel.mk:43: *** FreeType's build system  
>> needs a
>> Make program which supports $(value).  Stop.
>
> 10.3's make wasn't gnumake right?  Maybe freetype needs a  
> 'build.type gnu'
> so freetype is told to use that instead?

I'll look into it in a moment. I filed a ticket here:

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



From ryandesign at macports.org  Mon Jan 19 15:38:17 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 19 Jan 2009 17:38:17 -0600
Subject: error upgrading freetype / xorg-libxcb et al on Panther
In-Reply-To: <EE8D6E03-2924-426D-A26B-BEBBEC662993@macports.org>
References: <4F182005-88CD-4673-8CB5-FCEC0B8DA8D0@centosprime.com>
	<643C78AD-5169-4A06-BE51-3F1765F90A3E@macports.org>
	<F96368F9-9995-44A4-8DE8-A23A43B075CD@CentosPrime.COM>
	<EE8D6E03-2924-426D-A26B-BEBBEC662993@macports.org>
Message-ID: <84456A33-CFA6-469E-BC02-2A77196F36EF@macports.org>


On Jan 19, 2009, at 16:01, Jeremy Huddleston wrote:

> On Jan 19, 2009, at 12:38, Chris Janton wrote:
>
>> On 2009-01-19 , at 11:53 , Jeremy Huddleston wrote:
>>
>>> You'll need to provide more output than that.  What were the  
>>> lines before the failure?  Do you have gmake installed?
>>
>> admin at x:admin:129 $ sudo port upgrade outdated
>
> Yes, try doing 'sudo port -v upgrade outdated' and send us the  
> verbose messages...

I imagine Panther's make is just too old and I'll have to add a  
dependency on MacPorts GNU make. I'll handle this in a moment, and  
ask for more info in the ticket if I need it.

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



From HerrPoetry at HailMail.net  Mon Jan 19 16:04:08 2009
From: HerrPoetry at HailMail.net (Mark)
Date: Mon, 19 Jan 2009 19:04:08 -0500
Subject: Error building nspr during Gnome-Control Center install
In-Reply-To: <9D8BBD83-C6FC-4C0E-A038-730E389846A3@macports.org>
References: <49741C90.4050602@HailMail.net>
	<44505526-923A-4D06-AD95-33498942267C@macports.org>
	<4974ABC9.3050006@HailMail.net>
	<9D8BBD83-C6FC-4C0E-A038-730E389846A3@macports.org>
Message-ID: <497514F8.7000805@HailMail.net>

Ryan Schmidt wrote:
> On Jan 19, 2009, at 10:35, Mark wrote:
>
>> Ryan Schmidt wrote:
>>
>>> On Jan 19, 2009, at 00:24, Mark wrote:
>>>
>>>> Could someone help me interpret this error? I tried installing 
>>>> Gnome-Control-Center, and early it bombed.
>>>
>>> I'm not sure we're seeing the first error here. MacPorts only shows 
>>> you the last 40 (I think) lines of error. Try "sudo port clean nspr" 
>>> and then "sudo port -d install nspr" and see what the first error 
>>> is. That may tell us more.
> [snip]
>
>> /usr/bin/gcc-4.0 -o prlink.o -c    -I/opt/local/include -O2 -Wmost 
>> -fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 
>> -DDARWIN=1 -DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 
>> -DHAVE_LCHOWN=1 -DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS 
>> -UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/nspr 
>> -I../../../pr/include -I../../../pr/include/private 
>> -I/Developer/Headers/FlatCarbon  prlink.c
>> In file included from /usr/include/mach/mach_types.h:80,
>>                  from 
>> /System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:41,
>>                  from 
>> /System/Library/Frameworks/DiskArbitration.framework/Headers/DADisk.h:28, 
>>
>>                  from 
>> /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Files.h:62, 
>>
>>                  from 
>> /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Components.h:32, 
>>
>>                  from 
>> /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:85, 
>>
>>                  from 
>> /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20, 
>>
>>                  from 
>> /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:21, 
>>
>>                  from /Developer/Headers/FlatCarbon/CodeFragments.h:1,
>>                  from prlink.c:48:
>> /usr/include/mach/host_info.h:70:26: error: 
>> /usr/include/mach/machine.h: Input/output error
>
> There's the first error. It can't open /usr/include/mach/machine.h due 
> to an input/output error. That usually only occurs if your disk is 
> failing! Can you open this file manually? I expect not. You should 
> back up your data immediately, preferrably onto a second set of backup 
> media so that you don't overwrite a previous backup, in case the disk 
> is already gone. I'm not sure how best to test the disk, but you can 
> try verifying the disk in Disk Utility and also check its S.M.A.R.T. 
> status at the bottom of the Disk Utility window. A healthy disk should 
> have the status "verified".

I am happy to report that

    (a)  my hard drive hasn't crashed yet, and that Disk Utility says 
S.M.A.R.T. status is "verified" (though I will run some tests on the drive).

    (b) I found a backed-up copy of /usr/include/mach/machine.h, deleted 
the garbled file and replaced it with the backup. I then ran "sudo port 
clean nspr" followed by "sudo port -d install nspr" -- and the 
installation completed without any hiccups.

I'm now going to try resuming the installation of gnome-control-center. 
Wish me luck, and thanks for your help!

- Mark

From shreevatsa.public at gmail.com  Mon Jan 19 16:16:55 2009
From: shreevatsa.public at gmail.com (Shreevatsa R)
Date: Mon, 19 Jan 2009 19:16:55 -0500
Subject: Steps to ensure compatibility between fink and macports
In-Reply-To: <04352A2A-9380-447A-9FB3-7F5CEBC30921@macports.org>
References: <391652.36615.qm@web51909.mail.re2.yahoo.com>
	<AFC4F6B4-AC32-46FA-BE76-2F1780E7C3C7@macports.org>
	<7675454e0901190801q669586a2hc7473e960342dc15@mail.gmail.com>
	<04352A2A-9380-447A-9FB3-7F5CEBC30921@macports.org>
Message-ID: <7675454e0901191616s5281bddenbca336fe7dd8483d@mail.gmail.com>

On Mon, Jan 19, 2009 at 6:26 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Jan 19, 2009, at 10:01, Shreevatsa R wrote:
>
>> On Sat, Jan 17, 2009 at 3:58 AM, Ryan Schmidt wrote:
>>
>>> On Jan 17, 2009, at 01:12, David T. wrote:
>>>
>>>> Has anyone got a clear set of steps and guidelines for me to
>>>> follow to try using macports without messing up fink?
>>>
>>> Rename fink's /sw directory to something else. That should ensure it does
>>> not interfere with MacPorts.
>>>
>>> You should only use software installed via one package manager at a time
>>> --
>>> either Fink, or MacPorts, not both.
>>
>> Er, I don't think this is true. You don't have to do *anything* to
>> ensure Fink and MacPorts don't intefere with each other. They are both
>> designed to not interfere with the rest of the system, so if they do
>> interfere with each other, it's a bug in one of them.
>>
>> In my experience (and that of others) it works perfectly to use both
>> Fink and MacPorts simultaneously; installing packages from whichever
>> of the two happens to have a working version. (But do care about what
>> you do to your environment variables like $PATH: Fink's
>> /sw/bin/init.sh is a bit heavy-handed.)
>>
>> Of course I'm just a user and don't know very much of the internals of
>> either, so maybe someone can correct me if I'm wrong.
>
> There are software packages out there, for which we have ports in MacPorts,
> that will, in an attempt to find the dependent libraries they need, always
> look in /opt/local and /sw to find them. So if you have the same library
> installed with both Fink and MacPorts, it's possible a MacPorts port will
> link with the library from Fink, or the other way around. To prevent that,
> we would have to know which software packages do this and patch them in
> MacPorts to not do that. Since we do not know which software packages do
> this, the safe course of action is to explain that it is not supported to
> use Fink and MacPorts at the same time. "Not supported" means you can still
> do it, but we will not necessarily help you with problems you encounter as a
> result.

I understand; that makes sense. It seems the same as the /usr/local
problem again, with packages not being prevented from looking in
places they shouldn't be looking, and potentially causing problems as
a result. I guess it's worth investigating chroot and -nostdinc. The
latter has been around since gcc 2.7.2.2 at least, which is more than
10 years old: it should be safe to use.

[Technically, it should be considered a bug if a port isn't patched to
prevent its looking in /sw. Some ports do handle this, e.g.
http://trac.macports.org/browser/trunk/dports/net/pidgin/files/patch-configure.ac.diff
:-)]

Wrt the original question: I think MacPorts never installs anything
outside /opt/local, so while a existing Fink installation can result
in broken MacPorts ports, using MacPorts will not affect the
functioning Fink installation itself. Is this correct?

From rswwalker at gmail.com  Mon Jan 19 16:27:15 2009
From: rswwalker at gmail.com (Ross Walker)
Date: Mon, 19 Jan 2009 19:27:15 -0500
Subject: Error building nspr during Gnome-Control Center install
In-Reply-To: <497514F8.7000805@HailMail.net>
References: <49741C90.4050602@HailMail.net>
	<44505526-923A-4D06-AD95-33498942267C@macports.org>
	<4974ABC9.3050006@HailMail.net>
	<9D8BBD83-C6FC-4C0E-A038-730E389846A3@macports.org>
	<497514F8.7000805@HailMail.net>
Message-ID: <F28F6C9C-B66E-4BC0-9046-7FF627569618@gmail.com>


On Jan 19, 2009, at 7:04 PM, Mark <HerrPoetry at HailMail.net> wrote:

> Ryan Schmidt wrote:
>> On Jan 19, 2009, at 10:35, Mark wrote:
>>
>>> Ryan Schmidt wrote:
>>>
>>>> On Jan 19, 2009, at 00:24, Mark wrote:
>>>>
>>>>> Could someone help me interpret this error? I tried installing  
>>>>> Gnome-Control-Center, and early it bombed.
>>>>
>>>> I'm not sure we're seeing the first error here. MacPorts only  
>>>> shows you the last 40 (I think) lines of error. Try "sudo port  
>>>> clean nspr" and then "sudo port -d install nspr" and see what the  
>>>> first error is. That may tell us more.
>> [snip]
>>
>>> /usr/bin/gcc-4.0 -o prlink.o -c    -I/opt/local/include -O2 -Wmost  
>>> -fno-common -pthread -fPIC  -UDEBUG  -DNDEBUG=1 -DXP_UNIX=1 - 
>>> DDARWIN=1 -DHAVE_BSD_FLOCK=1 -DHAVE_SOCKLEN_T=1 -DXP_MACOSX=1 - 
>>> DHAVE_LCHOWN=1 -DHAVE_STRERROR=1  -DFORCE_PR_LOG -D_PR_PTHREADS - 
>>> UHAVE_CVAR_BUILT_ON_SEM -D_NSPR_BUILD_ -I../../../dist/include/ 
>>> nspr -I../../../pr/include -I../../../pr/include/private -I/ 
>>> Developer/Headers/FlatCarbon  prlink.c
>>> In file included from /usr/include/mach/mach_types.h:80,
>>>                 from /System/Library/Frameworks/IOKit.framework/ 
>>> Headers/IOKitLib.h:41,
>>>                 from /System/Library/Frameworks/ 
>>> DiskArbitration.framework/Headers/DADisk.h:28,
>>>                 from /System/Library/Frameworks/ 
>>> CoreServices.framework/Frameworks/CarbonCore.framework/Headers/ 
>>> Files.h:62,
>>>                 from /System/Library/Frameworks/ 
>>> CoreServices.framework/Frameworks/CarbonCore.framework/Headers/ 
>>> Components.h:32,
>>>                 from /System/Library/Frameworks/ 
>>> CoreServices.framework/Frameworks/CarbonCore.framework/Headers/ 
>>> CarbonCore.h:85,
>>>                 from /System/Library/Frameworks/ 
>>> CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20,
>>>                 from /System/Library/Frameworks/ 
>>> CoreServices.framework/Headers/CoreServices.h:21,
>>>                 from /Developer/Headers/FlatCarbon/CodeFragments.h: 
>>> 1,
>>>                 from prlink.c:48:
>>> /usr/include/mach/host_info.h:70:26: error: /usr/include/mach/ 
>>> machine.h: Input/output error
>>
>> There's the first error. It can't open /usr/include/mach/machine.h  
>> due to an input/output error. That usually only occurs if your disk  
>> is failing! Can you open this file manually? I expect not. You  
>> should back up your data immediately, preferrably onto a second set  
>> of backup media so that you don't overwrite a previous backup, in  
>> case the disk is already gone. I'm not sure how best to test the  
>> disk, but you can try verifying the disk in Disk Utility and also  
>> check its S.M.A.R.T. status at the bottom of the Disk Utility  
>> window. A healthy disk should have the status "verified".
>
> I am happy to report that
>
>   (a)  my hard drive hasn't crashed yet, and that Disk Utility says  
> S.M.A.R.T. status is "verified" (though I will run some tests on the  
> drive).
>
>   (b) I found a backed-up copy of /usr/include/mach/machine.h,  
> deleted the garbled file and replaced it with the backup. I then ran  
> "sudo port clean nspr" followed by "sudo port -d install nspr" --  
> and the installation completed without any hiccups.
>
> I'm now going to try resuming the installation of gnome-control- 
> center. Wish me luck, and thanks for your help!

It would be a good idea to run a file system check in 'Disk Utility'  
and fix any problems it finds either with fsck itself or with 'Disk  
Doctor'.

Just cause a disk isn't failing doesn't mean there isn't file system  
corruption due to multiple unclean shutdowns.

-Ross


From cedayiv at gmail.com  Mon Jan 19 16:38:18 2009
From: cedayiv at gmail.com (Charles Day)
Date: Mon, 19 Jan 2009 16:38:18 -0800
Subject: Gnucash upgrade ignores variants
In-Reply-To: <F2F1C83F-39A0-4F5C-A4FD-1BC0CD9D2E0A@sbcglobal.net>
References: <F2F1C83F-39A0-4F5C-A4FD-1BC0CD9D2E0A@sbcglobal.net>
Message-ID: <1d6843d80901191638h2505134dyb1d5a918a1a70df1@mail.gmail.com>

On Mon, Jan 19, 2009 at 2:44 PM, Lenore Horner
<LenoreHorner at sbcglobal.net>wrote:

> The gnucash upgrade is definitely ignoring variants.
>
> old version
> gnucash @2.2.7_2+without_hbci+without_ofx+without_quotes (active)
>
> upgrade command
> sudo port upgrade gnucash +without_hbci+without_ofx+without_quotes
>

Shouldn't there be spaces between the variants in your command? (I know the
existing version is always shown without spaces, but I don't know if the
command allows that.)


>
> ...
> --->  Fetching libofx
> --->  Verifying checksum(s) for libofx
> --->  Extracting libofx
> --->  Configuring libofx
> --->  Building libofx
> --->  Staging libofx into destroot
> --->  Installing libofx @0.8.3_0
> --->  Activating libofx @0.8.3_0
> --->  Cleaning libofx
> --->  Fetching qt3
> --->  Verifying checksum(s) for qt3
> --->  Extracting qt3
> --->  Configuring qt3
> --->  Building qt3
> killed because it's clearly doing the wrong thing.
>
> A) How do I get the upgrade without all the extra stuff?
>
> I'm guessing my current installation is toast now because a significant
> fraction of its dependencies have been upgraded.
>
> Lenore
> _______________________________________________
> 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/20090119/ee14d708/attachment.html>

From blb at macports.org  Mon Jan 19 16:41:16 2009
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 19 Jan 2009 17:41:16 -0700
Subject: Steps to ensure compatibility between fink and macports
In-Reply-To: <7675454e0901191616s5281bddenbca336fe7dd8483d@mail.gmail.com>
References: <391652.36615.qm@web51909.mail.re2.yahoo.com>
	<AFC4F6B4-AC32-46FA-BE76-2F1780E7C3C7@macports.org>
	<7675454e0901190801q669586a2hc7473e960342dc15@mail.gmail.com>
	<04352A2A-9380-447A-9FB3-7F5CEBC30921@macports.org>
	<7675454e0901191616s5281bddenbca336fe7dd8483d@mail.gmail.com>
Message-ID: <20090120004116.GH785@ninagal.withay.com>

On Mon, Jan 19, 2009 at 07:16:55PM -0500, Shreevatsa R said:
[...]
> 
> I understand; that makes sense. It seems the same as the /usr/local
> problem again, with packages not being prevented from looking in
> places they shouldn't be looking, and potentially causing problems as
> a result. I guess it's worth investigating chroot and -nostdinc. The
> latter has been around since gcc 2.7.2.2 at least, which is more than
> 10 years old: it should be safe to use.

I'd love to see MacPorts make use of things like nostdinc, but then we have
to re-add the true system-level stuff, and that is more than just
/usr/include.  You also have stuff in /usr/include/gcc and various places in
/usr/lib/gcc.  Is there a way to consistently find the proper locations for
a given gcc, on all platforms MacPorts claims to support?

Bryan

[...]

From talklists at newgeo.com  Mon Jan 19 17:11:44 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 19 Jan 2009 17:11:44 -0800
Subject: p5 modules, get me started on one
Message-ID: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>

Hello, I need a little help.

File::ReadBackwards
If I start with this one, I can probably get the other 15 to work.

If I look at another p5 module, as a way to learn:

# $Id: Portfile 30247 2007-10-23 02:05:08Z redacted at macports.org $
PortSystem 1.0
PortGroup perl5 1.0

perl5.setup             Pod-Escapes 1.04
maintainers             nomaintainer
description             for resolving Pod E<...> sequences
long_description        This module provides things that are useful in \
                                         decoding Pod E<...>  
sequences. Presumably, it should \
                                         be used only by Pod parsers  
and/or formatters.
checksums               md5 00ea2e0d2e84ed98517a4616708b68d3
platforms               darwin


So there is not a heck of a lot in there.
I did my best to get past these instructions:
http://guide.macports.org/#development.local-repositories
I have /Users/me/macports/

My sources file looks like this:
file:///Users/me/macports
rsync://rsync.macports.org/release/ports/ [default]

While I did do some tests, I am confused as to naming.  If I want to  
make a port for File::ReadBackward, what is my path to /Users/me/ 
macports ?
I think it will be /Users/macports/ports/p5(maybe)/file-readbackwards

Given the above example port file, where is it being told to  
download?  I can not seem to locate a file, so I must be  
misunderstanding this `sudo find /opt/ -name "perl5.setup"`
--
Scott


From talklists at newgeo.com  Mon Jan 19 17:19:43 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 19 Jan 2009 17:19:43 -0800
Subject: pf-net-dns
Message-ID: <FADF5247-E4DF-4825-A146-C352EAB62168@newgeo.com>

Stumped on this one, and rather than a line of terminal to fix it, can  
someone run me through what is going on, why does sudo port install  
xyz not work in most all cases for me?

me at macbook:~/Desktop/ $sudo port install p5-net-dns
--->  Activating p5-mime-base64 @3.07_0
Error: Target org.macports.activate returned: Image error: /opt/local/ 
share/man/man3/MIME::Base64.3pm.gz is being used by the active perl5.8  
port.  Please deactivate this port first, or use the -f flag to force  
the activation.
Error: The following dependencies failed to build: p5-mime-base64 p5- 
net-ip
Error: Status 1 encountered during processing.
me at macbook:~/Desktop/ $sudo port -f activate p5-net-dns
Error: port activate failed: Registry error: p5-net-dns not registered  
as installed.
me at macbook:~/Desktop/ $sudo port -f install p5-net-dns
--->  Installing p5-mime-base64 @3.07_0
Error: Target org.macports.install returned: Registry error: p5-mime- 
base64 @3.07_0 already registered as installed.  Please uninstall it  
first.
Error: The following dependencies failed to build: p5-mime-base64 p5- 
net-ip
Error: Status 1 encountered during processing.
me at macbook:~/Desktop/ $sudo port -f uninstall p5-net-dns
Error: port uninstall failed: Registry error: p5-net-dns not  
registered as installed.
me at macbook:~/Desktop/ $sudo port clean p5-net-dns
--->  Cleaning p5-net-dns
me at macbook:~/Desktop/ $sudo port install p5-net-dns
--->  Activating p5-mime-base64 @3.07_0
Error: Target org.macports.activate returned: Image error: /opt/local/ 
share/man/man3/MIME::Base64.3pm.gz is being used by the active perl5.8  
port.  Please deactivate this port first, or use the -f flag to force  
the activation.
Error: The following dependencies failed to build: p5-mime-base64 p5- 
net-ip
Error: Status 1 encountered during processing.
me at macbook:~/Desktop/ $sudo port -f deactivate p5-net-dns
Error: port deactivate failed: Registry error: p5-net-dns not  
registered as installed & active.
me at macbook:~/Desktop/ $sudo port -f uninstall p5-net-dns
Error: port uninstall failed: Registry error: p5-net-dns not  
registered as installed.
me at macbook:~/Desktop/ $

--
Scott


From blb at macports.org  Mon Jan 19 17:31:50 2009
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 19 Jan 2009 18:31:50 -0700
Subject: p5 modules, get me started on one
In-Reply-To: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
Message-ID: <20090120013150.GI785@ninagal.withay.com>

On Mon, Jan 19, 2009 at 05:11:44PM -0800, Scott Haneda said:
> Hello, I need a little help.
>
> File::ReadBackwards
> If I start with this one, I can probably get the other 15 to work.
>
> If I look at another p5 module, as a way to learn:
>
> # $Id: Portfile 30247 2007-10-23 02:05:08Z redacted at macports.org $
> PortSystem 1.0
> PortGroup perl5 1.0

This is enacting group code (specifically version 1.0 of the perl5 group
code [1]).

>
> perl5.setup             Pod-Escapes 1.04

This is where the magic happens for a perl module port.  Basically you'll
want to do:

perl5.setup   File::ReadBackwards 1.04

(since 1.04 appears to be the current version).  This then causes several
bits for the port to be set automatically:  name (to p5-file-readbackwards),
version, info on how to download from CPAN, and how to build and install it.
The rest of the info in this port is descriptive and the checksums.

> maintainers             nomaintainer
> description             for resolving Pod E<...> sequences
> long_description        This module provides things that are useful in \
>                                         decoding Pod E<...> sequences. 
> Presumably, it should \
>                                         be used only by Pod parsers  
> and/or formatters.
> checksums               md5 00ea2e0d2e84ed98517a4616708b68d3
> platforms               darwin
>
>
> So there is not a heck of a lot in there.
> I did my best to get past these instructions:
> http://guide.macports.org/#development.local-repositories
> I have /Users/me/macports/
>
> My sources file looks like this:
> file:///Users/me/macports
> rsync://rsync.macports.org/release/ports/ [default]
>
> While I did do some tests, I am confused as to naming.  If I want to make 
> a port for File::ReadBackward, what is my path to /Users/me/macports ?
> I think it will be /Users/macports/ports/p5(maybe)/file-readbackwards

You'll want to have this under /Users/me/macports/perl/p5-file-readbackwards
as this is in the perl category, and as mentioned above, will be named
p5-file-readbackwards.

Bryan

[1] - <http://guide.macports.org/#reference.portgroup.perl>

>
> Given the above example port file, where is it being told to download?  I 
> can not seem to locate a file, so I must be misunderstanding this `sudo 
> find /opt/ -name "perl5.setup"`
> --
> Scott

From blb at macports.org  Mon Jan 19 17:34:43 2009
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 19 Jan 2009 18:34:43 -0700
Subject: pf-net-dns
In-Reply-To: <FADF5247-E4DF-4825-A146-C352EAB62168@newgeo.com>
References: <FADF5247-E4DF-4825-A146-C352EAB62168@newgeo.com>
Message-ID: <20090120013443.GJ785@ninagal.withay.com>

On Mon, Jan 19, 2009 at 05:19:43PM -0800, Scott Haneda said:
> Stumped on this one, and rather than a line of terminal to fix it, can  
> someone run me through what is going on, why does sudo port install xyz 
> not work in most all cases for me?
>
> me at macbook:~/Desktop/ $sudo port install p5-net-dns
> --->  Activating p5-mime-base64 @3.07_0
> Error: Target org.macports.activate returned: Image error: /opt/local/ 
> share/man/man3/MIME::Base64.3pm.gz is being used by the active perl5.8  
> port.  Please deactivate this port first, or use the -f flag to force the 
> activation.
> Error: The following dependencies failed to build: p5-mime-base64 p5- 
> net-ip
> Error: Status 1 encountered during processing.

This is the quite-annoying #12710:

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

> me at macbook:~/Desktop/ $sudo port -f activate p5-net-dns
> Error: port activate failed: Registry error: p5-net-dns not registered as 
> installed.

Note that the failure is occurring during the install of p5-mime-base64
(which is a dependency needed for p5-net-dns) hence p5-net-dns is not yet
installed; you have to force p5-mime-base64's activation

$ sudo port -f activate p5-mime-base64

Also, this may happen with other perl modules which conflict with the base
perl5.8 port...

Bryan

[...]
>
> --
> Scott
>

From talklists at newgeo.com  Mon Jan 19 17:41:16 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 19 Jan 2009 17:41:16 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <20090120013150.GI785@ninagal.withay.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
Message-ID: <981B7CCC-70A1-4E89-8BBB-F05714F511BA@newgeo.com>

On Jan 19, 2009, at 5:31 PM, Bryan Blackburn wrote:

>>
>> perl5.setup             Pod-Escapes 1.04
>
> This is where the magic happens for a perl module port.  Basically  
> you'll
> want to do:
>
> perl5.setup   File::ReadBackwards 1.04
>
> (since 1.04 appears to be the current version).  This then causes  
> several
> bits for the port to be set automatically:  name (to p5-file- 
> readbackwards),
> version, info on how to download from CPAN, and how to build and  
> install it.
> The rest of the info in this port is descriptive and the checksums.


What is the best way to get the checksum, just download it and md5 it  
in the shell?

From talklists at newgeo.com  Mon Jan 19 17:45:56 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 19 Jan 2009 17:45:56 -0800
Subject: pf-net-dns
In-Reply-To: <20090120013443.GJ785@ninagal.withay.com>
References: <FADF5247-E4DF-4825-A146-C352EAB62168@newgeo.com>
	<20090120013443.GJ785@ninagal.withay.com>
Message-ID: <8CBC66DB-A7D7-478B-87C4-59514C957990@newgeo.com>

On Jan 19, 2009, at 5:34 PM, Bryan Blackburn wrote:

> This is the quite-annoying #12710:
>
> <http://trac.macports.org/ticket/12710>


16 months old. I am trying to push more and more people to use ports  
so I can get them to use assp, as a simple way to get it up and running.

is this an issue for all users more or less?  If so, I am curious, why  
is it at 16 months, is it a problem solving the way to solve this  
issue, and there is no real clean way to solve it?

Thanks for any pointers on this issue.
--
Scott

From whodoctor at gmail.com  Mon Jan 19 17:54:36 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Mon, 19 Jan 2009 20:54:36 -0500
Subject: locate not working
Message-ID: <4b75340e0901191754v57314797m607e7688ac3ef026@mail.gmail.com>

I installed 'locate' from MacPorts not realizing that it was part of
my Leopard install.  The locate command was working for me at one
point, but now it returns no results. :-(

tbook:~ who$ locate locate
tbook:~ who$ locate bash
tbook:~ who$ locate ls

I have run 'sudo /etc/periodic/weekly/310.locate' to update the
database for locate.  The 'locate' being run is:

tbook:~ who$ which locate
/opt/local/bin/locate

which appears to be the MacPorts version.  How can I get either this
locate working or start using Leopard's locate command by default?

Thanks.

From talklists at newgeo.com  Mon Jan 19 17:54:53 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 19 Jan 2009 17:54:53 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <20090120013150.GI785@ninagal.withay.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
Message-ID: <651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>

On Jan 19, 2009, at 5:31 PM, Bryan Blackburn wrote:

> On Mon, Jan 19, 2009 at 05:11:44PM -0800, Scott Haneda said:
>> Hello, I need a little help.

> You'll want to have this under /Users/me/macports/perl/p5-file- 
> readbackwards
> as this is in the perl category, and as mentioned above, will be named
> p5-file-readbackwards.
>
> [1] - <http://guide.macports.org/#reference.portgroup.perl>
>
>> Given the above example port file, where is it being told to  
>> download?  I
>> can not seem to locate a file, so I must be misunderstanding this  
>> `sudo
>> find /opt/ -name "perl5.setup"`


/Users/me/macports/perl

-rw-r--r--  1 me  wheel    0 Jan 19 17:50 PortIndex
-rw-r--r--  1 me  staff  284 Jan 19 17:50 p5-file-readbackward

$portindex
Creating software index in /Users/me/macports/perl

Total number of ports parsed:	0
Ports successfully parsed:	0	
Ports failed:			0

cat p5-file-readbackward
# $Id$
PortSystem 1.0
PortGroup perl5 1.0

perl5.setup             File::ReadBackwards 1.04
maintainers             nomaintainer
description             test of port file readbackwards
long_description        This module provides things that are useful
platforms               darwin

* How come other ports of this nature do not use :: and use - ?

sudo port install p5-file-readbackwards
Warning: Can't open index file for source: file:///Users/me/macports
Error: Port p5-file-readbackwards not found

Any suggestions?
--
Scott


From TimLee at rochester.rr.com  Mon Jan 19 18:05:00 2009
From: TimLee at rochester.rr.com (Timothy Lee)
Date: Mon, 19 Jan 2009 21:05:00 -0500
Subject: Liger: It's pretty much my favorite animal
Message-ID: <DB2FFC75-D2F5-4E92-A711-0747A48A8A0E@rochester.rr.com>

Hello all!

New to this list. I've been working on porting Musicbrainz Picard to  
the mac (dependencies fulfilled by MacPorts) over the past few weeks.  
While working through some of the issues, a few questions popped up:

1. I'm building on Leopard (i386) but was hoping to target Tiger. What  
(universal-ity aside) are the proper steps to compile everything on my  
Leopard install for Tiger? Is it simply setting universal_target to  
10.4 in my macports.conf ? Or are there other variables that need to  
be set? What packages do I need to have installed (the 10.4 SDK) ?

2. For building a Tiger Macports on my Leopard, should I simply  
download the 10.4 package installer and life will be fine?

Thanks a bunch for any help!

Tim Lee

From blb at macports.org  Mon Jan 19 18:45:28 2009
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 19 Jan 2009 19:45:28 -0700
Subject: locate not working
In-Reply-To: <4b75340e0901191754v57314797m607e7688ac3ef026@mail.gmail.com>
References: <4b75340e0901191754v57314797m607e7688ac3ef026@mail.gmail.com>
Message-ID: <20090120024528.GL785@ninagal.withay.com>

On Mon, Jan 19, 2009 at 08:54:36PM -0500, Doctor Who said:
> I installed 'locate' from MacPorts not realizing that it was part of
> my Leopard install.  The locate command was working for me at one
> point, but now it returns no results. :-(
> 
> tbook:~ who$ locate locate
> tbook:~ who$ locate bash
> tbook:~ who$ locate ls
> 
> I have run 'sudo /etc/periodic/weekly/310.locate' to update the
> database for locate.  The 'locate' being run is:
> 
> tbook:~ who$ which locate
> /opt/local/bin/locate
> 
> which appears to be the MacPorts version.  How can I get either this
> locate working or start using Leopard's locate command by default?

If '/usr/bin/locate bash' works then it's simply a path issue, and the
simplest fix would be to just uninstall that port; note that I see a port
'slocate' but none just called locate, so if that isn't it you can use 'port
provides /opt/local/bin/locate' to find the port which installed it.

Bryan


> 
> Thanks.

From blb at macports.org  Mon Jan 19 18:46:39 2009
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 19 Jan 2009 19:46:39 -0700
Subject: p5 modules, get me started on one
In-Reply-To: <981B7CCC-70A1-4E89-8BBB-F05714F511BA@newgeo.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<981B7CCC-70A1-4E89-8BBB-F05714F511BA@newgeo.com>
Message-ID: <20090120024639.GM785@ninagal.withay.com>

On Mon, Jan 19, 2009 at 05:41:16PM -0800, Scott Haneda said:
> On Jan 19, 2009, at 5:31 PM, Bryan Blackburn wrote:
>
>>>
>>> perl5.setup             Pod-Escapes 1.04
>>
>> This is where the magic happens for a perl module port.  Basically  
>> you'll
>> want to do:
>>
>> perl5.setup   File::ReadBackwards 1.04
>>
>> (since 1.04 appears to be the current version).  This then causes  
>> several
>> bits for the port to be set automatically:  name (to p5-file- 
>> readbackwards),
>> version, info on how to download from CPAN, and how to build and  
>> install it.
>> The rest of the info in this port is descriptive and the checksums.
>
>
> What is the best way to get the checksum, just download it and md5 it in 
> the shell?

'port -d checksum' when you're in the port directory, it'll give all
relevate checksum values for the file it downloaded for the port.

Bryan


From ryandesign at macports.org  Mon Jan 19 18:49:34 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 19 Jan 2009 20:49:34 -0600
Subject: Liger: It's pretty much my favorite animal
In-Reply-To: <DB2FFC75-D2F5-4E92-A711-0747A48A8A0E@rochester.rr.com>
References: <DB2FFC75-D2F5-4E92-A711-0747A48A8A0E@rochester.rr.com>
Message-ID: <D8E43117-1EB6-4637-9B9D-7953863385A8@macports.org>


On Jan 19, 2009, at 20:05, Timothy Lee wrote:

> New to this list. I've been working on porting Musicbrainz Picard  
> to the mac (dependencies fulfilled by MacPorts) over the past few  
> weeks. While working through some of the issues, a few questions  
> popped up:
>
> 1. I'm building on Leopard (i386) but was hoping to target Tiger.  
> What (universal-ity aside) are the proper steps to compile  
> everything on my Leopard install for Tiger? Is it simply setting  
> universal_target to 10.4 in my macports.conf ? Or are there other  
> variables that need to be set? What packages do I need to have  
> installed (the 10.4 SDK) ?
>
> 2. For building a Tiger Macports on my Leopard, should I simply  
> download the 10.4 package installer and life will be fine?


Welcome to MacPorts!

You could try setting universal_sdkroot to the 10.4u SDK,  
universal_target to 10.4 and x11prefix to /usr/X11R6. However,  
building on Leopard for Tiger, or any other such cross-compilation,  
is ill-tested in MacPorts and not supported. To truly test this, use  
a real Tiger machine. If you don't have one, perhaps someone else who  
does can test it for you.



From blb at macports.org  Mon Jan 19 18:50:55 2009
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 19 Jan 2009 19:50:55 -0700
Subject: p5 modules, get me started on one
In-Reply-To: <651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
Message-ID: <20090120025055.GN785@ninagal.withay.com>

On Mon, Jan 19, 2009 at 05:54:53PM -0800, Scott Haneda said:
> On Jan 19, 2009, at 5:31 PM, Bryan Blackburn wrote:
>
>> On Mon, Jan 19, 2009 at 05:11:44PM -0800, Scott Haneda said:
>>> Hello, I need a little help.
>
>> You'll want to have this under /Users/me/macports/perl/p5-file- 
>> readbackwards
>> as this is in the perl category, and as mentioned above, will be named
>> p5-file-readbackwards.
>>
>> [1] - <http://guide.macports.org/#reference.portgroup.perl>
>>
>>> Given the above example port file, where is it being told to  
>>> download?  I
>>> can not seem to locate a file, so I must be misunderstanding this  
>>> `sudo
>>> find /opt/ -name "perl5.setup"`
>
>
> /Users/me/macports/perl
>
> -rw-r--r--  1 me  wheel    0 Jan 19 17:50 PortIndex
> -rw-r--r--  1 me  staff  284 Jan 19 17:50 p5-file-readbackward
>
> $portindex
> Creating software index in /Users/me/macports/perl
>
> Total number of ports parsed:	0
> Ports successfully parsed:	0	
> Ports failed:			0
>
> cat p5-file-readbackward

Actually, p5-file-readbackward should be a directory, and what you have in
this file should actually be called Portfile; so you'd end up with
/Users/me/macports/perl/p5-file-readbackward/Portfile.

> # $Id$
> PortSystem 1.0
> PortGroup perl5 1.0
>
> perl5.setup             File::ReadBackwards 1.04
> maintainers             nomaintainer
> description             test of port file readbackwards
> long_description        This module provides things that are useful
> platforms               darwin
>
> * How come other ports of this nature do not use :: and use - ?

Oops, my mistake, that should be File-ReadBackwards instead of using the
'::'.

>
> sudo port install p5-file-readbackwards
> Warning: Can't open index file for source: file:///Users/me/macports
> Error: Port p5-file-readbackwards not found

When first developing a port it's simplest to be in the port's directory
(/Users/me/macports/perl/p5-file-readbackward in this case); that way you
can run the port commands without a port name, like

$ sudo port -d install
$ port lint

and any other commands.  This causes port to look in the current dir for a
Portfile, so you can be sure you're using what's there and not something
else.
Also, when developing a port, I seriously strongly suggest using -d so you
can watch what's going on.

Bryan


>
> Any suggestions?
> --
> Scott

From whodoctor at gmail.com  Mon Jan 19 19:41:54 2009
From: whodoctor at gmail.com (Doctor Who)
Date: Mon, 19 Jan 2009 22:41:54 -0500
Subject: locate not working
In-Reply-To: <20090120024528.GL785@ninagal.withay.com>
References: <4b75340e0901191754v57314797m607e7688ac3ef026@mail.gmail.com>
	<20090120024528.GL785@ninagal.withay.com>
Message-ID: <4b75340e0901191941tb61b5f1v5c0c24d347a106b4@mail.gmail.com>

On Mon, Jan 19, 2009 at 9:45 PM, Bryan Blackburn <blb at macports.org> wrote:
> On Mon, Jan 19, 2009 at 08:54:36PM -0500, Doctor Who said:
>> I installed 'locate' from MacPorts not realizing that it was part of
>> my Leopard install.  The locate command was working for me at one
>> point, but now it returns no results. :-(
>>
>> tbook:~ who$ locate locate
>> tbook:~ who$ locate bash
>> tbook:~ who$ locate ls
>>
>> I have run 'sudo /etc/periodic/weekly/310.locate' to update the
>> database for locate.  The 'locate' being run is:
>>
>> tbook:~ who$ which locate
>> /opt/local/bin/locate
>>
>> which appears to be the MacPorts version.  How can I get either this
>> locate working or start using Leopard's locate command by default?
>
> If '/usr/bin/locate bash' works then it's simply a path issue, and the
> simplest fix would be to just uninstall that port; note that I see a port
> 'slocate' but none just called locate, so if that isn't it you can use 'port
> provides /opt/local/bin/locate' to find the port which installed it.
>
> Bryan
>

Thanks, it was the findutils package and uninstalling it fixed the issue.

From sunfish62 at yahoo.com  Mon Jan 19 20:28:48 2009
From: sunfish62 at yahoo.com (David T.)
Date: Mon, 19 Jan 2009 20:28:48 -0800 (PST)
Subject: Steps to ensure compatibility between fink and macports
In-Reply-To: <7675454e0901191616s5281bddenbca336fe7dd8483d@mail.gmail.com>
Message-ID: <948404.90744.qm@web51905.mail.re2.yahoo.com>

Thanks all for the discussion. Ryan-- the point is not that MacPorts (or Fink, for that matter) installs in random places; each installs in their own directory hierarchy (/sw for fink, /opt/local for MacPorts). The problems arise if a package in one realm links to a library in the other--especially if the library versions and features differ. Which explains why the safe route is to move the "other" directory while using the first one. Now I understand how to play with fire.

David

--- On Mon, 1/19/09, Shreevatsa R <shreevatsa.public at gmail.com> wrote:

> From: Shreevatsa R <shreevatsa.public at gmail.com>
> Subject: Re: Steps to ensure compatibility between fink and macports
> To: "Ryan Schmidt" <ryandesign at macports.org>
> Cc: sunfish62 at yahoo.com, "MacPorts Users" <macports-users at lists.macosforge.org>
> Date: Monday, January 19, 2009, 4:16 PM
> On Mon, Jan 19, 2009 at 6:26 PM, Ryan Schmidt
> <ryandesign at macports.org> wrote:
> > On Jan 19, 2009, at 10:01, Shreevatsa R wrote:
> >
> >> On Sat, Jan 17, 2009 at 3:58 AM, Ryan Schmidt
> wrote:
> >>
> >>> On Jan 17, 2009, at 01:12, David T. wrote:
> >>>
> >>>> Has anyone got a clear set of steps and
> guidelines for me to
> >>>> follow to try using macports without
> messing up fink?
> >>>
> >>> Rename fink's /sw directory to something
> else. That should ensure it does
> >>> not interfere with MacPorts.
> >>>
> >>> You should only use software installed via one
> package manager at a time
> >>> --
> >>> either Fink, or MacPorts, not both.
> >>
> >> Er, I don't think this is true. You don't
> have to do *anything* to
> >> ensure Fink and MacPorts don't intefere with
> each other. They are both
> >> designed to not interfere with the rest of the
> system, so if they do
> >> interfere with each other, it's a bug in one
> of them.
> >>
> >> In my experience (and that of others) it works
> perfectly to use both
> >> Fink and MacPorts simultaneously; installing
> packages from whichever
> >> of the two happens to have a working version. (But
> do care about what
> >> you do to your environment variables like $PATH:
> Fink's
> >> /sw/bin/init.sh is a bit heavy-handed.)
> >>
> >> Of course I'm just a user and don't know
> very much of the internals of
> >> either, so maybe someone can correct me if I'm
> wrong.
> >
> > There are software packages out there, for which we
> have ports in MacPorts,
> > that will, in an attempt to find the dependent
> libraries they need, always
> > look in /opt/local and /sw to find them. So if you
> have the same library
> > installed with both Fink and MacPorts, it's
> possible a MacPorts port will
> > link with the library from Fink, or the other way
> around. To prevent that,
> > we would have to know which software packages do this
> and patch them in
> > MacPorts to not do that. Since we do not know which
> software packages do
> > this, the safe course of action is to explain that it
> is not supported to
> > use Fink and MacPorts at the same time. "Not
> supported" means you can still
> > do it, but we will not necessarily help you with
> problems you encounter as a
> > result.
> 
> I understand; that makes sense. It seems the same as the
> /usr/local
> problem again, with packages not being prevented from
> looking in
> places they shouldn't be looking, and potentially
> causing problems as
> a result. I guess it's worth investigating chroot and
> -nostdinc. The
> latter has been around since gcc 2.7.2.2 at least, which is
> more than
> 10 years old: it should be safe to use.
> 
> [Technically, it should be considered a bug if a port
> isn't patched to
> prevent its looking in /sw. Some ports do handle this, e.g.
> http://trac.macports.org/browser/trunk/dports/net/pidgin/files/patch-configure.ac.diff
> :-)]
> 
> Wrt the original question: I think MacPorts never installs
> anything
> outside /opt/local, so while a existing Fink installation
> can result
> in broken MacPorts ports, using MacPorts will not affect
> the
> functioning Fink installation itself. Is this correct?


      

From ryandesign at macports.org  Mon Jan 19 20:55:47 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 19 Jan 2009 22:55:47 -0600
Subject: Steps to ensure compatibility between fink and macports
In-Reply-To: <7675454e0901191616s5281bddenbca336fe7dd8483d@mail.gmail.com>
References: <391652.36615.qm@web51909.mail.re2.yahoo.com>
	<AFC4F6B4-AC32-46FA-BE76-2F1780E7C3C7@macports.org>
	<7675454e0901190801q669586a2hc7473e960342dc15@mail.gmail.com>
	<04352A2A-9380-447A-9FB3-7F5CEBC30921@macports.org>
	<7675454e0901191616s5281bddenbca336fe7dd8483d@mail.gmail.com>
Message-ID: <0F3D1770-3845-4376-AC63-5285A7557680@macports.org>

On Jan 19, 2009, at 18:16, Shreevatsa R wrote:

> On Mon, Jan 19, 2009 at 6:26 PM, Ryan Schmidt wrote:
>
>> There are software packages out there, for which we have ports in  
>> MacPorts,
>> that will, in an attempt to find the dependent libraries they  
>> need, always
>> look in /opt/local and /sw to find them. So if you have the same  
>> library
>> installed with both Fink and MacPorts, it's possible a MacPorts  
>> port will
>> link with the library from Fink, or the other way around. To  
>> prevent that,
>> we would have to know which software packages do this and patch  
>> them in
>> MacPorts to not do that. Since we do not know which software  
>> packages do
>> this, the safe course of action is to explain that it is not  
>> supported to
>> use Fink and MacPorts at the same time. "Not supported" means you  
>> can still
>> do it, but we will not necessarily help you with problems you  
>> encounter as a
>> result.
>
> I understand; that makes sense. It seems the same as the /usr/local
> problem again, with packages not being prevented from looking in
> places they shouldn't be looking, and potentially causing problems as
> a result. I guess it's worth investigating chroot and -nostdinc. The
> latter has been around since gcc 2.7.2.2 at least, which is more than
> 10 years old: it should be safe to use.
>
> [Technically, it should be considered a bug if a port isn't patched to
> prevent its looking in /sw. Some ports do handle this, e.g.
> http://trac.macports.org/browser/trunk/dports/net/pidgin/files/ 
> patch-configure.ac.diff
> :-)]

Probably. And you could file bugs against ports as you find them. But  
we might never find them all.

> Wrt the original question: I think MacPorts never installs anything
> outside /opt/local, so while a existing Fink installation can result
> in broken MacPorts ports, using MacPorts will not affect the
> functioning Fink installation itself. Is this correct?

I think that should be true, but of course I haven't tried it. But if  
a MacPorts port ever does write outside its intended area, it will  
print an error message to that effect.



From opendarwin.org at darkart.com  Mon Jan 19 21:23:21 2009
From: opendarwin.org at darkart.com (Eric Hall)
Date: Tue, 20 Jan 2009 05:23:21 +0000
Subject: pf-net-dns
In-Reply-To: <8CBC66DB-A7D7-478B-87C4-59514C957990@newgeo.com>
References: <FADF5247-E4DF-4825-A146-C352EAB62168@newgeo.com>
	<20090120013443.GJ785@ninagal.withay.com>
	<8CBC66DB-A7D7-478B-87C4-59514C957990@newgeo.com>
Message-ID: <20090120052321.GG1155@darkart.com>

On Mon, Jan 19, 2009 at 05:45:56PM -0800, Scott Haneda wrote:
> On Jan 19, 2009, at 5:34 PM, Bryan Blackburn wrote:
> 
> >This is the quite-annoying #12710:
> >
> ><http://trac.macports.org/ticket/12710>
> 
> 
> 16 months old. I am trying to push more and more people to use ports  
> so I can get them to use assp, as a simple way to get it up and running.
> 
> is this an issue for all users more or less?  If so, I am curious, why  
> is it at 16 months, is it a problem solving the way to solve this  
> issue, and there is no real clean way to solve it?
> 

	It hasn't been solved because nobody has taken the
time to do it.  I'm interested in fixing it by applying the
@INC inversion (ala FreeBSD ports), I've been stymied by
the lack of time to 1) go through all the various ideas
as to why this is or is not the "right" solution and
2) properly test it.
	The latter is the real kicker, while I use
perl quite a bit, I'm sure I don't have even half of
the possible test space covered.  The best thing I can
think of for testing coverage is to get a functional
@INC inverted perl Portfile done and make it available
for people to test with.  When I get that done, I'll
definitely get the word out.  If somebody else gets
it done first, I'll help test, etc.


		-eric


From talklists at newgeo.com  Mon Jan 19 21:33:46 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 19 Jan 2009 21:33:46 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <20090120025055.GN785@ninagal.withay.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
Message-ID: <E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>

Thanks still getting stuck though:

On Jan 19, 2009, at 6:50 PM, Bryan Blackburn wrote:

> When first developing a port it's simplest to be in the port's  
> directory
> (/Users/me/macports/perl/p5-file-readbackward in this case); that  
> way you
> can run the port commands without a port name, like
>
> $ sudo port -d install
> $ port lint
>
> and any other commands.  This causes port to look in the current dir  
> for a
> Portfile, so you can be sure you're using what's there and not  
> something
> else.
> Also, when developing a port, I seriously strongly suggest using -d  
> so you
> can watch what's going on.


Last login: Mon Jan 19 21:15:09 on ttys000
me at mes-macbook:~/ $cd ~/macports/
me at mes-macbook:~/ $cd ~/macports/perl/p5-file-readbackwards/
me at mes-macbook:~/macports/perl/p5-file-readbackwards/ $sudo port  
clean--->  Cleaning p5-file-readbackwards
me at mes-macbook:~/macports/perl/p5-file-readbackwards/ $sudo port -d  
install
DEBUG: Changing to port directory: /Users/me/macports/perl/p5-file- 
readbackwards
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: Using group file /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/_resources/port1.0/group/perl5-1.0.tcl
DEBUG: adding the default universal variant
DEBUG: Requested variant darwin is not provided by port p5-file- 
readbackwards.
DEBUG: Requested variant i386 is not provided by port p5-file- 
readbackwards.
DEBUG: Requested variant macosx is not provided by port p5-file- 
readbackwards.
DEBUG: Changing to port directory: /Users/me/macports/perl/p5-file- 
readbackwards
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: Using group file /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/_resources/port1.0/group/perl5-1.0.tcl
DEBUG: adding the default universal variant
DEBUG: Requested variant darwin is not provided by port p5-file- 
readbackwards.
DEBUG: Requested variant i386 is not provided by port p5-file- 
readbackwards.
DEBUG: Requested variant macosx is not provided by port p5-file- 
readbackwards.
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/lang/perl5
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 no' specified, so not adding the default  
universal variant
DEBUG: Requested variant darwin is not provided by port perl5.
DEBUG: Requested variant i386 is not provided by port perl5.
DEBUG: Requested variant macosx is not provided by port perl5.
DEBUG: Searching for dependency: perl5
DEBUG: Found Dependency: receipt exists for perl5
DEBUG: Executing org.macports.main (p5-file-readbackwards)
--->  Fetching p5-file-readbackwards
DEBUG: Executing org.macports.fetch (p5-file-readbackwards)
--->  Verifying checksum(s) for p5-file-readbackwards
DEBUG: Executing org.macports.checksum (p5-file-readbackwards)
--->  Checksumming File-ReadBackwards-1.04.tar.gz
DEBUG: Correct (md5) checksum for File-ReadBackwards-1.04.tar.gz
DEBUG: Correct (sha1) checksum for File-ReadBackwards-1.04.tar.gz
DEBUG: Correct (rmd160) checksum for File-ReadBackwards-1.04.tar.gz
--->  Extracting p5-file-readbackwards
DEBUG: Executing org.macports.extract (p5-file-readbackwards)
--->  Extracting File-ReadBackwards-1.04.tar.gz
DEBUG: setting option extract.args to /opt/local/var/macports/ 
distfiles/perl5/File-ReadBackwards-1.04.tar.gz
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
_Users_me_macports_perl_p5-file-readbackwards/work" && gzip -dc /opt/ 
local/var/macports/distfiles/perl5/File-ReadBackwards-1.04.tar.gz | / 
usr/bin/gnutar --no-same-owner -xf -'

gzip: /opt/local/var/macports/distfiles/perl5/File- 
ReadBackwards-1.04.tar.gz: not in gzip format
DEBUG: Executing org.macports.patch (p5-file-readbackwards)
--->  Configuring p5-file-readbackwards
DEBUG: Using compiler 'Mac OS X gcc 4.0'
DEBUG: Executing org.macports.configure (p5-file-readbackwards)
DEBUG: Environment: CFLAGS='-O2' CPPFLAGS='-I/opt/local/include'  
CXXFLAGS='-O2' MACOSX_DEPLOYMENT_TARGET='10.5' CPP='/usr/bin/cpp-4.0'  
CXX='/usr/bin/g++-4.0' F90FLAGS='-O2' LDFLAGS='-L/opt/local/lib'  
FCFLAGS='-O2' OBJC='/usr/bin/gcc-4.0' INSTALL='/usr/bin/install -c'  
OBJCFLAGS='-O2' FFLAGS='-O2' CC='/usr/bin/gcc-4.0'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
_Users_me_macports_perl_p5-file-readbackwards/work/File- 
ReadBackwards-1.04" && /opt/local/bin/perl Makefile.PL  
INSTALLDIRS=vendor'
sh: line 0: cd: /opt/local/var/macports/build/ 
_Users_me_macports_perl_p5-file-readbackwards/work/File- 
ReadBackwards-1.04: No such file or directory
Error: Target org.macports.configure returned: configure failure:  
shell command " cd "/opt/local/var/macports/build/ 
_Users_me_macports_perl_p5-file-readbackwards/work/File- 
ReadBackwards-1.04" && /opt/local/bin/perl Makefile.PL  
INSTALLDIRS=vendor " returned error 1
Command output: sh: line 0: cd: /opt/local/var/macports/build/ 
_Users_me_macports_perl_p5-file-readbackwards/work/File- 
ReadBackwards-1.04: No such file or directory

Warning: the following items did not execute (for p5-file- 
readbackwards): org.macports.activate org.macports.configure  
org.macports.build org.macports.destroot org.macports.install
Error: Status 1 encountered during processing.

--
Scott


From opendarwin.org at darkart.com  Mon Jan 19 21:56:48 2009
From: opendarwin.org at darkart.com (Eric Hall)
Date: Tue, 20 Jan 2009 05:56:48 +0000
Subject: p5 modules, get me started on one
In-Reply-To: <E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
Message-ID: <20090120055648.GI1155@darkart.com>

On Mon, Jan 19, 2009 at 09:33:46PM -0800, Scott Haneda wrote:
> Thanks still getting stuck though:

[snip]

> 
> DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
> _Users_me_macports_perl_p5-file-readbackwards/work" && gzip -dc /opt/ 
> local/var/macports/distfiles/perl5/File-ReadBackwards-1.04.tar.gz | / 
> usr/bin/gnutar --no-same-owner -xf -'
> 
> gzip: /opt/local/var/macports/distfiles/perl5/File- 
> ReadBackwards-1.04.tar.gz: not in gzip format

[snip]

	Looks like gzip doesn't like the distfile you downloaded.
Perhaps you got a failed download, and the distfile you have is
really a bunch of HTML telling you so?

	I was able to get something that appears to be a tarball
from cpan, size is 8318 bytes, MD5 and SHA1 are:

MD5 (File-ReadBackwards-1.04.tar.gz) = bda339c8b2e5139649cb28c4b775fb42
SHA1(File-ReadBackwards-1.04.tar.gz)= 19874cb169f2b105c82222588a163fb17bd77599

	Always good to check that the file you downloaded to make
checksums 1) is really the file you think it is and 2) can be demonstrated
to be so via cryptographic methods (if possible of course).



		-eric


From talklists at newgeo.com  Mon Jan 19 22:57:52 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 19 Jan 2009 22:57:52 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <20090120055648.GI1155@darkart.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
Message-ID: <7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>

On Jan 19, 2009, at 9:56 PM, Eric Hall wrote:
> On Mon, Jan 19, 2009 at 09:33:46PM -0800, Scott Haneda wrote:
>> Thanks still getting stuck though:
>> DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/
>> _Users_me_macports_perl_p5-file-readbackwards/work" && gzip -dc /opt/
>> local/var/macports/distfiles/perl5/File-ReadBackwards-1.04.tar.gz | /
>> usr/bin/gnutar --no-same-owner -xf -'
>>
>> gzip: /opt/local/var/macports/distfiles/perl5/File-
>> ReadBackwards-1.04.tar.gz: not in gzip format
>
> 	Always good to check that the file you downloaded to make
> checksums 1) is really the file you think it is and 2) can be  
> demonstrated
> to be so via cryptographic methods (if possible of course).

Got it, thanks, I think it was the bunk connection at the coffee  
shop.  I have a working port, what is the next step in the submission  
process?

Here is my final portfile, if anyone wants to critique, please do.

# $Id$
PortSystem 1.0
PortGroup perl5 1.0

perl5.setup             File-ReadBackwards 1.04
maintainers             hostwizard.com:scott

description             This module reads a file backwards line by line.

long_description        It is simple to use, memory efficient and  
fast. \
			It supports both an object and a tied handle interface. \
										\
			It is intended for processing log and other similar text \
			files which typically have their newest entries appended \
			to them. By default files are assumed to be plain text and \
			have a line ending appropriate to the OS. But you can set \
			the input record separator string on a per file basis.

homepage		http://search.cpan.org/~uri/File-ReadBackwards-1.04/

platforms               darwin

checksums		md5	bda339c8b2e5139649cb28c4b775fb42 \
			sha1	19874cb169f2b105c82222588a163fb17bd77599 \
			rmd160	ab166d1797b0e95ae8990ee583071337bfb54fdf


--
Scott


From talklists at newgeo.com  Mon Jan 19 23:09:02 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 19 Jan 2009 23:09:02 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
Message-ID: <8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>

If I have a requirement in software for Net::LDAP version 0.33, and I  
tried to make a port look for net-ldap 0.39 as at this url http://search.cpan.org/~gbarr/perl-ldap-0.39/

I see the download is for perl-ldap-0.39.tar.gz, which is not Net- 
LDAP-0.39.tar.gz.  Does this just mean I need to get the entire suite  
of ldap mods, and with it will come net::LDAP ?
--
Scott


From talklists at newgeo.com  Mon Jan 19 23:14:12 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Mon, 19 Jan 2009 23:14:12 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <20090120025055.GN785@ninagal.withay.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
Message-ID: <C7366AD3-3F98-4A86-AA4A-EDBEE6A6EA66@newgeo.com>

If I do sudo port search ldap one of the items I get back is
p5-file-readbackwards @1.04 (perl)
     net ldap

What does line #2 mean, and where does that descrption come from?  I  
just made the readbackwards port, and no where in the port was "net  
ldap".

However...
sudo port search readbackwards
p5-file-readbackwards @1.04 (perl)
     This module reads a file backwards line by line.

That one looks like mine for sure, but the first one, which seems to  
be part of the ldap package, now is not listed.

Confused...
--
Scott


From blb at macports.org  Mon Jan 19 23:30:41 2009
From: blb at macports.org (Bryan Blackburn)
Date: Tue, 20 Jan 2009 00:30:41 -0700
Subject: p5 modules, get me started on one
In-Reply-To: <7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
Message-ID: <20090120073041.GQ785@ninagal.withay.com>

On Mon, Jan 19, 2009 at 10:57:52PM -0800, Scott Haneda said:
[...]
>
> Got it, thanks, I think it was the bunk connection at the coffee shop.  I 
> have a working port, what is the next step in the submission process?

Create a new ticket at

<http://trac.macports.org/newticket>

and attach your Portfile to the new one (attachments are strongly preferred
as doing it inline causes whitespace issues).

Bryan


>
> Here is my final portfile, if anyone wants to critique, please do.
>
> # $Id$
> PortSystem 1.0
> PortGroup perl5 1.0
>
> perl5.setup             File-ReadBackwards 1.04
> maintainers             hostwizard.com:scott
>
> description             This module reads a file backwards line by line.
>
> long_description        It is simple to use, memory efficient and fast. \
> 			It supports both an object and a tied handle interface. \
> 										\
> 			It is intended for processing log and other similar text \
> 			files which typically have their newest entries appended \
> 			to them. By default files are assumed to be plain text and \
> 			have a line ending appropriate to the OS. But you can set \
> 			the input record separator string on a per file basis.
>
> homepage		http://search.cpan.org/~uri/File-ReadBackwards-1.04/
>
> platforms               darwin
>
> checksums		md5	bda339c8b2e5139649cb28c4b775fb42 \
> 			sha1	19874cb169f2b105c82222588a163fb17bd77599 \
> 			rmd160	ab166d1797b0e95ae8990ee583071337bfb54fdf
>
>
> --
> Scott

From blb at macports.org  Mon Jan 19 23:32:47 2009
From: blb at macports.org (Bryan Blackburn)
Date: Tue, 20 Jan 2009 00:32:47 -0700
Subject: p5 modules, get me started on one
In-Reply-To: <8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
Message-ID: <20090120073247.GR785@ninagal.withay.com>

On Mon, Jan 19, 2009 at 11:09:02PM -0800, Scott Haneda said:
> If I have a requirement in software for Net::LDAP version 0.33, and I  
> tried to make a port look for net-ldap 0.39 as at this url 
> http://search.cpan.org/~gbarr/perl-ldap-0.39/
>
> I see the download is for perl-ldap-0.39.tar.gz, which is not Net- 
> LDAP-0.39.tar.gz.  Does this just mean I need to get the entire suite of 
> ldap mods, and with it will come net::LDAP ?

That would be the best way to go about it, creating a port for p5-perl-ldap;
however, that already exists:

p5-perl-ldap @0.36 (perl)
    A client interface to LDAP servers

Bryan


> --
> Scott

From blb at macports.org  Mon Jan 19 23:35:32 2009
From: blb at macports.org (Bryan Blackburn)
Date: Tue, 20 Jan 2009 00:35:32 -0700
Subject: p5 modules, get me started on one
In-Reply-To: <C7366AD3-3F98-4A86-AA4A-EDBEE6A6EA66@newgeo.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<C7366AD3-3F98-4A86-AA4A-EDBEE6A6EA66@newgeo.com>
Message-ID: <20090120073532.GS785@ninagal.withay.com>

On Mon, Jan 19, 2009 at 11:14:12PM -0800, Scott Haneda said:
> If I do sudo port search ldap one of the items I get back is
> p5-file-readbackwards @1.04 (perl)
>     net ldap
>
> What does line #2 mean, and where does that descrption come from?  I just 
> made the readbackwards port, and no where in the port was "net ldap".
>
> However...
> sudo port search readbackwards
> p5-file-readbackwards @1.04 (perl)
>     This module reads a file backwards line by line.
>
> That one looks like mine for sure, but the first one, which seems to be 
> part of the ldap package, now is not listed.
>
> Confused...

Odd; make sure you have only one Portfile for p5-file-readbackwards,
checking any local sources you may have listed in
${prefix}/etc/macports/sources.conf.  And once done, run portindex in those
locations, see if it goes away afterwards.

Bryan


> --
> Scott

From mark at dxradio.demon.co.uk  Tue Jan 20 05:48:09 2009
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Tue, 20 Jan 2009 13:48:09 +0000
Subject: upgrading VIM errors
In-Reply-To: <20090119002025.GF741@ninagal.withay.com>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
	<20090119002025.GF741@ninagal.withay.com>
Message-ID: <AF5AB603-2BF2-444D-9AFB-577B8D26DD65@dxradio.demon.co.uk>


On 19 Jan 2009, at 00:20, Bryan Blackburn wrote:

> On Mon, Jan 19, 2009 at 12:06:38AM +0000, Mark Hattam said:
> [...]
>> iMac:~ mark$ sudo port upgrade outdated
>> --->  Fetching vim
>> --->  Verifying checksum(s) for vim
>> --->  Extracting vim
>> --->  Applying patches to vim
>> --->  Configuring vim
>> --->  Building vim
> [...]
>> Undefined symbols:
>>  "__Xsetlocale", referenced from:
>
> Looks like #17606:
>
> <http://trac.macports.org/ticket/17606>
>
> Bryan
>
> [...]
>>
>> Mark


Selfupdate'd just now ... lunchtime 20 Jan

The following installed ports are outdated:
curl                           7.19.2_0 < 7.19.3_0
vim                            7.2.077_0 < 7.2.077_1

and

iMac:~ mark$ sudo port upgrade outdated

[curl installed OK, then ...]

Portfile changed since last build; discarding previous state.
--->  Fetching vim
--->  Verifying checksum(s) for vim
--->  Extracting vim
--->  Applying patches to vim
--->  Configuring vim
--->  Building vim
--->  Staging vim into destroot
--->  Deactivating vim @7.2.077_0
--->  Installing vim @7.2.077_1
--->  Activating vim @7.2.077_1
--->  Cleaning vim

So the Portfile's changed but the same _1 version ... and it worked.

Mark

From raimue at macports.org  Tue Jan 20 05:52:58 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Tue, 20 Jan 2009 14:52:58 +0100
Subject: upgrading VIM errors
In-Reply-To: <AF5AB603-2BF2-444D-9AFB-577B8D26DD65@dxradio.demon.co.uk>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>	<20090119002025.GF741@ninagal.withay.com>
	<AF5AB603-2BF2-444D-9AFB-577B8D26DD65@dxradio.demon.co.uk>
Message-ID: <4975D73A.6070606@macports.org>

Mark Hattam wrote:
> Portfile changed since last build; discarding previous state.
> --->  Fetching vim
> --->  Verifying checksum(s) for vim
> --->  Extracting vim
> --->  Applying patches to vim
> --->  Configuring vim
> --->  Building vim
> --->  Staging vim into destroot
> --->  Deactivating vim @7.2.077_0
> --->  Installing vim @7.2.077_1
> --->  Activating vim @7.2.077_1
> --->  Cleaning vim
> 
> So the Portfile's changed but the same _1 version ... and it worked.

Thanks for the confirmation that the patch supplied by Bryan works. I
didn't bump the revision as the problem only affected users on install
and not users who already got it installed.

Rainer

From face at CentosPrime.COM  Tue Jan 20 07:22:43 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Tue, 20 Jan 2009 08:22:43 -0700
Subject: error upgrading freetype / xorg-libxcb et al on Panther
In-Reply-To: <84456A33-CFA6-469E-BC02-2A77196F36EF@macports.org>
References: <4F182005-88CD-4673-8CB5-FCEC0B8DA8D0@centosprime.com>
	<643C78AD-5169-4A06-BE51-3F1765F90A3E@macports.org>
	<F96368F9-9995-44A4-8DE8-A23A43B075CD@CentosPrime.COM>
	<EE8D6E03-2924-426D-A26B-BEBBEC662993@macports.org>
	<84456A33-CFA6-469E-BC02-2A77196F36EF@macports.org>
Message-ID: <05B70490-AFD2-4F0C-A5D9-B9EEA434D31F@CentosPrime.COM>

On 2009-01-19 , at 16:38 , Ryan Schmidt wrote:

> I imagine Panther's make is just too old and I'll have to add a  
> dependency on MacPorts GNU make. I'll handle this in a moment, and  
> ask for more info in the ticket if I need it.
>
> http://trac.macports.org/ticket/18107
>


that works like a champ. Thanks. freetype upgraded on my Panther system.

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



From ohce86 at kitcarson.net  Tue Jan 20 09:38:42 2009
From: ohce86 at kitcarson.net (Timothy Goins)
Date: Tue, 20 Jan 2009 10:38:42 -0700
Subject: upgrading VIM errors
In-Reply-To: <AF5AB603-2BF2-444D-9AFB-577B8D26DD65@dxradio.demon.co.uk>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
	<20090119002025.GF741@ninagal.withay.com>
	<AF5AB603-2BF2-444D-9AFB-577B8D26DD65@dxradio.demon.co.uk>
Message-ID: <F788C75E-EB65-4378-B548-B86E5DB310DB@kitcarson.net>

When I attempt to *upgrade outdated* openssl and vim fail; all other  
ports upgrade.  Here is the error stream for the vim failure:

tim at cotopaxi:~$ sudo port upgrade vim
--->  Building vim
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_editors_vim/work/vim72" && make all "  
returned error 2
Command output: Starting make in the src directory.
If there are problems, cd to the src directory and run make there
cd src && make all
/usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/include  
-DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/FlatCarbon  -O - 
D_FORTIFY_SOURCE=1         version.c -o objects/version.o
   /usr/bin/gcc-4.0   -L/opt/local/lib -L/usr/local/lib 	-o vim  
objects/buffer.o objects/charset.o objects/diff.o objects/digraph.o  
objects/edit.o objects/eval.o objects/ex_cmds.o objects/ex_cmds2.o  
objects/ex_docmd.o objects/ex_eval.o objects/ex_getln.o objects/ 
fileio.o objects/fold.o objects/getchar.o objects/hardcopy.o objects/ 
hashtab.o  objects/if_cscope.o objects/if_xcmdsrv.o objects/main.o  
objects/mark.o objects/memfile.o objects/memline.o objects/menu.o  
objects/message.o objects/misc1.o objects/misc2.o objects/move.o  
objects/mbyte.o objects/normal.o objects/ops.o objects/option.o  
objects/os_unix.o objects/pathdef.o objects/popupmnu.o objects/ 
quickfix.o objects/regexp.o objects/screen.o objects/search.o objects/ 
spell.o objects/syntax.o  objects/tag.o objects/term.o objects/ui.o  
objects/undo.o objects/window.o       objects/os_macosx.o objects/ 
os_mac_conv.o  objects/netbeans.o  objects/version.o       -lm  - 
lncurses -liconv -framework Carbon
Undefined symbols:
   "__Xsetlocale", referenced from:
       _get_locale_val in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _ex_language in ex_cmds2.o
       _main in main.o
       _main in main.o
       _enc_locale in mbyte.o
       _mac_lang_init in os_mac_conv.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[1]: *** [vim] Error 1
make: *** [all] Error 2

Error: Unable to upgrade port: 1

On Jan 20, 2009, at 6:48 AM, Mark Hattam wrote:

>
> On 19 Jan 2009, at 00:20, Bryan Blackburn wrote:
>
>> On Mon, Jan 19, 2009 at 12:06:38AM +0000, Mark Hattam said:
>> [...]
>>> iMac:~ mark$ sudo port upgrade outdated
>>> --->  Fetching vim
>>> --->  Verifying checksum(s) for vim
>>> --->  Extracting vim
>>> --->  Applying patches to vim
>>> --->  Configuring vim
>>> --->  Building vim
>> [...]
>>> Undefined symbols:
>>> "__Xsetlocale", referenced from:
>>
>> Looks like #17606:
>>
>> <http://trac.macports.org/ticket/17606>
>>
>> Bryan
>>
>> [...]
>>>
>>> Mark
>
>
> Selfupdate'd just now ... lunchtime 20 Jan
>
> The following installed ports are outdated:
> curl                           7.19.2_0 < 7.19.3_0
> vim                            7.2.077_0 < 7.2.077_1
>
> and
>
> iMac:~ mark$ sudo port upgrade outdated
>
> [curl installed OK, then ...]
>
> Portfile changed since last build; discarding previous state.
> --->  Fetching vim
> --->  Verifying checksum(s) for vim
> --->  Extracting vim
> --->  Applying patches to vim
> --->  Configuring vim
> --->  Building vim
> --->  Staging vim into destroot
> --->  Deactivating vim @7.2.077_0
> --->  Installing vim @7.2.077_1
> --->  Activating vim @7.2.077_1
> --->  Cleaning vim
>
> So the Portfile's changed but the same _1 version ... and it worked.
>
> Mark
> _______________________________________________
> 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/20090120/12123043/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2116 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090120/12123043/attachment.bin>

From pgijnxn02 at sneakemail.com  Tue Jan 20 09:48:02 2009
From: pgijnxn02 at sneakemail.com (Joel Thibault (MacPorts))
Date: Tue, 20 Jan 2009 12:48:02 -0500
Subject: upgrading VIM errors
In-Reply-To: <F788C75E-EB65-4378-B548-B86E5DB310DB@kitcarson.net>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
	<20090119002025.GF741@ninagal.withay.com>
	<AF5AB603-2BF2-444D-9AFB-577B8D26DD65@dxradio.demon.co.uk>
	<F788C75E-EB65-4378-B548-B86E5DB310DB@kitcarson.net>
Message-ID: <7a665ffc0901200948v22b58830m1296a22f09d38a04@mail.gmail.com>

On Tue, Jan 20, 2009 at 12:38 PM, Timothy Goins
ohce86-at-kitcarson.net|MacPorts|
<doxvk95gtd0t at sneakemail.com> wrote:

> When I attempt to *upgrade outdated* openssl and vim fail; all other ports
> upgrade.  Here is the error stream for the vim failure:
> tim at cotopaxi:~$ sudo port upgrade vim
> --->  Building vim
> Error: Target org.macports.build returned: shell command " cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_vim/work/vim72"
> && make all " returned error 2
> Command output: Starting make in the src directory.
> If there are problems, cd to the src directory and run make there
> cd src && make all
> /usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/include
> -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/FlatCarbon  -O
> -D_FORTIFY_SOURCE=1         version.c -o objects/version.o
>   /usr/bin/gcc-4.0   -L/opt/local/lib -L/usr/local/lib -o vim
> objects/buffer.o objects/charset.o objects/diff.o objects/digraph.o
> objects/edit.o objects/eval.o objects/ex_cmds.o objects/ex_cmds2.o
> objects/ex_docmd.o objects/ex_eval.o objects/ex_getln.o objects/fileio.o
> objects/fold.o objects/getchar.o objects/hardcopy.o objects/hashtab.o
>  objects/if_cscope.o objects/if_xcmdsrv.o objects/main.o objects/mark.o
> objects/memfile.o objects/memline.o objects/menu.o objects/message.o
> objects/misc1.o objects/misc2.o objects/move.o objects/mbyte.o
> objects/normal.o objects/ops.o objects/option.o objects/os_unix.o
> objects/pathdef.o objects/popupmnu.o objects/quickfix.o objects/regexp.o
> objects/screen.o objects/search.o objects/spell.o objects/syntax.o
>  objects/tag.o objects/term.o objects/ui.o objects/undo.o objects/window.o
>     objects/os_macosx.o objects/os_mac_conv.o  objects/netbeans.o
>  objects/version.o       -lm  -lncurses -liconv -framework Carbon
> Undefined symbols:
>   "__Xsetlocale", referenced from:
>       _get_locale_val in ex_cmds2.o
>       _ex_language in ex_cmds2.o
>       _ex_language in ex_cmds2.o
>       _ex_language in ex_cmds2.o
>       _main in main.o
>       _main in main.o
>       _enc_locale in mbyte.o
>       _mac_lang_init in os_mac_conv.o
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[1]: *** [vim] Error 1
> make: *** [all] Error 2
>
> Error: Unable to upgrade port: 1
>


Try doing a selfupdate and clean first, at least for vim:

$ sudo port selfupdate
$ port clean --all vim
$ sudo port upgrade vim

That fixed the problem for me.

Joel



-- 
Joel Thibault [AIM: Jole Tebo]
Software Engineer in Boston
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090120/30969145/attachment.html>

From frstan at bellsouth.net  Tue Jan 20 10:48:52 2009
From: frstan at bellsouth.net (William Davis)
Date: Tue, 20 Jan 2009 13:48:52 -0500
Subject: upgrading VIM errors
In-Reply-To: <7a665ffc0901200948v22b58830m1296a22f09d38a04@mail.gmail.com>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
	<20090119002025.GF741@ninagal.withay.com>
	<AF5AB603-2BF2-444D-9AFB-577B8D26DD65@dxradio.demon.co.uk>
	<F788C75E-EB65-4378-B548-B86E5DB310DB@kitcarson.net>
	<7a665ffc0901200948v22b58830m1296a22f09d38a04@mail.gmail.com>
Message-ID: <8B27BCC4-6655-49E5-A092-4288C3B6891B@bellsouth.net>


On Jan 20, 2009, at 12:48 PM, Joel Thibault (MacPorts) wrote:

>
> On Tue, Jan 20, 2009 at 12:38 PM, Timothy Goins ohce86-at- 
> kitcarson.net |MacPorts| <doxvk95gtd0t at sneakemail.com> wrote:
> When I attempt to *upgrade outdated* openssl and vim fail; all other  
> ports upgrade.  Here is the error stream for the vim failure:
>
> tim at cotopaxi:~$ sudo port upgrade vim
> --->  Building vim
> Error: Target org.macports.build returned: shell command " cd "/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_editors_vim/work/vim72" && make all "  
> returned error 2
> Command output: Starting make in the src directory.
> If there are problems, cd to the src directory and run make there
> cd src && make all
> /usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/ 
> include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/ 
> FlatCarbon  -O -D_FORTIFY_SOURCE=1         version.c -o objects/ 
> version.o
>   /usr/bin/gcc-4.0   -L/opt/local/lib -L/usr/local/lib 	-o vim  
> objects/buffer.o objects/charset.o objects/diff.o objects/digraph.o  
> objects/edit.o objects/eval.o objects/ex_cmds.o objects/ex_cmds2.o  
> objects/ex_docmd.o objects/ex_eval.o objects/ex_getln.o objects/ 
> fileio.o objects/fold.o objects/getchar.o objects/hardcopy.o objects/ 
> hashtab.o  objects/if_cscope.o objects/if_xcmdsrv.o objects/main.o  
> objects/mark.o objects/memfile.o objects/memline.o objects/menu.o  
> objects/message.o objects/misc1.o objects/misc2.o objects/move.o  
> objects/mbyte.o objects/normal.o objects/ops.o objects/option.o  
> objects/os_unix.o objects/pathdef.o objects/popupmnu.o objects/ 
> quickfix.o objects/regexp.o objects/screen.o objects/search.o  
> objects/spell.o objects/syntax.o  objects/tag.o objects/term.o  
> objects/ui.o objects/undo.o objects/window.o       objects/ 
> os_macosx.o objects/os_mac_conv.o  objects/netbeans.o  objects/ 
> version.o       -lm  -lncurses -liconv -framework Carbon
> Undefined symbols:
>   "__Xsetlocale", referenced from:
>       _get_locale_val in ex_cmds2.o
>       _ex_language in ex_cmds2.o
>       _ex_language in ex_cmds2.o
>       _ex_language in ex_cmds2.o
>       _main in main.o
>       _main in main.o
>       _enc_locale in mbyte.o
>       _mac_lang_init in os_mac_conv.o
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[1]: *** [vim] Error 1
> make: *** [all] Error 2
>
> Error: Unable to upgrade port: 1
>
>
> Try doing a selfupdate and clean first, at least for vim:
>
> $ sudo port selfupdate
> $ port clean --all vim
> $ sudo port upgrade vim
>
> That fixed the problem for me.
>
> Joel
>
>
>
> -- 
> Joel Thibault [AIM: Jole Tebo]
> Software Engineer in Boston

fixed it for me also


William Davis
frstanATbellsouthDOTnet
Mac OS X.5.6 Darwin 9.5.0
XQuartz 2.3.2 (xorg-server 1.4.2-apple31)
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/20090120/ce4cf5a6/attachment.html>

From ohce86 at kitcarson.net  Tue Jan 20 10:58:28 2009
From: ohce86 at kitcarson.net (Timothy Goins)
Date: Tue, 20 Jan 2009 11:58:28 -0700
Subject: upgrading VIM errors
In-Reply-To: <1143-17623@sneakemail.com>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
	<20090119002025.GF741@ninagal.withay.com>
	<AF5AB603-2BF2-444D-9AFB-577B8D26DD65@dxradio.demon.co.uk>
	<F788C75E-EB65-4378-B548-B86E5DB310DB@kitcarson.net>
	<1143-17623@sneakemail.com>
Message-ID: <B59B7ACF-25F5-49D0-8E13-1335A806F944@kitcarson.net>

Thanks, Joel, that worked.  However, I ran into two problems that I  
found interesting.  When I ran "tim at cotopaxi:~$ sudo port clean --all  
vim" the call returned "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_editors_vim/work/.macports.vim.state is  
not writable - check permission on port directory..."

When I did an "ls -al" the command returned the following:

drwxr-xr-x   4 root  admin   136 Jan 18 16:55 .
drwxr-xr-x   3 root  admin   102 Jan 18 16:55 ..
-rw-r--r--   1 root  admin   144 Jan 18 16:55 .macports.vim.state
drwxr-xr-x  43 root  admin  1462 Jan 18 16:55 vim72

Huh?  So, I did a chmod 666 on .macports.vim.state (although that  
didn't make much sense to me, since the file and directories were all  
writable by root) and ran "sudo port -f clean -all vim" and all was  
well.  I'm going to try a similar procedure on openssl, the only other  
active ports I can't seem to upgrade.

Okay, entirely different situation.  "sudo port upgrade openssl" looks  
for "cc", which somewhere along the way had disappeared from "/usr/ 
bin."  So I created a symlink from /usr/gcc-4.0 to "cc" and all went  
well!

Thanks again,

Tim

On Jan 20, 2009, at 10:48 AM, Joel Thibault wrote:

[snip]
> Undefined symbols:
>   "__Xsetlocale", referenced from:
>       _get_locale_val in ex_cmds2.o
>       _ex_language in ex_cmds2.o
>       _ex_language in ex_cmds2.o
>       _ex_language in ex_cmds2.o
>       _main in main.o
>       _main in main.o
>       _enc_locale in mbyte.o
>       _mac_lang_init in os_mac_conv.o
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[1]: *** [vim] Error 1
> make: *** [all] Error 2
>
> Error: Unable to upgrade port: 1
>
>
> Try doing a selfupdate and clean first, at least for vim:
>
> $ sudo port selfupdate
> $ port clean --all vim
> $ sudo port upgrade vim
>
> That fixed the problem for me.
>
> Joel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090120/6153cc61/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2116 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090120/6153cc61/attachment.bin>

From fbartolom at gmail.com  Tue Jan 20 12:48:18 2009
From: fbartolom at gmail.com (Fabrizio Bartolomucci)
Date: Tue, 20 Jan 2009 21:48:18 +0100
Subject: Problems on gimp.app updating
Message-ID: <49763892.1030203@gmail.com>

This the sequence of errors I get:

--->  Building gimp-app
Error: Target org.macports.build returned: shell command "cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec" 
&& xcodebuild  -alltargets -configuration Deployment build 
OBJROOT=build/ SYMROOT=build/ " returned error 1
Command output: (NOTE: project ScriptExec was written by an older Xcode 
version (39) -- temporarily upgrading it (without modifying project file))

=== BUILDING NATIVE TARGET ScriptExec OF PROJECT ScriptExec WITH 
CONFIGURATION Deployment ===

Checking Dependencies...

CompileC 
build/ScriptExec.build/Deployment/ScriptExec.build/Objects-normal/i386/main.o 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c 
normal i386 c com.apple.compilers.gcc.4_0
    cd 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec
    /Developer/usr/bin/gcc-4.0 -x c -arch i386 -fmessage-length=0 -pipe 
-Wno-trigraphs -fpascal-strings -fasm-blocks -Os -mdynamic-no-pic 
-fvisibility=hidden 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/build/ScriptExec.build/Deployment/ScriptExec.build/ScriptExec.hmap 
-Wmost -Wno-four-char-constants -Wno-unknown-pragmas 
-F/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/build/Deployment 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/build/Deployment/include 
-I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/build/ScriptExec.build/Deployment/ScriptExec.build/DerivedSources 
-include 
/var/folders/zz/zzzivhrRnAmviuee+++++++++++/-Caches-/com.apple.Xcode.0/SharedPrecompiledHeaders/ScriptExec_Prefix-gntvlnquiqoqbabqjbipnrgwmzsc/ScriptExec_Prefix.pch 
-c 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c 
-o 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/build/ScriptExec.build/Deployment/ScriptExec.build/Objects-normal/i386/main.o
cc1: error: 
/var/folders/zz/zzzivhrRnAmviuee+++++++++++/-Caches-/com.apple.Xcode.0/SharedPrecompiledHeaders/ScriptExec_Prefix-gntvlnquiqoqbabqjbipnrgwmzsc/ScriptExec_Prefix.pch: 
No such file or directory
cc1: error: one or more PCH files were found, but they were invalid
cc1: error: use -Winvalid-pch for more information
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c: 
In function 'FSMakePath':
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c:333: 
warning: 'FSpMakeFSRef' is deprecated (declared at 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Files.h:7477)
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c:336: 
warning: pointer targets in passing argument 2 of 'FSRefMakePath' differ 
in signedness
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c: 
In function 'AppOpenDocAEHandler':
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c:417: 
warning: pointer targets in passing argument 2 of 'FSMakePath' differ in 
signedness
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c: 
In function 'AppOpenAppAEHandler':
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c:444: 
warning: no return statement in function returning non-void
** BUILD FAILED **

The following build commands failed:
ScriptExec:
    CompileC 
build/ScriptExec.build/Deployment/ScriptExec.build/Objects-normal/i386/main.o 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c 
normal i386 c com.apple.compilers.gcc.4_0
(1 failure)


From jmr at macports.org  Tue Jan 20 13:14:41 2009
From: jmr at macports.org (Joshua Root)
Date: Wed, 21 Jan 2009 08:14:41 +1100
Subject: Problems on gimp.app updating
In-Reply-To: <49763892.1030203@gmail.com>
References: <49763892.1030203@gmail.com>
Message-ID: <49763EC1.4050805@macports.org>

Fabrizio Bartolomucci wrote:
> cc1: error:
> /var/folders/zz/zzzivhrRnAmviuee+++++++++++/-Caches-/com.apple.Xcode.0/SharedPrecompiledHeaders/ScriptExec_Prefix-gntvlnquiqoqbabqjbipnrgwmzsc/ScriptExec_Prefix.pch:
> No such file or directory
> cc1: error: one or more PCH files were found, but they were invalid
> cc1: error: use -Winvalid-pch for more information

Looks like Xcode's precompiled header cache is corrupt in some way. Try
clearing it by opening Xcode.app and selecting "Empty Caches..." from
the Xcode menu.

- Josh

From fbartolom at gmail.com  Tue Jan 20 13:19:24 2009
From: fbartolom at gmail.com (Fabrizio Bartolomucci)
Date: Tue, 20 Jan 2009 22:19:24 +0100
Subject: Problems on gimp.app updating
In-Reply-To: <49763EC1.4050805@macports.org>
References: <49763892.1030203@gmail.com> <49763EC1.4050805@macports.org>
Message-ID: <49763FDC.1050408@gmail.com>

An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090120/78d9aa81/attachment.html>

From talklists at newgeo.com  Tue Jan 20 14:44:46 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Tue, 20 Jan 2009 14:44:46 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <20090120073532.GS785@ninagal.withay.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<C7366AD3-3F98-4A86-AA4A-EDBEE6A6EA66@newgeo.com>
	<20090120073532.GS785@ninagal.withay.com>
Message-ID: <01B7A0D4-3F0B-4A42-B611-A04C3372DC5E@newgeo.com>

On Jan 19, 2009, at 11:35 PM, Bryan Blackburn wrote:

> On Mon, Jan 19, 2009 at 11:14:12PM -0800, Scott Haneda said:
>> If I do sudo port search ldap one of the items I get back is
>> p5-file-readbackwards @1.04 (perl)
>>    net ldap
>>
>> What does line #2 mean, and where does that descrption come from?   
>> I just
>> made the readbackwards port, and no where in the port was "net ldap".
>>
>> However...
>> sudo port search readbackwards
>> p5-file-readbackwards @1.04 (perl)
>>    This module reads a file backwards line by line.
>>
>> That one looks like mine for sure, but the first one, which seems  
>> to be
>> part of the ldap package, now is not listed.
>>
>> Confused...
>
> Odd; make sure you have only one Portfile for p5-file-readbackwards,
> checking any local sources you may have listed in
> ${prefix}/etc/macports/sources.conf.  And once done, run portindex  
> in those
> locations, see if it goes away afterwards.


Done.  Still the same issue:

port search ldap
p5-file-readbackwards @1.04 (perl)
     net ldap

port search readbackwards
p5-file-readbackwards @1.04 (perl)
     This module reads a file backwards line by line.

The second one should certainly find the first, but I have no idea  
where the first one is coming from.
--
Scott


From talklists at newgeo.com  Tue Jan 20 15:19:44 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Tue, 20 Jan 2009 15:19:44 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <20090120073247.GR785@ninagal.withay.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
	<20090120073247.GR785@ninagal.withay.com>
Message-ID: <82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>

On Jan 19, 2009, at 11:32 PM, Bryan Blackburn wrote:

> On Mon, Jan 19, 2009 at 11:09:02PM -0800, Scott Haneda said:
>> If I have a requirement in software for Net::LDAP version 0.33, and I
>> tried to make a port look for net-ldap 0.39 as at this url
>> http://search.cpan.org/~gbarr/perl-ldap-0.39/
>>
>> I see the download is for perl-ldap-0.39.tar.gz, which is not Net-
>> LDAP-0.39.tar.gz.  Does this just mean I need to get the entire  
>> suite of
>> ldap mods, and with it will come net::LDAP ?
>
> That would be the best way to go about it, creating a port for p5- 
> perl-ldap;
> however, that already exists:
>
> p5-perl-ldap @0.36 (perl)
>    A client interface to LDAP servers


Ok, installed p5-perl-ldap and I get this
sudo port list installed | grep ldap
p5-file-readbackwards          @1.04           perl/p5-net-ldap
p5-perl-ldap                   @0.36           perl/p5-perl-ldap

* Again, wondering why readbackwards is still in that list.

Anyway, the package I am trying to use needs specifically net::ldap . 
33, how do I test that it is there, as currently, it does not seem to  
be.
--
Scott


From ryandesign at macports.org  Tue Jan 20 15:19:41 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 20 Jan 2009 17:19:41 -0600
Subject: upgrading VIM errors
In-Reply-To: <B59B7ACF-25F5-49D0-8E13-1335A806F944@kitcarson.net>
References: <5F3B1DC4-31B6-4666-A4D0-80EF5F11FA57@dxradio.demon.co.uk>
	<20090119002025.GF741@ninagal.withay.com>
	<AF5AB603-2BF2-444D-9AFB-577B8D26DD65@dxradio.demon.co.uk>
	<F788C75E-EB65-4378-B548-B86E5DB310DB@kitcarson.net>
	<1143-17623@sneakemail.com>
	<B59B7ACF-25F5-49D0-8E13-1335A806F944@kitcarson.net>
Message-ID: <B13E0C68-AEE7-4D4A-A645-E2C461D414C8@macports.org>


On Jan 20, 2009, at 12:58, Timothy Goins wrote:

> Thanks, Joel, that worked.  However, I ran into two problems that I  
> found interesting.  When I ran "tim at cotopaxi:~$ sudo port clean -- 
> all vim" the call returned "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_edito 
> rs_vim/work/.macports.vim.state is not writable - check permission  
> on port directory..."
>
> When I did an "ls -al" the command returned the following:
>
> drwxr-xr-x   4 root  admin   136 Jan 18 16:55 .
> drwxr-xr-x   3 root  admin   102 Jan 18 16:55 ..
> -rw-r--r--   1 root  admin   144 Jan 18 16:55 .macports.vim.state
> drwxr-xr-x  43 root  admin  1462 Jan 18 16:55 vim72
>
> Huh?  So, I did a chmod 666 on .macports.vim.state (although that  
> didn't make much sense to me, since the file and directories were  
> all writable by root) and ran "sudo port -f clean -all vim" and all  
> was well.  I'm going to try a similar procedure on openssl, the  
> only other active ports I can't seem to upgrade.

I cannot explain that; a command run using sudo should have  
permission to do virtually anything.

> Okay, entirely different situation.  "sudo port upgrade openssl"  
> looks for "cc", which somewhere along the way had disappeared from  
> "/usr/bin."  So I created a symlink from /usr/gcc-4.0 to "cc" and  
> all went well!

If /usr/bin/cc was absent from your system, it should not have been;  
if you got that symlink recreated pointing to gcc-4.0, then that's fine.

Ports should compile using /usr/bin/gcc-4.0 (or, more specifically, $ 
{configure.compiler}); if openssl is using "cc", then a bug needs to  
be filed against openssl.



From jmr at macports.org  Tue Jan 20 15:28:29 2009
From: jmr at macports.org (Joshua Root)
Date: Wed, 21 Jan 2009 10:28:29 +1100
Subject: p5 modules, get me started on one
In-Reply-To: <82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>	<20090120013150.GI785@ninagal.withay.com>	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>	<20090120025055.GN785@ninagal.withay.com>	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>	<20090120055648.GI1155@darkart.com>	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>	<20090120073247.GR785@ninagal.withay.com>
	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
Message-ID: <49765E1D.50707@macports.org>

Scott Haneda wrote:
> Ok, installed p5-perl-ldap and I get this
> sudo port list installed | grep ldap
> p5-file-readbackwards          @1.04           perl/p5-net-ldap
> p5-perl-ldap                   @0.36           perl/p5-perl-ldap
> 
> * Again, wondering why readbackwards is still in that list.

'port list' gets information about the specified ports from the index,
so 'port list installed' will, for each installed port, look up its name
in the index and print the information that is there. You almost
certainly want 'port installed', which will print out the information
about the version that is actually installed.

- Josh

From mmensinger at mail.bradley.edu  Tue Jan 20 15:31:05 2009
From: mmensinger at mail.bradley.edu (Michael Mensinger)
Date: Tue, 20 Jan 2009 17:31:05 -0600
Subject: Problems on gimp.app updating
In-Reply-To: <49763FDC.1050408@gmail.com>
References: <49763892.1030203@gmail.com> <49763EC1.4050805@macports.org>
	<49763FDC.1050408@gmail.com>
Message-ID: <FB1BEA7E-E7C7-4B7B-A1B7-F240E39BE766@bradley.edu>

I was having some trouble with gimp also. for me i did $ sudo port  
install gimp
and it gave me nothing in response. however, i was able to install it  
with the package installer when I updated X11.
http://xquartz.macosforge.org/trac/wiki/X112.3.2.1
so MAYBE that will help, make sure it's updated :)
-mike

On Jan 20, 2009, at 3:19 PM, Fabrizio Bartolomucci wrote:

> Joshua Root ha scritto:
>>
>> Fabrizio Bartolomucci wrote:
>>
>>> cc1: error:
>>> /var/folders/zz/zzzivhrRnAmviuee+++++++++++/-Caches-/ 
>>> com.apple.Xcode.0/SharedPrecompiledHeaders/ScriptExec_Prefix- 
>>> gntvlnquiqoqbabqjbipnrgwmzsc/ScriptExec_Prefix.pch:
>>> No such file or directory
>>> cc1: error: one or more PCH files were found, but they were invalid
>>> cc1: error: use -Winvalid-pch for more information
>>>
>> Looks like Xcode's precompiled header cache is corrupt in some way.  
>> Try
>> clearing it by opening Xcode.app and selecting "Empty Caches..." from
>> the Xcode menu.
>>
>> - Josh
>>
> Thanks, I was not even aware of that application. I did as you  
> suggested and relaunched the update but, unfortunately without any  
> modification.
> --->  Building gimp-app
> Error: Target org.macports.build returned: shell command "cd "/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec" &&  
> xcodebuild  -alltargets -configuration Deployment build  
> OBJROOT=build/ SYMROOT=build/ " returned error 1
> Command output: (NOTE: project ScriptExec was written by an older  
> Xcode version (39) -- temporarily upgrading it (without modifying  
> project file))
>
> === BUILDING NATIVE TARGET ScriptExec OF PROJECT ScriptExec WITH  
> CONFIGURATION Deployment ===
>
> Checking Dependencies...
>
> CompileC build/ScriptExec.build/Deployment/ScriptExec.build/Objects- 
> normal/i386/main.o /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c  
> normal i386 c com.apple.compilers.gcc.4_0
>     cd /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec
>     /Developer/usr/bin/gcc-4.0 -x c -arch i386 -fmessage-length=0 - 
> pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -Os -mdynamic-no- 
> pic -fvisibility=hidden -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/build/ 
> ScriptExec.build/Deployment/ScriptExec.build/ScriptExec.hmap -Wmost - 
> Wno-four-char-constants -Wno-unknown-pragmas -F/opt/local/var/ 
> macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/build/ 
> Deployment -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/build/ 
> Deployment/include -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/build/ 
> ScriptExec.build/Deployment/ScriptExec.build/DerivedSources - 
> include /var/folders/zz/zzzivhrRnAmviuee+++++++++++/-Caches-/ 
> com.apple.Xcode.0/SharedPrecompiledHeaders/ScriptExec_Prefix- 
> gntvlnquiqoqbabqjbipnrgwmzsc/ScriptExec_Prefix.pch -c /opt/local/var/ 
> macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c -o / 
> opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/build/ 
> ScriptExec.build/Deployment/ScriptExec.build/Objects-normal/i386/ 
> main.o
> cc1: error: /var/folders/zz/zzzivhrRnAmviuee+++++++++++/-Caches-/ 
> com.apple.Xcode.0/SharedPrecompiledHeaders/ScriptExec_Prefix- 
> gntvlnquiqoqbabqjbipnrgwmzsc/ScriptExec_Prefix.pch: No such file or  
> directory
> cc1: error: one or more PCH files were found, but they were invalid
> cc1: error: use -Winvalid-pch for more information
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c: In  
> function 'FSMakePath':
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c: 
> 333: warning: 'FSpMakeFSRef' is deprecated (declared at /System/ 
> Library/Frameworks/CoreServices.framework/Frameworks/ 
> CarbonCore.framework/Headers/Files.h:7477)
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c: 
> 336: warning: pointer targets in passing argument 2 of  
> 'FSRefMakePath' differ in signedness
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c: In  
> function 'AppOpenDocAEHandler':
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c: 
> 417: warning: pointer targets in passing argument 2 of 'FSMakePath'  
> differ in signedness
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c: In  
> function 'AppOpenAppAEHandler':
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c: 
> 444: warning: no return statement in function returning non-void
> ** BUILD FAILED **
>
> The following build commands failed:
> ScriptExec:
>     CompileC build/ScriptExec.build/Deployment/ScriptExec.build/ 
> Objects-normal/i386/main.o /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_gimp-app/work/ScriptExec/main.c  
> normal i386 c com.apple.compilers.gcc.4_0
> (1 failure)
>
>
> Error: Unable to upgrade port: 1
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Michael Mensinger
Theta Xi Fraternity
Electrical Engineer
Bradley University
mmensinger at bradley.edu
630-297-6979




From talklists at newgeo.com  Tue Jan 20 16:07:56 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Tue, 20 Jan 2009 16:07:56 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
	<20090120073247.GR785@ninagal.withay.com>
	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
Message-ID: <16926AEC-7084-4517-8338-B99FE9C35B41@newgeo.com>

If I need this module
http://search.cpan.org/~gbarr/libnet-1.22/Net/SMTP.pm

I am still not entirely sure how I get to it.  There is source on the  
page for just net::smtp, but it looks like I have to get libnet as  
well?  If I do have libnet installed, how do I confirm it has  
net::smtp in it?

Just for kicks, I made a port for net-smtp 2.31 and all the fetches  
fail of course.  So I suspect I need to use libnet instead.  But how  
would someone searching in macports, for net::smtp, ever know it is  
there, since it is hidden away in libnet?

Is there some part of the port file where I am supposed to list all  
the parts?  If there is, how do I get such a list?

# $Id$
PortSystem 1.0
PortGroup perl5 1.0

perl5.setup             net-smtp 2.31
maintainers             hostwizard.com:scott

description             Net::SMTP - Simple Mail Transfer Protocol Client

long_description        test

homepage                http://search.cpan.org/~gbarr/libnet-1.22/Net/SMTP.pm

platforms               darwin

--
Scott


From TimLee at rochester.rr.com  Tue Jan 20 16:45:21 2009
From: TimLee at rochester.rr.com (Timothy Lee)
Date: Tue, 20 Jan 2009 19:45:21 -0500
Subject: Liger: It's pretty much my favorite animal
In-Reply-To: <D8E43117-1EB6-4637-9B9D-7953863385A8@macports.org>
References: <DB2FFC75-D2F5-4E92-A711-0747A48A8A0E@rochester.rr.com>
	<D8E43117-1EB6-4637-9B9D-7953863385A8@macports.org>
Message-ID: <CFF79E64-CA48-416E-A8EA-CF09E4F6C9BD@rochester.rr.com>

Thanks for the reply Ryan!

I've noticed this App Note published by Apple:
http://developer.apple.com/technotes/tn2002/tn2064.html

It looks like the universal_target (really the  
MACOSX_DEPLOYMENT_TARGET=10.4) might be the only thing required to  
build tiger-compatible apps on leopard.

Does anyone have any other insight into this?

Thanks
Tim

On Jan 19, 2009, at 9:49 PM, Ryan Schmidt wrote:

>
> On Jan 19, 2009, at 20:05, Timothy Lee wrote:
>
>> New to this list. I've been working on porting Musicbrainz Picard  
>> to the mac (dependencies fulfilled by MacPorts) over the past few  
>> weeks. While working through some of the issues, a few questions  
>> popped up:
>>
>> 1. I'm building on Leopard (i386) but was hoping to target Tiger.  
>> What (universal-ity aside) are the proper steps to compile  
>> everything on my Leopard install for Tiger? Is it simply setting  
>> universal_target to 10.4 in my macports.conf ? Or are there other  
>> variables that need to be set? What packages do I need to have  
>> installed (the 10.4 SDK) ?
>>
>> 2. For building a Tiger Macports on my Leopard, should I simply  
>> download the 10.4 package installer and life will be fine?
>
>
> Welcome to MacPorts!
>
> You could try setting universal_sdkroot to the 10.4u SDK,  
> universal_target to 10.4 and x11prefix to /usr/X11R6. However,  
> building on Leopard for Tiger, or any other such cross-compilation,  
> is ill-tested in MacPorts and not supported. To truly test this, use  
> a real Tiger machine. If you don't have one, perhaps someone else  
> who does can test it for you.
>
>


From blb at macports.org  Tue Jan 20 16:56:52 2009
From: blb at macports.org (Bryan Blackburn)
Date: Tue, 20 Jan 2009 17:56:52 -0700
Subject: p5 modules, get me started on one
In-Reply-To: <01B7A0D4-3F0B-4A42-B611-A04C3372DC5E@newgeo.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<C7366AD3-3F98-4A86-AA4A-EDBEE6A6EA66@newgeo.com>
	<20090120073532.GS785@ninagal.withay.com>
	<01B7A0D4-3F0B-4A42-B611-A04C3372DC5E@newgeo.com>
Message-ID: <20090121005652.GJ965@ninagal.withay.com>

On Tue, Jan 20, 2009 at 02:44:46PM -0800, Scott Haneda said:
> On Jan 19, 2009, at 11:35 PM, Bryan Blackburn wrote:
[...]
>>
>> Odd; make sure you have only one Portfile for p5-file-readbackwards,
>> checking any local sources you may have listed in
>> ${prefix}/etc/macports/sources.conf.  And once done, run portindex in 
>> those
>> locations, see if it goes away afterwards.
>
>
> Done.  Still the same issue:
>
> port search ldap
> p5-file-readbackwards @1.04 (perl)
>     net ldap
>
> port search readbackwards
> p5-file-readbackwards @1.04 (perl)
>     This module reads a file backwards line by line.
>
> The second one should certainly find the first, but I have no idea where 
> the first one is coming from.

Nor do I; it looks like it's seeing two copies of the same port, with
differing descriptions.  Only thing I can think of is to go through all of
your port sources in sources.conf, checking to see if you have a second copy
hiding away someplace.

FWIW, the only perl module hit I get for searching on ldap is p5-perl-ldap.

Bryan


> --
> Scott
>

From blb at macports.org  Tue Jan 20 16:58:53 2009
From: blb at macports.org (Bryan Blackburn)
Date: Tue, 20 Jan 2009 17:58:53 -0700
Subject: p5 modules, get me started on one
In-Reply-To: <82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
	<20090120073247.GR785@ninagal.withay.com>
	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
Message-ID: <20090121005853.GK965@ninagal.withay.com>

On Tue, Jan 20, 2009 at 03:19:44PM -0800, Scott Haneda said:
> On Jan 19, 2009, at 11:32 PM, Bryan Blackburn wrote:
>
>> On Mon, Jan 19, 2009 at 11:09:02PM -0800, Scott Haneda said:
>>> If I have a requirement in software for Net::LDAP version 0.33, and I
>>> tried to make a port look for net-ldap 0.39 as at this url
>>> http://search.cpan.org/~gbarr/perl-ldap-0.39/
>>>
>>> I see the download is for perl-ldap-0.39.tar.gz, which is not Net-
>>> LDAP-0.39.tar.gz.  Does this just mean I need to get the entire suite 
>>> of
>>> ldap mods, and with it will come net::LDAP ?
>>
>> That would be the best way to go about it, creating a port for p5- 
>> perl-ldap;
>> however, that already exists:
>>
>> p5-perl-ldap @0.36 (perl)
>>    A client interface to LDAP servers
>
>
> Ok, installed p5-perl-ldap and I get this
> sudo port list installed | grep ldap
> p5-file-readbackwards          @1.04           perl/p5-net-ldap
> p5-perl-ldap                   @0.36           perl/p5-perl-ldap
>
> * Again, wondering why readbackwards is still in that list.

Note that there isn't a p5-net-ldap in the main port list, so maybe that's
something else you added initially, prior to putting it into a
p5-file-readbackwards directory?

>
> Anyway, the package I am trying to use needs specifically net::ldap .33, 
> how do I test that it is there, as currently, it does not seem to be.

Are you saying you specifically need 0.33 and 0.36 can't work?

Bryan


> --
> Scott

From blb at macports.org  Tue Jan 20 17:01:09 2009
From: blb at macports.org (Bryan Blackburn)
Date: Tue, 20 Jan 2009 18:01:09 -0700
Subject: p5 modules, get me started on one
In-Reply-To: <16926AEC-7084-4517-8338-B99FE9C35B41@newgeo.com>
References: <20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
	<20090120073247.GR785@ninagal.withay.com>
	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
	<16926AEC-7084-4517-8338-B99FE9C35B41@newgeo.com>
Message-ID: <20090121010109.GL965@ninagal.withay.com>

On Tue, Jan 20, 2009 at 04:07:56PM -0800, Scott Haneda said:
> If I need this module
> http://search.cpan.org/~gbarr/libnet-1.22/Net/SMTP.pm
>
> I am still not entirely sure how I get to it.  There is source on the  
> page for just net::smtp, but it looks like I have to get libnet as well?  
> If I do have libnet installed, how do I confirm it has net::smtp in it?

Some perl modules come packaged in groups like that, which definitely can
cause confusion.  Maybe the best solution would be to list all actual
modules installed with the given port?  Then it may be easier to search for
it.

>
> Just for kicks, I made a port for net-smtp 2.31 and all the fetches fail 
> of course.  So I suspect I need to use libnet instead.  But how would 
> someone searching in macports, for net::smtp, ever know it is there, since 
> it is hidden away in libnet?
>
> Is there some part of the port file where I am supposed to list all the 
> parts?  If there is, how do I get such a list?

The base perl5.8 port should actually have what's in libnet like Net::SMTP,
so no port should actually be needed for this one.

Bryan

[...]
>
> --
> Scott

From talklists at newgeo.com  Tue Jan 20 17:45:34 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Tue, 20 Jan 2009 17:45:34 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <20090121005652.GJ965@ninagal.withay.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<C7366AD3-3F98-4A86-AA4A-EDBEE6A6EA66@newgeo.com>
	<20090120073532.GS785@ninagal.withay.com>
	<01B7A0D4-3F0B-4A42-B611-A04C3372DC5E@newgeo.com>
	<20090121005652.GJ965@ninagal.withay.com>
Message-ID: <E82E8102-7C5D-4E8E-BA23-939D8AE66D04@newgeo.com>

On Jan 20, 2009, at 4:56 PM, Bryan Blackburn wrote:

> On Tue, Jan 20, 2009 at 02:44:46PM -0800, Scott Haneda said:
>> On Jan 19, 2009, at 11:35 PM, Bryan Blackburn wrote:
> [...]
>>>
>>> Odd; make sure you have only one Portfile for p5-file-readbackwards,
>>> checking any local sources you may have listed in
>>> ${prefix}/etc/macports/sources.conf.  And once done, run portindex  
>>> in
>>> those
>>> locations, see if it goes away afterwards.
>>
>>
>> Done.  Still the same issue:
>>
>> port search ldap
>> p5-file-readbackwards @1.04 (perl)
>>   net ldap
>>
>> port search readbackwards
>> p5-file-readbackwards @1.04 (perl)
>>   This module reads a file backwards line by line.
>>
>> The second one should certainly find the first, but I have no idea  
>> where
>> the first one is coming from.
>
> Nor do I; it looks like it's seeing two copies of the same port, with
> differing descriptions.  Only thing I can think of is to go through  
> all of
> your port sources in sources.conf, checking to see if you have a  
> second copy
> hiding away someplace.
>
> FWIW, the only perl module hit I get for searching on ldap is p5- 
> perl-ldap.


Is this where you mean?
/opt/local/var/macports/sources/rsync.macports.org/release/ports/perl

$ls -la | grep read
drwxr-xr-x    3 root  admin    102 Jan 19 03:22 p5-patchreader
drwxr-xr-x    3 root  admin    102 Jan 19 03:22 p5-pod-readme
drwxr-xr-x    3 root  admin    102 Jan 19 03:22 p5-readonly
drwxr-xr-x    3 root  admin    102 Jan 19 03:22 p5-readonly-xs
drwxr-xr-x    3 root  admin    102 Jan 19 03:22 p5-spreadsheet- 
parseexcel
drwxr-xr-x    3 root  admin    102 Jan 19 03:22 p5-spreadsheet- 
writeexcel
drwxr-xr-x    3 root  admin    102 Jan 19 03:22 p5-term-readkey
drwxr-xr-x    3 root  admin    102 Jan 19 03:22 p5-term-readline-gnu

If I uninstall p5-file-readbackwards and then do my search, nothing  
for readbackward shows up in a new search, or a list installed.
--
Scott

From talklists at newgeo.com  Tue Jan 20 17:47:02 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Tue, 20 Jan 2009 17:47:02 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <20090121005853.GK965@ninagal.withay.com>
References: <C8B88A1E-AFEF-4037-B3A3-971A14EA7512@newgeo.com>
	<20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
	<20090120073247.GR785@ninagal.withay.com>
	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
	<20090121005853.GK965@ninagal.withay.com>
Message-ID: <D6C4E085-601A-44AA-9523-F3C61F5D7869@newgeo.com>

On Jan 20, 2009, at 4:58 PM, Bryan Blackburn wrote:
> On Tue, Jan 20, 2009 at 03:19:44PM -0800, Scott Haneda said:
>> On Jan 19, 2009, at 11:32 PM, Bryan Blackburn wrote:
>>
>>> On Mon, Jan 19, 2009 at 11:09:02PM -0800, Scott Haneda said:
>>>> If I have a requirement in software for Net::LDAP version 0.33,  
>>>> and I
>>>> tried to make a port look for net-ldap 0.39 as at this url
>>>> http://search.cpan.org/~gbarr/perl-ldap-0.39/
>>>>
>>>> I see the download is for perl-ldap-0.39.tar.gz, which is not Net-
>>>> LDAP-0.39.tar.gz.  Does this just mean I need to get the entire  
>>>> suite
>>>> of
>>>> ldap mods, and with it will come net::LDAP ?
>>>
>>> That would be the best way to go about it, creating a port for p5-
>>> perl-ldap;
>>> however, that already exists:
>>>
>>> p5-perl-ldap @0.36 (perl)
>>>   A client interface to LDAP servers
>>
>>
>> Ok, installed p5-perl-ldap and I get this
>> sudo port list installed | grep ldap
>> p5-file-readbackwards          @1.04           perl/p5-net-ldap
>> p5-perl-ldap                   @0.36           perl/p5-perl-ldap
>>
>> * Again, wondering why readbackwards is still in that list.
>
> Note that there isn't a p5-net-ldap in the main port list, so maybe  
> that's
> something else you added initially, prior to putting it into a
> p5-file-readbackwards directory


If that is the case, how do I clean up and only have my locally  
sourced ports be accurate?
--
Scott


From talklists at newgeo.com  Tue Jan 20 17:50:23 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Tue, 20 Jan 2009 17:50:23 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <20090121010109.GL965@ninagal.withay.com>
References: <20090120013150.GI785@ninagal.withay.com>
	<651B72A5-9925-4A90-9AB1-0180ECDE65A4@newgeo.com>
	<20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
	<20090120073247.GR785@ninagal.withay.com>
	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
	<16926AEC-7084-4517-8338-B99FE9C35B41@newgeo.com>
	<20090121010109.GL965@ninagal.withay.com>
Message-ID: <2AD35050-C46E-40C7-B993-4819F3F0CEE6@newgeo.com>

On Jan 20, 2009, at 5:01 PM, Bryan Blackburn wrote:
> On Tue, Jan 20, 2009 at 04:07:56PM -0800, Scott Haneda said:
>> If I need this module
>> http://search.cpan.org/~gbarr/libnet-1.22/Net/SMTP.pm
>>
>> I am still not entirely sure how I get to it.  There is source on the
>> page for just net::smtp, but it looks like I have to get libnet as  
>> well?
>> If I do have libnet installed, how do I confirm it has net::smtp in  
>> it?
>
> Some perl modules come packaged in groups like that, which  
> definitely can
> cause confusion.  Maybe the best solution would be to list all actual
> modules installed with the given port?  Then it may be easier to  
> search for
> it.

List it in the port description?  Will that get searched?  How do I  
even get a list of what is in these packages from the CPAN site?

>> Just for kicks, I made a port for net-smtp 2.31 and all the fetches  
>> fail
>> of course.  So I suspect I need to use libnet instead.  But how would
>> someone searching in macports, for net::smtp, ever know it is  
>> there, since
>> it is hidden away in libnet?
>>
>> Is there some part of the port file where I am supposed to list all  
>> the
>> parts?  If there is, how do I get such a list?
>
> The base perl5.8 port should actually have what's in libnet like  
> Net::SMTP,
> so no port should actually be needed for this one.


How would I know that?
port search smtp
All I see is
p5-net-smtp_auth @0.08 (perl)
     Perl5 SMTP client with AUTHentication

If that is it, great, but how would I confirm it is in fact the same  
thing?  All signs point to it being different.

Beginning to dislike perl and I have not written more than 100 lines  
of it in my life :)
--
Scott


From trog24 at comcast.net  Tue Jan 20 22:38:59 2009
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Tue, 20 Jan 2009 22:38:59 -0800
Subject: Mesa
Message-ID: <06B3AA9B-E1B5-4E03-BCFF-1C10A8CAC13D@comcast.net>

Hello,
	I tried to install mesa and got the following error:

Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mes 
a/work/Mesa-7.2" && make default INSTALL_DIR=/opt/local X11_DIR=/usr/ 
X11R6 " returned error 2
Command output: linux-x86-glide
linux-x86-static
netbsd
openbsd
osf1
osf1-static
solaris-x86
solaris-x86-gcc
solaris-x86-gcc-static
sunos4
sunos4-gcc
sunos4-static
sunos5
sunos5-64-gcc
sunos5-gcc
sunos5-smp
sunos5-v8
sunos5-v8-static
sunos5-v9
sunos5-v9-cc-g++
sunos5-v9-static
ultrix-gcc

Then type 'make <config>' (ex: 'make linux-x86')

Or, run './configure' then 'make'
See './configure --help' for details

(ignore the following error message)
make: *** [configs/current] Error 1

Error: Status 1 encountered during processing.

Anyone have any idea as to why this happened?
Frank

From ryandesign at macports.org  Tue Jan 20 22:54:50 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 21 Jan 2009 00:54:50 -0600
Subject: Mesa
In-Reply-To: <06B3AA9B-E1B5-4E03-BCFF-1C10A8CAC13D@comcast.net>
References: <06B3AA9B-E1B5-4E03-BCFF-1C10A8CAC13D@comcast.net>
Message-ID: <D9819347-29F5-46DE-A2B5-9FB64687D8DC@macports.org>

On Jan 21, 2009, at 00:38, Frank J. R. Hanstick wrote:

> 	I tried to install mesa and got the following error:
>
> Error: Target org.macports.build returned: shell command " cd "/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_m 
> esa/work/Mesa-7.2" && make default INSTALL_DIR=/opt/local X11_DIR=/ 
> usr/X11R6 " returned error 2
> Command output: linux-x86-glide
> linux-x86-static
> netbsd
> openbsd
> osf1
> osf1-static
> solaris-x86
> solaris-x86-gcc
> solaris-x86-gcc-static
> sunos4
> sunos4-gcc
> sunos4-static
> sunos5
> sunos5-64-gcc
> sunos5-gcc
> sunos5-smp
> sunos5-v8
> sunos5-v8-static
> sunos5-v9
> sunos5-v9-cc-g++
> sunos5-v9-static
> ultrix-gcc
>
> Then type 'make <config>' (ex: 'make linux-x86')
>
> Or, run './configure' then 'make'
> See './configure --help' for details
>
> (ignore the following error message)
> make: *** [configs/current] Error 1
>
> Error: Status 1 encountered during processing.
>
> Anyone have any idea as to why this happened?

I don't think we're seeing the first error here. Try "sudo port clean  
mesa" and then "sudo port -d install mesa" and show us the first  
error that occurs. Also, let us know what version of Mac OS X, Xcode  
and MacPorts you have, and on what kind of Mac.



From trog24 at comcast.net  Tue Jan 20 23:15:06 2009
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Tue, 20 Jan 2009 23:15:06 -0800
Subject: Mesa
In-Reply-To: <D9819347-29F5-46DE-A2B5-9FB64687D8DC@macports.org>
References: <06B3AA9B-E1B5-4E03-BCFF-1C10A8CAC13D@comcast.net>
	<D9819347-29F5-46DE-A2B5-9FB64687D8DC@macports.org>
Message-ID: <A044D164-79C7-4300-8995-6260C6D6ED76@comcast.net>

Hello,
	Here is the clean then -d:

DEBUG: Found port in file:///opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/x11/mesa
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/x11/mesa
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 mesa.
DEBUG: Requested variant darwin is not provided by port mesa.
DEBUG: Requested variant macosx is not provided by port mesa.
DEBUG: Found port in file:///opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/x11/xorg-libXext
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/x11/xorg-libXext
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 xorg-libXext.
DEBUG: Requested variant darwin is not provided by port xorg-libXext.
DEBUG: Requested variant macosx is not provided by port xorg-libXext.
DEBUG: Searching for dependency: xorg-libXext
DEBUG: Found Dependency: receipt exists for xorg-libXext
DEBUG: Found port in file:///opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/x11/xorg-glproto
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/x11/xorg-glproto
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 no' specified, so not adding the default  
universal variant
DEBUG: Requested variant powerpc is not provided by port xorg-glproto.
DEBUG: Requested variant darwin is not provided by port xorg-glproto.
DEBUG: Requested variant macosx is not provided by port xorg-glproto.
DEBUG: Searching for dependency: xorg-glproto
DEBUG: Found Dependency: receipt exists for xorg-glproto
DEBUG: Executing org.macports.main (mesa)
--->  Fetching mesa
DEBUG: Executing org.macports.fetch (mesa)
--->  Verifying checksum(s) for mesa
DEBUG: Executing org.macports.checksum (mesa)
--->  Checksumming MesaLib-7.2.tar.bz2
DEBUG: Correct (md5) checksum for MesaLib-7.2.tar.bz2
DEBUG: Correct (sha1) checksum for MesaLib-7.2.tar.bz2
DEBUG: Correct (rmd160) checksum for MesaLib-7.2.tar.bz2
DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
--->  Extracting mesa
DEBUG: Executing org.macports.extract (mesa)
--->  Extracting MesaLib-7.2.tar.bz2
DEBUG: setting option extract.args to /opt/local/var/macports/ 
distfiles/mesa/MesaLib-7.2.tar.bz2
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.4'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mes 
a/work" && /opt/local/bin/bzip2 -dc /opt/local/var/macports/distfiles/ 
mesa/MesaLib-7.2.tar.bz2 | /usr/bin/gnutar --no-same-owner -xf -'
DEBUG: Executing proc-post-org.macports.extract-extract-0
DEBUG: Executing org.macports.patch (mesa)
--->  Applying patches to mesa
--->  Applying /opt/local/var/macports/sources/rsync.macports.org/ 
release/ports/x11/mesa/files/ 
mesa-7.2-36c3e889d0cfbb040f7b860279987cd6ff5951f4.patch
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.4'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mes 
a/work/Mesa-7.2" && patch -p1'
patching file bin/mklib
patching file configs/darwin
patching file configure.ac
patching file docs/news.html
patching file docs/relnotes-7.2.1.html
patching file docs/relnotes-7.2.html
patching file docs/relnotes.html
patching file include/GL/glu.h
patching file src/mesa/drivers/dri/common/dri_bufmgr_fake.c
patching file src/mesa/drivers/dri/common/dri_util.c
patching file src/mesa/drivers/dri/i915/i830_vtbl.c
patching file src/mesa/drivers/dri/i915/intel_batchbuffer.c
patching file src/mesa/drivers/dri/i965/brw_eu.h
patching file src/mesa/drivers/dri/i965/brw_eu_emit.c
patching file src/mesa/drivers/dri/i965/brw_wm.h
patching file src/mesa/drivers/dri/i965/brw_wm_glsl.c
patching file src/mesa/drivers/dri/i965/intel_batchbuffer.c
patching file src/mesa/drivers/dri/intel/intel_batchbuffer.c
patching file src/mesa/main/debug.c
patching file src/mesa/main/get.c
patching file src/mesa/main/mtypes.h
patching file src/mesa/main/shaders.c
patching file src/mesa/main/teximage.c
patching file src/mesa/main/teximage.h
patching file src/mesa/main/texstore.c
patching file src/mesa/shader/shader_api.c
patching file src/mesa/shader/shader_api.h
patching file src/mesa/shader/slang/library/slang_120_core_gc.h
patching file src/mesa/shader/slang/library/ 
slang_builtin_120_common_gc.h
patching file src/mesa/shader/slang/library/slang_common_builtin_gc.h
patching file src/mesa/shader/slang/library/slang_core_gc.h
patching file src/mesa/shader/slang/library/slang_fragment_builtin_gc.h
patching file src/mesa/shader/slang/library/slang_shader.syn
patching file src/mesa/shader/slang/library/slang_shader_syn.h
patching file src/mesa/shader/slang/library/slang_vertex_builtin_gc.h
patching file src/mesa/shader/slang/slang_codegen.c
patching file src/mesa/shader/slang/slang_compile.c
patching file src/mesa/shader/slang/slang_compile_operation.c
patching file src/mesa/shader/slang/slang_emit.c
patching file src/mesa/shader/slang/slang_link.c
patching file src/mesa/shader/slang/slang_log.c
patching file src/mesa/shader/slang/slang_print.c
patching file src/mesa/shader/slang/slang_vartable.c
patching file src/mesa/swrast/s_depth.c
patching file src/mesa/swrast_setup/ss_context.c
--->  Applying /opt/local/var/macports/sources/rsync.macports.org/ 
release/ports/x11/mesa/files/mesa-7.2-Os.patch
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.4'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mes 
a/work/Mesa-7.2" && patch -p1'
patching file configs/darwin
--->  Applying /opt/local/var/macports/sources/rsync.macports.org/ 
release/ports/x11/mesa/files/mesa-7.2-drm_headers.patch
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.4'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mes 
a/work/Mesa-7.2" && patch -p1'
patching file src/glx/x11/drm.h
patching file src/glx/x11/xf86drm.h
--->  Applying /opt/local/var/macports/sources/rsync.macports.org/ 
release/ports/x11/mesa/files/mesa-7.2-x11dir.patch
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.4'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mes 
a/work/Mesa-7.2" && patch -p1'
patching file configs/darwin
--->  Configuring mesa
DEBUG: Using compiler 'Mac OS X gcc 4.0'
DEBUG: Executing org.macports.configure (mesa)
--->  Building mesa
DEBUG: Executing org.macports.build (mesa)
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.4'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mes 
a/work/Mesa-7.2" && make default INSTALL_DIR=/opt/local X11_DIR=/usr/ 
X11R6'


Please choose a configuration from the following list:
aix
aix-64
aix-64-static
aix-gcc
aix-static
beos
bluegene-osmesa
bluegene-xlc-osmesa
catamount-osmesa-pgi
config.mgw
darwin
darwin-fat-32bit
darwin-fat-all
freebsd
freebsd-dri
freebsd-dri-amd64
freebsd-dri-x86
hpux10
hpux10-gcc
hpux10-static
hpux11-32
hpux11-32-static
hpux11-32-static-nothreads
hpux11-64
hpux11-64-static
hpux11-ia64
hpux11-ia64-static
hpux9
hpux9-gcc
irix6-64
irix6-64-static
irix6-n32
irix6-n32-static
irix6-o32
irix6-o32-static
linux
linux-alpha
linux-alpha-static
linux-debug
linux-directfb
linux-dri
linux-dri-debug
linux-dri-ppc
linux-dri-x86
linux-dri-x86-64
linux-dri-xcb
linux-fbdev
linux-glide
linux-ia64-icc
linux-ia64-icc-static
linux-icc
linux-icc-static
linux-indirect
linux-osmesa
linux-osmesa16
linux-osmesa16-static
linux-osmesa32
linux-ppc
linux-ppc-static
linux-profile
linux-solo
linux-solo-ia64
linux-solo-x86
linux-sparc
linux-sparc5
linux-static
linux-ultrasparc
linux-x86
linux-x86-32
linux-x86-64
linux-x86-64-debug
linux-x86-64-static
linux-x86-debug
linux-x86-glide
linux-x86-static
netbsd
openbsd
osf1
osf1-static
solaris-x86
solaris-x86-gcc
solaris-x86-gcc-static
sunos4
sunos4-gcc
sunos4-static
sunos5
sunos5-64-gcc
sunos5-gcc
sunos5-smp
sunos5-v8
sunos5-v8-static
sunos5-v9
sunos5-v9-cc-g++
sunos5-v9-static
ultrix-gcc

Then type 'make <config>' (ex: 'make linux-x86')

Or, run './configure' then 'make'
See './configure --help' for details

(ignore the following error message)
make: *** [configs/current] Error 1
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mes 
a/work/Mesa-7.2" && make default INSTALL_DIR=/opt/local X11_DIR=/usr/ 
X11R6 " returned error 2
Command output: linux-x86-glide
linux-x86-static
netbsd
openbsd
osf1
osf1-static
solaris-x86
solaris-x86-gcc
solaris-x86-gcc-static
sunos4
sunos4-gcc
sunos4-static
sunos5
sunos5-64-gcc
sunos5-gcc
sunos5-smp
sunos5-v8
sunos5-v8-static
sunos5-v9
sunos5-v9-cc-g++
sunos5-v9-static
ultrix-gcc

Then type 'make <config>' (ex: 'make linux-x86')

Or, run './configure' then 'make'
See './configure --help' for details

(ignore the following error message)
make: *** [configs/current] Error 1

Warning: the following items did not execute (for mesa):  
org.macports.activate org.macports.build org.macports.destroot  
org.macports.install
Error: Status 1 encountered during processing.

Frank

On Jan 20, 2009, at 10:54 PM, Ryan Schmidt wrote:

> On Jan 21, 2009, at 00:38, Frank J. R. Hanstick wrote:
>
>> 	I tried to install mesa and got the following error:
>>
>> Error: Target org.macports.build returned: shell command " cd "/ 
>> opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_ 
>> mesa/work/Mesa-7.2" && make default INSTALL_DIR=/opt/local  
>> X11_DIR=/usr/X11R6 " returned error 2
>> Command output: linux-x86-glide
>> linux-x86-static
>> netbsd
>> openbsd
>> osf1
>> osf1-static
>> solaris-x86
>> solaris-x86-gcc
>> solaris-x86-gcc-static
>> sunos4
>> sunos4-gcc
>> sunos4-static
>> sunos5
>> sunos5-64-gcc
>> sunos5-gcc
>> sunos5-smp
>> sunos5-v8
>> sunos5-v8-static
>> sunos5-v9
>> sunos5-v9-cc-g++
>> sunos5-v9-static
>> ultrix-gcc
>>
>> Then type 'make <config>' (ex: 'make linux-x86')
>>
>> Or, run './configure' then 'make'
>> See './configure --help' for details
>>
>> (ignore the following error message)
>> make: *** [configs/current] Error 1
>>
>> Error: Status 1 encountered during processing.
>>
>> Anyone have any idea as to why this happened?
>
> I don't think we're seeing the first error here. Try "sudo port  
> clean mesa" and then "sudo port -d install mesa" and show us the  
> first error that occurs. Also, let us know what version of Mac OS  
> X, Xcode and MacPorts you have, and on what kind of Mac.
>
>


From trog24 at comcast.net  Tue Jan 20 23:18:34 2009
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Tue, 20 Jan 2009 23:18:34 -0800
Subject: Mesa
In-Reply-To: <D9819347-29F5-46DE-A2B5-9FB64687D8DC@macports.org>
References: <06B3AA9B-E1B5-4E03-BCFF-1C10A8CAC13D@comcast.net>
	<D9819347-29F5-46DE-A2B5-9FB64687D8DC@macports.org>
Message-ID: <2751591C-002B-4DAF-887B-F6A1D8126E9A@comcast.net>

Hello,
	Oops.  Forgot xcode and MacPorts:  2.5 and 1.7.0 respectively.
Frank

On Jan 20, 2009, at 10:54 PM, Ryan Schmidt wrote:

> On Jan 21, 2009, at 00:38, Frank J. R. Hanstick wrote:
>
>> 	I tried to install mesa and got the following error:
>>
>> Error: Target org.macports.build returned: shell command " cd "/ 
>> opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_ 
>> mesa/work/Mesa-7.2" && make default INSTALL_DIR=/opt/local  
>> X11_DIR=/usr/X11R6 " returned error 2
>> Command output: linux-x86-glide
>> linux-x86-static
>> netbsd
>> openbsd
>> osf1
>> osf1-static
>> solaris-x86
>> solaris-x86-gcc
>> solaris-x86-gcc-static
>> sunos4
>> sunos4-gcc
>> sunos4-static
>> sunos5
>> sunos5-64-gcc
>> sunos5-gcc
>> sunos5-smp
>> sunos5-v8
>> sunos5-v8-static
>> sunos5-v9
>> sunos5-v9-cc-g++
>> sunos5-v9-static
>> ultrix-gcc
>>
>> Then type 'make <config>' (ex: 'make linux-x86')
>>
>> Or, run './configure' then 'make'
>> See './configure --help' for details
>>
>> (ignore the following error message)
>> make: *** [configs/current] Error 1
>>
>> Error: Status 1 encountered during processing.
>>
>> Anyone have any idea as to why this happened?
>
> I don't think we're seeing the first error here. Try "sudo port  
> clean mesa" and then "sudo port -d install mesa" and show us the  
> first error that occurs. Also, let us know what version of Mac OS  
> X, Xcode and MacPorts you have, and on what kind of Mac.
>
>


From ryandesign at macports.org  Tue Jan 20 23:26:45 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 21 Jan 2009 01:26:45 -0600
Subject: Mesa
In-Reply-To: <A044D164-79C7-4300-8995-6260C6D6ED76@comcast.net>
References: <06B3AA9B-E1B5-4E03-BCFF-1C10A8CAC13D@comcast.net>
	<D9819347-29F5-46DE-A2B5-9FB64687D8DC@macports.org>
	<A044D164-79C7-4300-8995-6260C6D6ED76@comcast.net>
Message-ID: <DBD58D03-E467-450A-9049-D3A9B2845D3C@macports.org>

Frank J. R. Hanstick wrote:

>> 	Oops.  Forgot xcode and MacPorts:  2.5 and 1.7.0 respectively.


Ok, and based on other output you sent, running Mac OS X 10.4 on a  
PowerPC Mac.


> DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_m 
> esa/work/Mesa-7.2" && make default INSTALL_DIR=/opt/local X11_DIR=/ 
> usr/X11R6'
>
>
> Please choose a configuration from the following list:
> aix
> aix-64
> aix-64-static
> aix-gcc
> aix-static
> beos
> bluegene-osmesa
> bluegene-xlc-osmesa
> catamount-osmesa-pgi
> config.mgw
> darwin
> darwin-fat-32bit
> darwin-fat-all
> freebsd
> freebsd-dri
> freebsd-dri-amd64
> freebsd-dri-x86
> hpux10
> hpux10-gcc
> hpux10-static
> hpux11-32
> hpux11-32-static
> hpux11-32-static-nothreads
> hpux11-64
> hpux11-64-static
> hpux11-ia64
> hpux11-ia64-static
> hpux9
> hpux9-gcc
> irix6-64
> irix6-64-static
> irix6-n32
> irix6-n32-static
> irix6-o32
> irix6-o32-static
> linux
> linux-alpha
> linux-alpha-static
> linux-debug
> linux-directfb
> linux-dri
> linux-dri-debug
> linux-dri-ppc
> linux-dri-x86
> linux-dri-x86-64
> linux-dri-xcb
> linux-fbdev
> linux-glide
> linux-ia64-icc
> linux-ia64-icc-static
> linux-icc
> linux-icc-static
> linux-indirect
> linux-osmesa
> linux-osmesa16
> linux-osmesa16-static
> linux-osmesa32
> linux-ppc
> linux-ppc-static
> linux-profile
> linux-solo
> linux-solo-ia64
> linux-solo-x86
> linux-sparc
> linux-sparc5
> linux-static
> linux-ultrasparc
> linux-x86
> linux-x86-32
> linux-x86-64
> linux-x86-64-debug
> linux-x86-64-static
> linux-x86-debug
> linux-x86-glide
> linux-x86-static
> netbsd
> openbsd
> osf1
> osf1-static
> solaris-x86
> solaris-x86-gcc
> solaris-x86-gcc-static
> sunos4
> sunos4-gcc
> sunos4-static
> sunos5
> sunos5-64-gcc
> sunos5-gcc
> sunos5-smp
> sunos5-v8
> sunos5-v8-static
> sunos5-v9
> sunos5-v9-cc-g++
> sunos5-v9-static
> ultrix-gcc
>
> Then type 'make <config>' (ex: 'make linux-x86')
>
> Or, run './configure' then 'make'
> See './configure --help' for details
>
> (ignore the following error message)
> make: *** [configs/current] Error 1

It looks like the port should be either running configure then make,  
or it should run "make darwin". But the port is set up to not run  
configure, and then to run "make default".

We have a bug for this already; you can add yourself to the bug's Cc  
if you're interested in what happens:

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




From trog24 at comcast.net  Tue Jan 20 23:48:42 2009
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Tue, 20 Jan 2009 23:48:42 -0800
Subject: Mesa
In-Reply-To: <DBD58D03-E467-450A-9049-D3A9B2845D3C@macports.org>
References: <06B3AA9B-E1B5-4E03-BCFF-1C10A8CAC13D@comcast.net>
	<D9819347-29F5-46DE-A2B5-9FB64687D8DC@macports.org>
	<A044D164-79C7-4300-8995-6260C6D6ED76@comcast.net>
	<DBD58D03-E467-450A-9049-D3A9B2845D3C@macports.org>
Message-ID: <DB5F7582-8202-481B-9FED-26C3F6127B74@comcast.net>

Hello,
	Correct on base (MacOS 10.4.11 & dual 1.73 GHz MPC-7448's to be  
exact).  Added myself to cc.  Thank you.
Frank

On Jan 20, 2009, at 11:26 PM, Ryan Schmidt wrote:

> Frank J. R. Hanstick wrote:
>
>>> 	Oops.  Forgot xcode and MacPorts:  2.5 and 1.7.0 respectively.
>
>
> Ok, and based on other output you sent, running Mac OS X 10.4 on a  
> PowerPC Mac.
>
>
>> DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_ 
>> mesa/work/Mesa-7.2" && make default INSTALL_DIR=/opt/local  
>> X11_DIR=/usr/X11R6'
>>
>>
>> Please choose a configuration from the following list:
>> aix
>> aix-64
>> aix-64-static
>> aix-gcc
>> aix-static
>> beos
>> bluegene-osmesa
>> bluegene-xlc-osmesa
>> catamount-osmesa-pgi
>> config.mgw
>> darwin
>> darwin-fat-32bit
>> darwin-fat-all
>> freebsd
>> freebsd-dri
>> freebsd-dri-amd64
>> freebsd-dri-x86
>> hpux10
>> hpux10-gcc
>> hpux10-static
>> hpux11-32
>> hpux11-32-static
>> hpux11-32-static-nothreads
>> hpux11-64
>> hpux11-64-static
>> hpux11-ia64
>> hpux11-ia64-static
>> hpux9
>> hpux9-gcc
>> irix6-64
>> irix6-64-static
>> irix6-n32
>> irix6-n32-static
>> irix6-o32
>> irix6-o32-static
>> linux
>> linux-alpha
>> linux-alpha-static
>> linux-debug
>> linux-directfb
>> linux-dri
>> linux-dri-debug
>> linux-dri-ppc
>> linux-dri-x86
>> linux-dri-x86-64
>> linux-dri-xcb
>> linux-fbdev
>> linux-glide
>> linux-ia64-icc
>> linux-ia64-icc-static
>> linux-icc
>> linux-icc-static
>> linux-indirect
>> linux-osmesa
>> linux-osmesa16
>> linux-osmesa16-static
>> linux-osmesa32
>> linux-ppc
>> linux-ppc-static
>> linux-profile
>> linux-solo
>> linux-solo-ia64
>> linux-solo-x86
>> linux-sparc
>> linux-sparc5
>> linux-static
>> linux-ultrasparc
>> linux-x86
>> linux-x86-32
>> linux-x86-64
>> linux-x86-64-debug
>> linux-x86-64-static
>> linux-x86-debug
>> linux-x86-glide
>> linux-x86-static
>> netbsd
>> openbsd
>> osf1
>> osf1-static
>> solaris-x86
>> solaris-x86-gcc
>> solaris-x86-gcc-static
>> sunos4
>> sunos4-gcc
>> sunos4-static
>> sunos5
>> sunos5-64-gcc
>> sunos5-gcc
>> sunos5-smp
>> sunos5-v8
>> sunos5-v8-static
>> sunos5-v9
>> sunos5-v9-cc-g++
>> sunos5-v9-static
>> ultrix-gcc
>>
>> Then type 'make <config>' (ex: 'make linux-x86')
>>
>> Or, run './configure' then 'make'
>> See './configure --help' for details
>>
>> (ignore the following error message)
>> make: *** [configs/current] Error 1
>
> It looks like the port should be either running configure then  
> make, or it should run "make darwin". But the port is set up to not  
> run configure, and then to run "make default".
>
> We have a bug for this already; you can add yourself to the bug's  
> Cc if you're interested in what happens:
>
> http://trac.macports.org/ticket/17995
>
>
>


From jeremyhu at macports.org  Tue Jan 20 23:49:38 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Tue, 20 Jan 2009 23:49:38 -0800
Subject: Mesa
In-Reply-To: <DBD58D03-E467-450A-9049-D3A9B2845D3C@macports.org>
References: <06B3AA9B-E1B5-4E03-BCFF-1C10A8CAC13D@comcast.net>
	<D9819347-29F5-46DE-A2B5-9FB64687D8DC@macports.org>
	<A044D164-79C7-4300-8995-6260C6D6ED76@comcast.net>
	<DBD58D03-E467-450A-9049-D3A9B2845D3C@macports.org>
Message-ID: <DC8E63F3-C4A6-4B17-91CF-8682B7BE90B5@macports.org>

Should be fixed in r45750


On Jan 20, 2009, at 23:26, Ryan Schmidt wrote:

> Frank J. R. Hanstick wrote:
>
>>> 	Oops.  Forgot xcode and MacPorts:  2.5 and 1.7.0 respectively.
>
>
> Ok, and based on other output you sent, running Mac OS X 10.4 on a  
> PowerPC Mac.
>
>
>> DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_x11_mesa/work/Mesa-7.2" && make default  
>> INSTALL_DIR=/opt/local X11_DIR=/usr/X11R6'
>>
>>
>> Please choose a configuration from the following list:
>> aix
>> aix-64
>> aix-64-static
>> aix-gcc
>> aix-static
>> beos
>> bluegene-osmesa
>> bluegene-xlc-osmesa
>> catamount-osmesa-pgi
>> config.mgw
>> darwin
>> darwin-fat-32bit
>> darwin-fat-all
>> freebsd
>> freebsd-dri
>> freebsd-dri-amd64
>> freebsd-dri-x86
>> hpux10
>> hpux10-gcc
>> hpux10-static
>> hpux11-32
>> hpux11-32-static
>> hpux11-32-static-nothreads
>> hpux11-64
>> hpux11-64-static
>> hpux11-ia64
>> hpux11-ia64-static
>> hpux9
>> hpux9-gcc
>> irix6-64
>> irix6-64-static
>> irix6-n32
>> irix6-n32-static
>> irix6-o32
>> irix6-o32-static
>> linux
>> linux-alpha
>> linux-alpha-static
>> linux-debug
>> linux-directfb
>> linux-dri
>> linux-dri-debug
>> linux-dri-ppc
>> linux-dri-x86
>> linux-dri-x86-64
>> linux-dri-xcb
>> linux-fbdev
>> linux-glide
>> linux-ia64-icc
>> linux-ia64-icc-static
>> linux-icc
>> linux-icc-static
>> linux-indirect
>> linux-osmesa
>> linux-osmesa16
>> linux-osmesa16-static
>> linux-osmesa32
>> linux-ppc
>> linux-ppc-static
>> linux-profile
>> linux-solo
>> linux-solo-ia64
>> linux-solo-x86
>> linux-sparc
>> linux-sparc5
>> linux-static
>> linux-ultrasparc
>> linux-x86
>> linux-x86-32
>> linux-x86-64
>> linux-x86-64-debug
>> linux-x86-64-static
>> linux-x86-debug
>> linux-x86-glide
>> linux-x86-static
>> netbsd
>> openbsd
>> osf1
>> osf1-static
>> solaris-x86
>> solaris-x86-gcc
>> solaris-x86-gcc-static
>> sunos4
>> sunos4-gcc
>> sunos4-static
>> sunos5
>> sunos5-64-gcc
>> sunos5-gcc
>> sunos5-smp
>> sunos5-v8
>> sunos5-v8-static
>> sunos5-v9
>> sunos5-v9-cc-g++
>> sunos5-v9-static
>> ultrix-gcc
>>
>> Then type 'make <config>' (ex: 'make linux-x86')
>>
>> Or, run './configure' then 'make'
>> See './configure --help' for details
>>
>> (ignore the following error message)
>> make: *** [configs/current] Error 1
>
> It looks like the port should be either running configure then make,  
> or it should run "make darwin". But the port is set up to not run  
> configure, and then to run "make default".
>
> We have a bug for this already; you can add yourself to the bug's Cc  
> if you're interested in what happens:
>
> http://trac.macports.org/ticket/17995
>
>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From talklists at newgeo.com  Wed Jan 21 00:35:05 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 00:35:05 -0800
Subject: Understanding what I am calling the mess that is perl modules
Message-ID: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>

Me again... Sorry

I need Tie::RDBM
If someone can tell me anything wrong I am doing, or better ways, I  
would be able to provide more ports back to MacPorts.

`port search p5-tie`
4 results, none of which appear to be what I want.

What are the possibilities Tie::RDBM is contained within one of the 4  
results macports found?  The answer to that should be 0.  If it is  
not, I am searching wrong and would like to know how to correctly  
search.  If I am searching correctly, there needs to be a standard way  
to resolve this where the contents of a module are put into the port  
file so it can be searched and found.

I have a feeling the answer is not 0.  That being the case, I would  
like to suggest no port be approved until this qualification for  
search is met.  ports may have 5000+ port files, but with this issue  
solved, it could appear to have many many more.

I am trying to add in Tie::RDBM and find this page:
http://search.cpan.org/~lds/Tie-DBI-1.02/lib/Tie/RDBM.pm

Version 0.70, so I would make my port file with a name of:
p5-Tie-RDBM 0.70
Which is going to translate to downloading a file of:
Tie-RDBM-0.70.tar.gz

I am betting dollars to donuts that will fail.  On the cpan page I see  
they want me to download Tie-DBI-1.02.tar.gz.

And there, I am lost, the version is way off, the name is off, there  
is no way MacPorts is going to figure this out.

I actually do not even understand why a port has to be made for  
anything in CPAN.  I am sure the publish a list of all their modules,  
how come that list can not just exist in MacPorts, and we can simply  
issue something like `sudo port install cpan-foo::bar::baz and have  
MacPorts do the rest.

For items that would not build right away, or if someone wants  
something tried, true, and tested, there could be a full port file.

Thanks for all the help, I did manage to submit a few portfiles to the  
tracker today.
--
Scott


From ryandesign at macports.org  Wed Jan 21 01:09:32 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 21 Jan 2009 03:09:32 -0600
Subject: Understanding what I am calling the mess that is perl modules
In-Reply-To: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
References: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
Message-ID: <5D23BC70-3DA3-4914-8E55-3726D8B2CE7A@macports.org>

On Jan 21, 2009, at 02:35, Scott Haneda wrote:

> I need Tie::RDBM
> If someone can tell me anything wrong I am doing, or better ways, I  
> would be able to provide more ports back to MacPorts.
>
> `port search p5-tie`
> 4 results, none of which appear to be what I want.
>
> What are the possibilities Tie::RDBM is contained within one of the  
> 4 results macports found?  The answer to that should be 0.  If it  
> is not, I am searching wrong and would like to know how to  
> correctly search.  If I am searching correctly, there needs to be a  
> standard way to resolve this where the contents of a module are put  
> into the port file so it can be searched and found.
>
> I have a feeling the answer is not 0.  That being the case, I would  
> like to suggest no port be approved until this qualification for  
> search is met.  ports may have 5000+ port files, but with this  
> issue solved, it could appear to have many many more.

I'm not sure this issue is limited to Perl modules. What if a user  
knows that they want the program "mogrify", but they do not know what  
software package provides it? "port search mogrify" does not tell  
you. You have to already know that it's provided by ImageMagick.  
MacPorts at this time seems to assume that the user either already  
knows what software package they want to install, or that they can  
find it using keywords from the description.

It might be nice to let the user search by what files are in the  
port. "port contents" tells you what's in a port, but only if it's  
already installed, which isn't very helpful if you're trying to  
figure out which port to install. Problem is the list of files in a  
port is not known to MacPorts until the port is installed. This could  
be more easily done if we had binary packages, but that is a long way  
off. There are also the occasional ports that install different files  
on different systems; one would have to take care that all possible  
files are included in the search.


> I am trying to add in Tie::RDBM and find this page:
> http://search.cpan.org/~lds/Tie-DBI-1.02/lib/Tie/RDBM.pm
>
> Version 0.70, so I would make my port file with a name of:
> p5-Tie-RDBM 0.70
> Which is going to translate to downloading a file of:
> Tie-RDBM-0.70.tar.gz
>
> I am betting dollars to donuts that will fail.  On the cpan page I  
> see they want me to download Tie-DBI-1.02.tar.gz.
>
> And there, I am lost, the version is way off, the name is off,  
> there is no way MacPorts is going to figure this out.

So the MacPorts port should probably be for the entire Tie::DBI 1.02  
package, not just for its Tie::RDBM subpackage. You can ask the author 
(s) of Tie::DBI why they have combined several perl modules into one  
package, but presumably it's because they all work together and  
require one another.


> I actually do not even understand why a port has to be made for  
> anything in CPAN.  I am sure the publish a list of all their  
> modules, how come that list can not just exist in MacPorts, and we  
> can simply issue something like `sudo port install cpan- 
> foo::bar::baz and have MacPorts do the rest.
>
> For items that would not build right away, or if someone wants  
> something tried, true, and tested, there could be a full port file.


I don't recall anyone having discussed such an idea before, so that's  
probably one reason why it hasn't been done. We could have that  
discussion now.

One problem with this approach is that of the version number.  
MacPorts ports are always of a particular version -- one which has  
been tested by its maintainer, or at least, by someone. When a new  
version is released, someone tests it and updates the port. The new  
version may have new bugs the committer didn't see, the new version  
may not even compile for everyone, but at least it was tested in some  
way, presumably on a Mac, by somebody. If you just make MacPorts a  
conduit to CPAN, there would be no testing of those modules by a  
MacPorts user at all.

Consider also how MacPorts works: there is a directory of portfiles,  
and a portindex file that lists them all. "port install" consults the  
index to know if the port exists. "port outdated" consults the index  
to know if your ports are outdated. If there are no portfiles for  
CPAN modules, how would they appear in the index? If they're not in  
the index, how would "port outdated" work? Would we have a separate  
index for CPAN modules?

I'm sure there are several more issues to consider; those are just  
off the top of my head. And of course again they're not limited to  
Perl modules from CPAN. One could also consider how this could apply  
to PHP modules from PEAR and PECL, Ruby gems, Octave packages, etc.



From blb at macports.org  Wed Jan 21 01:40:10 2009
From: blb at macports.org (Bryan Blackburn)
Date: Wed, 21 Jan 2009 02:40:10 -0700
Subject: p5 modules, get me started on one
In-Reply-To: <2AD35050-C46E-40C7-B993-4819F3F0CEE6@newgeo.com>
References: <20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
	<20090120073247.GR785@ninagal.withay.com>
	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
	<16926AEC-7084-4517-8338-B99FE9C35B41@newgeo.com>
	<20090121010109.GL965@ninagal.withay.com>
	<2AD35050-C46E-40C7-B993-4819F3F0CEE6@newgeo.com>
Message-ID: <20090121094010.GU965@ninagal.withay.com>

On Tue, Jan 20, 2009 at 05:50:23PM -0800, Scott Haneda said:
> On Jan 20, 2009, at 5:01 PM, Bryan Blackburn wrote:
[...]
>> Some perl modules come packaged in groups like that, which definitely 
>> can
>> cause confusion.  Maybe the best solution would be to list all actual
>> modules installed with the given port?  Then it may be easier to search 
>> for
>> it.
>
> List it in the port description?  Will that get searched?  How do I even 
> get a list of what is in these packages from the CPAN site?

In the long_description is what I was pondering; if you're running MacPorts
1.7 'port search' will look in (among other field) long_description by
default, with trunk you'd need to add the --long_description flag to search
it.  Anything more specific to perl modules would mean changing base and of
course deciding first how that would work, etc...

[...]
>> The base perl5.8 port should actually have what's in libnet like  
>> Net::SMTP,
>> so no port should actually be needed for this one.
>
>
> How would I know that?
> port search smtp
> All I see is
> p5-net-smtp_auth @0.08 (perl)
>     Perl5 SMTP client with AUTHentication
>
> If that is it, great, but how would I confirm it is in fact the same  
> thing?  All signs point to it being different.

In many cases, a person running 'port install ...' is probably more
interested in some final program and not just perl modules, so that's where
the dependency management comes into play.  This way various port
maintainers only need to determine the which/where question the one time for
these things and anyone else just lets port take it from there.

If you're one of those maintainers, then it definitely helps to know the
software you're dealing with.  In perl's case, what I've done in the past is
to query search.cpan.org for the specific module, which leads you to either
a distribution specific to that module or one that includes several modules.
>From that you'd just create the port and be done with it.

Also, knowing that Net::SMTP is with the base perl5.8 port is something I
just knew because it's part of the perl libnet stuff which was integrated
into perl core some time ago.

>
> Beginning to dislike perl and I have not written more than 100 lines of it 
> in my life :)

One advantage is the massive amount of modules already written to reduce the
amount of work you have to do; one disadvantage is all of the massive amount
of modules one must wade through to determine what you might actually need.
Of course using CPAN makes that easier but then that installs outside of
port, which means you can't depend on it for other ports or use
uninstall/activate/deactivate to manage it, etc.

I guess what I'm trying to say is, if there's an easy answer, I haven't
heard it.

Bryan


> --
> Scott

From talklists at newgeo.com  Wed Jan 21 02:48:48 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 02:48:48 -0800
Subject: Understanding what I am calling the mess that is perl modules
In-Reply-To: <5D23BC70-3DA3-4914-8E55-3726D8B2CE7A@macports.org>
References: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
	<5D23BC70-3DA3-4914-8E55-3726D8B2CE7A@macports.org>
Message-ID: <AADA7963-4768-4033-B6E5-CA8CF1ACC4ED@newgeo.com>

On Jan 21, 2009, at 1:09 AM, Ryan Schmidt wrote:
> On Jan 21, 2009, at 02:35, Scott Haneda wrote:
>
>> I need Tie::RDBM
>> If someone can tell me anything wrong I am doing, or better ways, I  
>> would be able to provide more ports back to MacPorts.
>>
>> `port search p5-tie`
>> 4 results, none of which appear to be what I want.
>>
>> What are the possibilities Tie::RDBM is contained within one of the  
>> 4 results macports found?  The answer to that should be 0.  If it  
>> is not, I am searching wrong and would like to know how to  
>> correctly search.  If I am searching correctly, there needs to be a  
>> standard way to resolve this where the contents of a module are put  
>> into the port file so it can be searched and found.
>>
>> I have a feeling the answer is not 0.  That being the case, I would  
>> like to suggest no port be approved until this qualification for  
>> search is met.  ports may have 5000+ port files, but with this  
>> issue solved, it could appear to have many many more.
>
> I'm not sure this issue is limited to Perl modules. What if a user  
> knows that they want the program "mogrify", but they do not know  
> what software package provides it? "port search mogrify" does not  
> tell you. You have to already know that it's provided by  
> ImageMagick. MacPorts at this time seems to assume that the user  
> either already knows what software package they want to install, or  
> that they can find it using keywords from the description.
>
> It might be nice to let the user search by what files are in the  
> port. "port contents" tells you what's in a port, but only if it's  
> already installed, which isn't very helpful if you're trying to  
> figure out which port to install. Problem is the list of files in a  
> port is not known to MacPorts until the port is installed. This  
> could be more easily done if we had binary packages, but that is a  
> long way off. There are also the occasional ports that install  
> different files on different systems; one would have to take care  
> that all possible files are included in the search.

Wow, `port contents` is pretty damn handy.  I see your points.   
However, and maybe it is just me looking at this from the perspective  
of a user who does not know much about this, much like me...

How did I get here?
I want to make an ASSP port, so I downloaded it, I learned it is a  
pretty simple port.  In all reality, it may not even need a port, it  
works fine with Apple's perl, and it is nothing more than a copy of  
some files and a single command to get it up and running.  In this  
case, a port my be total overkill for ASSP.

But... ASSP needs about 15 perl modules to work, and maybe even 20 or  
so if you want anti-virus.  This led me here.  I wanted to make a port  
since my past experience with php and mysql here was pretty nice.  I  
thought I would give back and also to my own gain.

There is CPAN, and what is troublesome about all this, is the ASSP  
distro has a simple install file you can run, and it runs down the  
CPAN tree and gets what it needs.  I have always been wary of CPAN,  
since I am under the impression it hooks into the Apple perl, and for  
an email server proxy, the last thing I need is for Apple to break my  
kit.

I guess there is Fink, but somewhere I also got the impression  
MacPorts was sort of the new Fink.

ASSP lists the perl modules I need.  I am not sure why the developer  
lists them out as sub modules, if you can not get to them without  
getting the entire master module as well.  He seems to know what he is  
doing, so I would guess many other developers just list the one module  
they are using, rather than the entire package.

I, as a end user of MacPorts, got pretty hung up on this.  If I wanted  
to use ASSP, I would just download it, and if I wanted to hand install  
the modules it needs via CPAN, I just copy and paste the list out of  
the ASSP notes.

In MacPorts, I can not do that.  I have to google the port ASSP wants,  
look to see if it is in MacPorts, if not, google again for the main  
package the module may be contained in, then see if MacPorts knows  
about that.  If not, I can then think about making a port file.

How is CPAN solving this?  Even if there is no master list of files,  
so we could get to the result of `port contents` ahead of time, their  
site seems so structured it would should not be too hard to get to  
that list.  I just do not know enough about this, and I am not really  
looking for an answer from you, but more just to relay my experience  
so you may take it under consideration.

This will be a gross simplification, but take LWP::Simple, if I need  
that, I learn it is inside libwww-perl...

Gisle Aas > libwww-perl-5.823 > LWP::Simple

That is just a copy and paste of the breadcrumbs from their cpan  
site.  While it would be a mess, just backing up one on the breadcrumb  
gets you where you need to be.  I am not saying to html scrape the  
site, but you get what I mean. The process is a burden, there has to  
be a way to solve this for new users in order to attract more users.

Maybe, at the very least, add a new category, such as port_contains.   
When I as a port creator make a port, I could then run `port contents`  
and put it into that variable.  Or heck, automate it, and make a `port  
prepare` command, which will create a port file ready to submit to  
trac, or even just sent it in, over the wire.

>> I am trying to add in Tie::RDBM and find this page:
>> http://search.cpan.org/~lds/Tie-DBI-1.02/lib/Tie/RDBM.pm
>>
>> Version 0.70, so I would make my port file with a name of:
>> p5-Tie-RDBM 0.70
>> Which is going to translate to downloading a file of:
>> Tie-RDBM-0.70.tar.gz
>>
>> I am betting dollars to donuts that will fail.  On the cpan page I  
>> see they want me to download Tie-DBI-1.02.tar.gz.
>>
>> And there, I am lost, the version is way off, the name is off,  
>> there is no way MacPorts is going to figure this out.
>
> So the MacPorts port should probably be for the entire Tie::DBI 1.02  
> package, not just for its Tie::RDBM subpackage. You can ask the  
> author(s) of Tie::DBI why they have combined several perl modules  
> into one package, but presumably it's because they all work together  
> and require one another.

Understood.  Thanks.
I think part of this is, I have a tendency to want the bare minimum.   
I am getting over it, but others are much more strict.  The times I  
have watched someone use CPAN, to stop using it, just because all this  
stuff scrolls over the screen, and they walk away feeling there are  
now 100's to 1000's of files that were put into their system, and they  
will never get rid of them.

MacPorts solves this in that, at least, you know the files are all in  
one place, no matter how messy.  a drag of a folder more or less  
removes MacPorts sans a few dot files and maybe a startup item or  
launchd item.

My gut does not want me to get the entire parent package, I guess I  
just need to get over that.

>> I actually do not even understand why a port has to be made for  
>> anything in CPAN.  I am sure the publish a list of all their  
>> modules, how come that list can not just exist in MacPorts, and we  
>> can simply issue something like `sudo port install cpan- 
>> foo::bar::baz and have MacPorts do the rest.
>>
>> For items that would not build right away, or if someone wants  
>> something tried, true, and tested, there could be a full port file.
>
> I don't recall anyone having discussed such an idea before, so  
> that's probably one reason why it hasn't been done. We could have  
> that discussion now.
>
> One problem with this approach is that of the version number.  
> MacPorts ports are always of a particular version -- one which has  
> been tested by its maintainer, or at least, by someone. When a new  
> version is released, someone tests it and updates the port. The new  
> version may have new bugs the committer didn't see, the new version  
> may not even compile for everyone, but at least it was tested in  
> some way, presumably on a Mac, by somebody. If you just make  
> MacPorts a conduit to CPAN, there would be no testing of those  
> modules by a MacPorts user at all.

Ok, I understand that part.  And I hope my efforts are not being  
counterproductive, as what you describe above, all the bad parts, is  
what I am doing.  And I was almost proud of my work :)

I need a large handful of perl modules.  I do not generally code in  
perl, and I certainly have no intention of writing any test cases of  
the modules on my system.

I copy a stub portfile, edit the name of the folder to prepend p5- and  
replace :: with -.  From there, I will edit the port, change the name  
and version in the port, pop in my email address, copy and paste the  
two descriptions from the CPAN page, and drop in a url.

I then run `sudo port -d install` and let it error out, copy the  
checksums, put those in the port file, and install the bugger.

If it compiles, I call it a day, and submit it to trac.  Is this bad?   
I am not testing the module in any way, other than to make sure it  
compiles pretty clean.  And by "pretty clean" I just mean that as the  
compile is happening at a million lines a second on my screen, unless  
I catch something, I am just waiting to make sure it builds and I get  
a success message from the port install command.

Now, with ASSP, I will indeed test it and make it work, but these  
little bits of perl are just a means to an end for me.

Am I messing up a process with my methods?  It was not my intention to  
muddy up the port pool.

> Consider also how MacPorts works: there is a directory of portfiles,  
> and a portindex file that lists them all. "port install" consults  
> the index to know if the port exists. "port outdated" consults the  
> index to know if your ports are outdated. If there are no portfiles  
> for CPAN modules, how would they appear in the index? If they're not  
> in the index, how would "port outdated" work? Would we have a  
> separate index for CPAN modules?

I was thinking, if there is a portfile, it means a human made it, and  
took the time to make it work for the most part, even if only in the  
poor way in which I test it above.  So if there is a port file, that  
takes priority.  If not, fall back to automatic mode, to get the user  
the port file.  Grab the module, grab the most current version, build  
it out, and be done with it.  You would not consult the index in these  
cases, this would have to happen against a remote mapping database of  
sorts just for CPAN stuff.

> I'm sure there are several more issues to consider; those are just  
> off the top of my head. And of course again they're not limited to  
> Perl modules from CPAN. One could also consider how this could apply  
> to PHP modules from PEAR and PECL, Ruby gems, Octave packages, etc.


Indeed, and again, I do not know too much about this stuff.  I fall in  
the middle of all this, where I spend most of my day sysadmin, or  
developing in the actual code.

Thanks again for having this dialogue.  I am indeed making progress  
and learning about this system.  It was a long and windy road to get  
to a `sudo port install assp` but I am getting there.
--
Scott

From talklists at newgeo.com  Wed Jan 21 03:00:16 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 03:00:16 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <20090121094010.GU965@ninagal.withay.com>
References: <20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
	<20090120073247.GR785@ninagal.withay.com>
	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
	<16926AEC-7084-4517-8338-B99FE9C35B41@newgeo.com>
	<20090121010109.GL965@ninagal.withay.com>
	<2AD35050-C46E-40C7-B993-4819F3F0CEE6@newgeo.com>
	<20090121094010.GU965@ninagal.withay.com>
Message-ID: <2778265B-1293-4ED9-84AF-01E933702F7A@newgeo.com>

On Jan 21, 2009, at 1:40 AM, Bryan Blackburn wrote:
> On Tue, Jan 20, 2009 at 05:50:23PM -0800, Scott Haneda said:
>> On Jan 20, 2009, at 5:01 PM, Bryan Blackburn wrote:
> [...]
>>> Some perl modules come packaged in groups like that, which  
>>> definitely
>>> can
>>> cause confusion.  Maybe the best solution would be to list all  
>>> actual
>>> modules installed with the given port?  Then it may be easier to  
>>> search
>>> for
>>> it.
>>
>> List it in the port description?  Will that get searched?  How do I  
>> even
>> get a list of what is in these packages from the CPAN site?
>
> In the long_description is what I was pondering; if you're running  
> MacPorts
> 1.7 'port search' will look in (among other field) long_description by
> default, with trunk you'd need to add the --long_description flag to  
> search
> it.  Anything more specific to perl modules would mean changing base  
> and of
> course deciding first how that would work, etc...

Nice to know, thanks, I was not aware of --long_description

Seems an ok way to deal with it, not ideal to me though.  I am not  
sure if this problem is just perl module related, or is more generic.   
If it would be appropriate, the idea of adding a new variable to port  
files may be a fair idea.

file_contains or whatever is appropriate, which could then be searched  
on by default.  It seems very common that this comes up.

> [...]
>>> The base perl5.8 port should actually have what's in libnet like
>>> Net::SMTP,
>>> so no port should actually be needed for this one.
>>
>>
>> How would I know that?
>> port search smtp
>> All I see is
>> p5-net-smtp_auth @0.08 (perl)
>>    Perl5 SMTP client with AUTHentication
>>
>> If that is it, great, but how would I confirm it is in fact the same
>> thing?  All signs point to it being different.
>
> In many cases, a person running 'port install ...' is probably more
> interested in some final program and not just perl modules, so  
> that's where
> the dependency management comes into play.  This way various port
> maintainers only need to determine the which/where question the one  
> time for
> these things and anyone else just lets port take it from there.

Correct, and the more I think about it, the more I may be looking at  
this wrong.  My end game here is to get ASSP ported.  I need 20 or so  
perl modules to go with it, but once I get those, and build the  
dependency tree in the ASSP port file, no other user will ever care  
about the issues I am currently running into.

> If you're one of those maintainers, then it definitely helps to know  
> the
> software you're dealing with.  In perl's case, what I've done in the  
> past is
> to query search.cpan.org for the specific module, which leads you to  
> either
> a distribution specific to that module or one that includes several  
> modules.

That is exactly where I have been spending my time as well.  To be  
honest, I just wish the developer of ASSP had listed the parent perl  
module rather then the submodule, it would have made this seem a heck  
of a lot easier.

>> From that you'd just create the port and be done with it.
>
> Also, knowing that Net::SMTP is with the base perl5.8 port is  
> something I
> just knew because it's part of the perl libnet stuff which was  
> integrated
> into perl core some time ago.

And that there is the main major problem with this.  While not with  
Net::SMTP, but other perl modules, this bit me.  I need net:foo and  
did not find it, so I made a port.  I later learned net:foo was  
already in net:main so I wasted my time making the port.  In this  
case, these ports are mostly copy and paste, so not a big deal, but it  
could have been a larger waste of time.

This is the main thing I think needs solving, and it sounds like it  
can, with better search, a new field in the port file, and or  
automatic retrieval of some perl module index file that has some  
mappings in it. It may take all those suggestions, I am not sure.

The question of "How does a new user know that Net::SMTP is part of  
the base?" is a problem.

>> Beginning to dislike perl and I have not written more than 100  
>> lines of it
>> in my life :)
>
> One advantage is the massive amount of modules already written to  
> reduce the
> amount of work you have to do; one disadvantage is all of the  
> massive amount
> of modules one must wade through to determine what you might  
> actually need.
> Of course using CPAN makes that easier but then that installs  
> outside of
> port, which means you can't depend on it for other ports or use
> uninstall/activate/deactivate to manage it, etc.

Also, is it still true than CPAN can get clobbered by Apple Updates?   
This is one of the best selling points of MacPorts.

> I guess what I'm trying to say is, if there's an easy answer, I  
> haven't
> heard it.


Rarely is it easy :)  Curious, without going into a lot of detail, how  
does the hugely raves about apt-get and equivalent get past all this?
--
Scott


From raimue at macports.org  Wed Jan 21 03:00:40 2009
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Wed, 21 Jan 2009 12:00:40 +0100
Subject: Understanding what I am calling the mess that is perl modules
In-Reply-To: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
References: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
Message-ID: <49770058.4010804@macports.org>

Scott Haneda wrote:
> I actually do not even understand why a port has to be made for  
> anything in CPAN.  I am sure the publish a list of all their modules,  
> how come that list can not just exist in MacPorts, and we can simply  
> issue something like `sudo port install cpan-foo::bar::baz and have  
> MacPorts do the rest.
> 
> For items that would not build right away, or if someone wants  
> something tried, true, and tested, there could be a full port file.

There is cpan2port written by Marc [1] which is meant to create
Portfiles from CPAN. It is new and I don't know if it works in all
cases, so any help from someone with a Perl background would be appreciated.

This should also be moved to our contrib section [2] and then made
available as a port so it's easier to use for Portfile authors.

Rainer

[1]
http://lists.macosforge.org/pipermail/macports-users/2008-November/012298.html
[2] http://svn.macports.org/repository/macports/contrib/

From milosh at macports.org  Wed Jan 21 03:19:39 2009
From: milosh at macports.org (Emmanuel Hainry)
Date: Wed, 21 Jan 2009 12:19:39 +0100
Subject: Understanding what I am calling the mess that is perl modules
In-Reply-To: <5D23BC70-3DA3-4914-8E55-3726D8B2CE7A@macports.org>
References: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
	<5D23BC70-3DA3-4914-8E55-3726D8B2CE7A@macports.org>
Message-ID: <20090121111939.GA12488@weetamoe.loria.fr>

Citando Ryan Schmidt :
> On Jan 21, 2009, at 02:35, Scott Haneda wrote:
>
>> I actually do not even understand why a port has to be made for  
>> anything in CPAN.  I am sure the publish a list of all their modules, 
>> how come that list can not just exist in MacPorts, and we can simply 
>> issue something like `sudo port install cpan-foo::bar::baz and have 
>> MacPorts do the rest.
>>
>> For items that would not build right away, or if someone wants  
>> something tried, true, and tested, there could be a full port file.
>
>
> I don't recall anyone having discussed such an idea before, so that's  
> probably one reason why it hasn't been done. We could have that  
> discussion now.
>

There was an attempt at that: cpan2port
[http://www.nabble.com/announce:-cpan2port-td20415884.html]. I don't
know what is its current status, but that's a nice thing. If it was also
possible to have this for python eggs, ruby gems, ctan, etc. However,
debian has had such a tool for a long time, other package managers also
have.

Concerning the possibility to search for which port I should install to
get which command, I usually try google with the name of the thing I
want to get and "debian". It usually gives me the name of the debian
package which is usually easily translatable into macports' naming.
Once more however, debian, pkgsrc and probably other ones provide a way
to search for the files provided by a package. In debian, as they make
binary packages, it is "simple". In pkgsrc, it relies on their build in
a sandbox which only uses the specified dependencies (not anything from
/usr/local or /usr if it is not explicitly said in the Makefile) and
hence builds exactly the same on machines with different things
installed.

Is macports bound to reinvent wheels over and over?

Best,

milosh
-------------- 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/20090121/9e73ab60/attachment.bin>

From talklists at newgeo.com  Wed Jan 21 03:23:49 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 03:23:49 -0800
Subject: Can not get Net::SysLog installed
Message-ID: <0D6FDE1D-8E93-4690-B38C-C51565B0B5F0@newgeo.com>

Can someone tell me where I am going wrong with this port?

Creating software index in /Users/me/macports
Adding port perl/p5-file-readbackwards
Adding port perl/p5-mail-spf
Adding port perl/p5-mail-spf-query
Adding port perl/p5-mail-srs
Adding port perl/p5-net-cidr-lite
Adding port perl/p5-net-ip-match-regexp
Adding port perl/p5-net-senderbase
Adding port perl/p5-net-syslog
Adding port perl/p5-tie-dbi

Total number of ports parsed:	9
Ports successfully parsed:	9	
Ports failed:			0


/Users/me/macports/perl/p5-net-syslog
cat Portfile
# $Id$
PortSystem 1.0
PortGroup perl5 1.0

perl5.setup             net-syslog 0.03
maintainers             hostwizard.com:scott

description             Net::Syslog - Perl extension for sending  
syslog messages directly to a remote syslogd.

long_description        Net::Syslog implements the intra-host syslog  
forwarding \
			protocol. It is not intended to replace the Sys::Syslog \
			or Unix::Syslog modules, but instead to provide a method \
			of using syslog when a local syslogd is unavailable or \
			when you don't want to write syslog messages to the \
			local syslog

homepage		http://search.cpan.org/~lhoward/Net-Syslog-0.03/Syslog.pm

checksums           	md5     0201f8ac355c6509e8f232179f0a54fd \
                     	sha1    8b633f4f51540eb94240157e7c7683658ed4461b \
                     	rmd160  309b3d18afc6ddbfb0eba4a1aaba5b6aa0c45397

platforms               darwin


* I am in this ports dir /Users/me/macports/perl/p5-net-syslog

Below is lint, clean, and isntall..

---***------***------***------***------***------***------***---
$sudo port lint
--->  Verifying Portfile for p5-net-syslog
--->  0 errors and 0 warnings found.

---***------***------***------***------***------***------***---
$sudo port -d clean
DEBUG: Changing to port directory: /Users/me/macports/perl/p5-net-syslog
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: Using group file /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/_resources/port1.0/group/perl5-1.0.tcl
DEBUG: adding the default universal variant
DEBUG: Requested variant darwin is not provided by port p5-net-syslog.
DEBUG: Requested variant i386 is not provided by port p5-net-syslog.
DEBUG: Requested variant macosx is not provided by port p5-net-syslog.
DEBUG: Changing to port directory: /Users/me/macports/perl/p5-net-syslog
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: Using group file /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/_resources/port1.0/group/perl5-1.0.tcl
DEBUG: adding the default universal variant
DEBUG: Requested variant darwin is not provided by port p5-net-syslog.
DEBUG: Requested variant i386 is not provided by port p5-net-syslog.
DEBUG: Requested variant macosx is not provided by port p5-net-syslog.
DEBUG: Executing org.macports.main (p5-net-syslog)
--->  Cleaning p5-net-syslog
DEBUG: Executing org.macports.clean (p5-net-syslog)
--->  Removing build directory for p5-net-syslog
DEBUG: Removing directory: /opt/local/var/macports/build/ 
_Users_me_macports_perl_p5-net-syslog
DEBUG: delete: /opt/local/var/macports/build/ 
_Users_me_macports_perl_p5-net-syslog
DEBUG: Removing symlink: /Users/me/macports/perl/p5-net-syslog/work
DEBUG: delete: /Users/me/macports/perl/p5-net-syslog/work

---***------***------***------***------***------***------***---
$sudo port -d install
DEBUG: Changing to port directory: /Users/me/macports/perl/p5-net-syslog
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: Using group file /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/_resources/port1.0/group/perl5-1.0.tcl
DEBUG: adding the default universal variant
DEBUG: Requested variant darwin is not provided by port p5-net-syslog.
DEBUG: Requested variant i386 is not provided by port p5-net-syslog.
DEBUG: Requested variant macosx is not provided by port p5-net-syslog.
DEBUG: Changing to port directory: /Users/me/macports/perl/p5-net-syslog
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: Using group file /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/_resources/port1.0/group/perl5-1.0.tcl
DEBUG: adding the default universal variant
DEBUG: Requested variant darwin is not provided by port p5-net-syslog.
DEBUG: Requested variant i386 is not provided by port p5-net-syslog.
DEBUG: Requested variant macosx is not provided by port p5-net-syslog.
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/lang/perl5
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 no' specified, so not adding the default  
universal variant
DEBUG: Requested variant darwin is not provided by port perl5.
DEBUG: Requested variant i386 is not provided by port perl5.
DEBUG: Requested variant macosx is not provided by port perl5.
DEBUG: Searching for dependency: perl5
DEBUG: Found Dependency: receipt exists for perl5
DEBUG: Executing org.macports.main (p5-net-syslog)
--->  Fetching p5-net-syslog
DEBUG: Executing org.macports.fetch (p5-net-syslog)
--->  Verifying checksum(s) for p5-net-syslog
DEBUG: Executing org.macports.checksum (p5-net-syslog)
--->  Checksumming net-syslog-0.03.tar.gz
DEBUG: Correct (md5) checksum for net-syslog-0.03.tar.gz
DEBUG: Correct (sha1) checksum for net-syslog-0.03.tar.gz
DEBUG: Correct (rmd160) checksum for net-syslog-0.03.tar.gz
--->  Extracting p5-net-syslog
DEBUG: Executing org.macports.extract (p5-net-syslog)
--->  Extracting net-syslog-0.03.tar.gz
DEBUG: setting option extract.args to /opt/local/var/macports/ 
distfiles/perl5/net-syslog-0.03.tar.gz
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
_Users_me_macports_perl_p5-net-syslog/work" && gzip -dc /opt/local/var/ 
macports/distfiles/perl5/net-syslog-0.03.tar.gz | /usr/bin/gnutar --no- 
same-owner -xf -'

gzip: /opt/local/var/macports/distfiles/perl5/net-syslog-0.03.tar.gz:  
not in gzip format
DEBUG: Executing org.macports.patch (p5-net-syslog)
--->  Configuring p5-net-syslog
DEBUG: Using compiler 'Mac OS X gcc 4.0'
DEBUG: Executing org.macports.configure (p5-net-syslog)
DEBUG: Environment: CFLAGS='-O2' CPPFLAGS='-I/opt/local/include'  
CXXFLAGS='-O2' MACOSX_DEPLOYMENT_TARGET='10.5' CPP='/usr/bin/cpp-4.0'  
CXX='/usr/bin/g++-4.0' F90FLAGS='-O2' LDFLAGS='-L/opt/local/lib'  
FCFLAGS='-O2' OBJC='/usr/bin/gcc-4.0' INSTALL='/usr/bin/install -c'  
OBJCFLAGS='-O2' FFLAGS='-O2' CC='/usr/bin/gcc-4.0'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
_Users_me_macports_perl_p5-net-syslog/work/net-syslog-0.03" && /opt/ 
local/bin/perl Makefile.PL INSTALLDIRS=vendor'
sh: line 0: cd: /opt/local/var/macports/build/ 
_Users_me_macports_perl_p5-net-syslog/work/net-syslog-0.03: No such  
file or directory
Error: Target org.macports.configure returned: configure failure:  
shell command " cd "/opt/local/var/macports/build/ 
_Users_me_macports_perl_p5-net-syslog/work/net-syslog-0.03" && /opt/ 
local/bin/perl Makefile.PL INSTALLDIRS=vendor " returned error 1
Command output: sh: line 0: cd: /opt/local/var/macports/build/ 
_Users_me_macports_perl_p5-net-syslog/work/net-syslog-0.03: No such  
file or directory

Warning: the following items did not execute (for p5-net-syslog):  
org.macports.activate org.macports.configure org.macports.build  
org.macports.destroot org.macports.install
Error: Status 1 encountered during processing.

--
Scott


From jmr at macports.org  Wed Jan 21 03:40:07 2009
From: jmr at macports.org (Joshua Root)
Date: Wed, 21 Jan 2009 22:40:07 +1100
Subject: Understanding what I am calling the mess that is perl modules
In-Reply-To: <49770058.4010804@macports.org>
References: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
	<49770058.4010804@macports.org>
Message-ID: <49770997.4010700@macports.org>

Rainer M?ller wrote:
> Scott Haneda wrote:
>> I actually do not even understand why a port has to be made for  
>> anything in CPAN.  I am sure the publish a list of all their modules,  
>> how come that list can not just exist in MacPorts, and we can simply  
>> issue something like `sudo port install cpan-foo::bar::baz and have  
>> MacPorts do the rest.
>>
>> For items that would not build right away, or if someone wants  
>> something tried, true, and tested, there could be a full port file.
> 
> There is cpan2port written by Marc [1] which is meant to create
> Portfiles from CPAN. It is new and I don't know if it works in all
> cases, so any help from someone with a Perl background would be appreciated.
> 
> This should also be moved to our contrib section [2] and then made
> available as a port so it's easier to use for Portfile authors.
> 
> Rainer
> 
> [1]
> http://lists.macosforge.org/pipermail/macports-users/2008-November/012298.html
> [2] http://svn.macports.org/repository/macports/contrib/

Integrating something like cpan2port more directly into MacPorts as
Scott described would be a neat project. There a bunch of implementation
and UI issues, but I don't think they're insurmountable. As usual, it
hasn't been done yet simply because nobody has had the time and
motivation to do it. And of course cpan2port is a great first step.

- Josh

From jmr at macports.org  Wed Jan 21 03:47:24 2009
From: jmr at macports.org (Joshua Root)
Date: Wed, 21 Jan 2009 22:47:24 +1100
Subject: Can not get Net::SysLog installed
In-Reply-To: <0D6FDE1D-8E93-4690-B38C-C51565B0B5F0@newgeo.com>
References: <0D6FDE1D-8E93-4690-B38C-C51565B0B5F0@newgeo.com>
Message-ID: <49770B4C.1030108@macports.org>

Scott Haneda wrote:
> Can someone tell me where I am going wrong with this port?

> perl5.setup             net-syslog 0.03

You've used the wrong case here. Also the checksums are wrong. :-)

- Josh

From talklists at newgeo.com  Wed Jan 21 04:09:48 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 04:09:48 -0800
Subject: Can not get Net::SysLog installed
In-Reply-To: <49770B4C.1030108@macports.org>
References: <0D6FDE1D-8E93-4690-B38C-C51565B0B5F0@newgeo.com>
	<49770B4C.1030108@macports.org>
Message-ID: <67915607-F6FF-44ED-A6F2-DD073AAB10D4@newgeo.com>

On Jan 21, 2009, at 3:47 AM, Joshua Root wrote:

> Scott Haneda wrote:
>> Can someone tell me where I am going wrong with this port?
>
>> perl5.setup             net-syslog 0.03
>
> You've used the wrong case here. Also the checksums are wrong. :-)


Strange, I have never bothered with case since OS X is non case, I  
assume this is failing on the download, since the case is wrong?  I  
will go fiddle it and see what happens.

Thanks.
--
Scott


From talklists at newgeo.com  Wed Jan 21 04:18:19 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 04:18:19 -0800
Subject: Can not get Net::SysLog installed
In-Reply-To: <49770B4C.1030108@macports.org>
References: <0D6FDE1D-8E93-4690-B38C-C51565B0B5F0@newgeo.com>
	<49770B4C.1030108@macports.org>
Message-ID: <32CB2819-F8E9-44B0-A42B-EF8DFA947702@newgeo.com>

On Jan 21, 2009, at 3:47 AM, Joshua Root wrote:

> Scott Haneda wrote:
>> Can someone tell me where I am going wrong with this port?
>
>> perl5.setup             net-syslog 0.03
>
> You've used the wrong case here. Also the checksums are wrong. :-)


Ok, got it to work, but I had a empty download file and a messed up  
TMP file.  I deleted them in the Finder and all was well. They were  
at /opt/local/var/macports/distfiles/perl5/
What is the port command to clean those out?

I tried sudo port uninstall and sudo port clean and neither worked for  
me.
--
Scott


From jmr at macports.org  Wed Jan 21 04:23:20 2009
From: jmr at macports.org (Joshua Root)
Date: Wed, 21 Jan 2009 23:23:20 +1100
Subject: Can not get Net::SysLog installed
In-Reply-To: <32CB2819-F8E9-44B0-A42B-EF8DFA947702@newgeo.com>
References: <0D6FDE1D-8E93-4690-B38C-C51565B0B5F0@newgeo.com>
	<49770B4C.1030108@macports.org>
	<32CB2819-F8E9-44B0-A42B-EF8DFA947702@newgeo.com>
Message-ID: <497713B8.10903@macports.org>

Scott Haneda wrote:
> On Jan 21, 2009, at 3:47 AM, Joshua Root wrote:
> 
>> Scott Haneda wrote:
>>> Can someone tell me where I am going wrong with this port?
>>
>>> perl5.setup             net-syslog 0.03
>>
>> You've used the wrong case here. Also the checksums are wrong. :-)
> 
> 
> Ok, got it to work, but I had a empty download file and a messed up TMP
> file.  I deleted them in the Finder and all was well. They were at
> /opt/local/var/macports/distfiles/perl5/
> What is the port command to clean those out?
> 
> I tried sudo port uninstall and sudo port clean and neither worked for me.

Clean can take some options, see the port man page. `sudo port clean
--dist` will delete the distfile.

- Josh

From talklists at newgeo.com  Wed Jan 21 04:27:45 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 04:27:45 -0800
Subject: Understanding what I am calling the mess that is perl modules
In-Reply-To: <20090121111939.GA12488@weetamoe.loria.fr>
References: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
	<5D23BC70-3DA3-4914-8E55-3726D8B2CE7A@macports.org>
	<20090121111939.GA12488@weetamoe.loria.fr>
Message-ID: <A1226A1F-8C44-4BF0-BE92-DAC97C9DEF3C@newgeo.com>

On Jan 21, 2009, at 3:19 AM, Emmanuel Hainry wrote:

> There was an attempt at that: cpan2port
> [http://www.nabble.com/announce:-cpan2port-td20415884.html]. I don't
> know what is its current status, but that's a nice thing. If it was  
> also
> possible to have this for python eggs, ruby gems, ctan, etc. However,
> debian has had such a tool for a long time, other package managers  
> also
> have.


Cool, thanks.
I downloaded it, and moved it to ~/bin which is in my path.

When I run it with no arguments to get to help for it, I get errors,  
which reference macports, which I should not, since I am using the  
built in perl in OS X.

$whereis perl
/usr/bin/perl

perl cpan2port
Can't locate Module/Depends.pm in @INC (@INC contains: /opt/local/lib/ 
perl5/5.8.9/darwin-2level /opt/local/lib/perl5/5.8.9 /opt/local/lib/ 
perl5/site_perl/5.8.9/darwin-2level /opt/local/lib/perl5/site_perl/ 
5.8.9 /opt/local/lib/perl5/site_perl /opt/local/lib/perl5/vendor_perl/ 
5.8.9/darwin-2level /opt/local/lib/perl5/vendor_perl/5.8.9 /opt/local/ 
lib/perl5/vendor_perl /Users/me/bin) at cpan2port line 54.
BEGIN failed--compilation aborted at cpan2port line 54.

Anyone got any ideas as to what is going on, not so much specifically  
to this, but why has my local perl been messed with?

me at mes-macbook:~/bin/ $/usr/bin/perl -v

This is perl, v5.8.8 built for darwin-thread-multi-2level
(with 1 registered patch, see perl -V for more detail)

Copyright 1987-2006, Larry Wall

Perl may be copied only under the terms of either the Artistic License  
or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to  
the
Internet, point your browser at http://www.perl.org/, the Perl Home  
Page.

me at mes-macbook:~/bin/ $/opt/local/bin/perl -v

This is perl, v5.8.9 built for darwin-2level

Copyright 1987-2008, Larry Wall

Perl may be copied only under the terms of either the Artistic License  
or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to  
the
Internet, point your browser at http://www.perl.org/, the Perl Home  
Page.

--
Scott


From talklists at newgeo.com  Wed Jan 21 04:34:43 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 04:34:43 -0800
Subject: Understanding what I am calling the mess that is perl modules
In-Reply-To: <A1226A1F-8C44-4BF0-BE92-DAC97C9DEF3C@newgeo.com>
References: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
	<5D23BC70-3DA3-4914-8E55-3726D8B2CE7A@macports.org>
	<20090121111939.GA12488@weetamoe.loria.fr>
	<A1226A1F-8C44-4BF0-BE92-DAC97C9DEF3C@newgeo.com>
Message-ID: <E4A2D53F-A5AC-4188-A893-7C33FE889F91@newgeo.com>

On Jan 21, 2009, at 4:27 AM, Scott Haneda wrote:

> On Jan 21, 2009, at 3:19 AM, Emmanuel Hainry wrote:
>
>> There was an attempt at that: cpan2port
>> [http://www.nabble.com/announce:-cpan2port-td20415884.html]. I don't
>> know what is its current status, but that's a nice thing. If it was  
>> also
>> possible to have this for python eggs, ruby gems, ctan, etc. However,
>> debian has had such a tool for a long time, other package managers  
>> also
>> have.
>
>
> Cool, thanks.
> I downloaded it, and moved it to ~/bin which is in my path.
>
> When I run it with no arguments to get to help for it, I get errors,  
> which reference macports, which I should not, since I am using the  
> built in perl in OS X.
>
> $whereis perl
> /usr/bin/perl


I think I am sort of seeing what is going on here. perl -V is using  
the macports version for some reason.   would think that `perl` needs  
to continue to use the OS X perl, and that I would need to call out  
the /opt/local/bin/perl when I want to use the MacPorts one.

I came to this conclusion since when making a port, one of the main  
things the port does, is read in files and do a find and replace on  
the built in perl and stuff in /opt/local/bin/perl.

If that is the case, then it has to be my .bashrc file that is messing  
with the proper behavior.

I have the usual
export PATH="$PATH:$HOME/bin"

And I added in
# For MacPorts
export PATH=/opt/local/bin:/opt/local/sbin:$PATH
export DISPLAY=:0.0
export EDITOR=/usr/bin/mate

I had to ditch the pre-installed .profile since it did not work for  
me. Maybe I should have referenced it from this file.  How do I tell  
the shell to use a certain order on where perl is located, or is that  
the wrong way to solve this?

Also, is there any way for EDITOR to be dynamic, so that when I am on  
the actual machine I want to use mate as my editor, but if I am over  
ssh, I want to use a terminal based editor.  Is that just a matter of  
wrapping the default in a condition that checks where I am at?
--
Scott


From ryandesign at macports.org  Wed Jan 21 04:46:25 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 21 Jan 2009 06:46:25 -0600
Subject: Understanding what I am calling the mess that is perl modules
In-Reply-To: <E4A2D53F-A5AC-4188-A893-7C33FE889F91@newgeo.com>
References: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
	<5D23BC70-3DA3-4914-8E55-3726D8B2CE7A@macports.org>
	<20090121111939.GA12488@weetamoe.loria.fr>
	<A1226A1F-8C44-4BF0-BE92-DAC97C9DEF3C@newgeo.com>
	<E4A2D53F-A5AC-4188-A893-7C33FE889F91@newgeo.com>
Message-ID: <729ED907-738E-4E26-B105-6B22347328B4@macports.org>


On Jan 21, 2009, at 06:34, Scott Haneda wrote:

> On Jan 21, 2009, at 4:27 AM, Scott Haneda wrote:
>
>> On Jan 21, 2009, at 3:19 AM, Emmanuel Hainry wrote:
>>
>>> There was an attempt at that: cpan2port
>>> [http://www.nabble.com/announce:-cpan2port-td20415884.html]. I don't
>>> know what is its current status, but that's a nice thing. If it  
>>> was also
>>> possible to have this for python eggs, ruby gems, ctan, etc.  
>>> However,
>>> debian has had such a tool for a long time, other package  
>>> managers also
>>> have.
>>
>>
>> Cool, thanks.
>> I downloaded it, and moved it to ~/bin which is in my path.
>>
>> When I run it with no arguments to get to help for it, I get  
>> errors, which reference macports, which I should not, since I am  
>> using the built in perl in OS X.
>>
>> $whereis perl
>> /usr/bin/perl
>
>
> I think I am sort of seeing what is going on here. perl -V is using  
> the macports version for some reason.   would think that `perl`  
> needs to continue to use the OS X perl, and that I would need to  
> call out the /opt/local/bin/perl when I want to use the MacPorts one.

If you list /opt/local/bin first in your path, before /usr/bin, then  
sure, MacPorts perl will be used (in your Terminal) in preference to  
Apple perl. Same for any other program that exists in both locations.  
That's the whole reason we recommend putting (and set up for you, in  
the default .profile) /opt/local/bin first in the path -- so that you  
get MacPorts versions where available, since they are usually newer.


> I came to this conclusion since when making a port, one of the main  
> things the port does, is read in files and do a find and replace on  
> the built in perl and stuff in /opt/local/bin/perl.
>
> If that is the case, then it has to be my .bashrc file that is  
> messing with the proper behavior.
>
> I have the usual
> export PATH="$PATH:$HOME/bin"
>
> And I added in
> # For MacPorts
> export PATH=/opt/local/bin:/opt/local/sbin:$PATH
> export DISPLAY=:0.0
> export EDITOR=/usr/bin/mate
>
> I had to ditch the pre-installed .profile since it did not work for  
> me. Maybe I should have referenced it from this file.  How do I  
> tell the shell to use a certain order on where perl is located, or  
> is that the wrong way to solve this?

The shell searches for binaries in the paths in PATH and runs it in  
the first path where it's found.


> Also, is there any way for EDITOR to be dynamic, so that when I am  
> on the actual machine I want to use mate as my editor, but if I am  
> over ssh, I want to use a terminal based editor.  Is that just a  
> matter of wrapping the default in a condition that checks where I  
> am at?

I would also be interested in knowing how to set that up. I've wanted  
this many times but never really looked into what I would need to do.



From khillig at umich.edu  Wed Jan 21 05:04:16 2009
From: khillig at umich.edu (Kurt Hillig)
Date: Wed, 21 Jan 2009 08:04:16 -0500 (EST)
Subject: Understanding what I am calling the mess that is perl modules
In-Reply-To: <729ED907-738E-4E26-B105-6B22347328B4@macports.org>
References: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
	<5D23BC70-3DA3-4914-8E55-3726D8B2CE7A@macports.org>
	<20090121111939.GA12488@weetamoe.loria.fr>
	<A1226A1F-8C44-4BF0-BE92-DAC97C9DEF3C@newgeo.com>
	<E4A2D53F-A5AC-4188-A893-7C33FE889F91@newgeo.com>
	<729ED907-738E-4E26-B105-6B22347328B4@macports.org>
Message-ID: <Pine.LNX.4.64.0901210801130.10355@joust.gpcc.itd.umich.edu>

On Wed, 21 Jan 2009, Ryan Schmidt wrote:

> On Jan 21, 2009, at 06:34, Scott Haneda wrote:
>
> [snip]
>
>> Also, is there any way for EDITOR to be dynamic, so that when I am on the 
>> actual machine I want to use mate as my editor, but if I am over ssh, I 
>> want to use a terminal based editor.  Is that just a matter of wrapping the 
>> default in a condition that checks where I am at?
>
> I would also be interested in knowing how to set that up. I've wanted this 
> many times but never really looked into what I would need to do.

If you always use ssh for remote logins then you can test for the 
existence of the SSH_CLIENT environment variable.  It doesn't exist when 
you're logged in locally.

                             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 <


From pgijnxn02 at sneakemail.com  Wed Jan 21 06:47:58 2009
From: pgijnxn02 at sneakemail.com (Joel Thibault (MacPorts))
Date: Wed, 21 Jan 2009 09:47:58 -0500
Subject: Mesa
In-Reply-To: <DC8E63F3-C4A6-4B17-91CF-8682B7BE90B5@macports.org>
References: <06B3AA9B-E1B5-4E03-BCFF-1C10A8CAC13D@comcast.net>
	<D9819347-29F5-46DE-A2B5-9FB64687D8DC@macports.org>
	<A044D164-79C7-4300-8995-6260C6D6ED76@comcast.net>
	<DBD58D03-E467-450A-9049-D3A9B2845D3C@macports.org>
	<DC8E63F3-C4A6-4B17-91CF-8682B7BE90B5@macports.org>
Message-ID: <7a665ffc0901210647g54c3aa41n434f0769b1be51b9@mail.gmail.com>

On Wed, Jan 21, 2009 at 2:49 AM, Jeremy Huddleston
jeremyhu-at-macports.orgwrote:

> Should be fixed in r45750
>
>
> On Jan 20, 2009, at 23:26, Ryan Schmidt wrote:
>
>  Frank J. R. Hanstick wrote:
>>
>>         Oops.  Forgot xcode and MacPorts:  2.5 and 1.7.0 respectively.
>>>>
>>>
>>
>> Ok, and based on other output you sent, running Mac OS X 10.4 on a PowerPC
>> Mac.
>>
>>
>> http://trac.macports.org/ticket/17995
>>
>
After a selfupdate and cleaning mesa, the problem in #17995 no longer
occurs, but it can't find the command "makedepend":

DEBUG: Assembled command: 'cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mesa/work/Mesa-7.2"
&& nice
-n 10 make default INSTALL_DIR=/opt/local X11_DIR=/opt/local'
Making sources for darwin
touch depend
makedepend -fdepend -I. -I../../../include -I../../../include/GL/internal
-I../../../src/mesa/main -I../../../src/mesa/glapi   glcontextmodes.c
clientattrib.c
 compsize.c eval.c glxcmds.c glxcurrent.c glxext.c glxextensions.c
indirect.c indirect_init.c indirect_size.c indirect_window_pos.c
indirect_texture_compressi
on.c indirect_transpose_matrix.c indirect_vertex_array.c
indirect_vertex_program.c pixel.c pixelstore.c render2.c renderpix.c
single2.c singlepix.c vertarr.c
xfont.c glx_pbuffer.c glx_query.c drisw_glx.c dri_common.c dri_glx.c
XF86dri.c glxhash.c \
        ../../../src/mesa/main/dispatch.c ../../../src/mesa/glapi/glapi.c
../../../src/mesa/glapi/glthread.c
make[2]: makedepend: Command not found
make[2]: *** [depend] Error 127
make[1]: *** [subdirs] Error 1
make: *** [default] Error 1

[also Xcode 2.5 and OS X 10.4 on PPC but a newer Trunk MacPorts]


-- 
Joel Thibault [AIM: Jole Tebo]
Software Engineer in Boston
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090121/b48ff4ca/attachment.html>

From devans at macports.org  Wed Jan 21 08:09:27 2009
From: devans at macports.org (David Evans)
Date: Wed, 21 Jan 2009 08:09:27 -0800
Subject: Mesa
In-Reply-To: <7a665ffc0901210647g54c3aa41n434f0769b1be51b9@mail.gmail.com>
References: <06B3AA9B-E1B5-4E03-BCFF-1C10A8CAC13D@comcast.net>	<D9819347-29F5-46DE-A2B5-9FB64687D8DC@macports.org>	<A044D164-79C7-4300-8995-6260C6D6ED76@comcast.net>	<DBD58D03-E467-450A-9049-D3A9B2845D3C@macports.org>	<DC8E63F3-C4A6-4B17-91CF-8682B7BE90B5@macports.org>
	<7a665ffc0901210647g54c3aa41n434f0769b1be51b9@mail.gmail.com>
Message-ID: <497748B7.2030200@macports.org>

Joel Thibault (MacPorts) wrote:
>
> On Wed, Jan 21, 2009 at 2:49 AM, Jeremy Huddleston 
> jeremyhu-at-macports.org <http://jeremyhu-at-macports.org> wrote:
>
>     Should be fixed in r45750
>
>
>     On Jan 20, 2009, at 23:26, Ryan Schmidt wrote:
>
>         Frank J. R. Hanstick wrote:
>
>                        Oops.  Forgot xcode and MacPorts:  2.5 and
>                 1.7.0 respectively.
>
>
>
>         Ok, and based on other output you sent, running Mac OS X 10.4
>         on a PowerPC Mac.
>
>
>         http://trac.macports.org/ticket/17995
>
>
> After a selfupdate and cleaning mesa, the problem in #17995 no longer 
> occurs, but it can't find the command "makedepend":
>
> DEBUG: Assembled command: 'cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mesa/work/Mesa-7.2" 
> && nice
> -n 10 make default INSTALL_DIR=/opt/local X11_DIR=/opt/local'
> Making sources for darwin
> touch depend
> makedepend -fdepend -I. -I../../../include 
> -I../../../include/GL/internal -I../../../src/mesa/main 
> -I../../../src/mesa/glapi   glcontextmodes.c clientattrib.c
>  compsize.c eval.c glxcmds.c glxcurrent.c glxext.c glxextensions.c 
> indirect.c indirect_init.c indirect_size.c indirect_window_pos.c 
> indirect_texture_compressi
> on.c indirect_transpose_matrix.c indirect_vertex_array.c 
> indirect_vertex_program.c pixel.c pixelstore.c render2.c renderpix.c 
> single2.c singlepix.c vertarr.c
> xfont.c glx_pbuffer.c glx_query.c drisw_glx.c dri_common.c dri_glx.c 
> XF86dri.c glxhash.c \
>         ../../../src/mesa/main/dispatch.c 
> ../../../src/mesa/glapi/glapi.c ../../../src/mesa/glapi/glthread.c
> make[2]: makedepend: Command not found
> make[2]: *** [depend] Error 127
> make[1]: *** [subdirs] Error 1
> make: *** [default] Error 1
>
> [also Xcode 2.5 and OS X 10.4 on PPC but a newer Trunk MacPorts]
>
>
> -- 
> Joel Thibault [AIM: Jole Tebo]
> Software Engineer in Boston
See also http://trac.macports.org/ticket/18132 
<http://trac.macports.org/ticket/17995>

From icordoba at skios.es  Wed Jan 21 11:13:31 2009
From: icordoba at skios.es (=?UTF-8?Q?Ignacio_de_C=C3=B3rdoba?=)
Date: Wed, 21 Jan 2009 11:13:31 -0800 (PST)
Subject: Postfix and cyrus in Macports bind to different saslauthd
Message-ID: <21588754.post@talk.nabble.com>


Hi there,
I am experimenting an extrange behaviour with saslauthd daemons.
Macports port of Postfix seems to need Apple's builtin saslauthd daemon but
Macports port of Cyrus needs macports version of saslauthd.
I guess this is not normal... I don't mind using any of the versions of
saslauthd as I don't need a special auth mech; just rimap which is built in
both, but whould like to use just one of them. Now I have both saslauthd
started. mux files ar in /opt/local/var/state/saslauthd/mux and
/var/state/saslauthd/mux

Anybody knows how can y make Macports ports of postfix or Cyrus Imaps use
one or the other saslauthd daemons?
Thanks,
Ignacio
-- 
View this message in context: http://www.nabble.com/Postfix-and-cyrus-in-Macports-bind-to-different-saslauthd-tp21588754p21588754.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From talklists at newgeo.com  Wed Jan 21 12:03:37 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 12:03:37 -0800
Subject: Understanding what I am calling the mess that is perl modules
In-Reply-To: <729ED907-738E-4E26-B105-6B22347328B4@macports.org>
References: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
	<5D23BC70-3DA3-4914-8E55-3726D8B2CE7A@macports.org>
	<20090121111939.GA12488@weetamoe.loria.fr>
	<A1226A1F-8C44-4BF0-BE92-DAC97C9DEF3C@newgeo.com>
	<E4A2D53F-A5AC-4188-A893-7C33FE889F91@newgeo.com>
	<729ED907-738E-4E26-B105-6B22347328B4@macports.org>
Message-ID: <CFEA699F-9AB5-4DB8-BC55-ADE0A9C316FD@newgeo.com>

On Jan 21, 2009, at 4:46 AM, Ryan Schmidt wrote:

>> Also, is there any way for EDITOR to be dynamic, so that when I am  
>> on the actual machine I want to use mate as my editor, but if I am  
>> over ssh, I want to use a terminal based editor.  Is that just a  
>> matter of wrapping the default in a condition that checks where I  
>> am at?
>
> I would also be interested in knowing how to set that up. I've  
> wanted this many times but never really looked into what I would  
> need to do.


This seems to work for me:
if [[ -z $SSH_CLIENT ]]; then
         export EDITOR=/Users/me/bin/mate
else
         export EDITOR=/usr/bin/pico
fi;

--
Scott


From talklists at newgeo.com  Wed Jan 21 12:09:40 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 12:09:40 -0800
Subject: Understanding what I am calling the mess that is perl modules
In-Reply-To: <729ED907-738E-4E26-B105-6B22347328B4@macports.org>
References: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
	<5D23BC70-3DA3-4914-8E55-3726D8B2CE7A@macports.org>
	<20090121111939.GA12488@weetamoe.loria.fr>
	<A1226A1F-8C44-4BF0-BE92-DAC97C9DEF3C@newgeo.com>
	<E4A2D53F-A5AC-4188-A893-7C33FE889F91@newgeo.com>
	<729ED907-738E-4E26-B105-6B22347328B4@macports.org>
Message-ID: <E68C0754-32B1-44C0-9F04-167748FE5506@newgeo.com>

On Jan 21, 2009, at 4:46 AM, Ryan Schmidt wrote:

> On Jan 21, 2009, at 06:34, Scott me wrote:
>
>> On Jan 21, 2009, at 4:27 AM, Scott me wrote:
>>
>>> On Jan 21, 2009, at 3:19 AM, Emmanuel Hainry wrote:
>>>
>>>> There was an attempt at that: cpan2port
>>>> [http://www.nabble.com/announce:-cpan2port-td20415884.html]. I  
>>>> don't
>>>> know what is its current status, but that's a nice thing. If it  
>>>> was also
>>>> possible to have this for python eggs, ruby gems, ctan, etc.  
>>>> However,
>>>> debian has had such a tool for a long time, other package  
>>>> managers also
>>>> have.
>>>
>>> Cool, thanks.
>>> I downloaded it, and moved it to ~/bin which is in my path.
>>>
>>> When I run it with no arguments to get to help for it, I get  
>>> errors, which reference macports, which I should not, since I am  
>>> using the built in perl in OS X.
>>>
>>> $whereis perl
>>> /usr/bin/perl
>>
>> I think I am sort of seeing what is going on here. perl -V is using  
>> the macports version for some reason.   would think that `perl`  
>> needs to continue to use the OS X perl, and that I would need to  
>> call out the /opt/local/bin/perl when I want to use the MacPorts one.
>
> If you list /opt/local/bin first in your path, before /usr/bin, then  
> sure, MacPorts perl will be used (in your Terminal) in preference to  
> Apple perl. Same for any other program that exists in both  
> locations. That's the whole reason we recommend putting (and set up  
> for you, in the default .profile) /opt/local/bin first in the path  
> -- so that you get MacPorts versions where available, since they are  
> usually newer.


Duh, sorry, I do not know why I did not see that.  I was just looking  
at order of definition of the PATH, not the actual order inside each  
path.  I have a new echo'd out path of
/usr/bin:/bin:/usr/sbin:/sbin:/Users/me:/usr/local/bin:/usr/X11/bin:/ 
Users/me/bin:/opt/local/bin:/opt/local/sbin

perl -V is now showing what I want
     /System/Library/Perl/5.8.8/darwin-thread-multi-2level
     /System/Library/Perl/5.8.8
     /Library/Perl/5.8.8/darwin-thread-multi-2level
     /Library/Perl/5.8.8
     /Library/Perl
     /Network/Library/Perl/5.8.8/darwin-thread-multi-2level
     /Network/Library/Perl/5.8.8
     /Network/Library/Perl
     /System/Library/Perl/Extras/5.8.8/darwin-thread-multi-2level
     /System/Library/Perl/Extras/5.8.8
     /Library/Perl/5.8.6
     /Library/Perl/5.8.1

Thanks for all the help on this one.
--
Scott


From trog24 at comcast.net  Wed Jan 21 12:16:26 2009
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Wed, 21 Jan 2009 12:16:26 -0800
Subject: Mesa
In-Reply-To: <497748B7.2030200@macports.org>
References: <06B3AA9B-E1B5-4E03-BCFF-1C10A8CAC13D@comcast.net>	<D9819347-29F5-46DE-A2B5-9FB64687D8DC@macports.org>	<A044D164-79C7-4300-8995-6260C6D6ED76@comcast.net>	<DBD58D03-E467-450A-9049-D3A9B2845D3C@macports.org>	<DC8E63F3-C4A6-4B17-91CF-8682B7BE90B5@macports.org>
	<7a665ffc0901210647g54c3aa41n434f0769b1be51b9@mail.gmail.com>
	<497748B7.2030200@macports.org>
Message-ID: <D224BBE0-1778-4153-8E20-7516CD3E77CD@comcast.net>

Hello,
	After performing the selfupdate, clean mesa, and -d install mesa, I  
got the following error:

Making sources for darwin
touch depend
makedepend -fdepend -I. -I../../../include -I../../../include/GL/ 
internal -I../../../src/mesa/main -I../../../src/mesa/glapi    
glcontextmodes.c clientattrib.c compsize.c eval.c glxcmds.c  
glxcurrent.c glxext.c glxextensions.c indirect.c indirect_init.c  
indirect_size.c indirect_window_pos.c indirect_texture_compression.c  
indirect_transpose_matrix.c indirect_vertex_array.c  
indirect_vertex_program.c pixel.c pixelstore.c render2.c renderpix.c  
single2.c singlepix.c vertarr.c xfont.c glx_pbuffer.c glx_query.c  
drisw_glx.c dri_common.c dri_glx.c XF86dri.c glxhash.c \
         ../../../src/mesa/main/dispatch.c ../../../src/mesa/glapi/ 
glapi.c ../../../src/mesa/glapi/glthread.c
makedepend: warning:  glcontextmodes.c, line 42: cannot find include  
file "GL/glxint.h"
         not in GL/glxint.h
         not in GL/glxint.h
         not in ./GL/glxint.h
         not in ../../../include/GL/glxint.h
         not in ../../../include/GL/internal/GL/glxint.h
         not in ../../../src/mesa/main/GL/glxint.h
         not in ../../../src/mesa/glapi/GL/glxint.h
         not in /usr/local/lib/gcc-include/GL/glxint.h
         not in /usr/include/GL/glxint.h
         not in /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/include/GL/ 
glxint.h
makedepend: warning:  clientattrib.c (reading glxclient.h, line 53):  
cannot find include file "GL/glxint.h"
         not in GL/glxint.h
         not in GL/glxint.h
         not in ./GL/glxint.h
         not in ../../../include/GL/glxint.h
         not in ../../../include/GL/internal/GL/glxint.h
         not in ../../../src/mesa/main/GL/glxint.h
         not in ../../../src/mesa/glapi/GL/glxint.h
         not in /usr/local/lib/gcc-include/GL/glxint.h
         not in /usr/include/GL/glxint.h
         not in /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/include/GL/ 
glxint.h
makedepend: warning:  clientattrib.c (reading glxclient.h, line 54):  
cannot find include file "GL/glxproto.h"
         not in GL/glxproto.h
         not in GL/glxproto.h
         not in ./GL/glxproto.h
         not in ../../../include/GL/glxproto.h
         not in ../../../include/GL/internal/GL/glxproto.h
         not in ../../../src/mesa/main/GL/glxproto.h
         not in ../../../src/mesa/glapi/GL/glxproto.h
         not in /usr/local/lib/gcc-include/GL/glxproto.h
         not in /usr/include/GL/glxproto.h
         not in /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/include/GL/ 
glxproto.h
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 74
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 79
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 80
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 81
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 82
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 83
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 85
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 86
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 87
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 88
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 89
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 147
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 153
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 157
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 162
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 167
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 172
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 177
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 211
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 216
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 221
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 226
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 231
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 236
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 259
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 263
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 268
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 270
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 273
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 276
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 279
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 282
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 316
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 319
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 322
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 325
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 328
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 331
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 349
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 647
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 649
makedepend: warning:  /usr/include/architecture/ppc/math.h:  non- 
portable whitespace encountered at line 651
makedepend: warning:  indirect.c, line 36: cannot find include file  
"GL/glxproto.h"
         not in ./GL/glxproto.h
         not in ../../../include/GL/glxproto.h
         not in ../../../include/GL/internal/GL/glxproto.h
         not in ../../../src/mesa/main/GL/glxproto.h
         not in ../../../src/mesa/glapi/GL/glxproto.h
         not in /usr/local/lib/gcc-include/GL/glxproto.h
         not in /usr/include/GL/glxproto.h
         not in /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/include/GL/ 
glxproto.h
makedepend: warning:  indirect_vertex_array.c, line 32: cannot find  
include file "GL/glxproto.h"
         not in ./GL/glxproto.h
         not in ../../../include/GL/glxproto.h
         not in ../../../include/GL/internal/GL/glxproto.h
         not in ../../../src/mesa/main/GL/glxproto.h
         not in ../../../src/mesa/glapi/GL/glxproto.h
         not in /usr/local/lib/gcc-include/GL/glxproto.h
         not in /usr/include/GL/glxproto.h
         not in /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/include/GL/ 
glxproto.h
makedepend: warning:  indirect_vertex_array.c (reading  
indirect_vertex_array_priv.h, line 39): cannot find include file "GL/ 
glxproto.h"
         not in ./GL/glxproto.h
         not in ../../../include/GL/glxproto.h
         not in ../../../include/GL/internal/GL/glxproto.h
         not in ../../../src/mesa/main/GL/glxproto.h
         not in ../../../src/mesa/glapi/GL/glxproto.h
         not in /usr/local/lib/gcc-include/GL/glxproto.h
         not in /usr/include/GL/glxproto.h
         not in /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/include/GL/ 
glxproto.h
makedepend: warning:  indirect_vertex_program.c, line 32: cannot find  
include file "GL/glxproto.h"
         not in ./GL/glxproto.h
         not in ../../../include/GL/glxproto.h
         not in ../../../include/GL/internal/GL/glxproto.h
         not in ../../../src/mesa/main/GL/glxproto.h
         not in ../../../src/mesa/glapi/GL/glxproto.h
         not in /usr/local/lib/gcc-include/GL/glxproto.h
         not in /usr/include/GL/glxproto.h
         not in /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/include/GL/ 
glxproto.h
makedepend: warning:  singlepix.c, line 38: cannot find include file  
"GL/glxproto.h"
         not in ./GL/glxproto.h
         not in ../../../include/GL/glxproto.h
         not in ../../../include/GL/internal/GL/glxproto.h
         not in ../../../src/mesa/main/GL/glxproto.h
         not in ../../../src/mesa/glapi/GL/glxproto.h
         not in /usr/local/lib/gcc-include/GL/glxproto.h
         not in /usr/include/GL/glxproto.h
         not in /usr/lib/gcc/powerpc-apple-darwin8/4.0.1/include/GL/ 
glxproto.h
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" glcontextmodes.c -o  
glcontextmodes.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" clientattrib.c -o  
clientattrib.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" compsize.c -o compsize.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" eval.c -o eval.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" glxcmds.c -o glxcmds.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" glxcurrent.c -o glxcurrent.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" glxext.c -o glxext.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" glxextensions.c -o  
glxextensions.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" indirect.c -o indirect.o
indirect.c: In function 'glAreTexturesResidentEXT':
indirect.c:5125: warning: unused variable 'gc'
indirect.c: In function 'glDeleteTexturesEXT':
indirect.c:5278: warning: unused variable 'gc'
indirect.c: In function 'glGenTexturesEXT':
indirect.c:5349: warning: unused variable 'gc'
indirect.c: In function 'glIsTextureEXT':
indirect.c:5414: warning: unused variable 'gc'
indirect.c: In function 'glGetColorTableEXT':
indirect.c:5731: warning: unused variable 'gc'
indirect.c: In function 'glGetColorTableParameterfvEXT':
indirect.c:5807: warning: unused variable 'gc'
indirect.c: In function 'glGetColorTableParameterivEXT':
indirect.c:5880: warning: unused variable 'gc'
indirect.c: In function 'gl_dispatch_stub_356':
indirect.c:6206: warning: unused variable 'gc'
indirect.c: In function 'gl_dispatch_stub_357':
indirect.c:6284: warning: unused variable 'gc'
indirect.c: In function 'gl_dispatch_stub_358':
indirect.c:6357: warning: unused variable 'gc'
indirect.c: In function 'gl_dispatch_stub_361':
indirect.c:6437: warning: unused variable 'gc'
indirect.c: In function 'gl_dispatch_stub_362':
indirect.c:6514: warning: unused variable 'gc'
indirect.c: In function 'gl_dispatch_stub_363':
indirect.c:6585: warning: unused variable 'gc'
indirect.c: In function 'gl_dispatch_stub_364':
indirect.c:6660: warning: unused variable 'gc'
indirect.c: In function 'gl_dispatch_stub_365':
indirect.c:6734: warning: unused variable 'gc'
indirect.c: In function 'gl_dispatch_stub_366':
indirect.c:6802: warning: unused variable 'gc'
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" indirect_init.c -o  
indirect_init.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" indirect_size.c -o  
indirect_size.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" indirect_window_pos.c -o  
indirect_window_pos.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\"  
indirect_texture_compression.c -o indirect_texture_compression.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\"  
indirect_transpose_matrix.c -o indirect_transpose_matrix.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" indirect_vertex_array.c -o  
indirect_vertex_array.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" indirect_vertex_program.c - 
o indirect_vertex_program.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" pixel.c -o pixel.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" pixelstore.c -o pixelstore.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" render2.c -o render2.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" renderpix.c -o renderpix.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" single2.c -o single2.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" singlepix.c -o singlepix.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" vertarr.c -o vertarr.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" xfont.c -o xfont.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" glx_pbuffer.c -o  
glx_pbuffer.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" glx_query.c -o glx_query.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" drisw_glx.c -o drisw_glx.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" dri_common.c -o dri_common.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" dri_glx.c -o dri_glx.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" XF86dri.c -o XF86dri.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" glxhash.c -o glxhash.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" ../../../src/mesa/main/ 
dispatch.c -o ../../../src/mesa/main/dispatch.o
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" ../../../src/mesa/glapi/ 
glapi.c -o ../../../src/mesa/glapi/glapi.o
../../../src/mesa/glapi/glapitemp.h:1884: warning:  
'NoOp_dispatch_stub_339' defined but not used
../../../src/mesa/glapi/glapitemp.h:1901: warning:  
'NoOp_dispatch_stub_340' defined but not used
../../../src/mesa/glapi/glapitemp.h:1913: warning:  
'NoOp_dispatch_stub_341' defined but not used
../../../src/mesa/glapi/glapitemp.h:1925: warning:  
'NoOp_dispatch_stub_342' defined but not used
../../../src/mesa/glapi/glapitemp.h:2000: warning:  
'NoOp_dispatch_stub_346' defined but not used
../../../src/mesa/glapi/glapitemp.h:2012: warning:  
'NoOp_dispatch_stub_347' defined but not used
../../../src/mesa/glapi/glapitemp.h:2024: warning:  
'NoOp_dispatch_stub_348' defined but not used
../../../src/mesa/glapi/glapitemp.h:2036: warning:  
'NoOp_dispatch_stub_349' defined but not used
../../../src/mesa/glapi/glapitemp.h:2048: warning:  
'NoOp_dispatch_stub_350' defined but not used
../../../src/mesa/glapi/glapitemp.h:2060: warning:  
'NoOp_dispatch_stub_351' defined but not used
../../../src/mesa/glapi/glapitemp.h:2072: warning:  
'NoOp_dispatch_stub_352' defined but not used
../../../src/mesa/glapi/glapitemp.h:2084: warning:  
'NoOp_dispatch_stub_353' defined but not used
../../../src/mesa/glapi/glapitemp.h:2096: warning:  
'NoOp_dispatch_stub_354' defined but not used
../../../src/mesa/glapi/glapitemp.h:2108: warning:  
'NoOp_dispatch_stub_355' defined but not used
../../../src/mesa/glapi/glapitemp.h:2176: warning:  
'NoOp_dispatch_stub_360' defined but not used
../../../src/mesa/glapi/glapitemp.h:2272: warning:  
'NoOp_dispatch_stub_367' defined but not used
../../../src/mesa/glapi/glapitemp.h:2284: warning:  
'NoOp_dispatch_stub_368' defined but not used
../../../src/mesa/glapi/glapitemp.h:2296: warning:  
'NoOp_dispatch_stub_369' defined but not used
../../../src/mesa/glapi/glapitemp.h:2308: warning:  
'NoOp_dispatch_stub_370' defined but not used
../../../src/mesa/glapi/glapitemp.h:2765: warning:  
'NoOp_dispatch_stub_423' defined but not used
../../../src/mesa/glapi/glapitemp.h:4118: warning:  
'NoOp_dispatch_stub_576' defined but not used
../../../src/mesa/glapi/glapitemp.h:4140: warning:  
'NoOp_dispatch_stub_577' defined but not used
../../../src/mesa/glapi/glapitemp.h:4428: warning:  
'NoOp_dispatch_stub_607' defined but not used
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" ../../../src/mesa/glapi/ 
glthread.c -o ../../../src/mesa/glapi/glthread.o
/bin/sh ../../../bin/mklib -o GL -linker 'gcc' -ldflags '' \
         -major 1 -minor 2  \
         -install ../../../lib -id /opt/local/lib/libGL.1.dylib \
         -L/opt/local/lib -L/opt/local/lib -lX11 -lXext -lm -lpthread  
glcontextmodes.o clientattrib.o compsize.o eval.o glxcmds.o  
glxcurrent.o glxext.o glxextensions.o indirect.o indirect_init.o  
indirect_size.o indirect_window_pos.o indirect_texture_compression.o  
indirect_transpose_matrix.o indirect_vertex_array.o  
indirect_vertex_program.o pixel.o pixelstore.o render2.o renderpix.o  
single2.o singlepix.o vertarr.o xfont.o glx_pbuffer.o glx_query.o  
drisw_glx.o dri_common.o dri_glx.o XF86dri.o glxhash.o ../../../src/ 
mesa/main/dispatch.o ../../../src/mesa/glapi/glapi.o ../../../src/ 
mesa/glapi/glthread.o
mklib: Making Darwin shared library:  libGL.1.2.dylib
ld: common symbols not allowed with MH_DYLIB output format with the - 
multi_module option
../../../src/mesa/glapi/glapi.o definition of common __gl_DispatchTSD  
(size 8)
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: internal link  
edit command failed
mklib: Installing libGL.1.2.dylib libGL.1.dylib libGL.dylib  
in ../../../lib
mv: rename libGL.1.2.dylib to ../../../lib/libGL.1.2.dylib: No such  
file or directory
make[2]: *** [../../../lib/libGL.dylib] Error 1
make[1]: *** [subdirs] Error 1
make: *** [default] Error 1
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mes 
a/work/Mesa-7.2" && make default INSTALL_DIR=/opt/local " returned  
error 2
Command output: ../../../src/mesa/glapi/glapitemp.h:2036: warning:  
'NoOp_dispatch_stub_349' defined but not used
../../../src/mesa/glapi/glapitemp.h:2048: warning:  
'NoOp_dispatch_stub_350' defined but not used
../../../src/mesa/glapi/glapitemp.h:2060: warning:  
'NoOp_dispatch_stub_351' defined but not used
../../../src/mesa/glapi/glapitemp.h:2072: warning:  
'NoOp_dispatch_stub_352' defined but not used
../../../src/mesa/glapi/glapitemp.h:2084: warning:  
'NoOp_dispatch_stub_353' defined but not used
../../../src/mesa/glapi/glapitemp.h:2096: warning:  
'NoOp_dispatch_stub_354' defined but not used
../../../src/mesa/glapi/glapitemp.h:2108: warning:  
'NoOp_dispatch_stub_355' defined but not used
../../../src/mesa/glapi/glapitemp.h:2176: warning:  
'NoOp_dispatch_stub_360' defined but not used
../../../src/mesa/glapi/glapitemp.h:2272: warning:  
'NoOp_dispatch_stub_367' defined but not used
../../../src/mesa/glapi/glapitemp.h:2284: warning:  
'NoOp_dispatch_stub_368' defined but not used
../../../src/mesa/glapi/glapitemp.h:2296: warning:  
'NoOp_dispatch_stub_369' defined but not used
../../../src/mesa/glapi/glapitemp.h:2308: warning:  
'NoOp_dispatch_stub_370' defined but not used
../../../src/mesa/glapi/glapitemp.h:2765: warning:  
'NoOp_dispatch_stub_423' defined but not used
../../../src/mesa/glapi/glapitemp.h:4118: warning:  
'NoOp_dispatch_stub_576' defined but not used
../../../src/mesa/glapi/glapitemp.h:4140: warning:  
'NoOp_dispatch_stub_577' defined but not used
../../../src/mesa/glapi/glapitemp.h:4428: warning:  
'NoOp_dispatch_stub_607' defined but not used
gcc -c -I. -I../../../include -I../../../include/GL/internal - 
I../../../src/mesa/main -I../../../src/mesa/glapi   -ggdb3 -Os -Wall - 
Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -I/opt/ 
local/include -I/opt/local/include  -fPIC   -D_DARWIN_C_SOURCE - 
D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE  
-D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - 
DGLX_INDIRECT_RENDERING -DXF86VIDMODE -D_REENTRANT -UIN_DRI_DRIVER - 
DDEFAULT_DRIVER_DIR=\"/opt/local/lib/dri\" ../../../src/mesa/glapi/ 
glthread.c -o ../../../src/mesa/glapi/glthread.o
/bin/sh ../../../bin/mklib -o GL -linker 'gcc' -ldflags '' \
         -major 1 -minor 2  \
         -install ../../../lib -id /opt/local/lib/libGL.1.dylib \
         -L/opt/local/lib -L/opt/local/lib -lX11 -lXext -lm -lpthread  
glcontextmodes.o clientattrib.o compsize.o eval.o glxcmds.o  
glxcurrent.o glxext.o glxextensions.o indirect.o indirect_init.o  
indirect_size.o indirect_window_pos.o indirect_texture_compression.o  
indirect_transpose_matrix.o indirect_vertex_array.o  
indirect_vertex_program.o pixel.o pixelstore.o render2.o renderpix.o  
single2.o singlepix.o vertarr.o xfont.o glx_pbuffer.o glx_query.o  
drisw_glx.o dri_common.o dri_glx.o XF86dri.o glxhash.o ../../../src/ 
mesa/main/dispatch.o ../../../src/mesa/glapi/glapi.o ../../../src/ 
mesa/glapi/glthread.o
mklib: Making Darwin shared library:  libGL.1.2.dylib
ld: common symbols not allowed with MH_DYLIB output format with the - 
multi_module option
../../../src/mesa/glapi/glapi.o definition of common __gl_DispatchTSD  
(size 8)
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: internal link  
edit command failed
mklib: Installing libGL.1.2.dylib libGL.1.dylib libGL.dylib  
in ../../../lib
mv: rename libGL.1.2.dylib to ../../../lib/libGL.1.2.dylib: No such  
file or directory
make[2]: *** [../../../lib/libGL.dylib] Error 1
make[1]: *** [subdirs] Error 1
make: *** [default] Error 1

Warning: the following items did not execute (for mesa):  
org.macports.activate org.macports.build org.macports.destroot  
org.macports.install
Error: Status 1 encountered during processing.

Frank

On Jan 21, 2009, at 8:09 AM, David Evans wrote:

> Joel Thibault (MacPorts) wrote:
>>
>> On Wed, Jan 21, 2009 at 2:49 AM, Jeremy Huddleston jeremyhu-at- 
>> macports.org <http://jeremyhu-at-macports.org> wrote:
>>
>>     Should be fixed in r45750
>>
>>
>>     On Jan 20, 2009, at 23:26, Ryan Schmidt wrote:
>>
>>         Frank J. R. Hanstick wrote:
>>
>>                        Oops.  Forgot xcode and MacPorts:  2.5 and
>>                 1.7.0 respectively.
>>
>>
>>
>>         Ok, and based on other output you sent, running Mac OS X 10.4
>>         on a PowerPC Mac.
>>
>>
>>         http://trac.macports.org/ticket/17995
>>
>>
>> After a selfupdate and cleaning mesa, the problem in #17995 no  
>> longer occurs, but it can't find the command "makedepend":
>>
>> DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_ 
>> mesa/work/Mesa-7.2" && nice
>> -n 10 make default INSTALL_DIR=/opt/local X11_DIR=/opt/local'
>> Making sources for darwin
>> touch depend
>> makedepend -fdepend -I. -I../../../include -I../../../include/GL/ 
>> internal -I../../../src/mesa/main -I../../../src/mesa/glapi    
>> glcontextmodes.c clientattrib.c
>>  compsize.c eval.c glxcmds.c glxcurrent.c glxext.c glxextensions.c  
>> indirect.c indirect_init.c indirect_size.c indirect_window_pos.c  
>> indirect_texture_compressi
>> on.c indirect_transpose_matrix.c indirect_vertex_array.c  
>> indirect_vertex_program.c pixel.c pixelstore.c render2.c  
>> renderpix.c single2.c singlepix.c vertarr.c
>> xfont.c glx_pbuffer.c glx_query.c drisw_glx.c dri_common.c  
>> dri_glx.c XF86dri.c glxhash.c \
>>         ../../../src/mesa/main/dispatch.c ../../../src/mesa/glapi/ 
>> glapi.c ../../../src/mesa/glapi/glthread.c
>> make[2]: makedepend: Command not found
>> make[2]: *** [depend] Error 127
>> make[1]: *** [subdirs] Error 1
>> make: *** [default] Error 1
>>
>> [also Xcode 2.5 and OS X 10.4 on PPC but a newer Trunk MacPorts]
>>
>>
>> -- 
>> Joel Thibault [AIM: Jole Tebo]
>> Software Engineer in Boston
> See also http://trac.macports.org/ticket/18132 <http:// 
> trac.macports.org/ticket/17995>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From talklists at newgeo.com  Wed Jan 21 12:40:14 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 12:40:14 -0800
Subject: ASSP port testing, not getting all perl mods to work
Message-ID: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>

Hello, this may be getting a little outside the scope of what this  
list can help me with.  Hopefully we can solve it so I can actually  
get my email server where I want.

I downloaded the ASSP package
http://superb-east.dl.sourceforge.net/sourceforge/assp/ASSP_1.4.3.1-Install.zip

The notes say I need some modules, which I managed to port install or  
make a port to get them installed.

Here is the list from their README as to what I need
http://pastebin.com/f692f61e3

Here is a list from `port installed`
http://pastebin.com/f564a902e

In short, all I need to get it working is to cd into the ASSP  
directory, and run `perl assp.pl` which will start it as a server, and  
give me a report to the console, as well as a log, telling me what is  
going on.

Looking over their files, I can see they are referencing a local perl  
location, which will not work, so I do a global find and replace to  
repair that.  I am near certain for MacPorts I need to use /opt/local/ 
bin/perl

#!/usr/bin/perl -> #!/opt/local/bin/perl
I am pretty sure, according to the old outdated ASSP port, this is all  
it is doing.  The old port makes some new users and groups, but I do  
not think that is related, nor needed anymore.

cd /Users/me/Downloads/ASSP_1.4.3.1-Install/ASSP
sudo perl assp.pl

It starts, and most of my efforts worked out, however, there are a few  
that do not.  Here is the result of the log file:

http://pastebin.com/f539150d2

Most of the errors are because it is a new install, but there are a  
few I am lost on:
Jan-21-09 12:27:32 Email::Valid module not installed
Jan-21-09 12:27:32 Mail::SPF module not installed
*Jan-21-09 12:27:32 Tie::RDBM module not installed - mysql usage not  
available

* Tie:RDBM may simply fail because I do not have MySql installed at  
this point, however, I am pretty sure it should still show as installed.

port contents p5-email-valid
Port p5-email-valid contains:
   /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level/auto/Email/ 
Valid/.packlist
   /opt/local/lib/perl5/vendor_perl/5.8.9/Email/Valid.pm
   /opt/local/share/man/man3/Email::Valid.3pm.gz

port contents p5-mail-spf
Port p5-mail-spf contains:
   /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level/auto/Mail/ 
SPF/.packlist
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Base.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Exception.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/MacroString.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/A.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/All.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/Exists.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/Include.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/IP4.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/IP6.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/MX.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/PTR.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mod/Exp.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mod/Redirect.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mod.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Record.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Request.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Result.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/SenderIPAddrMech.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Server.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Term.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Util.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/v1/Record.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/v2/Record.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF.pm
   /opt/local/share/man/man3/Mail::SPF.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Base.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::MacroString.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Mech.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Mech::A.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Mech::All.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Mech::Exists.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Mech::Include.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Mech::IP4.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Mech::IP6.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Mech::MX.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Mech::PTR.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Mod.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Mod::Exp.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Mod::Redirect.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Record.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Request.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Result.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::SenderIPAddrMech.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Server.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Term.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::Util.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::v1::Record.3pm.gz
   /opt/local/share/man/man3/Mail::SPF::v2::Record.3pm.gz
   /usr/sbin/spfd

port contents p5-tie-dbi
Port p5-tie-dbi contains:
   /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level/auto/Tie/ 
DBI/.packlist
   /opt/local/lib/perl5/vendor_perl/5.8.9/Tie/DBI.pm
   /opt/local/lib/perl5/vendor_perl/5.8.9/Tie/RDBM.pm
   /opt/local/share/man/man3/Tie::DBI.3pm.gz
   /opt/local/share/man/man3/Tie::RDBM.3pm.gz

Looks to me like they are all there, and they should all work.  I do  
not know enough perl to run three basic tests to make calls to each,  
and confirm if it is in ASSP, or if it is in MacPorts. On another  
machine, a while back, I used CPAN, and had 100% success in making  
this work, but with that, I did not have to find and replace out the  
perl path.

I am 99% there, and I will have an awesome port, with a option to pre- 
enable LDAP for my email server, and the ability to add the ldap  
strings for any other server, which is the hardest part of getting  
ASSP running live.
--
Scott


From talklists at newgeo.com  Wed Jan 21 16:04:40 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 16:04:40 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
Message-ID: <CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>

I think I may have found some of the problem, from the email::valid  
docs:

If you installed the module into an alternative directory, you will  
need to let Perl know where it can be found: use
lib "/path/to/my/modules";
use Email::Valid;

I made a test case
use Email::Valid;
print (Email::Valid->address('maurice at hevanet.com') ? '\nyes' : '\nno');

If I run that as
perl filename
I get errors Can't locate Email/Valid.pm

If I run it as
/opt/local/bin/perl filename
It works

So I now know it works, and is in stalled, but why does ASSP not see  
it.  I think I am going to have to patch the ASSP files, would that be  
the correct method? I am also contacting the developer.

On Jan 21, 2009, at 12:40 PM, Scott Haneda wrote:

> Hello, this may be getting a little outside the scope of what this  
> list can help me with.  Hopefully we can solve it so I can actually  
> get my email server where I want.
>
> I downloaded the ASSP package
> http://superb-east.dl.sourceforge.net/sourceforge/assp/ASSP_1.4.3.1-Install.zip
>
> The notes say I need some modules, which I managed to port install  
> or make a port to get them installed.
>
> Here is the list from their README as to what I need
> http://pastebin.com/f692f61e3
>
> Here is a list from `port installed`
> http://pastebin.com/f564a902e
>
> In short, all I need to get it working is to cd into the ASSP  
> directory, and run `perl assp.pl` which will start it as a server,  
> and give me a report to the console, as well as a log, telling me  
> what is going on.
>
> Looking over their files, I can see they are referencing a local  
> perl location, which will not work, so I do a global find and  
> replace to repair that.  I am near certain for MacPorts I need to  
> use /opt/local/bin/perl
>
> #!/usr/bin/perl -> #!/opt/local/bin/perl
> I am pretty sure, according to the old outdated ASSP port, this is  
> all it is doing.  The old port makes some new users and groups, but  
> I do not think that is related, nor needed anymore.
>
> cd /Users/me/Downloads/ASSP_1.4.3.1-Install/ASSP
> sudo perl assp.pl
>
> It starts, and most of my efforts worked out, however, there are a  
> few that do not.  Here is the result of the log file:
>
> http://pastebin.com/f539150d2
>
> Most of the errors are because it is a new install, but there are a  
> few I am lost on:
> Jan-21-09 12:27:32 Email::Valid module not installed
> Jan-21-09 12:27:32 Mail::SPF module not installed
> *Jan-21-09 12:27:32 Tie::RDBM module not installed - mysql usage not  
> available
>
> * Tie:RDBM may simply fail because I do not have MySql installed at  
> this point, however, I am pretty sure it should still show as  
> installed.
>
> port contents p5-email-valid
> Port p5-email-valid contains:
>  /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level/auto/Email/ 
> Valid/.packlist
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Email/Valid.pm
>  /opt/local/share/man/man3/Email::Valid.3pm.gz
>
> port contents p5-mail-spf
> Port p5-mail-spf contains:
>  /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level/auto/Mail/ 
> SPF/.packlist
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Base.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Exception.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/MacroString.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/A.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/All.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/Exists.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/Include.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/IP4.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/IP6.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/MX.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/PTR.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mod/Exp.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mod/Redirect.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mod.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Record.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Request.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Result.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/SenderIPAddrMech.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Server.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Term.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Util.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/v1/Record.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/v2/Record.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF.pm
>  /opt/local/share/man/man3/Mail::SPF.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Base.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::MacroString.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Mech.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Mech::A.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Mech::All.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Mech::Exists.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Mech::Include.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Mech::IP4.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Mech::IP6.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Mech::MX.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Mech::PTR.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Mod.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Mod::Exp.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Mod::Redirect.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Record.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Request.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Result.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::SenderIPAddrMech.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Server.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Term.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::Util.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::v1::Record.3pm.gz
>  /opt/local/share/man/man3/Mail::SPF::v2::Record.3pm.gz
>  /usr/sbin/spfd
>
> port contents p5-tie-dbi
> Port p5-tie-dbi contains:
>  /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level/auto/Tie/ 
> DBI/.packlist
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Tie/DBI.pm
>  /opt/local/lib/perl5/vendor_perl/5.8.9/Tie/RDBM.pm
>  /opt/local/share/man/man3/Tie::DBI.3pm.gz
>  /opt/local/share/man/man3/Tie::RDBM.3pm.gz
>
> Looks to me like they are all there, and they should all work.  I do  
> not know enough perl to run three basic tests to make calls to each,  
> and confirm if it is in ASSP, or if it is in MacPorts. On another  
> machine, a while back, I used CPAN, and had 100% success in making  
> this work, but with that, I did not have to find and replace out the  
> perl path.
>
> I am 99% there, and I will have an awesome port, with a option to  
> pre-enable LDAP for my email server, and the ability to add the ldap  
> strings for any other server, which is the hardest part of getting  
> ASSP running live.
--
Scott


From vincent-opdarw at vinc17.org  Wed Jan 21 17:09:23 2009
From: vincent-opdarw at vinc17.org (Vincent Lefevre)
Date: Thu, 22 Jan 2009 02:09:23 +0100
Subject: Understanding what I am calling the mess that is perl modules
In-Reply-To: <Pine.LNX.4.64.0901210801130.10355@joust.gpcc.itd.umich.edu>
References: <E426679B-65CC-4FD0-A9ED-BE889FB326D2@newgeo.com>
	<5D23BC70-3DA3-4914-8E55-3726D8B2CE7A@macports.org>
	<20090121111939.GA12488@weetamoe.loria.fr>
	<A1226A1F-8C44-4BF0-BE92-DAC97C9DEF3C@newgeo.com>
	<E4A2D53F-A5AC-4188-A893-7C33FE889F91@newgeo.com>
	<729ED907-738E-4E26-B105-6B22347328B4@macports.org>
	<Pine.LNX.4.64.0901210801130.10355@joust.gpcc.itd.umich.edu>
Message-ID: <20090122010923.GL28662@prunille.vinc17.org>

On 2009-01-21 08:04:16 -0500, Kurt Hillig wrote:
> If you always use ssh for remote logins then you can test for the  
> existence of the SSH_CLIENT environment variable.  It doesn't exist when  
> you're logged in locally.

You need to be a bit smarter: the SSH_CLIENT environment variable
isn't necessarily meaningful.

1. Start the "screen" utility locally.
2. From a remote machine, ssh to the Mac OS X machine.
3. Recall the "screen" session.
4. Start the editor from it.

As SSH_CLIENT is not defined (because the "screen" session has been
started locally), the editor will open on the wrong physical screen!

If you want to have an idea of what can be done, see

  http://www.vinc17.org/mutt/index.en.html#smutt

I run Mutt in "screen" from my Mac OS X machine, which I can use
remotely by ssh (typically, a Linux machine). And my editor (Emacs)
opens its own window (on the Mac OS X screen) *only* when I've
recalled the "screen" session from the Mac OS X machine.

-- 
Vincent Lef?vre <vincent at vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

From trog24 at comcast.net  Wed Jan 21 17:13:51 2009
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Wed, 21 Jan 2009 17:13:51 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
Message-ID: <E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>

Hello,
	It sounds like opt/local is not the first location the path  
environment looks for perl.  This is a problem when several versions  
of a program exists because unless a prefix is supplied, the default  
program will always be found in the order of the pathname (first  
detected).  If perl exists in /opt/local/bin and /usr/bin and the  
path is in the order of /usr/bin:/opt/local/bin, then without a  
prefix, /usr/bin will always be the perl used and visa versa if path  
is /opt/local/bin:/usr/bin.  I ran into the same problem with gcc  
located in two different locations.
Frank

On Jan 21, 2009, at 4:04 PM, Scott Haneda wrote:

> I think I may have found some of the problem, from the email::valid  
> docs:
>
> If you installed the module into an alternative directory, you will  
> need to let Perl know where it can be found: use
> lib "/path/to/my/modules";
> use Email::Valid;
>
> I made a test case
> use Email::Valid;
> print (Email::Valid->address('maurice at hevanet.com') ? '\nyes' :  
> '\nno');
>
> If I run that as
> perl filename
> I get errors Can't locate Email/Valid.pm
>
> If I run it as
> /opt/local/bin/perl filename
> It works
>
> So I now know it works, and is in stalled, but why does ASSP not  
> see it.  I think I am going to have to patch the ASSP files, would  
> that be the correct method? I am also contacting the developer.
>
> On Jan 21, 2009, at 12:40 PM, Scott Haneda wrote:
>
>> Hello, this may be getting a little outside the scope of what this  
>> list can help me with.  Hopefully we can solve it so I can  
>> actually get my email server where I want.
>>
>> I downloaded the ASSP package
>> http://superb-east.dl.sourceforge.net/sourceforge/assp/ 
>> ASSP_1.4.3.1-Install.zip
>>
>> The notes say I need some modules, which I managed to port install  
>> or make a port to get them installed.
>>
>> Here is the list from their README as to what I need
>> http://pastebin.com/f692f61e3
>>
>> Here is a list from `port installed`
>> http://pastebin.com/f564a902e
>>
>> In short, all I need to get it working is to cd into the ASSP  
>> directory, and run `perl assp.pl` which will start it as a server,  
>> and give me a report to the console, as well as a log, telling me  
>> what is going on.
>>
>> Looking over their files, I can see they are referencing a local  
>> perl location, which will not work, so I do a global find and  
>> replace to repair that.  I am near certain for MacPorts I need to  
>> use /opt/local/bin/perl
>>
>> #!/usr/bin/perl -> #!/opt/local/bin/perl
>> I am pretty sure, according to the old outdated ASSP port, this is  
>> all it is doing.  The old port makes some new users and groups,  
>> but I do not think that is related, nor needed anymore.
>>
>> cd /Users/me/Downloads/ASSP_1.4.3.1-Install/ASSP
>> sudo perl assp.pl
>>
>> It starts, and most of my efforts worked out, however, there are a  
>> few that do not.  Here is the result of the log file:
>>
>> http://pastebin.com/f539150d2
>>
>> Most of the errors are because it is a new install, but there are  
>> a few I am lost on:
>> Jan-21-09 12:27:32 Email::Valid module not installed
>> Jan-21-09 12:27:32 Mail::SPF module not installed
>> *Jan-21-09 12:27:32 Tie::RDBM module not installed - mysql usage  
>> not available
>>
>> * Tie:RDBM may simply fail because I do not have MySql installed  
>> at this point, however, I am pretty sure it should still show as  
>> installed.
>>
>> port contents p5-email-valid
>> Port p5-email-valid contains:
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level/auto/Email/ 
>> Valid/.packlist
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Email/Valid.pm
>>  /opt/local/share/man/man3/Email::Valid.3pm.gz
>>
>> port contents p5-mail-spf
>> Port p5-mail-spf contains:
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level/auto/Mail/ 
>> SPF/.packlist
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Base.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Exception.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/MacroString.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/A.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/All.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/Exists.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/Include.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/IP4.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/IP6.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/MX.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech/PTR.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mech.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mod/Exp.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mod/Redirect.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Mod.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Record.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Request.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Result.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/SenderIPAddrMech.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Server.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Term.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/Util.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/v1/Record.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF/v2/Record.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Mail/SPF.pm
>>  /opt/local/share/man/man3/Mail::SPF.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Base.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::MacroString.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Mech.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Mech::A.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Mech::All.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Mech::Exists.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Mech::Include.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Mech::IP4.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Mech::IP6.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Mech::MX.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Mech::PTR.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Mod.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Mod::Exp.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Mod::Redirect.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Record.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Request.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Result.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::SenderIPAddrMech.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Server.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Term.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::Util.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::v1::Record.3pm.gz
>>  /opt/local/share/man/man3/Mail::SPF::v2::Record.3pm.gz
>>  /usr/sbin/spfd
>>
>> port contents p5-tie-dbi
>> Port p5-tie-dbi contains:
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level/auto/Tie/ 
>> DBI/.packlist
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Tie/DBI.pm
>>  /opt/local/lib/perl5/vendor_perl/5.8.9/Tie/RDBM.pm
>>  /opt/local/share/man/man3/Tie::DBI.3pm.gz
>>  /opt/local/share/man/man3/Tie::RDBM.3pm.gz
>>
>> Looks to me like they are all there, and they should all work.  I  
>> do not know enough perl to run three basic tests to make calls to  
>> each, and confirm if it is in ASSP, or if it is in MacPorts. On  
>> another machine, a while back, I used CPAN, and had 100% success  
>> in making this work, but with that, I did not have to find and  
>> replace out the perl path.
>>
>> I am 99% there, and I will have an awesome port, with a option to  
>> pre-enable LDAP for my email server, and the ability to add the  
>> ldap strings for any other server, which is the hardest part of  
>> getting ASSP running live.
> --
> Scott
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From talklists at newgeo.com  Wed Jan 21 17:23:20 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 17:23:20 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
Message-ID: <B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>

I am telling ASSP where the new perl is, this issue is that some  
modules, only three of 15 or more, are being looked for in the wrong  
spot.

I do not know if I should solve this in the port, by editing the  
source of the app, or if there is some other way.  I actually hope  
there is some other way, as there should be no reason why I need to  
modify the source other than to change the perl path at the top of a  
few files.

On Jan 21, 2009, at 5:13 PM, Frank J. R. Hanstick wrote:

> Hello,
> 	It sounds like opt/local is not the first location the path  
> environment looks for perl.  This is a problem when several versions  
> of a program exists because unless a prefix is supplied, the default  
> program will always be found in the order of the pathname (first  
> detected).  If perl exists in /opt/local/bin and /usr/bin and the  
> path is in the order of /usr/bin:/opt/local/bin, then without a  
> prefix, /usr/bin will always be the perl used and visa versa if path  
> is /opt/local/bin:/usr/bin.  I ran into the same problem with gcc  
> located in two different locations.
> Frank

--
Scott


From kellert at ohsu.edu  Wed Jan 21 19:15:15 2009
From: kellert at ohsu.edu (Thomas Keller)
Date: Wed, 21 Jan 2009 19:15:15 -0800
Subject: requirement installed where the sun don't shine
Message-ID: <CA1D3B2B-4EC8-40CB-84DE-3A7D87DBF6E8@ohsu.edu>

Greetings,
I've run into this problem a couple of times. The latest incident is  
with install of wine. It requires fontforge which I installed "by  
hand" in its default location of /usr/local/bin/

how do I impart that path to port?

thanks,
Tom K


From TimLee at rochester.rr.com  Wed Jan 21 19:22:46 2009
From: TimLee at rochester.rr.com (Timothy Lee)
Date: Wed, 21 Jan 2009 22:22:46 -0500
Subject: Universal Binaries
Message-ID: <4246E330-FE64-4D04-B92E-311E1539A067@rochester.rr.com>

Hi Macports people!

Two questions:

1. What is the current state of the +universal variant? Do most ports  
work?

2. How is dependencies and the +universal variants used? Meaning if I  
type "sudo port install pan2 +universal" will that pass the variant to  
all dependencies that get built before pan2?

Thanks!
Tim

From trog24 at comcast.net  Wed Jan 21 19:56:40 2009
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Wed, 21 Jan 2009 19:56:40 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>
Message-ID: <74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>

Hello,
	The problem I had with two gcc's was that one call to the gcc was  
done direct (gcc) instead of an indirect prefix variable [ ($SRC) 
gcc ].  I would look into ASSP to be sure that all calls to perl  
modules use the indirect method.  There may be some elements where  
the call is direct (using the pathname) rather than using the  
indirect "I told you where to look".  If the three offending calls  
use the direct method, then those need to be changed to indirect.   
The behavior you describe points to what I have seen.  I may be  
wrong; but, it is a place to start.
Frank

On Jan 21, 2009, at 5:23 PM, Scott Haneda wrote:

> I am telling ASSP where the new perl is, this issue is that some  
> modules, only three of 15 or more, are being looked for in the  
> wrong spot.
>
> I do not know if I should solve this in the port, by editing the  
> source of the app, or if there is some other way.  I actually hope  
> there is some other way, as there should be no reason why I need to  
> modify the source other than to change the perl path at the top of  
> a few files.
>
> On Jan 21, 2009, at 5:13 PM, Frank J. R. Hanstick wrote:
>
>> Hello,
>> 	It sounds like opt/local is not the first location the path  
>> environment looks for perl.  This is a problem when several  
>> versions of a program exists because unless a prefix is supplied,  
>> the default program will always be found in the order of the  
>> pathname (first detected).  If perl exists in /opt/local/bin and / 
>> usr/bin and the path is in the order of /usr/bin:/opt/local/bin,  
>> then without a prefix, /usr/bin will always be the perl used and  
>> visa versa if path is /opt/local/bin:/usr/bin.  I ran into the  
>> same problem with gcc located in two different locations.
>> Frank
>
> --
> Scott
>


From talklists at newgeo.com  Wed Jan 21 21:14:54 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Wed, 21 Jan 2009 21:14:54 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>
	<74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>
Message-ID: <C8A02700-F88C-4CB7-B85B-414C552D8006@newgeo.com>

I will look into it, thanks.  If I can not get more definitive answers  
here, I also moved into the perl mail list as well.

The ASSP dev just told me to use CPAN, so I do not think he has any  
interest in working this out.  I personally feel it is a bug in ASSP,  
since other mods work, and this one seems to assume some standard  
location of perl.

On Jan 21, 2009, at 7:56 PM, Frank J. R. Hanstick wrote:

> Hello,
> 	The problem I had with two gcc's was that one call to the gcc was  
> done direct (gcc) instead of an indirect prefix variable  
> [ ($SRC)gcc ].  I would look into ASSP to be sure that all calls to  
> perl modules use the indirect method.  There may be some elements  
> where the call is direct (using the pathname) rather than using the  
> indirect "I told you where to look".  If the three offending calls  
> use the direct method, then those need to be changed to indirect.   
> The behavior you describe points to what I have seen.  I may be  
> wrong; but, it is a place to start.
> Frank
>
> On Jan 21, 2009, at 5:23 PM, Scott Haneda wrote:
>
>> I am telling ASSP where the new perl is, this issue is that some  
>> modules, only three of 15 or more, are being looked for in the  
>> wrong spot.
>>
>> I do not know if I should solve this in the port, by editing the  
>> source of the app, or if there is some other way.  I actually hope  
>> there is some other way, as there should be no reason why I need to  
>> modify the source other than to change the perl path at the top of  
>> a few files.
>>
>> On Jan 21, 2009, at 5:13 PM, Frank J. R. Hanstick wrote:
>>
>>> Hello,
>>> 	It sounds like opt/local is not the first location the path  
>>> environment looks for perl.  This is a problem when several  
>>> versions of a program exists because unless a prefix is supplied,  
>>> the default program will always be found in the order of the  
>>> pathname (first detected).  If perl exists in /opt/local/bin and / 
>>> usr/bin and the path is in the order of /usr/bin:/opt/local/bin,  
>>> then without a prefix, /usr/bin will always be the perl used and  
>>> visa versa if path is /opt/local/bin:/usr/bin.  I ran into the  
>>> same problem with gcc located in two different locations.
>>> Frank
>

--
Scott


From jeremyhu at macports.org  Thu Jan 22 00:38:46 2009
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Thu, 22 Jan 2009 00:38:46 -0800
Subject: Universal Binaries
In-Reply-To: <4246E330-FE64-4D04-B92E-311E1539A067@rochester.rr.com>
References: <4246E330-FE64-4D04-B92E-311E1539A067@rochester.rr.com>
Message-ID: <F588440F-AA89-4708-A58E-8DF23FB9676B@macports.org>


On Jan 21, 2009, at 19:22, Timothy Lee wrote:

> Hi Macports people!
>
> Two questions:
>
> 1. What is the current state of the +universal variant? Do most  
> ports work?

Not all ports do, but many do.  gimp and inkscape do, for instance...

If something doesn't work for you, file a bug.  I think it's mostly  
usable now.

> 2. How is dependencies and the +universal variants used? Meaning if  
> I type "sudo port install pan2 +universal" will that pass the  
> variant to all dependencies that get built before pan2?

It's probably best to start from scratch and put it in your $prefix/ 
etc/macports/variants.conf  MacPorts doesn't support variants in  
dependencies


From ryandesign at macports.org  Thu Jan 22 01:19:19 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 22 Jan 2009 03:19:19 -0600
Subject: Universal Binaries
In-Reply-To: <4246E330-FE64-4D04-B92E-311E1539A067@rochester.rr.com>
References: <4246E330-FE64-4D04-B92E-311E1539A067@rochester.rr.com>
Message-ID: <BD87B8D4-4D7A-40C7-8E89-2BA9457C60C6@macports.org>

On Jan 21, 2009, at 21:22, Timothy Lee wrote:

> 1. What is the current state of the +universal variant? Do most  
> ports work?

It's unknown if most ports work. If it doesn't work for ports you  
want, file tickets. Note that 64-bit universal support is likely more  
broken than plain 32-bit universal support.

It's possible we could fix this situation a great deal by switching  
ports to the new universal build strategy available in the merge- 
universal portgroup.


> 2. How is dependencies and the +universal variants used? Meaning if  
> I type "sudo port install pan2 +universal" will that pass the  
> variant to all dependencies that get built before pan2?

Yes, as with all variants, the variants you ask for will get passed  
down to any other port that needs to get *installed* (but not to any  
other port that's needed that you already have installed). If you  
want to install X universal, and X depends on Y and Z, and Y and/or Z  
are already installed, you must ensure that Y and Z are already  
universal, otherwise you will get (possibly cryptic) errors  
installing X universal.



From ryandesign at macports.org  Thu Jan 22 01:24:43 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 22 Jan 2009 03:24:43 -0600
Subject: requirement installed where the sun don't shine
In-Reply-To: <CA1D3B2B-4EC8-40CB-84DE-3A7D87DBF6E8@ohsu.edu>
References: <CA1D3B2B-4EC8-40CB-84DE-3A7D87DBF6E8@ohsu.edu>
Message-ID: <8759ACA3-60A5-43B9-A93E-36E3726E3694@macports.org>


On Jan 21, 2009, at 21:15, Thomas Keller wrote:

> I've run into this problem a couple of times. The latest incident  
> is with install of wine. It requires fontforge which I installed  
> "by hand" in its default location of /usr/local/bin/
>
> how do I impart that path to port?

You don't. MacPorts is designed to use its own libraries, not those  
you have installed in /usr/local or anywhere else. Please see:

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


wine used to declare a dependency on fontforge, until it was  
explained to me that wine does not actually require fontforge, so I  
removed the dependency. Please see:

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

If you have justification for bringing the fontforge dependency back,  
I'm all ears.



From ryandesign at macports.org  Thu Jan 22 01:27:36 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 22 Jan 2009 03:27:36 -0600
Subject: Can not get Net::SysLog installed
In-Reply-To: <67915607-F6FF-44ED-A6F2-DD073AAB10D4@newgeo.com>
References: <0D6FDE1D-8E93-4690-B38C-C51565B0B5F0@newgeo.com>
	<49770B4C.1030108@macports.org>
	<67915607-F6FF-44ED-A6F2-DD073AAB10D4@newgeo.com>
Message-ID: <9C08A769-2926-491D-9DBE-123D007AF421@macports.org>


On Jan 21, 2009, at 06:09, Scott Haneda wrote:

> On Jan 21, 2009, at 3:47 AM, Joshua Root wrote:
>
>> Scott Haneda wrote:
>>
>>> Can someone tell me where I am going wrong with this port?
>>
>>> perl5.setup             net-syslog 0.03
>>
>> You've used the wrong case here. Also the checksums are wrong. :-)
>
> Strange, I have never bothered with case since OS X is non case, I  
> assume this is failing on the download, since the case is wrong?  I  
> will go fiddle it and see what happens.

Mac OS X has a case-sensitive filesystem option which some users use.  
Also, MacPorts can be used on Linux, FreeBSD and other non-Mac  
operating systems where case-sensitive filesystems are the norm. For  
these reasons one must care about case in MacPorts.



From sgoddar1 at san.rr.com  Thu Jan 22 07:55:51 2009
From: sgoddar1 at san.rr.com (Joe&Shirley Goddard)
Date: Thu, 22 Jan 2009 07:55:51 -0800
Subject: Installation problems with Expect
Message-ID: <49789707.9080606@san.rr.com>

I am having the same problem, reported all over  the web,  with Macport 
installation of the program
Expect, apparently because of a problem recognizing the current version 
of Tcl. Does someone
have a work-around? Thanks. Joe Goddard

From jmr at macports.org  Thu Jan 22 08:35:56 2009
From: jmr at macports.org (Joshua Root)
Date: Fri, 23 Jan 2009 03:35:56 +1100
Subject: Installation problems with Expect
In-Reply-To: <49789707.9080606@san.rr.com>
References: <49789707.9080606@san.rr.com>
Message-ID: <4978A06C.8060709@macports.org>

Joe&Shirley Goddard wrote:
> I am having the same problem, reported all over  the web,  with Macport
> installation of the program
> Expect, apparently because of a problem recognizing the current version
> of Tcl. Does someone
> have a work-around? Thanks. Joe Goddard

This ticket is (unfortunately) still the current state of things:
<http://trac.macports.org/ticket/13827>

- Josh

From talklists at newgeo.com  Thu Jan 22 12:41:03 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Thu, 22 Jan 2009 12:41:03 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>
	<74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>
Message-ID: <72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>

I have this solved, but I do not know how to solve this in a way that  
works for MacPorts.  I am assuming there is a solution for the issues,  
since it seems it would be common to many perl ports.

perl uses @INC to figure out where your perl modes are, you can check  
with:
perl -e 'print join "\n", @INC'

With MacPorts you will need to use the /opt/local path to perl

So, for reasons I am not entirely sure of, some perl mods will look at  
the macports @INC, and some will look at the default @INC.  How do we  
solve this?  Why do some perl mods look in the default, is this  
something I should take to the developers of the perl mods?

There seems to be two ways to solve this:
1. Add the directory to the PERL5LIB environment variable.
2. Add use lib 'directory'; in your Perl script.

I think the first way is simplest, but not so portable.  I am not even  
sure a port file can modify .profile or .bashrc, and even then, from  
what my experience is, env vars are a gotcha moment with MacPorts.  It  
certainly lives outside of /opt/local so to me, less than idea.

The second way may be best, but I have to work with the developer of  
ASSP to figure out where to best add this in.

Any suggestions?

On Jan 21, 2009, at 7:56 PM, Frank J. R. Hanstick wrote:

> Hello,
> 	The problem I had with two gcc's was that one call to the gcc was  
> done direct (gcc) instead of an indirect prefix variable  
> [ ($SRC)gcc ].  I would look into ASSP to be sure that all calls to  
> perl modules use the indirect method.  There may be some elements  
> where the call is direct (using the pathname) rather than using the  
> indirect "I told you where to look".  If the three offending calls  
> use the direct method, then those need to be changed to indirect.   
> The behavior you describe points to what I have seen.  I may be  
> wrong; but, it is a place to start.
> Frank
>

--
Scott


From jjstickel at vcn.com  Thu Jan 22 13:23:26 2009
From: jjstickel at vcn.com (Jonathan Stickel)
Date: Thu, 22 Jan 2009 14:23:26 -0700
Subject: system_x11 variant ignored during upgrade
Message-ID: <4978E3CE.4090708@vcn.com>

I am attempting to upgrade my outdated ports, and am curious to see how 
the newly implemented "system_x11" variant will work.  I upgraded with:

$ sudo port -u upgrade outdated

and sure enough, one of my outdated ports depends on xorg-libX11. 
However, the system_x11 variant was ignored, even though I have it set 
in /opt/local/etc/macports/variants.conf.  If I install xorg-libX11 
directly by

$ sudo port install xorg-X11

then it seems to work.  Is this a bug that I should report on the tracker?

Thanks,
Jonathan

From blb at macports.org  Thu Jan 22 14:02:49 2009
From: blb at macports.org (Bryan Blackburn)
Date: Thu, 22 Jan 2009 15:02:49 -0700
Subject: system_x11 variant ignored during upgrade
In-Reply-To: <4978E3CE.4090708@vcn.com>
References: <4978E3CE.4090708@vcn.com>
Message-ID: <20090122220249.GE691@ninagal.withay.com>

On Thu, Jan 22, 2009 at 02:23:26PM -0700, Jonathan Stickel said:
> I am attempting to upgrade my outdated ports, and am curious to see how  
> the newly implemented "system_x11" variant will work.  I upgraded with:
>
> $ sudo port -u upgrade outdated
>
> and sure enough, one of my outdated ports depends on xorg-libX11.  
> However, the system_x11 variant was ignored, even though I have it set in 
> /opt/local/etc/macports/variants.conf.  If I install xorg-libX11 directly 
> by
>
> $ sudo port install xorg-X11
>
> then it seems to work.  Is this a bug that I should report on the tracker?

Sounds like #8221:

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

Fortunately, fixed on trunk so it should be part of 1.8.

Bryan


>
> Thanks,
> Jonathan

From ryandesign at macports.org  Thu Jan 22 16:30:00 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 22 Jan 2009 18:30:00 -0600
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>
	<74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>
	<72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>
Message-ID: <ED894C6F-EF85-46EC-830B-F4C8EDAFDE49@macports.org>


On Jan 22, 2009, at 14:41, Scott Haneda wrote:

> There seems to be two ways to solve this:
> 1. Add the directory to the PERL5LIB environment variable.
> 2. Add use lib 'directory'; in your Perl script.
>
> I think the first way is simplest, but not so portable.  I am not  
> even sure a port file can modify .profile or .bashrc, and even  
> then, from what my experience is, env vars are a gotcha moment with  
> MacPorts.  It certainly lives outside of /opt/local so to me, less  
> than idea.
>
> The second way may be best, but I have to work with the developer  
> of ASSP to figure out where to best add this in.

I will just say that a port should not modify the user's .profile. If  
a port needs a modification to the user's .profile, it should print a  
message telling the user what change they should make.


From talklists at newgeo.com  Thu Jan 22 16:46:07 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Thu, 22 Jan 2009 16:46:07 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <ED894C6F-EF85-46EC-830B-F4C8EDAFDE49@macports.org>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>
	<74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>
	<72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>
	<ED894C6F-EF85-46EC-830B-F4C8EDAFDE49@macports.org>
Message-ID: <5D77E993-85F2-4B2A-9379-EADC7046BF0B@newgeo.com>

On Jan 22, 2009, at 4:30 PM, Ryan Schmidt wrote:

> On Jan 22, 2009, at 14:41, Scott Haneda wrote:
>
>> There seems to be two ways to solve this:
>> 1. Add the directory to the PERL5LIB environment variable.
>> 2. Add use lib 'directory'; in your Perl script.
>>
>> I think the first way is simplest, but not so portable.  I am not  
>> even sure a port file can modify .profile or .bashrc, and even  
>> then, from what my experience is, env vars are a gotcha moment with  
>> MacPorts.  It certainly lives outside of /opt/local so to me, less  
>> than idea.
>>
>> The second way may be best, but I have to work with the developer  
>> of ASSP to figure out where to best add this in.
>
> I will just say that a port should not modify the user's .profile.  
> If a port needs a modification to the user's .profile, it should  
> print a message telling the user what change they should make.


Whether or not you chimed in and stated that, it was my feeling it  
should not anyway, so I am working to solve it in other ways.  The  
developer has started to be a bit more forthcoming with helping, so I  
will see what I can work out.
--
Scott


From ryandesign at macports.org  Thu Jan 22 17:15:06 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 22 Jan 2009 19:15:06 -0600
Subject: p5 modules, get me started on one
In-Reply-To: <2778265B-1293-4ED9-84AF-01E933702F7A@newgeo.com>
References: <20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
	<20090120073247.GR785@ninagal.withay.com>
	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
	<16926AEC-7084-4517-8338-B99FE9C35B41@newgeo.com>
	<20090121010109.GL965@ninagal.withay.com>
	<2AD35050-C46E-40C7-B993-4819F3F0CEE6@newgeo.com>
	<20090121094010.GU965@ninagal.withay.com>
	<2778265B-1293-4ED9-84AF-01E933702F7A@newgeo.com>
Message-ID: <4A02763E-F01B-4264-AC4A-123A2200DEDD@macports.org>

On Jan 21, 2009, at 05:00, Scott Haneda wrote:

>>> List it in the port description?  Will that get searched?  How do  
>>> I even
>>> get a list of what is in these packages from the CPAN site?
>>
>> In the long_description is what I was pondering; if you're running  
>> MacPorts
>> 1.7 'port search' will look in (among other field)  
>> long_description by
>> default, with trunk you'd need to add the --long_description flag  
>> to search
>> it.  Anything more specific to perl modules would mean changing  
>> base and of
>> course deciding first how that would work, etc...

Sigh, "port search" had just been changed in 1.7.0 to include the  
long description. And now we've removed it already? Why?


> Seems an ok way to deal with it, not ideal to me though.  I am not  
> sure if this problem is just perl module related, or is more  
> generic.  If it would be appropriate, the idea of adding a new  
> variable to port files may be a fair idea.
>
> file_contains or whatever is appropriate, which could then be  
> searched on by default.  It seems very common that this comes up.

Please no new variable. It uglies up the port. When reading the  
portfile, I want to be able to concentrate on reading the portfile,  
not wading through a list of files I don't care about. The ncursesw  
portfile is currently 38 lines long but it installs 3311 files; I  
don't want the portfile to grow 3311 lines longer.

Not to mention the nightmare of ensuring that the list is always up  
to date with the port. If I update a port to a new version, I'm not  
going to remember to run some process to get a list of files and copy  
it into the port, in case it has changed since the last version.

Plus, as I mentioned before, the problem that ports can install  
different files depending on the version of Mac OS X or the processor  
architecture or variants or other factors.

Back in the very early days of this project, there *was* a variable  
in the port where the files had to be listed. That was before I was  
with the project. But it looks like some ports used the "contents"  
keyword inside the portfile, and others put it in a separate  
"contents" file which was then include into the portfile. If a  
variant added files, then that variant had to update the contents  
keyword. I believe the reason for this variable was so that port knew  
what files belonged to the port, so that ports could be cleanly  
uninstalled. This was before there was a destroot; now that there is  
a destroot, MacPorts can automatically determine what files are part  
of the port. See for example this revision where the "contents"  
mechanism was removed from the apache port:

http://trac.macports.org/changeset/1772/trunk/dports/www/apache


>> Also, knowing that Net::SMTP is with the base perl5.8 port is  
>> something I
>> just knew because it's part of the perl libnet stuff which was  
>> integrated
>> into perl core some time ago.

[snip]

> The question of "How does a new user know that Net::SMTP is part of  
> the base?" is a problem.

A MacPorts *user* does not need to know that; they just need to know  
what port they ultimately want to install, and install it.

A MacPorts *maintainer* (of perl modules) does perhaps need to know  
that. But I think it's a matter of knowing your corner of the world.  
If you're interested in writing perl modules, you need to know a few  
things about perl, like that it includes a small number of modules;  
once you know that, you can use "port contents perl5.8" to see what  
modules are included.


> Also, is it still true than CPAN can get clobbered by Apple  
> Updates?  This is one of the best selling points of MacPorts.

I suppose that's possible. If you use CPAN with Apple's perl, then  
the modules would go into Apple-owned directories, with which Apple  
is free to do whatever they want when you run Apple updates.

If you use CPAN with MacPorts perl, presumably the modules would go  
in MacPorts-owned directories, so Apple updates wouldn't clobber  
them; on the other hand, MacPorts ports may conflict with manually- 
installed CPAN modules.


> Rarely is it easy :)  Curious, without going into a lot of detail,  
> how does the hugely raves about apt-get and equivalent get past all  
> this?

I don't know what other package managers do. You could ask on their  
mailing lists...



From blb at macports.org  Thu Jan 22 17:30:16 2009
From: blb at macports.org (Bryan Blackburn)
Date: Thu, 22 Jan 2009 18:30:16 -0700
Subject: p5 modules, get me started on one
In-Reply-To: <4A02763E-F01B-4264-AC4A-123A2200DEDD@macports.org>
References: <7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
	<20090120073247.GR785@ninagal.withay.com>
	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
	<16926AEC-7084-4517-8338-B99FE9C35B41@newgeo.com>
	<20090121010109.GL965@ninagal.withay.com>
	<2AD35050-C46E-40C7-B993-4819F3F0CEE6@newgeo.com>
	<20090121094010.GU965@ninagal.withay.com>
	<2778265B-1293-4ED9-84AF-01E933702F7A@newgeo.com>
	<4A02763E-F01B-4264-AC4A-123A2200DEDD@macports.org>
Message-ID: <20090123013016.GL691@ninagal.withay.com>

On Thu, Jan 22, 2009 at 07:15:06PM -0600, Ryan Schmidt said:
[...]
>
> Sigh, "port search" had just been changed in 1.7.0 to include the long 
> description. And now we've removed it already? Why?

Ticket #15434:

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

Some have felt 1.7.0's search returns too many results, so Rainer added the
options to specify where to search on trunk for 1.8

Bryan

[...]

From trog24 at comcast.net  Thu Jan 22 19:29:33 2009
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Thu, 22 Jan 2009 19:29:33 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>
	<74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>
	<72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>
Message-ID: <4D571F2E-0D5C-477F-A51A-769D6136D2D7@comcast.net>

Hello,
	In that the variable acts two different ways in two different  
locations, I would look to where the variable is set and for where  
the setting may change or for a broken link that causes @INC to be  
used as a local variable instead of a global.
Frank

On Jan 22, 2009, at 12:41 PM, Scott Haneda wrote:

> I have this solved, but I do not know how to solve this in a way  
> that works for MacPorts.  I am assuming there is a solution for the  
> issues, since it seems it would be common to many perl ports.
>
> perl uses @INC to figure out where your perl modes are, you can  
> check with:
> perl -e 'print join "\n", @INC'
>
> With MacPorts you will need to use the /opt/local path to perl
>
> So, for reasons I am not entirely sure of, some perl mods will look  
> at the macports @INC, and some will look at the default @INC.  How  
> do we solve this?  Why do some perl mods look in the default, is  
> this something I should take to the developers of the perl mods?
>
> There seems to be two ways to solve this:
> 1. Add the directory to the PERL5LIB environment variable.
> 2. Add use lib 'directory'; in your Perl script.
>
> I think the first way is simplest, but not so portable.  I am not  
> even sure a port file can modify .profile or .bashrc, and even  
> then, from what my experience is, env vars are a gotcha moment with  
> MacPorts.  It certainly lives outside of /opt/local so to me, less  
> than idea.
>
> The second way may be best, but I have to work with the developer  
> of ASSP to figure out where to best add this in.
>
> Any suggestions?
>
> On Jan 21, 2009, at 7:56 PM, Frank J. R. Hanstick wrote:
>
>> Hello,
>> 	The problem I had with two gcc's was that one call to the gcc was  
>> done direct (gcc) instead of an indirect prefix variable [ ($SRC) 
>> gcc ].  I would look into ASSP to be sure that all calls to perl  
>> modules use the indirect method.  There may be some elements where  
>> the call is direct (using the pathname) rather than using the  
>> indirect "I told you where to look".  If the three offending calls  
>> use the direct method, then those need to be changed to indirect.   
>> The behavior you describe points to what I have seen.  I may be  
>> wrong; but, it is a place to start.
>> Frank
>>
>
> --
> Scott
>


From TimLee at rochester.rr.com  Thu Jan 22 19:59:56 2009
From: TimLee at rochester.rr.com (Timothy Lee)
Date: Thu, 22 Jan 2009 22:59:56 -0500
Subject: Universal Binaries
In-Reply-To: <BD87B8D4-4D7A-40C7-8E89-2BA9457C60C6@macports.org>
References: <4246E330-FE64-4D04-B92E-311E1539A067@rochester.rr.com>
	<BD87B8D4-4D7A-40C7-8E89-2BA9457C60C6@macports.org>
Message-ID: <9AE775F7-9732-4D08-A4FA-460D7FC39D21@rochester.rr.com>

I just compile 1.7.0 from source and my macports.conf universal_target  
has a 10.4 next to it. However, when I compile on my Leopard machine,  
I see DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'.

I thought universal_targe would set the MACOSX_DEPLOYMENT_TARGET.

Am I wrong?


On Jan 22, 2009, at 4:19 AM, Ryan Schmidt wrote:

> On Jan 21, 2009, at 21:22, Timothy Lee wrote:
>
>> 1. What is the current state of the +universal variant? Do most  
>> ports work?
>
> It's unknown if most ports work. If it doesn't work for ports you  
> want, file tickets. Note that 64-bit universal support is likely  
> more broken than plain 32-bit universal support.
>
> It's possible we could fix this situation a great deal by switching  
> ports to the new universal build strategy available in the merge- 
> universal portgroup.
>
>
>> 2. How is dependencies and the +universal variants used? Meaning if  
>> I type "sudo port install pan2 +universal" will that pass the  
>> variant to all dependencies that get built before pan2?
>
> Yes, as with all variants, the variants you ask for will get passed  
> down to any other port that needs to get *installed* (but not to any  
> other port that's needed that you already have installed). If you  
> want to install X universal, and X depends on Y and Z, and Y and/or  
> Z are already installed, you must ensure that Y and Z are already  
> universal, otherwise you will get (possibly cryptic) errors  
> installing X universal.
>
>


From talklists at newgeo.com  Thu Jan 22 20:23:34 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Thu, 22 Jan 2009 20:23:34 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <4D571F2E-0D5C-477F-A51A-769D6136D2D7@comcast.net>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>
	<74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>
	<72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>
	<4D571F2E-0D5C-477F-A51A-769D6136D2D7@comcast.net>
Message-ID: <6A1DB50D-09B5-4843-8BB1-F3E37D7E7B69@newgeo.com>

Forigve me... Would this var be in the ASSP code, or in the perl mod?   
I would be more than happy to track it down, but I do not fully  
understand how this @INC variable works.

On Jan 22, 2009, at 7:29 PM, Frank J. R. Hanstick wrote:

> Hello,
> 	In that the variable acts two different ways in two different  
> locations, I would look to where the variable is set and for where  
> the setting may change or for a broken link that causes @INC to be  
> used as a local variable instead of a global.
> Frank
>
> On Jan 22, 2009, at 12:41 PM, Scott Haneda wrote:
>
>> I have this solved, but I do not know how to solve this in a way  
>> that works for MacPorts.  I am assuming there is a solution for the  
>> issues, since it seems it would be common to many perl ports.
>>
>> perl uses @INC to figure out where your perl modes are, you can  
>> check with:
>> perl -e 'print join "\n", @INC'
>>
>> With MacPorts you will need to use the /opt/local path to perl
>>
>> So, for reasons I am not entirely sure of, some perl mods will look  
>> at the macports @INC, and some will look at the default @INC.  How  
>> do we solve this?  Why do some perl mods look in the default, is  
>> this something I should take to the developers of the perl mods?
>>
>> There seems to be two ways to solve this:
>> 1. Add the directory to the PERL5LIB environment variable.
>> 2. Add use lib 'directory'; in your Perl script.
>>
>> I think the first way is simplest, but not so portable.  I am not  
>> even sure a port file can modify .profile or .bashrc, and even  
>> then, from what my experience is, env vars are a gotcha moment with  
>> MacPorts.  It certainly lives outside of /opt/local so to me, less  
>> than idea.
>>
>> The second way may be best, but I have to work with the developer  
>> of ASSP to figure out where to best add this in.
>>
>> Any suggestions?
>>
>> On Jan 21, 2009, at 7:56 PM, Frank J. R. Hanstick wrote:
>>
>>> Hello,
>>> 	The problem I had with two gcc's was that one call to the gcc was  
>>> done direct (gcc) instead of an indirect prefix variable  
>>> [ ($SRC)gcc ].  I would look into ASSP to be sure that all calls  
>>> to perl modules use the indirect method.  There may be some  
>>> elements where the call is direct (using the pathname) rather than  
>>> using the indirect "I told you where to look".  If the three  
>>> offending calls use the direct method, then those need to be  
>>> changed to indirect.  The behavior you describe points to what I  
>>> have seen.  I may be wrong; but, it is a place to start.
>>> Frank
>>>
>>
>> --
>> Scott
>>
>

--
Scott


From trog24 at comcast.net  Thu Jan 22 20:51:20 2009
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Thu, 22 Jan 2009 20:51:20 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <6A1DB50D-09B5-4843-8BB1-F3E37D7E7B69@newgeo.com>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>
	<74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>
	<72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>
	<4D571F2E-0D5C-477F-A51A-769D6136D2D7@comcast.net>
	<6A1DB50D-09B5-4843-8BB1-F3E37D7E7B69@newgeo.com>
Message-ID: <0D359BF3-13C5-46DF-9AB5-A9E382A2BC7D@comcast.net>

Hello,
	Which is a little too deep for me.  I am only indicating anomalies  
from expected behavior and possible causes.  My guess would be ASSP  
since it is looking for the modules.  There might be a difference in  
the reference formation.  The alternative is to wait for someone else  
to fix the problem.
Frank

On Jan 22, 2009, at 8:23 PM, Scott Haneda wrote:

> Forigve me... Would this var be in the ASSP code, or in the perl  
> mod?  I would be more than happy to track it down, but I do not  
> fully understand how this @INC variable works.
>
> On Jan 22, 2009, at 7:29 PM, Frank J. R. Hanstick wrote:
>
>> Hello,
>> 	In that the variable acts two different ways in two different  
>> locations, I would look to where the variable is set and for where  
>> the setting may change or for a broken link that causes @INC to be  
>> used as a local variable instead of a global.
>> Frank
>>
>> On Jan 22, 2009, at 12:41 PM, Scott Haneda wrote:
>>
>>> I have this solved, but I do not know how to solve this in a way  
>>> that works for MacPorts.  I am assuming there is a solution for  
>>> the issues, since it seems it would be common to many perl ports.
>>>
>>> perl uses @INC to figure out where your perl modes are, you can  
>>> check with:
>>> perl -e 'print join "\n", @INC'
>>>
>>> With MacPorts you will need to use the /opt/local path to perl
>>>
>>> So, for reasons I am not entirely sure of, some perl mods will  
>>> look at the macports @INC, and some will look at the default  
>>> @INC.  How do we solve this?  Why do some perl mods look in the  
>>> default, is this something I should take to the developers of the  
>>> perl mods?
>>>
>>> There seems to be two ways to solve this:
>>> 1. Add the directory to the PERL5LIB environment variable.
>>> 2. Add use lib 'directory'; in your Perl script.
>>>
>>> I think the first way is simplest, but not so portable.  I am not  
>>> even sure a port file can modify .profile or .bashrc, and even  
>>> then, from what my experience is, env vars are a gotcha moment  
>>> with MacPorts.  It certainly lives outside of /opt/local so to  
>>> me, less than idea.
>>>
>>> The second way may be best, but I have to work with the developer  
>>> of ASSP to figure out where to best add this in.
>>>
>>> Any suggestions?
>>>
>>> On Jan 21, 2009, at 7:56 PM, Frank J. R. Hanstick wrote:
>>>
>>>> Hello,
>>>> 	The problem I had with two gcc's was that one call to the gcc  
>>>> was done direct (gcc) instead of an indirect prefix variable  
>>>> [ ($SRC)gcc ].  I would look into ASSP to be sure that all calls  
>>>> to perl modules use the indirect method.  There may be some  
>>>> elements where the call is direct (using the pathname) rather  
>>>> than using the indirect "I told you where to look".  If the  
>>>> three offending calls use the direct method, then those need to  
>>>> be changed to indirect.  The behavior you describe points to  
>>>> what I have seen.  I may be wrong; but, it is a place to start.
>>>> Frank
>>>>
>>>
>>> --
>>> Scott
>>>
>>
>
> --
> Scott
>


From talklists at newgeo.com  Thu Jan 22 21:43:19 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Thu, 22 Jan 2009 21:43:19 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <0D359BF3-13C5-46DF-9AB5-A9E382A2BC7D@comcast.net>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>
	<74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>
	<72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>
	<4D571F2E-0D5C-477F-A51A-769D6136D2D7@comcast.net>
	<6A1DB50D-09B5-4843-8BB1-F3E37D7E7B69@newgeo.com>
	<0D359BF3-13C5-46DF-9AB5-A9E382A2BC7D@comcast.net>
Message-ID: <ED9F55D0-7688-4640-8F01-EB6C91263FA6@newgeo.com>

ASSP just calls Email::Valid, so I have a feeling it is in the  
Email::Valid code itself.  I am going to probe the perl beginners list.

On Jan 22, 2009, at 8:51 PM, Frank J. R. Hanstick wrote:

> Hello,
> 	Which is a little too deep for me.  I am only indicating anomalies  
> from expected behavior and possible causes.  My guess would be ASSP  
> since it is looking for the modules.  There might be a difference in  
> the reference formation.  The alternative is to wait for someone  
> else to fix the problem.

--
Scott


From ryandesign at macports.org  Thu Jan 22 21:47:28 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 22 Jan 2009 23:47:28 -0600
Subject: Universal Binaries
In-Reply-To: <9AE775F7-9732-4D08-A4FA-460D7FC39D21@rochester.rr.com>
References: <4246E330-FE64-4D04-B92E-311E1539A067@rochester.rr.com>
	<BD87B8D4-4D7A-40C7-8E89-2BA9457C60C6@macports.org>
	<9AE775F7-9732-4D08-A4FA-460D7FC39D21@rochester.rr.com>
Message-ID: <520500B5-1A35-4BFF-A3CF-A5F1DB1B42ED@macports.org>


On Jan 22, 2009, at 21:59, Timothy Lee wrote:

> I just compile 1.7.0 from source and my macports.conf  
> universal_target has a 10.4 next to it. However, when I compile on  
> my Leopard machine, I see DEBUG: Environment:  
> MACOSX_DEPLOYMENT_TARGET='10.5'.
>
> I thought universal_targe would set the MACOSX_DEPLOYMENT_TARGET.
>
> Am I wrong?

universal_target is what is used to fill the MACOSX_DEPLOYMENT_TARGET  
variable. MacPorts should be setting this by default to whatever is  
right for the current OS: 10.3 on 10.3, 10.4 on 10.4, 10.5 on 10.5.  
If the macports.conf has this setting listed, then that overrides the  
default behavior.



From ryandesign at macports.org  Thu Jan 22 22:03:59 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 23 Jan 2009 00:03:59 -0600
Subject: gd2 fails on perl5
In-Reply-To: <A4B13498-1CD1-44AC-9EBA-5DBFA037D4D1@pixilla.com>
References: <D40DD212-0F6B-406D-A315-E5098A09C0CE@pixilla.com>
	<496AD51B.4020605@macports.org>
	<DA77313C-D6D8-406E-A9C8-B7162BE4ACD5@pixilla.com>
	<496AF30B.2070006@macports.org>
	<86CFF93B-ED95-4B30-8832-D941C1B375F5@pixilla.com>
	<DE28B0CA-1F3D-44DA-8910-4107EDCFB888@macports.org>
	<B681B217-F416-47D4-823B-70B258877268@pixilla.com>
	<20090114214248.GW1155@darkart.com>
	<A4B13498-1CD1-44AC-9EBA-5DBFA037D4D1@pixilla.com>
Message-ID: <B41297D1-AA17-493B-9E9B-2C8A2A6BB9A8@macports.org>


On Jan 14, 2009, at 16:28, Bradley Giesbrecht wrote:

>> There is a problem with some
>> ports automatically finding things installed under /usr/local,
>> and it is impractical to expect port authors to catch every
>> instance of that - that should be made clear to people (if it
>> isn't already).
>
> We agree. Also, if I already have mysql(d) installed somewhere else  
> (like os x server) and would like to keep what I have I'd be happy  
> if macports would use what I already have rather then build another  
> mysql(d) and force me to use this.

It's not MacPorts that needs to know about and optionally use such an  
existing MySQL; it's each individual port that wants to offer that  
option. For example, here is the open request to add that capability  
to the php5 port:

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


>> 	Also, if the MacPorts versions of software (mysql and php
>> as pointed out above) don't provided what you need, asking for
>> enhancements so that they do will (nominally) benefit you and
>> others, please file tickets (http://trac.macports.org) requesting
>> such.
>
> I did, and submitted a patch to add variants to bind9 and dovecot.  
> I have heard nothing back.

I apologize, I do recall that request, but I cannot find the email or  
ticket about it now. If there was a ticket, could you remind me of  
the ticket number? If the request was by email, could you forward it  
to me again? Thanks.


From talklists at newgeo.com  Fri Jan 23 00:31:47 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Fri, 23 Jan 2009 00:31:47 -0800
Subject: p5 modules, get me started on one
In-Reply-To: <4A02763E-F01B-4264-AC4A-123A2200DEDD@macports.org>
References: <20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
	<20090120073247.GR785@ninagal.withay.com>
	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
	<16926AEC-7084-4517-8338-B99FE9C35B41@newgeo.com>
	<20090121010109.GL965@ninagal.withay.com>
	<2AD35050-C46E-40C7-B993-4819F3F0CEE6@newgeo.com>
	<20090121094010.GU965@ninagal.withay.com>
	<2778265B-1293-4ED9-84AF-01E933702F7A@newgeo.com>
	<4A02763E-F01B-4264-AC4A-123A2200DEDD@macports.org>
Message-ID: <7F0DB44D-3E96-40D4-A0FA-61861D5586AA@newgeo.com>

On Jan 22, 2009, at 5:15 PM, Ryan Schmidt wrote:
> On Jan 21, 2009, at 05:00, Scott Haneda wrote:
>
>>>> List it in the port description?  Will that get searched?  How do  
>>>> I even
>>>> get a list of what is in these packages from the CPAN site?
>>>
>> Seems an ok way to deal with it, not ideal to me though.  I am not  
>> sure if this problem is just perl module related, or is more  
>> generic.  If it would be appropriate, the idea of adding a new  
>> variable to port files may be a fair idea.
>>
>> file_contains or whatever is appropriate, which could then be  
>> searched on by default.  It seems very common that this comes up.
>
> Please no new variable. It uglies up the port. When reading the  
> portfile, I want to be able to concentrate on reading the portfile,  
> not wading through a list of files I don't care about. The ncursesw  
> portfile is currently 38 lines long but it installs 3311 files; I  
> don't want the portfile to grow 3311 lines longer.

Is there any official guidance on this matter?  I am making perl  
module ports, and I generally go to CPAN, copy the title, and use that  
as the short desc, and for the long desc, I use their main  
description.  This can be long at times, is that not recommended?

>>> Also, knowing that Net::SMTP is with the base perl5.8 port is  
>>> something I
>>> just knew because it's part of the perl libnet stuff which was  
>>> integrated
>>> into perl core some time ago.
>
> [snip]
>
>> The question of "How does a new user know that Net::SMTP is part of  
>> the base?" is a problem.
>
> A MacPorts *user* does not need to know that; they just need to know  
> what port they ultimately want to install, and install it.

And I think I am a good case in which that sort of failed me. I needed  
Net::SMTP, but to me, as a user, it was not there.  I tried port list  
p5-net-smtp, and nothing.

This brings up a point, why was the naming convention changed?  It  
took me a while to even learn to prepend p5 and convert :: to -

Next, I tried `port search p5-net-smtp*` and I beleive, I got back p5- 
net-smtp-auth or close to it.  So still no match. Try as I might, I  
could not locate it, so I made my own portfile.  It was then, I found  
out, it was included in another higher up module.

For some reason, I skipped looking for that module, and tried to make  
a port for it, only to learn it was there. Good to learn it was there,  
so I could not take any more time on that one.

But, your statement of "... *user* does not need to know that ... "  
does not ring entirely true for me.  I had a list of modules I needed,  
90% of them did not immediately appear to be available.  In the end,  
about 50% of them were, but it was hard to locate them.

What if every perl module had a port file, and all it was was a port  
file that had a dependency back to the parent module that it is a part  
of?  Then search would find what it needed to, other port files would  
not get dirty with lists of included modules.

> A MacPorts *maintainer* (of perl modules) does perhaps need to know  
> that. But I think it's a matter of knowing your corner of the world.  
> If you're interested in writing perl modules, you need to know a few  
> things about perl, like that it includes a small number of modules;  
> once you know that, you can use "port contents perl5.8" to see what  
> modules are included.

I understand now, though I am still not sure I agree. I can manage,  
and don't get me wrong, I love this system and really commend you guys  
on your mailing list support, so I am not complaining at all.

This probably only applies to perl modules, and maybe some php modules  
or ruby gems.  At any rate, if I need foo::bar::baz I should be able  
to `port search p5-foo-bar-baz` and get something in the case it is  
part of some larger module package.

I would really like to know the history of why I can not `port install  
foo::bar::baz if even only an internal remap to use the standard ::  
notation.  Is this a tcl collision of some sort?

I sort of like the idea of a port file being a pointer to download  
some other package that contains the parent modules, unless someone  
tells me it is a really bad idea.

Thanks for the dialogue.
--
Scott


From jmr at macports.org  Fri Jan 23 00:42:07 2009
From: jmr at macports.org (Joshua Root)
Date: Fri, 23 Jan 2009 19:42:07 +1100
Subject: Universal Binaries
In-Reply-To: <520500B5-1A35-4BFF-A3CF-A5F1DB1B42ED@macports.org>
References: <4246E330-FE64-4D04-B92E-311E1539A067@rochester.rr.com>	<BD87B8D4-4D7A-40C7-8E89-2BA9457C60C6@macports.org>	<9AE775F7-9732-4D08-A4FA-460D7FC39D21@rochester.rr.com>
	<520500B5-1A35-4BFF-A3CF-A5F1DB1B42ED@macports.org>
Message-ID: <497982DF.70407@macports.org>

Ryan Schmidt wrote:
> 
> On Jan 22, 2009, at 21:59, Timothy Lee wrote:
> 
>> I just compile 1.7.0 from source and my macports.conf universal_target
>> has a 10.4 next to it. However, when I compile on my Leopard machine,
>> I see DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'.
>>
>> I thought universal_targe would set the MACOSX_DEPLOYMENT_TARGET.
>>
>> Am I wrong?
> 
> universal_target is what is used to fill the MACOSX_DEPLOYMENT_TARGET
> variable. MacPorts should be setting this by default to whatever is
> right for the current OS: 10.3 on 10.3, 10.4 on 10.4, 10.5 on 10.5. If
> the macports.conf has this setting listed, then that overrides the
> default behavior.

Not quite. It uses universal_target when the universal variant is
selected, otherwise it uses a variable called macosx_deployment_target,
which can be changed from portfiles but not from macports.conf.

- Josh

From jmr at macports.org  Fri Jan 23 00:45:15 2009
From: jmr at macports.org (Joshua Root)
Date: Fri, 23 Jan 2009 19:45:15 +1100
Subject: p5 modules, get me started on one
In-Reply-To: <7F0DB44D-3E96-40D4-A0FA-61861D5586AA@newgeo.com>
References: <20090120025055.GN785@ninagal.withay.com>	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>	<20090120055648.GI1155@darkart.com>	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>	<20090120073247.GR785@ninagal.withay.com>	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>	<16926AEC-7084-4517-8338-B99FE9C35B41@newgeo.com>	<20090121010109.GL965@ninagal.withay.com>	<2AD35050-C46E-40C7-B993-4819F3F0CEE6@newgeo.com>	<20090121094010.GU965@ninagal.withay.com>	<2778265B-1293-4ED9-84AF-01E933702F7A@newgeo.com>	<4A02763E-F01B-4264-AC4A-123A2200DEDD@macports.org>
	<7F0DB44D-3E96-40D4-A0FA-61861D5586AA@newgeo.com>
Message-ID: <4979839B.4030704@macports.org>

Scott Haneda wrote:
> I would really like to know the history of why I can not `port install
> foo::bar::baz if even only an internal remap to use the standard ::
> notation.  Is this a tcl collision of some sort?

There isn't really any history. MacPorts is not CPAN, so nobody ever
considered allowing perl-specific notation.

- Josh

From talklists at newgeo.com  Fri Jan 23 03:31:14 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Fri, 23 Jan 2009 03:31:14 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <ED894C6F-EF85-46EC-830B-F4C8EDAFDE49@macports.org>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>
	<74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>
	<72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>
	<ED894C6F-EF85-46EC-830B-F4C8EDAFDE49@macports.org>
Message-ID: <F1FA8438-2B18-42B9-A5DF-E55C82356FF6@newgeo.com>

Turns out this is not ASSP, or env vars at all.  I distilled it down  
to a simple test...

#!/opt/local/bin/perl --
use strict;

our $AvailSPF2 = eval("use Mail::SPF; 1");

if ($AvailSPF2) {
	print "true\n";
	my $ver = eval('Mail::SPF->VERSION');
	print $ver
} else {
	print "false\n";
}

I come up false on that one, so apparently, it is not installed, or  
installed wrong.

Here is the portfile

# $Id$
PortSystem 1.0
PortGroup perl5 1.0

perl5.setup             Mail-SPF v2.006
maintainers             hostwizard.com:scott

description       	Mail::SPF - An object-oriented implementation of  
Sender Policy Framework

long_description        Mail::SPF is an object-oriented implementation  
of \
			Sender Policy Framework (SPF). See http://www.openspf.org \
			for more information about SPF. \
			\
			This class collection aims to fully conform to the SPF \
			specification (RFC 4408) so as to serve both as a \
			production quality SPF implementation and as a reference \
			for other developers of SPF implementations.

homepage		http://search.cpan.org/dist/Mail-SPF/lib/Mail/SPF.pm

checksums           	md5     4da41591b612560627ddbc6026b047a3 \
                     	sha1    301b33f66d3a14a26c497fd80b91d6c7d5ce9faa \
                     	rmd160  5d7244a0dc21979159f6bbba11da1590b3f2c6ba

platforms               darwin

Here is ports telling me it is in fact installed:
`port list installed | grep p5-mail-spf`
p5-mail-spf                    @v2.006         perl/p5-mail-spf

Quick test to see if it works:
/opt/local/bin/perl -MMail::SPF -e 'print $INC{"Mail/SPF.pm"}'

Can't locate version.pm in @INC (@INC contains: /opt/local/lib/ 
perl5/5.8.9/darwin-2level /opt/local/lib/perl5/5.8.9 /opt/local/lib/ 
perl5/site_perl/5.8.9/darwin-2level /opt/local/lib/perl5/site_perl/ 
5.8.9 /opt/local/lib/perl5/site_perl /opt/local/lib/perl5/vendor_perl/ 
5.8.9/darwin-2level /opt/local/lib/perl5/vendor_perl/5.8.9 /opt/local/ 
lib/perl5/vendor_perl .) at /opt/local/lib/perl5/vendor_perl/5.8.9/ 
Mail/SPF.pm line 24.
BEGIN failed--compilation aborted at /opt/local/lib/perl5/vendor_perl/ 
5.8.9/Mail/SPF.pm line 24.
Compilation failed in require.
BEGIN failed--compilation aborted.

How do I get it to install correctly?
--
Scott


From talklists at newgeo.com  Fri Jan 23 03:36:53 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Fri, 23 Jan 2009 03:36:53 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <ED894C6F-EF85-46EC-830B-F4C8EDAFDE49@macports.org>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>
	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>
	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>
	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>
	<74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>
	<72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>
	<ED894C6F-EF85-46EC-830B-F4C8EDAFDE49@macports.org>
Message-ID: <01BB3178-DAD4-41BF-9C38-B79AE58A2DF4@newgeo.com>

Looking back over the install log:

Warning: violation by /usr
Warning: p5-mail-spf violates the layout of the ports-filesystems!
Warning: Please fix or indicate this misbehavior (if it is intended),  
it will be an error in future releases!
--->  Installing p5-mail-spf @v2.006_0

I did some quick searching.... I am taking a guess, but does this mod  
try to install somewhere it should not be installing?  What is the  
course of action here, modify the source, or go to the developer?
--
Scott


From jmr at macports.org  Fri Jan 23 03:43:42 2009
From: jmr at macports.org (Joshua Root)
Date: Fri, 23 Jan 2009 22:43:42 +1100
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <01BB3178-DAD4-41BF-9C38-B79AE58A2DF4@newgeo.com>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>	<74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>	<72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>	<ED894C6F-EF85-46EC-830B-F4C8EDAFDE49@macports.org>
	<01BB3178-DAD4-41BF-9C38-B79AE58A2DF4@newgeo.com>
Message-ID: <4979AD6E.30003@macports.org>

Scott Haneda wrote:
> Looking back over the install log:
> 
> Warning: violation by /usr
> Warning: p5-mail-spf violates the layout of the ports-filesystems!
> Warning: Please fix or indicate this misbehavior (if it is intended), it
> will be an error in future releases!
> --->  Installing p5-mail-spf @v2.006_0
> 
> I did some quick searching.... I am taking a guess, but does this mod
> try to install somewhere it should not be installing?  What is the
> course of action here, modify the source, or go to the developer?

Yes, that would certainly be the problem. Use `port contents
p5-mail-spf` to see exactly what has been installed where. Other perl
module ports install to $prefix, so it does seem to be a bug with this
particular module, or at least an oddity that makes it need special
treatment.

- Josh

From ryandesign at macports.org  Fri Jan 23 04:27:51 2009
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 23 Jan 2009 06:27:51 -0600
Subject: Error after trying to upgrade installed
In-Reply-To: <alpine.OSX.2.00L.0901190811250.80957@teraqry.sevanohynk.bet>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<alpine.OSX.2.00L.0901190811250.80957@teraqry.sevanohynk.bet>
Message-ID: <5E17D0EB-8173-4C41-AD00-2B32BBCD1ECE@macports.org>

On Jan 19, 2009, at 07:37, robert delius royar wrote:

> So much traffic on this thread, so much time spent answering  
> questions. But I do not recall any of the answerers trying
> port provides /opt/local/lib/libintl.dylib

Sorry; I thought it was already understood that libintl is the  
internationalization library and that it is provided by gettext.


> That would have pointerd out that the initial problem of gettext  
> wanting to reinstall itself (perhaps for no good reason) had  
> removed the dylibs that gettext provides and uses, itself.

"For no good reason" depends on your situation. In this particular  
case, gettext was updated from 0.17_3 to 0.17_4 because some 64-bit  
issues were corrected. If anyone had installed 0.17_3 with the  
+universal variant and had requested 64-bit architectures in the  
universal_archs variable in macports.conf, they would have had an  
incorrectly-functioning gettext, so for those users, it was necessary  
to force a rebuild by increasing the port's revision. If you did not  
have gettext installed with the +universal variant, or had not  
selected any 64-bit architectures in macports.conf (the default is  
only the 32-bit architectures ppc and i386) then you would not have  
been affected and would not need to rebuild gettext.

When using MacPorts, you can either assume that MacPorts maintainers  
know what they are doing and if they are requesting you to rebuild a  
port (as evidenced by it showing up in "port outdated") then you  
rebuild it. Or if you have the inclination you can dig deeper,  
subscribe to the macports-changes mailing list, monitor the changes  
taking place to the ports you use, and evaluate for yourself whether  
you need the changes provided in a new port revision, and if you  
don't, then don't upgrade the port until it's updated again later  
with a fix that you do want.

For many users the former strategy is sufficient, even to the point  
of just running "sudo port sync" and "sudo port upgrade outdated" and  
letting MacPorts take care of everything.


> I believe this highlights some error in the 1.70 base.  I say this  
> because it seems to be faulty UI that allows a user to specify a  
> variant that when in place the port command can be broken in a  
> simple upgrade.

I agree it's a MacPorts base issue. A ticket has now also been filed  
for this issue:

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

In it, I comment:

"Actually it surprises me that MacPorts base is shelling out to an ln  
command at all; why aren't we using the [file link] Tcl command?"

Does anybody know the answer? I haven't yet looked through the  
history of base to see if the commit messages give any indication.


> I mention above "perhaps for no good reason" because last week when  
> I upgraded graphviz which upgraded gd2, I got into a loop of trying  
> to upgrade freetype, zlib and gettext, none of which were outdated  
> according to port.  I finally had to force the reinstallation of  
> zlib and gettext, force uninstall gd2, freetype, zlib, and gettext  
> and start over.

Without seeing exactly what commands you typed and what output you  
got, I can only speculate that perhaps you used the -f flag to port  
upgrade and did not also use the -n flag. This can result in  
dependencies being rebuilt even if they are not outdated -- possibly  
even multiple times. Nobody wants this, so one should never use the - 
f flag with port upgrade without also using the -n flag. However,  
MacPorts should never get in any kind of "loop". It might seem that  
way, but if you let it run all the way through (which might take  
prohibitively long) it would eventually end, so it's not a loop.


> That was not the first time I had seen this loop of upgrading a  
> port that was the same version as the curreny installed version,  
> followed by failing to install the "new" version because a version  
> was already in place (the same version).  In some cases the process  
> stopps there; in others it moves to the next port that it either  
> "thinks" should be upgraded or really should be.  Then if that port  
> depends on one of the ports it has mistakenly identified as  
> outdated, it goes into the same pattern.  On a few occassions I  
> have found libraries from those ports which wer not in need of  
> replacement--but replaced anyway--missing. TimeMachine is useful,  
> then,

If you could provide actual commands typed and verbatim output  
received the next time you encounter this problem, that might be  
helpful to getting it resolved.


> I have the last model of the G5 iMac running 10.5.6, and the  
> portinstalltype is direct, and portarchivemode is no.  1.7 seems as  
> though it has sections that are not sure what "direct" mode is by  
> the way; some ports I have upgraded recently report "activating."   
> I have not used image mode on this machine at all.

Direct mode is certainly less well tested than image mode. I've never  
used it. Is there a particular reason why you are using it?

There are ports that define post-activation phases. Perhaps those are  
getting executed even in direct mode, and that is why you see  
MacPorts stating it is activating a port, even though in direct mode  
there isn't an activation phase...

If you could say exactly what ports do this, we could investigate  
further.



From jmr at macports.org  Fri Jan 23 05:02:33 2009
From: jmr at macports.org (Joshua Root)
Date: Sat, 24 Jan 2009 00:02:33 +1100
Subject: Error after trying to upgrade installed
In-Reply-To: <5E17D0EB-8173-4C41-AD00-2B32BBCD1ECE@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>	<4973BF65.7050700@macports.org>	<20090118235837.GE741@ninagal.withay.com>	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>	<4973D310.1090300@macports.org>	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>	<alpine.OSX.2.00L.0901190811250.80957@teraqry.sevanohynk.bet>
	<5E17D0EB-8173-4C41-AD00-2B32BBCD1ECE@macports.org>
Message-ID: <4979BFE9.6040701@macports.org>

Ryan Schmidt wrote:
> "Actually it surprises me that MacPorts base is shelling out to an ln
> command at all; why aren't we using the [file link] Tcl command?"

What seems even stranger to me is that it's the *de*activate phase
that's failing, which appears to only use 'file delete'.

- Josh

From jmr at macports.org  Fri Jan 23 05:07:31 2009
From: jmr at macports.org (Joshua Root)
Date: Sat, 24 Jan 2009 00:07:31 +1100
Subject: Universal Binaries
In-Reply-To: <E813CC9E-16CE-48EE-A9AF-048A8E0CD892@rochester.rr.com>
References: <4246E330-FE64-4D04-B92E-311E1539A067@rochester.rr.com>	<BD87B8D4-4D7A-40C7-8E89-2BA9457C60C6@macports.org>	<9AE775F7-9732-4D08-A4FA-460D7FC39D21@rochester.rr.com>
	<520500B5-1A35-4BFF-A3CF-A5F1DB1B42ED@macports.org>
	<497982DF.70407@macports.org>
	<E813CC9E-16CE-48EE-A9AF-048A8E0CD892@rochester.rr.com>
Message-ID: <4979C113.80700@macports.org>

Timothy Lee wrote:
> Hey Joshua-
> 
> Thanks for the reply.
> Do you know if its possible for me (on leopard) to build x86 code (all
> my macports ports) that will also run on Tiger?
> Short of physical access to an intel 10.4 install, is there anything I
> can do?

Don't forget to use Reply All so the discussion goes to the list as
well. There are no guarantees that this will work, but the way to do
what you want would be to set universal_target to 10.4,
universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and
universal_archs to i386. Then build everything with +universal (best to
add it to your variants.conf).

- Josh

From apple at frinabulax.org  Fri Jan 23 05:35:44 2009
From: apple at frinabulax.org (robert delius royar)
Date: Fri, 23 Jan 2009 08:35:44 -0500
Subject: Error after trying to upgrade installed
In-Reply-To: <5E17D0EB-8173-4C41-AD00-2B32BBCD1ECE@macports.org>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<alpine.OSX.2.00L.0901190811250.80957@teraqry.sevanohynk.bet>
	<5E17D0EB-8173-4C41-AD00-2B32BBCD1ECE@macports.org>
Message-ID: <alpine.OSX.2.00L.0901230810020.31248@teraqry.sevanohynk.bet>

Fri, 23 Jan 2009 (06:27 -0600 UTC) Ryan Schmidt wrote:

> On Jan 19, 2009, at 07:37, robert delius royar wrote:
>
>> So much traffic on this thread, so much time spent answering questions. But 
>> I do not recall any of the answerers trying
>> port provides /opt/local/lib/libintl.dylib
>
> Sorry; I thought it was already understood that libintl is the 
> internationalization library and that it is provided by gettext.

My original post was strident; it should not have been.
[...]
> I agree it's a MacPorts base issue. A ticket has now also been filed for this 
> issue:
>
> http://trac.macports.org/ticket/18149

Thanks

>> I have the last model of the G5 iMac running 10.5.6, and the 
>> portinstalltype is direct, and portarchivemode is no.  1.7 seems as though 
>> it has sections that are not sure what "direct" mode is by the way; some 
>> ports I have upgraded recently report "activating."  I have not used image 
>> mode on this machine at all.
>
> Direct mode is certainly less well tested than image mode. I've never used 
> it. Is there a particular reason why you are using it?

I began using Darwinports very soon after DP was created.  When Image 
mode was added, a few of us (perhaps under Panther but could have been 
Tiger) noticed significant (and documentable) slow downs on access to 
files in /opt/local/bin.  After a conversation on the old DP mailing 
list, we found that hard links were problematic for the OS (at least in 
that version) when they exceded some level.

I recall that an Apple employee stated that this was a known problem. 
After switching from my old G4 to this G5 and reinstalling MP, I kept 
the direct mode partly because it works just fine and I do not usually 
need to worry about which port is active.  I only have 518 ports 
installed on this computer.  On the earlier machine I had more of the 
X11 system in DP/MP.  But now that Apple has a real active developer 
working on porting X, all my X stuff (except gimp) is outside MP's 
system.

> There are ports that define post-activation phases. Perhaps those are getting 
> executed even in direct mode, and that is why you see MacPorts stating it is 
> activating a port, even though in direct mode there isn't an activation 
> phase...
>
> If you could say exactly what ports do this, we could investigate further.

I will make sure to do this the next time I see the problem.  I can 
usually work around it because of so many years using MP, so I just move 
forward.

-- 
Dr. Robert Delius Royar                   Associate Professor of English
Morehead State University                             Morehead, Kentucky


From choffman at eclimb.net  Fri Jan 23 05:54:30 2009
From: choffman at eclimb.net (Craig Hoffman)
Date: Fri, 23 Jan 2009 06:54:30 -0700
Subject: Problems using PHP and CURL
Message-ID: <B06456ED-A3F4-48EF-B121-AA747F4EBE71@eclimb.net>

Ok, here it goes.  I'll try to explain this the best I can.  A few  
days ago I started using MacPorts to replace Marc Lynage's  PHP  
package.  Everything installed and worked without a hitch (PHP,  
Apache2, MySQL, CURL, Etc...).  Yesterday, while working on a PHP CURL  
script, I noticed CURL is not  sending or receiving the request.  The  
script works fine on our production server and when I'm running Marc  
Lynage's  PHP package (5.2.5) / Apple's stock Apache version.    
MacPort PHP Info file (5.2.8)  tells me CURL is installed.   I've also  
compared both PHP INI files (Lynage's and MacPorts) and their  
identical.   I'm stumped on why it works on one but not the other.   
Could it be something with Apache2?

Does anyone have any ideas what's going on?

Here's what's installed with CURL
curl 7.19.3 (i386-apple-darwin9.6.0) libcurl/7.19.3 OpenSSL/0.9.8j
zlib/1.2.3
Protocols: tftp ftp telnet dict ldap http file https ftps
Features: IPv6 Largefile NTLM SSL libz
_______________________
Craig Hoffman
iChat / AIM: mountain.dog
_______________________






From hvdwolf at gmail.com  Fri Jan 23 06:14:34 2009
From: hvdwolf at gmail.com (Harry van der Wolf)
Date: Fri, 23 Jan 2009 15:14:34 +0100
Subject: Universal Binaries
In-Reply-To: <4979C113.80700@macports.org>
References: <4246E330-FE64-4D04-B92E-311E1539A067@rochester.rr.com>
	<BD87B8D4-4D7A-40C7-8E89-2BA9457C60C6@macports.org>
	<9AE775F7-9732-4D08-A4FA-460D7FC39D21@rochester.rr.com>
	<520500B5-1A35-4BFF-A3CF-A5F1DB1B42ED@macports.org>
	<497982DF.70407@macports.org>
	<E813CC9E-16CE-48EE-A9AF-048A8E0CD892@rochester.rr.com>
	<4979C113.80700@macports.org>
Message-ID: <8c242c590901230614u4ff808a1h449066d25522cf20@mail.gmail.com>

Hi,

I've setup my MacPorts 1.7 to always build universal (does not always work
and sometimes needs a manual change of the Portfile).
To do this I configured in the "macports.conf" the following:

# Options for Universal Binaries (+universal variant)

# MACOSX_DEPLOYMENT_TARGET
universal_target        10.4

# the SDK "sysroot" to use
universal_sysroot       /Developer/SDKs/MacOSX10.4u.sdk

# machine architectures
universal_archs         ppc i386

and in variants.conf:

+universal

Harry

2009/1/23 Joshua Root <jmr at macports.org>

> Timothy Lee wrote:
> > Hey Joshua-
> >
> > Thanks for the reply.
> > Do you know if its possible for me (on leopard) to build x86 code (all
> > my macports ports) that will also run on Tiger?
> > Short of physical access to an intel 10.4 install, is there anything I
> > can do?
>
> Don't forget to use Reply All so the discussion goes to the list as
> well. There are no guarantees that this will work, but the way to do
> what you want would be to set universal_target to 10.4,
> universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and
> universal_archs to i386. Then build everything with +universal (best to
> add it to your variants.conf).
>
> - Josh
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090123/58aea1ed/attachment.html>

From dluke at geeklair.net  Fri Jan 23 06:24:53 2009
From: dluke at geeklair.net (Daniel J. Luke)
Date: Fri, 23 Jan 2009 09:24:53 -0500
Subject: p5 modules, get me started on one
In-Reply-To: <7F0DB44D-3E96-40D4-A0FA-61861D5586AA@newgeo.com>
References: <20090120025055.GN785@ninagal.withay.com>
	<E2AEF0BD-5047-4347-81EE-17756C640C77@newgeo.com>
	<20090120055648.GI1155@darkart.com>
	<7DFBAACC-977D-464E-8E96-6A04BD2E43D2@newgeo.com>
	<8674C8B7-ED1B-4308-9B55-4920BA23168A@newgeo.com>
	<20090120073247.GR785@ninagal.withay.com>
	<82DC9333-19F8-4455-A439-A7933A37B264@newgeo.com>
	<16926AEC-7084-4517-8338-B99FE9C35B41@newgeo.com>
	<20090121010109.GL965@ninagal.withay.com>
	<2AD35050-C46E-40C7-B993-4819F3F0CEE6@newgeo.com>
	<20090121094010.GU965@ninagal.withay.com>
	<2778265B-1293-4ED9-84AF-01E933702F7A@newgeo.com>
	<4A02763E-F01B-4264-AC4A-123A2200DEDD@macports.org>
	<7F0DB44D-3E96-40D4-A0FA-61861D5586AA@newgeo.com>
Message-ID: <9E1D2FB4-6171-4491-BC4A-20BDE122E6F5@geeklair.net>

On Jan 23, 2009, at 3:31 AM, Scott Haneda wrote:
> And I think I am a good case in which that sort of failed me. I  
> needed Net::SMTP, but to me, as a user, it was not there.  I tried  
> port list p5-net-smtp, and nothing.

There are generally two kinds of users who need a specific perl module:

1 - The vast majority will need it as a dependency for something else  
(and they don't really care about that module as long as whatever they  
are trying to install works).

2 - People who plan on writing scripts or doing something else outside  
of MacPorts that require that module.

Looks like you were in group #2? Most of the time, I would think that  
someone who wanted a specific perl module would either know (or find  
it trivial to discover) that it was part of a 'larger' package of  
modules.

> I sort of like the idea of a port file being a pointer to download  
> some other package that contains the parent modules, unless someone  
> tells me it is a really bad idea.


It's not necessarily a bad idea, it's just a lot of work for the  
maintainer (since each module would require a portfile that points  
back to the parent package).

Not that it excuses the MacPorts behavior, but I don't think the other  
package managers do this.

I think making the ports you want show up more easily when doing port  
search would be an easier way to approach fixing this.
--
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/20090123/dab37c6d/attachment.bin>

From dluke at geeklair.net  Fri Jan 23 06:34:09 2009
From: dluke at geeklair.net (Daniel J. Luke)
Date: Fri, 23 Jan 2009 09:34:09 -0500
Subject: Error after trying to upgrade installed
In-Reply-To: <alpine.OSX.2.00L.0901230810020.31248@teraqry.sevanohynk.bet>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<alpine.OSX.2.00L.0901190811250.80957@teraqry.sevanohynk.bet>
	<5E17D0EB-8173-4C41-AD00-2B32BBCD1ECE@macports.org>
	<alpine.OSX.2.00L.0901230810020.31248@teraqry.sevanohynk.bet>
Message-ID: <DCEC1198-033D-4CB4-87D6-F9ACDDF6F75C@geeklair.net>

On Jan 23, 2009, at 8:35 AM, robert delius royar wrote:
>> Direct mode is certainly less well tested than image mode. I've  
>> never used it. Is there a particular reason why you are using it?
>
> I began using Darwinports very soon after DP was created.  When  
> Image mode was added, a few of us (perhaps under Panther but could  
> have been Tiger) noticed significant (and documentable) slow downs  
> on access to files in /opt/local/bin.  After a conversation on the  
> old DP mailing list, we found that hard links were problematic for  
> the OS (at least in that version) when they exceded some level.

For the list archives, this was fixed (in 10.4, IIRC).

As for your upgrade loop, I think you're experiencing bug #17762 (http://trac.macports.org/ticket/17762 
)

I haven't had time to investigate (and wasn't running trunk on my  
direct mode machine so I missed the change that caused 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/20090123/fcb9b028/attachment.bin>

From timlee at rochester.rr.com  Fri Jan 23 07:11:19 2009
From: timlee at rochester.rr.com (timlee at rochester.rr.com)
Date: Fri, 23 Jan 2009 10:11:19 -0500
Subject: Universal Binaries
In-Reply-To: <4979C113.80700@macports.org>
Message-ID: <20090123151119.20XKE.180435.root@hrndva-web27-z02>

Thanks for the tip!
Has anyone tried this? Success/failure stories?



---- Joshua Root <jmr at macports.org> wrote: 
> Timothy Lee wrote:
> > Hey Joshua-
> > 
> > Thanks for the reply.
> > Do you know if its possible for me (on leopard) to build x86 code (all
> > my macports ports) that will also run on Tiger?
> > Short of physical access to an intel 10.4 install, is there anything I
> > can do?
> 
> Don't forget to use Reply All so the discussion goes to the list as
> well. There are no guarantees that this will work, but the way to do
> what you want would be to set universal_target to 10.4,
> universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and
> universal_archs to i386. Then build everything with +universal (best to
> add it to your variants.conf).
> 
> - Josh


From choffman at eclimb.net  Fri Jan 23 07:57:58 2009
From: choffman at eclimb.net (Craig Hoffman)
Date: Fri, 23 Jan 2009 08:57:58 -0700
Subject: Problems using PHP and CURL
In-Reply-To: <6BA6AD39-BDEA-40AC-AB38-22A84247E27F@centosprime.com>
References: <B06456ED-A3F4-48EF-B121-AA747F4EBE71@eclimb.net>
	<6BA6AD39-BDEA-40AC-AB38-22A84247E27F@centosprime.com>
Message-ID: <F5D6D011-BE32-4E66-984C-6B63C7527E6E@eclimb.net>

Hi Chris -
Thanks for responding.  I pasted a code snippet below.  Basically it  
sends an array to Authorize.Net for processing.   Authorize.Net  
responds with transaction details (approved, declined, wrong address,  
etc...).
When CURL is working, using Liyanage PHP I get this response:

Sent:
Array ( [x_login] => 6zz6m5N4Et [x_test_request] => TRUE [x_tran_key]  
=> 9V9wUv6Yd92t27t5 [x_delim_char] => | [x_delim_data] => TRUE  
[x_encap_char] => [x_amount] => [x_method] => CC [x_type] =>  
AUTH_CAPTURE [x_card_num] => [x_card_code] => [x_exp_date] =>  
[x_first_name] => [x_last_name] => [x_address] => [x_company] =>  
[x_city] => [x_state] => [x_zip] => [x_country] => [x_phone] =>  
[x_customer_ip] => ::1 [x_description] => [x_invoice_num] => )

Received:
Array ( [0] => 3 [1] => 2 [2] => 33 [3] => (TESTMODE) Credit card  
number is required. ....

Using MacPorts PHP (5.2.8) - I do not get any response from CURL.  The  
received array comes returns empty.

Array ([0]=>)

Any thoughts?  Something with the configuration?

Code Snippet:
	public function processTransaction() {
		$this->transaction = array(
		"x_login"        => "$this->login",		// no x_version
		"x_test_request" => "$this->test_mode",
		"x_tran_key"     => "$this->transactionkey",
		"x_delim_char"   => "$this->delim_char",
		"x_delim_data"   => "$this->delim_data",
		"x_encap_char"   => "$this->encaps_char",			
		"x_amount"       => "$this->amount",
		"x_method"       => "$this->ccecheck",
		"x_type"         => "$this->trans_type",
		"x_card_num"     => "$this->cc_number",
		"x_card_code"    => "$this->ccv_num",
		"x_exp_date"     => "$this->exp_date",
		"x_card_code"    => "$this->ccv_num",
		"x_first_name"   => "$this->billing_first_name",
		"x_last_name"    => "$this->billing_last_name",
		"x_address"      => "$this->billing_address",
		"x_company"      => "$this->billing_company",
		"x_city"         => "$this->billing_city",
		"x_state"        => "$this->billing_state",
		"x_zip"          => "$this->billing_zip",
		"x_country"      => "$this->billing_country",
		"x_phone"        => "$this->billing_phone",
		"x_customer_ip"  => "$this->customer_ip",
		"x_description"  => "$this->billing_desc",
		"x_invoice_num"  => "$this->invoice");
	
	   //Print transaction array out for debugging
	   print_r($this->transaction);
	   		
		$data = "";
		reset($this->transaction);
		while (list ($key, $val) = each($this->transaction)) {
			$data .= $key . "=" . urlencode($val) . "&";
		}
		
		$data = preg_replace("/&$/", '', $data); // strip the trailing &
		$AuthNetConn = curl_init();
		curl_setopt($AuthNetConn, CURLOPT_URL, $this->auth_url);
		curl_setopt($AuthNetConn, CURLOPT_POST, 1);
		curl_setopt($AuthNetConn, CURLOPT_POSTFIELDS, $data);
		curl_setopt($AuthNetConn, CURLOPT_RETURNTRANSFER, 1);
		$this->response = curl_exec($AuthNetConn);
		$this->AuthResponse = explode($this->delim_char, $this->response);
		curl_close($AuthNetConn);
	}
_______________________
Craig Hoffman
iChat / AIM: mountain.dog
_______________________





On Jan 23, 2009, at 8:40 AM, Chris Janton wrote:

> On 2009-01-23 , at 06:54 , Craig Hoffman wrote:
>
>> Ok, here it goes.  I'll try to explain this the best I can.  A few  
>> days ago I started using MacPorts to replace Marc Lynage's  PHP  
>> package.  Everything installed and worked without a hitch (PHP,  
>> Apache2, MySQL, CURL, Etc...).  Yesterday, while working on a PHP  
>> CURL script, I noticed CURL is not  sending or receiving the  
>> request.  The script works fine on our production server and when  
>> I'm running Marc Lynage's  PHP package (5.2.5) / Apple's stock  
>> Apache version.   MacPort PHP Info file (5.2.8)  tells me CURL is  
>> installed.   I've also compared both PHP INI files (Lynage's and  
>> MacPorts) and their identical.   I'm stumped on why it works on one  
>> but not the other.  Could it be something with Apache2?
>>
>> Does anyone have any ideas what's going on?
>
>
> I replaced the Liyanage PHP long time ago - do you have an example  
> script (PHP, simple) that demonstrates the problem?
>
> 8)
> ----------------------------------
> Chris Janton  - face at CentosPrime dot COM
> Netminder for Opus1.COM
>
>


From face at CentosPrime.COM  Fri Jan 23 08:23:40 2009
From: face at CentosPrime.COM (Chris Janton)
Date: Fri, 23 Jan 2009 09:23:40 -0700
Subject: Problems using PHP and CURL
In-Reply-To: <F5D6D011-BE32-4E66-984C-6B63C7527E6E@eclimb.net>
References: <B06456ED-A3F4-48EF-B121-AA747F4EBE71@eclimb.net>
	<6BA6AD39-BDEA-40AC-AB38-22A84247E27F@centosprime.com>
	<F5D6D011-BE32-4E66-984C-6B63C7527E6E@eclimb.net>
Message-ID: <E26BA86F-D32F-4822-B595-2D3BC25EC17D@CentosPrime.COM>

On 2009-01-23 , at 08:57 , Craig Hoffman wrote:

> Thanks for responding.  I pasted a code snippet below.  Basically it  
> sends an array to Authorize.Net for processing.   Authorize.Net  
> responds with transaction details (approved, declined, wrong  
> address, etc...).
> When CURL is working, using Liyanage PHP I get this response:


what does the following PHP example do? In theory it will return the  
text of the web page which reads like this
"
You have reached this web page by typing "example.com", "example.net",  
or "example.org" into your web browser.
These domain names are reserved for use in documentation and are not  
available for registration. See RFC 2606, Section 3.

"


<?php
  $ch = curl_init();
  curl_setopt($ch, CURLOPT_URL, 'example.com');
  curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
  $output = curl_exec($ch);
  curl_close($ch);
  echo $output;
?>

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



From choffman at eclimb.net  Fri Jan 23 08:36:29 2009
From: choffman at eclimb.net (Craig Hoffman)
Date: Fri, 23 Jan 2009 09:36:29 -0700
Subject: Problems using PHP and CURL
In-Reply-To: <E26BA86F-D32F-4822-B595-2D3BC25EC17D@CentosPrime.COM>
References: <B06456ED-A3F4-48EF-B121-AA747F4EBE71@eclimb.net>
	<6BA6AD39-BDEA-40AC-AB38-22A84247E27F@centosprime.com>
	<F5D6D011-BE32-4E66-984C-6B63C7527E6E@eclimb.net>
	<E26BA86F-D32F-4822-B595-2D3BC25EC17D@CentosPrime.COM>
Message-ID: <CABC8568-6A75-4111-ABB5-A64B2E69F397@eclimb.net>

> what does the following PHP example do?  I get this:
You have reached this web page by typing "example.com", "example.net",  
or "example.org" into your web browser.
These domain names are reserved for use in documentation and are not  
available for registration. See RFC 2606, Section 3.

Ok, I guess CURL is working. Excellent.  I wonder why my script  
doesn't work with MacPorts PHP...

_______________________
Craig Hoffman
iChat / AIM: mountain.dog
_______________________





On Jan 23, 2009, at 9:23 AM, Chris Janton wrote:

> On 2009-01-23 , at 08:57 , Craig Hoffman wrote:
>
>> Thanks for responding.  I pasted a code snippet below.  Basically  
>> it sends an array to Authorize.Net for processing.   Authorize.Net  
>> responds with transaction details (approved, declined, wrong  
>> address, etc...).
>> When CURL is working, using Liyanage PHP I get this response:
>
>
> what does the following PHP example do? In theory it will return the  
> text of the web page which reads like this
> "
> You have reached this web page by typing "example.com",  
> "example.net", or "example.org" into your web browser.
> These domain names are reserved for use in documentation and are not  
> available for registration. See RFC 2606, Section 3.
>
> "
>
>
> <?php
> $ch = curl_init();
> curl_setopt($ch, CURLOPT_URL, 'example.com');
> curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
> $output = curl_exec($ch);
> curl_close($ch);
> echo $output;
> ?>
>
> 8)
> ----------------------------------
> Chris Janton  - face at CentosPrime dot COM
> Netminder for Opus1.COM
>
>


From mudiam at gmail.com  Fri Jan 23 09:07:13 2009
From: mudiam at gmail.com (Kiran Mudiam)
Date: Fri, 23 Jan 2009 10:07:13 -0700
Subject: Scribe From Facebook
Message-ID: <33a9e7ca0901230907x319190c2leaaf524e225768fd@mail.gmail.com>

Has any one had success with compiling Scribe for Mac OS X.

I wish there was a macport for this. How does one go about doing this.

I got the sources and tried compiling and have some dependecy errors.
I have installed all the preeqs like libevent, thrift, boost and fb303 etc.

----

/usr/bin/ar cru libscribe.a scribe.o scribe_types.o scribe_constants.o
ranlib libscribe.a
g++ -DPACKAGE_NAME=\"scribe\" -DPACKAGE_TARNAME=\"scribe\"
-DPACKAGE_VERSION=\"1.5.0\" -DPACKAGE_STRING=\"scribe\ 1.5.0\"
-DPACKAGE_BUGREPORT=\"\" -DHAVE_BOOST= -DHAVE_BOOST_SYSTEM=
-DHAVE_BOOST_FILESYSTEM= -I.  -I.. -I/usr/local/include/thrift
-I/usr/local/include/thrift/fb303 -I/usr/local/include/boost-1_37     -Wall
-O3 -MT store.o -MD -MP -MF .deps/store.Tpo -c -o store.o store.cpp
In file included from common.h:49,
                 from store.cpp:25:
/usr/local/include/thrift/server/TNonblockingServer.h:18:19: error: event.h:
No such file or directory
/usr/local/include/thrift/server/TNonblockingServer.h:59: error: expected
';' before '*' token
/usr/local/include/thrift/server/TNonblockingServer.h:62: error: field
'serverEvent_' has incomplete type
/usr/local/include/thrift/server/TNonblockingServer.h:143: error: expected
';' before '*' token
/usr/local/include/thrift/server/TNonblockingServer.h:147: error: expected
`;' before 'void'
/usr/local/include/thrift/server/TNonblockingServer.h:175: error:
'event_base' has not been declared

--------


Looks like I have issues with finind the event.h files

Has anyone compiled it for OS X?

thanks,
kiran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20090123/e1f84cca/attachment.html>

From choffman at eclimb.net  Fri Jan 23 09:19:06 2009
From: choffman at eclimb.net (Craig Hoffman)
Date: Fri, 23 Jan 2009 10:19:06 -0700
Subject: Problems using PHP and CURL
In-Reply-To: <CABC8568-6A75-4111-ABB5-A64B2E69F397@eclimb.net>
References: <B06456ED-A3F4-48EF-B121-AA747F4EBE71@eclimb.net>
	<6BA6AD39-BDEA-40AC-AB38-22A84247E27F@centosprime.com>
	<F5D6D011-BE32-4E66-984C-6B63C7527E6E@eclimb.net>
	<E26BA86F-D32F-4822-B595-2D3BC25EC17D@CentosPrime.COM>
	<CABC8568-6A75-4111-ABB5-A64B2E69F397@eclimb.net>
Message-ID: <07C5C685-72A2-4AAD-91CD-9892E341760F@eclimb.net>

Ok this strange -
When I put this URL (https://test.authorize.net/gateway/transact.dll)  
in your CURL example, you get this response:
The following errors have occurred.
(13) The merchant login ID or password is invalid or the account is  
inactive.

But when running MacPorts PHP it returns blank.  This example returns  
the correct response with Marc's PHP package (5.2.5).
Could this be perhaps an Apache thing?

	<?php
		$ch = curl_init();
		curl_setopt($ch, CURLOPT_URL, "https://test.authorize.net/gateway/transact.dll 
");
		curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
		$response = curl_exec($ch);
		
		curl_close($ch);
		echo $response;	
	?>
_______________________
Craig Hoffman
iChat / AIM: mountain.dog
_______________________





On Jan 23, 2009, at 9:36 AM, Craig Hoffman wrote:

>> what does the following PHP example do?  I get this:
> You have reached this web page by typing "example.com",  
> "example.net", or "example.org" into your web browser.
> These domain names are reserved for use in documentation and are not  
> available for registration. See RFC 2606, Section 3.
>
> Ok, I guess CURL is working. Excellent.  I wonder why my script  
> doesn't work with MacPorts PHP...
>
> _______________________
> Craig Hoffman
> iChat / AIM: mountain.dog
> _______________________
>
>
>
>
>
> On Jan 23, 2009, at 9:23 AM, Chris Janton wrote:
>
>> On 2009-01-23 , at 08:57 , Craig Hoffman wrote:
>>
>>> Thanks for responding.  I pasted a code snippet below.  Basically  
>>> it sends an array to Authorize.Net for processing.   Authorize.Net  
>>> responds with transaction details (approved, declined, wrong  
>>> address, etc...).
>>> When CURL is working, using Liyanage PHP I get this response:
>>
>>
>> what does the following PHP example do? In theory it will return  
>> the text of the web page which reads like this
>> "
>> You have reached this web page by typing "example.com",  
>> "example.net", or "example.org" into your web browser.
>> These domain names are reserved for use in documentation and are  
>> not available for registration. See RFC 2606, Section 3.
>>
>> "
>>
>>
>> <?php
>> $ch = curl_init();
>> curl_setopt($ch, CURLOPT_URL, 'example.com');
>> curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
>> $output = curl_exec($ch);
>> curl_close($ch);
>> echo $output;
>> ?>
>>
>> 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 hvdwolf at gmail.com  Fri Jan 23 09:51:04 2009
From: hvdwolf at gmail.com (Harry van der Wolf)
Date: Fri, 23 Jan 2009 18:51:04 +0100
Subject: Problems using PHP and CURL
In-Reply-To: <07C5C685-72A2-4AAD-91CD-9892E341760F@eclimb.net>
References: <B06456ED-A3F4-48EF-B121-AA747F4EBE71@eclimb.net>
	<6BA6AD39-BDEA-40AC-AB38-22A84247E27F@centosprime.com>
	<F5D6D011-BE32-4E66-984C-6B63C7527E6E@eclimb.net>
	<E26BA86F-D32F-4822-B595-2D3BC25EC17D@CentosPrime.COM>
	<CABC8568-6A75-4111-ABB5-A64B2E69F397@eclimb.net>
	<07C5C685-72A2-4AAD-91CD-9892E341760F@eclimb.net>
Message-ID: <8c242c590901230951h7d4cbe6fy76b080e998014ba3@mail.gmail.com>

Please check which curl version is used. curl is part of MacOsx and resides
in /usr/bin/curl. Macports curl is in /opt/local/bin. If I compare them I
see that they are not equally compiled with equal dependencies on my system
(10.5.6).  Normally when macports is installed it places /opt/local/bin as
first search path in your PATH. Your previous install might have used the
/usr/bin/curl wheras your macports install uses /opt/local/bin/curl.
You could try to systematically rename them (or do a sudo port deactivate
curl) and check if the "standard"  macosx curl gives you a different
message/error.

Harry



2009/1/23 Craig Hoffman <choffman at eclimb.net>

> Ok this strange -
> When I put this URL (https://test.authorize.net/gateway/transact.dll) in
> your CURL example, you get this response:
> The following errors have occurred.
> (13) The merchant login ID or password is invalid or the account is
> inactive.
>
> But when running MacPorts PHP it returns blank.  This example returns the
> correct response with Marc's PHP package (5.2.5).
> Could this be perhaps an Apache thing?
>
>        <?php
>                $ch = curl_init();
>                curl_setopt($ch, CURLOPT_URL, "
> https://test.authorize.net/gateway/transact.dll");
>                curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
>                $response = curl_exec($ch);
>
>                curl_close($ch);
>                echo $response;
>        ?>
> _______________________
> Craig Hoffman
> iChat / AIM: mountain.dog
> _______________________
>
>
>
>
>
> On Jan 23, 2009, at 9:36 AM, Craig Hoffman wrote:
>
>  what does the following PHP example do?  I get this:
>>>
>> You have reached this web page by typing "example.com", "example.net", or
>> "example.org" into your web browser.
>> These domain names are reserved for use in documentation and are not
>> available for registration. See RFC 2606, Section 3.
>>
>> Ok, I guess CURL is working. Excellent.  I wonder why my script doesn't
>> work with MacPorts PHP...
>>
>> _______________________
>> Craig Hoffman
>> iChat / AIM: mountain.dog
>> _______________________
>>
>>
>>
>>
>>
>> On Jan 23, 2009, at 9:23 AM, Chris Janton wrote:
>>
>>  On 2009-01-23 , at 08:57 , Craig Hoffman wrote:
>>>
>>>  Thanks for responding.  I pasted a code snippet below.  Basically it
>>>> sends an array to Authorize.Net for processing.   Authorize.Net responds
>>>> with transaction details (approved, declined, wrong address, etc...).
>>>> When CURL is working, using Liyanage PHP I get this response:
>>>>
>>>
>>>
>>> what does the following PHP example do? In theory it will return the text
>>> of the web page which reads like this
>>> "
>>> You have reached this web page by typing "example.com", "example.net",
>>> or "example.org" into your web browser.
>>> These domain names are reserved for use in documentation and are not
>>> available for registration. See RFC 2606, Section 3.
>>>
>>> "
>>>
>>>
>>> <?php
>>> $ch = curl_init();
>>> curl_setopt($ch, CURLOPT_URL, 'example.com');
>>> curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
>>> $output = curl_exec($ch);
>>> curl_close($ch);
>>> echo $output;
>>> ?>
>>>
>>> 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
>>
>
> _______________________________________________
> 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/20090123/fbeefe97/attachment.html>

From choffman at eclimb.net  Fri Jan 23 10:10:44 2009
From: choffman at eclimb.net (Craig Hoffman)
Date: Fri, 23 Jan 2009 11:10:44 -0700
Subject: Problems using PHP and CURL
In-Reply-To: <8c242c590901230951h7d4cbe6fy76b080e998014ba3@mail.gmail.com>
References: <B06456ED-A3F4-48EF-B121-AA747F4EBE71@eclimb.net>
	<6BA6AD39-BDEA-40AC-AB38-22A84247E27F@centosprime.com>
	<F5D6D011-BE32-4E66-984C-6B63C7527E6E@eclimb.net>
	<E26BA86F-D32F-4822-B595-2D3BC25EC17D@CentosPrime.COM>
	<CABC8568-6A75-4111-ABB5-A64B2E69F397@eclimb.net>
	<07C5C685-72A2-4AAD-91CD-9892E341760F@eclimb.net>
	<8c242c590901230951h7d4cbe6fy76b080e998014ba3@mail.gmail.com>
Message-ID: <DE2DA459-392B-4141-9164-962BA66F27E5@eclimb.net>

> Please check which curl version is used. curl is part of MacOsx and  
> resides in /usr/bin/curl.

capital:~ xxxx $ /opt/local/bin/curl -V
curl 7.19.3 (i386-apple-darwin9.6.0) libcurl/7.19.3 OpenSSL/0.9.8j  
zlib/1.2.3
Protocols: tftp ftp telnet dict ldap http file https ftps
Features: IPv6 Largefile NTLM SSL libz

> You could try to systematically rename them (or do a sudo port  
> deactivate curl) and check if the "standard"  macosx curl gives you  
> a different message/error.
Ok, I'll give that a try.
_______________________
Craig Hoffman
iChat / AIM: mountain.dog
_______________________





On Jan 23, 2009, at 10:51 AM, Harry van der Wolf wrote:

> Please check which curl version is used. curl is part of MacOsx and  
> resides in /usr/bin/curl. Macports curl is in /opt/local/bin. If I  
> compare them I see that they are not equally compiled with equal  
> dependencies on my system (10.5.6).  Normally when macports is  
> installed it places /opt/local/bin as first search path in your  
> PATH. Your previous install might have used the /usr/bin/curl wheras  
> your macports install uses /opt/local/bin/curl.
> You could try to systematically rename them (or do a sudo port  
> deactivate curl) and check if the "standard"  macosx curl gives you  
> a different message/error.
>
> Harry
>
>
>
> 2009/1/23 Craig Hoffman <choffman at eclimb.net>
> Ok this strange -
> When I put this URL (https://test.authorize.net/gateway/ 
> transact.dll) in your CURL example, you get this response:
> The following errors have occurred.
> (13) The merchant login ID or password is invalid or the account is  
> inactive.
>
> But when running MacPorts PHP it returns blank.  This example  
> returns the correct response with Marc's PHP package (5.2.5).
> Could this be perhaps an Apache thing?
>
>        <?php
>                $ch = curl_init();
>                curl_setopt($ch, CURLOPT_URL, "https://test.authorize.net/gateway/transact.dll 
> ");
>
>                curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
>                $response = curl_exec($ch);
>
>                curl_close($ch);
>                echo $response;
>        ?>
>
> _______________________
> Craig Hoffman
> iChat / AIM: mountain.dog
> _______________________
>
>
>
>
>
> On Jan 23, 2009, at 9:36 AM, Craig Hoffman wrote:
>
> what does the following PHP example do?  I get this:
> You have reached this web page by typing "example.com",  
> "example.net", or "example.org" into your web browser.
> These domain names are reserved for use in documentation and are not  
> available for registration. See RFC 2606, Section 3.
>
> Ok, I guess CURL is working. Excellent.  I wonder why my script  
> doesn't work with MacPorts PHP...
>
> _______________________
> Craig Hoffman
> iChat / AIM: mountain.dog
> _______________________
>
>
>
>
>
> On Jan 23, 2009, at 9:23 AM, Chris Janton wrote:
>
> On 2009-01-23 , at 08:57 , Craig Hoffman wrote:
>
> Thanks for responding.  I pasted a code snippet below.  Basically it  
> sends an array to Authorize.Net for processing.   Authorize.Net  
> responds with transaction details (approved, declined, wrong  
> address, etc...).
> When CURL is working, using Liyanage PHP I get this response:
>
>
> what does the following PHP example do? In theory it will return the  
> text of the web page which reads like this
> "
> You have reached this web page by typing "example.com",  
> "example.net", or "example.org" into your web browser.
> These domain names are reserved for use in documentation and are not  
> available for registration. See RFC 2606, Section 3.
>
> "
>
>
> <?php
> $ch = curl_init();
> curl_setopt($ch, CURLOPT_URL, 'example.com');
> curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
> $output = curl_exec($ch);
> curl_close($ch);
> echo $output;
> ?>
>
> 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
>
> _______________________________________________
> 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/20090123/0932a342/attachment.html>

From rswwalker at gmail.com  Fri Jan 23 10:38:21 2009
From: rswwalker at gmail.com (Ross Walker)
Date: Fri, 23 Jan 2009 13:38:21 -0500
Subject: Scribe From Facebook
In-Reply-To: <33a9e7ca0901230907x319190c2leaaf524e225768fd@mail.gmail.com>
References: <33a9e7ca0901230907x319190c2leaaf524e225768fd@mail.gmail.com>
Message-ID: <53c900fd0901231038o606f24b5g716355cc3a25909@mail.gmail.com>

On Fri, Jan 23, 2009 at 12:07 PM, Kiran Mudiam <mudiam at gmail.com> wrote:
> Has any one had success with compiling Scribe for Mac OS X.
>
> I wish there was a macport for this. How does one go about doing this.
>
> I got the sources and tried compiling and have some dependecy errors.
> I have installed all the preeqs like libevent, thrift, boost and fb303 etc.
>
> ----
>
> /usr/bin/ar cru libscribe.a scribe.o scribe_types.o scribe_constants.o
> ranlib libscribe.a
> g++ -DPACKAGE_NAME=\"scribe\" -DPACKAGE_TARNAME=\"scribe\"
> -DPACKAGE_VERSION=\"1.5.0\" -DPACKAGE_STRING=\"scribe\ 1.5.0\"
> -DPACKAGE_BUGREPORT=\"\" -DHAVE_BOOST= -DHAVE_BOOST_SYSTEM=
> -DHAVE_BOOST_FILESYSTEM= -I.  -I.. -I/usr/local/include/thrift
> -I/usr/local/include/thrift/fb303 -I/usr/local/include/boost-1_37     -Wall
> -O3 -MT store.o -MD -MP -MF .deps/store.Tpo -c -o store.o store.cpp
> In file included from common.h:49,
>                  from store.cpp:25:
> /usr/local/include/thrift/server/TNonblockingServer.h:18:19: error: event.h:
> No such file or directory
> /usr/local/include/thrift/server/TNonblockingServer.h:59: error: expected
> ';' before '*' token
> /usr/local/include/thrift/server/TNonblockingServer.h:62: error: field
> 'serverEvent_' has incomplete type
> /usr/local/include/thrift/server/TNonblockingServer.h:143: error: expected
> ';' before '*' token
> /usr/local/include/thrift/server/TNonblockingServer.h:147: error: expected
> `;' before 'void'
> /usr/local/include/thrift/server/TNonblockingServer.h:175: error:
> 'event_base' has not been declared
>
> --------
>
>
> Looks like I have issues with finind the event.h files
>
> Has anyone compiled it for OS X?

Not having looked at the code and guessing you may need to compile and
install libevent or libinotify first?

-Ross

From hvdwolf at gmail.com  Fri Jan 23 10:58:17 2009
From: hvdwolf at gmail.com (Harry van der Wolf)
Date: Fri, 23 Jan 2009 19:58:17 +0100
Subject: Problems using PHP and CURL
In-Reply-To: <DE2DA459-392B-4141-9164-962BA66F27E5@eclimb.net>
References: <B06456ED-A3F4-48EF-B121-AA747F4EBE71@eclimb.net>
	<6BA6AD39-BDEA-40AC-AB38-22A84247E27F@centosprime.com>
	<F5D6D011-BE32-4E66-984C-6B63C7527E6E@eclimb.net>
	<E26BA86F-D32F-4822-B595-2D3BC25EC17D@CentosPrime.COM>
	<CABC8568-6A75-4111-ABB5-A64B2E69F397@eclimb.net>
	<07C5C685-72A2-4AAD-91CD-9892E341760F@eclimb.net>
	<8c242c590901230951h7d4cbe6fy76b080e998014ba3@mail.gmail.com>
	<DE2DA459-392B-4141-9164-962BA66F27E5@eclimb.net>
Message-ID: <8c242c590901231058ra06506bkdb76cd1b0766f4af@mail.gmail.com>

Sorry. Should have mentioned that too.

Macports
/opt/local/bin/curl -V
curl 7.18.2 (i386-apple-darwin9.4.0) libcurl/7.18.2 zlib/1.2.3
Protocols: tftp ftp telnet dict http file
Features: Largefile libz

MacOSX
/usr/bin/curl -V
curl 7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3 OpenSSL/0.9.7l
zlib/1.2.3
Protocols: tftp ftp telnet dict ldap http file https ftps
Features: GSS-Negotiate IPv6 Largefile NTLM SSL libz

Harry


2009/1/23 Craig Hoffman <choffman at eclimb.net>

> Please check which curl version is used. curl is part of MacOsx and resides
> in /usr/bin/curl.
>
> capital:~ xxxx $ /opt/local/bin/curl -V
> curl 7.19.3 (i386-apple-darwin9.6.0) libcurl/7.19.3 OpenSSL/0.9.8j
> zlib/1.2.3
> Protocols: tftp ftp telnet dict ldap http file https ftps
> Features: IPv6 Largefile NTLM SSL libz
>
> You could try to systematically rename them (or do a sudo port deactivate
> curl) and check if the "standard"  macosx curl gives you a different
> message/error.
>
> Ok, I'll give that a try.
> _______________________
> Craig Hoffman
> iChat / AIM: mountain.dog
> _______________________
>
>
>
>
>
> On Jan 23, 2009, at 10:51 AM, Harry van der Wolf wrote:
>
> Please check which curl version is used. curl is part of MacOsx and resides
> in /usr/bin/curl. Macports curl is in /opt/local/bin. If I compare them I
> see that they are not equally compiled with equal dependencies on my system
> (10.5.6).  Normally when macports is installed it places /opt/local/bin as
> first search path in your PATH. Your previous install might have used the
> /usr/bin/curl wheras your macports install uses /opt/local/bin/curl.
> You could try to systematically rename them (or do a sudo port deactivate
> curl) and check if the "standard"  macosx curl gives you a different
> message/error.
>
> Harry
>
>
>
> 2009/1/23 Craig Hoffman <choffman at eclimb.net>
>
>> Ok this strange -
>> When I put this URL (https://test.authorize.net/gateway/transact.dll) in
>> your CURL example, you get this response:
>> The following errors have occurred.
>> (13) The merchant login ID or password is invalid or the account is
>> inactive.
>>
>> But when running MacPorts PHP it returns blank.  This example returns the
>> correct response with Marc's PHP package (5.2.5).
>> Could this be perhaps an Apache thing?
>>
>>        <?php
>>                $ch = curl_init();
>>                curl_setopt($ch, CURLOPT_URL, "
>> https://test.authorize.net/gateway/transact.dll");
>>                curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
>>                $response = curl_exec($ch);
>>
>>                curl_close($ch);
>>                echo $response;
>>        ?>
>> _______________________
>> Craig Hoffman
>> iChat / AIM: mountain.dog
>> _______________________
>>
>>
>>
>>
>>
>> On Jan 23, 2009, at 9:36 AM, Craig Hoffman wrote:
>>
>>  what does the following PHP example do?  I get this:
>>>>
>>> You have reached this web page by typing "example.com", "example.net",
>>> or "example.org" into your web browser.
>>> These domain names are reserved for use in documentation and are not
>>> available for registration. See RFC 2606, Section 3.
>>>
>>> Ok, I guess CURL is working. Excellent.  I wonder why my script doesn't
>>> work with MacPorts PHP...
>>>
>>> _______________________
>>> Craig Hoffman
>>> iChat / AIM: mountain.dog
>>> _______________________
>>>
>>>
>>>
>>>
>>>
>>> On Jan 23, 2009, at 9:23 AM, Chris Janton wrote:
>>>
>>>  On 2009-01-23 , at 08:57 , Craig Hoffman wrote:
>>>>
>>>>  Thanks for responding.  I pasted a code snippet below.  Basically it
>>>>> sends an array to Authorize.Net for processing.   Authorize.Net responds
>>>>> with transaction details (approved, declined, wrong address, etc...).
>>>>> When CURL is working, using Liyanage PHP I get this response:
>>>>>
>>>>
>>>>
>>>> what does the following PHP example do? In theory it will return the
>>>> text of the web page which reads like this
>>>> "
>>>> You have reached this web page by typing "example.com", "example.net",
>>>> or "example.org" into your web browser.
>>>> These domain names are reserved for use in documentation and are not
>>>> available for registration. See RFC 2606, Section 3.
>>>>
>>>> "
>>>>
>>>>
>>>> <?php
>>>> $ch = curl_init();
>>>> curl_setopt($ch, CURLOPT_URL, 'example.com');
>>>> curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
>>>> $output = curl_exec($ch);
>>>> curl_close($ch);
>>>> echo $output;
>>>> ?>
>>>>
>>>> 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
>>>
>>
>> _______________________________________________
>> 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/20090123/d176d66b/attachment.html>

From markd at macports.org  Fri Jan 23 11:22:02 2009
From: markd at macports.org (markd at macports.org)
Date: Fri, 23 Jan 2009 11:22:02 -0800
Subject: Installation problems with Expect
Message-ID: <fc.004c4c58114a5575004c4c58114a5575.114a5830@biola.edu>

>> I am having the same problem, reported all over  the web,  with Macport
>> installation of the program
>> Expect, apparently because of a problem recognizing the current version
>> of Tcl. Does someone
>> have a work-around? Thanks. Joe Goddard
>
>This ticket is (unfortunately) still the current state of things:
><http://trac.macports.org/ticket/13827>

I found a patch for using it with Tcl 8.5 and applied it.  Please do a
selfupdate to get revision 4  of expect and try again.  Note also that OS
X 10.4 and 10.5 have expect v5.42 included in case you weren't aware.

Mark


From markd at macports.org  Fri Jan 23 11:31:58 2009
From: markd at macports.org (markd at macports.org)
Date: Fri, 23 Jan 2009 11:31:58 -0800
Subject: Postfix and cyrus in Macports bind to different saslauthd
Message-ID: <fc.004c4c58114a5a44004c4c58114a5a44.114a5db5@biola.edu>

>Hi there,
>I am experimenting an extrange behaviour with saslauthd daemons.
>Macports port of Postfix seems to need Apple's builtin saslauthd daemon
>but
>Macports port of Cyrus needs macports version of saslauthd.
>I guess this is not normal... I don't mind using any of the versions of
>saslauthd as I don't need a special auth mech; just rimap which is built
>in
>both, but whould like to use just one of them. Now I have both saslauthd
>started. mux files ar in /opt/local/var/state/saslauthd/mux and
>/var/state/saslauthd/mux
>
>Anybody knows how can y make Macports ports of postfix or Cyrus Imaps use
>one or the other saslauthd daemons? 

Hi Ignacio,

I haven't used postscript this way, but it is set to do that and it seems
like it is building against the macports version of cyrus-sasl judging by
the build messages.  Can you give any information you see where it shows
that it isn't -error messages, otool output or anything else?  Thanks.

Mark


From christopher.rob.jones at cern.ch  Fri Jan 23 11:45:31 2009
From: christopher.rob.jones at cern.ch (Chris Jones)
Date: Fri, 23 Jan 2009 19:45:31 +0000
Subject: Difference between uninstalled and deactivated ?
Message-ID: <FE86DA8B-F218-4087-BE92-95EA685CE999@cern.ch>

Hi,

I've just noticed something the perhaps someone can explain to me.  
Whenever I run 'sudo port upgrade outpdated', and a port gets  
upgraded, the old port is first deactivated before the new one is  
installed and activated. But the old port is never uninstalled ? What  
does this mean ? Does it mean over time my system will slowly fill up  
with old unused versions of ports ?

  For instance for perl at the moment I have

localhost ~ > sudo port installed | grep perl
Password:
   perl5 @5.8.8_1
   perl5 @5.8.8_2
   perl5 @5.8.9_0 (active)
   perl5.8 @5.8.8_3+darwin_9
   perl5.8 @5.8.9_0
   perl5.8 @5.8.9_1
   perl5.8 @5.8.9_2 (active)


Should I worry about uninstalling the _0 and _1 ports ? If so, is  
there some way I can get this done automatically while upgrading ?

Sorry for the newbie questions ..

Chris

From choffman at eclimb.net  Fri Jan 23 11:50:21 2009
From: choffman at eclimb.net (Craig Hoffman)
Date: Fri, 23 Jan 2009 12:50:21 -0700
Subject: Problems using PHP and CURL
In-Reply-To: <B06456ED-A3F4-48EF-B121-AA747F4EBE71@eclimb.net>
References: <B06456ED-A3F4-48EF-B121-AA747F4EBE71@eclimb.net>
Message-ID: <B69E7150-AB63-47CD-B0E6-92CC6214C031@eclimb.net>

Follow-up - Adding this line to my script seemed to fix it:  
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0);

Problem resolved.
Thank you for everybody's suggestions and help.
_______________________
Craig Hoffman
iChat / AIM: mountain.dog
_______________________





On Jan 23, 2009, at 6:54 AM, Craig Hoffman wrote:

> Ok, here it goes.  I'll try to explain this the best I can.  A few  
> days ago I started using MacPorts to replace Marc Lynage's  PHP  
> package.  Everything installed and worked without a hitch (PHP,  
> Apache2, MySQL, CURL, Etc...).  Yesterday, while working on a PHP  
> CURL script, I noticed CURL is not  sending or receiving the  
> request.  The script works fine on our production server and when  
> I'm running Marc Lynage's  PHP package (5.2.5) / Apple's stock  
> Apache version.   MacPort PHP Info file (5.2.8)  tells me CURL is  
> installed.   I've also compared both PHP INI files (Lynage's and  
> MacPorts) and their identical.   I'm stumped on why it works on one  
> but not the other.  Could it be something with Apache2?
>
> Does anyone have any ideas what's going on?
>
> Here's what's installed with CURL
> curl 7.19.3 (i386-apple-darwin9.6.0) libcurl/7.19.3 OpenSSL/0.9.8j
> zlib/1.2.3
> Protocols: tftp ftp telnet dict ldap http file https ftps
> Features: IPv6 Largefile NTLM SSL libz
> _______________________
> Craig Hoffman
> iChat / AIM: mountain.dog
> _______________________
>
>
>
>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From jmr at macports.org  Fri Jan 23 12:11:03 2009
From: jmr at macports.org (Joshua Root)
Date: Sat, 24 Jan 2009 07:11:03 +1100
Subject: Difference between uninstalled and deactivated ?
In-Reply-To: <FE86DA8B-F218-4087-BE92-95EA685CE999@cern.ch>
References: <FE86DA8B-F218-4087-BE92-95EA685CE999@cern.ch>
Message-ID: <497A2457.6030900@macports.org>

Chris Jones wrote:
> Hi,
> 
> I've just noticed something the perhaps someone can explain to me.
> Whenever I run 'sudo port upgrade outpdated', and a port gets upgraded,
> the old port is first deactivated before the new one is installed and
> activated. But the old port is never uninstalled ? What does this mean ?
> Does it mean over time my system will slowly fill up with old unused
> versions of ports ?

Yes, that's exactly what it means. This is a design decision which
allows you to roll back to an older version if there are problems with
the new one.

> Should I worry about uninstalling the _0 and _1 ports ? If so, is there
> some way I can get this done automatically while upgrading ?

You can uninstall older versions with `sudo port uninstall name
@version` (just copy & paste the name and version from the output of
`port installed`). Or you can uninstall all inactive versions at once
with `sudo port uninstall inactive`.

If you wish, you can use the -u option when upgrading to immediately
uninstall the old versions after installing the new ones.

Reference:
<http://guide.macports.org/#using.port.upgrade>

- Josh

From christopher.rob.jones at cern.ch  Fri Jan 23 12:19:59 2009
From: christopher.rob.jones at cern.ch (Chris Jones)
Date: Fri, 23 Jan 2009 20:19:59 +0000
Subject: Difference between uninstalled and deactivated ?
In-Reply-To: <497A2457.6030900@macports.org>
References: <FE86DA8B-F218-4087-BE92-95EA685CE999@cern.ch>
	<497A2457.6030900@macports.org>
Message-ID: <741D5F02-D94F-4BBE-90AE-E92D00B05DC3@cern.ch>

>> Hi,

>> I've just noticed something the perhaps someone can explain to me.
>> Whenever I run 'sudo port upgrade outpdated', and a port gets  
>> upgraded,
>> the old port is first deactivated before the new one is installed and
>> activated. But the old port is never uninstalled ? What does this  
>> mean ?
>> Does it mean over time my system will slowly fill up with old unused
>> versions of ports ?
>
> Yes, that's exactly what it means. This is a design decision which
> allows you to roll back to an older version if there are problems with
> the new one.

Thanks for the clarification. Makes sense I guess.

>
>
>> Should I worry about uninstalling the _0 and _1 ports ? If so, is  
>> there
>> some way I can get this done automatically while upgrading ?
>
> You can uninstall older versions with `sudo port uninstall name
> @version` (just copy & paste the name and version from the output of
> `port installed`). Or you can uninstall all inactive versions at once
> with `sudo port uninstall inactive`.

Ah. Thats the command I was looking for but didn't know it !

>
>
> If you wish, you can use the -u option when upgrading to immediately
> uninstall the old versions after installing the new ones.

Thanks. I guess it makes sense though to check a new port works before  
uninstalling the old one.

cheers Chris
>
>
> Reference:
> <http://guide.macports.org/#using.port.upgrade>
>
> - Josh


From talklists at newgeo.com  Fri Jan 23 13:06:48 2009
From: talklists at newgeo.com (Scott Haneda)
Date: Fri, 23 Jan 2009 13:06:48 -0800
Subject: ASSP port testing, not getting all perl mods to work
In-Reply-To: <4979AD6E.30003@macports.org>
References: <9278E002-0E62-4C8E-B4A6-F405CB82230E@newgeo.com>	<CDE8F213-237A-4F78-8663-114C9B2075E5@newgeo.com>	<E80887E3-0F85-41EC-8A82-F1B74007E630@comcast.net>	<B9ED20B5-F68F-4254-BE81-CF315EEF5C34@newgeo.com>	<74FAF344-CBAF-40E1-BFBD-443DB7495355@comcast.net>	<72EF408A-2324-476F-A9F9-FDD589CED74B@newgeo.com>	<ED894C6F-EF85-46EC-830B-F4C8EDAFDE49@macports.org>
	<01BB3178-DAD4-41BF-9C38-B79AE58A2DF4@newgeo.com>
	<4979AD6E.30003@macports.org>
Message-ID: <CB6A1083-F389-4C6D-ACAC-9A010F7263BA@newgeo.com>

On Jan 23, 2009, at 3:43 AM, Joshua Root wrote:

> Scott Haneda wrote:
>> Looking back over the install log:
>>
>> Warning: violation by /usr
>> Warning: p5-mail-spf violates the layout of the ports-filesystems!
>> Warning: Please fix or indicate this misbehavior (if it is  
>> intended), it
>> will be an error in future releases!
>> --->  Installing p5-mail-spf @v2.006_0
>>
>> I did some quick searching.... I am taking a guess, but does this mod
>> try to install somewhere it should not be installing?  What is the
>> course of action here, modify the source, or go to the developer?
>
> Yes, that would certainly be the problem. Use `port contents
> p5-mail-spf` to see exactly what has been installed where. Other perl
> module ports install to $prefix, so it does seem to be a bug with this
> particular module, or at least an oddity that makes it need special
> treatment.


port contents p5-mail-spf | grep -v opt
Port p5-mail-spf contains:
   /usr/sbin/spfd

So, how does not resolve this?  And I thought ports expressly  
prevented this, or is this just the port makers job to prevent it?   
Since ports noticed it, I would think it would have blocked it
--
Scott


From blb at macports.org  Fri Jan 23 13:15:27 2009
From: blb at macports.org (Bryan Blackburn)
Date: Fri, 23 Jan 2009 14:15:27 -0700
Subject: Error after trying to upgrade installed
In-Reply-To: <DCEC1198-033D-4CB4-87D6-F9ACDDF6F75C@geeklair.net>
References: <4b75340e0901181530x6b9284e3wd39d84c4f37a507f@mail.gmail.com>
	<4973BF65.7050700@macports.org>
	<20090118235837.GE741@ninagal.withay.com>
	<4b75340e0901181625h297705earee5498725022c2bb@mail.gmail.com>
	<4973D310.1090300@macports.org>
	<69C9929E-156A-44D3-89EC-F9873E3EF118@macports.org>
	<alpine.OSX.2.00L.0901190811250.80957@teraqry.sevanohynk.bet>
	<5E17D0EB-8173-4C41-AD00-2B32BBCD1ECE@macports.org>
	<alpine.OSX.2.00L.0901230810020.31248@teraqry.sevanohynk.bet>
	<DCEC1198-03