[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uclibc
Subject:    Linking errors
From:       matthias.hofmann () tu-dortmund ! de (Matthias Hofmann)
Date:       2010-03-10 9:09:09
Message-ID: 9e9171699e55737b758d9d05802cb2a8.squirrel () webmail ! tu-dortmund ! de
[Download RAW message or body]

> Hi Matthias,
> Matthias Hofmann wrote,
>
>> Hello,
>>
>> i use a crosscompiler toolchain for compiling and linking programs from
>> cygwin to linux.
>> Currently, i try to figure out some informations about the following
>> linking errors, but i did not had any succes yet.
>
> Difficult to say without actually seeing how ld or gcc is called.
> Another nice information missing is what kind of software you are
> trying to compile. Did you disabled TLS while creating GCC?
> (--disable-tls)
>
> bye
>  Waldemar
>

Hi Waldemar,

you are absolutely right. Here the missing informations:
The buildflags are "-march=k6-2 -pipe -Wall -Wno-strict-aliasing
-Wno-non-virtual-dtor  -Wno-deprecated -fomit-frame-pointer -O3 -mmmx
-m3dnow -fgcse-after-reload -funswitch-loops -finline-functions"
The linkflag is only -s
i don't know if TLS was disabled by the build because i didn't build the
toolchain. is there a way to figure it out?
i build the software with an older version of gcc 4.1.1 and glibc without
any problems.
is it possible to get detailed meta-information about the gcc/toolchain?
thank you,
matthias


[prev in list] [next in list] [prev in thread] [next in thread]