Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: parisc-linux@parisc-linux.org
Cc: bcollins@debian.org, chris@debian.org
Subject: [parisc-linux] hppa binutils/glibc updates
Date: Sat, 3 Nov 2001 23:33:52 -0800	[thread overview]
Message-ID: <20011103233352.F505@tausq.org> (raw)

Some good news, I hope....

With latest patches from Alan Modra, things seem to be looking better.
Here's what I've tried:

In a chroot built with debootstrap plus build-essential:
- Rebuild binutils from sourceware cvs
- Using new binutils, rebuild glibc (2.2.4-5) with am's latest patch

With these bits installed, the following were tested:
- build and install wget (just a simple sanity test)
- install and run libgtk1.2 and gkrellm
- recompile and run python1.5 and apache

all these seem to be ok now. Before recompiling, things like python will
die with a SIGILL

I've made a list of all the packages that got uploaded between around
Oct 15 till now. All these need to be recompiled and binary-NMU's need to
be made. James/LaMont/Bdale/myself/etc can do these fairly easily with
sbuild after new binutils and glibc bits are uploaded. Hopefully we can also
restart the buildd after that.

Chris/Ben: can you let us know when we can expect new binutils/glibc?
I'll forward the glibc patch to Ben separately.

If you can think of anything else that we should try to make sure
everything works, please let us know.

fingers crossed,
randolph
-- 
   @..@                                         http://www.TauSq.org/
  (----)
 ( >__< )
 ^^ ~~ ^^

             reply	other threads:[~2001-11-04  7:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-04  7:33 Randolph Chung [this message]
2001-11-04 11:20 ` [parisc-linux] hppa binutils/glibc updates Albert Strasheim
2001-11-04 15:23   ` Randolph Chung
2001-11-04 16:11     ` Albert Strasheim
2001-11-04 16:50       ` Matthew Wilcox
2001-11-05  2:10 ` [parisc-linux] " Christopher C. Chimelis
2001-11-05  2:29   ` Matthew Wilcox
2001-11-05  2:40     ` Christopher C. Chimelis
2001-11-05  2:49       ` Matthew Wilcox
2001-11-05  6:37         ` Christopher C. Chimelis
2001-11-06  5:42           ` Randolph Chung
2001-11-06  8:16             ` Albert Strasheim
2001-11-06 13:23               ` Albert Strasheim
2001-11-06 13:54                 ` Albert Strasheim
2001-11-06 13:57                   ` Albert Strasheim
2001-11-06 14:36                   ` Matthew Wilcox
2001-11-06 16:16                     ` Richard Hirst
2001-11-06 19:24                       ` Richard Hirst
2001-11-06 19:51                         ` Albert Strasheim
2001-11-06 22:38                           ` Albert Strasheim
2001-11-07  9:36                             ` Richard Hirst
2001-11-06 13:11             ` Thomas Marteau
2001-11-06 13:17               ` Nathan Neulinger
2001-11-06 13:17                 ` Thomas Marteau
2001-11-06 14:00                   ` Kaj-Michael Lang
2001-11-06 13:24               ` Christopher C. Chimelis
2001-11-05  2:52     ` [parisc-linux] Re: FW SCSI (Was hppa binutils/glibc updates) Daniel Williams

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=20011103233352.F505@tausq.org \
    --to=randolph@tausq.org \
    --cc=bcollins@debian.org \
    --cc=chris@debian.org \
    --cc=parisc-linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox