Re: isremote and unix board special handling question

2018-11-27 Thread Ben Elliston
Hi Steve > if {[info exists env(DEJAGNU_UNIX_SYSROOT_FLAGS)]} { > set_board_info ldflags "$env(DEJAGNU_UNIX_SYSROOT_FLAGS)" > } Why not just put this into site.exp? append LDFLAGS $env(DEJAGNU_UNIX_SYSROOT_FLAGS) As Jacob indicated, a new baseboard is the wrong hammer. Cheers, Ben signat

Re: isremote and unix board special handling question

2018-11-27 Thread Ben Elliston
On Tue, Nov 27, 2018 at 06:53:17PM -0600, Jacob Bachmeyer wrote: > As we see, set_board_info only works if the specified /entry/ has not > already been defined. That is consistent with the manual: @node set_board_info procedure, [...] This checks if @code{board_info} array's field @emph{entr

Re: isremote and unix board special handling question

2018-11-27 Thread Jacob Bachmeyer
Steve Ellcey wrote: I have a question about the special handling of the 'unix' name in dejagnu. I am doing some GCC testing which uses dejagnu and I want to create a new baseboard (unix-sysroot) which is just like unix but sets ldflags so I can run GCC with a newly built glibc in a non-standard

isremote and unix board special handling question

2018-11-27 Thread Steve Ellcey
I have a question about the special handling of the 'unix' name in dejagnu. I am doing some GCC testing which uses dejagnu and I want to create a new baseboard (unix-sysroot) which is just like unix but sets ldflags so I can run GCC with a newly built glibc in a non-standard location. Specifical