Re: cyg*.dll, linking

2011-12-13 Thread Brian Craft
On Tue, Dec 13, 2011 at 11:16 AM, Csaba Raduly wrote: > On Tue, Dec 13, 2011 at 7:45 PM, Brian Craft  wrote: > >> And why don't I see cyg*.dll files, for example, in /usr/lib? > > They are all hiding under /usr/bin :) > Ah! I see. So the install is working fine, I

Re: cyg*.dll, linking

2011-12-13 Thread Brian Craft
On Tue, Dec 13, 2011 at 10:24 AM, Ryan Johnson wrote: > On 13/12/2011 1:16 PM, Brian Craft wrote: >> >> I'm building a few libraries which are dependencies of a program I'm >> building. Most of them build via autotools. Doing "make install" >>

cyg*.dll, linking

2011-12-13 Thread Brian Craft
I'm building a few libraries which are dependencies of a program I'm building. Most of them build via autotools. Doing "make install" installs files *.a, *.la, *.dll.a. Linking the executable succeeds without error, however when running it, the loader complains that it can't find cyg*.dll files. E.

Re: stdout output missing, but redirecting works

2011-12-09 Thread Brian Craft
On Fri, Dec 9, 2011 at 12:44 PM, Larry Hall (Cygwin) wrote: > On 12/9/2011 2:47 PM, Brian Craft wrote: >> >> I compiled a program yesterday which output some lines to stdout. It >> appeared to be working. Running it today, I get nothing on stdout. >> However, if I red

stdout output missing, but redirecting works

2011-12-09 Thread Brian Craft
I compiled a program yesterday which output some lines to stdout. It appeared to be working. Running it today, I get nothing on stdout. However, if I redirect stdout to a file, the correct output appears in the file. E.g. # no output ./foo # "hello world" in bar ./foo > bar In between yesterday