Re: Build breakage

2023-12-13 Thread Jonathan Wakely
On Wed, 13 Dec 2023 at 20:56, Thomas Schwinge wrote: > > Hi! > > On 2023-12-13T20:27:44+, Jonathan Wakely wrote: > > On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote: > >> On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote: > >> > I am getting this failure to build from clean trunk. > >> >

Re: Build breakage

2023-12-13 Thread Thomas Schwinge
Hi! On 2023-12-13T20:27:44+, Jonathan Wakely wrote: > On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote: >> On 2023-12-13T11:15:54-0800, Jerry D via Gcc wrote: >> > I am getting this failure to build from clean trunk. >> >> This is due to commit r14-6499-g348874f0baac0f22c98ab11abbfa65fd172

Re: Build breakage

2023-12-13 Thread Jonathan Wakely
On Wed, 13 Dec 2023, 19:37 Thomas Schwinge, wrote: > Hi! > > On 2023-12-13T11:15:54-0800, Jerry D via Gcc 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

Re: Build breakage

2023-12-13 Thread Thomas Schwinge
Hi! On 2023-12-13T11:15:54-0800, Jerry D via Gcc 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 A