[SOLVED] vte3 compile from SBo fails

BroX · 07-07-2014, 06:56 AM

Hi,

when upgrading vte3 (using either sbopkg or straight from SBo) the compilation fails with the following error:

Code:

  CC       libvte2_90_la-vteutils.lo
vteutils.c: In function '_vte_mkstemp':
vteutils.c:90:71: error: 'FS_NOCOW_FL' undeclared (first use in this function)
                 flags |= FS_SECRM_FL | FS_NOATIME_FL | FS_NOCOMP_FL | FS_NOCOW_FL | FS_NODUMP_FL;
                                                                       ^
vteutils.c:90:71: note: each undeclared identifier is reported only once for each function it appears in
make[3]: *** [libvte2_90_la-vteutils.lo] Error 1
make[3]: Leaving directory `/tmp/SBo/vte-0.36.3/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/tmp/SBo/vte-0.36.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/SBo/vte-0.36.3'
make: *** [all] Error 2
make  all-recursive
make[1]: Entering directory `/tmp/SBo/vte-0.36.3'
Making all in src
make[2]: Entering directory `/tmp/SBo/vte-0.36.3/src'
make  all-am
make[3]: Entering directory `/tmp/SBo/vte-0.36.3/src'
  CC       libvte2_90_la-vteutils.lo
vteutils.c: In function '_vte_mkstemp':
vteutils.c:90:71: error: 'FS_NOCOW_FL' undeclared (first use in this function)
                 flags |= FS_SECRM_FL | FS_NOATIME_FL | FS_NOCOMP_FL | FS_NOCOW_FL | FS_NODUMP_FL;
                                                                       ^
vteutils.c:90:71: note: each undeclared identifier is reported only once for each function it appears in
make[3]: *** [libvte2_90_la-vteutils.lo] Error 1
make[3]: Leaving directory `/tmp/SBo/vte-0.36.3/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/tmp/SBo/vte-0.36.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/SBo/vte-0.36.3'
make: *** [all] Error 2

Google wasn't of any help, and I can't figure out what is wrong (besides that 'FS_NOCOW_FL' is undeclared, but that doesn't mean much to me).

Any pointers?

willysr · 07-07-2014, 07:05 AM

Just tested here on my VM and it's working fine

Quote:

SUMMARY LOG
Using the SBo repository for Slackware 14.1
Queue Process: Download and build

vte3:
MD5SUM check for vte-0.36.3.tar.xz ... OK
Building package vte3-0.36.3-x86_64-1_SBo.tgz ... OK

Do you have a full installation of Slackware 14.1?

BroX · 07-07-2014, 07:08 AM

I have a full install, but current instead of 14.1.
Could that be the reason?

EDIT: @willysr: I wasn't suggesting there was anything wrong with the Slackbuild. I know one can always rely on your scripts.

I get the same error message when doing the manual configure/make thing.

ponce · 07-07-2014, 07:25 AM

are you by any chance missing the kernel-source package?

BroX · 07-07-2014, 07:27 AM

I have kernel-source-2.6.35.10-noarch-1 installed, but recompiled a custom kernel-3.15.3.

ponce · 07-07-2014, 07:29 AM

I think you must upgrade your kernel-source (and probably also kernel-headers) package to the one of -current.

ml4711 · 07-07-2014, 07:35 AM

That symbol is defined in

/usr/include/linux/fs.h from kernel-headers-3.14.5-x86-1.txz

Is this one installed?

BroX · 07-07-2014, 07:36 AM

Thanks Ponce, I will give that a try.

But shouldn't my kernel-3.15.3 sources be automagically detected?

ponce · 07-07-2014, 07:45 AM

no, because as ml4711 said (and as I just checked) the symbol FS_NOCOW_FL is defined in that file from the kernel-headers package and that is looked for in src/vteutils.c

Code:

#include <linux/fs.h>

so you need the kernel-headers package, not the kernel-source (that contains the same file but doesn't place it in /usr/include/linux/fs.h) as I first stated.

and you have to use the kernel-headers package your toolchain (glibc/gcc) has been built with (the versions in -current), you cannot upgrade it to a newer one derived from your custom built kernel.

BroX · 07-07-2014, 07:48 AM

Thanks ml4711,

Code:

$ grep FS_NOCOW_FL /usr/include/linux/fs.h 
$

Apparently that symbol has been removed in later kernels?

Isn't upgrading kernel headers (the package) going to give a mess since I am running another kernel version?

ponce · 07-07-2014, 07:52 AM

Alien's wiki - Building a Linux Kernel from source - Slackware kernel-headers package

ml4711 · 07-07-2014, 07:57 AM

kernel-headers should be those glibc is build against,
so You should upgrade kernel-headers

BroX · 07-07-2014, 08:07 AM

Code:

...
Slackware package /tmp/vte3-0.36.3-x86_64-1_SBo.tgz created.

Sweet

Thanks! Learned something again!