On Wed, 15 Jan 2025 at 02:04, Mingyu Wang (Fujitsu) <wan...@fujitsu.com> wrote:
> We think about two solutions:
> 1. Use the v2 patch to specify --with-xterm-kbs=del
> 2. Temporarily modify the following code in Yocto. And submit patches to
> upstream:
> --- a/configure
> +++ b/configure
> @@ -9470,7 +9470,7 @@ echo "${ECHO_T}$with_xterm_new" >&6
> WHICH_XTERM=$with_xterm_new
>
> case $host_os in
> -(*linux-gnu|*cygwin|*mingw32|*msys)
> +(*linux-gnu*|*cygwin|*mingw32|*msys)
> want_xterm_kbs=DEL
> ;;
> (*)
>
> Which plan do you think is better?
I think this plan with two action points:
1. Specify --with-xterm-kbs=del in the recipe. You can adjust the
commit message to explain the above problem with linux-gnueabi.
2. At the same time, propose the above patch upstream, without adding
it to Yocto.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#209895):
https://lists.openembedded.org/g/openembedded-core/message/209895
Mute This Topic: https://lists.openembedded.org/mt/110604398/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
