From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Khem Raj <raj.khem@gmail.com>, Fabio Estevam <festevam@gmail.com>
Cc: Fabio Estevam <festevam@denx.de>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"hs@denx.de" <hs@denx.de>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
"otavio.salvador@ossystems.com.br"
<otavio.salvador@ossystems.com.br>
Subject: RE: [oe] [PATCH v3 meta-oe] rtc-tools: Add a recipe
Date: Fri, 28 Jan 2022 18:36:48 +0000 [thread overview]
Message-ID: <afd084404e704b268d2f6c6adb104bc3@axis.com> (raw)
In-Reply-To: <CAMKF1sr+tUripPnYtWz+2xcwAqJq4QMYYkE82nobkw8i=N3bHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]
The default rules provided by make do include $(LDFLAGS). This is the default rule provided by make to link a binary from a .c file:
%: %.c
# recipe to execute (built-in):
$(LINK.c) $^ $(LOADLIBES) $(LDLIBS) -o $@
where LINK.c is defined as:
LINK.c = $(CC) $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) $(TARGET_ARCH)
(you can see the default rules by running make -p anywhere where there isn’t a Makefile).
I have now also applied the patch for the rtc-tools recipe. I then removed the TARGET_CC_ARCH line from it and built it without problems.
@Fabio: Are you sure you built with the correct version of the recipe and Makefile when you got the error about GNU_HASH? Because it should work (and I’ve verified that the files I built have the GNU_HASH and I never built with the TARGET_CC_ARCH line in the recipe).
//Peter
From: Khem Raj <raj.khem@gmail.com>
Sent: den 28 januari 2022 16:33
To: Fabio Estevam <festevam@gmail.com>
Cc: Fabio Estevam <festevam@denx.de>; Peter Kjellerstedt <peter.kjellerstedt@axis.com>; alexandre.belloni@bootlin.com; hs@denx.de; openembedded-devel@lists.openembedded.org; otavio.salvador@ossystems.com.br
Subject: Re: [oe] [PATCH v3 meta-oe] rtc-tools: Add a recipe
On Fri, Jan 28, 2022 at 2:28 AM Fabio Estevam <festevam@gmail.com<mailto:festevam@gmail.com>> wrote:
Hi Peter,
On Fri, Jan 28, 2022 at 1:48 AM Peter Kjellerstedt
<peter.kjellerstedt@axis.com<mailto: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?
I already suggested in earlier email to add LDFLAGS in makefile rules
Thanks
[-- Attachment #2: Type: text/html, Size: 8223 bytes --]
next prev parent reply other threads:[~2022-01-28 18:36 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
2022-01-28 15:33 ` Khem Raj
2022-01-28 18:36 ` Peter Kjellerstedt [this message]
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=afd084404e704b268d2f6c6adb104bc3@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=alexandre.belloni@bootlin.com \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=hs@denx.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox