From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OYh0C-0000B1-Jv for garchives@archives.gentoo.org; Tue, 13 Jul 2010 15:02:32 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 47E6FE0CE3 for ; Tue, 13 Jul 2010 15:02:32 +0000 (UTC) Received: from mail-bw0-f53.google.com (mail-bw0-f53.google.com [209.85.214.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 40CA8E095B for ; Tue, 13 Jul 2010 14:06:01 +0000 (UTC) Received: by bwz6 with SMTP id 6so4904844bwz.40 for ; Tue, 13 Jul 2010 07:06:00 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org MIME-Version: 1.0 Received: by 10.204.6.10 with SMTP id 10mr12012320bkx.191.1279029960515; Tue, 13 Jul 2010 07:06:00 -0700 (PDT) Received: by 10.204.103.132 with HTTP; Tue, 13 Jul 2010 07:06:00 -0700 (PDT) X-Originating-IP: [195.176.149.172] In-Reply-To: References: Date: Tue, 13 Jul 2010 16:06:00 +0200 Message-ID: Subject: Re: [gentoo-catalyst] Re: How to enable/disable FEATURES in spec files? From: Michael Zanetta To: gentoo-catalyst@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 2e324c74-9e45-4e1c-821d-dabcaab48386 X-Archives-Hash: 2dfefde4c29d5300daeb8d74cdb6c417 Have you tried using 'export FEATURES="-sandbos"' in catalystrc ? On Tue, Jul 13, 2010 at 3:30 PM, Matt Turner wrote: > On Fri, Jul 9, 2010 at 8:54 PM, Matt Turner wrote: >> I'm trying to build some new MIPS stages, and need to disable sandbox >> from FEATURES due to bug 45814. >> >> I've searched google and the catalyst source but don't see any way to >> disable an arbitrary FEATURE flag. I just hacked in a -sandbox and it >> works, but I'd like to think there's a better way. >> >> Also, since there are no recent MIPS-N32 stages, I just tar.bz2'd my >> installation and put it in the builds/ directory for use as the seed >> stage. It uses -march=sb1 in the make.conf, and the packages built by >> `catalyst -f file.spec` seem to be using this CFLAG (as shown by the >> file command, which reports that the binaries produced are MIPS64, >> instead of MIPS IV, as I've requested), even though I've specified >> CFLAGS in the spec file, and given it a proper subarch. Spec file is >> as follows >> >> --- >> subarch: mips4_n32 >> version_stamp: 20100709 >> target: stage3 >> rel_type: default >> profile: default/linux/mips/10.0/n32 >> snapshot: 20100907 >> source_subpath: stage4-mips4_n32-sb1-20100907 >> cflags: -O2 -march=mips4 -mabi=n32 -mplt -pipe >> cxxflags: -O2 -march=mips4 -mabi=n32 -mplt -pipe >> ldflags: -Wl,--as-needed >> >> makeopts: -j2 >> --- >> >> What gives? I'm looking at mips.py, and it looks like it should be >> assigning CFLAGS given subarch = mips4_n32. >> >> Thanks, >> Matt > > Ping? > >