On Thu, Jun 23, 2016 at 6:44 AM, Andy Polyakov via RT <r...@openssl.org> wrote: >> 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...
Fair enough, agreed. But Configure ignored my instructions: # ./config CFLAGS="-mx32" Operating system: x86_64-whatever-linux2 Configuring for linux-x86_64 Configuring OpenSSL version 1.1.0-pre6-dev (0x0x10100006L) target already defined - linux-x86_64 (offending arg: CFLAGS=-mx32) And: # ./config -mx32 Operating system: x86_64-whatever-linux2 Configuring for linux-x86_64 Perhaps the second case should fail at configure just like the first case. Upon failure, it would be nice to tell the user what to do: "Please configure with ./Configure linux-x32" Jeff -- 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
