At Sat, 22 Jan 2005 01:16:01 +0100, Guillem Jover <[EMAIL PROTECTED]> wrote: > > Hi, > > [ This is a repost of the latest patch. ] > > This patch is the one we are using on the latest gnumach Debian > package. > > It should be applied as Neal explained: > > $ cd gnumach-1-branch > $ mv i386/linux/{Drivers.in,configure.ac} > $ patch -p1 < gnumach-1.3_autoconf_update-3.patch > $ autoreconf -fis
You need to test if this doesn't break a full bootstrap. A full bootstrap works like this: 1. You compile a cross binutils and install it. 2. You try to compile a cross gcc, which will fail in libgcc2.a, but you can force it with -k. The resulting compiler will be in a half-broken state. 3. Compile and install Mach. We need to be able to at least install the header file, but the gcc from step 2 should already be able to compile the full kernel. 4. ... The thing is that the standard autoconf checks fail and bail out of configure if they find gcc in the half-broken state above. I think this is the reason why they were not used. OTOH, I could just be making it all up :) It is certainly the problem I am currently seeing in the Hurd on L4, and it seems to make sense that the same would happen with a gnumach configure based on the standard checks. In any case, the above full bootstrap procedure (assuming you cleared out your /usr/i686-gnu first, or whatever path you use) must work more or less as described in INSTALL-cross or Alfred's Cross-compiling guide from last september. If you can't configure and run make install-headers with a broken gcc, you are in some trouble getting the system up and running. Thanks, Marcus _______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd