Re: [gentoo-user] glibc-2.27 is broken

2018-10-30 Thread the
On 10/30/2018 12:52 PM, Philip Webb wrote:
> NB above : the error you cite is '4' :
> this shows there are other errors '1' '2' '3' above, which are more important.
> It would help if you find them & report them to the list.

Thanks, but that's the whole gcc output I got.
BTW the code for this is:

$ cat main.c
#include 

int main(int argc, char **argv) {

printf("hello world\n");
return 0;

}




Re: [gentoo-user] glibc-2.27 is broken

2018-10-30 Thread Philip Webb
181030 the wrote:
> I have upgraded to sys-libs/glibc-2.27-r6 and it broke the system.
> I can't even compile a hello world test program in c.
> I always get the following linking error:
>   $ gcc main.c -o main.elf
>   
> /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld:
>   
> /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../lib64/crtn.o(a.debug_info+0x10003):
>   reloc against `*UND*': error 4
>   
> /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld:
>   final link failed: Nonrepresentable section on output
>   collect2: error: ld returned 1 exit status
> When I try to install something it fails during configuration
> at compiler sanity check.

I updated to this version of Glibc 181027 & emerged other pkgs successfully.
I don't use the 'multiarch' USE flag.

> Should I report this as a bug or is there's something wrong with me ?

I'm sure there's nothing wrong with you (smile),
but there mb a USE flag or similar which needs changing.

NB above : the error you cite is '4' :
this shows there are other errors '1' '2' '3' above, which are more important.
It would help if you find them & report them to the list.

No doubt others will offer more detailed advice.

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca




[gentoo-user] glibc-2.27 is broken

2018-10-30 Thread the
Hello,

I have upgraded to sys-libs/glibc-2.27-r6
and it broke the system.

I can't even compile a hello world test program in c.

I always get the following linking error:

$ gcc main.c -o main.elf
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld:
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../lib64/crtn.o(a.debug_info+0x10003):
reloc against `*UND*': error 4
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld:
final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status

When I try to install something it fails during configuration at
compiler sanity check.

Should I report this as a bug or is there's something wrong with me?

System info:

Binutils 2.30-r2
gcc 7.3.0

# emerge -pvq '=sys-devel/gcc-7.3.0-r3'
[ebuild   R   ] sys-devel/gcc-7.3.0-r3  USE="cilk cxx fortran go
graphite (multilib) nls nptl openmp pch pgo* (pie) sanitize ssp vtv
(-altivec) -debug -doc (-fixed-point) (-hardened) (-jit) (-libssp) -mpx
-objc -objc++ -objc-gc -regression-test -vanilla"





# emerge --info '=sys-libs/glibc-2.27-r6'
Portage 2.3.49 (python 3.6.5-final-0, default/linux/amd64/17.0/desktop,
gcc-7.3.0, glibc-2.27-r6, 4.12.12-gentoo x86_64)
=
 System Settings
=
System uname:
Linux-4.12.12-gentoo-x86_64-AMD_Opteron-tm-_Processor_6320-with-gentoo-2.4.1
KiB Mem:32921172 total,  30174684 free
KiB Swap:   33303572 total,  33303572 free
Timestamp of repository gentoo: Mon, 29 Oct 2018 22:00:01 +
Head commit of repository gentoo: 0d1f9865d36f3c4efac70f236d962901a113b8b4
sh bash 4.4_p12
ld GNU ld (Gentoo 2.30 p2) 2.30.0
app-shells/bash:  4.4_p12::gentoo
dev-lang/perl:5.24.3-r1::gentoo
dev-lang/python:  2.7.14-r1::gentoo, 3.4.5::gentoo,
3.5.5::gentoo, 3.6.5::gentoo
dev-util/cmake:   3.9.6::gentoo
dev-util/pkgconfig:   0.29.2::gentoo
sys-apps/baselayout:  2.4.1-r2::gentoo
sys-apps/openrc:  0.34.11::gentoo
sys-apps/sandbox: 2.13::gentoo
sys-devel/autoconf:   2.13::gentoo, 2.69-r4::gentoo
sys-devel/automake:   1.12.6::gentoo, 1.14.1::gentoo, 1.15.1-r2::gentoo
sys-devel/binutils:   2.26.1::gentoo, 2.28.1::gentoo,
2.29.1-r1::gentoo, 2.30-r2::gentoo
sys-devel/gcc:4.9.3::gentoo, 5.4.0-r3::gentoo,
6.4.0-r1::gentoo, 7.3.0-r3::gentoo
sys-devel/gcc-config: 1.8-r1::gentoo
sys-devel/libtool:2.4.6-r3::gentoo
sys-devel/make:   4.2.1-r3::gentoo
sys-kernel/linux-headers: 4.13::gentoo (virtual/os-headers)
sys-libs/glibc:   2.27-r6::gentoo
Repositories:

