Re: Problem building GDB for sparc-rtems

[David Paterson <dnpaterson@gmail.com>]

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).

>> --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.
>
> 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.

> Did you check the output "running configure" produces? Occasionally, such
> build errors have their origin much earilier in the build-process,

I've checked through all the "config.log" files in the build
directory, and none of
them show any errors (apart from the expected ones where configure is
trying to figure out what's working / available).  All of them end with "exit 0"
which looks like a non-error result.

>> 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...
>
> I'd guess on one of the usual supects: Do you have '.' in $PATH? Which
> CFLAGS are you using? Does your pwd contain white spaces?

Ah, "pwd" has no spaces, but $PATH is does start with "." which could be
the cause of it.  I'll try to find where it's set up, although it's derived from
an Eclipse install, so I'm not sure where to look.  Maybe "." should be at the
end instead of the beginning?

> Did you check the output "configure produces"?

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.

Cheers,

David P.