All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Haritha  via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Kristoffer Haugsbakk <code@khaugsbakk.name>,
	Haritha  <harithamma.d@ibm.com>
Subject: [PATCH v2 0/2] This PR enables a successful git build on z/OS.
Date: Fri, 23 Feb 2024 03:48:29 +0000	[thread overview]
Message-ID: <pull.1663.v2.git.git.1708660111.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1663.git.git.1706710861778.gitgitgadget@gmail.com>

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. And, Introduced z/OS (OS/390) as a
platform in config.mak.uname

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!

Haritha D (2):
  build: support z/OS (OS/390).
  an improvement: removed configure.ac changes

 config.mak.uname | 12 ++++++++++++
 1 file changed, 12 insertions(+)


base-commit: f41f85c9ec8d4d46de0fd5fded88db94d3ec8c11
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1663%2FHarithaIBM%2Fzos-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1663/HarithaIBM/zos-v2
Pull-Request: https://github.com/git/git/pull/1663

Range-diff vs v1:

 1:  2eddc8f8860 ! 1:  53e211d7a65 This PR enables a successful git build on z/OS.
     @@ Metadata
      Author: Haritha D <harithamma.d@ibm.com>
      
       ## Commit message ##
     -    This PR enables a successful git build on z/OS.
     +    build: support z/OS (OS/390).
      
          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.
     -    And, Introduced z/OS (OS/390) as a platform in config.mak.uname
     +    Therefore, -L option is added.
     +    Also introduced z/OS (OS/390) as a platform in config.mak.uname
      
          Signed-off-by: Haritha D <harithamma.d@ibm.com>
      
 -:  ----------- > 2:  05df5d7e2d5 an improvement: removed configure.ac changes

-- 
gitgitgadget

  parent reply	other threads:[~2024-02-23  3:48 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 ` Haritha  via GitGitGadget [this message]
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   ` [PATCH v2 0/2] This PR enables a successful git build on z/OS Junio C Hamano
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=pull.1663.v2.git.git.1708660111.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=code@khaugsbakk.name \
    --cc=git@vger.kernel.org \
    --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 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.