public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "knrstaj at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15648] multiple definition of `__lll_lock_wait_private'
Date: Fri, 21 Jun 2013 01:33:00 -0000	[thread overview]
Message-ID: <bug-15648-131-OrPcYQjhV5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15648-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15648

--- Comment #14 from Neil <knrstaj at gmail dot com> ---
Created attachment 7088
  --> http://sourceware.org/bugzilla/attachment.cgi?id=7088&action=edit
link error message

I add -v and -Wl,--verbose.
There are more information.
Please see the attachment file.

Following is linking information.

gcc -ftree-parallelize-loops=2 -flto -O1 -save-temps *.o -static -o
coremark.exe -v -Wl,--verbose
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.6/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
4.6.3-1ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.6 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object
--enable-plugin --enable-objc-gc --enable-targets=all --disable-werror
--with-arch-32=i686 --with-tune=generic --enable-checking=release
--build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu
Thread model: posix
gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
COMPILER_PATH=/usr/lib/gcc/i686-linux-gnu/4.6/:/usr/lib/gcc/i686-linux-gnu/4.6/:/usr/lib/gcc/i686-linux-gnu/:/usr/lib/gcc/i686-linux-gnu/4.6/:/usr/lib/gcc/i686-linux-gnu/
LIBRARY_PATH=/usr/lib/gcc/i686-linux-gnu/4.6/:/usr/lib/gcc/i686-linux-gnu/4.6/../../../i386-linux-gnu/:/usr/lib/gcc/i686-linux-gnu/4.6/../../../../lib/:/lib/i386-linux-gnu/:/lib/../lib/:/usr/lib/i386-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/i686-linux-gnu/4.6/../../../:/lib/:/usr/lib/
Reading specs from /usr/lib/gcc/i686-linux-gnu/4.6/libgomp.spec
COLLECT_GCC_OPTIONS='-ftree-parallelize-loops=2' '-flto' '-O1' '-save-temps'
'-static' '-o' 'coremark.exe' '-v' '-mtune=generic' '-march=i686' '-pthread'
 /usr/lib/gcc/i686-linux-gnu/4.6/collect2 -plugin
/usr/lib/gcc/i686-linux-gnu/4.6/liblto_plugin.so
-plugin-opt=/usr/lib/gcc/i686-linux-gnu/4.6/lto-wrapper
-plugin-opt=-fresolution=--verbose.res -plugin-opt=-pass-through=-lgcc
-plugin-opt=-pass-through=-lgcc_eh -plugin-opt=-pass-through=-lpthread
-plugin-opt=-pass-through=-lc -flto --sysroot=/ --build-id --no-add-needed
--as-needed -m elf_i386 --hash-style=gnu -static -z relro -o coremark.exe
/usr/lib/gcc/i686-linux-gnu/4.6/../../../i386-linux-gnu/crt1.o
/usr/lib/gcc/i686-linux-gnu/4.6/../../../i386-linux-gnu/crti.o
/usr/lib/gcc/i686-linux-gnu/4.6/crtbeginT.o -L/usr/lib/gcc/i686-linux-gnu/4.6
-L/usr/lib/gcc/i686-linux-gnu/4.6/../../../i386-linux-gnu
-L/usr/lib/gcc/i686-linux-gnu/4.6/../../../../lib -L/lib/i386-linux-gnu
-L/lib/../lib -L/usr/lib/i386-linux-gnu -L/usr/lib/../lib
-L/usr/lib/gcc/i686-linux-gnu/4.6/../../.. core_list_join.o core_main.o
coremark.exe.ltrans0.o core_matrix.o core_portme.o core_state.o core_util.o
--verbose -lgomp -lrt --start-group -lgcc -lgcc_eh -lpthread -lc --end-group
/usr/lib/gcc/i686-linux-gnu/4.6/crtend.o
/usr/lib/gcc/i686-linux-gnu/4.6/../../../i386-linux-gnu/crtn.o

Hope this will help you.
Thanks,
Neil

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-06-21  1:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 10:15 [Bug libc/15648] New: " knrstaj at gmail dot com
2013-06-19 15:01 ` [Bug libc/15648] " carlos at redhat dot com
2013-06-20  2:47 ` knrstaj at gmail dot com
2013-06-20  2:54 ` knrstaj at gmail dot com
2013-06-20  3:32 ` [Bug libc/15648] Support building glibc with -flto carlos at redhat dot com
2013-06-20  3:34 ` carlos at redhat dot com
2013-06-20  6:10 ` knrstaj at gmail dot com
2013-06-20  8:15 ` [Bug libc/15648] multiple definition of `__lll_lock_wait_private' schwab@linux-m68k.org
2013-06-20  9:24 ` knrstaj at gmail dot com
2013-06-20 12:55 ` carlos at redhat dot com
2013-06-20 12:57 ` carlos at redhat dot com
2013-06-20 12:58 ` jakub at redhat dot com
2013-06-20 13:52 ` carlos at redhat dot com
2013-06-21  1:22 ` knrstaj at gmail dot com
2013-06-21  1:33 ` knrstaj at gmail dot com [this message]
2013-06-21  7:42 ` schwab@linux-m68k.org
2013-06-21  7:52 ` jakub at redhat dot com
2013-06-21 13:13 ` carlos at redhat dot com
2013-06-21 13:21 ` carlos at redhat dot com
2013-06-21 14:42 ` knrstaj at gmail dot com
2013-10-02 17:05 ` neleai at seznam dot cz
2013-10-03  1:00 ` carlos at redhat dot com
2014-02-07  3:04 ` [Bug nptl/15648] " jsm28 at gcc dot gnu.org
2014-06-13 15:03 ` fweimer at redhat dot com
2021-02-23  8:32 ` fweimer at redhat dot com

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=bug-15648-131-OrPcYQjhV5@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).