[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Merging feature/android
From: |
Po Lu |
Subject: |
Re: Merging feature/android |
Date: |
Sat, 04 Mar 2023 08:07:27 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Po Lu <luangruo@yahoo.com>
>> Cc: emacs-devel@gnu.org, eggert@cs.ucla.edu
>> Date: Fri, 03 Mar 2023 21:28:27 +0800
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > So why shouldn't it be the same with modules? Don't we want the user
>> > to be aware that modules support will be absent?
>>
>> No, I don't think so: that would amount to making Emacs not build
>> by default without a recent GCC.
>
> We had this in emacs-module.c for a long time, including two major
> releases. How come it was never a problem until now?
I don't know, but it doesn't surprise me, since most people use GCC.
- Re: Merging feature/android, (continued)
- Re: Merging feature/android, Po Lu, 2023/03/02
- Re: Merging feature/android, Eli Zaretskii, 2023/03/02
- Re: Merging feature/android, Po Lu, 2023/03/02
- Re: Merging feature/android, Eli Zaretskii, 2023/03/03
- Re: Merging feature/android, Po Lu, 2023/03/03
- Re: Merging feature/android, Eli Zaretskii, 2023/03/03
- Re: Merging feature/android, Po Lu, 2023/03/03
- Re: Merging feature/android, Eli Zaretskii, 2023/03/03
- Re: Merging feature/android, Po Lu, 2023/03/03
- Re: Merging feature/android, Eli Zaretskii, 2023/03/03
- Re: Merging feature/android,
Po Lu <=
- Re: Merging feature/android, Eli Zaretskii, 2023/03/04
- Re: Merging feature/android, Po Lu, 2023/03/04
- Re: Merging feature/android, Eli Zaretskii, 2023/03/04
- Re: Merging feature/android, Po Lu, 2023/03/04
- Re: Merging feature/android, Eli Zaretskii, 2023/03/04
- Re: Merging feature/android, Po Lu, 2023/03/04
- Re: Merging feature/android, Paul Eggert, 2023/03/04
- Re: Merging feature/android, Po Lu, 2023/03/04
- Re: Merging feature/android, Paul Eggert, 2023/03/05
- Re: Merging feature/android, Po Lu, 2023/03/05