From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] ocl-icd fails to build
Date: Fri, 28 Jan 2022 01:53:06 +0100 [thread overview]
Message-ID: <20220128005306.h98XFknXVNUw8WLjrkI0p0jvOFXWd9E2aPibxMKLyI0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35265@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]
Closed issue by RossComputerGuy on void-packages repository
https://github.com/void-linux/void-packages/issues/35265
Description:
```
ocl_icd_debug.h:55:84: note: in definition of macro 'debug'
55 | fprintf(stderr, "ocl-icd(%s:%i): %s: " fmt "\n", __FILE__, __LINE__, __func__, ##__VA_ARGS__); \
| ^~~~~~~~~~~
ocl_icd_loader_gen.c:2188:3: note: in expansion of macro 'dump_field'
2188 | dump_field(pid, f, clUnknown179);
| ^~~~~~~~~~
ocl_icd_debug.h:89:160: error: 'struct _cl_icd_dispatch' has no member named 'clGetExtensionFunctionAddressForPlatform'
89 | debug(D_ALWAYS, "%40s=%p [%p/%p]", #name, pid->dispatch->name, f(#name), ((long)(pid->dispatch->clGetExtensionFunctionAddressForPlatform)>10)?pid->dispatch->clGetExtensionFunctionAddressForPlatform(pid, #name):NULL)
| ^~
ocl_icd_debug.h:55:84: note: in definition of macro 'debug'
55 | fprintf(stderr, "ocl-icd(%s:%i): %s: " fmt "\n", __FILE__, __LINE__, __func__, ##__VA_ARGS__); \
| ^~~~~~~~~~~
ocl_icd_loader_gen.c:2188:3: note: in expansion of macro 'dump_field'
2188 | dump_field(pid, f, clUnknown179);
| ^~~~~~~~~~
make[2]: *** [Makefile:819: libOpenCL_la-ocl_icd_loader_gen.lo] Error 1
make[2]: Leaving directory '/builddir/ocl-icd-2.2.12'
make[1]: *** [Makefile:1016: all-recursive] Error 1
make[1]: Leaving directory '/builddir/ocl-icd-2.2.12'
make: *** [Makefile:588: all] Error 2
=> ERROR: ocl-icd-2.2.12_2: do_build: '${make_cmd} ${makejobs} ${make_build_args} ${make_build_target}' exited with 2
=> ERROR: in do_build() at common/build-style/gnu-configure.sh:15
```
I was playing around with `xbps-src` and while trying to compile `ocl-icd` for ffmpeg, I ran across this issue. The repo cloned is up to date so there should be no issues there.
prev parent reply other threads:[~2022-01-28 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 23:29 [ISSUE] " RossComputerGuy
2022-01-28 0:53 ` q66 [this message]
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=20220128005306.h98XFknXVNUw8WLjrkI0p0jvOFXWd9E2aPibxMKLyI0@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).