From: Tor Arntsen <tor@spacetec.no>
To: Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add Tru64/OSF1 support in Makefile
Date: Fri, 2 Apr 2010 16:07:39 +0200 [thread overview]
Message-ID: <u2ld2d39d861004020707m7577182et40b4cd6b93bae830@mail.gmail.com> (raw)
In-Reply-To: <DA8Or5TA0_betHA0BMcLIT0so7oVjDK6CYr4x1LCiX60SEmuPqVnXg@cipher.nrlssc.navy.mil>
On Wed, Mar 31, 2010 at 18:29, Brandon Casey
<brandon.casey.ctr@nrlssc.navy.mil> wrote:
> On 03/30/2010 01:22 PM, Tor Arntsen wrote:
>> This patch to Makefile makes git build for me on Tru64/OSF1 V5.1 with
>> the native compiler.
[..]
>> +ifeq ($(uname_S),OSF1)
>> + # Tested with V5.1 w/libcurl and zlib-1.1.4-5 in /usr/local/
>> + CC = cc
>> + CFLAGS = -O2 -g3
>
> I wonder if the native compiler will be the most common compiler
> used on this platform? I tend to lean towards configuring the
> Makefile for gcc, unless gcc is not available for a platform. The
> user can set CC and CFLAGS in config.mak and on the make command
> line if they desire something different.
>
> This isn't an objection by me, I'm just mentioning it to bring
> attention to the issue in case others think it is worthy for
> git to have a stated policy one way or the other.
I'm not certain. I do in fact have gcc (3.3) installed on this Tru64
box, but it doesn't seem to be part of the original 'freeware' CD that
used to come with Tru64. Besides, the freeware CD was first removed as
physical CD, and later (two or three years ago, apparently) pulled by
HP from the online download which was used by their 'tachometer'
('apt-get'-like) freeware tool. Tru64 V51B (which seems to be the
latest, there's no 5.2 as I originally thought) is still available for
download, and so is the native compiler. As far as I can tell it's
incredibly difficult to find precompiled freeware/oss packages for
Tru64 anymore.
>> + SHELL_PATH = /bin/ksh
>
> Can you run the test suite with this ksh? If it suffers from
> the same exit status behavior of ksh on IRIX and SunOS, then
> I have a patch which allows the test suite to run.
Good idea. I'll do that, and maybe that would indicate if there are
issues with using the native compiler as well.
> Also, I wonder if it suffers from the same trap handling that
> ksh has on SunOS.
[..]
I tested that snippet you provided, and it exits with 0 on Tru64 (I
also verified that indeed it doesn't on Solaris 10).
>> + BASIC_CFLAGS += -D_POSIX_C_SOURCE=1 -D_OSF_SOURCE=1
>> + BASIC_CFLAGS += -pthread
>
> There is a PTHREAD_LIBS variable and it seems there is precedent
> for setting it to -pthread in the FreeBSD section.
Right, I can do it similarly in my next version of the patch. Thanks
for your comments!
-Tor
next prev parent reply other threads:[~2010-04-02 14:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 18:22 [PATCH] Add Tru64/OSF1 support in Makefile Tor Arntsen
2010-03-30 23:54 ` Junio C Hamano
2010-03-31 8:45 ` Tor Arntsen
2010-03-31 16:29 ` Brandon Casey
2010-04-01 15:47 ` Brandon Casey
2010-04-02 14:07 ` Tor Arntsen [this message]
2010-04-02 14:56 ` Brandon Casey
2010-04-02 15:12 ` Tor Arntsen
2010-04-02 15:39 ` [PATCH WIP] t/test-lib.sh: support Korn shell by converting GIT_EXIT_OK to GIT_EXIT_CODE Brandon Casey
2010-04-23 14:59 ` [PATCH] Add Tru64/OSF1 support in Makefile Tor Arntsen
2010-05-21 20:45 ` Brandon Casey
2010-05-26 8:19 ` Tor Arntsen
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=u2ld2d39d861004020707m7577182et40b4cd6b93bae830@mail.gmail.com \
--to=tor@spacetec.no \
--cc=brandon.casey.ctr@nrlssc.navy.mil \
--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).