[Bug other/26966] linking of C++ app fail on OpenBSD 3.9 due POSIX threading unresolved symbols

kgardas at objectsecurity dot com gcc-bugzilla@gcc.gnu.org
Mon Apr 3 06:59:00 GMT 2006



------- Comment #8 from kgardas at objectsecurity dot com  2006-04-03 06:59 -------
Subject: Re:  linking of C++ app fail on OpenBSD 3.9 due
 POSIX threading unresolved symbols

> Now if this works, then we have a problem in libstdc++ check to enable weakref
> for some reason.

Could you be so kind and point me into direction where the check is made?
Anyway, greping thorough sources for "weakref" and thorough build 
directory I've found this (in build dir):

$ find . -name 'config*' -exec grep "weakref" \{} \; -print
configure:13473: checking assembler for .weakref
conftest.s:1: Error: unknown pseudo-op: `.weakref'
         .weakref foobar, barfnot
gcc_cv_as_weakref=no
./gcc/config.log
gcc_cv_as_weakref=${gcc_cv_as_weakref=no}
./gcc/config.cache
configure:13473: checking assembler for .weakref
conftest.s:1: Error: unknown pseudo-op: `.weakref'
         .weakref foobar, barfnot
gcc_cv_as_weakref=no
./prev-gcc/config.log
gcc_cv_as_weakref=${gcc_cv_as_weakref=no}
./prev-gcc/config.cache
configure:13473: checking assembler for .weakref
conftest.s:1: Error: unknown pseudo-op: `.weakref'
         .weakref foobar, barfnot
gcc_cv_as_weakref=no
./stage1-gcc/config.log
gcc_cv_as_weakref=${gcc_cv_as_weakref=no}
./stage1-gcc/config.cache
$

which seems to me .weakref is not supported by assembler. I've tried to 
syntetize back the test case and got this:

$ cat /tmp/weakref.s
         .weakref foobar, barfnot

$ as /tmp/weakref.s
/tmp/weakref.s: Assembler messages:
/tmp/weakref.s:1: Error: unknown pseudo-op: `.weakref'
$ as --version
GNU assembler 2.15
Copyright 2002 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License.  This program has absolutely no warranty.
This assembler was configured for a target of `i386-unknown-openbsd3.9'.
$

It's interesting it's working in gcc then...

Karel


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26966



More information about the Gcc-bugs mailing list