>
> 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.
Its not a good idea to use two different gccs with same name but
for different targets (and changing the paths). You should be having a
"rpine-elf32-gcc" also (if things were done properly). Use that one and
life would be less confusing :)
> 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?
But you did :)
Simple law for mailing lists
"Chance of getting a reply increases exponentially with the clarity
of problem statement"
>
> 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.
>
>
