selfupdate error

[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 
rsync://rsync.macports.org/release/ports/ 
/opt/local/var/macports/sources/rsync.macports.org/release/ports
DEBUG: MacPorts sources location: 
/opt/local/var/macports/sources/rsync.macports.org/release/base
DEBUG: Rebuilding and reinstalling MacPorts if needed
DEBUG: Permissions OK
DEBUG: Error installing new MacPorts base: shell command "cd 
/opt/local/var/macports/sources/rsync.macports.org/release/base && ./configure 
--
prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root 
--with-install-group=admin --with-directory-mode=0755 --enable-
readline && make && make install" returned error 2
while executing
"macports::selfupdate [array get global_options]"
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-tclpackage=/Library/Tcl --with-
install-user=root --with-install-group=admin --with-directory-mode=0755 
--enable-readline && make && make install" returned error 2

Attached to this email is the stderr output.

Can anybody help?

Thanks and best regards,
Tom



selfupdatestdout
Description: selfupdatestdout
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

RE: Re: selfupdate error

[t...@qx.net]

Thanks!  I do not know why things are the way they are, but a 'which make' 
revealed '/opt/local/bin/make', which points to gmake in the same 
location.  There was nothing in /usr/bin, so I created a link to 
'/opt/local/bin/make', and selfupdate ran fine.  There are 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-users@lists.macosforge.org
>Subject : RE: Re: selfupdate error
>
 >On Jul 27, 2010, at 10:54, t...@qx.net wrote:

> 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:

[snip]

[from attached logfile:]

> /bin/sh: line 3: make: command not found

Does "make" exist in /usr/bin? Do you have Xcode installed? If you don't, 
install Xcode 2.5. If you do, reinstall Xcode 2.5 :) making sure not to 
deselect 
the command-line development option.




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

RE: Re: selfupdate error

[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 Jul 27, 2010, at 13:03, t...@qx.net wrote:
>
>> Ryan Schmidt wrote:
>
>> 
>>> On Jul 27, 2010, at 10:54, t...@qx.net wrote:
>>>
>>>> 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:
>>>
>>> [snip]
>>>
>>>[from attached logfile:]
>>> 
>>>> /bin/sh: line 3: make: command not found
>>> 
>>> Does "make" exist in /usr/bin? Do you have Xcode installed? If you don't, 
>>> install Xcode 2.5. If you do, reinstall Xcode 2.5 :) making sure not to 
deselect 
>>> the command-line development option.
>> 
>>Thanks!  I do not know why things are the way they are, but a 'which make' 
>>revealed '/opt/local/bin/make', which points to gmake in the same 
>> location.  There was nothing in /usr/bin, so I created a link to 
>> '/opt/local/bin/make', and selfupdate ran fine.  There are too many moving 
>> parts to 
this 
>> computer stuff, but sadly, all of them seem to be mine!
>
>That's probably not a good idea
>You should remove the /usr/bin/make symlink you just created, and instead, 
>install Xcode properly, as I showed above.

Will do!

>
>You should also not have a file /opt/local/bin/make; you should only have 
>/opt/local/bin/gmake, as provided by the gmake port.
>Do you have any idea why you have a file /opt/local/bin/make?

No.

>What does "port provides /opt/local/bin/make" say? If it says it is not 
>provided by a MacPorts port, delete it as well.

It said not provided by Macports.  Will delete.

>
>Using a version of make for MacPorts that is not the version provided by Xcode 
>will likely cause you problems with some ports in the future, so it's 
best to clean this up now.

Will do!
Thanks for the follow-up!

>
>
>

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

RE: Re: selfupdate error

[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 Jul 27, 2010, at 13:03, t...@qx.net wrote: 
>> 
>>> Ryan Schmidt wrote: 
>> 
>>> 
>>>> On Jul 27, 2010, at 10:54, t...@qx.net wrote: 
>>>> 
>>>>> 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: 
>>>> 
>>>> [snip] 
>>>> 
>>>>[from attached logfile:] 
>>>> 
>>>>> /bin/sh: line 3: make: command not found 
>>>> 
>>>> Does "make" exist in /usr/bin? Do you have Xcode installed? If you don't, 
>>>> install Xcode 2.5. If you do, reinstall Xcode 2.5 :) making sure not to 
>deselect 
>>>> the command-line development option. 
>>> 
>>>Thanks! I do not know why things are the way they are, but a 'which make' 
>>>revealed '/opt/local/bin/make', which points to gmake in the same 
>>> location. There was nothing in /usr/bin, so I created a link to 
>>> '/opt/local/bin/make', and selfupdate ran fine. There are too many moving 
>>> parts to 
>this 
>>> computer stuff, but sadly, all of them seem to be mine! 
>> 
>>That's probably not a good idea 
>>You should remove the /usr/bin/make symlink you just created, and instead, 
>>install Xcode properly, as I showed above. 
>
>Will do! 

Reinstalled Xcode 2.5.  Doing this allowed some light to filter thru the gray 
matter, so here is what I have now and and a somewhat blurred account of 
what happened, with one possibly off subject question:

Before MacPorts I wanted ffmpeg, so I downloaded a zip file and started 
learning the configure/make process.  Questions about errors lead to the 
suggestions that I update Xcode from 2.0 to 2.5, which I think lead to the 
enlightenment that ffmpeg could only be compiled with 'make 3.81'.  Since 
Xcode 2.5 has 'make 3.80', I continued my learning process by downloading GNU 
Make 3.81 source package and did configure/make which by default 
put the gmake in /usr/local/bin.  Out smarting my self I created a link in 
/usr/bin to my new gmake.  A few option/variant solutions later I had my 
ffmpeg skeleton (few included libs).  Having learned so much I immediately 
wanted a full blown version of ffmpeg, so I went about learning how I could 
get one without all the headaches of the basic installation, and came across 
MacPorts.  A few headaches later I had a Macports version of ffmpeg, with 
the /opt/local/bin search at the beginning of my path.  Please with myself I 
merrily went on my way.  PROBABLY, somewhere alone the way to self 
adulation, I needed something to see a 'make' somewhere and created the make -> 
gmake link in /opt/local/bin.  As it stands now I have /usr/bin/ 
make -> /usr/bin/gnumake, which is 3.80.  I also have /opt/local/bin/gmake, 
which is 3.81.  When I do 'which make' I see /usr/bin/make.  I assume 
that MacPorts knows to look in /opt/local/bin for what it wants.  I hope this 
is the way it should be.

My question:  The only reason that I have Xcode is to have a compiler for my 
hobbyist level C utilities, AND to meet the MacPorts requirement.  From 
my hobbyist viewpoint, I do not need the 1.5Gig of development stuff under the 
/Developer directory.  I could really use the space.  Can I delete the 
/Developer directory and still have MacPorts work?

>
>> 
>>You should also not have a file /opt/local/bin/make; you should only have 
>>/opt/local/bin/gmake, as provided by the gmake port. 
>>Do you have any idea why you have a file /opt/local/bin/make? 
>
>No. 
>
>>What does "port provides /opt/local/bin/make" say? If it says it is not 
>>provided by a MacPorts port, delete it as well. 
>
>It said not provided by Macports. Will delete. 
>
>> 
>>Using a version of make for MacPorts that is not the version provided by 
>>Xcode will likely cause you problems with some ports in the future, so it's 
>best to clean this up now. 
>
>Will do! 
>Thanks for the follow-up! 
>
>> 
>> 
>> 
>
>___ 
>macports-users mailing list 
>macports-users@lists.macosforge.org 
>http://lists.macosforge.org/mailman/listinfo.cgi/macports-users 

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Upgrade ffmpeg 0.6_0 problem