gentoo
location: /usr/portage
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000
sync-rsync-extra-opts:
sync-rsync-verify-metamanifest: yes
sync-rsync-verify-jobs: 1
sync-rsync-verify-max-age: 24

ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -mno-tbm -mno-bmi -mno-avx -mno-aes -mno-sha
-mno-fma -mno-xop -mno-lwp -mno-abm -mno-3dnow -mno-sse3 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild
/etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d
/etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-march=native -mno-tbm -mno-bmi -mno-avx -mno-aes -mno-sha
-mno-fma -mno-xop -mno-lwp -mno-abm -mno-3dnow -mno-sse3 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
ENV_UNSET="DBUS_SESSION_BUS_ADDRESS DISPLAY PERL5LIB PERL5OPT PERLPREFIX
PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME
XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified
distlocks ebuild-locks fixlafiles merge-sync multilib-strict news
parallel-fetch preserve-libs protect-owned sandbox sfperms strict
unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv
usersandbox usersync xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="ftp://mirrors.tera-byte.com/pub/gentoo
http://gentoo.mirrors.tera-byte.com/ rsync://mirrors.tera-byte.com/gentoo"
LANG="en_US.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j9"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times
--omit-dir-times --compress --force --whole-file --delete --stats
--human-readable --timeout=180 --exclude=/distfiles --exclude=/local
--exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
USE="X a52 aac acl acpi alsa amd64 berkdb bluetooth branding bzip2 cairo
cdda cdr cli consolekit crypt cups cxx dbus dri dts dvd dvdr emacs
emboss encode exif fam ffmpeg flac fortran gdbm gif glamor gpm gtk iconv
ipv6 jpeg latex lcms ldap libnotify libti

[gentoo-user] subscribe

2018-10-30 Thread Zven Campe

subscribe




Re: [gentoo-user] portage sandbox path-depth limit ?

2018-10-30 Thread Håkon Alstadheim


