This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c/37995] using <stdio.h> fails if gcc invoked in a directory which has a subdirectory called "gcc"



------- Comment #4 from brian at dessent dot net  2008-11-03 23:23 -------
Subject: Re:  using <stdio.h> fails if gcc invoked in a directory 
 which has a subdirectory called "gcc"


>  /usr/lib/gcc/i686-pc-linux-gnu/4.3.2/cc1 -E -quiet -v -iprefix
> /home/mvanier/tmp/../lib/gcc/i686-pc-linux-gnu/4.3.2/ hello.c -mtune=generic
> -fpch-preprocess -o hello.i

That -iprefix is the problem.  It should not be there.  Do you have
GCC_EXEC_PREFIX set in your environment or something?  You should not
need this set in normal use of the compiler; try with a clean env.

Also, you are not building a stock gcc because there are these patches
added by your build script:

>   if [ "${CARCH}" = "x86_64" ]; then
>     patch -Np1 -i ../gcc_pure64.patch || return 1
>   fi
>   patch -Np0 -i ${srcdir}/gcc-hash-style-both.patch || return 1
>   patch -Np0 -i ${srcdir}/gcc-java-driver.patch || return 1

It makes it really hard to triage bugs when you report problems against
software build with random unmentioned outside changes.  Please try a
vanilla build.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37995


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]