Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

Oleg Vinichenko

Members
 View Profile  See their activity

  • Posts

    619

  • Joined

  • Last visited

  • Days Won

    53

 Content Type 

Posts posted by Oleg Vinichenko

  8. Confusion regarding debian-sources kernel and using LVM

    in Installation Help

    Posted

    for the 2) case, the debian-sources is compiled with initramfs which is created with LVM support by default. So, what you do is just unpack the stage into the volume that holds "/", use correct boot.conf, emerge lvm2 and add it's init script to boot runlevel. For the UEFI you just need additional partition formatted with FAT32. The LVM_Install does not cover this and this bit needs addition, but is as plain simple as having a separate partition with FAT32, rest of partition can be the LVM layout.

  22. Emerge Chromium: RAM requirements

    in Installation Help

    Posted

    unfortunately there is no 32-bit builds of chromium upstream anymore. and 64-bit during compilation exceeds 2GB, so there actually not much of an option for compiling it from sources.

    You could try setting  I_KNOW_WHAT_I_AM_DOING="1" emerge chromium with at least 4GB of swap enabled. It could pass. Alternatively, consider using precompiled versions such as google-chrome or firefox-bin.

  25. CFLAGS -O3 and emerge -e world have broken my world

    in General Help

    Posted

    no, there is no need to recompile kernel. Kernel has it's own compilation flags and which are quite specific and not the ones set for sources compilation on your box. generally, it is not recommended to deviate from the default flags. It is good that -O3 mostly work for you. For the rest of ebuilds that do not compile: ideally, those need fixed in source code, however it might be not the task for upstream. You can set specific package environment to have that list compiled with -O2. Here is how:

    mkdir -p /etc/portage/env

    create file in that directory called o2.conf (name is example, so you know what's the file about) with following content:

    CFLAGS="your flags -O2"

    CXXFLAGS="${CFLAGS}"

    Then, have following file:

    /etc/portage/package.env

    with contents:

    app-foo/bar o2.conf

    app-bar/baz o2.conf

    app-blarg/baroni o2.conf

    Use real category (app-foo) and package names (bar), those above are just dummy examples. Hope, this is clear.

     

×
×
  • Create New...