You can use the -I option to set a include path. Here is the info from
the manpage for gcc:
Directory Options
-Bprefix -Idir -iquotedir -Ldir -specs=file -I-
-I dir
Add the directory dir to the list of directories to be searched for
header files. Directories named by -I are searched before the
standard system include directories. If the directory dir is a
standard system include directory, the option is ignored to ensure
that the default search order for system directories and the spe-
cial treatment of system headers are not defeated .
-Pavan
On Nov 19, 2007 8:47 AM, vichy <vichy.kuo@xxxxxxxxx> wrote:
> Dear all:
> Below are my source code.
> #include<stdio.h>
> #include<asm-i386/Types.h>
>
> int main(void){
> u64 u64value;
>
> u64value = 0x2e32;
> printf("u64value = %0x\n",u64value);
> }
>
> While compiling it, the gcc tells me that it cannot find the Type.h.
> I also type gcc -v and get message as below
> [root@localhost ~]# gcc -v
> Using built-in specs.
> Target: i386-redhat-linux
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --enable-checking=release --with-system-zlib --enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-libgcj-multifile
> --enable-languages=c,c++,objc,obj-c++,java,fortran,ada
> --enable-java-awt=gtk --disable-dssi
> --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
> --with-cpu=generic --host=i386-redhat-linux
> Thread model: posix
> gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)
>
> I have read the gcc official document but it seems doesn't mention
> where to set or get the standard include path.
> Would someone please tell me where can I find the document which will
> clarify my concern?
>
> Sincerely Yours,
> vichy
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
> Please read the FAQ at http://kernelnewbies.org/FAQ
>
>
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
