| # 00:14:00 | ubergeek42 | quits : Read error: Operation timed out |
| # 00:17:26 | ubergeek42 | joins #crosstool-ng |
| # 01:55:47 | nandub | joins #crosstool-ng |
| # 01:59:08 | nandub_ | quits : Ping timeout: 255 seconds |
| # 03:29:32 | devcoder | quits : Quit: devcoder |
| # 03:44:49 | Eddiie | Anyone home? |
| # 03:45:06 | Eddiie | when I ./ct-ng build it says Must NOT be root to run crosstool-ng |
| # 03:45:24 | Eddiie | so I make a user that is not root |
| # 03:45:37 | Eddiie | repeat all the steps |
| # 03:45:56 | Eddiie | ./ct-ng build ... |
| # 03:46:20 | Eddiie | command not found messages - CT_DoLog |
| # 03:46:59 | Eddiie | This is using the latest from hg clone http://crosstool-ng.org/hg/crosstool-ng |
| # 03:47:15 | Eddiie | Using the release version is OK |
| # 03:52:41 | Eddiie | Anyone? |
| # 03:54:51 | tkil | as the new user, did you start over from scratch entirely? |
| # 03:55:07 | Eddiie | actually, yes |
| # 03:55:07 | tkil | meaning, new download, new configure local... |
| # 03:55:23 | Eddiie | same result as dirty system |
| # 03:55:51 | tkil | did you do some config before build? |
| # 03:55:58 | tkil | gah, back in a bit, my client is being stupid. |
| # 03:56:07 | Eddiie | yes |
| # 03:56:27 | Eddiie | ct-ng menuconfig |
| # 03:56:44 | tkil | back. |
| # 03:56:51 | Eddiie | great |
| # 03:57:06 | tkil | ok, that's very odd. what os are you running on? |
| # 03:57:33 | Eddiie | ah |
| # 03:57:41 | Eddiie | good question |
| # 03:57:53 | Eddiie | this is happening on my little NSLU2 slug thing |
| # 03:58:14 | Eddiie | armeb |
| # 03:58:21 | tkil | is the shell a full copy of "bash", or is it one of the stripped-down ones (ash, dash, busybox...) |
| # 03:58:34 | Eddiie | dash |
| # 03:58:46 | Eddiie | ok lemme change |
| # 04:01:21 | Eddiie | ok bash |
| # 04:01:44 | Eddiie | samn |
| # 04:01:51 | Eddiie | same |
| # 04:02:49 | Eddiie | if I try this on the release version, this does not happen. I need the unreleased because there is support for newer kernels, which is what I am ultimately trying to do. |
| # 04:03:47 | Eddiie | also, if I do the unreleased on my i486 box, it works ok, too... |
| # 04:04:10 | Eddiie | something with the new code, I am thinking |
| # 04:04:15 | tkil | just use 1.17 + custom location for kernel. |
| # 04:04:23 | tkil | (or whatever the lateset release is). |
| # 04:04:29 | tkil | and send to the mailing list, there are more eyes there. |
| # 04:04:58 | Eddiie | true that |
| # 04:05:19 | Eddiie | dont understand what you mean by + custom location for kernel |
| # 04:05:37 | tkil | instead of selecting a kernel from the list of options, there should be "custom kernel tarball" or words to that effect. |
| # 04:05:59 | Eddiie | checking |
| # 04:06:23 | Eddiie | actually, it will take 2 days for 1.17.0 to build on the NSLU2 lol |
| # 04:06:28 | Eddiie | I'll have to get back to you |
| # 04:06:45 | tkil | well, just testing for CT_blah functions should be faster than that... |
| # 04:07:00 | tkil | and if your CPU is that slow, cross compiling is probably a better choice than native, but whatever floats your boat. :) |
| # 04:08:39 | Eddiie | I've tried the cross compiling thing.. I get many warnings about ARCH not matching my archetititure .. i486 does not match ARM .. eventually I get a deb, move it on over, install it............ and |
| # 04:09:10 | Eddiie | get archetitirutere mismatches or sub- archtututiertete (I really need to learn how to spell that word). |
| # 04:10:19 | tkil | well, that's what cross compiling is supposed to fix... but i'm not sure what's going wrong (and don't have the time/energy to debug it, sadly). but you might take a look at something like buildroot or openembedded. |
| # 04:10:53 | tkil | i know that i can rebuild my embedded project in 2 hours total (from source, including toolchain on host) and update it in <5min ... on my core i7. no idea how long it would take on my 300MHz ppc. :) |
| # 04:11:13 | Eddiie | neener neener |
| # 04:12:04 | Eddiie | I obviously don't know what I am doing. Appreciate your help anyway |
| # 04:20:17 | nandub | quits : Read error: Connection reset by peer |
| # 04:20:50 | nandub | joins #crosstool-ng |
| # 04:23:03 | Eddiie | whee I think it is going to work now... |
| # 04:23:40 | Eddiie | blah new error |
| # 07:03:43 | smartin | joins #crosstool-ng |
| # 08:34:02 | plfiorini | quits : Quit: Leaving |
| # 09:17:00 | plfiorini | joins #crosstool-ng |
| # 10:07:04 | nandub | quits : Read error: Operation timed out |
| # 11:20:24 | plfiorini | quits : Quit: Leaving |
| # 12:10:51 | y_morin | joins #crosstool-ng |
| # 13:49:40 | smartin | y_morin: hi |
| # 13:51:14 | smartin | any reason to not use CT_TARGET in CT_WORK_DIR? except that the former is computed after the latter... |
| # 14:02:22 | y_morin | smartin: Hello! CT_TARGET is used as part as the build dir, which is a sub-dir of CT_WORK_DIR. |
| # 14:03:27 | y_morin | smartin: CT_WORK_DIR is not dependent on the target, as it contains all sub-dirs that are not target-dependent: tarballs, sources, build-tools wrappers... |
| # 14:03:45 | y_morin | smartin: What would be the use-case for you to include CT_TARGET in CT_WORK_DIR? |
| # 14:07:20 | smartin | y_morin: so if i want to build several toolchains, i don't need to define different work_dirs, things won't mess up... i was not aware of this! |
| # 14:08:13 | y_morin | smartin: exactly. As ct-ng does *not* have per-arch patches, the sources will all be the same, so we don't need to differentiate sources for different archs. |
| # 14:08:36 | y_morin | smartin: Only the build-dir contains target-specific stuff, and that one already contains the tuple. |
| # 14:08:52 | y_morin | smartin: However, if you want to build two toolchains with the same tuple, you're screwed. |
| # 14:09:20 | y_morin | smartin: For example: one can not really differentiate a toolchain for armv5 from another for armv6 only by looking at the tuple. |
| # 14:09:50 | y_morin | smartin: however, we now have such support in the repository, now, and that will be available with the next release. |
| # 14:10:37 | y_morin | smartin: see: http://crosstool-ng.org/hg/crosstool-ng/rev/9d0b37f08a10 |
| # 14:10:49 | smartin | ah! good to know |
| # 16:34:11 | plfiorini | joins #crosstool-ng |
| # 17:42:11 | diorcety | joins #crosstool-ng |
| # 18:59:54 | plfiorini | quits : Ping timeout: 276 seconds |
| # 19:00:42 | plfiorini | joins #crosstool-ng |
| # 20:57:16 | y_morin | smartin: Thank you! Sorry it needed a third attempt... :-/ |
| # 21:03:20 | smartin | y_morin: it's ok, i've just had some hard time with hg :P |
| # 21:09:58 | y_morin | smartin: running a test-build here, will push soonish. Thank you! :-) |
| # 21:23:13 | Eddiie | cool |
| # 21:23:30 | Eddiie | when is new release looking like it will be out? |
| # 22:11:02 | y_morin | Eddiie: Next release is scheduled for the en of the month. |
| # 22:23:11 | devcoder | joins #crosstool-ng |
| # 22:46:42 | alan_o | joins #crosstool-ng |
| # 23:14:23 | smartin | quits : Quit: leaving |
| # 23:54:08 | y_morin | quits : Quit: Nighty Night! |