> Date: Mon, 11 Feb 2008 11:26:41 -0600
> From: Joel Sherrill <[EMAIL PROTECTED]>
> RTEMS applications do not return the exit status
> to the environment. So it will have to print
> pass/fail based on the exit value. I vaguely
> remember this not being a big deal for DejaGNU.
As Dave mentioned,
For some time, the GNU Savannah system has allowed projects to use git
for version control. Last week, I imported all of DejaGnu's CVS
history into git and that is where we are now doing development. It
is wonderful to be CVS-free!
I have checked a ChangeLog entry into the CVS tree to advise peo
On 11 February 2008 21:29, Joel Sherrill wrote:
> We use versioned target names. Do I have to list them all in
> the following section?
>
> =
> # This is a list of toolchains that are supported on this board.
> set_board_info target_install {powerpc-rtems4.9}
Dave Korn wrote:
On 11 February 2008 17:27, Joel Sherrill wrote:
Starting with what I know. This is for the SPARC/SIS
BSP for RTEMS.
To compile:
sparc-rtems4.9-gcc -B${RTEMSBSP_prefix} \
-specs bsp_specs -qrtems -g -O2 -mcpu=cypress \
-c FILE.c
To Link:
sparc-rtems4.9-gcc -B${RTEMSB
On 11 February 2008 17:27, Joel Sherrill wrote:
> Starting with what I know. This is for the SPARC/SIS
> BSP for RTEMS.
>
> To compile:
> sparc-rtems4.9-gcc -B${RTEMSBSP_prefix} \
>-specs bsp_specs -qrtems -g -O2 -mcpu=cypress \
>-c FILE.c
>
> To Link:
> sparc-rtems4.9-gcc -B${RTEMSBSP_
Hi,
I asked on the gcc list but I hope someone here
can help me out. I really do want to be able to
post gcc test results for RTEMS targets.
Starting with what I know. This is for the SPARC/SIS
BSP for RTEMS.
To compile:
sparc-rtems4.9-gcc -B${RTEMSBSP_prefix} \
-specs bsp_specs -qrtems -g
Hi H-P
> There seems to have been a wholesale s/case/switch/ change some time
> ago, which missed at least in some parts that the switch argument
> must be guarded from arguments starting with a hyphen, or you'd get
> e.g. for cris-elf "make check-binutils
> 'RUNTESTFLAGS=--target_board=cris-sim\{
Hi H-P
> that this is documented as a deliberate omission. (See the automake
> FAQ; it's along the lines of with such a feature, it'd be easy to
> omit or distribute files by mistake. Just silly, if you ask me.)
Yes, agreed.
> I'm not sure how you wish to handle the problem of not introducing
There seems to have been a wholesale s/case/switch/ change some
time ago, which missed at least in some parts that the switch
argument must be guarded from arguments starting with a hyphen,
or you'd get e.g. for cris-elf "make check-binutils
'RUNTESTFLAGS=--target_board=cris-sim\{,-march=v10,-march
Testing HEAD using the gcc testsuite for cris-elf *without* my
local cris-sim.exp revealed an inconsistency in
baseboard_SCRIPTS; cris-sim.exp and at least two other files
aren't installed. To fix it, I searched for an automake feature
corresponding to GNU make $(wildcard baseboards/*.exp) but
not
10 matches
Mail list logo
