Re: Unexpected File Name Too Long Error With #includes

2005-10-12 Thread Rob Hatcherson
All, To recap my original post of 08/17/2005 on this issue, I had a situation where I was trying to #include a fairly long path in a C program. If the full path was given in-line, then the #include succeeded. If part of the path was given in the source, and the prefix was given as a -I opti

Re: Unexpected File Name Too Long Error With #includes

2005-08-18 Thread Rob Hatcherson
Dave Korn wrote: Original Message From: Rob Hatcherson Sent: 17 August 2005 20:49 All, This issue involves a "File name too long" error being generated by the C preprocessor that came along with 1.5.18-1. The compiler reports version 3.4.4, the distro file says 3.4.4-1.

RE: Unexpected File Name Too Long Error With #includes

2005-08-18 Thread Dave Korn
Original Message >From: Rob Hatcherson >Sent: 17 August 2005 20:49 > All, > > This issue involves a "File name too long" error being generated by the > C preprocessor that came along with 1.5.18-1. The compiler reports > version 3.4.4, the distro file says 3.4.4-1. > I can #include this

Unexpected File Name Too Long Error With #includes

2005-08-17 Thread Rob Hatcherson
All, This issue involves a "File name too long" error being generated by the C preprocessor that came along with 1.5.18-1. The compiler reports version 3.4.4, the distro file says 3.4.4-1. I have a header file whose total path length is 190 characters counting drive letters (yeah, I know i