Hey, On 07 May 2019, at 22:26, Frits Letteboer <[email protected]> wrote:
> > On 07-05-19 10:37, Frits Letteboer wrote: >> Source: https://gitlab.gnome.org/GNOME/glib/merge_requests/626 > > My apologies, it obviously is glib and glibc. yep, I realised this typo, no need to send a note for that ;-) I was just reviewing this, and as mentioned in the previous email I think this should probably already be work a rounded with the glib.desc line: [O] var_append GCC_WRAPPER_REMOVE ' ' '-Werror=format=2' # TODO: remove w/ update! As also mentioned in the previous email I guess that might not work for you if you built on a host system with a relatively new bash. I finally debugged this and it was a super supple (yet strange) bash variable escape expansion glitch (bug, issue, features, maybe standard compatibility change): svn di -c r48257 I would assume with svn up to this revision the command wrapper should finally work again for everyone (yay!) and also for you to potentially remove the -m[0-9]* o those -m68xxx in that gcc parse-config or what it was. You can check if this works by looking into the top of a newly build var/adm/logs usually they should show a wrapper test like: Old Command: gcc --version ENVPREFIX = 'CMD' OTHERS = '' INSERT = '--help?:-pipe -Os -march=core2' REMOVE = '-I/usr/local/include -I/usr/include -O -O[0-9sg] -mtune* -march* -mcpu* -Werror -Wextra -g*' APPEND = '-s' If they are all empty then the wrapper is not working due this amazing bash features. With the latest svn/trunk :HEAD this should finally be solved with a really poor-man’s workaround. Hope this helps, looking forward to more patches! René -- ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin, https://exactcode.com https://exactscan.com | https://ocrkit.com | https://t2sde.org | https://rene.rebe.de
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
