Vagrant Cascadian writes:
>> http://gitlab.com/janneke/nyacc
>
> Built!
Yay!
> Tried building with this, and had a couple issues.
>
> The clean target assumes a git checkout:
>
> clean:
> git clean -dfx
>
> But Debian builds against tarballs of the source, and running 'git clean
> -dfx' from a directory with the source unpackaged but no .git directory
> fails.
Ah, bummer. I'm somewhat reluctant to add and maintain a nice `make
clean' in the age of git. So what I've tried is to have configure (I
really need to cleanup that thing) create a git archive if necessary.
Would that work?
> The configure target doesn't take some common options, and fails when
> unknown options are passed, such as --includedir. The default build
> passed these:
>
> ./configure --build=x86_64-linux-gnu --prefix=/usr
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
> --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
> --disable-maintainer-mode --disable-dependency-tracking
That's helpful! I made sure this command now works. The pain of not
using autotools is almost becoming as great as the pain of not using
them.
> From the ./configure help output, it suggests that only --prefix and
> --sysconfdir are supported, but maybe not all the supported options are
> documented.
Currently, only --prefix and --infodir are supported.
> Working around that by only passing:
>
> ./configure --prefix=/usr --sysconfdir=/etc
>
> And a no-op clean target...
Okay...hoping that's not necessary and my git init hack works.
> Still fails to build:
>
> build-aux/build-cc.sh
> ...
> ;;; WARNING: compilation of
> /<<BUILDDIR>>/mes-0.16+0.3da4d01/build-aux/mes-snarf.scm failed:
> ;;; ERROR: failed to create path for auto-compiled file
> "/<<BUILDDIR>>/mes-0.16+0.3da4d01/build-aux/mes-snarf.scm"
> mes-snarf[guile]...
> lib/libmes.c:21:10: fatal error: libmes.h: No such file or directory
> #include <libmes.h>
Ah...CPPFLAGS, CFLAGS get overridden. I revised my build.
> So, some progress, but still some work left to do! :)
Something like this was to be expected, please have a look at my new
wip-gnu branch (or `debian' which is currently wip-gnu+your patches).
I intend to release this as 0.16.1 if/once it builds for you.
Do you prefer me including your debian packaging patches, i.e. having them
"upstream" or is that inconvenient?
Thanks!
Greetings,
janneke
--
Jan Nieuwenhuizen <jann...@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
