saskia

Hi, Thanks for your ongoing effort! I was using the stage3-intel64-skylake-funtoo-current-2018-08-21.tar.xz both, the multilib and the pure64 one. Both fail the same way. When I run nvim in the build directory directly cd /var/tmp/portage/app-editors/neovim-0.3.1/work/neovim-0.3.1_build/runtime && /var/tmp/portage/app-editors/neovim-0.3.1/work/neovim-0.3.1_build/bin/nvim this is the result <jemalloc>: Error in dlsym(RTLD_NEXT, "pthread_create" Aborted. With USE=-jemalloc both ruby as well as neovim built successfully. Rust build successfully with jemalloc enabled. I cannot relate the issue between Ruby and neovim as ruby hangs in the configure phase and I have no clue how to debug that. P.S. Lighttpd also built successfully with libressl on the pure64 stage3.

Hi, yes, I have read the How do I ask a good question page. But this wasn't me asking for help but rather a report that there are broken files hosted on that provider. I cannot post a log anymore because I re-downloaded the files from another mirror and didn't keep the broken files. There was no error message related to the problem either. Just a cannot extract <filename.tar...> which made it sound like the file doesn't exist.

Hi, this is more of a bug report and should probably be reported there but it appears I'm too dumb-sighted to spot the link. So sorry for the inconvenience. In the past few days I had some weird problems that emerge would always want to download files, even though they are present on the file system. May I suggest that when a downloaded file is corrupt, i.e. the checksum doesn't match, it would be great if emerge would mention that in the logs? As for the broken files: noto-cjk-201506.15.tar.xz [emerge -pv reported ~300MiB but the download was ~90MiB] flask-principal-0.4.0.tar.gz The download was from https://fastpull-us.funtoo.org/distfiles which was redirected to cdn77. Sorry I didn't make notes of the other files as I didn't relate that to broken downloads. Anyways, thanks for your effort.

Hello palica, Thanks a lot for your effort. It is kind of a weird issue and I never ran into something like that before. All I know is that ruby as well as neovim emerge fine without jemalloc, i.e. USE=-jemalloc. Rust, which happens to have a jemalloc use flag, too, emerged without issues. It happens on pure64 as well as on multilib. The hardware is a NUC6i5-SYK. I haven't experience any issues at all with this thing when it ran Arch Linux, however an internet search revealed that there are bugs and that linux support is not so awesome. If it happened only in my custom kernel I would blame that but the debian kernel [4.14.12], which is what I used initially, doesn't solve the issue either. jemalloc-5.0.1:0/2::dev-kit USE=hardned hugepages lazy-lock xmalloc -debug -static-libs -stats Emerging jemalloc with USE=-hugepages didn't solve the issue. There are a few options left... EDIT: sorry for lack of markup but it seems I didn't have a JS powered editor

The issue was related to jemalloc.

I had a problem similar to what you show in your screenshot. I.e. mounting /dev/sdxx ... no such device. Except in my case it was working with the debian kernel but not with my custom one. What is the output of lsblk in the rescue shell ? Also what do you get when you ls /dev in the rescue shell ? It looks like your ssd isn't even recognized. So maybe a driver is missing. Probably the sata driver.

boot-update generates the grub.cfg from boot.conf. More details here: https://www.funtoo.org/Install/Bootloader

neovim-0.3.1.log ruby-2.3.6.log ruby-2.4.3.log ruby-2.4.3-sans_ssl.log

Hello, first of all thank you everyone for all the effort you have put into funtoo/gentoo the wiki, the forum and everything not so obvious. As for the problem... I've installed funtoo and gentoo several times and everytime it went more or less smoothly. So I decided I want to switch my NUC to funtoo, too, and ran into some weird issues. Please note that this is an offline installation. I started the way I usually set this up. Use the installation wiki as a check list. ..., then emerge @world -uND and all went smooth so far. Then I rebooted and ran into several blockers which I have no idea how to debug [and which I'm unsure whether or not I shall mention them all here or in separate posts]. First thing after reboot I wanted to install neovim [which hangs at some other point [scanning dependencies of target helptags] when I tried to rebuild without ruby use flags]. After waiting for several hours I decided to abort and build ruby by itself and during the prepare phase it keeps hanging at the line: checking for broken backtrace the log files tell me exactly the same as the console output. I repeated this step a few times, same result every time. So what's going on? How can I check if my system is missing something? How can I debug this hang?