From: Hamish Moffatt <hamish@cloud.net.au>
To: linux-hams@vger.kernel.org
Subject: Re: SPLAT ...
Date: Fri, 28 Jun 2002 00:30:47 +1000 [thread overview]
Message-ID: <20020627143047.GA6878@silly.cloud.net.au> (raw)
In-Reply-To: <200206271358.g5RDw3X08658@amsat.org>
On Thu, Jun 27, 2002 at 06:58:03AM -0700, John A. Magliacane wrote:
> Someone running Red Hat 6.2 had a similar problem with the install scripts.
> It was cured by changing the '==' tests to '='. I'm not sure why this was
> necessary.
Sounds like a broken shell?
> As far as the bzip2 libraries are concerned, I'm pretty sure you need
> libbz2.so under /usr/lib in addition to libbz2.a. If you don't have it,
> my suggestion is to install libbz2 from source instead of an RPM.
libbz2.a should be sufficient to link statically.
Cheers,
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2002-06-27 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 13:58 SPLAT John A. Magliacane
2002-06-27 14:30 ` Hamish Moffatt [this message]
2002-06-27 18:51 ` SPLAT terry
2002-06-27 19:03 ` SPLAT Iain Young - G7III
2002-06-27 22:02 ` SPLAT Riley Williams
-- strict thread matches above, loose matches on Subject: below --
2002-06-27 12:57 SPLAT terry
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=20020627143047.GA6878@silly.cloud.net.au \
--to=hamish@cloud.net.au \
--cc=linux-hams@vger.kernel.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