>> Is it possible that real target is so called x32, i.e. x86_64 with
>> 32-bit address space limitation? In such case linux-x32 would be the
>> right target...
>
> I don't believe this is x32 since {x86_64|amd64} and __ILP32__ are not
> defined; see preprocessor output below.
Got it. But just
>> Is it possible that real target is so called x32, i.e. x86_64 with
>> 32-bit address space limitation? In such case linux-x32 would be the
>> right target...
>
> I don't believe this is x32 since {x86_64|amd64} and __ILP32__ are not
> defined; see preprocessor output below.
Got it. But just
On Mon, Mar 14, 2016 at 10:52 AM, Andy Polyakov via RT wrote:
> On 03/14/16 03:58, noloa...@gmail.com via RT wrote:
>> Working from Master...
>>
>> gentoo@Gentoo-2012 ~/openssl $ ./config
>> Operating system: x86_64-whatever-linux2
>> ...
>
> Can you confirm that it's not a
On Mon, Mar 14, 2016 at 10:52 AM, Andy Polyakov via RT wrote:
> On 03/14/16 03:58, noloa...@gmail.com via RT wrote:
>> Working from Master...
>>
>> gentoo@Gentoo-2012 ~/openssl $ ./config
>> Operating system: x86_64-whatever-linux2
>> ...
>
> Can you confirm that it's not a
> Is it possible that real target is so called x32, i.e. x86_64 with
> 32-bit address space limitation? In such case linux-x32 would be the
> right target...
On side note, I'm getting make test failures for linux-x32 target. I
mean if it turns out that it's the right target for you, and you see
On 03/14/16 03:58, noloa...@gmail.com via RT wrote:
> Working from Master...
>
> gentoo@Gentoo-2012 ~/openssl $ ./config
> Operating system: x86_64-whatever-linux2
> Configuring for linux-x86_64
> Configuring OpenSSL version 1.1.0-pre4-dev (0x0x1014L)
> no-crypto-mdebug [default]
Working from Master...
gentoo@Gentoo-2012 ~/openssl $ ./config
Operating system: x86_64-whatever-linux2
Configuring for linux-x86_64
Configuring OpenSSL version 1.1.0-pre4-dev (0x0x1014L)
no-crypto-mdebug [default] OPENSSL_NO_CRYPTO_MDEBUG (skip dir)
no-crypto-mdebug-backtrace