Your message dated Sat, 30 Jun 2001 13:14:14 +0200 with message-id <[EMAIL PROTECTED]> and subject line source parallelisation suggestion has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Darren Benham (administrator, Debian Bugs database) -------------------------------------- Received: (at submit) by bugs.debian.org; 18 Mar 2001 18:04:55 +0000 >From [EMAIL PROTECTED] Sun Mar 18 12:04:55 2001 Return-path: <[EMAIL PROTECTED]> Received: from ferret.phonewave.net (tarot.mentasm.org) [208.138.51.183] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 14ehXy-000188-00; Sun, 18 Mar 2001 12:04:54 -0600 Received: from heathen.mentasm.org [192.168.1.43] (mail) by tarot.mentasm.org with esmtp (Exim 3.12 #1 (Debian)) id 14ehXd-0001lG-00; Sun, 18 Mar 2001 10:04:33 -0800 Received: from idalton by heathen.mentasm.org with local (Exim 3.22 #1 (Debian)) id 14ehXu-00033P-00; Sun, 18 Mar 2001 10:04:50 -0800 From: <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: source parallelisation suggestion X-Reportbug-Version: 1.14 X-Mailer: reportbug 1.14 Date: Sun, 18 Mar 2001 10:04:49 -0800 Message-Id: <[EMAIL PROTECTED]> Sender: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] Package: gcc-2.95 Version: 1:2.95.3-6 Severity: wishlist This request is spawned by virtue of building cross-compiler packages on a dual-Pentium 200. I would like for the Debian build system to be able to run the native compiles and the cross-compiler compiles concurrently. The current build system appears (in the course of my tinkering around) to mostly be able to do this already, except for the job control and the source extraction phase. I point out that (for instance) first the native compiler will be built in build-native/, then the sparc-cross built in build-sparc/, and both builds will only utilise one of my two processors. So if these two builds can be performed at the same time, both processors should be utilised. Error handling may also need to be changed. I think the best way to report a build error (most likely not having a build-depends for a target arch, or just a buggy compiler -), would be to stop ALL concurrent builds and to report the build branch and the error to the console. -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux heathen 2.4.1 #1 SMP Thu Feb 1 13:32:45 PST 2001 i586 Versions of packages gcc-2.95 depends on: ii binutils 2.10.91.0.2-3 The GNU assembler, linker and bina ii cpp-2.95 1:2.95.3-6 The GNU C preprocessor. hi gcc 1:2.95.3-5 The GNU C compiler. ii libc6 2.2.2-1 GNU C Library: Shared libraries an --------------------------------------- Received: (at 90143-done) by bugs.debian.org; 30 Jun 2001 11:17:49 +0000 >From [EMAIL PROTECTED] Sat Jun 30 06:17:49 2001 Return-path: <[EMAIL PROTECTED]> Received: from mail.cs.tu-berlin.de [::ffff:130.149.17.13] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 15GIl3-0001KX-00; Sat, 30 Jun 2001 06:17:49 -0500 Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id NAA08712 for <[EMAIL PROTECTED]>; Sat, 30 Jun 2001 13:14:14 +0200 (MET DST) Received: (from [EMAIL PROTECTED]) by bolero.cs.tu-berlin.de (8.10.2+Sun/8.9.3) id f5UBEEa15074; Sat, 30 Jun 2001 13:14:14 +0200 (MEST) From: Matthias Klose <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <[EMAIL PROTECTED]> Date: Sat, 30 Jun 2001 13:14:14 +0200 To: [EMAIL PROTECTED] Subject: source parallelisation suggestion X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Delivered-To: [EMAIL PROTECTED] I doubt that will be done for 2.95.4. the 3.0 packaging has another kind of support for building cross packages: you can only build the native compiler. If you want to build a cross compiler, set GCC_TARGET in the environment. Then only the cross compiler is built, not the native one.