<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 12/12/2012 04:48 PM, ChenQi wrote:
<blockquote cite="mid:50C844E0.2080904@windriver.com" type="cite">On
12/11/2012 09:59 AM, Saul Wold wrote:
<br>
<blockquote type="cite">On 12/10/2012 05:07 PM, Andreas Müller
wrote:
<br>
<blockquote type="cite">On Mon, Dec 10, 2012 at 10:44 PM, Saul
Wold <a class="moz-txt-link-rfc2396E" href="mailto:sgw@linux.intel.com"><sgw@linux.intel.com></a> wrote:
<br>
<blockquote type="cite">On 12/10/2012 08:48 AM, Saul Wold
wrote:
<br>
<blockquote type="cite">
<br>
On 12/04/2012 12:46 AM, <a class="moz-txt-link-abbreviated" href="mailto:Qi.Chen@windriver.com">Qi.Chen@windriver.com</a> wrote:
<br>
<blockquote type="cite">
<br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<SNIP>
<br>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite"> "
<br>
SRC_URI = "${BASE_SRC_URI} \
<br>
<a class="moz-txt-link-freetext" href="file://noldlibpath.patch">file://noldlibpath.patch</a> \
<br>
@@ -28,6 +29,12 @@ inherit autotools pkgconfig binconfig
<br>
do_configure() {
<br>
libtoolize --force
<br>
gnu-configize --force
<br>
+ if [ "${PN}" != "icu-native" ]; then
<br>
+ OLD=`pwd`
<br>
+ cd ${S}
<br>
+ autoconf
<br>
+ cd ${OLD}
<br>
+ fi
<br>
</blockquote>
</blockquote>
<br>
<br>
I had some time this morning to investigate this more
deeply. What I found
<br>
was that the ICU tarball was being delivered with a
"configure" and that the
<br>
do_configure was avoiding the "autoconf" conversion of
configure.in ->
<br>
configure. I am not sure if this is historical or if this
is truly needed.
<br>
<br>
So by doing the autoconf above you changed the "configure"
script, this in
<br>
turn caused some configuration changes to occur in the
platform.h file. Why
<br>
these changed (particularly the U_HAVE_NAMESPACE define)
then caused the ICU
<br>
libraries to be built with different namespace.
<br>
<br>
So a couple of key questions that need to be resolved:
<br>
1) Will updating to 4.6 solve this issue, if not then we
need to dive into 2
<br>
+ 3 Below:
<br>
<br>
2) Why does icu tarball have a generated configure?
<br>
<br>
3) Why does the autoconf generated configure fail to
configure things
<br>
correctly?
<br>
<br>
Sau!
<br>
<br>
</blockquote>
Also got this error but reported it to the wrong mailing list
- sorry.
<br>
I also looked around for this. The patch added pkg-config to
icu. Just
<br>
a guess: webkit-gtk fails due to a mixture of renamed symbols
<br>
(EventListener_3_6 - see
sysroot/usr/include/unicode/urename.h) and
<br>
unrenamed symbols. Before the icu-patch this did not happen
because
<br>
(icu's) urename.h was not included and no symbols were renamed
or
<br>
renamed differently. My problem: The error gives me
information about
<br>
renamed symbol but I did not yet find the time to search for
<br>
unrenamed. As I said: Just a guess
<br>
<br>
</blockquote>
I am not sure that's it, the renaming is actually in the
NAMESPACE, the older (no pkg-config) sets HAVE_NAMESPACE in the
platform.h file and then the symbols have icu_2_6 in them,
that's the real issue, which is caused by running autoconf and
getting a bad/wrong "configure" script vs the one suplied in the
tarball.
<br>
<br>
Sau!
<br>
<br>
<blockquote type="cite">Andreas
<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
Hi Saul,
<br>
<br>
The errors are:
<br>
configure.in:219: error: possibly undefined macro:
AC_CHECK_STRICT_COMPILE
<br>
If this token and others are legitimate, please use
m4_pattern_allow.
<br>
See the Autoconf documentation.
<br>
configure.in:222: error: possibly undefined macro:
AC_CHECK_64BIT_LIBS
<br>
configure.in:492: error: possibly undefined macro:
AC_SEARCH_LIBS_FIRST
<br>
<br>
</blockquote>
<br>
Ah.... I see the problem. Our autoconf version is 2.69 while this
configure.ac file needs 2.68.<br>
<blockquote cite="mid:50C844E0.2080904@windriver.com" type="cite">The
recipe's in attachment.
<br>
<br>
I first tried it on my own computer without yocto, everything's
OK. The autoconf-generated configure is the same with the shipped
one. So I figured maybe we don't need to override the do_configure
and do_compile method here.
<br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Openembedded-core mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a>
<a class="moz-txt-link-freetext" href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a>
</pre>
</blockquote>
<br>
</body>
</html>