From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: lua-5.3.6-3
Date: Fri, 4 Jun 2021 14:16:16 +0100 [thread overview]
Message-ID: <3743f4f2-af52-7f12-7a68-f3d036d3dbdb@dronecode.org.uk> (raw)
In-Reply-To: <announce.20210601234102.A14C.50F79699@gmail.com>
On 01/06/2021 15:41, Lemures Lemniscati via Cygwin-announce via Cygwin
wrote:
> The following packages have been uploaded to the Cygwin distribution:
>
> * lua-5.3.6-3
> * liblua5.3-5.3.6-3
> * liblua-devel-5.3.6-3
>
> * lua-5.3.6-3-src
> * lua-debuginfo-5.3.6-3
>
> Lua is a powerful, light-weight programming language designed for extending
> applications. Lua is also frequently used as a general-purpose, stand-alone
> language.
Thanks for updating this.
This breaks building our 'lua-lfs' package, I think because that doesn't
use pkgconfig, and assumes that /usr/include/lua.h exists:
> $ cygport lua-lfs.cygport all
>>>> Preparing lua-lfs-1.7.0.2-1.x86_64
>>>> Unpacking source luafilesystem-v1_7_0_2.tar.gz
> *** Info: applying patch 1.7.0.2-cygwin.patch (-p2):
> patching file Makefile
> patching file src/lfs.c
>>>> Preparing working source directory
>>>> Compiling lua-lfs-1.7.0.2-1.x86_64
> gcc -ggdb -O2 -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=4 -fdebug-prefix-map=/wip/cygport-git/lua-lfs/lua-lfs-1.7.0.2-1.x86_64/build=/usr/src/debug/lua-lfs-1.7.0.2-1 -fdebug-prefix-map=/wip/cygport-git/lua-lfs/lua-lfs-1.7.0.2-1.x86_64/src/luafilesystem-1_7_0_2=/usr/src/debug/lua-lfs-1.7.0.2-1 -I/usr/local/include -c -o src/lfs.o src/lfs.c
> src/lfs.c:66:10: fatal error: lua.h: No such file or directory
> 66 | #include <lua.h>
> | ^~~~~~~
> compilation terminated.
> make: *** [<builtin>: src/lfs.o] Error 1
> *** ERROR: make failed
I only noticed this because this is part of the cygport test suite :)
next prev parent reply other threads:[~2021-06-04 13:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 3:20 [ANNOUNCEMENT] lua 5.3.5-1 Yaakov Selkowitz
2021-05-19 22:27 ` [ANNOUNCEMENT] Updated: lua-5.3.6-2 Lemures Lemniscati via Cygwin-announce
2021-05-27 8:49 ` Fergus Daly
2021-05-27 9:52 ` Lemures Lemniscati
2021-05-30 21:38 ` Andrey Repin
2021-05-30 23:30 ` Lemures Lemniscati
2021-05-31 4:12 ` Lemures Lemniscati
2021-05-31 8:54 ` Andrey Repin
2021-05-31 9:26 ` Andrey Repin
2021-05-31 10:41 ` Lemures Lemniscati
2021-06-01 14:39 ` Updated: lua-5.3.6-3 Lemures Lemniscati
2021-06-01 14:41 ` [ANNOUNCEMENT] " Lemures Lemniscati via Cygwin-announce
2021-06-04 13:16 ` Jon Turney [this message]
2021-06-04 16:10 ` Lemures Lemniscati
2021-06-05 22:26 ` [ANNOUNCEMENT] Updated: lua-5.3.6-4 Lemures Lemniscati via Cygwin-announce
2021-05-19 22:47 ` [ANNOUNCEMENT] Test: lua-5.4.3-1 Lemures Lemniscati via Cygwin-announce
2021-06-01 14:46 ` [ANNOUNCEMENT] Test: lua-5.4.3-2 Lemures Lemniscati via Cygwin-announce
2021-06-05 22:36 ` [ANNOUNCEMENT] Test: lua-5.4.3-3 Lemures Lemniscati via Cygwin-announce
2022-03-06 13:29 ` [ANNOUNCEMENT] Test: lua-5.4.4-1 Lemures Lemniscati via Cygwin-announce
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=3743f4f2-af52-7f12-7a68-f3d036d3dbdb@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).