Solutions to typical compiling errors: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
No edit summary
No edit summary
Line 12: Line 12:


<code>xxx file doesn't exist</code><br>
<code>xxx file doesn't exist</code><br>
One possible reason is that .mozconfig doesn't exist or it's in the wrong place. First check whether .mozconfig exists at browser/config/mozconfig. Additionally, for Win32, mozconfig.txt must point to the above path by using the following line :<br>
One possible reason is that .mozconfig doesn't exist or is in the wrong place. First check whether .mozconfig exists at browser/config/mozconfig. Additionally, for Win32, mozconfig.txt must point to the above path by using the following line :<br>
<code>. $topsrcdir/browser/config/mozconfig</code>
<code>. $topsrcdir/browser/config/mozconfig</code>

Revision as of 20:41, 21 October 2004

During a typical compiling process, there are quite a few errors where an inexperienced builder may stumble upon. Here there are a few of them :

fatal error C1601: unsupported inline assembly opcode
Older MS assemblers don't support SSE2 assembly instructions. Solution is to apply Microsoft Processor Pack 5 for VC++ (administrator rights may be needed)


fatal error C1600: unsupported data type in jidctint.c
Solution same as bove

some toolbar icons, toolbar text fields are broken (compiling with MS Visual Studio 6)
-O2 optimization is buggy. In your .mozconfig, include ac_add_options -enable-optimize (defaults to -O1 optimization) or disable optimization.

xxx file doesn't exist
One possible reason is that .mozconfig doesn't exist or is in the wrong place. First check whether .mozconfig exists at browser/config/mozconfig. Additionally, for Win32, mozconfig.txt must point to the above path by using the following line :
. $topsrcdir/browser/config/mozconfig