All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: "Pawar, Alok" <Alok.Pawar3@harman.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Compilation error : No GNU_HASH in elf bianry
Date: Wed, 28 Jun 2017 21:50:32 -0700	[thread overview]
Message-ID: <CAMKF1sq5FfN3tdhHFdfDUsMTA9GF6F1x93OJTk8R9FJL+OA1OQ@mail.gmail.com> (raw)
In-Reply-To: <2f3e1cd085204ac480e2435922a9cce1@HIBDWSMB03.ad.harman.com>

On Wed, Jun 28, 2017 at 9:29 PM, Pawar, Alok <Alok.Pawar3@harman.com> wrote:
> Hi,
>
>
>
> I am using krogoth release and I am facing one issue in custom bitbake file.
>
>
>
> When I am doing bitbake with custom bb file the following error is coming :
>
> “No GNU_HASH in the elf binary”
>
> In custom bb file, I am trying to copy precompiled binary and library.
>
> I tried also with Flag : FILES_${PN} += , but face same issue.
>

this error means you have an issue in Makefiles where
linker flags are not being respected.

I would suggest to add CFLAGS and LDFLAGS both to
linker cmdline in Makefile.

Other option is to set

TARGET_CC_ARCH += "${LDFLAGS}"

in your bb file but I would rather like to see it fixed in
right place which is the Makefile.

>
>
> Best Regards
>
> Alok Pawar
>
> Sr. Engineer Product Development
>
> Harman Connected Services
>
>
>
>
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


  reply	other threads:[~2017-06-29  4:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29  4:29 Compilation error : No GNU_HASH in elf bianry Pawar, Alok
2017-06-29  4:50 ` Khem Raj [this message]
2017-06-29  4:53   ` [EXTERNAL] " Pawar, Alok

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=CAMKF1sq5FfN3tdhHFdfDUsMTA9GF6F1x93OJTk8R9FJL+OA1OQ@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=Alok.Pawar3@harman.com \
    --cc=yocto@yoctoproject.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.