On Fri, 21 Apr 2006, Jakub Jelinek wrote:
>> Now, where is the TLS data supposed to be handled? Is that in glibc or
>> somewhere else?
> In the dynamic linker, but your glibc is clearly too old.
> The thing on sparc64 is, the assembler TLS (and GCC) support has been added
> many years ago, for 32-b
On Fri, Apr 21, 2006 at 02:42:49PM +0200, Christian Joensson wrote:
> hmm, I am uncertain again. The testresults available at
> http://gcc.gnu.org/ml/gcc-testresults/2006-04/msg01133.html indicate
> that this is indeed a TLS problem. From the log file of the libgomp
> testsuite (with the -m64 switc
On 4/21/06, Gerald Pfeifer <[EMAIL PROTECTED]> wrote:
> On Thu, 20 Apr 2006, Christian Joensson wrote:
> >> /usr/bin/ld: .libs/barrier.o: check_relocs: unhandled reloc type 0
> >> .libs/barrier.o: could not read symbols: File format not recognized
> >> collect2: ld returned 1 exit status
> >>
> >>
On Thu, 20 Apr 2006, Christian Joensson wrote:
>> /usr/bin/ld: .libs/barrier.o: check_relocs: unhandled reloc type 0
>> .libs/barrier.o: could not read symbols: File format not recognized
>> collect2: ld returned 1 exit status
>>
>> I will restart a build and see if I get to the same error, but, if
On 4/18/06, Christian Joensson <[EMAIL PROTECTED]> wrote:
> .libs/libgomp.so.1.0.0
> /usr/bin/ld: .libs/barrier.o: check_relocs: unhandled reloc type 0
> .libs/barrier.o: could not read symbols: File format not recognized
> collect2: ld returned 1 exit status
>
> I will restart a build and see if
I try to build gcc trunk on sparc/sparc64 linux.
The configure was done like this:
../gcc/configure --enable-__cxa_atexit --enable-shared --with-cpu=v7
--enable-languages=c,ada,c++,fortran,java,objc,obj-c++,treelang
when I enter the libgomp subdir, I see this:
make[2]: Entering directory
`/us
