Sender:	edevaldo AT pobox DOT mot DOT com
Message-ID:	<3770DA55.8151512A@email.sps.mot.com>
Date:	Wed, 23 Jun 1999 10:00:05 -0300
From:	"Edevaldo Pereira (q14792)" <q14792 AT email DOT sps DOT mot DOT com>
Organization:	Motorola - Semiconductor Producrs Sector
X-Mailer:	Mozilla 4.07 [en] (X11; I; SunOS 5.5.1 sun4u)
MIME-Version:	1.0
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC:	djgpp AT delorie DOT com
Subject:	Re: TCL Port
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 990623111651 DOT 13893B-100000 AT is>
X-Motorola-Sent-Wireless:	1
Reply-To:	djgpp AT delorie DOT com

Eli Zaretskii wrote:
> 
> 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.
>

	Oh yes! I did it that way only to see how big was the problem. As I
said yesterday it's not so big as I thought before. But I had a problem
with the scripts you sent me, I tried to execute the .bat file and when
it runs sed it gives me an error like "Error in line 1 unmatched {".
Despite of line one be a comment in all files I have, I started to look
in the sed documentation, It's a nice program to learn but takes some
time. Did it happen to you before?

> 
> 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.
> 

	As I said before it was only an extreme quick and very dirty hack, but
there was something funny about it. That structure only is declared for
one type of system and I think it is AIX. They use a lot of ifdefs to do
it.

> >       - 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.

	Thanks,


					Edevaldo

- Raw text -