Open mukeshmohanan opened 1 year ago
I'm afraid we are not supporting haproxy
any more. In addition, the support for oqs-openssl111 that this old code is built on is also going EOL. Please let us know about your use case and we might re-prioritize. In any case, it would need to be added to #182.
Okay. I understand support is only for ops-provider(which is base don opens 3.x) , I have used that few weeks back.
my use case to pack the haproxy container along with the sample webApp container with in a single , then expose the ha-proxy service alone to outside which will then forward the request back to the webapp service . For that I was trying to build the haproxy image using the steps outlined the README , but strange that gcc complains unrecognised command-line option '-m64' . I believe I miss something in MAC os set up . should I really need to set up a cross complier to make the docker build ? do you have any advise on the same ?
Okay. I understand support is only for ops-provider(which is base don opens 3.x) , I have used that few weeks back.
my use case to pack the haproxy container along with the sample webApp container with in a single , then expose the ha-proxy service alone to outside which will then forward the request back to the webapp service . For that I was trying to build the haproxy image using the steps outlined the README , but strange that gcc complains unrecognised command-line option '-m64' . I believe I miss something in MAC os set up . should I really need to set up a cross complier to make the docker build ? do you have any advise on the same ?
I guess overlooked the same , the gcc error is ideally coming from the docker build isn't it ? so somehow the base image gcc throws error w.r.t to the gcc flag ? or am I terribly wrong ?
I believe I miss something in MAC os set up . should I really need to set up a cross complier to make the docker build ? do you have any advise on the same ?
I'd personally always check what OpenSSL does for the platform I'm interested in (see https://github.com/openssl/openssl/tree/master/.github/workflows). In your case "darwin64-arm64" seems to be the right config option (instead of the x64
config option in our old haproxy Dockerfile).
I believe I miss something in MAC os set up . should I really need to set up a cross complier to make the docker build ? do you have any advise on the same ?
I'd personally always check what OpenSSL does for the platform I'm interested in (see https://github.com/openssl/openssl/tree/master/.github/workflows). In your case "darwin64-arm64" seems to be the right config option (instead of the
x64
config option in our old haproxy Dockerfile).
I tried that option , but not luck . error logs below . I wonder whether the gcc with in the alpine image is causing this issue or somehow the host gcc/architecture is causing . I believe people in his community already did similar build in Mac OS ARM so this os something verified stuff. So I assume it could be very much tied to the machine I do the build
aishwaryanarayanan@Aishwaryas-MBP haproxy % cat Dockerfile | grep darwin RUN LDFLAGS="-Wl,-rpath -Wl,$INSTALLPATH/lib" ./Configure darwin64-arm64-cc -prefix=$INSTALLPATH && if [[ -z "$MAKE_DEFINES" ]] ; then nproc=$(getconf _NPROCESSORS_ONLN) && MAKE_DEFINES="-j $nproc"; fi && make $MAKE_DEFINES && make install_sw aishwaryanarayanan@Aishwaryas-MBP haproxy %
I'm afraid I'm out of my depth there: Those are OpenSSL compile errors on a platform I'm not familiar with. You probably have to ask the OpenSSL team for help on this. But then again, this is a pretty much EOL'd software version... I'd personally try moving everything over to OpenSSL3 rather than spend time on outdated software.
haproxy build failing in MacOS
aishwaryanarayanan@Aishwaryas-MBP haproxy % uname -a Darwin Aishwaryas-MBP.fritz.box 22.5.0 Darwin Kernel Version 22.5.0: Thu Jun 8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000 arm64 aishwaryanarayanan@Aishwaryas-MBP haproxy %
error message captured below, I tried to the Dockerfile with darwin64-arm64-cc arg against the ./Configure but that does not help
am missing some pre-requisite to build this in MacOS ?