diff options
Diffstat (limited to 'DOCS/xml/en')
| -rw-r--r-- | DOCS/xml/en/bugreports.xml | 4 | ||||
| -rw-r--r-- | DOCS/xml/en/faq.xml | 2 | ||||
| -rw-r--r-- | DOCS/xml/en/install.xml | 4 |
3 files changed, 5 insertions, 5 deletions
diff --git a/DOCS/xml/en/bugreports.xml b/DOCS/xml/en/bugreports.xml index f72489ff63..786c2516ef 100644 --- a/DOCS/xml/en/bugreports.xml +++ b/DOCS/xml/en/bugreports.xml @@ -352,10 +352,10 @@ ld -v<!-- <para> If you get errors while running <command>./configure</command>, or autodetection -of something fails, read <filename>configure.log</filename>. You may find the +of something fails, read <filename>config.log</filename>. You may find the answer there, for example multiple versions of the same library mixed on your system, or you forgot to install the development package (those with the -dev -suffix). If you think there is a bug, include <filename>configure.log</filename> +suffix). If you think there is a bug, include <filename>config.log</filename> in your bug report. </para> </sect2> diff --git a/DOCS/xml/en/faq.xml b/DOCS/xml/en/faq.xml index 58450c3d83..164843589d 100644 --- a/DOCS/xml/en/faq.xml +++ b/DOCS/xml/en/faq.xml @@ -122,7 +122,7 @@ Configure ends with this text, and <application>MPlayer</application> won't comp <screen>Your gcc does not support even i386 for '-march' and '-mcpu'</screen> </para></question> <answer><para> -Your gcc isn't installed correctly, check the <filename>configure.log</filename> +Your gcc isn't installed correctly, check the <filename>config.log</filename> file for details. </para></answer> </qandaentry> diff --git a/DOCS/xml/en/install.xml b/DOCS/xml/en/install.xml index dd03e00377..fbbe0d2299 100644 --- a/DOCS/xml/en/install.xml +++ b/DOCS/xml/en/install.xml @@ -155,13 +155,13 @@ in <application>MPlayer</application>'s root directory. See <para> <emphasis role="bold">Always browse the output of</emphasis> <filename>./configure</filename>, and the -<filename>configure.log</filename> file, they contain information about +<filename>config.log</filename> file, they contain information about what will be built, and what will not. You may also want to view <filename>config.h</filename> and <filename>config.mak</filename> files. If you have some libraries installed, but not detected by <filename>./configure</filename>, then check if you also have the proper header files (usually the -dev packages) and their version matches. The -<filename>configure.log</filename> file usually tells you what is missing. +<filename>config.log</filename> file usually tells you what is missing. </para> <para> |