# Format for this file: # Epoch Channel Nickname Action Message # # All separated with a single space, empty values are replaced with a dash '-' # except messages which are kept empty. # Lines starting with '#' are comments; comments are not allowed except as the only content of the line # 1330388667 - y_morin quit Quit: Night! 1330395642 #crosstool-ng nandub join 1330404562 - nandub quit Quit: Leaving. 1330404576 #crosstool-ng nandub join 1330405277 - nandub quit Quit: Leaving. 1330407601 #crosstool-ng alan_o_ join 1330407906 - alan_o_ quit Quit: Leaving 1330418835 #crosstool-ng daggs123 join 1330418994 #crosstool-ng daggs123 say hello all, is there a solution for the termcap issue when compiling crosstool gdb using ct-ng? 1330421670 #crosstool-ng smartin join 1330428870 - sh4rm4 quit Remote host closed the connection 1330429120 #crosstool-ng sh4rm4 join 1330442609 - mnt_real quit *.net *.split 1330442609 - hank quit *.net *.split 1330442609 - ccole quit *.net *.split 1330442615 #crosstool-ng ccole join 1330442622 #crosstool-ng hank join 1330442640 #crosstool-ng mnt_real join 1330442826 - smartin quit Ping timeout: 245 seconds 1330450841 #crosstool-ng y_morin join 1330453784 - y_morin quit Read error: Operation timed out 1330453809 #crosstool-ng y_morin join 1330454820 - imMute quit Ping timeout: 265 seconds 1330455380 #crosstool-ng imMute join 1330455381 - imMute quit Changing host 1330455381 #crosstool-ng imMute join 1330456222 - y_morin nick y_morin|away 1330456228 - y_morin|away nick y_morin 1330457631 - y_morin nick y_morin|away 1330460150 - sh4rm4 quit Remote host closed the connection 1330460374 #crosstool-ng sh4rm4 join 1330463858 - arekinath quit *.net *.split 1330463858 - ChanServ quit *.net *.split 1330463858 - sh4rm4 quit *.net *.split 1330463858 - jledet quit *.net *.split 1330463858 - CcSsNET quit *.net *.split 1330463905 #crosstool-ng sh4rm4 join 1330463905 #crosstool-ng CcSsNET join 1330463905 #crosstool-ng arekinath join 1330463905 #crosstool-ng jledet join 1330463905 #crosstool-ng ChanServ join 1330464993 #crosstool-ng sh4rm4 say y_morin|away, if you create a sysrooted toolchain, do you usually compile the binutils before or after gcc ? 1330465510 - y_morin|away nick y_morin 1330465563 #crosstool-ng y_morin say sh4rm4: before, sysrooted or not. gcc needs the binutils (as and ld, at least) 1330465734 #crosstool-ng sh4rm4 say i was getting away with building it later in the past 1330465751 #crosstool-ng sh4rm4 say i disabled the build of target libraries and bootstrap 1330465781 #crosstool-ng sh4rm4 say so it was never trying to execute xgcc which depends on a sysrooted ld 1330465814 #crosstool-ng sh4rm4 say the addition of C++ support changed that... 1330469906 - ccole quit Quit: leaving 1330469981 #crosstool-ng sh4rm4 say y_morin, how do you tell the configure script of gcc to use the LD from the binutils you built ? 1330470024 #crosstool-ng y_morin say sh4rm4: set PATH to include it. 1330470068 #crosstool-ng sh4rm4 say hmm but then it will use that everytime 1330470088 #crosstool-ng sh4rm4 say which obviously only works in combination with a sysrooted gcc 1330470115 #crosstool-ng sh4rm4 say it should only use it to build target libraries 1330470119 #crosstool-ng y_morin say sh4rm4: that's LD_FOR_TARGET, sorry. 1330470133 #crosstool-ng y_morin say sh4rm4: forget all I said, I missed a sentence... 1330470140 #crosstool-ng y_morin say sh4rm4: here I do it again: 1330470171 #crosstool-ng y_morin say sh4rm4: either the binutils you just built are in the path, and gcc will use them (remember they are prefixed with the tuple!) 1330470203 #crosstool-ng y_morin say path-> $PATH 1330470235 #crosstool-ng y_morin say sh4rm4: or you can force it on the command line: ./configure LD_FOR_TARGET=blablab/tuple-ld 1330470237 #crosstool-ng sh4rm4 say hmm the toolchain is not prefixed 1330470246 #crosstool-ng y_morin say sh4rm4: why not ? 1330470255 #crosstool-ng sh4rm4 say no idea 1330470266 #crosstool-ng sh4rm4 say i just used with-sysroot and build-sysroot 1330470275 #crosstool-ng sh4rm4 say but no other cross compiler options 1330470287 #crosstool-ng sh4rm4 say i just want the toolchain to be usable standalone 1330470293 #crosstool-ng y_morin say sh4rm4: I'm lost, here... How did you configure binutils ? 1330470327 #crosstool-ng sh4rm4 say CC="$CC -static -L$R/lib -I$R/include" ./configure \ 1330470328 #crosstool-ng sh4rm4 say --prefix=/ --disable-nls --disable-shared \ 1330470328 #crosstool-ng sh4rm4 say --with-build-sysroot=$R --with-sysroot=$TC_PATH 1330470349 #crosstool-ng y_morin say sh4rm4: and what is $CC ? 1330470362 #crosstool-ng sh4rm4 say the static gcc3 in /bin/gcc 1330470410 #crosstool-ng y_morin say sh4rm4: and what is that gcc ? Did you configure it yourself ? 1330470438 #crosstool-ng Tick_ join 1330470483 #crosstool-ng sh4rm4 say yeah its a pretty standard gcc 3.4.6 1330470499 #crosstool-ng y_morin say sh4rm4: what are you trying to do? 1330470545 #crosstool-ng sh4rm4 say i'm creating a toolchain that is in /opt/toolchain and can be placed anywhere 1330470564 #crosstool-ng Tick_ say 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 1330470571 #crosstool-ng y_morin say sh4rm4: and what arch are you targetting. 1330470582 #crosstool-ng sh4rm4 say amd64 on amd64 1330470588 #crosstool-ng sh4rm4 say so no cross compiling going on 1330470590 #crosstool-ng y_morin say Tick_: hey! ;-) 1330470616 #crosstool-ng Tick_ say Quick question for you. I undestand that crosstool-ng doesn't support multilib. My question might sound very stupid. But here is my situation. 1330470632 #crosstool-ng y_morin say Tick_: there *is* multilib support now! :-) 1330470645 #crosstool-ng y_morin say Tick_: granted, it's still experimental... 1330470697 #crosstool-ng Tick_ say 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? 1330470700 #crosstool-ng y_morin say sh4rm4: sorry, I don't understand. Do you want to target the running machine? Or another x86_64 machine? 1330470735 #crosstool-ng y_morin say Tick_: for grub, the easy way is to get a separate, 32-bit toolchain. 1330470776 #crosstool-ng sh4rm4 say i target the running system 1330470783 #crosstool-ng Tick_ say 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. 1330470787 #crosstool-ng y_morin say Tick_: I was not able to build a multilib i386/x86_64 toolchain so far. 1330470792 #crosstool-ng sh4rm4 say but i want the tc to be usable on other hosts as well 1330470818 #crosstool-ng sh4rm4 say i.e. build a native i386 tc on a i386 host and then use it to compile i386 stuff on an amd64 sys 1330470846 #crosstool-ng sh4rm4 say haha it seems LD_FOR_TARGET did the job 1330470864 #crosstool-ng Tick_ say 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? 1330470879 #crosstool-ng y_morin say sh4rm4: OK, this *is* cross-compilation. You have to set --build=XXX --host=XXX --target=XXX 1330470899 #crosstool-ng y_morin say Tick_: yes, it will work, but what's the point, then? 1330470909 #crosstool-ng sh4rm4 say y_morin, no, it actually works fine without that 1330470923 #crosstool-ng y_morin say Tick_: you could build everything 64-bit, save for grub which you build 32-bit. 1330470924 #crosstool-ng sh4rm4 say even moreso, the build fails when is use host and target 1330470943 #crosstool-ng Tick_ say 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. 1330470973 #crosstool-ng y_morin say Tick_: Just consider grub to be special case. Build it with another toolchain. 1330470998 #crosstool-ng y_morin say kos_tom: around? What was the resolution for grub on x86_64 ? 1330471077 #crosstool-ng Tick_ say Yann. There are dependencies. The GRUB relies on ncurses. Do I need to build it with 32-bit toolchain as well? 1330471118 #crosstool-ng Tick_ say Then there are apps depending on ncurses.... 1330471213 #crosstool-ng y_morin say 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. 1330471250 #crosstool-ng Tick_ say What? Oh my.... Well... is it possible that I have a single build system which will build all of them in one make call? 1330471268 #crosstool-ng Tick_ say At least that's what I have right now for the 32-bit. One make call and it builds the whole system. 1330471368 #crosstool-ng y_morin say Tick_: I do not know your current build-system, so I can't say. 1330471388 #crosstool-ng Tick_ say That was the main reason that leads me to ask the question about multilib. 1330471393 #crosstool-ng y_morin say Tick_: you could view grub as a completely separate "project". 1330471430 #crosstool-ng y_morin say Tick_: even if the toolchain is multilib, you will need to build ncurses twice, first for 32-bit, then for 64-bit. 1330471452 #crosstool-ng Tick_ say 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? 1330471551 #crosstool-ng y_morin say Tick_: I don't think so. Why is ncurses required for grub? For the bootloader itself, or for the userland utilities? 1330471561 #crosstool-ng Tick_ say So how do I distinguish them? lib/ lib64/? Sorry for my stupid question again.... 1330471579 #crosstool-ng y_morin say Tick_: No question is stupid. Answers may be stupid, though! :-) 1330471594 #crosstool-ng Tick_ say There are multiple userland apps depend on ncurses. 1330471625 #crosstool-ng Tick_ say The current build script setup the dependency on ncurses for the grub. I don't know the reason. 1330471641 #crosstool-ng Tick_ say :-) 1330471643 #crosstool-ng y_morin say Tick_: OK, so the bootloader itself (that goes on the MBR!) does not depend on ncurses. So you should probably get away with: 1330471670 #crosstool-ng y_morin say - build a singl;e 64-bit ncurses 1330471677 #crosstool-ng y_morin say - build userland utilities in 64-bit against that ncurses 1330471687 #crosstool-ng Tick_ say Ok. I will remove the dependency and build it again. But you mean I have to have a totally separate build for the GRUB. 1330471699 #crosstool-ng y_morin say and in a separate step, build the bootloader itself 1330471734 #crosstool-ng Tick_ say Understood. Let me try it and I think there is a high possibility I will come back here :-) 1330471742 #crosstool-ng y_morin say 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. 1330471771 #crosstool-ng Tick_ say I don't get it. Isn't grub the bootloader? 1330471778 #crosstool-ng y_morin say Tick_: you should probably also inquire to the grub people about the procedure to build for x86_64. Maybe they get some hints?... 1330471795 #crosstool-ng y_morin say Tick_: grub is the package. It builds many things: 1330471806 #crosstool-ng y_morin say - the bootloader itself, that the BIOS loads 1330471817 #crosstool-ng y_morin say - userland utilities to setup grub 1330471844 #crosstool-ng Tick_ say I googled and googled... They all focus on grub2 now... the legacy grub is not 64-bit friendly.. (No 64-bit support anyway) 1330471861 #crosstool-ng y_morin say Tick_: then switch... 1330471885 #crosstool-ng y_morin say OK, it's late here, got to go to bed... 1330471889 - y_morin quit Quit: Night! 1330471894 #crosstool-ng Tick_ say Thanks. 1330471897 #crosstool-ng Tick_ say Ah.... 1330471900 #crosstool-ng Tick_ say :-)