-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[C++] error: implicit conversion loses integer precision: 'size_t' (aka 'unsigned long') to 'const int' .... #37735
Comments
ghost
added
the
Type: bug
label
Sep 15, 2023
Since you are building manually, I assume you can change the source code. Can you update the line to const int calls = static_cast<int>(backtrace(buffer, static_cast<int>(sizeof(buffer) / sizeof(void*)))); and then try again? |
Thank You ! |
Ver ystrange, can it be that pyarrow was not instaleld correctly ? it states:
|
kou
changed the title
error: implicit conversion loses integer precision: 'size_t' (aka 'unsigned long') to 'const int' ....
[C++] error: implicit conversion loses integer precision: 'size_t' (aka 'unsigned long') to 'const int' ....
Sep 15, 2023
kou
added a commit
to kou/arrow
that referenced
this issue
Oct 4, 2023
It's caused by `backtrace()` and `backtrace_symbols_fd()` signatures are different on Linux and FreeBSD (`int` vs `size_t`). Linux: ```c extern int backtrace (void **__array, int __size) __nonnull ((1)); extern void backtrace_symbols_fd (void *const *__array, int __size, int __fd) __THROW __nonnull ((1)); ``` FreeBSD: ```c size_t backtrace(void **, size_t); int backtrace_symbols_fd(void *const *, size_t, int); ``` We can use `auto` to ignore the difference.
kou
added a commit
that referenced
this issue
Oct 10, 2023
### Rationale for this change It's caused by `backtrace()` and `backtrace_symbols_fd()` signatures are different on Linux and FreeBSD (`int` vs `size_t`). Linux: ```c extern int backtrace (void **__array, int __size) __nonnull ((1)); extern void backtrace_symbols_fd (void *const *__array, int __size, int __fd) __THROW __nonnull ((1)); ``` FreeBSD: ```c size_t backtrace(void **, size_t); int backtrace_symbols_fd(void *const *, size_t, int); ``` ### What changes are included in this PR? Use `auto` to ignore the difference. ### Are these changes tested? Yes on FreeBSD 12. ### Are there any user-facing changes? No. * Closes: #37735 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
JerAguilon
pushed a commit
to JerAguilon/arrow
that referenced
this issue
Oct 23, 2023
…pache#38004) ### Rationale for this change It's caused by `backtrace()` and `backtrace_symbols_fd()` signatures are different on Linux and FreeBSD (`int` vs `size_t`). Linux: ```c extern int backtrace (void **__array, int __size) __nonnull ((1)); extern void backtrace_symbols_fd (void *const *__array, int __size, int __fd) __THROW __nonnull ((1)); ``` FreeBSD: ```c size_t backtrace(void **, size_t); int backtrace_symbols_fd(void *const *, size_t, int); ``` ### What changes are included in this PR? Use `auto` to ignore the difference. ### Are these changes tested? Yes on FreeBSD 12. ### Are there any user-facing changes? No. * Closes: apache#37735 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
loicalleyne
pushed a commit
to loicalleyne/arrow
that referenced
this issue
Nov 13, 2023
…pache#38004) ### Rationale for this change It's caused by `backtrace()` and `backtrace_symbols_fd()` signatures are different on Linux and FreeBSD (`int` vs `size_t`). Linux: ```c extern int backtrace (void **__array, int __size) __nonnull ((1)); extern void backtrace_symbols_fd (void *const *__array, int __size, int __fd) __THROW __nonnull ((1)); ``` FreeBSD: ```c size_t backtrace(void **, size_t); int backtrace_symbols_fd(void *const *, size_t, int); ``` ### What changes are included in this PR? Use `auto` to ignore the difference. ### Are these changes tested? Yes on FreeBSD 12. ### Are there any user-facing changes? No. * Closes: apache#37735 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
dgreiss
pushed a commit
to dgreiss/arrow
that referenced
this issue
Feb 19, 2024
…pache#38004) ### Rationale for this change It's caused by `backtrace()` and `backtrace_symbols_fd()` signatures are different on Linux and FreeBSD (`int` vs `size_t`). Linux: ```c extern int backtrace (void **__array, int __size) __nonnull ((1)); extern void backtrace_symbols_fd (void *const *__array, int __size, int __fd) __THROW __nonnull ((1)); ``` FreeBSD: ```c size_t backtrace(void **, size_t); int backtrace_symbols_fd(void *const *, size_t, int); ``` ### What changes are included in this PR? Use `auto` to ignore the difference. ### Are these changes tested? Yes on FreeBSD 12. ### Are there any user-facing changes? No. * Closes: apache#37735 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug, including details regarding any error messages, version, and platform.
New to al lthe stuff compiling.
Running FreeBSD 13.2-RELEASE-p1 trying to install pyarrow and i was following https://arrow.apache.org/docs/developers/python.html#using-system-and-bundled-dependencies .
on the step of make -j4 encountered this error.
Tried just to use "make" same problem , tried "make clean && make" same issue.
As im no C guy, checked actuall file which turs to my error:
Component(s)
C++, Python
The text was updated successfully, but these errors were encountered: