From: "Andreas Färber" <andreas.faerber@web.de>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: diger <admin@freenet59.ru>,
git@vger.kernel.org,
HaikuPorts developers discussion list
<haikuports-devs@lists.ports.haiku-files.org>
Subject: Re: patch for fix build git on Haiku
Date: Sun, 24 Feb 2013 10:36:35 +0100 [thread overview]
Message-ID: <5129DF23.7050206@web.de> (raw)
In-Reply-To: <20130223204208.GB3222@elie.Belkin>
Hi,
Am 23.02.2013 21:42, schrieb Jonathan Nieder:
> diger wrote:
>
>> This patch fixes build git on Haiku
>
> Lovely. May we have your sign-off? (See
> Documentation/SubmittingPatches for what this means.) Does "make
> test" pass? (Just curious --- it's fine if it doesn't, though in that
> case a list of test failures would be helpful.)
>
> Thanks,
> Jonathan
>
> (patch left unsnipped for reference)
>
>> --- Makefile.orig 2012-10-21 21:32:15.000000000 +0000
>> +++ Makefile
>> @@ -1211,6 +1204,16 @@ ifeq ($(uname_S),HP-UX)
>> endif
>> GIT_TEST_CMP = cmp
>> endif
>> +ifeq ($(uname_S),Haiku)
>> + NO_R_TO_GCC_LINKER = YesPlease
>> + NO_LIBGEN_H = YesPlease
>> + NO_MEMMEM = YesPlease
>> + NO_MKSTEMPS = YesPlease
>> + NEEDS_LIBICONV = YesPlease
>> + DEFAULT_EDITOR = nano
Patch looks okay from what I have from my earlier ones in mind, but I
believe nano is an Optional Package on Haiku and thus not guaranteed to
be installed. CC'ing HaikuPorts.
Regards,
Andreas
>> + PTHREAD_LIBS = -lroot
>> + NO_CROSS_DIRECTORY_HARDLINKS = YesPlease
>> +endif
>> ifeq ($(uname_S),Windows)
>> GIT_VERSION := $(GIT_VERSION).MSVC
>> pathsep = ;
prev parent reply other threads:[~2013-02-24 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 15:13 patch for fix build git on Haiku diger
2013-02-23 20:42 ` Jonathan Nieder
2013-02-24 9:36 ` Andreas Färber [this message]
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=5129DF23.7050206@web.de \
--to=andreas.faerber@web.de \
--cc=admin@freenet59.ru \
--cc=git@vger.kernel.org \
--cc=haikuports-devs@lists.ports.haiku-files.org \
--cc=jrnieder@gmail.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 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.