This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Help with binutils-cvs 2002-02-15 test results interpretation on sparc-linux


Thanks for your reply. Let me see if I got it somewhat correct.

Let's start with just gcc and binutils.

You have the gcc cvs source tree, in my case /share1/gcc-dev/gcc
and the binutils cvs source tree, in my case /share1/gcc-dev/src

Now, in the gcc tree, that’s is in the dir /share1/gcc-dev/gcc I make
symbolic links to binutil's cvs tree.

Like this, in my case:

cd /share1/gcc-dev/gcc
ln -s ../sourceware/src/bfd
ln -s ../sourceware/src/binutils
ln -s ../sourceware/src/gas
ln -s ../sourceware/src/gprof
ln -s ../sourceware/src/ld
ln -s ../sourceware/src/opcodes
cd include
ln -s ../../sourceware/src/include/aout
ln -s ../../sourceware/src/include/bfdlink.h
ln -s ../../sourceware/src/include/bin-bugs.h
ln -s ../../sourceware/src/include/bout.h
ln -s ../../sourceware/src/include/callback.h
ln -s ../../sourceware/src/include/coff
ln -s ../../sourceware/src/include/dis-asm.h
ln -s ../../sourceware/src/include/elf
ln -s ../../sourceware/src/include/filenames.h
ln -s ../../sourceware/src/include/fopen-same.h
ln -s ../../sourceware/src/include/ieee.h
ln -s ../../sourceware/src/include/opcode
ln -s ../../sourceware/src/include/progress.h
ln -s ../../sourceware/src/include/remote-sim.h

(not libgloss and not ld twice, right?)

The others will have to do. I'll try these.

Cheers,

/ChJ

-----Original Message-----
From: nickc@north-pole.nickc.cambridge.redhat.com
[mailto:nickc@north-pole.nickc.cambridge.redhat.com] On Behalf Of Nick
Clifton
Sent: den 16 januari 2002 11:33
To: chj@foi.se
Cc: binutils@sources.redhat.com
Subject: Re: Help with binutils-cvs 2002-02-15 test results
interpretation on sparc-linux


Hi Christian,

> - Are there scripts in the binutils cvs similar to gcc_update and
>   test_summary available in the gcc cvs sources?

Nope :-(

> - Can I somehow automatically "merge" the binutils and gcc cvs
>   sources so that I can test compile and check the two sources
>   jointly?

Yes, but it takes a little work.  What you do is to check out the
sources separately and then in the FSF GCC tree you make some symbolic
links to the sourceware tree.  Then you can just use the configure
script at the top level of the FSF tree to create a complete build
directory hierarchy.  You only need to make the symbolic links once, but
the two trees are still independent, so you need to "cvs update" then
separately.

The links that I make are:

   cd FSF-gcc
   ln -s ../sourceware/src/bfd .
   ln -s ../sourceware/src/binutils .
   ln -s ../sourceware/src/gas .
   ln -s ../sourceware/src/gprof .
   ln -s ../sourceware/src/ld .
   ln -s ../sourceware/src/libgloss .
   ln -s ../sourceware/src/opcodes .
   ln -s ../sourceware/src/ld .
   cd include
   ln -s ../../sourceware/src/include/aout .
   ln -s ../../sourceware/src/include/bfdlink.h .
   ln -s ../../sourceware/src/include/bin-bugs.h .
   ln -s ../../sourceware/src/include/bout.h .
   ln -s ../../sourceware/src/include/callback.h .
   ln -s ../../sourceware/src/include/coff .
   ln -s ../../sourceware/src/include/dis-asm.h .
   ln -s ../../sourceware/src/include/elf .
   ln -s ../../sourceware/src/include/filenames.h .
   ln -s ../../sourceware/src/include/fopen-same.h .
   ln -s ../../sourceware/src/include/ieee.h .
   ln -s ../../sourceware/src/include/opcode .
   ln -s ../../sourceware/src/include/progress.h .
   ln -s ../../sourceware/src/include/remote-sim.h .

 
I also make some links to other, sourceware based packages:

   cd FSF-gcc
   ln -s ../sourceware/src/gdb .
   ln -s ../sourceware/src/libgloss .
   ln -s ../sourceware/src/newlib .
   ln -s ../sourceware/src/sim .


Cheers
        Nick



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]