unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Brendan Tildesley <mail@brendan.scot>
To: 40190@debbugs.gnu.org
Subject: [bug#40190] v4l2loopback module builds with 5.4 but not 5.6
Date: Mon, 6 Apr 2020 20:38:06 +1000	[thread overview]
Message-ID: <e1125357-568a-18a7-7277-a489714b4deb@brendan.scot> (raw)
In-Reply-To: <53a0dc74-0cf2-2e08-a2b0-fb6de0260080@brendan.scot>

I just made a package definition for v4l2loopback. It built perfectly 
fine with Linux 5.4, but when i switched to 5.6.2 with the patch that 
sets it to default, suddenly I get this error below. I was wondering if 
anyone can tell if this is likely my fault, a guix bug with 5.6, or an 
upstream bug I should report there? Thanks.

In linux.scm:

(define-public v4l2loopback
   (package
        (name "v4l2loopback")
        (version "0.12.3")
        (source (origin
                  (method url-fetch)
                  (uri (string-append
"https://github.com/umlaeute/v4l2loopback/archive/v"
                        version".tar.gz"))
                  (file-name (string-append name "-" version))
                  (sha256
                   (base32
"1fkhxxj9i5d25ak7afkph1jp47d9bcngs9kwapgwhpl6h15v2srz"))))
        (build-system linux-module-build-system)
        (arguments
         `(#:tests? #f))
        (home-page "https://github.com/umlaeute/v4l2loopback")
        (synopsis "Create V4L2 loopback devices")
        (description "")
        (license license:gpl2)))

Error:


make: Entering directory 
'/gnu/store/swjg0hczahmhjph3na8czrwf5lzgp1z0-linux-libre-module-builder-5.6.2/lib/modules/build'
   AR 
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/built-in.a
   CC [M] 
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.o
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c:137:47: 
warning: 'struct timeval' declared inside parameter list will not be 
visible outside of this definition or declaration
  static inline void v4l2l_get_timestamp(struct timeval *tv) {
                                                ^~~~~~~
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c: 
In function 'v4l2l_get_timestamp':
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c:147:4: 
error: dereferencing pointer to incomplete type 'struct timeval'
   tv->tv_sec = (time_t)ts.tv_sec;
     ^~
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c:147:16: 
error: 'time_t' undeclared (first use in this function); did you mean 
'ktime_t'?
   tv->tv_sec = (time_t)ts.tv_sec;
                 ^~~~~~
                 ktime_t
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c:147:16: 
note: each undeclared identifier is reported only once for each function 
it appears in
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c:147:23: 
error: expected ';' before 'ts'
   tv->tv_sec = (time_t)ts.tv_sec;
                        ^~
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c: 
In function 'vidioc_qbuf':
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c:1523:24: 
error: passing argument 1 of 'v4l2l_get_timestamp' from incompatible 
pointer type [-Werror=incompatible-pointer-types]
     v4l2l_get_timestamp(&b->buffer.timestamp);
                         ^
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c:137:20: 
note: expected 'struct timeval *' but argument is of type 'struct 
__kernel_v4l2_timeval *'
  static inline void v4l2l_get_timestamp(struct timeval *tv) {
                     ^~~~~~~~~~~~~~~~~~~
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c: 
In function 'v4l2_loopback_write':
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c:1950:22: 
error: passing argument 1 of 'v4l2l_get_timestamp' from incompatible 
pointer type [-Werror=incompatible-pointer-types]
   v4l2l_get_timestamp(&b->timestamp);
                       ^
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c:137:20: 
note: expected 'struct timeval *' but argument is of type 'struct 
__kernel_v4l2_timeval *'
  static inline void v4l2l_get_timestamp(struct timeval *tv) {
                     ^~~~~~~~~~~~~~~~~~~
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c: 
In function 'init_buffers':
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c:2055:23: 
error: passing argument 1 of 'v4l2l_get_timestamp' from incompatible 
pointer type [-Werror=incompatible-pointer-types]
    v4l2l_get_timestamp(&b->timestamp);
                        ^
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.c:137:20: 
note: expected 'struct timeval *' but argument is of type 'struct 
__kernel_v4l2_timeval *'
  static inline void v4l2l_get_timestamp(struct timeval *tv) {
                     ^~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:268: 
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3/v4l2loopback.o] 
Error 1
make: *** [Makefile:1683: 
/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3] Error 2
make: Leaving directory 
'/gnu/store/swjg0hczahmhjph3na8czrwf5lzgp1z0-linux-libre-module-builder-5.6.2/lib/modules/build'
command "make" "-C" 
"/gnu/store/swjg0hczahmhjph3na8czrwf5lzgp1z0-linux-libre-module-builder-5.6.2/lib/modules/build" 
"M=/tmp/guix-build-v4l2loopback-0.12.3.drv-0/v4l2loopback-0.12.3" failed 
with status 2
builder for 
`/gnu/store/6zj7agvr4f4yy1121k5i3zc76bkgkzay-v4l2loopback-0.12.3.drv' 
failed with exit code 1
build of 
/gnu/store/6zj7agvr4f4yy1121k5i3zc76bkgkzay-v4l2loopback-0.12.3.drv failed

  reply	other threads:[~2020-04-06 10:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87k13gqhrw.fsf@ponder>
     [not found] ` <87sgi0le3g.fsf@ponder>
2020-03-23  4:08   ` [bug#40190] Linux-Libre 5.5.x Vagrant Cascadian
2020-03-30 17:32     ` Vagrant Cascadian
2020-03-30 17:34       ` Vagrant Cascadian
2020-03-31  0:10         ` [bug#40190] Linux-Libre 5.6 Vagrant Cascadian
2020-03-31 14:30           ` Marius Bakke
2020-03-31 17:44             ` Vagrant Cascadian
2020-03-31 18:35               ` Guillaume Le Vaillant
2020-04-03 23:28               ` Vagrant Cascadian
2020-04-03 23:29                 ` Vagrant Cascadian
2020-04-16 19:37                   ` Vagrant Cascadian
2020-04-17 19:26                     ` Mark H Weaver
2020-06-08 20:46                       ` [bug#40190] Linux-Libre 5.7 Vagrant Cascadian
2020-06-09  2:43                       ` [bug#40190] Linux-Libre 5.6 Leo Famulari
2020-04-06  4:12     ` [bug#40190] Works for me Brendan Tildesley
2020-04-06 10:38       ` Brendan Tildesley [this message]
2020-04-06 10:46         ` [bug#40190] v4l2loopback module builds with 5.4 but not 5.6 Danny Milosavljevic
2020-04-06 11:01         ` Tobias Geerinckx-Rice via Guix-patches via
2020-08-05 21:29     ` bug#40190: Linux-Libre 5.5.x Leo Famulari

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=e1125357-568a-18a7-7277-a489714b4deb@brendan.scot \
    --to=mail@brendan.scot \
    --cc=40190@debbugs.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 public inbox

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

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).