lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GUB / autoconf out-of-tree builds


From: Graham Percival
Subject: Re: GUB / autoconf out-of-tree builds
Date: Mon, 22 Jun 2009 15:16:53 -0700
User-agent: Mutt/1.5.18 (2008-05-17)

On Mon, Jun 22, 2009 at 11:23:09AM +0200, Jan Nieuwenhuizen wrote:
> Op woensdag 17-06-2009 om 13:24 uur [tijdzone -0700], schreef Graham
> Percival:
> 
> > I've tracked down the srcdir vs. builddir problem to autoconf.
> 
> Is this now fixed?  It seems that
> 
> > The $(TOPDOC_TXT_FILES) includes RELEASE-COMMIT, which is only
> > created in the builddir, not the srcdir.
> 
> RELEASE-COMMIT is not included in TOPDOC_TXT_FILES in master?

That's what I don't get!  TOPDOC_TXT_FILES is defined as

TOPDOC_TXT_FILES = $(addprefix 
$(top-build-dir)/Documentation/topdocs/$(outdir)/,$(addsuffix 
.txt,$(TOPDOC_FILES)))

and yet a fresh "make lilypond" in gub produces this line:

ln 
/home/lilypond/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-master/ChangeLog
 
/home/lilypond/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-master/RELEASE-COMMIT
 ...
  (it's a whole screenful of files to be ln'd)

but, as expected, ChangeLog and RELEASE-COMMIT don't exist in the
../src/.. dir.


I've attached the log file.  I just don't know where this "ln"
command is coming from!

Cheers,
- Graham

Attachment: log
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]