On Fri, May 16, 2008 at 4:23 PM, Chris Frey <[EMAIL PROTECTED]> wrote:
> On Fri, May 16, 2008 at 12:12:27PM -0400, Chris Frey wrote:
>> I don't know any quick way around that
>
> Well, actually the quick way around that is to just run buildgen.sh
> on a newer machine and then tar it up and move it
On Fri, May 16, 2008 at 12:12:27PM -0400, Chris Frey wrote:
> I don't know any quick way around that
Well, actually the quick way around that is to just run buildgen.sh
on a newer machine and then tar it up and move it to your older machine,
but that depends on what you have available.
- Chris
On Fri, May 16, 2008 at 02:06:55PM +0200, Niels de Vos wrote:
> Hi,
>
> I'm trying to get bcharge recognise my Pearl 8100 (productId: 0x0006).
> Others were advised to compile bcharge from CVS. Unfortunately
> CentOS-5 (and it's rother Red Hat Enterprise) delivers autoconf-2.59.
> This seems to be
Hi,
I'm trying to get bcharge recognise my Pearl 8100 (productId: 0x0006).
Others were advised to compile bcharge from CVS. Unfortunately
CentOS-5 (and it's rother Red Hat Enterprise) delivers autoconf-2.59.
This seems to be to old for barry-cvs :(. It's easy for me to
recompile barry from a .srpm
