Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

onli

Members
 View Profile  See their activity

  • Posts

    38

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Posts posted by onli

  1. sdl2-image needs LDFLAG="-lm"

    in Portage Help

    Posted

    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 reference to 'floorf'
./.libs/libSDL2_image.so: error: undefined reference to 'acosf'
./.libs/libSDL2_image.so: error: undefined reference to 'ceilf'
./.libs/libSDL2_image.so: error: undefined reference to 'atan2f'
./.libs/libSDL2_image.so: error: undefined reference to 'sqrt'
./.libs/libSDL2_image.so: error: undefined reference to 'pow'
./.libs/libSDL2_image.so: error: undefined reference to 'tanf'
./.libs/libSDL2_image.so: error: undefined reference to 'fmodf'
collect2: error: ld returned 1 exit status
make: *** [Makefile:550: showimage] Error 1
 * ERROR: media-libs/sdl2-image-2.0.2::media-kit failed (compile phase):
 *   emake failed

    After a lot of searching I realized the linker is missing the lm flag: 

    sudo LDFLAGS="-lm"  emerge media-libs/sdl2-image

    That way it compiled successfully.

    Is that somehow specific to my system?

  2. encfs conflict with tinyxml2 upgrade

    in Portage Help

    Posted

    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?

  4. mesa stuck on 17.2.8

    in Portage Help

    Posted

    Quote

    You can use the version 1.20 of xorg-server, but mask the xorg-1.20.

    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 ?

  7. LXD failing setting up id map

    in General Help

    Posted

    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
Created: 2018/10/21 14:32 UTC
Status: Stopped
Type: persistent
Profiles: default

Log:

lxc pipeblock 20181021150139.557 ERROR    cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1198 - The cgroup "/sys/fs/cgroup/openrc//lxc/pipeblock" already existed
lxc pipeblock 20181021150139.558 ERROR    cgfsng - cgroups/cgfsng.c:cgfsng_create:1287 - Failed to create cgroup "/sys/fs/cgroup/openrc//lxc/pipeblock"
lxc pipeblock 20181021150139.558 ERROR    cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1198 - The cgroup "/sys/fs/cgroup/openrc//lxc/pipeblock-1" already existed
lxc pipeblock 20181021150139.558 ERROR    cgfsng - cgroups/cgfsng.c:cgfsng_create:1287 - Failed to create cgroup "/sys/fs/cgroup/openrc//lxc/pipeblock-1"
lxc pipeblock 20181021150139.558 ERROR    cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1198 - The cgroup "/sys/fs/cgroup/openrc//lxc/pipeblock-2" already existed
lxc pipeblock 20181021150139.558 ERROR    cgfsng - cgroups/cgfsng.c:cgfsng_create:1287 - Failed to create cgroup "/sys/fs/cgroup/openrc//lxc/pipeblock-2"
lxc pipeblock 20181021150139.563 ERROR    conf - conf.c:lxc_map_ids:2999 - newuidmap failed to write mapping "newuidmap: uid range [0-1000000000) -> [1000000-1001000000) not allowed": newuidmap 2186 0 1000000 1000000000
lxc pipeblock 20181021150139.563 ERROR    start - start.c:lxc_spawn:1677 - Failed to set up id mapping.
lxc pipeblock 20181021150139.627 WARN     network - network.c:lxc_delete_network_priv:2597 - Invalid argument - Failed to remove interface "vethB76GK4" from "lxdbr0"
lxc pipeblock 20181021150139.627 ERROR    lxccontainer - lxccontainer.c:wait_on_daemonized_start:840 - Received container state "ABORTING" instead of "RUNNING"
lxc pipeblock 20181021150139.628 ERROR    start - start.c:__lxc_start:1910 - Failed to spawn container "pipeblock"
lxc pipeblock 20181021150139.633 ERROR    conf - conf.c:lxc_map_ids:2999 - newuidmap failed to write mapping "newuidmap: uid range [0-1000000000) -> [1000000-1001000000) not allowed": newuidmap 2197 0 1000000 1000000000 1000000000 0 1
lxc pipeblock 20181021150139.633 ERROR    conf - conf.c:userns_exec_1:4358 - Error setting up {g,u}id mappings for child process "2197"
lxc pipeblock 20181021150139.633 WARN     cgfsng - cgroups/cgfsng.c:cgfsng_destroy:1119 - Failed to destroy cgroups
lxc 20181021150139.633 WARN     commands - commands.c:lxc_cmd_rsp_recv:130 - Connection reset by peer - Failed to receive response for command "get_state"

    Is there a likely reason for the cgroup already existing, and for newuidmpa to be failing?

     

  8. mesa stuck on 17.2.8

    in Portage Help

    Posted

    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?

  10. XA state tracker failure with mesa 18.2.0-rc2

    in General Help

    Posted

    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):lp_bld_tgsi_action.c:function d2f_emit: error: undefined reference to 'LLVMBuildFPTrunc'
