| # 00:24:27 | y_morin | quits : Quit: Night! |
| # 02:20:42 | nandub | joins #crosstool-ng |
| # 04:49:22 | nandub | quits : Quit: Leaving. |
| # 04:49:36 | nandub | joins #crosstool-ng |
| # 05:01:17 | nandub | quits : Quit: Leaving. |
| # 05:40:01 | alan_o_ | joins #crosstool-ng |
| # 05:45:06 | alan_o_ | quits : Quit: Leaving |
| # 08:47:15 | daggs123 | joins #crosstool-ng |
| # 08:49:54 | daggs123 | hello all, is there a solution for the termcap issue when compiling crosstool gdb using ct-ng? |
| # 09:34:30 | smartin | joins #crosstool-ng |
| # 11:34:30 | sh4rm4 | quits : Remote host closed the connection |
| # 11:38:40 | sh4rm4 | joins #crosstool-ng |
| # 15:23:29 | mnt_real | quits : *.net *.split |
| # 15:23:29 | hank | quits : *.net *.split |
| # 15:23:29 | ccole | quits : *.net *.split |
| # 15:23:35 | ccole | joins #crosstool-ng |
| # 15:23:42 | hank | joins #crosstool-ng |
| # 15:24:00 | mnt_real | joins #crosstool-ng |
| # 15:27:06 | smartin | quits : Ping timeout: 245 seconds |
| # 17:40:41 | y_morin | joins #crosstool-ng |
| # 18:29:44 | y_morin | quits : Read error: Operation timed out |
| # 18:30:09 | y_morin | joins #crosstool-ng |
| # 18:47:00 | imMute | quits : Ping timeout: 265 seconds |
| # 18:56:20 | imMute | joins #crosstool-ng |
| # 18:56:21 | imMute | quits : Changing host |
| # 18:56:21 | imMute | joins #crosstool-ng |
| # 19:10:22 | y_morin | is now known as: y_morin|away |
| # 19:10:28 | y_morin|away | is now known as: y_morin |
| # 19:33:51 | y_morin | is now known as: y_morin|away |
| # 20:15:50 | sh4rm4 | quits : Remote host closed the connection |
| # 20:19:34 | sh4rm4 | joins #crosstool-ng |
| # 21:17:38 | arekinath | quits : *.net *.split |
| # 21:17:38 | ChanServ | quits : *.net *.split |
| # 21:17:38 | sh4rm4 | quits : *.net *.split |
| # 21:17:38 | jledet | quits : *.net *.split |
| # 21:17:38 | CcSsNET | quits : *.net *.split |
| # 21:18:25 | sh4rm4 | joins #crosstool-ng |
| # 21:18:25 | CcSsNET | joins #crosstool-ng |
| # 21:18:25 | arekinath | joins #crosstool-ng |
| # 21:18:25 | jledet | joins #crosstool-ng |
| # 21:18:25 | ChanServ | joins #crosstool-ng |
| # 21:36:33 | sh4rm4 | y_morin|away, if you create a sysrooted toolchain, do you usually compile the binutils before or after gcc ? |
| # 21:45:10 | y_morin|away | is now known as: y_morin |
| # 21:46:03 | y_morin | sh4rm4: before, sysrooted or not. gcc needs the binutils (as and ld, at least) |
| # 21:48:54 | sh4rm4 | i was getting away with building it later in the past |
| # 21:49:11 | sh4rm4 | i disabled the build of target libraries and bootstrap |
| # 21:49:41 | sh4rm4 | so it was never trying to execute xgcc which depends on a sysrooted ld |
| # 21:50:14 | sh4rm4 | the addition of C++ support changed that... |
| # 22:58:26 | ccole | quits : Quit: leaving |
| # 22:59:41 | sh4rm4 | y_morin, how do you tell the configure script of gcc to use the LD from the binutils you built ? |
| # 23:00:24 | y_morin | sh4rm4: set PATH to include it. |
| # 23:01:08 | sh4rm4 | hmm but then it will use that everytime |
| # 23:01:28 | sh4rm4 | which obviously only works in combination with a sysrooted gcc |
| # 23:01:55 | sh4rm4 | it should only use it to build target libraries |
| # 23:01:59 | y_morin | sh4rm4: that's LD_FOR_TARGET, sorry. |
| # 23:02:13 | y_morin | sh4rm4: forget all I said, I missed a sentence... |
| # 23:02:20 | y_morin | sh4rm4: here I do it again: |
| # 23:02:51 | y_morin | sh4rm4: either the binutils you just built are in the path, and gcc will use them (remember they are prefixed with the tuple!) |
| # 23:03:23 | y_morin | path-> $PATH |
| # 23:03:55 | y_morin | sh4rm4: or you can force it on the command line: ./configure LD_FOR_TARGET=blablab/tuple-ld |
| # 23:03:57 | sh4rm4 | hmm the toolchain is not prefixed |
| # 23:04:06 | y_morin | sh4rm4: why not ? |
| # 23:04:15 | sh4rm4 | no idea |
| # 23:04:26 | sh4rm4 | i just used with-sysroot and build-sysroot |
| # 23:04:35 | sh4rm4 | but no other cross compiler options |
| # 23:04:47 | sh4rm4 | i just want the toolchain to be usable standalone |
| # 23:04:53 | y_morin | sh4rm4: I'm lost, here... How did you configure binutils ? |
| # 23:05:27 | sh4rm4 | CC="$CC -static -L$R/lib -I$R/include" ./configure \ |
| # 23:05:28 | sh4rm4 | --prefix=/ --disable-nls --disable-shared \ |
| # 23:05:28 | sh4rm4 | --with-build-sysroot=$R --with-sysroot=$TC_PATH |
| # 23:05:49 | y_morin | sh4rm4: and what is $CC ? |
| # 23:06:02 | sh4rm4 | the static gcc3 in /bin/gcc |
| # 23:06:50 | y_morin | sh4rm4: and what is that gcc ? Did you configure it yourself ? |
| # 23:07:18 | Tick_ | joins #crosstool-ng |
| # 23:08:03 | sh4rm4 | yeah its a pretty standard gcc 3.4.6 |
| # 23:08:19 | y_morin | sh4rm4: what are you trying to do? |
| # 23:09:05 | sh4rm4 | i'm creating a toolchain that is in /opt/toolchain and can be placed anywhere |
| # 23:09:24 | Tick_ | Hi, Yann. Nice to see you again. I was the guy who had the trouble to create 64-bit toolchain because I was using Make 3.82 |
| # 23:09:31 | y_morin | sh4rm4: and what arch are you targetting. |
| # 23:09:42 | sh4rm4 | amd64 on amd64 |
| # 23:09:48 | sh4rm4 | so no cross compiling going on |
| # 23:09:50 | y_morin | Tick_: hey! ;-) |
| # 23:10:16 | Tick_ | Quick question for you. I undestand that crosstool-ng doesn't support multilib. My question might sound very stupid. But here is my situation. |
| # 23:10:32 | y_morin | Tick_: there *is* multilib support now! :-) |
| # 23:10:45 | y_morin | Tick_: granted, it's still experimental... |
| # 23:11:37 | Tick_ | I used the 64-bit toolchain to successfully compile most of the 3rdparty apps. However, GRUB 0.97 has to be a 32-bit app. What are the options I have? It's supporting multilib now? |
| # 23:11:40 | y_morin | sh4rm4: sorry, I don't understand. Do you want to target the running machine? Or another x86_64 machine? |
| # 23:12:15 | y_morin | Tick_: for grub, the easy way is to get a separate, 32-bit toolchain. |
| # 23:12:56 | sh4rm4 | i target the running system |
| # 23:13:03 | Tick_ | I do have the 32-bit toolchain as well. And I tried to compile it with the 32-bit one. However, it's still failed. |
| # 23:13:07 | y_morin | Tick_: I was not able to build a multilib i386/x86_64 toolchain so far. |
| # 23:13:12 | sh4rm4 | but i want the tc to be usable on other hosts as well |
| # 23:13:38 | sh4rm4 | i.e. build a native i386 tc on a i386 host and then use it to compile i386 stuff on an amd64 sys |
| # 23:14:06 | sh4rm4 | haha it seems LD_FOR_TARGET did the job |
| # 23:14:24 | Tick_ | My stupid question is this. Is it possible to compile all the apps in 32-bit but only compile a 64-bit kernel with IA32_EMULATION enabled. Will that work? |
| # 23:14:39 | y_morin | sh4rm4: OK, this *is* cross-compilation. You have to set --build=XXX --host=XXX --target=XXX |
| # 23:14:59 | y_morin | Tick_: yes, it will work, but what's the point, then? |
| # 23:15:09 | sh4rm4 | y_morin, no, it actually works fine without that |
| # 23:15:23 | y_morin | Tick_: you could build everything 64-bit, save for grub which you build 32-bit. |
| # 23:15:24 | sh4rm4 | even moreso, the build fails when is use host and target |
| # 23:15:43 | Tick_ | yeah... what's the point. My problem is that after I compiled almost 80% apps/libs... I am stuck at the the build for grub. It just failed on me. |
| # 23:16:13 | y_morin | Tick_: Just consider grub to be special case. Build it with another toolchain. |
| # 23:16:38 | y_morin | kos_tom: around? What was the resolution for grub on x86_64 ? |
| # 23:17:57 | Tick_ | Yann. There are dependencies. The GRUB relies on ncurses. Do I need to build it with 32-bit toolchain as well? |
| # 23:18:38 | Tick_ | Then there are apps depending on ncurses.... |
| # 23:20:13 | y_morin | Tick_: well, I believe so. You would need a 32-bit ncurses for grub, and a 64-bit ncurses for the rest of the system. |
| # 23:20:50 | Tick_ | What? Oh my.... Well... is it possible that I have a single build system which will build all of them in one make call? |
| # 23:21:08 | Tick_ | At least that's what I have right now for the 32-bit. One make call and it builds the whole system. |
| # 23:22:48 | y_morin | Tick_: I do not know your current build-system, so I can't say. |
| # 23:23:08 | Tick_ | That was the main reason that leads me to ask the question about multilib. |
| # 23:23:13 | y_morin | Tick_: you could view grub as a completely separate "project". |
| # 23:23:50 | y_morin | Tick_: even if the toolchain is multilib, you will need to build ncurses twice, first for 32-bit, then for 64-bit. |
| # 23:24:12 | Tick_ | Ok. In that case, both 32-bit and 64-bit ncurses have to be co-exist on the same runtime system with the required 32-bit/64-bit libraries in place as well, right? |
| # 23:25:51 | y_morin | Tick_: I don't think so. Why is ncurses required for grub? For the bootloader itself, or for the userland utilities? |
| # 23:26:01 | Tick_ | So how do I distinguish them? lib/ lib64/? Sorry for my stupid question again.... |
| # 23:26:19 | y_morin | Tick_: No question is stupid. Answers may be stupid, though! :-) |
| # 23:26:34 | Tick_ | There are multiple userland apps depend on ncurses. |
| # 23:27:05 | Tick_ | The current build script setup the dependency on ncurses for the grub. I don't know the reason. |
| # 23:27:21 | Tick_ | :-) |
| # 23:27:23 | y_morin | Tick_: OK, so the bootloader itself (that goes on the MBR!) does not depend on ncurses. So you should probably get away with: |
| # 23:27:50 | y_morin | - build a singl;e 64-bit ncurses |
| # 23:27:57 | y_morin | - build userland utilities in 64-bit against that ncurses |
| # 23:28:07 | Tick_ | Ok. I will remove the dependency and build it again. But you mean I have to have a totally separate build for the GRUB. |
| # 23:28:19 | y_morin | and in a separate step, build the bootloader itself |
| # 23:28:54 | Tick_ | Understood. Let me try it and I think there is a high possibility I will come back here :-) |
| # 23:29:02 | y_morin | Tick_: Not for grub, just for the bootloader , the parts that go to the MBR and in /boot/grub. The rest (userland utilities) can (probably) be 64-bit. |
| # 23:29:31 | Tick_ | I don't get it. Isn't grub the bootloader? |
| # 23:29:38 | y_morin | Tick_: you should probably also inquire to the grub people about the procedure to build for x86_64. Maybe they get some hints?... |
| # 23:29:55 | y_morin | Tick_: grub is the package. It builds many things: |
| # 23:30:06 | y_morin | - the bootloader itself, that the BIOS loads |
| # 23:30:17 | y_morin | - userland utilities to setup grub |
| # 23:30:44 | Tick_ | I googled and googled... They all focus on grub2 now... the legacy grub is not 64-bit friendly.. (No 64-bit support anyway) |
| # 23:31:01 | y_morin | Tick_: then switch... |
| # 23:31:25 | y_morin | OK, it's late here, got to go to bed... |
| # 23:31:29 | y_morin | quits : Quit: Night! |
| # 23:31:34 | Tick_ | Thanks. |
| # 23:31:37 | Tick_ | Ah.... |
| # 23:31:40 | Tick_ | :-) |