From: andi <andi@fischlustig.de>
To: andi <andi@fischlustig.de>
Cc: Matt Taggart <taggart@carmen.fc.hp.com>,
parisc-linux@parisc-linux.org, debian-hppa@lists.debian.org
Subject: Re: [parisc-linux] WARNING: DO NOT APT-GET UPGRADE HPPA
Date: 28 Oct 2001 02:38:04 +0100 [thread overview]
Message-ID: <1004233084.1307.6.camel@cube> (raw)
In-Reply-To: <1004225524.624.6.camel@cube>
On Sun, 2001-10-28 at 01:32, andi wrote:
> On Fri, 2001-10-26 at 20:27, Matt Taggart wrote:
> > As PeteM and others have discovered, upgrading your hppa box currently breaks
> > a *lot*.
>
>
> Every program that is linked agains gtk+ segfaults, no matter if it uses
> gtk or not. It seems to be a linker problem.
2.2.4-4 fixes that problem. python however is still broken.
andi
next prev parent reply other threads:[~2001-10-28 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 18:27 [parisc-linux] WARNING: DO NOT APT-GET UPGRADE HPPA Matt Taggart
2001-10-27 10:01 ` [parisc-linux] " Peter Mottram
2001-10-27 23:32 ` [parisc-linux] " andi
2001-10-28 1:38 ` andi [this message]
[not found] ` <20011031202107.A2654@alpha.of.nowhere>
2001-10-31 20:07 ` Matt Taggart
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=1004233084.1307.6.camel@cube \
--to=andi@fischlustig.de \
--cc=debian-hppa@lists.debian.org \
--cc=parisc-linux@parisc-linux.org \
--cc=taggart@carmen.fc.hp.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