Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Jader H. Silva" <jader@2mi.com.br>
To: OpenEmbedded Dev List <openembedded-devel@lists.openembedded.org>
Subject: libxml2-native including system zlib
Date: Tue, 17 Mar 2009 15:24:00 -0300	[thread overview]
Message-ID: <1237314240.6587.84.camel@northpole> (raw)

Hello again.
I'm trying to build an i586 x11-image, but I cannot pass libxml2-native
do_compile task, it seems it includes the host libz.h.

Error:

| i686-linux-libtool: link: ccache gcc
-isystem/home/jader/oe/build/conf/tmp/staging/i686-linux/usr/include -O2
-pedantic -W -Wformat -Wunused -Wimplicit -Wreturn-type -Wswitch
-Wcomment -Wtrigraphs -Wformat -Wchar-subscripts -Wuninitialized
-Wparentheses -Wshadow -Wpointer-arith -Wcast-align -Wwrite-strings
-Waggregate-return -Wstrict-prototypes -Wmissing-prototypes
-Wnested-externs -Winline -Wredundant-decls -Wl,-rpath-link
-Wl,/home/jader/oe/build/conf/tmp/staging/i686-linux/usr/lib -Wl,-rpath
-Wl,/home/jader/oe/build/conf/tmp/staging/i686-linux/usr/lib -Wl,-O1
-o .libs/xmllint xmllint.o
-L/home/jader/oe/build/conf/tmp/staging/i686-linux/usr/lib ./.libs/libxml2.so -ldl /home/jader/oe/build/conf/tmp/staging/i686-linux/usr/lib/libz.so -lm -Wl,-rpath -Wl,/home/jader/oe/build/conf/tmp/staging/i686-linux/usr/lib
|
| ./.libs/libxml2.so: undefined reference to `gzopen64'
| collect2: ld returned 1 exit status
| make[2]: *** [xmllint] Error 1
| make[2]: *** Waiting for unfinished jobs....
| mv -f .deps/testapi.Tpo .deps/testapi.Po
| make[2]: Leaving directory
`/home/jader/oe/build/conf/tmp/work/i686-linux/libxml2-native-2.7.2-r0/libxml2-2.7.2'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory
`/home/jader/oe/build/conf/tmp/work/i686-linux/libxml2-native-2.7.2-r0/libxml2-2.7.2'
| make: *** [all] Error 2
| FATAL: oe_runmake failed





Found gzopen in libxmlIO.c. gzopen is defined as gzopen64
in /usr/include/zlib.h, also, if i run make CFLAGS+=--verbose, I get
(stripped):

ccache gcc -DHAVE_CONFIG_H -I. -I./include -I./include  -D_REENTRANT
-isystem/home/jader/oe/build/conf/tmp/staging/i686-linux/usr/include
-isystem/home/j
ader/oe/build/conf/tmp/staging/i686-linux/usr/include -O2 -pedantic -W
-Wformat -Wunused -Wimplicit -Wreturn-type -Wswitch -Wcomment
-Wtrigraphs -Wformat -Wc
har-subscripts -Wuninitialized -Wparentheses -Wshadow -Wpointer-arith
-Wcast-align -Wwrite-strings -Waggregate-return -Wstrict-prototypes
-Wmissing-prototype
s -Wnested-externs -Winline -Wredundant-decls -MT xmlIO.o -MD -MP
-MF .deps/xmlIO.Tpo -c -o xmlIO.o xmlIO.c


[...]
gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu3)
 /usr/lib/gcc/i486-linux-gnu/4.2.4/cc1 -E -quiet -v -I. -I./include
-I./include -MD xmlIO.d -MF .deps/xmlIO.Tpo -MP -MT xmlIO.o
-isystem /usr/include -DHAVE_CONFIG_H -D_REENTRANT
-isystem/home/jader/oe/build/conf/tmp/staging/i686-linux/usr/include
xmlIO.c -mtune=generic
[...]
#include "..." search starts here:
#include <...> search starts here:
 .
 ./include
 /usr/include
 /home/jader/oe/build/conf/tmp/staging/i686-linux/usr/include
 /usr/local/include
 /usr/lib/gcc/i486-linux-gnu/4.2.4/include
End of search list.
Reading specs from /usr/lib/gcc/i486-linux-gnu/4.2.4/specs
Target: i486-linux-gnu






-isystem /usr/include is set on cc1, so it invalidate include
path /home/jader/oe/build/conf/tmp/staging/i686-linux/usr/include (where
zlib.h is).



Is it correct for Makefile to use my system GCC ?
Can anybody help me to compile it correctly?


Thanks in advance


Jader H. Silva
jader@2mi.com.br
Depto. de desenvolvimento
2MI Tecnologia









             reply	other threads:[~2009-03-17 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 18:24 Jader H. Silva [this message]
2009-03-17 19:34 ` libxml2-native including system zlib Jader H. Silva
2009-03-17 19:35 ` Jader H. Silva

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=1237314240.6587.84.camel@northpole \
    --to=jader@2mi.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