From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Michael Somos <somos@grail.cba.csuohio.edu>
Cc: git@vger.kernel.org
Subject: Re: git-1.4.0 make problems
Date: Sat, 17 Jun 2006 08:58:24 +0200 [thread overview]
Message-ID: <4493A810.6010706@lsrfire.ath.cx> (raw)
In-Reply-To: <200606170218.k5H2I0o0003192@grail.cba.csuohio.edu>
| I downloaded the git-1.4.0.tar.bz2 recently and encountered a few
| problems.
|
| 1) The untar process creates a stray file "pax_global_header".
| I am using GNU tar v1.13.22 and I get this message :
|
| ======================================================================
| > tar jxf ~/u/source/git-1.4.0.tar.bz2
| tar: pax_global_header: Unknown file type 'g', extracted as normal
| file
| ======================================================================
You can ignore or delete that file. It is a pax extended global header,
containing the git commit ID as a comment. GNU tar started supporting
pax headers with version 1.13.93 (released 2004-02-23). Version 1.13.22
was released on 2001-08-29, by the way. May I ask what operating system
and version you are using?
| 2) The make install process ignores the "prefix=..." argument. I have
| to comment out one line for this :
|
| ======================================================================
| > diff Makefile git-1.4.0/
| 94c94
| < #prefix = $(HOME)
| ---
| > prefix = $(HOME)
| ======================================================================
It took me a while to realize that your diffs are reversed. It's too
early for me, I think I'll go to bed again. :)
Anyway, prefix handling is currently being worked on. Yakov Lerner sent
a patch which seems to make make do what you need.
| 3) The make has a problem with "expat" include and libararies.
| I have to add more lines to the Makefile to handle this like some
| of the other include and libraries :
|
| ======================================================================
| 351,358c351
| < endif
| <
| < ifndef NO_EXPAT
| < ifdef EXPATDIR
| < # This is still problematic -- gcc does not always want -R.
| < ALL_CFLAGS += -I$(EXPATDIR)/include
| < EXPAT_LIBEXPAT = -L$(EXPATDIR)/lib -R$(EXPATDIR)/lib -lexpat
|
| < else
| ---
| > ifndef NO_EXPAT
| 360c353
| < endif
| ---
| > endif
| ======================================================================
Looks sensible, except for the formatting.
| Other than that, it installed okay. I will have to read the docs and
| use it to see how it goes otherwise.
A good first exercise would be to fetch the git repository, edit Makefile
and commit your change, and then send a patch to this list -- all using
git (except the editing part). :-) Care to try that? Please let us know
of any difficulties you may encounter.
Thanks,
René
next prev parent reply other threads:[~2006-06-17 6:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 2:18 git-1.4.0 make problems Michael Somos
2006-06-17 6:58 ` Rene Scharfe [this message]
2006-06-17 20:56 ` Junio C Hamano
2006-06-17 21:55 ` Rene Scharfe
2006-06-17 22:40 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-06-17 10:16 Michael Somos
2006-06-17 13:09 ` Dennis Stosberg
2006-06-17 22:11 ` Rene Scharfe
2006-06-17 14:46 Michael Somos
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=4493A810.6010706@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=somos@grail.cba.csuohio.edu \
/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.