From: Markus Volk <f_l_k@t-online.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH 2/4] python3: add libxcrypt-native dependency
Date: Sun, 28 May 2023 16:53:13 +0200 [thread overview]
Message-ID: <POIDVR.URDIMNIKV0SE3@t-online.de> (raw)
In-Reply-To: <CANNYZj_0ASF5ERsCgrB3W3qYgGJFwJzXn35cgc6ojQf0fi1Yxg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4478 bytes --]
Am So, 28. Mai 2023 um 16:23:36 +0200 schrieb Alexander Kanavin
<alex.kanavin@gmail.com>:
> But can you show the actual error please?
python3-native for example fails like this:
ERROR: python3-native-3.11.2-r0 do_install:
ExecutionError('/home/flk/poky/build/tmp/work/x86_64-linux/python3-native/3.11.2-r0/temp/run.do_install.4082972',
1, None, None)
ERROR: Logfile of failure stored in:
/home/flk/poky/build/tmp/work/x86_64-linux/python3-native/3.11.2-r0/temp/log.do_install.4082972
Log data follows:
| DEBUG: Executing python function autotools_aclocals
| DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc',
'bit-64', 'x86_64-linux', 'common']
| DEBUG: Python function autotools_aclocals finished
| DEBUG: Executing shell function do_install
| The necessary bits to build these optional modules were not found:
| _crypt
|
| WARNING: exit code 1 from a shell command.
ERROR: Task
(virtual:native:/home/flk/poky/meta/recipes-devtools/python/python3_3.11.2.bb:do_install)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1089 tasks of which 1078 didn't need to
be rerun and 1 failed.
Summary: 1 task failed:
virtual:native:/home/flk/poky/meta/recipes-devtools/python/python3_3.11.2.bb:do_install
Summary: There was 1 ERROR message, returning a non-zero exit code.
ruby-native fails like this:
compiling ../ruby-3.2.2/vm_trace.c
| In file included from ../ruby-3.2.2/include/ruby/ruby.h:42,
| from ../ruby-3.2.2/debug_counter.h:362,
| from ../ruby-3.2.2/string.c:24:
| ../ruby-3.2.2/string.c: In function ‘rb_str_crypt’:
| ../ruby-3.2.2/string.c:10169:35: error: invalid application of
‘sizeof’ to incomplete type ‘struct crypt_data’
| 10169 | data = ALLOCV(databuf, sizeof(struct crypt_data));
| | ^~~~~~
| ../ruby-3.2.2/include/ruby/internal/memory.h:299:7: note: in
definition of macro ‘RB_ALLOCV’
| 299 | ((n) < RUBY_ALLOCV_LIMIT ? \
| | ^
| ../ruby-3.2.2/string.c:10169:12: note: in expansion of macro
‘ALLOCV’
| 10169 | data = ALLOCV(databuf, sizeof(struct crypt_data));
| | ^~~~~~
| compiling ../ruby-3.2.2/missing/setproctitle.c
| compiling ../ruby-3.2.2/missing/strlcpy.c
| compiling ../ruby-3.2.2/missing/strlcat.c
| In file included from /usr/include/stdlib.h:574,
| from ../ruby-3.2.2/include/ruby/defines.h:27,
| from ../ruby-3.2.2/include/ruby/ruby.h:25,
| from ../ruby-3.2.2/debug_counter.h:362,
| from ../ruby-3.2.2/string.c:24:
| ../ruby-3.2.2/string.c:10169:35: error: invalid application of
‘sizeof’ to incomplete type ‘struct crypt_data’
| 10169 | data = ALLOCV(databuf, sizeof(struct crypt_data));
| | ^~~~~~
| ../ruby-3.2.2/include/ruby/internal/memory.h:398:20: note: in
expansion of macro ‘RB_ALLOCV’
| 398 | #define ALLOCV RB_ALLOCV /**< @old{RB_ALLOCV} */
| | ^~~~~~~~~
| ../ruby-3.2.2/string.c:10169:12: note: in expansion of macro
‘ALLOCV’
| 10169 | data = ALLOCV(databuf, sizeof(struct crypt_data));
| | ^~~~~~
| In file included from ../ruby-3.2.2/include/ruby/ruby.h:42,
| from ../ruby-3.2.2/debug_counter.h:362,
| from ../ruby-3.2.2/string.c:24:
| ../ruby-3.2.2/string.c:10169:35: error: invalid application of
‘sizeof’ to incomplete type ‘struct crypt_data’
| 10169 | data = ALLOCV(databuf, sizeof(struct crypt_data));
| | ^~~~~~
| ../ruby-3.2.2/include/ruby/internal/memory.h:301:33: note: in
definition of macro ‘RB_ALLOCV’
| 301 | rb_alloc_tmp_buffer(&(v), (n)))
| | ^
| ../ruby-3.2.2/string.c:10169:12: note: in expansion of macro
‘ALLOCV’
| 10169 | data = ALLOCV(databuf, sizeof(struct crypt_data));
| | ^~~~~~
| ../ruby-3.2.2/string.c:10173:11: warning: implicit declaration of
function ‘crypt_r’; did you mean ‘crypt’?
[-Wimplicit-function-declaration]
| 10173 | res = crypt_r(s, saltp, data);
| | ^~~~~~~
| | crypt
| ../ruby-3.2.2/string.c:10173:9: warning: assignment to ‘char *’
from ‘int’ makes pointer from integer without a cast
[-Wint-conversion]
| 10173 | res = crypt_r(s, saltp, data);
| | ^
[-- Attachment #2: Type: text/html, Size: 6487 bytes --]
next prev parent reply other threads:[~2023-05-28 14:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 13:32 [oe-core][PATCH 1/4] ell: upgrade 0.56 -> 0.57 Markus Volk
2023-05-27 13:32 ` [oe-core][PATCH 2/4] python3: add libxcrypt-native dependency Markus Volk
2023-05-28 13:39 ` Alexander Kanavin
2023-05-28 13:56 ` Markus Volk
[not found] ` <17635252DFD4EDDE.6918@lists.openembedded.org>
2023-05-28 13:41 ` Alexander Kanavin
2023-05-28 14:03 ` Markus Volk
2023-05-28 14:23 ` Alexander Kanavin
2023-05-28 14:53 ` Markus Volk [this message]
2023-05-28 15:01 ` Alexander Kanavin
2023-05-28 15:08 ` Markus Volk
2023-05-28 15:16 ` Alexander Kanavin
2023-05-29 7:08 ` Richard Purdie
[not found] ` <ZG5FVR.L4YKBKAES08S3@googlemail.com>
2023-05-29 12:34 ` Richard Purdie
2023-06-03 17:51 ` Markus Volk
2023-06-03 18:20 ` Alexander Kanavin
2023-06-04 19:53 ` Markus Volk
2023-05-27 13:32 ` [oe-core][PATCH 3/4] ruby: " Markus Volk
2023-05-27 13:32 ` [oe-core][PATCH 4/4] shadow: " Markus Volk
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=POIDVR.URDIMNIKV0SE3@t-online.de \
--to=f_l_k@t-online.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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