View previous topic :: View next topic |
Author |
Message |
padoor Advocate


Joined: 30 Dec 2005 Posts: 4185 Location: india
|
Posted: Wed Oct 24, 2007 8:11 am Post subject: Unable to make -j1 KERNEL_SOURCES=/usr/src/linux default. |
|
|
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h: At top level:
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h:35: error: expected declaration specifiers or '...' before 'kmem_cache_t'
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h: In function '__kmem_free_debug':
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h:41: error: 'cache' undeclared (first use in this function)
make[2]: *** [/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/dcache.o] Error 1
make[1]: *** [_module_/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.23-gentoo'
make: *** [default] Error 2
*
* ERROR: net-fs/shfs-0.35-r4 failed.
* Call stack:
* ebuild.sh, line 1695: Called dyn_compile
* ebuild.sh, line 1033: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* shfs-0.35-r4.ebuild, line 58: Called linux-mod_src_compile
* linux-mod.eclass, line 518: Called die
* The specific snippet of code:
* emake HOSTCC="$(tc-getBUILD_CC)" CC="$(get-KERNEL_CC)" LDFLAGS="$(get_abi_LDFLAGS)" \
* ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} \
* || die "Unable to make ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}."
* The die message:
* Unable to make -j1 KERNEL_SOURCES=/usr/src/linux default.
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/net-fs/shfs-0.35-r4/temp/build.log'.
*
* Messages for package net-fs/shfs-0.35-r4:
*
* ERROR: net-fs/shfs-0.35-r4 failed.
* Call stack:
* ebuild.sh, line 1695: Called dyn_compile
* ebuild.sh, line 1033: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* shfs-0.35-r4.ebuild, line 58: Called linux-mod_src_compile
* linux-mod.eclass, line 518: Called die
* The specific snippet of code:
* emake HOSTCC="$(tc-getBUILD_CC)" CC="$(get-KERNEL_CC)" LDFLAGS="$(get_abi_LDFLAGS)" \
* ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} \
* || die "Unable to make ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}."
* The die message:
* Unable to make -j1 KERNEL_SOURCES=/usr/src/linux default.
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/net-fs/shfs-0.35-r4/temp/build.log'.
*
* GNU info directory index is up-to-date.
localhost newdownloads #
what is wrong with kernel sources . i dont understand why shfs fails to emerge. _________________ reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name) |
|
Back to top |
|
 |
John R. Graham Administrator


Joined: 08 Mar 2005 Posts: 10744 Location: Somewhere over Atlanta, Georgia
|
Posted: Wed Oct 24, 2007 11:14 am Post subject: |
|
|
Padoor, I don't think that there's anything wrong with the kernel sources. It's not referring to the kernel source directory when it fails. Can you look through the compile log to make sure that you've found the topmost build error?
- John |
|
Back to top |
|
 |
padoor Advocate


