Thanks for Your answer!
I was not clearly describing our problem, sorry! Our project is for embedded devices running on MIPS processors. The system has a special OS, not Linux.
The development system is under Linux, and we are compiling OpenSSL with cross compile option for MIPS. We also compile the code for Linux, so that we have a simulation of the embedded system, that can be easily debugged under Linux.
Our problem is, that the OpenSSL V1.1.1d needs includes, that are nonexistent for MIPS in our development system. These headers were not needed for 1.0.2.
My question is not a 100% OpenSSL question. But I think, as OpenSSL is widely used on non-Linux/Windows/… systems, the question is legitime to ask, what to use on special systems? Or why are these headers needed now?
The programmer, who changed the code, probably had an idea about that.
Best regards,
Balazs
From: openssl-users <openssl-users-bounces@xxxxxxxxxxx> on behalf of Balázs Horváth <balazs.horvath.email@xxxxxxxxx>
Sent: Monday, March 30, 2020 10:00
> Following extra includes are needed:
> arpa/inet.h
> netinet/tcp.h
> netinet/in.h
> strings.h
> netdb.h
> sys/socket.h
> sys/ioctl.h
> sys/un.h
These are system headers, not OpenSSL headers. OpenSSL has no control over them.
> For Linux the includes under /usr/include work, but for MIPS they give compile errors.
Then you're using the wrong headers for the MIPS compilation. To be honest, it's not clear to me what you're doing, because Linux is an operating system (or more precisely a kernel), and MIPS is a processor family.
> What should we use for MIPS?
This is not an OpenSSL question. It's a cross-compilation question (I think, since I'm not sure what you're actually trying to do), and so depends on your cross-compilation toolchain.
