Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | environment parsing foo | ||
---|---|---|---|
Product: | Build Tools | Reporter: | mmeeks <mmeeks> |
Component: | dmake | Assignee: | hjs <hans-joachim.lankenau> |
Status: | CLOSED FIXED | QA Contact: | issues@tools <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, quetschke |
Version: | OOo 1.1.1RC | ||
Target Milestone: | OOo 2.0 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
mmeeks
2004-04-01 16:21:40 UTC
committed to cws_src680_ooo20040329 apparently that cws is shut; hmm. Hi Michael! Please try this workaround and report back. Enter in Start->Run: C:\cygwin\bin\rxvt.exe -sl 1000 -e /usr/bin/bash --login -i This should do. (The -sl 1000 gives you a thousand lines scrollbuffer, it's not needed, but convenient.) Another solution is installing sshd and logging into your Windows machine and working in a ssh shell. (This is what I always do, therefore I didn't get the problem.) The actual problem comes from cygwin being a bit to clever, in its source code, file environ.cc it says: /* Current directory information is recorded as variables of the form "=X:=X:\foo\bar; these must be changed into something legal (we could just ignore them but maybe an application will eventually want to use them). */ Unfortunately !SOMETHING is also not legal :-( I deduct from this and the existence of !EXITCODE that Windows sometimes has a variable named =EXITCODE. When using one of the two methods mentioned above to start bash/tcsh there should be no !X:=X:\foo\bar set. I have another one: Start your tcsh in your cygwin shell with: $ env `set | sed -ne '/\!/{s/=.*$//; s/^/-u / p}'` tcsh Sorry, couldn't resist ;-) Ahh, well I forgot, patch approved! closing . |