All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: JH <jupiter.hce@gmail.com>
Cc: yocto <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Yocto build error
Date: Mon, 11 Oct 2021 09:59:55 +0200	[thread overview]
Message-ID: <CANNYZj_T_fuYj2Ow_e1GydsJaHm36eOJArM7Ezzuj_hWk-TEvw@mail.gmail.com> (raw)
In-Reply-To: <CAA=hcWSPQbqv9MDuRKME=iK8NM3sJKOdAcS1hti2VW0iodGFbQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

You need to show the full command line that produces the error.

Alex

On Mon, 11 Oct 2021 at 03:45, JH <jupiter.hce@gmail.com> wrote:

> Hi,
>
> I have following errors:
>
> No GNU_HASH in the ELF binary
>
> /build/tmp-glibc/work/cortexa7t2hf-neon-oe-linux-gnueabi/solar/1.0.0-0/packages-split/wifi_signal,
> didn't pass LDFLAGS? [ldflags]
>
> So I add --hash-style=gnu to my Makefile:
>
> LD_FLAGS += --hash-style=gnu
> LDFLAGS = LD_FLAGS
>
> But that does not work:
>
> arm-oe-linux-gnueabi-gcc: error: unrecognized command line option
> '--hash-style=gnu'
>
> What is wrong about the error if the  --hash-style=gnu is not the right
> fix?
>
> Thank you.
>
> Kind regards.
>
> JH
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#55010):
> https://lists.yoctoproject.org/g/yocto/message/55010
> Mute This Topic: https://lists.yoctoproject.org/mt/86227801/1686489
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
> alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 1948 bytes --]

  reply	other threads:[~2021-10-11  8:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11  1:45 Yocto build error Jupiter
2021-10-11  7:59 ` Alexander Kanavin [this message]
2021-10-11 17:29 ` [yocto] " Khem Raj

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=CANNYZj_T_fuYj2Ow_e1GydsJaHm36eOJArM7Ezzuj_hWk-TEvw@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=jupiter.hce@gmail.com \
    --cc=yocto@lists.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.