From: Jakub Narebski <jnareb@gmail.com>
To: Hilco Wijbenga <hilco.wijbenga@gmail.com>
Cc: Greg <greggallen@gmail.com>, git@vger.kernel.org
Subject: Re: Git, Parrot, Perl6, Rakudo for G4 MAC
Date: Tue, 15 Nov 2011 10:12:11 -0800 (PST) [thread overview]
Message-ID: <m3fwhpmf1f.fsf@localhost.localdomain> (raw)
In-Reply-To: <CAE1pOi0fqzoz+Af8PaSORuW45UqDAEmqtKW3w4qYH-275BdUzw@mail.gmail.com>
Hilco Wijbenga <hilco.wijbenga@gmail.com> writes:
> On 15 November 2011 02:36, Greg <greggallen@gmail.com> wrote:
> > Could someone please assist me in locating the resources to "GIT"
> > this stuff going on a G4 MAC PPC? I
> > keep getting weird bugs.
> > Need me to be more explicit? Ok - it says gcc v3.3 isn't compatible, and a
> > bunch of other sheet!
Yes, you need to be more explicit. Please copy'n'paste exact error
messages that you get compiling Git.
>
> GCC 3.3 is from May 2003, I suggest you upgrade to a more recent GCC
> (probably 4.6).
I don't have experience compiling Git for PPC, but on i386 I can
compile Git without problems with gcc 4.0.2.
> > I already have Perl5.10.1 working fine, and performing
> > numerous marvelous tasks, so I (perhaps
> > mistakenly) thought it would be an easy addition.
>
> Perl 5.10.1 is from August 2009. Presumably less of a problem but,
> again, you should probably upgrade to something more recent.
Git requires Perl version 5.8 at least, so you should not have any
problems here.
--
Jakub Narębski
next prev parent reply other threads:[~2011-11-15 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 10:36 Git, Parrot, Perl6, Rakudo for G4 MAC Greg
2011-11-15 17:51 ` Hilco Wijbenga
2011-11-15 18:12 ` Jakub Narebski [this message]
2011-11-16 4:51 ` Sitaram Chamarty
2011-11-16 7:07 ` greggallen
2011-11-16 7:21 ` Jakub Narebski
2011-11-16 15:35 ` Torsten Bögershausen
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=m3fwhpmf1f.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=greggallen@gmail.com \
--cc=hilco.wijbenga@gmail.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 NNTP newsgroup(s).