emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Merging feature/android


From: Eli Zaretskii
Subject: Re: Merging feature/android
Date: Tue, 07 Mar 2023 15:36:14 +0200

> From: Po Lu <luangruo@yahoo.com>
> Cc: arsen@aarsen.me,  eggert@cs.ucla.edu,  emacs-devel@gnu.org
> Date: Tue, 07 Mar 2023 21:03:06 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Po Lu <luangruo@yahoo.com>
> >> Cc: arsen@aarsen.me,  eggert@cs.ucla.edu,  emacs-devel@gnu.org
> >> Date: Tue, 07 Mar 2023 08:36:16 +0800
> >> 
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >> 
> >> >> > Once again, let's please make this work like configure does with image
> >> >> > libraries, i.e. error out by default if modules aren't supported, and
> >> >> > suggest using ifavailable.  This will solve the problem cleanly and in
> >> >> > a way that cannot be missed by chance.
> >> >> 
> >> >> How about only on GNU/Linux systems, and maybe Mac OS and Windows?
> >> >
> >> > I don't understand what you propose, in practical terms.
> >> 
> >> Basically, to only default to the error when opsys is set to systems
> >> which use GCC.
> >
> > Why the distinction? what bad things will happen if we do this for any
> > compiler?
> 
> Emacs will not install by just running:
> 
>       ./configure
>       make
>       su
>       make install
> 
> from the distribution.

We are going in circles: as I already said before, Emacs will also not
install by just running the above if, say, the XPM library is not
available.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]