All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>,
	"otavio.salvador@ossystems.com.br"
	<otavio.salvador@ossystems.com.br>, "hs@denx.de" <hs@denx.de>,
	"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
	"raj.khem@gmail.com" <raj.khem@gmail.com>,
	Fabio Estevam <festevam@denx.de>
Subject: Re: [oe] [PATCH v3 meta-oe] rtc-tools: Add a recipe
Date: Fri, 28 Jan 2022 07:28:05 -0300	[thread overview]
Message-ID: <CAOMZO5DmubmJmVgTwVdkVBOc8h7+Ep7C2n0eRSKbhDMj9TimTA@mail.gmail.com> (raw)
In-Reply-To: <d204889ebaf04514b6ec2863a5104052@axis.com>

Hi Peter,

On Fri, Jan 28, 2022 at 1:48 AM Peter Kjellerstedt
<peter.kjellerstedt@axis.com> wrote:

> > +TARGET_CC_ARCH += "${LDFLAGS}"
>
> You forgot to remove the TAGET_CC_ARCH line.

If I remove this line, the following error happens:

ERROR: rtc-tools-1.0.0-r0 do_package_qa: QA Issue: File
/usr/bin/rtc-sync in package rtc-tools doesn't have GNU_HASH (didn't
pass LDFLAGS?)
File /usr/bin/rtc in package rtc-tools doesn't have GNU_HASH (didn't
pass LDFLAGS?)
File /usr/bin/rtc-range in package rtc-tools doesn't have GNU_HASH
(didn't pass LDFLAGS?) [ldflags]
ERROR: rtc-tools-1.0.0-r0 do_package_qa: QA run found fatal errors.
Please consider fixing them.

Any suggestions as to how this should be fixed?

Thanks


  reply	other threads:[~2022-01-28 10:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 23:06 [PATCH v3 meta-oe] rtc-tools: Add a recipe Fabio Estevam
2022-01-28  4:48 ` [oe] " Peter Kjellerstedt
2022-01-28 10:28   ` Fabio Estevam [this message]
2022-01-28 15:33     ` Khem Raj
2022-01-28 18:36       ` Peter Kjellerstedt
2022-01-28 19:58         ` Fabio Estevam

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=CAOMZO5DmubmJmVgTwVdkVBOc8h7+Ep7C2n0eRSKbhDMj9TimTA@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=festevam@denx.de \
    --cc=hs@denx.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=peter.kjellerstedt@axis.com \
    --cc=raj.khem@gmail.com \
    /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.