Re: [gentoo-user] Re: OT scripting - strip zero if between period and digit

[Alexander Kapshuk]

On Wed, Jan 23, 2019 at 9:41 PM Grant Edwards  wrote:
>
> On 2019-01-23, Alexander Kapshuk  wrote:
>
> > This any better? :-)
> >
> > echo '198.088.0.01
> > 198.088.062.01
> > 198.088.0.001' | sed -r 's/\.0+([^.0]+)/.\1/g'
>
> I guess it's 'better', but it's still broken:
>
> $ echo '003.4.5.6' | sed -r 's/\.0+([^.0]+)/.\1/g'
> 003.4.5.6
>
> This is not a good application for a regex.
>
> --
> Grant Edwards   grant.b.edwardsYow! I have accepted
>   at   Provolone into my life!
>   gmail.com
>
>
The OP stated that there were no leading zeros in the first octet of
the IP address, so that case did not need to be handled.

Re: [gentoo-user] Re: OT scripting - strip zero if between period and digit

[Alexander Kapshuk]

On Wed, Jan 23, 2019 at 4:10 PM Grant Edwards  wrote:
>
> On 2019-01-23, Alexander Kapshuk  wrote:
> >
> > How about this one?
> >
> > echo '198.088.0.01
> > 198.088.062.01' | sed 's/\.0\([0-9][0-9]*\)/.\1/g'
> > 198.88.0.1
> > 198.88.62.1
>
> Also no.
>
> $ echo 198.088.0.001 |   sed 's/\.0\([0-9][0-9]*\)/.\1/g'
> 198.88.0.01
>
>
> --
> Grant Edwards   grant.b.edwardsYow! Hello.  Just walk
>   at   along and try NOT to think
>   gmail.comabout your INTESTINES being
>almost FORTY YARDS LONG!!
>
>

This any better? :-)

echo '198.088.0.01
198.088.062.01
198.088.0.001' | sed -r 's/\.0+([^.0]+)/.\1/g'
198.88.0.1
198.88.62.1
198.88.0.1

Re: [gentoo-user] OT scripting - strip zero if between period and digit

[Alexander Kapshuk]

On Wed, Jan 23, 2019 at 9:05 AM Paul Colquhoun
 wrote:
>
> On Wednesday, 23 January 2019 5:52:57 PM AEDT Alexander Kapshuk wrote:
> > On Wed, Jan 23, 2019 at 5:20 AM Adam Carter  wrote:
> > >> > François-Xavier
> > >>
> > >> My bad, it should be:
> > >>
> > >> sed 's/0*\([0-9][0-9]*\)/\1/g'
> > >>
> > >> (tests are indeed needed!)
> > >
> > > Many thanks François. This is almost right, but it is also stripping zeros
> > > that follow a letter, and I only want it to strip zeros that are
> > > proceeded by a period. There are no leading zeros in the first octet of
> > > the IP so that case does not need to be handled.
> > >
> > > Does the \1 refer to what's in the ()'s? So anything that one would wont
> > > to carry through should be inside the ()'s and anything that's outside is
> > > stripped, right?
> > Would something like to do the trick?
> > echo 198.088.062.01 | sed 's/\.0/./g'
> > 198.88.62.1
>
> In a word, no.
>
> echo 198.088.0.01 | sed 's/\.0/./g'
> 198.88..1
>
>
> --
> Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/
>   Asking for technical help in newsgroups?  Read this first:
>  http://catb.org/~esr/faqs/smart-questions.html#intro
>
>
>
>

How about this one?

echo '198.088.0.01
198.088.062.01' | sed 's/\.0\([0-9][0-9]*\)/.\1/g'
198.88.0.1
198.88.62.1

Re: [gentoo-user] OT scripting - strip zero if between period and digit

[Alexander Kapshuk]

On Wed, Jan 23, 2019 at 5:20 AM Adam Carter  wrote:
>>
>> > François-Xavier
>> >
>> >
>>
>> My bad, it should be:
>>
>> sed 's/0*\([0-9][0-9]*\)/\1/g'
>>
>> (tests are indeed needed!)
>
>
> Many thanks François. This is almost right, but it is also stripping zeros 
> that follow a letter, and I only want it to strip zeros that are proceeded by 
> a period. There are no leading zeros in the first octet of the IP so that 
> case does not need to be handled.
>
> Does the \1 refer to what's in the ()'s? So anything that one would wont to 
> carry through should be inside the ()'s and anything that's outside is 
> stripped, right?
>
>
>

Would something like to do the trick?
echo 198.088.062.01 | sed 's/\.0/./g'
198.88.62.1

Re: [gentoo-user] Re: bash upgrading problem

[Alexander Kapshuk]

On Mon, Jan 21, 2019 at 3:43 PM Jacques Montier  wrote:
>
>
> Le lun. 21 janv. 2019 à 14:16, Alexander Kapshuk 
>  a écrit :
>>
>>
>>
>> What is the output of:
>> env | grep libsandbox.so
>>
>
> There is no output of env | grep libsandbox.so, but with env | grep sandbox, 
> i get this :
>
> $ env | grep sandbox
> 13:CONFIG_PROTECT_MASK=/etc/sandbox.d /etc/php/cli-php7.2/ext-active/ 
> /etc/php/cgi-php7.2/ext-active/ /etc/php/apache2-php7.2/ext-active/ 
> /etc/fonts/fonts.conf /etc/gentoo-release /etc/gconf /etc/terminfo /etc/dconf 
> /etc/ca-certificates.conf /etc/revdep-rebuild
>
> --
> Jacques
>

(1). Are you attempting to build bash as yourself or as user root?
(2). If the latter, what's in LD_PRELOAD and LD_LIBRARY_PATH?

(3). What's the output of:
ls -l /path/to/libsandbox.so?
(4). And:
file /path/to/libsandbox.so

Re: [gentoo-user] Re: bash upgrading problem

[Alexander Kapshuk]

On Mon, Jan 21, 2019 at 3:03 PM Jacques Montier  wrote:
>
> Le lun. 21 janv. 2019 à 13:04, Alexander Kapshuk 
>  a écrit :
>>
>>
>>
>> What is the output of:
>> echo $LD_PRELOAD
>> echo $LD_LIBRARY_PATH
>>
>
> No output.
>
> --
> Jacques
>

So these variables are both unset. But the build log you supplied, had
a record saying the object 'libsandbox.so' could not be preloaded from
LD_PRELOAD.
Is that in your build environment, or in your regular user's
environment, or are they both the same on your system?

What is the output of:
env | grep libsandbox.so

Re: [gentoo-user] Re: bash upgrading problem

[Alexander Kapshuk]

On Mon, Jan 21, 2019 at 1:31 PM Jacques Montier  wrote:
>
>
>
> Le lun. 21 janv. 2019 à 12:11, Alexander Kapshuk 
>  a écrit :
>
>>
>> The /proc/PID directory listed by the ls command is the directory for
>> the process that executed the ls command. See below.
>>
>> % ls -ld /proc/self &
>> [1] 27318
>> % lrwxrwxrwx 1 root root 0 Sep 24 14:06 /proc/self -> 27318
>> [1] +  Done
>>
>> As for the user/group owning the files in /proc/self, they are owned
>> by the user who initiated the process that created those entries in
>> the proc file system.
>>
>
> Thanks Alexander for your explanation.
> Nevertheless, the bash rejected password remains a mystery to me. :-(
>
> Regards,
>
>

What is the output of:
echo $LD_PRELOAD
echo $LD_LIBRARY_PATH

Re: [gentoo-user] Re: bash upgrading problem

[Alexander Kapshuk]

On Mon, Jan 21, 2019 at 12:52 PM Jacques Montier  wrote:
>
>
> Le lun. 21 janv. 2019 à 11:21, Raffaele Belardi  a 
> écrit :
>>
>>
>> Well, they are owned by jacques instead of root. Could it be the reason why 
>> you're asked
>> for a password? Maybe some strange interaction with the sandbox?
>>
>> raffaele
>
>
>
> Yes, i noticed that, but how to explain my root password rejected when 
> emerging bash ?
>
> I also noticed something strange :
> $ ls -al /proc/self/fd
> total 0
> dr-x-- 2 jacques jacques  0 21 janv. 11:49 ./
> dr-xr-xr-x 9 jacques jacques  0 21 janv. 11:49 ../
> lrwx-- 1 jacques jacques 64 21 janv. 11:49 0 -> /dev/pts/1
> lrwx-- 1 jacques jacques 64 21 janv. 11:49 1 -> /dev/pts/1
> lrwx-- 1 jacques jacques 64 21 janv. 11:49 2 -> /dev/pts/1
> lr-x-- 1 jacques jacques 64 21 janv. 11:49 3 -> /proc/4461/fd/
>
> The /proc/4461 directory does not exist !
>
> --
> Jacques
>

The /proc/PID directory listed by the ls command is the directory for
the process that executed the ls command. See below.

% ls -ld /proc/self &
[1] 27318
% lrwxrwxrwx 1 root root 0 Sep 24 14:06 /proc/self -> 27318
[1] +  Done

As for the user/group owning the files in /proc/self, they are owned
by the user who initiated the process that created those entries in
the proc file system.

Re: [gentoo-user] sys-process/audit | gen_flagtabs_h-gen_tables.o] Error 1

[Alexander Kapshuk]

On Wed, Dec 12, 2018 at 4:13 PM Hasan Ç.  wrote:
>
> Hello,
>
> Any idea?
>
>  * Package:sys-process/audit-2.8.3
>  * Repository: gentoo
>  * Maintainer: seli...@gentoo.org robb...@gentoo.org
>  * USE:abi_x86_64 amd64 elibc_glibc kernel_linux python 
> python_targets_python2_7 python_targets_python3_6 userland_GNU
>  * FEATURES:   preserve-libs sandbox userpriv usersandbox
>  * Determining the location of the kernel source code
>  * Found kernel source directory:
>  * /usr/src/linux
>  * Found sources for kernel version:
>  * 4.19.8-gentoo
>  * Checking for suitable kernel configuration options...
>  [ ok ]
>  * Applying audit-2.4.3-python.patch ...
>  [ ok ]
>  * Applying audit-2.1.3-ia64-compile-fix.patch ...
>  [ ok ]
>  * Running eautoreconf in 
> '/var/tmp/portage/sys-process/audit-2.8.3/work/audit-2.8.3' ...
>  * Running libtoolize --install --copy --force --automake ...
>  [ ok ]
>  * Running aclocal ...
>  [ ok ]
>  * Running autoconf --force ...
>  [ ok ]
>  * Running autoheader ...
>  [ ok ]
>  * Running automake --add-missing --copy --force-missing ...
>  [ ok ]
>  * Running elibtoolize in: audit-2.8.3/
>  *   Applying portage/1.2.0 patch ...
>  *   Applying sed/1.5.6 patch ...
>  *   Applying as-needed/2.4.3 patch ...
>  * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
> Configuring auditd
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking target system type... x86_64-pc-linux-gnu
> checking for a BSD-compatible install... 
> /usr/lib/portage/python3.6/ebuild-helpers/xattr/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking how to print strings... printf
> checking for style of include used by make... GNU
> checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
> checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
> checking whether x86_64-pc-linux-gnu-gcc understands -c and -o together... yes
> checking dependency style of x86_64-pc-linux-gnu-gcc... none
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by x86_64-pc-linux-gnu-gcc... 
> /usr/x86_64-pc-linux-gnu/bin/ld
> checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... 
> /usr/bin/x86_64-pc-linux-gnu-nm -B
> checking the name lister (/usr/bin/x86_64-pc-linux-gnu-nm -B) interface... 
> BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 201326592
> checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
> format... func_convert_file_noop
> checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
> func_convert_file_noop
> checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... 
> -r
> checking for x86_64-pc-linux-gnu-objdump... x86_64-pc-linux-gnu-objdump
> checking how to recognize dependent libraries... pass_all
> checking for x86_64-pc-linux-gnu-dlltool... no
> checking for dlltool... no
> checking how to associate runtime and link libraries... printf %s\n
> checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar
> checking for archiver @FILE support... @
> checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip
> checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
> checking command to parse /usr/bin/x86_64-pc-linux-gnu-nm -B output from 
> x86_64-pc-linux-gnu-gcc object... ok
> checking for sysroot... no
> checking for a working dd... /bin/dd
> checking how to truncate binary pipes... /bin/dd bs=4096 count=1
> checking for x86_64-pc-linux-gnu-mt... no
> checking for mt... no
> checking if : is a manifest tool... no
> checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking for objdir... .libs
> checking if x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
> checking 

Re: [gentoo-user] RAM checks for chromium

[Alexander Kapshuk]

On Tue, Dec 4, 2018 at 10:47 AM Mick  wrote:
>
> On Tuesday, 4 December 2018 08:06:22 GMT Alexander Kapshuk wrote:
> > On Tue, Dec 4, 2018 at 9:35 AM Mick  wrote:
> > > Two Intel systems with 4G RAM failed to build chromium, even after setting
> > >
> > > MAKEOPTS="-j2". The ebuild is checking for a minimum of 3G RAM:
> > > >>> Running pre-merge checks for www-client/chromium-70.0.3538.110
> > >
> > >  * Checking for at least 3 GiB RAM ...[ ok
> > >  ]
> > >  * Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/
> > >
> > > chromium-70.0.3538.110/temp" ...  [ ok
> > > ]
> > >
> > > Given I've spent more than two days compiling to get nowhere with this,
> > > I'm
> > > thinking:
> > >
> > > a) Chromium probably needs more than 3G now.
> > > b) Either the ebuild, or portage, ought to check available RAM and
> > > dynamically adjust the number of jobs accordingly - or have I watched too
> > > many AI movies?
> > >
> > > --
> > > Regards,
> > > Mick
> >
> > You're right. Chromium does require more than 3G of RAM to build.
> > Here are the current system requirements for building Chromium on Linux:
> >
> > System requirements
> > A 64-bit Intel machine with at least 8GB of RAM. More than 16GB is
> > highly recommended.
>
> OK it figures, an AMD system with 16G RAM and /var/portage/ on a tmpfs had no
> problem.
>
>
> > At least 100GB of free disk space.
>
> O_O  What the ... ?
>
>
> > You must have Git and Python v2 installed already.
> >
> > See the link below for details.
> > https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux_build_instr
> > uctions.md#system-requirements
>
> Thanks for this.  It may be I'll need to build chromium as a binary on the
> faster PC from now on and copy it over to the older clients, but I can't
> recall what command spews out the detailed CFLAGS for the client which I will
> need to run on the faster host's CLI to emerge the binary.  Grateful for any
> hints.
>
> --
> Regards,
> Mick

Perhaps these two gcc commands are what you're after:
gcc -c -Q -march=native --help=target
gcc -### -march=native /usr/include/stdlib.h

See this link for details, https://wiki.gentoo.org/wiki/GCC_optimization

Re: [gentoo-user] RAM checks for chromium

[Alexander Kapshuk]

On Tue, Dec 4, 2018 at 9:35 AM Mick  wrote:
>
> Two Intel systems with 4G RAM failed to build chromium, even after setting
> MAKEOPTS="-j2". The ebuild is checking for a minimum of 3G RAM:
>
> >>> Running pre-merge checks for www-client/chromium-70.0.3538.110
>  * Checking for at least 3 GiB RAM ...[ ok ]
>  * Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/
> chromium-70.0.3538.110/temp" ...  [ ok ]
>
> Given I've spent more than two days compiling to get nowhere with this, I'm
> thinking:
>
> a) Chromium probably needs more than 3G now.
> b) Either the ebuild, or portage, ought to check available RAM and dynamically
> adjust the number of jobs accordingly - or have I watched too many AI movies?
>
> --
> Regards,
> Mick

You're right. Chromium does require more than 3G of RAM to build.
Here are the current system requirements for building Chromium on Linux:

System requirements
A 64-bit Intel machine with at least 8GB of RAM. More than 16GB is
highly recommended.
At least 100GB of free disk space.
You must have Git and Python v2 installed already.

See the link below for details.
https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux_build_instructions.md#system-requirements

Re: [gentoo-user] Weird compilation error (nasm)

[Alexander Kapshuk]

On Tue, Nov 13, 2018 at 7:57 PM  wrote:
>
> On 11/13 07:52, Alexander Kapshuk wrote:
> > On Tue, Nov 13, 2018 at 7:10 PM  wrote:
> > >
> > > Hi,
> > >
> > > I got a weird looking error while upgrading/recompiling nasm:
> > > cmake -C 
> > > /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64/gentoo_common_config.cmake
> > >  -G Unix Makefiles -DCMAKE_INSTALL_PREFIX=/usr 
> > > -DCMAKE_INSTALL_DEFAULT_DOCDIR=/usr/share/doc/libjpeg-turbo-2.0.1 
> > > -DENABLE_STATIC=no -DWITH_JAVA=no -DWITH_MEM_SRCDST=ON 
> > > -DCMAKE_BUILD_TYPE=Gentoo 
> > > -DCMAKE_TOOLCHAIN_FILE=/var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64/gentoo_toolchain.cmake
> > >   /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1
> > > loading initial cache file 
> > > /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64/gentoo_common_config.cmake
> > > -- The C compiler identification is GNU 8.2.0
> > > -- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc
> > > -- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc -- works
> > > -- Detecting C compiler ABI info
> > > -- Detecting C compiler ABI info - done
> > > -- Detecting C compile features
> > > -- Detecting C compile features - done
> > > -- CMAKE_BUILD_TYPE = Gentoo
> > > -- VERSION = 2.0.1, BUILD = 20181113
> > > -- 64-bit build (x86_64)
> > > -- CMAKE_INSTALL_PREFIX = /usr
> > > -- CMAKE_INSTALL_BINDIR = bin (/usr/bin)
> > > -- CMAKE_INSTALL_DATAROOTDIR = share (/usr/share)
> > > -- CMAKE_INSTALL_DOCDIR = /usr/share/doc/libjpeg-turbo-2.0.1
> > > -- CMAKE_INSTALL_INCLUDEDIR = include (/usr/include)
> > > -- CMAKE_INSTALL_LIBDIR = lib64 (/usr/lib64)
> > > -- CMAKE_INSTALL_MANDIR = /usr/share/man
> > > -- Shared libraries enabled (ENABLE_SHARED = 1)
> > > -- Static libraries disabled (ENABLE_STATIC = 0)
> > > -- 12-bit JPEG support disabled (WITH_12BIT = 0)
> > > -- Arithmetic decoding support enabled (WITH_ARITH_DEC = 1)
> > > -- Arithmetic encoding support enabled (WITH_ARITH_ENC = 1)
> > > -- TurboJPEG API library enabled (WITH_TURBOJPEG = 1)
> > > -- TurboJPEG Java wrapper disabled (WITH_JAVA = 0)
> > > -- In-memory source/destination managers enabled (WITH_MEM_SRCDST = 1)
> > > -- Emulating libjpeg API/ABI v6.2 (WITH_JPEG7 = 0, WITH_JPEG8 = 0)
> > > -- libjpeg API shared library version = 62.3.0
> > > -- Compiler flags = -march=native -O -pipe
> > > -- Linker flags = -Wl,-O1 -Wl,--as-needed
> > > -- Looking for sys/types.h
> > > -- Looking for sys/types.h - found
> > > -- Looking for stdint.h
> > > -- Looking for stdint.h - found
> > > -- Looking for stddef.h
> > > -- Looking for stddef.h - found
> > > -- Check size of size_t
> > > -- Check size of size_t - done
> > > -- Check size of unsigned long
> > > -- Check size of unsigned long - done
> > > -- Performing Test HAVE_BUILTIN_CTZL
> > > -- Performing Test HAVE_BUILTIN_CTZL - Success
> > > -- Looking for include file locale.h
> > > -- Looking for include file locale.h - found
> > > -- Looking for include file stdlib.h
> > > -- Looking for include file stdlib.h - found
> > > -- Looking for include file sys/types.h
> > > -- Looking for include file sys/types.h - found
> > > -- Looking for memset
> > > -- Looking for memset - found
> > > -- Looking for memcpy
> > > -- Looking for memcpy - found
> > > -- Check size of unsigned char
> > > -- Check size of unsigned char - done
> > > -- Check size of unsigned short
> > > -- Check size of unsigned short - done
> > > -- Performing Test INCOMPLETE_TYPES
> > > -- Performing Test INCOMPLETE_TYPES - Success
> > > -- Compiler supports pointers to undefined structures.
> > > -- Performing Test RIGHT_SHIFT_IS_UNSIGNED
> > > -- Performing Test RIGHT_SHIFT_IS_UNSIGNED - Failed
> > > -- Performing Test __CHAR_UNSIGNED__
> > > -- Performing Test __CHAR_UNSIGNED__ - Failed
> > > -- Performing Test INLINE_WORKS
> > > -- Performing Test INLINE_WORKS - Success
> > > -- INLINE = __inline__ __attribute__((always_inline)) (FORCE_INLINE = 1)
> > > -- Performing Test HAVE_VERSION_SCRIPT
> > > -- Performing Test HAVE_VERSION_SCRIPT - Success
> > > -- Linker supports GNU-style version scripts
> > > -- CMA

Re: [gentoo-user] Weird compilation error (nasm)

[Alexander Kapshuk]

On Tue, Nov 13, 2018 at 7:10 PM  wrote:
>
> Hi,
>
> I got a weird looking error while upgrading/recompiling nasm:
> cmake -C 
> /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64/gentoo_common_config.cmake
>  -G Unix Makefiles -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_INSTALL_DEFAULT_DOCDIR=/usr/share/doc/libjpeg-turbo-2.0.1 
> -DENABLE_STATIC=no -DWITH_JAVA=no -DWITH_MEM_SRCDST=ON 
> -DCMAKE_BUILD_TYPE=Gentoo 
> -DCMAKE_TOOLCHAIN_FILE=/var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64/gentoo_toolchain.cmake
>   /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1
> loading initial cache file 
> /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64/gentoo_common_config.cmake
> -- The C compiler identification is GNU 8.2.0
> -- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc
> -- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- CMAKE_BUILD_TYPE = Gentoo
> -- VERSION = 2.0.1, BUILD = 20181113
> -- 64-bit build (x86_64)
> -- CMAKE_INSTALL_PREFIX = /usr
> -- CMAKE_INSTALL_BINDIR = bin (/usr/bin)
> -- CMAKE_INSTALL_DATAROOTDIR = share (/usr/share)
> -- CMAKE_INSTALL_DOCDIR = /usr/share/doc/libjpeg-turbo-2.0.1
> -- CMAKE_INSTALL_INCLUDEDIR = include (/usr/include)
> -- CMAKE_INSTALL_LIBDIR = lib64 (/usr/lib64)
> -- CMAKE_INSTALL_MANDIR = /usr/share/man
> -- Shared libraries enabled (ENABLE_SHARED = 1)
> -- Static libraries disabled (ENABLE_STATIC = 0)
> -- 12-bit JPEG support disabled (WITH_12BIT = 0)
> -- Arithmetic decoding support enabled (WITH_ARITH_DEC = 1)
> -- Arithmetic encoding support enabled (WITH_ARITH_ENC = 1)
> -- TurboJPEG API library enabled (WITH_TURBOJPEG = 1)
> -- TurboJPEG Java wrapper disabled (WITH_JAVA = 0)
> -- In-memory source/destination managers enabled (WITH_MEM_SRCDST = 1)
> -- Emulating libjpeg API/ABI v6.2 (WITH_JPEG7 = 0, WITH_JPEG8 = 0)
> -- libjpeg API shared library version = 62.3.0
> -- Compiler flags = -march=native -O -pipe
> -- Linker flags = -Wl,-O1 -Wl,--as-needed
> -- Looking for sys/types.h
> -- Looking for sys/types.h - found
> -- Looking for stdint.h
> -- Looking for stdint.h - found
> -- Looking for stddef.h
> -- Looking for stddef.h - found
> -- Check size of size_t
> -- Check size of size_t - done
> -- Check size of unsigned long
> -- Check size of unsigned long - done
> -- Performing Test HAVE_BUILTIN_CTZL
> -- Performing Test HAVE_BUILTIN_CTZL - Success
> -- Looking for include file locale.h
> -- Looking for include file locale.h - found
> -- Looking for include file stdlib.h
> -- Looking for include file stdlib.h - found
> -- Looking for include file sys/types.h
> -- Looking for include file sys/types.h - found
> -- Looking for memset
> -- Looking for memset - found
> -- Looking for memcpy
> -- Looking for memcpy - found
> -- Check size of unsigned char
> -- Check size of unsigned char - done
> -- Check size of unsigned short
> -- Check size of unsigned short - done
> -- Performing Test INCOMPLETE_TYPES
> -- Performing Test INCOMPLETE_TYPES - Success
> -- Compiler supports pointers to undefined structures.
> -- Performing Test RIGHT_SHIFT_IS_UNSIGNED
> -- Performing Test RIGHT_SHIFT_IS_UNSIGNED - Failed
> -- Performing Test __CHAR_UNSIGNED__
> -- Performing Test __CHAR_UNSIGNED__ - Failed
> -- Performing Test INLINE_WORKS
> -- Performing Test INLINE_WORKS - Success
> -- INLINE = __inline__ __attribute__((always_inline)) (FORCE_INLINE = 1)
> -- Performing Test HAVE_VERSION_SCRIPT
> -- Performing Test HAVE_VERSION_SCRIPT - Success
> -- Linker supports GNU-style version scripts
> -- CMAKE_EXECUTABLE_SUFFIX =
>  * ACCESS DENIED:  fopen_wr: /?
> -- The ASM_NASM compiler identification is NASM
> -- Found assembler: /usr/bin/nasm
> -- CMAKE_ASM_NASM_COMPILER = /usr/bin/nasm
> -- CMAKE_ASM_NASM_OBJECT_FORMAT = elf64
> -- CMAKE_ASM_NASM_FLAGS =  -DELF -D__x86_64__ -DPIC
> -- SIMD extensions: x86_64 (WITH_SIMD = 1)
> -- FLOATTEST = sse
> -- RPM architecture = x86_64, DEB architecture = amd64
> -- <<< Gentoo configuration >>>
> Build type  Gentoo
> Install path/usr
> Compiler flags:
> C   -march=native -O -pipe
> C++
> Linker flags:
> Executable  -Wl,-O1 -Wl,--as-needed
> Module  -Wl,-O1 -Wl,--as-needed
> Shared  -Wl,-O1 -Wl,--as-needed
>
> -- Configuring done
> -- Generating done
> -- Build files have been written to: 
> /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-abi_x86_64.amd64
> >>> Source configured.
>  * --- ACCESS VIOLATION SUMMARY 
> ---
>  * LOG FILE: "/var/log/sandbox/sandbox-16492.log"
>  *
> VERSION 1.0
> FORMAT: F - Function called
> FORMAT: S - Access Status
> FORMAT: P - Path as passed to function
> FORMAT: A - 

