> > What autoconf wants is to have an attempt to compile and link > a program that refers to a particular symbol cause, on a > system that doesn't have that symbol in the libraries being > used, the linker to exit with a non-zero exit status; that's > the sense in which the linker needs to fail in order for > autoconf to work. > > >> Also, if there is a way of getting the linker to fail with > undefined > >> references, so that we could, in theory, have the configure script > >> use an option to make it do so: > > > > This is problematic. Unfortunately, I do not know how, and the > > documentation does not make it obvious that this can be > done for the > > linker. > > Oh, well - I guess that means that autoconf won't work on QNX > (or QNX4, at least - it won't work on any of the QNX versions > where the Watcom linker is being used).
The Watcom Linker issues three classes of messages; each message has a 4-digit number associated with it: - fatal messages start with the digit 3 - error messages start with the digit 2 - warning messages start with the digit 1 If a fatal error occurs, the linker terminates immediately. If an error occurs, the linker continues so that all possible errors are issued, and no executable is created. If a warning occurs, the linker continues (and doesn't prevent the creation of a proper executable). The documentation for the Watcom Linker does not say how a given warning or error can be promoted to "fatal". :-( - This is the tcpdump-workers list. Visit https://lists.sandelman.ca/ to unsubscribe.
