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 14:08:18 +0100	[thread overview]
Message-ID: <20130307140818.0d48c197@skate> (raw)
In-Reply-To: <84EA0F7435E5F64C9B660453645DB90497AD52A6B0@DSW350.wattens.swarovski.com>

Dear Spielmann Werner,

On Thu, 7 Mar 2013 13:47:39 +0100, Spielmann Werner wrote:
> Hello Thomas,
> 
> Many thanks for your explanation. You are right, emacs was not really
> installed. There were only Links:
> 
>   /usr/bin/emacs -> /etc/alternatives/emacs
>   /etc/alternatives/emacs -> /usr/bin/jove
> 
> => strange!

Why strange? Jove pretends to be an emacs clone, so Debian/Ubuntu
installs it as an Emacs alternative. See
http://wiki.debian.org/DebianAlternatives.

> The Patch didn't work at the first attempt, as far as I can see the
> line numbers of autoconf.mk do not match (I have installed the
> buildroot-2013.02 from the download directory - perhaps do you use
> newer versions from the repository?). So I installed emacs - seemed
> to be the fastest solution!  ;-)

I don't think autoconf.mk has changed since 2013.02, so I don't
understand why the patch doesn't apply for you, especially since it's a
one-liner.

Anyway, I'm pretty sure EMACS="no" fixes your problem, even if you keep
Jove installed instead of Emacs. I tested it here, and the
host-autoconf build process no longer tries to compile the .el files
into .elc files using Emacs.

I've submitted the patch for inclusion into Buildroot.

Best regards,

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

  reply	other threads:[~2013-03-07 13:08 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
2013-03-07 12:47   ` Spielmann Werner
2013-03-07 13:08     ` Thomas Petazzoni [this message]
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=20130307140818.0d48c197@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