Re: Some packages (finally)
On Mon, Jul 19, 1999 at 11:41:43AM +0200, Florian Lohoff wrote:
> On Sun, Jul 18, 1999 at 07:20:19PM -0400, Ulf Carlsson wrote:
> >
> > I have built a couple of packages now, most of them from base:
> >
> > adduser_3.8_all.deb libreadlineg2-dbg_2.1-13.3_mips.deb
> > base-files_2.1.0_all.deb libreadlineg2-dev_2.1-13.3_mips.deb
> > base-passwd_2.0.3.3_mips.deb libreadlineg2_2.1-13.3_mips.deb
> > bash-builtins_2.02.1-1.4_mips.deb makedev_2.3.1-19_all.deb
> > bash_2.02.1-1.4_mips.deb mount_2.8a-2_mips.deb
> > bsdutils_4.4.1.1_mips.deb mount_2.9g-6_mips.deb
> > fileutils_3.16-5.4_mips.deb ncurses-base_4.2-3_all.deb
> > findutils_4.1-33_mips.deb ncurses-bin_4.2-3_mips.deb
> > grep_2.2-1_mips.deb ncurses-term_4.2-3_all.deb
> > gzip_1.2.4-28_mips.deb sed_3.02-1_mips.deb
> > hostname_2.04_mips.deb sysklogd_1.3-31_mips.deb
> > kbd-data_0.96a-14_all.deb sysvinit_2.76-3_mips.deb
> > kbd_0.96a-14_mips.deb tar_1.12-7_mips.deb
> > libncurses4-dbg_4.2-3_mips.deb textutils_1.22-2.4_mips.deb
> > libncurses4-dev_4.2-3_mips.deb update_1.3-2_mips.deb
> > libncurses4_4.2-3_mips.deb util-linux_2.9g-6_mips.deb
> >
> > I have dpkg built as well, but I lack some sgml tools so I can't build the
> > .deb at the moment. I'll do that tomorrow or something.
> >
> > I'll also check if I can actually use these packages or if I've just wasted
> > a lot of time :-). Maybe I can upload them somewhere if you want to try
> > them.
>
> Ops - It seems the architecture is wrong. I think there was a discussion were
> we will possibly have mipsel and mipseb (Both Big and Little endian)
>
> I started to make "mipsel" binarys as i have 2 Decstations which are both
> little endian...
I think the convention is:
mips = big endian
mipsel = little endian
These packages I've built are for big endian MIPS machines. Maybe I should have
compiled for both mips and mipsel, so that we can get two ports. It wouldn't be
much problem to build mipsel at the same time as I build mips, I'd just have to
type dpkg-buildpackage one more time. I have to compile new set of glibc, egcs
and binutils first though. It would be pointless to have one person working on
mips and one person on mipsel. We would probably have to make the same changes,
thus duplicating work.
This is from the Linux/MIPS HOWTO:
---->8----8<--------->8----8<--------->8----8<-----
9.5 Configuration names
Many of the packages based on autoconf support many different
architectures and operating systems. In order to differentiate between
these many configurations, names are constructed with
<cpu>-<company>-<os> or even <cpu>-<company>-<kernel>-<os>. Expressed
this way the configuration names of Linux/MIPS are
mips-unknown-linux-gnu for big endian targets or
mipsel-unknown-linux-gnu for little endian targets. These names are a
bit long and are allowed to be abbreviated to mips-linux or
mipsel-linux. You must use the same configuration name for all
packages that comprise your crosscompilation environment. Also, while
other names like mips-sni-linux or mipsel-sni-linux are legal
configuration names, use mips-linux or mipsel-linux instead; these are
the configuration names known to other packages like the Linux kernel
sources and they'd otherwise have to be changed for crosscompilation.
---->8----8<--------->8----8<--------->8----8<-----
I would have to tweak a some things to make dpkg-buildpackage -a build the
packages to have the name mipseb (since the tools have the prefix mips-linux and
not mipseb-linux) but if you have a nice solution and find it necessary, I can
certainly change it.
Regards,
Ulf
Reply to: