Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


onli last won the day on August 6 2017

onli had the most liked content!

About onli

  • Rank
    Advanced Member

Recent Profile Visitors

719 profile views
  1. That's more a questions whether someone can confirm it's a bug and I should report it somewhere else. When emerging media-libs/sdl2-image I got this error: libtool: link: x86_64-pc-linux-gnu-gcc -m32 -I/usr/include/libpng16 -march=native -O1 -pipe -I/usr/include/SDL2 -D_REENTRANT -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -o .libs/showimage showimage.o ./.libs/libSDL2_image.so -lpng16 -ljpeg -ltiff -lz -lwebp -lSDL2 ./.libs/libSDL2_image.so: error: undefined reference to 'sqrtf' ./.libs/libSDL2_image.so: error: undefined reference to 'sincosf' ./.libs/libSDL2_image.so: error: undefined ref
  2. I try to upgrade my system and run into an issue again. This time it is encfs: That relies on dev-libs/tinyxml2:0/3, but the upgrade schedules an upgrade for that: WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: dev-libs/tinyxml2:0 (dev-libs/tinyxml2-6.0.0:0/6::dev-kit, ebuild scheduled for merge) conflicts with dev-libs/tinyxml2:0/3 required by (sys-fs/encfs-1.9.2:0/0::core-kit, installed) ^^^^ Nothing to merge; quitting. What's the best solution here?
  3. The issue still seems to exist?
  4. onli

    mesa stuck on 17.2.8

    Thanks. I'm getting this error on an upgrade after this: ERROR: Specified xorg-kit branch 1.20-release is missing! Is it included in this release? Exiting. Do I have to run anything else instead of `ego sync`? Edit: notized the error message looks like there is a tab or something before the version number, so I added the xorg-kit line again. Seems to have worked now, I will now upgrade the system. Let's see ?
  5. Hi Yes, I think so. I did the lxd init, created /etc/subuid and subguid and executed the usermod commands.
  6. onli

    mesa stuck on 17.2.8

    Oh, so it's not my system that has a problem there? Thanks for the confirmation. I just bought a RX 580, hope the update arrives before the card.
  7. Hi I tried to get LXD working. I noticed the wiki page https://www.funtoo.org/LXD but it does not work for me (and I'm surprised to see calls to "service", is that usually installed?) I can execute launch, but the image then does not start. I get this error message: onli@Fallout:~$ lxc start pipeblock Error: Failed to run: /usr/libexec/lxd forkstart pipeblock /var/lib/lxd/containers /var/log/lxd/pipeblock/lxc.conf: Try `lxc info --show-log pipeblock` for more info onli@Fallout:~$ lxc info --show-log pipeblock Name: pipeblock Location: none Remote: unix:// Architecture: x86_64
  8. Hi A new mesa version would be important to me, I play quite often right now, also thanks to Steams Proton thing. I just stumbled over the news that the new version will contain game specific patches. There was already a post in this forum some time ago that mesa should be update soon, but that did not seem to happen. Or is there something wrong with my system?
  9. @Oleg Vinichenko Okay, thank you! I got a bunch of different related upgrades that worked. But mesa is still on 17.2.8, was that the idea? I guess that 18.2.0-rc2 was a mistake, but 18.1.5 should be the target now, right?
  10. I tried to fix this by removing the xa useflag I had in my /etc/portage/make.conf. That specific error vanished for me. However, now I'm getting a different error. I'm not even sure what exactly goes wrong there. Is it stopping because of the warning? {anonymous}::get_symbol_offsets(const llvm::Module&)’ defined but not used [-Wunused-function] get_symbol_offsets(const ::llvm::Module &mod) { ^~~~~~~~~~~~~~~~~ After all that is the last compilation step done. Or is the problem the llvm lib issues above? src/gallium/auxiliary/libgallium.a(gallivm_lp_bld_tgsi_action.c.o
  11. I just tried to do a system upgrade. I get this error message for the mesa build: The log of this is here. It mentions the meson log, I uploaded that one here. The initial portage output is here I will now dig into the libva problem, maybe the issue is that requirement? I'm using the radeon driver and do not see how any of those options mentioned in the error message could be required for me.
  12. Hm, an incompatibility with python 3.4 would be bad. But it seems it works now. So, what I did: sudo eselect python set 3 to select python 3.5, and then I re-added the missing # to the first line of /var/git/meta-repo/kits/core-kit/profiles/base/make.defaults. Now the upgrade commands reacht the step of calculating dependencies, unlike before. Thanks.
  13. @kris: onli@Fallout:~$ sudo eselect python list Password: Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 [3] python3.5 (fallback) You mean portage/ego relies on python 2 and I should select that?
  14. I think so, doesn't that follow from the log file output? Where do I check that?
  15. Otakku, I hadn't seen your. Though your thread is marked [solved] without there being a fix in the thread. How did you solve it? I can of course add the # to the file, but when I try to upgrade it gets removed again.
  • Create New...