Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ml@communistcode.co.uk
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Nothing provides libxcb-*
Date: Fri, 14 Sep 2012 14:22:19 +0100	[thread overview]
Message-ID: <1347628939.13596.10.camel@ted> (raw)
In-Reply-To: <505324E3.9090701@communistcode.co.uk>

On Fri, 2012-09-14 at 13:36 +0100, Jack Mitchell wrote:
> On 14/09/12 13:32, Jack Mitchell wrote:
> > On 14/09/12 13:16, Richard Purdie wrote:
> >> On Fri, 2012-09-14 at 13:09 +0100, Jack Mitchell wrote:
> >>> I am trying to use the package libxcb-xfixes in a recipe however when I
> >>> add 'libxcb-xfixes' to DEPENDS I get the error that nothing provides
> >>> libxcb-xfixes however the libxcb package clearly has it in the PACKAGES
> >>> variable
> >>>
> >>> recipes-graphics/xcb/libxcb.inc:PACKAGES =+ "libxcb-composite
> >>> libxcb-damage libxcb-dpms libxcb-glx \
> >>> recipes-graphics/xcb/libxcb.inc: libxcb-randr libxcb-record
> >>> libxcb-render libxcb-res \
> >>> recipes-graphics/xcb/libxcb.inc: libxcb-screensaver libxcb-shape
> >>> libxcb-shm libxcb-sync \
> >>> recipes-graphics/xcb/libxcb.inc: libxcb-xevie libxcb-xf86dri
> >>> libxcb-xfixes libxcb-xlib \
> >>> recipes-graphics/xcb/libxcb.inc: libxcb-xprint libxcb-xtest libxcb-xv
> >>> libxcb-xvmc \
> >>> recipes-graphics/xcb/libxcb.inc: libxcb-dri2"
> >>>
> >>> I have also tried using others in this package list to no avail, can
> >>> anybody comment on how I should be using these packages?
> >> You're mixing up the build time and runtime namespaces. You would add
> >> DEPENDS = "libxcb" or RDEPENDS_${PN}-xxx = "libxcb-xfixes".
> >>
> >> DEPENDS is build time and you use PN
> >>
> >> RDEPENDS/RRECOMMENDS/R* is runtime and values from PACKAGES
> >>
> >> Cheers,
> >>
> >> Richard
> >>
> >
> > Ok, thanks! I guess I have a bigger problem then, the error I am 
> > recieving is:
> >
> > | DEBUG: Executing shell function autotools_preconfigure
> > | DEBUG: Shell function autotools_preconfigure finished
> > | DEBUG: Executing shell function do_configure
> > | ERROR: Xfixes not found
> > |
> > | If you think configure made a mistake, make sure you are using the 
> > latest
> > | version from Git.  If the latest version fails, report the problem 
> > to the
> > | libav-user@libav.org mailing list or IRC #libav on irc.freenode.net.
> > | Include the log file "config.log" produced by configure as this will 
> > help
> > | solving the problem.
> >
> >
> > Now, I have libxcb in DEPENDS and I have the following configure options:
> >
> > EXTRA_OECONF = " \
> >         --cross-prefix=${TARGET_PREFIX} \
> >         --enable-cross-compile \
> >         --sysroot="${STAGING_DIR_TARGET}" \
> >         --sysinclude="${STAGING_DIR_TARGET}${includedir}" \
> >         --target-os="linux" \
> >         --extra-cflags="${TARGET_CFLAGS} 
> > ${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS}" \
> >         --extra-ldflags="${TARGET_LDFLAGS}" \
> >         --arch=${TARGET_ARCH} \
> >         --enable-hardcoded-tables \
> >         --enable-shared \
> >         --enable-pthreads \
> >         --enable-gpl \
> >         --enable-avfilter \
> >         --prefix=${prefix} \
> >         --enable-x11grab \
> >         --enable-libtheora  \
> >         --enable-libvorbis \
> >         ${EXTRA_FFCONF} \
> > "
> >
> > Is there anything glaringly wrong?I am worried about these two:
> >
> >         --sysroot="${STAGING_DIR_TARGET}" \
> >         --sysinclude="${STAGING_DIR_TARGET}${includedir}" \
> >
> > Cheers,
> >
> 
> Possibly of use?
> 
> check_lib X11/extensions/Xfixes.h XFixesGetCursorImage -lXfixes
> check_header X11/extensions/Xfixes.h
> check_cpp
> BEGIN /tmp/ffconf.RboCj6pF.c
>      1 #include <X11/extensions/Xfixes.h>
>      2 int x;
> END /tmp/ffconf.RboCj6pF.c
> arm-poky-linux-gnueabi-gcc 
> --sysroot=/home/jack/Projects/poky-rasp/raspberry/tmp/sysroots/raspberrypi 
> -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
> -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -O2 -pipe -g 
> -feliminate-unused-debug-types -O2 -pipe -g 
> -feliminate-unused-debug-types -march=armv6 -mthumb-interwork 
> -mfloat-abi=softfp -mtune=arm1176jzf-s 
> --sysroot=/home/jack/Projects/poky-rasp/raspberry/tmp/sysroots/raspberrypi 
> -std=c99 -fomit-frame-pointer -marm -pthread -E -o 
> /tmp/ffconf.IQTkUVuf.o /tmp/ffconf.RboCj6pF.c
> /tmp/ffconf.RboCj6pF.c:1:35: fatal error: X11/extensions/Xfixes.h: No 
> such file or directory
> compilation terminated.
> ERROR: Xfixes not found

Sorry, I misunderstood this, ignore my last reply. That header comes
from libxfixes so you probably need a DEPENDS on that too.

Cheers,

Richard




  parent reply	other threads:[~2012-09-14 13:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 12:09 Nothing provides libxcb-* Jack Mitchell
2012-09-14 12:12 ` Burton, Ross
2012-09-14 12:16 ` Richard Purdie
2012-09-14 12:32   ` Jack Mitchell
2012-09-14 12:36     ` Jack Mitchell
2012-09-14 13:01       ` Jack Mitchell
2012-09-14 13:19         ` Richard Purdie
2012-09-14 13:22       ` Richard Purdie [this message]
2012-09-14 13:28         ` Jack Mitchell

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=1347628939.13596.10.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=ml@communistcode.co.uk \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox