From braden at endoframe.com  Mon Dec  1 00:20:05 2008
From: braden at endoframe.com (Braden McDaniel)
Date: Mon, 01 Dec 2008 03:20:05 -0500
Subject: Using libsdl-framework
In-Reply-To: <642E2F63-BE8B-4945-930D-6CDF71AB87E4@macports.org>
References: <4933869D.9060401@endoframe.com>
	<642E2F63-BE8B-4945-930D-6CDF71AB87E4@macports.org>
Message-ID: <49339E35.9030803@endoframe.com>

Anders F Bj?rklund wrote:
> Braden McDaniel wrote:
> 
>> Is MacPorts' libsdl-framework usable directly from C and C++, or do I 
>> need an Objective-C entry point as described here?
>>
>>   <http://www.libsdl.org/faq.php?action=listentries&category=7#55>
> 
> For Cocoa backend with SDL 1.2 you need a SDLMain entry point.
> Normally this is handled by `sdl-config`, not so with Xcode.

Ah, you mean if I'm using libsdl (i.e., not the framework variant).

>> When I try to compile this program:
>>
>>   #include <SDL/SDL.h>
>>   int main(int argc, char * argv[])
>>   {
>>     SDL_Init(0);
>>   }
>>
>> ... like this:
>>
>>   gcc -o foo -framework SDL foo.c
> 
> You are missing a "-F/opt/local/Library/Frameworks", as well ?
> (so that it can find it in the ${prefix}, like with -I or -L)

libsdl-framework appears to get installed to /Library/Frameworks, so 
this is not required.

>> ... I get this linker error:
>>
>>   Undefined symbols:
>>     "_main", referenced from:
>>         start in crt1.10.5.o
>>   ld: symbol(s) not found
>>   collect2: ld returned 1 exit status
>>
>> -lSDLmain didn't help (AFAICT, the framework provides no 
>> libSDLmain.a); is there some other alternative?
> 
> libSDLmain.a is only included with the library (non-framework)
> version of SDL, with the framework you need to compile SDLMain.m

Okay; thanks for the confirmation.

-- 
Braden McDaniel                      e-mail: <braden at endoframe.com>
<http://endoframe.com>               Jabber: <braden at jabber.org>

From afb at macports.org  Mon Dec  1 00:32:26 2008
From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=)
Date: Mon, 1 Dec 2008 09:32:26 +0100
Subject: Using libsdl-framework
In-Reply-To: <49339E35.9030803@endoframe.com>
References: <4933869D.9060401@endoframe.com>
	<642E2F63-BE8B-4945-930D-6CDF71AB87E4@macports.org>
	<49339E35.9030803@endoframe.com>
Message-ID: <48C68640-77E1-4417-9E09-4C066044D519@macports.org>

Braden McDaniel:

>> Normally this is handled by `sdl-config`, not so with Xcode.
>
> Ah, you mean if I'm using libsdl (i.e., not the framework variant).

Yup. (gcc -o foo `sdl-config --cflags --libs` foo.c)

Using frameworks outside of Xcode.app usually lands in "unsupported",
i.e. most setups are using frameworks with GUI or libraries with CLI...

Note that the include style varies between frameworks and libraries too.
As in <SDL/SDL.h> is for frameworks, while "SDL.h" is for libraries.
For SDL it usually leads to the same place, but for other frameworks
such as SDL_image or OpenGL the install location varies between the two.

>>>   gcc -o foo -framework SDL foo.c
>> You are missing a "-F/opt/local/Library/Frameworks", as well ?
>> (so that it can find it in the ${prefix}, like with -I or -L)
>
> libsdl-framework appears to get installed to /Library/Frameworks,  
> so this is not required.

Consider that a bug ;-)

Seriously, you don't need any -I or -F when using /usr/local or
/Library/Frameworks but MacPorts *should* install to /opt/local...

>> libSDLmain.a is only included with the library (non-framework)
>> version of SDL, with the framework you need to compile SDLMain.m
>
> Okay; thanks for the confirmation.

It's the same thing really (i.e. libSDLmain.a is built from SDLMain.m)
just that the framework download/install doesn't include a binary...

Normally you would use the Xcode template to set up a new Xcode project,
and that would include the SDLMain.m source. Outside MacPorts, that is.

--anders


From raimue at macports.org  Mon Dec  1 02:08:12 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Mon, 01 Dec 2008 11:08:12 +0100
Subject: *_select's
In-Reply-To: <20081130061937.GU525@ninagal.withay.com>
References: <5993BFC8-35E4-4222-9E98-DB8362CC2DBB@voidfx.net>	<2FA70823-8979-4E41-B1C6-1F382273846B@macports.org>
	<20081130061937.GU525@ninagal.withay.com>
Message-ID: <4933B78C.5070808@macports.org>

Bryan Blackburn wrote:
[...]
> it would just be
> 
> $ select python 2.5
> $ select gcc mp-4.3
> 
> The ${prefix}/etc/select stuff is already subdivided by system like this, so
> it should be a pretty natural change, though the arguments will obviously be
> a bit different.

Best would be to add select stuff to base like 'port select'. All other
functionality of MacPorts is called from the port tool and we should
stick to this.
*_select tools were just a quick workaround to make it usable until this
is available in base. Also, using a base tool it can be more automated,
for example de-select a version if its port is deactivated/uninstalled.

Rainer

From face at CentosPrime.COM  Mon Dec  1 07:45:53 2008
From: face at CentosPrime.COM (Chris Janton)
Date: Mon, 01 Dec 2008 08:45:53 -0700
Subject: Error upgrading xrender on Panther
In-Reply-To: <478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
Message-ID: <6662D0EB-06F1-47D3-B0EA-58B0EDC98545@CentosPrime.COM>

On 2008-11-30 , at 12:18 , Jeremy Huddleston wrote:

> Can you please see:
>
> http://trac.macports.org/ticket/17429#comment:
>
> I think if you pull in xorg-libX11 first, it'll be fine, but I need  
> someone to test that first...

sudo port install xorg-libX11

followed by

sudo port upgrade xrender

works just fine on Panther.

Thanks.

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



From ryandesign at macports.org  Mon Dec  1 12:35:39 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 1 Dec 2008 14:35:39 -0600
Subject: [macports-mgr] A problem
In-Reply-To: <00F7544F-7E8F-44A6-85A7-6C99375FFA8B@gmail.com>
References: <00F7544F-7E8F-44A6-85A7-6C99375FFA8B@gmail.com>
Message-ID: <CD1CF498-B2CE-4EA3-A221-9824721BDF9F@macports.org>

On Dec 1, 2008, at 14:24, Christos Vlachos wrote:

> Dear maintainers,
> Apologies for using this email address, but couldn't find any other  
> to address to you. I would appreciate your help on the following  
> problem. I want to uninstall MacPorts, since I installed it before  
> installing X11 and Xcode. Now, the problem is that although I  
> follow the command line below, I get the error:
>
> rm: illegal option -- /
> usage: rm [-f | -i] [-dPRrvW] file ...
>        unlink file
>
>
>
>
>
>
>  sudo rm -rf \
>     /opt/local \
>     /etc/manpaths.d/macports \
>     /etc/paths.d/macports \
>     /Applications/DarwinPorts \
>     /Applications/MacPorts \
>     /Library/LaunchDaemons/org.macports.* \
>     /Library/Receipts/DarwinPorts*.pkg \
>     /Library/Receipts/MacPorts*.pkg \
>     /Library/StartupItems/DarwinPortsStartup \
>     /Library/Tcl/darwinports1.0 \
>     /Library/Tcl/macports1.0
>
>
> I would really appreciate your help on this. Is there any possible  
> command line to solve the problem?
>
> Thank you,
> Chris

Hi Chris. The command given above is correct. Indeed "--" is not a  
legal option to "rm", but "--" does not appear in the command  
provided above. Which command did you actually execute? You should  
just be able to copy all the above lines and paste them into a Terminal.

The correct place to ask these kinds of questions is on the macports- 
users mailing list, which I have Cc'd on this reply. Please direct  
any further replies there, and make sure you subscribe to the list  
first so that you will be allowed to post.

http://lists.macosforge.org/mailman/listinfo.cgi/macports-users



From ndiscreet at gmail.com  Mon Dec  1 13:01:23 2008
From: ndiscreet at gmail.com (Altoine Barker)
Date: Mon, 1 Dec 2008 15:01:23 -0600
Subject: sudo port upgrade all
In-Reply-To: <B27E8161-EAD0-4238-A6C3-4FDDDBD43962@dxradio.demon.co.uk>
References: <20716578.post@talk.nabble.com>
	<4AC371D1-3252-4FD1-BC4C-62A73A8141E2@macports.org>
	<5C300143-2925-45F2-A7F7-CE4926D9D13B@web.de>
	<F493F668-5932-4E33-986D-E30F1E53F716@macports.org>
	<52851960-A1E4-4AF4-9F43-E25E1F2D1561@bellsouth.net>
	<B27E8161-EAD0-4238-A6C3-4FDDDBD43962@dxradio.demon.co.uk>
Message-ID: <3aa26b560812011301u16e941c6jada56533664677ea@mail.gmail.com>

Personally, I came across this before and use this command "sudo port -vu
upgrade outdated" to avoid having any more similar issues. It has worked for
me so far for the past year.HTH

-Altoine

On Sun, Nov 30, 2008 at 5:24 PM, Mark Hattam <mark at dxradio.demon.co.uk>wrote:

>
> On 29 Nov 2008, at 03:01, William Davis wrote:
>
>
>>
>>>
>>>  Then sudo port upgrade all would equate to sudo port upgrade installed.
>>>>
>>>
>>> which would still be a bad command to run; you really want "sudo port
>>> upgrade outdated".
>>>
>>>
>>
>> What I really want is "sudo port upgrade -R outdated"  but that runs
>> nearly forever and makes a big mess in various ways.
>> Running "sudo port upgrade installed" is a sort of limping substitute
>> since it will as it gets repeated over time rebuild the various chains of
>> dependents thus updating them.
>>
>> So if "-R" is really going to work correctly in 1.7 I dont care. OTW I
>> want "sudo port upgrade outdated" to work.
>>
>> Just my 2 centavos.
>> William Davis
>>
>>
>
>
> Tried a "sudo port upgrade -R outdated" just now, and it promptly errored
> and quit ... so what's supposed to happen with -R option? But the new
> version is active so it upgraded OK. I've always just done "sudo port
> upgrade outdated" up til now.
>
>
> Downloaded MacPorts base version 1.600
>
> The MacPorts installation is not outdated and so was not updated
> selfupdate done!
> The following installed ports are outdated:
> sqlite3                        3.6.6.1_0 < 3.6.6.2_0
> All Done
>
> Mac:~ me$ sudo port upgrade -R outdated
> --->  Fetching sqlite3
> --->  Attempting to fetch sqlite-3.6.6.2.tar.gz from
> http://www.sqlite.org/
> --->  Verifying checksum(s) for sqlite3
> --->  Extracting sqlite3
> --->  Configuring sqlite3
> --->  Building sqlite3 with target all
> --->  Staging sqlite3 into destroot
> --->  Deactivating sqlite3 3.6.6.1_0
> --->  Installing sqlite3 3.6.6.2_0
> --->  Activating sqlite3 3.6.6.2_0
> --->  Cleaning sqlite3
> --->  Deactivating sqlite3 3.6.6.1_0
> Error: Deactivating sqlite3 3.6.6.1_0 failed: Active version of sqlite3 is
> not 3.6.6.1_0 but 3.6.6.2_0.
>
> Mac:~ me$ sudo port installed | grep sqlite
>  sqlite3 @3.6.6.1_0
>  sqlite3 @3.6.6.2_0 (active)
>
>
> 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/20081201/b38abd72/attachment.html>

From ryandesign at macports.org  Mon Dec  1 13:04:39 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 1 Dec 2008 15:04:39 -0600
Subject: sudo port upgrade all
In-Reply-To: <3aa26b560812011301u16e941c6jada56533664677ea@mail.gmail.com>
References: <20716578.post@talk.nabble.com>
	<4AC371D1-3252-4FD1-BC4C-62A73A8141E2@macports.org>
	<5C300143-2925-45F2-A7F7-CE4926D9D13B@web.de>
	<F493F668-5932-4E33-986D-E30F1E53F716@macports.org>
	<52851960-A1E4-4AF4-9F43-E25E1F2D1561@bellsouth.net>
	<B27E8161-EAD0-4238-A6C3-4FDDDBD43962@dxradio.demon.co.uk>
	<3aa26b560812011301u16e941c6jada56533664677ea@mail.gmail.com>
Message-ID: <C1626320-30C8-4EDE-995B-8AAB48D5BE92@macports.org>

On Dec 1, 2008, at 15:01, Altoine Barker wrote:

> Personally, I came across this before and use this command "sudo  
> port -vu upgrade outdated" to avoid having any more similar issues.  
> It has worked for me so far for the past year.HTH

"port upgrade" is for upgrading ports and dependencies (ports that  
the port being upgraded depends on)
The "-R" flag is for upgrading dependents (ports that depend on the  
port being upgraded)
The "-u" flag tells MacPorts to uninstall the old version after  
installing the new version
The "-v" flag tells MacPorts to be verbose about what it's doing


> -Altoine
>
> On Sun, Nov 30, 2008 at 5:24 PM, Mark Hattam  
> <mark at dxradio.demon.co.uk> wrote:
>
> On 29 Nov 2008, at 03:01, William Davis wrote:
>
>
>
>
> Then sudo port upgrade all would equate to sudo port upgrade  
> installed.
>
> which would still be a bad command to run; you really want "sudo  
> port upgrade outdated".
>
>
>
> What I really want is "sudo port upgrade -R outdated"  but that  
> runs nearly forever and makes a big mess in various ways.
> Running "sudo port upgrade installed" is a sort of limping  
> substitute since it will as it gets repeated over time rebuild the  
> various chains of dependents thus updating them.
>
> So if "-R" is really going to work correctly in 1.7 I dont care.  
> OTW I want "sudo port upgrade outdated" to work.
>
> Just my 2 centavos.
> William Davis
>
>
>
>
> Tried a "sudo port upgrade -R outdated" just now, and it promptly  
> errored and quit ... so what's supposed to happen with -R option?  
> But the new version is active so it upgraded OK. I've always just  
> done "sudo port upgrade outdated" up til now.
>
>
> Downloaded MacPorts base version 1.600
>
> The MacPorts installation is not outdated and so was not updated
> selfupdate done!
> The following installed ports are outdated:
> sqlite3                        3.6.6.1_0 < 3.6.6.2_0
> All Done
>
> Mac:~ me$ sudo port upgrade -R outdated
> --->  Fetching sqlite3
> --->  Attempting to fetch sqlite-3.6.6.2.tar.gz from http:// 
> www.sqlite.org/
> --->  Verifying checksum(s) for sqlite3
> --->  Extracting sqlite3
> --->  Configuring sqlite3
> --->  Building sqlite3 with target all
> --->  Staging sqlite3 into destroot
> --->  Deactivating sqlite3 3.6.6.1_0
> --->  Installing sqlite3 3.6.6.2_0
> --->  Activating sqlite3 3.6.6.2_0
> --->  Cleaning sqlite3
> --->  Deactivating sqlite3 3.6.6.1_0
> Error: Deactivating sqlite3 3.6.6.1_0 failed: Active version of  
> sqlite3 is not 3.6.6.1_0 but 3.6.6.2_0.
>
> Mac:~ me$ sudo port installed | grep sqlite
>  sqlite3 @3.6.6.1_0
>  sqlite3 @3.6.6.2_0 (active)
>
>
> Mark
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>


From moshe.kamensky at gmail.com  Mon Dec  1 13:53:24 2008
From: moshe.kamensky at gmail.com (Moshe Kamensky)
Date: Mon, 1 Dec 2008 16:53:24 -0500
Subject: [macports-mgr] A problem
In-Reply-To: <CD1CF498-B2CE-4EA3-A221-9824721BDF9F@macports.org>
References: <00F7544F-7E8F-44A6-85A7-6C99375FFA8B@gmail.com>
	<CD1CF498-B2CE-4EA3-A221-9824721BDF9F@macports.org>
Message-ID: <20081201215324.GA5657@detritus>

* Ryan Schmidt <ryandesign at macports.org> [01/12/08 15:39]:
> On Dec 1, 2008, at 14:24, Christos Vlachos wrote:
>
>> Dear maintainers,
>> Apologies for using this email address, but couldn't find any other to 
>> address to you. I would appreciate your help on the following problem. I 
>> want to uninstall MacPorts, since I installed it before installing X11 and 
>> Xcode. Now, the problem is that although I follow the command line below, I 
>> get the error:
>>
>> rm: illegal option -- /
>> usage: rm [-f | -i] [-dPRrvW] file ...
>>        unlink file
>>
>>
>>
>>
>>
>>
>>  sudo rm -rf \
>>     /opt/local \
>>     /etc/manpaths.d/macports \
>>     /etc/paths.d/macports \
>>     /Applications/DarwinPorts \
>>     /Applications/MacPorts \
>>     /Library/LaunchDaemons/org.macports.* \
>>     /Library/Receipts/DarwinPorts*.pkg \
>>     /Library/Receipts/MacPorts*.pkg \
>>     /Library/StartupItems/DarwinPortsStartup \
>>     /Library/Tcl/darwinports1.0 \
>>     /Library/Tcl/macports1.0
>>
>>
>> I would really appreciate your help on this. Is there any possible command 
>> line to solve the problem?
>>
>> Thank you,
>> Chris
>
> Hi Chris. The command given above is correct. Indeed "--" is not a legal 
> option to "rm", but "--" does not appear in the command provided above. 
> Which command did you actually execute? You should just be able to copy all 
> the above lines and paste them into a Terminal.
>

Maybe rm is a shell alias or function. Try replacing rm with /bin/rm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081201/3381c705/attachment.bin>

From blb at macports.org  Mon Dec  1 14:47:42 2008
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 1 Dec 2008 15:47:42 -0700
Subject: *_select's
In-Reply-To: <4933B78C.5070808@macports.org>
References: <5993BFC8-35E4-4222-9E98-DB8362CC2DBB@voidfx.net>
	<2FA70823-8979-4E41-B1C6-1F382273846B@macports.org>
	<20081130061937.GU525@ninagal.withay.com>
	<4933B78C.5070808@macports.org>
Message-ID: <20081201224742.GH651@ninagal.withay.com>

On Mon, Dec 01, 2008 at 11:08:12AM +0100, Rainer M?ller said:
> Bryan Blackburn wrote:
> [...]
> > it would just be
> > 
> > $ select python 2.5
> > $ select gcc mp-4.3
> > 
> > The ${prefix}/etc/select stuff is already subdivided by system like this, so
> > it should be a pretty natural change, though the arguments will obviously be
> > a bit different.
> 
> Best would be to add select stuff to base like 'port select'. All other
> functionality of MacPorts is called from the port tool and we should
> stick to this.
> *_select tools were just a quick workaround to make it usable until this
> is available in base. Also, using a base tool it can be more automated,
> for example de-select a version if its port is deactivated/uninstalled.

Agreed, and so it doesn't get lost:

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

Bryan


> 
> Rainer

From tim.visher at gmail.com  Mon Dec  1 17:49:13 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Mon, 1 Dec 2008 20:49:13 -0500
Subject: Error on 10.3.9 v 1.600 installing mplayer
Message-ID: <c115fd3c0812011749n4713cfa6v4002f15c7aba34ef@mail.gmail.com>

Hey Everyone,

I'm trying to install mplayer 1.0rc2 on 10.3.9 using port 1.600 and I
got the following error.

    ld: warning -L: directory name (/opt/local/lib/samba3) does not exist
    ld: warning -L: directory name (/usr/local/lib) does not exist
    ld: get_path.o illegal reference to symbol: _CFBundleCopyBundleURL
defined in indirectly referenced dynamic
library/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
make: *** [mplayer] Error 1

The full dump of the install is pasted at the following pastebin URL:

http://pastebin.com/m1ce19f11

Any help would be much appreciated.

-- 

In Christ,

Timmy V.

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

From ryandesign at macports.org  Mon Dec  1 19:44:37 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 1 Dec 2008 21:44:37 -0600
Subject: Error on 10.3.9 v 1.600 installing mplayer
In-Reply-To: <c115fd3c0812011749n4713cfa6v4002f15c7aba34ef@mail.gmail.com>
References: <c115fd3c0812011749n4713cfa6v4002f15c7aba34ef@mail.gmail.com>
Message-ID: <55B24BA1-EB73-49D5-8B8A-F7ACA0AAABB9@macports.org>


On Dec 1, 2008, at 19:49, Tim Visher wrote:

> I'm trying to install mplayer 1.0rc2 on 10.3.9 using port 1.600 and I
> got the following error.
>
>     ld: warning -L: directory name (/opt/local/lib/samba3) does not  
> exist
>     ld: warning -L: directory name (/usr/local/lib) does not exist
>     ld: get_path.o illegal reference to symbol: _CFBundleCopyBundleURL
> defined in indirectly referenced dynamic
> library/System/Library/Frameworks/CoreFoundation.framework/Versions/ 
> A/CoreFoundation
> make: *** [mplayer] Error 1
>
> The full dump of the install is pasted at the following pastebin URL:
>
> http://pastebin.com/m1ce19f11
>
> Any help would be much appreciated.

Possibly similar to this:

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

Though that was with Tiger and you're on Panther, which is  
unfortunately not well-tested anymore. Check if you've properly  
installed the optional SDKs available in the Xcode install.

I can also try it on my Panther machine later.


From blb at macports.org  Mon Dec  1 20:10:51 2008
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 1 Dec 2008 21:10:51 -0700
Subject: Error on 10.3.9 v 1.600 installing mplayer
In-Reply-To: <55B24BA1-EB73-49D5-8B8A-F7ACA0AAABB9@macports.org>
References: <c115fd3c0812011749n4713cfa6v4002f15c7aba34ef@mail.gmail.com>
	<55B24BA1-EB73-49D5-8B8A-F7ACA0AAABB9@macports.org>
Message-ID: <20081202041051.GK651@ninagal.withay.com>

On Mon, Dec 01, 2008 at 09:44:37PM -0600, Ryan Schmidt said:
>
> On Dec 1, 2008, at 19:49, Tim Visher wrote:
>
>> I'm trying to install mplayer 1.0rc2 on 10.3.9 using port 1.600 and I
>> got the following error.
>>
>>     ld: warning -L: directory name (/opt/local/lib/samba3) does not  
>> exist
>>     ld: warning -L: directory name (/usr/local/lib) does not exist
>>     ld: get_path.o illegal reference to symbol: _CFBundleCopyBundleURL
>> defined in indirectly referenced dynamic
>> library/System/Library/Frameworks/CoreFoundation.framework/Versions/ 
>> A/CoreFoundation
>> make: *** [mplayer] Error 1
>>
>> The full dump of the install is pasted at the following pastebin URL:
>>
>> http://pastebin.com/m1ce19f11
>>
>> Any help would be much appreciated.
>
> Possibly similar to this:
>
> http://trac.macports.org/ticket/11748
>
> Though that was with Tiger and you're on Panther, which is unfortunately 
> not well-tested anymore. Check if you've properly installed the optional 
> SDKs available in the Xcode install.
>
> I can also try it on my Panther machine later.

There were some issues with QuickTime SDK on 10.3 way back when:

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

Not sure if that's still an issue.

Bryan


From christos.vlachos at gmail.com  Tue Dec  2 02:06:52 2008
From: christos.vlachos at gmail.com (Christos Vlachos)
Date: Tue, 2 Dec 2008 12:06:52 +0200
Subject: Please help.....
Message-ID: <D11A3001-AA33-45FD-81D4-19595DDF3CA8@gmail.com>

Dear all,
I would appreciate your help on the following problem. I want to  
uninstall MacPorts, since I installed it before installing X11 and  
Xcode. Now, the problem is that although I follow the command line  
below, I get the error:

rm: illegal option -- /
usage: rm [-f | -i] [-dPRrvW] file ...
        unlink file

The problem is that I have not used any "--" in the terminal command.  
The command line I used is the following (copy+pasted) from the web  
page.



  sudo rm -rf \
     /opt/local \
     /etc/manpaths.d/macports \
     /etc/paths.d/macports \
     /Applications/DarwinPorts \
     /Applications/MacPorts \
     /Library/LaunchDaemons/org.macports.* \
     /Library/Receipts/DarwinPorts*.pkg \
     /Library/Receipts/MacPorts*.pkg \
     /Library/StartupItems/DarwinPortsStartup \
     /Library/Tcl/darwinports1.0 \
     /Library/Tcl/macports1.0


I would really appreciate your help on this. Is there any possible  
command line to solve the problem? Specifically, is there any command  
line that uninstalls the MacPort successfully under these circumstances?

Thank you,
Chris

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081202/03ca5cd6/attachment.html>

From ryandesign at macports.org  Tue Dec  2 03:04:11 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 2 Dec 2008 05:04:11 -0600
Subject: rm: illegal option -- / (was: Re: Please help.....)
In-Reply-To: <D11A3001-AA33-45FD-81D4-19595DDF3CA8@gmail.com>
References: <D11A3001-AA33-45FD-81D4-19595DDF3CA8@gmail.com>
Message-ID: <91893CBB-71A0-476A-BC1D-A435277E262C@macports.org>


On Dec 2, 2008, at 04:06, Christos Vlachos wrote:

> I would appreciate your help on the following problem. I want to  
> uninstall MacPorts, since I installed it before installing X11 and  
> Xcode. Now, the problem is that although I follow the command line  
> below, I get the error:
>
> rm: illegal option -- /
> usage: rm [-f | -i] [-dPRrvW] file ...
>        unlink file
>
> The problem is that I have not used any "--" in the terminal  
> command. The command line I used is the following (copy+pasted)  
> from the web page.
>
>
>
>  sudo rm -rf \
>     /opt/local \
>     /etc/manpaths.d/macports \
>     /etc/paths.d/macports \
>     /Applications/DarwinPorts \
>     /Applications/MacPorts \
>     /Library/LaunchDaemons/org.macports.* \
>     /Library/Receipts/DarwinPorts*.pkg \
>     /Library/Receipts/MacPorts*.pkg \
>     /Library/StartupItems/DarwinPortsStartup \
>     /Library/Tcl/darwinports1.0 \
>     /Library/Tcl/macports1.0
>
>
> I would really appreciate your help on this. Is there any possible  
> command line to solve the problem? Specifically, is there any  
> command line that uninstalls the MacPort successfully under these  
> circumstances?

Ah, sorry, I misread earlier: it's saying the illegal option is "/".  
Which also doesn't make sense to me.

What do you get if you type "which rm"?

What do you get if you type "alias | grep rm"?

Does the "rm" command work for you in other circumstances?

To remove MacPorts, you just need to remove all the items listed  
above. If your "rm" command is not working, you can delete them in  
the Finder instead.


From ryandesign at macports.org  Tue Dec  2 03:37:48 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 2 Dec 2008 05:37:48 -0600
Subject: Error on 10.3.9 v 1.600 installing mplayer
In-Reply-To: <55B24BA1-EB73-49D5-8B8A-F7ACA0AAABB9@macports.org>
References: <c115fd3c0812011749n4713cfa6v4002f15c7aba34ef@mail.gmail.com>
	<55B24BA1-EB73-49D5-8B8A-F7ACA0AAABB9@macports.org>
Message-ID: <17C857FA-77E9-40DB-B2FB-FA8C2F6ABB00@macports.org>

On Dec 1, 2008, at 21:44, Ryan Schmidt wrote:

> On Dec 1, 2008, at 19:49, Tim Visher wrote:
>
>> I'm trying to install mplayer 1.0rc2 on 10.3.9 using port 1.600 and I
>> got the following error.
>>
>>     ld: warning -L: directory name (/opt/local/lib/samba3) does  
>> not exist
>>     ld: warning -L: directory name (/usr/local/lib) does not exist
>>     ld: get_path.o illegal reference to symbol:  
>> _CFBundleCopyBundleURL
>> defined in indirectly referenced dynamic
>> library/System/Library/Frameworks/CoreFoundation.framework/ 
>> Versions/A/CoreFoundation
>> make: *** [mplayer] Error 1
>>
>> The full dump of the install is pasted at the following pastebin URL:
>>
>> http://pastebin.com/m1ce19f11
>>
>> Any help would be much appreciated.
>
> Possibly similar to this:
>
> http://trac.macports.org/ticket/11748
>
> Though that was with Tiger and you're on Panther, which is  
> unfortunately not well-tested anymore. Check if you've properly  
> installed the optional SDKs available in the Xcode install.
>
> I can also try it on my Panther machine later.

On my Panther Mac I have:

ld: osdep/libosdep.a(macosx_finder_args.o) illegal reference to  
symbol: _QuitApplicationEventLoop defined in indirectly referenced  
dynamic library /System/Library/Frameworks/Carbon.framework/Versions/ 
A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox



From ndiscreet at gmail.com  Tue Dec  2 12:10:16 2008
From: ndiscreet at gmail.com (Altoine Barker)
Date: Tue, 2 Dec 2008 14:10:16 -0600
Subject: Please help.....
In-Reply-To: <D11A3001-AA33-45FD-81D4-19595DDF3CA8@gmail.com>
References: <D11A3001-AA33-45FD-81D4-19595DDF3CA8@gmail.com>
Message-ID: <3aa26b560812021210g51a73721q48a1fecbcc4b3059@mail.gmail.com>

What shell are you working in?

-Altoine

On Tue, Dec 2, 2008 at 4:06 AM, Christos Vlachos <christos.vlachos at gmail.com
> wrote:

> Dear all,
> I would appreciate your help on the following problem. I want to uninstall
> MacPorts, since I installed it before installing X11 and Xcode. Now, the
> problem is that although I follow the command line below, I get the error:
>
> rm: illegal option -- /
> usage: rm [-f | -i] [-dPRrvW] file ...
>        unlink file
>
> The problem is that I have not used any "--" in the terminal command. The
> command line I used is the following (copy+pasted) from the web page.
>
>
>
>  *sudo rm -rf \
>     /opt/local \
>     /etc/manpaths.d/macports \
>     /etc/paths.d/macports \
>     /Applications/DarwinPorts \
>     /Applications/MacPorts \
>     /Library/LaunchDaemons/org.macports.* \
>     /Library/Receipts/DarwinPorts*.pkg \
>     /Library/Receipts/MacPorts*.pkg \
>     /Library/StartupItems/DarwinPortsStartup \
>     /Library/Tcl/darwinports1.0 \
>     /Library/Tcl/macports1.0*
>
>
>
> I would really appreciate your help on this. Is there any possible command
> line to solve the problem? Specifically, is there any command line that
> uninstalls the MacPort successfully under these circumstances?
>
> Thank you,
> Chris
>
>
> _______________________________________________
> 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/20081202/704245e4/attachment.html>

From peter at pogma.com  Tue Dec  2 14:36:20 2008
From: peter at pogma.com (Peter O'Gorman)
Date: Tue, 02 Dec 2008 16:36:20 -0600
Subject: Please help.....
In-Reply-To: <3aa26b560812021210g51a73721q48a1fecbcc4b3059@mail.gmail.com>
References: <D11A3001-AA33-45FD-81D4-19595DDF3CA8@gmail.com>
	<3aa26b560812021210g51a73721q48a1fecbcc4b3059@mail.gmail.com>
Message-ID: <4935B864.8010902@pogma.com>

Altoine Barker wrote:
> What shell are you working in?
> 
> -Altoine
> 
> On Tue, Dec 2, 2008 at 4:06 AM, Christos Vlachos
> <christos.vlachos at gmail.com <mailto:christos.vlachos at gmail.com>> wrote:
> 
>     Dear all,
>     I would appreciate your help on the following problem. I want to
>     uninstall MacPorts, since I installed it before installing X11 and
>     Xcode. Now, the problem is that although I follow the command line
>     below, I get the error:
> 
>     rm: illegal option -- /
>     usage: rm [-f | -i] [-dPRrvW] file ...
>            unlink file

Leave the spaces and newlines as they appear in the example.

rm -rf\/
Gives - rm: illegal option -- /

Peter

From sthuebner at nym.hush.com  Wed Dec  3 01:13:17 2008
From: sthuebner at nym.hush.com (Stefan =?utf-8?Q?H=C3=BCbner?=)
Date: Wed, 03 Dec 2008 10:13:17 +0100
Subject: Installing privoxy failed
Message-ID: <gh5ijd$vo$1@ger.gmane.org>

Hi,

I was just about to upgrade privoxy from 3.0.8_1 to 3.0.10_0. But
staging fails exposing the following error:

--->  Fetching privoxy
--->  Attempting to fetch privoxy-3.0.10-stable-src.tar.gz from http://downloads.sourceforge.net/ijbswa
--->  Verifying checksum(s) for privoxy
--->  Extracting privoxy
--->  Configuring privoxy
--->  Building privoxy with target all
--->  Staging privoxy into destroot
Error: Target org.macports.destroot returned: error renaming "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_privoxy/work/destroot/opt/local/etc/privoxy/config": no such file or directory
Error: Status 1 encountered during processing.

Here's the contents of this directory:

nb-imac1:~ sthuebner$ ls -l /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_privoxy/work/destroot/opt/local/etc/privoxy/
total 360
-rw-rw----   1 privoxy  privoxy  42470  3 Dez 10:07 config.new
-rw-rw----   1 privoxy  privoxy  61148  3 Dez 10:07 default.action
-rw-rw----   1 privoxy  privoxy  54887  3 Dez 10:07 default.filter
-rw-rw----   1 privoxy  privoxy   2675  3 Dez 10:07 standard.action
drwxr-xr-x  37 root     admin     1258  3 Dez 10:07 templates
-rw-rw----   1 privoxy  privoxy   3761  3 Dez 10:07 trust.new
-rw-rw----   1 privoxy  privoxy   6425  3 Dez 10:07 user.action.new
-rw-rw----   1 privoxy  privoxy   3334  3 Dez 10:07 user.filter


Has anyone encountered the same issue recently?

-Stefan


From ndiscreet at gmail.com  Wed Dec  3 06:52:32 2008
From: ndiscreet at gmail.com (Altoine Barker)
Date: Wed, 03 Dec 2008 08:52:32 -0600
Subject: Installing privoxy failed
In-Reply-To: <gh5ijd$vo$1@ger.gmane.org>
References: <gh5ijd$vo$1@ger.gmane.org>
Message-ID: <49369D30.6050204@GmAiL.cOm>

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

Have you tried "port clean --all privoxy" and reran your upgrade to see
if you get the same result? HTH

- -Altoine

Stefan H?bner wrote:
> Hi,
> 
> I was just about to upgrade privoxy from 3.0.8_1 to 3.0.10_0. But
> staging fails exposing the following error:
> 
> --->  Fetching privoxy
> --->  Attempting to fetch privoxy-3.0.10-stable-src.tar.gz from http://downloads.sourceforge.net/ijbswa
> --->  Verifying checksum(s) for privoxy
> --->  Extracting privoxy
> --->  Configuring privoxy
> --->  Building privoxy with target all
> --->  Staging privoxy into destroot
> Error: Target org.macports.destroot returned: error renaming "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_privoxy/work/destroot/opt/local/etc/privoxy/config": no such file or directory
> Error: Status 1 encountered during processing.
> 
> Here's the contents of this directory:
> 
> nb-imac1:~ sthuebner$ ls -l /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_privoxy/work/destroot/opt/local/etc/privoxy/
> total 360
> -rw-rw----   1 privoxy  privoxy  42470  3 Dez 10:07 config.new
> -rw-rw----   1 privoxy  privoxy  61148  3 Dez 10:07 default.action
> -rw-rw----   1 privoxy  privoxy  54887  3 Dez 10:07 default.filter
> -rw-rw----   1 privoxy  privoxy   2675  3 Dez 10:07 standard.action
> drwxr-xr-x  37 root     admin     1258  3 Dez 10:07 templates
> -rw-rw----   1 privoxy  privoxy   3761  3 Dez 10:07 trust.new
> -rw-rw----   1 privoxy  privoxy   6425  3 Dez 10:07 user.action.new
> -rw-rw----   1 privoxy  privoxy   3334  3 Dez 10:07 user.filter
> 
> 
> Has anyone encountered the same issue recently?
> 
> -Stefan
> 
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkk2nTAACgkQQlfc9y4ObkMRtACggdLqv13Hg+kykXJwVPlRhrIk
vjYAn2zLNoNGD580SGnMUm/bPbI0MLiu
=N60d
-----END PGP SIGNATURE-----

From tim.visher at gmail.com  Wed Dec  3 06:55:08 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Wed, 3 Dec 2008 09:55:08 -0500
Subject: Error on 10.3.9 v 1.600 installing mplayer
In-Reply-To: <5FB4D404-BD39-4E9A-BF7F-22F9BAA9DD2A@gizmolabs.org>
References: <c115fd3c0812011749n4713cfa6v4002f15c7aba34ef@mail.gmail.com>
	<55B24BA1-EB73-49D5-8B8A-F7ACA0AAABB9@macports.org>
	<17C857FA-77E9-40DB-B2FB-FA8C2F6ABB00@macports.org>
	<5FB4D404-BD39-4E9A-BF7F-22F9BAA9DD2A@gizmolabs.org>
Message-ID: <c115fd3c0812030655g47e26d5ch349d3d2fcc50a82e@mail.gmail.com>

Thanks to everyone who's responded so far.  I know it's a bit of an
archaic question.

Life has me busy at the moment so I haven't had any time since I
posted this to look into the solutions presented.  From memory I did
_not_ install any of the optional SDKs when I installed XCode so that
may be part of it.  I'll try to look into it ASAIC.

On Tue, Dec 2, 2008 at 1:47 PM, Eric Cronin <ecronin at gizmolabs.org> wrote:
> I still have a panther XServe around, so I will take a look at this.  At the
> very least it should be possible to disable linking against quicktime on
> Panther...
>
> Thanks,
> Eric
>
>
> On Dec 2, 2008, at 6:37 AM, Ryan Schmidt wrote:
>
>> On Dec 1, 2008, at 21:44, Ryan Schmidt wrote:
>>
>>> On Dec 1, 2008, at 19:49, Tim Visher wrote:
>>>
>>>> I'm trying to install mplayer 1.0rc2 on 10.3.9 using port 1.600 and I
>>>> got the following error.
>>>>
>>>>   ld: warning -L: directory name (/opt/local/lib/samba3) does not exist
>>>>   ld: warning -L: directory name (/usr/local/lib) does not exist
>>>>   ld: get_path.o illegal reference to symbol: _CFBundleCopyBundleURL
>>>> defined in indirectly referenced dynamic
>>>>
>>>> library/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
>>>> make: *** [mplayer] Error 1
>>>>
>>>> The full dump of the install is pasted at the following pastebin URL:
>>>>
>>>> http://pastebin.com/m1ce19f11
>>>>
>>>> Any help would be much appreciated.
>>>
>>> Possibly similar to this:
>>>
>>> http://trac.macports.org/ticket/11748
>>>
>>> Though that was with Tiger and you're on Panther, which is unfortunately
>>> not well-tested anymore. Check if you've properly installed the optional
>>> SDKs available in the Xcode install.
>>>
>>> I can also try it on my Panther machine later.
>>
>> On my Panther Mac I have:
>>
>> ld: osdep/libosdep.a(macosx_finder_args.o) illegal reference to symbol:
>> _QuitApplicationEventLoop defined in indirectly referenced dynamic library
>> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
>>
>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>
>
>



-- 

In Christ,

Timmy V.

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

From dersh at alum.mit.edu  Wed Dec  3 08:37:56 2008
From: dersh at alum.mit.edu (Adam Dershowitz Ph.D., P.E.)
Date: Wed, 3 Dec 2008 08:37:56 -0800
Subject: Tk Port Question
Message-ID: <57F9CC0E-52E6-4247-816C-9B285D5DB51D@alum.mit.edu>

I have Tk 8.5.5 installed.  I am trying to run an application (GRASS)  
and the new version (6.4 is the development version that will be  
released soon) requires the "Aqua framework" Tk, according to what I  
have learned.
I tried rebuilding Tk with +quartz.  But the binary application that I  
am trying to use is not finding the correct libraries, because it is  
looking for frameworks.  The person who does the binaries suggested  
that I install the ActiveTcl distribution, but that seems silly, given  
that I already have the MacPorts TclTk installed.
So, I am wondering if there is any way to make this installation  
work?  Is there something that can be done with Tk to have it also  
build frameworks?  There is a "--enable-frameworks" flag as part of  
TclTk, but I am not sure if that will work within MacPorts.

Any ideas?

Thanks,

--Adam




From admin2 at enabled.com  Wed Dec  3 11:40:37 2008
From: admin2 at enabled.com (Noah)
Date: Wed, 03 Dec 2008 11:40:37 -0800
Subject: gtk2 failing to build
Message-ID: <4936E0B5.2060401@enabled.com>

any help is appreciated to figure out why gtk2 is failing to build.

sh-3.2# port -v
MacPorts 1.600
Entering interactive mode... ("help" for help, "quit" to quit)



# port install wireshark
--->  Building gtk2 with target all
Error: Target org.macports.build returned: shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_gtk2/work/gtk+-2.14.4" 
&& make all " returned error 2
Command output: make[2]: Nothing to be done for `all'.
Making all in gdk-pixbuf
make  all-recursive
Making all in pixops
make[4]: Nothing to be done for `all'.
Making all in gdk
make  all-recursive
Making all in x11
if /bin/sh ../../libtool --mode=compile /usr/bin/gcc-4.0 -DHAVE_CONFIG_H 
-I. -I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. 
-I../../gdk -I../../gdk -DG_DISABLE_CAST_CHECKS -D_REENTRANT 
-I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include 
-I/opt/local/include -I/opt/local/include/pango-1.0 
-I/opt/local/include/cairo -I/opt/local/include/pixman-1 
-I/opt/local/include/freetype2 -I/opt/local/include/libpng12 
-I/usr/X11/include      -I/opt/local/include -no-cpp-precomp -DX_LOCALE 
-I/usr/X11R6/include -DG_DISABLE_SINGLE_INCLUDES 
-DATK_DISABLE_SINGLE_INCLUDES -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES 
-DGTK_DISABLE_SINGLE_INCLUDES -I/opt/local/include -I/usr/X11/include 
  -DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops -fstrict-aliasing 
-Wall -MT gdkevents-x11.lo -MD -MP -MF ".deps/gdkevents-x11.Tpo" \
           -c -o gdkevents-x11.lo `test -f 'gdkevents-x11.c' || echo 
'./'`gdkevents-x11.c; \
         then mv -f ".deps/gdkevents-x11.Tpo" ".deps/gdkevents-x11.Plo"; \
         else rm -f ".deps/gdkevents-x11.Tpo"; exit 1; \
         fi
  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I../.. 
-DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. -I../../gdk -I../../gdk 
-DG_DISABLE_CAST_CHECKS -D_REENTRANT -I/opt/local/include/glib-2.0 
-I/opt/local/lib/glib-2.0/include -I/opt/local/include 
-I/opt/local/include/pango-1.0 -I/opt/local/include/cairo 
-I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 
-I/opt/local/include/libpng12 -I/usr/X11/include -I/opt/local/include 
-no-cpp-precomp -DX_LOCALE -I/usr/X11R6/include 
-DG_DISABLE_SINGLE_INCLUDES -DATK_DISABLE_SINGLE_INCLUDES 
-DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES 
-I/opt/local/include -I/usr/X11/include -DGDK_PIXBUF_DISABLE_DEPRECATED 
-O2 -funroll-loops -fstrict-aliasing -Wall -MT gdkevents-x11.lo -MD -MP 
-MF .deps/gdkevents-x11.Tpo -c gdkevents-x11.c  -fno-common -DPIC -o 
.libs/gdkevents-x11.o
gdkevents-x11.c: In function 'gdk_event_translate':
gdkevents-x11.c:2110: error: 'RRNotify' undeclared (first use in this 
function)
gdkevents-x11.c:2110: error: (Each undeclared identifier is reported 
only once
gdkevents-x11.c:2110: error: for each function it appears in.)
gdkevents-x11.c:2112: error: 'XRRNotifyEvent' undeclared (first use in 
this function)
gdkevents-x11.c:2112: error: 'notify' undeclared (first use in this 
function)
gdkevents-x11.c:2112: error: syntax error before ')' token
gdkevents-x11.c: In function 'gdk_x11_screen_get_window_manager_name':
gdkevents-x11.c:2721: warning: dereferencing type-punned pointer will 
break strict-aliasing rules
gdkevents-x11.c: In function 'gdk_x11_screen_supports_net_wm_hint':
gdkevents-x11.c:2821: warning: dereferencing type-punned pointer will 
break strict-aliasing rules
make[4]: *** [gdkevents-x11.lo] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

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



sh-3.2# port installed
The following ports are currently installed:
   apple-gcc42 @5531_0 (active)
   atk @1.24.0_0 (active)
   autoconf @2.63_0 (active)
   automake @1.10.1_0
   automake @1.10.2_0 (active)
   bison @2.4_1 (active)
   bzip2 @1.0.5_1 (active)
   cairo @1.8.4_0+macosx (active)
   clamav @0.94.1_0+darwin_i386
   clamav @0.94.2_0+darwin_i386 (active)
   expat @2.0.1_0 (active)
   fontconfig @2.6.0_0+macosx (active)
   fping @2.4b2_0 (active)
   freetype @2.3.7_3+macosx (active)
   gawk @3.1.6_0 (active)
   gd2 @2.0.35_2 (active)
   gettext @0.17_3 (active)
   glib2 @2.18.3_0+darwin_9 (active)
   gmp @4.2.4_0 (active)
   gnome-common @2.24.0_1 (active)
   gperf @3.0.3_0 (active)
   help2man @1.36.4_1 (active)
   intltool @0.40.5_0 (active)
   jasper @1.900.1_2+darwin_9 (active)
   jpeg @6b_3 (active)
   libiconv @1.12_0 (active)
   libpcap @1.0.0_0 (active)
   libpixman @0.12.0_1 (active)
   libpng @1.2.33_0 (active)
   libtool @1.5.26_0 (active)
   libxml2 @2.7.2_1+darwin_9 (active)
   libxslt @1.1.24_1+darwin_9 (active)
   m4 @1.4.12_1 (active)
   nagios @3.0.5_0 (active)
   nagios-plugins @1.4.13_1 (active)
   nawk @20070501_0 (active)
   ncurses @5.7_0 (active)
   ncursesw @5.7_0 (active)
   netcat @1.10_2 (active)
   nmap @4.76_0 (active)
   openssl @0.9.8i_0 (active)
   ossp-uuid @1.6.2_0 (active)
   p5-crypt-des @2.05_0 (active)
   p5-digest-hmac @1.01_2 (active)
   p5-digest-sha1 @2.11_0 (active)
   p5-locale-gettext @1.05_0 (active)
   p5-net-snmp @5.2.0_0 (active)
   p5-xml-parser @2.36_0 (active)
   pango @1.22.3_0 (active)
   pcre @7.8_1 (active)
   perl5.8 @5.8.8_3+darwin_9 (active)
   pkgconfig @0.23_1 (active)
   postgresql83 @8.3.5_0 (active)
   readline @5.2.012_1 (active)
   render @0.9.2_0 (active)
   shared-mime-info @0.51_0 (active)
   tiff @3.8.2_2+darwin_9+macosx (active)
   Xft2 @2.1.13_0 (active)
   xorg-renderproto @0.9.3_0 (active)
   xorg-xproto @7.0.14_1 (active)
   xrender @0.9.4_1+macosx (active)
   zlib @1.2.3_1
   zlib @1.2.3_2 (active)

From ram at macports.org  Wed Dec  3 13:16:07 2008
From: ram at macports.org (Adam Mercer)
Date: Wed, 3 Dec 2008 15:16:07 -0600
Subject: Dependency problem with swig / py25-scipy
In-Reply-To: <06C25DCB-A09A-4366-A95F-CDB89DF33284@ient.rwth-aachen.de>
References: <06C25DCB-A09A-4366-A95F-CDB89DF33284@ient.rwth-aachen.de>
Message-ID: <799406d60812031316t912d8a5qa61e95b157620050@mail.gmail.com>

On Wed, Dec 3, 2008 at 15:10, Mark Asbach <asbach at ient.rwth-aachen.de> wrote:

> I've got a problem with py25-scipy or with its dependencies to be precise.
>
> - At first, scipy seems to need gcc42 or gcc43 from macports which means
> that it needs to build a very huge package. Isn't it possible to build it
> with the Mac OS X developer tools version of gcc?

No, scipy needs a fortran compiler which is not provided in Xcode.
Also on Mac OS X the only fortran compiler that is supported in the
numpy distutils in gfortran therefore gcc42, or gcc43 is required.

Cheers

Adam

From rowue at digitalis.org  Wed Dec  3 15:39:03 2008
From: rowue at digitalis.org (=?ISO-8859-1?Q?Rolf_W=FCrdemann?=)
Date: Thu, 4 Dec 2008 00:39:03 +0100
Subject: gtk2 failing to build
In-Reply-To: <4936E0B5.2060401@enabled.com>
References: <4936E0B5.2060401@enabled.com>
Message-ID: <F4D35B33-1F37-4BB7-AE4C-DCD2843F11E1@digitalis.org>


Am 03.12.2008 um 20:40 schrieb Noah:

> any help is appreciated to figure out why gtk2 is failing to build.
>
> [...]
> gdkevents-x11.c: In function 'gdk_event_translate':
> gdkevents-x11.c:2110: error: 'RRNotify' undeclared (first use in  
> this function)
> gdkevents-x11.c:2110: error: (Each undeclared identifier is  
> reported only once
> gdkevents-x11.c:2110: error: for each function it appears in.)
> gdkevents-x11.c:2112: error: 'XRRNotifyEvent' undeclared (first use  
> in this function)
> gdkevents-x11.c:2112: error: 'notify' undeclared (first use in this  
> function)
> gdkevents-x11.c:2112: error: syntax error before ')' token
> gdkevents-x11.c: In function 'gdk_x11_screen_get_window_manager_name':
> gdkevents-x11.c:2721: warning: dereferencing type-punned pointer  
> will break strict-aliasing rules
> gdkevents-x11.c: In function 'gdk_x11_screen_supports_net_wm_hint':
> gdkevents-x11.c:2821: warning: dereferencing type-punned pointer  
> will break strict-aliasing rules
> make[4]: *** [gdkevents-x11.lo] Error 1
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> Error: The following dependencies failed to build: gtk2
> Error: Status 1 encountered during processing.

There is an ticket (#17360) on trac (http://trac.macports.org/ticket/ 
17360)
dealing with this issue (see also Known Leopard Problems)

However: installing XQuartz works against compile Bug but "my" Port
(gwyddion) crashes (Extension "RANDR" missing). I'll try compiling
gtk2 with variant quartz tomorrow - perhaps this will work.

(It seems there is a little to much change on X11 this times)

>
> [...]

reg's

	Rolf

--
			               Security is an illusion - Datasecurity twice
   Rolf W?rdemann    -   private: rowue at digitalis.org   -   office:  
rowue at crew-gmbh.de
   GnuPG fingerprint:          7383 348F 67D1 CD27 C90F DDD0 86A3  
31B6 67F0 D02F
   jabber: rowue at digitalis.org ECF127C7 EAB85F87 BC75ACB5 2EC646D4  
99211A31

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: Signierter Teil der Nachricht
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081204/78756824/attachment.bin>

From jeremyhu at macports.org  Wed Dec  3 17:16:23 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Wed, 3 Dec 2008 17:16:23 -0800
Subject: gtk2 failing to build
In-Reply-To: <4936E0B5.2060401@enabled.com>
References: <4936E0B5.2060401@enabled.com>
Message-ID: <4F93E796-6474-490E-A056-AF6F13CF05B9@macports.org>


On Dec 3, 2008, at 11:40, Noah wrote:

> gdkevents-x11.c: In function 'gdk_event_translate':
> gdkevents-x11.c:2110: error: 'RRNotify' undeclared (first use in  
> this function)
> gdkevents-x11.c:2110: error: (Each undeclared identifier is reported  
> only once
> gdkevents-x11.c:2110: error: for each function it appears in.)
> gdkevents-x11.c:2112: error: 'XRRNotifyEvent' undeclared (first use  
> in this function)
> gdkevents-x11.c:2112: error: 'notify' undeclared (first use in this  
> function)
> gdkevents-x11.c:2112: error: syntax error before ')' token

<snip />

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

<snip />

Try pulling in xorg-randrproto (you'll probably need libXrandr as  
well... which I just noticed isn't in macports yet...)

--Jeremy



From sthuebner at nym.hush.com  Thu Dec  4 01:18:35 2008
From: sthuebner at nym.hush.com (Stefan =?utf-8?Q?H=C3=BCbner?=)
Date: Thu, 04 Dec 2008 10:18:35 +0100
Subject: Installing privoxy failed
References: <gh5ijd$vo$1@ger.gmane.org> <49369D30.6050204@GmAiL.cOm>
Message-ID: <gh879b$k5a$1@ger.gmane.org>

Altoine Barker <ndiscreet at gmail.com> writes:

> Have you tried "port clean --all privoxy" and reran your upgrade to see
> if you get the same result? HTH

Frankly, that didn't help. I finally fixed it by manually removing
/opt/local/etc/privoxy.

I found out that 'sudo port -v install privoxy' was complaining about
modified local config files and it wouldn't install new config
files. /opt/local/etc/privoxy/config was modified, since I use Tor in
conjunction with Privoxy.

-Stefan


From lovecraftian at mac.com  Thu Dec  4 03:39:28 2008
From: lovecraftian at mac.com (Scott)
Date: Thu, 4 Dec 2008 11:39:28 +0000 (UTC)
Subject: MacPorts installs libraries I already have!
Message-ID: <loom.20081204T113828-529@post.gmane.org>

Hello.

I MacPorted a bunch of stuff yesterday (libpng, netpbm, and gocr), and
MacPorts added repeats of lib files, man pages, and other stuff I
ALREADY HAD in both my system-installed libraries and in
/usr/local/share!  What?s up with that?

For example, when I MacPorted gocr, it fetched and installed jpeg 6b_3
-- but I already have it.

Then it installed jasper 1.900.1_1+darwin_9.  Already have that, too.

Then it installed tiff.  Already have that, too.

Then it installed netpbm, which I had already installed myself --
using the ordinary ./config, make, install -- into /usr/local/share.

Two questions:

(1) Shouldn?t MacPorts LOOK to see if I have what it thinks it should
install?  Is there a way to MAKE MacPorts look first, and thus skip
duplicate files?

(2) Should I now delete ONE of the duplicate file-sets?  If so, which
should I kill -- the ordinary /usr/...  embedded set, or MacPorts'
/opt/... embedded set?

Thank you so much!




From lovecraftian at mac.com  Thu Dec  4 04:02:45 2008
From: lovecraftian at mac.com (Scott Heftler)
Date: Thu, 4 Dec 2008 12:02:45 +0000 (UTC)
Subject: MacPorts installs libraries I already have?
Message-ID: <loom.20081204T120219-175@post.gmane.org>

Hello.

I MacPorted a bunch of stuff yesterday (libpng, netpbm, and gocr), and
MacPorts added repeats of lib files, man pages, and other stuff I
ALREADY HAD in both my system-installed libraries and in
/usr/local/share!  What?s up with that?

For example, when I MacPorted gocr, it fetched and installed jpeg 6b_3
-- but I already have it.

Then it installed jasper 1.900.1_1+darwin_9.  Already have that, too.

Then it installed tiff.  Already have that, too.

Then it installed netpbm, which I had already installed myself --
using the ordinary ./config, make, install -- into /usr/local/share.

Two questions:

(1) Shouldn?t MacPorts LOOK to see if I have what it thinks it should
install?  Is there a way to MAKE MacPorts look first, and thus skip
duplicate files?

(2) Should I now delete ONE of the duplicate file-sets?  If so, which
should I kill -- the ordinary /usr/...  embedded set, or MacPorts'
/opt/... embedded set?

Thank you so much!




From milosh at macports.org  Thu Dec  4 04:10:14 2008
From: milosh at macports.org (Emmanuel Hainry)
Date: Thu, 4 Dec 2008 13:10:14 +0100
Subject: MacPorts installs libraries I already have!
In-Reply-To: <loom.20081204T113828-529@post.gmane.org>
References: <loom.20081204T113828-529@post.gmane.org>
Message-ID: <20081204121014.GA5523@weetamoe.loria.fr>

Citando Scott :
> Hello.
> 
> I MacPorted a bunch of stuff yesterday (libpng, netpbm, and gocr), and
> MacPorts added repeats of lib files, man pages, and other stuff I
> ALREADY HAD in both my system-installed libraries and in
> /usr/local/share!  What?s up with that?
> 
> For example, when I MacPorted gocr, it fetched and installed jpeg 6b_3
> -- but I already have it.
> 
> Then it installed jasper 1.900.1_1+darwin_9.  Already have that, too.
> 
> Then it installed tiff.  Already have that, too.
> 
> Then it installed netpbm, which I had already installed myself --
> using the ordinary ./config, make, install -- into /usr/local/share.
> 
> Two questions:
> 
> (1) Shouldn?t MacPorts LOOK to see if I have what it thinks it should
> install?  Is there a way to MAKE MacPorts look first, and thus skip
> duplicate files?

No. It is a choice. Apart from very specific cases, macports depends
only on things installed through macports.
http://trac.macports.org/wiki/FAQ#WhyisMacPortsusingitsownlibraries

> 
> (2) Should I now delete ONE of the duplicate file-sets?  If so, which
> should I kill -- the ordinary /usr/...  embedded set, or MacPorts'
> /opt/... embedded set?

If you want macports to keep on working, don't delete anything in
/opt/local by hand. To convince yourself, have a look at 'otool -L
/opt/local/bin/gocr' (not sure of the switch, not sure gocr installs a
binary named gocr, but however). You will see that it depends on the
libraries installed by macports.

Your /usr/local/ tree should be as empty as possible, if you need to
delete something, delete it. (be warned that things you installed using
those libraries will probably stop working, but you can probably install
them through macports).

Best,

Emmanuel

From andrea.damore at macports.org  Thu Dec  4 08:40:26 2008
From: andrea.damore at macports.org (Andrea D'Amore)
Date: Thu, 4 Dec 2008 17:40:26 +0100
Subject: MacPorts installs libraries I already have!
In-Reply-To: <loom.20081204T113828-529@post.gmane.org>
References: <loom.20081204T113828-529@post.gmane.org>
Message-ID: <411AC674-9AE1-4217-A8D2-36971D3A9E9E@macports.org>

On 04/dic/08, at 12:39, Scott wrote:

> What?s up with that?

You could check FAQ:
<http://trac.macports.org/wiki/FAQ#WillMacPortslinktosystemlibrariesratherthanitsown 
 >
and
<http://trac.macports.org/wiki/FAQ#WhyisMacPortsusingitsownlibraries>

By the way those anchors are _ugly_, we should consider switching to  
numbers instead, like "#2.5" and "#2.6" editing the [[PageOutline]]  
macro.

From kpreid at mac.com  Thu Dec  4 14:50:24 2008
From: kpreid at mac.com (Kevin Reid)
Date: Thu, 4 Dec 2008 17:50:24 -0500
Subject: MacPorts installs libraries I already have!
In-Reply-To: <411AC674-9AE1-4217-A8D2-36971D3A9E9E@macports.org>
References: <loom.20081204T113828-529@post.gmane.org>
	<411AC674-9AE1-4217-A8D2-36971D3A9E9E@macports.org>
Message-ID: <9A57D4A4-167B-4785-A4E7-69C08D94F58E@mac.com>

On Dec 4, 2008, at 11:40, Andrea D'Amore wrote:

> You could check FAQ:
> <http://trac.macports.org/wiki/FAQ#WillMacPortslinktosystemlibrariesratherthanitsown 
> >
> and
> <http://trac.macports.org/wiki/FAQ#WhyisMacPortsusingitsownlibraries>
>
> By the way those anchors are _ugly_, we should consider switching to  
> numbers instead, like "#2.5" and "#2.6" editing the [[PageOutline]]  
> macro.

Using numbers is a bad idea, unless the document is never modified;  
existing links break whenever items are added, removed, or reordered.

I recommend creating short identifiers for each heading separate from  
any numbering *or* title.

(The Subversion FAQ is an example of this style:
   <http://subversion.tigris.org/faq.html>)

-- 
Kevin Reid                            <http://homepage.mac.com/kpreid/>



From ryandesign at macports.org  Thu Dec  4 19:26:29 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 4 Dec 2008 21:26:29 -0600
Subject: MacPorts installs libraries I already have!
In-Reply-To: <9A57D4A4-167B-4785-A4E7-69C08D94F58E@mac.com>
References: <loom.20081204T113828-529@post.gmane.org>
	<411AC674-9AE1-4217-A8D2-36971D3A9E9E@macports.org>
	<9A57D4A4-167B-4785-A4E7-69C08D94F58E@mac.com>
Message-ID: <94D83DF8-5A0C-4B91-A961-DE2F03DDED7D@macports.org>


On Dec 4, 2008, at 16:50, Kevin Reid wrote:

> On Dec 4, 2008, at 11:40, Andrea D'Amore wrote:
>
>> You could check FAQ:
>> <http://trac.macports.org/wiki/ 
>> FAQ#WillMacPortslinktosystemlibrariesratherthanitsown>
>> and
>> <http://trac.macports.org/wiki/FAQ#WhyisMacPortsusingitsownlibraries>
>>
>> By the way those anchors are _ugly_, we should consider switching  
>> to numbers instead, like "#2.5" and "#2.6" editing the  
>> [[PageOutline]] macro.
>
> Using numbers is a bad idea, unless the document is never modified;  
> existing links break whenever items are added, removed, or reordered.
>
> I recommend creating short identifiers for each heading separate  
> from any numbering *or* title.
>
> (The Subversion FAQ is an example of this style:
>   <http://subversion.tigris.org/faq.html>)

Yes, I would love to have cleaner anchors like the Subversion FAQ,  
however the Subversion FAQ is a manually crafted HTML document; it  
was not made using Trac. How can we do the same with Trac syntax?




From perry at macports.org  Thu Dec  4 20:45:43 2008
From: perry at macports.org (Perry Lee)
Date: Thu, 04 Dec 2008 20:45:43 -0800
Subject: MacPorts installs libraries I already have!
In-Reply-To: <94D83DF8-5A0C-4B91-A961-DE2F03DDED7D@macports.org>
References: <loom.20081204T113828-529@post.gmane.org>	<411AC674-9AE1-4217-A8D2-36971D3A9E9E@macports.org>	<9A57D4A4-167B-4785-A4E7-69C08D94F58E@mac.com>
	<94D83DF8-5A0C-4B91-A961-DE2F03DDED7D@macports.org>
Message-ID: <4938B1F7.1050707@macports.org>

Ryan Schmidt wrote:
> Yes, I would love to have cleaner anchors like the Subversion FAQ,
> however the Subversion FAQ is a manually crafted HTML document; it was
> not made using Trac. How can we do the same with Trac syntax?

This syntax appears to work (at least in preview mode):

=== Explicit id === #using-explicit-id-in-heading

I found the info here: http://trac.edgewall.org/wiki/WikiFormatting

From blb at macports.org  Thu Dec  4 21:20:07 2008
From: blb at macports.org (Bryan Blackburn)
Date: Thu, 4 Dec 2008 22:20:07 -0700
Subject: MacPorts installs libraries I already have!
In-Reply-To: <4938B1F7.1050707@macports.org>
References: <loom.20081204T113828-529@post.gmane.org>
	<411AC674-9AE1-4217-A8D2-36971D3A9E9E@macports.org>
	<9A57D4A4-167B-4785-A4E7-69C08D94F58E@mac.com>
	<94D83DF8-5A0C-4B91-A961-DE2F03DDED7D@macports.org>
	<4938B1F7.1050707@macports.org>
Message-ID: <20081205052007.GJ1193@ninagal.withay.com>

On Thu, Dec 04, 2008 at 08:45:43PM -0800, Perry Lee said:
> Ryan Schmidt wrote:
> > Yes, I would love to have cleaner anchors like the Subversion FAQ,
> > however the Subversion FAQ is a manually crafted HTML document; it was
> > not made using Trac. How can we do the same with Trac syntax?
> 
> This syntax appears to work (at least in preview mode):
> 
> === Explicit id === #using-explicit-id-in-heading

That works nicely, but of course we've linked to many of those sections at
this point (I know I have many times in tickets, to fetch failures and Tcl
env bug stuff at least) so changing them will break those links and might
confuse people.

For new sections, it definitely would make sense to use shorter anchors.

Bryan


> 
> I found the info here: http://trac.edgewall.org/wiki/WikiFormatting

From andrea.damore at macports.org  Fri Dec  5 01:08:29 2008
From: andrea.damore at macports.org (Andrea D'Amore)
Date: Fri, 5 Dec 2008 10:08:29 +0100
Subject: MacPorts installs libraries I already have!
In-Reply-To: <9A57D4A4-167B-4785-A4E7-69C08D94F58E@mac.com>
References: <loom.20081204T113828-529@post.gmane.org>
	<411AC674-9AE1-4217-A8D2-36971D3A9E9E@macports.org>
	<9A57D4A4-167B-4785-A4E7-69C08D94F58E@mac.com>
Message-ID: <158A00FE-7929-4259-A8B8-B6B72CE3A408@macports.org>

On 04/dic/08, at 23:50, Kevin Reid wrote:

> Using numbers is a bad idea, unless the document is never modified;  
> existing links break whenever items are added, removed, or reordered.

But I didn't mean to manually add numbers, I was wondering about  
changing a bit the PageOutline macro, after all it already have to  
parse the page content before creating ToC so it could as well number  
items.

From tim.visher at gmail.com  Fri Dec  5 04:16:56 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Fri, 5 Dec 2008 07:16:56 -0500
Subject: Generating a list of all installed software (or something like that).
Message-ID: <c115fd3c0812050416k48ddb28s171d90d452d67557@mail.gmail.com>

Hello Everyone,

I'd be interested in generating a complete list of all software I have
installed through MacPorts so that I don't have to back up my
installation in case of a hard drive failure.  Basic use case would be
that if my disk fails, I just download MacPorts again, and then run
this script through it and after awhile I get my exact install back
the way I had it n-days before the crash.  Any way to do this?

This has been inspired by APTonCD's ability to generate a list of
everything you've installed through apt for various purposes, if you
want to know an analogue.

-- 

In Christ,

Timmy V.

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

From macports at truenix.net  Fri Dec  5 04:55:37 2008
From: macports at truenix.net (Mikael Gripenstedt)
Date: Fri, 5 Dec 2008 13:55:37 +0100
Subject: Generating a list of all installed software (or something like
	that).
In-Reply-To: <c115fd3c0812050416k48ddb28s171d90d452d67557@mail.gmail.com>
References: <c115fd3c0812050416k48ddb28s171d90d452d67557@mail.gmail.com>
Message-ID: <42789608-359C-455A-8A90-EB2395442E20@truenix.net>

On Dec 5, 2008, at 13:16 , Tim Visher wrote:

> Hello Everyone,
>
> I'd be interested in generating a complete list of all software I have
> installed through MacPorts so that I don't have to back up my
> installation in case of a hard drive failure.  Basic use case would be
> that if my disk fails, I just download MacPorts again, and then run
> this script through it and after awhile I get my exact install back
> the way I had it n-days before the crash.  Any way to do this?
>
> This has been inspired by APTonCD's ability to generate a list of
> everything you've installed through apt for various purposes, if you
> want to know an analogue.
>
> --  
>
> In Christ,
>
> Timmy V.
>
> http://burningones.com/
> http://five.sentenc.es/ - Spend less time on e-mail

Hi Timmy,

port list installed

Will give you a list of installed software. Is this what you were  
looking for?

Mikael Gripenstedt
http://truenix.se - another way of doing IT!




From afb at macports.org  Fri Dec  5 05:04:36 2008
From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=)
Date: Fri, 5 Dec 2008 14:04:36 +0100
Subject: Generating a list of all installed software (or something like
	that).
In-Reply-To: <c115fd3c0812050416k48ddb28s171d90d452d67557@mail.gmail.com>
References: <c115fd3c0812050416k48ddb28s171d90d452d67557@mail.gmail.com>
Message-ID: <77BF5368-F515-4772-AF85-5E8F230ADD5E@macports.org>

Tim Visher wrote:

> I'd be interested in generating a complete list of all software I have
> installed through MacPorts so that I don't have to back up my
> installation in case of a hard drive failure.  Basic use case would be
> that if my disk fails, I just download MacPorts again, and then run
> this script through it and after awhile I get my exact install back
> the way I had it n-days before the crash.  Any way to do this?

sudo port archive installed

You'd need to enable "archive mode" first though (in macports.conf).
And if you had "auto clean" enabled, probably rebuild everything too.

If you don't want to save the binaries, but only the list of what
you had installed then save this output to a file for later use:

port installed > installed.txt

>
> This has been inspired by APTonCD's ability to generate a list of
> everything you've installed through apt for various purposes, if you
> want to know an analogue.

There's some DEB building support as well, but it is pretty flaky...
(and you can't install .deb packages so that they use the registry)

--anders


From jmr at macports.org  Fri Dec  5 05:37:20 2008
From: jmr at macports.org (Joshua Root)
Date: Sat, 06 Dec 2008 00:37:20 +1100
Subject: Generating a list of all installed software (or something like
	that).
In-Reply-To: <42789608-359C-455A-8A90-EB2395442E20@truenix.net>
References: <c115fd3c0812050416k48ddb28s171d90d452d67557@mail.gmail.com>
	<42789608-359C-455A-8A90-EB2395442E20@truenix.net>
Message-ID: <49392E90.60505@macports.org>

Mikael Gripenstedt wrote:
> On Dec 5, 2008, at 13:16 , Tim Visher wrote:
> 
>> Hello Everyone,
>>
>> I'd be interested in generating a complete list of all software I have
>> installed through MacPorts so that I don't have to back up my
>> installation in case of a hard drive failure.  Basic use case would be
>> that if my disk fails, I just download MacPorts again, and then run
>> this script through it and after awhile I get my exact install back
>> the way I had it n-days before the crash.  Any way to do this?
>>
>> This has been inspired by APTonCD's ability to generate a list of
>> everything you've installed through apt for various purposes, if you
>> want to know an analogue.
>>
>> -- 
>> In Christ,
>>
>> Timmy V.
>>
>> http://burningones.com/
>> http://five.sentenc.es/ - Spend less time on e-mail
> 
> Hi Timmy,
> 
> port list installed
> 
> Will give you a list of installed software. Is this what you were
> looking for?

You actually want 'port installed' rather than 'port list installed',
because 'port list' shows you the version in the index, which may not be
the same as what's installed.

- Josh

From tim.visher at gmail.com  Fri Dec  5 06:04:40 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Fri, 5 Dec 2008 09:04:40 -0500
Subject: Generating a list of all installed software (or something like
	that).
In-Reply-To: <49392E90.60505@macports.org>
References: <c115fd3c0812050416k48ddb28s171d90d452d67557@mail.gmail.com>
	<42789608-359C-455A-8A90-EB2395442E20@truenix.net>
	<49392E90.60505@macports.org>
Message-ID: <c115fd3c0812050604t14104518uaddcdac22733b379@mail.gmail.com>

On Fri, Dec 5, 2008 at 8:37 AM, Joshua Root <jmr at macports.org> wrote:
> Mikael Gripenstedt wrote:
>> On Dec 5, 2008, at 13:16 , Tim Visher wrote:
>>
>>> Hello Everyone,
>>>
>>> I'd be interested in generating a complete list of all software I have
>>> installed through MacPorts so that I don't have to back up my
>>> installation in case of a hard drive failure.  Basic use case would be
>>> that if my disk fails, I just download MacPorts again, and then run
>>> this script through it and after awhile I get my exact install back
>>> the way I had it n-days before the crash.  Any way to do this?
>>>
>>> This has been inspired by APTonCD's ability to generate a list of
>>> everything you've installed through apt for various purposes, if you
>>> want to know an analogue.
>>>
>>> --
>>> In Christ,
>>>
>>> Timmy V.
>>>
>>> http://burningones.com/
>>> http://five.sentenc.es/ - Spend less time on e-mail
>>
>> Hi Timmy,
>>
>> port list installed
>>
>> Will give you a list of installed software. Is this what you were
>> looking for?
>
> You actually want 'port installed' rather than 'port list installed',
> because 'port list' shows you the version in the index, which may not be
> the same as what's installed.
>
> - Josh
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>

Wow do I feel sheepish.  I can't believe I couldn't think to do that
all by me'lonesome... :\

Thanks a lot everyone!

-- 

In Christ,

Timmy V.

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

From neil at voidfx.net  Fri Dec  5 08:41:17 2008
From: neil at voidfx.net (Neil)
Date: Fri, 5 Dec 2008 11:41:17 -0500
Subject: Generating a list of all installed software (or something like
	that).
In-Reply-To: <c115fd3c0812050604t14104518uaddcdac22733b379@mail.gmail.com>
References: <c115fd3c0812050416k48ddb28s171d90d452d67557@mail.gmail.com>
	<42789608-359C-455A-8A90-EB2395442E20@truenix.net>
	<49392E90.60505@macports.org>
	<c115fd3c0812050604t14104518uaddcdac22733b379@mail.gmail.com>
Message-ID: <D5407364-478C-4294-9F88-08D1BBF30CAE@voidfx.net>


On 5 Dec 2008, at 09:04, Tim Visher wrote:

> On Fri, Dec 5, 2008 at 8:37 AM, Joshua Root <jmr at macports.org> wrote:
>> Mikael Gripenstedt wrote:
>>> On Dec 5, 2008, at 13:16 , Tim Visher wrote:
>>>
>>>> Hello Everyone,
>>>>
>>>> I'd be interested in generating a complete list of all software I  
>>>> have
>>>> installed through MacPorts so that I don't have to back up my
>>>> installation in case of a hard drive failure.  Basic use case  
>>>> would be
>>>> that if my disk fails, I just download MacPorts again, and then run
>>>> this script through it and after awhile I get my exact install back
>>>> the way I had it n-days before the crash.  Any way to do this?
>>>>
>>>> This has been inspired by APTonCD's ability to generate a list of
>>>> everything you've installed through apt for various purposes, if  
>>>> you
>>>> want to know an analogue.
>>>>
>>>> --
>>>> In Christ,
>>>>
>>>> Timmy V.
>>>>
>>>> http://burningones.com/
>>>> http://five.sentenc.es/ - Spend less time on e-mail
>>>
>>> Hi Timmy,
>>>
>>> port list installed
>>>
>>> Will give you a list of installed software. Is this what you were
>>> looking for?
>>
>> You actually want 'port installed' rather than 'port list installed',
>> because 'port list' shows you the version in the index, which may  
>> not be
>> the same as what's installed.
>>
>> - Josh
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>
>
> Wow do I feel sheepish.  I can't believe I couldn't think to do that
> all by me'lonesome... :\
>
> Thanks a lot everyone!

(Almost) totally untested:
$ port install | sed 's/(active)$//' | sed 's/^/install/' | grep -v  
'The following ports are currently installed:' > my_ports.txt
<trash your partition, reformat, reinstall>
$ port -F my_ports.txt

Break down of the first line:
1. Get list of ports.
2. Strip out "(active)"
3. Prefix each line with "install" (so port -F knows what action to do  
with each port)
4. Remove the line at the top: 'The following ports are currently  
installed:'
5. Send to file.

Caveats:
1. If you, like me, always want the most recent port installed, not a  
specific one, then you can drop | sed 's/@[^+]*//'
  | into the chain of seds in line 1, and that should filter out all  
the version information (and still leave variants).
2. This list contains things that were installed as dependencies.  If  
dependencies have been eliminated since you installed stuff last,  
they'll get installed again, even though this time they're not  
needed.  MacPorts is currently working towards remedying that situation.

Personally, I just have a textfile with the ports and variants I want  
in it.

Hope it helps.

-N.

From ryandesign at macports.org  Fri Dec  5 13:31:32 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 5 Dec 2008 15:31:32 -0600
Subject: Generating a list of all installed software (or something like
	that).
In-Reply-To: <D5407364-478C-4294-9F88-08D1BBF30CAE@voidfx.net>
References: <c115fd3c0812050416k48ddb28s171d90d452d67557@mail.gmail.com>
	<42789608-359C-455A-8A90-EB2395442E20@truenix.net>
	<49392E90.60505@macports.org>
	<c115fd3c0812050604t14104518uaddcdac22733b379@mail.gmail.com>
	<D5407364-478C-4294-9F88-08D1BBF30CAE@voidfx.net>
Message-ID: <55EB8288-0504-454F-B09A-6BDB97762C5A@macports.org>

On Dec 5, 2008, at 10:41, Neil wrote:

> On 5 Dec 2008, at 09:04, Tim Visher wrote:
>
>> On Fri, Dec 5, 2008 at 8:37 AM, Joshua Root wrote:
>>
>>> Mikael Gripenstedt wrote:
>>>
>>>> On Dec 5, 2008, at 13:16 , Tim Visher wrote:
>>>>
>>>>> I'd be interested in generating a complete list of all software  
>>>>> I have
>>>>> installed through MacPorts so that I don't have to back up my
>>>>> installation in case of a hard drive failure.  Basic use case  
>>>>> would be
>>>>> that if my disk fails, I just download MacPorts again, and then  
>>>>> run
>>>>> this script through it and after awhile I get my exact install  
>>>>> back
>>>>> the way I had it n-days before the crash.  Any way to do this?
>>>>>
>>>>> This has been inspired by APTonCD's ability to generate a list of
>>>>> everything you've installed through apt for various purposes,  
>>>>> if you
>>>>> want to know an analogue.
>>>>
>>>> port list installed
>>>>
>>>> Will give you a list of installed software. Is this what you were
>>>> looking for?
>>>
>>> You actually want 'port installed' rather than 'port list  
>>> installed',
>>> because 'port list' shows you the version in the index, which may  
>>> not be
>>> the same as what's installed.
>>
>> Wow do I feel sheepish.  I can't believe I couldn't think to do that
>> all by me'lonesome... :\
>
> (Almost) totally untested:
> $ port install | sed 's/(active)$//' | sed 's/^/install/' | grep -v  
> 'The following ports are currently installed:' > my_ports.txt

I'm sure you meant "port installed" as the first bit on that line.

> <trash your partition, reformat, reinstall>
> $ port -F my_ports.txt

Probably prefaced by "sudo".

> Break down of the first line:
> 1. Get list of ports.
> 2. Strip out "(active)"
> 3. Prefix each line with "install" (so port -F knows what action to  
> do with each port)
> 4. Remove the line at the top: 'The following ports are currently  
> installed:'

Using "sed 1d" to remove the header line is shorter and allows for  
the specific message to be changed either through localization or by  
a wording change in some future version of MacPorts.

> 5. Send to file.
>
> Caveats:
> 1. If you, like me, always want the most recent port installed, not  
> a specific one, then you can drop | sed 's/@[^+]*//'
>  | into the chain of seds in line 1, and that should filter out all  
> the version information (and still leave variants).
> 2. This list contains things that were installed as dependencies.   
> If dependencies have been eliminated since you installed stuff  
> last, they'll get installed again, even though this time they're  
> not needed.  MacPorts is currently working towards remedying that  
> situation.
>
> Personally, I just have a textfile with the ports and variants I  
> want in it.

Well, there are several big problems with this method.

First, MacPorts cannot install specific versions of ports, only the  
version specified in your portfiles. Any version number specified in  
your install command is totally ignored. Also you can only have one  
version of a port installed at a time. So if you had php5 @5.2.5_0,  
and then at some point you used "sudo port upgrade php5" which  
upgraded you to php5 @5.2.6_2 (and left php5 @5.2.5_0 around,  
deactivated), and now you wanted to trash your drive and reinstall  
those ports exactly, you can't, because MacPorts doesn't have a  
command to let you do that. You can only install the current version  
of php5, which as of yesterday is php5 @5.2.7_0. There are  
instructions for how to manually get back to an older version if  
that's really necessary:

http://trac.macports.org/wiki/howto/InstallingOlderPort

Second, if you just install ports in alphabetical order, you're  
likely to get the wrong variants of things installed, as later ports  
are installed automatically as dependencies of earlier ones. For  
example, I have the subversion port installed with the +mod_dav_svn  
and +tools variants. But subversion is a build dependency of ffmpeg.  
ffmpeg appears in the alphabetically-sorted list of ports before  
subversion. So as soon as you try to install ffmpeg (on Tiger or  
earlier, on which Apple doesn't provide the svn program), it will  
first install subversion -- with no variants selected. When you later  
come to subversion in your list of installed ports, it will be  
rebuilt with the +mod_dav_svn +tools variants but it won't be able to  
activate it because another version is already active. So what you  
really need to do is install the ports in dependency order, where the  
first ports to be installed are the ones that don't have any  
dependencies, then you install ports that depend on the ports you've  
already installed, and so on until all ports are installed. Basically  
you reinvent the entire MacPorts dependency engine.



From neil at voidfx.net  Fri Dec  5 13:47:59 2008
From: neil at voidfx.net (Neil)
Date: Fri, 5 Dec 2008 16:47:59 -0500
Subject: Generating a list of all installed software (or something like
	that).
In-Reply-To: <55EB8288-0504-454F-B09A-6BDB97762C5A@macports.org>
References: <c115fd3c0812050416k48ddb28s171d90d452d67557@mail.gmail.com>
	<42789608-359C-455A-8A90-EB2395442E20@truenix.net>
	<49392E90.60505@macports.org>
	<c115fd3c0812050604t14104518uaddcdac22733b379@mail.gmail.com>
	<D5407364-478C-4294-9F88-08D1BBF30CAE@voidfx.net>
	<55EB8288-0504-454F-B09A-6BDB97762C5A@macports.org>
Message-ID: <409E7D7B-3E57-4D57-9E74-C6CA077F07B3@voidfx.net>


On 5 Dec 2008, at 16:31, Ryan Schmidt wrote:

> On Dec 5, 2008, at 10:41, Neil wrote:
>
>> On 5 Dec 2008, at 09:04, Tim Visher wrote:
>>
>>> On Fri, Dec 5, 2008 at 8:37 AM, Joshua Root wrote:
>>>
>>>> Mikael Gripenstedt wrote:
>>>>
>>>>> On Dec 5, 2008, at 13:16 , Tim Visher wrote:
>>>>>
>>>>>> I'd be interested in generating a complete list of all software  
>>>>>> I have
>>>>>> installed through MacPorts so that I don't have to back up my
>>>>>> installation in case of a hard drive failure.  Basic use case  
>>>>>> would be
>>>>>> that if my disk fails, I just download MacPorts again, and then  
>>>>>> run
>>>>>> this script through it and after awhile I get my exact install  
>>>>>> back
>>>>>> the way I had it n-days before the crash.  Any way to do this?
>>>>>>
>>>>>> This has been inspired by APTonCD's ability to generate a list of
>>>>>> everything you've installed through apt for various purposes,  
>>>>>> if you
>>>>>> want to know an analogue.
>>>>>
>>>>> port list installed
>>>>>
>>>>> Will give you a list of installed software. Is this what you were
>>>>> looking for?
>>>>
>>>> You actually want 'port installed' rather than 'port list  
>>>> installed',
>>>> because 'port list' shows you the version in the index, which may  
>>>> not be
>>>> the same as what's installed.
>>>
>>> Wow do I feel sheepish.  I can't believe I couldn't think to do that
>>> all by me'lonesome... :\
>>
>> (Almost) totally untested:
>> $ port install | sed 's/(active)$//' | sed 's/^/install/' | grep -v  
>> 'The following ports are currently installed:' > my_ports.txt
>
> I'm sure you meant "port installed" as the first bit on that line.
>
>> <trash your partition, reformat, reinstall>
>> $ port -F my_ports.txt
>
> Probably prefaced by "sudo".
>
>> Break down of the first line:
>> 1. Get list of ports.
>> 2. Strip out "(active)"
>> 3. Prefix each line with "install" (so port -F knows what action to  
>> do with each port)
>> 4. Remove the line at the top: 'The following ports are currently  
>> installed:'
>
> Using "sed 1d" to remove the header line is shorter and allows for  
> the specific message to be changed either through localization or by  
> a wording change in some future version of MacPorts.

Ah, I didn't know; I actually have barely ever used sed before this  
(and after this, I suppose).

>> 5. Send to file.
>>
>> Caveats:
>> 1. If you, like me, always want the most recent port installed, not  
>> a specific one, then you can drop | sed 's/@[^+]*//'
>> | into the chain of seds in line 1, and that should filter out all  
>> the version information (and still leave variants).
>> 2. This list contains things that were installed as dependencies.   
>> If dependencies have been eliminated since you installed stuff  
>> last, they'll get installed again, even though this time they're  
>> not needed.  MacPorts is currently working towards remedying that  
>> situation.
>>
>> Personally, I just have a textfile with the ports and variants I  
>> want in it.
>
> Well, there are several big problems with this method.
>
> First, MacPorts cannot install specific versions of ports, only the  
> version specified in your portfiles. Any version number specified in  
> your install command is totally ignored. Also you can only have one  
> version of a port installed at a time. So if you had php5 @5.2.5_0,  
> and then at some point you used "sudo port upgrade php5" which  
> upgraded you to php5 @5.2.6_2 (and left php5 @5.2.5_0 around,  
> deactivated), and now you wanted to trash your drive and reinstall  
> those ports exactly, you can't, because MacPorts doesn't have a  
> command to let you do that. You can only install the current version  
> of php5, which as of yesterday is php5 @5.2.7_0. There are  
> instructions for how to manually get back to an older version if  
> that's really necessary:
>
> http://trac.macports.org/wiki/howto/InstallingOlderPort
>
> Second, if you just install ports in alphabetical order, you're  
> likely to get the wrong variants of things installed, as later ports  
> are installed automatically as dependencies of earlier ones. For  
> example, I have the subversion port installed with the +mod_dav_svn  
> and +tools variants. But subversion is a build dependency of ffmpeg.  
> ffmpeg appears in the alphabetically-sorted list of ports before  
> subversion. So as soon as you try to install ffmpeg (on Tiger or  
> earlier, on which Apple doesn't provide the svn program), it will  
> first install subversion -- with no variants selected. When you  
> later come to subversion in your list of installed ports, it will be  
> rebuilt with the +mod_dav_svn +tools variants but it won't be able  
> to activate it because another version is already active. So what  
> you really need to do is install the ports in dependency order,  
> where the first ports to be installed are the ones that don't have  
> any dependencies, then you install ports that depend on the ports  
> you've already installed, and so on until all ports are installed.  
> Basically you reinvent the entire MacPorts dependency engine.
>

Thank you for those additions.  I assume you mean with the semi- 
automated I proposed above, not my little by-hand list.

I do think the custom list is the way to go (that's why I use it),  
though it's easy to forget to add something to the list when you run  
the port install (then again, if I forget something, it's not the end  
of the world, I can always reinstall it when I remember, and if I  
forgot it probably wasn't that important in the first place).  But I  
thought I'd offer an alternative, and if you're going to make a by- 
hand list, it's a good place to start, I think.

I always want the most recent, so I toss the version numbers and let  
ports do its thing with them.  And I follow some rough rules for how I  
order items on the list: languages (eg. perl, python, ruby, etc.),  
then basically everything I picked variants for, standalone programs,  
and then modules (eg. py25-readline).  It has worked out pretty  
decently for me so far.


From frstan at bellsouth.net  Fri Dec  5 14:58:08 2008
From: frstan at bellsouth.net (William Davis)
Date: Fri, 5 Dec 2008 17:58:08 -0500
Subject: py26-pyobjc2
Message-ID: <96A12368-9BFB-4681-A34A-D036AA7DF5CD@bellsouth.net>

py26-py0bjc2:

raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (py2app 0.3.6 (/opt/local/Library/ 
Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages),  
Requirement.parse('py2app>=0.4.0'))

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

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

Mundus vult decepi, ego non


From jmr at macports.org  Fri Dec  5 15:17:41 2008
From: jmr at macports.org (Joshua Root)
Date: Sat, 06 Dec 2008 10:17:41 +1100
Subject: py26-pyobjc2
In-Reply-To: <96A12368-9BFB-4681-A34A-D036AA7DF5CD@bellsouth.net>
References: <96A12368-9BFB-4681-A34A-D036AA7DF5CD@bellsouth.net>
Message-ID: <4939B695.8070904@macports.org>

William Davis wrote:
> py26-py0bjc2:
> 
> raise VersionConflict(dist,req) # XXX put more info here
> pkg_resources.VersionConflict: (py2app 0.3.6
> (/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages),
> Requirement.parse('py2app>=0.4.0'))
> 
> Warning: the following items did not execute (for py26-pyobjc2):
> org.macports.activate org.macports.build org.macports.destroot
> org.macports.install
> Error: Status 1 encountered during processing.
> macintosh:~ frstan$

py26-pyobjc2 depends on port:py26-py2app-devel, which is version 0.4.2,
so I can only assume that py26-py2app-devel is inactive, and you're
using MP 1.6 so it doesn't notice.

- Josh

From jmr at macports.org  Fri Dec  5 15:19:27 2008
From: jmr at macports.org (Joshua Root)
Date: Sat, 06 Dec 2008 10:19:27 +1100
Subject: [macports-mgr] Macports issue
In-Reply-To: <C55F6695.19%davidfoster.studio@virgin.net>
References: <C55F6695.19%davidfoster.studio@virgin.net>
Message-ID: <4939B6FF.3080805@macports.org>

d f wrote:
> Hey
> I can't get ghostscript installed after putting macports onto a powerbook
> 10.4.11
> Get an error type 1
> I followed some advice on CADP website about setting $PATH but no joy when
> typing  sudo install ghostscript
> Any ideas?
> Can I configure the installation to use a locally downloaded ghostscript
> package (and ghostview)
> My aims are "simple" - to be able to live preview direct postscript -
> without burning trees on my old laserwriter II - and maybe later on my rip
> to a designjet
> Any help most gratefully received.
> 
> Also happy to join the community if any help.
> Cheers
> 
> David

I'm forwarding this to the macports-users list, which is the appropriate
place for this sort of thing.

- Josh

From frstan at bellsouth.net  Fri Dec  5 15:40:01 2008
From: frstan at bellsouth.net (William Davis)
Date: Fri, 5 Dec 2008 18:40:01 -0500
Subject: py26-pyobjc2
In-Reply-To: <4939B695.8070904@macports.org>
References: <96A12368-9BFB-4681-A34A-D036AA7DF5CD@bellsouth.net>
	<4939B695.8070904@macports.org>
Message-ID: <6730CC78-8A06-4BFF-A47C-2F81E6ED3ED3@bellsouth.net>


On Dec 5, 2008, at 6:17 PM, Joshua Root wrote:

> William Davis wrote:
>> py26-py0bjc2:
>>
>> raise VersionConflict(dist,req) # XXX put more info here
>> pkg_resources.VersionConflict: (py2app 0.3.6
>> (/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
>> python2.6/site-packages),
>> Requirement.parse('py2app>=0.4.0'))
>>
>> Warning: the following items did not execute (for py26-pyobjc2):
>> org.macports.activate org.macports.build org.macports.destroot
>> org.macports.install
>> Error: Status 1 encountered during processing.
>> macintosh:~ frstan$
>
> py26-pyobjc2 depends on port:py26-py2app-devel, which is version  
> 0.4.2,
> so I can only assume that py26-py2app-devel is inactive, and you're
> using MP 1.6 so it doesn't notice.
>
> - Josh

good diagnosis
However merely deactivating py26-py2app and activating py-py2app-devel  
wasnt enough.  The error recurred.  After uninstalling py26-py2app,
the error still remains the same.

So it appears this wont work on mp version 1.6

The full error mesg is:
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_python_py26-pyobjc2/work/pyobjc-core" && / 
opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin/ 
python2.6 setup.py --no-user-cfg build'
Traceback (most recent call last):
   File "setup.py", line 324, in <module>
     '': ['*.bridgesupport'],
   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/ 
lib/python2.6/distutils/core.py", line 113, in setup
     _setup_distribution = dist = klass(attrs)
   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/ 
lib/python2.6/site-packages/setuptools/dist.py", line 219, in __init__
     self.fetch_build_eggs(attrs.pop('setup_requires'))
   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/ 
lib/python2.6/site-packages/setuptools/dist.py", line 243, in  
fetch_build_eggs
     parse_requirements(requires), installer=self.fetch_build_egg
   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/ 
lib/python2.6/site-packages/pkg_resources.py", line 528, in resolve
     raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (py2app 0.3.6 (/opt/local/Library/ 
Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages),  
Requirement.parse('py2app>=0.4.0'))
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_python_py26-pyobjc2/work/pyobjc-core" && / 
opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin/ 
python2.6 setup.py --no-user-cfg build " returned error 1
Command output: Traceback (most recent call last):
   File "setup.py", line 324, in <module>
     '': ['*.bridgesupport'],
   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/ 
lib/python2.6/distutils/core.py", line 113, in setup
     _setup_distribution = dist = klass(attrs)
   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/ 
lib/python2.6/site-packages/setuptools/dist.py", line 219, in __init__
     self.fetch_build_eggs(attrs.pop('setup_requires'))
   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/ 
lib/python2.6/site-packages/setuptools/dist.py", line 243, in  
fetch_build_eggs
     parse_requirements(requires), installer=self.fetch_build_egg
   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/ 
lib/python2.6/site-packages/pkg_resources.py", line 528, in resolve
     raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (py2app 0.3.6 (/opt/local/Library/ 
Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages),  
Requirement.parse('py2app>=0.4.0'))

Warning: the following items did not execute (for py26-pyobjc2):  
org.macports.activate org.macports.build org.macports.destroot  
org.macports.install
Error: Status 1 encountered during processing.



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

Mundus vult decepi, ego non


From frstan at bellsouth.net  Fri Dec  5 15:45:54 2008
From: frstan at bellsouth.net (William Davis)
Date: Fri, 5 Dec 2008 18:45:54 -0500
Subject: py26-pyobjc2
In-Reply-To: <4939B695.8070904@macports.org>
References: <96A12368-9BFB-4681-A34A-D036AA7DF5CD@bellsouth.net>
	<4939B695.8070904@macports.org>
Message-ID: <19051CF2-66CE-43DF-8F3F-0E6991554D86@bellsouth.net>


On Dec 5, 2008, at 6:17 PM, Joshua Root wrote:

> William Davis wrote:
>> py26-py0bjc2:
>>
>> raise VersionConflict(dist,req) # XXX put more info here
>> pkg_resources.VersionConflict: (py2app 0.3.6
>> (/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
>> python2.6/site-packages),
>> Requirement.parse('py2app>=0.4.0'))
>>
>> Warning: the following items did not execute (for py26-pyobjc2):
>> org.macports.activate org.macports.build org.macports.destroot
>> org.macports.install
>> Error: Status 1 encountered during processing.
>> macintosh:~ frstan$
>
> py26-pyobjc2 depends on port:py26-py2app-devel, which is version  
> 0.4.2,
> so I can only assume that py26-py2app-devel is inactive, and you're
> using MP 1.6 so it doesn't notice.
>
> - Josh


btw  building py26-pyobjc2-cocoa also fails with this same  error   
concerning py2app 0.3.6

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

Mundus vult decepi, ego non


From frstan at bellsouth.net  Fri Dec  5 15:58:49 2008
From: frstan at bellsouth.net (William Davis)
Date: Fri, 5 Dec 2008 18:58:49 -0500
Subject: py26-pyobjc2
In-Reply-To: <4939B695.8070904@macports.org>
References: <96A12368-9BFB-4681-A34A-D036AA7DF5CD@bellsouth.net>
	<4939B695.8070904@macports.org>
Message-ID: <73177342-231B-4E7C-B198-8E6579A4DEDC@bellsouth.net>


On Dec 5, 2008, at 6:17 PM, Joshua Root wrote:

> William Davis wrote:
>> py26-py0bjc2:
>>
>> raise VersionConflict(dist,req) # XXX put more info here
>> pkg_resources.VersionConflict: (py2app 0.3.6
>> (/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
>> python2.6/site-packages),
>> Requirement.parse('py2app>=0.4.0'))
>>
>> Warning: the following items did not execute (for py26-pyobjc2):
>> org.macports.activate org.macports.build org.macports.destroot
>> org.macports.install
>> Error: Status 1 encountered during processing.
>> macintosh:~ frstan$
>
> py26-pyobjc2 depends on port:py26-py2app-devel, which is version  
> 0.4.2,
> so I can only assume that py26-py2app-devel is inactive, and you're
> using MP 1.6 so it doesn't notice.
>
> - Josh

Further followup:  I also needed, as it turns out, to deactivate py26- 
modulegraph and then activate py26-modulegraph-devel @0.7.2_0
After that I could install py26-pyobjc2. This also fixed the build of  
py26-pyobjc2-cocoa.

thanks

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

Mundus vult decepi, ego non


From jmr at macports.org  Fri Dec  5 16:03:10 2008
From: jmr at macports.org (Joshua Root)
Date: Sat, 06 Dec 2008 11:03:10 +1100
Subject: py26-pyobjc2
In-Reply-To: <6730CC78-8A06-4BFF-A47C-2F81E6ED3ED3@bellsouth.net>
References: <96A12368-9BFB-4681-A34A-D036AA7DF5CD@bellsouth.net>
	<4939B695.8070904@macports.org>
	<6730CC78-8A06-4BFF-A47C-2F81E6ED3ED3@bellsouth.net>
Message-ID: <4939C13E.1020701@macports.org>

William Davis wrote:
> 
> On Dec 5, 2008, at 6:17 PM, Joshua Root wrote:
> 
>> William Davis wrote:
>>> py26-py0bjc2:
>>>
>>> raise VersionConflict(dist,req) # XXX put more info here
>>> pkg_resources.VersionConflict: (py2app 0.3.6
>>> (/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages),
>>>
>>> Requirement.parse('py2app>=0.4.0'))
>>>
>>> Warning: the following items did not execute (for py26-pyobjc2):
>>> org.macports.activate org.macports.build org.macports.destroot
>>> org.macports.install
>>> Error: Status 1 encountered during processing.
>>> macintosh:~ frstan$
>>
>> py26-pyobjc2 depends on port:py26-py2app-devel, which is version 0.4.2,
>> so I can only assume that py26-py2app-devel is inactive, and you're
>> using MP 1.6 so it doesn't notice.
>>
>> - Josh
> 
> good diagnosis
> However merely deactivating py26-py2app and activating py-py2app-devel
> wasnt enough.  The error recurred.  After uninstalling py26-py2app,
> the error still remains the same.

Did you clean first?

- Josh

From ryandesign at macports.org  Fri Dec  5 22:00:12 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sat, 6 Dec 2008 00:00:12 -0600
Subject: [macports-mgr] Macports issue
In-Reply-To: <4939B6FF.3080805@macports.org>
References: <C55F6695.19%davidfoster.studio@virgin.net>
	<4939B6FF.3080805@macports.org>
Message-ID: <9D2A4B90-2B9B-4190-A27A-E1C67C9CAF73@macports.org>


On Dec 5, 2008, at 17:19, Joshua Root wrote:

> d f wrote:
>
>> Hey
>> I can't get ghostscript installed after putting macports onto a  
>> powerbook
>> 10.4.11
>> Get an error type 1
>> I followed some advice on CADP website about setting $PATH but no  
>> joy when
>> typing  sudo install ghostscript
>> Any ideas?
>> Can I configure the installation to use a locally downloaded  
>> ghostscript
>> package (and ghostview)
>> My aims are "simple" - to be able to live preview direct postscript -
>> without burning trees on my old laserwriter II - and maybe later  
>> on my rip
>> to a designjet
>> Any help most gratefully received.
>>
>> Also happy to join the community if any help.
>> Cheers
>>
>> David
>
> I'm forwarding this to the macports-users list, which is the  
> appropriate
> place for this sort of thing.

Welcome to MacPorts, David.

What happened when you ran "sudo port install ghostscript"? Could you  
show us the exact output you received?

I assume you know that you can open PostScript files into Apple's  
Preview program also?


From macports at tprfct.net  Fri Dec  5 23:19:57 2008
From: macports at tprfct.net (Kastus Shchuka)
Date: Fri, 5 Dec 2008 23:19:57 -0800
Subject: ffmpeg build error
Message-ID: <E5826F2A-5DDA-4E4D-8CED-A71040FADC48@tprfct.net>

I tried to upgrade to ffmpeg 15261_0 and stumbled at this error:

--->  Building ffmpeg with target all
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_multimedia_ffmpeg/work/trunk" && gmake all  
" returned error 2
Command output: libavcodec/ppc/snow_altivec.c:727: warning: pointer  
type mismatch in conditional expression
gcc-4.0 -DHAVE_AV_CONFIG_H -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE - 
I. -I"/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_multimedia_ffmpeg/work/trunk" -O2 - 
DHAVE_LRINTF -I/opt/local/include -D_ISOC99_SOURCE - 
D_POSIX_C_SOURCE=200112 -fasm -std=c99 -pipe -force_cpusubtype_ALL - 
Wno-sign-compare -fomit-frame-pointer -maltivec -mabi=altivec -g - 
Wdeclaration-after-statement -Wall -Wno-switch -Wdisabled-optimization  
-Wpointer-arith -Wredundant-decls -Wno-pointer-sign -Wcast-qual - 
Wwrite-strings -O3 -fno-math-errno      -maltivec -mabi=altivec - 
maltivec -mabi=altivec -fPIC -DPIC -c -o libavcodec/ppc/ 
vc1dsp_altivec.o libavcodec/ppc/vc1dsp_altivec.c
gcc-4.0 -DHAVE_AV_CONFIG_H -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE - 
I. -I"/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_multimedia_ffmpeg/work/trunk" -O2 - 
DHAVE_LRINTF -I/opt/local/include -D_ISOC99_SOURCE - 
D_POSIX_C_SOURCE=200112 -fasm -std=c99 -pipe -force_cpusubtype_ALL - 
Wno-sign-compare -fomit-frame-pointer -maltivec -mabi=altivec -g - 
Wdeclaration-after-statement -Wall -Wno-switch -Wdisabled-optimization  
-Wpointer-arith -Wredundant-decls -Wno-pointer-sign -Wcast-qual - 
Wwrite-strings -O3 -fno-math-errno      -fPIC -DPIC -c -o libavcodec/ 
ppc/check_altivec.o libavcodec/ppc/check_altivec.c
In file included from /usr/include/sys/ucred.h:76,
                  from /usr/include/sys/sysctl.h:83,
                  from libavcodec/ppc/check_altivec.c:26:
/usr/include/bsm/audit.h:224: error: syntax error before 'u_char'
/usr/include/bsm/audit.h:227: error: syntax error before '}' token
/usr/include/bsm/audit.h:234: error: syntax error before 'u_char'
/usr/include/bsm/audit.h:237: error: syntax error before '}' token
In file included from /usr/include/sys/sysctl.h:83,
                  from libavcodec/ppc/check_altivec.c:26:
/usr/include/sys/ucred.h:90: error: syntax error before 'u_long'
/usr/include/sys/ucred.h:113: error: syntax error before '}' token
/usr/include/sys/ucred.h:130: error: syntax error before 'u_int'
/usr/include/sys/ucred.h:134: error: syntax error before '}' token
In file included from /usr/include/sys/sysctl.h:84,
                  from libavcodec/ppc/check_altivec.c:26:
/usr/include/sys/proc.h:114: error: syntax error before 'u_int'
/usr/include/sys/proc.h:119: error: syntax error before 'p_swtime'
/usr/include/sys/proc.h:120: error: syntax error before 'p_slptime'
/usr/include/sys/proc.h:134: error: syntax error before 'p_priority'
/usr/include/sys/proc.h:135: error: syntax error before 'p_usrpri'
/usr/include/sys/proc.h:140: error: syntax error before 'p_xstat'
/usr/include/sys/proc.h:141: error: syntax error before 'p_acflag'
/usr/include/sys/proc.h:143: error: syntax error before '}' token
In file included from libavcodec/ppc/check_altivec.c:26:
/usr/include/sys/sysctl.h:440: error: field 'kp_proc' has incomplete  
type
/usr/include/sys/sysctl.h:750: error: syntax error before 'u_int'
gmake: *** [libavcodec/ppc/check_altivec.o] Error 1

Error: Unable to upgrade port: 1

This happened  on iBook G4 running Leopard (10.5.5). Is it me doing  
something wrong or did I hit a bug?

Thanks, -Kastus

From macports at tprfct.net  Fri Dec  5 23:29:21 2008
From: macports at tprfct.net (Kastus Shchuka)
Date: Fri, 5 Dec 2008 23:29:21 -0800
Subject: ffmpeg build error
In-Reply-To: <E5826F2A-5DDA-4E4D-8CED-A71040FADC48@tprfct.net>
References: <E5826F2A-5DDA-4E4D-8CED-A71040FADC48@tprfct.net>
Message-ID: <9CFF0862-B1A6-41EF-8FDF-414ED3F1046F@tprfct.net>

I found ticket #17527 in Trac about it. Sorry for the noise.

On Dec 5, 2008, at 11:19 PM, Kastus Shchuka wrote:

> I tried to upgrade to ffmpeg 15261_0 and stumbled at this error:
>
> --->  Building ffmpeg with target all
> Error: Target org.macports.build returned: shell command " cd "/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_multimedia_ffmpeg/work/trunk" && gmake  
> all " returned error 2
> Command output: libavcodec/ppc/snow_altivec.c:727: warning: pointer  
> type mismatch in conditional expression
> gcc-4.0 -DHAVE_AV_CONFIG_H -D_FILE_OFFSET_BITS=64 - 
> D_LARGEFILE_SOURCE -I. -I"/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_multimedia_ffmpeg/work/trunk" -O2 - 
> DHAVE_LRINTF -I/opt/local/include -D_ISOC99_SOURCE - 
> D_POSIX_C_SOURCE=200112 -fasm -std=c99 -pipe -force_cpusubtype_ALL - 
> Wno-sign-compare -fomit-frame-pointer -maltivec -mabi=altivec -g - 
> Wdeclaration-after-statement -Wall -Wno-switch -Wdisabled- 
> optimization -Wpointer-arith -Wredundant-decls -Wno-pointer-sign - 
> Wcast-qual -Wwrite-strings -O3 -fno-math-errno      -maltivec - 
> mabi=altivec -maltivec -mabi=altivec -fPIC -DPIC -c -o libavcodec/ 
> ppc/vc1dsp_altivec.o libavcodec/ppc/vc1dsp_altivec.c
> gcc-4.0 -DHAVE_AV_CONFIG_H -D_FILE_OFFSET_BITS=64 - 
> D_LARGEFILE_SOURCE -I. -I"/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_multimedia_ffmpeg/work/trunk" -O2 - 
> DHAVE_LRINTF -I/opt/local/include -D_ISOC99_SOURCE - 
> D_POSIX_C_SOURCE=200112 -fasm -std=c99 -pipe -force_cpusubtype_ALL - 
> Wno-sign-compare -fomit-frame-pointer -maltivec -mabi=altivec -g - 
> Wdeclaration-after-statement -Wall -Wno-switch -Wdisabled- 
> optimization -Wpointer-arith -Wredundant-decls -Wno-pointer-sign - 
> Wcast-qual -Wwrite-strings -O3 -fno-math-errno      -fPIC -DPIC -c - 
> o libavcodec/ppc/check_altivec.o libavcodec/ppc/check_altivec.c
> In file included from /usr/include/sys/ucred.h:76,
>                 from /usr/include/sys/sysctl.h:83,
>                 from libavcodec/ppc/check_altivec.c:26:
> /usr/include/bsm/audit.h:224: error: syntax error before 'u_char'
> /usr/include/bsm/audit.h:227: error: syntax error before '}' token
> /usr/include/bsm/audit.h:234: error: syntax error before 'u_char'
> /usr/include/bsm/audit.h:237: error: syntax error before '}' token
> In file included from /usr/include/sys/sysctl.h:83,
>                 from libavcodec/ppc/check_altivec.c:26:
> /usr/include/sys/ucred.h:90: error: syntax error before 'u_long'
> /usr/include/sys/ucred.h:113: error: syntax error before '}' token
> /usr/include/sys/ucred.h:130: error: syntax error before 'u_int'
> /usr/include/sys/ucred.h:134: error: syntax error before '}' token
> In file included from /usr/include/sys/sysctl.h:84,
>                 from libavcodec/ppc/check_altivec.c:26:
> /usr/include/sys/proc.h:114: error: syntax error before 'u_int'
> /usr/include/sys/proc.h:119: error: syntax error before 'p_swtime'
> /usr/include/sys/proc.h:120: error: syntax error before 'p_slptime'
> /usr/include/sys/proc.h:134: error: syntax error before 'p_priority'
> /usr/include/sys/proc.h:135: error: syntax error before 'p_usrpri'
> /usr/include/sys/proc.h:140: error: syntax error before 'p_xstat'
> /usr/include/sys/proc.h:141: error: syntax error before 'p_acflag'
> /usr/include/sys/proc.h:143: error: syntax error before '}' token
> In file included from libavcodec/ppc/check_altivec.c:26:
> /usr/include/sys/sysctl.h:440: error: field 'kp_proc' has incomplete  
> type
> /usr/include/sys/sysctl.h:750: error: syntax error before 'u_int'
> gmake: *** [libavcodec/ppc/check_altivec.o] Error 1
>
> Error: Unable to upgrade port: 1
>
> This happened  on iBook G4 running Leopard (10.5.5). Is it me doing  
> something wrong or did I hit a bug?
>
> Thanks, -Kastus
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From david.trem at gmail.com  Sat Dec  6 01:26:51 2008
From: david.trem at gmail.com (David Trem)
Date: Sat, 06 Dec 2008 10:26:51 +0100
Subject: py26-   modules install problem
Message-ID: <493A455B.8060904@gmail.com>

Hi,

 Trying to start playing with python 2.6 that compiled smoothly, I
encounter a problem installing py26-* modules:
py26-setuptools install fail returning this message:
"""
--->  Staging py26-setuptools into destroot
Error: Target org.macports.destroot returned: can't read
"python.bindir": no such variable
"""

Any idea what is going on and how I could solve the issue?

Macport 1.600 version on a Macbook running OS X 10.5.5

Thanks in advance,

David

From mcalhoun at macports.org  Sat Dec  6 03:48:40 2008
From: mcalhoun at macports.org (Marcus Calhoun-Lopez)
Date: Sat, 6 Dec 2008 11:48:40 +0000 (UTC)
Subject: py26-   modules install problem
References: <493A455B.8060904@gmail.com>
Message-ID: <loom.20081206T113601-514@post.gmane.org>

David Trem <david.trem <at> gmail.com> writes:

>  Trying to start playing with python 2.6 that compiled smoothly, I
> encounter a problem installing py26-* modules:
> py26-setuptools install fail returning this message:
> """
> --->  Staging py26-setuptools into destroot
> Error: Target org.macports.destroot returned: can't read
> "python.bindir": no such variable
> """

It was a bug in the Portfile.
It should be fixed now (in r43170).

-Marcus




From david.trem at gmail.com  Sat Dec  6 03:59:54 2008
From: david.trem at gmail.com (David Trem)
Date: Sat, 06 Dec 2008 12:59:54 +0100
Subject: py26-   modules install problem
In-Reply-To: <loom.20081206T113601-514@post.gmane.org>
References: <493A455B.8060904@gmail.com>
	<loom.20081206T113601-514@post.gmane.org>
Message-ID: <493A693A.9030007@gmail.com>

Yes, it works now!

Thanks,

David

Marcus Calhoun-Lopez a ?crit :
> David Trem <david.trem <at> gmail.com> writes:
> 
>>  Trying to start playing with python 2.6 that compiled smoothly, I
>> encounter a problem installing py26-* modules:
>> py26-setuptools install fail returning this message:
>> """
>> --->  Staging py26-setuptools into destroot
>> Error: Target org.macports.destroot returned: can't read
>> "python.bindir": no such variable
>> """
> 
> It was a bug in the Portfile.
> It should be fixed now (in r43170).
> 
> -Marcus
> 
> 
> 
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

From smibrahim at gmail.com  Sat Dec  6 04:30:00 2008
From: smibrahim at gmail.com (S. M. Ibrahim (Lavlu))
Date: Sat, 6 Dec 2008 18:30:00 +0600
Subject: install gnome +www
Message-ID: <4997275b0812060430h74a3cf01qb97edadde7e7a858@mail.gmail.com>

hi,

i am trying to install gnome with www variants . but getting this error.

[lavlu/test] > install gnome +www
Skipping org.macports.activate (py25-pygtksourceview +darwin_9) since this
port is already active
--->  Cleaning py25-pygtksourceview
Skipping org.macports.activate (gtksourceview ) since this port is already
active
--->  Cleaning gtksourceview
Skipping org.macports.activate (gnome-python-desktop +darwin_9) since this
port is already active
--->  Cleaning gnome-python-desktop
Skipping org.macports.activate (gnome-games +darwin_9) since this port is
already active
--->  Cleaning gnome-games
Skipping org.macports.activate (gnome-terminal ) since this port is already
active
--->  Cleaning gnome-terminal
Skipping org.macports.activate (gnome-utils ) since this port is already
active
--->  Cleaning gnome-utils
Skipping org.macports.activate (gnopernicus ) since this port is already
active
--->  Cleaning gnopernicus
--->  Configuring avahi
Error: Target org.macports.configure returned: configure failure: shell
command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_avahi/work/avahi-0.6.23"
&& ./configure --prefix=/opt/local --disable-autoipd --disable-qt3
--disable-qt4 --disable-mono --disable-monodoc
--with-libiconv-prefix=/opt/local --with-libintl-prefix=/opt/local
--with-distro=darwin --enable-compat-libdns_sd " returned error 1
Command output: checking for gmsgfmt... (cached) /opt/local/bin/msgfmt
checking for xgettext... (cached) /opt/local/bin/xgettext
checking for pkg-config... yes
checking for pkg-config... /opt/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GLIB20... yes
checking for GOBJECT... yes
checking for GTK20... yes
checking for GLADE20... yes
checking for DBUS... yes
Your D-Bus version is 1,2,4.
checking for dbus_connection_close... yes
checking for dbus_bus_get_private... yes
checking for XML_ParserCreate in -lexpat... yes
checking expat.h usability... yes
checking expat.h presence... yes
checking for expat.h... yes
checking for XML_ParserCreate in -lbsdxml... no
checking for gdbm_open in -lgdbm... yes
checking gdbm.h usability... yes
checking gdbm.h presence... yes
checking for gdbm.h... yes
checking for LIBDAEMON... yes
checking whether /opt/local/bin/python2.5 version >= 2.4... yes
checking for /opt/local/bin/python2.5 version... 2.5
checking for /opt/local/bin/python2.5 platform... darwin
checking for /opt/local/bin/python2.5 script directory...
${prefix}/lib/python2.5/site-packages
checking for /opt/local/bin/python2.5 extension module directory...
${exec_prefix}/lib/python2.5/site-packages
checking for python module gtk... no
configure: error: Could not find Python module gtk

Error: The following dependencies failed to build: gnome-desktop-suite
seahorse avahi gpgme vino yelp zenity
Error: Status 1 encountered during processing.
[lavlu/test] >

i checked, i have already py25-gtk  .



-- 
S. M. Ibrahim Lavlu
software engineer, php
somewhere in...
http://www.somewherein.net

bangla blog: http://www.somewhereinblog.net
my blog: http://www.lavluda.com
mac blog: htttp://www.mac-talks.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081206/f089adf5/attachment.html>

From face at CentosPrime.COM  Sat Dec  6 05:59:23 2008
From: face at CentosPrime.COM (Chris Janton)
Date: Sat, 06 Dec 2008 06:59:23 -0700
Subject: panther - php5 upgrade - i'm confused
Message-ID: <B1303BBD-3F85-4602-9F7C-AF35AFF1E375@centosprime.com>

admin at x:admin:123 $ sudo port sync
admin at x:admin:124 $ port outdated
The following installed ports are outdated:
php5                           5.2.6_2 < 5.2.7_1
admin at x:admin:125 $ sudo port upgrade php5
--->  Installing apache2 2.2.10_0+darwin_7
--->  Activating apache2 2.2.10_0+darwin_7
Error: Target org.macports.activate returned: Image error: /opt/local/ 
share/man/man1/dbmmanage.1.gz is being used by the active apache  
port.  Please deactivate this port first, or use the -f flag to force  
the activation.
--->  Fetching php5
--->  Attempting to fetch php-5.2.7.tar.bz2 from http://www.php.net/distributions/
--->  Verifying checksum(s) for php5
--->  Extracting php5
--->  Applying patches to php5
--->  Configuring php5
--->  Building php5 with target all
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7" && make all "  
returned error 2
Command output: /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3624: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3628: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3637: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3641: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3642: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3642: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3644: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3646: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3650: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3652: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3653: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3654: warning: passing arg 2 of `zend_register_resource'  
makes pointer from integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c: In function `zif_odbc_tableprivileges':
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3664: error: invalid lvalue in assignment
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3687: error: parse error before ')' token
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3689: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3691: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3698: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3702: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3709: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3713: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3714: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3714: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3716: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3718: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3722: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3724: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3725: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3726: warning: passing arg 2 of `zend_register_resource'  
makes pointer from integer without a cast
make: *** [ext/odbc/php_odbc.lo] Error 1

Error: Unable to upgrade port: 1

Installed ports (edited)

admin at x:admin:126 $ port installed
The following ports are currently installed:
   apache @1.3.41_0 (active)
   apache2 @2.2.10_0+darwin_7
   apr @1.3.3_0 (active)
   apr-util @1.3.4_1+no_bdb (active)
   php5 @5.2.6_2+apache+darwin_7+macosx+mysql5+pear (active)
admin at x:admin:127 $

Why does the php5 upgrade "install" apache2?

clearly something is a bit different today ;-)

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



From harrylparker at gmail.com  Sat Dec  6 09:24:50 2008
From: harrylparker at gmail.com (Harry Parker)
Date: Sat, 6 Dec 2008 12:24:50 -0500
Subject: MacPorts installs libraries I already have!
Message-ID: <2a77b9140812060924p7437e068h7412fdec172b217c@mail.gmail.com>

Emmanuel Hainry wrote:


Citando Scott :
> Hello.
>
> I MacPorted a bunch of stuff yesterday (libpng, netpbm, and gocr), and
> MacPorts added repeats of lib files, man pages, and other stuff I
> ALREADY HAD in both my system-installed libraries and in
> /usr/local/share!  What?s up with that?
>
> For example, when I MacPorted gocr, it fetched and installed jpeg 6b_3
> -- but I already have it.
>
> Then it installed jasper 1.900.1_1+darwin_9.  Already have that, too.
>
> Then it installed tiff.  Already have that, too.
>
> Then it installed netpbm, which I had already installed myself --
> using the ordinary ./config, make, install -- into /usr/local/share.
>
> Two questions:
>
> (1) Shouldn?t MacPorts LOOK to see if I have what it thinks it should
> install?  Is there a way to MAKE MacPorts look first, and thus skip
> duplicate files?

No. It is a choice. Apart from very specific cases, macports depends
only on things installed through macports.
http://trac.macports.org/wiki/FAQ#WhyisMacPortsusingitsownlibraries

>
> (2) Should I now delete ONE of the duplicate file-sets?  If so, which
> should I kill -- the ordinary /usr/...  embedded set, or MacPorts'
> /opt/... embedded set?

If you want macports to keep on working, don't delete anything in
/opt/local by hand. To convince yourself, have a look at 'otool -L
/opt/local/bin/gocr' (not sure of the switch, not sure gocr installs a
binary named gocr, but however). You will see that it depends on the
libraries installed by macports.

Your /usr/local/ tree should be as empty as possible, if you need to
delete something, delete it. (be warned that things you installed using
those libraries will probably stop working, but you can probably install
them through macports).

Actually, a much less destructive way to go is to temporarily rename
/usr/local/ to something else while using the MacPorts build system.  Once
your ports are built, you can rename it back.  No sense "throwing the baby
out with the bath water."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081206/5b79b1d8/attachment.html>

From ryandesign at macports.org  Sat Dec  6 11:24:34 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sat, 6 Dec 2008 13:24:34 -0600
Subject: panther - php5 upgrade - i'm confused
In-Reply-To: <B1303BBD-3F85-4602-9F7C-AF35AFF1E375@centosprime.com>
References: <B1303BBD-3F85-4602-9F7C-AF35AFF1E375@centosprime.com>
Message-ID: <10F7AB09-3DD4-4C40-9FE9-AD0A7BB9F08C@macports.org>


On Dec 6, 2008, at 07:59, Chris Janton wrote:

> admin at x:admin:123 $ sudo port sync
> admin at x:admin:124 $ port outdated
> The following installed ports are outdated:
> php5                           5.2.6_2 < 5.2.7_1
> admin at x:admin:125 $ sudo port upgrade php5
> --->  Installing apache2 2.2.10_0+darwin_7
> --->  Activating apache2 2.2.10_0+darwin_7
> Error: Target org.macports.activate returned: Image error: /opt/ 
> local/share/man/man1/dbmmanage.1.gz is being used by the active  
> apache port.  Please deactivate this port first, or use the -f flag  
> to force the activation.
> --->  Fetching php5
> --->  Attempting to fetch php-5.2.7.tar.bz2 from http://www.php.net/ 
> distributions/
> --->  Verifying checksum(s) for php5
> --->  Extracting php5
> --->  Applying patches to php5
> --->  Configuring php5
> --->  Building php5 with target all
> Error: Target org.macports.build returned: shell command " cd "/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7" && make all " returned error 2
> Command output: /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3624: warning: passing arg 1  
> of `_efree' makes pointer from integer without a cast
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3628: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3637: warning: passing arg 1  
> of `_efree' makes pointer from integer without a cast
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3641: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3642: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3642: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3644: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3646: warning: passing arg 1  
> of `_efree' makes pointer from integer without a cast
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3650: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3652: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3653: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3654: warning: passing arg 2  
> of `zend_register_resource' makes pointer from integer without a cast
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c: In function  
> `zif_odbc_tableprivileges':
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3664: error: invalid lvalue  
> in assignment
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3687: error: parse error  
> before ')' token
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3689: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3691: warning: passing arg 1  
> of `_efree' makes pointer from integer without a cast
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3698: warning: passing arg 1  
> of `_efree' makes pointer from integer without a cast
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3702: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3709: warning: passing arg 1  
> of `_efree' makes pointer from integer without a cast
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3713: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3714: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3714: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3716: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3718: warning: passing arg 1  
> of `_efree' makes pointer from integer without a cast
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3722: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3724: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3725: error: invalid type  
> argument of `->'
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.7/ext/odbc/php_odbc.c:3726: warning: passing arg 2  
> of `zend_register_resource' makes pointer from integer without a cast
> make: *** [ext/odbc/php_odbc.lo] Error 1
>
> Error: Unable to upgrade port: 1
>
> Installed ports (edited)
>
> admin at x:admin:126 $ port installed
> The following ports are currently installed:
>   apache @1.3.41_0 (active)
>   apache2 @2.2.10_0+darwin_7
>   apr @1.3.3_0 (active)
>   apr-util @1.3.4_1+no_bdb (active)
>   php5 @5.2.6_2+apache+darwin_7+macosx+mysql5+pear (active)
> admin at x:admin:127 $
>
> Why does the php5 upgrade "install" apache2?

I don't know... I didn't change anything in the dependencies  
recently. I'll test on my Panther machine later.

I notice you have the apache port installed. Are you currently using  
php5 with that apache, and/or is that your intention? Because the  
+apache variant of php5 currently uses Apple's Apache 1 server, not  
MacPorts apache. Though I have been meaning to change this forever.

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



From jwdavison at me.com  Sat Dec  6 17:04:24 2008
From: jwdavison at me.com (joseph davison)
Date: Sat, 06 Dec 2008 19:04:24 -0600
Subject: Hurrah for emacs-app
Message-ID: <84864F1B-E2A8-4812-80BF-9D84B4E617D7@me.com>

Just moved from Tiger to Leopard on my MacBookPro.   Did an erase and  
install and then tried moving some things back from my backup.

I must have missed something with my emacs-app, because it would start  
& disappear.   I think I set it up to share the lisp files with  
another version but hadn't saved the other version, probably.

Thought I'd need to relearn how to build it, and that wasn't working  
well.

Luckily for me, I remembered it was now built from the standard files  
and thought I'd seen something about it being available with MacPorts...

Imagine my satisfaction to find it was as simple as port install emacs- 
app!

Great job, y'all!   I got my productivity back!

joe

From mp+u at v6shell.org  Sat Dec  6 17:48:30 2008
From: mp+u at v6shell.org (mp+u at v6shell.org)
Date: Sun, 07 Dec 2008 01:48:30 +0000
Subject: Hurrah for emacs-app
In-Reply-To: <84864F1B-E2A8-4812-80BF-9D84B4E617D7@me.com>
References: <84864F1B-E2A8-4812-80BF-9D84B4E617D7@me.com>
Message-ID: <493b2b6e.ZIRjBD5C1AmQbvCS%mp+u@v6shell.org>

joseph davison <jwdavison at me.com> wrote:

> Luckily for me, I remembered it was now built from the standard files  
> and thought I'd seen something about it being available with MacPorts...
>
> Imagine my satisfaction to find it was as simple as port install emacs- 
> app!
>
> Great job, y'all!   I got my productivity back!

I agree; I do the same w/ vim-app (to each his own ;^)

For me, MacPorts truly simplifies installing and upgrading a wealth
of open source software that I simply could not live without.

Thus, here is another "great job" to all the MacPorts team members
and all the other humans who help make MacPorts what it is!  Jeff
-- 
J.A. Neitzel
V6 Thompson Shell Port - http://v6shell.org/

From jmr at macports.org  Sun Dec  7 02:57:03 2008
From: jmr at macports.org (Joshua Root)
Date: Sun, 07 Dec 2008 21:57:03 +1100
Subject: 1.7.0 release candidate 1 available for testing
Message-ID: <493BABFF.7030200@macports.org>

Forwarding to macports-users for wider exposure. :-)

- Josh
-------------- next part --------------
An embedded message was scrubbed...
From: unknown sender
Subject: no subject
Date: no date
Size: 4806
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081207/faf7e6a4/attachment.eml>

From jmr at macports.org  Sun Dec  7 03:27:01 2008
From: jmr at macports.org (Joshua Root)
Date: Sun, 07 Dec 2008 22:27:01 +1100
Subject: 1.7.0 release candidate 1 available for testing
In-Reply-To: <493BABFF.7030200@macports.org>
References: <493BABFF.7030200@macports.org>
Message-ID: <493BB305.50500@macports.org>

Hmm, looks like the attachment was scrubbed in the archives, so here's a
link to the announcement on -dev:

<http://lists.macosforge.org/pipermail/macports-dev/2008-December/006614.html>

- Josh

From admin2 at enabled.com  Sun Dec  7 05:22:02 2008
From: admin2 at enabled.com (Admin)
Date: Sun, 07 Dec 2008 05:22:02 -0800
Subject: building apple-gcc42 fails: C compiler cannot create executables.
Message-ID: <493BCDFA.7090407@enabled.com>

Hi there,

I am not sure where to begin to troubleshoot this issue.  Anybody know 
what to do here?  Building apple-gcc42 fails.


sh-3.2# port install apple-gcc42
--->  Configuring apple-gcc42
Error: Target org.macports.configure returned: configure failure: shell 
command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_apple-gcc42/work/build" 
&& 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_apple-gcc42/work/gcc_42-5531/configure 
--prefix=/opt/local/lib/apple-gcc42 --enable-languages=c,objc 
--program-suffix=-apple-4.2 " returned error 1
Command output: loading cache ./config.cache
checking host system type... powerpc-apple-darwin9.5.0
checking target system type... powerpc-apple-darwin9.5.0
checking build system type... powerpc-apple-darwin9.5.0
checking for a BSD compatible install... /usr/bin/install
checking whether ln works... yes
checking whether ln -s works... yes
checking for gcc... /usr/bin/gcc-4.0
checking whether the C compiler (/usr/bin/gcc-4.0  ) works... no
configure: error: installation or configuration problem: C compiler 
cannot create executables.

Error: Status 1 encountered during processing.
sh-3.2# whoami
root


From admin2 at enabled.com  Sun Dec  7 05:30:25 2008
From: admin2 at enabled.com (Admin)
Date: Sun, 07 Dec 2008 05:30:25 -0800
Subject: port upgrade installed fails:  Can't map the URL 'file://.' to a
	port description file 
Message-ID: <493BCFF1.3090006@enabled.com>

Hi there,

might somebody have a clue as to what is going on here?
I am running macports on a dual G5 with 10.5.5

I replaced my home directory path in the error message with <homedir>

sh-3.2# /opt/local/bin/port upgrade installed
Can't map the URL 'file://.' to a port description file ("Could not find 
Portfile in /Users/<homedir>").
Please verify that the directory and portfile syntax are correct.
To use the current port, you must be in a port's directory.
(you might also see this message if a pseudo-port such as
outdated or installed expands to no ports).
Error: No port  found.
sh-3.2# whoami
root



Cheers,

Noah

From raimue at macports.org  Sun Dec  7 05:36:02 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Sun, 07 Dec 2008 14:36:02 +0100
Subject: port upgrade installed fails:  Can't map the URL 'file://.' to
	a	port description file
In-Reply-To: <493BCFF1.3090006@enabled.com>
References: <493BCFF1.3090006@enabled.com>
Message-ID: <493BD142.1080303@macports.org>

Admin wrote:
> sh-3.2# /opt/local/bin/port upgrade installed

Usually it is better to use 'upgrade outdated'.

> Can't map the URL 'file://.' to a port description file ("Could not find 
> Portfile in /Users/<homedir>").
> Please verify that the directory and portfile syntax are correct.
> To use the current port, you must be in a port's directory.

> (you might also see this message if a pseudo-port such as
> outdated or installed expands to no ports).

^ Please read this sentence in parentheses again :-)

> Error: No port  found.

There will be a much better error message in 1.7.0.

Rainer

From face at CentosPrime.COM  Sun Dec  7 05:43:37 2008
From: face at CentosPrime.COM (Chris Janton)
Date: Sun, 07 Dec 2008 06:43:37 -0700
Subject: panther - php5 upgrade - i'm confused
In-Reply-To: <10F7AB09-3DD4-4C40-9FE9-AD0A7BB9F08C@macports.org>
References: <B1303BBD-3F85-4602-9F7C-AF35AFF1E375@centosprime.com>
	<10F7AB09-3DD4-4C40-9FE9-AD0A7BB9F08C@macports.org>
Message-ID: <8FCE77D3-15B5-4836-9038-4818C7F19801@CentosPrime.COM>

On 2008-12-06 , at 12:24 , Ryan Schmidt wrote:

>> Why does the php5 upgrade "install" apache2?
>
> I don't know... I didn't change anything in the dependencies  
> recently. I'll test on my Panther machine later.
>
> I notice you have the apache port installed. Are you currently using  
> php5 with that apache, and/or is that your intention? Because the  
> +apache variant of php5 currently uses Apple's Apache 1 server, not  
> MacPorts apache. Though I have been meaning to change this forever.


Way back in the past I couldn't get PHP to build without installing  
Apache, even though I want to use the Apple installed Apache 1 server.

admin at x:admin:122 $ sudo port deactivate apache
--->  Deactivating apache
admin at x:admin:123 $ sudo port upgrade php5
--->  Activating apache2 2.2.10_0+darwin_7
--->  Building php5 with target all
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/_opt_local_var_ma
  ...

admin at x:admin:124 $ sudo port uninstall apache2
--->  Deactivating apache2 2.2.10_0+darwin_7
--->  Uninstalling apache2 2.2.10_0+darwin_7
admin at x:admin:125 $ sudo port uninstall apache
--->  Uninstalling apache 1.3.41_0
admin at x:admin:126 $ sudo port upgrade php5
--->  Installing apache2 2.2.10_0+darwin_7
--->  Activating apache2 2.2.10_0+darwin_7
--->  Cleaning apache2
--->  Building php5 with target all
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7" && make all "  
returned error 2
Command output: /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.7/ext/odbc/ 
php_odbc.c:3624: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
  ...

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



From jmr at macports.org  Sun Dec  7 05:49:14 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 08 Dec 2008 00:49:14 +1100
Subject: building apple-gcc42 fails: C compiler cannot create executables.
In-Reply-To: <493BCDFA.7090407@enabled.com>
References: <493BCDFA.7090407@enabled.com>
Message-ID: <493BD45A.4030809@macports.org>

Admin wrote:
> Hi there,
> 
> I am not sure where to begin to troubleshoot this issue.  Anybody know
> what to do here?  Building apple-gcc42 fails.
> 
> 
> sh-3.2# port install apple-gcc42
> --->  Configuring apple-gcc42
> Error: Target org.macports.configure returned: configure failure: shell
> command " cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_apple-gcc42/work/build"
> &&
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_apple-gcc42/work/gcc_42-5531/configure
> --prefix=/opt/local/lib/apple-gcc42 --enable-languages=c,objc
> --program-suffix=-apple-4.2 " returned error 1
> Command output: loading cache ./config.cache
> checking host system type... powerpc-apple-darwin9.5.0
> checking target system type... powerpc-apple-darwin9.5.0
> checking build system type... powerpc-apple-darwin9.5.0
> checking for a BSD compatible install... /usr/bin/install
> checking whether ln works... yes
> checking whether ln -s works... yes
> checking for gcc... /usr/bin/gcc-4.0
> checking whether the C compiler (/usr/bin/gcc-4.0  ) works... no
> configure: error: installation or configuration problem: C compiler
> cannot create executables.

The usual reason for getting this error is that XCode is not installed,
or it is too old for your current OS. XCode 3.0 is the minimum for
Leopard, and 3.1 or later is highly recommended (latest is 3.1.2).

- Josh

From severin.lists at kacianka.at  Sun Dec  7 07:57:14 2008
From: severin.lists at kacianka.at (Severin Kacianka)
Date: Sun, 07 Dec 2008 16:57:14 +0100
Subject: Problems linking against OSG on OS X Tiger (on a Power PC)
Message-ID: <493BF25A.8030603@kacianka.at>

Hello,

I posted this question also on the osg-users mailing list, but it just 
occoured to me, that it may be more appropriate to post it here. Sorry 
for the cross posting :(

Message:

I hope I do not ask a too obvious question, but I am just trying to get 
familiar with OSG and in the process want to be able to compile it on 
Linux and OS X. On Linux I have no problems compiling a sample program 
like this:
g++ -I /usr/local/include/osg/ -losg -losgViewer -o foo test.cpp

On OS X I installed OS X via macports. First I tried to compile it 
directly form the sources, but ran into the bug described here:
http://trac.macports.org/ticket/17294

Compiling and installing via macports worked fine.
However if I try to compile a sample program I get the following error:

g++  -L/opt/local/lib/ -I/opt/local/include/  -losg -losgViewer -o foo 
test.cpp
/usr/bin/ld: warning can't open dynamic library: libOpenThreads.11.dylib 
referenced from: /opt/local/lib//libosg.dylib (checking for undefined 
symbols may be affected) (No such file or directory, errno = 2)
/usr/bin/ld: warning can't open dynamic library: libosgGA.48.dylib 
referenced from: /opt/local/lib//libosgViewer.dylib (checking for 
undefined symbols may be affected) (No such file or directory, errno = 2)
/usr/bin/ld: warning can't open dynamic library: libosgText.48.dylib 
referenced from: /opt/local/lib//libosgViewer.dylib (checking for 
undefined symbols may be affected) (No such file or directory, errno = 2)
/usr/bin/ld: warning can't open dynamic library: libosgDB.48.dylib 
referenced from: /opt/local/lib//libosgViewer.dylib (checking for 
undefined symbols may be affected) (No such file or directory, errno = 2)
/usr/bin/ld: warning can't open dynamic library: libosgUtil.48.dylib 
referenced from: /opt/local/lib//libosgViewer.dylib (checking for 
undefined symbols may be affected) (No such file or directory, errno = 2)
/usr/bin/ld: Undefined symbols:
*snip long list of symbols*
collect2: ld returned 1 exit status

So for some reason ld cannot find the references from the libraries 
among each other. The directory looks like this:

libOpenThreads.11.dylib -> libOpenThreads.2.3.0.dylib
libOpenThreads.2.3.0.dylib
libOpenThreads.dylib -> libOpenThreads.11.dylib


(other libs are linked in the same manner)

So the libs are there, but somehow not referenced correctly. Does anyone 
know what the problem may be, or any other way to use OSG on OS X?

Thank you for your time,
Severin Kacianka

From ohce86 at kitcarson.net  Sun Dec  7 09:16:41 2008
From: ohce86 at kitcarson.net (Timothy Goins)
Date: Sun, 7 Dec 2008 10:16:41 -0700
Subject: building apple-gcc42 fails: C compiler cannot create executables.
In-Reply-To: <493BCDFA.7090407@enabled.com>
References: <493BCDFA.7090407@enabled.com>
Message-ID: <B726E5E4-B38A-4863-997E-6A76A6C4D17E@kitcarson.net>

I encountered this problem compiling 4.3.  In /usr/bin I had the gcc  
executable but no gcc-4.0 file, so I created a link (sudo ln -s /usr/ 
bin/gcc /usr/bin/gcc-4.0).  The -s is unnecessary, I believe, but I  
did it because my symbolic links show up in a different color.

What I don't know why the configuration looks for gcc-4.0(.1) and not  
just /usr/bin/gcc.  Seems to me the link ought be the current  
executable linked to a /usr/bin/gcc pointer.  That way the current  
gcc, like /opt/local/bin/gcc-4.3 on my system, could be located  
anywhere.

Am I missing something here?

On Dec 7, 2008, at 6:22 AM, Admin wrote:

> Hi there,
>
> I am not sure where to begin to troubleshoot this issue.  Anybody  
> know what to do here?  Building apple-gcc42 fails.
>
>
> sh-3.2# port install apple-gcc42
> --->  Configuring apple-gcc42
> Error: Target org.macports.configure returned: configure failure:  
> shell command " cd "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_lang_apple-gcc42/work/build" && /opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_lang_apple-gcc42/work/gcc_42-5531/ 
> configure --prefix=/opt/local/lib/apple-gcc42 --enable- 
> languages=c,objc --program-suffix=-apple-4.2 " returned error 1
> Command output: loading cache ./config.cache
> checking host system type... powerpc-apple-darwin9.5.0
> checking target system type... powerpc-apple-darwin9.5.0
> checking build system type... powerpc-apple-darwin9.5.0
> checking for a BSD compatible install... /usr/bin/install
> checking whether ln works... yes
> checking whether ln -s works... yes
> checking for gcc... /usr/bin/gcc-4.0
> checking whether the C compiler (/usr/bin/gcc-4.0  ) works... no
> configure: error: installation or configuration problem: C compiler  
> cannot create executables.
>
> Error: Status 1 encountered during processing.
> sh-3.2# whoami
> root
>
> _______________________________________________
> 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/20081207/d20d8bb2/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/20081207/d20d8bb2/attachment.bin>

From jmr at macports.org  Sun Dec  7 09:49:28 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 08 Dec 2008 04:49:28 +1100
Subject: building apple-gcc42 fails: C compiler cannot create executables.
In-Reply-To: <B726E5E4-B38A-4863-997E-6A76A6C4D17E@kitcarson.net>
References: <493BCDFA.7090407@enabled.com>
	<B726E5E4-B38A-4863-997E-6A76A6C4D17E@kitcarson.net>
Message-ID: <493C0CA8.1000106@macports.org>

Timothy Goins wrote:
> I encountered this problem compiling 4.3.  In //usr/bin/ I had the
> /gcc/ executable but no gcc-4.0 file, so I created a link (/sudo ln -s
> /usr/bin/gcc /usr/bin/gcc-4.0/).  The /-s/ is unnecessary, I believe,
> but I did it because my symbolic links show up in a different color.  
> 
> What I don't know why the configuration looks for /gcc-4.0(.1)/ and not
> just //usr/bin/gcc/.  Seems to me the link ought be the current
> executable linked to a //usr/bin/gcc/ pointer.  That way the current
> /gcc/, like //opt/local/bin/gcc-4.3 /on my system, could be located
> anywhere.
> 
> Am I missing something here? 

If there is no /usr/bin/gcc-4.0, then your XCode installation is
incomplete. MacPorts will always use that specific compiler on Tiger and
Leopard (and gcc-3.3 on Panther) unless the Portfile specifies a
different one. The reason for this is that users will encounter a much
smaller variety of bugs if they are all building with the same compiler
as the port's maintainer.

- Josh

From frstan at bellsouth.net  Sun Dec  7 09:55:27 2008
From: frstan at bellsouth.net (William Davis)
Date: Sun, 7 Dec 2008 12:55:27 -0500
Subject: 1.7.0 release candidate 1 available for testing
In-Reply-To: <493BB305.50500@macports.org>
References: <493BABFF.7030200@macports.org> <493BB305.50500@macports.org>
Message-ID: <A7194711-E7FA-4391-BB0E-A575BD82D08F@bellsouth.net>


On Dec 7, 2008, at 6:27 AM, Joshua Root wrote:

> Hmm, looks like the attachment was scrubbed in the archives, so  
> here's a
> link to the announcement on -dev:
>
> <http://lists.macosforge.org/pipermail/macports-dev/2008-December/006614.html 
> >
>
> - Josh
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

just this so far:

(from selfupdate)
MacPorts base version 1.700 installed
DEBUG: Rebuilding and reinstalling MacPorts if needed
Downloaded MacPorts base version 1.600

The MacPorts installation is not outdated so it was not updated
DEBUG: Setting MacPorts sources ownership to root

note typo in "Downloaded MacPorts base version" message

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

Mundus vult decepi, ego non


From mp+u at v6shell.org  Sun Dec  7 09:58:41 2008
From: mp+u at v6shell.org (J.A. Neitzel)
Date: Sun, 07 Dec 2008 17:58:41 +0000
Subject: building apple-gcc42 fails: C compiler cannot create executables.
In-Reply-To: <B726E5E4-B38A-4863-997E-6A76A6C4D17E@kitcarson.net>
References: <493BCDFA.7090407@enabled.com>
	<B726E5E4-B38A-4863-997E-6A76A6C4D17E@kitcarson.net>
Message-ID: <493c0ed1.3d8pYcc8pllWf1P2%mp+u@v6shell.org>

Timothy Goins <ohce86 at kitcarson.net> wrote:

> On Dec 7, 2008, at 6:22 AM, Admin wrote:
>
> > Hi there,
> >
> > I am not sure where to begin to troubleshoot this issue.  Anybody  
> > know what to do here?  Building apple-gcc42 fails.
> >

[snip]

> I encountered this problem compiling 4.3.  In /usr/bin I had the gcc  
> executable but no gcc-4.0 file, so I created a link (sudo ln -s /usr/ 
> bin/gcc /usr/bin/gcc-4.0).  The -s is unnecessary, I believe, but I  
> did it because my symbolic links show up in a different color.
>
> What I don't know why the configuration looks for gcc-4.0(.1) and not  
> just /usr/bin/gcc.  Seems to me the link ought be the current  
> executable linked to a /usr/bin/gcc pointer.  That way the current  
> gcc, like /opt/local/bin/gcc-4.3 on my system, could be located  
> anywhere.
>
> Am I missing something here?

I am not MacPorts fluent on all the hows and whys and so forth, but
my guess is that MacPorts has some basis for what compiler is used
by default on a given system.

EG: In a Portfile, "configure.cc ${prefix}/name/that/compiler" =)

This reflects common usage I have seen over time.  Where you can
hopefully always do one of the following:

	`env CC=/name/that/compiler ./configure ...',
	`env CC=/name/that/compiler make ...',
	or
	`make CC=/name/that/compiler ...'

...
Maybe this helps a little; maybe not.
-- 
J.A. Neitzel
V6 Thompson Shell Port - http://v6shell.org/

From jmr at macports.org  Sun Dec  7 11:10:09 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 08 Dec 2008 06:10:09 +1100
Subject: 1.7.0 release candidate 1 available for testing
In-Reply-To: <A7194711-E7FA-4391-BB0E-A575BD82D08F@bellsouth.net>
References: <493BABFF.7030200@macports.org> <493BB305.50500@macports.org>
	<A7194711-E7FA-4391-BB0E-A575BD82D08F@bellsouth.net>
Message-ID: <493C1F91.3040708@macports.org>

William Davis wrote:
> 
> On Dec 7, 2008, at 6:27 AM, Joshua Root wrote:
> 
>> Hmm, looks like the attachment was scrubbed in the archives, so here's a
>> link to the announcement on -dev:
>>
>> <http://lists.macosforge.org/pipermail/macports-dev/2008-December/006614.html>
>>
>>
>> - Josh
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> 
> just this so far:
> 
> (from selfupdate)
> MacPorts base version 1.700 installed
> DEBUG: Rebuilding and reinstalling MacPorts if needed
> Downloaded MacPorts base version 1.600
> 
> The MacPorts installation is not outdated so it was not updated
> DEBUG: Setting MacPorts sources ownership to root
> 
> note typo in "Downloaded MacPorts base version" message

Sorry if I'm being thick, but what typo? If you're referring to the fact
that it says it downloaded 1.600, that's actually correct. The sources
on the rsync server are still 1.6 because 1.7 final hasn't been released
yet.

- Josh

From frstan at bellsouth.net  Sun Dec  7 11:42:31 2008
From: frstan at bellsouth.net (William Davis)
Date: Sun, 7 Dec 2008 14:42:31 -0500
Subject: 1.7.0 release candidate 1 available for testing
In-Reply-To: <493C1F91.3040708@macports.org>
References: <493BABFF.7030200@macports.org> <493BB305.50500@macports.org>
	<A7194711-E7FA-4391-BB0E-A575BD82D08F@bellsouth.net>
	<493C1F91.3040708@macports.org>
Message-ID: <B19F84BE-9B04-48D9-BCD0-5E2E3BF1FC0D@bellsouth.net>


On Dec 7, 2008, at 2:10 PM, Joshua Root wrote:

> William Davis wrote:
>>
>> On Dec 7, 2008, at 6:27 AM, Joshua Root wrote:
>>
>>> Hmm, looks like the attachment was scrubbed in the archives, so  
>>> here's a
>>> link to the announcement on -dev:
>>>
>>> <http://lists.macosforge.org/pipermail/macports-dev/2008-December/006614.html 
>>> >
>>>
>>>
>>> - Josh
>>> _______________________________________________
>>> macports-users mailing list
>>> macports-users at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>
>> just this so far:
>>
>> (from selfupdate)
>> MacPorts base version 1.700 installed
>> DEBUG: Rebuilding and reinstalling MacPorts if needed
>> Downloaded MacPorts base version 1.600
>>
>> The MacPorts installation is not outdated so it was not updated
>> DEBUG: Setting MacPorts sources ownership to root
>>
>> note typo in "Downloaded MacPorts base version" message
>
> Sorry if I'm being thick, but what typo? If you're referring to the  
> fact
> that it says it downloaded 1.600, that's actually correct. The sources
> on the rsync server are still 1.6 because 1.7 final hasn't been  
> released
> yet.
>
> - Josh

neat! ok, then.   1.7 is looking very good, so much so that I have re- 
installed gnome.  For me, the acid test will be upgrading some basic  
gnome component and using the -R option.  Thanks to everyone for all  
the hard work!

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

Mundus vult decepi, ego non


From masschel at gmail.com  Sun Dec  7 13:23:03 2008
From: masschel at gmail.com (Bart Masschelein)
Date: Sun, 7 Dec 2008 22:23:03 +0100
Subject: Uninstall non-active packages
Message-ID: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>

Hi all,

Is there a way to get a list of the non-active packages, so one could  
do sth like sudo port uninstall <list>, or sudo port clean <list>? I  
never use the -u option (read: I only recently discovered it, and will  
start using it from now one ;-)), hence I have a lot of non-active  
packages laying around.

Or in short: how can I get rid of non-active packages, for which new  
versions are already installed?

Bart

From ryandesign at macports.org  Sun Dec  7 13:39:18 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 7 Dec 2008 15:39:18 -0600
Subject: Problems linking against OSG on OS X Tiger (on a Power PC)
In-Reply-To: <493BF25A.8030603@kacianka.at>
References: <493BF25A.8030603@kacianka.at>
Message-ID: <A786DE46-E8B1-40B1-BDD5-501293A69CA5@macports.org>

On Dec 7, 2008, at 09:57, Severin Kacianka wrote:

> I hope I do not ask a too obvious question, but I am just trying to  
> get familiar with OSG and in the process want to be able to compile  
> it on Linux and OS X. On Linux I have no problems compiling a  
> sample program like this:
> g++ -I /usr/local/include/osg/ -losg -losgViewer -o foo test.cpp
>
> On OS X I installed OS X via macports. First I tried to compile it  
> directly form the sources, but ran into the bug described here:
> http://trac.macports.org/ticket/17294
>
> Compiling and installing via macports worked fine.
> However if I try to compile a sample program I get the following  
> error:
>
> g++  -L/opt/local/lib/ -I/opt/local/include/  -losg -losgViewer -o  
> foo test.cpp
> /usr/bin/ld: warning can't open dynamic library: libOpenThreads. 
> 11.dylib referenced from: /opt/local/lib//libosg.dylib (checking  
> for undefined symbols may be affected) (No such file or directory,  
> errno = 2)
> /usr/bin/ld: warning can't open dynamic library: libosgGA.48.dylib  
> referenced from: /opt/local/lib//libosgViewer.dylib (checking for  
> undefined symbols may be affected) (No such file or directory,  
> errno = 2)
> /usr/bin/ld: warning can't open dynamic library: libosgText. 
> 48.dylib referenced from: /opt/local/lib//libosgViewer.dylib  
> (checking for undefined symbols may be affected) (No such file or  
> directory, errno = 2)
> /usr/bin/ld: warning can't open dynamic library: libosgDB.48.dylib  
> referenced from: /opt/local/lib//libosgViewer.dylib (checking for  
> undefined symbols may be affected) (No such file or directory,  
> errno = 2)
> /usr/bin/ld: warning can't open dynamic library: libosgUtil. 
> 48.dylib referenced from: /opt/local/lib//libosgViewer.dylib  
> (checking for undefined symbols may be affected) (No such file or  
> directory, errno = 2)
> /usr/bin/ld: Undefined symbols:
> *snip long list of symbols*
> collect2: ld returned 1 exit status
>
> So for some reason ld cannot find the references from the libraries  
> among each other. The directory looks like this:
>
> libOpenThreads.11.dylib -> libOpenThreads.2.3.0.dylib
> libOpenThreads.2.3.0.dylib
> libOpenThreads.dylib -> libOpenThreads.11.dylib
>
>
> (other libs are linked in the same manner)
>
> So the libs are there, but somehow not referenced correctly. Does  
> anyone know what the problem may be, or any other way to use OSG on  
> OS X?

I see that it's linked this way:

$ otool -L /opt/local/lib/libosg.dylib
/opt/local/lib/libosg.dylib:
         libosg.48.dylib (compatibility version 48.0.0, current  
version 2.6.1)
         libOpenThreads.11.dylib (compatibility version 11.0.0,  
current version 2.3.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,  
current version 88.3.10)
         /System/Library/Frameworks/AGL.framework/Versions/A/AGL  
(compatibility version 1.0.0, current version 1.0.0)
         /System/Library/Frameworks/OpenGL.framework/Versions/A/ 
OpenGL (compatibility version 1.0.0, current version 1.0.0)
         /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)
$

That looks wrong. It should look like this:

$ otool -L /opt/local/lib/libosg.dylib
/opt/local/lib/libosg.dylib:
         /opt/local/lib/libosg.48.dylib (compatibility version  
48.0.0, current version 2.6.1)
         /opt/local/lib/libOpenThreads.11.dylib (compatibility  
version 11.0.0, current version 2.3.0)
         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,  
current version 88.3.10)
         /System/Library/Frameworks/AGL.framework/Versions/A/AGL  
(compatibility version 1.0.0, current version 1.0.0)
         /System/Library/Frameworks/OpenGL.framework/Versions/A/ 
OpenGL (compatibility version 1.0.0, current version 1.0.0)
         /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)
$

This probably means they're not using the -install_name parameter.


From ryandesign at macports.org  Sun Dec  7 13:40:32 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 7 Dec 2008 15:40:32 -0600
Subject: Uninstall non-active packages
In-Reply-To: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>
References: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>
Message-ID: <FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>


On Dec 7, 2008, at 15:23, Bart Masschelein wrote:

> Is there a way to get a list of the non-active packages, so one  
> could do sth like sudo port uninstall <list>, or sudo port clean  
> <list>? I never use the -u option (read: I only recently discovered  
> it, and will start using it from now one ;-)), hence I have a lot  
> of non-active packages laying around.
>
> Or in short: how can I get rid of non-active packages, for which  
> new versions are already installed?

Sure:

sudo port uninstall inactive

Note that this won't quite work right in MacPorts 1.6.0: it will  
complain that you are uninstalling a dependency of another port, even  
though you're not, really -- you have newer versions active already.  
In MacPorts 1.7.0 this will work right. Until then, you need to force  
it with:

sudo port -f uninstall inactive




From masschel at gmail.com  Sun Dec  7 13:48:54 2008
From: masschel at gmail.com (Bart Masschelein)
Date: Sun, 7 Dec 2008 22:48:54 +0100
Subject: Uninstall non-active packages
In-Reply-To: <FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
References: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>
	<FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
Message-ID: <42B84F86-AA3C-4E61-82AC-D0CFD6B338D4@gmail.com>

Lucky I installed 1.7.0 half an hour ago then ;-). Will give it try...


On 07 Dec 2008, at 22:40, Ryan Schmidt wrote:

>
> On Dec 7, 2008, at 15:23, Bart Masschelein wrote:
>
>> Is there a way to get a list of the non-active packages, so one  
>> could do sth like sudo port uninstall <list>, or sudo port clean  
>> <list>? I never use the -u option (read: I only recently discovered  
>> it, and will start using it from now one ;-)), hence I have a lot  
>> of non-active packages laying around.
>>
>> Or in short: how can I get rid of non-active packages, for which  
>> new versions are already installed?
>
> Sure:
>
> sudo port uninstall inactive
>
> Note that this won't quite work right in MacPorts 1.6.0: it will  
> complain that you are uninstalling a dependency of another port,  
> even though you're not, really -- you have newer versions active  
> already. In MacPorts 1.7.0 this will work right. Until then, you  
> need to force it with:
>
> sudo port -f uninstall inactive
>
>
>


From masschel at gmail.com  Sun Dec  7 13:57:08 2008
From: masschel at gmail.com (Bart Masschelein)
Date: Sun, 7 Dec 2008 22:57:08 +0100
Subject: Uninstall non-active packages
In-Reply-To: <FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
References: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>
	<FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
Message-ID: <9C044C29-4305-40D8-8817-42AC48E528F6@gmail.com>

Hi Ryan,

Not so sweet as you mention ;-). I get

--->  Unable to uninstall perl5 5.8.8_0+darwin_9, the following ports  
depend on it:
--->  	autoconf
--->  	automake
Error: port uninstall failed: Please uninstall the ports that depend  
on perl5 first.

I have 5.8.8_3 installed, which is the active one. When I use the -f  
option, I get:

--->  Unable to uninstall perl5 5.8.8_0+darwin_9, the following ports  
depend on it:
--->  	autoconf
--->  	automake
Warning: Uninstall forced.  Proceeding despite dependencies.

I guess I will see if this was  a clever idea when I recompile one of  
my repositories...

But indeed, my inactive ports are gone now. Thanks. Inactive, saved in  
memory ;-).

Bart

On 07 Dec 2008, at 22:40, Ryan Schmidt wrote:

>
> On Dec 7, 2008, at 15:23, Bart Masschelein wrote:
>
>> Is there a way to get a list of the non-active packages, so one  
>> could do sth like sudo port uninstall <list>, or sudo port clean  
>> <list>? I never use the -u option (read: I only recently discovered  
>> it, and will start using it from now one ;-)), hence I have a lot  
>> of non-active packages laying around.
>>
>> Or in short: how can I get rid of non-active packages, for which  
>> new versions are already installed?
>
> Sure:
>
> sudo port uninstall inactive
>
> Note that this won't quite work right in MacPorts 1.6.0: it will  
> complain that you are uninstalling a dependency of another port,  
> even though you're not, really -- you have newer versions active  
> already. In MacPorts 1.7.0 this will work right. Until then, you  
> need to force it with:
>
> sudo port -f uninstall inactive
>
>
>


From masschel at gmail.com  Sun Dec  7 14:01:26 2008
From: masschel at gmail.com (Bart Masschelein)
Date: Sun, 7 Dec 2008 23:01:26 +0100
Subject: Uninstall non-active packages
In-Reply-To: <FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
References: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>
	<FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
Message-ID: <49886846-BB84-4BDF-8AE1-223A2B616688@gmail.com>

Small side-question: why is 'inactive' not available from the  
interactive console?


On 07 Dec 2008, at 22:40, Ryan Schmidt wrote:

>
> On Dec 7, 2008, at 15:23, Bart Masschelein wrote:
>
>> Is there a way to get a list of the non-active packages, so one  
>> could do sth like sudo port uninstall <list>, or sudo port clean  
>> <list>? I never use the -u option (read: I only recently discovered  
>> it, and will start using it from now one ;-)), hence I have a lot  
>> of non-active packages laying around.
>>
>> Or in short: how can I get rid of non-active packages, for which  
>> new versions are already installed?
>
> Sure:
>
> sudo port uninstall inactive
>
> Note that this won't quite work right in MacPorts 1.6.0: it will  
> complain that you are uninstalling a dependency of another port,  
> even though you're not, really -- you have newer versions active  
> already. In MacPorts 1.7.0 this will work right. Until then, you  
> need to force it with:
>
> sudo port -f uninstall inactive
>
>
>


From jmr at macports.org  Sun Dec  7 14:30:51 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 08 Dec 2008 09:30:51 +1100
Subject: Uninstall non-active packages
In-Reply-To: <49886846-BB84-4BDF-8AE1-223A2B616688@gmail.com>
References: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>	<FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
	<49886846-BB84-4BDF-8AE1-223A2B616688@gmail.com>
Message-ID: <493C4E9B.4050004@macports.org>

Bart Masschelein wrote:
> Small side-question: why is 'inactive' not available from the
> interactive console?

I just tested, and it works in interactive mode. Note that 'inactive'
specifies a set of ports, it's not an action. So to see the list of
inactive ports, you'd use "port echo inactive".

- Josh

From jmr at macports.org  Sun Dec  7 14:32:36 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 08 Dec 2008 09:32:36 +1100
Subject: Uninstall non-active packages
In-Reply-To: <9C044C29-4305-40D8-8817-42AC48E528F6@gmail.com>
References: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>	<FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
	<9C044C29-4305-40D8-8817-42AC48E528F6@gmail.com>
Message-ID: <493C4F04.9010300@macports.org>

Bart Masschelein wrote:
> Hi Ryan,
> 
> Not so sweet as you mention ;-). I get
> 
> --->  Unable to uninstall perl5 5.8.8_0+darwin_9, the following ports
> depend on it:
> --->      autoconf
> --->      automake
> Error: port uninstall failed: Please uninstall the ports that depend on
> perl5 first.
> 
> I have 5.8.8_3 installed, which is the active one. When I use the -f
> option, I get:
> 
> --->  Unable to uninstall perl5 5.8.8_0+darwin_9, the following ports
> depend on it:
> --->      autoconf
> --->      automake
> Warning: Uninstall forced.  Proceeding despite dependencies.

This is due to the recent creation of a perl5 port, which installs the
same files as perl5.8, so only one can be active at a time. Some ports
depend on perl5.8, some on perl5, so the dependency error is most likely
correct.

- Josh

From masschel at gmail.com  Sun Dec  7 14:38:39 2008
From: masschel at gmail.com (Bart Masschelein)
Date: Sun, 7 Dec 2008 23:38:39 +0100
Subject: Uninstall non-active packages
In-Reply-To: <493C4E9B.4050004@macports.org>
References: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>	<FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
	<49886846-BB84-4BDF-8AE1-223A2B616688@gmail.com>
	<493C4E9B.4050004@macports.org>
Message-ID: <B00D5ECD-E575-42F7-B4A4-B6FFD4F64A0D@gmail.com>


On 07 Dec 2008, at 23:30, Joshua Root wrote:

> Bart Masschelein wrote:
>> Small side-question: why is 'inactive' not available from the
>> interactive console?
>
> I just tested, and it works in interactive mode. Note that 'inactive'
> specifies a set of ports, it's not an action. So to see the list of
> inactive ports, you'd use "port echo inactive".

Right. But isn't the same true for 'installed', and this works without  
echo. You get different formatting, though.

Bart

From masschel at gmail.com  Sun Dec  7 14:40:14 2008
From: masschel at gmail.com (Bart Masschelein)
Date: Sun, 7 Dec 2008 23:40:14 +0100
Subject: Uninstall non-active packages
In-Reply-To: <493C4F04.9010300@macports.org>
References: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>	<FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
	<9C044C29-4305-40D8-8817-42AC48E528F6@gmail.com>
	<493C4F04.9010300@macports.org>
Message-ID: <02667C9E-B48D-4013-948D-AFED0AD2C050@gmail.com>


On 07 Dec 2008, at 23:32, Joshua Root wrote:

> Bart Masschelein wrote:
>> Hi Ryan,
>>
>> Not so sweet as you mention ;-). I get
>>
>> --->  Unable to uninstall perl5 5.8.8_0+darwin_9, the following ports
>> depend on it:
>> --->      autoconf
>> --->      automake
>> Error: port uninstall failed: Please uninstall the ports that  
>> depend on
>> perl5 first.
>>
>> I have 5.8.8_3 installed, which is the active one. When I use the -f
>> option, I get:
>>
>> --->  Unable to uninstall perl5 5.8.8_0+darwin_9, the following ports
>> depend on it:
>> --->      autoconf
>> --->      automake
>> Warning: Uninstall forced.  Proceeding despite dependencies.
>
> This is due to the recent creation of a perl5 port, which installs the
> same files as perl5.8, so only one can be active at a time. Some ports
> depend on perl5.8, some on perl5, so the dependency error is most  
> likely
> correct.

So what I have done could potentially create problems, unless 'the  
same files' are as well in the same location, and the involved ports  
find their way?

Bart


From jmr at macports.org  Sun Dec  7 14:46:22 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 08 Dec 2008 09:46:22 +1100
Subject: Uninstall non-active packages
In-Reply-To: <B00D5ECD-E575-42F7-B4A4-B6FFD4F64A0D@gmail.com>
References: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>	<FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
	<49886846-BB84-4BDF-8AE1-223A2B616688@gmail.com>
	<493C4E9B.4050004@macports.org>
	<B00D5ECD-E575-42F7-B4A4-B6FFD4F64A0D@gmail.com>
Message-ID: <493C523E.4010402@macports.org>

Bart Masschelein wrote:
> 
> On 07 Dec 2008, at 23:30, Joshua Root wrote:
> 
>> Bart Masschelein wrote:
>>> Small side-question: why is 'inactive' not available from the
>>> interactive console?
>>
>> I just tested, and it works in interactive mode. Note that 'inactive'
>> specifies a set of ports, it's not an action. So to see the list of
>> inactive ports, you'd use "port echo inactive".
> 
> Right. But isn't the same true for 'installed', and this works without
> echo. You get different formatting, though.

Yes, 'installed' has the dubious distinction of being both an action and
a pseudo-port. For historical reasons.

- Josh

From jmr at macports.org  Sun Dec  7 14:49:23 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 08 Dec 2008 09:49:23 +1100
Subject: Uninstall non-active packages
In-Reply-To: <02667C9E-B48D-4013-948D-AFED0AD2C050@gmail.com>
References: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>	<FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
	<9C044C29-4305-40D8-8817-42AC48E528F6@gmail.com>
	<493C4F04.9010300@macports.org>
	<02667C9E-B48D-4013-948D-AFED0AD2C050@gmail.com>
Message-ID: <493C52F3.3080305@macports.org>

Bart Masschelein wrote:
> 
> On 07 Dec 2008, at 23:32, Joshua Root wrote:
> 
>> Bart Masschelein wrote:
>>> Hi Ryan,
>>>
>>> Not so sweet as you mention ;-). I get
>>>
>>> --->  Unable to uninstall perl5 5.8.8_0+darwin_9, the following ports
>>> depend on it:
>>> --->      autoconf
>>> --->      automake
>>> Error: port uninstall failed: Please uninstall the ports that depend on
>>> perl5 first.
>>>
>>> I have 5.8.8_3 installed, which is the active one. When I use the -f
>>> option, I get:
>>>
>>> --->  Unable to uninstall perl5 5.8.8_0+darwin_9, the following ports
>>> depend on it:
>>> --->      autoconf
>>> --->      automake
>>> Warning: Uninstall forced.  Proceeding despite dependencies.
>>
>> This is due to the recent creation of a perl5 port, which installs the
>> same files as perl5.8, so only one can be active at a time. Some ports
>> depend on perl5.8, some on perl5, so the dependency error is most likely
>> correct.
> 
> So what I have done could potentially create problems, unless 'the same
> files' are as well in the same location, and the involved ports find
> their way?

No, what the perl maintainers have done could potentially create (has
definitely created?) problems. You're innocent this time. ;-)

The same files are in the same location, which is why there is a conflict.

- Josh

From frstan at bellsouth.net  Sun Dec  7 15:32:11 2008
From: frstan at bellsouth.net (William Davis)
Date: Sun, 7 Dec 2008 18:32:11 -0500
Subject: macports 1.7.0  and gnome
Message-ID: <92EE925B-995A-4975-91E8-E6CBA636F421@bellsouth.net>

using MacPorts 1.7.0_rc1 to install gnome (sudo port -d install gnome)  
I got this error
-->  Activating gnome-session @2.24.1_0
Error: Target org.macports.activate returned: Image error: /opt/local/ 
share/xsessions/gnome.desktop is being used by the active gdm port.   
Please deactivate this port first, or use the -f flag to force the  
activation.
Warning: the following items did not execute (for gnome-session):  
org.macports.activate
Error: The following dependencies failed to build: gnome-desktop-suite  
gnome-session gnome-system-monitor gtkmm cairomm libsigcxx2 glibmm  
pangomm gnome-terminal gnome-user-docs gnome-utils gnopernicus libgail- 
gnome libgtkhtml3 seahorse avahi dbus-python25 libdaemon py25-gdbm  
gpgme gnupg pth vino yelp firefox-x11 zenity
Error: Status 1 encountered during processing.

I did
sudo port -df activate gnome-session
and then resumed the install with
sudo port -d install gnome
was this correct?


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

Mundus vult decepi, ego non


From jmr at macports.org  Sun Dec  7 15:36:40 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 08 Dec 2008 10:36:40 +1100
Subject: macports 1.7.0  and gnome
In-Reply-To: <92EE925B-995A-4975-91E8-E6CBA636F421@bellsouth.net>
References: <92EE925B-995A-4975-91E8-E6CBA636F421@bellsouth.net>
Message-ID: <493C5E08.6090000@macports.org>

William Davis wrote:
> using MacPorts 1.7.0_rc1 to install gnome (sudo port -d install gnome) I
> got this error
> -->  Activating gnome-session @2.24.1_0
> Error: Target org.macports.activate returned: Image error:
> /opt/local/share/xsessions/gnome.desktop is being used by the active gdm
> port.  Please deactivate this port first, or use the -f flag to force
> the activation.
> Warning: the following items did not execute (for gnome-session):
> org.macports.activate
> Error: The following dependencies failed to build: gnome-desktop-suite
> gnome-session gnome-system-monitor gtkmm cairomm libsigcxx2 glibmm
> pangomm gnome-terminal gnome-user-docs gnome-utils gnopernicus
> libgail-gnome libgtkhtml3 seahorse avahi dbus-python25 libdaemon
> py25-gdbm gpgme gnupg pth vino yelp firefox-x11 zenity
> Error: Status 1 encountered during processing.
> 
> I did
> sudo port -df activate gnome-session
> and then resumed the install with
> sudo port -d install gnome
> was this correct?

I guess whether it will work or not depends on what the gnome.desktop
file does. In any case, gdm and/or gnome-session need to be modified so
they don't conflict.

- Josh

From frstan at bellsouth.net  Sun Dec  7 15:53:08 2008
From: frstan at bellsouth.net (William Davis)
Date: Sun, 7 Dec 2008 18:53:08 -0500
Subject: macports 1.7.0  and gnome
In-Reply-To: <493C5E08.6090000@macports.org>
References: <92EE925B-995A-4975-91E8-E6CBA636F421@bellsouth.net>
	<493C5E08.6090000@macports.org>
Message-ID: <FDC8E28C-D31E-48A9-A277-D249D3675D8C@bellsouth.net>


On Dec 7, 2008, at 6:36 PM, Joshua Root wrote:

> William Davis wrote:
>> using MacPorts 1.7.0_rc1 to install gnome (sudo port -d install  
>> gnome) I
>> got this error
>> -->  Activating gnome-session @2.24.1_0
>> Error: Target org.macports.activate returned: Image error:
>> /opt/local/share/xsessions/gnome.desktop is being used by the  
>> active gdm
>> port.  Please deactivate this port first, or use the -f flag to force
>> the activation.
>> Warning: the following items did not execute (for gnome-session):
>> org.macports.activate
>> Error: The following dependencies failed to build: gnome-desktop- 
>> suite
>> gnome-session gnome-system-monitor gtkmm cairomm libsigcxx2 glibmm
>> pangomm gnome-terminal gnome-user-docs gnome-utils gnopernicus
>> libgail-gnome libgtkhtml3 seahorse avahi dbus-python25 libdaemon
>> py25-gdbm gpgme gnupg pth vino yelp firefox-x11 zenity
>> Error: Status 1 encountered during processing.
>>
>> I did
>> sudo port -df activate gnome-session
>> and then resumed the install with
>> sudo port -d install gnome
>> was this correct?
>
> I guess whether it will work or not depends on what the gnome.desktop
> file does. In any case, gdm and/or gnome-session need to be modified  
> so
> they don't conflict.
>
> - Josh

I created Ticket #17567 (new defect) for this.

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.5 Darwin 9.5.0
XQuartz 2.3.2_rc3 (xorg-server 1.4.2-apple27)
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/20081207/998e9898/attachment.html>

From admin2 at enabled.com  Sun Dec  7 22:33:14 2008
From: admin2 at enabled.com (Admin)
Date: Sun, 07 Dec 2008 22:33:14 -0800
Subject: Image error: /opt/local/bin/a2p is being used by the active perl5.8
	port
Message-ID: <493CBFAA.6050106@enabled.com>


Hi there,

I am getting an image error: "Image error: /opt/local/bin/a2p is being 
used by the active perl5.8 port"

The error message explains the trouble well but I dont really understand 
how I can fix the problem.

I want the macports perl5.8 to be the active perl binary on my OSX machine

running 10.5 on a dual G5


here is the entire output from the build


--- snip ---

sh-3.2# port install wireshark
--->  Configuring expat
--->  Building expat with target all
--->  Staging expat into destroot
--->  Installing expat 2.0.1_0
--->  Activating expat 2.0.1_0
--->  Cleaning expat
--->  Fetching gperf
--->  Attempting to fetch gperf-3.0.3.tar.gz from 
http://ftp.gnu.org/gnu/gperf
--->  Verifying checksum(s) for gperf
--->  Extracting gperf
--->  Configuring gperf
--->  Building gperf with target all
--->  Staging gperf into destroot
--->  Installing gperf 3.0.3_0
--->  Activating gperf 3.0.3_0
--->  Cleaning gperf
--->  Fetching libiconv
--->  Attempting to fetch libiconv-1.12.tar.gz from 
http://ftp.gnu.org/gnu/libiconv
--->  Verifying checksum(s) for libiconv
--->  Extracting libiconv
--->  Applying patches to libiconv
--->  Configuring libiconv
--->  Building libiconv with target all
--->  Staging libiconv into destroot
--->  Installing libiconv 1.12_0
--->  Activating libiconv 1.12_0
--->  Cleaning libiconv
--->  Fetching ncursesw
--->  Attempting to fetch ncurses-5.7.tar.gz from 
http://ftp.gnu.org/gnu/ncurses
--->  Verifying checksum(s) for ncursesw
--->  Extracting ncursesw
--->  Configuring ncursesw
--->  Building ncursesw with target all
--->  Staging ncursesw into destroot
--->  Installing ncursesw 5.7_0
--->  Activating ncursesw 5.7_0
--->  Cleaning ncursesw
--->  Fetching ncurses
--->  Verifying checksum(s) for ncurses
--->  Extracting ncurses
--->  Configuring ncurses
--->  Building ncurses with target all
--->  Staging ncurses into destroot
--->  Installing ncurses 5.7_0
--->  Activating ncurses 5.7_0
--->  Cleaning ncurses
--->  Fetching gettext
--->  Attempting to fetch gettext-0.17.tar.gz from 
http://ftp.gnu.org/gnu/gettext
--->  Verifying checksum(s) for gettext
--->  Extracting gettext
--->  Applying patches to gettext
--->  Configuring gettext
--->  Building gettext with target all
--->  Staging gettext into destroot
--->  Installing gettext 0.17_3
--->  Activating gettext 0.17_3
--->  Cleaning gettext
--->  Fetching pkgconfig
--->  Attempting to fetch pkg-config-0.23.tar.gz from 
http://pkg-config.freedesktop.org/releases/
--->  Verifying checksum(s) for pkgconfig
--->  Extracting pkgconfig
--->  Configuring pkgconfig
--->  Building pkgconfig with target all
--->  Staging pkgconfig into destroot
--->  Installing pkgconfig 0.23_1
--->  Activating pkgconfig 0.23_1
--->  Cleaning pkgconfig
--->  Fetching glib2
--->  Attempting to fetch glib-2.18.3.tar.bz2 from 
http://mandril.creatis.insa-lyon.fr/linux/gnome.org/sources/glib/2.18/
--->  Verifying checksum(s) for glib2
--->  Extracting glib2
--->  Applying patches to glib2
--->  Configuring glib2
--->  Building glib2 with target all
--->  Staging glib2 into destroot
--->  Installing glib2 2.18.3_0+darwin_9
--->  Activating glib2 2.18.3_0+darwin_9
--->  Cleaning glib2
--->  Fetching atk
--->  Attempting to fetch atk-1.24.0.tar.bz2 from 
http://mandril.creatis.insa-lyon.fr/linux/gnome.org/sources/atk/1.24/
--->  Verifying checksum(s) for atk
--->  Extracting atk
--->  Configuring atk
--->  Building atk with target all
--->  Staging atk into destroot
--->  Installing atk 1.24.0_0
--->  Activating atk 1.24.0_0
--->  Cleaning atk
--->  Building zlib with target all
--->  Staging zlib into destroot
--->  Installing zlib 1.2.3_2
--->  Activating zlib 1.2.3_2
--->  Cleaning zlib
--->  Fetching freetype
--->  Attempting to fetch freetype-2.3.7.tar.bz2 from 
http://download.savannah.gnu.org/releases/freetype/
--->  Attempting to fetch freetype-doc-2.3.7.tar.bz2 from 
http://download.savannah.gnu.org/releases/freetype/
--->  Verifying checksum(s) for freetype
--->  Extracting freetype
--->  Applying patches to freetype
--->  Configuring freetype
--->  Building freetype with target all
--->  Staging freetype into destroot
--->  Installing freetype 2.3.7_3+macosx
--->  Activating freetype 2.3.7_3+macosx
--->  Cleaning freetype
--->  Fetching fontconfig
--->  Attempting to fetch fontconfig-2.6.0.tar.gz from 
http://fontconfig.org/release/
--->  Verifying checksum(s) for fontconfig
--->  Extracting fontconfig
--->  Configuring fontconfig
--->  Building fontconfig with target all
--->  Staging fontconfig into destroot
--->  Installing fontconfig 2.6.0_0+macosx
--->  Activating fontconfig 2.6.0_0+macosx
--->  Cleaning fontconfig
--->  Fetching libpixman
--->  Attempting to fetch pixman-0.12.0.tar.bz2 from 
http://www.x.org/pub/individual/lib/
--->  Verifying checksum(s) for libpixman
--->  Extracting libpixman
--->  Configuring libpixman
--->  Building libpixman with target all
--->  Staging libpixman into destroot
--->  Installing libpixman 0.12.0_1
--->  Activating libpixman 0.12.0_1
--->  Cleaning libpixman
--->  Fetching libpng
--->  Attempting to fetch libpng-1.2.33.tar.bz2 from 
http://downloads.sourceforge.net/libpng
--->  Verifying checksum(s) for libpng
--->  Extracting libpng
--->  Configuring libpng
--->  Building libpng with target all
--->  Staging libpng into destroot
--->  Installing libpng 1.2.33_0
--->  Activating libpng 1.2.33_0
--->  Cleaning libpng
--->  Fetching render
--->  Verifying checksum(s) for render
--->  Extracting render
--->  Configuring render
--->  Building render with target all
--->  Staging render into destroot
--->  Installing render 0.9.2_0
--->  Activating render 0.9.2_0
--->  Cleaning render
--->  Fetching xorg-renderproto
--->  Attempting to fetch renderproto-0.9.3.tar.bz2 from 
http://www.x.org/pub/individual/proto/
--->  Verifying checksum(s) for xorg-renderproto
--->  Extracting xorg-renderproto
--->  Configuring xorg-renderproto
--->  Building xorg-renderproto with target all
--->  Staging xorg-renderproto into destroot
--->  Installing xorg-renderproto 0.9.3_0
--->  Activating xorg-renderproto 0.9.3_0
--->  Cleaning xorg-renderproto
--->  Fetching xrender
--->  Attempting to fetch libXrender-0.9.4.tar.bz2 from 
http://www.x.org/archive/individual/lib/
--->  Verifying checksum(s) for xrender
--->  Extracting xrender
--->  Configuring xrender
--->  Building xrender with target all
--->  Staging xrender into destroot
--->  Installing xrender 0.9.4_1+macosx
--->  Activating xrender 0.9.4_1+macosx
--->  Cleaning xrender
--->  Fetching cairo
--->  Attempting to fetch cairo-1.8.4.tar.gz from 
http://cairographics.org/releases/
--->  Verifying checksum(s) for cairo
--->  Extracting cairo
--->  Configuring cairo
--->  Building cairo with target all
--->  Staging cairo into destroot
--->  Installing cairo 1.8.4_0+macosx
--->  Activating cairo 1.8.4_0+macosx
--->  Cleaning cairo
--->  Fetching jpeg
--->  Attempting to fetch jpegsrc.v6b.tar.gz from http://www.ijg.org/files
--->  Attempting to fetch droppatch.tar.gz from http://sylvana.net/jpegcrop/
--->  Verifying checksum(s) for jpeg
--->  Extracting jpeg
--->  Applying patches to jpeg
--->  Configuring jpeg
--->  Building jpeg with target all
--->  Staging jpeg into destroot
--->  Installing jpeg 6b_3
--->  Activating jpeg 6b_3
--->  Cleaning jpeg
--->  Fetching jasper
--->  Attempting to fetch jasper-1.900.1.zip from 
http://www.ece.uvic.ca/~mdadams/jasper/software/
--->  Verifying checksum(s) for jasper
--->  Extracting jasper
--->  Applying patches to jasper
--->  Configuring jasper
--->  Building jasper with target all
--->  Staging jasper into destroot
--->  Installing jasper 1.900.1_2+darwin_9
--->  Activating jasper 1.900.1_2+darwin_9
--->  Cleaning jasper
--->  Fetching xorg-xproto
--->  Attempting to fetch xproto-7.0.14.tar.bz2 from 
http://www.x.org/pub/individual/proto/
--->  Verifying checksum(s) for xorg-xproto
--->  Extracting xorg-xproto
--->  Configuring xorg-xproto
--->  Building xorg-xproto with target all
--->  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://xorg.freedesktop.org/releases/individual/lib/
--->  Verifying checksum(s) for Xft2
--->  Extracting Xft2
--->  Configuring Xft2
--->  Building Xft2 with target all
--->  Staging Xft2 into destroot
--->  Installing Xft2 2.1.13_0
--->  Activating Xft2 2.1.13_0
--->  Cleaning Xft2
--->  Fetching pango
--->  Attempting to fetch pango-1.22.3.tar.bz2 from 
http://mandril.creatis.insa-lyon.fr/linux/gnome.org/sources/pango/1.22
--->  Verifying checksum(s) for pango
--->  Extracting pango
--->  Applying patches to pango
--->  Configuring pango
--->  Building pango with target all
--->  Staging pango into destroot
--->  Installing pango 1.22.3_0
--->  Activating pango 1.22.3_0
--->  Cleaning pango
--->  Fetching gnome-common
--->  Attempting to fetch gnome-common-2.24.0.tar.bz2 from 
http://mandril.creatis.insa-lyon.fr/linux/gnome.org/sources/gnome-common/2.24/
--->  Verifying checksum(s) for gnome-common
--->  Extracting gnome-common
--->  Applying patches to gnome-common
--->  Configuring gnome-common
--->  Building gnome-common with target all
--->  Staging gnome-common into destroot
--->  Installing gnome-common 2.24.0_1
--->  Activating gnome-common 2.24.0_1
--->  Cleaning gnome-common
--->  Fetching perl5.8
--->  Attempting to fetch perl-5.8.8.tar.bz2 from 
http://www.cpan.org/src/5.0/
--->  Verifying checksum(s) for perl5.8
--->  Extracting perl5.8
--->  Applying patches to perl5.8
--->  Configuring perl5.8
--->  Building perl5.8 with target all
--->  Staging perl5.8 into destroot
--->  Installing perl5.8 5.8.8_3+darwin_9
--->  Activating perl5.8 5.8.8_3+darwin_9
--->  Cleaning perl5.8
--->  Fetching p5-xml-parser
--->  Attempting to fetch XML-Parser-2.36.tar.gz from 
http://ftp.ucr.ac.cr/Unix/CPAN/modules/by-module/XML
--->  Verifying checksum(s) for p5-xml-parser
--->  Extracting p5-xml-parser
--->  Configuring p5-xml-parser
--->  Building p5-xml-parser with target all
--->  Staging p5-xml-parser into destroot
--->  Installing p5-xml-parser 2.36_0
--->  Activating p5-xml-parser 2.36_0
--->  Cleaning p5-xml-parser
--->  Fetching perl5
--->  Attempting to fetch perl-5.8.8.tar.bz2 from http://www.cpan.org/src/
--->  Verifying checksum(s) for perl5
--->  Extracting perl5
--->  Applying patches to perl5
--->  Configuring perl5
--->  Building perl5 with target all
--->  Staging perl5 into destroot
--->  Installing perl5 5.8.8_0+darwin_9
--->  Activating perl5 5.8.8_0+darwin_9
Error: Target org.macports.activate returned: Image error: 
/opt/local/bin/a2p 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: gtk2 shared-mime-info 
intltool perl5 libxml2 tiff libpcap openssl
Error: Status 1 encountered during processing.
sh-3.2#



From blb at macports.org  Sun Dec  7 23:03:51 2008
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 8 Dec 2008 00:03:51 -0700
Subject: Image error: /opt/local/bin/a2p is being used by the active
	perl5.8 port
In-Reply-To: <493CBFAA.6050106@enabled.com>
References: <493CBFAA.6050106@enabled.com>
Message-ID: <20081208070351.GN506@ninagal.withay.com>

On Sun, Dec 07, 2008 at 10:33:14PM -0800, Admin said:
>
> Hi there,
>
> I am getting an image error: "Image error: /opt/local/bin/a2p is being  
> used by the active perl5.8 port"
>
> The error message explains the trouble well but I dont really understand  
> how I can fix the problem.
>
> I want the macports perl5.8 to be the active perl binary on my OSX machine
>
> running 10.5 on a dual G5
>
>
> here is the entire output from the build
>
>
> --- snip ---
>
> sh-3.2# port install wireshark
[...]
> --->  Activating perl5 5.8.8_0+darwin_9
> Error: Target org.macports.activate returned: Image error:  
> /opt/local/bin/a2p is being used by the active perl5.8 port.  Please  

See if

<http://trac.macports.org/wiki/ProblemHotlist#perl5-image-error>

helps out for this.

Bryan


From ryandesign at macports.org  Sun Dec  7 23:16:37 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 8 Dec 2008 01:16:37 -0600
Subject: Problems linking against OSG on OS X Tiger (on a Power PC)
In-Reply-To: <A786DE46-E8B1-40B1-BDD5-501293A69CA5@macports.org>
References: <493BF25A.8030603@kacianka.at>
	<A786DE46-E8B1-40B1-BDD5-501293A69CA5@macports.org>
Message-ID: <59540D99-8712-4C8F-849B-02F03F4B39CB@macports.org>

On Dec 7, 2008, at 15:39, Ryan Schmidt wrote:

> On Dec 7, 2008, at 09:57, Severin Kacianka wrote:
>
>> I hope I do not ask a too obvious question, but I am just trying  
>> to get familiar with OSG and in the process want to be able to  
>> compile it on Linux and OS X. On Linux I have no problems  
>> compiling a sample program like this:
>> g++ -I /usr/local/include/osg/ -losg -losgViewer -o foo test.cpp
>>
>> On OS X I installed OS X via macports. First I tried to compile it  
>> directly form the sources, but ran into the bug described here:
>> http://trac.macports.org/ticket/17294
>>
>> Compiling and installing via macports worked fine.
>> However if I try to compile a sample program I get the following  
>> error:
>>
>> g++  -L/opt/local/lib/ -I/opt/local/include/  -losg -losgViewer -o  
>> foo test.cpp
>> /usr/bin/ld: warning can't open dynamic library: libOpenThreads. 
>> 11.dylib referenced from: /opt/local/lib//libosg.dylib (checking  
>> for undefined symbols may be affected) (No such file or directory,  
>> errno = 2)
>> /usr/bin/ld: warning can't open dynamic library: libosgGA.48.dylib  
>> referenced from: /opt/local/lib//libosgViewer.dylib (checking for  
>> undefined symbols may be affected) (No such file or directory,  
>> errno = 2)
>> /usr/bin/ld: warning can't open dynamic library: libosgText. 
>> 48.dylib referenced from: /opt/local/lib//libosgViewer.dylib  
>> (checking for undefined symbols may be affected) (No such file or  
>> directory, errno = 2)
>> /usr/bin/ld: warning can't open dynamic library: libosgDB.48.dylib  
>> referenced from: /opt/local/lib//libosgViewer.dylib (checking for  
>> undefined symbols may be affected) (No such file or directory,  
>> errno = 2)
>> /usr/bin/ld: warning can't open dynamic library: libosgUtil. 
>> 48.dylib referenced from: /opt/local/lib//libosgViewer.dylib  
>> (checking for undefined symbols may be affected) (No such file or  
>> directory, errno = 2)
>> /usr/bin/ld: Undefined symbols:
>> *snip long list of symbols*
>> collect2: ld returned 1 exit status
>>
>> So for some reason ld cannot find the references from the  
>> libraries among each other. The directory looks like this:
>>
>> libOpenThreads.11.dylib -> libOpenThreads.2.3.0.dylib
>> libOpenThreads.2.3.0.dylib
>> libOpenThreads.dylib -> libOpenThreads.11.dylib
>>
>>
>> (other libs are linked in the same manner)
>>
>> So the libs are there, but somehow not referenced correctly. Does  
>> anyone know what the problem may be, or any other way to use OSG  
>> on OS X?
>
> I see that it's linked this way:
>
> $ otool -L /opt/local/lib/libosg.dylib
> /opt/local/lib/libosg.dylib:
>         libosg.48.dylib (compatibility version 48.0.0, current  
> version 2.6.1)
>         libOpenThreads.11.dylib (compatibility version 11.0.0,  
> current version 2.3.0)
>         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,  
> current version 88.3.10)
>         /System/Library/Frameworks/AGL.framework/Versions/A/AGL  
> (compatibility version 1.0.0, current version 1.0.0)
>         /System/Library/Frameworks/OpenGL.framework/Versions/A/ 
> OpenGL (compatibility version 1.0.0, current version 1.0.0)
>         /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)
> $
>
> That looks wrong. It should look like this:
>
> $ otool -L /opt/local/lib/libosg.dylib
> /opt/local/lib/libosg.dylib:
>         /opt/local/lib/libosg.48.dylib (compatibility version  
> 48.0.0, current version 2.6.1)
>         /opt/local/lib/libOpenThreads.11.dylib (compatibility  
> version 11.0.0, current version 2.3.0)
>         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,  
> current version 88.3.10)
>         /System/Library/Frameworks/AGL.framework/Versions/A/AGL  
> (compatibility version 1.0.0, current version 1.0.0)
>         /System/Library/Frameworks/OpenGL.framework/Versions/A/ 
> OpenGL (compatibility version 1.0.0, current version 1.0.0)
>         /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)
> $
>
> This probably means they're not using the -install_name parameter.

I filed a ticket:

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


From mcalhoun at macports.org  Sun Dec  7 23:19:50 2008
From: mcalhoun at macports.org (Marcus Calhoun-Lopez)
Date: Mon, 8 Dec 2008 07:19:50 +0000 (UTC)
Subject: Image error: /opt/local/bin/a2p is being used by the active
	=?utf-8?b?cGVybDUuOAlwb3J0?=
References: <493CBFAA.6050106@enabled.com>
Message-ID: <loom.20081208T065653-96@post.gmane.org>

Admin <admin2 <at> enabled.com> writes:
> 
> 
> Hi there,
> 
> I am getting an image error: "Image error: /opt/local/bin/a2p is being 
> used by the active perl5.8 port"

This was a bug in the perl5 Portfile, but hopefully it is fixed now.
See http://trac.macports.org/ticket/16830 for the gory details.

After about an hour after this message was sent, the changes
should propagate to where they need to be.

Run (perhaps using sudo):
port sync
port install wireshark

-Marcus


From lists-macports at shopwatch.org  Mon Dec  8 12:25:19 2008
From: lists-macports at shopwatch.org (Jay Levitt)
Date: Mon, 08 Dec 2008 15:25:19 -0500
Subject: 1.7.0 beta & rc1: libcurl errors
Message-ID: <493D82AF.5080203@shopwatch.org>

I know this isn't a great bug report, because I already overwrote the fail 
case; sorry about that.

I upgraded from a DMG-installed 1.6.0 to a built-from-source 1.7.0 beta 1. 
I then updated a bunch of ports, but I don't think libcurl was one of them. 
  (Is there a log?  I don't think there is.)

Today, I tried using git, and got:

dyld: Library not loaded: /opt/local/lib/libcurl.4.dylib
   Referenced from: /opt/local/bin/git
   Reason: Incompatible library version: git requires version 6.0.0 or 
later, but libcurl.4.dylib provides version 5.0.0

I tried to rebuild the port, but the port command had the same problem:

sudo port clean git
couldn't load file "/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib": 
dlopen(/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib, 10): Library 
not loaded: /opt/local/lib/libcurl.4.dylib
   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib
   Reason: Incompatible library version: Pextlib.dylib requires version 
6.0.0 or later, but libcurl.4.dylib provides version 5.0.0
     while executing
"load /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib"
     ("package ifneeded" script)
     invoked from within
"package require Pextlib 1.0"
     (file "/opt/local/bin/port" line 40)

I tried upgrading to 1.7.0rc1, but IT had the same problem:

$ svn switch http://svn.macports.org/repository/macports/tags/release_1_7_0-rc1
$ ./configure;make;sudo make install
[...]
/usr/bin/tclsh src/dep_map_clean.tcl /Library/Tcl
can't find package Pextlib 1.0
     while executing
"package require Pextlib 1.0"
     (file "/opt/local/share/macports/Tcl/registry1.0/receipt_flat.tcl" line 37)
     invoked from within
"source /opt/local/share/macports/Tcl/registry1.0/receipt_flat.tcl"
     ("package ifneeded" script)
     invoked from within
"package require receipt_flat 1.0"
     (file "/opt/local/share/macports/Tcl/registry1.0/registry.tcl" line 35)
     invoked from within
"source /opt/local/share/macports/Tcl/registry1.0/registry.tcl"
     ("package ifneeded" script)
     invoked from within
"package require registry 1.0"
     (file "src/dep_map_clean.tcl" line 10)
make: *** [install] Error 1

Finally, I did "make clean;make;sudo make install" which succeeded.  I was 
then able to get things working:

$ sudo port clean git-core
Portfile changed since last build; discarding previous state.
--->  Cleaning git-core
$ sudo port sync
$ sudo port install git-core
Error: Requested variants do not match original selection.
Please perform 'port clean curl' or specify the force option.
Error: The following dependencies failed to build: curl
Error: Status 1 encountered during processing.
$ sudo port clean curl
--->  Cleaning curl
$ sudo port install curl
--->  Activating curl @7.19.2_0
$ git version
git version 1.6.0.4
$

So, since I can't reproduce this anymore... consider this an FYI that 
something might be broken for people upgrading from 1.6.0.  Or it might not. 
  Probably one of the two.

Jay


From blb at macports.org  Mon Dec  8 13:41:14 2008
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 8 Dec 2008 14:41:14 -0700
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <493D82AF.5080203@shopwatch.org>
References: <493D82AF.5080203@shopwatch.org>
Message-ID: <20081208214114.GF506@ninagal.withay.com>

On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said:
> I know this isn't a great bug report, because I already overwrote the fail 
> case; sorry about that.
>
> I upgraded from a DMG-installed 1.6.0 to a built-from-source 1.7.0 beta 1. 
> I then updated a bunch of ports, but I don't think libcurl was one of 
> them.  (Is there a log?  I don't think there is.)
>
> Today, I tried using git, and got:
>
> dyld: Library not loaded: /opt/local/lib/libcurl.4.dylib
>   Referenced from: /opt/local/bin/git
>   Reason: Incompatible library version: git requires version 6.0.0 or  
> later, but libcurl.4.dylib provides version 5.0.0

Did you happen to activate an older version of the curl port?  What does
'port installed curl' say, as here, 7.19.2_0 is installed and libcurl has a
compat version of 6.0.0 and current 6.1.0.

>
> I tried to rebuild the port, but the port command had the same problem:
>
> sudo port clean git
> couldn't load file 
> "/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib":  
> dlopen(/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib, 10): 
> Library not loaded: /opt/local/lib/libcurl.4.dylib
>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib
>   Reason: Incompatible library version: Pextlib.dylib requires version  
> 6.0.0 or later, but libcurl.4.dylib provides version 5.0.0

This could be an issue with selfupdate as it should be linking Pextlib
against the system libcurl, not one found in MacPorts.  Will have to look
into this.

[...]
> I tried upgrading to 1.7.0rc1, but IT had the same problem:
>
> $ svn switch http://svn.macports.org/repository/macports/tags/release_1_7_0-rc1
> $ ./configure;make;sudo make install
> [...]
> /usr/bin/tclsh src/dep_map_clean.tcl /Library/Tcl
> can't find package Pextlib 1.0

Probably the above issue I'm guessing.

[...]
>
> Finally, I did "make clean;make;sudo make install" which succeeded.  I was 
> then able to get things working:

Suggesting selfupdate is picking up the MacPorts one instead since make
should be seeing the system libcurl properly.

>
> $ sudo port clean git-core
> Portfile changed since last build; discarding previous state.
> --->  Cleaning git-core
> $ sudo port sync
> $ sudo port install git-core
> Error: Requested variants do not match original selection.
> Please perform 'port clean curl' or specify the force option.
> Error: The following dependencies failed to build: curl
> Error: Status 1 encountered during processing.

That's interesting, definitely sounds like you have some oddities with the
curl port, which would explain the git issues mentioned above.

Bryan


> $ sudo port clean curl
> --->  Cleaning curl
> $ sudo port install curl
> --->  Activating curl @7.19.2_0
> $ git version
> git version 1.6.0.4
> $
>
> So, since I can't reproduce this anymore... consider this an FYI that  
> something might be broken for people upgrading from 1.6.0.  Or it might 
> not.  Probably one of the two.
>
> Jay
>

From ryandesign at macports.org  Mon Dec  8 14:19:41 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 8 Dec 2008 16:19:41 -0600
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <20081208214114.GF506@ninagal.withay.com>
References: <493D82AF.5080203@shopwatch.org>
	<20081208214114.GF506@ninagal.withay.com>
Message-ID: <1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>

On Dec 8, 2008, at 15:41, Bryan Blackburn wrote:

> On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said:
>
>> I tried to rebuild the port, but the port command had the same  
>> problem:
>>
>> sudo port clean git
>> couldn't load file
>> "/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib":
>> dlopen(/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib, 10):
>> Library not loaded: /opt/local/lib/libcurl.4.dylib
>>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/ 
>> Pextlib.dylib
>>   Reason: Incompatible library version: Pextlib.dylib requires  
>> version
>> 6.0.0 or later, but libcurl.4.dylib provides version 5.0.0
>
> This could be an issue with selfupdate as it should be linking Pextlib
> against the system libcurl, not one found in MacPorts.  Will have  
> to look
> into this.

I remember when building MacPorts manually, it will link with its own  
ports, which isn't so great IMHO. Which is why I now build MacPorts  
through a script which first sets the PATH so it doesn't contain the  
MacPorts prefix. Like this:


#!/bin/bash

PREFIX=/mp

cd ~/macports/base
PATH=/bin:/sbin:/usr/bin:/usr/sbin \
./configure \
--prefix=$PREFIX \
--with-tclpackage=$PREFIX/Library/Tcl \
--with-install-user=rschmidt \
--with-install-group=admin \
--with-applications-dir=/Applications/mp \
--with-frameworks-dir=$PREFIX/Library/Frameworks \
--enable-readline || exit $?
make -j2 || exit $?
make install || exit $?
make clean || exit $?





From blb at macports.org  Mon Dec  8 14:42:00 2008
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 8 Dec 2008 15:42:00 -0700
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>
References: <493D82AF.5080203@shopwatch.org>
	<20081208214114.GF506@ninagal.withay.com>
	<1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>
Message-ID: <20081208224200.GL506@ninagal.withay.com>

On Mon, Dec 08, 2008 at 04:19:41PM -0600, Ryan Schmidt said:
> On Dec 8, 2008, at 15:41, Bryan Blackburn wrote:
>
>> On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said:
>>
>>> I tried to rebuild the port, but the port command had the same  
>>> problem:
>>>
>>> sudo port clean git
>>> couldn't load file
>>> "/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib":
>>> dlopen(/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib, 10):
>>> Library not loaded: /opt/local/lib/libcurl.4.dylib
>>>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/ 
>>> Pextlib.dylib
>>>   Reason: Incompatible library version: Pextlib.dylib requires  
>>> version
>>> 6.0.0 or later, but libcurl.4.dylib provides version 5.0.0
>>
>> This could be an issue with selfupdate as it should be linking Pextlib
>> against the system libcurl, not one found in MacPorts.  Will have to 
>> look
>> into this.
>
> I remember when building MacPorts manually, it will link with its own  
> ports, which isn't so great IMHO. Which is why I now build MacPorts  
> through a script which first sets the PATH so it doesn't contain the  
> MacPorts prefix. Like this:

FYI I've never had MacPorts link against anything installed by MacPorts when
using configure/make/make install.  I do have the curl port installed by
Pextlib is still linked to the system libcurl...

Bryan


From jmr at macports.org  Mon Dec  8 14:56:57 2008
From: jmr at macports.org (Joshua Root)
Date: Tue, 09 Dec 2008 09:56:57 +1100
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>
References: <493D82AF.5080203@shopwatch.org>	<20081208214114.GF506@ninagal.withay.com>
	<1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>
Message-ID: <493DA639.7010300@macports.org>

Ryan Schmidt wrote:
> On Dec 8, 2008, at 15:41, Bryan Blackburn wrote:
> 
>> On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said:
>>
>>> I tried to rebuild the port, but the port command had the same problem:
>>>
>>> sudo port clean git
>>> couldn't load file
>>> "/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib":
>>> dlopen(/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib, 10):
>>> Library not loaded: /opt/local/lib/libcurl.4.dylib
>>>   Referenced from:
>>> /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib
>>>   Reason: Incompatible library version: Pextlib.dylib requires version
>>> 6.0.0 or later, but libcurl.4.dylib provides version 5.0.0
>>
>> This could be an issue with selfupdate as it should be linking Pextlib
>> against the system libcurl, not one found in MacPorts.  Will have to look
>> into this.
> 
> I remember when building MacPorts manually, it will link with its own
> ports, which isn't so great IMHO.

Yet when I build base, configure finds /usr/bin/curl-config even though
I have the curl port installed (and /opt/local/bin is first in my PATH).
Under what circumstances will it find the one in /opt/local?

- Josh

From jmr at macports.org  Mon Dec  8 15:04:03 2008
From: jmr at macports.org (Joshua Root)
Date: Tue, 09 Dec 2008 10:04:03 +1100
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <20081208224200.GL506@ninagal.withay.com>
References: <493D82AF.5080203@shopwatch.org>	<20081208214114.GF506@ninagal.withay.com>	<1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>
	<20081208224200.GL506@ninagal.withay.com>
Message-ID: <493DA7E3.1060209@macports.org>

Bryan Blackburn wrote:
> On Mon, Dec 08, 2008 at 04:19:41PM -0600, Ryan Schmidt said:
>> On Dec 8, 2008, at 15:41, Bryan Blackburn wrote:
>>
>>> On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said:
>>>
>>>> I tried to rebuild the port, but the port command had the same  
>>>> problem:
>>>>
>>>> sudo port clean git
>>>> couldn't load file
>>>> "/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib":
>>>> dlopen(/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib, 10):
>>>> Library not loaded: /opt/local/lib/libcurl.4.dylib
>>>>   Referenced from: /opt/local/share/macports/Tcl/pextlib1.0/ 
>>>> Pextlib.dylib
>>>>   Reason: Incompatible library version: Pextlib.dylib requires  
>>>> version
>>>> 6.0.0 or later, but libcurl.4.dylib provides version 5.0.0
>>> This could be an issue with selfupdate as it should be linking Pextlib
>>> against the system libcurl, not one found in MacPorts.  Will have to 
>>> look
>>> into this.
>> I remember when building MacPorts manually, it will link with its own  
>> ports, which isn't so great IMHO. Which is why I now build MacPorts  
>> through a script which first sets the PATH so it doesn't contain the  
>> MacPorts prefix. Like this:
> 
> FYI I've never had MacPorts link against anything installed by MacPorts when
> using configure/make/make install.  I do have the curl port installed by
> Pextlib is still linked to the system libcurl...

Could the wrong libcurl be picked up if there is something like
LDFLAGS=-L/opt/local/lib in the environment? If that's what happened to
Jay, it shouldn't be a problem with selfupdate because the environment
is sanitised.

- Josh

From jwdavison at me.com  Mon Dec  8 16:19:08 2008
From: jwdavison at me.com (joseph davison)
Date: Mon, 08 Dec 2008 18:19:08 -0600
Subject: install manopen fails on 10.5.5
Message-ID: <3F9717BA-6AE3-4DFD-8CD4-DBC7F07EA6D3@me.com>

Just installed macports on a new leopard installation on my macbook pro.

Tried to install manopen and it blows up with:
ManDocument.m: In function '-[ManDocument windowControllerDidLoadNib:]':
ManDocument.m:328: error: 'NSSimpleHorizontalTypesetter' undeclared  
(first use in this function)
ManDocument.m:328: error: (Each undeclared identifier is reported only  
once
ManDocument.m:328: error: for each function it appears in.)

and then some warnings.

Presuming it useful, here's the whole output from port -v install  
macports

--->  Fetching ManOpen
--->  Verifying checksum(s) for ManOpen
--->  Checksumming ManOpen-2.5.1.s.tar.gz
--->  Extracting ManOpen
--->  Extracting ManOpen-2.5.1.s.tar.gz
--->  Configuring ManOpen
--->  Building ManOpen with target all
== Making all for i386 in ManOpen openman.tproj ==
== Making ManOpen for i386 ==
Pre-build setup...
/bin/rm -f /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/derived_src/TrustedPrecomps.txt
......in cat2html
......in cat2rtf
Building...
......in cat2html
/usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/var/ 
macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/PrivateHeaders/ -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/Headers/ -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/derived_src/ManOpen/cat2html.tproj -I. -pipe        -I/ 
opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/Headers -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1          - 
c -o /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/objects-optimized/ManOpen/cat2html.tproj/cat2html.i386.o  
cat2html.c
cat2html.l: In function 'cat2htmllex':
cat2html.l:304: warning: pointer targets in passing argument 1 of  
'decodeUTF8' differ in signedness
cat2html.l:311: warning: pointer targets in passing argument 1 of  
'decodeUTF8' differ in signedness
/usr/bin/cc -o /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.app/Resources/cat2html   -L/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/objects-optimized/ManOpen/cat2html.tproj        -F/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1 -L/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1       - 
arch i386  /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/objects-optimized/ManOpen/cat2html.tproj/ 
cat2html.o       -framework Foundation
......in cat2rtf
/usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/var/ 
macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/PrivateHeaders/ -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/Headers/ -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/derived_src/ManOpen/cat2rtf.tproj -I. -pipe        -I/ 
opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/Headers -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1          - 
c -o /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/objects-optimized/ManOpen/cat2rtf.tproj/cat2rtf.i386.o  
cat2rtf.c
cat2rtf.l: In function 'cat2rtflex':
cat2rtf.l:344: warning: pointer targets in passing argument 1 of  
'decodeUTF8' differ in signedness
cat2rtf.l:351: warning: pointer targets in passing argument 1 of  
'decodeUTF8' differ in signedness
/usr/bin/cc -o /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.app/Resources/cat2rtf   -L/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/objects-optimized/ManOpen/cat2rtf.tproj        -F/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1 -L/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1       - 
arch i386  /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/objects-optimized/ManOpen/cat2rtf.tproj/cat2rtf.o
/usr/lib/mergeInfo PB.project CustomInfo.plist /opt/local/var/macports/ 
build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/derived_src/ManOpen/Java.plist -o /opt/local/var/ 
macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.app/Resources/Info-macos.plist
-n
Copying English resources...
Copied ManOpen.nib PrefPanel.nib DocController.nib ManOpen- 
macintosh.nib Apropos.nib ManOpen-macos.nib ManPage.nib FindPanel.nib  
Credits.rtf InfoPlist.strings
Copied LinkCursor.tiff ManOpen-nextstep.tiff ManOpen.tiff ManOpen.icns  
ManOpen.scriptSuite ManOpen.scriptTerminology
/usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/var/ 
macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.app/PrivateHeaders -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/Headers -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/derived_src/ManOpen -I. -pipe        -I/opt/local/var/ 
macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/Headers -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1      - 
ObjC       -c -o /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/objects-optimized/ManOpen/AproposDocument.i386.o  
AproposDocument.m
/usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/var/ 
macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.app/PrivateHeaders -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/Headers -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/derived_src/ManOpen -I. -pipe        -I/opt/local/var/ 
macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/Headers -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1      - 
ObjC       -c -o /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/objects-optimized/ManOpen/FindPanelController.i386.o  
FindPanelController.m
/usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/var/ 
macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.app/PrivateHeaders -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/Headers -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/derived_src/ManOpen -I. -pipe        -I/opt/local/var/ 
macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/Headers -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1      - 
ObjC       -c -o /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/objects-optimized/ManOpen/ManDocument.i386.o ManDocument.m
ManDocument.m: In function '-[ManDocument windowControllerDidLoadNib:]':
ManDocument.m:328: error: 'NSSimpleHorizontalTypesetter' undeclared  
(first use in this function)
ManDocument.m:328: error: (Each undeclared identifier is reported only  
once
ManDocument.m:328: error: for each function it appears in.)
ManDocument.m: In function '-[ManTextView drawPageBorderWithSize:]':
ManDocument.m:634: warning: 'widthOfString:' is deprecated (declared  
at /System/Library/Frameworks/AppKit.framework/Headers/NSFont.h:216)
ManDocument.m:644: warning: 'cString' is deprecated (declared at / 
System/Library/Frameworks/Foundation.framework/Headers/NSString.h:345)
ManDocument.m:645: warning: 'cString' is deprecated (declared at / 
System/Library/Frameworks/Foundation.framework/Headers/NSString.h:345)
ManDocument.m:645: warning: 'cStringLength' is deprecated (declared  
at /System/Library/Frameworks/Foundation.framework/Headers/NSString.h: 
347)
make[1]: *** [/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
ManOpen.build/objects-optimized/ManOpen/ManDocument.i386.o] Error 1
make: *** [all at ManOpen] Error 2
Warning: the following items did not execute (for ManOpen):  
org.macports.activate org.macports.build org.macports.destroot  
org.macports.install


From jwdavison at me.com  Mon Dec  8 16:23:50 2008
From: jwdavison at me.com (joseph davison)
Date: Mon, 08 Dec 2008 18:23:50 -0600
Subject: nco fails to build & install on 10.5.5
Message-ID: <97EBE94B-B393-41AF-8174-D08DD4E3A5FA@me.com>

new Leopard installation on a macbook pro.

installed netcdf, then tried to install nco
hours later, after installing a new gcc and a new perl, and ... it  
finally tried to do nco.

Here's the nco build output:

--->  Fetching nco
--->  nco-3.9.5.tar.gz doesn't seem to exist in /opt/local/var/ 
macports/distfiles/nco
--->  Attempting to fetch nco-3.9.5.tar.gz from http://nco.sourceforge.net/src/
--->  Verifying checksum(s) for nco
--->  Checksumming nco-3.9.5.tar.gz
--->  Extracting nco
--->  Extracting nco-3.9.5.tar.gz
--->  Configuring nco
checking build system type... i686-apple-darwin9.5.0
checking host system type... i686-apple-darwin9.5.0
checking target system type... i686-apple-darwin9.5.0
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for a BSD-compatible install... /usr/bin/install
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /opt/local/bin/gmkdir -p
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking for gcc... /usr/bin/gcc-4.0
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /usr/bin/gcc-4.0 accepts -g... yes
checking for /usr/bin/gcc-4.0 option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of /usr/bin/gcc-4.0... none
checking whether we are using the GNU C++ compiler... yes
checking whether /usr/bin/g++-4.0 accepts -g... yes
checking dependency style of /usr/bin/g++-4.0... none
checking how to run the C preprocessor... /usr/bin/cpp-4.0
checking how to run the C++ preprocessor... /usr/bin/g++-4.0 -E
checking for /usr/bin/gcc-4.0 option to accept ISO C99... -std=gnu99
checking for /usr/bin/gcc-4.0 -std=gnu99 option to accept ISO Standard  
C... (cached) -std=gnu99
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for bison... bison -y
checking for a BSD-compatible install... /usr/bin/install
checking whether ln -s works... yes
checking for a sed that does not truncate output... /usr/bin/sed
checking for ld used by /usr/bin/gcc-4.0 -std=gnu99... /usr/libexec/ 
gcc/i686-apple-darwin9/4.0.1/ld
checking if the linker (/usr/libexec/gcc/i686-apple-darwin9/4.0.1/ld)  
is GNU ld... no
checking for /usr/libexec/gcc/i686-apple-darwin9/4.0.1/ld option to  
reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -p
checking how to recognize dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... /usr/bin/g++-4.0 -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 196608
checking command to parse /usr/bin/nm -p output from /usr/bin/gcc-4.0 - 
std=gnu99 object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking for dsymutil... dsymutil
checking for nmedit... nmedit
checking for -single_module linker flag... yes
checking for -exported_symbols_list linker flag... yes
checking if /usr/bin/gcc-4.0 -std=gnu99 supports -fno-rtti -fno- 
exceptions... no
checking for /usr/bin/gcc-4.0 -std=gnu99 option to produce PIC... -fno- 
common
checking if /usr/bin/gcc-4.0 -std=gnu99 PIC flag -fno-common works...  
yes
checking if /usr/bin/gcc-4.0 -std=gnu99 static flag -static works... no
checking if /usr/bin/gcc-4.0 -std=gnu99 supports -c -o file.o... yes
checking whether the /usr/bin/gcc-4.0 -std=gnu99 linker (/usr/libexec/ 
gcc/i686-apple-darwin9/4.0.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin9.5.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
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by /usr/bin/g++-4.0... /usr/libexec/gcc/i686- 
apple-darwin9/4.0.1/ld
checking if the linker (/usr/libexec/gcc/i686-apple-darwin9/4.0.1/ld)  
is GNU ld... no
checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/i686- 
apple-darwin9/4.0.1/ld) supports shared libraries... yes
checking for /usr/bin/g++-4.0 option to produce PIC... -fno-common
checking if /usr/bin/g++-4.0 PIC flag -fno-common works... yes
checking if /usr/bin/g++-4.0 static flag -static works... no
checking if /usr/bin/g++-4.0 supports -c -o file.o... yes
checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/i686- 
apple-darwin9/4.0.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin9.5.0 dyld
(cached) (cached) checking how to hardcode library paths into  
programs... immediate
appending configuration tag "F77" to libtool
checking whether to enable maintainer-specific portions of  
Makefiles... no
checking for working memcmp... yes
checking whether lstat dereferences a symlink specified with a  
trailing slash... no
checking whether stat accepts an empty string... no
checking for working strtod... yes
checking for floor... yes
checking for canonicalize_file_name... no
checking for gethostname... yes
checking for getpagesize... yes
checking for getrusage... yes
checking for memchr... yes
checking for memmove... yes
checking for memset... yes
checking for mkstemp... yes
checking for pow... yes
checking for readlink... yes
checking for realpath... yes
checking for regcomp... yes
checking for setlocale... yes
checking for sqrt... yes
checking for strchr... yes
checking for strerror... yes
checking for strpbrk... yes
checking for strrchr... yes
checking for strstr... yes
checking for strtol... yes
checking for ANSI C header files... (cached) yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking libintl.h usability... no
checking libintl.h presence... no
checking for libintl.h... no
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking cstdlib usability... yes
checking cstdlib presence... yes
checking for cstdlib... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for pid_t... yes
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for uid_t in sys/types.h... yes
checking for ptrdiff_t... yes
checking for int*... yes
checking size of int*... 4
checking whether C++ compiler implements namespaces... yes
checking whether C++ compiler has working valarray<T>... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
########################################
#  Testing for DAP (aka DODS) support  #
########################################
#################################
#  Testing for netCDF4 support  #
#################################
DEBUG: enable_netcdf4 = no and enable_dap = yes
checking for nc_open in -lnc-dap... yes
configure: DAP support enabled
################################################
# Testing whether libnetcdf is Version 3 or 4  #
################################################
DEBUG: enable_netcdf4: no and enable_dap: yes
DEBUG: LIBS = -lnc-dap -L/opt/local/lib -lnc-dap -L/opt/local/lib - 
ldapclient -lcurl -ldap -lxml2 -lpthread -lz -liconv -lm
#############################################
# Testing for HDF5 & netCDF4 libs           #
#############################################
DEBUG: LIBS = -lnc-dap -L/opt/local/lib -lnc-dap -L/opt/local/lib - 
ldapclient -lcurl -ldap -lxml2 -lpthread -lz -liconv -lm
checking netcdf.h usability... yes
checking netcdf.h presence... yes
checking for netcdf.h... yes
DEBUG: After enable_dap section LIBS = -lnc-dap -L/opt/local/lib -lnc- 
dap -L/opt/local/lib -ldapclient -lcurl -ldap -lxml2 -lpthread -lz - 
liconv -lm
checking for _g95_ac_array in -lf95... no
checking for sin in -lm... yes
checking for sinf in -lsunmath... no
checking for nc_inq_format... yes
checking for getopt... yes
checking for getopt_long... yes
checking for getopt_long... (cached) yes
checking for atan2... yes
checking for acosf... yes
checking for asinf... yes
checking for atanf... yes
checking for atan2f... yes
checking for cosf... yes
checking for expf... yes
checking for fabsf... yes
checking for fmodf... yes
checking for log10f... yes
checking for logf... yes
checking for powf... yes
checking for sinf... yes
checking for sqrtf... yes
checking for tanf... yes
checking for erff... yes
checking for erfcf... yes
checking for gammaf... no
checking for acoshf... yes
checking for asinhf... yes
checking for atanhf... yes
checking for coshf... yes
checking for sinhf... yes
checking for tanhf... yes
checking for ceilf... yes
checking for floorf... yes
checking for nearbyintf... yes
checking for rintf... yes
checking for roundf... yes
checking for truncf... yes
checking for getopt_long... (cached) yes
checking for strdup... yes
checking for strcasecmp... yes
checking for gettext in -lintl... yes
checking for res_init in -lresolv... yes
checking for main in -lsocket... no
checking for main in -lthread... no
checking for main in -lnsl... no
checking for nco_open in -lnco... no
##########################################################
#     Sorting out MacOSX build parameters                #
##########################################################
DEBUG: enable_libnco =  and MACOSX = 1
DEBUG: After library checks LIBS=-lresolv -lintl -lm -lnc-dap -L/opt/ 
local/lib -lnc-dap -L/opt/local/lib -ldapclient -lcurl -ldap -lxml2 - 
lpthread -lz -liconv -lm
DEBUG: enable_mpi = ''
#################################
#  Testing for ANTLR support    #
#################################
checking for runantlr... yes
checking antlr/CommonToken.hpp usability... yes
checking antlr/CommonToken.hpp presence... yes
checking for antlr/CommonToken.hpp... yes
INFO: ANTLR development support found---will build nco++ directory and  
ncap2
checking regex.h usability... yes
checking regex.h presence... yes
checking for regex.h... yes
checking for sys/types.h... (cached) yes
checking for regexec... yes
checking for regcomp... (cached) yes
checking for regfree... yes
########################################
#     Testing for UDUNITS support      #
########################################
checking for tdelete... yes
checking for ... no
configure: WARNING: file  was not found but will be compiled into NCO.  
Some executables may fail without it.
checking for tdelete... (cached) yes
configure: NB: Following tests of UDUnits library and header must  
succeed for UDUnits support:
checking for utInit in -ludunits... yes
checking udunits.h usability... yes
checking udunits.h presence... yes
checking for udunits.h... yes
configure: UDUnits support enabled
DEBUG: After UDUnits tests LIBS = -ludunits -lresolv -lintl -lm -lnc- 
dap -L/opt/local/lib -lnc-dap -L/opt/local/lib -ldapclient -lcurl - 
ldap -lxml2 -lpthread -lz -liconv -lm     -ludunits
checking for ncgen... /opt/local/bin/ncgen
configure: Creating sample netCDF data files for self-tests
###############################
#    Require Shared Libs?     #
###############################
DEBUG: enable_shared: no
DEBUG: enable_shared: rejected due to netcdf4 requirement
DEBUG: enable_ncoxx: yes and NCOXX = nco++
configure: creating ./config.status
config.status: creating Makefile
config.status: creating data/Makefile
config.status: creating src/Makefile
config.status: creating src/nco/Makefile
config.status: creating man/Makefile
config.status: creating doc/Makefile
config.status: creating src/nco_c++/Makefile
config.status: creating src/nco++/Makefile
config.status: creating config.h
config.status: executing depfiles commands

Configuration Parameters:
AR_FLAGS............. cru
CC................... /usr/bin/gcc-4.0 -std=gnu99
CFLAGS............... -fno-common -O2 -std=c99 -D_BSD_SOURCE
CPP.................. /usr/bin/cpp-4.0
CPPFLAGS............. -I/opt/local/include/libnc-dap -I/usr/include/ 
malloc -I/opt/local/include
CXX.................. /usr/bin/g++-4.0
CXXFLAGS............. -O2
HOST.................
host................. i686-apple-darwin9.5.0
HOSTNAME............. jason.local
LDFLAGS.............. -L/opt/local/lib -L/opt/local/lib
LIBS................. -ludunits -lresolv -lintl -lm -lnc-dap -L/opt/ 
local/lib -lnc-dap -L/opt/local/lib -ldapclient -lcurl -ldap -lxml2 - 
lpthread -lz -liconv -lm     -ludunits
NETCDF4_ROOT.........
*******************************************************************
If the build fails, please examine the file 'configure.eg'
in the top-level NCO directory.  It contains examples known to
build NCO for various platforms and compilers.
*******************************************************************
--->  Building nco with target all
make  all-recursive
Making all in data
/opt/local/bin/ncgen -o big.nc big.cdl
/opt/local/bin/ncgen -o in_rec_zero.nc in_rec_zero.cdl
Making all in doc
make[2]: Nothing to be done for `all'.
Making all in src
Making all in nco
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_att_utl.lo nco_att_utl.c
mkdir .libs
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_att_utl.c  -fno-common -DPIC - 
o .libs/nco_att_utl.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_att_utl.c -o nco_att_utl.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_aux.lo nco_aux.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_aux.c  -fno-common -DPIC - 
o .libs/nco_aux.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_aux.c -o nco_aux.o >/dev/null  
2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_bnr.lo nco_bnr.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_bnr.c  -fno-common -DPIC - 
o .libs/nco_bnr.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_bnr.c -o nco_bnr.o >/dev/null  
2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_cln_utl.lo nco_cln_utl.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_cln_utl.c  -fno-common -DPIC - 
o .libs/nco_cln_utl.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_cln_utl.c -o nco_cln_utl.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_cnf_dmn.lo nco_cnf_dmn.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_cnf_dmn.c  -fno-common -DPIC - 
o .libs/nco_cnf_dmn.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_cnf_dmn.c -o nco_cnf_dmn.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_cnf_typ.lo nco_cnf_typ.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_cnf_typ.c  -fno-common -DPIC - 
o .libs/nco_cnf_typ.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_cnf_typ.c -o nco_cnf_typ.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_cnv_arm.lo nco_cnv_arm.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_cnv_arm.c  -fno-common -DPIC - 
o .libs/nco_cnv_arm.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_cnv_arm.c -o nco_cnv_arm.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_cnv_csm.lo nco_cnv_csm.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_cnv_csm.c  -fno-common -DPIC - 
o .libs/nco_cnv_csm.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_cnv_csm.c -o nco_cnv_csm.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_ctl.lo nco_ctl.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_ctl.c  -fno-common -DPIC - 
o .libs/nco_ctl.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_ctl.c -o nco_ctl.o >/dev/null  
2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_dbg.lo nco_dbg.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_dbg.c  -fno-common -DPIC - 
o .libs/nco_dbg.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_dbg.c -o nco_dbg.o >/dev/null  
2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_dmn_utl.lo nco_dmn_utl.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_dmn_utl.c  -fno-common -DPIC - 
o .libs/nco_dmn_utl.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_dmn_utl.c -o nco_dmn_utl.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_fl_utl.lo nco_fl_utl.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_fl_utl.c  -fno-common -DPIC - 
o .libs/nco_fl_utl.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_fl_utl.c -o nco_fl_utl.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_lmt.lo nco_lmt.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_lmt.c  -fno-common -DPIC - 
o .libs/nco_lmt.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_lmt.c -o nco_lmt.o >/dev/null  
2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_lst_utl.lo nco_lst_utl.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_lst_utl.c  -fno-common -DPIC - 
o .libs/nco_lst_utl.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_lst_utl.c -o nco_lst_utl.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_mmr.lo nco_mmr.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_mmr.c  -fno-common -DPIC - 
o .libs/nco_mmr.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_mmr.c -o nco_mmr.o >/dev/null  
2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_msa.lo nco_msa.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_msa.c  -fno-common -DPIC - 
o .libs/nco_msa.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_msa.c -o nco_msa.o >/dev/null  
2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_mss_val.lo nco_mss_val.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_mss_val.c  -fno-common -DPIC - 
o .libs/nco_mss_val.o
nco_mss_val.c:35:32: warning: integer constant is so large that it is  
unsigned
nco_mss_val.c:36:34: warning: integer constant is so large that it is  
unsigned
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_mss_val.c -o nco_mss_val.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_netcdf.lo nco_netcdf.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_netcdf.c  -fno-common -DPIC - 
o .libs/nco_netcdf.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_netcdf.c -o nco_netcdf.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_omp.lo nco_omp.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_omp.c  -fno-common -DPIC - 
o .libs/nco_omp.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_omp.c -o nco_omp.o >/dev/null  
2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_pck.lo nco_pck.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_pck.c  -fno-common -DPIC - 
o .libs/nco_pck.o
nco_pck.c:818:38: warning: integer constant is so large that it is  
unsigned
nco_pck.c:819:39: warning: integer constant is so large that it is  
unsigned
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_pck.c -o nco_pck.o >/dev/null  
2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_prn.lo nco_prn.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_prn.c  -fno-common -DPIC - 
o .libs/nco_prn.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_prn.c -o nco_prn.o >/dev/null  
2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_rec_var.lo nco_rec_var.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_rec_var.c  -fno-common -DPIC - 
o .libs/nco_rec_var.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_rec_var.c -o nco_rec_var.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_rth_flt.lo nco_rth_flt.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_rth_flt.c  -fno-common -DPIC - 
o .libs/nco_rth_flt.o
nco_rth_flt.c: In function 'gammaf':
nco_rth_flt.c:70: warning: implicit declaration of function 'gamma'
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_rth_flt.c -o nco_rth_flt.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_rth_utl.lo nco_rth_utl.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_rth_utl.c  -fno-common -DPIC - 
o .libs/nco_rth_utl.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_rth_utl.c -o nco_rth_utl.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_scl_utl.lo nco_scl_utl.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_scl_utl.c  -fno-common -DPIC - 
o .libs/nco_scl_utl.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_scl_utl.c -o nco_scl_utl.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_scm.lo nco_scm.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_scm.c  -fno-common -DPIC - 
o .libs/nco_scm.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_scm.c -o nco_scm.o >/dev/null  
2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_sng_utl.lo nco_sng_utl.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_sng_utl.c  -fno-common -DPIC - 
o .libs/nco_sng_utl.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_sng_utl.c -o nco_sng_utl.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_var_avg.lo nco_var_avg.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_var_avg.c  -fno-common -DPIC - 
o .libs/nco_var_avg.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_var_avg.c -o nco_var_avg.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_var_lst.lo nco_var_lst.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_var_lst.c  -fno-common -DPIC - 
o .libs/nco_var_lst.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_var_lst.c -o nco_var_lst.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_var_rth.lo nco_var_rth.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_var_rth.c  -fno-common -DPIC - 
o .libs/nco_var_rth.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_var_rth.c -o nco_var_rth.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_var_scv.lo nco_var_scv.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_var_scv.c  -fno-common -DPIC - 
o .libs/nco_var_scv.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_var_scv.c -o nco_var_scv.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=compile /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H - 
I. -I../..   -I/opt/local/include/libnc-dap -I/usr/include/malloc -I/ 
opt/local/include  -fno-common -O2 -std=c99 -D_BSD_SOURCE  -c -o  
nco_var_utl.lo nco_var_utl.c
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_var_utl.c  -fno-common -DPIC - 
o .libs/nco_var_utl.o
  /usr/bin/gcc-4.0 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I/opt/local/ 
include/libnc-dap -I/usr/include/malloc -I/opt/local/include -fno- 
common -O2 -std=c99 -D_BSD_SOURCE -c nco_var_utl.c -o nco_var_utl.o >/ 
dev/null 2>&1
/bin/sh ../../libtool --tag=CXX --tag=CXX --preserve-dup-deps -- 
tag=CC   --mode=link /usr/bin/gcc-4.0 -std=gnu99  -fno-common -O2 - 
std=c99 -D_BSD_SOURCE  -release 3.9.5 -L/opt/local/lib -L/opt/local/ 
lib -o libnco.la -rpath /opt/local/lib   nco_att_utl.lo nco_aux.lo  
nco_bnr.lo nco_cln_utl.lo nco_cnf_dmn.lo nco_cnf_typ.lo nco_cnv_arm.lo  
nco_cnv_csm.lo nco_ctl.lo nco_dbg.lo nco_dmn_utl.lo nco_fl_utl.lo  
nco_lmt.lo nco_lst_utl.lo nco_mmr.lo nco_msa.lo nco_mss_val.lo  
nco_netcdf.lo nco_omp.lo nco_pck.lo nco_prn.lo nco_rec_var.lo  
nco_rth_flt.lo nco_rth_utl.lo nco_scl_utl.lo nco_scm.lo nco_sng_utl.lo  
nco_var_avg.lo nco_var_lst.lo nco_var_rth.lo nco_var_scv.lo  
nco_var_utl.lo  -ludunits -lresolv -lintl -lm -lnc-dap -L/opt/local/ 
lib -lnc-dap -L/opt/local/lib -ldapclient -lcurl -ldap -lxml2 - 
lpthread -lz -liconv -lm     -ludunits
/usr/bin/g++-4.0 -dynamiclib  -o .libs/libnco-3.9.5.dylib  .libs/ 
nco_att_utl.o .libs/nco_aux.o .libs/nco_bnr.o .libs/ 
nco_cln_utl.o .libs/nco_cnf_dmn.o .libs/nco_cnf_typ.o .libs/ 
nco_cnv_arm.o .libs/nco_cnv_csm.o .libs/nco_ctl.o .libs/ 
nco_dbg.o .libs/nco_dmn_utl.o .libs/nco_fl_utl.o .libs/nco_lmt.o .libs/ 
nco_lst_utl.o .libs/nco_mmr.o .libs/nco_msa.o .libs/ 
nco_mss_val.o .libs/nco_netcdf.o .libs/nco_omp.o .libs/nco_pck.o .libs/ 
nco_prn.o .libs/nco_rec_var.o .libs/nco_rth_flt.o .libs/ 
nco_rth_utl.o .libs/nco_scl_utl.o .libs/nco_scm.o .libs/ 
nco_sng_utl.o .libs/nco_var_avg.o .libs/nco_var_lst.o .libs/ 
nco_var_rth.o .libs/nco_var_scv.o .libs/nco_var_utl.o  -L/opt/local/ 
lib -ludunits -lresolv /opt/local/lib/libintl.dylib -lm /opt/local/lib/ 
libz.dylib /opt/local/lib/libnc-dap.dylib /opt/local/lib/ 
libdapclient.dylib /opt/local/lib/libcurl.dylib /opt/local/lib/ 
libdap.dylib /opt/local/lib/libxml2.dylib -lpthread -lz /opt/local/lib/ 
libiconv.dylib -lm -ludunits  -install_name  /opt/local/lib/ 
libnco-3.9.5.dylib
Undefined symbols:
   "_nco_mss_val_sng_get", referenced from:
       _nco_aed_prc in nco_att_utl.o
       _nco_aed_prc in nco_att_utl.o
       _nco_att_cpy in nco_att_utl.o
       _nco_lbr_vrs_prn in nco_ctl.o
       _nco_lbr_vrs_prn in nco_ctl.o
       _nco_mss_val_get in nco_mss_val.o
       _nco_mss_val_get in nco_mss_val.o
       _nco_mss_val_get in nco_mss_val.o
       _nco_mss_val_get in nco_mss_val.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
   "_prg_nm_get", referenced from:
       _nco_aed_prc in nco_att_utl.o
       _nco_aed_prc in nco_att_utl.o
       _nco_aed_prc in nco_att_utl.o
       _nco_aed_prc in nco_att_utl.o
       _nco_att_cpy in nco_att_utl.o
       _nco_att_cpy in nco_att_utl.o
       _nco_att_cpy in nco_att_utl.o
       _nco_hst_att_cat in nco_att_utl.o
       _nco_prs_aed_lst in nco_att_utl.o
       _nco_prs_aed_lst in nco_att_utl.o
       _nco_prs_aed_lst in nco_att_utl.o
       _nco_prs_aed_lst in nco_att_utl.o
       _nco_prs_aed_lst in nco_att_utl.o
       _nco_prs_aed_lst in nco_att_utl.o
       _nco_prs_att in nco_att_utl.o
       _nco_bnr_open in nco_bnr.o
       _nco_bnr_open in nco_bnr.o
       _nco_bnr_close in nco_bnr.o
       _nco_bnr_close in nco_bnr.o
       _nco_bnr_wrt in nco_bnr.o
       _nco_nd2endm in nco_cln_utl.o
       _nco_var_cnf_dmn in nco_cnf_dmn.o
       _nco_var_cnf_dmn in nco_cnf_dmn.o
       _nco_var_cnf_dmn in nco_cnf_dmn.o
       _nco_var_cnf_dmn in nco_cnf_dmn.o
       _nco_var_cnf_dmn in nco_cnf_dmn.o
       _nco_var_cnf_dmn in nco_cnf_dmn.o
       _nco_var_cnf_dmn in nco_cnf_dmn.o
       _nco_var_cnf_dmn in nco_cnf_dmn.o
       _ncap_var_cnf_dmn in nco_cnf_dmn.o
       _nco_var_dmn_rdr_mtd in nco_cnf_dmn.o
       _nco_var_dmn_rdr_mtd in nco_cnf_dmn.o
       _nco_var_dmn_rdr_mtd in nco_cnf_dmn.o
       _nco_var_dmn_rdr_mtd in nco_cnf_dmn.o
       _nco_var_dmn_rdr_val in nco_cnf_dmn.o
       _nco_var_dmn_rdr_val in nco_cnf_dmn.o
       _nco_var_dmn_rdr_val in nco_cnf_dmn.o
       _nco_var_dmn_rdr_val in nco_cnf_dmn.o
       _nco_var_cnf_typ in nco_cnf_typ.o
       _nco_cnv_mss_val_typ in nco_cnf_typ.o
       _nco_cnv_arm_inq in nco_cnv_arm.o
       _nco_cnv_arm_time_mk in nco_cnv_arm.o
       _nco_cnv_arm_time_install in nco_cnv_arm.o
       _nco_cnv_arm_time_install in nco_cnv_arm.o
       _nco_cnv_arm_time_install in nco_cnv_arm.o
       _nco_cnv_ccm_ccsm_cf_inq in nco_cnv_csm.o
       _nco_cnv_ccm_ccsm_cf_inq in nco_cnv_csm.o
       _nco_cnv_ccm_ccsm_cf_inq in nco_cnv_csm.o
       _nco_cnv_ccm_ccsm_cf_date in nco_cnv_csm.o
       _nco_cnv_ccm_ccsm_cf_date in nco_cnv_csm.o
       _nco_cnv_ccm_ccsm_cf_date in nco_cnv_csm.o
       _nco_cnv_ccm_ccsm_cf_date in nco_cnv_csm.o
       _nco_cnv_cf_crd_add in nco_cnv_csm.o
       _nco_cmp_get in nco_ctl.o
       _nco_mpi_get in nco_ctl.o
       _nco_exit in nco_ctl.o
       _nco_ddra in nco_ctl.o
       _nco_ddra in nco_ctl.o
       _nco_ddra in nco_ctl.o
       _nco_ddra in nco_ctl.o
       _nco_exit_gracefully in nco_ctl.o
       _nco_lbr_vrs_prn in nco_ctl.o
       _nco_usg_prn in nco_ctl.o
       _nco_usg_prn in nco_ctl.o
       _nco_usg_prn in nco_ctl.o
       _nco_usg_prn in nco_ctl.o
       _nco_usg_prn in nco_ctl.o
       _nco_usg_prn in nco_ctl.o
       _nco_usg_prn in nco_ctl.o
       _nco_usg_prn in nco_ctl.o
       _err_prn in nco_dbg.o
       _nco_dmn_dfn in nco_dmn_utl.o
       _nco_create_mode_mrg in nco_fl_utl.o
       _nco_create_mode_mrg in nco_fl_utl.o
       _nco_create_mode_prs in nco_fl_utl.o
       _nco_create_mode_prs in nco_fl_utl.o
       _nco_create_mode_prs in nco_fl_utl.o
       _nco_fl_cp in nco_fl_utl.o
       _nco_fl_info_get in nco_fl_utl.o
       _nco_fl_info_get in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mv in nco_fl_utl.o
       _nco_fl_mv in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_cls in nco_fl_utl.o
       _nco_fl_rm in nco_fl_utl.o
       _nco_fl_rm in nco_fl_utl.o
       _nco_lmt_sct_mk in nco_lmt.o
       _nco_lmt_sct_mk in nco_lmt.o
       _nco_lmt_sct_mk in nco_lmt.o
       _nco_lmt_sct_mk in nco_lmt.o
       _nco_lmt_prs in nco_lmt.o
       _nco_lmt_prs in nco_lmt.o
       _nco_lmt_udu_cnv in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_srt_ntg in nco_lst_utl.o
       _nco_srt_lph in nco_lst_utl.o
       _sng_lst_cat in nco_lst_utl.o
       _nco_calloc in nco_mmr.o
       _nco_malloc_err_hnt_prn in nco_mmr.o
       _nco_malloc in nco_mmr.o
       _nco_malloc_flg in nco_mmr.o
       _nco_malloc_flg in nco_mmr.o
       _nco_malloc_flg in nco_mmr.o
       _nco_malloc_dbg in nco_mmr.o
       _nco_malloc_dbg in nco_mmr.o
       _nco_malloc_dbg in nco_mmr.o
       _nco_realloc in nco_mmr.o
       _nco_mmr_stt in nco_mmr.o
       _nco_mmr_rusage_prn in nco_mmr.o
       _nco_cpy_var_val_mlt_lmt in nco_msa.o
       _nco_msa_lmt_all_int in nco_msa.o
       _nco_msa_lmt_all_int in nco_msa.o
       _nco_mss_val_cnf in nco_mss_val.o
       _nco_mss_val_get in nco_mss_val.o
       _nco_mss_val_get in nco_mss_val.o
       _nco_openmp_ini in nco_omp.o
       _nco_var_prc_crr_prn in nco_omp.o
       _nco_is_packable in nco_pck.o
       _nco_pck_map_get in nco_pck.o
       _nco_pck_map_get in nco_pck.o
       _nco_pck_plc_get in nco_pck.o
       _nco_pck_plc_get in nco_pck.o
       _nco_pck_plc_typ_get in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_upk in nco_pck.o
       _nco_var_upk in nco_pck.o
       _nco_var_upk_swp in nco_pck.o
       _nco_var_upk_swp in nco_pck.o
       _nco_pck_val in nco_pck.o
       _nco_pck_val in nco_pck.o
       _nco_pck_val in nco_pck.o
       _nco_pck_val in nco_pck.o
       _nco_prn_var_val_lmt in nco_prn.o
       _nco_prn_var_val_lmt in nco_prn.o
       _nco_prn_var_val_lmt in nco_prn.o
       _rec_var_dbg in nco_rec_var.o
       _rec_var_dbg in nco_rec_var.o
       _rec_var_dbg in nco_rec_var.o
       _rec_crd_chk in nco_rec_var.o
       _rec_crd_chk in nco_rec_var.o
       _nco_op_typ_get in nco_rth_utl.o
       _nco_op_prs_rlt in nco_rth_utl.o
       _ptr_unn_2_scl_dbl in nco_scl_utl.o
       _cvs_vrs_prs in nco_scm.o
       _cvs_vrs_prs in nco_scm.o
       _cvs_vrs_prs in nco_scm.o
       _cvs_vrs_prs in nco_scm.o
       _cvs_vrs_prs in nco_scm.o
       _cvs_vrs_prs in nco_scm.o
       _cvs_vrs_prs in nco_scm.o
       _copyright_prn in nco_scm.o
       _copyright_prn in nco_scm.o
       _sng_ascii_trn in nco_sng_utl.o
       _sng_ascii_trn in nco_sng_utl.o
       _sng_ascii_trn in nco_sng_utl.o
       _nco_var_avg in nco_var_avg.o
       _nco_var_avg in nco_var_avg.o
       _nco_var_meta_search in nco_var_lst.o
       _nco_var_lst_mk in nco_var_lst.o
       _nco_var_lst_mk in nco_var_lst.o
       _nco_var_lst_mk in nco_var_lst.o
       _nco_var_lst_crd_add in nco_var_lst.o
       _nco_var_lst_crd_ass_add in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_lst_mrg in nco_var_lst.o
       _nco_var_lst_mrg in nco_var_lst.o
       _nco_var_msk in nco_var_rth.o
       _nco_var_pwr in nco_var_rth.o
       _nco_cpy_var_dfn in nco_var_utl.o
       _nco_cpy_var_dfn_lmt in nco_var_utl.o
       _nco_cpy_var_val in nco_var_utl.o
       _nco_cpy_var_val_lmt in nco_var_utl.o
       _nco_var_dfn in nco_var_utl.o
       _nco_var_dfn in nco_var_utl.o
       _nco_var_dfn in nco_var_utl.o
       _nco_var_fll in nco_var_utl.o
       _nco_var_fll in nco_var_utl.o
   "_prg_get", referenced from:
       _nco_usg_prn in nco_ctl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_lmt_evl in nco_lmt.o
       _nco_msa_var_get in nco_msa.o
       _nco_msa_lmt_all_int in nco_msa.o
       _nco_msa_lmt_all_int in nco_msa.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_op_typ_get in nco_rth_utl.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_var_get in nco_var_utl.o
       _nco_var_dfn in nco_var_utl.o
   "_dbg_lvl_get", referenced from:
       _nco_aed_prc in nco_att_utl.o
       _nco_att_cpy in nco_att_utl.o
       _nco_hst_att_cat in nco_att_utl.o
       _nco_prs_aed_lst in nco_att_utl.o
       _nco_prs_aed_lst in nco_att_utl.o
       _nco_prs_rnm_lst in nco_att_utl.o
       _nco_bnr_open in nco_bnr.o
       _nco_bnr_open in nco_bnr.o
       _nco_bnr_close in nco_bnr.o
       _nco_bnr_close in nco_bnr.o
       _nco_bnr_close in nco_bnr.o
       _nco_bnr_wrt in nco_bnr.o
       _nco_bnr_wrt in nco_bnr.o
       _nco_var_cnf_dmn in nco_cnf_dmn.o
       _nco_var_cnf_dmn in nco_cnf_dmn.o
       _nco_var_cnf_dmn in nco_cnf_dmn.o
       _nco_var_dmn_rdr_mtd in nco_cnf_dmn.o
       _nco_var_dmn_rdr_mtd in nco_cnf_dmn.o
       _nco_var_dmn_rdr_mtd in nco_cnf_dmn.o
       _nco_var_dmn_rdr_val in nco_cnf_dmn.o
       _nco_var_dmn_rdr_val in nco_cnf_dmn.o
       _nco_var_cnf_typ in nco_cnf_typ.o
       _nco_cnv_mss_val_typ in nco_cnf_typ.o
       _nco_cnv_arm_inq in nco_cnv_arm.o
       _nco_cnv_ccm_ccsm_cf_inq in nco_cnv_csm.o
       _nco_cnv_ccm_ccsm_cf_inq in nco_cnv_csm.o
       _nco_cmp_get in nco_ctl.o
       _nco_mpi_get in nco_ctl.o
       _nco_exit in nco_ctl.o
       _nco_ddra in nco_ctl.o
       _nco_ddra in nco_ctl.o
       _nco_fl_cp in nco_fl_utl.o
       _nco_fl_cp in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_lst_mk in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mk_lcl in nco_fl_utl.o
       _nco_fl_mv in nco_fl_utl.o
       _nco_fl_mv in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_out_open in nco_fl_utl.o
       _nco_fl_rm in nco_fl_utl.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lmt_evl in nco_lmt.o
       _nco_lst_prs_1D in nco_lst_utl.o
       _nco_lst_prs_1D in nco_lst_utl.o
       _nco_lst_prs_2D in nco_lst_utl.o
       _nco_msa_lmt_all_int in nco_msa.o
       _nco_mss_val_get in nco_mss_val.o
       _nco_openmp_ini in nco_omp.o
       _nco_pck_plc_get in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_dsk_inq in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_pck_mtd in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_pck in nco_pck.o
       _nco_var_upk in nco_pck.o
       _nco_var_upk_swp in nco_pck.o
       _nco_pck_val in nco_pck.o
       _nco_pck_val in nco_pck.o
       _nco_pck_val in nco_pck.o
       _nco_prn_var_val_lmt in nco_prn.o
       _rec_crd_chk in nco_rec_var.o
       _cvs_vrs_prs in nco_scm.o
       _cvs_vrs_prs in nco_scm.o
       _cvs_vrs_prs in nco_scm.o
       _cvs_vrs_prs in nco_scm.o
       _sng_ascii_trn in nco_sng_utl.o
       _nco_var_avg in nco_var_avg.o
       _nco_var_avg in nco_var_avg.o
       _nco_var_lst_mk in nco_var_lst.o
       _nco_var_lst_dvd in nco_var_lst.o
       _nco_cpy_var_val_lmt in nco_var_utl.o
       _nco_var_dfn in nco_var_utl.o
       _nco_var_dfn in nco_var_utl.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[3]: *** [libnco.la] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Warning: the following items did not execute (for nco):  
org.macports.activate org.macports.build org.macports.destroot  
org.macports.install


From blb at macports.org  Mon Dec  8 16:46:56 2008
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 8 Dec 2008 17:46:56 -0700
Subject: install manopen fails on 10.5.5
In-Reply-To: <3F9717BA-6AE3-4DFD-8CD4-DBC7F07EA6D3@me.com>
References: <3F9717BA-6AE3-4DFD-8CD4-DBC7F07EA6D3@me.com>
Message-ID: <20081209004656.GM506@ninagal.withay.com>

On Mon, Dec 08, 2008 at 06:19:08PM -0600, joseph davison said:
> Just installed macports on a new leopard installation on my macbook pro.
>
> Tried to install manopen and it blows up with:
> ManDocument.m: In function '-[ManDocument windowControllerDidLoadNib:]':
> ManDocument.m:328: error: 'NSSimpleHorizontalTypesetter' undeclared  
> (first use in this function)
> ManDocument.m:328: error: (Each undeclared identifier is reported only  
> once
> ManDocument.m:328: error: for each function it appears in.)
>
> and then some warnings.

Looks like a long-standing bug:

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

Bryan


From ryandesign at macports.org  Mon Dec  8 19:35:58 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Mon, 8 Dec 2008 21:35:58 -0600
Subject: nco fails to build & install on 10.5.5
In-Reply-To: <97EBE94B-B393-41AF-8174-D08DD4E3A5FA@me.com>
References: <97EBE94B-B393-41AF-8174-D08DD4E3A5FA@me.com>
Message-ID: <72483EC3-2F3A-4C74-8C4B-2D59A2B9249A@macports.org>


On Dec 8, 2008, at 18:23, joseph davison wrote:

> new Leopard installation on a macbook pro.
>
> installed netcdf, then tried to install nco
> hours later, after installing a new gcc and a new perl, and ... it  
> finally tried to do nco.
>
> Here's the nco build output:

[snip]

I don't see a ticket filed for this problem. Could you file one, please?



From blb at macports.org  Mon Dec  8 21:25:30 2008
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 8 Dec 2008 22:25:30 -0700
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <493DA7E3.1060209@macports.org>
References: <493D82AF.5080203@shopwatch.org>
	<20081208214114.GF506@ninagal.withay.com>
	<1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>
	<20081208224200.GL506@ninagal.withay.com>
	<493DA7E3.1060209@macports.org>
Message-ID: <20081209052530.GN506@ninagal.withay.com>

On Tue, Dec 09, 2008 at 10:04:03AM +1100, Joshua Root said:
[...]
> 
> Could the wrong libcurl be picked up if there is something like
> LDFLAGS=-L/opt/local/lib in the environment? If that's what happened to
> Jay, it shouldn't be a problem with selfupdate because the environment
> is sanitised.

Considering that the MacPorts port clears configure.cppflags and
configure.ldflags, I'm guessing the same should probably be done in
macports::selfupdate?

Bryan


> 
> - Josh

From severin.lists at kacianka.at  Tue Dec  9 01:09:56 2008
From: severin.lists at kacianka.at (Severin Kacianka)
Date: Tue, 09 Dec 2008 10:09:56 +0100
Subject: Problems linking against OSG on OS X Tiger (on a Power PC)
In-Reply-To: <59540D99-8712-4C8F-849B-02F03F4B39CB@macports.org>
References: <493BF25A.8030603@kacianka.at>
	<A786DE46-E8B1-40B1-BDD5-501293A69CA5@macports.org>
	<59540D99-8712-4C8F-849B-02F03F4B39CB@macports.org>
Message-ID: <493E35E4.3070002@kacianka.at>

Ryan Schmidt wrote:
> On Dec 7, 2008, at 15:39, Ryan Schmidt wrote:
> 
>> On Dec 7, 2008, at 09:57, Severin Kacianka wrote:
>>
>>> I hope I do not ask a too obvious question, but I am just trying to 
>>> get familiar with OSG and in the process want to be able to compile 
>>> it on Linux and OS X. On Linux I have no problems compiling a sample 
>>> program like this:
>>> g++ -I /usr/local/include/osg/ -losg -losgViewer -o foo test.cpp
>>>
>>> On OS X I installed OS X via macports. First I tried to compile it 
>>> directly form the sources, but ran into the bug described here:
>>> http://trac.macports.org/ticket/17294
>>>
>>> Compiling and installing via macports worked fine.
>>> However if I try to compile a sample program I get the following error:
>>>
>>> g++  -L/opt/local/lib/ -I/opt/local/include/  -losg -losgViewer -o 
>>> foo test.cpp
>>> /usr/bin/ld: warning can't open dynamic library: 
>>> libOpenThreads.11.dylib referenced from: /opt/local/lib//libosg.dylib 
>>> (checking for undefined symbols may be affected) (No such file or 
>>> directory, errno = 2)
>>> /usr/bin/ld: warning can't open dynamic library: libosgGA.48.dylib 
>>> referenced from: /opt/local/lib//libosgViewer.dylib (checking for 
>>> undefined symbols may be affected) (No such file or directory, errno 
>>> = 2)
>>> /usr/bin/ld: warning can't open dynamic library: libosgText.48.dylib 
>>> referenced from: /opt/local/lib//libosgViewer.dylib (checking for 
>>> undefined symbols may be affected) (No such file or directory, errno 
>>> = 2)
>>> /usr/bin/ld: warning can't open dynamic library: libosgDB.48.dylib 
>>> referenced from: /opt/local/lib//libosgViewer.dylib (checking for 
>>> undefined symbols may be affected) (No such file or directory, errno 
>>> = 2)
>>> /usr/bin/ld: warning can't open dynamic library: libosgUtil.48.dylib 
>>> referenced from: /opt/local/lib//libosgViewer.dylib (checking for 
>>> undefined symbols may be affected) (No such file or directory, errno 
>>> = 2)
>>> /usr/bin/ld: Undefined symbols:
>>> *snip long list of symbols*
>>> collect2: ld returned 1 exit status
>>>
>>> So for some reason ld cannot find the references from the libraries 
>>> among each other. The directory looks like this:
>>>
>>> libOpenThreads.11.dylib -> libOpenThreads.2.3.0.dylib
>>> libOpenThreads.2.3.0.dylib
>>> libOpenThreads.dylib -> libOpenThreads.11.dylib
>>>
>>>
>>> (other libs are linked in the same manner)
>>>
>>> So the libs are there, but somehow not referenced correctly. Does 
>>> anyone know what the problem may be, or any other way to use OSG on 
>>> OS X?
>>
>> I see that it's linked this way:
>>
>> $ otool -L /opt/local/lib/libosg.dylib
>> /opt/local/lib/libosg.dylib:
>>         libosg.48.dylib (compatibility version 48.0.0, current version 
>> 2.6.1)
>>         libOpenThreads.11.dylib (compatibility version 11.0.0, current 
>> version 2.3.0)
>>         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, 
>> current version 88.3.10)
>>         /System/Library/Frameworks/AGL.framework/Versions/A/AGL 
>> (compatibility version 1.0.0, current version 1.0.0)
>>         /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL 
>> (compatibility version 1.0.0, current version 1.0.0)
>>         /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)
>> $
>>
>> That looks wrong. It should look like this:
>>
>> $ otool -L /opt/local/lib/libosg.dylib
>> /opt/local/lib/libosg.dylib:
>>         /opt/local/lib/libosg.48.dylib (compatibility version 48.0.0, 
>> current version 2.6.1)
>>         /opt/local/lib/libOpenThreads.11.dylib (compatibility version 
>> 11.0.0, current version 2.3.0)
>>         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, 
>> current version 88.3.10)
>>         /System/Library/Frameworks/AGL.framework/Versions/A/AGL 
>> (compatibility version 1.0.0, current version 1.0.0)
>>         /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL 
>> (compatibility version 1.0.0, current version 1.0.0)
>>         /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)
>> $
>>
>> This probably means they're not using the -install_name parameter.
> 
> I filed a ticket:
> 
> http://trac.macports.org/ticket/17577
(uh - this time to the list and not only to you)

thank you very much for your help. With your pointers I managed to 
compile my sample program (although it takes a lot of hacking around):

It is possible to get around the linking errors by using ld's 
-dylib_file flag:
g++  -L/opt/local/lib/  -I/opt/local/include/  -losg -losgViewer -losgDB 
-losgGA -o foo test.cpp 
-Wl,-dylib_file,libOpenThreads.11.dylib:/opt/local/lib/libOpenThreads.2.3.0.dylib 
-Wl,-dylib_file,libosgGA.48.dylib:/opt/local/lib/libosgGA.2.6.1.dylib 
-Wl,-dylib_file,libosgText.48.dylib:/opt/local/lib/libosgText.2.6.1.dylib 
-Wl,-dylib_file,libosgDB.48.dylib:/opt/local/lib/libosgDB.2.6.1.dylib 
-Wl,-dylib_file,libosgUtil.48.dylib:/opt/local/lib/libosgUtil.2.6.1.dylib

(the -Wl,option,value just tells gcc to pass these arguments to the linker)

If you then try to execute the binary you will get the following error:
./foo
dyld: Library not loaded: libosg.48.dylib
   Referenced from: /Users/severin/Desktop/blabla/test/./foo
   Reason: image not found
Trace/BPT trap

to get around these errors, you have to symlink all the 'missing' 
libraries into the directory of foo:
ln -s /opt/local/lib/libosg.2.6.1.dylib libosg.48.dylib
(and repeat that for every library....)

then you will get the following error (if you load files):
./foo
Warning: Could not find plugin to read objects from file "dog_hut.3ds".
Warning: Could not find plugin to read objects from file "cube.3ds".
GraphicsWindowCarbon::grabFocusIfPointerInWindow

Now you have to symlink the osgPlugin directory into foo's directory:
ln -s /opt/local/lib/osgPlugins-2.6.1 .

Thank you again :)



From marco.calviani at gmail.com  Tue Dec  9 04:13:03 2008
From: marco.calviani at gmail.com (Marco Calviani)
Date: Tue, 9 Dec 2008 13:13:03 +0100
Subject: re-build again all the installed packages
Message-ID: <da5cd1900812090413w1e52c1d7j1614d560ff808d73@mail.gmail.com>

Dear list,
I've just install a new version of Xcode that contains apple-gcc-4.2. Since
now some ports are compiled with gcc-4.0 and some other with gcc-4.2, I
would like to know how (and if) is it possible to recompile all the packages
installed in the system, something like the #emerge -e world command present
in Gentoo linux distribution.

Regards,
Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081209/d6cb9777/attachment.html>

From jmr at macports.org  Tue Dec  9 04:30:30 2008
From: jmr at macports.org (Joshua Root)
Date: Tue, 09 Dec 2008 23:30:30 +1100
Subject: re-build again all the installed packages
In-Reply-To: <da5cd1900812090413w1e52c1d7j1614d560ff808d73@mail.gmail.com>
References: <da5cd1900812090413w1e52c1d7j1614d560ff808d73@mail.gmail.com>
Message-ID: <493E64E6.1040102@macports.org>

Marco Calviani wrote:
> Dear list,
> 
> I've just install a new version of Xcode that contains apple-gcc-4.2.
> Since now some ports are compiled with gcc-4.0 and some other with
> gcc-4.2, I would like to know how (and if) is it possible to recompile
> all the packages installed in the system, something like the #emerge -e
> world command present in Gentoo linux distribution.

MacPorts always uses /usr/bin/gcc-4.0 on Tiger and Leopard unless
overridden by the individual Portfile. So there should be no need to
recompile after upgrading XCode.

To rebuild everything you could use `sudo port -fn upgrade installed`,
though that won't rebuild things in correct dependency order. It may be
easier to just get a list of what's installed with `port installed`,
`sudo port -f uninstall installed`, then install everything again.

- Josh

From raimue at macports.org  Tue Dec  9 04:45:30 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Tue, 09 Dec 2008 13:45:30 +0100
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <20081209052530.GN506@ninagal.withay.com>
References: <493D82AF.5080203@shopwatch.org>	<20081208214114.GF506@ninagal.withay.com>	<1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>	<20081208224200.GL506@ninagal.withay.com>	<493DA7E3.1060209@macports.org>
	<20081209052530.GN506@ninagal.withay.com>
Message-ID: <493E686A.4070308@macports.org>

Bryan Blackburn wrote:
> Considering that the MacPorts port clears configure.cppflags and
> configure.ldflags, I'm guessing the same should probably be done in
> macports::selfupdate?

MacPorts already removes $prefix/bin and $prefix/sbin from PATH on
configure. See MP_PATH_SCAN in aclocal.m4. This ensures that it not only
works on selfupdate, but also on reinstalling/upgrading from a source
tarball.

Rainer


From marco.calviani at gmail.com  Tue Dec  9 04:57:24 2008
From: marco.calviani at gmail.com (Marco Calviani)
Date: Tue, 9 Dec 2008 13:57:24 +0100
Subject: re-build again all the installed packages
In-Reply-To: <493E64E6.1040102@macports.org>
References: <da5cd1900812090413w1e52c1d7j1614d560ff808d73@mail.gmail.com>
	<493E64E6.1040102@macports.org>
Message-ID: <da5cd1900812090457v724d91adsc6a471dfaceae96d@mail.gmail.com>

Ok thanks a lot.
marco

On Tue, Dec 9, 2008 at 1:30 PM, Joshua Root <jmr at macports.org> wrote:

> Marco Calviani wrote:
> > Dear list,
> >
> > I've just install a new version of Xcode that contains apple-gcc-4.2.
> > Since now some ports are compiled with gcc-4.0 and some other with
> > gcc-4.2, I would like to know how (and if) is it possible to recompile
> > all the packages installed in the system, something like the #emerge -e
> > world command present in Gentoo linux distribution.
>
> MacPorts always uses /usr/bin/gcc-4.0 on Tiger and Leopard unless
> overridden by the individual Portfile. So there should be no need to
> recompile after upgrading XCode.
>
> To rebuild everything you could use `sudo port -fn upgrade installed`,
> though that won't rebuild things in correct dependency order. It may be
> easier to just get a list of what's installed with `port installed`,
> `sudo port -f uninstall installed`, then install everything again.
>
> - Josh
>



-- 
Will I dream? Of course you will. All intelligent beings dream.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081209/c14cd775/attachment.html>

From lists-macports at shopwatch.org  Tue Dec  9 05:20:59 2008
From: lists-macports at shopwatch.org (Jay Levitt)
Date: Tue, 09 Dec 2008 08:20:59 -0500
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <493DA7E3.1060209@macports.org>
References: <493D82AF.5080203@shopwatch.org>	<20081208214114.GF506@ninagal.withay.com>	<1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>	<20081208224200.GL506@ninagal.withay.com>
	<493DA7E3.1060209@macports.org>
Message-ID: <493E70BB.9030108@shopwatch.org>

Joshua Root wrote:

> Could the wrong libcurl be picked up if there is something like
> LDFLAGS=-L/opt/local/lib in the environment? If that's what happened to
> Jay, it shouldn't be a problem with selfupdate because the environment
> is sanitised.

I do, in fact, have that:

CPATH=/opt/local/include
CPPFLAGS=-I/opt/local/include
LDFLAGS=-L/opt/local/lib
LIBTOOLIZE=/opt/local/bin/glibtoolize
PATH=/usr/local/bin:/usr/local/sbin:/Users/jay/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin:/Applications/Utilities/diglloyd/disktester:/usr/local/git/bin:/opt/local/lib/postgresql83/bin

I realized that, thanks to CrashPlan, I do in fact have a full backup of my 
system at many points-in-time, which should let me recreate the situation, 
assuming it didn't depend on some precise sequence of port installations.

What would be useful to you guys?  Are there files and links you want to 
know about, or verbose outputs of.. something..?



From lists-macports at shopwatch.org  Tue Dec  9 05:38:25 2008
From: lists-macports at shopwatch.org (Jay Levitt)
Date: Tue, 09 Dec 2008 08:38:25 -0500
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <20081208214114.GF506@ninagal.withay.com>
References: <493D82AF.5080203@shopwatch.org>
	<20081208214114.GF506@ninagal.withay.com>
Message-ID: <493E74D1.8030708@shopwatch.org>

Bryan Blackburn wrote:
> On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said:
>> I know this isn't a great bug report, because I already overwrote the fail 
>> case; sorry about that.
>>
>> I upgraded from a DMG-installed 1.6.0 to a built-from-source 1.7.0 beta 1. 
>> I then updated a bunch of ports, but I don't think libcurl was one of 
>> them.  (Is there a log?  I don't think there is.)
>>
>> Today, I tried using git, and got:
>>
>> dyld: Library not loaded: /opt/local/lib/libcurl.4.dylib
>>   Referenced from: /opt/local/bin/git
>>   Reason: Incompatible library version: git requires version 6.0.0 or  
>> later, but libcurl.4.dylib provides version 5.0.0
> 
> Did you happen to activate an older version of the curl port?  What does
> 'port installed curl' say, as here, 7.19.2_0 is installed and libcurl has a
> compat version of 6.0.0 and current 6.1.0.

Not intentionally.  I don't use curl directly, certainly not enough to know 
which version I need, so it would have been installed at some point with 
"port install curl", possibly later upgraded with "port upgrade curl", and 
then possibly cleaned up with "port uninstall -f outdated" if I saw multiple 
versions of it.

Does MacPorts log any history anywhere?  I don't think it does.  I do see 
two directories in /opt/local/var/macports/receipts/curl:

curl% ll
total 0
drwxr-xr-x  4 root  admin   136B Dec  8 15:17 7.19.2_0/
drwxr-xr-x  4 root  admin   136B Dec  8 15:10 7.19.2_0+ssl/

curl% ll 7.19.2_0
total 16
-rw-r--r--  1 root  admin   3.3K Dec  8 15:17 receipt.bz2
-rw-r--r--  1 root  admin   3.3K Dec  6 09:05 receipt.bz2.mpsaved
curl% ll 7.19.2_0+ssl
total 16
-rw-r--r--  1 root  admin   3.4K Dec  8 15:10 receipt.bz2
-rw-r--r--  1 root  admin   3.4K Dec  8 15:10 receipt.bz2.mpsaved





From jmr at macports.org  Tue Dec  9 05:39:38 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Dec 2008 00:39:38 +1100
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <493E70BB.9030108@shopwatch.org>
References: <493D82AF.5080203@shopwatch.org>	<20081208214114.GF506@ninagal.withay.com>	<1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>	<20081208224200.GL506@ninagal.withay.com>
	<493DA7E3.1060209@macports.org> <493E70BB.9030108@shopwatch.org>
Message-ID: <493E751A.7020707@macports.org>

Jay Levitt wrote:
> Joshua Root wrote:
> 
>> Could the wrong libcurl be picked up if there is something like
>> LDFLAGS=-L/opt/local/lib in the environment? If that's what happened to
>> Jay, it shouldn't be a problem with selfupdate because the environment
>> is sanitised.
> 
> I do, in fact, have that:
> 
> CPATH=/opt/local/include
> CPPFLAGS=-I/opt/local/include
> LDFLAGS=-L/opt/local/lib
> LIBTOOLIZE=/opt/local/bin/glibtoolize
> PATH=/usr/local/bin:/usr/local/sbin:/Users/jay/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin:/Applications/Utilities/diglloyd/disktester:/usr/local/git/bin:/opt/local/lib/postgresql83/bin
> 
> 
> I realized that, thanks to CrashPlan, I do in fact have a full backup of
> my system at many points-in-time, which should let me recreate the
> situation, assuming it didn't depend on some precise sequence of port
> installations.
> 
> What would be useful to you guys?  Are there files and links you want to
> know about, or verbose outputs of.. something..?

I'm not sure we should try to second-guess this for manual builds. If
the wrong libs can be picked up within selfupdate though, then we need
to fix that.

- Josh

From vincent-opdarw at vinc17.org  Tue Dec  9 09:00:25 2008
From: vincent-opdarw at vinc17.org (Vincent Lefevre)
Date: Tue, 9 Dec 2008 18:00:25 +0100
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <493E686A.4070308@macports.org>
References: <493D82AF.5080203@shopwatch.org>
	<20081208214114.GF506@ninagal.withay.com>
	<1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>
	<20081208224200.GL506@ninagal.withay.com>
	<493DA7E3.1060209@macports.org>
	<20081209052530.GN506@ninagal.withay.com>
	<493E686A.4070308@macports.org>
Message-ID: <20081209170025.GO24462@prunille.vinc17.org>

On 2008-12-09 13:45:30 +0100, Rainer M?ller wrote:
> MacPorts already removes $prefix/bin and $prefix/sbin from PATH on
> configure.

Does it also handle environment variables such as LIBRARY_PATH,
CPATH and C_INCLUDE_PATH?

-- 
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  Tue Dec  9 09:05:20 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Dec 2008 04:05:20 +1100
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <20081209170025.GO24462@prunille.vinc17.org>
References: <493D82AF.5080203@shopwatch.org>	<20081208214114.GF506@ninagal.withay.com>	<1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>	<20081208224200.GL506@ninagal.withay.com>	<493DA7E3.1060209@macports.org>	<20081209052530.GN506@ninagal.withay.com>	<493E686A.4070308@macports.org>
	<20081209170025.GO24462@prunille.vinc17.org>
Message-ID: <493EA550.70406@macports.org>

Vincent Lefevre wrote:
> On 2008-12-09 13:45:30 +0100, Rainer M?ller wrote:
>> MacPorts already removes $prefix/bin and $prefix/sbin from PATH on
>> configure.
> 
> Does it also handle environment variables such as LIBRARY_PATH,
> CPATH and C_INCLUDE_PATH?

It clears the entire environment apart from the list of keep_vars.

- Josh

From listacct at anthrotech.com  Tue Dec  9 11:20:58 2008
From: listacct at anthrotech.com (List Acct)
Date: Tue, 9 Dec 2008 12:20:58 -0700
Subject: Macports Install 1.6: cshrc shell not working
Message-ID: <08780B61-352E-4DB0-AEB1-4798B626586B@anthrotech.com>

Hello All,

Yesterday I installed Macports 1.6 in a Powerbook running Leopard  
10.5.5 in one of our user's computers,  so that I could install  
ImageMagick more easily.

After installing it, her cshrc shell environment was hosed.

When she typed  in echo $PATH, the Macports directory was returned.

/opt/local/bin

which had been added in her .bash_profile file, but she is not using  
bash.

So, the temporary fix was to create a shell script that sets  
environmental variables.

How do I permanently fix this problem without uninstalling Macports?

Thanks,
Eliot Lee

From jmr at macports.org  Tue Dec  9 11:36:57 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Dec 2008 06:36:57 +1100
Subject: Macports Install 1.6: cshrc shell not working
In-Reply-To: <08780B61-352E-4DB0-AEB1-4798B626586B@anthrotech.com>
References: <08780B61-352E-4DB0-AEB1-4798B626586B@anthrotech.com>
Message-ID: <493EC8D9.8000006@macports.org>

List Acct wrote:
> Hello All,
> 
> Yesterday I installed Macports 1.6 in a Powerbook running Leopard 10.5.5
> in one of our user's computers,  so that I could install ImageMagick
> more easily.
> 
> After installing it, her cshrc shell environment was hosed.
> 
> When she typed  in echo $PATH, the Macports directory was returned.
> 
> /opt/local/bin
> 
> which had been added in her .bash_profile file, but she is not using bash.
> 
> So, the temporary fix was to create a shell script that sets
> environmental variables.
> 
> How do I permanently fix this problem without uninstalling Macports?

Uninstalling MacPorts won't help (if you follow the usual instructions),
this is a shell configuration file issue. It sounds similar to what was
reported in this ticket: <http://trac.macports.org/ticket/17588>

>From a quick glance at the man page, it doesn't appear that tcsh will
read .bash_profile, so that won't be the problem. If it's the same
problem as in the ticket, a new .tcshrc will have been created with the
MacPorts environment stuff, thus causing .cshrc to be ignored. The
solution would thus be to combine .tcshc and .cshrc into one file.

- Josh

From listacct at anthrotech.com  Tue Dec  9 11:48:01 2008
From: listacct at anthrotech.com (List Acct)
Date: Tue, 9 Dec 2008 12:48:01 -0700
Subject: Macports Install 1.6: cshrc shell not working
In-Reply-To: <493EC8D9.8000006@macports.org>
References: <08780B61-352E-4DB0-AEB1-4798B626586B@anthrotech.com>
	<493EC8D9.8000006@macports.org>
Message-ID: <DBAFBA73-4B27-4FFA-86F4-B3A19069A89E@anthrotech.com>

Hello,

I read that ticket and assumed  it was a problem with 1.7rc1 based in  
the title of the ticket.

macports 1.7rc1 writes path variable to .tcshrc even when a .cshrc is  
present
Another Sys Admin and I modified the existing .tcshrc file to no   
avail. There was no .cshrc file, so I may try doing that next.

But again, I thought this was a problem with the new RC version of  
Macports, _not_ 1.6 stable, which is what I installed.

Thanks,
Eliot Lee

On Dec 9, 2008, at 12:36 PM, Joshua Root wrote:

> List Acct wrote:
>> Hello All,
>>
>> Yesterday I installed Macports 1.6 in a Powerbook running Leopard  
>> 10.5.5
>> in one of our user's computers,  so that I could install ImageMagick
>> more easily.
>>
>> After installing it, her cshrc shell environment was hosed.
>>
>> When she typed  in echo $PATH, the Macports directory was returned.
>>
>> /opt/local/bin
>>
>> which had been added in her .bash_profile file, but she is not  
>> using bash.
>>
>> So, the temporary fix was to create a shell script that sets
>> environmental variables.
>>
>> How do I permanently fix this problem without uninstalling Macports?
>
> Uninstalling MacPorts won't help (if you follow the usual  
> instructions),
> this is a shell configuration file issue. It sounds similar to what  
> was
> reported in this ticket: <http://trac.macports.org/ticket/17588>
>
>> From a quick glance at the man page, it doesn't appear that tcsh will
> read .bash_profile, so that won't be the problem. If it's the same
> problem as in the ticket, a new .tcshrc will have been created with  
> the
> MacPorts environment stuff, thus causing .cshrc to be ignored. The
> solution would thus be to combine .tcshc and .cshrc into one file.
>
> - Josh

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081209/3b829d2a/attachment.html>

From raimue at macports.org  Tue Dec  9 12:08:40 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Tue, 09 Dec 2008 21:08:40 +0100
Subject: Macports Install 1.6: cshrc shell not working
In-Reply-To: <DBAFBA73-4B27-4FFA-86F4-B3A19069A89E@anthrotech.com>
References: <08780B61-352E-4DB0-AEB1-4798B626586B@anthrotech.com>	<493EC8D9.8000006@macports.org>
	<DBAFBA73-4B27-4FFA-86F4-B3A19069A89E@anthrotech.com>
Message-ID: <493ED048.5080204@macports.org>

List Acct wrote:
> Hello,
> 
> I read that ticket and assumed  it was a problem with 1.7rc1 based in
> the title of the ticket.
> 
> macports 1.7rc1 writes path variable to .tcshrc even when a .cshrc is
> present
> Another Sys Admin and I modified the existing .tcshrc file to no  avail.
> There was no .cshrc file, so I may try doing that next.
> 
> But again, I thought this was a problem with the new RC version of
> Macports, _not_ 1.6 stable, which is what I installed.

There will be no 1.6.x release any more, so we can only address it in 1.7.x.

See http://guide.macports.org/#installing.shell which variables you need
to set up manually in the .cshrc.

Rainer

From jmr at macports.org  Tue Dec  9 12:26:00 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Dec 2008 07:26:00 +1100
Subject: Macports Install 1.6: cshrc shell not working
In-Reply-To: <DBAFBA73-4B27-4FFA-86F4-B3A19069A89E@anthrotech.com>
References: <08780B61-352E-4DB0-AEB1-4798B626586B@anthrotech.com>
	<493EC8D9.8000006@macports.org>
	<DBAFBA73-4B27-4FFA-86F4-B3A19069A89E@anthrotech.com>
Message-ID: <493ED458.2010307@macports.org>

List Acct wrote:
> Hello,
> 
> I read that ticket and assumed  it was a problem with 1.7rc1 based in
> the title of the ticket.
> 
> macports 1.7rc1 writes path variable to .tcshrc even when a .cshrc is
> present
> Another Sys Admin and I modified the existing .tcshrc file to no  avail.
> There was no .cshrc file, so I may try doing that next.
> 
> But again, I thought this was a problem with the new RC version of
> Macports, _not_ 1.6 stable, which is what I installed.

The problem may well be present in 1.6 as well, it was just reported
against 1.7.0rc1.

Did the MacPorts installer create the .tcshrc? If so, deleting it will
probably cause the shell to go back to getting its settings from
wherever it got them before. You'd then need to do the manual
configuration that Rainer pointed out, if you wish to use MacPorts.

- Josh

From listacct at anthrotech.com  Tue Dec  9 12:31:32 2008
From: listacct at anthrotech.com (List Acct)
Date: Tue, 9 Dec 2008 13:31:32 -0700
Subject: Macports Install 1.6: cshrc shell not working
In-Reply-To: <493ED458.2010307@macports.org>
References: <08780B61-352E-4DB0-AEB1-4798B626586B@anthrotech.com>
	<493EC8D9.8000006@macports.org>
	<DBAFBA73-4B27-4FFA-86F4-B3A19069A89E@anthrotech.com>
	<493ED458.2010307@macports.org>
Message-ID: <8D997C74-647A-40DB-A306-6CA2D84E9B9A@anthrotech.com>

Hello,

The .tcshrc file was already there.

So, I'll try moving that file before deleting it and see what happens.

Thanks,
Eliot Lee


On Dec 9, 2008, at 1:26 PM, Joshua Root wrote:

> List Acct wrote:
>> Hello,
>>
>> I read that ticket and assumed  it was a problem with 1.7rc1 based in
>> the title of the ticket.
>>
>> macports 1.7rc1 writes path variable to .tcshrc even when a .cshrc is
>> present
>> Another Sys Admin and I modified the existing .tcshrc file to no   
>> avail.
>> There was no .cshrc file, so I may try doing that next.
>>
>> But again, I thought this was a problem with the new RC version of
>> Macports, _not_ 1.6 stable, which is what I installed.
>
> The problem may well be present in 1.6 as well, it was just reported
> against 1.7.0rc1.
>
> Did the MacPorts installer create the .tcshrc? If so, deleting it will
> probably cause the shell to go back to getting its settings from
> wherever it got them before. You'd then need to do the manual
> configuration that Rainer pointed out, if you wish to use MacPorts.
>
> - Josh


From jmr at macports.org  Tue Dec  9 12:34:39 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Dec 2008 07:34:39 +1100
Subject: Macports Install 1.6: cshrc shell not working
In-Reply-To: <8D997C74-647A-40DB-A306-6CA2D84E9B9A@anthrotech.com>
References: <08780B61-352E-4DB0-AEB1-4798B626586B@anthrotech.com>
	<493EC8D9.8000006@macports.org>
	<DBAFBA73-4B27-4FFA-86F4-B3A19069A89E@anthrotech.com>
	<493ED458.2010307@macports.org>
	<8D997C74-647A-40DB-A306-6CA2D84E9B9A@anthrotech.com>
Message-ID: <493ED65F.4050201@macports.org>

List Acct wrote:
> Hello,
> 
> The .tcshrc file was already there.

OK. If the installer modified it, there should be a .tcshrc.mpsaved with
the old contents.

- Josh

From admin2 at enabled.com  Tue Dec  9 13:47:04 2008
From: admin2 at enabled.com (Noah)
Date: Tue, 09 Dec 2008 13:47:04 -0800
Subject: gtk2 build failing
Message-ID: <493EE758.5050208@enabled.com>

Hi there,

I am trying to figure out how to move forward here.  I find that I am 
running into a gtk2 build error

$ sudo port install easytag fdupes
--->  Building gtk2 with target all
Error: Target org.macports.build returned: shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_gtk2/work/gtk+-2.14.4" 
&& make all " returned error 2
Command output: make[2]: Nothing to be done for `all'.
Making all in gdk-pixbuf
make  all-recursive
Making all in pixops
make[4]: Nothing to be done for `all'.
Making all in gdk
make  all-recursive
Making all in x11
if /bin/sh ../../libtool --mode=compile /usr/bin/gcc-4.0 -DHAVE_CONFIG_H 
-I. -I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. 
-I../../gdk -I../../gdk -DG_DISABLE_CAST_CHECKS -D_REENTRANT 
-I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include 
-I/opt/local/include -I/opt/local/include/pango-1.0 
-I/opt/local/include/cairo -I/opt/local/include/pixman-1 
-I/opt/local/include/freetype2 -I/opt/local/include/libpng12 
-I/usr/X11/include      -I/opt/local/include -no-cpp-precomp -DX_LOCALE 
-I/usr/X11R6/include -DG_DISABLE_SINGLE_INCLUDES 
-DATK_DISABLE_SINGLE_INCLUDES -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES 
-DGTK_DISABLE_SINGLE_INCLUDES -I/opt/local/include -I/usr/X11/include 
  -DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops -fstrict-aliasing 
-Wall -MT gdkevents-x11.lo -MD -MP -MF ".deps/gdkevents-x11.Tpo" \
           -c -o gdkevents-x11.lo `test -f 'gdkevents-x11.c' || echo 
'./'`gdkevents-x11.c; \
         then mv -f ".deps/gdkevents-x11.Tpo" ".deps/gdkevents-x11.Plo"; \
         else rm -f ".deps/gdkevents-x11.Tpo"; exit 1; \
         fi
  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I../.. 
-DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. -I../../gdk -I../../gdk 
-DG_DISABLE_CAST_CHECKS -D_REENTRANT -I/opt/local/include/glib-2.0 
-I/opt/local/lib/glib-2.0/include -I/opt/local/include 
-I/opt/local/include/pango-1.0 -I/opt/local/include/cairo 
-I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 
-I/opt/local/include/libpng12 -I/usr/X11/include -I/opt/local/include 
-no-cpp-precomp -DX_LOCALE -I/usr/X11R6/include 
-DG_DISABLE_SINGLE_INCLUDES -DATK_DISABLE_SINGLE_INCLUDES 
-DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES 
-I/opt/local/include -I/usr/X11/include -DGDK_PIXBUF_DISABLE_DEPRECATED 
-O2 -funroll-loops -fstrict-aliasing -Wall -MT gdkevents-x11.lo -MD -MP 
-MF .deps/gdkevents-x11.Tpo -c gdkevents-x11.c  -fno-common -DPIC -o 
.libs/gdkevents-x11.o
gdkevents-x11.c: In function 'gdk_event_translate':
gdkevents-x11.c:2110: error: 'RRNotify' undeclared (first use in this 
function)
gdkevents-x11.c:2110: error: (Each undeclared identifier is reported 
only once
gdkevents-x11.c:2110: error: for each function it appears in.)
gdkevents-x11.c:2112: error: 'XRRNotifyEvent' undeclared (first use in 
this function)
gdkevents-x11.c:2112: error: 'notify' undeclared (first use in this 
function)
gdkevents-x11.c:2112: error: syntax error before ')' token
gdkevents-x11.c: In function 'gdk_x11_screen_get_window_manager_name':
gdkevents-x11.c:2721: warning: dereferencing type-punned pointer will 
break strict-aliasing rules
gdkevents-x11.c: In function 'gdk_x11_screen_supports_net_wm_hint':
gdkevents-x11.c:2821: warning: dereferencing type-punned pointer will 
break strict-aliasing rules
make[4]: *** [gdkevents-x11.lo] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

From jmr at macports.org  Tue Dec  9 13:57:18 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Dec 2008 08:57:18 +1100
Subject: gtk2 build failing
In-Reply-To: <493EE758.5050208@enabled.com>
References: <493EE758.5050208@enabled.com>
Message-ID: <493EE9BE.5050806@macports.org>

Noah wrote:
> Hi there,
> 
> I am trying to figure out how to move forward here.  I find that I am
> running into a gtk2 build error
<snip>
> gdkevents-x11.c:2110: error: 'RRNotify' undeclared (first use in this
> function)

Install xorg-libXrandr. See this ticket:
<http://trac.macports.org/ticket/17360>

- Josh

From cjsvance at gmail.com  Tue Dec  9 14:10:02 2008
From: cjsvance at gmail.com (Christopher Vance)
Date: Wed, 10 Dec 2008 09:10:02 +1100
Subject: repeated rebuilding
Message-ID: <ace45c0a0812091410k738503e6t8aa5655a523c08fb@mail.gmail.com>

When I do
   port upgrade outdated
some packages get rebuilt several times.

Isn't port supposed to calculate and order transitive dependencies to stop this?

-- 
Christopher Vance

From jmr at macports.org  Tue Dec  9 14:13:07 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Dec 2008 09:13:07 +1100
Subject: repeated rebuilding
In-Reply-To: <ace45c0a0812091410k738503e6t8aa5655a523c08fb@mail.gmail.com>
References: <ace45c0a0812091410k738503e6t8aa5655a523c08fb@mail.gmail.com>
Message-ID: <493EED73.6040106@macports.org>

Christopher Vance wrote:
> When I do
>    port upgrade outdated
> some packages get rebuilt several times.
> 
> Isn't port supposed to calculate and order transitive dependencies to stop this?

No, but it is meant to not rebuild anything that isn't outdated. What
you describe should not be possible unless you're using the -f option,
which causes ports to rebuilt even if they don't appear to be outdated.

- Josh

From frstan at bellsouth.net  Tue Dec  9 14:13:39 2008
From: frstan at bellsouth.net (William Davis)
Date: Tue, 9 Dec 2008 17:13:39 -0500
Subject: freeciv and freeciv-x11 ggz problem
Message-ID: <61C85017-4CE1-4DE0-B547-BAFB78453AE1@bellsouth.net>

unable to install  freeciv-x11 or activate freeciv:
macintosh:~ frstan$ sudo port install -d freeciv-x11
Password:
--->  Fetching freeciv-x11
--->  Attempting to fetch freeciv-2.1.8.tar.bz2 from http://superb-east.dl.sourceforge.net/freeciv
--->  Verifying checksum(s) for freeciv-x11
--->  Extracting freeciv-x11
--->  Configuring freeciv-x11
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_games_freeciv-x11/work/freeciv-2.1.8" && ./ 
configure --prefix=/opt/local --enable-client=gtk2 --with-readline -- 
with-zlib --enable-nls --with-sdl-prefix=/opt/local --with-libiconv- 
prefix=/opt/local --mandir=/opt/local/share/man " returned error 1
Command output: checking for C99 initializers... yes
checking for stdint.h... (cached) yes
checking for C99 stdint.h... yes
checking for gzgets in -lz... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for gzip... /opt/local/bin/gzip
checking for pkg-config... /opt/local/bin/pkg-config
checking for GTK+ - version >= 2.4.0... yes (version 2.14.4)
checking for X... libraries /usr/X11/lib, headers /usr/X11/include
checking whether Xfuncproto was supplied... no, found:
checking for sdl-config... /opt/local/bin/sdl-config
checking for SDL - version >= 1.0.0... yes
checking SDL/SDL_mixer.h usability... yes
checking SDL/SDL_mixer.h presence... yes
checking for SDL/SDL_mixer.h... yes
checking for Mix_OpenAudio in -lSDL_mixer... yes
checking building SDL_mixer support... yes
checking for GGZ library: libggz... yes (libraries /opt/local/lib,  
headers /opt/local/include)
checking for GGZ library version: 0.0.14... yes
checking for GGZ library: ggzmod... yes (libraries /opt/local/lib,  
headers /opt/local/include)
checking for GGZ configuration tool: ggz-config... /opt/local/bin/ggz- 
config
checking for GGZ library: ggz-gtk... no
configure: WARNING: no
   The library 'ggz-gtk' does not seem to be installed correctly.
   Headers searched in:  /opt/local/include /usr/local/include /usr/ 
include
   Libraries searched in:  /opt/local/lib /usr/local/lib /usr/local/ 
lib64 /usr/lib /usr/lib64
   Please read QuickStart.GGZ in order to fix this.


Error: Status 1 encountered during processing.
macintosh:~ frstan$ sudo port install -d freeciv
Password:
--->  Fetching freeciv
Please note that this port conflicts with port:freeciv-x11.
--->  Attempting to fetch freeciv-2.1.8.tar.bz2 from http://voxel.dl.sourceforge.net/freeciv
--->  Verifying checksum(s) for freeciv
--->  Extracting freeciv
--->  Configuring freeciv
--->  Building freeciv
--->  Staging freeciv into destroot
--->  Installing freeciv @2.1.8_0
--->  Activating freeciv @2.1.8_0
Error: Target org.macports.activate returned: Image error: /opt/local/ 
etc/ggz.modules is being used by the active gnome-games port.  Please  
deactivate this port first, or use the -f flag to force the activation.
Error: Status 1 encountered during processing.



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

Mundus vult decepi, ego non


From cjsvance at gmail.com  Tue Dec  9 15:30:38 2008
From: cjsvance at gmail.com (Christopher Vance)
Date: Wed, 10 Dec 2008 10:30:38 +1100
Subject: kdebase3 and libXdamage
Message-ID: <ace45c0a0812091530j6d761837m3b62141176596e99@mail.gmail.com>

Building kdebase3 fails on an up to date Leopard machine because
libXdamage is at 1.0.0, but kdebase3 wants 1.1.0.

Any thoughts?

-- 
Christopher Vance

From jmr at macports.org  Tue Dec  9 15:36:08 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Dec 2008 10:36:08 +1100
Subject: kdebase3 and libXdamage
In-Reply-To: <ace45c0a0812091530j6d761837m3b62141176596e99@mail.gmail.com>
References: <ace45c0a0812091530j6d761837m3b62141176596e99@mail.gmail.com>
Message-ID: <493F00E8.4030106@macports.org>

Christopher Vance wrote:
> Building kdebase3 fails on an up to date Leopard machine because
> libXdamage is at 1.0.0, but kdebase3 wants 1.1.0.
> 
> Any thoughts?

1. Install the latest XQuartz package from <http://xquartz.macosforge.org/>

2. Make Jeremy create an xorg-libXdamage port :-)

- Josh

From jwdavison at me.com  Tue Dec  9 16:19:17 2008
From: jwdavison at me.com (joseph davison)
Date: Tue, 09 Dec 2008 18:19:17 -0600
Subject: install manopen fails on 10.5.5
In-Reply-To: <3F9717BA-6AE3-4DFD-8CD4-DBC7F07EA6D3@me.com>
References: <3F9717BA-6AE3-4DFD-8CD4-DBC7F07EA6D3@me.com>
Message-ID: <F5C30EAA-4DAD-4126-BB96-B06A0A2F2EB9@me.com>

Oh I See...

    NSSimpleHorizontalTypeSetter was deprecated in 10.4 -- I suppose  
it's gone in 10.5, eh?    Joy -- I'll see if I can find an example or  
replacing it, but if the maintainer already knows how...

joe


On Dec 8, 2008, at 6:19 PM, joseph davison wrote:

> Just installed macports on a new leopard installation on my macbook  
> pro.
>
> Tried to install manopen and it blows up with:
> ManDocument.m: In function '-[ManDocument  
> windowControllerDidLoadNib:]':
> ManDocument.m:328: error: 'NSSimpleHorizontalTypesetter' undeclared  
> (first use in this function)
> ManDocument.m:328: error: (Each undeclared identifier is reported  
> only once
> ManDocument.m:328: error: for each function it appears in.)
>
> and then some warnings.
>
> Presuming it useful, here's the whole output from port -v install  
> macports
>
> --->  Fetching ManOpen
> --->  Verifying checksum(s) for ManOpen
> --->  Checksumming ManOpen-2.5.1.s.tar.gz
> --->  Extracting ManOpen
> --->  Extracting ManOpen-2.5.1.s.tar.gz
> --->  Configuring ManOpen
> --->  Building ManOpen with target all
> == Making all for i386 in ManOpen openman.tproj ==
> == Making ManOpen for i386 ==
> Pre-build setup...
> /bin/rm -f /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/derived_src/TrustedPrecomps.txt
> ......in cat2html
> ......in cat2rtf
> Building...
> ......in cat2html
> /usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/var/ 
> macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/PrivateHeaders/ -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/Headers/ -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/derived_src/ManOpen/cat2html.tproj -I. -pipe        -I/ 
> opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1           
> -c -o /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/objects-optimized/ManOpen/cat2html.tproj/ 
> cat2html.i386.o cat2html.c
> cat2html.l: In function 'cat2htmllex':
> cat2html.l:304: warning: pointer targets in passing argument 1 of  
> 'decodeUTF8' differ in signedness
> cat2html.l:311: warning: pointer targets in passing argument 1 of  
> 'decodeUTF8' differ in signedness
> /usr/bin/cc -o /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.app/Resources/cat2html   -L/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/objects-optimized/ManOpen/cat2html.tproj        -F/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1 -L/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1       - 
> arch i386  /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/objects-optimized/ManOpen/cat2html.tproj/ 
> cat2html.o       -framework Foundation
> ......in cat2rtf
> /usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/var/ 
> macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/PrivateHeaders/ -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/Headers/ -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/derived_src/ManOpen/cat2rtf.tproj -I. -pipe        -I/ 
> opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1           
> -c -o /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/objects-optimized/ManOpen/cat2rtf.tproj/cat2rtf.i386.o  
> cat2rtf.c
> cat2rtf.l: In function 'cat2rtflex':
> cat2rtf.l:344: warning: pointer targets in passing argument 1 of  
> 'decodeUTF8' differ in signedness
> cat2rtf.l:351: warning: pointer targets in passing argument 1 of  
> 'decodeUTF8' differ in signedness
> /usr/bin/cc -o /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.app/Resources/cat2rtf   -L/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/objects-optimized/ManOpen/cat2rtf.tproj        -F/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1 -L/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1       - 
> arch i386  /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/objects-optimized/ManOpen/cat2rtf.tproj/cat2rtf.o
> /usr/lib/mergeInfo PB.project CustomInfo.plist /opt/local/var/ 
> macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/derived_src/ManOpen/Java.plist -o /opt/local/var/ 
> macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.app/Resources/Info-macos.plist
> -n
> Copying English resources...
> Copied ManOpen.nib PrefPanel.nib DocController.nib ManOpen- 
> macintosh.nib Apropos.nib ManOpen-macos.nib ManPage.nib  
> FindPanel.nib Credits.rtf InfoPlist.strings
> Copied LinkCursor.tiff ManOpen-nextstep.tiff ManOpen.tiff  
> ManOpen.icns ManOpen.scriptSuite ManOpen.scriptTerminology
> /usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/var/ 
> macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.app/PrivateHeaders -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/derived_src/ManOpen -I. -pipe        -I/opt/local/var/ 
> macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1      - 
> ObjC       -c -o /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/objects-optimized/ManOpen/AproposDocument.i386.o  
> AproposDocument.m
> /usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/var/ 
> macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.app/PrivateHeaders -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/derived_src/ManOpen -I. -pipe        -I/opt/local/var/ 
> macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1      - 
> ObjC       -c -o /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/objects-optimized/ManOpen/FindPanelController.i386.o  
> FindPanelController.m
> /usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/var/ 
> macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.app/PrivateHeaders -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/derived_src/ManOpen -I. -pipe        -I/opt/local/var/ 
> macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1      - 
> ObjC       -c -o /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/objects-optimized/ManOpen/ManDocument.i386.o  
> ManDocument.m
> ManDocument.m: In function '-[ManDocument  
> windowControllerDidLoadNib:]':
> ManDocument.m:328: error: 'NSSimpleHorizontalTypesetter' undeclared  
> (first use in this function)
> ManDocument.m:328: error: (Each undeclared identifier is reported  
> only once
> ManDocument.m:328: error: for each function it appears in.)
> ManDocument.m: In function '-[ManTextView drawPageBorderWithSize:]':
> ManDocument.m:634: warning: 'widthOfString:' is deprecated (declared  
> at /System/Library/Frameworks/AppKit.framework/Headers/NSFont.h:216)
> ManDocument.m:644: warning: 'cString' is deprecated (declared at / 
> System/Library/Frameworks/Foundation.framework/Headers/NSString.h:345)
> ManDocument.m:645: warning: 'cString' is deprecated (declared at / 
> System/Library/Frameworks/Foundation.framework/Headers/NSString.h:345)
> ManDocument.m:645: warning: 'cStringLength' is deprecated (declared  
> at /System/Library/Frameworks/Foundation.framework/Headers/ 
> NSString.h:347)
> make[1]: *** [/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
> ManOpen.build/objects-optimized/ManOpen/ManDocument.i386.o] Error 1
> make: *** [all at ManOpen] Error 2
> Warning: the following items did not execute (for ManOpen):  
> org.macports.activate org.macports.build org.macports.destroot  
> org.macports.install
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From asato at cae1.aero.org  Tue Dec  9 16:48:57 2008
From: asato at cae1.aero.org (Max Asato)
Date: Tue, 9 Dec 2008 16:48:57 -0800
Subject: Distfiles mirror behind proxy
Message-ID: <20081210004857.GB16414@cae1.aero.org>

I'm looking for info and seasoned advice on getting MacPorts to work
for a moderate number of users (probably less than 50) behind an
authenticated http/ftp proxy.  We already provide an internal mirror 
server for CPAN, CTAN, and a bunch of Linux and BSD distributions so 
hardware and expertise in setting a mirror up for MacPorts would not 
be a problem.

Rsync to external servers isn't permitted from user desktops so
I've done a bit of testing with MacPorts 1.6 and have been able to
get the sync and selfupdate functions to work with an internal mirror
of the ports and source trees.  We'd have to customize the macports.conf
and sources.conf files in the installer but that seems to be workable.
Any other suggestions?

We would ideally like to mirror the primary distfile server internally
as well, but it sounds like that the new distserver.macports.org site
is tied to the 1.7 release.  I've futzed around with the mirror_sites.tcl
file a bit so it looks like it would be possible to direct our users
to an internal mirror first before trying to navigate through the
proxies.  Are there any reasons not to do this?  It looks like the
MASTER_SITE_LOCAL environment variable mechanism doesn't support
subdirectories under 1.6, does 1.7 work differently?

Last but not least, is there any way to get MacPorts to install packages
from a port archive file that was built on another system?  I've set the
portarchivemode parameter in macports.conf on two intel Macs (both
running 10.4.11), built a package on one and copied the archive over
to /opt/local/var/macports/packages/darwin/i386/ on the other but
MacPorts ignored the archive and attempted to fetch and build the
package again on the other system.  It would be nice if we didn't have
to subject every Scipy user to a bootstrap build of gcc.

TIA,

-Max

From jmr at macports.org  Tue Dec  9 17:14:35 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Dec 2008 12:14:35 +1100
Subject: Distfiles mirror behind proxy
In-Reply-To: <20081210004857.GB16414@cae1.aero.org>
References: <20081210004857.GB16414@cae1.aero.org>
Message-ID: <493F17FB.8050204@macports.org>

Max Asato wrote:
> We would ideally like to mirror the primary distfile server internally
> as well, but it sounds like that the new distserver.macports.org site
> is tied to the 1.7 release.  I've futzed around with the mirror_sites.tcl
> file a bit so it looks like it would be possible to direct our users
> to an internal mirror first before trying to navigate through the
> proxies.  Are there any reasons not to do this?  It looks like the
> MASTER_SITE_LOCAL environment variable mechanism doesn't support
> subdirectories under 1.6, does 1.7 work differently?

You could edit the macports mirror group in
/opt/local/share/macports/resources/port1.0/fetch/mirror_sites.tcl to
contain "http://your.mirror.host/:mirror".

> Last but not least, is there any way to get MacPorts to install packages
> from a port archive file that was built on another system?  I've set the
> portarchivemode parameter in macports.conf on two intel Macs (both
> running 10.4.11), built a package on one and copied the archive over
> to /opt/local/var/macports/packages/darwin/i386/ on the other but
> MacPorts ignored the archive and attempted to fetch and build the
> package again on the other system.  It would be nice if we didn't have
> to subject every Scipy user to a bootstrap build of gcc.

At least in theory, the -b option should do this.

- Josh

From asato at cae1.aero.org  Tue Dec  9 18:11:00 2008
From: asato at cae1.aero.org (Max Asato)
Date: Tue, 9 Dec 2008 18:11:00 -0800
Subject: Distfiles mirror behind proxy
In-Reply-To: <493F17FB.8050204@macports.org>
References: <20081210004857.GB16414@cae1.aero.org>
	<493F17FB.8050204@macports.org>
Message-ID: <20081210021100.GA18550@cae1.aero.org>

On Wed, Dec 10, 2008 at 12:14:35PM +1100, Joshua Root wrote:
> Max Asato wrote:
> > We would ideally like to mirror the primary distfile server internally
> > as well, but it sounds like that the new distserver.macports.org site
> > is tied to the 1.7 release.  I've futzed around with the mirror_sites.tcl
> > file a bit so it looks like it would be possible to direct our users
> > to an internal mirror first before trying to navigate through the
> > proxies.  Are there any reasons not to do this?  It looks like the
> > MASTER_SITE_LOCAL environment variable mechanism doesn't support
> > subdirectories under 1.6, does 1.7 work differently?
> 
> You could edit the macports mirror group in
> /opt/local/share/macports/resources/port1.0/fetch/mirror_sites.tcl to
> contain "http://your.mirror.host/:mirror".

Is there a simple way to get MacPorts to try our internal mirror first?  
This seems to set a default that is tried after everything else fails.
We could also add our mirror to the top of each group but won't these
changes get undone at the next "port sync" or "port selfupdate"?

> 
> > Last but not least, is there any way to get MacPorts to install packages
> > from a port archive file that was built on another system?  I've set the
> > portarchivemode parameter in macports.conf on two intel Macs (both
> > running 10.4.11), built a package on one and copied the archive over
> > to /opt/local/var/macports/packages/darwin/i386/ on the other but
> > MacPorts ignored the archive and attempted to fetch and build the
> > package again on the other system.  It would be nice if we didn't have
> > to subject every Scipy user to a bootstrap build of gcc.
> 
> At least in theory, the -b option should do this.
> 
> - Josh

I'll try that tonight.   Thanks.

-Max

From admin2 at enabled.com  Tue Dec  9 18:21:07 2008
From: admin2 at enabled.com (Noah)
Date: Tue, 09 Dec 2008 18:21:07 -0800
Subject: gtk2 build failing
In-Reply-To: <493EE9BE.5050806@macports.org>
References: <493EE758.5050208@enabled.com> <493EE9BE.5050806@macports.org>
Message-ID: <493F2793.9040701@enabled.com>

Joshua Root wrote:
> Noah wrote:
>> Hi there,
>>
>> I am trying to figure out how to move forward here.  I find that I am
>> running into a gtk2 build error
> <snip>
>> gdkevents-x11.c:2110: error: 'RRNotify' undeclared (first use in this
>> function)
> 
> Install xorg-libXrandr. See this ticket:
> <http://trac.macports.org/ticket/17360>
> 
> - Josh

thanks Joshua - that fixed it.


From jmr at macports.org  Tue Dec  9 18:27:42 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 10 Dec 2008 13:27:42 +1100
Subject: Distfiles mirror behind proxy
In-Reply-To: <20081210021100.GA18550@cae1.aero.org>
References: <20081210004857.GB16414@cae1.aero.org>
	<493F17FB.8050204@macports.org>
	<20081210021100.GA18550@cae1.aero.org>
Message-ID: <493F291E.9030203@macports.org>

Max Asato wrote:
> On Wed, Dec 10, 2008 at 12:14:35PM +1100, Joshua Root wrote:
>> Max Asato wrote:
>>> We would ideally like to mirror the primary distfile server internally
>>> as well, but it sounds like that the new distserver.macports.org site
>>> is tied to the 1.7 release.  I've futzed around with the mirror_sites.tcl
>>> file a bit so it looks like it would be possible to direct our users
>>> to an internal mirror first before trying to navigate through the
>>> proxies.  Are there any reasons not to do this?  It looks like the
>>> MASTER_SITE_LOCAL environment variable mechanism doesn't support
>>> subdirectories under 1.6, does 1.7 work differently?
>> You could edit the macports mirror group in
>> /opt/local/share/macports/resources/port1.0/fetch/mirror_sites.tcl to
>> contain "http://your.mirror.host/:mirror".
> 
> Is there a simple way to get MacPorts to try our internal mirror first?  
> This seems to set a default that is tried after everything else fails.
> We could also add our mirror to the top of each group but won't these
> changes get undone at the next "port sync" or "port selfupdate"?

Only the macports mirror group is always tried. The rest are only used
if the port specifies them in master_sites. MASTER_SITE_LOCAL will be
tried first, but it doesn't seem to support the :mirror tag (which looks
for the files on the server in dist_subdir).

This would be far easier with 1.7, where you could add your mirror to
the macports_distfiles mirror group, and it would be tried first because
it would presumably always have the lowest ping time.

- Josh

From afb at macports.org  Tue Dec  9 23:59:55 2008
From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=)
Date: Wed, 10 Dec 2008 08:59:55 +0100
Subject: Distfiles mirror behind proxy
In-Reply-To: <20081210004857.GB16414@cae1.aero.org>
References: <20081210004857.GB16414@cae1.aero.org>
Message-ID: <B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>

Max Asato wrote:

> Last but not least, is there any way to get MacPorts to install  
> packages
> from a port archive file that was built on another system?  I've  
> set the
> portarchivemode parameter in macports.conf on two intel Macs (both
> running 10.4.11), built a package on one and copied the archive over
> to /opt/local/var/macports/packages/darwin/i386/ on the other but
> MacPorts ignored the archive and attempted to fetch and build the
> package again on the other system.  It would be nice if we didn't have
> to subject every Scipy user to a bootstrap build of gcc.

That sounds correct...

If you run MacPorts in debugging mode (port -d), you should get
some output telling you what happened to the unarchive phase...
But when you enable portarchivemode=yes, it is supposed to try
"unarchive" (binary) before doing the "destroot" (source build)

--anders


From milosh at macports.org  Wed Dec 10 01:02:16 2008
From: milosh at macports.org (Emmanuel Hainry)
Date: Wed, 10 Dec 2008 10:02:16 +0100
Subject: repeated rebuilding
In-Reply-To: <493EED73.6040106@macports.org>
References: <ace45c0a0812091410k738503e6t8aa5655a523c08fb@mail.gmail.com>
	<493EED73.6040106@macports.org>
Message-ID: <20081210090216.GA1998@weetamoe.loria.fr>

Citando Joshua Root :
> Christopher Vance wrote:
> > When I do
> >    port upgrade outdated
> > some packages get rebuilt several times.
> > 
> > Isn't port supposed to calculate and order transitive dependencies to stop this?
> 
> No, but it is meant to not rebuild anything that isn't outdated. What
> you describe should not be possible unless you're using the -f option,
> which causes ports to rebuilt even if they don't appear to be outdated.
> 

Or if a dependency (say libfoo) is outdated: both the dependent (say
bar) and libfoo belong to "outdated". When port upgrades bar, it will
first upgrade its dependencies hence libfoo. When arrives the time to
upgrade libfoo, it will upgrade it once more.

Emmanuel

From jmr at macports.org  Wed Dec 10 05:15:05 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 00:15:05 +1100
Subject: repeated rebuilding
In-Reply-To: <20081210090216.GA1998@weetamoe.loria.fr>
References: <ace45c0a0812091410k738503e6t8aa5655a523c08fb@mail.gmail.com>	<493EED73.6040106@macports.org>
	<20081210090216.GA1998@weetamoe.loria.fr>
Message-ID: <493FC0D9.9070505@macports.org>

Emmanuel Hainry wrote:
> Citando Joshua Root :
>> Christopher Vance wrote:
>>> When I do
>>>    port upgrade outdated
>>> some packages get rebuilt several times.
>>>
>>> Isn't port supposed to calculate and order transitive dependencies to stop this?
>> No, but it is meant to not rebuild anything that isn't outdated. What
>> you describe should not be possible unless you're using the -f option,
>> which causes ports to rebuilt even if they don't appear to be outdated.
>>
> 
> Or if a dependency (say libfoo) is outdated: both the dependent (say
> bar) and libfoo belong to "outdated". When port upgrades bar, it will
> first upgrade its dependencies hence libfoo. When arrives the time to
> upgrade libfoo, it will upgrade it once more.

Sure, except the second time libfoo won't be outdated and hence won't be
rebuilt.

- Josh

From osna at ginko.de  Wed Dec 10 06:14:06 2008
From: osna at ginko.de (Joachim Oosnaabryg)
Date: Wed, 10 Dec 2008 15:14:06 +0100
Subject: Install or use problem: no .profile created
Message-ID: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>


Hello Helpers,

I wanted to use the Import RTF Function in LyX (LaTeX) with the  
converter "rtf2latex2e" which is an available port on MacPorts
http://www.macports.org/ports.php?by=name&substr=rtf2latex2e

The advice came from the LyX user list:
> If there is no native os x version, then install macports (<http:// 
> www.macports.org/>), and from there install the needed packages.

I followed the advice, downloaded the Mac-OSX 10.4 Tiger version of  
MacPorts, made the standard MacPorts-1.6.0-10.4-Tiger.dmg installing,  
the installer program said "MacPorts have been successfully installed  
at your system" or the like,

but now I'm puzzling about:

==> How to "install the needed packages" (i. e. the rtf2latex2e  
script or package) "from there" (MacPorts?).

Testwise I called in the Terminal
sudo port -d selfupdate
with the answer: "sudo: port: command not found"

Therefore I ask you:

How can I proof if MacPorts is installed rightly?

Of course probably I also need some "first help" to use it at all,  
especially how to install then an unix application like the  
rtf2latex2e converter?

Hopefully,
Goutgaun! joachim
--
MacTeXLive 2008 - TeXShop 2.18-svn - LyX 1.6
MacBook Pro OSX 10.4.11 Tiger




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081210/50d1e237/attachment.html>

From jmr at macports.org  Wed Dec 10 06:39:17 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 01:39:17 +1100
Subject: Install or use problem: no .profile created
In-Reply-To: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>
References: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>
Message-ID: <493FD495.7020301@macports.org>

Joachim Oosnaabryg wrote:
> 
> 
> Hello Helpers,
> 
> I wanted to use the Import RTF Function in LyX (LaTeX) with the
> converter "rtf2latex2e" which is an available port on MacPorts
> http://www.macports.org/ports.php?by=name&substr=rtf2latex2e
> <http://www.macports.org/ports.php?by=name&substr=rtf2latex2e>
> 
> The advice came from the LyX user list:
>> If there is no native os x version, then install macports
>> (<http://www.macports.org/>), and from there install the needed packages.
> 
> I followed the advice, downloaded the Mac-OSX 10.4 Tiger version of
> MacPorts, made the standard MacPorts-1.6.0-10.4-Tiger.dmg installing,
> the installer program said "MacPorts have been successfully installed at
> your system" or the like,
> 
> but now I'm puzzling about:
> 
> ==> How to "install the needed packages" (i. e. the rtf2latex2e script
> or package) "from there" (MacPorts?).
> 
> Testwise I called in the Terminal
> sudo port -d selfupdate
> with the answer: "sudo: port: command not found"
> 
> Therefore I ask you:
> 
> How can I proof if MacPorts is installed rightly?

MacPorts is installed into /opt/local, so to use the port command, you
need to have /opt/local/bin in your PATH. See
<http://guide.macports.org/#installing.shell>.

The installer for MacPorts 1.7 will do this for you more reliably.

- Josh

From s.wiggins at bristol.ac.uk  Wed Dec 10 06:53:13 2008
From: s.wiggins at bristol.ac.uk (Stephen Wiggins)
Date: Wed, 10 Dec 2008 14:53:13 +0000
Subject: Installation Problem: "run postflight script for MacPorts-1.6.0"
Message-ID: <964B57A2-C5AC-42B4-8EB1-EBC20C3EAA3D@bristol.ac.uk>

My installation failed with the following message:

The following install step failed: run postflight script for  
MacPorts-1.6.0. Contact the software manufacturer for assistance.





I would be grateful for any help.



Thanks,

Steve



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081210/4435caf9/attachment.html>

From frstan at bellsouth.net  Wed Dec 10 07:31:51 2008
From: frstan at bellsouth.net (William Davis)
Date: Wed, 10 Dec 2008 10:31:51 -0500
Subject: Installation Problem: "run postflight script for MacPorts-1.6.0"
In-Reply-To: <964B57A2-C5AC-42B4-8EB1-EBC20C3EAA3D@bristol.ac.uk>
References: <964B57A2-C5AC-42B4-8EB1-EBC20C3EAA3D@bristol.ac.uk>
Message-ID: <1DD88F83-D242-4BAA-A280-E93DD234E20B@bellsouth.net>


On Dec 10, 2008, at 9:53 AM, Stephen Wiggins wrote:

> My installation failed with the following message:
>
> The following install step failed: run postflight script for  
> MacPorts-1.6.0. Contact the software manufacturer for assistance.
>
>
>
>
>
> I would be grateful for any help.
>
>
>
> Thanks,
>
> Steve
>
>

Joshua Root just answered this same question for some one else. He  
wrote:
MacPorts is installed into /opt/local, so to use the port command, you
need to have /opt/local/bin in your PATH. See
<http://guide.macports.org/#installing.shell>.

The installer for MacPorts 1.7 will do this for you more reliably.

- Josh


William Davis
frstanATbellsouthDOTnet
Mac OS X.5.5 Darwin 9.5.0
XQuartz 2.3.2_rc3 (xorg-server 1.4.2-apple27)
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/20081210/c59f8d08/attachment.html>

From jmr at macports.org  Wed Dec 10 07:37:00 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 02:37:00 +1100
Subject: Installation Problem: "run postflight script for MacPorts-1.6.0"
In-Reply-To: <1DD88F83-D242-4BAA-A280-E93DD234E20B@bellsouth.net>
References: <964B57A2-C5AC-42B4-8EB1-EBC20C3EAA3D@bristol.ac.uk>
	<1DD88F83-D242-4BAA-A280-E93DD234E20B@bellsouth.net>
Message-ID: <493FE21C.5090601@macports.org>

William Davis wrote:
> 
> On Dec 10, 2008, at 9:53 AM, Stephen Wiggins wrote:
> 
>> My installation failed with the following message:
>>
>> The following install step failed: run postflight script for
>> MacPorts-1.6.0. Contact the software manufacturer for assistance.
>>
>>
>>
>> I would be grateful for any help.
>>
>>
>> Thanks,
>>
>> Steve
>>
>>
> 
> Joshua Root just answered this same question for some one else. He wrote:
> MacPorts is installed into /opt/local, so to use the port command, you
> need to have /opt/local/bin in your PATH. See
> <http://guide.macports.org/#installing.shell>.
> 
> The installer for MacPorts 1.7 will do this for you more reliably.

Actually, this message usually results from the initial 'port
selfupdate' failing. This can happen if you don't have Internet
connectivity, or if rsync is blocked.

If you can run 'sudo port selfupdate' manually afterwards and it
succeeds, everything should be fine.

- Josh

From osna at ginko.de  Wed Dec 10 07:37:31 2008
From: osna at ginko.de (Joachim Oosnaabryg)
Date: Wed, 10 Dec 2008 16:37:31 +0100
Subject: Install or use problem: no .profile created
In-Reply-To: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>
References: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>
Message-ID: <4D604997-E9E0-4924-8C36-08C6A051C7D6@ginko.de>

Am 10.12.2008 um 15:14 schrieb Joachim Oosnaabryg:
> Testwise I called in the Terminal
> sudo port -d selfupdate
> with the answer: "sudo: port: command not found"
>
> Therefore I ask you:
>
> How can I proof if MacPorts is installed rightly?

Hey, additionally I add the output of env:

localhost:/ joachim$ env
TERM_PROGRAM=Apple_Terminal
TERM=xterm-color
SHELL=/bin/bash
TERM_PROGRAM_VERSION=133-1
OLDPWD=/Developer/Applications
USER=joachim
__CF_USER_TEXT_ENCODING=0x1F5:0:3
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/texbin
PWD=/
SHLVL=1
HOME=/Users/joachim
SECURITYSESSIONID=fa0ee0
_=/usr/bin/env

Thereover, I'm wondering that most of the locations, that are  
mentioned for the case of uninstalling MacPorts,
http://guide.macports.org/#installing.macports.uninstalling
an my HD do not exist ore are empty, especially

- no /etc/paths.d/macports
- no /etc/paths.d/
- no /Library/StartupItems/DarwinPortsStartup
- no /Library/Tcl/macports1.0

Hope that helps (for helping ;-)

Goutgaun! joachim
--
MacTeXLive 2008 - TeXShop 2.18-svn - LyX 1.6
MacBook Pro OSX 10.4.11 Tiger





From deliverable at gmail.com  Wed Dec 10 07:50:53 2008
From: deliverable at gmail.com (Alexy Khrabrov)
Date: Wed, 10 Dec 2008 10:50:53 -0500
Subject: plplot fails to build
Message-ID: <7902A353-6A6E-4B58-9DAD-DE986E3DFAE7@gmail.com>

Tried to build plplot today, it starts by pulling half the Horn of  
Africa such as gcc 4.2.4, tk, and such, and eventually bails with

/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_science_plplot/work/plplot-5.9.0/drivers/ 
cairo.c:43:24: error: cairo-xlib.h: No such file or directory

Where do I get a fitting cairo-xlib.h to give it?
Cheers,
Alexy

From jmr at macports.org  Wed Dec 10 07:55:12 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 02:55:12 +1100
Subject: Install or use problem: no .profile created
In-Reply-To: <4D604997-E9E0-4924-8C36-08C6A051C7D6@ginko.de>
References: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>
	<4D604997-E9E0-4924-8C36-08C6A051C7D6@ginko.de>
Message-ID: <493FE660.3050103@macports.org>

Joachim Oosnaabryg wrote:
> Am 10.12.2008 um 15:14 schrieb Joachim Oosnaabryg:
>> Testwise I called in the Terminal
>> sudo port -d selfupdate
>> with the answer: "sudo: port: command not found"
>>
>> Therefore I ask you:
>>
>> How can I proof if MacPorts is installed rightly?
> 
> Hey, additionally I add the output of env:
> 
> localhost:/ joachim$ env
> TERM_PROGRAM=Apple_Terminal
> TERM=xterm-color
> SHELL=/bin/bash
> TERM_PROGRAM_VERSION=133-1
> OLDPWD=/Developer/Applications
> USER=joachim
> __CF_USER_TEXT_ENCODING=0x1F5:0:3
> PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/texbin
> PWD=/
> SHLVL=1
> HOME=/Users/joachim
> SECURITYSESSIONID=fa0ee0
> _=/usr/bin/env
> 
> Thereover, I'm wondering that most of the locations, that are mentioned
> for the case of uninstalling MacPorts,
> http://guide.macports.org/#installing.macports.uninstalling
> an my HD do not exist ore are empty, especially
> 
> - no /etc/paths.d/macports
> - no /etc/paths.d/
> - no /Library/StartupItems/DarwinPortsStartup
> - no /Library/Tcl/macports1.0

I don't see the connection between that and your environment, but it's
true that no single version of MacPorts/DarwinPorts will install in all
of the places given in the uninstall instructions.
/Library/Tcl/macports1.0 should definitely be present and non-empty if
you installed the current version from the .dmg.

- Josh

From deliverable at gmail.com  Wed Dec 10 08:31:08 2008
From: deliverable at gmail.com (Alexy Khrabrov)
Date: Wed, 10 Dec 2008 11:31:08 -0500
Subject: plplot fails to build
In-Reply-To: <7902A353-6A6E-4B58-9DAD-DE986E3DFAE7@gmail.com>
References: <7902A353-6A6E-4B58-9DAD-DE986E3DFAE7@gmail.com>
Message-ID: <7c737f300812100831k5fc554bfgd6841a9422a48664@mail.gmail.com>

Ah, in fact I built the whole gnome stack with +no_x11 (gtk-osx), and
plplot apparently supports cairo quartz drivers -- we just need to
tell it not to use X11 somehow.

> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_plplot/work/plplot-5.9.0/drivers/cairo.c:43:24:
> error: cairo-xlib.h: No such file or directory

Also, plplot variants only include python, java, and octave.  Who
decides that OCaml and Ada are not needed on a Mac?  :)   Similarly,
SWIG lacks OCaml although it has it in the source.  What's the idea
with cutting things from the ports?  Can there be a "full" install by
default -- if a package provides everything?  E.g., one may have OCaml
from source, so you may use OCaml bingings even if OCaml is not in
macports.

Cheers,
Alexy

From pgijnxn02 at sneakemail.com  Wed Dec 10 08:45:59 2008
From: pgijnxn02 at sneakemail.com (Joel Thibault (MacPorts))
Date: Wed, 10 Dec 2008 11:45:59 -0500
Subject: Configure error? vim wouldn't build without linking x11
Message-ID: <7a665ffc0812100845q3f3daea5xe40142ca5d326b1a@mail.gmail.com>

It appears that either configure is not detecting my system properly
or vim depends on X and is not looking for it.

When I tried to upgrade vim, the linker kept failing with this error.
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols:
__Xsetlocale

Adding -lX11 to the linker command line enabled it to build and now I
have the new vim.

Maybe there should be a no_x11 variant, too?

OS X Tiger 10.4.11
Macports Trunk

I saved the output from port -d upgrade -cuv vim, but I didn't want to
paste 1452 lines :)  Would any of that be useful?
Joel


-- 
Joel Thibault [AIM: Jole Tebo]
Software Engineer in Boston

From jmr at macports.org  Wed Dec 10 08:49:28 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 03:49:28 +1100
Subject: plplot fails to build
In-Reply-To: <7c737f300812100831k5fc554bfgd6841a9422a48664@mail.gmail.com>
References: <7902A353-6A6E-4B58-9DAD-DE986E3DFAE7@gmail.com>
	<7c737f300812100831k5fc554bfgd6841a9422a48664@mail.gmail.com>
Message-ID: <493FF318.5030604@macports.org>

Alexy Khrabrov wrote:
> Ah, in fact I built the whole gnome stack with +no_x11 (gtk-osx), and
> plplot apparently supports cairo quartz drivers -- we just need to
> tell it not to use X11 somehow.
> 
>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_plplot/work/plplot-5.9.0/drivers/cairo.c:43:24:
>> error: cairo-xlib.h: No such file or directory
> 
> Also, plplot variants only include python, java, and octave.  Who
> decides that OCaml and Ada are not needed on a Mac?  :)   Similarly,
> SWIG lacks OCaml although it has it in the source.  What's the idea
> with cutting things from the ports?  Can there be a "full" install by
> default -- if a package provides everything?  E.g., one may have OCaml
> from source, so you may use OCaml bingings even if OCaml is not in
> macports.

Mostly it's the sort of lame tradeoff between too many dependencies and
not enough functionality that comes from the lack of a fix for
<http://trac.macports.org/ticket/126>.

Also there are factors like simply nobody thought to add an ocaml
variant. We're not going to start building against random user-installed
software that may or may not work. See
<http://trac.macports.org/wiki/FAQ#WhyisMacPortsusingitsownlibraries>.

- Josh

From osna at ginko.de  Wed Dec 10 09:22:42 2008
From: osna at ginko.de (Joachim Oosnaabryg)
Date: Wed, 10 Dec 2008 18:22:42 +0100
Subject: Install or use problem: no .profile created
In-Reply-To: <493FE660.3050103@macports.org>
References: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>
	<4D604997-E9E0-4924-8C36-08C6A051C7D6@ginko.de>
	<493FE660.3050103@macports.org>
Message-ID: <B7F3937F-648C-4F9F-B739-26F871BA23FF@ginko.de>

Am 10.12.2008 um 16:55 schrieb Joshua Root:
> /Library/Tcl/macports1.0 should definitely be present and non-empty if
> you installed the current version from the .dmg.

This _is_ the case on my HD, indeed.

> true that no single version of MacPorts/DarwinPorts will install in  
> all
> of the places given in the uninstall instructions.

OK, but neither =>/Applications/DarwinPorts \
nor 			=>/Applications/MacPorts \
are there (I forgot to mention that in the last message)!

To give full information, ls -a in /Library/Tcl/macports1.0 gives:

.                       	macports_autoconf.tcl   	macports_util.tcl
..                     		macports_dlist.tcl     	   	pkgIndex.tcl
MacPorts.dylib          macports_fastload.tcl
macports.tcl          	macports_index.tcl

Together not more than 192 kB,
and the MacPorts-1.6.0-10.4-Tiger.dmg in my download directory has  
580 kB, the installer package MacPorts-1.6.0-10.4-Tiger.dmg therein  
620 kB, and it's content is:

.               Archive.bom     Info.plist      Resources
..              Archive.pax.gz  PkgInfo

But I didn't find any file ?.profile? on my HD..

Before downloading and installing MacPorts I updated my X11  
installation as recommanded, from the Apple Webside.

"On Mac OS X 10.4, look for files X11User.pkg & X11SDK.pkg in / 
Library/Receipts/", ==> TRUE

"To verify the presence of both, check for files  
com.apple.pkg.X11User.bom & com.apple.pkg.X11SDKLeo.bom in /Library/ 
Receipts/boms/"
==> FALSE, no /boms there.

Many thanks, Joshua, for your endeavor! Should I suppy other  
information?

Goutgaun! joachim
--
MacTeXLive 2008 - TeXShop 2.18-svn - LyX 1.6
MacBook Pro OSX 10.4.11 Tiger





From deliverable at gmail.com  Wed Dec 10 09:21:30 2008
From: deliverable at gmail.com (Alexy Khrabrov)
Date: Wed, 10 Dec 2008 12:21:30 -0500
Subject: plplot fails to build
In-Reply-To: <493FF318.5030604@macports.org>
References: <7902A353-6A6E-4B58-9DAD-DE986E3DFAE7@gmail.com>
	<7c737f300812100831k5fc554bfgd6841a9422a48664@mail.gmail.com>
	<493FF318.5030604@macports.org>
Message-ID: <C78585FA-CBFA-4D96-8BD2-1A5E7200F8F1@gmail.com>


On Dec 10, 2008, at 11:49 AM, Joshua Root wrote:

> Alexy Khrabrov wrote:
>> Ah, in fact I built the whole gnome stack with +no_x11 (gtk-osx), and
>> plplot apparently supports cairo quartz drivers -- we just need to
>> tell it not to use X11 somehow.
>>
>>> /opt/local/var/macports/build/ 
>>> _opt_local_var_macports_sources_rsync 
>>> .macports.org_release_ports_science_plplot/work/plplot-5.9.0/ 
>>> drivers/cairo.c:43:24:
>>> error: cairo-xlib.h: No such file or directory

I still wonder whether anybody knows how to make plplot build with  
+no_x11 -- it is using cmake which is different from make.

>> Also, plplot variants only include python, java, and octave.  Who
>> decides that OCaml and Ada are not needed on a Mac?  :)   Similarly,
>> SWIG lacks OCaml although it has it in the source.  What's the idea
>> with cutting things from the ports?  Can there be a "full" install by
>> default -- if a package provides everything?  E.g., one may have  
>> OCaml
>> from source, so you may use OCaml bingings even if OCaml is not in
>> macports.
>
> Mostly it's the sort of lame tradeoff between too many dependencies  
> and
> not enough functionality that comes from the lack of a fix for
> <http://trac.macports.org/ticket/126>.


How do I see (a) all variants the port provides, (b) the variants the  
port is installed with?  Then, how do I change (b) by selecting other  
variants from (a)?

Is it possible to add +x11 to gtk things compiled as +no_x11 without  
forcing those things of using quartz to use x11, selectively?

Cheers,
Alexy

From jmr at macports.org  Wed Dec 10 10:28:36 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 05:28:36 +1100
Subject: plplot fails to build
In-Reply-To: <C78585FA-CBFA-4D96-8BD2-1A5E7200F8F1@gmail.com>
References: <7902A353-6A6E-4B58-9DAD-DE986E3DFAE7@gmail.com>
	<7c737f300812100831k5fc554bfgd6841a9422a48664@mail.gmail.com>
	<493FF318.5030604@macports.org>
	<C78585FA-CBFA-4D96-8BD2-1A5E7200F8F1@gmail.com>
Message-ID: <49400A54.7090900@macports.org>

Alexy Khrabrov wrote:
> How do I see (a) all variants the port provides, (b) the variants the
> port is installed with?  Then, how do I change (b) by selecting other
> variants from (a)?

(a) port variants <portname>
(b) port installed <portname>
(c) sudo port -f uninstall <portname> ;
sudo port install <portname> +variant1 +variant2 ...

> Is it possible to add +x11 to gtk things compiled as +no_x11 without
> forcing those things of using quartz to use x11, selectively?

That would depend on the individual port, but it seems in general that
it is not.

- Josh

From jmr at macports.org  Wed Dec 10 10:32:38 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 05:32:38 +1100
Subject: Install or use problem: no .profile created
In-Reply-To: <B7F3937F-648C-4F9F-B739-26F871BA23FF@ginko.de>
References: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>	<4D604997-E9E0-4924-8C36-08C6A051C7D6@ginko.de>	<493FE660.3050103@macports.org>
	<B7F3937F-648C-4F9F-B739-26F871BA23FF@ginko.de>
Message-ID: <49400B46.2030509@macports.org>

Joachim Oosnaabryg wrote:
> Am 10.12.2008 um 16:55 schrieb Joshua Root:
>> true that no single version of MacPorts/DarwinPorts will install in all
>> of the places given in the uninstall instructions.
> 
> OK, but neither =>/Applications/DarwinPorts \
> nor             =>/Applications/MacPorts \
> are there (I forgot to mention that in the last message)!

/Applications/MacPorts will appear when you install a port that provides
a .app, which will be installed there.

> To give full information, ls -a in /Library/Tcl/macports1.0 gives:
> 
> .                           macports_autoconf.tcl       macports_util.tcl
> ..                             macports_dlist.tcl               
> pkgIndex.tcl
> MacPorts.dylib          macports_fastload.tcl
> macports.tcl              macports_index.tcl
> 
> Together not more than 192 kB,
> and the MacPorts-1.6.0-10.4-Tiger.dmg in my download directory has 580
> kB, the installer package MacPorts-1.6.0-10.4-Tiger.dmg therein 620 kB,
> and it's content is:
> 
> .               Archive.bom     Info.plist      Resources
> ..              Archive.pax.gz  PkgInfo

The rest is installed in /opt/local.

> But I didn't find any file ?.profile? on my HD..

That's a bug in the 1.6 installer:
<http://trac.macports.org/wiki/ProblemHotlist#a.profilenotsetup>

- Josh

From asato at cae1.aero.org  Wed Dec 10 10:43:21 2008
From: asato at cae1.aero.org (Max Asato)
Date: Wed, 10 Dec 2008 10:43:21 -0800
Subject: Distfiles mirror behind proxy
In-Reply-To: <B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
References: <20081210004857.GB16414@cae1.aero.org>
	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
Message-ID: <20081210184321.GA25989@cae1.aero.org>

On Wed, Dec 10, 2008 at 08:59:55AM +0100, Anders F Bj?rklund wrote:
> 
> If you run MacPorts in debugging mode (port -d), you should get
> some output telling you what happened to the unarchive phase...
> But when you enable portarchivemode=yes, it is supposed to try
> "unarchive" (binary) before doing the "destroot" (source build)
> 
> --anders

I tried forcing a binary install with the -b option at Josh's suggestion 
but that still didn't work.  Here's a test for a glib2 archive that
I copied over from another Mac/Intel system.

imac2$ ls -l /opt/local/var/macports/packages/darwin/i386/glib2*
-rw-r--r--   1 root  admin  3629276 Dec  8 13:18 /opt/local/var/macports/packages/darwin/i386/glib2-2.18.3_0+darwin_8.i386.tgz

imac2$ sudo port -b install glib2
Error: Target org.macports.unarchive returned: Archive for glib2 2.18.3_0 not found, required when binary-only is set!
Error: Status 1 encountered during processing.

Is there any other package metadata that gets referenced before MacPorts
looks at the archive directory?  I'll try the -d option to get more
diagnostic info tonight.

-Max

From jmr at macports.org  Wed Dec 10 10:49:49 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 05:49:49 +1100
Subject: Distfiles mirror behind proxy
In-Reply-To: <20081210184321.GA25989@cae1.aero.org>
References: <20081210004857.GB16414@cae1.aero.org>	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
	<20081210184321.GA25989@cae1.aero.org>
Message-ID: <49400F4D.7090805@macports.org>

Max Asato wrote:
> On Wed, Dec 10, 2008 at 08:59:55AM +0100, Anders F Bj?rklund wrote:
>> If you run MacPorts in debugging mode (port -d), you should get
>> some output telling you what happened to the unarchive phase...
>> But when you enable portarchivemode=yes, it is supposed to try
>> "unarchive" (binary) before doing the "destroot" (source build)
>>
>> --anders
> 
> I tried forcing a binary install with the -b option at Josh's suggestion 
> but that still didn't work.  Here's a test for a glib2 archive that
> I copied over from another Mac/Intel system.
> 
> imac2$ ls -l /opt/local/var/macports/packages/darwin/i386/glib2*
> -rw-r--r--   1 root  admin  3629276 Dec  8 13:18 /opt/local/var/macports/packages/darwin/i386/glib2-2.18.3_0+darwin_8.i386.tgz
> 
> imac2$ sudo port -b install glib2
> Error: Target org.macports.unarchive returned: Archive for glib2 2.18.3_0 not found, required when binary-only is set!
> Error: Status 1 encountered during processing.
> 
> Is there any other package metadata that gets referenced before MacPorts
> looks at the archive directory?  I'll try the -d option to get more
> diagnostic info tonight.

Do you have the same portarchivetype set on both systems?

- Josh

From asato at cae1.aero.org  Wed Dec 10 12:01:26 2008
From: asato at cae1.aero.org (Max Asato)
Date: Wed, 10 Dec 2008 12:01:26 -0800
Subject: Distfiles mirror behind proxy
In-Reply-To: <49400F4D.7090805@macports.org>
References: <20081210004857.GB16414@cae1.aero.org>
	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
	<20081210184321.GA25989@cae1.aero.org>
	<49400F4D.7090805@macports.org>
Message-ID: <20081210200126.GA26429@cae1.aero.org>

On Thu, Dec 11, 2008 at 05:49:49AM +1100, Joshua Root wrote:
> 
> Do you have the same portarchivetype set on both systems?
> 
> - Josh

I'll have to verify but I think it is the same.  One install was done 
from source and the other using the .dmg packaged installer but I would 
expect the default portarchivetype to be the same.

-Max

From s.wiggins at bristol.ac.uk  Wed Dec 10 12:12:45 2008
From: s.wiggins at bristol.ac.uk (Stephen Wiggins)
Date: Wed, 10 Dec 2008 20:12:45 +0000
Subject: Follow on to earlier installation question--now trying to install jam
Message-ID: <4A840816-FA54-4C00-AFEC-32CBBA286830@bristol.ac.uk>

Thanks to everyone that answered my earlier question

>> My installation failed with the following message:
>>
>> The following install step failed: run postflight script for
>> MacPorts-1.6.0. Contact the software manufacturer for assistance.
>>
>>
>>
>> I would be grateful for any help.


A colleague gave me a simpler solution. He said he had the same  
problem, and it was because we were behind a firewall. He installed it  
from home with no problem. The same worked for me.


Now my main motivation  was to install jam.

However, on following the instructions for installation below.

I find that there are no directories /portslocation/dports/jam


I am new at this, but I am clearly missing something. The implication  
from the  web page is that those directories should be there. Should I  
just create them and proceed?

Thanks,
Steve


Once Darwin Ports has been installed, in a terminal window and while  
online, type the following and hit return:




%  cd /opt/local/bin/portslocation/dports/jam
%  sudo port install jam
Password:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081210/4e1edc06/attachment.html>

From dluke at geeklair.net  Wed Dec 10 12:20:38 2008
From: dluke at geeklair.net (Daniel J. Luke)
Date: Wed, 10 Dec 2008 15:20:38 -0500
Subject: Follow on to earlier installation question--now trying to install
	jam
In-Reply-To: <4A840816-FA54-4C00-AFEC-32CBBA286830@bristol.ac.uk>
References: <4A840816-FA54-4C00-AFEC-32CBBA286830@bristol.ac.uk>
Message-ID: <FA806990-0B05-4309-9857-611CAA055E68@geeklair.net>

On Dec 10, 2008, at 3:12 PM, Stephen Wiggins wrote:
> Once Darwin Ports has been installed, in a terminal window and while  
> online, type the following and hit return:
> % cd /opt/local/bin/portslocation/dports/jam
>
> %  sudo port install jam
> Password:

These instructions appear to come from the website that must not be  
named (its existence is one of the reasons why the name was changed to  
MacPorts).

You probably need to run

sudo port selfupdate

followed by

sudo port install jam

Although if your firewall blocks your connection to the MacPorts rsync  
server, this will not work, and you'll need to refer to our FAQ:

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

--
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/20081210/94fcb84e/attachment.bin>

From jmr at macports.org  Wed Dec 10 12:40:20 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 07:40:20 +1100
Subject: Follow on to earlier installation question--now trying to install
	jam
In-Reply-To: <4A840816-FA54-4C00-AFEC-32CBBA286830@bristol.ac.uk>
References: <4A840816-FA54-4C00-AFEC-32CBBA286830@bristol.ac.uk>
Message-ID: <49402934.70507@macports.org>

Stephen Wiggins wrote:
> Once Darwin Ports has been installed, in a terminal window and while
> online, type the following and hit return:
> 
> 
> 
> %  cd /opt/local/bin/portslocation/dports/jam
> %  sudo port install jam  
> Password:

Where did these instructions come from? The DarwinPorts project changed
its name to MacPorts many years ago now. The MacPorts home page is
<http://www.macports.org/>. Beware of any site claiming to be DarwinPorts.

Our installation and basic usage guides are here:
<http://trac.macports.org/wiki/InstallingMacPorts>
<http://trac.macports.org/wiki/UsingMacPortsQuickStart>

- Josh

From face at CentosPrime.COM  Wed Dec 10 12:57:36 2008
From: face at CentosPrime.COM (Chris Janton)
Date: Wed, 10 Dec 2008 13:57:36 -0700
Subject: libxml2 woes (PHP5 and friends)
Message-ID: <02208C59-5C29-4C05-B36B-3A3841C8CFD7@centosprime.com>

I am a heavy user of Wordpress. Especially using the xmlrpc functions  
(blog photos from Flickr, "external" blog editors, etc.)

In the past few months this has become a large problem. Entities get  
stripped from the text, so no links, HTML formatting etc.

The apparent culprit is libxml2 post version 2.6.31

No resolution from the PHP folks - see the discussion at

	http://bugs.php.net/bug.php?id=45996

No resolution from the Wordpress folks - see the discussion at

	http://trac.wordpress.org/ticket/7771

There's no simple fix, but apparently workarounds in some of the Linux  
communities by forcing PHP to use expat libraries as opposed to the  
libxml2 libraries. I don't understand the pointers to the fix, which  
mostly appear to be changes to PHP configuration that look like this

	-enable-xml=shared,%{_prefix} --with-expat-dir=%{_prefix}
	--with-xmlrpc=shared,%{_prefix} --with-expat-dir=%{_prefix}

but I don't see the difference between those and what is in the PHP  
configuration on macports that looks like

	 --with-libxml-dir=${prefix} \
	 --with-gettext=${prefix} \
	 --with-xml \
	 --with-expat-dir=${prefix} \
	 --with-xmlrpc \

unless there is some special magic because the expat directory is  
included on the same line as the --with-xmlrpc

I could just hack the PHP portfile to try the workaround, but I don't  
know what the "shared" means, or the repetitive declaration of --with- 
expat-dir

Or, I could just brute force the libxml2 port back to version 2.6.31

Anyone out there want to weigh in on the problem? Assure me that  
trying the hacked PHP portfile might not hurt?

Thanks.

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



From jmr at macports.org  Wed Dec 10 13:47:36 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 08:47:36 +1100
Subject: Follow on to earlier installation question--now trying to install
	jam
In-Reply-To: <DAF9FFC7-2902-4ECC-838F-6C32A4B87DC0@bristol.ac.uk>
References: <4A840816-FA54-4C00-AFEC-32CBBA286830@bristol.ac.uk>
	<49402934.70507@macports.org>
	<3A92FB65-CF35-4537-BDE7-808F5191432B@bristol.ac.uk>
	<49402D17.50404@macports.org>
	<DAF9FFC7-2902-4ECC-838F-6C32A4B87DC0@bristol.ac.uk>
Message-ID: <494038F8.4060209@macports.org>

Stephen Wiggins wrote:
> Thanks this is very helpful.
> 
> But I still have problems after a "successful installation". For example:
> 
> Typing 
> 
> sudo port -v selfupdate
> 
> gives
> 
> 
> stephen-wigginss-macbook:~ Steve$ sudo port -v selfupdate
> Password:
> sudo: port: command not found

Didn't I address this earlier today? Anyhow, here's the link again:
<http://trac.macports.org/wiki/ProblemHotlist#a.profilenotsetup>

- Josh

From mark at dxradio.demon.co.uk  Wed Dec 10 14:03:42 2008
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Wed, 10 Dec 2008 22:03:42 +0000
Subject: Follow on to earlier installation question--now trying to install
	jam
In-Reply-To: <FA806990-0B05-4309-9857-611CAA055E68@geeklair.net>
References: <4A840816-FA54-4C00-AFEC-32CBBA286830@bristol.ac.uk>
	<FA806990-0B05-4309-9857-611CAA055E68@geeklair.net>
Message-ID: <3EA9189B-7501-4D9B-85AA-E6F9CAB12FF4@dxradio.demon.co.uk>


On 10 Dec 2008, at 20:20, Daniel J. Luke wrote:

> On Dec 10, 2008, at 3:12 PM, Stephen Wiggins wrote:
>> Once Darwin Ports has been installed, in a terminal window and  
>> while online, type the following and hit return:
>> % cd /opt/local/bin/portslocation/dports/jam
>>
>> %  sudo port install jam
>> Password:
>
> These instructions appear to come from the website that must not be  
> named (its existence is one of the reasons why the name was changed  
> to MacPorts).
>
> You probably need to run
>
> sudo port selfupdate
>
> followed by
>
> sudo port install jam
>
> Although if your firewall blocks your connection to the MacPorts  
> rsync server, this will not work, and you'll need to refer to our FAQ:
>
> http://trac.macports.org/wiki/FAQ#WhatdoIdoifportselfupdatedoesntworkortheRsyncserverrefusesconnections
>
> --
> Daniel J. Luke


But *many* software sites link to the "nameless" site for instructions  
& method on how to install their software on MacOSX rather than  
linking to MacPorts.

Mark

From jmr at macports.org  Wed Dec 10 14:13:39 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 09:13:39 +1100
Subject: Follow on to earlier installation question--now trying to install
	jam
In-Reply-To: <3EA9189B-7501-4D9B-85AA-E6F9CAB12FF4@dxradio.demon.co.uk>
References: <4A840816-FA54-4C00-AFEC-32CBBA286830@bristol.ac.uk>	<FA806990-0B05-4309-9857-611CAA055E68@geeklair.net>
	<3EA9189B-7501-4D9B-85AA-E6F9CAB12FF4@dxradio.demon.co.uk>
Message-ID: <49403F13.4020809@macports.org>

Mark Hattam wrote:
> 
> On 10 Dec 2008, at 20:20, Daniel J. Luke wrote:
> 
>> On Dec 10, 2008, at 3:12 PM, Stephen Wiggins wrote:
>>> Once Darwin Ports has been installed, in a terminal window and while
>>> online, type the following and hit return:
>>> % cd /opt/local/bin/portslocation/dports/jam
>>>
>>> %  sudo port install jam
>>> Password:
>>
>> These instructions appear to come from the website that must not be
>> named (its existence is one of the reasons why the name was changed to
>> MacPorts).
>>
>> You probably need to run
>>
>> sudo port selfupdate
>>
>> followed by
>>
>> sudo port install jam
>>
>> Although if your firewall blocks your connection to the MacPorts rsync
>> server, this will not work, and you'll need to refer to our FAQ:
>>
>> http://trac.macports.org/wiki/FAQ#WhatdoIdoifportselfupdatedoesntworkortheRsyncserverrefusesconnections
>>
>>
>> -- 
>> Daniel J. Luke
> 
> 
> But *many* software sites link to the "nameless" site for instructions &
> method on how to install their software on MacOSX rather than linking to
> MacPorts.

When I see a site that does that, I ask its owner to correct it. If
everyone does the same, maybe we can reduce our dear leech's influence.

- Josh

From mark at dxradio.demon.co.uk  Wed Dec 10 14:24:14 2008
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Wed, 10 Dec 2008 22:24:14 +0000
Subject: Follow on to earlier installation question--now trying to install
	jam
In-Reply-To: <49403F13.4020809@macports.org>
References: <4A840816-FA54-4C00-AFEC-32CBBA286830@bristol.ac.uk>	<FA806990-0B05-4309-9857-611CAA055E68@geeklair.net>
	<3EA9189B-7501-4D9B-85AA-E6F9CAB12FF4@dxradio.demon.co.uk>
	<49403F13.4020809@macports.org>
Message-ID: <416BD36B-B6C6-42C9-A9EA-C687A1C0C865@dxradio.demon.co.uk>


On 10 Dec 2008, at 22:13, Joshua Root wrote:

> Mark Hattam wrote:
>>
>> On 10 Dec 2008, at 20:20, Daniel J. Luke wrote:
>>
>>> On Dec 10, 2008, at 3:12 PM, Stephen Wiggins wrote:
>>>> Once Darwin Ports has been installed, in a terminal window and  
>>>> while
>>>> online, type the following and hit return:
>>>> % cd /opt/local/bin/portslocation/dports/jam
>>>>
>>>> %  sudo port install jam
>>>> Password:
>>>
>>> These instructions appear to come from the website that must not be
>>> named (its existence is one of the reasons why the name was  
>>> changed to
>>> MacPorts).
>>>
>>> You probably need to run
>>>
>>> sudo port selfupdate
>>>
>>> followed by
>>>
>>> sudo port install jam
>>>
>>> Although if your firewall blocks your connection to the MacPorts  
>>> rsync
>>> server, this will not work, and you'll need to refer to our FAQ:
>>>
>>> http://trac.macports.org/wiki/FAQ#WhatdoIdoifportselfupdatedoesntworkortheRsyncserverrefusesconnections
>>>
>>>
>>> -- 
>>> Daniel J. Luke
>>
>>
>> But *many* software sites link to the "nameless" site for  
>> instructions &
>> method on how to install their software on MacOSX rather than  
>> linking to
>> MacPorts.
>
> When I see a site that does that, I ask its owner to correct it. If
> everyone does the same, maybe we can reduce our dear leech's  
> influence.
>
> - Josh

But it doesn't help the cause when Macports.org *still* doesn't work  
in IE7 on a PC. Granted that useful software authors will probably not  
contaminate their machines with IE7, but it is a great "put off" to  
normal folk.

Mark

From raimue at macports.org  Wed Dec 10 14:25:45 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Wed, 10 Dec 2008 23:25:45 +0100
Subject: Configure error? vim wouldn't build without linking x11
In-Reply-To: <7a665ffc0812100845q3f3daea5xe40142ca5d326b1a@mail.gmail.com>
References: <7a665ffc0812100845q3f3daea5xe40142ca5d326b1a@mail.gmail.com>
Message-ID: <494041E9.1040103@macports.org>

Joel Thibault (MacPorts) wrote:
> It appears that either configure is not detecting my system properly
> or vim depends on X and is not looking for it.
> 
> When I tried to upgrade vim, the linker kept failing with this error.
> /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols:
> __Xsetlocale
> 
> Adding -lX11 to the linker command line enabled it to build and now I
> have the new vim.
>
> Maybe there should be a no_x11 variant, too?

vim should not require X11 with the default variants, as the Portfile
explicitely configures using --without-x. Only if you chose one of the
GUI variants +athena, +gtk2, +gtk1, +motif it will require X11.

> OS X Tiger 10.4.11
> Macports Trunk
> 
> I saved the output from port -d upgrade -cuv vim, but I didn't want to
> paste 1452 lines :)  Would any of that be useful?
> Joel

Might be helpful to see why X11 support was enabled although it is
disabled. Could you also provide config.log from the work directory?
Best would be to open a ticket in Trac[1] and attach it there.

Rainer

[1] http://guide.macports.org/#project.tickets

From blb at macports.org  Wed Dec 10 14:27:20 2008
From: blb at macports.org (Bryan Blackburn)
Date: Wed, 10 Dec 2008 15:27:20 -0700
Subject: Configure error? vim wouldn't build without linking x11
In-Reply-To: <7a665ffc0812100845q3f3daea5xe40142ca5d326b1a@mail.gmail.com>
References: <7a665ffc0812100845q3f3daea5xe40142ca5d326b1a@mail.gmail.com>
Message-ID: <20081210222720.GG487@ninagal.withay.com>

On Wed, Dec 10, 2008 at 11:45:59AM -0500, Joel Thibault (MacPorts) said:
> It appears that either configure is not detecting my system properly
> or vim depends on X and is not looking for it.
> 
> When I tried to upgrade vim, the linker kept failing with this error.
> /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols:
> __Xsetlocale
> 
> Adding -lX11 to the linker command line enabled it to build and now I
> have the new vim.
> 
> Maybe there should be a no_x11 variant, too?

With what variants did you install vim?  Use 'port installed vim' to see;
there are several variants which enable various toolkits based on X11, but
the default should be to ignore any X11 at all.  'port variants vim' will
list which add a graphical interface and all of those do enable X11 use.

Bryan


> 
> OS X Tiger 10.4.11
> Macports Trunk
> 
> I saved the output from port -d upgrade -cuv vim, but I didn't want to
> paste 1452 lines :)  Would any of that be useful?
> Joel
> 
> 
> -- 
> Joel Thibault [AIM: Jole Tebo]
> Software Engineer in Boston

From osna at ginko.de  Wed Dec 10 14:22:09 2008
From: osna at ginko.de (Joachim Oosnaabryg)
Date: Wed, 10 Dec 2008 23:22:09 +0100
Subject: Install or use problem: no .profile created
In-Reply-To: <49400B46.2030509@macports.org>
References: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>	<4D604997-E9E0-4924-8C36-08C6A051C7D6@ginko.de>	<493FE660.3050103@macports.org>
	<B7F3937F-648C-4F9F-B739-26F871BA23FF@ginko.de>
	<49400B46.2030509@macports.org>
Message-ID: <0974822B-1F8B-43EE-9C06-D659D21F7558@ginko.de>

Am 10.12.2008 um 19:32 schrieb Joshua Root:
> That's a bug in the 1.6 installer:
> <http://trac.macports.org/wiki/ProblemHotlist#a.profilenotsetup>

Great, Joshua, that's it. Without your kindly help I hadn't found  
that page!

Hardly understandable, that the macports-creator let the new  
(installing) user unknowing of the bug and the fixing script (I lost  
a day with trial and error without success).
It should be made clear at the install-page: http://www.macports.org/ 
install.php
but what is written there dosn't let you suspect that there is e  
fundamental bug:

"This procedure will place a fully-functional and default MacPorts  
installation on your host system, ready for usage. If needed your  
shell configuration files will be adapted by the installer to include  
the necessary settings to run MacPorts and the programs it installs,  
but you may need to open a new shell for these changes to take effect."

Or at least as a warning at
http://guide.macports.org/#installing.shell

But however, with the command:

curl -O http://svn.macports.org/repository/macports/branches/ 
release_1_6/base/portmgr/dmg/postflight && bash postflight

all went well.

So the problem of installation of MacPorts seems to be resolved. I  
continued with:

sudo port install rtf2latex2e

which went logtime well, but finished with:

--->  Configuring rtf2latex2e
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_tex_rtf 
2latex2e/work/rtf2latex2eUnix-1.0fc1/Unix" && ./configure --prefix=/ 
opt/local " returned error 1
Command output: creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install
checking whether build environment is sane... yes
...- still more "yes" and "found", but then:

checking host system type... ./config.guess: line 1017: syntax error:  
unexpected end of file
configure: error: can not guess host type; you must specify one

Error: Status 1 encountered during processing.

I'm not fit to read from this wether the problem lies in the  
rtf2latex2e port, or in the MacPort configuration.

If someone has a knowing/guess/hint about it, please tell me, what  
you would do after this error message, please!

Goutgaun! joachim
--
MacTeXLive 2008 - TeXShop 2.18-svn - LyX 1.6
MacBook Pro OSX 10.4.11 Tiger

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081210/0e1e1ad7/attachment.html>

From blb at macports.org  Wed Dec 10 14:34:47 2008
From: blb at macports.org (Bryan Blackburn)
Date: Wed, 10 Dec 2008 15:34:47 -0700
Subject: Distfiles mirror behind proxy
In-Reply-To: <20081210184321.GA25989@cae1.aero.org>
References: <20081210004857.GB16414@cae1.aero.org>
	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
	<20081210184321.GA25989@cae1.aero.org>
Message-ID: <20081210223447.GH487@ninagal.withay.com>

On Wed, Dec 10, 2008 at 10:43:21AM -0800, Max Asato said:
> On Wed, Dec 10, 2008 at 08:59:55AM +0100, Anders F Bj?rklund wrote:
> > 
> > If you run MacPorts in debugging mode (port -d), you should get
> > some output telling you what happened to the unarchive phase...
> > But when you enable portarchivemode=yes, it is supposed to try
> > "unarchive" (binary) before doing the "destroot" (source build)
> > 
> > --anders
> 
> I tried forcing a binary install with the -b option at Josh's suggestion 
> but that still didn't work.  Here's a test for a glib2 archive that
> I copied over from another Mac/Intel system.
> 
> imac2$ ls -l /opt/local/var/macports/packages/darwin/i386/glib2*
> -rw-r--r--   1 root  admin  3629276 Dec  8 13:18 /opt/local/var/macports/packages/darwin/i386/glib2-2.18.3_0+darwin_8.i386.tgz
> 
> imac2$ sudo port -b install glib2
> Error: Target org.macports.unarchive returned: Archive for glib2 2.18.3_0 not found, required when binary-only is set!
> Error: Status 1 encountered during processing.

Just to make sure, this system is running Mac OS X 10.4.x (darwin_8) and is
Intel-based (i386) right?

Bryan


> 
> Is there any other package metadata that gets referenced before MacPorts
> looks at the archive directory?  I'll try the -d option to get more
> diagnostic info tonight.
> 
> -Max

From blb at macports.org  Wed Dec 10 14:49:27 2008
From: blb at macports.org (Bryan Blackburn)
Date: Wed, 10 Dec 2008 15:49:27 -0700
Subject: Install or use problem: no .profile created
In-Reply-To: <0974822B-1F8B-43EE-9C06-D659D21F7558@ginko.de>
References: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>
	<4D604997-E9E0-4924-8C36-08C6A051C7D6@ginko.de>
	<493FE660.3050103@macports.org>
	<B7F3937F-648C-4F9F-B739-26F871BA23FF@ginko.de>
	<49400B46.2030509@macports.org>
	<0974822B-1F8B-43EE-9C06-D659D21F7558@ginko.de>
Message-ID: <20081210224927.GI487@ninagal.withay.com>

On Wed, Dec 10, 2008 at 11:22:09PM +0100, Joachim Oosnaabryg said:
[...]
> So the problem of installation of MacPorts seems to be resolved. I  
> continued with:
>
> sudo port install rtf2latex2e
>
> which went logtime well, but finished with:
>
> --->  Configuring rtf2latex2e
[...]
> checking host system type... ./config.guess: line 1017: syntax error:  
> unexpected end of file
> configure: error: can not guess host type; you must specify one
>
> Error: Status 1 encountered during processing.
>
> I'm not fit to read from this wether the problem lies in the rtf2latex2e 
> port, or in the MacPort configuration.

Looks like rtf2latex2e's configure script can't handle proper detection on a
Mac normally, so a PowerPC fix was put in there; unfortunately, there wasn't
one for Intel, so I just added one in r43442.  At least 30 minutes after
I've written this email, do a 'sudo port sync' and 'sudo port clean --work
rtf2latex2e' then try installing it again.

Bryan


>
> If someone has a knowing/guess/hint about it, please tell me, what you 
> would do after this error message, please!
>
> Goutgaun! joachim
> --
> MacTeXLive 2008 - TeXShop 2.18-svn - LyX 1.6
> MacBook Pro OSX 10.4.11 Tiger
>

From pgijnxn02 at sneakemail.com  Wed Dec 10 14:51:03 2008
From: pgijnxn02 at sneakemail.com (Joel Thibault (MacPorts))
Date: Wed, 10 Dec 2008 17:51:03 -0500
Subject: Configure error? vim wouldn't build without linking x11
In-Reply-To: <20081210222720.GG487@ninagal.withay.com>
References: <7a665ffc0812100845q3f3daea5xe40142ca5d326b1a@mail.gmail.com>
	<20081210222720.GG487@ninagal.withay.com>
Message-ID: <7a665ffc0812101451u5195b69epb26030a096cf5d5b@mail.gmail.com>

On Wed, Dec 10, 2008 at 5:27 PM, Bryan Blackburn blb-at-macports.org wrote:
> On Wed, Dec 10, 2008 at 11:45:59AM -0500, Joel Thibault (MacPorts) said:
>> It appears that either configure is not detecting my system properly
>> or vim depends on X and is not looking for it.
>>
>> When I tried to upgrade vim, the linker kept failing with this error.
>> /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols:
>> __Xsetlocale
>>
>> Adding -lX11 to the linker command line enabled it to build and now I
>> have the new vim.
>>
>> Maybe there should be a no_x11 variant, too?
>
> With what variants did you install vim?  Use 'port installed vim' to see;
> there are several variants which enable various toolkits based on X11, but
> the default should be to ignore any X11 at all.  'port variants vim' will
> list which add a graphical interface and all of those do enable X11 use.

Right, I didn't think I had added any variants so I didn't know why it
needed X11, but I wasn't sure how to find out which variant I actually
had.  Thanks for the "installed" tip.

$ port installed vim
The following ports are currently installed:
  vim @7.2.065_0 (active)

That means the default variant, right?

Joel




-- 
Joel Thibault [AIM: Jole Tebo]
Software Engineer in Boston

From pgijnxn02 at sneakemail.com  Wed Dec 10 15:00:15 2008
From: pgijnxn02 at sneakemail.com (Joel Thibault (MacPorts))
Date: Wed, 10 Dec 2008 18:00:15 -0500
Subject: Configure error? vim wouldn't build without linking x11
In-Reply-To: <494041E9.1040103@macports.org>
References: <7a665ffc0812100845q3f3daea5xe40142ca5d326b1a@mail.gmail.com>
	<494041E9.1040103@macports.org>
Message-ID: <7a665ffc0812101500k170cdb32k8230baee3fdc3e1e@mail.gmail.com>

On Wed, Dec 10, 2008 at 5:25 PM, Rainer M?ller raimue-at-macports.org
|MacPorts| <5m2vjqstp00t at sneakemail.com> wrote:
> Joel Thibault (MacPorts) wrote:
>> It appears that either configure is not detecting my system properly
>> or vim depends on X and is not looking for it.
>>
>> When I tried to upgrade vim, the linker kept failing with this error.
>> /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols:
>> __Xsetlocale
>>
>> Adding -lX11 to the linker command line enabled it to build and now I
>> have the new vim.
>>
>> Maybe there should be a no_x11 variant, too?
>
> vim should not require X11 with the default variants, as the Portfile
> explicitely configures using --without-x. Only if you chose one of the
> GUI variants +athena, +gtk2, +gtk1, +motif it will require X11.
>
>> OS X Tiger 10.4.11
>> Macports Trunk
>>
>> I saved the output from port -d upgrade -cuv vim, but I didn't want to
>> paste 1452 lines :)  Would any of that be useful?
>> Joel
>
> Might be helpful to see why X11 support was enabled although it is
> disabled. Could you also provide config.log from the work directory?
> Best would be to open a ticket in Trac[1] and attach it there.
>
> Rainer
>
> [1] http://guide.macports.org/#project.tickets
>

https://trac.macports.org/ticket/17606


-- 
Joel Thibault [AIM: Jole Tebo]
Software Engineer in Boston

From wasamy at umich.edu  Wed Dec 10 15:11:45 2008
From: wasamy at umich.edu (Waheed Samy)
Date: Wed, 10 Dec 2008 18:11:45 -0500
Subject: problem installing rsync
Message-ID: <417CFEB5-7B28-4A2F-8BEE-898A6DB74A94@umich.edu>

I am getting an error installing rsync.  I would be grateful if you  
can provide assistance.  The following shows the output of the port  
command.  Before doing this I ran sudo port -v selfupdate, and found  
the package up to date.

MacBook:~ waheedsamy$ sudo port install rsync
Password:
--->  Configuring gperf
Error: Target org.macports.configure returned: configure failure:  
shell command " cd "/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_devel_gperf/work/gperf-3.0.3" && ./ 
configure --prefix=/opt/local --infodir=/opt/local/share/info "  
returned error 1
Command output: checking whether make sets $(MAKE)... no
configure: creating ./config.status
config.status: creating Makefile
=== configuring in lib (/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_devel_gperf/work/gperf-3.0.3/lib)
configure: running /bin/sh ./configure '--prefix=/opt/local'  '-- 
infodir=/opt/local/share/info' --cache-file=/dev/null --srcdir=.
checking whether make sets $(MAKE)... no
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.
configure: error: ./configure failed for lib

Error: The following dependencies failed to build: libiconv gperf popt  
gettext expat ncurses ncursesw
Error: Status 1 encountered during processing.
MacBook:~ waheedsamy$

Much obliged.
Waheed
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081210/74a282aa/attachment.html>

From jmr at macports.org  Wed Dec 10 15:17:01 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 10:17:01 +1100
Subject: problem installing rsync
In-Reply-To: <417CFEB5-7B28-4A2F-8BEE-898A6DB74A94@umich.edu>
References: <417CFEB5-7B28-4A2F-8BEE-898A6DB74A94@umich.edu>
Message-ID: <49404DED.6000000@macports.org>

Waheed Samy wrote:
> I am getting an error installing rsync.  I would be grateful if you can
> provide assistance.  The following shows the output of the port command.
>  Before doing this I ran sudo port -v selfupdate, and found the package
> up to date.
> 
> MacBook:~ waheedsamy$ sudo port install rsync
> Password:
> --->  Configuring gperf
> Error: Target org.macports.configure returned: configure failure: shell
> command " cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gperf/work/gperf-3.0.3"
> && ./configure --prefix=/opt/local --infodir=/opt/local/share/info "
> returned error 1
> Command output: checking whether make sets $(MAKE)... no
> configure: creating ./config.status
> config.status: creating Makefile
> === configuring in lib
> (/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gperf/work/gperf-3.0.3/lib)
> configure: running /bin/sh ./configure '--prefix=/opt/local'
>  '--infodir=/opt/local/share/info' --cache-file=/dev/null --srcdir=.
> checking whether make sets $(MAKE)... no
> 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.
> configure: error: ./configure failed for lib
> 
> Error: The following dependencies failed to build: libiconv gperf popt
> gettext expat ncurses ncursesw
> Error: Status 1 encountered during processing.
> MacBook:~ waheedsamy$ 

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

- Josh

From cjsvance at gmail.com  Wed Dec 10 17:08:32 2008
From: cjsvance at gmail.com (Christopher Vance)
Date: Thu, 11 Dec 2008 12:08:32 +1100
Subject: repeated rebuilding
In-Reply-To: <493EED73.6040106@macports.org>
References: <ace45c0a0812091410k738503e6t8aa5655a523c08fb@mail.gmail.com>
	<493EED73.6040106@macports.org>
Message-ID: <ace45c0a0812101708o2476ac29s3291cec405d4b168@mail.gmail.com>

On Wed, Dec 10, 2008 at 9:13 AM, Joshua Root <jmr at macports.org> wrote:
> Christopher Vance wrote:
>> When I do
>>    port upgrade outdated
>> some packages get rebuilt several times.
>>
>> Isn't port supposed to calculate and order transitive dependencies to stop this?
>
> No, but it is meant to not rebuild anything that isn't outdated. What
> you describe should not be possible unless you're using the -f option,
> which causes ports to rebuilt even if they don't appear to be outdated.

I had copied -f from a porticus run without understanding what it meant.

-- 
Christopher Vance

From ryandesign at macports.org  Wed Dec 10 18:14:17 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 10 Dec 2008 20:14:17 -0600
Subject: repeated rebuilding
In-Reply-To: <ace45c0a0812101708o2476ac29s3291cec405d4b168@mail.gmail.com>
References: <ace45c0a0812091410k738503e6t8aa5655a523c08fb@mail.gmail.com>
	<493EED73.6040106@macports.org>
	<ace45c0a0812101708o2476ac29s3291cec405d4b168@mail.gmail.com>
Message-ID: <B6723C29-5803-46DE-B148-B4E7F8D32EF5@macports.org>


On Dec 10, 2008, at 19:08, Christopher Vance wrote:

> On Wed, Dec 10, 2008 at 9:13 AM, Joshua Root <jmr at macports.org> wrote:
>> Christopher Vance wrote:
>>> When I do
>>>    port upgrade outdated
>>> some packages get rebuilt several times.
>>>
>>> Isn't port supposed to calculate and order transitive  
>>> dependencies to stop this?
>>
>> No, but it is meant to not rebuild anything that isn't outdated. What
>> you describe should not be possible unless you're using the -f  
>> option,
>> which causes ports to rebuilt even if they don't appear to be  
>> outdated.
>
> I had copied -f from a porticus run without understanding what it  
> meant.

Then that explains it. You basically never want to use "-f" with  
"port upgrade" unless you also use "-n". See:

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



From ryandesign at macports.org  Wed Dec 10 18:30:14 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 10 Dec 2008 20:30:14 -0600
Subject: Install or use problem: no .profile created
In-Reply-To: <0974822B-1F8B-43EE-9C06-D659D21F7558@ginko.de>
References: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>	<4D604997-E9E0-4924-8C36-08C6A051C7D6@ginko.de>	<493FE660.3050103@macports.org>
	<B7F3937F-648C-4F9F-B739-26F871BA23FF@ginko.de>
	<49400B46.2030509@macports.org>
	<0974822B-1F8B-43EE-9C06-D659D21F7558@ginko.de>
Message-ID: <F829F5D9-A6EE-4E9B-B667-F8E9E4ACC493@macports.org>

On Dec 10, 2008, at 16:22, Joachim Oosnaabryg wrote:

> Am 10.12.2008 um 19:32 schrieb Joshua Root:
>> That's a bug in the 1.6 installer:
>> <http://trac.macports.org/wiki/ProblemHotlist#a.profilenotsetup>
>
> Great, Joshua, that's it. Without your kindly help I hadn't found  
> that page!
>
> Hardly understandable, that the macports-creator let the new  
> (installing) user unknowing of the bug and the fixing script (I  
> lost a day with trial and error without success).

We apologize for this problem. It has gone unfixed for far too long.  
The fix will be in MacPorts 1.7.0. We have already made available  
1.7.0 release candidate 1, so hopefully we can release the final  
version of 1.7.0 very soon.


> It should be made clear at the install-page: http:// 
> www.macports.org/install.php
> but what is written there dosn't let you suspect that there is e  
> fundamental bug:
>
> "This procedure will place a fully-functional and default MacPorts  
> installation on your host system, ready for usage. If needed your  
> shell configuration files will be adapted by the installer to  
> include the necessary settings to run MacPorts and the programs it  
> installs, but you may need to open a new shell for these changes to  
> take effect."
>
> Or at least as a warning at
> http://guide.macports.org/#installing.shell
>
> But however, with the command:
>
> curl -O http://svn.macports.org/repository/macports/branches/ 
> release_1_6/base/portmgr/dmg/postflight && bash postflight
>
> all went well.
>
> So the problem of installation of MacPorts seems to be resolved. I  
> continued with:
>
> sudo port install rtf2latex2e
>
> which went logtime well, but finished with:
>
> --->  Configuring rtf2latex2e
> 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_tex_r 
> tf2latex2e/work/rtf2latex2eUnix-1.0fc1/Unix" && ./configure -- 
> prefix=/opt/local " returned error 1
> Command output: creating cache ./config.cache
> checking for a BSD compatible install... /usr/bin/install
> checking whether build environment is sane... yes
> ...- still more "yes" and "found", but then:
>
> checking host system type... ./config.guess: line 1017: syntax  
> error: unexpected end of file
> configure: error: can not guess host type; you must specify one
>
> Error: Status 1 encountered during processing.
>
> I'm not fit to read from this wether the problem lies in the  
> rtf2latex2e port, or in the MacPort configuration.
>
> If someone has a knowing/guess/hint about it, please tell me, what  
> you would do after this error message, please!
>
> Goutgaun! joachim
> --
> MacTeXLive 2008 - TeXShop 2.18-svn - LyX 1.6
> MacBook Pro OSX 10.4.11 Tiger

I can confirm that error on 10.4.11 Intel. We had two tickets filed  
for it too:

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

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

Bryan's fix seems to work for me so I'll note that in the tickets.


I also filed a ticket requesting rtf2latex2e be updated from 1.0fc1  
to 1.0fc2:

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


From ms at mac-specialist.com  Wed Dec 10 21:30:37 2008
From: ms at mac-specialist.com (Bill Hernandez)
Date: Wed, 10 Dec 2008 23:30:37 -0600
Subject: freetype - Status 1 encountered during processing
Message-ID: <93D784D7-96AB-4129-8BD6-EDAD24967B83@mac-specialist.com>

Support,

[2008.10.12](11:17PM) -> [roscoe] ~ $ sudo port install -v freetype
--->  Fetching freetype
--->  Attempting to fetch patch-detect.mk.diff from http://svn.macports.org/repository/macports/distfiles/freetype
--->  Attempting to fetch patch-detect.mk.diff from http://svn.macports.org/repository/macports/distfiles/general/
--->  Attempting to fetch patch-detect.mk.diff from http://svn.macports.org/repository/macports/downloads/freetype
Error: Target org.macports.fetch returned: fetch failed
Error: Status 1 encountered during processing.
[2008.10.12](11:17PM) -> [roscoe] ~ $


I tried PortAuthority and got this :
--->  Fetching freetype
--->  patch-detect.mk.diff doesn't seem to exist in /opt/local/var/ 
macports/distfiles/freetype
--->  Attempting to fetch patch-detect.mk.diff from http://svn.macports.org/repository/macports/distfiles/freetype
--->  Attempting to fetch patch-detect.mk.diff from http://svn.macports.org/repository/macports/distfiles/general/
--->  Attempting to fetch patch-detect.mk.diff from http://svn.macports.org/repository/macports/downloads/freetype
Warning: the following items did not execute (for freetype):  
org.macports.activate org.macports.fetch org.macports.extract  
org.macports.checksum org.macports.patch org.macports.configure  
org.macports.build org.macports.destroot org.macports.install

Any ideas ?

Bill Hernandez
Plano, Texas

From jmr at macports.org  Wed Dec 10 21:52:21 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 11 Dec 2008 16:52:21 +1100
Subject: freetype - Status 1 encountered during processing
In-Reply-To: <93D784D7-96AB-4129-8BD6-EDAD24967B83@mac-specialist.com>
References: <93D784D7-96AB-4129-8BD6-EDAD24967B83@mac-specialist.com>
Message-ID: <4940AA95.7030401@macports.org>

Bill Hernandez wrote:
> Support,
> 
> [2008.10.12](11:17PM) -> [roscoe] ~ $ sudo port install -v freetype
> --->  Fetching freetype
> --->  Attempting to fetch patch-detect.mk.diff from
> http://svn.macports.org/repository/macports/distfiles/freetype
> --->  Attempting to fetch patch-detect.mk.diff from
> http://svn.macports.org/repository/macports/distfiles/general/
> --->  Attempting to fetch patch-detect.mk.diff from
> http://svn.macports.org/repository/macports/downloads/freetype
> Error: Target org.macports.fetch returned: fetch failed
> Error: Status 1 encountered during processing.
> [2008.10.12](11:17PM) -> [roscoe] ~ $

That patch file exists in the ports tree, so it shouldn't need to be
downloaded. Presumably you have somehow deleted it. A 'port sync' should
bring it back.

- Josh

From ryandesign at macports.org  Wed Dec 10 22:27:46 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 11 Dec 2008 00:27:46 -0600
Subject: freeciv and freeciv-x11 ggz problem
In-Reply-To: <61C85017-4CE1-4DE0-B547-BAFB78453AE1@bellsouth.net>
References: <61C85017-4CE1-4DE0-B547-BAFB78453AE1@bellsouth.net>
Message-ID: <90529E53-579B-49DF-B899-A3AB954CB650@macports.org>

On Dec 9, 2008, at 16:13, William Davis wrote:

> unable to install  freeciv-x11 or activate freeciv:
> macintosh:~ frstan$ sudo port install -d freeciv-x11
> Password:
> --->  Fetching freeciv-x11
> --->  Attempting to fetch freeciv-2.1.8.tar.bz2 from http://superb- 
> east.dl.sourceforge.net/freeciv
> --->  Verifying checksum(s) for freeciv-x11
> --->  Extracting freeciv-x11
> --->  Configuring freeciv-x11
> 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_games 
> _freeciv-x11/work/freeciv-2.1.8" && ./configure --prefix=/opt/local  
> --enable-client=gtk2 --with-readline --with-zlib --enable-nls -- 
> with-sdl-prefix=/opt/local --with-libiconv-prefix=/opt/local -- 
> mandir=/opt/local/share/man " returned error 1
> Command output: checking for C99 initializers... yes
> checking for stdint.h... (cached) yes
> checking for C99 stdint.h... yes
> checking for gzgets in -lz... yes
> checking zlib.h usability... yes
> checking zlib.h presence... yes
> checking for zlib.h... yes
> checking for gzip... /opt/local/bin/gzip
> checking for pkg-config... /opt/local/bin/pkg-config
> checking for GTK+ - version >= 2.4.0... yes (version 2.14.4)
> checking for X... libraries /usr/X11/lib, headers /usr/X11/include
> checking whether Xfuncproto was supplied... no, found:
> checking for sdl-config... /opt/local/bin/sdl-config
> checking for SDL - version >= 1.0.0... yes
> checking SDL/SDL_mixer.h usability... yes
> checking SDL/SDL_mixer.h presence... yes
> checking for SDL/SDL_mixer.h... yes
> checking for Mix_OpenAudio in -lSDL_mixer... yes
> checking building SDL_mixer support... yes
> checking for GGZ library: libggz... yes (libraries /opt/local/lib,  
> headers /opt/local/include)
> checking for GGZ library version: 0.0.14... yes
> checking for GGZ library: ggzmod... yes (libraries /opt/local/lib,  
> headers /opt/local/include)
> checking for GGZ configuration tool: ggz-config... /opt/local/bin/ 
> ggz-config
> checking for GGZ library: ggz-gtk... no
> configure: WARNING: no
>   The library 'ggz-gtk' does not seem to be installed correctly.
>   Headers searched in:  /opt/local/include /usr/local/include /usr/ 
> include
>   Libraries searched in:  /opt/local/lib /usr/local/lib /usr/local/ 
> lib64 /usr/lib /usr/lib64
>   Please read QuickStart.GGZ in order to fix this.
>
>
> Error: Status 1 encountered during processing.

My theories so far:

freeciv-x11 does not declare a dependency on libggz. However it looks  
like freeciv-x11 will use libggz if present. That's the first bug  
that needs to be fixed. Either freeciv-x11 must be changed to not use  
libggz even if present, or freeciv-x11 must declare a dependency on  
libggz.

Second, libggz appears to have been built without gtk support, and  
freeciv-x11 apparently does not work with libggz without gtk support.  
That's the second bug. Either libggz must declare a dependency on  
gtk2 so that it always builds with gtk support, or there needs to be  
a variant in the libggz port to enable gtk2 support. In the interest  
of fewer variant, I assume the former is preferable.


Your workaround for now would be to deactivate libggz, clean and  
install freeciv-x11, then reactivate libggz if desired.


> macintosh:~ frstan$ sudo port install -d freeciv
> Password:
> --->  Fetching freeciv
> Please note that this port conflicts with port:freeciv-x11.
> --->  Attempting to fetch freeciv-2.1.8.tar.bz2 from http:// 
> voxel.dl.sourceforge.net/freeciv
> --->  Verifying checksum(s) for freeciv
> --->  Extracting freeciv
> --->  Configuring freeciv
> --->  Building freeciv
> --->  Staging freeciv into destroot
> --->  Installing freeciv @2.1.8_0
> --->  Activating freeciv @2.1.8_0
> Error: Target org.macports.activate returned: Image error: /opt/ 
> local/etc/ggz.modules is being used by the active gnome-games  
> port.  Please deactivate this port first, or use the -f flag to  
> force the activation.
> Error: Status 1 encountered during processing.

Third bug: It sounds like the freeciv (when built while the libggz  
port is active) and gnome-games ports conflict. It will need to be  
decided which of these two ports, if any, should be the true owner of  
${prefix}/etc/ggz.modules.



From ryandesign at macports.org  Wed Dec 10 22:31:11 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 11 Dec 2008 00:31:11 -0600
Subject: kdebase3 and libXdamage
In-Reply-To: <ace45c0a0812091530j6d761837m3b62141176596e99@mail.gmail.com>
References: <ace45c0a0812091530j6d761837m3b62141176596e99@mail.gmail.com>
Message-ID: <5F4A5F5B-6602-433F-B82C-DC5F8AE9945F@macports.org>


On Dec 9, 2008, at 17:30, Christopher Vance wrote:

> Building kdebase3 fails on an up to date Leopard machine because
> libXdamage is at 1.0.0, but kdebase3 wants 1.1.0.

That's this ticket:

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




From ryandesign at macports.org  Thu Dec 11 01:30:34 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 11 Dec 2008 03:30:34 -0600
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <493E74D1.8030708@shopwatch.org>
References: <493D82AF.5080203@shopwatch.org>
	<20081208214114.GF506@ninagal.withay.com>
	<493E74D1.8030708@shopwatch.org>
Message-ID: <C5BBEE60-4E06-472D-AD20-56012AC8D1F2@macports.org>


On Dec 9, 2008, at 07:38, Jay Levitt wrote:

> Does MacPorts log any history anywhere?  I don't think it does.

Nope, MacPorts writes no logfiles.


From ryandesign at macports.org  Thu Dec 11 01:32:31 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 11 Dec 2008 03:32:31 -0600
Subject: 1.7.0 beta & rc1: libcurl errors
In-Reply-To: <493E70BB.9030108@shopwatch.org>
References: <493D82AF.5080203@shopwatch.org>	<20081208214114.GF506@ninagal.withay.com>	<1C33C3D0-1791-4DFB-BD43-3FCEEA0C5B49@macports.org>	<20081208224200.GL506@ninagal.withay.com>
	<493DA7E3.1060209@macports.org> <493E70BB.9030108@shopwatch.org>
Message-ID: <03AF7EE1-5838-4448-9BEA-C3F3B23CB695@macports.org>


On Dec 9, 2008, at 07:20, Jay Levitt wrote:

> Joshua Root wrote:
>
>> Could the wrong libcurl be picked up if there is something like
>> LDFLAGS=-L/opt/local/lib in the environment? If that's what  
>> happened to
>> Jay, it shouldn't be a problem with selfupdate because the  
>> environment
>> is sanitised.
>
> I do, in fact, have that:
>
> CPATH=/opt/local/include
> CPPFLAGS=-I/opt/local/include
> LDFLAGS=-L/opt/local/lib
> LIBTOOLIZE=/opt/local/bin/glibtoolize
> PATH=/usr/local/bin:/usr/local/sbin:/Users/jay/bin:/opt/local/bin:/ 
> opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin:/ 
> Applications/Utilities/diglloyd/disktester:/usr/local/git/bin:/opt/ 
> local/lib/postgresql83/bin


Stuff in /usr/local can and does conflict with MacPorts-installed  
software. Perhaps you have a different version of curl in there. See  
what happens if you rename /usr/local to e.g. /usr/local-off.




From randall.h.wood at alexandriasoftware.com  Thu Dec 11 02:10:08 2008
From: randall.h.wood at alexandriasoftware.com (Randall Wood)
Date: Thu, 11 Dec 2008 05:10:08 -0500
Subject: freeciv and freeciv-x11 ggz problem
In-Reply-To: <90529E53-579B-49DF-B899-A3AB954CB650@macports.org>
References: <61C85017-4CE1-4DE0-B547-BAFB78453AE1@bellsouth.net>
	<90529E53-579B-49DF-B899-A3AB954CB650@macports.org>
Message-ID: <3C94F956-4A66-46EB-83D0-5B0ACFB415A2@alexandriasoftware.com>

I was not aware of the libggz dependency when I did the upgrade. There  
is a ggz client for gtk, but its not in the macports tree. I'm looking  
into this.


On 11 Dec 2008, at 01:27, Ryan Schmidt wrote:

> On Dec 9, 2008, at 16:13, William Davis wrote:
>
>> unable to install  freeciv-x11 or activate freeciv:
>> macintosh:~ frstan$ sudo port install -d freeciv-x11
>> Password:
>> --->  Fetching freeciv-x11
>> --->  Attempting to fetch freeciv-2.1.8.tar.bz2 from http://superb-east.dl.sourceforge.net/freeciv
>> --->  Verifying checksum(s) for freeciv-x11
>> --->  Extracting freeciv-x11
>> --->  Configuring freeciv-x11
>> 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_games_freeciv-x11/work/freeciv-2.1.8"  
>> && ./configure --prefix=/opt/local --enable-client=gtk2 --with- 
>> readline --with-zlib --enable-nls --with-sdl-prefix=/opt/local -- 
>> with-libiconv-prefix=/opt/local --mandir=/opt/local/share/man "  
>> returned error 1
>> Command output: checking for C99 initializers... yes
>> checking for stdint.h... (cached) yes
>> checking for C99 stdint.h... yes
>> checking for gzgets in -lz... yes
>> checking zlib.h usability... yes
>> checking zlib.h presence... yes
>> checking for zlib.h... yes
>> checking for gzip... /opt/local/bin/gzip
>> checking for pkg-config... /opt/local/bin/pkg-config
>> checking for GTK+ - version >= 2.4.0... yes (version 2.14.4)
>> checking for X... libraries /usr/X11/lib, headers /usr/X11/include
>> checking whether Xfuncproto was supplied... no, found:
>> checking for sdl-config... /opt/local/bin/sdl-config
>> checking for SDL - version >= 1.0.0... yes
>> checking SDL/SDL_mixer.h usability... yes
>> checking SDL/SDL_mixer.h presence... yes
>> checking for SDL/SDL_mixer.h... yes
>> checking for Mix_OpenAudio in -lSDL_mixer... yes
>> checking building SDL_mixer support... yes
>> checking for GGZ library: libggz... yes (libraries /opt/local/lib,  
>> headers /opt/local/include)
>> checking for GGZ library version: 0.0.14... yes
>> checking for GGZ library: ggzmod... yes (libraries /opt/local/lib,  
>> headers /opt/local/include)
>> checking for GGZ configuration tool: ggz-config... /opt/local/bin/ 
>> ggz-config
>> checking for GGZ library: ggz-gtk... no
>> configure: WARNING: no
>>  The library 'ggz-gtk' does not seem to be installed correctly.
>>  Headers searched in:  /opt/local/include /usr/local/include /usr/ 
>> include
>>  Libraries searched in:  /opt/local/lib /usr/local/lib /usr/local/ 
>> lib64 /usr/lib /usr/lib64
>>  Please read QuickStart.GGZ in order to fix this.
>>
>>
>> Error: Status 1 encountered during processing.
>
> My theories so far:
>
> freeciv-x11 does not declare a dependency on libggz. However it  
> looks like freeciv-x11 will use libggz if present. That's the first  
> bug that needs to be fixed. Either freeciv-x11 must be changed to  
> not use libggz even if present, or freeciv-x11 must declare a  
> dependency on libggz.
>
> Second, libggz appears to have been built without gtk support, and  
> freeciv-x11 apparently does not work with libggz without gtk  
> support. That's the second bug. Either libggz must declare a  
> dependency on gtk2 so that it always builds with gtk support, or  
> there needs to be a variant in the libggz port to enable gtk2  
> support. In the interest of fewer variant, I assume the former is  
> preferable.
>
>
> Your workaround for now would be to deactivate libggz, clean and  
> install freeciv-x11, then reactivate libggz if desired.
>
>
>> macintosh:~ frstan$ sudo port install -d freeciv
>> Password:
>> --->  Fetching freeciv
>> Please note that this port conflicts with port:freeciv-x11.
>> --->  Attempting to fetch freeciv-2.1.8.tar.bz2 from http://voxel.dl.sourceforge.net/freeciv
>> --->  Verifying checksum(s) for freeciv
>> --->  Extracting freeciv
>> --->  Configuring freeciv
>> --->  Building freeciv
>> --->  Staging freeciv into destroot
>> --->  Installing freeciv @2.1.8_0
>> --->  Activating freeciv @2.1.8_0
>> Error: Target org.macports.activate returned: Image error: /opt/ 
>> local/etc/ggz.modules is being used by the active gnome-games  
>> port.  Please deactivate this port first, or use the -f flag to  
>> force the activation.
>> Error: Status 1 encountered during processing.
>
> Third bug: It sounds like the freeciv (when built while the libggz  
> port is active) and gnome-games ports conflict. It will need to be  
> decided which of these two ports, if any, should be the true owner  
> of ${prefix}/etc/ggz.modules.
>
>


From ryandesign at macports.org  Thu Dec 11 02:41:42 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 11 Dec 2008 04:41:42 -0600
Subject: libxml2 woes (PHP5 and friends)
In-Reply-To: <02208C59-5C29-4C05-B36B-3A3841C8CFD7@centosprime.com>
References: <02208C59-5C29-4C05-B36B-3A3841C8CFD7@centosprime.com>
Message-ID: <DBDDE28C-BD43-4F23-92D7-1EEADEA2F118@macports.org>

On Dec 10, 2008, at 14:57, Chris Janton wrote:

> I am a heavy user of Wordpress. Especially using the xmlrpc  
> functions (blog photos from Flickr, "external" blog editors, etc.)
>
> In the past few months this has become a large problem. Entities  
> get stripped from the text, so no links, HTML formatting etc.
>
> The apparent culprit is libxml2 post version 2.6.31
>
> No resolution from the PHP folks - see the discussion at
>
> 	http://bugs.php.net/bug.php?id=45996
>
> No resolution from the Wordpress folks - see the discussion at
>
> 	http://trac.wordpress.org/ticket/7771
>
> There's no simple fix, but apparently workarounds in some of the  
> Linux communities by forcing PHP to use expat libraries as opposed  
> to the libxml2 libraries. I don't understand the pointers to the  
> fix, which mostly appear to be changes to PHP configuration that  
> look like this
>
> 	-enable-xml=shared,%{_prefix} --with-expat-dir=%{_prefix}
> 	--with-xmlrpc=shared,%{_prefix} --with-expat-dir=%{_prefix}
>
> but I don't see the difference between those and what is in the PHP  
> configuration on macports that looks like
>
> 	 --with-libxml-dir=${prefix} \
> 	 --with-gettext=${prefix} \
> 	 --with-xml \
> 	 --with-expat-dir=${prefix} \
> 	 --with-xmlrpc \
>
> unless there is some special magic because the expat directory is  
> included on the same line as the --with-xmlrpc
>
> I could just hack the PHP portfile to try the workaround, but I  
> don't know what the "shared" means, or the repetitive declaration  
> of --with-expat-dir
>
> Or, I could just brute force the libxml2 port back to version 2.6.31
>
> Anyone out there want to weigh in on the problem? Assure me that  
> trying the hacked PHP portfile might not hurt?

Ok, I've spent some time on this problem now. I can reproduce it with  
both php5 @5.2.8_0 and php5-devel @5.3.0alpha3_1.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: simple.php
Type: text/php
Size: 360 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081211/5be09927/attachment.bin>
-------------- next part --------------


As I understand it, this is a PHP bug because they're bypassing the  
libxml API and using internal libxml structures they were never  
supposed to be accessing. When libxml changed those internal  
structures in libxml 2.7.x, this PHP feature stopped working. So the  
PHP team needs to fix their code.

We could try to work around the problem in MacPorts in the meantime.  
The workaround Mandriva is using seems to be to force the xml  
extension specifically (ext/xml) to use expat instead of libxml,  
while keeping the rest of the extensions using libxml (since expat  
support in PHP is said to be deprecated, according to "./configure -- 
help").

http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/updates/2009.0/ 
php/current/SPECS/php.spec?r1=278891&r2=281822

http://svn.mandriva.com/svn/packages/cooker/php/current/SOURCES/php- 
xml_expat_fix.diff

php5 already declares dependencies on and links with both expat and  
libxml. I made a quick attempt at making ext/xml use expat only, but  
failed. We may need what you showed above: we may need to instruct  
PHP to build ext/xml shared (instead of, presumably, statically) so  
that we can use different libraries when linking ext/xml than we do  
for the others. I will try this later. (Building the xml extension  
shared is not part of the fix that Mandriva uses; they were already  
building xml shared before. But building xml shared may turn out to  
be necessary for the fix that they did employ.)

In fact, maybe we should be building all the extensions shared  
instead of statically. I will have to look into that too.

The "shared" flag is explained in "./configure --help":

Extensions:

   --with-EXTENSION=[shared[,PATH]]

     NOTE: Not all extensions can be build as 'shared'.

     Example: --with-foobar=shared,/usr/local/foobar/

       o Builds the foobar extension as shared extension.
       o foobar package install prefix is /usr/local/foobar/


To answer your question, the order of configure arguments should not  
matter, for standard autoconf configure scripts, and repetition of  
configure arguments should also be irrelevant (though if the values  
differ, I'm not sure whether the first or last one wins).


From osna at ginko.de  Thu Dec 11 03:21:42 2008
From: osna at ginko.de (Joachim Oosnaabryg)
Date: Thu, 11 Dec 2008 12:21:42 +0100
Subject: Install or use problem: no .profile created
In-Reply-To: <20081210224927.GI487@ninagal.withay.com>
References: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>
	<4D604997-E9E0-4924-8C36-08C6A051C7D6@ginko.de>
	<493FE660.3050103@macports.org>
	<B7F3937F-648C-4F9F-B739-26F871BA23FF@ginko.de>
	<49400B46.2030509@macports.org>
	<0974822B-1F8B-43EE-9C06-D659D21F7558@ginko.de>
	<20081210224927.GI487@ninagal.withay.com>
Message-ID: <8CAB0BB1-C673-4BF6-AAFC-AB1D6DFDA8B4@ginko.de>


Resolved !! both
- the installation problem of MacPorts 1.6 and
- the bug in rtf2latex2e on Intel.

Am 10.12.2008 um 23:49 schrieb Bryan Blackburn:
> Looks like rtf2latex2e's configure script can't handle proper  
> detection on a
> Mac normally, so a PowerPC fix was put in there; unfortunately,  
> there wasn't
> one for Intel, so I just added one in r43442.  At least 30 minutes  
> after
> I've written this email, do a 'sudo port sync' and 'sudo port clean  
> --work
> rtf2latex2e' then try installing it again.

Thank you, Bryan for your quick fixing action! rtf2latex2e is now  
working an my MacBook, both from command line as within LyX!

@Ryan Schmidt: OK, I appreciate the effort. But at my advice the bug  
in the MacPorts.dmg/pgk 1.6

> should be made clear at the install-page: http://www.macports.org/ 
> install.php

> Or at least as a warning at
> http://guide.macports.org/#installing.shell

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

to prevent people like mi to make useless trials :-(

Goutgaun! joachim
--
MacTeXLive 2008 - TeXShop 2.18-svn - LyX 1.6
MacBook Pro OSX 10.4.11 Tiger




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081211/776634ef/attachment.html>

From jwdavison at me.com  Thu Dec 11 08:53:24 2008
From: jwdavison at me.com (joseph davison)
Date: Thu, 11 Dec 2008 10:53:24 -0600
Subject: install manopen fails on 10.5.5
In-Reply-To: <F5C30EAA-4DAD-4126-BB96-B06A0A2F2EB9@me.com>
References: <3F9717BA-6AE3-4DFD-8CD4-DBC7F07EA6D3@me.com>
	<F5C30EAA-4DAD-4126-BB96-B06A0A2F2EB9@me.com>
Message-ID: <39E6501F-DD68-48BB-883D-BC6D27E8D938@me.com>

AHA!

     The problem is that there's a check to see if this is panther or  
earlier, and if it is, it creates an NSSimpleHorizontalTypesetter.    
I  put an ifdef around it with an undefined value and it compiles fine  
and works.


I don't know what the right way to do that fix is, but that's what the  
problem is -- perhaps the maintainer can Do The Right Thing?

That should probably be a bug report, eh?

joe


On Dec 9, 2008, at 6:19 PM, joseph davison wrote:

> Oh I See...
>
>   NSSimpleHorizontalTypeSetter was deprecated in 10.4 -- I suppose  
> it's gone in 10.5, eh?    Joy -- I'll see if I can find an example  
> or replacing it, but if the maintainer already knows how...
>
> joe
>
>
> On Dec 8, 2008, at 6:19 PM, joseph davison wrote:
>
>> Just installed macports on a new leopard installation on my macbook  
>> pro.
>>
>> Tried to install manopen and it blows up with:
>> ManDocument.m: In function '-[ManDocument  
>> windowControllerDidLoadNib:]':
>> ManDocument.m:328: error: 'NSSimpleHorizontalTypesetter' undeclared  
>> (first use in this function)
>> ManDocument.m:328: error: (Each undeclared identifier is reported  
>> only once
>> ManDocument.m:328: error: for each function it appears in.)
>>
>> and then some warnings.
>>
>> Presuming it useful, here's the whole output from port -v install  
>> macports
>>
>> --->  Fetching ManOpen
>> --->  Verifying checksum(s) for ManOpen
>> --->  Checksumming ManOpen-2.5.1.s.tar.gz
>> --->  Extracting ManOpen
>> --->  Extracting ManOpen-2.5.1.s.tar.gz
>> --->  Configuring ManOpen
>> --->  Building ManOpen with target all
>> == Making all for i386 in ManOpen openman.tproj ==
>> == Making ManOpen for i386 ==
>> Pre-build setup...
>> /bin/rm -f /opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/derived_src/TrustedPrecomps.txt
>> ......in cat2html
>> ......in cat2rtf
>> Building...
>> ......in cat2html
>> /usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/ 
>> var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/PrivateHeaders/ -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/Headers/ -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/derived_src/ManOpen/cat2html.tproj -I. -pipe        - 
>> I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ 
>> ManOpen-2.5.1          -c -o /opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/objects-optimized/ManOpen/cat2html.tproj/ 
>> cat2html.i386.o cat2html.c
>> cat2html.l: In function 'cat2htmllex':
>> cat2html.l:304: warning: pointer targets in passing argument 1 of  
>> 'decodeUTF8' differ in signedness
>> cat2html.l:311: warning: pointer targets in passing argument 1 of  
>> 'decodeUTF8' differ in signedness
>> /usr/bin/cc -o /opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.app/Resources/cat2html   -L/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/objects-optimized/ManOpen/cat2html.tproj        -F/ 
>> opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1 -L/opt/ 
>> local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1       - 
>> arch i386  /opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/objects-optimized/ManOpen/cat2html.tproj/ 
>> cat2html.o       -framework Foundation
>> ......in cat2rtf
>> /usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/ 
>> var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/PrivateHeaders/ -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/Headers/ -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/derived_src/ManOpen/cat2rtf.tproj -I. -pipe        -I/ 
>> opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ 
>> ManOpen-2.5.1          -c -o /opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/objects-optimized/ManOpen/cat2rtf.tproj/ 
>> cat2rtf.i386.o cat2rtf.c
>> cat2rtf.l: In function 'cat2rtflex':
>> cat2rtf.l:344: warning: pointer targets in passing argument 1 of  
>> 'decodeUTF8' differ in signedness
>> cat2rtf.l:351: warning: pointer targets in passing argument 1 of  
>> 'decodeUTF8' differ in signedness
>> /usr/bin/cc -o /opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.app/Resources/cat2rtf   -L/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/objects-optimized/ManOpen/cat2rtf.tproj        -F/opt/ 
>> local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1 -L/opt/ 
>> local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1       - 
>> arch i386  /opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/objects-optimized/ManOpen/cat2rtf.tproj/cat2rtf.o
>> /usr/lib/mergeInfo PB.project CustomInfo.plist /opt/local/var/ 
>> macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/derived_src/ManOpen/Java.plist -o /opt/local/var/ 
>> macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.app/Resources/Info-macos.plist
>> -n
>> Copying English resources...
>> Copied ManOpen.nib PrefPanel.nib DocController.nib ManOpen- 
>> macintosh.nib Apropos.nib ManOpen-macos.nib ManPage.nib  
>> FindPanel.nib Credits.rtf InfoPlist.strings
>> Copied LinkCursor.tiff ManOpen-nextstep.tiff ManOpen.tiff  
>> ManOpen.icns ManOpen.scriptSuite ManOpen.scriptTerminology
>> /usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/ 
>> var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.app/PrivateHeaders -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/derived_src/ManOpen -I. -pipe        -I/opt/local/var/ 
>> macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1      - 
>> ObjC       -c -o /opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/objects-optimized/ManOpen/AproposDocument.i386.o  
>> AproposDocument.m
>> /usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/ 
>> var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.app/PrivateHeaders -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/derived_src/ManOpen -I. -pipe        -I/opt/local/var/ 
>> macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1      - 
>> ObjC       -c -o /opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/objects-optimized/ManOpen/FindPanelController.i386.o  
>> FindPanelController.m
>> /usr/bin/cc -arch i386 -Os  -Wmost  -g  -fno-common -I/opt/local/ 
>> var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/ProjectHeaders -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.app/PrivateHeaders -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/derived_src/ManOpen -I. -pipe        -I/opt/local/var/ 
>> macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/Headers -I/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/PrivateHeaders -F/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1      - 
>> ObjC       -c -o /opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/objects-optimized/ManOpen/ManDocument.i386.o  
>> ManDocument.m
>> ManDocument.m: In function '-[ManDocument  
>> windowControllerDidLoadNib:]':
>> ManDocument.m:328: error: 'NSSimpleHorizontalTypesetter' undeclared  
>> (first use in this function)
>> ManDocument.m:328: error: (Each undeclared identifier is reported  
>> only once
>> ManDocument.m:328: error: for each function it appears in.)
>> ManDocument.m: In function '-[ManTextView drawPageBorderWithSize:]':
>> ManDocument.m:634: warning: 'widthOfString:' is deprecated  
>> (declared at /System/Library/Frameworks/AppKit.framework/Headers/ 
>> NSFont.h:216)
>> ManDocument.m:644: warning: 'cString' is deprecated (declared at / 
>> System/Library/Frameworks/Foundation.framework/Headers/NSString.h: 
>> 345)
>> ManDocument.m:645: warning: 'cString' is deprecated (declared at / 
>> System/Library/Frameworks/Foundation.framework/Headers/NSString.h: 
>> 345)
>> ManDocument.m:645: warning: 'cStringLength' is deprecated (declared  
>> at /System/Library/Frameworks/Foundation.framework/Headers/ 
>> NSString.h:347)
>> make[1]: *** [/opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync 
>> .macports.org_release_ports_aqua_ManOpen/work/ManOpen-2.5.1/ 
>> ManOpen.build/objects-optimized/ManOpen/ManDocument.i386.o] Error 1
>> make: *** [all at ManOpen] Error 2
>> Warning: the following items did not execute (for ManOpen):  
>> org.macports.activate org.macports.build org.macports.destroot  
>> org.macports.install
>>
>> _______________________________________________
>> 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 asato at cae1.aero.org  Thu Dec 11 09:41:00 2008
From: asato at cae1.aero.org (Max Asato)
Date: Thu, 11 Dec 2008 09:41:00 -0800
Subject: Distfiles mirror behind proxy
In-Reply-To: <49400F4D.7090805@macports.org>
References: <20081210004857.GB16414@cae1.aero.org>
	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
	<20081210184321.GA25989@cae1.aero.org>
	<49400F4D.7090805@macports.org>
Message-ID: <20081211174100.GA7446@cae1.aero.org>

This thread got a bit fragmented so I'll restate this particular problem.
Sorry about the length of this posting.

I had created a binary archive on one system and copied the archive
to another system in the hopes that I could install the binaries
directly and avoid a second build.  This would demonstrate the
feasibility of accelerating Port installations for users on our network
by providing a shared repository for prebuilt archives.

It turns out that I either just happened to pick an odd package for my
initial testing or there are architectural differences between a
PowerMac (2x dual-core Xeon) and an iMac (Core 2 Duo) that the glib2 port 
cares about.

I built glib2 originally on a PowerMac running 10.4.11.

   abk239$ port installed glib2
   The following ports are currently installed:
     glib2 @2.18.3_0+darwin_8 (active)

   abk239$ port variants glib2
   glib2 has the variants:
           universal
           puredarwin
           darwin
           powerpc
           darwin_6
           darwin_7
           darwin_8
           darwin_9

   abk239$ ls -l /opt/local/var/macports/packages/darwin/i386/glib2*
   -rw-r--r--   1 root  admin  3629276 Dec  8 13:18 /opt/local/var/macports/packages/darwin/i386/glib2-2.18.3_0+darwin_8.i386.tgz
   
I then tried to install that binary on an iMac running 10.4.11 (which 
doesn't seem to support the darwin_8 variant).  This failed even when that 
variant was requested.

   imac2$ ls -l /opt/local/var/macports/packages/darwin/i386/glib2*
   -rw-r--r--   1 root  admin  3629276 Dec  8 13:18 /opt/local/var/macports/packages/darwin/i386/glib2-2.18.3_0+darwin_8.i386.tgz

   imac2$ port variants glib2
   glib2 has the variants:
           universal
           puredarwin
           darwin
           powerpc
           darwin_6
           darwin_9

   imac2$ sudo port -bd install glib2 +darwin_8
   DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/glib2
   DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/glib2
   DEBUG: Requested variant darwin_8 is not provided by port glib2.
   DEBUG: Requested variant i386 is not provided by port glib2.
   DEBUG: Requested variant macosx is not provided by port glib2.
   DEBUG: Executing variant darwin provides darwin
   DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext
   DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext
   DEBUG: Requested variant darwin_8 is not provided by port gettext.
   DEBUG: Requested variant darwin is not provided by port gettext.
   DEBUG: Requested variant i386 is not provided by port gettext.
   DEBUG: Requested variant macosx is not provided by port gettext.
   DEBUG: Searching for dependency: gettext
   DEBUG: Found Dependency: receipt exists for gettext
   DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv
   DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv
   DEBUG: Requested variant darwin is not provided by port libiconv.
   DEBUG: Requested variant i386 is not provided by port libiconv.
   DEBUG: Requested variant macosx is not provided by port libiconv.
   DEBUG: Executing variant darwin_8 provides darwin_8
   DEBUG: Searching for dependency: libiconv
   DEBUG: Found Dependency: receipt exists for libiconv
   DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pkgconfig
   DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pkgconfig
   DEBUG: Requested variant darwin_8 is not provided by port pkgconfig.
   DEBUG: Requested variant darwin is not provided by port pkgconfig.
   DEBUG: Requested variant i386 is not provided by port pkgconfig.
   DEBUG: Requested variant macosx is not provided by port pkgconfig.
   DEBUG: Searching for dependency: pkgconfig
   DEBUG: Found Dependency: receipt exists for pkgconfig
   DEBUG: Skipping completed org.macports.main (glib2)
   DEBUG: No TGZ archive: /opt/local/var/macports/packages/darwin/i386/glib2-2.18.3_0.i386.tgz
   Error: Target org.macports.unarchive returned: Archive for glib2 2.18.3_0 not found, required when binary-only is set!


So it looks like MacPorts is searching for an archive and would have used
it if the port and variant had matched.  So the jury is still out on 
whether it is worth the effort of creating a mechanism for sharing
prebuilt binaries among our users.

Thanks to all of those who responded.

-Max


From jmr at macports.org  Thu Dec 11 10:25:59 2008
From: jmr at macports.org (Joshua Root)
Date: Fri, 12 Dec 2008 05:25:59 +1100
Subject: Distfiles mirror behind proxy
In-Reply-To: <20081211174100.GA7446@cae1.aero.org>
References: <20081210004857.GB16414@cae1.aero.org>
	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
	<20081210184321.GA25989@cae1.aero.org>
	<49400F4D.7090805@macports.org>
	<20081211174100.GA7446@cae1.aero.org>
Message-ID: <49415B37.3080000@macports.org>

Max Asato wrote:
>    abk239$ port variants glib2
>    glib2 has the variants:
>            universal
>            puredarwin
>            darwin
>            powerpc
>            darwin_6
>            darwin_7
>            darwin_8
>            darwin_9

>    imac2$ port variants glib2
>    glib2 has the variants:
>            universal
>            puredarwin
>            darwin
>            powerpc
>            darwin_6
>            darwin_9

Looks like you don't have the same Portfile on both machines. Have you
synced them both lately? What does 'port info glib2' say on each? I
suspect you'll find that they have a different version/revision.

- Josh

From afb at macports.org  Thu Dec 11 10:33:55 2008
From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=)
Date: Thu, 11 Dec 2008 19:33:55 +0100
Subject: Distfiles mirror behind proxy
In-Reply-To: <20081211174100.GA7446@cae1.aero.org>
References: <20081210004857.GB16414@cae1.aero.org>
	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
	<20081210184321.GA25989@cae1.aero.org>
	<49400F4D.7090805@macports.org>
	<20081211174100.GA7446@cae1.aero.org>
Message-ID: <9CF46291-A870-4E81-A368-93A1F40FF75F@macports.org>

Max Asato wrote:

> This thread got a bit fragmented so I'll restate this particular  
> problem.
> Sorry about the length of this posting.
>
> I had created a binary archive on one system and copied the archive
> to another system in the hopes that I could install the binaries
> directly and avoid a second build.  This would demonstrate the
> feasibility of accelerating Port installations for users on our  
> network
> by providing a shared repository for prebuilt archives.
>
> It turns out that I either just happened to pick an odd package for my
> initial testing or there are architectural differences between a
> PowerMac (2x dual-core Xeon) and an iMac (Core 2 Duo) that the  
> glib2 port
> cares about.

Seems that you got unlucky, yes.

> I built glib2 originally on a PowerMac running 10.4.11.
>
...
>    abk239$ ls -l /opt/local/var/macports/packages/darwin/i386/glib2*
>    -rw-r--r--   1 root  admin  3629276 Dec  8 13:18 /opt/local/var/ 
> macports/packages/darwin/i386/glib2-2.18.3_0+darwin_8.i386.tgz
>
> I then tried to install that binary on an iMac running 10.4.11 (which
> doesn't seem to support the darwin_8 variant).  This failed even  
> when that
> variant was requested.
...
>    DEBUG: No TGZ archive: /opt/local/var/macports/packages/darwin/ 
> i386/glib2-2.18.3_0.i386.tgz
>    Error: Target org.macports.unarchive returned: Archive for glib2  
> 2.18.3_0 not found, required when binary-only is set!
>
>
> So it looks like MacPorts is searching for an archive and would  
> have used
> it if the port and variant had matched.  So the jury is still out on
> whether it is worth the effort of creating a mechanism for sharing
> prebuilt binaries among our users.

This sounds like a bug to me. Presumably the default variants
should have matched, between "archive" and "unarchive"...

+darwin_8 isn't even a real variant but a platform variant,
and it should match between 10.4.11 and 10.4.11 you'd think ?


Can't seem to reproduce it, though. Trying the same gets me a:
DEBUG: No TGZ archive: /opt/local/var/macports/packages/darwin/i386/ 
glib2-2.18.3_0+darwin_8.i386.tgz

So it must be something else that causes +darwin_8 to disappear
on your iMac installation. It is supposed to predefined for you.

--anders


From ryandesign at macports.org  Thu Dec 11 22:05:16 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 12 Dec 2008 00:05:16 -0600
Subject: Distfiles mirror behind proxy
In-Reply-To: <49415B37.3080000@macports.org>
References: <20081210004857.GB16414@cae1.aero.org>
	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
	<20081210184321.GA25989@cae1.aero.org>
	<49400F4D.7090805@macports.org>
	<20081211174100.GA7446@cae1.aero.org>
	<49415B37.3080000@macports.org>
Message-ID: <359241CF-00A1-42EB-98C9-58ADEA0A9568@macports.org>


On Dec 11, 2008, at 12:25, Joshua Root wrote:

> Max Asato wrote:
>
>>    abk239$ port variants glib2
>>    glib2 has the variants:
>>            universal
>>            puredarwin
>>            darwin
>>            powerpc
>>            darwin_6
>>            darwin_7
>>            darwin_8
>>            darwin_9
>
>>    imac2$ port variants glib2
>>    glib2 has the variants:
>>            universal
>>            puredarwin
>>            darwin
>>            powerpc
>>            darwin_6
>>            darwin_9
>
> Looks like you don't have the same Portfile on both machines. Have you
> synced them both lately? What does 'port info glib2' say on each? I
> suspect you'll find that they have a different version/revision.

I added the darwin_8 (and darwin_7) sections to the glib2 Portfile in  
r42796 on November 30, 2008, because without them, the port would not  
compile on MacPorts 1.6.0. I had not noticed this before because I  
usually run MacPorts from trunk. I did not increase the version or  
revision of the port because either the port had already built  
successfully for you (because you were running MacPorts from trunk;  
no need to force you to rebuild) or else the port did not build for  
you (because you were running MacPorts 1.6.0; after this change, now  
it will build for you).

So as Joshua said, you need to "sudo port sync" on both machines to  
get the same ports trees.


From ryandesign at macports.org  Thu Dec 11 22:09:41 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 12 Dec 2008 00:09:41 -0600
Subject: Install or use problem: no .profile created
In-Reply-To: <8CAB0BB1-C673-4BF6-AAFC-AB1D6DFDA8B4@ginko.de>
References: <C09A923A-B689-4EAE-A5DE-152CC71A5EC8@ginko.de>
	<4D604997-E9E0-4924-8C36-08C6A051C7D6@ginko.de>
	<493FE660.3050103@macports.org>
	<B7F3937F-648C-4F9F-B739-26F871BA23FF@ginko.de>
	<49400B46.2030509@macports.org>
	<0974822B-1F8B-43EE-9C06-D659D21F7558@ginko.de>
	<20081210224927.GI487@ninagal.withay.com>
	<8CAB0BB1-C673-4BF6-AAFC-AB1D6DFDA8B4@ginko.de>
Message-ID: <DA597336-4A7A-4E45-A691-0125D0741203@macports.org>

On Dec 11, 2008, at 05:21, Joachim Oosnaabryg wrote:

> @Ryan Schmidt: OK, I appreciate the effort. But at my advice the  
> bug in the MacPorts.dmg/pgk 1.6
> should be made clear at the install-page: http://www.macports.org/ 
> install.php
>
> Or at least as a warning at
> http://guide.macports.org/#installing.shell
>
> with a link to http://trac.macports.org/wiki/ 
> ProblemHotlist#a.profilenotsetup
>
> to prevent people like mi to make useless trials :-(

I would not be opposed to a link on the install pages pointing to the  
FAQ, ProblemHotlist and LeopardProblems wiki pages, advising people  
to check there before reporting problems. I would not want to point  
to specific issues from the install page though.

It would also be nice if we didn't have effectively three FAQ pages...


From ryandesign at macports.org  Thu Dec 11 22:11:24 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 12 Dec 2008 00:11:24 -0600
Subject: install manopen fails on 10.5.5
In-Reply-To: <39E6501F-DD68-48BB-883D-BC6D27E8D938@me.com>
References: <3F9717BA-6AE3-4DFD-8CD4-DBC7F07EA6D3@me.com>
	<F5C30EAA-4DAD-4126-BB96-B06A0A2F2EB9@me.com>
	<39E6501F-DD68-48BB-883D-BC6D27E8D938@me.com>
Message-ID: <56CA9230-9242-4000-9FDE-0B10B436AFEE@macports.org>


On Dec 11, 2008, at 10:53, joseph davison wrote:

>     The problem is that there's a check to see if this is panther  
> or earlier, and if it is, it creates an  
> NSSimpleHorizontalTypesetter.   I  put an ifdef around it with an  
> undefined value and it compiles fine and works.

So you're saying the software intends to only use  
NSSimpleHorizontalTypesetter on Panther or earlier, but for some  
reason the OS version check is failing and it's still using it on  
Leopard?


> I don't know what the right way to do that fix is, but that's what  
> the problem is -- perhaps the maintainer can Do The Right Thing?
>
> That should probably be a bug report, eh?

Yes, please do file an issue in the tracker.



From blb at macports.org  Thu Dec 11 22:41:03 2008
From: blb at macports.org (Bryan Blackburn)
Date: Thu, 11 Dec 2008 23:41:03 -0700
Subject: install manopen fails on 10.5.5
In-Reply-To: <56CA9230-9242-4000-9FDE-0B10B436AFEE@macports.org>
References: <3F9717BA-6AE3-4DFD-8CD4-DBC7F07EA6D3@me.com>
	<F5C30EAA-4DAD-4126-BB96-B06A0A2F2EB9@me.com>
	<39E6501F-DD68-48BB-883D-BC6D27E8D938@me.com>
	<56CA9230-9242-4000-9FDE-0B10B436AFEE@macports.org>
Message-ID: <20081212064103.GS507@ninagal.withay.com>

On Fri, Dec 12, 2008 at 12:11:24AM -0600, Ryan Schmidt said:
> On Dec 11, 2008, at 10:53, joseph davison wrote:
[...]
>
>> I don't know what the right way to do that fix is, but that's what the 
>> problem is -- perhaps the maintainer can Do The Right Thing?
>>
>> That should probably be a bug report, eh?
>
> Yes, please do file an issue in the tracker.

As I mentioned earlier [1] there is already a ticket [2] so just append the
info there.

Bryan

[1] - <http://lists.macosforge.org/pipermail/macports-users/2008-December/012753.html>
[2] - <http://trac.macports.org/ticket/13787>


From c.kiefer at sussex.ac.uk  Fri Dec 12 05:15:23 2008
From: c.kiefer at sussex.ac.uk (Chris Kiefer)
Date: Fri, 12 Dec 2008 13:15:23 +0000
Subject: error with new install
Message-ID: <8D273B62-893E-4C6D-BEDF-821E7EB65570@sussex.ac.uk>

Hi,

i've made a new installation of macports so I can install 'Glew', but  
im getting an error:

$sudo port install glew
--->  Verifying checksum(s) for glew
Error: Checksum (md5) mismatch for glew-1.5.1-src.tgz
Error: Checksum (sha1) mismatch for glew-1.5.1-src.tgz
Error: Checksum (rmd160) mismatch for glew-1.5.1-src.tgz
Error: Target org.macports.checksum returned: Unable to verify file  
checksums
Error: Status 1 encountered during processing.

I'm using the latest version of Leopard

any ideas how i can fix this?

thanks,

Chris

From face at CentosPrime.COM  Fri Dec 12 07:12:11 2008
From: face at CentosPrime.COM (Chris Janton)
Date: Fri, 12 Dec 2008 08:12:11 -0700
Subject: error upgrading PHP5 on Panther
Message-ID: <3F6ECE80-ECEF-480A-ACBE-97B5E94CF8F4@centosprime.com>

--->  Fetching php5
--->  Attempting to fetch php-5.2.8.tar.bz2 from http://www.php.net/distributions/
--->  Verifying checksum(s) for php5
--->  Extracting php5
--->  Applying patches to php5
--->  Configuring php5
--->  Building php5 with target all
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8" && make all "  
returned error 2
Command output: /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3624: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3628: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3637: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3641: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3642: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3642: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3644: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3646: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3650: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3652: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3653: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3654: warning: passing arg 2 of `zend_register_resource'  
makes pointer from integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c: In function `zif_odbc_tableprivileges':
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3664: error: invalid lvalue in assignment
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3687: error: parse error before ')' token
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3689: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3691: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3698: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3702: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3709: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3713: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3714: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3714: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3716: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3718: warning: passing arg 1 of `_efree' makes pointer from  
integer without a cast
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3722: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3724: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3725: error: invalid type argument of `->'
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_php5/work/php-5.2.8/ext/odbc/ 
php_odbc.c:3726: warning: passing arg 2 of `zend_register_resource'  
makes pointer from integer without a cast
make: *** [ext/odbc/php_odbc.lo] Error 1

Error: Unable to upgrade port: 1


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



From jmr at macports.org  Fri Dec 12 08:27:45 2008
From: jmr at macports.org (Joshua Root)
Date: Sat, 13 Dec 2008 03:27:45 +1100
Subject: error with new install
In-Reply-To: <8D273B62-893E-4C6D-BEDF-821E7EB65570@sussex.ac.uk>
References: <8D273B62-893E-4C6D-BEDF-821E7EB65570@sussex.ac.uk>
Message-ID: <49429101.3030609@macports.org>

Chris Kiefer wrote:
> Hi,
> 
> i've made a new installation of macports so I can install 'Glew', but im
> getting an error:
> 
> $sudo port install glew
> --->  Verifying checksum(s) for glew
> Error: Checksum (md5) mismatch for glew-1.5.1-src.tgz
> Error: Checksum (sha1) mismatch for glew-1.5.1-src.tgz
> Error: Checksum (rmd160) mismatch for glew-1.5.1-src.tgz
> Error: Target org.macports.checksum returned: Unable to verify file
> checksums
> Error: Status 1 encountered during processing.
> 
> I'm using the latest version of Leopard
> 
> any ideas how i can fix this?

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

The checksum matches here, so possibilities 1 and 4 from the FAQ seem
most likely.

- Josh

From watts at imem.cnr.it  Fri Dec 12 09:57:31 2008
From: watts at imem.cnr.it (Bernard Watts)
Date: Fri, 12 Dec 2008 18:57:31 +0100
Subject: connection errors when macports libs are used with Tiger X11 headers
Message-ID: <6157F2F4-E6BD-4DF6-9FC4-293078AC6F8E@imem.cnr.it>

I get a problem running gwyddion and chemtools as described in Ticket  
#17558 after upgrading gwyddion. It was alright till it upgraded with  
the latest version of xrender.
  I get:
fatal IO error 0 (Unknown error: 0) on X server ":0.0"
       after 9 requests (8 known processed) with 0 events remaining.


Bernard Watts

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

From jeremyhu at macports.org  Fri Dec 12 10:21:41 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Fri, 12 Dec 2008 10:21:41 -0800
Subject: connection errors when macports libs are used with Tiger X11
	headers
In-Reply-To: <6157F2F4-E6BD-4DF6-9FC4-293078AC6F8E@imem.cnr.it>
References: <6157F2F4-E6BD-4DF6-9FC4-293078AC6F8E@imem.cnr.it>
Message-ID: <DB5CB40C-1675-4347-8C16-9FBC859DC87C@macports.org>


I fixed a big chunk of this yesterday, so resync and:

sudo port -v -f uninstall xrender cairo pango gtk2
sudo port -v install gtk2

Does it work now?  If not, does 'gtk-demo' work?

On Dec 12, 2008, at 09:57, Bernard Watts wrote:

> I get a problem running gwyddion and chemtools as described in  
> Ticket #17558 after upgrading gwyddion. It was alright till it  
> upgraded with the latest version of xrender.
> I get:
> fatal IO error 0 (Unknown error: 0) on X server ":0.0"
>      after 9 requests (8 known processed) with 0 events remaining.
>
>
> Bernard Watts
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From ohce86 at kitcarson.net  Fri Dec 12 11:25:48 2008
From: ohce86 at kitcarson.net (Timothy Goins)
Date: Fri, 12 Dec 2008 12:25:48 -0700
Subject: 'sudo port upgrade vim' fails
Message-ID: <8C164EBA-4049-40BB-95AA-48AA100058B7@kitcarson.net>

I am in the process of 'upgrading' my outdated ports.  When I got to  
'vim' I discovered that 44 patches needed to be applied (7.2.021 to  
7.2.065).  However, when I ran 'sudo port upgrade vim' it spat out 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

The 'vim72' directory is in the correct place and is populated.

The command 'which gcc-4.0' returns '/usr/bin/gcc-4.0' as expected.

Prior to stubbing my toe on 'vim', I successfully upgraded half a  
dozen ports.  I am guessing this is a catch-all dependence issue;  
however, the only ports left to be upgraded are 'xorg...' ports.   
What's crashing this install?  Thanks for any help.

Here is a snippet of what follows the error message:
--->  .................
--->  Attempting to fetch 7.2.065 from http://distfiles.macports.org/vim72
--->  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
/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/screen.o screen.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/search.o search.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/spell.o spell.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/syntax.o syntax.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/tag.o tag.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/term.o term.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/ui.o ui.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/undo.o undo.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/window.o window.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/os_macosx.o os_macosx.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/os_mac_conv.o os_mac_conv.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/netbeans.o netbeans.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         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








From jmr at macports.org  Fri Dec 12 11:42:47 2008
From: jmr at macports.org (Joshua Root)
Date: Sat, 13 Dec 2008 06:42:47 +1100
Subject: 'sudo port upgrade vim' fails
In-Reply-To: <8C164EBA-4049-40BB-95AA-48AA100058B7@kitcarson.net>
References: <8C164EBA-4049-40BB-95AA-48AA100058B7@kitcarson.net>
Message-ID: <4942BEB7.8010101@macports.org>

Timothy Goins wrote:
> Here is a snippet of what follows the error message:
> --->  .................
> --->  Attempting to fetch 7.2.065 from http://distfiles.macports.org/vim72
> --->  Verifying checksum(s) for vim
> --->  Extracting vim
> --->  Applying patches to vim
> --->  Configuring vim
> --->  Building vim
<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

FYI, this problem is being tracked in
<http://trac.macports.org/ticket/17606>.

- Josh

From me at brianhogg.ca  Fri Dec 12 13:06:23 2008
From: me at brianhogg.ca (pres201)
Date: Fri, 12 Dec 2008 13:06:23 -0800 (PST)
Subject: Apache2 Modules?
Message-ID: <20983670.post@talk.nabble.com>


Hi,

My apologies if this is answered elsewhere, but some searching hasn't turned
anything up yet.  I'm new to ports after trying to install apache2 from
scratch with little success so far.

Basically I'm able to install the basic apache2 with "sudo port apache2" but
I require additional configuration options (such as mod_access and mod_auth
to start).

Is there an easy way to do something this basic without hacking away at the
Ports files?  Also since these modules are included in the core apache2
download, they should compile no problem correct?

Thanks for any tips, greatly appreciated.

Brian
-- 
View this message in context: http://www.nabble.com/Apache2-Modules--tp20983670p20983670.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From blb at macports.org  Fri Dec 12 13:19:07 2008
From: blb at macports.org (Bryan Blackburn)
Date: Fri, 12 Dec 2008 14:19:07 -0700
Subject: Apache2 Modules?
In-Reply-To: <20983670.post@talk.nabble.com>
References: <20983670.post@talk.nabble.com>
Message-ID: <20081212211907.GD486@ninagal.withay.com>

On Fri, Dec 12, 2008 at 01:06:23PM -0800, pres201 said:
> 
> Hi,
> 
> My apologies if this is answered elsewhere, but some searching hasn't turned
> anything up yet.  I'm new to ports after trying to install apache2 from
> scratch with little success so far.
> 
> Basically I'm able to install the basic apache2 with "sudo port apache2" but
> I require additional configuration options (such as mod_access and mod_auth
> to start).

mod_access is gone as of, I believe, 2.1; there are various mod_auth*
modules which should be present with a normal apache2 install, I see:

mod_auth_basic.so
mod_auth_digest.so
mod_authn_anon.so
mod_authn_dbd.so
mod_authn_dbm.so
mod_authn_default.so
mod_authn_file.so
mod_authz_dbm.so
mod_authz_default.so
mod_authz_groupfile.so
mod_authz_host.so
mod_authz_owner.so
mod_authz_svn.so
mod_authz_user.so

(all in ${prefix}/apache2/modules).

Further info can be found at:

<http://httpd.apache.org/docs/2.1/howto/auth.html>

Bryan


> 
> Is there an easy way to do something this basic without hacking away at the
> Ports files?  Also since these modules are included in the core apache2
> download, they should compile no problem correct?
> 
> Thanks for any tips, greatly appreciated.
> 
> Brian

From ryandesign at macports.org  Fri Dec 12 17:30:42 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 12 Dec 2008 19:30:42 -0600
Subject: panther - php5 upgrade - i'm confused
In-Reply-To: <10F7AB09-3DD4-4C40-9FE9-AD0A7BB9F08C@macports.org>
References: <B1303BBD-3F85-4602-9F7C-AF35AFF1E375@centosprime.com>
	<10F7AB09-3DD4-4C40-9FE9-AD0A7BB9F08C@macports.org>
Message-ID: <233E52B4-A188-4195-B75B-E8F2001591CC@macports.org>


On Dec 6, 2008, at 13:24, Ryan Schmidt wrote:

> On Dec 6, 2008, at 07:59, Chris Janton wrote:
>
>> admin at x:admin:125 $ sudo port upgrade php5
>> --->  Installing apache2 2.2.10_0+darwin_7
[snip]
>> admin at x:admin:126 $ port installed
>> The following ports are currently installed:
>>   apache @1.3.41_0 (active)
>>   apache2 @2.2.10_0+darwin_7
>>   apr @1.3.3_0 (active)
>>   apr-util @1.3.4_1+no_bdb (active)
>>   php5 @5.2.6_2+apache+darwin_7+macosx+mysql5+pear (active)
>> admin at x:admin:127 $
>>
>> Why does the php5 upgrade "install" apache2?
>
> I don't know... I didn't change anything in the dependencies  
> recently. I'll test on my Panther machine later.

[snip]

I see it now too, if I install php5 with something other than the  
+apache2 variant (so, either +apache or +fastcgi or +no_web) and then  
ask to upgrade the port. It's not Panther-specific. It's this base bug:

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

The port declares dependencies on apache2 by default (via the  
+apache2 variant), but even though you've overridden that default  
with your variant selection, MacPorts doesn't respect that during  
upgrade.

The workaround for now is to first manually ensure php5's  
dependencies are up to date, then ignore dependencies when upgrading  
php5:

sudo port -nf upgrade php5



From ryandesign at macports.org  Fri Dec 12 20:55:17 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 12 Dec 2008 22:55:17 -0600
Subject: error upgrading PHP5 on Panther
In-Reply-To: <3F6ECE80-ECEF-480A-ACBE-97B5E94CF8F4@centosprime.com>
References: <3F6ECE80-ECEF-480A-ACBE-97B5E94CF8F4@centosprime.com>
Message-ID: <D833F527-E070-475C-9DA2-D89B93894BBA@macports.org>

On Dec 12, 2008, at 09:12, Chris Janton wrote:

> --->  Fetching php5
> --->  Attempting to fetch php-5.2.8.tar.bz2 from http://www.php.net/ 
> distributions/
> --->  Verifying checksum(s) for php5
> --->  Extracting php5
> --->  Applying patches to php5
> --->  Configuring php5
> --->  Building php5 with target all
> Error: Target org.macports.build returned: shell command " cd "/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.8" && make all " returned error 2
> Command output: /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.8/ext/odbc/php_odbc.c:3624: warning: passing arg 1  
> of `_efree' makes pointer from integer without a cast
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_www_p 
> hp5/work/php-5.2.8/ext/odbc/php_odbc.c:3628: error: invalid type  
> argument of `->'

[snip]

Indeed. I filed a ticket for this:

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

If anyone has any information on PHP and ODBC, if anyone here uses  
PHP's ODBC support, please let me know.



From urkapd at libero.it  Sat Dec 13 01:49:58 2008
From: urkapd at libero.it (MAS!)
Date: Sat, 13 Dec 2008 10:49:58 +0100
Subject: connection errors when macports libs are used with Tiger X11
	headers
In-Reply-To: <DB5CB40C-1675-4347-8C16-9FBC859DC87C@macports.org>
References: <6157F2F4-E6BD-4DF6-9FC4-293078AC6F8E@imem.cnr.it>
	<DB5CB40C-1675-4347-8C16-9FBC859DC87C@macports.org>
Message-ID: <6735E272-42E3-4652-91DE-23CEBD273B1F@libero.it>

I had the same troubles:


> I fixed a big chunk of this yesterday, so resync and:
> sudo port -v -f uninstall xrender cairo pango gtk2
> sudo port -v install gtk2
>

I did it but it doesn't work:
(for example)

bart:~ mas$ pidgin
XIO:  fatal IO error 9 (Bad file descriptor) on X server ":0.0"
       after 7 requests (6 known processed) with 0 events remaining.


> Does it work now?  If not, does 'gtk-demo' work?
>

yes, gtk-demo works.

and I'm trying to install the new gtk release (2.14.5) but ...

(...)
/bin/sh: line 1: gtkdoc-rebase: command not found
:(

any help?
thank you in advance

marco

From face at CentosPrime.COM  Sat Dec 13 07:37:00 2008
From: face at CentosPrime.COM (Chris Janton)
Date: Sat, 13 Dec 2008 08:37:00 -0700
Subject: libxml2 woes (PHP5 and friends)
In-Reply-To: <DBDDE28C-BD43-4F23-92D7-1EEADEA2F118@macports.org>
References: <02208C59-5C29-4C05-B36B-3A3841C8CFD7@centosprime.com>
	<DBDDE28C-BD43-4F23-92D7-1EEADEA2F118@macports.org>
Message-ID: <B9010DCC-67E1-4C1B-9ED8-423A016B2EB6@CentosPrime.COM>

On 2008-12-11 , at 03:41 , Ryan Schmidt wrote:

>> but I don't see the difference between those and what is in the PHP  
>> configuration on macports that looks like
>>
>> 	 --with-libxml-dir=${prefix} \
>> 	 --with-gettext=${prefix} \
>> 	 --with-xml \
>> 	 --with-expat-dir=${prefix} \
>> 	 --with-xmlrpc \
>


w00t

with this change

     --with-xml \
     --with-libexpat-dir=${prefix} \
     --with-xmlrpc \

the xml parsing problem "goes away". I upgraded php5 on my Leopard  
system, restarted Apache (finally learned the trick of "kill -SIGHUP  
xx" where xx is the PID of the Apache daemondo process) and tested from

	Wordpress/external Wordpress edit tool (MarsEdit)
	Flickr "Blog This"

Both tests passed with flying colors. Thanks Ryan!!!

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



From face at CentosPrime.COM  Sat Dec 13 09:17:49 2008
From: face at CentosPrime.COM (Chris Janton)
Date: Sat, 13 Dec 2008 10:17:49 -0700
Subject: libxml2 - PHP5 - expat - Panther
Message-ID: <C6DA327E-DAD5-4D40-9D02-C2F5A4B0EE31@centosprime.com>

short version - if I modify a php5.2.6 portfile to use --with-libexpat- 
dir (as opposed to --with-expat-dir)
the "fix" to the broken XML parsing doesn't work.

On my Leopard systems that change in configuration works fine.

On my Panther system if I run the simple test case of the failing  
parse on the command line I see a proper result.

The real test is through Apache to Wordpress/xmlrpc.php -
I try that (via MarsEdit or Flickr) and what I get in the Apache error  
log is

	[Sat Dec 13 09:48:21 2008] [notice] child pid 21568 exit signal Bus  
error (10)

along with no response at the client side. Essentially something dies  
hard.

I have tracked it as far as I can, to the deeply embedded class- 
IXR.php call to "xml_parse()"
This call

	if (!xml_parse($this->_parser, $this->message)) {...}

never completes.

For the time being I think I prefer a poor result due to the parse as  
opposed to httpd client processes dying.

To that end I put the php5 Portfile back to 5.2.6 with the wrong "-- 
with-expat-dir". That was the last, known, working edition of php5 and  
friends.

I'm basically back to square -1 on my 10.3.9 system.

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



From jeremyhu at macports.org  Sat Dec 13 11:44:11 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Sat, 13 Dec 2008 11:44:11 -0800
Subject: connection errors when macports libs are used with Tiger X11
	headers
In-Reply-To: <6735E272-42E3-4652-91DE-23CEBD273B1F@libero.it>
References: <6157F2F4-E6BD-4DF6-9FC4-293078AC6F8E@imem.cnr.it>
	<DB5CB40C-1675-4347-8C16-9FBC859DC87C@macports.org>
	<6735E272-42E3-4652-91DE-23CEBD273B1F@libero.it>
Message-ID: <91748C79-DDD9-4083-B048-0BE9CF16DF0F@macports.org>


On Dec 13, 2008, at 01:49, MAS! wrote:

> I had the same troubles:
>
>
>> I fixed a big chunk of this yesterday, so resync and:
>> sudo port -v -f uninstall xrender cairo pango gtk2
>> sudo port -v install gtk2
>>
>
> I did it but it doesn't work:
> (for example)
>
> bart:~ mas$ pidgin
> XIO:  fatal IO error 9 (Bad file descriptor) on X server ":0.0"
>      after 7 requests (6 known processed) with 0 events remaining.
>
>
>> Does it work now?  If not, does 'gtk-demo' work?
>>
>
> yes, gtk-demo works.

Yeah, there seems to be some problem when some libs link against the  
Tiger X11 libs and others link against ones from Macports... I started  
a thread about this in macports-dev yesterday...

> and I'm trying to install the new gtk release (2.14.5) but ...
>
> (...)
> /bin/sh: line 1: gtkdoc-rebase: command not found
> :(

It was missing a depends_build on gtk-doc ... I've added it.

---

My advice to you is to stick entirely with macports xorg-* ports or  
the system /usr/X11R6 libs and not mix the two until we figure this out.



From christopher.rob.jones at cern.ch  Sat Dec 13 12:52:12 2008
From: christopher.rob.jones at cern.ch (Chris Jones)
Date: Sat, 13 Dec 2008 20:52:12 +0000
Subject: change gcc version ?
Message-ID: <3C5AF90B-5B75-4210-8ACB-73926A32B363@cern.ch>

Hi,

I'm trying to compile some KDE4 packages from macports and am running  
into a problem with kdelibs4. After some googling I found various  
places which mention the error I am getting, and all suggest using gcc  
4.2 instead of 4.0

So, I want to try this, but cannot figure out how I am suppose to tell  
macports to use the newer gcc version (I have the latest Xcode  
instead, so have both versions available).

Can someone point me to some instructions on how to change the gcc  
version that is used ?

cheers Chris

From ryandesign at macports.org  Sat Dec 13 14:45:39 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sat, 13 Dec 2008 16:45:39 -0600
Subject: change gcc version ?
In-Reply-To: <3C5AF90B-5B75-4210-8ACB-73926A32B363@cern.ch>
References: <3C5AF90B-5B75-4210-8ACB-73926A32B363@cern.ch>
Message-ID: <30DAF0ED-C0DE-4F42-9E4C-F17EECBCFAAB@macports.org>


On Dec 13, 2008, at 14:52, Chris Jones wrote:

> I'm trying to compile some KDE4 packages from macports and am  
> running into a problem with kdelibs4. After some googling I found  
> various places which mention the error I am getting, and all  
> suggest using gcc 4.2 instead of 4.0
>
> So, I want to try this, but cannot figure out how I am suppose to  
> tell macports to use the newer gcc version (I have the latest Xcode  
> instead, so have both versions available).
>
> Can someone point me to some instructions on how to change the gcc  
> version that is used ?

You would add the line "configure.compiler gcc-4.2" to the kdelibs4  
portfile.

gcc-4.2 is only provided in Xcode 3 and up, so this would only work  
on Leopard and up.

Since you're likely not the only one experiencing whatever issue it  
is, you should file an issue in our issue tracker explaining what the  
problem is and suggesting this fix, if it works for you. Then the  
maintainer of the port can evaluate it and hopefully include it in  
the portfile so you and everyone else can benefit from it.




From christopher.rob.jones at cern.ch  Sat Dec 13 15:27:31 2008
From: christopher.rob.jones at cern.ch (Chris Jones)
Date: Sat, 13 Dec 2008 23:27:31 +0000
Subject: change gcc version ?
In-Reply-To: <30DAF0ED-C0DE-4F42-9E4C-F17EECBCFAAB@macports.org>
References: <3C5AF90B-5B75-4210-8ACB-73926A32B363@cern.ch>
	<30DAF0ED-C0DE-4F42-9E4C-F17EECBCFAAB@macports.org>
Message-ID: <687FCAD9-2AA4-4589-A36E-AE73D46F7E63@cern.ch>

Hi,

On 13 Dec 2008, at 10:45PM, Ryan Schmidt wrote:

>
> On Dec 13, 2008, at 14:52, Chris Jones wrote:
>
>> I'm trying to compile some KDE4 packages from macports and am  
>> running into a problem with kdelibs4. After some googling I found  
>> various places which mention the error I am getting, and all  
>> suggest using gcc 4.2 instead of 4.0
>>
>> So, I want to try this, but cannot figure out how I am suppose to  
>> tell macports to use the newer gcc version (I have the latest Xcode  
>> instead, so have both versions available).
>>
>> Can someone point me to some instructions on how to change the gcc  
>> version that is used ?
>
> You would add the line "configure.compiler gcc-4.2" to the kdelibs4  
> portfile.

Thanks. Eventually I decoded the MacPorts documentation and figured  
out I could also do it from the command line with

>   $ sudo port install <portname> configure.compiler=gcc-4.2

>
>
> gcc-4.2 is only provided in Xcode 3 and up, so this would only work  
> on Leopard and up.

Yeah. One of the places I found the suggestion to use gcc 4.2 was the  
kde-mac mailing list, and there this very point is also discussed.

http://mail.kde.org/pipermail/kde-mac/2008-November/000257.html

only a couple weeks old.

>
>
> Since you're likely not the only one experiencing whatever issue it  
> is, you should file an issue in our issue tracker explaining what  
> the problem is and suggesting this fix, if it works for you. Then  
> the maintainer of the port can evaluate it and hopefully include it  
> in the portfile so you and everyone else can benefit from it.

OK, I'm currently rebuilding with gcc 4.2 so I'll see what happens.  
I'll post a ticket when that is done.

Chris

>
>
>
>
> _______________________________________________
> 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/20081213/b4017319/attachment.html>

From blb at macports.org  Sat Dec 13 20:13:18 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sat, 13 Dec 2008 21:13:18 -0700
Subject: MacPorts 1.7.0 has been released
Message-ID: <20081214041318.GG530@ninagal.withay.com>

The MacPorts Project is happy to announce that, after nearly a year in
the making, the 1.7.0 version has been released.  It is now available
via the usual methods:

 - selfupdate if you already have it installed
 - package installers in DMGs for 10.3 [1], 10.4 [2], and 10.5 [3] (the
   latter two being universal builds)
 - source tarballs, both .tar.bz2 [4] and .tar.gz [5]
 - subversion tag [6]

The list of what's new in 1.7.0 is quite extensive (so I won't list it here),
the details can be found in the NEWS [7] file or the somewhat more
exhaustive ChangeLog [8].

A big thanks to the developers for their hard work with all of the various
features and bug fixes in 1.7.0, and to everyone for your patience while
waiting for this version.

Detached PGP signatures for the DMGs and source tarballs have been made
with my key, which is available on the keyservers and my MacPorts wiki
page [9].

Bryan

[1] - <http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0-10.3-Panther.dmg>

[2] - <http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0-10.4-Tiger.dmg>

[3] - <http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0-10.5-Leopard.dmg>

[4] - <http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0.tar.bz2>

[5] - <http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0.tar.gz>

[6] - <http://svn.macports.org/repository/macports/tags/release_1_7_0>

[7] - <http://svn.macports.org/repository/macports/branches/release_1_7/base/NEWS>

[8] - <http://svn.macports.org/repository/macports/branches/release_1_7/base/ChangeLog>

[9] - <http://trac.macports.org/wiki/blb>

PS, my PGP key ID is 2952D7AF,
fingerprint BEB4 6B21 320E 737F F176  2D15 C853 3784 2952 D7AF

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081213/0b36d9ef/attachment.bin>

From frstan at bellsouth.net  Sat Dec 13 20:23:33 2008
From: frstan at bellsouth.net (William Davis)
Date: Sat, 13 Dec 2008 23:23:33 -0500
Subject: MacPorts 1.7.0 has been released
In-Reply-To: <20081214041318.GG530@ninagal.withay.com>
References: <20081214041318.GG530@ninagal.withay.com>
Message-ID: <0636F601-28A1-4217-9B46-E72F4D1B8A00@bellsouth.net>


On Dec 13, 2008, at 11:13 PM, Bryan Blackburn wrote:

> The MacPorts Project is happy to announce that, after nearly a year in
> the making, the 1.7.0 version has been released.  It is now available
> via ...../snip/
> A big thanks to the developers for their hard work with all of the  
> various
> features and bug fixes in 1.7.0, and to everyone for your patience  
> while
> waiting for this version.
>

A statement well worth repeating! Hoozah!
Normal upgrade via selfupdate here.  :)
William Davis
frstanATbellsouthDOTnet
Mac OS X.5.5 Darwin 9.5.0
XQuartz 2.3.2_rc3 (xorg-server 1.4.2-apple27)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From jmr at macports.org  Sat Dec 13 21:22:02 2008
From: jmr at macports.org (Joshua Root)
Date: Sun, 14 Dec 2008 16:22:02 +1100
Subject: MacPorts 1.7.0 has been released
In-Reply-To: <20081214041318.GG530@ninagal.withay.com>
References: <20081214041318.GG530@ninagal.withay.com>
Message-ID: <494497FA.8080009@macports.org>

Bryan Blackburn wrote:
> The MacPorts Project is happy to announce that, after nearly a year in
> the making, the 1.7.0 version has been released.  It is now available
> via the usual methods:

Kudos to Bryan for his work in packaging this release.

> The list of what's new in 1.7.0 is quite extensive (so I won't list it here),
> the details can be found in the NEWS [7] file or the somewhat more
> exhaustive ChangeLog [8].

Quick highlights:

We have worked around a bug in Leopard's Tcl which often caused
mysterious build failures.

There should no longer be any need to use the -f option in normal use.

Several bugs which affected the -R option have been fixed.

You can choose which architectures to build for in the +universal
variant, using the universal_archs setting in macports.conf. Must be a
subset of ppc, i386, ppc64, x86_64. (Note that not all ports will build
universal, and even less will build for all architectures.)

We now try to download files from the mirror with the fastest ping time.

We now have our own mirrors which are added to the mix, so fetch
failures due to the upstream site being down should be much more rare.

You can sync using a daily tarball of the ports tree by adding a line to
sources.conf like:
http://macports.org/files/ports.tar.gz

- Josh

From kuepper.jochen at googlemail.com  Sun Dec 14 00:58:02 2008
From: kuepper.jochen at googlemail.com (=?ISO-8859-1?Q?Jochen_K=FCpper?=)
Date: Sun, 14 Dec 2008 09:58:02 +0100
Subject: MacPorts 1.7.0 has been released
In-Reply-To: <20081214041318.GG530@ninagal.withay.com>
References: <20081214041318.GG530@ninagal.withay.com>
Message-ID: <54CF8070-2BD0-4229-8E2A-42DDB86FE3B7@googlemail.com>

On 14.12.2008, at 05:13, Bryan Blackburn wrote:

> The MacPorts Project is happy to announce that, after nearly a year  
> in the making, the 1.7.0 version has been released.


Great. Thank you very much, all you have contributed!
It's nice to see that "restructuring of the organization" bears fruits  
quickly!


Anyway, here's my experience, showing one old bug (which currently has  
a trac milestone of 1.7.1) and an issue with sources.conf, which might  
be due to a change of the files' format? Anyway, easy to get along,  
hope it'll get fixed sometime soon;-)



 > sudo port selfupdate

MacPorts base version 1.600 installed

Downloaded MacPorts base version 1.700
Configuring, Building and Installing new MacPorts base
Error: /opt/local/bin/port: port selfupdate failed: 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: + /usr/bin/install -c -o root -g admin -m 444  
portuninstall.tcl /opt/local/share/macports/Tcl/registry2.0/ 
portuninstall.tcl
===> making install in src/darwintracelib1.0
/usr/bin/install -c -d -o root -g admin -m 0755 /opt/local/share/ 
macports/Tcl/darwintrace1.0
/usr/bin/install -c -o root -g admin -m 444 darwintrace.dylib /opt/ 
local/share/macports/Tcl/darwintrace1.0
===> making install in src/tclobjc1.0
/usr/bin/install -c -d -o root -g admin -m 0755 /opt/local/share/ 
macports/Tcl/tclobjc1.0
/usr/bin/install -c -o root -g admin -m 444 tclobjc.dylib /opt/local/ 
share/macports/Tcl/tclobjc1.0
===> making install in src/port
cat ../../doc/prefix.mtree | /usr/sbin/mtree -U -d -e -p /opt/local > / 
dev/null
/usr/bin/install -c -d -o root -g admin -m 0755 /opt/local/bin
/usr/bin/install -c -d -o root -g admin -m 0755 /opt/local/var/macports
/usr/bin/install -c -o root -g admin -m 555 port portindex portmirror / 
opt/local/bin/
/usr/bin/install -c -o root -g admin -m 444 port-help.tcl  /opt/local/ 
var/macports/
cd /opt/local/bin && ln -s -f port portf
===> making install in src/programs
===> making install in src/programs/daemondo
/usr/bin/install -c -o root -g admin -m 555 build/daemondo /opt/local/ 
bin
/usr/bin/install -c -o root -g admin -m 444 setupenv.bash  /opt/local/ 
share/macports/
/usr/bin/tclsh src/upgrade_sources_conf_default.tcl /opt/local
svn: This client is too old to work with working copy '/Users/jochen/ 
source/macports/dports'; please get a newer Subversion client
     while executing
"close $svnChannel"
     ("while" body line 17)
     invoked from within
"while {[gets $sourcesConfChannel line] >= 0} {
    set addDefault false
    if {!$defaultSeen && ![regexp {^\s*#|^$} $line]} {
       if {[regexp {^([\w-..."
     (file "src/upgrade_sources_conf_default.tcl" line 34)
make: *** [install] Error 1

This is tickets #15868 and #16062, the workaround in the latter works.


 > sudo vi /Library/Tcl/macports1.0/macports_autoconf.tcl

Change accordind to #16062


 > sudo port selfupdate

No default port source specified in /opt/local/etc/macports/sources.conf
     while executing
"mportinit ui_options global_options global_variations"
Error: /opt/local/bin/port: Failed to initialize MacPorts, No default  
port source specified in /opt/local/etc/macports/sources.conf

Need to manually add "[default]" to my only source specification line...


 > sudo port selfupdate

MacPorts base version 1.700 installed
Downloaded MacPorts base version 1.700

The MacPorts installation is not outdated so it was not updated



Greetings,
Jochen
-- 
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
     Libert?, ?galit?, Fraternit?                GnuPG key: CC1B0B4D
         Sex, drugs and rock-n-roll


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

From blb at macports.org  Sun Dec 14 01:19:32 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 14 Dec 2008 02:19:32 -0700
Subject: MacPorts 1.7.0 has been released
In-Reply-To: <54CF8070-2BD0-4229-8E2A-42DDB86FE3B7@googlemail.com>
References: <20081214041318.GG530@ninagal.withay.com>
	<54CF8070-2BD0-4229-8E2A-42DDB86FE3B7@googlemail.com>
Message-ID: <20081214091932.GA59407@ninagal.withay.com>

On Sun, Dec 14, 2008 at 09:58:02AM +0100, Jochen K?pper said:
[...]
>
> Anyway, here's my experience, showing one old bug (which currently has a 
> trac milestone of 1.7.1) and an issue with sources.conf, which might be 
> due to a change of the files' format? Anyway, easy to get along, hope 
> it'll get fixed sometime soon;-)
[...]
> /usr/bin/tclsh src/upgrade_sources_conf_default.tcl /opt/local
> svn: This client is too old to work with working copy '/Users/jochen/ 
> source/macports/dports'; please get a newer Subversion client

That upgrade script tries to be smart in finding out which source needs to
be called the default one.  In your case you have a subversion-checkout for
your ports, which needs an svn version of 1.5.x, but it apparently found an
older (probably /usr/bin/svn if you are on 10.5).  Hence, it failed.  This
is somewhat similar to

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

in that either way, the script fails and doesn't update sources.conf.  The
message from that script, had it not bombed, would have otherwise notified
you that your /opt/local/etc/macports/sources.conf file needs to be updated,
with one of the entries (the one pointing to the main MacPorts repository)
tagged default, like so:

file:///path/to/svn/checkout [default]

[...]
>
> > sudo port selfupdate
>
> No default port source specified in /opt/local/etc/macports/sources.conf
>     while executing
> "mportinit ui_options global_options global_variations"
> Error: /opt/local/bin/port: Failed to initialize MacPorts, No default  
> port source specified in /opt/local/etc/macports/sources.conf
>
> Need to manually add "[default]" to my only source specification line...

Yup, that is the correct fix to it, since the upgrade script was unable to
figure out which to do.  I think one way to handle such things is, if there
is only one (as in your case), it should be tagged default, since otherwise
MacPorts probably wouldn't be too functional without the primary repository.

Sorry about you having an install with just the right settings to run into
this...

Bryan


>
>
> > sudo port selfupdate
>
> MacPorts base version 1.700 installed
> Downloaded MacPorts base version 1.700
>
> The MacPorts installation is not outdated so it was not updated
>
>
>
> Greetings,
> Jochen
> -- 
> Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
>     Libert?, ?galit?, Fraternit?                GnuPG key: CC1B0B4D
>         Sex, drugs and rock-n-roll
>
>

From urkapd at libero.it  Sun Dec 14 02:51:04 2008
From: urkapd at libero.it (MAS!)
Date: Sun, 14 Dec 2008 11:51:04 +0100
Subject: connection errors when macports libs are used with Tiger X11
	headers
In-Reply-To: <91748C79-DDD9-4083-B048-0BE9CF16DF0F@macports.org>
References: <6157F2F4-E6BD-4DF6-9FC4-293078AC6F8E@imem.cnr.it>
	<DB5CB40C-1675-4347-8C16-9FBC859DC87C@macports.org>
	<6735E272-42E3-4652-91DE-23CEBD273B1F@libero.it>
	<91748C79-DDD9-4083-B048-0BE9CF16DF0F@macports.org>
Message-ID: <B3DC2C0C-24B9-4461-9BCD-132540121B57@libero.it>

>>>
>> yes, gtk-demo works.
>
> Yeah, there seems to be some problem when some libs link against  
> the Tiger X11 libs and others link against ones from Macports... I  
> started a thread about this in macports-dev yesterday...

thanks; I really need my gtk applications under tiger..

>> /bin/sh: line 1: gtkdoc-rebase: command not found
>> :(
> It was missing a depends_build on gtk-doc ... I've added it.

but it seems even gtk-doc port is broken:

(...)
configure: error: could not find DocBook XML DTD V4.3 in XML catalog
(...)

(even if the docbook-xml-4.3 port is installed)

thank you in advance for the support

MAS!


From masschel at gmail.com  Sun Dec 14 03:40:13 2008
From: masschel at gmail.com (Bart Masschelein)
Date: Sun, 14 Dec 2008 12:40:13 +0100
Subject: MacPorts 1.7.0 has been released
In-Reply-To: <20081214041318.GG530@ninagal.withay.com>
References: <20081214041318.GG530@ninagal.withay.com>
Message-ID: <160BBB51-3D13-4887-B81D-21E483B8E3A8@gmail.com>

> A big thanks to the developers for their hard work with all of the  
> various
> features and bug fixes in 1.7.0.

Many thanks and congratulations from a happy user indeed!!! Upgrade  
went smooth...

Well, appart from sth I don't know if it is a MacPorts issue. I did an  
upgrade of my outdated ports, and iso-codes needed to be installed as  
well apparantly. And it was waiting to fetch the source for half an  
hour at least, waiting on:

--->  Attempting to fetch iso-codes-3.5.tar.bz2 from ftp://pkg-isocodes.alioth.debian.org/pub/pkg-isocodes/

I Ctrl-C-ed, and re-issued an update, and then it went smooth again.

Again, keep up the good work!

Bart

From christopher.rob.jones at cern.ch  Sun Dec 14 05:08:33 2008
From: christopher.rob.jones at cern.ch (Chris Jones)
Date: Sun, 14 Dec 2008 13:08:33 +0000
Subject: change gcc version ?
In-Reply-To: <687FCAD9-2AA4-4589-A36E-AE73D46F7E63@cern.ch>
References: <3C5AF90B-5B75-4210-8ACB-73926A32B363@cern.ch>
	<30DAF0ED-C0DE-4F42-9E4C-F17EECBCFAAB@macports.org>
	<687FCAD9-2AA4-4589-A36E-AE73D46F7E63@cern.ch>
Message-ID: <6CEA549F-1074-4808-B0B5-DA450346FA8E@cern.ch>

Hi,

On 13 Dec
>
> OK, I'm currently rebuilding with gcc 4.2 so I'll see what happens.  
> I'll post a ticket when that is done.
>
Building with gcc 4.2 worked for me. Ticket available here.

https://trac.macports.org/ticket/17643

btw., I noticed a few other problems when trying to build kdelibs with  
the dependencies. Being new to macports I'm not sure if they should be  
considered bugs or features

1. kdelibs4 depends on qt4-mac. However, the default installation of  
qt4-mac does not include SSL support, which kdelibs4 requires. If you  
allow the installation of kdelibs4 to trigger the default installation  
of qt4-mac, then kdelibs4 fails to configure complaining about the  
lack of ssl support in qt4. I had to go back and install qt4-mac again  
by hand with the +ssl variant ?

2. various deps seem to be missing. kdelibs4 does not have deps on  
pcre or shared-mime-info, but without either of these being installed  
kdelibs4 fails to configure.

Are problems like this bugs and should I also submit tickets for cases  
like this (I am starting to try and build other kde4 packages and  
seeing similar things...

Chris

From raimue at macports.org  Sun Dec 14 05:13:55 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Sun, 14 Dec 2008 14:13:55 +0100
Subject: MacPorts 1.7.0 has been released
In-Reply-To: <160BBB51-3D13-4887-B81D-21E483B8E3A8@gmail.com>
References: <20081214041318.GG530@ninagal.withay.com>
	<160BBB51-3D13-4887-B81D-21E483B8E3A8@gmail.com>
Message-ID: <49450693.9010207@macports.org>

Bart Masschelein wrote:
> Well, appart from sth I don't know if it is a MacPorts issue. I did an  
> upgrade of my outdated ports, and iso-codes needed to be installed as  
> well apparantly. And it was waiting to fetch the source for half an  
> hour at least, waiting on:
> 
> --->  Attempting to fetch iso-codes-3.5.tar.bz2 from ftp://pkg-isocodes.alioth.debian.org/pub/pkg-isocodes/
> 
> I Ctrl-C-ed, and re-issued an update, and then it went smooth again.

There have been download issues with alioth.debian.org before. But as
the new distfile mirroring is in place, it should not happen often
anymore. port uses now ping-based mirror selection and will also
automatically try distfiles.macports.org.

Rainer

From masschel at gmail.com  Sun Dec 14 07:53:02 2008
From: masschel at gmail.com (Bart Masschelein)
Date: Sun, 14 Dec 2008 16:53:02 +0100
Subject: Uninstall non-active packages
In-Reply-To: <493C523E.4010402@macports.org>
References: <1ADB355C-7E0F-4325-A6C1-06137CEEA7E1@gmail.com>	<FF43A2E0-AF89-4CAE-B96C-31D0C9FD8008@macports.org>
	<49886846-BB84-4BDF-8AE1-223A2B616688@gmail.com>
	<493C4E9B.4050004@macports.org>
	<B00D5ECD-E575-42F7-B4A4-B6FFD4F64A0D@gmail.com>
	<493C523E.4010402@macports.org>
Message-ID: <5279AE0E-E58F-4BAC-B2D5-F00E0B81291B@gmail.com>


On 07 Dec 2008, at 23:46, Joshua Root wrote:

> Bart Masschelein wrote:
>>
>> On 07 Dec 2008, at 23:30, Joshua Root wrote:
>>
>>> Bart Masschelein wrote:
>>>> Small side-question: why is 'inactive' not available from the
>>>> interactive console?
>>>
>>> I just tested, and it works in interactive mode. Note that  
>>> 'inactive'
>>> specifies a set of ports, it's not an action. So to see the list of
>>> inactive ports, you'd use "port echo inactive".
>>
>> Right. But isn't the same true for 'installed', and this works  
>> without
>> echo. You get different formatting, though.
>
> Yes, 'installed' has the dubious distinction of being both an action  
> and
> a pseudo-port. For historical reasons.

Add 'outdated' to this dubious list :-).

Never mind.

Bart

From deepblue4711 at gmx.net  Sun Dec 14 08:30:00 2008
From: deepblue4711 at gmx.net (Thomas G.)
Date: Sun, 14 Dec 2008 17:30:00 +0100
Subject: dbus not starting up after upgrade to dbus-1.2.6_0
Message-ID: <49453488.8060603@gmx.net>

Hi Group,
I ran into the problem that gtk-programs (e.g. nautilus) came up with an
error message, that the dbus-connection failed and config data could not
be stored.

I found a thread
    https://trac.macports.org/ticket/16833
where the problem is described, but it was related to the 1.2.3.

Downgrading to 1.2.4_2 (from 1.2.6_0)  solved the problem for me.

Can anyone confirm this behavior?


Thomas



From tim.visher at gmail.com  Sun Dec 14 10:15:51 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Sun, 14 Dec 2008 13:15:51 -0500
Subject: Issues Upgrading Outdated Under 1.700
Message-ID: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>

Hello Everyone,

So I upgraded to 1.700 this morning and that went totally fine.  Then,
I proceeded to attempt to do a `sudo port upgrade outdated` (which
I've never really had any success with in the past _either_) and I'm
consistently failing.  I get to a line such as `--->  Deactivating
db46 @4.6.21_1` and then the CPU cools down and it just stalls and
sits there doing nothing.  I have no idea what's going on.

Any suggestions?

-- 

In Christ,

Timmy V.

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

From jeremyhu at macports.org  Sun Dec 14 10:29:39 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Sun, 14 Dec 2008 10:29:39 -0800
Subject: connection errors when macports libs are used with Tiger X11
	headers
In-Reply-To: <B3DC2C0C-24B9-4461-9BCD-132540121B57@libero.it>
References: <6157F2F4-E6BD-4DF6-9FC4-293078AC6F8E@imem.cnr.it>
	<DB5CB40C-1675-4347-8C16-9FBC859DC87C@macports.org>
	<6735E272-42E3-4652-91DE-23CEBD273B1F@libero.it>
	<91748C79-DDD9-4083-B048-0BE9CF16DF0F@macports.org>
	<B3DC2C0C-24B9-4461-9BCD-132540121B57@libero.it>
Message-ID: <FEA7B71A-8BE0-406A-9DCE-E02430ED4A69@macports.org>


On Dec 14, 2008, at 02:51, MAS! wrote:

>>>>
>>> yes, gtk-demo works.
>>
>> Yeah, there seems to be some problem when some libs link against  
>> the Tiger X11 libs and others link against ones from Macports... I  
>> started a thread about this in macports-dev yesterday...
>
> thanks; I really need my gtk applications under tiger..

I suggest you just sudo port -v -f uninstall all your xorg-* ports and  
rebuild what was linked against them or pull in all the xorg-* ports  
and recompile ports that were linking against the system X11.

I'm sorry I don't have something better than that as a solution right  
now.  I'm working on it.

I think that just looping through the installed binaries with  
install_name_tool changing them from using /usr/X11R6/lib/... to /usr/ 
X11/lib/... should work as a mid-term solution... but it's messy.

> but it seems even gtk-doc port is broken:
>
> (...)
> configure: error: could not find DocBook XML DTD V4.3 in XML catalog
> (...)
>
> (even if the docbook-xml-4.3 port is installed)
>
> thank you in advance for the support

That kind of thing I know nothing about.  XML DTD cruft scares me...  
Open a ticket ;)

From jmr at macports.org  Sun Dec 14 10:33:22 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 15 Dec 2008 05:33:22 +1100
Subject: change gcc version ?
In-Reply-To: <6CEA549F-1074-4808-B0B5-DA450346FA8E@cern.ch>
References: <3C5AF90B-5B75-4210-8ACB-73926A32B363@cern.ch>	<30DAF0ED-C0DE-4F42-9E4C-F17EECBCFAAB@macports.org>	<687FCAD9-2AA4-4589-A36E-AE73D46F7E63@cern.ch>
	<6CEA549F-1074-4808-B0B5-DA450346FA8E@cern.ch>
Message-ID: <49455172.4070009@macports.org>

Chris Jones wrote:
> Hi,
> 
> On 13 Dec
>>
>> OK, I'm currently rebuilding with gcc 4.2 so I'll see what happens.
>> I'll post a ticket when that is done.
>>
> Building with gcc 4.2 worked for me. Ticket available here.
> 
> https://trac.macports.org/ticket/17643
> 
> btw., I noticed a few other problems when trying to build kdelibs with
> the dependencies. Being new to macports I'm not sure if they should be
> considered bugs or features

Bugs. :)

> 1. kdelibs4 depends on qt4-mac. However, the default installation of
> qt4-mac does not include SSL support, which kdelibs4 requires. If you
> allow the installation of kdelibs4 to trigger the default installation
> of qt4-mac, then kdelibs4 fails to configure complaining about the lack
> of ssl support in qt4. I had to go back and install qt4-mac again by
> hand with the +ssl variant ?

This is <http://trac.macports.org/ticket/126>. But since it causes such
problems, perhaps qt4-mac's ssl variant should be made default until
whenever someone fixes #126.

> 2. various deps seem to be missing. kdelibs4 does not have deps on pcre
> or shared-mime-info, but without either of these being installed
> kdelibs4 fails to configure.
> 
> Are problems like this bugs and should I also submit tickets for cases
> like this (I am starting to try and build other kde4 packages and seeing
> similar things...

Yes, definitely. (Make sure you search for existing tickets first, of
course.)

- Josh

From fred at dushin.net  Sun Dec 14 11:15:15 2008
From: fred at dushin.net (Fred Dushin)
Date: Sun, 14 Dec 2008 14:15:15 -0500
Subject: gnucash configure error (gnomecanvas)
Message-ID: <24BF2C81-4525-485C-ADDC-38F969AD6AD5@dushin.net>

Okay, this seems to be an issue with 1.6 and 1.7.0 (after reaching a  
fixed point with selfupdate:

 > sudo port selfupdate

MacPorts base version 1.700 installed
Downloaded MacPorts base version 1.700

The MacPorts installation is not outdated so it was not updated


 > sudo port -v install gnucash +without_hbci +without_ofx  
+without_quotes
--->  Fetching libgnomecanvas
--->  Verifying checksum(s) for libgnomecanvas
--->  Checksumming libgnomecanvas-2.20.1.1.tar.bz2
--->  Extracting libgnomecanvas
--->  Extracting libgnomecanvas-2.20.1.1.tar.bz2
--->  Configuring libgnomecanvas
...
checking for LIBGNOMECANVAS... configure: error: Package requirements  
(  gtk+-2.0 >= 2.0.3   gail >= 1.9.0   libart-2.0 >= 2.3.8   pango >=  
1.0.1   pangoft2 >= 1.0.1) were not met:

No package 'gail' found
...
Warning: the following items did not execute (for libgnomecanvas):  
org.macports.activate org.macports.configure org.macports.build  
org.macports.destroot org.macports.install
Error: The following dependencies failed to build: evince  
libgnomecanvas libgnomeui libbonoboui nautilus eel gnome-desktop gnome- 
themes gtk-engines2 py25-gnome py25-gtk py25-cairo py25-numpy fftw-3  
py25-nose py25-setuptools py25-zlib py25-orbit startup-notification  
gnome-menus librsvg libcroco libgsf libexif poppler openjpeg poppler- 
data goffice guile16 libgnomeprintui libgnomeprint bison libgnomecups  
libgtkhtml3 enchant libsoup slib slib-guile16

So then I do:
 > port search gail
libgail-gnome @1.20.1 (gnome)
     An implementation of the ATK interfaces for GNOME widgets.

Okay, so let's try:
 > sudo port -v install libgail-gnome
--->  Fetching at-spi
--->  Verifying checksum(s) for at-spi
--->  Checksumming at-spi-1.24.0.tar.bz2
--->  Extracting at-spi
--->  Extracting at-spi-1.24.0.tar.bz2
--->  Configuring at-spi
...
checking for X... no
configure: error: X development libraries not found

I'm running XQuartz 2.3.1

Ideas?

-Fred

From jmr at macports.org  Sun Dec 14 11:35:41 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 15 Dec 2008 06:35:41 +1100
Subject: gnucash configure error (gnomecanvas)
In-Reply-To: <24BF2C81-4525-485C-ADDC-38F969AD6AD5@dushin.net>
References: <24BF2C81-4525-485C-ADDC-38F969AD6AD5@dushin.net>
Message-ID: <4945600D.6010006@macports.org>

Fred Dushin wrote:
> Okay, this seems to be an issue with 1.6 and 1.7.0 (after reaching a
> fixed point with selfupdate:
> 
>> sudo port selfupdate
> 
> MacPorts base version 1.700 installed
> Downloaded MacPorts base version 1.700
> 
> The MacPorts installation is not outdated so it was not updated
> 
> 
>> sudo port -v install gnucash +without_hbci +without_ofx +without_quotes
> --->  Fetching libgnomecanvas
> --->  Verifying checksum(s) for libgnomecanvas
> --->  Checksumming libgnomecanvas-2.20.1.1.tar.bz2
> --->  Extracting libgnomecanvas
> --->  Extracting libgnomecanvas-2.20.1.1.tar.bz2
> --->  Configuring libgnomecanvas
> ...
> checking for LIBGNOMECANVAS... configure: error: Package requirements ( 
> gtk+-2.0 >= 2.0.3   gail >= 1.9.0   libart-2.0 >= 2.3.8   pango >=
> 1.0.1   pangoft2 >= 1.0.1) were not met:
> 
> No package 'gail' found

GAIL is now part of gtk2. Perhaps you need to upgrade the latter?

- Josh

From deepblue4711 at gmx.net  Sun Dec 14 12:22:10 2008
From: deepblue4711 at gmx.net (Thomas G.)
Date: Sun, 14 Dec 2008 21:22:10 +0100
Subject: dbus not starting up after upgrade to dbus-1.2.6_0
In-Reply-To: <49453488.8060603@gmx.net>
References: <49453488.8060603@gmx.net>
Message-ID: <49456AF2.9040004@gmx.net>

Hmmm,
funny thing.

Just switched back to 1.2.6_0 and it is still working.

Don't have a clue what happened...

Thanks.
 
Thomas

Thomas G. schrieb:
> Hi Group,
> I ran into the problem that gtk-programs (e.g. nautilus) came up with an
> error message, that the dbus-connection failed and config data could not
> be stored.
>
> I found a thread
>    https://trac.macports.org/ticket/16833
> where the problem is described, but it was related to the 1.2.3.
>
> Downgrading to 1.2.4_2 (from 1.2.6_0)  solved the problem for me.
>
> Can anyone confirm this behavior?
>
>
> Thomas
>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>


From fred at dushin.net  Sun Dec 14 12:44:41 2008
From: fred at dushin.net (Fred Dushin)
Date: Sun, 14 Dec 2008 15:44:41 -0500
Subject: gnucash configure error (gnomecanvas)
In-Reply-To: <4945600D.6010006@macports.org>
References: <24BF2C81-4525-485C-ADDC-38F969AD6AD5@dushin.net>
	<4945600D.6010006@macports.org>
Message-ID: <9A38C64E-8C29-4A76-8412-CC2DED4F07D6@dushin.net>

That worked, thanks.

I also needed to install both xorg-libXrandr and xorg-libXdamage to  
build gtk2.  There is a trac ticket for xorg-libXrandr (http://trac.macports.org/ticket/17360 
), but I don't know if there is one for the missing xorg-libXdamage  
dependency.

Should there be a trac ticket to capture the missing dependency from  
gnomecanvas to gtk2, as well?

Thanks,
-Fred

On Dec 14, 2008, at 2:35 PM, Joshua Root wrote:

> Fred Dushin wrote:
>> Okay, this seems to be an issue with 1.6 and 1.7.0 (after reaching a
>> fixed point with selfupdate:
>>
>>> sudo port selfupdate
>>
>> MacPorts base version 1.700 installed
>> Downloaded MacPorts base version 1.700
>>
>> The MacPorts installation is not outdated so it was not updated
>>
>>
>>> sudo port -v install gnucash +without_hbci +without_ofx  
>>> +without_quotes
>> --->  Fetching libgnomecanvas
>> --->  Verifying checksum(s) for libgnomecanvas
>> --->  Checksumming libgnomecanvas-2.20.1.1.tar.bz2
>> --->  Extracting libgnomecanvas
>> --->  Extracting libgnomecanvas-2.20.1.1.tar.bz2
>> --->  Configuring libgnomecanvas
>> ...
>> checking for LIBGNOMECANVAS... configure: error: Package  
>> requirements (
>> gtk+-2.0 >= 2.0.3   gail >= 1.9.0   libart-2.0 >= 2.3.8   pango >=
>> 1.0.1   pangoft2 >= 1.0.1) were not met:
>>
>> No package 'gail' found
>
> GAIL is now part of gtk2. Perhaps you need to upgrade the latter?
>
> - Josh


From blb at macports.org  Sun Dec 14 13:14:38 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 14 Dec 2008 14:14:38 -0700
Subject: Issues Upgrading Outdated Under 1.700
In-Reply-To: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>
References: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>
Message-ID: <20081214211438.GC489@ninagal.withay.com>

On Sun, Dec 14, 2008 at 01:15:51PM -0500, Tim Visher said:
> Hello Everyone,
> 
> So I upgraded to 1.700 this morning and that went totally fine.  Then,
> I proceeded to attempt to do a `sudo port upgrade outdated` (which
> I've never really had any success with in the past _either_) and I'm
> consistently failing.  I get to a line such as `--->  Deactivating
> db46 @4.6.21_1` and then the CPU cools down and it just stalls and
> sits there doing nothing.  I have no idea what's going on.
> 
> Any suggestions?

Try running it again with the debug switch:

$ sudo port -d upgrade outdated

That should point out more precisely where it's having an issue and should
also help track down why.

Bryan


> 
> -- 
> 
> In Christ,
> 
> Timmy V.
> 
> http://burningones.com/
> http://five.sentenc.es/ - Spend less time on e-mail

From jmr at macports.org  Sun Dec 14 13:14:53 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 15 Dec 2008 08:14:53 +1100
Subject: gnucash configure error (gnomecanvas)
In-Reply-To: <9A38C64E-8C29-4A76-8412-CC2DED4F07D6@dushin.net>
References: <24BF2C81-4525-485C-ADDC-38F969AD6AD5@dushin.net>
	<4945600D.6010006@macports.org>
	<9A38C64E-8C29-4A76-8412-CC2DED4F07D6@dushin.net>
Message-ID: <4945774D.9070806@macports.org>

Fred Dushin wrote:
> That worked, thanks.
> 
> I also needed to install both xorg-libXrandr and xorg-libXdamage to
> build gtk2.  There is a trac ticket for xorg-libXrandr
> (http://trac.macports.org/ticket/17360), but I don't know if there is
> one for the missing xorg-libXdamage dependency.

If you're using Leopard, it's actually a problem with some files that
Apple shipped referring to the wrong library:
<http://trac.macports.org/wiki/LeopardProblems#usrX11liblibXrandr.2.0.0.dylib:Nosuchfileordirectory>

> Should there be a trac ticket to capture the missing dependency from
> gnomecanvas to gtk2, as well?

The libgnomecanvas port does depend on gtk2. You already had gtk2
installed, so the dependency appeared to be satisfied. Unfortunately
it's not currently possible to specify a dependency on a particular version.

- Josh

From tim.visher at gmail.com  Sun Dec 14 13:56:08 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Sun, 14 Dec 2008 16:56:08 -0500
Subject: Issues Upgrading Outdated Under 1.700
In-Reply-To: <20081214211438.GC489@ninagal.withay.com>
References: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>
	<20081214211438.GC489@ninagal.withay.com>
Message-ID: <c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>

On Sun, Dec 14, 2008 at 4:14 PM, Bryan Blackburn <blb at macports.org> wrote:

> Try running it again with the debug switch:

`sudo port -d upgrade outdated`

It's been hung with no output for a solid hour.

[Full output](http://pastebin.com/m757f2865)

Thanks for the suggestion.

-- 

In Christ,

Timmy V.

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

From raimue at macports.org  Sun Dec 14 14:10:28 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Sun, 14 Dec 2008 23:10:28 +0100
Subject: Issues Upgrading Outdated Under 1.700
In-Reply-To: <c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>
References: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>	<20081214211438.GC489@ninagal.withay.com>
	<c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>
Message-ID: <49458454.9040302@macports.org>

Tim Visher wrote:
> `sudo port -d upgrade outdated`
> 
> It's been hung with no output for a solid hour.

I suppose it is hanging on a stale lock, as I have seen several such
reports on IRC (already with 1.6, this is not new). But I don't know the
reason for these locks. Probably force-exiting port using Ctrl-c during
activate/deactivate could leave this lock file around.

Check first if there is any other running instance of port:
  ps aux | grep port
If there is not, stop the running port instance first (Ctrl-c) and check
again - just to be sure.

Then check for the lock file:
  /opt/local/var/macports/receipts/dep_map.bz2.lock
If it is there, remove it.

After that, trying the previous command again should work.

HTH,
Rainer

From blb at macports.org  Sun Dec 14 14:19:58 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 14 Dec 2008 15:19:58 -0700
Subject: Issues Upgrading Outdated Under 1.700
In-Reply-To: <c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>
References: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>
	<20081214211438.GC489@ninagal.withay.com>
	<c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>
Message-ID: <20081214221958.GE489@ninagal.withay.com>

On Sun, Dec 14, 2008 at 04:56:08PM -0500, Tim Visher said:
> On Sun, Dec 14, 2008 at 4:14 PM, Bryan Blackburn <blb at macports.org> wrote:
> 
> > Try running it again with the debug switch:
> 
> `sudo port -d upgrade outdated`
> 
> It's been hung with no output for a solid hour.
> 
> [Full output](http://pastebin.com/m757f2865)

That is very strange indeed.  I just tried the same here (which did have
an outdated db46) and it deactivated/upgraded just fine.  The deactivating
phase for db46 shouldn't take but a few seconds.  If you open Console.app
(/Applications/Utilities) are there any interesting entries from around the
time of the hang beginning?

Bryan


> 
> Thanks for the suggestion.
> 
> -- 
> 
> In Christ,
> 
> Timmy V.
> 
> http://burningones.com/
> http://five.sentenc.es/ - Spend less time on e-mail

From David.Epstein at warwick.ac.uk  Sun Dec 14 15:32:22 2008
From: David.Epstein at warwick.ac.uk (David Epstein)
Date: Sun, 14 Dec 2008 15:32:22 -0800 (PST)
Subject: More than one version of a port installed.
Message-ID: <21006096.post@talk.nabble.com>


On doing port installed, I found many examples like this:
tcl @8.5.4_0
tcl @8.5.5_0 (active)

The first would not allow an uninstall because of dependencies. Is there
anyway to reasonably clean up the situation so that I end up with only one
version (the latest) of each port? But I suppose that wouldn't work because
some port may insist on a particular outdated version of a package it
depends on. So what's the best one can do in this direction with not too
much manual work?

By the way, I installed the most recent version of port, so any advice
should be in the light of that. I enjoyed the fact that port selfupdate no
longer produces large amounts of seemingly irrelevant output. Very nice and
clean. Thanks so much for all the work---much appreciated.
David

-- 
View this message in context: http://www.nabble.com/More-than-one-version-of-a-port-installed.-tp21006096p21006096.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From blb at macports.org  Sun Dec 14 15:46:40 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 14 Dec 2008 16:46:40 -0700
Subject: Issues Upgrading Outdated Under 1.700
In-Reply-To: <49458454.9040302@macports.org>
References: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>
	<20081214211438.GC489@ninagal.withay.com>
	<c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>
	<49458454.9040302@macports.org>
Message-ID: <20081214234640.GF489@ninagal.withay.com>

On Sun, Dec 14, 2008 at 11:10:28PM +0100, Rainer M?ller said:
> Tim Visher wrote:
> > `sudo port -d upgrade outdated`
> > 
> > It's been hung with no output for a solid hour.
> 
> I suppose it is hanging on a stale lock, as I have seen several such
> reports on IRC (already with 1.6, this is not new). But I don't know the
> reason for these locks. Probably force-exiting port using Ctrl-c during
> activate/deactivate could leave this lock file around.
> 
> Check first if there is any other running instance of port:
>   ps aux | grep port
> If there is not, stop the running port instance first (Ctrl-c) and check
> again - just to be sure.

Ah, the lock file; I hadn't thought about that because I was under the
(mistaken?) impression it would have kicked in earlier than deactivating the
port being upgraded.

Can we add the pid to that file at least, then port can test for the
existence of that pid and if not around, claim the lock for itself?

Bryan


> 
> Then check for the lock file:
>   /opt/local/var/macports/receipts/dep_map.bz2.lock
> If it is there, remove it.
> 
> After that, trying the previous command again should work.
> 
> HTH,
> Rainer

From jmr at macports.org  Sun Dec 14 15:47:17 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 15 Dec 2008 10:47:17 +1100
Subject: More than one version of a port installed.
In-Reply-To: <21006096.post@talk.nabble.com>
References: <21006096.post@talk.nabble.com>
Message-ID: <49459B05.2030701@macports.org>

David Epstein wrote:
> On doing port installed, I found many examples like this:
> tcl @8.5.4_0
> tcl @8.5.5_0 (active)
> 
> The first would not allow an uninstall because of dependencies. Is there
> anyway to reasonably clean up the situation so that I end up with only one
> version (the latest) of each port? But I suppose that wouldn't work because
> some port may insist on a particular outdated version of a package it
> depends on. So what's the best one can do in this direction with not too
> much manual work?

The incorrect complaining about dependents is fixed in MacPorts 1.7.
Ports can't currently depend on particular versions of other ports, so
you should be able to remove the old version with:

sudo port uninstall tcl @8.5.4_0

or, to remove all inactive versions:

sudo port uninstall inactive

- Josh

From blb at macports.org  Sun Dec 14 15:51:53 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 14 Dec 2008 16:51:53 -0700
Subject: More than one version of a port installed.
In-Reply-To: <21006096.post@talk.nabble.com>
References: <21006096.post@talk.nabble.com>
Message-ID: <20081214235153.GG489@ninagal.withay.com>

On Sun, Dec 14, 2008 at 03:32:22PM -0800, David Epstein said:
> 
> On doing port installed, I found many examples like this:
> tcl @8.5.4_0
> tcl @8.5.5_0 (active)
> 
> The first would not allow an uninstall because of dependencies. Is there
> anyway to reasonably clean up the situation so that I end up with only one
> version (the latest) of each port? But I suppose that wouldn't work because
> some port may insist on a particular outdated version of a package it
> depends on. So what's the best one can do in this direction with not too
> much manual work?

As of 1.7 uninstalling the inactive ports shouldn't complain about them
being needed as dependencies.  So using:

$ sudo port uninstall inactive

should clean out all the inactive ports; just make sure everything inactive
is stuff you don't need anymore or already has been upgraded.  You can use:

$ port installed inactive

to list just what's installed but inactive.  Otherwise you'll need to
specify exactly which needs to be uninstalled, using your tcl ports above:

$ sudo port uninstall tcl @8.5.4_0

Bryan


> 
> By the way, I installed the most recent version of port, so any advice
> should be in the light of that. I enjoyed the fact that port selfupdate no
> longer produces large amounts of seemingly irrelevant output. Very nice and
> clean. Thanks so much for all the work---much appreciated.
> David
> 

From David.Epstein at warwick.ac.uk  Sun Dec 14 16:05:37 2008
From: David.Epstein at warwick.ac.uk (David Epstein)
Date: Sun, 14 Dec 2008 16:05:37 -0800 (PST)
Subject: More than one version of a port installed.
In-Reply-To: <21006096.post@talk.nabble.com>
References: <21006096.post@talk.nabble.com>
Message-ID: <21006381.post@talk.nabble.com>




David Epstein wrote:
> 
> On doing port installed, I found many examples like this:
> tcl @8.5.4_0
> tcl @8.5.5_0 (active)
> 
> The first would not allow an uninstall because of dependencies. Is there
> anyway to reasonably clean up the situation so that I end up with only one
> version (the latest) of each port? But I suppose that wouldn't work
> because some port may insist on a particular outdated version of a package
> it depends on. So what's the best one can do in this direction with not
> too much manual work?
> 
> By the way, I installed the most recent version of port, so any advice
> should be in the light of that. I enjoyed the fact that port selfupdate no
> longer produces large amounts of seemingly irrelevant output. Very nice
> and clean. Thanks so much for all the work---much appreciated.
> David
> 
> 

I did further cleaning up of my Macports files, and these annoying
duplicates went away. So maybe my original question is a non-question, or
maybe the situation I described is occasionally possible.
David
-- 
View this message in context: http://www.nabble.com/More-than-one-version-of-a-port-installed.-tp21006096p21006381.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From David.Epstein at warwick.ac.uk  Sun Dec 14 16:12:31 2008
From: David.Epstein at warwick.ac.uk (David Epstein)
Date: Sun, 14 Dec 2008 16:12:31 -0800 (PST)
Subject: More than one version of a port installed.
In-Reply-To: <49459B05.2030701@macports.org>
References: <21006096.post@talk.nabble.com> <49459B05.2030701@macports.org>
Message-ID: <21006434.post@talk.nabble.com>




Joshua Root-8 wrote:
> 
> David Epstein wrote:
>> On doing port installed, I found many examples like this:
>> tcl @8.5.4_0
>> tcl @8.5.5_0 (active)
>> 
>> The first would not allow an uninstall because of dependencies. Is there
>> anyway to reasonably clean up the situation so that I end up with only
>> one
>> version (the latest) of each port? But I suppose that wouldn't work
>> because
>> some port may insist on a particular outdated version of a package it
>> depends on. So what's the best one can do in this direction with not too
>> much manual work?
> 
> The incorrect complaining about dependents is fixed in MacPorts 1.7.
> Ports can't currently depend on particular versions of other ports, so
> you should be able to remove the old version with:
> 
> sudo port uninstall tcl @8.5.4_0
> 
> or, to remove all inactive versions:
> 
> sudo port uninstall inactive
> 
> - Josh
> 

Great!! I wondered why I suddenly stopped getting those error messages.
Thanks again.
D
-- 
View this message in context: http://www.nabble.com/More-than-one-version-of-a-port-installed.-tp21006096p21006434.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From fred at dushin.net  Sun Dec 14 16:34:15 2008
From: fred at dushin.net (Fred Dushin)
Date: Sun, 14 Dec 2008 19:34:15 -0500
Subject: X11 checks in configure phase for some packages
Message-ID: <F01BFA5D-2718-4530-A123-6136E9DF65B0@dushin.net>

I've found a few ports that have had issues checking for X11 libraries  
and headers during configuration.  Hacking my way through the  
configure scripts, I've found lines in the checking of X11 libs like:

for ac_extension in a so sl; do

which of course works fine on Solaris, Linux, BSD, and HP/UX.   
Changing this to:

for ac_extension in a so sl dylib; do

fixes the configure phase, and the package then installs properly.

I found this lately with the start-notification package, and I'm  
wonder if I am doing something fundamentally wrong.  There have been  
others like this in the past, but I didn't take record of them.

   Model Name:	MacBook
   Model Identifier:	MacBook2,1
   System Version:	Mac OS X 10.5.5 (9F33)

 > port version
Version: 1.700

XQuartz 2.3.1

I also installed the X11SDK from the Leopard install disk, just to  
make sure.

From jeremyhu at macports.org  Sun Dec 14 16:53:47 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Sun, 14 Dec 2008 16:53:47 -0800
Subject: X11 checks in configure phase for some packages
In-Reply-To: <F01BFA5D-2718-4530-A123-6136E9DF65B0@dushin.net>
References: <F01BFA5D-2718-4530-A123-6136E9DF65B0@dushin.net>
Message-ID: <43C6E9D1-6217-4BF7-87FA-7DDAC6537E5D@macports.org>

That is fixed in autoconf-2.63.  The m4 macro you are referring to is  
AC_X_PATH.

If you see a port failing this, first check if it is REALLY failing.   
Some ports do AC_X_PATH followed by some PKG_CONFIG checks for X11  
(IMO, this itself is a bug since the PKG_CONFIG results are far  
superior to the AC_X_PATH results)... but none the less, make sure the  
port is actually failing to find X.  If it is misbehaving, you  
probably need to:

depends_build port:autoconf # and probably port:automake and  
port:libtool too
use_autoreconf yes

If that fails, you may need to do some autoreconf.env setting like:

autoreconf.env ACLOCAL="aclocal -I <some path the tarball stores m4  
macros>"

See the x11/lesstif port.  That one was particularly annoying.

Setting '--x-include=${x11prefix}/include --x-lib=${x11prefix}/lib' is  
not the best way to address that.

--Jeremy

On Dec 14, 2008, at 16:34, Fred Dushin wrote:

> I've found a few ports that have had issues checking for X11  
> libraries and headers during configuration.  Hacking my way through  
> the configure scripts, I've found lines in the checking of X11 libs  
> like:
>
> for ac_extension in a so sl; do
>
> which of course works fine on Solaris, Linux, BSD, and HP/UX.   
> Changing this to:
>
> for ac_extension in a so sl dylib; do
>
> fixes the configure phase, and the package then installs properly.
>
> I found this lately with the start-notification package, and I'm  
> wonder if I am doing something fundamentally wrong.  There have been  
> others like this in the past, but I didn't take record of them.
>
>  Model Name:	MacBook
>  Model Identifier:	MacBook2,1
>  System Version:	Mac OS X 10.5.5 (9F33)
>
> > port version
> Version: 1.700
>
> XQuartz 2.3.1
>
> I also installed the X11SDK from the Leopard install disk, just to  
> make sure.
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From jmr at macports.org  Sun Dec 14 17:05:14 2008
From: jmr at macports.org (Joshua Root)
Date: Mon, 15 Dec 2008 12:05:14 +1100
Subject: X11 checks in configure phase for some packages
In-Reply-To: <F01BFA5D-2718-4530-A123-6136E9DF65B0@dushin.net>
References: <F01BFA5D-2718-4530-A123-6136E9DF65B0@dushin.net>
Message-ID: <4945AD4A.8040501@macports.org>

Fred Dushin wrote:
> XQuartz 2.3.1
> 
> I also installed the X11SDK from the Leopard install disk, just to make
> sure.

I hope you didn't install the X11SDK after XQuartz. Maybe it's smart
enough not to, but it may have overwritten some of the XQuartz bits with
older versions.

- Josh

From fred at dushin.net  Sun Dec 14 17:34:34 2008
From: fred at dushin.net (Fred Dushin)
Date: Sun, 14 Dec 2008 20:34:34 -0500
Subject: X11 checks in configure phase for some packages
In-Reply-To: <4945AD4A.8040501@macports.org>
References: <F01BFA5D-2718-4530-A123-6136E9DF65B0@dushin.net>
	<4945AD4A.8040501@macports.org>
Message-ID: <112E62D6-D349-48DA-BC17-40BD24A0F5AF@dushin.net>

Yeah, I did :(

Should be okay, though.  I'll be moving up to 2.3.2 shortly, I hope :)

-F

On Dec 14, 2008, at 8:05 PM, Joshua Root wrote:

> Fred Dushin wrote:
>> XQuartz 2.3.1
>>
>> I also installed the X11SDK from the Leopard install disk, just to  
>> make
>> sure.
>
> I hope you didn't install the X11SDK after XQuartz. Maybe it's smart
> enough not to, but it may have overwritten some of the XQuartz bits  
> with
> older versions.
>
> - Josh


From jeremyhu at macports.org  Sun Dec 14 17:37:22 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Sun, 14 Dec 2008 17:37:22 -0800
Subject: X11 checks in configure phase for some packages
In-Reply-To: <112E62D6-D349-48DA-BC17-40BD24A0F5AF@dushin.net>
References: <F01BFA5D-2718-4530-A123-6136E9DF65B0@dushin.net>
	<4945AD4A.8040501@macports.org>
	<112E62D6-D349-48DA-BC17-40BD24A0F5AF@dushin.net>
Message-ID: <6FBD2686-83B2-460E-8906-E75D924BA64C@macports.org>

yeah, 2.3.2_rc3 is pretty good right now... I just want to try to get  
rid of the "white rectangle" issue before I release 2.3.2 final.

--Jeremy

On Dec 14, 2008, at 17:34, Fred Dushin wrote:

> Yeah, I did :(
>
> Should be okay, though.  I'll be moving up to 2.3.2 shortly, I hope :)
>
> -F
>
> On Dec 14, 2008, at 8:05 PM, Joshua Root wrote:
>
>> Fred Dushin wrote:
>>> XQuartz 2.3.1
>>>
>>> I also installed the X11SDK from the Leopard install disk, just to  
>>> make
>>> sure.
>>
>> I hope you didn't install the X11SDK after XQuartz. Maybe it's smart
>> enough not to, but it may have overwritten some of the XQuartz bits  
>> with
>> older versions.
>>
>> - Josh
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From David.Epstein at warwick.ac.uk  Sun Dec 14 23:06:36 2008
From: David.Epstein at warwick.ac.uk (David Epstein)
Date: Sun, 14 Dec 2008 23:06:36 -0800 (PST)
Subject: Error upgrading xrender on Panther
In-Reply-To: <478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
Message-ID: <21009181.post@talk.nabble.com>



Jeremy Huddleston-5 wrote:
> 
> Can you please see:
> http://trac.macports.org/ticket/17429#comment:
> I think if you pull in xorg-libX11 first, it'll be fine, but I need  
> someone to test that first...
> 

I just tried sudo port upgrade installed (I should have said outdated
instead of installed, but nothing seemed to go wrong) and I hit this xrender
problem. I looked at the conversation over the ticket, but didn't understand
much of it. Also, I was surprised to find that the bug report was closed,
because that would indicate to me that the problems with porting xrender
have been removed. But I am continuing to get exactly the same errors as
those originally reported. How should one interpret a "bug closed" message?

I run Mac Os X 10.4.11, so I should have changed the name of the thread from
Panther to Tiger, but I didn't know how to do that.

Could someone post advice on how to proceed, directed at uneducated users?
Thanks very much. I would have tried installing xorg-libX11, except that
Jeremy says, in the email I quote, that the solution is untested, and,
furthermore, the discussion on the ticket seems a little equivocal.
Furthermore, I saw the comment in that discussion that installing
xorg-libX11 brings in a lot of other stuff, so I don't want to do it, unless
it's necessary.
-- 
View this message in context: http://www.nabble.com/Error-upgrading-xrender-on-Panther-tp20758046p21009181.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From jeremyhu at macports.org  Mon Dec 15 00:12:25 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Mon, 15 Dec 2008 00:12:25 -0800
Subject: Error upgrading xrender on Panther
In-Reply-To: <21009181.post@talk.nabble.com>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
Message-ID: <AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>

The actual issue of that ticket is resolved meaning things are no more  
broken with xrender now than they were before (which means, they're  
still not too great).  If you sync, you should be able to install  
xrender without pulling in xorg-libX11 (assuming you can satisfy the  
lib:libX11.6 dependency some other way).

The problem lies in some sort of conflict when both /usr/X11R6/lib/ 
libX11.dylib and /opt/local/lib/libX11/dylib are linked to by your  
executable... so... yeah... my short term solution to offer you is  
either

1) use all macports for your X11 dependencies (maybe setting x11prefix  
to /opt/local in macports.conf will be enough... you should probably  
then install xorg-libX11 so you don't accidently pull in XFree86)

or

2) use none of the xorg-* ports in macports

Sorry I can't offer you a better solution right now.

On Dec 14, 2008, at 23:06, David Epstein wrote:

>
>
> Jeremy Huddleston-5 wrote:
>>
>> Can you please see:
>> http://trac.macports.org/ticket/17429#comment:
>> I think if you pull in xorg-libX11 first, it'll be fine, but I need
>> someone to test that first...
>>
>
> I just tried sudo port upgrade installed (I should have said outdated
> instead of installed, but nothing seemed to go wrong) and I hit this  
> xrender
> problem. I looked at the conversation over the ticket, but didn't  
> understand
> much of it. Also, I was surprised to find that the bug report was  
> closed,
> because that would indicate to me that the problems with porting  
> xrender
> have been removed. But I am continuing to get exactly the same  
> errors as
> those originally reported. How should one interpret a "bug closed"  
> message?
>
> I run Mac Os X 10.4.11, so I should have changed the name of the  
> thread from
> Panther to Tiger, but I didn't know how to do that.
>
> Could someone post advice on how to proceed, directed at uneducated  
> users?
> Thanks very much. I would have tried installing xorg-libX11, except  
> that
> Jeremy says, in the email I quote, that the solution is untested, and,
> furthermore, the discussion on the ticket seems a little equivocal.
> Furthermore, I saw the comment in that discussion that installing
> xorg-libX11 brings in a lot of other stuff, so I don't want to do  
> it, unless
> it's necessary.
> -- 
> View this message in context: http://www.nabble.com/Error-upgrading-xrender-on-Panther-tp20758046p21009181.html
> Sent from the MacPorts - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From devans at macports.org  Mon Dec 15 09:43:14 2008
From: devans at macports.org (David Evans)
Date: Mon, 15 Dec 2008 09:43:14 -0800
Subject: [Fwd: guile doesn't build for me]
Message-ID: <49469732.5000205@macports.org>


-------------- next part --------------
An embedded message was scrubbed...
From: james <derhindemith at googlemail.com>
Subject: guile doesn't build for me
Date: Mon, 15 Dec 2008 18:11:48 +0100
Size: 14656
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081215/fe7ae51f/attachment.eml>

From devans at macports.org  Mon Dec 15 10:15:17 2008
From: devans at macports.org (David Evans)
Date: Mon, 15 Dec 2008 10:15:17 -0800
Subject: guile doesn't build for me
In-Reply-To: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>
Message-ID: <49469EB5.9010004@macports.org>

james wrote:
> Hello, I don't know if this email will end up anywhere, but I'm trying
> anyway. Guile 1.8 or 1.6 do not build on my computer. I'm using osx
> 10.4.11. This is the output from the failed attempt:
> Thank you
>
> (I'm only copying this to devans at macports because the last change made
> was signed by him, I don't know if he has anything to do with guile)
>
>
> jamesebaileys-computer:/Users/jamesebailey/Downloads bigdaddy$ sudo
> /opt/local/bin/port clean guile
> --->  Cleaning guile
> jamesebaileys-computer:/Users/jamesebailey/Downloads bigdaddy$ sudo
> /opt/local/bin/port install guile
> --->  Fetching guile
> --->  Verifying checksum(s) for guile
> --->  Extracting guile
> --->  Applying patches to guile
> --->  Configuring guile
> --->  Building guile with target all
> Error: Target org.macports.build returned: shell command " cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/work/guile-1.8.5"
> && make all " returned error 2
> Command output: mv -f .deps/regex-posix.Tpo .deps/regex-posix.Plo
> /bin/sh ../libtool --tag=CC   --mode=link /usr/bin/gcc-4.0
> -I/opt/local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing-prototypes
> -Werror -lintl -Wl,-framework -Wl,CoreFoundation -version-info 19:0:2
> -export-dynamic -no-undefined -L/opt/local/lib -o libguile.la -rpath
> /opt/local/lib libguile_la-alist.lo libguile_la-arbiters.lo
> libguile_la-async.lo libguile_la-backtrace.lo libguile_la-boolean.lo
> libguile_la-chars.lo libguile_la-continuations.lo
> libguile_la-convert.lo libguile_la-debug.lo libguile_la-deprecation.lo
> libguile_la-deprecated.lo libguile_la-discouraged.lo
> libguile_la-dynwind.lo libguile_la-environments.lo libguile_la-eq.lo
> libguile_la-error.lo libguile_la-eval.lo libguile_la-evalext.lo
> libguile_la-extensions.lo libguile_la-feature.lo libguile_la-fluids.lo
> libguile_la-fports.lo libguile_la-futures.lo libguile_la-gc.lo
> libguile_la-gc-mark.lo libguile_la-gc-segment.lo
> libguile_la-gc-malloc.lo libguile_la-gc-card.lo
> libguile_la-gc-freelist.lo libguile_la-gc_os_dep.lo
> libguile_la-gdbint.lo libguile_la-gh_data.lo libguile_la-gh_eval.lo
> libguile_la-gh_funcs.lo libguile_la-gh_init.lo libguile_la-gh_io.lo
> libguile_la-gh_list.lo libguile_la-gh_predicates.lo
> libguile_la-goops.lo libguile_la-gsubr.lo libguile_la-guardians.lo
> libguile_la-hash.lo libguile_la-hashtab.lo libguile_la-hooks.lo
> libguile_la-i18n.lo libguile_la-init.lo libguile_la-inline.lo
> libguile_la-ioext.lo libguile_la-keywords.lo libguile_la-lang.lo
> libguile_la-list.lo libguile_la-load.lo libguile_la-macros.lo
> libguile_la-mallocs.lo libguile_la-modules.lo libguile_la-numbers.lo
> libguile_la-objects.lo libguile_la-objprop.lo libguile_la-options.lo
> libguile_la-pairs.lo libguile_la-ports.lo libguile_la-print.lo
> libguile_la-procprop.lo libguile_la-procs.lo libguile_la-properties.lo
> libguile_la-random.lo libguile_la-rdelim.lo libguile_la-read.lo
> libguile_la-root.lo libguile_la-rw.lo libguile_la-scmsigs.lo
> libguile_la-script.lo libguile_la-simpos.lo libguile_la-smob.lo
> libguile_la-sort.lo libguile_la-srcprop.lo libguile_la-stackchk.lo
> libguile_la-stacks.lo libguile_la-stime.lo libguile_la-strings.lo
> libguile_la-srfi-4.lo libguile_la-srfi-13.lo libguile_la-srfi-14.lo
> libguile_la-strorder.lo libguile_la-strports.lo libguile_la-struct.lo
> libguile_la-symbols.lo libguile_la-threads.lo
> libguile_la-null-threads.lo libguile_la-throw.lo libguile_la-values.lo
> libguile_la-variable.lo libguile_la-vectors.lo libguile_la-version.lo
> libguile_la-vports.lo libguile_la-weaks.lo libguile_la-ramap.lo
> libguile_la-unif.lo dynl.lo filesys.lo posix.lo net_db.lo socket.lo
> regex-posix.lo -lgmp -lm -lltdl
> /usr/bin/gcc-4.0 -dynamiclib  -o .libs/libguile.17.2.0.dylib 
> .libs/libguile_la-alist.o .libs/libguile_la-arbiters.o
> .libs/libguile_la-async.o .libs/libguile_la-backtrace.o
> .libs/libguile_la-boolean.o .libs/libguile_la-chars.o
> .libs/libguile_la-continuations.o .libs/libguile_la-convert.o
> .libs/libguile_la-debug.o .libs/libguile_la-deprecation.o
> .libs/libguile_la-deprecated.o .libs/libguile_la-discouraged.o
> .libs/libguile_la-dynwind.o .libs/libguile_la-environments.o
> .libs/libguile_la-eq.o .libs/libguile_la-error.o
> .libs/libguile_la-eval.o .libs/libguile_la-evalext.o
> .libs/libguile_la-extensions.o .libs/libguile_la-feature.o
> .libs/libguile_la-fluids.o .libs/libguile_la-fports.o
> .libs/libguile_la-futures.o .libs/libguile_la-gc.o
> .libs/libguile_la-gc-mark.o .libs/libguile_la-gc-segment.o
> .libs/libguile_la-gc-malloc.o .libs/libguile_la-gc-card.o
> .libs/libguile_la-gc-freelist.o .libs/libguile_la-gc_os_dep.o
> .libs/libguile_la-gdbint.o .libs/libguile_la-gh_data.o
> .libs/libguile_la-gh_eval.o .libs/libguile_la-gh_funcs.o
> .libs/libguile_la-gh_init.o .libs/libguile_la-gh_io.o
> .libs/libguile_la-gh_list.o .libs/libguile_la-gh_predicates.o
> .libs/libguile_la-goops.o .libs/libguile_la-gsubr.o
> .libs/libguile_la-guardians.o .libs/libguile_la-hash.o
> .libs/libguile_la-hashtab.o .libs/libguile_la-hooks.o
> .libs/libguile_la-i18n.o .libs/libguile_la-init.o
> .libs/libguile_la-inline.o .libs/libguile_la-ioext.o
> .libs/libguile_la-keywords.o .libs/libguile_la-lang.o
> .libs/libguile_la-list.o .libs/libguile_la-load.o
> .libs/libguile_la-macros.o .libs/libguile_la-mallocs.o
> .libs/libguile_la-modules.o .libs/libguile_la-numbers.o
> .libs/libguile_la-objects.o .libs/libguile_la-objprop.o
> .libs/libguile_la-options.o .libs/libguile_la-pairs.o
> .libs/libguile_la-ports.o .libs/libguile_la-print.o
> .libs/libguile_la-procprop.o .libs/libguile_la-procs.o
> .libs/libguile_la-properties.o .libs/libguile_la-random.o
> .libs/libguile_la-rdelim.o .libs/libguile_la-read.o
> .libs/libguile_la-root.o .libs/libguile_la-rw.o
> .libs/libguile_la-scmsigs.o .libs/libguile_la-script.o
> .libs/libguile_la-simpos.o .libs/libguile_la-smob.o
> .libs/libguile_la-sort.o .libs/libguile_la-srcprop.o
> .libs/libguile_la-stackchk.o .libs/libguile_la-stacks.o
> .libs/libguile_la-stime.o .libs/libguile_la-strings.o
> .libs/libguile_la-srfi-4.o .libs/libguile_la-srfi-13.o
> .libs/libguile_la-srfi-14.o .libs/libguile_la-strorder.o
> .libs/libguile_la-strports.o .libs/libguile_la-struct.o
> .libs/libguile_la-symbols.o .libs/libguile_la-threads.o
> .libs/libguile_la-null-threads.o .libs/libguile_la-throw.o
> .libs/libguile_la-values.o .libs/libguile_la-variable.o
> .libs/libguile_la-vectors.o .libs/libguile_la-version.o
> .libs/libguile_la-vports.o .libs/libguile_la-weaks.o
> .libs/libguile_la-ramap.o .libs/libguile_la-unif.o .libs/dynl.o
> .libs/filesys.o .libs/posix.o .libs/net_db.o .libs/socket.o
> .libs/regex-posix.o  -lintl -L/opt/local/lib
> /opt/local/lib/libgmp.dylib -lm -lltdl  -Wl,-framework
> -Wl,CoreFoundation -install_name  /opt/local/lib/libguile.17.dylib
> -compatibility_version 20 -current_version 20.0 -Wl,-single_module
> dsymutil .libs/libguile.17.2.0.dylib || :
> warning: no debug map in executable (-arch i386)
> (cd .libs && rm -f libguile.17.dylib && ln -s libguile.17.2.0.dylib
> libguile.17.dylib)
> (cd .libs && rm -f libguile.dylib && ln -s libguile.17.2.0.dylib
> libguile.dylib)
> ar cru .libs/libguile.a  libguile_la-alist.o libguile_la-arbiters.o
> libguile_la-async.o libguile_la-backtrace.o libguile_la-boolean.o
> libguile_la-chars.o libguile_la-continuations.o libguile_la-convert.o
> libguile_la-debug.o libguile_la-deprecation.o libguile_la-deprecated.o
> libguile_la-discouraged.o libguile_la-dynwind.o
> libguile_la-environments.o libguile_la-eq.o libguile_la-error.o
> libguile_la-eval.o libguile_la-evalext.o libguile_la-extensions.o
> libguile_la-feature.o libguile_la-fluids.o libguile_la-fports.o
> libguile_la-futures.o libguile_la-gc.o libguile_la-gc-mark.o
> libguile_la-gc-segment.o libguile_la-gc-malloc.o libguile_la-gc-card.o
> libguile_la-gc-freelist.o libguile_la-gc_os_dep.o libguile_la-gdbint.o
> libguile_la-gh_data.o libguile_la-gh_eval.o libguile_la-gh_funcs.o
> libguile_la-gh_init.o libguile_la-gh_io.o libguile_la-gh_list.o
> libguile_la-gh_predicates.o libguile_la-goops.o libguile_la-gsubr.o
> libguile_la-guardians.o libguile_la-hash.o libguile_la-hashtab.o
> libguile_la-hooks.o libguile_la-i18n.o libguile_la-init.o
> libguile_la-inline.o libguile_la-ioext.o libguile_la-keywords.o
> libguile_la-lang.o libguile_la-list.o libguile_la-load.o
> libguile_la-macros.o libguile_la-mallocs.o libguile_la-modules.o
> libguile_la-numbers.o libguile_la-objects.o libguile_la-objprop.o
> libguile_la-options.o libguile_la-pairs.o libguile_la-ports.o
> libguile_la-print.o libguile_la-procprop.o libguile_la-procs.o
> libguile_la-properties.o libguile_la-random.o libguile_la-rdelim.o
> libguile_la-read.o libguile_la-root.o libguile_la-rw.o
> libguile_la-scmsigs.o libguile_la-script.o libguile_la-simpos.o
> libguile_la-smob.o libguile_la-sort.o libguile_la-srcprop.o
> libguile_la-stackchk.o libguile_la-stacks.o libguile_la-stime.o
> libguile_la-strings.o libguile_la-srfi-4.o libguile_la-srfi-13.o
> libguile_la-srfi-14.o libguile_la-strorder.o libguile_la-strports.o
> libguile_la-struct.o libguile_la-symbols.o libguile_la-threads.o
> libguile_la-null-threads.o libguile_la-throw.o libguile_la-values.o
> libguile_la-variable.o libguile_la-vectors.o libguile_la-version.o
> libguile_la-vports.o libguile_la-weaks.o libguile_la-ramap.o
> libguile_la-unif.o dynl.o filesys.o posix.o net_db.o socket.o
> regex-posix.o
> ranlib: file: .libs/libguile.a(libguile_la-futures.o) has no symbols
> ranlib: file: .libs/libguile.a(libguile_la-null-threads.o) has no symbols
> ranlib .libs/libguile.a
> ranlib: file: .libs/libguile.a(libguile_la-futures.o) has no symbols
> ranlib: file: .libs/libguile.a(libguile_la-null-threads.o) has no symbols
> creating libguile.la
> (cd .libs && rm -f libguile.la && ln -s ../libguile.la libguile.la)
> /usr/bin/gcc-4.0 -DHAVE_CONFIG_H  -I.. -I.. -I..  -I/opt/local/include
> -I/opt/local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing-prototypes
> -Werror -MT guile-guile.o -MD -MP -MF .deps/guile-guile.Tpo -c -o
> guile-guile.o `test -f 'guile.c' || echo './'`guile.c
> mv -f .deps/guile-guile.Tpo .deps/guile-guile.Po
> /bin/sh ../libtool --tag=CC   --mode=link /usr/bin/gcc-4.0
> -I/opt/local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing-prototypes
> -Werror -dlpreopen force -I/opt/local/include -D_THREAD_SAFE 
> -L/opt/local/lib -o guile guile-guile.o libguile.la -lgmp -lm -lltdl
> rm -f .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
> creating .libs/guileS.c
> (cd .libs && /usr/bin/gcc-4.0  -O2 -c -fno-builtin "guileS.c")
> rm -f .libs/guileS.c .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
> /usr/bin/gcc-4.0 -I/opt/local/include -D_THREAD_SAFE -O2 -Wall
> -Wmissing-prototypes -Werror .libs/guileS.o -I/opt/local/include
> -D_THREAD_SAFE -o .libs/guile guile-guile.o  -L/opt/local/lib
> ./.libs/libguile.dylib -lintl /opt/local/lib/libgmp.dylib -lm -lltdl
> /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
> _lt__PROGRAM__LTX_preloaded_symbols
> collect2: ld returned 1 exit status
> make[3]: *** [guile] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> Error: Status 1 encountered during processing.
>
James --

I just tried building guile and it completed without error (also on
10.4.11 PPC).  Suggest you
make sure your ports are up to date by issuing

sudo port selfupdate
sudo port clean --all  guile

before trying again.  Is this an initial install or an update?

Dave

From asato at cae1.aero.org  Mon Dec 15 10:15:06 2008
From: asato at cae1.aero.org (Max Asato)
Date: Mon, 15 Dec 2008 10:15:06 -0800
Subject: Distfiles mirror behind proxy
In-Reply-To: <359241CF-00A1-42EB-98C9-58ADEA0A9568@macports.org>
References: <20081210004857.GB16414@cae1.aero.org>
	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
	<20081210184321.GA25989@cae1.aero.org>
	<49400F4D.7090805@macports.org>
	<20081211174100.GA7446@cae1.aero.org>
	<49415B37.3080000@macports.org>
	<359241CF-00A1-42EB-98C9-58ADEA0A9568@macports.org>
Message-ID: <20081215181506.GA28775@cae1.aero.org>

On Fri, Dec 12, 2008 at 12:05:16AM -0600, Ryan Schmidt wrote:
> 
> On Dec 11, 2008, at 12:25, Joshua Root wrote:
> 
> >Looks like you don't have the same Portfile on both machines. Have you
> >synced them both lately? What does 'port info glib2' say on each? I
> >suspect you'll find that they have a different version/revision.
> 
> I added the darwin_8 (and darwin_7) sections to the glib2 Portfile in  
> r42796 on November 30, 2008, because without them, the port would not  
> compile on MacPorts 1.6.0. I had not noticed this before because I  
> usually run MacPorts from trunk. I did not increase the version or  
> revision of the port because either the port had already built  
> successfully for you (because you were running MacPorts from trunk;  
> no need to force you to rebuild) or else the port did not build for  
> you (because you were running MacPorts 1.6.0; after this change, now  
> it will build for you).
> 
> So as Joshua said, you need to "sudo port sync" on both machines to  
> get the same ports trees.

Sorry about the delay in responding... long weekend for me.

You were right about the portfile.  I did the installs a day or two
apart.  The binary installations worked after doing a "port sync".

I suppose that this does leave the door open for a shared repository
of binary archives but I don't think that I can get away with a world
writable shared directory.  Are there any features in 1.7 that would
permit a read-only archive directory?

-Max

From frstan at bellsouth.net  Mon Dec 15 10:46:58 2008
From: frstan at bellsouth.net (William Davis)
Date: Mon, 15 Dec 2008 13:46:58 -0500
Subject: guile doesn't build for me
In-Reply-To: <49469EB5.9010004@macports.org>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>
	<49469EB5.9010004@macports.org>
Message-ID: <8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>


On Dec 15, 2008, at 1:15 PM, David Evans wrote:

> james wrote:
>> Hello, I don't know if this email will end up anywhere, but I'm  
>> trying
>> anyway. Guile 1.8 or 1.6 do not build on my computer. I'm using osx
>> 10.4.11. This is the output from the failed attempt:
>> Thank you
>>
>> (I'm only copying this to devans at macports because the last change  
>> made
>> was signed by him, I don't know if he has anything to do with guile)
>>
>>
>> jamesebaileys-computer:/Users/jamesebailey/Downloads bigdaddy$ sudo
>> /opt/local/bin/port clean guile
>> --->  Cleaning guile
>> jamesebaileys-computer:/Users/jamesebailey/Downloads bigdaddy$ sudo
>> /opt/local/bin/port install guile
>> --->  Fetching guile
>>
>>
>> Error: Status 1 encountered during processing.
>>
> James --
>
> I just tried building guile and it completed without error (also on
> 10.4.11 PPC).  Suggest you
> make sure your ports are up to date by issuing
>
> sudo port selfupdate
> sudo port clean --all  guile
>
> before trying again.  Is this an initial install or an update?
>
> Dave


Given the way you gave the port command:
>> bigdaddy$ sudo
>> /opt/local/bin/port clean guile

I wonder if the bug in macports 1.6 install that failed to setup the  
macports path in your ~.profile has bitten you. if so this bug (and  
many others) is fixed in macports 1.7.  I suggest you download that.   
Im not sure that sudo port selfupdate will run correctly if your PATH  
is not correctly set.
William Davis
frstanATbellsouthDOTnet
Mac OS X.5.5 Darwin 9.5.0
XQuartz 2.3.2_rc3 (xorg-server 1.4.2-apple27)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non


From frstan at bellsouth.net  Mon Dec 15 11:06:46 2008
From: frstan at bellsouth.net (William Davis)
Date: Mon, 15 Dec 2008 14:06:46 -0500
Subject: Distfiles mirror behind proxy
In-Reply-To: <20081215181506.GA28775@cae1.aero.org>
References: <20081210004857.GB16414@cae1.aero.org>
	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
	<20081210184321.GA25989@cae1.aero.org>
	<49400F4D.7090805@macports.org>
	<20081211174100.GA7446@cae1.aero.org>
	<49415B37.3080000@macports.org>
	<359241CF-00A1-42EB-98C9-58ADEA0A9568@macports.org>
	<20081215181506.GA28775@cae1.aero.org>
Message-ID: <E1E23A4C-EF00-499B-B7D9-71BFE4A2DA55@bellsouth.net>


On Dec 15, 2008, at 1:15 PM, Max Asato wrote:

> On Fri, Dec 12, 2008 at 12:05:16AM -0600, Ryan Schmidt wrote:
>>
>> On Dec 11, 2008, at 12:25, Joshua Root wrote:
>>
>>> Looks like you don't have the same Portfile on both machines. Have  
>>> you
>>> synced them both lately? What does 'port info glib2' say on each? I
>>> suspect you'll find that they have a different version/revision.
>>
>> I added the darwin_8 (and darwin_7) sections to the glib2 Portfile in
>> r42796 on November 30, 2008, because without them, the port would not
>> compile on MacPorts 1.6.0. I had not noticed this before because I
>> usually run MacPorts from trunk. I did not increase the version or
>> revision of the port because either the port had already built
>> successfully for you (because you were running MacPorts from trunk;
>> no need to force you to rebuild) or else the port did not build for
>> you (because you were running MacPorts 1.6.0; after this change, now
>> it will build for you).
>>
>> So as Joshua said, you need to "sudo port sync" on both machines to
>> get the same ports trees.
>
> Sorry about the delay in responding... long weekend for me.
>
> You were right about the portfile.  I did the installs a day or two
> apart.  The binary installations worked after doing a "port sync".
>
> I suppose that this does leave the door open for a shared repository
> of binary archives but I don't think that I can get away with a world
> writable shared directory.  Are there any features in 1.7 that would
> permit a read-only archive directory?
>
> -Max
>

see man 5 macport.conf
portarchivepath
          Location where to store/retrieve ports binary archive files  
from when archive mode is active.
          Default: ${portdbpath}/packages
This variable can be set in each users macport.conf file to point to  
some network readonly dir as far as I know.

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

Mundus vult decepi, ego non


From trog24 at comcast.net  Mon Dec 15 11:19:52 2008
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Mon, 15 Dec 2008 11:19:52 -0800
Subject: Error upgrading xrender on Panther
In-Reply-To: <AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
Message-ID: <AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>

Hello,
	i am get the following error many times (4) when trying to execute  
"sudo port upgrade installed":

--->  Building xrender
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_xre 
nder/work/libXrender-0.9.4" && make all " returned error 2
Command output: make  all-recursive
Making all in src
/bin/sh ../libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0 - 
DHAVE_CONFIG_H -I. -I..   -I/opt/local/include -I/opt/local/include - 
I/opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/ 
xrender/files/include -I/opt/local/include   -I/usr/X11R6/include - 
DXTHREADS -I.. -I../include/X11/extensions  -O2 -MT Picture.lo -MD - 
MP -MF .deps/Picture.Tpo -c -o Picture.lo Picture.c
  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I.. -I/opt/local/include -I/ 
opt/local/include -I/opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/x11/xrender/files/include -I/opt/ 
local/include -I/usr/X11R6/include -DXTHREADS -I.. -I../include/X11/ 
extensions -O2 -MT Picture.lo -MD -MP -MF .deps/Picture.Tpo -c  
Picture.c  -fno-common -DPIC -o .libs/Picture.o
Picture.c:29:25: error: X11/Xregion.h: No such file or directory
Picture.c: In function 'XRenderSetPictureClipRegion':
Picture.c:177: error: 'BOX' undeclared (first use in this function)
Picture.c:177: error: (Each undeclared identifier is reported only once
Picture.c:177: error: for each function it appears in.)
Picture.c:177: error: 'pb' undeclared (first use in this function)
Picture.c:182: error: dereferencing pointer to incomplete type
Picture.c:184: error: dereferencing pointer to incomplete type
Picture.c:184: error: dereferencing pointer to incomplete type
Picture.c:191: error: dereferencing pointer to incomplete type
Picture.c:193: error: dereferencing pointer to incomplete type
make[2]: *** [Picture.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Error: Unable to upgrade port: 1

There is no /opt/local/lib/libX11/dylib on my system; but, Apple's  
X11R6 is installed in /usr.  The file Xrender.h is in /opt/local/ 
include/extensions.  I notice in the -I path designation for the  
extensions is -I../include/extensions instead of /opt/local/include/ 
extensions.  This is different from the other -I designations where / 
opt/local precedes the directory.  This could be a problem if the  
working directory is not ../ relative away from the include/ 
extensions directory.
Frank

On Dec 15, 2008, at 12:12 AM, Jeremy Huddleston wrote:

> The actual issue of that ticket is resolved meaning things are no  
> more broken with xrender now than they were before (which means,  
> they're still not too great).  If you sync, you should be able to  
> install xrender without pulling in xorg-libX11 (assuming you can  
> satisfy the lib:libX11.6 dependency some other way).
>
> The problem lies in some sort of conflict when both /usr/X11R6/lib/ 
> libX11.dylib and /opt/local/lib/libX11/dylib are linked to by your  
> executable... so... yeah... my short term solution to offer you is  
> either
>
> 1) use all macports for your X11 dependencies (maybe setting  
> x11prefix to /opt/local in macports.conf will be enough... you  
> should probably then install xorg-libX11 so you don't accidently  
> pull in XFree86)
>
> or
>
> 2) use none of the xorg-* ports in macports
>
> Sorry I can't offer you a better solution right now.
>
> On Dec 14, 2008, at 23:06, David Epstein wrote:
>
>>
>>
>> Jeremy Huddleston-5 wrote:
>>>
>>> Can you please see:
>>> http://trac.macports.org/ticket/17429#comment:
>>> I think if you pull in xorg-libX11 first, it'll be fine, but I need
>>> someone to test that first...
>>>
>>
>> I just tried sudo port upgrade installed (I should have said outdated
>> instead of installed, but nothing seemed to go wrong) and I hit  
>> this xrender
>> problem. I looked at the conversation over the ticket, but didn't  
>> understand
>> much of it. Also, I was surprised to find that the bug report was  
>> closed,
>> because that would indicate to me that the problems with porting  
>> xrender
>> have been removed. But I am continuing to get exactly the same  
>> errors as
>> those originally reported. How should one interpret a "bug closed"  
>> message?
>>
>> I run Mac Os X 10.4.11, so I should have changed the name of the  
>> thread from
>> Panther to Tiger, but I didn't know how to do that.
>>
>> Could someone post advice on how to proceed, directed at  
>> uneducated users?
>> Thanks very much. I would have tried installing xorg-libX11,  
>> except that
>> Jeremy says, in the email I quote, that the solution is untested,  
>> and,
>> furthermore, the discussion on the ticket seems a little equivocal.
>> Furthermore, I saw the comment in that discussion that installing
>> xorg-libX11 brings in a lot of other stuff, so I don't want to do  
>> it, unless
>> it's necessary.
>> -- 
>> View this message in context: http://www.nabble.com/Error- 
>> upgrading-xrender-on-Panther-tp20758046p21009181.html
>> Sent from the MacPorts - Users mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From devans at macports.org  Mon Dec 15 11:39:00 2008
From: devans at macports.org (David Evans)
Date: Mon, 15 Dec 2008 11:39:00 -0800
Subject: guile doesn't build for me
In-Reply-To: <8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>
	<49469EB5.9010004@macports.org>
	<8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>
Message-ID: <4946B254.8040606@macports.org>

William Davis wrote:
> Given the way you gave the port command:
>>> bigdaddy$ sudo
>>> /opt/local/bin/port clean guile
>
> I wonder if the bug in macports 1.6 install that failed to setup the
> macports path in your ~.profile has bitten you. if so this bug (and
> many others) is fixed in macports 1.7.  I suggest you download that. 
> Im not sure that sudo port selfupdate will run correctly if your PATH
> is not correctly set.
> William Davis
Yes, updating to MacPorts 1.7.0 is a good idea for everyone.

Have just updated guile to version 1.8.6 in r43824.  Perhaps this will help.

Dave

From christopher.rob.jones at cern.ch  Mon Dec 15 11:40:24 2008
From: christopher.rob.jones at cern.ch (Chris Jones)
Date: Mon, 15 Dec 2008 19:40:24 +0000
Subject: KDE4 applications need X11 ?
Message-ID: <67DD9ACD-45F8-4ABD-9F8B-D41B0051AB28@cern.ch>

Hi,

OK, I've been experimenting with building the KDE4 ports over the last  
few days. I'm new to macports so bear with me, but I'm having some  
issues.

I finally managed to get kdebase4 built, which gives some basic  
applications like kwrite, konqueror. However, each time I start these  
they trigger X11 to start ! I thought these where suppose to be using  
QT4-mac, which is OSX native, but it seems some X11 dependency is  
sneaking in. The apps do seem to be aqua though. After starting they  
seem to hang (after triggering X11 to start) but if I kill X11 off  
they sometimes come up (kinda off, all icons are messing and most  
things don't work).

Its clear I haven't done something correct here, either or the KDE4  
ports are simply well broken at the moment (I know they are  
experimental). I thought I had perhaps accidentally built them with  
X11 enabled somehow, so I went back through and rebuilt explicitly  
disabling X11, following the suggestions here

http://techbase.kde.org/Projects/KDE_on_Mac_OS_X/Macbook_Manifesto

but no luck.

Has anyone out there built the KDE4 ports successfully ?

One thing I had to do was use gcc 4.2 for kdelibs4 - I wasn't sure  
whether I should then use gcc 4.2 for all other KDE4 ports, or go back  
to gcc 4.0 for them. I tried using gcc 4.2...

cheers Chris

From trog24 at comcast.net  Mon Dec 15 11:43:04 2008
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Mon, 15 Dec 2008 11:43:04 -0800
Subject: Error upgrading xrender on Panther
In-Reply-To: <AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
Message-ID: <7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>

Hello,
	MacPorts 1.700 got caught in an infinite loop in trying to upgrade  
xrender.  12 attempts were made before I terminated the loop with a  
control C.  Each attempt had the same failure as the preceding email,  
namely:

Error: Unable to upgrade port: 1
--->  Building xrender
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_xre 
nder/work/libXrender-0.9.4" && make all " returned error 2
Command output: make  all-recursive
Making all in src
/bin/sh ../libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0 - 
DHAVE_CONFIG_H -I. -I..   -I/opt/local/include -I/opt/local/include - 
I/opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/ 
xrender/files/include -I/opt/local/include   -I/usr/X11R6/include - 
DXTHREADS -I.. -I../include/X11/extensions  -O2 -MT Picture.lo -MD - 
MP -MF .deps/Picture.Tpo -c -o Picture.lo Picture.c
  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I.. -I/opt/local/include -I/ 
opt/local/include -I/opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/x11/xrender/files/include -I/opt/ 
local/include -I/usr/X11R6/include -DXTHREADS -I.. -I../include/X11/ 
extensions -O2 -MT Picture.lo -MD -MP -MF .deps/Picture.Tpo -c  
Picture.c  -fno-common -DPIC -o .libs/Picture.o
Picture.c:29:25: error: X11/Xregion.h: No such file or directory
Picture.c: In function 'XRenderSetPictureClipRegion':
Picture.c:177: error: 'BOX' undeclared (first use in this function)
Picture.c:177: error: (Each undeclared identifier is reported only once
Picture.c:177: error: for each function it appears in.)
Picture.c:177: error: 'pb' undeclared (first use in this function)
Picture.c:182: error: dereferencing pointer to incomplete type
Picture.c:184: error: dereferencing pointer to incomplete type
Picture.c:184: error: dereferencing pointer to incomplete type
Picture.c:191: error: dereferencing pointer to incomplete type
Picture.c:193: error: dereferencing pointer to incomplete type
make[2]: *** [Picture.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Frank

On Dec 15, 2008, at 11:19 AM, Frank J. R. Hanstick wrote:

> Hello,
> 	i am get the following error many times (4) when trying to execute  
> "sudo port upgrade installed":
>
> --->  Building xrender
> Error: Target org.macports.build returned: shell command " cd "/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_x 
> render/work/libXrender-0.9.4" && make all " returned error 2
> Command output: make  all-recursive
> Making all in src
> /bin/sh ../libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0 - 
> DHAVE_CONFIG_H -I. -I..   -I/opt/local/include -I/opt/local/include  
> -I/opt/local/var/macports/sources/rsync.macports.org/release/ports/ 
> x11/xrender/files/include -I/opt/local/include   -I/usr/X11R6/ 
> include -DXTHREADS -I.. -I../include/X11/extensions  -O2 -MT  
> Picture.lo -MD -MP -MF .deps/Picture.Tpo -c -o Picture.lo Picture.c
>  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I.. -I/opt/local/include -I/ 
> opt/local/include -I/opt/local/var/macports/sources/ 
> rsync.macports.org/release/ports/x11/xrender/files/include -I/opt/ 
> local/include -I/usr/X11R6/include -DXTHREADS -I.. -I../include/X11/ 
> extensions -O2 -MT Picture.lo -MD -MP -MF .deps/Picture.Tpo -c  
> Picture.c  -fno-common -DPIC -o .libs/Picture.o
> Picture.c:29:25: error: X11/Xregion.h: No such file or directory
> Picture.c: In function 'XRenderSetPictureClipRegion':
> Picture.c:177: error: 'BOX' undeclared (first use in this function)
> Picture.c:177: error: (Each undeclared identifier is reported only  
> once
> Picture.c:177: error: for each function it appears in.)
> Picture.c:177: error: 'pb' undeclared (first use in this function)
> Picture.c:182: error: dereferencing pointer to incomplete type
> Picture.c:184: error: dereferencing pointer to incomplete type
> Picture.c:184: error: dereferencing pointer to incomplete type
> Picture.c:191: error: dereferencing pointer to incomplete type
> Picture.c:193: error: dereferencing pointer to incomplete type
> make[2]: *** [Picture.lo] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> Error: Unable to upgrade port: 1
>
> There is no /opt/local/lib/libX11/dylib on my system; but, Apple's  
> X11R6 is installed in /usr.  The file Xrender.h is in /opt/local/ 
> include/extensions.  I notice in the -I path designation for the  
> extensions is -I../include/extensions instead of /opt/local/include/ 
> extensions.  This is different from the other -I designations  
> where /opt/local precedes the directory.  This could be a problem  
> if the working directory is not ../ relative away from the include/ 
> extensions directory.
> Frank
>
> On Dec 15, 2008, at 12:12 AM, Jeremy Huddleston wrote:
>
>> The actual issue of that ticket is resolved meaning things are no  
>> more broken with xrender now than they were before (which means,  
>> they're still not too great).  If you sync, you should be able to  
>> install xrender without pulling in xorg-libX11 (assuming you can  
>> satisfy the lib:libX11.6 dependency some other way).
>>
>> The problem lies in some sort of conflict when both /usr/X11R6/lib/ 
>> libX11.dylib and /opt/local/lib/libX11/dylib are linked to by your  
>> executable... so... yeah... my short term solution to offer you is  
>> either
>>
>> 1) use all macports for your X11 dependencies (maybe setting  
>> x11prefix to /opt/local in macports.conf will be enough... you  
>> should probably then install xorg-libX11 so you don't accidently  
>> pull in XFree86)
>>
>> or
>>
>> 2) use none of the xorg-* ports in macports
>>
>> Sorry I can't offer you a better solution right now.
>>
>> On Dec 14, 2008, at 23:06, David Epstein wrote:
>>
>>>
>>>
>>> Jeremy Huddleston-5 wrote:
>>>>
>>>> Can you please see:
>>>> http://trac.macports.org/ticket/17429#comment:
>>>> I think if you pull in xorg-libX11 first, it'll be fine, but I need
>>>> someone to test that first...
>>>>
>>>
>>> I just tried sudo port upgrade installed (I should have said  
>>> outdated
>>> instead of installed, but nothing seemed to go wrong) and I hit  
>>> this xrender
>>> problem. I looked at the conversation over the ticket, but didn't  
>>> understand
>>> much of it. Also, I was surprised to find that the bug report was  
>>> closed,
>>> because that would indicate to me that the problems with porting  
>>> xrender
>>> have been removed. But I am continuing to get exactly the same  
>>> errors as
>>> those originally reported. How should one interpret a "bug  
>>> closed" message?
>>>
>>> I run Mac Os X 10.4.11, so I should have changed the name of the  
>>> thread from
>>> Panther to Tiger, but I didn't know how to do that.
>>>
>>> Could someone post advice on how to proceed, directed at  
>>> uneducated users?
>>> Thanks very much. I would have tried installing xorg-libX11,  
>>> except that
>>> Jeremy says, in the email I quote, that the solution is untested,  
>>> and,
>>> furthermore, the discussion on the ticket seems a little equivocal.
>>> Furthermore, I saw the comment in that discussion that installing
>>> xorg-libX11 brings in a lot of other stuff, so I don't want to do  
>>> it, unless
>>> it's necessary.
>>> -- 
>>> View this message in context: http://www.nabble.com/Error- 
>>> upgrading-xrender-on-Panther-tp20758046p21009181.html
>>> Sent from the MacPorts - Users mailing list archive at Nabble.com.
>>>
>>> _______________________________________________
>>> macports-users mailing list
>>> macports-users at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>
>> _______________________________________________
>> 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 jmr at macports.org  Mon Dec 15 12:08:20 2008
From: jmr at macports.org (Joshua Root)
Date: Tue, 16 Dec 2008 07:08:20 +1100
Subject: Error upgrading xrender on Panther
In-Reply-To: <7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>	<21009181.post@talk.nabble.com>	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
Message-ID: <4946B934.2040700@macports.org>

Frank J. R. Hanstick wrote:
> Hello,
>     MacPorts 1.700 got caught in an infinite loop in trying to upgrade
> xrender.  12 attempts were made before I terminated the loop with a
> control C.

This sounds kind of like <http://trac.macports.org/ticket/14829>. What
was the command line you used? I'd be interested in seeing debug output
for this.

- Josh

From derhindemith at googlemail.com  Mon Dec 15 12:23:38 2008
From: derhindemith at googlemail.com (James E. Bailey)
Date: Mon, 15 Dec 2008 21:23:38 +0100
Subject: guile doesn't build for me
In-Reply-To: <4946B254.8040606@macports.org>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>
	<49469EB5.9010004@macports.org>
	<8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>
	<4946B254.8040606@macports.org>
Message-ID: <7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>


Am 15.12.2008 um 20:39 schrieb David Evans:

> William Davis wrote:
>> Given the way you gave the port command:
>>>> bigdaddy$ sudo
>>>> /opt/local/bin/port clean guile
>>
>> I wonder if the bug in macports 1.6 install that failed to setup the
>> macports path in your ~.profile has bitten you. if so this bug (and
>> many others) is fixed in macports 1.7.  I suggest you download that.
>> Im not sure that sudo port selfupdate will run correctly if your PATH
>> is not correctly set.
>> William Davis
> Yes, updating to MacPorts 1.7.0 is a good idea for everyone.
>
> Have just updated guile to version 1.8.6 in r43824.  Perhaps this  
> will help.
>

Thanks for all the help, everyone. I've updated macports to 1.7, and  
I still can't build guile. It's using the updated 1.8.6 version, and  
the output follows. The reason for the path is because my normal user  
account isn't an admin account, and I haven't bothered adding the  
macports path to the admin accounts' $PATH, so I just specify it  
manually.

jamesebaileys-computer:/Users/jamesebailey/Downloads bigdaddy$ sudo / 
opt/local/bin/port selfupdate

MacPorts base version 1.600 installed

Downloaded MacPorts base version 1.700
Configuring, Building and Installing new MacPorts base
selfupdate done!

21:07:27 bigdaddy Downloads:sudo /opt/local/bin/port clean --all guile
--->  Cleaning guile
21:07:35 bigdaddy Downloads:sudo /opt/local/bin/port install guile
--->  Fetching guile
--->  Attempting to fetch guile-1.8.5.tar.gz from http:// 
trd.no.distfiles.macports.org/guile
--->  Verifying checksum(s) for guile
--->  Extracting guile
--->  Applying patches to guile
--->  Configuring guile
--->  Building guile
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gu 
ile/work/guile-1.8.5" && make all " returned error 2
Command output: mv -f .deps/regex-posix.Tpo .deps/regex-posix.Plo
/bin/sh ../libtool --tag=CC   --mode=link /usr/bin/gcc-4.0 -I/opt/ 
local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing-prototypes -Werror - 
lintl -Wl,-framework -Wl,CoreFoundation -version-info 19:0:2 -export- 
dynamic -no-undefined -L/opt/local/lib -o libguile.la -rpath /opt/ 
local/lib libguile_la-alist.lo libguile_la-arbiters.lo libguile_la- 
async.lo libguile_la-backtrace.lo libguile_la-boolean.lo libguile_la- 
chars.lo libguile_la-continuations.lo libguile_la-convert.lo  
libguile_la-debug.lo libguile_la-deprecation.lo libguile_la- 
deprecated.lo libguile_la-discouraged.lo libguile_la-dynwind.lo  
libguile_la-environments.lo libguile_la-eq.lo libguile_la-error.lo  
libguile_la-eval.lo libguile_la-evalext.lo libguile_la-extensions.lo  
libguile_la-feature.lo libguile_la-fluids.lo libguile_la-fports.lo  
libguile_la-futures.lo libguile_la-gc.lo libguile_la-gc-mark.lo  
libguile_la-gc-segment.lo libguile_la-gc-malloc.lo libguile_la-gc- 
card.lo libguile_la-gc-freelist.lo libguile_la-gc_os_dep.lo  
libguile_la-gdbint.lo libguile_la-gh_data.lo libguile_la-gh_eval.lo  
libguile_la-gh_funcs.lo libguile_la-gh_init.lo libguile_la-gh_io.lo  
libguile_la-gh_list.lo libguile_la-gh_predicates.lo libguile_la- 
goops.lo libguile_la-gsubr.lo libguile_la-guardians.lo libguile_la- 
hash.lo libguile_la-hashtab.lo libguile_la-hooks.lo libguile_la- 
i18n.lo libguile_la-init.lo libguile_la-inline.lo libguile_la- 
ioext.lo libguile_la-keywords.lo libguile_la-lang.lo libguile_la- 
list.lo libguile_la-load.lo libguile_la-macros.lo libguile_la- 
mallocs.lo libguile_la-modules.lo libguile_la-numbers.lo libguile_la- 
objects.lo libguile_la-objprop.lo libguile_la-options.lo libguile_la- 
pairs.lo libguile_la-ports.lo libguile_la-print.lo libguile_la- 
procprop.lo libguile_la-procs.lo libguile_la-properties.lo  
libguile_la-random.lo libguile_la-rdelim.lo libguile_la-read.lo  
libguile_la-root.lo libguile_la-rw.lo libguile_la-scmsigs.lo  
libguile_la-script.lo libguile_la-simpos.lo libguile_la-smob.lo  
libguile_la-sort.lo libguile_la-srcprop.lo libguile_la-stackchk.lo  
libguile_la-stacks.lo libguile_la-stime.lo libguile_la-strings.lo  
libguile_la-srfi-4.lo libguile_la-srfi-13.lo libguile_la-srfi-14.lo  
libguile_la-strorder.lo libguile_la-strports.lo libguile_la-struct.lo  
libguile_la-symbols.lo libguile_la-threads.lo libguile_la-null- 
threads.lo libguile_la-throw.lo libguile_la-values.lo libguile_la- 
variable.lo libguile_la-vectors.lo libguile_la-version.lo libguile_la- 
vports.lo libguile_la-weaks.lo libguile_la-ramap.lo libguile_la- 
unif.lo dynl.lo filesys.lo posix.lo net_db.lo socket.lo regex- 
posix.lo -lgmp -lm -lltdl
/usr/bin/gcc-4.0 -dynamiclib  -o .libs/libguile.17.2.0.dylib  .libs/ 
libguile_la-alist.o .libs/libguile_la-arbiters.o .libs/libguile_la- 
async.o .libs/libguile_la-backtrace.o .libs/libguile_la- 
boolean.o .libs/libguile_la-chars.o .libs/libguile_la- 
continuations.o .libs/libguile_la-convert.o .libs/libguile_la- 
debug.o .libs/libguile_la-deprecation.o .libs/libguile_la- 
deprecated.o .libs/libguile_la-discouraged.o .libs/libguile_la- 
dynwind.o .libs/libguile_la-environments.o .libs/libguile_la- 
eq.o .libs/libguile_la-error.o .libs/libguile_la-eval.o .libs/ 
libguile_la-evalext.o .libs/libguile_la-extensions.o .libs/ 
libguile_la-feature.o .libs/libguile_la-fluids.o .libs/libguile_la- 
fports.o .libs/libguile_la-futures.o .libs/libguile_la-gc.o .libs/ 
libguile_la-gc-mark.o .libs/libguile_la-gc-segment.o .libs/ 
libguile_la-gc-malloc.o .libs/libguile_la-gc-card.o .libs/libguile_la- 
gc-freelist.o .libs/libguile_la-gc_os_dep.o .libs/libguile_la- 
gdbint.o .libs/libguile_la-gh_data.o .libs/libguile_la- 
gh_eval.o .libs/libguile_la-gh_funcs.o .libs/libguile_la- 
gh_init.o .libs/libguile_la-gh_io.o .libs/libguile_la-gh_list.o .libs/ 
libguile_la-gh_predicates.o .libs/libguile_la-goops.o .libs/ 
libguile_la-gsubr.o .libs/libguile_la-guardians.o .libs/libguile_la- 
hash.o .libs/libguile_la-hashtab.o .libs/libguile_la-hooks.o .libs/ 
libguile_la-i18n.o .libs/libguile_la-init.o .libs/libguile_la- 
inline.o .libs/libguile_la-ioext.o .libs/libguile_la-keywords.o .libs/ 
libguile_la-lang.o .libs/libguile_la-list.o .libs/libguile_la- 
load.o .libs/libguile_la-macros.o .libs/libguile_la-mallocs.o .libs/ 
libguile_la-modules.o .libs/libguile_la-numbers.o .libs/libguile_la- 
objects.o .libs/libguile_la-objprop.o .libs/libguile_la- 
options.o .libs/libguile_la-pairs.o .libs/libguile_la-ports.o .libs/ 
libguile_la-print.o .libs/libguile_la-procprop.o .libs/libguile_la- 
procs.o .libs/libguile_la-properties.o .libs/libguile_la- 
random.o .libs/libguile_la-rdelim.o .libs/libguile_la-read.o .libs/ 
libguile_la-root.o .libs/libguile_la-rw.o .libs/libguile_la- 
scmsigs.o .libs/libguile_la-script.o .libs/libguile_la-simpos.o .libs/ 
libguile_la-smob.o .libs/libguile_la-sort.o .libs/libguile_la- 
srcprop.o .libs/libguile_la-stackchk.o .libs/libguile_la- 
stacks.o .libs/libguile_la-stime.o .libs/libguile_la-strings.o .libs/ 
libguile_la-srfi-4.o .libs/libguile_la-srfi-13.o .libs/libguile_la- 
srfi-14.o .libs/libguile_la-strorder.o .libs/libguile_la- 
strports.o .libs/libguile_la-struct.o .libs/libguile_la- 
symbols.o .libs/libguile_la-threads.o .libs/libguile_la-null- 
threads.o .libs/libguile_la-throw.o .libs/libguile_la-values.o .libs/ 
libguile_la-variable.o .libs/libguile_la-vectors.o .libs/libguile_la- 
version.o .libs/libguile_la-vports.o .libs/libguile_la-weaks.o .libs/ 
libguile_la-ramap.o .libs/libguile_la-unif.o .libs/dynl.o .libs/ 
filesys.o .libs/posix.o .libs/net_db.o .libs/socket.o .libs/regex- 
posix.o  -lintl -L/opt/local/lib /opt/local/lib/libgmp.dylib -lm - 
lltdl  -Wl,-framework -Wl,CoreFoundation -install_name  /opt/local/ 
lib/libguile.17.dylib -compatibility_version 20 -current_version 20.0  
-Wl,-single_module
dsymutil .libs/libguile.17.2.0.dylib || :
warning: no debug map in executable (-arch i386)
(cd .libs && rm -f libguile.17.dylib && ln -s libguile.17.2.0.dylib  
libguile.17.dylib)
(cd .libs && rm -f libguile.dylib && ln -s libguile.17.2.0.dylib  
libguile.dylib)
ar cru .libs/libguile.a  libguile_la-alist.o libguile_la-arbiters.o  
libguile_la-async.o libguile_la-backtrace.o libguile_la-boolean.o  
libguile_la-chars.o libguile_la-continuations.o libguile_la-convert.o  
libguile_la-debug.o libguile_la-deprecation.o libguile_la- 
deprecated.o libguile_la-discouraged.o libguile_la-dynwind.o  
libguile_la-environments.o libguile_la-eq.o libguile_la-error.o  
libguile_la-eval.o libguile_la-evalext.o libguile_la-extensions.o  
libguile_la-feature.o libguile_la-fluids.o libguile_la-fports.o  
libguile_la-futures.o libguile_la-gc.o libguile_la-gc-mark.o  
libguile_la-gc-segment.o libguile_la-gc-malloc.o libguile_la-gc- 
card.o libguile_la-gc-freelist.o libguile_la-gc_os_dep.o libguile_la- 
gdbint.o libguile_la-gh_data.o libguile_la-gh_eval.o libguile_la- 
gh_funcs.o libguile_la-gh_init.o libguile_la-gh_io.o libguile_la- 
gh_list.o libguile_la-gh_predicates.o libguile_la-goops.o libguile_la- 
gsubr.o libguile_la-guardians.o libguile_la-hash.o libguile_la- 
hashtab.o libguile_la-hooks.o libguile_la-i18n.o libguile_la-init.o  
libguile_la-inline.o libguile_la-ioext.o libguile_la-keywords.o  
libguile_la-lang.o libguile_la-list.o libguile_la-load.o libguile_la- 
macros.o libguile_la-mallocs.o libguile_la-modules.o libguile_la- 
numbers.o libguile_la-objects.o libguile_la-objprop.o libguile_la- 
options.o libguile_la-pairs.o libguile_la-ports.o libguile_la-print.o  
libguile_la-procprop.o libguile_la-procs.o libguile_la-properties.o  
libguile_la-random.o libguile_la-rdelim.o libguile_la-read.o  
libguile_la-root.o libguile_la-rw.o libguile_la-scmsigs.o libguile_la- 
script.o libguile_la-simpos.o libguile_la-smob.o libguile_la-sort.o  
libguile_la-srcprop.o libguile_la-stackchk.o libguile_la-stacks.o  
libguile_la-stime.o libguile_la-strings.o libguile_la-srfi-4.o  
libguile_la-srfi-13.o libguile_la-srfi-14.o libguile_la-strorder.o  
libguile_la-strports.o libguile_la-struct.o libguile_la-symbols.o  
libguile_la-threads.o libguile_la-null-threads.o libguile_la-throw.o  
libguile_la-values.o libguile_la-variable.o libguile_la-vectors.o  
libguile_la-version.o libguile_la-vports.o libguile_la-weaks.o  
libguile_la-ramap.o libguile_la-unif.o dynl.o filesys.o posix.o  
net_db.o socket.o regex-posix.o
ranlib: file: .libs/libguile.a(libguile_la-futures.o) has no symbols
ranlib: file: .libs/libguile.a(libguile_la-null-threads.o) has no  
symbols
ranlib .libs/libguile.a
ranlib: file: .libs/libguile.a(libguile_la-futures.o) has no symbols
ranlib: file: .libs/libguile.a(libguile_la-null-threads.o) has no  
symbols
creating libguile.la
(cd .libs && rm -f libguile.la && ln -s ../libguile.la libguile.la)
/usr/bin/gcc-4.0 -DHAVE_CONFIG_H  -I.. -I.. -I..  -I/opt/local/ 
include -I/opt/local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing- 
prototypes -Werror -MT guile-guile.o -MD -MP -MF .deps/guile- 
guile.Tpo -c -o guile-guile.o `test -f 'guile.c' || echo './'`guile.c
mv -f .deps/guile-guile.Tpo .deps/guile-guile.Po
/bin/sh ../libtool --tag=CC   --mode=link /usr/bin/gcc-4.0 -I/opt/ 
local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing-prototypes -Werror - 
dlpreopen force -I/opt/local/include -D_THREAD_SAFE  -L/opt/local/lib  
-o guile guile-guile.o libguile.la -lgmp -lm -lltdl
rm -f .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
creating .libs/guileS.c
(cd .libs && /usr/bin/gcc-4.0  -O2 -c -fno-builtin "guileS.c")
rm -f .libs/guileS.c .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
/usr/bin/gcc-4.0 -I/opt/local/include -D_THREAD_SAFE -O2 -Wall - 
Wmissing-prototypes -Werror .libs/guileS.o -I/opt/local/include - 
D_THREAD_SAFE -o .libs/guile guile-guile.o  -L/opt/local/lib ./.libs/ 
libguile.dylib -lintl /opt/local/lib/libgmp.dylib -lm -lltdl
/usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
_lt__PROGRAM__LTX_preloaded_symbols
collect2: ld returned 1 exit status
make[3]: *** [guile] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Error: Status 1 encountered during processing.


From dluke at geeklair.net  Mon Dec 15 12:25:44 2008
From: dluke at geeklair.net (Daniel J. Luke)
Date: Mon, 15 Dec 2008 15:25:44 -0500
Subject: Distfiles mirror behind proxy
In-Reply-To: <20081215181506.GA28775@cae1.aero.org>
References: <20081210004857.GB16414@cae1.aero.org>
	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
	<20081210184321.GA25989@cae1.aero.org>
	<49400F4D.7090805@macports.org>
	<20081211174100.GA7446@cae1.aero.org>
	<49415B37.3080000@macports.org>
	<359241CF-00A1-42EB-98C9-58ADEA0A9568@macports.org>
	<20081215181506.GA28775@cae1.aero.org>
Message-ID: <1D694E2E-EABB-4780-B5B2-604B00E1838C@geeklair.net>

On Dec 15, 2008, at 1:15 PM, Max Asato wrote:
> I suppose that this does leave the door open for a shared repository
> of binary archives but I don't think that I can get away with a world
> writable shared directory.  Are there any features in 1.7 that would
> permit a read-only archive directory?


Not that I'm aware of, but you could probably adapt one of the dusty  
patches in http://trac.macports.org/ticket/8571 to do what you want.
--
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/20081215/02d53382/attachment.bin>

From jeremyhu at macports.org  Mon Dec 15 12:46:23 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Mon, 15 Dec 2008 12:46:23 -0800
Subject: KDE4 applications need X11 ?
In-Reply-To: <67DD9ACD-45F8-4ABD-9F8B-D41B0051AB28@cern.ch>
References: <67DD9ACD-45F8-4ABD-9F8B-D41B0051AB28@cern.ch>
Message-ID: <96A2F8CC-79A0-4D0F-9377-851025661450@macports.org>

Are you using QT4 for Mac or QT4 for X11?


On Dec 15, 2008, at 11:40, Chris Jones wrote:

> Hi,
>
> OK, I've been experimenting with building the KDE4 ports over the  
> last few days. I'm new to macports so bear with me, but I'm having  
> some issues.
>
> I finally managed to get kdebase4 built, which gives some basic  
> applications like kwrite, konqueror. However, each time I start  
> these they trigger X11 to start ! I thought these where suppose to  
> be using QT4-mac, which is OSX native, but it seems some X11  
> dependency is sneaking in. The apps do seem to be aqua though. After  
> starting they seem to hang (after triggering X11 to start) but if I  
> kill X11 off they sometimes come up (kinda off, all icons are  
> messing and most things don't work).
>
> Its clear I haven't done something correct here, either or the KDE4  
> ports are simply well broken at the moment (I know they are  
> experimental). I thought I had perhaps accidentally built them with  
> X11 enabled somehow, so I went back through and rebuilt explicitly  
> disabling X11, following the suggestions here
>
> http://techbase.kde.org/Projects/KDE_on_Mac_OS_X/Macbook_Manifesto
>
> but no luck.
>
> Has anyone out there built the KDE4 ports successfully ?
>
> One thing I had to do was use gcc 4.2 for kdelibs4 - I wasn't sure  
> whether I should then use gcc 4.2 for all other KDE4 ports, or go  
> back to gcc 4.0 for them. I tried using gcc 4.2...
>
> cheers Chris
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From jeremyhu at macports.org  Mon Dec 15 12:52:40 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Mon, 15 Dec 2008 12:52:40 -0800
Subject: Error upgrading xrender on Panther
In-Reply-To: <AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
Message-ID: <AC2C7954-CCAC-48EA-8E75-6CC7FE68E6AC@macports.org>

Uh... eh...  my bad.

I "fixed" this last week in r43377 but I forgot to svn add the files  
dir... so you should be able to get it now with r43828


On Dec 15, 2008, at 11:19, Frank J. R. Hanstick wrote:

> Hello,
> 	i am get the following error many times (4) when trying to execute  
> "sudo port upgrade installed":
>
> --->  Building xrender
> 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_xrender/work/libXrender-0.9.4" &&  
> make all " returned error 2
> Command output: make  all-recursive
> Making all in src
> /bin/sh ../libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0 - 
> DHAVE_CONFIG_H -I. -I..   -I/opt/local/include -I/opt/local/include - 
> I/opt/local/var/macports/sources/rsync.macports.org/release/ports/ 
> x11/xrender/files/include -I/opt/local/include   -I/usr/X11R6/ 
> include -DXTHREADS -I.. -I../include/X11/extensions  -O2 -MT  
> Picture.lo -MD -MP -MF .deps/Picture.Tpo -c -o Picture.lo Picture.c
> /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I.. -I/opt/local/include -I/ 
> opt/local/include -I/opt/local/var/macports/sources/ 
> rsync.macports.org/release/ports/x11/xrender/files/include -I/opt/ 
> local/include -I/usr/X11R6/include -DXTHREADS -I.. -I../include/X11/ 
> extensions -O2 -MT Picture.lo -MD -MP -MF .deps/Picture.Tpo -c  
> Picture.c  -fno-common -DPIC -o .libs/Picture.o
> Picture.c:29:25: error: X11/Xregion.h: No such file or directory
> Picture.c: In function 'XRenderSetPictureClipRegion':
> Picture.c:177: error: 'BOX' undeclared (first use in this function)
> Picture.c:177: error: (Each undeclared identifier is reported only  
> once
> Picture.c:177: error: for each function it appears in.)
> Picture.c:177: error: 'pb' undeclared (first use in this function)
> Picture.c:182: error: dereferencing pointer to incomplete type
> Picture.c:184: error: dereferencing pointer to incomplete type
> Picture.c:184: error: dereferencing pointer to incomplete type
> Picture.c:191: error: dereferencing pointer to incomplete type
> Picture.c:193: error: dereferencing pointer to incomplete type
> make[2]: *** [Picture.lo] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> Error: Unable to upgrade port: 1
>
> There is no /opt/local/lib/libX11/dylib on my system; but, Apple's  
> X11R6 is installed in /usr.  The file Xrender.h is in /opt/local/ 
> include/extensions.  I notice in the -I path designation for the  
> extensions is -I../include/extensions instead of /opt/local/include/ 
> extensions.  This is different from the other -I designations where / 
> opt/local precedes the directory.  This could be a problem if the  
> working directory is not ../ relative away from the include/ 
> extensions directory.
> Frank
>
> On Dec 15, 2008, at 12:12 AM, Jeremy Huddleston wrote:
>
>> The actual issue of that ticket is resolved meaning things are no  
>> more broken with xrender now than they were before (which means,  
>> they're still not too great).  If you sync, you should be able to  
>> install xrender without pulling in xorg-libX11 (assuming you can  
>> satisfy the lib:libX11.6 dependency some other way).
>>
>> The problem lies in some sort of conflict when both /usr/X11R6/lib/ 
>> libX11.dylib and /opt/local/lib/libX11/dylib are linked to by your  
>> executable... so... yeah... my short term solution to offer you is  
>> either
>>
>> 1) use all macports for your X11 dependencies (maybe setting  
>> x11prefix to /opt/local in macports.conf will be enough... you  
>> should probably then install xorg-libX11 so you don't accidently  
>> pull in XFree86)
>>
>> or
>>
>> 2) use none of the xorg-* ports in macports
>>
>> Sorry I can't offer you a better solution right now.
>>
>> On Dec 14, 2008, at 23:06, David Epstein wrote:
>>
>>>
>>>
>>> Jeremy Huddleston-5 wrote:
>>>>
>>>> Can you please see:
>>>> http://trac.macports.org/ticket/17429#comment:
>>>> I think if you pull in xorg-libX11 first, it'll be fine, but I need
>>>> someone to test that first...
>>>>
>>>
>>> I just tried sudo port upgrade installed (I should have said  
>>> outdated
>>> instead of installed, but nothing seemed to go wrong) and I hit  
>>> this xrender
>>> problem. I looked at the conversation over the ticket, but didn't  
>>> understand
>>> much of it. Also, I was surprised to find that the bug report was  
>>> closed,
>>> because that would indicate to me that the problems with porting  
>>> xrender
>>> have been removed. But I am continuing to get exactly the same  
>>> errors as
>>> those originally reported. How should one interpret a "bug closed"  
>>> message?
>>>
>>> I run Mac Os X 10.4.11, so I should have changed the name of the  
>>> thread from
>>> Panther to Tiger, but I didn't know how to do that.
>>>
>>> Could someone post advice on how to proceed, directed at  
>>> uneducated users?
>>> Thanks very much. I would have tried installing xorg-libX11,  
>>> except that
>>> Jeremy says, in the email I quote, that the solution is untested,  
>>> and,
>>> furthermore, the discussion on the ticket seems a little equivocal.
>>> Furthermore, I saw the comment in that discussion that installing
>>> xorg-libX11 brings in a lot of other stuff, so I don't want to do  
>>> it, unless
>>> it's necessary.
>>> -- 
>>> View this message in context: http://www.nabble.com/Error-upgrading-xrender-on-Panther-tp20758046p21009181.html
>>> Sent from the MacPorts - Users mailing list archive at Nabble.com.
>>>
>>> _______________________________________________
>>> macports-users mailing list
>>> macports-users at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>


From frstan at bellsouth.net  Mon Dec 15 13:13:02 2008
From: frstan at bellsouth.net (William Davis)
Date: Mon, 15 Dec 2008 16:13:02 -0500
Subject: guile doesn't build for me
In-Reply-To: <7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>
	<49469EB5.9010004@macports.org>
	<8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>
	<4946B254.8040606@macports.org>
	<7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>
Message-ID: <3B47485C-1C8E-453E-934E-B941F19309ED@bellsouth.net>


On Dec 15, 2008, at 3:23 PM, James E. Bailey wrote:

>
> Am 15.12.2008 um 20:39 schrieb David Evans:
>
>> William Davis wrote:
>>> Given the way you gave the port command:
>>>>> bigdaddy$ sudo
>>>>> /opt/local/bin/port clean guile
>>>
>>> I wonder if the bug in macports 1.6 install that failed to setup the
>>> macports path in your ~.profile has bitten you. if so this bug (and
>>> many others) is fixed in macports 1.7.  I suggest you download that.
>>> Im not sure that sudo port selfupdate will run correctly if your  
>>> PATH
>>> is not correctly set.
>>> William Davis
>> Yes, updating to MacPorts 1.7.0 is a good idea for everyone.
>>
>> Have just updated guile to version 1.8.6 in r43824.  Perhaps this  
>> will help.
>>
>
> Thanks for all the help, everyone. I've updated macports to 1.7, and  
> I still can't build guile. It's using the updated 1.8.6 version, and  
> the output follows. The reason for the path is because my normal  
> user account isn't an admin account, and I haven't bothered adding  
> the macports path to the admin accounts' $PATH, so I just specify it  
> manually.
>
> jamesebaileys-computer:/Users/jamesebailey/Downloads bigdaddy$ sudo / 
> opt/local/bin/port selfupdate
>
> MacPorts base version 1.600 installed
>
> Downloaded MacPorts base version 1.700
> Configuring, Building and Installing new MacPorts base
> selfupdate done!
>
> 21:07:27 bigdaddy Downloads:sudo /opt/local/bin/port clean --all guile
> --->  Cleaning guile
> 21:07:35 bigdaddy Downloads:sudo /opt/local/bin/port install guile
> --->  Fetching guile
> --->  Attempting to fetch guile-1.8.5.tar.gz from http://trd.no.distfiles.macports.org/guile
> --->  Verifying checksum(s) for guile
> --->  Extracting guile
> --->  Applying patches to guile
> --->  Configuring guile
> --->  Building guile
> Error: Target org.macports.build returned: shell command " cd "/opt/ 
> local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_lang_guile/work/guile-1.8.5" && make all  
> " returned error 2
> Command output: mv -f .deps/regex-posix.Tpo .deps/regex-posix.Plo
> /bin/sh ../libtool --tag=CC   --mode=link /usr/bin/gcc-4.0 -I/opt/ 
> local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing-prototypes -Werror  
> -lintl -Wl,-framework -Wl,CoreFoundation -version-info 19:0:2 - 
> export-dynamic -no-undefined -L/opt/local/lib -o libguile.la -rpath / 
> opt/local/lib libguile_la-alist.lo libguile_la-arbiters.lo  
> libguile_la-async.lo libguile_la-backtrace.lo libguile_la-boolean.lo  
> libguile_la-chars.lo libguile_la-continuations.lo libguile_la- 
> convert.lo libguile_la-debug.lo libguile_la-deprecation.lo  
> libguile_la-deprecated.lo libguile_la-discouraged.lo libguile_la- 
> dynwind.lo libguile_la-environments.lo libguile_la-eq.lo libguile_la- 
> error.lo libguile_la-eval.lo libguile_la-evalext.lo libguile_la- 
> extensions.lo libguile_la-feature.lo libguile_la-fluids.lo  
> libguile_la-fports.lo libguile_la-futures.lo libguile_la-gc.lo  
> libguile_la-gc-mark.lo libguile_la-gc-segment.lo libguile_la-gc- 
> malloc.lo libguile_la-gc-card.lo libguile_la-gc-freelist.lo  
> libguile_la-gc_os_dep.lo libguile_la-gdbint.lo libguile_la- 
> gh_data.lo libguile_la-gh_eval.lo libguile_la-gh_funcs.lo  
> libguile_la-gh_init.lo libguile_la-gh_io.lo libguile_la-gh_list.lo  
> libguile_la-gh_predicates.lo libguile_la-goops.lo libguile_la- 
> gsubr.lo libguile_la-guardians.lo libguile_la-hash.lo libguile_la- 
> hashtab.lo libguile_la-hooks.lo libguile_la-i18n.lo libguile_la- 
> init.lo libguile_la-inline.lo libguile_la-ioext.lo libguile_la- 
> keywords.lo libguile_la-lang.lo libguile_la-list.lo libguile_la- 
> load.lo libguile_la-macros.lo libguile_la-mallocs.lo libguile_la- 
> modules.lo libguile_la-numbers.lo libguile_la-objects.lo libguile_la- 
> objprop.lo libguile_la-options.lo libguile_la-pairs.lo libguile_la- 
> ports.lo libguile_la-print.lo libguile_la-procprop.lo libguile_la- 
> procs.lo libguile_la-properties.lo libguile_la-random.lo libguile_la- 
> rdelim.lo libguile_la-read.lo libguile_la-root.lo libguile_la-rw.lo  
> libguile_la-scmsigs.lo libguile_la-script.lo libguile_la-simpos.lo  
> libguile_la-smob.lo libguile_la-sort.lo libguile_la-srcprop.lo  
> libguile_la-stackchk.lo libguile_la-stacks.lo libguile_la-stime.lo  
> libguile_la-strings.lo libguile_la-srfi-4.lo libguile_la-srfi-13.lo  
> libguile_la-srfi-14.lo libguile_la-strorder.lo libguile_la- 
> strports.lo libguile_la-struct.lo libguile_la-symbols.lo libguile_la- 
> threads.lo libguile_la-null-threads.lo libguile_la-throw.lo  
> libguile_la-values.lo libguile_la-variable.lo libguile_la-vectors.lo  
> libguile_la-version.lo libguile_la-vports.lo libguile_la-weaks.lo  
> libguile_la-ramap.lo libguile_la-unif.lo dynl.lo filesys.lo posix.lo  
> net_db.lo socket.lo regex-posix.lo -lgmp -lm -lltdl
> /usr/bin/gcc-4.0 -dynamiclib  -o .libs/libguile.17.2.0.dylib  .libs/ 
> libguile_la-alist.o .libs/libguile_la-arbiters.o .libs/libguile_la- 
> async.o .libs/libguile_la-backtrace.o .libs/libguile_la- 
> boolean.o .libs/libguile_la-chars.o .libs/libguile_la- 
> continuations.o .libs/libguile_la-convert.o .libs/libguile_la- 
> debug.o .libs/libguile_la-deprecation.o .libs/libguile_la- 
> deprecated.o .libs/libguile_la-discouraged.o .libs/libguile_la- 
> dynwind.o .libs/libguile_la-environments.o .libs/libguile_la- 
> eq.o .libs/libguile_la-error.o .libs/libguile_la-eval.o .libs/ 
> libguile_la-evalext.o .libs/libguile_la-extensions.o .libs/ 
> libguile_la-feature.o .libs/libguile_la-fluids.o .libs/libguile_la- 
> fports.o .libs/libguile_la-futures.o .libs/libguile_la-gc.o .libs/ 
> libguile_la-gc-mark.o .libs/libguile_la-gc-segment.o .libs/ 
> libguile_la-gc-malloc.o .libs/libguile_la-gc-card.o .libs/ 
> libguile_la-gc-freelist.o .libs/libguile_la-gc_os_dep.o .libs/ 
> libguile_la-gdbint.o .libs/libguile_la-gh_data.o .libs/libguile_la- 
> gh_eval.o .libs/libguile_la-gh_funcs.o .libs/libguile_la- 
> gh_init.o .libs/libguile_la-gh_io.o .libs/libguile_la- 
> gh_list.o .libs/libguile_la-gh_predicates.o .libs/libguile_la- 
> goops.o .libs/libguile_la-gsubr.o .libs/libguile_la- 
> guardians.o .libs/libguile_la-hash.o .libs/libguile_la- 
> hashtab.o .libs/libguile_la-hooks.o .libs/libguile_la-i18n.o .libs/ 
> libguile_la-init.o .libs/libguile_la-inline.o .libs/libguile_la- 
> ioext.o .libs/libguile_la-keywords.o .libs/libguile_la-lang.o .libs/ 
> libguile_la-list.o .libs/libguile_la-load.o .libs/libguile_la- 
> macros.o .libs/libguile_la-mallocs.o .libs/libguile_la- 
> modules.o .libs/libguile_la-numbers.o .libs/libguile_la- 
> objects.o .libs/libguile_la-objprop.o .libs/libguile_la- 
> options.o .libs/libguile_la-pairs.o .libs/libguile_la-ports.o .libs/ 
> libguile_la-print.o .libs/libguile_la-procprop.o .libs/libguile_la- 
> procs.o .libs/libguile_la-properties.o .libs/libguile_la- 
> random.o .libs/libguile_la-rdelim.o .libs/libguile_la-read.o .libs/ 
> libguile_la-root.o .libs/libguile_la-rw.o .libs/libguile_la- 
> scmsigs.o .libs/libguile_la-script.o .libs/libguile_la- 
> simpos.o .libs/libguile_la-smob.o .libs/libguile_la-sort.o .libs/ 
> libguile_la-srcprop.o .libs/libguile_la-stackchk.o .libs/libguile_la- 
> stacks.o .libs/libguile_la-stime.o .libs/libguile_la-strings.o .libs/ 
> libguile_la-srfi-4.o .libs/libguile_la-srfi-13.o .libs/libguile_la- 
> srfi-14.o .libs/libguile_la-strorder.o .libs/libguile_la- 
> strports.o .libs/libguile_la-struct.o .libs/libguile_la- 
> symbols.o .libs/libguile_la-threads.o .libs/libguile_la-null- 
> threads.o .libs/libguile_la-throw.o .libs/libguile_la-values.o .libs/ 
> libguile_la-variable.o .libs/libguile_la-vectors.o .libs/libguile_la- 
> version.o .libs/libguile_la-vports.o .libs/libguile_la-weaks.o .libs/ 
> libguile_la-ramap.o .libs/libguile_la-unif.o .libs/dynl.o .libs/ 
> filesys.o .libs/posix.o .libs/net_db.o .libs/socket.o .libs/regex- 
> posix.o  -lintl -L/opt/local/lib /opt/local/lib/libgmp.dylib -lm - 
> lltdl  -Wl,-framework -Wl,CoreFoundation -install_name  /opt/local/ 
> lib/libguile.17.dylib -compatibility_version 20 -current_version  
> 20.0 -Wl,-single_module
> dsymutil .libs/libguile.17.2.0.dylib || :
> warning: no debug map in executable (-arch i386)
> (cd .libs && rm -f libguile.17.dylib && ln -s libguile.17.2.0.dylib  
> libguile.17.dylib)
> (cd .libs && rm -f libguile.dylib && ln -s libguile.17.2.0.dylib  
> libguile.dylib)
> ar cru .libs/libguile.a  libguile_la-alist.o libguile_la-arbiters.o  
> libguile_la-async.o libguile_la-backtrace.o libguile_la-boolean.o  
> libguile_la-chars.o libguile_la-continuations.o libguile_la- 
> convert.o libguile_la-debug.o libguile_la-deprecation.o libguile_la- 
> deprecated.o libguile_la-discouraged.o libguile_la-dynwind.o  
> libguile_la-environments.o libguile_la-eq.o libguile_la-error.o  
> libguile_la-eval.o libguile_la-evalext.o libguile_la-extensions.o  
> libguile_la-feature.o libguile_la-fluids.o libguile_la-fports.o  
> libguile_la-futures.o libguile_la-gc.o libguile_la-gc-mark.o  
> libguile_la-gc-segment.o libguile_la-gc-malloc.o libguile_la-gc- 
> card.o libguile_la-gc-freelist.o libguile_la-gc_os_dep.o libguile_la- 
> gdbint.o libguile_la-gh_data.o libguile_la-gh_eval.o libguile_la- 
> gh_funcs.o libguile_la-gh_init.o libguile_la-gh_io.o libguile_la- 
> gh_list.o libguile_la-gh_predicates.o libguile_la-goops.o  
> libguile_la-gsubr.o libguile_la-guardians.o libguile_la-hash.o  
> libguile_la-hashtab.o libguile_la-hooks.o libguile_la-i18n.o  
> libguile_la-init.o libguile_la-inline.o libguile_la-ioext.o  
> libguile_la-keywords.o libguile_la-lang.o libguile_la-list.o  
> libguile_la-load.o libguile_la-macros.o libguile_la-mallocs.o  
> libguile_la-modules.o libguile_la-numbers.o libguile_la-objects.o  
> libguile_la-objprop.o libguile_la-options.o libguile_la-pairs.o  
> libguile_la-ports.o libguile_la-print.o libguile_la-procprop.o  
> libguile_la-procs.o libguile_la-properties.o libguile_la-random.o  
> libguile_la-rdelim.o libguile_la-read.o libguile_la-root.o  
> libguile_la-rw.o libguile_la-scmsigs.o libguile_la-script.o  
> libguile_la-simpos.o libguile_la-smob.o libguile_la-sort.o  
> libguile_la-srcprop.o libguile_la-stackchk.o libguile_la-stacks.o  
> libguile_la-stime.o libguile_la-strings.o libguile_la-srfi-4.o  
> libguile_la-srfi-13.o libguile_la-srfi-14.o libguile_la-strorder.o  
> libguile_la-strports.o libguile_la-struct.o libguile_la-symbols.o  
> libguile_la-threads.o libguile_la-null-threads.o libguile_la-throw.o  
> libguile_la-values.o libguile_la-variable.o libguile_la-vectors.o  
> libguile_la-version.o libguile_la-vports.o libguile_la-weaks.o  
> libguile_la-ramap.o libguile_la-unif.o dynl.o filesys.o posix.o  
> net_db.o socket.o regex-posix.o
> ranlib: file: .libs/libguile.a(libguile_la-futures.o) has no symbols
> ranlib: file: .libs/libguile.a(libguile_la-null-threads.o) has no  
> symbols
> ranlib .libs/libguile.a
> ranlib: file: .libs/libguile.a(libguile_la-futures.o) has no symbols
> ranlib: file: .libs/libguile.a(libguile_la-null-threads.o) has no  
> symbols
> creating libguile.la
> (cd .libs && rm -f libguile.la && ln -s ../libguile.la libguile.la)
> /usr/bin/gcc-4.0 -DHAVE_CONFIG_H  -I.. -I.. -I..  -I/opt/local/ 
> include -I/opt/local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing- 
> prototypes -Werror -MT guile-guile.o -MD -MP -MF .deps/guile- 
> guile.Tpo -c -o guile-guile.o `test -f 'guile.c' || echo './'`guile.c
> mv -f .deps/guile-guile.Tpo .deps/guile-guile.Po
> /bin/sh ../libtool --tag=CC   --mode=link /usr/bin/gcc-4.0 -I/opt/ 
> local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing-prototypes -Werror  
> -dlpreopen force -I/opt/local/include -D_THREAD_SAFE  -L/opt/local/ 
> lib -o guile guile-guile.o libguile.la -lgmp -lm -lltdl
> rm -f .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
> creating .libs/guileS.c
> (cd .libs && /usr/bin/gcc-4.0  -O2 -c -fno-builtin "guileS.c")
> rm -f .libs/guileS.c .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
> /usr/bin/gcc-4.0 -I/opt/local/include -D_THREAD_SAFE -O2 -Wall - 
> Wmissing-prototypes -Werror .libs/guileS.o -I/opt/local/include - 
> D_THREAD_SAFE -o .libs/guile guile-guile.o  -L/opt/local/lib ./.libs/ 
> libguile.dylib -lintl /opt/local/lib/libgmp.dylib -lm -lltdl
> /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
> _lt__PROGRAM__LTX_preloaded_symbols
> collect2: ld returned 1 exit status
> make[3]: *** [guile] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> Error: Status 1 encountered during processing.
>

Have you installed XCode (current version) and X11SDK?

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

Mundus vult decepi, ego non


From christopher.rob.jones at cern.ch  Mon Dec 15 13:16:37 2008
From: christopher.rob.jones at cern.ch (Chris Jones)
Date: Mon, 15 Dec 2008 21:16:37 +0000
Subject: KDE4 applications need X11 ?
In-Reply-To: <96A2F8CC-79A0-4D0F-9377-851025661450@macports.org>
References: <67DD9ACD-45F8-4ABD-9F8B-D41B0051AB28@cern.ch>
	<96A2F8CC-79A0-4D0F-9377-851025661450@macports.org>
Message-ID: <624DCE93-CD71-45ED-BAFE-2653C723707A@cern.ch>


On 15 Dec 2008, at 8:46PM, Jeremy Huddleston wrote:

> Are you using QT4 for Mac or QT4 for X11?

The Mac one qt4-mac (kdelibs4 explicitly depends on it).

Some other details. I'm using OS X 10.5.5 (intel) and Xquartz 2.3.1.  
macports 1.7.0. The ports I have installed are below.

cheers Chris

localhost ~ > port installed
The following ports are currently installed:
   a52dec @0.7.4_0 (active)
   aalib @1.4rc5_3 (active)
   akonadi @1.0.0_1 (active)
   aspell @0.60.6_1+macosx (active)
   atk @1.24.0_0 (active)
   audiofile @0.2.6_2 (active)
   autoconf @2.63_0 (active)
   automake @1.10.2_0 (active)
   automoc @0.9.84_1 (active)
   avahi @0.6.23_0 (active)
   boost @1.37.0_0+darwin_9 (active)
   boost-jam @3.1.16_0 (active)
   bzip2 @1.0.5_1 (active)
   cairo @1.8.4_1+macosx (active)
   clucene @0.9.20_0 (active)
   cmake @2.6.2_0 (active)
   dbus @1.2.6_0 (active)
   dbus-glib @0.78_0 (active)
   dbus-python25 @0.83.0_0+darwin_9 (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)
   enchant @1.4.2_0 (active)
   esound @0.2.41_1 (active)
   expat @2.0.1_0 (active)
   ffmpeg @15261_0+a52+darwin_i386+gpl (active)
   fftw-3 @3.2_0 (active)
   flac @1.2.1_0+darwin_i386 (active)
   fontconfig @2.6.0_1+macosx (active)
   freetype @2.3.7_3+macosx (active)
   gdbm @1.8.3_1 (active)
   getopt @1.1.4_1 (active)
   gettext @0.17_3 (active)
   giflib @4.1.6_0 (active)
   glib2 @2.18.3_0+darwin_9 (active)
   gmake @3.81_0 (active)
   gnome-common @2.24.0_1 (active)
   gnome-doc-utils @0.14.0_0 (active)
   gnupg @1.4.9_0 (active)
   gperf @3.0.3_0 (active)
   gpgme @1.1.7_0 (active)
   gtk-doc @1.11_0 (active)
   gtk2 @2.14.5_0+x11 (active)
   help2man @1.36.4_1 (active)
   ilmbase @1.0.1_2 (active)
   ImageMagick @6.4.7-2_0+q16 (active)
   intltool @0.40.5_0 (active)
   iso-codes @3.5_0 (active)
   jasper @1.900.1_2+darwin_9 (active)
   jpeg @6b_3 (active)
   kdebase4 @4.1.3_1 (active)
   kdelibs4 @4.1.3_1 (active)
   kdepimlibs4 @4.1.3_1 (active)
   lame @3.98.2_0 (active)
   lcms @1.17_0 (active)
   libdaemon @0.12_1 (active)
   libdvdread @4.1.3_0 (active)
   libglade2 @2.6.3_0 (active)
   libgpg-error @1.7_0 (active)
   libiconv @1.12_0 (active)
   libmng @1.0.10_0 (active)
   libmpeg2 @0.5.1_0 (active)
   libogg @1.1.3_2 (active)
   libpixman @0.12.0_1 (active)
   libpng @1.2.33_0 (active)
   libsdl @1.2.13_2 (active)
   libtool @1.5.26_0 (active)
   libvorbis @1.2.0_1 (active)
   libxml2 @2.7.2_1+darwin_9 (active)
   libxslt @1.1.24_1+darwin_9 (active)
   lzmautils @4.32.7_0 (active)
   m4 @1.4.12_1 (active)
   macfuse @1.7_1 (active)
   mysql5 @5.0.67_1 (active)
   ncurses @5.7_0 (active)
   ncursesw @5.7_0 (active)
   openexr @1.6.1_1 (active)
   openssh @5.1p1_0+darwin_9 (active)
   openssl @0.9.8i_0 (active)
   p5-locale-gettext @1.05_0 (active)
   p5-xml-parser @2.36_0 (active)
   pango @1.22.3_1 (active)
   pcre @7.8_1 (active)
   perl5 @5.8.8_1
   perl5 @5.8.8_2 (active)
   perl5.8 @5.8.8_3+darwin_9 (active)
   phonon @4.2.0_1 (active)
   pkgconfig @0.23_1 (active)
   popt @1.14_0 (active)
   pth @2.0.7_0 (active)
   py25-cairo @1.6.4_0+darwin_9 (active)
   py25-gdbm @2.5.2_0 (active)
   py25-gobject @2.14.2_0+darwin_9 (active)
   py25-gtk @2.12.1_0+darwin_9 (active)
   py25-hashlib @2.5.2_0 (active)
   py25-libxml2 @2.6.21_1 (active)
   py25-nose @0.10.4_0 (active)
   py25-numeric @24.2_1+macosx (active)
   py25-numpy @1.2.1_0 (active)
   py25-setuptools @0.6c9_0 (active)
   py25-zlib @2.5.2_0 (active)
   python25 @2.5.2_7+darwin_9 (active)
   qimageblitz @0.0.5_1 (active)
   qt4-mac @4.4.3_0+dbus+docs+mysql5+ssl (active)
   rarian @0.8.1_0 (active)
   readline @5.2.012_1 (active)
   samba3 @3.2.4_0+darwin_9 (active)
   shared-mime-info @0.51_0 (active)
   sshfs @1.9_0 (active)
   sshfs-gui @1.3_0 (active)
   strigi @0.5.10_0 (active)
   texinfo @4.13_0 (active)
   tiff @3.8.2_2+darwin_9+macosx (active)
   tightvnc @1.3.9_0 (active)
   transcode @1.1.0beta1_0 (active)
   wget @1.11.4_0 (active)
   xine-lib @1.1.14_0 (active)
   xmlcatmgr @2.2_1 (active)
   zlib @1.2.3_2 (active)


From blb at macports.org  Mon Dec 15 13:20:11 2008
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 15 Dec 2008 14:20:11 -0700
Subject: guile doesn't build for me
In-Reply-To: <7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>
	<49469EB5.9010004@macports.org>
	<8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>
	<4946B254.8040606@macports.org>
	<7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>
Message-ID: <20081215212011.GE799@ninagal.withay.com>

On Mon, Dec 15, 2008 at 09:23:38PM +0100, James E. Bailey said:
[...]
> 21:07:35 bigdaddy Downloads:sudo /opt/local/bin/port install guile
[...]
> (cd .libs && /usr/bin/gcc-4.0  -O2 -c -fno-builtin "guileS.c")
> rm -f .libs/guileS.c .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
> /usr/bin/gcc-4.0 -I/opt/local/include -D_THREAD_SAFE -O2 -Wall - 
> Wmissing-prototypes -Werror .libs/guileS.o -I/opt/local/include - 
> D_THREAD_SAFE -o .libs/guile guile-guile.o  -L/opt/local/lib ./.libs/ 
> libguile.dylib -lintl /opt/local/lib/libgmp.dylib -lm -lltdl
> /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
> _lt__PROGRAM__LTX_preloaded_symbols
> collect2: ld returned 1 exit status

Do you have libtool2 someplace?  Either one of the ports (libtool-devel and
libtool2) or somewhere else?

Bryan


From trog24 at comcast.net  Mon Dec 15 13:28:04 2008
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Mon, 15 Dec 2008 13:28:04 -0800
Subject: Error upgrading xrender on Panther
In-Reply-To: <4946B934.2040700@macports.org>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>	<21009181.post@talk.nabble.com>	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
	<4946B934.2040700@macports.org>
Message-ID: <C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>

Hello,
	The command was "sudo port upgrade installed".  I wish there were a  
debug output.  The only output I had was the repeated sequence of:

--->  Building xrender
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_xre 
nder/work/libXrender-0.9.4" && make all " returned error 2
Command output: make  all-recursive
Making all in src
/bin/sh ../libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0 - 
DHAVE_CONFIG_H -I. -I..   -I/opt/local/include -I/opt/local/include - 
I/opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/ 
xrender/files/include -I/opt/local/include   -I/usr/X11R6/include - 
DXTHREADS -I.. -I../include/X11/extensions  -O2 -MT Picture.lo -MD - 
MP -MF .deps/Picture.Tpo -c -o Picture.lo Picture.c
  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I.. -I/opt/local/include -I/ 
opt/local/include -I/opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/x11/xrender/files/include -I/opt/ 
local/include -I/usr/X11R6/include -DXTHREADS -I.. -I../include/X11/ 
extensions -O2 -MT Picture.lo -MD -MP -MF .deps/Picture.Tpo -c  
Picture.c  -fno-common -DPIC -o .libs/Picture.o
Picture.c:29:25: error: X11/Xregion.h: No such file or directory
Picture.c: In function 'XRenderSetPictureClipRegion':
Picture.c:177: error: 'BOX' undeclared (first use in this function)
Picture.c:177: error: (Each undeclared identifier is reported only once
Picture.c:177: error: for each function it appears in.)
Picture.c:177: error: 'pb' undeclared (first use in this function)
Picture.c:182: error: dereferencing pointer to incomplete type
Picture.c:184: error: dereferencing pointer to incomplete type
Picture.c:184: error: dereferencing pointer to incomplete type
Picture.c:191: error: dereferencing pointer to incomplete type
Picture.c:193: error: dereferencing pointer to incomplete type
make[2]: *** [Picture.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Error: Unable to upgrade port: 1

in the terminal window for 12 iterations.  There was no command line  
for input until I did the control C.  There were earlier iterations  
of the same message sequence interwoven with other upgrades.  When  
all the other elements were upgraded, MacPorts just cycled on trying  
to upgrade xrender.  Is there a way to get a debug output?
Frank

On Dec 15, 2008, at 12:08 PM, Joshua Root wrote:

> Frank J. R. Hanstick wrote:
>> Hello,
>>     MacPorts 1.700 got caught in an infinite loop in trying to  
>> upgrade
>> xrender.  12 attempts were made before I terminated the loop with a
>> control C.
>
> This sounds kind of like <http://trac.macports.org/ticket/14829>. What
> was the command line you used? I'd be interested in seeing debug  
> output
> for this.
>
> - Josh


From frstan at bellsouth.net  Mon Dec 15 13:33:31 2008
From: frstan at bellsouth.net (William Davis)
Date: Mon, 15 Dec 2008 16:33:31 -0500
Subject: Error upgrading xrender on Panther
In-Reply-To: <C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>	<21009181.post@talk.nabble.com>	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
	<4946B934.2040700@macports.org>
	<C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>
Message-ID: <EC8A4216-ADC7-4270-A92C-D5C6B29CA39B@bellsouth.net>


On Dec 15, 2008, at 4:28 PM, Frank J. R. Hanstick wrote:

> Hello,
> 	The command was "sudo port upgrade installed".  I wish there were a  
> debug output.  The only output I had was the repeated sequence of:
>
> --->  Building xrender
> 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_xrender/work/libXrender-0.9.4" &&  
> make all " returned error 2
> Command output: make  all-recursive
> Making all in src
> /bin/sh ../libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0 - 
> DHAVE_CONFIG_H -I. -I..   -I/opt/local/include -I/opt/local/include - 
> I/opt/local/var/macports/sources/rsync.macports.org/release/ports/ 
> x11/xrender/files/include -I/opt/local/include   -I/usr/X11R6/ 
> include -DXTHREADS -I.. -I../include/X11/extensions  -O2 -MT  
> Picture.lo -MD -MP -MF .deps/Picture.Tpo -c -o Picture.lo Picture.c
> /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I.. -I/opt/local/include -I/ 
> opt/local/include -I/opt/local/var/macports/sources/ 
> rsync.macports.org/release/ports/x11/xrender/files/include -I/opt/ 
> local/include -I/usr/X11R6/include -DXTHREADS -I.. -I../include/X11/ 
> extensions -O2 -MT Picture.lo -MD -MP -MF .deps/Picture.Tpo -c  
> Picture.c  -fno-common -DPIC -o .libs/Picture.o
> Picture.c:29:25: error: X11/Xregion.h: No such file or directory
> Picture.c: In function 'XRenderSetPictureClipRegion':
> Picture.c:177: error: 'BOX' undeclared (first use in this function)
> Picture.c:177: error: (Each undeclared identifier is reported only  
> once
> Picture.c:177: error: for each function it appears in.)
> Picture.c:177: error: 'pb' undeclared (first use in this function)
> Picture.c:182: error: dereferencing pointer to incomplete type
> Picture.c:184: error: dereferencing pointer to incomplete type
> Picture.c:184: error: dereferencing pointer to incomplete type
> Picture.c:191: error: dereferencing pointer to incomplete type
> Picture.c:193: error: dereferencing pointer to incomplete type
> make[2]: *** [Picture.lo] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> Error: Unable to upgrade port: 1
>
> in the terminal window for 12 iterations.  There was no command line  
> for input until I did the control C.  There were earlier iterations  
> of the same message sequence interwoven with other upgrades.  When  
> all the other elements were upgraded, MacPorts just cycled on trying  
> to upgrade xrender.  Is there a way to get a debug output?
> Frank
>
> On Dec 15, 2008, at 12:08 PM, Joshua Root wrote:
>
>> Frank J. R. Hanstick wrote:
>>> Hello,
>>>    MacPorts 1.700 got caught in an infinite loop in trying to  
>>> upgrade
>>> xrender.  12 attempts were made before I terminated the loop with a
>>> control C.
>>
>> This sounds kind of like <http://trac.macports.org/ticket/14829>.  
>> What
>> was the command line you used? I'd be interested in seeing debug  
>> output
>> for this.
>>
>> - Josh
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

To get a debug output use -d as in
sudo port -d install foo

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

Mundus vult decepi, ego non


From christopher.rob.jones at cern.ch  Mon Dec 15 13:37:37 2008
From: christopher.rob.jones at cern.ch (Chris Jones)
Date: Mon, 15 Dec 2008 21:37:37 +0000
Subject: KDE4 applications need X11 ?
In-Reply-To: <624DCE93-CD71-45ED-BAFE-2653C723707A@cern.ch>
References: <67DD9ACD-45F8-4ABD-9F8B-D41B0051AB28@cern.ch>
	<96A2F8CC-79A0-4D0F-9377-851025661450@macports.org>
	<624DCE93-CD71-45ED-BAFE-2653C723707A@cern.ch>
Message-ID: <7C378D6F-138A-463E-97AF-A1AF9A779B2E@cern.ch>

Hi,

One possibly related thing. If I try and build kdebase4-runtime (Do I  
need this, its not clear to me ?) I get the error below. It seems it  
is trying to use X11 in some way ?

cd /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_kde_kdebase4-runtime/work/build/phonon/ 
xine && /usr/bin/g++-4.2   -DQT_NO_STL -DQT_NO_CAST_TO_ASCII - 
D_REENTRANT -DKDE_DEPRECATED_WARNINGS -D_FILE_OFFSET_BITS=64 - 
D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 - 
DPHONON_BACKEND_VERSION_4_2 -Dphonon_xine_EXPORTS -O2  -fno-common - 
Woverloaded-virtual -fvisibility=hidden -fvisibility-inlines-hidden - 
O2 -DNDEBUG -DQT_NO_DEBUG -fPIC -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_kde_kdebase4-runtime/work/build/phonon/ 
xine -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_kde_kdebase4-runtime/work/kdebase- 
runtime-4.1.3/phonon/xine -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_kde_kdebase4-runtime/work/kdebase- 
runtime-4.1.3 -I/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_kde_kdebase4-runtime/work/build -I/opt/ 
local/include -I/opt/local/include/KDE -I/opt/local/include/qt4-mac/ 
phonon -I/opt/local/include/qt4-mac/QtXmlPatterns -I/opt/local/include/ 
qt4-mac/QtWebKit -I/opt/local/include/qt4-mac/QtHelp -I/opt/local/ 
include/qt4-mac/QtAssistant -I/opt/local/include/qt4-mac/QtDBus -I/opt/ 
local/include/qt4-mac/QtTest -I/opt/local/include/qt4-mac/QtUiTools -I/ 
opt/local/include/qt4-mac/QtScript -I/opt/local/include/qt4-mac/QtSvg - 
I/opt/local/include/qt4-mac/QtXml -I/opt/local/include/qt4-mac/QtSql - 
I/opt/local/include/qt4-mac/QtOpenGL -I/opt/local/include/qt4-mac/ 
QtNetwork -I/opt/local/include/qt4-mac/QtDesigner -I/opt/local/include/ 
qt4-mac/Qt3Support -I/opt/local/include/qt4-mac/QtGui -I/opt/local/ 
include/qt4-mac/QtCore -I/opt/local/include/qt4-mac/Qt -I/opt/local/ 
share/qt4-mac/mkspecs/default -I/opt/local/include/qt4-mac -I/usr/ 
X11R6/include   -F/opt/local/Library/Frameworks -L/opt/local/Library/ 
Frameworks -D__APPLE_KDE__ -D_LARGEFILE64_SOURCE -I/usr/X11/include -o  
CMakeFiles/phonon_xine.dir/videowidget.o -c /opt/local/var/macports/ 
build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_kde_kdebase4-runtime/work/kdebase- 
runtime-4.1.3/phonon/xine/videowidget.cpp
/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_kde_kdebase4-runtime/work/kdebase- 
runtime-4.1.3/phonon/xine/videowidget.cpp:29:20: error: QX11Info: No  
such file or directory
make[2]: *** [phonon/xine/CMakeFiles/phonon_xine.dir/videowidget.o]  
Error 1
make[1]: *** [phonon/xine/CMakeFiles/phonon_xine.dir/all] Error 2
make: *** [all] Error 2

Chris

On 15 Dec 2008, at 9:16PM, Chris Jones wrote:

>
> On 15 Dec 2008, at 8:46PM, Jeremy Huddleston wrote:
>
>> Are you using QT4 for Mac or QT4 for X11?
>
> The Mac one qt4-mac (kdelibs4 explicitly depends on it).
>
> Some other details. I'm using OS X 10.5.5 (intel) and Xquartz 2.3.1.  
> macports 1.7.0. The ports I have installed are below.
>
> cheers Chris
>
> localhost ~ > port installed
> The following ports are currently installed:
>  a52dec @0.7.4_0 (active)
>  aalib @1.4rc5_3 (active)
>  akonadi @1.0.0_1 (active)
>  aspell @0.60.6_1+macosx (active)
>  atk @1.24.0_0 (active)
>  audiofile @0.2.6_2 (active)
>  autoconf @2.63_0 (active)
>  automake @1.10.2_0 (active)
>  automoc @0.9.84_1 (active)
>  avahi @0.6.23_0 (active)
>  boost @1.37.0_0+darwin_9 (active)
>  boost-jam @3.1.16_0 (active)
>  bzip2 @1.0.5_1 (active)
>  cairo @1.8.4_1+macosx (active)
>  clucene @0.9.20_0 (active)
>  cmake @2.6.2_0 (active)
>  dbus @1.2.6_0 (active)
>  dbus-glib @0.78_0 (active)
>  dbus-python25 @0.83.0_0+darwin_9 (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)
>  enchant @1.4.2_0 (active)
>  esound @0.2.41_1 (active)
>  expat @2.0.1_0 (active)
>  ffmpeg @15261_0+a52+darwin_i386+gpl (active)
>  fftw-3 @3.2_0 (active)
>  flac @1.2.1_0+darwin_i386 (active)
>  fontconfig @2.6.0_1+macosx (active)
>  freetype @2.3.7_3+macosx (active)
>  gdbm @1.8.3_1 (active)
>  getopt @1.1.4_1 (active)
>  gettext @0.17_3 (active)
>  giflib @4.1.6_0 (active)
>  glib2 @2.18.3_0+darwin_9 (active)
>  gmake @3.81_0 (active)
>  gnome-common @2.24.0_1 (active)
>  gnome-doc-utils @0.14.0_0 (active)
>  gnupg @1.4.9_0 (active)
>  gperf @3.0.3_0 (active)
>  gpgme @1.1.7_0 (active)
>  gtk-doc @1.11_0 (active)
>  gtk2 @2.14.5_0+x11 (active)
>  help2man @1.36.4_1 (active)
>  ilmbase @1.0.1_2 (active)
>  ImageMagick @6.4.7-2_0+q16 (active)
>  intltool @0.40.5_0 (active)
>  iso-codes @3.5_0 (active)
>  jasper @1.900.1_2+darwin_9 (active)
>  jpeg @6b_3 (active)
>  kdebase4 @4.1.3_1 (active)
>  kdelibs4 @4.1.3_1 (active)
>  kdepimlibs4 @4.1.3_1 (active)
>  lame @3.98.2_0 (active)
>  lcms @1.17_0 (active)
>  libdaemon @0.12_1 (active)
>  libdvdread @4.1.3_0 (active)
>  libglade2 @2.6.3_0 (active)
>  libgpg-error @1.7_0 (active)
>  libiconv @1.12_0 (active)
>  libmng @1.0.10_0 (active)
>  libmpeg2 @0.5.1_0 (active)
>  libogg @1.1.3_2 (active)
>  libpixman @0.12.0_1 (active)
>  libpng @1.2.33_0 (active)
>  libsdl @1.2.13_2 (active)
>  libtool @1.5.26_0 (active)
>  libvorbis @1.2.0_1 (active)
>  libxml2 @2.7.2_1+darwin_9 (active)
>  libxslt @1.1.24_1+darwin_9 (active)
>  lzmautils @4.32.7_0 (active)
>  m4 @1.4.12_1 (active)
>  macfuse @1.7_1 (active)
>  mysql5 @5.0.67_1 (active)
>  ncurses @5.7_0 (active)
>  ncursesw @5.7_0 (active)
>  openexr @1.6.1_1 (active)
>  openssh @5.1p1_0+darwin_9 (active)
>  openssl @0.9.8i_0 (active)
>  p5-locale-gettext @1.05_0 (active)
>  p5-xml-parser @2.36_0 (active)
>  pango @1.22.3_1 (active)
>  pcre @7.8_1 (active)
>  perl5 @5.8.8_1
>  perl5 @5.8.8_2 (active)
>  perl5.8 @5.8.8_3+darwin_9 (active)
>  phonon @4.2.0_1 (active)
>  pkgconfig @0.23_1 (active)
>  popt @1.14_0 (active)
>  pth @2.0.7_0 (active)
>  py25-cairo @1.6.4_0+darwin_9 (active)
>  py25-gdbm @2.5.2_0 (active)
>  py25-gobject @2.14.2_0+darwin_9 (active)
>  py25-gtk @2.12.1_0+darwin_9 (active)
>  py25-hashlib @2.5.2_0 (active)
>  py25-libxml2 @2.6.21_1 (active)
>  py25-nose @0.10.4_0 (active)
>  py25-numeric @24.2_1+macosx (active)
>  py25-numpy @1.2.1_0 (active)
>  py25-setuptools @0.6c9_0 (active)
>  py25-zlib @2.5.2_0 (active)
>  python25 @2.5.2_7+darwin_9 (active)
>  qimageblitz @0.0.5_1 (active)
>  qt4-mac @4.4.3_0+dbus+docs+mysql5+ssl (active)
>  rarian @0.8.1_0 (active)
>  readline @5.2.012_1 (active)
>  samba3 @3.2.4_0+darwin_9 (active)
>  shared-mime-info @0.51_0 (active)
>  sshfs @1.9_0 (active)
>  sshfs-gui @1.3_0 (active)
>  strigi @0.5.10_0 (active)
>  texinfo @4.13_0 (active)
>  tiff @3.8.2_2+darwin_9+macosx (active)
>  tightvnc @1.3.9_0 (active)
>  transcode @1.1.0beta1_0 (active)
>  wget @1.11.4_0 (active)
>  xine-lib @1.1.14_0 (active)
>  xmlcatmgr @2.2_1 (active)
>  zlib @1.2.3_2 (active)
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From jmr at macports.org  Mon Dec 15 13:56:18 2008
From: jmr at macports.org (Joshua Root)
Date: Tue, 16 Dec 2008 08:56:18 +1100
Subject: Error upgrading xrender on Panther
In-Reply-To: <C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>	<21009181.post@talk.nabble.com>	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
	<4946B934.2040700@macports.org>
	<C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>
Message-ID: <4946D282.10706@macports.org>

Frank J. R. Hanstick wrote:
> Hello,
>     The command was "sudo port upgrade installed".

That may explain it. Many different installed ports could depend on
xrender either directly or indirectly, and upgrading a port upgrades its
dependencies too (recursively). So when it failed for one dependency
relationship, it moved on to the next and tried again.

This is one reason that `sudo port upgrade outdated` is preferred.

> Is there a way to get a debug output?

Add the -d option, e.g. `sudo port -d upgrade outdated`.

- Josh

From jmr at macports.org  Mon Dec 15 13:58:12 2008
From: jmr at macports.org (Joshua Root)
Date: Tue, 16 Dec 2008 08:58:12 +1100
Subject: guile doesn't build for me
In-Reply-To: <20081215212011.GE799@ninagal.withay.com>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>	<49469EB5.9010004@macports.org>	<8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>	<4946B254.8040606@macports.org>	<7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>
	<20081215212011.GE799@ninagal.withay.com>
Message-ID: <4946D2F4.5060503@macports.org>

Bryan Blackburn wrote:
> On Mon, Dec 15, 2008 at 09:23:38PM +0100, James E. Bailey said:
> [...]
>> 21:07:35 bigdaddy Downloads:sudo /opt/local/bin/port install guile
> [...]
>> (cd .libs && /usr/bin/gcc-4.0  -O2 -c -fno-builtin "guileS.c")
>> rm -f .libs/guileS.c .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
>> /usr/bin/gcc-4.0 -I/opt/local/include -D_THREAD_SAFE -O2 -Wall - 
>> Wmissing-prototypes -Werror .libs/guileS.o -I/opt/local/include - 
>> D_THREAD_SAFE -o .libs/guile guile-guile.o  -L/opt/local/lib ./.libs/ 
>> libguile.dylib -lintl /opt/local/lib/libgmp.dylib -lm -lltdl
>> /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
>> _lt__PROGRAM__LTX_preloaded_symbols
>> collect2: ld returned 1 exit status
> 
> Do you have libtool2 someplace?  Either one of the ports (libtool-devel and
> libtool2) or somewhere else?

There actually isn't a libtool2. The libtool port is meant to be updated
to 2.x soon, but it hasn't happened yet. Could still be libtool-devel,
of course.

- Josh

From trog24 at comcast.net  Mon Dec 15 14:00:15 2008
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Mon, 15 Dec 2008 14:00:15 -0800
Subject: Error upgrading xrender on Panther
In-Reply-To: <EC8A4216-ADC7-4270-A92C-D5C6B29CA39B@bellsouth.net>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>	<21009181.post@talk.nabble.com>	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
	<4946B934.2040700@macports.org>
	<C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>
	<EC8A4216-ADC7-4270-A92C-D5C6B29CA39B@bellsouth.net>
Message-ID: <E247A2D5-813E-423B-9A53-6F9B3F9DA0B1@comcast.net>

Hello,
	Attached is a debug sample of the loop.  I tried "sudo port -d  
upgrade installed >ports.log" and the output only went to the  
Terminal window.  So, I copied a sample to a TextEdit file.  If you  
need more, I can rerun because it is repeatable.
Frank
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InfiniteLoop.rtf
Type: text/rtf
Size: 81582 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081215/7881f7ad/attachment.bin>
-------------- next part --------------


On Dec 15, 2008, at 1:33 PM, William Davis wrote:

>
> On Dec 15, 2008, at 4:28 PM, Frank J. R. Hanstick wrote:
>
>> Hello,
>> 	The command was "sudo port upgrade installed".  I wish there were  
>> a debug output.  The only output I had was the repeated sequence of:
>>
>> --->  Building xrender
>> 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_ 
>> xrender/work/libXrender-0.9.4" && make all " returned error 2
>> Command output: make  all-recursive
>> Making all in src
>> /bin/sh ../libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0 - 
>> DHAVE_CONFIG_H -I. -I..   -I/opt/local/include -I/opt/local/ 
>> include -I/opt/local/var/macports/sources/rsync.macports.org/ 
>> release/ports/x11/xrender/files/include -I/opt/local/include   -I/ 
>> usr/X11R6/include -DXTHREADS -I.. -I../include/X11/extensions  -O2  
>> -MT Picture.lo -MD -MP -MF .deps/Picture.Tpo -c -o Picture.lo  
>> Picture.c
>> /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I.. -I/opt/local/include -I/ 
>> opt/local/include -I/opt/local/var/macports/sources/ 
>> rsync.macports.org/release/ports/x11/xrender/files/include -I/opt/ 
>> local/include -I/usr/X11R6/include -DXTHREADS -I.. -I../include/ 
>> X11/extensions -O2 -MT Picture.lo -MD -MP -MF .deps/Picture.Tpo -c  
>> Picture.c  -fno-common -DPIC -o .libs/Picture.o
>> Picture.c:29:25: error: X11/Xregion.h: No such file or directory
>> Picture.c: In function 'XRenderSetPictureClipRegion':
>> Picture.c:177: error: 'BOX' undeclared (first use in this function)
>> Picture.c:177: error: (Each undeclared identifier is reported only  
>> once
>> Picture.c:177: error: for each function it appears in.)
>> Picture.c:177: error: 'pb' undeclared (first use in this function)
>> Picture.c:182: error: dereferencing pointer to incomplete type
>> Picture.c:184: error: dereferencing pointer to incomplete type
>> Picture.c:184: error: dereferencing pointer to incomplete type
>> Picture.c:191: error: dereferencing pointer to incomplete type
>> Picture.c:193: error: dereferencing pointer to incomplete type
>> make[2]: *** [Picture.lo] Error 1
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all] Error 2
>>
>> Error: Unable to upgrade port: 1
>>
>> in the terminal window for 12 iterations.  There was no command  
>> line for input until I did the control C.  There were earlier  
>> iterations of the same message sequence interwoven with other  
>> upgrades.  When all the other elements were upgraded, MacPorts  
>> just cycled on trying to upgrade xrender.  Is there a way to get a  
>> debug output?
>> Frank
>>
>> On Dec 15, 2008, at 12:08 PM, Joshua Root wrote:
>>
>>> Frank J. R. Hanstick wrote:
>>>> Hello,
>>>>    MacPorts 1.700 got caught in an infinite loop in trying to  
>>>> upgrade
>>>> xrender.  12 attempts were made before I terminated the loop with a
>>>> control C.
>>>
>>> This sounds kind of like <http://trac.macports.org/ticket/14829>.  
>>> What
>>> was the command line you used? I'd be interested in seeing debug  
>>> output
>>> for this.
>>>
>>> - Josh
>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
> To get a debug output use -d as in
> sudo port -d install foo
>
> William Davis
> frstanATbellsouthDOTnet
> Mac OS X.5.5 Darwin 9.5.0
> XQuartz 2.3.2_rc3 (xorg-server 1.4.2-apple27)
> Mac Mini Intel Duo @ 1.86 GHz
>
> Mundus vult decepi, ego non
>


From blb at macports.org  Mon Dec 15 14:07:11 2008
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 15 Dec 2008 15:07:11 -0700
Subject: guile doesn't build for me
In-Reply-To: <4946D2F4.5060503@macports.org>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>
	<49469EB5.9010004@macports.org>
	<8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>
	<4946B254.8040606@macports.org>
	<7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>
	<20081215212011.GE799@ninagal.withay.com>
	<4946D2F4.5060503@macports.org>
Message-ID: <20081215220711.GA729@ninagal.withay.com>

On Tue, Dec 16, 2008 at 08:58:12AM +1100, Joshua Root said:
> Bryan Blackburn wrote:
> > On Mon, Dec 15, 2008 at 09:23:38PM +0100, James E. Bailey said:
> > [...]
> >> 21:07:35 bigdaddy Downloads:sudo /opt/local/bin/port install guile
> > [...]
> >> (cd .libs && /usr/bin/gcc-4.0  -O2 -c -fno-builtin "guileS.c")
> >> rm -f .libs/guileS.c .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
> >> /usr/bin/gcc-4.0 -I/opt/local/include -D_THREAD_SAFE -O2 -Wall - 
> >> Wmissing-prototypes -Werror .libs/guileS.o -I/opt/local/include - 
> >> D_THREAD_SAFE -o .libs/guile guile-guile.o  -L/opt/local/lib ./.libs/ 
> >> libguile.dylib -lintl /opt/local/lib/libgmp.dylib -lm -lltdl
> >> /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
> >> _lt__PROGRAM__LTX_preloaded_symbols
> >> collect2: ld returned 1 exit status
> > 
> > Do you have libtool2 someplace?  Either one of the ports (libtool-devel and
> > libtool2) or somewhere else?
> 
> There actually isn't a libtool2. The libtool port is meant to be updated
> to 2.x soon, but it hasn't happened yet. Could still be libtool-devel,
> of course.

Oops, you're right, libtool2 is in my local repo...so ignore that one.

Bryan


> 
> - Josh

From perry at macports.org  Mon Dec 15 14:10:31 2008
From: perry at macports.org (Perry Lee)
Date: Mon, 15 Dec 2008 14:10:31 -0800
Subject: Error upgrading xrender on Panther
In-Reply-To: <E247A2D5-813E-423B-9A53-6F9B3F9DA0B1@comcast.net>
References: <DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
	<4946B934.2040700@macports.org>
	<C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>
	<EC8A4216-ADC7-4270-A92C-D5C6B29CA39B@bellsouth.net>
	<E247A2D5-813E-423B-9A53-6F9B3F9DA0B1@comcast.net>
Message-ID: <20081215221031.GA231@spr-wlan-net-166.AirBears.Berkeley.EDU>

On Mon, Dec 15, 2008 at 02:00:15PM -0800, Frank J. R. Hanstick wrote:
> 	Attached is a debug sample of the loop.  I tried "sudo port -d upgrade
> installed >ports.log" and the output only went to the Terminal window.

As a quick answer to why the output only went to the Terminal window rather
than to ports.log, debug output is sent to stderr rather than stdout.  In order
to send debug output to the file ports.log as well, you want to add 2>&1, which
redirects stderr to stdout (or alternatively use 2>foo.log to send stderr to
the file foo.log).

From derhindemith at googlemail.com  Mon Dec 15 14:12:41 2008
From: derhindemith at googlemail.com (James E. Bailey)
Date: Mon, 15 Dec 2008 23:12:41 +0100
Subject: guile doesn't build for me
In-Reply-To: <4946D2F4.5060503@macports.org>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>	<49469EB5.9010004@macports.org>	<8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>	<4946B254.8040606@macports.org>	<7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>
	<20081215212011.GE799@ninagal.withay.com>
	<4946D2F4.5060503@macports.org>
Message-ID: <797619E2-1CF8-4BAC-8309-0710D9EE576F@googlemail.com>


Am 15.12.2008 um 22:58 schrieb Joshua Root:

> Bryan Blackburn wrote:
>> On Mon, Dec 15, 2008 at 09:23:38PM +0100, James E. Bailey said:
>> [...]
>>> 21:07:35 bigdaddy Downloads:sudo /opt/local/bin/port install guile
>> [...]
>>> (cd .libs && /usr/bin/gcc-4.0  -O2 -c -fno-builtin "guileS.c")
>>> rm -f .libs/guileS.c .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
>>> /usr/bin/gcc-4.0 -I/opt/local/include -D_THREAD_SAFE -O2 -Wall -
>>> Wmissing-prototypes -Werror .libs/guileS.o -I/opt/local/include -
>>> D_THREAD_SAFE -o .libs/guile guile-guile.o  -L/opt/local/ 
>>> lib ./.libs/
>>> libguile.dylib -lintl /opt/local/lib/libgmp.dylib -lm -lltdl
>>> /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
>>> _lt__PROGRAM__LTX_preloaded_symbols
>>> collect2: ld returned 1 exit status
>>
>> Do you have libtool2 someplace?  Either one of the ports (libtool- 
>> devel and
>> libtool2) or somewhere else?
>
> There actually isn't a libtool2. The libtool port is meant to be  
> updated
> to 2.x soon, but it hasn't happened yet. Could still be libtool-devel,
> of course.
>
> - Josh

Yes, I have libtool 2.2.6 installed. I usually just build things  
myself, outside of guile. Is libtool 2 a problem? Shouldn't macports  
build and configure things itself, regardless of what I have  
installed in /usr/local and ~/ ?


From blb at macports.org  Mon Dec 15 14:23:14 2008
From: blb at macports.org (Bryan Blackburn)
Date: Mon, 15 Dec 2008 15:23:14 -0700
Subject: guile doesn't build for me
In-Reply-To: <797619E2-1CF8-4BAC-8309-0710D9EE576F@googlemail.com>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>
	<49469EB5.9010004@macports.org>
	<8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>
	<4946B254.8040606@macports.org>
	<7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>
	<20081215212011.GE799@ninagal.withay.com>
	<4946D2F4.5060503@macports.org>
	<797619E2-1CF8-4BAC-8309-0710D9EE576F@googlemail.com>
Message-ID: <20081215222314.GC729@ninagal.withay.com>

On Mon, Dec 15, 2008 at 11:12:41PM +0100, James E. Bailey said:
>
> Am 15.12.2008 um 22:58 schrieb Joshua Root:
>
>> Bryan Blackburn wrote:
>>> On Mon, Dec 15, 2008 at 09:23:38PM +0100, James E. Bailey said:
>>> [...]
>>>> 21:07:35 bigdaddy Downloads:sudo /opt/local/bin/port install guile
>>> [...]
>>>> (cd .libs && /usr/bin/gcc-4.0  -O2 -c -fno-builtin "guileS.c")
>>>> rm -f .libs/guileS.c .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
>>>> /usr/bin/gcc-4.0 -I/opt/local/include -D_THREAD_SAFE -O2 -Wall -
>>>> Wmissing-prototypes -Werror .libs/guileS.o -I/opt/local/include -
>>>> D_THREAD_SAFE -o .libs/guile guile-guile.o  -L/opt/local/lib 
>>>> ./.libs/
>>>> libguile.dylib -lintl /opt/local/lib/libgmp.dylib -lm -lltdl
>>>> /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
>>>> _lt__PROGRAM__LTX_preloaded_symbols
>>>> collect2: ld returned 1 exit status
>>>
>>> Do you have libtool2 someplace?  Either one of the ports (libtool- 
>>> devel and
>>> libtool2) or somewhere else?
>>
>> There actually isn't a libtool2. The libtool port is meant to be  
>> updated
>> to 2.x soon, but it hasn't happened yet. Could still be libtool-devel,
>> of course.
>>
>> - Josh
>
> Yes, I have libtool 2.2.6 installed. I usually just build things myself, 
> outside of guile. Is libtool 2 a problem? Shouldn't macports build and 
> configure things itself, regardless of what I have installed in /usr/local 
> and ~/ ?

The first hit when googling lt__PROGRAM__LTX_preloaded_symbols is about
building guile, and suggests it may be an incompatibility issue with
libtool2.

Having stuff in /usr/local is problematic because some tools like to
look there regardless of what port says, eg, the -lltdl in the above compile
line may be picking up libtool2's version in /usr/local.

Bryan


From jmr at macports.org  Mon Dec 15 14:30:04 2008
From: jmr at macports.org (Joshua Root)
Date: Tue, 16 Dec 2008 09:30:04 +1100
Subject: Error upgrading xrender on Panther
In-Reply-To: <E247A2D5-813E-423B-9A53-6F9B3F9DA0B1@comcast.net>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>	<21009181.post@talk.nabble.com>	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>	<4946B934.2040700@macports.org>	<C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>	<EC8A4216-ADC7-4270-A92C-D5C6B29CA39B@bellsouth.net>
	<E247A2D5-813E-423B-9A53-6F9B3F9DA0B1@comcast.net>
Message-ID: <4946DA6C.4020502@macports.org>

Frank J. R. Hanstick wrote:
> Hello,
>     Attached is a debug sample of the loop.  I tried "sudo port -d
> upgrade installed >ports.log" and the output only went to the Terminal
> window.  So, I copied a sample to a TextEdit file.  If you need more, I
> can rerun because it is repeatable.

Do you get the same result if you upgrade outdated rather than
installed, though?

- Josh

From derhindemith at googlemail.com  Mon Dec 15 14:32:21 2008
From: derhindemith at googlemail.com (James E. Bailey)
Date: Mon, 15 Dec 2008 23:32:21 +0100
Subject: guile doesn't build for me
In-Reply-To: <3B47485C-1C8E-453E-934E-B941F19309ED@bellsouth.net>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>
	<49469EB5.9010004@macports.org>
	<8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>
	<4946B254.8040606@macports.org>
	<7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>
	<3B47485C-1C8E-453E-934E-B941F19309ED@bellsouth.net>
Message-ID: <547C7EE0-03A5-4E92-9437-C40B722F8202@googlemail.com>


Am 15.12.2008 um 22:13 schrieb William Davis:

>
> On Dec 15, 2008, at 3:23 PM, James E. Bailey wrote:
>
>>
>> Am 15.12.2008 um 20:39 schrieb David Evans:
>>
>>> William Davis wrote:
>>>> Given the way you gave the port command:
>>>>>> bigdaddy$ sudo
>>>>>> /opt/local/bin/port clean guile
>>>>
>>>> I wonder if the bug in macports 1.6 install that failed to setup  
>>>> the
>>>> macports path in your ~.profile has bitten you. if so this bug (and
>>>> many others) is fixed in macports 1.7.  I suggest you download  
>>>> that.
>>>> Im not sure that sudo port selfupdate will run correctly if your  
>>>> PATH
>>>> is not correctly set.
>>>> William Davis
>>> Yes, updating to MacPorts 1.7.0 is a good idea for everyone.
>>>
>>> Have just updated guile to version 1.8.6 in r43824.  Perhaps this  
>>> will help.
>>>
>>
>> Thanks for all the help, everyone. I've updated macports to 1.7,  
>> and I still can't build guile. It's using the updated 1.8.6  
>> version, and the output follows. The reason for the path is  
>> because my normal user account isn't an admin account, and I  
>> haven't bothered adding the macports path to the admin accounts'  
>> $PATH, so I just specify it manually.
>>
>> jamesebaileys-computer:/Users/jamesebailey/Downloads bigdaddy$  
>> sudo /opt/local/bin/port selfupdate
>>
>> MacPorts base version 1.600 installed
>>
>> Downloaded MacPorts base version 1.700
>> Configuring, Building and Installing new MacPorts base
>> selfupdate done!
>>
>> 21:07:27 bigdaddy Downloads:sudo /opt/local/bin/port clean --all  
>> guile
>> --->  Cleaning guile
>> 21:07:35 bigdaddy Downloads:sudo /opt/local/bin/port install guile
>> --->  Fetching guile
>> --->  Attempting to fetch guile-1.8.5.tar.gz from http:// 
>> trd.no.distfiles.macports.org/guile
>> --->  Verifying checksum(s) for guile
>> --->  Extracting guile
>> --->  Applying patches to guile
>> --->  Configuring guile
>> --->  Building guile
>> Error: Target org.macports.build returned: shell command " cd "/ 
>> opt/local/var/macports/build/ 
>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang 
>> _guile/work/guile-1.8.5" && make all " returned error 2
>> Command output: mv -f .deps/regex-posix.Tpo .deps/regex-posix.Plo
>> /bin/sh ../libtool --tag=CC   --mode=link /usr/bin/gcc-4.0 -I/opt/ 
>> local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing-prototypes - 
>> Werror -lintl -Wl,-framework -Wl,CoreFoundation -version-info  
>> 19:0:2 -export-dynamic -no-undefined -L/opt/local/lib -o  
>> libguile.la -rpath /opt/local/lib libguile_la-alist.lo libguile_la- 
>> arbiters.lo libguile_la-async.lo libguile_la-backtrace.lo  
>> libguile_la-boolean.lo libguile_la-chars.lo libguile_la- 
>> continuations.lo libguile_la-convert.lo libguile_la-debug.lo  
>> libguile_la-deprecation.lo libguile_la-deprecated.lo libguile_la- 
>> discouraged.lo libguile_la-dynwind.lo libguile_la-environments.lo  
>> libguile_la-eq.lo libguile_la-error.lo libguile_la-eval.lo  
>> libguile_la-evalext.lo libguile_la-extensions.lo libguile_la- 
>> feature.lo libguile_la-fluids.lo libguile_la-fports.lo libguile_la- 
>> futures.lo libguile_la-gc.lo libguile_la-gc-mark.lo libguile_la-gc- 
>> segment.lo libguile_la-gc-malloc.lo libguile_la-gc-card.lo  
>> libguile_la-gc-freelist.lo libguile_la-gc_os_dep.lo libguile_la- 
>> gdbint.lo libguile_la-gh_data.lo libguile_la-gh_eval.lo  
>> libguile_la-gh_funcs.lo libguile_la-gh_init.lo libguile_la- 
>> gh_io.lo libguile_la-gh_list.lo libguile_la-gh_predicates.lo  
>> libguile_la-goops.lo libguile_la-gsubr.lo libguile_la-guardians.lo  
>> libguile_la-hash.lo libguile_la-hashtab.lo libguile_la-hooks.lo  
>> libguile_la-i18n.lo libguile_la-init.lo libguile_la-inline.lo  
>> libguile_la-ioext.lo libguile_la-keywords.lo libguile_la-lang.lo  
>> libguile_la-list.lo libguile_la-load.lo libguile_la-macros.lo  
>> libguile_la-mallocs.lo libguile_la-modules.lo libguile_la- 
>> numbers.lo libguile_la-objects.lo libguile_la-objprop.lo  
>> libguile_la-options.lo libguile_la-pairs.lo libguile_la-ports.lo  
>> libguile_la-print.lo libguile_la-procprop.lo libguile_la-procs.lo  
>> libguile_la-properties.lo libguile_la-random.lo libguile_la- 
>> rdelim.lo libguile_la-read.lo libguile_la-root.lo libguile_la- 
>> rw.lo libguile_la-scmsigs.lo libguile_la-script.lo libguile_la- 
>> simpos.lo libguile_la-smob.lo libguile_la-sort.lo libguile_la- 
>> srcprop.lo libguile_la-stackchk.lo libguile_la-stacks.lo  
>> libguile_la-stime.lo libguile_la-strings.lo libguile_la-srfi-4.lo  
>> libguile_la-srfi-13.lo libguile_la-srfi-14.lo libguile_la- 
>> strorder.lo libguile_la-strports.lo libguile_la-struct.lo  
>> libguile_la-symbols.lo libguile_la-threads.lo libguile_la-null- 
>> threads.lo libguile_la-throw.lo libguile_la-values.lo libguile_la- 
>> variable.lo libguile_la-vectors.lo libguile_la-version.lo  
>> libguile_la-vports.lo libguile_la-weaks.lo libguile_la-ramap.lo  
>> libguile_la-unif.lo dynl.lo filesys.lo posix.lo net_db.lo  
>> socket.lo regex-posix.lo -lgmp -lm -lltdl
>> /usr/bin/gcc-4.0 -dynamiclib  -o .libs/libguile. 
>> 17.2.0.dylib  .libs/libguile_la-alist.o .libs/libguile_la- 
>> arbiters.o .libs/libguile_la-async.o .libs/libguile_la- 
>> backtrace.o .libs/libguile_la-boolean.o .libs/libguile_la- 
>> chars.o .libs/libguile_la-continuations.o .libs/libguile_la- 
>> convert.o .libs/libguile_la-debug.o .libs/libguile_la- 
>> deprecation.o .libs/libguile_la-deprecated.o .libs/libguile_la- 
>> discouraged.o .libs/libguile_la-dynwind.o .libs/libguile_la- 
>> environments.o .libs/libguile_la-eq.o .libs/libguile_la- 
>> error.o .libs/libguile_la-eval.o .libs/libguile_la-evalext.o .libs/ 
>> libguile_la-extensions.o .libs/libguile_la-feature.o .libs/ 
>> libguile_la-fluids.o .libs/libguile_la-fports.o .libs/libguile_la- 
>> futures.o .libs/libguile_la-gc.o .libs/libguile_la-gc-mark.o .libs/ 
>> libguile_la-gc-segment.o .libs/libguile_la-gc-malloc.o .libs/ 
>> libguile_la-gc-card.o .libs/libguile_la-gc-freelist.o .libs/ 
>> libguile_la-gc_os_dep.o .libs/libguile_la-gdbint.o .libs/ 
>> libguile_la-gh_data.o .libs/libguile_la-gh_eval.o .libs/ 
>> libguile_la-gh_funcs.o .libs/libguile_la-gh_init.o .libs/ 
>> libguile_la-gh_io.o .libs/libguile_la-gh_list.o .libs/libguile_la- 
>> gh_predicates.o .libs/libguile_la-goops.o .libs/libguile_la- 
>> gsubr.o .libs/libguile_la-guardians.o .libs/libguile_la- 
>> hash.o .libs/libguile_la-hashtab.o .libs/libguile_la-hooks.o .libs/ 
>> libguile_la-i18n.o .libs/libguile_la-init.o .libs/libguile_la- 
>> inline.o .libs/libguile_la-ioext.o .libs/libguile_la- 
>> keywords.o .libs/libguile_la-lang.o .libs/libguile_la-list.o .libs/ 
>> libguile_la-load.o .libs/libguile_la-macros.o .libs/libguile_la- 
>> mallocs.o .libs/libguile_la-modules.o .libs/libguile_la- 
>> numbers.o .libs/libguile_la-objects.o .libs/libguile_la- 
>> objprop.o .libs/libguile_la-options.o .libs/libguile_la- 
>> pairs.o .libs/libguile_la-ports.o .libs/libguile_la-print.o .libs/ 
>> libguile_la-procprop.o .libs/libguile_la-procs.o .libs/libguile_la- 
>> properties.o .libs/libguile_la-random.o .libs/libguile_la- 
>> rdelim.o .libs/libguile_la-read.o .libs/libguile_la-root.o .libs/ 
>> libguile_la-rw.o .libs/libguile_la-scmsigs.o .libs/libguile_la- 
>> script.o .libs/libguile_la-simpos.o .libs/libguile_la-smob.o .libs/ 
>> libguile_la-sort.o .libs/libguile_la-srcprop.o .libs/libguile_la- 
>> stackchk.o .libs/libguile_la-stacks.o .libs/libguile_la- 
>> stime.o .libs/libguile_la-strings.o .libs/libguile_la- 
>> srfi-4.o .libs/libguile_la-srfi-13.o .libs/libguile_la- 
>> srfi-14.o .libs/libguile_la-strorder.o .libs/libguile_la- 
>> strports.o .libs/libguile_la-struct.o .libs/libguile_la- 
>> symbols.o .libs/libguile_la-threads.o .libs/libguile_la-null- 
>> threads.o .libs/libguile_la-throw.o .libs/libguile_la- 
>> values.o .libs/libguile_la-variable.o .libs/libguile_la- 
>> vectors.o .libs/libguile_la-version.o .libs/libguile_la- 
>> vports.o .libs/libguile_la-weaks.o .libs/libguile_la-ramap.o .libs/ 
>> libguile_la-unif.o .libs/dynl.o .libs/filesys.o .libs/ 
>> posix.o .libs/net_db.o .libs/socket.o .libs/regex-posix.o  -lintl - 
>> L/opt/local/lib /opt/local/lib/libgmp.dylib -lm -lltdl  -Wl,- 
>> framework -Wl,CoreFoundation -install_name  /opt/local/lib/ 
>> libguile.17.dylib -compatibility_version 20 -current_version 20.0 - 
>> Wl,-single_module
>> dsymutil .libs/libguile.17.2.0.dylib || :
>> warning: no debug map in executable (-arch i386)
>> (cd .libs && rm -f libguile.17.dylib && ln -s libguile. 
>> 17.2.0.dylib libguile.17.dylib)
>> (cd .libs && rm -f libguile.dylib && ln -s libguile.17.2.0.dylib  
>> libguile.dylib)
>> ar cru .libs/libguile.a  libguile_la-alist.o libguile_la- 
>> arbiters.o libguile_la-async.o libguile_la-backtrace.o libguile_la- 
>> boolean.o libguile_la-chars.o libguile_la-continuations.o  
>> libguile_la-convert.o libguile_la-debug.o libguile_la- 
>> deprecation.o libguile_la-deprecated.o libguile_la-discouraged.o  
>> libguile_la-dynwind.o libguile_la-environments.o libguile_la-eq.o  
>> libguile_la-error.o libguile_la-eval.o libguile_la-evalext.o  
>> libguile_la-extensions.o libguile_la-feature.o libguile_la- 
>> fluids.o libguile_la-fports.o libguile_la-futures.o libguile_la- 
>> gc.o libguile_la-gc-mark.o libguile_la-gc-segment.o libguile_la-gc- 
>> malloc.o libguile_la-gc-card.o libguile_la-gc-freelist.o  
>> libguile_la-gc_os_dep.o libguile_la-gdbint.o libguile_la-gh_data.o  
>> libguile_la-gh_eval.o libguile_la-gh_funcs.o libguile_la-gh_init.o  
>> libguile_la-gh_io.o libguile_la-gh_list.o libguile_la- 
>> gh_predicates.o libguile_la-goops.o libguile_la-gsubr.o  
>> libguile_la-guardians.o libguile_la-hash.o libguile_la-hashtab.o  
>> libguile_la-hooks.o libguile_la-i18n.o libguile_la-init.o  
>> libguile_la-inline.o libguile_la-ioext.o libguile_la-keywords.o  
>> libguile_la-lang.o libguile_la-list.o libguile_la-load.o  
>> libguile_la-macros.o libguile_la-mallocs.o libguile_la-modules.o  
>> libguile_la-numbers.o libguile_la-objects.o libguile_la-objprop.o  
>> libguile_la-options.o libguile_la-pairs.o libguile_la-ports.o  
>> libguile_la-print.o libguile_la-procprop.o libguile_la-procs.o  
>> libguile_la-properties.o libguile_la-random.o libguile_la-rdelim.o  
>> libguile_la-read.o libguile_la-root.o libguile_la-rw.o libguile_la- 
>> scmsigs.o libguile_la-script.o libguile_la-simpos.o libguile_la- 
>> smob.o libguile_la-sort.o libguile_la-srcprop.o libguile_la- 
>> stackchk.o libguile_la-stacks.o libguile_la-stime.o libguile_la- 
>> strings.o libguile_la-srfi-4.o libguile_la-srfi-13.o libguile_la- 
>> srfi-14.o libguile_la-strorder.o libguile_la-strports.o  
>> libguile_la-struct.o libguile_la-symbols.o libguile_la-threads.o  
>> libguile_la-null-threads.o libguile_la-throw.o libguile_la- 
>> values.o libguile_la-variable.o libguile_la-vectors.o libguile_la- 
>> version.o libguile_la-vports.o libguile_la-weaks.o libguile_la- 
>> ramap.o libguile_la-unif.o dynl.o filesys.o posix.o net_db.o  
>> socket.o regex-posix.o
>> ranlib: file: .libs/libguile.a(libguile_la-futures.o) has no symbols
>> ranlib: file: .libs/libguile.a(libguile_la-null-threads.o) has no  
>> symbols
>> ranlib .libs/libguile.a
>> ranlib: file: .libs/libguile.a(libguile_la-futures.o) has no symbols
>> ranlib: file: .libs/libguile.a(libguile_la-null-threads.o) has no  
>> symbols
>> creating libguile.la
>> (cd .libs && rm -f libguile.la && ln -s ../libguile.la libguile.la)
>> /usr/bin/gcc-4.0 -DHAVE_CONFIG_H  -I.. -I.. -I..  -I/opt/local/ 
>> include -I/opt/local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing- 
>> prototypes -Werror -MT guile-guile.o -MD -MP -MF .deps/guile- 
>> guile.Tpo -c -o guile-guile.o `test -f 'guile.c' || echo './'`guile.c
>> mv -f .deps/guile-guile.Tpo .deps/guile-guile.Po
>> /bin/sh ../libtool --tag=CC   --mode=link /usr/bin/gcc-4.0 -I/opt/ 
>> local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing-prototypes - 
>> Werror -dlpreopen force -I/opt/local/include -D_THREAD_SAFE  -L/ 
>> opt/local/lib -o guile guile-guile.o libguile.la -lgmp -lm -lltdl
>> rm -f .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
>> creating .libs/guileS.c
>> (cd .libs && /usr/bin/gcc-4.0  -O2 -c -fno-builtin "guileS.c")
>> rm -f .libs/guileS.c .libs/guile.nm .libs/guile.nmS .libs/guile.nmT
>> /usr/bin/gcc-4.0 -I/opt/local/include -D_THREAD_SAFE -O2 -Wall - 
>> Wmissing-prototypes -Werror .libs/guileS.o -I/opt/local/include - 
>> D_THREAD_SAFE -o .libs/guile guile-guile.o  -L/opt/local/ 
>> lib ./.libs/libguile.dylib -lintl /opt/local/lib/libgmp.dylib -lm - 
>> lltdl
>> /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
>> _lt__PROGRAM__LTX_preloaded_symbols
>> collect2: ld returned 1 exit status
>> make[3]: *** [guile] Error 1
>> make[2]: *** [all] Error 2
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all] Error 2
>>
>> Error: Status 1 encountered during processing.
>>
>
> Have you installed XCode (current version) and X11SDK?

Yes. Well, I have XCode 2.5 installed. I don't know of a newer  
version that I can install.


From derhindemith at googlemail.com  Mon Dec 15 14:37:47 2008
From: derhindemith at googlemail.com (James E. Bailey)
Date: Mon, 15 Dec 2008 23:37:47 +0100
Subject: guile doesn't build for me
In-Reply-To: <20081215222314.GC729@ninagal.withay.com>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>
	<49469EB5.9010004@macports.org>
	<8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>
	<4946B254.8040606@macports.org>
	<7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>
	<20081215212011.GE799@ninagal.withay.com>
	<4946D2F4.5060503@macports.org>
	<797619E2-1CF8-4BAC-8309-0710D9EE576F@googlemail.com>
	<20081215222314.GC729@ninagal.withay.com>
Message-ID: <97E98802-15CB-4CE1-9617-D57369F0FA2F@googlemail.com>


Am 15.12.2008 um 23:23 schrieb Bryan Blackburn:

> On Mon, Dec 15, 2008 at 11:12:41PM +0100, James E. Bailey said:
>>
>> Am 15.12.2008 um 22:58 schrieb Joshua Root:
>>
>>> Bryan Blackburn wrote:
>>>> On Mon, Dec 15, 2008 at 09:23:38PM +0100, James E. Bailey said:
>>>> [...]
>>>>> 21:07:35 bigdaddy Downloads:sudo /opt/local/bin/port install guile
>>>> [...]
>>>>> (cd .libs && /usr/bin/gcc-4.0  -O2 -c -fno-builtin "guileS.c")
>>>>> rm -f .libs/guileS.c .libs/guile.nm .libs/guile.nmS .libs/ 
>>>>> guile.nmT
>>>>> /usr/bin/gcc-4.0 -I/opt/local/include -D_THREAD_SAFE -O2 -Wall -
>>>>> Wmissing-prototypes -Werror .libs/guileS.o -I/opt/local/include -
>>>>> D_THREAD_SAFE -o .libs/guile guile-guile.o  -L/opt/local/lib
>>>>> ./.libs/
>>>>> libguile.dylib -lintl /opt/local/lib/libgmp.dylib -lm -lltdl
>>>>> /usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
>>>>> _lt__PROGRAM__LTX_preloaded_symbols
>>>>> collect2: ld returned 1 exit status
>>>>
>>>> Do you have libtool2 someplace?  Either one of the ports (libtool-
>>>> devel and
>>>> libtool2) or somewhere else?
>>>
>>> There actually isn't a libtool2. The libtool port is meant to be
>>> updated
>>> to 2.x soon, but it hasn't happened yet. Could still be libtool- 
>>> devel,
>>> of course.
>>>
>>> - Josh
>>
>> Yes, I have libtool 2.2.6 installed. I usually just build things  
>> myself,
>> outside of guile. Is libtool 2 a problem? Shouldn't macports build  
>> and
>> configure things itself, regardless of what I have installed in / 
>> usr/local
>> and ~/ ?
>
> The first hit when googling lt__PROGRAM__LTX_preloaded_symbols is  
> about
> building guile, and suggests it may be an incompatibility issue with
> libtool2.
>
> Having stuff in /usr/local is problematic because some tools like to
> look there regardless of what port says, eg, the -lltdl in the  
> above compile
> line may be picking up libtool2's version in /usr/local.
>
> Bryan

I actually just installed libtool 1.8.5, and here is the error log:

jamesebaileys-computer:/Users/jamesebailey/Downloads/guile-1.8.6  
root# ./configure -q && make && make install
make  all-recursive
Making all in oop
Making all in goops
make[3]: Nothing to be done for `all'.
make[3]: Nothing to be done for `all-am'.
Making all in libguile
Generating libpath.h...
./guile-snarf -o load.x load.c -DHAVE_CONFIG_H -I.. -I.. -I.. -I/usr/ 
local/include -g -O2 -Wall -Wmissing-prototypes -Werror
make  all-am
/bin/sh ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H   - 
I.. -I.. -I.. -I/usr/local/include -I/usr/local/include - 
D_THREAD_SAFE  -g -O2 -Wall -Wmissing-prototypes -Werror -MT  
libguile_la-load.lo -MD -MP -MF .deps/libguile_la-load.Tpo -c -o  
libguile_la-load.lo `test -f 'load.c' || echo './'`load.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I.. -I.. -I.. -I/usr/local/ 
include -I/usr/local/include -D_THREAD_SAFE -g -O2 -Wall -Wmissing- 
prototypes -Werror -MT libguile_la-load.lo -MD -MP -MF .deps/ 
libguile_la-load.Tpo -c load.c  -fno-common -DPIC -o .libs/ 
libguile_la-load.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I.. -I.. -I.. -I/usr/local/ 
include -I/usr/local/include -D_THREAD_SAFE -g -O2 -Wall -Wmissing- 
prototypes -Werror -MT libguile_la-load.lo -MD -MP -MF .deps/ 
libguile_la-load.Tpo -c load.c -o libguile_la-load.o >/dev/null 2>&1
mv -f .deps/libguile_la-load.Tpo .deps/libguile_la-load.Plo
/bin/sh ../libtool --tag=CC   --mode=link gcc -I/usr/local/include - 
D_THREAD_SAFE  -g -O2 -Wall -Wmissing-prototypes -Werror -L/usr/local/ 
lib -lintl -L/usr/local/lib -liconv -lc -R/usr/local/lib -Wl,- 
framework -Wl,CoreFoundation -version-info 20:0:3 -export-dynamic -no- 
undefined  -o libguile.la -rpath /usr/local/lib libguile_la-alist.lo  
libguile_la-arbiters.lo libguile_la-async.lo libguile_la-backtrace.lo  
libguile_la-boolean.lo libguile_la-chars.lo libguile_la- 
continuations.lo libguile_la-convert.lo libguile_la-debug.lo  
libguile_la-deprecation.lo libguile_la-deprecated.lo libguile_la- 
discouraged.lo libguile_la-dynwind.lo libguile_la-environments.lo  
libguile_la-eq.lo libguile_la-error.lo libguile_la-eval.lo  
libguile_la-evalext.lo libguile_la-extensions.lo libguile_la- 
feature.lo libguile_la-fluids.lo libguile_la-fports.lo libguile_la- 
futures.lo libguile_la-gc.lo libguile_la-gc-mark.lo libguile_la-gc- 
segment.lo libguile_la-gc-malloc.lo libguile_la-gc-card.lo  
libguile_la-gc-freelist.lo libguile_la-gc_os_dep.lo libguile_la- 
gdbint.lo libguile_la-gh_data.lo libguile_la-gh_eval.lo libguile_la- 
gh_funcs.lo libguile_la-gh_init.lo libguile_la-gh_io.lo libguile_la- 
gh_list.lo libguile_la-gh_predicates.lo libguile_la-goops.lo  
libguile_la-gsubr.lo libguile_la-guardians.lo libguile_la-hash.lo  
libguile_la-hashtab.lo libguile_la-hooks.lo libguile_la-i18n.lo  
libguile_la-init.lo libguile_la-inline.lo libguile_la-ioext.lo  
libguile_la-keywords.lo libguile_la-lang.lo libguile_la-list.lo  
libguile_la-load.lo libguile_la-macros.lo libguile_la-mallocs.lo  
libguile_la-modules.lo libguile_la-numbers.lo libguile_la-objects.lo  
libguile_la-objprop.lo libguile_la-options.lo libguile_la-pairs.lo  
libguile_la-ports.lo libguile_la-print.lo libguile_la-procprop.lo  
libguile_la-procs.lo libguile_la-properties.lo libguile_la-random.lo  
libguile_la-rdelim.lo libguile_la-read.lo libguile_la-root.lo  
libguile_la-rw.lo libguile_la-scmsigs.lo libguile_la-script.lo  
libguile_la-simpos.lo libguile_la-smob.lo libguile_la-sort.lo  
libguile_la-srcprop.lo libguile_la-stackchk.lo libguile_la-stacks.lo  
libguile_la-stime.lo libguile_la-strings.lo libguile_la-srfi-4.lo  
libguile_la-srfi-13.lo libguile_la-srfi-14.lo libguile_la-strorder.lo  
libguile_la-strports.lo libguile_la-struct.lo libguile_la-symbols.lo  
libguile_la-threads.lo libguile_la-null-threads.lo libguile_la- 
throw.lo libguile_la-values.lo libguile_la-variable.lo libguile_la- 
vectors.lo libguile_la-version.lo libguile_la-vports.lo libguile_la- 
weaks.lo libguile_la-ramap.lo libguile_la-unif.lo dynl.lo filesys.lo  
posix.lo net_db.lo socket.lo regex-posix.lo -lgmp -lm -lltdl
libtool: link: rm -fr  .libs/libguile.17.dylib .libs/libguile. 
17.dylib.dSYM .libs/libguile.a .libs/libguile.dylib .libs/ 
libguile.la .libs/libguile.lai
libtool: link: gcc -dynamiclib  -o .libs/libguile.17.dylib  .libs/ 
libguile_la-alist.o .libs/libguile_la-arbiters.o .libs/libguile_la- 
async.o .libs/libguile_la-backtrace.o .libs/libguile_la- 
boolean.o .libs/libguile_la-chars.o .libs/libguile_la- 
continuations.o .libs/libguile_la-convert.o .libs/libguile_la- 
debug.o .libs/libguile_la-deprecation.o .libs/libguile_la- 
deprecated.o .libs/libguile_la-discouraged.o .libs/libguile_la- 
dynwind.o .libs/libguile_la-environments.o .libs/libguile_la- 
eq.o .libs/libguile_la-error.o .libs/libguile_la-eval.o .libs/ 
libguile_la-evalext.o .libs/libguile_la-extensions.o .libs/ 
libguile_la-feature.o .libs/libguile_la-fluids.o .libs/libguile_la- 
fports.o .libs/libguile_la-futures.o .libs/libguile_la-gc.o .libs/ 
libguile_la-gc-mark.o .libs/libguile_la-gc-segment.o .libs/ 
libguile_la-gc-malloc.o .libs/libguile_la-gc-card.o .libs/libguile_la- 
gc-freelist.o .libs/libguile_la-gc_os_dep.o .libs/libguile_la- 
gdbint.o .libs/libguile_la-gh_data.o .libs/libguile_la- 
gh_eval.o .libs/libguile_la-gh_funcs.o .libs/libguile_la- 
gh_init.o .libs/libguile_la-gh_io.o .libs/libguile_la-gh_list.o .libs/ 
libguile_la-gh_predicates.o .libs/libguile_la-goops.o .libs/ 
libguile_la-gsubr.o .libs/libguile_la-guardians.o .libs/libguile_la- 
hash.o .libs/libguile_la-hashtab.o .libs/libguile_la-hooks.o .libs/ 
libguile_la-i18n.o .libs/libguile_la-init.o .libs/libguile_la- 
inline.o .libs/libguile_la-ioext.o .libs/libguile_la-keywords.o .libs/ 
libguile_la-lang.o .libs/libguile_la-list.o .libs/libguile_la- 
load.o .libs/libguile_la-macros.o .libs/libguile_la-mallocs.o .libs/ 
libguile_la-modules.o .libs/libguile_la-numbers.o .libs/libguile_la- 
objects.o .libs/libguile_la-objprop.o .libs/libguile_la- 
options.o .libs/libguile_la-pairs.o .libs/libguile_la-ports.o .libs/ 
libguile_la-print.o .libs/libguile_la-procprop.o .libs/libguile_la- 
procs.o .libs/libguile_la-properties.o .libs/libguile_la- 
random.o .libs/libguile_la-rdelim.o .libs/libguile_la-read.o .libs/ 
libguile_la-root.o .libs/libguile_la-rw.o .libs/libguile_la- 
scmsigs.o .libs/libguile_la-script.o .libs/libguile_la-simpos.o .libs/ 
libguile_la-smob.o .libs/libguile_la-sort.o .libs/libguile_la- 
srcprop.o .libs/libguile_la-stackchk.o .libs/libguile_la- 
stacks.o .libs/libguile_la-stime.o .libs/libguile_la-strings.o .libs/ 
libguile_la-srfi-4.o .libs/libguile_la-srfi-13.o .libs/libguile_la- 
srfi-14.o .libs/libguile_la-strorder.o .libs/libguile_la- 
strports.o .libs/libguile_la-struct.o .libs/libguile_la- 
symbols.o .libs/libguile_la-threads.o .libs/libguile_la-null- 
threads.o .libs/libguile_la-throw.o .libs/libguile_la-values.o .libs/ 
libguile_la-variable.o .libs/libguile_la-vectors.o .libs/libguile_la- 
version.o .libs/libguile_la-vports.o .libs/libguile_la-weaks.o .libs/ 
libguile_la-ramap.o .libs/libguile_la-unif.o .libs/dynl.o .libs/ 
filesys.o .libs/posix.o .libs/net_db.o .libs/socket.o .libs/regex- 
posix.o   -L/usr/local/lib /usr/local/lib/libintl.dylib -L/usr/lib / 
usr/lib/libiconv.dylib /usr/local/lib/libiconv.dylib -lc /usr/local/ 
lib/libgmp.dylib -lm /usr/local/lib/libltdl.dylib -ldl  -Wl,- 
framework -Wl,CoreFoundation   -install_name  /usr/local/lib/libguile. 
17.dylib -compatibility_version 21 -current_version 21.0 -Wl,- 
single_module
libtool: link: dsymutil .libs/libguile.17.dylib || :
warning: no debug map in executable (-arch i386)
libtool: link: (cd ".libs" && rm -f "libguile.dylib" && ln -s  
"libguile.17.dylib" "libguile.dylib")
libtool: link: ar cru .libs/libguile.a  libguile_la-alist.o  
libguile_la-arbiters.o libguile_la-async.o libguile_la-backtrace.o  
libguile_la-boolean.o libguile_la-chars.o libguile_la-continuations.o  
libguile_la-convert.o libguile_la-debug.o libguile_la-deprecation.o  
libguile_la-deprecated.o libguile_la-discouraged.o libguile_la- 
dynwind.o libguile_la-environments.o libguile_la-eq.o libguile_la- 
error.o libguile_la-eval.o libguile_la-evalext.o libguile_la- 
extensions.o libguile_la-feature.o libguile_la-fluids.o libguile_la- 
fports.o libguile_la-futures.o libguile_la-gc.o libguile_la-gc-mark.o  
libguile_la-gc-segment.o libguile_la-gc-malloc.o libguile_la-gc- 
card.o libguile_la-gc-freelist.o libguile_la-gc_os_dep.o libguile_la- 
gdbint.o libguile_la-gh_data.o libguile_la-gh_eval.o libguile_la- 
gh_funcs.o libguile_la-gh_init.o libguile_la-gh_io.o libguile_la- 
gh_list.o libguile_la-gh_predicates.o libguile_la-goops.o libguile_la- 
gsubr.o libguile_la-guardians.o libguile_la-hash.o libguile_la- 
hashtab.o libguile_la-hooks.o libguile_la-i18n.o libguile_la-init.o  
libguile_la-inline.o libguile_la-ioext.o libguile_la-keywords.o  
libguile_la-lang.o libguile_la-list.o libguile_la-load.o libguile_la- 
macros.o libguile_la-mallocs.o libguile_la-modules.o libguile_la- 
numbers.o libguile_la-objects.o libguile_la-objprop.o libguile_la- 
options.o libguile_la-pairs.o libguile_la-ports.o libguile_la-print.o  
libguile_la-procprop.o libguile_la-procs.o libguile_la-properties.o  
libguile_la-random.o libguile_la-rdelim.o libguile_la-read.o  
libguile_la-root.o libguile_la-rw.o libguile_la-scmsigs.o libguile_la- 
script.o libguile_la-simpos.o libguile_la-smob.o libguile_la-sort.o  
libguile_la-srcprop.o libguile_la-stackchk.o libguile_la-stacks.o  
libguile_la-stime.o libguile_la-strings.o libguile_la-srfi-4.o  
libguile_la-srfi-13.o libguile_la-srfi-14.o libguile_la-strorder.o  
libguile_la-strports.o libguile_la-struct.o libguile_la-symbols.o  
libguile_la-threads.o libguile_la-null-threads.o libguile_la-throw.o  
libguile_la-values.o libguile_la-variable.o libguile_la-vectors.o  
libguile_la-version.o libguile_la-vports.o libguile_la-weaks.o  
libguile_la-ramap.o libguile_la-unif.o dynl.o filesys.o posix.o  
net_db.o socket.o regex-posix.o
libtool: link: ranlib .libs/libguile.a
libtool: link: ( cd ".libs" && rm -f "libguile.la" && ln -s "../ 
libguile.la" "libguile.la" )
gcc -DHAVE_CONFIG_H   -I.. -I.. -I.. -I/usr/local/include -I/usr/ 
local/include -D_THREAD_SAFE  -g -O2 -Wall -Wmissing-prototypes - 
Werror -MT guile-guile.o -MD -MP -MF .deps/guile-guile.Tpo -c -o  
guile-guile.o `test -f 'guile.c' || echo './'`guile.c
mv -f .deps/guile-guile.Tpo .deps/guile-guile.Po
/bin/sh ../libtool --tag=CC   --mode=link gcc -I/usr/local/include - 
D_THREAD_SAFE  -g -O2 -Wall -Wmissing-prototypes -Werror -I/usr/local/ 
include -D_THREAD_SAFE   -o guile guile-guile.o libguile.la -lgmp -lm  
-lltdl
libtool: link: gcc -I/usr/local/include -D_THREAD_SAFE -g -O2 -Wall - 
Wmissing-prototypes -Werror -I/usr/local/include -D_THREAD_SAFE - 
o .libs/guile guile-guile.o  ./.libs/libguile.dylib -L/usr/local/lib / 
usr/local/lib/libintl.dylib /usr/lib/libiconv.dylib /usr/local/lib/ 
libiconv.dylib -lc /usr/local/lib/libgmp.dylib -lm /usr/local/lib/ 
libltdl.dylib -ldl
cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc  
chars.doc continuations.doc debug.doc deprecation.doc deprecated.doc  
discouraged.doc dynl.doc dynwind.doc environments.doc eq.doc  
error.doc eval.doc evalext.doc extensions.doc feature.doc fluids.doc  
fports.doc futures.doc gc.doc goops.doc gsubr.doc gc-mark.doc gc- 
segment.doc gc-malloc.doc gc-card.doc guardians.doc hash.doc  
hashtab.doc hooks.doc i18n.doc init.doc ioext.doc keywords.doc  
lang.doc list.doc load.doc macros.doc mallocs.doc modules.doc  
numbers.doc objects.doc objprop.doc options.doc pairs.doc ports.doc  
print.doc procprop.doc procs.doc properties.doc random.doc rdelim.doc  
read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc  
sort.doc srcprop.doc stackchk.doc stacks.doc stime.doc strings.doc  
srfi-4.doc srfi-13.doc srfi-14.doc strorder.doc strports.doc  
struct.doc symbols.doc threads.doc throw.doc values.doc variable.doc  
vectors.doc version.doc vports.doc weaks.doc ramap.doc unif.doc  
dynl.doc filesys.doc posix.doc net_db.doc socket.doc regex-posix.doc  
| GUILE="/Users/jamesebailey/Downloads/guile-1.8.6/pre-inst-guile" ../ 
scripts/snarf-check-and-output-texi          > guile-procedures.texi  
|| { rm guile-procedures.texi; false; }
rm -f guile-procedures.txt
makeinfo --force -o guile-procedures.txt guile-procedures.texi ||  
test -f guile-procedures.txt
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:10344: Cross reference to nonexistent node `Backslash  
Escapes' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:10044: Cross reference to nonexistent node `Network  
Address Conversion' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:9993: Cross reference to nonexistent node `Network  
Databases' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:9943: Cross reference to nonexistent node `Network  
Databases' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:8782: Cross reference to nonexistent node `Ports and  
File Descriptors' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:8770: Cross reference to nonexistent node  
`Closing' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:8090: Cross reference to nonexistent node `Hash  
Tables' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:8083: Cross reference to nonexistent node `Hash  
Tables' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:8076: Cross reference to nonexistent node `Hash  
Tables' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:7990: Cross reference to nonexistent node `File  
Ports' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:7334: Cross reference to nonexistent node  
`Vtables' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:5939: Cross reference to nonexistent node `Character  
Sets' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:5917: Cross reference to nonexistent node `Character  
Sets' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:4907: Cross reference to nonexistent node  
`Locales' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:3921: Cross reference to nonexistent node `File  
Ports' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:3699: Cross reference to nonexistent node `Ports and  
File Descriptors' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:3688: Cross reference to nonexistent node `Ports and  
File Descriptors' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:3677: Cross reference to nonexistent node `Ports and  
File Descriptors' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:2514: Cross reference to nonexistent node `File  
Ports' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:2096: Cross reference to nonexistent node `Hash  
Tables' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:2089: Cross reference to nonexistent node `Hash  
Tables' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:2082: Cross reference to nonexistent node `Hash  
Tables' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:1634: Cross reference to nonexistent node `Ports and  
File Descriptors' (perhaps incorrect sectioning?).
/Users/jamesebailey/Downloads/guile-1.8.6/libguile//guile- 
procedures.texi:1620: Cross reference to nonexistent node `Ports and  
File Descriptors' (perhaps incorrect sectioning?).
Making all in ice-9
Making all in debugger
make[3]: Nothing to be done for `all'.
Making all in debugging
make[3]: Nothing to be done for `all'.
make[3]: Nothing to be done for `all-am'.
Making all in guile-config
rm -f guile-config.tmp
sed < ./guile-config.in > guile-config.tmp \
     -e 's|@-bindir-@|/usr/local/bin|' \
     -e s:@-GUILE_VERSION-@:1.8.6:
chmod +x guile-config.tmp
mv guile-config.tmp guile-config
Making all in guile-readline
make  all-recursive
Making all in ice-9
make[4]: Nothing to be done for `all'.
/bin/sh ./libtool --tag=CC   --mode=link gcc  -g -O2 -version-info  
17:3:0 -export-dynamic -no-undefined  -o libguilereadline-v-17.la - 
rpath /usr/local/lib readline.lo ../libguile/libguile.la -lreadline - 
lncurses
libtool: link: gcc -dynamiclib  -o .libs/libguilereadline- 
v-17.17.dylib  .libs/readline.o   ../libguile/.libs/libguile.dylib -L/ 
usr/local/lib -L/usr/lib /usr/local/lib/libintl.dylib /usr/lib/ 
libiconv.dylib /usr/local/lib/libiconv.dylib -lc /usr/local/lib/ 
libgmp.dylib -lm /usr/local/lib/libltdl.dylib -ldl -lreadline - 
lncurses    -install_name  /usr/local/lib/libguilereadline- 
v-17.17.dylib -compatibility_version 18 -current_version 18.3 -Wl,- 
single_module
ld: warning multiple definitions of symbol _rl_free_line_state
.libs/readline.o definition of _rl_free_line_state in section  
(__TEXT,__text)
/usr/local/lib/libreadline.dylib(signals.so) definition of  
_rl_free_line_state
ld: warning multiple definitions of symbol _rl_cleanup_after_signal
.libs/readline.o definition of _rl_cleanup_after_signal in section  
(__TEXT,__text)
/usr/local/lib/libreadline.dylib(signals.so) definition of  
_rl_cleanup_after_signal
ld: Undefined symbols:
__rl_init_argument
/usr/libexec/gcc/i686-apple-darwin8/4.0.1/libtool: internal link edit  
command failed
make[4]: *** [libguilereadline-v-17.la] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2


From jmr at macports.org  Mon Dec 15 14:42:49 2008
From: jmr at macports.org (Joshua Root)
Date: Tue, 16 Dec 2008 09:42:49 +1100
Subject: guile doesn't build for me
In-Reply-To: <97E98802-15CB-4CE1-9617-D57369F0FA2F@googlemail.com>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>	<49469EB5.9010004@macports.org>	<8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>	<4946B254.8040606@macports.org>	<7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>	<20081215212011.GE799@ninagal.withay.com>	<4946D2F4.5060503@macports.org>	<797619E2-1CF8-4BAC-8309-0710D9EE576F@googlemail.com>	<20081215222314.GC729@ninagal.withay.com>
	<97E98802-15CB-4CE1-9617-D57369F0FA2F@googlemail.com>
Message-ID: <4946DD69.4050000@macports.org>

James E. Bailey wrote:
> /bin/sh ./libtool --tag=CC   --mode=link gcc  -g -O2 -version-info
> 17:3:0 -export-dynamic -no-undefined  -o libguilereadline-v-17.la -rpath
> /usr/local/lib readline.lo ../libguile/libguile.la -lreadline -lncurses
> libtool: link: gcc -dynamiclib  -o .libs/libguilereadline-v-17.17.dylib 
> .libs/readline.o   ../libguile/.libs/libguile.dylib -L/usr/local/lib
> -L/usr/lib /usr/local/lib/libintl.dylib /usr/lib/libiconv.dylib
> /usr/local/lib/libiconv.dylib -lc /usr/local/lib/libgmp.dylib -lm
> /usr/local/lib/libltdl.dylib -ldl -lreadline -lncurses    -install_name 
> /usr/local/lib/libguilereadline-v-17.17.dylib -compatibility_version 18
> -current_version 18.3 -Wl,-single_module
> ld: warning multiple definitions of symbol _rl_free_line_state
> .libs/readline.o definition of _rl_free_line_state in section
> (__TEXT,__text)
> /usr/local/lib/libreadline.dylib(signals.so) definition of
> _rl_free_line_state

Yep, definitely a problem with stuff in /usr/local. We'd like ports to
ignore /usr/local, but just about everything is hard-coded to look in
there, and there's currently no generic way we can make them stop.

- Josh

From derhindemith at googlemail.com  Mon Dec 15 14:56:18 2008
From: derhindemith at googlemail.com (James E. Bailey)
Date: Mon, 15 Dec 2008 23:56:18 +0100
Subject: guile doesn't build for me
In-Reply-To: <4946DD69.4050000@macports.org>
References: <B3A30665-0E3B-43F8-B4B2-547A3CFAAACB@googlemail.com>	<49469EB5.9010004@macports.org>	<8D00F623-3522-4DCF-BFFE-D601EABEEEB9@bellsouth.net>	<4946B254.8040606@macports.org>	<7A996B28-9785-47A0-99C8-645DA2CDDA64@googlemail.com>	<20081215212011.GE799@ninagal.withay.com>	<4946D2F4.5060503@macports.org>	<797619E2-1CF8-4BAC-8309-0710D9EE576F@googlemail.com>	<20081215222314.GC729@ninagal.withay.com>
	<97E98802-15CB-4CE1-9617-D57369F0FA2F@googlemail.com>
	<4946DD69.4050000@macports.org>
Message-ID: <659AEAB1-3B8A-4043-BDE9-FFE3DED98E56@googlemail.com>


Am 15.12.2008 um 23:42 schrieb Joshua Root:

> James E. Bailey wrote:
>> /bin/sh ./libtool --tag=CC   --mode=link gcc  -g -O2 -version-info
>> 17:3:0 -export-dynamic -no-undefined  -o libguilereadline-v-17.la - 
>> rpath
>> /usr/local/lib readline.lo ../libguile/libguile.la -lreadline - 
>> lncurses
>> libtool: link: gcc -dynamiclib  -o .libs/libguilereadline- 
>> v-17.17.dylib
>> .libs/readline.o   ../libguile/.libs/libguile.dylib -L/usr/local/lib
>> -L/usr/lib /usr/local/lib/libintl.dylib /usr/lib/libiconv.dylib
>> /usr/local/lib/libiconv.dylib -lc /usr/local/lib/libgmp.dylib -lm
>> /usr/local/lib/libltdl.dylib -ldl -lreadline -lncurses    - 
>> install_name
>> /usr/local/lib/libguilereadline-v-17.17.dylib - 
>> compatibility_version 18
>> -current_version 18.3 -Wl,-single_module
>> ld: warning multiple definitions of symbol _rl_free_line_state
>> .libs/readline.o definition of _rl_free_line_state in section
>> (__TEXT,__text)
>> /usr/local/lib/libreadline.dylib(signals.so) definition of
>> _rl_free_line_state
>
> Yep, definitely a problem with stuff in /usr/local. We'd like ports to
> ignore /usr/local, but just about everything is hard-coded to look in
> there, and there's currently no generic way we can make them stop.
>
> - Josh

And I just realised that I sent the wrong error message (too many  
windows open). Apparently, downgrading to libtool 1.5.8 solved my  
problems. Thanks for the tip!


From vincent-opdarw at vinc17.org  Mon Dec 15 17:37:59 2008
From: vincent-opdarw at vinc17.org (Vincent Lefevre)
Date: Tue, 16 Dec 2008 02:37:59 +0100
Subject: Error upgrading xrender on Panther
In-Reply-To: <AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
Message-ID: <20081216013759.GA15002@prunille.vinc17.org>

On 2008-12-15 00:12:25 -0800, Jeremy Huddleston wrote:
> The problem lies in some sort of conflict when both /usr/X11R6/lib/ 
> libX11.dylib and /opt/local/lib/libX11/dylib are linked to by your  
> executable... so... yeah... my short term solution to offer you is  
> either
>
> 1) use all macports for your X11 dependencies (maybe setting x11prefix  
> to /opt/local in macports.conf will be enough... you should probably  
> then install xorg-libX11 so you don't accidently pull in XFree86)
>
> or
>
> 2) use none of the xorg-* ports in macports

How can one do that? pango depends on xrender, which depends on
xorg-renderproto!

-- 
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 jeremyhu at macports.org  Mon Dec 15 19:14:37 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Mon, 15 Dec 2008 19:14:37 -0800
Subject: Error upgrading xrender on Panther
In-Reply-To: <4946DA6C.4020502@macports.org>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
	<4946B934.2040700@macports.org>
	<C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>
	<EC8A4216-ADC7-4270-A92C-D5C6B29CA39B@bellsouth.net>
	<E247A2D5-813E-423B-9A53-6F9B3F9DA0B1@comcast.net>
	<4946DA6C.4020502@macports.org>
Message-ID: <B9DF4334-5D8B-4E8C-9F06-11AD5977A082@macports.org>

On Dec 15, 2008, at 14:30, Joshua Root wrote:

> Frank J. R. Hanstick wrote:
>> Hello,
>>    Attached is a debug sample of the loop.  I tried "sudo port -d
>> upgrade installed >ports.log" and the output only went to the  
>> Terminal
>> window.  So, I copied a sample to a TextEdit file.  If you need  
>> more, I
>> can rerun because it is repeatable.
>
> Do you get the same result if you upgrade outdated rather than
> installed, though?

As mentioned earlier, resync and this should be fixed...


From jeremyhu at macports.org  Mon Dec 15 19:16:30 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Mon, 15 Dec 2008 19:16:30 -0800
Subject: Error upgrading xrender on Panther
In-Reply-To: <20081216013759.GA15002@prunille.vinc17.org>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
	<20081216013759.GA15002@prunille.vinc17.org>
Message-ID: <613C2ED1-528E-40C2-BE4C-25E99A9548B6@macports.org>


On Dec 15, 2008, at 17:37, Vincent Lefevre wrote:

> On 2008-12-15 00:12:25 -0800, Jeremy Huddleston wrote:
>> The problem lies in some sort of conflict when both /usr/X11R6/lib/
>> libX11.dylib and /opt/local/lib/libX11/dylib are linked to by your
>> executable... so... yeah... my short term solution to offer you is
>> either
>>
>> 1) use all macports for your X11 dependencies (maybe setting  
>> x11prefix
>> to /opt/local in macports.conf will be enough... you should probably
>> then install xorg-libX11 so you don't accidently pull in XFree86)
>>
>> or
>>
>> 2) use none of the xorg-* ports in macports
>
> How can one do that? pango depends on xrender, which depends on
> xorg-renderproto!

It depends on it through lib:...: dependencies which I've tested to  
work with Tiger's installed X11.

--Jeremy


From trog24 at comcast.net  Mon Dec 15 20:02:54 2008
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Mon, 15 Dec 2008 20:02:54 -0800
Subject: Error upgrading xrender on Panther
In-Reply-To: <B9DF4334-5D8B-4E8C-9F06-11AD5977A082@macports.org>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
	<4946B934.2040700@macports.org>
	<C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>
	<EC8A4216-ADC7-4270-A92C-D5C6B29CA39B@bellsouth.net>
	<E247A2D5-813E-423B-9A53-6F9B3F9DA0B1@comcast.net>
	<4946DA6C.4020502@macports.org>
	<B9DF4334-5D8B-4E8C-9F06-11AD5977A082@macports.org>
Message-ID: <C329C323-4B97-4C16-913B-41F2EFF019D0@comcast.net>

Hello,
	I sent the following in an earlier posting; but, the log file was  
attached and it exceeds the maximum file size.  It got caught  
awaiting moderator approval.  Hit a choke point I guess.  In any  
case, here is the non-file text to keep you up to date.
Hello,
	I used the "sudo port upgrade outdated" after I did a "sudo port  
sync" and everything worked as advertised.  I actually made it  
through the upgrade process.  Now, I do not think that I can repeat  
the problem because all the ports referenced are now up to date.   
Even the latest guile built and installed.  Ruined a debugging  
opportunity.  I did get a proper log file for the last "sudo port -d  
upgrade installed" and will attach it so that you can peruse at your  
convenience.  Thank you one and all for the help.
Frank

On Dec 15, 2008, at 7:14 PM, Jeremy Huddleston wrote:

> On Dec 15, 2008, at 14:30, Joshua Root wrote:
>
>> Frank J. R. Hanstick wrote:
>>> Hello,
>>>    Attached is a debug sample of the loop.  I tried "sudo port -d
>>> upgrade installed >ports.log" and the output only went to the  
>>> Terminal
>>> window.  So, I copied a sample to a TextEdit file.  If you need  
>>> more, I
>>> can rerun because it is repeatable.
>>
>> Do you get the same result if you upgrade outdated rather than
>> installed, though?
>
> As mentioned earlier, resync and this should be fixed...
>


From jmr at macports.org  Mon Dec 15 20:52:08 2008
From: jmr at macports.org (Joshua Root)
Date: Tue, 16 Dec 2008 15:52:08 +1100
Subject: Error upgrading xrender on Panther
In-Reply-To: <B9DF4334-5D8B-4E8C-9F06-11AD5977A082@macports.org>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
	<4946B934.2040700@macports.org>
	<C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>
	<EC8A4216-ADC7-4270-A92C-D5C6B29CA39B@bellsouth.net>
	<E247A2D5-813E-423B-9A53-6F9B3F9DA0B1@comcast.net>
	<4946DA6C.4020502@macports.org>
	<B9DF4334-5D8B-4E8C-9F06-11AD5977A082@macports.org>
Message-ID: <494733F8.5040500@macports.org>

Jeremy Huddleston wrote:
> On Dec 15, 2008, at 14:30, Joshua Root wrote:
> 
>> Frank J. R. Hanstick wrote:
>>> Hello,
>>>    Attached is a debug sample of the loop.  I tried "sudo port -d
>>> upgrade installed >ports.log" and the output only went to the Terminal
>>> window.  So, I copied a sample to a TextEdit file.  If you need more, I
>>> can rerun because it is repeatable.
>>
>> Do you get the same result if you upgrade outdated rather than
>> installed, though?
> 
> As mentioned earlier, resync and this should be fixed...

I was interested in the reported infinite loop rather than the specific
port failure. But it looks like it was just `port upgrade installed`
behaving as expected. (Kind of annoying when there's a failure, but
still expected.)

- Josh

From trog24 at comcast.net  Mon Dec 15 22:38:12 2008
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Mon, 15 Dec 2008 22:38:12 -0800
Subject: Error upgrading xrender on Panther
In-Reply-To: <494733F8.5040500@macports.org>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
	<4946B934.2040700@macports.org>
	<C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>
	<EC8A4216-ADC7-4270-A92C-D5C6B29CA39B@bellsouth.net>
	<E247A2D5-813E-423B-9A53-6F9B3F9DA0B1@comcast.net>
	<4946DA6C.4020502@macports.org>
	<B9DF4334-5D8B-4E8C-9F06-11AD5977A082@macports.org>
	<494733F8.5040500@macports.org>
Message-ID: <B866DFBF-76F9-4E0B-B0B0-3635B9E3D2DF@comcast.net>

Hello,
	It is quite possible that the only way into the infinite loop is via  
a port failure under certain circumstances.  Problems usually arise  
when anomalies occur and not when things run as expected because not  
all anomalies can be planned for.  If not, sorry  to disappoint you.
Frank

On Dec 15, 2008, at 8:52 PM, Joshua Root wrote:

> Jeremy Huddleston wrote:
>> On Dec 15, 2008, at 14:30, Joshua Root wrote:
>>
>>> Frank J. R. Hanstick wrote:
>>>> Hello,
>>>>    Attached is a debug sample of the loop.  I tried "sudo port -d
>>>> upgrade installed >ports.log" and the output only went to the  
>>>> Terminal
>>>> window.  So, I copied a sample to a TextEdit file.  If you need  
>>>> more, I
>>>> can rerun because it is repeatable.
>>>
>>> Do you get the same result if you upgrade outdated rather than
>>> installed, though?
>>
>> As mentioned earlier, resync and this should be fixed...
>
> I was interested in the reported infinite loop rather than the  
> specific
> port failure. But it looks like it was just `port upgrade installed`
> behaving as expected. (Kind of annoying when there's a failure, but
> still expected.)
>
> - Josh


From jmr at macports.org  Tue Dec 16 00:23:16 2008
From: jmr at macports.org (Joshua Root)
Date: Tue, 16 Dec 2008 19:23:16 +1100
Subject: Error upgrading xrender on Panther
In-Reply-To: <B866DFBF-76F9-4E0B-B0B0-3635B9E3D2DF@comcast.net>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
	<4946B934.2040700@macports.org>
	<C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>
	<EC8A4216-ADC7-4270-A92C-D5C6B29CA39B@bellsouth.net>
	<E247A2D5-813E-423B-9A53-6F9B3F9DA0B1@comcast.net>
	<4946DA6C.4020502@macports.org>
	<B9DF4334-5D8B-4E8C-9F06-11AD5977A082@macports.org>
	<494733F8.5040500@macports.org>
	<B866DFBF-76F9-4E0B-B0B0-3635B9E3D2DF@comcast.net>
Message-ID: <49476574.2030602@macports.org>

Frank J. R. Hanstick wrote:
> Hello,
>     It is quite possible that the only way into the infinite loop is via
> a port failure under certain circumstances.  Problems usually arise when
> anomalies occur and not when things run as expected because not all
> anomalies can be planned for.  If not, sorry  to disappoint you.

Fair enough, but I would have expected to see a large number of
iterations given the command you used, and we have no evidence that the
number of iterations would have been unbounded and not just large.

- Josh

From krischik at users.sourceforge.net  Tue Dec 16 02:45:33 2008
From: krischik at users.sourceforge.net (Martin Krischik)
Date: Tue, 16 Dec 2008 11:45:33 +0100
Subject: Problems with Track after login
Message-ID: <48A1B24F-F45B-4122-87DA-F306A93F79A4@users.sourceforge.net>

Hello,

After I logged in track only displays the following error message:

---------------------------
Traceback (most recent call last):
   File "/opt/local/lib/python2.5/site-packages/trac/web/api.py", line  
367, in send_error
     'text/html')
   File "/opt/local/lib/python2.5/site-packages/trac/web/chrome.py",  
line 706, in render_template
     if not req.session or not int(req.session.get('accesskeys', 0)):
   File "/opt/local/lib/python2.5/site-packages/trac/web/api.py", line  
194, in __getattr__
     value = self.callbacks[name](self)
   File "/opt/local/lib/python2.5/site-packages/trac/web/main.py",  
line 264, in _get_session
     return Session(self.env, req)
   File "/opt/local/lib/python2.5/site-packages/trac/web/session.py",  
line 156, in __init__
     self.promote_session(sid)
   File "/opt/local/lib/python2.5/site-packages/trac/web/session.py",  
line 214, in promote_session
     "WHERE sid=%s OR sid=%s ", (sid, self.req.authname))
   File "/opt/local/lib/python2.5/site-packages/trac/db/util.py", line  
50, in execute
     return self.cursor.execute(sql_escape_percent(sql), args)
   File "/opt/local/lib/python2.5/site-packages/trac/db/util.py", line  
50, in execute
     return self.cursor.execute(sql_escape_percent(sql), args)
ProgrammingError: current transaction is aborted, commands ignored  
until end of transaction block

---------------------------

Regards

Martin

-- 
Martin Krischik
krischik at users.sourceforge.net


From wasamy at umich.edu  Tue Dec 16 06:16:36 2008
From: wasamy at umich.edu (Waheed Samy)
Date: Tue, 16 Dec 2008 09:16:36 -0500
Subject: port command not working
Message-ID: <604C0F46-5543-4B59-96EB-4E95D71F9F94@umich.edu>

The port command is not working.  Should I uninstall MacPorts and then  
reinstall?
Waheed

From asato at cae1.aero.org  Tue Dec 16 10:52:36 2008
From: asato at cae1.aero.org (Max Asato)
Date: Tue, 16 Dec 2008 10:52:36 -0800
Subject: Distfiles mirror behind proxy
In-Reply-To: <1D694E2E-EABB-4780-B5B2-604B00E1838C@geeklair.net>
References: <20081210004857.GB16414@cae1.aero.org>
	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>
	<20081210184321.GA25989@cae1.aero.org>
	<49400F4D.7090805@macports.org>
	<20081211174100.GA7446@cae1.aero.org>
	<49415B37.3080000@macports.org>
	<359241CF-00A1-42EB-98C9-58ADEA0A9568@macports.org>
	<20081215181506.GA28775@cae1.aero.org>
	<1D694E2E-EABB-4780-B5B2-604B00E1838C@geeklair.net>
Message-ID: <20081216185236.GB11249@cae1.aero.org>

On Mon, Dec 15, 2008 at 03:25:44PM -0500, Daniel J. Luke wrote:
> On Dec 15, 2008, at 1:15 PM, Max Asato wrote:
> >Are there any features in 1.7 that would
> >permit a read-only archive directory?
> 
> 
> Not that I'm aware of, but you could probably adapt one of the dusty  
> patches in http://trac.macports.org/ticket/8571 to do what you want.
> --
> Daniel J. Luke

That looks interesting but I don't have the time to learn Tcl right now
so I'll have to back-burner the shared binary repository idea.

I'm looking forward to the release of 1.7 as that should make an internal
MacPorts mirror a bit easier to implement.  Thanks again to all who
responded.

-Max

From jmr at macports.org  Tue Dec 16 11:46:08 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 17 Dec 2008 06:46:08 +1100
Subject: Distfiles mirror behind proxy
In-Reply-To: <20081216185236.GB11249@cae1.aero.org>
References: <20081210004857.GB16414@cae1.aero.org>	<B16B0D8F-C9D1-4756-91AE-28040AA66DFE@macports.org>	<20081210184321.GA25989@cae1.aero.org>	<49400F4D.7090805@macports.org>	<20081211174100.GA7446@cae1.aero.org>	<49415B37.3080000@macports.org>	<359241CF-00A1-42EB-98C9-58ADEA0A9568@macports.org>	<20081215181506.GA28775@cae1.aero.org>	<1D694E2E-EABB-4780-B5B2-604B00E1838C@geeklair.net>
	<20081216185236.GB11249@cae1.aero.org>
Message-ID: <49480580.10500@macports.org>

Max Asato wrote:
> I'm looking forward to the release of 1.7 as that should make an internal
> MacPorts mirror a bit easier to implement.

1.7.0 was released last Saturday. :-)

- Josh

From jmr at macports.org  Tue Dec 16 11:48:01 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 17 Dec 2008 06:48:01 +1100
Subject: port command not working
In-Reply-To: <604C0F46-5543-4B59-96EB-4E95D71F9F94@umich.edu>
References: <604C0F46-5543-4B59-96EB-4E95D71F9F94@umich.edu>
Message-ID: <494805F1.5060306@macports.org>

Waheed Samy wrote:
> The port command is not working.  Should I uninstall MacPorts and then
> reinstall?

"Not working" is rather vague. What are you doing, and what is the
result you get?

- Josh

From trog24 at comcast.net  Tue Dec 16 13:16:27 2008
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Tue, 16 Dec 2008 13:16:27 -0800
Subject: Error upgrading xrender on Panther
In-Reply-To: <49476574.2030602@macports.org>
References: <2FF4BFD4-ADD6-45E8-8B58-AA3DE1FD3AF9@centosprime.com>
	<DD1BF403-B8AF-4496-9FD3-580F7BCCBE05@centosprime.com>
	<478BC18B-1A97-42DB-8B34-3249E1783AE5@macports.org>
	<21009181.post@talk.nabble.com>
	<AD175C97-2977-484C-BA91-61A85C3198B1@macports.org>
	<AE549A05-0A3B-4623-BF20-79D9B3D0E986@comcast.net>
	<7C9E3CC3-25D1-404D-AB15-D94673617A50@comcast.net>
	<4946B934.2040700@macports.org>
	<C58AE586-286F-4F26-ADB6-761BFEF63738@comcast.net>
	<EC8A4216-ADC7-4270-A92C-D5C6B29CA39B@bellsouth.net>
	<E247A2D5-813E-423B-9A53-6F9B3F9DA0B1@comcast.net>
	<4946DA6C.4020502@macports.org>
	<B9DF4334-5D8B-4E8C-9F06-11AD5977A082@macports.org>
	<494733F8.5040500@macports.org>
	<B866DFBF-76F9-4E0B-B0B0-3635B9E3D2DF@comcast.net>
	<49476574.2030602@macports.org>
Message-ID: <A5E4627F-BC47-448B-9782-834228E3E66A@comcast.net>

Hello,
	There were 12 contiguous iterations when I first reported the  
problem.  Given the large loop, there was a stopwatch period of time  
between iterations printed to the terminal window (seemed fairly even  
in duration during output to terminal window; but, I was not  
timing).  In the sample I pared it down to three.  I tried sending a  
log file with the -d in the command that ended up over 324 kbytes in  
size (exceeding the 150 kbyte limit) containing 14 iterations before  
I hit the "control C" and that file choked at access to the list.   
The iterations may have been testing dependencies each time; but, the  
file was getting quite large and the run time taking quite long.
	Yes, I agree with you on the possibility of not being unbounded;  
but, the lack of evidence is not running long enough to find out.   
Given the corrections to the process via the "sudo port sync"  
command, it is unlikely that I can repeat the problem for another  
run.  We can file this as something to watch for in the future.
Frank

On Dec 16, 2008, at 12:23 AM, Joshua Root wrote:

> Frank J. R. Hanstick wrote:
>> Hello,
>>     It is quite possible that the only way into the infinite loop  
>> is via
>> a port failure under certain circumstances.  Problems usually  
>> arise when
>> anomalies occur and not when things run as expected because not all
>> anomalies can be planned for.  If not, sorry  to disappoint you.
>
> Fair enough, but I would have expected to see a large number of
> iterations given the command you used, and we have no evidence that  
> the
> number of iterations would have been unbounded and not just large.
>
> - Josh


From jmr at macports.org  Tue Dec 16 14:12:51 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 17 Dec 2008 09:12:51 +1100
Subject: port command not working
In-Reply-To: <0539DC3A-4A6A-48CE-9D38-AD3AACAFAC27@umich.edu>
References: <604C0F46-5543-4B59-96EB-4E95D71F9F94@umich.edu>
	<494805F1.5060306@macports.org>
	<0539DC3A-4A6A-48CE-9D38-AD3AACAFAC27@umich.edu>
Message-ID: <494827E3.4020905@macports.org>

Waheed Samy wrote:
> I apologize for vagueness.
> I don't know what caused the path (opt/local/bin) to disappear.  I
> created a .profile in my home directory with the necessary path info,
> and now things are alright.
> What I mean was that when I gave the "port" command I got a no such file
> response.

That was a known bug in the MacPorts 1.6.0 installer. It should be fixed
in the 1.7.0 pkg though.

You may still find that the existence of other shell config files like
.bash_profile will stop the shell from reading the .profile created by
the installer, but since creating a .profile fixed the problem for you,
that doesn't seem to have been the issue.

- Josh

From jjstickel at vcn.com  Wed Dec 17 06:53:59 2008
From: jjstickel at vcn.com (Jonathan Stickel)
Date: Wed, 17 Dec 2008 07:53:59 -0700
Subject: Tiger and X11 and kdelibs
Message-ID: <49491287.9010905@vcn.com>

Until a most recent upgrade of macports ports (after release of 1.7), I 
had no trouble with X11.  However, I am now caught with this bug:

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

One recommended workaround is to remove all macports xorg ports and 
reinstall ports that have links to xorg libs, now using OS X X11 libs. 
This is what I am trying to do.  Right now I am stuck at trying to 
reinstall kde3.  kdelibs3 fails with:

checking for libXext... no
configure: error: We need a working libXext to proceed. Since configure
can't find it itself, we stop here assuming that make wouldn't find
them either.
kdelibs3-3.5.8-3 configure failed!

However, I do have libXext:

$ ls /usr/X11R6/lib/libXext*
/usr/X11R6/lib/libXext.6.4.dylib /usr/X11R6/lib/libXext.6.dylib 
/usr/X11R6/lib/libXext.a         /usr/X11R6/lib/libXext.dylib

How can I resolve this?

Jonathan

From David.Epstein at warwick.ac.uk  Wed Dec 17 07:04:01 2008
From: David.Epstein at warwick.ac.uk (David Epstein)
Date: Wed, 17 Dec 2008 07:04:01 -0800 (PST)
Subject: R GUI
Message-ID: <21054535.post@talk.nabble.com>


Does Macports have a port for the GUI for R, the statistical computing
program? Is it in fact possible to have a Macport supplying a MacOsX GUI
(not necessarily R) that is invoked by double-clicking on an icon?

My inability to use the port search facility efficiently became evident on
this issue, since my search for the R-gui failed miserably. "port search R"
brings in every port with an r in its name. "man port" advertises that one
can use regular expressions in the search, but fails to point to a
particular set of regular expressions, ignoring the fact that there are many
"standard" collections of basic regular expressions, each likely to have a
different way of indicating word boundaries. I tried
port search "\<R\>" and also port search "\bR\b",
and was told there are no matches, even through "port info R works". Nor
could I figure out how to make the matching case-sensitive.

So, if anyone can give me a hint on port search regular expressions, that
would be helpful.
Thanks
David
-- 
View this message in context: http://www.nabble.com/R-GUI-tp21054535p21054535.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From jhamner at gmail.com  Wed Dec 17 07:54:17 2008
From: jhamner at gmail.com (Jesse Hamner)
Date: Wed, 17 Dec 2008 10:54:17 -0500
Subject: R GUI
In-Reply-To: <21054535.post@talk.nabble.com>
References: <21054535.post@talk.nabble.com>
Message-ID: <4948DA59.8DF9.006D.0@gmail.com>

Hi David,

port list | grep R

(searching only for capital Rs in the list)

reveals that R-2.8 is housed under math/R, and even more narrow, 

port list | grep "R "

(note the trailing space) currently only pulls two entries, one of which is our CRAN buddy.

Some packages, like GRASS GIS, actually have the option as part of the config file to build for Mac OS X. R is one of those packages as well. There are build options --with-aqua and --enable-R-framework, but both of these options are "yes" by default. I suppose that then, perhaps the question would be "how does one start the application in Aqua GUI mode?" rather than "how does one build the GUI?"

I just download R from CRAN as a Mac OS X package, so I haven't built it for OSX myself. Sorry about that.

Jesse

-- 



>>> On 12/17/2008 at 10:04 AM, in message <21054535.post at talk.nabble.com>, David
Epstein<David.Epstein at warwick.ac.uk> wrote:

> Does Macports have a port for the GUI for R, the statistical computing
> program? Is it in fact possible to have a Macport supplying a MacOsX GUI
> (not necessarily R) that is invoked by double-clicking on an icon?
> 
> My inability to use the port search facility efficiently became evident on
> this issue, since my search for the R-gui failed miserably. "port search R"
> brings in every port with an r in its name. "man port" advertises that one
> can use regular expressions in the search, but fails to point to a
> particular set of regular expressions, ignoring the fact that there are many
> "standard" collections of basic regular expressions, each likely to have a
> different way of indicating word boundaries. I tried
> port search "\<R\>" and also port search "\bR\b",
> and was told there are no matches, even through "port info R works". Nor
> could I figure out how to make the matching case-sensitive.
> 
> So, if anyone can give me a hint on port search regular expressions, that
> would be helpful.
> Thanks
> David

From face at CentosPrime.COM  Wed Dec 17 07:55:23 2008
From: face at CentosPrime.COM (Chris Janton)
Date: Wed, 17 Dec 2008 08:55:23 -0700
Subject: R GUI
In-Reply-To: <21054535.post@talk.nabble.com>
References: <21054535.post@talk.nabble.com>
Message-ID: <9D4B674F-3F30-480F-AC13-665BE95A8407@centosprime.com>

On 2008-12-17 , at 08:04 , David Epstein wrote:

> and was told there are no matches, even through "port info R works".  
> Nor
> could I figure out how to make the matching case-sensitive.
>
> So, if anyone can give me a hint on port search regular expressions,  
> that
> would be helpful.


port list R*

works fine for me.

port cat R shows that the ported version of R specifically disables  
the Aqua GUI (--without-aqua) and looks like it basically builds an  
Xwindows version of R.

If you don't mind my asking, what's wrong with using the R GUI app  
that is provided on the CRAN?

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



From andrei at tchijov.com  Wed Dec 17 08:51:07 2008
From: andrei at tchijov.com (Andrei Tchijov)
Date: Wed, 17 Dec 2008 11:51:07 -0500
Subject: R GUI
In-Reply-To: <21054535.post@talk.nabble.com>
References: <21054535.post@talk.nabble.com>
Message-ID: <4CED61BB-D059-4974-9136-A82A4AF6FFF4@tchijov.com>

Why bother with Mac port when R ppl have native mac gui?

On Dec 17, 2008, at 10:04 , David Epstein wrote:

>
> Does Macports have a port for the GUI for R, the statistical computing
> program? Is it in fact possible to have a Macport supplying a MacOsX  
> GUI
> (not necessarily R) that is invoked by double-clicking on an icon?
>
> My inability to use the port search facility efficiently became  
> evident on
> this issue, since my search for the R-gui failed miserably. "port  
> search R"
> brings in every port with an r in its name. "man port" advertises  
> that one
> can use regular expressions in the search, but fails to point to a
> particular set of regular expressions, ignoring the fact that there  
> are many
> "standard" collections of basic regular expressions, each likely to  
> have a
> different way of indicating word boundaries. I tried
> port search "\<R\>" and also port search "\bR\b",
> and was told there are no matches, even through "port info R works".  
> Nor
> could I figure out how to make the matching case-sensitive.
>
> So, if anyone can give me a hint on port search regular expressions,  
> that
> would be helpful.
> Thanks
> David
> -- 
> View this message in context: http://www.nabble.com/R-GUI-tp21054535p21054535.html
> Sent from the MacPorts - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From ndiscreet at gmail.com  Wed Dec 17 09:15:04 2008
From: ndiscreet at gmail.com (Altoine Barker)
Date: Wed, 17 Dec 2008 11:15:04 -0600
Subject: R GUI
In-Reply-To: <21054535.post@talk.nabble.com>
References: <21054535.post@talk.nabble.com>
Message-ID: <49493398.7040603@GmAiL.cOm>

-----BEGIN PGP MESSAGE-----
Charset: ISO-8859-1
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

hQIOA2Xwf9idlRnZEAf+LwdG2fSlKQ8V2jUbJ4u60LC1c8SA6FATu8Gjq7QGodXh
rc966CSaD/WDJuQ0P0YXoP3YMDWl+EJZEDRRixs9m9oaGOVs/HfQeUOlE3IlEgVL
DfQYc39gXyupDJGziwKVH60fJjuo4SCfu5Rd+DTZETWEHCzTJKEIVuQqT8irdtVh
m1GY20DVYRGM8ALpWz9bh7L1ZebNlNx8HwfELe1/cCyPVhiWqA6vb9G+Gxk6rOdw
hZX0UF3rLhrG8hWldcfWqvgTAE9uAsmF8V4xhclG9ZeOfMHp+RZuriJHQJAmUHAS
8ihxvSIOkEyOufHxJmDYt/zs0L+s8dJ1Vv2+Mm/JXAf/RwySsCsJvy1y4WqxsSd8
uihcpRcLMhKMhwqp1ZgwEzYiP3uegM6J05j75N5v4yskLs6bHbS8/ROLK2nfqROH
P1YQbNbKTcjyW3xa1s+PysPf4ET8QkrlTQp29bIAsBeYdngtL6Tc5DGTBBVvVm/h
Lw366vtpnXYSYcJc+rMYjFfnNvj2cETSo/aiBdY9HXlSKgL0q8WuH1LTRYtmns/p
VIY/xycD32HDzYrfkjb7azJSXqWFqJ5rQ7kFV7QlklGwURDacbpoxfEjWEe6FWEj
O0ekcOJTcJKAtTm8UuaFvbDLQaX57OcgdyOaJiBkKIseiokcQ9WvwGRNHn9Zh1VO
ytLpAfDJ/Qp1kAtfzNUBaWBjcqD7WsxCIRe8YgrMIiQKEhAqDHJT2OI2DaVz+V77
Zt/WRiV0eOHusisx3h61umyVr1uucS7Yd+npKnnV/alM9yZsJNylB+0AazeWAa9n
A6Ty17bUQOAGeMIEoLEVkNof2Kgbk89pRvDYhbB6UZe8wz5YpBnmYCXC7bK1T5vh
2CmRua7zqGt/LjtOemGU5nehw4ToB6QQswtV3/p+BOjEAggfKgRYzbjI7TAjinki
q7bxvupiO5j8VpopavMbUl6B7rSQoqnhNEV99V4YLxCrVp9hwyCrspwT8mvfnPSe
q+LnsQ1zscWRa3V6CnMPb2dSQf2dH1YscskVijHSpFrTkWBeMoePcykYGiEISgyO
LdRR/tGUwv0w9lXN/ntarYvMr/6IHt283WxfObPik2hhQcag9ec3qah2zNWLFuTD
lrvMf7mGMLQjpf0w3B6voZ1BUe8bok8GhdwXTC00M/Ye7f2dpajB0hYy5sbIIaka
h3gS5xVEAijKz6rtR56JMsmfjxKxGh5aC9bcqDEOydmNQNeZzjSQ/B+9jTvq5vaz
inde0gqxMk+JiODbfaxJgspHhGBwc6HKPV3N6F8a345LFxir3V8Wl9n6QUfataTK
mRfN30ZlC0PfDiV8A9IrViv1U6xKUgaKez4x/PFYQZcwWwLA364RUzwDdvRDlXke
5uqWeEsIC4yUnNMERLMcqV13Et/alhFcR3acHXD3RLlUGQWRfa/+8iFevrQ/zapj
SSca30TyskJQaZs6f16w3O0oMZ+hCPt1ZfkW6wC3ufLXhutCqs3Kpn13ow6x1lsQ
6GTkOHzEGSFc7wcMDRN8fODqX/18kbxtGK5Youc0wbBvcl1IVadEIGjXUt4AVzL7
HBGKKtiOYl3yVIS1gk47sHfzGm8OcNRsQmk8rvw7oqb0Mwf2FVH5EwLi4IW2Wtoe
RxmY4PvKmJXWP9wfq2T8R/s3WH0VPO7j7VfPfihiYuw2IZ6ubBWANpRuR2D4s7Fw
LrJXRUmui3+ISRURrjLwjH7Z+UYPjLzC09FGraELGAIa3CE1XkG/xn/SwlvXJaet
QsjGjif8aT++LIVt2EXBy1AR+uxhVWJu8WGqI2oo7+46Q3uxMNBGNi49hG/fI/xn
nXRqww+LNSrSLPEfISi32y4b6mvelNvKWDLmeuzU+YFaAC2oam1Vmwr0gNKiXN0T
HQqtBOr9aVGNnjgTgX4hQsGbUKo=
=wgTA
-----END PGP MESSAGE-----

From ndiscreet at gmail.com  Wed Dec 17 09:22:02 2008
From: ndiscreet at gmail.com (Altoine Barker)
Date: Wed, 17 Dec 2008 11:22:02 -0600
Subject: R GUI
In-Reply-To: <21054535.post@talk.nabble.com>
References: <21054535.post@talk.nabble.com>
Message-ID: <4949353A.20507@GmAiL.cOm>

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

Here is the best way I came up with coming to one singe result:

port search R* | grep math | grep R

HTH

- -Altoine

David Epstein wrote:
> Does Macports have a port for the GUI for R, the statistical computing
> program? Is it in fact possible to have a Macport supplying a MacOsX GUI
> (not necessarily R) that is invoked by double-clicking on an icon?
> 
> My inability to use the port search facility efficiently became evident on
> this issue, since my search for the R-gui failed miserably. "port search R"
> brings in every port with an r in its name. "man port" advertises that one
> can use regular expressions in the search, but fails to point to a
> particular set of regular expressions, ignoring the fact that there are many
> "standard" collections of basic regular expressions, each likely to have a
> different way of indicating word boundaries. I tried
> port search "\<R\>" and also port search "\bR\b",
> and was told there are no matches, even through "port info R works". Nor
> could I figure out how to make the matching case-sensitive.
> 
> So, if anyone can give me a hint on port search regular expressions, that
> would be helpful.
> Thanks
> David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAklJNToACgkQQlfc9y4ObkMwkwCghicFgvh5FUd+cNFE3zI1Pos4
B+kAnRFoRRJtwAXBy3KrjfguM3u1O4+M
=kE73
-----END PGP SIGNATURE-----

From David.Epstein at warwick.ac.uk  Wed Dec 17 09:46:45 2008
From: David.Epstein at warwick.ac.uk (David Epstein)
Date: Wed, 17 Dec 2008 09:46:45 -0800 (PST)
Subject: R GUI
In-Reply-To: <4CED61BB-D059-4974-9136-A82A4AF6FFF4@tchijov.com>
References: <21054535.post@talk.nabble.com>
	<4CED61BB-D059-4974-9136-A82A4AF6FFF4@tchijov.com>
Message-ID: <21057934.post@talk.nabble.com>



Andrei Tchijov wrote:
> 
> Why bother with Mac port when R ppl have native mac gui?
> 

I really wanted to find out how to search using port. Jesse Hamner showed
how to remove the regular expression part from the clutches of port, so that
the output from port list can be dealt with using standard Unix facilities.
In retrospect, this is the obvious approach.

port list R* can't do what we want, can it? The shell tries to expand R* to
match a file in the current directory, and otherwise exits with "No match".
If one shields R* from the shell with quote marks, for example, then one
gets a list of all ports starting with R or r, and there are too many of
them for comfort.

David

-- 
View this message in context: http://www.nabble.com/R-GUI-tp21054535p21057934.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From frstan at bellsouth.net  Wed Dec 17 09:59:58 2008
From: frstan at bellsouth.net (William Davis)
Date: Wed, 17 Dec 2008 12:59:58 -0500
Subject: R GUI
In-Reply-To: <21054535.post@talk.nabble.com>
References: <21054535.post@talk.nabble.com>
Message-ID: <6E8D1A5D-1378-4686-BF35-CD99B52F76EC@bellsouth.net>


On Dec 17, 2008, at 10:04 AM, David Epstein wrote:

>
> Does Macports have a port for the GUI for R, the statistical computing
> program? Is it in fact possible to have a Macport supplying a MacOsX  
> GUI
> (not necessarily R) that is invoked by double-clicking on an icon?
/snip/

Others have responded to you.  I'll add that
port info R
shows kjell.konis at epfl.ch is the maintainer of the Mac Port.  You  
might ask him why he has configured the port using --without-aqua, and  
if a variant --with-aqua could be provided.  Or you could write a Traq  
ticket requesting the same.


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

Mundus vult decepi, ego non


From face at CentosPrime.COM  Wed Dec 17 11:05:00 2008
From: face at CentosPrime.COM (Chris Janton)
Date: Wed, 17 Dec 2008 12:05:00 -0700
Subject: R GUI
In-Reply-To: <21057934.post@talk.nabble.com>
References: <21054535.post@talk.nabble.com>
	<4CED61BB-D059-4974-9136-A82A4AF6FFF4@tchijov.com>
	<21057934.post@talk.nabble.com>
Message-ID: <1708FBC5-4B16-4065-89F0-0D9ECF79821B@centosprime.com>

On 2008-12-17 , at 10:46 , David Epstein wrote:

> port list R* can't do what we want, can it? The shell tries to  
> expand R* to
> match a file in the current directory, and otherwise exits with "No  
> match".
> If one shields R* from the shell with quote marks, for example, then  
> one
> gets a list of all ports starting with R or r, and there are too  
> many of
> them for comfort.


face at mac:~:125 $ port list R*
R                              @2.8.0          math/R

That's running from trunk - so MacPorts version is

face at mac:~:126 $ port
MacPorts 1.8.0
Entering interactive mode... ("help" for help, "quit" to quit)
[Users/face] > ^D
Goodbye

On my *old* system

face at x:face:123 $ port
MacPorts 1.600
Entering interactive mode... ("help" for help, "quit" to quit)
[Users/face] > ^D
Goodbye
face at x:face:124 $ port list R*
face at x:face:125 $

Looks like you need a newer version of port ;-)

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



From gkshenaut at ucdavis.edu  Wed Dec 17 11:36:27 2008
From: gkshenaut at ucdavis.edu (Greg Shenaut)
Date: Wed, 17 Dec 2008 11:36:27 -0800
Subject: R GUI
In-Reply-To: <1708FBC5-4B16-4065-89F0-0D9ECF79821B@centosprime.com>
References: <21054535.post@talk.nabble.com>
	<4CED61BB-D059-4974-9136-A82A4AF6FFF4@tchijov.com>
	<21057934.post@talk.nabble.com>
	<1708FBC5-4B16-4065-89F0-0D9ECF79821B@centosprime.com>
Message-ID: <FB53C8AF-0A04-4A4D-BD9D-D5A2908540E7@ucdavis.edu>

I generally use the -i and -w flags with grep, as in "port list | grep  
-iw r".

These flags have always been so useful to me that IMHO their  
equivalent should be the default in "port search", or perhaps there  
could be an alternate command such as "port lookup".

Greg Shenaut

From perry at macports.org  Wed Dec 17 11:49:03 2008
From: perry at macports.org (Perry Lee)
Date: Wed, 17 Dec 2008 11:49:03 -0800
Subject: *_select's
In-Reply-To: <20081201224742.GH651@ninagal.withay.com>
References: <5993BFC8-35E4-4222-9E98-DB8362CC2DBB@voidfx.net>
	<2FA70823-8979-4E41-B1C6-1F382273846B@macports.org>
	<20081130061937.GU525@ninagal.withay.com>
	<4933B78C.5070808@macports.org>
	<20081201224742.GH651@ninagal.withay.com>
Message-ID: <20081217194903.GA228@phoenix.lan>

On Mon, Dec 01, 2008 at 03:47:42PM -0700, Bryan Blackburn wrote:
> On Mon, Dec 01, 2008 at 11:08:12AM +0100, Rainer M?ller said:
> > Best would be to add select stuff to base like 'port select'. All other
> > functionality of MacPorts is called from the port tool and we should
> > stick to this.
> > *_select tools were just a quick workaround to make it usable until this
> > is available in base. Also, using a base tool it can be more automated,
> > for example de-select a version if its port is deactivated/uninstalled.
> 
> Agreed, and so it doesn't get lost:
> 
> <http://trac.macports.org/ticket/17477>

I've attached a patch to that ticket
(http://trac.macports.org/attachment/ticket/17477/port.tcl.diff) that
integrates some of the *_select tools' functionality into port. I didn't want
to commit it to trunk until more people have taken a look at it (e.g., the
syntax: port select <module> <action> <options>).

From jmr at macports.org  Wed Dec 17 13:13:46 2008
From: jmr at macports.org (Joshua Root)
Date: Thu, 18 Dec 2008 08:13:46 +1100
Subject: R GUI
In-Reply-To: <21054535.post@talk.nabble.com>
References: <21054535.post@talk.nabble.com>
Message-ID: <49496B8A.80304@macports.org>

David Epstein wrote:
> My inability to use the port search facility efficiently became evident on
> this issue, since my search for the R-gui failed miserably. "port search R"
> brings in every port with an r in its name. "man port" advertises that one
> can use regular expressions in the search, but fails to point to a
> particular set of regular expressions, ignoring the fact that there are many
> "standard" collections of basic regular expressions, each likely to have a
> different way of indicating word boundaries. I tried
> port search "\<R\>" and also port search "\bR\b",
> and was told there are no matches, even through "port info R works". Nor
> could I figure out how to make the matching case-sensitive.

The man page is actually wrong. The search expression is evaluated as a
glob, not a regex. `port search " R "` seems to do what you want.

It's hard not to suspect that its creators were *trying* to make life
hard when they chose a single-letter name...

- Josh

From David.Epstein at warwick.ac.uk  Wed Dec 17 14:01:47 2008
From: David.Epstein at warwick.ac.uk (David Epstein)
Date: Wed, 17 Dec 2008 14:01:47 -0800 (PST)
Subject: R GUI
In-Reply-To: <1708FBC5-4B16-4065-89F0-0D9ECF79821B@centosprime.com>
References: <21054535.post@talk.nabble.com>
	<4CED61BB-D059-4974-9136-A82A4AF6FFF4@tchijov.com>
	<21057934.post@talk.nabble.com>
	<1708FBC5-4B16-4065-89F0-0D9ECF79821B@centosprime.com>
Message-ID: <21062507.post@talk.nabble.com>



Chris Janton wrote:
> 
> On 2008-12-17 , at 10:46 , David Epstein wrote:
> 
>> port list R* can't do what we want, can it? The shell tries to  
>> expand R* to
>> match a file in the current directory, and otherwise exits with "No  
>> match".
>> If one shields R* from the shell with quote marks, for example, then  
>> one
>> gets a list of all ports starting with R or r, and there are too  
>> many of
>> them for comfort.
> 
> 
> face at mac:~:125 $ port list R*
> R                              @2.8.0          math/R
> 
> That's running from trunk - so MacPorts version is
> 
> face at mac:~:126 $ port
> MacPorts 1.8.0
> Entering interactive mode... ("help" for help, "quit" to quit)
> [Users/face] > ^D
> Goodbye
> 
> On my *old* system
> 
> face at x:face:123 $ port
> MacPorts 1.600
> Entering interactive mode... ("help" for help, "quit" to quit)
> [Users/face] > ^D
> Goodbye
> face at x:face:124 $ port list R*
> face at x:face:125 $
> 
> Looks like you need a newer version of port ;-)
> 

I have version 1.700 of MacPorts, under MacOsX 10.4.11, and when I do sudo
port selfupdate, I'm told I am already up-to-date.

This discussion is assuming a complexity that I didn't at first suspect. I
found to my surprise that bash and tcsh interpret port list R* differently.
bash seems to pass the R* argument unaltered to port. But tcsh attempts an
immediate expansion of R* before handing over to port.

I am still unable to track down the other difference, in that on my machine,
the argument following "port list" seems to be dealt with in a
case-insensitive manner, and on Chris's machine seems to be dealt with in a
case-sensitive manner. Using interactive mode for port simplifies by
removing potentially complex interactions with the shell. However, for me,
the case-insensitivity remains. Perhaps this is due to some different
configuration setting. Or maybe it's a difference between Leopard and Tiger.
Since, thanks to this thread, I now have several ways of dealing with these
searches efficiently, I don't think it's worthwhile investigating the matter
further. However, if someone knows why there's this difference, without
having to spend time on it, it would be interesting to know the answer.
David
-- 
View this message in context: http://www.nabble.com/R-GUI-tp21054535p21062507.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From mark at dxradio.demon.co.uk  Wed Dec 17 15:25:50 2008
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Wed, 17 Dec 2008 23:25:50 +0000
Subject: R GUI
In-Reply-To: <21062507.post@talk.nabble.com>
References: <21054535.post@talk.nabble.com>
	<4CED61BB-D059-4974-9136-A82A4AF6FFF4@tchijov.com>
	<21057934.post@talk.nabble.com>
	<1708FBC5-4B16-4065-89F0-0D9ECF79821B@centosprime.com>
	<21062507.post@talk.nabble.com>
Message-ID: <29143908-9745-4A6B-9C90-75575DAC11A5@dxradio.demon.co.uk>


On 17 Dec 2008, at 22:01, David Epstein wrote:

>
>
> Chris Janton wrote:
>>
>> On 2008-12-17 , at 10:46 , David Epstein wrote:
>>
>>> port list R* can't do what we want, can it? The shell tries to
>>> expand R* to
>>> match a file in the current directory, and otherwise exits with "No
>>> match".
>>> If one shields R* from the shell with quote marks, for example, then
>>> one
>>> gets a list of all ports starting with R or r, and there are too
>>> many of
>>> them for comfort.
>>
>>
>> face at mac:~:125 $ port list R*
>> R                              @2.8.0          math/R
>>
>> That's running from trunk - so MacPorts version is
>>
>> face at mac:~:126 $ port
>> MacPorts 1.8.0
>> Entering interactive mode... ("help" for help, "quit" to quit)
>> [Users/face] > ^D
>> Goodbye
>>
>> On my *old* system
>>
>> face at x:face:123 $ port
>> MacPorts 1.600
>> Entering interactive mode... ("help" for help, "quit" to quit)
>> [Users/face] > ^D
>> Goodbye
>> face at x:face:124 $ port list R*
>> face at x:face:125 $
>>
>> Looks like you need a newer version of port ;-)
>>
>
> I have version 1.700 of MacPorts, under MacOsX 10.4.11, and when I  
> do sudo
> port selfupdate, I'm told I am already up-to-date.
>
> This discussion is assuming a complexity that I didn't at first  
> suspect. I
> found to my surprise that bash and tcsh interpret port list R*  
> differently.
> bash seems to pass the R* argument unaltered to port. But tcsh  
> attempts an
> immediate expansion of R* before handing over to port.
>
> I am still unable to track down the other difference, in that on my  
> machine,
> the argument following "port list" seems to be dealt with in a
> case-insensitive manner, and on Chris's machine seems to be dealt  
> with in a
> case-sensitive manner. Using interactive mode for port simplifies by
> removing potentially complex interactions with the shell. However,  
> for me,
> the case-insensitivity remains. Perhaps this is due to some different
> configuration setting. Or maybe it's a difference between Leopard  
> and Tiger.
> Since, thanks to this thread, I now have several ways of dealing  
> with these
> searches efficiently, I don't think it's worthwhile investigating  
> the matter
> further. However, if someone knows why there's this difference,  
> without
> having to spend time on it, it would be interesting to know the  
> answer.
> David


OK ... I'll play dumb ... I'm running Macports 1.7 on OSX 10.5.6 in  
Bash ... "port list" and "port info" both work as I'd expect (and are  
case insensitive)

iMac:~ $ sudo port list R
R                              @2.8.0          math/R

iMac:~ $ sudo port info R
R @2.8.0 (math, science)
Variants:    gcc42, gcc43

R is a language and environment for statistical computing and  
graphics. R provides a wide variety of statistical (linear and nonlinear
modelling, classical statistical tests, time-series analysis,  
classification, clustering, ...) and graphical techniques, and is highly
extensible.
Homepage:    http://www.r-project.org/

Library Dependencies: gettext, glib2, jpeg, libiconv, pango, readline,  
tcl, tk, tiff, xorg-libXmu, xorg-libXScrnSaver, gcc43
Platforms:            darwin
Maintainers:          kjell.konis at epfl.ch



what doesn't "work" in a similar fashion is
sudo port search R

5124 ports contain a case-insensitive [r|R]

But then you probably wouldn't be searching if you knew the name that  
well.

But these do "work"

iMac:~$ sudo port search ' R '
R @2.8.0 (math, science)
     R is GNU S - an interpreted language for statistical computing

iMac:~$ sudo port search " R "
R @2.8.0 (math, science)
     R is GNU S - an interpreted language for statistical computing


`Mark

From christopher.rob.jones at cern.ch  Wed Dec 17 16:08:45 2008
From: christopher.rob.jones at cern.ch (Chris Jones)
Date: Thu, 18 Dec 2008 00:08:45 +0000
Subject: KDE4 applications need X11 ?
In-Reply-To: <624DCE93-CD71-45ED-BAFE-2653C723707A@cern.ch>
References: <67DD9ACD-45F8-4ABD-9F8B-D41B0051AB28@cern.ch>
	<96A2F8CC-79A0-4D0F-9377-851025661450@macports.org>
	<624DCE93-CD71-45ED-BAFE-2653C723707A@cern.ch>
Message-ID: <17069294-3B9C-468D-A90B-839A11660116@cern.ch>


Hi,

I've filed a ticket for this.

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

Chris


From lovecraftian at mac.com  Thu Dec 18 00:55:46 2008
From: lovecraftian at mac.com (Scott)
Date: Thu, 18 Dec 2008 08:55:46 +0000 (UTC)
Subject: sudo port -f uninstall lame: DOES NOT UNINSTALL DEPENDENCIES
Message-ID: <loom.20081218T084946-155@post.gmane.org>

The `-f' option does not work properly -- it is supposed to kill
dependencies, too.

b8$ port -f uninstall lame
--->  Deactivating lame 3.98.2_0
Error: port uninstall failed: error deleting \
"/opt/local/share/man/man1/lame.1.gz": permission denied
b9$ sudo port -f uninstall lame
Password:
--->  Deactivating lame 3.98.2_0
--->  Uninstalling lame 3.98.2_0

[Then I checked the directory: all the ncurses and ncursesw files are
still there.  So I try again ...]

b11$ sudo port -f uninstall lame
Error: port uninstall failed: Registry error: lame not \
registered as installed.

[Damn.  So I do it manually ...]

b12$ sudo port uninstall ncurses
--->  Deactivating ncurses 5.7_0
--->  Uninstalling ncurses 5.7_0
b13$ sudo port uninstall ncursesw
--->  Deactivating ncursesw 5.7_0
--->  Uninstalling ncursesw 5.7_0
b14$

Is `-f' supposed to actually work?




From milosh at macports.org  Thu Dec 18 01:06:12 2008
From: milosh at macports.org (Emmanuel Hainry)
Date: Thu, 18 Dec 2008 10:06:12 +0100
Subject: sudo port -f uninstall lame: DOES NOT UNINSTALL DEPENDENCIES
In-Reply-To: <loom.20081218T084946-155@post.gmane.org>
References: <loom.20081218T084946-155@post.gmane.org>
Message-ID: <20081218090612.GA9268@weetamoe.loria.fr>

Citando Scott :
> The `-f' option does not work properly -- it is supposed to kill
> dependencies, too.

No, it is not.
 
> Is `-f' supposed to actually work?

Yes. It works. But it does not do what you expected.

According to the man page -f is for force mode. When uninstalling a port
that has dependents (not dependencies), port will stop if you don't use
the -f switch. If you force the uninstall, it will render the dependents
unworking, but it will uninstall however.

% port uninstall ncurses
--->  Unable to uninstall ncurses 5.6_0, the following ports depend on
it:
--->  	gettext
--->  	cmus
Error: port uninstall failed: Please uninstall the ports that depend on
ncurses first.
% port -f uninstall ncurses
--->  Unable to uninstall ncurses 5.6_0, the following ports depend on
it:
--->  	gettext
--->  	cmus
Warning: Uninstall forced.  Proceeding despite dependencies.
--->  Deactivating ncurses @5.6_0
--->  Uninstalling ncurses @5.6_0


And I no longer have ncurses. (and cmus does not work anymore as I
predicted).

Emmanuel

From lovecraftian at mac.com  Thu Dec 18 01:13:06 2008
From: lovecraftian at mac.com (Scott)
Date: Thu, 18 Dec 2008 09:13:06 +0000 (UTC)
Subject: sudo port -f uninstall lame: DOES NOT UNINSTALL DEPENDENCIES
References: <loom.20081218T084946-155@post.gmane.org>
	<20081218090612.GA9268@weetamoe.loria.fr>
Message-ID: <loom.20081218T090920-11@post.gmane.org>

Emmanuel Hainry <milosh <at> macports.org> writes:

> According to the man page -f is for force mode. When uninstalling a port
> that has dependents (not dependencies), port will stop if you don't use
> the -f switch. If you force the uninstall, it will render the dependents
> unworking, but it will uninstall however.

Thank you very much.  You explained it perfectly, and I understand the
logic behind protecting dependents.  Also, now that I think about it, since
a dependency-port may have multiple dependents, killing a given port's
dependencies may do unforeseen harm since that dependency may have
OTHER dependents.




From ryandesign at macports.org  Fri Dec 19 04:21:38 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 19 Dec 2008 06:21:38 -0600
Subject: sudo port -f uninstall lame: DOES NOT UNINSTALL DEPENDENCIES
In-Reply-To: <loom.20081218T090920-11@post.gmane.org>
References: <loom.20081218T084946-155@post.gmane.org>
	<20081218090612.GA9268@weetamoe.loria.fr>
	<loom.20081218T090920-11@post.gmane.org>
Message-ID: <2EBCED20-F27C-4507-AB67-0C6963490215@macports.org>


On Dec 18, 2008, at 03:13, Scott wrote:

> Emmanuel Hainry writes:
>
>> According to the man page -f is for force mode. When uninstalling  
>> a port
>> that has dependents (not dependencies), port will stop if you  
>> don't use
>> the -f switch. If you force the uninstall, it will render the  
>> dependents
>> unworking, but it will uninstall however.
>
> Thank you very much.  You explained it perfectly, and I understand the
> logic behind protecting dependents.  Also, now that I think about  
> it, since
> a dependency-port may have multiple dependents, killing a given port's
> dependencies may do unforeseen harm since that dependency may have
> OTHER dependents.

You may be interested in this related discussion:

http://lists.macosforge.org/pipermail/macports-dev/2008-December/ 
006576.html



From tim.visher at gmail.com  Fri Dec 19 06:50:58 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Fri, 19 Dec 2008 09:50:58 -0500
Subject: Issues Upgrading Outdated Under 1.700
In-Reply-To: <49458454.9040302@macports.org>
References: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>
	<20081214211438.GC489@ninagal.withay.com>
	<c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>
	<49458454.9040302@macports.org>
Message-ID: <c115fd3c0812190650s5d4f90b1v26d511d0a3f30503@mail.gmail.com>

On Sun, Dec 14, 2008 at 5:10 PM, Rainer M?ller <raimue at macports.org> wrote:

> Then check for the lock file:
>  /opt/local/var/macports/receipts/dep_map.bz2.lock
> If it is there, remove it.

Well, you nailed it.  There was a persistent lock file.  I did remove
it.  And I was able to continue the install successfully for a very
brief amount of time.  Unfortunately, now I'm failing with the
following message (and _no_ lock file):

    Waiting for lock on
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/.macports.boost.state

I've done `find /opt -name '*.lock' -print` a bunch of times and
nothing shows up, so I don't _think_ it's a lock file issue this time,
but I've got no idea.

Thanks for your help so far.

-- 

In Christ,

Timmy V.

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

From brad at pixilla.com  Fri Dec 19 07:16:23 2008
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Fri, 19 Dec 2008 07:16:23 -0800
Subject: configuring port
Message-ID: <620ABA27-1233-4A34-BA68-511BDC4E3689@pixilla.com>

There are a couple ports (dovecot and bind9) that I want to install  
that do not have variants that match my needs.

My needs would be something like:

port install dovecot +mysql
port install bind9 +dlz-mysql

Is there some reading that someone could point me to that could help  
me with downloading and reconfiguring a port from macports?

I'm looking to take advantage of the macports patches and handling of  
dependies.

I'm somewhat familiar with freebsd ports and gentoo emerge.

Is there something equiveleant to freebsd port where I could run ./ 
configure --with-some_option?


TIA,
Brad

From dluke at geeklair.net  Fri Dec 19 07:24:38 2008
From: dluke at geeklair.net (Daniel J. Luke)
Date: Fri, 19 Dec 2008 10:24:38 -0500
Subject: configuring port
In-Reply-To: <620ABA27-1233-4A34-BA68-511BDC4E3689@pixilla.com>
References: <620ABA27-1233-4A34-BA68-511BDC4E3689@pixilla.com>
Message-ID: <BA3B3C12-8980-42E1-959B-A15A6E3B8BC2@geeklair.net>

On Dec 19, 2008, at 10:16 AM, Bradley Giesbrecht wrote:
> Is there some reading that someone could point me to that could help  
> me with downloading and reconfiguring a port from macports?

The guide should help you out, especially:

http://guide.macports.org/#development

> I'm looking to take advantage of the macports patches and handling  
> of dependies.


If you think your variants would be useful to more than just you, I'm  
sure we'd be glad to add them. Please file tickets with your proposed  
patches if so.

--
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/20081219/ab6cd582/attachment.bin>

From frstan at bellsouth.net  Fri Dec 19 07:28:19 2008
From: frstan at bellsouth.net (William Davis)
Date: Fri, 19 Dec 2008 10:28:19 -0500
Subject: Issues Upgrading Outdated Under 1.700
In-Reply-To: <c115fd3c0812190650s5d4f90b1v26d511d0a3f30503@mail.gmail.com>
References: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>
	<20081214211438.GC489@ninagal.withay.com>
	<c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>
	<49458454.9040302@macports.org>
	<c115fd3c0812190650s5d4f90b1v26d511d0a3f30503@mail.gmail.com>
Message-ID: <D76E262D-49FE-49B0-AEAE-B59F3ECE2652@bellsouth.net>

try:
sudo port -d clean boost
WD
On Dec 19, 2008, at 9:50 AM, Tim Visher wrote:

> On Sun, Dec 14, 2008 at 5:10 PM, Rainer M?ller <raimue at macports.org>  
> wrote:
>
>> Then check for the lock file:
>> /opt/local/var/macports/receipts/dep_map.bz2.lock
>> If it is there, remove it.
>
> Well, you nailed it.  There was a persistent lock file.  I did remove
> it.  And I was able to continue the install successfully for a very
> brief amount of time.  Unfortunately, now I'm failing with the
> following message (and _no_ lock file):
>
>    Waiting for lock on
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_devel_boost/work/.macports.boost.state
>
> I've done `find /opt -name '*.lock' -print` a bunch of times and
> nothing shows up, so I don't _think_ it's a lock file issue this time,
> but I've got no idea.
>
> Thanks for your help so far.
>
> -- 
>
> In Christ,
>
> Timmy V.
>
> http://burningones.com/
> http://five.sentenc.es/ - Spend less time on e-mail
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users



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

Mundus vult decepi, ego non


From tim.visher at gmail.com  Fri Dec 19 07:37:47 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Fri, 19 Dec 2008 10:37:47 -0500
Subject: Issues Upgrading Outdated Under 1.700
In-Reply-To: <D76E262D-49FE-49B0-AEAE-B59F3ECE2652@bellsouth.net>
References: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>
	<20081214211438.GC489@ninagal.withay.com>
	<c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>
	<49458454.9040302@macports.org>
	<c115fd3c0812190650s5d4f90b1v26d511d0a3f30503@mail.gmail.com>
	<D76E262D-49FE-49B0-AEAE-B59F3ECE2652@bellsouth.net>
Message-ID: <c115fd3c0812190737g36f7e56cwaabd8b1c695e3587@mail.gmail.com>

On Fri, Dec 19, 2008 at 10:28 AM, William Davis <frstan at bellsouth.net> wrote:
> try:
> sudo port -d clean boost
> WD
> On Dec 19, 2008, at 9:50 AM, Tim Visher wrote:

Output:

	DEBUG: Found port in
file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/boost
	DEBUG: Changing to port directory:
/opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/boost
	DEBUG: setting option os.universal_supported to yes
	DEBUG: org.macports.load registered provides 'load', a pre-existing
procedure. Target override will not be provided
	DEBUG: org.macports.distfiles registered provides 'distfiles', a
pre-existing procedure. Target override will not be provided
	DEBUG: adding the default universal variant
	DEBUG: Requested variant i386 is not provided by port boost.
	DEBUG: Requested variant macosx is not provided by port boost.
	DEBUG: Executing variant darwin_9 provides darwin_9
	DEBUG: Executing variant darwin provides darwin
	DEBUG: Executing org.macports.main (boost)
	Waiting for lock on
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/.macports.boost.state

-- 

In Christ,

Timmy V.

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

From raimue at macports.org  Fri Dec 19 09:12:20 2008
From: raimue at macports.org (=?UTF-8?B?UmFpbmVyIE3DvGxsZXI=?=)
Date: Fri, 19 Dec 2008 18:12:20 +0100
Subject: Issues Upgrading Outdated Under 1.700
In-Reply-To: <c115fd3c0812190650s5d4f90b1v26d511d0a3f30503@mail.gmail.com>
References: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>	
	<20081214211438.GC489@ninagal.withay.com>	
	<c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>	
	<49458454.9040302@macports.org>
	<c115fd3c0812190650s5d4f90b1v26d511d0a3f30503@mail.gmail.com>
Message-ID: <494BD5F4.2080801@macports.org>

Tim Visher wrote:
> [...]
> Unfortunately, now I'm failing with the
> following message (and _no_ lock file):
> 
>     Waiting for lock on
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/.macports.boost.state
> 
> I've done `find /opt -name '*.lock' -print` a bunch of times and
> nothing shows up, so I don't _think_ it's a lock file issue this time,
> but I've got no idea.

In fact, this is a lock file, it is locking a specific port. The port
tool is thinking there is another port instance running to build boost
currently. Look for running tclsh processes.

Rainer

From jmr at macports.org  Fri Dec 19 09:23:15 2008
From: jmr at macports.org (Joshua Root)
Date: Sat, 20 Dec 2008 04:23:15 +1100
Subject: Issues Upgrading Outdated Under 1.700
In-Reply-To: <c115fd3c0812190737g36f7e56cwaabd8b1c695e3587@mail.gmail.com>
References: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>	<20081214211438.GC489@ninagal.withay.com>	<c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>	<49458454.9040302@macports.org>	<c115fd3c0812190650s5d4f90b1v26d511d0a3f30503@mail.gmail.com>	<D76E262D-49FE-49B0-AEAE-B59F3ECE2652@bellsouth.net>
	<c115fd3c0812190737g36f7e56cwaabd8b1c695e3587@mail.gmail.com>
Message-ID: <494BD883.70005@macports.org>

Tim Visher wrote:
> On Fri, Dec 19, 2008 at 10:28 AM, William Davis <frstan at bellsouth.net> wrote:
>> try:
>> sudo port -d clean boost
>> WD
>> On Dec 19, 2008, at 9:50 AM, Tim Visher wrote:
> 
> Output:
> 
> 	DEBUG: Found port in
> file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/boost
> 	DEBUG: Changing to port directory:
> /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/boost
> 	DEBUG: setting option os.universal_supported to yes
> 	DEBUG: org.macports.load registered provides 'load', a pre-existing
> procedure. Target override will not be provided
> 	DEBUG: org.macports.distfiles registered provides 'distfiles', a
> pre-existing procedure. Target override will not be provided
> 	DEBUG: adding the default universal variant
> 	DEBUG: Requested variant i386 is not provided by port boost.
> 	DEBUG: Requested variant macosx is not provided by port boost.
> 	DEBUG: Executing variant darwin_9 provides darwin_9
> 	DEBUG: Executing variant darwin provides darwin
> 	DEBUG: Executing org.macports.main (boost)
> 	Waiting for lock on
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_boost/work/.macports.boost.state

See if there's another instance of port running:

ps -A | grep tclsh

- Josh

From r.shekhar at gmail.com  Fri Dec 19 13:01:12 2008
From: r.shekhar at gmail.com (Raj Shekhar)
Date: Fri, 19 Dec 2008 13:01:12 -0800
Subject: sieve for dovecot
Message-ID: <7983ccf30812191301y5848fc11jc6b9b7587fc69341@mail.gmail.com>

Hi,

I installed dovecot from macports.  The imap server is running fine.

However, I wanted to have mail filtering on the imap server.  Dovecot
says that it works with sieve for filtering.  The problem is that
sieve is not available in the ports.  I tried compiling sieve for
dovecot, but the INSTALL file for the sieve says that I need the
pre-built dovecot sources available.  If sources are not available, it
requires the dovecot-config to present.

My questions are -

- Is there a sieve available in the ports somewhere that I am missing?
- Has anyone compiled sieve for dovecot?  If yes, please let me know
the magic ./configure line :-)
- Is there an alternative to sieve for filtering imap?

Any hints would be appreciated!

Thanks in advance

-- 
Raj Shekhar
blog : http://rajshekhar.net/blog  home : http://rajshekhar.net
Disclaimer : http://rajshekhar.net/disclaimer

From frstan at bellsouth.net  Fri Dec 19 13:10:32 2008
From: frstan at bellsouth.net (William Davis)
Date: Fri, 19 Dec 2008 16:10:32 -0500
Subject: Issues Upgrading Outdated Under 1.700
In-Reply-To: <c115fd3c0812190737g36f7e56cwaabd8b1c695e3587@mail.gmail.com>
References: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>
	<20081214211438.GC489@ninagal.withay.com>
	<c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>
	<49458454.9040302@macports.org>
	<c115fd3c0812190650s5d4f90b1v26d511d0a3f30503@mail.gmail.com>
	<D76E262D-49FE-49B0-AEAE-B59F3ECE2652@bellsouth.net>
	<c115fd3c0812190737g36f7e56cwaabd8b1c695e3587@mail.gmail.com>
Message-ID: <594AFB5B-0B3E-45D0-9B14-315DAC7D87AB@bellsouth.net>


On Dec 19, 2008, at 10:37 AM, Tim Visher wrote:

> On Fri, Dec 19, 2008 at 10:28 AM, William Davis  
> <frstan at bellsouth.net> wrote:
>> try:
>> sudo port -d clean boost
>> WD
>> On Dec 19, 2008, at 9:50 AM, Tim Visher wrote:
>
> Output:
>
> 	DEBUG: Found port in
> file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/boost
> 	DEBUG: Changing to port directory:
> /opt/local/var/macports/sources/rsync.macports.org/release/ports/ 
> devel/boost
> 	DEBUG: setting option os.universal_supported to yes
> 	DEBUG: org.macports.load registered provides 'load', a pre-existing
> procedure. Target override will not be provided
> 	DEBUG: org.macports.distfiles registered provides 'distfiles', a
> pre-existing procedure. Target override will not be provided
> 	DEBUG: adding the default universal variant
> 	DEBUG: Requested variant i386 is not provided by port boost.
> 	DEBUG: Requested variant macosx is not provided by port boost.
> 	DEBUG: Executing variant darwin_9 provides darwin_9
> 	DEBUG: Executing variant darwin provides darwin
> 	DEBUG: Executing org.macports.main (boost)
> 	Waiting for lock on
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_devel_boost/work/.macports.boost.state
>
> -- 
>
> In Christ,
>
> Timmy V.
>
> http://burningones.com/
> http://five.sentenc.es/ - Spend less time on e-mail

What command did you give? That doesn't look like the output of port  
clean -- it looks like port upgrade.


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

Mundus vult decepi, ego non


From brad at pixilla.com  Fri Dec 19 13:59:58 2008
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Fri, 19 Dec 2008 13:59:58 -0800
Subject: sieve for dovecot
In-Reply-To: <7983ccf30812191301y5848fc11jc6b9b7587fc69341@mail.gmail.com>
References: <7983ccf30812191301y5848fc11jc6b9b7587fc69341@mail.gmail.com>
Message-ID: <05C7DEEA-25F3-4309-84B2-8466D43FFC07@pixilla.com>

> My questions are -
>
> - Is there a sieve available in the ports somewhere that I am missing?
> - Has anyone compiled sieve for dovecot?  If yes, please let me know
> the magic ./configure line :-)
> - Is there an alternative to sieve for filtering imap?
>
> Any hints would be appreciated!

Though I can't contribute to your answer I'm working on dovecot +  
mysql and also will want sieve so I want to express my interest in  
this thread.


//Brad

From mark at dxradio.demon.co.uk  Fri Dec 19 14:23:35 2008
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Fri, 19 Dec 2008 22:23:35 +0000
Subject: sieve for dovecot
In-Reply-To: <7983ccf30812191301y5848fc11jc6b9b7587fc69341@mail.gmail.com>
References: <7983ccf30812191301y5848fc11jc6b9b7587fc69341@mail.gmail.com>
Message-ID: <10014CAA-FDCB-4F59-86D7-D74FB4B5D3B6@dxradio.demon.co.uk>


On 19 Dec 2008, at 21:01, Raj Shekhar wrote:

> Hi,
>
> I installed dovecot from macports.  The imap server is running fine.
>
> However, I wanted to have mail filtering on the imap server.  Dovecot
> says that it works with sieve for filtering.  The problem is that
> sieve is not available in the ports.  I tried compiling sieve for
> dovecot, but the INSTALL file for the sieve says that I need the
> pre-built dovecot sources available.  If sources are not available, it
> requires the dovecot-config to present.
>
> My questions are -
>
> - Is there a sieve available in the ports somewhere that I am missing?
> - Has anyone compiled sieve for dovecot?  If yes, please let me know
> the magic ./configure line :-)
> - Is there an alternative to sieve for filtering imap?
>
> Any hints would be appreciated!
>
> Thanks in advance
>
> --  
> Raj Shekhar


Hi Raj

I use the combination of

getmail
maildrop <> DSpam
dovecot

maildrop is available via Macports
http://www.courier-mta.org/maildrop/

As I also couldn't find a way of having Sieve work in Dovecot via  
MacPorts. Also Dovecot is now at 1.1.7 (MacPorts is at 1.1.3).

Mark Hattam

From r.shekhar at gmail.com  Fri Dec 19 15:37:41 2008
From: r.shekhar at gmail.com (Raj Shekhar)
Date: Fri, 19 Dec 2008 15:37:41 -0800
Subject: sieve for dovecot
In-Reply-To: <10014CAA-FDCB-4F59-86D7-D74FB4B5D3B6@dxradio.demon.co.uk>
References: <7983ccf30812191301y5848fc11jc6b9b7587fc69341@mail.gmail.com>
	<10014CAA-FDCB-4F59-86D7-D74FB4B5D3B6@dxradio.demon.co.uk>
Message-ID: <7983ccf30812191537y3a57062fme71d154ec4a2168f@mail.gmail.com>

On Fri, Dec 19, 2008 at 2:23 PM, Mark Hattam <mark at dxradio.demon.co.uk> wrote:

> maildrop is available via Macports
> http://www.courier-mta.org/maildrop/

Thanks for the tip!

Would you mind sharing your dovecot.conf lines where you made dovecot
use maildrop instead of whatever it uses as the default?

I am not able to find anything good when I search for dovecot+maildrop :-/

Thanks!

-- 
Raj Shekhar
blog : http://rajshekhar.net/blog  home : http://rajshekhar.net
Disclaimer : http://rajshekhar.net/disclaimer

From mark at dxradio.demon.co.uk  Fri Dec 19 15:57:27 2008
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Fri, 19 Dec 2008 23:57:27 +0000
Subject: sieve for dovecot
In-Reply-To: <7983ccf30812191537y3a57062fme71d154ec4a2168f@mail.gmail.com>
References: <7983ccf30812191301y5848fc11jc6b9b7587fc69341@mail.gmail.com>
	<10014CAA-FDCB-4F59-86D7-D74FB4B5D3B6@dxradio.demon.co.uk>
	<7983ccf30812191537y3a57062fme71d154ec4a2168f@mail.gmail.com>
Message-ID: <563090BB-5172-4DDA-87F6-C77BB0154E3E@dxradio.demon.co.uk>


On 19 Dec 2008, at 23:37, Raj Shekhar wrote:

> On Fri, Dec 19, 2008 at 2:23 PM, Mark Hattam  
> <mark at dxradio.demon.co.uk> wrote:
>
>> maildrop is available via Macports
>> http://www.courier-mta.org/maildrop/
>
> Thanks for the tip!
>
> Would you mind sharing your dovecot.conf lines where you made dovecot
> use maildrop instead of whatever it uses as the default?
>
> I am not able to find anything good when I search for dovecot 
> +maildrop :-/
>
> Thanks!
>
> -- 
> Raj Shekhar


You probably wouldn't. Dovecot does what it's told ... it serves the  
mail you've already sorted.

I call maildrop from getmail ... getmail connects to my ISP(s),  
downloads mail, deletes it from the ISP(s), then calls maildrop to  
process the mail.

In my  ~/.getmail/getmailrc  configuration, this tells it what to do  
with mail it receives

[destination]
type = MDA_external
path = /opt/local/bin/maildrop
unixfrom = True
user = <yourusername>

and Maildrop obeys the filters I've set up in   ~/.mailfilter

and the first thing in the .mailfilter that is done is to send off any/ 
all mail to DSpam


DEFAULT = "$HOME/Maildir"
xfilter "/opt/local/bin/dspam --user <yourusername> --process --stdout  
--deliver=innocent,spam"
if (/^X-DSPAM-Result: Spam.*$/)
{
     to "$DEFAULT/.Junk/"
}


So anything that doesn't come back flagged as Spam, then gets filtered  
into the desired places which is what you then see in Dovecot.


Mark

From r.shekhar at gmail.com  Fri Dec 19 16:12:25 2008
From: r.shekhar at gmail.com (Raj Shekhar)
Date: Fri, 19 Dec 2008 16:12:25 -0800
Subject: sieve for dovecot
In-Reply-To: <563090BB-5172-4DDA-87F6-C77BB0154E3E@dxradio.demon.co.uk>
References: <7983ccf30812191301y5848fc11jc6b9b7587fc69341@mail.gmail.com>
	<10014CAA-FDCB-4F59-86D7-D74FB4B5D3B6@dxradio.demon.co.uk>
	<7983ccf30812191537y3a57062fme71d154ec4a2168f@mail.gmail.com>
	<563090BB-5172-4DDA-87F6-C77BB0154E3E@dxradio.demon.co.uk>
Message-ID: <7983ccf30812191612j49f5129al7c26da64d5e5073c@mail.gmail.com>

On Fri, Dec 19, 2008 at 3:57 PM, Mark Hattam <mark at dxradio.demon.co.uk> wrote:

>
> You probably wouldn't. Dovecot does what it's told ... it serves the mail
> you've already sorted.

Doh! Thanks for setting me on the correct path!

>
> I call maildrop from getmail ... getmail connects to my ISP(s), downloads
> mail, deletes it from the ISP(s), then calls maildrop to process the mail.
>

As I have multiple accounts that I want to fetch to my local laptop,
this howto for ubuntu looks useful
<https://help.ubuntu.com/community/POP3Aggregator> (for anyone else
who wants to do something similar)


Thanks for your help!

-- 
Raj Shekhar
blog : http://rajshekhar.net/blog  home : http://rajshekhar.net
Disclaimer : http://rajshekhar.net/disclaimer

From mark at dxradio.demon.co.uk  Fri Dec 19 17:15:43 2008
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Sat, 20 Dec 2008 01:15:43 +0000
Subject: sieve for dovecot
In-Reply-To: <7983ccf30812191612j49f5129al7c26da64d5e5073c@mail.gmail.com>
References: <7983ccf30812191301y5848fc11jc6b9b7587fc69341@mail.gmail.com>
	<10014CAA-FDCB-4F59-86D7-D74FB4B5D3B6@dxradio.demon.co.uk>
	<7983ccf30812191537y3a57062fme71d154ec4a2168f@mail.gmail.com>
	<563090BB-5172-4DDA-87F6-C77BB0154E3E@dxradio.demon.co.uk>
	<7983ccf30812191612j49f5129al7c26da64d5e5073c@mail.gmail.com>
Message-ID: <DA5884C9-7CAE-4768-84E0-6F5B7FF252FE@dxradio.demon.co.uk>


On 20 Dec 2008, at 00:12, Raj Shekhar wrote:

> On Fri, Dec 19, 2008 at 3:57 PM, Mark Hattam  
> <mark at dxradio.demon.co.uk> wrote:
>
>>
>> You probably wouldn't. Dovecot does what it's told ... it serves  
>> the mail
>> you've already sorted.
>
> Doh! Thanks for setting me on the correct path!
>
>>
>> I call maildrop from getmail ... getmail connects to my ISP(s),  
>> downloads
>> mail, deletes it from the ISP(s), then calls maildrop to process  
>> the mail.
>>
>
> As I have multiple accounts that I want to fetch to my local laptop,
> this howto for ubuntu looks useful
> <https://help.ubuntu.com/community/POP3Aggregator> (for anyone else
> who wants to do something similar)
>
>
> Thanks for your help!
>
> -- 
> Raj Shekhar

Yep, that's pretty much it in principle.
I'm triggering getmail using a LaunchAgent rather than Cron, and yes  
you set a separate getmailrc file for each ISP account.
Also another watch folder Agent is watching a "you missed this spam"  
directory which I move any missed spam into.
DSpam is set up with a MySQL db store.


Mark


From ryandesign at macports.org  Fri Dec 19 20:51:52 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 19 Dec 2008 22:51:52 -0600
Subject: sieve for dovecot
In-Reply-To: <7983ccf30812191301y5848fc11jc6b9b7587fc69341@mail.gmail.com>
References: <7983ccf30812191301y5848fc11jc6b9b7587fc69341@mail.gmail.com>
Message-ID: <2187EA0D-4C2F-42FD-9F2B-DD69F65A72A4@macports.org>

On Dec 19, 2008, at 15:01, Raj Shekhar wrote:

> I installed dovecot from macports.  The imap server is running fine.
>
> However, I wanted to have mail filtering on the imap server.  Dovecot
> says that it works with sieve for filtering.  The problem is that
> sieve is not available in the ports.  I tried compiling sieve for
> dovecot, but the INSTALL file for the sieve says that I need the
> pre-built dovecot sources available.  If sources are not available, it
> requires the dovecot-config to present.
>
> My questions are -
>
> - Is there a sieve available in the ports somewhere that I am missing?

"port search sieve" says a port called libsieve is available.

> - Has anyone compiled sieve for dovecot?  If yes, please let me know
> the magic ./configure line :-)

There is an open ticket for this request, with an attached patch:

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

The ticket is old, but you can test whether the patch still works. If  
so (or if not), let us know. If not, and if you can update the patch  
so it works again, please attach it to the ticket so that we can  
finally commit it.

> - Is there an alternative to sieve for filtering imap?



From ryandesign at macports.org  Fri Dec 19 20:52:32 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 19 Dec 2008 22:52:32 -0600
Subject: sieve for dovecot
In-Reply-To: <10014CAA-FDCB-4F59-86D7-D74FB4B5D3B6@dxradio.demon.co.uk>
References: <7983ccf30812191301y5848fc11jc6b9b7587fc69341@mail.gmail.com>
	<10014CAA-FDCB-4F59-86D7-D74FB4B5D3B6@dxradio.demon.co.uk>
Message-ID: <329F0BB7-7594-4C15-BA89-BE578C9F4E41@macports.org>

On Dec 19, 2008, at 16:23, Mark Hattam wrote:

> Also Dovecot is now at 1.1.7 (MacPorts is at 1.1.3).

There is a ticket filed for this request:

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

If you would like to provide a patch implementing the request, and  
test it to make sure it works, and can attach the patch to the  
ticket, someone can commit it for you.



From tim.visher at gmail.com  Sat Dec 20 06:54:32 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Sat, 20 Dec 2008 09:54:32 -0500
Subject: Issues Upgrading Outdated Under 1.700
In-Reply-To: <594AFB5B-0B3E-45D0-9B14-315DAC7D87AB@bellsouth.net>
References: <c115fd3c0812141015y3f0ac74co290b37e70c68511b@mail.gmail.com>
	<20081214211438.GC489@ninagal.withay.com>
	<c115fd3c0812141356l63bd3a94s9b603e73da6d6ffb@mail.gmail.com>
	<49458454.9040302@macports.org>
	<c115fd3c0812190650s5d4f90b1v26d511d0a3f30503@mail.gmail.com>
	<D76E262D-49FE-49B0-AEAE-B59F3ECE2652@bellsouth.net>
	<c115fd3c0812190737g36f7e56cwaabd8b1c695e3587@mail.gmail.com>
	<594AFB5B-0B3E-45D0-9B14-315DAC7D87AB@bellsouth.net>
Message-ID: <c115fd3c0812200654v2e48ee65p87621620e6f00684@mail.gmail.com>

Well, I've had success.  It seems that once I got the other port
instance killed off, a few of the ports that were involved in the
previous upgrade effort had gotten corrupted and needed to be cleaned.
 I went through each of those and cleaned them and instaleld them
again and, voila!, it works.

Thanks for everyone's help!

-- 

In Christ,

Timmy V.

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

From tim.visher at gmail.com  Sat Dec 20 08:36:17 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Sat, 20 Dec 2008 11:36:17 -0500
Subject: MPlayer failing to install
Message-ID: <c115fd3c0812200836u152687b3o9b9edc748fa9a134@mail.gmail.com>

Hello Everyone,

I'm trying to get MPlayer installed again after my upgrade fiascos and
I'm encountering an error I don't know how to resolve.  I'm issuing
`sudo port install mplayer +osd +fribidi +smb +theora +xvid +x264
+binary_codecs +speex +faac +dv +twolame +dts +sdl +aa +caca` and all
of the dependencies build just fine.  However, when it gets to
mplayer, it fails with [this output](http://pastebin.com/m69578cb8).

Thoughts?

-- 

In Christ,

Timmy V.

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

From tim.visher at gmail.com  Sat Dec 20 08:49:57 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Sat, 20 Dec 2008 11:49:57 -0500
Subject: Unable to install dosbox because of conflict with mplayer?
Message-ID: <c115fd3c0812200849l5fc91f09w96c9e7da89de6b22@mail.gmail.com>

Hello all,

I'm trying to get dosbox and mplayer installed.  I already sent a
message about the issue I'm having with MPlayer but I'm also
discovering an issues with dosbox.  This is strange, because I just
had both of these packages installed but had to deactivate them to get
upgrades to work correctly.  Anyway,  I'm encountering the following
when attempting to install dosbox:

    [~]$ sudo port install -f dosbox
    --->  Installing speex @1.0.5_0
    Error: Target org.macports.install returned: Registry error: speex
@1.0.5_0 already registered as installed.  Please uninstall it first.
    Error: The following dependencies failed to build: libsdl_sound speex
    Error: Status 1 encountered during processing.

The reason I'm using the -f flag is because dosbox had previously
reported the following:

    [~]$ sudo port install dosbox
    Password:
    --->  Installing speex @1.0.5_0
    --->  Activating speex @1.0.5_0
    Error: Target org.macports.activate returned: Image error:
/opt/local/bin/speexdec is being used by the active speex-devel port.
Please deactivate this port first, or use the -f flag to force the
activation.
    Error: The following dependencies failed to build: libsdl_sound speex
    Error: Status 1 encountered during processing.

It seems that there may be some sort of weird multi-branch dependency
that port can't figure out how to resolve between dosbox and mplayer?

Anyway, help would be appreciated.

-- 

In Christ,

Timmy V.

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

From matt at rainboxx.de  Sat Dec 20 06:57:37 2008
From: matt at rainboxx.de (Matthias Dietrich)
Date: Sat, 20 Dec 2008 15:57:37 +0100
Subject: Upgrading ncurses & ncursesw fails
Message-ID: <D3CBF654-9544-4CF0-B109-D0042F37B57F@rainboxx.de>

Hi list,

I just migrated from a MacBook Air to a new MacBook Pro.  I tried to  
upgrade first all outdated ports, when failed I tried to upgrad all  
installed ports (I thought there may be a problem from the migration)  
but it fails also at ncurses. The installation process hangs after the  
following output:

   You may see messages regarding extended capabilities, e.g., AX.
   These are extended terminal capabilities which are compiled
   using
   	tic -x
   If you have ncurses 4.2 applications, you should read the INSTALL
   document, and install the terminfo without the -x option.

I googled and found that this may be a dependency problem, so I tried  
to upgrad ncursesw manually after cleaning both ncurses and ncursesw.   
But upgrading ncrusesw fails, too, with the following messages:

   --->  Unable to uninstall ncursesw 5.7_0, the following ports  
depend on it:
   --->    ncurses
   Warning: Uninstall forced.  Proceeding despite dependencies.
   Error: Uninstall ncursesw 5.7_0 failed: Registry error: Please  
specify the name of the port.

So, ncursesw cannot be updated because it depends on ncurses, and  
ncurses cannot be updated because it depends on ncursesw (which it  
doesn't know).  Now, how can I do an `upgrade outdated`?

Need help :)!

Greetings,
  matt

P.S.: I noticed that there are two versions of ncurses installed:

    The following ports are currently installed:
      ncurses @5.6_0 (active)
      ncurses @5.7_0 (active)

Is this a problem?


-- 
rainboxx Matthias Dietrich
Freier Software Engineer

rainboxx                  |  Tel.: +49 (0) 151 / 50 60 78 64
T?lzer Str. 19            |  Mail: matt at rainboxx.de
70372 Stuttgart           |  WWW : http://www.rainboxx.de

XING: https://www.xing.com/profile/Matthias_Dietrich18
GULP: http://www.gulp.de/profil/rainboxx.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: Signierter Teil der Nachricht
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081220/2754d28d/attachment.bin>

From blb at macports.org  Sat Dec 20 12:56:06 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sat, 20 Dec 2008 13:56:06 -0700
Subject: MPlayer failing to install
In-Reply-To: <c115fd3c0812200836u152687b3o9b9edc748fa9a134@mail.gmail.com>
References: <c115fd3c0812200836u152687b3o9b9edc748fa9a134@mail.gmail.com>
Message-ID: <20081220205606.GC783@ninagal.withay.com>

On Sat, Dec 20, 2008 at 11:36:17AM -0500, Tim Visher said:
> Hello Everyone,
> 
> I'm trying to get MPlayer installed again after my upgrade fiascos and
> I'm encountering an error I don't know how to resolve.  I'm issuing
> `sudo port install mplayer +osd +fribidi +smb +theora +xvid +x264
> +binary_codecs +speex +faac +dv +twolame +dts +sdl +aa +caca` and all
> of the dependencies build just fine.  However, when it gets to
> mplayer, it fails with [this output](http://pastebin.com/m69578cb8).

From the output:
> /usr/bin/gcc-4.0 -o mplayer mplayer.o m_property.o mp_fifo.o mp_msg.o mixer.o parser-mpcmd.o subopt-helper.o command.o asxparser.o codec-cfg.o cpudetect.o edl.o find_sub.o get_path.o m_config.o m_option.o m_struct.o mpcommon.o parser-cfg.o playtree.o playtreeparser.o spudec.o sub_cc.o subreader.o vobsub.o libvo/libvo.a libao2/libao2.a input/libinput.a libmenu/libmenu.a libmpcodecs/libmpcodecs.a libaf/libaf.a libmpdemux/libmpdemux.a stream/stream.a libswscale/libswscale.a libvo/libosd.a libavformat/libavformat.a libavcodec/libavcodec.a libavutil/libavutil.a libpostproc/libpostproc.a loader/libloader.a mp3lib/libmp3.a liba52/liba52.a libmpeg2/libmpeg2.a libfaad2/libfaad2.a tremor/libvorbisidec.a dvdread/libdvdread.a libdvdcss/libdvdcss.a osdep/libosdep.a -laa -lcaca -lX11 -lncurses -lncurses -L/usr/X11/lib -L/opt/local/lib -L/opt/local/lib -L/opt/local/lib/samba3 -L/usr/local/lib -liconv -lncurses -framework Carbon -framework QuickTime -framework CoreAudio -framework AudioUnit -framework AudioToolbox -framework Cocoa -framework QuartzCore -framework OpenGL -framework IOKit -lsmbclient -lpng -lz -ljpeg -lgif -framework IOKit -L/opt/local/lib -lfreetype -lz -llzo2 -lmad -ltheora -logg     -lm
> ld: library not found for -lgif

It looks like it isn't finding the GIF library, which should be installed
with the giflib port; MPlayer does declare a dependency on giflib, so it
should have been installed.  Does it show up with 'port installed giflib'?

Bryan


> 
> Thoughts?
> 
> -- 
> 
> In Christ,
> 
> Timmy V.
> 
> http://burningones.com/
> http://five.sentenc.es/ - Spend less time on e-mail

From blb at macports.org  Sat Dec 20 13:00:56 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sat, 20 Dec 2008 14:00:56 -0700
Subject: Unable to install dosbox because of conflict with mplayer?
In-Reply-To: <c115fd3c0812200849l5fc91f09w96c9e7da89de6b22@mail.gmail.com>
References: <c115fd3c0812200849l5fc91f09w96c9e7da89de6b22@mail.gmail.com>
Message-ID: <20081220210056.GD783@ninagal.withay.com>

On Sat, Dec 20, 2008 at 11:49:57AM -0500, Tim Visher said:
> Hello all,
> 
> I'm trying to get dosbox and mplayer installed.  I already sent a
> message about the issue I'm having with MPlayer but I'm also
> discovering an issues with dosbox.  This is strange, because I just
> had both of these packages installed but had to deactivate them to get
> upgrades to work correctly.  Anyway,  I'm encountering the following
> when attempting to install dosbox:
> 
>     [~]$ sudo port install -f dosbox
>     --->  Installing speex @1.0.5_0
>     Error: Target org.macports.install returned: Registry error: speex
> @1.0.5_0 already registered as installed.  Please uninstall it first.
>     Error: The following dependencies failed to build: libsdl_sound speex
>     Error: Status 1 encountered during processing.
> 
> The reason I'm using the -f flag is because dosbox had previously
> reported the following:

Using force (-f) can have odd results, like this, when you start dealing
with dependencies as well; it's really best to use force only in certain
specific cases, and only when dealing with one port at a time, so using it
for install can be risky at best.

> 
>     [~]$ sudo port install dosbox
>     Password:
>     --->  Installing speex @1.0.5_0
>     --->  Activating speex @1.0.5_0
>     Error: Target org.macports.activate returned: Image error:
> /opt/local/bin/speexdec is being used by the active speex-devel port.
> Please deactivate this port first, or use the -f flag to force the
> activation.
>     Error: The following dependencies failed to build: libsdl_sound speex
>     Error: Status 1 encountered during processing.
> 
> It seems that there may be some sort of weird multi-branch dependency
> that port can't figure out how to resolve between dosbox and mplayer?

It sounds like you already have speex-devel installed (which is the
in-development version compared to speex), so it makes sense that speex
would conflict with it.

As a dependency, the best way to deal with this would be to update the
libsdl_sound port (which is what wants speex) to also allow speex-devel by
using a path:some/file/speex/installs:speex so it can make use of an
already-installed speex-devel.  Someone who knows more about libsdl_sound
and speex would need to determine if this is in fact feasible.

Bryan


> 
> Anyway, help would be appreciated.
> 
> -- 
> 
> In Christ,
> 
> Timmy V.
> 
> http://burningones.com/
> http://five.sentenc.es/ - Spend less time on e-mail

From blb at macports.org  Sat Dec 20 13:03:55 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sat, 20 Dec 2008 14:03:55 -0700
Subject: Upgrading ncurses & ncursesw fails
In-Reply-To: <D3CBF654-9544-4CF0-B109-D0042F37B57F@rainboxx.de>
References: <D3CBF654-9544-4CF0-B109-D0042F37B57F@rainboxx.de>
Message-ID: <20081220210355.GE783@ninagal.withay.com>

On Sat, Dec 20, 2008 at 03:57:37PM +0100, Matthias Dietrich said:
> Hi list,
>
> I just migrated from a MacBook Air to a new MacBook Pro.  I tried to  
> upgrade first all outdated ports, when failed I tried to upgrad all  
> installed ports (I thought there may be a problem from the migration) but 
> it fails also at ncurses. The installation process hangs after the  
> following output:
>
>   You may see messages regarding extended capabilities, e.g., AX.
>   These are extended terminal capabilities which are compiled
>   using
>   	tic -x
>   If you have ncurses 4.2 applications, you should read the INSTALL
>   document, and install the terminfo without the -x option.
>
> I googled and found that this may be a dependency problem, so I tried to 
> upgrad ncursesw manually after cleaning both ncurses and ncursesw.  But 
> upgrading ncrusesw fails, too, with the following messages:
>
>   --->  Unable to uninstall ncursesw 5.7_0, the following ports depend on 
> it:
>   --->    ncurses
>   Warning: Uninstall forced.  Proceeding despite dependencies.
>   Error: Uninstall ncursesw 5.7_0 failed: Registry error: Please specify 
> the name of the port.

What were the exact commands you used to get to this point?

>
> So, ncursesw cannot be updated because it depends on ncurses, and ncurses 
> cannot be updated because it depends on ncursesw (which it doesn't know).  
> Now, how can I do an `upgrade outdated`?
>
> Need help :)!
>
> Greetings,
>  matt
>
> P.S.: I noticed that there are two versions of ncurses installed:
>
>    The following ports are currently installed:
>      ncurses @5.6_0 (active)
>      ncurses @5.7_0 (active)
>
> Is this a problem?

Yeah, that looks wrong, both shouldn't be active at the same time; how about
for the ncursesw port?  Are there any other ports which are like this?  If
not, it can probably be fixed with some forced uninstalling of those, and
reinstalling.

Bryan


>
>
> -- 
> rainboxx Matthias Dietrich
> Freier Software Engineer
>
> rainboxx                  |  Tel.: +49 (0) 151 / 50 60 78 64
> T?lzer Str. 19            |  Mail: matt at rainboxx.de
> 70372 Stuttgart           |  WWW : http://www.rainboxx.de
>
> XING: https://www.xing.com/profile/Matthias_Dietrich18
> GULP: http://www.gulp.de/profil/rainboxx.html
>

From masschel at gmail.com  Sat Dec 20 17:40:31 2008
From: masschel at gmail.com (Bart Masschelein)
Date: Sun, 21 Dec 2008 02:40:31 +0100
Subject: How to keep source
Message-ID: <0DFC4DBE-A7AB-48E1-82C4-463C695F5985@gmail.com>

Hi all,

I'm using mono from MacPorts, and at a point my program crashes,  
pointing to the following file

/opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_devel_mono/work/mono-2.0.1/mcs/class/ 
System/System.Net.Sockets/Socket.cs

This file is not there however. I assume it is put there termporarily,  
and removed after install. Which steps should I undertake (and  
especially which not) in order to keep those source files?

Thanks in advance,

Bart


From lionteeth at cogweb.net  Sat Dec 20 23:37:02 2008
From: lionteeth at cogweb.net (David Liontooth)
Date: Sat, 20 Dec 2008 23:37:02 -0800
Subject: munin
Message-ID: <494DF21E.3020304@cogweb.net>

Is anyone using munin? If someone would volunteer to package it, that 
would be much appreciated. It's a nice cross-platform monitoring package.

I noticed Dave Cameron submitted an rrdtool bug indicating he has munin 
running on OSX, http://trac.macports.org/ticket/16534.

We could perhaps start by sharing installation experiences?

Dave

From spam.spam.spam.spam at free.fr  Sun Dec 21 01:19:31 2008
From: spam.spam.spam.spam at free.fr (spam.spam.spam.spam at free.fr)
Date: Sun, 21 Dec 2008 10:19:31 +0100
Subject: Error installing xpdf with openmotif
Message-ID: <1229851171.494e0a23ad995@imp.free.fr>

Hello,
When I install xpdf, I get this :
$ sudo port install xpdf
Password:
--->  Building openmotif
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_openmotif/work/openmotif-2.3.1"
&& make all " returned error 2
Command output: /usr/X11R6/include/X11/Xft/Xft.h:191: error: parse error before
'*' token
/usr/X11R6/include/X11/Xft/Xft.h:257: warning: type defaults to 'int' in
declaration of 'XftGlyphSpec'
/usr/X11R6/include/X11/Xft/Xft.h:257: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:263: warning: type defaults to 'int' in
declaration of 'XftGlyphFontSpec'
/usr/X11R6/include/X11/Xft/Xft.h:263: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:296: warning: type defaults to 'int' in
declaration of 'FT_UInt'
/usr/X11R6/include/X11/Xft/Xft.h:296: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:355: error: parse error before 'XftLockFace'
/usr/X11R6/include/X11/Xft/Xft.h:355: warning: type defaults to 'int' in
declaration of 'XftLockFace'
/usr/X11R6/include/X11/Xft/Xft.h:355: warning: data definition has no type or
storage class
/usr/X11R6/include/X11/Xft/Xft.h:394: warning: type defaults to 'int' in
declaration of 'FT_UInt'
/usr/X11R6/include/X11/Xft/Xft.h:394: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:400: warning: type defaults to 'int' in
declaration of 'FT_UInt'
/usr/X11R6/include/X11/Xft/Xft.h:400: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:409: error: parse error before 'FT_UInt'
/usr/X11R6/include/X11/Xft/Xft.h:419: error: parse error before 'XftCharIndex'
/usr/X11R6/include/X11/Xft/Xft.h:421: warning: type defaults to 'int' in
declaration of 'XftCharIndex'
/usr/X11R6/include/X11/Xft/Xft.h:421: warning: data definition has no type or
storage class
/usr/X11R6/include/X11/Xft/Xft.h:462: warning: type defaults to 'int' in
declaration of 'FT_UInt'
/usr/X11R6/include/X11/Xft/Xft.h:462: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:473: warning: type defaults to 'int' in
declaration of 'XftGlyphSpec'
/usr/X11R6/include/X11/Xft/Xft.h:473: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:494: warning: type defaults to 'int' in
declaration of 'XftGlyphFontSpec'
/usr/X11R6/include/X11/Xft/Xft.h:494: error: parse error before '*' token
List.c: In function 'MakeGC':
List.c:2773: warning: passing argument 1 of '_XmAssignInsensitiveColor' from
incompatible pointer type
make[3]: *** [List.lo] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

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

So I try to install openmotif :
$ sudo port install openmotif
--->  Building openmotif
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_openmotif/work/openmotif-2.3.1"
&& make all " returned error 2
Command output: /usr/X11R6/include/X11/Xft/Xft.h:191: error: parse error before
'*' token
/usr/X11R6/include/X11/Xft/Xft.h:257: warning: type defaults to 'int' in
declaration of 'XftGlyphSpec'
/usr/X11R6/include/X11/Xft/Xft.h:257: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:263: warning: type defaults to 'int' in
declaration of 'XftGlyphFontSpec'
/usr/X11R6/include/X11/Xft/Xft.h:263: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:296: warning: type defaults to 'int' in
declaration of 'FT_UInt'
/usr/X11R6/include/X11/Xft/Xft.h:296: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:355: error: parse error before 'XftLockFace'
/usr/X11R6/include/X11/Xft/Xft.h:355: warning: type defaults to 'int' in
declaration of 'XftLockFace'
/usr/X11R6/include/X11/Xft/Xft.h:355: warning: data definition has no type or
storage class
/usr/X11R6/include/X11/Xft/Xft.h:394: warning: type defaults to 'int' in
declaration of 'FT_UInt'
/usr/X11R6/include/X11/Xft/Xft.h:394: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:400: warning: type defaults to 'int' in
declaration of 'FT_UInt'
/usr/X11R6/include/X11/Xft/Xft.h:400: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:409: error: parse error before 'FT_UInt'
/usr/X11R6/include/X11/Xft/Xft.h:419: error: parse error before 'XftCharIndex'
/usr/X11R6/include/X11/Xft/Xft.h:421: warning: type defaults to 'int' in
declaration of 'XftCharIndex'
/usr/X11R6/include/X11/Xft/Xft.h:421: warning: data definition has no type or
storage class
/usr/X11R6/include/X11/Xft/Xft.h:462: warning: type defaults to 'int' in
declaration of 'FT_UInt'
/usr/X11R6/include/X11/Xft/Xft.h:462: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:473: warning: type defaults to 'int' in
declaration of 'XftGlyphSpec'
/usr/X11R6/include/X11/Xft/Xft.h:473: error: parse error before '*' token
/usr/X11R6/include/X11/Xft/Xft.h:494: warning: type defaults to 'int' in
declaration of 'XftGlyphFontSpec'
/usr/X11R6/include/X11/Xft/Xft.h:494: error: parse error before '*' token
List.c: In function 'MakeGC':
List.c:2773: warning: passing argument 1 of '_XmAssignInsensitiveColor' from
incompatible pointer type
make[3]: *** [List.lo] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

Error: Status 1 encountered during processing.

I am on MaxOSX Tiger with port Version: 1.700.
Thank you for help.

From jjstickel at vcn.com  Sun Dec 21 07:45:51 2008
From: jjstickel at vcn.com (Jonathan Stickel)
Date: Sun, 21 Dec 2008 08:45:51 -0700
Subject: KDE3 broken
Message-ID: <494E64AF.3070808@vcn.com>

KDE3 is broken for me since recently upgrading to Macports 1.7. 
Everything installs fine, but no kde application will start.  Among many 
messages, I see (e.g. when trying kwrite):

KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kwrite path = <unknown> pid = 8226

Any ideas?  I am a heavy user of kde apps, especially konqueror for file 
  management.  I am using Tiger (10.4.11).

Thanks,
Jonathan

From brad at pixilla.com  Sun Dec 21 09:40:24 2008
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Sun, 21 Dec 2008 09:40:24 -0800
Subject: How to keep source
In-Reply-To: <0DFC4DBE-A7AB-48E1-82C4-463C695F5985@gmail.com>
References: <0DFC4DBE-A7AB-48E1-82C4-463C695F5985@gmail.com>
Message-ID: <D0CB4274-8FF6-430D-972C-CA268AAE0594@pixilla.com>

I don't know the answer to your problem but if you want to look at the  
files in work you could do:

# port extract mono
cd `port dir mono`
ls work/


On Dec 20, 2008, at 5:40 PM, Bart Masschelein wrote:

> Hi all,
>
> I'm using mono from MacPorts, and at a point my program crashes,  
> pointing to the following file
>
> /opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_devel_mono/work/mono-2.0.1/mcs/class/ 
> System/System.Net.Sockets/Socket.cs
>
> This file is not there however. I assume it is put there  
> termporarily, and removed after install. Which steps should I  
> undertake (and especially which not) in order to keep those source  
> files?
>
> Thanks in advance,
>
> Bart
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


From dluke at geeklair.net  Sun Dec 21 09:43:19 2008
From: dluke at geeklair.net (Daniel J. Luke)
Date: Sun, 21 Dec 2008 12:43:19 -0500
Subject: How to keep source
In-Reply-To: <0DFC4DBE-A7AB-48E1-82C4-463C695F5985@gmail.com>
References: <0DFC4DBE-A7AB-48E1-82C4-463C695F5985@gmail.com>
Message-ID: <2501AB68-69A3-467A-B5C8-2B1509638FD4@geeklair.net>

On Dec 20, 2008, at 8:40 PM, Bart Masschelein wrote:
> This file is not there however. I assume it is put there  
> termporarily, and removed after install. Which steps should I  
> undertake (and especially which not) in order to keep those source  
> files?


from the macports.conf manpage:

      portautoclean
          Automatic cleaning of the build directory of a given port  
after it
          has been installed.
          Default: yes

So, if you really want the source (and objects) for ever port you  
build to stay around unless you explicitly clean them, then you'll  
want to set this to 'no'

--
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/20081221/4e3b5157/attachment.bin>

From brad at pixilla.com  Sun Dec 21 09:56:37 2008
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Sun, 21 Dec 2008 09:56:37 -0800
Subject: configuring port
In-Reply-To: <BA3B3C12-8980-42E1-959B-A15A6E3B8BC2@geeklair.net>
References: <620ABA27-1233-4A34-BA68-511BDC4E3689@pixilla.com>
	<BA3B3C12-8980-42E1-959B-A15A6E3B8BC2@geeklair.net>
Message-ID: <6F6F958E-D9F8-4271-B180-A318F091A811@pixilla.com>

> On Dec 19, 2008, at 10:16 AM, Bradley Giesbrecht wrote:
>> Is there some reading that someone could point me to that could  
>> help me with downloading and reconfiguring a port from macports?
>
> The guide should help you out, especially:
>
> http://guide.macports.org/#development
>
>> I'm looking to take advantage of the macports patches and handling  
>> of dependies.
>
>
> If you think your variants would be useful to more than just you,  
> I'm sure we'd be glad to add them. Please file tickets with your  
> proposed patches if so.

Daniel, I see you are the macports maintainer for bind9 which I am  
trying to create a variant for. I wouldn't call my work patch quality  
yet.

If I wanted to share what I have found with a maintainer and get some  
feedback and learn enough about macports to be able to offer quality  
patches is there an email list or forum target for this type of  
discussion?


TIA,

Brad

From tim.visher at gmail.com  Sun Dec 21 10:52:56 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Sun, 21 Dec 2008 13:52:56 -0500
Subject: MPlayer failing to install
In-Reply-To: <20081220205606.GC783@ninagal.withay.com>
References: <c115fd3c0812200836u152687b3o9b9edc748fa9a134@mail.gmail.com>
	<20081220205606.GC783@ninagal.withay.com>
Message-ID: <c115fd3c0812211052w68bd7e16w8a8f32308bb2936@mail.gmail.com>

On Sat, Dec 20, 2008 at 3:56 PM, Bryan Blackburn <blb at macports.org> wrote:

> Does it show up with 'port installed giflib'?

Nope. It didn't.  Weird.

I went ahead and installed giflib manually and ran into another weird
problem.  Apparently, gif2epsn, which giflib depends on, was already
being used by another port, libungif.  I deactivated libungif, and
then installed giflib with no problem.  Now, when I tried to activate
libungif, it gets the same issue.  I activated with the `-f` flag and
I got the following output.

    Warning: File /opt/local/bin/gif2epsn already exists.  Moving to:
/opt/local/bin/gif2epsn.mp_1229884393.
    Warning: File /opt/local/bin/gif2ps already exists.  Moving to:
/opt/local/bin/gif2ps.mp_1229884393.
    Warning: File /opt/local/bin/gif2rgb already exists.  Moving to:
/opt/local/bin/gif2rgb.mp_1229884393.
    Warning: File /opt/local/bin/gifasm already exists.  Moving to:
/opt/local/bin/gifasm.mp_1229884393.
    Warning: File /opt/local/bin/gifbg already exists.  Moving to:
/opt/local/bin/gifbg.mp_1229884393.
    Warning: File /opt/local/bin/gifburst already exists.  Moving to:
/opt/local/bin/gifburst.mp_1229884393.
    Warning: File /opt/local/bin/gifclip already exists.  Moving to:
/opt/local/bin/gifclip.mp_1229884393.
    Warning: File /opt/local/bin/gifclrmp already exists.  Moving to:
/opt/local/bin/gifclrmp.mp_1229884393.
    Warning: File /opt/local/bin/gifcolor already exists.  Moving to:
/opt/local/bin/gifcolor.mp_1229884393.
    Warning: File /opt/local/bin/gifcomb already exists.  Moving to:
/opt/local/bin/gifcomb.mp_1229884393.
    Warning: File /opt/local/bin/gifcompose already exists.  Moving
to: /opt/local/bin/gifcompose.mp_1229884393.
    Warning: File /opt/local/bin/giffiltr already exists.  Moving to:
/opt/local/bin/giffiltr.mp_1229884393.
    Warning: File /opt/local/bin/giffix already exists.  Moving to:
/opt/local/bin/giffix.mp_1229884393.
    Warning: File /opt/local/bin/gifflip already exists.  Moving to:
/opt/local/bin/gifflip.mp_1229884393.
    Warning: File /opt/local/bin/gifhisto already exists.  Moving to:
/opt/local/bin/gifhisto.mp_1229884393.
    Warning: File /opt/local/bin/gifinfo already exists.  Moving to:
/opt/local/bin/gifinfo.mp_1229884393.
    Warning: File /opt/local/bin/gifinter already exists.  Moving to:
/opt/local/bin/gifinter.mp_1229884393.
    Warning: File /opt/local/bin/gifinto already exists.  Moving to:
/opt/local/bin/gifinto.mp_1229884393.
    Warning: File /opt/local/bin/gifovly already exists.  Moving to:
/opt/local/bin/gifovly.mp_1229884393.
    Warning: File /opt/local/bin/gifpos already exists.  Moving to:
/opt/local/bin/gifpos.mp_1229884393.
    Warning: File /opt/local/bin/gifrotat already exists.  Moving to:
/opt/local/bin/gifrotat.mp_1229884393.
    Warning: File /opt/local/bin/gifrsize already exists.  Moving to:
/opt/local/bin/gifrsize.mp_1229884393.
    Warning: File /opt/local/bin/gifspnge already exists.  Moving to:
/opt/local/bin/gifspnge.mp_1229884393.
    Warning: File /opt/local/bin/giftext already exists.  Moving to:
/opt/local/bin/giftext.mp_1229884393.
    Warning: File /opt/local/bin/gifwedge already exists.  Moving to:
/opt/local/bin/gifwedge.mp_1229884393.
    Warning: File /opt/local/bin/icon2gif already exists.  Moving to:
/opt/local/bin/icon2gif.mp_1229884393.
    Warning: File /opt/local/bin/raw2gif already exists.  Moving to:
/opt/local/bin/raw2gif.mp_1229884393.
    Warning: File /opt/local/bin/rgb2gif already exists.  Moving to:
/opt/local/bin/rgb2gif.mp_1229884393.
    Warning: File /opt/local/bin/text2gif already exists.  Moving to:
/opt/local/bin/text2gif.mp_1229884393.
    Warning: File /opt/local/include/gif_lib.h already exists.  Moving
to: /opt/local/include/gif_lib.h.mp_1229884393.

However, despite that, mplayer now installs, which is cool.  I'm just
concerned that something I want was depending somehow on libungif and
now I broke that.  But, oh well.

Thanks for all your help! :)

-- 

In Christ,

Timmy V.

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

From matt at rainboxx.de  Sun Dec 21 08:17:17 2008
From: matt at rainboxx.de (Matthias Dietrich)
Date: Sun, 21 Dec 2008 17:17:17 +0100
Subject: Upgrading ncurses & ncursesw fails
In-Reply-To: <20081220210355.GE783@ninagal.withay.com>
References: <D3CBF654-9544-4CF0-B109-D0042F37B57F@rainboxx.de>
	<20081220210355.GE783@ninagal.withay.com>
Message-ID: <34235064-1927-4417-B3FA-53FFE167A497@rainboxx.de>

Hi,

>> --->  Unable to uninstall ncursesw 5.7_0, the following ports  
>> depend on
>> it:
>> --->    ncurses
>> Warning: Uninstall forced.  Proceeding despite dependencies.
>> Error: Uninstall ncursesw 5.7_0 failed: Registry error: Please  
>> specify
>> the name of the port.
>
> What were the exact commands you used to get to this point?

the command was:
  sudo port -f upgrade ncurses

I used the f flag because there were errors without but I cannot  
reproduce them now (the errors without the f flag).

> Yeah, that looks wrong, both shouldn't be active at the same time;  
> how about
> for the ncursesw port?

There are two active ports two:

  The following ports are currently installed:
    ncursesw @5.6_1 (active)
    ncursesw @5.7_0 (active)

> Are there any other ports which are like this?

Phew!  There are plenty of ports installed twice!  Here is the list of  
all currently installed ports:

  2Pong @0.6_1 (active)
  4th @3.5c3_0 (active)
  54321 @1.0.2001.11.16_0 (active)
  9e @1.0_0 (active)
  a2ps @4.13b_3 (active)
  aalib @1.4rc5_3 (active)
  apache2 @2.2.9_1+darwin_9 (active)
  apache2 @2.2.11_0+darwin_9 (active)
  apr @1.2.12_1+darwin_9 (active)
  apr-util @1.2.12_0 (active)
  autoconf @2.62_0 (active)
  autoconf @2.63_0 (active)
  autoconf213 @2.13_0 (active)
  automake @1.10.1_0 (active)
  automake @1.10.2_0 (active)
  bison @2.3_2 (active)
  bison @2.4_1 (active)
  bzip2 @1.0.4_1 (active)
  bzip2 @1.0.5_1 (active)
  cairo @1.4.14_0 (active)
  cairo @1.8.4_1+macosx (active)
  curl @7.18.2_0 (active)
  curl @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)
  expat @2.0.1_0 (active)
  fontconfig @2.5.0_0+macosx (active)
  fontconfig @2.6.0_1+macosx (active)
  freetype @2.3.5_1 (active)
  freetype @2.3.7_3+macosx (active)
  gawk @3.1.6_0 (active)
  gd2 @2.0.35_1 (active)
  gd2 @2.0.35_2 (active)
  gdk-pixbuf @0.22.0_1 (active)
  gettext @0.17_3 (active)
  giflib @4.1.6_0
  glib1 @1.2.10_5 (active)
  glib2 @2.14.6_0+darwin_9 (active)
  glib2 @2.18.3_0+darwin_9 (active)
  gnupg @1.4.9_0 (active)
  gperf @3.0.3_0 (active)
  graphviz @2.16.1_1 (active)
  graphviz @2.20.3_0+darwin_9 (active)
  gtk1 @1.2.10_6 (active)
  gtk1 @1.2.10_7 (active)
  help2man @1.36.4_1 (active)
  jbigkit @1.6_0 (active)
  jpeg @6b_2 (active)
  jpeg @6b_3 (active)
  lcms @1.16_0 (active)
  lcms @1.17_0 (active)
  libart_lgpl @2.3.20_0 (active)
  libexif @0.6.16_1 (active)
  libexif @0.6.17_0 (active)
  libgdiplus @1.2.6_1 (active)
  libiconv @1.12_0 (active)
  libmcrypt @2.5.8_0 (active)
  libogg @1.1.3_2 (active)
  libpcap @0.9.8_0 (active)
  libpcap @1.0.0_0 (active)
  libpixman @0.12.0_1 (active)
  libpng @1.2.25_0 (active)
  libpng @1.2.34_0 (active)
  libsdl @1.2.13_1 (active)
  libsdl @1.2.13_2 (active)
  libsdl_image @1.2.6_3 (active)
  libsdl_mixer @1.2.8_0 (active)
  libsdl_mixer @1.2.8_1 (active)
  libtool @1.5.26_0 (active)
  libungif @4.1.4_2 (active)
  libungif @4.1.4_3 (active)
  libusb @0.1.12_1 (active)
  libvorbis @1.2.0_0 (active)
  libvorbis @1.2.0_1 (active)
  libxml2 @2.6.31_0 (active)
  libxml2 @2.7.2_1+darwin_9 (active)
  libxslt @1.1.22_0 (active)
  libxslt @1.1.24_1+darwin_9 (active)
  lynx @2.8.6rel.5_1+ssl (active)
  m4 @1.4.10_1 (active)
  m4 @1.4.12_1 (active)
  mhash @0.9.9_0 (active)
  mhash @0.9.9.9_0 (active)
  mod_perl @1.30_0 (active)
  mod_perl2 @2.0.3_0 (active)
  mono @1.2.6_0+darwin_9 (active)
  mono @2.0.1_0+darwin_9 (active)
  mysql5 @5.0.67_1+server (active)
  ncurses @5.6_0 (active)
  ncurses @5.7_0 (active)
  ncursesw @5.6_1 (active)
  ncursesw @5.7_0 (active)
  neon @0.26.4_0 (active)
  neon @0.28.3_0 (active)
  nmap @4.50_0 (active)
  nmap @4.76_0 (active)
  openssl @0.9.8g_0 (active)
  openssl @0.9.8i_0 (active)
  ossp-uuid @1.6.0_1 (active)
  ossp-uuid @1.6.2_0 (active)
  p5-archive-tar @1.38_0 (active)
  p5-archive-tar @1.40_0 (active)
  p5-compress-raw-bzip2 @2.015_0 (active)
  p5-compress-raw-zlib @2.008_0 (active)
  p5-compress-raw-zlib @2.015_0 (active)
  p5-compress-zlib @2.008_0 (active)
  p5-compress-zlib @2.015_0 (active)
  p5-digest-sha @5.47_0
  p5-extutils-cbuilder @0.22_0 (active)
  p5-extutils-cbuilder @0.24_0 (active)
  p5-extutils-parsexs @2.19_0 (active)
  p5-gd @2.35_0 (active)
  p5-gd-securityimage @1.65_0 (active)
  p5-graph @0.84_0 (active)
  p5-graphviz @2.03_0 (active)
  p5-heap @0.80_0 (active)
  p5-html-parser @3.56_0 (active)
  p5-html-parser @3.59_0 (active)
  p5-html-tagset @3.20_0 (active)
  p5-io-compress-base @2.008_0 (active)
  p5-io-compress-base @2.015_0 (active)
  p5-io-compress-bzip2 @2.015_0 (active)
  p5-io-compress-zlib @2.008_0 (active)
  p5-io-compress-zlib @2.015_0 (active)
  p5-io-zlib @1.09_0 (active)
  p5-ipc-run @0.80_0
  p5-ipc-run @0.82_0 (active)
  p5-locale-gettext @1.05_0 (active)
  p5-math-bezier @0.01_0 (active)
  p5-package-constants @0.01_0
  p5-package-constants @0.02_0
  p5-scalar-list-utils @1.19_0
  p5-scalar-list-utils @1.19_1
  p5-universal-require @0.11_0 (active)
  p5-version @0.74_0 (active)
  p5-version @0.76_0 (active)
  pango @1.18.4_0 (active)
  pango @1.22.4_0 (active)
  pcre @7.6_0 (active)
  pcre @7.8_1 (active)
  perl5.8 @5.8.8_2 (active)
  perl5.8 @5.8.8_3+darwin_9 (active)
  pgAdmin3 @1.8.2_0 (active)
  pgAdmin3 @1.8.4_0 (active)
  php5 @5.2.6_1+apache2+macosx+mysql5 (active)
  php5 @5.2.8_0+apache2+macosx+mysql5 (active)
  phpmyadmin @2.11.4_0 (active)
  pkgconfig @0.23_0 (active)
  pkgconfig @0.23_1 (active)
  postgresql82 @8.2.6_0 (active)
  postgresql82 @8.2.11_0 (active)
  postgresql83 @8.3.0_1 (active)
  postgresql83 @8.3.5_0 (active)
  postgresql83-doc @8.3.0_0 (active)
  postgresql83-doc @8.3.5_0 (active)
  postgresql83-server @8.3.0_0 (active)
  postgresql83-server @8.3.5_0 (active)
  psutils @p17_0 (active)
  readline @5.2.007_0+darwin_9 (active)
  readline @5.2.012_1 (active)
  render @0.9_1 (active)
  render @0.9.2_0 (active)
  serf @0.2.0_0 (active)
  smpeg @0.4.4_6 (active)
  sqlite3 @3.5.6_0 (active)
  sqlite3 @3.6.6.2_0 (active)
  subversion @1.4.6_0 (active)
  subversion @1.5.4_0 (active)
  tiff @3.8.2_1+macosx (active)
  tiff @3.8.2_2+darwin_9+macosx (active)
  urw-fonts @1.0.7pre44_0 (active)
  wget @1.11_0 (active)
  wget @1.11.4_0 (active)
  wxWidgets @2.8.7_0 (active)
  wxWidgets @2.8.9_0 (active)
  Xft2 @2.1.12_0 (active)
  Xft2 @2.1.13_0 (active)
  xorg-renderproto @0.9.3_0 (active)
  xorg-util-macros @1.1.5_0 (active)
  xorg-util-macros @1.2.1_0 (active)
  xorg-xproto @7.0.11_1 (active)
  xorg-xproto @7.0.14_1 (active)
  xrender @0.9.0_2 (active)
  xrender @0.9.4_4+macosx (active)
  zlib @1.2.3_1 (active)
  zlib @1.2.3_2 (active)

Yesterday I tried to upgrade all outdated without checking  
dependencies (flag u).  It ran through but with many errors.  This is  
an example for the apache2, there are many others like this:

  Error: Deactivating apache2 @2.2.9_1 failed: Registry error: Please  
specify the name of the port.

Now I tried `sudo port -vun upgrade outdated` and got the same errors  
again (beside some apache make errors: there's missing uuid.h, but  
it's on the system).

> If not, it can probably be fixed with some forced uninstalling of  
> those, and
> reinstalling.

I tried that already but it doesn't work:

  $ sudo port -d uninstall ncursesw @5.6_1
  DEBUG: ncurses depends on this port
  --->  Unable to uninstall ncursesw 5.6_1, the following ports depend  
on it:
  --->  	ncurses
  DEBUG: Please uninstall the ports that depend on ncursesw first.
      while executing
  "portuninstall::uninstall $portname [composite_version $portversion  
[array get variations]] [array get options]"
  Error: port uninstall failed: Please uninstall the ports that depend  
on ncursesw first.

Could this be an issue of the migration process?  May be `rm -rf /opt`  
with a reinstallation of the macports would help? ;)

matt

P.S.: I have problems sending mails to the list.  It's very slow and  
most of my mails don't go though (msg 1 day later: connected but  
greeting failed).  Is this a known problem?

-- 
rainboxx Matthias Dietrich
Freier Software Engineer

rainboxx                  |  Tel.: +49 (0) 151 / 50 60 78 64
T?lzer Str. 19            |  Mail: matt at rainboxx.de
70372 Stuttgart           |  WWW : http://www.rainboxx.de

XING: https://www.xing.com/profile/Matthias_Dietrich18
GULP: http://www.gulp.de/profil/rainboxx.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: Signierter Teil der Nachricht
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081221/2fb43dab/attachment.bin>

From blb at macports.org  Sun Dec 21 13:00:33 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 21 Dec 2008 14:00:33 -0700
Subject: MPlayer failing to install
In-Reply-To: <c115fd3c0812211052w68bd7e16w8a8f32308bb2936@mail.gmail.com>
References: <c115fd3c0812200836u152687b3o9b9edc748fa9a134@mail.gmail.com>
	<20081220205606.GC783@ninagal.withay.com>
	<c115fd3c0812211052w68bd7e16w8a8f32308bb2936@mail.gmail.com>
Message-ID: <20081221210032.GC749@ninagal.withay.com>

On Sun, Dec 21, 2008 at 01:52:56PM -0500, Tim Visher said:
> On Sat, Dec 20, 2008 at 3:56 PM, Bryan Blackburn <blb at macports.org> wrote:
> 
> > Does it show up with 'port installed giflib'?
> 
> Nope. It didn't.  Weird.
> 
> I went ahead and installed giflib manually and ran into another weird
> problem.  Apparently, gif2epsn, which giflib depends on, was already
> being used by another port, libungif.  I deactivated libungif, and
> then installed giflib with no problem.  Now, when I tried to activate
> libungif, it gets the same issue.  I activated with the `-f` flag and
> I got the following output.

So you already had libungif which should have supplied the library mplayer
was looking for, not sure why it wasn't.  Going forward, giflib is the
preferred port these days, so switching from libungif to giflib should
eventually happen anyway.

Though you shouldn't have both libungif and giflib active at the same time,
just use giflib and completely kill libungif, force uninstall it if
necessary.  Though since you did a force activate of libungif, you will
probably have to deactivate/reactivate giflib to get the files back.

Bryan

[...]
> -- 
> 
> In Christ,
> 
> Timmy V.
> 
> http://burningones.com/
> http://five.sentenc.es/ - Spend less time on e-mail

From blb at macports.org  Sun Dec 21 13:18:10 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 21 Dec 2008 14:18:10 -0700
Subject: Upgrading ncurses & ncursesw fails
In-Reply-To: <34235064-1927-4417-B3FA-53FFE167A497@rainboxx.de>
References: <D3CBF654-9544-4CF0-B109-D0042F37B57F@rainboxx.de>
	<20081220210355.GE783@ninagal.withay.com>
	<34235064-1927-4417-B3FA-53FFE167A497@rainboxx.de>
Message-ID: <20081221211810.GD749@ninagal.withay.com>

On Sun, Dec 21, 2008 at 05:17:17PM +0100, Matthias Dietrich said:
> Hi,
[...]
>> What were the exact commands you used to get to this point?
>
> the command was:
>  sudo port -f upgrade ncurses
>
> I used the f flag because there were errors without but I cannot  
> reproduce them now (the errors without the f flag).

Forcing on anything that can traverse multiple ports because of dependencies
(like install and upgrade) can have bad results, as I believe that force is
going to be propagated to everything port touches.  In the (hopefully) very
rare situtations where you truly need to force with upgrade/install, at
least use the -n as well so it doesn't do that traversal.

[...]
>> Are there any other ports which are like this?
>
> Phew!  There are plenty of ports installed twice!  Here is the list of  
> all currently installed ports:
[...lots of ports with multiple versions activated]

That definitely shouldn't be happening, only one should be active at a time;
it seems like something became really confused/corrupt in the MacPorts
database somehow.

[...]
> Could this be an issue of the migration process?  May be `rm -rf /opt`  
> with a reinstallation of the macports would help? ;)

Unfortunately, at this point, it may probably be less work for you to just
restart from scratch.  Otherwise it may involve doing lots of
deactivations, activations, following dependencies, etc, to try to get
things working on the current install again.

>
> matt
>
> P.S.: I have problems sending mails to the list.  It's very slow and most 
> of my mails don't go though (msg 1 day later: connected but greeting 
> failed).  Is this a known problem?

That's the first I've heard anything about email problems, is that 'greeting
failed' coming from your sending mail server trying to connect to one of the
apple.com servers?  If so and it keeps up, see

<http://www.macosforge.org/contact/>

Bryan


>
> -- 
> rainboxx Matthias Dietrich
> Freier Software Engineer
>
> rainboxx                  |  Tel.: +49 (0) 151 / 50 60 78 64
> T?lzer Str. 19            |  Mail: matt at rainboxx.de
> 70372 Stuttgart           |  WWW : http://www.rainboxx.de
>
> XING: https://www.xing.com/profile/Matthias_Dietrich18
> GULP: http://www.gulp.de/profil/rainboxx.html
>

From brad at pixilla.com  Sun Dec 21 13:27:44 2008
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Sun, 21 Dec 2008 13:27:44 -0800
Subject: port collections
Message-ID: <06566F0C-1BC1-4E2C-BE44-5BC565C8380C@pixilla.com>

Is there such a thing as a port collection?

Like port install-collection lamp or something that would install not- 
linux:)/apache/mysql/php/python/perl?

Bad example but just wondering.

Maybe a better one would be port install-collection pbx which could  
install a solid asterisk system.

I'm silly, I know.


//brad

From ryandesign at macports.org  Sun Dec 21 13:28:29 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 21 Dec 2008 15:28:29 -0600
Subject: configuring port
In-Reply-To: <6F6F958E-D9F8-4271-B180-A318F091A811@pixilla.com>
References: <620ABA27-1233-4A34-BA68-511BDC4E3689@pixilla.com>
	<BA3B3C12-8980-42E1-959B-A15A6E3B8BC2@geeklair.net>
	<6F6F958E-D9F8-4271-B180-A318F091A811@pixilla.com>
Message-ID: <D170D9FD-A580-4A89-8D07-3A537E3E14FF@macports.org>


On Dec 21, 2008, at 11:56, Bradley Giesbrecht wrote:

>> If you think your variants would be useful to more than just you,  
>> I'm sure we'd be glad to add them. Please file tickets with your  
>> proposed patches if so.
>
> Daniel, I see you are the macports maintainer for bind9 which I am  
> trying to create a variant for. I wouldn't call my work patch  
> quality yet.
>
> If I wanted to share what I have found with a maintainer and get  
> some feedback and learn enough about macports to be able to offer  
> quality patches is there an email list or forum target for this  
> type of discussion?

macports-dev is the preferred list for discussing the development of  
portfiles.



From matt at rainboxx.de  Sun Dec 21 13:10:42 2008
From: matt at rainboxx.de (Matthias Dietrich)
Date: Sun, 21 Dec 2008 22:10:42 +0100
Subject: Upgrading ncurses & ncursesw fails
In-Reply-To: <34235064-1927-4417-B3FA-53FFE167A497@rainboxx.de>
References: <D3CBF654-9544-4CF0-B109-D0042F37B57F@rainboxx.de>
	<20081220210355.GE783@ninagal.withay.com>
	<34235064-1927-4417-B3FA-53FFE167A497@rainboxx.de>
Message-ID: <B0239DF4-C077-45D4-A00C-C0B186AD932E@rainboxx.de>

Hi,

> I used the f flag because there were errors without but I cannot  
> reproduce them now (the errors without the f flag).

now I know why I used the f flag: I wanted to reinstall *every* port  
which is installed because there were problems with them (gues the  
migration was a fault).  Now I get an error using perl with it's  
modules:

   Errno architecture (darwin-2level-9.6.0) does not match executable
   architecture (darwin-2level-9.2.0) at
   /opt/local/lib/perl5/5.8.8/darwin-2level/Errno.pm line 11.

I try upgrading it and it seems to work (with the f flag).

How can I delete the macport system and any installed modules and the  
"installed db" so I can reinstall it?  This really sucks...

matt

-- 
rainboxx Matthias Dietrich
Freier Software Engineer

rainboxx                  |  Tel.: +49 (0) 151 / 50 60 78 64
T?lzer Str. 19            |  Mail: matt at rainboxx.de
70372 Stuttgart           |  WWW : http://www.rainboxx.de

XING: https://www.xing.com/profile/Matthias_Dietrich18
GULP: http://www.gulp.de/profil/rainboxx.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: Signierter Teil der Nachricht
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081221/087d830b/attachment.bin>

From blb at macports.org  Sun Dec 21 13:41:03 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 21 Dec 2008 14:41:03 -0700
Subject: port collections
In-Reply-To: <06566F0C-1BC1-4E2C-BE44-5BC565C8380C@pixilla.com>
References: <06566F0C-1BC1-4E2C-BE44-5BC565C8380C@pixilla.com>
Message-ID: <20081221214103.GE749@ninagal.withay.com>

On Sun, Dec 21, 2008 at 01:27:44PM -0800, Bradley Giesbrecht said:
> Is there such a thing as a port collection?
>
> Like port install-collection lamp or something that would install not- 
> linux:)/apache/mysql/php/python/perl?
>
> Bad example but just wondering.

There are a couple, gnome [1] and gimp [2] that I know of.  The problem with
this in some situations is dealing with variants, as depending on ports
currently doesn't handle variants [3].  So for something like MAMP, where
you'll probably want mysql5 with the +server variant, and possibly quite a
few variants with php5, it can't be done.

Bryan

[1] - <http://trac.macports.org/browser/trunk/dports/gnome/gnome/Portfile>
[2] - <http://trac.macports.org/browser/trunk/dports/graphics/gimp/Portfile>
[3] - <http://trac.macports.org/ticket/126>


>
> Maybe a better one would be port install-collection pbx which could  
> install a solid asterisk system.
>
> I'm silly, I know.
>
>
> //brad

From ryandesign at macports.org  Sun Dec 21 14:20:07 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 21 Dec 2008 16:20:07 -0600
Subject: Upgrading ncurses & ncursesw fails
In-Reply-To: <B0239DF4-C077-45D4-A00C-C0B186AD932E@rainboxx.de>
References: <D3CBF654-9544-4CF0-B109-D0042F37B57F@rainboxx.de>
	<20081220210355.GE783@ninagal.withay.com>
	<34235064-1927-4417-B3FA-53FFE167A497@rainboxx.de>
	<B0239DF4-C077-45D4-A00C-C0B186AD932E@rainboxx.de>
Message-ID: <E1FDEA5C-FAB3-4019-A73C-616B529939E0@macports.org>

On Dec 21, 2008, at 15:10, Matthias Dietrich wrote:

>> I used the f flag because there were errors without but I cannot  
>> reproduce them now (the errors without the f flag).
>
> now I know why I used the f flag: I wanted to reinstall *every*  
> port which is installed because there were problems with them (gues  
> the migration was a fault).

How did you do the migration?


> Now I get an error using perl with it's modules:
>
>   Errno architecture (darwin-2level-9.6.0) does not match executable
>   architecture (darwin-2level-9.2.0) at
>   /opt/local/lib/perl5/5.8.8/darwin-2level/Errno.pm line 11.

Sounds like one bit was built with Mac OS X 10.5.2 and another bit  
was built with Mac OS X 10.5.6 and these bits for some reason care  
about that minute difference. I think that must be unique to perl  
ports; usually it shouldn't matter, as long as everything is built on  
the same major version of Mac OS X (e.g. 10.5.x).


> I try upgrading it and it seems to work (with the f flag).

So the bit that had been built on 10.5.2 was now rebuilt on 10.5.6  
fixing the complaint.


> How can I delete the macport system and any installed modules and  
> the "installed db" so I can reinstall it?  This really sucks...

Uninstall instructions are here:

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



From vr8ce at yahoo.com  Sun Dec 21 15:03:31 2008
From: vr8ce at yahoo.com (Vince Rice)
Date: Sun, 21 Dec 2008 15:03:31 -0800 (PST)
Subject: Permissions problem
Message-ID: <846808.23065.qm@web65716.mail.ac4.yahoo.com>

> uname
Darwin SRSMBPRO.local 9.5.2 Darwin Kernel Version 9.5.2: Thu Oct  2 14:51:59 PDT 2008; root:xnu-1228.8.59~2/RELEASE_I386 i386

> sw_vers
ProductName:Mac OS X
ProductVersion:10.5.5
BuildVersion:9F2533


> port -v
MacPorts 1.700

Xcode is 3.1.2 from the Xcode/About menu.

All steps below performed from an Administrator login.

I installed port itself by downloading the .dmg and running the Installer. That created the /opt/local/* directories and added them to my path, etc. I then ran
port -v selfupdate
without incident, i.e. no errors and it said it had nothing to update.

However, trying to subsequently install any package is giving me permission denied messages on /opt/local/var/macports/build. The exact error message is:
Error: Unable to execute port: can't create directory "/opt/local/var/macports/build": permission denied

A quick ls of the /opt/local/var/macports directory shows:
drwxr-xr-x   8 root  admin  - 272 Dec 21 16:41 macports/

So, it's owned by root, and none but root has write access to it. Is this normal? Is there something else the Installer should have done to allow write access? Are the directories supposed to be owned by root? Are they supposed to have write access? What went wrong, and what do I need to do to fix it?

I checked the FAQ and didn't see anything related to this.

Thanks!


      

From ryandesign at macports.org  Sun Dec 21 15:07:01 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 21 Dec 2008 17:07:01 -0600
Subject: Permissions problem
In-Reply-To: <846808.23065.qm@web65716.mail.ac4.yahoo.com>
References: <846808.23065.qm@web65716.mail.ac4.yahoo.com>
Message-ID: <AB865CA5-B6F3-4E8D-8408-3464BFE1305C@macports.org>

On Dec 21, 2008, at 17:03, Vince Rice wrote:

>> uname
> Darwin SRSMBPRO.local 9.5.2 Darwin Kernel Version 9.5.2: Thu Oct  2  
> 14:51:59 PDT 2008; root:xnu-1228.8.59~2/RELEASE_I386 i386
>
>> sw_vers
> ProductName:Mac OS X
> ProductVersion:10.5.5
> BuildVersion:9F2533
>
>
>> port -v
> MacPorts 1.700
>
> Xcode is 3.1.2 from the Xcode/About menu.
>
> All steps below performed from an Administrator login.
>
> I installed port itself by downloading the .dmg and running the  
> Installer. That created the /opt/local/* directories and added them  
> to my path, etc. I then ran
> port -v selfupdate
> without incident, i.e. no errors and it said it had nothing to update.
>
> However, trying to subsequently install any package is giving me  
> permission denied messages on /opt/local/var/macports/build. The  
> exact error message is:
> Error: Unable to execute port: can't create directory "/opt/local/ 
> var/macports/build": permission denied
>
> A quick ls of the /opt/local/var/macports directory shows:
> drwxr-xr-x   8 root  admin  - 272 Dec 21 16:41 macports/
>
> So, it's owned by root, and none but root has write access to it.  
> Is this normal? Is there something else the Installer should have  
> done to allow write access? Are the directories supposed to be  
> owned by root? Are they supposed to have write access? What went  
> wrong, and what do I need to do to fix it?
>
> I checked the FAQ and didn't see anything related to this.

It's normal that everything is owned by root. You would use "sudo"  
before any port command which modifies things, such as sync,  
selfupdate, upgrade, install, etc.



From vr8ce at yahoo.com  Sun Dec 21 15:16:22 2008
From: vr8ce at yahoo.com (Vince Rice)
Date: Sun, 21 Dec 2008 15:16:22 -0800 (PST)
Subject: Permissions problem
References: <846808.23065.qm@web65716.mail.ac4.yahoo.com>
	<AB865CA5-B6F3-4E8D-8408-3464BFE1305C@macports.org>
Message-ID: <664120.33688.qm@web65705.mail.ac4.yahoo.com>

----- Original Message ----
From: Ryan Schmidt <ryandesign at macports.org>
To: Vince Rice <vr8ce at yahoo.com>
Cc: macports-users at lists.macosforge.org
Sent: Sunday, December 21, 2008 5:07:01 PM
Subject: Re: Permissions problem

> It's normal that everything is owned by root. You would use "sudo" before any port command 
> which modifies things, such as sync, selfupdate, upgrade, install, etc.

Wow, that was fast!

OK, I see that now. I did look in the docs before, but the examples I saw were for non-modification items, i.e. list, etc., and there was no sudo on the line. I took that to mean I didn't need it. Going back and looking, I see that it's on the install and other modifying lines.

Sorry for the noise, and thanks very much for the insanely quick response!



      

From ryandesign at macports.org  Sun Dec 21 15:36:34 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 21 Dec 2008 17:36:34 -0600
Subject: Permissions problem
In-Reply-To: <664120.33688.qm@web65705.mail.ac4.yahoo.com>
References: <846808.23065.qm@web65716.mail.ac4.yahoo.com>
	<AB865CA5-B6F3-4E8D-8408-3464BFE1305C@macports.org>
	<664120.33688.qm@web65705.mail.ac4.yahoo.com>
Message-ID: <39058445-E602-47E3-A462-45B6E9D4457E@macports.org>

On Dec 21, 2008, at 17:16, Vince Rice wrote:

>> It's normal that everything is owned by root. You would use "sudo"  
>> before any port command
>> which modifies things, such as sync, selfupdate, upgrade, install,  
>> etc.
>
> Wow, that was fast!
>
> OK, I see that now. I did look in the docs before, but the examples  
> I saw were for non-modification items, i.e. list, etc., and there  
> was no sudo on the line. I took that to mean I didn't need it.  
> Going back and looking, I see that it's on the install and other  
> modifying lines.
>
> Sorry for the noise, and thanks very much for the insanely quick  
> response!

You're welcome :)

Most ports don't actually need to be installed as root (though the  
way MacPorts is set up on the .dmg installer package, they always  
are). You can, if you prefer, install MacPorts manually by building  
from source, and specify the --with-install-user and --with-install- 
group configure parameters to use a different user. I do this on my  
own installation. Occasionally a port will fail with a permissions  
error; in that case, you can issue your port install command again  
with sudo to fix it.

There was also a Google Summer of Code project this year to make  
MacPorts only use root when necessary:

http://trac.macports.org/wiki/gsoc08-privileges

I don't think we've released that yet though.


From LenoreHorner at sbcglobal.net  Mon Dec 22 16:00:51 2008
From: LenoreHorner at sbcglobal.net (Lenore Horner)
Date: Mon, 22 Dec 2008 18:00:51 -0600
Subject: smaller version of Gnucash
Message-ID: <04144F5A-3362-4E13-B097-81231AA0DDD1@sbcglobal.net>

I made this mistake today of upgrading Gnucash from 2.2.5 to 2.2.7  
without using any variants.  So far it's taken 6 hours  and it's not  
done yet.  Plus I have to go back and deal with a couple of errors.   
(most

I'm pretty sure the only thing I'm using Macports for is to install  
Gnucash.  Everything else I can find binaries for which is much, much  
faster!  What I'm wondering is how much extra stuff I'm installing  
because I didn't think to do +without_quotes +without_hbci  
+without_ofx.  How am I supposed to know based on port info (A) what  
the variants do and (B) how much extra time putting them in will cost  
me?

I'm also curious, though at this point it would I think be a waste of  
time, whether I could
sudo port deactivate all
sudo port install gnucash +without_quotes +without_hbci +without_ofx
sudo port uninstall inactive

and have the lighter version in place without recompiling everything  
and also see how much extra work I've had to wait for my computer to do.

Wasn't there a +without_docs variant?  Is this gone because docs don't  
work so they aren't being installed anyhow?

Thanks,
Lenore

MacPorts 1.7.0
PowerBook G4
10.5.6
XCode 3.1 
  

From tim.visher at gmail.com  Mon Dec 22 19:19:27 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Mon, 22 Dec 2008 22:19:27 -0500
Subject: Strange MPlayer error after successful install
Message-ID: <c115fd3c0812221919k665fd0d2pdd69a3bc7a5b2f09@mail.gmail.com>

Hello Everyone,

I've had a successful run of installing mplayer and now I'm getting a
strange error when attempting to use it.

     dyld: Library not loaded: bin/libsmbclient.dylib.0
       Referenced from: /opt/local/bin/mplayer
       Reason: image not found
       Trace/BPT trap

Thoughts?

-- 

In Christ,

Timmy V.

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

From ryandesign at macports.org  Tue Dec 23 00:16:23 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 23 Dec 2008 02:16:23 -0600
Subject: smaller version of Gnucash
In-Reply-To: <04144F5A-3362-4E13-B097-81231AA0DDD1@sbcglobal.net>
References: <04144F5A-3362-4E13-B097-81231AA0DDD1@sbcglobal.net>
Message-ID: <A8F2FFB0-8521-4DA6-977F-A5E694802068@macports.org>

On Dec 22, 2008, at 18:00, Lenore Horner wrote:

> I made this mistake today of upgrading Gnucash from 2.2.5 to 2.2.7  
> without using any variants.  So far it's taken 6 hours  and it's  
> not done yet.  Plus I have to go back and deal with a couple of  
> errors.  (most
>
> I'm pretty sure the only thing I'm using Macports for is to install  
> Gnucash.  Everything else I can find binaries for which is much,  
> much faster!  What I'm wondering is how much extra stuff I'm  
> installing because I didn't think to do +without_quotes  
> +without_hbci +without_ofx.  How am I supposed to know based on  
> port info (A) what the variants do and (B) how much extra time  
> putting them in will cost me?

Hi Lenore.

Via "port info gnucash", all you'll learn is the names of the  
variants. If those aren't clear enough to tell you what they're for,  
use "port variants gnucash" to read the variant descriptions. If the  
descriptions aren't clear enough (or are absent), you can read the  
portfile with "port cat gnucash" or (if your EDITOR environment  
variable is set suitably) with "port edit gnucash" to see what it  
does. For many ports you could also ask the maintainer, but gnucash  
has none. You could look through the commit messages for gnucash and  
see if they explain anything:

http://trac.macports.org/log/trunk/dports/gnome/gnucash

As to how much time it will cost to install a port, MacPorts doesn't  
tell you that. The download time for the distfile varies based on  
your network, and the compile time varies based on the speed of your  
computer's processor and hard drive and how much memory it has.  
Variants may bring in dependencies, and those dependencies may bring  
in other dependencies, and so on, and there isn't a MacPorts command  
that will tell you all of that at once. You can piece it together  
manually, for example:

$ port deps gnucash
gnucash has build dependencies on:
         libtool
gnucash has library dependencies on:
         p5-xml-parser
         glib2
         gconf
         guile16
         slib
         slib-guile16
         popt
         libgnomeui
         libgnomeprintui
         libgtkhtml3
         libgsf
         goffice
         aqbanking
         libofx
         p5-finance-quote
gnucash has runtime dependencies on:
         evince

$ port deps gnucash +without_hbci
gnucash has build dependencies on:
         libtool
gnucash has library dependencies on:
         p5-xml-parser
         glib2
         gconf
         guile16
         slib
         slib-guile16
         popt
         libgnomeui
         libgnomeprintui
         libgtkhtml3
         libgsf
         goffice
         libofx
         p5-finance-quote
gnucash has runtime dependencies on:
         evince

So we see that if we add the +without_hbci variant, it causes the  
aqbanking library dependency to be deleted. We can see the same thing  
by reading the gnucash Portfile, which says, in part:

variant without_hbci description {Disables HBCI support} {
     depends_lib-delete  port:aqbanking
     configure.args-delete   --enable-hbci
     configure.args-append   --disable-hbci
}

Then we could ask what the dependencies of aqbanking are:

$ port deps aqbanking
aqbanking has build dependencies on:
         libtool
aqbanking has library dependencies on:
         gwenhywfar
         qt3
         ktoblzcheck
         libglade2
         libofx
         gmp

libtool and libofx are already needed by gnucash itself, but  
gwenhywfar, qt3, ktoblzcheck, libglade2 and gmp are new dependencies.  
Then we could ask what the dependencies of each of those are. You get  
the idea.

I wrote a PHP web page to create a graph of a port's dependencies  
which I find useful for researching these kinds of things. Here are  
the dependencies of aqbanking and libofx graphed:

http://ryandesign.com/tmp/aqbanking.png

http://ryandesign.com/tmp/libofx.png

Filled ovals represent ports I already have installed on my system;  
hollow ones are not installed. This would obviously vary on your  
system if you ran the script there. The different line styles are not  
terribly important to pay attention to: Solid lines are library  
dependencies, dotted lines are build dependencies, and dashed lines  
are runtime dependencies. The script does not take into account that  
some dependencies can be satisfied by other than the specified port  
(so, not all the ports shown will necessarily end up being installed).


> I'm also curious, though at this point it would I think be a waste  
> of time, whether I could
> sudo port deactivate all
> sudo port install gnucash +without_quotes +without_hbci +without_ofx
> sudo port uninstall inactive
>
> and have the lighter version in place without recompiling  
> everything and also see how much extra work I've had to wait for my  
> computer to do.

Good idea! With MacPorts 1.7.0 I think this should work correctly.


> Wasn't there a +without_docs variant?  Is this gone because docs  
> don't work so they aren't being installed anyhow?

I see the +without_docs variant was removed here:

http://trac.macports.org/changeset/35197

The reason given for its removal ("Remove variant without-docs. No  
hyphen allowed.") does not seem to match since the variant name  
didn't have a hyphen but an underscore (which is legal). In any case,  
the documentation is in a separate port, gnucash-docs, so if you want  
the docs, you install that port; if you don't, you don't.



From ryandesign at macports.org  Tue Dec 23 00:51:57 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 23 Dec 2008 02:51:57 -0600
Subject: Strange MPlayer error after successful install
In-Reply-To: <c115fd3c0812221919k665fd0d2pdd69a3bc7a5b2f09@mail.gmail.com>
References: <c115fd3c0812221919k665fd0d2pdd69a3bc7a5b2f09@mail.gmail.com>
Message-ID: <829729D0-835F-449D-8750-356B006DEC71@macports.org>


On Dec 22, 2008, at 21:19, Tim Visher wrote:

> I've had a successful run of installing mplayer and now I'm getting a
> strange error when attempting to use it.
>
>      dyld: Library not loaded: bin/libsmbclient.dylib.0
>        Referenced from: /opt/local/bin/mplayer
>        Reason: image not found
>        Trace/BPT trap
>
> Thoughts?

I don't see that message on my system, but there are several  
interesting things about it: 1) it has a relative path for the  
library it can't find; usually they're absolute paths; 2) the library  
is being looked for in bin; libraries virtually always live in lib;  
3) the library version is after .dylib, which is like on other  
operating systems where the version comes after .so, but on Darwin,  
the version is supposed to come before .dylib, e.g. libsmbclient. 
0.dylib.

Do have a file somewhere on your hard drive whose name starts with  
"libsmbclient"? If so where is it, and if it's in the MacPorts  
prefix, what port installed it?


From blb at macports.org  Tue Dec 23 01:07:52 2008
From: blb at macports.org (Bryan Blackburn)
Date: Tue, 23 Dec 2008 02:07:52 -0700
Subject: Strange MPlayer error after successful install
In-Reply-To: <829729D0-835F-449D-8750-356B006DEC71@macports.org>
References: <c115fd3c0812221919k665fd0d2pdd69a3bc7a5b2f09@mail.gmail.com>
	<829729D0-835F-449D-8750-356B006DEC71@macports.org>
Message-ID: <20081223090752.GF744@ninagal.withay.com>

On Tue, Dec 23, 2008 at 02:51:57AM -0600, Ryan Schmidt said:
>
> On Dec 22, 2008, at 21:19, Tim Visher wrote:
>
>> I've had a successful run of installing mplayer and now I'm getting a
>> strange error when attempting to use it.
>>
>>      dyld: Library not loaded: bin/libsmbclient.dylib.0
>>        Referenced from: /opt/local/bin/mplayer
>>        Reason: image not found
>>        Trace/BPT trap
>>
>> Thoughts?
>
> I don't see that message on my system, but there are several interesting 
> things about it: 1) it has a relative path for the library it can't find; 
> usually they're absolute paths; 2) the library is being looked for in bin; 
> libraries virtually always live in lib; 3) the library version is after 
> .dylib, which is like on other operating systems where the version comes 
> after .so, but on Darwin, the version is supposed to come before .dylib, 
> e.g. libsmbclient.0.dylib.
>
> Do have a file somewhere on your hard drive whose name starts with  
> "libsmbclient"? If so where is it, and if it's in the MacPorts prefix, 
> what port installed it?

Probably samba3:

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

Bryan


From kngspook at gmail.com  Tue Dec 23 01:12:31 2008
From: kngspook at gmail.com (Neil)
Date: Tue, 23 Dec 2008 01:12:31 -0800
Subject: smaller version of Gnucash
In-Reply-To: <A8F2FFB0-8521-4DA6-977F-A5E694802068@macports.org>
References: <04144F5A-3362-4E13-B097-81231AA0DDD1@sbcglobal.net>
	<A8F2FFB0-8521-4DA6-977F-A5E694802068@macports.org>
Message-ID: <77e4079b0812230112i7a1cf065y6747b7e749d56624@mail.gmail.com>

On Tue, Dec 23, 2008 at 12:16 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Dec 22, 2008, at 18:00, Lenore Horner wrote:
> In any case, the documentation is
> in a separate port, gnucash-docs, so if you want the docs, you install that
> port; if you don't, you don't.
>

Why would you keep the docs separate from the app?
Seems like it would increase the risk of a mistake by both the user
and the maintainer...

From dave.evans55 at googlemail.com  Tue Dec 23 05:44:24 2008
From: dave.evans55 at googlemail.com (David Evans)
Date: Tue, 23 Dec 2008 13:44:24 +0000
Subject: gtk2 fails to build - libXdamage wrong version
Message-ID: <4950EB38.8030001@googlemail.com>

After gtk2 builds its objects, at the final link stage
I get this error:

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


libXdamage does exist but not this version.

After this error message is displayed there is one final error:

Warning: the following items did not execute (for gtk2): 
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


OSX 10.5.6
Xcode 3.1.2

From masschel at gmail.com  Tue Dec 23 05:49:02 2008
From: masschel at gmail.com (Bart Masschelein)
Date: Tue, 23 Dec 2008 14:49:02 +0100
Subject: How to keep source
In-Reply-To: <2501AB68-69A3-467A-B5C8-2B1509638FD4@geeklair.net>
References: <0DFC4DBE-A7AB-48E1-82C4-463C695F5985@gmail.com>
	<2501AB68-69A3-467A-B5C8-2B1509638FD4@geeklair.net>
Message-ID: <1AF84E7B-9530-42EE-A691-A9F4D05D446D@gmail.com>

>     portautoclean
>         Automatic cleaning of the build directory of a given port  
> after it
>         has been installed.
>         Default: yes
>
> So, if you really want the source (and objects) for ever port you  
> build to stay around unless you explicitly clean them, then you'll  
> want to set this to 'no'
>

Thanks a lot, that's what I needed, for the moment.

Bart


From raw915 at comcast.net  Tue Dec 23 06:25:48 2008
From: raw915 at comcast.net (Roger Wehage)
Date: Tue, 23 Dec 2008 08:25:48 -0600
Subject: Installing gcc version 4.3.2 on Mac OS X
Message-ID: <87FD96EF-49D5-424C-B90E-2A07F025D9C3@comcast.net>

Hi,

Is there an easy way to correct symbolic links to the executables in  
gcc version 4.3.2 on Mac OS X?

I successfully installed MacPorts 1.7.0 (Darwin Ports?) on my MacBook  
Pro 2.4 GHz Intel Core 2 Duo with version 10.5.6 OS. Then I  
miraculously installed gcc43 version 4.3.2 with no errors. I did this  
directly form MacPorts, not having a clue what I was doing. I tried to  
follow the instructions on http://gcc43.darwinports.com/, but I got  
lost in the chaff.

First, I didn't know what I was supposed to do with all that  
information above the solid line in http://gcc43.darwinports.com/, so  
I ignored it after reading through it. Then I went down to "Once  
Darwin Ports has been installed, in a terminal window and while  
online, type the following and hit return:"

My computer didn't have a /opt/local/bin/portslocation/dports/gcc43  
subdirectory, but I found my way to /opt/local/bin/ and did a "sudo  
port install gcc43" from there. All of the commands executed without  
error, and all of the gcc43 files were created in the /opt/local/bin/  
subdirectory.

I suspect my problem is related to not having started from an /opt/ 
local/bin/portslocation/dports/gcc43 subdirectory. Typing man gcc43,  
etc, gives no information, because gcc43 apparently doesn't exist.  
However, if I type man gcc-mp-4.3, etc., I do get the man pages for  
the corresponding executables, etc.

So, is there a command somewhere that will create the correct symbolic  
links to the appropriate executables, or do I have to do this myself?  
For example, in /usr/bin I find symbolic links such as "gcc ->  
gcc-4.0" and "g++ -> g++-4.0." I assume that I can delete these  
symbolic links and create new ones pointing to the corresponding gcc- 
mp-4.3 and g++-mp-4.3 executables. But I don't know what all symbolic  
links need to be changed.

And... I don't want to break something.

OSX 10.5.6
Xcode 3.1.2

Thank you,

Roger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081223/c113bfc7/attachment.html>

From devans at macports.org  Tue Dec 23 07:32:22 2008
From: devans at macports.org (David Evans)
Date: Tue, 23 Dec 2008 07:32:22 -0800
Subject: gtk2 fails to build - libXdamage wrong version
In-Reply-To: <4950EB38.8030001@googlemail.com>
References: <4950EB38.8030001@googlemail.com>
Message-ID: <49510486.5000807@macports.org>

David Evans wrote:
> After gtk2 builds its objects, at the final link stage
> I get this error:
>
> i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libXdamage.1.1.0.dylib: No
> such file or directory
>
>
> libXdamage does exist but not this version.
>
> After this error message is displayed there is one final error:
>
> Warning: the following items did not execute (for gtk2):
> 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
>
>
> OSX 10.5.6
> Xcode 3.1.2
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
David --

There's an open ticket on this

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

although the fix isn't completely clear (to me anyway) as yet.

The other Dave Evans



From LenoreHorner at sbcglobal.net  Tue Dec 23 06:02:12 2008
From: LenoreHorner at sbcglobal.net (Lenore Horner)
Date: Tue, 23 Dec 2008 08:02:12 -0600
Subject: smaller version of Gnucash
In-Reply-To: <A8F2FFB0-8521-4DA6-977F-A5E694802068@macports.org>
References: <04144F5A-3362-4E13-B097-81231AA0DDD1@sbcglobal.net>
	<A8F2FFB0-8521-4DA6-977F-A5E694802068@macports.org>
Message-ID: <9A6DEC7D-D0C6-482D-ABAF-93C4F91E7140@sbcglobal.net>

Hi Ryan,

Thanks for the very good description.

>
> $ port deps gnucash +without_hbci
This would not have occurred to me to try.  Thanks.

>
> libtool and libofx are already needed by gnucash itself, but  
> gwenhywfar, qt3, ktoblzcheck, libglade2 and gmp are new  
> dependencies. Then we could ask what the dependencies of each of  
> those are. You get the idea.
Hmmm.  The first thing that
sudo port install gnucash +without_hcbi +without_ofx +without_quotes
did was to install gmp.  It must be coming in somewhere else.

>
>
>> I'm also curious, though at this point it would I think be a waste  
>> of time, whether I could
>> sudo port deactivate all
>> sudo port install gnucash +without_quotes +without_hbci +without_ofx
>> sudo port uninstall inactive
>>
>> and have the lighter version in place without recompiling  
>> everything and also see how much extra work I've had to wait for my  
>> computer to do.
>
> Good idea! With MacPorts 1.7.0 I think this should work correctly.
I think there's a flaw in what I wrote above.  I should have put
sudo port deactivate installed
because "all" I think ended up with trying to deactivate ports that  
don't exist.

Lenore

From LenoreHorner at sbcglobal.net  Tue Dec 23 08:13:00 2008
From: LenoreHorner at sbcglobal.net (Lenore Horner)
Date: Tue, 23 Dec 2008 10:13:00 -0600
Subject: odd Gnucash dependencies
Message-ID: <ADA6CE25-2344-49D6-87C3-855EB4B2D4C2@sbcglobal.net>

Running
sudo port install gnucash +without_hbci +without_ofx +without_quotes

on a clean install of MacPorts 1.7.0 on a Powerbook G4 with OS X  
10.5.6 and XCode 3.1

seems to install multiple versions of docbook-xml (4.3, 4.1.2, 4.2,  
4.4, 4.5, and 5.0) as shown in the excerpts below. I notice that the  
successive versions are not saying they deactivated previous  
versions.  I haven't finished the installation yet, so I don't know if  
this is working or what ends up active, but it seems, naively, like  
very bizarre behavior.

Lenore

--->  Fetching docbook-xml-4.3
--->  Attempting to fetch docbook-xml-4.3.zip from http://www.oasis-open.org/docbook/xml/4.3/
--->  Verifying checksum(s) for docbook-xml-4.3
--->  Extracting docbook-xml-4.3
--->  Configuring docbook-xml-4.3
--->  Building docbook-xml-4.3
--->  Staging docbook-xml-4.3 into destroot
--->  Installing docbook-xml-4.3 @4.3_0
--->  Activating docbook-xml-4.3 @4.3_0
######################################################################
# As MacPorts does not currently have a post-deactivate hook,
# you will need to ensure that you manually remove the catalog
# entry for this port when you uninstall it.  To do so, run
# "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.3/ 
catalog.xml".
######################################################################
--->  Cleaning docbook-xml-4.3
--->  Fetching docbook-xsl
--->  Attempting to fetch docbook-xsl-1.74.0.tar.bz2 from http://downloads.sourceforge.net/docbook
--->  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 docbook-xml-4.1.2
--->  Attempting to fetch docbkx412.zip from http://distfiles.macports.org/docbook-xml-4.1.2
--->  Verifying checksum(s) for docbook-xml-4.1.2
--->  Extracting docbook-xml-4.1.2
--->  Configuring docbook-xml-4.1.2
--->  Building docbook-xml-4.1.2
--->  Staging docbook-xml-4.1.2 into destroot
--->  Installing docbook-xml-4.1.2 @4.1.2_1
--->  Activating docbook-xml-4.1.2 @4.1.2_1
######################################################################
# As MacPorts does not currently have a post-deactivate hook,
# you will need to ensure that you manually remove the catalog
# entry for this port when you uninstall it.  To do so, run
# "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.1.2/ 
catalog.xml".
######################################################################
--->  Cleaning docbook-xml-4.1.2
--->  Fetching docbook-xml-4.2
--->  Attempting to fetch docbook-xml-4.2.zip from http://www.oasis-open.org/docbook/xml/4.2/
--->  Verifying checksum(s) for docbook-xml-4.2
--->  Extracting docbook-xml-4.2
--->  Configuring docbook-xml-4.2
--->  Building docbook-xml-4.2
--->  Staging docbook-xml-4.2 into destroot
--->  Installing docbook-xml-4.2 @4.2_0
--->  Activating docbook-xml-4.2 @4.2_0
######################################################################
# As MacPorts does not currently have a post-deactivate hook,
# you will need to ensure that you manually remove the catalog
# entry for this port when you uninstall it.  To do so, run
# "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.2/ 
catalog.xml".
######################################################################
--->  Cleaning docbook-xml-4.2
--->  Fetching docbook-xml-4.4
--->  Attempting to fetch docbook-xml-4.4.zip from http://distfiles.macports.org/docbook-xml-4.4
--->  Verifying checksum(s) for docbook-xml-4.4
--->  Extracting docbook-xml-4.4
--->  Configuring docbook-xml-4.4
--->  Building docbook-xml-4.4
--->  Staging docbook-xml-4.4 into destroot
--->  Installing docbook-xml-4.4 @4.4_0
--->  Activating docbook-xml-4.4 @4.4_0
######################################################################
# As MacPorts does not currently have a post-deactivate hook,
# you will need to ensure that you manually remove the catalog
# entry for this port when you uninstall it.  To do so, run
# "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.4/ 
catalog.xml".
######################################################################
--->  Cleaning docbook-xml-4.4
--->  Fetching docbook-xml-4.5
--->  Attempting to fetch docbook-xml-4.5.zip from http://distfiles.macports.org/docbook-xml-4.5
--->  Verifying checksum(s) for docbook-xml-4.5
--->  Extracting docbook-xml-4.5
--->  Configuring docbook-xml-4.5
--->  Building docbook-xml-4.5
--->  Staging docbook-xml-4.5 into destroot
--->  Installing docbook-xml-4.5 @4.5_0
--->  Activating docbook-xml-4.5 @4.5_0
######################################################################
# As MacPorts does not currently have a post-deactivate hook,
# you will need to ensure that you manually remove the catalog
# entry for this port when you uninstall it.  To do so, run
# "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.5/ 
catalog.xml".
######################################################################
--->  Cleaning docbook-xml-4.5
--->  Fetching docbook-xml-5.0
--->  Attempting to fetch docbook-5.0.zip from http://distfiles.macports.org/docbook-xml-5.0
--->  Verifying checksum(s) for docbook-xml-5.0
--->  Extracting docbook-xml-5.0
--->  Configuring docbook-xml-5.0
--->  Building docbook-xml-5.0
--->  Staging docbook-xml-5.0 into destroot
--->  Installing docbook-xml-5.0 @5.0_0
--->  Activating docbook-xml-5.0 @5.0_0
--->  Cleaning docbook-xml-5.0
--->  Fetching docbook-xml
--->  Verifying checksum(s) for docbook-xml
--->  Extracting docbook-xml
--->  Configuring docbook-xml
--->  Building docbook-xml
--->  Staging docbook-xml into destroot
--->  Installing docbook-xml @5.0_0
--->  Activating docbook-xml @5.0_0




From lenorehorner at sbcglobal.net  Tue Dec 23 08:32:23 2008
From: lenorehorner at sbcglobal.net (Lenore Horner)
Date: Tue, 23 Dec 2008 10:32:23 -0600
Subject: more Gnucash questions
Message-ID: <7A7D37EA-696B-4622-B3E4-9029D6F6DF89@sbcglobal.net>

Is there something malformed about the following command?

$ sudo port install gnucash +without_hcbi +without_ofx +without_quotes

After I issued that command, the first item installed was gmp and now  
its installing libofx.

Thanks,
Lenore


From face at CentosPrime.COM  Tue Dec 23 10:14:37 2008
From: face at CentosPrime.COM (Chris Janton)
Date: Tue, 23 Dec 2008 11:14:37 -0700
Subject: New version of subversion and apache2 not indicated?
Message-ID: <D6DF3063-E9F9-4723-BB93-B4A19787BB7A@centosprime.com>

I may just be confused.

I'm running from trunk.

I did my typical svn update / build

I get the following results from my check for new versions of things.  
I expect to see subversion and apache2 (upgraded on a system running  
1.7, not from trunk)

mac 17 # port outdated
No installed ports are outdated.
mac 18 # port info subversion
subversion @1.5.5 (devel)
Variants:    bash_completion, darwin_7, mac_os_x_server_mod_dav_svn,  
mod_dav_svn, no_bdb, no_neon, tools, universal

Subversion is a version control system designed to be as similar to  
cvs(1) as possible, while fixing many outstanding problems with
cvs(1).
Homepage:    http://subversion.tigris.org/

Build Dependencies:   bzip2
Library Dependencies: expat, neon, apr, apr-util, db46, gettext,  
libiconv, serf, cyrus-sasl2
Platforms:            darwin
Maintainers:          dluke at geeklair.net
mac 19 # port installed | grep subversion
   subversion @1.5.4_0+bash_completion+mod_dav_svn+no_bdb+tools (active)

So, shouldn't I have a needed upgrade to subversion?

Same for apache2?

mac 20 # port installed | grep apache2
   apache2 @2.2.10_0+darwin_9 (active)
   php5 @5.2.8_0+apache2+macosx+mysql5+pear (active)
mac 21 # port info apache2
apache2 @2.2.11 (www)
Variants:    darwin, darwin_7, darwin_9, eventmpm, no_startupitem,  
openbsd, openldap, preforkmpm, universal, workermpm

Apache is an HTTP server designed as a plug-in replacement for the  
NCSA server version 1.3 (or 1.4). It fixes numerous bugs in the
NCSA server and includes many frequently requested new features, and  
has an API which allows it to be extended to meet users' needs
more easily.
Homepage:    http://httpd.apache.org/

Build Dependencies:   bzip2
Library Dependencies: apr, apr-util, expat, openssl, pcre
Platforms:            darwin, freebsd, openbsd
Maintainers:          imajes at macports.org

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



From dave.evans55 at googlemail.com  Tue Dec 23 10:44:59 2008
From: dave.evans55 at googlemail.com (David Evans)
Date: Tue, 23 Dec 2008 18:44:59 +0000
Subject: gtk2 fails to build - libXdamage wrong version
In-Reply-To: <49510486.5000807@macports.org>
References: <4950EB38.8030001@googlemail.com> <49510486.5000807@macports.org>
Message-ID: <495131AB.6080207@googlemail.com>

David Evans wrote:
> David Evans wrote:
>   
>> After gtk2 builds its objects, at the final link stage
>> I get this error:
>>
>> i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libXdamage.1.1.0.dylib: No
>> such file or directory
>>
>>
>> libXdamage does exist but not this version.
>>
>> After this error message is displayed there is one final error:
>>
>> Warning: the following items did not execute (for gtk2):
>> 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
>>
>>
>> OSX 10.5.6
>> Xcode 3.1.2
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>
>>     
> David --
>
> There's an open ticket on this
>
> http://trac.macports.org/ticket/17356
>
> although the fix isn't completely clear (to me anyway) as yet.
>
> The other Dave Evans
>
>   
I installed xorg-libXdamage and gtk2 now compiles and links.  Thanks for 
the pointer.

Macports moves in mysterious ways as the installation of xorg-libXdamage 
claimed at
the end that it was already installed.


From devans at macports.org  Tue Dec 23 11:02:55 2008
From: devans at macports.org (David Evans)
Date: Tue, 23 Dec 2008 11:02:55 -0800
Subject: gtk2 fails to build - libXdamage wrong version
In-Reply-To: <495131AB.6080207@googlemail.com>
References: <4950EB38.8030001@googlemail.com> <49510486.5000807@macports.org>
	<495131AB.6080207@googlemail.com>
Message-ID: <495135DF.8090809@macports.org>

David Evans wrote:
> I installed xorg-libXdamage and gtk2 now compiles and links.  Thanks
> for the pointer.
>
> Macports moves in mysterious ways as the installation of
> xorg-libXdamage claimed at
> the end that it was already installed.
>
By the time it gets to the end, it is! ;-)

I've wondered about this myself.  Glad you got it working.

From ryandesign at macports.org  Tue Dec 23 12:33:31 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 23 Dec 2008 14:33:31 -0600
Subject: odd Gnucash dependencies
In-Reply-To: <ADA6CE25-2344-49D6-87C3-855EB4B2D4C2@sbcglobal.net>
References: <ADA6CE25-2344-49D6-87C3-855EB4B2D4C2@sbcglobal.net>
Message-ID: <7E06F53A-DDE5-49BA-A653-2D13B6A04327@macports.org>


On Dec 23, 2008, at 10:13, Lenore Horner wrote:

> Running
> sudo port install gnucash +without_hbci +without_ofx +without_quotes
>
> on a clean install of MacPorts 1.7.0 on a Powerbook G4 with OS X  
> 10.5.6 and XCode 3.1
>
> seems to install multiple versions of docbook-xml (4.3, 4.1.2, 4.2,  
> 4.4, 4.5, and 5.0) as shown in the excerpts below. I notice that  
> the successive versions are not saying they deactivated previous  
> versions.  I haven't finished the installation yet, so I don't know  
> if this is working or what ends up active, but it seems, naively,  
> like very bizarre behavior.

I believe that's simply the way the docbook-xml ports are designed to  
work. I don't know why but perhaps Maun Suang or Anthony can explain  
why the ports are like that.


From ryandesign at macports.org  Tue Dec 23 12:35:21 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 23 Dec 2008 14:35:21 -0600
Subject: more Gnucash questions
In-Reply-To: <7A7D37EA-696B-4622-B3E4-9029D6F6DF89@sbcglobal.net>
References: <7A7D37EA-696B-4622-B3E4-9029D6F6DF89@sbcglobal.net>
Message-ID: <B7559CED-55B8-445E-B28B-E0AB666CD4FC@macports.org>


On Dec 23, 2008, at 10:32, Lenore Horner wrote:

> Is there something malformed about the following command?
>
> $ sudo port install gnucash +without_hcbi +without_ofx +without_quotes
>
> After I issued that command, the first item installed was gmp and  
> now its installing libofx.

It's +without_hbci (for "Home Banking Computer Interface"), not  
+without_hcbi. MacPorts doesn't issue a warning if you select a  
variant that does not exist...




From ryandesign at macports.org  Tue Dec 23 12:37:13 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 23 Dec 2008 14:37:13 -0600
Subject: New version of subversion and apache2 not indicated?
In-Reply-To: <D6DF3063-E9F9-4723-BB93-B4A19787BB7A@centosprime.com>
References: <D6DF3063-E9F9-4723-BB93-B4A19787BB7A@centosprime.com>
Message-ID: <3F47EB88-F165-4D7E-9548-04CFE2AB3790@macports.org>

On Dec 23, 2008, at 12:14, Chris Janton wrote:

> I may just be confused.
>
> I'm running from trunk.
>
> I did my typical svn update / build
>
> I get the following results from my check for new versions of  
> things. I expect to see subversion and apache2 (upgraded on a  
> system running 1.7, not from trunk)
>
> mac 17 # port outdated
> No installed ports are outdated.
> mac 18 # port info subversion
> subversion @1.5.5 (devel)
[snip]
> mac 19 # port installed | grep subversion
>   subversion @1.5.4_0+bash_completion+mod_dav_svn+no_bdb+tools  
> (active)
>
> So, shouldn't I have a needed upgrade to subversion?
>
> Same for apache2?
>
> mac 20 # port installed | grep apache2
>   apache2 @2.2.10_0+darwin_9 (active)
>   php5 @5.2.8_0+apache2+macosx+mysql5+pear (active)
> mac 21 # port info apache2
> apache2 @2.2.11 (www)
[snip]

The only reason I can think of why the ports would not be shown as  
outdated is if your PortIndex was not up to date. Try "port sync" one  
more time. subversion and apache2 did show as outdated for me recently.


From ryandesign at macports.org  Tue Dec 23 12:46:09 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 23 Dec 2008 14:46:09 -0600
Subject: Installing gcc version 4.3.2 on Mac OS X
In-Reply-To: <87FD96EF-49D5-424C-B90E-2A07F025D9C3@comcast.net>
References: <87FD96EF-49D5-424C-B90E-2A07F025D9C3@comcast.net>
Message-ID: <43040449-4324-4603-AC05-A31EDB2C7CA8@macports.org>


On Dec 23, 2008, at 08:25, Roger Wehage wrote:

> Is there an easy way to correct symbolic links to the executables  
> in gcc version 4.3.2 on Mac OS X?
>
> I successfully installed MacPorts 1.7.0 (Darwin Ports?)

Hi Roger. Welcome to MacPorts! The project used to be called  
DarwinPorts a long time ago but is now called MacPorts to emphasize  
that it's designed to be used with Mac OS X (and not so much the open- 
source Darwin OS).

> on my MacBook Pro 2.4 GHz Intel Core 2 Duo with version 10.5.6 OS.  
> Then I miraculously installed gcc43 version 4.3.2 with no errors. I  
> did this directly form MacPorts, not having a clue what I was  
> doing. I tried to follow the instructions on http:// 
> gcc43.darwinports.com/, but I got lost in the chaff.
>
> First, I didn't know what I was supposed to do with all that  
> information above the solid line in http://gcc43.darwinports.com/,  
> so I ignored it after reading through it. Then I went down to "Once  
> Darwin Ports has been installed, in a terminal window and while  
> online, type the following and hit return:"
>
> My computer didn't have a /opt/local/bin/portslocation/dports/gcc43  
> subdirectory, but I found my way to /opt/local/bin/ and did a "sudo  
> port install gcc43" from there. All of the commands executed  
> without error, and all of the gcc43 files were created in the /opt/ 
> local/bin/ subdirectory.
>
> I suspect my problem is related to not having started from an /opt/ 
> local/bin/portslocation/dports/gcc43 subdirectory. Typing man  
> gcc43, etc, gives no information, because gcc43 apparently doesn't  
> exist. However, if I type man gcc-mp-4.3, etc., I do get the man  
> pages for the corresponding executables, etc.

Please do not refer to that web site for any information about  
MacPorts. It is not affiliated with the MacPorts project and has  
inaccurate information. All information about MacPorts is at http:// 
www.macports.org/ . Specifically reading the Guide is probably  
helpful; see http://guide.macports.org/ . For more information about  
the rogue web site, you can read http://trac.macports.org/wiki/ 
DarwinPorts .


> So, is there a command somewhere that will create the correct  
> symbolic links to the appropriate executables, or do I have to do  
> this myself? For example, in /usr/bin I find symbolic links such as  
> "gcc -> gcc-4.0" and "g++ -> g++-4.0." I assume that I can delete  
> these symbolic links and create new ones pointing to the  
> corresponding gcc-mp-4.3 and g++-mp-4.3 executables. But I don't  
> know what all symbolic links need to be changed.
>
> And... I don't want to break something.

Yes, you should not change the gcc symlinks in /usr/bin (or anything  
else in /usr/bin). MacPorts is designed to run separately from and  
not conflict with anything installed by Apple. You can type "port  
contents gcc43" to see what was installed and where. So, e.g., you  
can use the MacPorts gcc 4.3 by executing /opt/local/bin/gcc-mp-4.3.  
If you would like to be able to run it by just typing "gcc", you can  
install the port gcc_select ("sudo port install gcc_select"), then  
use the installed gcc_select to create those symlinks in /opt/local/ 
bin (type "gcc_select" to see its help message).




From jmr at macports.org  Tue Dec 23 13:04:55 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 24 Dec 2008 08:04:55 +1100
Subject: smaller version of Gnucash
In-Reply-To: <A8F2FFB0-8521-4DA6-977F-A5E694802068@macports.org>
References: <04144F5A-3362-4E13-B097-81231AA0DDD1@sbcglobal.net>
	<A8F2FFB0-8521-4DA6-977F-A5E694802068@macports.org>
Message-ID: <49515277.2000808@macports.org>

Ryan Schmidt wrote:
> I wrote a PHP web page to create a graph of a port's dependencies which
> I find useful for researching these kinds of things. Here are the
> dependencies of aqbanking and libofx graphed:
> 
> http://ryandesign.com/tmp/aqbanking.png
> 
> http://ryandesign.com/tmp/libofx.png
> 
> Filled ovals represent ports I already have installed on my system;
> hollow ones are not installed. This would obviously vary on your system
> if you ran the script there. The different line styles are not terribly
> important to pay attention to: Solid lines are library dependencies,
> dotted lines are build dependencies, and dashed lines are runtime
> dependencies. The script does not take into account that some
> dependencies can be satisfied by other than the specified port (so, not
> all the ports shown will necessarily end up being installed).

There's also the port-rdeps script:
<http://svn.macports.org/repository/macports/contrib/port-rdeps/port-rdeps>

- Josh

From ryandesign at macports.org  Tue Dec 23 13:08:12 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 23 Dec 2008 15:08:12 -0600
Subject: smaller version of Gnucash
In-Reply-To: <77e4079b0812230112i7a1cf065y6747b7e749d56624@mail.gmail.com>
References: <04144F5A-3362-4E13-B097-81231AA0DDD1@sbcglobal.net>
	<A8F2FFB0-8521-4DA6-977F-A5E694802068@macports.org>
	<77e4079b0812230112i7a1cf065y6747b7e749d56624@mail.gmail.com>
Message-ID: <0174671D-E001-4B05-BF2C-DAD4F0592E4A@macports.org>


On Dec 23, 2008, at 03:12, Neil wrote:

> On Tue, Dec 23, 2008 at 12:16 AM, Ryan Schmidt wrote:
>
>> In any case, the documentation is
>> in a separate port, gnucash-docs, so if you want the docs, you  
>> install that
>> port; if you don't, you don't.
>
> Why would you keep the docs separate from the app?
> Seems like it would increase the risk of a mistake by both the user
> and the maintainer...

What kind of mistake are you thinking of? I like the idea of having  
docs in a separate port a lot, if the docs are big -- better than  
having a +doc / +docs variant in the main port, for example, because  
if you "sudo port install something" and then later realize you  
needed the docs, it's more of a pain to "sudo port -f uninstall  
something && sudo port install something +docs" than it is to just  
"sudo port install something-docs". If the docs are small, though,  
then I'm in favor of the main port always installing them; see e.g.  
freetype where I recently nuked the +doc variant:

http://trac.macports.org/changeset/42509


From jmr at macports.org  Tue Dec 23 13:09:46 2008
From: jmr at macports.org (Joshua Root)
Date: Wed, 24 Dec 2008 08:09:46 +1100
Subject: gtk2 fails to build - libXdamage wrong version
In-Reply-To: <4950EB38.8030001@googlemail.com>
References: <4950EB38.8030001@googlemail.com>
Message-ID: <4951539A.3030706@macports.org>

David Evans wrote:
> After gtk2 builds its objects, at the final link stage
> I get this error:
> 
> i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libXdamage.1.1.0.dylib: No
> such file or directory

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

- Josh

From face at CentosPrime.COM  Tue Dec 23 13:12:28 2008
From: face at CentosPrime.COM (Chris Janton)
Date: Tue, 23 Dec 2008 14:12:28 -0700
Subject: New version of subversion and apache2 not indicated?
In-Reply-To: <3F47EB88-F165-4D7E-9548-04CFE2AB3790@macports.org>
References: <D6DF3063-E9F9-4723-BB93-B4A19787BB7A@centosprime.com>
	<3F47EB88-F165-4D7E-9548-04CFE2AB3790@macports.org>
Message-ID: <C01E0AAA-18C4-4A84-B082-985FB8343490@CentosPrime.COM>

On 2008-12-23 , at 13:37 , Ryan Schmidt wrote:

> The only reason I can think of why the ports would not be shown as  
> outdated is if your PortIndex was not up to date. Try "port sync"  
> one more time. subversion and apache2 did show as outdated for me  
> recently.


mac 3 # cd /opt/mports/trunk
mac 4 # svn update
svn: Failed to add directory 'dports/audio/mpeg4ip': an unversioned  
directory of the same name already exists
mac 5 # ls dports/audio/mpeg4ip
work@
mac 6 # rm -r dports/audio/mpeg4ip
mac 7 # svn update
A    dports/audio/mpeg4ip
...

finish the build...

port outdated shows all of the missing updates.

That was the ticket - thanks!

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



From ryandesign at macports.org  Tue Dec 23 13:13:57 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Tue, 23 Dec 2008 15:13:57 -0600
Subject: Strange MPlayer error after successful install
In-Reply-To: <20081223090752.GF744@ninagal.withay.com>
References: <c115fd3c0812221919k665fd0d2pdd69a3bc7a5b2f09@mail.gmail.com>
	<829729D0-835F-449D-8750-356B006DEC71@macports.org>
	<20081223090752.GF744@ninagal.withay.com>
Message-ID: <EDBC0AF2-674C-4332-84B3-E770DC3CC275@macports.org>

On Dec 23, 2008, at 03:07, Bryan Blackburn wrote:

> On Tue, Dec 23, 2008 at 02:51:57AM -0600, Ryan Schmidt said:
>
>> On Dec 22, 2008, at 21:19, Tim Visher wrote:
>>
>>> I've had a successful run of installing mplayer and now I'm  
>>> getting a
>>> strange error when attempting to use it.
>>>
>>>      dyld: Library not loaded: bin/libsmbclient.dylib.0
>>>        Referenced from: /opt/local/bin/mplayer
>>>        Reason: image not found
>>>        Trace/BPT trap
>>>
>>> Thoughts?
>>
>> I don't see that message on my system, but there are several  
>> interesting
>> things about it: 1) it has a relative path for the library it  
>> can't find;
>> usually they're absolute paths; 2) the library is being looked for  
>> in bin;
>> libraries virtually always live in lib; 3) the library version is  
>> after
>> .dylib, which is like on other operating systems where the version  
>> comes
>> after .so, but on Darwin, the version is supposed to come  
>> before .dylib,
>> e.g. libsmbclient.0.dylib.
>>
>> Do have a file somewhere on your hard drive whose name starts with
>> "libsmbclient"? If so where is it, and if it's in the MacPorts  
>> prefix,
>> what port installed it?
>
> Probably samba3:
>
> <http://trac.macports.org/ticket/16023>

Mhm... I see samba3 does install the weirdly-named ${prefix}/lib/ 
samba3/libsmbclient.dylib.0

I rebuilt MPlayer and it still doesn't seem to link with  
libsmbclient, based on the (lack of any) output from:

port contents MPlayer | sed 1d | xargs grep smbclient



From blb at macports.org  Tue Dec 23 14:36:26 2008
From: blb at macports.org (Bryan Blackburn)
Date: Tue, 23 Dec 2008 15:36:26 -0700
Subject: odd Gnucash dependencies
In-Reply-To: <7E06F53A-DDE5-49BA-A653-2D13B6A04327@macports.org>
References: <ADA6CE25-2344-49D6-87C3-855EB4B2D4C2@sbcglobal.net>
	<7E06F53A-DDE5-49BA-A653-2D13B6A04327@macports.org>
Message-ID: <20081223223626.GC592@ninagal.withay.com>

On Tue, Dec 23, 2008 at 02:33:31PM -0600, Ryan Schmidt said:
>
> On Dec 23, 2008, at 10:13, Lenore Horner wrote:
>
>> Running
>> sudo port install gnucash +without_hbci +without_ofx +without_quotes
>>
>> on a clean install of MacPorts 1.7.0 on a Powerbook G4 with OS X 10.5.6 
>> and XCode 3.1
>>
>> seems to install multiple versions of docbook-xml (4.3, 4.1.2, 4.2,  
>> 4.4, 4.5, and 5.0) as shown in the excerpts below. I notice that the 
>> successive versions are not saying they deactivated previous versions.  
>> I haven't finished the installation yet, so I don't know if this is 
>> working or what ends up active, but it seems, naively, like very bizarre 
>> behavior.
>
> I believe that's simply the way the docbook-xml ports are designed to  
> work. I don't know why but perhaps Maun Suang or Anthony can explain why 
> the ports are like that.

Yes, that's how it is supposed to work; note that it isn't installing
multiple versions of docbook-xml but a docbook-xml-4.1.2, docbook-xml-4.2,
etc.  Since different docbook sources use different versions of the DTDs,
each really needs to be installed to cover them all.  That's why the actual
docbook-xml port depends on all of the versioned ports.

Bryan


From jjstickel at vcn.com  Wed Dec 24 08:54:03 2008
From: jjstickel at vcn.com (Jonathan Stickel)
Date: Wed, 24 Dec 2008 09:54:03 -0700
Subject: xfe (fox) segmentation fault
Message-ID: <4952692B.6060507@vcn.com>

I would like to try the xfe file manager.  It installs fine (Tiger 
10.4.11), but then seg faults when I try to run it:

$ xfe
Segmentation fault

The problem seems to be with the fox library on which it is built; if I 
run a binary that is part of the fox build, I also get segmentation 
faults.  For example:

$ port contents fox | grep bin
   /opt/local/bin/adie
...

$ /opt/local/bin/adie
Segmentation fault

Does anyone else see this?  Should I file a bug report ticket?

Jonathan

From ryandesign at macports.org  Wed Dec 24 12:02:13 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 24 Dec 2008 14:02:13 -0600
Subject: xfe (fox) segmentation fault
In-Reply-To: <4952692B.6060507@vcn.com>
References: <4952692B.6060507@vcn.com>
Message-ID: <35FFACA7-3176-46AB-9830-8C4EEA90EE3D@macports.org>


On Dec 24, 2008, at 10:54, Jonathan Stickel wrote:

> I would like to try the xfe file manager.  It installs fine (Tiger  
> 10.4.11), but then seg faults when I try to run it:
>
> $ xfe
> Segmentation fault
>
> The problem seems to be with the fox library on which it is built;  
> if I run a binary that is part of the fox build, I also get  
> segmentation faults.  For example:
>
> $ port contents fox | grep bin
>   /opt/local/bin/adie
> ...
>
> $ /opt/local/bin/adie
> Segmentation fault
>
> Does anyone else see this?  Should I file a bug report ticket?

I don't get a segmentation fault on Tiger... When X11 is not running  
I get:

$ adie
Adie::openDisplay: unable to open display :0.0


And when X11 is running I get:

$ adie
_X11TransSocketUNIXConnect: Cannot connect to non-local  
host ????????????
XIO:  fatal IO error 22 (Unknown error: 0) on X server ":0.0"
       after 7 requests (6 known processed) with 0 events remaining.


Which is this ticket:

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



From ms at mac-specialist.com  Wed Dec 24 20:12:05 2008
From: ms at mac-specialist.com (Bill Hernandez)
Date: Wed, 24 Dec 2008 22:12:05 -0600
Subject: mod_authn_dbm.so and dbmmanage are not playing well together,
	causing [500] Internal Server Error
Message-ID: <CEF6A01C-88D5-4E7A-A327-F8AE12A3228C@mac-specialist.com>

Problem with mod_authn_dbm.so

I have been using the standard flat file created by htpasswd, but  
tried to switch to mod_authn_dbm.so , So I went to http://httpd.apache.org/docs/2.0/programs/dbmmanage.html 
  and followed the plan...

Using the dbmmanage that MacPorts installed with apache2, I created  
some user password records.

dbmmanage does not have a way to specify AuthDBMType, so I created the  
records and then tried to figure out what type of records dbmmanage  
was actually generating by trying the five AuthDBMType(s) below, but  
none of them worked.

-------------------------------------------------
The log showed after the last restart :
-------------------------------------------------
[Wed Dec 24 21:15:47 2008] [notice] Apache/2.2.9 (Unix) mod_ssl/2.2.9  
OpenSSL/0.9.7l DAV/2 PHP/5.2.6 configured -- resuming normal operations

/www/etc/dbmpasswd: unexpected file type or format

[Wed Dec 24 21:16:02 2008] [error] [client ::1] (120022)APR does not  
understand this error code: could not open dbm (type DB) auth file: / 
www/etc/dbmpasswd
-------------------------------------------------
The permissions are set the same as ones for the standard flat file.
-------------------------------------------------
Displaying the records at the terminal :
-------------------------------------------------
$ path="/www/etc/dbmpasswd" ; dbmmanage $path view
---> shows all the user password records

-------------------------------------------------
The virtual host file contains
-------------------------------------------------
<Directory /www/secure>
	AllowOverride None
	Order Allow,Deny
	Allow from 127.0.0.1
	Allow from localhost
	Satisfy All

	AuthType basic
	AuthName "private area"
	AuthBasicProvider dbm
	AuthDBMType default

	# I tried all five of the AuthDBMType(s) below
	# [500] INTERNAL SERVER ERROR

	# AuthDBMType default
	# AuthDBMType DB
	# AuthDBMType GDBM
	# AuthDBMType NDBM
	# AuthDBMType SDBM

	AuthDBMUserFile /www/etc/dbmpasswd
	Require valid-user
</Directory>

These are the modules that deal with auth that are installed

LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_anon_module modules/mod_authn_anon.so
LoadModule authn_dbd_module modules/mod_authn_dbd.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_owner_module modules/mod_authz_owner.so
# LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule auth_digest_module modules/mod_auth_digest.so

Any ideas what else to try ?

From kngspook at gmail.com  Thu Dec 25 02:30:33 2008
From: kngspook at gmail.com (Neil)
Date: Thu, 25 Dec 2008 02:30:33 -0800
Subject: Will ruby19 replace ruby?
Message-ID: <77e4079b0812250230n2f09367fk235f0ef98cdb82c@mail.gmail.com>

After ruby19 is stable, will it replace ruby?

From j.van_den_hoff at fzd.de  Thu Dec 25 02:48:46 2008
From: j.van_den_hoff at fzd.de (Joerg van den Hoff)
Date: Thu, 25 Dec 2008 11:48:46 +0100
Subject: unison outdated?
Message-ID: <20081225104846.GD4049@claude.fz-rossendorf.de>

hello,

currently `macports' provides `unison' version 2.57.2
while the recommendation of its principal author on the
unison help list is "use version 2.31 or higher" if someone
complains about unison being redicously slow in certain situations
(which it is...).

question: would it be possible to update the maports version, irrespective
of whether the version is declared officially stable -- it is not at the
moment despite b. pierce's recommendation to use it?

I'll simultaneously ask on the unison help list whether 2.31 can be moved
to stable. maybe it helps if the maintainer of the macports package would
do the same :-) ?

thanks,

joerg

From florian.ebeling at gmail.com  Thu Dec 25 02:59:08 2008
From: florian.ebeling at gmail.com (C. Florian Ebeling)
Date: Thu, 25 Dec 2008 11:59:08 +0100
Subject: Will ruby19 replace ruby?
In-Reply-To: <77e4079b0812250230n2f09367fk235f0ef98cdb82c@mail.gmail.com>
References: <77e4079b0812250230n2f09367fk235f0ef98cdb82c@mail.gmail.com>
Message-ID: <5cbbe4ae0812250259v47d5a655u7dab791f4eeeab0@mail.gmail.com>

On Thu, Dec 25, 2008 at 11:30 AM, Neil <kngspook at gmail.com> wrote:
> After ruby19 is stable, will it replace ruby?

since 1.9 has a slightly, but incompatibly changed syntax, I don't
think that would be a good idea. I find other dynamic languages
being present in parallel in several versions and though we do
the same with ruby. E.g we have php4/php5,
python{21,22,23,24,25,26,30}, perl{5,5.8,5.10},
so it seems reasonable to do the same with ruby.



-- 
Florian Ebeling
Twitter: febeling
florian.ebeling at gmail.com

From vincent-opdarw at vinc17.org  Thu Dec 25 03:14:31 2008
From: vincent-opdarw at vinc17.org (Vincent Lefevre)
Date: Thu, 25 Dec 2008 12:14:31 +0100
Subject: unison outdated?
In-Reply-To: <20081225104846.GD4049@claude.fz-rossendorf.de>
References: <20081225104846.GD4049@claude.fz-rossendorf.de>
Message-ID: <20081225111431.GL17090@prunille.vinc17.org>

On 2008-12-25 11:48:46 +0100, Joerg van den Hoff wrote:
> question: would it be possible to update the maports version,
> irrespective of whether the version is declared officially stable --
> it is not at the moment despite b. pierce's recommendation to use
> it?

Warning! New Unison versions sometimes break the protocol. In such
a case, a new port should be created so that one can have both ports
installed (and activated) at the same time. One should not assume
that all machines (not just those using MacPorts) have the latest
unstable version (and even the latest stable when it is recent).

-- 
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 brad at pixilla.com  Thu Dec 25 04:54:47 2008
From: brad at pixilla.com (Bradley Giesbrecht)
Date: Thu, 25 Dec 2008 04:54:47 -0800
Subject: configuring port [bind9]
In-Reply-To: <BA3B3C12-8980-42E1-959B-A15A6E3B8BC2@geeklair.net>
References: <620ABA27-1233-4A34-BA68-511BDC4E3689@pixilla.com>
	<BA3B3C12-8980-42E1-959B-A15A6E3B8BC2@geeklair.net>
Message-ID: <26D3675A-3D93-4815-A431-7F5241CCCF09@pixilla.com>

On Dec 19, 2008, at 7:24 AM, Daniel J. Luke wrote:
> On Dec 19, 2008, at 10:16 AM, Bradley Giesbrecht wrote:
>> Is there some reading that someone could point me to that could  
>> help me with downloading and reconfiguring a port from macports?
>
> The guide should help you out, especially:
>
> http://guide.macports.org/#development
>
>> I'm looking to take advantage of the macports patches and handling  
>> of dependies.
>
>
> If you think your variants would be useful to more than just you,  
> I'm sure we'd be glad to add them. Please file tickets with your  
> proposed patches if so.

I added a Portfile.bind9.diff patch to the ticket I opened at macports  
for a bind9 dlz-mysql variant.

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



Happy holidays.


//Brad

From jjstickel at vcn.com  Thu Dec 25 09:58:55 2008
From: jjstickel at vcn.com (Jonathan Stickel)
Date: Thu, 25 Dec 2008 10:58:55 -0700
Subject: xfe (fox) segmentation fault
In-Reply-To: <35FFACA7-3176-46AB-9830-8C4EEA90EE3D@macports.org>
References: <4952692B.6060507@vcn.com>
	<35FFACA7-3176-46AB-9830-8C4EEA90EE3D@macports.org>
Message-ID: <4953C9DF.7010807@vcn.com>

Ryan Schmidt wrote:
> 
> On Dec 24, 2008, at 10:54, Jonathan Stickel wrote:
> 
>> I would like to try the xfe file manager.  It installs fine (Tiger 
>> 10.4.11), but then seg faults when I try to run it:
>>
>> $ xfe
>> Segmentation fault
>>
>> The problem seems to be with the fox library on which it is built; if 
>> I run a binary that is part of the fox build, I also get segmentation 
>> faults.  For example:
>>
>> $ port contents fox | grep bin
>>   /opt/local/bin/adie
>> ...
>>
>> $ /opt/local/bin/adie
>> Segmentation fault
>>
>> Does anyone else see this?  Should I file a bug report ticket?
> 
> I don't get a segmentation fault on Tiger... When X11 is not running I get:
> 
> $ adie
> Adie::openDisplay: unable to open display :0.0
> 
> 
> And when X11 is running I get:
> 
> $ adie
> _X11TransSocketUNIXConnect: Cannot connect to non-local host ????????????
> XIO:  fatal IO error 22 (Unknown error: 0) on X server ":0.0"
>       after 7 requests (6 known processed) with 0 events remaining.
> 
> 
> Which is this ticket:
> 
> http://trac.macports.org/ticket/17558
> 

I am well aware of that bug.  It can be at least partially fixed for 
gtk2 by removing the libXfixes dependency from the portfile, as I report 
in the ticket.

Perhaps this bug with the fox library is related... How can we debug it?

Jonathan

From lists at sequestered.net  Thu Dec 25 12:34:17 2008
From: lists at sequestered.net (Corey Chandler)
Date: Thu, 25 Dec 2008 12:34:17 -0800
Subject: gtk2 failure
Message-ID: <4953EE49.8050804@sequestered.net>

Has anyone seen this before?  I'm about out of ideas... 10.5.6, macports 1.7

bash-3.2# port upgrade gtk2
--->  Fetching gtk2
--->  Verifying checksum(s) for gtk2
--->  Extracting gtk2
--->  Applying patches to gtk2
--->  Configuring gtk2
--->  Building gtk2
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_gtk2/work/gtk+-2.14.5" 
&& make all " returned error 2
Command output: libtool: compile:  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. 
-I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. -I../../gdk 
-I../../gdk -DG_DISABLE_CAST_CHECKS -D_REENTRANT 
-I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include 
-I/opt/local/include -I/opt/local/include/pango-1.0 
-I/opt/local/include/cairo -I/opt/local/include/pixman-1 
-I/opt/local/include/freetype2 -I/opt/local/include/libpng12 
-I/usr/X11/include -I/opt/local/include -no-cpp-precomp -DX_LOCALE 
-DG_DISABLE_SINGLE_INCLUDES -DATK_DISABLE_SINGLE_INCLUDES 
-DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES 
-I/opt/local/include -I/usr/X11/include -DGDK_PIXBUF_DISABLE_DEPRECATED 
-O2 -funroll-loops -fstrict-aliasing -Wall -MT gdkdnd-x11.lo -MD -MP -MF 
.deps/gdkdnd-x11.Tpo -c gdkdnd-x11.c  -fno-common -DPIC -o 
.libs/gdkdnd-x11.o
if /bin/sh ../../libtool --mode=compile /usr/bin/gcc-4.0 -DHAVE_CONFIG_H 
-I. -I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. 
-I../../gdk -I../../gdk -DG_DISABLE_CAST_CHECKS -D_REENTRANT 
-I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include 
-I/opt/local/include -I/opt/local/include/pango-1.0 
-I/opt/local/include/cairo -I/opt/local/include/pixman-1 
-I/opt/local/include/freetype2 -I/opt/local/include/libpng12 
-I/usr/X11/include      -I/opt/local/include -no-cpp-precomp -DX_LOCALE 
-DG_DISABLE_SINGLE_INCLUDES -DATK_DISABLE_SINGLE_INCLUDES 
-DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES 
-I/opt/local/include -I/usr/X11/include    
-DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops -fstrict-aliasing 
-Wall -MT gdkdrawable-x11.lo -MD -MP -MF ".deps/gdkdrawable-x11.Tpo" \
      -c -o gdkdrawable-x11.lo `test -f 'gdkdrawable-x11.c' || echo 
'./'`gdkdrawable-x11.c; \
    then mv -f ".deps/gdkdrawable-x11.Tpo" ".deps/gdkdrawable-x11.Plo"; \
    else rm -f ".deps/gdkdrawable-x11.Tpo"; exit 1; \
    fi
libtool: compile:  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I../.. 
-DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. -I../../gdk -I../../gdk 
-DG_DISABLE_CAST_CHECKS -D_REENTRANT -I/opt/local/include/glib-2.0 
-I/opt/local/lib/glib-2.0/include -I/opt/local/include 
-I/opt/local/include/pango-1.0 -I/opt/local/include/cairo 
-I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 
-I/opt/local/include/libpng12 -I/usr/X11/include -I/opt/local/include 
-no-cpp-precomp -DX_LOCALE -DG_DISABLE_SINGLE_INCLUDES 
-DATK_DISABLE_SINGLE_INCLUDES -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES 
-DGTK_DISABLE_SINGLE_INCLUDES -I/opt/local/include -I/usr/X11/include 
-DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops -fstrict-aliasing 
-Wall -MT gdkdrawable-x11.lo -MD -MP -MF .deps/gdkdrawable-x11.Tpo -c 
gdkdrawable-x11.c  -fno-common -DPIC -o .libs/gdkdrawable-x11.o
gdkdrawable-x11.c:1289: warning: 'get_shm_pixmap_for_image' defined but 
not used
if /bin/sh ../../libtool --mode=compile /usr/bin/gcc-4.0 -DHAVE_CONFIG_H 
-I. -I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. 
-I../../gdk -I../../gdk -DG_DISABLE_CAST_CHECKS -D_REENTRANT 
-I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include 
-I/opt/local/include -I/opt/local/include/pango-1.0 
-I/opt/local/include/cairo -I/opt/local/include/pixman-1 
-I/opt/local/include/freetype2 -I/opt/local/include/libpng12 
-I/usr/X11/include      -I/opt/local/include -no-cpp-precomp -DX_LOCALE 
-DG_DISABLE_SINGLE_INCLUDES -DATK_DISABLE_SINGLE_INCLUDES 
-DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES 
-I/opt/local/include -I/usr/X11/include    
-DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops -fstrict-aliasing 
-Wall -MT gdkevents-x11.lo -MD -MP -MF ".deps/gdkevents-x11.Tpo" \
      -c -o gdkevents-x11.lo `test -f 'gdkevents-x11.c' || echo 
'./'`gdkevents-x11.c; \
    then mv -f ".deps/gdkevents-x11.Tpo" ".deps/gdkevents-x11.Plo"; \
    else rm -f ".deps/gdkevents-x11.Tpo"; exit 1; \
    fi
libtool: compile:  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I../.. 
-DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. -I../../gdk -I../../gdk 
-DG_DISABLE_CAST_CHECKS -D_REENTRANT -I/opt/local/include/glib-2.0 
-I/opt/local/lib/glib-2.0/include -I/opt/local/include 
-I/opt/local/include/pango-1.0 -I/opt/local/include/cairo 
-I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 
-I/opt/local/include/libpng12 -I/usr/X11/include -I/opt/local/include 
-no-cpp-precomp -DX_LOCALE -DG_DISABLE_SINGLE_INCLUDES 
-DATK_DISABLE_SINGLE_INCLUDES -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES 
-DGTK_DISABLE_SINGLE_INCLUDES -I/opt/local/include -I/usr/X11/include 
-DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops -fstrict-aliasing 
-Wall -MT gdkevents-x11.lo -MD -MP -MF .deps/gdkevents-x11.Tpo -c 
gdkevents-x11.c  -fno-common -DPIC -o .libs/gdkevents-x11.o
gdkevents-x11.c: In function 'gdk_event_translate':
gdkevents-x11.c:2110: error: 'RRNotify' undeclared (first use in this 
function)
gdkevents-x11.c:2110: error: (Each undeclared identifier is reported 
only once
gdkevents-x11.c:2110: error: for each function it appears in.)
gdkevents-x11.c:2112: error: 'XRRNotifyEvent' undeclared (first use in 
this function)
gdkevents-x11.c:2112: error: 'notify' undeclared (first use in this 
function)
gdkevents-x11.c:2112: error: syntax error before ')' token
gdkevents-x11.c: In function 'gdk_x11_screen_get_window_manager_name':
gdkevents-x11.c:2721: warning: dereferencing type-punned pointer will 
break strict-aliasing rules
gdkevents-x11.c: In function 'gdk_x11_screen_supports_net_wm_hint':
gdkevents-x11.c:2821: warning: dereferencing type-punned pointer will 
break strict-aliasing rules
make[4]: *** [gdkevents-x11.lo] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Error: Unable to upgrade port: 1


From jeremyhu at macports.org  Thu Dec 25 12:39:34 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Thu, 25 Dec 2008 12:39:34 -0800
Subject: gtk2 failure
In-Reply-To: <4953EE49.8050804@sequestered.net>
References: <4953EE49.8050804@sequestered.net>
Message-ID: <63BD1264-7852-485F-A2BA-60E15923710A@macports.org>

It looks like you might not have the X11SDK installed or you didn't  
reinstall Xquartz after doing the OS Update.  Otherwise, just install  
xorg-randrproto...


On Dec 25, 2008, at 12:34, Corey Chandler wrote:

> Has anyone seen this before?  I'm about out of ideas... 10.5.6,  
> macports 1.7
>
> bash-3.2# port upgrade gtk2
> --->  Fetching gtk2
> --->  Verifying checksum(s) for gtk2
> --->  Extracting gtk2
> --->  Applying patches to gtk2
> --->  Configuring gtk2
> --->  Building gtk2
> 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_gtk2/work/gtk+-2.14.5" && make all "  
> returned error 2
> Command output: libtool: compile:  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H - 
> I. -I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. - 
> I../../gdk -I../../gdk -DG_DISABLE_CAST_CHECKS -D_REENTRANT -I/opt/ 
> local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/ 
> local/include -I/opt/local/include/pango-1.0 -I/opt/local/include/ 
> cairo -I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 - 
> I/opt/local/include/libpng12 -I/usr/X11/include -I/opt/local/include  
> -no-cpp-precomp -DX_LOCALE -DG_DISABLE_SINGLE_INCLUDES - 
> DATK_DISABLE_SINGLE_INCLUDES -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES - 
> DGTK_DISABLE_SINGLE_INCLUDES -I/opt/local/include -I/usr/X11/include  
> -DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops -fstrict-aliasing  
> -Wall -MT gdkdnd-x11.lo -MD -MP -MF .deps/gdkdnd-x11.Tpo -c gdkdnd- 
> x11.c  -fno-common -DPIC -o .libs/gdkdnd-x11.o
> if /bin/sh ../../libtool --mode=compile /usr/bin/gcc-4.0 - 
> DHAVE_CONFIG_H -I. -I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" - 
> DGDK_COMPILATION -I../.. -I../../gdk -I../../gdk - 
> DG_DISABLE_CAST_CHECKS -D_REENTRANT -I/opt/local/include/glib-2.0 -I/ 
> opt/local/lib/glib-2.0/include -I/opt/local/include -I/opt/local/ 
> include/pango-1.0 -I/opt/local/include/cairo -I/opt/local/include/ 
> pixman-1 -I/opt/local/include/freetype2 -I/opt/local/include/ 
> libpng12 -I/usr/X11/include      -I/opt/local/include -no-cpp- 
> precomp -DX_LOCALE -DG_DISABLE_SINGLE_INCLUDES - 
> DATK_DISABLE_SINGLE_INCLUDES -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES - 
> DGTK_DISABLE_SINGLE_INCLUDES -I/opt/local/include -I/usr/X11/ 
> include    -DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops - 
> fstrict-aliasing -Wall -MT gdkdrawable-x11.lo -MD -MP -MF ".deps/ 
> gdkdrawable-x11.Tpo" \
>     -c -o gdkdrawable-x11.lo `test -f 'gdkdrawable-x11.c' || echo  
> './'`gdkdrawable-x11.c; \
>   then mv -f ".deps/gdkdrawable-x11.Tpo" ".deps/gdkdrawable- 
> x11.Plo"; \
>   else rm -f ".deps/gdkdrawable-x11.Tpo"; exit 1; \
>   fi
> libtool: compile:  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I../.. - 
> DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. -I../../gdk -I../../ 
> gdk -DG_DISABLE_CAST_CHECKS -D_REENTRANT -I/opt/local/include/ 
> glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/ 
> opt/local/include/pango-1.0 -I/opt/local/include/cairo -I/opt/local/ 
> include/pixman-1 -I/opt/local/include/freetype2 -I/opt/local/include/ 
> libpng12 -I/usr/X11/include -I/opt/local/include -no-cpp-precomp - 
> DX_LOCALE -DG_DISABLE_SINGLE_INCLUDES -DATK_DISABLE_SINGLE_INCLUDES - 
> DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES -I/ 
> opt/local/include -I/usr/X11/include -DGDK_PIXBUF_DISABLE_DEPRECATED  
> -O2 -funroll-loops -fstrict-aliasing -Wall -MT gdkdrawable-x11.lo - 
> MD -MP -MF .deps/gdkdrawable-x11.Tpo -c gdkdrawable-x11.c  -fno- 
> common -DPIC -o .libs/gdkdrawable-x11.o
> gdkdrawable-x11.c:1289: warning: 'get_shm_pixmap_for_image' defined  
> but not used
> if /bin/sh ../../libtool --mode=compile /usr/bin/gcc-4.0 - 
> DHAVE_CONFIG_H -I. -I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" - 
> DGDK_COMPILATION -I../.. -I../../gdk -I../../gdk - 
> DG_DISABLE_CAST_CHECKS -D_REENTRANT -I/opt/local/include/glib-2.0 -I/ 
> opt/local/lib/glib-2.0/include -I/opt/local/include -I/opt/local/ 
> include/pango-1.0 -I/opt/local/include/cairo -I/opt/local/include/ 
> pixman-1 -I/opt/local/include/freetype2 -I/opt/local/include/ 
> libpng12 -I/usr/X11/include      -I/opt/local/include -no-cpp- 
> precomp -DX_LOCALE -DG_DISABLE_SINGLE_INCLUDES - 
> DATK_DISABLE_SINGLE_INCLUDES -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES - 
> DGTK_DISABLE_SINGLE_INCLUDES -I/opt/local/include -I/usr/X11/ 
> include    -DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops - 
> fstrict-aliasing -Wall -MT gdkevents-x11.lo -MD -MP -MF ".deps/ 
> gdkevents-x11.Tpo" \
>     -c -o gdkevents-x11.lo `test -f 'gdkevents-x11.c' || echo  
> './'`gdkevents-x11.c; \
>   then mv -f ".deps/gdkevents-x11.Tpo" ".deps/gdkevents-x11.Plo"; \
>   else rm -f ".deps/gdkevents-x11.Tpo"; exit 1; \
>   fi
> libtool: compile:  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I../.. - 
> DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. -I../../gdk -I../../ 
> gdk -DG_DISABLE_CAST_CHECKS -D_REENTRANT -I/opt/local/include/ 
> glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/ 
> opt/local/include/pango-1.0 -I/opt/local/include/cairo -I/opt/local/ 
> include/pixman-1 -I/opt/local/include/freetype2 -I/opt/local/include/ 
> libpng12 -I/usr/X11/include -I/opt/local/include -no-cpp-precomp - 
> DX_LOCALE -DG_DISABLE_SINGLE_INCLUDES -DATK_DISABLE_SINGLE_INCLUDES - 
> DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES -I/ 
> opt/local/include -I/usr/X11/include -DGDK_PIXBUF_DISABLE_DEPRECATED  
> -O2 -funroll-loops -fstrict-aliasing -Wall -MT gdkevents-x11.lo -MD - 
> MP -MF .deps/gdkevents-x11.Tpo -c gdkevents-x11.c  -fno-common -DPIC  
> -o .libs/gdkevents-x11.o
> gdkevents-x11.c: In function 'gdk_event_translate':
> gdkevents-x11.c:2110: error: 'RRNotify' undeclared (first use in  
> this function)
> gdkevents-x11.c:2110: error: (Each undeclared identifier is reported  
> only once
> gdkevents-x11.c:2110: error: for each function it appears in.)
> gdkevents-x11.c:2112: error: 'XRRNotifyEvent' undeclared (first use  
> in this function)
> gdkevents-x11.c:2112: error: 'notify' undeclared (first use in this  
> function)
> gdkevents-x11.c:2112: error: syntax error before ')' token
> gdkevents-x11.c: In function 'gdk_x11_screen_get_window_manager_name':
> gdkevents-x11.c:2721: warning: dereferencing type-punned pointer  
> will break strict-aliasing rules
> gdkevents-x11.c: In function 'gdk_x11_screen_supports_net_wm_hint':
> gdkevents-x11.c:2821: warning: dereferencing type-punned pointer  
> will break strict-aliasing rules
> make[4]: *** [gdkevents-x11.lo] Error 1
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> 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


From lists at sequestered.net  Thu Dec 25 13:06:05 2008
From: lists at sequestered.net (Corey Chandler)
Date: Thu, 25 Dec 2008 13:06:05 -0800
Subject: gtk2 failure [SOLVED]
In-Reply-To: <63BD1264-7852-485F-A2BA-60E15923710A@macports.org>
References: <4953EE49.8050804@sequestered.net>
	<63BD1264-7852-485F-A2BA-60E15923710A@macports.org>
Message-ID: <4953F5BD.8000707@sequestered.net>

Yeah, forgot to reinstall XQuartz. *sheepish grin*  My apologies for 
that--- it's working now.

Jeremy Huddleston wrote:
> It looks like you might not have the X11SDK installed or you didn't 
> reinstall Xquartz after doing the OS Update.  Otherwise, just install 
> xorg-randrproto...
>
>
> On Dec 25, 2008, at 12:34, Corey Chandler wrote:
>
>> Has anyone seen this before?  I'm about out of ideas... 10.5.6, 
>> macports 1.7
>>
>> bash-3.2# port upgrade gtk2
>> --->  Fetching gtk2
>> --->  Verifying checksum(s) for gtk2
>> --->  Extracting gtk2
>> --->  Applying patches to gtk2
>> --->  Configuring gtk2
>> --->  Building gtk2
>> 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_gtk2/work/gtk+-2.14.5" 
>> && make all " returned error 2
>> Command output: libtool: compile:  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H 
>> -I. -I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. 
>> -I../../gdk -I../../gdk -DG_DISABLE_CAST_CHECKS -D_REENTRANT 
>> -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include 
>> -I/opt/local/include -I/opt/local/include/pango-1.0 
>> -I/opt/local/include/cairo -I/opt/local/include/pixman-1 
>> -I/opt/local/include/freetype2 -I/opt/local/include/libpng12 
>> -I/usr/X11/include -I/opt/local/include -no-cpp-precomp -DX_LOCALE 
>> -DG_DISABLE_SINGLE_INCLUDES -DATK_DISABLE_SINGLE_INCLUDES 
>> -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES 
>> -I/opt/local/include -I/usr/X11/include 
>> -DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops -fstrict-aliasing 
>> -Wall -MT gdkdnd-x11.lo -MD -MP -MF .deps/gdkdnd-x11.Tpo -c 
>> gdkdnd-x11.c  -fno-common -DPIC -o .libs/gdkdnd-x11.o
>> if /bin/sh ../../libtool --mode=compile /usr/bin/gcc-4.0 
>> -DHAVE_CONFIG_H -I. -I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" 
>> -DGDK_COMPILATION -I../.. -I../../gdk -I../../gdk 
>> -DG_DISABLE_CAST_CHECKS -D_REENTRANT -I/opt/local/include/glib-2.0 
>> -I/opt/local/lib/glib-2.0/include -I/opt/local/include 
>> -I/opt/local/include/pango-1.0 -I/opt/local/include/cairo 
>> -I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 
>> -I/opt/local/include/libpng12 -I/usr/X11/include      
>> -I/opt/local/include -no-cpp-precomp -DX_LOCALE 
>> -DG_DISABLE_SINGLE_INCLUDES -DATK_DISABLE_SINGLE_INCLUDES 
>> -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES 
>> -I/opt/local/include -I/usr/X11/include    
>> -DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops -fstrict-aliasing 
>> -Wall -MT gdkdrawable-x11.lo -MD -MP -MF ".deps/gdkdrawable-x11.Tpo" \
>>     -c -o gdkdrawable-x11.lo `test -f 'gdkdrawable-x11.c' || echo 
>> './'`gdkdrawable-x11.c; \
>>   then mv -f ".deps/gdkdrawable-x11.Tpo" ".deps/gdkdrawable-x11.Plo"; \
>>   else rm -f ".deps/gdkdrawable-x11.Tpo"; exit 1; \
>>   fi
>> libtool: compile:  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I../.. 
>> -DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. -I../../gdk 
>> -I../../gdk -DG_DISABLE_CAST_CHECKS -D_REENTRANT 
>> -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include 
>> -I/opt/local/include -I/opt/local/include/pango-1.0 
>> -I/opt/local/include/cairo -I/opt/local/include/pixman-1 
>> -I/opt/local/include/freetype2 -I/opt/local/include/libpng12 
>> -I/usr/X11/include -I/opt/local/include -no-cpp-precomp -DX_LOCALE 
>> -DG_DISABLE_SINGLE_INCLUDES -DATK_DISABLE_SINGLE_INCLUDES 
>> -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES 
>> -I/opt/local/include -I/usr/X11/include 
>> -DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops -fstrict-aliasing 
>> -Wall -MT gdkdrawable-x11.lo -MD -MP -MF .deps/gdkdrawable-x11.Tpo -c 
>> gdkdrawable-x11.c  -fno-common -DPIC -o .libs/gdkdrawable-x11.o
>> gdkdrawable-x11.c:1289: warning: 'get_shm_pixmap_for_image' defined 
>> but not used
>> if /bin/sh ../../libtool --mode=compile /usr/bin/gcc-4.0 
>> -DHAVE_CONFIG_H -I. -I. -I../.. -DG_LOG_DOMAIN=\"Gdk\" 
>> -DGDK_COMPILATION -I../.. -I../../gdk -I../../gdk 
>> -DG_DISABLE_CAST_CHECKS -D_REENTRANT -I/opt/local/include/glib-2.0 
>> -I/opt/local/lib/glib-2.0/include -I/opt/local/include 
>> -I/opt/local/include/pango-1.0 -I/opt/local/include/cairo 
>> -I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 
>> -I/opt/local/include/libpng12 -I/usr/X11/include      
>> -I/opt/local/include -no-cpp-precomp -DX_LOCALE 
>> -DG_DISABLE_SINGLE_INCLUDES -DATK_DISABLE_SINGLE_INCLUDES 
>> -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES 
>> -I/opt/local/include -I/usr/X11/include    
>> -DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops -fstrict-aliasing 
>> -Wall -MT gdkevents-x11.lo -MD -MP -MF ".deps/gdkevents-x11.Tpo" \
>>     -c -o gdkevents-x11.lo `test -f 'gdkevents-x11.c' || echo 
>> './'`gdkevents-x11.c; \
>>   then mv -f ".deps/gdkevents-x11.Tpo" ".deps/gdkevents-x11.Plo"; \
>>   else rm -f ".deps/gdkevents-x11.Tpo"; exit 1; \
>>   fi
>> libtool: compile:  /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I../.. 
>> -DG_LOG_DOMAIN=\"Gdk\" -DGDK_COMPILATION -I../.. -I../../gdk 
>> -I../../gdk -DG_DISABLE_CAST_CHECKS -D_REENTRANT 
>> -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include 
>> -I/opt/local/include -I/opt/local/include/pango-1.0 
>> -I/opt/local/include/cairo -I/opt/local/include/pixman-1 
>> -I/opt/local/include/freetype2 -I/opt/local/include/libpng12 
>> -I/usr/X11/include -I/opt/local/include -no-cpp-precomp -DX_LOCALE 
>> -DG_DISABLE_SINGLE_INCLUDES -DATK_DISABLE_SINGLE_INCLUDES 
>> -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES 
>> -I/opt/local/include -I/usr/X11/include 
>> -DGDK_PIXBUF_DISABLE_DEPRECATED -O2 -funroll-loops -fstrict-aliasing 
>> -Wall -MT gdkevents-x11.lo -MD -MP -MF .deps/gdkevents-x11.Tpo -c 
>> gdkevents-x11.c  -fno-common -DPIC -o .libs/gdkevents-x11.o
>> gdkevents-x11.c: In function 'gdk_event_translate':
>> gdkevents-x11.c:2110: error: 'RRNotify' undeclared (first use in this 
>> function)
>> gdkevents-x11.c:2110: error: (Each undeclared identifier is reported 
>> only once
>> gdkevents-x11.c:2110: error: for each function it appears in.)
>> gdkevents-x11.c:2112: error: 'XRRNotifyEvent' undeclared (first use 
>> in this function)
>> gdkevents-x11.c:2112: error: 'notify' undeclared (first use in this 
>> function)
>> gdkevents-x11.c:2112: error: syntax error before ')' token
>> gdkevents-x11.c: In function 'gdk_x11_screen_get_window_manager_name':
>> gdkevents-x11.c:2721: warning: dereferencing type-punned pointer will 
>> break strict-aliasing rules
>> gdkevents-x11.c: In function 'gdk_x11_screen_supports_net_wm_hint':
>> gdkevents-x11.c:2821: warning: dereferencing type-punned pointer will 
>> break strict-aliasing rules
>> make[4]: *** [gdkevents-x11.lo] Error 1
>> make[3]: *** [all-recursive] Error 1
>> make[2]: *** [all] Error 2
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all] Error 2
>>
>> 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
>


From ryandesign at macports.org  Thu Dec 25 14:24:39 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 25 Dec 2008 16:24:39 -0600
Subject: Error installing xpdf with openmotif
In-Reply-To: <1229851171.494e0a23ad995@imp.free.fr>
References: <1229851171.494e0a23ad995@imp.free.fr>
Message-ID: <D9A68E42-484D-4057-9E64-07824345C683@macports.org>

On Dec 21, 2008, at 03:19, spam.spam.spam.spam at free.fr wrote:

> --->  Building openmotif
> 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_o 
> penmotif/work/openmotif-2.3.1"
> && make all " returned error 2
> Command output: /usr/X11R6/include/X11/Xft/Xft.h:191: error: parse  
> error before
> '*' token
> /usr/X11R6/include/X11/Xft/Xft.h:257: warning: type defaults to  
> 'int' in
> declaration of 'XftGlyphSpec'
> /usr/X11R6/include/X11/Xft/Xft.h:257: error: parse error before '*'  
> token

[snip]

Looks like this ticket:

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



From ryandesign at macports.org  Thu Dec 25 14:47:47 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 25 Dec 2008 16:47:47 -0600
Subject: Error installing xpdf with openmotif
In-Reply-To: <D9A68E42-484D-4057-9E64-07824345C683@macports.org>
References: <1229851171.494e0a23ad995@imp.free.fr>
	<D9A68E42-484D-4057-9E64-07824345C683@macports.org>
Message-ID: <BD9FA5AE-738F-4D64-B3F2-D4AC9F5D1EBE@macports.org>


On Dec 25, 2008, at 16:24, Ryan Schmidt wrote:

> On Dec 21, 2008, at 03:19, spam.spam.spam.spam at free.fr wrote:
>
>> --->  Building openmotif
>> 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_ 
>> openmotif/work/openmotif-2.3.1"
>> && make all " returned error 2
>> Command output: /usr/X11R6/include/X11/Xft/Xft.h:191: error: parse  
>> error before
>> '*' token
>> /usr/X11R6/include/X11/Xft/Xft.h:257: warning: type defaults to  
>> 'int' in
>> declaration of 'XftGlyphSpec'
>> /usr/X11R6/include/X11/Xft/Xft.h:257: error: parse error before  
>> '*' token
>
> [snip]
>
> Looks like this ticket:
>
> http://trac.macports.org/ticket/17631


...although that ticket seems to be for Leopard and you're on Tiger.  
I'm on Tiger too and it builds for me. Could you "sudo port  
selfupdate" to make sure everything's up to date, then "sudo port  
clean openmotif" and "sudo port -d install openmotif 2>&1 | tee ~/ 
Desktop/openmotif.txt" to generate a complete log? If it fails again,  
compress the log with "bzip2 ~/Desktop/openmotif.txt" then attach  
openmotif.txt.bz2 from your desktop to your reply and I'll compare it  
with the output I got from building on my system.




From jeremyhu at macports.org  Thu Dec 25 16:16:03 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Thu, 25 Dec 2008 16:16:03 -0800
Subject: Error installing xpdf with openmotif
In-Reply-To: <BD9FA5AE-738F-4D64-B3F2-D4AC9F5D1EBE@macports.org>
References: <1229851171.494e0a23ad995@imp.free.fr>
	<D9A68E42-484D-4057-9E64-07824345C683@macports.org>
	<BD9FA5AE-738F-4D64-B3F2-D4AC9F5D1EBE@macports.org>
Message-ID: <C3990515-CA23-466B-8EE6-103E90676D35@macports.org>

I wonder if this is some
On Dec 25, 2008, at 14:47, Ryan Schmidt wrote:

>
> On Dec 25, 2008, at 16:24, Ryan Schmidt wrote:
>
>> On Dec 21, 2008, at 03:19, spam.spam.spam.spam at free.fr wrote:
>>
>>> --->  Building openmotif
>>> 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_openmotif/work/openmotif-2.3.1"
>>> && make all " returned error 2
>>> Command output: /usr/X11R6/include/X11/Xft/Xft.h:191: error: parse  
>>> error before
>>> '*' token
>>> /usr/X11R6/include/X11/Xft/Xft.h:257: warning: type defaults to  
>>> 'int' in
>>> declaration of 'XftGlyphSpec'
>>> /usr/X11R6/include/X11/Xft/Xft.h:257: error: parse error before  
>>> '*' token
>>
>> [snip]
>>
>> Looks like this ticket:
>>
>> http://trac.macports.org/ticket/17631
>
>
> ...although that ticket seems to be for Leopard and you're on Tiger.  
> I'm on Tiger too and it builds for me. Could you "sudo port  
> selfupdate" to make sure everything's up to date, then "sudo port  
> clean openmotif" and "sudo port -d install openmotif 2>&1 | tee ~/ 
> Desktop/openmotif.txt" to generate a complete log? If it fails  
> again, compress the log with "bzip2 ~/Desktop/openmotif.txt" then  
> attach openmotif.txt.bz2 from your desktop to your reply and I'll  
> compare it with the output I got from building on my system.

I wonder if /usr/X11R6/include/X11/Xft/Xft.h is seeing headers from  
macports' freetype instead of X11SDK freetype and getting flustered...




From ryandesign at macports.org  Thu Dec 25 19:05:54 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 25 Dec 2008 21:05:54 -0600
Subject: Error installing xpdf with openmotif
In-Reply-To: <C3990515-CA23-466B-8EE6-103E90676D35@macports.org>
References: <1229851171.494e0a23ad995@imp.free.fr>
	<D9A68E42-484D-4057-9E64-07824345C683@macports.org>
	<BD9FA5AE-738F-4D64-B3F2-D4AC9F5D1EBE@macports.org>
	<C3990515-CA23-466B-8EE6-103E90676D35@macports.org>
Message-ID: <D4355FC2-0210-45F1-B97D-79EFDBE0D361@macports.org>

On Dec 25, 2008, at 18:16, Jeremy Huddleston wrote:

> On Dec 25, 2008, at 14:47, Ryan Schmidt wrote:
>
>> On Dec 25, 2008, at 16:24, Ryan Schmidt wrote:
>>
>>> On Dec 21, 2008, at 03:19, spam.spam.spam.spam at free.fr wrote:
>>>
>>>> --->  Building openmotif
>>>> Error: Target org.macports.build returned: shell command " cd
>>>> "/opt/local/var/macports/build/ 
>>>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x1 
>>>> 1_openmotif/work/openmotif-2.3.1"
>>>> && make all " returned error 2
>>>> Command output: /usr/X11R6/include/X11/Xft/Xft.h:191: error:  
>>>> parse error before
>>>> '*' token
>>>> /usr/X11R6/include/X11/Xft/Xft.h:257: warning: type defaults to  
>>>> 'int' in
>>>> declaration of 'XftGlyphSpec'
>>>> /usr/X11R6/include/X11/Xft/Xft.h:257: error: parse error before  
>>>> '*' token
>>>
>>> [snip]
>>>
>>> Looks like this ticket:
>>>
>>> http://trac.macports.org/ticket/17631
>>
>> ...although that ticket seems to be for Leopard and you're on  
>> Tiger. I'm on Tiger too and it builds for me. Could you "sudo port  
>> selfupdate" to make sure everything's up to date, then "sudo port  
>> clean openmotif" and "sudo port -d install openmotif 2>&1 | tee ~/ 
>> Desktop/openmotif.txt" to generate a complete log? If it fails  
>> again, compress the log with "bzip2 ~/Desktop/openmotif.txt" then  
>> attach openmotif.txt.bz2 from your desktop to your reply and I'll  
>> compare it with the output I got from building on my system.
>
> I wonder if /usr/X11R6/include/X11/Xft/Xft.h is seeing headers from  
> macports' freetype instead of X11SDK freetype and getting flustered...

We want freetype in ${prefix} to be used instead of freetype in $ 
{x11prefix}, as per our standing policy, because MacPorts freetype is  
newer...

If Xft2 in ${x11prefix} gets confused by using freetype in ${prefix}  
then we should be using Xft2 in ${prefix}, which I would think we  
should be doing anyway because it's newer too. But in r43207 you  
changed the port, Jeremy, from requiring the MacPorts Xft2 to  
accepting an Xft2 in ${x11prefix}. I do have the Xft2 port installed.  
Do you, "spam.spam.spam.spam", or are you using Xft2 in ${x11prefix}?



From ryandesign at macports.org  Thu Dec 25 20:33:53 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Thu, 25 Dec 2008 22:33:53 -0600
Subject: xfe (fox) segmentation fault
In-Reply-To: <4953C9DF.7010807@vcn.com>
References: <4952692B.6060507@vcn.com>
	<35FFACA7-3176-46AB-9830-8C4EEA90EE3D@macports.org>
	<4953C9DF.7010807@vcn.com>
Message-ID: <7F11C96A-4F3C-406B-80E1-FC38E308F449@macports.org>

On Dec 25, 2008, at 11:58, Jonathan Stickel wrote:

> Ryan Schmidt wrote:
>> On Dec 24, 2008, at 10:54, Jonathan Stickel wrote:
>>> I would like to try the xfe file manager.  It installs fine  
>>> (Tiger 10.4.11), but then seg faults when I try to run it:
>>>
>>> $ xfe
>>> Segmentation fault
>>>
>>> The problem seems to be with the fox library on which it is  
>>> built; if I run a binary that is part of the fox build, I also  
>>> get segmentation faults.  For example:
>>>
>>> $ port contents fox | grep bin
>>>   /opt/local/bin/adie
>>> ...
>>>
>>> $ /opt/local/bin/adie
>>> Segmentation fault
>>>
>>> Does anyone else see this?  Should I file a bug report ticket?
>> I don't get a segmentation fault on Tiger... When X11 is not  
>> running I get:
>> $ adie
>> Adie::openDisplay: unable to open display :0.0
>> And when X11 is running I get:
>> $ adie
>> _X11TransSocketUNIXConnect: Cannot connect to non-local  
>> host ????????????
>> XIO:  fatal IO error 22 (Unknown error: 0) on X server ":0.0"
>>       after 7 requests (6 known processed) with 0 events remaining.
>> Which is this ticket:
>> http://trac.macports.org/ticket/17558
>
> I am well aware of that bug.  It can be at least partially fixed  
> for gtk2 by removing the libXfixes dependency from the portfile, as  
> I report in the ticket.
>
> Perhaps this bug with the fox library is related... How can we  
> debug it?

I'm not sure... Since adie crashed, hopefully it wrote a crash log to  
~/Library/Logs/CrashReporter. Maybe its contents will clue us in...


From jjstickel at vcn.com  Fri Dec 26 09:14:39 2008
From: jjstickel at vcn.com (Jonathan Stickel)
Date: Fri, 26 Dec 2008 10:14:39 -0700
Subject: xfe (fox) segmentation fault
In-Reply-To: <7F11C96A-4F3C-406B-80E1-FC38E308F449@macports.org>
References: <4952692B.6060507@vcn.com>
	<35FFACA7-3176-46AB-9830-8C4EEA90EE3D@macports.org>
	<4953C9DF.7010807@vcn.com>
	<7F11C96A-4F3C-406B-80E1-FC38E308F449@macports.org>
Message-ID: <495510FF.5030604@vcn.com>

Ryan Schmidt wrote:
> On Dec 25, 2008, at 11:58, Jonathan Stickel wrote:
> 
>> Ryan Schmidt wrote:
>>> On Dec 24, 2008, at 10:54, Jonathan Stickel wrote:
>>>> I would like to try the xfe file manager.  It installs fine (Tiger 
>>>> 10.4.11), but then seg faults when I try to run it:
>>>>
>>>> $ xfe
>>>> Segmentation fault
>>>>
>>>> The problem seems to be with the fox library on which it is built; 
>>>> if I run a binary that is part of the fox build, I also get 
>>>> segmentation faults.  For example:
>>>>
>>>> $ port contents fox | grep bin
>>>>   /opt/local/bin/adie
>>>> ...
>>>>
>>>> $ /opt/local/bin/adie
>>>> Segmentation fault
>>>>
>>>> Does anyone else see this?  Should I file a bug report ticket?
>>> I don't get a segmentation fault on Tiger... When X11 is not running 
>>> I get:
>>> $ adie
>>> Adie::openDisplay: unable to open display :0.0
>>> And when X11 is running I get:
>>> $ adie
>>> _X11TransSocketUNIXConnect: Cannot connect to non-local host 
>>> ????????????
>>> XIO:  fatal IO error 22 (Unknown error: 0) on X server ":0.0"
>>>       after 7 requests (6 known processed) with 0 events remaining.
>>> Which is this ticket:
>>> http://trac.macports.org/ticket/17558
>>
>> I am well aware of that bug.  It can be at least partially fixed for 
>> gtk2 by removing the libXfixes dependency from the portfile, as I 
>> report in the ticket.
>>
>> Perhaps this bug with the fox library is related... How can we debug it?
> 
> I'm not sure... Since adie crashed, hopefully it wrote a crash log to 
> ~/Library/Logs/CrashReporter. Maybe its contents will clue us in...
> 

In the last two days, fox-1.6.34 was checked into Macports.  Initially I 
got:

$ sudo port install fox
--->  Fetching fox
--->  Verifying checksum(s) for fox
--->  Extracting fox
--->  Configuring fox
--->  Building fox
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_fox/work/fox-1.6.34" 
&& make all " returned error 2
Command output: FXFont.cpp:509: error: 'FC_WIDTH_SEMICONDENSED' was not 
declared in this scope
FXFont.cpp:510: error: 'FC_WIDTH_NORMAL' was not declared in this scope
...

After some googling, it was apparent this is related to the Xft2 
libraries.  After installing the Macports Xft2 (instead of relying on 
Apple's), it installs cleanly, does not segfault, and xfe also now 
works!  Again, this is on Tiger.

I have filed a bug report for fox:  https://trac.macports.org/ticket/17779

Also, gtk2 (+x11) still compiles and works fine, even though Xft2 pulled 
in the Macports xrender.

Jonathan

From ryandesign at macports.org  Fri Dec 26 13:19:05 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Fri, 26 Dec 2008 15:19:05 -0600
Subject: Error installing xpdf with openmotif
In-Reply-To: <1230315226.49551edaf41cd@imp.free.fr>
References: <1229851171.494e0a23ad995@imp.free.fr>
	<D9A68E42-484D-4057-9E64-07824345C683@macports.org>
	<BD9FA5AE-738F-4D64-B3F2-D4AC9F5D1EBE@macports.org>
	<C3990515-CA23-466B-8EE6-103E90676D35@macports.org>
	<D4355FC2-0210-45F1-B97D-79EFDBE0D361@macports.org>
	<1230315226.49551edaf41cd@imp.free.fr>
Message-ID: <EAA2B6DD-09DE-4F42-BF1A-9F5D8C6C6C19@macports.org>


On Dec 26, 2008, at 12:13, spam.spam.spam.spam at free.fr wrote:

> Ryan Schmidt wrote:
>
>> On Dec 25, 2008, at 18:16, Jeremy Huddleston wrote:
>>
>>> On Dec 25, 2008, at 14:47, Ryan Schmidt wrote:
>>>
>>>> On Dec 25, 2008, at 16:24, Ryan Schmidt wrote:
>>>>
>>>>> On Dec 21, 2008, at 03:19, spam.spam.spam.spam at free.fr wrote:
>>>>>
>>>>>> --->  Building openmotif
>>>>>> Error: Target org.macports.build returned: shell command " cd
>>>>>> "/opt/local/var/macports/build/
>>>>>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_ 
>>>>>> x1
>>>>>> 1_openmotif/work/openmotif-2.3.1"
>>>>>> && make all " returned error 2
>>>>>> Command output: /usr/X11R6/include/X11/Xft/Xft.h:191: error:
>>>>>> parse error before
>>>>>> '*' token
>>>>>> /usr/X11R6/include/X11/Xft/Xft.h:257: warning: type defaults to
>>>>>> 'int' in
>>>>>> declaration of 'XftGlyphSpec'
>>>>>> /usr/X11R6/include/X11/Xft/Xft.h:257: error: parse error before
>>>>>> '*' token
>>>>>
>>>>> [snip]
>>>>>
>>>>> Looks like this ticket:
>>>>>
>>>>> http://trac.macports.org/ticket/17631
>>>>
>>>> ...although that ticket seems to be for Leopard and you're on
>>>> Tiger. I'm on Tiger too and it builds for me. Could you "sudo port
>>>> selfupdate" to make sure everything's up to date, then "sudo port
>>>> clean openmotif" and "sudo port -d install openmotif 2>&1 | tee ~/
>>>> Desktop/openmotif.txt" to generate a complete log? If it fails
>>>> again, compress the log with "bzip2 ~/Desktop/openmotif.txt" then
>>>> attach openmotif.txt.bz2 from your desktop to your reply and I'll
>>>> compare it with the output I got from building on my system.
>>>
>>> I wonder if /usr/X11R6/include/X11/Xft/Xft.h is seeing headers from
>>> macports' freetype instead of X11SDK freetype and getting  
>>> flustered...
>>
>> We want freetype in ${prefix} to be used instead of freetype in $
>> {x11prefix}, as per our standing policy, because MacPorts freetype is
>> newer...
>>
>> If Xft2 in ${x11prefix} gets confused by using freetype in ${prefix}
>> then we should be using Xft2 in ${prefix}, which I would think we
>> should be doing anyway because it's newer too. But in r43207 you
>> changed the port, Jeremy, from requiring the MacPorts Xft2 to
>> accepting an Xft2 in ${x11prefix}. I do have the Xft2 port installed.
>> Do you, "spam.spam.spam.spam", or are you using Xft2 in ${x11prefix}?
>
> $ port uninstall Xft2
> Error: port uninstall failed: Registry error: Xft2 not registered  
> as installed.
>
> so...it is not installed.
> What I should do?


Ok, so you do not have the Xft2 port installed, and I do. So try  
installing Xft2 ("sudo port install Xft2"). Then see if openmotif  
will build ("sudo port clean openmotif" and "sudo port install  
openmotif").

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


From jeremyhu at macports.org  Fri Dec 26 13:46:38 2008
From: jeremyhu at macports.org (Jeremy Huddleston)
Date: Fri, 26 Dec 2008 13:46:38 -0800
Subject: Error installing xpdf with openmotif
In-Reply-To: <D4355FC2-0210-45F1-B97D-79EFDBE0D361@macports.org>
References: <1229851171.494e0a23ad995@imp.free.fr>
	<D9A68E42-484D-4057-9E64-07824345C683@macports.org>
	<BD9FA5AE-738F-4D64-B3F2-D4AC9F5D1EBE@macports.org>
	<C3990515-CA23-466B-8EE6-103E90676D35@macports.org>
	<D4355FC2-0210-45F1-B97D-79EFDBE0D361@macports.org>
Message-ID: <0347CEA0-D11C-4632-BD2D-946DE3736D03@macports.org>


On Dec 25, 2008, at 19:05, Ryan Schmidt wrote:

>>>>> --->  Building openmotif
>>>>> 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_openmotif/work/openmotif-2.3.1"
>>>>> && make all " returned error 2
>>>>> Command output: /usr/X11R6/include/X11/Xft/Xft.h:191: error:  
>>>>> parse error before
>>>>> '*' token
>>>>> /usr/X11R6/include/X11/Xft/Xft.h:257: warning: type defaults to  
>>>>> 'int' in
>>>>> declaration of 'XftGlyphSpec'
>>>>> /usr/X11R6/include/X11/Xft/Xft.h:257: error: parse error before  
>>>>> '*' token
>>>>
>>>> [snip]
>>>>
>>>> Looks like this ticket:
>>>>
>>>> http://trac.macports.org/ticket/17631
>>>
>>> ...although that ticket seems to be for Leopard and you're on  
>>> Tiger. I'm on Tiger too and it builds for me. Could you "sudo port  
>>> selfupdate" to make sure everything's up to date, then "sudo port  
>>> clean openmotif" and "sudo port -d install openmotif 2>&1 | tee ~/ 
>>> Desktop/openmotif.txt" to generate a complete log? If it fails  
>>> again, compress the log with "bzip2 ~/Desktop/openmotif.txt" then  
>>> attach openmotif.txt.bz2 from your desktop to your reply and I'll  
>>> compare it with the output I got from building on my system.
>>
>> I wonder if /usr/X11R6/include/X11/Xft/Xft.h is seeing headers from  
>> macports' freetype instead of X11SDK freetype and getting  
>> flustered...
>
> We want freetype in ${prefix} to be used instead of freetype in $ 
> {x11prefix}, as per our standing policy, because MacPorts freetype  
> is newer...

Right, I understand that.  I was drawing the line for "from macports"  
at png, pixman, cairo, freetype, and fontconfig.  Everything in /usr/ 
X11 from x.org was being used if it is compatible.

> If Xft2 in ${x11prefix} gets confused by using freetype in ${prefix}  
> then we should be using Xft2 in ${prefix}, which I would think we  
> should be doing anyway because it's newer too.

Well then where do you draw the line?  Should we start forcing libX11  
in macports because it's newer?  I'd be all for forcing Macports X11  
libs over system X11 libs, since it would throw all of these issues  
(.la-fu, dependencies pulling in conflicting libX11s (#17558), header- 
mixup-fu, ...) out the window!

We could still add a +system_x11 variant to all of the X11 lib  
packages which would cause them to just be stubs, so people could  
continue to use their system X11 by enabling that variant...

> But in r43207 you changed the port, Jeremy, from requiring the  
> MacPorts Xft2 to accepting an Xft2 in ${x11prefix}. I do have the  
> Xft2 port installed. Do you, "spam.spam.spam.spam", or are you using  
> Xft2 in ${x11prefix}?

Everything that I changed from using port:Xft2 to lib:libXft:Xft2  
(including openmotif), I tested with no Xft2 port installed on both  
Tiger and Leopard.

Unfortunately, I don't have my Tiger box with me over holiday, so I  
can't be much help with this right now, but I'll be able to diagnose  
it further next week.



From spam.spam.spam.spam at free.fr  Fri Dec 26 14:47:08 2008
From: spam.spam.spam.spam at free.fr (spam.spam.spam.spam at free.fr)
Date: Fri, 26 Dec 2008 23:47:08 +0100
Subject: Error installing xpdf with openmotif
In-Reply-To: <0347CEA0-D11C-4632-BD2D-946DE3736D03@macports.org>
References: <1229851171.494e0a23ad995@imp.free.fr>
	<D9A68E42-484D-4057-9E64-07824345C683@macports.org>
	<BD9FA5AE-738F-4D64-B3F2-D4AC9F5D1EBE@macports.org>
	<C3990515-CA23-466B-8EE6-103E90676D35@macports.org>
	<D4355FC2-0210-45F1-B97D-79EFDBE0D361@macports.org>
	<0347CEA0-D11C-4632-BD2D-946DE3736D03@macports.org>
Message-ID: <1230331628.49555eec9013b@imp.free.fr>

Selon Jeremy Huddleston <jeremyhu at macports.org>:

>
> On Dec 25, 2008, at 19:05, Ryan Schmidt wrote:
>
> >>>>> --->  Building openmotif
> >>>>> 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_openmotif/work/openmotif-2.3.1"
> >>>>> && make all " returned error 2
> >>>>> Command output: /usr/X11R6/include/X11/Xft/Xft.h:191: error:
> >>>>> parse error before
> >>>>> '*' token
> >>>>> /usr/X11R6/include/X11/Xft/Xft.h:257: warning: type defaults to
> >>>>> 'int' in
> >>>>> declaration of 'XftGlyphSpec'
> >>>>> /usr/X11R6/include/X11/Xft/Xft.h:257: error: parse error before
> >>>>> '*' token
> >>>>
> >>>> [snip]
> >>>>
> >>>> Looks like this ticket:
> >>>>
> >>>> http://trac.macports.org/ticket/17631
> >>>
> >>> ...although that ticket seems to be for Leopard and you're on
> >>> Tiger. I'm on Tiger too and it builds for me. Could you "sudo port
> >>> selfupdate" to make sure everything's up to date, then "sudo port
> >>> clean openmotif" and "sudo port -d install openmotif 2>&1 | tee ~/
> >>> Desktop/openmotif.txt" to generate a complete log? If it fails
> >>> again, compress the log with "bzip2 ~/Desktop/openmotif.txt" then
> >>> attach openmotif.txt.bz2 from your desktop to your reply and I'll
> >>> compare it with the output I got from building on my system.
> >>
> >> I wonder if /usr/X11R6/include/X11/Xft/Xft.h is seeing headers from
> >> macports' freetype instead of X11SDK freetype and getting
> >> flustered...
> >
> > We want freetype in ${prefix} to be used instead of freetype in $
> > {x11prefix}, as per our standing policy, because MacPorts freetype
> > is newer...
>
> Right, I understand that.  I was drawing the line for "from macports"
> at png, pixman, cairo, freetype, and fontconfig.  Everything in /usr/
> X11 from x.org was being used if it is compatible.
>
> > If Xft2 in ${x11prefix} gets confused by using freetype in ${prefix}
> > then we should be using Xft2 in ${prefix}, which I would think we
> > should be doing anyway because it's newer too.
>
> Well then where do you draw the line?  Should we start forcing libX11
> in macports because it's newer?  I'd be all for forcing Macports X11
> libs over system X11 libs, since it would throw all of these issues
> (.la-fu, dependencies pulling in conflicting libX11s (#17558), header-
> mixup-fu, ...) out the window!
>
> We could still add a +system_x11 variant to all of the X11 lib
> packages which would cause them to just be stubs, so people could
> continue to use their system X11 by enabling that variant...
>
> > But in r43207 you changed the port, Jeremy, from requiring the
> > MacPorts Xft2 to accepting an Xft2 in ${x11prefix}. I do have the
> > Xft2 port installed. Do you, "spam.spam.spam.spam", or are you using
> > Xft2 in ${x11prefix}?
>
> Everything that I changed from using port:Xft2 to lib:libXft:Xft2
> (including openmotif), I tested with no Xft2 port installed on both
> Tiger and Leopard.
>
> Unfortunately, I don't have my Tiger box with me over holiday, so I
> can't be much help with this right now, but I'll be able to diagnose
> it further next week.
>
>
>

Thanx for all you answers.

I havn't Xft2 package installed :
$ port uninstall Xft2
Error: port uninstall failed: Registry error: Xft2 not registered as installed.

So, if xpdf depend of it, I install it:
$ sudo port install Xft2

After this, I restart the MacBook then I do :
$ sudo port selfupdate

MacPorts base version 1.700 installed
Downloaded MacPorts base version 1.700

The MacPorts installation is not outdated so it was not updated

$ sudo port clean openmotif
--->  Cleaning openmotif

Finally, I install xpdf :
$ sudo port install xpdf

After this I must deactivate the port poppler and restart :
$ sudo port install xpdf

And now xpdf works fine! (after launch X11)
Thank you a lot. I think xpdf need the dependance : Xft2 to works correctly. But
I let you decide what you should do :)

From kuepper.jochen at googlemail.com  Sat Dec 27 05:27:44 2008
From: kuepper.jochen at googlemail.com (=?ISO-8859-1?Q?Jochen_K=FCpper?=)
Date: Sat, 27 Dec 2008 14:27:44 +0100
Subject: Fwd: [MacPorts] #17761: molden4.6 rev 11: checksum error
References: <074.2ba0c45b31882a83192683ad2cfa5cc4@macports.org>
Message-ID: <066CA7A3-AF2B-44F4-BB12-B937DA3AD85F@googlemail.com>

> #17761: molden4.6 rev 11: checksum error
> ------------------------------------------- 
> +--------------------------------
> Reporter:  valerie.vallet@?               |       Owner:  jochen@?
>     Type:  defect                         |      Status:  new
> Priority:  High                           |   Milestone:  Port Bugs
> Component:  ports                          |     Version:  1.7.0
> Keywords:                                 |        Port:  molden
> ------------------------------------------- 
> +--------------------------------
>
> Comment(by jmr@?):
>
> There was probably a stealth update (contents of tarball changed  
> without
> changing the version number in its name), molden seems to do that a  
> lot.

true... fixing it right now

However, it is important that the tar-ball is always downloaded from  
the original site (see Portfile for details).
Nevertheless, port checks for macports mirrors:

DEBUG: ftp.cmbi.ru.nl ping time is 225.490
DEBUG: distfiles.macports.org ping time is 310.530
DEBUG: trd.no.distfiles.macports.org ping time is 239.436

How can I make sure, in the Portfile, that the mirrors are never used?

Greetings,
Jochen
-- 
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
     Libert?, ?galit?, Fraternit?                GnuPG key: CC1B0B4D
         Sex, drugs and rock-n-roll


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

From raimue at macports.org  Sat Dec 27 05:52:02 2008
From: raimue at macports.org (=?windows-1252?Q?Rainer_M=FCller?=)
Date: Sat, 27 Dec 2008 14:52:02 +0100
Subject: Fwd: [MacPorts] #17761: molden4.6 rev 11: checksum error
In-Reply-To: <066CA7A3-AF2B-44F4-BB12-B937DA3AD85F@googlemail.com>
References: <074.2ba0c45b31882a83192683ad2cfa5cc4@macports.org>
	<066CA7A3-AF2B-44F4-BB12-B937DA3AD85F@googlemail.com>
Message-ID: <49563302.1040103@macports.org>

Jochen K?pper wrote:
> However, it is important that the tar-ball is always downloaded from  
> the original site (see Portfile for details).
> Nevertheless, port checks for macports mirrors:
> 
> DEBUG: ftp.cmbi.ru.nl ping time is 225.490
> DEBUG: distfiles.macports.org ping time is 310.530
> DEBUG: trd.no.distfiles.macports.org ping time is 239.436
> 
> How can I make sure, in the Portfile, that the mirrors are never used?

No, the mirror sites are always tried. We are aware that molden should
not be mirrored and that it has a "special" license. The molden port is
explicitely excluded in the scripts used for mirroring.

See
<http://trac.macports.org/browser/trunk/base/portmgr/jobs/mirror_macports.sh>

Rainer

From kuepper.jochen at googlemail.com  Sat Dec 27 06:04:51 2008
From: kuepper.jochen at googlemail.com (=?WINDOWS-1252?Q?Jochen_K=FCpper?=)
Date: Sat, 27 Dec 2008 15:04:51 +0100
Subject: [MacPorts] #17761: molden4.6 rev 11: checksum error
In-Reply-To: <49563302.1040103@macports.org>
References: <074.2ba0c45b31882a83192683ad2cfa5cc4@macports.org>
	<066CA7A3-AF2B-44F4-BB12-B937DA3AD85F@googlemail.com>
	<49563302.1040103@macports.org>
Message-ID: <BBD38099-A8C8-444D-8E5A-53842A3E3FA1@googlemail.com>

Hi Rainer,

thanks for the quick reply!

On 27.12.2008, at 14:52, Rainer M?ller wrote:

> Jochen K?pper wrote:
>> However, it is important that the tar-ball is always downloaded from
>> the original site (see Portfile for details).
>> Nevertheless, port checks for macports mirrors:
>>
>> DEBUG: ftp.cmbi.ru.nl ping time is 225.490
>> DEBUG: distfiles.macports.org ping time is 310.530
>> DEBUG: trd.no.distfiles.macports.org ping time is 239.436
>>
>> How can I make sure, in the Portfile, that the mirrors are never  
>> used?
>
> No, the mirror sites are always tried. We are aware that molden should
> not be mirrored and that it has a "special" license. The molden port  
> is
> explicitely excluded in the scripts used for mirroring.
>
> See
> <http://trac.macports.org/browser/trunk/base/portmgr/jobs/mirror_macports.sh 
> >


good

Greetings,
Jochen
-- 
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
     Libert?, ?galit?, Fraternit?                GnuPG key: CC1B0B4D
         Sex, drugs and rock-n-roll


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

From ryandesign at macports.org  Sun Dec 28 01:01:25 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 28 Dec 2008 03:01:25 -0600
Subject: libxml2 woes (PHP5 and friends)
In-Reply-To: <976FF5EE-724C-46A0-B6FC-A1993A49D392@gmail.com>
References: <976FF5EE-724C-46A0-B6FC-A1993A49D392@gmail.com>
Message-ID: <D4D8EA5A-7B1D-4B07-BF23-FD6FDAEB9BCC@macports.org>


On Dec 26, 2008, at 21:06, Thomas Foutz wrote:

> I have been bugged by this for a while.  I currently have php5  
> 5.2.8 installed on my tiger system.  How could i go about  
> implementing this fix you mentioned?

Hi Thomas. I'm afraid I don't know of any fix at this time. Chris  
Janton mentioned in his last message that things now worked for him,  
but I didn't understand why.

The PHP bug on this issue mentions that the next version of libxml2  
will include a fix for this issue:

http://bugs.php.net/bug.php?id=45996

So, we wait for that release to occur. Or if someone can figure out  
where their source code is repository and if they have already  
checked in a fix then perhaps we can apply it to the libxml2 port now  
already.

I'm copying this message back to the macports-users mailing list  
where the thread originated.



From blb at macports.org  Sun Dec 28 01:35:59 2008
From: blb at macports.org (Bryan Blackburn)
Date: Sun, 28 Dec 2008 02:35:59 -0700
Subject: libxml2 woes (PHP5 and friends)
In-Reply-To: <D4D8EA5A-7B1D-4B07-BF23-FD6FDAEB9BCC@macports.org>
References: <976FF5EE-724C-46A0-B6FC-A1993A49D392@gmail.com>
	<D4D8EA5A-7B1D-4B07-BF23-FD6FDAEB9BCC@macports.org>
Message-ID: <20081228093559.GJ1291@ninagal.withay.com>

On Sun, Dec 28, 2008 at 03:01:25AM -0600, Ryan Schmidt said:
>
> On Dec 26, 2008, at 21:06, Thomas Foutz wrote:
>
>> I have been bugged by this for a while.  I currently have php5 5.2.8 
>> installed on my tiger system.  How could i go about implementing this 
>> fix you mentioned?
>
> Hi Thomas. I'm afraid I don't know of any fix at this time. Chris Janton 
> mentioned in his last message that things now worked for him, but I didn't 
> understand why.
>
> The PHP bug on this issue mentions that the next version of libxml2 will 
> include a fix for this issue:
>
> http://bugs.php.net/bug.php?id=45996
>
> So, we wait for that release to occur. Or if someone can figure out where 
> their source code is repository and if they have already checked in a fix 
> then perhaps we can apply it to the libxml2 port now already.

Possibly this:

<http://mail.gnome.org/archives/xml/2008-December/msg00041.html>

Bryan

[...]


From face at CentosPrime.COM  Sun Dec 28 07:29:38 2008
From: face at CentosPrime.COM (Chris Janton)
Date: Sun, 28 Dec 2008 08:29:38 -0700
Subject: libxml2 woes (PHP5 and friends)
In-Reply-To: <D4D8EA5A-7B1D-4B07-BF23-FD6FDAEB9BCC@macports.org>
References: <976FF5EE-724C-46A0-B6FC-A1993A49D392@gmail.com>
	<D4D8EA5A-7B1D-4B07-BF23-FD6FDAEB9BCC@macports.org>
Message-ID: <52E7D001-2C30-4FED-9004-2B7AE17A63E0@centosprime.com>

On 2008-12-28 , at 02:01 , Ryan Schmidt wrote:

> Hi Thomas. I'm afraid I don't know of any fix at this time. Chris  
> Janton mentioned in his last message that things now worked for him,  
> but I didn't understand why.


On my 10.5 system things are working well. On my 10.3 system, not so  
well.

The "fix" happened when this change was applied

	http://trac.macports.org/changeset/43388

As far as I understand it we need to tell PHP to use "expat" as  
opposed to defaulting to using libxml2 for parsing.

Somewhere in mid-2008 this configuration option for PHP

	--with-expat-dir=${prefix}

needed to be changed to this configuration option

	--with-libexpat-dir=${prefix}

that causes PHP to use expat instead of libxml2, so the old behavior  
"returned".

The renaming of the configure option for PHP 5.1 or later was noted at http://bugs.php.net/bug.php?id=34221 
  back in August, 2005.

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



From tim.visher at gmail.com  Sun Dec 28 09:22:35 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Sun, 28 Dec 2008 12:22:35 -0500
Subject: Strange MPlayer error after successful install
In-Reply-To: <EDBC0AF2-674C-4332-84B3-E770DC3CC275@macports.org>
References: <c115fd3c0812221919k665fd0d2pdd69a3bc7a5b2f09@mail.gmail.com>
	<829729D0-835F-449D-8750-356B006DEC71@macports.org>
	<20081223090752.GF744@ninagal.withay.com>
	<EDBC0AF2-674C-4332-84B3-E770DC3CC275@macports.org>
Message-ID: <c115fd3c0812280922j5344a090geecc732cacbb13d2@mail.gmail.com>

On Tue, Dec 23, 2008 at 4:13 PM, Ryan Schmidt <ryandesign at macports.org> wrote:

> Mhm... I see samba3 does install the weirdly-named
> ${prefix}/lib/samba3/libsmbclient.dylib.0
>
> I rebuilt MPlayer and it still doesn't seem to link with libsmbclient, based
> on the (lack of any) output from:
>
> port contents MPlayer | sed 1d | xargs grep smbclient

    [~]$ port contents MPlayer | sed 1d | xargs grep smbclient
    Binary file /opt/local/bin/mencoder matches
    Binary file /opt/local/bin/mplayer matches

I guess in the interest of full disclosure, I don't have a plain
vanilla version of mplayer installed.

    [~]$ port installed mplayer
    The following ports are currently installed:
      MPlayer @1.0rc2_2+aa+binary_codecs+caca+dts+dv+faac+fribidi+macosx+osd+sdl+smb+speex+theora+twolame+x264+xvid
(active)

I didn't think this was important but it clearly has introduced some
ambiguity into the discussion.  I'm thinking that the smb variant
might be what's causing this?

-- 

In Christ,

Timmy V.

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

From tim.visher at gmail.com  Sun Dec 28 10:20:09 2008
From: tim.visher at gmail.com (Tim Visher)
Date: Sun, 28 Dec 2008 13:20:09 -0500
Subject: Strange MPlayer error after successful install
In-Reply-To: <c115fd3c0812280922j5344a090geecc732cacbb13d2@mail.gmail.com>
References: <c115fd3c0812221919k665fd0d2pdd69a3bc7a5b2f09@mail.gmail.com>
	<829729D0-835F-449D-8750-356B006DEC71@macports.org>
	<20081223090752.GF744@ninagal.withay.com>
	<EDBC0AF2-674C-4332-84B3-E770DC3CC275@macports.org>
	<c115fd3c0812280922j5344a090geecc732cacbb13d2@mail.gmail.com>
Message-ID: <c115fd3c0812281020x7571b4a8pbe1799f413f31ca6@mail.gmail.com>

On Sun, Dec 28, 2008 at 12:22 PM, Tim Visher <tim.visher at gmail.com> wrote:

> I'm thinking that the smb variant might be what's causing this?

I just finished reinstalling sans-+smb and I can now run mplayer.  So
I think this is a confirmed source of the error I was getting.  What
would this cause said failure though?  I'd like the smb variant if I
can get it.

Thanks in advance!

-- 

In Christ,

Timmy V.

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

From gundalav at gmail.com  Sun Dec 28 11:21:56 2008
From: gundalav at gmail.com (Gundala Viswanath)
Date: Mon, 29 Dec 2008 04:21:56 +0900
Subject: MacPorts Fail to Install Package/Port
Message-ID: <73f827b50812281121w5af794cfgf8c1cf0883f91e8f@mail.gmail.com>

Dear all,

I tried to install any port using MacPorts, using the following
command:

gundalas-macbook-pro:~ gundala$ sudo port install gnuplot


However it give such error:

Error: Target org.macports.fetch returned: couldn't read file
"/opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/fetch/mirror_sites.tcl":
no such file or directory
Error: The following dependencies failed to build: aquaterm expat
fontconfig freetype zlib libiconv gd2 jpeg libpng ncurses ncursesw
pdflib readline
Error: Status 1 encountered during processing.

How can I resolve the problem?

- Gundala Viswanath
Jakarta - Indonesia

From raimue at macports.org  Sun Dec 28 11:31:40 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Sun, 28 Dec 2008 20:31:40 +0100
Subject: MacPorts Fail to Install Package/Port
In-Reply-To: <73f827b50812281121w5af794cfgf8c1cf0883f91e8f@mail.gmail.com>
References: <73f827b50812281121w5af794cfgf8c1cf0883f91e8f@mail.gmail.com>
Message-ID: <4957D41C.4090807@macports.org>

Gundala Viswanath wrote:
> Error: Target org.macports.fetch returned: couldn't read file
> "/opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/fetch/mirror_sites.tcl":
> no such file or directory
> Error: The following dependencies failed to build: aquaterm expat
> fontconfig freetype zlib libiconv gd2 jpeg libpng ncurses ncursesw
> pdflib readline
> Error: Status 1 encountered during processing.
> 
> How can I resolve the problem?

Looks like you installed MacPorts 1.7.0, but you have not synced your
tree. Just run 'sudo port selfupdate' to get the latest set of Portfiles.

Rainer

From gundalav at gmail.com  Sun Dec 28 11:37:46 2008
From: gundalav at gmail.com (Gundala Viswanath)
Date: Mon, 29 Dec 2008 04:37:46 +0900
Subject: MacPorts Fail to Install Package/Port
In-Reply-To: <4957D41C.4090807@macports.org>
References: <73f827b50812281121w5af794cfgf8c1cf0883f91e8f@mail.gmail.com>
	<4957D41C.4090807@macports.org>
Message-ID: <73f827b50812281137q7107d4bfr2c9521e4eaea33c8@mail.gmail.com>

Hi Rainer,

Even my 'selfupdate' has problem:

gundalas-macbook-pro:~ ewijaya$ sudo port selfupdate
Error: Synchronization of the local ports tree failed doing rsync
Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the
ports tree: Synchronization of 1 source(s) failed


Is there a way I can solve this?

- Gundala Viswanath
Jakarta - Indonesia



On Mon, Dec 29, 2008 at 4:31 AM, Rainer M?ller <raimue at macports.org> wrote:
> Gundala Viswanath wrote:
>> Error: Target org.macports.fetch returned: couldn't read file
>> "/opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/fetch/mirror_sites.tcl":
>> no such file or directory
>> Error: The following dependencies failed to build: aquaterm expat
>> fontconfig freetype zlib libiconv gd2 jpeg libpng ncurses ncursesw
>> pdflib readline
>> Error: Status 1 encountered during processing.
>>
>> How can I resolve the problem?
>
> Looks like you installed MacPorts 1.7.0, but you have not synced your
> tree. Just run 'sudo port selfupdate' to get the latest set of Portfiles.
>
> Rainer
>

From raimue at macports.org  Sun Dec 28 11:45:50 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Sun, 28 Dec 2008 20:45:50 +0100
Subject: MacPorts Fail to Install Package/Port
In-Reply-To: <73f827b50812281137q7107d4bfr2c9521e4eaea33c8@mail.gmail.com>
References: <73f827b50812281121w5af794cfgf8c1cf0883f91e8f@mail.gmail.com>	
	<4957D41C.4090807@macports.org>
	<73f827b50812281137q7107d4bfr2c9521e4eaea33c8@mail.gmail.com>
Message-ID: <4957D76E.1080901@macports.org>

Gundala Viswanath wrote:
> Even my 'selfupdate' has problem:
> 
> gundalas-macbook-pro:~ ewijaya$ sudo port selfupdate
> Error: Synchronization of the local ports tree failed doing rsync
> Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the
> ports tree: Synchronization of 1 source(s) failed

That seems like there is a network issue, e.g. rsync is blocked. You can
run 'sudo port -v selfupdate' (or even -d) for more details.

If rsync is blocked by your company or ISP for whatever reason, either
convince your administrator that rsync isn't harmful and there is no
reason to block it - or use alternatives provided over HTTP. Please see
these HOWTOs:

  * http://trac.macports.org/wiki/howto/PortTreeTarball
  * http://trac.macports.org/wiki/howto/SyncingWithSVN

Rainer

From gundalav at gmail.com  Sun Dec 28 12:33:53 2008
From: gundalav at gmail.com (Gundala Viswanath)
Date: Mon, 29 Dec 2008 05:33:53 +0900
Subject: MacPorts Fail to Install GD2
Message-ID: <73f827b50812281233r22c6b9a8p4701c2244cf5e6b4@mail.gmail.com>

Dear all,

In the process of installing gnuplot, it needs gd2.
However when I tried to install gd2 it gives the following error:

gundalas-macbook-pro:~ gundalas$ sudo port -v install gd2
--->  Building gd2
make  all-recursive
Making all in config
make[2]: Nothing to be done for `all'.
Making all in test
make[2]: Nothing to be done for `all'.
/bin/sh ./libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0
-DHAVE_CONFIG_H -I.   -I/opt/local/include/freetype2
-I/opt/local/include -I/opt/local/include -I/usr/X11/include  -O2 -MT
gd.lo -MD -MP -MF .deps/gd.Tpo -c -o gd.lo gd.c
./libtool: line 838: X--tag=CC: command not found
./libtool: line 871: libtool: ignoring unknown tag : command not found
./libtool: line 838: X--mode=compile: command not found
./libtool: line 1004: *** Warning: inferring the mode of operation is
deprecated.: command not found
./libtool: line 1005: *** Future versions of Libtool will require
--mode=MODE be specified.: command not found
./libtool: line 1035: libtool: warning: cannot infer operation mode
from `/usr/bin/gcc-4.0': No such file or directory
./libtool: line 7122: libtool: you must specify a MODE: command not found
./libtool: line 7123: Try `libtool --help' for more information.:
command not found
make[2]: *** [gd.lo] 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_gd2/work/gd-2.0.35"
&& make all " returned error 2
Command output: make  all-recursive
Making all in config
make[2]: Nothing to be done for `all'.
Making all in test
make[2]: Nothing to be done for `all'.
/bin/sh ./libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0
-DHAVE_CONFIG_H -I.   -I/opt/local/include/freetype2
-I/opt/local/include -I/opt/local/include -I/usr/X11/include  -O2 -MT
gd.lo -MD -MP -MF .deps/gd.Tpo -c -o gd.lo gd.c
./libtool: line 838: X--tag=CC: command not found
./libtool: line 871: libtool: ignoring unknown tag : command not found
./libtool: line 838: X--mode=compile: command not found
./libtool: line 1004: *** Warning: inferring the mode of operation is
deprecated.: command not found
./libtool: line 1005: *** Future versions of Libtool will require
--mode=MODE be specified.: command not found
./libtool: line 1035: libtool: warning: cannot infer operation mode
from `/usr/bin/gcc-4.0': No such file or directory
./libtool: line 7122: libtool: you must specify a MODE: command not found
./libtool: line 7123: Try `libtool --help' for more information.:
command not found
make[2]: *** [gd.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Warning: the following items did not execute (for gd2):
org.macports.activate org.macports.build org.macports.destroot
org.macports.install

Is there a way I can fix this?
Error: Status 1 encountered during processing.


- Gundala Viswanath
Jakarta - Indonesia

From macsforever2000 at macports.org  Sun Dec 28 12:38:58 2008
From: macsforever2000 at macports.org (Frank Schima)
Date: Sun, 28 Dec 2008 13:38:58 -0700
Subject: MacPorts Fail to Install GD2
In-Reply-To: <73f827b50812281233r22c6b9a8p4701c2244cf5e6b4@mail.gmail.com>
References: <73f827b50812281233r22c6b9a8p4701c2244cf5e6b4@mail.gmail.com>
Message-ID: <15BA7DC4-BE15-4A37-84C6-5829FB9E4790@macports.org>


On Dec 28, 2008, at 1:33 PM, Gundala Viswanath wrote:

> In the process of installing gnuplot, it needs gd2.
> However when I tried to install gd2 it gives the following error:

[snip]

> Is there a way I can fix this?

I just opened a ticket about this problem:

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


Cheers!
Frank


From com.nabble at nicerobot.org  Sun Dec 28 13:28:34 2008
From: com.nabble at nicerobot.org (nicerobot)
Date: Sun, 28 Dec 2008 13:28:34 -0800 (PST)
Subject: Perl 5.8.8 already present on Leopard; can I make a "dummy"
	Portfile?
Message-ID: <21156946.post@talk.nabble.com>


There's one fairly significant oversight with respect to doing this with
perl. Modules. Having multiple instances of the same version of perl5 that
are built with different @INC is a complete mess. At the very least, port
should configure itself to (or ask if it should) use the same configuration
as the existing perl installation.

-- 
View this message in context: http://www.nabble.com/Perl-5.8.8-already-present-on-Leopard--can-I-make-a-%22dummy%22-Portfile--tp14919531p21156946.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From tgommes at gmail.com  Sun Dec 28 14:08:31 2008
From: tgommes at gmail.com (Thomas Gommes)
Date: Sun, 28 Dec 2008 23:08:31 +0100
Subject: Newbie - Keeping a macport installation clean
Message-ID: <4957F8DF.7080501@gmail.com>

Hi Everyone,

after a couple of year using Gentoo Linux, I moved to Mac OS and was 
very happy to discover Macport. I have been playing around with it since 
a couple of days, installing and removing quite some stuff. I was now 
wondering if there was a way to keep the macport installation clean. I 
could not find advices on this topic in the doc; sorry if i missed it.

What I'm looking for is the equivalent of the Gentoo "emerge depclean" 
and "revdep-rebuild" commands; the idea is that the installation of 
package 1 also installs package 2 and package 3 as dependencies. 
Removing package 1 afterward would keep the packages 2 and 3 installed 
where there are no longer necessary. The "emerge depclean" command would 
remove the packages 2 and 3. This could however break some other package 
4 that would depend on package 3 for instance. Revdep-rebuild would find 
this and re-install package 3. Is there a way to achieve the equivalent 
with macport?

Many thanks for the help and for making macport,

Thomas


From trog24 at comcast.net  Sun Dec 28 14:12:21 2008
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Sun, 28 Dec 2008 14:12:21 -0800
Subject: Error message when nothing to upgrade?
Message-ID: <9F38A325-0B23-4BBD-8F5E-8730A10345C2@comcast.net>

Hello,
	When I ran "sudo port upgrade outdated", I got the following message:

Error: No ports found

	Is this message because no ports needed upgrading or is it because  
the command could find no ports?  If this message is a result of the  
former, then I think the wrong message is being displayed.
Frank


From frstan at bellsouth.net  Sun Dec 28 14:20:54 2008
From: frstan at bellsouth.net (William Davis)
Date: Sun, 28 Dec 2008 17:20:54 -0500
Subject: Error message when nothing to upgrade?
In-Reply-To: <9F38A325-0B23-4BBD-8F5E-8730A10345C2@comcast.net>
References: <9F38A325-0B23-4BBD-8F5E-8730A10345C2@comcast.net>
Message-ID: <ED033B83-2A7E-4163-97F1-DA5F6F3FF7CD@bellsouth.net>


On Dec 28, 2008, at 5:12 PM, Frank J. R. Hanstick wrote:

> Hello,
> 	When I ran "sudo port upgrade outdated", I got the following message:
>
> Error: No ports found
>
> 	Is this message because no ports needed upgrading or is it because  
> the command could find no ports?  If this message is a result of the  
> former, then I think the wrong message is being displayed.
> Frank
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Do:
sudo port -d selfupdate


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

Mundus vult decepi, ego non


From raimue at macports.org  Sun Dec 28 14:34:02 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Sun, 28 Dec 2008 23:34:02 +0100
Subject: Newbie - Keeping a macport installation clean
In-Reply-To: <4957F8DF.7080501@gmail.com>
References: <4957F8DF.7080501@gmail.com>
Message-ID: <4957FEDA.6010005@macports.org>

Thomas Gommes wrote:
> Is there a way to achieve the equivalent
> with macport?

Unfortunately, there is no such way. MacPorts does not track if you
installed a port as a dependency or if you requested it to be installed.

  * http://trac.macports.org/ticket/15260

There is also currently nothing to scan for broken packages and rebuild
them, except rebuild all dependent ports using 'port -R upgrade'.

  * http://trac.macports.org/ticket/17473

If you want to bring your ideas in, feel free to tell them (better being
discussed on macports-dev).

Rainer

From raimue at macports.org  Sun Dec 28 14:36:39 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Sun, 28 Dec 2008 23:36:39 +0100
Subject: Error message when nothing to upgrade?
In-Reply-To: <9F38A325-0B23-4BBD-8F5E-8730A10345C2@comcast.net>
References: <9F38A325-0B23-4BBD-8F5E-8730A10345C2@comcast.net>
Message-ID: <4957FF77.5060207@macports.org>

Frank J. R. Hanstick wrote:
> Hello,
> 	When I ran "sudo port upgrade outdated", I got the following message:
> 
> Error: No ports found
> 
> 	Is this message because no ports needed upgrading or is it because  
> the command could find no ports?  If this message is a result of the  
> former, then I think the wrong message is being displayed.

This means there are no ports that need upgrading.

This has already been improved in 1.7.0, as this is now a general
message you see any time the a list of ports could not be expanded to
any ports. I think it is some kind of error, although I understand that
you don't consider it an error when there is nothing to upgrade.

Rainer

From ryandesign at macports.org  Sun Dec 28 14:51:08 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Sun, 28 Dec 2008 16:51:08 -0600
Subject: Strange MPlayer error after successful install
In-Reply-To: <c115fd3c0812281020x7571b4a8pbe1799f413f31ca6@mail.gmail.com>
References: <c115fd3c0812221919k665fd0d2pdd69a3bc7a5b2f09@mail.gmail.com>
	<829729D0-835F-449D-8750-356B006DEC71@macports.org>
	<20081223090752.GF744@ninagal.withay.com>
	<EDBC0AF2-674C-4332-84B3-E770DC3CC275@macports.org>
	<c115fd3c0812280922j5344a090geecc732cacbb13d2@mail.gmail.com>
	<c115fd3c0812281020x7571b4a8pbe1799f413f31ca6@mail.gmail.com>
Message-ID: <84870892-DA40-4CC9-A0C1-A09E5138FB8D@macports.org>

On Dec 28, 2008, at 12:20, Tim Visher wrote:

> On Sun, Dec 28, 2008 at 12:22 PM, Tim Visher wrote:
>
>> I'm thinking that the smb variant might be what's causing this?
>
> I just finished reinstalling sans-+smb and I can now run mplayer.  So
> I think this is a confirmed source of the error I was getting.  What
> would this cause said failure though?  I'd like the smb variant if I
> can get it.

I can confirm it too. I even got a crash during the build:

2008-12-28 16:41:45 -0600

Link (dyld) error:

Library not loaded: bin/libsmbclient.dylib.0
   Referenced from: /tmp/mplayer-conf-21768-20833
   Reason: image not found

I'd recommend you file a bug report in our issue tracker for this  
problem. I'm not clear whether the problem is with MPlayer or samba3  
so you'd better send the ticket to both maintainers.


From trog24 at comcast.net  Sun Dec 28 18:39:20 2008
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Sun, 28 Dec 2008 18:39:20 -0800
Subject: Error message when nothing to upgrade?
In-Reply-To: <4957FF77.5060207@macports.org>
References: <9F38A325-0B23-4BBD-8F5E-8730A10345C2@comcast.net>
	<4957FF77.5060207@macports.org>
Message-ID: <391116C2-1B08-46E3-9B74-60B02C2A4D36@comcast.net>

Hello,
	Is replacing older versions with newer versions expanding the list  
of ports?
	Personally, I would prefer "everything current, nothing to  
upgrade".  That seems to me a less confusing response.
Frank

On Dec 28, 2008, at 2:36 PM, Rainer M?ller wrote:

> Frank J. R. Hanstick wrote:
>> Hello,
>> 	When I ran "sudo port upgrade outdated", I got the following  
>> message:
>>
>> Error: No ports found
>>
>> 	Is this message because no ports needed upgrading or is it because
>> the command could find no ports?  If this message is a result of the
>> former, then I think the wrong message is being displayed.
>
> This means there are no ports that need upgrading.
>
> This has already been improved in 1.7.0, as this is now a general
> message you see any time the a list of ports could not be expanded to
> any ports. I think it is some kind of error, although I understand  
> that
> you don't consider it an error when there is nothing to upgrade.
>
> Rainer


From wsiegrist at apple.com  Sun Dec 28 19:09:10 2008
From: wsiegrist at apple.com (William Siegrist)
Date: Sun, 28 Dec 2008 19:09:10 -0800
Subject: New Mirror in Sweden
Message-ID: <C815848E-D2F3-41F1-BAB9-1677B4E72CF4@apple.com>

The MacPorts project has a new mirror for both distfiles and portfiles  
in Stockholm, Sweden.  The distfile mirror will get used automatically  
when it is faster for you, but the portfile mirror is set in your  
sources.conf. See the wiki for more details.

http://trac.macports.org/wiki/Mirrors

Thanks
-Bill


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2421 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081228/f97cac94/attachment.bin>

From frstan at bellsouth.net  Sun Dec 28 20:20:01 2008
From: frstan at bellsouth.net (William Davis)
Date: Sun, 28 Dec 2008 23:20:01 -0500
Subject: inconsistent error mesgs (1.7)
Message-ID: <282F9BDF-65DD-4985-8470-70285576E612@bellsouth.net>

In MacPorts 1.7 when there are no outdated ports
port outdated
gives:

No installed ports are outdated.

but
sudo port upgrade outdated
gives:

Error: No ports found

which is much less clear.

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

Mundus vult decepi, ego non


From dluke at geeklair.net  Sun Dec 28 20:27:28 2008
From: dluke at geeklair.net (Daniel J. Luke)
Date: Sun, 28 Dec 2008 23:27:28 -0500
Subject: Perl 5.8.8 already present on Leopard;
	can I make a "dummy" Portfile?
In-Reply-To: <21156946.post@talk.nabble.com>
References: <21156946.post@talk.nabble.com>
Message-ID: <BC38256E-A835-4A56-B3A3-615112EE3475@geeklair.net>

On Dec 28, 2008, at 4:28 PM, nicerobot wrote:
> There's one fairly significant oversight

nope, it's a considered design decision.

> with respect to doing this with
> perl. Modules. Having multiple instances of the same version of  
> perl5 that
> are built with different @INC is a complete mess. At the very least,  
> port
> should configure itself to (or ask if it should) use the same  
> configuration
> as the existing perl installation.


This would probably be a bad idea.

See also:

http://trac.macports.org/wiki/FAQ#WillMacPortslinktosystemlibrariesratherthanitsown
--
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/20081228/b0b8d0d7/attachment.bin>

From com.nabble at nicerobot.org  Sun Dec 28 22:45:40 2008
From: com.nabble at nicerobot.org (nicerobot)
Date: Sun, 28 Dec 2008 22:45:40 -0800 (PST)
Subject: Perl 5.8.8 already present on Leopard; can I make a "dummy"
	Portfile?
In-Reply-To: <BC38256E-A835-4A56-B3A3-615112EE3475@geeklair.net>
References: <200801171508.00735.p.k.f.holzenspies@utwente.nl>
	<568AC4FE-44C8-4C63-A6D4-100C73F07320@macports.org>
	<200801171644.52264.p.k.f.holzenspies@utwente.nl>
	<0CCDFBA3-2F40-4012-BF4D-7320A93036D4@macports.org>
	<21156946.post@talk.nabble.com>
	<BC38256E-A835-4A56-B3A3-615112EE3475@geeklair.net>
Message-ID: <21199592.post@talk.nabble.com>


I fully understand the design decision. My point is that the decision is
flawed because it's too inflexible. Macports should be more versatile with
respect to perl because perl modules aren't generally treated the same as
binary libraries (i.e. the FAQ link you referenced isn't completely
applicable to perl modules). It's completely acceptable and understandable
for macports to provide it's own version(s) of perl and even to require a
set of modules. There's just absolutely no reason whatsoever that macport's
version of perl can't, for those that decide to do so, share/combine the
@INC with the OS's perl's @INC, especially when the two builds of perl are
identical versions.

To deny this request essentially forces users that have a significant
investment in the OS's perl to either spend the time getting macports into
the same state and switching to macports' perl or having to decide which
perl to use for certain situations and not be able to just rely on the
$PATH. Either way, it's not a user-friendly approach. Maybe i'm wrong but i
thought macports was about providing solution, not creating hurdles.



Daniel J. Luke wrote:
> 
> On Dec 28, 2008, at 4:28 PM, nicerobot wrote:
>> There's one fairly significant oversight
> 
> nope, it's a considered design decision.
> 
>> with respect to doing this with
>> perl. Modules. Having multiple instances of the same version of  
>> perl5 that
>> are built with different @INC is a complete mess. At the very least,  
>> port
>> should configure itself to (or ask if it should) use the same  
>> configuration
>> as the existing perl installation.
> 
> 
> This would probably be a bad idea.
> 
> See also:
> 
> http://trac.macports.org/wiki/FAQ#WillMacPortslinktosystemlibrariesratherthanitsown
> --
> Daniel J. Luke
> +========================================================+
> | *---------------- dluke at geeklair.net ----------------* |
> | *-------------- http://www.geeklair.net -------------* |
> +========================================================+
> |   Opinions expressed are mine and do not necessarily   |
> |          reflect the opinions of my employer.          |
> +========================================================+
> 
> 
> 
> 
>  
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> 
> 

-- 
View this message in context: http://www.nabble.com/Perl-5.8.8-already-present-on-Leopard--can-I-make-a-%22dummy%22-Portfile--tp14919531p21199592.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From kngspook at gmail.com  Sun Dec 28 23:41:50 2008
From: kngspook at gmail.com (Neil)
Date: Sun, 28 Dec 2008 23:41:50 -0800
Subject: Fwd: Perl 5.8.8 already present on Leopard;
	can I make a "dummy" Portfile?
In-Reply-To: <77e4079b0812282340j4e14df67ne41b732f17e771ef@mail.gmail.com>
References: <200801171508.00735.p.k.f.holzenspies@utwente.nl>
	<568AC4FE-44C8-4C63-A6D4-100C73F07320@macports.org>
	<200801171644.52264.p.k.f.holzenspies@utwente.nl>
	<0CCDFBA3-2F40-4012-BF4D-7320A93036D4@macports.org>
	<21156946.post@talk.nabble.com>
	<BC38256E-A835-4A56-B3A3-615112EE3475@geeklair.net>
	<21199592.post@talk.nabble.com>
	<77e4079b0812282340j4e14df67ne41b732f17e771ef@mail.gmail.com>
Message-ID: <77e4079b0812282341t31845990y89470d135d327b2d@mail.gmail.com>

On Sun, Dec 28, 2008 at 10:45 PM, nicerobot <com.nabble at nicerobot.org>wrote:

>
> To deny this request essentially forces users that have a significant
> investment in the OS's perl to either spend the time getting macports into
> the same state and switching to macports' perl


True, but...
1. ...it's a one-off.
2. ...I find it preferable to customize MacPort's Perl anyways (not that I
really have, but if I was going to...) because it's easier to wipe out the
MacPorts installation than it is to wipe out the OS' installation, and by
leaving the OS' installation pristine, I'm (more or less) guaranteed it will
be in the expected state for third-party apps.
3. ...how hard is it to duplicate your OS Perl customizations on the
MacPort's installation?  Exactly how much customizing are we dealing with?


> or having to decide which
> perl to use for certain situations and not be able to just rely on the
> $PATH.
>

Why can't you use the $PATH?
/opt/local/bin at the end -> system perl
/opt/local/bin at the start -> macports perl


> Maybe i'm wrong but i
> thought macports was about providing solution, not creating hurdles.
>

Not helping.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081228/e3a6170b/attachment.html>

From mp+u at v6shell.org  Mon Dec 29 00:53:04 2008
From: mp+u at v6shell.org (J.A. Neitzel)
Date: Mon, 29 Dec 2008 08:53:04 +0000
Subject: Newbie - Keeping a macport installation clean
In-Reply-To: <4957F8DF.7080501@gmail.com>
References: <4957F8DF.7080501@gmail.com>
Message-ID: <49588ff0.K6OlT3lKMboZCQ2P%mp+u@v6shell.org>

Thomas Gommes <tgommes at gmail.com> wrote:

> after a couple of year using Gentoo Linux, I moved to Mac OS and was 
> very happy to discover Macport. I have been playing around with it since 
> a couple of days, installing and removing quite some stuff. I was now 
> wondering if there was a way to keep the macport installation clean.

I guess it depends on what exactly you mean by clean ;)

For example, since I keep a set of installed ports around long
enough, keeping my MacPorts installation clean means uninstalling
"inactive" ports while keeping everything up to date.

The following fills this need for me:

% sudo port selfupdate
% sudo port upgrade outdated
% sudo port uninstall inactive

> What I'm looking for is the equivalent of the Gentoo "emerge depclean" 
> and "revdep-rebuild" commands; the idea is that the installation of 
> package 1 also installs package 2 and package 3 as dependencies. 

[snip]

In the normal case, MacPorts does not allow you to uninstall a port
if other port(s) depend on it.  Fortunately, a little shell goes a
long way to determine what depends on what.  I translated an osh(1)
script that I use into sh(1) and inlined it below [1].

For example, when you uninstall something you can run this to see
if there are any ports left that have "no dependents".  These ports
are now at the end of the dependency chain.  If you do not need
them, then you can do a:

% sudo port uninstall <port(s)_in_question>

...
to uninstall them.

Welcome to Mac OS X and MacPorts.
-- 
J.A. Neitzel
V6 Thompson Shell Port - http://v6shell.org/

[1] (mpdepinfo):
#!/bin/sh -

# mpdepinfo - print 2 lists of dependents in the following forms
#	1) <port> depends on <port>
#	2) <port> has no dependents!

umask 0077

dir="/tmp/`basename $0`-$$"
fil="$dir/cmdfil"
trap 'rtn=$?; rm -rf $dir; exit $rtn' EXIT
trap 'exit $?' HUP INT QUIT TERM

mkdir "$dir" || exit 2

(
	IFS='
'
	for p in `port installed | sed '1d ; s/^  // ; s/ (active)$//'` ; do
		echo dependents "$p"
	done
) >"$fil"

port -F "$fil" | egrep -v '^$|no dependents' | sort
echo
port -F "$fil" | grep 'no dependents' | sort

From mark at dxradio.demon.co.uk  Mon Dec 29 01:49:14 2008
From: mark at dxradio.demon.co.uk (Mark Hattam)
Date: Mon, 29 Dec 2008 09:49:14 +0000
Subject: New Mirror in Sweden
In-Reply-To: <C815848E-D2F3-41F1-BAB9-1677B4E72CF4@apple.com>
References: <C815848E-D2F3-41F1-BAB9-1677B4E72CF4@apple.com>
Message-ID: <F2F711B0-9275-4219-9561-CCC18D11A9AA@dxradio.demon.co.uk>


On 29 Dec 2008, at 03:09, William Siegrist wrote:

> The MacPorts project has a new mirror for both distfiles and  
> portfiles in Stockholm, Sweden.  The distfile mirror will get used  
> automatically when it is faster for you, but the portfile mirror is  
> set in your sources.conf. See the wiki for more details.
>
> http://trac.macports.org/wiki/Mirrors
>
> Thanks
> -Bill


Is this sources.conf file something we have to edit manually? Of is it  
updated when we sync/update?

The only non-commented line in my MacPorts 1.7 is
rsync://rsync.macports.org/release/ports/ [default]

and that line has more "path" on it than the Wiki page suggests.

Mark

From raimue at macports.org  Mon Dec 29 01:52:40 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Mon, 29 Dec 2008 10:52:40 +0100
Subject: inconsistent error mesgs (1.7)
In-Reply-To: <282F9BDF-65DD-4985-8470-70285576E612@bellsouth.net>
References: <282F9BDF-65DD-4985-8470-70285576E612@bellsouth.net>
Message-ID: <49589DE8.2060308@macports.org>

William Davis wrote:
> In MacPorts 1.7 when there are no outdated ports
> port outdated
> gives:
> 
> No installed ports are outdated.
> 
> but
> sudo port upgrade outdated
> gives:
> 
> Error: No ports found
> 
> which is much less clear.

We just had another thread about this with Frank.


The problem is that this error message is generated before the upgrade
action is run at all. You will see this message for all actions on any
pseudo-port which expands to an empty list. With "expand" I mean that
the pseudo-port 'outdated' is internally replaced with a list of all
outdated ports.

Should we just lower the priority of this message and remove the
"Error:" prefix?

Rainer

From raimue at macports.org  Mon Dec 29 01:58:21 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Mon, 29 Dec 2008 10:58:21 +0100
Subject: New Mirror in Sweden
In-Reply-To: <F2F711B0-9275-4219-9561-CCC18D11A9AA@dxradio.demon.co.uk>
References: <C815848E-D2F3-41F1-BAB9-1677B4E72CF4@apple.com>
	<F2F711B0-9275-4219-9561-CCC18D11A9AA@dxradio.demon.co.uk>
Message-ID: <49589F3D.9050608@macports.org>

Mark Hattam wrote:
> Is this sources.conf file something we have to edit manually? Of is it  
> updated when we sync/update?
> 
> The only non-commented line in my MacPorts 1.7 is
> rsync://rsync.macports.org/release/ports/ [default]
> 
> and that line has more "path" on it than the Wiki page suggests.

Right, the wiki page only lists the server part of the rsync URL. You
can also use it to sync base (configured in macports.conf) and that's a
similar URL.

Rainer

From wsiegrist at apple.com  Mon Dec 29 02:00:55 2008
From: wsiegrist at apple.com (William Siegrist)
Date: Mon, 29 Dec 2008 02:00:55 -0800
Subject: New Mirror in Sweden
In-Reply-To: <F2F711B0-9275-4219-9561-CCC18D11A9AA@dxradio.demon.co.uk>
References: <C815848E-D2F3-41F1-BAB9-1677B4E72CF4@apple.com>
	<F2F711B0-9275-4219-9561-CCC18D11A9AA@dxradio.demon.co.uk>
Message-ID: <B168EE0B-28A7-4A81-A9B6-E0CDE74727E0@apple.com>

On Dec 29, 2008, at 1:49 AM, Mark Hattam wrote:

>
> On 29 Dec 2008, at 03:09, William Siegrist wrote:
>
>> The MacPorts project has a new mirror for both distfiles and  
>> portfiles in Stockholm, Sweden.  The distfile mirror will get used  
>> automatically when it is faster for you, but the portfile mirror is  
>> set in your sources.conf. See the wiki for more details.
>>
>> http://trac.macports.org/wiki/Mirrors
>>
>> Thanks
>> -Bill
>
>
> Is this sources.conf file something we have to edit manually? Of is  
> it updated when we sync/update?
>
> The only non-commented line in my MacPorts 1.7 is
> rsync://rsync.macports.org/release/ports/ [default]
>
> and that line has more "path" on it than the Wiki page suggests.
>

You manually opt into the mirror by replacing the default URL with one  
of the others on the wiki page. You'll note that the default is the  
first one on the wiki page (the mirror at Apple in California).  So  
yes, edit the file manually. We do not have a lot of documentation on  
the file, but you should just be able to replace one URL for another  
(and leave that [default] tag there).  You can read the MacPorts guide  
for more details.

And good point on the paths missing on the URL. I added them to the  
wiki so hopefully it is less confusing.

Thanks
-Bill
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2421 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081229/3a665307/attachment.bin>

From wsiegrist at apple.com  Mon Dec 29 02:12:37 2008
From: wsiegrist at apple.com (William Siegrist)
Date: Mon, 29 Dec 2008 02:12:37 -0800
Subject: New Mirror in Sweden
In-Reply-To: <49589F3D.9050608@macports.org>
References: <C815848E-D2F3-41F1-BAB9-1677B4E72CF4@apple.com>
	<F2F711B0-9275-4219-9561-CCC18D11A9AA@dxradio.demon.co.uk>
	<49589F3D.9050608@macports.org>
Message-ID: <DD7E7FD1-EA31-421C-B3BE-4E174D84EF3D@apple.com>

On Dec 29, 2008, at 1:58 AM, Rainer M?ller wrote:

> Mark Hattam wrote:
>> Is this sources.conf file something we have to edit manually? Of is  
>> it
>> updated when we sync/update?
>>
>> The only non-commented line in my MacPorts 1.7 is
>> rsync://rsync.macports.org/release/ports/ [default]
>>
>> and that line has more "path" on it than the Wiki page suggests.
>
> Right, the wiki page only lists the server part of the rsync URL. You
> can also use it to sync base (configured in macports.conf) and  
> that's a
> similar URL.
>

Rainer,

I added a third table to point out the mirror usage in macports.conf.


-Bill

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2421 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20081229/dcdfd34c/attachment.bin>

From ndiscreet at gmail.com  Mon Dec 29 02:36:23 2008
From: ndiscreet at gmail.com (Altoine Barker)
Date: Mon, 29 Dec 2008 04:36:23 -0600
Subject: port collections
In-Reply-To: <06566F0C-1BC1-4E2C-BE44-5BC565C8380C@pixilla.com>
References: <06566F0C-1BC1-4E2C-BE44-5BC565C8380C@pixilla.com>
Message-ID: <4958A827.9080900@GmAiL.cOm>

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

I have been away for the holidays but I think this link:

<snip>
http://trac.macports.org/wiki/howto/MAMP
</snip>

is the answer you are seeking. If someone has already posted this
forgive me as I am trying to catch up on my email.

Bradley Giesbrecht wrote:
> Is there such a thing as a port collection?
> 
> Like port install-collection lamp or something that would install
> not-linux:)/apache/mysql/php/python/perl?
> 
> Bad example but just wondering.
> 
> Maybe a better one would be port install-collection pbx which could
> install a solid asterisk system.
> 
> I'm silly, I know.
> 
> 
> //brad
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAklYqCYACgkQQlfc9y4ObkMORQCeIXFIv9m8nCjyN6oa4u+9pz8n
Y9cAoISEYrjDB8JBLilvP15yQBOtvL10
=p5PT
-----END PGP SIGNATURE-----

From com.nabble at nicerobot.org  Mon Dec 29 03:27:15 2008
From: com.nabble at nicerobot.org (nicerobot)
Date: Mon, 29 Dec 2008 03:27:15 -0800 (PST)
Subject: Fwd: Perl 5.8.8 already present on Leopard; can I make a
	"dummy" Portfile?
In-Reply-To: <77e4079b0812282341t31845990y89470d135d327b2d@mail.gmail.com>
References: <200801171508.00735.p.k.f.holzenspies@utwente.nl>
	<568AC4FE-44C8-4C63-A6D4-100C73F07320@macports.org>
	<200801171644.52264.p.k.f.holzenspies@utwente.nl>
	<0CCDFBA3-2F40-4012-BF4D-7320A93036D4@macports.org>
	<21156946.post@talk.nabble.com>
	<BC38256E-A835-4A56-B3A3-615112EE3475@geeklair.net>
	<21199592.post@talk.nabble.com>
	<77e4079b0812282341t31845990y89470d135d327b2d@mail.gmail.com>
Message-ID: <21201971.post@talk.nabble.com>



King Spook wrote:
> 
> On Sun, Dec 28, 2008 at 10:45 PM, nicerobot
> <com.nabble at nicerobot.org>wrote:
> 
>>
>> To deny this request essentially forces users that have a significant
>> investment in the OS's perl to either spend the time getting macports
>> into
>> the same state and switching to macports' perl
> 
> 
> True, but...
> 1. ...it's a one-off.
> 2. ...I find it preferable to customize MacPort's Perl anyways (not that I
> really have, but if I was going to...) because it's easier to wipe out the
> MacPorts installation than it is to wipe out the OS' installation, and by
> leaving the OS' installation pristine, I'm (more or less) guaranteed it
> will
> be in the expected state for third-party apps.
> 
If i have dozens of utilities i've written that depend on particular modules
being present, i'd definitely _not_ want an easy way to wipe it out.
Personally, i'm not a wipe-and-rebuild person. I like to create environments
that work and modify them as needed. Once a system like that is configured,
it can take hours or days to rebuild it and it can be difficult or at least
more time consuming to ensure it's back to 100%.

King Spook wrote:
> 
> 3. ...how hard is it to duplicate your OS Perl customizations on the
> MacPort's installation?  Exactly how much customizing are we dealing with?
> 
Well, guessing, in my case, i probably use about 20-30 modules but am not
sure about their dependencies nor what was required to build them all.
Again, like my point above, the problem is identifying them. I have the OS
perl configured and working. If i want macports at the front of my $PATH, i
can't use any port that depends on perl without some pain. The only other
option i see is to tarball all the modules in the OS perl's @INC and
shoehorn them into macports' @INC.
I just didn't see a reason to deal with this when it should be relatively
easy to provide the ability to configure macports perl to use the OS perl's
@INC. 

King Spook wrote:
> 
> 
>> or having to decide which
>> perl to use for certain situations and not be able to just rely on the
>> $PATH.
>>
> 
> Why can't you use the $PATH?
> /opt/local/bin at the end -> system perl
> /opt/local/bin at the start -> macports perl
> 
You see my point here. $PATH has to be modified. That is essentially the
same as just fully qualifying the path to the binary i want to use. I mean,
if i need to modify the $PATH to use a single binary under different
situations, it'd actually be easier and safer to just qualify the path to
the binary.

King Spook wrote:
> 
> 
>> Maybe i'm wrong but i
>> thought macports was about providing solution, not creating hurdles.
>>
> 
> Not helping.
> 
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> 
> 

-- 
View this message in context: http://www.nabble.com/Perl-5.8.8-already-present-on-Leopard--can-I-make-a-%22dummy%22-Portfile--tp14919531p21201971.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From raimue at macports.org  Mon Dec 29 03:49:21 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Mon, 29 Dec 2008 12:49:21 +0100
Subject: Perl 5.8.8 already present on Leopard;
	can I make a "dummy"	Portfile?
In-Reply-To: <21199592.post@talk.nabble.com>
References: <200801171508.00735.p.k.f.holzenspies@utwente.nl>	<568AC4FE-44C8-4C63-A6D4-100C73F07320@macports.org>	<200801171644.52264.p.k.f.holzenspies@utwente.nl>	<0CCDFBA3-2F40-4012-BF4D-7320A93036D4@macports.org>	<21156946.post@talk.nabble.com>	<BC38256E-A835-4A56-B3A3-615112EE3475@geeklair.net>
	<21199592.post@talk.nabble.com>
Message-ID: <4958B941.3080903@macports.org>

nicerobot wrote:
> Maybe i'm wrong but i
> thought macports was about providing solution, not creating hurdles.

I don't know much about perl modules, but please propose changes to
current ports to macports-dev, file tickets and discuss it with the port
maintainers.

I think perl modules from the system in @INC are just left out for
consistency. Adding dependencies on perl modules isn't that easy and I
don't know if it creates any side effects to include system by default.
If any perl modules are missing, please report so and file tickets in
"Port Requests".

Marc Chantreux is working on cpan2port which is quite an interesting
project to make it easier to port perl modules also available over CPAN
and should make this process more easy in the future.

Rainer

From dluke at geeklair.net  Mon Dec 29 07:18:49 2008
From: dluke at geeklair.net (Daniel J. Luke)
Date: Mon, 29 Dec 2008 10:18:49 -0500
Subject: Perl 5.8.8 already present on Leopard;
	can I make a "dummy" Portfile?
In-Reply-To: <21199592.post@talk.nabble.com>
References: <200801171508.00735.p.k.f.holzenspies@utwente.nl>
	<568AC4FE-44C8-4C63-A6D4-100C73F07320@macports.org>
	<200801171644.52264.p.k.f.holzenspies@utwente.nl>
	<0CCDFBA3-2F40-4012-BF4D-7320A93036D4@macports.org>
	<21156946.post@talk.nabble.com>
	<BC38256E-A835-4A56-B3A3-615112EE3475@geeklair.net>
	<21199592.post@talk.nabble.com>
Message-ID: <E8F93EEC-60FD-4172-B1E1-BC4A8DC613C4@geeklair.net>

On Dec 29, 2008, at 1:45 AM, nicerobot wrote:
> I fully understand the design decision. My point is that the  
> decision is
> flawed because it's too inflexible.

It's basically impossible to ensure a working macports system while  
relying on software not installed by macports.

> Macports should be more versatile with
> respect to perl because perl modules aren't generally treated the  
> same as
> binary libraries (i.e. the FAQ link you referenced isn't completely
> applicable to perl modules).

Many perl modules compile libraries that are used (and aren't just  
pure perl).

> It's completely acceptable and understandable
> for macports to provide it's own version(s) of perl and even to  
> require a
> set of modules. There's just absolutely no reason whatsoever that  
> macport's
> version of perl can't, for those that decide to do so, share/combine  
> the
> @INC with the OS's perl's @INC, especially when the two builds of  
> perl are
> identical versions.

If you really wanted to, you could hack the portfile (or the macports  
perl install) to have @INC behave the way you want. It's just probably  
not something that is going to be set by default.

> To deny this request essentially forces users that have a significant
> investment in the OS's perl to either spend the time getting  
> macports into
> the same state and switching to macports' perl or having to decide  
> which
> perl to use for certain situations and not be able to just rely on the
> $PATH. Either way, it's not a user-friendly approach.

It's even less user-friendly to break seemingly randomly (what, I  
installed some broken module foo in my system perl and now all of the  
macports I installed that depend on perl are broken?)

If the perl-requiring software you use is in MacPorts, MacPorts will  
install all of the modules you need for it when you're installing it  
(so it can be fairly trivial to get MacPorts perl set up).

In any event... MacPorts is all run by volunteers, so if you have time  
to help make things better, we're happy to have your contributions.
--
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/20081229/3dfaa998/attachment.bin>

From frstan at bellsouth.net  Mon Dec 29 07:30:54 2008
From: frstan at bellsouth.net (William Davis)
Date: Mon, 29 Dec 2008 10:30:54 -0500
Subject: inconsistent error mesgs (1.7)
In-Reply-To: <49589DE8.2060308@macports.org>
References: <282F9BDF-65DD-4985-8470-70285576E612@bellsouth.net>
	<49589DE8.2060308@macports.org>
Message-ID: <48F191E2-E7E2-4187-B403-FC244A831F09@bellsouth.net>


On Dec 29, 2008, at 4:52 AM, Rainer M?ller wrote:

> William Davis wrote:
>> In MacPorts 1.7 when there are no outdated ports
>> port outdated
>> gives:
>>
>> No installed ports are outdated.
>>
>> but
>> sudo port upgrade outdated
>> gives:
>>
>> Error: No ports found
>>
>> which is much less clear.
>
> We just had another thread about this with Frank.
>
>
> The problem is that this error message is generated before the upgrade
> action is run at all. You will see this message for all actions on any
> pseudo-port which expands to an empty list. With "expand" I mean that
> the pseudo-port 'outdated' is internally replaced with a list of all
> outdated ports.
>
> Should we just lower the priority of this message and remove the
> "Error:" prefix?
>
> Rainer

Perhaps the  unexpanded pseudo-port name ought to appear in the  
message, eg:
No {pseudo-list} ports found

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

Mundus vult decepi, ego non


From com.nabble at nicerobot.org  Mon Dec 29 07:59:09 2008
From: com.nabble at nicerobot.org (nicerobot)
Date: Mon, 29 Dec 2008 07:59:09 -0800 (PST)
Subject: Perl 5.8.8 already present on Leopard; can I make a "dummy"
	Portfile?
In-Reply-To: <E8F93EEC-60FD-4172-B1E1-BC4A8DC613C4@geeklair.net>
References: <200801171508.00735.p.k.f.holzenspies@utwente.nl>
	<568AC4FE-44C8-4C63-A6D4-100C73F07320@macports.org>
	<200801171644.52264.p.k.f.holzenspies@utwente.nl>
	<0CCDFBA3-2F40-4012-BF4D-7320A93036D4@macports.org>
	<21156946.post@talk.nabble.com>
	<BC38256E-A835-4A56-B3A3-615112EE3475@geeklair.net>
	<21199592.post@talk.nabble.com>
	<E8F93EEC-60FD-4172-B1E1-BC4A8DC613C4@geeklair.net>
Message-ID: <21205043.post@talk.nabble.com>




Daniel J. Luke wrote:
> 
> If you really wanted to, you could hack the portfile (or the macports  
> perl install) to have @INC behave the way you want. It's just probably  
> not something that is going to be set by default.
> 
> It's even less user-friendly to break seemingly randomly (what, I  
> installed some broken module foo in my system perl and now all of the  
> macports I installed that depend on perl are broken?)
> 
This is really the point of my request in the first place. _I can_ hack the
system to do this and the fact that others seem to want to do something
similar means i'm not alone. I was simply asking for ports to provide a
feature to have the perl build do this automatically so that i don't have to
mess around with it myself. For a user to enable such a feature implies they
have some idea of what they're doing and know it could destabilize macports
so it isn't breaking it "seemingly randomly" since it would be intentional.
-- 
View this message in context: http://www.nabble.com/Perl-5.8.8-already-present-on-Leopard--can-I-make-a-%22dummy%22-Portfile--tp14919531p21205043.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.


From dluke at geeklair.net  Mon Dec 29 09:12:31 2008
From: dluke at geeklair.net (Daniel J. Luke)
Date: Mon, 29 Dec 2008 12:12:31 -0500
Subject: Perl 5.8.8 already present on Leopard;
	can I make a "dummy" Portfile?
In-Reply-To: <21205043.post@talk.nabble.com>
References: <200801171508.00735.p.k.f.holzenspies@utwente.nl>
	<568AC4FE-44C8-4C63-A6D4-100C73F07320@macports.org>
	<200801171644.52264.p.k.f.holzenspies@utwente.nl>
	<0CCDFBA3-2F40-4012-BF4D-7320A93036D4@macports.org>
	<21156946.post@talk.nabble.com>
	<BC38256E-A835-4A56-B3A3-615112EE3475@geeklair.net>
	<21199592.post@talk.nabble.com>
	<E8F93EEC-60FD-4172-B1E1-BC4A8DC613C4@geeklair.net>
	<21205043.post@talk.nabble.com>
Message-ID: <18122248-F194-46F9-B68F-3E5317A0A2B7@geeklair.net>

On Dec 29, 2008, at 10:59 AM, nicerobot wrote:
>  For a user to enable such a feature implies they
> have some idea of what they're doing and know it could destabilize  
> macports
> so it isn't breaking it "seemingly randomly" since it would be  
> intentional.

 From this, I would assume that you've never worked in a support  
role ;-)

This is a case where an additional option could cause a lot of harm to  
an unsuspecting end user, and there's not a lot of benefit (that I can  
see, anyway).

Either you buy into the idea of using a system to organize and install  
software for you, or you want to manage it yourself - there's not  
really a good way to combine the two.

--
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/20081229/505facab/attachment.bin>

From tgommes at gmail.com  Mon Dec 29 12:34:10 2008
From: tgommes at gmail.com (Thomas Gommes)
Date: Mon, 29 Dec 2008 21:34:10 +0100
Subject: Newbie - Keeping a macport installation clean
In-Reply-To: <49588ff0.K6OlT3lKMboZCQ2P%mp+u@v6shell.org>
References: <4957F8DF.7080501@gmail.com>
	<49588ff0.K6OlT3lKMboZCQ2P%mp+u@v6shell.org>
Message-ID: <49593442.9040407@gmail.com>

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

From trog24 at comcast.net  Mon Dec 29 13:19:38 2008
From: trog24 at comcast.net (Frank J. R. Hanstick)
Date: Mon, 29 Dec 2008 13:19:38 -0800
Subject: inconsistent error mesgs (1.7)
In-Reply-To: <49589DE8.2060308@macports.org>
References: <282F9BDF-65DD-4985-8470-70285576E612@bellsouth.net>
	<49589DE8.2060308@macports.org>
Message-ID: <F99ADCDE-9473-41D1-9E54-E8D5FB369DDC@comcast.net>

Hello,
	Unless one knows that "expand" in this case is the replacement of  
the "outdated port list", then this is a very confusing and  
misleading message.  Dropping "Error" would not do anything to  
alleviate the problem.  Maybe an inclusion in the error message of  
which list (ie "No outdated ports found") could be used.  The "No  
ports found" implies MacPorts cannot find any ports, not just the  
ports the command is looking for.
Frank

On Dec 29, 2008, at 1:52 AM, Rainer M?ller wrote:

> William Davis wrote:
>> In MacPorts 1.7 when there are no outdated ports
>> port outdated
>> gives:
>>
>> No installed ports are outdated.
>>
>> but
>> sudo port upgrade outdated
>> gives:
>>
>> Error: No ports found
>>
>> which is much less clear.
>
> We just had another thread about this with Frank.
>
>
> The problem is that this error message is generated before the upgrade
> action is run at all. You will see this message for all actions on any
> pseudo-port which expands to an empty list. With "expand" I mean that
> the pseudo-port 'outdated' is internally replaced with a list of all
> outdated ports.
>
> Should we just lower the priority of this message and remove the
> "Error:" prefix?
>
> Rainer


From raimue at macports.org  Mon Dec 29 13:55:28 2008
From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=)
Date: Mon, 29 Dec 2008 22:55:28 +0100
Subject: inconsistent error mesgs (1.7)
In-Reply-To: <48F191E2-E7E2-4187-B403-FC244A831F09@bellsouth.net>
References: <282F9BDF-65DD-4985-8470-70285576E612@bellsouth.net>
	<49589DE8.2060308@macports.org>
	<48F191E2-E7E2-4187-B403-FC244A831F09@bellsouth.net>
Message-ID: <49594750.8070903@macports.org>

William Davis wrote:
> Perhaps the  unexpanded pseudo-port name ought to appear in the  
> message, eg:
> No {pseudo-list} ports found

You can specify multiple pseudo-ports together with real ports and even
use logical statements with and/or/not.

For example:
  sudo port upgrade outdated and not \( vim bash \)
    => This would upgrade all outdated ports except vim and bash.

The error message you are seeing only appears if expanding *all* of the
given port arguments returns an empty set. By default, lists without
operator are assumed to be concatenated by the 'or' operation.

Maybe the error message should be:
  $ sudo port upgrade {portlist}
  Error: '{portlist}' did not match any ports

That should fit all needs, right?

Rainer

From jmr at macports.org  Mon Dec 29 23:17:49 2008
From: jmr at macports.org (Joshua Root)
Date: Tue, 30 Dec 2008 18:17:49 +1100
Subject: MacPorts Fail to Install Package/Port
In-Reply-To: <4957D76E.1080901@macports.org>
References: <73f827b50812281121w5af794cfgf8c1cf0883f91e8f@mail.gmail.com>		<4957D41C.4090807@macports.org>	<73f827b50812281137q7107d4bfr2c9521e4eaea33c8@mail.gmail.com>
	<4957D76E.1080901@macports.org>
Message-ID: <4959CB1D.1050505@macports.org>

Rainer M?ller wrote:
> Gundala Viswanath wrote:
>> Even my 'selfupdate' has problem:
>>
>> gundalas-macbook-pro:~ ewijaya$ sudo port selfupdate
>> Error: Synchronization of the local ports tree failed doing rsync
>> Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the
>> ports tree: Synchronization of 1 source(s) failed
> 
> That seems like there is a network issue, e.g. rsync is blocked. You can
> run 'sudo port -v selfupdate' (or even -d) for more details.
> 
> If rsync is blocked by your company or ISP for whatever reason, either
> convince your administrator that rsync isn't harmful and there is no
> reason to block it - or use alternatives provided over HTTP. Please see
> these HOWTOs:
> 
>   * http://trac.macports.org/wiki/howto/PortTreeTarball

That reminds me, howto/PortTreeTarball needs to be updated for 1.7 since
you can just set it in sources.conf now.

- Josh

From e_wiemann at gmx.de  Tue Dec 30 12:44:20 2008
From: e_wiemann at gmx.de (Eckhard Wiemann)
Date: Tue, 30 Dec 2008 21:44:20 +0100
Subject: Configuring recode fails after upgrading libtool
Message-ID: <8298A5D6-CF2A-45A4-A500-A24B37DAA730@gmx.de>

Hi all,

in order to upgrade libtool I uninstalled recode which depends on  
libtool. Trying to re-install recode I get the following error message:

[Users/eckhardwiemann] > install recode
--->  Fetching recode
--->  Verifying checksum(s) for recode
--->  Extracting recode
--->  Applying patches to recode
--->  Configuring recode
Error: Target org.macports.configure returned: error copying "/opt/ 
local/share/libtool/config.guess": no such file or directory
Error: Status 1 encountered during processing.

Does anyone have an idea of what's going wrong?

Happy New Year to all nevertheless!

Eckhard

From blb at macports.org  Tue Dec 30 14:02:59 2008
From: blb at macports.org (Bryan Blackburn)
Date: Tue, 30 Dec 2008 15:02:59 -0700
Subject: Configuring recode fails after upgrading libtool
In-Reply-To: <8298A5D6-CF2A-45A4-A500-A24B37DAA730@gmx.de>
References: <8298A5D6-CF2A-45A4-A500-A24B37DAA730@gmx.de>
Message-ID: <20081230220259.GC651@ninagal.withay.com>

On Tue, Dec 30, 2008 at 09:44:20PM +0100, Eckhard Wiemann said:
> Hi all,
>
> in order to upgrade libtool I uninstalled recode which depends on  
> libtool. Trying to re-install recode I get the following error message:
>
> [Users/eckhardwiemann] > install recode
> --->  Fetching recode
> --->  Verifying checksum(s) for recode
> --->  Extracting recode
> --->  Applying patches to recode
> --->  Configuring recode
> Error: Target org.macports.configure returned: error copying "/opt/ 
> local/share/libtool/config.guess": no such file or directory
> Error: Status 1 encountered during processing.
>
> Does anyone have an idea of what's going wrong?

Yes, it is an incompatibility with the 2.x version of libtool we now have;
I've fixed recode in r44568 so it works with either 1.x or 2.x.

Bryan


>
> Happy New Year to all nevertheless!
>
> Eckhard

From ryandesign at macports.org  Wed Dec 31 00:14:15 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 31 Dec 2008 02:14:15 -0600
Subject: Perl 5.8.8 already present on Leopard;
	can I make a "dummy" Portfile?
In-Reply-To: <21199592.post@talk.nabble.com>
References: <200801171508.00735.p.k.f.holzenspies@utwente.nl>
	<568AC4FE-44C8-4C63-A6D4-100C73F07320@macports.org>
	<200801171644.52264.p.k.f.holzenspies@utwente.nl>
	<0CCDFBA3-2F40-4012-BF4D-7320A93036D4@macports.org>
	<21156946.post@talk.nabble.com>
	<BC38256E-A835-4A56-B3A3-615112EE3475@geeklair.net>
	<21199592.post@talk.nabble.com>
Message-ID: <48A36A47-BF20-4228-9EC4-B5F49A807BDE@macports.org>


On Dec 29, 2008, at 00:45, nicerobot wrote:

> I fully understand the design decision. My point is that the  
> decision is
> flawed because it's too inflexible. Macports should be more  
> versatile with
> respect to perl because perl modules aren't generally treated the  
> same as
> binary libraries (i.e. the FAQ link you referenced isn't completely
> applicable to perl modules). It's completely acceptable and  
> understandable
> for macports to provide it's own version(s) of perl and even to  
> require a
> set of modules. There's just absolutely no reason whatsoever that  
> macport's
> version of perl can't, for those that decide to do so, share/ 
> combine the
> @INC with the OS's perl's @INC, especially when the two builds of  
> perl are
> identical versions.

That's just it -- the version of Perl included with Mac OS X and the  
version of perl5.8 in MacPorts happen to be identical at this moment  
in time -- they're both 5.8.8. But Perl 5.8.9 was released two weeks  
ago, and the perl5.8 port will likely be updated to that version  
soon. Then they are different versions. Based on past experience, I  
would guess Apple will never update the version of Perl provided in  
Panther (because they're not updating anything for Panther anymore),  
and they'll probably only update the versions in Tiger and Leopard if  
the new version fixes a security issue or some other show-stopper,  
and even then they may not do so for months. This is the whole reason  
we want MacPorts to use software provided by MacPorts, and not  
software provided by Apple in Mac OS X -- so that we're not stuck to  
whatever release schedule Apple decides to use.

We also routinely have trouble when users have already installed  
software in /usr/local and then start using MacPorts -- lots of  
software in MacPorts looks in /usr/local first and if it finds what  
it's looking for, uses that version of the software instead of the  
copy MacPorts installed, and then things often don't work right  
because the version in /usr/local is older than what we need.

The point, as others have made, is that things work best when you let  
MacPorts manage all your software for you.


From ryandesign at macports.org  Wed Dec 31 00:16:33 2008
From: ryandesign at macports.org (Ryan Schmidt)
Date: Wed, 31 Dec 2008 02:16:33 -0600
Subject: MacPorts Fail to Install GD2
In-Reply-To: <15BA7DC4-BE15-4A37-84C6-5829FB9E4790@macports.org>
References: <73f827b50812281233r22c6b9a8p4701c2244cf5e6b4@mail.gmail.com>
	<15BA7DC4-BE15-4A37-84C6-5829FB9E4790@macports.org>
Message-ID: <4F21F739-78F1-4ECF-87AF-65CA23D02A10@macports.org>


On Dec 28, 2008, at 14:38, Frank Schima wrote:

> On Dec 28, 2008, at 1:33 PM, Gundala Viswanath wrote:
>
>> In the process of installing gnuplot, it needs gd2.
>> However when I tried to install gd2 it gives the following error:
>
> [snip]
>
>> Is there a way I can fix this?
>
> I just opened a ticket about this problem:
>
> <http://trac.macports.org/ticket/17808>

It's fixed now.



From gundalav at gmail.com  Wed Dec 31 03:26:19 2008
From: gundalav at gmail.com (Gundala Viswanath)
Date: Wed, 31 Dec 2008 20:26:19 +0900
Subject: MacPorts Fail to Install GD2
In-Reply-To: <4F21F739-78F1-4ECF-87AF-65CA23D02A10@macports.org>
References: <73f827b50812281233r22c6b9a8p4701c2244cf5e6b4@mail.gmail.com>
	<15BA7DC4-BE15-4A37-84C6-5829FB9E4790@macports.org>
	<4F21F739-78F1-4ECF-87AF-65CA23D02A10@macports.org>
Message-ID: <73f827b50812310326y203483f7h1e82d3f248b015c5@mail.gmail.com>

Thanks Ryan. I can install GD2 successfully now!

- Gundala Viswanath
Jakarta - Indonesia



On Wed, Dec 31, 2008 at 5:16 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
>
> On Dec 28, 2008, at 14:38, Frank Schima wrote:
>
>> On Dec 28, 2008, at 1:33 PM, Gundala Viswanath wrote:
>>
>>> In the process of installing gnuplot, it needs gd2.
>>> However when I tried to install gd2 it gives the following error:
>>
>> [snip]
>>
>>> Is there a way I can fix this?
>>
>> I just opened a ticket about this problem:
>>
>> <http://trac.macports.org/ticket/17808>
>
> It's fixed now.
>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>

From fbartolom at gmail.com  Wed Dec 31 09:41:47 2008
From: fbartolom at gmail.com (Fabrizio Bartolomucci)
Date: Wed, 31 Dec 2008 18:41:47 +0100
Subject: New Mac user and gdk-pixbuf-2-0
Message-ID: <495BAEDB.8050809@gmail.com>

Hullo everyone,
sorry if this question has been already asked and in that case I would
be happy if someone pointed me to the answer.
I own a Mac PowerBook with MacPorts installed and since some time the
'upgrade outdated' procedure loops on the following message and I do not
know what to do:

Thanks everyone,
Fabrizio Bartolomucci

No package 'gdk-pixbuf-2.0' 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 LIBRSVG_CFLAGS
and LIBRSVG_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


Error: Unable to upgrade port: 1
--->  Activating gtk2 @2.14.5_0+x11
Error: Target org.macports.activate returned: Image error:
/opt/local/include/gail-1.0/gail/gailwidget.h is being used by the
active gail port.  Please deactivate this port first, or use the -f flag
to force the activation.
Error: The following dependencies failed to build: gtk2
Error: Unable to upgrade port: 1


From devans at macports.org  Wed Dec 31 11:30:44 2008
From: devans at macports.org (David Evans)
Date: Wed, 31 Dec 2008 11:30:44 -0800
Subject: New Mac user and gdk-pixbuf-2-0
In-Reply-To: <495BAEDB.8050809@gmail.com>
References: <495BAEDB.8050809@gmail.com>
Message-ID: <495BC864.9000708@macports.org>

Fabrizio Bartolomucci wrote:
> Hullo everyone,
> sorry if this question has been already asked and in that case I would
> be happy if someone pointed me to the answer.
> I own a Mac PowerBook with MacPorts installed and since some time the
> 'upgrade outdated' procedure loops on the following message and I do not
> know what to do:
>
> Thanks everyone,
> Fabrizio Bartolomucci
>
> No package 'gdk-pixbuf-2.0' 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 LIBRSVG_CFLAGS
> and LIBRSVG_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
>
> Error: Unable to upgrade port: 1
> --->  Activating gtk2 @2.14.5_0+x11
> Error: Target org.macports.activate returned: Image error:
> /opt/local/include/gail-1.0/gail/gailwidget.h is being used by the
> active gail port.  Please deactivate this port first, or use the -f flag
> to force the activation.
> Error: The following dependencies failed to build: gtk2
> Error: Unable to upgrade port: 1
>
Fabrizio --

Both gail and gdk-pixbuf-2.0 are now provided by gtk2.  The gail port is
obsolete and
should be removed.

Try this (as per the error message)

sudo port deactivate gail
sudo port activate gtk2
sudo port upgrade outdated

then you should be able to uninstall gail

sudo port uninstall gail