[Bug ld/6431] ld says: invalid version 3 (max 0)
--- Additional Comments From nickc at redhat dot com 2008-07-21 15:28 --- Subject: Re: ld says: invalid version 3 (max 0) Hi niki, > found a workaround!!! ... it seems that on sol10, all pthread_XXX stuff is now > in libc.so. if you remove the -lpthread -thread options when glib compiles, > everything looks good. Hmm, so to me this sounds like it is a glib problem - ie its build makefile needs to be altered to remove the thread library when building on Solaris 10. Have you tried asking about this on their email list ? Cheers Nick -- http://sourceware.org/bugzilla/show_bug.cgi?id=6431 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
Re: [Bug ld/6727] Thumb interworking code zero when another section is positioned before positioning .text
Hi Aaron,
how do i build binutils from source for ARM?
i followed instructions on http://www.gnuarm.com/support.html
Well those instructions should work, although obviously you can stop
once you have built and installed your new set of binutils.
# cd [binutils-build]
# [binutils-source]/configure --target=arm-elf --prefix=[toolchain-prefix]
# --enable-interwork --enable-multilib
# make all install
i found this to be incorrect. so, i changed it to:
--program-prefix=arm-elf --prefix=${HOME}/local --target=arm-elf
however, i get a message that i am building for arm-unknown-elf.
what should i do?
Is that a problem ? The config.sub script automatically expands
"arm-elf" into "arm-unknown-elf". This is OK. The middle part of the
triplet is the manufacturer's name and "unknown" is a perfectly common
value. The binutils should still build correctly.
I should also point out that you should not be invoking the linker directly.
however, if i use GCC to link, i will not be able to position the
objects and libraries in the order i want.
OK, but please be careful to construct the linker command line
correctly. (I mentioned using gcc to drive the linker because quiet a
few bug reports that we receive are due to people trying to run the
linker directly and not appreciating the work that gcc does in
constructing the command line).
Cheers
Nick
___
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug ld/6727] Thumb interworking code zero when another section is positioned before positioning .text
--- Additional Comments From nickc at redhat dot com 2008-07-21 15:53
---
Subject: Re: Thumb interworking code zero when another section
is positioned before positioning .text
Hi Aaron,
> how do i build binutils from source for ARM?
> i followed instructions on http://www.gnuarm.com/support.html
Well those instructions should work, although obviously you can stop
once you have built and installed your new set of binutils.
> # cd [binutils-build]
> # [binutils-source]/configure --target=arm-elf --prefix=[toolchain-prefix]
> # --enable-interwork --enable-multilib
> # make all install
>
> i found this to be incorrect. so, i changed it to:
> --program-prefix=arm-elf --prefix=${HOME}/local --target=arm-elf
>
> however, i get a message that i am building for arm-unknown-elf.
> what should i do?
Is that a problem ? The config.sub script automatically expands
"arm-elf" into "arm-unknown-elf". This is OK. The middle part of the
triplet is the manufacturer's name and "unknown" is a perfectly common
value. The binutils should still build correctly.
>> I should also point out that you should not be invoking the linker directly.
>
> however, if i use GCC to link, i will not be able to position the
> objects and libraries in the order i want.
OK, but please be careful to construct the linker command line
correctly. (I mentioned using gcc to drive the linker because quiet a
few bug reports that we receive are due to people trying to run the
linker directly and not appreciating the work that gcc does in
constructing the command line).
Cheers
Nick
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6727
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.
___
bug-binutils mailing list
bug-binutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-binutils
Re: linker problem ? help needed !!!
Hi Navi, i am trying to link some object files but i am getting error "System cant execute this program" Please can you tell us: * What type of host machine you are using. * What type of target machine you are linking for. * Which version of the linker are you using ? * What is the command line that you are using ? It would also really help if you could put together a *small* demonstration of the problem that we can use to reproduce the issue locally. Cheers Nick ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug ld/6431] ld says: invalid version 3 (max 0)
--- Additional Comments From niki dot waibel at gmx dot net 2008-07-21 17:02 --- well -- as a workaround, you can remove -lpthread -thread options from gcc. but binutils/ld should also be able to handle this case. exiting with a message like "invalid version 3 (max 0)" is meaningless, especially, if it means that you should remove some gcc options (and everything works ok, for some magic reason) ... the right way to fix this is binutils/ld, and not glib (and possibly every other package using pthreads on solaris10). -- http://sourceware.org/bugzilla/show_bug.cgi?id=6431 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug ld/6758] New: Import library produced by --out-implib doesn't work with MSVC
When using an import library produced by --out-implib with MSVC, the Microsoft linker reports this warning: pcre.lib(d04.o) : warning LNK4078: multiple '.text' sections found with different attributes (E020) The resulting executable crashes immediately when a function in the library is called. Workaround: If I instead produce a .def file with --output-def, I can use Microsoft's lib.exe to create an import library that works correctly - no link warning and no problems using the dll from the MSVC compiled application. Specifics: Windows Vista x64, MSVC 9.0, 32 bit build environment, ld.exe version 2.17.50 20060824, gcc 3.4.5 (mingw-vista special r3), compiling PCRE 7.7. -- Summary: Import library produced by --out-implib doesn't work with MSVC Product: binutils Version: 2.17 Status: NEW Severity: normal Priority: P2 Component: ld AssignedTo: unassigned at sources dot redhat dot com ReportedBy: msw at stjernholm dot org CC: bug-binutils at gnu dot org GCC build triplet: i686-pc-mingw32 GCC host triplet: i686-pc-mingw32 GCC target triplet: i686-pc-mingw32 http://sourceware.org/bugzilla/show_bug.cgi?id=6758 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
