Sender: ml AT delorie DOT com
Message-ID: <33DDCB84.72140DD0@cdata.tvnet.hu>
Date: Tue, 29 Jul 1997 12:52:52 +0200
From: Molnar Laszlo <molnarl AT cdata DOT tvnet DOT hu>
MIME-Version: 1.0
To: Robert Hoehne <robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de>
CC: DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: perl for djgpp
References: <Pine DOT HPP DOT 3 DOT 95q DOT 970728120400 DOT 13578D-100000 AT newton DOT mathematik DOT tu-chemnitz DOT de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Robert Hoehne wrote:
 
>> When I first tried to run Configure, I received a SIGSEGV immediately
> And I got it, because I had in my djgpp.env the following:
> [bash]
> PATH_SEPARATOR=:
> [sh]
> PATH_SEPARATOR=:

Hmm. And how did you solved the problem? Did you change your djgpp.env
or msdos_djgpp.sh? Should I support this in msdos_djgpp.sh or just add a
warning to the README? 

> And some minor problems to the source distrib:
> I sent about half an hour to find the DJGPP readme
> until I found it randomly in the base dir where I
> unzipped the archive. Please move it to the bease
> src directory and name it readme.dos or readme.djg.

:-( Sorry. I'll move it the base dir.

> I searched for it, becuase I couldn't find a configure.bat
> (which was the next problem).

Ok, I'll rename prepare.bat.

> You should change the directory tree from
> gnu/src/p500401
> to only
> gnu/p500401

OK.

> And please try to strip the sources to the needed
> files only for DJGPP which is common usage for
> such huge source package (see the bnu281s.zip
> file, which is hardly stripped down)

Ok, I'll try to make it smaller, but the LIB and POD directories are the
big ones, and they must be shipped with the distribution.

> And at last some comments to your questions about
> the binary distribution. Because I'm not so familar
> with perl, I cannot say what the user really needs.
> But you should include at least the doc and all the
> stuff which is needed to use perl in a common way
> (for instance to use automake or autoheader).

I think about creating 3 archives for the binary distribution: one for
the executable programs and the documentation in .pod format (or should
I use .txt??), one for the LIB directory, and one for the documentation
in html format. What do you think?
 
> If the user needs really some special modules for
> doing tricky perl programming, he should get the
> sources and build them for it's own. I for instance
> thought also the first time about including`libbfd.a
> and so on in the binary binutils package but then
> I decided to not to do so.

Then I'll skip libperl.a and the headers too.

Thanks for your comments,
				Laszlo