Hi Javier, and thank you for your reply.

Saturday 15 Aug 2009 10:44:27 (-0300), Javier Villavicencio wrote :
>
> Ahh good old times. FreeBSD devs did also patch GCC sources to work on
> FreeBSD. See http://bugs.gentoo.org/192403 for what it takes to get "our
> toolchain" to behave properly on FreeBSD. And that's why I asked some
> time ago if you managed to compile the kernel with a gentoo toolchain,
> it's a big pain in the back :D.
>
> There might be many things patched, however those in the gcc spec are
> key to get a working gcc, and lucky us, the specs don't vary too much,
> so you can try a diff between NetBSD gcc specs versus GNU gcc specs to
> spot what's missing/required.
>
> From there you can start a "copy" of your sys-devel/gcc ebuild of
> choice, and add patches as required, once you get a somewhat working
> version the patches can be tested/reviewed by the GNU devs to iron out
> what's not required, what's correct, and what's wrong.
>
> And here is where the legal BSD vs GPL battle starts, cause you can't
> add BSD copyrighted code into GPL code :D, fun fun.
>
> As a last note, beware that some of the ebuilds in portage may not
> compile correctly or at all if they don't use a GNU (gentooized, but gnu
> at it's heart) toolchain, which includes the versions of the utils
> stated above (m4, sed, awk, etc), binutils, and gcc.
>
> Salu2!,
> Javier.
>

That seems to be a huge amount of work. As said before, I'll keep things
"as-is" for now because it just works. This week, I'll focus on problems
solving with PAM and stage building. I'm sorry but I'm a bit in a hurry due to
lack of time. I want to bring something functionnal for everyone. I really want
to continue my work after GSoC, don't doubt on my motivation. You, guys and
devs of this mailing list, were always here to bring me some piece of advices
when I was in trouble.. I want to give a back to you. :)

Cheers!

Patrice