Joined: 30 Dec 2005 Posts: 4185 Location: india
|
Posted: Wed Oct 24, 2007 2:33 pm Post subject: |
|
|
localhost net-fs # cat /var/tmp/portage/net-fs/shfs-0.35-r4/temp/build.log
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found kernel object directory:
* /lib/modules/2.6.23-gentoo/build
* Found sources for kernel version:
* 2.6.23-gentoo
* Checking for suitable kernel configuration options... [ ok ]
>>> Unpacking source...
>>> Unpacking shfs-0.35.tar.gz to /var/tmp/portage/net-fs/shfs-0.35-r4/work
* Applying df.patch ... [ ok ]
* Applying shfs-0.35-2.6.18-dentry.patch ... [ ok ]
* Applying shfs-0.35-clean-inode-clear.patch ... [ ok ]
* Applying shfs-0.35-gcc4.patch ... [ ok ]
* Applying shfs-0.35-inode-and-fs.patch ... [ ok ]
* Applying space_chars.patch ... [ ok ]
* Applying uidgid32.patch ... [ ok ]
* Converting shfs-0.35/shfs/Linux-2.6/Makefile to use M= instead of SUBDIRS= [ ok ]
* Applying shfs-0.35-2.6.16-dentry.patch ... [ ok ]
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35 ...
* Preparing shfs module
make -C /usr/src/linux M=/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6 modules
make[1]: Entering directory `/usr/src/linux-2.6.23-gentoo'
CC [M] /var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/dcache.o
In file included from /var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/dcache.c:24:
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_fs.h:82: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_fs.h:83: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_fs.h:84: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_fs.h:85: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
In file included from /var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/dcache.c:26:
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h:22: error: expected declaration specifiers or '...' before 'kmem_cache_t'
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h: In function '__kmem_malloc_debug':
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h:25: error: 'cache' undeclared (first use in this function)
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h:25: error: (Each undeclared identifier is reported only once
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h:25: error: for each function it appears in.)
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h: At top level:
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h:35: error: expected declaration specifiers or '...' before 'kmem_cache_t'
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h: In function '__kmem_free_debug':
/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/shfs_debug.h:41: error: 'cache' undeclared (first use in this function)
make[2]: *** [/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6/dcache.o] Error 1
make[1]: *** [_module_/var/tmp/portage/net-fs/shfs-0.35-r4/work/shfs-0.35/shfs/Linux-2.6] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.23-gentoo'
make: *** [default] Error 2
*
* ERROR: net-fs/shfs-0.35-r4 failed.
* Call stack:
* ebuild.sh, line 1695: Called dyn_compile
* ebuild.sh, line 1033: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* shfs-0.35-r4.ebuild, line 58: Called linux-mod_src_compile
* linux-mod.eclass, line 518: Called die
* The specific snippet of code:
* emake HOSTCC="$(tc-getBUILD_CC)" CC="$(get-KERNEL_CC)" LDFLAGS="$(get_abi_LDFLAGS)" \
* ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} \
* || die "Unable to make ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}."
* The die message:
* Unable to make -j1 KERNEL_SOURCES=/usr/src/linux default.
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/net-fs/shfs-0.35-r4/temp/build.log'.
*
localhost net-fs #
i dont find any extra info in the log _________________ reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name) |
|
Back to top |
|
 |
John R. Graham Administrator


Joined: 08 Mar 2005 Posts: 10744 Location: Somewhere over Atlanta, Georgia
|
Posted: Wed Oct 24, 2007 4:06 pm Post subject: |
|
|
Padoor, it's building fine against my 2.6.20 kernel. Apparently there's a reason why the 2.6.23 kernel is still hard masked. Have you tried emerging shfs against a stable branch kernel?
- John |
|
Back to top |
|
 |
padoor Advocate


Joined: 30 Dec 2005 Posts: 4185 Location: india
|
Posted: Thu Oct 25, 2007 1:48 am Post subject: |
|
|
i have kernel-2.6.21-gentoo-r2
i can try eselect set default to /usr/src/linux and try to emerge shfs again.
else i have to emerge 2.6.20 mostly i may not find the patches in portage.
untill recently i had kept all bzImages in /boot from 2.5.15 ... 2.6.23
just last week only i cleaned out un ecessaary files for space.
tough luck this new kernel i got configured to work with my laptop with all frills like ntfs writing acpi brightnesscontrol sound and all.
i will try to emegre shfs for 2.6.21 first and then try to get 2.6.20
thanks for your post john_r_graham
i would never have thought the kernel itself is giving this problem.  _________________ reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name) |
|
Back to top |
|
 |
John R. Graham Administrator


Joined: 08 Mar 2005 Posts: 10744 Location: Somewhere over Atlanta, Georgia
|
Posted: Thu Oct 25, 2007 2:25 pm Post subject: |
|
|
Filesystems are very kernel centric. Any time you're dealing with a filesystem, you'll at least be dealing with kernel header files. In this case, the build messages indicated that it was reaching into the kernel source tree for something. That was my clue.
- John |
|
Back to top |
|
 |
padoor Advocate


Joined: 30 Dec 2005 Posts: 4185 Location: india
|
Posted: Fri Oct 26, 2007 2:32 am Post subject: |
|
|
in my desktop 2 installations have 2.6.20 kernel and shfs emerge fine in both of them.
is it enough to copy /usr/src/linux=2.6.20-gentoo to laptop/usr/src/
and male && make modules_install
that may save downloading of sources and patches. _________________ reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name) |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|