memory.h is in the following path: [ I am using Linux debian 2.6.26-2-686 #1
SMP Thu Nov 25 01:53:57 UTC 2010 i686 GNU/Linux ]
/usr/src/linux-headers-2.6.26-2-686/include/linux/memory.h
So make sure your path is set properly to include the linux include files
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Michael Bergandi
Sent: Wednesday, December 29, 2010 2:37 PM
To: [email protected]
Subject: memory.h confusion: Is it needed?
Hi all,
While porting OpenSSL v1.0.0c I got a 'no such file' error on an include of
<memory.h>. The error is correct. My platform has no memory.h. So, I
investigated a little further as to where and if it is needed. I only see
memory.h included in the following:
$ grep \<memory\.h\> . -r -C2
./crypto/asn1/bio_ndef.c-
./crypto/asn1/bio_ndef.c-#ifndef OPENSSL_SYSNAME_NETWARE
./crypto/asn1/bio_ndef.c:#include <memory.h> ./crypto/asn1/bio_ndef.c-#endif
./crypto/asn1/bio_ndef.c-#include <stdio.h>
grep: ./crypto/cms/cms.h: Too many levels of symbolic links
--
./crypto/jpake/jpake.c-#include <openssl/sha.h>
./crypto/jpake/jpake.c-#include <openssl/err.h>
./crypto/jpake/jpake.c:#include <memory.h>
./crypto/jpake/jpake.c-
./crypto/jpake/jpake.c-/*
--
./crypto/pkcs7/bio_pk7.c-
./crypto/pkcs7/bio_pk7.c-#ifndef OPENSSL_SYSNAME_NETWARE
./crypto/pkcs7/bio_pk7.c:#include <memory.h> ./crypto/pkcs7/bio_pk7.c-#endif
./crypto/pkcs7/bio_pk7.c-#include <stdio.h>
--
./crypto/seed/seed.c-#include <string.h> ./crypto/seed/seed.c-#ifdef WIN32
./crypto/seed/seed.c:#include <memory.h> ./crypto/seed/seed.c-#endif
./crypto/seed/seed.c-
--
./demos/ssl/cli.cpp-
./demos/ssl/cli.cpp-#include <stdio.h>
./demos/ssl/cli.cpp:#include <memory.h>
./demos/ssl/cli.cpp-#include <errno.h>
./demos/ssl/cli.cpp-#include <sys/types.h>
--
./demos/ssl/serv.cpp-#include <unistd.h> ./demos/ssl/serv.cpp-#include
<stdlib.h> ./demos/ssl/serv.cpp:#include <memory.h>
./demos/ssl/serv.cpp-#include <errno.h> ./demos/ssl/serv.cpp-#include
<sys/types.h>
grep: ./include/openssl/cms.h: Too many levels of symbolic links
My concern is with the actual library code, not the demo stuff. My confusion
comes from the #ifdef's around the include. In one place, it gets include
for everyone but NETWARE, in another only for WIN32, and in JPAKE (i know
this experimental code) says include it for everyone.
I looked through the source for each and I can't determine where anything
from memory.h is even being used.
Can someone else confirm whether or not memory.h is actually needed?
If so, under what system should it be included?
I can submit a patch to clean it up after we sort it out.
--
Mike
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
