git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Tim Schumacher <schumact@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Building GIT on older systems.
Date: Wed, 29 Feb 2012 15:55:10 -0500	[thread overview]
Message-ID: <20120229205510.GA628@sigill.intra.peff.net> (raw)
In-Reply-To: <CAFqtsHd=b=Ey8j1zTCC4-fut7rno3daQ2Q3HMs3k2SHFvE4dSQ@mail.gmail.com>

On Wed, Feb 29, 2012 at 01:22:21PM -0700, Tim Schumacher wrote:

> After a long battle trying to get git to compile on my dev boxes I am
> seeking help from the gurus...  I have an old system, redhat linux
> 7.3, with a 2.4.18 kernel with gcc 2.96 toolchain.  Unfortuneatly,
> upgrading is not currently an option.

That's pretty old, but I would think git should be build-able on it with
the right Makefile flags set. We build on even older versions of
Solaris.

> I have figured out so far that I can run the command
> 
> make NO_NSEC=true
> 
> to get past the time struct compile error.

As an aside, you can put definitions like this into config.mak, which is
read automatically by the Makefile. Then you don't have to specify them
on the command line for each 'make' invocation.

> After that, I was able to hand edit the Makefile to set
> 
> BASIC_LDFLAGS = -ldl
> 
> so linking the git-imap-send program succeeds (was failing to link
> against this library for some reason...). 

What was the link error? I don't know why imap-send would need to link
against -ldl. However, you should be able to just put -ldl into the
LDFLAGS on the command-line or in config.mak.

> I tried to run configure with these options, but it did not seem to
> take, only setting NO_NSEC=true to the make command line seems to
> work.

Was NO_NSEC set in the resulting config.mak.autogen?

> Anyway, now I get to the point in the build where it goes into the
> perl subdir and fails with:
> 
>    SUBDIR perl
> /bin/sh: -c: line 3: syntax error near unexpected token
> `"s<\Q++LOCALEDIR++\E></'
> /bin/sh: -c: line 3: `        -e "pm_to_blib({qw{Git/I18N.pm
> blib/lib/Git/I18N.pm private-Error.pm blib/lib/Error.pm Git.pm
> blib/lib/Git.pm}},'blib/lib/auto','/usr/bin/perl -pe
> "s<\Q++LOCALEDIR++\E></usr/local/git-1.7.9.2/share/locale>"')"'
> make[2]: *** [pm_to_blib] Error 2
> make[1]: *** [all] Error 2
> make: *** [all] Error 2

I haven't seen that before. The snippet mentioned in the error message
is actually written to the Makefile by Makefile.PL. Can you show us the
relevant part of the Makefile (i.e., the command that contains
"++LOCALEDIR++") so we can see if it's broken? My suspicion is that
there is an error in the generation of the Makefile by Makefile.PL.

Although your perl is so old the first step may be either to turn off
perl or upgrade to a newer version (see below).

> A couple questions I have so far:
> (1)  how can I make make output the actual command it is executing so
> I can try to debug things more quickly?

Doing "make V=1" will be more verbose. You can also use "make -d" to get
more output about which rules and commands are being followed, but its
output can be a bit overwhelming (and I don't think you have a make
problem, exactly).

> (2)  how can I configure the Makefile to automatically set -ldl as
> well as the NO_NSEC flag?

Put it in LDFLAGS.

> (3)  My perl -v output: This is perl, v5.6.1 built for i386-linux.  Is
> this sufficient?

These days we require at least 5.8, mostly because no developers are using 5.6
and support for it is bit-rotting. If your perl is that old, probably
setting NO_PERL is the best option. You will lose a few perl features
like interactive patch selection ("git add -p") and git-svn.

-Peff

  parent reply	other threads:[~2012-02-29 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFqtsHfrk89qHexg8VwMZnKwgWDqbseJNNKFSUkwDtVKX_t=5g@mail.gmail.com>
2012-02-29 20:22 ` Building GIT on older systems Tim Schumacher
2012-02-29 20:35   ` Dan Johnson
2012-02-29 20:55   ` Jeff King [this message]
2012-02-29 22:17     ` Tim Schumacher
2012-02-29 21:00   ` Junio C Hamano

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=20120229205510.GA628@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=schumact@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).