Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with buildroot-2013.02 - emacs
Date: Thu, 7 Mar 2013 09:30:24 +0100	[thread overview]
Message-ID: <20130307093024.30cb7d23@skate> (raw)
In-Reply-To: <84EA0F7435E5F64C9B660453645DB90497AD4DEF0D@DSW350.wattens.swarovski.com>

Dear Spielmann Werner,

On Wed, 6 Mar 2013 12:43:20 +0100, Spielmann Werner wrote:

> I'm a Newbie at buildroot and when I start my first trial to build a
> system with buildroot-2013.02 I run into troubles.
> 
> A few problems I was moving around and so  "make source" worked!
> 
> When I use "make" the script works for a short time, then an editor
> window is opened - I don't know  what to do.  :-(

Which editor opens up? I kind of believe the only way to get the issue
you have is that /usr/bin/emacs exists, but doesn't point to Emacs, but
to some other text editor.

> The process of the editor shown by "ps" is:
> emacs -batch -q -l script -f batch-byte-compile autoconf-mode.el
> autotest-mode.el
> 
> The status line of the editor shows (typed manual, couldn't copy):
> 
> Jove (Text)  [Main:1]  "[No file]" - <my_workspace>/buildroot-2013.02/

And this gets clear now: you don't have Emacs installed, but you have
Jove (http://en.wikipedia.org/wiki/JOVE). The thing is that Jove is
pretending to be compatible with Emacs, but it's not, so it makes the
autoconf stuff think there is Emacs, even though Emacs is not here.

As a workaround, you can apply this patch:

diff --git a/package/autoconf/autoconf.mk b/package/autoconf/autoconf.mk
index 0c36b66..daac1f2 100644
--- a/package/autoconf/autoconf.mk
+++ b/package/autoconf/autoconf.mk
@@ -15,7 +15,7 @@ AUTOCONF_CONF_ENV = EMACS="no" ac_cv_path_M4=$(HOST_DIR)/usr/bin/m4 \
 
 AUTOCONF_DEPENDENCIES = host-m4 perl
 
-HOST_AUTOCONF_CONF_ENV = ac_cv_path_M4=$(HOST_DIR)/usr/bin/m4 \
+HOST_AUTOCONF_CONF_ENV = EMACS="no" ac_cv_path_M4=$(HOST_DIR)/usr/bin/m4 \
                        ac_cv_prog_gnu_m4_gnu=no
 
 HOST_AUTOCONF_DEPENDENCIES = host-m4 host-libtool

-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-03-07  8:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 11:43 [Buildroot] Problem with buildroot-2013.02 - emacs Spielmann Werner
2013-03-07  6:31 ` Spielmann Werner
2013-03-07  8:30 ` Thomas Petazzoni [this message]
2013-03-07 12:47   ` Spielmann Werner
2013-03-07 13:08     ` Thomas Petazzoni
2013-03-08 11:29       ` [Buildroot] Problem with buildroot-2013.02 - ncurses Spielmann Werner
2013-03-08 12:16         ` Thomas Petazzoni
2013-03-08 13:07           ` Spielmann Werner
2013-03-08 13:16             ` Thomas Petazzoni
2013-03-11  7:35               ` Spielmann Werner
2013-03-12 14:51               ` Spielmann Werner
2013-03-12 23:14         ` Arnout Vandecappelle
2013-03-13  7:21           ` Thomas Petazzoni
2013-03-13  8:47           ` Spielmann Werner
2013-03-13 19:38             ` Arnout Vandecappelle
2013-03-14  7:15               ` Spielmann Werner
2013-03-14  8:03                 ` Arnout Vandecappelle
2013-03-14 14:53                   ` Spielmann Werner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130307093024.30cb7d23@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox