all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Garlick <pgarlick@tourbillion-technology.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 39727@debbugs.gnu.org
Subject: bug#39727: statx error running 'guix gc' on CentOS 7
Date: Mon, 24 Feb 2020 12:52:42 +0000	[thread overview]
Message-ID: <da3144c34f55171b7f4e92564997469a88da9c53.camel@tourbillion-technology.com> (raw)
In-Reply-To: <87sgj3ze3y.fsf@gnu.org>

Hi Ludo,

> This was during the “removing unused link” phase, right?
> 
Yes, that's it.

> The system is running CentOS 7:
> 
> $ cat /etc/centos-release
> CentOS Linux release 7.7.1908 (Core)
> 
> What does “uname -r” return?

3.10.0-1062.12.1.el7.x86_64

> Let me know how it goes!

I compiled a C program with the following code using gcc-toolchain
9.2.0:

#define _GNU_SOURCE
#include <stdio.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <unistd.h>
#include <fcntl.h>

int main(void)
{
  struct statx st;
  if (statx(AT_FDCWD, "/",
            AT_SYMLINK_NOFOLLOW | AT_STATX_DONT_SYNC,
            /* AT_SYMLINK_NOFOLLOW, */
            STATX_SIZE | STATX_NLINK, &st) == -1)
    printf ("failed: %m\n");

  return 0;
}

Initially, with the AT_STATX_DONT_SYNC flag, the output is:

$ failed: Invalid argument

Then, without the  AT_STATX_DONT_SYNC flag, the program runs and there
is no output.

Best regards,

Paul.

  reply	other threads:[~2020-02-24 12:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 22:49 bug#39727: statx error running 'guix gc' on CentOS 7 Paul Garlick
2020-02-21 23:59 ` Ludovic Courtès
2020-02-24 12:52   ` Paul Garlick [this message]
2020-02-24 15:12     ` Ludovic Courtès
2020-02-24 19:51       ` Paul Garlick
2020-02-26 21:07         ` Ludovic Courtès

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

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

  git send-email \
    --in-reply-to=da3144c34f55171b7f4e92564997469a88da9c53.camel@tourbillion-technology.com \
    --to=pgarlick@tourbillion-technology.com \
    --cc=39727@debbugs.gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.