On Sun, Apr 01, 2001 at 10:40:46PM +0100, Brian Somers wrote:
> Hi,
>
> I'm not convinced that the patch will help. It looks like the error
> is because it's using the ppp.lo that was built with crypto support
> but without the mppe bits. Maybe other objects (such as ccp.o in
> this case - w
Hi,
I'm not convinced that the patch will help. It looks like the error
is because it's using the ppp.lo that was built with crypto support
but without the mppe bits. Maybe other objects (such as ccp.o in
this case - which seems to be built with HAVE_DES and therefore
includes MPPEAlgorithm
Hi!
This was tricky. Due to the old bug in release/Makefile (it did
not pass -DRELEASE_CRUNCH when building list of object files for
crunched binary), ${OBJS} list for ppp was computed incorrectly,
and ppp/Makefile had a special glue to build empty object files:
: .if defined(RELEASE_CRUNCH)
:
Hi Ruslan,
>
> Could you please try the attached patch and let me know?
>
> I had to move -DRELEASE_CRUNCH to *_fixit.conf so that
> ${OBJS} are computed correctly for usr.bin/telnet.
I have tried it, but now it breaks in boot_crunch:
##
cc -O -pipe-DCRUNCHED_BINARY -c tunefs_stub
John!
Could you please try the attached patch and let me know?
I had to move -DRELEASE_CRUNCH to *_fixit.conf so that
${OBJS} are computed correctly for usr.bin/telnet.
On Thu, Mar 29, 2001 at 10:08:50AM +0200, John Hay wrote:
> > On Wed, Mar 28, 2001 at 01:00:59PM +0300, Ruslan Ermilov wrote:
Hi!
I don't see how my changes to non-secure Makefiles might affect this.
What I did is disabled building of non-secure, standard libtelnet,
telnet and telnetd if we are also building the secure versions.
I did not touch the secure/ versions in this commit. Moreover, the
standard versions are st
Hi Ruslan,
On the 26th you made changes to the Makefiles with this log message:
##
Do not build (and install) both secure/ and standard versions
of libtelnet, telnetd, and telnet. This only worked because
secure/ was listed late in SUBDIR in Makefile.inc1.
##
Did you chec