From: Enrico Castro <castroenrico@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: qt4-tools-native_4.4.3.bb failed
Date: Wed, 01 Apr 2009 11:34:31 +0200 [thread overview]
Message-ID: <49D33527.6050102@gmail.com> (raw)
> Could you please post that log?
http://lists.linuxtogo.org/pipermail/openembedded-devel/attachments/20090401/62fe5532/attachment.asc
> Enrico,
>
> It looks like g++ is not picking up libz from native staging:
>
> g++ -fno-exceptions -Wl,-rpath,/home/enrico/oe/tmp/staging/i686-linux/usr/lib
> -Wl,-rpath,/home/enrico/oe/tmp/staging/i686-linux/usr/lib -o ../../../bin/uic
> [snip]
> .obj/release-static-emb-x86/qfsfileengine_iterator_unix.o -lz -ldl
> /usr/bin/ld: cannot find -lz
>
> This is very odd as qt4-tools-native DEPENDS on zlib-native, so libz should be available.
> Could you please post the output of:
>
> ls -l /home/enrico/oe/tmp/staging/i686-linux/usr/lib/libz.*
>
> Cheers,
> --
> Jeremy LAINE
> Bolloré telecom | 11bis, rue Scribe | F-75009 Paris
>
The output is:
-rw-r--r-- 1 enrico enrico 78752 2009-03-27 12:36 /home/enrico/oe/tmp/staging/i686-linux/usr/lib/libz.a
-rwxr-xr-x 1 enrico enrico 978 2009-03-27 12:36 /home/enrico/oe/tmp/staging/i686-linux/usr/lib/libz.la
lrwxrwxrwx 1 enrico enrico 13 2009-03-27 12:36
/home/enrico/oe/tmp/staging/i686-linux/usr/lib/libz.so -> libz.so.1.2.3
lrwxrwxrwx 1 enrico enrico 13 2009-03-27 12:36
/home/enrico/oe/tmp/staging/i686-linux/usr/lib/libz.so.1 -> libz.so.1.2.3
-rwxr-xr-x 1 enrico enrico 79084 2009-03-27 12:36
/home/enrico/oe/tmp/staging/i686-linux/usr/lib/libz.so.1.2.3
Regards
Enrico
next reply other threads:[~2009-04-01 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 9:34 Enrico Castro [this message]
2009-04-02 7:54 ` qt4-tools-native_4.4.3.bb failed Jeremy Lainé
2009-04-02 18:00 ` Enrico Castro
-- strict thread matches above, loose matches on Subject: below --
2009-04-01 8:13 Enrico Castro
2009-04-01 8:29 ` Koen Kooi
2009-04-01 8:37 ` Jeremy Lainé
2009-04-01 8:47 ` Jeremy Lainé
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=49D33527.6050102@gmail.com \
--to=castroenrico@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox