Iain's fix changes the assembly output to succeed if the assembler detected
during the i386 gcc build is clang, but this is not an on-the-fly change,
rather a configure-at-build change... so for our purposes, we will still need
to force the older gas behaviour when gcc is built i386, so gcc
Iain has sorted out what the error is.
Apparently it is fixed in gcc9+, so I'll try those and see if they build i386
now.
He is prepared to backport the fixes into gcc5 to gcc8 so that the i386 builds
won't error out if clang/llvm is used as assembler.
So once that is available, we can add
>
> I'm puzzled. If this is solely about building gcc itself, doesn't that
> mean that the iuse of /usr/bin/as is only inflicted on gcc itself?
it means that gcc would use /usr/bin/as as the default assembler going forward
for everything it builds, unless forced to do otherwise. This is
On Wed, 4 Mar 2020, Ken Cunningham wrote:
On Tue, 25 Feb 2020, Ken Cunningham wrote:
building i386, gcc 5,6,7,8 misconfigures when our "as" redirects it to
clang for assembly, following our hack in cctools to do that. the gcc
build then fails.
I have not so far been able to overcome this
I am discussing with the gcc darwin lead to see if any other options are
available.
Ken
> On Tue, 25 Feb 2020, Ken Cunningham wrote:
>
> > building i386, gcc 5,6,7,8 misconfigures when our "as" redirects it to
> > clang for assembly, following our hack in cctools to do that. the gcc
> > build then fails.
> >
> > I have not so far been able to overcome this other than:
> >
> > 1.
On Tue, 25 Feb 2020, Ken Cunningham wrote:
building i386, gcc 5,6,7,8 misconfigures when our "as" redirects it to
clang for assembly, following our hack in cctools to do that. the gcc
build then fails.
I have not so far been able to overcome this other than:
1. deactivating all clangs 5+
So, second notice / heads up on this.
Plan is:
to roll back to libgcc / gcc 7.4.x on 10.4, 10.5, and maybe on i386 10.6.
to conflicts_build every clang version >= 5.0 when build_arch is i386 on every
gcc version >= 5.
and then this will perhaps stay like this forever, or at least until some
building i386, gcc 5,6,7,8 misconfigures when our "as" redirects it to clang
for assembly, following our hack in cctools to do that. the gcc build then
fails.
I have not so far been able to overcome this other than:
1. deactivating all clangs 5+ prior to the build, to get the old gas
or
2.
