Tatsuya Kinoshita writes:
> On 2023-02-20 at 20:22 +0000, Andrea Corallo wrote:
>> I've installed 5d0b45cd67b on emacs-29 in order to use always
>> `make-temp-file'.
>
> Please be careful with the difference between make-temp-file-internal
> and make-temp-file.
>
>&
Eli Zaretskii writes:
>> From: Andrea Corallo
>> Cc: monn...@iro.umontreal.ca, t...@debian.org, emacs-de...@gnu.org,
>> spwhit...@spwhitton.name, 1021...@bugs.debian.org
>> Date: Mon, 20 Feb 2023 15:42:08 +
>>
>> > You mean, from master to emac
Stefan Monnier writes:
>> Before e6043641d30 the file was created by Fmake_temp_file_internal and
>> afterwards overwritten by libgccjit.
>
> Yes, that was good.
>
>> So I guess one could remove the file after the first creation and make
>> it a link pointing to some other file waiting for
Stefan Monnier writes:
>>> `make-temp-name` uses `O_EXCL | O_CREAT` so as to close the race
>>> condition: if someone predicated the filename, we detect it atomically
>>> and we try again.
>>>
>>> You might like to check
>>>
>>>
>>>
Eli Zaretskii writes:
>> From: Andrea Corallo
>> Cc: Tatsuya Kinoshita , emacs-de...@gnu.org,
>> spwhit...@spwhitton.name, 1021...@bugs.debian.org, Eli Zaretskii
>>
>> Date: Mon, 20 Feb 2023 09:03:34 +
>>
>> OTOH on a slightly differn
Andrea Corallo writes:
> Stefan Monnier writes:
>
>>> Shouldn't make-temp-file-internal return a non predictable file name?
>>
>> Nope. It's less predictable but it's still predictable.
>>
>>> Otherwise what's the point of using make-temp-file in
Stefan Monnier writes:
>> Shouldn't make-temp-file-internal return a non predictable file name?
>
> Nope. It's less predictable but it's still predictable.
>
>> Otherwise what's the point of using make-temp-file in the first place if
>> the temporary name is predictable?
>
> `make-temp-name`
Tatsuya Kinoshita writes:
> On 2023-02-17 at 09:42 -0700, Sean Whitton wrote:
>> So: commit ce4a066ed1e fixes Debian bug #1021842 without the env var.
>
> On 2023-02-14 at 11:32 +, Andrea Corallo wrote:
>> Stefan Monnier writes:
>> > `temporary-file-directory'
Eli Zaretskii writes:
>> From: Andrea Corallo
>> Cc: Vincent Lefevre , spwhit...@spwhitton.name,
>> 58...@debbugs.gnu.org, 1017...@bugs.debian.org
>> Date: Thu, 03 Nov 2022 21:25:08 +
>>
>> AFAIU the Emacs subprocess we use to compile s
Eli Zaretskii writes:
>> Date: Thu, 3 Nov 2022 11:13:08 +0100
>> From: Vincent Lefevre
>> Cc: spwhit...@spwhitton.name, 58...@debbugs.gnu.org,
>> 1017...@bugs.debian.org
>>
>> On 2022-11-03 08:47:06 +0200, Eli Zaretskii wrote:
>> > > On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote:
>> >
Stefan Monnier writes:
> Russ Allbery [2022-08-19 11:42:30] wrote:
>> The 28.1 version of emacs-lucid fails on startup with a cryptic error
>> message:
>>
>> % emacs
>> Cannot find suitable directory for output in ‘comp-native-load-path’.
>>
>> Running emacs -q allows it to start, but it still
I experience the same on i386.
Running under valgrind I get an "Invalid read of size 4". I have
installed libgccjit-10-dev/testing,now 10-20200324-1 i386
Compiling from the vanilla repositiory is working fine for me.
Andrea
--
a...@sdf.org
12 matches
Mail list logo
