OK - the issue causing the fail was the lack of a regtest tarball, which I
knew how to fix. There were a couple of other problems, but I have
definitely now successfully run GUB and got installation media. More
details to follow.
--
Phil Holmes
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc: "Devel"
Sent: Sunday, March 11, 2012 4:31 PM
Subject: Re: GUB success?
On Sun, Mar 11, 2012 at 04:19:24PM -, Phil Holmes wrote:
- Original Message - From: "Grah
On Sun, Mar 11, 2012 at 04:19:24PM -, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
>
> To: "Phil Holmes"
> Cc: "Devel"
> Sent: Sunday, March 11, 2012 3:30 PM
> Subject: Re: GUB success?
>
> >On Sun, Ma
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc: "Devel"
Sent: Sunday, March 11, 2012 3:30 PM
Subject: Re: GUB success?
On Sun, Mar 11, 2012 at 03:10:41PM -, Phil Holmes wrote:
I think I have GUB running properly. I gave up tryi
Phil Holmes wrote Sunday, March 11, 2012 3:10 PM
I think I have GUB running properly. I gave up trying to get it working on
64-bit Ubuntu and created a new VirtualBox VM with lilydev 1.1 as the OS.
Congratulations! One of the select few!
Trevor
__
On Sun, Mar 11, 2012 at 03:10:41PM -, Phil Holmes wrote:
> I think I have GUB running properly. I gave up trying to get it
> working on 64-bit Ubuntu and created a new VirtualBox VM with
> lilydev 1.1 as the OS.
Are you sure you mean lilydev 1.1 and not 1.2 ?
> I have documented what I did f
I think I have GUB running properly. I gave up trying to get it working on
64-bit Ubuntu and created a new VirtualBox VM with lilydev 1.1 as the OS.
After a number of lengthy false starts (lesson 1: when it's running, don't
interrupt it) I've just completed a build. I have documented what I di
Erik Sandberg wrote:
Hi,
Now gub works here (on my IA32 partition), so I can commit code again.
I couldn't easily force a rebuild. If I have a patch I want to test, what
should I do? I applied the patch to downloads/lilypond-HEAD, but I couldn't
find a good way to force make or make linux to
Erik Sandberg wrote:
Strangely, this didn't happen when building in 32-bit mode.
The problem seems to be that Apple's implementation of ranlib assumes 32-bit
architecture for some optimizations, so the lib doesn't work with platforms
where sizeof(char*)>4. I don't know what to do about this.
On Saturday 26 August 2006 21:51, Erik Sandberg wrote:
> On Saturday 26 August 2006 01:07, Han-Wen Nienhuys wrote:
> > Erik Sandberg wrote:
> - I could temporarily fix the above problem, but now there's a failure in
> the compilation of odcctools:
> *** Stage: compile (odcctools)
> [...]
> gcc -Wa
On Saturday 26 August 2006 01:07, Han-Wen Nienhuys wrote:
> Erik Sandberg wrote:
> > Hi,
> >
> > Now gub works here (on my IA32 partition), so I can commit code again.
> >
> > I couldn't easily force a rebuild. If I have a patch I want to test, what
> > should I do? I applied the patch to downloads
Erik Sandberg wrote:
Hi,
Now gub works here (on my IA32 partition), so I can commit code again.
I couldn't easily force a rebuild. If I have a patch I want to test, what
should I do? I applied the patch to downloads/lilypond-HEAD, but I couldn't
find a good way to force make or make linux to
Hi,
Now gub works here (on my IA32 partition), so I can commit code again.
I couldn't easily force a rebuild. If I have a patch I want to test, what
should I do? I applied the patch to downloads/lilypond-HEAD, but I couldn't
find a good way to force make or make linux to rebuild (the only way I
On 8/24/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Hmmm, I'm not sure this is a good idea. Although it checks each release
only once, it does run hourly, so this will generate a huge amount of
email. Perhaps it would be better to only send a message when the
status goes back from "failed"
Erik Sandberg wrote:
Hi,
Whenever the GUB autotester has failed and someone committed something
new, I only want to update to the new revision if it is not broken.
Would it be possible to add a brief "GUB autotester succeeded"
message, similar to the current failure notice, which the autotester
Hi,
Whenever the GUB autotester has failed and someone committed something
new, I only want to update to the new revision if it is not broken.
Would it be possible to add a brief "GUB autotester succeeded"
message, similar to the current failure notice, which the autotester
spits out whenever it
16 matches
Mail list logo
