Hi!
> Yes, and I have fixed this two weeks ago. The problem is that the "ADDINC" > and "ADDLIB" variables are not suited for passing single-component paths > since they suffix everything. Look what it results in your build log : > > -lcrypt -lssl -lcrypto -L/usr/lib -Wl,-Bstatic -lpcreposix \ > -lpcre -Wl,-Bdynamic -L/tmp/staticlibssl/lib -ldl > > As you can see, -lssl and -lcrypto are looked up in your system path. Ok, but what I don't get is why does it work on some system and not on others? For me, on Debian and Ubuntu, it always worked fine, see this: > Since commit 9a05945bd0, you now have an explicit set of SSL_INC/SSL_LIB > variables, just like with PCRE, that you can point to your openssl > location. I'm using this to build with a static openssl version, as > this time it's safe, as you can see below : > > # in the usual path, use SSL_INC=/path/to/inc and SSL_LIB=/path/to/lib. > BUILD_OPTIONS += $(call ignore_implicit,USE_OPENSSL) > OPTIONS_CFLAGS += -DUSE_OPENSSL $(if $(SSL_INC),-I$(SSL_INC)) > OPTIONS_LDFLAGS += $(if $(SSL_LIB),-L$(SSL_LIB)) -lssl -lcrypto > > If you have a recent enough haproxy snapshot, simply make these two > variables point to the proper location and it will be OK. > > Best regards, > Willy > >
