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: Thu, 28 Jun 2012 19:04:00 -0000	[thread overview]
Message-ID: <87wr2rs1fn.fsf@Rainer.invalid> (raw)
In-Reply-To: <4FEC86D2.2060308@acm.org>

David Rothenberger writes:
>> I can't seem to get this working.  There are a few warnings, but nothing that
>> would explain such a massive fail.  Would you mind posting the ldd output for
>> your _Core.dll?
>
> % ldd /usr/lib/perl5/vendor_perl/5.10/i686-cygwin/auto/SVN/_Core/_Core.dll
>         ntdll.dll => /c/Windows/SysWOW64/ntdll.dll (0x772f0000)
[...]
>         cygsvn_diff-1-0.dll => /usr/bin/cygsvn_diff-1-0.dll (0x67df0000)
>         ??? => ??? (0x770000)

Hmm.  This is an installed version of the same library, not the one from
the build directory... note also that I build for Perl 5.14 in case that
makes a difference.  Looking at the addresses from my library I know
where cygwin1.dll is and it is already in a different place.  I could
look up all the other libraries in the rebase database to find what they
are.  I have no idea what the unresolved addresses above 0x70000000 are
and I see you also have one of these, so maybe this is normal.  Anyway,
I still don't know when and why ldd decides to show you "???" and if
that relates to the problem with DynaLoader.

Any way, I think those "???" are a red herring, I've built on my home
machine and there it works, even though I have those "???"  entries as
well (albeit in total much less lines, but this is a Win7/64 machine
vs. Win7/32bit at work and perl 5.10).

>> I was still missing a -devel package.  Once installed, the Apache modules build
>> and, more importantly link.
>
> Which -devel package was missing? cygport should have warned you
> about missing build dependencies.

I updated some other packages (libserf) as well, so I don't know which
one it was exactly, but I think it might have been openldap-devel.
Interestingly enough it was the linking step that failed, not the
compilation, so the header files must already have been present via some
other package.

Gnome-keyring requires pkg-config during the configure step, not
requested by the cygport file.  

Ruby tests are still failing because it looks for the extension
libraries in a different directory than where they really are.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


--
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

  reply	other threads:[~2012-06-28 19:04 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
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 [this message]
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=87wr2rs1fn.fsf@Rainer.invalid \
    --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).