From: Stafford Horne <shorne@gmail.com>
To: Joel Stanley <joel@jms.id.au>
Cc: openrisc@lists.librecores.org, Nicolas Boulenguez <nicolas@debian.org>
Subject: Re: Link failure with Debian toolchain
Date: Fri, 3 Jun 2022 05:01:09 +0900 [thread overview]
Message-ID: <YpkXBWWyWSG6XwoO@antec> (raw)
In-Reply-To: <CACPK8XcmXLGyn+2BK-nthgVyo5U9SEr+jaw8GJbZTK6Fhy7mfw@mail.gmail.com>
On Thu, Jun 02, 2022 at 04:52:01AM +0000, Joel Stanley wrote:
> On Mon, 30 May 2022 at 08:27, Joel Stanley <joel@jms.id.au> wrote:
> > Stripping libgcc.a breaks it. I could reproduce by running:
> >
> > or1k-elf-strip lib/gcc/or1k-elf/12/libgcc.a
> >
> > If I then reinstated the original libgcc.a the build succeeded again.
> > I suggest we drop that line from the Debian package.
>
> Nicolas merged my change to remove the strip from the package. Thanks!
>
> I was able to build and boot a kernel with the new version of the
> package 12.1.0-2+1.0.3.
>
> I've proposed a change that enables the or1k target in the Debian
> gdb-multiarch package:
>
> https://salsa.debian.org/gdb-team/gdb/-/merge_requests/11
>
> With a local build of that I'm able to connect to qemu's gdb interface
> and poke at the running machine.
Thanks for getting this sorted out. I have been on vacation for the last 2 weeks
and just following these on my phone but not able to get to a computer and do
any useful investigation.
-Stafford
next prev parent reply other threads:[~2022-06-02 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 23:26 Link failure with Debian toolchain Joel Stanley
2022-05-27 22:38 ` Stafford Horne
2022-05-28 9:51 ` Nicolas Boulenguez
2022-05-30 8:27 ` Joel Stanley
2022-06-02 4:52 ` Joel Stanley
2022-06-02 20:01 ` Stafford Horne [this message]
2022-05-30 7:59 ` Joel Stanley
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=YpkXBWWyWSG6XwoO@antec \
--to=shorne@gmail.com \
--cc=joel@jms.id.au \
--cc=nicolas@debian.org \
--cc=openrisc@lists.librecores.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).