bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: Corinna Vinschen <vinschen@redhat.com>
Cc: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: [PATCH] Do not decorate symbols as dllexport on Cygwin
Date: Fri, 17 Feb 2023 09:30:44 +0000	[thread overview]
Message-ID: <CAOnWdojGcq6Lea7ZA_RTsnHyS2m-PG48aFozt8YMcuBRtp4-mg@mail.gmail.com> (raw)
In-Reply-To: <Y+eMoLWtsK6MxK6l@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

On Sat, 11 Feb 2023 at 12:40, Corinna Vinschen <vinschen@redhat.com> wrote:

> On Feb 11 12:29, Reuben Thomas wrote:
> > On Sat, 11 Feb 2023 at 12:06, Corinna Vinschen <vinschen@redhat.com>
> wrote:
> >
> > >
> > > 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?
> > >
> > >
> > Yes, because it was working fine before, and I've not changed anything
> > about where it is built.
>
> Uhm, ok, but... given you didn't build with -no-undefined yet, I'm
> pretty sure libtool only built a static librecode.a, so there's a good
> chance cython was linked statrically against the recode lib, no?
>

Thanks, that was the answer; adding the DLL's build directory to PATH on
Windows fixes the tests.

I have some issues with building dependencies of Recode on Debian to
investigate, and then I'll make another release.

-- 
https://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1872 bytes --]

  reply	other threads:[~2023-02-17  9:31 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
2023-02-11 12:29                           ` Reuben Thomas
2023-02-11 12:40                             ` Corinna Vinschen
2023-02-17  9:30                               ` Reuben Thomas [this message]
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=CAOnWdojGcq6Lea7ZA_RTsnHyS2m-PG48aFozt8YMcuBRtp4-mg@mail.gmail.com \
    --to=rrt@sc3d.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=vinschen@redhat.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).