Hi all-

If anyone likes another posix riddle, here goes:

I run a program having an unresolved external. As expected, the
system tells me exactly what's wrong:

$ hello
UNRESOLVED EXTERNALS: callit  (LDRERR 512)

**** EXEC FUNCTION FAILED; subsys =517; info = 48
ABORT: /UTOOLS/PUB/etc/hello
NM SYS   a.00a82288 dbg_abort_trace+$24
[1] + Done (134) hello
  85786723      Abort   hello
$

Ok. Now I want to capture that in a file - let's use two for fun:

$ hello >1.log 2>2.log
$

Now I look in these two files. Neither of them contains the message

        UNRESOLVED EXTERNALS: callit  (LDRERR 512)

that I get on the screen w/o redirection. Go figure !?
Also, the 1.log (stdout) does not contain any linefeeds.
Guess there must be funky stuff going on somewhere...
Anyone got a clue ?

BTW Anybody know of a way to tell the linker to flag unresolved
externals as an error ? My makefiles trot on happily after linking a
program with unresolveds - and generate lots of problems
later on because of it. They're just stupid UNIX makefiles that do
not know about runtime binding ;-)

TIA !

--
Kind regards,

        Chris Breemer           [log in to unmask]
        Compuware Europe B.V.   http://www.compuware.com