- I'm not looking for fewer unusual problems, I want to learn how this works 
and figure out what's going on so I can solve these problems on my own. 

- I'm not using bleeding edge version of everything, I've gone through the 
trouble to check out the appropriate branches in all repositories and if that’s 
not enough, I've reset to specific commit hashes just to be sure. 

- I insist on adjusting my versions according to this: 
http://www.linuxfromscratch.org/lfs/view/development/ if someone else can get 
that to work then I should be able to as well.

- you guys don’t post section 4.4 and 5.2 here ? 
http://www.linuxfromscratch.org/lfs/view/development/

- I'm sorry but the only reason I top-posted was to add additional information 
that I thought would be helpful in getting information as to what is going on 
with my toolchain. I also use a thread view email client.





-----Original Message-----
From: lfs-support-boun...@linuxfromscratch.org 
[mailto:lfs-support-boun...@linuxfromscratch.org] On Behalf Of Ken Moffat
Sent: Wednesday, November 14, 2012 11:22 AM
To: LFS Support List
Subject: Re: [lfs-support] still doesnt work right (after binutils pass 2)

On Wed, Nov 14, 2012 at 10:38:45AM -0800, Paige Thompson wrote:
> dev@dev-VirtualBox /mnt/erraticOS/tools/bin $ strace ./as
> 
> execve("./as", ["./as"], [/* 28 vars */]) = 0
> 
> brk(0)                                  = 0x1432000
> 
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
> 0) =
> 0x7f59289d4000
> 
> access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or
> directory)
> 
[...]
> 
> open("/tools/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
> 
> read(3,
> "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\300\27\2\0\0\0\0\0"...
> , 832) = 832
> 
> fstat(3, {st_mode=S_IFREG|0755, st_size=9593885, ...}) = 0
> 
> mmap(NULL, 3824768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 
> 0) =
> 0x7f592840f000
> 
> mprotect(0x7f59285ab000, 2097152, PROT_NONE) = 0
> 
> mmap(0x7f59287ab000, 24576, PROT_READ|PROT_WRITE, 
> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x19c000) = 0x7f59287ab000
> 
> mmap(0x7f59287b1000, 15488, PROT_READ|PROT_WRITE, 
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f59287b1000
> 
> close(3)                                = 0
> 
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
> 0) =
> 0x7f59289d3000
> 
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
> 0) =
> 0x7f59289d2000
> 
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
> 0) =
> 0x7f59289d1000
> 
> arch_prctl(ARCH_SET_FS, 0x7f59289d2700) = 0
> 
> mprotect(0x7f59287ab000, 16384, PROT_READ) = 0
> 
> mprotect(0x7f59289d5000, 4096, PROT_READ) = 0
> 
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> 
> +++ killed by SIGSEGV +++
> 
> Segmentation fault
> 
> dev@dev-VirtualBox /mnt/erraticOS/tools/bin $
> 
 Possibly, you need to do something specific to build in VirtualBox.
Not something I've ever used, and a quick google didn't highlight anything 
obvious.
>  
> dev@dev-VirtualBox /mnt/erraticOS/tools/bin $ ldd as
> 
>         linux-vdso.so.1 =>  (0x00007fffb63ff000)
> 
>         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 
> (0x00007f3d79c06000)
> 
>         /tools/lib64/ld-linux-x86-64.so.2 => 
> /lib64/ld-linux-x86-64.so.2
> (0x00007f3d79fd9000)
> 
 Umm, /tools/lib64/ld-linux-x86-64.so.2 links to the host's version in /lib64.  
That won't work when you enter chroot.

> cant compile gcc because of it
> 
> x86_64-linux-gnu-gcc (GCC) 4.7.2 20120614 (prerelease)
> 
 LFS-7.2 is on gcc-4.7.1.  I suggest that you use the latest release of the LFS 
book until you can successfully build it.  You seem to have a lot of knowledge 
of some things, but you don't seem to understand *how* we build LFS.  I'm sure 
that will come, if you stick with it.

> Using built-in specs.
> 
> COLLECT_GCC=/mnt/erraticOS/tools/bin/x86_64-linux-gnu-gcc
> 
 Does a /mnt/lfs directory (or symlink, I suppose) exist ?  Mounting the build 
system at /mnt/lfs should NOT be regarded as optional - from time to time 
references to /mnt/lfs may be hardcoded in patches or in seds.

> 
> configure:4087: /mnt/erraticOS/tools/bin/x86_64-linux-gnu-gcc    conftest.c
> >&5
> x86_64-linux-gnu-gcc: internal compiler error: Segmentation fault 
> (program
> as)
> Please submit a full bug report,

 I have to recommend that you start again, but following the book (preferably 
the 7.2 release, for your first attempt.)  And for preference make 
/mnt/erraticOS a symlink to /mnt/lfs - you will get fewer unusual problems by 
doing that.  I'm sure it is possible to use the bleeding edge versions of 
everything (modulo occasional new difficulties, and things which get reverted 
before a package is released), but it needs a lot more effort.

 Also, (re)read the Host System Requirements in the preface (ALL of them need 
to pass), section 4.4 Setting Up the Environment, and the Toolchain Technical 
Notes in section 5.2

 Lastly, please don't add unnecessary blank lines when pasting (or strip them 
if you are posting a long part of a log from a windows machine), and don't top 
post.  Thanks, and good luck.

ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to