gcc configure --with-headers broken?

[Matt Taggart]

Hi,

I'm working on the hppa-linux port and routinely build gcc on i386-linux to 
cross compile for hppa-linux. On Monday(Aug 21) I was able to build this cross 
compiler with no problems using the source in our CVS(puffin.external.hp.com) 
that was a snapshot of upstream from 20000707. On Tuesday we merged our CVS to 
a new upstream snapshot from 20000822. Now it appears that the --with-headers 
configure option no longer works. The configure line I used in both cases is,

configure --target=hppa-linux --host=i386-linux \
    --prefix=/home/al-76/puffin/xc --disable-shared --disable-nls \
    --with-headers=/home/al-76/puffin/palinux/include --without-libc \
    --enable-languages=c

Attached is script of the failures from the second build. All of the headers 
it can't find are present in the --with-headers directory.

It looks like "-nostdinc" is added to the compile line but then the right 
include directory is not specified. I can confirm that the contents of the 
directory specified with --with-headers are copied to 
$PREFIX/hppa-linux/sys-include/ but the build doesn't find them(is this where 
it should be looking?).

A few people have suggested work-arounds including copying the headers in by 
hand and using "make LIBGCC2_INCLUDES=-I/your/include/files". However, the 
--with-headers way seems like the proper method.

If something changed between 20000707 and 20000822 to break this I suspect 
most people wouldn't have noticed since either they don't use --with-headers 
or they are building on top of a previous build.

I suspect that a Makefile change caused this. So, I used the (very nice) 
cvsweb to do diffs of Makefile.in and gcc/Makefile.in for the dates in 
question. As the Makefiles are pretty complicated I gave up for now.

Am I correct in assuming that --with-headers should work?
Is anyone else seeing this problem?
Does someone who knows this magic know whats going on?

I am not subscribed to the list so I would appreciate a cc on any responses.

Thanks,

-- 
Matt Taggart
taggart@fc.hp.com