| # 10:08:21 | devster31 | ok, I tried armv8-rpi3 sample, but the cortex-a53 reports itself as armv7l in 32-bit mode, so unless you enable 64 bit mode (and use aarch64) suffix for the rpi3 should still be v7l |
| # 10:08:50 | devster31 | this is an issue for python stuff, which looks for armv8 in the rpi3 instead of armv7l as it is |
| # 13:49:58 | diorcety | joins #crosstool-ng |
| # 16:55:50 | blueness | quits : Quit: blueness |
| # 17:04:52 | blueness | joins #crosstool-ng |
| # 17:06:49 | diorcety | quits : Read error: Connection reset by peer |
| # 17:16:16 | blueness | quits : Quit: blueness |
| # 17:26:36 | blueness | joins #crosstool-ng |
| # 17:41:06 | devster31 | trying to build libnuma but it complains that #error "Add syscalls for your architecture or update kernel headers" , does it refer to the pc I'm using to cross-compile? because I selected the option to build and check the kernel headers in ct-ng |
| # 17:55:08 | enunes | devster31: apparently this libnuma doesn't support arm |
| # 17:59:17 | enunes | devster31: I don't own a rpi3, but armv8 should be 32-bit mode, isn't it the raspberry pi distributed kernel which is configured to support armv7 ? |
| # 19:28:36 | diorcety | joins #crosstool-ng |
| # 21:26:29 | diorcety | quits : Read error: Connection reset by peer |
| # 22:13:12 | devster31 | it should be, cat /proc/cpuinfo reports armv7l |