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

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

bug#60563: closed ([PATCH 0/1] Fix mingw cross-compilation of nettle)


From: GNU bug Tracking System
Subject: bug#60563: closed ([PATCH 0/1] Fix mingw cross-compilation of nettle)
Date: Thu, 19 Jan 2023 16:32:01 +0000

Your message dated Thu, 19 Jan 2023 17:31:26 +0100
with message-id <87lelya3kx.fsf_-_@gnu.org>
and subject line Re: bug#60563: [PATCH 0/1] Fix mingw cross-compilation of 
nettle
has caused the debbugs.gnu.org bug report #60563,
regarding [PATCH 0/1] Fix mingw cross-compilation of nettle
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
60563: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60563
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH 0/1] Fix mingw cross-compilation of nettle Date: Thu, 5 Jan 2023 00:36:00 +0100 User-agent: Evolution 3.46.0
Dear guix,

nettle separates its static library output from its main output by moving all
files with a ".a" extension. However, doing that also moves the ".dll.a" files
on mingw. These files are required to link against a DLL. Packages that want
to link against the nettle DLL will require the default output of nettle, and
will not want the static output. So, these files must stay in the default
output.

Best regards,

Vivien

Vivien Kraus (1):
  gnu: nettle: Fix mingw cross-compilation.

 gnu/packages/nettle.scm | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)


base-commit: 658c09333da095edf6e1b3c5e351a7bfa3c87354
-- 
2.38.1



--- End Message ---
--- Begin Message --- Subject: Re: bug#60563: [PATCH 0/1] Fix mingw cross-compilation of nettle Date: Thu, 19 Jan 2023 17:31:26 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Hi Vivien,

Vivien Kraus <vivien@planete-kraus.eu> skribis:

> * gnu/packages/nettle.scm (nettle-2) [move-static-libraries]: .dll.a files are
> not static libraries.

Applied, thanks!

Ludo’.


--- End Message ---

reply via email to

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