All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nayab Sayed via buildroot <buildroot@buildroot.org>
To: <buildroot@buildroot.org>
Subject: [Buildroot] [help] v4l2loopback package build fails for raspberrypi5
Date: Wed, 26 Mar 2025 14:09:48 +0000	[thread overview]
Message-ID: <37ad9e8d-bc5a-4e79-85e0-0128adfac465@microchip.com> (raw)

Hi there,

I am using latest source on master branch.

I am trying to build the v4l2loopback package after enabling the config 
BR2_PACKAGE_V4L2LOOPBACK_UTILS in menuconfig

    make O=raspberrypi5 raspberrypi5_defconfig

    make O=raspberrypi5 v4l2loopback

When installing to target, I see the following error:

    >>> v4l2loopback 0.13.2 Installing to target
    /usr/bin/install -D -m 0755
    /home/nayab/buildroot/raspberrypi5/build/v4l2loopback-0.13.2/utils/v4l2loopback-ctl
    /home/nayab/buildroot/raspberrypi5/target/usr/bin/v4l2loopback-ctl
    /usr/bin/install: cannot stat
    '/home/nayab/buildroot/raspberrypi5/build/v4l2loopback-0.13.2/utils/v4l2loopback-ctl':
    No such file or directory
    make[1]: *** [package/pkg-generic.mk:364:
    /home/nayab/buildroot/raspberrypi5/build/v4l2loopback-0.13.2/.stamp_target_installed]
    Error 1
    make: *** [Makefile:83: _all] Error 2

In 2025.02-LTS also, I see this behavior. Buildroot is unable to 
generate the file `v4l2loopback-ctl` in the 
build/v4l2loopback-0.13.2/utils/ directory.

But when I go the package build directory and execute `make`, I could 
see the file is generating.

Could somebody help fixing this issue?

Thanks,
Nayab

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2025-03-26 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 14:09 Nayab Sayed via buildroot [this message]
2025-03-27 16:51 ` [Buildroot] [help] v4l2loopback package build fails for raspberrypi5 Peter Seiderer via buildroot

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=37ad9e8d-bc5a-4e79-85e0-0128adfac465@microchip.com \
    --to=buildroot@buildroot.org \
    --cc=Nayabbasha.Sayed@microchip.com \
    /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.