Menu

#13 ObjectIcon 2.6 test issue

Closed
nobody
None
Medium
Defect
2014-04-04
2011-12-09
Anonymous
No

Originally created by: grshiplett

What steps will reproduce the problem?
1. make test
2.
3.

What is the expected output? What do you see instead?

tpp:
tpp.err tpp.stde differ: byte 487, line 11

What version of the product are you using? On what operating system?
2.6
What C compiler are you using, and what version?
Cygwin gcc

Please provide any additional information below.
ieval  has some oddities with no refreshing the > prompt
ivib good in xwin session when from an xterm

Discussion

  • Anonymous

    Anonymous - 2011-12-09

    Originally posted by: r.parl...@gmail.com

    Could you post the file tpp.err, which hopefully should be left in the test directory after running make test.  I can then see how it differs from tpp.stde.

    Many thanks.

    Status: Accepted

     
  • Anonymous

    Anonymous - 2012-01-19

    Originally posted by: r.parl...@gmail.com

    Without further info there's not much I can do about this, so if I don't hear anything I'll assume it has resolved itself.

     
  • Anonymous

    Anonymous - 2012-01-19

    Originally posted by: grshiplett

    I have been ill for days ... but I will try to get this up on a PC
    when I am able

    Robert

     
  • Anonymous

    Anonymous - 2012-01-20

    Originally posted by: r.parl...@gmail.com

    Very sorry to hear that, hope you feel better soon.

    Kind regards,
    R

     
  • Anonymous

    Anonymous - 2014-04-04

    Originally posted by: r.parl...@gmail.com

    Further information reveals the problem to be a warning message issued by cygwin (on stderr), which ends up in the test output file, tpp.err.  The message is self-explanatory :-

    cygwin warning:
      MS-DOS style path detected: abc\def\ghi#jkl\#mno\\pqr stu
      Preferred POSIX equivalent is: abc/def/ghi#jkl/#mno//pqr stu
      CYGWIN environment variable option "nodosfilewarning" turns off this warning.
      Consult the user's guide for more details about POSIX paths:
        http://cygwin.com/cygwin-ug-net/using.html#using-pathnames

    So this test failure can be ignored, or the mentioned environment variable can be set if desired to ensure the test passes okay.

    Status: Closed

     

Log in to post a comment.