I gave the build of bison under cygwin another shot.
The file build-aux/prefix-gnulib-mk is not corrupted. It's a symlink (as
you said), and it's fine.
The problem seems to be related to the fact that the path 'lib/' and the
prefix 'lib_' are missing in the files generated by gnulib_tool. For
example, under cygwin the first 3 lines (after the comment) in the file lib/
gnulib.mk are:
MOSTLYCLEANFILES += core *.stackdump
noinst_LIBRARIES += libbison.a
libbison_a_SOURCES =
while under Ubunto (where things run smoothly) the first 3 lines are:
MOSTLYCLEANFILES += lib/core lib/*.stackdump
noinst_LIBRARIES += lib/libbison.a
lib_libbison_a_SOURCES =
At least this is the reason for the failure of automake.
On Wed, Apr 17, 2013 at 4:26 PM, Akim Demaille <a...@lrde.epita.fr> wrote:
>
> Le 16 avr. 2013 à 22:42, Efi Fogel <efifo...@gmail.com> a écrit :
>
> > I did not run the 'git submodule...' command the first time, but I did
> now. I still get the first error; see below. Am I suppose to run anything
> else before I run 'bootstrap'?
> > I am master.
>
> Good for you ;)
>
> > I was imprecise. I actually get the error above while running
> 'bootstrap'. So first, here is the error message. (Notice the first line
> about some unrecognized character.)
> >
> > Unrecognized character \xFF in column 11 at build-aux/prefix-gnulib-mk
> line 1.
> > […]
> > When I look at build-aux/prefix-gnulib-mk it seems completely corrupted.
>
> Well, that's the problem, obviously. Maybe it's because it's a symlink
> that it fails, I don't know. If you want to build on Cygwin, maybe the
> simplest is to build the tarball on Unix (make dist), and then to use
> this tarball, instead of working with git.
--
____ _ ____ _
/_____/_) o /__________ __ //
(____ ( ( ( (_/ (_/-(-'_(/
_/
_______________________________________________
help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
