[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnu-arch-users] Solution to running configure on SFU (was: Problems ins
From: |
Parker, Ron |
Subject: |
[Gnu-arch-users] Solution to running configure on SFU (was: Problems installing t la on FreeBSD) |
Date: |
Thu, 1 Apr 2004 13:45:43 -0600 |
> From: Tom Lord [mailto:address@hidden
> Can you double check whether the version of patch
> you are trying to configure with does or does not
> support that option?
Turns out that patch was not the actual problem in this case. Microsoft
ships a very strange which(1) with SFU. It puts out Windows-style paths,
while most of the rest of SFU uses Unix-style paths and there is some
end-of-line weirdness going on as well.
The following patch to package-framework gets past this issue. I am still
looking at post-config build issues.
--- tla-1.2.orig/src/build-tools/auto-conf-lib/gnu-patch-test Mon Feb 9
12:08:25 2004
+++ tla-1.2/src/build-tools/auto-conf-lib/gnu-patch-test Thu Apr 1
12:41:15 2004
@@ -116,7 +116,12 @@
FAIL=""
-if [ -x "`which "$PATCHPROG" 2>/dev/null`" ] ; then
+if [ "`uname`" = Interix ] ; then
+ PATCHPATH=`winpath2unix "\`which \"$PATCHPROG\" 2>/dev/null\`"|tr -d
'\\r'`
+else
+ PATCHPATH="`which "$PATCHPROG" 2>/dev/null`"
+fi
+if [ -x "$PATCHPATH" ] ; then
testresults "$ORIG_A" "$PATCHED_A" "$EXPECTED_A" "$ORIG_PRISTINE_A"
"$PATCH_A"
testresults "$ORIG_B" "$PATCHED_B" "$EXPECTED_B" "$ORIG_PRISTINE_B"
"$PATCH_B"
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gnu-arch-users] Solution to running configure on SFU (was: Problems installing t la on FreeBSD),
Parker, Ron <=