git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Junio C Hamano <junkio@cox.net>
Cc: Petr Baudis <pasky@suse.cz>, git@vger.kernel.org
Subject: Re: [PATCH] Introduce Git.pm (v3)
Date: Fri, 23 Jun 2006 06:04:17 -0600	[thread overview]
Message-ID: <m1k678yt6m.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <7vejxgckq9.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri, 23 Jun 2006 01:57:50 -0700")

Junio C Hamano <junkio@cox.net> writes:

> Petr Baudis <pasky@suse.cz> writes:
>
>> Also, is there any real problem with just using -fPIC?
>
> Personally, not really, but I consider it a workaround having to
> compile with -fPIC (being able to compile with -fPIC is a
> feature).
>
> Doesn't it have performance implications to use -fPIC when you
> do not have to?
>
> By the way, you also need to adjust the testsuite so that it
> finds the Perl modules from freshly built tree before
> installing.  I think (but haven't checked yet) the stuff written
> in Python does that already, so you might want to mimic it.

So what was being compiled was a shared Git.so.

32bit x86 is on of the few architectures that allows you to build
a .so without compiling with -fPIC.  

The question is why are we building with a .so?

Eric

  reply	other threads:[~2006-06-23 12:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 22:02 [PATCH] Introduce Git.pm (v3) Petr Baudis
2006-06-22 23:18 ` Junio C Hamano
2006-06-22 23:50   ` Petr Baudis
2006-06-23  0:22     ` Junio C Hamano
2006-06-23  1:12       ` Petr Baudis
2006-06-23  4:41         ` Junio C Hamano
2006-06-23  6:03           ` Jakub Narebski
2006-06-23  6:34             ` Nguyễn Thái Ngọc Duy
2006-06-23 12:45             ` Petr Baudis
2006-06-26 23:20               ` Jakub Narebski
2006-06-23  8:57         ` Junio C Hamano
2006-06-23 12:04           ` Eric W. Biederman [this message]
2006-06-23 12:39     ` Petr Baudis
2006-06-24  0:39       ` Junio C Hamano
2006-06-24  1:01       ` Junio C Hamano
2006-06-24  1:07         ` Junio C Hamano
2006-06-24 20:10           ` Johannes Schindelin
2006-06-25  1:20             ` Junio C Hamano
2006-06-25  1:54               ` Johannes Schindelin
2006-06-24  1:04       ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1k678yt6m.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=pasky@suse.cz \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).