Jump to content
funtoo forums


  • Content count

  • Joined

  • Last visited

  • Days Won

  1. Cmake fails with "bus error"

    Turns out that the class ten SD cards were part of it as well, But a larger swap partition really made the difference and now I have cmake emerged.
  2. Cmake fails with "bus error"

    That is all that there is as far as build log (maddening how it just stops and leaves me in a dead zone of - WTF just happened? ) - the next thing I have noticed is I was not using a Class 10 SD card and on what I have been reading that is what is suggested for pi - Funny that I bought them at fry's electronics and even asked the guy working for a SD card for raspberry pi and he took me to the Pi section and handed me a card - turns out it was a class 4. when I asked this time for class 10 the guy looked at me like he was lost - anyway found class 10 SD and trying again.
  3. Cmake fails with "bus error"

    Ok, Turkey day break from Techie stuff is over, figured out how to find build log and use wgetpaste. Build log is at: https://paste.pound-python.org/show/K9q4NBqmUr0YwXCSNX1c/ Doesnt seem to show much but I wouldnt know. The last line is where I get bus error, I thought it might be a power issue since I am Chroot into funtoo install on Raspberry Pi and my funtoo is in usb sd card reader. Found 2.5 amp PSU still get Bus error.
  4. Cmake fails with "bus error"

    I knew bus error would suggest hardware problems, which is why I tried with identical new hardware. I will read up on how to get build log and provide that. Thank you
  5. Cmake fails with "bus error"

    Hello all, dev-util/cmake-3.8.0::core-kit I was working on my Raspberry pi this weekend, (chroot from Rasberry linux) did ego sync, then emerge networkmanager. I had problems with use flags , did --autounmask-write and updated config file. everything goes along fine 51 packages installed. Then we get to cmake, everything seems to get started properly, applying patches etc until this one part shown below and I get "bus error" armv7a-hardfloat-linux-gnueabi-g++ -O2 -pipe -march=armv7-a -mfloat-abi=hard -I/var/tmp/portage/dev-util/cmake-3.8.0/work/cmake-3.8.0/Bootstrap.cmk -I/var/tmp/portage/dev-util/cmake-3.8.0/work/cmake-3.8.0/Source -I/var/tmp/portage/dev-util/cmake-3.8.0/work/cmake-3.8.0/Utilities -c /var/tmp/portage/dev-util/cmake-3.8.0/work/cmake-3.8.0/Source/cmGlobalGenerator.cxx -o cmGlobalGenerator.o armv7a-hardfloat-linux-gnueabi-g++ -O2 -pipe -march=armv7-a -mfloat-abi=hard -I/var/tmp/portage/dev-util/cmake-3.8.0/work/cmake-3.8.0/Bootstrap.cmk -I/var/tmp/portage/dev-util/cmake-3.8.0/work/cmake-3.8.0/Source -I/var/tmp/portage/dev-util/cmake-3.8.0/work/cmake-3.8.0/Utilities -c /var/tmp/portage/dev-util/cmake-3.8.0/work/cmake-3.8.0/Source/cmGlobalUnixMakefileGenerator3.cxx -o cmGlobalUnixMakefileGenerator3.o Bus error Everything is locked up for awhile but comes back - except chroot - terminal window has all of the info in it still. I did as much as i know to do - tried again - redid ego sync - rebooted and chroot with different chroot instructions - Checked that I still had disk space - tried another Pi - I reflashed my raspberry pi to clean SD with pi Linux, reinstalled funtoo and paid particularly close attention when setting up env and portage config / environment variables. i did notice at the beginning of emerge it says *unable to find kernel sources at /usr/src/linux *Was unable to determine your kernel .config Not sure where to look or what to do. suggestions requested.
  6. Help a N00B with chroot

    A picture of the area I am using to work on Funtoo, and all of the instruction sets that are now suspect because of firefox reader view and stupid users. Someone say a prayer for the trees!
  7. Help a N00B with chroot

    Oleg forgive me it is not a fault with any instruction, I figured out this morning, it is the fact that I used reader view with firefox and printed from there and so it looked like the rc-update commands belonged in the /etc/conf.d/xdm config file. - I am learning by leaps and bounds ... Woohoo gonna get stuck in a corner again! Maybe not now, maybe not tomorrow, but I can feel it coming :) The instruction that i followed that lead me to put # in my /etc/conf.d/xdm file is: funtoo.org/package:Xfce4-meta (it was because I printed from firefox reader view) @tefreem34 Thank you for clearing that up for me, and thank you for the further instructions.
  8. Help a N00B with chroot

    Hello all, I am rusty enough with Unix/Linux to call myself a Newbie, I know enough to get myself in trouble. So I need to chroot into my funtoo installation so I can run: rc-update del xdm default However when looking at the commands for chroot on the install instructions and I try to run: mount /mnt/funtoo/ I get no such directory. So I am thinking it is because I am booted to "rescue" and then I try to run: mount /dev/sdb3/ /mnt/funtoo/ and I also got no such directory. I ran: mount /dev/sdb3/ / and it seemed to work but when I changed to / and looked around at some of the files and directories I found that I was looking at directories and files on the "rescue" Linux. I looked back in the instructions and they say: mkdir /mnt/funtoo mount /dev/sdb3 /mnt/funtoo However I do not want to create a new directory I want to mount what is already there, so I did not do that. As you can see I somewhat understand the commands and what I am doing but not really (my linux install is on sdb). I could use some help - even if it is "Hey you need to read this" - I will learn and want to learn. What got me here: Installing xfce4 after testing xwindows - the instructions say to edit /etc/conf.d/xdm and make these entries: DISPLAYMANAGER="<LightDM>" # rc-update add xdm default # rc-update add dbus default # rc Finished up with the other instructions - created power group and added root to it etc. rebooted and did not get my xfce session as expected so not knowing what I was doing, and I seem to remember from somewhere years ago that # in a config file = a comment, I ran the rc-update commands at the command prompt and rebooted now I am presented with a login screen and can get no where and cannot get a command prompt.