All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: poky@yoctoproject.org
Subject: Re: Problem populating rootfs with a binary only recipe
Date: Wed, 08 Jan 2014 17:11:10 +0100	[thread overview]
Message-ID: <52CD789E.7090201@message-id.googlemail.com> (raw)
In-Reply-To: <CAL-qi526ua3G0iyPqE+awLKNgiobftcswofZ2qHXMgCsX1-WRQ@mail.gmail.com>

Hi Scott,

Am 07.01.2014 20:17, schrieb Kroll, Scott:
> I have a recipe for NVIDIA display drivers written that simply fetches
> the drivers, compiles a kernel module, and populates some
> (unfortunately) binary only libraries. The RPMs created work just
> fine, but when generating the root filesystem, an issue crops up due
> to a "missing" dependency.
> 
> The drivers provide a libGL.so.325.15, which eventually becomes the
> symlinked libGL.so (at least in the -dev package). However, one of the
> required libraries in the NVIDIA package depends directly on libGL.so
> instead of libGL.so.325.15, so when the root filesystem population is
> to occur, the RPM refuses to install because no package provides
> libGL.so.

Maybe putting the libGL.so into the main package might already be enough?

You can achieve that by using

FILES_${PN}-dev = ""

(but then -dev is completely empty).

Another thing worth trying might be

PROVIDES += "libGL.so"

Good luck :-)

	Stefan
-- 
Stefan Seyfried
Linux Consultant & Developer -- GPG Key: 0x731B665B

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


      reply	other threads:[~2014-01-08 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 19:17 Problem populating rootfs with a binary only recipe Kroll, Scott
2014-01-08 16:11 ` Stefan Seyfried [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=52CD789E.7090201@message-id.googlemail.com \
    --to=stefan.seyfried@googlemail.com \
    --cc=poky@yoctoproject.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.