All of lore.kernel.org
 help / color / mirror / Atom feed
From: JS <js@hipro.co.in>
To: buildroot@busybox.net
Subject: [Buildroot] To fix the build failure of xlib_liblbxutil, xlib_libX11, xlib_libXt
Date: Wed, 05 Mar 2008 14:19:45 +0530	[thread overview]
Message-ID: <1204706985.6596.3.camel@localhost> (raw)
In-Reply-To: <20080305030255.GA2436@codepoet.org>


On Tue, 2008-03-04 at 20:02 -0700, Erik Andersen wrote:
> Thanks for your work trying to get X11r7 working in buildroot.

Thanks for replying. I started to think that I was missing something
very obvious ;)

> This does seem to be an improvement; however, there still seems
> to be some problems.  At least for me I am getting "-L/usr/lib"
> in the build, which then pulls the wrong libraries..
> 
> (cd /home/andersen/SVN/buildroot/build_i586/xlib_libX11-1.1.1/src; /bin/bash ../libtool  --tag=CC --mode=relink /home/andersen/SVN/buildroot/build_i586/staging_dir/usr/bin/i586-linux-uclibc-gcc -Os -pipe -I/home/andersen/SVN/buildroot/build_i586/staging_dir/usr/include -I/home/andersen/SVN/buildroot/build_i586/staging_dir/include --sysroot=/home/andersen/SVN/buildroot/build_i586/staging_dir/ -isysroot /home/andersen/SVN/buildroot/build_i586/staging_dir -mtune=i586 -march=i586 -I../include -I../include/X11 -I../include -I../include/X11 -I../src/xcms -I../src/xkb -I../src/xlibi18n -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -D_BSD_SOURCE -DHAS_FCHOWN -DHAS_STICKY_DIR_BIT -I/home/andersen/SVN/buildroot/build_i586/staging_dir/usr/include -I/home/andersen/SVN/buildroot/build_i586/staging_dir/usr/include -I/home/andersen/SVN/buildroot/build_i586/staging_dir/usr/include -I/home/andersen/SVN/buildroot/build_i586/staging_dir/usr/include -D_BSD_SOURCE -DX11_t -DTRANS_CLIENT -g -O2 -version-info 1:0:0 -no-undefined -o libX11-xcb.la -rpath /usr/lib x11_xcb.lo libX11.la -ldl -inst-prefix-dir /home/andersen/SVN/buildroot/project_build_i586/uclibc/root)
> /home/andersen/SVN/buildroot/build_i586/staging_dir/usr/bin/i586-linux-uclibc-gcc -Os -pipe  -I/home/andersen/SVN/buildroot/build_i586/staging_dir/usr/include -I/home/andersen/SVN/buildroot/build_i586/staging_dir/include --sysroot=/home/andersen/SVN/buildroot/build_i586/staging_dir/ -isysroot /home/andersen/SVN/buildroot/build_i586/staging_dir -mtune=i586 -march=i586 -shared  .libs/x11_xcb.o  -L/home/andersen/SVN/buildroot/project_build_i586/uclibc/root/usr/lib -L/usr/lib -lX11 -L/home/andersen/SVN/buildroot/build_i586/staging_dir/usr/lib -ldl  -mtune=i586 -march=i586 -Wl,-soname -Wl,libX11-xcb.so.1 -o .libs/libX11-xcb.so.1.0.0
> /usr/lib/libdl.so: file not recognized: File format not recognized
> collect2: ld returned 1 exit status

This doesnt seem to happen for me (on mipsel). I am currently stuck at
another issue that I filed a bug on (Bug:0002424), which happens much
later. I mean after x11 gets built, in gdk-pixbuf.

-- 
HiPro Solutions
http://hipro.co.in/

      reply	other threads:[~2008-03-05  8:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04  6:20 [Buildroot] To fix the build failure of xlib_liblbxutil, xlib_libX11, xlib_libXt JS
2008-03-05  3:02 ` Erik Andersen
2008-03-05  8:49   ` JS [this message]

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=1204706985.6596.3.camel@localhost \
    --to=js@hipro.co.in \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.