On Fri, Aug 25, 2017 at 9:50 AM, Rainer Orth <r...@cebitec.uni-bielefeld.de> wrote: > Hi H.J., > >> On Fri, Aug 25, 2017 at 6:32 AM, David Edelsohn <dje....@gmail.com> wrote: >>> On Fri, Aug 25, 2017 at 9:24 AM, H.J. Lu <hjl.to...@gmail.com> wrote: >>>> On Fri, Aug 25, 2017 at 6:01 AM, David Edelsohn <dje....@gmail.com> wrote: >>>>> FYI, DejaGNU 1.6.1 is not compatible with the GCC Testsuite. The GCC >>>>> Testsuite uses "unsetenv" in multiple instances and that feature has >>>>> been removed from DejaGNU. The testsuite is going to experience >>>>> DejaGNU errors when Fedora or OpenSUSE upgrades to a more recent >>>>> DejaGNU in the 1.6 series. >>>>> >>>> >>>> I am running Fedora 26 with dejagnu-1.6-2.fc26. What should I >>>> look for? >>> >>> ERROR: (DejaGnu) proc "unsetenv GCC_EXEC_PREFIX" does not exist. >>> The error code is NONE >>> The info on the error is: >>> invalid command name "unsetenv" >>> while executing >>> "::tcl_unknown unsetenv GCC_EXEC_PREFIX" >>> ("uplevel" body line 1) >>> invoked from within >>> "uplevel 1 ::tcl_unknown $args" >>> >> >> I checked my log. I didn't see them. Which log file do they appear in? > > unsetenv was only removed after DejaGnu 1.6 was released. The change is > in the git repo; so far there exists no post-1.6 release.
That is why I wrote 1.6.1. I didn't know if 1.6-2 was from snapshot after 1.6. Future releases of DejaGNU will elicit errors from the GCC Testsuite as currently written. My message is a warning about future incompatibility. Thanks, David