Date
21 - 23 of 23
undefined reference problem persists
Alexander Kanavin
On Mon, 7 Nov 2022 at 16:13, Ron Eggler <ron.eggler@...> wrote:
I'm curious as to how though. Are you going to give them a completeAre you able to fulfil that obligation you have under the license?Yes, that will definitely be doable for the recepient if they chose to set of yocto layers and source code for everything that goes into the image, so that they can replicate the yocto build? If they choose to replace readline with their own version, I don't see any other way. Note that we are not talking about the manufacturer of the device, we are talking about the actual end users who will buy and use the device for its intended purpose. Alex |
|
On 2022-11-07 7:20 a.m., Alexander
Kanavin wrote:
Exactly, the customer will have full access to the source code incl. the complete set of Yocto layers and all.On Mon, 7 Nov 2022 at 16:13, Ron Eggler <ron.eggler@...> wrote:Are you able to fulfil that obligation you have under the license?Yes, that will definitely be doable for the recepient if they chose to do so.I'm curious as to how though. Are you going to give them a complete set of yocto layers and source code for everything that goes into the image, so that they can replicate the yocto build? If they choose to replace readline with their own version, I don't see any other way. Yes, understood!Note that we are not talking about the manufacturer of the device, we are talking about the actual end users who will buy and use the device for its intended purpose. |
|
Alexander Kanavin
On Mon, 7 Nov 2022 at 18:57, Ron Eggler <ron.eggler@...> wrote:
Then your best option is to drop meta-gplv2 layer from builds altogether. This will update everything to current, compatible versions that are easier to fix if needed. Just to be on the safe side, you do need to find out why it was added though. The reason may still hold. Alex |
|