![](https://secure.gravatar.com/avatar/4e374bb9f03cbbca5d9541a8bf8ec8bf.jpg?s=120&d=mm&r=g)
24 May
2007
24 May
'07
11:55 a.m.
Hi Pawel, On Thu, May 24, 2007 at 13:26:10 +0200, Pawel Wielgus wrote: > Dear CRUXers, > > I'm sorry for non-CRUX-specific question. > I tried to compile gcc4 out of our ports (I was affraid what would > happen if I updated my gcc-3.4.3 to gcc-4.?.? from ports, since I have > quite old OS, still 2.0. I assumed a lot of things would need an update > afterwards...). Well, if you want recent software (like gcc 4.x), it's probably a good idea to update the whole system, not only single components. Deferring the system update will bring you more grief in the end, and the longer you wait with updating the harder it'll be. Unless you never want to upgrade again, of course :-) > Anyway, for gcc-4.2.0 and gcc-4.1.2 I get the same error message, which > is attached below. Google shows the following as a possible fix: http://lists.pld-linux.org/mailman/pipermail/pld-devel-pl/2005-February/123508.html In other words a header provided by glibc in CRUX 2.0's version needs an adjustment to build with the "newer" gccs. > Anyone could help me to solve this and suggest a solution ? 1. Update your distribution -> consistent system with current versions 2. Stay with gcc 3.4 if you want to -> consistent system with outdated versions 3. update glibc 4. patch your glibc headers I'd try to avoid #3 and #4, unless you're familiar with the issues involved with glibc/gcc upgrades. HTH, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch