From: Christian Kujau on
Hello,

I could not find this anywhere reported, so here it goes:

when is enabled, gcc-4.0.3 (ubuntu/dapper, x86_64) gives:

fs/built-in.o: In function `init_nfs_fs':inode.c:(.init.text+0x16a9): undefined reference to `__fscache_register_netfs'
:inode.c:(.init.text+0x1757): undefined reference to `__fscache_unregister_netfs'

see the full error here:
http://nerdbynature.de/bits/2.6.18-rc6-mm2/make.log

I suspect a missing "#include <linux/fscache.h>" but could not find out
where yet :(

Thanks,
Christian.
--
BOFH excuse #96:

Vendor no longer supports the product
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Christian Kujau on
On Sun, 17 Sep 2006, Christian Kujau wrote:
> when is enabled, gcc-4.0.3 (ubuntu/dapper, x86_64) gives:
------^ uh, that should read:

"when CONFIG_NFS_FSCACHE is enabled..."

The diff to the old-and-working-config is here:
http://nerdbynature.de/bits/2.6.18-rc6-mm2/config.diff

Christian.
--
BOFH excuse #50:

Change in Earth's rotational speed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: David Howells on
Christian Kujau <evil(a)g-house.de> wrote:

> I could not find this anywhere reported, so here it goes:
>
> when is enabled, gcc-4.0.3 (ubuntu/dapper, x86_64) gives:
>
> fs/built-in.o: In function `init_nfs_fs':inode.c:(.init.text+0x16a9): undefined reference to `__fscache_register_netfs'
> :inode.c:(.init.text+0x1757): undefined reference to `__fscache_unregister_netfs'

It looks like your build failed to build the fscache facility or built it as a
module but build NFS directly into the kernel. What's your full configuration?

David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: David Howells on

Hmmm... It looks like a configurator problem:

warthog>grep 'NFS\|CACHE' .config
CONFIG_X86_L1_CACHE_BYTES=128
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_INTERNODE_CACHE_BYTES=128
# CONFIG_IP_ROUTE_MULTIPATH_CACHED is not set
CONFIG_IRDA_CACHE_LAST_LSAP=y
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
CONFIG_FS_MBCACHE=y
---> CONFIG_FSCACHE=m
# CONFIG_CACHEFILES is not set
---> CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_FSCACHE=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_NCPFS_NFS_NS=y

I'm not sure what I can do about that. NFS_FS doesn't depend on FSCACHE, and
so isn't forced to become a module when FSCACHE is. The dependency is through
one of NFS's configuation options.

David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Christian Kujau on
Hello David,

On Fri, 22 Sep 2006, David Howells wrote:
> ---> CONFIG_FSCACHE=m
> # CONFIG_CACHEFILES is not set
> ---> CONFIG_NFS_FS=y
[...]
> I'm not sure what I can do about that. NFS_FS doesn't depend on FSCACHE, and
> so isn't forced to become a module when FSCACHE is. The dependency is through
> one of NFS's configuation options.

I'll try to build with different settings (CONFIG_FSCACHE=y and will
look at the Kconfig for this one again, only my (faster) build-machine
is offline right now...

Thanks,
Christian.
--
BOFH excuse #378:

Operators killed by year 2000 bug bite.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/