[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:main .:debug:main 
Searching for dependency: gmake
:debug:main Found Dependency: receipt exists for gmake
:debug:main Searching for dependency: lame
:debug:main Found Dependency: receipt exists for lame
:debug:main Searching for dependency: libvorbis
:debug:main Found Dependency: receipt exists for libvorbis
:debug:main Searching for dependency: libogg
:debug:main Found Dependency: receipt exists for libogg
:debug:main Searching for dependency: libtheora
:debug:main Found Dependency: receipt exists for libtheora
:debug:main Searching for dependency: dirac
:debug:main Found Dependency: receipt exists for dirac
:debug:main Searching for dependency: schroedinger
:debug:main Found Dependency: receipt exists for schroedinger
:debug:main Searching for dependency: faac
:debug:main Found Dependency: receipt exists for faac
:debug:main Searching for dependency: faad2
:debug:main Found Dependency: receipt exists for faad2
:debug:main Searching for dependency: speex
:debug:main Found Dependency: receipt exists for speex
:debug:main Searching for dependency: XviD
:debug:main Found Dependency: receipt exists for XviD
:debug:main Searching for dependency: x264
:debug:main Found Dependency: receipt exists for x264
:debug:main Searching for dependency: libsdl
:debug:main Found Dependency: receipt exists for libsdl
:debug:main Searching for dependency: bzip2
:debug:main Found Dependency: receipt exists for bzip2
:debug:main Searching for dependency: zlib
:debug:main Found Dependency: receipt exists for zlib
:msg:main 
:debug:main Executing org.macports.main (ffmpeg)
:debug:main Skipping completed org.macports.fetch (ffmpeg)
:debug:main Skipping completed org.macports.checksum (ffmpeg)
:debug:main setting option extract.cmd to /usr/bin/bzip2
:debug:main Skipping completed org.macports.extract (ffmpeg)
:debug:main Skipping completed org.macports.patch (ffmpeg)
:debug:main Skipping completed org.macports.configure (ffmpeg)
:msg:main --->  Building ffmpeg
:debug:build build phase started at Fri Jul 30 10:32:33 EDT 2010
:debug:build Executing org.macports.build (ffmpeg)
:debug:build Environment: CPATH='/opt/local/include' 
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/wor
k/.CC_PRINT_OPTIONS' LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES' 
MACOSX_DEPLOYMENT_TARGET='10.4'
:debug:build Assembled command: 'cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/ffmpeg-0.6"
 && gmake 
all'
:info:build LD  libavutil/libavutil.50.dylib
:info:build ld: /opt/local/lib/libavutil.dylib can't be linked because it has 
the same install_name (/opt/local/lib/libavutil.dylib) as the output
:info:build ld: warning can't open dynamic library: 
/opt/local/lib/libx264.93.dylib referenced from: /opt/local/lib/libavutil.dylib 
(checking for 
undefined symbols may be affected) (No such file or directory, errno = 2)
:info:build /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: internal link 
edit command failed
:info:build gmake: *** [libavutil/libavutil.50.dylib] Error 1
:info:build shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/ffmpeg-0.6"
 && gmake 
all " returned error 2
:error:build Target org.macports.build returned: shell command failed
:debug:build Backtrace: shell command failed
while executing
"command_exec build"
(procedure "portbuild::build_main" line 8)
invoked from within
"$procedure $targetname"
:info:build Warning: the following items did not execute (for ffmpeg): 
org.macports.destroot org.macports.build
:notice:build Log for ffmpeg is at: 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/main.log


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

RE: Upgrade ffmpeg 0.6_0 problem

[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:main 
Searching for dependency: gmake
:debug:main Found Dependency: receipt exists for gmake
:debug:main Searching for dependency: lame
:debug:main Found Dependency: receipt exists for lame
:debug:main Searching for dependency: libvorbis
:debug:main Found Dependency: receipt exists for libvorbis
:debug:main Searching for dependency: libogg
:debug:main Found Dependency: receipt exists for libogg
:debug:main Searching for dependency: libtheora
:debug:main Found Dependency: receipt exists for libtheora
:debug:main Searching for dependency: dirac
:debug:main Found Dependency: receipt exists for dirac
:debug:main Searching for dependency: schroedinger
:debug:main Found Dependency: receipt exists for schroedinger
:debug:main Searching for dependency: faac
:debug:main Found Dependency: receipt exists for faac
:debug:main Searching for dependency: faad2
:debug:main Found Dependency: receipt exists for faad2
:debug:main Searching for dependency: speex
:debug:main Found Dependency: receipt exists for speex
:debug:main Searching for dependency: XviD
:debug:main Found Dependency: receipt exists for XviD
:debug:main Searching for dependency: x264
:debug:main Found Dependency: receipt exists for x264
:debug:main Searching for dependency: libsdl
:debug:main Found Dependency: receipt exists for libsdl
:debug:main Searching for dependency: bzip2
:debug:main Found Dependency: receipt exists for bzip2
:debug:main Searching for dependency: zlib
:debug:main Found Dependency: receipt exists for zlib
:msg:main 
:debug:main Executing org.macports.main (ffmpeg)
:debug:main Skipping completed org.macports.fetch (ffmpeg)
:debug:main Skipping completed org.macports.checksum (ffmpeg)
:debug:main setting option extract.cmd to /usr/bin/bzip2
:debug:main Skipping completed org.macports.extract (ffmpeg)
:debug:main Skipping completed org.macports.patch (ffmpeg)
:debug:main Skipping completed org.macports.configure (ffmpeg)
:msg:main --->  Building ffmpeg
:debug:build build phase started at Fri Jul 30 10:32:33 EDT 2010
:debug:build Executing org.macports.build (ffmpeg)
:debug:build Environment: CPATH='/opt/local/include' 
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/wor
k/.CC_PRINT_OPTIONS' LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES' 
MACOSX_DEPLOYMENT_TARGET='10.4'
:debug:build Assembled command: 'cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/ffmpeg-0.6"
 && gmake 
all'
:info:build LD  libavutil/libavutil.50.dylib
EXACTLY THE SAME TO HERE (except for the time above)


BEFORE DEACTIVATION FFMPEG
:info:build ld: /opt/local/lib/libavutil.dylib can't be linked because it has 
the same install_name (/opt/local/lib/libavutil.dylib) as the output
:info:build ld: warning can't open dynamic library: 
/opt/local/lib/libx264.93.dylib referenced from: /opt/local/lib/libavutil.dylib 
(checking for 
undefined symbols may be affected) (No such file or directory, errno = 2)
:info:build /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: internal link 
edit command failed
BEFORE DEACTIVATION FFMPEG


AFTER DEACTIVATION FFMPEG
:info:build /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: can't locate 
file for: -lavutil
:info:build /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: file: 
-lavutil is not an object file (not allowed in a library)
AFTER DEACTIVATION FFMPEG


EXACTLY THE SAME AFTER HERE
:info:build gmake: *** [libavutil/libavutil.50.dylib] Error 1
:info:build shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/ffmpeg-0.6"
 && gmake 
all " returned error 2
:error:build Target org.macports.build returned: shell command failed
:debug:build Backtrace: shell command failed
while executing
"command_exec build"
(procedure "portbuild::build_main" line 8)
invoked from within
"$procedure $targetname"
:info:build Warning: the following items did not execute (for ffmpeg): 
org.macports.destroot org.macports.build
:notice:build Log for ffmpeg is at: 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmp

RE: Re: Upgrade ffmpeg 0.6_0 problem

[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 attempting to 
>build the new ffmpeg? If not, please do that.

I did clean after deactivating.  I even went so far as to uninstall the old 
version and clean the new version and start from scratch.  Received the same 
messages as after deactivating.  I am sitting here now with no ffmpeg on my 
machine, but all the dependents are still here.  Thanks for your help.
 


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

RE: Re: Upgrade ffmpeg 0.6_0 problem

[t...@qx.net]

As a follow-up, just for something to do, I uninstalled/cleaned ffmpeg again, 
uninstalled Xcode 2.5, Shutdown my computer ( because I read that 
somewhere ), Redownloaded Xcode 2.5 and Installed again, Shutdown the computer 
again, restarted and did 'sudo port -d selfupdate' ( just for grins ), 
and 'sudo port install ffmpeg' again with the same result.  I don't pretend to 
understand how all this fits together, but from the error message it is 
almost as if something is misspelled somewhere.  I found a reference to 
'-lavutil' in a ffmpegSDKtutorial.txt 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/2010 9:33:35 AM
>To  : macports-users@lists.macosforge.org
>Cc  : 
>Subject : RE: Re: Upgrade ffmpeg 0.6_0 problem
>
 >>> 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 attempting to 
>build the new ffmpeg? If not, please do that.

I did clean after deactivating.  I even went so far as to uninstall the old 
version and clean the new version and start from scratch.  Received the same 
messages as after deactivating.  I am sitting here now with no ffmpeg on my 
machine, but all the dependents are still here.  Thanks for your help.
 


___
macports-users mailing list
macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macports-users 


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

RE: Re: Upgrade ffmpeg 0.6_0 problem

[t...@qx.net]

Now I have a new error.  I have attached three files.  One is the terminal 
output from the time I started after receiving this post.  One is the main.log 
indicated by the terminal output.  The main.log suggested that I look at 
config.err, which I have included also.  This error occurred while attempting 
to 
install a new ffmpeg dependency, libvpx.  While looking at the main.log I have 
already noticed one thing that is going to give me trouble, that is a 
comment about activating altivec.  My ppc is pre-altivec ( which I learned the 
first time I installed ffmpeg ) and needs altivec to be disabled.

Do you want me to file a ticket on this error or the first one?  I still have 
information on the first error, but with the changes, I don't know how valid it 
is.  Thank you for your help.  Are not computers fun!?

>--- Original Message ---
>From: Ryan 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 uninstalled/cleaned ffmpeg again, 
> uninstalled Xcode 2.5, Shutdown my computer ( because I read that 
> somewhere ), Redownloaded Xcode 2.5 and Installed again, Shutdown the 
> computer again, restarted and did 'sudo port -d selfupdate' ( just for grins 
), 
> and 'sudo port install ffmpeg' again with the same result.  I don't pretend 
> to understand how all this fits together, but from the error message it is 
> almost as if something is misspelled somewhere.  I found a reference to 
> '-lavutil' in a ffmpegSDKtutorial.txt 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?

The command "-lavutil" means "please link with the library libavutil.dylib", so 
that seems correct enough.

I cannot reproduce this problem today on Tiger or Snow Leopard. My log says I 
did have this problem yesterday on Snow Leopard, but now I don't, and 
of course I didn't save the log from when it failed. :/ If you could file a 
ticket with the complete log showing the failure that should be helpful in 
figuring out what's happening differently for you. Be sure to "sudo port 
selfupdate" first because an unrelated fix was just committed to ffmpeg.



# ./configure --prefix=/opt/local --enable-vp8 --enable-psnr --enable-postproc 
--enable-multithread --enable-runtime-cpu-detect --disable-install-docs
Configuring selected codecs
  enabling vp8_encoder
  enabling vp8_decoder
Configuring for target 'universal-darwin8-gcc'
  enabling universal
check_cflags -O3
check_cc -O3
BEGIN /tmp/vpx-conf-10933-11745.c
1   int x;
END /tmp/vpx-conf-10933-11745.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -c -o /tmp/vpx-conf-10933-10061.o 
/tmp/vpx-conf-10933-11745.c
check_cc
BEGIN /tmp/vpx-conf-10933-11745.c
1   unsigned int e = 'O'<<24 | '2'<<16 | 'B'<<8 | 'E';
END /tmp/vpx-conf-10933-11745.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -c -o /tmp/vpx-conf-10933-10061.o 
/tmp/vpx-conf-10933-11745.c
check_header pthread.h
check_cpp
BEGIN /tmp/vpx-conf-10933-11745.c
1   #include "pthread.h"
2   int x;
END /tmp/vpx-conf-10933-11745.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -E -o /tmp/vpx-conf-10933-10061.o 
/tmp/vpx-conf-10933-11745.c
check_cflags -Wall
check_cc -Wall
BEGIN /tmp/vpx-conf-10933-11745.c
1   int x;
END /tmp/vpx-conf-10933-11745.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -Wall -c -o /tmp/vpx-conf-10933-10061.o 
/tmp/vpx-conf-10933-11745.c
check_cflags -Wdeclaration-after-statement
check_cc -Wdeclaration-after-statement
BEGIN /tmp/vpx-conf-10933-11745.c
1   int x;
END /tmp/vpx-conf-10933-11745.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -Wall -Wdeclaration-after-statement -c -o 
/tmp/vpx-conf-10933-10061.o /tmp/vpx-conf-10933-11745.c
check_cflags -Wdisabled-optimization
check_cc -Wdisabled-optimization
BEGIN /tmp/vpx-conf-10933-11745.c
1   int x;
END /tmp/vpx-conf-10933-11745.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -Wall -Wdeclaration-after-statement 
-Wdisabled-optimization -c -o /tmp/vpx-conf-10933-10061.o 
/tmp/vpx-conf-10933-11745.c
check_cflags -Wpointer-arith
check_cc -Wpointer-arith
BEGIN /tmp/vpx-conf-10933-11745.c
1   int x;
END /tmp/

trac.macports.org/ticket/25815

[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;^\(.*\)\.o;\$(dir \$@)\1\$(suffix \$<).o \$@;' #hide
Just change this to

fmt_deps = sed -e 's;^\(.*\)\.ox;\$(dir \$@)\1\$(suffix \$<).o \$@;' #hide


sudo port clean libvpx

sudo port fetch libvpx

sudo port extract libvpx

cd to the staging directory where the port was being built - this directory 
should have been shown in one of the error messages. On my system it was 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/work/libvpx-0.9.1/

then:

cd build/make

edit the configure.sh file in that folder to change the line as shown above.

sudo port build libvpx
sudo port install libvpx
--

and received the following error:

--
22:30> sudo port build libvpx
--->  Computing dependencies for libvpx
--->  Configuring libvpx
Error: Target org.macports.configure returned: configure failure: shell command 
failed
Log for libvpx is at: 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/main.log
Error: Status 1 encountered during processing.
To report a bug, see 
--

Attached is the main.log and the config.err

Thanks for your help, Tom


main.log
Description: main.log
# ./configure --prefix=/opt/local --enable-vp8 --enable-psnr --enable-postproc 
--enable-multithread --enable-runtime-cpu-detect --disable-install-docs
Configuring selected codecs
  enabling vp8_encoder
  enabling vp8_decoder
Configuring for target 'universal-darwin8-gcc'
  enabling universal
check_cflags -O3
check_cc -O3
BEGIN /tmp/vpx-conf-226-3241.c
1   int x;
END /tmp/vpx-conf-226-3241.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -c -o /tmp/vpx-conf-226-10397.o 
/tmp/vpx-conf-226-3241.c
check_cc
BEGIN /tmp/vpx-conf-226-3241.c
1   unsigned int e = 'O'<<24 | '2'<<16 | 'B'<<8 | 'E';
END /tmp/vpx-conf-226-3241.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -c -o /tmp/vpx-conf-226-10397.o 
/tmp/vpx-conf-226-3241.c
check_header pthread.h
check_cpp
BEGIN /tmp/vpx-conf-226-3241.c
1   #include "pthread.h"
2   int x;
END /tmp/vpx-conf-226-3241.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -E -o /tmp/vpx-conf-226-10397.o 
/tmp/vpx-conf-226-3241.c
check_cflags -Wall
check_cc -Wall
BEGIN /tmp/vpx-conf-226-3241.c
1   int x;
END /tmp/vpx-conf-226-3241.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -Wall -c -o /tmp/vpx-conf-226-10397.o 
/tmp/vpx-conf-226-3241.c
check_cflags -Wdeclaration-after-statement
check_cc -Wdeclaration-after-statement
BEGIN /tmp/vpx-conf-226-3241.c
1   int x;
END /tmp/vpx-conf-226-3241.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -Wall -Wdeclaration-after-statement -c -o 
/tmp/vpx-conf-226-10397.o /tmp/vpx-conf-226-3241.c
check_cflags -Wdisabled-optimization
check_cc -Wdisabled-optimization
BEGIN /tmp/vpx-conf-226-3241.c
1   int x;
END /tmp/vpx-conf-226-3241.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -Wall -Wdeclaration-after-statement 
-Wdisabled-optimization -c -o /tmp/vpx-conf-226-10397.o /tmp/vpx-conf-226-3241.c
check_cflags -Wpointer-arith
check_cc -Wpointer-arith
BEGIN /tmp/vpx-conf-226-3241.c
1   int x;
END /tmp/vpx-conf-226-3241.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -Wall -Wdeclaration-after-statement 
-Wdisabled-optimization -Wpointer-arith -c -o /tmp/vpx-conf-226-10397.o 
/tmp/vpx-conf-226-3241.c
check_cflags -Wtype-limits
check_cc -Wtype-limits
BEGIN /tmp/vpx-conf-226-3241.c
1   int x;
END /tmp/vpx-conf-226-3241.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -Wall -Wdeclaration-after-statement 
-Wdisabled-optimization -Wpointer-arith -Wtype-limits -c -o 
/tmp/vpx-conf-226-10397.o /tmp/vpx-conf-226-3241.c
cc1: error: unrecognized command line option "-Wtype-limits"
check_cflags -Wcast-qual
check_cc -Wcast-qual
BEGIN /tmp/vpx-conf-226-3241.c
1   int x;
END /tmp/vpx-conf-226-3241.c
/usr/bin/gcc-4.0 -O2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk 
-mmacosx-version-min=10.4 -O3 -Wall -Wdeclaration-after-statement 
-Wdisabled-optimization -Wpointer-arith -Wcast-qual -c -o 
/tmp/vpx-

libvpx

[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 I restarted my 
computer, thinking I had done something to exhaust my virtual memory.  Got the 
same error the second time.

--

Last login: Wed Aug  4 00:16:56 on console
Welcome to Darwin!
0:18> sudo port -d selfupdate
Password:
--->  Updating the ports tree
DEBUG: Synchronizing ports tree(s)
Synchronizing local ports tree from rsync://rsync.macports.org/release/ports/
DEBUG: /usr/bin/rsync -rtzv --delete-after '--exclude=/PortIndex*' 
rsync://rsync.macports.org/release/ports/ 
/opt/local/var/macports/sources/rsync.macports.org/release/ports
receiving file list ... done
./
multimedia/ffmpeg/
multimedia/libvpx/
deleting multimedia/ffmpeg/work

sent 71 bytes  received 468248 bytes  40723.39 bytes/sec
total size is 26525873  speedup is 56.64
Creating port index in 
/opt/local/var/macports/sources/rsync.macports.org/release/ports

Total number of ports parsed:   0 
Ports successfully parsed:  0 
Ports failed:   0 
Up-to-date ports skipped:   7265

DEBUG: MacPorts sources location: 
/opt/local/var/macports/sources/rsync.macports.org/release/base
--->  Updating MacPorts base sources using rsync
receiving file list ... done

sent 36 bytes  received 6810 bytes  2738.40 bytes/sec
total size is 2879032  speedup is 420.54
MacPorts base version 1.9.1 installed,
DEBUG: Rebuilding and reinstalling MacPorts if needed
MacPorts base version 1.9.1 downloaded.
--->  MacPorts base is already the latest version
DEBUG: Setting MacPorts sources ownership to root

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated
0:20> sudo port clean --all libvpx
--->  Cleaning libvpx
0:21> sudo port install libvpx
--->  Computing dependencies for libvpx
--->  Fetching libvpx
--->  Attempting to fetch libvpx-0.9.1.tar.bz2 from 
http://webm.googlecode.com/files/
--->  Verifying checksum(s) for libvpx
--->  Extracting libvpx
--->  Applying patches to libvpx
--->  Configuring libvpx
--->  Building libvpx
--->  Staging libvpx into destroot
Error: Target org.macports.destroot returned: shell command failed
Log for libvpx is at: 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/main.log
Error: Status 1 encountered during processing.
To report a bug, see 
0:25>
-

The full main.log is 320KB, so I am just going to include the last few lines 
below.

-
:debug:destroot destroot phase started at Wed Aug  4 00:25:07 EDT 2010
:debug:destroot Executing org.macports.destroot (libvpx)
:debug:destroot Environment: CPATH='/opt/local/include' 
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/work
/.CC_PRINT_OPTIONS' LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES' 
MACOSX_DEPLOYMENT_TARGET='10.4'
:debug:destroot Assembled command: 'cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/work/libvpx-0.9.1"
 && 
/usr/bin/make install 
DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/work/destroot'
:info:destroot make[1]: *** virtual memory exhausted.  Stop.
:info:destroot make: *** [.DEFAULT] Error 2
:info:destroot shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/work/libvpx-0.9.1"
 && 
/usr/bin/make install 
DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/work/destroot
 " 
returned error 2
:error:destroot Target org.macports.destroot returned: shell command failed
:debug:destroot Backtrace: shell command failed
while executing
"command_exec destroot"
(procedure "portdestroot::destroot_main" line 2)
invoked from within
"$procedure $targetname"
:info:destroot Warning: the following items did not execute (for libvpx): 
org.macports.activate org.macports.destroot org.macports.install
:notice:destroot Log for libvpx is at: 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/main.log
-

Thanks for your help!  Tom


___
macports-users mailing list
macports-users@lists.macosforge.or

New user, port selfupdate error

[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 port -v selfupdate

receiving the error shown in the below partial terminal output.

My system is Mac PowerPC 750 ( pismo ) running OS X 10.4.11.
Darwin Kernel Version 8.11.0
Xcode 2.5
gcc 4.0.1
GNU make 3.81

-
I have also tried the following, with the current port version 1.7, and 
received the indicated Error:

% cd /opt/local/bin/portslocation/dports/faac
% sudo port install faac
Password:
Error: Unable to execute port: invalid command name "livecheck.type"

--
Any help will be greatly appreciated!

Best regards,
Tom

The following is the partial selfupdate terminal output: 
.
.
.
configure: creating ./config.status
config.status: creating src/programs/daemondo/Makefile
config.status: creating Doxyfile
config.status: creating Makefile
config.status: creating Mk/macports.autoconf.mk
config.status: creating doc/prefix.mtree
config.status: creating doc/macosx.mtree
config.status: creating doc/macports.conf
config.status: creating portmgr/freebsd/Makefile
config.status: creating portmgr/fedora/macports.spec
config.status: creating src/Makefile
config.status: creating src/macports1.0/macports_autoconf.tcl
config.status: creating src/port1.0/port_autoconf.tcl
config.status: creating src/registry1.0/registry_autoconf.tcl
config.status: creating src/programs/Makefile
config.status: creating src/macports1.0/macports_fastload.tcl
config.status: creating setupenv.bash
config.status: creating src/pkg_mkindex.sh
config.status: creating src/config.h
sh: line 1: make: command not found
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-tclpackage=/Library/Tcl --with-
install-user=root --with-install-group=admin --with-directory-mode=0755 && make 
&& make install" returned error 127
Command output: checking for Tcl public headers... /usr/include
checking for tclsh... /usr/bin/tclsh
checking for Tcl package directory... /Library/Tcl
checking whether tclsh was compiled with threads... yes
checking for curl-config... /usr/bin/curl-config
checking for Tcl Thread package... yes
checking for sqlite3_open in -lsqlite3... yes
checking for Tcl sqlite3 location... /usr/lib/sqlite3
checking how to build libraries... shared
checking that any existing MacPorts install can be upgraded... yes
configure: creating ./config.status
config.status: creating src/programs/daemondo/Makefile
config.status: creating Doxyfile
config.status: creating Makefile
config.status: creating Mk/macports.autoconf.mk
config.status: creating doc/prefix.mtree
config.status: creating doc/macosx.mtree
config.status: creating doc/macports.conf
config.status: creating portmgr/freebsd/Makefile
config.status: creating portmgr/fedora/macports.spec
config.status: creating src/Makefile
config.status: creating src/macports1.0/macports_autoconf.tcl
config.status: creating src/port1.0/port_autoconf.tcl
config.status: creating src/registry1.0/registry_autoconf.tcl
config.status: creating src/programs/Makefile
config.status: creating src/macports1.0/macports_fastload.tcl
config.status: creating setupenv.bash
config.status: creating src/pkg_mkindex.sh
config.status: creating src/config.h
sh: line 1: make: command not found

% 

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

RE: Re: New user, port selfupdate error

[t...@qx.net]

First, I have just realized that I have been replying to the mailing list 
incorrectly.  The error occurred because I have been using the ffmpeg mailing 
list 
and when one replies to that list, the mailing list email address automatically 
goes in the To: box, at least on my system.  I have been replying directly 
to those that replyed to my needs, and not the mailing list.   My mistake, my 
apologies.

So, to Richard DeLaurell, thanks for your reply.  I meant -d, but typed -v.  
Sorry!

Next, to Frank Schima, it seems I should not mention the 'other site', so 
hopefully you got my email with the requested information.

As background, I have been trying to install faac from a source download, and 
have not been able to get any help with the problem I have 
encountered. Continued web searching lead me to a mention of installing with 
'the other site', which lead me to the 'other sites' web site. I then just 
followed the instructions. I will run port uninstall and then find the latest 
source and try that. As for your other question, which make? ==> 
/usr/local/bin/make I installed this ( 3.81 ) from a source download to replace 
3.80, a requirement for installing ffmpeg  Thanks for your help! 

Now, to Ryan,

I followed Frank's guidance to install 1.8.2, which I have installed, over 1.7. 
 I initially thought about doing port uninstall for 1.7, but not 
knowing that I was dealing with two different 'port' sites, I decided that 
1.8.2 fit in the update category and that uninstall should not be necessary.  
Was that a mistake?   port version shows 1.8.2, and it seemed to run once I got 
the make binary in it's path.

My problem now is that I received an Error when I tried sudo port install 
faac   which I then reexecuted with the -d flag and saved the output.  It 
is 
unclear whether I should go directly to the 
<http://guide.macports.org/#project.tickets> or put the Error on this mailing 
list?  I will list the Error in 
this email, but if I should go to the bug site, I will do that also.  The 
Error:

.
.
.
Usage: /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool -dynamic [-] file 
[...] [-filelist listfile[,dirname]] [-arch_only arch] [-o output] [-
install_name name] [-compatibility_version #] [-current_version #] [-seg1addr 
0x#] [-segs_read_only_addr 0x#] [-segs_read_write_addr 0x#] [-
seg_addr_table ] [-seg_addr_table_filename ] 
[-all_load] [-noall_load]
make: *** [libmp4v2.la] Error 1
Error: Target org.macports.build returned: shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_mp4v2/work/mp4v2-1.9.1"
 && 
/opt/local/bin/make -j1 all " returned error 2
DEBUG: Backtrace: shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_mp4v2/work/mp4v2-1.9.1"
 && 
/opt/local/bin/make -j1 all " returned error 2
while executing
"command_exec build"
(procedure "portbuild::build_main" line 9)
invoked from within
"$procedure $targetname"
Warning: the following items did not execute (for mp4v2): org.macports.activate 
org.macports.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



--- Original Message ---
>From: Ryan Schmidt[mailto:ryandes...@macports.org]
Sent: 3/20/2010 4:09:57 AM
To  : t...@qx.net
Cc  : macports-users@lists.macosforge.org
Subject : RE: Re: New user, port selfupdate error

 On Mar 19, 2010, at 17:15, t...@qx.net wrote:

> 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 port -v selfupdate
> 
> receiving the error shown in the below partial terminal output.
> 
> My system is Mac PowerPC 750 ( pismo ) running OS X 10.4.11.
> Darwin Kernel Version 8.11.0
> Xcode 2.5
> gcc 4.0.1
> GNU make 3.81
> 
> -
> I have also tried the following, with the current port version 1.7, and 
> received the indicated Error:
> 
> % cd /opt/local/bin/portslocation/dports/faac
> % sudo port install faac
> Password:
> Error: Unable to execute port: invalid command name "livecheck.type"

The command "livecheck.type" is only available in MacPorts 1.8 and later. "sudo 
port selfupdate" should have updated you to the latest version of 
MacPorts, 1.8.2, unless rsync does not work on yo

RE: Re: New user, port selfupdate error

[t...@qx.net]

Hello,  I wasn't sure whether I was suppose wait for something to be done that 
was suppose to be done, or install the patch, so I decided to install the 
batch, and, the following happened after downloading what I thought to be the 
proper patch:
-
% cd `port dir mp4v2`
% pwd
/opt/local/var/macports/sources/rsync.macports.org/release/ports/multimedia/mp4v2
% sudo patch -p0 < ~/mp4v2-1.9.1-libversion.patch 
Password:
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|diff -Nru ../mp4v2-1.9.1-orig/GNUmakefile.in ./GNUmakefile.in
|--- ../mp4v2-1.9.1-orig/GNUmakefile.in 2009-07-14 02:25:44.0 +0300
|+++ ./GNUmakefile.in   2009-10-10 11:12:15.0 +0300
--
File to patch: 


This was my first attempt at installing patches, so I probably did something 
wrong.

Further guidance will be greatly appreciated!

Regards,
Tom




--- Original Message ---
>From: Ryan Schmidt[mailto:ryandes...@macports.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 
> have not been able to get any help with the problem I have 
> encountered. Continued web searching lead me to a mention of installing with 
> 'the other site', which lead me to the 'other sites' web site. I then just 
> followed the instructions. I will run port uninstall and then find the latest 
> source and try that. As for your other question, which make? ==> 
> /usr/local/bin/make I installed this ( 3.81 ) from a source download to 
> replace 3.80, a requirement for installing ffmpeg  Thanks for your help! 

Please remove this make and anything else in /usr/local; it will probably 
interfere and cause problems sooner or later. If you need a newer make, 
install it with MacPorts using the gmake port (on which the ffmpeg port already 
depends, FYI).


> Now, to Ryan,
> 
> I followed Frank's guidance to install 1.8.2, which I have installed, over 
> 1.7.  I initially thought about doing port uninstall for 1.7, but not 
> knowing that I was dealing with two different 'port' sites, I decided that 
> 1.8.2 fit in the update category and that uninstall should not be necessary.  
> Was that a mistake?   port version shows 1.8.2, and it seemed to run once I 
> got the make binary in it's path.

No, that's fine.

Note that "port uninstall" uninstalls (and "port install" installs) ports, not 
the MacPorts base infrastructure. To uninstall the MacPorts base 
infrastructure, should you ever want to do so, instructions are in the guide:

 http://guide.macports.org/chunked/installing.macports.uninstalling.html 


> My problem now is that I received an Error when I tried sudo port install 
> faac   which I then reexecuted with the -d flag and saved the output.  It 
is 
> unclear whether I should go directly to the < 
> http://guide.macports.org/#project.tickets>  or put the Error on this mailing 
> list?  I will list the Error in 
> this email, but if I should go to the bug site, I will do that also.  The 
> Error:
> 
> .
> .
> .
> Usage: /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool -dynamic [-] file 
> [...] [-filelist listfile[,dirname]] [-arch_only arch] [-o output] [-
> install_name name] [-compatibility_version #] [-current_version #] [-seg1addr 
> 0x#] [-segs_read_only_addr 0x#] [-segs_read_write_addr 0x#] [-
> seg_addr_table ] [-seg_addr_table_filename ] 
> [-all_load] [-noall_load]
> make: *** [libmp4v2.la] Error 1
> Error: Target org.macports.build returned: shell command " cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_mp4v2/work/mp4v2-1.9.1"
>  && 
> /opt/local/bin/make -j1 all " returned error 2

This problem is reported here:

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

There is a patch in the ticket. I have not yet looked at it to see why this has 
not yet been committed to the ports tree.



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

RE: Re: New user, port selfupdate error

[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  : macports-users@lists.macosforge.org
Subject : RE: Re: New user, port selfupdate error

 
On Mar 21, 2010, at 20:38, t...@qx.net wrote:

> Hello,  I wasn't sure whether I was suppose wait for something to be done 
> that was suppose to be done, or install the patch, so I decided to install 
the 
> batch, and, the following happened after downloading what I thought to be the 
> proper patch:
> -
> % cd `port dir mp4v2`
> % pwd
> /opt/local/var/macports/sources/rsync.macports.org/release/ports/multimedia/mp4v2
> % sudo patch -p0 < ~/mp4v2-1.9.1-libversion.patch 
> Password:
> can't find file to patch at input line 4
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --
> |diff -Nru ../mp4v2-1.9.1-orig/GNUmakefile.in ./GNUmakefile.in
> |--- ../mp4v2-1.9.1-orig/GNUmakefile.in 2009-07-14 02:25:44.0 +0300
> |+++ ./GNUmakefile.in   2009-10-10 11:12:15.0 +0300
> --
> File to patch: 
> 
> 
> This was my first attempt at installing patches, so I probably did something 
> wrong.
> 
> Further guidance will be greatly appreciated!

The ticket includes instructions on how to use the patch, and also my request 
for more information, as I'm not able to reproduce the failure here.




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

ffmpeg --disable-altivec option

[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

[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
>>
 >>
>On Mar 28, 2010, at 11:11, t...@qx.net wrote:

>> I need to install ffmpeg with the --disable-altivec option.  Is that 
>> possible?

>I don't see an option for that in the portfile. Out of curiosity, why do you 
>need this option?

I have a G3 PPC.  Altivec was a G4 implementation ( Velocity Engine ).  Without 
disabling altivec I get 'illegal instruction' failures from ffmpeg.  
As a note, I have installed the same release of ffmpeg from source, with 
--disable-altivec, and it works fine.  I had to have help from the 
ffmpeg user mailing list to discover this.  I would like to get my 'stuff' 
under MacPorts, but the install I did would not work because of 'illegal 
instructions.'  Is a patch possible?  Thanks for your help!  Best regards, 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

[t...@qx.net]

Thanks Josh,

Now, I am not sure just what to do next.  Since receiving your reply I have:

% sudo port uninstall ffmpeg
% sudo port clean --all ffmpeg
% sudo port install ffmpeg

The resultant ffmpeg did not indicate --disable-altivec in the header and my 
test case failed with 'illegal 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
>Subject : RE: Re: ffmpeg --disable-altivec option
>
 >On 2010-3-29 05:19 , t...@qx.net wrote:
>>> --- 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
>>>
>  >>
>> On Mar 28, 2010, at 11:11, t...@qx.net wrote:
> 
>>> I need to install ffmpeg with the --disable-altivec option.  Is that 
>>> possible?
> 
>> I don't see an option for that in the portfile. Out of curiosity, why do you 
>> need this option?
> 
> I have a G3 PPC.  Altivec was a G4 implementation ( Velocity Engine ).  
> Without disabling altivec I get 'illegal instruction' failures from ffmpeg.  
> As a note, I have installed the same release of ffmpeg from source, with 
> --disable-altivec, and it works fine.  I had to have help from the 
> ffmpeg user mailing list to discover this.  I would like to get my 'stuff' 
> under MacPorts, but the install I did would not work because of 'illegal 
> instructions.'  Is a patch possible?  Thanks for your help!  Best regards, Tom

I've changed the portfile to add --disable-altivec to the configure args
when building on a PPC CPU that does not have a vector unit.

- Josh


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

RE: Re: ffmpeg --disable-altivec option

[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  : macports-users@lists.macosforge.org
>Subject : RE: Re: ffmpeg --disable-altivec option
>
 >On 2010-3-29 11:24 , t...@qx.net wrote:
> Thanks Josh,
> 
> Now, I am not sure just what to do next.  Since receiving your reply I have:
> 
> % sudo port uninstall ffmpeg
> % sudo port clean --all ffmpeg
> % sudo port install ffmpeg
> 
> The resultant ffmpeg did not indicate --disable-altivec in the header and my 
> test case failed with 'illegal instruction.'
> 
> What should I have done?

port selfupdate

- Josh


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users