Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3FEBB20E.78216370@dessent.net> Date: Thu, 25 Dec 2003 19:59:10 -0800 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: Cygwin mailing list CC: anjali1@umbc.edu Subject: Re: Problem using export command References: <3696.68.55.203.3.1072381783.squirrel@webmail.umbc.edu> <3FEB4237.BA1E9533@dessent.net> <4107.68.55.203.3.1072399290.squirrel@webmail.umbc.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.linuxsv3.net X-AntiAbuse: Original Domain - cygwin.com X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - dessent.net X-IsSubscribed: yes Anjali Bharat Shah wrote: > > Hi Brian, Please keep replies to the list and not to me directly. > 1)Your CLASSPATH contains a directory with a space in it, probably > > \Program Files. You'll need to quote it so that the shell sees it all > > as one word. > Can you please show how to use quotes for such directories? as in where to > place the quotes? Also does the export command have to be outside the script > at the prompt or does it work from inside the script as well? export CLASSPATH="$CLASSPATH:$CP:$REI_HOME/classes:." The export will set the variable in the environment of that script and any processes launched from it. It cannot change the value of variables in the environment above it. To get around this you typically use the 'source' command which runs a script in the context of the current shell rather than spawning a subshell. > > 2) Also, I don't think LD_LIBRARY_PATH has any effect under Cygwin. > > There's no such feature. > > Can you please suggest the equivalent variable same? Under Windows, the system searches the PATH for shared libraries (.DLLs). I think it also searches the directory of the executable first, and then tries the PATH. (It might be the other way around, I don't know.) Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/