From: Ritesh Raj Sarraf <rrs@researchut.com>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Mattia Dongili <malattia@linux.it>
Subject: Re: [uml-devel] UML build failure on 4.7
Date: Mon, 05 Sep 2016 20:37:52 +0530 [thread overview]
Message-ID: <1473088072.10346.11.camel@researchut.com> (raw)
In-Reply-To: <1473081950.10346.10.camel@researchut.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Disabling drivers/nvdimm (seen only on x86_64 architecture) solved the problem.
On Mon, 2016-09-05 at 18:55 +0530, Ritesh Raj Sarraf wrote:
> Hi,
>
> I'm working on refreshing UML to version 4.7 in Debian.
>
> The linux source tarball we use is from Debian, which is mostly the stock
> kernel.
>
> The build failure I've run into is:
>
> CC [M] lib/ts_fsm.o
> CC [M] lib/lru_cache.o
> CC [M] lib/cordic.o
> CC [M] lib/asn1_decoder.o
> GEN lib/oid_registry_data.c
> CC [M] lib/oid_registry.o
> LD virt/lib/built-in.o
> LD virt/built-in.o
> LINK vmlinux
> LD vmlinux.o
> MODPOST vmlinux.o
> GEN .version
> CHK include/generated/compile.h
> UPD include/generated/compile.h
> CC init/version.o
> LD init/built-in.o
> KSYM .tmp_kallsyms1.o
> KSYM .tmp_kallsyms2.o
> LD vmlinux
> SYSMAP System.map
> LINK linux
> Building modules, stage 2.
> MODPOST 906 modules
> ERROR: "devm_memunmap" [drivers/nvdimm/libnvdimm.ko] undefined!
> ERROR: "devm_memremap" [drivers/nvdimm/libnvdimm.ko] undefined!
> scripts/Makefile.modpost:91: recipe for target '__modpost' failed
> make[2]: *** [__modpost] Error 1
> Makefile:1186: recipe for target 'modules' failed
> make[1]: *** [modules] Error 2
> make[1]: Leaving directory '/build/user-mode-linux-4.7-1um/linux-source-4.7'
> debian/rules:73: recipe for target 'build-stamp' failed
> make: *** [build-stamp] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> I: copying local configuration
> W: No local /etc/resolv.conf to copy, relying on /var/tmp/Debian-
> Build/Build//9419/etc/resolv.conf to be correct
> E: Failed autobuilding of package
> W: no hooks of type C found -- ignoring
> I: unmounting /var/tmp/lxc/ccache/ccache filesystem
> I: unmounting /var/cache/apt/archives/ filesystem
> I: unmounting dev/pts filesystem
> I: unmounting run/shm filesystem
> I: unmounting proc filesystem
> I: unmounting sys filesystem
> I: cleaning the build env
> I: removing directory /var/tmp/Debian-Build/Build//9419 and its subdirectories
>
>
> The same .config builds fine for 4.6. Have others been able to build a 4.7 um
> kernel ?
>
>
- --
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJXzYpIAAoJEKY6WKPy4XVpSQYQAKFD4ltRSAEcv8nOOqqXi8vm
W6QFp4f7QD6xehJ84yOJvOaeYG75l0/K16DaQwfDiOQT1sE4FSDVZ6SJGbvNhKKk
dmRUFzuMAli/LNJamVAfSnHsmPi33UfAPcOB28r/7cKwH1jEHBoBgP7C55VvVIrw
/r3dAJJirD447dj6fkN6qNTlBhuuNIYfq68AGBSmK33eNUMoIgOtcyoq0D2Gkvzr
VcDj2zs36jz3gbSXLdJWxctz4Li5TOsw/EW21r6+tbdogf7dZ1okvm7+dwDWQWrC
U/qb4M43ClYuL1QU4NjngyK9suPdaNBjlMTA63TnucVi0uUxrJlza9NErbRqY33+
4YDMZSEZf9WOTfNMdK3pAT2hyrEtzWP+suCg2u5IKUZu/6fea7sOK7thyCFMDBPV
gOiBFOGpKaFikDVF8b7fheQsSvesi2j38STYvBV4RBCzKuNsRdAHZBQH2sYdxi/0
PfmxSwy8jTschwaaz3NWYWgJUeH20QYSUZFgqrhNBsITud+CXKJDCpHQy8epbls3
aJAfUdZqBeQmw7tJAdUkgKmGgy/B8uF3Jo8s1Cg19QvbGVFyCbIK2SOVaD4w5VFR
rnYlfCxPFzrWqcfHriTRmvVRdFGa4x3Nfor4DocDNlrcpnO7S0j8a5dfVcflZNgc
YGwATQp2ZPTuogWJfCWO
=acar
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2016-09-05 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 13:25 [uml-devel] UML build failure on 4.7 Ritesh Raj Sarraf
2016-09-05 15:07 ` Ritesh Raj Sarraf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1473088072.10346.11.camel@researchut.com \
--to=rrs@researchut.com \
--cc=malattia@linux.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).