Showing posts with label env. Show all posts
Showing posts with label env. Show all posts

Tuesday, November 30, 2010

configure & make node.js under Cygwin

Just one oddity with building node.js on cygwin (it was fine Ubuntu) and that is that I could not get ./configure to complete until it occurred to me to run
unset PYTHONHOME
unset PYTHONPATH
After that the
./configure
make
make install
ran without a hitch and node/js behaving much as it does on linux. 

The python module path issue was not becuase cygwin was using my Windows values: a simple bash check with
echo $PYTHONPATH
echo $PYTHONHOME
cleared that up.
The symptom could be seem by just running a verbose python REPL at thecommand prompt
python -v
and noting the "site" package error.  Yet loading sys and doing
print sys.path
showed no obvious problem.  I have seen this gift once when a linux version upgrade required a python version upgrade.  I checked in the registery under LOCAL_MACHINE | SOFTWARE but the three values there for python25, python26 and python31 look fine (although the latter appears truncated ...)

I tried various export statements and looked for a doubtful resource rc file or other config in /etc but the answer (porbably obvious enough) eludes me.

When set and export to reasonable values and to no value fail and there is nothing else odd reported by env then unset to the rescue.

Now back to looking at axiom and sproutcore as server-side JavaScript options.

Monday, August 30, 2010

ObjectIcon 2.4 and Cygwin make

ObjectIcon 2.4 is available at code.google.com/p/objecticon

This is the Icon language of the late Ralph Griswold and others as extended by Robert Parlett with class-based objects and Unicode.

If you are a Windows user with Cygwin as your gcc build environment, you will have to recall how to apply env var changes to the current shell: ObjectIcon comes with a handy paths.sh file which will only be of use if run as
.  ./paths.sh
where the initial dot ensures that a script not using exit will have its variables export into the scope of the current shell in which it will run.  Just running the script will not set the var's for ObjectIcon to use.

This way you are able to pick up the ObjectIcon env vars such as OIHOME without adding them into a bash rc file or the like.

On my system that paths.sh file is
# Object Icon path settings

export OIHOME="/cygdrive/i/objecticon-2.4"
export OIBIN="$OIHOME/bin"
export OILIB="$OIHOME/lib"
export OIPATH="$OILIB/main:$OILIB/gui:$OILIB/xml:$OILIB/parser:$OILIB/ipl"
export OIINCL="$OILIB/incl"
PATH="$PATH:$OIBIN"
LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$OILIB/native"
export TRACE OIMAXLEVEL