5.1. Development | |
| 问: | How do I create a proper patch for MPlayer? |
| 答: | We made a short document describing all the necessary details. Please follow the instructions. |
| 问: | How do I translate MPlayer to a new language? |
| 答: | Read the translation HOWTO, it should explain everything. You can get further help on the MPlayer-translations mailing list. |
| 问: | How can I support MPlayer development? |
| 答: | We are more than happy to accept your hardware and software donations. They help us in continuously improving MPlayer. |
| 问: | How can I become an MPlayer developer? |
| 答: | We always welcome coders and documenters. Read the technical documentation to get a first grasp. Then you should subscribe to the MPlayer-dev-eng mailing list and start coding. If you want to help out with the documentation, join the MPlayer-docs mailing list. |
| 问: | Why don't you use autoconf/automake? |
| 答: | We have a modular, handwritten build system. It does a reasonably good job, so why change? Besides, we dislike the auto* tools, just like other people. |
5.2. Compilation and installation | |
| |
| 问: |
Compilation fails with an error and gcc bails out
with some cryptic message containing the phrase
|
| 答: | You have stumbled over a bug in gcc. Please report it to the gcc team but not to us. For some reason MPlayer seems to trigger compiler bugs frequently. Nevertheless we cannot fix them and do not add workarounds for compiler bugs to our sources. To avoid this problem, either stick with a compiler version that is known to be reliable and stable, or upgrade frequently. |
| 问: | Are there binary (RPM/Debian) packages of MPlayer? |
| 答: | |
| 问: | How can I build a 32 bit MPlayer on a 64 bit Athlon? |
| 答: | Try the following configure options: ./configure --target=athlon_xp --cc="gcc -m32" --as="as --32" --with-extralibdir=/usr/lib
|
| 问: | Configure ends with this text, and MPlayer won't compile! Your gcc does not support even i386 for '-march' and '-mcpu'
|
| 答: | Your gcc isn't installed correctly, check the configure.log file for details. |
| 问: |
I have a Matrox G200/G400/G450/G550, how do I compile/use the
|
| 答: | Read the mga_vid section. |
| 问: | During 'make', MPlayer complains about missing X11 libraries. I don't understand, I do have X11 installed!? |
| 答: | ... but you don't have the X11 development package installed. Or not correctly. It's called XFree86-devel* under Red Hat, xlibs-dev under Debian Woody and libx11-dev under Debian Sarge. Also check if the /usr/X11 and /usr/include/X11 symlinks exist. |
| 问: | Building on Mac OS 10.3 leads to several link errors. |
| 答: | The link error you're experiencing most likely looks like this: ld: Undefined symbols: _LLCStyleInfoCheckForOpenTypeTables referenced from QuartzCore expected to be defined in ApplicationServices _LLCStyleInfoGetUserRunFeatures referenced from QuartzCore expected to be defined in ApplicationServices This problem is the result of Apple developers using 10.4 to compile their software and distributing the binaries to 10.3 users via Software Update. The undefined symbols are present in Mac OS 10.4, but not 10.3. One solution can be to downgrade to QuickTime 7.0.1. Here is a better solution. Get an older copy of the frameworks. This will give you a compressed file that contains the QuickTime 7.0.1 Framework and a 10.3.9 QuartzCore Framework. Uned file are more than happy to accept your hardware and software donations. They help us in continuously improving MPlayer. |
| 问: | How can I become an MPlayer developer? |
| 答: | We always welcome coders and documenters. Read the technical documentation to get a first grasp. Then you should subscribe to the MPlayer-dev-eng mailing list and start coding. If you want to help out with the documentation, join the MPlayer-docs mailing list. |
| 问: | Why don't you use autoconf/automake? |
| 答: | We have a modular, handwritten build system. It does a reasonably good job, so why change? Besides, we dislike the auto* tools, just like other people. |
5.2. Compilation and installation | |
| |
| 问: |
Compilation fails with an error and gcc bails out
with some cryptic message containing the phrase
|
| 答: | You have stumbled over a bug in gcc. Please report it to the gcc team but not to us. For some reason MPlayer seems to trigger compiler bugs frequently. Nevertheless we cannot fix them and do not add workarounds for compiler bugs to our sources. To avoid this problem, either stick with a compiler version that is known to be reliable and stable, or upgrade frequently. |
| 问: | Are there binary (RPM/Debian) packages of MPlayer? |
| 答: | |
| 问: | How can I build a 32 bit MPlayer on a 64 bit Athlon? |
| 答: | Try the following configure options: ./configure --target=athlon_xp --cc="gcc -m32" --as="as --32" --with-extralibdir=/usr/lib
|
| 问: | Configure ends with this text, and MPlayer won't compile! Your gcc does not support even i386 for '-march' and '-mcpu'
|
| 答: | Your gcc isn't installed correctly, check the configure.log file for details. |
| 问: |
I have a Matrox G200/G400/G450/G550, how do I compile/use the
|
| 答: | Read the mga_vid section. |
| 问: | During 'make', MPlayer complains about missing X11 libraries. I don't understand, I do have X11 installed!? |
| 答: | ... but you don't have the X11 development package installed. Or not correctly. It's called XFree86-devel* under Red Hat, xlibs-dev under Debian Woody and libx11-dev under Debian Sarge. Also check if the /usr/X11 and /usr/include/X11 symlinks exist. |
| 问: | Building on Mac OS 10.3 leads to several link errors. |
| 答: | The link error you're experiencing most likely looks like this: ld: Undefined symbols: _LLCStyleInfoCheckForOpenTypeTables referenced from QuartzCore expected to be defined in ApplicationServices _LLCStyleInfoGetUserRunFeatures referenced from QuartzCore expected to be defined in ApplicationServices This problem is the result of Apple developers using 10.4 to compile their software and distributing the binaries to 10.3 users via Software Update. The undefined symbols are present in Mac OS 10.4, but not 10.3. One solution can be to downgrade to QuickTime 7.0.1. Here is a better solution. Get an older copy of the frameworks. This will give you a compressed file that contains the QuickTime 7.0.1 Framework and a 10.3.9 QuartzCore Framework. Uned file are more than happy to accept your hardware and software donations. They help us in continuously improving MPlayer. |
| 问: | How can I become an MPlayer developer? |
| 答: | We always welcome coders and documenters. Read the technical documentation to get a first grasp. Then you should subscribe to the MPlayer-dev-eng mailing list and start coding. If you want to help out with the documentation, join the MPlayer-docs mailing list. |
| 问: | Why don't you use autoconf/automake? |
| 答: | We have a modular, handwritten build system. It does a reasonably good job, so why change? Besides, we dislike the auto* tools, just like other people. |
5.2. Compilation and installation | |
| |
| 问: |
Compilation fails with an error and gcc bails out
with some cryptic message containing the phrase
|
| 答: | You have stumbled over a bug in gcc. Please report it to the gcc team but not to us. For some reason MPlayer seems to trigger compiler bugs frequently. Nevertheless we cannot fix them and do not add workarounds for compiler bugs to our sources. To avoid this problem, either stick with a compiler version that is known to be reliable and stable, or upgrade frequently. |
| 问: | Are there binary (RPM/Debian) packages of MPlayer? |
| 答: | |
| 问: | How can I build a 32 bit MPlayer on a 64 bit Athlon? |
| 答: | Try the following configure options: ./configure --target=athlon_xp --cc="gcc -m32" --as="as --32" --with-extralibdir=/usr/lib
|
| 问: | Configure ends with this text, and MPlayer won't compile! Your gcc does not support even i386 for '-march' and '-mcpu'
|
| 答: | Your gcc isn't installed correctly, check the configure.log file for details. |
| 问: |
I have a Matrox G200/G400/G450/G550, how do I compile/use the
|
| 答: | Read the mga_vid section. |
| 问: | During 'make', MPlayer complains about missing X11 libraries. I don't understand, I do have X11 installed!? |
| 答: | ... but you don't have the X11 development package installed. Or not correctly. It's called XFree86-devel* under Red Hat, xlibs-dev under Debian Woody and libx11-dev under Debian Sarge. Also check if the /usr/X11 and /usr/include/X11 symlinks exist. |
| 问: | Building on Mac OS 10.3 leads to several link errors. |
| 答: | The link error you're experiencing most likely looks like this: ld: Undefined symbols: _LLCStyleInfoCheckForOpenTypeTables referenced from QuartzCore expected to be defined in ApplicationServices _LLCStyleInfoGetUserRunFeatures referenced from QuartzCore expected to be defined in ApplicationServices This problem is the result of Apple developers using 10.4 to compile their software and distributing the binaries to 10.3 users via Software Update. The undefined symbols are present in Mac OS 10.4, but not 10.3. One solution can be to downgrade to QuickTime 7.0.1. Here is a better solution. Get an older copy of the frameworks. This will give you a compressed file that contains the QuickTime 7.0.1 Framework and a 10.3.9 QuartzCore Framework. Uned file are more than happy to accept your hardware and software donations. They help us in continuously improving MPlayer. |
| 问: | How can I become an MPlayer developer? |
| 答: | We always welcome coders and documenters. Read the technical documentation to get a first grasp. Then you should subscribe to the MPlayer-dev-eng mailing list and start coding. If you want to help out with the documentation, join the MPlayer-docs mailing list. |
| 问: | Why don't you use autoconf/automake? |
| 答: | We have a modular, handwritten build system. It does a reasonably good job, so why change? Besides, we dislike the auto* tools, just like other people. |
5.2. Compilation and installation | |
| |
| 问: |
Compilation fails with an error and gcc bails out
with some cryptic message containing the phrase
|
| 答: | You have stumbled over a bug in gcc. Please report it to the gcc team but not to us. For some reason MPlayer seems to trigger compiler bugs frequently. Nevertheless we cannot fix them and do not add workarounds for compiler bugs to our sources. To avoid this problem, either stick with a compiler version that is known to be reliable and stable, or upgrade frequently. |
| 问: | Are there binary (RPM/Debian) packages of MPlayer? |
| 答: | |
| 问: | How can I build a 32 bit MPlayer on a 64 bit Athlon? |
| 答: | Try the following configure options: ./configure --target=athlon_xp --cc="gcc -m32" --as="as --32" --with-extralibdir=/usr/lib
|
| 问: | Configure ends with this text, and MPlayer won't compile! Your gcc does not support even i386 for '-march' and '-mcpu'
|
| 答: | Your gcc isn't installed correctly, check the configure.log file for details. |
| 问: |
I have a Matrox G200/G400/G450/G550, how do I compile/use the
|
| 答: | Read the mga_vid section. |
| 问: | During 'make', MPlayer complains about missing X11 libraries. I don't understand, I do have X11 installed!? |
| 答: | ... but you don't have the X11 development package installed. Or not correctly. It's called XFree86-devel* under Red Hat, xlibs-dev under Debian Woody and libx11-dev under Debian Sarge. Also check if the /usr/X11 and /usr/include/X11 symlinks exist. |
| 问: | Building on Mac OS 10.3 leads to several link errors. |
| 答: | The link error you're experiencing most likely looks like this: ld: Undefined symbols: _LLCStyleInfoCheckForOpenTypeTables referenced from QuartzCore expected to be defined in ApplicationServices _LLCStyleInfoGetUserRunFeatures referenced from QuartzCore expected to be defined in ApplicationServices This problem is the result of Apple developers using 10.4 to compile their software and distributing the binaries to 10.3 users via Software Update. The undefined symbols are present in Mac OS 10.4, but not 10.3. One solution can be to downgrade to QuickTime 7.0.1. Here is a better solution. Get an older copy of the frameworks. This will give you a compressed file that contains the QuickTime 7.0.1 Framework and a 10.3.9 QuartzCore Framework. Uned file are more than happy to accept your hardware and software donations. They help us in continuously improving MPlayer. |
| 问: | How can I become an MPlayer developer? |
| 答: | We always welcome coders and documenters. Read the technical documentation to get a first grasp. Then you should subscribe to the MPlayer-dev-eng mailing list and start coding. If you want to help out with the documentation, join the MPlayer-docs mailing list. |
| 问: | Why don't you use autoconf/automake? |
| 答: | We have a modular, handwritten build system. It does a reasonably good job, so why change? Besides, we dislike the auto* tools, just like other people. |
5.2. Compilation and installation | |
| |
| 问: |
Compilation fails with an error and gcc bails out
with some cryptic message containing the phrase
|
| 答: | You have stumbled over a bug in gcc. Please report it to the gcc team but not to us. For some reason MPlayer seems to trigger compiler bugs frequently. Nevertheless we cannot fix them and do not add workarounds for compiler bugs to our sources. To avoid this problem, either stick with a compiler version that is known to be reliable and stable, or upgrade frequently. |
| 问: | Are there binary (RPM/Debian) packages of MPlayer? |
| 答: | |
| 问: | How can I build a 32 bit MPlayer on a 64 bit Athlon? |
| 答: | Try the following configure options: ./configure --target=athlon_xp --cc="gcc -m32" --as="as --32" --with-extralibdir=/usr/lib
|
| 问: | Configure ends with this text, and MPlayer won't compile! Your gcc does not support even i386 for '-march' and '-mcpu'
|
| 答: | Your gcc isn't installed correctly, check the configure.log file for details. |
| 问: |
I have a Matrox G200/G400/G450/G550, how do I compile/use the
|
| 答: | Read the mga_vid section. |
| 问: | During 'make', MPlayer complains about missing X11 libraries. I don't understand, I do have X11 installed!? |
| 答: | ... but you don't have the X11 development package installed. Or not correctly. It's called XFree86-devel* under Red Hat, xlibs-dev under Debian Woody and libx11-dev under Debian Sarge. Also check if the /usr/X11 and /usr/include/X11 symlinks exist. |
| 问: | Building on Mac OS 10.3 leads to several link errors. |
| 答: | The link error you're experiencing most likely looks like this: ld: Undefined symbols: _LLCStyleInfoCheckForOpenTypeTables referenced from QuartzCore expected to be defined in ApplicationServices _LLCStyleInfoGetUserRunFeatures referenced from QuartzCore expected to be defined in ApplicationServices This problem is the result of Apple developers using 10.4 to compile their software and distributing the binaries to 10.3 users via Software Update. The undefined symbols are present in Mac OS 10.4, but not 10.3. One solution can be to downgrade to QuickTime 7.0.1. Here is a better solution. Get an older copy of the frameworks. This will give you a compressed file that contains the QuickTime 7.0.1 Framework and a 10.3.9 QuartzCore Framework. Uned file are more than happy to accept your hardware and software donations. They help us in continuously improving MPlayer. |
| 问: | How can I become an MPlayer developer? |
| 答: | We always welcome coders and documenters. Read the technical documentation to get a first grasp. Then you should subscribe to the MPlayer-dev-eng mailing list and start coding. If you want to help out with the documentation, join the MPlayer-docs mailing list. |
| 问: | Why don't you use autoconf/automake? |
| 答: | We have a modular, handwritten build system. It does a reasonably good job, so why change? Besides, we dislike the auto* tools, just like other people. |
5.2. Compilation and installation | |
| |
| 问: |
Compilation fails with an error and gcc bails out
with some cryptic message containing the phrase
|
| 答: | You have stumbled over a bug in gcc. Please report it to the gcc team but not to us. For some reason MPlayer seems to trigger compiler bugs frequently. Nevertheless we cannot fix them and do not add workarounds for compiler bugs to our sources. To avoid this problem, either stick with a compiler version that is known to be reliable and stable, or upgrade frequently. |
| 问: | Are there binary (RPM/Debian) packages of MPlayer? |
| 答: | |
| 问: | How can I build a 32 bit MPlayer on a 64 bit Athlon? |
| 答: | Try the following configure options: ./configure --target=athlon_xp --cc="gcc -m32" --as="as --32" --with-extralibdir=/usr/lib
|
| 问: | Configure ends with this text, and MPlayer won't compile! Your gcc does not support even i386 for '-march' and '-mcpu'
|
| 答: | Your gcc isn't installed correctly, check the configure.log file for details. |
| 问: |
I have a Matrox G200/G400/G450/G550, how do I compile/use the
|
| 答: | Read the mga_vid section. |
| 问: | During 'make', MPlayer complains about missing X11 libraries. I don't understand, I do have X11 installed!? |
| 答: | ... but you don't have the X11 development package installed. Or not correctly. It's called XFree86-devel* under Red Hat, xlibs-dev under Debian Woody and libx11-dev under Debian Sarge. Also check if the /usr/X11 and /usr/include/X11 symlinks exist. |
| 问: | Building on Mac OS 10.3 leads to several link errors. |
| 答: | The link error you're experiencing most likely looks like this: ld: Undefined symbols: _LLCStyleInfoCheckForOpenTypeTables referenced from QuartzCore expected to be defined in ApplicationServices _LLCStyleInfoGetUserRunFeatures referenced from QuartzCore expected to be defined in ApplicationServices This problem is the result of Apple developers using 10.4 to compile their software and distributing the binaries to 10.3 users via Software Update. The undefined symbols are present in Mac OS 10.4, but not 10.3. One solution can be to downgrade to QuickTime 7.0.1. Here is a better solution. Get an older copy of the frameworks. This will give you a compressed file that contains the QuickTime 7.0.1 Framework and a 10.3.9 QuartzCore Framework. Uned file are more than happy to accept your hardware and software donations. They help us in continuously improving MPlayer. |
| 问: | How can I become an MPlayer developer? |
| 答: | We always welcome coders and documenters. Read the technical documentation to get a first grasp. Then you should subscribe to the MPlayer-dev-eng mailing list and start coding. If you want to help out with the documentation, join the MPlayer-docs mailing list. |
| 问: | Why don't you use autoconf/automake? |
| 答: | We have a modular, handwritten build system. It does a reasonably good job, so why change? Besides, we dislike the auto* tools, just like other people. |
5.2. Compilation and installation | |
| |
| 问: |
Compilation fails with an error and gcc bails out
with some cryptic message containing the phrase
|
| 答: | You have stumbled over a bug in gcc. Please report it to the gcc team but not to us. For some reason MPlayer seems to trigger compiler bugs frequently. Nevertheless we cannot fix them and do not add workarounds for compiler bugs to our sources. To avoid this problem, either stick with a compiler version that is known to be reliable and stable, or upgrade frequently. |
| 问: | Are there binary (RPM/Debian) packages of MPlayer? |
| 答: | |
| 问: | How can I build a 32 bit MPlayer on a 64 bit Athlon? |
| 答: | Try the following configure options: ./configure --target=athlon_xp --cc="gcc -m32" --as="as --32" --with-extralibdir=/usr/lib
|
| 问: | Configure ends with this text, and MPlayer won't compile! Your gcc does not support even i386 for '-march' and '-mcpu'
|
| 答: | Your gcc isn't installed correctly, check the configure.log file for details. |
| 问: |
I have a Matrox G200/G400/G450/G550, how do I compile/use the
|
| 答: | Read the mga_vid section. |
| 问: | During 'make', MPlayer complains about missing X11 libraries. I don't understand, I do have X11 installed!? |
| 答: | ... but you don't have the X11 development package installed. Or not correctly. It's called XFree86-devel* under Red Hat, xlibs-dev under Debian Woody and libx11-dev under Debian Sarge. Also check if the /usr/X11 and /usr/include/X11 symlinks exist. |
| 问: | Building on Mac OS 10.3 leads to several link errors. |
| 答: | The link error you're experiencing most likely looks like this: ld: Undefined symbols: _LLCStyleInfoCheckForOpenTypeTables referenced from QuartzCore expected to be defined in ApplicationServices _LLCStyleInfoGetUserRunFeatures referenced from QuartzCore expected to be defined in ApplicationServices This problem is the result of Apple developers using 10.4 to compile their software and distributing the binaries to 10.3 users via Software Update. The undefined symbols are present in Mac OS 10.4, but not 10.3. One solution can be to downgrade to QuickTime 7.0.1. Here is a better solution. Get an older copy of the frameworks. This will give you a compressed file that contains the QuickTime 7.0.1 Framework and a 10.3.9 QuartzCore Framework. Uned file are more than happy to accept your hardware and software donations. They help us in continuously improving MPlayer. |
| 问: | How can I become an MPlayer developer? |
| 答: | We always welcome coders and documenters. Read the technical documentation to get a first grasp. Then you should subscribe to the MPlayer-dev-eng mailing list and start coding. If you want to help out with the documentation, join the MPlayer-docs mailing list. |
| 问: | Why don't you use autoconf/automake? |
| 答: | We have a modular, handwritten build system. It does a reasonably good job, so why change? Besides, we dislike the auto* tools, just like other people. |
5.2. Compilation and installation | |
| |
| 问: |
Compilation fails with an error and gcc bails out
with some cryptic message containing the phrase
|
| 答: | You have stumbled over a bug in gcc. Please report it to the gcc team but not to us. For some reason MPlayer seems to trigger compiler bugs frequently. Nevertheless we cannot fix them and do not add workarounds for compiler bugs to our sources. To avoid this problem, either stick with a compiler version that is known to be reliable and stable, or upgrade frequently. |
| 问: | Are there binary (RPM/Debian) packages of MPlayer? |
| 答: | |
| 问: | How can I build a 32 bit MPlayer on a 64 bit Athlon? |
| 答: | Try the following configure options: ./configure --target=athlon_xp --cc="gcc -m32" --as="as --32" --with-extralibdir=/usr/lib
|
| 问: | Configure ends with this text, and MPlayer won't compile! Your gcc does not support even i386 for '-march' and '-mcpu'
|
| 答: | Your gcc isn't installed correctly, check the configure.log file for details. |
| 问: |
I have a Matrox G200/G400/G450/G550, how do I compile/use the
|
| 答: | Read the mga_vid section. |
| 问: | During 'make', MPlayer complains about missing X11 libraries. I don't understand, I do have X11 installed!? |
| 答: | ... but you don't have the X11 development package installed. Or not correctly. It's called XFree86-devel* under Red Hat, xlibs-dev under Debian Woody and libx11-dev under Debian Sarge. Also check if the /usr/X11 and /usr/include/X11 symlinks exist. |
| 问: | Building on Mac OS 10.3 leads to several link errors. |
| 答: | The link error you're experiencing most likely looks like this: ld: Undefined symbols: _LLCStyleInfoCheckForOpenTypeTables referenced from QuartzCore expected to be defined in ApplicationServices _LLCStyleInfoGetUserRunFeatures referenced from QuartzCore expected to be defined in ApplicationServices This problem is the result of Apple developers using 10.4 to compile their software and distributing the binaries to 10.3 users via Software Update. The undefined symbols are present in Mac OS 10.4, but not 10.3. One solution can be to downgrade to QuickTime 7.0.1. Here is a better solution. Get an older copy of the frameworks. This will give you a compressed file that contains the QuickTime 7.0.1 Framework and a 10.3.9 QuartzCore Framework. Uned file are more than happy to accept your hardware and software donations. They help us in continuously improving MPlayer. |
| 问: | How can I become an MPlayer developer? |
| 答: | We always welcome coders and documenters. Read the technical documentation to get a first grasp. Then you should subscribe to the MPlayer-dev-eng mailing list and start coding. If you want to help out with the documentation, join the MPlayer-docs mailing list. |
| 问: | Why don't you use autoconf/automake? |
| 答: | We have a modular, handwritten build system. It does a reasonably good job, so why change? Besides, we dislike the auto* tools, just like other people. |
5.2. Compilation and installation | |
| |