On Sat, Jun 8, 2024 at 12:46 AM Martin Jansa via
lists.openembedded.org
wrote:
>
> > > +-o_flag_munging = sed -e 's/-O\([1-9sgz][1-9sgz]*\)/-O0/g' -e
> > > 's/-Ofast/-O0/g'
> > > ++o_flag_munging = sed -e 's/[[:blank:]]-O\([2-9sgz][2-9sgz]*\)/ -O0 /'
> > > -e 's/[[:blank:]]-Ofast/ -O0 /g'
>
> I
> > +-o_flag_munging = sed -e 's/-O\([1-9sgz][1-9sgz]*\)/-O0/g' -e
> > 's/-Ofast/-O0/g'
> > ++o_flag_munging = sed -e 's/[[:blank:]]-O\([2-9sgz][2-9sgz]*\)/ -O0 /' -e
> > 's/[[:blank:]]-Ofast/ -O0 /g'
I guess the 1-9 should have stayed in this one (now it no longer
replaces -O1 with -O0) and als
This seems to fail:
| libtool: compile: arm-poky-linux-gnueabi-gcc -mfpu=neon -mfloat-abi=hard
-mcpu=cortex-a8 -fstack-protector-strong -O0 -D_FORTIFY_SOURCE=2 -Wformat
-Wformat-security -Werror=format-security -D_TIME_BITS=64
-D_FILE_OFFSET_BITS=64
--sysroot=/home/pokybuild/yocto-worker/beag
Characters like '-O2' or '-Ofast' will be replaced by '-O1' and '-O0'
respectively when compiling cipher and random in the filesystem
paths as well if they happen to contain '-O2' or '-Ofast
If we are cross compiling libgcrypt and sysroot contains such
characters, we would
get compile errors becau
