Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by geekt

  1. Thank you! Disappointed that didn't show up when I was searching. I spent over an hour, but that was mostly in the Gentoo forums, because that's usually where my answers to problems show up. It built beautifully after I removed cppunit. Only problem was me being dumb and forgetting to use -1 when reinstalling cppunit, so I had to go remove it from the world file, but gave me a chance to see if anything else needed to be removed. Thank you so much!
  2. I just got a few "new" old games, two of which run in DOSbox, and require libcaca. Needless to say, it fails, and I haven't been able to find a solution online. I was hoping that maybe someone could help me. emerge -pqv '=media-libs/libcaca-0.99_beta19::gentoo' [ebuild N ] media-libs/libcaca-0.99_beta19 USE="X cxx ncurses opengl python truetype -doc -imlib -java -mono (-ruby) -slang -static-libs {-test}" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python2_7" RUBY_TARGETS="ruby21 ruby22 ruby23 ruby24" emerge --info: https://pastebin.com/K5r10ABi build env: https://pastebin.com/ERQh6Wfd build log: https://pastebin.com/cpNMKJ16
  3. Well, I've got a new system installed, full with Python 3.5. Still needs some work, but that should be easy enough. I at least learned a few things from this experience. One was that I shouldn't have just changed my ABI's...especially with an unstable system where I couldn't simply recompile everything. I simply didn't remember how much of a pain the ABI's were, and why I had chosen to do a selectively mixed system, versus a fully mixed system, such as you had suggested. I had only dealt with them once, and hadn't reinstalled my system since the change to them had occurred. While trying to do the install, I tried to cheat and sort of patch a new install into the old one. I've done this before a few times years ago. It didn't work. I still got the same python maximum recursion error. That tells me that whatever the problem was, it wasn't in any of the standard config files, or even the base packages installed by Funtoo. Where the problem was, I don't know. I ended up wasting a ton of time doing that, then eventually moved my home folder onto another partition, and reinstalled Funtoo from scratch. This took all night, largely due to the fact that I chose to install Chromium with the base system, so I could use the web browser as soon as I started my system. I ended up going to bed super late, when Chromium had already been compiling for 3 and a half hours. If there's any package that makes me want to upgrade my system to an 8 core, it's Chromium. Before I even posted here I had researched the problem extensively and discovered a few other people that had had it before, but never saw a solution. It would have been nice if I could have found a solution, not only for myself, but for anyone that suffers from it in the future. I at least narrowed it down, minutely, to not being a base package.
  4. My system is mostly from the stable branch. I only use current when there's either no other option, or its something that needs to be current, or I just need or want a newer version. There's just something borked somewhere. Either in a config file, or some other part of the system.
  5. Well this isn't fun. It stopped with the same error on another dev-python package, and now I can't launch Chromium. Will post the logs for that package when I get it running again. Edit: I can't get even close to rebuilding chromium because of the dev-python packages. In the morning I'll likely have to boot from a flash drive and see if I can compile them. If not, I'll have to reinstall likely. BTW, the top of my package.use flag has */* python3_5 or something like that. Not in front of my coputer. But its functionally equivalent to what you said to put in the make.conf, but you had put 3.5, when it should have been python3_5. I ended up changing it to your way, because it seems like a more proper way.
  6. Yes, Python 3.5 is a requirement for various new python libraries that have come out in the last few years. The emerge world is actually going well so far. I expect it to fail any moment now...but it's not...which is odd... It should have hit the failing packages by now. But I did just do a sync, plus the changes you mentioned, so we'll see if by some miracle it's actually working now. Edit: Oh, duh. It's rebuilding practically everything, because now everything has the 32 bit ABI's, rather than only the ones that absolutely require it. On a side note: they probably would work with Python 3.4 if they made some conditionals, but a lot of the community is working on Python 3.5, so I'm not sure it's a priority.
  7. hmm...odd...that change caused python targets for 2.7 to disappear. I'm perfectly fine with that though, because I think it's about time that old code be updated to support newer python versions. I'll just add it for the individual packages requiring it. Will edit when I get through this mess of edits to package.use. Edit: Turns out that somehow adding the following to my make.conf actually got rid of all my python targets. Odd. I removed it. PYTHON_TARGETS="2.7 3.4 3.5" Will try with the python ABI's as well, which you added with an edit, but it's currently emerging some things. Maybe by some miracle it will go through the packages that were failing as well.
  8. Well, yeah. I would figure they would compile fine on other's. There's obviously something wrong with my system. I was just hoping someone could possibly point out what it might be. On a side note, you have a lot of USE variables. Edit: I replied before your further comment. I have the ABI's defined in my package.use for multi-lib: https://pastebin.com/2peEzBfF # eselect python list Available Python interpreters, in order of preference: [1] python3.4 [2] python3.5 [3] python2.7 (fallback) I have it currently set to python 3.4, but that was due to not being able to install pip with python 3.5, so I couldn't get a required lib I needed for development. I just switched it back. Same behavior. I did rely on my profile to set the proper optimizations, since my CPU family is selected, however I went ahead and added the CPU flags just now. This should probably be added to the documentation. The top result on google was for old news that was no longer accurate. cpuinfo2cpuflags is now called cpuid2cpuflags in portage. to run it you need to call cpuinfo2cpuflags-x86 And it seems setting it to python 3.5 breaks my epro, since it hasn't fully emerged everything yet. Set it back... # epro list === flavor: === core, desktop, hardened, minimal, server, workstation* === build: === current, experimental, (stable*) === arch: === arm-32bit, arm-64bit, pure64, x86-32bit, (x86-64bit*) === subarch: === amd64-bulldozer, amd64-excavator, amd64-jaguar, amd64-k10 amd64-k8, amd64-k8+sse3, amd64-piledriver, amd64-steamroller atom_64, btver1_64, core-avx-i, core2_64, corei7, generic_64 intel64-broadwell, intel64-haswell, intel64-ivybridge, intel64-nehalem intel64-sandybridge*, intel64-silvermont, intel64-westmere native_64, nocona, opteron_64, xen-pentium4+sse3_64 === mix-ins: === X, audio, cinnamon, console-extras, dvd, gfxcard-intel-glamor gnome, gnome-3.16-fixups, hardened, kde, kde-plasma-5, lxde lxqt, mate, media, media-pro*, mediadevice-audio-consumer, mediadevice-audio-pro mediadevice-base, mediadevice-video-consumer, mediadevice-video-pro mediaformat-audio-common, mediaformat-audio-extra*, mediaformat-gfx-common mediaformat-gfx-extra*, mediaformat-video-common, mediaformat-video-extra* no-emul-linux-x86, no-systemd, openvz-host, print*, python3-only selinux, vmware-guest, xfce*
  9. I've been having a few problems upgrading for a while, and I'm embarrassed to say I've let my box get a little out of date. I've been mainly upgrading on a package by package basis. Now, I need to upgrade to Python 3.5 as a dependency for some libs I'm working with, and the problems seem extensive. I managed to get Python upgraded to 3.5.3, but now pip is giving me trouble. I actually managed to solve quite a few of the problems, but a few are still giving me trouble. I'm about ready to give up and do a fresh install, but I figured I'd ask here first, to try to maybe get through them. I've cleaned out a lot of my world file of packages I don't really use, and cleaned up my package.use & package.accept_keywords, then rewrote them. Now I seem stuck on a few dev-python packages giving me "RuntimeError: maximum recursion depth exceeded" One of them is dev-python/certifi-2017.1.23 certifi build log: https://pastebin.com/Mdu44q8S make.conf: https://pastebin.com/t9306hDY emerge --info certifi: https://pastebin.com/kUZG9Knb emerge -pqv '=dev-python/certifi-2017.1.23::gentoo' [ebuild R ] dev-python/certifi-2017.1.23 PYTHON_TARGETS="python2_7 python3_4 python3_5* -pypy -pypy3 (-python3_6)"
  10. I haven't tried ssh-ing into it, as it's my main computer. However, I do know that it's only X freezing. No key combination allows me to escape X if I'm in it when it freezes. It's as if they aren't registering having been pressed. If I am outside of X when it freezes, I can keep working in the terminal. Except for with the latest versions of the intel drivers, command line applications would appear unresponsive simply due to running X in another console. I could run a console prog, but then it would just hang. I have not tried the debian source kernel. I had trouble trying to get it to boot when I was first installing.
  11. I'm now up to xf86-video-intel-2.99.910 in my attempt to find the most stable version. So far 2.99.905-r1 has seemed the most stable. I went a day and a half without any freezes. If I can't find any versions more stable than that I'll roll back to it. I'm hopeful though that I will be able to. I'm sure others have likely experienced this issue, and I'm just not confident that I have found the correct bug when reading info, so I'll try to talk to them directly about it. It doesn't help that no debug info is thrown though because it's not a crash.
  12. I believe that was the version of the Intel drivers that were working so bad for me I reverted to stable. The current branch of the intel drivers had seemed to be working better for me before the latest release, so I'll go through one at a time when I have the chance, and see if one version seems to be working better. For a few days it even seemed to not freeze at all. I was thinking maybe it might be a conflict between flash and the video drivers. The likelihood of a freeze seems to raises dramatically when I have more tabs open. But it could be just linked to processor or memory intensive tasks, as it most definitely seems to freeze whenever something spikes the processor up to 100%.
  13. Mainly just Chrome & Thunderbird most times. Chrome seems to take up a lot. I rolled back to the stable intel drivers, since it had gotten worse. Now the freezing seems a lot better. I'm able to emerge again with only momentary freezing of X. So it's likely a bug in them. I'll have to pay extremely close attention to it as new versions are stabilized. I managed to find similar issues dealing the HD3000 Intel drivers, with varying symptoms. Not sure, if it's the same issue. I'll try to find more info. They suggested upgrading to 3.4 kernel or switching to vesa drivers. I'll try to find more info or go ahead and switch drivers. There may be another version that's more stable.
  14. I just switched to Sawfish window manager and the problem persists, so it wasn't related to qtile. I can't even sync portage without it freezing now. ANY ideas of what might help to make it better would be greatly appreciated.
  15. I've had the issue of Xserver freezing when there's high CPU usage since install, but I can't seem to find exactly where the problem is. Everything freezes up. Can't use the mouse. Can't even switch out of Xserver to kill it. As a result I usually switch to the console when emerging so it doesn't freeze, but Thunderbird randomly spikes in CPU usage causing a freeze, or occasionally Flash. Searching online suggested it may be a driver issue or Xserver issue, so I switched to current for intel drivers & Xserver, but the problem persists. I kept with current for the intel drivers & Xserver though, because it seems to work a little better & therefore freeze less. I also saw a few things online suggesting that low swap space could be causing it. Despite having 8 gigs of ram, my swap space was somewhat full, so I increased it to 4 gigs from the standard recommended 2. It seems to run better, but the problem persisted. I also tried messing with niceness a few times, but that just changed the behavior of the freezing a bit. At one point I was able to get the freezes to not effect the mouse, but I still couldn't do anything. I'm using qtile, so perhaps it is a bug in that, but I want to try to ensure I didn't mess anything up. I think perhaps it might be a setting in the kernel config that I missed. .config > http://pastebin.com/TcS0uEg1 make.conf > http://pastebin.com/RnjNgGHc Running an Intel Quad Core i5 integrated graphics. Stable on encrypted ZFS with workstation eselect profile. Any additional info you need let me know. Thank you for your help in trying to resolve this issue. Edit: I haven't experienced the freezing for a few days, even though chromium updated, so perhaps something that updated has fixed the issue. I'll edit this again if the problem persists.
  16. Oh, so it is a bug. Wasn't sure. Thank you. Eselect emerged perfectly after using the workaround posted on the link above.
  17. Can't seem to update eselect. doins: /usr/portage/app-admin/eselect/files/1.3.8-r1/profile.eselect does not exist emerge --info '=app-admin/eselect-1.3.8-r1' > http://pastebin.com/nqst3RGA emerge -pqv '=app-admin/eselect-1.3.8-r1' > http://pastebin.com/LazfMAU7 eselect-1.3.8-r1 build log > http://pastebin.com/d18NnzVy eselect-1.3.8-r1 build env > http://pastebin.com/vCPnZ6Un
  • Create New...