Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: libx11 1.2 problems (dolt vs. libtool)
Date: Fri, 29 May 2009 10:22:00 +0200	[thread overview]
Message-ID: <gvo5v8$1ef$1@ger.gmane.org> (raw)
In-Reply-To: <4A1F82D2.6020707@bolloretelecom.eu>

On 29-05-09 08:38, Jeremy Lainé wrote:
> Since libx11 was upgraded to 1.2, my libx11 builds are failing with:
>
> | ../../../doltlibtool: line 17:
> /home/oebuilder/oe/build/tmp/work/ppce300c3-angstrom-linux/libx11-1_1.2-r0/libX11-1.2/modules/im/ximcp/../../../libtool:
> No such file or directory
> | ../../../doltlibtool: line 17: exec:
> /home/oebuilder/oe/build/tmp/work/ppce300c3-angstrom-linux/libx11-1_1.2-r0/libX11-1.2/modules/im/ximcp/../../../libtool:
> cannot execute: No suchfile or directory
>
> It would seem I am not the only one with this problem:
>
> http://tinderbox.openembedded.net/packages/libx11/
>
> The problem is that the "dolibtool" script (see http://dolt.freedesktop.org) is trying to
> invoke the "libtool" script which it assumes lives in the base directory. However in OE
> the libtool script is called ${HOST_SYS}-libtool, so it is not being found.
>
> For now I am working around the problem with the following patch, but I suspect this is
> going to crop up in other packages sooner or later:

Powerpc is in the dolt whitelist (upstream, not OE), we already see this 
problem with webkit, and solve it in the exact same way.

regards,

Koen




  reply	other threads:[~2009-05-29  8:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29  6:38 libx11 1.2 problems (dolt vs. libtool) Jeremy Lainé
2009-05-29  8:22 ` Koen Kooi [this message]
2009-05-29 16:47   ` Otavio Salvador
2009-05-29 21:52 ` Mario Domenech Goulart

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='gvo5v8$1ef$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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