Uploaded image for project: 'Funtoo Linux'
  1. Funtoo Linux
  2. FL-6885

XDG_CACHE_HOME env var allowed inside ebuild environment, breaking go

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Normal Normal
    • None
    • None
    • None
    • Hide
      Set XDG_CACHE_HOME to any directory that Portage does not have write permissions.
      Run "ebuild" or "emerge" for the affected ebuild, and runc will fail with error of not being able to write to that directory.
      Show
      Set XDG_CACHE_HOME to any directory that Portage does not have write permissions. Run "ebuild" or "emerge" for the affected ebuild, and runc will fail with error of not being able to write to that directory.
    • Hide
      The root cause is that XDG_CACHE_HOME environment variable, when set, is allowed to propagate to the ebuild environment, and then the go compiler will mess up as this points to a non-writable location. The workaround is to use Gentoo's xdg_environment_reset function in src_prepare() (it's part of xdg-utils.eclass.)
      Show
      The root cause is that XDG_CACHE_HOME environment variable, when set, is allowed to propagate to the ebuild environment, and then the go compiler will mess up as this points to a non-writable location. The workaround is to use Gentoo's xdg_environment_reset function in src_prepare() (it's part of xdg-utils.eclass.)
    • Hide
      Exporting XDG_CACHE_HOME to point to any non-writeable-by-portage directory will result in runc failing.
      xdg-utils.eclass does set XDG_CACHE_HOME to $HOME/.cache.
      There is a newer version of runc where it has been reported that this issue is not reproducible. This has been shown to be FALSE. The issue reproducible with runc-1.0.0_rc9 as well.
      Show
      Exporting XDG_CACHE_HOME to point to any non-writeable-by-portage directory will result in runc failing. xdg-utils.eclass does set XDG_CACHE_HOME to $HOME/.cache. There is a newer version of runc where it has been reported that this issue is not reproducible. This has been shown to be FALSE. The issue reproducible with runc-1.0.0_rc9 as well.

    Description

      Fresh install as of 12/25/19 and installing steam-nvidia-launcher. app-emulation/runc fails to build immediately.

      Attachments

        1. build_env_2.txt
          8 kB
        2. build_log2.txt
          2 kB
        3. build.txt
          4 kB
        4. build-log.txt
          2 kB
        5. emerge-info.txt
          8 kB
        6. epro_show_and_emerge_pv.txt
          3 kB
        7. make_conf.txt
          0.7 kB
        8. set.txt
          53 kB

        Activity

          People

            drobbins drobbins
            azerthoth Jim Cook
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: