Re: mipsel target
On Mon, Jul 19, 1999 at 09:57:50AM -0400, Justin Maurer wrote:
> > There are "mips" and "mipsel" (Big and Little Endian).
> >
> > Although i thought that Big Endian is called "mipseb" but this
> > seems not to be true.
>
> dunno how official, but mipseb/mipsel is what i've always seen them called,
> at least when it was necessary to differentiate between the two.
I thought so too but Ulf is currently building with mips (Big Endian)
as mentioned in the Mips FAQ.
> > I began to work on the Debian/mipsel which is quiete difficult
> > as i have a running System (Half selfmade and half Redhat) on
> > mips and tried now to compile packages. This was half
> > successful (although the dependencies were broken as expected)
>
> ulf carlsson (ulfc@thepuffingroup.com) has been working on this, as well.
> apparently he has made a number of packages already (he helped port linux
> to the sgi) - you may wish to contact him. he can't upload his packages,
> since he is not yet a developer. however, even when i sign his PGP key
> at OLS this week, he'll have to go through new-maintainer....
Right - He is doing mips(eb) (Big Endian) but i have Decstations
which are pure little endian.
I also started to make packages (ncurses, sysvinit etc) but i tried
to do native compiling on the decstation so the dependencies are
broken in the first stage packages.
I thought of compiling the first stage binarys from base, then boot
again and build 2nd Stage binarys with correct dependencies.
I am missing basic packages right now, like glibc2.0, dpkg etc ...
I am currently not even able to build dpkg as libtool etc have a "source
dependency" on "makeinfo" which i currently do not have ... :)
Flo
--
Florian Lohoff flo@rfc822.org +49-5241-470566
Good, Fast, Cheap: Pick any two (you can't have all three). (RFC 1925)
Reply to: