From: Kevin Puetz <puetzk@iastate.edu>
To: Kevin Puetz <puetzk@iastate.edu>
Cc: linuxppc-dev@lists.linuxppc.org, debian-powerpc@lists.debian.org
Subject: Re: Updated Mozilla M13 Release Build Available
Date: Thu, 27 Jan 2000 23:47:59 -0600 [thread overview]
Message-ID: <E12E4GI-0001RX-00@puetz.penguinpowered.com> (raw)
In-Reply-To: Your message of "Thu, 27 Jan 2000 13:46:40 CST." <E12DusK-0007We-00@puetz.penguinpowered.com>
In response to the problems that some of you had with my Mozilla M13 build,
here is an updated one. If there are no problems with it now, it will be
submitted and I will announce when the mozilla.org tarball is up to date.
same place as last time, I just updated the file <http://www.public.iastate.edu
/~puetzk/>
You will need to go to ftp.linuxppc.com/linuxppc-1999/software/updates and get
libstdc++-2.10.0 (and, of course, any dependencies it has). You should not
need to use the funky ld-hack to make libelf.so anymore - if you did so,
delete it. You should not need to run this version as root before running it
as a normal user.
If anyone could verify that this runs fine, please email me so that I can get
mozilla.org's FTP site up to date.
As before, I'm not on the linuxppc-dev list, so please CC me.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-28 5:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-27 19:46 Mozilla M13 Release Build Available Kevin Puetz
2000-01-27 20:26 ` Nelson Abramson
2000-01-27 20:39 ` Hartmut Koptein
2000-01-28 5:47 ` Kevin Puetz [this message]
[not found] <Pine.LNX.4.10.10001280907150.2865-100000@xpol.uchicago.edu>
2000-01-28 15:38 ` Updated " Kevin Puetz
2000-01-28 17:56 ` Nelson Abramson
2000-01-28 19:19 ` Kevin Puetz
2000-01-28 20:47 ` Martin Costabel
2000-01-28 21:46 ` Nelson Abramson
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=E12E4GI-0001RX-00@puetz.penguinpowered.com \
--to=puetzk@iastate.edu \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).