Build Fails if Emacs, gperf, bison, flex are not installed #1

Closed
ppannuto opened this Issue Feb 14, 2013 · 3 comments

Comments

Projects
None yet
3 participants
@ppannuto
Contributor

ppannuto commented Feb 14, 2013

The configure script does not detect the presence / absence of emacs, causing the build to fail unexpectedly. Does some piece of nesC actually require emacs?

Making all in src
make[1]: Entering directory `/home/ppannuto/code/nesc/src'
cd . && emacs  -batch -load build-types.el AST nodetypes.def 42
/bin/bash: emacs: command not found
make[1]: *** [AST_defs.h] Error 127
make[1]: Leaving directory `/home/ppannuto/code/nesc/src'
make: *** [all-recursive] Error 1
@dgay42

This comment has been minimized.

Show comment
Hide comment
@dgay42

dgay42 Feb 14, 2013

Member

On Feb 13, 2013, at 9:22 PM, ppannuto wrote:

The configure script does not detect the presence / absence of emacs, causing the build to fail unexpectedly. Does some piece of nesC actually require emacs?

Building from scratch requires emacs. However, the release tarballs don't (the files generated by emacs are included).

David Gay

Making all in src
make[1]: Entering directory /home/ppannuto/code/nesc/src' cd . && emacs -batch -load build-types.el AST nodetypes.def 42 /bin/bash: emacs: command not found make[1]: *** [AST_defs.h] Error 127 make[1]: Leaving directory/home/ppannuto/code/nesc/src'
make: *** [all-recursive] Error 1


Reply to this email directly or view it on GitHub.

Member

dgay42 commented Feb 14, 2013

On Feb 13, 2013, at 9:22 PM, ppannuto wrote:

The configure script does not detect the presence / absence of emacs, causing the build to fail unexpectedly. Does some piece of nesC actually require emacs?

Building from scratch requires emacs. However, the release tarballs don't (the files generated by emacs are included).

David Gay

Making all in src
make[1]: Entering directory /home/ppannuto/code/nesc/src' cd . && emacs -batch -load build-types.el AST nodetypes.def 42 /bin/bash: emacs: command not found make[1]: *** [AST_defs.h] Error 127 make[1]: Leaving directory/home/ppannuto/code/nesc/src'
make: *** [all-recursive] Error 1


Reply to this email directly or view it on GitHub.

@cire831

This comment has been minimized.

Show comment
Hide comment
@cire831

cire831 Feb 14, 2013

Member

We should put the release tar balls up on the git repository.

I haven't done it in a while, David, can you generate the tar balls?

On Wed, Feb 13, 2013 at 9:27 PM, dgay42 notifications@github.com wrote:

On Feb 13, 2013, at 9:22 PM, ppannuto wrote:

The configure script does not detect the presence / absence of emacs,
causing the build to fail unexpectedly. Does some piece of nesC actually
require emacs?

Building from scratch requires emacs. However, the release tarballs don't
(the files generated by emacs are included).

David Gay

Making all in src
make[1]: Entering directory /home/ppannuto/code/nesc/src' cd . && emacs -batch -load build-types.el AST nodetypes.def 42 /bin/bash: emacs: command not found make[1]: *** [AST_defs.h] Error 127 make[1]: Leaving directory/home/ppannuto/code/nesc/src'
make: *** [all-recursive] Error 1


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHubhttps://github.com/tinyos/nesc/issues/1#issuecomment-13533780.

Eric B. Decker
Senior (over 50 :-) Researcher

Member

cire831 commented Feb 14, 2013

We should put the release tar balls up on the git repository.

I haven't done it in a while, David, can you generate the tar balls?

On Wed, Feb 13, 2013 at 9:27 PM, dgay42 notifications@github.com wrote:

On Feb 13, 2013, at 9:22 PM, ppannuto wrote:

The configure script does not detect the presence / absence of emacs,
causing the build to fail unexpectedly. Does some piece of nesC actually
require emacs?

Building from scratch requires emacs. However, the release tarballs don't
(the files generated by emacs are included).

David Gay

Making all in src
make[1]: Entering directory /home/ppannuto/code/nesc/src' cd . && emacs -batch -load build-types.el AST nodetypes.def 42 /bin/bash: emacs: command not found make[1]: *** [AST_defs.h] Error 127 make[1]: Leaving directory/home/ppannuto/code/nesc/src'
make: *** [all-recursive] Error 1


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHubhttps://github.com/tinyos/nesc/issues/1#issuecomment-13533780.

Eric B. Decker
Senior (over 50 :-) Researcher

@ppannuto

This comment has been minimized.

Show comment
Hide comment
@ppannuto

ppannuto Feb 14, 2013

Contributor

The configure script also fails to detect if gperf, bison, or flex are present. The latter two are often unnecessary when shipping tarballs, and some Googling around didn't present an obvious best practice.

None of these issues are particularly critical, but they're hard to find unless you're building on a fresh system so I figured they merited documenting here.

Contributor

ppannuto commented Feb 14, 2013

The configure script also fails to detect if gperf, bison, or flex are present. The latter two are often unnecessary when shipping tarballs, and some Googling around didn't present an obvious best practice.

None of these issues are particularly critical, but they're hard to find unless you're building on a fresh system so I figured they merited documenting here.

@ghost ghost assigned dgay42 Feb 14, 2013

bradjc pushed a commit to lab11/nesc that referenced this issue May 11, 2013

Brad Campbell
Updated configure to check for more dependencies
Now checks for emacs, bison, gperf, flex

Fixes issue #1

bradjc pushed a commit to lab11/nesc that referenced this issue May 12, 2013

Brad Campbell
Updated configure to check for more dependencies
Now checks for emacs, bison, gperf, flex but only if the code is from
the github repo and not a tarball.

Fixes issue #1

bradjc pushed a commit to lab11/nesc that referenced this issue May 12, 2013

Brad Campbell
Updated configure to check for more dependencies
Now checks for emacs, bison, gperf, flex but only if the code is from
the github repo and not a tarball.

Fixes issue #1

@ppannuto ppannuto closed this Dec 4, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment