-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/20/10 09:43, Uoti Urpala wrote: > On Wed, 2010-01-20 at 09:28 -0700, Kevin DeKorte wrote: >> I was trying to build mplayer from the git repository and noticed that >> my builds were failing since the make command tries to install things as >> part of the process. >> >> I do not like to build things as root, so I think the git build scripts >> need to be fixed so that it can properly build in a non-root environment. > > The mplayer-build repo certainly does NOT need to be built as root. The > internally used static FFmpeg and libass libraries are created under the > build tree so that needs no extra permissions. > > Did you perhaps specify --prefix, and incorrectly place that in > common_options? The static libraries created during the build process > are not suitable for system-wide installation, so specifying --prefix > for them makes no sense; if you want to install the resulting mplayer > binary in a particular location then place --prefix in mplayer_options. > There should probably be a separate warning against --prefix in > common_options as many users seem to make the same mistake... Ok moving --prefix from common_options to mplayer_options did help some. But I am running into some more issues. make -j 4 doesn't appear to work right, make -j 1 is a workaround libass does not seem to pick up values from the common_options. I'm trying to build a 32bit mplayer on a 64bit machine (mainly so I can use the additional codecs) and so I have placed this in my common_options - --cc=gcc -m32 - --as=as --32 ffmpeg_options is blank mplayer_options has this - --target=i386-linux - --prefix=/usr When I build mplayer from SVN I use this and it works great. ./configure --target=i386-linux --cc="gcc -m32" --as="as --32" - --prefix=/usr So when I build using git, libass is still built in 64bit mode, which then will not link with the 32bit mplayer. I tried putting --target in the common options and ffmpeg would not configure with that in there. I have attached a python version of libass-config, but since I have not figured out what options to use to build it in 32bit mode I'm still kinda stuck. libass does not seem to like the --cc and --as options. Hope this is clear as to what I am trying to do. Kevin - -- Get my public GnuPG key from http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAktXYGAACgkQ6w2kMH0L1dEYeQCfd4tGWt3VY4m2Sb0HHyquc/AF 21UAoI1JqSUcv4grv8J3V7Sg4YpwJ+6N =8yeF -----END PGP SIGNATURE----- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: libass-config URL: <http://lists.mplayerhq.hu/pipermail/mplayer-users/attachments/20100120/ba408aa2/attachment.asc>
