git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: [PATCH v3] build: support z/OS (OS/390).

From
Haritha D <harithamma.d@ibm.com>
Date
Mar 1, 2024, 09:09 UTC
Message-ID
<B3775704-6FCE-4994-8682-309D521FD2CB@ibm.com>
In-Reply-To
<xmqq7circevo.fsf@gitster.g>
Hi Team,
The win test(7) test case failed stating the reason as "The Operation cancelled". I saw that it failed after 5 hours 59 minutes of running the test cases(build). How do I handle this?
Please suggest.

Best regards Haritha

On 26/02/24, 11:15 PM, "Junio C Hamano" <gitster@pobox.com <mailto:gitster@pobox.com>> wrote:
"Haritha via GitGitGadget" <gitgitgadget@gmail.com <mailto:gitgitgadget@gmail.com>> writes:
Show 8 quoted lines
> From: Haritha D <harithamma.d@ibm.com <mailto:harithamma.d@ibm.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, -L option is added.

Shouldn't all of the above removed by now, with 07bbe4ca (Merge branch 'jc/make-libpath-template', 2024-02-06) that merged the support for platforms whose linker does not have a way to specify the path used at runtime to locate dynamic libraries and is already in the Git 2.44 release? The autoconf-generated config.mak.autogen would leave CC_LD_DYNPATH to empty on such a platform, which then adds only one "-L $where" (instead of the usual "-L $where -R $where") on the linker command line, making your earlier workaround to use "-L $where -L $where" unnecessary?

> Also introduced z/OS (OS/390) as a platform in config.mak.uname
"Introduce z/OS ..." (cf. Documentation/SubmittingPatches)
Or perhaps

Add platform specific settings in config.mak.uname for zOS (OS/390).

Show 19 quoted lines
> diff --git a/config.mak.uname b/config.mak.uname
> index dacc95172dc..03ee2b74525 100644
> --- a/config.mak.uname
> +++ b/config.mak.uname
> @@ -638,6 +638,18 @@ ifeq ($(uname_S),NONSTOP_KERNEL)
> SANE_TOOL_PATH = /usr/coreutils/bin:/usr/local/bin
> SHELL_PATH = /usr/coreutils/bin/bash
> endif
> +ifeq ($(uname_S),OS/390)
> + NO_SYS_POLL_H = YesPlease
> + NO_STRCASESTR = YesPlease
> + NO_REGEX = YesPlease
> + NO_MMAP = YesPlease
> + NO_NSEC = YesPlease
> + NO_STRLCPY = YesPlease
> + NO_MEMMEM = YesPlease
> + NO_GECOS_IN_PWENT = YesPlease
> + HAVE_STRINGS_H = YesPlease
> + NEEDS_MODE_TRANSLATION = YesPlease

All of the above should be indented with TAB to imitate the support for other platforms, I think.

Thanks.
Show 6 quoted lines
> +endif
> ifeq ($(uname_S),MINGW)
> ifeq ($(shell expr "$(uname_R)" : '1\.'),2)
> $(error "Building with MSys is no longer supported")
>
> base-commit: f41f85c9ec8d4d46de0fd5fded88db94d3ec8c11
Previous: Junio C HamanoNext: Ghanshyam Thakkar
Message 12 of 18 in “This PR enables a successful git build on z/OS.”
  1. This PR enables a successful git build on z/OS.Haritha via GitGitGadget, Jan 31, 2024
  2. Kristoffer HaugsbakkJan 31, 2024
  3. Junio C HamanoJan 31, 2024
  4. Junio C HamanoJan 31, 2024
  5. 0/2 This PR enables a successful git build on z/OS.Haritha via GitGitGadget, Feb 23, 2024
  6. 1/2 build: support z/OS (OS/390).Haritha D via GitGitGadget, Feb 23, 2024
  7. 2/2 an improvement: removed configure.ac changesHaritha D via GitGitGadget, Feb 23, 2024
  8. Junio C HamanoFeb 23, 2024
  9. Junio C HamanoFeb 23, 2024
  10. build: support z/OS (OS/390).Haritha via GitGitGadget, Feb 25, 2024
  11. Junio C HamanoFeb 26, 2024
  12. Haritha DMar 1, 2024
  13. Ghanshyam ThakkarMar 1, 2024
  14. Junio C HamanoMar 1, 2024
  15. rsbecker@nexbridge.comMar 1, 2024
  16. Haritha DMar 4, 2024
  17. build: support z/OS (OS/390).Haritha via GitGitGadget, Mar 6, 2024
  18. Junio C HamanoMar 6, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.