> Hi all, > I want cross compile openssl for arm-xilinx-linux-gnueabi-gcc > platform .I have downloaded source code openssl-1.02a and I have looked > options for > for configure file. Arm-xilinx-linux-gnueabi is not found in list of > os/compiler option .so I selected linux-armv4 and configure like this > ./configure no-threads shared linux-armv4 --prefix=/home/sum/ > --openssl=/home/sum/
Normally cross-compiler toolchain is prefixed, e.g. compiler is called arm-linux-gnueabi-gcc. To cross-compile you are expected to pass --cross-compile-prefix as additional argument to ./Configure, for mentioned example --cross-compile-prefix=arm-linux-gnueabi-, or set CROSS_COMPILE environment variable prior ./Configure. > Configuration is successful when I going for make itt has given me error > stating that > > relocation R_ARM_MOVW_ABS_NC against `a local symbol' can not be used when > making a shared object; recompile with -fPIC > libcrypto.a(armcap.o): error adding symbols: Bad value Well, if right target compiler was called and with right flag, i.e. with -fPIC as directed by linux-armv4 config line, then it's likely between you and your system vendor. I mean there is nothing we can do about your compiler. It might happen that it was not the first attempt to configure and compile in that directory, so that there is remote possibility that file was originally compiled without -fPIC and then wasn't recompiled. In this case 'make clean' or just starting over would solve the problem. > under compiler options why arm-none-linux-gneabi support is not there? Because it's unfeasible to create all possible configurations. Instead single processor-specific is supported that allows for customization at Configure command line. _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
