Jump to content
funtoo forums

Search the Community

Showing results for tags 'ebuild'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Funtoo Discussion Forums
    • News and Announcements
    • General Discussion
    • Dev Central
    • Funtoo Hosting
    • Funtoo Infrastructure
  • Help Central
    • General Help
    • Installation Help
    • Portage Help
    • Desktop Help
    • Server Help
  • Funtoo Services

Blogs

There are no results to display.

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


freenode


github


Location


Interests

Found 12 results

  1. NikosAlexandris

    No ebuild for qscintilla-2.10.4

    QGIS requires `qscintilla-python` which in turn requires `qscintilla`. Version 2.10.4 for the latter, seems not to be available. See emerge -av qgis These are the packages that would be merged, in order: Calculating dependencies... done! emerge: there are no ebuilds to satisfy "~x11-libs/qscintilla-2.10.4:=". (dependency required by "dev-python/qscintilla-python-2.10.4::python-modules-kit" [ebuild]) (dependency required by "sci-geosciences/qgis-9999::science-kit[python]" [ebuild]) (dependency required by "qgis" [argument]) This ebuild exists in the gentoo repository: https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-libs/qscintilla/qscintilla-2.10.4.ebuild How do we "upgrade" in Funtoo?
  2. As part of my try to build ROS2 Bouncy distribution with Funtoo I added ros-overlay to my repository. At present i get a build error for the package ros-bouncy/ament_cmake_core-0.5.1 Since i was unable to upload the file, there here is my /var/tmp/portage/ros-bouncy/ament_cmake_core-0.5.1/temp/build.log: As i tried to investigate the problem, i found that i do have package ament_package, but at a different path: As you can see, /opt/ros/bouncy/lib64/python3.6/site-packages rather then /usr/lib64/python3.6/site-packages. My guess is that the PYTHONPATH which is set in /var/git/overlay/ros-overlay/eclass/ament-cmake.eclass is not correct.
  3. Is there a reason Funtoo seems to be lagging behind with certain software? The one I notice in particular is with desktop environments: Plasma is only available as version 5.12.3 and LXQt is only available as 0.11. I can somewhat understand Plasma 5.12, since that is the LTS release, though I'd like to see the improvements from 5.13 on my Funtoo system. 5.12.6 is the latest LTS though, so it's still behind the current LTS. LXQt being on 0.11 means two years of not being updated, with the project now on 0.13. Is this due to following Gentoo (I notice 5.12.5 and 0.11 being the latest "stable" ebuilds, respectively) and not bringing over the "testing" ebuilds? A lack of manpower to keep these things updated? If the former, would it be possible to have non-default "current" branches of DE kits so we can get the latest stable version? I notice that I could subscribe to the KDE and Qt Gentoo testing overlays, but I assume they are called "testing" for a reason and would rather not chance random breakages from unstable build scripts.
  4. skunk

    chromium 65

    hello, any chance to get safe chromium ebuild to the tree? thank you
  5. znavko

    20 GiB of free space?

    Hello, dear Funtoo developers! I want to ask about free space for debian-sources. Why 20GiB ? # eix-sync ... # emerge -auDN debian-sources These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild NS ] sys-kernel/debian-sources-4.14.12 [4.8.15, 4.14.2] USE="binary" Would you like to merge these packages? [Yes/No] yes >>> Recording sys-kernel/debian-sources:4.14.2 in "world" favorites file... >>> Verifying ebuild manifests >>> Running pre-merge checks for sys-kernel/debian-sources-4.14.12 * Checking for at least 20 GiB disk space at "/var/tmp/portage/sys-kernel/debian-sources-4.14.12/temp" ... [ !! ] * There is NOT at least 20 GiB disk space at "/var/tmp/portage/sys-kernel/debian-sources-4.14.12/temp" * * Space constraints set in the ebuild were not met! * The build will most probably fail, you should enhance the space * as per failed tests. * * ERROR: sys-kernel/debian-sources-4.14.12::core-kit failed (pretend phase): * Build requirements not met! * * Call stack: * ebuild.sh, line 121: Called pkg_pretend * debian-sources-4.14.12.ebuild, line 41: Called check-reqs_pkg_setup * check-reqs.eclass, line 99: Called check-reqs_output * check-reqs.eclass, line 255: Called die * The specific snippet of code: * [[ ${EBUILD_PHASE} == "pretend" && -z ${I_KNOW_WHAT_I_AM_DOING} ]] && \ * die "Build requirements not met!" * * If you need support, post the output of `emerge --info '=sys-kernel/debian-sources-4.14.12::core-kit'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/debian-sources-4.14.12::core-kit'`. * The complete build log is located at '/var/tmp/portage/sys-kernel/debian-sources-4.14.12/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/debian-sources-4.14.12/temp/die.env'. * Working directory: '/var/tmp/portage/sys-kernel/debian-sources-4.14.12/homedir' * S: '/var/tmp/portage/sys-kernel/debian-sources-4.14.12/work/linux-4.14.12' * Messages for package sys-kernel/debian-sources-4.14.12: * There is NOT at least 20 GiB disk space at "/var/tmp/portage/sys-kernel/debian-sources-4.14.12/temp" * * Space constraints set in the ebuild were not met! * The build will most probably fail, you should enhance the space * as per failed tests. * * ERROR: sys-kernel/debian-sources-4.14.12::core-kit failed (pretend phase): * Build requirements not met! * * Call stack: * ebuild.sh, line 121: Called pkg_pretend * debian-sources-4.14.12.ebuild, line 41: Called check-reqs_pkg_setup * check-reqs.eclass, line 99: Called check-reqs_output * check-reqs.eclass, line 255: Called die * The specific snippet of code: * [[ ${EBUILD_PHASE} == "pretend" && -z ${I_KNOW_WHAT_I_AM_DOING} ]] && \ * die "Build requirements not met!" * * If you need support, post the output of `emerge --info '=sys-kernel/debian-sources-4.14.12::core-kit'`, * the complete build log and the output of `emerge -pqv '=sys-kernel/debian-sources-4.14.12::core-kit'`. * The complete build log is located at '/var/tmp/portage/sys-kernel/debian-sources-4.14.12/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/debian-sources-4.14.12/temp/die.env'. * Working directory: '/var/tmp/portage/sys-kernel/debian-sources-4.14.12/homedir' * S: '/var/tmp/portage/sys-kernel/debian-sources-4.14.12/work/linux-4.14.12'
  6. Otakku

    Question about GCC 5.4

    Hi folks, I wonder if may I use the Gentoo ebuild to install the GCC 5.4, I looked and the funtoo gcc 5.3-r1 ebuild is different of gentoo 5.3 or 5.4 ebuild is safe use the gentoo ebuild to do that ?
  7. therickaman

    Question about USE Flags

    Hello All, I have a question regarding the use flags with the intel64-haswell subarch. Since I don't plan to compile code on any other machine but the computer I'm installing on, why would the use flag -march=core-avx2 be superior to -march=native? Perhaps I'm incorrect, but wouldn't -march=native be best for me? If not, why? I'm really confused by core-avx2. I could be wrong, but I think using -march=native is equivalent to -march=haswell in this case. If so, is -march=haswell different from -march=core-avx2? I did notice that the CPU_FLAGS mentioned on the subarch page missed avx2, so I added that into the CPU_FLAGS within make.conf. Any help would be greatly appreciated. Thanks, Rick
  8. Hi - Is anyone having issues with these two ebuilds in the last two or three days? After recent update of @world, I am left with only two these packages which fail to build. Thought I would quick post here to see it anyone else had noticed issues with these two packages recently. Checking at bugs.funtoo.org, a search shows no recent trouble with these. Best Regards
  9. ballsystemlord

    no python doc package?

    Hello, I am installing funtoo and I copied my make.conf, package.use, etc. files over since I liked that use flags I'm using and I got a messsage while updating world that there are no ebuilds for dev-python/python-docs needed by dev-lang/python-3.3.6-r1000 with the doc use flag enabled. I'm not sure if this is a bug in the ebuild or what.
  10. zombiechicken

    Wanting to contribute ebuilds

    I'm wanting to start contributing ebuilds, but right now I'm not sure exactly what I'd need to do to set that up. I have a github account and have the ebuilds posted there, but I want to know how I should go about setting up the repo and whatnot to make it easy for someone else to merge it into the main tree. For reference, the repo is https://github.com/ZombieChicken/funtoo-ebuild-contrib (I hope the name isn't too confusing) If someone could take a look at that and tell me what I need to do, or preferably link me to the documentation, I'd be thrilled.
  11. Is there a way to pull dead ebuilds (no longer in Funtoo tree) from funtoo git? I can access dead gentoo ebuilds and files from sources.gentoo.org. Is there any way to access and download dead funtoo-ported ebuilds from funtoo's git tree?
  12. Hello everybody! after six years using Linux distributions like fedora and sabayon , finally i decided to move to a really serious distro. I was researching on what kind of meta-distro must be installed on my computer and i really really liked the funtoo way for linux since the first time i meet the welcome page in funtoo.org, ,,, anyway, i was wondering on how to install the Mate environment over my new stage 3 tarball and brand new compiled kernel already installed on my hard drive. First i take a look to http://www.funtoo.org/MATE_Desktop, but when i needed to do the following step: cp /usr/portage/sets/mate /etc/portage/sets suddenly the things went very dark... the '/usr/portage/sets/mate' doesn't exist on my installation, i decided to install Mate following the little guide provided by the gentoo wiki (http://wiki.gentoo.org/wiki/MATE), after that, finally i can run the mate desktop by 'startx' , but to be honest, the desktop really sucks balls, it lack a lot of things that usally i need: doesn't mount any kind of media, doesn't have network manager, there are no sound, even i don't know how to set up the time. So, how to correctly install the Mate environment?? or how to complete the installation of the very minimal 'mate-base/mate' desktop. I really appreciate any information or any help . Thanks!
×