| # 06:49:52 | sfan5|OFF | is now known as: sfan5 |
| # 06:52:58 | sspiff | joins #crosstool-ng |
| # 06:52:59 | sspiff | quits : Changing host |
| # 06:52:59 | sspiff | joins #crosstool-ng |
| # 06:59:56 | sfan5 | is now known as: sfan5|OFF |
| # 07:17:07 | sfan5|OFF | is now known as: sfan5 |
| # 07:38:55 | smartin | joins #crosstool-ng |
| # 09:05:25 | knommad | joins #crosstool-ng |
| # 09:12:02 | sfan5 | can i use crosstool-ng for build != host = target ? |
| # 10:00:20 | knommad | parts #crosstool-ng |
| # 10:05:55 | kos_tom | sfan5: no |
| # 10:06:04 | kos_tom | sfan5: at the moment, ct-ng does not support "cross-native" mode |
| # 10:06:16 | kos_tom | sfan5: of course, if you're interested, I'm pretty sure Yann will welcome patches to add this |
| # 10:16:58 | sfan5 | i'm trying to compile a arm-unknown-linux-gnu toolchain but i get: /tmp/crosstc-build/build/src/gcc-4.3.2/libgcc/../gcc/unwind-dw2.c:1413: internal compiler error: in arm_dbx_register_number, at config/arm/arm.c:18266 |
| # 10:48:13 | kos_tom | sfan5: http://comments.gmane.org/gmane.comp.gcc.cross-compiling/9970 ? |
| # 10:49:37 | sfan5 | so, how do i change the options? |
| # 11:04:50 | sspiff | quits : Remote host closed the connection |
| # 11:06:43 | sspiff | joins #crosstool-ng |
| # 11:06:44 | sspiff | quits : Changing host |
| # 11:06:44 | sspiff | joins #crosstool-ng |
| # 11:18:19 | sh4rm4 | quits : Remote host closed the connection |
| # 12:29:02 | sh4rm4 | joins #crosstool-ng |
| # 13:47:12 | alan_o | joins #crosstool-ng |
| # 15:15:28 | sspiff | quits : Remote host closed the connection |
| # 16:11:50 | sfan5 | [ERROR] configure: error: forced unwind support is required || how to fix that? |
| # 16:12:57 | sfan5 | nvm |
| # 16:31:39 | codyps | quits : Ping timeout: 260 seconds |
| # 16:45:21 | smartin | quits : Quit: back later |
| # 17:03:51 | codyps | joins #crosstool-ng |
| # 17:54:04 | smartin | joins #crosstool-ng |
| # 17:57:36 | y_morin | joins #crosstool-ng |
| # 18:01:43 | y_morin | sfan5, kos_tom: Indeed cross-native is not supported (by lack of time on my part), so any (sane!) patch will be welcome! :-) |
| # 18:03:02 | sfan5 | y_morin: i can't find any working combination of gcc, binutils and glibc for an arm-unknown-linux toolchain |
| # 18:03:19 | y_morin | sfan5: arm-unknown-linux-gnu <- uese the old ARM ABI (aka OABI). This is deprecated, and crosstol-NG, although has an option to disable EABI, does not really support OABI. |
| # 18:03:34 | y_morin | -> s/uese/uses/ |
| # 18:03:43 | sfan5 | so i should enable the new abi? |
| # 18:04:16 | y_morin | sfan5: unless you have a *very* good reason to not enable EABI, yes you should. |
| # 18:04:26 | y_morin | sfan5: Note that this is the default in crosstool-NG |
| # 18:04:56 | sfan5 | i didn't know if the target uses the new abi... |
| # 18:05:01 | sfan5 | so i disabled it |
| # 18:05:52 | y_morin | sfan5: EABI is purely a software thing. |
| # 18:06:28 | y_morin | sfan5: there's no requirement toward the CPU (except maybe it needs a few instructions that are missing in armv4) |
| # 18:15:18 | sfan5 | ok |
| # 18:20:45 | sfan5 | thanks for your help :) |
| # 18:41:21 | sfan5 | how do i add a toolchain to my $PATH |
| # 18:41:22 | sfan5 | ? |
| # 18:44:59 | sfan5 | or can i copy the content of $HOME/x-tools/arm-unknown-linux-gnueabi into /usr ? |
| # 18:52:16 | sfan5 | i'll copy it to /usr |
| # 19:30:49 | smartin | quits : Quit: leaving |
| # 19:30:58 | y_morin | sfan5: What I usually do, is have /opt writable by my user, and I install all my toolchains in /opt/x-tools/TUPLE. |
| # 19:31:13 | sfan5 | ok |
| # 19:31:47 | y_morin | sfan5: Then, my login scripts add /opt/x-tools/*/bin to my PATH (eg.: for d in /opt/x-tools/*/bin; do PATH="${PATH}:${d}"; done ) |
| # 19:32:16 | y_morin | sfan5: moving to /usr is a bit dangerous. You risk overwriting your system files (eg. libs) |
| # 19:32:30 | sfan5 | i did it carefully |
| # 19:32:46 | y_morin | sfan5: Also, do not run ct-ng as root, it's dangerous, too (as ct-ng does a 'rm -rf' on the install dir). |
| # 19:33:06 | y_morin | sfan5: Sure, it can be doen safely, I was just saying to be careful! ;-) |
| # 19:33:10 | sfan5 | :D |
| # 19:33:30 | sfan5 | i think i'll use your /opt method next time |
| # 19:34:09 | y_morin | sfan5: alternatively, you can have your login script (eg. .profile, or .bashrc) scan ${HOME}/x-tools/*/bin, and add that to $PATH as I do for /opt. |
| # 19:35:23 | y_morin | sfan5: it really depends what you want to do with your toolchains: are you the only user? If so, keep in ${HOME}/x-tool, otherwise install them in /opt (or /usr/local/TUPLE or whatever is accessible to all users). |
| # 19:35:51 | sfan5 | i'm the only user |
| # 19:37:27 | sfan5 | that gives me an idea.... someone could make a public root-/v-server that contains a big collection of toolchains and anyone could compile their programs thee |
| # 19:43:32 | y_morin | sfan5: been there, done that. ;-) |
| # 19:44:15 | sfan5 | s/thee/There |
| # 19:45:21 | y_morin | sfan5: that's the kind of setup we use at work: all toolchains on a (farm of) machine(s), a common build system (home-brewed), and recipes (somewhere between OpenEmbedded and buildroot) |
| # 19:47:11 | sfan5 | :D |
| # 19:50:44 | sfan5 | crosstool-ng is awesome |
| # 19:53:07 | sfan5 | y_morin: do i need to rebuild the toolchain if i want to move anything to /opt/x-tools ? |
| # 19:53:47 | y_morin | sfan5: normally, no. The toolchain crosstool-NG builds are relocatable, which means you can move them wherever you want on your machine. |
| # 19:53:53 | sfan5 | ok |
| # 19:54:17 | y_morin | sfan5: of course, you need to move the complete toolchain (not just the bin directory, or the sysroot, or whateevr). |
| # 19:54:38 | sfan5 | yeah, i know |
| # 19:54:43 | sfan5 | that makes sense |
| # 19:55:10 | y_morin | sfan5: not for everybody (yes, I've had the issue raised once...) |
| # 19:55:12 | y_morin | ;-) |
| # 19:55:21 | y_morin | or :-/ |
| # 19:55:35 | y_morin | or o_O |
| # 20:06:55 | sfan5 | it works :) |
| # 20:08:06 | y_morin | sfan5: Nice to hear! :-) |
| # 20:10:01 | sfan5 | if i ever need to make and use another toolchain i can use /opt/x-tools |
| # 20:13:42 | sfan5 | y_morin: why is obj-c marked experimental in the menu? building gcc with obj-c support worked fine |
| # 20:14:26 | y_morin | sfan5: I do not do ObjC, so I can tell if it works, hence the EXPERIMENTAL. Nobody before you confirmed it working (or not) so it stayed marked experimental. |
| # 20:14:39 | y_morin | I can't tell , of course... |
| # 20:16:39 | y_morin | sfan5: it you can confirm it works for you, then send a patch to the mailing list that removes the experimental status. ;-) |
| # 20:28:07 | sfan5 | i'l maybe do that |
| # 20:28:22 | sfan5 | i'll test hello world and some small programs first |
| # 20:29:12 | sfan5 | is now known as: sfan5|OFF |
| # 20:57:07 | y_morin | quits : Quit: Nighty Night! |
| # 21:44:53 | codyps | quits : Ping timeout: 255 seconds |
| # 21:57:19 | codyps | joins #crosstool-ng |