git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Duft <mduft@gentoo.org>
To: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/2] Add additional build options for Interix, and remove obsolete ones.
Date: Thu, 26 May 2011 08:29:13 +0200	[thread overview]
Message-ID: <4DDDF339.4000703@gentoo.org> (raw)
In-Reply-To: <1306332924-28587-2-git-send-email-mduft@gentoo.org>

On 05/25/11 16:15, mduft@gentoo.org wrote:

(sorry for actually replying to the wrong mail - wasn't subscribed to the list (but am now.))

>> The removed options are obsolete, because interix support now
>> depends on libsuacomp.
>
> and linkage with -lsuacomp happens automatically without any change in the
> Makefile for anybody?  Just asking, as I do not have an access to (nor any
> particular desire to get an access to) an Interix to figure it out myself,
> and the only think I care about in this patch is if it helps only your
> installation or it will help everybody who has Interix but not necessarily
> with the same set of additional configuration as you have.

Yes. suacomp installs itself as libc.{a,so}. Of course the path to the suacomp prefix needs to be told to the compiler. Without it, interix (at least the newer versions) are near unusable, because of a whole lot of bugs M$ won't fix (as usual...). Suacomp can be installed manually by whoever likes to, and is included in the Gentoo Prefix project automatically (which is my target). I guess without Gentoo Prefix there'd be another whole lot of things missing to build git anyway (haven't tried). Gentoo Prefix also automatically get's all paths right, etc.

Currently, suacomp is already required for things like coreutils, perl, python, openssh, findutils, etc., etc. to work correctly, if not build at all...

Hope that explains some, sorry for not doing so at first :)

Regards, Markus

>
>> Signed-off-by: Markus Duft <mduft <at> gentoo.org>

  parent reply	other threads:[~2011-05-26  6:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 14:15 [PATCH] Interix catch-ups for recent changes/releases mduft
2011-05-25 14:15 ` [PATCH 1/2] Add additional build options for Interix, and remove obsolete ones mduft
2011-05-25 17:51   ` Junio C Hamano
2011-05-26  6:29   ` Markus Duft [this message]
2011-05-26 18:06     ` Junio C Hamano
2011-05-25 14:15 ` [PATCH 2/2] Include unistd.h mduft
2011-05-25 18:30   ` Junio C Hamano
2011-05-25 20:37     ` Tor Arntsen
2011-05-25 21:00       ` Junio C Hamano
2011-05-25 21:52     ` Erik Faye-Lund
2011-05-26  2:20   ` Jonathan Nieder
2011-05-26 15:48     ` Junio C Hamano
2011-05-26 16:39       ` Jonathan Nieder
2011-05-30  6:51         ` Markus Duft
2011-06-15  9:31           ` Markus Duft
2011-06-15  9:48             ` Jonathan Nieder
2011-06-15 11:34               ` [PATCH] Update the Interix default build configuration mduft
2011-05-27  6:27   ` [PATCH 2/2] Include unistd.h Markus Duft

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=4DDDF339.4000703@gentoo.org \
    --to=mduft@gentoo.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).