#includes not being processed across network (revised)

Larry Hall (RFK Partners, Inc) lhall@rfk.com
Thu Jan 4 07:40:00 GMT 2001


At 09:34 PM 1/3/2001, M4um@aol.com wrote:
>One other thought just struck me: Are #included files accessed by any 
>specific dll or bash/sh command or function that can be excersized or tested 
>independantly by some clever means?  It may be that I have something still 
>outdated in my installation that's fallen through the cracks.  (By the way, 
>since the last cygcheck I've upgraded the cygtcl dlls.) 


If you're concerned about having things up-to-date, just rerun setup.  It 
will update anything that's out-of-date.


>While I research how Samba will fit into our configuration, can you think of 
>any gcc/cpp tests that might help me isolate this problem?


Sounds to me like strace is your best bet, as Earnie suggested.


Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple



More information about the Cygwin mailing list