diff --git a/libf2c/Makefile.in b/libf2c/Makefile.in
index 92d4a33fb84..d8f6962dcb1 100644
--- a/libf2c/Makefile.in
+++ b/libf2c/Makefile.in
@@ -101,7 +101,7 @@ f77:
 u77:
 	cd libU77; $(MAKE) $(FLAGS_TO_PASS) all
 
-s-libe77: $(srcdir)/f2cext.c
+s-libe77: f2cext.c
 	if [ -d libE77 ]; then rm -f libE77/*.o; else mkdir libE77; fi
 	for name in $(F2CEXT); \
 	do \
@@ -113,12 +113,12 @@ s-libe77: $(srcdir)/f2cext.c
 	done
 	echo timestamp >s-libe77
 
-${srcdir}/configure: ${srcdir}/configure.in
+${srcdir}/configure: configure.in
 	rm -f config.cache
 	cd $(srcdir) && autoconf
 
 # Dependence on Makefile serializes for parallel make.
-g2c.h: $(srcdir)/g2c.hin config.status Makefile
+g2c.h: g2c.hin config.status Makefile
 # Might try to avoid rebuilding everything if Makefile or configure
 # changes and g2c.h doesn't; see also the Makefile rule.  Should
 # depend on another stamp file rather than using the commented-out
@@ -127,11 +127,11 @@ g2c.h: $(srcdir)/g2c.hin config.status Makefile
 	$(SHELL) config.status
 #	$(srcdir)/../move-if-change g2c.h g2c.x && mv g2c.x g2c.h
 
-Makefile: $(srcdir)/Makefile.in config.status
+Makefile: Makefile.in config.status
 # Autoconf doc uses `./config.status'.  Is there a good reason to use 
 	  $(SHELL) config.status
 
-config.status: $(srcdir)/configure $(gcc_version_trigger)
+config.status: configure $(gcc_version_trigger)
 # Make sure we don't pick up a site config file and that configure
 # gets run with correct values of variables such as CC.
 	CONFIG_SITE=no-such-file $(FLAGS_TO_PASS) \
@@ -178,7 +178,7 @@ distclean: clean
 
 maintainer-clean:
 
-rebuilt: ${srcdir}/configure
+rebuilt: configure
 
 .PHONY: rebuilt mostlyclean clean distclean maintainer-clean all \
         i77 f77 u77 check uninstall install-strip dist \