[openssl-dev] [openssl.org #4583] AutoReply: Debian X32 and "fatal error: sys/cdefs.h: No such file or directory"

[noloader@gmail.com via RT]

>> # ./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"?

Kinda agree. I image there could be many cases like you describe.

In this case, there's not "too many" or "too numerous". There's only
one item of interest: -mx32. When Configure ignores it, it results in
a failed compile.

Jeff


-- 
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4583
Please log in as guest with password guest if prompted