This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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]

Re: dejagnu version update?


On Fri, Aug 25, 2017 at 9:43 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Fri, Aug 25, 2017 at 6:32 AM, David Edelsohn <dje.gcc@gmail.com> wrote:
>> On Fri, Aug 25, 2017 at 9:24 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
>>> On Fri, Aug 25, 2017 at 6:01 AM, David Edelsohn <dje.gcc@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?

All log files.  I don't know what is different about the invocation of
DejaGNU directives used by testcases on x86 that avoids the problem in
your runs.

One can see references to unsetenv in GCC Testsuite and those are not
valid for DejaGNU 1.6.1+.

- David


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]