Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: captain.deadly@gmail.com
To: openembedded-devel@lists.openembedded.org
Subject: bitbake emacs failing
Date: Thu, 28 Oct 2010 10:11:09 +0100	[thread overview]
Message-ID: <201010281011.10206.captain.deadly@gmail.com> (raw)

Hello all,
    have a strange problem on my system whereby when I try to build emacs the 
Makefiles generated by the configure script have random carriage return 
characters injected into them which makes a mess of the build. This was the 
case for both emacs_22.3.bb and emacs_23.1.bb.

I then decided that I'd stick in a recipe for version 23.2 and edited the 
generated makefiles to remove the new lines to get the package built. I 
eventually hit another problem:

| make[1]: *** No rule to make target 
`/home/john/programming/openmoko/shr2/shr-unstable/tmp/sysroots/armv4t-
oe-linux-gnueabi/usr/lib64/crt1.o', needed by `temacs'.  Stop.

The above error comes from a line in the Makefile generated for the src 
directory:

STARTFILES = pre-crt0.o /home/john/programming/openmoko/shr2/shr-
unstable/tmp/sysroots/armv4t-oe-linux-gnueabi/usr/lib64/crt1.o 
/home/john/programming/openmoko/shr2/shr-unstable/tmp/sysroots/armv4t-
oe-linux-gnueabi/usr/lib64/crti.o

This line is directing the build to a lib64 directory which does not exist. 
The required files do exist in the lib directory so I edited the Makefile again 
to remove the 64.

I guess I've two questions: why would configure make a mess of generating 
Makefiles and is there a problem using a 64 bit machine for openembedded?




                 reply	other threads:[~2010-10-28  9:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201010281011.10206.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox