Messages in this thread | | | Date | Thu, 30 Oct 2003 16:55:45 GMT | From | John Bradford <> | Subject | Re: Post-halloween doc updates. |
| |
> > >Compiler issues. > > >~~~~~~~~~~~~~~~~ > > >- The recommended compiler (for x86) is still 2.95.3. > > > > I'm not sure this is still the case, in practice. Recent times have > > seen people breaking 2.95.x, which did not support the C99/C++ style of > > mixing variable declarations and code. People would forget this, and we > > only find out a few days later that the 2.95.x build was broken. > > *nod*, more and more distros are now shipping gcc3 as their stock compiler,
That may be partially motivated by the fact that latest GLIBC no longer compiles with GCC 2.95.x
> so it's likely at some point things are going to change.
Do you think that GCC > 2.95.x actually produces noticably better code though? I'm not convinced yet, and yet compile times can be a lot higher.
By the way, it might be worth adding something to the input devices section suggesting that people try forcing set 3 if they have a keyboard which has keys that are not independently usable, and it's not a regression since 2.4. I have such a keyboard, and I saw a post recently describing similar behavior with a VMS keyboard.
John. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |