[augeas-devel] building on OSX (Lion)

[David N. Blank-Edelman]

Hi David-

Thanks for your response. Replies inline.

On Jul 18, 2012, at 5:45 PM, David Lutterkort wrote:

> I am not sure what causes this particular issue - augeas explicitly
> requests the strchrnul module from gnulib; so this might be a gnulib
> bug.

Hmm, I wonder if it has to do with the age of gnulib provided in the last official release tarball (http://augeas.net/download/augeas-0.10.0.tar.gz):

$ cd augeas-0.10.0/gnulib/ 
$ grep -Rl strchrnul *
lib/string.in.h
m4/string_h.m4

vs. the current one pulled down from git:

lib/.deps/strchrnul.Plo
lib/.gitignore
lib/Makefile
lib/Makefile.am
lib/Makefile.in
lib/strchrnul.c
lib/strchrnul.valgrind
lib/string.in.h
m4/.gitignore
m4/gnulib-cache.m4
m4/gnulib-comp.m4
m4/rawmemchr.m4
m4/strchrnul.m4
m4/string_h.m4
tests/.gitignore
tests/Makefile
tests/Makefile.am
tests/Makefile.in
tests/test-strchrnul.c

(i.e. now they ship an implementation, note this was mention in a closed bug: https://fedorahosted.org/augeas/ticket/261. That bug was closed as a dupe, but I don't see the original anywhere).

>> I also saw David mention in June the possibility of cutting a new
>> release (perhaps with that fix) back in June, but I don't know if that
>> addresses the strchrnul() problem.
> 
> I have to admit I am not sure which discussion you are referring to for
> the fix - the only recent Solaris discussion I recall was around making
> augeas buildable with the Sun compiler

In https://www.redhat.com/archives/augeas-devel/2012-March/msg00005.html, a discussion of this bug, one of the OpenCSW maintainers pointed at the patches:

http://sourceforge.net/apps/trac/gar/browser/csw/mgar/pkg/augeas/trunk

One of those patches attempts to work around this (for Solaris).

> ... as for a release, I am sorry it's still not there. First, vacation, and then other stuff intruded.
> But I still want to make one soon(ish)

No worries. I guess one question would be whether you would consider releasing a 0.10.1 with a newer gnulib. Not sure how kosher this would be, but I bet it would solve this particular problem for the people downstream from you.

>> YACC     parser.c
>> /tmp/augeas/augeas/src/parser.y:46.1-5: invalid directive: `%code'
>> /tmp/augeas/augeas/src/parser.y:46.7-14: syntax error, unexpected identifier
> 
> This might be an issue with bison being too old - I have bison-2.5 on my
> Fedora system.

OSX ships with 2.3:

$ /usr/bin/bison --version
bison (GNU Bison) 2.3

MacPorts provides 2.5.1 which does indeed build the latest from HEAD cleanly. I think you may need to declare/test for this dependency explicitly somewhere. Thanks for your help!

      -- dNb