All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Greg <greggallen@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git, Parrot, Perl6, Rakudo for G4 MAC
Date: Wed, 16 Nov 2011 16:35:29 +0100	[thread overview]
Message-ID: <4EC3D841.1050805@web.de> (raw)
In-Reply-To: <loom.20111115T112500-386@post.gmane.org>

Hej,
you actually don't need perl, if I remember my experimenta with git under
G4 MAC PPC right.

See the Makefile:
# Define NO_PERL if you do not want Perl scripts or libraries at all

And, if I remember it right, git (the selfe compiled) stopped
working after 1.7.0 or so.
I didn't do a bisect, since that machine runs linux most of the time.
/Torsten



On 15.11.11 11:36, Greg wrote:
> Howdy:
> 
> 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!
> 
> I'd like to start messing with this while I'm waiting for my Debian
>  Linux box to be returned. (A friend 
> borrowed it to do some work:  
> He installed a horribly virulent bug called WInBlows XP!!!!)  
> 
> I already have Perl5.10.1 working fine, and performing 
> numerous marvelous tasks, so I (perhaps 
> mistakenly) thought it would be an easy addition.
> 
> 
> Cheers,
> 
> Greg
> 
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2011-11-16 15:41 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
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 [this message]

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=4EC3D841.1050805@web.de \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=greggallen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.