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 testsuite/36443] [4.3/4.4 Regression]: HOSTCC doesn't work with installed gcc



------- Comment #36 from rob1weld at aol dot com  2009-01-27 21:12 -------
(In reply to comment #33)
*** Bug 38820 has been marked as a duplicate of this bug. ***
(In reply to comment #34)
> If I have an old gcc 4.4 installed on my machine, will setting
> GCC_EXEC_PREFIX use the old installed gcc 4.4 for "make check"?


That was my concern and here is proof:

# gcc/xgcc -v
Using built-in specs.
Target: i386-redhat-linux
Configured with: ../gcc_trunk/configure
--enable-languages=c,c++,fortran,java,objc,obj-c++ --enable-shared
--disable-static --enable-decimal-float --with-long-double-128 --enable-nls
--with-included-gettext --disable-gather-detailed-mem-stats --with-stabs
--enable-debug --enable-symvers --enable-version-specific-runtime-libs
--without-system-zlib --enable-gtk-cairo --enable-gconf-peer --enable-xmlj
--enable-gtk-peer --enable-plugin --enable-tool-wrappers
--enable-portable-native-sync --enable-hash-synchronization
--enable-interpreter --enable-local-sockets --enable-gjdoc
--enable-java-awt=gtk,xlib,x --enable-gc-debug --enable-libgcj-debug
--enable-objc-gc --disable-concept-checks --enable-libstdcxx-debug
--disable-stage1-checking --enable-checking=release --with-tune=k8
--with-cpu=k8 --with-arch=k8 --enable-__cxa_atexit
--disable-libunwind-exceptions --disable-dssi --enable-libgcj-multifile
--build=i386-redhat-linux --prefix=/mnt/drive2/gcc_test --with-cloog=/usr/local
Thread model: posix
gcc version 4.4.0 20090126 (experimental) [trunk revision 143680] (GCC) 


Here is a small portion of the build output:

make[4]: Leaving directory `/mnt/drive2/gcc_build/i386-redhat-linux/libgcc'
# Early copyback; see "all" above for the rationale.  The
# early copy is necessary so that the gcc -B options find
# the right startup files when linking shared libgcc.
/bin/sh ../../../gcc_trunk/libgcc/../mkinstalldirs ../.././gcc
parts="crtbegin.o crtbeginS.o crtbeginT.o crtend.o crtendS.o crtprec32.o
crtprec64.o crtprec80.o crtfastmath.o";                                       
\
        for file in $parts; do                                  \
          rm -f ../.././gcc/$file;              \
          /usr/bin/install -c -m 644 $file ../.././gcc/;        \
        done
# @multilib_flags@ is still needed because this may use
# /mnt/drive2/gcc_build/./gcc/xgcc -B/mnt/drive2/gcc_build/./gcc/
-B/mnt/drive2/gcc_test/i386-redhat-linux/bin/
-B/mnt/drive2/gcc_test/i386-redhat-linux/lib/ -isystem
/mnt/drive2/gcc_test/i386-redhat-linux/include -isystem
/mnt/drive2/gcc_test/i386-redhat-linux/sys-include and -O2  -g -O2 -DIN_GCC  
-W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual
-Wold-style-definition  -isystem ./include  -fPIC -g -DHAVE_GTHR_DEFAULT
-DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  directly.
# @multilib_dir@ is not really necessary, but sometimes it has
# more uses than just a directory name.
/bin/sh ../../../gcc_trunk/libgcc/../mkinstalldirs .


Notice this:
parts="crtbegin.o crtbeginS.o crtbeginT.o crtend.o crtendS.o crtprec32.o
crtprec64.o crtprec80.o crtfastmath.o";        


# locate crtbegin.o | grep usr
/usr/lib/gcc/i386-redhat-linux/4.3.2/crtbegin.o

# locate crtprec80.o | grep usr
/usr/lib/gcc/i386-redhat-linux/4.3.2/crtprec80.o

# locate crtfastmath.o | grep usr
/usr/lib/gcc/i386-redhat-linux/4.3.2/crtfastmath.o


Lets us use newly compiled crt* files instead of the wrong ones.

The priority here is "NORMAL", someone bump it to MAJOR for us.

Rob


-- 


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


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