From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 43479@debbugs.gnu.org
Subject: bug#43479: Generated files ’doc/os-conf-*.texi’ and “make“
Date: Sat, 19 Sep 2020 11:35:02 +0200 [thread overview]
Message-ID: <87k0wqrtx5.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ3+d7NiUNV6YvnmapoqU=0H=a_JZL1ObbmzVAa3Cwy0Xw@mail.gmail.com> (zimoun's message of "Fri, 18 Sep 2020 22:18:51 +0200")
zimoun <zimon.toutoune@gmail.com> skribis:
>> The reason seems to be that:
>>
>> --8<---------------cut here---------------start------------->8---
>> # Bundle this file so that makeinfo finds it in out-of-source-tree builds.
>> BUILT_SOURCES += $(OS_CONFIG_EXAMPLES_TEXI) $(TRANSLATED_INFO)
>> EXTRA_DIST += $(OS_CONFIG_EXAMPLES_TEXI) $(TRANSLATED_INFO)
>> MAINTAINERCLEANFILES = $(OS_CONFIG_EXAMPLES_TEXI) $(TRANSLATED_INFO)
>> --8<---------------cut here---------------end--------------->8---
>
> Yah, I have tried to tweak a lot of stuff and it has always failed.
> Simon's relationship with configure and Makefile.am: is complicated.
> :-)
> Well, since these files are only a hard copy of files in
> gnu/system/examples/, does it make sense to simply symlink them and
> remove the rule?
You can try, but the comment above about out-of-source-tree builds
suggests it won’t work. :-)
(That’s because .info is treated specially; namely, Info files are part
of the distribution, so they are always built in the source tree.)
Ludo’.
next prev parent reply other threads:[~2020-09-19 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 21:14 bug#43479: Generated files ’doc/os-conf-*.texi’ and “make“ zimoun
2020-09-18 12:15 ` Ludovic Courtès
2020-09-18 20:18 ` zimoun
2020-09-19 9:35 ` Ludovic Courtès [this message]
2020-09-25 13:43 ` zimoun
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0wqrtx5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43479@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).