On Tue, Jan 16, 2001 at 12:27:19PM -0500, Earnie Boyd wrote:
>Robert Collins wrote:
>>
>> GCC, the most common compiler in use under cygwin (I feel pretty safe with this
>assumption) is the tool that will be faced with two
>> include files of the same name, and the issue of getting the right one *has* been
>solved by *distributors* on platforms where the
>> cygwin differences shouldn't affect the solution for this issue.
>>
>
>As I've said in response to Chuck, GCC has a solution, it's the -I
>switch. If you want to use the ncurses headers that are stored in
>/usr/include/ncurses you just add `-I/usr/include/ncurses' and viola it
>uses those headers instead of the /usr/include/unctrl.h header. To
>configure a program you would
> CC='gcc -I/usr/include/ncurses' ../configure ...
>and the configure script would find the available headers.
>
>The rule of thumb to use is, if a package footprint steps on the
>OS/runtime footprint the package footprint needs to be segregated in a
>recognizable manner. My suggestion to use /usr/include/ncurses fits
>that rule.
In this case, I'm not sure exactly why newlib has a unctrl.h file, though.
I'm willing to use the ncurses version instead if that is the consensus.
The ncurses layout on my linux system seems to be different than cygwin
though so I don't see a clear correspondence.
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
