All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rosenberg <steven.rosenberg@devalore.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: STK1160 USB VIDEO CAPTURE DRIVER kconfig compatibility issues
Date: Wed, 18 May 2022 16:29:42 +0300	[thread overview]
Message-ID: <CACBf5_X4iUpHBagxFao_E4Z_jaM8i6Bb-h1bkXFzhoTPLVdpHw@mail.gmail.com> (raw)
In-Reply-To: <CACBf5_UoTap2gtHbkRfX6cSza5rHcKZY_HSfzzGV7g+UBMiGNA@mail.gmail.com>

Resending in plain text:

---------- Forwarded message ----------
From: Steven Rosenberg <steven.rosenberg@devalore.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: linux-media <linux-media@vger.kernel.org>
Bcc:
Date: Wed, 18 May 2022 16:17:07 +0300
Subject: Re: STK1160 USB VIDEO CAPTURE DRIVER kconfig compatibility issues
Dear Ezequiel,

Thank you for your response. Yes, your patch seemed to work.
Unfortunately, we cannot upgrade the package, there are too many
version specific dependencies. Currently we are getting another error
on the gcc version:

poky-hardknott-25.0.5/build/tmp/work-shared/dcbullet/kernel-source/include/linux/compiler-gcc.h:106:1:
fatal error: linux/compiler-gcc10.h: No such file or directory
|   106 | #include gcc_header(__GNUC__)
|       | ^~~~~
| compilation terminated.

There were no errors using Yocto sumo which used gcc version 7.3, but
hardknott uses gcc 10.3. Attempting to set the preferred version in
yocto after adding sumo's gcc 7.3 to the environment did not help.

Maybe you have some idea on how to set the __GNUC__ define for version
7 or some other way to have the linux kernel use gcc 7.3 instead of
the gcc 10.3?

Thank you again for your help, time and consideration.

With Best Regards.

Steven.


On Wed, May 18, 2022 at 4:17 PM Steven Rosenberg
<steven.rosenberg@devalore.com> wrote:
>
> Dear Ezequiel,
>
> Thank you for your response. Yes, your patch seemed to work. Unfortunately, we cannot upgrade the package, there are too many version specific dependencies. Currently we are getting another error on the gcc version:
>
> poky-hardknott-25.0.5/build/tmp/work-shared/dcbullet/kernel-source/include/linux/compiler-gcc.h:106:1: fatal error: linux/compiler-gcc10.h: No such file or directory
> |   106 | #include gcc_header(__GNUC__)
> |       | ^~~~~
> | compilation terminated.
>
> There were no errors using Yocto sumo which used gcc version 7.3, but hardknott uses gcc 10.3. Attempting to set the preferred version in yocto after adding sumo's gcc 7.3 to the environment did not help.
>
> Maybe you have some idea on how to set the __GNUC__ define for version 7 or some other way to have the linux kernel use gcc 7.3 instead of the gcc 10.3?
>
> Thank you again for your help, time and consideration.
>
> With Best Regards.
>
> Steven.
>
>
>
> On Tue, May 17, 2022 at 9:45 PM Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> wrote:
>>
>> Hi Steven,
>>
>> I think your mail didn't get delivered because it's HTML and mailing
>> list filter this. Plain-text is required.
>>
>> El mar, 17 may 2022 a la(s) 10:10, Steven Rosenberg
>> (steven.rosenberg@devalore.com) escribió:
>> >
>> > Dear Ezequiel Garcia,
>> >
>> >
>> >
>> > We are using the linux 3.10.73 package [1], which includes your "drivers/media/usb/stk1160/ Kconfig" file. We are upgrading versions of Yocto and the current version of kconfiglib.py gives errors [2]. There is indeed an extra dot on line 20. Perhaps you have already fixed this in a later version  of this linux package so that we can avoid adding a patch? If so or if you have another solution, please advise accordingly. Currently your Kconfig file for this version of Linux is not compatible with the current version of  kconfiglib.
>>
>> Thanks for the report. The extra dot was apparently introduced by
>> commit "[media] rename most media/video usb drivers to media/usb",
>> and later fixed in commit "[media] stk1160: Build as a module if SND
>> is m and audio support is selected".
>> See: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dfb9f94e8e5e7f73c8e2bcb7d4fb1de57e7c333d
>>
>> 3.10 is EOLed so you will have to patch this yourself.
>>
>> PS: If you still want to use 3.10, I would suggest you should be using
>> 3.10.108 (latest stable).
>>
>> Thanks,
>> Ez
>>
>>
>>
>> >
>> >
>> >
>> >
>> >
>> >
>> > [1] https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.10.73.tar.xz
>> >
>> > [2]
>> >
>> >
>> > kconfiglib.KconfigError: drivers/media/usb/stk1160/Kconfig:20: error: couldn't parse '.': unknown token at start of line
>> >
>> > ERROR: config analysis failed:
>> >
>> > DEBUG: Python function do_kernel_configcheck finished
>> >
>> >
>> > With Best Regards.
>> >
>> >
>> > Steven Rosenberg.
>>
>>
>>
>> --
>> Ezequiel García, VanguardiaSur
>> www.vanguardiasur.com.ar

      parent reply	other threads:[~2022-05-18 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACBf5_XDzBAAPwx9wn-p-moLyWGzx5o_cnFKPqZuS7puvZbmGg@mail.gmail.com>
2022-05-17 18:45 ` STK1160 USB VIDEO CAPTURE DRIVER kconfig compatibility issues Ezequiel Garcia
     [not found]   ` <CACBf5_UoTap2gtHbkRfX6cSza5rHcKZY_HSfzzGV7g+UBMiGNA@mail.gmail.com>
2022-05-18 13:29     ` Steven Rosenberg [this message]

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=CACBf5_X4iUpHBagxFao_E4Z_jaM8i6Bb-h1bkXFzhoTPLVdpHw@mail.gmail.com \
    --to=steven.rosenberg@devalore.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=linux-media@vger.kernel.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.