bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: Reuben Thomas <rrt@sc3d.org>
Cc: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: [PATCH] Do not decorate symbols as dllexport on Cygwin
Date: Sat, 11 Feb 2023 13:06:04 +0100	[thread overview]
Message-ID: <Y+eErFGr/P4ixh8P@calimero.vinschen.de> (raw)
In-Reply-To: <CAOnWdoh76PbuEeizXruQG5kTa+oMt2=wYW8zpXF3KR6Dg_Ao0A@mail.gmail.com>

On Feb 11 11:36, Reuben Thomas wrote:
> On Fri, 10 Feb 2023 at 14:21, Bruno Haible <bruno@clisp.org> wrote:
> 
> > It complains about the symbols defined in libiconv. This means, you need
> > to invoke the Gnulib module 'iconv' and add $(LIBICONV) or $(LTLIBICONV)
> > to the LDFLAGS.
> >
> 
> Bruno to the rescue again! Many thanks.
> 
> Having added the iconv gnulib module, the Windows build works, but the
> tests, which use a Cython module, are now broken. The actual error is:
> 
> Traceback (most recent call last):
> File "D:\a\recode\recode\tests\pytest", line 135, in main
> module = __import__(base[:-3])
> File "D:/a/recode/recode/tests/./t21_names.py", line 2, in <module>
> import common
> File "D:/a/recode/recode/tests/./common.py", line 10, in <module>
> import Recode
> ImportError: DLL load failed while importing Recode: The specified module
> could not be found.
> 
> I assume that the "DLL load failed" indicates a link error.

If you're sure that the native recode.dll has been built, is it possible
that it's just not found, because it's not in Windows' DLL search path?

Keep in mind that Windows searches DLLs in the OS default paths, in
$PATH, or in the same dir the executable has been started from.
https://learn.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order

So at a guess, you either just have to add the directory where
recode.dll resides to $PATH, or you have to copy the DLL into a path
already in $PATH.


Corinna



  reply	other threads:[~2023-02-11 12:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05 19:43 [PATCH] Do not decorate symbols as dllexport on Cygwin Corinna Vinschen
2023-02-05 20:41 ` Bruno Haible
2023-02-05 20:48   ` Bruno Haible
2023-02-05 21:22   ` Corinna Vinschen
2023-02-06 15:08     ` Corinna Vinschen
2023-02-06 16:36       ` Bruno Haible
2023-02-06 17:37       ` Bruno Haible
2023-02-06 20:04         ` Corinna Vinschen
2023-02-06 20:38           ` Bruno Haible
2023-02-06 20:43             ` Corinna Vinschen
2023-02-06 20:50             ` Reuben Thomas
2023-02-07 13:22               ` Corinna Vinschen
2023-02-07 15:22                 ` Corinna Vinschen
2023-02-10 14:11                   ` Reuben Thomas
2023-02-10 14:21                     ` Bruno Haible
2023-02-11 11:36                       ` Reuben Thomas
2023-02-11 12:06                         ` Corinna Vinschen [this message]
2023-02-11 12:29                           ` Reuben Thomas
2023-02-11 12:40                             ` Corinna Vinschen
2023-02-17  9:30                               ` Reuben Thomas
2023-02-17  9:58                                 ` Corinna Vinschen

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=Y+eErFGr/P4ixh8P@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=rrt@sc3d.org \
    /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).