> 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)
Well, I don't think that you can complain about this one. Basically you can't assume that ./config will [gracefully] handle whatever you might think of. You probably meant to run 'CFLAGS=-mx32 ./config' and computer didn't get what you wanted. But they never do, don't they? Computers getting what you meant to do that is... > 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" Well, there is a trade-off. Special cases are too numerous to cover them all, so question would be if this would be common and grave enough to guard against. For example you can actually run ./Configure tru64-alpha-cc on your Linux computer. Running make would fail miserably, but would it give you right to say "you're not allowed to break the compile"? -- 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
