All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: pango-native build problem (and solution idea)
Date: Mon, 8 Oct 2012 07:01:53 -0700	[thread overview]
Message-ID: <CAMKF1soS0oBnwSUGVcJ1csgNGFdjPLY9qxW0-sZMr52TB=wOxw@mail.gmail.com> (raw)
In-Reply-To: <5072847C.7@dresearch-fe.de>

On Mon, Oct 8, 2012 at 12:45 AM, Steffen Sledz <sledz@dresearch-fe.de> wrote:
> After upgrading my build host to openSUSE 12.2 i hit a build problem with pango-native (from oe-classic).
>

heh keeping the build going with newer distros is going to be a
challange with time.

> It seems that the libXrender version at the build host now misses the _XGetRequest symbol.
>
> Would it be an acceptable solution to add libxrender-native to DEPENDS_virtclass-native?
>

seems ok to me.

> Regards,
> Steffen
>
> --
> DResearch Fahrzeugelektronik GmbH
> Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
> Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
> Fax: +49 30 515932-299
> Geschäftsführer: Dr. Michael Weber, Werner Mögle;
> Amtsgericht Berlin Charlottenburg; HRB 130120 B;
> Ust.-IDNr. DE273952058
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  reply	other threads:[~2012-10-08 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08  7:45 pango-native build problem (and solution idea) Steffen Sledz
2012-10-08 14:01 ` Khem Raj [this message]
2012-10-09  8:49   ` [2011.03-maintenance 0/1] pull request 20121009 Steffen Sledz
2012-10-09  8:49     ` [2011.03-maintenance 1/1] pango-native: add libxrender-native to dependencies Steffen Sledz
2012-10-09 14:42     ` [2011.03-maintenance 0/1] pull request 20121009 Tom Rini
2012-10-10  6:41       ` Steffen Sledz
2012-10-10 14:55         ` Tom Rini

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='CAMKF1soS0oBnwSUGVcJ1csgNGFdjPLY9qxW0-sZMr52TB=wOxw@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@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 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.