public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-catalyst] How to enable/disable FEATURES in spec files?
@ 2010-07-10  0:54 Matt Turner
  2010-07-13 13:30 ` [gentoo-catalyst] " Matt Turner
  0 siblings, 1 reply; 6+ messages in thread
From: Matt Turner @ 2010-07-10  0:54 UTC (permalink / raw
  To: gentoo-catalyst

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



^ permalink raw reply	[flat|nested] 6+ messages in thread

* [gentoo-catalyst] Re: How to enable/disable FEATURES in spec files?
  2010-07-10  0:54 [gentoo-catalyst] How to enable/disable FEATURES in spec files? Matt Turner
@ 2010-07-13 13:30 ` Matt Turner
  2010-07-13 14:06   ` Michael Zanetta
  2010-07-13 14:54   ` Tom Stellard
  0 siblings, 2 replies; 6+ messages in thread
From: Matt Turner @ 2010-07-13 13:30 UTC (permalink / raw
  To: gentoo-catalyst

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?



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-catalyst] Re: How to enable/disable FEATURES in spec  files?
  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
  1 sibling, 1 reply; 6+ messages in thread
From: Michael Zanetta @ 2010-07-13 14:06 UTC (permalink / raw
  To: gentoo-catalyst

Have you tried using 'export FEATURES="-sandbos"' in catalystrc ?

On Tue, Jul 13, 2010 at 3:30 PM, Matt Turner <mattst88@gmail.com> 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?
>
>



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-catalyst] Re: How to enable/disable FEATURES in spec files?
  2010-07-13 13:30 ` [gentoo-catalyst] " Matt Turner
  2010-07-13 14:06   ` Michael Zanetta
@ 2010-07-13 14:54   ` Tom Stellard
  2010-07-13 15:30     ` Matt Turner
  1 sibling, 1 reply; 6+ messages in thread
From: Tom Stellard @ 2010-07-13 14:54 UTC (permalink / raw
  To: gentoo-catalyst

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



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-catalyst] Re: How to enable/disable FEATURES in spec  files?
  2010-07-13 14:54   ` Tom Stellard
@ 2010-07-13 15:30     ` Matt Turner
  0 siblings, 0 replies; 6+ messages in thread
From: Matt Turner @ 2010-07-13 15:30 UTC (permalink / raw
  To: gentoo-catalyst

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!



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-catalyst] Re: How to enable/disable FEATURES in spec  files?
  2010-07-13 14:06   ` Michael Zanetta
@ 2010-07-13 15:31     ` Matt Turner
  0 siblings, 0 replies; 6+ messages in thread
From: Matt Turner @ 2010-07-13 15:31 UTC (permalink / raw
  To: gentoo-catalyst

On Tue, Jul 13, 2010 at 10:06 AM, Michael Zanetta <grimmlin@pentoo.ch> wrote:
> Have you tried using 'export FEATURES="-sandbos"' in catalystrc ?

I had tried 'FEATURES="-sandbox"' without the export. :\

Thanks, this works.
Matt

> On Tue, Jul 13, 2010 at 3:30 PM, Matt Turner <mattst88@gmail.com> 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?



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2010-07-13 16:02 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox