From: Vlasios Tsiatsis <tsiatsis@ee.ucla.edu>
To: gdb@sources.redhat.com
Subject: Re: Intel Xscale GDB
Date: Wed, 16 Jan 2002 17:32:00 -0000 [thread overview]
Message-ID: <3C4629BB.9885C920@ee.ucla.edu> (raw)
In-Reply-To: <3C451CE4.2F06104C@ee.ucla.edu>
Vlasios Tsiatsis wrote:
> Hi all!
> I am reposting this problem in case someone can help me.
>
> I have a question about the source code of the Intel Xscale gdb
> residing in the GNUPro toolkit source bundle.
> I downloaded both versions (010413 and 010827) of the source code from
> Intel's website
> (http://developer.intel.com/design/intelxscale/dev_tools/010827/) and
> tried to build them
> on a RedHat Linux 7.1 machine (kernel 2.4.2-2, processor i686, gcc
> version 2.96).
I found the proper way to fix the problem and here it is.
I assume that you expand the GNUPro source code in a directory called
~/gnupro-src/
leon:/home/tsiatsis>ls -al gnupro-src
drwxr-xr-x 6 tsiatsis DomainUs 4096 Jan 16 11:28 ./
drwx------ 21 tsiatsis DomainUs 4096 Jan 16 12:09 ../
drwxr-xr-x 45 tsiatsis DomainUs 4096 Jan 15 23:19 src/
In order to get the above system to build the GNUPro tools and GDB for
version 010413 you have to do the following:
1) Comment out the lines 39 and 69 from the file src/gdb/devsw.c.
Those lines have the folowing declaration:
struct tm lt;
This declaration is useless since the variable lt is never used in the
scope of the functions that is declared. The compiler complains that
it cannot find the declaration of the type "struct tm" therefore cannot
determine the size of this type.
2) Parallel to the directory src create a directory e.g. build. So ls
in gnupro-src will give you something like the following:
leon:/home/tsiatsis>ls -al gnupro-src
drwxr-xr-x 6 tsiatsis DomainUs 4096 Jan 16 11:28 ./
drwx------ 21 tsiatsis DomainUs 4096 Jan 16 12:09 ../
drwxr-xr-x 33 tsiatsis DomainUs 4096 Jan 16 11:31 build/
drwxr-xr-x 45 tsiatsis DomainUs 4096 Jan 15 23:19 src/
Change to the directory ~/gnupro-src/build and execute the following
leon:/home/tsiatsis/gnupro-src/build>../src/configure
--host=i686-pc-linux-gnulibc2.1 --target=xscale-elf
Of course this configure command line is for the toolchain that deals
with the ELF executables. I haven't tried to produce the corresponding
toolchain for the COFF executables.
Can you please add those clarifications in the README of the GNUPro
toolchain?
>
> I have tried to build them on RedHat Linux 6.2 machine with egcs-2.91.66
> but
> i had no luck.
>
The same installation instructions hold for this system but you can ommit
step 1.
>
> I am having problems compiling the gdb sources because of an error in
> the directory src/gdb/i386-linux-nat.c line 102. A data type called
> "gregset_t" is
> not declared anywhere in any header file and this results in a
> compilation
> error.
> I can see that the "configure" program (in the gdb directory) checks
> whether this type is declared in <sys/procfs.h> and it cannot find the
> type gregset_t in this file.
> In the file <sys/procfs.h> the only type that is similar to gregset_t
> is called elf_gregset_t.
>
vlassis
next prev parent reply other threads:[~2002-01-17 1:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 22:25 Vlasios Tsiatsis
2002-01-16 17:32 ` Vlasios Tsiatsis [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-13 17:41 Intel Xscale gdb Vlasios Tsiatsis
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=3C4629BB.9885C920@ee.ucla.edu \
--to=tsiatsis@ee.ucla.edu \
--cc=gdb@sources.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