From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/RFC] no shared library support warning on powerpc-elf
Date: Fri, 11 May 2007 18:02:00 -0000 [thread overview]
Message-ID: <20070511180155.GB1684@caradoc.them.org> (raw)
In-Reply-To: <20070508221252.GG3798@adacore.com>
On Tue, May 08, 2007 at 03:12:53PM -0700, Joel Brobecker wrote:
> Hello,
>
> When running a program on the powerpc-elf simulator, I get the following
> warning:
>
> (gdb) run
> Starting program: /[...]/ex/other
> !!! -> warning: no shared library support for this OS / ABI
>
> Breakpoint 1, other () at other.adb:12
> 12 end Other;
> In the case of powerpc-elf, GDB links in solib.c and solib-svr4.c.
> I don't think the bareboard case is supported by these units, so
> I think the sensible thing to do is to remove them from the closure
> and not build them.
Except this interferes with using one GDB for both powerpc-elf and
powerpc-linux. So it's not a great solution.
Maybe the warning should simply be removed? I don't think it's very
valuable. If shared library support is really missing, either the
testsuite will catch it or a user will eventually notice.
> Is it possible to run the testsuite? The compilers I have use the
> powerpc-elf- prefix (eg: powerpc-elf-gcc).
Yes, using the powerpc-eabisim board; but it's easier if you build
everything using --target=powerpc-eabisim. powerpc-elf-gcc may need
some additional options, like -msim.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-05-11 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 22:12 Joel Brobecker
2007-05-11 18:02 ` Daniel Jacobowitz [this message]
2007-05-11 22:49 ` Joel Brobecker
2007-05-21 12:52 ` Daniel Jacobowitz
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=20070511180155.GB1684@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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