From: Junio C Hamano <gitster@pobox.com>
To: "Haritha via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Kristoffer Haugsbakk <code@khaugsbakk.name>,
Haritha <harithamma.d@ibm.com>
Subject: Re: [PATCH v2 0/2] This PR enables a successful git build on z/OS.
Date: Thu, 22 Feb 2024 23:37:58 -0800 [thread overview]
Message-ID: <xmqqsf1j1vhl.fsf@gitster.g> (raw)
In-Reply-To: <pull.1663.v2.git.git.1708660111.gitgitgadget@gmail.com> (Haritha via GitGitGadget's message of "Fri, 23 Feb 2024 03:48:29 +0000")
"Haritha via GitGitGadget" <gitgitgadget@gmail.com> writes:
> Since the z/OS linker does not support searching dynamic libraries, and the
> current setting of CC_LD_DYNPATH results in a directory to be supplied to
> the link step with no option as the suffix, it causes a linker error because
> the z/OS LD linker does not accept directories as input. Therefore, we
> workaround this by adding the -L option.
Hmph, do we still need that CC_LD_DYNPATH hack, with 07bbe4ca (Merge
branch 'jc/make-libpath-template', 2024-02-06) already in 'master'?
> And, Introduced z/OS (OS/390) as a
> platform in config.mak.uname
Add support for z/OS (OS/390) in config.mak.uname.
or something (cf. Documentation/SubmittingPatches)?
> Thanks for taking the time to contribute to Git! Please be advised that the
> Git community does not use github.com for their contributions. Instead, we
> use a mailing list (git@vger.kernel.org) for code submissions, code reviews,
> and bug reports. Nevertheless, you can use GitGitGadget
> (https://gitgitgadget.github.io/) to conveniently send your Pull Requests
> commits to our mailing list.
>
> Please read the "guidelines for contributing" linked above!
For whom is the above message addressed? Who is expected to read
that guidelines?
next prev parent reply other threads:[~2024-02-23 7:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 14:21 [PATCH] This PR enables a successful git build on z/OS Haritha via GitGitGadget
2024-01-31 16:12 ` Kristoffer Haugsbakk
2024-01-31 17:58 ` Junio C Hamano
2024-01-31 17:12 ` Junio C Hamano
2024-02-23 3:48 ` [PATCH v2 0/2] " Haritha via GitGitGadget
2024-02-23 3:48 ` [PATCH v2 1/2] build: support z/OS (OS/390) Haritha D via GitGitGadget
2024-02-23 3:48 ` [PATCH v2 2/2] an improvement: removed configure.ac changes Haritha D via GitGitGadget
2024-02-23 7:38 ` Junio C Hamano
2024-02-23 7:37 ` Junio C Hamano [this message]
2024-02-25 6:10 ` [PATCH v3] build: support z/OS (OS/390) Haritha via GitGitGadget
2024-02-26 17:30 ` Junio C Hamano
2024-03-01 9:09 ` Haritha D
2024-03-01 14:39 ` Ghanshyam Thakkar
2024-03-01 18:15 ` Junio C Hamano
2024-03-01 18:25 ` rsbecker
2024-03-04 4:19 ` Haritha D
2024-03-06 5:44 ` [PATCH v4] " Haritha via GitGitGadget
2024-03-06 16:10 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqsf1j1vhl.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=harithamma.d@ibm.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).