selfupdate error

2010-07-27 Thread t...@qx.net
Hello, First, great product! Thanks for your hard work! I am trying to run 'sudo port -d selfupdate' on a powerpc (pismo) running OS X 10.4.11 and encountering the following error messages captured from stderr: DEBUG: Synchronizing ports tree(s) DEBUG: /usr/bin/rsync -rtzv --delete-after rs

RE: Re: selfupdate error

2010-07-27 Thread t...@qx.net
too many moving parts to this computer stuff, but sadly, all of them seem to be mine! Best regards, Tom >--- Original Message --- >From: Ryan Schmidt[mailto:ryandes...@macports.org] >Sent : 7/27/2010 12:47:00 PM >To : t...@qx.net >Cc : macports

RE: Re: selfupdate error

2010-07-28 Thread t...@qx.net
>>--- Original Message --- >>From: Ryan Schmidt[mailto:ryandes...@macports.org] >>Sent: 7/28/2010 10:07:53 AM >>To : t...@qx.net >>Cc : macports-users@lists.macosforge.org >>Subject : RE: Re: selfupdate error >> >> >On J

RE: Re: selfupdate error

2010-07-29 Thread t...@qx.net
>>>--- Original Message --- >>>From : Ryan Schmidt[ mailto:ryandes...@macports.org ] >>>Sent : 7/28/2010 10:07:53 AM >>>To : t...@qx.net >>>Cc : macports-users@lists.macosforge.org >>>Subject : RE: Re: selfupdate error &g

Upgrade ffmpeg 0.6_0 problem

2010-07-30 Thread t...@qx.net
Hello, Tried to upgade to ffmpeg 0.6_0 and received the following: ( I did this twice. The first main.log has more stuff in it, but the ending is the same. Can provide first main.log if necessary ) Thanks ahead for any help!!! version:1 :msg:main ---> Computing dependencies for ffmpeg:info:m

RE: Upgrade ffmpeg 0.6_0 problem

2010-07-30 Thread t...@qx.net
I have sent the original email again as a means of distinguishing the difference between the error message before deactivating ffmpeg and after deactivating ffmpeg. The files were exactly the same, except as noted: version:1 :msg:main ---> Computing dependencies for ffmpeg:info:main .:debug

RE: Re: Upgrade ffmpeg 0.6_0 problem

2010-07-31 Thread t...@qx.net
>> I have sent the original email again as a means of distinguishing the >> difference between the error message before deactivating ffmpeg and after >> deactivating ffmpeg. The files were exactly the same, except as noted: > >After deactivating the old ffmpeg, did you clean ffmpeg before attemp

RE: Re: Upgrade ffmpeg 0.6_0 problem

2010-07-31 Thread t...@qx.net
that I had downloaded sometime back, but could not find 'lavutil' anywhere on my computer. I can find 'libavutil' a bunch of places. Is this a spelling thing? >--- Original Message --- >From: t...@qx.net[mailto:t...@qx.net] >Sent: 7/31/20

RE: Re: Upgrade ffmpeg 0.6_0 problem

2010-07-31 Thread t...@qx.net
yan Schmidt[mailto:ryandes...@macports.org] >Sent: 7/31/2010 4:26:47 PM >To : t...@qx.net >Cc : macports-users@lists.macosforge.org >Subject : RE: Re: Upgrade ffmpeg 0.6_0 problem > >On Jul 31, 2010, at 12:25, t...@qx.net wrote: > As a follow-up, just for something to do, I

trac.macports.org/ticket/25815

2010-08-01 Thread t...@qx.net
The ticket seemed to be closed and fixed, so I am posting here. I am unfamiliar with the ticket process, so if I am doing this wrong, please provide guidance. I did what I thought the ticket said to do: -- fmt_deps = sed -e 's;^\(.*\)\.

libvpx

2010-08-03 Thread t...@qx.net
Hello, Well, it is certainly a new error for me! Virtual Memory exhausted! Girls and Guys, all of this is out of my league. Just tell me what to do I will do it. After seeing the ticket 25907 closed and a few comments of success, I did the following. It failed the first time just as below so

New user, port selfupdate error

2010-03-19 Thread t...@qx.net
Hello, I am attempting to use macports for the first time. I am not a computer science person, but do have limited experience with gcc and configure/make installations. I installed macports 1.7 from a disk image, with a successful completion message. I then tried the second step of % sudo p

RE: Re: New user, port selfupdate error

2010-03-20 Thread t...@qx.net
orts.build org.macports.destroot org.macports.install Error: The following dependencies failed to build: mp4v2 Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> My thanks to everybody for your support!!!! Tom --- Origina

RE: Re: New user, port selfupdate error

2010-03-21 Thread t...@qx.net
cports.org] Sent: 3/20/2010 2:21:29 PM To : t...@qx.net Cc : macports-users@lists.macosforge.org Subject : RE: Re: New user, port selfupdate error On Mar 20, 2010, at 12:18, t...@qx.net wrote: > As background, I have been trying to install faac from a source download, and > hav

RE: Re: New user, port selfupdate error

2010-03-22 Thread t...@qx.net
I've got no teeth and am headed to the shop for a though honing, but SUCCESS! FAAC installed! Many thanks, Tom --- Original Message --- >From: Ryan Schmidt[mailto:ryandes...@macports.org] Sent: 3/22/2010 6:18:20 AM To : t...@qx.net Cc : macpor

ffmpeg --disable-altivec option

2010-03-28 Thread t...@qx.net
Hello, I need to install ffmpeg with the --disable-altivec option. Is that possible? Best regards to all, Tom ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

RE: Re: ffmpeg --disable-altivec option

2010-03-28 Thread t...@qx.net
>>--- Original Message --- >>From: Ryan Schmidt[mailto:ryandes...@macports.org] >>Sent: 3/28/2010 12:48:07 PM >>To : t...@qx.net >>Cc : macports-users@lists.macosforge.org >>Subject : RE: Re: ffmpeg --disable-altivec option >>

RE: Re: ffmpeg --disable-altivec option

2010-03-28 Thread t...@qx.net
legal instruction.' What should I have done? Sorry for my confusion and thanks for your help, Tom >--- Original Message --- >From: Joshua Root[mailto:j...@macports.org] >Sent: 3/28/2010 3:03:24 PM >To : t...@qx.net >Cc : macports-users@lists.macosforge.org

RE: Re: ffmpeg --disable-altivec option

2010-03-28 Thread t...@qx.net
Success! Thanks Josh! My apologies for not understanding the port command usages better! Best regards, Tom >--- Original Message --- >From: Joshua Root[mailto:j...@macports.org] >Sent: 3/28/2010 8:45:47 PM >To : t...@qx.net >Cc :