From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yu Ke <ke.yu@intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] xserver: force to use libdl
Date: Sat, 28 May 2011 09:07:05 +0100 [thread overview]
Message-ID: <1306570025.27470.320.camel@rex> (raw)
In-Reply-To: <4DE07DE3.1090303@intel.com>
On Sat, 2011-05-28 at 12:45 +0800, Yu Ke wrote:
> The marco in question is in xorg-server-1.10.1/configure.ac
> "
> AC_CHECK_FUNC([dlopen], [],
> AC_CHECK_LIB([dl], [dlopen], DLOPEN_LIBS="-ldl"))
> AC_SUBST(DLOPEN_LIBS)
> "
>
> Ideally, the dlopen test should fail since dlopen is not available in
> libc, and then DLOPEN_LIBS="-ldl" is executed. In this case, the later
> build will correctly link libdl. qemux86 fall into this case.
>
> But in ppc case, the dlopen test unfortunately pass, and DLOPEN_LIBS
> become "", which caused later linker error of unresolved dlopen
> reference. but I did not yet understand why ppc is so special.
>
> For detail, I've attached two config.log, one for ppc, one for qemux86.
> in ppc,
> configure:15235: checking for dlopen
> configure:15235: result: yes
Thanks. If you look at config.log you'll see this near the top:
| #modphp
| ac_cv_c_bigendian_php=${ac_cv_c_bigendian_php=yes}
| ac_cv_sizeof_ptrdiff_t=${ac_cv_sizeof_ptrdiff_t=4}
| ac_cv_func_dlopen=${ac_cv_func_dlopen=yes}
| lt_cv_dlopen_self=${lt_cv_dlopen_self=yes}
and then if you look at the configure script for the xserver you'll see
${ac_cv_func_dlopen} being set to yes is likely triggering the bad
result.
These are coming from the powerpc site files:
richard@rex:poky/meta/site$ grep dlopen * -r
powerpc-common:ac_cv_func_dlopen=${ac_cv_func_dlopen=yes}
powerpc-common:lt_cv_dlopen_self=${lt_cv_dlopen_self=yes}
and I suspect if you remove those two lines, things will work a lot
better!
Only powerpc has the broken site file which is why only powerpc is
affected.
Cheers,
Richard
next prev parent reply other threads:[~2011-05-28 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 21:09 [PATCH 0/1] Fix for build failure of xserver on mpc build Saul Wold
2011-05-27 21:09 ` [PATCH 1/1] xserver: force to use libdl Saul Wold
2011-05-27 21:24 ` Phil Blundell
2011-05-27 22:23 ` Richard Purdie
2011-05-27 22:35 ` Koen Kooi
2011-05-30 7:35 ` Richard Purdie
2011-05-28 4:45 ` Yu Ke
2011-05-28 8:07 ` Richard Purdie [this message]
2011-05-30 6:10 ` Yu Ke
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=1306570025.27470.320.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=ke.yu@intel.com \
--cc=koen@dominion.thruhere.net \
--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