summaryrefslogtreecommitdiff
path: root/bindisttest
diff options
context:
space:
mode:
authorIan Lynagh <igloo@earth.li>2009-02-10 21:52:15 +0000
committerIan Lynagh <igloo@earth.li>2009-02-10 21:52:15 +0000
commitf75d258c4e74aa91dd5c64e47e9d96889870743a (patch)
treea49ecd808e41e84b2bc2dee7c6fa98654379eb9f /bindisttest
parentef378f7cd93227321ce127f542865f1d799e0ccb (diff)
downloadhaskell-f75d258c4e74aa91dd5c64e47e9d96889870743a.tar.gz
Don't use the absolute path to the bindist tarball
On Windows, we end up doing something like rsync c:/build/ghc-6.10.1-unknown-mingw32.tar.bz2 haskell.org:dist and it thinks that it is meant to get the file from the host called "c". Now we just do rsync ghc-6.10.1-unknown-mingw32.tar.bz2 haskell.org:dist so rsync understand what we mean.
Diffstat (limited to 'bindisttest')
-rw-r--r--bindisttest/Makefile2
1 files changed, 1 insertions, 1 deletions
diff --git a/bindisttest/Makefile b/bindisttest/Makefile
index e6e2ed7292..c14a08577b 100644
--- a/bindisttest/Makefile
+++ b/bindisttest/Makefile
@@ -13,7 +13,7 @@ all:
$(RM) -rf ghc*
$(RM) HelloWorld HelloWorld.o HelloWorld.hi output
# --force-local makes tar not think that c:/foo refers to a remote file
- $(TAR) --force-local -jxf $(BIN_DIST_TAR_BZ2)
+ $(TAR) --force-local -jxf $(FPTOOLS_TOP_ABS)/$(BIN_DIST_TAR_BZ2)
ifeq "$(Windows)" "YES"
mv $(BIN_DIST_NAME) $(BIN_DIST_INST_DIR)
else