Building ZNC on SmartOS (Illumos) Fails to ./configure and build properly #205

New Issue

2026-10-05T04:04:18+02:00

adam commented

2026-10-05 04:04:18 +02:00

During the configure, "checking whether openssl is usable...no" will get triggered every time. Ive tried setting --with-openssl, openssl_CFLAGS, openssl_LIBS, CXXFLAGS, LDFLAGS, just about everything.

I got it to compile by removing that check entirely and hardcoding SSL=yes and specifiying --with-openssl=/path/to/my/openssl.

I also had to remove the '-mt' flag that was getting set in all the Makefiles. It was trying to pass a Sun WorkShop flag to gcc even tho it detected the compiler as gcc.

also the library path to libssl.so.1.0.0 had to be set via crle, this was probably due to the way I built it but anyhow, I got it built and it works flawlessy so far.

Id like to help assist in making this build correctly on SmartOS

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

During the configure, "checking whether openssl is usable...no" will get triggered every time. Ive tried setting --with-openssl, openssl_CFLAGS, openssl_LIBS, CXXFLAGS, LDFLAGS, just about everything. I got it to compile by removing that check entirely and hardcoding SSL=yes and specifiying --with-openssl=/path/to/my/openssl. I also had to remove the '-mt' flag that was getting set in all the Makefiles. It was trying to pass a Sun WorkShop flag to gcc even tho it detected the compiler as gcc. also the library path to libssl.so.1.0.0 had to be set via crle, this was probably due to the way I built it but anyhow, I got it built and it works flawlessy so far. Id like to help assist in making this build correctly on SmartOS ## <bountysource-plugin> Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/138093-building-znc-on-smartos-illumos-fails-to-configure-and-build-properly?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin>

adam closed this issue

2026-10-05 04:04:18 +02:00

adam commented

2026-10-05 04:04:19 +02:00

Pastebin config.log

2013/3/18 William Broach notifications@github.com

During the configure, "checking whether openssl is usable...no" will get
triggered every time. Ive tried setting --with-openssl, openssl_CFLAGS,
openssl_LIBS, CXXFLAGS, LDFLAGS, just about everything.

I got it to compile by removing that check entirely and hardcoding SSL=yes
and specifiying --with-openssl=/path/to/my/openssl.

I also had to remove the '-mt' flag that was getting set in all the
Makefiles. It was trying to pass a Sun WorkShop flag to gcc even tho it
detected the compiler as gcc.

also the library path to libssl.so.1.0.0 had to be set via crle, this was
probably due to the way I built it but anyhow, I got it built and it works
flawlessy so far.

Id like to help assist in making this build correctly on SmartOS

—
Reply to this email directly or view it on GitHubhttps://github.com/znc/znc/issues/309
.

Pastebin config.log 2013/3/18 William Broach notifications@github.com > During the configure, "checking whether openssl is usable...no" will get > triggered every time. Ive tried setting --with-openssl, openssl_CFLAGS, > openssl_LIBS, CXXFLAGS, LDFLAGS, just about everything. > > I got it to compile by removing that check entirely and hardcoding SSL=yes > and specifiying --with-openssl=/path/to/my/openssl. > > I also had to remove the '-mt' flag that was getting set in all the > Makefiles. It was trying to pass a Sun WorkShop flag to gcc even tho it > detected the compiler as gcc. > > also the library path to libssl.so.1.0.0 had to be set via crle, this was > probably due to the way I built it but anyhow, I got it built and it works > flawlessy so far. > > Id like to help assist in making this build correctly on SmartOS > > — > Reply to this email directly or view it on GitHubhttps://github.com/znc/znc/issues/309 > .

adam commented

2026-10-05 04:04:20 +02:00

Here is the config.log: http://pastie.org/pastes/6606636/text

It looks like when configure went to compile the test code to deteremine if openssl is was working it was passing that -mt flag to gcc causing the test code to not compile in turn causing configure to fail the openssl check.

Here is what I did to get it to compile: http://pastie.org/pastes/6606678/text

Here is the config.log: http://pastie.org/pastes/6606636/text It looks like when configure went to compile the test code to deteremine if openssl is was working it was passing that -mt flag to gcc causing the test code to not compile in turn causing configure to fail the openssl check. Here is what I did to get it to compile: http://pastie.org/pastes/6606678/text

adam commented

2026-10-05 04:04:20 +02:00

Meh. This is another case of "m4/ax_pthread.m4 was meant for C, not for C++". It uses $GCC, but in our case it actually wants "$GXX" for this check. I don't remember where I saw that problem before...

Meh. This is another case of "m4/ax_pthread.m4 was meant for C, not for C++". It uses $GCC, but in our case it actually wants "$GXX" for this check. I don't remember where I saw that problem before...

adam commented

2026-10-05 04:04:21 +02:00

Can anyone provide some guidance as to how I might go about fixing this issue?

Can anyone provide some guidance as to how I might go about fixing this issue?

adam commented

2026-10-05 04:04:22 +02:00

You could try replacing $GCC with $GXX in m4/ax_pthread.m4.

You could try replacing $GCC with $GXX in m4/ax_pthread.m4.

adam commented

2026-10-05 04:04:22 +02:00

Curious if anyone has gotten this successfully build.

Curious if anyone has gotten this successfully build.

adam commented

2026-10-05 04:04:23 +02:00

What is the case with 1.6.1?

What is the case with 1.6.1?

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#205