@ foxylinux preferably before March 2, http://pt.wikipedia.org/wiki/Foxy_Linux

I Wish I Could join Australia-day http://www.internetblackout.com.au/australia-day/ , But I'll celebrate nonetheless

@ robersonfox beautiful your background oxygen, great choice, fill my breath away!

@ jonathanglima mdf to iso is no more problem now n even need cdemu: http://iat.berlios.de/

Congratulations Gentoo, 10 years!

python3 = python 1.240375522193495298121 * ^ 5.1

@ kico1968 Who teaches only one way, is no learning.

Updated to 4.3.1 # KDE

If you got this far, chances are that you also experiencing this problem. If you just look for a solution, you can skip straight to the solution [in my case, in others, the problem is related to gcc-config have left the tree ].

I spent almost a year with this problem occurring almost randomly in my builds, wondering what might be happening ... So I got up to this site, it noticed the following:

GLIBC Version 2.4 (and later) requires TLS support. This means That GCC Version 3.4.3 Will NOT work with GLIBC Version 2.4 (or later). The system make glibc Will Generate The Following compilation error if TLS support is not enabled 'error: # error "TLS support is required"'

I began to wonder if the problem would be in my version of gcc [4.3.3], I checked several things, including support for TLS, it was working! But when gcc was called by portage, it did not work [nonsense!]. I tested calling the gcc-4.3.3 directly, and to my surprise TLS stopped working at the same time. There! The problem was in front all the time.

So I solved it by editing the call of gcc in my make.conf. I remember that I followed some tips [tips?!] to improve the speed of the build system. A hint, noted that when calling gcc [a symlink] gcc actually grew more slowly and are recommended to use the command gcc-$ (VERSION), which actually caused the 'error: # error "TLS support is required "'during the compilation of gblic ...

Visual aid

The solution.

1. Accept that you missed while editing the $ (CC) and $ (CXX) in your make.conf
2. Have seriously to accept that you missed while editing the $ (CC) and $ (CXX) in your make.conf
3. Really regret having edited the $ (CC) and $ (CXX) in your make.conf
4. Erase the lines you setou the $ (CC) and $ (CXX)

If you have repented, the quickest way to clean your make.conf is through the following command:

mv / etc / make.conf / etc / make.conf.tlserror & & cat / etc / make.conf.tlserror | grep-Ev '(CC | CCX) "> / etc / make.conf

Lula's speech at FISL 10, em português! http://bit.ly/jNgiq