[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SIM env. variable question in baseboards

From: Steve Ellcey
Subject: Re: SIM env. variable question in baseboards
Date: Thu, 24 May 2012 17:06:34 -0700

On Thu, 2012-05-24 at 23:34 +0200, Hans-Peter Nilsson wrote:
> > From: "Steve Ellcey " <address@hidden>
> > Date: Thu, 24 May 2012 23:03:22 +0200
> > I am trying to create a generic baseboard file in dejagnu for use in
> > testing GCC with a simulator.
> Most GCC targets already have baseboard files that fit the
> simulators (for newlib targets) that cohabit with gdb, but a
> generic baseboard file is certainly on the wishlist.  (One was
> put together at a gccsummit BOF some years ago, but I guess it
> was lost in action.)
> >  Rather then specify the simulator name
> > in the baseboard I want to use the SIM env. variable, but that does not
> > seem to be working.   Does any one know why?
> Sorry, I don't know the answer to that, I just want to add that
> for a generic baseboard file to be usable please also make the
> dejagnu ldflags adjustable by appending a unique environment
> variable if it exists, something like DEJAGNU_SIM_LDFLAGS.
> Thinking about it, better make the same for all the
> set_board_info options.
> brgds, H-P

So right now my baseboard file has:

set_board_info ldflags "[libgloss_link_flags] [newlib_link_flags]"

Are you thinking of something like:

if {[info exists DEJAGNU_SIM_LDFLAGS]} {
  set_board_info ldflags "$DEJAGNU_SIM_LDFLAGS"
else {
  set_board_info ldflags "[libgloss_link_flags] [newlib_link_flags]"

I might go with SIM_LDFLAGS instead of DEJAGNU_SIM_LDFLAGS just to match
SIM (not DEJAGNU_SIM).  I don't think name pollution is a problem if
these are Tcl variables and not env. variables as Ben indicated in his

Steve Ellcey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]