public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Houda Benabderrazik" <hbena76@yahoo.fr>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sources.redhat.com
Subject: Re: How to test binutils?
Date: Wed, 05 May 2004 16:49:00 -0000	[thread overview]
Message-ID: <20040505164945.578.qmail@web60402.mail.yahoo.com> (raw)
In-Reply-To: <40991023.9060606@redhat.com>


Thank you very much for your answer Nick, 
Do i have to write all this files before testing any
one?
I want to know if there is the only method for
testing?
So, I can not for example just making a makefile.
Can i test without building cross-target? 

I think, i have to write some other files for ld for
example. 



 --- Nick Clifton <nickc@redhat.com> a écrit : > Hi
Houda,
> 
> >Does anyone know how to build Gas and binutils
> after
> >adding new processor (tc-cpu.c tc-cpu.h)?
> >  
> >
> You will probably need to add more files than these.
>  In particular you 
> will probably need to create these files:
> 
>   bfd/cpu-<name>.c
>   bfd/elf32-<name>.c   [I am assuming that you are
> using the ELF file 
> format]
>   opcodes/<name>-dis.c
>   opcodes/<name>-asm.c
> 
> You will also need to add entries to the
> gas/configure.in, 
> bfd/config.bfd, ld/configure.tgt,
> opcodes/configure.in and 
> opcodes/disassembler.c files, as well as
> regenerating the various 
> */configure files and adding an entry to the top
> level config.sub file.
> 
> As for building GAS and binutils you should try to
> follow the standard 
> procedure for building a cross-targeted toolchain. 
> ie create a separate 
> build directory that is not part of the sources
> directories.  In that 
> directory run the "configure" script from the top
> level of the sources 
> directory and give it a command line switch of
> "--target=<name>-elf".  
> If this succeeds then run "make".  If that passes
> then run "make check".
> 
> >How can i test what the program in Mac OS X?
> >  
> >
> I am not quite sure what you mean here.  If you want
> to test to see if 
> your new code works then the above procedure should
> be a good start.
> 
> Cheers
>   Nick
>  


	

	
		
Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout ! 
Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/

Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez Yahoo! Messenger sur http://fr.messenger.yahoo.com

  reply	other threads:[~2004-05-05 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-30 10:43 Houda Benabderrazik
2004-05-05 15:58 ` Nick Clifton
2004-05-05 16:49   ` Houda Benabderrazik [this message]
2004-05-05 17:30     ` Nick Clifton

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=20040505164945.578.qmail@web60402.mail.yahoo.com \
    --to=hbena76@yahoo.fr \
    --cc=binutils@sources.redhat.com \
    --cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).