2024年3月20日发(作者：)

标题: MPlayer 最新完整的中文文档

FAQ:

5. FAQ

* 5.1 编译

* 5.2 一般问题

* 5.3 播放问题

* 5.4 视频与音频驱动问题(vo/ao)

* 5.5 DVD播放

* 5.6 特性要求

* 5.7 编码

5.1 编译

Q：编译停止并出现类似这样的出错信息：

In file included from mplayer.c:34:

mw.h: In function `mplMainDraw':

mw.h:209: Internal compiler error in print_rtl_and_abort, at flow.c:6458

Please submit a full bug report,

with preprocessed source if appropriate.

A：这是gcc 3.0.4的一个已知的bug，升级到3.1就可以解决问题。如何安装gcc参阅gcc 2.96

部分。

Q：Configure结束时出现这样的文字，MPlayer无法编译！

"Your gcc does not support even i386 for '-march' and '-mcpu'."

A：你的gcc没有正确的安装，细节需要查看文件。

Q："No such file or directory"是什么意思？

A：有可能真的没有这样文件或目录。

Q：gcc2.96有什么问题？

A：我们强烈反对使用gcc 2.96！

细节参见这个文件了解为什么Red Hat发布gcc 2.96，以及它有什么问题。如果你仍然确实

确实确实确实想要使用它，总是使用最新的版本并且在configure的时候加上--disable-

gcc-checking选项。记住是你自己选择这条路的。一定不要报告bug，一定不要到邮件列表

上寻求帮助。如果你遇到问题我们将不提供任何支持。

Q：好极了，那么我使用Red Hat/Mandrake的gcc 3.0.1，我没问题！

A：不，因为那些编译器同样有问题。为了了解当前的编译器对MPlayer的支持状况，参见安

装部分。

Q：我试图编译MPlayer，但是我得到这样的输出：

In file included from /usr/include/g++-v3/bits/std_cwchar.h:42,

from /usr/include/g++-v3/bits/fpos.h:40,

from /usr/include/g++-v3/bits/char_traits.h:40,

from /usr/include/g++-v3/bits/std_string.h:41,

from /usr/include/g++-v3/string:31,

from libwin32.h:36,

from DS_AudioDecoder.h:4,

from DS_:5:

/usr/include/wchar.h: In function Long long int wcstoq(const wchar_t*,

wchar_t**, int)':

/usr/include/wchar.h:514: cannot convert `const wchar_t* __restrict' to

`const

A：把你的glibc升级到最新的发行版。对于Mandrake，使用2.2.4-8mdk。

Q：... gcc 2.96 ... (是的，有些人还在为gcc 2.96上火！)

A：我们引用A'rpi发送到mplayer-users邮件列表的一封 邮件('ideg'的意思将在下面解释)：

And we have idegs. And our idegcounter overflowed again and again.

Unfortunately MPlayer is out of our control. It's used by lamers, Linux users who

can't even use Windows, and never tried to compile a kernel. They installed (with

default options) Mandrake or Red Hat or SuSE, and without RTFM'ing they send messages

saying 'it doesn't work! help me! please! i'm new to Linux! help! oh! help me!'. We

can't stop them, but at least we try to force them to RTFM and to read the messages

of ./configure and MPlayer.

And you clever guys come and flame us with gcc 2.96 and binary packages. Instead of

helping users or making patches to help solve problems.

Half of our spare/free time is spent by answering silly mails here and making newer

tricks and checks to configure to avoid such mails.

And there is a balance. On the one side are you, clever guys, saying we are very bad

because we don't like buggy gcc 2.96, and on the other side there are the 'new to

Linux' guys who are showing us gcc 2.96 is buggy.