home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!jvnc.net!yale.edu!yale!gumby!destroyer!fmsrl7!eccdb1.pms.ford.com!vscarafi
- From: vscarafi@eccdb1.pms.ford.com (Vincent F. Scarafino)
- Newsgroups: comp.os.ms-windows.programmer.win32
- Subject: Re: write this down!!
- Message-ID: <Bs5x9I.K5@fmsrl7.srl.ford.com>
- Date: 29 Jul 92 18:12:50 GMT
- References: <1992Jul29.003953.7220@pony.Ingres.COM>
- Sender: usenet@fmsrl7.srl.ford.com (0000-Admin(0000))
- Organization: Ford Motor Co.
- Lines: 16
- Originator: news@pms001
-
- rion@Ingres.COM (Rion Cassidy (x3357) OGT) writes:
- > Some of the warnings from the NT linker are routed to stderr, not stdout.
- > This means that you cannot redirect these warning to a file UNLESS you add
- > the following:
- >
- > 2>&1
- >
- > Add it anywhere on your command line where you are also redirecting output
- > to a file. Apparently this is some kind of UNIX trick brought over to NT.
- >
- This is a DOS feature (copied from Multics). Errors are supposed to go to
- stderr to give you the capability to route standard output to a file and still
- see errors on your terminal. Is the NT linker the first piece of software
- to do this right?
-
- Vince
-