Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] libusb compile error
Date: Tue, 04 Sep 2007 17:32:37 +0100	[thread overview]
Message-ID: <46DD88A5.5070708@carallon.com> (raw)

Hello,

I am trying to get libusb to compile with my i686 buildroot target.

When I run the compile it fails with this error:

/bin/sh ../libtool --mode=link
/home/willw/buildroot/build_i686/staging_dir/usr/bin/i686-linux-uclibc-g++
-Os -pipe  -I/home/willw/buildroot/build_i686/staging_dir/usr/include
-I/home/willw/buildroot/build_i686/staging_dir/include
--sysroot=/home/willw/buildroot/build_i686/staging_dir/ -isysroot
/home/willw/buildroot/build_i686/staging_dir -mtune=i686 -march=i686  -g
-O2   -o descriptor_test  descriptor_test.o ../libusbpp.la
libtool: link: warning: library
`/home/willw/buildroot/build_i686/staging_dir/usr/bin/../lib/gcc/i686-linux-uclibc/4.2.1/../../../../i686-linux-uclibc/lib/libstdc++.la' 

was moved.
/home/willw/buildroot/build_i686/staging_dir/usr/bin/i686-linux-uclibc-g++
-Os -pipe -I/home/willw/buildroot/build_i686/staging_dir/usr/include
-I/home/willw/buildroot/build_i686/staging_dir/include
--sysroot=/home/willw/buildroot/build_i686/staging_dir/ -isysroot
/home/willw/buildroot/build_i686/staging_dir -mtune=i686 -march=i686 -g
-O2 -o .libs/descriptor_test descriptor_test.o  ../.libs/libusbpp.so
-L/home/willw/buildroot/toolchain_build_i686/gcc-4.2.1-final/i686-linux-uclibc/libstdc++-v3/src 

-L/home/willw/buildroot/toolchain_build_i686/gcc-4.2.1-final/i686-linux-uclibc/libstdc++-v3/src/.libs 

-L/home/willw/buildroot/toolchain_build_i686/gcc-4.2.1-final/./gcc
-L/home/willw/buildroot/build_i686/staging_dir/lib
-L/home/willw/buildroot/build_i686/staging_dir/usr/lib -Wl,--rpath
-Wl,//lib -Wl,--rpath
-Wl,/home/willw/buildroot/build_i686/staging_dir/usr/bin/../lib/gcc/i686-linux-uclibc/4.2.1/../../../../i686-linux-uclibc/lib
/home/willw/buildroot/build_i686/staging_dir/usr/bin/../lib/gcc/i686-linux-uclibc/4.2.1/../../../../i686-linux-uclibc/bin/ld: 

warning: libc.so.6, needed by //lib/libusb-0.1.so.4, may conflict with
libc.so.0
/home/willw/buildroot/build_i686/staging_dir/usr/bin/../lib/gcc/i686-linux-uclibc/4.2.1/../../../../i686-linux-uclibc/bin/ld: 

errno: TLS definition in //lib/libc.so.6 section .tbss mismatches
non-TLS definition in
/home/willw/buildroot/build_i686/staging_dir//lib/libc.so.0 section .bss
//lib/libc.so.6: could not read symbols: Bad value
collect2: ld returned 1 exit status


Can anyone suggest what is wrong?

Thanks,

Will.
-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Senior Project Engineer                  Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

             reply	other threads:[~2007-09-04 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-04 16:32 Will Wagner [this message]
2007-09-04 19:08 ` [Buildroot] libusb compile error Will Wagner
2007-09-05 12:23   ` [Buildroot] [PATCH] " Will Wagner

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=46DD88A5.5070708@carallon.com \
    --to=will_wagner@carallon.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox