linux-um archives
 help / color / mirror / Atom feed
From: Ritesh Raj Sarraf <rrs@researchut.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Build failure on new gcc-6 on Debian Sid
Date: Sat, 03 Dec 2016 23:50:53 +0530	[thread overview]
Message-ID: <1480789253.13532.5.camel@researchut.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2948 bytes --]

Hi,

On Debian Sid (Unstable), with Linux version 4.8.11, I was hopeful that uml
would build proper with gcc-6. But I still am getting the below mentioned build
failure.

The 4.8.11 kernel has the fixes for the core kernel. I'm not sure if any extra
changes are needed for UM again.

The current workaround that we use in Debian to build latest UML bits from the
kernel source, is to use the gcc-5 compiler.

The Debian bug report is accessible at:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837579

Thanks,
Ritesh


The fix that went in the stable release is:
http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git/commit/?id=a
fad7e0e67ef545a4d92507a236f0666c33d3ad4

  CC [M]  lib/cordic.o
  CC [M]  lib/asn1_decoder.o
  GEN     lib/oid_registry_data.c
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = "en_IN:en",
        LC_ALL = (unset),
        LC_TIME = "en_IN.utf8",
        LC_MONETARY = "en_IN.utf8",
        LC_COLLATE = "C",
        LC_MEASUREMENT = "en_IN.utf8",
        LC_NUMERIC = "C",
        LC_PAPER = "en_IN.utf8",
        LANG = "C"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("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
/usr/bin/ld: arch/um/drivers/built-in.o: relocation R_X86_64_32 against
`.rodata.str1.1' can not be used when making a shared object; recompile with
-fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
Makefile:955: recipe for target 'vmlinux' failed
make[1]: *** [vmlinux] Error 1
make[1]: Leaving directory '/build/user-mode-linux-4.8-1um/linux-source-4.8'
debian/rules:76: 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
E: Failed autobuilding of package
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//25270 and its subdirectories
23:15 ♒♒♒    ☹  => 1  
rrs@chutzpah:~/Community/Packaging/user-mode-linux (master)$



-- 
Given the large number of mailing lists I follow, I request you to CC
me in replies for quicker response

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 203 bytes --]

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

[-- Attachment #3: Type: text/plain, Size: 194 bytes --]

_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

             reply	other threads:[~2016-12-03 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-03 18:20 Ritesh Raj Sarraf [this message]
2016-12-12 16:32 ` [uml-devel] Build failure on new gcc-6 on Debian Sid Richard Weinberger
2016-12-12 19:10   ` Ritesh Raj Sarraf
2016-12-12 20:28     ` Richard Weinberger

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=1480789253.13532.5.camel@researchut.com \
    --to=rrs@researchut.com \
    --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