From: Ron Eggler <ron.eggler@mistywest.com>
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: undefined reference problem persists
Date: Sun, 6 Nov 2022 00:45:36 -0700 [thread overview]
Message-ID: <49ac7ca4-2af5-43e9-d5f8-02bb98ac372a@mistywest.com> (raw)
Hi,
I'm working with dunfell and want to compile and install the drivers for
the Laird LWB5+ module (available from
https://github.com/LairdCP/meta-laird-cp).
I have included the path to the layer in meta-laird-cp-pre-3.4 in my
`bblayers.conf` and since I need the networkmanager and with information
from their support team (don't trust the README apparently), I've added
`lrd-networkmanager-sterling` to the `IMAGE_INSTALL` list in
`sample-image-cp-lwb5plus.bb`. When I invoke `$ bitbake
sample-image-cp-lwb5plus`, I keep getting:
|
/usr/src/debug/lrd-networkmanager-sterling/10.4.0.10-r0/build/../lrd-network-manager-10.4.0.10/src/nmcli/common.c:904:
undefined reference to `rl_echo_signal_char'
even though I've added `readline` to the `DEPENDS` list. Why is this? I
expected the `rl_echo_signal_char` dependency to be resolved, any hints?
next reply other threads:[~2022-11-06 7:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 7:45 Ron Eggler [this message]
2022-11-06 8:14 ` [yocto] undefined reference problem persists Alexander Kanavin
2022-11-06 15:43 ` Ron Eggler
2022-11-06 8:40 ` Markus Volk
2022-11-06 15:45 ` Ron Eggler
2022-11-06 10:26 ` Anders Montonen
2022-11-06 16:02 ` Ron Eggler
2022-11-06 16:48 ` Anders Montonen
2022-11-06 17:13 ` Alexander Kanavin
2022-11-06 17:36 ` Ron Eggler
2022-11-06 18:12 ` Alexander Kanavin
2022-11-07 1:35 ` Ron Eggler
2022-11-07 8:27 ` Alexander Kanavin
2022-11-07 15:12 ` Ron Eggler
2022-11-07 15:20 ` Alexander Kanavin
2022-11-07 17:57 ` Ron Eggler
2022-11-07 19:15 ` Alexander Kanavin
2022-11-07 2:19 ` Ron Eggler
2022-11-07 8:32 ` Alexander Kanavin
2022-11-07 1:00 ` Khem Raj
2022-11-07 2:16 ` Khem Raj
2022-11-07 2:30 ` Ron Eggler
[not found] ` <17252C937E759BD8.12191@lists.yoctoproject.org>
2022-11-07 4:19 ` Ron Eggler
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=49ac7ca4-2af5-43e9-d5f8-02bb98ac372a@mistywest.com \
--to=ron.eggler@mistywest.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.