public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@NexGo.DE>
To: cygwin@cygwin.com
Subject: Re: cygwin 1.7.15: svn disk I/O error
Date: Wed, 27 Jun 2012 14:07:00 -0000	[thread overview]
Message-ID: <loom.20120627T133520-888@post.gmane.org> (raw)
In-Reply-To: <87a9zqj6b7.fsf@Rainer.invalid>

Achim Gratz <Stromeko <at> nexgo.de> writes:
> I'm not near my work machine, so this is from memory...  the test suite
> requires perl modules I didn't have installed and fails most perl tests
> without them — not too worried about this, will install those later this
> week.

The fail is not due to a module missing, but due to the perl dynaloader not
being able to load the DLL produced by the build.  The error message is not
helpful as there's no reason given for why it couldn't load the DLL.  The file
exists and is readable /executable.  However, LDD gives strange output:

# ldd subversion/bindings/swig/perl/native/blib/arch/auto/SVN/_Core/_Core.dll
        ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x772e0000)
        kernel32.dll => /cygdrive/c/Windows/system32/kernel32.dll (0x75c60000)
        KERNELBASE.dll => /cygdrive/c/Windows/system32/KERNELBASE.dll (0x756b0000)
        ??? => ??? (0x587f0000)
        ??? => ??? (0x6c540000)
        ??? => ??? (0x61000000)
        ??? => ??? (0x6b1a0000)
        ??? => ??? (0x615e0000)
        ??? => ??? (0x61ad0000)
        ??? => ??? (0x617d0000)
        ??? => ??? (0x619a0000)
        ??? => ??? (0x617e0000)
        ??? => ??? (0x6c520000)
        ??? => ??? (0x6be20000)
        ??? => ??? (0x6b6a0000)
        ??? => ??? (0x66620000)
        ??? => ??? (0x65030000)
        ??? => ??? (0x64ca0000)
        ??? => ??? (0x60560000)
        ??? => ??? (0x61bf0000)
        ??? => ??? (0x75590000)
        ??? => ??? (0x771d0000)
        ??? => ??? (0x754a0000)

> I've had to comment out the Apache module build since the mod_dav.la
> was nowhere to be found and no Cygwin package provides it.

Even with the changes to the build config by Yaakov trying to build the Apache
module fails for me, now with unresolved symbols of the form "_dav_*".  I've
built without mod_dav to work around that.

> The ephemeral rebase option I posted patches for in cygwin-apps should
> help with that.  Since I should have the same problem, I'll see that I
> can adapt the cygport file to use it.

Rebasing does help.  Failing Perl tests aside (which never start due to the
issue outlined above), all further tests so far are pass.  Judging from the
current progress, I'd think tests will run at least for two more hours.
 

Regards,
Achim.





--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2012-06-27 14:07 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 19:48 Rolf Campbell
2012-06-14 19:55 ` Christopher Faylor
2012-06-14 20:09   ` Rolf Campbell
2012-06-14 22:00   ` Garrison, Jim (ETW)
2012-06-14 22:02     ` Garrison, Jim (ETW)
2012-06-15 10:38     ` Warren Young
2012-06-15 13:24       ` Rolf Campbell
2012-06-15 13:43       ` Rolf Campbell
2012-06-19  9:32 ` Adam Dinwoodie
2012-06-19 19:24   ` Rolf Campbell
2012-06-19 21:19     ` Achim Gratz
2012-06-20  0:22       ` Warren Young
2012-06-20  5:25         ` Achim Gratz
2012-06-26 16:46           ` Achim Gratz
2012-06-26 17:25             ` David Rothenberger
2012-06-26 18:07               ` Achim Gratz
2012-06-27  9:11                 ` Adam Dinwoodie
2012-06-27 14:07                 ` Achim Gratz [this message]
2012-06-27 18:18                   ` David Rothenberger
2012-06-27 18:41                     ` Achim Gratz
2012-06-28 11:49                       ` Achim Gratz
2012-06-28 16:31                         ` David Rothenberger
2012-06-28 19:04                           ` Achim Gratz
2012-06-28 19:27                             ` David Rothenberger
2012-06-28 20:40                               ` Achim Gratz
2012-07-11  6:34                               ` Achim Gratz
2012-07-11  7:07                                 ` marco atzeri
2012-07-11  7:48                                   ` Achim Gratz
2012-07-11 17:19                                     ` marco atzeri
2012-06-28 17:37                     ` Rolf Campbell
2012-06-28 19:11                       ` Achim Gratz
2012-06-28 20:03                         ` Warren Young
2012-06-28 20:35                           ` Achim Gratz
2012-06-28 21:17                             ` Warren Young
2012-06-28 20:37                       ` David Rothenberger
     [not found] <CABVhxxKw8i96668GgHmMyPXCn+nBS8S874Q7wSSHgoer8iiSsw@mail.gmail.com>
2012-08-07  1:10 ` Michael Gundlach
2012-08-07  1:55   ` Warren Young
2012-08-07  1:57     ` Michael Gundlach
2012-08-07  2:42       ` Warren Young
2012-08-07 12:16         ` Michael Gundlach
2012-08-07 17:56         ` David Rothenberger
2012-08-08 13:14           ` Warren Young
2012-08-07  7:00     ` Achim Gratz
2012-08-07  7:38       ` Warren Young
2012-08-07  5:07   ` Christopher Faylor
     [not found]     ` <CABVhxxJ_nsTF3o85nWJsRdMOq38LYr2R9b9H8ATHfNCCqnmbqw@mail.gmail.com>
2012-08-07 14:05       ` Michael Gundlach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20120627T133520-888@post.gmane.org \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).