unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: "62226@debbugs.gnu.org" <62226@debbugs.gnu.org>
Subject: bug#62226: bash-minimal fails to build on x86_64-w64-mingw32
Date: Sat, 01 Apr 2023 11:14:11 +0000	[thread overview]
Message-ID: <w6O3eWqBMn7g1oZS1-4SFahGohlakG_MOkBE-B6MmDutk1DmjEww6mTAeZRRjDSBpnRJbAVv3a1HT1X52cfgB-f0O04WpMyAiVVvloerRMo=@elenq.tech> (raw)
In-Reply-To: <w5ToAECm6QVz81owny9pmPnjKuy2Mf0jVTA17w4HNLw653YowDp9SFpV_cecIsdqzKik9N40o1LqviSIQhSkhSizFHn0exzgxO0Z8ZCZkPA=@elenq.tech>

Hi,

Adding:

```
"ac_cv_header_sys_socket_h=no"
```

To configure flags in the case the target is mingw solves the first issue, but more issues appear.

I have no enough knowledge about autotools to dig into this much further but it looks like we are finding wrong stuff in the configure step:

```
In file included from shell.c:28:
config.h:340:18: error: ‘long long long’ is too long for GCC
  340 | #define intmax_t long long
      |                  ^~~~
config.h:340:23: error: ‘long long long’ is too long for GCC
  340 | #define intmax_t long long
      |                       ^~~~
config.h:343:19: error: duplicate ‘unsigned’
  343 | #define uintmax_t unsigned long long
      |                   ^~~~~~~~
config.h:343:28: error: ‘long long long’ is too long for GCC
  343 | #define uintmax_t unsigned long long
      |                            ^~~~
config.h:343:33: error: ‘long long long’ is too long for GCC
  343 | #define uintmax_t unsigned long long
      |                                 ^~~~
In file included from bashjmp.h:24,
                 from shell.h:25,
                 from shell.c:53:
./include/posixjmp.h:29:21: error: unknown type name ‘sigjmp_buf’
   29 | #  define procenv_t sigjmp_buf
      |                     ^~~~~~~~~~
bashjmp.h:26:8: note: in expansion of macro ‘procenv_t’
   26 | extern procenv_t top_level;
      |        ^~~~~~~~~
./include/posixjmp.h:29:21: error: unknown type name ‘sigjmp_buf’
   29 | #  define procenv_t sigjmp_buf
      |                     ^~~~~~~~~~
bashjmp.h:27:8: note: in expansion of macro ‘procenv_t’
   27 | extern procenv_t subshell_top_level;
      |        ^~~~~~~~~
./include/posixjmp.h:29:21: error: unknown type name ‘sigjmp_buf’
   29 | #  define procenv_t sigjmp_buf
      |                     ^~~~~~~~~~
bashjmp.h:28:8: note: in expansion of macro ‘procenv_t’
   28 | extern procenv_t return_catch; /* used by `return' builtin */
      |        ^~~~~~~~~
./include/posixjmp.h:29:21: error: unknown type name ‘sigjmp_buf’
   29 | #  define procenv_t sigjmp_buf
      |                     ^~~~~~~~~~
bashjmp.h:29:8: note: in expansion of macro ‘procenv_t’
   29 | extern procenv_t wait_intr_buf;
      |        ^~~~~~~~~
In file included from shell.h:28,
                 from shell.c:53:
/gnu/store/7b119byi86gb3ab5x87ld9fz5xg5bwyd-mingw-w64-x86_64-10.0.0/include/ctype.h:144:13: error: expected identifier or ‘(’ before ‘int’
  144 | int __cdecl isblank(int _C);
      |             ^~~~~~~
syntax.h:103:27: error: expected ‘)’ before ‘==’ token
  103 | #  define isblank(x) ((x) == ' ' || (x) == '\t')
      |                           ^~
In file included from shell.h:29,
                 from shell.c:53:
general.h:33:12: fatal error: sys/resource.h: No such file or directory
   33 | #  include <sys/resource.h>
      |            ^~~~~~~~~~~~~~~~
compilation terminated.
```


ElenQ Technology
Ethical Innovation




      reply	other threads:[~2023-04-01 11:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 19:50 bug#62226: bash-minimal fails to build on x86_64-w64-mingw32 Ekaitz Zarraga
2023-04-01 11:14 ` Ekaitz Zarraga [this message]

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to='w6O3eWqBMn7g1oZS1-4SFahGohlakG_MOkBE-B6MmDutk1DmjEww6mTAeZRRjDSBpnRJbAVv3a1HT1X52cfgB-f0O04WpMyAiVVvloerRMo=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=62226@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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