Re: [gentoo-user] libQt5Core.so.5 => not found

[Alexander Kapshuk]

On Fri, Nov 9, 2018 at 1:33 PM  wrote:
>
> I'm trying to build/emerge dev-qt/qtgui-5.11.1, but I get this:
>
> # ldd 
> /Net/portage_tmpdir/portage/dev-qt/qtgui-5.11.1/work/qtbase-everywhere-src-5.11.1/bin/qvkgen
> linux-vdso.so.1 (0x7fff3ddff000)
> libQt5Core.so.5 => not found
> libc.so.6 => /lib64/libc.so.6 (0x7f697dbd8000)
> /lib64/ld-linux-x86-64.so.2 (0x7f697e1f5000)
> # strings /etc/ld.so.cache | grep libQt5Core.so.5
> libQt5Core.so.5
> /usr/lib64/libQt5Core.so.5
> # ls -l /usr/lib64/libQt5Core.so.5*
> lrwxrwxrwx 1 root root  20 Nov  5 12:49 /usr/lib64/libQt5Core.so.5 -> 
> libQt5Core.so.5.11.1
> lrwxrwxrwx 1 root root  20 Nov  5 12:49 /usr/lib64/libQt5Core.so.5.11 -> 
> libQt5Core.so.5.11.1
> -rwxr-xr-x 1 root root 5351376 Nov  5 12:49 /usr/lib64/libQt5Core.so.5.11.1
>
> So why isn't it found ?
>
> Regards,
> /Karl Hammar
>
> ---
> Aspö Data
> Lilla Aspö 148
> S-742 94 Östhammar
> Sweden
>
>
>

Seeing the actual build error message, rather then the output of ldd,
may contain information about the build environment, and other
information that might offer better clues as to what else might be
amiss.
Also, the output of 'strace /bin/qvkgen' will indicate what paths are
searched for libQt5Core.so.5.

Re: [gentoo-user] Compilation problem iptables

[Alexander Kapshuk]

On Wed, Oct 24, 2018 at 7:07 PM  wrote:
>
> Hi,
>
> while syncing/updateing, this happens (net-firewall/iptables-1.8.1) :
> ototypes -Wredundant-decls -Wshadow -Wstrict-prototypes -Wlogical-op  
>   -Winline -pipe -D_INIT=libxt_multiport_init -DPIC -fPIC -march=native -O 
> -pipe -o libxt_multiport.oo -c libxt_multiport.c;
> x86_64-pc-linux-gnu-gcc -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES 
> -D_FILE_OFFSET_BITS=64 -D_REENTRANT
> -DXTABLES_LIBDIR=\"/usr/lib64/xtables\" -DXTABLES_INTERNAL -I../include -I.. 
> -I../include -I.. -Wp,-MMD,./.libxt_nfacct.oo.d,-MT,libxt_nfacct.oo -Wall 
> -Waggregate-return -Wmissing-declarations-Wmissing-prototypes 
> -Wredundant-decls -Wshadow -Wstrict-prototypes -Wlogical-op-Winline 
> -pipe -D_INIT=libxt_nfacct_init -DPIC -fPIC -march=native -O -pipe -o 
> libxt_nfacct.oo -c libxt_nfacct.c;
> x86_64-pc-linux-gnu-gcc -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES 
> -D_FILE_OFFSET_BITS=64 -D_REENTRANT
> -DXTABLES_LIBDIR=\"/usr/lib64/xtables\" -DXTABLES_INTERNAL -I../include -I.. 
> -I../include -I.. -Wp,-MMD,./.libxt_osf.oo.d,-MT,libxt_osf.oo -Wall 
> -Waggregate-return -Wmissing-declarations  -Wmissing-prototypes 
> -Wredundant-decls -Wshadow -Wstrict-prototypes -Wlogical-op-Winline 
> -pipe -D_INIT=libxt_osf_init -DPIC -fPIC -march=native -O -pipe -o 
> libxt_osf.oo -c libxt_osf.c;
> In file included from ../iptables/nft.h:5,
>  from libxt_limit.c:18:
> ../iptables/nft-shared.h:6:10: fatal error: libnftnl/rule.h: No such file or 
> directory
>  #include 
>   ^
> compilation terminated.
> x86_64-pc-linux-gnu-gcc -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES 
> -D_FILE_OFFSET_BITS=64 -D_REENTRANT
> -DXTABLES_LIBDIR=\"/usr/lib64/xtables\" -DXTABLES_INTERNAL -I../include -I.. 
> -I../include -I.. -Wp,-MMD,./.libxt_owner.oo.d,-MT,libxt_owner.oo -Wall 
> -Waggregate-return -Wmissing-declarations  -Wmissing-prototypes 
> -Wredundant-decls -Wshadow -Wstrict-prototypes -Wlogical-op-Winline 
> -pipe -D_INIT=libxt_owner_i
>
> I wanted I sent the whole bunch of logs...
>
> Cheers!
> Meino
>
>
>
>

The header file reported as missing belongs to the net-libs/libnftnl package.
Do you have it installed?

Re: [gentoo-user] problem updating KDE breeze

[Alexander Kapshuk]

On Mon, Oct 22, 2018 at 7:15 AM Philip Webb  wrote:
>
> 181021 Franz Fellner wrote:
> > the actual error really is missing.
> > Can you use pastebin or something similar to upload the whole build.log?
> > The number of cores may help to estimate the unmber of compilation units
> > that still get built.  Unfortunately not with cmake.  It usually continues
> > building targets that do not depend on the failed target.
> > You may have to scroll up hundreds of lines.
> > So, again: Please give us the complete build.log !
>
> I hadn't run into this kind of error before
> & assumed there cb only  1  error for each Emerge.
> Here is where 'Error 1' occurs :
>
> [ 37%] Building CXX object 
> kdecoration/CMakeFiles/breezedecoration.dir/breezesettings.cpp.o
> cd 
> /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kdecoration
>  && /usr/bin/x86_64-pc-linux-gnu-g++ -DKCOREADDONS_LIB -DKGUIADDONS_LIB 
> -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -\
> DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB 
> -DTRANSLATION_DOMAIN=\"breeze_kwin_deco\" -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
> -Dbreezedecoration_EXPORTS -I/var/tmp/portage/portage/kde-plasm\
> a/breeze-5.13.5/work/breeze-5.13.5_build/kdecoration 
> -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kdecoration
>  -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.1\
> 3.5_build/kdecoration/breezedecoration_autogen/include -isystem 
> /usr/include/qt5 -isystem /usr/include/qt5/QtCore -isystem 
> /usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtGui -isystem 
> /usr/i\
> nclude/qt5/QtDBus -isystem /usr/include/KDecoration2 -isystem 
> /usr/include/KF5 -isystem /usr/include/KF5/KConfigCore -isystem 
> /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KConfigWidgets -isyste\
> m /usr/include/KF5/KCodecs -isystem /usr/include/KF5/KWidgetsAddons -isystem 
> /usr/include/qt5/QtWidgets -isystem /usr/include/KF5/KConfigGui -isystem 
> /usr/include/qt5/QtXml -isystem /usr/include/KF5/KAut\
> h -isystem /usr/include/KF5/KGuiAddons -isystem /usr/include/KF5/KI18n 
> -isystem /usr/include/KF5/KWindowSystem -isystem /usr/include/qt5/QtX11Extras 
>   -DQT_NO_DEBUG -DNDEBUG -march=native -O2 -pipe -std=\
> c++0x -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align 
> -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef 
> -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type\
>  -Wvla -Wdate-time -fPIC -fvisibility=hidden -fvisibility-inlines-hidden   
> -fPIC -std=gnu++11 -o CMakeFiles/breezedecoration.dir/breezesettings.cpp.o -c 
> /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/\
> work/breeze-5.13.5_build/kdecoration/breezesettings.cpp
> /usr/lib64/libKF5Declarative.so.5: undefined reference to 
> `QQmlPropertyMap::init(QMetaObject const*)@Qt_5'
> /usr/lib64/libKF5Declarative.so.5: undefined reference to 
> `QQmlPropertyMap::allocatePrivate()@Qt_5'
> collect2: error: ld returned 1 exit status
> make[2]: *** [kstyle/config/CMakeFiles/breeze-settings5.dir/build.make:121: 
> kstyle/config/breeze-settings5] Error 1
> make[2]: Leaving directory 
> '/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build'
> make[1]: *** [CMakeFiles/Makefile2:550: 
> kstyle/config/CMakeFiles/breeze-settings5.dir/all] Error 2
> make[1]: *** Waiting for unfinished jobs
> Generating MOC source 4NBMFDNHZT/moc_breezetransitionwidget.cpp
> /usr/lib64/qt5/bin/moc 
> -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kstyle
>  
> -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kstyle/breeze_autog\
> en/include 
> -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kstyle 
> -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kstyle/animations
>  -I/var/tmp/portage/portag\
> e/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kstyle/debug -I/usr/include/qt5 
> -I/usr/include/qt5/QtCore -I/usr/lib64/qt5/mkspecs/linux-g++ 
> -I/usr/include/qt5/QtGui -I/usr/include/qt5/QtWidgets -I/usr/inc\
> lude/qt5/QtDBus -I/usr/include/qt5/QtQuick -I/usr/include/qt5/QtQml 
> -I/usr/include/qt5/QtNetwork -I/usr/include/KF5/KConfigCore 
> -I/usr/include/KF5 -I/usr/include/KF5/KConfigWidgets -I/usr/include/KF5/KCo\
> decs -I/usr/include/KF5/KWidgetsAddons -I/usr/include/KF5/KConfigGui 
> -I/usr/include/qt5/QtXml -I/usr/include/KF5/KAuth 
> -I/usr/include/KF5/KCoreAddons -I/usr/include/KF5/KGuiAddons 
> -I/usr/include/KF5/KWin\
> dowSystem -I/usr/include/KF5/KStyle -I/usr/include/qt5/QtX11Extras 
> -I/usr/include -I/usr/include -DKCOREADDONS_LIB -DKGUIADDONS_LIB 
> -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG\
>  -DQT_QML_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB 
> -D_GNU_SOURCE -D_LARGEFILE64_SOURCE --include 
> /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/ksty\
> le/breeze_autogen/moc_predefs.h -o 
> 

Re: [gentoo-user] Nvidia proprietary driver broken

[Alexander Kapshuk]

On Wed, Oct 10, 2018 at 11:06 PM Christoph Böhmwalder
 wrote:
>
> Hi,
>
> Since the last kernel update (?), my Nvidia driver refuses to load:
>
> [   74.675437] udevd[3315]: worker [3376] /module/nvidia is taking a long time
> [   74.675445] udevd[3315]: worker [3377] 
> /devices/pci:00/:00:03.0/:03:00.0 is taking a long time
> [  193.411394] udevd[3376]: timeout 'nvidia-udev.sh add'
> [  193.411409] udevd[3376]: slow: 'nvidia-udev.sh add' [3544]
> [  194.412484] udevd[3376]: timeout: killing 'nvidia-udev.sh add' [3544]
> [  194.412504] udevd[3376]: slow: 'nvidia-udev.sh add' [3544]
> [  194.412668] udevd[3376]: 'nvidia-udev.sh add' [3544] terminated by signal 
> 9 (Killed)
> [  197.415861] udevd[3315]: worker [3377] 
> /devices/pci:00/:00:03.0/:03:00.0 timeout; kill it
> [  197.415875] udevd[3315]: seq 2089 
> '/devices/pci:00/:00:03.0/:03:00.0' killed
> [  616.150724] udevd[3315]: specified group 'render' unknown
>
> I haven't done a kernel update in a while, and I'm pretty sure I was
> running 4.17.3 before. After updating to 4.18.11 things started to
> break.
>
> I've also tried a more recent kernel (4.18.13) and a much older LTS
> kernel (4.14.75), of course recompiling the module every time.
>
> I'm using the default genkernel config minus Nouveau, so this is my
> procedure:
>
> # genkernel --menuconfig all
> (disable nouveau)
> # grub-mkconfig -o /boot/grub/grub.cfg
> # emerge -av @module-rebuild
> # reboot
>
> Any ideas on what could be wrong?
>
> Thanks!
>
> --
> Christoph
>

Here's a link to a Gentoo Bugzilla report for the issue in question:
https://bugs.gentoo.org/667362

With a workaround suggested.

Re: [gentoo-user] profile-sync-daemon "bad substitution" at boot

[Alexander Kapshuk]

On Thu, Sep 6, 2018 at 11:18 AM Alexander Kapshuk
 wrote:
