All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] boot-floppies build status
Date: Sat, 23 Jun 2001 17:00:25 +0100	[thread overview]
Message-ID: <20010623170024.G14416@linuxcare.com> (raw)

Hi,
  I'm busy building new boot-floppies, and have run into sufficient
issues, that I thought I'd better write them down...

deboostrap, good news, I am using 0.1.13 with no local edits, but
it is not in the archive, so I built it myself.  pehc cvs is not
up to date atm.

slang...  to get rid of the problems with slang.so references I had
to

build and install slang1, slang1-dev, slang1-pic
build and install libnewt0, libnewt-dev, libnewt-pic
build and install whiptail
build and install util-linux
build nano-tiny

NOTE when building slang I hacked the rules file to specify
--host=hppa-linux on the configure line - apparently it builds a
broken pkg if you don't do that.

I needed groff-base, which isn't in the archive, so had to build it.

boot-floppies depended on a newer version of libbogl-dev than was in
the archive, so I had to build that.

I tried to build the latest busybox, but failed.  conflicting types for
blah blah blah.

The new dpkg-dev 1.9.12 seems broken; with that installed
apt-get -b source foo fails because it doesn't like the directory
foo is unpacked in to (expects base-config, gets base-config-1.0.8, or
similar).

Building util-linux had problems, maybe due to dpkg-dev, I think
debian/rules probably didn't have execute permissions.

I had trouble upgrading my box because I already had an apt 0.5.3.0.90,
which was taken as newer than the fixed one, 0.5.3.  Guess I got that
from pehc somewhere.

I'm now using boot-floppies source from debian cvs, with a couple of
local hacks to avoid library reduction and reduce language set, just
to speed up the build.  Also an edit to dbootstrap.h to default to
sid rather than woody.  That edit is in pehc cvs, but otherwise pehc cvs
needs bringing in to sync again.

I had whiptail crashing after upgrading to latest slang/newt/whiptail
from the archive, but having installed my own built pkgs that problem
seems to have gone away.

I tried to remove libstdc++3.0, but we still have things depending on
it:

slab:~# dpkg --remove libstdc++3.0
dpkg: dependency problems prevent removal of libstdc++3.0:
 tetex-bin depends on libstdc++3.0.
 telnet depends on libstdc++3.0.

telnet is part of base, so I had to build a new telnet.

An attempt to upgrade my system reports:
The following packages have been kept back
  debconf debhelper perl-modules 

but that isn't causing me a problem at the moment.

Known outstanding ussues:

keyboard generates 'unknown scancode 7f' for various keys, eg. capslock,
'|' on a uk keyboard.

Lines round dialog boxes use the wrong chars for serial console, or don't
exist for sti consoles.  Varies between stage 1 and 2 of install.  May be
better with my rebuilt newt/slang/whiptail stuff.  We'll see.

Kernel configs need ps/2 mouse support adding (Helge said he would, havn't
checked).

Kernel needs serial patch from Clement.

Kernel configs might need sound/harmony adding.  32 bit only?  Modules?

Last night an install on my 712 broke during 2nd stage, ran to the
end, but had never asked for root password, or to create a user, etc.
Some perl errors flashed by.  Date was 1970... Will try with the newer
stuff tonight.

Should we be building kernel-images optimised for each cpu type, like
x86 do -386, -486, -586, etc?

So, now b-f builds, and debootstrap seems happy with the pkgs in my
new base tree.  I'll see if it actually works later tonight.

Richard

             reply	other threads:[~2001-06-23 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-23 16:00 Richard Hirst [this message]
2001-06-24  1:07 ` [parisc-linux] boot-floppies build status Richard Hirst
2001-06-24 15:21 ` Richard Hirst
2001-06-25 13:43 ` Richard Hirst

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=20010623170024.G14416@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.