Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Graham Gower <graham.gower@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: emacs copying ${STAGING_DIR_TARGET} - wtf?
Date: Tue, 16 Nov 2010 11:05:29 +1030	[thread overview]
Message-ID: <4CE1D1D1.1000009@gmail.com> (raw)

emacs.inc has this nugget in do_compile_prepend():
cp -pPR ${STAGING_DIR_TARGET}/* $treedir

During a world build, both emacs and emacs-x11 copy some 5GB into
their work dirs. This really seems like overkill.

Could someone familiar with building emacs take a look to see if
there is a reasonable alternative?

thanks,
-Graham

PS: emacs and emacs-x11 fail for me in do_compile.

NOTE: make -j 12 QEMU=qemu-mipsel  -s 1048576 -L /mnt/oe/tmp/work/mipsel-oe-linux/emacs-22.3-r1/qemu-treedir 
cd lib-src; make all - --jobserver-fds=3,22 -j \
	  CC='mipsel-oe-linux-gcc -march=mips32' CFLAGS='-isystem/mnt/oe/tmp/sysroots/mipsel-oe-linux/usr/include -fexpensive-optimizations -fomit-frame-pointer -frename-registers -Os' CPPFLAGS='-D_BSD_SOURCE  -isystem/mnt/oe/tmp/sysroots/mipsel-oe-linux/usr/include' \
	  LDFLAGS='-L/mnt/oe/tmp/sysroots/mipsel-oe-linux/usr/lib -Wl,-rpath-link,/mnt/oe/tmp/sysroots/mipsel-oe-linux/usr/lib -Wl,-O1 -Wl,-znocombreloc' MAKE='make'
make[1]: Entering directory `/mnt/oe/tmp/work/mipsel-oe-linux/emacs-22.3-r1/emacs-22.3/lib-src'
Makefile:149: *** commands commence before first target.  Stop.
make[1]: Leaving directory `/mnt/oe/tmp/work/mipsel-oe-linux/emacs-22.3-r1/emacs-22.3/lib-src'
make: *** [lib-src] Error 2
FATAL: oe_runmake failed



             reply	other threads:[~2010-11-16  0:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16  0:35 Graham Gower [this message]
2010-11-16  6:13 ` emacs copying ${STAGING_DIR_TARGET} - wtf? Martin Jansa
2010-11-16  7:38   ` Graham Gower
2010-11-17  8:20     ` captain.deadly
2010-11-17  8:50     ` captain.deadly

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=4CE1D1D1.1000009@gmail.com \
    --to=graham.gower@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox