From: Bruno Haible <bruno@clisp.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: "Arsen Arsenović" <arsen@aarsen.me>,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
bug-gettext@gnu.org
Subject: Re: building GNU gettext on AIX
Date: Wed, 15 Nov 2023 22:22:27 +0100 [thread overview]
Message-ID: <4277517.TpOvJl0BfU@nimes> (raw)
In-Reply-To: <CAGWvnynrk1vYXLdur7d1CBGyGrUp2Qoai1NTDZDfMSQkG4o02g@mail.gmail.com>
David Edelsohn wrote:
> When I try to configure gettext-0.22.3, I receive the following error:
>
> checking for socklen_t equivalent... configure: error: Cannot find a type
> to use in place of socklen_t
>
> configure: error:
> /nasfarm/edelsohn/src/gettext-0.22.3/libtextstyle/configure failed for
> libtextstyle
>
>
> configure:43943: /nasfarm/edelsohn/install/GCC12/bin/gcc -c -g -O2
> -D_THREAD_SAFE
> conftest.c >&5
>
> conftest.c:112:18: error: two or more data types in declaration specifiers
>
> 112 | #define intmax_t long long
>
> | ^~~~
>
> conftest.c:112:23: error: two or more data types in declaration specifiers
>
> 112 | #define intmax_t long long
>
> | ^~~~
>
> In file included from conftest.c:212:
>
> conftest.c:214:24: error: conflicting types for 'ngetpeername'; have
> 'int(int, void *, long unsigned int *)'
>
> 214 | int getpeername (int, void *, unsigned long int
> *);
>
> | ^~~~~~~~~~~
>
> /nasfarm/edelsohn/install/GCC12/lib/gcc/powerpc-ibm-aix7.2.5.0/12.1.1/include-fixed/sys/socket.h:647:9:
> note: previous declaration of 'ngetpeername' with type 'int(int, struct
> sockaddr * restrict, socklen_t * restrict)' {aka 'int(int, struct
> sockaddr * restrict, long unsigned int * restrict)'}
>
> 647 | int getpeername(int, struct sockaddr *__restrict__, socklen_t
> *__restrict__);
>
> | ^~~~~~~~~~~
>
>
> configure and config.h seems to get itself confused about types.
There seem to be two problems, both related to the include files of
your compiler:
- The configure test "checking for intmax_t..." must have found the
answer "no". But on a modern system, <stdint.h> should be defining
intmax_t already.
- This configure test that tries to find the getpeername declaration,
but cannot find it (maybe because of the first problem?):
================================================================================
for arg2 in "struct sockaddr" void; do
for t in int size_t "unsigned int" "long int" "unsigned long int"; do
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include <sys/types.h>
#include <sys/socket.h>
int getpeername (int, $arg2 *, $t *);
int
main (void)
{
$t len;
getpeername (0, 0, &len);
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"
then :
gl_cv_socklen_t_equiv="$t"
fi
================================================================================
I would concentrate on the first problem. If you don't get it fixed, then I'd
suggest to try 'gcc' from the AIX Toolbox [1] or 'xlc' (as an IBM product)
instead of 'gcc' (that looks like you built it yourself).
Bruno
[1] https://public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/SPECS/gcc12-12.3.0-1.spec
next prev parent reply other threads:[~2023-11-15 21:22 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 20:37 [PATCH v3 0/2] Replace intl/ with out-of-tree GNU gettext David Edelsohn
2023-11-14 23:06 ` Arsen Arsenović
2023-11-15 1:49 ` David Edelsohn
2023-11-15 12:29 ` building GNU gettext on AIX Bruno Haible
2023-11-15 19:26 ` David Edelsohn
2023-11-15 21:22 ` Bruno Haible [this message]
2023-11-15 21:31 ` David Edelsohn
2023-11-15 22:39 ` Bruno Haible
2023-11-16 16:00 ` David Edelsohn
2023-11-16 16:35 ` David Edelsohn
2023-11-16 18:01 ` David Edelsohn
2023-11-16 18:17 ` David Edelsohn
2023-11-16 18:52 ` Bruno Haible
2023-11-16 22:18 ` David Edelsohn
2023-11-16 22:46 ` Bruno Haible
2023-11-16 23:10 ` Arsen Arsenović
2023-11-17 8:33 ` Richard Biener
2023-11-17 8:49 ` Arsen Arsenović
2023-11-17 12:24 ` Bruno Haible
2023-11-17 13:06 ` Arsen Arsenović
2023-11-16 23:38 ` David Edelsohn
2023-11-17 0:07 ` Bruno Haible
2023-11-17 0:15 ` David Edelsohn
[not found] ` <84B39BF1-33D5-488E-8CF5-D08B09417568@gmail.com>
2023-11-16 17:44 ` David Edelsohn
2023-11-16 18:47 ` Bruno Haible
2023-11-16 18:50 ` Arsen Arsenović
2023-11-16 18:59 ` Bruno Haible
2023-11-16 19:14 ` Arsen Arsenović
2023-11-19 19:49 ` Bruno Haible
2023-11-15 14:14 ` [PATCH v3 0/2] Replace intl/ with out-of-tree GNU gettext Arsen Arsenović
2023-11-15 15:51 ` Xi Ruoyao
2023-11-16 18:48 ` Arsen Arsenović
2023-11-15 17:19 ` David Edelsohn
2023-11-16 18:33 ` Arsen Arsenović
2023-11-16 21:11 ` Arsen Arsenović
2023-11-16 21:40 ` David Edelsohn
2023-11-16 22:19 ` Arsen Arsenović
2023-11-16 22:30 ` David Edelsohn
2023-11-16 22:32 ` Arsen Arsenović
2023-11-16 23:59 ` David Edelsohn
2023-11-17 8:34 ` Arsen Arsenović
2023-11-17 8:50 ` Richard Biener
2023-11-17 8:56 ` Arsen Arsenović
2023-11-17 14:41 ` David Edelsohn
2023-11-17 15:16 ` Arsen Arsenović
2023-11-17 16:07 ` David Edelsohn
2023-11-18 18:10 ` Arsen Arsenović
2023-11-19 21:55 ` Bruno Haible
2023-11-19 23:00 ` Bruno Haible
2023-11-19 23:06 ` Andrew Pinski
2023-11-20 1:17 ` David Edelsohn
2023-11-20 21:18 ` Arsen Arsenović
2023-11-20 21:38 ` David Edelsohn
2023-11-21 0:44 ` Arsen Arsenović
2023-11-20 23:00 ` Bruno Haible
2023-11-21 0:45 ` Arsen Arsenović
2023-11-21 13:13 ` Arsen Arsenović
2023-11-21 16:28 ` David Edelsohn
2023-11-21 20:58 ` Eric Gallager
2023-11-15 19:58 ` David Edelsohn
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=4277517.TpOvJl0BfU@nimes \
--to=bruno@clisp.org \
--cc=arsen@aarsen.me \
--cc=bug-gettext@gnu.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.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.
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).