Hi Dan,
Use of the DIST file is only needed if building ragel from a tarball
distributed on the site. The generated scanner and parser are included
in the tarballs, but not the source code repository. When building from
a tarball they are not normally generated. The DIST file allows that to
be changed.
When building from the source repository they should always be built,
which means you need ragel and kelbt installed.
You may need to run ./autogen.sh and ./configure again. If that doesn't
clear it up for you there may be a bug related to the fact that the
ragel directory was renamed to src.
-Adrian
On 12-09-07 09:39 PM, Dan Kortschak wrote:
Resolved:
The ragel executable needs to be in .../ragel/ and DIST needs to hold
the value 'build_parsers=yes'.
This was not clear from the README, which says: "If you would like to
modify Ragel and need to build Ragel's scanners and parsers from the
specifications then set "build_parsers=yes" the DIST file and
reconfigure." This is misleading/incomplete as I did not want to modify
ragel, and did not know that it was necessary to build the scanners and
parsers to build ragel itself. A comment that this is necessary for the
first build would be helpful.
thanks
On Sat, 2012-09-08 at 10:31 +0930, Dan Kortschak wrote:
Hello,
I have tried to build ragel from source from the git repository
(ref:37e4b), but I get the following error:
$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for ./DIST... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for ar... ar
checking for ranlib... ranlib
checking whether make sets $(MAKE)... (cached) yes
checking for gdc... no
checking for the Objective-C compiler... no
checking for javac... javac
checking for txl... no
checking for ruby... ruby
checking for gmcs... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating aapl/Makefile
config.status: creating doc/Makefile
config.status: creating doc/ragel.1
config.status: creating contrib/Makefile
config.status: creating test/Makefile
config.status: creating test/runtests
config.status: creating examples/Makefile
config.status: creating src/config.h
config.status: src/config.h is unchanged
config.status: executing depfiles commands
config.status: executing default commands
configuration of ragel complete
$ make
Making all in src
make[1]: Entering directory `/home/x/dev/ragel/src'
make[1]: *** No rule to make target `rlscan.cc', needed by `all'. Stop.
make[1]: Leaving directory `/home/x/dev/ragel/src'
make: *** [all-recursive] Error 1
I can find no information regarding rlscan.cc that helps me figure this
out.
Having ragel installed as a binary (6.7 from debs) made no difference to
this. Is there perhaps some documentation missing here?
thanks
Dan
_______________________________________________
ragel-users mailing list
[email protected]
http://www.complang.org/mailman/listinfo/ragel-users
_______________________________________________
ragel-users mailing list
[email protected]
http://www.complang.org/mailman/listinfo/ragel-users
_______________________________________________
ragel-users mailing list
[email protected]
http://www.complang.org/mailman/listinfo/ragel-users
