From: Jeffrey A Law <law@cygnus.com>
To: Julian Seward <Julian_Seward@muraroa.demon.co.uk>
Cc: egcs@cygnus.com
Subject: Re: egcs & bzip2
Date: Sat, 28 Nov 1998 18:42:00 -0000 [thread overview]
Message-ID: <26031.912304530@hurl.cygnus.com> (raw)
In-Reply-To: <34899AD1.9FE2C90C@muraroa.demon.co.uk>
Going through some old mail... Found this...
In message <34899AD1.9FE2C90C@muraroa.demon.co.uk>you write:
> I was pleased to see you using bzip2 to distribute it. A couple
> of small things, re your page
> ftp://ftp.cygnus.com/pub/egcs/releases/index.html:
>
> -- Perhaps put a link to http://www.muraroa.demon.co.uk
> where people can pick up pre-compiled versions? Or mirror
> them yourself? Saves people the hassle of compiling it,
> at least for some platforms.
We did this a month or so ago -- we now link to the bzip2 home page.
> -- I was alarmed to read: "gcc-2.7 for linux will mis-compile bzip2
> if you use the optimizer; make sure to turn off the optimizer when
> building bzip2 with gcc-2.7."
>
> Can you be a little more specific? Is this gcc-2.7.0, or 2.7.X, or
> what? I've bzip2'd several thousand MB on x86-linux with 2.7.2
> with no problems at all. I presume it works ok on egcs-1.0 :-)
I don't remember the details -- basically we couldn't bzip2, then bunzip2 the
egcs-1.0 distribution :(
We haven't had any trouble with the newer versions of bzip as far as I know.
jeff
next prev parent reply other threads:[~1998-11-28 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-06 10:32 Julian Seward
1998-11-28 18:42 ` Jeffrey A Law [this message]
[not found] <twk9diurcl.fsf@penalty.cygnus.com>
1997-12-06 13:16 ` Jason Molenda
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=26031.912304530@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=Julian_Seward@muraroa.demon.co.uk \
--cc=egcs@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).