src/gallium/auxiliary/libgallium.a(gallivm_lp_bld_tgsi_action.c.o):lp_bld_tgsi_action.c:function up2h_emit: error: undefined reference to 'LLVMInt16TypeInContext'
src/gallium/auxiliary/libgallium.a(gallivm_lp_bld_tgsi_action.c.o):lp_bld_tgsi_action.c:function i64div_emit_cpu: error: undefined reference to 'LLVMBuildSDiv'
src/gallium/auxiliary/libgallium.a(gallivm_lp_bld_tgsi_action.c.o):lp_bld_tgsi_action.c:function u64div_emit_cpu: error: undefined reference to 'LLVMBuildUDiv'
src/gallium/auxiliary/libgallium.a(gallivm_lp_bld_format_aos_array.c.o):lp_bld_format_aos_array.c:function lp_build_fetch_rgba_aos_array: error: undefined reference to 'LLVMBuildFPTrunc'

    I already recompiled gcc and llvm, so I'm stuck there.

    But maybe removing xa makes it work for you and the llvm stuff is something specific to my system?

     

  11. XA state tracker failure with mesa 18.2.0-rc2

    in General Help

    Posted

    I just tried to do a system upgrade. I get this error message for the mesa build:

    Quote

    Meson encountered an error in file meson.build, line 593, column 4:
    Problem encountered: XA state tracker requires at least one of the following gallium drivers: nouveau, freedreno, i915, svga.

    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. Invalid token '1999-2017' (not '=')

    in Portage Help

    Posted

    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.

  16. Invalid token '1999-2017' (not '=')

    in Portage Help

    Posted

    I'm running this script for upgrades: 

    #!/bin/sh
ego sync
emerge --sync
layman -S
emerge -uavDN @world

    But today I'm getting the error message from the title. The full message is:

    Quote

    "/var/git/meta-repo/kits/core-kit/profiles/base/make.defaults", line 1: Invalid token '1999-2017' (not '=')

    That means one of those scripts removes the # sign from the first line of that file. There is an other error before: 

    Already up to date.
Sync successful and kits in alignment! :)
Updating /etc/portage/repos.conf...
Updating profiles at /etc/portage/make.profile/parent...
Updating non-funtoo repositories...
Traceback (most recent call last):
  File "/usr/bin/ego", line 120, in <module>
    EgoModule.run_ego_module(action, econfig, args, VERSION)
  File "/usr/share/ego/python/ego/module.py", line 102, in run_ego_module
    ego_module(*args)
  File "/usr/share/ego/python/ego/module.py", line 87, in __call__
    self.handle()
  File "/usr/share/ego/modules/sync.ego", line 337, in handle
    self.sync_meta_repo()
  File "/usr/share/ego/modules/sync.ego", line 325, in sync_meta_repo
    self._do_package_moves()
  File "/usr/share/ego/modules/sync.ego", line 46, in _do_package_moves
    import portage
ImportError: No module named 'portage'

    Full output here. I'm not aware of having changed anything related to this. How can I fix this?

     

  17. Getting newer mesa version?

    in Desktop Help

    Posted

    Hi, just checking in to see if I'm doing something wrong. I'm running the current funtoo, I switched to 1.2 pretty early. Now my steam package (coming from the overlay) is complaining: 

    emerge: there are no ebuilds to satisfy ">=media-libs/mesa-17.3.9[-bindist(-)]".
