From: Roland Hieber <rhi@pengutronix.de>
To: Jon Ringle <jon@ringle.org>
Cc: ptxdist@pengutronix.com
Subject: Re: [ptxdist] SHARED_GDB_VERSION is undefined or empty
Date: Thu, 27 May 2021 15:50:39 +0200 [thread overview]
Message-ID: <20210527135039.2e5rr3jlwedxfjq3@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjw+5JCJ=2j28e3mnsSxX_EdGuzhOaoNw-yj2n3bsyqobQ@mail.gmail.com>
On Thu, May 27, 2021 at 09:45:04AM -0400, Jon Ringle wrote:
> I'm in the process of updating our bsp to 2021.05.0, and I'm running into
> this problem and I'm not sure how to fix this...
>
> /usr/local/lib/ptxdist-2021.05.1_GP/rules/gdbserver.make:18: ***
> SHARED_GDB_VERSION is undefined or empty. Stop.
>
> I see that it gets defined in gdb.make:
> SHARED_GDB_VERSION := $(call ptx/get-kconfig, $(TOOLCHAIN_CONFIG),
> PTXCONF_CROSS_GDB_VERSION)
>
> Not sure what to check here. Is this missing from my toolchain config?
I ran into this yesterday, and the problem in my case was that I had
bisected over a commit that updated the toolchain in the platformconfig,
but the selected_toolchain symlink still pointed to the old toolchain.
Removing the symlink got rid of the issue. Sadly I didn't manage to
recreate this situation, or I would have tried a patch, but maybe this
helps you already…
- Roland
--
Roland Hieber, Pengutronix e.K. | r.hieber@pengutronix.de |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
parent reply other threads:[~2021-05-27 13:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAMwGMjw+5JCJ=2j28e3mnsSxX_EdGuzhOaoNw-yj2n3bsyqobQ@mail.gmail.com>]
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=20210527135039.2e5rr3jlwedxfjq3@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=jon@ringle.org \
--cc=ptxdist@pengutronix.com \
--cc=ptxdist@pengutronix.de \
/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