* Re: include and library paths
@ 1999-07-01 12:11 Earnie Boyd
1999-07-31 18:34 ` Earnie Boyd
0 siblings, 1 reply; 20+ messages in thread
From: Earnie Boyd @ 1999-07-01 12:11 UTC (permalink / raw)
To: Ian T Zimmerman; +Cc: cygwin users
--- Ian T Zimmerman <itz@lbin.com> wrote:
> Hi, do the C_INCLUDE_PATH and LIBRARY_PATH envars work as advertised
> (and as they work on Unix installataions of gcc & friends)?
>
> I do this:
>
> amazon:~$ printenv C_INCLUDE_PATH
> /usr/X11R6.4/LessTif/Motif2.0/include/:/usr/X11R6.4/include/
What happens if you remove the ending / so that it reads:
/usr/X11R6.4/LessTif/Motif2.0/include:/usr/X11R6.4/include
===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
(If you respond to the list, then please don't cc me)
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: include and library paths
1999-07-01 12:11 include and library paths Earnie Boyd
@ 1999-07-31 18:34 ` Earnie Boyd
0 siblings, 0 replies; 20+ messages in thread
From: Earnie Boyd @ 1999-07-31 18:34 UTC (permalink / raw)
To: Ian T Zimmerman; +Cc: cygwin users
--- Ian T Zimmerman <itz@lbin.com> wrote:
> Hi, do the C_INCLUDE_PATH and LIBRARY_PATH envars work as advertised
> (and as they work on Unix installataions of gcc & friends)?
>
> I do this:
>
> amazon:~$ printenv C_INCLUDE_PATH
> /usr/X11R6.4/LessTif/Motif2.0/include/:/usr/X11R6.4/include/
What happens if you remove the ending / so that it reads:
/usr/X11R6.4/LessTif/Motif2.0/include:/usr/X11R6.4/include
===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
(If you respond to the list, then please don't cc me)
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* include and library paths
@ 1999-07-22 2:33 Joseph M. Hinkle
1999-07-31 18:34 ` Joseph M. Hinkle
0 siblings, 1 reply; 20+ messages in thread
From: Joseph M. Hinkle @ 1999-07-22 2:33 UTC (permalink / raw)
To: cygwin
I see Mumit's Cygnus egcs-1.1.2 gcc automatically searches for include
files in /usr/include, but the same compiler in the MinGW distribution of
the same date (March 16, 1999) does not.
Could I learn the reason for that? If it's just an oversight to be
corrected, I'll leave construction of a specific -I/usr/include out of this
makefile generation code...
Thanks
jmh
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* include and library paths
1999-07-22 2:33 Joseph M. Hinkle
@ 1999-07-31 18:34 ` Joseph M. Hinkle
0 siblings, 0 replies; 20+ messages in thread
From: Joseph M. Hinkle @ 1999-07-31 18:34 UTC (permalink / raw)
To: cygwin
I see Mumit's Cygnus egcs-1.1.2 gcc automatically searches for include
files in /usr/include, but the same compiler in the MinGW distribution of
the same date (March 16, 1999) does not.
Could I learn the reason for that? If it's just an oversight to be
corrected, I'll leave construction of a specific -I/usr/include out of this
makefile generation code...
Thanks
jmh
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* include and library paths
@ 1999-07-01 11:53 Ian T Zimmerman
1999-07-01 12:19 ` Chris Faylor
1999-07-31 18:34 ` Ian T Zimmerman
0 siblings, 2 replies; 20+ messages in thread
From: Ian T Zimmerman @ 1999-07-01 11:53 UTC (permalink / raw)
To: cygwin
Hi, do the C_INCLUDE_PATH and LIBRARY_PATH envars work as advertised
(and as they work on Unix installataions of gcc & friends)?
I do this:
amazon:~$ printenv C_INCLUDE_PATH
/usr/X11R6.4/LessTif/Motif2.0/include/:/usr/X11R6.4/include/
amazon:~$ ls -l /usr/X11R6.4/include/X11/Intrinsic.h
-r--r--r-- 1 administ None 73459 Nov 3 1998 /usr/X11R6.4/include/X11/Intrinsic.h
amazon:~$ cat stupid_test.c
#include <X11/Intrinsic.h>
amazon:~$ gcc -E stupid_test.c
stupid_test.c:1: X11/Intrinsic.h: No such file or directory
# 1 "stupid_test.c"
amazon:~$
?!?
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: include and library paths
1999-07-01 11:53 Ian T Zimmerman
@ 1999-07-01 12:19 ` Chris Faylor
1999-07-01 13:21 ` Ian T Zimmerman
1999-07-31 18:34 ` Chris Faylor
1999-07-31 18:34 ` Ian T Zimmerman
1 sibling, 2 replies; 20+ messages in thread
From: Chris Faylor @ 1999-07-01 12:19 UTC (permalink / raw)
To: Ian T Zimmerman; +Cc: cygwin
On Thu, Jul 01, 1999 at 06:52:08PM +0000, Ian T Zimmerman wrote:
>Hi, do the C_INCLUDE_PATH and LIBRARY_PATH envars work as advertised
>(and as they work on Unix installataions of gcc & friends)?
>
>I do this:
>
>amazon:~$ printenv C_INCLUDE_PATH
>/usr/X11R6.4/LessTif/Motif2.0/include/:/usr/X11R6.4/include/
>amazon:~$ ls -l /usr/X11R6.4/include/X11/Intrinsic.h
>-r--r--r-- 1 administ None 73459 Nov 3 1998 /usr/X11R6.4/include/X11/Intrinsic.h
>amazon:~$ cat stupid_test.c
>#include <X11/Intrinsic.h>
>amazon:~$ gcc -E stupid_test.c
>stupid_test.c:1: X11/Intrinsic.h: No such file or directory
># 1 "stupid_test.c"
Try doing a "gcc -v -E stupid_test.c" to see what libraries are
being searched.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: include and library paths
1999-07-01 12:19 ` Chris Faylor
@ 1999-07-01 13:21 ` Ian T Zimmerman
1999-07-01 13:50 ` Chris Faylor
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-31 18:34 ` Chris Faylor
1 sibling, 2 replies; 20+ messages in thread
From: Ian T Zimmerman @ 1999-07-01 13:21 UTC (permalink / raw)
To: Chris Faylor
>>>>> "Chris" == Chris Faylor <cygwin@sourceware.cygnus.com> writes:
Chris> On Thu, Jul 01, 1999 at 06:52:08PM +0000, Ian T Zimmerman
Chris> wrote:
>> Hi, do the C_INCLUDE_PATH and LIBRARY_PATH envars work as
>> advertised (and as they work on Unix installataions of gcc &
>> friends)?
>>
>> I do this:
>>
>> amazon:~$ printenv C_INCLUDE_PATH
>> /usr/X11R6.4/LessTif/Motif2.0/include/:/usr/X11R6.4/include/
>> amazon:~$ ls -l /usr/X11R6.4/include/X11/Intrinsic.h -r--r--r--
>> 1 administ None 73459 Nov 3 1998
>> /usr/X11R6.4/include/X11/Intrinsic.h amazon:~$ cat
>> stupid_test.c #include <X11/Intrinsic.h> amazon:~$ gcc -E
>> stupid_test.c stupid_test.c:1: X11/Intrinsic.h: No such file or
>> directory # 1 "stupid_test.c"
Chris> Try doing a "gcc -v -E stupid_test.c" to see what libraries
Chris> are being searched.
amazon:~$ gcc -v -E stupid_test.c
Reading specs from d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\specs
gcc version egcs-2.91.57 19980901 (egcs-1.1 release)
d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\cpp.exe -lang-c -v -iprefix d:\C
YGWIN~1\H-I586~1\bin\..\lib/gcc-lib/i586-cygwin32\egcs-2.91.57\ -undef -D__GNUC__=2 -D__GNUC_MINOR__
=91 -Di386 -D_WIN32 -DWINNT -D_X86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdec
l=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x)) -D__i386__ -D_WIN32 -D__WINNT__ -D_X
86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((__cdecl__)) -D_
_declspec(x)=__attribute__((x)) -D__i386 -D__WINNT -Asystem(winnt) -Acpu(i386) -Amachine(i386) -rema
p -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -Di586 -Dpentium -D__i586 -D__i586__ -D__pe
ntium -D__pentium__ -D__CYGWIN32__ -D__CYGWIN__ stupid_test.c
GNU CPP version egcs-2.91.57 19980901 (egcs-1.1 release) (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:
d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\..\include
d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i586-cygwin32\includ
e
d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\include
\cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\..\include
\cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i586-cygwin32
\include
\cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\include
\usr\include
End of search list.
stupid_test.c:1: X11/Intrinsic.h: No such file or directory
# 1 "stupid_test.c"
amazon:~$
It sure looks like the environment has no effect whatsoever.
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: include and library paths
1999-07-01 13:21 ` Ian T Zimmerman
@ 1999-07-01 13:50 ` Chris Faylor
1999-07-01 14:11 ` Ian T Zimmerman
` (2 more replies)
1999-07-31 18:34 ` Ian T Zimmerman
1 sibling, 3 replies; 20+ messages in thread
From: Chris Faylor @ 1999-07-01 13:50 UTC (permalink / raw)
To: Ian T Zimmerman; +Cc: cygwin
On Thu, Jul 01, 1999 at 08:19:57PM +0000, Ian T Zimmerman wrote:
>>>>>> "Chris" == Chris Faylor <cygwin@sourceware.cygnus.com> writes:
>
> Chris> On Thu, Jul 01, 1999 at 06:52:08PM +0000, Ian T Zimmerman
> Chris> wrote:
> >> Hi, do the C_INCLUDE_PATH and LIBRARY_PATH envars work as
> >> advertised (and as they work on Unix installataions of gcc &
> >> friends)?
> >>
> >> I do this:
> >>
> >> amazon:~$ printenv C_INCLUDE_PATH
> >> /usr/X11R6.4/LessTif/Motif2.0/include/:/usr/X11R6.4/include/
> >> amazon:~$ ls -l /usr/X11R6.4/include/X11/Intrinsic.h -r--r--r--
> >> 1 administ None 73459 Nov 3 1998
> >> /usr/X11R6.4/include/X11/Intrinsic.h amazon:~$ cat
> >> stupid_test.c #include <X11/Intrinsic.h> amazon:~$ gcc -E
> >> stupid_test.c stupid_test.c:1: X11/Intrinsic.h: No such file or
> >> directory # 1 "stupid_test.c"
>
> Chris> Try doing a "gcc -v -E stupid_test.c" to see what libraries
> Chris> are being searched.
>
>amazon:~$ gcc -v -E stupid_test.c
>Reading specs from d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\specs
>gcc version egcs-2.91.57 19980901 (egcs-1.1 release)
> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\cpp.exe -lang-c -v -iprefix d:\C
>YGWIN~1\H-I586~1\bin\..\lib/gcc-lib/i586-cygwin32\egcs-2.91.57\ -undef -D__GNUC__=2 -D__GNUC_MINOR__
>=91 -Di386 -D_WIN32 -DWINNT -D_X86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdec
>l=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x)) -D__i386__ -D_WIN32 -D__WINNT__ -D_X
>86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((__cdecl__)) -D_
>_declspec(x)=__attribute__((x)) -D__i386 -D__WINNT -Asystem(winnt) -Acpu(i386) -Amachine(i386) -rema
>p -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -Di586 -Dpentium -D__i586 -D__i586__ -D__pe
>ntium -D__pentium__ -D__CYGWIN32__ -D__CYGWIN__ stupid_test.c
>GNU CPP version egcs-2.91.57 19980901 (egcs-1.1 release) (80386, BSD syntax)
>#include "..." search starts here:
>#include <...> search starts here:
> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\..\include
> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i586-cygwin32\includ
>e
> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\include
> \cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\..\include
> \cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i586-cygwin32
>\include
> \cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\include
> \usr\include
>End of search list.
>stupid_test.c:1: X11/Intrinsic.h: No such file or directory
># 1 "stupid_test.c"
>
>amazon:~$
Ok, next, how about a:
ls /usr/X116.4/LessTif/Motif2.0/include /usr/X11R6.4/include
?
If those work then I'll leave this to Mumit to comment.
-chris
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: include and library paths
1999-07-01 13:50 ` Chris Faylor
@ 1999-07-01 14:11 ` Ian T Zimmerman
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-01 14:15 ` Mumit Khan
1999-07-31 18:34 ` Chris Faylor
2 siblings, 1 reply; 20+ messages in thread
From: Ian T Zimmerman @ 1999-07-01 14:11 UTC (permalink / raw)
To: Chris Faylor
>>>>> "Chris" == Chris Faylor <cygwin@sourceware.cygnus.com> writes:
Chris> On Thu, Jul 01, 1999 at 08:19:57PM +0000, Ian T Zimmerman
Chris> wrote:
>>>>>>> "Chris" == Chris Faylor <cygwin@sourceware.cygnus.com>
>>>>>>> writes:
>>
Chris> On Thu, Jul 01, 1999 at 06:52:08PM +0000, Ian T Zimmerman
Chris> wrote:
>> >> Hi, do the C_INCLUDE_PATH and LIBRARY_PATH envars work as >>
>> advertised (and as they work on Unix installataions of gcc & >>
>> friends)? >> >> I do this: >> >> amazon:~$ printenv
>> C_INCLUDE_PATH >>
>> /usr/X11R6.4/LessTif/Motif2.0/include/:/usr/X11R6.4/include/ >>
>> amazon:~$ ls -l /usr/X11R6.4/include/X11/Intrinsic.h -r--r--r--
>> >> 1 administ None 73459 Nov 3 1998 >>
>> /usr/X11R6.4/include/X11/Intrinsic.h amazon:~$ cat >>
>> stupid_test.c #include <X11/Intrinsic.h> amazon:~$ gcc -E >>
>> stupid_test.c stupid_test.c:1: X11/Intrinsic.h: No such file or
>> >> directory # 1 "stupid_test.c"
>>
Chris> Try doing a "gcc -v -E stupid_test.c" to see what libraries
Chris> are being searched.
>> amazon:~$ gcc -v -E stupid_test.c Reading specs from
>> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\specs
>> gcc version egcs-2.91.57 19980901 (egcs-1.1 release)
>> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\cpp.exe
>> -lang-c -v -iprefix d:\C
>> YGWIN~1\H-I586~1\bin\..\lib/gcc-lib/i586-cygwin32\egcs-2.91.57\
>> -undef -D__GNUC__=2 -D__GNUC_MINOR__ =91 -Di386 -D_WIN32
>> -DWINNT -D_X86_=1 -D__STDC__=1
>> -D__stdcall=__attribute__((__stdcall__)) -D__cdec
>> l=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x))
>> -D__i386__ -D_WIN32 -D__WINNT__ -D_X 86_=1 -D__STDC__=1
>> -D__stdcall=__attribute__((__stdcall__))
>> -D__cdecl=__attribute__((__cdecl__)) -D_
>> _declspec(x)=__attribute__((x)) -D__i386 -D__WINNT
>> -Asystem(winnt) -Acpu(i386) -Amachine(i386) -rema p -Acpu(i386)
>> -Amachine(i386) -Di386 -D__i386 -D__i386__ -Di586 -Dpentium
>> -D__i586 -D__i586__ -D__pe ntium -D__pentium__ -D__CYGWIN32__
>> -D__CYGWIN__ stupid_test.c GNU CPP version egcs-2.91.57
>> 19980901 (egcs-1.1 release) (80386, BSD syntax) #include "..."
>> search starts here: #include <...> search starts here:
>> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\..\include
>> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i586-cygwin32\includ
>> e
>> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\include
>> \cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\..\include
>> \cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i586-cygwin32
>> \include
>> \cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\include
>> \usr\include End of search list. stupid_test.c:1:
>> X11/Intrinsic.h: No such file or directory # 1 "stupid_test.c"
>>
>> amazon:~$
Chris> Ok, next, how about a:
Chris> ls /usr/X116.4/LessTif/Motif2.0/include
Chris> /usr/X11R6.4/include
This was part of my original post:
amazon:~$ ls -l /usr/X11R6.4/include/X11/Intrinsic.h
-r--r--r-- 1 administ None 73459 Nov 3 1998 /usr/X11R6.4/include/X11/Intrinsic.h
amazon:~$
And just to be sure:
amazon:~$ ls -la /usr/X11R6.4/include/
total 43
drwxr-xr-x 11 administ None 0 May 11 11:30 .
drwxr-xr-x 10 administ None 0 May 11 11:30 ..
drwxr-xr-x 2 administ None 0 Apr 19 12:39 AFM
-r--r--r-- 1 administ None 2142 Feb 8 1997 Actions.h
-r--r--r-- 1 administ None 2929 Feb 8 1997 Caption.h
-r--r--r-- 1 administ None 2572 Feb 8 1997 CaptionP.h
-r--r--r-- 1 administ None 1251 Feb 8 1997 Cell.h
-r--r--r-- 1 administ None 1640 Feb 8 1997 CellP.h
-r--r--r-- 1 administ None 2060 Feb 8 1997 Clip.h
-r--r--r-- 1 administ None 2571 Feb 8 1997 ClipP.h
-r--r--r-- 1 administ None 3262 Feb 8 1997 Converters.h
-r--r--r-- 1 administ None 3658 Feb 8 1997 Create.h
-r--r--r-- 1 administ None 2028 Feb 8 1997 Draw.h
-r--r--r-- 1 administ None 15502 Jul 10 1997 Macros.h
-r--r--r-- 1 administ None 21966 May 3 1997 Matrix.h
-r--r--r-- 1 administ None 2766 Feb 8 1997 Methods.h
drwxr-xr-x 2 administ None 0 May 7 12:06 Mrm
-r--r--r-- 1 administ None 1944 Feb 8 1997 ScrollMgr.h
-r--r--r-- 1 administ None 1599 Feb 8 1997 Shadow.h
-r--r--r-- 1 administ None 3017 Feb 8 1997 Utils.h
drwxr-xr-x 2 administ None 0 Apr 19 12:39 Vk
drwxr-xr-x 11 administ None 0 Mar 18 20:56 X11
drwxr-xr-x 2 administ None 0 Feb 5 12:13 Xarm
drwxr-xr-x 2 administ None 0 Jan 29 13:55 Xlt
drwxr-xr-x 3 administ None 0 May 7 12:06 Xm
drwxr-xr-x 2 administ None 0 Feb 5 12:13 Xmext
drwxr-xr-x 2 administ None 0 Mar 16 15:50 include
-r--r--r-- 1 administ None 1385 Feb 8 1997 patchlevel.h
amazon:~$
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: include and library paths
1999-07-01 14:11 ` Ian T Zimmerman
@ 1999-07-31 18:34 ` Ian T Zimmerman
0 siblings, 0 replies; 20+ messages in thread
From: Ian T Zimmerman @ 1999-07-31 18:34 UTC (permalink / raw)
To: Chris Faylor
>>>>> "Chris" == Chris Faylor <cygwin@sourceware.cygnus.com> writes:
Chris> On Thu, Jul 01, 1999 at 08:19:57PM +0000, Ian T Zimmerman
Chris> wrote:
>>>>>>> "Chris" == Chris Faylor <cygwin@sourceware.cygnus.com>
>>>>>>> writes:
>>
Chris> On Thu, Jul 01, 1999 at 06:52:08PM +0000, Ian T Zimmerman
Chris> wrote:
>> >> Hi, do the C_INCLUDE_PATH and LIBRARY_PATH envars work as >>
>> advertised (and as they work on Unix installataions of gcc & >>
>> friends)? >> >> I do this: >> >> amazon:~$ printenv
>> C_INCLUDE_PATH >>
>> /usr/X11R6.4/LessTif/Motif2.0/include/:/usr/X11R6.4/include/ >>
>> amazon:~$ ls -l /usr/X11R6.4/include/X11/Intrinsic.h -r--r--r--
>> >> 1 administ None 73459 Nov 3 1998 >>
>> /usr/X11R6.4/include/X11/Intrinsic.h amazon:~$ cat >>
>> stupid_test.c #include <X11/Intrinsic.h> amazon:~$ gcc -E >>
>> stupid_test.c stupid_test.c:1: X11/Intrinsic.h: No such file or
>> >> directory # 1 "stupid_test.c"
>>
Chris> Try doing a "gcc -v -E stupid_test.c" to see what libraries
Chris> are being searched.
>> amazon:~$ gcc -v -E stupid_test.c Reading specs from
>> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\specs
>> gcc version egcs-2.91.57 19980901 (egcs-1.1 release)
>> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\cpp.exe
>> -lang-c -v -iprefix d:\C
>> YGWIN~1\H-I586~1\bin\..\lib/gcc-lib/i586-cygwin32\egcs-2.91.57\
>> -undef -D__GNUC__=2 -D__GNUC_MINOR__ =91 -Di386 -D_WIN32
>> -DWINNT -D_X86_=1 -D__STDC__=1
>> -D__stdcall=__attribute__((__stdcall__)) -D__cdec
>> l=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x))
>> -D__i386__ -D_WIN32 -D__WINNT__ -D_X 86_=1 -D__STDC__=1
>> -D__stdcall=__attribute__((__stdcall__))
>> -D__cdecl=__attribute__((__cdecl__)) -D_
>> _declspec(x)=__attribute__((x)) -D__i386 -D__WINNT
>> -Asystem(winnt) -Acpu(i386) -Amachine(i386) -rema p -Acpu(i386)
>> -Amachine(i386) -Di386 -D__i386 -D__i386__ -Di586 -Dpentium
>> -D__i586 -D__i586__ -D__pe ntium -D__pentium__ -D__CYGWIN32__
>> -D__CYGWIN__ stupid_test.c GNU CPP version egcs-2.91.57
>> 19980901 (egcs-1.1 release) (80386, BSD syntax) #include "..."
>> search starts here: #include <...> search starts here:
>> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\..\include
>> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i586-cygwin32\includ
>> e
>> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\include
>> \cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\..\include
>> \cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i586-cygwin32
>> \include
>> \cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\include
>> \usr\include End of search list. stupid_test.c:1:
>> X11/Intrinsic.h: No such file or directory # 1 "stupid_test.c"
>>
>> amazon:~$
Chris> Ok, next, how about a:
Chris> ls /usr/X116.4/LessTif/Motif2.0/include
Chris> /usr/X11R6.4/include
This was part of my original post:
amazon:~$ ls -l /usr/X11R6.4/include/X11/Intrinsic.h
-r--r--r-- 1 administ None 73459 Nov 3 1998 /usr/X11R6.4/include/X11/Intrinsic.h
amazon:~$
And just to be sure:
amazon:~$ ls -la /usr/X11R6.4/include/
total 43
drwxr-xr-x 11 administ None 0 May 11 11:30 .
drwxr-xr-x 10 administ None 0 May 11 11:30 ..
drwxr-xr-x 2 administ None 0 Apr 19 12:39 AFM
-r--r--r-- 1 administ None 2142 Feb 8 1997 Actions.h
-r--r--r-- 1 administ None 2929 Feb 8 1997 Caption.h
-r--r--r-- 1 administ None 2572 Feb 8 1997 CaptionP.h
-r--r--r-- 1 administ None 1251 Feb 8 1997 Cell.h
-r--r--r-- 1 administ None 1640 Feb 8 1997 CellP.h
-r--r--r-- 1 administ None 2060 Feb 8 1997 Clip.h
-r--r--r-- 1 administ None 2571 Feb 8 1997 ClipP.h
-r--r--r-- 1 administ None 3262 Feb 8 1997 Converters.h
-r--r--r-- 1 administ None 3658 Feb 8 1997 Create.h
-r--r--r-- 1 administ None 2028 Feb 8 1997 Draw.h
-r--r--r-- 1 administ None 15502 Jul 10 1997 Macros.h
-r--r--r-- 1 administ None 21966 May 3 1997 Matrix.h
-r--r--r-- 1 administ None 2766 Feb 8 1997 Methods.h
drwxr-xr-x 2 administ None 0 May 7 12:06 Mrm
-r--r--r-- 1 administ None 1944 Feb 8 1997 ScrollMgr.h
-r--r--r-- 1 administ None 1599 Feb 8 1997 Shadow.h
-r--r--r-- 1 administ None 3017 Feb 8 1997 Utils.h
drwxr-xr-x 2 administ None 0 Apr 19 12:39 Vk
drwxr-xr-x 11 administ None 0 Mar 18 20:56 X11
drwxr-xr-x 2 administ None 0 Feb 5 12:13 Xarm
drwxr-xr-x 2 administ None 0 Jan 29 13:55 Xlt
drwxr-xr-x 3 administ None 0 May 7 12:06 Xm
drwxr-xr-x 2 administ None 0 Feb 5 12:13 Xmext
drwxr-xr-x 2 administ None 0 Mar 16 15:50 include
-r--r--r-- 1 administ None 1385 Feb 8 1997 patchlevel.h
amazon:~$
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: include and library paths
1999-07-01 13:50 ` Chris Faylor
1999-07-01 14:11 ` Ian T Zimmerman
@ 1999-07-01 14:15 ` Mumit Khan
1999-07-01 14:36 ` Ian T Zimmerman
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` Chris Faylor
2 siblings, 2 replies; 20+ messages in thread
From: Mumit Khan @ 1999-07-01 14:15 UTC (permalink / raw)
To: cygwin; +Cc: Ian T Zimmerman
Chris Faylor <cygwin@sourceware.cygnus.com> writes:
> On Thu, Jul 01, 1999 at 08:19:57PM +0000, Ian T Zimmerman wrote:
> >amazon:~$ gcc -v -E stupid_test.c
> >Reading specs from d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egc
> s-2.91.57\specs
^^^^^^^
In any new port, GCC moves much faster than compared to a stable port;
x86-win32 happens to be one where every release fixes tons of bugs,
and 2.91.57 (aka egcs-1.1) is considered ancient by now.
It's one of about 150 known bugs.
> Ok, next, how about a:
>
> ls /usr/X116.4/LessTif/Motif2.0/include /usr/X11R6.4/include
>
> ?
>
> If those work then I'll leave this to Mumit to comment.
>
Upgrade.
How about trying the "GCC" way -- use -I/usr/X11R6.4/include -I...?
My personal opinion -- C_INCLUDE_PATH etc should never be used. You should
see the number of bug reports from people who "forget" that they have these
variables set in the environment and of course gets the wrong include file
and all hell breaks loose. I like -I, -L, etc options that are visible when
compiling/linking a file.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: include and library paths
1999-07-01 14:15 ` Mumit Khan
@ 1999-07-01 14:36 ` Ian T Zimmerman
1999-07-01 15:00 ` Mumit Khan
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-31 18:34 ` Mumit Khan
1 sibling, 2 replies; 20+ messages in thread
From: Ian T Zimmerman @ 1999-07-01 14:36 UTC (permalink / raw)
To: Mumit Khan; +Cc: cygwin
>>>>> "Mumit" == Mumit Khan <khan@xraylith.wisc.EDU> writes:
Mumit> How about trying the "GCC" way -- use
Mumit> -I/usr/X11R6.4/include -I...?
Mumit> My personal opinion -- C_INCLUDE_PATH etc should never be
Mumit> used. You should see the number of bug reports from people
Mumit> who "forget" that they have these variables set in the
Mumit> environment and of course gets the wrong include file and
Mumit> all hell breaks loose. I like -I, -L, etc options that are
Mumit> visible when compiling/linking a file.
Except that my original situation involved a configure failure. I
know that I can pass extra options like this
CPPFLAGS=-I/foo/bar configure
but that only works for GNU autoconf style scripts, and only the clean
ones among these. (Ie. the ones that use CPPFLAGS and not some other
home cooked name, and that initialize it from the environment.)
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: include and library paths
1999-07-01 14:36 ` Ian T Zimmerman
@ 1999-07-01 15:00 ` Mumit Khan
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` Ian T Zimmerman
1 sibling, 1 reply; 20+ messages in thread
From: Mumit Khan @ 1999-07-01 15:00 UTC (permalink / raw)
To: Ian T Zimmerman; +Cc: cygwin
Ian T Zimmerman <itz@lbin.com> writes:
> >>>>> "Mumit" == Mumit Khan <khan@xraylith.wisc.EDU> writes:
>
> Mumit> How about trying the "GCC" way -- use
> Mumit> -I/usr/X11R6.4/include -I...?
>
> Mumit> My personal opinion -- C_INCLUDE_PATH etc should never be
> Mumit> used. You should see the number of bug reports from people
> Mumit> who "forget" that they have these variables set in the
> Mumit> environment and of course gets the wrong include file and
> Mumit> all hell breaks loose. I like -I, -L, etc options that are
> Mumit> visible when compiling/linking a file.
>
> Except that my original situation involved a configure failure. I
> know that I can pass extra options like this
>
> CPPFLAGS=-I/foo/bar configure
>
> but that only works for GNU autoconf style scripts, and only the clean
> ones among these. (Ie. the ones that use CPPFLAGS and not some other
> home cooked name, and that initialize it from the environment.)
>
Try ``CC="gcc -I/foo:/bar" configure'' instead of using CPPFLAGS. It's
usually a better bet when using not-so-well-behaved configure-style
script.
The bug has been fixed long since, so all you need to do is upgrade.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: include and library paths
1999-07-01 15:00 ` Mumit Khan
@ 1999-07-31 18:34 ` Mumit Khan
0 siblings, 0 replies; 20+ messages in thread
From: Mumit Khan @ 1999-07-31 18:34 UTC (permalink / raw)
To: Ian T Zimmerman; +Cc: cygwin
Ian T Zimmerman <itz@lbin.com> writes:
> >>>>> "Mumit" == Mumit Khan <khan@xraylith.wisc.EDU> writes:
>
> Mumit> How about trying the "GCC" way -- use
> Mumit> -I/usr/X11R6.4/include -I...?
>
> Mumit> My personal opinion -- C_INCLUDE_PATH etc should never be
> Mumit> used. You should see the number of bug reports from people
> Mumit> who "forget" that they have these variables set in the
> Mumit> environment and of course gets the wrong include file and
> Mumit> all hell breaks loose. I like -I, -L, etc options that are
> Mumit> visible when compiling/linking a file.
>
> Except that my original situation involved a configure failure. I
> know that I can pass extra options like this
>
> CPPFLAGS=-I/foo/bar configure
>
> but that only works for GNU autoconf style scripts, and only the clean
> ones among these. (Ie. the ones that use CPPFLAGS and not some other
> home cooked name, and that initialize it from the environment.)
>
Try ``CC="gcc -I/foo:/bar" configure'' instead of using CPPFLAGS. It's
usually a better bet when using not-so-well-behaved configure-style
script.
The bug has been fixed long since, so all you need to do is upgrade.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: include and library paths
1999-07-01 14:36 ` Ian T Zimmerman
1999-07-01 15:00 ` Mumit Khan
@ 1999-07-31 18:34 ` Ian T Zimmerman
1 sibling, 0 replies; 20+ messages in thread
From: Ian T Zimmerman @ 1999-07-31 18:34 UTC (permalink / raw)
To: Mumit Khan; +Cc: cygwin
>>>>> "Mumit" == Mumit Khan <khan@xraylith.wisc.EDU> writes:
Mumit> How about trying the "GCC" way -- use
Mumit> -I/usr/X11R6.4/include -I...?
Mumit> My personal opinion -- C_INCLUDE_PATH etc should never be
Mumit> used. You should see the number of bug reports from people
Mumit> who "forget" that they have these variables set in the
Mumit> environment and of course gets the wrong include file and
Mumit> all hell breaks loose. I like -I, -L, etc options that are
Mumit> visible when compiling/linking a file.
Except that my original situation involved a configure failure. I
know that I can pass extra options like this
CPPFLAGS=-I/foo/bar configure
but that only works for GNU autoconf style scripts, and only the clean
ones among these. (Ie. the ones that use CPPFLAGS and not some other
home cooked name, and that initialize it from the environment.)
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: include and library paths
1999-07-01 14:15 ` Mumit Khan
1999-07-01 14:36 ` Ian T Zimmerman
@ 1999-07-31 18:34 ` Mumit Khan
1 sibling, 0 replies; 20+ messages in thread
From: Mumit Khan @ 1999-07-31 18:34 UTC (permalink / raw)
To: cygwin; +Cc: Ian T Zimmerman
Chris Faylor <cygwin@sourceware.cygnus.com> writes:
> On Thu, Jul 01, 1999 at 08:19:57PM +0000, Ian T Zimmerman wrote:
> >amazon:~$ gcc -v -E stupid_test.c
> >Reading specs from d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egc
> s-2.91.57\specs
^^^^^^^
In any new port, GCC moves much faster than compared to a stable port;
x86-win32 happens to be one where every release fixes tons of bugs,
and 2.91.57 (aka egcs-1.1) is considered ancient by now.
It's one of about 150 known bugs.
> Ok, next, how about a:
>
> ls /usr/X116.4/LessTif/Motif2.0/include /usr/X11R6.4/include
>
> ?
>
> If those work then I'll leave this to Mumit to comment.
>
Upgrade.
How about trying the "GCC" way -- use -I/usr/X11R6.4/include -I...?
My personal opinion -- C_INCLUDE_PATH etc should never be used. You should
see the number of bug reports from people who "forget" that they have these
variables set in the environment and of course gets the wrong include file
and all hell breaks loose. I like -I, -L, etc options that are visible when
compiling/linking a file.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: include and library paths
1999-07-01 13:50 ` Chris Faylor
1999-07-01 14:11 ` Ian T Zimmerman
1999-07-01 14:15 ` Mumit Khan
@ 1999-07-31 18:34 ` Chris Faylor
2 siblings, 0 replies; 20+ messages in thread
From: Chris Faylor @ 1999-07-31 18:34 UTC (permalink / raw)
To: Ian T Zimmerman; +Cc: cygwin
On Thu, Jul 01, 1999 at 08:19:57PM +0000, Ian T Zimmerman wrote:
>>>>>> "Chris" == Chris Faylor <cygwin@sourceware.cygnus.com> writes:
>
> Chris> On Thu, Jul 01, 1999 at 06:52:08PM +0000, Ian T Zimmerman
> Chris> wrote:
> >> Hi, do the C_INCLUDE_PATH and LIBRARY_PATH envars work as
> >> advertised (and as they work on Unix installataions of gcc &
> >> friends)?
> >>
> >> I do this:
> >>
> >> amazon:~$ printenv C_INCLUDE_PATH
> >> /usr/X11R6.4/LessTif/Motif2.0/include/:/usr/X11R6.4/include/
> >> amazon:~$ ls -l /usr/X11R6.4/include/X11/Intrinsic.h -r--r--r--
> >> 1 administ None 73459 Nov 3 1998
> >> /usr/X11R6.4/include/X11/Intrinsic.h amazon:~$ cat
> >> stupid_test.c #include <X11/Intrinsic.h> amazon:~$ gcc -E
> >> stupid_test.c stupid_test.c:1: X11/Intrinsic.h: No such file or
> >> directory # 1 "stupid_test.c"
>
> Chris> Try doing a "gcc -v -E stupid_test.c" to see what libraries
> Chris> are being searched.
>
>amazon:~$ gcc -v -E stupid_test.c
>Reading specs from d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\specs
>gcc version egcs-2.91.57 19980901 (egcs-1.1 release)
> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\cpp.exe -lang-c -v -iprefix d:\C
>YGWIN~1\H-I586~1\bin\..\lib/gcc-lib/i586-cygwin32\egcs-2.91.57\ -undef -D__GNUC__=2 -D__GNUC_MINOR__
>=91 -Di386 -D_WIN32 -DWINNT -D_X86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdec
>l=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x)) -D__i386__ -D_WIN32 -D__WINNT__ -D_X
>86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((__cdecl__)) -D_
>_declspec(x)=__attribute__((x)) -D__i386 -D__WINNT -Asystem(winnt) -Acpu(i386) -Amachine(i386) -rema
>p -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -Di586 -Dpentium -D__i586 -D__i586__ -D__pe
>ntium -D__pentium__ -D__CYGWIN32__ -D__CYGWIN__ stupid_test.c
>GNU CPP version egcs-2.91.57 19980901 (egcs-1.1 release) (80386, BSD syntax)
>#include "..." search starts here:
>#include <...> search starts here:
> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\..\include
> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i586-cygwin32\includ
>e
> d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\include
> \cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\..\include
> \cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i586-cygwin32
>\include
> \cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\include
> \usr\include
>End of search list.
>stupid_test.c:1: X11/Intrinsic.h: No such file or directory
># 1 "stupid_test.c"
>
>amazon:~$
Ok, next, how about a:
ls /usr/X116.4/LessTif/Motif2.0/include /usr/X11R6.4/include
?
If those work then I'll leave this to Mumit to comment.
-chris
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: include and library paths
1999-07-01 13:21 ` Ian T Zimmerman
1999-07-01 13:50 ` Chris Faylor
@ 1999-07-31 18:34 ` Ian T Zimmerman
1 sibling, 0 replies; 20+ messages in thread
From: Ian T Zimmerman @ 1999-07-31 18:34 UTC (permalink / raw)
To: Chris Faylor
>>>>> "Chris" == Chris Faylor <cygwin@sourceware.cygnus.com> writes:
Chris> On Thu, Jul 01, 1999 at 06:52:08PM +0000, Ian T Zimmerman
Chris> wrote:
>> Hi, do the C_INCLUDE_PATH and LIBRARY_PATH envars work as
>> advertised (and as they work on Unix installataions of gcc &
>> friends)?
>>
>> I do this:
>>
>> amazon:~$ printenv C_INCLUDE_PATH
>> /usr/X11R6.4/LessTif/Motif2.0/include/:/usr/X11R6.4/include/
>> amazon:~$ ls -l /usr/X11R6.4/include/X11/Intrinsic.h -r--r--r--
>> 1 administ None 73459 Nov 3 1998
>> /usr/X11R6.4/include/X11/Intrinsic.h amazon:~$ cat
>> stupid_test.c #include <X11/Intrinsic.h> amazon:~$ gcc -E
>> stupid_test.c stupid_test.c:1: X11/Intrinsic.h: No such file or
>> directory # 1 "stupid_test.c"
Chris> Try doing a "gcc -v -E stupid_test.c" to see what libraries
Chris> are being searched.
amazon:~$ gcc -v -E stupid_test.c
Reading specs from d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\specs
gcc version egcs-2.91.57 19980901 (egcs-1.1 release)
d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\cpp.exe -lang-c -v -iprefix d:\C
YGWIN~1\H-I586~1\bin\..\lib/gcc-lib/i586-cygwin32\egcs-2.91.57\ -undef -D__GNUC__=2 -D__GNUC_MINOR__
=91 -Di386 -D_WIN32 -DWINNT -D_X86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdec
l=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x)) -D__i386__ -D_WIN32 -D__WINNT__ -D_X
86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D__cdecl=__attribute__((__cdecl__)) -D_
_declspec(x)=__attribute__((x)) -D__i386 -D__WINNT -Asystem(winnt) -Acpu(i386) -Amachine(i386) -rema
p -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -Di586 -Dpentium -D__i586 -D__i586__ -D__pe
ntium -D__pentium__ -D__CYGWIN32__ -D__CYGWIN__ stupid_test.c
GNU CPP version egcs-2.91.57 19980901 (egcs-1.1 release) (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:
d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\..\include
d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i586-cygwin32\includ
e
d:\CYGWIN~1\H-I586~1\bin\..\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\include
\cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\..\include
\cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\..\..\..\..\i586-cygwin32
\include
\cygnus\cygwin-b20\H-i586-cygwin32\lib\gcc-lib\i586-cygwin32\egcs-2.91.57\include
\usr\include
End of search list.
stupid_test.c:1: X11/Intrinsic.h: No such file or directory
# 1 "stupid_test.c"
amazon:~$
It sure looks like the environment has no effect whatsoever.
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: include and library paths
1999-07-01 12:19 ` Chris Faylor
1999-07-01 13:21 ` Ian T Zimmerman
@ 1999-07-31 18:34 ` Chris Faylor
1 sibling, 0 replies; 20+ messages in thread
From: Chris Faylor @ 1999-07-31 18:34 UTC (permalink / raw)
To: Ian T Zimmerman; +Cc: cygwin
On Thu, Jul 01, 1999 at 06:52:08PM +0000, Ian T Zimmerman wrote:
>Hi, do the C_INCLUDE_PATH and LIBRARY_PATH envars work as advertised
>(and as they work on Unix installataions of gcc & friends)?
>
>I do this:
>
>amazon:~$ printenv C_INCLUDE_PATH
>/usr/X11R6.4/LessTif/Motif2.0/include/:/usr/X11R6.4/include/
>amazon:~$ ls -l /usr/X11R6.4/include/X11/Intrinsic.h
>-r--r--r-- 1 administ None 73459 Nov 3 1998 /usr/X11R6.4/include/X11/Intrinsic.h
>amazon:~$ cat stupid_test.c
>#include <X11/Intrinsic.h>
>amazon:~$ gcc -E stupid_test.c
>stupid_test.c:1: X11/Intrinsic.h: No such file or directory
># 1 "stupid_test.c"
Try doing a "gcc -v -E stupid_test.c" to see what libraries are
being searched.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* include and library paths
1999-07-01 11:53 Ian T Zimmerman
1999-07-01 12:19 ` Chris Faylor
@ 1999-07-31 18:34 ` Ian T Zimmerman
1 sibling, 0 replies; 20+ messages in thread
From: Ian T Zimmerman @ 1999-07-31 18:34 UTC (permalink / raw)
To: cygwin
Hi, do the C_INCLUDE_PATH and LIBRARY_PATH envars work as advertised
(and as they work on Unix installataions of gcc & friends)?
I do this:
amazon:~$ printenv C_INCLUDE_PATH
/usr/X11R6.4/LessTif/Motif2.0/include/:/usr/X11R6.4/include/
amazon:~$ ls -l /usr/X11R6.4/include/X11/Intrinsic.h
-r--r--r-- 1 administ None 73459 Nov 3 1998 /usr/X11R6.4/include/X11/Intrinsic.h
amazon:~$ cat stupid_test.c
#include <X11/Intrinsic.h>
amazon:~$ gcc -E stupid_test.c
stupid_test.c:1: X11/Intrinsic.h: No such file or directory
# 1 "stupid_test.c"
amazon:~$
?!?
--
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324, San Francisco, California 94107
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~1999-07-31 18:34 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-07-01 12:11 include and library paths Earnie Boyd
1999-07-31 18:34 ` Earnie Boyd
-- strict thread matches above, loose matches on Subject: below --
1999-07-22 2:33 Joseph M. Hinkle
1999-07-31 18:34 ` Joseph M. Hinkle
1999-07-01 11:53 Ian T Zimmerman
1999-07-01 12:19 ` Chris Faylor
1999-07-01 13:21 ` Ian T Zimmerman
1999-07-01 13:50 ` Chris Faylor
1999-07-01 14:11 ` Ian T Zimmerman
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-01 14:15 ` Mumit Khan
1999-07-01 14:36 ` Ian T Zimmerman
1999-07-01 15:00 ` Mumit Khan
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` Chris Faylor
1999-07-31 18:34 ` Ian T Zimmerman
1999-07-31 18:34 ` Chris Faylor
1999-07-31 18:34 ` Ian T Zimmerman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).