Summary: | random packages fail with Error:unknown pseudo-op: '.weakref' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Walter-Martin <delphinewaltermartin> |
Component: | [OLD] Library | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | VERIFIED INVALID | ||
Severity: | normal | CC: | adeel_n, charlesx, daemon, prikolov314, s0m2, tukachinchila |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
test.verbose.log
test.S test.ii test.ii.dd test.log test.verbose.log test.ii test.ii.dd test.S |
Description
Walter-Martin
2007-01-03 09:08:20 UTC
"include this in your bug report" doesn't mean "put this in summary and nothing more" what is your problem? {standard input}:4433: Error:unknown pseudo-op: '.weakref' {standard input}:4434: Error:unknown pseudo-op: '.weakref' {standard input}:4435: Error:unknown pseudo-op: '.weakref' make: *** [cxx_db.lo]Error 1 !!! Error: sys-libs/db-4.2.52-p4-r2 failed. call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile db-4.2.52_p4-r2.ebuild, line 103: Called die !!!!make failed !!!! if you need support ... !!! When you file a bug report, please include the following information: GENTOO_VM=blackdown-jdk-1.4.2 CLASSPATH="" JAVA_HOME="opt/blackdown-jdk-1.4.2.03" JAVACFLAGS="-source 1.4 -target 1.4" COMPILER="" I made an emerge -e system and i had this error. Before I made emerge -uD gqview but I did not remember that the option "~X86" was in my make.conf (I am a beginner). Thanks! . Kindly post a couple more than those 3 lines without any context whatsoever. Thanks. I hope it's help. localhost dwm # emerge sys-libs/db >> toto.txt configure: WARNING: I have to compile Test.class from scratch configure: WARNING: O_DIRECT interface ignored on linux-gnu-pc. In file included from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/backward/iostream.h:31, from ./db_cxx.h:59, from ../dist/../cxx/cxx_db.cpp:17: /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <iostream> instead of the deprecated header <iostream.h>. To disable this warning use -Wno-deprecated. {standard input}: Assembler messages: {standard input}:4422: Error: unknown pseudo-op: `.weakref' {standard input}:4423: Error: unknown pseudo-op: `.weakref' {standard input}:4424: Error: unknown pseudo-op: `.weakref' {standard input}:4425: Error: unknown pseudo-op: `.weakref' {standard input}:4426: Error: unknown pseudo-op: `.weakref' {standard input}:4427: Error: unknown pseudo-op: `.weakref' {standard input}:4428: Error: unknown pseudo-op: `.weakref' {standard input}:4429: Error: unknown pseudo-op: `.weakref' {standard input}:4430: Error: unknown pseudo-op: `.weakref' {standard input}:4431: Error: unknown pseudo-op: `.weakref' {standard input}:4432: Error: unknown pseudo-op: `.weakref' {standard input}:4433: Error: unknown pseudo-op: `.weakref' {standard input}:4434: Error: unknown pseudo-op: `.weakref' {standard input}:4435: Error: unknown pseudo-op: `.weakref' make: *** [cxx_db.lo] Error 1 !!! ERROR: sys-libs/db-4.2.52_p4-r2 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile db-4.2.52_p4-r2.ebuild, line 103: Called die !!! make failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! When you file a bug report, please include the following information: GENTOO_VM=blackdown-jdk-1.4.2 CLASSPATH="" JAVA_HOME="/opt/blackdown-jdk-1.4.2.03" JAVACFLAGS="-source 1.4 -target 1.4" COMPILER="" and of course, the output of emerge --info ---------------------------------------------------------------------- java-config-1 --list -available-vms The following JDKs are available for generation-1: *) Blackdown JDK 1.4.2.03 [blackdown-jdk-1.4.2.03] java-config-2 -L The following VMs are available for generation-2: 1) Blackdown JDK 1.4.2.03 [blackdown-jdk-1.4.2] *) Sun JDK 1.5.0.09 [sun-jdk-1.5] run these commands: echo 'int main(){}' > test.cpp g++ test.cpp >& test.log g++ -v test.cpp >& test.verbose.log g++ -S test.cpp -o test.S g++ -E test.cpp -o test.ii g++ -E -dD test.cpp -o test.ii.dd and then post each of those files as attachments It seems indeed that something on the toolchain is broken. Created attachment 105404 [details]
test.verbose.log
test.log is empty
Created attachment 105405 [details]
test.S
Created attachment 105406 [details]
test.ii
Created attachment 105407 [details]
test.ii.dd
Thanks a lot!
you're saying that `g++ test.cpp` worked ? if that's true, please redo those tests, but use this for your test.cpp: #include <iostream> void someoutput (void) { std::cout << 123; } int main (void) { return 0; } Created attachment 105419 [details]
test.log
It seems it did not worked.
Created attachment 105420 [details]
test.verbose.log
Created attachment 105421 [details]
test.ii
Created attachment 105422 [details]
test.ii.dd
Created attachment 105423 [details]
test.S
for some reason your gcc thinks your assembler supports .weakref when it obviously does not ... did you have newer versions of binutils installed at some point ? if you built gcc-4.1.1 with binutils-2.17 but then downgraded your binutils to 2.16.1, you'd hit this localhost dwm # equery list binutils [ Searching for package 'binutils' in all categories among: ] * installed packages [I--] [ -] sys-devel/binutils-2.16.1-r3 (0) [I--] [ ] sys-devel/binutils-config-1.9-r3 (0) I don't know if i had a newer version installed before. Is there a command that gives all the versions that where built? What can i do exactly? Thanks a lot!! run `qlop -l binutils` ... if you dont have `qlop`, run `emerge portage-utils` solution: dont downgrade your binutils *** Bug 147303 has been marked as a duplicate of this bug. *** *** Bug 149710 has been marked as a duplicate of this bug. *** *stabs vapier* don't add me to bugs that don't concern me please if you actually read the bug you'd see that this explained the duped bug report *you filed* *** Bug 172881 has been marked as a duplicate of this bug. *** *** Bug 144563 has been marked as a duplicate of this bug. *** *** Bug 182766 has been marked as a duplicate of this bug. *** *** Bug 186592 has been marked as a duplicate of this bug. *** *** Bug 186594 has been marked as a duplicate of this bug. *** *** Bug 186595 has been marked as a duplicate of this bug. *** *** Bug 187549 has been marked as a duplicate of this bug. *** *** Bug 187549 has been marked as a duplicate of this bug. *** |