Re: Verify AES support when Blumenthal draft is enabled

Keith Mendoza <[email protected]>
Newsgroups gmane.network.net-snmp.devel
Message-ID <1524972686.1564770.1354307168.1C9B536C@webmail.messagingengine.com>

On Fri, Apr 27, 2018, at 11:00 PM, Keith Mendoza wrote:
> > 
> > Regardless, configure should be doing the right thing based on what
> > is currently installed.
> > 
> > BVA> Regarding your pull request:
> > BVA> I'd like to avoid adding AC_CHECK_HEADERS() calls in
> > BVA> config_project_with_enable because whether or not these
> > BVA> succeed depend on the compiler flags (-I) and some compiler
> > BVA> flags are only set at a later phase.
> > 
> > I agree that header checks inside a feature check is undesirable.
> > Keith, do you think you could come up with a patch that re-arranges
> > configure checks that that the desired effect is achieved?
> 
> Let me give this another go. I think the best solution is when --with-
> openssl is processed that a variable like "blumenthalcapable" be set 
> based on whether the AES-related functions and headers are available. 
> This will also open it up to other configuration checks that may need 
> the same things.

https://sourceforge.net/p/net-snmp/code/merge-requests/14/ has my proposed changes.

> 
> > 
> > Robert
> 
> 
> -- 
> Thanks,
> Keith (pantherse)


-- 
Thanks,
Keith (pantherse)

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.