All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Freyther <holger+oe@freyther.de>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Latest qt4-sdk-tools* patch is wrong
Date: Wed, 06 Oct 2010 04:20:52 +0800	[thread overview]
Message-ID: <4CAB88A4.8000209@freyther.de> (raw)
In-Reply-To: <AANLkTinnQ75Ytjz+dhQxfsqFVsGNw4CJbTViNEZz=eAP@mail.gmail.com>

On 10/06/2010 04:13 AM, Dmitry Eremin-Solenikov wrote:

> 
> Prehistory: I'm building OE on the Debian lenny box with nearly no
> development packages
> installed (no X11 headers, etc.). qt4 configure script was trying to
> build xlib test.
> Compilation went OK (as there are X11 headers in the chroot). However
> during linkage,
> came a problem: xlib.o required libX11 which in turn required
> libxcb.so (with some symbols
> that were not available in the version in /usr/lib on my lenny) and
> libpthread-stubs.so.
> As configuration test did not pass rpath-link to gcc, linker failed to
> resolve libxcb.so from
> OE sysroot and thus failed link stage with undefined symbols.

> 
> I ain't sure that this description is very clear, but I hope this
> helps. At least I know for sure
> how to reproduce the problem.

Hi Dmitry,

I think you have figured out the root cause of why we were adding other libs
to the link line as well. In general this extra dependency is fixed when using
the -embedded option (or as someone pointed out... might be -no-x11 for stuff
< 4.7.). It would be good if your patch would contain this information itself.

thanks a lot

	z


PS: Your message does not seem to make it to the list, so I am not removing
parts of your email.



      reply	other threads:[~2010-10-05 20:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 14:01 Latest qt4-sdk-tools* patch is wrong Holger Freyther
2010-10-05 15:39 ` Dmitry Eremin-Solenikov
2010-10-05 15:47   ` Holger Freyther
2010-10-05 20:13     ` Dmitry Eremin-Solenikov
2010-10-05 20:20       ` Holger Freyther [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=4CAB88A4.8000209@freyther.de \
    --to=holger+oe@freyther.de \
    --cc=dbaryshkov@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.