octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #33736] ./configure on MinGW / WinXP introduce


From: anonymous
Subject: [Octave-bug-tracker] [bug #33736] ./configure on MinGW / WinXP introduces hard disk "errors"
Date: Sat, 09 Jul 2011 20:34:53 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6

URL:
  <http://savannah.gnu.org/bugs/?33736>

                 Summary: ./configure on MinGW / WinXP introduces hard disk
"errors"
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Sat Jul  9 20:34:52 2011
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Other
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.4.2
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

The configure script, when run under MinGW/MSYS on Windows-XP, introduces a
hard disk "error". While trying to "check if rename manages hard links
correctly" a systray message pops up:

"conftest.exe - Corrupt file"

and on reboot a chkdsk is performed.
(The latter is nasty on 150 GB NTFS partitions with > 250,000 files on it.
Takes ages to complete).

I think there are no real disk errors introduced, it's just that configure's
rename/hard link test under MinGW/MSYS seems to confuse Windows' HD disk
driver so that it sets the "dirty" flag.
Tatsuro reported that he didn't see this anymore on Windows 7.

Nevertheless, as it is known that hard links don't exist on Windows, this
configure test had better be left out when ./configure detects it runs under
Windows or MinGW (is that at all possible?)
Or could a configure option "--enable-MinGW" or so be added to avoid this
test?

BTW I didn't hit this issue when building additional tools and dependencies
(which also invoke configure).





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?33736>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]