On 12/10/2013 07:40 PM, Burton, Ross wrote:
On 10 December 2013 11:37, Richard Purdie
wrote:
I thought it would do no harm. And I will send this patch to upstream,
so it might be a little strange that I only modify the Makefile.am file
even if Makefile.in has the same problem.
It can actually
On 10 December 2013 11:37, Richard Purdie
wrote:
>> I thought it would do no harm. And I will send this patch to upstream,
>> so it might be a little strange that I only modify the Makefile.am file
>> even if Makefile.in has the same problem.
>
> It can actually be harmful since the modification t
On Fri, 2013-12-06 at 09:30 +0800, ChenQi wrote:
> On 12/06/2013 06:41 AM, Saul Wold wrote:
> > On 12/05/2013 12:55 AM, qi.c...@windriver.com wrote:
> >> From: Chen Qi
> >>
> >> Characters like '-O2' or '-Ofast' will be replaced by '-O1' when
> >> compiling cipher. If we are cross compiling libgcr
On 12/06/2013 06:41 AM, Saul Wold wrote:
On 12/05/2013 12:55 AM, qi.c...@windriver.com wrote:
From: Chen Qi
Characters like '-O2' or '-Ofast' will be replaced by '-O1' when
compiling cipher. If we are cross compiling libgcrypt and sysroot
contains such characters, we would get compile errors b
On 12/05/2013 12:55 AM, qi.c...@windriver.com wrote:
From: Chen Qi
Characters like '-O2' or '-Ofast' will be replaced by '-O1' when
compiling cipher. If we are cross compiling libgcrypt and sysroot
contains such characters, we would get compile errors because the
sysroot path has been modified.
From: Chen Qi
Characters like '-O2' or '-Ofast' will be replaced by '-O1' when
compiling cipher. If we are cross compiling libgcrypt and sysroot
contains such characters, we would get compile errors because the
sysroot path has been modified.
Fix this by adding whitespaces before and after the o
