Mark -
I have never seen this problem in the release tarballs.
The major place we hit this is in cygwin, which (depending on the setting used when
installing cygwin) may automagically unpack/untar all your source code into CR/LF
files! The only way I have ever seen it on a Linux system was when (I suspect) the
source was FTPed in BIN mode from a windoze box.
Mike
----
Michael Kobar [EMAIL PROTECTED]
Software Engineer 860.434.4018
Lymeware Corporation 801.383.9021 fax
www.lymeware.com
> >--- "Mark H. Wood" <[EMAIL PROTECTED]> wrote:
> Curiouser and curiouser! I unpacked a fresh kit
> tree yet again. I ran
> those files through a little tool I wrote which
> replaces <CR><LF> with
> <NL>. Output size = input size, so no '<CR><LF>'
> sequences were found.
> Then I ran 'od -c Makefile.org | less' and had less
> search for naked <CR>s
> (/\\r) and found none, so they aren't in <LF><CR>
> sequences either. (I
> tested this with '/\\n', and less found the newlines
> with no problem.)
>
> I don't know where your <CR>s are coming from. But
> thanks for the tip.
>
> --
> Mark H. Wood, Lead System Programmer
> [EMAIL PROTECTED]
> MS Windows *is* user-friendly, but only for certain
> values of "user".
>
>
> On Thu, 8 Aug 2002, Michael Kobar wrote:
> > I too have run into this problem, and it was due
> > to CR/LFs in both the
> > Makefile.orig and the Configure script. After
> > running the ./Config (or
> > ./Configure) you will notice that the SDIRS in the
> > generated Makefile
> > will still contain rc5 and idea which causes your
> > problem.
> >
> >
> > Mike
> >
> > ----
> > Michael Kobar [EMAIL PROTECTED]
> > Software Engineer 860.434.4018
> > Lymeware Corporation 801.383.9021 fax
> > www.lymeware.com
> >
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
