unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Yan Li <yan.i.li@intel.com>
Cc: bug-guile@gnu.org, yanli@gnome.org
Subject: Re: [PATCH] Compiling DOT_X_FILES requires version.h
Date: Wed, 04 Aug 2010 20:21:07 +0200	[thread overview]
Message-ID: <m3y6cm2q98.fsf@unquote.localdomain> (raw)
In-Reply-To: <26f7d03710529a3bae3a2b6b7417bd4348e908f8.1280904428.git.yan.i.li@intel.com> (Yan Li's message of "Wed, 4 Aug 2010 15:02:43 +0800")

On Wed 04 Aug 2010 09:02, Yan Li <yan.i.li@intel.com> writes:

> There was a race condition when building Guile since DOT_X_FILES didn't
> depend on version.h, which is dynamically generated. Sometimes the
> DOT_X_FILES are compiled before the version.h is generated and leads to
> build failure. This patch fixed this problem.

Applied. Thanks!

Andy
-- 
http://wingolog.org/



      reply	other threads:[~2010-08-04 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04  7:02 [PATCH] Compiling DOT_X_FILES requires version.h Yan Li
2010-08-04 18:21 ` Andy Wingo [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: 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=m3y6cm2q98.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.org \
    --cc=yan.i.li@intel.com \
    --cc=yanli@gnome.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).