[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Denemo-devel] GUB status
From: |
Richard Shann |
Subject: |
Re: [Denemo-devel] GUB status |
Date: |
Sat, 25 Jun 2011 09:33:50 +0100 |
Nils - do you see a series of messages like this
cd: 1: can't cd to /home/rshann/gub/downloads/lilypond/git
during the build?
Richard
On Fri, 2011-06-24 at 22:39 +0200, Nils Gey wrote:
> Further apporaches were unsucessful, too.
> I've checked out a complete new gub and just tried to
> a) build Denemo
> b) build the normal Lilypond for linux-64 and mingw
>
> All return the same error. Lilypond is the only package that fails with
> the error /mnt/sdb3/workdir/vanilla-gub/target/tools/root/usr/bin/autoconf:
> line 188: CONFIG_SHELL: unbound variable
> Manually changing the autoconf script itself to see what is wrong results in
> many other variables not found. CONFIG_SHEL is only the first one.
>
> Since b) must be the most tested option because Lilypond uses it itself to
> release at least for Windows it must be an incompatibility with at least my
> system. Usual culprits are "too new" releases of my host toolchain, even if
> GUB is there to elimate those host dependencies. Especially since
> gub/Lilypond is the 30th or 40th package gub builds and its the only one that
> fails. Maybe no other packages uses this autoconf version gub build for
> itself? I don't know...
>
> The current status remains unchanged.
>
> Nils
>
> On Wed, 22 Jun 2011 20:36:48 +0200
> Nils Gey <address@hidden> wrote:
>
> > Hello,
> >
> > 1) GUB still fails to build MinGW Lilypond (any version) in an autoconf
> > step . Even upgrading the complete toolchain (in Gub) did not change
> > anything. Its a strange autoconf error where certain variables cannot be
> > found. I've seen this before but I don't think the error log shows the real
> > cause. Current status is I'm checking out a complete new gub dir right now,
> > try to keep it as vanilla as possible (except the missing downlodad urls
> > which are broken since the beginning of time but nobody cares to fix -
> > which shows how untested the whole Gub system is) and build Denemo. I don't
> > know how that can be any different then deleting the complete workdir of
> > gub ("target") which I did frequently, but who knows...
> >
> > 2) OSX Denemo is discontinued through GUB for me. I still have a slow OSX
> > system lying around where I compiled some dependencies already, but nothing
> > more. My motivation to do anything for OSX is minimal, only spreading
> > Denemo is even worth running OSX. Maybe some day someone will show up in
> > here and present a Denemo binary build and show me how to compile it on my
> > system.
> >
> > Nils
> >
> > _______________________________________________
> > Denemo-devel mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/denemo-devel
> >
>
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/denemo-devel