comparison etc/PROBLEMS @ 42789:b016f6f9056c

Document problems with linking libraries compiled with GCC.
author Eli Zaretskii <eliz@gnu.org>
date Wed, 16 Jan 2002 18:21:14 +0000
parents 3ff0fcbfdfa9
children ff6514dbd1ce
comparison
equal deleted inserted replaced
42788:ec9199e7ac0f 42789:b016f6f9056c
24 (replace the ellipsis "..." with any additional arguments you pass to 24 (replace the ellipsis "..." with any additional arguments you pass to
25 the script). 25 the script).
26 26
27 Note that this problem does not pertain to the MS-Windows port of 27 Note that this problem does not pertain to the MS-Windows port of
28 Emacs, since it doesn't use the preprocessor to generate Makefiles. 28 Emacs, since it doesn't use the preprocessor to generate Makefiles.
29
30 * Building Emacs with a system compiler fails during link stage.
31
32 This can happen if some of the libraries linked into Emacs were built
33 with GCC, but Emacs itself is being linked with a compiler other than
34 GCC. Object files compiled with GCC might need some helper functions
35 from libgcc.a, the library which comes with GCC, but the system
36 compiler does not instruct the linker to search libgcc.a during the
37 link stage.
38
39 A solution is to link with GCC, like this:
40
41 make CC=gcc
29 42
30 * Building the MS-Windows port with Cygwin GCC can fail. 43 * Building the MS-Windows port with Cygwin GCC can fail.
31 44
32 Emacs may not build using recent Cygwin builds of GCC, such as Cygwin 45 Emacs may not build using recent Cygwin builds of GCC, such as Cygwin
33 version 1.1.8, using the default configure settings. It appears to be 46 version 1.1.8, using the default configure settings. It appears to be