00:02:32 DataLinkDroid [~DataLinkD@1.124.184.43] has joined #ccl 00:05:01 rme [~rme@50.43.161.98] has joined #ccl 00:06:26 -!- mdc [~mdc@indigo.entity.com] has quit [Read error: Connection reset by peer] 00:15:29 mdc [~mdc@indigo.entity.com] has joined #ccl 01:10:05 -!- rme [~rme@50.43.161.98] has quit [Quit: rme] 03:02:34 rme [~rme@50.43.161.98] has joined #ccl 04:04:20 -!- rme [~rme@50.43.161.98] has quit [Quit: rme] 05:46:08 -!- DataLinkDroid [~DataLinkD@1.124.184.43] has quit [Quit: Bye] 06:04:27 woudshoo [~user@ironhead.xs4all.nl] has joined #ccl 06:23:42 ffigen does not build on raspbian, so i guess i'll just switch to cffi+swig unless someone can tell me how to get around this: http://paste.lisp.org/display/131553 06:56:47 -!- woudshoo [~user@ironhead.xs4all.nl] has quit [Ping timeout: 244 seconds] 06:57:44 You seem to be missing a library. Get it. 07:09:00 you seem to be having no clue. 07:10:46 make[3]: *** No rule to make target `../build-armv6l-unknown-linux-gnu/libiberty/libiberty.a', needed by `build/genmodes'. Stop. 07:12:57 well, as you don't have actual experience, you can't help me beyond reading the obvious back to me. i appreciate that, but it does not actually solve any problem. 07:13:46 Why don't you debug that libiberty problem? 07:28:03 -!- Vivitron [~Vivitron@pool-98-110-213-33.bstnma.fios.verizon.net] has quit [Quit: trivial-irc-0.0.3] 09:15:25 milanj [~milanj_@178-223-156-24.dynamic.isp.telekom.rs] has joined #ccl 10:03:29 Vivitron [~Vivitron@pool-98-110-213-33.bstnma.fios.verizon.net] has joined #ccl 10:14:32 i think the problem with building ffigen is that it makes assumptions about the linux distribution that are not met by raspbian 10:15:08 so if anyone could share some information on the distribution that can be used to build ffigen, it'd be helpful. 10:24:21 It 10:26:06 It's supposed to be self-contained; it's basically the GCC build process, which is pretty portable, and I doubt if it knows anything about Linux distributions. 10:26:45 Stupid question (that I might as well ask): is the system clock set properly ? 10:28:44 yes 10:29:15 the bit that i pasted was just one of the problems. later on, kernel include files were not found. 10:29:54 Surprising that you need them, but what happens if you install kernel include files ? 10:30:19 I have them, but they're in a subdirectory that was not in the include path of the compiler. 10:30:51 there's an option to apt-get that installs all of the packages needed to build a target package; you're basically trying to build gcc. 10:32:51 Hm, I'm not doubting that you know what you're saying, but I still wonder why the build looks in ../build-armv61-unknown-linux-gnu/libiberty/... when the correct path would be ../build/libiberty/... 10:33:44 Not sure, but I wonder if the ffigen makefile assumes armv7 10:33:45 I've got past that with a symlink, but much later in the build process, I ran into the include path problem, which was in the same class (i.e. could be fixed by a symlink in the build directory) 10:34:09 That'd explain why there were also some errors regarding unsupported instructions. 10:34:29 Yep. 10:35:08 Okay, so that'd also mean that a compiled ffigen would probably not help unless it had been specifically built to run on ARMv6. 10:35:21 I guess I should go with cffi then :/ 10:36:01 Yeah. It might take a whole hour to change that. When in doubt, cffi. 10:36:28 Okay, thanks! 10:36:42 I was kidding. 10:37:17 "portable ffi" always sounds like an oxymoron. 10:37:49 Hey, I'm all willing to not use cffi, but I really lack the expertise and patience to fix GCC builds. 10:38:29 Can you wait < 1 hr ? "armv7" vs "armv6" somewhere probably isn't too deep ... 10:38:41 Sure! Thanks! 10:40:22 if you look at ffigen-linuxarm/Makefile around line 11 ... 10:41:01 *H4ns* looks 10:42:02 :/ 10:43:17 Ok, I changed that to armv6l and build-armv6l-unknown-linux-gnu 10:44:31 Trying to remember if the 'gnueabi' stuff matters. 4.1.0 was the first version to support the ARM eabi, which changed structure alignment rules slightly. 10:47:11 My first inclination is to make the armv6l case parallel the armv7l case except for the obvious (7->6), and there's probably some wondrous way of doing that by pattern matching but I don't remember. 10:51:37 Could you try that (just repeat the test for armv7 to test for armv6l and keep everything else the same except for the obvious substitution of 7 for 6) ? I actually have a raspberry pi here but haven't unpacked it yet. 10:52:34 Ok, compiling. I'll keep you posted, thanks for the help! 10:53:39 If you have a build running and don't want to interrupt it, a test case involves parsing a header with a structure that defines two fields, an int and a double. The double should be aligned on a 64-bit boundary in the output. Some linux things (struct stat, maybe ?) are sensitive to that. 10:54:44 I just restarted the build. Will probably take a few hours, so I might not have results until tonight. 10:55:29 If the double isn't on a 64-bit boundary in the .ffi file, try editing the makefile to say ...-gnueabi. 10:56:19 It'll probably take longer than an hour, but I should probably set up a raspberry pi and try it myself. 10:56:48 I'm using that now. Maybe I'll have some results before you've set up yours. 11:14:08 yakov [~yakov@spb.nexenta.com] has joined #ccl 12:13:13 -!- Vivitron [~Vivitron@pool-98-110-213-33.bstnma.fios.verizon.net] has quit [Quit: trivial-irc-0.0.3] 13:07:16 -!- pirateking-_- [~piratekin@c-67-169-182-169.hsd1.ca.comcast.net] has quit [Quit: pirateking-_-] 14:48:21 -!- bzzbzz [~franco@modemcable216.122-57-74.mc.videotron.ca] has quit [Remote host closed the connection] 15:39:49 Zetetic [5284f9bf@gateway/web/freenode/ip.82.132.249.191] has joined #ccl 15:51:29 rme [~rme@50.43.161.98] has joined #ccl 15:54:24 -!- rme [rme@6D31FCC9.2729170C.699BA7A6.IP] has quit [Ping timeout] 15:55:37 -!- rme [~rme@50.43.161.98] has quit [Ping timeout: 246 seconds] 16:03:30 rme [~rme@50.43.145.91] has joined #ccl 16:06:27 pnpuff [~pnpuff@gateway/tor-sasl/pnpuff] has joined #ccl 17:11:20 pirateking-_- [~piratekin@c-67-169-182-169.hsd1.ca.comcast.net] has joined #ccl 17:11:58 pnpuff` [~pnpuff@gateway/tor-sasl/pnpuff] has joined #ccl 17:12:15 -!- pnpuff [~pnpuff@gateway/tor-sasl/pnpuff] has quit [Ping timeout: 276 seconds] 17:19:06 -!- sellout42 [~Adium@c-98-245-92-119.hsd1.co.comcast.net] has quit [Quit: Leaving.] 17:26:33 -!- yakov [~yakov@spb.nexenta.com] has quit [Remote host closed the connection] 17:57:28 -!- pnpuff` [~pnpuff@gateway/tor-sasl/pnpuff] has left #ccl 17:58:40 pnpuff [~pnpuff@gateway/tor-sasl/pnpuff] has joined #ccl 18:14:23 sellout42 [~Adium@65.101.242.214] has joined #ccl 18:15:34 -!- sellout42 is now known as sellout 18:34:35 -!- Zetetic [5284f9bf@gateway/web/freenode/ip.82.132.249.191] has quit [Ping timeout: 245 seconds] 19:14:17 -!- harshrc [~harshrc@moat3.centtech.com] has quit [Remote host closed the connection] 19:24:13 -!- milanj [~milanj_@178-223-156-24.dynamic.isp.telekom.rs] has quit [Quit: Leaving] 19:51:32 -!- pnpuff [~pnpuff@gateway/tor-sasl/pnpuff] has quit [Quit: pnpuff] 20:05:53 -!- sellout [~Adium@65.101.242.214] has quit [Quit: Leaving.] 20:25:26 sellout42 [~Adium@c-98-245-92-119.hsd1.co.comcast.net] has joined #ccl 20:25:54 -!- sellout42 is now known as sellout 21:23:23 -!- pirateking-_- [~piratekin@c-67-169-182-169.hsd1.ca.comcast.net] has quit [Quit: pirateking-_-] 21:55:37 -!- rme [~rme@50.43.145.91] has quit [Quit: rme] 21:56:17 gbyers: the ffigen build failed again, and unfortunately, the error messages scrolled off my tmux buffer so i can't be specific as to where it failed :( 21:56:48 gbyers: have you been able to build it on your pi? 22:30:38 pirateking-_- [~piratekin@c-67-169-182-169.hsd1.ca.comcast.net] has joined #ccl 22:41:37 -!- sellout [~Adium@c-98-245-92-119.hsd1.co.comcast.net] has quit [Remote host closed the connection] 22:43:13 sellout42 [~Adium@c-98-245-92-119.hsd1.co.comcast.net] has joined #ccl 23:01:22 DataLinkDroid [~DataLinkD@1.150.181.215] has joined #ccl