Re: building GNOME 2.11 on x86_64 using jhbuild
- From: Pat Suwalski <pat suwalski net>
- To: Jeroen Zwartepoorte <jeroen zwartepoorte gmail com>
- Cc: desktop-devel-list gnome org
- Subject: Re: building GNOME 2.11 on x86_64 using jhbuild
- Date: Mon, 13 Jun 2005 22:24:10 -0400
Jeroen Zwartepoorte wrote:
> Hi,
>
> In the last couple of days i've built gnome-2.11 using jhbuild about
> 10 times so far. It builds fine (uncovered some gcc4-related bugs,
> filed them and they're fixed; apply a hal patch to n-c-b etc.). This
> is on a Fedora system, with up-to-date packages from rawhide.
>
> However, after it has finished building and you look at which
> libraries the binaries are linked to, most of them are linked to
> /usr/lib64 libraries instead of /home/jeroen/Gnome/built/lib64. I've
> tried *lots* of things, but nothing helped. LD_LIBRARY_PATH is
> pointing to /home/jeroen/Gnome/built/lib64. I even went as far as to
> strace gnome-about and it *doesn't even look* in
> /home/jeroen/Gnome/built/lib64:
I was hoping to test your theory this evening, but I can't get very far
in the build, which dies at gtk because of:
./.libs/libgtk-x11-2.0.so: undefined reference to
`g_utf8_collate_key_for_filename'
Anyway, using the libraries that had already been built, Gentoo ldd
reports that they're all linked to libraries in my build target:
pat fx /opt/g212/lib64 $ ls /opt/g212/
bin etc include lib64 man share
pat fx /opt/g212/lib64 $ ldd /opt/g212/lib64/libatk-1.0.so
libgobject-2.0.so.0 => /opt/g212/lib64/libgobject-2.0.so.0
(0x00002aaaaabcb000)
libgmodule-2.0.so.0 => /opt/g212/lib64/libgmodule-2.0.so.0
(0x00002aaaaad0b000)
libdl.so.2 => /lib/libdl.so.2 (0x00002aaaaae24000)
libglib-2.0.so.0 => /opt/g212/lib64/libglib-2.0.so.0
(0x00002aaaaaf27000)
libc.so.6 => /lib/libc.so.6 (0x00002aaaab0b2000)
/lib64/ld-linux-x86-64.so.2 (0x0000555555555000)
pat fx /opt/g212/lib64 $
Is this different than what you have?
--Pat
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]