public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] pocl
Date: Sun, 14 Jan 2024 23:57:42 +0900	[thread overview]
Message-ID: <20240114235742.d10665f00ffaea33f854d348@nifty.ne.jp> (raw)
In-Reply-To: <171fe56e-9c90-46be-89f2-fa5c2d8e2b90@dronecode.org.uk>

Hi Jon,

Thanks for revewing.

On Sat, 13 Jan 2024 15:48:33 +0000
Jon Turney wrote:
> On 04/01/2024 00:55, Takashi Yano via Cygwin-apps wrote:
> [...]
> > Any comments and advices will be appreciated.
> 
> Thanks for adopting this.
> 
> > pocl.cygport
> > 
> > inherit clang cmake
> > 
> > NAME="pocl"
> > VERSION=3.1
> > RELEASE=1
> > CATEGORY="Libs"
> > # 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?

> 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?

My environment is as follows.

Cygwin Package Information
Package              Version        Status
binutils             2.41-3         OK
clang                8.0.1-1        OK
cmake                3.25.3-1       OK
cygport              0.36.7-1       OK
ninja                1.11.1-1       OK

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  reply	other threads:[~2024-01-14 14:57 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 [this message]
2024-01-14 20:46                     ` Jon Turney
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=20240114235742.d10665f00ffaea33f854d348@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin-apps@cygwin.com \
    /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).