All of lore.kernel.org
 help / color / mirror / Atom feed
From: captain.deadly@gmail.com
To: "openembedded-devel" <openembedded-devel@lists.openembedded.org>
Subject: emacs alternative?
Date: Fri, 5 Nov 2010 07:35:25 +0000	[thread overview]
Message-ID: <201011050735.26140.captain.deadly@gmail.com> (raw)

I posted here before to say that emacs in OE doesn't build on my machine as 
the Makefile's being generated by autotools are being corrupted somehow. I've 
not been able to get to the bottom of it at all.

I thought I saw a post here recently that mentioned an embedded version of an 
emacs editor but can't find any such email. Maybe I imagined it. If anybody 
knows of the alternative which does build or perhaps knows why the Makefile's 
would be corrupted I'd be very glad to hear from you.

bitbake emacs gives me:

ERROR: Function do_compile failed
NOTE: Task failed: ('function do_compile failed', 
'/home/john/programming/openmoko/shr/shr-unstable/tmp/work/armv4t-oe-linux-
gnueabi/emacs-22.3-r1/temp/log.do_compile.9130')
ERROR: Logfile of failure stored in: /home/john/programming/openmoko/shr/shr-
unstable/tmp/work/armv4t-oe-linux-gnueabi/emacs-22.3-
r1/temp/log.do_compile.9130
Log data follows:
| NOTE: make -j 4 QEMU=qemu-arm  -s 1048576 -L 
/home/john/programming/openmoko/shr/shr-unstable/tmp/work/armv4t-oe-linux-
gnueabi/emacs-22.3-r1/qemu-treedir
| cd lib-src; make all - --jobserver-fds=10,11 -j \
|         CC='arm-oe-linux-gnueabi-gcc -march=armv4t -mtune=arm920t -mthumb-
interwork -mthumb' CFLAGS='-isystem/home/john/programming/openmoko/shr/shr-
unstable/tmp/sysroots/armv4t-oe-linux-gnueabi/usr/include -fexpensive-
optimizations -fomit-frame-pointer -frename-registers -Os' CPPFLAGS='-
D_BSD_SOURCE  -isystem/home/john/programming/openmoko/shr/shr-
unstable/tmp/sysroots/armv4t-oe-linux-gnueabi/usr/include' \
|         LDFLAGS='-Wl,-O1 -Wl,--hash-style=gnu -Wl,-znocombreloc' MAKE='make'
| make[1]: Entering directory `/home/john/programming/openmoko/shr/shr-
unstable/tmp/work/armv4t-oe-linux-gnueabi/emacs-22.3-r1/emacs-22.3/lib-src'
| Makefile:149: *** commands commence before first target.  Stop.
| make[1]: Leaving directory `/home/john/programming/openmoko/shr/shr-
unstable/tmp/work/armv4t-oe-linux-gnueabi/emacs-22.3-r1/emacs-22.3/lib-src'
| make: *** [lib-src] Error 2
| FATAL: oe_runmake failed
| ERROR: Function do_compile failed
NOTE: package emacs-22.3-r1: task do_compile: Failed


In the above output the emace-22.3 Makefile in /lib-src is failing at line 149. 
The Makefile at that line contains:

ALL_CFLAGS = -D_BSD_SOURCE -DHAVE_CONFIG_H
	  -I. -I../src -I${srcdir} -I${srcdir}/../src ${LDFLAGS} ${CPPFLAGS} 
${CFLAGS}

That is there are two lines but there should only be one. For some reason the 
line is being split into two and make is interpreting the second line (149) 
starting with "-I" as a command. Like the error says Make don't expect this 
command before it's read a target for some sort. If I remove this error I'll 
just move on to the next error where a new line has been inserted. There's a 
few of them :-(





             reply	other threads:[~2010-11-05  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05  7:35 captain.deadly [this message]
2010-11-05  7:44 ` emacs alternative? Martin Jansa
2010-11-05  9:05   ` captain.deadly
2010-11-05 13:08 ` Mike Westerhof

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=201011050735.26140.captain.deadly@gmail.com \
    --to=captain.deadly@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.