Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Mario Domenech Goulart <mario@ossystems.com.br>
To: openembedded-devel@lists.openembedded.org
Subject: Re: libx11 1.2 problems (dolt vs. libtool)
Date: Fri, 29 May 2009 18:52:07 -0300	[thread overview]
Message-ID: <87octbk260.fsf@ossystems.com.br> (raw)
In-Reply-To: <4A1F82D2.6020707@bolloretelecom.eu> ("Jeremy Lainé"'s message of "Fri, 29 May 2009 08:38:10 +0200")

[-- Attachment #1: Type: text/plain, Size: 2199 bytes --]

Hi folks

On Fri, 29 May 2009 08:38:10 +0200 Jeremy Lainé <jeremy.laine@bolloretelecom.eu> 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.

That's the behavior we observed here too.


> 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:
>
> diff --git a/recipes/xorg-lib/libx11_1.2.bb b/recipes/xorg-lib/libx11_1.2.bb
> index a3d000f..8415315 100644
> --- a/recipes/xorg-lib/libx11_1.2.bb
> +++ b/recipes/xorg-lib/libx11_1.2.bb
> @@ -13,6 +13,10 @@ SRC_URI += "file://x11_disable_makekeys.patch;patch=1 \
>
>  EXTRA_OECONF += "--without-xcb --with-keysymdef=${STAGING_INCDIR}/X11/keysymdef.h"
>
> +do_configure_append() {
> +       ln -s ${HOST_SYS}-libtool libtool
> +}
> +
>  do_compile() {
>         (
>                 unset CC LD CXX CCLD CFLAGS CPPFLAGS LDFLAGS CXXFLAGS

As Otavio mentioned, we faced this problem here, but our approach to
solve it was a little different (in terms of implementation).  We
actually fixed the acinclude.m4 file (the patch is attached).

I guess the right thing to do is to patch dolt.m4
(http://cgit.freedesktop.org/dolt/ -- from where libx11's and xserver's
acinclude.m4 are generated, I suppose).  We are working on a patch for
it (the fix is basically the same as for acinclude.m4).

Best wishes.
Mario

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: acinclude.m4.patch --]
[-- Type: text/x-diff, Size: 676 bytes --]

--- libX11-1.2/acinclude.m4.orig	2009-05-29 16:45:39.000000000 -0300
+++ libX11-1.2/acinclude.m4	2009-05-29 18:29:56.000000000 -0300
@@ -213,10 +213,16 @@
 if $modeok && $tagok ; then
     . ${top_builddir_slash}doltcompile "${args@<:@@@:>@}"
 else
-    exec ${top_builddir_slash}libtool "$[]@"
-fi
 __DOLTLIBTOOL__EOF__
 
+maybe_hyphen=
+if ! test x$host_alias = x; then
+    maybe_hyphen="-"
+fi
+
+echo '    exec ${top_builddir_slash}'${host_alias}${maybe_hyphen}'libtool "$[]@"' >>doltlibtool
+echo 'fi' >>doltlibtool
+
 dnl Done writing out doltlibtool; substitute it for libtool.
     chmod +x doltlibtool
     LIBTOOL='$(top_builddir)/doltlibtool'

      parent reply	other threads:[~2009-05-29 22:00 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
2009-05-29 16:47   ` Otavio Salvador
2009-05-29 21:52 ` Mario Domenech Goulart [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=87octbk260.fsf@ossystems.com.br \
    --to=mario@ossystems.com.br \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox