Re: ./configure --with-native-compilation on macos (11.5.2 Big Sur)

[Alan Third <alan@idiocy.org>]

On Mon, Sep 06, 2021 at 06:45:58PM +0900, Jean-Christophe Helary wrote:
> > On Sep 6, 2021, at 15:27, Jean-Christophe Helary <lists@traduction-libre.org> wrote:
> >>>>> On Sep 5, 2021, at 22:07, Alan Third <alan@idiocy.org> wrote:
> >>>> 
> >>>> Alan, thank you for your help, and sorry, it looks like the new
> >>>> config log is exactly the same as the other. I'm sending it to you
> >>>> offlist.
> >>> 
> >>> What is the result of
> >>> 
> >>> port installed active | grep '^ *gcc@<:@0-9@:>@* ' | awk '{ print $1; }'
> >> 
> >> the result is a blank line
> >> 
> >>> and
> >>> 
> >>> port contents $PORT_PACKAGE
> >>> 
> >>> replacing $PORT_PACKAGE with the result of the previous command (if
> >>> there is anything).
> >>> 
> >>> I'm wondering if the right thing to do here is to add --without-brew
> >>> and --without-macports, but then again, clearly something is going
> >>> wrong with the macports set up.
> >> 
> >> It's an old macports system that I keep upgrading/updating.
> >> 
> >> Do you think reinstalling from scratch could help ?
> > 
> > Alan,
> > 
> > Totally removing macports allowed me to properly run ./configure --with-native-compilation
> > I am currently "make"ing emacs.
> > 
> > There are some apps that I need from macport so I'll reinstall it from scratch.
> 
> Alan,
> 
> I confirm that reinstalling llvm through macports makes the issue
> appear again. So there is indeed a conflict between brew and
> macports here.

Installing llvm causes the problem?!

Lars, is there any chance you could have a look and see if you can
work out what's going on, here?
-- 
Alan Third