[Bug 203759] [NEW PORT] devel/llfuse: Python bindings for the low-level FUSE API

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Oct 15 10:46:50 UTC 2015


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203759

--- Comment #4 from Niklaas Baudet von Gersdorff <niklaas at kulturflatrate.net> ---
Created attachment 162063
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162063&action=edit
Output of `poudriere testport`with 4 warnings

`poudriere testport` looks fine but it generates 4 warnings. I don't know
python at all. Shall I forward the issues to the maintainer upstream?

---

cc -DNDEBUG -O2 -pipe -fstack-protector -fno-strict-aliasing -fPIC
-I/usr/local/include/python3.4m -c src/llfuse/capi.c -o
build/temp.freebsd-10.1-RELEASE-p22-amd64-3.4/src/llfuse/capi.o
-I/usr/local/include/fuse -D_FILE_OFFSET_BITS=64 -DFUSE_USE_VERSION=28 -Wall
-Wextra -Wconversion -Wno-sign-conversion -DLLFUSE_VERSION="0.41.1"
-Wno-unused-but-set-variable -Wno-maybe-uninitialized
-DHAVE_STRUCT_STAT_ST_ATIMESPEC
warning: unknown warning option '-Wno-unused-but-set-variable'; did you mean
'-Wno-unused-const-variable'? [-Wunknown-warning-option]
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
In file included from src/llfuse/capi.c:13:
src/llfuse/capi_freebsd.c:22911:23: warning: implicit conversion loses integer
precision: 'ssize_t' (aka 'long') to 'int' [-Wshorten-64-to-32]
        __pyx_v_ret = extattr_set_file(__pyx_v_cpath, __pyx_v_cnamespace,
__pyx_v_cname, __pyx_v_cvalue, __pyx_v_len_);
                    ~
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/llfuse/capi_freebsd.c:23423:37: warning: comparison of integers of
different signs: 'Py_ssize_t' (aka 'long') and 'size_t' (aka 'unsigned long')
[-Wsign-compare]
          __pyx_t_3 = ((__pyx_v_ret == __pyx_v_bufsize) != 0);
                        ~~~~~~~~~~~ ^  ~~~~~~~~~~~~~~~
4 warnings generated.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-python mailing list