>
> On Thu, Sep 6, 2018 at 10:48 AM Samuraiii  wrote:
> >
> > On 5.9.2018 21:20, Mick wrote:
> >
> > Hi All,
> >
> > I just noticed a psd error at boot time:
> >
> > /usr/bin/profile-sync-daemon: line 325: ${#DIRArr[@]##*/}: bad substitution
> >
> > Any idea what's brought this about?
> >
> > Hi,
> >
> > my bet is that your /bin/sh != /bin/bash and /usr/bin/profile-sync-daemon 
> > starts with #!/bin/sh.
> >
> > The other way around /usr/bin/profile-sync-daemon contains bashishms.
> >
> > You can try (as a test) to change #!/bin/sh for #!/bin/bash...
> >
> > S
>
> The shebang in the master repository is '#!/bin/bash'.
> https://raw.githubusercontent.com/graysky2/profile-sync-daemon/master/common/profile-sync-daemon.in
>
> The error message is a shell parameter expansion syntax error, which
> comprises two different expansion constructs referenced below.
> ${#parameter}
> String Length.
>
> ${parameter##[word]}
> Remove Largest Prefix Pattern.
>
> See section 2.6.2 Parameter Expansion,
> http://pubs.opengroup.org/onlinepubs/9699919799/nframe.html.
>
> The script in the master repository referenced above does not contain
> the line in question. It has '${#DIRArr[@]/}' and '${DIRArr[@]##*/}'.

This appears to have been reported as a bug in Debian [1]
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839049
And applied upstream [2].
https://github.com/graysky2/profile-sync-daemon/pull/185/files/654f5359abfe7aab2e1616dd74c8ba0f76ce4ab4

Re: [gentoo-user] profile-sync-daemon "bad substitution" at boot

[Alexander Kapshuk]

On Thu, Sep 6, 2018 at 10:48 AM Samuraiii  wrote:
>
> On 5.9.2018 21:20, Mick wrote:
>
> Hi All,
>
> I just noticed a psd error at boot time:
>
> /usr/bin/profile-sync-daemon: line 325: ${#DIRArr[@]##*/}: bad substitution
>
> Any idea what's brought this about?
>
> Hi,
>
> my bet is that your /bin/sh != /bin/bash and /usr/bin/profile-sync-daemon 
> starts with #!/bin/sh.
>
> The other way around /usr/bin/profile-sync-daemon contains bashishms.
>
> You can try (as a test) to change #!/bin/sh for #!/bin/bash...
>
> S

The shebang in the master repository is '#!/bin/bash'.
https://raw.githubusercontent.com/graysky2/profile-sync-daemon/master/common/profile-sync-daemon.in

The error message is a shell parameter expansion syntax error, which
comprises two different expansion constructs referenced below.
${#parameter}
String Length.

${parameter##[word]}
Remove Largest Prefix Pattern.

See section 2.6.2 Parameter Expansion,
http://pubs.opengroup.org/onlinepubs/9699919799/nframe.html.

The script in the master repository referenced above does not contain
the line in question. It has '${#DIRArr[@]/}' and '${DIRArr[@]##*/}'.

Re: [gentoo-user] x86.c:(.text+0xb2): undefined reference to `l1tf_vmx_mitigation' with linux kernel 4.18.1

[Alexander Kapshuk]

On Fri, Aug 17, 2018 at 8:58 AM Alexander Kapshuk
 wrote:
>
> On Fri, Aug 17, 2018 at 8:57 AM Alexander Kapshuk
>  wrote:
> >
> > On Fri, Aug 17, 2018 at 8:10 AM  wrote:
> > >
> > > On 08/17 02:53, Adam Carter wrote:
> > > > On Fri, Aug 17, 2018 at 1:15 PM,  wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > CPU bugs seem to be more and more common:
> > > > > https://www.heise.de/security/meldung/Linux-Kernel-und-
> > > > > Distributionen-schuetzen-vor-Prozessorluecke-Foreshadow-L1TF-4137264.html
> > > > > https://www.heise.de/security/meldung/Spectre-NG-Foreshadow-
> > > > > gefaehrdet-Intel-Prozessoren-4137209.html
> > > > > (sorry, I only know of this german spoken references...)
> > > > >
> > > > > With Linux kernel 4.18.1 Linus has introduced a fix (aka workaround)
> > > > > of the  Foreshadow bug.
> > > > >
> > > >
> > > >  4.18, 4.17, 4.14, 4.9, and 4.4 have all had the fixes applied.
> > > >
> > > > >
> > > > > Unfortunately compiling that kernel (as downloaded from
> > > > > https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/ )
> > > > >
> > > > > gives me this bug:
> > > > >
> > > >
> > > > gentoo-sources with gcc 7.3 builds fine for me.
> > > >
> > > > Intel: grep . /sys/devices/system/cpu/vulnerabilities/*
> > > > /sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion
> > > > /sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
> > > > /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
> > > > Speculative Store Bypass disabled via prctl and seccomp
> > > > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > > > pointer sanitization
> > > > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full 
> > > > generic
> > > > retpoline, IBPB, IBRS_FW
> > > >
> > > > AMD: grep . /sys/devices/system/cpu/vulnerabilities/*
> > > > /sys/devices/system/cpu/vulnerabilities/l1tf:Not affected
> > > > /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected
> > > > /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
> > > > Speculative Store Bypass disabled via prctl and seccomp
> > > > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > > > pointer sanitization
> > > > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full AMD
> > > > retpoline, IBPB
> > >
> > > Hi,
> > >
> > > I am happy, that other sources do work for you Adam.
> > >
> > > Interesting would be, why the original sources does not compile for
> > > me.
> > > Any idea?
> > >
> > >
> > >
> >
> > This problem has been reported upstream. See below.
> > https://lkml.org/lkml/2018/8/15/118
> >
> > In particular:
> >
> > Build is successful with
> > CONFIG_KVM=y
> > CONFIG_KVM_INTEL=y
> > CONFIG_KVM_AMD=y
> > but fails if only
> > CONFIG_KVM=y
> > CONFIG_KVM_AMD=y
> > are selected.
>
> And a follow up email with a reference to a patch that addresses the issue:
> https://lkml.org/lkml/2018/8/15/122

The patch in question will become available in 4.18.2 upstream. See
the link below.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-4.18.y=eca268a3133cafcd188d85489f08a7c5907d985d

Re: [gentoo-user] x86.c:(.text+0xb2): undefined reference to `l1tf_vmx_mitigation' with linux kernel 4.18.1

[Alexander Kapshuk]

On Fri, Aug 17, 2018 at 8:57 AM Alexander Kapshuk
 wrote:
>
> On Fri, Aug 17, 2018 at 8:10 AM  wrote:
> >
> > On 08/17 02:53, Adam Carter wrote:
> > > On Fri, Aug 17, 2018 at 1:15 PM,  wrote:
> > >
> > > > Hi,
> > > >
> > > > CPU bugs seem to be more and more common:
> > > > https://www.heise.de/security/meldung/Linux-Kernel-und-
> > > > Distributionen-schuetzen-vor-Prozessorluecke-Foreshadow-L1TF-4137264.html
> > > > https://www.heise.de/security/meldung/Spectre-NG-Foreshadow-
> > > > gefaehrdet-Intel-Prozessoren-4137209.html
> > > > (sorry, I only know of this german spoken references...)
> > > >
> > > > With Linux kernel 4.18.1 Linus has introduced a fix (aka workaround)
> > > > of the  Foreshadow bug.
> > > >
> > >
> > >  4.18, 4.17, 4.14, 4.9, and 4.4 have all had the fixes applied.
> > >
> > > >
> > > > Unfortunately compiling that kernel (as downloaded from
> > > > https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/ )
> > > >
> > > > gives me this bug:
> > > >
> > >
> > > gentoo-sources with gcc 7.3 builds fine for me.
> > >
> > > Intel: grep . /sys/devices/system/cpu/vulnerabilities/*
> > > /sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion
> > > /sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
> > > /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
> > > Speculative Store Bypass disabled via prctl and seccomp
> > > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > > pointer sanitization
> > > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full 
> > > generic
> > > retpoline, IBPB, IBRS_FW
> > >
> > > AMD: grep . /sys/devices/system/cpu/vulnerabilities/*
> > > /sys/devices/system/cpu/vulnerabilities/l1tf:Not affected
> > > /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected
> > > /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
> > > Speculative Store Bypass disabled via prctl and seccomp
> > > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > > pointer sanitization
> > > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full AMD
> > > retpoline, IBPB
> >
> > Hi,
> >
> > I am happy, that other sources do work for you Adam.
> >
> > Interesting would be, why the original sources does not compile for
> > me.
> > Any idea?
> >
> >
> >
>
> This problem has been reported upstream. See below.
> https://lkml.org/lkml/2018/8/15/118
>
> In particular:
>
> Build is successful with
> CONFIG_KVM=y
> CONFIG_KVM_INTEL=y
> CONFIG_KVM_AMD=y
> but fails if only
> CONFIG_KVM=y
> CONFIG_KVM_AMD=y
> are selected.

And a follow up email with a reference to a patch that addresses the issue:
https://lkml.org/lkml/2018/8/15/122

Re: [gentoo-user] x86.c:(.text+0xb2): undefined reference to `l1tf_vmx_mitigation' with linux kernel 4.18.1

[Alexander Kapshuk]

On Fri, Aug 17, 2018 at 8:10 AM  wrote:
>
> On 08/17 02:53, Adam Carter wrote:
> > On Fri, Aug 17, 2018 at 1:15 PM,  wrote:
> >
> > > Hi,
> > >
> > > CPU bugs seem to be more and more common:
> > > https://www.heise.de/security/meldung/Linux-Kernel-und-
> > > Distributionen-schuetzen-vor-Prozessorluecke-Foreshadow-L1TF-4137264.html
> > > https://www.heise.de/security/meldung/Spectre-NG-Foreshadow-
> > > gefaehrdet-Intel-Prozessoren-4137209.html
> > > (sorry, I only know of this german spoken references...)
> > >
> > > With Linux kernel 4.18.1 Linus has introduced a fix (aka workaround)
> > > of the  Foreshadow bug.
> > >
> >
> >  4.18, 4.17, 4.14, 4.9, and 4.4 have all had the fixes applied.
> >
> > >
> > > Unfortunately compiling that kernel (as downloaded from
> > > https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/ )
> > >
> > > gives me this bug:
> > >
> >
> > gentoo-sources with gcc 7.3 builds fine for me.
> >
> > Intel: grep . /sys/devices/system/cpu/vulnerabilities/*
> > /sys/devices/system/cpu/vulnerabilities/l1tf:Mitigation: PTE Inversion
> > /sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
> > /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
> > Speculative Store Bypass disabled via prctl and seccomp
> > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > pointer sanitization
> > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic
> > retpoline, IBPB, IBRS_FW
> >
> > AMD: grep . /sys/devices/system/cpu/vulnerabilities/*
> > /sys/devices/system/cpu/vulnerabilities/l1tf:Not affected
> > /sys/devices/system/cpu/vulnerabilities/meltdown:Not affected
> > /sys/devices/system/cpu/vulnerabilities/spec_store_bypass:Mitigation:
> > Speculative Store Bypass disabled via prctl and seccomp
> > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > pointer sanitization
> > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full AMD
> > retpoline, IBPB
>
> Hi,
>
> I am happy, that other sources do work for you Adam.
>
> Interesting would be, why the original sources does not compile for
> me.
> Any idea?
>
>
>

This problem has been reported upstream. See below.
https://lkml.org/lkml/2018/8/15/118

In particular:

Build is successful with
CONFIG_KVM=y
CONFIG_KVM_INTEL=y
CONFIG_KVM_AMD=y
but fails if only
CONFIG_KVM=y
CONFIG_KVM_AMD=y
are selected.

Re: [gentoo-user] vlc failed to compile

[Alexander Kapshuk]

On Tue, Jul 10, 2018 at 3:00 PM gevisz  wrote:
>
> 2018-07-10 12:58 GMT+03:00 Alexander Kapshuk :
> > On Tue, Jul 10, 2018 at 12:42 PM gevisz  wrote:
> >>
> >> In today's update vlc failed to compile.
> >>
> >> What shall I do?
> >>
> >
> > Rebuild libebml:
> > emerge -1 libebml
> >
> > See 
> > https://forums.gentoo.org/viewtopic-p-8184582.html?sid=f451f5dcad08d0eba731189fa8480c77
>
> It has helped. Thank you.
>

Good to hear. Thanks for letting us know.

Re: [gentoo-user] vlc failed to compile

[Alexander Kapshuk]

On Tue, Jul 10, 2018 at 12:42 PM gevisz  wrote:
>
> In today's update vlc failed to compile:
>
> make[4]: Leaving directory
> '/var/tmp/portage/media-video/vlc-3.0.3-r1/work/vlc-3.0.3/modules'
> make[3]: *** [Makefile:26145: all-recursive] Error 1
> make[3]: Leaving directory
> '/var/tmp/portage/media-video/vlc-3.0.3-r1/work/vlc-3.0.3/modules'
> make[2]: *** [Makefile:11238: all] Error 2
> make[2]: Leaving directory
> '/var/tmp/portage/media-video/vlc-3.0.3-r1/work/vlc-3.0.3/modules'
> make[1]: *** [Makefile:1530: all-recursive] Error 1
> make[1]: Leaving directory
> '/var/tmp/portage/media-video/vlc-3.0.3-r1/work/vlc-3.0.3'
> make: *** [Makefile:1415: all] Error 2
>  * ERROR: media-video/vlc-3.0.3-r1::gentoo failed (compile phase):
>  *   emake failed
>  *
>  * If you need support, post the output of `emerge --info
> '=media-video/vlc-3.0.3-r1::gentoo'`,
>  * the complete build log and the output of `emerge -pqv
> '=media-video/vlc-3.0.3-r1::gentoo'`.
>  * The complete build log is located at
> '/var/log/portage/media-video:vlc-3.0.3-r1:20180710-081824.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/media-video/vlc-3.0.3-r1/temp/environment'.
>  * Working directory: 
> '/var/tmp/portage/media-video/vlc-3.0.3-r1/work/vlc-3.0.3'
>  * S: '/var/tmp/portage/media-video/vlc-3.0.3-r1/work/vlc-3.0.3'
>
> >>> Failed to emerge media-video/vlc-3.0.3-r1, Log file:
>
> >>>  '/var/log/portage/media-video:vlc-3.0.3-r1:20180710-081824.log'
>
> What shall I do?
>

Rebuild libebml:
emerge -1 libebml

See 
https://forums.gentoo.org/viewtopic-p-8184582.html?sid=f451f5dcad08d0eba731189fa8480c77

Re: [gentoo-user] how to set python version for one user

[Alexander Kapshuk]

On Tue, Jul 10, 2018 at 11:23 AM  wrote:
>
> Hi,
>
> I need to set specific python version to a user and I don't want to set
> it up for whole system. Is it possible? If so how to do it. All I found
> is about setting for whole system.
>
> Thanks
>
> Pat
>
> 
> Freehosting PIPNI - http://www.pipni.cz/
>
>
How about this?
echo alias python='python2.7' >> ~user/.bash_profile

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Thu, Jun 14, 2018 at 7:56 PM Ian Zimmerman  wrote:
>
> On 2018-06-13 20:29, Alexander Kapshuk wrote:
>
> > 4.9.108 is out with some objtool fixes among other things. See the
> > change log for details.
> > https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.108
> >
> > Want to give this kernel a try and seen if it fixes the issues you were 
> > having?
>
> 4.9.108 didn't solve the problem.  But I installed 4.14.49 and it behaves.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

Good to hear. Thanks for letting us know.

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Tue, Jun 12, 2018 at 5:54 PM Ian Zimmerman  wrote:
>
> On 2018-06-12 09:56, Alexander Kapshuk wrote:
>
> > Any reason you're trying to load those modules by hand rather then
> > have them loaded for you automatically?
>
> The only one I try to "load by hand" (rather: via conf.d/modules) is
> fbcon, because IME that is how I actually get a framebuffer console.  Is
> there a better way?
>
> But there were other modules, including network drivers, that produced
> the same error, despite getting autoloaded.  Not all modules, though.
>
> > Did dmesg have any more info on the failing modules?
>
> I will report on this when I can play the reboot game again, which may
> be a few days yet.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

4.9.108 is out with some objtool fixes among other things. See the
change log for details.
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.108

Want to give this kernel a try and seen if it fixes the issues you were having?

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Tue, Jun 12, 2018 at 8:54 AM Ian Zimmerman  wrote:
>
> On 2018-06-12 08:23, Alexander Kapshuk wrote:
>
> > Looks like I'd have to build kernel 4.9.107 in an environment
> > resembling yours to try and reproduce the behavior in question.
> > What is the version of kmods you have installed on your system?
> > What's the output of 'emerge --info'?
>
> https://gist.github.com/nobrowser/314da0f994ce134e3d554cc4cfed266e
>
> BTW, why are you so interested in this?  It seems to me to be purely a
> kernel/kernel tools problem.  What is the gentoo angle?
>
> Of course I'm not complaining that you're trying to help - thanks a lot.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

I do programming for a living with an interest in kernel programming.
I'm not a Gentoo developer and I'm not doing this on behalf of the
Gentoo Foundation.
I was just l curious to find out what could have caused the issue
you're having and if possible to try and come up with a fix.

I can't promise I will be able to fix this for you. Chances are, the
next kmods and/or kernel upgrade will  have fixed this for you.

Any reason you're trying to load those modules by hand rather then
have them loaded for you automatically?
Did dmesg have any more info on the failing modules?

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Mon, Jun 11, 2018 at 6:09 PM Ian Zimmerman  wrote:
>
> On 2018-06-09 18:51, Alexander Kapshuk wrote:
>
> > readelf -h /path/to/module.ko
>
> ELF Header:
>   Magic:   7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
>   Class: ELF64
>   Data:  2's complement, little endian
>   Version:   1 (current)
>   OS/ABI:UNIX - System V
>   ABI Version:   0
>   Type:  REL (Relocatable file)
>   Machine:   Advanced Micro Devices X86-64
>   Version:   0x1
>   Entry point address:   0x0
>   Start of program headers:  0 (bytes into file)
>   Start of section headers:  52808 (bytes into file)
>   Flags: 0x0
>   Size of this header:   64 (bytes)
>   Size of program headers:   0 (bytes)
>   Number of program headers: 0
>   Size of section headers:   64 (bytes)
>   Number of section headers: 23
>   Section header string table index: 22
>
> This was less frustrating than the other times as I didn't have to
> reboot back and forth, so you need not feel guilty about it.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

Hmm...

Looks like I'd have to build kernel 4.9.107 in an environment
resembling yours to try and reproduce the behavior in question.
What is the version of kmods you have installed on your system?
What's the output of 'emerge --info'?

In the meantime, see this email exchange [1] that  might be relevant
to the problem you're having.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857354#10

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Sat, Jun 9, 2018 at 5:26 PM Ian Zimmerman  wrote:
>
> On 2018-06-09 14:15, Alexander Kapshuk wrote:
>
> > I had a look at the source code for kmod-25. If I read it right, dmesg
> > should have records along the lines of:
> > kmod-25/libkmod/libkmod-module.c:886:   INFO(mod->ctx, "Failed
> > to insert module '%s': %m\n", path);
> >
> > modprobe returns Exec format error.
>
> > Now, if my understanding of the source code above is right, you either
> > have CONFIG_X86_32 set in your kernel, e.i. your Elf_Ehdr is set to
> > Elf32_Ehdr, or the module's header is for the architecture that is
> > different from what is expected by the kernel.
>
> The former is definitely false.  If the latter holds, it is not due to
> any action on my part, but due to how the module is built by the kernel
> build system (at the same time as the kernel proper).  Again, I strongly
> suspect this is due to all the "objtool" churn in 4.9.106 and later.
>
> I'm afraid I'm at the limit of my patience diving into this for now.
> You see, I have to remove the broken kernel from grub manually every
> time (and then re-add it for another test), otherwise it breaks
> unattended boots.
>
> Sorry about that.  Maybe in a few days I'll have time to sit down and
> track it properly.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

I appreciate that this has been a frustrating experience for you, but
when you get a change, could you please run 'readelf -h' on the module
concerned and show the output below:
readelf -h /path/to/module.ko
ELF Header:
Magic:
Class:
Machine:
Size of this header:

This will either confirm or refute my assumption about the ELF header
being the wrong size and causing the 'Exec format error' message to be
printed.

Thanks.

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Sat, Jun 9, 2018 at 8:56 AM Alexander Kapshuk
 wrote:
>
>
>
> On Sat, Jun 9, 2018, 07:34 Ian Zimmerman  wrote:
>>
>> On 2018-06-08 22:38, Alexander Kapshuk wrote:
>>
>> > On Fri, Jun 8, 2018, 22:30 Ian Zimmerman  wrote:
>> >
>> > > On 2018-06-08 22:00, Alexander Kapshuk wrote:
>> > >
>> > > > What's the output of:
>> > > > uname -r
>> > > > strings /path/to/your/module.ko | grep vermagic=
>> > >
>> > > Here are the results for 4.9.105 (working):
>> > >
>> > >  matica!6 ~$ uname -r
>> > > 4.9.105
>> > >  matica!7 ~$ strings
>> > >  /lib64/modules/4.9.105/kernel/drivers/video/console/fbcon.ko |
>> > >  fgrep -e 'vermagic='
>> > > vermagic=4.9.105 SMP
>> > >
>> > > Let me know if you need to see the ones for the broken kernel ...
>> > >
>> >
>> > Yes, we want to make sure the vermagic of the modules you're trying to load
>> > matches the output of uname -r of the running kernel.
>>
>> Ok, here:
>>
>> Script started on 2018-06-08 21:11:04-0700
>>  matica!501 ~# ls -l 
>> /lib64/modules/4.9.107/kernel/drivers/video/console/fbcon.ko
>> -rw-r--r-- 1 root root 54280 Jun  8 20:57 
>> /lib64/modules/4.9.107/kernel/drivers/video/console/fbcon.ko
>>  matica!502 ~# uname -r
>> 4.9.107
>>  matica!503 ~# strings 
>> /lib64/modules/4.9.107/kernel/drivers/video/console/fbcon
>> .ko | fgrep -e 'vermagic='
>> vermagic=4.9.107 SMP
>>  matica!504 ~# modprobe fbcon
>> modprobe: ERROR: could not insert 'fbcon': Exec format error
>>  matica!505 ~# exit
>>
>> Script done on 2018-06-08 21:14:46-0700
>>
>> Sorry to ruin the low-hanging hypothesis :-P
>>
>
> Did dmesg have anything useful to say other than exec format error?
> Have you tried insmod'ing the modules instead of modprobe'ing them?
>>
>>
>> --

I had a look at the source code for kmod-25. If I read it right, dmesg
should have records along the lines of:
kmod-25/libkmod/libkmod-module.c:886:   INFO(mod->ctx, "Failed
to insert module '%s': %m\n", path);

modprobe returns Exec format error.

errno -l | grep 'Exec format error'
ENOEXEC 8 Exec format error

/usr/include/asm-generic/errno-base.h:
#define   ENOEXEC  8  /* Exec format error */

Here's the execution path I've been able to follow:
insmod()->kmod_module_probe_insert_module()->kmod_module_insert_module()->init_module()->copy_module_from_user();

init_module(2):
http://man7.org/linux/man-pages/man2/init_module.2.html
ENOEXEC
  The binary image supplied in module_image is not an ELF image,
  or is an ELF image that is invalid or for a different
  architecture.

(1). kmod-25/tools/modprobe.c
ENOEXEC returned by kmod_module_probe_insert_module().
static int insmod(struct kmod_ctx *ctx, const char *alias,
const char *extra_options)
{
...
kmod_list_foreach(l, list) {
...
if (lookup_only)
printf("%s\n", kmod_module_get_name(mod));
else {
err = kmod_module_probe_insert_module(mod, flags,
extra_options, NULL, NULL, show);
}

if (err >= 0)
/* ignore flag return values such as a mod being blacklisted */
err = 0;
else {
switch (err) {
...
default:
ERR("could not insert '%s': %s\n", <- the error message reported by modprobe
kmod_module_get_name(mod),
strerror(-err));
break;
}
}

(2). kmod-25/libkmod/libkmod-module.c
KMOD_EXPORT int kmod_module_probe_insert_module(struct kmod_module *mod,
unsigned int flags, const char *extra_options,
int (*run_install)(struct kmod_module *m,
const char *cmd, void *data),
const void *data,
void (*print_action)(struct kmod_module *m,
bool install,
const char *options))
{
...
if (!(flags & KMOD_PROBE_DRY_RUN))
err = kmod_module_insert_module(m, flags,
options);
}
...
}

(3). KMOD_EXPORT int kmod_module_insert_module(struct kmod_module *mod,
unsigned int flags,
const char *options)
{
...
size = kmod_file_get_size(mod->file); <- the size of your modules elf file
...
err = init_module(mem, size, args);
...
}

(4). [init_module syscall]
kernel/module.c
SYSCALL_DEFINE3(init_module, void __user *, umod,
unsigned long, len, const char __user *, uargs)
{
int err;
struct load_info info = { };

err = may_init_module();
if (err)
return err;

pr_debug("init_module: umod=%p, len=%lu, uargs=%p\n",
   umod, len, uargs);

err = copy_module_from_user(umod, len, );
if (err)
return err;

return load_module(, uargs, 0);
}

(5). kernel/module.c
/* Sets info->hdr and info->len. */
static int copy_module_from_user(con

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Sat, Jun 9, 2018, 07:34 Ian Zimmerman  wrote:

> On 2018-06-08 22:38, Alexander Kapshuk wrote:
>
> > On Fri, Jun 8, 2018, 22:30 Ian Zimmerman  wrote:
> >
> > > On 2018-06-08 22:00, Alexander Kapshuk wrote:
> > >
> > > > What's the output of:
> > > > uname -r
> > > > strings /path/to/your/module.ko | grep vermagic=
> > >
> > > Here are the results for 4.9.105 (working):
> > >
> > >  matica!6 ~$ uname -r
> > > 4.9.105
> > >  matica!7 ~$ strings
> > >  /lib64/modules/4.9.105/kernel/drivers/video/console/fbcon.ko |
> > >  fgrep -e 'vermagic='
> > > vermagic=4.9.105 SMP
> > >
> > > Let me know if you need to see the ones for the broken kernel ...
> > >
> >
> > Yes, we want to make sure the vermagic of the modules you're trying to
> load
> > matches the output of uname -r of the running kernel.
>
> Ok, here:
>
> Script started on 2018-06-08 21:11:04-0700
>  matica!501 ~# ls -l
> /lib64/modules/4.9.107/kernel/drivers/video/console/fbcon.ko
> -rw-r--r-- 1 root root 54280 Jun  8 20:57
> /lib64/modules/4.9.107/kernel/drivers/video/console/fbcon.ko
>  matica!502 ~# uname -r
> 4.9.107
>  matica!503 ~# strings
> /lib64/modules/4.9.107/kernel/drivers/video/console/fbcon
> .ko | fgrep -e 'vermagic='
> vermagic=4.9.107 SMP
>  matica!504 ~# modprobe fbcon
> modprobe: ERROR: could not insert 'fbcon': Exec format error
>  matica!505 ~# exit
>
> Script done on 2018-06-08 21:14:46-0700
>
> Sorry to ruin the low-hanging hypothesis :-P
>
>
Did dmesg have anything useful to say other than exec format error?
Have you tried insmod'ing the modules instead of modprobe'ing them?

>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>
>

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Fri, Jun 8, 2018, 22:30 Ian Zimmerman  wrote:

> On 2018-06-08 22:00, Alexander Kapshuk wrote:
>
> > What's the output of:
> > uname -r
> > strings /path/to/your/module.ko | grep vermagic=
>
> Here are the results for 4.9.105 (working):
>
>  matica!6 ~$ uname -r
> 4.9.105
>  matica!7 ~$ strings
>  /lib64/modules/4.9.105/kernel/drivers/video/console/fbcon.ko |
>  fgrep -e 'vermagic='
> vermagic=4.9.105 SMP
>
> Let me know if you need to see the ones for the broken kernel ...
>

Yes, we want to make sure the vermagic of the modules you're trying to load
matches the output of uname -r of the running kernel.



> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>
>

Re: [gentoo-user] Re: Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Fri, Jun 8, 2018 at 7:37 PM Ian Zimmerman  wrote:
>
> On 2018-06-08 09:22, Alexander Kapshuk wrote:
>
> > >  matica!501 ~# modprobe fbcon
> > > modprobe: ERROR: could not insert 'fbcon': Exec format error
>
> > Could this be a multilib issue? Does you kernel have
> > CONFIG_IA32_EMULATION enabled?
> > See https://forums.gentoo.org/viewtopic-p-7647744.html.
>
> CONFIG_IA32_EMULATION is definitely set in the _current_ working kernel
> (ie. 4.9.105), and I use the working config-* file as the start for the
> new one (with make oldconfig), so unless there was a radical change in
> the kernel build, this doesn't look like a possible cause.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

What's the output of:
uname -r
strings /path/to/your/module.ko | grep vermagic=

Re: [gentoo-user] Latest 4.9 kernels broken?

[Alexander Kapshuk]

On Thu, Jun 7, 2018 at 11:45 PM Ian Zimmerman  wrote:
>
> I cannot get either 4.9.106 or 4.9.107 to work on my amd64 system at
> all.  It seems some (but not all) modules refuse to load:
>
> Script started on 2018-06-07 13:31:28-0700
>  matica!501 ~# modprobe fbcon
> modprobe: ERROR: could not insert 'fbcon': Exec format error
>  matica!502 ~# ls /usr/lib/modules/4.9.106/kernel/sound/
> core/ hda/  pci/  soundcore.ko
>  matica!502 ~# ls /lib/modules/4.9.106/kernel/sound/hda/
> snd-hda-core.ko
>  matica!503 ~# modprobe snd-hda-core
> modprobe: ERROR: could not insert 'snd_hda_core': Exec format error
>  matica!504 ~# exit
> Script done on 2018-06-07 13:32:56-0700
>
> I am pretty sure this is caused by:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=b790b4f22a165e85f0b53a3231764034e42c7ea6
>
> Wth can I do about it?  Wait for an updated kmod package?  How long will
> that take?
>
> I run without initramfs, gcc version is 6.4.0-r1
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>

Could this be a multilib issue? Does you kernel have
CONFIG_IA32_EMULATION enabled?
See https://forums.gentoo.org/viewtopic-p-7647744.html.

Re: [gentoo-user] OT: Extracting year from data, but honour empty lines

[Alexander Kapshuk]

On Sat, May 12, 2018 at 2:16 AM, Daniel Frey  wrote:
> Hi all,
>
> I am trying to do something relatively simple and I've had something
> working in the past, but my brain just doesn't want to work today.
>
> I have a text file with the following (this is just a subset of about
> 2500 dates, and I don't want to edit these all by hand if I can avoid it):
>
> --- START ---
> December 2, 1994
> March 27, 1992
> June 4, 1994
> 1993
> January 11, 1992
> January 3, 1995
>
>
> March 12, 1993
> July 12, 1991
> May 17, 1991
> August 7, 1992
> December 23, 1994
> March 27, 1992
> March 1995
> --- END ---
>
> As you can see, there's no standard in the way the date is formatted.
> Some of them are also formatted -MM-DD and MM-DD-.
>
> I have a basic grep that I tossed together:
>
> grep -o '\([0-9]\{4\}\)'
>
> This does extract the year but yields the following:
>
> 1994
> 1992
> 1994
> 1993
> 1992
> 1995
> 1993
> 1991
> 1991
> 1992
> 1994
> 1992
> 1995
>
> As you can see, the two empty lines are removed but this will cause
> problems with data not lining up later on.
>
> Does anyone have a quick tip for my tired brain to make this work and
> just output a blank line if there's no match? I swear I did this months
> ago and had something working but I apparently didn't bother saving the
> script I made. Argh!
>
> Dan
>

Here's an awk and sed scripts for you to try:
cat dates
December 2, 1994
March 27, 1992
June 4, 1994
1993
January 11, 1992
January 3, 1995


March 12, 1993
July 12, 1991
May 17, 1991
August 7, 1992
December 23, 1994
March 27, 1992
March 1995

2018-05-12
05-12-2018

awk 'match($0,/[0-9][0-9][0-9][0-9]/){
print substr($0, RSTART, RLENGTH)
}
/^$/
' dates

1994
1992
1994
1993
1992
1995


1993
1991
1991
1992
1994
1992
1995

2018
2018

sed 's/.*\([0-9][0-9][0-9][0-9]\).*/\1/p
/^$/p
d' dates

1994
1992
1994
1993
1992
1995


1993
1991
1991
1992
1994
1992
1995

2018
2018

Re: [gentoo-user] Kernel compile error

[Alexander Kapshuk]

On Wed, Apr 25, 2018 at 10:03 AM, Klaus Ethgen  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi,
>
> I stumbled into the next problem.
>
> I do have a decent kernel compile knowledge but that seems to be gentoo
> specific.
>
> I have a old i686 machine where I installed gentoo on. Now when I did
> the kernel the first time, it worked well. everything fine exept some
> minor stuff (see below).
>--- /etc/kernels/kernel-config-x86-4.9.76-gentoo-r1 2018-04-25 
> 07:48:25.735961235 +0100
>+++ .config 2018-04-25 07:48:25.830960047 +0100
>@@ -480,7 +480,6 @@
> # CONFIG_PHYS_ADDR_T_64BIT is not set
> CONFIG_BOUNCE=y
> CONFIG_VIRT_TO_BUS=y
>-CONFIG_MMU_NOTIFIER=y
> # CONFIG_KSM is not set
> CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
> # CONFIG_TRANSPARENT_HUGEPAGE is not set
>@@ -1528,7 +1527,7 @@
> # CONFIG_DM_THIN_PROVISIONING is not set
> # CONFIG_DM_CACHE is not set
> # CONFIG_DM_ERA is not set
>-# CONFIG_DM_MIRROR is not set
>+CONFIG_DM_MIRROR=m
> # CONFIG_DM_RAID is not set
> # CONFIG_DM_ZERO is not set
> # CONFIG_DM_MULTIPATH is not set
>@@ -1805,8 +1804,8 @@
> #
> CONFIG_INPUT_MOUSEDEV=m
> # CONFIG_INPUT_MOUSEDEV_PSAUX is not set
>-CONFIG_INPUT_MOUSEDEV_SCREEN_X=1600
>-CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1200
>+CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
>+CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
> # CONFIG_INPUT_JOYDEV is not set
> CONFIG_INPUT_EVDEV=y
> # CONFIG_INPUT_EVBUG is not set
>@@ -2463,12 +2462,12 @@
> # CONFIG_AGP_ALI is not set
> # CONFIG_AGP_ATI is not set
> # CONFIG_AGP_AMD is not set
>-# CONFIG_AGP_AMD64 is not set
>+CONFIG_AGP_AMD64=y
> CONFIG_AGP_INTEL=y
> # CONFIG_AGP_NVIDIA is not set
>-# CONFIG_AGP_SIS is not set
>+CONFIG_AGP_SIS=y
> # CONFIG_AGP_SWORKS is not set
>-# CONFIG_AGP_VIA is not set
>+CONFIG_AGP_VIA=y
> # CONFIG_AGP_EFFICEON is not set
> CONFIG_INTEL_GTT=y
> CONFIG_VGA_ARB=y
>@@ -2489,7 +2488,7 @@
> # CONFIG_DRM_I2C_SIL164 is not set
> # CONFIG_DRM_I2C_NXP_TDA998X is not set
> CONFIG_DRM_RADEON=m
>-CONFIG_DRM_RADEON_USERPTR=y
>+# CONFIG_DRM_RADEON_USERPTR is not set
> # CONFIG_DRM_AMDGPU is not set
>
> #
>
> But now, when I try to compile the kernel, I get the following error:
>...
>make[2]: *** [scripts/kconfig/Makefile:39: silentoldconfig] Fehler 1
>make[1]: *** [Makefile:541: silentoldconfig] Fehler 2
>  SYSTBL  arch/x86/entry/syscalls/../../include/generated/asm/syscalls_32.h
>make: *** Keine Regel vorhanden, um das Ziel »include/config/auto.conf«,
>  benötigt von »include/config/kernel.release«, zu erstellen.  Schluss.
>make: *** Es wird auf noch nicht beendete Prozesse gewartet
>  SYSHDR  
> arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_32.h
>  SYSHDR  
> arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_64.h
>  SYSHDR  
> arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_x32.h
>* Gentoo Linux Genkernel; Version 3.4.52.4
>* Running with options: --btrfs --lvm --menuconfig 
> --kernel-cc=/usr/lib/ccache/bin/gcc all
>* Using genkernel.conf from /etc/genkernel.conf
>* Sourcing arch-specific config.sh from 
> /usr/share/genkernel/arch/x86/config.sh ..
>* Sourcing arch-specific modules_load from 
> /usr/share/genkernel/arch/x86/modules_load ..
>
>* ERROR: Failed to compile the "prepare" target...
>*
>* -- Grepping log... --
>*
>*
>* -- End log... --
>*
>* Please consult /var/log/genkernel.log for more information and any
>* errors that were reported above.
>*
>* Report any genkernel bugs to bugs.gentoo.org and
>* assign your bug to genker...@gentoo.org. Please include
>* as much information as you can in your bug report; attaching
>* /var/log/genkernel.log so that your issue can be dealt with effectively.
>*
>* Please do *not* report compilation failures as genkernel bugs!
>
> I even try to compile with exactly the same config that compiled some
> days before but got the same error.
>
> The installed kernel sources and genkernel are:
> [IP-] [  ] sys-kernel/genkernel-3.4.52.4-r2:0
> [IP-] [  ] sys-kernel/gentoo-sources-4.9.76-r1:4.9.76-r1
>
> As the error is completely without a meaning for me, maybe others have
> an Idea.
>
> Regards
>Klaus
> - --
> Klaus Ethgen   http://www.ethgen.ch/
> pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
> Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
> -BEGIN PGP SIGNATURE-
> Comment: Charset: ISO-8859-1
>
> iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlrgKDIACgkQpnwKsYAZ
> 9qyYvQwAtK+EA0Kv8Vt5443fml9mh0te6k/WUMlAps0u0Ds58NU+IBYebcLCasmM
> SG/SDjt/WSJCeb9LQ0w8W9xpi5NAn2HpUiKdpZHeyqiJ5EqHxE6qAMHbsdgSsybY
> 

Re: [gentoo-user] The return of the dreaded "Cannot run C compiled programs"

[Alexander Kapshuk]

On Tue, Mar 27, 2018 at 12:01 PM, Peter Humphrey  wrote:
> On Tuesday, 27 March 2018 01:24:09 BST Daniel Frey wrote:
>
>> I ran into this some time ago and one of the updates removed the /lib ->
>> /lib64 symlink.
>>
>> I simply ran `ln -s /lib64 /lib` and it was fine after that.
>
> Nice idea, Dan, but that isn't it in this case:
>
> # /bin/ls -ld /lib
> lrwxrwxrwx 1 root root 5 Mar 12 00:08 /lib -> lib64
>
> --
> Regards
> Peter
>
>

See if this post helps:
Failed to emerge sys-apps/sandbox-2.12:
https://forums.gentoo.org/viewtopic-t-1076582-start-0.html

Re: [gentoo-user] Nvidia kernel module API version mismatch

[Alexander Kapshuk]

On Thu, Mar 15, 2018 at 1:09 PM, Aleksander Okonski
 wrote:
> Hey,
>
> I have run into a strange problem with my nvidia drivers and gentoo. I am
> currently running kernel 4.14.14 and I upgraded my
> x11-drivers/nvidia-drivers to 390.42 from 390.25. Once the new drivers were
> installed I rebooted my laptop. Once rebooted I was unable to start the xorg
> server using startx and was greeted with errors. The /var/logs/xorg.0.log
> said that the problem was with the kernel module. Looking at dmesg I see
> that I am getting the error:
>
> NVRM: API mismatch: the client has the version 390.42, but this kernel
> module has version 390.25. please make sure that this kernel module and all
> NVIDIA driver components have the same version.
>
> I therefor thought that maybe I forgot to "emerge @module-rebuild" so I ran
> that and rebooted to make sure that everything was ok. However I am still
> getting the same problem.
>
> Looking at /usr/src/linux it is pointing to the correct kernel of 4.14.14
> and running "modinfo nvidia" it shows that "filename:
> /lib/modules/4/14/14-gentoo/video/nvidia.ko" and that version is 390.42.
> The other nvidia modules (nvidia-drm, nvidia-modeset, and nvidia-uvm) show
> that they are built for the correct kernel and that they are also version
> 390.42.
>
> I have tried to debug this issue however all the recourse that I was able to
> find mostly said to reboot or perform rmmod nvidia then modprobe nvidia.
> However when I try to rmmod nvidia it is dependent on nvidia-modeset and
> nvidia-drm. Trying to rmmod nvidia-drm will not work as I get the error
> "rmmod error: module nvidia_drm in in use".
>
> I therefor cannot understand why and where the error is coming from as it
> seems like the kernel has the correct nvidia modules loaded. Any ideas on
> how to fix it or any other suggestions?
>
> Thanks,
> Aleks

Just to clarify, does:
modinfo nvidia
display version 390.42 or 390.25?

Re: [gentoo-user] chromium-65.0.3325.146 compilation warnings

[Alexander Kapshuk]

On Mon, Mar 12, 2018 at 10:17 AM, Mick  wrote:
> I can see a few warnings pilling up on different systems when trying to emerge
> chromium-65.0.3325.146:
>
> warning: unknown warning option '-Wno-enum-compare-switch'; did you mean '-
> Wno-enum-compare'? [-Wunknown-warning-option]
> warning: unknown warning option '-Wno-tautological-unsigned-zero-compare' [-
> Wunknown-warning-option]
> warning: unknown warning option '-Wno-null-pointer-arithmetic'; did you mean
> '-Wno-null-arithmetic'? [-Wunknown-warning-option]
> warning: unknown warning option '-Wno-tautological-constant-compare'; did you
> mean '-Wno-tautological-pointer-compare'? [-Wunknown-warning-option]
> 4 warnings generated.
>
> Does this mean I should be using a different gcc or CFLAGS?
>
> They mostly are:
>
> CFLAGS="-march=native -O2 -pipe"
>
> --
> Regards,
> Mick

On my x86 system, I've been seeing similar warnings being generated by
clang when compiling the ffmpeg that comes with chromium.
I've also hit another bug related to that, where clang compilation
terminates with an error message along the lines of there being not
enough registers available.
There's a bug registered for that in chromium bugzilla, which I can't
reference at the moment. So far, no solution has been implemented, as
far as I could tell.

Re: [gentoo-user] [OT] Kinda "try ... catch" in a shell script...how

[Alexander Kapshuk]

On Sat, Mar 10, 2018 at 10:26 AM,   wrote:
> Hi,
>
> I have a coyple of files on my harddisk and on a mobile usb-disc.
>
> Their names are of that pattern:
>
>  something--something
>
> where 'soemthing' can be totally different from file to file and
> '' is a checksum, which does not match the checksum of the
> according file.
>
> I want to delete the files on my harddisk, which has a ''
> which matches the '' of the according file on the mobile
> harddisk.
>
> The problem arises from a line of the shellscript I wrote.
>
> # code to extract the checksum from the file and put into
> # a variable named crc
>
> if [ -f /*$crc* ] ; then
>
> # remove file on PC harddisk here
>
> fi
>
> As soon the file is not found, the script ends with an 'Not found'
> error, which '-f' is exactly for, because the expanding comes before
> the '-f'...
>
> So I need something else or a try-catch-thingy to make that work...but
> how?
>
> Or do I miss the forest for the trees here... ;)
>
> Thanks a lot for the forest in advance!
> Cheers
> Meino
>
>
>
>
>

If you were using a loop, you could do something like this:
for file in /path/to/files
do test -f $file || continue
rm $file
done

Care to post the entire script, so we could probably come up with the
right solution for you?

Re: [gentoo-user] Re: kernel choices for booting gentoo as guest in vbox vm

[Alexander Kapshuk]

On Fri, Feb 2, 2018 at 6:32 AM, Harry Putnam <rea...@newsguy.com> wrote:
> Alexander Kapshuk <alexander.kaps...@gmail.com> writes:
>
> [...]
>
>>> Can anyone tell me what they used to allow gentoo in vbox to boot?
>>>
>>>
>>>
>> Did you enable the recommended kernel config options as suggested here [1]?
>> [1] https://wiki.gentoo.org/wiki/VirtualBox
>
> I did go thru that page and `think' I checked them off but I came to
> that URL kind of late in the game... It would have no doubt went
> better if I'd caught that earlier on.
>
> It does appear to share some confusion with a couple of other pages.
> I don't have them to hand but one said flatly not to use `any' of the
> first bunch of framebuffer settings (1st and 2nd is based on how they
> are arranged in `menuconfig') and to only use the second set (a few
> lines below).
>
> They were saying that the kernel frame buffering will absolutely
> not work if one employs any of the settings from the first bunch.
>
>

The Kernel modesetting section of the xorg guide,
https://wiki.gentoo.org/wiki/Xorg/Guide, recommends disabling most of
the drivers listed in the 'Support for frame buffer devices' section
of .config.
I could be wrong, but I believe that applies to installing the kernel
on real hardware specifically.

For emulated environments, such as virtualbox, the instructions given
in the wiki article for virtualbox take precedence.
Virtualbox uses GPU frame buffers and has routines that convert GPU
memory layouts to kernel ones and back, as far as I can tell.

Re: [gentoo-user] kernel choices for booting gentoo as guest in vbox vm

[Alexander Kapshuk]

On Wed, Jan 31, 2018 at 2:44 PM, Harry Putnam  wrote:
> Installing gentoo as guest into vbox vm on solaris-11 (openindiana)
> HOST
> gentoo-17
> VBox 5.2.6
> Kernel 4.15.0
>
> My first boot resulted in resulted in a kernel panic... not able to
> mount root.
>
> I checked my /etc/fstab trying to make sure I didn't make a stupid
> mistake there... it appear to be sound. (Included at the end of post)
>
> I suspect it may be the result of a kernel choice... or rather the
> lack of one.  Something that would have been able to mount /
>
> I thought it would be ata_piix and made sure that was selected in
> kernel .config
>
> I'm thinking it may be be ata_generic, which I did not have selected.
> Which I have now enabled.  But I see now, that is for IDE.
>
> In a chroot now I can see lspci -k shows ata_piix in use .. but that
> would probably be because in vbox I have the gentoo install media on
> IDE secondary master.  But also shows sata controller ahci
>
> Which I do also have selected in .config.  However there a number of
> AHCI choices in the kernel config that were not selected.
>
> Can anyone tell me what they used to allow gentoo in vbox to boot?
>
>
>
Did you enable the recommended kernel config options as suggested here [1]?
[1] https://wiki.gentoo.org/wiki/VirtualBox

Re: [gentoo-user] Re: gcc 7.3 + kernel 4.15 = spectre_v2 fixed

[Alexander Kapshuk]

On Mon, Jan 29, 2018 at 7:50 PM, Ian Zimmerman  wrote:
> On 2018-01-29 20:11, Adam Carter wrote:
>
>> Comparing the contents of /sys/devices/system/cpu/vulnerabilities/spectre_v2
>>
>> With gcc 7.2 + kernel 4.14.15;
>> Intel system shows; Vulnerable: Minimal generic ASM retpoline
>> AMD system shows: Vulnerable: Minimal AMD ASM retpoline
>>
>> With gcc 7.3 + kernel 4.15.0;
>> Intel system shows; Mitigation: Full generic retpoline
>> AMD system shows' Mitigation: Full AMD retpoline
>
> Is there a simple way, with the upstream (kernel.org) sources, to force
> a compiler different from the system default?  If there is, it's not in the
> README, and a simple grep over the Makefiles also doesn't enlighten.
>
> I am not ready to activate a keyworded gcc for general use.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet, fetch the TXT record for the domain.
>

To compile the kernel with a different compiler, the method shown
below may be used, e.g.:
make CC=clang

See [1], for details:
Building the kernel with Clang:
[1] https://lwn.net/Articles/734071/

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Alexander Kapshuk]

On Tue, Jan 23, 2018 at 10:03 AM, Corbin Bird <corbinb...@charter.net> wrote:
>
>
> On 01/23/2018 01:42 AM, Alexander Kapshuk wrote:
>> On Tue, Jan 23, 2018 at 4:34 AM, Corbin Bird <corbinb...@charter.net> wrote:
>>> On 01/22/2018 11:56 AM, Rich Freeman wrote:
>>>> On Mon, Jan 22, 2018 at 12:11 PM, Alexander Kapshuk
>>>> <alexander.kaps...@gmail.com> wrote:
>>>>> On Mon, Jan 22, 2018 at 5:51 PM, Corbin Bird <corbinb...@charter.net> 
>>>>> wrote:
>>>>>> Anyone else getting this error? ( kernel 4.9.77 )
>>>>>>
>>>>>>>   CC  fs/ext4/mballoc.o
>>>>>>>   CC  fs/ext4/block_validity.o
>>>>>>>   CC  fs/ext4/move_extent.o
>>>>>>>   CC  fs/ext4/mmp.o
>>>>>>>   CC  fs/ext4/indirect.o
>>>>>>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>>>>>>> find jump dest instruction at .text+0x56c
>>>>>>>   CC  fs/ext4/extents_status.o
>>>>>>> /bin/sh: line 1: 31735 Segmentation fault  ./tools/objtool/objtool
>>>>>>> check "fs/ext4/extents_status.o"
>>>>>>> make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
>>>>>>> Error 139
>>>>>>> make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
>>>>>>> make: *** [Makefile:995: fs] Error 2
>>>>>> Corbin
>>>>>>
>>>>>>
>>>>> Based on the output you supplied, objtool isn't happy with
>>>>> fs/ext4/indirect.o and fs/ext4/extents_status.o.
>>>>> Did you do 'make clean' prior to building the kernel?
>>>>> If you did, it might be worth doing a 'make mrproper' before
>>>>> rebuilding the kernel.
>>>>> Don't forget to back up your .config before running mrproper.
>>>>>
>>>> While this is going to cause a bit more building, I personally tend to
>>>> redirect kernel build output.  I add O=/var/tmp/linux to all my make
>>>> commands, which leaves /usr/src untouched and builds faster besides
>>>> (tmpfs).
>>>>
>>>> The main downsides to this are:
>>>> 1.  Make can't re-use objects from previous builds, so rebuilds will
>>>> go slower.  Though, IMO this is worthwhile if re-using those objects
>>>> causes issues (which I assume is due to imperfect makefiles).
>>>> 2.  When building packages that install kernel modules the prepared
>>>> sources won't exist.  This requires going back and re-preparing them
>>>> (make O=/var/tmp/linux modules_prepare).  For packages like zfs-kmod
>>>> that use Module.symvers this is even more painful as you can only get
>>>> that by rebuilding the whole thing.
>>>>
>>> Tried both approaches ... the results :
>>>> make distclean
>>>> make mrproper
>>>> --> copy over .config
>>>> make modules_prepare
>>>> make && make modules_install
>>>>
>>>>   CC  fs/ext4/block_validity.o
>>>>   CC  fs/ext4/move_extent.o
>>>>   CC  fs/ext4/mmp.o
>>>>   CC  fs/ext4/indirect.o
>>>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>>>> find jump dest instruction at .text+0x56c
>>>>   CC  fs/ext4/extents_status.o
>>>> /bin/sh: line 1: 24095 Segmentation fault  ./tools/objtool/objtool
>>>> check "fs/ext4/extents_status.o"
>>>> make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
>>>> Error 139
>>>> make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
>>>> make: *** [Makefile:995: fs] Error 2
>>>>
>>>>
>>> Try 2 :
>>>> make distclean
>>>> make mrproper
>>>> --> copy over .config
>>>> make O=/var/tmp/linux modules_prepare
>>>> make O=/var/tmp/linux && make O=/var/tmp/linux modules_install
>>>>
>>>>   CC  fs/ext4/move_extent.o
>>>>   CC  fs/ext4/mmp.o
>>>>   CC  fs/ext4/indirect.o
>>>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>>>> find jump dest instruction at .text+0x56c
>>>>   CC  fs/ext4/extents_status.o
>>>> /bin/sh: line 1: 21028 Segmentation fault  ./tools/objtool/objtool
>

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Alexander Kapshuk]

On Tue, Jan 23, 2018 at 4:34 AM, Corbin Bird <corbinb...@charter.net> wrote:
> On 01/22/2018 11:56 AM, Rich Freeman wrote:
>> On Mon, Jan 22, 2018 at 12:11 PM, Alexander Kapshuk
>> <alexander.kaps...@gmail.com> wrote:
>>> On Mon, Jan 22, 2018 at 5:51 PM, Corbin Bird <corbinb...@charter.net> wrote:
>>>> Anyone else getting this error? ( kernel 4.9.77 )
>>>>
>>>>>   CC  fs/ext4/mballoc.o
>>>>>   CC  fs/ext4/block_validity.o
>>>>>   CC  fs/ext4/move_extent.o
>>>>>   CC  fs/ext4/mmp.o
>>>>>   CC  fs/ext4/indirect.o
>>>>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>>>>> find jump dest instruction at .text+0x56c
>>>>>   CC  fs/ext4/extents_status.o
>>>>> /bin/sh: line 1: 31735 Segmentation fault  ./tools/objtool/objtool
>>>>> check "fs/ext4/extents_status.o"
>>>>> make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
>>>>> Error 139
>>>>> make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
>>>>> make: *** [Makefile:995: fs] Error 2
>>>> Corbin
>>>>
>>>>
>>> Based on the output you supplied, objtool isn't happy with
>>> fs/ext4/indirect.o and fs/ext4/extents_status.o.
>>> Did you do 'make clean' prior to building the kernel?
>>> If you did, it might be worth doing a 'make mrproper' before
>>> rebuilding the kernel.
>>> Don't forget to back up your .config before running mrproper.
>>>
>> While this is going to cause a bit more building, I personally tend to
>> redirect kernel build output.  I add O=/var/tmp/linux to all my make
>> commands, which leaves /usr/src untouched and builds faster besides
>> (tmpfs).
>>
>> The main downsides to this are:
>> 1.  Make can't re-use objects from previous builds, so rebuilds will
>> go slower.  Though, IMO this is worthwhile if re-using those objects
>> causes issues (which I assume is due to imperfect makefiles).
>> 2.  When building packages that install kernel modules the prepared
>> sources won't exist.  This requires going back and re-preparing them
>> (make O=/var/tmp/linux modules_prepare).  For packages like zfs-kmod
>> that use Module.symvers this is even more painful as you can only get
>> that by rebuilding the whole thing.
>>
>
> Tried both approaches ... the results :
>> make distclean
>> make mrproper
>> --> copy over .config
>> make modules_prepare
>> make && make modules_install
>>
>>   CC  fs/ext4/block_validity.o
>>   CC  fs/ext4/move_extent.o
>>   CC  fs/ext4/mmp.o
>>   CC  fs/ext4/indirect.o
>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>> find jump dest instruction at .text+0x56c
>>   CC  fs/ext4/extents_status.o
>> /bin/sh: line 1: 24095 Segmentation fault  ./tools/objtool/objtool
>> check "fs/ext4/extents_status.o"
>> make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
>> Error 139
>> make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
>> make: *** [Makefile:995: fs] Error 2
>>
>>
> Try 2 :
>>
>> make distclean
>> make mrproper
>> --> copy over .config
>> make O=/var/tmp/linux modules_prepare
>> make O=/var/tmp/linux && make O=/var/tmp/linux modules_install
>>
>>   CC  fs/ext4/move_extent.o
>>   CC  fs/ext4/mmp.o
>>   CC  fs/ext4/indirect.o
>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>> find jump dest instruction at .text+0x56c
>>   CC  fs/ext4/extents_status.o
>> /bin/sh: line 1: 21028 Segmentation fault  ./tools/objtool/objtool
>> check "fs/ext4/extents_status.o"
>> make[3]: *** [/usr/src/linux-4.9.77-gentoo/scripts/Makefile.build:294:
>> fs/ext4/extents_status.o] Error 139
>> make[2]: *** [/usr/src/linux-4.9.77-gentoo/scripts/Makefile.build:544:
>> fs/ext4] Error 2
>> make[1]: *** [/usr/src/linux-4.9.77-gentoo/Makefile:995: fs] Error 2
>> make[1]: Leaving directory '/var/tmp/linux'
>> make: *** [Makefile:150: sub-make] Error 2
> Try 2 gave an error warning about needing an 'make mrproper' ... the error :
>>
>>   CHK include/config/kernel.release
>>   UPD include/config/kernel.release
>>   Using /usr/src/linux-4.9.77-gentoo as source for kernel
>>   /usr/src/linux-4.9.77-gentoo is not clean, please run 'make mrproper'
>>   in the '/usr/src/linux-4.9.77-gentoo' directory.
>> make[1]: *** [/usr/src/linux-4.9.77-gentoo/Makefile:1021: prepare3]
>> Error 1
>> make[1]: Leaving directory '/var/tmp/linux'
>> make: *** [Makefile:150: sub-make] Error 2
> So ... I followed directions :
>> Darkstar /usr/src/linux # cd /usr/src/linux-4.9.77-gentoo
>> Darkstar /usr/src/linux-4.9.77-gentoo # make mrproper
>>   CLEAN   scripts/basic
>>   CLEAN   scripts/kconfig
>>   CLEAN   .config
>
> Still get the same error ...
>
> Corbin
>

Is this a distribution supplied kernel or vanilla or one with your own
customisations/modifications?

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Alexander Kapshuk]

On Mon, Jan 22, 2018 at 5:51 PM, Corbin Bird  wrote:
> Anyone else getting this error? ( kernel 4.9.77 )
>
>>   CC  fs/ext4/mballoc.o
>>   CC  fs/ext4/block_validity.o
>>   CC  fs/ext4/move_extent.o
>>   CC  fs/ext4/mmp.o
>>   CC  fs/ext4/indirect.o
>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>> find jump dest instruction at .text+0x56c
>>   CC  fs/ext4/extents_status.o
>> /bin/sh: line 1: 31735 Segmentation fault  ./tools/objtool/objtool
>> check "fs/ext4/extents_status.o"
>> make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
>> Error 139
>> make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
>> make: *** [Makefile:995: fs] Error 2
>
> Corbin
>
>

Based on the output you supplied, objtool isn't happy with
fs/ext4/indirect.o and fs/ext4/extents_status.o.
Did you do 'make clean' prior to building the kernel?
If you did, it might be worth doing a 'make mrproper' before
rebuilding the kernel.
Don't forget to back up your .config before running mrproper.

Let us know how you go.

Re: [gentoo-user] OT awk question

[Alexander Kapshuk]

On Fri, Jan 19, 2018 at 12:13 AM, Adam Carter <adamcart...@gmail.com> wrote:
> On Wed, Jan 17, 2018 at 6:16 PM, Alexander Kapshuk
> <alexander.kaps...@gmail.com> wrote:
>>
>> On Wed, Jan 17, 2018 at 3:49 AM, Adam Carter <adamcart...@gmail.com>
>> wrote:
>> > I'm using this to grab a section of text across multiple lines, how do i
>> > get
>> > it to exit after the first match?
>> >
>> > awk '/foo/,/bar/'
>>
>> See if this works for you:
>> awk '/foo/,/bar/{print;if(/bar/)exit}' file
>> sed '/foo/,/bar/!d;/bar/q' file
>>
> The awk line works. I didnt try the sed line. Thanks!

Good to hear.
Thanks for letting us know.

The sed line is identical in operation to the awk one:
(1). Delete anything that's not in the range of lines from /foo/ to /bar/;
(2). Print the lines that match the range specified;
(3). Quit processing further lines of input on finding the first
occurrence of /bar/;

Re: [gentoo-user] OT awk question

[Alexander Kapshuk]

On Wed, Jan 17, 2018 at 3:49 AM, Adam Carter  wrote:
> I'm using this to grab a section of text across multiple lines, how do i get
> it to exit after the first match?
>
> awk '/foo/,/bar/'

See if this works for you:
awk '/foo/,/bar/{print;if(/bar/)exit}' file
sed '/foo/,/bar/!d;/bar/q' file

Re: [gentoo-user] old kernels are installed during the upgrade

[Alexander Kapshuk]

On Tue, Jan 2, 2018 at 1:54 PM, Kruglov Sergey  wrote:
> Hello, All!
>
>
> Now I have  gentoo-sources-4.14.8-r1 installed.
>
> After  "emerge --ask --update --deep --with-bdeps=y --newuse @world" command
> emerge installs old kernel in NS (after first update 4.12.12, after second
> update 4.9.49-r1).
> How can I fix it?
> There is sys-kernel/gentoo-sources in my world set.
>
>

There was a discussion about this on the gentoo-dev mailing list. See
the link below for details:
https://archives.gentoo.org/gentoo-dev/message/1d2f3f98c2485fa53ed602bc8285054c

Re: [gentoo-user] Re: openrc : autoload kernel modules

[Alexander Kapshuk]

On Thu, Dec 14, 2017 at 8:11 PM, Hartmut Figge  wrote:
> Helmut Jarausch:
>
>>I have added the following lines to  /etc/conf.d/modules
>>
>>modules="enhanceio"
>>modules="enhanceio_lru"
>>modules="enhanceio_fifo"
>>modules="enhanceio_rand"
>>
>>
>>but these modules don't get loaded at boot time.
>
> Looking in my /etc/conf.d/modules there are
>
> # for a list of modules and their options.
> modprobe vboxdrv
> modprobe vboxnetflt
> modprobe vboxnetadp
> modprobe vboxpci
>
> Hm? ;)
>
> Hartmut
>
>

You want to verify the way you built and installed your external
modules against this doc,
https://www.kernel.org/doc/Documentation/kbuild/modules.txt.
See if you overlooked anything.

Re: [gentoo-user] autofs wants rpcgen despite libtirpc is USEd

[Alexander Kapshuk]

On Sat, Dec 9, 2017 at 6:03 PM,   wrote:
> Hi,
>
> autofs-5.1.3 fails to compile:
> solfire:/root>emerge -v autofs
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R] net-fs/autofs-5.1.3::gentoo  USE="libtirpc -dmalloc -hesiod 
> -ldap -mount-locking -sasl" 0 KiB
>
> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
>
 Verifying ebuild manifests
 Emerging (1 of 1) net-fs/autofs-5.1.3::gentoo
 Failed to emerge net-fs/autofs-5.1.3, Log file:
  '/var/tmp/portage/net-fs/autofs-5.1.3/temp/build.log'
 Jobs: 0 of 1 complete, 1 failed Load avg: 0.71, 0.95, 0.88
>  * Package:net-fs/autofs-5.1.3
>  * Repository: gentoo
>  * Maintainer: d...@gentoo.org
>  * USE:abi_x86_64 amd64 elibc_glibc kernel_linux libtirpc userland_GNU
>  * FEATURES:   preserve-libs sandbox userpriv usersandbox
>  * Determining the location of the kernel source code
>  * Found kernel source directory:
>  * /usr/src/linux
>  * Found sources for kernel version:
>  * 4.14.4-RT
>  * Checking for suitable kernel configuration options...
>  [ ok ]
 Unpacking source...
 Unpacking autofs-5.1.3.tar.xz to /var/tmp/portage/net-fs/autofs-5.1.3/work
 Source unpacked in /var/tmp/portage/net-fs/autofs-5.1.3/work
 Preparing source in /var/tmp/portage/net-fs/autofs-5.1.3/work/autofs-5.1.3 
 ...
>  * Running eautoreconf in 
> '/var/tmp/portage/net-fs/autofs-5.1.3/work/autofs-5.1.3' ...
>  * This package has a configure.in file which has long been deprecated.  
> Please
>  * update it to use configure.ac instead as newer versions of autotools will 
> die
>  * when it finds this file.  See https://bugs.gentoo.org/426262 for details.
>  * Running autoconf --force ...
>  [ ok ]
>  * Running autoheader ...
>  [ ok ]
>  * Running elibtoolize in: autofs-5.1.3/
 Source prepared.
 Configuring source in 
 /var/tmp/portage/net-fs/autofs-5.1.3/work/autofs-5.1.3 ...
 Working in BUILD_DIR: 
 "/var/tmp/portage/net-fs/autofs-5.1.3/work/autofs-5.1.3"
> /var/tmp/portage/net-fs/autofs-5.1.3/work/autofs-5.1.3/configure 
> --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu 
> --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share 
> --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 
> --docdir=/usr/share/doc/autofs-5.1.3 --with-confdir=/etc/conf.d 
> --with-mapdir=/etc/autofs --without-dmalloc --without-openldap 
> --with-libtirpc --without-sasl --without-hesiod --disable-mount-locking 
> --disable-ext-env --enable-sloppy-mount --enable-force-shutdown 
> --enable-ignore-busy --with-systemd=/usr/lib/systemd/system 
> RANLIB=/usr/bin/x86_64-pc-linux-gnu-ranlib
> configure: loading site script /usr/share/config.site
> checking for binaries in... /usr/bin:/bin:/usr/sbin:/sbin
> checking for Linux proc filesystem... yes
> checking location of the init.d directory... /etc/init.d
> checking for autofs configuration file directory... /etc/conf.d
> checking for autofs maps directory... /etc/autofs
> checking for autofs fifos directory... /run
> checking for autofs flag file directory... /run
> checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
> checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
> checking if libtirpc is requested and available... yes
> checking for getrpcbyname... yes
> checking for getservbyname... yes
> checking if malloc debugging is wanted... no
> checking for mount... /bin/mount
> checking for mount.nfs... /sbin/mount.nfs
> checking for umount... /bin/umount
> checking for fsck.ext2... /sbin/fsck.ext2
> checking for fsck.ext3... /sbin/fsck.ext3
> checking for fsck.ext4... /sbin/fsck.ext4
> checking for modprobe... /sbin/modprobe
> checking for flex... /usr/bin/flex
> checking for bison... /usr/bin/bison
> checking for ranlib... /usr/bin/x86_64-pc-linux-gnu-ranlib
> checking for rpcgen... no
> configure: error: required program RPCGEN not found
>
>
>
> configure misses rpcgen...and seems not to evaluate the USE of
> libtirpc.
>
> I didn't find any fix/patch online.
>
> What goes wrong here?
>
> Cheers
> Meino
>
>
>
If I'm reading the ebuild quoted below right, if 'libtirpc' is set, it
is net-libs/libtirpc that meets the dependency, otherwise it is glibc
compiled with rpc that does that.
/usr/portage/net-fs/autofs/autofs-5.1.3.ebuild:41,42
libtirpc? ( net-libs/libtirpc )
!libtirpc? ( elibc_glibc? ( sys-libs/glibc[rpc(-)] ) )

equery -q u sys-libs/glibc | grep rpc
+rpc

On my system, rpc is included in glibc:
equery -q b /usr/bin/rpcgen

Re: [gentoo-user] Is gnome becoming obligatory?

[Alexander Kapshuk]

On Sat, Dec 9, 2017 at 11:51 AM, Mick  wrote:
> I've seen gnome-base/gnome-common pulled in on more than one systems, all of
> which have USE="-gnome" set:
>
>  # emerge -uaNDvt world
>
> These are the packages that would be merged, in reverse order:
>
> Calculating dependencies... done!
> [nomerge   ] kde-apps/kdebase-meta-17.08.3:5::gentoo
> [nomerge   ]  kde-plasma/plasma-meta-5.10.5:5::gentoo  USE="bluetooth
> display-manager handbook pam pulseaudio sddm wallpapers -grub -gtk -
> networkmanager -plymouth -sdk"
> [nomerge   ]   kde-plasma/powerdevil-5.10.5:5::gentoo  USE="consolekit
> handbook wireless -debug"
> [nomerge   ]kde-frameworks/solid-5.37.0:5/5.37::gentoo  USE="nls -
> debug -doc {-test}"
> [ebuild U  ] sys-fs/udisks-2.7.4:2::gentoo [2.1.8:2::gentoo] USE="acl
> gptfdisk introspection nls%* -cryptsetup -debug (-elogind) -lvm% (-selinux) -
> systemd" 1,257 KiB
> [ebuild  N ]  sys-libs/libblockdev-2.14::gentoo  USE="crypt -bcache -
> dmraid -doc -kbd -lvm {-test}" PYTHON_SINGLE_TARGET="python3_5 -python3_4 -
> python3_6" PYTHON_TARGETS="python3_5 -python3_4 -python3_6" 268 KiB
> [ebuild  N ]   dev-libs/volume_key-0.3.9::gentoo  USE="{-test}"
> PYTHON_SINGLE_TARGET="python3_5 -python3_4 -python3_6"
> PYTHON_TARGETS="python3_5 -python3_4 -python3_6" 435 KiB
> [ebuild  N ]  gnome-base/gnome-common-3.18.0-r1:3::gentoo
> USE="autoconf-archive" 153 KiB
> [nomerge   ] sys-libs/libblockdev-2.14::gentoo  USE="crypt -bcache -dmraid
> -doc -kbd -lvm {-test}" PYTHON_SINGLE_TARGET="python3_5 -python3_4 -python3_6"
> PYTHON_TARGETS="python3_5 -python3_4 -python3_6"
> [ebuild  N ]  dev-libs/libbytesize-1.2::gentoo  USE="-doc {-test}"
> PYTHON_SINGLE_TARGET="python3_5 -python2_7 -python3_4 -python3_6"
> PYTHON_TARGETS="python2_7 python3_5 -python3_4 -python3_6" 69 KiB
>
> Total: 5 packages (1 upgrade, 4 new), Size of downloads: 2,180 KiB
>
> All systems are on profile:  default/linux/amd64/17.0/desktop/plasma
>
> Why is gnome-base/gnome-common needed?
>
> --
> Regards,
> Mick

It's sys-fs/udisks that wants gnome-base/gnome-common.

Re: [gentoo-user] memset_s

[Alexander Kapshuk]

On Fri, Nov 10, 2017 at 6:25 PM, R0b0t1  wrote:

> Hello,
>
> On Fri, Nov 10, 2017 at 5:34 AM, Jorge Almeida 
> wrote:
> > On Fri, Nov 10, 2017 at 10:52 AM, Marc Joliet  wrote:
> >> Am Freitag, 10. November 2017, 10:54:53 CET schrieb Jorge Almeida:
> >>> I'm trying to use memset_s() but the system (glibc?) doesn't know
> >>> about it. I also tried to compile against musl, same result.
> >>>
> >
> >
> >> It seems as though it is simply not implemented, I found a variety of
> links
> >> that all support this:
> >>
> >> https://stackoverflow.com/a/40162721
> >>
> >> https://stackoverflow.com/questions/38322363/when-will-
> the-safe-string-functions-of-c11-be-part-of-glibc
> >>
> >> https://gcc.gnu.org/wiki/C11Status (which states that Annex K is not
> >> implemented)
> >>
> >> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1967.htm
> >>
> > OK, thanks. The last link even suggests that Annex K should be
> > deprecated. I suppose this people don't care about security at all.
> >
>
> I'm having trouble finding the article again, but these functions look
> very similar to Microsoft's extensions to the C standard. There is a
> good case to be made that they are counterproductive.
>
> > Of course, what would really solve the optimize-into-oblivion problem
> > is a pragma that when invoked on a particular block of code (maybe
> > only a function definition) would tell the compiler to do what the
> > programmer says rather than viewing a function as a kind of black box.
> >
>
> This would probably be useful. It may be wise to reimplement important
> functionality.
>
> Cheers,
>  R0b0t1
>
>
It's also a part of NetBSD's libc used by Apple.
https://opensource.apple.com/source/Libc/Libc-1044.1.2/string/NetBSD/memset_s.c

Re: [gentoo-user] UFO: 'No. You make ME a sandwich.'

[Alexander Kapshuk]

On Mon, Oct 30, 2017 at 1:59 PM, Helmut Jarausch  wrote:

> Hi,
> when trying to re-emerge libreoffice I get the strange message
> No. You make ME a sandwich.
> Has anybody seen this before?
> This occurs after having re-emerge 3500 packages from an
> emerge --emptyworld
>
> Many thanks for some hints,
> Helmut
>
>
You probably want to contact the libreoffice maintainers about this.
The code that generates the message you were asking about seems to be this:

https://raw.githubusercontent.com/LibreOffice/core/master/Makefile.in

check-if-root:
@if test `id -u` = 0 && ! grep -q 'lxc\|docker' /proc/self/cgroup; then 
\
echo; \
echo 'No. You make ME a sandwich.'; \
echo; \
exit 1; \
fi

Re: [gentoo-user] www-plugins/adobe-flash

[Alexander Kapshuk]

On Fri, Oct 27, 2017 at 10:42 AM, Jorge Almeida  wrote:

> Cannot download it: 404
>
> I emerge --sync'ed yesterday, and again just a few minutes ago, in
> case the particular version of the package required by portage (
> www-plugins/adobe-flash-27.0.0.170) was nuked.
>
> What might be happening here?
>
> Jorge Almeida
>
>
Using a UK-based portage mirror here:
:; grep -R '^[^#]*uk' /etc/portage/
/etc/portage/repos.conf/gentoo.conf:sync-uri = rsync://
rsync.uk.gentoo.org/gentoo-portage
/etc/portage/make.conf:GENTOO_MIRRORS="http://mirror.bytemark.co.uk/gentoo/;

With adobe-flash-27.0.0.170 still available in the portage tree:
equery -q w adobe-flash
/usr/portage/www-plugins/adobe-flash/adobe-flash-27.0.0.170.ebuild

You may want to try a different mirror. See if that helps.

Re: [gentoo-user] Machine not booting properly: profile.env cannot execute binary file

[Alexander Kapshuk]

On Wed, Oct 25, 2017 at 9:45 PM, Andrew Lowe  wrote:

> On 25/10/17 11:28, Andrew Lowe wrote:
> > Hi all,
> > My machine went feral which resulted in me having to kill the power
> > to kill it. Upon reboot everything looked good, fsck did it's job,
> > [ok]'s scrolled up the screen etc and then I got the login prompt. I
> > entered my username & password and then the fun began.
> >
> > I got:
> >
> > -bash: .: /etc/profile.env: cannot execute binary file
> >
> > If I tried any command, say ls, I got:
> >
> > -bash: ls: no such file or dir
> >
> > I've now rebooted the machine using a relatively recent sysrescueCD
> > and had a look at profile.env and it's binary but I thought it should
> > have been text In the top line or so it mentions "ld" for some
> > reason. I checked the same file on the boot disk and it's text. One or
> > two I found on line are also text.
> >
> > Does anyone have any idea as to what's going on here? Should I just
> > grab the profile.env from the boot disk and drop it into the /etc dir?
> > Or should I go through the whole process of chroot off a gentoo disc and
> > then run env-update as it says in the header of the text versions I'v
> seen?
> >
> > Thoughts greatly appreciated,
> >
> > Andrew
> >
> >
>
> Well, I managed to work this out. I grabbed profile.env from a
> laptop
> running gentoo and using sysrescuecd booted the desktop and dropped
> profile.env into it's /etc dir. Fiddled the permissions and rebooted.
> This time after the reboot, it only told me that it couldn't find
> commands, ls, cd etc. Obviously pathing wasn't working. I found out
> where env-update lived, /usr/sbin/env-update, providing the full path to
> it, ran it then kicked over into another terminal, logged in and hey
> presto, things are good. A reboot and this was confirmed.
>
> The cause - I have no idea. It now works so I'm happy. Thanks for
> the
> suggestions people provided,
>
> Andrew
>
>
Posting your query on the gentoo-portage-dev mailing list might get you a
more informed response as to why this happened in the first place.

Re: [gentoo-user] Machine not booting properly: profile.env cannot execute binary file

[Alexander Kapshuk]

On Wed, Oct 25, 2017 at 6:28 AM, Andrew Lowe  wrote:

> Hi all,
> My machine went feral which resulted in me having to kill the
> power to kill it. Upon reboot everything looked good, fsck did it's job,
> [ok]'s scrolled up the screen etc and then I got the login prompt. I
> entered my username & password and then the fun began.
>
> I got:
>
> -bash: .: /etc/profile.env: cannot execute binary file
>
> If I tried any command, say ls, I got:
>
> -bash: ls: no such file or dir
>
> I've now rebooted the machine using a relatively recent
> sysrescueCD and had a look at profile.env and it's binary but I thought it
> should have been text In the top line or so it mentions "ld" for some
> reason. I checked the same file on the boot disk and it's text. One or two
> I found on line are also text.
>
> Does anyone have any idea as to what's going on here? Should I
> just grab the profile.env from the boot disk and drop it into the /etc dir?
> Or should I go through the whole process of chroot off a gentoo disc and
> then run env-update as it says in the header of the text versions I'v seen?
>
> Thoughts greatly appreciated,
>
> Andrew
>
>
Something else for you to try.
https://forums.gentoo.org/viewtopic-t-797683-start-0.html

Re: [gentoo-user] ARCH is not set

[Alexander Kapshuk]

On Sat, Sep 30, 2017 at 9:55 AM, IceAmber <iceamber2...@gmail.com> wrote:

> No, I cannot find the make.default in the profile directory
>
> On Sat, Sep 30, 2017 at 1:36 PM, Alexander Kapshuk <
> alexander.kaps...@gmail.com> wrote:
>
>>
>>
>> On Fri, Sep 29, 2017 at 3:48 PM, IceAmber <iceamber2...@gmail.com> wrote:
>>
>>> Hi, everyone
>>>
>>> I have a problem when updating my system
>>>
>>>  * ARCH is not set... Are you missing the '/etc/portage/make.profile'
>>>  * symlink? Is the symlink correct? Is your portage tree complete?
>>>
>>> and the symlink of '/etc/portage/make.profile' is
>>>
>>> # ls -l /etc/portage/make.profile
>>> lrwxrwxrwx 1 root root 59 7  13 2016 /etc/portage/make.profile ->
>>> ../../usr/portage/profiles/default/linux/amd64/13.0/desktop
>>>
>>> any suggestions?
>>>
>>>
>>>
>>>
>> Do you have make.defaults in the profile directory for your architecture?
>> As this is where ARCH is set.
>>
>> grep ^ARCH /usr/portage/profiles/arch/amd64/make.defaults
>> ARCH="amd64"
>>
>
>
Can you try re-syncing your portage tree and see if make.defaults gets
pulled in?

Re: [gentoo-user] ARCH is not set

[Alexander Kapshuk]

On Fri, Sep 29, 2017 at 3:48 PM, IceAmber  wrote:

> Hi, everyone
>
> I have a problem when updating my system
>
>  * ARCH is not set... Are you missing the '/etc/portage/make.profile'
>  * symlink? Is the symlink correct? Is your portage tree complete?
>
> and the symlink of '/etc/portage/make.profile' is
>
> # ls -l /etc/portage/make.profile
> lrwxrwxrwx 1 root root 59 7  13 2016 /etc/portage/make.profile ->
> ../../usr/portage/profiles/default/linux/amd64/13.0/desktop
>
> any suggestions?
>
>
>
>
Do you have make.defaults in the profile directory for your architecture?
As this is where ARCH is set.

grep ^ARCH /usr/portage/profiles/arch/amd64/make.defaults
ARCH="amd64"

Re: [gentoo-user] virtualbox: no x-server after kernel upgrade to 4.12.12-gentoo

[Alexander Kapshuk]

On Fri, Sep 15, 2017 at 5:47 PM, Alexander Puchmayr <
alexander.puchm...@linznet.at> wrote:

> Hi there,
>
> I'm using a gentoo-guest inside a virtual box on a Win10 host. The last
> somewhat working combination was kernel 4.4.39/virtualbox-5.1.24.
>
> When I update to kernel 4.12.12, the X-Server does not work anymore (I've
> also
> tried with 4.9.xx, same result -- no X)
>
> I used genkernel to compile the kernel, copied the previous 4.4.39-config
> from
> /proc/config.gz to /usr/src/linux-4.12.12-gentoo via zcat, and did no
> further
> changes; so nothing relevant should be changed, at least to my knowledge.
>
> After compilation of the kernel, required packages have been re-emerged:
> - app-emulation/virtualbox-guest-additions
> - x11-drivers/xf86-video-virtualbox
>
> Booting with 4.12.12:
> - sddm crashes with segfaults
> - Starting X from the command line: X complains missing EGL_MESA_drm
> EGL_MESA_drm_image required.
> : CommandLine Error: Option 'asan-instrument-assembly' registered more than
> once!
> LLVM ERROR: inconsistency in registered CommandLine options
> [??? No idea where this comes from :-( ]
>
>
> cat /var/log/Xorg.0.log
> [   793.159] (II) LoadModule: "vboxvideo"
> [   793.159] (II) Loading /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
> [   793.159] (II) Module vboxvideo: vendor="Oracle Corporation"
> [   793.159]compiled for 1.19.3, module version = 1.0.1
> [   793.159]Module class: X.Org Video Driver
> [   793.159]ABI class: X.Org Video Driver, version 23.0
> [   793.159] (**) Load address of symbol "VBOXVIDEO" is 0x7f3840a24380
> [   793.160] (II) VBoxVideo: guest driver for VirtualBox: vbox
> [   793.160] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> [   793.160] (II) FBDEV: driver for framebuffer: fbdev
> [   793.160] (II) VESA: driver for VESA chipsets: vesa
> [   793.160] (II) vboxvideo: kernel driver found, not loading.
> <-- !!
> [   793.160] (II) vboxvideo: kernel driver found, not loading.
> [   793.160] (II) modeset(0): using drv /dev/dri/card0
> [   793.160] (II) Loading sub module "glamoregl"
> [   793.160] (II) LoadModule: "glamoregl"
> [   793.160] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
> [   793.163] (II) Module glamoregl: vendor="X.Org Foundation"
> [   793.163]compiled for 1.19.3, module version = 1.0.0
> [   793.163]ABI class: X.Org ANSI C Emulation, version 0.4
> [   793.163] (II) glamor: OpenGL accelerated X.org driver based.
> [   793.217] (II) glamor: EGL version 1.4 (DRI2):
> [   793.217] EGL_MESA_drm_image required.
> [   793.218] (EE) modeset(0): glamor initialization failed
>
> dmesg shows:
> 5.269630] VBoxService 5.1.24 r117012 (verbosity: 0) linux.amd64 (Sep 15
> 2017
> 16:09:26) release log
>   00:00:00.46 main Log opened
> 2017-09-15T15:23:25.22099Z
> [5.269691] 00:00:00.000133 main OS Product: Linux
> [5.269717] 00:00:00.000165 main OS Release: 4.12.12-gentoo
> [5.269740] 00:00:00.000191 main OS Version: #1 SMP Fri Sep 15
> 15:33:45
> CEST 2017
> [5.269772] 00:00:00.000213 main Executable: /usr/sbin/vboxguest-
> service
>00:00:00.000214 main Process ID: 4275
>00:00:00.000215 main Package type: LINUX_64BITS_GENERIC
> (OSE)
> [5.272160] 00:00:00.002532 main 5.1.24 r117012 started. Verbose
> level
> = 0
> [7.780006] vboxvideo :00:02.0: fb0: vboxdrmfb frame buffer device
>
> Booting old 4.4.39 kernel[Just select old kernel in grub]
> - sddm shows login screen
> - /var/log/Xorg.0.log shows lots of lines regarding VBoxVideo driver.
> - dmesg does not show the  vboxvideo line from above
>
> Obviously, something is going terribly wrong here, and I'm getting stuck
> as I
> do not have any Idea where to start. The only thing that changed is a
> kernel
> upgrade and a rebuild of the virtual box modules.
>
> Any ideas?
>
> Thanks in advance,
> Alex
>
>
>
>
>
>
>
>
The Gentoo wiki article referenced below emphasizes the fact that certain
kernel config options need enabling in order to have proper hardware
emulation. So you want to make sure you have those enabled in your kernel
config. Then take it from there.

https://wiki.gentoo.org/wiki/VirtualBox

Re: [gentoo-user] Failed to load driver: Nouveau

[Alexander Kapshuk]

On Tue, Aug 29, 2017 at 5:58 PM, IceAmber <iceamber2...@gmail.com> wrote:
> yes, I have in the video group.
>
> the version of mesa is
>
>media-libs/mesa
>   Latest version available: 17.0.6
>   Latest version installed: 17.0.6
>   Size of files: 9,273 KiB
>   Homepage:  https://www.mesa3d.org/ https://mesa.freedesktop.org/
>   Description:   OpenGL-like graphic library for Linux
>   License:   MIT
>
> this is the first time to use the nouveau driver, I used the AMD video card,
> the model was HD6580, and the driver was radeon before.
>
>
> On Tue, Aug 29, 2017 at 2:28 PM, Alexander Kapshuk
> <alexander.kaps...@gmail.com> wrote:
>>
>> On Tue, Aug 29, 2017 at 12:35 PM, Alexander Kapshuk
>> <alexander.kaps...@gmail.com> wrote:
>> > On Mon, Aug 28, 2017 at 7:41 PM, Alexander Kapshuk
>> > <alexander.kaps...@gmail.com> wrote:
>> >> On Mon, Aug 28, 2017 at 6:30 PM, IceAmber <iceamber2...@gmail.com>
>> >> wrote:
>> >>> here is the result
>> >>>
>> >>> iceamber@localhost:~ $ lsmod | grep nouveau
>> >>> nouveau  1507328  2
>> >>> i2c_algo_bit   16384  1 nouveau
>> >>> drm_kms_helper118784  1 nouveau
>> >>> ttm77824  1 nouveau
>> >>> drm   282624  5 nouveau,ttm,drm_kms_helper
>> >>> agpgart32768  3 nouveau,ttm,drm
>> >>> led_class  16384  3 input_leds,hid_sony,nouveau
>> >>>
>> >>>
>> >>
>> >> Your nouveau kernel driver seems to be OK. That's good news.
>> >> The bad news is we're back to square one.
>> >>
>> >> It was glxinfo, which is a part of x11-apps/mesa-progs, that generated
>> >> the original error message.
>> >> So, perhaps, it is a mesa problem.
>> >>
>> >> Can you please try this command line and see what it outputs:
>> >> LIBGL_DEBUG=verbose glxgears
>> >
>> > This reference may help better debug your problem:
>> > https://nouveau.freedesktop.org/wiki/MesaDrivers/
>>
>> The Mesa drivers wiki page above says:
>>
>> nv50 and nvc0
>>
>> Make sure you are using at least Mesa 7.11, but please consider using
>> latest stable release. You have to use at least the 2.6.38 kernel or
>> you will encounter memory corruptions. For nvc0 hardware it's
>> recommended to use at least kernel 3.1.
>>
>> Bug reports for nv50 and nvc0 can be submitted by following the
>> general reporting guidelines. Please, also follow the About bugs and
>> problems section above.
>>
>> What version is your media-libs/mesa?
>>
>> Is this the first time you've run into this trouble using the nouveau
>> driver?
>> What driver did you use before with this piece of hardware proprietary
>> nvidia one, or nouveau?
>>
>

I don't have any further suggestions to make at the moment. Sorry.
Hopefully, someone else might be able to help.

Re: [gentoo-user] Failed to load driver: Nouveau

[Alexander Kapshuk]

On Tue, Aug 29, 2017 at 12:35 PM, Alexander Kapshuk
<alexander.kaps...@gmail.com> wrote:
> On Mon, Aug 28, 2017 at 7:41 PM, Alexander Kapshuk
> <alexander.kaps...@gmail.com> wrote:
>> On Mon, Aug 28, 2017 at 6:30 PM, IceAmber <iceamber2...@gmail.com> wrote:
>>> here is the result
>>>
>>> iceamber@localhost:~ $ lsmod | grep nouveau
>>> nouveau  1507328  2
>>> i2c_algo_bit   16384  1 nouveau
>>> drm_kms_helper118784  1 nouveau
>>> ttm77824  1 nouveau
>>> drm   282624  5 nouveau,ttm,drm_kms_helper
>>> agpgart32768  3 nouveau,ttm,drm
>>> led_class  16384  3 input_leds,hid_sony,nouveau
>>>
>>>
>>
>> Your nouveau kernel driver seems to be OK. That's good news.
>> The bad news is we're back to square one.
>>
>> It was glxinfo, which is a part of x11-apps/mesa-progs, that generated
>> the original error message.
>> So, perhaps, it is a mesa problem.
>>
>> Can you please try this command line and see what it outputs:
>> LIBGL_DEBUG=verbose glxgears
>
> This reference may help better debug your problem:
> https://nouveau.freedesktop.org/wiki/MesaDrivers/

The Mesa drivers wiki page above says:

nv50 and nvc0

Make sure you are using at least Mesa 7.11, but please consider using
latest stable release. You have to use at least the 2.6.38 kernel or
you will encounter memory corruptions. For nvc0 hardware it's
recommended to use at least kernel 3.1.

Bug reports for nv50 and nvc0 can be submitted by following the
general reporting guidelines. Please, also follow the About bugs and
problems section above.

What version is your media-libs/mesa?

Is this the first time you've run into this trouble using the nouveau driver?
What driver did you use before with this piece of hardware proprietary
nvidia one, or nouveau?

Re: [gentoo-user] Failed to load driver: Nouveau

[Alexander Kapshuk]

On Mon, Aug 28, 2017 at 7:41 PM, Alexander Kapshuk
<alexander.kaps...@gmail.com> wrote:
> On Mon, Aug 28, 2017 at 6:30 PM, IceAmber <iceamber2...@gmail.com> wrote:
>> here is the result
>>
>> iceamber@localhost:~ $ lsmod | grep nouveau
>> nouveau  1507328  2
>> i2c_algo_bit   16384  1 nouveau
>> drm_kms_helper118784  1 nouveau
>> ttm77824  1 nouveau
>> drm   282624  5 nouveau,ttm,drm_kms_helper
>> agpgart32768  3 nouveau,ttm,drm
>> led_class  16384  3 input_leds,hid_sony,nouveau
>>
>>
>
> Your nouveau kernel driver seems to be OK. That's good news.
> The bad news is we're back to square one.
>
> It was glxinfo, which is a part of x11-apps/mesa-progs, that generated
> the original error message.
> So, perhaps, it is a mesa problem.
>
> Can you please try this command line and see what it outputs:
> LIBGL_DEBUG=verbose glxgears

This reference may help better debug your problem:
https://nouveau.freedesktop.org/wiki/MesaDrivers/

Re: [gentoo-user] Failed to load driver: Nouveau

[Alexander Kapshuk]

On Mon, Aug 28, 2017 at 6:30 PM, IceAmber  wrote:
> here is the result
>
> iceamber@localhost:~ $ lsmod | grep nouveau
> nouveau  1507328  2
> i2c_algo_bit   16384  1 nouveau
> drm_kms_helper118784  1 nouveau
> ttm77824  1 nouveau
> drm   282624  5 nouveau,ttm,drm_kms_helper
> agpgart32768  3 nouveau,ttm,drm
> led_class  16384  3 input_leds,hid_sony,nouveau
>
>

Your nouveau kernel driver seems to be OK. That's good news.
The bad news is we're back to square one.

It was glxinfo, which is a part of x11-apps/mesa-progs, that generated
the original error message.
So, perhaps, it is a mesa problem.

Can you please try this command line and see what it outputs:
LIBGL_DEBUG=verbose glxgears

Re: [gentoo-user] Failed to load driver: Nouveau

[Alexander Kapshuk]

On Aug 28, 2017 17:57, "Alexander Kapshuk" <alexander.kaps...@gmail.com>
wrote:

On Mon, Aug 28, 2017 at 5:38 PM, IceAmber <iceamber2...@gmail.com> wrote:
> `du -a /lib/modules/`uname -r`/ | sed '/nouveau.ko$/!d;s/.*\t//'` as the
> same result
>
> On Mon, Aug 28, 2017 at 2:36 PM, IceAmber <iceamber2...@gmail.com> wrote:
>>
>> the result is
>> iceamber@localhost:~ $ modinfo nouveau | grep filename
>> filename:
>> /lib/modules/4.12.5-gentoo/kernel/drivers/gpu/drm/nouveau/nouveau.ko
>>
>> On Mon, Aug 28, 2017 at 2:17 PM, David Abbott <dabb...@gentoo.org> wrote:
>>>
>>> On Mon, Aug 28, 2017 at 10:00 AM, IceAmber <iceamber2...@gmail.com>
>>> wrote:
>>> > so, what should I do to locate the driver?
>>> >
>>> > On Mon, Aug 28, 2017 at 11:48 AM, Alexander Kapshuk
>>> > <alexander.kaps...@gmail.com> wrote:
>>> >>
>>> >> On Mon, Aug 28, 2017 at 2:41 PM, IceAmber <iceamber2...@gmail.com>
>>> >> wrote:
>>> >> > No, the error still there.
>>> >> > And the script `modinfo /lib/modules/`uname -r`/path/to/nouveau.ko`
>>> >> > shows
>>> >> > iceamber@localhost:~ $ modinfo /lib/modules/`uname
>>> >> > -r`/path/to/nouveau.ko
>>> >> > modinfo: ERROR: Module /lib/modules/4.12.5-gentoo/
path/to/nouveau.ko
>>> >> > not
>>> >> > found.
>>> >> >
>>> >>
>>> >> Note: 'path/to' in 'modinfo /lib/modules/`uname
>>> >> -r`/path/to/nouveau.ko' above needs substituting for the path to your
>>> >> nouveau.ko driver. Try locating it and rerun modinfo on it.
>>> >> Alternatively, you could try compiling nouveau into the kernel by
>>> >> setting CONFIG_DRM_NOUVEAU=y, reboot and see if that helps.
>>> >>
>>> >
>>>
>>> try;
>>> modinfo nouveau | grep filename
>>>
>>
>
Now run:
modinfo /lib/modules/4.12.5-gentoo/kernel/drivers/gpu/drm/nouveau/nouveau.ko


To make 100 per cent certain your driver is loaded, can you also run:
lsmod | grep nouveau

Re: [gentoo-user] Failed to load driver: Nouveau

[Alexander Kapshuk]

On Mon, Aug 28, 2017 at 5:38 PM, IceAmber <iceamber2...@gmail.com> wrote:
> `du -a /lib/modules/`uname -r`/ | sed '/nouveau.ko$/!d;s/.*\t//'` as the
> same result
>
> On Mon, Aug 28, 2017 at 2:36 PM, IceAmber <iceamber2...@gmail.com> wrote:
>>
>> the result is
>> iceamber@localhost:~ $ modinfo nouveau | grep filename
>> filename:
>> /lib/modules/4.12.5-gentoo/kernel/drivers/gpu/drm/nouveau/nouveau.ko
>>
>> On Mon, Aug 28, 2017 at 2:17 PM, David Abbott <dabb...@gentoo.org> wrote:
>>>
>>> On Mon, Aug 28, 2017 at 10:00 AM, IceAmber <iceamber2...@gmail.com>
>>> wrote:
>>> > so, what should I do to locate the driver?
>>> >
>>> > On Mon, Aug 28, 2017 at 11:48 AM, Alexander Kapshuk
>>> > <alexander.kaps...@gmail.com> wrote:
>>> >>
>>> >> On Mon, Aug 28, 2017 at 2:41 PM, IceAmber <iceamber2...@gmail.com>
>>> >> wrote:
>>> >> > No, the error still there.
>>> >> > And the script `modinfo /lib/modules/`uname -r`/path/to/nouveau.ko`
>>> >> > shows
>>> >> > iceamber@localhost:~ $ modinfo /lib/modules/`uname
>>> >> > -r`/path/to/nouveau.ko
>>> >> > modinfo: ERROR: Module /lib/modules/4.12.5-gentoo/path/to/nouveau.ko
>>> >> > not
>>> >> > found.
>>> >> >
>>> >>
>>> >> Note: 'path/to' in 'modinfo /lib/modules/`uname
>>> >> -r`/path/to/nouveau.ko' above needs substituting for the path to your
>>> >> nouveau.ko driver. Try locating it and rerun modinfo on it.
>>> >> Alternatively, you could try compiling nouveau into the kernel by
>>> >> setting CONFIG_DRM_NOUVEAU=y, reboot and see if that helps.
>>> >>
>>> >
>>>
>>> try;
>>> modinfo nouveau | grep filename
>>>
>>
>
Now run:
modinfo /lib/modules/4.12.5-gentoo/kernel/drivers/gpu/drm/nouveau/nouveau.ko

Re: [gentoo-user] Failed to load driver: Nouveau

[Alexander Kapshuk]

On Mon, Aug 28, 2017 at 5:00 PM, IceAmber <iceamber2...@gmail.com> wrote:
> so, what should I do to locate the driver?
>
> On Mon, Aug 28, 2017 at 11:48 AM, Alexander Kapshuk
> <alexander.kaps...@gmail.com> wrote:
>>
>> On Mon, Aug 28, 2017 at 2:41 PM, IceAmber <iceamber2...@gmail.com> wrote:
>> > No, the error still there.
>> > And the script `modinfo /lib/modules/`uname -r`/path/to/nouveau.ko`
>> > shows
>> > iceamber@localhost:~ $ modinfo /lib/modules/`uname
>> > -r`/path/to/nouveau.ko
>> > modinfo: ERROR: Module /lib/modules/4.12.5-gentoo/path/to/nouveau.ko not
>> > found.
>> >
>>
>> Note: 'path/to' in 'modinfo /lib/modules/`uname
>> -r`/path/to/nouveau.ko' above needs substituting for the path to your
>> nouveau.ko driver. Try locating it and rerun modinfo on it.
>> Alternatively, you could try compiling nouveau into the kernel by
>> setting CONFIG_DRM_NOUVEAU=y, reboot and see if that helps.
>>
>
du -a /lib/modules/`uname -r`/ | sed '/nouveau.ko$/!d;s/.*\t//'

Re: [gentoo-user] Failed to load driver: Nouveau

[Alexander Kapshuk]

On Mon, Aug 28, 2017 at 2:41 PM, IceAmber  wrote:
> No, the error still there.
> And the script `modinfo /lib/modules/`uname -r`/path/to/nouveau.ko` shows
> iceamber@localhost:~ $ modinfo /lib/modules/`uname -r`/path/to/nouveau.ko
> modinfo: ERROR: Module /lib/modules/4.12.5-gentoo/path/to/nouveau.ko not
> found.
>

Note: 'path/to' in 'modinfo /lib/modules/`uname
-r`/path/to/nouveau.ko' above needs substituting for the path to your
nouveau.ko driver. Try locating it and rerun modinfo on it.
Alternatively, you could try compiling nouveau into the kernel by
setting CONFIG_DRM_NOUVEAU=y, reboot and see if that helps.

Re: [gentoo-user] Failed to load driver: Nouveau

[Alexander Kapshuk]

On Sun, Aug 27, 2017 at 8:24 PM, IceAmber <iceamber2...@gmail.com> wrote:
> iceamber@localhost:~ $ grep NOUVEAU /usr/src/linux/.config
> CONFIG_DRM_NOUVEAU=m
> CONFIG_NOUVEAU_DEBUG=5
> CONFIG_NOUVEAU_DEBUG_DEFAULT=3
> CONFIG_DRM_NOUVEAU_BACKLIGHT=y
>
> iceamber@localhost:~ $ grep -E 'nvidia|VIDEO_CARDS' /etc/portage/make.conf
> VIDEO_CARDS="nouveau"
>
> here is the `grep -si nouveau /var/log/*`
>
> I have rebuilt the xorg-server, it is built for kernel 4.12.5 now.
> And I have set the USEs of "gallium" and "video_cards_nouveau"
>
> On Sun, Aug 27, 2017 at 4:54 PM, Alexander Kapshuk
> <alexander.kaps...@gmail.com> wrote:
>>
>> On Sun, Aug 27, 2017 at 5:49 PM, Alexander Kapshuk
>> <alexander.kaps...@gmail.com> wrote:
>> > On Sun, Aug 27, 2017 at 5:45 PM, Alexander Kapshuk
>> > <alexander.kaps...@gmail.com> wrote:
>> >> On Sun, Aug 27, 2017 at 2:27 PM, IceAmber <iceamber2...@gmail.com>
>> >> wrote:
>> >>> I have tried, but the same result
>> >>>
>> >>> On Sun, Aug 27, 2017 at 10:04 AM, Adam Carter <adamcart...@gmail.com>
>> >>> wrote:
>> >>>>>
>> >>>>> yes, here is the eselect
>> >>>>
>> >>>>
>> >>>> When i have X problems i can resolve i run emerge -av
>> >>>> @x11-module-rebuild
>> >>>> xorg-server mesa but its generally an act of desperation after
>> >>>> running out
>> >>>> of intelligent options.
>> >>>
>> >>>
>> >>
>> >> Your xorg-server was built for kernel 4.9.34.
>> >> [24.014] Build Operating System: Linux 4.9.34-gentoo x86_64 Gentoo
>> >> [24.014] Current Operating System: Linux localhost 4.12.5-gentoo
>> >> #10 SMP Sat Aug 26 13:15:20 UTC 2017 x86_64
>> >>
>> >> Might be a good idea to rebuild x11-base/xorg-server for your current
>> >> kernel.
>> >>
>> >> What's the output of the command lines below?
>> >> grep NOUVEAU linux/.config
>> >> grep -E 'nvidia|VIDEO_CARDS' /etc/portage/make.conf
>> >
>> > This one too please:
>> > grep -si nouveau /var/log/*
>>
>> Also, let's make sure mesa has the USE flags below enabled:
>>
>> equery -q u mesa | grep -E 'gallium|nouveau'
>> +gallium
>> +video_cards_nouveau
>>
>

I'm not seeing these errors in your Xorg.0.log any more:
[25.361] (EE) AIGLX error: Calling driver entry point failed
[25.375] (EE) AIGLX: reverting to software rendering

Are you still getting the error message about the nouveau driver not
being loaded when running glxinfo or glxgears?
If you are, what's the output of:
lsmod nouveau
modinfo /lib/modules/`uname -r`/path/to/nouveau.ko

Re: [gentoo-user] Failed to load driver: Nouveau

[Alexander Kapshuk]

On Sun, Aug 27, 2017 at 5:49 PM, Alexander Kapshuk
<alexander.kaps...@gmail.com> wrote:
> On Sun, Aug 27, 2017 at 5:45 PM, Alexander Kapshuk
> <alexander.kaps...@gmail.com> wrote:
>> On Sun, Aug 27, 2017 at 2:27 PM, IceAmber <iceamber2...@gmail.com> wrote:
>>> I have tried, but the same result
>>>
>>> On Sun, Aug 27, 2017 at 10:04 AM, Adam Carter <adamcart...@gmail.com> wrote:
>>>>>
>>>>> yes, here is the eselect
>>>>
>>>>
>>>> When i have X problems i can resolve i run emerge -av @x11-module-rebuild
>>>> xorg-server mesa but its generally an act of desperation after running out
>>>> of intelligent options.
>>>
>>>
>>
>> Your xorg-server was built for kernel 4.9.34.
>> [24.014] Build Operating System: Linux 4.9.34-gentoo x86_64 Gentoo
>> [24.014] Current Operating System: Linux localhost 4.12.5-gentoo
>> #10 SMP Sat Aug 26 13:15:20 UTC 2017 x86_64
>>
>> Might be a good idea to rebuild x11-base/xorg-server for your current kernel.
>>
>> What's the output of the command lines below?
>> grep NOUVEAU linux/.config
>> grep -E 'nvidia|VIDEO_CARDS' /etc/portage/make.conf
>
> This one too please:
> grep -si nouveau /var/log/*

Also, let's make sure mesa has the USE flags below enabled:

equery -q u mesa | grep -E 'gallium|nouveau'
+gallium
+video_cards_nouveau

Re: [gentoo-user] Failed to load driver: Nouveau

[Alexander Kapshuk]

On Sun, Aug 27, 2017 at 5:45 PM, Alexander Kapshuk
<alexander.kaps...@gmail.com> wrote:
> On Sun, Aug 27, 2017 at 2:27 PM, IceAmber <iceamber2...@gmail.com> wrote:
>> I have tried, but the same result
>>
>> On Sun, Aug 27, 2017 at 10:04 AM, Adam Carter <adamcart...@gmail.com> wrote:
>>>>
>>>> yes, here is the eselect
>>>
>>>
>>> When i have X problems i can resolve i run emerge -av @x11-module-rebuild
>>> xorg-server mesa but its generally an act of desperation after running out
>>> of intelligent options.
>>
>>
>
> Your xorg-server was built for kernel 4.9.34.
> [24.014] Build Operating System: Linux 4.9.34-gentoo x86_64 Gentoo
> [24.014] Current Operating System: Linux localhost 4.12.5-gentoo
> #10 SMP Sat Aug 26 13:15:20 UTC 2017 x86_64
>
> Might be a good idea to rebuild x11-base/xorg-server for your current kernel.
>
> What's the output of the command lines below?
> grep NOUVEAU linux/.config
> grep -E 'nvidia|VIDEO_CARDS' /etc/portage/make.conf

This one too please:
grep -si nouveau /var/log/*

Re: [gentoo-user] Failed to load driver: Nouveau

[Alexander Kapshuk]

On Sun, Aug 27, 2017 at 2:27 PM, IceAmber  wrote:
> I have tried, but the same result
>
> On Sun, Aug 27, 2017 at 10:04 AM, Adam Carter  wrote:
>>>
>>> yes, here is the eselect
>>
>>
>> When i have X problems i can resolve i run emerge -av @x11-module-rebuild
>> xorg-server mesa but its generally an act of desperation after running out
>> of intelligent options.
>
>

Your xorg-server was built for kernel 4.9.34.
[24.014] Build Operating System: Linux 4.9.34-gentoo x86_64 Gentoo
[24.014] Current Operating System: Linux localhost 4.12.5-gentoo
#10 SMP Sat Aug 26 13:15:20 UTC 2017 x86_64

Might be a good idea to rebuild x11-base/xorg-server for your current kernel.

What's the output of the command lines below?
grep NOUVEAU linux/.config
grep -E 'nvidia|VIDEO_CARDS' /etc/portage/make.conf

Re: [gentoo-user] Something started muting the sound

[Alexander Kapshuk]

On Sat, Aug 12, 2017 at 4:49 PM, Robin Atwood  wrote:
> I have a Thinkpad T410 where, after I installed Gentoo on it, everything
> "just worked (TM)". The sound is via the bog-standard Intel chips on the
> mobo and uses the hda_intel drivers. I didn't use the TP for a long time,
> just periodically updating Gentoo, but when I eventually did try to use it
> the sound was muted. This means I shut down the X server to remove
> complications from the desktop and from the console aplay doesn't produce
> any sound. Everything looks normal, driver modules loaded, alsamixer shows
> the usual output, channels all active. I booted to a windows partition and
> the sound works, so the hardware is OK. The very weird thing is if I put the
> TP to sleep with acpitool and wake it up again, the sound works for about 60
> seconds and then dies. There is nothing in the message log at all when this
> happens. I upgraded the kernel but that didn't help.
>
>
>
> This problem has been dragging on for some years and I am contemplating a
> complete re-install from scratch. But before I do that does anyone have any
> idea what I could try?
>
>
>
> TIA
>
> Robin
>
>
>
> --
>
> --
>
> Robin Atwood.
>
>
>
> "Ship me somewheres east of Suez, where the best is like the worst,
>
> Where there ain't no Ten Commandments an' a man can raise a thirst"
>
> from "Mandalay" by Rudyard Kipling
>
> --
>
>

What's the output of these command lines?
(1). lspci -vnn | sed '/Audio/,/driver/!d'

(2). grep -Ei '^[^#]*(snd|hda)' linux/.config

(3). rc-update show | grep alsa

(4). grep HDA /var/log/dmesg

(5). Postinst message for alsa-utils:
pkg_postinst() {
if [[ -z ${REPLACING_VERSIONS} ]]; then
elog
elog "To take advantage of the init script, and automate the process of"
elog "saving and restoring sound-card mixer levels you should"
elog "add alsasound to the boot runlevel. You can do this as"
elog "root like so:"
elog "# rc-update add alsasound boot"
ewarn
ewarn "The ALSA core should be built into the kernel or loaded through other"
ewarn "means. There is no longer any modular auto(un)loading in alsa-utils."
fi
}

(6). Also, if you check out the Gentoo wiki article on how to set up ALSA.
See if there's anything you might've overlooked when setting it up:
https://wiki.gentoo.org/wiki/ALSA

Re: [gentoo-user] Why bash script, that works in "Debian", does not work on "Gentoo" install CD?

[Alexander Kapshuk]

On Jul 29, 2017 12:27, "Ста Деюс"  wrote:

Hi, Neil.


On Fri, 28 Jul 2017 21:43:53 +0100, you wrote:

> > How do you know that the contents of the script are not relevant
> > when you
> don't know what the problem is? It is also useful to know the exact

Mathematics (mother of computers) answers: 1+1=2. -- Meaning: same
script w/ the same bash gets same execution.

> version of bash in use on each system. There are subtle differences,
> and bugs, between bash versions. Your script may be tripping up on
> one of these.

Alright. Here is an example of the problematic line from the point
of view of "Gentoo's" bash:

read 'Enter device (like /dev/sd(a1,b1,...): ' device

Until i remove the brackets, "Gentoo's" bash keeps error messaging.


Thank you for your time,
Sthu.

The line from your script above doesn't seem to have a matching right hand
side bracket.
Try running your script in trace mode like so, bash -x script, to further
troubleshoot the issue.

Re: [gentoo-user] Can't emerge --sync

[Alexander Kapshuk]

On Sat, Jul 15, 2017 at 1:00 PM, Peter Humphrey  wrote:
> Hello list,
>
> Today I get this:
>
> # emerge --sync
 Syncing repository 'gentoo' into '/usr/portage'...
> /usr/bin/git pull
> remote: Counting objects: 25, done.
> remote: Compressing objects: 100% (9/9), done.
> remote: Total 25 (delta 15), reused 25 (delta 15), pack-reused 0
> Unpacking objects: 100% (25/25), done.
> From https://github.com/gentoo-mirror/gentoo
>c80ef88a736..b9cb9e0b42e  stable -> origin/stable
> Updating c5ec29f674c..b9cb9e0b42e
> error: Your local changes to the following files would be overwritten by
> merge:
> metadata/layout.conf
> Please commit your changes or stash them before you merge.
> Aborting
> !!! git pull error in /usr/portage
>
> I can't imagine I'd ever make any changes to that file, especially not using
> git, but I tried reverting to backups of /var and /usr/portage from a week
> ago, but I still get the same error. Using backups from two weeks ago also
> made no difference.
>
> I sync and update every day, with never a problem like this before.
>
> Can anyone see what else I should try? Should I just delete the offending
> file? (I'll get some coffee meanwhile...)
>
> --
> Regards
> Peter
>
>
git-checkout(1) has a '--theirs' option that might do the trick there:

The index may contain unmerged entries because of a previous failed
merge. By default, if you try to check out such an entry from the
index, the checkout operation will fail and nothing will be checked
out.
...
You could try:
git checkout --theirs metadata/layout.conf

Re: [gentoo-user] genkernel iwlwifi WiFi driver

[Alexander Kapshuk]

On Sat, Jul 15, 2017 at 12:20 PM, Radoje Stojisic
 wrote:
> Hello everyone,
>
> I've installed Gentoo on my ThinkPad T460p couple of times. For some reason
> I can't get the WiFi working. I did the installation with SystemRescueCD
> because I needed working WiFi for the install.
>
> So here comes the question:
>
> I've installed the Genkernel. Does Genkernel enables the iwlwifi driver
> automatically? Or do I need the modify the kernel on my own? I've installed
> Gentoo with KDE. iwconfig showed no wifi interface.
>
>
> Thanks for any advice.
>
> Greetings
>
> -Radi
>
>

As already pointed out, this driver does require firmware to run. See below.

drivers/net/wireless/intel/iwlwifi/Kconfig:1,31
config IWLWIFI
tristate "Intel Wireless WiFi Next Gen AGN -
Wireless-N/Advanced-N/Ultimate-N (iwlwifi) "
depends on PCI && MAC80211 && HAS_IOMEM
select FW_LOADER
---help---
 Select to build the driver supporting the:

 Intel Wireless WiFi Link Next-Gen AGN

 This option enables support for use with the following hardware:
Intel Wireless WiFi Link 6250AGN Adapter
Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
Intel WiFi Link 1000BGN
Intel Wireless WiFi 5150AGN
Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
Intel 6005 Series Wi-Fi Adapters
Intel 6030 Series Wi-Fi Adapters
Intel Wireless WiFi Link 6150BGN 2 Adapter
Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN)
Intel 2000 Series Wi-Fi Adapters
Intel 7260 Wi-Fi Adapter
Intel 3160 Wi-Fi Adapter
Intel 7265 Wi-Fi Adapter
Intel 8260 Wi-Fi Adapter
Intel 3165 Wi-Fi Adapter


 This driver uses the kernel's mac80211 subsystem.

 In order to use this driver, you will need a firmware
 image for it.

Also, see this Gentoo wiki article for instructions on how to set up
your driver:
https://wiki.gentoo.org/wiki/Iwlwifi

Re: [gentoo-user] Problem starting VM image on QEMU

[Alexander Kapshuk]

On Fri, Jul 14, 2017 at 7:43 PM, Mick <michaelkintz...@gmail.com> wrote:
> On Friday 14 Jul 2017 19:02:55 Alexander Kapshuk wrote:
>> On Fri, Jul 14, 2017 at 6:31 PM, Mick <michaelkintz...@gmail.com> wrote:
>
>> > Trying to start it gives:
>> >
>> > $ ./coreos_production_qemu.sh -a /home/michael/.ssh/id_rsa.pub -p  --
>> > -
>> > curses
>> > -bash: ./coreos_production_qemu.sh: Permission denied
>
>> Try running the script in trace mode as yourself:
>> bash -x coreos_production_qemu.sh etc.
>>
>> See if that reveals anything useful.
>
> Ha!  What do you know?  Running it with bash -x in front I was able to execute
> it ... hmmm ... OK ... it seems the partition had been mounted as noexec ...
>
> /dev/sda11 on /data type ext4 (rw,nosuid,nodev,noexec,noatime,data=ordered)
> none on /run/user/1000 type tmpfs (rw,relatime,mode=700,uid=1000)
>
> A clear case of mea culpa!
>
> Thanks for helping me spot this.  :-)
>
> --
> Regards,
> Mick

No worries at all.
Good to hear it worked out for you.

Re: [gentoo-user] Problem starting VM image on QEMU

[Alexander Kapshuk]

On Fri, Jul 14, 2017 at 6:31 PM, Mick  wrote:
> I have followed the gentoo wiki to install and setup QEMU:
>
> https://wiki.gentoo.org/wiki/QEMU
>
>
> Then I tried to start up a CoreOS image following this guide, but I must be
> doing something wrong:
>
> https://coreos.com/os/docs/latest/booting-with-qemu.html
>
>
> This is the script's ownership and access rights:
>
> $ stat coreos_production_qemu.sh
>   File: 'coreos_production_qemu.sh'
>   Size: 6635Blocks: 24 IO Block: 4096   regular file
> Device: 80bh/2059d  Inode: 13631491Links: 1
> Access: (0755/-rwxr-xr-x)  Uid: ( 1000/ michael)   Gid: ( 1002/ michael)
> Access: 2017-07-14 09:21:18.0 +0100
> Modify: 2017-07-06 19:41:30.0 +0100
> Change: 2017-07-14 14:38:55.104862083 +0100
>  Birth: -
>
> Trying to start it gives:
>
> $ ./coreos_production_qemu.sh -a /home/michael/.ssh/id_rsa.pub -p  -- -
> curses
> -bash: ./coreos_production_qemu.sh: Permission denied
>
> Any idea what permissions it refers to?  I have not tried to run the above as
> root.
> --
> Regards,
> Mick

Try running the script in trace mode as yourself:
bash -x coreos_production_qemu.sh etc.

See if that reveals anything useful.

Re: [gentoo-user] Xserver: /dev/dri/card0 -- no such file.

[Alexander Kapshuk]

On Sat, Jul 8, 2017 at 9:05 AM, Ста Деюс  wrote:
> Hi.
>
> I'm fighting already days the problem of "/dev/dri/card0 -- no such
> file" (old AGP card, NVIDIA GeForce4 MX 440) -- as x-server states in
> its log file.
>
> I have installed my system w/ hardened profile, it's being 32bit-system,
> and then added x-programs to use it as desktop (i didn't install desktop
> profile). Also, i didn't notice, that i set up testing version of the
> distro (~86), and now want not to recompile all it to turn to stable
> (86).
>
> The problem lays -- as i suppose -- in the kernel configuration that
> does not create the /dev/dri/card0 device, required by x-server. I
> exhausted all my ideas on which options to turn on to make it create
> the device. I even compiled the general kernel -- but it was not
> sufficient for that too.
>
> So, do you have any idea on which kernel's configuration option lets
> kernel to create such a device?
>
> Thank you for your time,
> Sthu.
>

On my system, card0 is set up by the nouveau driver:

:; ls -l /dev/dri/card0
crw-rw+ 1 root video 226, 0 Jul  8 08:28 /dev/dri/card0

:; ls /sys/class/drm/card0/device/driver/module/drivers/
pci:nouveau

Hope this helps.

Re: [gentoo-user] Anjuta - Segmentation Fault

[Alexander Kapshuk]

On Fri, Jul 7, 2017 at 2:14 PM, Hogren  wrote:
> Hello !
>
>
> I try to develop with Anjuta.
>
> When I run it, many times it works, many times it won't to start.
>
> I have a lot of WARNING, and several CRITICAL messages :
>
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :2:30: The
> style property GtkWidget:focus-line-width is deprecated and shouldn't be
> used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :3:27: The
> style property GtkWidget:focus-padding is deprecated and shouldn't be
> used anymore. It will be removed in a future version
>
> (anjuta:5134): GLib-GObject-CRITICAL **:
> g_cclosure_marshal_VOID__POINTER: assertion 'n_param_values == 2' failed
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :2:28: The
> style property GtkButton:default-border is deprecated and shouldn't be
> used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :3:36: The
> style property GtkButton:default-outside-border is deprecated and
> shouldn't be used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :4:25: The
> style property GtkButton:inner-border is deprecated and shouldn't be
> used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :5:30: The
> style property GtkWidget:focus-line-width is deprecated and shouldn't be
> used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :6:27: The
> style property GtkWidget:focus-padding is deprecated and shouldn't be
> used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **:
> (/var/tmp/portage/x11-libs/gtk+-3.22.15/work/gtk+-3.22.15/gtk/gtkicontheme.c:2184):gtk_icon_theme_choose_icon:
> runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)
>
> (anjuta:5134): GLib-GObject-CRITICAL **:
> g_cclosure_marshal_VOID__POINTER: assertion 'n_param_values == 2' failed
>
> (anjuta:5134): GLib-GObject-CRITICAL **:
> g_cclosure_marshal_VOID__POINTER: assertion 'n_param_values == 2' failed
>
> (anjuta:5134): GLib-GObject-CRITICAL **:
> g_cclosure_marshal_VOID__POINTER: assertion 'n_param_values == 2' failed
>
> (anjuta:5134): Gtk-WARNING **:
> (/var/tmp/portage/x11-libs/gtk+-3.22.15/work/gtk+-3.22.15/gtk/gtkicontheme.c:2184):gtk_icon_theme_choose_icon:
> runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)
>
> (anjuta:5134): Gtk-WARNING **:
> (/var/tmp/portage/x11-libs/gtk+-3.22.15/work/gtk+-3.22.15/gtk/gtkicontheme.c:2184):gtk_icon_theme_choose_icon:
> runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)
>
> (anjuta:5134): Gtk-WARNING **:
> (/var/tmp/portage/x11-libs/gtk+-3.22.15/work/gtk+-3.22.15/gtk/gtkicontheme.c:2184):gtk_icon_theme_choose_icon:
> runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :11:31: The
> style property GtkButton:default-border is deprecated and shouldn't be
> used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :12:39: The
> style property GtkButton:default-outside-border is deprecated and
> shouldn't be used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :13:29: The
> style property GtkButton:inner-border is deprecated and shouldn't be
> used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :27:30: The
> style property GtkComboBox:arrow-size is deprecated and shouldn't be
> used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :32:31: The
> style property GtkButton:default-border is deprecated and shouldn't be
> used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :33:39: The
> style property GtkButton:default-outside-border is deprecated and
> shouldn't be used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :34:29: The
> style property GtkButton:inner-border is deprecated and shouldn't be
> used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :38:30: The
> style property GtkToolbar:shadow-type is deprecated and shouldn't be
> used anymore. It will be removed in a future version
>
> (anjuta:5134): Gtk-WARNING **: Theme parsing error: :45:30: The
> style property GtkToolbar:shadow-type is deprecated and shouldn't be
> used anymore. It will be removed in a future version
> GladeUI-Message: 1 missing displayable value for GtkWidget::events
> GladeUI-Message: No displayable values for property GtkMenu::anchor-hints
> GladeUI-Message: 1 missing displayable value for
> GtkAboutDialog::license-type
> 

Re: [gentoo-user] glibc-2.24-r2 failed (install phase)

[Alexander Kapshuk]

On Mon, Jun 19, 2017 at 7:43 PM,  <tu...@posteo.de> wrote:
> On 06/19 11:55, Alexander Kapshuk wrote:
>> On Mon, Jun 19, 2017 at 6:21 AM,  <tu...@posteo.de> wrote:
>> > On 06/15 05:56, tu...@posteo.de wrote:
>> >> Hi,
>> >>
>> >> While updateing glibc-2.24-r2 failed to install.
>> >>
>> >> These are the last few lines of that process:
>> >>
>> >> 
>> >> al/execinfo.c.texi 
>> >> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/add.c.texi
>> >>  
>> >> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/summary.texi
>> >>  
>> >> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/pkgvers.texi
>> >>  | sort;\
>> >>  echo "@end direntry") > 
>> >> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/dir-add.texi.new
>> >> mv -f 
>> >> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/dir-add.texi.new
>> >>  
>> >> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/dir-add.texi
>> >> LANGUAGE=C LC_ALL=C makeinfo -P 
>> >> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/
>> >>  
>> >> --output=/var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/libc.info
>> >>  libc.texinfo
>> >> libc.texinfo:6: warning: @codequotebacktick should only appear at the 
>> >> beginning of a line
>> >> libc.texinfo:6: warning: @codequoteundirected should only appear at the 
>> >> beginning of a line
>> >> libc.texinfo:6: warning: @codequoteundirected should not appear in 
>> >> @codequotebacktick
>> >> libc.texinfo:6: expected @codequoteundirected on or off, not `on' require'
>> >> libc.texinfo:6: superfluous argument to @codequotebacktick
>> >> libc.texinfo:6: expected @codequotebacktick on or off, not `on' and ''
>> >> make[2]: *** [Makefile:144: 
>> >> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/libc.info]
>> >>  Error 1
>> >> make[2]: Leaving directory 
>> >> '/var/tmp/portage/sys-libs/glibc-2.24-r2/work/glibc-2.24/manual'
>> >> make[1]: *** [Makefile:215: manual/subdir_install] Error 2
>> >> make[1]: Leaving directory 
>> >> '/var/tmp/portage/sys-libs/glibc-2.24-r2/work/glibc-2.24'
>> >> make: *** [Makefile:12: install] Error 2
>> >>  * ERROR: sys-libs/glibc-2.24-r2::gentoo failed (install phase):
>> >>  *   emake failed
>> >>  *
>> >>
>> >> If anything more is wanted, I will be happy to post the wanted logs.
>> >> But I want to prevent to logbomnb the mailinglist in beforehand... ;)
>> >>
>> >> Cheers
>> >> Meino
>> >>
>> >
>> > Hi,
>> >
>> > Is there any solution for this problem ?
>> > Does anyone else has the same or similiar problems with this system
>> > update?
>> >
>> > Cheers
>> > Meino
>> >
>>
>> What is the version of your gcc compiler?
>> The ebuild has this info on the version of gcc:
>> https://gitweb.gentoo.org/repo/gentoo.git/plain/sys-libs/glibc/glibc-2.24-r2.ebuild
>> src_prepare() {
>> ...
>>
>> case $(gcc-fullversion) in
>> 4.8.[0-3]|4.9.0)
>> eerror "You need to switch to a newer compiler; gcc-4.8.[0-3] and
>> gcc-4.9.0 miscompile"
>> eerror "glibc.  See https://bugs.gentoo.org/547420 for details."
>> die "need to switch compilers #547420"
>> ;;
>> esac
>> ...
>> }
>>
>
> The gcc on my system says:
>
> gcc (Gentoo 5.4.0-r3 p1.3, pie-0.6.5) 5.4.0
> Copyright (C) 2015 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> if asked...
>
> Cheers
> mcc
>
>
>

See if this post [1] helps:
[1]. https://forums.gentoo.org/viewtopic-t-789652-start-0.html

Re: [gentoo-user] glibc-2.24-r2 failed (install phase)

[Alexander Kapshuk]

On Mon, Jun 19, 2017 at 6:21 AM,   wrote:
> On 06/15 05:56, tu...@posteo.de wrote:
>> Hi,
>>
>> While updateing glibc-2.24-r2 failed to install.
>>
>> These are the last few lines of that process:
>>
>> 
>> al/execinfo.c.texi 
>> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/add.c.texi
>>  
>> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/summary.texi
>>  
>> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/pkgvers.texi
>>  | sort;\
>>  echo "@end direntry") > 
>> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/dir-add.texi.new
>> mv -f 
>> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/dir-add.texi.new
>>  
>> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/dir-add.texi
>> LANGUAGE=C LC_ALL=C makeinfo -P 
>> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/
>>  
>> --output=/var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/libc.info
>>  libc.texinfo
>> libc.texinfo:6: warning: @codequotebacktick should only appear at the 
>> beginning of a line
>> libc.texinfo:6: warning: @codequoteundirected should only appear at the 
>> beginning of a line
>> libc.texinfo:6: warning: @codequoteundirected should not appear in 
>> @codequotebacktick
>> libc.texinfo:6: expected @codequoteundirected on or off, not `on' require'
>> libc.texinfo:6: superfluous argument to @codequotebacktick
>> libc.texinfo:6: expected @codequotebacktick on or off, not `on' and ''
>> make[2]: *** [Makefile:144: 
>> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/libc.info]
>>  Error 1
>> make[2]: Leaving directory 
>> '/var/tmp/portage/sys-libs/glibc-2.24-r2/work/glibc-2.24/manual'
>> make[1]: *** [Makefile:215: manual/subdir_install] Error 2
>> make[1]: Leaving directory 
>> '/var/tmp/portage/sys-libs/glibc-2.24-r2/work/glibc-2.24'
>> make: *** [Makefile:12: install] Error 2
>>  * ERROR: sys-libs/glibc-2.24-r2::gentoo failed (install phase):
>>  *   emake failed
>>  *
>>
>> If anything more is wanted, I will be happy to post the wanted logs.
>> But I want to prevent to logbomnb the mailinglist in beforehand... ;)
>>
>> Cheers
>> Meino
>>
>
> Hi,
>
> Is there any solution for this problem ?
> Does anyone else has the same or similiar problems with this system
> update?
>
> Cheers
> Meino
>

What is the version of your gcc compiler?
The ebuild has this info on the version of gcc:
https://gitweb.gentoo.org/repo/gentoo.git/plain/sys-libs/glibc/glibc-2.24-r2.ebuild
src_prepare() {
...

case $(gcc-fullversion) in
4.8.[0-3]|4.9.0)
eerror "You need to switch to a newer compiler; gcc-4.8.[0-3] and
gcc-4.9.0 miscompile"
eerror "glibc.  See https://bugs.gentoo.org/547420 for details."
die "need to switch compilers #547420"
;;
esac
...
}

Re: [gentoo-user] texlive-core dependency conflict

[Alexander Kapshuk]

On Sun, Jun 18, 2017 at 3:09 AM, Lasse Pouru
 wrote:
> Any way to get around this? I've already tried removing both the cjk and
> xetex USE flags, running emerge -c, unmerging and remerging texlive-core
> etc. I do actually want both the cjk and the xetex packages installed,
> and this seems to be mostly an aesthetic issue since the version of
> texlive-core I have installed is the latest (2016-r5).
>
> I guess I'm really just wondering if my LaTeX installation is messed up
> somehow and if there's something I could do to prevent errors like this
> in the future.
>
> Here's the error message:
>
> WARNING: One or more updates/rebuilds have been skipped due to a
> dependency conflict:
>
> app-text/texlive-core:0
>
>   (app-text/texlive-core-2016-r5:0/0::gentoo, ebuild scheduled for
>   merge) conflicts with
> >=app-text/texlive-core-2010[cjk] required by
>  ^^^
>   (dev-texlive/texlive-langcjk-2016:0/0::gentoo, installed)
>
> >=app-text/texlive-core-2010[xetex] required by
>  ^
>   (dev-texlive/texlive-xetex-2016:0/0::gentoo, installed)
>
> - Lasse
>

Please search this mailing list's archive. This issue has recently
been discussed and a few solutions suggested.

Re: [gentoo-user] emerge update problem with blocking packages

[Alexander Kapshuk]

On Wed, Jun 14, 2017 at 8:14 AM, Quico Jurado  wrote:
> Hello list!
>
> I'm trying to update @world, and I'm getting a problem with blocking
> packages which I'm not sure if I understand. It looks like a circular
> blocking problem, but not sure.
>
> Here's what emerge is telling me:
>
> [ebuild U  ] app-text/texlive-2016::gentoo [2015::gentoo] USE="X context
> detex dvi2tty extra graphics humanities jadetex luatex omega png pstricks
> publishers science tex4ht texi2html truetype xetex xindy xml -cjk -epspdf
> -games -metapost -music -pdfannotextractor" L10N="-af -ar -as -bg -bn -br
> -ca -cs -cy -da -de -el -en -en-GB -eo -es -et -eu -fa -fi -fr -ga -gl -gu
> -he -hi -hr -hsb -hu -hy -ia -id -is -it -ja -kn -ko -la -lo -lt -lv -ml -mn
> -mr -nb -nl -nn -no -or -pa -pl -pt -rm -ro -ru -sa -sco -sk -sl -sq -sr -sv
> -ta -te -th -tk -tr -uk -vi -zh" 0 KiB
> [blocks B  ]  (" dev-texlive/texlive-basic-2016)
> [blocks B  ]  (" dev-texlive/texlive-latex-2016)
> [blocks B  ]  (" dev-texlive/texlive-langgerman-2016, dev-texlive/texlive-langcyrillic-2016)
> [blocks B  ]  (" dev-texlive/texlive-basic-2016)
> [blocks B  ]  (" dev-texlive/texlive-basic-2016)
> [blocks B  ]  (" dev-texlive/texlive-basic-2016)
>
> Total: 40 packages (36 upgrades, 1 new, 1 in new slot, 2 reinstalls, 2
> uninstalls), Size of downloads: 500,112 KiB
> Conflict: 9 blocks (6 unsatisfied)
>
>  * Error: The above package list contains packages which cannot be
>  * installed at the same time on the same system.
>
>
> And this is the update command that I'm running:
>
> emerge -uvaND --with-bdeps=y --backtrack=100 @world
>
> Any help is much appreciated.
>
> Cheers!

I ended up removing some of the packages reported as blocking other
packages, tagged 2015, as suggested in the wiki article [1], and was
able to proceed with the update.
[1] https://wiki.gentoo.org/wiki/Handbook:Parts/Working/Portage#Blocked_packages

Re: [gentoo-user] Imdb videos won't play in Chromium

[Alexander Kapshuk]

With chromium recompiled with the 'system-ffmpeg' USE flag disabled, I
can now play imdb.com videos without any trouble.

The Arch Linux PKGBUILD for chromium has this system library disabled
as well. See 
https://git.archlinux.org/svntogit/packages.git/plain/trunk/PKGBUILD?h=packages/chromium.

Thanks.

Re: [gentoo-user] Imdb videos won't play in Chromium

[Alexander Kapshuk]

On Sun, Jun 4, 2017 at 8:10 PM, Rasmus Thomsen
 wrote:
> Sorry, should've tried it myself before answering. I'm using Chromium
> 58.0.3029.110 ( 64 bit though ) built with cups,gconf,pulseaudio and it
> works for me ( both with extensions enabled and without any )
>

I have chromium built with the default USE flags settings:

equery -q u chromium | sed '/^+/!d;/l10/d'
+cups
+gtk3
+hangouts
+proprietary-codecs
+pulseaudio
+suid
+system-ffmpeg
+tcmalloc

Re: [gentoo-user] Imdb videos won't play in Chromium

[Alexander Kapshuk]

On Sun, Jun 4, 2017 at 7:45 PM, Rasmus Thomsen
<rasmus.thom...@protonmail.com> wrote:
> So chromium does detect flash, that's something ;)
>
> Please go to advanced settings → content settings and allow flash for all
> sites ( just to test it - don't use this config as daily driver
>
>  Original Message 
>
> On 4 Jun 2017, 18:41, Alexander Kapshuk < alexander.kaps...@gmail.com>
> wrote:
>
>
> On Sun, Jun 4, 2017 at 6:51 PM, Rasmus Thomsen
> <rasmus.thom...@protonmail.com> wrote:
>> Hi,
>>
>> Does chromium even recognize flash? Go to chrome://flash, it should
>> display
>> the current flash version under "Flash Plugin".
>> About the YouTube thing:
>> Are you sure that it doesn't use its HTML5 player? You can to go
>> youtube.com/html5 to check that.
>>
>> Regards,
>> Rasmus
>>
>>
>>
>>  Original Message 
>>
>> On 4 Jun 2017, 07:17, Alexander Kapshuk < alexander.kaps...@gmail.com>
>> wrote:
>>
>>
>> With these installed:
>> equery -q l chromium adobe-flash
>> www-client/chromium-58.0.3029.110
>> www-plugins/adobe-flash-25.0.0.171
>>
>> Imdb.com videos won't play any more. I get a 'sorry, this video is
>> unsupported on this browser' message displayed.
>>
>> A friend of mine has the same version of chromium installed with no
>> adobe-flash installed on Arch Linux and he is able to play imdb
>> videos.
>>
>> I've Googled it, but so far have not been able to find a solution to this.
>>
>> Clearing browsing data didn't help either.
>>
>> Youtube videos play OK though.
>>
>> Anyone else has had the same trouble and been able to fix it?
>>
>> Thanks.
>>
>
> Here's the Flash plugin settings as detected by Chromium:
>
> About Flash
>
> Chromium58.0.3029.110 ()
> OSLinux
> Flash plugin25.0.0.171 /usr/lib/chromium/PepperFlash/libpepflashplayer.so
> --- Crash data ---
> Crash ReportingEnable crash reporting to see crash IDs
> For more detailshttps://support.google.com/chrome/?p=ui_usagestat
> --- GPU information ---
> --- GPU driver, more information ---
> Vendor Id0x10de
> Device Id0x0a23
> Driver vendorMesa
> Driver version13.0.5
> Driver date
> Pixel shader version3.30
> Vertex shader version3.30
> GL_VENDORnouveau
> GL_RENDERERGallium 0.4 on NV84
> GL_VERSION3.3 (Core Profile) Mesa 17.0.6
> GL_EXTENSIONSGL_AMD_conservative_depth GL_AMD_performance_monitor
> GL_AMD_shader_trinary_minmax GL_ARB_ES2_compatibility
> GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_base_instance
> GL_ARB_blend_func_extended GL_ARB_buffer_storage
> GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control
> GL_ARB_color_buffer_float GL_ARB_compressed_texture_pixel_storage
> GL_ARB_conditional_render_inverted GL_ARB_conservative_depth
> GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance
> GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp
> GL_ARB_derivative_control GL_ARB_direct_state_access
> GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex
> GL_ARB_draw_instanced GL_ARB_enhanced_layouts
> GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location
> GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport
> GL_ARB_fragment_shader GL_ARB_framebuffer_object
> GL_ARB_framebuffer_sRGB GL_ARB_get_program_binary
> GL_ARB_get_texture_sub_image GL_ARB_half_float_pixel
> GL_ARB_half_float_vertex GL_ARB_instanced_arrays
> GL_ARB_internalformat_query GL_ARB_internalformat_query2
> GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment
> GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_occlusion_query2
> GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object
> GL_ARB_point_sprite GL_ARB_program_interface_query
> GL_ARB_provoking_vertex GL_ARB_robustness GL_ARB_sampler_objects
> GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects
> GL_ARB_shader_bit_encoding GL_ARB_shader_objects
> GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples
> GL_ARB_shader_texture_lod GL_ARB_shading_language_420pack
> GL_ARB_shading_language_packing GL_ARB_stencil_texturing GL_ARB_sync
> GL_ARB_texture_barrier GL_ARB_texture_buffer_object
> GL_ARB_texture_buffer_range GL_ARB_texture_compression_rgtc
> GL_ARB_texture_float GL_ARB_texture_mirror_clamp_to_edge
> GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two
> GL_ARB_texture_query_levels GL_ARB_texture_rectangle GL_ARB_texture_rg
> GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8
> GL_ARB_texture_storage GL_ARB_texture_storage_multisample
> GL_ARB_texture_swizzle GL_ARB_texture_v

Re: [gentoo-user] Imdb videos won't play in Chromium

[Alexander Kapshuk]

On Sun, Jun 4, 2017 at 6:51 PM, Rasmus Thomsen
<rasmus.thom...@protonmail.com> wrote:
> Hi,
>
> Does chromium even recognize flash? Go to chrome://flash, it should display
> the current flash version under "Flash Plugin".
> About the YouTube thing:
> Are you sure that it doesn't use its HTML5 player? You can to go
> youtube.com/html5 to check that.
>
> Regards,
> Rasmus
>
>
>
> ---- Original Message 
>
> On 4 Jun 2017, 07:17, Alexander Kapshuk < alexander.kaps...@gmail.com>
> wrote:
>
>
> With these installed:
> equery -q l chromium adobe-flash
> www-client/chromium-58.0.3029.110
> www-plugins/adobe-flash-25.0.0.171
>
> Imdb.com videos won't play any more. I get a 'sorry, this video is
> unsupported on this browser' message displayed.
>
> A friend of mine has the same version of chromium installed with no
> adobe-flash installed on Arch Linux and he is able to play imdb
> videos.
>
> I've Googled it, but so far have not been able to find a solution to this.
>
> Clearing browsing data didn't help either.
>
> Youtube videos play OK though.
>
> Anyone else has had the same trouble and been able to fix it?
>
> Thanks.
>

Here's the Flash plugin settings as detected by Chromium:

About Flash

Chromium58.0.3029.110 ()
OSLinux
Flash plugin25.0.0.171 /usr/lib/chromium/PepperFlash/libpepflashplayer.so
--- Crash data ---
Crash ReportingEnable crash reporting to see crash IDs
For more detailshttps://support.google.com/chrome/?p=ui_usagestat
--- GPU information ---
--- GPU driver, more information ---
Vendor Id0x10de
Device Id0x0a23
Driver vendorMesa
Driver version13.0.5
Driver date
Pixel shader version3.30
Vertex shader version3.30
GL_VENDORnouveau
GL_RENDERERGallium 0.4 on NV84
GL_VERSION3.3 (Core Profile) Mesa 17.0.6
GL_EXTENSIONSGL_AMD_conservative_depth GL_AMD_performance_monitor
GL_AMD_shader_trinary_minmax GL_ARB_ES2_compatibility
GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_base_instance
GL_ARB_blend_func_extended GL_ARB_buffer_storage
GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control
GL_ARB_color_buffer_float GL_ARB_compressed_texture_pixel_storage
GL_ARB_conditional_render_inverted GL_ARB_conservative_depth
GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance
GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp
GL_ARB_derivative_control GL_ARB_direct_state_access
GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex
GL_ARB_draw_instanced GL_ARB_enhanced_layouts
GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location
GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport
GL_ARB_fragment_shader GL_ARB_framebuffer_object
GL_ARB_framebuffer_sRGB GL_ARB_get_program_binary
GL_ARB_get_texture_sub_image GL_ARB_half_float_pixel
GL_ARB_half_float_vertex GL_ARB_instanced_arrays
GL_ARB_internalformat_query GL_ARB_internalformat_query2
GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment
GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_occlusion_query2
GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object
GL_ARB_point_sprite GL_ARB_program_interface_query
GL_ARB_provoking_vertex GL_ARB_robustness GL_ARB_sampler_objects
GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects
GL_ARB_shader_bit_encoding GL_ARB_shader_objects
GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples
GL_ARB_shader_texture_lod GL_ARB_shading_language_420pack
GL_ARB_shading_language_packing GL_ARB_stencil_texturing GL_ARB_sync
GL_ARB_texture_barrier GL_ARB_texture_buffer_object
GL_ARB_texture_buffer_range GL_ARB_texture_compression_rgtc
GL_ARB_texture_float GL_ARB_texture_mirror_clamp_to_edge
GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two
GL_ARB_texture_query_levels GL_ARB_texture_rectangle GL_ARB_texture_rg
GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8
GL_ARB_texture_storage GL_ARB_texture_storage_multisample
GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query
GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra
GL_ARB_vertex_array_object GL_ARB_vertex_attrib_binding
GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev
GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array
GL_ATI_blend_equation_separate GL_ATI_texture_float
GL_ATI_texture_mirror_once GL_EXT_abgr GL_EXT_blend_equation_separate
GL_EXT_depth_bounds_test GL_EXT_draw_buffers2 GL_EXT_draw_instanced
GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample
GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_sRGB
GL_EXT_packed_depth_stencil GL_EXT_packed_float
GL_EXT_pixel_buffer_object GL_EXT_polygon_offset_clamp
GL_EXT_provoking_vertex GL_EXT_shader_integer_mix GL_EXT_texture_array
GL_EXT_texture_compression_rgtc GL_EXT_texture_filter_anisotropic
GL_EXT_texture_integer GL_EXT_texture_mirror_clamp GL_EXT_texture_sRGB
GL_EXT_texture_sRGB_decode GL_EXT_texture_shared_exponent
GL_EXT_texture_snorm G

Re: [gentoo-user] Imdb videos won't play in Chromium

[Alexander Kapshuk]

On Sun, Jun 4, 2017 at 11:10 AM, Neil Bothwick <n...@digimed.co.uk> wrote:
> On Sun, 4 Jun 2017 08:17:40 +0300, Alexander Kapshuk wrote:
>
>> With these installed:
>> equery -q l chromium adobe-flash
>> www-client/chromium-58.0.3029.110
>> www-plugins/adobe-flash-25.0.0.171
>>
>> Imdb.com videos won't play any more. I get a 'sorry, this video is
>> unsupported on this browser' message displayed.
>>
>> A friend of mine has the same version of chromium installed with no
>> adobe-flash installed on Arch Linux and he is able to play imdb
>> videos.
>
> Do you have www-plugins/chrome-binary-plugins installed?

No, I don't. Mine is a 32-bit system. Chrome-binary-plugins were
64-bit last time I checked.

[gentoo-user] Imdb videos won't play in Chromium

[Alexander Kapshuk]

With these installed:
equery -q l chromium adobe-flash
www-client/chromium-58.0.3029.110
www-plugins/adobe-flash-25.0.0.171

Imdb.com videos won't play any more. I get a 'sorry, this video is
unsupported on this browser' message displayed.

A friend of mine has the same version of chromium installed with no
adobe-flash installed on Arch Linux and he is able to play imdb
videos.

I've Googled it, but so far have not been able to find a solution to this.

Clearing browsing data didn't help either.

Youtube videos play OK though.

Anyone else has had the same trouble and been able to fix it?

Thanks.

Re: [gentoo-user] nodejs and qtnetwork = conflict on bindist openssl USE flag

[Alexander Kapshuk]

On Fri, Jun 2, 2017 at 8:35 AM, Hogren  wrote:
> Hello list,
>
> When I try to update my system, I have many conflicts.
>
> A first conflict which about I need help is this:
>
> dev-libs/openssl:0
>
>   (dev-libs/openssl-1.0.2k:0/0::gentoo, installed) pulled in by
> >=dev-libs/openssl-1.0.2g:0=[-bindist] required by
> (net-libs/nodejs-7.10.0:0/0::gentoo, installed)
>
> 
>
> >=dev-libs/openssl-1.0.2g:0/0=[-bindist] required by
> (net-libs/nodejs-7.10.0:0/0::gentoo, installed)
>
> 
>
> >=dev-libs/openssl-0.9.8f:0[bindist=] required by
> (net-misc/openssh-7.3_p1-r7:0/0::gentoo, installed)
>
> 
>
>
>   (dev-libs/openssl-1.0.2k:0/0::gentoo, ebuild scheduled for merge)
> pulled in by
> dev-libs/openssl:0[bindist=] required by
> (dev-qt/qtnetwork-5.6.2:5/5.6::gentoo, ebuild scheduled for merge)
>
> 
>
>
>
>
> I tried de make "-ssl" USE flag to nodejs, but I have an error at the
> emerge time :
>
 Configuring source in
> /var/tmp/portage/net-libs/nodejs-7.10.0/work/node-v7.10.0 ...
> Error: --without-ssl is incompatible with --shared-openssl
>
>
> I look in the ebuild and I see there is apparently no method to drop the
> --shared-openssl option. So I can't use "-ssl".
>
>
> Did anybody have already the problem ?
>
>
> Thank you for help !
>
>
> Hogren
>
>

On my system, I overcame that by disabling the 'bindist' USE flag
globally in /etc/portage/make.conf.

Re: [gentoo-user] gdm fails to start

[Alexander Kapshuk]

On Mon, May 22, 2017 at 1:00 PM, Raffaele Belardi
<raffaele.bela...@st.com> wrote:
> On Mon, 2017-05-22 at 12:47 +0300, Alexander Kapshuk wrote:
>>
>> A Google search found this systemd issue:
>> https://github.com/systemd/systemd/issues/4342
>> Quote:
>> @poettering I see I left no account modules in the bare-bones PAM
>> config. Maybe it is pam_acct_mgmt failing then?
>>
>> @yuwata what happens if you add account required pam_unix.so ?
>>
>> @fsateler Thanks. By adding the line, user sessions successfully
>> start
>> without the error messages. Do you think the line should be added to
>> the minimal PAM file?
>>
>> See if that helps.
>>
>
> Yes, I saw that but the solution is not at all clear to me: which PAM
> config file are they referring to?
>
> raffaele
>
>
>
Could it be this one, /etc/pam.d/systemd-user?

Re: [gentoo-user] gdm fails to start

[Alexander Kapshuk]

On Mon, May 22, 2017 at 11:16 AM, Raffaele Belardi
 wrote:
> I'm unable to start the gdm service on a recently installed gnome
> desktop (~x86): the service continuously fails and restarts with the
> errors below. If I disable the service and login into a text console,
> startx works fine but the Gnome session misses some features (e.g.
> screen lock). I enabled debug logging on gdm but nothing significant
> appears.
>
> Any suggestions?
>
> thanks,
>
> raffaele
>
>
> systemd[356]: user@32.service: Failed at step PAM spawning
> /usr/lib/systemd/systemd: Operation not permitted
> systemd[1]: Failed to start User Manager for UID 32.
> gdm-launch-environment][310]: pam_systemd(gdm-launch-
> environment:session): Failed to create session: Start job for unit user
> @32.service failed with 'failed'
> systemd[1]: user@32.service: Unit entered failed state.
> systemd[1]: user@32.service: Failed with result 'protocol'.
>
> ...
>
> /usr/libexec/gdm-x-session[359]: Activated service
> 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1
> exited with stat
> /usr/libexec/gdm-x-session[359]: Unable to register display with
> display manager
>
>  # grep 32 /etc/passwd
> gdm:x:32:32:GDM:/var/lib/gdm:/bin/false
>
> # eselect profile list
> Available profile symlink targets:
>   [1]   default/linux/x86/13.0
>   [2]   default/linux/x86/13.0/selinux
>   [3]   default/linux/x86/13.0/desktop
>   [4]   default/linux/x86/13.0/desktop/gnome
>   [5]   default/linux/x86/13.0/desktop/gnome/systemd *
>   [6]   default/linux/x86/13.0/desktop/plasma
>   [7]   default/linux/x86/13.0/desktop/plasma/systemd
>   [8]   default/linux/x86/13.0/developer
>   [9]   default/linux/x86/13.0/systemd
>   [10]  hardened/linux/x86
>   [11]  hardened/linux/x86/selinux
>   [12]  hardened/linux/musl/x86
>   [13]  default/linux/uclibc/x86
>   [14]  hardened/linux/uclibc/x86
>

A Google search found this systemd issue:
https://github.com/systemd/systemd/issues/4342
Quote:
@poettering I see I left no account modules in the bare-bones PAM
config. Maybe it is pam_acct_mgmt failing then?

@yuwata what happens if you add account required pam_unix.so ?

@fsateler Thanks. By adding the line, user sessions successfully start
without the error messages. Do you think the line should be added to
the minimal PAM file?

See if that helps.

Re: [gentoo-user] libreoffice and java.

[Alexander Kapshuk]

On Thu, May 18, 2017 at 9:46 AM, Bill Kenworthy  wrote:
> Hi,
> I am trying use some java based plugins with libreoffice.
>
> libreoffice is compiled with the java use flag, both the oracle JDK and
> JRE are installed and the user and system VM's are set and JAVA_HOME is
> set in the environment.  In the libreoffice jre selection dialog the jre
> is showing an selected but I still get this error:
>
> $ lowriter
> javaldx: Could not find a Java Runtime Environment!
> Warning: failed to read path from javaldx
>
>
> What have I missed?
>
> BillK
>

Saw this post on the Gentoo forum:
https://forums.gentoo.org/viewtopic-t-1050766.html?sid=a282245dacbe0cf6206a4a452184fd46
Quote:
Open libreoffice Tools-> Options... in side menu go to LibreOffice ->
Advanced and select a virtual machine proposed on list (use flag java
must be enabled).

Haven't verified this myself though.

Re: [gentoo-user] Kernel config checks

[Alexander Kapshuk]

On Thu, Apr 27, 2017 at 11:45 AM, Manuel Schönlaub
 wrote:
> Hi,
>
> i just have a question regarding packages using linux-info.eclass to check
> for specific kernel config flags (e.g. app-emaulation/docker).
>
> Currently it seems like the flags are only checked against the config in
> /usr/src/linux which is not necessariliy the running kernel.
>
> Furthermore there are some warnings printed, but after some time i find it
> hard to remember what i will have to change in my kernel configs in order to
> make the package work right. It is also just a snapshot of the situation at
> the time emerge is building the package.
>
> Does there exists a tool helping in maintaining consistency between kernel
> configuration and configs required by currently installed packages.
>
> If not, could emaint be be the right tool to extend with this functionality?
> Or is this functionality not really needed?
>
> Regards,
>
> Manuel

I too run custom rather than gentoo kernels on my system with
/usr/src/linux being a symbolic link pointing to the location of the
kernel sources I have in my $HOME directory for this very reason.

Re: [gentoo-user] Multiple conflicts on perl upgrade

[Alexander Kapshuk]

On Wed, Apr 19, 2017 at 4:02 PM, Alarig Le Lay  wrote:
> Hi,
>
> I’m doing the normal updates on a server using this command:
> obelix ~ # eix-sync && emerge -va --update --newuse --deep --with-bdeps\=y 
> @world && emerge -va --depclean --with-bdeps\=y && eix-test-obsolete
>
> But it fails on perl packages update:
> dev-lang/perl:0
>
>   (dev-lang/perl-5.24.1-r1:0/5.24::gentoo, ebuild scheduled for merge) pulled 
> in by
> =dev-lang/perl-5.24* required by 
> (virtual/perl-version-0.991.600-r1:0/0::gentoo, ebuild scheduled for merge)
> ^  ^
> (and 33 more with the same problem)
>
>   (dev-lang/perl-5.22.3_rc4:0/5.22::gentoo, installed) pulled in by
> dev-lang/perl:0/5.22=[-build(-)] required by 
> (dev-perl/IO-Socket-INET6-2.720.0:0/0::gentoo, installed)
>  
> (and 50 more with the same problem)
>
> NOTE: Use the '--verbose-conflicts' option to display parents omitted above
>
> But, if I look at the required version for the printed package, it’s
> perl-5.24.1-r1 and not 5.22.3_rc4:
> obelix ~ # equery depgraph dev-perl/IO-Socket-INET6
>  * Searching for IO-Socket-INET6 in dev-perl ...
>
>  * dependency graph for dev-perl/IO-Socket-INET6-2.720.0
>  `--  dev-perl/IO-Socket-INET6-2.720.0  amd64
>`--  dev-perl/Socket6-0.270.0  (dev-perl/Socket6) amd64
>`--  dev-perl/Module-Build-0.421.600  (dev-perl/Module-Build) amd64
>`--  dev-lang/perl-5.24.1-r1  (dev-lang/perl) amd64  [-build(-)]
> [ dev-perl/IO-Socket-INET6-2.720.0 stats: packages (4), max depth (1) ]
>
> So, what’s the cause of this conflict?
>
> --
> alarig

https://wiki.gentoo.org/wiki/Perl#Upgrading_.28major_version.29
emerge -uDNav --with-bdeps y --backtrack 100 @world
perl-cleaner --all

Re: [gentoo-user] nxclient: cannot execute binary file: Exec format error

[Alexander Kapshuk]

On Sun, Apr 9, 2017 at 7:15 PM, Alexander Kapshuk
<alexander.kaps...@gmail.com> wrote:
> On Sun, Apr 9, 2017 at 7:06 PM,  <the...@sys-concept.com> wrote:
>> On 04/09/2017 09:55 AM, Alexander Kapshuk wrote:
>>> On Sun, Apr 9, 2017 at 6:49 PM,  <the...@sys-concept.com> wrote:
>>>> I've installed: net-misc/nxclient-3.5.0.7 on x86 and it compiled without 
>>>> errors, but when I try to run it I get an error:
>>>>
>>>> nxclient
>>>> /usr/bin/nxclient: line 8: /usr/NX/bin/nxclient: cannot execute binary 
>>>> file: Exec format error
>>>> /usr/bin/nxclient: line 8: /usr/NX/bin/nxclient: Success
>>>>
>>>> In a remote location all my boxes are Gentoo except one Win10 (Home 
>>>> Edition).
>>>> I have a hard time connecting to it.
>>>> X2Go has only client for Win10 but in order for x2go to connect to Win10, 
>>>> it would have to run X2Go-server isn't it?
>>>>
>>>> Win10 has Remote Desktop for connecting to other computers, but you can't 
>>>> remote desktop to Windows 10 Home itself. That requires Windows 10 Pro.
>>>>
>>>> What are my alternatives?
>>>>
>>>> --
>>>> Thelma
>>>>
>>>
>>> What's the output of 'readelf -h /path/to/nxclient'?
>>>
>>>
>> readelf -h  /usr/NX/bin/nxclient
>> ELF Header:
>>   Magic:   7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
>>   Class: ELF64
>>   Data:  2's complement, little endian
>>   Version:   1 (current)
>>   OS/ABI:UNIX - System V
>>   ABI Version:   0
>>   Type:  EXEC (Executable file)
>>   Machine:   Advanced Micro Devices X86-64
>>   Version:   0x1
>>   Entry point address:   0x4207e0
>>   Start of program headers:  64 (bytes into file)
>>   Start of section headers:  6314232 (bytes into file)
>>   Flags: 0x0
>>   Size of this header:   64 (bytes)
>>   Size of program headers:   56 (bytes)
>>   Number of program headers: 8
>>   Size of section headers:   64 (bytes)
>>   Number of section headers: 29
>>   Section header string table index: 28
>>
>> --
>> Thelma
>>
>
> OK. It's an x86-64 binary. That explains the error message you got
> when attempting to run it on your x86 machine.
> How did that happen, I wonder?
>
> Just to be 100% sure, can you please supply the output of the commands below?
> uname -m
> gcc -v 2>&1 | grep ^Target
> emerge --info

'net-misc/nxclient' doesn't seem to be in my portage tree?
Is it supported by Gentoo devs at all?

Re: [gentoo-user] nxclient: cannot execute binary file: Exec format error

[Alexander Kapshuk]

On Sun, Apr 9, 2017 at 7:06 PM,  <the...@sys-concept.com> wrote:
> On 04/09/2017 09:55 AM, Alexander Kapshuk wrote:
>> On Sun, Apr 9, 2017 at 6:49 PM,  <the...@sys-concept.com> wrote:
>>> I've installed: net-misc/nxclient-3.5.0.7 on x86 and it compiled without 
>>> errors, but when I try to run it I get an error:
>>>
>>> nxclient
>>> /usr/bin/nxclient: line 8: /usr/NX/bin/nxclient: cannot execute binary 
>>> file: Exec format error
>>> /usr/bin/nxclient: line 8: /usr/NX/bin/nxclient: Success
>>>
>>> In a remote location all my boxes are Gentoo except one Win10 (Home 
>>> Edition).
>>> I have a hard time connecting to it.
>>> X2Go has only client for Win10 but in order for x2go to connect to Win10, 
>>> it would have to run X2Go-server isn't it?
>>>
>>> Win10 has Remote Desktop for connecting to other computers, but you can't 
>>> remote desktop to Windows 10 Home itself. That requires Windows 10 Pro.
>>>
>>> What are my alternatives?
>>>
>>> --
>>> Thelma
>>>
>>
>> What's the output of 'readelf -h /path/to/nxclient'?
>>
>>
> readelf -h  /usr/NX/bin/nxclient
> ELF Header:
>   Magic:   7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
>   Class: ELF64
>   Data:  2's complement, little endian
>   Version:   1 (current)
>   OS/ABI:UNIX - System V
>   ABI Version:   0
>   Type:  EXEC (Executable file)
>   Machine:   Advanced Micro Devices X86-64
>   Version:   0x1
>   Entry point address:   0x4207e0
>   Start of program headers:  64 (bytes into file)
>   Start of section headers:  6314232 (bytes into file)
>   Flags: 0x0
>   Size of this header:   64 (bytes)
>   Size of program headers:   56 (bytes)
>   Number of program headers: 8
>   Size of section headers:   64 (bytes)
>   Number of section headers: 29
>   Section header string table index: 28
>
> --
> Thelma
>

OK. It's an x86-64 binary. That explains the error message you got
when attempting to run it on your x86 machine.
How did that happen, I wonder?

Just to be 100% sure, can you please supply the output of the commands below?
uname -m
gcc -v 2>&1 | grep ^Target
emerge --info

Re: [gentoo-user] nxclient: cannot execute binary file: Exec format error

[Alexander Kapshuk]

On Sun, Apr 9, 2017 at 6:49 PM,   wrote:
> I've installed: net-misc/nxclient-3.5.0.7 on x86 and it compiled without 
> errors, but when I try to run it I get an error:
>
> nxclient
> /usr/bin/nxclient: line 8: /usr/NX/bin/nxclient: cannot execute binary file: 
> Exec format error
> /usr/bin/nxclient: line 8: /usr/NX/bin/nxclient: Success
>
> In a remote location all my boxes are Gentoo except one Win10 (Home Edition).
> I have a hard time connecting to it.
> X2Go has only client for Win10 but in order for x2go to connect to Win10, it 
> would have to run X2Go-server isn't it?
>
> Win10 has Remote Desktop for connecting to other computers, but you can't 
> remote desktop to Windows 10 Home itself. That requires Windows 10 Pro.
>
> What are my alternatives?
>
> --
> Thelma
>

What's the output of 'readelf -h /path/to/nxclient'?