kde-base/kdelibs-4.14.14 fails to compile

While doing my weekly world update I had one compilation failure for kdelibs version 4.14.13-r1 the package is stable but the code seems to require header files that I do not have on my system. lere is a list of my missing headers:

filio.h
libutil.h
crtdbg.h
mnttab.h

There are other failures in the build log that are probably a result of the missing files.

Is I have searched and searched and can not find these files on my system or a place where I can grab the headers online.

Any help will be much appreciated.

Thanks.

Hi, mnttab.h in the sys-fs/zfs
crtdbg.h in the wine

libutil.h --> dev-libs/libbsd

Still having the same issue with kde-base/kdelibs-4.14.14. Does anyone know how to resolve this?

Still having an issue. Attaching build logs.

build.log (2.13 MB)

I think the problem may be due to: link
Why not use a binary package?

How do I get the binary? An eix kdelibs shows no binary package.

Greetings, Antonio
Package in place

  • Binary host is set? Can you check this by command: emerge --info | grep PORTAGE_BINHOST ?
  • Show me the profile used by you: eselect profile show
  • Also, as I can see, USE flags in binary package and in you system completely different by these: altivec aqua debug doc fam kerberos libressl lzma test zeroconf Quick fix is to add them to package use: echo ‘kde-base/kdelibs altivec aqua debug doc fam kerberos libressl lzma test zeroconf’ >> /etc/portage/package.use/custom I wrote a little bash script for investigate USE differences, which you can use if you wish.

emerge --info | grep PORTAGE_BINHOST
no result showed
sys-kernel/linux-headers
eselect profile show
distros:CLD/amd64

Question, are you saying the binary on your system was compiled with altivec aqua debug doc fam kerberos libressl lzma test zeroconf USE flags? Portage is wanting to pull in acl alsa bzip2 crypt handbook jpeg2k nls openexr opengl policykit spell ssl udev udisks upower.

I can try to compile with the USE flags you listed.

emerge info http://pastebin.calculate-linux.org/en/show/11480

Сергей Федотов,

Thank you for your assistance and incite, I would like to know more about this PORTAGE_BINHOST. I got the package to compile with the USE flags you suggested, but portage pulled in the following:

acl alsa bzip2 crypt debug* doc* handbook jpeg2k kerberos* lzma* nls openexr opengl policykit spell ssl udev udisks upower zeroconf*

Here is my make.conf
http://pastebin.calculate-linux.org/en/show/11482

Antonio Hutsona wrote:

emerge --info | grep PORTAGE_BINHOST
no result showed

Looks like your system is heavily modified. PORTAGE_BINHOST variable must declared by your profile templates. Let’s see: distros/cld profile point to [desktop/kde](file:///var/lib/layman/calculate/profiles/base/desktop/kde/amd64/make.defaults) where this variable declared

Question, are you saying the binary on your system was compiled with altivec aqua debug doc fam kerberos libressl lzma test zeroconf USE flags?

I do not have kdelibs on my system. All I did just spied this flags in the binary repository and your build.log. You can search the package by “CPV: kde-base/kde-libs” keyword and investigate its USE flags. Or just by using my script mentioned above, of course if binary host is declared.

I can try to compile with the USE flags you listed.

Yes, you can. But if system USE flags completely different, the result will does not suit you

I would like to know more about this PORTAGE_BINHOST

Please check: this and this

Here is my make.conf

Pay attention to FEATURES=“-getbinpkg” in you make.conf. Binary packages completely disabled in you system. Why you do it? It is one of the great features of Calculate Linux. Also I do not recommend using global USE flags or LINGUAS in make.conf, they discourage the use of binary packages. Better practice is specify them in /etc/portage/package.use/custom per package.

If you like to build system from source, then why do you need Calculate Linux?

Is it not wonderful?

Unfortunately, due to the fact that you are using CFLAGS and other optimizations, binaries will not work for you completely.