From: Bruce Korb <bkorb@gnu.org>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: Trying to bootstrap my project, distcheck doesn't configure
Date: Tue, 15 Sep 2020 07:16:45 -0700 [thread overview]
Message-ID: <4725cba4-3dc2-314a-0e1d-fb48c1a51540@gnu.org> (raw)
In-Reply-To: <2357683.mymbEOZtgl@omega>
Hi Bruno,
On 9/14/20 3:53 PM, Bruno Haible wrote:
> Hi Bruce,
>
> It would help if you would give a pointer to the source code you are
> trying to bootstrap. Because a single line in Makefile.am or configure.ac
> can have a big effect.
It lives on my home machine while I try to get it ready for prime time.
As you may recollect, autogen is a monster. You can pull a copy from
GNU's git repo, if you're interested:
https://savannah.gnu.org/git/?group=autogen
> It is documented here:
> https://www.gnu.org/software/gnulib/manual/html_node/Modified-build-rules.html
Apparently, somewhere along the line I added "--lib=do_not_make_me".
That had to have been years ago and I have no recollection of adding
that. Anyway, that triggered some do_not_make_me_la_SOURCE += whatever
stuff, which was not added previously. I have no idea how those names
get selected, but after a grep, sed and unique sort, I came up with this
list:
> EXTRA_do_not_make_me_la_SOURCES =
> do_not_make_me_la_DEPENDENCIES =
> do_not_make_me_la_LIBADD =
> do_not_make_me_la_SOURCES =
These aren't documented on that page. I googled for "do_not_make_me" and
got no results, tho were I to do it today, I'd likely get this email
thread. :) Anyway, I am gathering from reading what you've pointed to
that the grep/sed/sort accommodation is the right solution. Thank you.
Regards, Bruce
For your possible (unlikely?) entertainment:
> fix_do_not_make_me() {
> local fix_list=$(
> grep -l FIX-DO-NOT-MAKE-ME \
> $(find * -type f -name 'Makefile.am'))
> local sedcmd= vlist= f= v=
>
> for f in $fix_list
> do
> sedcmd=$'/^##* *FIX-DO-NOT-MAKE-ME/ {\ns/.*//\n'
> vlist=$(sed -n '/do_not_make_me/s/ *[+=].*//p' $f | \
> sort -u)
> if test ${#vlist} -gt 1
> then
> sedcmd+=$'i\\\n'
> for v in $vlist
> do
> sedcmd+="$(printf '%-32s=' $v)"$'\\\n'
> done
> sedcmd+=$'\n'
> fi
> sedcmd+='}'
>
> sed "$sedcmd" $f > $f.make-me-fixed
> mv -f $f.make-me-fixed $f
> done
> }
next prev parent reply other threads:[~2020-09-15 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKRnqNLXD7waxPm7h=5S2-HkAe9WMVsLDtCuNrOFy_eyJZeZBQ@mail.gmail.com>
[not found] ` <56102afd-8924-3338-722f-da03e590dd63@gnu.org>
[not found] ` <87d02ob434.fsf@herbrand>
2020-09-14 21:11 ` Trying to bootstrap my project, distcheck doesn't configure Bruce Korb
2020-09-14 22:53 ` Bruno Haible
2020-09-15 14:16 ` Bruce Korb [this message]
2020-09-18 15:58 ` gc-pbkdf2-sha1 is deprecated Bruce Korb
2020-09-18 16:32 ` Bruno Haible
2020-09-21 22:49 ` Bruce Korb
2020-09-22 15:04 ` Bruce Korb
2020-09-22 17:03 ` Bruno Haible
2020-09-23 16:55 ` gc-pbkdf2-sha1 must not be deprecated Bruce Korb
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: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4725cba4-3dc2-314a-0e1d-fb48c1a51540@gnu.org \
--to=bkorb@gnu.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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.
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).