Re: Please help test the new v4l-subdev support in v4l2-compliance

[Mauro Carvalho Chehab <mchehab@s-opensource.com>]

Em Mon, 5 Feb 2018 18:01:34 +0100
Hans Verkuil <hverkuil@xs4all.nl> escreveu:

> On 02/05/2018 05:59 PM, Hans Verkuil wrote:
> > On 02/05/2018 05:55 PM, Mauro Carvalho Chehab wrote:  
> >> Em Mon, 5 Feb 2018 14:37:29 -0200
> >> Mauro Carvalho Chehab <mchehab@kernel.org> escreveu:
> >>  
> >>> Em Mon, 5 Feb 2018 08:21:54 -0800
> >>> Tim Harvey <tharvey@gateworks.com> escreveu:
> >>>  
> >>>> Hans,
> >>>>
> >>>> I'm failing compile (of master 4ee9911) with:
> >>>>
> >>>>   CXX      v4l2_compliance-media-info.o
> >>>> media-info.cpp: In function ‘media_type media_detect_type(const char*)’:
> >>>> media-info.cpp:79:39: error: no matching function for call to
> >>>> ‘std::basic_ifstream<char>::basic_ifstream(std::__cxx11::string&)’
> >>>>   std::ifstream uevent_file(uevent_path);
> >>>>                                        ^    
> >>>
> >>> Btw, while on it, a few days ago, I noticed several class warnings when
> >>> building v4l-utils on Raspbian, saying that it was using some features
> >>> that future versions of gcc would stop using at qv4l2. See enclosed.
> >>>
> >>> I didn't have time to look on them.  
> >>
> >> FYI, it still happens with today's upstream's version:
> >>
> >> 	4ee99116d0ec (HEAD, origin/master, origin/HEAD) v4l2-ctl: improve the fps calculation when streaming
> >>
> >> $ gcc --version
> >> gcc (Raspbian 6.3.0-18+rpi1) 6.3.0 20170516
> >> Copyright (C) 2016 Free Software Foundation, Inc.
> >> This is free software; see the source for copying conditions.  There is NO
> >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  
> > 
> > My guess is that it is a bogus message from gcc 6.
> > 
> > Regards,
> > 
> > 	Hans
> >   
> 
> See: https://gcc.gnu.org/ml/gcc/2017-05/msg00073.html
> 
> Nothing to worry about.

Hmm... as suggested there, it could be worth to add -Wno-psabi at qv4l2
Makefile if arch is arm[1], in order to avoid those warnings there.

[1] from what's said at https://gcc.gnu.org/gcc-7/changes.html, this is
due to a bug on gcc 5 for ARM.

> 
> 	Hans



Thanks,
Mauro