From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: David Paterson <dnpaterson@gmail.com>
Cc: Keith Seitz <keiths@redhat.com>, gdb@sourceware.org
Subject: Re: Problem building GDB for sparc-rtems
Date: Thu, 19 May 2011 10:39:00 -0000 [thread overview]
Message-ID: <4DD4F35B.6030704@rtems.org> (raw)
In-Reply-To: <BANLkTimvwvEZqMMAFnWuX9edKThNmwnFHA@mail.gmail.com>
On 05/19/2011 12:11 PM, David Paterson wrote:
> On Thu, May 19, 2011 at 10:49 AM, Ralf Corsepius
> <ralf.corsepius@rtems.org> wrote:
>> On 05/19/2011 10:53 AM, David Paterson wrote:
>>> 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:
>>> cd build.gdb-7.2/
>>> rm -rf *
>>>
>>> ../../GCCSources/gdb-7.2/configure --target=sparc-rtems4.10.0
>> FWIW (should not matter, here): The offical target name is
>> "sparc-rtems4.10".
> Thanks Ralf - I'll change the scripts (although as you say it
> shouldn't make a difference).
All patterns in all binutils, gcc and gdb configuration scripts are
supposed to match on "sparc-rtems*", so it should not actually matter.
>>>> FWIW, I just built sparc-rtems on linux (Fedora 13) without incident from
>>>> the 7.2 tarball, so it should work for you, too.
>> I am building all *-rtems targets fairly frequently without many problems
>> (cf. ftp://ftp.rtems.org/pub/rtems/linux/4.11).
>>
>> However gdb's dependencies are a royal pain and occasionally cause building
>> gdb produce bizarre errors. Which host OS are you using?
> I'm using MinGW under Windows 7. If that's likely to be a problem I could
> set up a VM for Linux.
It likely is a problem.
I am building mingw32 RTEMS packages Canadian-cross under Fedora
c.f. http://www.rtems.org/ftp/pub/rtems/mingw32
http://www.rtems.org/ftp/pub/rtems/mingw32/4.11/rtems-4.11-sparc-rtems4.11-gdb/
contains sparc-rtems4.11-gdb-7.2
(Despite the target name, these packages should also be usable with
rtems4.10.)
> It all looks OK, and the makefiles seem to be sensible, but I'll check through
> it again. I've done a diff between the "sparc-rtems" and "sparc-elf" versions
> of the build and nothing obvious jumps out.
I have no idea. As you correctly found out, sparc-rtems*-gdb and
sparc-elf*-gdb are almost identical.
The only real difference is the official RTEMS packages have patches
applied, which are not in FSF's gdb.
Dunno, if you are using these patches - If so, timestamps could make a
difference.
However none of our patches explain your breakdown.
Ralf
next prev parent reply other threads:[~2011-05-19 10:39 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
2011-05-19 9:49 ` Ralf Corsepius
2011-05-19 10:11 ` David Paterson
2011-05-19 10:39 ` Ralf Corsepius [this message]
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=4DD4F35B.6030704@rtems.org \
--to=ralf.corsepius@rtems.org \
--cc=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