When looking into Yast, both zlib and zlib-devel Version 1.2.3 are installed.
Maybe ISPConfig expects them at another location?
How do I find where the needed files are and how do I tell ISPConfig this location?
Or any other ideas?

Yes, it's strange. So I talked to the support for my vserver a few minutes before.

- They confirmed that it is a 64-bit host system.
- They also confirmed that the "uname -m" looks strange.
- They told me to use the *x86_64.rpm files.

But for sure they had no solution for the compilation problem...

I tried another trick last night:
I found many others via google they also have problems while compiling openssl. Nearly or completely the same errors. I read about a "workaround" which is also mentioned in the INSTALL-readme in the openssl package: compile with "no-asm". The compilation worked fine without any errors. I was lucky! But it lasts just a few seconds. The generation of the certificates which is done via the mkcert.sh in your setup2 or somewhere doesn't work properly then. It tries to generate a certificate (many "." are printed to screen) but the generator never ends. I canceled it after about two minutes of "whatching dots". I don't know if it is another problem or just the result of the "quick and dirty hack" with the openssl package.

I tried to "config" and "make" openssl again and did a "make test" afterwards. The make succeeded, the test failed. So I tried a "make report" to see what's going wrong. The only error I see is the following:

Maybe you should ask the OpenSSL guys. This is a SuSE 64Bit specific problem. Suse is known to be problematic on 64Bit installations as many software wnt compile correctly. I guess that the Suse guys added some incompatible patches to their applications.

It can't be true that this is the moment I have to deinstall postfix, install QMail and use Plesk!

Click to expand...

Or you use a better suited linux distribution like debian, centos or fedora This is not a problem with ISPConfig, its just a problem that SuSE had made its 64Bit distribution / compiler aplications incompatible to some major software packages like openssl.

Yes, for sure it's not a problem of you and your ISPconfig software. I know SuSE sometimes does strages things. :-( But we always do SuSE Linux Enterprise Server in our company and had never had such strage behaviours - so I decided to use SuSE in the private sector too. ;-)

But now I switched to a Ubuntu 6.10 vServer. ISP installed perfect there. I already have other questions, but I think I should post them in a separate thread.