mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: libelf-0.175 breaks objtool
Date: Tue, 5 Feb 2019 20:16:11 -0600	[thread overview]
Message-ID: <20190206021611.2nsqomt6a7wuaket@treble> (raw)
In-Reply-To: <20190205133821.1a243836@gandalf.local.home>

On Tue, Feb 05, 2019 at 01:38:21PM -0500, Steven Rostedt wrote:
> Just a FYI.
> 
> After a recent upgrade in debian testing, I was not able to build the
> kernel. I have a custom build of gcc, so I thought it was strange that
> I was getting something like this (took this from the web, as I don't
> have the error anymore with the work around, and currently doing a full
> build):
> 
> objdump: kernel/.tmp_signal.o: unable to initialize decompress status for section .debug_info                       
> objdump: kernel/.tmp_signal.o: unable to initialize decompress status for section .debug_info                       
> objdump: kernel/.tmp_signal.o: file format not recognized                                                           
>   CC      arch/x86/kernel/platform-quirks.o                                                                         
> objdump: arch/x86/kernel/.tmp_ebda.o: unable to initialize decompress status for section .debug_info                
> objdump: arch/x86/kernel/.tmp_ebda.o: unable to initialize decompress status for section .debug_info                
> objdump: arch/x86/kernel/.tmp_ebda.o: file format not recognized                                                    
> objdump: mm/.tmp_swap_slots.o: unable to initialize decompress status for section .debug_info                       
> objdump: mm/.tmp_swap_slots.o: unable to initialize decompress status for section .debug_info                       
> objdump: mm/.tmp_swap_slots.o: file format not recognized                                   

I installed debian testing on a VM, which has libelf 0.175-2, but I
can't recreate.  Can you share your config?

-- 
Josh

  reply	other threads:[~2019-02-06  2:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 18:38 Steven Rostedt
2019-02-06  2:16 ` Josh Poimboeuf [this message]
2019-02-06 17:16   ` Steven Rostedt
2020-04-06 21:07     ` Arnd Bergmann
2020-04-06 22:16       ` Josh Poimboeuf
2020-04-06 22:31         ` Arnd Bergmann
2020-04-07 15:46           ` Arnd Bergmann
2020-04-07 16:32             ` Josh Poimboeuf
2020-04-07 18:44               ` Arnd Bergmann
2020-04-07 19:30                 ` Arnd Bergmann
2020-04-09  7:41                 ` Christoph Hellwig
2020-04-09  8:25                   ` Arnd Bergmann
2020-04-10  0:46                     ` Dave Chinner

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=20190206021611.2nsqomt6a7wuaket@treble \
    --to=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /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

all inboxes | Powered by JetHome®