All of lore.kernel.org
 help / color / mirror / Atom feed
From: Si, Beibei <beibei.si@intel.com>
To: lkp@lists.01.org
Subject: [f2fs_io] 1531853eb7: make fail
Date: Wed, 12 May 2021 07:30:20 +0000	[thread overview]
Message-ID: <a4574a56ef3d46a3bcc5fdff40013a6b@intel.com> (raw)

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

Hi Robin,



We noticed a compiling issue due to commit 1531853eb7, and its parent 3bfcca8c81 has no such compiling issue, could you pls have a check?



Commit: 1531853eb72b335c488171dd0803e9c417de7e1f (“f2fs_io: Add get file name encryption mode”)
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git master

We followed steps in /f2fs-tools/README and the output was shown as below.



/f2fs-tools# ./autogen.sh

/f2fs-tools# ./configure

/f2fs-tools# make

...

f2fs_io.h:123:28: error: field 'v1' has incomplete type

   struct fscrypt_policy_v1 v1;

                            ^~

f2fs_io.c: In function 'do_get_filename_encrypt_mode':

f2fs_io.c:1141:7: error: 'FSCRYPT_POLICY_V1' undeclared (first use in this function); did you mean 'FSCRYPT_POLICY_V2'?

  case FSCRYPT_POLICY_V1:

       ^~~~~~~~~~~~~~~~~

       FSCRYPT_POLICY_V2

f2fs_io.c:1141:7: note: each undeclared identifier is reported only once for each function it appears in

make[3]: *** [Makefile:419: f2fs_io.o] Error 1

make[3]: Leaving directory '/tmp/lkp/xfstests/src/f2fs-tools/tools/f2fs_io'

make[2]: *** [Makefile:609: all-recursive] Error 1

make[2]: Leaving directory '/tmp/lkp/xfstests/src/f2fs-tools/tools'

make[1]: *** [Makefile:421: all-recursive] Error 1

make[1]: Leaving directory '/tmp/lkp/xfstests/src/f2fs-tools'

make: *** [Makefile:353: all] Error 2





Thanks,

Carel




[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 5117 bytes --]

             reply	other threads:[~2021-05-12  7:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12  7:30 Si, Beibei [this message]
2021-05-12 16:08 ` [f2fs_io] 1531853eb7: make fail Jaegeuk Kim

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=a4574a56ef3d46a3bcc5fdff40013a6b@intel.com \
    --to=beibei.si@intel.com \
    --cc=lkp@lists.01.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 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.