Current status of the GCC NUV branch
Nate Riffe <[email protected]> Wed, 4 Aug 2004 21:03:40 -0400
| Newsgroups | gmane.linux.bbc.devel |
|---|---|
| Message-ID | <[email protected]> |
I've been working through a toolchain upgrade in lnx-bbc--gcc-nuv--3.3, and have succeeded in building a working gcc 3.3 based toolchain which targets the singularity image. That work is all committed and functioning. There are currently two problem areas in the gcc-nuv branch. First there is the need for a uclibc upgrade and with it a rootbin toolchain, which is where I plan to proceed. Second is that the 2.0.1 version of discover fails to build under gcc 3.3, and so we need the NUV. The latest is 2.0.4, and while it successfully builds under gcc 3.3, its doc/ subtree requires docbook tools. I see two acceptable solutions to this. One is to package the appropriate docbook tools and BUILDDEPS them from kernel/discover, and the other is to patch discover so that we skip its doc/ subtree in the build. I'm inclined to favor the first solution, but regardless of which way we go on this, could someone else pursue the issue? -Nate -- --< ((\))< >----< [email protected] >----< http://www.movealong.org/ >-- pub 1024D/05A058E0 2002-03-07 Nate Riffe (06-Mar-2002) <[email protected]> Key fingerprint = 0DAC F5CB D182 3165 D757 C466 CD42 12A8 05A0 58E0