DJGPP FAQ -- Compile-time and Link-time Problems

www.delorie.com/djgpp/v2faq/faq050.html

search

8. Compile-time and Link-time Problems

Being of a Unix origin, GCC has a somewhat different flavor of command-line syntax and its peculiar compilation and link algorithms. It also has a plethora of optional switches, some of them obscure or semi-documented. These are known to confuse users, especially those who had previous experience with DOS-based C compilers.

This chapter explains how to solve some of those problems which tend to appear when compiling and linking your programs.

8.1 Missing headers or libraries--GCC can't find header files/libraries.
8.2 Missing C++ headers--GCC can't find C++ header files.
8.3 C++ comments--Avoid C++ comments in C programs.
8.4 Which language--GCC resolves it by looking at filename extensions.
8.5 Objective C--Can't use ObjC 2.6.0.
8.6 DJGPP-specific--How to write DJGPP-specific fragments.
8.7 Unresolved externals--Where are those library functions?
8.8 Which library--Which library has which functions?
8.9 Libraries order--Which libraries to put first?
8.10 Still unresolved--C++ misses complex and iostream functions.
8.11 djgpp_first_ctor--Why are these unresolved?
8.12 Large image--Static arrays bloat C++ program image.
8.13 Large executable--Why is DJGPP .EXE so large?
8.14 Linker script--Problems with it can cause linker to fail.
8.15 No EXE--Novell Netware fails STUBIFY.
8.16 Large object files--Linker fails for large objects/libraries.
8.17 Allegro--Problems building Allegro library.
8.18 NULL redefined--Some C++ headers redefine NULL.
8.19 C++ exceptions--GCC before 2.8.1 doesn't support them.
8.20 Assembly output--How to generate assembly code with GCC.
8.21 movedata.h--This header triggers compiler errors.
8.22 Libraries--How to create object libraries.

webmaster donations bookstore	delorie software privacy
Copyright ⌐ 1998 by Eli Zaretskii	Updated Sep 1998

You can help support this site by visiting the advertisers that sponsor it! (only once each, though)