Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: linux-mips@oss.sgi.com
Subject: Re: base.tgz
Date: Tue, 17 Oct 2000 16:27:24 +0200	[thread overview]
Message-ID: <20001017162724.H4890@paradigm.rfc822.org> (raw)
In-Reply-To: <20001017041449.A17546@lug-owl.de>; from jbglaw@lug-owl.de on Tue, Oct 17, 2000 at 04:14:50AM +0200

On Tue, Oct 17, 2000 at 04:14:50AM +0200, Jan-Benedict Glaw wrote:

> Packages which seem to be not used/useable. They'll not be included:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Package: console-tools-libs
> Package: fbset
> Package: fdflush
> Package: fdutils
> Package: isapnptools
> Package: lilo
> Package: mbr
> Package: pciutils
> Package: pump
> Package: syslinux
> Package: xviddetect
> Package: pcmcia-cs

We should include them without syslinux, lilo, mbr which
are i386 specific. All others might need some special
hacking ...

> Packages which are broken in some way right now:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Package: debconf-tiny (not found)
> Package: bsdutils (not found)
  from util-linux

> Package: libc6 (will use converted 206-5 rpm)
> Package: libnewt0 (not found, will use newt-0.40-9.rpm)
> Package: libstdc++2.10 (not found)

> Package: locales (not found)
 This is glibc ...

> Package: mount (not found, will take mount-2.9o-1.rpm)
  from util-linux
> Package: util-linux (not found, will take util-linux-2.7-19.rpm)
  from util-linux

The util-linux stuff is tricky - I have made a debian-mips package
from it using wesolows patches - The packages are at
ftp://ftp.rfc822.org/pub/local/debian-mips/temp-packages

One could easily build these for mipsel ...

Flo
-- 
Florian Lohoff		flo@rfc822.org		      	+49-5201-669912
      "Write only memory - Oops. Time for my medication again ..."

  parent reply	other threads:[~2000-10-17 14:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-16  2:33 base.tgz Jan-Benedict Glaw
2000-10-17  2:14 ` base.tgz Jan-Benedict Glaw
2000-10-17 11:20   ` base.tgz Geert Uytterhoeven
2000-10-17 14:27   ` Florian Lohoff [this message]
2000-10-17 15:35     ` base.tgz Jan-Benedict Glaw
2000-10-17 15:50       ` base.tgz Mike McDonald
2000-10-17 16:33         ` base.tgz Kevin D. Kissell
2000-10-17 16:33           ` base.tgz Kevin D. Kissell
2000-10-18  1:30       ` base.tgz Florian Lohoff
2000-10-18  2:12         ` base.tgz Ralf Baechle
2000-10-18 20:16   ` base.tgz Jan-Benedict Glaw

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20001017162724.H4890@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --cc=linux-mips@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox