Re: NO_OPENSSL broken...

[David Rhodus <sdrhodus@xxxxxxxxx>]

On Sun, 12 Dec 2004 18:04:37 +0100, Joerg Sonnenberger
<joerg@xxxxxxxxxxxxxxxxx> wrote:
> On Fri, Dec 10, 2004 at 06:45:18PM -0600, Spearow wrote:
> 
> 
> > Building world with NO_OPENSSL defined is broken as usr.bin/dc requires
> > -lcrypto. Can this be changed such that either dc is not built when
> > NO_OPENSSL is defined, or that it is built in a manner so as not to
> > reqire -lcrypto?
> 
> If we wouldn't build dc when NO_OPENSSL is set, it would make bc unusable
> and break standard compliance. We can't make it easily work without, because
> that mean code duplication. Why do you actually use NO_OPENSSL? This is
> an undocumented knob and for me, it should die.
> 

This option was added fir embedded systems makers that didn't need to
include openssl with their build.  I don't see breaking standard
compliance for those guys being a big deal as far as dc/bc goes...

-- 
                                            -David
                                            Steven David Rhodus
                                            <drhodus@xxxxxxxxxxx>