OK, I'm looking into this. Over the weekend I installed cygwin on my
wife's home machine to be sure that there's no hidden stuff from my
environment that comes into play, downloaded OpenDX from CVS and am
building it. I've already run into one small problem - local.mk.in in
dxmods doesn't let you build in an object tree, and I'll fix that. I also
ran into the problem compiling the big generated file zclipQ.c (at least I
think it was that; I'm in the office now and can't look) - it took forever
(though did in fact complete over night). By editting the object-tree
libdx Makefile and removing -O2 from the CFLAGS line and then making it
it'll compile a lot faster.
Tonight I'll restart the build and see whats what. It got well into the UI
build before my wife needed her computer back.
I believe the MacroDefinition.C:631 problem is related to the use of
backslashes in pathnames. I'll figure it out and get back to y'all.
Greg
"Macdonald, Luke H"
<[EMAIL PROTECTED]> To:
"'[email protected]'"
Sent by:
<[email protected]>
[EMAIL PROTECTED] cc:
son.ibm.com Subject:
[opendx-users] opendx on cygwin: "Unable to connect to
dxexec" and
"Macrodefinit ion.C" errors
07/09/03 11:42 AM
Please respond to
opendx-users
Hi,
I've compiled opendx-4.1.1-cygwin-1.1.2.tar.gz on my W2K box at work which
runs
cygwin version 1.3.22-1, but dx does not have functionality. All XFree86
packages available from the cygwin website are installed on my machine, and
so
is tcsh and openGL. I'd like to take Gregory D Abram up on his offer to
help
Cygwin/OpenDX users which he posted on Tue, July 1 of this year (Re:
[opendx-users] cygwin binaries).
Initially, there were some problems with read permissions of the libraries,
and
showing dx where the libraries were, but all of that now works fine.
Cygwin/OpenDX users have documented the problem I now encounter dozens of
times
over the past three years, but there is no answer on any of the mailing
lists.
A few of these mailing list postings are referenced at the bottom of this
message. The problem is as follows:
-I enter "dx" at prompt in an Xterm. The data explorerer starts.
-If I try to open a *.net file using the samples button, two dialogue boxes
open
which say "starting data explorer" and "Error: Unable to Connect to
dxexec".
-at the prompt this appears:
_dxl_ReadPortNumber: Bad file descriptor
timeout waiting for response from DX
Internal error deteted at "MacroDefinition.C":631.
Another problem, which seems to be the same issue, is if I enter "dx -edit"
or
"dx -uionly &" at prompt. This appears:
Starting DX user interface
Internal error detected at "MacroDefinition.C":631.
No files needed to be saved.
Aborted (core dumped)
"dx -execonly &" seems to work fine, although no windows open. This is what
it
says:
Memory cache will use 24 MB (2 for small items, 22 for large)
port = 1900
If someone knows how to fix my problem, please lend a hand. Since so many
users
have complained about this exact problem, but no answer is out there yet,
it is
probably important that this issue gets resolved. Sometimes people with
this
question are told to use the windows openDX binary, but I don't want to do
this.
Thanks,
Luke
A FEW OTHERS WHO RECENTLY HAD THE SAME (OR SIMILAR) PROBLEM:
* To: [email protected]
* Subject: [opendx-users] Windows 95/NT (cygwin) - Internal Error detected
at
Macrodefinition.C : 631
* From: [EMAIL PROTECTED]
* Date: Wed, 29 Jan 2003 01:38:00 EST
* Reply-To: [email protected]
* Sender: [EMAIL PROTECTED]
* To: [email protected]
* Subject: [opendx-users] cygwin binaries
* From: Shan-Ho Tsai <[EMAIL PROTECTED]>
* Date: Mon, 30 Jun 2003 16:11:04 -0400 (EDT)
* In-Reply-To: <[EMAIL PROTECTED]>
* Reply-To: [email protected]
* Sender: [EMAIL PROTECTED]
* To: <[email protected]>
* From: "Arun Rajagopalan" <[EMAIL PROTECTED]>
* Date: Wed, 4 Jun 2003 11:57:22 -0400
* Importance: Normal
* Reply-To: [email protected]
* Sender: [EMAIL PROTECTED]
