public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Re: How to enable/disable FEATURES in spec  files?
Date: Tue, 13 Jul 2010 11:30:21 -0400	[thread overview]
Message-ID: <AANLkTikNwXbxapVUURwR-xEPsL8xxabHU4SPd-NeKNbF@mail.gmail.com> (raw)
In-Reply-To: <20100713145402.GA16977@thinkpadr51e.hsd1.or.comcast.net>

On Tue, Jul 13, 2010 at 10:54 AM, Tom Stellard <tstellar@gmail.com> wrote:
> On Tue, Jul 13, 2010 at 09:30:43AM -0400, Matt Turner wrote:
>> On Fri, Jul 9, 2010 at 8:54 PM, Matt Turner <mattst88@gmail.com> 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?
>>
>
> I think you can do this in your catalystrc file.  Try something like:
> export FEATURES="-sandbox"
>
> -Tom

This works. Thanks Tom!



      reply	other threads:[~2010-07-13 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-10  0:54 [gentoo-catalyst] How to enable/disable FEATURES in spec files? Matt Turner
2010-07-13 13:30 ` [gentoo-catalyst] " Matt Turner
2010-07-13 14:06   ` Michael Zanetta
2010-07-13 15:31     ` Matt Turner
2010-07-13 14:54   ` Tom Stellard
2010-07-13 15:30     ` Matt Turner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikNwXbxapVUURwR-xEPsL8xxabHU4SPd-NeKNbF@mail.gmail.com \
    --to=mattst88@gmail.com \
    --cc=gentoo-catalyst@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox