[Mono-bugs] [Bug 618128] New: Problem installing mono-2.6.4.tar.bz2 - A REALLY deep directory was created in the 'tests' directory

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=618128

http://bugzilla.novell.com/show_bug.cgi?id=618128#c0


           Summary: Problem installing mono-2.6.4.tar.bz2 - A REALLY deep
                    directory was created in the 'tests' directory
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.6.x
          Platform: i686
        OS/Version: Linux
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Configuration
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: jdc843 at sccoast.net
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Opera/9.80 (X11; Linux i686; U; en) Presto/2.2.15
Version/10.10

This might not be a bug but I was wondering if anyone was aware of this.

My system is running Linux on a x86 system.
I've had this same problem a few years back while installing mono-2.2 also.

The problem is that there is a directory named
'abcde12345abcde12345abcde12345abcde12345' in mono/tests and it is repeatedly
created under itself for a great many sublevels. If I remember correctly from
mono-2.2, it was about 100 levels deep.
I don't know of or how to use a command that will show me how many levels so I
can't be more specific.

rm -R tests will delete it so no permanent harm done. But Midnight Commander
certainly didn't like it.

I'm guessing that this directory was created during 'make check'



Reproducible: Always

Steps to Reproduce:
1. ./configure
2. make
3. make check
4. make install

Actual Results:  
Just read the details above. I've filled out enough of these text boxes Novell
!

Expected Results:  
N/A

None

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.