[Bug testsuite/38526] WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator
--- Comment #7 from iains at gcc dot gnu dot org 2010-07-24 07:46 --- fixed -- iains at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38526
[Bug testsuite/38526] WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator
--- Comment #6 from janis at gcc dot gnu dot org 2009-03-17 17:36 --- Subject: Bug 38526 Author: janis Date: Tue Mar 17 17:35:55 2009 New Revision: 144908 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=144908 Log: gcc/ PR testsuite/38526 * Makefile.in (site.exp): Rename TEST_GCC_EXEC_PREFIX and comment its use. (check-%): Don't set GCC_EXEC_PREFIX when invoking runtest. (check-parallel-%): Ditto. (check-consistency): Ditto. testsuite/ PR testsuite/38526 * lib/target-libpath.exp (set_ld_library_path_env_vars): Save existing GCC_EXEC_PREFIX, set to TEST_GCC_EXEC_PREFIX if that is defined. (restore_ld_library_path_env_vars): Restore GCC_EXEC_PREFIX to its original value, or unset if it was not defined. * gcc.dg/compat/struct-layout-1.exp: Use set/restore library path procs around use of HOSTCC. * g++.dg/compat/struct-layout-1.exp: Ditto. * objc.dg/gnu-encoding/gnu-encoding.exp: Ditto. Modified: trunk/gcc/ChangeLog trunk/gcc/Makefile.in trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/g++.dg/compat/struct-layout-1.exp trunk/gcc/testsuite/gcc.dg/compat/struct-layout-1.exp trunk/gcc/testsuite/lib/target-libpath.exp trunk/gcc/testsuite/objc.dg/gnu-encoding/gnu-encoding.exp -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38526
[Bug testsuite/38526] WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator
--- Comment #4 from janis at gcc dot gnu dot org 2009-02-27 23:40 --- If this is still a problem, please try the patch at http://gcc.gnu.org/ml/gcc-patches/2009-01/msg01496.html I'd rather not make changes like that so late in the release cycle but I'll do it if it's needed and not just cosmetic. -- janis at gcc dot gnu dot org changed: What|Removed |Added CC||janis at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38526
[Bug testsuite/38526] WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator
--- Comment #5 from dave at hiauly1 dot hia dot nrc dot ca 2009-02-28 03:12 --- Subject: Re: WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator If this is still a problem, please try the patch at http://gcc.gnu.org/ml/gcc-patches/2009-01/msg01496.html Yes, this is still a problem on darwin. The patch fixes the PR. I'd rather not make changes like that so late in the release cycle but I'll do it if it's needed and not just cosmetic. I would say the issue is more than cosmetic, but testsuite issues aren't crucial unless the test results are misleading. Dave -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38526
[Bug testsuite/38526] WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator
--- Comment #3 from hjl dot tools at gmail dot com 2008-12-15 15:51 --- (In reply to comment #2) Subject: Re: WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator This is really PR 36443. Aside from darwin specific issues with the environment, the problem looks the same. Did anybody try Mark's suggestion (i.e., setting HOSTCC to unset GCC_EXEC_PREFIX gcc)? Other C cpmpilers may be used for bootstrap. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38526
[Bug testsuite/38526] WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator
--- Comment #1 from hjl dot tools at gmail dot com 2008-12-14 20:07 --- This is really PR 36443. -- hjl dot tools at gmail dot com changed: What|Removed |Added BugsThisDependsOn||36443 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38526
[Bug testsuite/38526] WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator
--- Comment #2 from dave at hiauly1 dot hia dot nrc dot ca 2008-12-14 22:25 --- Subject: Re: WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator This is really PR 36443. Aside from darwin specific issues with the environment, the problem looks the same. Did anybody try Mark's suggestion (i.e., setting HOSTCC to unset GCC_EXEC_PREFIX gcc)? Dave -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38526
