public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu•org>
To: Jakub Narebski <jnareb@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] Makefile: set USE_PIC on Linux x86_64 for linking with Git.pm
Date: Thu, 29 Jun 2006 20:03:00 -0400	[thread overview]
Message-ID: <1151625780.10358.13.camel@dv> (raw)
In-Reply-To: <e81jr5$l1c$1@sea.gmane.org>

Hi, Jakub!

I don't have the newsgroup access, so I'm copying to the mailing list
instead.

On Fri, 2006-06-30 at 00:22 +0200, Jakub Narebski wrote:

> If I remember correctly everybody agreed that autoconf is least evil of the
> whole autotools package.

Sort of.  Some people were less dismissive than others.

>  pasky suggested to write ./configure script by
> hand on #git...

That's probably not a good idea.  Autoconf can do this very well if used
correctly.  And I'm ready to help when it comes to correctness.

> I'm trying to do inobtrusive _optional_ autoconf support in the patch series
> beginning with
>   Message-ID: <200606290301.51657.jnareb@gmail•com>
>   http://permalink.gmane.org/gmane.comp.version-control.git/22832

The problem with optional support is that you suddenly have two
alternative mechanisms to adjust the build to the system, and both
should be kept in a  working condition.  But it's a good first step.

> Please wait for the patch moving ./autoconf output away from config.mak
> (as some people here requested), and do contribute! My autoconf/m4
> experience is nonexistent (I'm learning it as I go). See comments in the
> third [PATCH/RFC] in series.
> 
> BTW. patches are against master.

The link doesn't show the "@" characters correctly.  Maybe somebody
could establish a git repository?  Ideally, the autoconf changes should
go to one of the Git branches.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2006-06-30  0:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 18:35 [PATCH] Makefile: set USE_PIC on Linux x86_64 for linking with Git.pm Marco Roeland
2006-06-28 18:53 ` Junio C Hamano
2006-06-28 18:59   ` Junio C Hamano
2006-06-28 19:21     ` Marco Roeland
2006-06-28 19:55       ` [PATCH] Makefile: set USE_PIC on Linux x86_64 for linking with Git.xs Marco Roeland
2006-06-28 20:52       ` [PATCH] Makefile: set USE_PIC on Linux x86_64 for linking with Git.pm Pavel Roskin
2006-06-29 22:22         ` Jakub Narebski
2006-06-30  0:03           ` Pavel Roskin [this message]
2006-06-30  0:29             ` Jakub Narebski
2006-06-28 19:08   ` Marco Roeland
2006-06-28 21:24     ` Junio C Hamano
2006-06-29  9:04       ` Sergey Vlasov
2006-06-29  9:58         ` Josef Weidendorfer

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=1151625780.10358.13.camel@dv \
    --to=proski@gnu$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    --cc=jnareb@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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