On Mon, Jun 5, 2023 at 7:43 AM Andrew Pinski wrote:
>
> On Sun, Jun 4, 2023 at 10:24 PM Richard Biener via Gcc-patches
> wrote:
> >
> >
> >
> > > Am 05.06.2023 um 06:42 schrieb Andrew Pinski via Gcc-patches
> > > :
> > >
> > > On sh target, there is a MULTILIB_DIRNAMES (or is it MULTILIB_OPTION
On Sun, Jun 4, 2023 at 10:24 PM Richard Biener via Gcc-patches
wrote:
>
>
>
> > Am 05.06.2023 um 06:42 schrieb Andrew Pinski via Gcc-patches
> > :
> >
> > On sh target, there is a MULTILIB_DIRNAMES (or is it MULTILIB_OPTIONS)
> > named m2,
> > this conflicts with the langauge m2. So when you do
> Am 05.06.2023 um 06:42 schrieb Andrew Pinski via Gcc-patches
> :
>
> On sh target, there is a MULTILIB_DIRNAMES (or is it MULTILIB_OPTIONS) named
> m2,
> this conflicts with the langauge m2. So when you do a `make clean`, it will
> remove
> the m2 directory and then a build will fail. Now
On sh target, there is a MULTILIB_DIRNAMES (or is it MULTILIB_OPTIONS) named m2,
this conflicts with the langauge m2. So when you do a `make clean`, it will
remove
the m2 directory and then a build will fail. Now since r0-78222-gfa9585134f6f58,
the multilib directories are no longer created in the