> [miroslav.za...@skype.net - Sat Jul 17 02:17:51 2010]:
>
> The cipher_table was always null when I accessed it and method
> ENGINE_unregister_ciphers was not called at all (even though
> breakpoint was set).
>
> Here is the backtrace.
>
Well that makes no sense at all, if cipher_table is NULL
> [philipp_s...@redfish-solutions.com - Tue Jul 06 23:40:15 2010]:
>
> On 6/29/09 3:26 PM, Stephen Henson via RT wrote:
> >
> >> Also, in a cross-compiling environment, "CC" tends to default to the
> >> target machine.
> >>
> >> If you're building intermediate binaries to be run as part of the
> >
On 7/18/10 10:00 AM, Stephen Henson via RT wrote:
[philipp_s...@redfish-solutions.com - Tue Jul 06 23:40:15 2010]:
On 6/29/09 3:26 PM, Stephen Henson via RT wrote:
Also, in a cross-compiling environment, "CC" tends to default to the
target machine.
If you're building intermediate binaries to
On 7/18/10 10:00 AM, Stephen Henson via RT wrote:
>> [philipp_s...@redfish-solutions.com - Tue Jul 06 23:40:15 2010]:
>>
>> On 6/29/09 3:26 PM, Stephen Henson via RT wrote:
Also, in a cross-compiling environment, "CC" tends to default to the
target machine.
If you're building
How does one pass in extra values for these variables into Configure?
In a cross-compile, I need to add various CFLAG values like -march=k6-2 ... and
for PEX_LIBS, --sysroot=$(STAGING_DIR)/usr/lib -L$(STAGING_DIR)/usr/lib ... etc.
Thanks.
__
> [philipp_s...@redfish-solutions.com - Sun Jul 18 19:02:04 2010]:
>
> The problem here is that the intermediate binaries like
> ./fips_standalone_sha1 are being built with the target compiler, not
> the host compiler.
>
> I had submitted a patch a year and a half ago to fix this issue, but
> for
