[helix-maintainers] SYSTEM_ID recommendations for Helix Player
Ryan Gammon
rgammon@real.com
Wed, 27 Apr 2005 11:46:36 -0700
This is a multi-part message in MIME format.
--------------020603060703010308020909
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Hi guys,
Our debian package maintainer (and a few other folks) are looking for
some tips on what they can use for SYSTEM_ID's for some of the various
cpu architectures supported by linux.
The full list of what debian tries to support with the helix player:
http://people.debian.org/~igloo/status.php?packages=helix-player
From the below, I figure we have a decent shot at building on amd64,
i386, and powerpc -- the most desktop-oriented cpu architectures.
If one were interested in contributing support for additional CPU
architectures for the helix client, the general steps would be to:
- create a .cf for that cpu architecture, using existing .cf's as a
reference.
- the fix build busters
Does that sound right?
(Out of curiousity, what would be involved in removing some of the more
rotten of the .cf's? umakecf is getting kinda cluttered. If we remove a
.cf, does that mean that we can't go back and build old products with
that .cf (ie - will the build system check ribosome out from a
branch/time that corresponds to the product being built, and hence pick
up the old cf that way)?)
*Arch
* *SYSTEM_ID
* *Status
*
alpha none
Candidate is:
linux-2.0-libc6-alpha-gcc2.95.cf
Needs to be updated, potentially should include: linux-2.2-libc6-gcc32.cf
amd64 linux-2.6-glibc23-amd64.cf
Has some awkward but harmless
project.IsDefined('HELIX_FEATURE_SERVER') stuff. Not sure how we pick
the version numbers here for kernel and glibc -- if they're minimums,
they could potentially be lower.
Last word on the amd64 port is that the player comes up, but RA/RV
playback gives weird errors, and audio doesn't work.
arm none
Options are:
linux-2.2-libc6-armv4l-cross-gcc2.95.cf
linux-2.2-libc6-armv4l-cross-gcc3.2-softfloat.cf
linux-2.2-libc6-armv4l-cross-gcc3.2.cf
linux-2.2-libc6-armv4l-zaurus.cf
linux-2.2-libc6-armv4l.cf
linux-2.2-libc6-armv5te-cross-gcc3.3-iwmmxt-softfloat.cf
linux-2.2-libc6-armv5te-cross-gcc3.3-softfloat.cf
linux-2.2-mizi-armv4l-xscale.cf
linux-2.2-libc6-armv4l.cf is the closest, but needs to be fixed up to
use linux-2.2-libc6-gcc32.cf instead of linux-2.2-libc6-i386.cf, and
ideally wouldn't override project.output_dir
hppa none
Candidates are:
hpux-10.2-parisc.cf
hpux-11.0-parisc.cf
... both of which are for HPUX / HP compiler, not hppa linux
i386 linux-2.2-libc6-gcc32-i586.cf
Looks good, has some rlink stuff that could be pushed down to
linux-common.cf (assuming rlink is cpu architecture independant)
ia64 none
linux-2.4-libc6-ia64.cf
Needs to be updated, potentially should include: linux-2.2-libc6-gcc32.cf
m68k none
No candidates
mips none
No candidates
mipsel none
No candidates (though I've built with linux-2.0-libc6-mips-ps2.cf in
the past, which is actually mipsel).
powerpc linux-2.2-libc6-gcc32-powerpc.cf
Needs to be updated, potentially should include: linux-2.2-libc6-gcc32.cf
s390 none
No candidates
sparc none
Candidate is:
linux-2.2-libc6-sparc.cf
Needs to be updated, potentially should include: linux-2.2-libc6-gcc32.cf
--
Ryan Gammon
rgammon@real.com
Developer for Helix Player
https://player.helixcommunity.org
--------------020603060703010308020909
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi guys,<br>
<br>
Our debian package maintainer (and a few other folks) are looking for
some tips on what they can use for SYSTEM_ID's for some of the various
cpu architectures supported by linux.<br>
<br>
The full list of what debian tries to support with the helix player:<br>
<a class="moz-txt-link-freetext" href="http://people.debian.org/~igloo/status.php?packages=helix-player">http://people.debian.org/~igloo/status.php?packages=helix-player</a><br>
<br>
>From the below, I figure we have a decent shot at building on amd64,
i386, and powerpc -- the most desktop-oriented cpu architectures.<br>
<br>
If one were interested in contributing support for additional CPU
architectures for the helix client, the general steps would be to:<br>
- create a .cf for that cpu architecture, using existing .cf's as a
reference.<br>
- the fix build busters<br>
<br>
Does that sound right?<br>
<br>
(Out of curiousity, what would be involved in removing some of the more
rotten of the .cf's? umakecf is getting kinda cluttered. If we remove a
.cf, does that mean that we can't go back and build old products with
that .cf (ie - will the build system check ribosome out from a
branch/time that corresponds to the product being built, and hence pick
up the old cf that way)?)<br>
<br>
<br>
<table border="1" cellpadding="2" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><b>Arch<br>
</b></td>
<td valign="top"><b>SYSTEM_ID<br>
</b></td>
<td valign="top"><b>Status<br>
</b></td>
</tr>
<tr>
<td valign="top">alpha</td>
<td valign="top">none <br>
</td>
<td valign="top">Candidate is:<br>
linux-2.0-libc6-alpha-gcc2.95.cf<br>
<br>
Needs to be updated, potentially should include:
linux-2.2-libc6-gcc32.cf<br>
</td>
</tr>
<tr>
<td valign="top">amd64</td>
<td valign="top">linux-2.6-glibc23-amd64.cf<br>
</td>
<td valign="top">Has some awkward but harmless
project.IsDefined('HELIX_FEATURE_SERVER') stuff. Not sure how we pick
the version numbers here for kernel and glibc -- if they're minimums,
they could potentially be lower.<br>
<br>
Last word on the amd64 port is that the player comes up, but RA/RV
playback gives weird errors, and audio doesn't work.<br>
</td>
</tr>
<tr>
<td valign="top">arm</td>
<td valign="top">none<br>
</td>
<td valign="top">Options are:<br>
linux-2.2-libc6-armv4l-cross-gcc2.95.cf<br>
linux-2.2-libc6-armv4l-cross-gcc3.2-softfloat.cf<br>
linux-2.2-libc6-armv4l-cross-gcc3.2.cf<br>
linux-2.2-libc6-armv4l-zaurus.cf<br>
linux-2.2-libc6-armv4l.cf<br>
linux-2.2-libc6-armv5te-cross-gcc3.3-iwmmxt-softfloat.cf<br>
linux-2.2-libc6-armv5te-cross-gcc3.3-softfloat.cf<br>
linux-2.2-mizi-armv4l-xscale.cf<br>
<br>
linux-2.2-libc6-armv4l.cf is the closest, but needs to be fixed up to
use linux-2.2-libc6-gcc32.cf instead of linux-2.2-libc6-i386.cf, and
ideally wouldn't override project.output_dir<br>
</td>
</tr>
<tr>
<td valign="top">hppa</td>
<td valign="top">none<br>
</td>
<td valign="top">Candidates are:<br>
hpux-10.2-parisc.cf<br>
hpux-11.0-parisc.cf<br>
<br>
... both of which are for HPUX / HP compiler, not hppa linux<br>
</td>
</tr>
<tr>
<td valign="top">i386</td>
<td valign="top">linux-2.2-libc6-gcc32-i586.cf<br>
</td>
<td valign="top">Looks good, has some rlink stuff that could be
pushed down to linux-common.cf (assuming rlink is cpu architecture
independant)<br>
</td>
</tr>
<tr>
<td valign="top">ia64</td>
<td valign="top">none<br>
</td>
<td valign="top">linux-2.4-libc6-ia64.cf<br>
Needs to be updated, potentially should include:
linux-2.2-libc6-gcc32.cf<br>
</td>
</tr>
<tr>
<td valign="top">m68k</td>
<td valign="top">none<br>
</td>
<td valign="top">No candidates<br>
</td>
</tr>
<tr>
<td valign="top">mips</td>
<td valign="top">none<br>
</td>
<td valign="top">No candidates<br>
</td>
</tr>
<tr>
<td valign="top">mipsel</td>
<td valign="top">none<br>
</td>
<td valign="top">No candidates (though I've built with
linux-2.0-libc6-mips-ps2.cf in the past, which is actually mipsel).<br>
</td>
</tr>
<tr>
<td valign="top">powerpc</td>
<td valign="top">linux-2.2-libc6-gcc32-powerpc.cf<br>
</td>
<td valign="top">Needs to be updated, potentially should include:
linux-2.2-libc6-gcc32.cf</td>
</tr>
<tr>
<td valign="top">s390</td>
<td valign="top">none<br>
</td>
<td valign="top">No candidates<br>
</td>
</tr>
<tr>
<td valign="top">sparc</td>
<td valign="top">none<br>
</td>
<td valign="top">Candidate is:<br>
linux-2.2-libc6-sparc.cf<br>
<br>
Needs to be updated, potentially should include:
linux-2.2-libc6-gcc32.cf<br>
</td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Ryan Gammon
<a class="moz-txt-link-abbreviated" href="mailto:rgammon@real.com">rgammon@real.com</a>
Developer for Helix Player
<a class="moz-txt-link-freetext" href="https://player.helixcommunity.org">https://player.helixcommunity.org</a>
</pre>
</body>
</html>
--------------020603060703010308020909--