>>> When build kernel from the source rpm I
>>> get the following depmod failure:
>>>
>>> + depmod -b . -aeF ./System.map 3.16.1-301.fc20.x86_64
>>> + '[' -s depmod.out ']'
>>> + echo 'Depmod failure'
>>> Depmod failure
>>> + cat depmod.out
>>> depmod: WARNING:
/home/steved/rpmbuild/BUILDROOT/kernel-3.16.1-301.fc20.x86_64/./lib/modules/3.16.1-301.fc20.x86_64/kernel/fs/gfs2/gfs2.ko
needs unknown symbol dlm_new_lockspace
>>> depmod: WARNING:
/home/steved/rpmbuild/BUILDROOT/kernel-3.16.1-301.fc20.x86_64/./lib/modules/3.16.1-301.fc20.x86_64/kernel/fs/gfs2/gfs2.ko
needs unknown symbol dlm_unlock
>>> depmod: WARNING:
/home/steved/rpmbuild/BUILDROOT/kernel-3.16.1-301.fc20.x86_64/./lib/modules/3.16.1-301.fc20.x86_64/kernel/fs/gfs2/gfs2.ko
needs unknown symbol dlm_release_lockspace
>>> depmod: WARNING:
/home/steved/rpmbuild/BUILDROOT/kernel-3.16.1-301.fc20.x86_64/./lib/modules/3.16.1-301.fc20.x86_64/kernel/fs/gfs2/gfs2.ko
needs unknown symbol dlm_posix_unlock
>>> depmod: WARNING:
/home/steved/rpmbuild/BUILDROOT/kernel-3.16.1-301.fc20.x86_64/./lib/modules/3.16.1-301.fc20.x86_64/kernel/fs/gfs2/gfs2.ko
needs unknown symbol dlm_posix_get
>>> depmod: WARNING:
/home/steved/rpmbuild/BUILDROOT/kernel-3.16.1-301.fc20.x86_64/./lib/modules/3.16.1-301.fc20.x86_64/kernel/fs/gfs2/gfs2.ko
needs unknown symbol dlm_lock
>>> depmod: WARNING:
/home/steved/rpmbuild/BUILDROOT/kernel-3.16.1-301.fc20.x86_64/./lib/modules/3.16.1-301.fc20.x86_64/kernel/fs/gfs2/gfs2.ko
needs unknown symbol dlm_posix_lock
>>> + exit 1
>>>
>>> What needs to happen to get this fixed? Should I open up a bz or
>>> open up a ticket somewhere? Please tell me where to go... nicely! ;-)
>>
>> Didn't we discuss all of this in #fedora-kernel yesterday? Did the
>> advice we gave there not work, or?
> Yes.. Your advice was to use 'fedpkg local' which does indeed work but
> it also builds a bunch of rpms I don't need or use, like debug kernels.
Which you failed to tell us yesterday. Come on Steve.
> When I rpmbuild from a srpm I use the following flags
> --without extra --without tools --without debug --without perf --without headers
I'm guessing it's the --without extra that's breaking things. gfs2.ko
is typically shoved in the modules-extra package. You aren't actually
saving any build time by passing that, since everything in there is
still getting built. It's just winding up in some other package. We
should probably just remove that config switch because it really
doesn't make sense.
I do the above all the time but I've never used the "--without extra"
so I suspect your correct on that.
Peter