Re: intent to package pa-risc stuff
Justin Maurer wrote: Justin, can you find out if those machines are binary compatible. I've heard that there are two general types flying around (5i and 3i, iirc). I wonder if one new architecture is enough or if we need both - like for mips. which two machines? the ones the puffins are working on? they are working on the a180c (a-class). it is only a 32-bit machine, however. i think it is compatible with all the 64-bit machines, and can confirm this if you'd like and provide me with more info. HP told me that there were two types of machines, or two types of architectures. I'm not familiar with PA RISC so I can't say much. It's possible that the difference was 32 bit and 64 bit. If the code is compatible, that's fine. Regards, Joey -- GNU does not eliminate all the world's problems, only some of them. -- The GNU Manifesto Please always Cc to me when replying to me on the lists.
Re: intent to package pa-risc stuff
Justin Maurer wrote: consider this my intent to package pa-risc egcs and binutils. the kernel, when one arrives, too. i speak with the puffins (www.thepuffingroup.com, for those who don't know) on a daily basis, so i suppose i am a good candidate. i plan to order myself a machine when my next paycheck rolls around (if spi wants to foot some of the bill, that would be just fine by me...:), but the port is still *months* away from a booting kernel. I wonder if this ITP is a little bit early then... anyway, since for now they will be x-compilers, where should the bins be placed? should egcs be /usr/bin/egcs-parisc? /usr/parisc/egcs? We will have to create binary-parisc or similar. As the beginning, where no port exists, a directory within experimental looks proper to me. Justin, can you find out if those machines are binary compatible. I've heard that there are two general types flying around (5i and 3i, iirc). I wonder if one new architecture is enough or if we need both - like for mips. Regards, Joey -- Computers are not intelligent. They only think they are. Please always Cc to me when replying to me on the lists.
Re: intent to package pa-risc stuff
(me saying a bootable kernel is still quite aways off) I wonder if this ITP is a little bit early then... well, sort of. i can still package the cross compilers and such, so that we will all be ready for it. but the new arch obviously is still another relase or two away. i have binutils packaged, and i haven't worked on it in awhile, but i think egcs is mostly done, too... anyway, since for now they will be x-compilers, where should the bins be placed? should egcs be /usr/bin/egcs-parisc? /usr/parisc/egcs? We will have to create binary-parisc or similar. well, for the cross compilers, i'm doing /usr/lib/parisc-xxx e.g, /usr/bin/parisc-egcs /usr/bin/parisc-as etc. As the beginning, where no port exists, a directory within experimental looks proper to me. agreed. Justin, can you find out if those machines are binary compatible. I've heard that there are two general types flying around (5i and 3i, iirc). I wonder if one new architecture is enough or if we need both - like for mips. which two machines? the ones the puffins are working on? they are working on the a180c (a-class). it is only a 32-bit machine, however. i think it is compatible with all the 64-bit machines, and can confirm this if you'd like and provide me with more info. -- Justin Maurer[EMAIL PROTECTED] IFT Systems, Inc.http://linux.hypnotic.org 6717 N.31st Street Tel: +1 (703) 237-5511 Arlington, Virginia, 22213 USA acf on LinuxNet
Re: intent to package pa-risc stuff
On Tue, May 18, 1999 at 01:45:04PM -0500, Justin Maurer wrote:
well, for the cross compilers, i'm doing /usr/lib/parisc-xxx
e.g,
/usr/bin/parisc-egcs
/usr/bin/parisc-as
etc.
You should really use standard gnu style, such as parisc-linux-{gcc,as,ld,...}
and /usr/parisc-linux/{lib,bin,include}/
Please don't upload a package that would create confusion in the naming scheme
that most people are used to.
Re: intent to package pa-risc stuff
At 14:56 -0400 1999-05-18, Ben Collins wrote:
On Tue, May 18, 1999 at 01:45:04PM -0500, Justin Maurer wrote:
well, for the cross compilers, i'm doing /usr/lib/parisc-xxx
e.g,
/usr/bin/parisc-egcs
/usr/bin/parisc-as
etc.
You should really use standard gnu style, such as
parisc-linux-{gcc,as,ld,...}
and /usr/parisc-linux/{lib,bin,include}/
I might add that the tools do that automagically when configured in a
host != target configuration.
Please don't upload a package that would create confusion in the naming scheme
that most people are used to.
And do not use a cpu name that config.sub does not understand, the
GNU tools use hppa throughout, changing it will require that we
patch every config.guess and config.sub in the source packages that
use autoconf.
--
Joel Klecker (aka Espy)Debian GNU/Linux Developer
URL:mailto:[EMAIL PROTECTED] URL:mailto:[EMAIL PROTECTED]
URL:http://web.espy.org/ URL:http://www.debian.org/
