From: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
To: guile-devel@gnu.org
Subject: [PATCH] byacc: fix potential parallel build issue
Date: Wed, 9 Jan 2013 14:45:10 +0200 [thread overview]
Message-ID: <1357735510-7295-1-git-send-email-bogdan.a.marinescu@intel.com> (raw)
Add explicit dependency for libpath.h on dynl.x which fixes a potential parallel build issue. The other file that includes libguile/libpath.h (libguile/load.c) already has an explicit dependency on libpath.h
diff --git a/libguile/Makefile.am b/libguile/Makefile.am
index e216435..016bd90 100644
--- a/libguile/Makefile.am
+++ b/libguile/Makefile.am
@@ -700,6 +700,7 @@ $(DOT_DOC_FILES) $(EXTRA_DOT_DOC_FILES): scmconfig.h snarf.h guile-snarf-docs.in
error.x: cpp-E.c
posix.x: cpp-SIG.c
load.x: libpath.h
+dynl.x: libpath.h
alldotdocfiles = $(DOT_DOC_FILES) $(EXTRA_DOT_DOC_FILES)
snarf2checkedtexi = GUILE_AUTO_COMPILE=0 $(top_builddir)/meta/uninstalled-env guild snarf-check-and-output-texi
next reply other threads:[~2013-01-09 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 12:45 Bogdan Marinescu [this message]
2013-01-09 12:49 ` [PATCH] byacc: fix potential parallel build issue Marinescu, Bogdan A
2013-01-21 21:10 ` Andy Wingo
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1357735510-7295-1-git-send-email-bogdan.a.marinescu@intel.com \
--to=bogdan.a.marinescu@intel.com \
--cc=guile-devel@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).