changeset 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 ec9199e7ac0f
children 987fa2a733e0
files etc/PROBLEMS
diffstat 1 files changed, 13 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/etc/PROBLEMS	Wed Jan 16 13:46:59 2002 +0000
+++ b/etc/PROBLEMS	Wed Jan 16 18:21:14 2002 +0000
@@ -27,6 +27,19 @@
 Note that this problem does not pertain to the MS-Windows port of
 Emacs, since it doesn't use the preprocessor to generate Makefiles.
 
+* Building Emacs with a system compiler fails during link stage.
+
+This can happen if some of the libraries linked into Emacs were built
+with GCC, but Emacs itself is being linked with a compiler other than
+GCC.  Object files compiled with GCC might need some helper functions
+from libgcc.a, the library which comes with GCC, but the system
+compiler does not instruct the linker to search libgcc.a during the
+link stage.
+
+A solution is to link with GCC, like this:
+
+  	make CC=gcc
+
 * Building the MS-Windows port with Cygwin GCC can fail.
 
 Emacs may not build using recent Cygwin builds of GCC, such as Cygwin