[gentoo-dev] Pentium M stages

[gentoo-dev] Pentium M stages

[Josh Glover]

[-- Attachment #1: Type: text/plain, Size: 2554 bytes --]

I am very interested in using Catalyst to make Stages 1-3 for Pentium M
CPUs. The problem with just using Pentium 3 stages is that Pentium M
supports SSE2 instructions, whereas P3 does not. Adding -msse2 to my
CFLAGS is fine for me, but when I want to reinstall or setup a Faketoo[1]
instance for Portage development on my laptop, I don't want to have to
start from Stage 1. Even if no-one else in the world is interested in
Pentium M stage tarballs (which I seriously doubt is the case), I would
like them for my own use.

I tried first with this specfile:

subarch: pentium-m
version_stamp: 20040509
target: stage1
rel_type: default
rel_version: 2004.1
profile: default-pentium3-2004.1
snapshot: 20040413
source_subpath: default/stage3-pentium3-2004.1

But the result was (not surprisingly for those of you who are familiar
with Catalyst):

: jmglov@laurana; sudo catalyst -f /etc/catalyst/pentium-m-stage1-20040509.spec
Setting storedir to default value "/var/tmp/catalyst"
Setting portdir to default value "/usr/portage"
Setting distdir to config file value "/usr/portage/distfiles"
Setting options to config file value "ccache pkgcache"
Setting sharedir to config file value "/usr/lib/catalyst"
Compiler cache support enabled.
Package cache support enabled.
Traceback (most recent call last):
  File "/usr/bin/catalyst", line 100, in ?
    mytarget=targetmap[myspec["target"]](myspec,addlargs)
  File "/usr/lib/catalyst/modules/targets.py", line 367, in __init__
    generic_stage_target.__init__(self,spec,addlargs)
  File "/usr/lib/catalyst/modules/targets.py", line 73, in __init__
    self.arch=self.subarchmap[self.settings["subarch"]](self.settings)
KeyError: 'pentium-m'

So I altered the specfile to this:

subarch: pentium3
version_stamp: 20040509
target: stage1
rel_type: default
rel_version: 2004.0
profile: default-pentium3-2004.0
snapshot: 20040413
source_subpath: default/stage3-pentium3-2004.1

(I tweaked the rel_version and profile back to 2004.0 because setting
them to 2004.1 was resulting in a bad symlink which killed Catalyst
at a later point.)

I also added an envscript, containing the single line:

export CFLAGS="-O2 -march=pentium3 -msse2 -fomit-frame-pointer -pipe"

The problem is that my CFLAGS seem to be ignored when Catalyst starts
to build the stage.

Anyone have any ideas as to what I am doing wrong?


-- 
Josh Glover

GPG keyID 0xDE8A3103 (C3E4 FA9E 1E07 BBDB 6D8B  07AB 2BF1 67A1 DE8A 3103)
gpg --keyserver pgp.mit.edu --recv-keys DE8A3103

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Pentium M stages

[Chris Gianelloni]

On Sun, 2004-05-09 at 13:58, Josh Glover wrote:
> I am very interested in using Catalyst to make Stages 1-3 for Pentium M
> CPUs. The problem with just using Pentium 3 stages is that Pentium M
> supports SSE2 instructions, whereas P3 does not. Adding -msse2 to my
> CFLAGS is fine for me, but when I want to reinstall or setup a Faketoo[1]
> instance for Portage development on my laptop, I don't want to have to
> start from Stage 1. Even if no-one else in the world is interested in
> Pentium M stage tarballs (which I seriously doubt is the case), I would
> like them for my own use.
> 
> I tried first with this specfile:
> 
> subarch: pentium-m
> version_stamp: 20040509
> target: stage1
> rel_type: default
> rel_version: 2004.1
> profile: default-pentium3-2004.1
> snapshot: 20040413
> source_subpath: default/stage3-pentium3-2004.1
> 
> But the result was (not surprisingly for those of you who are familiar
> with Catalyst):
> 
> : jmglov@laurana; sudo catalyst -f /etc/catalyst/pentium-m-stage1-20040509.spec
> Setting storedir to default value "/var/tmp/catalyst"
> Setting portdir to default value "/usr/portage"
> Setting distdir to config file value "/usr/portage/distfiles"
> Setting options to config file value "ccache pkgcache"
> Setting sharedir to config file value "/usr/lib/catalyst"
> Compiler cache support enabled.
> Package cache support enabled.
> Traceback (most recent call last):
>   File "/usr/bin/catalyst", line 100, in ?
>     mytarget=targetmap[myspec["target"]](myspec,addlargs)
>   File "/usr/lib/catalyst/modules/targets.py", line 367, in __init__
>     generic_stage_target.__init__(self,spec,addlargs)
>   File "/usr/lib/catalyst/modules/targets.py", line 73, in __init__
>     self.arch=self.subarchmap[self.settings["subarch"]](self.settings)
> KeyError: 'pentium-m'
> 
> So I altered the specfile to this:
> 
> subarch: pentium3
> version_stamp: 20040509
> target: stage1
> rel_type: default
> rel_version: 2004.0
> profile: default-pentium3-2004.0
> snapshot: 20040413
> source_subpath: default/stage3-pentium3-2004.1
> 
> (I tweaked the rel_version and profile back to 2004.0 because setting
> them to 2004.1 was resulting in a bad symlink which killed Catalyst
> at a later point.)
> 
> I also added an envscript, containing the single line:
> 
> export CFLAGS="-O2 -march=pentium3 -msse2 -fomit-frame-pointer -pipe"
> 
> The problem is that my CFLAGS seem to be ignored when Catalyst starts
> to build the stage.
> 
> Anyone have any ideas as to what I am doing wrong?

I was under the impression that stage1 is always a stage1 and doesn't
have optimizations.  See if when you get to stage2 it doesn't start
using your optimizations as placed in your envscript.

-- 
Chris Gianelloni
Developer, Gentoo Linux
Games Team

Is your power animal a pengiun?


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Pentium M stages

[John Davis]

[-- Attachment #1: Type: text/plain, Size: 758 bytes --]

On Sun, 2004-05-09 at 14:10, Chris Gianelloni wrote:
> > 
> > Anyone have any ideas as to what I am doing wrong?
> 
> I was under the impression that stage1 is always a stage1 and doesn't
> have optimizations.  See if when you get to stage2 it doesn't start
> using your optimizations as placed in your envscript.

pentium-m is not a recognized subarchitecture. If it does not use P4 or
P3 optimizations, you will have to add a subarch to
/usr/lib/catalyst/modules/targets.py. Otherwise, use the P{4,3}
optimizations.

Cheers,
//zhen
-- 
John Davis
Gentoo Linux Developer
<http://dev.gentoo.org/~zhen>

----
GnuPG Public Key: <http://dev.gentoo.org/~zhen/zhen_pub.asc>
Fingerprint: 2364 71BD 4BC2 705D F338  FF70 6650 1235 1946 2D47


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]