From: possum AT nospam DOT com (J. Hughes)
Newsgroups: comp.os.msdos.djgpp
Subject: stdout flushing after printf, SIGALRM signal and GNU Make
Date: Wed, 19 Nov 1997 03:32:42 GMT
Message-ID: <347259eb.883582@news.total.net>
NNTP-Posting-Host: 205.205.161.84
Organization: TotalNet Inc.
Lines: 39
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Hello,

I've been reading the newsgroup for a while now and I haven't found
anything on the following things I have problems with; sorry if it's
already been asked:

1. When using printf without a "\n", you need to use fflush (stdout);
to make it appear on screen. I was simply wandering if there was a
compiler switch, a conditional define or anything (besides making a
new function for 'printf') which could automate the process? That
would basically output to the screen on every printf with or without a
trailing \n..

2. Also, I've written a small inet client/daemon in Linux, which works
very well, but when I try to run it on DJGPP with the libsocket-0.5,
the signal (signal(SIGALRM, handler);) doesn't seem to work.. I have
the handler all setup (runs fine in Linux as I said)

void handler ()
{
  signal (SIGALRM, handler);
}

But without signal I just don't know how to make the winsock 'connect'
function quit after an X second delay..

3. And finally (sorry), I'm having problems with the GNU make
(3.76.1): though it's supposed to support long file names, when I try
to run a makefile with LFN or a dep file starting with a dot, it
crashes out:

make.exe[1]: Entering directory `d:/gcc/libsoc~1.5/src'
make.exe[1]: *** No rule to make target `protoresolve', needed by
`library2'.  Stop.
Any ideas?

Thanks!

E-mail address witholded because spammers have nothing better to do.