> you're not allowed to break the compile, regardless of whether there's > a proper "X32" kernel.
I don't understand what do you mean by "break the compile". I'd say it's the kind of thing that lies on both parties. We are responsible for providing code and config lines, but you have responsibilities too, you are responsible for providing sane compiler environment. For example if there is a system header file missing on target system [or another standard header file attempts to include non-existing system header file], there is nothing we can do. There either is a package missing, not installed, or vendor screwed up packaging... As suggested, start by ./Configure linux-x32... -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4583 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev