All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denys@ti.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: <meta-ti@lists.yoctoproject.org>
Subject: Re: ti-cgt6x bundling libc.a with unreadable ELF file header
Date: Wed, 12 Feb 2020 15:08:11 -0500	[thread overview]
Message-ID: <20200212200811.GE30768@beryl> (raw)
In-Reply-To: <CAMKF1sqBztnkEciT045JbkeYyacjCe91b3FNCkv8k77DLEY=-g@mail.gmail.com>

On Sun, Feb 09, 2020 at 10:26:44AM -0800, Khem Raj wrote:
> Hi
> 
> Recently, I am seeing below packaging error for ti-cgt6x
> 
> https://errors.yoctoproject.org/Errors/Details/390526/

Is this on master? Any specific configuration I should use to get this error? 
I don't think I've ever seen this before or lately...


> eu-readelf also fails to read this file as well as binutils readelf
> also complains
> 
> readelf: Error:
> /mnt/b/yoe/build/tmp/work/armv7vet2hf-neon-yoe-linux-musleabi/ti-cgt6x/1_8.3.2-r0/package/usr/share/ti/cgt-c6x/lib/libc.a(__TI_$$LIBINFO):
> Failed to read file header
> 
> this libc.a is a binary blob so I cant find out how it is. built so
> pinpoint where the problem
> could be.
> 
> since these are DSP blobs should this be ignored from processing and
> just dumped into rootfs
> this will help packager turn a blind eye towards its contents or
> should this be fixed and turned into
> a readable ELF file by normal binutils. I doubt it being a problem
> with tools, since I see same issue
> with elfutils tools as well as binutils ELF manipulation tools.
> 
> Thanks
> -Khem

  reply	other threads:[~2020-02-12 20:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09 18:26 ti-cgt6x bundling libc.a with unreadable ELF file header Khem Raj
2020-02-12 20:08 ` Denys Dmytriyenko [this message]
2020-02-12 22:19   ` Khem Raj
2020-02-20  2:43     ` Denys Dmytriyenko
2020-02-20  2:57       ` Khem Raj

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=20200212200811.GE30768@beryl \
    --to=denys@ti.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=raj.khem@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.