Error No Include Path In Which To Search For Stdint.h
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up error: no include path in which to search for stdio.h up vote 3 down vote favorite I used to be able to compile C programs, but now I can't: $ cat helloworld.c #include int main(void) { printf("Hello, world!\n"); return 0; } $ gcc helloworld.c helloworld.c:1:19: error: no include path in which to search for stdio.h Yes, I do have /usr/include/stdio.h . Yes, build-essentials is installed. This problem began after I modified my ~/.bashrc to run a program installed in my user directory. I know this is what's wrong because if I remove ~/.bashrc, it works. What environment variable would be shadowing /usr/include as an include path? c linux gcc bash share|improve this question asked Nov 21 '10 at 7:10 Joey Adams 19.1k85591 4 Pasting the contents of your .bashrc would be helpful. –cdhowie Nov 21 '10 at 7:12 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted The problem was that I had another GCC in my PATH: $ which gcc /home/joey/gcc4ti/bin/gcc When I was trying to compile "Hello World", it was running a compiler for a 68000, not my system compiler :D I had this in my ~/.bashrc: export PATH="/home/joey/gcc4ti/bin:$PATH" Because paths are scanned in order, the gcc in /home/joey/gcc4ti/bin is seen first. I changed it to: export PATH="$PATH:/home/joey/gcc4ti/bin" share|improve thi
in /usr/include/idn-int.h Date: Tue, 19 Jun 2007 23:57:21 +0200 User-agent: Mutt/1.5.14 (2007-02-28) Hello everyone, I have a problem with using libidn; I tried to compile mutt (1.5.9 and CVS) with libidn support, but got the following error in both cases: gcc -DPKGDATADIR=\"/usr/share/mutt\" -DSYSCONFDIR=\"/etc\" -DBINDIR=\"/usr/bin\" -DMUTTLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H=1 -I. -I. -I. -I./imap -Iintl -I./intl -I/usr/include -Wall -pedantic -O -march=pentium3 -pipe -O3 -g -MT addrbook.o -MD -MP -MF .deps/addrbook.Tpo -c -o addrbook.o addrbook.c In file included from /usr/include/idna.h:31, from mutt_idna.h:26, from addrbook.c:28: /usr/include/idn-int.h:48:27: error: no include path in which to http://stackoverflow.com/questions/4236827/error-no-include-path-in-which-to-search-for-stdio-h search for stdint.h /usr/include/idn-int.h uses a #include_next which fails because the include path past /usr/include is empty as is evident from the gcc call. I do not understand why idn-int.h uses #include_next instead of #include. Is this a bug, or is there something wrong in the way mutt uses libidn, or something in the layour of https://lists.gnu.org/archive/html/help-libidn/2007-06/msg00001.html my include files? When I change the #include_next to an #include I can compile mutt without problems. Please see: http://bugs.sourcemage.org/show_bug.cgi?id=13857 Kind regards, Remko van der Vossen. pgpJQtjmELMFA.pgp Description: PGP signature reply via email to [Prev in Thread] Current Thread [Next in Thread] problem with #include_next in /usr/include/idn-int.h, Remko van der Vossen<= Re: problem with #include_next in /usr/include/idn-int.h, Simon Josefsson, 2007/06/20 Re: problem with #include_next in /usr/include/idn-int.h, Paul Eggert, 2007/06/20 Re: problem with #include_next in /usr/include/idn-int.h, Bruno Haible, 2007/06/21 proposed changes to fchdir, iconv_open, locale, netinet_in, sys_select, sys_socket, sysexits, Paul Eggert, 2007/06/21 Re: proposed changes to fchdir, iconv_open, locale, netinet_in, sys_select, sys_socket, sysexits, Bruno Haible, 2007/06/21 Re: proposed changes to fchdir, iconv_open, locale, netinet_in, sys_select, sys_socket, sysexits, Paul Eggert, 2007/06/21 Re: problem with #include_next in /usr/include/idn-int.h, Paul Eggert, 2007/06/21 Prev by Date: Public git repository Next by Date: Re: problem with #include_next in /usr/include/idn-int.h Previous by thread: Public git repository Next by thread: Re: problem with #include_next in /usr/include/idn-int.h Index(es): Date Thread
instructions: Windows Mac Red Hat Linux Ubuntu Click URL instructions: Right-click on ad, choose "Copy Link", then paste here → (This may not be possible with some types of ads) More information about our ad policies X You seem https://sourceforge.net/p/genode/mailman/message/34569540/ to have CSS turned off. Please don't fill out this field. You seem to http://osdir.com/ml/gnu.libidn.general/2007-08/msg00000.html have CSS turned off. Please don't fill out this field. Briefly describe the problem (required): Upload screenshot of ad (required): Select a file, or drag & drop file here. ✔ ✘ Please provide the ad click URL, if possible: Home Browse Genode OS Framework Mailing Lists Genode OS Framework Tool kit for building highly secure special-purpose operating systems error no Brought to you by: chelmuth, nfeske Summary Files Reviews Support News Mailing Lists Discussion Code genode-announce genode-main From: Adrien de GRAEVE - 2015-10-21 20:24:41 Attachments: Message as HTML Hi everyone, I tried to make compile SEL4 + GENODE. However, I must admit that this is a fail from my side. The demo linux is compiling fine, but regarding sel4 I cannot make it work due to standard lib header missing. To error no include make it happen, I simply followed the tutorial from Norman (step 1). I managed to make things work until make kernel command. After that I discovered that it was not executing the right kernel.mk file (there is one already delivered in latest sources), It compiles fine if I adapt a little bit CFLAGS. Then the issue comes when trying to test the make run/test that is failing differently than what is described in the tutorial. (In fact, it is supposed to work in the tutorial) It may be for sure a simple issue, but I don't really understand why I have this issue while compiling test and not the kernel... The issue is the following: error: no include path in which to search for stdint.h (and same for assert.h) Do you think you could help me to figure out this issue, and maybe document it in your web page ? Here is the trace below (I have a Ubuntu 14.04 LTS & x64 installation) *adg@...:~/dev/genode/genode/repos/base-sel4$ make run/test VERBOSE=* *test -f "/home/adg/dev/genode/genode/repos/base-sel4/run/test.run" || (echo "Error: No run script for test"; exit -1)* *~/dev/genode/genode/tool/run/run --genode-dir ~/dev/genode/genode \* * --name test \* * --specs "sel4 x86_32 x86 32bit" \* * --repositories "/home/adg/dev/genode/genode/repos/base-sel4 /home/adg/dev/genode/genode/repos/base" \* * --cross-dev-prefix "/usr/local/genode-gcc/bin/genode-x86-" \* * --qemu-args "" \* * \* * --include /home/adg/dev/genode/genode/repos/base-sel4/run
> > I have a problem with using libidn; > > I tried to compile mutt (1.5.9 and CVS) with libidn support, but got the > following error in both cases: > > gcc -DPKGDATADIR=\"/usr/share/mutt\" -DSYSCONFDIR=\"/etc\" > -DBINDIR=\"/usr/bin\" -DMUTTLOCALEDIR=\"/usr/share/locale\" > -DHAVE_CONFIG_H=1 -I. -I. -I. -I./imap -Iintl -I./intl -I/usr/include > -Wall -pedantic -O -march=pentium3 -pipe -O3 -g -MT addrbook.o -MD -MP > -MF .deps/addrbook.Tpo -c -o addrbook.o addrbook.c > In file included from /usr/include/idna.h:31, > from mutt_idna.h:26, > from addrbook.c:28: > /usr/include/idn-int.h:48:27: error: no include path in which to search > for stdint.h > > /usr/include/idn-int.h uses a #include_next which fails > because the include path past /usr/include is empty as is evident from > the gcc call. > > I do not understand why idn-int.h uses #include_next instead of > #include. Is this a bug, or is there something wrong in the way mutt > uses libidn, or something in the layour of my include files? > > When I change the #include_next to an #include I can > compile mutt without problems. > > Please see: http://bugs.sourcemage.org/show_bug.cgi?id=13857 Hello again everyone, The problem seems to persist after version 1.0 of libidn. Were the proposed changes not committed or not effective? I still receive the same error when trying to compile mutt with libidn support. Kind regards, Remko van der Vossen. pgpY5ufxb5Q5V.pgp Description: PGP signature _______________________________________________ Help-libidn mailing list Help-libidn@xxxxxxx http://lists.gnu.org/mailman/listinfo/help-libidn Thread at a glance: Next Message by Date: Compile problem under windows Hello list! I am currently trying to compile libidn with mingw/msys under windows and I get an error right at the start of making: C:/msys/bin/sh.exe ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT getopt.lo -MD -MP -MF .deps/getopt.Tpo -c -o getopt.lo getopt.c gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT getopt.lo -MD -MP -MF .deps/getopt.Tpo -c getopt.c -DDLL_EXPORT -DPIC -o .libs/getopt.o In file included from getopt.h:38, from getopt.c:27: ./unistd.h:23:13: stdout: No such