On Mon, Jul 4, 2022 at 3:09 PM Martin Liška wrote:
>
> On 7/4/22 14:28, Richard Biener wrote:
> > ... but ... is libatomic properly built for the host? libgo is a
> > target library.
>
> You're correct.
>
> Well, so the host library should be taken, which works for stage1 lto-plugin:
>
> [ 668s]
On 7/4/22 14:28, Richard Biener wrote:
> ... but ... is libatomic properly built for the host? libgo is a
> target library.
You're correct.
Well, so the host library should be taken, which works for stage1 lto-plugin:
[ 668s] libtool: link: gcc -shared -fPIC -DPIC .libs/lto-plugin.o
-pth
On Mon, Jul 4, 2022 at 2:28 PM Richard Biener
wrote:
>
> On Mon, Jul 4, 2022 at 1:32 PM Martin Liška wrote:
> >
> > Similarly to libgo, we need to provide -L for targets where
> > libpthread does depends on libatomic.
> >
> > Ready for master?
>
> OK
... but ... is libatomic properly built for t
On Mon, Jul 4, 2022 at 1:32 PM Martin Liška wrote:
>
> Similarly to libgo, we need to provide -L for targets where
> libpthread does depends on libatomic.
>
> Ready for master?
OK
> PR bootstrap/106156
>
> lto-plugin/ChangeLog:
>
> * Makefile.am: Use PTHREAD_CFLAGS.
> * M
Similarly to libgo, we need to provide -L for targets where
libpthread does depends on libatomic.
Ready for master?
PR bootstrap/106156
lto-plugin/ChangeLog:
* Makefile.am: Use PTHREAD_CFLAGS.
* Makefile.in: Regenerate.
* configure.ac: Detect if PTHREAD_CFLAGS sh
