From: Jon Turney <jon.turney@dronecode.org.uk>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin-apps@cygwin.com
Subject: Re: [ITA] pocl
Date: Sun, 14 Jan 2024 20:46:10 +0000 [thread overview]
Message-ID: <c8509ea6-8276-43ef-b913-98148cc623f9@dronecode.org.uk> (raw)
In-Reply-To: <20240114235742.d10665f00ffaea33f854d348@nifty.ne.jp>
On 14/01/2024 14:57, Takashi Yano via Cygwin-apps wrote:
> On Sat, 13 Jan 2024 15:48:33 +0000
> Jon Turney wrote:
>> On 04/01/2024 00:55, Takashi Yano via Cygwin-apps wrote:
>> [...]
>>> # The entire code is under MIT
>>> # include/utlist.h which is under BSD-1-Clause (unbundled)
>>> # lib/kernel/vecmath which is under GPL-3.0-or-later OR LGPL-3.0-or-later
>>> LICENSE="MIT, BSD-1-Clause, GPL-3.0-or-later OR LGPL-3.0-or-later"
>>
>> I think this is going to fail to validate as an SPDX license expression.
>> The identifiers should be combined with AND and OR (where OR represents
>> a choice, and AND represents compliance with both alternatives is required).
>
> What about "MIT AND BSD-1-Clause AND (GPL-3.0-or-later OR LGPL-3.0-or-later)"?
> Is "()" allowed?
Yes.
https://spdx.github.io/spdx-spec/v2-draft/SPDX-license-expressions/#d45-order-of-precedence-and-parentheses
>
>> When I try to build it fails:
>>
>> [449/761] Linking CXX shared module lib/llvmopencl/cygllvmopencl.dll
>> FAILED: lib/llvmopencl/cygllvmopencl.dll
>> [...]
>> /usr/bin/ld: cannot find -lpocl: No such file or directory
>> clang-8: error: linker command failed with exit code 1 (use -v to see
>> invocation)
>>
>> I don't know if that means it's looking for the installed rather than
>> just built libpocl there, or something else is wrong.
>
> I cannot reproduce this even if I uninstall libpocl-devel. Umm, what
> is the difference?
Yeah, confusing. I think it might have been caused by not having
libOpenCL-devel installed.
Anyhow, I can build it OK now, so all is good.
Maybe consider adding BUILD_REQUIRES="clang libllvm-devel libhwloc-devel
libOpenCL-devel ninja" or whatever is correct :)
next prev parent reply other threads:[~2024-01-14 20:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 5:14 Takashi Yano
2024-01-03 5:25 ` Takashi Yano
2024-01-03 7:54 ` Marco Atzeri
2024-01-03 9:29 ` Takashi Yano
2024-01-03 11:38 ` Brian Inglis
2024-01-03 12:00 ` Takashi Yano
2024-01-03 12:26 ` Brian Inglis
2024-01-03 12:42 ` Takashi Yano
2024-01-03 12:30 ` Takashi Yano
2024-01-03 14:08 ` Takashi Yano
2024-01-04 0:55 ` Takashi Yano
2024-01-13 15:48 ` Jon Turney
2024-01-14 14:57 ` Takashi Yano
2024-01-14 20:46 ` Jon Turney [this message]
2024-01-15 3:14 ` Takashi Yano
2024-01-07 12:51 ` Jon Turney
2024-01-07 13:05 ` Takashi Yano
2024-01-08 0:38 ` Andrew Schulman
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=c8509ea6-8276-43ef-b913-98148cc623f9@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).