Error compiling Linux-3.14.21 kernel for CLFS Version GIT-20150207-x86_64-Multilib

Xenanthropy · 03-30-2015, 01:43 PM

had time to compile one more time, i'll need to link x86_64-unknown-linux-gnu-objcopy as well. I can do that myself though, I should be good now unless there's another problem besides missing symlinks.

veerain · 03-30-2015, 01:55 PM

I found out the issue. What I did opted was 'to boot'. So I had '/cross-tools/bin' in the PATH first. So no need for these symlinks.

And you are using 'to chroot' option which doesn't builds a kernel assuming the system kernel would boot properly. In your case it won't probably. So it's better to isolate as much and use build tools from cross-gcc and cross-binutils.

Sorry I did CLFS a year or so ago. So I was not well versed. So much trouble.

veerain · 03-30-2015, 01:56 PM

And it's wrong to use gcc and binutils toolchain from /tools. They are to be used only after booting with the new kernel.

veerain · 03-30-2015, 02:19 PM

And you should build the kernel without chrooting. So that /cross-tools/bin is still first in PATH.

Xenanthropy · 03-30-2015, 06:56 PM

Ok, thanks for the help. I'll try making it outside of the chroot. This is a pain, but then again, it'd be a pain as well to only have a 64bit system that couldn't do 32bit stuff, since a lot of new gaming stuff is designed for standard "32bit ubuntu" etc. Would building a 64bit only system be that much of a pain or are 32bit programs on 64bit only not a problem? I think it'd only be a problem if I don't have access to the source code, like say for instance, steam, I think they only ship binaries. And also, if I were to start over, do you recommend the boot method over chroot method? I only did the chroot method so I could have the book on my second monitor, but I could always do boot. I just wouldn't be able to copy-paste so it'd just take longer. But hey, whatever works.

Edit: Yep, kernel compiling fine outside of the chroot.

Edit2: Well, it did give me a bit of an error (warnings I assume, since it says warning) close to the beginning:

Code:

In file included from scripts/sortextable.c:190:0:
scripts/sortextable.c: In function 'main':
scripts/sortextable.h:176:3: warning: 'relocs_size' may be used uninitialized in this function [-Wmaybe-uninitialized]
   memset(relocs, 0, relocs_size);
   ^
scripts/sortextable.h:106:6: note: 'relocs_size' was declared here
  int relocs_size;
      ^
In file included from scripts/sortextable.c:188:0:
scripts/sortextable.h:176:3: warning: 'relocs_size' may be used uninitialized in this function [-Wmaybe-uninitialized]
   memset(relocs, 0, relocs_size);
   ^
scripts/sortextable.h:106:6: note: 'relocs_size' was declared here
  int relocs_size;
      ^

But other than that, it compiled fine and finished. I'm gonna try installing and see what happens.
Also, I found out why gnutls wasn't working properly. I had built nettle from the lfs page, so when I installed it, it automatically did it as 64bit. But GnuTLS was expecting 32bit since I was on the lfs page, so it wasn't searching inside lib64. I went to the cblfs page, and it has nettle and gnutls, and both pages have the instructions for compiling for both 32bit and 64 bit. Silly me.

veerain · 03-31-2015, 12:26 AM

Quote:

-Wmaybe-uninitialized

These error messages are benign.

Xenanthropy · 03-31-2015, 01:19 AM

Ok, good. Honestly I might just start over with a fully 64-bit system, i've run into quite a bit of problems with installing various programs (openssl/gnutls, wget, pam-library, curl, nettle, to name a few) I'm just assuming i've messed something up somewhere that I didn't catch, and it's just messed my whole build up. Besides, i'm sure the fully 64bit system would be faster to make anyway.

sr_ls_boy · 04-12-2015, 10:03 PM

Are you still having trouble with the have() command not being found in bash?

Xenanthropy · 04-13-2015, 01:49 AM

Oh I haven't tried compiling LFS since I gave up on that instance that I was compiling. I think I probably fixed the problem, i'm not really sure though, I just decided it'd be easier to just compile a 64-bit only system, since apparently you can still build and compile 32-bit programs. Which makes me confused as to why you'd need multilib. I have no clue, unless i'm misinterpreting something.