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] |
> As I see it there are two ways to commence this: > > 1) Run 'cpp' (manually) from the test script when testing. I cant assume > that the command 'cpp' is available, right? How can I discover how to > call cpp? (By e.g. using the configuration process results or similar.) > Using "gcc -E"? Other suggestions, please? > > 2) Manually run cpp and store the derived file (.s) into the CVS, > similar to the regenerate mechanisms of Makefile.in from Makefile.am. > Choice two would be better. If you have some way to generate your testcases, that's fine, but you need to check in a testcase that doesn't depend on anything outside of binutils. -eric -- Yeah, I used to play basketball...
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |