From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Struggling with creating recipe liblockdev
Date: Wed, 05 Sep 2012 12:33:43 +0100 [thread overview]
Message-ID: <1346844824.2673.154.camel@phil-desktop> (raw)
In-Reply-To: <50473834.3070407@communistcode.co.uk>
On Wed, 2012-09-05 at 12:32 +0100, Jack Mitchell wrote:
> | /usr/bin/ld: ../src/lockdev.z: Relocations in generic ELF (EM: 40)
> | /usr/bin/ld: ../src/lockdev.z: Relocations in generic ELF (EM: 40)
> | /usr/bin/ld: ../src/lockdev.z: Relocations in generic ELF (EM: 40)
> | /usr/bin/ld: ../src/lockdev.z: Relocations in generic ELF (EM: 40)
> | /usr/bin/ld: ../src/lockdev.z: Relocations in generic ELF (EM: 40)
> | ../src/lockdev.z: could not read symbols: File in wrong format
> | collect2: error: ld returned 1 exit status
> | make[1]: *** [blib/arch/auto/LockDev/LockDev.so] Error 1
You seem to be trying to use /usr/bin/cc and /usr/bin/ld to generate
target binaries. Those should almost certainly be ${CC} and ${LD}
respectively.
p.
prev parent reply other threads:[~2012-09-05 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 11:22 Struggling with creating recipe liblockdev Jack Mitchell
2012-09-05 11:30 ` Burton, Ross
2012-09-05 11:32 ` Jack Mitchell
2012-09-05 11:33 ` Phil Blundell [this message]
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=1346844824.2673.154.camel@phil-desktop \
--to=philb@gnu.org \
--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.