(dependency required by "games-util/steam-games-meta-0-r20180619::steam-overlay" [ebuild])

    And if I understand this right, https://github.com/funtoo/xorg-kit/tree/master/media-libs/mesa got his last upgrade indeed 9 month ago, while https://gentoobrowse.randomdan.homeip.net/packages/media-libs/mesa and https://mesa.freedesktop.org/ look like there were some updates. Am I looking into the wrong place, or is that kit just a bit behind (which would not be a big problem yet, it's just that mesa upgrades are often very useful for getting better performance).

  18. AssertionError: setcpv recursion detected

    in Portage Help

    Posted

    Hm, it seemed to work just fine with Python 2.7 as the first, but I changed it around. Thanks :)

    That I double-posted to describe the solution was not really easy to see with the re-ordering going on here, sorry about that. Everything is good now (or rather, the QT issues I have now seem to be unrelated and already in the bugtracker).

     

  19. AssertionError: setcpv recursion detected

    in Portage Help

    Posted

    Okay, I got it. A configuration thing/possible conflict. I had added this to package.use:

    Quote

    >=dev-libs/xmlsec-1.2.24[nss] gcrypt

    Because I had gotten this error before:

    Quote

    onli@Fallout:~$ sudo emerge --ask --update --deep --with-bdeps=y --newuse @world

    These are the packages that would be merged, in order:

    Calculating dependencies... done!

    Oops! Conflicts have been encountered:

    >>> games-util/xboxdrv-0.8.8:0/0::gentoo, installed, wants dev-libs/boost:0/1.62.0=

    My candidates are:

    >>> dev-libs/boost-1.63.0:0/1.63.0::core-kit, ebuild scheduled for merge has SLOT 0/1.63.0
    >>> dev-libs/boost-1.62.0-r1:0/1.62.0::gentoo, installed has SLOT 0/1.62.0
    >>> dev-libs/boost-1.63.0:0/1.63.0::core-kit, ebuild scheduled for merge, wants =dev-util/boost-build-1.63*
    >>> dev-libs/boost-1.62.0-r1:0/1.62.0::gentoo, installed, wants =dev-util/boost-build-1.62*

    My candidates are:

    >>> dev-util/boost-build-1.63.0:0/0::core-kit, ebuild scheduled for merge has SLOT 0/0
    >>> dev-util/boost-build-1.62.0-r1:0/0::gentoo, installed has SLOT 0/0


    We hope this informational output has been useful in identifying the
    problem. We are continually working to reduce conflicts. Do not
    hesitate to report a bug at https://bugs.funtoo.org. Thank you! :)


    !!! The ebuild selected to satisfy ">=dev-libs/xmlsec-1.2.24[nss]" has unmet requirements.
    - dev-libs/xmlsec-1.2.24-r1::dev-kit USE="gnutls openssl -doc -gcrypt -libressl -nss -static-libs"

      The following REQUIRED_USE flag constraints are unsatisfied:
        gnutls? ( gcrypt )

      The above constraints are a subset of the following complete expression:
        any-of ( gcrypt gnutls nss openssl ) gnutls? ( gcrypt )

    (dependency required by "app-office/libreoffice-5.4.2.2::kde-kit" [ebuild])
    (dependency required by "@selected" [set])
    (dependency required by "@world" [argument])

    Now I removed that line and unmerged libreoffice, emerge could calculate the upgrade and found 72. Yeah :)

    Thanks for the help!

  20. AssertionError: setcpv recursion detected

    in Portage Help

    Posted

    I did an ego sync now, but that did not help.

    There is no error when updating ego :) That works just fine, it gets compiled.
    Portage might be outdated, but I tried to update it like ego, did not change.

    Quote

    onli@Fallout:~$ emerge --version
    Portage 2.3.11 (python 2.7.13-final-0, funtoo/1.0/linux-gnu/arch/x86-64bit, gcc-4.9.3, glibc-2.23-r4, 4.8.15-1 x86_64)

     

     

  21. AssertionError: setcpv recursion detected

    in Portage Help

    Posted

    @Sandro:

    Quote

    onli@Fallout:~$ eselect python list
    Available Python interpreters, in order of preference:
      [1]   python2.7
      [2]   python3.4

    (Sorry, the Code Box does not work).

    @dhudson: I did that already (and now tried again of course), does not help. Though I don't actually know what ego does. Do I have to call that before using that emerge command, or is that used internally by emerge?

     

     

  22. AssertionError: setcpv recursion detected

    in Portage Help

    Posted

    I run the kit system for a while now. Was gone for the month, now when I try to upgrade I get this:

    Quote

     

    onli@Fallout:~$ sudo emerge --ask --update --deep --with-bdeps=y --newuse @world

    These are the packages that would be merged, in order:

    Calculating dependencies... done!
    Traceback (most recent call last):
      File "/usr/lib/python-exec/python2.7/emerge", line 50, in <module>
        retval = emerge_main()
      File "/usr/lib64/python2.7/site-packages/_emerge/main.py", line 1250, in emerge_main
        return run_action(emerge_config)
      File "/usr/lib64/python2.7/site-packages/_emerge/actions.py", line 3297, in run_action
        retval = action_build(emerge_config, spinner=spinner)
      File "/usr/lib64/python2.7/site-packages/_emerge/actions.py", line 339, in action_build
        settings, trees, myopts, myparams, myaction, myfiles, spinner)
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 9579, in backtrack_depgraph
        myaction, myfiles, spinner)
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 9616, in _backtrack_depgraph
        success, favorites = mydepgraph.select_files(myfiles)
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 3791, in select_files
        return self._select_files(args)
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 4134, in _select_files
        return self._resolve(myfavorites)
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 4285, in _resolve
        if not self._create_graph():
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 2561, in _create_graph
        allow_unsatisfied=allow_unsatisfied):
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 3285, in _add_pkg_deps
        allow_unsatisfied):
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 3301, in _add_pkg_dep_string
        allow_unsatisfied)
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 3381, in _wrapped_add_pkg_dep_string
        pkg, dep_priority, root_config, selected_atoms[pkg]):
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 3580, in _minimize_children
        root_config.root, atom, parent=parent)
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 5569, in _select_pkg_highest_available
        ret = self._select_pkg_highest_available_imp(root, atom, onlydeps=onlydeps, parent=parent)
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 5793, in _select_pkg_highest_available_imp
        root, atom, onlydeps=onlydeps, parent=parent)
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 6094, in _wrapped_select_pkg_highest_available_imp
        onlydeps=onlydeps):
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 5487, in _iter_match_pkgs_atom
        installed=installed, onlydeps=onlydeps, myrepo=repo)
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 6834, in _pkg
        if not self._pkg_visibility_check(pkg) and \
      File "/usr/lib64/python2.7/site-packages/_emerge/depgraph.py", line 5837, in _pkg_visibility_check
        if pkg.visible:
      File "/usr/lib64/python2.7/site-packages/_emerge/Package.py", line 177, in visible
        self._visible = self._eval_visiblity(self.masks)
      File "/usr/lib64/python2.7/site-packages/_emerge/Package.py", line 171, in masks
        self._masks = self._eval_masks()
      File "/usr/lib64/python2.7/site-packages/_emerge/Package.py", line 403, in _eval_masks
        self.cpv, self._metadata)
      File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/config.py", line 2066, in _getMissingLicenses
        cpv, metadata["USE"], metadata["LICENSE"], metadata["SLOT"], metadata.get('repository'))
      File "/usr/lib64/python2.7/site-packages/_emerge/Package.py", line 873, in __getitem__
        v = self._pkg._init_use()
      File "/usr/lib64/python2.7/site-packages/_emerge/Package.py", line 665, in _init_use
        use_str = self._get_pkgsettings()["PORTAGE_USE"]
      File "/usr/lib64/python2.7/site-packages/_emerge/Package.py", line 640, in _get_pkgsettings
        pkgsettings.setcpv(self)
      File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/config.py", line 1411, in wrapper
        return f(self, *args, **kwargs)
      File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/config.py", line 1586, in setcpv
        self.puse = self._use_manager.getPUSE(cpv_slot)
      File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/_config/UseManager.py", line 558, in getPUSE
        puse_matches = ordered_by_atom_specificity(cpdict, pkg)
      File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/_config/helper.py", line 34, in ordered_by_atom_specificity
        bestmatch = best_match_to_list(pkg, keys)
      File "/usr/lib64/python2.7/site-packages/portage/dep/__init__.py", line 2066, in best_match_to_list
        for x in match_to_list(mypkg, mylist):
      File "/usr/lib64/python2.7/site-packages/portage/dep/__init__.py", line 2034, in match_to_list
        if x not in matches and match_from_list(x, pkgs):
      File "/usr/lib64/python2.7/site-packages/portage/dep/__init__.py", line 2349, in match_from_list
        use = getattr(x, "use", None)
      File "/usr/lib64/python2.7/site-packages/_emerge/Package.py", line 634, in use
        self._init_use()
      File "/usr/lib64/python2.7/site-packages/_emerge/Package.py", line 665, in _init_use
        use_str = self._get_pkgsettings()["PORTAGE_USE"]
      File "/usr/lib64/python2.7/site-packages/_emerge/Package.py", line 640, in _get_pkgsettings
        pkgsettings.setcpv(self)
      File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/config.py", line 1408, in wrapper
        raise AssertionError('setcpv recursion detected')
    AssertionError: setcpv recursion detected

     

    I already deleted /var/git/meta-repo and followed https://github.com/funtoo/meta-repo#using-meta-repo to recreate it, but now I don't have any ideas left.

     

  23. meld requires too new glib 2.50:2

    in Portage Help

    Posted

    Hi jhan. I think there was an update to the ebuilds by now. I am not aware of having changed my system (and certainly not the USE flags), but meld compiles now.

     

    The dbus USE flag is disabled on my system, but I had to enable it for some specific packages. But I don't see it activated for meld.

  24. meld requires too new glib 2.50:2

    in Portage Help

    Posted

    Emerge is failing to upgrade:

    emerge: there are no ebuilds to satisfy ">=dev-libs/glib-2.50:2[dbus]".
(dependency required by "dev-util/meld-3.17.4::dev-kit" [ebuild])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

    And indeed, the ebuild of meld, https://github.com/funtoo/dev-kit/blob/master/dev-util/meld/meld-3.17.4.ebuild, got an update 6 hours ago that added a new ebuild for 3.17.4 that requires glib-2.50:2, but https://github.com/funtoo/gnome-kit/tree/3.20-prime/dev-libs/glib contains no ebuild for that version.

     

    Should I report this in the bug tracker?

×
×
  • Create New...