Den 30. okt. 2018 10:01, skrev Mick:
> On Tuesday, 30 October 2018 06:30:23 GMT Håkon Alstadheim wrote:
>> I'm having fun enabling "test" in FEATURES on my gentoo-desktop. One
>> interesting failure, that brings to mind build failures I have had in
>> the past:
>>
>> Building sys-apps/mlocate-0.26-r2, I get
>>
>>  43: updatedb: Very deep hierarchy   FAILED
>> (updatedb.at:261)
>>
>> Trying to reproduce, as root I do "make check" in the work/mlocate-0.26/
>> , and the test passes.
>>
>>  43: updatedb: Very deep hierarchy   ok
>>
>> I'd really like to get to the bottom of this, as I believe it must have
>> the same root-cause as issues I have had compiling large packages such
>> as firefox.
>>
>> Re-running both the emerge and the make check, I get the same results.
>> emerge fails, make check succeeds. I made a local copy of the ebuild and
>> inserted a "ulimit -a" in pre_src_test.
>>
>> ulimit from root-shell:
>>
>> # ulimit -a
>> core file size  (blocks, -c) unlimited
>> data seg size   (kbytes, -d) unlimited
>> scheduling priority (-e) 0
>> file size   (blocks, -f) unlimited
>> pending signals (-i) 59958
>> max locked memory   (kbytes, -l) 16384
>> max memory size (kbytes, -m) unlimited
>> open files  (-n) 1024
>> pipe size(512 bytes, -p) 8
>> POSIX message queues (bytes, -q) 819200
>> real-time priority  (-r) 0
>> stack size  (kbytes, -s) 8192
>> cpu time   (seconds, -t) unlimited
>> max user processes  (-u) 1
>> virtual memory  (kbytes, -v) unlimited
>> file locks  (-x) unlimited
>>
>> ulimit from emerge:
> Source compiled.
>> core file size  (blocks, -c) unlimited
>> data seg size   (kbytes, -d) unlimited
>> scheduling priority (-e) 0
>> file size   (blocks, -f) unlimited
>> pending signals (-i) 59958
>> max locked memory   (kbytes, -l) 16384
>> max memory size (kbytes, -m) unlimited
>> open files  (-n) 1024
>> pipe size(512 bytes, -p) 8
>> POSIX message queues (bytes, -q) 819200
>> real-time priority  (-r) 0
>> stack size  (kbytes, -s) 9788
>> cpu time   (seconds, -t) unlimited
>> max user processes  (-u) 1
>> virtual memory  (kbytes, -v) unlimited
>> file locks  (-x) unlimited
>>
> Test phase: sys-apps/mlocate-0.26-r2
>> I have plenty of space in my portage temp directory (/pt):
>>
>>  # df -hT ./
>> Filsystem  Type Størrelse Brukt Tilgj. Bruk% Montert på
>> /dev/xvdc  ext4  163G  8,0G   147G6% /pt
>>
>> Portage temp is at /pt due to the earlier mentioned issues with firefox.
>>
>> At my wits end here. Anyone ?
> I have not looked or used the test FEATURES of portage, but have also noticed 
> over time certain packages fail to build on machines with low RAM.  As low 
> here I consider anything less than 4G.  It seems each thread is now consuming 
> so much memory they cumulatively use up all RAM available and then start 
> swapping endlessly until the compilation invariably fails.  Increasingly more 
> and more packages have been suffering from this, the last two I noticed are 
> qtwebkit and qtwebengine.
>
> My solution has been to create a package.env file in which I specify MAKEOPTS 
> limiting the number of jobs and average load for any of these packages which 
> chew up all the RAM.
Memory should not be a problem here. Fails with only that one emerge
running,
succeeds if run directly as root, or with FEATURES="-sandbox -usersandbox".

Memory is >14GB:
# vmstat
procs ---memory-- ---swap-- -io -system--
--cpu-
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy
id wa st
 3  4  28416 6904608 174112 4616144    0    0    65   266   13    4 10 
2 84  4  0




Re: [gentoo-user] TLSv1.3 with apache?

2018-10-30 Thread Stefan G. Weichinger

Am 30.10.18 um 13:01 schrieb Stefan G. Weichinger:


Is that possible with gentoo already?

Simply adding "SSLProtocol TLSv1.3" to my vhost did not work out here, 
pls point me to some info, thanks ;-)


Ah, I see, only with >=openssl-1.1.1, correct?

I will simply wait




[gentoo-user] TLSv1.3 with apache?

2018-10-30 Thread Stefan G. Weichinger



Is that possible with gentoo already?

Simply adding "SSLProtocol TLSv1.3" to my vhost did not work out here, 
pls point me to some info, thanks ;-)





Re: [gentoo-user] Android studio emulator without PulseAudio

2018-10-30 Thread Pouru Lasse
"Davyd McColl"  writes:

> Would apulse not do the trick?
>
> -d
> On 2018-10-30 11:15:14, Pouru Lasse  wrote:
>
> Is it possible to run the emulator included with Android Studio without
> having PulseAudio installed? When I try to launch the emulator, it
> instantly crashes because it can't find libpulse.so.0. My QEMU package
> is compiled without PulseAudio, but Android SDK comes with its own
> version of QEMU.
>
> Setting QEMU_AUDIO_DRV=none, as instructed in Android Studio manual,
> seems to have no effect, and the Gentoo wiki page on Android Studio just
> tells you to install PulseAudio.
>
> I don't mind having no audio at all, I just don't want to install
> PulseAudio. Any options?
>
> - Lasse

I already had apulse installed, but apparently the emulator doesn't look
for the library in the right directory. I copied all the libpulse.*
files under ~/Android/Sdk/emulator/lib/ and
~/Android/Sdk/emulator/lib64/ and now it seems to work.

- Lasse



Re: [gentoo-user] Android studio emulator without PulseAudio

2018-10-30 Thread Davyd McColl
Would apulse not do the trick?

-d
On 2018-10-30 11:15:14, Pouru Lasse  wrote:

