On Tue, 27 Jul 2004 13:18:23 -0400, Schofield, Bryan (GE Transportation) bryan.schofield@trans.ge.com wrote:
I had that problem at as well. I didn't care to make xowish or xotclsh, I ended up commenting portions of the make file out to get it to work. Specifically, I commented out "binaries", "install", and part of "libraries" target.
after staring it at it with several people it looks like the problem is a bash parsing one for this piece of code:
dir in $(subdirs) ; do \
the problem is that if $(subdirs) is "" then bash will try to parse "dir in; do " , which is of course wrong. the if statement doens't actually protect you from this (it's a parsing problem, not an execution time one)
so i just changed $(subdirs) to ". $(subdir)" and that seems to make bash happy-- it's not going to run it anyway.
I don't mean to speak for Gustaf, but maybe give this version a try: http://media.wu-wien.ac.at/download/xotcl-1.2.1.tar.gz
I don't think it's quite ready for primetime, since Gustaf & Co. are adding a few enhancements. But I think all that remains is documentation. I've been using it & testing out the new features for a about 2 months and consider it stable. That version also has a better build & configuration system and compiles with out complaint fine for me (which is the only reason I'm mentioning it, it was a painful to get the last publicly released version to compile on Solaris). I'm sure the XOTcl guys will correct me if I'm wrong.
I noticed you posted a question on the IncrTcl mailing list earlier today about "unknown" handlers. I think you'll find that XOTcl's unknown handler is fantastic. I've used IncrTcl extensively, but over the last 6 months or so I've began using XOTcl instead. I now prefer XOTcl greatly to IncrTcl. After using it, I feel so constrained with IncrTcl by having to fully define my classes, and thus my object behavior, a head of time. The flexibility of XOTcl is phenomenal.
I agree. I went thru the manual last night, and was quite impressed with options and features avaliable. It really is a shame that xotcl isn't more widely distributed. One thing that popped into my mind was how to do private variables and methods (i think this can be done via the filters, but i haven't exactly figured them out yet)
Thank-you to the developers for maintianing xotcl.
-- bryan
-----Original Message----- From: xotcl-admin@alice.wu-wien.ac.at [mailto:xotcl-admin@alice.wu-wien.ac.at]On Behalf Of Aamer Akhter Sent: Tuesday, July 27, 2004 12:42 PM To: xotcl@alice.wu-wien.ac.at Subject: [Xotcl] build problem on solaris
Folks,
I'm having a a makefile problem on solaris (the linux build went fine)
gcc -pipe -shared -o libxotcl1.2.so so/xotcl.o so/xotclError.o so/xotclMetaData.o so/xotclObjectData.o so/xotclProfile.o so/xotclTrace.o so/xotclUtil.o so/xotclShadow.o so/xotclCompile.o so/aolstub.o so/xotclStubInit.o -L/auto/nsite-mmpls/users/aakhter/ats4.0/lib -ltclstub8.4 : libxotcl1.2.so /bin/bash: -c: line 1: syntax error near unexpected token `;' /bin/bash: -c: line 1: `if test ! "x" = "x" ; then for dir in ; do if (cd $dir; make binaries) ; then true ; else exit 1 ; fi ; done; fi;'
which is (with make -d):
Finished prerequisites of target file `binaries'. Must remake target `binaries'. Putting child 0x00068080 (binaries) PID 17840 on the chain. Live child 0x00068080 (binaries) PID 17840 /bin/bash: -c: line 1: syntax error near unexpected token `;' /bin/bash: -c: line 1: `if test ! "x" = "x" ; then for dir in ; do if (cd $dir; make binaries) ; then true ; else exit 1 ; fi ; done; fi;'
makefile:
binaries: $(BINARIES) $(XOTCLSH) $(XOWISH) pkgIndex.tcl @if test ! "x$(subdirs)" = "x" ; then \ for dir in $(subdirs) ; do \ if (cd $$dir; $(MAKE) $@) ; then true ; else exit 1 ; fi ; \ done; fi;
has anybody run into this problem already?
-- Aamer Akhter / aakhter@gmail.com _______________________________________________ Xotcl mailing list - Xotcl@alice.wu-wien.ac.at http://alice.wu-wien.ac.at/mailman/listinfo/xotcl