This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Top-level Makefile
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 30 Nov 2001 18:16:50 -0800
- Subject: Re: Top-level Makefile
- References: <10111301059.AA25731@vlsi1.ultra.nyu.edu>
On Fri, Nov 30, 2001 at 05:59:39AM -0500, Richard Kenner wrote:
> - Put "set -x" at the top of the configure script, then post the last
> thirty or so lines of the output once it gets stuck.
>
> + echo nan.h
> ac_safe=nan_h
> + echo checking for nan.h... \c
> checking for nan.h... + echo configure:5085: checking for nan.h
> + echo ${ac_cv_header_nan_h+set}
> + eval test "${ac_cv_header_nan_h+set}" = set
> + test = set
> + cat
> ac_try=$CPP $CPPFLAGS conftest.c >/dev/null 2>conftest.out
> + eval echo configure:5095: "$CPP $CPPFLAGS conftest.c >/dev/null 2>conftest.out
> "
...
>
> So it's not doing a whole lot, but doing it slowly: there are delays of
> perhaps 5-10 seconds between a number of those lines.
It would be useful to know which. The cat commands are most likely,
but something else might be going on.
> - Look in all the tmp directories your system has (/tmp, /usr/tmp,
> /var/tmp, etc) and see if there's a large number of scratch files
> created by the configure script.
>
> Yes, 605 of them.
Okay, so that's a strong case for being the same problem rth and I
were looking at last May. I'll send you a hack to try sometime
tomorrow.
zw