Thanks Dave, that did the trick. At first I just modified the Makefile
and reran the make and got the same error so I went back and did a
runConfigure again, ran the make and everything built OK.
There was another problem though with the install. When it tried to
create the 'lib' directory for the install, the path it was using had a
double slash at the beginning and mkdir failed with a "network path not
found" type of error. I've backtracked through as many of the makefiles
as I can and can't find how 'DESTDIR' in the line
$(MKINSTALLDIRS) $(DESTDIR)/$(libdir)
gets set.
On the chance that rebuilding the makefiles with runConfigure might be
part of the problem I went back, wiped everything, patched the
(...)/Util makefile, and rebuilt the libraries from scratch with just
"make". That went OK, but then when I did a "make install" I got the
problem. Transcript below. And again, thanks much for all the help.
<much build output snipped>
make[1]: Leaving directory
`/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c/src/xalanc'
[EMAIL PROTECTED]
/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c
$ make install
make -C src/xalanc install
make[1]: Entering directory
`/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c/src/xalanc'
Preparing the directory structure for a build ...
mkdir -p ../../obj
mkdir -p ../../lib
mkdir -p ../../bin
make -C Utils prepare
make[2]: Entering directory
`/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c/src/xalanc/
Utils
'
mkdir -p ../../../nls
mkdir -p ../../../nls/include
make[2]: Leaving directory
`/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c/src/xalanc/
Utils'
make -C Utils locale
make[2]: Entering directory
`/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c/src/xalanc/
Utils
'
make[2]: Nothing to be done for `locale'.
make[2]: Leaving directory
`/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c/src/xalanc/
Utils'
make -C Utils install
make[2]: Entering directory
`/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c/src/xalanc/
Utils
'
/usr/bin/install -c -m 644 ../../../nls/include/LocalMsgIndex.hpp
/cygdrive/c/proj/3rdParty/libs/xalan-c_
1_10_0-C/xml-xalan/c//src/xalanc/PlatformSupport
make -C XalanMsgLib install
make[3]: Entering directory
`/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c/src/xalanc/
Utils
/XalanMsgLib'
mkdir -p //cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/package/lib
mkdir: cannot create directory `//cygdrive': No such host or network
path
make[3]: *** [install] Error 1
make[3]: Leaving directory
`/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c/src/xalanc/
Utils/
XalanMsgLib'
make[2]: *** [install] Error 2
make[2]: Leaving directory
`/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c/src/xalanc/
Utils'
make[1]: *** [install] Error 2
make[1]: Leaving directory
`/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c/src/xalanc'
make: *** [install] Error 2
[EMAIL PROTECTED]
/cygdrive/c/proj/3rdParty/libs/xalan-c_1_10_0-C/xml-xalan/c
$
-----Original Message-----
From: David Bertoni [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 3:22 AM
To: xalan-c-users@xml.apache.org
Subject: Re: building xalan on cygwin
Will Sappington wrote:
> While STFLA for a problem I'm having building with Cygwin I came
across a somewhat lengthy thread between Dave and Thomas Porschberg
regarding exactly the problem I'm having. Was this problem ever
resolved? The last post ended with Thomas having modified a makefile to
contain a hard-coded windows form of a path and removing something
involving XLIFF_FILE_NAME. I'm not going to get into all that, there
has to be a more general solution. BTW, I would have replied to the
thread on the archive list (if you can do that) but a banner at the top
of the page said the site was read-only while some problems were being
resolved.
>
>
>
> As to the problem, it is the same as Thomas', "multiple targets"
message when make runs. I recognize that message as having something to
do with EOL issues. At first I thought the problem might be that I
untarred the file from a DOS window and CR's were added courtesy of MS.
So I deleted everything except the tarball, opened a Cygwin shell,
untarred again, set everything again, and got the same error again. I'm
pretty sure I'm following everything to the letter, but I've captured
the screen text of my session which I'll paste in below. I can say that
I also know first hand about the bash problems in recent Cygwin updates,
they screwed me up royally for a few days. The gist of it is they
changed something about how bash handles CR/LF sequences in scripts and
after a certain version, any script with CR/LFs in it would fail unless
you put "shopt -s igncr;#" at the top. About a month and a half ago,
maybe 2, I went to download a new package and my whole installation got
updated. I didn't realize they'd be so kind. And that's when
everything started breaking. So like Dave's when he was involved in
this issue, my installation is pretty new too. Here's the transcript of
my session, starting with a new shell and a freshly unzipped tarball.
Any ideas?
Strangely enough, I just tried the build, and now I have the same
problem,
even though I was unable to reproduce it before.
It turns out the new version of gnumake doesn't like mixed cygwin paths.
Here's a patch you can apply:
Index: src/xalanc/Utils/Makefile.in
===================================================================
--- src/xalanc/Utils/Makefile.in (revision 505617)
+++ src/xalanc/Utils/Makefile.in (working copy)
@@ -35,7 +35,7 @@
CATALOG_NAME=$(MSGFILENAME)$(LOCALE)
ifeq ($(PLATFORM), CYGWIN)
-XLIFF_FILE_NAME=$(shell cygpath -m
$(XSL_NLS_SRC_DIR)/$(LOCALE)/$(MSGFILENAME)$(LOCALE).xlf)
+XLIFF_FILE_NAME=$(shell cygpath -u
$(XSL_NLS_SRC_DIR)/$(LOCALE)/$(MSGFILENAME)$(LOCALE).xlf)
else
XLIFF_FILE_NAME=$(XSL_NLS_SRC_DIR)/$(LOCALE)/$(MSGFILENAME)$(LOCALE).xlf
endif
(basically, change the -m option for shell cygpath to -u)
Dave
