Re: building x86_64 using lsflivecd-86_64
--- On Tue, 11/17/09, Bruce Dubbs bruce.du...@gmail.com wrote: Sorry for the late reply, I thought I would get individual messages back to my inbox. Now I know they come back bundled up in Digests (can I change this in any way?) It shouldn't be that way. You are not signed up in digest mode. If you are using google groups, you may want to check your settings there. Thanks, Bruce. I do not use any google groups. But I do use Yahoo! groups. Nevertheless, I do not see any related settings there. It's interesting, that this message of yours I got back directly in my mailbox, but others that I just received in the lfs-support Digest, Vol 1849, Issue 1 , namely the one sent by Mike McCarty mike.mcca...@sbcglobal.net, I did not... Thanks for that, Mike. Those are very good lines of documentation, and I'd like to suggest to the (C)LSF community to find a section for such description in the book(s) as well. Also, my requests to clfs-support get banned, and subjected to the moderator's approval on grounds of suspicious header. Any ideas how I could avoid this? I did try to comply with the posting rules/requirements, but I must be missing something... All the best, Tibor -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: building x86_64 using lsflivecd-86_64
Thank you Bruce, Aleksandar. Sorry for the late reply, I thought I would get individual messages back to my inbox. Now I know they come back bundled up in Digests (can I change this in any way?) 1) For now, I am booting off the x86_64 lsflivecd, and I am following the CLFS way to build a 64-bit multilib system, although pure 64 would suffice, and somehow I find it unnatural that one would need to cross-compile, while building for the host, on the host itself. It just doesn't feel right. Or am I completelly wrong? Bruce wrote: Yes, you are wrong. The reason for the cross compile is to completely isolate the current host from the new system. OK, but is that not what we do in the LFS 6.4 or 6.5 as well? I am not trying to argue, just to better understand. In both LFS and CLFS we build such that we gradually detach ourselves completly from the host, right? Then what does the 64 bit compilation have to do with the detachment process once the target and the host acrhitectures are the same? Aleksandar's reply kind of underlines this: This depends on the target capabilities. I have successfully built and am running/depending on a pure 64-bit system, and in my experience, for a pure 64-bit, no cross-compilers are necessary (apart from the first, which catapults your userland kernel from x86 to x86_64). Put this way, it makes sense to me. What I would like to obtain is a 64 bit machine that has 32 bit libraries as well, so that I do not limit the system to 64 bit applications. 64 bits I need for those of my own. And, for this purpose, what Aleksandar wrote, that is, However, for a multilib, a 32-bit compiler is a requirement (which should be logical - you want to be able to build x86 binaries, right?). Thus - CLFS.. seems logical to me. While on this note, I do ot quite understand why one would not re-compile GRUB as well: Aleksandar wrote: Woops! I forgot to mention I don't build GRUB anymore, those binaries (the GRUB in MBR, /boot/stage1 and /boot/stage2) are leftovers from my last x86. 3) The lsflivecd (x86_64) site mentions an unofficial version of the, I suppose, 64-bit version book, ... Use the -dev book for a pure-64 system. Thank you, Bruce, I'll look at it. Thank you All, again, Tibor-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
building x86_64 using lsflivecd-86_64
Hello All, I the the 6.4 book thourgh, and it worked out very nicely. Now I need a 64 bit version. I am aware that the support for 64 bit systems is only about to come in a future release of LFS, but I would like to give it a shot somehow, since that is what I need. In order to do this, one needs a 64-bit compiler and kernel, which the x86_64 lsflivecd has, at least in my understanding. Having said that, I would like to ask a few questions: 1) For now, I am booting off the x86_64 lsflivecd, and I am following the CLFS way to build a 64-bit multilib system, although pure 64 would suffice, and somehow I find it unnatural that one would need to cross-compile, while building for the host, on the host itself. It just doesn't feel right. Or am I completelly wrong? 2) While on the x86_64 lsflivecd platform, by following the LSF 6.5 instructions one should, more or less, be able to build a 64 bit system. A few parameters would need to be modified only, right? For example, having --target=x86_64-unknown-linux-gnu among the compilation parameters, should on its own invoke 64-bit output generation. A few settings could also be borrowed from the CLFS book, in order to get 64-bit generation enabled, right? By the way, would that not be the default gcc setting on a 64-bit platform? I mean, automatically? 3) The lsflivecd (x86_64) site mentions an unofficial version of the, I suppose, 64-bit version book, that I hope would contain some pointers for me to start with, but neither could I find it in the mounted CD iso image nor on the webpages. Is such thing really available? A pointer to any version or draft would be highly appreciated. Thank you All in advance, Tibor-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
