From: Sriharsha Vedurmudi <sriharsha.v@redpinesignals.com>
To: gcc <gcc-help@gcc.gnu.org>
Subject: Need Help.
Date: Mon, 11 Oct 2004 17:50:00 -0000 [thread overview]
Message-ID: <416AC9D7.8000408@redpinesignals.com> (raw)
Hello Group,
I need some help with Deja Gnu for testing a ported version of gcc
for a custom processor. I have downloaded Deja and untarred it into a
directory.
I then ran
./configure
make
make install
as specified in the INSTALL file. So, now Im sure it got installed well.
But how do I run it to verify the custom version of gcc.
My gcc (the one I use for Linux running on AMD Athelon XP 2400) is as below:
bash-2.05b$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --host=i386-redhat-linux --with-system-zlib
--enable-__cxa_atexit
Thread model: posix
gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
bash-2.05b$
When I want to shift to the new ported gcc (whose output I currently use
with a simulator in GDB), I use this shell script:
bash-2.05b$ cat setup
echo "=============================================="
echo "Setting Environment for GCC compiler for RPINE"
echo "=============================================="
export GCC_EXEC_PREFIX=/opt/GNUPlus/rpine/lib/gcc-lib/
export PATH=${GCC_EXEC_PREFIX}/rpine-elf32/3.3:$PATH
export PATH=/opt/GNUPlus/rpine/rpine-elf32/bin:$PATH
export PATH=/opt/GNUPlus/rpine/bin/:$PATH
export LD_LIBRARY_PATH=/opt/GNUPlus/rpine/lib/gdb:${LD_LIBRARY_PATH}
bash-2.05b$source ./setup
That last one was the command I am to give to use the ported gcc instead
of the regular one. The version of this ported gcc is:
bash-2.05b$ source ./setup
==============================================
Setting Environment for GCC compiler for RPINE
==============================================
bash-2.05b$ gcc -v
Reading specs from /opt/GNUPlus/rpine/lib/gcc-lib/rpine-elf32/3.3/specs
Configured with:
/mnt/vsdc416/sankhya/PS/l2333/src/views/support_release-1/gnu/gcc-3.3/configure
--prefix=/opt/GNUPlus/rpine --target=rpine-elf32 --enable-languages=c
--with-gnu-as --with-gnu-ld --without-newlib --host=i686-pc-linux-gnu
--with-dwarf2
Thread model: single
gcc version 3.3 20040831 (rpine_support_release-1.0)
bash-2.05b$
Now, I guess, you have a picture of what is going on. I have two
versions of Gcc installed in my system and depending on which target I
am compiling for, I change the path so that, that gcc version is used.
When I configure and make deja, the path is ofcourse for the
AMD-Linux-targetted gcc. But I want to test our "rpine" gcc with this
installation of deja (I hope I am not confusing you). How do I do this?
From my side, I went through Deja site and read all that was written
(at some point it was even suggested that I create a separate user for
the purpose) and all that confused me like hell. Can someone explain the
following in simpler terms.
1. How to run the test suite on a cross-compiler that co-exists with a
native installation? (Refer above to the setup).
2. How to add/delete tests to this suite? (Also, I couldnt see any
test-case programs with it)
3. How do I obtain/store results?
I've done much searching, but all that left me more confused.
Kind regards,
Harsha.
--
*****************************
* Sriharsha Vedurmudi
* Software Engineer
*
* Redpine Signals Inc.
* Gate #395, Plot 87,88
* Sagar Society, Road #2,
* Banjara Hills,
* Hyderabad - 500 034
* www.redpinesignals.com
*
* +91-40-23559911 (Office)
* +91-9849133133 (Mobile)
*****************************
next reply other threads:[~2004-10-11 17:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 17:50 Sriharsha Vedurmudi [this message]
2004-10-13 7:16 ` Muthukumar Ratty
-- strict thread matches above, loose matches on Subject: below --
2007-06-07 12:23 need help ASHA GOWDA
2007-06-07 14:53 ` Ian Lance Taylor
2005-03-21 8:54 arul kumaran
2005-02-08 12:19 Vijayalakshmic
2003-10-01 5:23 cro
2003-10-01 6:10 ` Jeffrey Holle
2003-09-26 11:28 Eitan
2003-09-26 11:34 ` Jon Beniston
2003-07-08 16:16 V Robert
2003-07-09 18:42 ` LLeweLLyn Reese
2002-08-19 10:07 Kitti Kittirutsunetorn
2002-08-19 12:02 ` bjorn rohde jensen
2002-08-19 14:56 ` Oscar Fuentes
2002-08-19 15:29 ` bjorn rohde jensen
2001-07-01 22:30 Need help Martin Kalen
2001-07-01 14:42 Jules FOSSO
2001-07-01 22:02 ` Parameshwari B.
2000-05-02 9:31 need help Claudiu BRASOVEAN
2000-05-02 10:00 ` llewelly
1999-11-05 13:05 Need Help Powell, Sandy
1999-11-30 23:28 ` Powell, Sandy
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=416AC9D7.8000408@redpinesignals.com \
--to=sriharsha.v@redpinesignals.com \
--cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).