ALTERNATIVE_LINK_NAME in bash recipe doesn't create /bin/sh

ALTERNATIVE_LINK_NAME in bash recipe doesn't create /bin/sh

[Devendra Tewari]

[-- Attachment #1: Type: text/plain, Size: 342 bytes --]

Hello,

I've added bash recipe (version 5.1.8) to a target but it does not seem to produce the /bin/sh link. I've checked that the recipe is supposed to provide the following link

ALTERNATIVE_LINK_NAME[sh] = "${base_bindir}/sh"

Is that by itself sufficient to produce the link? If so, it does not seem to do so.

Thanks,
Devendra

[-- Attachment #2: Type: text/html, Size: 378 bytes --]

Re: ALTERNATIVE_LINK_NAME in bash recipe doesn't create /bin/sh

[Devendra Tewari]

[-- Attachment #1: Type: text/plain, Size: 524 bytes --]

To provide more context, these are the ALTERNATIVE variables in the recipe around ALTERNATIVE_LINK_NAME[sh]

ALTERNATIVE:${PN} = "bash sh"
ALTERNATIVE_LINK_NAME[bash] = "${base_bindir}/bash"
ALTERNATIVE_TARGET[bash] = "${base_bindir}/bash"
ALTERNATIVE_LINK_NAME[sh] = "${base_bindir}/sh"
ALTERNATIVE_TARGET[sh] = "${base_bindir}/bash.${BPN}"

Based on earlier messages on ALTERNATIVE_LINK_NAME and ALTERNATIVE_TARGET, I have arrived at the conclusion that a link should be created but isn't.

Thanks,
Devendra

[-- Attachment #2: Type: text/html, Size: 2194 bytes --]

Re: ALTERNATIVE_LINK_NAME in bash recipe doesn't create /bin/sh

[Devendra Tewari]

[-- Attachment #1: Type: text/plain, Size: 123 bytes --]

Looks like update-alternatives --install is not happening at all for any packages during do_rootfs.

Thanks,
Devendra

[-- Attachment #2: Type: text/html, Size: 139 bytes --]