From: Michael J Gruber <git@drmicha•warpmail.net>
To: "H.Merijn Brand" <h.m.brand@xs4all•nl>
Cc: Jeff King <peff@peff•net>, Junio C Hamano <gitster@pobox•com>,
git@vger•kernel.org
Subject: Re: Interested in helping open source friends on HP-UX?
Date: Tue, 03 Mar 2015 17:05:53 +0100 [thread overview]
Message-ID: <54F5DBE1.6080004@drmicha.warpmail.net> (raw)
In-Reply-To: <20150303163042.655fe00c@pc09.procura.nl>
H.Merijn Brand venit, vidit, dixit 03.03.2015 16:30:
> On Tue, 03 Mar 2015 15:55:48 +0100, Michael J Gruber
> <git@drmicha•warpmail.net> wrote:
>
>> H.Merijn Brand venit, vidit, dixit 19.02.2015 19:56:
>>> On Thu, 19 Feb 2015 14:21:11 +0100, Michael J Gruber
>>> <git@drmicha•warpmail.net> wrote:
>>>
>>>> Jeff, you got it wrong. You should do the hard part and leave the easy
>>>> part to us!
>>>>
>>>> Thanks anyways, I'll add this to my HP_UX branch.
>>>
>>> I did not mention this in earlier mails. When using the HP C-ANSI-C
>>> compiler, MAX_INT is not set.
>>>
>>> I had to add
>>> --8<---
>>> #ifndef SIZE_MAX
>>> # define SIZE_MAX (18446744073709551615UL)
>>> /* define SIZE_MAX (4294967295U) */
>>> # endif
>>> -->8---
>>>
>>> to these files
>>>
>>> sha1_file.c
>>> utf8.c
>>> walker.c
>>> wrapper.c
>>>
>>> And yes, that could be dynamic and probably be in another header file
>>>
>>
>> In compat/regex/regex_internal.h we have
>>
>> /* For loser systems without the definition. */
>> #ifndef SIZE_MAX
>> # define SIZE_MAX ((size_t) -1)
>> #endif
>>
>> Does this work in your environment?
>
> I think it does:
>
> make
> CC sha1_file.o
> CC utf8.o
> CC walker.o
> "walker.c", line 119: warning #4232-D: conversion from "struct object *" to a
> more strictly aligned type "struct commit *" may cause misaligned
> access
> if (process_commit(walker, (struct commit *)obj))
> ^
>
> "walker.c", line 124: warning #4232-D: conversion from "struct object *" to a
> more strictly aligned type "struct tree *" may cause misaligned
> access
> if (process_tree(walker, (struct tree *)obj))
> ^
>
> "walker.c", line 132: warning #4232-D: conversion from "struct object *" to a
> more strictly aligned type "struct tag *" may cause misaligned access
> if (process_tag(walker, (struct tag *)obj))
> ^
>
> CC wrapper.o
> AR libgit.a
>
>
Hmmh. Did you get these same warnings with the fix you had before? They
don't make feel that confident...
>> [Trying to not let this fall into oblivion...]
>
> Much appreciated!
>
>> Michael
>
>
next prev parent reply other threads:[~2015-03-03 16:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 7:46 Interested in helping open source friends on HP-UX? Junio C Hamano
2015-02-18 16:00 ` H.Merijn Brand
2015-02-18 17:46 ` Michael J Gruber
2015-02-18 18:25 ` Jeff King
2015-02-18 18:47 ` Junio C Hamano
2015-02-18 18:57 ` Jeff King
2015-02-19 10:33 ` Michael J Gruber
2015-02-19 11:14 ` H.Merijn Brand
2015-02-19 11:20 ` Michael J Gruber
2015-02-19 12:54 ` Jeff King
2015-02-19 13:21 ` Michael J Gruber
2015-02-19 18:56 ` H.Merijn Brand
2015-03-03 14:55 ` Michael J Gruber
2015-03-03 15:30 ` H.Merijn Brand
2015-03-03 16:05 ` Michael J Gruber [this message]
2015-03-03 22:25 ` H.Merijn Brand
2015-02-20 1:48 ` Jeff King
2015-02-20 10:36 ` Michael J Gruber
2015-02-20 10:49 ` Jeff King
2015-02-20 11:24 ` H.Merijn Brand
2015-02-18 19:22 ` H.Merijn Brand
2015-02-18 19:20 ` H.Merijn Brand
2015-02-21 23:31 ` David Aguilar
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=54F5DBE1.6080004@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=h.m.brand@xs4all$(echo .)nl \
--cc=peff@peff$(echo .)net \
/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