3.4 installation problems: libc is somewhere unusual

[prj at po dot cwru dot edu (Paul Jarc)]

My glibc installation is not in the usual place.  This means I have to
pull a few tricks to build gcc, but the tricks that worked for gcc up
to 3.3.1 (tweaking C_INCLUDE_PATH and LIBRARY_PATH, and adding the
appropriate -Wl,--dynamic-linker and -Wl,-R arguments to
STAGE1_CFLAGS, BOOT_CFLAGS, and LDFLAGS) don't work for 3.4-20030910.

The first new change I had to make was to edit gcc/Makefile.in to
tweak the NATIVE_SYSTEM_HEADER_DIR definition.  Easy enough.

Now I'm running into another problem.  libf2c configuration fails:
checking for stdio.h... no
configure: error: Can't find stdio.h.
You must have a usable C system for the target already installed, at least
including headers and, preferably, the library, before you can configure
the G77 runtime system.  If necessary, install gcc now with `LANGUAGES=c',
then the target library, then build with `LANGUAGES=f77'.
make[1]: *** [configure-target-libf2c] Error 1
make[1]: Leaving directory `/fs/data/mount/home/prj/src/spf/gcc-3.4-20030910-build'
make: *** [bootstrap-lean] Error 2

In fact, the tricks I've been using are indeed sufficient to let
the configure test find stdio.h.  The test only thinks it fails
because some warnings are produced, specifically:
gcc: --dynamic-linker: linker input file unused because linking not done
gcc: /package/misc/spf/gcc-3.4-20030910/spf/glibc/lib/ld-linux.so.2: linker input file unused because linking not done
gcc: -R: linker input file unused because linking not done
gcc: /package/misc/spf/gcc-3.4-20030910/spf/glibc/lib: linker input file unused because linking not done

This is a result of my adding -Wl,--dynamic-linker and -Wl,-R
arguments to all of STAGE1_CFLAGS, BOOT_CFLAGS, and LDFLAGS.  This is
rather heavy-handed, but I haven't found any other way that works, at
least for < 3.4.  So:
- Is there a less pervasive set of variables I could set, that would
  not be used for tests such as this one, but would be used for
  absolutely all linking commands, where I can put my -Wl arguments?
  Ideally, I'd like to set the same variable regardless of the gcc
  version, but I can set different variables depending on the version
  if necessary.
- Otherwise, could this test be more permissive about warnings?  The
  exit status in this case is 0; is that not sufficient to indicate
  success?


paul