bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, Ondrej Valousek <ondrej.valousek.xm@renesas.com>
Cc: kdudka@redhat.com
Subject: Re: [PATCH] Use xattr (Linux) in copy-acl.c
Date: Wed, 04 Jan 2023 12:27:57 +0100	[thread overview]
Message-ID: <3727963.L4jQFfv3LO@nimes> (raw)
In-Reply-To: <20230104100328.1215830-1-ondrej.valousek.xm@renesas.com>

Ondrej Valousek wrote:
> Hope it looks fine now.

This looks better indeed.

> +#ifdef USE_XATTR

Since USE_XATTR is always defined (to 0 or 1), you need to test it
with #if, not #ifdef.

> @@ -42,10 +56,29 @@ qcopy_acl (const char *src_name, int source_desc, const char *dst_name,
>    struct permission_context ctx;

This variable is only used in the #else case. To avoid compiler warnings
(I hope you always test with -Wall, right?) this variable declaration
should be moved into the #else block.

> +  AC_SUBST([LIB_XATTR])

I don't see any use of $(LIB_XATTR) so far. AFAICS, it ought to be
used
  - in the 'Link' section of modules/qcopy-acl,
  - in the 'Link' section of modules/acl, modules/copy-file, modules/qacl,
    modules/supersede — since these modules depend on qcopy-acl.
  - for the programs created in modules/acl-tests, modules/copy-file-tests,
    modules/supersede-tests.
Preferably each time right after $(LIB_ACL).
(One needs to lists the libraries explicitly, because you have no guarantee
that the distro uses shared libraries with implicit dependencies. It could
also be shared libraries without explicit dependencies, or static libraries.)

Bruno





  reply	other threads:[~2023-01-04 11:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 10:03 [PATCH] Use xattr (Linux) in copy-acl.c Ondrej Valousek
2023-01-04 11:27 ` Bruno Haible [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-03 14:08 Ondrej Valousek
2023-01-03 16:44 ` Bruno Haible
2023-01-03 20:40 ` Paul Eggert
2023-01-03 20:53   ` Bruno Haible

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://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=3727963.L4jQFfv3LO@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=kdudka@redhat.com \
    --cc=ondrej.valousek.xm@renesas.com \
    /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).