From: "Girar awaiter (viy)" <girar-builder@altlinux.org> To: Igor Vlasenko <viy@altlinux.org> Cc: sisyphus-incominger@lists.altlinux.org, girar-builder-sisyphus@altlinux.org Subject: [#322047] FAILED srpm=clanlib-2.3.7-alt2_13.src.rpm Date: Sat, 27 May 2023 19:42:15 +0000 Message-ID: <girar.task.322047.1.1@gyle.mskdc.altlinux.org> (raw) https://git.altlinux.org/tasks/322047/logs/events.1.1.log subtask name aarch64 armh i586 ppc64le x86_64 #100 clanlib 3:49 5:39 2:21 failed 2:06 2023-May-27 19:36:34 :: task #322047 for sisyphus started by viy: #100 build clanlib-2.3.7-alt2_13.src.rpm 2023-May-27 19:36:36 :: [ppc64le] #100 clanlib-2.3.7-alt2_13.src.rpm: build start 2023-May-27 19:36:36 :: [i586] #100 clanlib-2.3.7-alt2_13.src.rpm: build start 2023-May-27 19:36:36 :: [armh] #100 clanlib-2.3.7-alt2_13.src.rpm: build start 2023-May-27 19:36:36 :: [aarch64] #100 clanlib-2.3.7-alt2_13.src.rpm: build start 2023-May-27 19:36:36 :: [x86_64] #100 clanlib-2.3.7-alt2_13.src.rpm: build start [ppc64le] | vec_or [ppc64le] ../../Sources/API/Core/Zip/../System/../System/cl_platform.h:314:12: error: 'vector' does not name a type; did you mean 'vec_or'? [ppc64le] 314 | typedef vector unsigned short __cl_ushort8; [ppc64le] | vec_or [ppc64le] ../../Sources/API/Core/Zip/../System/../System/cl_platform.h:315:12: error: 'vector' does not name a type; did you mean 'vec_or'? [ppc64le] 315 | typedef vector signed short __cl_short8; [ppc64le] | vec_or [ppc64le] ../../Sources/API/Core/Zip/../System/../System/cl_platform.h:316:12: error: 'vector' does not name a type; did you mean 'vec_or'? [ppc64le] 316 | typedef vector unsigned int __cl_uint4; [ppc64le] | vec_or [ppc64le] ../../Sources/API/Core/Zip/../System/../System/cl_platform.h:317:12: error: 'vector' does not name a type; did you mean 'vec_or'? [ppc64le] 317 | typedef vector signed int __cl_int4; [ppc64le] | vec_or [ppc64le] ../../Sources/API/Core/Zip/../System/../System/cl_platform.h:318:12: error: 'vector' does not name a type; did you mean 'vec_or'? [ppc64le] 318 | typedef vector float __cl_float4; [ppc64le] | vec_or [ppc64le] ../../Sources/API/Core/Zip/../System/../System/cl_platform.h:525:5: error: '__cl_char16' does not name a type; did you mean 'cl_char8'? [ppc64le] 525 | __cl_char16 v16; [ppc64le] | cl_char8 [ppc64le] ../../Sources/API/Core/Zip/../System/../System/cl_platform.h:600:5: error: '__cl_uchar16' does not name a type; did you mean 'cl_char16'? [ppc64le] 600 | __cl_uchar16 v16; [ppc64le] | cl_char16 [ppc64le] ../../Sources/API/Core/Zip/../System/../System/cl_platform.h:653:5: error: '__cl_short8' does not name a type; did you mean 'cl_short4'? [ppc64le] 653 | __cl_short8 v8; [ppc64le] | cl_short4 [ppc64le] ../../Sources/API/Core/Zip/../System/../System/cl_platform.h:672:5: error: '__cl_short8' does not name a type; did you mean 'cl_short8'? [ppc64le] 672 | __cl_short8 v8[2]; [ppc64le] | cl_short8 [ppc64le] ../../Sources/API/Core/Zip/../System/../System/cl_platform.h:728:5: error: '__cl_ushort8' does not name a type; did you mean 'cl_ushort4'? [ppc64le] 728 | __cl_ushort8 v8; 2023-May-27 19:37:45 :: [ppc64le] clanlib-2.3.7-alt2_13.src.rpm: remote: build failed 2023-May-27 19:37:45 :: [ppc64le] #100 clanlib-2.3.7-alt2_13.src.rpm: build FAILED 2023-May-27 19:37:45 :: [ppc64le] requesting cancellation of task processing 2023-May-27 19:38:42 :: [x86_64] #100 clanlib-2.3.7-alt2_13.src.rpm: build OK 2023-May-27 19:38:57 :: [i586] #100 clanlib-2.3.7-alt2_13.src.rpm: build OK 2023-May-27 19:40:25 :: [aarch64] #100 clanlib-2.3.7-alt2_13.src.rpm: build OK 2023-May-27 19:42:15 :: [armh] #100 clanlib-2.3.7-alt2_13.src.rpm: build OK 2023-May-27 19:37:45 :: [ppc64le] build FAILED 2023-May-27 19:42:15 :: task #322047 for sisyphus FAILED
reply other threads:[~2023-05-27 19:42 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=girar.task.322047.1.1@gyle.mskdc.altlinux.org \ --to=girar-builder@altlinux.org \ --cc=devel@lists.altlinux.org \ --cc=girar-builder-sisyphus@altlinux.org \ --cc=sisyphus-incominger@lists.altlinux.org \ --cc=viy@altlinux.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
ALT Linux Girar Builder robot reports This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/sisyphus-incominger/0 sisyphus-incominger/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 sisyphus-incominger sisyphus-incominger/ http://lore.altlinux.org/sisyphus-incominger \ sisyphus-incominger@lists.altlinux.org sisyphus-incominger@lists.altlinux.ru sisyphus-incominger@lists.altlinux.com public-inbox-index sisyphus-incominger Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.sisyphus-incominger AGPL code for this site: git clone https://public-inbox.org/public-inbox.git