Date: Wed, 23 Jun 1999 11:17:11 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: "Edevaldo Pereira (q14792)" cc: djgpp AT delorie DOT com Subject: Re: TCL Port In-Reply-To: <376F8F7A.5D6FD48D@email.sps.mot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Tue, 22 Jun 1999, Edevaldo Pereira (q14792) wrote: > I created a directory structure like the unix one (/bin > /usr/bin /usr/local/bin etc...) just to avoid some problems I had > before. The /bin was necessary because it was looking for sh inside it. You shouldn't need any of these special directories. These are some of the small tidbits that the files I sent take care of. Creating special directories might be okay for a quick hack, but if you ever decide to release your port for others to use (which I hope you will), it should work out of the box on any DJGPP installation, without requiring users to make special directories and copy programs there. > Then I called the ./configure script it worked so well that i couldn't > believe. Detected the compiler, shared libraries, even some library > functions that were not present. It tests a lot of things. Yes, the current DJGPP environment is extremely compatible with Unix. It took a lot of work by many people, but with the pieces of this puzzle finally in place, the result is amazing, if you consider the initial incompatibilities between bare-bones DOS/Windows and Unix. > - When handling math exceptions the TCL code defines a structure with > the same name of a structure defined in DJGPP library (exception I > think). The structures were compatible in some way so I commented it > just to go on with the compilation. I suggest to return to this problem and handle it in a more ordered way. The DJGPP declaration, at least in v2.02, should not cause any trouble. And anyway, it's wrong for the application code to declare structures that are declared in the system headers. Please try to find out what went wrong. > - There is a file copy command in TCL. Inside this command it tests to > see if the file is a link. Inside this function it called a macro that > were not defined. It may be a problem with the configuration script. Either the configure script should check if symlinks work, or, even better, the code that requires symlinks should be conditioned on #ifdef S_ISLNK.