From: <rsbecker@nexbridge.com>
To: "'Todd Zullinger'" <tmz@pobox.com>,
"'Junio C Hamano'" <gitster@pobox.com>
Cc: "'Johannes Sixt'" <j6t@kdbg.org>,
"'Patrick Steinhardt'" <ps@pks.im>, <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.50.0-rc1 - Test Failed
Date: Fri, 6 Jun 2025 03:20:20 -0400 [thread overview]
Message-ID: <016d01dbd6b3$7a27f290$6e77d7b0$@nexbridge.com> (raw)
In-Reply-To: <aEIqXphU07pYjFCg@teonanacatl.net>
On June 5, 2025 7:38 PM, Todd Zullinger wrote:
>Junio C Hamano wrote:
>> <rsbecker@nexbridge.com> writes:
>>
>>> Can I pass this in via command line? Instead of modifying config.mak?
>>
>> make NO_TCLTK=NoThanks
>>
>> just like you are passing V=1 on the command line of "make" in your
>> earlier message. That would not build or install gitk and git-gui.
>>
>> By the way, I do not think writing into config.mak qualifies as
>> "modifying", as we do not ship one ourselves.
>
>Indeed, I always considered that the ideal way to set options.
>
>Another benefit, from the perspective of package builder, is that you then
use the
>same options for all the invocations of make. This avoids things being
needlessly
>rebuilt if you happen to set them in build and install sections of your
packaging
>recipes and then let them get out of sync.
>
>In the Fedora builds, we did it like so¹:
>
># Use these same options for every invocation of 'make'.
># Otherwise it will rebuild in %%install due to flags # changes.
># Pipe to tee to aid confirmation/verification of settings.
>cat << \EOF | tee config.mak
>V = 1
>CFLAGS = %{build_cflags}
>LDFLAGS = %{build_ldflags}
>...
>EOF
>
>['%{build_*flags}' are rpm macros, not something to be used literally,
just in case
>anyone wonders.]
>
>¹ https://src.fedoraproject.org/rpms/git/blob/ee7f0d4/f/git.spec#_545-582
Thanks. Thinks are looking much better now on NonStop.
prev parent reply other threads:[~2025-06-06 7:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 17:02 [ANNOUNCE] Git v2.50.0-rc1 Junio C Hamano
2025-06-03 22:33 ` [ANNOUNCE] Git v2.50.0-rc1 - Test Failed rsbecker
2025-06-03 22:45 ` rsbecker
2025-06-04 13:51 ` Todd Zullinger
2025-06-04 15:17 ` Junio C Hamano
2025-06-04 19:25 ` Johannes Sixt
2025-06-05 8:09 ` rsbecker
2025-06-05 8:56 ` Patrick Steinhardt
2025-06-05 20:27 ` rsbecker
2025-06-05 21:11 ` Johannes Sixt
2025-06-05 21:33 ` Junio C Hamano
2025-06-06 5:57 ` [GIT PULL] git-gui: fix for: " Johannes Sixt
2025-07-22 17:45 ` [GIT PULL] git-gui: Sync with 2.50.1, Tcl >= 8.6, git >= 2.36 Johannes Sixt
2025-06-05 21:44 ` [ANNOUNCE] Git v2.50.0-rc1 - Test Failed rsbecker
2025-06-05 22:06 ` Junio C Hamano
2025-06-05 23:38 ` 'Todd Zullinger'
2025-06-06 7:20 ` rsbecker [this message]
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='016d01dbd6b3$7a27f290$6e77d7b0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=ps@pks.im \
--cc=tmz@pobox.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.