Hi Jim,
the problem lies in the command
-$(INSTALL_PROGRAM) xgcc$(exeext)
$(DESTDIR)$(bindir)/$(GCC_INSTALL_NAME)$(exeext)
which on my machine evaluates to
/afs/rzg/@sys/bin/install -c xgcc /afs/mpa/data/martin/ugcc/bin/gcc
Apparently this special version of "install" in my path creates a subdirectory
whenever the name of the executable and the last part of the install path
(in this case "xgcc" and "gcc") are not identical.
I have verified that other versions of "install" don't behave that way.
Is this a bug in my local version of "install", or could it be interpreted as
acceptable behaviour?
Unfortunately I have no way of finding out more about the local "install",
as it doesn't accept the --help flag:
/scratch/ogcc/gcc>/afs/rzg/@sys/bin/install --help
Bad switch --help
/scratch/ogcc/gcc>/afs/rzg/@sys/bin/install -h
Bad switch -h
Cheers,
Martin