00:13:16  * not-an-aardvarkjoined
00:17:08  * rmgquit (Remote host closed the connection)
00:35:06  * rmgjoined
00:40:20  * rmgquit (Ping timeout: 260 seconds)
01:01:17  * node-ghjoined
01:01:17  * node-ghpart
01:29:20  * rmgjoined
01:34:00  * rmgquit (Ping timeout: 260 seconds)
01:56:47  * rmgjoined
02:01:32  * rmgquit (Ping timeout: 260 seconds)
02:24:00  * rmgjoined
02:28:36  * rmgquit (Ping timeout: 260 seconds)
02:50:59  * rmgjoined
02:55:40  * rmgquit (Ping timeout: 260 seconds)
03:18:04  * rmgjoined
03:22:43  * rmgquit (Ping timeout: 260 seconds)
03:45:06  * rmgjoined
03:49:48  * rmgquit (Ping timeout: 260 seconds)
04:12:11  * rmgjoined
04:16:52  * rmgquit (Ping timeout: 260 seconds)
04:39:16  * rmgjoined
04:43:56  * rmgquit (Ping timeout: 260 seconds)
05:06:28  * rmgjoined
05:10:59  * rmgquit (Ping timeout: 260 seconds)
05:23:03  * italoacasasquit (Quit: Connection closed for inactivity)
05:33:38  * rmgjoined
05:38:04  * rmgquit (Ping timeout: 260 seconds)
06:00:33  * rmgjoined
06:05:08  * rmgquit (Ping timeout: 260 seconds)
06:27:36  * rmgjoined
06:32:12  * rmgquit (Ping timeout: 260 seconds)
07:21:50  * rmgjoined
07:26:48  * rmgquit (Ping timeout: 260 seconds)
09:23:42  * sgimenojoined
10:04:15  * rmgjoined
10:09:12  * rmgquit (Ping timeout: 260 seconds)
10:54:13  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
11:25:07  * thealphanerdquit (Quit: farewell for now)
11:25:38  * thealphanerdjoined
12:20:03  * jenkins-monitorquit (Remote host closed the connection)
12:20:12  * jenkins-monitorjoined
12:36:56  * italoacasasjoined
13:14:07  * rmgjoined
13:18:39  * rmgquit (Ping timeout: 260 seconds)
13:41:14  * rmgjoined
13:45:44  * rmgquit (Ping timeout: 260 seconds)
13:48:51  * lance|afkchanged nick to lanceball
14:38:49  * chorrelljoined
15:22:12  * mmassijoined
15:24:13  <mmassi>Hi! I am trying to build node on a ARMv9 (a Lego EV3 brick, Debian Linux, TI Sitara AM1808 (ARM926EJ-S core)) but I get an error building V8:
15:24:38  <mmassi>../deps/v8/src/base/atomicops_internals_arm_gcc.h:260:4: error: #error "Your CPU's ARM architecture is not supported yet" # error "Your CPU's ARM architecture is not supported yet"
15:24:58  <mmassi>anybody knows what I should define to get past this?
15:25:16  <mmassi>note that there *are* node packages that are already working
15:25:32  <mmassi>they are the Debian armel ones
15:25:47  <mmassi>but it is an ancient node 0.10 without snapshot
15:25:57  <mmassi>I wanted to see if I could have a newer one
15:26:40  <mmassi>second note: even if it is dog slow, I am not cross compiling: the error happens on the ARM system itself
15:27:46  <mmassi>final note: I am building from the node-v6.9.1 source tree
15:32:39  * node-ghjoined
15:32:40  * node-ghpart
15:42:41  <jbergstroem>mmassi: try changing architecture passed to configure?
15:43:03  <mmassi>I did not pass any arch, just thought it would figure out itself
15:43:24  <mmassi>but it seems that the file that gives the error has no option for armv9
15:43:41  <mmassi>I checked atomicops_internals_arm_gcc.h
15:44:11  <mmassi>and it seems to me that it wants either a v7 or a v5
15:44:38  <mmassi>but my knowledge of arm archs is... nothing :-/
15:44:47  <mmassi>what should I pass to configure?
15:45:51  <mmassi>what puzzles me is that there *are* node packages for this box
15:46:17  <mmassi>so it must be possible to build it (unless the v8 team dropped armv9 support at some point)
15:46:29  <mmassi>(which is something I don't know)
15:47:06  <mmassi>btw, googling v8 and armv9 is next to impossible... the v8 and v9 get mixed up
15:49:25  <joaocgreis>mmassi: I don't know about armv9, at least we don't test on it. You might be able to build if you force it to build a armv7 binary, run this before configure: export CC="gcc -march=armv7-a" CXX="g++ -march=armv7-a"
15:50:20  <jbergstroem>joaocgreis: wouldn't we pass that properly if we pass DESTCPU?
15:50:23  <jbergstroem>and ARCH
15:50:27  <jbergstroem>to gyp, i mean
15:54:29  <joaocgreis>jbergstroem: not sure if there's a combination of options to pass to configure that would set it up right, there's some autodetection inside so I'd have to check. --dest-cpu can only be arm or arm64, and that file is looking for the __ARM_ARCH_xx compiler defines
15:54:46  <jbergstroem>joaocgreis: yeah thats true.
15:54:57  <jbergstroem>mmassi: if you find a combination that works perhasp a patch to us would be good :)
16:08:19  <mmassi>I did it, the build started... it will take hours to get to that point
16:08:30  <jbergstroem>use ccache!
16:08:37  <mmassi>I'll keep you posted here :-)
16:09:06  <mmassi>does ccache have a meaning if I change defines like that basic one?
16:09:26  <mmassi>I mean, wouldn't this define change invalidate the cache?
16:11:23  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
16:12:03  <mmassi>this is a 300Mhz CPU with 64MB of ram, using a micro sd as hard drive... I just wanted to see if I could get the build env right, then I'll switch to cross compiling
16:13:08  <jbergstroem>sure, if you change artitecture constantly you'd be out of ccache luck
16:21:43  <joaocgreis>mmassi: about cc, if you need a reference this is how we do it: https://github.com/nodejs/build/pull/244/files
16:37:07  <mmassi>jaocgreis: I actually already have instructions to set up a cross compiling env for my target: http://www.ev3dev.org/docs/tutorials/using-docker-to-cross-compile/
16:38:00  <mmassi>it is docker based with qemu to run the native binaries, and the compiler is arm-linux-gnueabi-gcc
16:50:29  * rmgjoined
16:55:39  * rmgquit (Ping timeout: 260 seconds)
17:06:15  * rmgjoined
18:26:36  <mmassi>bummer... now I see that the cpu of the EV3 is an ARMv5 and not an ARMv9 (the "ARM926EJ-S" was confusing me)
18:27:02  <mmassi>so it is not supported by modern v8, and therefore by modern node
18:28:11  <mmassi>do I stand a chance trying to build node-chakracore-7.0.0-pre10 on this linux ARMv5 box?
18:28:32  <mmassi>I mean, I know it's preview, but is it worth trying?
19:41:18  * not-an-aardvarkjoined
20:12:29  * lanceballchanged nick to lance|afk
20:56:43  * node-ghjoined
20:56:44  * node-ghpart
20:58:42  * lance|afkchanged nick to lanceball
21:22:11  * node-ghjoined
21:22:11  * node-ghpart
21:22:16  <joaocgreis>mmassi: Windows 10 iot is for armv7+ so chakra is unlikely to work on anything before that, but I don't know. You may want to dig in https://github.com/nodejs/node/issues?utf8=%E2%9C%93&q=armv5 but it doesn't look promising
22:11:12  * lanceballchanged nick to lance|afk