public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: 정희철 <heecheol.jung@lginnotek.com>
To: "green@moxielogic.com" <green@moxielogic.com>,
	"libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Cc: "Jin Park(박진)" <jpark@lginnotek.com>,
	"Hyunsuk Lim(임현석)" <hslim@lginnotek.com>, 김남 <knam@lginnotek.com>
Subject: Question about libffi OSS license
Date: Thu, 05 Apr 2018 07:02:00 -0000	[thread overview]
Message-ID: <422A357000E4C84B8736561B3DD52AAFDAC622@LITMEMBOX01.lginnotek.com> (raw)
In-Reply-To: <2418934BE59743969C17B9804BCF421C@LITACAS04GSP.lginnotek.com>

Dear libffi developers



we use libffi v3.2.1 (QCT default) , but the following files have been confirmed to GPLv3+ when check with fossology

files : target-libpath.exp,  wrapper.exp, libffi.exp,  call.exp



The libffi page said libffi is freeware, and in Wikipedia, it said MIT license. what license should I apply?

Also, if I should apply GPLv3+, can I delete those files for using libffi ?



Thanks & Regards

heecheol.jung



________________________________

상기 메일은 지정된 수신인만을 위한 것이며, 부정경쟁방지 및 영업비밀의 보호에 관한 법률을 포함하여
관계 법령에 따라 보호의 대상이 되는 영업비밀, 기밀정보 등을 포함하고 있을 수 있습니다.
본 문서에 포함된 정보의 전부 또는 일부를 무단으로 제3자에게 공개, 배포, 복사 또는 사용하는 것은 엄격히 금지됩니다.
본 메일이 잘못 전송된 경우, 발신인 또는 당사에 알려주시고, 본 메일을 즉시 삭제하여 주시기 바랍니다.
The above message is intended solely for the named addressee and may contain
information that is privileged, confidential or otherwise protected under
applicable law. Any unauthorized dissemination, distribution, copying or use of
the information contained in this communication is strictly prohibited. If you
have received this communication in error, please notify the sender by email
and erase this communication immediately.

       reply	other threads:[~2018-04-05  7:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2418934BE59743969C17B9804BCF421C@LITACAS04GSP.lginnotek.com>
2018-04-05  7:02 ` 정희철 [this message]
2018-04-05 12:26   ` Anthony Green

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=422A357000E4C84B8736561B3DD52AAFDAC622@LITMEMBOX01.lginnotek.com \
    --to=heecheol.jung@lginnotek.com \
    --cc=green@moxielogic.com \
    --cc=hslim@lginnotek.com \
    --cc=jpark@lginnotek.com \
    --cc=knam@lginnotek.com \
    --cc=libffi-discuss@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).