Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Paterson <dnpaterson@gmail.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Problem building GDB for sparc-rtems
Date: Thu, 19 May 2011 08:54:00 -0000	[thread overview]
Message-ID: <BANLkTimt0ZJZec8up7Uxx6Q4GGoTJY113w@mail.gmail.com> (raw)
In-Reply-To: <4DD45A0F.4040909@redhat.com>

On Thu, May 19, 2011 at 12:45 AM, Keith Seitz <keiths@redhat.com> wrote:
> On 05/16/2011 09:34 AM, David Paterson wrote:
>
>> This may be more appropriate for the RTEMS, or even Binutils,
>> mailing lists - if so, please let me know and I'll move it over.
>
> It might be, but let's have some fun and see if we can figure it out.

Thanks Keith.  I'm not sure "fun" is the word to use though... :-)

>> I'm trying to build a cross-toolchain for a Sparc (Leon2) system,
>> and while the basic version, configured for "sparc-elf" is no
>> problem, when I try to rebuild for RTEMS I'm getting an error during
>> the GDB build :-
>
> How did you do this? Can you share your build commands? I presume you did
> this in a clean build directory?

I've tried a few different configure options, but the last ones I
tried, which are
still giving the same error, are :-

    cd build.gdb-7.2/
    rm -rf *

    ../../GCCSources/gdb-7.2/configure  --target=sparc-rtems4.10.0
--disable-shared --disable-nls \
    --disable-werror --disable-sim --with-gnu-as --with-gnu-ld
--prefix=/usr/local/SParcRtems

    make all
    make install

(run from a script file, rather than command line, but that also gives the same
result, as I tried it in case there was some script environment problem).

For reference, I'm also using gmp-5.0.1, mpfr-3.0.1, mpc-0.9, binutils-2.21,
gcc-4.5.2 and newlib-1.19.0 (of course not all of those are used for GDB).

> FWIW, I just built sparc-rtems on linux (Fedora 13) without incident from
> the 7.2 tarball, so it should work for you, too.

Interesting.  I'll try building some other targets as well, and see if
it's purely a
Sparc problem.  I should have thought to try that...

Cheers,

David P.


  reply	other threads:[~2011-05-19  8:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 16:35 David Paterson
2011-05-18 23:45 ` Keith Seitz
2011-05-19  8:54   ` David Paterson [this message]
2011-05-19  9:49     ` Ralf Corsepius
2011-05-19 10:11       ` David Paterson
2011-05-19 10:39         ` Ralf Corsepius
2011-05-19 13:07           ` David Paterson
2011-05-19 13:44             ` Joel Sherrill
2011-05-19 14:09               ` David Paterson
2011-05-19 18:51                 ` Keith Seitz
2011-05-20  8:59                   ` David Paterson
2011-05-20 13:05                     ` Joel Sherrill

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=BANLkTimt0ZJZec8up7Uxx6Q4GGoTJY113w@mail.gmail.com \
    --to=dnpaterson@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=keiths@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox