All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ron Eggler <ron.eggler@mistywest.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Anders Montonen <Anders.Montonen@iki.fi>,
	"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] undefined reference problem persists
Date: Sun, 6 Nov 2022 18:19:24 -0800	[thread overview]
Message-ID: <1e2ca4a3-c266-90a4-9315-ecb5502e03f1@mistywest.com> (raw)
In-Reply-To: <CANNYZj-PtwKFqs+DHCR-CTC86UiVU7p9D=mBNyjG+pes6zeK8g@mail.gmail.com>


On 11/6/22 10:12, Alexander Kanavin wrote:
> On Sun, 6 Nov 2022 at 18:36, Mistyron <ron.eggler@mistywest.com> wrote:
>> I'll attempt to "just drop" meta-gplv2, then. However I see that there are other dependencies on readline too, i.e. it might be easier to just replace the existing 5.2 version in meta-gplv2 with 8.2 from here: https://git.yoctoproject.org/poky/plain/meta/recipes-core/readline/
> No. You cannot 'just replace' it, as they are under different
> licenses, and meta-gplv2 specifically collects versions under gpl
> version 2 only.
https://www.gnu.org/licenses/rms-why-gplv3.en.html specifies:

"When we say that GPLv2 and GPLv3 are incompatible, it means there is no 
legal way to combine code under GPLv2 with code under GPLv3 in a single 
program." - What is a single program though? Readline would still be a 
single program within the bitbake build, would it not? I'm not 
"stealing" nor editing its code but compile it as is.

>
> Are you going to ship what you're working on to other users, or is it
> just experimentation?
>
> Alex
-- 
RON EGGLER Firmware Engineer (he/him/his) www.mistywest.com


  parent reply	other threads:[~2022-11-07  2:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06  7:45 undefined reference problem persists Ron Eggler
2022-11-06  8:14 ` [yocto] " 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 [this message]
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=1e2ca4a3-c266-90a4-9315-ecb5502e03f1@mistywest.com \
    --to=ron.eggler@mistywest.com \
    --cc=Anders.Montonen@iki.fi \
    --cc=alex.kanavin@gmail.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.