On Wed, 13 Dec 2023 at 20:56, Thomas Schwinge <tho...@codesourcery.com> wrote: > > Hi! > > On 2023-12-13T20:27:44+0000, Jonathan Wakely <jwakely....@gmail.com> wrote: > > On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, <tho...@codesourcery.com> wrote: > >> On 2023-12-13T11:15:54-0800, Jerry D via Gcc <g...@gcc.gnu.org> wrote: > >> > I am getting this failure to build from clean trunk. > >> > >> This is due to commit r14-6499-g348874f0baac0f22c98ab11abbfa65fd172f6bdd > >> "libgomp: basic pinned memory on Linux", which supposedly was only tested > >> with '--disable-multilib' or so. As Andrew's now on vacations -- > >> conveniently ;-P -- I'll soon push a fix. > >> > >> (To restore your build, you may locally disable the 'gomp_debug' call, or > >> cast 'size' into '(long) size', for example.) > >> > > > > Wouldn't --disable-werror work too? > > I suppose so, but that comes with re-'configure'ing, re-starting the > build from scratch, or otherwise manually fiddling with 'Makefile's etc., > whereas after editing the source file as indicated, you may simply resume > 'make'.
True. Sometimes start a completely new build with different config is preferable to changing the sources. Sometimes it isn't :-)