git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jupiter.hce@gmail.com
To: git@vger.kernel.org
Subject: Re: 1.7.10.3 configure does not generate Makefiles
Date: Mon, 4 Jun 2012 09:34:20 +1000	[thread overview]
Message-ID: <20120603233420.GA3002@gmail.com> (raw)
In-Reply-To: <CABPQNSZaNeu7n36_v_Xe26WHqtXNQWWXiPVutvVM7hk+q5S_-Q@mail.gmail.com>

I posted following comments on Forum many days ago, somehow, it was
pending for being accepted.Sorry if it is duplicated:

--- Attachement post on forum --

This post has NOT been accepted by the mailing list yet. 

In reply to this post by Erik Faye-Lund-2 

I thought I've sent the comments, but did not see on the forum, sorry
if it is duplicated. 

Thanks for all response. The Makefile is included in the source
directory, but I'd like to build the git in a separated build
directory, not the source directory. Is it possible to build the
git in a separated build directory? Or if there is any way to
geneerate a Makeifle in a separaed build directory? 

Thank you. 

Kind regards, 

hce

On 2012-05-30 13:38+0200, Erik Faye-Lund wrote:
>On Wed, May 30, 2012 at 1:32 AM,  <jupiter.hce@gmail.com> wrote:
>> Hi,
>>
>> I've just downloaded 1.7.10.3 source tarball and following the
>> instruction from INSTALL, I ran the autoconf to generate the
>> configure, then to run configure --prefix=/usr/local/git/1.7.10.3.
>> There were no errors but there was no Makefiles generated either. How
>> can I run the configure to generate Makefiles?
>>
>> .......
>> configure: creating ./config.status
>> config.status: creating config.mak.autogen
>>
>
>This is as expected. Git doesn't use Automake, only Autoconf. So all
>it generates is a config.mak.autogen, which gets included by the
>Makefile which is already present on the top-level.

-- 

  parent reply	other threads:[~2012-06-04 11:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29 23:32 1.7.10.3 configure does not generate Makefiles jupiter.hce
2012-05-30 11:38 ` Erik Faye-Lund
2012-06-01 11:48   ` hce
2012-06-03 23:34   ` jupiter.hce [this message]
2012-06-04 12:14     ` Vincent van Ravesteijn
2012-05-30 11:38 ` David Michael Barr

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=20120603233420.GA3002@gmail.com \
    --to=jupiter.hce@gmail.com \
    --cc=git@vger.kernel.org \
    /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).