unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: help-debbugs@gnu.org (GNU bug Tracking System)
To: bug-guile@gnu.org
Subject: bug#46220: closed (Re: bug#46220: Fwd: Some non-standard O_* flags are missing)
Date: Sat, 08 May 2021 10:06:02 +0000	[thread overview]
Message-ID: <handler.46220.D46220.162046834310704.notifdone@debbugs.gnu.org> (raw)
In-Reply-To: 308932c261a6f953a498606fb45cb35e08988af5.camel@telenet.be

[-- Attachment #1: Type: text/plain, Size: 411 bytes --]

Your bug report

#46220: Fwd: Some non-standard O_* flags are missing

which was filed against the guile package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 46220@debbugs.gnu.org.

-- 
46220: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=46220
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

[-- Attachment #2: Type: message/rfc822, Size: 3519 bytes --]

From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 46220-done@debbugs.gnu.org
Subject: Re: bug#46220: Fwd: Some non-standard O_* flags are missing
Date: Sat, 08 May 2021 12:05:32 +0200
Message-ID: <878s4pa6c3.fsf@gnu.org>

Hi Maxime,

Maxime Devos <maximedevos@telenet.be> skribis:

> From d769a75962c64804f354a0133494491626b8b2dc Mon Sep 17 00:00:00 2001
> From: Maxime Devos <maximedevos@telenet.be>
> Date: Tue, 2 Mar 2021 18:03:22 +0100
> Subject: [PATCH] Define `O_NOFOLLOW' and various other flags when supported.
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> * libguile/filesys.c (scm_init_filesys): Define ‘O_IGNORE_CTTY’,
>   ‘O_NOLINK’, ‘O_NOFOLLOW’, ‘O_PATH’, ‘O_TMPFILE’, ‘O_SHLOCK’,
>   ‘O_EXLOCK’, ‘O_ASYNC’, ‘O_NOATIME’, ‘O_DIRECTORY’, ‘O_CLOEXEC’
>   and ‘O_DIRECT’ when available.

Pushed as 553c82cee924f0bada27f8209c3bcb28be407953, followed with a NEWS
update.

Thanks!

Ludo’.


[-- Attachment #3: Type: message/rfc822, Size: 6248 bytes --]

[-- Attachment #3.1.1.1: Type: text/plain, Size: 124 bytes --]

Hi guilers,

I've accidentally sent the message to guile-devel instead
of bug-guile.  The bug report is forwarded here.

[-- Attachment #3.1.1.2: Forwarded message — Some non-standard O_* flags are missing --]
[-- Type: message/rfc822, Size: 1619 bytes --]

[-- Attachment #3.1.1.2.1.1: Type: text/plain, Size: 654 bytes --]

Hi guilers,

I noticed the following open flags are not defined:
O_NOFOLLOW, O_TMPFILE, O_IGNORE_CTTY, O_NOLINK,
O_SHLOCK, O_EXLOCK, O_ASYNC, O_NOATIME.

Some of these are Hurd-specific, Linux-specific
and BSD-specific.  I'm particularily interested
in O_NOFOLLOW, O_TMPFILE, O_IGNORE_CTTY, O_NOLINK
and O_NOATIME, the others don't matter for me,
though they may be useful for others.

Could extra O_* flags be exported to Guile (in libguile/filesys.c)
on systems where they are defined?

Greetings,
Maxime
-- 
Maxime Devos <maximedevos@telenet.be>
PGP Key: C1F3 3EE2 0C52 8FDB 7DD7  011F 49E3 EE22 1917 25EE
Freenode handle: mdevos

[-- Attachment #3.1.1.2.1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

[-- Attachment #3.1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2021-05-08 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <eee99a01c43dec23cd119f71b9a9758c7986aceb.camel@telenet.be>
2021-01-31 21:30 ` bug#46220: Fwd: Some non-standard O_* flags are missing Maxime Devos
2021-01-31 21:31   ` bug#46220: Acknowledgement (Fwd: Some non-standard O_* flags are missing) GNU bug Tracking System
2021-03-09 19:03   ` bug#46220: Fwd: Some non-standard O_* flags are missing Maxime Devos
2021-05-02 14:05     ` Ludovic Courtès
2021-05-08 10:05     ` Ludovic Courtès
2021-05-08 10:06   ` GNU bug Tracking System [this message]
2021-03-02 18:30 ` bug#46220: " Maxime Devos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=handler.46220.D46220.162046834310704.notifdone@debbugs.gnu.org \
    --to=help-debbugs@gnu.org \
    --cc=46220@debbugs.gnu.org \
    --cc=bug-guile@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).