From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: BSD make problem [was: [PATCH 5/5] www: wire up search ...]
Date: Thu, 25 Apr 2024 08:11:32 +0000 [thread overview]
Message-ID: <20240425081132.M769448@dcvr> (raw)
In-Reply-To: <20240424064447.523799-6-e@80x24.org>
Eric Wong <e@80x24.org> wrote:
> diff --git a/MANIFEST b/MANIFEST
> index 4c974338..fb175e5f 100644
> --- a/MANIFEST
> +++ b/MANIFEST
> @@ -382,6 +382,8 @@ lib/PublicInbox/XapClient.pm
> lib/PublicInbox/XapHelper.pm
> lib/PublicInbox/XapHelperCxx.pm
> lib/PublicInbox/Xapcmd.pm
> +lib/PublicInbox/XhcMset.pm
> +lib/PublicInbox/XhcMsetIterator.pm
With FreeBSD 13.2 make(1), changes to MANIFEST don't seem to
trigger Makefile rebuilds even when Makefile.PL is made to
depend on MANIFEST:
Makefile.PL : MANIFEST
touch -r MANIFEST $@
$(PERLRUN) $@
# and Makefile depends on Makefile.PL via this
# ExtUtils::MakeMaker supplied rule:
FIRST_MAKEFILE = Makefile
$(FIRST_MAKEFILE) : Makefile.PL $(CONFIGDEP)
...
It's not a problem with gmake, Makefile gets rebuilt whenever
MANIFEST gets updated.
Any suggestions? ExtUtils::MakeMaker seems generate some
GNU-isms in its Makefile anyways, so perhaps requiring GNU make
on *BSD is acceptable...
prev parent reply other threads:[~2024-04-25 8:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 6:44 [PATCH 0/5] www: start using xap_helper process Eric Wong
2024-04-24 6:44 ` [PATCH 1/5] searchview: get rid of unused adump callback arg Eric Wong
2024-04-24 6:44 ` [PATCH 2/5] xap_helper.h: remove _SC_NPROCESSORS_ONLN default Eric Wong
2024-04-24 6:44 ` [PATCH 3/5] xap_helper: drop terms+data from `mset' command Eric Wong
2024-04-24 6:44 ` [PATCH 4/5] mbox: hoist out refill_result_ids Eric Wong
2024-04-24 6:44 ` [PATCH 5/5] www: wire up search to use async xap_helper Eric Wong
2024-04-24 9:39 ` [PATCH 6/5] xap_helper: PERL_INLINE_DIRECTORY fallback for JAOT build Eric Wong
2024-04-25 8:11 ` Eric Wong [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
List information: http://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240425081132.M769448@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).