From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Working on master and branch_release-1-8 in the same repository
Date: Tue, 10 Jun 2008 09:40:43 +0200 [thread overview]
Message-ID: <87k5gxlouc.fsf@gnu.org> (raw)
In-Reply-To: 49dd78620806091359h4d942bb1q367d6ab142b8cde2@mail.gmail.com
Hi,
"Neil Jerram" <neiljerram@googlemail.com> writes:
> I find that when switching from master to branch_release-1-8, I
> usually need to do a complete rebuild (i.e. make distclean, autogen,
> configure, make, make check). Do others find this too, or is there
> something clever I can do to avoid it and still be sure that I'm
> getting correct builds?
I use `ccache', which helps reduce the time needed to recompile.
I found that, for some reason, running `autoreconf' is only needed when
switching from 1.8 to `master', otherwise a failure is hit in
`socket.test', typically.
Of course, another solution is to store each branch in a separate
directory.
Thanks,
Ludo'.
next prev parent reply other threads:[~2008-06-10 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 20:59 Working on master and branch_release-1-8 in the same repository Neil Jerram
2008-06-10 7:40 ` Ludovic Courtès [this message]
2008-06-19 13:25 ` Neil Jerram
2008-06-23 12:30 ` Ludovic Courtès
2008-06-23 22:48 ` Neil Jerram
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=87k5gxlouc.fsf@gnu.org \
--to=ludo@gnu.org \
--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).