Is it possible to run the emulator included with Android Studio without
having PulseAudio installed? When I try to launch the emulator, it
instantly crashes because it can't find libpulse.so.0. My QEMU package
is compiled without PulseAudio, but Android SDK comes with its own
version of QEMU.

Setting QEMU_AUDIO_DRV=none, as instructed in Android Studio manual,
seems to have no effect, and the Gentoo wiki page on Android Studio just
tells you to install PulseAudio.

I don't mind having no audio at all, I just don't want to install
PulseAudio. Any options?

- Lasse



[gentoo-user] Android studio emulator without PulseAudio

2018-10-30 Thread Pouru Lasse


Is it possible to run the emulator included with Android Studio without
having PulseAudio installed? When I try to launch the emulator, it
instantly crashes because it can't find libpulse.so.0. My QEMU package
is compiled without PulseAudio, but Android SDK comes with its own
version of QEMU.

Setting QEMU_AUDIO_DRV=none, as instructed in Android Studio manual,
seems to have no effect, and the Gentoo wiki page on Android Studio just
tells you to install PulseAudio.

I don't mind having no audio at all, I just don't want to install
PulseAudio. Any options?

- Lasse



Re: [gentoo-user] portage sandbox path-depth limit ?

2018-10-30 Thread Mick
On Tuesday, 30 October 2018 06:30:23 GMT Håkon Alstadheim wrote:
> I'm having fun enabling "test" in FEATURES on my gentoo-desktop. One
> interesting failure, that brings to mind build failures I have had in
> the past:
> 
> Building sys-apps/mlocate-0.26-r2, I get
> 
>  43: updatedb: Very deep hierarchy   FAILED
> (updatedb.at:261)
> 
> Trying to reproduce, as root I do "make check" in the work/mlocate-0.26/
> , and the test passes.
> 
>  43: updatedb: Very deep hierarchy   ok
> 
> I'd really like to get to the bottom of this, as I believe it must have
> the same root-cause as issues I have had compiling large packages such
> as firefox.
> 
> Re-running both the emerge and the make check, I get the same results.
> emerge fails, make check succeeds. I made a local copy of the ebuild and
> inserted a "ulimit -a" in pre_src_test.
> 
> ulimit from root-shell:
> 
> # ulimit -a
> core file size  (blocks, -c) unlimited
> data seg size   (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size   (blocks, -f) unlimited
> pending signals (-i) 59958
> max locked memory   (kbytes, -l) 16384
> max memory size (kbytes, -m) unlimited
> open files  (-n) 1024
> pipe size(512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority  (-r) 0
> stack size  (kbytes, -s) 8192
> cpu time   (seconds, -t) unlimited
> max user processes  (-u) 1
> virtual memory  (kbytes, -v) unlimited
> file locks  (-x) unlimited
> 
> ulimit from emerge:
> >>> Source compiled.
> 
> core file size  (blocks, -c) unlimited
> data seg size   (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size   (blocks, -f) unlimited
> pending signals (-i) 59958
> max locked memory   (kbytes, -l) 16384
> max memory size (kbytes, -m) unlimited
> open files  (-n) 1024
> pipe size(512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority  (-r) 0
> stack size  (kbytes, -s) 9788
> cpu time   (seconds, -t) unlimited
> max user processes  (-u) 1
> virtual memory  (kbytes, -v) unlimited
> file locks  (-x) unlimited
> 
> >>> Test phase: sys-apps/mlocate-0.26-r2
> 
> I have plenty of space in my portage temp directory (/pt):
> 
>  # df -hT ./
> Filsystem  Type Størrelse Brukt Tilgj. Bruk% Montert på
> /dev/xvdc  ext4  163G  8,0G   147G6% /pt
> 
> Portage temp is at /pt due to the earlier mentioned issues with firefox.
> 
> At my wits end here. Anyone ?

I have not looked or used the test FEATURES of portage, but have also noticed 
over time certain packages fail to build on machines with low RAM.  As low 
here I consider anything less than 4G.  It seems each thread is now consuming 
so much memory they cumulatively use up all RAM available and then start 
swapping endlessly until the compilation invariably fails.  Increasingly more 
and more packages have been suffering from this, the last two I noticed are 
qtwebkit and qtwebengine.

My solution has been to create a package.env file in which I specify MAKEOPTS 
limiting the number of jobs and average load for any of these packages which 
chew up all the RAM.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.